Give each window one ID and use it to link what is needed, what is offered, the supplier’s evidence and the final decision. This template keeps that record together across drawings, quotes and handover.
It does not calculate acoustic performance or approve a product. The project team must establish the requirements and review the evidence.
Set up the schedule
Create a record for each distinct opening or window type that needs its own specification. If several openings share a type, identify their locations and quantities without losing the ability to record an exception.
Keep Window IDs stable through revisions. Record the project, author, issue date and revision at the top of the schedule, and keep a change log when a requirement or proposal changes.
Keep what you need separate from what is offered
| Field group | Fields to complete |
|---|---|
| Identification | Window ID, location/elevation, room use, type and quantity |
| Requirement | Acoustic quantity, criterion, assessed scope, operating state, brief reference and requirement owner |
| Proposed system | Supplier, system revision, dimensions, opening configuration, glazing, frame, seals and ventilation |
| Evidence | Report/assessment reference, issuer, date, result notation, assessed item and applicability explanation |
| Interfaces | Detail reference, installation responsibility, exclusions and outstanding design questions |
| Decision | Review status, reviewer, decision date, conditions and accepted revision |
A blank evidence field means information is missing. It must not become a zero rating or an implied acceptance.
Check evidence for each window type
Compare the assessed and proposed assemblies. Record differences in dimensions, opening arrangement, components and operating state. Ask the supplier for the basis on which a result is considered applicable, and refer that basis to the appointed reviewer.
The test-report guide provides questions for this step. Do not combine a glass-only result and a complete-window requirement in an unlabelled “dB” column.
Use simple review stages
Choose a state such as Information required, Under review, Accepted with recorded conditions, or Not accepted. The responsible reviewer should define the meaning of acceptance for the project.
A record should retain the unresolved action, owner and date even where another part of the proposal has been accepted. Acceptance of a document is not confirmation of installation or project-wide compliance.
Handle a product swap
Add the alternative as a new proposed revision. Preserve the previously accepted construction, describe the differences and record the replacement evidence. Do not overwrite the accepted proposal before the change has been reviewed.
Carry the record through to handover
Reconcile the schedule with what was supplied and installed. Include accepted changes, inspection or verification references and the operating information relevant to the building team.
Download the editable schedule and use it with the specification checklist. For developer procurement, read planning to window procurement.
Discuss a bespoke system
Send a professional project brief to Hugo Carter. A partially completed schedule is useful when it clearly distinguishes issued requirements from unanswered questions.


