Guide/glossary

Reference

Glossary

Definitions for the terms used throughout MOOSH, gathered in one place for quick reference. Each entry links back to the screen where it applies.

A record of every significant action taken on the platform, kept for accountability and troubleshooting.
A first version written by the assistant. It always needs a person to check it before it counts as final.
Results only appear when at least five people are behind them — never a smaller group that could identify someone.
A formal, frozen evidence report proving the work was done properly, ready for leadership or the board.
Auto-approvable control
See: Control library
A library definition allowed to skip the pack click under Tier 3 policy when risk band and rules permit.
Autonomy tier
See: Playbooks
0 console · 1 assisted · 2 orchestrated · 3 conditional auto for standard controls only.
One round of a questionnaire sent out to employees, from launch until it closes.
A reusable platform feature a jurisdiction pack can declare it needs — for example event-driven review or worker risk communication.
A short questionnaire you complete about your own work experience. Your individual answers are private to you.
The exact policy document and version the answer was grounded on.
A fix — something changed in how work happens so a risk is genuinely reduced, not just written about.
Control task email
See: My controls
A transactional message with a deep link to the assigned control — never includes private check-in content.
Corrective action (CAPA)
See: Investigations
The fix put in place after an investigation, plus the plan to stop the same thing happening again.
Decision Pack
See: Dashboard
A playbook-assembled bundle of proposed work waiting for shared-service approve, amend, or reject.
Enough people took part
See: Consultations
A minimum number and mix of attendees is required for a consultation to count as valid.
Exception cockpit
See: Dashboard
The dashboard panel that lists only work needing shared-service judgment — packs, overdue tasks, triggers.
The set of rules and standards the organisation has agreed to follow — for the UK, ISO 45003 plus UK guidance.
Group result
See: Dashboard
A combined answer from several employees. We never show a result unless at least five people are behind it.
A fixed, tested questionnaire — the actual set of questions behind a check-in or campaign.
An international standard for managing psychological health and safety at work.
The country or region whose specific rules apply — each one needs its own local approval before it's treated as active.
How strongly a pack binds practice — for example guidance, model source, or adopted requirement.
A hard block that prevents selecting a commercial instrument until the organisation has cleared the publisher's terms.
How developed and consistent your safety practices are — separate from whether any specific risk currently exists.
Mental Health First Aider — a colleague trained to give first-line, confidential support.
In Brazil, the risk inventory and action plan document required under NR-1 — shown here only as a synthetic concept fixture.
A versioned rule that can start work from a schedule, threshold, or event without a blank-page rebuild.
A versioned, vertical- and regulation-agnostic rule that starts work from a schedule, threshold, or event.
A versioned rule that starts work from a schedule, threshold, or event.
A versioned company policy file kept in a separate, access-controlled corpus — not mixed with anonymous check-in answers.
Ranked list of fixes
See: Control library
Changing the work itself outranks things like extra training — it deals with the cause, not just the symptom.
A team result is only shown once enough people have answered. Below that, the screen simply shows nothing, on purpose.
Required capability
See: Framework packs
A generic platform feature a pack must have enabled before it can be activated.
Resilience score
See: Dashboard
A single 0–100 number summarising how healthy things look across the whole organisation right now.
Response-time target
See: Review queue
How quickly a suggestion needs a decision — the most serious risks must be reviewed within 24 hours.
How long different kinds of data are kept before being deleted, set by the organisation within allowed limits.
An event or statutory clock that requires a targeted re-assessment, rather than waiting for a routine campaign cycle.
Risk acceptance
See: Board portal
A formal decision that a risk which can't be reduced further right now is tolerable for a stated period, with reasons recorded.
Risk left after a fix
See: Risk register
How much risk remains once a fix has been put in place — rarely zero, which is why review dates matter.
An early hint that something might be wrong — not yet a confirmed, written-up risk.
Standard-control auto-approve
See: Decision packs
Tier-3 path where a library control flagged auto_approvable may apply without a pack click when band and policy allow.
A well-known, voluntary way of identifying what you're naturally good at — separate from any work performance measure.
Conditional auto path for standard library controls only — never employment or investigation decisions.
Transactional email
See: Organisation admin
Action and notification messages (packs, tasks) without open/click tracking and without HIGHEST content in the body.
Quickly deciding how urgent a report is and what needs to happen with it first — always human-confirmed for severity-dependent routing.