Skip to content

Choose who signs off and approves what

Set who countersigns and approves each stage of work, find gaps in the chain, preview who a piece of work would go to and read the history.

Checked against the screens:

Every organisation can choose its own words for the people and roles it works with. When you are signed in, this guide uses your organisation’s words. Otherwise it uses the product’s own.

For admins. This page decides who countersigns write-ups and approves plans. Others are told it is for administrators.

Steps

  1. Open Admin, then authorisation. The page is headed Who signs for what?.
  2. On Tree, pick a stage. Name who handles it for the whole organisation, then for each area.
  3. Add a more specific rule only where it is needed, for one mentor or one young person. The closest rule wins.
  4. Open Gaps. Fix anything it lists, such as an area with nobody named.
  5. Use Who signs for… to search for one person. Or use Preview to choose a mentor and a young person, and see who the work goes to.
  6. Use Stage settings to rename a stage and set after how many days a reminder goes out.
  7. Read History to see who changed a route and when.

If it goes wrong

  • If a page shows this goes to nobody, add an organisation-wide backstop on the tree.
  • If part of the page could not be loaded, reload before you edit anything.
  • If your account is not linked to an organisation, ask a manager to check it.

The tree

The tree answers one question: when a piece of work needs a countersignature or approval, who gets it? Rules can be set for a young person, for a mentor, for an area or for the whole organisation.

The closest rule wins: a child rule, then their area, then the organisation-wide backstop.

Backstop and fall-backs

Each stage should have an organisation backstop. It catches anything the more specific rules do not. Without it, work can resolve to nobody.

People are ranked. The first choice is told, and the next steps in if they cannot act.

Gaps, preview and history

Gaps lists problems, such as an area with nobody named or an approver with no one to back them up. Some entries are for information only and say what happens meanwhile.

Preview asks the same question the system asks. The countersign queue and its three-day reminder are not yet wired to this preview.

History shows route changes, including ended ones, marked rather than removed.

Stage settings

Each stage can have a name your staff use, and a number of days after which countersigners get a daily reminder in the app.

Some stages, such as quality checks on course claims, are chosen organisation-wide because a claim spans areas.

How it links together

This tree decides who sees a write-up in the countersign queue and who is asked to approve a plan. It feeds the tasks and notices those people get.

A profile shows each person who their write-ups go to. See the guides on countersigning write-ups and on your tasks.

How a write-up finds its signerThe closest rule wins, falling back to the organisation.
  1. Write-up sent
  2. Tree consultedChild, then area, then organisation
  3. Signer toldIn their tasks and inbox
  4. Countersigned

Questions people ask

What happens if no one is named?

Work with no route goes to nobody. Add an organisation backstop.

Which rule wins if two apply?

The most specific: a child, then a mentor, then an area, then the organisation.

Can I stop someone signing their own work?

Self-sign-off rules are set per stage on stage settings.

Where can a mentor see who signs their work?

On their own profile, which says where their write-ups go.

Can I see old changes?

Yes, on History. Ended routes stay listed.