Role
Management System Manager
Learn to run a system people actually use, get help building it, and have it audited
A system the organisation runs, not just maintains
Managers carry the system in daily work: scope and accountability, risk ownership, control design, review and improvement. It is management work first and a standard second.
Overview
A manager owns what they cannot command
A manager's week is mostly other people's work: asking for evidence somebody sees as bureaucracy, explaining to the person a control slows down why it is there, and keeping current a system nobody else has time to think about. What comes with it is a view of the organisation almost nobody else has, because the system cuts across every function that owns a piece of it.
The frustration is authority. A manager owns the system and rarely commands the people who run it, so everything turns on being persuasive while a process is still being designed rather than after it has shipped. A system that holds pays that back: a control that catches something before it costs anything, an improvement that survives the person who proposed it, and an audit that finds little because there is little to find.
Professional tracks
Build the capability this role needs
All tracks →Halderstone tracks follow a modular structure. They first establish a strong, role-specific foundation across disciplines, which is then applied to the chosen discipline.
Training modules
Deepen your expertise
All modules →The cross-discipline core is the part every track of this role shares, and the rest applies it to one standard.
Advisory
Build and improve your management system
Learn more →Most of this work is done alongside the people who will carry it afterwards, which is the only way it outlasts the engagement.
The scope no longer fits the organisation
It was drawn to make certification straightforward, and the business has moved since. We work it through with the people who run the processes, so what you end up governing is real and the same audit still passes.
Controls exist and nobody operates them
A treatment decision became a procedure and went to people whose work it does not fit, so they keep working the way that works. We work the control back into the process with the people who operate it.
The system runs on one person
That person is usually you. We help you put in the parts that survive a handover: ownership somebody can act on, evidence that is a by-product of the work, and a review that ends in decisions rather than in a note to revisit it.
Audit
Assess the system you run
Learn more →An audit is worth having only if it could have come out badly. The occasions below are the ones managers bring us in for, and each of them is scoped by discipline, because the criteria live in the standards.
Audit contexts
Readiness before a certification or surveillance audit
Internal audits your own function cannot staff
Areas where your independence would be questioned
Supplier and outsourced-process audits
A review after an incident the system did not catch
Integrated audits across two or more standards
Insights
What we have written on this
All insights →Where do you need support?
A short conversation to understand your current situation and discuss possible next steps.
Other roles
By discipline