Every GC says the job was planned before bid day. Fewer can show you what was actually reviewed, by whom, and against which version of the plans. That gap between "we planned it" and "someone checked it" is where most preventable bid problems live.
Pre-construction planning, as this guide uses the term, is the work from the bid decision through subcontractor buyout. It covers the go/no-go call, plan review, takeoff, sub coverage, the priced estimate, and the handoff to the project team. Below is a five-gate workflow for that preconstruction phase, plus a reusable checklist and a backward-scheduled calendar you can adapt to your own bids.
Where Pre-Construction Planning Breaks Down on a Real Bid
Most failures aren't math errors. They're sequencing errors: the right person sees the right sheet too late. Here is a hypothetical to make the pattern concrete.
Hypothetical scenario (illustrative, not a documented project): You're bidding a mid-size office tenant improvement with a 10-working-day window. The estimator opens the plan set on day one, starts counting, and doesn't read the full set until day eight. An addendum on day six revised the ceiling spec, but the drywall and electrical sub packages went out on day three. After award, the electrical sub's exclusion of fire alarm devices surfaces, because nobody leveled the bids against each other's scope. The number was fine. The scope wasn't.
Nothing in that story requires bad estimating. It requires a calendar with no review points and a scope nobody compared line by line.
Planning that lives in one person's head
The first things lost are undocumented assumptions: site access, work hours, phasing, who handles temporary protection, which allowances you carried and why. The estimator knows them because they made the calls. Nobody else does.
When that estimator is out sick during peak bid season, or the job moves to a project manager after award, those assumptions vanish. The new person finds out the hard way, usually in a sub meeting or an RFI response. If an assumption isn't written where another person can read it, treat it as lost.
Why a gate-based approach fixes it
A gate is a go/no-go review point with a defined input and a defined output. You don't move to the next stage until the output exists and someone other than its author can check it.
That's the whole idea. A gate turns "I looked at it" into a document, a list, or a signed-off number. It also gives you a stop condition, so a problem found at gate two doesn't become a surprise at gate five.
The Pre-Construction Planning Process in Five Gates
This is a framework to adapt, not an industry standard. Firms name and order these stages differently, and your owners, lenders, and delivery methods will change the details. Struvia's scope in this workflow ends at buyout. Anything after handoff belongs to your project management and accounting tools.
| Gate | Inputs | Output | Who signs off | Stop condition |
|---|---|---|---|---|
| 1. Bid decision | Invitation, bid date, capacity, client history | Go/no-go note with reasons | Owner or lead estimator | Scope mismatch, no capacity, or an unrealistic bid date |
| 2. Plan and scope review | Full plan set, specs, addenda | Sheet index, missing-sheet list, scale check, takeoff setup | Estimator | Missing sheets or unresolved scale conflicts |
| 3. Sub bid coverage | Trade scopes, bid packages, sub list | Leveled bids with a gap and exclusion list | Estimator and PM | A major trade with no coverage or an open scope gap |
| 4. Estimate review | Priced estimate, quotes, price book, assumptions | Reviewed estimate with a change log | Someone other than the estimator | Quantities that don't trace to plans or unsupported unit prices |
| 5. Buyout handoff | Final estimate, selected subs, open items | Handoff package for the project team | PM and superintendent | Handoff without exclusions, open RFIs, or long-lead items |
How to adapt the gates to your job size
A small residential remodel with two or three trades can collapse gates 2 and 3. You read the plans, call your regular subs, and review the result in one sitting. The checklist still applies. You just run it faster.
A multi-trade commercial job needs all five, and some jobs need more. Public work might add a bonding and prequalification gate. A lender-financed project might add a draw schedule review before handoff. If an owner requires a mandatory pre-bid meeting or a specific submission format, build that into the calendar as its own gate rather than treating it as an interruption.
Gates 1 and 2: Bid Decision, Plan Review, and Takeoff Setup
These two gates decide whether you spend the next 80 hours well or waste them. Gate one costs minutes. Gate two costs a day or two. Skipping either is expensive.
The go/no-go screen before you open the plans
Answer these before anyone starts counting:
- Do you have estimator and sub-outreach capacity for the whole window, not just day one?
- Do you know this client's payment and change-order history?
- Does the scope fit what you build, in the region you build it?
- Is the bid date realistic for the size of the plan set and the number of trades?
- Do you have bonding, insurance, and prequalification requirements covered?
If two or more answers are shaky, pass. A no-bid on day one beats a rushed bid on day eight, and it protects the estimator's time for jobs you can actually win.
Plan set triage and where AI-assisted takeoff fits
Before you measure anything, sort and read the set. Check the sheet index against what you received, look for addenda, confirm the scale on every sheet you'll measure, and note where structural, civil, and architectural sheets disagree. Our guide to reading structural drawings covers that last part in detail.
Then run quantities. Struvia's AI-assisted takeoff works from uploaded plan PDFs and can turn a takeoff around in hours, not days.
The estimator still verifies. Matching totals don't prove every boundary or class is right, so you check that the slab edge, the room classes, and the scope boundaries match what you intend to bid. For the measurement fundamentals, see our construction takeoff guide.
Gate 3: Subcontractor Buyout Planning and Bid Leveling
Subcontractor buyout planning starts long before award. It starts when you decide how to package trades, because that decision controls how many scope gaps you'll find later. By the time sub prices are in, gate three is about making gaps visible while you can still fix them.
Building bid packages that don't invite exclusions
Define scope by trade, in writing. List what's included, what the GC provides, and where adjacent trades meet, such as who patches after electrical or who supplies blocking. Attach the specific sheets and spec sections for that trade, not the whole set with a "see plans" note.
Set an RFI cutoff date and state it in the package. Send packages the same day the scope is set, because every day of delay comes out of the sub's pricing window.
Leveling bids on scope, not just price
The lowest number is often the smallest scope. Bid leveling puts each sub's proposal on the same basis so you compare what's included, not just what's quoted. You normalize inclusions, list every exclusion and qualification, and flag the gaps where nobody is carrying a scope item.
Struvia's bid leveling normalizes scope across sub bids and flags gaps and exclusions, so a missing fire alarm device or an unpriced patch shows up before pricing locks. It also supports prequalification, insurance certificate tracking, and sub performance scorecards, which are being rolled out to more subs. Its sub search works by service area and checks licenses. It is not a pre-qualified network, so you still make the final call on who's right for the job.
Finding enough subs to level is its own problem, especially in a new market. Jayton, Estimating at Roylance Construction, said:
Once you pick a sub, lock the contract terms before award. Our guide to construction subcontracts covers the clauses worth settling first.
Gates 4 and 5: Estimate Review and Handoff to Buyout
Gate four is where preconstruction estimating gets a second set of eyes. Gate five is where everything the estimate assumed gets passed to the people who'll build it. Both are about making the work legible to someone new.
A second-set-of-eyes review procedure
The reviewer should be someone other than the estimator, and the sequence should be the same every time:
- Quantities to plans. Spot-check the largest and riskiest quantities against the sheets, not the estimator's notes.
- Units. Confirm every line uses consistent units, such as SF versus LF versus EA.
- Unit pricing source. For each major line, confirm whether it came from your price book, a supplier quote, or a sub bid, and that the source is current.
- Scope-gap list. Read the leveling output and confirm each gap is either priced, excluded on purpose, or assigned.
- Allowances and general conditions. Check that allowances are labeled and general conditions match the schedule length.
- Markups. Verify overhead, profit, bond, and contingency are applied once, in the right place.
Struvia prices estimates from your own company price book and can pull from your actual suppliers if you set that up. Each line traces to its basis. It delivers in your own Excel template with your formulas intact, and the Struvia team reviews estimates to make sure pricing is in the right place.
None of that replaces your judgment on site-specific risk. A tool can't know that the alley access is tight, the building is occupied, or the owner changes their mind. Your superintendent can. Send the reviewed estimate to the field before bid day, not after award.
What the handoff package should contain
At buyout, the project team inherits the estimate's assumptions. Give them a package that makes those assumptions explicit:
- The assumptions list: access, phasing, work hours, allowances, and temporary conditions
- Exclusions and clarifications, both yours and the ones carried in sub bids
- Open RFIs and the answers received so far
- Sub scope sheets for each trade, with the leveling notes
- Long-lead items and their lead times
Tracking actual costs afterward is a different job. Committed costs, actuals, and job-cost variance belong in job-costing and accounting tools. Struvia is not job-costing or WIP software, and preconstruction ends at buyout.
Pre-Construction Checklist and a Backward-Scheduled Calendar
This section is the part to copy. The checklist gives you pass/fail criteria per gate. The calendar shows how to count back from a bid due date so the review points actually fit.
The gate checklist
Paste this into your own template or Excel estimate file. Each item should be a clear pass or fail.
Gate 1: Bid decision
- Capacity confirmed for the full window (pass/fail)
- Client and scope fit reviewed (pass/fail)
- Bid date judged realistic (pass/fail)
Gate 2: Plan and scope review
- Sheet index matches received sheets; missing sheets listed (pass/fail)
- All addenda logged and reflected (pass/fail)
- Scale verified on every measured sheet (pass/fail)
Gate 3: Sub bid coverage
- Packages sent per trade with sheets, specs, and an RFI cutoff (pass/fail)
- Each major trade has at least the number of bids you require (pass/fail)
- Every exclusion and gap logged and assigned (pass/fail)
Gate 4: Estimate review
- Reviewer other than the estimator signed off (pass/fail)
- Each major line traces to a price source (pass/fail)
- Allowances, general conditions, and markups checked (pass/fail)
Gate 5: Handoff
- Assumptions, exclusions, open RFIs, sub scope sheets, and long-lead items delivered (pass/fail)
- Superintendent has reviewed the package (pass/fail)
A single fail means stop and resolve it before proceeding, or document why you accepted the risk.
Worked example: counting back from bid day (hypothetical)
Hypothetical assumptions: a mid-size commercial job, 10 working days from plan receipt to bid due, 2:00 pm on day 10. One estimator, one reviewer, and sub bids due at noon on day 7. These day counts are illustrative, not benchmarks.
| Day | Activity | Gate |
|---|---|---|
| 1 | Go/no-go (0.5 day), then plan triage | 1, 2 |
| 2 | Finish plan review, set up takeoff, send bid packages by end of day | 2, 3 |
| 3–6 | Takeoff and pricing of self-perform work; subs price; RFI cutoff end of day 4 | 3 |
| 7 | Sub bids due at noon; leveling starts in the afternoon | 3 |
| 8 | Finish leveling, close scope gaps, update estimate | 3, 4 |
| 9 | Independent estimate review | 4 |
| 10 | Buffer for late addenda; submit by noon | 4 |
The arithmetic: days 1–2 cover gates 1 and 2 (2 days). Days 3–6 cover the sub window and self-perform pricing (4 days). Day 7 is split between the sub deadline and leveling. Days 8, 9, and 10 are 1 day each for leveling completion, review, and buffer. That's 2 + 4 + 1 + 1 + 1 + 1 = 10 days.
The subs get five working days (days 3 through 7), and the RFI cutoff on day 4 leaves time for answers before they price. If you only have six days, compress by shortening the sub window and calling the major trades directly. Or pass.
This template is insufficient for complex or public work. Prevailing wage, bonding, mandatory pre-bid meetings, owner-specified forms, and phased addenda all add steps. Build those in as their own entries rather than squeezing them into the buffer day.
Tools for Each Gate Without Buying a Whole Suite
You don't need one platform for everything. Map each gate to a tool category and buy only what your team uses. If you're comparing platforms, our guide to AI-powered preconstruction software goes deeper on the software side.
- Takeoff (gate 2): Struvia, PlanSwift, STACK, and Bluebeam all handle takeoff or measurement in different ways. PlanSwift lists Essential at $2,000 per year for one seat and Core at $3,000 per year for one seat, per its pricing page checked 2026-10-14. STACK's official page distinguishes Premium takeoff from Pro worksheet estimating, and Bluebeam's features vary by tier, so verify the tier you need.
- Estimating (gate 4): Struvia turns the takeoff into a priced estimate in your own Excel template. Other tools do this inside their own formats.
- Bid management (gate 3): Struvia handles packages, outreach, and bid leveling. Procore's official page describes an annual quote based on selected products and Annual Construction Volume, and doesn't publish a rate card. Our Procore estimating pricing breakdown covers what that means for a GC.
- Project management (after gate 5): Procore and Buildertrend sit here. Buildertrend's pricing is a custom quote.
On cost structure, Struvia is billed on usage, with no seats and no monthly subscription. You can run a few real plan sets free once you confirm your email, and current rates are on the pricing page. Higher-volume teams can ask for a custom plan.
One contrast worth making plainly: Togal does quantity takeoff only. It has no cost database and exports quantities to Excel for you to price. Its Growth plan is $299 per user per month, billed yearly (see our Togal AI pricing breakdown), with custom pricing for teams of four or more. A per-seat takeoff tool stops at quantities. Struvia carries the job through to a priced estimate.
Frequently Asked Questions
What is pre-construction planning in construction?
Pre-construction planning is the work a contractor does between deciding to bid and handing the job to the project team. It includes the bid decision, plan review, takeoff, subcontractor coverage, the priced estimate, and its review. The goal is to make the scope, price, and assumptions clear before anyone commits.
What are the main stages of the preconstruction phase?
This guide uses five gates: bid decision, plan and scope review, sub bid coverage, estimate review, and buyout handoff. Firms name and order stages differently, and owner or lender requirements can add more. Treat the gates as a starting framework and adapt them.
How long should pre-construction planning take?
It depends on job size, bid date, and delivery method. A small remodel might take a day or two, while a multi-trade commercial bid can use every day of a two-week window. Use the backward-scheduled calendar above and adjust the day counts to your own jobs rather than relying on a universal number.
Who is responsible for pre-construction planning on a GC team?
The estimator usually leads, with a project manager owning sub coverage and handoff. The superintendent's input matters most before bid day, when a field review can catch access, phasing, and sequencing problems the plans don't show. A reviewer other than the estimator should sign off on the estimate.
What should be in a pre-construction checklist?
At minimum: a go/no-go note, a sheet index with addenda logged, a scale check, bid packages with an RFI cutoff, a leveled bid comparison with gaps listed, an independent estimate review, and a handoff package. The gate checklist above gives pass/fail criteria for each.
Where does preconstruction end and project management begin?
Preconstruction ends at buyout and handoff, when the project team takes over the assumptions, exclusions, and selected subs. After that, tracking actual costs, committed costs, and variances sits in job-costing and accounting systems, not in preconstruction software.
Make Pre-Construction Planning Reviewable
Gates make pre-construction planning something a second person can check. Each stage ends with a document, a list, or a signed-off number, so a sick day or a job transfer doesn't erase the work. Start with the checklist and the calendar, and adjust them until they fit how your team bids.
To run your next bid through these gates, try Struvia free on your next plan set, or book a demo to walk through takeoff, priced estimates in your own Excel template, and sub bid leveling.
*Reviewed by Baylor Jeppsen, Construction Estimating Expert and Founder of Struvia.*
