Project closeout archive context checklist: what to confirm before project records are put away

Short answer

Run three milestones in order: before closeout starts, before project records are archived, and before practical access to them ends. At each, confirm whether approved design changes can still be followed from the RFI to the executed change order and final cost, name who owns each item, and note what is lost if it is skipped. Use the contractor's documented steps, never invented dates, and record descriptions only.

Visual briefFull-size diagram
A horizontal countdown road from substantial completion to archive to end of project access, with checklist items about RFI references, settlement memos and archive location ticking off at each milestone.
The checklist as a countdown to the end of project access. Milestones follow the contractor's own documented steps.

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.

MilestoneTypical triggerSet byIf undefined
Closeout startsSubstantial completion or the final coordination meetingProject executiveUse the first closeout meeting on the calendar
ArchiveWarranty start, final payment or handover of turnover documentsProject controls or ITAsk who moves files and when
Access endsProject-level license lapses, cold storage, or owner handover onlyIT or operations directorMark 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.

ConfirmOwnerIf skipped
Change events or change orders cite the RFI that started themProject executiveLinks have to be reconstructed later from memory, if at all
Bundled change orders list each underlying RFIProject managerOne change order hides several design causes
Pending changes have a written route to resolutionProject executive and accountantSettled items end up in emails no one files
Who owns closed-project records under the prime contractOwner with counselRights 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.

ConfirmOwnerIf skipped
The archive keeps RFI, change event and change order logs with their reference fieldsProject controlsLogs survive but no longer point to each other
Closeout settlement memos are filed with the project, not in a mailboxProject accountantNegotiated outcomes, the hardest to trace, disappear first
The export route is known, and covers more than PDFsIT or project controlsStructured links are lost in a document dump
Which projects share the same practice, for the record set descriptionOperations directorEach 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.

ConfirmOwnerIf skipped
The documented date or event that ends accessIT or operations directorRecords lapse without a decision
Where the archive will live and who can describe itITNobody can say what the company still holds
Any retention rule that purges closed projectsRecords or risk managerHistory is deleted on schedule before anyone asks
Whether the owner wants an introduction to SourceX before access endsOwnerThe 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.

MilestoneItemStatusNote recorded
Closeout startsPriced changes point to the questionDoneAutomatic since 2021; spreadsheet before
Closeout startsCombined changes name each sourcePartialDrainage revision lists one of two questions
ArchiveNegotiated outcome filedAt riskRetaining wall agreement sits in one estimator's inbox
ArchiveExport carries reference fieldsDoneStructured log export, not only PDFs
Access endsDocumented stepDonePer-project license ends after final acceptance
Access endsOwner decisionPendingCEO 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.

  1. Step 1Share your linkSend your personal link to a company you know.
  2. Step 2Company appliesThe company applies itself at /apply.
  3. Step 3Company signs and is paidThe company signs, delivers its data and is paid by SourceX under its agreement.
  4. Step 4You get your rewardthe greater of $50,000 plus 5% and 15% of the actual supplier payout, with no cap. A reward becomes payable after SourceX has paid the referred company under its signed agreement and the payout conditions in the program terms are met, including finance approval and your tax and payment details.

Common questions

What counts as the switch-off milestone on a construction project?

Whatever ends practical access to the project records: a project-level software license ending, the project moving to cold storage, or files being handed to the building owner. Use the step the contractor actually documents.

Should the advisor organize the archive?

No. The contractor's project and IT teams decide how records are filed. The advisor makes sure the questions are asked before each step and writes down the answers.

What if the contractor is in financial difficulty?

Authority over records can change quickly in a restructuring. Confirm who can authorize today before anything else, and see the construction insolvency page for that situation.

Sources

  1. help.aiacontracts.com/hc/en-us/articles/1500009325281-Instructions…
  2. help.aiacontracts.com/hc/en-us/articles/1500009322061-Instructions…
  3. support.procore.com/products/online/user-guide/project-level/rfi…
  4. refer.sourcex.si/terms
  5. refer.sourcex.si/rewards

Free resources

Know a company with valuable proprietary data?

Become a referral partner, get your link and introduce the company’s CEO (in an owner-run company, usually the owner). Referral partners can join from most countries. We can't work with partners in countries or regions under U.S. sanctions or on U.S. restricted-party lists. The companies you introduce should be based in the U.S., Canada and the EU, or in the UK, Australia, New Zealand, India, Singapore, South Africa, Latin America, the UAE and Saudi Arabia with at least 70% of their data in English.

Refer a company →

I own a business

Explore licensing your company's data directly to SourceX for AI training and evaluation. Start a short assessment; no uploads needed.

Start an assessment