Define the audit question
A post-award audit usually asks whether the cost was built from the documents and whether later changes are traceable to a real scope difference. It may also ask who approved an assumption and when the team knew about a risk. The turnover file should answer those questions without requiring the original estimator to remember the bid.
Write the likely questions before choosing the files. Keep the audit scope practical. The file does not need every email, but it needs the documents that explain how the cost was formed.
The estimate summary detail reconciliation shows how the total should tie to the detail, and the project cost analyst service describes the review support that can maintain the file after award. AACE recommended practices provide a useful model for a documented cost basis. The total-to-detail tie is described in the estimate summary reconciliation.
The project cost analyst service describes who can maintain the file after award. AACE recommended practices provide a useful model for a documented cost basis. Use those references to keep the turnover file complete and traceable.
Collect the source set
Start with the bid documents, the addenda, the final drawing set, and the specifications that were priced. Record the revision or issue date for each item so a later reader can tell which version was used. Include the bid form, the alternates, and the unit cost schedule when they were part of the submission.
A file with the right documents but no revision record is only half complete. Add the takeoff files, the quantity summary, and the quote log with the final quotes. Keep the source documents separate from the working files so the audit can compare them.
If a quote was replaced, retain the replacement note and the reason. The chain from the source to the cost should be visible without opening a dozen unrelated folders.
Capture the assumptions
List the assumptions that materially affect the cost, including productivity, crew size, access, weather, escalation, and exclusions. Give each one a source, a date, and an owner. An assumption without a source is a guess, and a guess without an owner cannot be reviewed.
The audit should be able to see which assumptions were tested and which were accepted as risks. Include the open items that existed at bid time, even if they were later resolved. A later reviewer needs to know what was unresolved when the cost was set.
Mark each item as closed, carried, or excluded in the bid. That status explains why the submitted cost may differ from a later estimate built with better information.
Index the file
Create a one-page index that maps each audit question to the folder and file that answers it. Use the same categories as the estimate so a reader can move from the summary to the detail. Keep the index current when a file is added or replaced.
A good index saves more time than a large folder with no structure. Name files with the trade, document type, and revision rather than a personal shorthand. Avoid duplicate names that differ only by a date suffix, because the wrong version is easy to open under pressure.
Store the index at the top level and include the name of the person who maintained the file. A future reader should not have to guess who to ask.
Hand off and review
Hand the file to the project team at award, not at the first audit request. Walk through the index and the major assumptions in a short meeting. Ask the project manager to confirm that the file matches the contract and the buyout plan.
A turnover that happens before the team is busy is more likely to be accurate. Review the file again after buyout to see whether the assumptions held. Add the buyout results and any scope changes without deleting the original entries.
That layered record shows how the estimate moved from bid to construction. The post-award audit then becomes a review of documented decisions rather than a search for missing evidence.
Keep the file useful after handoff
A turnover file is only useful if the project team can add to it without breaking its structure. Give the team a simple place to record buyout results, change orders, and scope clarifications. Keep the original bid basis separate from the later entries so the history stays readable.
The file should grow by layers rather than by overwriting the original record.Review the file at the first change order and at the first buyout award to confirm that the index still works. If a new document type appears, add a category instead of dropping the file into a miscellaneous folder. A little maintenance during the project is far cheaper than rebuilding the record during an audit.
The project team should be able to find the answer without calling the estimator. The file should also record the bid result and the reason the project was won or lost. A lost bid with a clear cost comparison is useful evidence for the next estimate, and a won bid with a thin margin is useful evidence for the buyout plan.
Add the result after the award decision without changing the original bid record. That final layer completes the turnover history. The file should be easy to transfer to a new project manager without a long explanation.
A short cover page with the project name, the bid date, the contract value, and the file owner saves time on the first day. Add a note about the largest risk the estimate accepted and where the supporting evidence sits. That context helps the new owner ask the right question before the first change order.
| Section | Contents | Audit use |
|---|---|---|
| Bid basis | Drawings, specifications, addenda, and bid form | Shows what was priced |
| Quantity trail | Takeoff files, summaries, and variance notes | Shows how quantities were derived |
| Commercial trail | Quote log, replacements, and validity dates | Shows the source of each trade cost |
| Assumptions | Productivity, access, escalation, and exclusions | Shows what was accepted as risk |
| Open items | Clarifications, qualifications, and status | Explains differences from later estimates |