Actionable HR Data: A Decision and Follow-Up Template

Describe the observation before the explanation

Write what the evidence actually shows, then write the interpretation in a separate field. Keep the record small enough for the decision and avoid copying identifying employee comments into a broad action tracker.

• Work moment: which task, transition or recurring situation needs attention?
• Population and period: whose experience and which dates does the evidence cover?
• Observed evidence: name the record, measure or approved summary and its owner.
• Coverage and limits: who was invited, who contributed and what remains unknown?
• Competing explanation: what else could account for the same pattern?

Complete the action card

Use these fields in your existing project tool or a shared document. This is a template to copy, not a connected task system.

• Decision: what must the accountable person choose?
• Proposed change: what will happen differently, for whom and where?
• Owner: who has authority to deliver it?
• Resources: what time, access or spending has been agreed?
• Delivery check: what observable record will show that the change reached the intended people?
• Outcome check: what work condition should improve, and what other effects must be checked?
• Review date: when will enough relevant work have happened to assess the change?
• Decision at review: continue, adjust, stop or gather missing evidence.

Close the conversation with a realistic commitment

Explain the decision in language employees can recognise. State what was heard, what will happen, what cannot currently change and when an update will be available. Do not ask employees to promise to stay in exchange for an action.

• If the request is feasible, confirm the owner and next step.
• If another team owns it, confirm a handoff and who will return with an answer.
• If the request is declined, explain the reason and any realistic alternative.
• If the matter requires a specialist route, use that route rather than treating it as a routine experiment.

Review delivery and results separately

An action that was not delivered has not tested the proposed change. An action that was delivered may still fail to improve the condition. If results improve, check changes in workload, staffing or participation before claiming the action caused the improvement. Keep the first expectation in the record and add the later finding so the next reviewer can reconstruct the decision.

Why this guide is useful

Use this worksheet when a report ends with a broad recommendation such as improve communication. It makes the proposed change specific enough for the operational owner to accept, question or revise. Complete one card before expanding the work to more teams.

What an action card can establish

The HSE guidance on action planning for work-related stress highlights priorities, resources, responsibility and review. This original worksheet applies a similar planning discipline to an ordinary HR decision. A completed card records an agreed test; it does not prove a diagnosis, guarantee an outcome or replace a specialist process.

Concrete example

Fictional example: a US service team reports that starter questions wait until a weekly meeting. The HR partner checks a sample of onboarding records and invites accounts from different shifts. The manager tests a named daily contact during the next intake, with time allocated for the contact person. At review, the team checks whether starters reached the contact and whether questions were resolved sooner. A fall in departures would remain a separate result to investigate, not an effect automatically attributed to the contact.

Sources

• HSE: record findings and implement action plans