SPCSEARPERMIT OS
HOW IT WORKS

One controlled record from intake to authority response.

SPCSEAR organizes the permit process around evidence, explicit responsibility, and fail-closed automation—not an untraceable chatbot answer.

01

Verify the contractor

Company identity, TDLR licenses, Master Electrician assignment, insurance, and local registration are reviewed before activation.

02

Create the job

The office records the project address, dwelling, work type, and exact scope facts in a versioned intake.

03

Resolve the authority

Server-side geocoding and a published boundary produce a candidate jurisdiction with near-boundary cases routed to people.

04

Run procedural checks

Only currently published, effective-dated workflows evaluate the immutable job facts and identify missing information.

05

Retain documents

Uploads enter quarantine, pass scanning, and remain bound to their checksum and retention record.

06

Human review

A qualified reviewer accepts the procedural record or returns specific changes without silently overwriting prior evidence.

07

Approve and assemble

The contractor controls technical approval. The packet manifest binds every accepted artifact and input version.

08

Coordinate the next step

When separately authorized, Managed Submit and Concierge preserve filing and follow-up evidence without guaranteeing approval.

WHAT AUTOMATION DOES

Repeat the reliable work.

  • Validate structured inputs
  • Bind evidence to exact versions
  • Apply published procedural checks
  • Surface blockers and owners
  • Preserve immutable audit events
WHAT PEOPLE CONTROL

Make consequential decisions.

  • Confirm the permitting authority
  • Approve technical content
  • Authorize filing and payment
  • Perform electrical work
  • Respond to the AHJ