The note that nobody read
A night officer notices that a first-year has not been seen leaving their room for several days, and their flatmates are worried. They write it in the night log. The morning shift is dealing with a leak and a lockout and does not read that page. Two days later a flatmate emails the general inbox, which is checked by someone in the lettings team.
Nobody did anything wrong on purpose. The information simply had no single place to go and nobody to own it.
Why concerns fall between shifts
Residence teams work around the clock, often with a mix of in-house staff, security contractors and residence life assistants. Each group has its own way of recording things. Welfare concerns are sensitive, so people are rightly careful where they write them, and that caution pushes them into personal notes and private messages.
- Concerns are written in general logs that also hold repairs and noise complaints.
- There is no clear owner for each concern.
- Follow-up relies on someone remembering to check back.
- Escalation routes, for example to a university wellbeing service, are known by some staff and not others.
- Sensitive notes end up in shared inboxes where too many people can read them.
What the gaps cost
The real cost is the one nobody wants to write down: a student who needed someone to check on them and did not get it quickly. Beyond that, there is the strain on staff who worry that they missed something, and the difficulty of showing a university partner or a family that concerns were taken seriously when the record is spread across notebooks.
The concern log we build
- Staff raise a concern from a phone or desktop in a short form: resident, what was noticed, when, and how urgent it feels. The resident is picked from your booking system so details are correct.
- Each concern gets an owner, based on the rota and rules you set, and appears on their list and on the shift handover.
- Follow-up prompts are set by the type of concern and your policy, so the owner is reminded to check in and record what happened.
- Escalation contacts are held in the system, for example the residence life lead, the university's wellbeing service where you have an arrangement, or emergency services guidance. Staff see who to contact for each situation.
- Access is limited by role. Night security can raise and see their own concerns, residence life sees the full record, and general staff do not.
- Every action is time-stamped, so the history of a concern can be reviewed later by the people allowed to see it.
| Question | Today | With the concern log |
|---|---|---|
| Where is the concern written? | Night log, email, notebook | One record per concern |
| Who owns it? | Unclear | Named owner |
| Has anyone followed up? | Ask around | Follow-up recorded with time |
| Who should be told? | Depends who is on shift | Escalation contacts shown |
| Who can read it? | Anyone with the log | Role-based access |
What counts as a concern, when to escalate and who to share information with are decisions for your own safeguarding policy and advisers. We build the log around them and do not give welfare advice.
What your team gets from it
Every concern has a home and an owner. Shift handovers include open concerns automatically. Staff know where to write things down and who will see them. Managers can review open concerns in one place and see where follow-up is overdue, rather than discovering it later.
Is this how concerns are handled now?
- Welfare notes are mixed in with repairs and noise in the night log.
- Concerns raised on one shift are not always picked up by the next.
- Staff are unsure who to escalate to.
- Sensitive information sits in shared inboxes.
- You would struggle to show the history of a concern if asked.