Inquest
Inquest is the court list and public case record of a coroner's court, built as the document it actually is rather than as a marketing page with a table bolted underneath. The fold is the cause list itself: every hearing listed for the week with its case reference, the deceased and their age, the hearing type, the time, the court room, the coroner sitting and the interested persons due to attend — set in ruled columns with the case references running down a marginal column in the manner of a statute's marginal notes. Behind the list sits the whole statutory journey. Deaths reported in are partitioned by their source — hospital, GP, police, care home, registrar, ambulance — each with the decision that followed: no investigation required, post-mortem directed, or an investigation opened. Directions and evidence tracks the post-mortem and toxicology instructions, the pathologist assigned and the turnaround against what is expected. A drawn statutory timeline plate opens one case out as an inline-SVG track from the date reported through post-mortem, opening, pre-inquest review and final hearing to conclusion, with the six-month statutory expectation drawn as a vertical rule across the track so a reader can see at a glance which steps crossed it. Conclusions are partitioned by type — natural causes, accident, suicide, misadventure, industrial disease, open, narrative, unlawful killing — and the Prevention of Future Deaths section records each report issued, the organisation it went to, the statutory 56-day response deadline, and what that organisation reported doing about it. A coroner's officer signs in to their own case view: the cases assigned to them, the directions outstanding, the families awaiting contact and their next listed hearing. The visual language is HMSO official-publication printing — the typography of government stationery-office documents and court cause lists. Ink on dry oyster-grey paper, authority carried entirely by hairline rules, wide-tracked small capitals and disciplined columns, with a single reserved maroon spot used only for the court's own marks and a drawn seal as the page's one ornament. Newsreader carries the document voice, Public Sans the interface and small capitals, Spline Sans Mono the case references, times and elapsed-day counts. There is no hero image, no card grid and no gradient anywhere: the record is the design. It is a ready skeleton for any organisation whose product is a public register with a statutory clock running through it — tribunals and hearing lists, licensing and planning committees, regulators publishing determinations, ombudsman schemes, professional conduct panels, and any body that must show both what it has listed and what it concluded. Every figure on the page is derived from one data layer, so the totals, counts and fractions cannot drift from the rows they summarise.
Did you know? Every template can become any business.
What's inside
Frequently asked questions
What is the Inquest template?
Inquest is the court list and public case record of a coroner's court, built as the document it actually is rather than as a marketing page with a table bolted underneath. The fold is the cause list itself: every hearing listed for the week with its case reference, the deceased and their age, the hearing type, the time, the court room, the coroner sitting and the interested persons due to attend — set in ruled columns with the case references running down a marginal column in the manner of a statute's marginal notes. Behind the list sits the whole statutory journey. Deaths reported in are partitioned by their source — hospital, GP, police, care home, registrar, ambulance — each with the decision that followed: no investigation required, post-mortem directed, or an investigation opened. Directions and evidence tracks the post-mortem and toxicology instructions, the pathologist assigned and the turnaround against what is expected. A drawn statutory timeline plate opens one case out as an inline-SVG track from the date reported through post-mortem, opening, pre-inquest review and final hearing to conclusion, with the six-month statutory expectation drawn as a vertical rule across the track so a reader can see at a glance which steps crossed it. Conclusions are partitioned by type — natural causes, accident, suicide, misadventure, industrial disease, open, narrative, unlawful killing — and the Prevention of Future Deaths section records each report issued, the organisation it went to, the statutory 56-day response deadline, and what that organisation reported doing about it. A coroner's officer signs in to their own case view: the cases assigned to them, the directions outstanding, the families awaiting contact and their next listed hearing. The visual language is HMSO official-publication printing — the typography of government stationery-office documents and court cause lists. Ink on dry oyster-grey paper, authority carried entirely by hairline rules, wide-tracked small capitals and disciplined columns, with a single reserved maroon spot used only for the court's own marks and a drawn seal as the page's one ornament. Newsreader carries the document voice, Public Sans the interface and small capitals, Spline Sans Mono the case references, times and elapsed-day counts. There is no hero image, no card grid and no gradient anywhere: the record is the design. It is a ready skeleton for any organisation whose product is a public register with a statutory clock running through it — tribunals and hearing lists, licensing and planning committees, regulators publishing determinations, ombudsman schemes, professional conduct panels, and any body that must show both what it has listed and what it concluded. Every figure on the page is derived from one data layer, so the totals, counts and fractions cannot drift from the rows they summarise.
Who is the Inquest template for?
Use it as a starting point for social teams and creators exploring a Inquest app. Check the preview and included features against your workflow before you remix.
How long does it take to build an app with the Inquest template?
Timing depends on your changes and setup. Review the generated app, connect any required services, and test the core workflow before sharing it.
Do I need to code to use the Inquest template?
You can start with plain-language instructions. Complex behavior, custom integrations, and production troubleshooting may need technical help.
How much does the Inquest template cost?
This template has no separate template purchase price. Building and AI edits require builder access and available credits. Hosting and connected services may have their own costs; check current pricing and provider terms.
Can I customize the Inquest template?
You can request changes to the design and behavior. Review each change, complete any connection setup, and test forms, permissions, and payments that your app uses.
Review current pricing and the template inspection guide before you start.
Related templates
Make this template your starting point.
Inspect the preview, plan your changes, and test the workflow before you share it.
Use this template