This checklist belongs to the project closeout guide for construction technology advisors. The 15-minute meeting agenda gathers most answers; this page tracks them against the steps that put records away.
The clock: three closeout milestones
Every contractor puts records away differently. Before ticking anything, write down each milestone as the company defines it.
| Milestone | Typical trigger | Set by | If undefined |
|---|---|---|---|
| Closeout starts | Substantial completion or the final coordination meeting | Project executive | Use the first closeout meeting on the calendar |
| Archive | Warranty start, final payment or handover of turnover documents | Project controls or IT | Ask who moves files and when |
| Access ends | Project-level license lapses, cold storage, or owner handover only | IT or operations director | Mark open; ask who decides |
Before closeout starts
The project team still remembers which RFI caused which change. That memory is the cheapest record there is.
| Confirm | Owner | If skipped |
|---|---|---|
| Change events or change orders cite the RFI that started them | Project executive | Links have to be reconstructed later from memory, if at all |
| Bundled change orders list each underlying RFI | Project manager | One change order hides several design causes |
| Pending changes have a written route to resolution | Project executive and accountant | Settled items end up in emails no one files |
| Who owns closed-project records under the prime contract | Owner with counsel | Rights questions surface after the team disperses |
AIA's G716 instructions say an RFI does not authorize changes in cost or project time, so the commercial outcome has to be recorded elsewhere. G701 instructions say executing a change order records agreement on contract sum and time. This milestone is about making sure the reference between the two is in place while people still know it.
Before records are archived
Archive steps tend to flatten structure: logs become exports, links become filenames.
| Confirm | Owner | If skipped |
|---|---|---|
| The archive keeps RFI, change event and change order logs with their reference fields | Project controls | Logs survive but no longer point to each other |
| Closeout settlement memos are filed with the project, not in a mailbox | Project accountant | Negotiated outcomes, the hardest to trace, disappear first |
| The export route is known, and covers more than PDFs | IT or project controls | Structured links are lost in a document dump |
| Which projects share the same practice, for the record set description | Operations director | Each project is judged alone and looks thin |
Procore's documentation describes creating a change event directly from an RFI when both tools are on a project; where a team worked that way, check that the archive route keeps that link. Exporting Procore project data covers what typically leaves the system.
Before project access ends
After this step, whatever was not kept is gone or expensive to recover.
| Confirm | Owner | If skipped |
|---|---|---|
| The documented date or event that ends access | IT or operations director | Records lapse without a decision |
| Where the archive will live and who can describe it | IT | Nobody can say what the company still holds |
| Any retention rule that purges closed projects | Records or risk manager | History is deleted on schedule before anyone asks |
| Whether the owner wants an introduction to SourceX before access ends | Owner | The choice is made by default |
Worked example: one contractor's countdown
Illustrative. A 450-person civil contractor finishing a highway interchange for a state transportation department, its eleventh public works job on the same platform.
| Milestone | Item | Status | Note recorded |
|---|---|---|---|
| Closeout starts | Priced changes point to the question | Done | Automatic since 2021; spreadsheet before |
| Closeout starts | Combined changes name each source | Partial | Drainage revision lists one of two questions |
| Archive | Negotiated outcome filed | At risk | Retaining wall agreement sits in one estimator's inbox |
| Archive | Export carries reference fields | Done | Structured log export, not only PDFs |
| Access ends | Documented step | Done | Per-project license ends after final acceptance |
| Access ends | Owner decision | Pending | CEO wants to read the agency contract terms first |
The "at risk" row is a closeout housekeeping item in its own right; the advisor raises it because the project record is incomplete, not because of a referral. The engineering change order process page shows the manufacturing equivalent of this chain.
Who can authorize, and what stays unknown
- Records: closed projects and years with a consistent practice, described by the contractor.
- Owner: the contractor, subject to owner and design-team contracts project by project.
- Authority: the president, CEO or COO named before closeout.
- Fit: 50+ full-time employees at peak (contractors excluded; full-time field staff on payroll count), a documented operating history, rights to license and an authorized contact. Companies in the U.S., Canada and the EU qualify, as do companies in the UK, Australia, New Zealand, India, Singapore, South Africa, Latin America, the UAE and Saudi Arabia when at least 70% of the data is in English.
Unknown until SourceX reviews it: demand for design-change records, the rights result, any offer and any reward. When the owner opts in, send the introduction email. Sign the Channel Partner Agreement first; the first valid introduction within the 90-day window is credited when the company submits a verified application, one partner per company. SourceX pays any reward separately, never from the contractor's payout. Illustrative only: if the contractor were paid USD 800,000 for a qualifying completed handoff and it was the company's first qualifying transaction, the reward would be USD 120,000 (15% of the payout, which is more than the USD 50,000-plus-5% floor); a further qualifying transaction agreed within 12 months would pay 15% with no floor and no cap. See rewards. For the owner's perspective see construction data monetization; where the contractor is under financial stress, see construction company insolvency.
Next step
Refer a company. No cap on rewards. Default reward on a company's first qualifying transaction: the greater of $50,000 plus 5% and 15% of Actual Supplier Payout, with no cap; further qualifying transactions first agreed within 12 months of the first Closing pay 15%. Eligibility and payment conditions apply, including the USD 100,000 Minimum Transaction, and a signed Schedule A or addendum can differ. A lead, meeting or signature alone does not trigger payment.
If the countdown shows traceable design changes and the owner wants to talk before access ends, register as a partner, check the contractor against who qualifies and read the program terms.