Utility Cutover Scheduling and Customer Notification
Purpose
A cutover date is not a date the shop picks. It is the last item in a chain of releases the shop does not control, and every one of those releases can move without telling anybody. Permit, utility work order, inspection release, meter set: four links, four owners, none of them yours. A shop that promises a Tuesday because Tuesday is when the crew is free has committed to an outcome it cannot deliver and told a customer to empty their freezer for it.
The other half is the abort. Almost every failed cutover was visible the day before, and the difference between catching it then and catching it at 8 am is not effort, it is a fixed decision point with named preconditions. Aborting the day before costs one phone call and a crew reassignment. Aborting on site costs a crew day, a burned utility slot, and a customer who has already thrown food away.
Scope
Covers scheduling the utility-dependent cutover for a service change, meter relocation, service entrance replacement or panel replacement, and the customer notification that tracks it, residential and small commercial.
Not covered: the outage-day coordination itself and the written confirmations from utility, customer and occupants that gate mobilization, which are owned by electrical-utility-outage-coordination-and-customer-notification; the electrical work performed during the outage; and the meter socket process at electrical-meter-socket-replacement-and-utility-coordination.
Roles and handoffs
| Role | Owns | Hands off |
|---|---|---|
| Office scheduler | The chain, every date on it, and the go/no-go gate | The gate result to the lead and the customer by a fixed hour the day before, go or no-go, never silence |
| Estimator | Naming the customer's critical dependencies before any date is offered | Those dependencies to the scheduler in writing, before the first notice goes out |
| Lead installer | Crew and material readiness as one gate item | Ready or not ready to the scheduler by the gate hour, in those words |
| Customer | Their own preparation and access | Confirmation at each notice, which is the only proof they heard it |
The dependency chain
| Link | Owner | What it blocks | Can it run in parallel |
|---|---|---|---|
| Permit issued | Authority having jurisdiction | Inspection release, and in many territories the utility work order | Yes, start it first |
| Utility work order and window | Utility | The cutover date itself | Yes, once the permit application exists in territories that allow it |
| Inspection release | Authority having jurisdiction | The meter set | No, it needs the work finished |
| Meter set and re-seal | Utility | Restoration of the customer's power | No, it follows the release |
Use your shop's own measured median for each link rather than a published figure, because these vary more between two neighbouring jurisdictions than between two states. The longest pole is almost always the utility work order, and that is what the cutover date is set from. What breaks the chain is nearly always one of four things: a permit revision, a utility crew reassigned to storm restoration, an inspector slot moved, or a customer dependency nobody asked about.
Procedure
Build the chain for this job and put a date on every link before offering the customer one. Write each of the four links with its owner and your measured median, then work forward from today to the earliest cutover the longest pole allows. Accept when all four links carry a date and the longest pole is named. Wrong looks like a cutover date chosen from crew availability; stop rule, no chain means no date is offered, not even a range. Hazard: none, a desk step, though a date promised without a chain is what puts a crew and a customer in a house with the wall open and no utility coming.
Name the customer's life-safety and business-critical dependencies before a date exists. Ask directly: oxygen concentrator, home dialysis, powered medical equipment, a tenant's walk-in cooler, a sump pump on a wet basement, a business that cannot close. Accept when the answer is written down as a list or as an explicit none. Wrong looks like discovering an oxygen concentrator on the morning of the outage; stop rule, any life-safety dependency stops the scheduling until a covered arrangement exists, which is a utility medical-baseline registration, a backup supply, or a relocation for the day. Hazard: this is the safety step of the whole procedure, because an unplanned outage on powered medical equipment is the injury this SOP exists to prevent.
Submit the parallel links immediately and hold the serial ones in sequence. Permit and utility work order go in as early as your territory allows, and the inspection is requested only when the work will genuinely be complete. Accept when each submission has a reference number and a date recorded on the job. Wrong looks like an inspection requested to hold a slot before the work can possibly be ready; stop rule, a failed inspection because the work was not ready costs a re-inspection and a re-booked meter set, so it is not requested optimistically. Hazard: none, a desk step.
Issue the customer notice as a window with named conditions, not as a promise. Give the date, a start window rather than a time, the expected duration, what they must do, and in one plain sentence what would move it. Accept when the notice has been sent, the customer has confirmed receipt, and the confirmation is logged with a time. Wrong looks like a voicemail counted as notification; stop rule, no confirmed receipt means the notice has not been given and it is sent again by another channel. Hazard: none, but a customer who empties a freezer for a date nobody confirmed is the reputational injury here.
Run the confirmation two business days out with each external party. Call the utility scheduler and the inspection desk, re-read the window back to them, and ask specifically whether anything has been reassigned. Accept when each party has confirmed within the last 48 hours and the name of who confirmed is recorded. Wrong looks like relying on a confirmation given three weeks ago; stop rule, a party that cannot be reached at two days out is treated as unconfirmed at the gate, not as probably fine. Hazard: none.
Run the go or no-go gate at a fixed hour the day before, against all five preconditions. The five are: permit issued and on site, utility work order confirmed within the last 24 hours, inspection release obtained or an inspector slot confirmed, customer dependencies covered, and crew plus material staged. Accept when all five read yes and the decision is recorded as go with a time. Wrong looks like four yeses and one probably; stop rule, any precondition short of yes is a no-go, the customer is told that evening, and the job is re-dated from the chain rather than from hope. Hazard: none, and this is the step whose entire value is that it happens before anybody is standing at an open service.
On the day, make the start call and the restore call, and close the record. Call the customer when the utility arrives and again when power is restored and verified at a device inside. Accept when both calls are logged with times and the restore call is made only after the customer's own critical loads have been observed running. Wrong looks like a crew leaving while the customer discovers the freezer is still off; stop rule, an unverified restore is not reported as a restore. Hazard: power is going back in with the customer present, so the restore call happens after the panel is closed and the space is clear, not while somebody is still at the deadfront.
The record this produces
- The four-link chain with owner, date and reference number per link. Read by the next scheduler on the next cutover in the same jurisdiction, and it is how a shop builds real medians instead of guesses.
- The customer dependency list, or an explicit none. Read before any future outage on this address, forever.
- Every notice with its confirmed-receipt time and channel. Read when a customer says nobody told them.
- The two-day confirmation with the name of who confirmed. Read when the utility says the window was never booked.
- The gate result, all five preconditions, with the decision time. Read after a failed cutover, and it is the only record that shows whether the failure was foreseeable.
Worked pass: one gate, two jobs, opposite outcomes
Both jobs are service changes booked for the same Tuesday, and both run the same five-precondition gate at 3 pm Monday.
Job A, owner-occupied house. Chain built on the shop's own medians: permit 4 business days, utility work order 10 business days, inspection release same day when requested before 10 am, meter set 1 business day after release. The utility work order is the longest pole at 10 days, so the earliest cutover is set from it and the customer is given a date 12 business days out with a 8 am to 10 am start window. Step 2 returned a dependency list of one, a chest freezer, covered by the customer moving contents to a neighbour. Two-day confirmation reached the utility scheduler by name on Friday.
At the gate: permit issued and on site, yes. Utility work order confirmed at 2:40 pm Monday, yes. Inspector slot confirmed for Tuesday 1 pm, yes. Dependencies covered, yes. Crew and material staged, lead says ready, yes. Five of five, recorded as go at 3:05 pm. The job runs, the start call goes out at 8:15 am and the restore call at 2:40 pm after the freezer is observed running.
Job B, two-tenant retail strip. Same chain, same gate. Permit issued, yes. Utility work order confirmed Monday, yes. Dependencies covered, yes, with one tenant's cooler contents moved. Crew staged, yes. Inspection release: the inspector's Tuesday slot was reassigned Monday morning and the desk can only offer Thursday. That is four yeses and one no, so under the rule as written it is a no-go, and it is called as one at 3:10 pm.
The customer hears it Monday evening, the utility slot is released back rather than burned, and the job is re-dated from the chain. Compare the two aborts honestly in the same unit: calling it Monday costs one day of slip and two phone calls. Calling it Tuesday morning would have cost the crew day, a re-booked utility work order at the shop's 10-business-day median, and two tenants closed for a morning for nothing. One day against roughly ten, which is why the gate has a fixed hour and why a probably is scored as a no.
Both records close with all five preconditions written out, including Job B's single no. The no is the useful line: it is what tells the next scheduler that this jurisdiction's inspector slots move on short notice, which belongs in the chain's medians rather than in somebody's memory.
References
- Your utility's electric service requirements manual, which sets the work-order process, the lead time and the conditions for a meter set.
- Your authority having jurisdiction's permit and inspection procedures, in the form your jurisdiction publishes them.
- NEC Article 230, in the edition your authority having jurisdiction has adopted, for the service work the cutover exists to complete.
- See related:
electrical-utility-outage-coordination-and-customer-notificationfor the outage-day confirmations,electrical-meter-socket-replacement-and-utility-coordination,electrical-temporary-service-for-a-construction-site.