The operations desk and the working life of a file

Milestones make stalled work visible

A file passes through a known set of states: instruction received, booked, collected, received at origin facility, departed, arrived, cleared, delivered, invoiced, closed. The purpose of recording them is not reporting. It is that a file which has been sitting in the same state longer than the lane normally requires can be surfaced automatically, before anyone complains. Without that, attention is allocated by whoever telephones, which reliably means the loudest customer receives service and the largest problem goes unnoticed.

How desks are carved up

Organising by lane builds deep knowledge of routings, correspondents and local peculiarities, but leaves customers speaking to several people. Organising by customer gives a single point of contact and consistent handling, at the cost of every operator needing competence across every trade. Splitting by function, with separate booking, documentation and clearance teams, is efficient at volume and introduces handovers where files are dropped. Each structure fails differently, and the failure mode should be chosen deliberately. Whichever is adopted, the handover points need an explicit owner, because a file belonging to a team belongs to nobody.

Exception handling is the actual job

Triage should follow consequence rather than volume or noise. A shipment rolled off a departure with a fixed onward commitment outranks a routine document query, even though the query is quicker to answer and the customer asking it is more insistent. Written playbooks for the recurring exceptions, a rolled booking, a hold, a failed collection, a damaged consignment, remove the need to invent a response under pressure. What separates a competent desk from an overwhelmed one is usually not headcount. It is whether the first hour of the day is spent on the files that have stopped or on the ones that are shouting.

The customer procedure as an operating contract

Each significant account should have a written procedure covering routing preferences, documentation requirements, release instructions, escalation contacts, billing rules and anything the customer has asked for that is not obvious. It exists so that the handling does not depend on which operator is at the desk. Its weakness is age. Procedures are written at onboarding and then diverge from what actually happens, until the document describes a service nobody provides. Reviewing them against reality periodically is dull and prevents a surprising number of complaints.

Handovers across time zones

International files pass between offices and correspondents whose working hours barely overlap. A pre-alert that leaves incomplete costs a full day at the far end, and a query raised late in the afternoon may not be answered until the following one. Structuring the day so that outbound information leaves before the receiving office closes is worth more than any amount of chasing. Where a correspondent handles the destination, its responsiveness becomes the firm's service level whether or not that was intended, which is a good argument for choosing partners on operational quality rather than on the profit split alone.

Frequently asked questions

Should operators be organised by customer or by trade lane?

Both work, and each fails in a predictable way. Customer desks give consistency and require broader competence; lane desks give depth and fragment the customer experience. The decision should follow whichever failure the business can better absorb.

What is the single most useful operational report?

A list of files that have not changed state within the expected period for their lane. It finds problems before customers do, which is the only form of early warning the function reliably gets.