PROFESSIONAL SERVICES · SYSTEM

Your trainees are being paid to retype photographs of receipts

IN SHORT

Document intake is the least valuable work in a professional firm and it is done by the people you are trying to train into something better. Reading, filing and extracting automatically returns those hours and starts jobs weeks earlier.

What actually goes wrong

Clients send what is convenient for them: a photograph taken at an angle, a forwarded chain with the attachment three replies down, a bag of paper. Someone junior reads, sorts, names, files and retypes all of it. It is slow, it is error-prone at the exact point errors are most expensive, and it happens before any chargeable work can start.

What it costs

Directly, a large share of junior capacity — the easiest saving in the sector to calculate. Indirectly, retention: nobody qualified into this profession to name PDFs, and the firms losing trainees are usually the ones where the first two years look like data entry.

How the fix works

Everything arriving by email, portal or upload is read. The system identifies the document type, the client and the matter, extracts the fields that matter, files it under your own naming convention and pushes the data into your practice or bookkeeping system. Poor-quality images, duplicates and anything it cannot confidently place are separated and chased with the client directly, describing exactly what is wrong rather than asking for everything again.

What stays with your people

Anything below the confidence threshold, and every professional judgement about what the records mean. The system is a reader and a filer, not a reviewer.

What you get

  • Photographs, PDFs, scans and forwarded chains all read
  • Document type, client and matter identified automatically
  • Extracted data pushed into your practice or bookkeeping system
  • Filed under your own naming and folder conventions
  • Illegible, duplicate and missing items chased with the client directly

Questions we get asked

How accurate is the extraction?
Good on structured documents, and designed around not needing to be perfect. Every extraction carries a confidence level and anything below your threshold goes to a person with the document open beside the fields. The saving comes from the confident majority.
Can it handle a whole year of records at once?
Yes, and bulk intake is where it looks most impressive — a bag of paper scanned once becomes a filed, extracted, queryable set of records in an afternoon.
Do clients have to change how they send things?
No. That is the point. A client who insists on emailing photographs is handled exactly as well as one who uses a portal.

TRUST & CREDENTIALS

How we work, and what stands behind it

This page is maintained by Forth Systems. Everything listed below describes our own team, hosting choices and the technologies we build on — it is a statement of practice, not an independent certification or an endorsement by the vendors named.

UK team & data residency

Who builds it, and where your data sits while they do.

  • UK-based engineers

    Edinburgh-headquartered. Every system is designed, built and supported by our own UK-based engineering team — no offshore delivery pool.

  • UK / EU hosting by default

    Applications and databases are provisioned in UK or EU regions unless you require otherwise, with encryption in transit and at rest.

  • Human-in-the-loop by design

    Every AI system we ship keeps a manual override. Nothing irreversible happens without an operator able to review, edit or stop it.

  • Audit trails as standard

    Automated actions are written as first-class records — who or what did it, when, against which input — so operations stay evidence-ready.

Systems we build on

The platforms our systems run on. These are the technologies we deploy and support — not sponsorships or reseller badges.

  • OpenAI, Anthropic & Google models

    Model-agnostic delivery. We route each workload to the model that fits it on cost, latency and accuracy, and can switch without a rebuild.

  • Supabase & Postgres

    Row-level-security Postgres as the operational spine under every platform we run.

  • Stripe payments

    Payment capture, checkout and reconciliation wired directly into job and permit workflows.

  • Xero, Sage & HubSpot integrations

    Production integrations into the finance and CRM systems UK operators already run, so automation lands where the business keeps its records.

Streetworks & industry credentials

Operational domains we build in daily, with the sector systems we integrate against.

  • DfT Street Manager integration

    The permit chain we built for Kerbco creates and tracks streetworks permit applications against DfT Street Manager and local highway authority processes.

  • NRSWA-aligned workflows

    Permit, reinstatement and traffic-management workflows built to the New Roads and Street Works Act process contractors are inspected against.

  • Traffic management planning

    Roadplan produces signing and guarding layouts for council submission and for the crew installing them on site.

  • Operator-built, not consultancy-built

    Our platforms are built around real operating workflows — including the permit chain we built for our client Kerbco, a Scottish drop kerb contractor.

Insurance certificates, registration numbers and security documentation are available on request — ask the team.