The developer asks where the adoption is. Nobody knows for sure.
Your practice designed the drainage and highways for six residential sites. Each has a sewer adoption submission with the water company and a highway adoption submission with the local authority. Some are on the first round of technical comments, one is waiting for a fee to be paid, another has an approval in principle but needs a revised long section. The developer's project manager emails every other week asking for an update.
To answer, an engineer opens old emails, finds the last response from each authority, and tries to remember which comments were already answered in the resubmission.
Why adoption submissions are hard to follow
- Each water company and highway authority has its own process, forms and portal.
- Technical comments arrive as letters or PDFs with numbered points, and responses are scattered across drawings and emails.
- Fees, inspection charges and bonds are requested at different points and must be passed to the developer.
- Submissions go quiet for weeks and nobody notices until the developer asks.
- Different engineers handle different sites, each with their own way of keeping track.
The time scale matters too. An adoption agreement can run on for a long time, and the engineer who made the submission may have moved to other work, or left, before the final approval arrives. Knowledge of where each submission stands walks out of the door with them.
What losing track costs
| Gap | Consequence |
|---|---|
| Unanswered comment | Resubmission rejected, another round of review |
| Fee request missed | Submission sits unreviewed |
| Silent authority not chased | Adoption slips further behind the build |
| No status view for developers | Frequent update requests, and a strained relationship |
For developers, delays in adoption can hold back other things they care about, and they notice which consultants keep them well informed.
How we build an adoption tracker
- Each site has records for its sewer and highway submissions, with authority, reference, submission date and current stage.
- Authority responses are saved to the record from a project mailbox, and numbered comments are split into individual items.
- Each comment is assigned to an engineer and linked to the drawing revision or calculation that answers it.
- When a resubmission is prepared, a comment response schedule is generated from the log.
- Fee requests and payments are tracked, with a notice sent to the developer to pay and a reminder if it has not been confirmed.
- If an authority has not responded within the period you set, the engineer is prompted to chase.
- A status page per developer shows every site's adoption position, which you can share or export for their meetings.
The tracker does not interpret the authority's standards or tell your engineers how to design to them. It keeps the admin and the correspondence in order.
Existing submissions are loaded from your current spreadsheets and inboxes, so the tracker starts with every live site rather than only new ones. We also set up each authority's typical process steps as a template, so a new submission starts with the right sequence of stages already in place.
After the tracker goes in
Engineers answer comments against a list, not a letter, and nothing is missed on resubmission. Silent submissions are chased because the tracker notices the silence.
When the developer asks for an update, the answer is a link or a report produced in seconds.
Sound like your team?
- Adoption status lives in engineers' inboxes.
- Comment responses are prepared by rereading the authority's letter.
- Fee requests have held up a submission.
- Developers ask for adoption updates frequently.
- Nobody notices when an authority has gone quiet.