What a maintenance in-charge checks after a power cut

This story shows a practical response to restarting in the right order and checking for damage.

Who this is

This composite follows the maintenance in-charge in a castings business of about 80 people. Their work crosses several desks, with handwritten registers and messages used alongside digital records. The role is answerable for the state of the breakdown log and machine service plan and for passing exceptions to the production manager. Calls most often come from people who need a yes, no or reliable date before they can continue.

The task here is what a maintenance in-charge checks after a power cut. The responsibility is limited: this person can check and record facts within their role, then seek approval when money, safety, customer promises or rules require it.

The moment

The breakdown log and machine service plan is open, but nobody can identify the next owner. The issue now being examined is restarting in the right order and checking for damage. The maintenance in-charge has to decide what can move now and what must wait. The information comes from operator checks, downtime notes, spare stock and maintenance calendar. A quick answer is tempting, especially when the next team is already standing nearby, but an unverified status can become a commitment.

The first action is to put the current source on the desk or screen. It may be a job card, a supplier message or a bank entry. The maintenance in-charge compares the source with the last approved record. A difference is recorded openly. The role then asks who can verify it, rather than inventing a missing value.

This particular moment turns on three small decisions: confirm safe utilities and machine conditions before staged restart, inspect controls and affected product, and record safe return to service approval. Their order matters. A later approval does not repair a wrong quantity or an unsafe condition discovered after work has started.

What they check, in order

1. Confirm the case. Confirm safe utilities and machine conditions before staged restart. Look at operator checks, downtime notes, spare stock and maintenance calendar. Write the reference next to the question instead of keeping it only in chat.
2. Check the original evidence. Verify isolation safety, fault time, symptoms, spare availability and restart approval. If two records disagree, keep both and record what needs reconciliation.
3. Look for downstream effects. Inspect controls and affected product. Tell the affected team which job, payment, batch or person is waiting. Avoid giving a firm time without evidence.
4. Apply the authority boundary. The production manager reviews exceptions involving an altered commitment or a decision outside the normal limit. A verbal approval should be documented.
5. Keep the next action visible. Record safe return to service approval. Show the person, deadline and the record that will prove the task is done.
6. Verify closure. Find machine ID, downtime entry and repair sign-off. If it is missing, keep the item open and make it the first check at the next review.

The checks are intentionally small. They should fit into the person's existing shift instead of creating another report. More detail is useful only when someone will read it and act on it.

What they wish they knew earlier

They would prefer to have isolation safety, fault time, symptoms, spare availability and restart approval before the request becomes urgent. A short update from the previous team can prevent repeated calls. The hard part is deciding whether the update is current and authorised.

The hand-off is complete only when the next person knows the reference, agreed date and what remains unverified. Do not restart after an electrical or guarding fault until a competent person confirms it is safe.

The one sheet that helps

A small breakdown log and machine service plan brings the question, the evidence and the next person together. The rows below are examples only. They are neither a real company's records nor measured results.

Update the sheet when something changes, even if that change is a revised promise or a failed check. Do not erase the original instruction. For a reusable version, open Machine start up checklist.

If you do this job

1. Tomorrow, select one real case that matches Utility failure response. Keep the original source visible while you make the check.
2. Record who owns the next move. If the evidence is missing, mark the case open and state the exact document or physical check needed.
3. Before hand-over, tell the next role which part is confirmed and which part still needs a decision. Use POwer problems damage machines to investigate any repeated gap.

Read next

• POwer problems damage machines
• Utility failure response
• Machine start up checklist