Research
Assessing Records Retention Duties for Offshore Support Work
Build a record inventory, identify the legal and client drivers, and set a disposal rule that a Philippines support team can actually follow.
On this page
Key stats
The U.S. National Archives and Records Administration requires federal records to be scheduled for disposition, and its guidance distinguishes temporary records from permanent ones.
Methodology
This note reviews records-management guidance from the U.S. National Archives and Records Administration, privacy material from the Philippine National Privacy Commission, and privacy and security guidance from the U.S. Federal Trade Commission. It asks how a buyer and a Philippines-based support team should set retention and disposal rules for the records the team handles. The analysis is a planning aid for a contract and an operating procedure, not legal advice. It does not claim that one retention period fits every record type or that a vendor's schedule satisfies a client's own obligations.
Evidence summary
Start with a record inventory rather than a retention policy. List the records the team creates, receives, or stores, including tickets, call notes, approval emails, identity documents, invoices, and reports. For each one, note where it lives, who can access it, and which business process depends on it. A policy written before the inventory often covers the obvious files and misses the shared drive where the real copies accumulate.
Identify the drivers behind each retention period. A record may be kept for a client contract, a tax rule, a privacy obligation, an audit requirement, or a legal hold. Write the driver beside the record so the team knows why the period exists. If nobody can name a driver, the record may be kept by habit rather than by duty. That question alone often reduces the volume of stored data.
Separate the client's records from the provider's own records. The client may own the customer file and set its retention, while the provider must keep employment, payroll, and tax records for its own obligations. A support team can hold both types in the same tool, which makes the boundary easy to blur. Label each record by owner and driver before setting a disposal date.
Translate the retention period into a concrete event. A rule that says keep for seven years is incomplete until it states seven years from what: the transaction date, the end of the contract, the final payment, or the closure of an audit. Write the trigger and the disposal date calculation. A rule with an unclear trigger is usually applied differently by each supervisor.
Do not keep everything to avoid a decision. Excessive retention increases the cost of storage, the exposure in a privacy incident, and the time spent searching for the current version. It also makes a legal hold harder to apply because the team cannot tell which copies are in scope. A defensible schedule names what to keep, for how long, and what to delete.
Build a disposal step with evidence. When a record reaches the end of its period, the owner should confirm that no hold applies, dispose of every copy in scope, and record the date and method. Include backups and shared drives in the scope, or state why they are excluded. A deletion that removes the primary file but leaves an exported copy is not a completed disposal.
Handle legal holds before any routine deletion. A hold may arise from a dispute, an investigation, or a regulator's request, and it can override the normal schedule. Name the person who can declare a hold and the process for notifying the team. Suspend deletion for the affected records until the hold is lifted in writing. A hold that lives only in one manager's inbox will not reach the night shift.
Keep the schedule short enough that the team can apply it without a legal review. A one-page table with the record type, the driver, the trigger, the retention period, and the owner is usually enough. Long prose policies are often filed and forgotten, while a short table can be checked at the moment of disposal. Review the table with the people who handle the records so the steps match the tools they use.
Assign a records owner for the account and a backup. The owner confirms disposal, answers questions about the schedule, and raises a hold when a dispute appears. The backup keeps the process alive during leave, which is when disposal mistakes often happen. Record both names in the client file and update them at handover. A schedule without an owner is a document that waits for someone else to apply it.
Make access and retention work together. A record that is kept too long but accessible to everyone is a larger risk than the same record kept in a restricted archive. Limit access to the people who need the record for the stated purpose. Review the access list when a person changes roles. Retention without access control is only half of the control.
Ask the client to confirm the retention expectations at renewal. A client may have a new policy, a new regulator, or a new record type that the original schedule did not cover. Record the confirmation and the date. If the client's requirement conflicts with the provider's own duty, escalate the conflict rather than choosing one silently. Keep the client's response with the current schedule.
Review the schedule annually and when the service, tools, or data categories change. A new tool can create a new copy of every record, and a new workflow can add a record type that nobody classified. Keep the inventory, the drivers, and the disposal log in one place. The test of the schedule is whether a new coordinator can apply it without asking which rule wins.
Build the inventory
List each record type, where it lives, who can access it, and which process depends on it. Include shared drives, exports, and backups. Mark the owner of the record. Review the list with the team that does the work. Update it when a tool or workflow changes.
Identify the drivers
Write the contract, tax, privacy, audit, or legal reason beside each record. A period without a driver is a habit rather than a duty. Ask the client to confirm its requirements. Record the source of each rule. Escalate a conflict instead of guessing.
Set the trigger
Define the event that starts the retention period, such as the transaction date, contract end, or final payment. Show how the disposal date is calculated. Apply the same trigger across the team. Record the calculation in the schedule. Review the trigger when the contract changes.
Apply legal holds
Name the person who can declare a hold and the notice path to the team. Suspend deletion for the affected records. Require a written release before disposal resumes. Keep the hold notice with the record inventory. Test that the night shift receives the notice.
Dispose with evidence
Confirm that no hold applies, remove every copy in scope, and record the date and method. Include exports and shared drives or state the exclusion. Name the person who verified the disposal. Keep the log for the review. Do not delete the log with the records.
Review annually
Reopen the inventory and the schedule once a year and when the service changes. Confirm the client's expectations at renewal. Check for new record types created by a tool or workflow. Update the drivers and triggers. Record the next review date.
FAQs
Does the provider own the records it creates for a client?
Ownership depends on the contract and the applicable law. The agreement should say which party owns each record type and who may access, retain, and delete it. A provider may still have its own recordkeeping duties for employment and tax records.
How long should support tickets be kept?
There is no single period. The answer depends on the client's contract, the purpose of the record, and any legal or audit requirement. Set the period from a named driver and state the trigger that starts it.
Can we delete records at the end of the contract?
Only after confirming that no legal hold or retention duty applies. The agreement should describe the deletion step, the systems covered, and the verification the provider will give. Some records may need to be retained for a defined period.
What should happen when a legal hold is declared?
Suspend deletion for the affected records, notify the team through a documented path, and keep the hold notice with the inventory. Resume disposal only after a written release from the person who declared the hold.