Safety data sheets, pyrotechnics, access equipment, tickets and stores — what you hold, what it is, and what is out of date.
| Substance | CAS | Stock quantity | Location | Hazards | Routes | Gloves | Risk | Last ordered |
|---|
Nothing in the library yet. Press Safety data sheets under Add and drop some in.
Worst first: failed, then overdue, then never done. The chips narrow each other, so Overdue and Ladder together gives overdue ladders. Press a lit one again to drop it.
A store is somewhere things are kept — the tape store, the ironmongery store. Open one to see what is in it and add to it. Each thing inside keeps its own purchase history and its own log.
What should be in each place, and what has gone from it. "Here now" is what should be there less what has been recorded lost or broken in that store since the last count. A place that is a venue and room rather than a store is not tracked that closely, so it only shows whether the total is short.
Everything the tool has changed, newest first — sheets read, revisions recorded, hazard data corrected, orders, templates and every document produced. Each entry says who did it, when, and what changed. Entries are only ever added: nothing here is rewritten when the thing it describes is edited or deleted.
The things you set up once and then stop thinking about. Nothing here is part of a day's work, which is why it is out of the way of the tabs that are.
Whose tool this is
Named in the header of every page and on the start page, so a screen or a printout is obviously the property of the place it belongs to.
Your university's or college's own logo, shown in the top right of every page. It sits beside the tool's mark, not instead of it, so it is clear whose department this is and what the software is.
The first-time set-up asked for all of this; it can be run again from here to go through the whole thing — registers, start page, logo, name and PIN — in order.
How it looks
Dark is easier on the eyes in a dimly lit control room or a get-out. Match my Mac follows the system setting, so it turns dark when everything else does.
Hazard pictograms and the chemical, pyrotechnic and venue badges keep their colours in both, because those colours mean something.
Which tabs show along the top. Hiding one turns nothing off — what is behind it still works, still holds everything it held, and comes straight back if you show it again or follow a link into it. Settings always shows, and at least one other tab has to.
Showing a tab leaves you where you are rather than jumping you onto it, so you can set all six and then go.
Where you land when you open the tool without asking for a particular page. Hide that tab later and the first one showing is used instead, until you bring it back.
What the registers are built on
The buildings you work in, each with a colour. That colour becomes the badge on every tool row, and the rooms you add under a venue are what the Tools list filters by. Cupboard lists are kept if a venue goes — they simply stop naming one.
Tools and Tape are two settings of the same register. Add a kind of your own — radios, keys, lamps — and choose what it does from the behaviours the tool already has: kept in one store or spread across cupboards with a number expected in each, chased below a minimum or when a cupboard is short, lent out or not, filed under words read off the name. Each kind can have a tab of its own. No new code, nothing asked of Claude.
What kind of place each storage location is — a fire-resisting flammables cabinet, a lockable COSHH cabinet, an acids cabinet, the pyro store, a general shelf — and the room it stands in. The kind is the only thing recorded here. From it, and from the sheets kept there, the tool works out what a storage rule objects to: an oxidiser beside a flammable, an alkali in the acids cabinet, flammable liquids on an open shelf, and a room holding more flammable liquid than HSG51 allows in a workroom (50 litres of highly flammable, 250 of flammable, in a fire-resisting cabinet). The warnings appear on the cupboard poster, the phone page its code opens, the cupboard walk and What needs doing.
Who signs, and what is recorded
Everyone logs in with a name and a four-digit PIN; without logging in the tool can be read but not changed. Four roles: an administrator does everything, a technician adds, edits and removes records but cannot touch the change log, a regular user adds and edits but removes nothing, and a viewer only looks. Every guarded action asks for your own PIN and checks your role at the same time.
Risk assessments are signed in the tool: the assessor with their own signature and PIN when the document is generated, and whoever approves it from the nudge that appears under their account. The signed copy is kept beside the document as issued.
Everything the tool has changed, newest first, and who changed it. Entries are only ever added — nothing is rewritten when the thing it describes is edited or deleted.
What leaves the tool
Pages that open ready to print. What needs doing gathers everything the registers are waiting on — inspections, expiring tickets, missing sheets, ageing sheets, low stock — into one list. The emergency pack is what is held and where, for the fire service or an assessor. QR labels open each record's own card when scanned on the internal network. The offline copy is one zip of every current safety data sheet and the registers as spreadsheets — for a USB stick or the fire box, nothing in it needs this tool or a login.
The order list is everything short of its cupboard
list or minimum, with the last supplier, catalogue number and price beside
each line. The tag inserts fit a ladder-tag holder and print the next
inspection date. The store record is last month's pyrotechnic movements
with a running net explosive content; add ?since=2026-01-01&until=2026-03-31
to the address for another period. The binder is every sheet in one
indexed PDF, grouped by cupboard, with anything that could not be
included named on its index; pick a cupboard to bind that one alone.
Lets the tool put files into a Teams folder — the one central health and safety look in for evidence. It signs in as you, on Microsoft's own page, so it can never reach anything you could not open yourself, and it only ever acts when you press a button.
Where the tool writes to, and the mail server it sends through. Neither is required: with no server nothing is ever emailed. What it sends is narrow — the weekly digest below, and a test message — and every send is in the change log.
The digest is the page a technician prints on a Monday. Sent on a set day each week — posted to the Teams folder above, emailed to the notification address, or both, whichever is set up — it reaches the people who never open the register. A week the Mac is asleep at the time is skipped rather than caught up — a Monday digest arriving on Tuesday would be read as Tuesday's.
The tool itself
The tool keeps itself up to date from its own source repository. Checking only looks; nothing changes until you install, and installing never touches the records — they live in their own folder, which updates leave alone.