Check a port maintenance contractor mobilisation roster before release

A fictional port maintenance project receives a contractor workbook listing mobilisation, work and demobilisation days. Supervisors need a common roster reference before the maintenance period begins. That reference must reflect the approved plan without being mistaken for permission to enter the site.

RosterField can review and publish the spreadsheet roster. It does not certify inductions, qualifications, security permissions or other compliance requirements. Keep the processes that approve those matters separate from the roster release.

Define what this release covers

Confirm the maintenance package, contractor group, worksheet and dates with the roster owner. A workbook may include contingency crews or an alternative mobilisation sequence that has not been approved.

Write a clear operational purpose in the existing handoff process: this release shows the reviewed daily roster for the specified project period. It is not an access register or proof that workers have satisfied site requirements.

Where several parties supply files, decide which approved source represents the intended release. Workers remain separate per upload, and there is no cross-file merge. Do not assume that uploading another subcontractor’s sheet automatically combines it with the current roster.

Check identities across contractor boundaries

Compare names, employer and work location fields with the approved source. Similar names across different contractors can make a superficially tidy roster misleading.

Check the layout’s identity requirements. Shift lists need employee IDs. Matrix imports can assign missing identifiers from physical ROW-# or COL-letter positions within the upload. A generated physical identity is not evidence that a contractor’s personnel system has verified that worker.

Review duplicates and exclusions rather than guessing from a name. The duplicate employment numbers guide provides a focused investigation sequence, while mixed employer and location fields helps with contextual fields.

Distinguish mobilisation from site duty

Check how the owner uses travel, mobilisation, work and demobilisation labels. A mobilisation date might mean departure from home, arrival near the port or the first planned site day. Those are not interchangeable.

Unknown nonempty labels are offered with their exact cleaned text and require confirmation. Preserve an approved label when its meaning is clear; do not silently map Mobilise to Day just to make the roster look uniform.

Time-only values block. If a cell says only 05:30, ask whether it represents transport or duty and obtain a meaningful daily status decision. Long instructions over 120 characters also block; keep detailed mobilisation instructions in their appropriate communication process.

Verify the maintenance date edges

Check the selected start and end dates, including year and day/month interpretation. The window is limited to 140 inclusive days. Applicable source limits are configurable, so follow actual messages if a large source workbook cannot be accepted.

Inspect the day before first planned duty and the last demobilisation entry where relevant to the approved release. A one-day shift in interpretation can change the meaning of the handoff even if most sample rows look correct.

Refresh after every set of review edits. Compare counts and exclusions with the source, remembering that the normalized sample contains only the first 100 rows, paginated ten at a time.

Release without overstating assurance

A signed-in project is required for publication. Before publishing, establish who approves the roster content and who continues to manage site readiness through separate records.

Use the contractor roster handoff guide for coordinating the release. Avoid descriptions such as “verified access roster” unless an independent process genuinely supports that wording; the import itself supplies no certification.

The worker-facing project link uses unauthenticated name search. Treat the link as shareable and publish only appropriate information. Do not put security instructions or sensitive personnel notes into daily labels simply because the workbook contains them.

Practise the handoff with fictional contractors

Use synthetic names, invented IDs and a small maintenance period in the demo to rehearse identity and date checks. The demo cannot publish and is not a site-readiness assessment.

Once the real roster is released, use established contractor communication channels for material changes. A current project roster is a useful reference, but it is not proof of worker acknowledgement, transport booking or authorisation to mobilise.