Every RFI, submittal, and change order on a Canadian project eventually has to show up somewhere in the closeout package, and provincial limitation periods mean those records often need to survive well past the day the keys change hands. Building document control around what closeout will require, rather than scrambling to assemble it afterward, is what keeps a project’s records usable instead of just accumulated.
Key Takeaways
- Canadian construction documentation generally follows CCDC standard forms, with RFIs, submittals, change orders, and daily records all feeding into the eventual closeout package.
- Provincial limitation periods, commonly around two years from discovery, mean project records need to be retained well past handover, not filed away and forgotten.
- Submittals prove that installed work matches what was approved, and missing ones are a common closeout holdup.
- Change orders need written authorization before the work happens, not a verbal agreement reconstructed afterward.
- Setting up the document structure before a project starts is far faster than organizing it retroactively mid-project.
- Most of this tracking work can be delegated to a VA, while approvals and technical sign-offs stay with the project team.
Why Closeout Is Where Document Control Gets Tested
A closeout package is really just a compilation of everything that should have been tracked properly the whole way through. If RFIs, submittals, and change orders were logged as they happened, closeout is mostly assembly. If they weren’t, closeout turns into archaeology, chasing down O&M manuals from suppliers who stopped returning calls months ago and reconstructing approvals nobody wrote down.
Canadian construction contracts generally follow standard forms published by the Canadian Construction Documents Committee, with CCDC 2 being the most common package of agreement and general conditions. That standard framework is part of why certain documents, drawings, specifications, change orders, and submittals aren’t optional extras, they’re contractually expected from day one.
- Lien waivers from every subcontractor and supplier in the payment chain
- As-built drawings reflecting what was actually constructed, including any field changes
- Operation and maintenance manuals and warranty documents for installed systems
- A final payment application reconciling the contract sum against all approved change orders
One change made during construction often requires several of these documents at once. Swapping a specified material for an equivalent one might mean a new submittal, an updated O&M manual, a revised warranty, and a note on the as-built drawings, all traceable back to the single decision that started it.
Document Control Across the Project
Different documents get created at different points and carry different retention needs.
| Document Type | When It’s Created | What Happens to It Later |
| RFIs | During construction, whenever a clarification is needed | Filed with the project record for the retention period |
| Submittals | Before installation, for architect or engineer approval | Included in the closeout package as proof of compliance |
| Change Orders | Whenever scope, cost, or schedule changes | Reflected in final payment and as-built drawings |
| Closeout Package | Assembled at project completion | Retained for the full provincial limitation period |
The common thread is that nothing here is really a one-time event. An RFI logged in March still matters if a dispute surfaces two years later, which is exactly why treating each category as a running record, not a folder that gets closed the day it’s created, matters more than it might seem in the moment.
A change order is the clearest example. It’s created once, but it echoes through the rest of the project: into the final payment application, into the as-built drawings, and potentially into a dispute years down the line if the paper trail doesn’t hold up.
Where Records Have to Outlive the Project
Limitation periods for construction claims vary by province, but a common pattern is roughly two years from when a problem is discovered, not from when the project finished. A leak that shows up three years after handover can still trigger a claim if it’s discovered within the limitation window from that point.
That timeline has a practical consequence: project records can’t just live in whatever folder was convenient during construction. They need a long-term home that survives staff turnover, closed job sites, and a contractor’s own internal reorganizations, organized well enough that someone can actually find the right document years later, not just technically retained somewhere.
This is where a lot of otherwise well-run projects quietly fail. The documentation was solid while the project was active, but nobody planned for where it would live once the team moved on to the next job, and two years later the file is technically retained but practically unusable.
What a VA Can Keep Running
Most of this is tracking and organization rather than technical judgment, which is why it fits well under RFI tracking coordinator support:
- Logging RFIs with dates and deadlines as they come in, not batched at the end of the week.
- Tracking submittal status, submitted, under review, approved, or rejected, across every trade package.
- Maintaining a change order register with authorization status and cost impact.
- Assembling the closeout package incrementally as documents arrive, rather than all at once at the end.
- Organizing lien waivers as they’re collected instead of chasing them down after substantial completion.
- Filing as-built markups and O&M manuals as they arrive from subs and suppliers.
- Flagging retention and archiving requirements once a project formally closes out.
- Cross-referencing related documents, so an RFI stays linked to the drawing or spec it affects.
Change orders with a cost impact also connect directly to financial documentation support for contractors, since the final payment reconciliation depends on every approved change being accurately reflected.
What Stays With the Project Team
None of this tracking replaces technical judgment. Whether a submitted product actually meets spec, how to resolve a design conflict raised in an RFI, and whether a change order’s scope is reasonable are calls that stay with the architect, engineer, or project manager.
What gets delegated is the system underneath those decisions: the logging, the deadlines, the filing. That’s the same division of labour behind most Canadian construction virtual assistants arrangements, administrative structure, not technical sign-off.
Setting Up Before You Need It
- Set up the folder structure and naming convention before the project starts, not partway through.
- Start logging RFIs and submittals from the first one, even before volume feels like it justifies a system.
- Collect lien waivers as work is completed rather than waiting until closeout to chase them all down.
This connects naturally to remote construction coordinator support, since scheduling and document control tend to run through the same person, and it’s worth planning ahead for Canadian project admin workflows as a project scales toward closeout.
Things to Know
- Canadian construction contracts commonly follow CCDC standard forms, which define what documentation is contractually required.
- Provincial limitation periods mean project records typically need to be retained well beyond handover, commonly around two years from discovery of an issue.
- Submittals prove installed work matches what was approved; missing ones are a common closeout holdup.
- Change orders need written authorization before the work happens, not a verbal agreement reconstructed afterward.
- Setting up the document structure before a project starts is far faster than organizing it retroactively mid-project.
- Technical review and approval authority stays with the architect, engineer, or project manager; a VA maintains the tracking around it.
Frequently Asked Questions
What’s the difference between an RFI and a submittal?
An RFI asks a question that needs an answer before work proceeds; a submittal shows what’s actually going to be installed for approval before it happens.
Both go through a formal review process, but they serve different purposes: one clarifies an unclear detail, the other confirms a specific product or material meets what was specified. Mixing the two up in tracking usually causes more confusion than the original question ever did.
How long do Canadian contractors need to keep project records?
Retention periods vary by province, but limitation periods for construction claims commonly run around two years from when a problem is discovered, which can be well after the project itself finished.
That means project records need a long-term home, not just a folder that gets cleared out once the next job starts, since the window for a claim often opens well after the crew has moved on.
Can a virtual assistant manage submittal tracking?
Yes, a VA can track submittal status, log RFIs, and maintain a change order register, though the actual technical review and approval stay with the architect, engineer, or project manager.
The tracking and organizing side is process-driven enough to delegate; the judgment call on whether a submitted product actually meets spec stays with whoever has the technical authority to approve it, typically the architect or engineer of record.
What happens if a change order isn’t documented before the work happens?
Undocumented change orders are one of the most common sources of payment disputes, since there’s no written record of what was authorized or what it should cost. A subcontractor who does extra work on a verbal direction can end up unpaid if the owner denies a change with no paper trail behind it, which is why written authorization before the work starts matters more than it might seem in the moment, especially on a fast-moving site.
What documents are typically required for project closeout in Canada?
A typical closeout package includes lien waivers, as-built drawings, O&M manuals, warranty documents, and a final payment application reflecting all approved change orders.
Assembling these as the project goes, rather than scrambling for them after substantial completion, is usually the difference between a closeout that takes days and one that takes months, and between prompt final payment and a drawn-out holdback release.
Closeout Doesn’t Create the Problem, It Reveals It
Closeout doesn’t create the paperwork problem, it just reveals whichever one was building the whole time. A project with clean RFI logs, tracked submittals, and documented change orders closes out in days; one without them can drag on for months chasing down records that should have been filed as they happened. Reach out to see what a document control system built around your closeout requirements could look like from day one.
