Public Consultation Submission Handling SOP
Use this when: A consultation will bring in many submissions, and you need a fair, traceable process.
Owner: [consultation lead] 1. Before opening, publish how submissions will be used, and whether they may be made public. 2. Log each submission with a reference number and the date it was received. 3. Acknowledge receipt. 4. Remove personal details from working copies, where your policy requires. 5. Tag each one by theme, using an agreed list. 6. Have a second person check a sample for consistent tagging. 7. Note late submissions, and apply your stated rule to them. 8. Summarize the themes, noting both common views and important minority views. 9. Have the lead approve the summary. 10. Publish what you heard, and keep records under your retention schedule.
Before you use this: Your privacy, access-to-information and records rules apply, so check this with your privacy office.
Fill in the items in square brackets and adapt this to your business. It's a starting point, not legal or professional advice. You can also check the AI & Privacy Checker.
More for government
Public Enquiry Phone Script for Government Offices
Staff answer public calls and need a consistent, helpful approach.
AI Prompt to Summarize Consultation Comments
Staff want a first-pass grouping of consultation comments to check by hand.
More sops
New Listing Launch SOP
A listing agreement is signed and you need every launch to happen the same way.
RFI Logging and Tracking SOP
Questions to the design team are getting lost, or nobody can say which ones are still open.
Service Call Close-Out SOP for Technicians
Job notes, photos and follow-ups vary from one technician to the next.
Check your key numbers with the Operator ScorecardSAZ's government practice