Designed around roster access
Rotational work and dispersed crews can make it important for workers to be able to refer to the roster that has been published for their operation.
Mining and FIFO
Keep established Excel planning practices while publishing a roster view workers can access when they need it.
View demoTypical roster context
A site team may use an Excel workbook to group people by swing, shift, operational area, and crew. This example shows the type of publishing context that can be reviewed before release.
The workbook remains the planning record; RosterField provides a controlled published reference for the reviewed roster version.
Rotational work and dispersed crews can make it important for workers to be able to refer to the roster that has been published for their operation.
RosterField is built around the roster spreadsheets teams already use for planning. It focuses on the path from spreadsheet to published view.
When roster spreadsheets are sent between people, it can be difficult to know which version is relevant. Controlled publication provides a clearer workflow for making a roster available.
Company, project, and template profile selection help the publishing process work with the format and operational context in use.
Mapping where needed, validation, review, and limited corrections support the preparation of a roster before it is published.
A project worker link or QR code opens the published roster view on a phone; people with the link can search by name without an account.
A demo is the right place to discuss workbook formats, template setup, and the roster publishing process for a specific operation.
Useful answers
Yes. Prepare and approve the swing plan in your existing workbook, then import a CSV or XLSX copy for review and publication. RosterField does not calculate rotations for you.
The project can share a worker link or QR code. Someone with the link searches the published roster by name without an individual sign-in.
No. Codes for flights, rest and work can be reviewed as roster statuses, but the app does not certify fatigue, travel or employment compliance.
Try a fictional roster in the isolated import sandbox, or upload a small, non-sensitive CSV or XLSX test file. Publishing stays disabled.