Skip to content

Check service health and watch work come through

See whether anyone is blocked, whether notes are reaching their plans, and read the live feed of saves and what is wrong with them.

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. Both pages are read-only. The monitor refreshes itself every twenty seconds.

Steps

  1. Open Admin, then Service health. Read Right now first.
  2. Look at the counts for people blocked, and for notes that missed their plan.
  3. Read Last 7 days for write-ups not done and notes written.
  4. Open Health snapshot and Signed in today to see who has used the service.
  5. For the record-by-record view, open the monitor. Read Needs attention first.
  6. Check Failed to save, Possible duplicates and Incomplete records. Open the linked record to fix it.
  7. Scroll to the Transaction log to see what went through.

If it goes wrong

  • If the page says part could not be read, the feed is incomplete. Refresh.
  • If a duplicate looks real, judge it yourself. Nothing is merged automatically.
  • If the transaction log says it is not switched on, ask the platform team.

Service health

Service health answers how the service is doing this morning, in counts. It shows who is blocked from submitting a note, notes that missed their plan, and sessions not written up.

It also shows a fortnight's timeline and who has signed in today. Sign-in history is not kept beyond the latest, so someone working today may not appear.

The monitor

The monitor shows every write that went through in the window, newest first, with what is wrong with any of it. A count of three tells you nothing about which three. This does.

  • Failed saves, with the error.
  • Possible duplicates, for a person to judge.
  • Incomplete records, such as no outcome or no place.
  • Planned work at a venue that needs a room, with none booked.
  • Contact details that need correcting.

Possible duplicates

Two mentors writing up one shared session is ordinary work. The monitor flags overlaps for a human to judge and never merges them.

Scope

You see your organisation and the children you can see, by the same rules as every other page. Only successful writes appear in the log, since a refused save changes nothing.

How it links together

Both pages read the same records as the planner, write-ups and bookings. Fixing a record in its own page clears it here. The activity page and the audit log give other views.

See the guides on what happened across the service and on the audit log.

Finding and fixing a problemStart with the counts, go to the row, fix it where it lives.
  1. CountsService health
  2. The rowNeeds attention
  3. Fixed in placeOn the record itself
  4. Gone from the list

Questions people ask

Why does the monitor show a duplicate?

Two write-ups overlap. It may be a genuine copy or a shared session. You decide.

Can I fix things from the monitor?

It links to the record. Fix it there.

Why is someone missing from signed in today?

Only the latest sign-in is kept, so a long sign-in may not show.

How often does it refresh?

The monitor every twenty seconds.

Who can see these pages?

Admins.