Ready to verify your roster
Each subcontractor is checked against the Florida DBPR registry and county permit records.
A sweep checks every subcontractor on the roster against the state register. The filter in the sidebar only hides rows on screen, it never changes what gets checked.
What changed
Since the previous check
Exposure across the roster
Checks over time
Agent activity
Live · every registry answer as it arrives
Findings View all
Ranked by exposure, not by expiry date
Add subcontractors
Proto resolves the business name from the registry, you only need the licence number.
The licence is looked up as you add it, so a typo is caught immediately.
Roster
Everyone working under this project
| Subcontractor | Licence | Trade |
|---|
Findings
A dead licence carrying open work outranks a dormant one expiring next week.
Triage & notice
The agent orders the morning and drafts the notice. It cannot invent a number that is not in the findings.
Project setup
Three things: what the project is, where it is, and how often Proto should look.
Who is on this project
Paste the licence numbers you want watched. Proto looks each one up as it imports, so the business name comes from the state register rather than from whoever typed the list.
Keeping the list in a Google Sheet instead? Open Roster to connect one, or to add a single licence and remove people.
How often should Proto check?
A licence verified once is a snapshot. Verified on a schedule it becomes a watch, which is the whole point, Proto re-checks on its own and speaks up only when something changed.
Where should Proto reach you
Optional. The first check sends the whole roster, with every licence number, class, status and expiry date. After that each check reports what moved, and says so plainly when nothing did, so you can always tell working from broken.
Licences come from the Florida DBPR register; permit activity from county ArcGIS services. Both are public records, so there is nothing to connect and no key to manage.