Seventeen messages before breakfast
The yard WhatsApp group is busy from 6am. One livery wants her mare left in because the field is waterlogged at the bottom gate. Another asks for a heavier rug on tonight. Someone else wants his horse brought in at four for the saddler. In between are photos of a loose shoe, a question about the arena surface and a debate about whose wheelbarrow is by the muck heap.
The groom on the morning shift scrolls through it while holding three headcollars. She misses the rug request because it was sent the previous evening and has scrolled out of view. That night, the horse is out in the wrong rug and the owner is upset.
Nobody did anything wrong on purpose. The group chat is simply trying to be a job list, and it is not one.
A chat is not a task list
Messaging apps are good for conversation and bad for work that has to be done at a specific time. On a yard, requests are tied to a horse, a day and a time, and they need someone to take responsibility for them.
- Requests are mixed in with chat, photos and general yard news.
- Private messages to one member of staff are invisible to whoever covers their day off.
- There is no way to mark a request as done, so liveries do not know if it happened.
- Requests for tomorrow get lost under today's messages.
- Chargeable requests and free favours look identical.
The more liveries a yard has, the faster the chat moves and the more slips through.
Missed requests hurt the relationship
A missed rug change or a horse turned out when the owner asked for it to stay in feels to a livery like a lack of care. It damages trust in the yard more than its size would suggest, and it tends to be mentioned to other liveries and to people looking for a yard.
For staff, the cost is stress. They are blamed for requests they never saw, they spend time scrolling instead of working, and they take calls and messages on their days off because the information only exists on their phone. It also means chargeable requests go unbilled, because nobody records them in a way that reaches the invoice.
One request board for the whole yard
We build a request board that works on any phone and on a screen in the tack room.
- Liveries open a simple page, pick their horse, the request type and the day and time it is needed. Free text is there for anything unusual.
- Requests are grouped into the shift they belong to: morning feeds, turnout, lunchtime, bring in, evening checks.
- Staff on duty see their shift list with each request against the right horse, in stable order if that suits your yard.
- When a job is done, staff tick it off, with an optional note or photo. The livery gets a short confirmation.
- If a request cannot be done, for example the field is closed, staff mark it and the livery is told, rather than finding out at the gate.
- Chargeable requests are priced from your list and carried through to the monthly invoice.
| Group chat | Request board | |
|---|---|---|
| Where requests live | Mixed with chat and photos | One list per shift |
| Staff day off | Requests on their phone | Visible to whoever covers |
| Confirmation | None, or a thumbs up | Marked done with time and name |
| Charging | Often forgotten | Priced and added to invoice |
| Looking back | Scroll and search | Filter by horse, date or livery |
The WhatsApp group can carry on for yard news and chat. It just stops being the place where work is supposed to be found.
Shifts that start with a clear list
The groom starting at six opens the morning list and sees exactly what has been asked for: which horses stay in, which need rugs changed, who is being collected by the farrier at ten. Nothing depends on how far she scrolls. Whoever covers the weekend sees the same list.
Liveries stop asking "did you get my message?", because they can see the request was done. Yard owners stop being the switchboard between liveries and staff, which is often the biggest change of all.
Is the group chat running your yard?
- Requests arrive in a WhatsApp group mixed with everything else.
- Staff have missed requests they never saw.
- Liveries message staff directly on their days off.
- Nobody can easily say whether a request was done.
- Chargeable requests are often not billed.