Overview#
One fixed intake form is rarely enough. A housing repair request, an environmental complaint, a safeguarding notification, and a service feedback form all need different fields, different routing logic, and different evidence requirements. If teams have to wait for a code release every time a form changes, operational services stall behind small admin updates.
The Dynamic Form Builder and Public Submission Workflows module gives organisations a configurable form layer that can be published internally or publicly, routed into downstream workflows, localised for different audiences, and governed with retention, lawful-basis, and access rules. It is built for services that want structured intake without turning every new form into a bespoke development project.
Last Reviewed: 2026-04-07 Last Updated: 2026-04-07
Key Features#
- Template Authoring: Create structured form templates with named fields, descriptions, and category-specific layouts.
- Conditional Logic: Show or require fields based on earlier answers so forms stay short for simple cases and detailed for complex ones.
- Public and Authenticated Publishing: Publish forms openly or require sign-in when the workflow needs identity assurance.
- Workflow Routing: Attach forms to downstream routes, SLAs, and review queues instead of relying on a shared mailbox.
- Lookup and Reference Support: Use controlled lookup values and reference-number retrieval to keep submissions consistent and traceable.
- Localisation Support: Present the same form in multiple locales without maintaining separate versions by hand.
- Retention and Lawful-Basis Controls: Capture governance settings at the template level so data handling rules travel with the workflow.
- Submission Analytics: Monitor volumes, statuses, and bottlenecks by template rather than pulling statistics from multiple teams.
Use Cases#
- Municipal Service Intake: A council publishes category-specific service forms for roads, waste, environment, and housing requests.
- Representative Casework Intake: An elected member office submits structured constituency cases with the right routing and evidence fields.
- Clinical or Welfare Follow-Up: A service publishes questionnaires, consent forms, or referral follow-up forms without commissioning a new app screen each time.
- Incident and Complaint Reporting: Internal users submit structured operational reports with different branching paths depending on incident type.
- Multilingual Public Services: One template supports multiple languages while preserving a single workflow and reporting view.
Integration#
- Municipal CRM and Public Portal: Published forms can be embedded directly into citizen-facing service journeys.
- Identity and Access Services: Authenticated forms can align with citizen, representative, or staff sign-in flows.
- Workflow, SLA, and Notification Services: New submissions can trigger review queues, deadlines, and updates automatically.
- Reporting and Analytics: Submission data can feed dashboards and management reporting without re-keying.
- Lookup and Reference Services: External catalogues and internal code lists can drive controlled field values.
Open Standards#
- JSON Schema: form structure and validation can align with a standard machine-readable way to describe fields and constraints.
- RFC 8259 JSON: template definitions, logic blocks, and submissions can be exchanged in a standard structured format.
- BCP 47 Language Tags: locale variants can be identified using the standard language-tag model used across multilingual systems.
- WCAG 2.2: published forms can align with recognised accessibility requirements for keyboard, screen-reader, and low-vision users.
- OpenID Connect and OAuth 2.0: authenticated form journeys can integrate with standard identity and delegated-access patterns.
- ISO 8601: submission, deadline, and status timestamps use a standard date-time format.