Choose a template: Startup, Enterprise or General
What each of the three built-in templates contains, how to pick one, and what the example-data option does.
Every project starts from a template. The template sets the phases, exit criteria, workstreams, teams, starter tasks, process list and readiness checklist. You can change most of these afterward.
The three built-in templates
| Startup HRIS rollout | Enterprise HCM rollout | General project | |
|---|---|---|---|
| Best for | One system, one country, one go-live | A long rollout in regional waves | Any team's project |
| Phases | Discovery and current state; Future state and vendor selection; Configuration, migration and integration; Testing, change and go-live | The same four phases | Plan; Design; Build; Launch |
| Extra exit criteria | None | Regional process variations documented; rollout waves sequenced by region | None |
| Workstreams | Core HR, Payroll, Benefits, Time & absence, Data migration, Integrations, Testing, Change & training | The same eight | Planning, Design, Delivery, Communications |
| Teams | HR, IT, Finance, Legal, Vendor | The same five | Project lead, Team, Stakeholders, Vendor |
| Process maps | Hire to onboard, Time off request, Payroll run, Benefits enrollment, Offboarding | The same five | One blank map |
| Parallel payroll tracker | Yes, two runs to start | Yes, two runs to start | No |
| Readiness checklist | HR items, including payroll and data validation | The same, plus regional privacy and works council sign-offs | Five general items |
How to pick
- Choose Startup HRIS rollout if you are putting in one HR or payroll system for one country with a small team.
- Choose Enterprise HCM rollout if you are rolling out across regions and need compliance sign-offs such as works council consultation and regional privacy reviews.
- Choose General project for work that is not an HR system rollout: an IT tool, a finance system, a process change, a policy rollout.
If you have saved a project as a template, it appears in the same list. See saving a project as a template.
The example-data option
When you create a project from a built-in template, you can fill it with an example rollout. The example is part-way through. It has ticked exit criteria, tasks in different statuses, filled-in process maps with pain points and gaps, at least one logged issue, a business case with figures and, in the HR templates, one payroll run that missed tolerance. The people and figures are made up.
Use it to explore or to show a colleague how HRjects works. For a real project, leave the option off. You get the same structure with nothing ticked, no owners assigned, empty process maps and zero in every figure.
After you choose
A template is a starting point. Editors and Owners can add and remove exit criteria, tasks, process maps, cost lines and readiness items. The phase names, workstreams and teams come from the template and stay as they are.