By Maria Mothibeli, Head of Operations, SPM

 

Two clients can each have a good reason to want work done on Monday. If their projects require the same team, Operations still has to decide which one goes ahead. Calling both urgent leaves that decision unresolved, while each client continues to plan around the date they were given.

A maintenance contractor has to take urgent requests seriously. Failed electrical equipment can interrupt a client’s operations and require a rapid response. Clients also book shutdowns around production needs, often with several contractors due to attend. Moving an agreed maintenance job can leave them carrying the cost of those arrangements, even when there is good reason to send the team elsewhere.

Suppose a specialist team is preparing for a transformer service during an agreed shutdown when another client reports an equipment failure. Both jobs need the same specialist and test equipment. Sending the team to the breakdown may be the right decision, but moving them could leave the first client with a shutdown it cannot use. Before changing the assignment, Operations needs to understand what can be done at each site and what a delay would mean.

The technical assessment matters here. The reported failure may require immediate specialist attendance, or an initial assessment may establish that the specialist is needed later. At the planned site, postponing the work could mean losing access for several weeks. Operations has to compare the actual circumstances of the two jobs, with advice from the people qualified to assess the equipment. The word urgent supplies none of that information.

As Head of Operations, I need to be able to explain why one job should take precedence. That explanation must hold up when the client whose work has been moved asks what happened to its booking. A decision made because someone called repeatedly is difficult to defend, particularly if the business never examined the effect on work already promised.

The assessment must include money already committed to the first job. Travel and equipment hire may already have been paid for, leaving costs that the business or its client will carry even if the team goes elsewhere.

Competing requests become harder to manage when several people can change the order of work independently. A client may speak to its account contact while a project manager gives separate instructions to the site team. Unless those conversations reach the person responsible for allocating the team, each request can produce another promise. The supervisor then has to reconcile instructions that should have been settled before they reached site. Operations needs the authority to resolve routine conflicts within limits agreed by the business, so that every disagreement does not have to wait for a senior manager.

A change that would break a major client commitment or create costs beyond those limits needs a senior decision. The manager making it should approve the effect on the displaced work and identify who will carry the revised plan through.

An allocation agreed in the morning can unravel when a client challenges it. If each complaint prompts a different manager to reverse the assignment, the team can spend the day preparing to leave for work it never reaches. Moving people repeatedly uses time that was meant to be spent on the job. Managers who disagree with an allocation need to resolve that disagreement with Operations before issuing another instruction to the team.

After a priority changes, Logistics needs to know which assignment to prepare for and whether arrangements for the original job should be cancelled. The project manager responsible for that job needs to establish a revised date with the client. Some bookings may already be too far advanced to change without a charge, which is another reason to settle the decision promptly. A shared schedule helps only if the people arranging the work know that their instructions have changed.

A further inspection may justify changing the order again. That is reasonable when the condition of the equipment turns out to be worse than reported. The reason should be recorded and shared with the people arranging the work, particularly if they have already acted on an earlier instruction. Without that record, a later review may show several changes to the schedule and offer little explanation for any of them.

Work that has been postponed needs particular attention. A routine maintenance task can be moved several times because it remains less pressing than each new request. By the time it becomes urgent itself, the business may struggle to explain why the earlier opportunities to complete it were lost. Each postponement should therefore carry a revised date and an assessment of whether the work can reasonably wait that long.

The pattern of urgent requests deserves review after the immediate pressure has passed. Repeated changes may point to a client requirement that needs a different service arrangement. They may also reveal that the business is agreeing to dates before Operations has checked the existing commitments. Those are different problems, and a record of why work was moved will help management decide which one it needs to address.

A priority decision should leave the business able to tell each client what will happen next. The client whose work has moved should hear from the person responsible for that commitment, with a revised date that Operations has confirmed. They should never have to discover the decision by calling to ask why the team has not arrived.