HR policy or compensation-cycle rollout

A new leave policy, a hybrid-work policy or the yearly compensation cycle is a project even when no new system is involved. Each one needs decisions, approvals, a build step, manager briefings and a launch date. Two things tend to go wrong: an approval is assumed, or managers hear about the change at the same time as their teams.

Which template to use

Use the General project template. It has four phases (Plan, Design, Build, Launch), a gate at the end of each, and the workstreams Planning, Design, Delivery and Communications. The HR rollout templates are built around a system implementation and would give you payroll runs and data-migration criteria you do not need here.

If the change needs system work, such as new accrual rules for a leave policy, track that work as tasks in the Delivery workstream.

Use gates for approvals

Policy and pay changes depend on sign-offs. Put each one in a gate as an exit criterion, so it is visible and recorded:

Phase	Policy rollout	Compensation cycle
Plan	Scope and reason agreed with the sponsor	Budget and timeline approved by Finance
Design	Policy text reviewed by Legal	Guidelines and eligibility rules approved
Build	System rules configured and tested	Planning sheets or system set up and tested
Launch	Managers briefed before employees	Letters approved and manager conversations scheduled

These criteria are examples to add yourself. When someone ticks one, HRjects records who and when. That record is useful when a question comes up later about who approved what.

Map what changes for people

In Process maps, write the current steps of the affected process beside the future steps. For a leave policy, that is how someone requests leave now and how they will request it afterward. Log anything unresolved as a gap, such as "Who approves when a manager is on leave", and turn it into a task so it gets an owner.

Check readiness before launch

Edit the readiness checklist to fit. Useful items: final text or guidelines approved, system changes tested, managers briefed, employee communication ready, questions channel staffed. The project shows Go at 90% with no open critical issues. Use the Issues log for problems found while testing, and after launch for questions that expose a hole in the policy.

Keep personal data out

This matters most for compensation. HRjects is for the project plan. Do not enter salaries, increases, ratings or anything about named employees. Track "Planning sheets sent to all department heads" as a task and keep the sheets in your compensation system.

Reuse it

A compensation cycle repeats every year. When the cycle ends, save the project as a template and start the next one from your own plan.

Also see

Operations process change uses the same template in a similar way. Roadmap and phase gates explains how sign-offs are recorded.