The preliminaries are the part of the specification that governs the project rather than the building. They describe the parties, the contract, the site, and the general obligations the contractor takes on to deliver the work. In the NBS structure they sit in the A group, ahead of the technical work sections, and under Uniclass 2015 they map across to the project and management tables rather than the product or system tables.
Think of the technical sections as describing what gets built. The prelims describe how the job is run. They cover possession and access, the programme, insurances, supervision, quality control regimes, working hours, and the cost items a contractor needs to price but which don't belong to any single trade. None of that is glamorous. All of it decides how the project behaves when something goes wrong.
The danger with preliminary clauses is that they look harmless. They read like standard text, so they get reused without much thought, and the risk hides in the gaps between what they say and what the contract says. A prelim that restates a JCT clause slightly wrong doesn't just create confusion. It can amend the contract by accident, and now you're defending a position you never meant to take.
The same problem shows up in omissions. If your prelims don't set out how samples and benchmarks are approved, the contractor decides. If they're silent on the standard of making good after the CDM principal contractor hands back, that argument lands on your desk at practical completion. Silence in a specification is never neutral. It transfers the decision to whoever has the commercial incentive to read it in their own favour.
Then there's duplication. When the prelims, the contract particulars, and the technical sections all say something about the programme, and they don't quite agree, you've built a contradiction into the tender documents. Contractors find these. Their quantity surveyors are paid to find these. A senior architect who has sat through one loss-and-expense claim knows exactly how a single inconsistent clause turns into months of correspondence.
The contract is the spine of the project. The preliminaries should support it, not rewrite it. The most common failure in specification preliminaries is treating the prelims as a place to restate contract terms, which means any drafting slip becomes a live conflict between two documents that are meant to work together.
The cleaner approach is to reference rather than repeat. Where the JCT or NEC form already deals with insurances, liquidated damages, or extensions of time, point to it and add only the project-specific detail it needs. State the contract type and edition clearly. Set out the order of precedence so that if two documents disagree, everyone already knows which one wins. Define your provisional sums and contingencies precisely, because a vague provisional sum is an invitation to a claim. The goal is a set of preliminary clauses that a contract administrator can hold up next to the building contract and find no daylight between them.
Good prelims are specific where it counts. Possession and access should say when the contractor gets the site, in what condition, and what constraints apply, whether that's a live campus, a party wall, or restricted delivery windows in a city centre. The programme clause should state the key dates and the obligations around updating and reporting, not just gesture at a completion date.
Insurances and indemnities deserve the same precision. The prelims should state who insures the works, to what value, and against what, and they must match the contract particulars exactly rather than approximately. A mismatch between a prelim clause and the JCT insurance options is the sort of thing nobody notices until there's a fire and two parties point at each other. Set the professional indemnity and public liability requirements clearly, and say what evidence the contractor provides and when.
Quality control is where prelims earn their keep. Spell out the sample and benchmark process, who approves, and how long approval takes, so a delayed decision can't later be blamed on you. Set the supervision and inspection regime. Define working hours and any noise or environmental limits, especially on sensitive sites. Say what the defects liability period covers and how making good is agreed. Cover the CDM 2015 duties so the principal designer and principal contractor roles are unambiguous from day one. Each of these clauses is small. Together they decide whether the job runs on rails or on goodwill.
Start from a recognised structure rather than a blank page. The NBS prelims and the Uniclass classification exist precisely so that nothing important falls through the cracks, and a contractor pricing your job expects to see clauses in roughly the order they've seen on every other tender. Familiarity reduces error. It also reduces the questions you field during the tender period.
Then resist the copy-paste reflex. The prelims from your last project were written for a different site, a different contract, and a different client. Reusing them wholesale is how a clause about a Section 278 highways agreement ends up in the specification for a domestic extension. Read every clause against the job in front of you and delete what doesn't apply. A short, accurate set of preliminary clauses protects you better than a long one stuffed with irrelevant text that a contractor can mine for ambiguity.
Write in plain, enforceable language. A preliminary clause that says the contractor shall "endeavour to" do something has given away the obligation, because endeavour is not a duty a contract administrator can hold anyone to. Say what must happen, by when, and what follows if it doesn't. Vague verbs are where risk leaks out of a specification, and a senior architect reviewing prelims should be hunting for them the way they'd hunt for a missing fire rating in a door schedule.
Coordinate the prelims with the technical sections and the drawings before you issue. If the prelims promise a mock-up of the brickwork and the technical section is silent on it, that gap is yours. The same logic applied to coordinating drawings before BIM made it routine, and to checking schedules against the plan before software did it automatically. Consistency across documents is the whole game, and it's the part humans are worst at doing by hand across hundreds of pages.
Checking a full set of preliminaries against the contract, the technical sections, and the schedules is exactly the kind of slow, cross-referencing work that drains a senior architect's week. It's also the work that tools built for architectural specification are starting to handle properly. Avoice ingests a firm's existing documentation, including its prelims, technical sections, schedules, and historical projects, and turns them into structured data it can actually reason over rather than a pile of separate files.
That structure is what makes the difference. Because Avoice reads the prelims and the technical sections together, it can flag where a preliminary clause contradicts a work section or where the programme obligations in one document don't match another, before any of it reaches a contractor. It generates and classifies specification content under Uniclass, CAWS, and other recognised standards, so the output sits in the structure your team and your contractors already expect. And it grounds what it produces in your own historical documents, not a generic clause library, which means the prelims read like your practice wrote them.
None of this removes the architect's judgement, and it shouldn't. Deciding how much risk to carry on a given project is a professional decision, not a document-processing task. What platforms like Avoice change is the time between drafting a clause and knowing whether it conflicts with everything else you've issued. That feedback used to take a careful read-through and a good memory. Now it can happen as you write.
Run the same check every time. Do the preliminary clauses agree with the contract particulars on dates, insurances, and damages. Does the order of precedence resolve any conflict cleanly. Have you deleted every clause that belonged to the last job and not this one. Are the quality, sample, and approval regimes specific enough that nobody can claim the rules were unclear. Does anything in the prelims promise something the technical sections don't deliver.
The preliminaries are the first thing a contractor's commercial team reads closely and the last thing most architects want to spend an afternoon on. That imbalance is the opportunity. Tighten your prelims and you remove the cracks before anyone has a reason to look for them. If you want to see how this works against a real set of documents, Avoice offers demos tailored to how your practice already writes. The clauses that protect you are the ones you got right while the project was still on paper.
