# RFI and change order records at closeout: timeline | SourceX

Canonical: https://refer.sourcex.si/guides/preserve-rfi-to-change-order-decisions-records
Last updated: 2026-11-04

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.

This timeline is part of [change order data in construction](/data-types/change-order-data-construction). The closeout conversation itself is covered in the [project closeout guide](/guides/moment-project-closeout-construction-technology-advisors); 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.

| When | Event | What is at risk | Who approves keeping it |
|---|---|---|---|
| Month 0 | Substantial completion | Nothing yet; all systems live | Not applicable |
| Month 1 | Field and subcontractor seats removed from the project platform | Daily reports and comments tied to people who leave | Project executive |
| Month 2 | Project manager reassigned or leaves | Notice letters filed in a personal mailbox | IT under the company's mail retention policy |
| Month 3 | Owner's document control project handed over or set read-only | Drawing versions and transmittals the contractor never copied | Contracts manager, under the owner contract |
| Month 6 | Platform license for the project downgraded or archived | RFI activity logs and attached references | Platform administrator with the project executive |
| Month 9 | Final payment received | Start of the federal retention clock where it applies | CFO and counsel |
| Final payment plus 3 years | Federal baseline retention period ends | Cost records and change files kept only for that period | CFO 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 type | Where it usually lives | What sets how long it stays | Question to ask |
|---|---|---|---|
| RFI, official response, activity log | Project platform | Software license and project archive settings | What does a project archive include, and until when? |
| Drawing versions and transmittals | Owner's or contractor's document control | Owner contract and who controls the project | Do you hold your own copy, or only access to the owner's? |
| Notice letters | Document control mail or personal mailboxes | Mail retention policy | Are notices filed centrally, or in project managers' mail? |
| Cost by change | Job cost or ERP | Accounting retention policy, contract audit clauses | Was extra work coded separately on closed jobs? |
| Change orders, executed, rejected and withdrawn | Change order log, contract files | Contract audit clauses, company policy | Are 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](/guides/rfi-to-change-order-decisions-records-across-systems) 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](/data-types/construction-rfi-log) and [Procore project data exports](/systems/procore-export-project-data) cover nearby records, and the [surety bond agent guide](/guides/surety-bond-agent-for-contractors) 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](/register), confirm the company on [who qualifies](/who-qualifies) and read the [program terms](/terms) before introducing its decision-maker.

## Sources

- https://www.acquisition.gov/far/4.703
- https://help.aconex.com/documents/how-do-version-control-and-the-aconex-audit-trail-work/
- https://help.autodesk.com/cloudhelp/ENU/Build-Rfis/files/work-rfis/Export_RFIs.html
- https://refer.sourcex.si/terms
