Records Destruction Certification Duties for Executive Support Teams
by ExecutiveAssistantAgency Editorial Team · 6 min read
An analysis of records destruction certification for executive support teams, covering retention schedules, legal holds, vendor evidence, and reconciliation.
In this article
- Destruction is a controlled event
- Know what may be destroyed and when
- Separate retention from legal holds
- Choose a destruction method that fits the record
- Select and qualify the vendor
- Witness and document the destruction
- Handle failed or partial destruction
- Reconcile certificates with the register
- Train the team and define exceptions
- Audit the program annually
Destruction is a controlled event
Shredding a box of old files feels like cleaning, but it is a records action with legal consequences. The organization must be able to show that a record was destroyed only after its retention period ended and that no legal hold required it to be kept. A certificate of destruction is the evidence that connects the action to the authority and the date. Without that evidence, an auditor sees a gap rather than a completed task.
Executive support teams often hold the records that matter most: board minutes, compensation files, signed contracts, and correspondence with regulators. The assistant may not set the retention schedule, but the assistant usually coordinates the destruction. That makes the role responsible for the paperwork that proves the process was followed. A rushed purge can destroy the one document a dispute needed.
Know what may be destroyed and when
Start with the organization's records retention schedule. The schedule should list record categories, the retention period, the triggering event, and the final disposition. A contract may be kept for a number of years after expiration, while a board minute may be permanent. Do not apply a single rule to every document in a folder. The category and the trigger determine the date.
Government requirements vary by record type and industry. The NARA records management guidance explains how federal agencies approach retention and disposition, and the IRS recordkeeping guidance gives a useful reference for common business records. These sources do not replace the organization's own schedule or counsel's advice. They help the team ask better questions. Ask counsel which regulator, if any, sets a minimum for the specific record type.
Separate retention from legal holds
A legal hold suspends destruction for any record that may be relevant to a matter. The hold can arrive from counsel, a regulator, or a threatened dispute. It may cover a category, a person, a date range, or a specific matter. The assistant must know how a hold is communicated and how to confirm that it has been applied to the right systems.
Check for holds before every destruction batch, not only at the start of the project. A hold can arrive after the batch is assembled. Record the name of the person who confirmed the clearance and the date. If a hold is ambiguous, stop and ask counsel. Destroying a record under a hold is far more damaging than delaying a routine purge.
Choose a destruction method that fits the record
Paper records can be shredded, pulped, or incinerated depending on sensitivity and the vendor's capability. Electronic records require more than deleting a file. Confirm whether the method overwrites the media, destroys the device, or relies on a certified sanitization process. A deleted file may remain recoverable on a backup or a shared drive. Ask the vendor to describe what happens to backups and to the metadata that links a file to its owner.
Match the method to the sensitivity of the record. Board materials, personnel files, and regulated data deserve a higher standard than routine correspondence. Record the method in the destruction request and on the certificate. If a vendor uses a subcontractor, confirm that the subcontractor follows the same standard. Do not accept a generic "secure destruction" label without the detail. For regulated data, confirm the standard in writing before the pickup is scheduled.
Select and qualify the vendor
Ask for the vendor's certification, insurance, and audit history before the first pickup. Confirm that the facility is licensed and that the vehicle is secure. Check how the vendor handles chain of custody from pickup to destruction. A vendor that cannot explain the handoff should not receive executive records. Visit the facility or request a recent audit report if the volume is large.
Review the contract for liability, notification, and subcontracting terms. Confirm the turnaround time for the certificate and the process for a failed or partial destruction. Ask whether the vendor provides a witnessed destruction option for highly sensitive material. Keep the vendor's contact and escalation path with the destruction procedure. Store the signed contract with the certificate template and the vendor's after-hours number.
Witness and document the destruction
For high-sensitivity records, arrange for a representative of the organization to witness the destruction. Record the date, time, location, and names of the people present. Count the containers and note the seal numbers before the process begins. The witness should confirm that the containers were destroyed rather than merely collected. Photograph the sealed containers before they leave the loading dock and attach the image to the record.
Capture the certificate number, the method, the weight or volume, and the date of destruction. Attach the pickup manifest and the vendor's certificate to the internal destruction record. If the certificate arrives without a manifest, ask for the missing document before closing the file. A certificate that cannot be tied to a specific pickup is weak evidence. Note the name and title of the vendor representative who signed the certificate.
Handle failed or partial destruction
A vendor may destroy part of a batch and return the rest because of a damaged container or a scheduling problem. Treat the remainder as an open item rather than a completed one. Record what was destroyed, what remains, and where the remainder is stored. Assign a new destruction date and tell the records owner in writing so the inventory is not closed prematurely.
If a certificate is inaccurate, ask the vendor to correct it in writing rather than editing the original. Keep both versions and a note explaining the correction. If the vendor cannot explain a discrepancy, escalate to the records manager and consider a different provider. A certificate with an unexplained gap is worse than no certificate at all. Record the escalation date and the person who approved the replacement.
Reconcile certificates with the register
Maintain a destruction register that lists each batch, the record categories, the date range, the authority, the vendor, and the certificate number. Reconcile the register against the certificates at the end of each quarter. Look for batches that were picked up but never certified, and certificates that do not match a pickup. The reconciliation is where most errors surface. Assign one person to own the reconciliation and a backup who understands the register.
Update the inventory to show that the records are no longer held. Remove the entries from the active location list and note the destruction date. Do not delete the register entry itself, because the organization may need to prove that the record existed and was destroyed. The register is a permanent control record, not a working to-do list. Keep the register backed up in a system that survives a change of staff or software.
Train the team and define exceptions
Brief the executive support team on the difference between routine disposal and certified destruction. A draft in a shared folder may be deleted under a routine rule, while a signed original may require a certificate. Give the team a short decision tree and a named contact for questions. Training should include the most common mistakes, such as destroying a folder because it looked old.
Define the exception process for records that cannot be destroyed on schedule. A pending investigation, a tax question, or a vendor dispute may justify an extension. Record the reason, the approver, and the new review date. An exception without a review date becomes permanent by default. Review open exceptions at the quarterly records meeting and close the ones that no longer apply.
Audit the program annually
Once a year, review the retention schedule, the legal hold process, the vendor list, and the destruction register. Sample a few batches and confirm that each has an authority, a certificate, and a reconciled inventory entry. Check whether any record category has changed because of a new regulation or a new system. Update the procedure and retrain the team. Ask the vendor for a current certificate of insurance and keep it with the contract.
Document the audit and the corrective actions. Keep the audit memo with the register so the next reviewer can see what changed. A short list of open actions is more useful than a long narrative. For help managing executive records, destruction evidence, and retention schedules, contact us to discuss assistant coverage. The records retention guide and the signature authority documentation guide cover the controls that sit on either side of destruction.
“My EA handles everything from board prep to multi-city travel, and I finally have time to focus on the work that matters.”
Related Research
Research
Decision Memo Traceability and Retention in Executive Offices
An analysis of decision memo traceability and retention, covering identifiers, version links, approval evidence, access control, retention periods, and archive testing.
Research
Executive Correspondence Retention Duties for Support Teams
An analysis of correspondence retention duties for executive support teams, covering classification, ownership, legal holds, mailbox handovers, disposal, and retrieval testing.
Research
Follow-Up Closure Evidence Standards for Executive Support Teams
An analysis of follow-up closure evidence for executive support teams, covering closure states, commitment records, acceptance criteria, owner confirmation, sampling, and retention.