Customer Submittal / Drawing Approval SOP

This procedure defines how Blitzpanel prepares customer submittal drawing packages, transmits them for approval, tracks approval status and markups, and incorporates accepted comments before a job is released to build.

It exists to ensure production only ever builds to a drawing revision the customer has actually approved, preventing unauthorized deviations, disputes, and warranty exposure.

A disciplined submittal process gives Sales, Engineering, and Production a shared, auditable record of what was submitted, what the customer changed, and what was ultimately released to the shop floor.

Applies to all customer-facing submittal drawing packages issued for approval prior to production release, across new builds, re-orders, and jobs with customer-requested revisions.

Covers assembling the submittal package, transmitting it to the customer, logging and tracking approval status and markups, and incorporating accepted comments through to release-to-build.

Applies regardless of transmittal method (email, customer portal, printed package). TODO: confirm approved transmittal methods and any customer-specific portals.

Does not cover initial technical scoping performed during quoting (see Quoting SOP) or changes made after a job has already been released to build (see Engineering Change Order / Revision Control SOP).

Submittal package — the drawing/document set (schematic, panel layout, bill of materials, nameplate and label copy) issued to the customer for review and approval before build.

Redline / Markup — corrections, changes, or annotations the customer returns on a submitted drawing.

Approved As Noted (AAN) — customer approval conditioned on incorporating specific noted corrections, without a further formal re-submittal cycle. TODO: confirm whether Blitzpanel requires a follow-up re-submittal after AAN or proceeds directly to release.

Rejected / Resubmit — customer disapproval requiring the package to be revised and re-issued through a new submittal cycle.

Released to Build — the point at which Engineering/Document Control formally authorizes Production to begin work against an approved drawing revision.

Role	Responsibility
Design / Submittal Engineer	Assembles the submittal package, incorporates customer markups, and maintains drawing revision history.
Sales / Account Manager	Transmits the package to the customer, owns the customer relationship during review, and follows up on overdue responses.
Customer / Customer's Engineer	Reviews the submittal package and returns an approval status and any markups within the agreed response window.
Quality	Verifies that all customer comments are incorporated or dispositioned, and that SCCR/listing marks are correct, before release-to-build sign-off.
Document Control	Assigns submittal drawing numbers and revisions, maintains the transmittal/approval log. TODO: confirm whether this is a standalone role or folded into the Design Engineer role.
Production / Scheduling	Holds job start until release-to-build authorization is received; begins work only against the released, approved revision.

Submittal drawing template covering schematic, panel/door layout, bill of materials, and nameplate/label copy. TODO: link the current Blitzpanel submittal template.

Transmittal / approval tracking log recording submittal number, revision, date sent, date returned, and status. TODO: name the system of record (spreadsheet, PLM, or CRM module).

PDF markup or customer-portal tool used to receive and review redlines. TODO: name the standard markup tool, e.g. Bluebeam.

UL508A listing/labeling and SCCR reference material used to confirm submittal content is consistent with the compliance basis (see UL508A Compliance Documentation SOP).

6.1 Preparing the submittal package

Compile the package: schematic/wiring diagrams, panel and door layout drawing, bill of materials, and nameplate/label copy consistent with the approved quote and PO.

Assign a submittal drawing number and initial revision (e.g., Rev A) per Job Traveler / Document Control SOP.

Confirm the package reflects the intended SCCR basis, component ratings, and any customer-specified options or exceptions carried over from the quote.

Perform an internal engineering/QC self-check of the package against the RFQ/PO scope before it is transmitted to the customer.

6.2 Submitting for customer approval

Generate a transmittal cover sheet listing package contents, submittal number/revision, and the requested response date. TODO: define the standard response window (business days).

Send the package via the approved transmittal method and log the transmittal date, recipient, and submittal status as "Pending" in the tracking log.

Clearly mark all drawings "FOR APPROVAL — NOT FOR CONSTRUCTION" (or equivalent) until a formal approval is received. TODO: confirm Blitzpanel's standard stamp wording.

Place a schedule/production hold on the job so build cannot start before release-to-build authorization (see Job Traveler / Document Control SOP).

6.3 Tracking approval status & markups

Update the tracking log with a status of Pending, Approved, Approved As Noted, or Rejected/Resubmit for each transmitted package.

Follow up with the customer on the standard cadence if a response is not received by the requested date. TODO: define the follow-up cadence, e.g. every N business days.

On receipt of markups, review them against the original package for buildability, and for cost or schedule impact; route scope-adding markups to Sales/Estimating for pricing and schedule impact before proceeding (see Quoting SOP).

Escalate any customer-requested change that affects SCCR, listing basis, or other UL508A compliance elements to Engineering/Quality for review before it is accepted. TODO: verify exact UL508A clause governing SCCR/listing changes before citing to the customer.

6.4 Incorporating comments & release to build

Update the drawings to reflect all accepted/incorporated comments and increment the drawing revision per Engineering Change Order / Revision Control SOP.

Disposition each individual markup item (incorporated, declined with rationale, or deferred) and retain this record with the submittal package.

Quality verifies that every customer comment has been addressed or formally dispositioned before signing off on release.

Route the final Approved or Approved-As-Noted documentation into the job traveler and formally release the job to build (see Job Traveler / Document Control SOP).

Production must never start against a package still marked "For Approval"; any exception requires documented risk-buy sign-off. TODO: define the exception/risk-buy approval path and who may authorize it.

Transmittal/approval log: submittal number, revision, dates sent and returned, customer contact, and current status.

Customer-returned markup/redline documents, retained as evidence of the approval basis for the released revision.

Final approved drawing set matching the released revision, filed with the job traveler (see Job Traveler / Document Control SOP).

Retention period for submittal and approval records. TODO: set retention policy.

Quoting SOP, Job Traveler / Document Control SOP, Engineering Change Order / Revision Control SOP, UL508A Compliance Documentation SOP, Design Checklist / Final Checkoff Gates SOP.

UL508A — Standard for Industrial Control Panels (listing marks and SCCR documentation basis referenced in submittal packages). TODO: verify exact clause references before citing.

NFPA 79 / NEC references where applicable to submittal drawing content (e.g., disconnect/marking requirements). TODO: verify applicability and exact clause references before citing.

Back to document index