Public Sector · Applications

Applications and portals for public services.

An applicant submits, tracks the status and receives the document - without calls or queues.

Tell us about the project All projects

When public bodies bring us in

you're preparing a tender and need a supplier
the project needs several disciplines at once
an existing system needs extending or connecting
a procedure needs digitalising from application to decision
long-term support after handover is required

What this means for the contracting authority

Traceability for every step of the procedure.
Documentation that matches the tender requirements.
One accountable partner even with several vendors.
Acceptance testing against pre-agreed criteria.
Support and development after handover.

Problem → solution

Applications arrive by email.→ a portal with validation and statuses The archive is too large to search manually.→ AI search with cited sources Several vendors work on the same project.→ project management and coordination

Features

validated online submission
login and identification
statuses and notifications
documents and decisions
payments
accessibility standards
multi-language

The portal is also used by people who do not know how

An applicant is not a regular user. They open the portal once a year or once in a lifetime, often on a phone and often in a hurry. So the path to submission must be short, and any error understandable without phoning the office.

a form that can be completed across several sittings
an error that says which field is missing and why
data already known is pre-filled
a submission receipt straight away
status tracking without phoning
working the same on a phone as on a computer

Accessibility is not optional

For public-sector websites and mobile applications, accessibility is not a recommendation but a requirement that tenders often state explicitly. In practice that means the site must be usable with a keyboard and a screen reader, not merely look tidy.

full operation without a mouse
field labels a screen reader reads correctly
sufficient text contrast
text that enlarges without breaking the layout
descriptions for images and documents
an accessibility statement listing known gaps

Accessibility is cheapest to build in during development. Fixing it afterwards means rework, not a patch.

When clients come to us

people queue at the counter for things that could run online
applications arrive by email and are retyped by hand
the existing portal does not work on a phone
accessibility does not meet the requirements
applicants call because they cannot see the status

What you receive

a portal for submitting and tracking applications
a back office for processing them
integration with existing systems where possible
an accessibility statement
documentation and training

How we run a public project

Requirements

Tender and technical requirements are translated into a delivery plan with milestones and responsibilities.

Project management

One contact, regular progress reporting and subcontractor coordination in one place.

Quality and security

Test scenarios, a security review and compliance with the client's requirements before acceptance.

Documentation

Technical and user documentation, instructions and training material.

Acceptance and SLA

Acceptance testing, handover and support with agreed response times.

FAQ

Must the portal be accessible to users with disabilities?

For the public sector accessibility is a requirement and tenders often state it explicitly. We build it in during development rather than adding it later.

Sounds like your project?

Send us the project description, your existing system, the tender documents or the event date.

Tell us about the project

Applications and portals for public services.

When public bodies bring us in#

What this means for the contracting authority#

Problem → solution#

Features#

The portal is also used by people who do not know how#

Accessibility is not optional#

When clients come to us#

What you receive#

How we run a public project#