Scheduling Multiple Crews Across Multiple Clients

The scheduling problem is not the calendar. It is the four constraints — competency, calibration, permit and cost — that the calendar does not know about.

Every inspection contractor above a handful of crews runs into the same wall. The whiteboard or shared calendar knows where people are, but it does not know whether the technician assigned is currently qualified for the method, whether the instrument going with them is in calibration, whether the site permit and induction are valid, or which contract absorbs the mobilisation cost. Those four unknowns are where margin and compliance both leak.

The four constraints a calendar cannot see

  • Competency — the scope requires a method and level; the assigned technician must hold it, currently, with vision exam in date.
  • Calibration — the instruments, probes and reference blocks going to site must be in calibration for the duration of the job, not just on the day of dispatch.
  • Access — site induction, permit-to-work, client-specific approval and medical clearance each have their own expiry.
  • Cost — mobilisation, travel, standby and per-diem have to land on the contract that caused them, or per-contract margin is fiction.

What good dispatch looks like

A dispatch decision should be a validated action, not an entry. When a scope is assigned, the system checks competency, calibration and access, and refuses the assignment if any fail — surfacing which technician or instrument would satisfy the constraint instead. That turns a compliance risk into a scheduling suggestion, which is the only form in which schedulers will actually engage with it.

The second property is visibility of committed capacity. Standby, travel days and rotation cycles consume crew availability as surely as productive days do, and schedules built only from productive days routinely over-commit by twenty to thirty per cent.

Multi-site and rotation realities

Contractors working offshore rotations, remote sites or multiple regions carry constraints that a simple calendar cannot express: a technician on a two-week-on rotation is not available for a shore job on day three regardless of what the calendar shows; a crew mobilising to a remote site cannot be re-tasked mid-mobilisation without absorbing the cost twice. Modelling rotation cycles and mobilisation windows explicitly is what stops the schedule from being aspirational.

Costing at the point of dispatch

  • Assign every dispatched hour, travel day, standby day and per-diem to the work order at the moment of dispatch rather than reconstructing it at invoicing.
  • Cost equipment usage to the job, including hire and consumables — small individually, material across a year.
  • Track subcontracted NDT against the same work order so the true delivered cost of the contract is visible.
  • Expose per-contract margin while the contract is still running, not at final account when nothing can be changed.

Frequently Asked Questions

How is this different from a generic field service scheduler?

Generic field service tools schedule people against jobs and handle travel and routing well. What they lack is method-level competency validation against a written practice, instrument and reference-block calibration state as a dispatch constraint, and client-specific approval tracking. Those three are exactly what make inspection dispatch different from, say, appliance repair.

What is the fastest win when scheduling is currently on a whiteboard?

Put the competency and calibration check on the dispatch action first, before building any scheduling UI. That single control removes the two failure modes that cost mobilisations. Sophisticated optimisation can wait; preventing a lapsed technician reaching a client gate cannot.

How do we handle emergency call-outs and schedule churn?

Model them as first-class work rather than exceptions handled verbally. Emergency work still consumes capacity, still requires the same competency and calibration validation, and still has a cost that belongs to a contract. Companies that keep call-outs off the system systematically under-report utilisation and over-report margin.

Does this need to integrate with the client's system?

Usually yes, at least one-way. Operators commonly expect inspection findings to raise notifications or work orders in their own SAP PM, Maximo or ServiceNow instance. That integration should be automatic from the work order rather than a person re-keying findings into a client portal, which is both slow and a source of transcription error.

See it running on your own workflow

Thirty minutes, your job types and your reporting formats, co-presented by an ASNT NDT Level III. Affordable, accessible, fully customizable — request a demo and a tailored quote.

Related: Inspection scheduling module · Work order management · Inspection management software · Atlantis NDT ERP