Your first thirty minutes

This is the shortest path from signing up to something useful. It assumes you are the first person in your organization to use StatusLoop and that nobody else is in yet.

1. Create one space (2 minutes)

Resist the urge to model your whole org chart. Pick one department or business area you actually want visibility on, and create a single space for it. You can add the rest once you know the shape works.

It arrives with seven default phases. Leave them for now — you will have better opinions about phases after you have one real project in.

2. Add a program and two or three real projects (8 minutes)

Use real work, not test data. A workspace full of “Test Project 1” teaches you nothing about whether this fits, and you will have to delete it later anyway.

Set an owner on each project. The owner is who gets asked for status, so this is the field that makes everything else work. If the real owner is not in StatusLoop yet, add them as a tracked-only person for now — it takes no seat.

3. Invite the owners (5 minutes)

Only invite the people who will actually submit updates. Leadership can come later; they will be more impressed by a populated portfolio than by an empty one.

4. Open a cycle (3 minutes)

Go to Updates and open one with a period label and a due date two or three days out. Every project with an owner becomes a pending submission.

Do not customise the questions yet. The default set is reasonable, and you will make much better decisions about what to add after you have read one round of real answers.

5. Submit one yourself (2 minutes)

Fill in an update for a project you own. It is the fastest way to understand what you are asking other people to do, and it is where most admins realise their form is longer than it needs to be.

6. Tell people, in one sentence (5 minutes)

The rollout message that works is short and says what they get, not what you get: “Status is moving to StatusLoop. It takes three minutes a week and replaces the reporting email. You will get a reminder the day before it is due.”

What to do after the first cycle closes

• •Look at coverage before you look at the statuses. Low coverage is a process problem; red projects are just information.
• •Read the narratives and notice which fields went unanswered — those are candidates to remove.
• •Only then consider customising the form, adding spaces, or inviting a wider audience.