Skip to main content
VectisFlow
VectisFlow
All industries

Sector

Central government

Casework and correspondence above, case, grant and payment records below, where the obligation is not to find material but to assemble a defensible position.

Classical stone columns of a government building rising against an overcast sky

Where it sits

The corpora that matter here.

  • Casework correspondence

    Submissions, responses and internal assessments, usually spread across successive case management systems and a shared drive older than both.

  • Consultation responses

    Thousands of free-text submissions per consultation, analysed under a deadline by a small team, where the outlying response is often the one that matters.

  • Policy and guidance archives

    Superseded guidance sits alongside current, and the question is usually which version applied on a specific date.

  • FOI and disclosure material

    Requires exhaustive recall with a documented method, and the ability to show what was excluded and why.

Challenges

What actually goes wrong.

Not the sector's problems in general, the specific failure modes that decide whether a system in this sector survives contact with production.

  • Explainability to auditors

    A relevance score that cannot be explained is not usable. Lineage from surfaced passage to pipeline and model version is the price of approval.

  • Recall asymmetry

    The cost of missing a relevant document vastly exceeds the cost of reviewing an irrelevant one. Retrieval is tuned for recall and the review interface absorbs the precision cost.

  • Vocabulary mismatch

    Correspondents do not use departmental terminology. Keyword-and-taxonomy approaches miss exactly the submissions most worth finding.

  • Thread reconstruction

    A single message is often meaningless without the exchange around it, and the exchange frequently spans two systems.

  • Counting a case two ways

    Two systems disagree about when a case opened and when it closed. The published caseload depends on which definition survives into the mart, so the definition needs an owner rather than a convention.

  • Statistics restated after publication

    A figure released last quarter has to be reproducible this quarter, from the same code against the same snapshot. Without versioned inputs, a routine correction becomes an incident with a press line attached.

Constraints

What shapes the architecture before a line is written.

  • Data residency and egress

    Material cannot leave the boundary. Inference runs through a private endpoint or a self-hosted model, and that is assumed from the first design session.

  • Assurance and audit

    Method, measured error rates and known failure modes have to be written for an internal auditor, not for engineers.

  • Procurement and accreditation

    Security assurance, DPIA and supplier accreditation shape the timeline as much as the engineering does. We plan for it rather than discovering it.

Engagement

How this looks in practice.

Repeating stone facade of a government building, shot from below against overcast sky

Central government

Assembling regulatory evidence from casework correspondence in central government

An extraction and evidence-assembly pipeline over eleven years of casework correspondence, built to a standard where every extracted fact traces to a source passage and a pipeline version.

UK central government agency, ~2,000 staff · 20 weeks

Read the engagement

Services that apply here

Start here

Talk to us about central government.

Describe the estate and the decision it should be supporting. We will tell you which parts are tractable now, which need remediation first, and which we would advise against.

Response time
One working day, from a person who has read it.