Messages Inbound operations can show

This docket is {direction}, not inbound. Inbound operations belong to a file where the visitors are arriving.

This docket already has an inbound group.

This docket has no inbound group yet.

{field} must be a whole number of visitors, one or more.

No travellers are on this file yet, so the passenger list cannot be recorded as received.

The passenger list has not arrived. The group is still a headcount of {declaredPax}, and a rooming list needs names.

That room is not on this rooming list.

{roomType} is not a room type. Use single, twin, double, triple or quad.

A {roomType} sleeps at most {capacity}.

A single supplement cannot apply to a room sleeping {occupancy}.

Room {roomSeq} already holds {occupancy}.

That traveller is not on this docket, so they cannot be given a room on it.

That traveller already has a room on this list.

That traveller is not in room {roomSeq}.

The rooming list does not add up: {beds} beds and {assigned} named travellers against {declaredPax} visitors, with {roomsUnderfilled} room(s) short and {roomsOverfilled} over.

This rooming list went to the hotel on {releasedAt} and cannot be changed here.

{kind} is not a movement. Use arrival, departure, excursion or intercity.

A movement must end after it starts. It was given {startsAt} to {endsAt}.

{paxCount} visitors on a movement, but the operator sent {declaredPax}.

That movement is not on this group.

That movement is cancelled, so nobody can be assigned to it.

{role} is not a role on a movement sheet.

A {resourceKind} cannot take the {role} place on a movement.

No guide, driver, rep or vehicle with that id.

{resourceName} is already on this movement.

{resourceName} is already committed from {startsAt} to {endsAt} on another group. One {resourceKind} cannot be in two places at once.

{resourceKind} is not a resource. Use guide, driver, rep or vehicle.

The code {resourceCode} is already in use.

A guide, driver, rep or vehicle needs a code and a name.

The board needs a day to show, written as a date.

{status} is not a status for a guide, driver, rep or vehicle. Use active, dormant or blocked.

{resourceName} is not active, so they cannot be given new work. Mark them active on the Operations screen first.

That guide, driver, rep or vehicle is not on this movement.

{source} is not a place a guide, driver or vehicle can come from. Use your own list, a Logistics driver or a fleet vehicle.

{resourceName} is on Logistics route {routeCode} on {serviceDate}, so they cannot be on this movement too.

This company does not have the Logistics app, so its drivers and vehicles cannot be put on a movement.

Logistics drivers cannot be assigned yet: this company’s database is still being updated. Try again in a minute.

That sign-in does not belong to anyone in this company.