Everything included: £4.25 per pupil/year before volume discounts of 5% to 20%, £250 minimum/year, excluding VAT. See pricing

Core / Unresolved Absences

Unresolved Absences: check the reason before changing a mark

Student Radar gives attendance staff a queue of unexplained marks to investigate, with routes to historical marks, replacement codes and the recorded save outcome.

Request a demo Watch a product example

Choose a replacement only when the reason is known. Check the register-source notice and final outcome; a local-only save does not update the MIS.

Fictional school example; read the selected scope, dates and any coverage or availability notices.

Unresolved Absences

Resolve unexplained marks with a confirmed reason.

Find unexplained attendance sessions, confirm the context and record the appropriate replacement code.

01
Find the session that needs attention
Today and Historical separate immediate follow-up from earlier unresolved marks. Search pupils and filter year, form, session and dates. Counts distinguish outstanding marks from different pupils, so two unresolved sessions for one child do not become two children.
02
Keep the original context in view
Review absence shows the pupil, date, AM/PM or period context, current mark and recorded comment. Search the school’s active replacement codes and choose one only when the reason is known. If it remains unknown, cancel and continue the enquiry.
03
Know where the change will land
The save control identifies whether Student Radar keeps the register or a change is local only. Configured MIS writeback has its own connection/review status. After saving, check the refreshed queue and the register outcome; a queued request or an empty filtered list does not prove the MIS was updated.

Inspect

Review the original mark before replacing it

Pupil, date, session and recorded comment stay together in Review absence. Staff confirm the reason rather than treating queue clearance as the goal.

Pupil, date, session and recorded comment stay together in Review absence. Staff confirm the reason rather than treating queue clearance as the goal. Fictional school example.

Act deliberately

Choose a known reason and a clear destination

The active replacement-code picker helps staff find the appropriate recorded reason. The save control states whether the change updates the Student Radar register or is local only.

The active replacement-code picker helps staff find the appropriate recorded reason. The save control states whether the change updates the Student Radar register or is local only. Fictional school example.

Review

Check the queue after the change

The fictional reconciled mark leaves the refreshed queue. A local queue result is separate from confirmation that an external MIS was updated.

The fictional reconciled mark leaves the refreshed queue. A local queue result is separate from confirmation that an external MIS was updated. Fictional school example.

A clearer school review

Keep the working record useful to the people making the next decision.

Match the confirmed reason to the correct session

Avoid confusing local saves with MIS updates

Check the refreshed queue before another attempt

Questions about Unresolved Absences

Does the queue total count individual pupils?

The queue concerns unexplained marks. A pupil can have several marks, so the marks count is not a count of different children.

Can a correction update the school MIS?

Some schools have configured MIS writeback. Check which system holds the register and follow the displayed outcome; a local save is not automatic proof of a completed MIS update.

Related help guides

See how to carry out these tasks in Student Radar, with step-by-step product help for the people using them.

Review unresolved absences and confirm corrected marks For Attendance staff, pastoral leaders and school leaders with the relevant access

The value of a connected school

See the pattern. Bring the context.

A change in attendance or behaviour is the start of a conversation. The connected pupil record helps staff ask a better next question.

SENDPlans, provision & reviews
HealthMedical needs & care plans
Family communicationContact history & next actions

Core

Context for the next step

Student Radar

Follow a connection to see what it makes possible

Relevant context, with access set by each staff member’s role and responsibilities. Staff decide the response.

SEND + Core
Check whether support is reaching the pupil
Put attendance and behaviour alongside plans, provision and review evidence. Staff can investigate missed support before deciding what needs to change.
Explore SEND
Health + Core
Bring health needs into the attendance conversation
Authorised staff can check relevant medical needs and care plans when following up absence, then agree practical support with the family.
Explore health
Family communication + Core
Keep the family conversation with the follow-up
Read the contact history around a pupil before reaching out. Record the next action so another colleague can pick up the conversation with context.
Explore family communication

Ask to see Unresolved Absences in the Demo School