Operational templates
Worksite Setup Checklist Template
A structured checklist for defining site details, operating rules, attendance controls and accountable owners before rollout.
Explore 20 questionsThe short answer
What matters for your decision
Use this blank worksheet to organize site configuration and local operating rules. It is an illustrative planning aid: confirm field meanings, approval ownership and the configured Hirebase workflow for your deployment before operational use.
Suggested worksheet
Fields and illustrative entries
These entries illustrate how to use the worksheet. The downloadable CSV provides blank fields for your organization; it is a planning tool rather than a product export or a customer record.
| site_id | site_name | address_or_area | timezone | operating_hours | site_owner | attendance_controls_to_configure | job_codes | open_questions | approval_status |
|---|---|---|---|---|---|---|---|---|---|
| Example only | North Yard | Example address | America/Chicago | 06:00-22:00 | Site lead | Confirm configured location and punch controls | JOB-01 | Illustrative; verify with site owner | Draft |
Illustrative sample row
The in-page worksheet includes an illustrative sample entry. Replace it with approved local data; it is not a customer outcome. The downloadable CSV is blank apart from its headers.
Identify the site
Assign a stable site ID, official display name, time zone and location owner. Resolve duplicate names and define which organization or client owns the record.
Document operating conditions
Capture hours, work areas, roles, access constraints and site-specific instructions that affect worker assignment or attendance review.
Agree configured controls
List requested geofence, punch, photo or face-liveness controls for implementation review. These settings depend on the deployment; this checklist does not prove a location or identity.
Approve readiness
Have operations and implementation owners confirm the site record, test the relevant worker journey and document unresolved items before live use.
Hirebase for your operation
Make the workflow fit your business.
Connect workforce workflows with organization-wide licensing, configurable operating rules and customer-controlled Azure deployment. Bring your site requirements, worker journey and integration needs to an implementation conversation.
Evaluate HirebaseYour buying questions
Questions, answered
20 of 20 questions
Which identifiers should be set for a site?
Use a stable site ID, display name, address or area, time zone and accountable owner.
Link to this answerWhy record a site's time zone?
It clarifies local shift times; have implementation confirm time-zone behavior for the deployment.
Link to this answerHow should a site geofence be recorded?
Document the requested boundary or center, approver and test reference; confirm actual settings in deployment.
Link to this answerWhat radius can Hirebase geofences use?
Product information describes per-site geofences configurable down to 10 meters; confirm site-specific settings.
Link to this answerShould this checklist store location history?
No. Record only the requested control and a secure configuration reference.
Link to this answerHow are site job codes aligned?
Create an owner-approved crosswalk and flag retired or ambiguous codes.
Link to this answerWho confirms operating hours?
The site or operations owner validates local hours and planned exceptions.
Link to this answerHow do duplicate site names get resolved?
Use unique IDs and keep aliases documented rather than merging locations.
Link to this answerHow should punch controls be checked?
Run a representative authorized punch test and review its event and exceptions.
Link to this answerWhen is setup accepted?
After site owner approval and implementation test evidence with open issues assigned.
Link to this answerWorksite Setup Checklist: what should be covered first?
Start with site configuration and local operating rules; agree the scope and owner before entering operational records.
Link to this answerWorksite Setup Checklist: Who owns the source information?
The business process owner should name the authoritative source and a person responsible for resolving inaccurate or outdated entries.
Link to this answerWorksite Setup Checklist: Which fields are essential?
Use the columns in the downloadable blank CSV as a starting point for site configuration and local operating rules. Add only fields with a clear operational purpose.
Link to this answerWorksite Setup Checklist: How should we handle missing values?
Leave unknown information blank or mark it for review. Do not invent a value to make a row appear complete.
Link to this answerWorksite Setup Checklist: How do we record an exception?
Keep the original observation, assign an owner, record the decision separately and retain a source reference for later review.
Link to this answerWorksite Setup Checklist: What evidence should be linked?
Link to an approved source record or controlled repository. Avoid copying sensitive personal details into an open worksheet.
Link to this answerWorksite Setup Checklist: Who reviews a completed row?
The role accountable for the decision should review the record under the organization's own approval rules.
Link to this answerWorksite Setup Checklist: How should sites use the same vocabulary?
Agree stable site identifiers and shared labels, then document any local aliases so cross-site reporting remains understandable.
Link to this answerWorksite Setup Checklist: Can teams add local columns?
Yes, when a local field has a clear purpose and an owner. Document its meaning and do not repurpose an existing field silently.
Link to this answerWorksite Setup Checklist: How often should this be updated?
Set a cadence based on the process, event frequency and close or rollout calendar; record the last review date and owner.
Link to this answer