Start here
Throughline is where you ask for anything to do with technology — and where you watch what happens to your request afterwards.
A broken label printer. Access to a system. A report you need every Monday. A new piece of software for your department. A five-year programme. All of it goes through the same front door, gets the same kind of answer, and stays visible to you from the moment you submit it until the day it is switched off.
You do not need to know which team owns what. You do not need to know whether your request counts as a "ticket" or a "project". That is the platform's job.
Read Submit your first request. It takes about four minutes and assumes you have never seen this before.
What do you need to do?
| I want to… | Go to |
|---|---|
| Ask for something | Submit your first request |
| Find out what is happening with something I asked for | Check what is happening |
| Understand why my request was turned down | If your request is declined |
| Understand a word I saw on screen | Glossary |
| Understand how decisions get made here | The pipeline, step by step |
| Do my job — I triage, approve, or build | Guides by role |
| Ask a person | Ask a question |
Why this exists
Asking for technology help used to mean guessing. Guessing which form, which team, which queue — and then silence.
Silence, not slowness, is the primary driver of frustration and bad faith.
Throughline is built around that sentence. Every request has one visible state, one named owner, and a written record of every decision made about it — including the decisions you will not like. If your request is turned down, you are told why, in words a person wrote, and you can ask for that to be looked at again.
More about why it works this way →
What this documentation assumes
Nothing. It does not assume you know what an intake gate is, why anyone would ask whether your request involves patient data, or what a governance tier does. Each of those has a page, and every unfamiliar word links to the glossary the first time it appears.
This is a proof of concept. Every name, department, and example in this documentation is invented — "Dr. Test Cardigan", "Ward 9-3/4", "the Department of Imaginary Medicine". If a screenshot looks like a real request, it is not one.