Skip to Content
Z8Z8 Docs
Admin Guide

Implementation Checklist

Check that Z8 actually works for the employees going live, rehearse what it would do for one of them, and see the first real workflows arrive.

The implementation checklist tells you whether your organization is ready to go live with Z8. For the settings that decide whether people can work, it doesn't stop at "a policy exists": Z8 checks each person who is going live against the real setup and lists anyone it doesn't work for, with a link to the setting that fixes it.

Organization owners and admins open it in Settings -> Implementation Checklist. Managers and employees can't see it.


What the Page Shows

From top to bottom:

  1. Go-live readiness: whether the mandatory go-live checks pass, and when they were checked.
  2. Go-live group: who is checked, the teams going live and the go-live exclusions.
  3. Setup progress: how many of the checklist items that apply are done: nine, or eight when payroll export doesn't apply.
  4. The checklist items, each with its status, what Z8 checks and a link to the setting. The First workflows item holds the go-live rehearsal.

Checklist Items

ItemHow Z8 decidesCounts for go-live readiness
Organization structureManual confirmation. Z8 can't know whether your structure is final, so you confirm it yourself.No
HolidaysPresence: an active holiday preset, a preset assignment or a custom holiday.No
Work policiesGo-live check: everyone in the go-live group has an effective work policy today.Yes, mandatory
Approval rulesGo-live check: everyone in the go-live group can get each kind of request decided. Confirming that your approval process is agreed is optional.Yes, mandatory
Payroll exportGo-live check: the payroll setup for the go-live group. Confirming it is optional.Mandatory with an active payroll export target. Without one it doesn't apply: optional, and left out of setup progress
IntegrationsPresence: an active Slack, Discord, Teams, Telegram or webhook configuration.No
NotificationsPresence: notification preferences or a configured notification channel.No
First employee importPresence: the organization has more employees than the founding admin.No
First workflowsFirst-workflow evidence: the first real clock-in, decided request and payroll export.No, never

Presence items tell you something is set up, not that it works. Z8 doesn't test whether notification channels or integrations actually deliver.

Item Statuses

StatusMeaning
Not set upNothing is configured yet. A go-live item can still list the people affected.
ConfiguredSettings exist. For a go-live item, this means its settings exist but nobody in the go-live group could be checked.
VerifiedThe go-live check passed for everyone in the go-live group. Only go-live checks can verify an item. Settings that exist and a manual confirmation never do.
Needs attentionThe go-live check failed for at least one person, or for the whole organization.
UnavailableA lookup failed, so Z8 can't say. Use Retry checks. An unavailable check never counts as passed.
Manually completeOrganization structure, confirmed by an admin. A go-live item never shows it: its status always comes from its check.

The First workflows item has its own statuses: Not started, Under way (some first workflows seen) and All seen.

Setup Progress

Setup progress counts an item when:

  • a go-live item is Verified;
  • a presence item is Configured;
  • Organization structure has a confirmation that still counts (see Manual Confirmations);
  • First workflows shows All seen.

A manual confirmation on Approval rules or Payroll export doesn't count toward progress. Only a passing check does.

Without an active payroll export target, payroll export doesn't apply to your organization. The Payroll export item leaves the progress total, so the checklist can still reach 100%, and First workflows needs only its first two lines. With a target, Payroll export counts like any other go-live item.


Go-Live Readiness

Go-live readiness combines the mandatory go-live checks for everyone in the go-live group. Z8 works it out afresh each time you open the page and never stores it, so it can't be out of date. The header shows when the checks ran, in your display time zone. Retry checks runs them again.

ReadinessMeaning
Ready to go liveEvery mandatory go-live check passed.
Not readyAt least one mandatory check failed. The header counts the people who need attention; someone who fails several checks is counted once. A failure for the whole organization that lists nobody also makes readiness Not ready; the header then names the failing check instead of a count.
UnavailableA check could not be completed, so nothing counts as passed.

With nobody in the go-live group, every check would pass with nobody to check, so readiness shows Not ready: no one is in the go-live group to check. This happens before anyone is added, or when the teams going live have no members yet.

Advisory results are shown as warnings ("1 advisory warning below") and never block going live.

Go-live readiness describes your setup. It doesn't check whether recorded time or absences are correct.

Mandatory, Advisory and Optional

CheckWeight
Work policyMandatory
ApproverMandatory
Payroll setup, with an active payroll export targetMandatory, except missing employment terms, which are advisory warnings
Payroll setup, without an active payroll export targetOptional: the item shows Not set up with an Optional badge, never blocks and is left out of setup progress
Organization structure, holidays, integrations, notifications, first employee import, first workflowsNot part of go-live readiness

Each failing check groups the people it fails for by cause, for example "Team Warehouse has no work policy: 12 employees" or "No organization work policy: 3 employees in no team". When there is no shared cause, people are listed one by one with the detail for each.

Every group shows:

  • the reason;
  • the people affected, ten per page. Invited people carry an Invited badge;
  • a link to the settings page that fixes it. The link only appears when you may open that page;
  • a Rehearse button next to each person, which opens the go-live rehearsal for them.

Someone who fails several checks appears under each one.


The Go-Live Checks

All checks use today in the organization's time zone.

Work Policy

Everyone in the go-live group needs an effective work policy today. Z8 resolves it the same way as elsewhere: a policy assigned to the employee, then one assigned to their primary team, then the organization's. See Work Policies.

Failures are grouped by team ("Team X has no work policy") or as "No organization work policy" for people in no team. The fix link, Assign work policies, opens the Assignments tab of the work policy settings.

Approver

Everyone in the go-live group needs someone who would decide each kind of request they can raise:

  • absence requests;
  • time corrections;
  • work-period submissions;
  • period submissions, when a period submission cadence is set;
  • expense reports;
  • shift requests, when shifts are enabled.

When period submissions or shifts are off, a note says so and that kind isn't checked. Z8 works out each route the way a real request would be routed, through approval policies, change policies and manager assignments, without creating a request. Absence requests are checked for each absence category an approval policy names, and expense reports for report totals around each amount threshold.

Typical failures:

  • a team has no eligible manager, or someone in no team has none;
  • their manager has left and nobody stands in;
  • an approval policy finds no approver, or the approval policies can't be applied;
  • the request would go to the employee themselves;
  • more than one change policy applies, so their entries are refused;
  • no manager or admin can decide their shift requests.

Some people need no approval for a kind. These count as passes and are listed as notes:

  • for work-period submissions, no change policy applies to them or their change policy is in trust mode;
  • owners and admins record their own work directly;
  • no absence category requires approval;
  • they are their own approver, so their requests complete at once;
  • for shift requests, they are the only manager or admin who can decide them, so their own requests wait until they approve them;
  • the owner approves their own expense reports, because nobody else can.

Time corrections always need an approver. When no change policy applies, the change policy is in trust mode, or it only allows changes within its self-service days, people edit their own entries directly, and a note says so. But deletion requests and edits that change an entry's date always go to approval, so Z8 still checks that someone would decide them.

Payroll Setup

The payroll setup check reuses payroll readiness's own setup checks: export target, wage-type mappings, confirmed employment terms and personnel identifiers. The pay-period checks of payroll readiness are left out, because go-live readiness is about setup, not about a pay run.

A payroll setup failure blocks going live only when the organization has an active payroll export target. Without one, payroll export is an optional integration: the item shows Not set up with an Optional badge, never affects readiness and is left out of setup progress.

With an active target:

ResultWeight
No active wage-type mappings, so exports can't classify hoursFailure; lists everyone in the go-live group
Someone in the go-live group shares a personnel identifier with anyone on the current roster, so exports would merge themFailure; each person in the go-live group shows the identifier and who shares it. People outside the go-live group count too, because an export still includes them
No confirmed employment terms covering todayAdvisory warning

Invited people are skipped for employment terms and personnel identifiers until they join.


Go-Live Group

The go-live group is everyone Z8 checks. By default it is:

  • everyone on the current roster, and
  • everyone invited from Settings -> Employees who hasn't joined yet (pending, unexpired invitations),

less any go-live exclusions. Former employees are never in it, and neither are owners or admins without an employee record. The Go-live group card shows how many people are checked.

An invited person is checked through the team their invitation names, or at organization level when it names none: the work policy of that team or the organization, and the team's manager or the organization's approval policies.

Teams Going Live

For a phased go-live, choose the teams going live and select Save teams. With teams chosen, only these people are checked:

  • employees whose primary team is chosen;
  • invited people whose invitation names a chosen team.

Other team memberships don't count. With no team chosen, everyone is checked. Deleting a chosen team removes it from the choice; deleting the last chosen team checks everyone again.

Go-Live Exclusions

A go-live exclusion leaves one employee out of the checks, for example a director who doesn't track time. It affects nothing outside going live.

  1. In the Go-live group card, choose the Employee.
  2. Enter a Reason. It is required.
  3. Select Exclude.

Excluded employees are listed with the reason, who excluded them and when. An exclusion lasts until you Lift it, or ends by itself when the employee becomes a former employee (deactivated, departed or removed from the organization). Reactivating or rehiring them doesn't bring the exclusion back. Only employees on the current roster can be excluded, not invited people.

The reason is part of the employee's personal data export, so write it as you would any note the employee may read.

Choosing teams, excluding someone and lifting an exclusion each write an entry to the organization audit log.


Go-Live Rehearsal

The go-live rehearsal shows what Z8 would do for one person in the go-live group today. It changes nothing, notifies nobody and delivers nothing: no work records, approval requests, notifications, deliveries to payroll providers or audit entries.

Start it from the First workflows item: choose a person and select Rehearse. You can also select Rehearse next to anyone in a failure list. A side panel shows:

  • Work policy: the effective policy today, where it is assigned (to them, their team or the organization), the hours per week or other cycle, and the working days. If none applies, it says so and links to the fix.
  • Approvals: for each covered kind, whether it needs approval, and if so the stages and the people who would decide each one. For time corrections it also says when they edit their own entries directly; deletion requests and date changes still go to the approver shown. It shows when a stage starts only after earlier stages decide, when someone stands in for an approver who has left, when a stage's fallback decides, and when the person is their own approver. A kind that needs no approval says why; a kind that can't be routed gives the reason and a fix link. Absence categories and expense report totals that route differently are shown separately.
  • Payroll: with an active payroll export target, their personnel number (unique or shared, and with whom), whether employment terms are confirmed for today, and whether wage types are mapped. Without one, it says there are no payroll prerequisites.

The rehearsal shows the same result as the go-live checks for that person, traced step by step.


Manual Confirmations

Some things Z8 can't judge, such as whether your organization structure is final or whether your approval process is agreed. For these you record a manual confirmation:

ItemActionWhat the confirmation covers
Organization structureMark completeTeams, team memberships, primary teams, manager links, member roles and custom role assignments
Approval rulesConfirm our approval process is agreed (optional)Change policies and their assignments, approval policies with their stages, conditions and employee groups, and which absence categories require approval
Payroll exportConfirm our payroll export setup is agreed (optional)Payroll export configurations, wage-type mappings and expense wage-type mappings

On Approval rules and Payroll export, a confirmation is a business sign-off only. The item's status still comes from its go-live check, so a confirmation never makes it Verified. Without an active payroll export target, a Payroll export confirmation is kept but changes nothing.

When a Confirmation Goes Stale

When you confirm, Z8 records a fingerprint of the configuration the confirmation covers. On each view it compares the current configuration with that fingerprint. Deleting something counts as a change, for example removing a team member or a wage-type mapping. Unrelated changes, such as adding a holiday or renaming an absence category, don't.

Adding or removing people makes an Organization structure confirmation stale. It covers every employee's role and primary team and every member, so each new hire or removed member changes it. Confirm it again once the people going live are in place.

Note under the itemCounts toward progress
Confirmed {date}Yes
Confirmed {date}, before change tracking: confirmed before Z8 recorded fingerprintsYes, until confirmed again
Settings changed since confirmed on {date}No
Couldn't check for settings changes since confirmed on {date}No

A stale confirmation is kept, not deleted. Review the changes, then select Confirm again, or remove the confirmation. A stale Organization structure confirmation drops the item back to Not set up until you confirm again.

Confirming and removing a confirmation each write an entry to the organization audit log.


First Workflows

The First workflows item shows first-workflow evidence: proof, noticed from real use, that your organization has started working with Z8.

LineWhat counts
First clock-inThe first clock-in by someone in the go-live group. Manual entries and imported work don't count.
First decided requestThe first request by someone in the go-live group that was approved or rejected. Pending requests don't count.
First successful payroll exportThe organization's first completed payroll export. Failed runs don't count.

Each line shows when it happened and who did it, or Not yet. On the payroll export line, someone who has since left is marked Former employee. Because the first two lines follow the go-live group, they change when you choose teams, exclude someone or an employee leaves.

Without an active payroll export target, payroll export doesn't apply, so the payroll export line is left out.

First workflows never affects go-live readiness. It counts toward setup progress once every line that applies is seen.


Going Live

  1. Work through the checklist items until go-live readiness shows Ready to go live for the people you want to start with.
  2. Use the go-live rehearsal on a few people from different teams, and anyone the checks flagged, to confirm their work policy, approvers and payroll prerequisites look right.
  3. For a phased go-live, narrow the go-live group to the teams going live first under Teams going live. Exclude anyone who won't use Z8, with a reason.
  4. Let those teams start working. First workflows shows their first clock-in, decided request and payroll export as they happen.
  5. Add the next teams. The checks cover them as soon as you save.

Don't create test employees

You don't need test employees or test requests to go live. Their work records would enter the tamper-evident time records and audit exports, their requests would reach real approvers, and a payroll export could reach your payroll provider. Use the go-live rehearsal instead, which writes nothing.


The checklist covers what Z8 can check. Before going live, also review:

  • Permissions and role assignments;
  • SSO, SCIM, social OAuth and access controls, if your organization uses enterprise identity controls;
  • email templates, if editable templates are enabled;
  • the onboarding instructions you send to employees once the setup is ready.

On this page