How much pre-read time survives before executive meetings? An observational protocol

The question begins after delivery

Research question: how much usable attention time remains between a complete pre-read becoming available and the meeting or decision it supports? Executive assistants and chiefs of staff often track whether a document was sent, yet a timestamp alone cannot show that the leader received the correct version, understood the decision requested, or had an uninterrupted chance to review it. HireExecutiveTeam's audience needs a method that studies the preparation window without claiming access to a leader's thoughts. O*NET and BLS establish that executive administrative work includes scheduling, information organization, and document preparation. HBR's discussion of meeting load supplies context, not a universal threshold for adequate review. ^[1][2][3]

Observe a defined set of recurring leadership meetings for six to eight weeks. For each agenda item, record the meeting start, decision question, accountable content owner, first delivery, final material change, executive-support quality check, calendar time reserved for review, urgent interruptions during that block, and whether the item proceeded, moved, or returned for clarification. Do not capture private reading behavior or infer attention from presence indicators. The study measures the opportunity to prepare and the condition of the material. It cannot prove comprehension. State this boundary prominently in the method and in any report of findings. ^[1][4][5]

Constructing an honest attention window

Calculate the nominal window from final usable delivery to meeting start, then annotate it with observed constraints. A document sent two days early may have no usable window if its decision question arrives ten minutes before the meeting. A paper delivered that morning may be usable when it is short, expected, and paired with a protected review block. Keep both cases intact rather than forcing them into an average. The final report should show distributions and short case narratives, because a median can hide the difference between predictable weekly materials and an exceptional board matter. ^[3][6]

Define final usable delivery before collecting data. A version qualifies only if the named owner confirms that it contains the evidence intended for review, the decision or discussion purpose is explicit, and the executive can access it through the approved system. Cosmetic edits after that point may be logged separately. A changed recommendation, missing appendix, or corrected figure restarts the substantive clock. This rule prevents the support team from receiving credit for early delivery of a document that was not ready. It also avoids blaming the support role when the content owner changes the material later. ^[5][1][2]

Sample the interruptions that overlap reserved review time, but avoid moral judgments about them. A customer escalation or board request may correctly displace preparation. Record who authorized the tradeoff, whether another review period was created, and what happened to the agenda item. The useful distinction is between a visible choice and an accidental collision. Microsoft reports on workplace communication can frame why interruptions deserve study, but its broad survey findings cannot establish the cause or cost of a particular leadership team's missed review. ^[4][6]

Comparisons that preserve context

Compare decision items with status updates, first reviews with follow-up reviews, and routine meetings with board or hiring cycles. These categories have different preparation needs. Within each group, examine late substantive changes, missing decision questions, access failures, and displaced review blocks. Do not publish a league table of document owners. The goal is to locate operating conditions that compress the window. A content owner may deliver late because another accountable function supplied evidence late. Preserve that dependency rather than assigning the visible delay to the final sender. ^[1][2]

Outcome observations should stay modest: whether the item proceeded, was deferred, required clarification, or produced a recorded next step. A deferral may be the best decision when evidence is incomplete. Proceeding is not proof that preparation was sufficient. Interview notes can add the executive's and meeting owner's accounts, but label them as reported perceptions and retain disagreements. If a participant says the pre-read was useful while the version record shows a late correction, both facts belong in the case. The report should not smooth away tension to create a simple success story. ^[5][3]

Executive support can own the calendar holds, delivery checklist, version pointer, and escalation when a deadline slips. It can ask a content owner to name the decision and confirm readiness. It should not certify technical claims it cannot evaluate, invent a recommendation, conceal a late change, or decide that a leader has read enough. A chief of staff may resolve a conflict between agenda priorities, while the executive and functional owners retain substantive judgment. The study should test these boundaries rather than rewarding support for absorbing responsibilities that belong elsewhere. ^[1][2][4]

Limits and conclusion

Calendar records omit mental preparation that happens outside reserved blocks, and they may miss interruptions handled through private channels. Observation can change behavior. Meeting types vary, samples are often small, and an executive's preferred preparation style may not generalize. The method also cannot convert available minutes into a financial return or causal productivity result. Report missing records, excluded confidential items, the definition of a substantive change, and the meeting mix. Re-run the study after a cadence change instead of treating one period as a permanent benchmark. ^[6][5][3]

The evidence-led conclusion is that pre-read reliability depends on the intersection of usable material, a clear decision question, access to the final version, and an attention window that survives competing demands. Measuring delivery alone misses that intersection. For organizations considering HireExecutiveTeam's support lanes, the study can reveal whether the main need is document coordination, calendar protection, cross-functional escalation, or clearer executive decision rights. It cannot tell a leader how long every document deserves. It can show, case by case, where the intended chance to prepare disappeared and which owner can repair the underlying condition. ^[1][3][5]

Sources

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

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.