Coverage & Continuity Toolkit

List the recurring jobs your statistical-programming or biometrics team runs (who owns each one, when it runs, what it reads and writes, how critical it is). Pick a scenario. The page builds a coverage matrix, flags uncovered and single-owner risks, writes a handoff checklist for every job, and gives you a handoff packet to print or download. It runs on the same rules as the On-Leave Coverage Playbook: service accounts, a named backup, heartbeat plus watchdog, and “no news is never all clear.”

What are you covering for?

Person

Cover

From

Until

Team or programme

Notes for the packet

Your data

Everything you enter stays in this browser (localStorage). Nothing is uploaded; the page cannot make network requests. To keep a copy, move it to another machine, or share it with a colleague, export a JSON file. CSV import and export use the same columns as continuity_jobs_template.csv.

A CSV that has an id column but no name column is treated as a status update: it refreshes last_run and last_status on matching jobs and leaves everything else alone. tm_inventory.sh writes that file from the monitors’ heartbeat files.

Backups, inputs and outputs take several values; separate them with semicolons when importing CSV.

P primary owner B named backup C scenario cover (not a trained backup) ▒ out during this scenario

Rows are coloured by the job’s worst risk under the current scenario. “People” counts the distinct people who can run the job; that number is the job’s bus factor.

Risk register

What if each person were out?

Jobs that nobody else could run if this one person were unavailable tomorrow. Unowned jobs are uncovered whoever is out, so they are listed separately in the register above.