Key takeaways
- Audit contact duplication by matching records to a stable identity key and a named source of truth, so a merge does not quietly delete the only correct phone number.
- Keep the measurement definitions fixed across the review period so the next cycle can compare like with like.
- Record the correction owner and a repeat date before the file is closed.
Question and scope
This audit asks whether the executive office holds more than one record for the same person across its contact systems and whether the duplicates agree. The unit is one contact identity. The review follows the person across the address book, the customer system, the email directory, and the assistant's list. It does not judge whether the contact should be retained.
Set the scope to the contacts the executive office uses most often, such as board members, key clients, and regular suppliers, and fix a review period. A full address book audit is large and quickly stale. Record the list and the period. The sample should include contacts that appear in more than one system.
Include at least one contact who changed role, one who changed company, and one who has two phone numbers in active use. A role change is the most common cause of a duplicate that looks current. Record the change and the record. The sample should test the point where the systems most often diverge.
What the sources establish
The BLS description of administrative support work establishes that maintaining contact records is a core assistant task but does not define a data standard. The NIST cybersecurity framework describes identity and access management as a control area, which supports a stable identity key. The National Archives records management guidance describes maintaining records with sufficient authenticity and integrity, which supports a documented source of truth. The sources do not establish how many contact systems an office should run.
The sources do not set a retention period for contact records or a required merge procedure. They also do not say which system should be authoritative. The audit therefore measures the office's own data rule and the evidence it keeps. The report should keep that local scope visible.
The sources support treating a contact record as a controlled record rather than a personal address book. A record that exists in four systems without a source of truth is a coordination risk. The audit should test both the duplication and the agreement between copies. A tidy list can still contain four different phone numbers.
Definitions and measures
Define a duplicate as two records that refer to the same person, even when the names are spelled differently or one record uses a nickname. Keep the matching rule fixed across the sample. The audit should record the evidence used to decide that the records are the same person. The rule should be written before the matching begins.
Define the source of truth for each field, such as the customer system for the account owner and the directory for the work phone. A field without a named source will be merged from whichever record was opened last. Record the field and the source. The rule should be agreed with the system owners.
Measure the number of records per identity, the share of fields that disagree, and the age of the last update in each system. Record the measures together. A duplicate that agrees on every field is still a maintenance cost, while a single record with a stale phone number is a usage risk. The report should show each measure at the identity level.
Sampling and collection
Sample identities from the executive's recent outbound mail, the meeting attendee lists, and the contact systems themselves. Include a contact who was added by an assistant and one who was imported from a conference list. Record the source and the entry method. A system-only sample will miss the contacts that live in a personal folder.
Collect the record from each system, the last update date, the owner, and any note about a merge. Mask the personal detail that is not needed for the review. If a merge was done manually, record who did it and when. A merge without a note is difficult to reverse later.
Include a contact who left a company and one who returned to a previous role. A departure often creates a duplicate when the old record is retained and a new one is created. Record the event and the record. The sample should test how the office handles a change rather than only a steady state.
Verification pathway
Check each duplicate by comparing the phone, the email, the role, and the company against a current source such as the person's own signature or the company website. A match on name alone is not enough to merge two records. Record the comparison and the result. The audit should keep the evidence for each merge decision.
Confirm that the merge was performed in the system of record and that the other systems were updated or linked. A merge in one address book can leave a duplicate in the customer system and a third copy in the assistant's list. Record each system and the status. The audit should test the whole chain, not only the first system.
Test one merge by asking a colleague who did not perform it to find the contact and confirm the preferred phone number. A merged record that cannot be found is worse than a duplicate that can. Record the test and the result. The test should use the search the team actually uses.
Analysis and reporting
Report the number of identities reviewed, the share with more than one record, the share with conflicting fields, and the number of merges performed. Break the results down by system and by contact type. Report the contacts with no clear source of truth separately. A single duplicate count hides the difference between a harmless copy and a conflicting record.
Inspect the conflicts for patterns. A cluster of stale phone numbers may point to a system that is no longer updated, while a cluster of name variants may point to an import without a key. Choose one change, such as a required identity field or a monthly merge review. Do not rank assistants by the number of duplicates they inherited.
Report the time spent reconciling duplicates and the contacts that were missed because the wrong record was used. A duplicate that caused a misdirected message is a cost that the count alone does not show. Show the examples and the fix. The measure should connect the record to the work it supports.
Limits and next action
The audit cannot prove that a merged record is correct in every field or that the source of truth will remain current. It also cannot capture the contacts that exist only in a phone or a personal notebook. The report should state those limits and avoid treating a clean merge as a guarantee. Keep the comparison evidence and the merge log with the study so the next reviewer can check the same decision.
Set a repeat audit date and keep the matching rule stable. Assign the correction to the contact data owner and give the executive office a one-page source-of-truth map. The next quarter should test whether the same system or the same import creates a new duplicate. A useful result is one contact record that the whole office can trust.
Sources
- Secretaries and Administrative Assistants, U.S. Bureau of Labor Statistics, Occupational Outlook Handbook.
- Executive Secretaries and Executive Administrative Assistants, U.S. Bureau of Labor Statistics, Occupational Employment and Wage Statistics.
- Executive Secretaries and Executive Administrative Assistants, O*NET OnLine.
- Business Formation Statistics, U.S. Census Bureau.
- Nonfarm Business Sector: Labor Productivity, Federal Reserve Economic Data.
- Productivity Statistics, OECD Data Explorer.
- World Development Indicators, World Bank DataBank.
- ILOSTAT Labour Statistics, International Labour Organization.
- 2024 Work Trend Index Annual Report, Microsoft and LinkedIn.
- The economic potential of generative AI, McKinsey Global Institute.
- Creating helpful, reliable, people first content, Google Search Central.
- Search Engine Optimization Starter Guide, Google Search Central.
- Dear Manager, You Are Holding Too Many Meetings, Harvard Business Review.
- BLS, Secretaries and Administrative Assistants.
- NIST, Cybersecurity Framework.
- U.S. National Archives, Records Management.
Related research
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.
Turn the finding into a support scope.
Bring the workflow that feels hardest to see. We will help define the role, the evidence it should maintain, and the decisions that stay with leadership.
Talk through the role