Measuring Records Handover Completeness at Executive Year-End

Key takeaways

• Define completeness as usable access, not as a file count.
• Test the incoming owner's own account, not the outgoing one.
• Report restricted records and their approvals separately.
• Keep the handover record with the retention schedule.

Question and scope

This study asks whether an executive office year-end records handover gives the incoming owner usable access to the records the role requires. The unit is one record or record set tied to one owner and one retention rule. The review follows the index, the access test, and the signed transfer. It does not judge whether every record should have been kept.

Set the scope to one executive office and one year-end transfer. Record the record types, the systems, and the incoming owner. If the transfer spans two systems, separate the periods. A migration can change access without changing the index.

Include active, archived, and restricted records. Include at least one record that is past its retention date and one under a legal hold. Record the category. A sample of only active files will overstate the handover's completeness.

What the sources establish

NARA records-management guidance supports a planned transfer with an index and a retention schedule. NIST privacy guidance supports limiting access to restricted material. IRS recordkeeping guidance describes the kind of records a business should keep but does not set an executive-office standard. Record the date and the owner so the next review can rebuild the decision.

The sources do not establish a completeness percentage or a required folder structure. They also do not say which records the incoming executive will need first. The study therefore measures the office's own index and the access the role actually requires. The report should keep that local scope visible.

The sources also support separating a missing record from an inaccessible one. A file can be present in the archive and still unreadable to the incoming owner. The study should record both the presence and the access. A file count alone is not a completeness measure.

Definitions and measures

Define a required record as one the incoming owner needs to perform a named task in the first ninety days. Define completeness as the share of required records that are present, readable, and listed in the index. Define restricted completeness separately for records that require special access. Record the date and the owner so the next review can rebuild the decision.

Measure the presence, the access, and the index match for each required record. Report the three results separately. A record that is present but not indexed is hard to find, while one that is indexed but unreadable is not usable. The combined rate can hide either failure.

Record the time from the transfer date to the first successful access for each required record. A handover that becomes usable only after a month is not complete at transfer. Report the median and the longest case. The measure reflects the incoming owner's experience.

Record the retention rule and the legal-hold status for each restricted record. A record that is kept past its retention date without a hold is a different risk from one that was destroyed early. Report the rule and the status. The study should not treat all restricted records the same.

Sampling and collection

Sample required records from the incoming owner's first-week task list, the retention schedule, and the shared drive index. Include board papers, travel files, correspondence, and personnel notes. Record the task and the record. A task-based sample is more useful than a random folder sample.

Collect the index entry, the file location, the access test result, and the signed transfer record. Mask personal details that are not needed. If a record was supplied verbally, record the conversation and the follow-up. A verbal handover is not a record.

Include a record that the outgoing owner believed was archived but that the incoming owner could not find. The disagreement is the most useful case. Record the search path and the result. The study should show where the index and the archive diverge.

Verification pathway

Test access with the incoming owner's own account and device. A folder that opens for the outgoing assistant may fail for the successor because of a group membership or a local sync. Record the test and the result. The access should be proven, not assumed.

Check the index against the archive for a sample of records. An index entry without a file is a broken handover, while a file without an index entry is a hidden record. Record both directions. The check should include at least one restricted folder.

Confirm that the outgoing owner's access was removed on the agreed date. A transfer that leaves old access open is not complete. Record the removal and the confirmation. The access change is part of the control.

Analysis and reporting

Report the number of required records, the presence rate, the access rate, and the index-match rate. Break the results down by record type, system, and restriction level. Report the restricted records separately. A single completeness rate can hide a serious access gap.

Inspect the failures for patterns. A cluster of unindexed records may point to a folder convention, while a cluster of access failures may point to a group membership. Choose one change, such as a task-based index or an access test. Do not rank owners by completeness when their record mixes differ.

Report the time from transfer to first successful access. A record that is complete on paper but unusable in practice is not complete. Show the median and the longest case. The measure is closer to the incoming owner's first week than a file count.

Limits and next action

The study cannot prove that the index covers every record the role will need or that the retention rule was applied correctly in every case. It also cannot capture a record that was never created. The report should state those limits and avoid treating the index as the whole archive. Record the date and the owner so the next review can rebuild the decision.

Set a repeat review date and keep the required-record list stable. Assign the correction to the executive office lead and give the incoming owner a simple way to report a missing record. The next year-end should test whether the same record type or the same access step fails again. A useful result is a handover that works in the first week.

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. NARA, Records Management.
15. NIST Privacy Framework.
16. IRS, What Kind of Records Should I Keep.

Related research

• Running a Year-End Records Handover for an Executive Office
• Setting Up a New Executive's First Ninety Days of Calendar and Files
• Measuring Onboarding Document Readiness for a New Executive

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.