Electrician How-To Lesson · Electrical contractors, foremen and project leads
When an electrical project is delayed, establish what changed, identify the affected work, assign the next decision, and tell the relevant people when they will receive another update. Then revise the lookahead using confirmed readiness and actual crew capacity. Avoid promising a recovery date before you understand what the recovery requires.
This lesson helps contractors and foremen turn a disruption into a clear response. You will leave with the outline of a delay procedure and a two-week lookahead.
Consider this hypothetical example, not a report about a named contractor or customer.
A crew is due to start a job on Monday, but a prerequisite will not be ready. The owner moves that work to Wednesday. Another customer has already been promised the same crew on Wednesday.
The calendar has changed. The capacity has not.
The office now needs answers: which job can proceed, who will lead it, what remains uncertain, and what should each customer be told? Moving a calendar entry did not answer those questions.
The useful next move is to examine the affected work and make a plan the team can explain. Sometimes that means resequencing. Sometimes a commitment needs to change. Either way, people need a clear decision rather than a string of hopeful updates.
Write down the change and separate confirmed facts from estimates. What was expected? What is different now? Who provided the information? What still needs verification?
Then identify the affected work. A missing prerequisite may stop one task while leaving other work ready. It may also affect another trade, a customer appointment or the next job assigned to the same crew.
Do not assume that every task can be rearranged. Check the actual requirements and dependencies with the responsible project lead before assigning replacement work. A schedule change does not override safety, required supervision or project requirements.
“We are working on it” is rarely enough for the person trying to plan around you.
Name who will confirm the missing information and who can decide the next step. Record when that answer is expected. If the answer is not available yet, set a realistic update time instead of inventing a completion date.
The purpose is to keep responsibility clear while conditions change. A foreman should not have to chase five people to discover who is checking whether the work can start.
A useful delay update explains what changed, what it affects, what is being done next, and when the next update will come.
For example, an illustrative update might say: “The prerequisite for this phase is still unconfirmed. The project lead is checking readiness. We will update the affected work plan after that check and contact you at the agreed time.” Replace those general terms with the actual facts and owners for your project.
Keep the message consistent with the records. Do not tell the crew one date while the customer and office receive another. Follow the project's established communication process, including any notices that need qualified review.
Our BULD June Workbook's Module 3 connects handling delays, project overlap and buffer planning. Its assignments are to write a delay SOP and plan a two-week lookahead.
Use the lookahead to ask what needs to be ready, not simply what date you would like to write down. For each planned activity, identify the necessary people, information, materials, access and preceding work. Mark what is confirmed and what remains open.
Check whether the same person or resource is being counted twice. Consider travel and other commitments. If your revised plan requires capacity you do not have, resolve that gap before confirming the plan.
A buffer can give the team room to respond, but it cannot guarantee that a delay will be absorbed. Base allowances on the actual project and update them when the facts change.
Download the original BULD June Workbook and turn to Module 3 on page 8. Use the notes page that follows for its delay-SOP and two-week-lookahead assignments.
An SOP is simply the repeatable procedure your team follows. For this exercise, write down:
These prompts are an article-based way to complete the original assignment. The PDF does not contain a new prefilled delay form.
Test the procedure using one past or hypothetical disruption without including private customer details. Can someone else follow it and identify the next action? Where do they have to guess? Improve that part before relying on the procedure during a busy day.
The download remains the unchanged original workbook, including its historical June/July context and software list.
Say which information is missing, who is checking it and when you will update them. An honest update time is more useful than a completion promise the current facts cannot support.
The lookahead exposes upcoming readiness constraints and decisions. The weekly crew schedule assigns available capacity to ready work. Review both when a delay changes the plan.
I’m Wilson Matthew Betances, and my mission is simple: Building the People Who Build Things. Take one thing from this lesson and put it to work. If it helped, keep learning with us.