A four-line internal memo announces that the accountable manager will change on the first of the month. In the hangar, nobody looks up: the name printed at the top of the exposition has never kept an aircraft on the ground. Yet it is the only signature in the organisation that commits money and compliance at the same time, and its transfer quietly reopens every trade-off everyone thought was settled.
What the function covers, verb by verb
The texts governing approved organisations — air transport operators, maintenance organisations, continuing airworthiness management organisations, training organisations — all ask for the same thing, in neighbouring words: one person, and one only, holding the authority within the company necessary to ensure that all activities can be financed and carried out in accordance with the applicable requirements. These two verbs are the whole scheme, and it is the first one that surprises those discovering the subject.
The second, carrying out, is a matter of technical competence. It can be delegated, and indeed must be delegated, to nominated postholders who know the trade: ground operations, flight operations, maintenance, crew training, the management system. The first cannot be delegated, because it presupposes effective access to the budget. The rule learned the lesson from a pattern observed everywhere: a safety function burdened with responsibility but with no spending power at all, producing reports that no one is obliged to fund. By attaching regulatory accountability to whoever holds the purse strings, the text removes the usual escape route — « agreed in principle, but it’s not my budget. »
One point needs to be precise, since everyday conversation blurs it. The approval, certificate or authorisation is issued to the organisation, not to the person. The accountable manager does not hold a personal title, and their departure does not automatically cancel anything. But the supervisory authority does not deal with a legal entity: it addresses a named individual, whom it has accepted after examining their real authority within the company and their understanding of the framework they are signing up to. An accountable manager who cannot commit an expense without referring to an absent shareholder does not meet the condition, even if their title suggests otherwise.
Another useful distinction: the function does not require technical competence in the domain. An accountable manager does not need to know how to certify a return to service, nor to hold a type rating. What they must possess is the authority to arbitrate and sufficient knowledge of their obligations not to sign blindly. That does not make it an honorary post — quite the opposite: it is precisely because they do not judge the technical side that they depend entirely on the quality of what is reported up to them.
The accountable manager is the only person who can both approve spending and ensure compliance. They don’t need technical expertise, but they must have real authority to make decisions and understand the rules. Their signature means the company promises to follow all safety and operational requirements.
At a small maintenance organisation, the new accountable manager (a finance director) reduces the budget for certifying staff. Six months later, a routine audit finds deferred defects piling up because there aren’t enough qualified inspectors. The authority traces this back to the budget decision, not just the technical oversight.
What the signature actually commits
Three categories of documents carry the accountable manager’s signature, and each produces a different effect.

The first is the safety policy statement. It is seen posted in corridors and read as a profession of faith; that is a misjudgement. In audit, it serves as a benchmark: the auditor compares what the text promises — resources allocated, a just culture, priority in the event of conflicting objectives — against what the year’s decisions show. An ambitious policy signed by someone who has frozen recruitment of certifying staff is not a neutral document; it is evidence against the organisation, supplied by the organisation itself.
The second is the exposition: the operations manual, the maintenance organisation exposition, the continuing airworthiness management exposition, the training organisation manual. The signature at the top constitutes a commitment that the organisation operates as the document describes and will continue to do so. It is not an approval of content in the technical sense — the manager has not reviewed the de-icing procedures — but a declaration that the resources promised match the procedures described.
The third is more diffuse and is the one people forget: acceptance acts. Accepting a residual risk in the risk register, validating a corrective action plan whose deadline runs past the quarter, arbitrating a conflict between a production requirement and a compliance requirement, chairing the safety review. These are not administrative formalities: they are the written trace of who decided, and it is this trace that gets pulled out two years later.
| Subject | What is entrusted to a nominated postholder | What remains on the accountable manager’s signature |
|---|---|---|
| Technical competence in the domain | All of it: methods, qualifications, control of work performed | Nothing, except choosing the person and verifying their real authority |
| Spending commitment | A delegated envelope, with a written threshold and scope | The trade-off as soon as the envelope no longer suffices to hold the declared standard |
| Safety policy and just culture | Implementation, promotion, training | The text, its signature, its republication after any change of organisation |
| Acceptance of a residual risk | The analysis, the proposal of measures, the scoring | The decision to accept, refuse or reduce the scope of activity |
| Relationship with the authority | Routine technical exchanges, response to minor findings | Liaison on major findings and on any change to the management system |
| Accountability to the authority | No share at all: it cannot be shared | The whole of it, including for what has been delegated |
The trade-off changes hands, the constraint stays the same
Here is the point that a change of postholder lays bare. No accountable manager ever decides « less safety. » They decide on a hangar slot pushed back a month, an overtime envelope trimmed back to last year’s level, a spares stock recalibrated to average consumption rather than to peak, a recurrent training session grouped into the following quarter to fill the class, a certifying staff post left unfilled during the low season. Each of these decisions can be defended on its own before any committee. It is their sum, over two or three quarters, that shifts the operating margin.
The new postholder arrives with no memory of these trade-offs. What their predecessor had refused to cut — often because they had seen, ten years earlier, what cutting it cost — becomes just another line in a table again. The safety case that had justified keeping two certifying staff on the night shift usually exists nowhere in writing: it lived in the head of someone who is no longer there. That is the first reason why a change of accountable manager is not neutral, and it has nothing to do with regulation.
The second reason is timing. Safety indicators react to resourcing decisions with a considerable delay. Leading indicators move first — reporting rate, number of open deferred defects, minimum equipment list items in progress, training deadlines nearing their limit, volume of overtime — but they are not in the financial dashboards, and nobody looks at them the month the decision is made.
Practical consequence for anyone holding a safety or compliance function: at the moment of handover, the case has to be rebuilt in the new decision-maker’s language. A manager coming from finance or another industrial sector does not hear « safety margin »; they hear delayed departure, unscheduled removal, grounding, a major-level finding, insurance premium, loss of a client under audit. Translating is not betraying: it is the only way to get a technical requirement into an allocation decision. A three-page case, costed in operational consequences, weighs infinitely more than a reminder of the regulatory obligation — which the new postholder, in any case, has not yet internalised.
The transition window, where the real gaps hide
A change of accountable manager falls, in every approved-organisation framework, under the regime of changes affecting the management system: they cannot remain internal. Depending on the reference framework and on what the organisation’s approved procedure sets out, it is either a change to be notified to the authority or a change that must be accepted before it becomes effective. The authority may request an interview, examine the candidate’s real authority within the company, and verify that they have understood what they are signing up to. It is not a technical examination; it is a check of effectiveness.
Between the internal decision and the distribution of the revised exposition, several weeks commonly pass. That interval is the real subject. Who signs off acceptance of a residual risk during that period? Who responds to a finding whose deadline falls precisely then? Who chairs the safety review that has been scheduled for six months? The answer must be found in the manual, in the chapter on deputising arrangements, not built on the spot when the question arises.
The trap. The exposition that still carries, six months later, the name and signature of the former postholder. The finding that results is almost guaranteed, and it usually stays minor; the real problem lies elsewhere. Every risk acceptance, every corrective action plan validated during that interval rests on an authority the document attaches to no one. A more serious variant: an « acting » manager installed internally without the authority having been informed. The organisation is then working outside the management system it was approved for, and discovers this at the occasion of an event, when someone asks who decided what.
Three configurations, three predictable drifts
How a change plays out on the ground depends less on the person than on the position they hold within the company. Three configurations recur, with distinct symptoms.
| Configuration | Where the trade-off is actually made | Typical drift | Safeguard to write into the exposition |
|---|---|---|---|
| Group executive, external to the site | In the executive committee, at a distance from operations | Safety enters a financial dashboard and loses its unit of measure there; the safety review is held without them, chaired by standing delegation | Review calendar fixed in the manual, minutes signed by their own hand, leading indicators presented at the same rank as production indicators |
| Site director, also nominated postholder for a domain | Immediately, on the ground, with no intermediate body | Judge and party: they accept the deviations of the activity they manage, and compliance monitoring loses its de facto independence | Written reporting line for compliance monitoring, cross or outsourced audits on their own domain, named traceability of acceptances |
| Owner-operator of a small structure | Blended with day-to-day cash management | Deferral becomes the rule: spares ordered one at a time, training deadlines grouped as late as possible, tooling calibration left at the limit | A safety envelope identified in the budget, a training and periodic-task schedule kept out of routine trade-offs |
None of these configurations is irregular in itself, and the texts explicitly allow combined roles in small structures. What sets them apart is the nature of the safeguard that must be written to offset their particular weakness. An organisation that changes configuration at the same time as its postholder — the frequent case of an acquisition, where a site director present for twenty years is replaced by a group executive — stacks the two transitions and cannot get away with simply changing a name on a cover page.
The right reflex. In the days following the announcement, pull from the manual the three pages that carry a signature — safety policy, exposition cover page, responsibilities chapter — and re-read the deputising clause. Then ask in writing for the date of the first safety review chaired by the new postholder. The written request creates a trace: if the answer is slow in coming, it documents by itself the state of the management system during the transition, and that trace is worth more than the memory of corridor conversations.
What staff can read in the first few months
The useful signals are not those of the arrival speech. They are structural and can be read without being invited into the executive committee.
- Where compliance monitoring reports. If it is moved under an operational line « to simplify the org chart, » that is a substantive regression, whatever the intention. The function must be able to write a finding about the activity of the person it reports to hierarchically — which never happens.
- Republication of the just culture policy. A text not re-signed after a change of postholder no longer commits anyone, and staff understand this very quickly. The voluntary reporting rate is one of the first indicators to show it: it generally dips before the production indicators do.
- Handling of resource requests. Not the answer — a reasoned refusal is still an answer — but the existence of a dated response. A channel that stops answering is a channel that has stopped existing.
- Physical presence at the boards. A safety review chairmanship permanently delegated indicates that the trade-off is being made elsewhere, and that the risk register no longer reaches the person who can fund it.
- Budget identification. A « safety » line visible in the budget, distinct from production, survives difficult years. A safety expense buried in overheads disappears at the first tight trade-off.
How far staff can legitimately document these signals comes up regularly in exchanges between nominated postholders on the FL330 forums. The answer fits in one sentence: everything that goes through the reporting system and the risk register is, by construction, normal use of the management system, not a challenge to management.
What to check in your own documentation
Three checks require no special tool and prove useful well beyond a handover. The first: identify every page in your manuals that names a person rather than a function. Each one is a mandatory revision at every personnel change, and that is where oversights hide. An exposition written in terms of functions needs only one page of nominative update.
The second: read the deputising clause as it is actually written, not as you assume it is. Many expositions provide a deputy for nominated postholders and stay silent on the accountable manager, on the implicit assumption that they are never absent. The third: check what level can accept a residual risk under your own procedure. If the manual sets no threshold, everything escalates to the accountable manager, including what should never reach them — and the system clogs up.
One grey area remains, and it would be dishonest to hide it: the boundary between an internal reorganisation with no regulatory effect and a change to the management system that requires the authority’s involvement is judged case by case. A change in the hierarchical reporting line of the compliance function, with no change of person, can fall into the second category. When in doubt, the question put to the supervising inspector costs less than the finding.
For anyone preparing for a nominated postholder position, or considering the function itself, the lesson is clear: the acceptance interview does not only cover the technical domain, it covers the ability to commit resources and knowledge of the obligations attached to the signature. It is the least-worked axis in preparation, and the one on which candidates are most often caught off guard; FL330’s preparation courses for nominated functions now make it a stand-alone module.
This text describes a mechanism and replaces no reference framework: the regulation applicable to your organisation, the decisions of your supervisory authority and the operator’s approved documentation prevail over anything written here.
Questions fréquentes
Does an accountable manager need to be a pilot, a mechanic or an instructor?
No. The function does not require technical competence in the domain, which falls to nominated postholders. What it requires is effective authority to commit the organisation’s resources and sufficient knowledge of the regulatory framework to understand what the signature commits to. The supervisory authority checks these two points at acceptance, not the ability to certify a return to service.
Can the accountable manager function be combined with that of a nominated postholder?
The texts allow combined roles in small organisations, subject to the supervisory authority’s agreement. The limit is structural: the compliance monitoring function must retain its independence from the activities it controls. When the accountable manager also runs the audited domain, this must be offset by cross or outsourced audits and by named traceability of acceptances.
What happens between the former postholder's departure and the new one's acceptance?
The organisation cannot be left without an identified accountable manager. The normal solution is the deputising clause set out in the exposition, together with notification of the supervisory authority. If your manual provides a deputy for nominated postholders but stays silent on the accountable manager, that is a point to fix before the next move, not during it.
Does a change of accountable manager suspend the organisation's approval?
No, the approval is issued to the organisation and does not lapse with a person’s departure. It is, however, a change to the management system: depending on the reference framework and the organisation’s approved procedure, it must be notified to the authority or accepted by it before becoming effective. Failure to notify is the classic finding on this point.
Can an accountable manager refuse an expense presented as necessary for safety?
They can arbitrate between priorities, refuse a solution and ask for a cheaper one: that is precisely their role. What they cannot do is let the organisation operate outside what its approved documentation describes. If resources no longer allow the declared standard to be held, the adjustment variable is the scope of activity, never the level of requirement.
How can a need for resources be argued to a new postholder who comes from another sector?
Through the channels of the management system, that is, the risk register and the safety review, with a dated written trace. The case must be translated into measurable operational consequences — grounding, delay, unscheduled removal, major finding — rather than into a reminder of the obligation. A costed two- or three-page case weighs more than a regulatory reference the counterpart has not yet internalised.

Leave a Reply
You must be logged in to post a comment.