01 / Jobs that cross a county boundary
Step 1 · Where it starts
A quote request that establishes the jurisdiction first — the address, which county and municipality it falls in, and whether it needs a permit before anybody drives out to look at it.
Step 2 · What gets automated
Permit forms, inspection notices and plan comments are read as they arrive, sorted by which authority issued them, and attached to the right job rather than to whoever happened to open the email.
Step 3 · The process it plugs into
Each job carries its own checklist by jurisdiction — what has to be applied for, what has been issued, what inspection is outstanding — because the two counties do not ask for the same things or take the same time.
Step 4 · SolaceSentry review
A person confirms the jurisdiction before an application is filed. The system will point out that an address looks like it falls the other side of a line; it does not decide.
Step 5 · What leaves the system
A job file that shows exactly which approvals are in hand and which are still with an authority, and a customer who was told the truth about the timeline.
Proof metric: Working days lost waiting on an approval nobody had applied for yet, and the number of jobs that stalled at inspection.