Govform vs. LocalGov Drupal and LocalGov Forms

Already using LocalGov Drupal? Compare extending LocalGov Forms with Govform for council transactions, including the work to build, run and maintain each service.

LocalGov Drupal is an open-source council publishing platform. LocalGov Forms adds configuration, styling and components to Drupal Webform. Both this stack and Govform support capable online forms. The decision is how much work your council needs to build, operate and maintain the complete transaction.

Reviewed 19 October 2026. This is a comparison of published capabilities and delivery responsibilities, not a price benchmark or a measured savings claim. Compare the supported installation and Govform plan you would actually use.

Which approach fits your service?

Extending LocalGov Forms can be economical when your existing modules, supplier agreement and team already meet the need. Shared development and supplier choice are strengths. You can also retain LocalGov Drupal for publishing and use Govform for selected transactions.

Consider Govform when you want to configure journeys, reviews and supported connections in one maintained platform. Built-in service-performance reporting helps identify difficult questions; configurable review workflows reduce manual handoffs; permissions and controlled releases help teams change services safely. These are practical benefits to test against your current approach.

Compare initial build and ongoing maintenance costs

LocalGov Drupal's shared components and absence of licence fees can reduce costs. A Govform subscription is a recurring cost that needs to earn its place. Its potential advantage is less repeated development, reporting setup and platform upkeep across your services. Include configuration and integration work on both sides.

Webform is also configurable by non-developers: routine editor changes do not automatically require a developer. Specialist effort depends on the change and the installed solution. See Webform's editor and configuration features.

Costs to evaluate for the same service over three years
Area	Govform	LocalGov Drupal / LocalGov Forms
Initial build	Configure the journey, reviews and supported connections. Include content design, migration, training and acceptance testing, plus any delivery support.	Configure Webform and reuse available components. Include any extra modules, custom development and integrations, plus the same content, migration, training and testing work.
Recurring charges	Platform subscription, usage and agreed support, plus connected providers and external systems.	No Drupal or Webform licence fee. Include hosting, supplier support, external services and any community subscription you choose.
Platform maintenance	Govform maintains the managed platform. Your team still owns service rules, content and external integrations; agree support responsibilities.	Agree who applies core/module security updates, checks compatibility, maintains custom code and tests releases. A managed supplier may already cover this.
Reporting and assurance	Use built-in journey reporting and release controls. Include service accessibility, integration testing and your own assurance work.	Include setup and upkeep of the reporting and release process you need, plus the same service-level assurance. Reuse existing provision where it fits.
Routine service changes	Measure staff time to change and test rules, questions, reviews and mappings. Include specialist help where required.	Editors can maintain configured Webforms. Measure staff time and any supplier work for changes to modules, custom logic or integrations.
Staff processing	Measure the review, correction, rekeying and exception handling left after the configured workflow and integrations.	Measure the same work across Webform, workflow extensions and the receiving systems. Credit existing automation.
Migration and exit	Include overlapping operation, data transfer, training and ownership of the connection to your website. Agree export, contract and migration requirements.	Include equivalent transition work, data transfer and supplier handover. Source-code access helps portability, but moving a working service still takes effort.

Use current Govform pricing and support scope alongside a quote for your Drupal implementation. Compare initial delivery + three years of recurring charges, maintenance, routine changes and staff processing + migration and exit work. Use the same service volumes and change assumptions; separate cash expenditure from staff time released.

If you retain LocalGov Drupal for your website, its core hosting and maintenance costs remain. Compare the additional cost of extending LocalGov Forms with the additional Govform cost. Count savings only where expenditure is removed or work is reduced. Do not count patching or support twice if your existing Drupal contract already includes it.

A small estate of stable, well-supported forms may be economical to retain. Across frequently changing services, a maintained transaction platform may reduce repeated specialist work. Measure that advantage with your own services and quotes.

Compare the complete service

There is substantial overlap in form-building capability. Drupal capabilities may come from Webform, additional modules or local development; do not assume every listed extension is installed or included in support. Govform capabilities depend on the selected plan and configuration.

Govform and LocalGov Drupal / LocalGov Forms: features and operating responsibilities
Area	Govform	LocalGov Drupal / LocalGov Forms
Primary purpose	Build and operate transactional services, including applications, reviews and back-office handoffs.	Council website publishing through LocalGov Drupal, with Webform-based transactions extended by LocalGov Forms and other modules.
Forms and journeys	Multi-page journeys, conditions, validation, calculations, uploads and save-and-return.	Webform offers multi-page forms, conditions, calculations, uploads and drafts. LocalGov Forms adds council-oriented configuration, styling and components.
Reviews and corrections	Configure sequential reviews, approvals and returns for correction, then continue the service after acceptance.	Webform Workflows Element adds states, permission-controlled transitions, notifications and logged changes. Compare the configured approval and correction process.
Integrations	Guided setup for supported connections such as SharePoint, Dataverse, Power Automate and GOV.UK Notify, plus configurable REST requests.	Remote posts, handlers, Drupal APIs and contributed or custom integrations. Agree mapping, failure recovery, support and maintenance for the connections used.
Payments and documents	Supported payment-provider connections and PDF generation within the journey. Confirm the provider and document requirements for your service.	Additional modules and connected providers can supply payments and documents. Check the whole checkout, confirmation, review and evidence process.
Service-performance analytics	Built-in, server-side completion, page drop-off and field validation-failure reporting without analytics cookies.	Submission reporting and exports; Webform Analysis adds charts. Datalayer Webform connects submission events to Google Tag Manager. Other reporting approaches can also be configured.
Permissions	Library roles separate administration, design, deployment and live-data access. Configure access for the people doing each task.	Drupal and Webform provide role-based access controls. Installed permissions and extensions determine who can change forms, see submissions and progress work.
Testing and service changes	Prototype, QA and Production, environment-specific configuration, saved version comparison and restore controls, with deployment permissions and audit records.	Drupal configuration export and deployment workflows. Agree how editor-maintained forms coexist with supplier releases; LocalGov Forms documents this configuration issue.
Hosting and security maintenance	Managed hosting, platform monitoring and backups. Confirm support hours, recovery arrangements and service levels in your agreement.	Council- or supplier-operated hosting, patching, monitoring, backups and recovery. A managed Drupal supplier can provide these services; compare the actual agreement.
Accessibility	Components designed to support WCAG 2.2 AA, with published accessibility statements and testing evidence. Test your configured journey.	LocalGov Drupal's accessibility quality standards reference WCAG 2.2 AA and ATAG 2.0. Test the installed modules, theme, content and complete journey.
Ownership and support	A commercially supported platform. Agree data exports, service migration and support scope when evaluating the contract.	Open-source code, control over hosting and a choice of development supplier. Agree responsibility for the installed solution and its handover.

Use completion, drop-off and validation-failure reports to find difficult questions and assess whether a service change helps. Submission charts and journey-performance reports answer different questions. Drupal options include Webform Analysis and Datalayer Webform; assess their actual reporting coverage. Compare Webform Workflows Element with the approval and correction process you need.

Read Govform's accessibility statements and testing report and LocalGov Drupal's accessibility quality standards. Neither platform automatically guarantees that a completed service is accessible.

Keep LocalGov Drupal. Compare the transactions behind it.

A Drupal service page can link to a Govform journey with agreed branding and return navigation. Further data exchange can use supported integrations and APIs. Agree which system holds each record, how failures are handled and who maintains the connection. Website publishing costs remain part of your existing estate.

Test the build, then test three routine changes

Use a council application with evidence uploads, staff review, a return for correction and a back-office handoff. Include a fee if the service needs one. Build the same outcome in the proposed LocalGov Forms stack and in Govform.

Change an eligibility rule and test the affected routes.
Change an evidence requirement and check the respondent and review journeys.
Change an API field mapping and test successful and failed handoffs.

Record delivery time, staff and specialist hours, release testing, support and remaining manual processing. Include accessibility, permissions, failure recovery and a realistic update cycle. Use these observations to estimate the three-year cost; do not assume that a quicker form build proves lower lifetime cost.

Compare one of your council services

Bring an existing form or service requirement. We'll help you assess the journey, staff processing, integrations and ongoing maintenance against your current approach. Talk to us about a service comparison.

Sources and further comparisons

Official Drupal and LocalGov Drupal sources reviewed 19 October 2026. These describe published capabilities and responsibilities; they do not establish the cost or quality of a particular installation.

For Govform, see the feature directory, analytics, security and hosting, pricing and support. Read the general Drupal Webform comparison, or explore the full platform evaluation guide.