A publish-ready roster review for construction shutdowns

Construction shutdowns combine time pressure with many moving parts: mobilising contractors, changing work fronts, day and night teams, supervision and site support. Often the operating roster is still an Excel workbook. Publishing it well is less about adding another planning screen and more about making the reviewed version identifiable and accessible.

Name the project and the roster period

Before upload, confirm that the file belongs to the shutdown project, not a similarly named project or a previous stage. Check the first and last dates in the proposed publication window. A draft workbook may contain mobilisation rows, active-work dates and a future demobilisation plan; publishing every visible column by default may not reflect the release you intended.

If dates such as 03/04/2026 appear, confirm the day/month order against the source. Check at least one known day-shift and night-shift assignment on each side of a weekend or shift handover. The fact that a date parses successfully does not mean it denotes the day your crew expected.

Reconcile people, employer and location

Shutdown rosters may list an electrician, supervisor or rigger more than once under different work packages. A repeated employment number requires a specific source-record choice. If the records actually describe different people, correct their identifiers upstream. Matrix records without numbers can use physical source-position identifiers; shift lists require employee identifiers. Neither name similarity nor a source position establishes identity across uploads.

Where the workbook includes employer and work location fields, compare these with the actual contractor and work front. A title row or empty metadata cell can shift a field mapping. A pre-release review should inspect more than the first few rows: sample each contractor, shift and work area, especially those added late.

This does not verify a worker’s licence, induction, competency or permission to enter a site. Those checks belong to the project’s safety and access systems. A roster may tell someone where they are planned, but publication is not an approval to perform regulated work.

Make changes conspicuous

Choose a single source owner who can answer questions about roster changes. When a crew, work area or shift changes, update the workbook, import again, resolve new conflicts and publish a new current version. Earlier releases remain in project roster history for administrator reference. Workers should be directed to the current project link or QR code instead of comparing attachments with similar filenames.

Explain what the link does: the published project roster can be searched by name without an individual worker sign-in. Share it only with intended recipients, and keep information needing authenticated access out of the published worker view. If the same name belongs to multiple workers, make sure a worker can identify the appropriate result without exposing unnecessary details.

A 10-minute pre-release walk-through

1. Confirm project, source filename and the intended date window.
2. Inspect the chosen worksheet and map the worker, employment-number, date and shift cells.
3. Compare a handful of known people across contractors, work fronts, day/night shifts and the edge dates.
4. Open flagged actions, resolve duplicate numbers and confirm or replace unfamiliar daily labels. Blank mappings retain their cleaned source values. Check source-position identities, exclusions and formula warnings.
5. Refresh the preview, compare total counts and the date window, and ask the source owner to approve the release. The first-100-entry sample, paginated 10 per page, is not the whole roster.
6. Publish, then communicate that the project link points to the current version.

Construction crew and equipment scheduling is a broader planning category. RosterField does not allocate crews or equipment for you; it publishes a reviewed copy of the plan already made in the workbook.

Use the upload checklist and the version-control guide to turn this into a repeatable site procedure.

Questions people ask

Will publishing a revised shutdown roster notify every contractor?

No. Publishing changes the current project roster, but does not prove people have seen the change. Use your established direct communication procedure for time-critical or safety-related revisions.

Can this replace construction crew or plant allocation?

No. The allocation and approval happen in the process that owns the plan. RosterField reviews and publishes the spreadsheet roster you provide; it does not schedule a crew or assign equipment.