CEO Executive Assistant
What evidence should an executive assistant coordinate before an executive device is reassigned, returned, donated, recycled, or destroyed?
A CEO replaces a phone and laptop before a trip. Both devices contain synced mail, calendar attachments, authentication apps, downloads, and local notes. A trade-in deadline is approaching, but backups, holds, account removal, and sanitization ownership are unclear.
This research guide converts current primary guidance into a narrow CEO-office workflow. It distinguishes sourced facts from our operational analysis, identifies uncertainty, and leaves legal, employment, security, records, and business judgments with qualified owners. The sources were checked on 2026-10-05; their requirements and advice can change, and organizations must account for their own geography, contracts, systems, policies, and risk.
- Guidelines for Media Sanitization, NIST Special Publication 800-88 Revision 1 — National Institute of Standards and Technology; checked 2026-10-05.
- Protecting Personal Information: A Guide for Business — Federal Trade Commission; checked 2026-10-05.
- Disposing of Consumer Report Information? Rule Tells How — Federal Trade Commission; checked 2026-10-05.
Method and limitations
We reviewed the cited authorities for controls that can be observed in executive-assistant work: purpose limitation, named ownership, trustworthy source evidence, access restriction, independent verification, version history, exception handling, and documented closure. We then applied those controls to the scenario above. This is practical operational analysis, not legal, employment, cybersecurity, privacy, records-management, or compliance advice. The cited publishers do not endorse this site or this synthesis.
The method has important limits. Public guidance cannot establish the facts of a particular candidate, device, message, account, incident, or organization. A checklist cannot replace product-specific testing or professional judgment. Local law, collective agreements, employment rules, contractual duties, and sector obligations may change the correct process. Where the source and the operational recommendation differ, the source describes the authority’s guidance; the workflow is our inference for CEO-office coordination.
Identify the asset and every attached data path
Record the serial or asset identifier, assigned person, storage media, management status, synced accounts, removable cards, eSIM or carrier relationship, authenticator registrations, and peripheral storage. The visible device is not the whole system. Copies may remain in cloud services, backups, downloads, printers, vehicles, or support tools.
Resolve preservation before sanitization
Ask the records, legal, security, and business owners whether any material requires migration or preservation. A routine refresh must stop if an authorized hold or incident instruction applies. Preserve through an approved method and record the source, destination, scope, and verifier; do not copy the whole device into an assistant-controlled folder.
Select a method based on media and destination
NIST organizes sanitization around clear, purge, and destroy concepts and emphasizes verification and documentation. The technical owner chooses a method suited to the media, data sensitivity, and whether the asset will be reused. Consumer reset language, encryption assumptions, or physical damage should not be treated as proof without the approved technical assessment.
Reconcile identities, custody, and final destination
Remove delegated access, management enrollment, registered authenticators, recovery routes, carrier services, and inventory assignments as applicable. Maintain custody through return or destruction. Record the final recipient and evidence, then apply the approved retention rule to the retirement record itself.
A twelve-field control record
The control record should be short enough to use during real work and precise enough for a different authorized person to reconstruct the decision. These fields are a starting model, not a universal retention requirement.
1. Asset identifier
Record asset identifier in the approved system and name the person accountable for its accuracy. Link to source evidence rather than copying restricted information into a general tracker. Show whether the item is verified, assumed, disputed, expired, or awaiting a decision. If it changes after approval, preserve the version that informed the earlier decision and route the change to the appropriate owner.
2. Assigned executive
Record assigned executive in the approved system and name the person accountable for its accuracy. Link to source evidence rather than copying restricted information into a general tracker. Show whether the item is verified, assumed, disputed, expired, or awaiting a decision. If it changes after approval, preserve the version that informed the earlier decision and route the change to the appropriate owner.
3. Media and peripherals
Record media and peripherals in the approved system and name the person accountable for its accuracy. Link to source evidence rather than copying restricted information into a general tracker. Show whether the item is verified, assumed, disputed, expired, or awaiting a decision. If it changes after approval, preserve the version that informed the earlier decision and route the change to the appropriate owner.
4. Data classification
Record data classification in the approved system and name the person accountable for its accuracy. Link to source evidence rather than copying restricted information into a general tracker. Show whether the item is verified, assumed, disputed, expired, or awaiting a decision. If it changes after approval, preserve the version that informed the earlier decision and route the change to the appropriate owner.
5. Preservation decision
Record preservation decision in the approved system and name the person accountable for its accuracy. Link to source evidence rather than copying restricted information into a general tracker. Show whether the item is verified, assumed, disputed, expired, or awaiting a decision. If it changes after approval, preserve the version that informed the earlier decision and route the change to the appropriate owner.
6. Approved sanitization method
Record approved sanitization method in the approved system and name the person accountable for its accuracy. Link to source evidence rather than copying restricted information into a general tracker. Show whether the item is verified, assumed, disputed, expired, or awaiting a decision. If it changes after approval, preserve the version that informed the earlier decision and route the change to the appropriate owner.
7. Technical owner
Record technical owner in the approved system and name the person accountable for its accuracy. Link to source evidence rather than copying restricted information into a general tracker. Show whether the item is verified, assumed, disputed, expired, or awaiting a decision. If it changes after approval, preserve the version that informed the earlier decision and route the change to the appropriate owner.
8. Verification result
Record verification result in the approved system and name the person accountable for its accuracy. Link to source evidence rather than copying restricted information into a general tracker. Show whether the item is verified, assumed, disputed, expired, or awaiting a decision. If it changes after approval, preserve the version that informed the earlier decision and route the change to the appropriate owner.
9. Account and authenticator cleanup
Record account and authenticator cleanup in the approved system and name the person accountable for its accuracy. Link to source evidence rather than copying restricted information into a general tracker. Show whether the item is verified, assumed, disputed, expired, or awaiting a decision. If it changes after approval, preserve the version that informed the earlier decision and route the change to the appropriate owner.
10. Custody transfer
Record custody transfer in the approved system and name the person accountable for its accuracy. Link to source evidence rather than copying restricted information into a general tracker. Show whether the item is verified, assumed, disputed, expired, or awaiting a decision. If it changes after approval, preserve the version that informed the earlier decision and route the change to the appropriate owner.
11. Final destination
Record final destination in the approved system and name the person accountable for its accuracy. Link to source evidence rather than copying restricted information into a general tracker. Show whether the item is verified, assumed, disputed, expired, or awaiting a decision. If it changes after approval, preserve the version that informed the earlier decision and route the change to the appropriate owner.
12. Record retention trigger
Record record retention trigger in the approved system and name the person accountable for its accuracy. Link to source evidence rather than copying restricted information into a general tracker. Show whether the item is verified, assumed, disputed, expired, or awaiting a decision. If it changes after approval, preserve the version that informed the earlier decision and route the change to the appropriate owner.
Decision gates for the CEO office
Proceed only when the purpose, accountable owner, authority, source evidence, audience, and completion proof are clear. Pause when an essential fact is unverified, a required reviewer is unavailable, the request conflicts with policy, or the requested action would be difficult to reverse. Escalate when the request crosses legal, employment, security, financial, privacy, or governance boundaries. An escalation should identify the decision needed and the last useful decision time without pressuring the owner to approve an unsupported choice.
Urgency changes the cadence, not the evidence standard. A fast path can shorten the record to verified facts, material uncertainty, decision owner, safe options, and next checkpoint. It should not remove independent verification, combine incompatible roles, or turn an assistant’s access into authority. If no approved path exists, preserve the request and stop condition while the accountable owner decides.
Quality review before closure
- Sample asset identifier against its authoritative source. Log a mismatch, missing owner, or expired check as an exception with a due date; do not silently rewrite the history.
- Sample assigned executive against its authoritative source. Log a mismatch, missing owner, or expired check as an exception with a due date; do not silently rewrite the history.
- Sample media and peripherals against its authoritative source. Log a mismatch, missing owner, or expired check as an exception with a due date; do not silently rewrite the history.
- Sample data classification against its authoritative source. Log a mismatch, missing owner, or expired check as an exception with a due date; do not silently rewrite the history.
- Sample preservation decision against its authoritative source. Log a mismatch, missing owner, or expired check as an exception with a due date; do not silently rewrite the history.
- Sample approved sanitization method against its authoritative source. Log a mismatch, missing owner, or expired check as an exception with a due date; do not silently rewrite the history.
- Sample technical owner against its authoritative source. Log a mismatch, missing owner, or expired check as an exception with a due date; do not silently rewrite the history.
- Sample verification result against its authoritative source. Log a mismatch, missing owner, or expired check as an exception with a due date; do not silently rewrite the history.
Review exceptions by consequence. A cosmetic formatting defect is not equivalent to an unverified identity, unclear authority, uncontrolled copy, or missing preservation instruction. Closure requires evidence that the action reached the right system, person, or state—not merely that someone sent an email.
A 30-day implementation pattern
During days 1–5, inventory the current request paths, systems, owners, copies, approvals, and recurring exceptions. Follow at least one normal case and one difficult case from intake to closure. During days 6–10, agree on the minimum record, decision rights, stop conditions, authoritative source, backup owner, and proof of completion.
During days 11–20, pilot the workflow with realistic uncertainty. Test a missing owner, conflicting source, urgent request, unavailable approver, and backup handoff. Verify that the process works without shared credentials, private archives, or unwritten exceptions. During days 21–30, review rework, preventable escalation, access, stale evidence, cycle time, and user confusion. Remove fields that do not support decisions, but retain the controls that make authority and closure visible.
Niche-specific conclusion
Device retirement is complete only when the organization can connect the asset, preservation decision, approved sanitization method, verification, destination, and account cleanup. A factory-reset screenshot alone does not establish that every relevant data path was handled.
An executive assistant creates leverage by making the right decision easier and the wrong action harder: establish the purpose, bring forward current evidence, protect restricted information, preserve the authority boundary, and close the loop in the system of record. That discipline protects executive attention without asking the assistant to become the organization’s lawyer, security officer, HR leader, records manager, or final risk owner.
To connect this control model with hands-on delegation, review our project and task coordination service or contact us about the executive work you want to structure.