Potential citizen self-service portal requirements
Discuss whether an approved future implementation should evaluate applicant-facing forms, documented accessibility needs, and staff-controlled application status.
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.
Applicant-facing workflow requirements
Identify the jurisdiction's existing public channels, accessibility obligations, authorized records, communications policies, and payment rules. No public portal, payment processor, applicant assistant, or production status service exists.
Confirm buyer and vendor permissions
Any records access, third-party export, payment processor, transfer method, vendor interface, or system mapping must be separately authorized, implemented, and independently verified.
Separate proposed requirements from implemented capabilities
The public website shows an illustrative fictional-data preview only. No working product, deployed integration, production security control, customer result, savings estimate, or implementation schedule is claimed.
Review a separately scoped jurisdiction pilot
Discuss the illustrative workflow, your actual requirements, and the purchasing approvals your jurisdiction determines.
Discuss a proposed pilot