How to use the Outline Specification
Define the specification purpose, regional terminology, procurement stage and who owns each technical decision before drafting clauses.
The workspace starts blank. Load example temporarily fills the controls with demonstration data; reload or use the tool’s New or reset action, where provided, before entering live information.
- Choose the Regional terminology and create only the work sections needed, giving each a Section code, title and Scope / coordination intent.
- Add clauses with a clear title and requirement, then record Responsibility / design ownership and a Draft, For review, Coordinated or Superseded status.
- Use Source / version / authority for the technical basis and link the affected schedule, drawing, detail, product or decision.
- Complete issue status, date, preparer, reviewer and project reference; resolve placeholders and broken cross-references before producing the PDF.
Worked examples
These examples explain the set-up, expected output and review needed without changing the tool workspace.
Early masonry section
- Set-up
- Create a masonry section covering appearance, sample approval, workmanship and evidence, with unresolved product selection assigned to an owner.
- Result
- The issue shows which clauses are usable for coordination and which remain Draft or For review.
- Review
- Confirm performance wording and responsibility with the structural, fire, conservation and procurement information that applies.
Room-finish coordination
- Set-up
- Link floor and wall finish clauses to the room-finish schedule and material-board references.
- Result
- A reviewer can move from each finish requirement to the location and current selection without duplicating the full schedule.
- Review
- Check that product substitutions update both the selection record and the affected specification clause.
Suggested workflow
Place the tool in a controlled project or practice process rather than treating its output as an isolated verdict.
- Agree the specification structure and responsibility matrix before writing product-level requirements.
- Draft clauses from verified sources and expose unresolved decisions through status and ownership.
- Coordinate the issue against drawings and schedules, record the reviewer, then freeze the issued PDF and editable record together.
Check before saving or issuing
- Every requirement has an identifiable source or project decision and a responsible reviewer.
- Draft language, placeholders and unresolved selections remain visible rather than reading like approved requirements.
- Drawing, schedule and detail references point to the same issue being reviewed.
Common problems
- Clause is descriptive but not actionable: state the required outcome, evidence and responsible party.
- Conflicting information persists: nominate one controlled source and cross-reference it instead of repeating values.
- A product name has become a silent specification: record equivalence, performance and procurement constraints explicitly.
Output
A structured outline specification and decision list with a PDF issue output.
Professional boundary
Every clause requires project-specific technical, legal and procurement review before use in contract or construction information.