Panel schedules and as-builts that live with the job

The panel is trimmed out and energized. Somebody, probably the apprentice, wrote the circuit list on the flap of a wire box with a Sharpie: kitchen recept, disposal, master bath GFCI, the outside receptacle that shares a breaker with the garage for reasons nobody wrote down. That cardboard sat on the ground next to the panel all day. It is the most accurate record of what got wired on that job, and at cleanup it goes in the same trailer as the scrap and the empty MC reels, and by Friday it is in the dumpster.

That is not sloppiness. It is the fastest way to capture the schedule while your hands are in the panel, and the fastest way has always won in the field. The problem is not the cardboard. The problem is that the cardboard is the only copy, and the only copy dies at cleanup. You did the work of mapping every circuit, and then you threw the map away. Keeping that record is part of the wider proof and getting paid guides.

The circuit map is as-built data, not scratch paper

Think about what is actually on that flap. It is the finished layout of the panel: which breaker feeds what, where the multiwire circuits share a neutral, which slot is a spare and which is a dead space you left for the future range circuit. That is as-built information. It is the same class of record as your rough-in photos before the drywall covers it and the shots you take before the next trade buries your work. You already treat those as worth keeping. The panel schedule is worth exactly as much, and it is the one that leaves the site as trash.

The reason it feels like scratch paper is that it looks like scratch paper. A Sharpie on cardboard reads as temporary. But the information on it is permanent: that panel will carry those circuits for twenty years, and the label inside the door, if anyone even filled it in, is a printed grid that says “bedrooms” and “lights” in three abbreviations that made sense to one guy on one afternoon. The real detail lived on the cardboard. Then the cardboard went in the dumpster and the detail went with it.

Ask around any shop and you will hear the same story. Nobody planned to lose the schedule. It just had nowhere to go except a truck dash, a text thread, or the trash, and all three lose it.

The service call that one photo would have answered

Here is where the missing map costs you. Fourteen months later the homeowner calls: half the garage is dead, and the outside receptacle went with it. You send a tech, a good one, and he opens the panel to a door label that reads “GAR” on one breaker and nothing useful anywhere else. The GFCI that is actually tripped is the one you set in the master bath, because that outside receptacle was fed off the bathroom GFCI to save a device. Reasonable choice at rough-in. Invisible now.

So the tech starts tracing. He resets every breaker, checks the obvious garage GFCI, finds nothing, pulls the receptacle, tests it dead, works backward. He is in three rooms with a toner before he thinks to try the master bath GFCI and the garage comes back to life. Call it an hour of a licensed tech standing in a house solving a puzzle your own crew already solved at rough-in.

Put a number on it. An hour of tech time on a service call, loaded with the truck and the drive, is real money, and on a warranty callback you are eating it, not billing it. Say sixty-five dollars in wages and a share of the truck for that hour, plus the half hour of windshield time to get there. Call it a hundred dollars, gone, on a question your crew answered for free the day the panel was wired. Do that three or four times a year across your service calls and it is a week of a tech’s pay spent re-learning things you already knew.

The sting is the same as any lost record: the information existed. Your apprentice wrote it down. You just had no place to keep it where the service tech could find it fourteen months later.

Shoot and keep, at every stage

The fix is not a binder and it is not a new form nobody fills out. It is a habit that takes ten seconds and rides on the phone already in the electrician’s pocket: shoot the schedule, keep the shot with the job.

Do it at each stage, because the panel changes:

At rough-in, photograph the homerun list or the panel layout while the wires are still landed and labeled and nobody has cut a tail short.

At trim, photograph the finished cardboard schedule, the one with every circuit mapped, before it leaves the ground next to the panel.

At any change, when you add the range circuit or move a load, shoot the updated flap so the latest version is the one that wins. An old photo of a superseded schedule is worse than none, so the newest shot has to be the one the crew lands on.

That is the whole discipline: the cardboard scrap becomes a job photo instead of dumpster fill. The apprentice’s Sharpie work stops being throwaway and becomes the as-built. And the day the garage goes dead, the answer is a photo, not an hour of toning.

Where this falls apart is storage. A photo in your camera roll is barely better than the cardboard, because in fourteen months you will be scrolling ten thousand images trying to remember which Tuesday and which house. If the photo is not findable by the job, you have moved the loss, not fixed it. This is the same trap behind winning a callback argument with a photo you can actually produce: the shot only helps if you can put your hand on it when the phone rings.

Where the schedule should live

The answer is that the schedule belongs to the job, not to a phone. Give each job its own thread that remembers, and the panel photo lands on that job and stays there: the rough-in map, the trim schedule, the change you made in month three, all in one place with the address on top. When the service call comes in fourteen months later, whoever takes it opens the job and sees the last true version of the panel before the truck even rolls. The tech shows up already knowing the outside receptacle is fed off the master bath GFCI, resets it, and is back on the road while the old way is still toning circuits.

That is the idea behind Crewmigo: a thread per job that holds the proof your crew already gathers, so the as-built lives where the next person can find it instead of dying in the dumpster at cleanup. We are new, so put one panel on it. Shoot the schedule, keep it with the job, and see how it reads the next time a circuit goes dead a year out.