Weekly Priorities Through a Carry-Over Audit: Why Last Week's Leftovers Matter
Most weekly planning starts from the wrong place. Teams open a board, look at what is waiting, and add new items on top of the pile. By Wednesday, the list holds last week's unfinished work, this week's requests, and a few items nobody remembers approving. A carry-over audit reverses that order. Before anyone plans new work, the team examines everything that rolled forward from the previous week and asks a simple question about each item: should this still be here, and if so, why? The method is quick, requires no special software, and tends to clarify priorities more than any amount of brainstorming. This article explains how to run the audit, what to look for, and how to turn the results into a short, honest list of weekly priorities.
Why carry-over work deserves its own review
Unfinished items are not neutral. Each one represents a decision that was made once and never revisited. Someone committed to it, a deadline was attached, or it was simply left in a column when the week ended. Over time these items accumulate a kind of inertia: they stay because nobody removed them, not because anyone decided they still matter. A carry-over audit forces that decision back into the open.
The audit also protects the team from a common illusion. When a board shows twelve active cards, people assume twelve things are in motion. In practice, several of those cards may be waiting on an answer, blocked by a dependency, or quietly abandoned. Counting carry-over items honestly reveals how much of the team's capacity is already spoken for before the week begins.
Running the audit in about twenty minutes
Set aside a short, fixed slot at the start of the planning meeting, or have one person prepare the list before the meeting. Pull every item that moved into the current week from the previous one. For each item, the owner answers four questions in order: Is it still the right work? Is it still the right size? Is it still unblocked? Does it still have a realistic date? Any item that fails a question gets flagged, not silently moved forward.
Decisions for flagged items fall into a few categories. The item can be completed this week as written. It can be split into a smaller piece that fits this week, with the remainder placed back in the backlog. It can be explicitly moved back to the backlog with a note on why. Or it can be closed because the underlying need has disappeared. The key discipline is that every carry-over item leaves the audit with a named outcome. Nothing should simply drift into the new week without a fresh decision attached to it.
Spotting patterns that signal deeper trouble
A single carry-over item is usually a scheduling detail. A recurring one is information. If the same kind of task appears in the audit week after week, the board is telling you something. Items that repeatedly fail the size test often need breaking down before anyone can estimate them well. Items that fail the unblocked test point to a dependency that the team keeps ignoring, perhaps a decision that belongs to someone outside the group. Items that keep failing the date test may have been given deadlines that never reflected real capacity.
Look also at who owns the carry-over items. If one person holds a disproportionate share, the problem may be workload rather than discipline. Surface that pattern calmly in the meeting and discuss whether the weekly plan actually fits the people who must carry it out. The audit is a tool for seeing reality, so its findings should be used to adjust the plan, not to assign blame.
A practical checklist for the audit
Use this sequence each week. First, list every item rolling forward from last week, including items that are nearly done. Second, ask the four questions for each one: still the right work, still the right size, still unblocked, still a realistic date. Third, assign each flagged item one outcome: finish, split, return to backlog, or close. Fourth, count the items that remain as committed work for this week, and compare that count against the team's usual throughput. Fifth, only after the carry-over decisions are settled, pull new candidates from the backlog and apply the same capacity test to them.
Compared with a planning session that starts from new requests, the audit approach produces a shorter and more credible list. Teams that begin with carry-over work usually discover that they have less room than they assumed, which is the whole point. A list of three priorities that the team can genuinely finish is worth more than a list of nine that will all roll forward again next Monday.
Questions to ask when the audit gets uncomfortable
Some findings will be unpleasant. An item may have been championed by a senior person, or it may represent a commitment made to a customer. Handle these with the same questions. Is the work still the right work? If yes, what would it take to make it fit this week, and what else must give way? If the honest answer is that it cannot fit, say so plainly and move it with a clear note, so the people waiting on it know where it stands.
Consider also whether the audit itself needs adjusting. If every item keeps failing the same question, the team may be estimating poorly or accepting work without checking dependencies at intake. Those are upstream problems, and the carry-over audit will keep revealing them until they are addressed. Treat the audit as a feedback loop about how work enters the board, not only about how it leaves.