Create your first permit project
Set up a project with the address, jurisdiction, type, and work description so PermitOS can run accurate prechecks.
Last updated 2026-05-01
Why accurate setup matters
Every PermitOS workflow — readiness scoring, missing-document detection, and zoning notes — keys off your project fields. The more precise the project, the more trustworthy the precheck output.
Required fields
Title, jurisdiction, address, project type, and work description. Estimated construction value and desired permit type are recommended for sharper checks.
Project type
Pick the closest type (e.g. ADU, single-family addition, tenant improvement). Type drives which document categories the precheck expects.
Jurisdiction
Use the exact name of the authority having jurisdiction. PermitOS uses this as a label only — it does not call the jurisdiction's permitting system.
Work description
Write 2–4 sentences covering scope, square footage, and any new systems (electrical, plumbing, structural). A vague description triggers a 'needs more detail' issue in your precheck.
Next step
Once the project is created, open it and switch to the Documents tab to upload your packet.
Related guides
Upload and categorize permit documents
Categorize each document so the precheck checklist can match it. Files are stored privately, scoped to your organization.
Run a rules-only Permit Precheck
Rules-only precheck verifies project metadata and document inventory. It does not read plan contents.