Help & Documentation

What StatusLoop is for

The problem it solves, who it suits, and where it deliberately stops.

Your first thirty minutes

From an empty workspace to a cycle collecting real status.

How work is organised

Spaces, programs and projects — what each level is for, and how to decide where something belongs.

Update cycles

The core loop: how StatusLoop collects status from owners and turns it into one portfolio view.

Projects, phases, tasks and milestones

How delivery detail is structured inside a project, and how much of it is worth maintaining.

People, members and tracked-only

Who can own work, who needs a login, and why those are different questions.

Dependencies

Linking work that waits on other work, and what the at-risk flag actually means.

OKRs and revenue

Connecting delivery to the outcomes it is supposed to produce.

Spaces and phase templates

Creating spaces, and shaping the phases every new project in them starts with.

Inviting people and choosing roles

Who gets a login, who just gets tracked, and what each role can do.

Customising the intake form

Adding your own fields to how new work gets requested.

Customising update cycles

Changing the questions owners answer — for every cycle, or just one.

Branding

Your logo, colours and RAG palette — and what is and is not configurable.

API tokens

Pushing status updates in from your own tooling, and handling tokens safely.

Submitting a status update

What you are being asked for during a cycle, and how to answer it in a few minutes.

Owning tasks and keeping a plan current

Statuses, dates, progress notes and dependencies — the day-to-day of a project plan.

Raising an intake request

Asking for new work to be picked up, and what happens to the request afterwards.

Exports

Getting data out — as a deck, a plan, a spreadsheet, or everything at once.

Your data

Where it lives, who can see it, how to get it out, and what happens when you leave.