Electrician How-To Lesson · Contractors, foremen and project leads
Start an electrical project with a short kickoff that establishes the work, who owns each next step, what must be ready, and how changes will be communicated. Finish with a written recap and a simple progress tracker. Everyone should leave able to explain their responsibility without guessing what someone else meant.
This lesson is for the contractor or foreman coordinating several people before work begins. The practical goal is a kickoff script you can use on your next job.
Picture this hypothetical job, not a story about a specific customer or crew.
The electrical crew arrives expecting access to the work area. Another trade is still using it. The customer thought the electrician was coming to confirm the plan, while the foreman thought the plan had already been settled. Someone says, “I thought you handled that.”
The crew has tools, people and a date on the calendar. What it does not have is a shared understanding of what that date means.
Before the next start, the project lead brings the relevant people together. They identify the open questions, assign someone to resolve each one, and agree when readiness will be checked. The meeting does not magically finish the other trade's work. It makes the dependency visible before another promise is made.
That is what a useful kickoff should do for your electrical business.
Ask each person to explain their part of the project in plain language. Confirm the current scope and identify questions that need an answer before the affected work starts. If someone is working from an older document or a different assumption, resolve that difference through the appropriate project process.
Keep this practical. What is the next work to be completed? Who is responsible for it? What information does that person still need?
A kickoff discussion supports the project's existing documents and requirements. It does not replace them or authorize a scope change by itself.
A start date is more useful when the prerequisites are attached to it.
Confirm the relevant access, materials, information and preceding work. Identify the person who can verify each item, rather than accepting “somebody is checking.” Keep staffing, qualifications and required supervision in the plan as well.
When an item is unconfirmed, mark it unconfirmed. Give it an owner and a time for the next answer. Avoid turning an expected delivery or hoped-for completion into a confirmed fact.
This is also the moment to ask what another trade needs from your crew. A handoff works both ways. Your team may be waiting on someone, and someone may be waiting on you.
Our original BULD June Workbook puts kickoff calls, update frequency and subcontractor progress together in Module 2. That connection matters: the first conversation should establish how the next conversations happen.
Choose a practical place for the shared update. Agree who maintains it and which changes need a direct conversation. Do not assume everyone checks the same app or sees every message.
An update should tell the recipient what changed, which work is affected, what decision is needed, and when another update will follow. If the answer is still unknown, say what is being checked and who is checking it.
The workbook asks you to build a subcontractor tracker. Start small enough that you will actually maintain it.
For each handoff, record the deliverable, responsible person or company, prerequisite, agreed date, current status and next update. These fields are a suggested application of the workbook assignment, not a preprinted form inside the PDF.
Use the tracker to expose missing decisions. A row marked “waiting” needs more information: waiting for what, from whom, and what happens next?
Before closing the kickoff, ask participants to repeat their next step. If their answer differs from your notes, clarify it now. Send a concise written recap through the agreed project channel.
Download the original BULD June Workbook and turn to Module 2 on page 6. Its two assignments are to write a kickoff call script and build a subcontractor tracker. Use the notes page that follows.
Build your script around five questions:
Then test the script with someone who will be involved in the job. Ask them to explain the handoff back to you. Clear answers are a better test than the length of your meeting.
This is the unchanged original workbook. Its June/July course references and software list are historical context, not a newly updated schedule or current software recommendation.
Long enough to resolve the start-critical questions and assign the remaining ones. A small job may need a short conversation; more participants and dependencies may need more preparation. Use the outcome, not an arbitrary meeting length, as the test.
The kickoff establishes project responsibilities and handoffs. The weekly crew schedule matches ready work to available people. Use them together.
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.