Can Performance Review Status Be Reported Without Scoring People?

Research question: which performance-review cycle facts a Philippines-based coordinator can report while managers retain ratings, interpretation, feedback, calibration, and employment decisions? The purpose is to test a narrow administrative evidence model. It is not a legal opinion, an employment decision, or a claim that one workflow fits every employer.

Why this matters to a staffing buyer: Leaders need to know whether a review cycle is moving, but status dashboards can quietly become shadow performance files. A label such as at risk may describe a late form, a manager delay, a disputed goal, or an employee judgment. Those meanings should not be collapsed.

Source basis: the Philippine Data Privacy Act implementing rules address transparency, legitimate purpose, proportionality, accountability, security, access, retention, and outsourced processing. Current National Privacy Commission materials reinforce the need to govern third-party processing. DOLE materials provide labor context, and NIST SP 800-53 provides control language for access, audit, personnel, and system records. These sources frame questions; the responsible organization must determine its actual obligations.

Unit of analysis: one required review milestone for one role in one defined cycle. Keeping that unit fixed prevents a reassuring batch total from hiding an unresolved person, record, promise, or decision. Each observation receives a stable reference so reviewers can trace a conclusion without relying on names or copied sensitive content.

Method: build eighty-four synthetic milestone histories covering goal confirmation, employee input, manager input, secondary review, calibration meeting, feedback delivery, acknowledgment, correction, reopened review, manager change, approved leave, inaccessible form, and confidential escalation. Use invented people, organizations, dates, and identifiers only. A study administrator keeps the seeded answer key away from reviewers until classification is complete.

The review record contains cycle and milestone identifier, role reference, due date, expected owner, observable receipt event, source system, reminder history, access class, dependency, approved extension, exception code, next action, and closure event. Every field needs a stated purpose and source. Blank, unknown, not applicable, and restricted are separate values; reviewers may not convert any of them into a convenient assumption.

Before review, the responsible business owner defines the accepted states, required evidence, access roles, response windows, and stop conditions. The definitions are frozen for the first pass. If a rule changes, the study records a new version and reruns affected cases instead of silently editing prior outcomes.

Primary measure: correct status reporting without inferring performance. Secondary measures include disclosure to the wrong viewer, reminder sent to the wrong owner, false overdue status, overwritten correction, hidden reopened review, unsupported rating inference, and time to locate evidence. Reviewers cite the exact source event for every classification and use cannot determine when the record does not support a conclusion. Confidence without evidence counts as an error, even if the guess matches the seeded answer.

Error taxonomy: Received does not mean accepted; acknowledged does not mean agreed; a missed deadline does not indicate poor employee performance; and a manager draft is not a final rating. The protocol treats each as a separate state and forbids translating administrative delay into a people conclusion.

Decision boundary: The coordinator can maintain milestones, issue approved reminders, record receipt, prepare meeting logistics, and route access or workflow problems. Managers and HR retain goals, ratings, calibration, feedback, extensions, disputes, corrective action, and every employment consequence.

Comparison design: Compare a role-based milestone dashboard with a spreadsheet that contains ratings and narrative comments. Test whether managers can act on missing steps using references and controlled links rather than copying substantive feedback into the coordination layer. Reviewers receive the same underlying cases in randomized order. The study compares correctness, unnecessary access, unresolved work, and review time, not just speed or completion percentage.

Privacy and security treatment: Restrict review content by role and avoid names in aggregate operating reports when a stable internal reference is sufficient. Examine exports, email subjects, calendar invitations, and notification previews for leakage, not only the main application page. The protocol records viewers, exports, notifications, and linked-system propagation because a safe-looking tracker can still reproduce protected information elsewhere.

Negative controls matter. Include ordinary cases that should proceed, difficult cases that should stop, and misleading cases with a plausible but insufficient signal. A design that never stops is not controlled; a design that stops everything is not operationally useful.

Analysis plan: Calculate status accuracy and routing accuracy by milestone. Report confidentiality events and judgment inferences as distinct serious failures even if the overall status count is correct. Keep approved extensions separate from genuinely overdue work. Two reviewers classify an overlapping sample independently. Disagreements are preserved, categorized, and resolved by the named owner; they are not averaged away or settled by whoever entered the record first.

Quality thresholds must be set before reviewers see outcomes. The owner defines acceptable routing accuracy, maximum unresolved age, serious-error classes, and the conditions that stop a pilot. A faster workflow does not pass if it increases unauthorized decisions, disclosure, or false closure. Results include counts and denominators for every threshold, plus the cases excluded and why. This prevents a favorable percentage from being created by removing difficult records after the fact.

A repeatability check follows the first review. A second reviewer receives the written definitions, a clean copy of the cases, and no coaching from the first reviewer. The study records agreement by state and error class. Low agreement points to an unclear rule or insufficient evidence; it is not automatically a training failure. The owner must clarify the rule, version the change, and retest affected cases before using the process on live work.

Provider evidence should match the proposed operating model. Buyers can request a sanitized role demonstration, sample permission view, blank register, escalation map, and example audit export. Each artifact answers a different question and carries its own date and scope. Marketing language, a policy document, or a successful demo cannot establish how every live case is handled. Unavailable evidence remains an open question rather than a negative or positive assumption.

Uncertainty is part of the result. Missing source events, ambiguous definitions, unavailable owners, integration delays, and inaccessible records receive explicit codes. The report separates observed fact, rule-based classification, owner decision, and researcher inference so readers can see where judgment entered.

Limitations: The study does not assess performance, fairness of ratings, quality of feedback, validity of a review system, or compliance with a specific employment process. Synthetic cycles omit power dynamics, retaliation concerns, and unrecorded conversations. A live pilot should begin with a small approved queue, named reviewers, least-privilege access, monitored exceptions, and a stop rule for unexpected sensitive data or decisions outside the written lane.

Decision use: The appropriate output is a cycle operations report with milestone definitions, counts, aged exceptions, source links, and next owners, deliberately excluding ratings and narrative performance content from the coordination view. Buyers can ask a provider to demonstrate this record with sanitized examples, but a successful demonstration is point-in-time evidence, not proof of continuous compliance or a guarantee of outcomes.

Sources checked September 22, 2026: National Privacy Commission, Implementing Rules and Regulations of the Data Privacy Act of 2012 (https://privacy.gov.ph/implementing-rules-regulations-data-privacy-act-2012/); National Privacy Commission, Advisories and Circulars (https://privacy.gov.ph/pips-and-pics/advisories-circulars/); Department of Labor and Employment Bureau of Working Conditions, Labor Advisories (https://bwc.dole.gov.ph/issuances/labor-advisories/); Department of Labor and Employment Bureau of Working Conditions, guidance on flexible work arrangements (https://bwc.dole.gov.ph/dole-bwc-provides-guidance-on-flexible-work-arrangements-while-safeguarding-workers-rights/); National Institute of Standards and Technology, Security and Privacy Controls for Information Systems and Organizations, SP 800-53 Revision 5 (https://csrc.nist.gov/pubs/sp/800/53/r5/upd1/final). These primary government sources establish general legal or control context. They do not approve a provider, determine a worker's rights, or decide a specific employment matter.