Regulatory Submission Engine

From hundreds of submissions to a response you can defend.

The Regulatory Submission Engine helps your team analyse public submissions, see sentiment by issue and draft responses, with every point traced back to its source. Built for government teams consulting on a paper, and for the engagement and planning teams responding to submissions on a project.

The challenge

Responding to submissions is high stakes

Every submission deserves a fair reading, and every response will be read closely. That work lands on small teams, on tight timeframes.

The volume spike

A major consultation or project can attract hundreds or thousands of submissions, often in a few weeks.

The scrutiny

Your responses are read by regulators, decision-makers and the community. A missed issue is a real risk.

The consistency gap

Different reviewers classify issues differently, and knowledge gets lost in spreadsheets.

The platform

What the engine produces

The engine does the reading and the cross-referencing, so your team can focus on judgement. It materially reduces the work of reading and responding to submissions.

  • Issues and themes

    Every issue raised across every submission, grouped into themes your team can refine.

  • Sentiment by issue

    Where stakeholders support, oppose or raise concerns, shown issue by issue.

  • Stakeholder briefings

    Meeting briefings that set out what a stakeholder raised and where.

  • Help drafting responses

    Helps your team draft responses by issue or theme, plus individual responses for key stakeholders.

  • Traceability

    Every point links back to the submission sentence it came from.

  • Branded Word and PDF exports

    Branded Word and PDF reports, ready for your team to review and finalise.

How it works

Three steps to a response your team can defend

From the submissions you received to a response your team owns.

  1. Load

    Upload the paper and the submissions you received.

  2. Analyse

    The engine reads every submission, identifies the issues and sentiment, groups them into themes, and links each point back to its source.

  3. Review and respond

    Your team checks the results, refines themes, prepares stakeholder briefings and drafts responses by issue, then exports to Word or PDF.

Read the full process

Who it's for

For every team that must respond to submissions

Government teams and project teams face the same task from different sides: hearing what people said, and showing how each issue was considered.

Proponents

Exhibition and response to submissions on a project.

Account for every community submission and respond to each issue the community raised.

Learn more about Proponents

FAQ

Frequently asked questions

Is this a consultancy service?

No. It is a platform your own team uses. If you want to see results before committing, we can run a single report for you.

How is this different from Copilot or ChatGPT?

General assistants are powerful, and we use them too. The difference is what the engine is built for:

  • Built for one job. General assistants are built for every industry. The engine only does submissions.
  • Consistent, whoever runs it. The same structure and quality whoever on your team uses it, however much they know about prompting. Every quote is checked against its source.
  • Thorough. It works through every submission against every theme, rather than answering in minutes and skipping steps.
  • The best model for each task. We’re not locked to one model provider, and every model we use runs in Australia.
  • Predictable cost. Our pricing is mostly flat, and we carry the processing cost.
  • You ask, we build. Need a feature or a fix? Tell us and we build it.
Does it write our responses?

It helps your team draft responses by issue or theme. Your team reviews them and owns the final words.

Where is our data stored?

In Australia, both storage and processing.

What file types can we upload?

PDF, Word and many more.

Can we try it on a past project?

Yes. Choose a past consultation or project and send us the paper and its submissions. We run them through the engine and hand you the report, so you can see how it handles your own material before choosing a plan. Book a walkthrough or email us to arrange one.

See it on one of your own papers.

Book a walkthrough with our team, or ask us about running a single report on a past or live project.