For multi-site operations
Every site submits. Head office sees the lot
Running the same process across thirty locations is not thirty small problems. It is one problem: the sites need to submit work without seeing each other's, and head office needs one view of all of it without chasing thirty inboxes.
Sites see only their own
Enforced in lists, search, counts, analytics and direct links, not just hidden in the interface.
Stages per audience
Editable, read-only or invisible, chosen stage by stage.
One record across processes
Opening, fit-out and decommissioning stay linked as one site with one history.
Where everything is stuck
Targets per stage, a weekly summary, and analytics across every site at once.
One login per site, and it only sees its own
Give each store, branch or site its own login. Turn on 'members see only their own records' for the stream and that login sees only the jobs it created. Not a filtered view it could undo, and not a convention: the lists, the search, the dashboard counts and the analytics are all scoped to match, and a direct link to another site's job does not open.
Head office and admins see everything, all sites at once, without switching accounts.
Submit, then hand over
The common shape is that a site raises the job and head office runs it from there. Each stage can be set so the site can work on it, can see it but not change it, or cannot see it at all.
So the submission stage stays theirs. The middle stages become read-only, which means the site can follow progress without being able to alter anything. And any stage holding costs, supplier rates or internal notes is hidden outright: the site never sees the stage name, let alone what is in it.
If the last stage is 'confirm the work is done', hand it back to them. They regain control exactly when it is their turn again.
A site's whole life, not one project
A location is not one job. It is opened, fitted out, maintained for years and eventually closed, and those are different processes with different stages.
When a site finishes one process and enters another, copy it across and the two stay linked. The earlier record is kept as history, and one view follows the whole chain and shows it as a single record: every process it passed through, the field values from all of them merged together, and one activity history across the lot.
That is how you answer 'what has actually happened at this site' two years later, when the person who opened it has left.
Knowing where everything is stuck
Set a target number of days per stage. Anything over is flagged on the record, lands in the weekly summary to owners and admins, and emails whoever owns it the morning after it goes over.
The analytics view shows records by stage across every site, the average time sitting at each one, and the jobs stuck longest. It is exact and instant, with no report to build. If you would rather just ask, you can ask in plain English and get an answer drawn only from your own records.
See it happen
Every business has a process and most of them live in someone's head. Two minutes on what Streams actually is: your steps, written down once, with every job moving down them one at a time.
A starting point: the Project Schedule template
Plan projects with milestone dates that automatically plot as cards on the Timeline view. 5 stages and 9 fields, with written instructions on every stage. Change any of it, because it is your process.
Questions
- Can one site see another site's jobs?
- No, when 'members see only their own records' is on for that stream. It applies to the stream page, the records list, search, the dashboard counts, analytics, the timeline and direct links. A site opening a link to another site's job is not shown it.
- Can a site follow progress without being able to change anything?
- Yes. Set the middle stages to 'members can view but not change'. They can open the job and read what head office has entered, but cannot edit it or move it on.
- Can I hide cost information from sites completely?
- Yes. A stage set to 'members cannot see this step' disappears from their view entirely. The stage name is never shown and its field values are never rendered. While a job sits there, the site is told it is at a stage handled by administrators.
- How many sites can this handle?
- Users and records are what scale, and both are set by the plan. Standard covers 20 users and 10,000 records, Pro covers 50 users and 100,000 records. Streams themselves are unlimited on every plan, including free.
Other trades doing the same thing
Start with the free plan
Two users, 500 records and every feature switched on. No credit card, and your data stays in Australia.
Get started free