Preserving RFI-to-change-order history at closeout: a retention timeline of what disappears first

Short answer

Before closeout, inventory five record classes and the date each one loses access: RFIs with responses and activity logs, drawing version history, notice letters, change-coded cost, and executed or rejected change orders. Personal mailboxes and owner-portal access usually go first. Platform seats follow, then the contractor's own retention period. Note who owns each class and the real access date, and leave the decision to keep anything to the company's authorized people and counsel.

Visual briefFull-size diagram
Record lanes run from completion to three years after final payment; PM mailbox notices, owner portal drawings, platform RFI logs and cost and change orders each stop at their access point, while an archive kept with company approval runs to the end.
Illustrative closeout schedule. Real dates come from the company's contracts, licenses and retention policy.

This timeline is part of change order data in construction. The closeout conversation itself is covered in the project closeout guide; this page covers when each record is at risk.

The closeout timeline, month by month (Illustrative)

An invented schedule for a fictional 300-person specialty contractor finishing a public-sector building. Months count from substantial completion. Every date here is an example; the real ones sit in the company's contracts, software licenses and retention policy.

WhenEventWhat is at riskWho approves keeping it
Month 0Substantial completionNothing yet; all systems liveNot applicable
Month 1Field and subcontractor seats removed from the project platformDaily reports and comments tied to people who leaveProject executive
Month 2Project manager reassigned or leavesNotice letters filed in a personal mailboxIT under the company's mail retention policy
Month 3Owner's document control project handed over or set read-onlyDrawing versions and transmittals the contractor never copiedContracts manager, under the owner contract
Month 6Platform license for the project downgraded or archivedRFI activity logs and attached referencesPlatform administrator with the project executive
Month 9Final payment receivedStart of the federal retention clock where it appliesCFO and counsel
Final payment plus 3 yearsFederal baseline retention period endsCost records and change files kept only for that periodCFO and counsel, under policy

The last row comes from federal rules. Under FAR 4.703(a), contractors make records available for 3 years after final payment, or for shorter periods set for certain records; a contract clause can require longer, and electronic records may not be deleted or overwritten during the period. Private contracts set their own terms.

How long each record type tends to be kept

Retention depends on the record's home, not on how important it is. The table shows the usual driver for each class, so a partner knows which question to ask.

Record typeWhere it usually livesWhat sets how long it staysQuestion to ask
RFI, official response, activity logProject platformSoftware license and project archive settingsWhat does a project archive include, and until when?
Drawing versions and transmittalsOwner's or contractor's document controlOwner contract and who controls the projectDo you hold your own copy, or only access to the owner's?
Notice lettersDocument control mail or personal mailboxesMail retention policyAre notices filed centrally, or in project managers' mail?
Cost by changeJob cost or ERPAccounting retention policy, contract audit clausesWas extra work coded separately on closed jobs?
Change orders, executed, rejected and withdrawnChange order log, contract filesContract audit clauses, company policyAre rejected and withdrawn requests kept too?

Accounting and contract files tend to be kept longest because contract audit clauses and accounting retention policies usually cover them. Project-platform detail, the record that shows how a question became a change, tends to be kept the shortest.

What disappears first, and why

Three things usually go before anyone decides to delete them.

Context in mailboxes. A notice letter sent from a project manager's mailbox lives as long as that mailbox. When the person leaves, the letter that turned an RFI answer into a change can disappear, even though the change order that cites it survives.

Version history after a copy. Oracle Aconex documents that document history does not transfer when documents are copied to another project, and that an organization sees other organizations' versions only once they are transmitted to it. A contractor that copies drawings into its own archive project keeps the files but not the trail behind them.

Links in exports. Autodesk documents that a single-RFI PDF export can include references and the activity log, but embeds only PDF files and leaves out files over 30 MB. A turnover package built from exports can keep each RFI while dropping the marked-up model or large drawing set it referred to.

Cost records and executed change orders tend to survive longest. That leaves an archive with the answer and the money but without the reasoning in between. The system map shows which keys connect them.

Who must approve keeping it

Keeping records is a company decision, never a partner's. In a contractor of this size:

  • Project executive or operations lead: project archives and platform settings.
  • Contracts manager: anything controlled by the owner contract, including access to the owner's document control.
  • IT: mailbox and file-share retention under company policy.
  • CFO: accounting records and the retention schedule.
  • Counsel: anything under a claim, dispute or litigation hold, which stays untouched.

A partner's job is to ask, note and pass the dates on. A partner should never suggest keeping data beyond the company's policy, copying records out of an owner's system, or exporting anything for an introduction.

What to write down for the introduction

Metadata only: record classes, projects and years covered, the system and owner for each, and the documented date access changes. If no date is documented, there is no deadline to mention. The company must have 50+ full-time employees at peak (contractors excluded), documented operating history, rights to license and an authorized contact, the CEO, who can authorize a licensing discussion and sign. 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. What stays unknown until SourceX reviews it: which records the owner contracts allow, and whether any buyer wants them. The RFI log page and Procore project data exports cover nearby records, and the surety bond agent guide covers another advisor who sees contractors at closeout.

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 a contractor can tell you when each record class loses access and who decides what is kept, register as a partner, confirm the company on who qualifies and read the program terms before introducing its decision-maker.

  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

Should a partner tell the contractor to keep its records longer?

No. Retention is the company's decision under its contracts and policy, and anything under a legal hold belongs to counsel. A partner can ask what the dates are and note them; that is all.

Is closeout a reason to rush an introduction?

Only if the company has a documented date when access ends. A real license expiry or handover date is a reason to have the conversation now; a vague sense that records might be lost is not.

What if the company already archived everything as PDFs?

Note it. A turnover archive keeps the documents but often loses activity logs, system versions and the links between records, so ask what was exported and in what form.

Sources

  1. acquisition.gov/far/4.703
  2. help.aconex.com/documents/how-do-version-control-and-the-aco…
  3. help.autodesk.com/cloudhelp/ENU/Build-Rfis/files/work-rfis/Exp…
  4. refer.sourcex.si/terms

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