Back to Saath

What is real here

Saath is an independent prototype built for a hackathon. It is not a government service and is not connected to one.

Rather than hide the parts that stand in for something real, they are labelled where they appear and listed here. 6 parts of this work as they look. 7 are standing in. 2 are named but not built.

This works

Built, running, and doing what it looks like it is doing.

  • The conversation

    A live model reads the case, decides what to ask, and writes every reply.

  • The checks on what gets recorded

    Dates, names, identifiers and contacts are all checked before they reach a form, and again before anything is submitted.

  • Document checks

    File type, size and legibility are checked when you attach something.

  • The letters and emails

    Written for your case, by the same model, and never sent without you pressing send.

  • Speaking instead of typing

    Your voice is transcribed by a live speech model.

  • The case moving between screens

    Cases are held on a server and pushed live, so a submission shows up on another device straight away.

This is standing in

Here so the rest of the journey can be shown end to end.

  • Contact addresses on letters

    Addresses are filled in from a small built-in list and use example domains.

    A deployed version would use each organisation's published contact details.

  • Sending a letter

    Pressing send records the letter on your case. No email leaves this prototype.

    A deployed version would send it and track the reply.

  • Replies from organisations

    A reply arrives on a timer so the rest of the journey can be shown.

    A deployed version would wait for the real one.

  • Decisions from the office

    A reviewer accepts or returns the case in a separate demonstration screen.

    A deployed version would connect to the office that actually decides.

  • Case reference numbers

    Generated here, so your case has something to be called.

    A deployed version would carry the reference the office issues.

  • Reading a bank statement

    The findings shown are a fixed set prepared for this demonstration. Saath does not read what is inside your file.

    A deployed version would read the statement you attach and find what is actually on it.

  • Searching for what they left

    Saath names the places that hold unclaimed money and explains how to reach them. It does not search any of them.

    Most of these have no route for software to search on a family's behalf. This may always be a matter of telling you where to look.

This is not built

Named where it applies, and deliberately left alone.

  • The processes we only map

    Named on your journey with who holds them, so you know they are coming. Saath does not carry them.

  • Anything that goes to a court

    Named where it applies, and deliberately left alone. No software should suggest it can settle these.

Saath does not use government logos or claim any approval or partnership. No real identity, payment or health data is used anywhere in it.