Match the research job to a covered market, then verify the city source, newest record, and available fields before your team acts.
Each market page identifies its public source, newest published record, and available fields before you subscribe.
PermitGrab is useful when a public record can add dated context to a real research process. Select the work your team actually controls; each route starts with the city source, newest published record, and fields available in that market.
For product reps, branches, and distributors deciding where public construction activity merits account or territory research.
Published project context, not a purchase order, product list, or promised buyer.
Explore supplier researchFor alarm, sprinkler, suppression, standpipe, and egress teams reviewing source-published life-safety context before independent project research.
Explicit scope only—not an open bid, service request, or subcontract invitation.
Explore fire/life-safety researchFor equipment-rental, temporary-fencing, portable-facility, and site-service teams evaluating source-published new-construction context by territory.
Construction activity for research—not a rental reservation, service order, supplier selection, or open bid.
Explore equipment and site-service researchFor facilities and portfolio teams watching newly published permit activity at one selected covered-city property.
An exact permit-record watch—not a condition, risk, ownership, or compliance score.
Explore property monitoringFor facilities, portfolio, and diligence teams reviewing a known property through the specific permit or status fields a supported city publishes.
Not a lien, title, closing, legal, condition, or property-availability result.
Compare selected-property workflowsFor design-build, estimating, and business-development teams adding public project context to a market or account-research workflow.
Not plans, specifications, bidder lists, or a replacement for a plan room.
Explore project-team researchFor Washington subcontractor, supplier, facilities, and project teams reviewing one already-known prime company, awarding agency, or published project identity in the official L&I filing record.
A published filing is research context—not an open bid, a contact list, project availability, or a procurement result.
Explore Washington public-works researchFor procurement, compliance, risk-operations, and project teams reviewing one New York Contractor Registry Certificate number they already know.
A publisher record is not current registration, bid eligibility, insurance, qualification, or a contractor directory.
Research a known New York contractor certificateInsurance, property-data, and other high-volume teams can request a human coverage review for a defined geography, fields, cadence, and permitted use. PermitGrab does not offer a public API, a blanket bulk feed, or a uniform national-coverage promise.
A permit is a public-record research input. The right workflow depends on your job, your market, and what the relevant source actually publishes.
Start with supplier and distributor research when the job is territory or account prioritization from published project context. Review a source-dated city sample before treating any market as useful.
No. The fire/life-safety workflow is for research on explicit published scope. A permit does not establish an open bid, subcontract need, service request, or decision-maker intent.
It sends permit-only alerts for newly collected records matching the same city-scoped canonical property identity. It does not assess property condition, risk, ownership, or compliance.
Request a coverage review with the geography, fields, cadence, volume, and permitted use. PermitGrab will assess actual public-source support before discussing a pilot; there is no public self-serve API or blanket data-feed promise.