Blog
A practical guide to management referrals
The quality of an occupational health report is often decided before the clinician meets the employee.
It is decided in the referral.
A vague referral asks for an assessment and leaves occupational health to work out why. A useful referral explains the decision facing the employer, the relevant demands of the role and the questions that clinical advice can help answer.
That distinction sounds small. In practice, it separates a focused assessment from one spent reconstructing the reason for the appointment.
A referral is not a medical questionnaire
Managers do not need to diagnose an employee or assemble a detailed medical history. The clinician will take an appropriate history during the assessment.
The manager’s contribution is different. They know what has happened at work, what the role requires and what decision needs to be made.
A useful referral might explain that an employee has been absent for six weeks, that their role includes regular driving and lone working, that a return has been discussed, and that the manager needs advice about timing and temporary restrictions.
It should not invite the manager to speculate about diagnosis, prognosis or whether the condition is “genuine”. Those are not management facts, and presenting them as facts can distort the assessment before it begins.
Referral forms often blur this boundary. They ask for everything that might be relevant in any case, so managers fill clinical fields with partial information or leave long sections blank. The result looks comprehensive while giving the clinician little dependable context.
A complete form is not necessarily a useful referral.
“Is this employee fit for work?” is rarely enough
Fitness is not an abstract property of a person. It relates to particular work, under particular conditions, at a particular time.
Consider the question:
Is the employee fit for work?
The clinician cannot answer it well without knowing what the work involves. A desk-based role with control over hours raises different questions from safety-critical work, regular night shifts or a job involving manual handling.
The question also hides the decision the manager may be trying to make. Are they considering a return next week? Reviewing a temporary adjustment? Deciding whether the employee can attend a particular site? Trying to understand the likely duration of restrictions?
“Fit for work?” compresses those questions into a yes-or-no answer that occupational health is rarely in a position to give without qualification.
A better referral makes the decision visible:
The employee is planning to return following a period of sickness absence. Their role involves two night shifts each week and regular driving between sites. We need advice on whether a return is clinically reasonable now, whether temporary changes to hours or driving should be considered, and when those arrangements should be reviewed.
This does not tell the clinician what conclusion to reach. It gives them something specific to assess.
Separate facts, observations and questions
Management referrals often contain the right information in the wrong form.
A manager may write that an employee is “struggling with workload”. That could mean work is being missed, the employee has said they feel overwhelmed, colleagues have raised concerns or the manager has inferred a health problem from a change in behaviour. Those are different facts.
Good referrals separate what is known from what is observed.
Dates of absence, contractual hours and role requirements can be stated directly. Workplace observations should be attributed: what changed, when it changed and who noticed. Information provided by the employee should be identified as such. The referral questions can then explain what advice is needed.
This separation helps the clinician judge the relevance and reliability of the context. It also gives the employee a fair account of why they have been referred.
The referral should not be the first place the purpose becomes clear. If the manager cannot explain the reason for referral to the employee in ordinary language, the request is probably not ready to send.
More questions can produce a weaker report
Question libraries are useful. They help managers ask about common matters such as functional restrictions, adjustments, likely timescales and review.
They also create an easy failure mode: selecting every available question in case one proves useful.
The report then has to cover fitness, prognosis, disability, adjustments, attendance, redeployment and ill-health retirement, even when only one or two issues relate to the current decision. Broad questions invite broad answers. Repeated across a service, they make reports longer without making them more useful.
The strongest referral forms do not present the same catalogue for every case. They narrow the questions according to the reason for referral and ask the manager to add what is specific.
A return-to-work referral might concentrate on current functional capacity, temporary changes and review dates. A concern about performance should require the manager to describe the observed work problem before asking whether health may be contributing. An ill-health retirement pathway needs different evidence and should not be reached by adding another question to a routine management referral.
Good configuration removes irrelevant choices. It does not expose every possible choice at once.
Triage should improve the referral, not work around it
Weak referrals are often accepted because returning them feels slower than letting the clinician sort them out.
The delay does not disappear. It moves.
The clinician uses assessment time to establish basic role information. The employee is surprised by questions they did not know the employer was asking. The report answers a clinically sensible question, but not the management decision that prompted the referral. An administrator then coordinates clarification after the appointment.
A short triage step can prevent that sequence. Missing role demands, contradictory dates or unclear questions can be returned for clarification before an appointment is booked. The important detail is to preserve the exchange in the case record. Quietly editing the manager’s referral removes the distinction between what was submitted and what occupational health later clarified.
Not every referral needs clinical triage. Clear rules can identify which cases are ready to proceed and which need review. The aim is not to add an approval stage. It is to resolve ambiguity at the least expensive point in the process.
Software should make a good question easier to ask
Management referral software is often judged by how quickly someone can submit a form. Speed matters, but submission is the wrong endpoint.
The real test is whether the resulting referral can support a focused assessment and a useful report.
That means showing managers only the questions relevant to the pathway. Role demands should be concrete enough to inform a clinical opinion. Existing adjustments and absence details should be visible without asking for the same information twice. The employee, clinician and manager should all be able to recognise the purpose of the referral.
The workflow should preserve what was submitted, what was clarified and which questions were ultimately accepted for assessment. That history matters when the report is reviewed later.
Occentra treats the referral as the start of the case, not an isolated form that disappears once submitted. The principle is broader than any product: information captured at the start should give structure to the work that follows. Our guide to occupational health referral management explains that Referral-to-Case lifecycle in more detail. You can also see how it fits within the wider Occentra platform.
A referral has succeeded when it creates a shared question. If the manager, employee and clinician enter the process with three different ideas about why they are there, no amount of detail added later will make the pathway feel clear.