A construction permit checklist is not a universal shopping list. Its contents depend on the site, proposed work, building use, approval route and responsible authority. Digital tools make it easier to collect guidance, but they can also combine incompatible sources into one confident-looking answer. Start with a short scope record that a reviewer can inspect without opening an AI conversation.
Record the project address, the applicant’s reference, a plain-language description of the work and any known constraints. Distinguish confirmed facts from assumptions. “Existing commercial use confirmed by owner” and “lawful use confirmed by authority” are different statements. The ledger should preserve that difference instead of turning both into an unchecked project fact.
Separate the approval routes
Planning permission and building regulation approval are not interchangeable. Other permissions may involve heritage, highways, drainage, fire safety or environmental matters. Do not assume that receiving one decision settles another route. In England, the Planning Portal explains planning and building control as separate areas; the GOV.UK building regulations guidance provides a useful starting point for the latter. Read the relevant local authority’s current instructions alongside these general resources.
Germany provides a different context. The Musterbauordnung, published through the Bauministerkonferenz, is a model framework, not a substitute for the applicable state building code. A project in Berlin needs attention to Berlin’s own building regulations and administrative process. A project in Hannover requires the relevant Lower Saxony framework and local authority instructions. Geography is therefore a field in the register, not a detail to add at the end.
Make every source retrievable
For each candidate requirement, save the issuing body, document title, URL, section or page, publication or revision date where available, and your access date. If a source has no visible revision date, record that limitation. Retain a permitted copy or screenshot where useful, while recognising that a saved copy does not establish that the guidance remains current.
| Scope field | What to record | Why it matters |
|---|---|---|
| Responsible body | Authority and department | Prevents an unrelated checklist becoming the baseline |
| Approval route | Confirmed route or open question | Separates parallel obligations |
| Requirement source | Title, section, URL and access date | Makes extraction auditable |
| Applicability | Confirmed, conditional or unresolved | Keeps assumptions visible |
Use a stable requirement identifier even if the source later changes. The identifier belongs to your record; the source edition is an attribute of that record. This distinction lets a coordinator identify which documents and checks need revisiting when an authority updates an application form or guidance note.
Use AI for extraction, not jurisdiction selection
A useful prompt asks a tool to extract explicit document requests from supplied guidance, preserve the wording, identify the source location and flag uncertainty. Ask it to distinguish mandatory language from examples and recommendations. Do not ask it to invent a complete local checklist from a project description alone. Search results, summaries and model memory are not equivalent to the authority’s current instructions.
Review every extracted entry against the original. Watch for omitted conditions, such as a report being required only for particular work or circumstances. Also watch for silent scope expansion: a tool may import a familiar requirement from a different country. New York City’s Department of Buildings and Singapore’s Building and Construction Authority provide useful examples of distinct administrative systems; neither is evidence of what a German or English authority requires.
Keep authority questions out of the “missing” pile
If the relevant route is unclear, create an authority-specific question with an owner and a target response date. Do not label a report missing when you have not established whether it applies. Phrase the query narrowly: describe the work, identify the source passage and ask which requirement or evidence route applies. Avoid requesting a general assurance that the whole scheme is compliant.
When an answer arrives, record who provided it, when, through which channel and for which project facts. Preserve qualifications and attachments. An informal discussion may be useful without replacing a formal decision. If the design changes, reopen the question rather than assuming the earlier response covers the new scope.
The handover from scope to inventory is a controlled baseline: a source-backed list of applicable requirements, conditional items and unresolved questions. It is not an approval prediction. Once that baseline is understandable, the team can assign documents and evidence without losing sight of why each item exists.