On this page
The open-loop audit: measuring delegated follow-ups past due
A bounded protocol for auditing delegated executive follow-ups that remain open past their due date, with a record design and a local review routine.
Remote Executive Support Editorial Desk · · 9 min read · Sources: 5 · Verified 2026-11-04

Key statistics
- The protocol defines an open loop as a delegated commitment with no recorded outcome and no current owner action.
- The cited sources describe internal control, records management, and security practice; none reports a private-sector executive follow-up benchmark.
- The proposed review reports counts, age bands, and unresolved exceptions rather than a single average.
Key takeaways
- A delegated follow-up is open until the record shows a result, not until someone remembers sending it.
- Due dates should be recorded when the follow-up is created, not reconstructed when the audit begins.
- The useful measure is the age and ownership of open loops, not a single completion percentage.
- A small queue sample can expose where follow-ups stall, but it cannot establish a universal completion benchmark.
Published November 4, 2026
A delegated follow-up is easy to start and easy to lose. The executive asks the assistant to chase a contract, confirm a reference, or get a date from a partner. The assistant sends the message, notes the request, and moves on. Two weeks later the executive asks what happened. The message was sent, but no reply arrived, and nobody noticed. The loop was never closed; it simply stopped being visible.
Remote executive support is especially exposed to this pattern because the office often spans time zones and handoffs. The person who sent the follow-up may not be the person who sees the reply. Without a shared record, a follow-up becomes a memory held by one assistant and a hope held by the executive. An open-loop audit makes the backlog visible and gives the office a way to decide what to do next.
This article proposes a bounded local protocol for measuring delegated follow-ups that remain open past their due date. It does not offer a universal completion target. The cited sources describe internal control, records management, and security practice in general terms; they do not measure follow-up behavior in a private executive office. The protocol is a way to define a local rule, test whether the office can follow it, and fix the most common failure.
The question and the unit of analysis
The question is: for a defined period, which delegated follow-ups are open past their due date, how old are they, who owns them, and what is the next action? The unit of analysis is one delegated commitment, from the moment it is assigned to the moment a result is recorded. A commitment may be a request for information, a document, an introduction, a decision, a confirmation, or a correction. It is not the same as a task list item that the assistant performs alone. The distinguishing feature is that the outcome depends on someone outside the immediate exchange.
The record should identify the executive who delegated the follow-up, the person or group who owes the result, the assistant or owner responsible for chasing it, the date the follow-up was created, the due date, the last contact, and the current state. The current state should be one of a small set: waiting on the other party, waiting on the executive, waiting on an internal team, resolved, or abandoned with a reason. That vocabulary prevents the audit from becoming a search for a single "done" flag that hides the real blocker.
The scope should be fixed before the audit begins. One option is all follow-ups created in a calendar quarter. Another is all follow-ups that were open at the start of the quarter plus all new ones created during it. The second option captures inherited work, which is often where the oldest loops live. Whichever scope is chosen, write it down and use the same scope for the next review. A changing scope makes the trend meaningless.
Define an open loop and its due date
An open loop is a delegated commitment with no recorded outcome and no current owner action. The definition has two parts, and both matter. A follow-up with no recorded outcome is not closed just because a message was sent. A follow-up with no current owner action is not being worked, even if it appears on a list. The audit should treat "sent" as an event, not a result.
The due date is the date by which the office expected a result or a meaningful response. It should be recorded when the follow-up is created, not reconstructed later. If the requester did not specify a date, the assistant should propose one and confirm it with the executive or the owner. A follow-up without a due date is not necessarily late, but it is unauditable. The office cannot tell whether it is early, on time, or forgotten.
Some follow-ups have natural due dates: a contract renewal, a board meeting, a travel departure. Others are open-ended relationship requests with no external deadline. For those, use a review date rather than a completion date. The review date is when the office will check in, not when the other party must respond. That distinction keeps the audit honest.
A follow-up can be legitimately paused for a reason, an owner, and a resume date; record it as paused and exclude it from the past-due count, but keep it visible.
Record the fields that make an audit possible
The record needs enough structure to answer the audit question without becoming a second inbox. At minimum, capture the commitment, the executive, the counterparty, the responsible owner, the created date, the due date, the last contact date, the next action, the next action date, and the state. A short reference to the source message is enough for context. The record should not contain sensitive personal details that are not needed to manage the follow-up.
The last contact date is especially useful. It separates a follow-up that is waiting patiently from one that has been forgotten. A loop with a due date two weeks ago and a last contact date three weeks ago is a different problem from one with a due date two weeks ago and a contact yesterday. The first needs a nudge or an escalation; the second may simply need more time. Report both age and contact recency.
The next action field is what turns the audit into management. "Chase" is not an action. "Email the counterparty's chief of staff, copy the executive, and ask for a date by Friday" is an action. If the next action depends on the executive, name the decision the executive needs to make. If it depends on another team, name the team and the requested output. A record with no next action is a loop that has already stalled, even if nobody has labeled it that way.
Access control matters. Follow-up records can reveal client relationships, negotiations, personnel issues, or legal matters. Keep the audit queue in the approved system, limit access to the people who need it, and reference sensitive documents rather than copying them into the queue. NIST SP 800-53 and the NARA records-management guidance support the general disciplines of access limitation, accountability, and retention; they do not prescribe a specific tool. Choose a record design that is small enough to maintain and controlled enough to protect.
Sample the queue without flattering it
Choose a review date and freeze the queue as of that date. Count every open loop in scope, not just the ones that are easy to find. Include inherited loops, loops with no due date, loops marked paused, and loops whose owner has changed. If a loop cannot be classified, keep it in an "unclassified" bucket and explain why.
Report counts by age band: zero to seven days past due, eight to thirty days, thirty-one to ninety days, and more than ninety days. Report the owner and the counterparty type. Report how many loops have had no contact in the last fourteen days. Report how many have no next action. These counts are more useful than a single completion percentage because they show where the backlog is concentrated and what kind of intervention it needs.
Do not sample only the clean cases. A queue that looks healthy because the messy items were excluded is not evidence. If the office has a separate spreadsheet for "special" follow-ups, include it or explain why it is out of scope. If a follow-up was closed verbally but never recorded, count it as a record gap rather than a success. The audit is about the reliability of the record, not just the diligence of the assistant.
A worked example makes the method concrete. Suppose an assistant is asked on October 1 to confirm a partner's participation in a November panel. The due date is October 15. The assistant emails on October 2 and receives no reply. On October 9, the assistant sends a second note and gets a tentative yes. On October 16, the partner confirms in a call, but the assistant does not update the record until October 20. As of an October 18 review, the loop is past due and has no recorded outcome, even though the substantive answer arrived. The audit should count the record gap and note the late update.
Interpret the result and set the next check
A low past-due count is not automatically good. It may mean the office is closing loops promptly, or it may mean the queue excludes the difficult cases. A high count is not automatically bad. It may reflect a large inherited backlog, a slow counterparty, or a period of executive travel. Pair the count with the record quality: how many loops have a due date, a next action, and a recent contact? How many were closed with a recorded result? How many were reopened after being marked done?
Use the results to choose one change. The change might be a required due date for every delegated follow-up, a weekly fifteen-minute queue review, a rule that any loop with no contact in fourteen days gets a nudge, or a handoff requirement that names the next action and owner. Choose the change that addresses the largest preventable group. Assign one owner and one check date. Do not announce a broad transformation that the office cannot maintain.
The executive or chief of staff owns decisions about escalation, priority, and relationships. The assistant can maintain the queue, prepare the counts, send the agreed nudges, and route the exceptions. When a follow-up involves a legal, personnel, or client-sensitive matter, or when the counterparty's response changes the executive's commitment, the assistant should stop and escalate rather than closing the loop independently. That boundary protects the executive relationship and keeps the assistant's authority clear.
The cited control guidance supports the underlying discipline. The GAO Green Book describes internal control as a system of ongoing activities, not a one-time audit. COSO's guidance similarly emphasizes accountability and monitoring. NARA's records-management material and 36 CFR Part 1220 describe how records should be identified, retained, and made retrievable. Those sources do not tell an office how many follow-ups should be open, but they support the idea that a commitment should have an owner, a record, and a review point. For a related view of board-level follow-through, see the research on board action item follow-through.
A follow-up audit is not a hunt for a careless assistant. It is a check on whether the office can see its own commitments. The oldest loop in the queue is often a symptom of a missing handoff, an unclear owner, or a due date that was never written down. Fixing that one pattern is more valuable than closing a hundred easy items and leaving the hard ones invisible.
Sources
- U.S. Government Accountability Office, Standards for Internal Control in the Federal Government , checked November 4, 2026.
- COSO, Guidance on Internal Control , checked November 4, 2026.
- NIST Special Publication 800-53 Revision 5 , checked November 4, 2026.
- National Archives and Records Administration, Federal Records Management , checked November 4, 2026.
- 36 CFR Part 1220, Federal Records; General , checked November 4, 2026.
Related research
See measuring rework in executive meeting requests for a companion protocol on the cost of rebuilding a meeting after it has been accepted.
Frequently Asked Questions
What does The open-loop audit: measuring delegated follow-ups past due examine?
A bounded protocol for auditing delegated executive follow-ups that remain open past their due date, with a record design and a local review routine.
What key statistics does The open-loop audit: measuring delegated follow-ups past due report?
The protocol defines an open loop as a delegated commitment with no recorded outcome and no current owner action. The cited sources describe internal control, records management, and security practice; none reports a private-sector executive follow-up benchmark. The proposed review reports counts, age bands, and unresolved exceptions rather than a single average.
What are the key takeaways from The open-loop audit: measuring delegated follow-ups past due?
A delegated follow-up is open until the record shows a result, not until someone remembers sending it. Due dates should be recorded when the follow-up is created, not reconstructed when the audit begins. The useful measure is the age and ownership of open loops, not a single completion percentage. A small queue sample can expose where follow-ups stall, but it cannot establish a universal completion benchmark.