Proposed permitting-intake pilot requirements
This guide identifies questions a jurisdiction would need to resolve before approving or implementing a PermitDesk pilot. It does not describe an existing production application or deployed infrastructure.
Proposed scope only. Illustrative proposed pilot only. No working PermitDesk application, public intake portal, production AI workflow, payment connection, third-party integration, or implemented security control is represented as existing. Every production capability requires a separately scoped, buyer-approved implementation.
1. Proposed scope and architecture
Define one permitting or licensing workflow, staff owners, authorized data, required approvals, and measurable acceptance criteria before any implementation decision.
2. Intake requirements
Document the jurisdiction's existing application channels, submission fields, document checklists, retention obligations, and accessibility requirements. No public application portal is currently represented as deployed.
3. Review and completeness requirements
Potential classification, completeness checking, or automated assistance must be separately scoped, authorized, implemented, and verified. Jurisdiction personnel retain every eligibility and permitting decision.
4. Department routing and fee requirements
Identify authorized reviewers, department handoffs, status requirements, and the jurisdiction's approved fee schedules. No routing engine, fee engine, notification service, or inspection scheduler is represented as existing.
5. Potential data exchange
A jurisdiction and its vendors must independently confirm whether exports, interfaces, permissions, transfer methods, and mappings are available. No finance, GIS, payment, records, or third-party integration is deployed.
6. Security and data-handling review
Hosting, encryption, access control, logging, retention, incident response, model-use restrictions, and disposal are proposed requirements for buyer review. They have not been independently verified or represented as production controls or certifications.
7. Implementation and purchasing approvals
Any timeline depends on purchasing approval, buyer and vendor permissions, documented requirements, implementation work, and independent verification. No standard go-live timeline or customer deployment is claimed.
8. Working application status
The public preview uses fictional sample figures to illustrate a potential workflow. There is no separate live PermitDesk application, production integration, public intake portal, or deployed automated-review system.
Review a separately scoped jurisdiction pilot
Discuss the illustrative workflow, your actual requirements, and the purchasing approvals your jurisdiction determines.
Discuss a proposed pilot