A control concern can be open for nine months — challenged repeatedly, promised and re-promised, one missed deadline from escalation — and still reach a successor as a single line marked “open.” Glenn Oborne of Ingen Partners explains why senior governance handovers lose that escalation history and how a simple live concerns register can preserve it.
Picture a control concern that has been open for nine months. Management has said more than once that remediation is underway, but two deadlines have come and gone. Directors have pushed back on the lack of progress, and the committee is one missed commitment away from escalating.
Then the senior governance lead leaves.
The successor inherits the action log, the recent committee papers and the latest management update. The concern is recorded, correctly, as open. But the history behind that single line can be nearly invisible: how many times directors have already challenged management, what assurances were given and broken, how close the committee came to escalating. On paper it looks like one outstanding action. But really it’s the latest chapter in a long, deteriorating pattern — and the person now responsible for it may have no way to see that.
This is what senior governance handovers routinely miss. An organization can transfer every open item cleanly and still hand the incoming person an incomplete picture of the risk.
When the current status hides the history
An action log shows what’s outstanding, who owns it and when it’s due — but not how a concern has hardened over time. The same limitation applies to management assurances: a promise to resolve something by the next meeting is reasonable the first time it’s made, but after two missed deadlines it should carry far less weight, and the log records the promise the same way either way. If that history isn’t clear to the incoming governance lead, they may reasonably grant management more time or ask questions that have already been asked — not because anyone downgraded the concern, but because part of the escalation history disappeared in the transition.
The UK’s Financial Conduct Authority (FCA) already recognizes the value of this kind of context. Under SYSC 25.9 of its handbook, handover material for senior managers can include unresolved or possible regulatory breaches and concerns raised by regulators, and the FCA says that material should identify priorities and include judgment and opinion, not just facts and figures.
Those provisions apply in a specific regulatory setting, but the principle travels: A handover needs to help someone understand which matters require attention, not simply hand them an accurate list of everything currently open.
What should survive the handover
This is more complex and difficult when several functions are involved. Compliance may identify a concern, legal advises on its implications, risk maintains the rating, internal audit tests the control, the business owns the remediation, and governance manages reporting to the board. Each team may keep perfectly good records, but none of them necessarily captures the history of the board’s own involvement — what directors have already asked, what management committed to, which deadlines were accepted and whether another failure would trigger escalation.
For significant unresolved matters, a simple live concerns register, kept alongside the normal action tracker, can preserve that. It might record when the concern first reached the board or committee; the main questions directors raised; commitments management made and deadlines it later missed; who currently owns the response across functions; any previous related concerns; and the event that would trigger further escalation. This shouldn’t become another lengthy governance document; the point is to preserve a small amount of context that would otherwise be hard to reconstruct later.
The escalation trigger matters most. If a committee has effectively decided that one more missed deadline will require a different response, the incoming lead needs to know it, so a change of personnel doesn’t hand the issue an unintended fresh start. Some of this will travel through judgment rather than a register: an experienced governance professional may know that a committee chair has lost patience with repeated explanations, that a director has asked the same question at several meetings, or that an action was marked complete without resolving the concern behind it. That doesn’t call for subjective commentary about individual executives. It calls for an honest account of where the formal status of a matter understates the level of board concern.
Keep the issue moving
Governance handovers are often judged by whether the machinery continues to operate. Meetings are scheduled, papers are circulated, minutes are completed and action logs stay current. That is necessary, but it is not enough for significant compliance concerns.
The incoming person should be able to establish quickly what has already been challenged, what assurances have been given, which commitments have slipped and what the board or committee expects to happen next.
If they can, the concern retains its history and momentum. If they cannot, an issue the organization has already spent months challenging may quietly return to an earlier stage of scrutiny.
A good handover should prevent that reset.
A control concern can be open for nine months — challenged repeatedly, promised and re-promised, one missed deadline from escalation — and still reach a successor as a single line marked “open.” Glenn Oborne of Ingen Partners explains why senior governance handovers lose that escalation history and how a simple live concerns register can preserve it.
Picture a control concern that has been open for nine months. Management has said more than once that remediation is underway, but two deadlines have come and gone. Directors have pushed back on the lack of progress, and the committee is one missed commitment away from escalating.
Then the senior governance lead leaves.
The successor inherits the action log, the recent committee papers and the latest management update. The concern is recorded, correctly, as open. But the history behind that single line can be nearly invisible: how many times directors have already challenged management, what assurances were given and broken, how close the committee came to escalating. On paper it looks like one outstanding action. But really it’s the latest chapter in a long, deteriorating pattern — and the person now responsible for it may have no way to see that.
This is what senior governance handovers routinely miss. An organization can transfer every open item cleanly and still hand the incoming person an incomplete picture of the risk.
When the current status hides the history
An action log shows what’s outstanding, who owns it and when it’s due — but not how a concern has hardened over time. The same limitation applies to management assurances: a promise to resolve something by the next meeting is reasonable the first time it’s made, but after two missed deadlines it should carry far less weight, and the log records the promise the same way either way. If that history isn’t clear to the incoming governance lead, they may reasonably grant management more time or ask questions that have already been asked — not because anyone downgraded the concern, but because part of the escalation history disappeared in the transition.
The UK’s Financial Conduct Authority (FCA) already recognizes the value of this kind of context. Under SYSC 25.9 of its handbook, handover material for senior managers can include unresolved or possible regulatory breaches and concerns raised by regulators, and the FCA says that material should identify priorities and include judgment and opinion, not just facts and figures.
Those provisions apply in a specific regulatory setting, but the principle travels: A handover needs to help someone understand which matters require attention, not simply hand them an accurate list of everything currently open.
What should survive the handover
This is more complex and difficult when several functions are involved. Compliance may identify a concern, legal advises on its implications, risk maintains the rating, internal audit tests the control, the business owns the remediation, and governance manages reporting to the board. Each team may keep perfectly good records, but none of them necessarily captures the history of the board’s own involvement — what directors have already asked, what management committed to, which deadlines were accepted and whether another failure would trigger escalation.
For significant unresolved matters, a simple live concerns register, kept alongside the normal action tracker, can preserve that. It might record when the concern first reached the board or committee; the main questions directors raised; commitments management made and deadlines it later missed; who currently owns the response across functions; any previous related concerns; and the event that would trigger further escalation. This shouldn’t become another lengthy governance document; the point is to preserve a small amount of context that would otherwise be hard to reconstruct later.
The escalation trigger matters most. If a committee has effectively decided that one more missed deadline will require a different response, the incoming lead needs to know it, so a change of personnel doesn’t hand the issue an unintended fresh start. Some of this will travel through judgment rather than a register: an experienced governance professional may know that a committee chair has lost patience with repeated explanations, that a director has asked the same question at several meetings, or that an action was marked complete without resolving the concern behind it. That doesn’t call for subjective commentary about individual executives. It calls for an honest account of where the formal status of a matter understates the level of board concern.
Keep the issue moving
Governance handovers are often judged by whether the machinery continues to operate. Meetings are scheduled, papers are circulated, minutes are completed and action logs stay current. That is necessary, but it is not enough for significant compliance concerns.
The incoming person should be able to establish quickly what has already been challenged, what assurances have been given, which commitments have slipped and what the board or committee expects to happen next.
If they can, the concern retains its history and momentum. If they cannot, an issue the organization has already spent months challenging may quietly return to an earlier stage of scrutiny.
A good handover should prevent that reset.
