Permit queue
Each application shows its filing date, the last city response and the owner responsible for the next step.
A general manager at a sign shop often hears about a missed install from the property manager standing in front of an unlit sign. A manager app for sign shops lays out the permit queue, crew load and install backlog on one screen, so a problem is visible days before a crew is sent.
A sign job passes through more hands than most small trades. It moves from quote to artwork approval, then to a permit, to fabrication, to an install crew and finally to an invoice. A generic dashboard can count jobs, but it cannot tell a manager that a permit has stalled for a week while the fab bay waits.
The margins are thinner than they look. Channel letter margin depends on aluminum, acrylic, LEDs and power supplies whose prices move, and a rush job can push a crew into overtime. The manager needs material cost and labor hours beside each sale, or the shop keeps quoting work that loses money.
Start with three views: the permit queue view, the install calendar and the job pipeline from quote to invoice. This permit queue lists each application with its filing date and the last city response, so a stalled file is obvious. The install calendar shows crew load by day, and the pipeline shows where each sign sits.
Leave margin modelling by sign type, multi-location reporting and forecasting for a later phase. The margin view that matters first is simple: actual materials and labor on each finished job. Add the rest once the daily views are part of the routine. The margin view stays simple on purpose, so the number people argue about is the one they trust.
The general manager opens the app at half past seven and sees a permit flagged for a restaurant storefront, filed nine days ago with no city response. He opens the queue, adds a note and assigns the follow-up to the permit coordinator who knows the inspector's schedule. The app logs the note and the time. The journey should feel like a morning checklist, not a report to read.
Next he checks the install calendar. Two crews are booked on the same Thursday at sites across town, and one site has no confirmed lift access. He moves that install to Friday, and the app flags the change for the property manager's approval before anything is sent.
Before lunch he opens the pipeline and sees a channel letter job stuck in fabrication because the power supplies have not arrived. He asks the fab lead to start the next job in the queue and asks purchasing for an expected delivery date. The pipeline records the new date against the job.
Each application shows its filing date, the last city response and the owner responsible for the next step.
Crew loads by day, with access status and weather holds shown against each site.
Every sign moves through quote, artwork, permit, fabrication, install and invoice, with the date of each stage.
Actual materials, labor hours and rework are logged on each job, so the margin figure reflects what happened.
Sign shops feel the calendar in waves. Grand openings and new retail leases cluster in spring and early fall, and a holiday push fills the fab bay before the year closes. Yard sign rushes arrive with short deadlines around election season, and cold or wet weather can hold outdoor installs for days.
The manager view should support crew load planning that shows those waves early. Compare the coming month with the same month last year, and mark weather holds on the install calendar. When the fab bay is overloaded, the app should show which jobs can slip without a client penalty, so the general manager makes that call early.
The first mistake is building views that show every field the office can type into. A general manager needs the permit queue, the install calendar and margin on a few jobs. Start with those, then add others only when someone asks for them twice. Trust in the views grows when every number can be traced back to a job.
The second is leaving permits and installs in separate tools, because every handoff becomes a phone call and the call is where the install slips. The third is trusting the quoted margin, since rework and rush costs never reach the estimate.
Measure on-time installs, the number of permits that stall beyond the first city response and crew utilization on each route. Track margin per job by sign type using actual costs, the rework cost by cause and the share of rush jobs that moved a planned install. An install backlog report should show all of this in one place.
Compare each figure with the same period before launch, and review the list monthly with the general manager. If he stops asking for the status round-up and starts asking about margin by job type, the app has become the working record. The real test is whether a stalled permit is caught before the property manager calls.
No. The coordinator still talks to the city, the property manager and the crew. The app holds the dates, owners and status, so the coordinator spends less time rebuilding where each job stands.
Often, yes. The app can pick up job numbers, invoice status and material costs from QuickBooks Online where the connection is supported. Design files stay in Illustrator or CorelDRAW. We confirm each link during the free scoping call.
Margins are limited to the general manager and the finance lead. Crew leads see the calendar for their route, the coordinator sees permits and installs, and the owner decides any exceptions. Each change to a role is logged.
Yes. Each permit has a city response date, and the app raises a warning when a file goes without a response beyond the period the shop sets. The alert goes to the named owner and the general manager, so nobody learns about it from a property manager.
The starting figure for a mobile build is $4,500, and the written scope sets the final number for each view, role and connection. We confirm the scope in writing before work begins.
Book a free scoping call to map your permit queue and get the price in writing.