Project Handoff for General Contracting

Locate the final proposal, scope letter, alternates list, and any clarifications sent to the client. Make sure you are using the final versions that match what was accepted, not an earlier draft.

Obtain the final approved estimate, including summaries by division/trade, alternates, allowances, and unit prices. Confirm this version matches the submitted number and has any post-review changes included.

If available, add the client’s notice of award, letter of intent, or executed contract draft to the package. These documents confirm the agreed value, schedule expectations, and any special conditions.

Search for and save important emails or letters that clarify scope, exclusions, or special client expectations (for example, phasing constraints, site access rules). Avoid saving every email—only those with real content decisions.

Place all files into a “Project_Handoff” folder with subfolders such as “Proposal,” “Estimate,” “Contract,” and “Key_Correspondence.” Use clean, descriptive file names so someone new can quickly see what each file is.

Create a simple one-page index listing each document, its date, and where it is stored. Save this index at the top of the “Project_Handoff” folder so the team can see at a glance what’s included.

Open your company’s project handoff checklist (or create a basic one) with sections for commercial documents, technical documents, and communications. This becomes your “go/no-go” list for handoff readiness.

Verify that proposal, final estimate, award letter or contract, and any contract exhibits (insurance requirements, schedules of values templates, etc.) are present. Note anything missing or draft-only in the checklist.

Ensure the latest issued drawings, specifications, and all addenda that were priced are available and stored in a project folder. Confirm that the drawing/spec issue dates match what was used for pricing.

Check that client contact names, roles, billing addresses, and any project numbers the client uses are documented somewhere accessible (CRM, handoff sheet, or contact list). Add them if missing.

If any essential items are missing (for example, signed contract, certain addenda, or client contact info), log them in the checklist with a note on who will obtain them and by when.

Confirm that the minimum required items are in place before scheduling the handoff meeting. If not, coordinate with sales/estimating to fill the gaps so the project team does not start with blind spots.

Read the executive summary sections of the proposal, the cover sheets of drawings, and any award letters. Focus on descriptions of building use, size, phases, and key requirements.

In a short document, describe the project in a few paragraphs: building type, approximate size, number of levels, primary systems, and any special features (for example, labs, kitchens, data rooms). Avoid internal shorthand or acronyms that a new team member might not know.

Clarify whether the job is lump sum, GMP, CM at-risk, design-build, or another structure. Note any special pre-construction services obligations, such as early budgeting or target value design.

Add bullets for major constraints: required completion dates, working hour restrictions, site access limits, interim milestones, and any third-party coordination (for example, tenants, neighbors, agencies).

From proposal and conversations, identify what the client cares about most: schedule, budget, disruption minimization, specific quality benchmarks, or future expansion. Note these clearly so the team can make decisions that support them.

Save the “Project Scope & Constraints Summary” in the handoff folder and send it to the incoming project manager, pre-con manager, and superintendent as pre-reading for the handoff meeting.

Open the final estimate, estimate review summary, and bid risk assessment documents. Note how costs are grouped, where fee and contingency sit, and any key risk-related notes.

List the top few cost drivers by dollar amount or percentage of total (for example, structure, envelope, MEP systems, sitework). Note any unusually high or low areas compared to typical projects.

Write a short section explaining whether the bid was aggressive, neutral, or conservative, and in which areas. For example, you may have tight numbers on structure but more contingency on interior finishes due to incomplete design.

List the major contingencies and allowances in the estimate, including what they are meant to cover and their dollar values. Clarify which are general and which are tied to specific scopes or risks.

From the estimate notes and risk register, extract assumptions that could significantly affect cost if they change (for example, assumed productivity in an occupied space, temporary facilities scope, or extent of hazardous materials).

Pull this information into a 1–2 page summary and save it in the handoff folder. This document becomes the quick reference for the project team when making early decisions that affect cost.

Review proposal clarifications, estimate notes, and the bid-phase risk register. Extract any statements that start with “assume,” “exclude,” “by owner,” or “not included” and list them in a document.

Look at RFIs and addenda that affected scope or quantities. Note which design questions were answered and which were deferred or partially addressed, flagging any that still present risk.

Organize the list into three sections: assumptions you made to price the job, clarifications that were formally documented with the client, and open issues that still need resolution in pre-construction.

For each open issue, briefly note the likely impact area: cost, schedule, logistics, safety, or quality. This helps the team prioritize which issues to tackle first.

Mark which assumptions and clarifications were actually communicated in the proposal or during negotiation versus those that remained internal. This distinction is important for how the team approaches conversations with the client.

Save this log in the handoff folder and share it with the incoming project manager and pre-con manager as required reading. It will also feed directly into later Contract Review and Pre-Construction Readiness checks.

List the roles that must attend: estimating lead, proposal or BD lead, incoming project manager, pre-construction manager (if separate), field superintendent (if known), and possibly a finance representative for large jobs.

Set the meeting for soon after award or notice of intent, ideally within a few business days. Use a calendar invite with a clear subject (for example, “Project Handoff – [Project Name]”).

Draft an agenda that includes: project overview, scope and delivery method, estimate/pricing summary, key assumptions and open issues, client expectations, and next-step assignments. Allocate rough times to each section.

Add links or attachments for the scope summary, estimate summary, and assumptions/open issues log to the calendar invite. Ask attendees to review them briefly beforehand so meeting time is not spent reading.

Follow up with key people to ensure they can attend. If critical decision-makers cannot attend, reschedule within reason rather than holding a weak handoff that will need to be repeated.

Reserve a meeting room with a screen or set up a video call with screen sharing. Make sure you can display the estimate and key documents during the discussion without technical issues.

Begin the meeting with a quick review of the project scope summary and client priorities. Make sure the new team understands what matters most to the client, not just the technical details.

Have the estimator present how the number was built: major cost drivers, contingencies, allowances, and where the bid is tight or conservative. Encourage questions so the team really understands the cost structure.

Go through the assumptions and open issues log, highlighting items with the biggest potential impact. Discuss whether any should be addressed immediately with the client or design team.

Review any schedule dates, phasing requirements, and basic site constraints. Note where the schedule is aggressive and where the team has some flexibility.

Clarify who will lead pre-construction, who will own client communication, and how decisions will be made during this phase. Make sure everyone understands their responsibilities coming out of the meeting.

Assign someone to record questions, decisions, and follow-up tasks as they are discussed. Do not rely on memory; every agreed action should have an owner and a due date.

Right after the handoff meeting, the note-taker should review and clean up their notes while everything is fresh. Group similar items and remove duplicate or unclear points.

For each issue, write a specific action statement (for example, “Clarify MEP scope for rooftop units with engineer” instead of “MEP questions”). Clear actions are easier to track and complete.

Decide who is responsible for each action and by when it should be completed. The owner should be a person, not a team (for example, “Alex – Precon Manager,” not “Precon”).

Mark which items must be done immediately (for example, those affecting contract signing or early procurement) versus items that can be addressed later in pre-construction.

Add all action items into your preferred tracking tool (spreadsheet, project management system, or task software) and link it in the project folder. Make sure owners are notified of their tasks.

Schedule a quick follow-up meeting or call within 1–2 weeks to review progress on these handoff actions, especially those that affect Contract Review, Budget Finalization, and Schedule Development.

If not already created, set up the standard project folder tree in your file system or document management platform (for example, folders for Contract, Drawings, Specs, Estimate, Precon, Procurement, Field, etc.).

Copy the finalized proposal, estimate, handoff summaries, and key correspondence from the bid/handoff area into the appropriate project folders. Avoid storing duplicate versions in multiple places without clear labels.

Create or confirm the project record in core systems such as ERP/accounting, project management software, and CRM. Make sure basic data (client, location, value, key dates) are entered correctly.

Work with IT or system admins to ensure the right team members have access to the project folders and systems. Remove access for people who do not need it, especially for sensitive commercial documents.

Where possible, link project IDs across systems (for example, make sure the project number in accounting matches that in the project management platform and folder naming). This reduces confusion later.

Notify the project team where they should store and pull documents going forward. Be explicit about which locations are official and discourage storing key files only on local drives or email.

Confirm the named pre-construction lead (if separate) and the project manager who will carry the job into execution. Ensure their names are recorded in the project record and visible to the team.

Based on the action log and handoff discussions, outline the top priorities for pre-construction, such as Contract Review, Budget Finalization, early Schedule Development, and Permitting Process steps.

Create a short, high-level roadmap showing key pre-con milestones (for example, “contract executed,” “early sub selections,” “permit submitted,” “client precon meeting”). Include rough target dates.

Prepare a concise email summarizing the handoff outcomes: who owns the project, key risks, immediate priorities, and where documents are stored. Send it to all relevant internal stakeholders.

Change the project’s status from “Bid/Award” or similar to “Pre-Construction – Active” in your CRM or project tracking tools. This signals to the wider organization that pre-construction work is underway.

Set a date for the first formal pre-construction checkpoint meeting (for example, in 2–4 weeks) to review progress on Contract Review, Project Setup, Budget Finalization, and Schedule Development.