Citizen Portal Development

Service forms built around the actual eligibility and conditional logic of each service: the questions that depend on previous answers, the document requirements that change based on the applicant's circumstances, and the sections only shown to certain categories of applicant. Form validation catches errors at the point of entry rather than after submission, with clear error messages that meet the plain-language requirements of government accessibility guidance. Save and return functionality lets citizens start a complex application, save their progress, and come back to it without losing what they've already entered. An application reference number is generated at submission with confirmation sent to the applicant's email. Multi-step form journeys include a progress indicator so citizens can see how much of the application remains at each stage.

Identity verification is integrated into the application journey at the point where the service requires it: from basic email verification for low-risk services to document-based identity checking for services with higher fraud risk. Document upload includes file type and size validation, virus scanning, and secure storage with the retention period configured to your data schedule. A document checklist is presented to the applicant before they start so they know what to gather before the form times out. An automated document completeness check at submission notifies the applicant if a required document is missing or the uploaded file is the wrong format. That check happens at submission rather than after an officer has spent time reviewing an incomplete application. Secure document storage makes files accessible to officers through the back-office case management interface without requiring them to download and re-upload anything.

Citizen-facing case tracking shows the current status of every active application the citizen has submitted: where it is in the process, what the next step is, what the estimated timeline is, and whether any action is required from the citizen before the application can proceed. Status update notifications go to the citizen's email or mobile when the application moves to a new stage, a decision is made, or additional information is needed. Citizen-initiated correspondence from within the tracking portal lets the applicant upload an additional document, ask a question, or respond to an officer request without logging a new enquiry through a separate channel. Application history is retained in the citizen's account for the configured retention period so they can access decision notices, correspondence, and previous applications without contacting the service. Contact centre integration means officers see the same case view as the citizen when handling telephone enquiries, reducing call handling time.

Payment processing is integrated into the application journey at the appropriate point: before submission for services where the fee is fixed, or after officer assessment for services where the fee depends on the application outcome. Integration with your existing payment gateway or council payment system means online payments reconcile with your finance system automatically rather than requiring a manual reconciliation step. Fee calculation logic is built into the form based on the application details: the building regulation fee that depends on the type and value of the works, the licence fee that varies by premises size, or the planning fee calculated from the proposed floor area. Payment receipts are generated automatically and sent to the applicant's email at the point of payment. Partial payment and payment plan handling covers services where fees are paid in instalments. Refund management handles applications withdrawn or refused where a refund is due under your fee schedule.

Integration with your existing back-office systems, including the case management system, planning system, finance system, and housing register, means applications submitted through the citizen portal appear in the back-office workflow without requiring an officer to re-enter the information. The integration architecture is designed around what your back-office systems actually support: REST API where available, file-based exchange or database-level integration where APIs aren't available, and a middleware layer for legacy systems with proprietary data formats. Address lookup integration with your property database or the national address gazetteer means applicants select from validated addresses rather than typing free text. GIS integration connects location-based services where the application needs to be associated with a specific property, planning zone, or service area. Data mapping from the citizen portal application form to the back-office system's data model is documented before development begins.

WCAG 2.1 AA accessibility compliance is built into the development process from the first sprint, not audited against at the end. Every component is built using accessible HTML patterns, with keyboard navigation, screen reader compatibility, and sufficient colour contrast tested throughout development. An accessibility audit is conducted before go-live with remediation of any issues identified. Security controls include HTTPS, secure session management, CSRF protection, and input sanitisation against injection attacks as a baseline. Data protection compliance includes a Data Protection Impact Assessment for services handling personal data, retention periods configured to your data schedule, and subject access request tooling for the obligations that apply to citizen records. Penetration testing is facilitated before go-live with remediation of any critical findings.