- Project plans
- Project activities
- Legislation and standards
- Industry context
Last edited 19 Sep 2018
Specification guidance for construction
When writing architectural specifications getting the basics in place from the start will help you build a document suitable to your needs. Listed below are some basic rules to follow when writing your next specification:
- Always start from a solid baseline document. Do not take the last project you prepared a specification for and change the headers and footers. No matter how vigilant you are, mistakes such as naming the wrong project, specifying incorrect materials and other basic errors will creep into your documents.
- Avoid using the term 'or similar approved' in a specification. If you approve it you are assuming liability for it. Instead use the term ‘or acceptable equivalent’. By accepting an alternative the responsibility for Fitness for Purpose moves to the contractor and the architect's acceptance is for design intent only. If the architect approves, they take back that responsibility. Normally, alternatives are offered for program or cost reasons and the contractor is responsible for the fact that they are providing a different product that must be at least as good quality-wise as the one specified by the architect. If the architect is specifying by description only, the contractor is obliged to provide the technical solution which again they have to be responsible for in terms of quality, performance, appearance and fitness for purpose.
- Document/section identification should appear on every page in the footer for document control purposes.
- Avoid putting specification clause numbers on your drawings. The use of product reference codes is recommended which should all be included on a technical reference sheet (T-Sheet) that links the drawings and the specification. This makes life much easier when changes are required.
- Avoid mixing prescriptive and performance specifications, that is, don’t name a very specific product and then provide performance characteristics for that product – this is not necessary and creates the potential for conflict resulting in claims.
- Avoid specifying temporary works – this is the contractor’s responsibility. Just specify the need to protect adequately, not how to do it.
- Remove unfinished clauses and terms such as 'if required'. If you are specifying a specific technical solution then you have to specify everything.
- Do not highlight particular clauses by using bold or underlining, as this indicates that the clause is of special importance and there is no such thing in a specification, as by default it indicates that everything else is not so important.
- Always allow time to have your specifications proof-read.
 Related articles on Designing Buildings Wiki
- Building information modelling.
- Bill of quantities.
- Common Arrangement of Work Sections (CAWS).
- Comparison of SMM7 with NRM2.
- Construction contract.
- Insulation specification.
- New Rules of Measurement (NRM)
- Output-based specification.
- Outline specification.
- Performance specification.
- Prescriptive specification.
- Standard Method of Measurement (SMM7).
- Tender documentation.
- Temporary works.
- What should be included in a scope of work?
Featured articles and news
Delivering an infrastructure revolution.
The admissibility of evidence.
How many can you name? 37 anyone?
CIOB respond to the points-based system.
When is the weather considered 'exceptionally adverse'?
ECA backs call for a rolling programme of rail electrification.
What does 'curtilage' mean and why does it matter?
Our duty to prevent harm and protect each other.
A quality perspective.
If buildings were people, they would be just starting to walk on two legs.
Air filtration and clean air standards.