Product fit / Field notes
Employment Hero HR workflows and a separately prepared project spreadsheet
A team can manage people processes and still prepare a project roster in a workbook. Give each owner a clear hand-off and verify the release copy.
HR software and a project roster answer related but different questions. A people team might be responsible for employment records and workplace processes, while a project coordinator decides who attends a particular site on particular days. The coordinator may still compile that project plan in Excel. Buying software for HR and rostering does not, by itself, tell you who approves that separately prepared spreadsheet or who should publish it.
Employment Hero presents rostering features such as shift creation, templates, cost visibility, timesheet comparison and an employee app. Those capabilities may matter when considering a wider team workflow. This article is not a claim that an Employment Hero record is passed to RosterField, that a spreadsheet can be synchronised with it, or that either product validates the other’s data. Treat the project workbook as its own source until your organisation has established and tested a different process.
Name the decisions, not only the applications
Suppose HR confirms that a worker is engaged for a three-month contract, a site coordinator chooses which swing they will work, and a project manager signs off the crew allocation. Who enters the dates in the project workbook? Who checks the worker’s name and employment number there? Who can approve a change after the manager has signed? These are operational questions, regardless of where your business manages HR records.
A practical responsibility map could look like this:
- People team: maintains its normal employment and onboarding processes. Do not treat publication of a roster as an HR approval.
- Planning owner: prepares or revises the Excel workbook, including shifts and project dates, according to the site’s rules.
- Approver: confirms the intended plan and any contractor or supervisor sign-offs outside the publication step.
- Publisher: imports the approved CSV/XLSX copy into the relevant RosterField project, resolves review issues and checks what workers will see.
- Communicator: tells affected people about important changes through the organisation’s established channel.
One person can have more than one role; what matters is that a publication click is not confused with an employment decision. Keep the worksheet name, roster period, approval state and release owner visible in your own hand-off notes.
What a clean spreadsheet hand-off looks like
Imagine a fictional bridge-maintenance project. HR has confirmed the contractors’ arrangements, but the project administrator receives a separate workbook containing crew names, employment numbers and daily status codes. On Tuesday, the manager approves a date range through the next fortnight. The administrator saves a release copy and uploads it to the correct project; on review, one person appears twice under the same employment number and another has no number. Those are source-data questions to take back to the project owner, not a reason to assume the HR system has reconciled them.
The administrator selects the intended sheet and period, confirms that date headers represent the right days, makes a supported duplicate choice or corrects the workbook and uploads again. They check a few known workers against the preview before publishing. RosterField does not invent missing IDs, recalculate payroll, approve leave, or create the original shifts. See duplicate employment numbers and Excel roster upload checks for the concrete review decisions.
Decide which details belong in a worker view
An internal HR or planning workbook may contain notes that do not belong on a roster reached through a shareable link. Decide what the worker-facing roster needs to show, and prepare the source accordingly. RosterField’s project worker link lets someone search the published roster by name without an individual worker login. Passing around the URL therefore requires care; it is not proof of identity or a private HR portal.
Where two workers have similar names, test the search result with fictional data and check the appropriate record. Do not place sensitive HR notes into a roster under the assumption that only the named worker will see them. The worker-link privacy guide describes the access model and questions to ask before a release.
Reconcile the process when the plan changes
If a site supervisor changes a Friday assignment, decide which source they must update and which approver must acknowledge it. A change recorded in an HR or scheduling workflow does not automatically update an independent workbook or a published RosterField version. Equally, publishing an updated spreadsheet does not update a separate HR or timesheet record. Assign someone to verify both sides when your business uses multiple processes, rather than assuming any unmentioned integration will keep them aligned.
The best comparison question is not “Which platform has more features?” It is “Where does the approved project plan live, and who is accountable for its accurate release?” The how-it-works page shows the narrower publication stage so the team can place it beside, rather than inside, its existing people workflow.
Questions people ask
Does publishing the spreadsheet confirm that HR has approved each person?
No. Publication confirms that an administrator released the reviewed project roster, not a person’s employment status, onboarding or eligibility for a site. Keep those checks with the appropriate people team and project approver. Resolve disagreements with the source owner before treating the workbook as ready to share.
What if the employment number in the workbook differs from an HR record?
Check the source with the responsible team rather than assuming a product will reconcile two separate records. An absent number can exclude a person from the imported roster, and repeated numbers require an administrator’s choice. Correct the authorised source and repeat the import review before publishing.