Consultation Submission Drafter
Turns a council or agency consultation notice plus your own prior submissions, policy positions and meeting resolutions into a structured, fully cited first draft — mapping each consultation question to a recorded position and flagging anything unrecorded for an officer to decide.
Reads the open consultation and your evidence, maps each question to a cited prior position, and hands an officer a grounded draft with every claim sourced.
Where this works well
The slow, invisible problem here is consistency under deadline. Every public consultation — a draft council plan, a road upgrade, a management strategy — implicitly asks your organisation to show that what you're saying now lines up with what you've said before. That evidence is scattered across old submissions, policy papers and meeting minutes, and an officer has to reassemble it from scratch every time the window opens, usually with only days to spare. This pattern earns its keep when you respond to consultations regularly and have a real archive of prior positions to draw on: a peak body, a traders' association, a community organisation, or a council unit responding to state and federal consultations.
It works best for the officer or advocacy lead who keeps finding themselves rebuilding the same argument under a closing clock. Mapping each consultation question to a cited prior position, and producing a sectioned draft with a source against every claim, turns a five-day reconstruction into a one-day review. The recaptured days go back into the judgment work — the framing, the relationships, the politics — not into hunting for the 2023 submission.
Where it works badly
If you have no archive — this is your first submission, or your prior positions were never written down — there is nothing to retrieve and nothing to cite, and the tool will honestly show most questions as unrecorded. It accelerates synthesis of existing positions; it does not invent a stance you've never taken.
It also fails quietly when your records are stale and unmarked. If a 2022 submission has been overtaken by a later board resolution that isn't in your library, the tool will surface and cite the *old* position as if it still stood. The failure mode is confident and plausible: a well-cited draft built on a superseded view. The honest test: pull your last three submissions and ask whether you could, today, point to the document behind each major claim and say which is current. If that takes you an afternoon of digging, the tool will have the same problem — and that gap is the work to fix first.
What it doesn't do — and shouldn't
The tool surfaces, maps and drafts. It does not decide what your organisation's position should be, and it does not lodge anything. The question of what to say to *this* council on *this* plan — how hard to push, what to concede, what's politically live — is the officer's judgment, and the draft goes to them to refine and approve before it goes anywhere near a Have Your Say portal.
That boundary is deliberate. A submission is a public, attributable act: under the Local Government Act 2020 (Vic), councils run consultations under a community engagement policy, and submissions are commonly published on a public register. Lodging the wrong position, or one your governance never endorsed, carries real consequence. So the tool's job ends at a cited draft with its gaps flagged; a person owns the decision and the lodgement.
What your data has to look like for this to work
Concretely, the tool needs a retrievable library of your recorded positions: prior submissions, policy papers, and board or committee resolutions, each stored somewhere it can be found and quoted, with a date attached. It needs the consultation notice itself — the draft document, its numbered questions, and the close date — and it needs superseded positions to be marked as superseded, not silently left alongside current ones. The citation against each claim is only as trustworthy as the date and source behind it.
Most organisations have some of this in good shape and some of it scattered across drives, inboxes and people's memories. Getting the prior-position library consistent and findable — deciding what counts as a position of record, where it lives, and how a new resolution supersedes an old one — is usually the real first job, and it's a matter of how you capture and keep information, not of buying a tool. That groundwork is bigger and more durable than the drafting layer on top of it, and it's the part we help with.
Could it draft a position we never actually agreed to, or commit us to something council can hold us to?
No — it only drafts from positions it can cite back to one of your own sources: a prior submission, a policy paper, a board or committee resolution, or the notes you supply. Where a consultation question has no recorded position behind it, it flags the gap rather than inventing an answer, so the officer decides what to say. Nothing is lodged until a person has read the draft and approved it.
Our prior submissions and minutes are a mess of PDFs and Word files across different drives. Will it still work?
Partly, and it will be honest about where it can't. It reads the documents you point it at and cites the specific source for each claim, but it can only retrieve a position that is actually written down somewhere retrievable. If your real position lives only in someone's head or in an email thread no one kept, it will show that question as unrecorded. Getting the prior-position library into a consistent, findable shape is usually the first piece of work, and it is the part we help with.
Does this replace the policy officer who normally writes our submissions?
It replaces the cold-start rebuild, not the officer. The judgment about what the organisation should say to this council on this plan stays with the person — the tool just removes the days spent hunting through old files and assembling the evidence trail. The officer's time shifts from reconstruction to refining the argument and the politics of it, which is where their experience actually earns its keep.
How current does the source material need to be? We don't want it quoting a position we've since reversed.
Currency is the real risk, so it cites the date and source of every position it uses and surfaces them for review rather than silently merging them. If a 2022 submission has been superseded by a 2025 resolution, the tool will still surface the older one unless the newer position is in your library — which is exactly why the officer reviews each cited claim before sign-off. Keeping superseded positions clearly marked in your records is part of what makes this reliable.
Where does our data go? These are sometimes commercially or politically sensitive positions.
Your prior submissions, notes and resolutions are processed within a private retrieval setup, not used to train a public model, and the draft stays inside your review environment until an officer chooses to lodge it. Treat the output the way you would any draft submission — once lodged through a portal like Engage Victoria's Have Your Say, it may be published on a public register, so the human lodgement step is also your last privacy check.
Estimated build: 4–6 weeks. Most of it is template work we've already done.
Fixed scope, fixed price, fixed dates.
The cost band reflects the engagement shape, not a per-feature line item. We work on fixed scope, fixed price, fixed dates — see the services catalogue for what falls inside each band.
Considering this for your org?
The honest place to start is a bite-sized first piece — one contained change, low risk. Tell us where it hurts; we’ll play it back, scope it, and show you what’s possible.