CPD session

Writing clear and proportionate specifications for small studios

A practical 45–60 minute CPD for architectural practices, designed to help you write clear, technically robust and proportionate specifications on small projects.

  • Focused and practicalGuidance, examples and template approaches tailored to small-scale work.
  • For architectural studiosRelevant to architects and technicians working on smaller projects.
  • With live examplesReal project examples and common challenges.
  • Includes an Oruma demoA short 10-minute overview of how Oruma supports specification writing.

Request a CPD Session

Complete the form below and we'll be in touch to arrange your CPD session.

Session details

Duration:
45–60 minutes (plus 10-minute demo)
Format:
Online or in person (subject to location)
Audience:
Architects and studio teams
Cost:
Free of charge

By submitting this form, you agree that we may use your details to arrange the CPD session and send relevant information. See our Privacy Policy.

02Oruma How

Tips for Proportionate Specification Writing on Small Projects

Small projects may have fewer documents, but they don't necessarily have fewer risks. Even a modest residential extension can involve complex decisions around waterproofing, insulation, fire safety, finishes and the coordination of specialist systems.

The challenge for smaller practices is finding the right balance: providing enough information to protect the design intent and communicate quality, without creating unnecessary documentation.

Here are six principles worth considering.

01/Principle

Choose the right level of specification

Not every project requires a comprehensive specification document.

For straightforward, low-risk work, clear drawing notes may be sufficient. Where more detailed product, performance or workmanship requirements are needed, a short-form specification can provide a useful middle ground.

For technically complex work, competitive tenders or projects requiring greater contractual control, a fuller specification may be appropriate.

The objective is to use the lightest level of documentation that still provides adequate clarity and control.

02/Principle

Don't confuse Building Regulations compliance with specification

Building Regulations establish minimum statutory requirements. They don't necessarily define the quality, appearance or particular products a client expects.

A note requiring windows to comply with Building Regulations, for example, says relatively little about their appearance, finish, hardware, installation or acceptable substitutions.

These decisions should be communicated clearly, whether through drawings, schedules or a separate specification.

03/Principle

Use drawings, schedules and specifications together

Each document serves a different purpose.

Drawings are generally best for communicating location, geometry and construction details. Schedules organise repeated information such as door types, sizes and finishes. Specifications define product requirements, performance and workmanship.

The aim isn't to duplicate information across all three, but to make sure each requirement is recorded somewhere appropriate and remains coordinated.

04/Principle

Write requirements that can be checked

Terms such as "high quality", "suitable" or "to the architect's approval" are open to interpretation.

Where possible, requirements should identify the intended product or technical characteristics, measurable performance criteria and any relevant testing or certification.

And remember that specifying the correct product is only half the job. Requirements for substrate preparation, installation, tolerances and protection can be just as important to the finished result.

05/Principle

Be clear about specialist design responsibilities

One common gap on smaller projects is the extent of contractor-designed work, particularly for building services.

An architect may reasonably rely on a specialist to design an air source heat pump or heating distribution system. However, the client and design team may already have requirements for performance, equipment locations, appearance and sustainability.

These requirements need to be established before the specialist starts designing.

A specification should clarify what the contractor is expected to design, the constraints that apply, and how compliance will be demonstrated. Design responsibilities should also align with the project appointments and building contract.

06/Principle

Coordinate before issuing for tender

Even a well-written specification can create problems if it contradicts the drawings or schedules.

Before issuing, check that all work packages are covered, product selections are consistent, contractor design responsibilities are clear and substitutions are properly controlled.

A relatively short coordination exercise can prevent significant uncertainty during pricing and construction.

A final thought

A proportionate specification isn't simply a shorter specification. It's one that focuses on the decisions that matter: what is being provided, the quality expected, who is responsible and how the finished work will be assessed.

The goal isn't more paperwork. It's fewer assumptions, more consistent pricing and a clearer understanding of what the client is purchasing.