SeePEA Rootscope · Clients
Processes and flows
During your Snapshot, SeePEA interviews the people who do the work and the people who own it, and records the answers here. Contributors and admins can review and correct them.
How it's organized
- A process is a piece of back-office work, such as getting a finished job invoiced.
- A flow is one way that process runs. A process with three job types that each follow their own path has three flows.
- People who answered lists everyone interviewed, once each, as someone who does the work, owns it, or both.
The numbers for each flow
Each number is a range, low to high, because real work varies. For example:
| Number | What it means |
|---|---|
| Runs a month | Lowest and highest of the last three months |
| Hands-on minutes per run | All checks and manual steps, without waiting |
| Of those, minutes looking up or retyping | Steps that copy a value between sheets or systems |
| Runs that fail a check | Out of 100, how many go to someone else to resolve |
| Runs that lose money | Out of 100: underbilled, short-paid or written off |
| Days from start to paid | Trigger to sent, plus sent to paid |
Each answer is marked by where it came from: a report, an estimate or a guess. A report counts for more than a guess, so replacing a guess with a number from a report makes your results firmer.
A few more questions ask how the work is done today: how decisions are made, what the inputs look like, and whether the systems can be reached by software.
Saving
Changes are kept on the page until you select Save. Unsaved changes shows while something isn't saved yet.
If someone else saved after you opened the page, your save is refused rather than overwriting their work. Reload, then make your change again.
Viewers can't edit or save. Some answers SeePEA records with your leadership during the Snapshot can only be changed by SeePEA.