Measuring delegation quality from task reassignment records

Key takeaways

• Score each handoff on outcome, deadline, constraints, and decision authority.
• Count rework and second handoffs separately from the time a task takes.
• Look for repeated incomplete briefs by task type, not by individual owner.
• Test one brief template for three weeks and compare the same rework causes.

Question and scope

This study asks whether tasks delegated by an executive are completed with the context and authority the executive intended. The unit is one reassignment recorded in the task system or the executive's message. The review records the brief, the owner, the deadline, the authority granted, and the outcome. It does not rate the person's effort, only whether the handoff produced a usable result.

Set the scope to one executive and four weeks of reassigned work. Include tasks sent to an assistant, a chief of staff, and a functional lead so the comparison is not limited to one role. Record the task system and the channels used for the handoff. If the executive changes the delegation rule during the window, separate the periods.

Record the task type and the skill it requires, because delegation quality looks different for a research task and a routine approval. A brief that is complete for one may be insufficient for the other. Use the same categories across the sample so the comparison is fair. The review should not compare a complex strategy task with a calendar change.

What the sources establish

The Small Business Administration's management guidance describes assigning responsibility and clear expectations. BLS occupational data provides context on the administrative support role but not a delegation benchmark. GAO's Green Book addresses internal control, including authority and accountability. Harvard Business Review's work on meetings and management discusses follow-through. These sources support the importance of clear ownership but cannot measure whether a specific brief was complete.

The study therefore treats delegation as a handoff with observable parts. A brief can be short and still be complete if it names the outcome, the boundary, and the deadline. A long brief can still fail if it leaves the decision authority unclear. The review scores those parts separately rather than treating length as a proxy for quality.

Ask the executive what they expect the owner to decide without checking back. That answer defines the authority more clearly than a general statement about ownership. Write it beside the task type. A new owner can then see the boundary before the first handoff rather than learning it through rework.

Definitions and measures

Define a reassignment as a task that moves from the executive to another owner with an expectation of action. Define a complete brief as one that states the outcome, the deadline, the constraints, and the decision authority. Define rework as any change the executive made after the task was returned. Write the definitions before collection so two reviewers can apply them consistently.

Measure the number of reassignments, the number with a complete brief, the number that required rework, and the number that closed without a second handoff. Record the time to completion and the number of follow-up messages. A simple count of rework causes is more useful than a satisfaction rating that cannot be traced to a specific handoff. Record the date of each follow-up so the time cost is visible beside the rework count.

Define a second handoff as any transfer of the task to another person before it closes. A task that moves from an assistant to a functional lead may still be fine, but the transfer adds context loss. Record the reason for the transfer. That record shows whether the original owner had enough authority or access.

Sampling and collection

Sample tasks from the task system and the executive's sent messages, then review the full thread. Include tasks that were completed, delayed, and abandoned. Do not review only the successful ones, because the failures usually carry the clearest lesson. Record the owner's role and whether the task crossed a team boundary.

Ask the owner what was missing from the brief, using a short list of categories rather than an open question. The categories might be outcome, deadline, authority, access, or context. That structure makes the answers comparable and reduces the tendency to blame the executive. Keep the owner's comments separate from the reviewer's judgment.

Include tasks that were delegated verbally and later confirmed in writing. The written confirmation is often the only record of what was agreed. If no confirmation exists, mark the task as unverifiable rather than guessing. A sample with a clear evidence rule is more useful than one that fills gaps with memory.

Analysis and reporting

Report rework by cause and by task type. Show the share of tasks that needed a second handoff and the time lost to each. Separate a task that was genuinely complex from one that was poorly briefed. A complex task may need more context, while a simple task with rework usually points to an unclear authority or deadline.

Look for the same owner receiving repeated incomplete briefs. That pattern may indicate a mismatch between the task and the role, not a performance problem. Rank the fixes by the cost of the rework. Choose one change, such as a standard brief template or a decision-rights note, and test it on the next set of tasks.

Compare the rework rate with the number of follow-up messages. A task that requires many messages but little rework may still be consuming the executive's attention. A task with one message and a large rework may be worse. Report both so the office can see the difference between coordination cost and quality cost.

Compare the briefs that produced clean work with the ones that produced rework. Look for the presence of an outcome, a deadline, and an authority statement rather than for length. A short brief with all three may outperform a long brief with none. That comparison gives the executive a practical model to copy.

Limits and sources of error

The study cannot prove that better briefs produce better outcomes, because the owner's skill and the task's difficulty also matter. Rework may be a legitimate part of a creative task rather than a failure. Report the category and the context so a single number does not mislead. The executive's own memory of the brief may also differ from the written record.

Some delegation happens in conversation and leaves no written trace. Those tasks are likely to be missing from the sample, and they may be the ones with the weakest briefs. Note the gap rather than pretending the record is complete. A small sample with a clear method is still useful for choosing one change.

Do not assume that a delegated task failed because the owner lacked skill. The brief, the access, and the timing can each cause the same result. Report the cause categories separately. That separation keeps the review fair and points to a fix the executive can actually make.

Review and next action

Choose one change, such as a four-part brief or a named decision owner for each task. Test it for three weeks and repeat the same measures. The [decision log](/blog/building-a-decision-log-the-executive-team-actually-reuses/) can hold the authority record that the brief refers to. Keep the old brief format for one team during the test so the comparison has a control.

Close the review when the office can show which task types still return for rework and which owners need a different kind of support. Keep the findings with the delegation template so the next review starts from the same definitions. Share one example of a complete brief and one example of a costly gap. The goal is fewer repeated explanations, not more paperwork.

Share the revised brief with the people who receive delegated work, not only with the executive. They are the ones who experience the missing context. Ask for one example of a brief that worked and one that did not. That conversation is often more useful than another template.

Ask the owners to mark the one part of the brief they use most and the one part they ignore. A template that is not used is worse than no template because it creates the appearance of clarity. Remove the unused section and keep the test small. The next review should show whether the simpler brief improved the result.

Sources

1. Secretaries and Administrative Assistants, U.S. Bureau of Labor Statistics, Occupational Outlook Handbook.
2. Executive Secretaries and Executive Administrative Assistants, U.S. Bureau of Labor Statistics, Occupational Employment and Wage Statistics.
3. Executive Secretaries and Executive Administrative Assistants, O*NET OnLine.
4. Business Formation Statistics, U.S. Census Bureau.
5. Nonfarm Business Sector: Labor Productivity, Federal Reserve Economic Data.
6. Productivity Statistics, OECD Data Explorer.
7. World Development Indicators, World Bank DataBank.
8. ILOSTAT Labour Statistics, International Labour Organization.
9. 2024 Work Trend Index Annual Report, Microsoft and LinkedIn.
10. The economic potential of generative AI, McKinsey Global Institute.
11. Creating helpful, reliable, people first content, Google Search Central.
12. Search Engine Optimization Starter Guide, Google Search Central.
13. Dear Manager, You Are Holding Too Many Meetings, Harvard Business Review.
14. SBA, Manage your business.
15. BLS, Secretaries and Administrative Assistants.
16. GAO Green Book.
17. Harvard Business Review, meetings.

Related research

• Measuring decision log reuse across executive team meetings
• Building a Decision Log the Executive Team Actually Reuses
• Preparing a Chief of Staff Weekly Agenda from Open Decisions

Apply the research

Use the finding to frame one question for your own team: which support work is currently invisible, and who should own the next step? A scoped consultation can turn that question into a practical role. Write the question down before the meeting. Name the person who owns the next step.