As year end approaches, most organizations know which tasks remain open. Fewer have a clear view of which issues remain unresolved.
An open task has an expected action and an owner. An unresolved issue is different. It may involve a decision that has been deferred, an exception that became routine, evidence that was never completed, a commitment without a clear disposition, or a control that works differently from the approved design.
This week's executive question asks what unresolved issue the organization is carrying into year end that still needs a leadership decision. The field response is to reconcile more than the accounts. Leaders should reconcile decisions, exceptions, evidence, ownership, and commitments before they become the starting conditions for another year.
Unreconciled is not only an accounting term
Finance teams are accustomed to reconciling balances, transactions, supporting schedules, and source records. The same discipline can be applied to the operating environment.
A policy may say one thing while the workflow does another. A vendor may remain active although its role has changed. A project may be treated as complete even though documentation, ownership, or benefit tracking remains open. A recurring exception may be accepted informally without a decision about whether to correct the process or approve a new standard.
These differences create operational residue. Individually, each item may appear manageable. Together, they weaken reporting, blur accountability, consume attention, and make the organization begin the new year with inherited ambiguity.
Build one view of unresolved matters
Unresolved issues often sit in separate places. Finance maintains a close checklist. Operations tracks project actions. Technology holds a vendor list and system backlog. Risk and compliance maintain open findings. Leadership decisions are scattered across meeting notes, email, and individual follow up.
The goal is not to merge every task list into one large register. It is to create one leadership view of matters that require a decision, exception, acceptance, or formal carryforward.
Each item should state the issue, the business impact, the accountable owner, the decision or evidence required, the due date, and the proposed disposition. It should also show whether the item affects financial reporting, cash, customer commitments, regulatory obligations, vendor exposure, system reliability, or the operating plan.
This view helps leadership distinguish routine completion work from issues that require judgment. It also prevents the same matter from appearing under several labels without anyone seeing the combined risk.
Separate resolution from decision ownership
Teams often know how to investigate an issue but do not know who has authority to resolve it. The work remains active while the decision waits.
For every significant unresolved matter, name both the action owner and the decision owner. The action owner develops the facts, options, and recommendation. The decision owner accepts the risk, approves the change, allocates the resources, or sets the operating direction.
This distinction is especially important when issues cross functions. Finance may identify the exposure, Operations may own the process, Technology may hold the system constraint, and Legal or Risk may define the acceptable boundary. Shared contribution should not become shared ambiguity.
A useful leadership review does not ask only whether the item is still open. It asks what decision is due, who will make it, what evidence is sufficient, and what happens if the decision is delayed.
Treat exceptions as management evidence
Exceptions are often reviewed one at a time. A manual override is approved. A required field is bypassed. A purchase follows an alternate route. A deadline moves. A control is performed late but eventually completed.
Each exception may be reasonable. The pattern may still reveal a larger issue. Repeated exceptions can show that the policy does not fit the operating model, that authority is unclear, that the system design creates unnecessary friction, or that teams do not have the capacity to follow the intended process.
Before year end, group recurring exceptions by cause, process, owner, and business impact. Decide which ones should be eliminated, which need a redesigned control, which require a policy change, and which represent an accepted way of working that should be documented honestly.
An exception log becomes valuable when it changes the operating standard. If it only records deviations after the fact, the organization may document the same weakness repeatedly without resolving it.
Close the evidence gap
A control is not complete because someone believes it happened. Important approvals, reviews, reconciliations, and decisions need evidence that another person can locate and understand.
Year end is a useful point to test whether the evidence chain is intact. Can the organization show who approved the decision, what information was reviewed, which exception was accepted, when the control was performed, and where the final record is stored?
Missing evidence does not always mean the underlying work failed. It does mean the organization cannot rely on memory as its control environment. The remedy may be a better repository, a standard naming convention, an approval record, a completed checklist, or a workflow that captures the evidence as part of the work rather than after it.
Leaders should prioritize evidence that supports consequential decisions and material risks. The objective is not documentation for its own sake. It is a reliable record that supports accountability, continuity, and review.
Carry work forward deliberately
Not every issue should be forced closed before December 31. Some matters depend on information that will not be available. Others require a broader redesign, contract decision, system change, or investment that belongs in the next operating cycle.
Deliberate carryforward is different from passive rollover. A carried item should have a named owner, an agreed decision date, an interim control where needed, a clear risk statement, and a place in the next year's operating plan. Leadership should understand what remains exposed and why accepting that exposure is reasonable.
This is also the point to remove stale work. Some open items remain on lists because no one has made the decision to close, cancel, combine, or replace them. Carrying everything forward preserves activity, not discipline.
The final year end review should produce four outcomes: resolved, accepted, redesigned, or deliberately carried forward. Anything without one of those dispositions remains unreconciled.
What good looks like
A disciplined year end process gives leadership one view of unresolved matters, separates action ownership from decision authority, examines recurring exceptions for patterns, closes important evidence gaps, and carries remaining work forward with an explicit disposition.
Leaders can test this quickly. Select one significant issue that has remained open for more than one review cycle and ask five questions. What decision is actually required? Who owns that decision? Which evidence is missing? What risk exists while the issue remains open? Will it be resolved, accepted, redesigned, or deliberately carried forward?
If those answers are unclear, the issue is not simply unfinished. It is unreconciled, and the organization is already making an unspoken decision to carry it into the next year.