Safe to Say: Is it defensible?
The handover sticks to what’s in the carrier’s authority. It explains what can safely be said and stops short of personal advice.
Safe to Say, Safe to Reach, Safe to Use · Handovers
A referral isn’t the same as a handover. And a disclaimer doesn’t count as a plan.
From Safe to Say, Safe to Reach, Safe to Use · Draft v0.1 · 1 October 2026
In this framework, a referral just points to a possible service. A real handover goes further: it gives the person a way to actually reach help, spells out what that help can offer, and shows them how to pick up the pieces if things don’t work out.
Why handovers fall flat
Why do handovers fall flat?
Teams often finish their bit and leave the person to figure out the rest. Maybe they hand over a phone number that’s impossible to call, or recommend a service that’s already stretched too thin, or give instructions that demand paperwork no one can easily get. Even when professionals tell the truth, like “I can’t give individual advice”, the person’s still left wondering which facts matter and what to do next, especially if the first referral fails.
That’s why the framework looks at the whole pathway expertise has to travel:
Source→carrier→person→judgement→action→help, review or recovery
We’re not saying every carrier has to fix every problem. But we do insist that boundaries, dependencies and handovers shouldn’t be invisible.
A real handover
What makes a handover “real”?
There are four things:
- 1A named service. Saying “a lawyer” or “a professional” isn’t enough.
- 2A route. Give a phone number, website, counter, form, webchat, or a way to book an appointment.
- 3Access conditions. Stuff like hours, fees, documents, eligibility, language options and accessibility.
- 4A backup. If the usual route fails, what’s the alternative?
In plain language, a proper handover answers: “Who can help me?” It gives you a name, a way to get there, details on hours and eligibility, and tells you what to say. It also answers: “What if this doesn’t work?” with options for review, correction, complaint, appeal, escalation, independent help, fallback and recovery.
Every carrier
What should every carrier do?
This isn’t about giving personalised legal advice or fixing everything. But carriers must:
- Explain clearly what they can safely explain.
- Show the boundary of their authority or competence.
- Make sure the next source of help is visible and practical.
- Not imply that an unavailable, unsuitable or unauthorised pathway is a real solution.
- Offer a route for review, escalation, correction or recovery where one exists.
Authority and usability go hand in hand. Don’t overstep your role, but don’t hide behind disclaimers instead of showing a useful pathway.
Principle 6: Make boundaries actually useful
A professional or technical boundary shouldn’t leave people stuck. Sometimes you have to say, “We can’t advise you personally,” or “This tool can’t check your eligibility,” or “This isn’t medical advice.” But always add, where possible, what the resource can do, what extra help is needed, how to find it, and what to do if the first option fizzles.
Ask yourself: Does the boundary stop people relying on this resource more than it can support, but still leave them with a real way forward?
Questions to ask at every handover
Has the work really been passed on, or not?
A referral points to another service. A handover is about passing info, authority and responsibility to the right person or team, and giving them a chance to ask questions and actually accept the job.
This idea comes from clinical safety practice. We adapt it carefully: clinical handover processes and their evidence don’t automatically carry over to legal, regulatory or public-service settings. But the key questions are:
- What info needs to travel to the next carrier?
- What’s still uncertain?
- Who’s authorised to take over?
- Can the next service actually accept the person?
- Does the person know what’ll happen?
- What’s the fallback if the transfer stalls?
The action boundary
Where does the handover actually go?
You can support at two levels:
General pathway level
What’s available for people in a similar spot: processes, deadlines, services, required documents, questions to ask, and how to get help.
Personal advice level
Which option is best for this individual, based on an assessment of their evidence, with a prediction of their outcome or a recommendation.
If you’re only allowed to give general info, build out that path fully, then stop before you start steering someone’s personal decisions. The stop isn’t a gap in your resource. It’s where the handover goes.
Help people carry out their own choices
Sometimes, even when someone intends to act, life gets in the way. Help them follow through by checking:
- When will they take the next step?
- Where will they do it?
- What do they need to have ready?
- What’s the first likely roadblock?
- What’s the backup plan?
This isn’t about directing their decision. It’s about supporting them in the choice they’ve already made, if your resource allows it.
When the route fails
When the route fails
Just putting a referral down doesn’t mean the pathway works. It only works if someone can actually use it, or if the missing pathway is marked, owned and escalated as a system problem.
Take Maya’s story (fictional): she gets a family violence safety notice but can’t call from home safely. She tries the court’s online form on a borrowed device, but it needs an email address she can’t safely use. There’s no other verified option. The pathway fails.
The framework doesn’t paper over this with “Use another safe route.” Instead, here’s what happens:
| Finding | Status | Required response |
|---|---|---|
| Maya can’t use the phone safely | Pathway failure | Court or service owner must offer or verify another safe contact method |
| Maya can’t use the online form | Pathway failure | Digital and court owners must look at another submission or contact route |
| No alternative is named | Unresolved risk | Don’t call the pathway complete; record the owner, escalate, and set a review date |
| Specialist service may help plan | Partial support | Check if they can help Maya connect safely to the court |
Honestly, it’s not a happy ending for Maya, on purpose. The framework surfaces a system failure instead of pretending the pathway works or making it Maya’s personal problem.
Spot when the problem isn’t about expertise
Don’t chalk up someone’s inability to act as a lack of understanding if the real issue is safety, money, time, disability, trauma, privacy, missing documents, lack of authority, digital exclusion, language barriers, geographic isolation, low service capacity, unfair requirements, or simply no real option.
Those are system findings.
Where handovers fit in
Safe to Reach: Will it land?
The person knows why they’re being sent on. The next service is actually reachable, on time and safely.
Safe to Use: Can the person act on it?
Real info: a named service, a way to reach them, access conditions, and a backup in case things don’t work.
Chami Rupasinghe · Admitted Australian lawyer (non-practising) · Founder, Lejacie · info@lejacie.com
This comes from Safe to Say, Safe to Reach, Safe to Use, a framework still in development (Draft v0.1). This page gives general information on designing handovers between services. It’s not legal advice, and it doesn’t tell your organisation what it may or must share: follow your own privacy, consent and information-sharing obligations. The Maya example is fictional. Lejacie doesn’t provide legal advice or representation.