30-min call with RobBook a proof-of-concept call
Job 01 · Permit desk

// Commercial sign companies · Sign permit packages

Sign permit packages, drafted from the city's own checklist, your survey and your drawing.

Each new location means finding that jurisdiction's sign code, reading its application and lining both up against the survey and the sign drawing. In a free AI proof of concept, AI drafts that permit packet from copies of 20 to 30 packets your office has already filed, and lists every requirement with nothing on file. Your reviewer, the person who knows your permitting best, compares each draft with the packet that really went in. Nothing goes to a building department.

Book a proof-of-concept call30 minutes with Rob
Filed packets
20 to 30
Sent to a city
None
Compliance rulings
None

// The one job

From a checklist and a drawing to a draft packet with its gaps listed

A sign permit starts from three things: the jurisdiction's sign code and application checklist, the site survey, and the drawing of the sign itself. Your coordinator reads each requirement, pulls the answer from the survey or the drawing, works out area and frontage the way that code defines them, gathers the landlord's letter and the electrical details, and chases whatever isn't there.

For the test, AI reads copies of those same inputs and drafts the packet for each location: every application field with its value and where the value came from, the attachments the checklist calls for, and a separate list of requirements with nothing on file for a person to resolve. Frontage and area, height and setback, illumination, zoning and landlord approvals and electrical listing each get their own lines. The draft reports what your files say and where the checklist asks for more, and stops short of saying whether a sign will pass.

One location's inputsChecklist
Jurisdiction
Checklist rev.
Survey date
Drawing rev.
RequirementCode sectionOn file
Illustration, not a real checklist
Compared with
survey and drawing
Draft permit packetDraft
Tenant frontage
Sign area
Height to top
Illumination
FieldSourceOpen item
Made-up packet, for illustration

// What makes it hard

Why no two jurisdictions take the same packet

Frontage is a defined word. Sacramento's Sign Permit Submittal Checklist, form CDD-0276, revised June 5, 2025, wants Building Tenant Frontage in lineal feet for attached signs and Parcel Street frontage for detached ones. Boulder's puts building frontage on the site plan, cites its definition at B.R.C. 9-16-1, then asks for tenant frontage separately on the elevation. Bend, Oregon has you give the primary facade as its code defines it. Paramus, New Jersey sizes a sign with a rectangle drawn around all of it, highest point to lowest. So the draft quotes each code's definition beside each number and shows which survey measurement it used.

The number of filings changes by city. Sacramento takes up to ten signs on one application for the same parcel, while Chicago wants a separate application for each sign, online and then a paper supplement. Chicago also requires a City Council order for any sign over 100 square feet or over 24 feet above ground level, and a Public Way Use Permit plus a council ordinance for anything extending over the public way, floodlights included. Its list of signs needing drawings sealed by an Illinois architect or structural engineer includes new sign boxes and channel letters, which then puts a licensed general contractor on the application. New York City separates the SG permit, filed for the copy, from an ALT permit when the sign hangs on a structure rather than directly on the wall, with electrical work filed apart by a licensed electrician. Each filing becomes its own line in the draft.

Illumination and listing ask for different details. UL 48, the Standard for Electric Signs, and NEC Article 600, Electric Signs and Outline Lighting, sit behind most of these lines. Paramus wants UL numbers on the electrical permit. Sacramento wants UL-approved electrical details giving illumination type, power source, disconnect switch, volts and amps, plus California's sign lighting certificate, NRCC-LTS-01-E. Washington's WAC 296-46B-600 holds every electric sign, whatever its voltage, to being listed or field evaluated by an accredited lab. Boulder asks for a full specification sheet with lumen rating and correlated color temperature on internally lit signs. Bend wants an image of the sign at night as well as by day, and its checklist says electronic message signs are currently prohibited. The draft sets what each form asks beside what your drawing and cut sheets supply.

Some approvals belong to someone else. Boulder requires a Building Owner Authorization Form when the applicant isn't the owner. Sacramento may need written approval from the owner or the management company for a shopping center, and separate encroachment permits for work in or over the right of way. Bend can ask for the master sign plan governing a tenant space and, for a historic site, photographs of every side of the building and of its neighbors along with the historic review application number; Boulder names a Landmark Alteration Certificate. The draft names each approval, who grants it and whether a copy is on file. Those decisions stay with the people who make them, and none of this is legal, zoning or engineering advice.

What stays open for a person. Sacramento's checklist asks for the composition of the existing wall, the mounting hardware's size, type, embedment, quantity and spacing, and the sign's weight, and may call for a special inspection form on field welds, foundations and post-installed anchors. Bend wants engineering on anything over 80 pounds or whenever its building official asks. When a survey doesn't answer one of those, the line stays open with a note on who can. Your reviewer, usually your permit coordinator, holds each draft against the packet that went in and the corrections that came back: values, code versions, attachments, and whether the open-items list caught what the city later asked for.

// What you send

Packets your office has already filed

Copies only
Commercial locations
01

20 to 30 filed packets

Application, plans and whatever came back from the city: correction notices, stamped sets, approvals. Include one that was rejected the first time, one reface, and one that needed a variance or a council step.

02

What each packet started from

The site survey, the sign drawing as released, photos, and the landlord's sign criteria or the customer's sign program where one applied.

03

The rules you filed under

The code sections and the checklist version in force on the filing date. If you can't find an old version, tell us, and that packet's draft is marked as unverified.

04

After the NDA

The NDA comes first, and copies follow. We never sign in to a city permit portal or to your job or estimating system.

// Before it starts

Settled before a packet is copied

The owner signs off on each of these in writing.

Terms for the permit testAgreed up front
Your reviewer
The owner's choice, often the permit coordinator
Success criteria
Written: which fields must match, and which gaps must be caught
Packets
Picked by your reviewer, across several jurisdictions
Who decides
Your team, and licensed people for structural and electrical calls
Price
A range for the live job, stated before any packet is copied
NDA
Signed before the first file moves

// How the test is judged

The packet you filed beside each draft

Field by field
Your reviewer decides
Across the same 20 to 30 packetsWhat your team filedDraft from the test
Frontage and sign area, with the code's definition quotedFilled in on your packetsFilled in on your packets
Height, setback and clearance fieldsFilled in on your packetsFilled in on your packets
Illumination type and the listing details the form asks forFilled in on your packetsFilled in on your packets
Landlord, zoning and historic approvals namedFilled in on your packetsFilled in on your packets
Attachments against the checklist version in forceFilled in on your packetsFilled in on your packets
Requirements marked as having nothing on fileFilled in on your packetsFilled in on your packets
Corrections the city asked for that the draft would have raisedFilled in on your packetsFilled in on your packets
Time from survey and drawing to a packet ready to checkFilled in on your packetsFilled in on your packets
Blank for now. These cells fill in only once your own filed packets have been run.Your reviewer scores each row and makes the call.

// After a yes

A month of new locations

If your reviewer says yes, new locations get the same draft packet for about 30 days.

Your permit coordinator checks every packet and sends it the way your office does today. Licensed people still seal, sign and answer for what they always have.

Live drafts keep being compared with what your team files. Whether a next job follows is up to you, at its own price.

// Possible next jobs

After permit packets, if you choose

Ranked, not promised
Each priced alone
  1. 01

    Rollout site surveys

    Survey reports from a multi-location program read into one schedule, feeding the same packets.

    Next
  2. 02

    Landlord sign approval requests

    The request a landlord or property manager needs drafted from the drawing and that center's sign criteria.

    Then
  3. 03

    Permit status summaries

    Open applications across jurisdictions gathered from your own log into one list for the project manager.

    After that

// One hard limit

No packet is submitted and no sign is ruled compliant by the AI.

The test never touches your job or estimating system, never files anything with a building department, and never decides that a sign complies with a code or that a wall can carry a load. A person checks every packet before it goes out, and licensed engineers and electricians make the structural and electrical calls. Nothing here is legal, zoning or engineering advice.

Priced per job. You get a range before the proof of concept and a fixed price before you sign.

Rob gives the range on the call, once he knows how many jurisdictions you file in and roughly how many packets go out in a month.

// Questions

Permit questions

Can the AI tell us what a city will approve?
No. It compares your survey and drawing with what that city's code and checklist ask for, then lists differences and gaps. Approval belongs to the jurisdiction, and whether to file belongs to your team.
Every city has its own form. How does the test handle that?
That is the point of testing it across jurisdictions. Each draft follows the application and checklist version you send for that location, and when a version is missing the draft says so instead of borrowing another city's.
What about stamped drawings and engineering?
The draft lists when a checklist asks for sealed drawings or calculations and whether your file holds them. It writes no calculations and seals nothing. Those stay with your licensed engineer.
Does this replace our permit expediter?
It isn't built to. The test asks whether a first draft and a gap list can be ready when your coordinator or expediter opens the file. Anyone who speaks with a city today keeps doing so.
Should we include packets the city corrected?
Yes, those are the most useful ones. A correction notice shows what the reviewer wanted, so your reviewer can see whether the draft would have raised the same point before the packet went in.
Rob Eason

Rob Eason, founder

// Book a proof of concept call

Start with last quarter's filed packets.

Thirty minutes with Rob on your company, your role, the jurisdictions you file in and roughly how many packets go out each month. Surveys, drawings and packets stay with you until the NDA is signed.

  • Co-owned a 60-employee financial services firm and sold his share to his partner.
  • Ran GOSO Technologies, a Boston solar company rated 5/5 across 24 Google reviews.
  • 5/5 across 83 reviews in HighLevel's Certified Admin Directory.
  • 4.3/5 from 6 Google reviews of Massmarket AI.
  • Every directory and Google review, critical ones included, is shown word for word at massmarket.ai/reviews.
  • Takes every proof-of-concept call himself.