Revision clouds and solar resubmittals

A resubmittal is not a fresh submission. It is an argument that specific comments have been addressed and nothing else moved. Revision marking is how you make that argument, and skipping it is the cheapest way to turn a two-day recheck into another full review.

The three parts

• The cloud. An irregular outline around the changed content. It should enclose the change and not much else — a cloud around half a sheet says "something in here" and helps nobody.
• The delta. A numbered triangle beside the cloud, keyed to the revision table. Revision 1 is delta 1 on every sheet it touches.
• The revision table. Number, description, date, author. In or beside the title block, on every sheet — including sheets that did not change, showing the current revision level.

Write descriptions a reviewer can match to their own comment

Bad: "Electrical revisions." Good: "Comment 3 — added grounding electrode conductor and 250.66 sizing to one-line."

The reviewer is holding their correction list. A description that quotes their comment number lets them tick it off. A description that does not makes them go looking.

What must stay stable

This is the part people underestimate. A reviewer compares the resubmittal against the sheet they marked up. Anything that shifts without a cloud undermines that comparison:

• Sheet numbers. Do not renumber. If you must insert, use 4A rather than renumbering 5 through 10 — every reference in your correspondence stays true.
• Circuit and conductor tags. If tag C means a different run than it did last time, the reviewer's notes are now wrong. Keyed tags should derive from something stable about the run, not its position in a list. See keyed conductor callouts.
• Equipment reference numbers in the schedules.

Do not silently improve things

Tempting: while you are in there, you tidy a label, resize a conductor, move a disconnect. Uncelouded, those changes are invisible to the reviewer and they are exactly what erodes trust when found. Cloud every change, even the improvements — or leave them for the next revision.

Keep the superseded set

Archive the exact set you submitted, per revision. When a comment says "as noted on the previous submittal", you need the previous submittal, not your best reconstruction of it.

Tools that hash-link each revision make this automatic: OneLine Studio's provenance chain fingerprints every design revision so any submitted set can be verified against the lineage it came from, and you can always show what was filed when.

A short checklist

1. Cloud the change, tightly. 2. Delta beside every cloud, keyed to the table. 3. Revision table on every sheet, current level shown even where nothing changed. 4. Descriptions that reference the reviewer's comment numbers. 5. No renumbering of sheets, circuits or tags. 6. Archive the superseded set.

See also: how to read a plan-check correction and why solar permits get rejected.

> Design aid — a licensed electrician or PE must review and stamp before filing.

Educational reference, reviewed 2026-07. A design aid, not a substitute for a licensed electrician or PE. Confirm the enforced NEC edition and local amendments with your AHJ.