Trust centre
Technical review policy
Technical review adds a subject-matter check when website content could influence engineering, construction, safety or authority-coordination decisions.
Content record
Last reviewed 23 July 2026
English-language public information
Policy principles
Risk-based review
The depth of review should match the technical, regulatory and safety consequences of the topic.
Roles stay distinct
Editorial review improves communication; technical review checks subject matter; neither replaces a project appointment.
Limitations stay visible
Review does not turn general website material into drawings, calculations, approvals or site instructions.
When technical review is expected
- The page explains engineering principles, construction sequencing, installation methods or material selection.
- The content discusses health and safety, fire and life safety, utilities, structural work or inspection readiness.
- The content summarizes authority, landlord or master-developer processes that can change by jurisdiction or project.
- A reader could reasonably mistake general guidance for a project instruction without an explicit limitation.
What a technical reviewer checks
- Whether the stated scope, terminology and sequence are technically coherent.
- Whether important assumptions, interfaces and project variables are visible.
- Whether claims about standards or authority processes need a current primary source.
- Whether the content could encourage unsafe work, premature procurement or action without required approvals.
- Whether a consultant, authority, specialist contractor or manufacturer must make the project-specific determination.
Editorial review is not technical approval
Editorial review checks structure, clarity, sourcing, consistency and readability. Technical review considers the subject matter within the stated scope of the page.
Neither review is a signed design, engineering calculation, method statement, risk assessment, permit, no-objection certificate, inspection approval or instruction for a particular site.
Reviewer identification
A formal technical-review label should be published only after the review has occurred. The label should state the reviewer role, review date and scope of the review without inventing qualifications or authority.
Named reviewers, professional credentials and registration identifiers are published only after verification. Management verification required before publication.
Project-specific professional advice
Readers must use the appointed and appropriately qualified project professionals for design, calculations, code interpretation, authority submissions, safety planning and site instructions.
Where an authority, consultant, contract document or approved drawing differs from this website, the project-specific controlling information takes precedence.