Define what must be destroyed and when
A destruction log begins with the retention schedule, not with a shredding bin. Identify the record series, the retention period, the trigger event, and the destruction date. A board packet, a personnel file, a signed contract, and a routine travel receipt have different schedules and different owners. Do not destroy a record because it is old or because the file cabinet is full.
Record the schedule version and the person who confirmed it for each series. If a record is part of an open investigation, a litigation hold, an audit, or a pending request, destruction stops. The log should show the hold flag and the person who applied it, because a destroyed record cannot be restored by explaining that the schedule looked expired.
Use an approved destruction method
Paper, electronic files, backup media, and devices need different methods. A cross-cut shredder may be acceptable for routine paper; a contracted destruction vendor with a certificate may be required for sensitive records. Deleting a file from a shared drive does not remove it from backups or sync services. Follow the organization's approved method for the medium.
Do not destroy records at a local copy shop or a personal shredder outside the approved process. If a vendor is used, confirm the chain of custody, the collection date, the container or serial number, and the certificate of destruction. The log should reference the certificate rather than the contents of the documents.
Record the certificate, not the content
The destruction log needs enough information to prove what happened without recreating the confidential material. Record the record series, the date range, the volume or container count, the method, the vendor, the certificate number, the date of destruction, and the authorized approver. Do not list individual document titles if the titles themselves reveal a sensitive matter.
Store the certificate with the log and restrict access to the records owner and the approver. If a regulator or auditor asks for proof, the certificate and the schedule reference should answer the question. The log is not a place to paste the contents of a personnel file or a legal memo.
Separate routine shredding from legal holds
Routine shredding can run on a schedule, but a legal hold overrides it. Before a batch is destroyed, check the hold register against the record series, the custodian, and the date range. A hold that applies to “all records concerning the X matter” may reach a file that looks routine. When the scope is unclear, pause the batch and ask the legal owner.
Record the hold check and the date. If a hold is released, do not destroy the records automatically; confirm the new destruction date with the records owner. A hold release is a legal decision, not a signal for the assistant to clear a shelf.
Reconcile the log with the retention schedule
At least annually, compare the destruction log with the retention schedule and the inventory of record series. Look for series that were never destroyed, batches with no certificate, certificates with no matching log entry, and holds that were applied but never released. The reconciliation is a control, not a paperwork exercise.
Sample a few entries and trace them back to the schedule and the certificate. If the vendor cannot produce a certificate for a batch, mark the gap and escalate. Do not estimate a destruction date or create a replacement certificate. The integrity of the log depends on recording what actually happened, including the exceptions.
Review vendor evidence and improve the process
For a vendor destruction, review the certificate, the service report, and any chain-of-custody document. Confirm that the vendor's name, address, and certification match the approved contract. If the vendor uses a subcontractor, the records owner should know and the certificate should identify the actual destruction site.
At the annual review, update the schedule references, the approved vendor list, and the training for the people who handle records. A short refresher on holds and approved methods is more useful than a long policy reminder. The goal is a log that can be understood by someone who was not in the room and that never destroys a record the organization still needs.