Projects and permit packets
Project setup fields and how a project ties documents, reports, issues, corrections, zoning checks, and activity together.
Last updated 2026-05-11
Project fields
title, jurisdiction, address, project_type, work_description, optional estimated_construction_value, optional desired_permit_type, status.
Why fields matter
The rules-only precheck consumes these fields directly. Missing required fields lower the readiness score and produce explicit issues.
Linked records
permit_documents.project_id, precheck_reports.project_id, precheck_issues.project_id, correction_tasks.project_id, zoning_checks.project_id, activity_log.project_id.
Lifecycle
draft → in_review → submitted → archived. Status changes are recorded in activity_log.
Related docs
PermitOS concepts
Glossary of the entities PermitOS works with: projects, packets, documents, prechecks, issues, scores, corrections, zoning checks, and activity.
Document intake
How files reach PermitOS, what metadata is stored, and what happens when document extraction is not configured.
Rules-only Permit Precheck
Deterministic readiness check that runs against project fields and uploaded document categories. No AI required.