Instead of Solv
Stop renting Solv. Own your injury and claims system.
We build your version around your sites, the schemes they sit under and the way your return to work team works, bring your Solv injuries and claims across and run it for you. Your business keeps every injury, certificate, plan and payment.
Solv publishes no price. Its pricing page says you pay a one-time setup fee and then an annual licence fee, quoted on the size of your business, your requirements and your injury and claim volumes.
- check_circleYour data in a database you own
- check_circleOpen source, no lock-in
- check_circleBuilt and run by Enterprise DNA
What the licence charges for
A setup fee, then a licence that follows your claims
Solv is sold on a quote. Its own pricing page says the annual licence is set by the size of the business and how many injuries and claims you run through it, on top of a setup fee. Compare that with your own claims records, where another site, another claim or another case manager costs nothing to add.
A quote, never a price list
There is no published price to compare. You learn what the licence costs after a pricing form or a call with sales.
A bill that grows with your injuries
The licence is quoted on your injury and claim volumes. A bad year on the floor, a new site or an acquisition moves what you pay.
A setup project before you start
A one-time setup fee comes first, and the vendor says onboarding takes from 6 to 18 weeks.
The legislation, as they keep it
The rules for each state live inside the vendor's system. You see the alert, not the section of the Act behind it.
The reports they chose to build
You get the standard reports and charts. Hours from injury to insurer notice by site, or claims stepping down to 80% next month, depend on what they offer.
Your workers' health records in their cloud
Injury, certificate and claim history is confidential and you keep it for years. Today it sits in a system you rent rather than own.
Your own injury and claims desk
Start with the deadlines and rates the law sets
Deadlines
Every clock an injury starts, with the section behind it
Record an injury once and it shows every deadline it starts for that site, counted from when a supervisor became aware.
- check The insurer told within 48 hours in New South Wales and within 8 business days in Queensland
- check The claim to the insurer within 7 days in New South Wales and to the agent within 10 days in Victoria, and WorkSafe told of a mental injury claim within 3 business days
- check A cover decision within 21 days for an ACC Accredited Employer, with deemed cover shown the day the time runs out and a decline refused after it
- check Notifiable incidents to the regulator and the register of injuries for each workplace, with a deadline met late kept on the record as late
Recovery
Certificates and plans that check each other
Every certificate of capacity is copied in with its restrictions, and the return to work plan is held to it.
- check A certificate that has run out, or one about to, at the top of the list each morning
- check A plan refused when it asks for more hours than the certificate allows, or when the worker has no capacity
- check Suitable capacity with no plan agreed after ten days, and a plan review date missed, both flagged
- check The plan for signing and the suitable duties letter to the treating doctor, drafted from the records
Money
Weekly compensation at the right rate
The weekly amount comes from pre-injury earnings, hours worked and the week of incapacity, with the rule written beside it.
- check 95% then 80% of pre-injury earnings in New South Wales and Victoria, with the date each claim steps down
- check First week compensation at 80% in New Zealand flagged until it is paid
- check The same pay period or invoice refused a second time, and no weekly payment on a declined claim
- check Money the insurer or agent owes back listed by how long it has waited, so a seven-week-old reimbursement gets chased
Answers
Questions across every site and claim at once
Ask in plain English and get the answer from your own records.
- check Which mechanisms of injury cost the most this year, paid and estimated, by site
- check How many hours each site takes to tell its insurer
- check Which claims step down from 95% to 80% in the next 30 days
- check Which open claims have gone quiet, and what is estimated on them
Make it yours
Design your own Solv replacement
Everything starts from the open-source base. Then it gets your name, the parts you run, your rules and your data from Solv. Try it here, and we build the real one.
2. What it runs
3. Make it fit
4. Your colour
Answered from your own database
Good morning. Here is what needs you today.
We build it from the open-source base, bring your Solv data across and run it for you.
What it looks like
Ask it like you would ask a colleague
Real answers from a fictional food manufacturer with an ACC Accredited Employer plant in Auckland and insured sites in New South Wales, Victoria and Queensland. Your return to work team asks the question and checks the records behind the answer.
Injury Claims for Claude Code
Connected to your own database
What needs my attention on injuries and claims today?
claim to agent overdue
- Ref
- CLM-0004
- Detail
- Marco Russo (MEL): due 2026-10-31 23:59. Vic Workplace Injury Rehab...
cover deemed: decision missed
- Ref
- CLM-0009
- Detail
- Daniel Fale (AKL): due 2026-10-30 23:59. Accident Compensation Act ...
first week compensation overdue
- Ref
- CLM-0009
- Detail
- Daniel Fale (AKL): due 2026-10-23 23:59. Accident Compensation Act ...
insurer notice overdue
- Ref
- INJ-0001
- Detail
- Josh Kelly (SYD): due 2026-11-01 10:00. NSW Workplace Injury Manage...
insurer notice overdue
- Ref
- INJ-0007
- Detail
- Kylie Brooks (BNE): due 2026-10-29 23:59. Qld Workers' Compensation...
mental injury notice overdue
- Ref
- CLM-0005
- Detail
- Sarah O'Neill (MEL): due 2026-10-30 23:59. Vic WIRC Act 2013: notif...
register of injuries overdue
- Ref
- INJ-0003
- Detail
- Ana Moala (SYD): due 2026-11-01 23:59. NSW 1998 Act s 63: keep a re...
regulator notice overdue
- Ref
- INJ-0004
- Detail
- Marco Russo (MEL): due 2026-10-22 08:00. Work Health and Safety Act...
certificate expired
- Ref
- CLM-0002
- Detail
- Priya Nair (SYD): last certificate ran out 2026-10-31
plan review missed
- Ref
- RTW-001
- Detail
- Priya Nair (SYD) CLM-0002: review was due 2026-10-28
action overdue
- Ref
- ACT-001
- Detail
- CLM-0006: Ask Dr Ellis whether cab work can come back at the next r...
certificate expiring
- Ref
- CLM-0004
- Detail
- Marco Russo (MEL): no capacity to 2026-11-04
reimbursement to chase
- Ref
- PAY-0007
- Detail
- Tom Nguyen CLM-0006: 1449.00 AUD paid 2026-08-05, 89 days with Work...
gone quiet
- Ref
- CLM-0006
- Detail
- Tom Nguyen (MEL): no case note since 2026-10-08
gone quiet
- Ref
- CLM-0009
- Detail
- Daniel Fale (AKL): no case note since 2026-10-13
| Item | Ref | Detail |
|---|---|---|
| claim to agent overdue | CLM-0004 | Marco Russo (MEL): due 2026-10-31 23:59. Vic Workplace Injury Rehab... |
| cover deemed: decision missed | CLM-0009 | Daniel Fale (AKL): due 2026-10-30 23:59. Accident Compensation Act ... |
| first week compensation overdue | CLM-0009 | Daniel Fale (AKL): due 2026-10-23 23:59. Accident Compensation Act ... |
| insurer notice overdue | INJ-0001 | Josh Kelly (SYD): due 2026-11-01 10:00. NSW Workplace Injury Manage... |
| insurer notice overdue | INJ-0007 | Kylie Brooks (BNE): due 2026-10-29 23:59. Qld Workers' Compensation... |
| mental injury notice overdue | CLM-0005 | Sarah O'Neill (MEL): due 2026-10-30 23:59. Vic WIRC Act 2013: notif... |
| register of injuries overdue | INJ-0003 | Ana Moala (SYD): due 2026-11-01 23:59. NSW 1998 Act s 63: keep a re... |
| regulator notice overdue | INJ-0004 | Marco Russo (MEL): due 2026-10-22 08:00. Work Health and Safety Act... |
| certificate expired | CLM-0002 | Priya Nair (SYD): last certificate ran out 2026-10-31 |
| plan review missed | RTW-001 | Priya Nair (SYD) CLM-0002: review was due 2026-10-28 |
| action overdue | ACT-001 | CLM-0006: Ask Dr Ellis whether cab work can come back at the next r... |
| certificate expiring | CLM-0004 | Marco Russo (MEL): no capacity to 2026-11-04 |
| reimbursement to chase | PAY-0007 | Tom Nguyen CLM-0006: 1449.00 AUD paid 2026-08-05, 89 days with Work... |
| gone quiet | CLM-0006 | Tom Nguyen (MEL): no case note since 2026-10-08 |
| gone quiet | CLM-0009 | Daniel Fale (AKL): no case note since 2026-10-13 |
Ask it anything
Questions answered from your injury and claims records
These examples combine your own records across every site, scheme and claim at once. They are not a claim that Solv cannot produce a similar report.
Switching
How to switch from Solv
A move usually involves exporting your employee, injury and claim records, checking the import, and running both systems side by side before you stop using Solv.
- 1
Export your Solv records
Use Solv’s reports to export your employees, injuries and claims as comma-separated files. Export the whole case files available from those reports too, so you can review the history you want to bring across. Check that you have the records you need before starting the import. If you are unsure which reports to use, check with Solv.
- 2
Test the import first
Run a test import for employees, then injuries, then claims. The test run keeps nothing, so you can check the results before adding records to the new system. Keep the order: injuries and claims depend on the employee records being there first. If your Solv reports use different headings, the import can map them to the fields it expects.
- 3
Load the records in order
After the test run looks right, import employees, injuries and claims in that same order. The imported history arrives already registered and notified, so the attention list starts clean. Certificates, return to work plans and payments on open claims are brought across as part of the setup. Repeated rows are skipped, and one bad row stops the whole file.
- 4
Review flagged records
Check the import results and address anything the import flags before relying on the records. If a report has different headings, map them rather than guessing which fields match. Since a bad row stops the whole file, correct the source or mapping and run the import again. Confirm that the records you intended to bring across are present.
- 5
Run both, then switch
Use Solv and the new system side by side for a short period. Compare the records and the work your team relies on, including open claims, certificates, plans and payments. Once you have checked the new system and your team is ready to use it, switch your process over and stop using Solv.
Where the real effort goes
Most effort is not the file transfer. It is matching your Solv report headings to the fields here, deciding which case history to bring, and checking that your own fields and working rules are represented correctly. If Enterprise DNA installs and runs it for you, they handle the mapping and migration as part of the setup.
Not ready for a call?
Get your Solv switch plan by email
We will send you the step-by-step plan for moving your business off Solv, what the move really involves, and how we would do it for you.
Sent. Check your inbox.
Your Solv switch plan is on its way.
Rather talk it through? Book a call arrow_forwardThree ways to make it yours
Start with the free injury and claims desk or have your version built
Open source
Do it yourself
Free code
- 1 Clone the repo and run npm install, npm test and npm run demo.
- 2 Open it in Claude Code, Codex, OpenCode or Cursor.
- 3 Export employees, injuries and claims from Solv reports as CSV files and import them with a dry run first.
- 4 Add each site with its state and whether it is insured, self-insured or accredited, then run /compliance and /attention.
Built around your business
We customise it
One setup fee, then a retainer
- check The deadlines and weekly rates for every state and scheme you run, including Comcare and self-insurance
- check Your notices, plans and decision letters in your own brand and wording
- check Your Solv injuries, claims, certificates and payments brought across and checked
- check A form for supervisors to report an injury from a phone, and regulator submission files, if you want them
Omni by Enterprise DNA
We run it for you
One setup fee, then a retainer
- check Installed and operated through Omni by Enterprise DNA
- check Access for every coordinator, case manager and site manager with no charge per user, plus backups and restore checks
- check Late insurer notices, expired certificates and reimbursements to chase raised every morning
- check The rules kept current as New Zealand and each Australian state change them
Questions
Instead of Solv, answered
Does this replace everything Solv does? expand_more
The free version covers injuries and workers compensation claims: sites, workers, the register, every statutory deadline, certificates, return to work plans, weekly compensation, payments, reimbursements and case notes. It has no live link to an insurer, no form for supervisors on a phone, no regulator submission files and no safety module. Claim numbers and decisions are recorded from the insurer, or we build the link, the form and the files on the same records.
Can we trust the deadlines and the weekly rates? expand_more
Each one is written beside the section of the Act it comes from, and the full list with sources ships with the free version so your team can check it. The deadlines cover New South Wales, Victoria, Queensland, New Zealand and notifiable incidents everywhere. Where no rule is built in, it says so and gives no figure rather than a guess. The insurer's calculation is still the one that pays.
What happens to the claims we already hold in Solv? expand_more
Solv exports injury and claim information from its reports. Employees, injuries and claims come across in that order, with a test run first that keeps nothing, and history arrives already registered and notified so the morning list starts clean. Certificates, plans and payments on open claims are brought across as part of the setup.
These are workers' health records. Who can see them? expand_more
They sit in a database your business owns, not a vendor's cloud. Records cannot be deleted, every change is logged with who made it, and nothing is ever sent from the system: notices, letters and plans are drafts a person reads and sends.
What do we pay Enterprise DNA? expand_more
One setup fee to build your version and bring your Solv records across, then a monthly retainer if we run it for you. There is no licence tied to your injury and claim volumes, and no charge per user. Book a call and we will price it against your Solv quote.
Own the records behind every injured worker
Take 30 minutes with Sam to go through your Solv quote, your sites and the schemes they sit under. We map your claims process and agree what your version needs before you change systems.
Injury Claims for Claude Code is free and open source, published by Enterprise DNA.
Done paying for Solv?
Get your version built