Plan across large work areas
Bulk earthworks and civil projects may spread teams across cut and fill zones, haul routes, drainage, services, and structures. Published rosters help crews refer to the current workforce plan.
Bulk Civil Works
Publish the workforce plan for large crews, plant operations, and changing civil work areas without abandoning Excel.
View demoTypical roster context
A civil project workbook may separate people by work front, plant activity, support function, and the stage of the program.
The project can continue using its own Excel format while publishing the reviewed workforce plan in one defined place.
Bulk earthworks and civil projects may spread teams across cut and fill zones, haul routes, drainage, services, and structures. Published rosters help crews refer to the current workforce plan.
Administrators can retain roster planning that reflects operators, labour, supervision, and project support roles, then use RosterField for controlled publication.
Crew requirements can change as the project moves between mobilisation, production, testing, and handover. A defined publishing workflow supports roster updates without relying only on emailed files.
Project and template profiles support recurring Excel formats, while mapping provides a setup path when a new workbook structure is introduced.
Validation and review help roster administrators inspect prepared data and make limited corrections before release.
The project link or QR code provides a mobile-friendly way to search the published roster by name. Share it only when that access model is suitable for your crew.
Useful answers
Yes, keep your existing planning method. RosterField publishes the mapped people and shift data it can interpret; it is not a plant allocation system.
The signed-in import workflow lets an administrator review the proposed date window. Confirm that it matches the period you intend to share.
Prepare an updated workbook and publish a new reviewed version. Roster history keeps earlier publications available to administrators.
Try a fictional roster in the isolated import sandbox, or upload a small, non-sensitive CSV or XLSX test file. Publishing stays disabled.