Pricing and enterprise access
Schedule Forensics is licensed per reviewing organisation, not per seat and not per analysis. A department that reviews four hundred submissions a year pays the same as one that reviews forty, because what you are licensing is the review capability, not its throughput.
Run it on your schedule first Ask about an enterprise package
Why there is no number on this page
Because the work to stand one up honestly is not finished, and publishing a figure before it is would be a number we would have to withdraw.
The pricing model is settled: per reviewing organisation, scoped to the procurement route your organization actually has. The figures are argued against published public-sector procurement thresholds, and several of those thresholds are in the middle of being re-verified — a state that moved its ceiling, a delegated authority we could not retrieve, a federal authorization programme whose retirement date is unconfirmed. Quoting a price built on a threshold that moved is worse than quoting none.
So: tell us which procurement route applies to you — micro-purchase, delegated authority, a cooperative contract, or a competed award — and the quote is built to it. That conversation is not a sales sequence and it costs nothing.
What a deployment includes
| The engine | Runs inside your environment. No network calls, and no third-party runtime dependencies — enforced as a build failure rather than promised. |
| The rule packs | Thirteen authority packs: federal specifications, the analysis standards, and the state DOT specifications your reviewers actually work to. |
| The local browser interface | So reviewers work without a command line. It binds to the local computer. |
| The report set | HTML, Markdown and JSON from the same run, plus the reproducibility record that lets another party retrace the calculation. |
| Your specification | Scoping and authoring the clauses for the documents you enforce, where an existing pack does not already cover them. |
| Onboarding | Installation, verification against schedules you choose, and the acceptance process your organization needs before it relies on anything. |
There is no public download, no self-service checkout, and no per-analysis charge. Software is supplied after the scope and the agreement are settled.
The route
- Look at the output. The worked example is a complete report, abstentions included. No file, no contact, no account.
- Run it on something of yours. Send one export and read the engine's review of your own project. Still free, still no obligation.
- Agree a pilot. Representative schedules, and the acceptance criteria written down before anyone looks at the results. Measure review turnaround and repeated work during the pilot rather than accepting a claim about them.
- Settle the agreement. Licensing scope, permitted use, deliverables, support, security requirements and commercial terms.
- Deploy and verify. Your installation, your verification process, your sign-off.
Step three is the one most vendors skip and the one that decides whether this is worth anything to you.
Before your procurement team asks
Better that you hear this here than find it in a security review.
There is no SOC 2, no ISO 27001, no FedRAMP authorization, no penetration test and no cyber liability insurance to offer. There is no professional certification behind the output. The build has not yet been reproduced on a machine other than the author's, and the evidence page says exactly what has and has not been measured.
Project data stays in your environment. This public website serves generated demonstration files and saved outputs; it does not receive or analyse confidential schedule uploads. Where you choose to send a file for step two, it is handled as described on that page and under privacy.
Organization-wide hosting, authentication, access control and operational support are things to agree and verify for your deployment. A local browser service is not, by itself, a production multi-user platform.
What you are not buying
Schedule Forensics supplies computations and evidence for a qualified reviewer. It does not provide an expert opinion, approve a schedule, or determine entitlement. Computed dates and floats should be reconciled against the source scheduling application before reliance. Read the limitations before the contract, not after.
Speak with Charley
Email charley@scheduleforensics.com with your organization, your intended use, and the procurement route you expect to use. No project file is needed for the first conversation.
For a project in dispute, or where a dispute is anticipated, coordinate any proposed file sharing through your counsel of record. Contact and privacy details.
Source: web/pages/pricing.md. Source commit date: 2026-09-11.