The Preconstruction-to-Field Handoff: What the Project Team Needs on Day One
Hand off scope decisions, clarifications, the submittal register, and the current drawings so the field starts from the same evidence preconstruction used.
Preconstruction produces months of decisions: what each trade carries, which exclusions were accepted, what bidders clarified, which alternates were taken, and which documents are current. Then the project moves to the field team, and much of that knowledge leaves with the people who made it.
A good handoff is not a meeting. It is a set of records the project team can rely on after the meeting ends, each connected to the documents that support it.
Why handoffs lose information
Preconstruction and operations often have different people, different tools, and different deadlines. The estimator knows why a proposal was leveled the way it was; the project manager inherits a number and a subcontract. The precon team knows which addendum changed the electrical scope; the superintendent has a drawing set and a schedule. When a question comes up three months later, the answer exists, but in an email thread, a spreadsheet tab, or someone's memory.
What to hand off
Hand off records, not summaries. At a minimum:
- The current document set. The drawings and specifications with every addendum incorporated, clearly marked as the set the work is based on. - The leveling record. The comparison matrix, accepted exclusions and qualifications, and the clarification questions with each bidder's answer. - Subcontract scopes. What each trade carries, what it excludes, and the interfaces between them. - The submittal register. Every required submittal, with responsible trades, need-by dates, and long-lead items flagged. - Open risks and assumptions. Pricing assumptions, allowances, pending owner decisions, and items carried as risk. - Commitments made to the owner. Accepted alternates, schedule assumptions, and anything promised during pursuit or negotiation.
Keep every record tied to its source
A handoff record is only useful if the next person can check it. "Electrical excludes temporary power" should come with the proposal page where the exclusion appears and the scope language it differs from. "Switchgear is a long-lead item" should come with the specification requirement and the lead time the team used. Records with sources can be verified in minutes; records without them get argued again.
Run the handoff around real questions
Instead of walking through every document, run the turnover meeting around the questions the field will actually ask:
1. What does each major trade include and exclude? 2. Which clarifications changed scope or price? 3. Which submittals are on the critical path? 4. Which drawing set is current, and what changed during bidding? 5. What risks did preconstruction carry, and who owns them now?
Each answer should point to a record the team can open later.
Make the current documents easy to reach
The field rarely asks for a document by its file name. A foreman asks for the second-floor fire alarm plan, not sheet FA102. If reaching the right sheet requires knowing the sheet index or the folder structure, every question becomes a call to the office. The handoff is the moment to make the current set findable by the people who will use it, and to agree who publishes changes once construction starts.
How Mobus carries the evidence forward
Each Mobus workflow keeps its output reviewable after preconstruction ends. Mobus Bid Leveling exports a source-linked Excel workbook in which matrix findings, cited evidence, risks, and clarifications remain reviewable. Mobus Submittal Review keeps each review's findings attached to the package version that was reviewed, with an exportable cited register and review report.
For the field, Mobus Document Retrieval lets the team ask for a drawing in plain language, review the ranked match, and open the original document at the cited page. It reads page-level content and title-block fields rather than file names alone. Document control still decides what is current: issue and revision metadata can inform a result, but supersession resolution is not guaranteed, and a new upload is not added to the search index automatically.
A day-one checklist
- Publish the current document set with addenda incorporated. - Hand over the leveling record with exclusions and clarifications. - Share subcontract scopes and the interfaces between trades. - Transfer the submittal register with need-by dates and long-lead items. - Review open risks and owner commitments with the project team. - Agree who publishes document changes after day one.
When the handoff is built from cited records, the project team starts where preconstruction left off instead of starting over.