A Myrmex PCSA is structured around six zones: Scope, Technical, Governance, Financial, Programme, and Actions. Each zone closes a different category of question that has to be answered before the main construction contract can be signed. The six zones run in parallel over four weeks and produce a defined set of deliverables. The fee is 2.5–3% of project value, fixed at the outset.
The architect sends drawings. The contractor reads them. Trade quotes come back from a few subcontractors. Someone writes a cost plan. Someone else maintains a separate risk list. The client signs a contract that is a composite of all of these inputs. None of the inputs reference each other formally. The cost plan does not name the risks. The risk list does not reference the programme. The programme does not confirm buildability. The pre-construction phase happened. What it produced is less clear. The drawings were read, the quotes were collected, the documents were assembled. Whether any of those activities resolved the questions the main contract needs answered is a different matter.
What a structured Pre-Construction Services Agreement closes down
An unstructured pre-construction phase typically leaves six categories of question open. The first is scope ambiguity: what is included in the contract price and what is not. The second is design buildability: whether the design as drawn can be built as drawn, and where it cannot, what changes. The third is decision authority: who signs off on what, through what channel, and at what point in the sequence. The fourth is cost predictability: whether the cost plan reflects what the project will actually cost once trades are engaged and quantities are measured. The fifth is programme dependencies: which trades depend on which, where the critical path runs, and what happens to the sequence when one trade slips. The sixth is the open list of items still to resolve: the questions, gaps, and unconfirmed details that have not yet been closed but will need to be closed before the main contract can be signed on known terms.
Each of these categories is a failure mode. A contract signed with scope ambiguity produces variations. A contract signed without a buildability review produces site problems that become programme delays. A contract signed without a decision authority map produces confusion when a change needs approving and nobody knows who approves it. The categories are not theoretical. They are the six ways a project drifts after the main contract is signed.
The six zones
Scope is first because every other zone depends on what is in scope. The Scope zone produces a written scope statement and a written exclusions list. Until both exist, the cost plan is pricing an assumption, the programme is sequencing a guess, and the risk register is cataloguing unknowns against an undefined baseline.
Technical runs once Scope has locked. The Technical zone is the contractor’s assessment of how the design will be built: where the design creates construction risk, where coordination between trades is required, and where the design needs resolving before the main contract is signed. It produces a buildability review and a design coordination report.
Governance is set early and runs throughout. The Governance zone defines the contract structure, the change control protocol, and the decision authority map. It answers the question the other zones do not address: when a decision is needed during the build, who makes it, through what process, and what documentation records it.
Financial runs alongside Technical because the cost plan and the buildability review feed each other. The Financial zone produces the cost plan and the contingency framework. The cost plan is built from measured quantities priced against trade returns. The contingency framework names what the contingency covers and what it does not. A contingency that covers everything covers nothing. The Financial zone makes the contingency specific.
Programme assembles from Technical and Financial. The Programme zone produces the construction sequence with gated milestones. The sequence is not a bar chart drawn from experience. It is the logical output of the Technical zone’s buildability findings and the Financial zone’s trade engagement timeline. If the Technical zone identified a coordination dependency between structural steel and mechanical services, the Programme zone sequences them accordingly.
Actions is last because it is the running list across all four weeks. The Actions zone captures every open item surfaced by the other five zones that has not yet been closed. It is the list of questions, gaps, pending confirmations, and unresolved details. The Actions list is closed before the main contract is signed. Any item still open at that point is either resolved or explicitly excluded from the contract scope.
How the zones run in parallel
The zones are not sequential. They run in parallel across four weeks, with dependencies between them shaping the sequence in which each zone completes its work.
Scope locks down in week one. It has to. The Technical zone cannot assess buildability against an undefined scope, and the Financial zone cannot price a project whose inclusions and exclusions are still moving. Governance is set early. The decision authority map and the change control protocol are established in the first days and run throughout the PCSA period.
Technical and Financial run together through weeks one to three. The design coordination findings feed into the cost plan. The cost plan tests the buildability assumptions against real trade prices. If the Technical zone identifies a construction risk, the Financial zone prices the mitigation. If the Financial zone receives a trade return that exceeds the allowance, the Technical zone revisits the design assumption.
Programme assembles in week four from the outputs of Technical and Financial. The construction sequence cannot be finalised until the buildability review is complete and the trade engagement timeline is known. The pre-contract documentation handover follows in the same week. Actions runs across all four weeks, accumulating open items as the other zones surface them and closing items as they are resolved.
The structure is the point. Pre-construction is not a phase that happens and then ends. It is a set of conversations that produce a contract. Without the structure, the conversations happen informally: over email, in site meetings, between phone calls. The contract is signed before the conversations finish. The questions that were not asked become the variations that follow.
What each zone produces by the end of the PCSA
The deliverables are specific. Scope produces the written scope statement and exclusions. Technical produces the buildability review and the design coordination report. Governance produces the contract structure, the change control protocol, and the decision authority map. Financial produces the cost plan and the contingency framework. Programme produces the construction sequence with gated milestones. Actions produces the open-items list, closed before signing.
The set of these deliverables is the pre-contract documentation handover. It is the package the client signs when they commit to Stage 2. The contract, the specification, the drawings schedule, the programme, the cost plan, and the terms under which variations will be managed. All of it assembled from the outputs of the six zones, all of it produced through a named process rather than assembled from informal conversations.
Each deliverable is tied to a payment milestone. The contractor earns each stage payment by producing the deliverable, not by reaching a date on the calendar. If the deliverable is late, the payment is late. The incentive structure matches the output structure.
Why this structure exists
The six-zone structure exists because Myrmex was built specifically to fix the gap between a quote and the actual cost of the work. That gap is not closed by working harder during pre-construction. It is not closed by hiring better people. It is closed by structuring the pre-construction conversations into named zones with named deliverables, so that each category of question has a named owner, a named output, and a named deadline.
The gap between a quote and the actual cost of a residential renovation is not a pricing failure. It is a sequencing failure. The contract is signed before the conversations that price the project have finished. The PCSA is the instrument that finishes those conversations before the contract is signed. The six zones are the structure that makes the conversations finishable in four weeks.
Myrmex is not exempt from the failure mode the structure exists to fix. The firm was built by two people who ran a different construction company for two years and watched that gap shape project after project. The structure is not a claim that the gap no longer exists. It is the mechanism that makes the gap closable. The broader procurement context covers where the PCSA sits inside the two-stage tender process. The fee structure covers what the 2.5–3% fee funds and how payment stages against deliverables.