Engineering and architecture
Project closeout checklist for architects: what to archive
By SourceX Editorial · Updated
Short answer
An architect's project closeout archive should hold the contract history, the issued and record sets, and the construction administration logs with their links intact: RFIs, submittals, change documents and review comments. Before freezing the archive, tag each record set with its rights status. A log without its attachments and responses is barely a record.
Key takeaways
- Archive RFI, submittal and change logs together with their attachments, responses and cross-references.
- Capture internal review comments and markups before review sessions close or the team moves to the next project.
- Tag every record set with a rights status at closeout, while the people who know the contract are still on the project.
- Make a frozen, tagged archive a condition of closing the project number in project accounting.
What should an architect archive at project closeout?#
An architect should archive everything needed to explain what was designed, what was approved during construction and why: the contract and its amendments, the issued and conformed sets, the construction administration logs with their links intact, internal review comments and the record documents the agreement calls for. The archive should be complete before the team disperses.
Construction administration is where links matter most. An RFI answer refers to a sketch, which revised a detail, which triggered a change order, which was priced against a submittal. Archived as separate PDFs in separate folders, that chain disappears, and with it the firm's best evidence of how decisions were made.
The owner-architect agreement may define record drawing and closeout deliverables, so build the checklist from the contract rather than from habit.
The closeout archive checklist#
The closeout archive checklist below runs roughly in the order the work happens, starting before substantial completion and ending with a frozen archive. Each item names the record and what must travel with it.
- Confirm the final contract, every amendment and each additional services authorization, and file them with the fee history.
- Close the RFI log: every RFI answered or voided, with question, response, attachments and any resulting sketch or bulletin.
- Close the submittal log: final action on each item, review stamps, resubmittals and reviewer comments.
- Reconcile change documents: ASIs, bulletins, construction change directives and change orders, each cross-referenced to the RFI or submittal that caused it.
- Capture internal review comments: QA markups, design review notes and Bluebeam session markups, exported with the PDFs they reference.
- Archive issued sets, conformed sets and record documents in PDF, with the native Revit and CAD files and their linked references.
- Export project correspondence, meeting minutes and field observation reports filed to the project.
- Export logs from the contractor's platform, such as Procore, before the firm's project access ends.
- Hold a short lessons-learned review and file the notes with the project.
- Tag each record set with its rights status and retention date, then freeze the archive read-only.
Keeping log links intact#
Keeping log links intact means every log entry can still be followed to its attachments, response and consequences after the platform that produced it is gone. Summary exports often keep the entries but drop the attachments, while attachment dumps lose the entry each file belonged to.
One habit fixes most of this: export each log as structured data with its IDs, save attachments into folders named by those IDs, and keep cross-reference columns such as the RFI number on each change document. Check what a platform export actually contains before access ends: Procore's FAQ, for example, notes that for some tools its Project Archive export does not let you choose whether attachments are included.
| Log | What must stay linked | How links usually break |
|---|---|---|
| RFI log | Question, response, sketches, attachments and any resulting ASI or change | Summary export without attachments; responses left in email |
| Submittal log | Package, review stamp, comments, resubmittals and final action | Only the final stamped copy kept; earlier review rounds lost |
| Change log | ASI, CCD or change order, its cause, pricing and approval | Change documents filed apart from the RFI or submittal behind them |
| Review comments | Markup, the sheet version it applies to and its resolution | Review session closed without export, or sheet revised after markup |
| Meeting minutes | Decision, action owner and follow-up document | Minutes saved as PDFs with no reference to the log entries discussed |
Tag rights status at closeout#
Rights status tagging records, for each record set, who controls it and what restrictions apply. Closeout is the right moment because the project manager and contract administrator still remember which documents came from the client, which from consultants and which carry confidentiality terms. Years later, that knowledge has left with the people who held it.
These tags mirror metadata that enterprise dataset buyers increasingly expect. The Data & Trust Alliance's Data Provenance Standards, for example, include elements for confidentiality classification, consent documentation location and license to use. A firm that tags at closeout already holds most of that information if it ever needs it.
| Rights tag | Meaning | Typical examples |
|---|---|---|
| Firm internal | Created by the firm for its own work and not delivered to the client | Review notes, QA checklists, internal memos |
| Client deliverable | Delivered to the client, with use governed by the agreement | Issued sets, reports, record documents |
| Client furnished | Provided by the client or its separate consultants | Surveys, geotechnical reports, owner standards |
| Third party | Authored by consultants, contractors or suppliers | Consultant models, shop drawings, product data |
| Restricted | Security-sensitive, under NDA or flagged by the client | Facilities with security requirements, confidential programs |
| Personal data present | Contains names, contact details or images of people | Correspondence, site photos, sign-in sheets |
Who should own closeout inside the firm?#
Closeout should have one named owner per project, usually the project manager, with a firm-level records owner who sets the standard and checks completion. Without a named owner, closeout drifts into the next project's kickoff and the logs stay open indefinitely.
Make a frozen, tagged archive a condition of closing the project number in Deltek, Unanet or BQE Core. Tying closeout to accounting status gives finance a reason to ask about unfinished archives, which is often the nudge a busy project manager needs.
Illustrative: a studio standardizes closeout after a lost RFI trail#
Illustrative: a fictional architecture firm working on multifamily and hospitality projects receives an owner's question about a detail changed during construction years earlier. The archived RFI log lists the RFI, but the response sketch lived only in the contractor's Procore project, and the firm's access ended at closeout.
The COO introduces a closeout standard: logs exported as data with IDs, attachments in ID-named folders, Bluebeam review markups exported before sessions close, and a rights tag on every record set. Project numbers in Deltek Vantagepoint cannot be closed until the archive is frozen and tagged. Later projects have complete, linked trails, and the principals can see at a glance which archives are firm internal and which are client controlled.
Where SourceX fits after closeout#
A tagged closeout archive simplifies the Rights step of the SourceX five-step transaction: Supply, Rights, Preparation, Approval and Delivery. Record sets tagged firm internal, with intact links, are the usual starting point; client deliverables and third-party records go through the rights review or stay out.
Rights tags and closeout notes feed the SourceX Evidence Packet, which documents provenance, licensing rights, permitted use, the privacy record and release authorization. The firm keeps the archive in its own storage and approves every step.
Frequently asked questions
When should closeout start?
Closeout should start before substantial completion, not after final payment. Open RFIs and submittals are easiest to resolve while the contractor and consultants are still engaged, and starting early leaves time to export logs from platforms the firm does not control.
Do we archive consultant drawings?
Yes, as part of the project record, since they show what the firm coordinated and reviewed. Tag them as third party, because the consultant usually owns them, and keep them apart from the firm's own files so later reuse decisions are clear.
Which file formats should the archive use?
PDF for issued sets, logs and correspondence; native files for models and drawings; and structured data such as CSV or spreadsheets for logs, so entries and IDs survive. Avoid formats that need a platform subscription to open.
Should lessons-learned notes go in the archive?
Yes. Lessons-learned notes record what the team would change and why, which is often the most candid record of a project. Keep them firm internal, avoid personal criticism of named individuals, and file them with the project rather than in a separate shared folder.
What if our access to the contractor's platform has already ended?
Ask the contractor for an export of the RFI, submittal and change logs with attachments, and say which projects and date ranges you need. Many contractors keep project archives for their own retention needs. Record what was recovered and what was not, so later readers know where the trail has gaps.
How do we handle site photos with people in them?
Keep them as part of the record, but tag them as containing personal data. Photos of workers, neighbors or license plates may need removal or blurring before any reuse outside the firm, and access inside the firm can stay limited to the project team.
Sources
- The Use group of the Data & Trust Alliance Data Provenance Standards includes elements for confidentiality classification, consent documentation location, privacy-enhancing technologies applied, allowed and excluded processing and storage geographies, license to use, intended data use, and copyright, patent and trademark status. Source
- Procore's FAQ lists the tools its Project Archive tool can export from, and for some tools you cannot choose whether attachments are included. Source
Related resources
See if your company qualifies
A short company assessment. No data uploads are needed.