Enforcement notice drafter

A notice line is ready for your signature only when it names both the finding in the case file and the statutory clause that finding engages. If either is missing, the line stays blank. The model does not guess the clause from a similar case, and it does not write a penalty amount that is not already calculated from a published schedule.

That rule is the quality bar. A fluent paragraph that sounds like an enforcement notice is not a notice. A line that cites "inadequate refrigeration" without the inspection observation, or that cites a regulation without the finding that triggers it, is unfinished work. You still sign. You still serve. Generation does not replace either act.

The same bar applies to money. Penalty figures belong on the notice only when a schedule or a calibrated calculation already exists in the pack you loaded. If the amount is not there, the amount field stays empty. Do not treat a plausible-looking number as a statutory figure.

When the finding itself is thin, stop and send the file back. The evidence sufficiency assessor is the check that belongs before drafting, not after you have already produced a letterhead document that looks ready to post.

Do not prompt a model with a case number and a request to write the notice. Load two sources, then draft.

The case file is the factual record: inspection notes, photographs with timestamps, prior warnings, licence or permit conditions, correspondence, and any finding already written up. If the finding lives in an inspection write-up, start from that document rather than from memory. The inspection report auto-drafter is a common upstream source. Treat its output as a draft finding until you have accepted it into the file.

The clause book is the legal record: the Act, regulation, by-law, licence condition, or code provision that the finding is alleged to breach, plus any penalty schedule that attaches to that provision. Keep the edition and the commencement date with the text. A clause pulled from last year's reprint is a different instrument.

Permit systems, records management, and legal research platforms (Accela, Tyler, Microsoft, LexisNexis, and the rest of that class) hold pieces of this pack. They do not hold a finished notice. Pull the finding from the case system and the clause from the authorised text. Do not ask the model to remember either.

If the clause book has no mapping from this finding to a provision, you do not have a notice to draft. Log the gap. Do not let the model pick the nearest-looking section.

With both sources loaded, generate the notice structure your authority already uses: parties, premises, finding, legal basis, required action, penalty if any, response rights, and service details. Every substantive line should carry dual cites: the case-file locator for the finding, and the clause citation for the legal basis.

Worked example. One premises, one finding. The case file records that on 4 June an officer measured the display cabinet at 11°C at 14:20, against a documented maximum of 8°C, photograph 17 in the inspection album. The clause book maps that observation to the temperature-control duty in the food hygiene regulations your authority enforces, and the penalty schedule lists a fixed penalty for a first breach of that duty. The draft line then reads, in substance: display cabinet recorded at 11°C at 14:20 on 4 June (inspection album, photograph 17), contrary to the mapped temperature-control provision, fixed penalty as set out in the schedule entry. Both cites are present. The amount is the schedule amount, not a number the model chose.

Change one input and the line must change with it. If photograph 17 is not in the file, the finding cite is missing and that line stays empty. If the clause book has no mapped provision, the legal-basis cite is missing and that line stays empty. If the schedule has no entry for this breach, the penalty amount stays empty even if the rest of the notice can still be drafted as a warning or a works-required notice. A penalty with no schedule is not a penalty. Do not let the model average other cases, round to a typical band, or copy last month's ticket.

Deadlines follow the same rule. A compliance date belongs on the notice only when your procedure, the instrument, or a recorded officer decision already supplies it. Inventing a deadline, fourteen days because that is what the last notice said, is a defect. Leave the date field blank and fill it when you decide, or when the statute supplies a period.

Required works and prohibited acts should be copied from the finding and the clause, not paraphrased into something easier to read if the paraphrase drops a condition. If the model cannot quote both, it leaves the instruction blank.

After generation, read the dual cites before you read the prose. If a line is eloquent and uncited, it is not ready.

Where a penalty needs more than a schedule lookup, bands, aggravation, previous similar breaches, send the amount out to the penalty calibration engine and bring the result back into the notice. Do not let the notice drafter invent a figure that the calibration step has not produced.

You review every dual cite against the file. You confirm the party and the premises. You confirm that empty fields are empty for a reason, not because the model skipped a paragraph. You decide whether this is a warning, a works notice, a penalty notice, or a referral. Then you sign.

The draft is not served when it appears in your inbox. Treating the draft as served is a failure mode with downstream consequences: clocks that never started, appeal rights that were never triggered, and a file that looks complete while the recipient has nothing. Service is a separate act under your authority's rules, personal, postal, electronic, or affixing. Record the method, the time, and the copy served. The generated document is an input to that act.

Do not backfill blanks at sign-off by typing a clause you know or a penalty you usually use. If the cite was missing at generation, either load the missing source and regenerate that line, or write the cite yourself from the authorised text and record that you did so. Silent completion of a blank is the same as invention.

If review shows the finding will not stand, do not dress it in better language. Withdraw the draft. Return to evidence. A signed notice on a finding you do not believe is worse than an empty line.

Store drafts as drafts. Use a status that cannot be mistaken for served in the case system. If your workflow auto-stamps a date on generation, treat that stamp as a document date, not a service date.

Once you have signed and served, the notice becomes the baseline for what happens next. The post-enforcement compliance monitor should watch the requirements you actually served, not an earlier generated version that still had blank penalty or blank deadline fields. Mismatch between the signed copy and the monitoring copy is how follow-up work chases the wrong obligation.

Re-drafts after service are new documents. Do not overwrite the served PDF with a corrected generation. If a clause cite was wrong, withdraw or vary under your procedure. Do not silently replace the file.

The quality outcome is narrow on purpose. Every notice line either cites the case finding and the statutory clause, or it is empty. Empty is correct when the source is missing. A filled line that cannot be traced to both sources is the defect. You remain the officer who signs and serves.