Management Accountability & Decision Rights
Management accountability is the named allocation of decision rights: who may approve, who must be consulted, who can stop work, and where a disagreement goes when two functions cannot resolve it. It lives in delegations, forum terms of reference and escalation paths rather than in an org chart. When a batch is released or a study is closed, someone with defined authority made that call against defined criteria — and the absence of that clarity is why so many investigations end at an assumption.
What an explainer is not
A topic explainer is SPEQ’s synthesis of what a practice involves, cited to the standards that govern it. It does not reproduce their text, and it does not determine which of them apply to your product or process.
[ POSITION IN THE FRAMEWORK ]
7 DIMENSIONS · 22 LINKSRegulations assign responsibility to people, not to committees: the practical test is whether a named individual can be produced for a specific decision, and whether they could have said no.
06 · QUALITY MATURITY — MANAGEMENT ACCOUNTABILITY & DECISION RIGHTS, REACTIVE TO ADAPTIVE
Decisions emerge from meetings. Asked who decided something, the honest answer is that the group did.
An organisation chart and job descriptions exist, but they describe reporting lines rather than which decisions each role may take alone.
Decision rights are explicit for the decisions that matter — release, stop, escalate, accept risk — and each names a person rather than a function.
The independence of the quality decision is structural: the person who can stop production does not report to the person whose numbers stopping it damages.
Accountability is visible in behaviour rather than documents — decisions are made at the level that holds the knowledge, and unwelcome ones are made and survive.
SPEQ’s shared five-stage progression, labelled synthesis — not the FDA QMM rating scale. Where does your organization sit? Score your quality system →
07 · REGULATORY & EVIDENCE
GOVERNING STANDARDS · 5
Derived from the 5 standards SPEQ maps to this subject, across 5 regulatory bodies: FDA, EMA, ICH, ISO, PIC/S.
RECORDS & OBJECTIVE EVIDENCE
- Documented decision rights for release, rejection, stop and risk acceptance
- Reporting lines showing the independence of the quality decision
- Delegation records, including how absence is covered
- Named accountability against each element of the quality system
- Records of decisions where the accountable person overruled a commercial preference
COMMON INSPECTION FINDINGS
- Decisions attributed to a committee with no individual accountable for them
- A quality decision-maker reporting to the function whose output they judge
- Delegation exercised informally, so the person deciding is not the person named
- Job descriptions describing duties but never authority to stop or refuse
- No instance of an accountable person exercising a refusal, on a system that requires one
What the quality-system frameworks actually require
ICH Q10 places management responsibility at the front of the pharmaceutical quality system, not as a preamble but as a set of obligations: leadership must establish and communicate the quality policy, define roles and responsibilities and authorities, provide resources, and conduct management review with defined inputs and outputs. ISO 9001 reaches the same ground through its leadership clause, and PIC/S PE 009 makes senior management responsible for the quality system with the pharmaceutical quality system explicitly requiring participation from management.
These are usually satisfied on paper by an organisation chart and a signed policy. Neither answers the operative question, which is not who reports to whom but who is permitted to decide what — and specifically who is permitted to decide that something unresolved may proceed.
The authority that matters is the authority to stop
Approval authority is well defined in most regulated organisations. Stop authority usually is not. Who can halt a shipment, hold a batch, suspend a study, or refuse a release when they are not the person accountable for the schedule? Where that authority is undefined or is held only at a level too senior to be exercised routinely, the practical answer is that nobody stops anything, and the concern gets raised as a comment rather than as a hold.
This is the same ground the maturity model scores through observable behaviour rather than felt safety: not whether people say they could stop the line, but whether anyone has, and what happened to them afterwards. An organisation with a documented stop authority nobody has ever used has a document, not a control.
Escalation paths that terminate somewhere
Cross-functional disagreement is normal and healthy; what matters is whether it has a defined route to resolution. Where quality and operations disagree about a disposition, the escalation path should name the forum or the individual who decides, and that decision should be recorded with its rationale. Where the path is undefined, disagreements are resolved by persistence, seniority or fatigue, and no record exists of what was decided or why.
The tell is an investigation in which two functions each believed the other had accepted the risk. That is not a communication failure; it is an escalation path that terminated in a meeting rather than in a decision with a named owner.
SPEQ interpretation — accountability is tested by what was deferred
Management review typically examines what happened: metrics, deviations, complaints, audit findings. The more revealing question is what was deferred, and who accepted the risk of deferring it. A CAPA extended for the fourth time, a validation gap carried for two years, an unsupported system left in production — each is an accepted risk, and each was accepted by someone, usually without that being framed as an acceptance.
SPEQ’s view is that a standing review of open acceptances — what is being carried, by whom, since when, and against what compensating control — is the highest-value governance artefact an organisation can maintain, and one of the rarest. It makes visible the decisions that were never announced as decisions, which is where accountability actually lives.
FREQUENTLY ASKED
Is an organisation chart evidence of defined responsibilities?
No. A chart shows reporting lines; ICH Q10 and ISO 9001 require defined roles, responsibilities and authorities — which is a statement of who may decide what. The operative question a chart cannot answer is who is permitted to decide that something unresolved may proceed.
What is stop authority and why is it usually weak?
The authority to halt a shipment, hold a batch, suspend a study or refuse a release without being accountable for the schedule. It is weak because it is often undefined, or held only at a level too senior to use routinely — so concerns get raised as comments rather than holds. A documented stop authority nobody has ever exercised is a document, not a control.
What does a healthy escalation path look like?
It names the forum or individual who decides when two functions disagree, and the decision is recorded with its rationale. The failure signature is an investigation in which each function believed the other had accepted the risk — which means the path terminated in a meeting rather than in a decision with an owner.
What should management review examine that it usually does not?
What was deferred and who accepted the risk. Extended CAPAs, carried validation gaps and unsupported systems in production are all accepted risks, accepted by someone, usually without being framed as acceptances. A standing review of open acceptances — what, by whom, since when, against what compensating control — makes those decisions visible.