'I don't want to go back tonight'
A student comes to reception at lunchtime and says she is unhappy with her host. The food is not what was promised, the room is cold, and she feels unwelcome. The accommodation officer listens, writes a note and promises to call the host. On Thursday, the host rings to complain the student comes home late and does not tell them. The agent emails on Friday, having heard the student's version.
The student is moved the following week. The new host is found in a hurry. Nobody writes down what happened with the first host, and three months later another student is placed there and raises the same issues.
Why homestay issues go round in circles
- Concerns arrive through reception, teachers, agents, hosts and the students themselves.
- Many are raised in conversation and never written down.
- Follow-up depends on the accommodation officer's memory and their day.
- When a student moves, the placement, payments and host calendar all change.
- Outcomes are not recorded against the host, so the next match knows nothing.
- Some concerns are welfare matters that your policy says must go to a named person.
What that costs
A student unhappy at home is unhappy in class, and they tell their agent and their friends. Rushed moves lead to weaker second matches. Hosts feel judged without being heard, and good hosts leave. Where a concern is a welfare matter, not recording it properly and passing it to the right person is a serious gap under your own safeguarding policy.
The issue log and move process we build
- Anyone on staff can log a homestay concern in a few taps: student, host, who raised it, what was said. Students and hosts can also report through a simple form.
- Each concern is given a type, such as food, room, rules, communication or welfare, and anything marked as welfare goes straight to the person your policy names, with the usual log restricted to what others need.
- The concern is assigned to someone with a follow-up date, and both sides of the story can be recorded.
- If a move is agreed, the move screen lists suitable hosts using the same matching rules as new placements, and the officer chooses one.
- Confirming the move ends the first placement on the right date, starts the new one, splits host payments correctly and updates both host calendars.
- The agent is informed in the words you choose, and the outcome is recorded against both host and student.
- Hosts with repeated concerns of the same type show a pattern, which the accommodation officer can review at their next home visit.
| Type of concern | Default route |
|---|---|
| Food or room | Accommodation officer, host contacted |
| House rules or curfew | Officer with both sides recorded |
| Travel to school | Officer, may lead to a move |
| Welfare concern | Person named in your policy, restricted record |
| Host complaint about student | Officer and, if needed, director of studies |
How concerns are handled, and who must be told, is set by your policies. We build the routes you specify.
Homestay issues handled once
Concerns are logged when they are raised, not remembered later. Follow-ups happen because someone is assigned and reminded. Moves are made carefully, with the placement and payment changes done automatically. The next time a student is matched with that host, the officer can see the history and decide with full knowledge.
Hosts also benefit: they see that a complaint about them was heard alongside their own account, and they get specific feedback at their next visit rather than a vague sense that something went wrong.
Is this how homestay issues run?
- Complaints are raised at reception and not written down.
- Students are moved host in a hurry.
- Host payments are wrong after a move.
- The same problems recur with the same host.
- Agents hear about problems before you have a record of them.