Enterprise DNA

Instead of NextRequest

Stop renting NextRequest. Own your records request desk.

We build your version around how your officers receive, search and review requests. We map your NextRequest history, connect the services you need and run the system for you.

NextRequest pricing is quoted for your organisation. Bring the current invoice and the services it covers. We compare the complete cost before recommending a switch.

  • check_circleYour data in a database you own
  • check_circleOpen source, no lock-in
  • check_circleBuilt and run by Enterprise DNA

What the subscription covers

Separate the request desk from the services around it

NextRequest combines tracking, public intake, document review and delivery. Your invoice is the starting point. Its pricing page asks you to contact sales, so there is no list-price saving claimed here.

paid

An organisation-specific quote

CivicPlus asks for your organisation details before quoting NextRequest. Compare your actual renewal and included services.

inbox

Public request intake

A public portal collects requests. We scope the intake connection your agency needs around its own request history.

assignment

Routing and follow-up work

NextRequest routes requests and follow-up tasks. Those assignments, owners and dates can live in your own system.

find_in_page

Document review tools

RapidReview handles document redaction. We agree the document tools and review process your version needs before switching.

receipt_long

Billing and cost recovery

NextRequest includes invoicing tools. We keep the request desk separate from any payment service your agency retains.

download

Reporting and leaving

Requests Reports export selected fields. We check the exported scope and preserve every original row during migration.

Your owned request desk

Run the work from the evidence

Deadlines

See the requests that need attention

Read the due date beside the work still outstanding. An imported date remains subject to officer review.

  • check Overdue requests with their responsible officer
  • check Open searches and document reviews beside each deadline
  • check Original dates preserved when an extension is recorded
  • check Missing jurisdiction and deadline basis shown for review

Searches

Give each search a scope and an owner

Record what a department must look for and the evidence returned. A completed search needs a result, including when nothing was found.

  • check Department, owner, scope and due date on every search
  • check Evidence references attached to completed work
  • check Open workload compared across departments
  • check Internal search instructions drafted from current records

Review

Keep the decision trail with the request

Officers record the outcome for each document. The system checks that outstanding searches and reviews are resolved before recording a completed response.

  • check Release, redact or withhold outcomes recorded by an officer
  • check Reasons and authority recorded with each review
  • check A reviewed-copy reference required for redacted documents
  • check Actual response date, complaint notice and evidence kept together

Ownership

Change the desk around your own process

Your records stay available for new questions and new reports. The free base provides the internal desk, and we build the connected version around your agency.

  • check Original export rows retained beside the working history
  • check Work minutes and progress notes tied to a request
  • check Branded internal summaries and review schedules
  • check Your own fields, review rules and joined reports added as needs change

Make it yours

Design your own NextRequest replacement

Everything starts from the open-source base. Then it gets your name, the parts you run, your rules and your data from NextRequest. Try it here, and we build the real one.

2. What it runs

3. Make it fit

4. Your colour

Your business · your NextRequest replacement Your version
YB Your business

auto_awesome

Answered from your own database

Build my version

We build it from the open-source base, bring your NextRequest data across and run it for you.

What it looks like

Ask it like you would ask a colleague

Real answers from the demo data that ships with Records Requests for Claude Code. It runs in Claude Code inside the Claude app, so it feels like any chat you already use.

forum

Records Requests for Claude Code

Connected to your own database

Which requests are overdue, and what still needs doing?

DEMO-104

Owner
Leo
Due_on
2026-09-25
Days_left
-40
Searches_open
0
Reviews_open
0

DEMO-101

Owner
Mira
Due_on
2026-11-01
Days_left
-3
Searches_open
1
Reviews_open
1

Ask it anything

Questions your request history can answer

These questions run against the demonstration records today. Your officers can change the rules and reports around their own process.

chat_bubble Which overdue requests still have departmental searches open?
chat_bubble Which requests have documents waiting for an officer review?
chat_bubble Which departments hold the largest open backlog?
chat_bubble Which request deadlines have no recorded basis?
chat_bubble Which open requests have no recorded work for fourteen days?
chat_bubble Which searches are late and who owns them?
chat_bubble Which requests consumed the most recorded work minutes?
chat_bubble Which extension notices were recorded after the previous deadline?
chat_bubble Which imported closed requests lack response evidence?
chat_bubble Who recorded each deadline change and review decision?

Switching

How to switch from NextRequest

A move usually involves exporting your request register, mapping your fields and rules, checking the imported records, then running both systems side by side before you switch.

  1. 1

    Export your request register

    In NextRequest, download a Requests Report and select the fields you need. Bring across the request register, including its dates, statuses and other fields you rely on. Check the available fields with NextRequest if you are unsure what the report includes. Documents and message archives are not part of this request-register import, so plan their migration separately.

  2. 2

    Map and load the report

    Use an actual Requests Report export to check how its headings, dates and statuses map to the new register before you rely on the imported records. The import validates and loads a CSV report, and preserves the original rows and extra fields. Start with a trial using your agency's export, rather than assuming a synthetic example matches your data.

  3. 3

    Review the import flags

    Check the imported record counts and compare key dates and statuses with NextRequest. Review deadlines that remain unconfirmed, since imported deadlines are not treated as verified legal dates. Check any closed requests flagged for missing response evidence, and resolve discrepancies before staff rely on the new register. Officers still need to confirm the basis for deadlines and closure records.

  4. 4

    Run both systems side by side

    Keep NextRequest in use while you check the new register against current work. Compare requests, deadlines, open searches and reviews, and confirm that staff can find the history they need. Keep your existing intake, requester communication, redaction and delivery processes in place until any required replacements or connections are installed and tested. The base system does not provide those services.

  5. 5

    Switch off NextRequest

    Switch off NextRequest only after you have checked the imported records and decided how to handle documents, message archives and any services you still use there. Confirm that your approved intake, redaction and response process will continue to work. The new base is an internal request desk, not a public portal or an automatic disclosure tool. Keep the evidence and process your officers need.

construction

Where the real effort goes

The main work is usually mapping your own fields, dates and statuses, agreeing how your rules apply, and deciding which history to bring. The request register import does not cover documents or message archives, so those need a separate plan. Enterprise DNA maps the export, changes fields and rules, and handles this setup work when you have them run the system.

Not ready for a call?

Get your NextRequest switch plan by email

We will send you the step-by-step plan for moving your business off NextRequest, what the move really involves, and how we would do it for you.

One email with your plan. No spam, and you can unsubscribe any time.

Three ways to own it

Build it yourself, have it customised, or have it run for you

Open source

Do it yourself

Free, open source

  1. 1 Clone the repo and run npm install, npm test and npm run demo
  2. 2 Open it in Claude Code, Codex, OpenCode or Cursor and ask for the overdue desk
  3. 3 Export a NextRequest Requests Report as CSV, map its columns and test the import
  4. 4 Review dates and counts, then protect the database and keep your existing intake and delivery services until the switch is checked
Get it on GitHub

Built around your business

We customise it

One setup fee, then a retainer for ongoing work

  • check Your departmental structure, deadlines and review rules
  • check Your NextRequest export mapped and reconciled with the original
  • check A web front end, public intake and document connections scoped for your agency
  • check A different technology stack when your environment requires it
Get your version built

Omni by Enterprise DNA

We run it for you

One setup fee, then a retainer

  • check Installed with the access and backup arrangements your agency approves
  • check The request desk and weekly review prepared for your officers
  • check Connections maintained as the surrounding systems change
  • check Run through Omni by Enterprise DNA, with your team retaining every disclosure decision
Book a 30-minute review

Questions

Instead of NextRequest, answered

Will this cost less than our NextRequest renewal? expand_more

The free base has no licence fee. Hosting, your agent subscription and the time to operate it are separate. CivicPlus quotes NextRequest for each organisation. Sam compares your invoice, included services and the complete replacement scope before recommending a switch.

Can we bring our existing requests across? expand_more

Yes. NextRequest provides a Requests Report download with selectable fields. The import brings across the request register, preserves the original rows and flags deadlines for review. We reconcile the headings, dates, statuses and counts with you. Documents and message archives need a separate migration plan.

What happens to our public portal and redaction tools? expand_more

We build the intake and staff screens you need and connect the document tools your agency approves. The free base runs the internal request desk. Keep your existing intake, redaction and delivery process until those connections are installed and tested.

Does it decide what we can release or calculate legal deadlines? expand_more

Your authorised officers make those decisions. The system records the jurisdiction, reviewed due date, reasons and supporting evidence. It flags missing details and dates that have passed. Officers check applicable law, holidays, redacted files and complaint rights. Nothing sends or publishes from the free version.

Can several departments work from the same history? expand_more

Yes, in an installation configured for your agency. We agree staff access, document storage, backups and the screens or connections each department needs. The free base is for a trusted operator. A shared service gets its access controls tested before staff use it.

Bring your NextRequest invoice to a 30-minute call

Spend 30 minutes with Sam. Bring the renewal, a sample request workflow and the services your officers rely on. We will map what your own request desk needs, what connects to it and how the switch would be checked. If staying with NextRequest is the better call, we will say so.

Records Requests for Claude Code is free and open source, published by Enterprise DNA.

Done paying for NextRequest?

Get your version built