Setting up council reporting
A state template is a starting point. Your office still needs the right form, delivery route and owner-copy process for each council it reports to.

Copying the last council’s email address and changing the name is a risky way to set up reporting. The service form, property reference and delivery process need checking for the council and work involved. A profile should tell the office how to send the right document and what evidence to keep afterwards.
Start with the councils your current customers actually use. Choose one familiar reporting route, document it and test it before importing a long directory. A smaller checked list is easier to trust than dozens of entries nobody has confirmed.
Write down the source
For each reporting requirement, save the official council or government page, the date checked and any direct clarification you received. Name the report type and work it applies to. A note saying council requires paperwork doesn’t help someone choose between a service report and an installation document.
Check the current form or specification against your template. Where a council supplies instructions or a property reference, record those details in the appropriate place. Keep uncertain requirements marked for confirmation and assign the question to someone.
For Queensland treatment plant servicing, the Form 11 guide links the official form and regulation. Use those sources for that report; don’t infer another jurisdiction’s process from the fact that the work looks similar.
Define the delivery route
Record the actual method: email, council portal, an agreed system connection or another confirmed route. For email, check the destination and any naming instructions. For a portal, identify who has access and what information they need to complete an upload.
An API option in software doesn’t mean a council offers an API connection. Confirm availability, access and the expected response before treating it as an automated route. The same applies to SFTP or any other integration a supplier lists.
Give manual work a named owner. If a person must upload the report, include that action in the routine list instead of leaving it as an unwritten step after a PDF is generated.
Map the property and recipients
Check which council belongs to each site and whether the council uses a reference that differs from your internal site number. Test a property with several systems so the report identifies the specific unit serviced as well as the street address.
The owner-copy process also needs configuring where applicable. Confirm the contact and delivery details, then distinguish them from the billing customer or person who arranged access. Having one email field filled in doesn’t prove every required recipient has been considered.
Keep reporting destinations in the council profile and property details against the property. That avoids changing a council-wide address separately on every job when the destination changes later.
Set dates deliberately
Enter the deadline that applies to the particular report after checking its source. Document what event starts the calculation and how your team reviews upcoming work. Don’t pick a convenient number just to fill a required software field.
Set an internal review target earlier than the external due date where practical. Someone needs time to resolve an incomplete form or a rejected submission. Agree who covers that review when the usual person is away.
Keep the source beside the setting so it can be rechecked. A deadline copied from an old spreadsheet without context is difficult to defend or update.
Test from field form to receipt
Use an authorised sample or agreed test process before sending anything to a real council destination. Generate the report, open the PDF and compare it with the expected format. Check the owner’s copy independently of the council copy.
Walk through the submission route with the person who will do it. For a portal, test that the office knows where to record the receipt. For a failed delivery, check how the task returns to the unfinished list. Our submission register guide describes the evidence to keep at each stage.
Rangefront Waste starts from state and territory rule templates, then uses a profile for each council. Portal and manual uploads need a person to upload the file and record the reference; email, SFTP and API methods can queue delivery. Review those settings with your own requirements when evaluating wastewater management software. Keep the checked profile date visible so future changes have an owner too.


