Institutional

Digital service transformation with Govforms behind you

For governments, public institutions and regulated organisations that need more than access to software.

Combine the Govforms Digital Service Builder with the support, assurance, delivery and commercial relationship needed for complex or mission-critical services.

The operating model

When the service matters, the operating model matters too.

Some organisations simply need a powerful platform. Others need the platform provider to participate in delivery.

Institutional is for the second group. It creates a contracted relationship around Govforms that can include dedicated support, tailored service levels, assurance, implementation, migration and bespoke technical requirements.

01Central, federal and national government
02Government agencies and regulators
03Regional and local public authorities
04Health and public-service organisations
05Universities and research institutions
06Public corporations
07Justice and regulatory bodies
08Highly regulated organisations
Central Government pricing

Enhanced support for government services

Central government services use an Enhanced tier, with governance and assurance support, additional security hardening, and hosting in a separate government cloud environment.

Enhanced Tier 1

Fewer than 25 pages · Up to 500 transactions/month

£1.21 per transaction
£47.00 support per month

Enhanced Tier 2

Fewer than 50 pages · Up to 1,500 transactions/month

£0.61 per transaction
£358.00 support per month

Enhanced Tier 3

No page or transaction limit

£0.066 per transaction
£1,207.00 support per month

Estimate one live service

Enter its page count and expected monthly transactions. We'll show the lowest-cost tier for which it qualifies.

Estimated monthly cost

Enhanced Tier 1

Support fee£47.00
100 transactions × £1.21£121.00
Total per month£168.00

Prices exclude VAT and are introductory pricing for the first three services. This is an estimate for one live service; bespoke Institutional support, delivery and contract terms are agreed separately.

Discuss Central Government pricing
A deeper partnership

The same powerful Digital Service Builder. A different level of partnership.

Your teams use the same platform for accessible applications, portals, data collections, workflows and transactional services. What changes is the relationship around it.

01

Dedicated support

Named contacts, agreed escalation routes and customer-specific service levels where required.

02

Architecture and integration

Complex integrations, identity architecture and service patterns spanning multiple systems.

03

Security and assurance

Questionnaires, technical workshops, evidence requests and resilience discussions.

04

Delivery and migration

Service design, implementation, service builds, migration programmes and estate conversion.

05

Governance and operations

Regular governance and account-level engagement for broader delivery programmes.

06

Bespoke procurement

Formal procurement, negotiated contracts, tailored packaging and contractual review.

Complete journeys

Build more than forms

Citizen-facing, business-facing and internal services where a basic form-and-email tool is not enough.

01

Applications and registrations

Branching journeys with validation, evidence, saved progress and authentication.

02

Regulatory returns

Structured datasets, calculations, validation and operational-system integration.

03

Case management frontends

Find, view and update records held in another system.

04

Portals and multi-stage services

Homepages, multiple journeys, task lists and saved work.

05

Reviews and approvals

Review, approval, return-for-changes and multi-party authorisation.

06

Eligibility and decisioning

Trusted APIs, rules and server-side results that control the journey.

07

Evidence-heavy services

Secure documents, privacy processing and configurable validation.

08

Operational workflows

Notifications, APIs, assignment, document generation and downstream actions.

Connected architecture

Integrate Govforms into your existing technology estate

Use Govforms as the user-facing service layer while retaining authoritative data and business processes in the platforms you already operate.

Institutional engagements can include solution design for patterns beyond documented standard integration.

PeopleStaffPartners
GovformsService layer
IdentityCase dataEvidence

Lookup and validate

Check information against authoritative data before a user proceeds.

Retrieve and update

Fetch an existing record and send authorised changes back.

Submit to case management

Transform service data for a downstream operational system.

Notify multiple parties

Trigger messages and actions for applicants, staff and systems.

Store evidence where needed

Use Govforms-managed or customer-controlled storage patterns.

Orchestrate journeys

Call systems in sequence and route users using the resulting status.

Identity

Know who the user is, when the service needs to

Build authenticated journeys for known users, staff and organisational accounts. For complex identity models, work directly with Govforms on the architecture.

  • Save and return
  • Multiple concurrent applications
  • Role-based journeys
  • Group access
  • Reviewer access
  • Record management
  • Internal staff services
  • Shared submissions
Secure content

Uploaded content is part of the threat model

Alongside validation and antivirus processing, Content Disarm and Reconstruction creates controlled representations of supported uploads.

  • Rebuild supported Office files without unsupported active components
  • Rasterise PDFs into controlled image-only representations
  • Inspect links in supported Office documents
  • Let users review reconstructed documents
  • Strip image metadata, resize images and blur detected faces where configured
Darcy AI

AI-assisted delivery with human governance

Darcy can create pages, draft accessible content, construct logic and make targeted changes. In institutional environments, it works within Govforms access and change-management mechanisms, with human control and version history.

Controlled delivery

From prototype to production

Separate experimentation from production, then add the assurance and release processes your organisation requires.

1

Prototype

Design services, test journeys and validate ideas.

2

QA

Test integrations, permissions and release candidates.

3

Production

Promote approved versions through controlled release.

Technical design reviewsSecurity evidenceGo-live assuranceOperational readinessResilience discussionsRelease planning
Choosing the right route

Business Estate or Institutional?

The distinction is intentionally simple.

Business Estate

Operate the platform yourself

For organisations with significant capacity needs and the capability to run the platform.

  • Build and maintain your own services
  • Use documented capabilities and standard integrations
  • Work with standard security evidence
  • Use ticket-based product support
  • Purchase against published commercial terms
Explore Business Estate →
Scale deliberately

Support for transformation, not just implementation

Start with a handful of legacy services, establish a reusable architecture and prove the operating model. Then expand across programmes or the wider institution.

Internal teams, systems integrators and delivery partners can build on Govforms while we provide the product, enablement and agreed support.

01Platform governance
02Reusable service patterns
03Integration conventions
04Common identity approaches
05Migration prioritisation
06Delivery standards
07Service templates
08Training and enablement
Commercial model

Arrangements built around the institution

Enhanced tier rates for central government are published above. For bespoke Institutional engagements, we agree platform capacity, delivery and the service relationship with you.

Discuss your requirements
Service estate sizeProduction usageSupport model and SLAsDelivery involvementMigration requirementsIntegration complexityAssurance requirementsIdentity and infrastructureProcurement obligations
Questions

Institutional FAQ

Practical answers about support, delivery and the right commercial route.

Is Institutional only for central government?

No. It is for any institution whose support, assurance, procurement or delivery requirements go beyond Business Cloud and Business Estate, including universities, healthcare organisations and regulators.

Does Institutional include unlimited professional services?

No. Delivery, migration, bespoke development and other professional services are scoped according to the engagement.

Can our internal teams still build services?

Yes. Your teams can continue building and operating services. Govforms involvement can be as focused or extensive as the agreed model requires.

Can our systems integrator use Govforms?

Yes. Govforms can support a delivery model involving your internal teams and delivery partners.

Can you complete our security questionnaire?

Customer-specific assurance activity can be included or separately scoped under an Institutional engagement.

Can we agree a custom SLA?

Yes. Custom service arrangements are a principal reason to choose Institutional.

Can Govforms help migrate an existing estate?

Yes. Planning, service conversion, redesign and large-scale migration can be scoped as part of the engagement.

What if we have hundreds of services but do not need dedicated support?

Choose Business Estate. It provides portfolio economics without an enterprise services relationship you do not need.

Ready when you are

One platform for rapid service delivery. An institutional relationship when the mission requires it.

Give teams and partners a platform they can use repeatedly, with deeper support, assurance and delivery when the work demands it.