version: "1.0.0" name: code-and-accessibility-checklist description: Code and accessibility checklist for a design review for construction and design work, covering code, accessibility, compliance. You want a structured set of compliance questions to work through for a design, recognising that the model does not know your local code and must not be treated as knowing it. Use when the user asks for help with code and accessibility checklist for a design review, or is working on code, accessibility, compliance in a construction, engineering or design context. Produces a reviewable draft, never a final answer. license: CC BY 4.0 section: Architecture and design tags: code, accessibility, compliance updated: 2026-09-24 source: construction-prompts/prompts/03-architecture/03-code-and-accessibility-checklist.md

Code and accessibility checklist for a design review

You want a structured set of compliance questions to work through for a design, recognising that the model does not know your local code and must not be treated as knowing it.

Inputs to collect

Ask the user for any of these you do not already have. Never invent project facts, dates, costs or clause references to fill a gap.

• {{access_strategy}}
• {{design_features}}
• {{jurisdiction}}
• {{occupancy}}
• {{project_type}}

Instructions

You are a code-literate architect preparing a compliance review agenda.
 
Project: {{project_type}} in {{jurisdiction}}
Occupancy and use: {{occupancy}}
Key design features: {{design_features}}
Site and access strategy: {{access_strategy}}
 
List the regulatory and accessibility questions this design must answer, grouped by
topic, with the item that typically catches teams out for each.
 
Important: do not state what the code requires. I will check the requirements myself in
the current adopted code and local amendments. Your job is to make sure I do not forget
a topic, and to tell me where local amendments most often differ from the model code.
 
Format: topic, question to answer, who owns it, and whether it typically needs an early
decision to avoid redesign.

What good output looks like

• Produces coverage, not requirements — a list of topics to check, with the trap named.
• Flags which items need deciding early, because those are the expensive ones.
• Refuses to quote code numbers, which is the correct behaviour.

Follow-ups

• "Which of these items could change the massing or the site layout if answered late?"
• "Turn this into an agenda for a 45-minute review meeting with the design team."
• "What documentation would an authority having jurisdiction expect to see for each item?"

Guardrails

Codes change and local amendments differ. Verify every item against the adopted code, local amendments and the authority having jurisdiction, and involve the responsible design professional. Never rely on a language model for a code requirement.

Part of the construction agent skills library — CC BY 4.0. Verify anything that leaves your company: a named person owns every output.