Records built to outlast the vendor.
Most public-facing data dies twice — once when the funding runs out, and again when the platform it was built on shuts down, gets acquired, or stops being maintained. Prior Signal builds records that survive both: verified against the source, packaged to run without a server, and citable for as long as anyone keeps the file.
The discipline.
Verified first
Every figure is checked against the primary source before design work begins. A mismatch stops the build — it is never designed around.
Zero dependencies
No CDN calls, no third-party scripts, no build toolchain required to open it. What you receive is what runs, indefinitely.
Single-file portable
The deliverable is one file. It can be emailed, archived, or mirrored without asking anyone’s permission.
Accessible by default
WCAG 2.1 AA, keyboard- and screen-reader-tested, colorblind-safe palettes. A build requirement, not a retrofit.
Documented
Sourcing, suppression logic, and derived metrics are written down, so the record can be checked by someone who was not in the room when it was built.
A record that only works while the bill gets paid isn’t a record.
A dataset that depends on a CMS subscription staying current, a framework staying supported, or a hosting bill staying paid is a liability with a due date. Organizations that need a figure to hold up in five years, in an audit, or in front of a tribunal need it built differently from the start.
This discipline is built into every Prior Signal data engagement. It matters most for organizations publishing figures that need to survive scrutiny for years — unions and associations with funding-dependent research, regulators and public bodies, and any organization publishing data it may need to defend long after the project budget is closed.
Common questions.
Why would a record need to be “durable”?
- Most public-facing data depends on a live server, a hosting bill, or a vendor that stays in business. When any of those stop, the record disappears with them. A durable record is built to keep working after the engagement, the funding, or the platform is gone.
Does this mean no database at all?
- For the record itself, yes — the deliverable is a self-contained file with the data inlined, not a live application dependent on a server or a subscription. It can be opened, archived, or mirrored indefinitely without asking anyone’s permission.
Does a static, dependency-free build limit what the record can do?
- No. It can still be fully interactive — charts, filters, search — built in vanilla JavaScript with no runtime network calls and no third-party scripts. What it gives up is fragility, not capability.
Is this only for large datasets?
- No. The discipline applies any time a record needs to survive scrutiny for years — a small evidence packet has the same requirement as a 98,010-row dataset.
Built and proven on a live, public dataset.
98,010 U.S. schools, two years of federal civil-rights data, delivered as a single ~820KB file with no server or network dependency.