Tracking council report submissions
A PDF in Sent mail only answers part of the question. Keep the report, delivery evidence and outstanding action together.

Someone asks whether a property’s service report went to council. One person checks Sent mail, another searches a portal, and the technician has the document on a phone. You can usually reconstruct the answer, but it takes longer than it should and nobody knows which jobs still need attention.
A reporting register gives each visit one place to record the answer. It can start as a spreadsheet. The useful part is agreeing what each stage means and keeping the evidence beside the entry, rather than making everyone remember how the last report was sent.
Give each report a reference
Use a report number tied to the visit and system. Include the property address for searching, but don’t rely on the address alone: one property may have several systems and years of services.
Your register should identify the council, service date, report type and person handling submission. Record the applicable due date after checking the requirements for that work. Our Queensland Form 11 guide explains that report’s deadline and sources; it isn’t a deadline to copy onto every type of council document.
Keep the outgoing file linked to the row. A shared folder works if its naming is consistent and access is limited to people doing the work. An attachment somewhere in a long email chain is harder for a colleague covering leave to find.
Separate the stages
Choose labels your team can use without debate. For example:
| Stage | What the office should be able to show |
|---|---|
| Preparing | The visit record and who is finishing the report |
| Ready | The checked document and intended recipient |
| Sent or uploaded | A delivery record or portal reference |
| Accepted | An acknowledgement, where the council provides one |
| Needs action | The problem, responsible person and next check date |
These are suggested register labels, not a claim that every council uses those stages. Some councils provide a reference immediately; others communicate differently. Record the evidence you have rather than treating silence as an acknowledgement.
The owner copy is a separate task where required. Give it its own delivery field so a successful council upload doesn’t hide an unsent owner report.
Store evidence as it arrives
After an email submission, keep the outgoing message and attachment reference. Monitor for failed delivery. After a portal upload, capture the reference and any confirmation document while the session is still open.
Record when the event happened and who recorded it. If a colleague later updates the entry after a council response, preserve the earlier submission information. Overwriting the original date with today’s follow-up date makes the register less useful when someone asks what happened first.
For a correction, link the new version and state which earlier document it replaces. Keep the original file available internally. Our guide to rejected reports covers assigning the correction without losing the original submission trail.
Work from the unfinished list
Set aside a short daily review of rows needing action. Sort by due date, then check reports with no outgoing evidence and submissions with a failed delivery. Assign the next step to one person. A comment saying that somebody should chase council leaves the same uncertainty in place.
Once a week, compare recent service visits with the register. This catches the report that never became a row, which a filter on overdue entries can’t find. Also check a small sample of finished entries against their evidence. A confident tick should survive opening the linked file.
Keep the process when you change software
Ask a prospective supplier to demonstrate the stages using one of your ordinary reporting routes. Include a council that uses a portal, because an integration claim may cover email delivery while a person still has to perform the upload.
In Rangefront Waste, email, SFTP and API submissions are queued by the system. Portal and manual methods wait for a person to upload the report and record the receipt. The Compliance page shows due, overdue and rejected work, and its report sheet holds submission details. Council reporting setup still needs checking for each council you work with; software can’t infer the correct destination from an old email address. See the wastewater service workflow for how field capture feeds that queue.



