From award letter to mobilisation in days, not weeks.
Every document, every subcontractor, every programme — structured and issued.
The Pre-Con Pack
- Workflow
- Templates
- Evidence
- Approvals
- Audit log
Win on Tuesday. Mobilise by Friday.
- Methodology pack templatedrafting
- Programme template (P3-aligned)drafting
- Sub-let strategy registerdrafting
- Risk register (project-specific)drafting
- Mobilisation checklistdrafting
30-second walk-through
Watch The Pre-Con Pack run on a real engagement.
Recorded inside the BuiltAI app against a redacted client dataset. Same QA gates, same evidence pattern, same approval rhythm you'll get on day one.
Walk-through landing soon
We're recording the The Pre-Con Packwalk-through against a redacted pilot dataset. Drop us a note if you'd like an early preview.
What gets installed
Productised workflow components
Each item below is delivered as a templated, governed workflow piece - not a bespoke build. Same QA gates apply regardless of which pack you start with.
What we need from you
To run a useful audit and deploy this pack
We don't need everything up-front - but the more of the below we can see early, the sharper the diagnostic and the faster the workflow lands.
- Two recent pre-construction packages (one straightforward, one complex)
- Your current programme template and risk-register format
- List of pre-con leads / project managers who will use the workflow
- One representative live pre-con engagement to use as the deployment pilot
- Standard sub-contractor / supplier list (Amber-classified)
The pattern
What this pack solves and how it lands
Problem
Pre-construction sits between bid award and site mobilisation — a phase where decisions accelerate, but document discipline often slips because the team is rebuilding methodology, programmes and risk registers from scratch under pressure.
Commercial impact
Late or inconsistent pre-con packs create downstream cost — sub-let gaps, programme rework, risk-register drift, and the kind of scope ambiguity that triggers variations months into delivery.
Success criteria
Pre-con package issued within 5 working days of award. Methodology, programme and risk register signed off by competent reviewer. Sub-let strategy traceable to the as-priced bid.
Governance controls
Methodology QA gate, programme QA gate, risk-register evidence index, client approval log, and professional boundary wording on competent-reviewer sign-off.
Outcomes
What "done" tends to look like
Every figure below carries a disclosure label per BuiltAI's governance approach. Actual findings depend on contract value, data quality and commercial-process maturity.
5days
From award letter to issued pre-construction package
−60%
Time spent on pre-con doc admin once pack is live
100%
Mobilisation handovers signed off by competent reviewer
Sits alongside
BuiltAI runs alongside the systems your team already uses - it does not replace them. This pack is built to fit:
- Microsoft 365 (Word, SharePoint)
- Google Workspace
- Asta Powerproject / MS Project
- Procore / Aconex
- Existing methodology + programme templates
A BuiltAI output, in five seconds
What this pack actually returns.
Every BuiltAI output is scoped to a pack and traced to a source. That's what makes it a governed output, not just an LLM call.
Award letter — 5-day mobilisation window
Award letter received Tuesday 09:00 for £4.2m Cat-A fit-out. Client expects mobilisation pack by Friday 17:00: methodology, P3-aligned programme, sub-let strategy, project-specific risk register, and kickoff agenda for Monday's site walkdown.
BuiltAI output
Pre-con package issued Friday 14:30 — methodology pack drawn from bidroom scope skeleton + tender library §fit-out. Programme template populated against critical-path milestones from tender programme. Sub-let strategy logged with traceability to as-priced bid. Risk register surfaces 7 project-specific items above Amber threshold. Kickoff agenda + competent-reviewer sign-off recorded.
Governed by: The Pre-Con Pack™ v1 - methodology + programme QA gates
Cited from: Tender pack §scope skeleton + bidroom assumptions register + project-specific risk matrix
We used to lose the first ten days of every project rebuilding the methodology pack. Now the bid library hands the pre-con team a structured starter — they spend that time on the things that actually need judgement.
Common questions
Buyer FAQs about The Pre-Con Pack
Does this replace our project managers' judgement?
No. Pre-Con structures the document workflow — the methodology, programme template, risk register and sub-let strategy. Your project managers and pre-con leads make the calls; the pack ensures those calls land in the right place, traceable to bid and signed off by a competent reviewer.
How does it integrate with our programme tool (Asta / P6 / MS Project)?
Pre-Con's programme template is tool-agnostic at the structure level — it defines the activity breakdown and dependencies. Your existing programme tool consumes that structure; we don't replace the scheduling tool, we replace the bespoke template every PM rebuilds from scratch.
Is this only for main contractors?
No. The Pack is used by Tier-1 / Tier-2 main contractors and by larger M&E sub-contractors with their own pre-construction phase. The methodology template adapts; the discipline (5-day issue, competent-reviewer sign-off) holds.
How it works
Where this pack sits in the engagement model
Step 1 - Discovery
Operational Intelligence Audit™ - fixed-scope, four-week engagement with QA2 sign-off.
Step 2 - Deploy
Controlled workflow deployment - AI-assisted, QA-gated, client-approved before issue.
Step 3 - Embed
Ongoing governance rhythm - monthly board reports, RAG reviews, continuous improvement.
Deployed in Step 2 - typically alongside Bidroom so the bid library and pre-con package share the same scope skeleton.
Adjacent workflows
Pairs well with this pack
Pre-Con uses the scope discipline Bidroom established at tender stage and hands clean methodology + programme into Commercial Control once site mobilises.
Long-form on this topic
Read deeper into tender quality.
Frameworks and checklists from the audit playbook - same discipline that the The Pre-Con Pack workflow installs.
Tender quality
Clarifications discipline - what separates a 70% bid from a 90% bid
Clarifications are the single highest-leverage pre-submission lever. A short, evidenced, deadline-respecting clarifications register turns ambiguity into scoreable answers - and exposes the gaps your competition will leave open.
7 min readTender quality
Bidroom - the Requirements Traceability Matrix that wins tenders
A bid is a compliance argument first and a sales pitch second. The Requirements Traceability Matrix is how you prove every ITT requirement is met, evidenced and signed off - before the technical lead reads page two.
8 min readTender quality
Clarifications discipline - winning more by writing fewer
Clarifications are not free hits. A disciplined RTM, a single clarifications log and an evidence-backed bid are the difference between credible and cluttered.
4 min read
Engagement modes
The Pre-Con Pack sits inside one of three engagement modes.
Indicative ranges - confirmed in the SOW after the discovery call. Full pricing breakdown.
Discovery audit
From a four-figure fixed fee
2 weeks · audit-only
- Most common
Pilot pack
From low five figures
6–10 weeks · The Pre-Con Pack
Governance retainer
From a four-figure monthly fee
Rolling · 3-month minimum
Ready to scope this pack against your real data?
Book a readiness call. We'll confirm whether this pack, an audit, or a different starting point fits your operation.