These cookies are required for the website to function properly. They ensure security, enable basic features like page navigation, and store user session data. You cannot disable these cookies.
- HRMS with Workforce Analytics
- Features
- Review and evidence
Review and evidence
Keep a review decision, evidence and the resulting action with the snapshot revision.
OverviewReview decisions pending×
HRMS with Workforce Analytics · Review and evidence
New
Review decisions pending
Approval conditions
| Source revision | Decision | Reviewer | Source | Evidence reference | |
|---|---|---|---|---|---|
| 850 | Pending | WS-10239 | ER-512 | ||
| 190 | Pending | WS-15215 | ER-195 | ||
| 410 | Pending | WS-41997 | ER-841 | ||
| 110 | Pending | WS-81681 | ER-191 | ||
| 290 | Pending | WS-63429 | ER-378 |
6 of 6 records
ER-512Review decisions · RD-72397
PendingSource revision850
SourceWS-10239
What you can do
Give the reviewer a traceable case
A workforce result is useful when another person can see its date, scope and basis. Review decisions point to a snapshot, name the reviewer and carry the source revision, decision, decision date, reason and evidence reference. That revision is the handoff point: if the figures change, the owner prepares a new review of the changed result.
Supporting documents can hold a title, attachment, document date, external reference, verification flag and verifier. External reconciliations compare expected and confirmed amounts. Follow-up actions record the issue, assigned person, due date, status, completion date and resolution. Together, those records let a people leader move from a headline number to the unresolved question behind it.
How the work is organized
- Decision. Record Pending, Approved, Returned or Rejected against the source revision.
- Evidence. Link the document or external confirmation to the same snapshot.
- Action. Assign a finding and record its resolution rather than hiding the discrepancy.
State history can record the from and to status, occurrence time, source revision, operation key, reason and actor when a snapshot status changes. Use that trail when someone asks why the displayed result differs from a prior meeting pack. The status history is distinct from a review decision: a status change shows what happened to the snapshot, while the decision records a person’s judgment.
What to agree during setup
Name the people who may own and review the reporting cut. Decide what evidence is required for a material adjustment, what makes an external reconciliation complete, and how a returned result goes back to the owner. Set due dates for follow-up work in line with the reporting cycle. Review who may see an attachment before it is shared beyond the people who need it.
A CHRO / VP People role provides read-only visibility over people and performance records. Snapshot and evidence access must be assigned explicitly for the intended review team. Keep the reviewer distinct from the person preparing the result when independence is required by the business.
Check the handoff on an actual case
Suppose an external confirmation differs from the recorded hiring cost. Link the confirmation to the snapshot, mark the reconciliation Difference and assign a follow-up to a named person. The reviewer returns the snapshot with a reason tied to the current revision. After the owner checks the amount, add the corrected evidence, record the action’s resolution and request a decision on the revised snapshot. The earlier decision and status history remain available to explain the change.
What your team sees
- Review decisions pending — Decisions with the reviewer and exact source revision.
- Open follow-up actions — Assigned findings that still need a resolution.
- Snapshots awaiting review — Validated reporting cuts ready for a decision.
Follow the work through
Use Evidence follow-up for a returned result and Workforce snapshot review for the decision sequence.
What it keeps track of
Data model- Review decisions
- Independent reviewer decision recorded against an exact workforce snapshot revision.
- Evidence documents
- Supporting document retained for a workforce snapshot.
- External reconciliations
- Comparison of expected workforce/HR cost against externally confirmed values.
- Follow up actions
- Remediation task raised from a review finding or missing evidence.
- State history
- Append-only audit trail of workforce snapshot status transitions.
- Workforce snapshots
- Periodic dated workforce observation for one organization unit: the analytics grain.
- People
- Named HR and business users (owners, reviewers, approvers) referenced by workforce records.
Who uses it
Permissions- HR Business Partner
- (HRBP) supplies the employment context.
- CHRO / VP People
- Reads authorized enterprise context.
- The named reviewer decides on a snapshot revision; the assigned person resolves a follow-up action.
Set up HRMS with Workforce Analytics your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.