Writing Clear, Evidence-Based Deficiency Notices

Executive summary

Deficiency notices carry the department’s reasoning to the applicant. When they state only a conclusion, the applicant guesses, responds partially, and a second cycle follows.

A well-formed notice contains four elements: the requirement with its edition, the evidence observed, the precise location, and the action that would resolve it. This structure also happens to be what makes a notice defensible.

Why notice quality drives cycle count

Each cycle is measured in weeks of elapsed time. The difference between a one-cycle and a three-cycle resolution is usually not the complexity of the issue but the specificity of the first notice.

There is a governance dimension as well. Where automated support contributes to findings, public-sector guidance expects the reasons for a decision to be available and understandable to the person affected [1][2].

The four-part notice

Language that holds up

• State observations, not motives. "The submitted plan does not show …" rather than "you failed to …".
• Say which items are administrative and which are technical; applicants prioritise differently.
• Where interpretation is involved, say so and cite the interpretation being applied.
• Never imply that resolving the listed items guarantees approval; other findings may follow from the revision.
• Use status labels with words and icons, not colour alone, so the notice remains readable for everyone [3].

Implications for authorities having jurisdiction

Maintain a deficiency library: standard wording per recurring requirement, with placeholders for evidence and location. It raises consistency between reviewers and shortens writing time, and it becomes the deficiency taxonomy used for prevention analysis.

Consolidate notices across departments before sending. Two separate notices on the same element invite a partial response.

Implications for applicants and professionals

Respond item by item using the department’s numbering, state what changed and where, and mark the changes on the drawings. A response that mirrors the notice structure can be re-reviewed in one pass.

Where a deficiency rests on an interpretation the designer disputes, say so explicitly and provide the alternative demonstration rather than making a silent change.

Risks, limitations and safeguards

• Template wording can be applied where it does not fit; reviewers must be able to edit freely.
• Over-long notices bury the critical items; order by severity and separate administrative items.
• Automated draft text must be reviewed before sending, and the reviewer remains the author of record.
• Citing evidence exposes extraction errors, which is a benefit — but it requires the evidence link to be correct.
• Notices become part of the record; write them as documents that may be read years later.

PermitAssure perspective

PermitAssure composes notices from the finding record, so requirement, edition, evidence and location are populated from what was actually evaluated. Reviewers edit and approve every notice; the platform does not send communications on its own authority.