Philippines staffing research · Updated September 24, 2026

Which expired records are ready for an authorized disposition decision?

A blinded review study of retention rules, legal holds, system copies, approval evidence, disposition events, and exceptions.

Decision in scope. This protocol is for a buyer considering back-office operations. It tests whether disposition preparation can be delegated without delegating legal-hold, regulatory, contractual, privacy, evidence-preservation, or destruction decisions. It does not publish an industry benchmark, promise a result, or score individual workers. The output is a documented account of one buyer's queue and the conditions that would make a limited handoff reviewable.

Research question. Among records flagged as past their scheduled retention period, which contain enough evidence for an authorized owner to approve retention, destruction, transfer, or further review? Freeze that question before the first record is coded. If the team changes the question after seeing the data, keep the new analysis separate and label it exploratory. That discipline matters because a convenient metric can answer a different question from the one that drove the staffing decision.

Sources and their role. This protocol uses primary guidance checked on September 24, 2026. The 2025 GAO Green Book informs authorization, documentation, control design, monitoring, and response to change. NIST SP 800-53 supplies audit, accountability, access-control, and privacy-control concepts. FTC guidance supports collecting only needed data, limiting retention, and controlling access. The Philippine Data Privacy Act supplies the local privacy context. AAPOR's disclosure elements inform the methods record. These sources shape the protocol. They do not supply observations or outcomes for the buyer.

Population and window. Include all record groups first flagged by one approved retention schedule during two consecutive monthly review cycles, including held, duplicated, inaccessible, transferred, and previously reviewed groups. Register the start and end dates, working timezone, eligible channels, source systems, cutoff rule, and terminal events before export. Keep a screening log that counts included units, test records, out-of-window events, missing identifiers, duplicates, and records withheld because the reviewer lacked permission.

Unit of analysis. Count one defined record group in one controlling system, linked to registered copies and later decisions under a stable disposition identifier. Messages, reminders, edits, exports, system checks, and status changes are events attached to that unit. They are not extra units. This prevents busy cases from inflating the denominator and keeps the result tied to completed or unresolved work rather than activity volume.

Field dictionary. Collect only what the question requires: record-group ID, category, owner, system, creation and cutoff dates, retention-rule version, trigger evidence, hold status and source, duplicate locations, access class, proposed action, approver requirement, decision, execution evidence, exception, and terminal state. Define each field, allowed values, controlling source, timestamp meaning, timezone, change behavior, and missing-value code. Keep direct identifiers in the approved operating system. Use stable pseudonymous identifiers in the analysis file whenever the review does not need a person's identity.

Controlling evidence. Treat the approved retention schedule, documented trigger, current hold register, accountable owner decision, and system disposition event; age or a spreadsheet flag alone does not authorize destruction. If two permitted sources disagree, preserve both values, effective times, and the conflict. Apply only the source-precedence rule approved by the buyer. An analyst must not choose the more convenient source simply because it makes the record look complete.

Outcome coding. Use these registered classes: packet ready, trigger missing, rule ambiguous, active hold, owner missing, duplicate location unresolved, access restricted, retained by decision, approved for destruction, transferred, execution unverified, and unresolved. The codebook should state which conditions can coexist, which class takes priority, and what evidence moves a unit to a terminal state. Keep an unresolved class. Forced success and failure labels hide uncertainty and make later correction harder.

Measures. Show counts and denominators before percentages. The primary output is the distribution of registered outcome classes. Secondary measures are record-group counts, packet-readiness coverage, hold prevalence, missing triggers, duplicate locations, owner wait, decision distribution, execution-evidence coverage, exceptions, and unresolved age. For elapsed time, report medians and selected percentiles rather than a mean alone. Put missingness, exclusions, and censored units beside every affected measure.

Event order. Reconstruct creation, first action, each material transition, owner request, response, correction, and terminal event in the site's UTC timezone while retaining original offsets. Write a deterministic rule for events with the same timestamp. Separate active preparation from owner wait, scheduled delay, system delay, and unknown time when the records allow it.

Review quality. A second reviewer reconstructs every proposed destruction and every hold conflict plus a random sample of retained and transferred groups using the frozen schedule. Both reviewers use the same frozen codebook. Record disagreements before discussion, then publish agreement counts for the reviewed sample and list any rule changed during reconciliation. A material rule change requires recoding the affected population or separating the later analysis.

Worked classification. A folder is older than its schedule, but a registered legal hold names the project under an older code. Preserve the possible link and route it. The coordinator cannot decide that the hold is irrelevant. The example tests whether the rule is understandable. It is not an observed result and should never appear in the findings table. Actual records may show a different pattern, and the reviewer should preserve that result even when it makes the proposed handoff less attractive.

Operating boundary. A Philippines-based specialist may collect permitted records, link identifiers, apply the codebook, maintain the screening log, flag conflicts, and prepare an exception packet. Retention policy, legal-hold scope, regulatory and contractual interpretation, privacy rights, evidence preservation, destruction approval, and exception acceptance remain with authorized owners. A deadline, absent owner, or familiar precedent does not transfer that authority to the coordinator.

Privacy and security. Use named accounts, least privilege, approved export methods, encrypted storage and transfer, and a written retention period. Do not copy an unrestricted inbox or an entire personnel, customer, or transaction history when a bounded event table answers the question. Delete working copies under the buyer's approved rule and report access or data-quality incidents through its existing route.

Bias and alternatives. Treat the findings as a description of the registered queue. Differences may come from work mix, source quality, system design, policy changes, shift coverage, owner availability, or missing events. They do not by themselves show that a coordinator, provider, or location caused the outcome. Use only preregistered subgroups, show small groups as counts, and suppress cells when privacy or instability requires it.

Limitations. Copies may exist in unmanaged systems, triggers can be unclear, holds can use different identifiers, and deletion logs may show an attempt without proving every copy was removed. One buyer and one operating window do not establish causality or external validity. The records cannot prove what a person knew or why an event occurred. Document any change in system, policy, staffing, volume, or access that overlaps the study so a reader can judge comparability.

Decision rule. Before collection, state the evidence needed to start a narrow pilot, repair records and measure again, keep the queue internal, or request specialist review. Include evidence coverage, unresolved risk, owner capacity, and reversibility. Speed is not enough. A quick queue with missing authority or source records is not ready to hand off.

Pilot. If the evidence supports a test, open one bounded queue with a named internal owner and backup. Record permitted actions, stop conditions, review sample, escalation time, and rollback path. Compare the pilot with the registered baseline using the same units and classes. Version any scope change instead of folding new tasks into the original measure.

Conclusion for this niche. Outsource disposition preparation only when the rule, trigger, holds, copies, owner decision, and execution evidence can be reviewed together. OutsourcedCompany.com readers are choosing which company function to hand off first. The process must become observable before the staffing decision: sources stay attributable, exceptions stay visible, and consequential decisions stay with the buyer's named owners.