The appointment has been accepted, the office has stood empty for several weeks, and the drawer holds a dozen open findings. Three fall due within the month. Two were declared closed by the predecessor without any effectiveness check having been recorded. Nobody lied: the clock simply kept running while the post was vacant. A nominated person does not inherit a scope of responsibility, they inherit a countdown that is already under way, and day one is for taking stock of it rather than discovering it one deadline at a time, always a week late.
The deadline belongs to the finding, not to the person
Deadlines keep running during vacancies. It is tempting to assume that taking up the post opens a fresh page. It opens nothing. A finding is notified to the approved organisation, not to the holder of a post: the implementation period runs from the date of notification, and a change of nominated person is not among the grounds that suspend it. The authority accepts a person — competence file, interview, acceptance form — but it does not reopen any deadline on that occasion. The successor therefore takes over a period shortened by everything the vacancy and the handover have consumed.
Corrective action plans bind the organisation. What does transfer, on the other hand, is a signature. An accepted corrective action plan binds the organisation, and in practice the person responsible for carrying it out. The successor becomes its guarantor without having written it, sometimes without sharing its analysis. If they judge the plan unrealistic — a deadline built on a recruitment that never happened, an action assigned to a department whose remit has changed, an IT resource pushed back —, the time to say so is the first week, not the last. A request for postponement submitted a fortnight before the deadline reads as a failure to follow up; the same request submitted early, backed by a written reassessment and by a mitigation measure already in place, is open to discussion. Extending an implementation period remains bounded by the regulation and conditional on a plan judged satisfactory: it is never a given, it is negotiated on facts.
The clock on a finding doesn’t stop when the post is vacant. You inherit deadlines as they are, not reset to zero. If the plan to fix a problem is unrealistic, you must speak up early with evidence, not wait until the last minute.
An AOC holder takes over a post with two Level 2 findings. One has 30 days left, the other 60. The first requires a simple procedure update, while the second involves retraining 50 staff. The successor must prioritise the 30-day deadline, even if it’s easier, to avoid missing it.
The registers to open before meeting anyone
Start with documents, not people. The inventory is done on documents, alone, before the courtesy meetings. The meetings will come afterwards, and they will be more useful if you already know what you are trying to verify. Eight registers are enough to map the real state of the scope.
- open external findings, with their notification date, their level and their implementation deadline;
- internal findings raised by compliance monitoring, often more numerous and less closely tracked;
- the internal audit programme and its completion rate: a programme running late is a finding that has not yet been raised;
- the risk register, with the status of each mitigation measure and its named owner;
- reported occurrences under analysis, and those whose analysis is closed with no traceable follow-up;
- exemptions, deviations and specific approvals, with their expiry date;
- the manual amendment log, with the status of each one: approved, submitted, or merely drafted;
- correspondence with the authority, including the minutes of closing meetings.
Check closure files carefully. The list of findings is easy to obtain; their true status much less so. A tracking table displaying green dots says nothing until the corresponding closure file has been opened. And the level of a finding is not negotiable: it dictates the handling regime from day one.
| What you look at | Level 1 finding | Level 2 finding |
|---|---|---|
| Nature of the non-compliance | Lowers the level of safety or calls into question the validity of the approval | Could lower it if left untreated; an established deviation with no immediate effect |
| Effect on the exercise of the approval | Precautionary measure possible: limitation, suspension, partial revocation | No immediate effect as long as the plan is kept to |
| Handling horizon | Immediate: action precedes the drafting of the plan | Period bounded by the regulation, of the order of a quarter |
| Extension | Not applicable | Possible, but conditional on a plan judged satisfactory by the authority |
| What you do about it on day one | Check that none is open; if there is one, it comes before the inventory | Rank by time remaining, never by apparent difficulty |
The “closed” actions that have only been written up
Three types of actions exist. Three distinct operations hide behind the word “action”, and confusing them is the most expensive mistake in the file. The immediate correction deals with the occurrence: you replace the missing record, you requalify the staff member, you withdraw the aircraft from the programme. The corrective action deals with the cause: why the record was missing, why the qualification had expired without an alert. The effectiveness check, finally, establishes that some time after implementation the deviation is no longer recurring: it is a dated sampling exercise, not a statement of intent.
Closure files must be verified. A closure file containing nothing but a manual revision reference and a date has skipped the last two steps. It will hold until the next inspection, then the deviation will resurface. And a deviation that comes back is no longer read in the same way: a repeat occurrence shifts the problem from the technical level to the management system, that is to say to the post you have just taken up. Rereading the closure files of the last twelve to eighteen months is not a trial of the predecessor; it is the only way to know how many findings are genuinely closed.
The trap. An action closed on the sole basis of a manual amendment, with no evidence of distribution, of training or of subsequent monitoring, reopens twice over: the original finding comes back, joined by a second one about the reliability of closures. The sign is easy to spot: the file contains no record dated after the closure date.
A finding isn’t truly closed until you prove the problem won’t return. Just updating a manual isn’t enough—you need to check later that the fix worked and train people to follow it.
An AOC holder finds a closed finding about missing maintenance records. The file only shows a manual update, with no training records or audits. They reopen it, conduct training, and then audit the process three months later to confirm compliance.
The manual says one thing, the front line does another
Check procedures in practice. The second source of invisible inheritance is the gap between the approved text and actual practice. It cannot be detected by reading the manual, only by physically following a procedure from end to end with the person who performs it. Two or three procedures picked at random within the scope are enough to sense the discrepancy; more are needed, taken from different departments, to know whether it is local or general. Preference goes to those amended recently, because an amendment drafted under the pressure of a finding is often more ambitious than what the organisation can sustain.
Direction matters. The direction of the gap changes everything. Where practice is more demanding than the text, safety is not in question, but the organisation is living on a documentary debt: the manual is not read, it is bypassed from above, and nothing guarantees that the next arrival will reproduce the excess of caution. Where practice falls short of the text, that is a finding waiting for its inspection. Both are corrected, but not by the same means: one by a revision of the text, the other by action on resources or on workload.
The risk register is the memory of the post
Risk registers hold critical info. The risk register is where the predecessor’s judgement was recorded, or should have been. You read it backwards: not through the hazards, which look much the same from one organisation to another, but through the mitigation measures. They are what carries the residual risk, and they are what gives way first. A measure that rests on the vigilance of a named person, on a spreadsheet kept by a single individual, or on “particular attention” with nothing to support it, is not a measure: it is a dependency. And the person on whom several of them depended has just left.
Check indicators too. Performance indicators and the associated targets are read with the same suspicion. An indicator that has not been updated for two review cycles is a finding in waiting, and it says a great deal about the real vitality of the system. The minutes of the last three safety review meetings complete the picture: they show what was raised, what was decided, and above all what comes back meeting after meeting without ever being dealt with. That recurring item is the real subject of the post.
The right move. For each open risk, ask a single question: who does what if the person named in the mitigation measure is not there? Risks with no answer move to the top of the list, ahead even of those with the highest rating.
What was promised to the authority and is written down nowhere
Verbal commitments matter. The organisation’s file and the authority’s file do not contain the same things. An audit closing meeting produces verbal commitments that the inspector records: a timetable announced, a recruitment promised, a reorganisation mentioned. These commitments appear in no manual, they trigger no internal alert, and yet they will be brought up again. A successor who discovers them in a meeting is in a weak position for the rest of the cycle.
Request records early. The counter-measure is administrative and is done in writing: asking the authority for a copy of the correspondence and the state of the oversight file — date of the last inspection, history of findings, planned date of the next. The request is normal and well received: it signals a post holder taking the measure of their scope. It is also useful for another reason: the oversight cycle is not fixed. It is modulated by the organisation’s performance, and an accumulation of findings tightens the intervals and multiplies triggered inspections. An inheritance of findings therefore determines not only the next three months, but the oversight workload for the whole cycle to come.
The vacancy, the interim and the moment responsibility shifts
Vacancies shift responsibility. A change of nominated person is a change to the organisation, and it is notified to the authority before it takes effect where it is foreseeable. An unforeseen departure is covered by a temporary deputisation, whose duration and conditions are framed: it is neither a blank cheque nor a situation that can be renewed indefinitely, and the accountable manager remains answerable throughout the period. The vacancy suspends nothing; it merely shifts the load onto someone who had not planned to carry it.
First signature is key. The real shift of responsibility does not occur when the appointment file is signed. It occurs with the first document signed in the name of the function: a corrective action plan, a manual amendment, an acceptance of a deviation. From then on, the distinction between “what was found” and “what was decided” becomes theoretical for the inspector sitting opposite. That is the practical reason why the inventory is done before, and not after.
The trap. Signing, in the first few days, an action plan drafted by the predecessor in order to “unblock the file” amounts to adopting its cause analysis as your own. If that analysis is weak, the finding will come back, and it is your signature that will be on the file.
Thirty days, three passes
Three passes are needed. The inventory is not done in one go, and above all not in the order of the binder. It is done in three passes, each of which answers a different question. The first sorts by real urgency: time remaining crossed with the effect on operations, which produces a counter-intuitive order. A finding that is simple to close but a fortnight from its deadline comes ahead of a heavy finding that still has two months.

| Timing | What you open | The question that decides | Record to produce |
|---|---|---|---|
| Day one | Open external and internal findings | How many days remain, and what does the effect bear on? | Sorted, dated list, handed to the accountable manager |
| First week | Closure files from the last twelve to eighteen months | Does the closure rest on evidence postdating the action? | List of closures to be reopened, with the reason |
| First month | Manuals, risk register, correspondence with the authority | Does what is written match what is done? | Written status review, gap by gap |
Three phases exist. The second pass no longer sorts, it verifies. It bears on closures already pronounced and asks only one question of each file: does it contain a document dated after implementation — a sampling record, an attendance sheet, an internal monitoring report? If the last document in the file is the amendment itself, the closure is declaratory and the file joins the list of items to be reopened. The third pass, the slowest, sets the text against practice and is conducted in the field rather than at the desk: it is the one that brings to light the dependencies in the risk register, because there you finally see who actually performs the task.
Adjust for size. The calibration of these three passes changes with the size and the type of operation. In a large structure, functions are separated and the inventory consists mainly in cross-checking systems that do not talk to one another: findings tracking lives in one tool, training in another, document control in a third, and the three contradict each other on the same facts. In a small organisation, where the same person holds several nominated posts, the problem is reversed: everything looks consistent because everything was held in a single head, and that person’s departure has emptied the system’s memory without leaving any visible gap. The first case is handled by cross-checking, the second by reconstruction — going back over recent decisions and giving them a written trace again before they are challenged.
Subcontractors add complexity. A maintenance organisation or a continuing airworthiness management organisation adds a constraint of its own: part of its commitments live with its subcontractors and with its customers. Findings there often bear on the interface — a task delegated with no associated monitoring, a contract that does not carry over the applicable requirements, a customer who has changed maintenance programme without the agreement following suit. The day-one inventory therefore remains incomplete until the contracts and interface agreements have been reread with the same method as the findings: who does what, on what evidence, and by what deadline.
Final report is crucial. The third pass concludes with a written note to the accountable manager: the state of the inherited findings, the real deadlines, the resources needed, the points where the existing plan will not hold. This note is not defensive, it is functional: it turns a diffuse inheritance into dated decisions, and it gives the accountable manager the visibility their own accountability demands. It has a useful side effect: it fixes the date on which the successor took the exact measure of the situation.
The right move. Date and circulate the status review, even incomplete, rather than waiting until it is finished. An imperfect document delivered on the thirtieth day is worth more than an exhaustive one delivered in the fourth month, when two deadlines have already passed.
What to go and check in your own documentation
Check your manuals first. The regulation establishes the existence of the posts and the principle of their acceptance; for the rest it refers to the operator’s documentation. That is therefore where to look for the answers that bind: who may sign what, what a deputy not yet accepted may sign, the threshold above which an occurrence goes up to the accountable manager, the review frequency of the risk register, and the change management procedure that applies to the appointment itself. Many organisations discover on this occasion that their own manual describes a deputisation arrangement that has never been put in place.
Grey areas exist. A grey area remains, and it is better to know about it than to discover it. Oversight bears on the approved organisation, not on the chronology of the people who have held the post: a finding predating the successor’s arrival does not name them, but nothing discharges them from it either, and it is they whom the inspector will question. The only real protection is documentary: a dated status review, a written reassessment of plans judged untenable, and a request for extension filed early rather than late.
Interview preparation. For anyone preparing for an appointment, the acceptance interview holds fewer surprises than expected on the regulation, and many more on the state of the organisation: what the authority checks is the ability to describe what you are taking over and to say what is wrong. Arriving with the inventory already done is the most solid answer there is to that question, and it is also what distinguishes a post holder from a manager of deadlines. The training paths preparing for management functions start from precisely this point.
The applicable texts, the decisions of the competent authority and the operator’s approved documentation prevail over this article, which describes general mechanisms and replaces neither a job description nor a management system manual.
Questions fréquentes
Does the handling period for a finding restart when the nominated person changes?
No. The finding is notified to the approved organisation, and the implementation period runs from that notification. The authority’s acceptance of a new person concerns the competence of the post holder, not the schedule of corrective actions. The successor therefore takes over a residual period, part of which the vacancy in the post has already consumed.
Can an extension be requested because the predecessor has left?
The departure of a post holder is not in itself a ground for extension. Extending an implementation period remains bounded by the regulation and conditional on an action plan judged satisfactory by the authority. A request filed early, backed by a written reassessment and by a mitigation measure already in place, has a far better chance of succeeding than a last-minute one.
How do you recognise a finding closed only on paper?
The closure file contains nothing but a documentary revision reference and a date, with no subsequent record. What is missing is the evidence of distribution and training, and above all the effectiveness check, which is a dated sampling exercise carried out after implementation. Such a finding generally resurfaces at the next inspection, and a repeat occurrence is in practice assessed more severely than the original deviation, because it calls into question the closure process itself and no longer merely the fact observed.
Should action plans drafted by the predecessor be signed?
Not before reading them as far as the cause analysis. Signing a plan amounts to adopting its reasoning as your own before the authority, including where it was built on resources that no longer exist. When a plan looks untenable, it is better to reassess it in writing in the first few weeks than to discover its failure at the deadline.
How can you find out what the organisation promised the authority before the successor arrived?
By asking the competent authority in writing for a copy of the correspondence and the state of the oversight file: date of the last inspection, history of findings, planned date of the next. The minutes of closing meetings record verbal commitments that appear in no internal manual. The step is routine and well received coming from a new post holder.
May an interim holder not yet accepted exercise the prerogatives of the post?
An unforeseen vacancy may be covered by a temporary deputisation, whose duration and conditions are framed and known to the authority. The exact extent of the signatures authorised during that period is defined by the operator’s approved documentation, which must therefore be read before making any commitment. The accountable manager, for their part, remains answerable throughout the interim period.

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