Appointments booking

Birthday-month recall: does it work for chronic disease?

Birthday-month recall compared with condition-based and hybrid recall for long-term conditions: workload, uptake, QOF timing and how to switch.

Ava research teamPublished 6 min read

On this page
  1. What birthday-month recall is
  2. Why the choice matters now
  3. The models compared
  4. Workload: the strongest argument for birthday month
  5. QOF timing and the 31 March deadline
  6. Uptake: what to expect
  7. Explaining it to patients
  8. Where birthday month struggles
  9. How to switch to birthday-month recall
  10. The hybrid most practices end up with
  11. Decision checklist
  12. Frequently asked questions
  13. References

Key takeaways

  • Birthday-month recall reviews all of a patient's long-term conditions once a year in the month of their birthday, which spreads work evenly and is easy for patients to remember.
  • Condition-based recall gives clinical leads more control over timing but often produces several visits per patient and a busy winter.
  • QOF achievement is measured on 31 March, so any recall model must leave room to catch up patients missed during the year.
  • Birthday-month recall struggles with poorly controlled patients who need more frequent checks, new diagnoses and October and November birthdays that clash with flu clinics.
  • A hybrid usually works best: birthday month as the default, with clinical exceptions and a catch-up quarter.

What birthday-month recall is

In a birthday-month system, every patient with one or more long-term conditions is invited once a year, in or just before the month they were born, for a single combined review of all their conditions. Tests are booked a week or two before, and the review covers everything the patient needs that year. The idea is simple enough for patients to remember: 'My review is in my birthday month.'

The alternative most practices have used is condition-based recall: asthma reviews in one season, diabetes in another, often driven by the QOF year and by which clinician runs which clinic. Many practices have something in between. This comparison looks at which approach works best for workload, uptake and QOF, and when to choose each.

Why the choice matters now

Clinical capacity is not keeping pace with list sizes. England had 29,400 full-time-equivalent fully qualified GPs in September 2026, only 36 more than in September 2015[1], while the average number of patients per FTE GP rose to 2,143[2]. At the same time, the over-65 population keeps growing, by 2.0% in England in the year to mid-2025[3]. A recall system that creates peaks or duplicate visits wastes capacity the practice no longer has.

Patients per full-time-equivalent GP, England2015 figure derived from the reported rise of 205 patients
Patients per full-time-equivalent GP, EnglandColumn chart. September 2015: 1,938; September 2026: 2,143.01,0002,0003,000September 2015: 1,9381,938September 2015September 2026: 2,1432,143September 2026Patients per full-time-equivalent GP, EnglandColumn chart. September 2015: 1,938; September 2026: 2,143.01,0002,0003,000September 2015: 1,9381,938September 2015September 2026: 2,1432,143September 2026

Source: British Medical Association, 2026[2]

Show the data
ItemValue
September 20151,938
September 20262,143

The models compared

Birthday-month, condition-based and hybrid recall compared on practical criteria.
CriterionBirthday monthCondition-basedHybrid
Monthly workloadEven across the yearPeaks by condition and seasonMostly even, with a planned catch-up quarter
Visits per patient with several conditionsOne combined reviewOften severalOne combined review, with exceptions
Patient understandingVery easy to explainHarder; different dates for different conditionsEasy, with clear exceptions
Clinical control over timingLower; fixed to birth monthHigherHigh for exceptions, low for the rest
QOF year-end riskLow if missed patients are caught upOften high in Q4Lowest, with a catch-up quarter
Set-up effortHigh at first: searches and re-schedulingLow if already in placeHighest at first, then routine
Fit with flu seasonPoor for October and November birthdaysCan avoid autumnMove autumn birthdays earlier

Workload: the strongest argument for birthday month

Birthdays are spread fairly evenly across the year, so birthday-month recall gives roughly a twelfth of the long-term condition population each month. That makes staffing predictable: the same number of HCA and nurse sessions every month, rather than a scramble in the last quarter.

Example (fictional): a practice has 2,400 patients with at least one long-term condition. Under condition-based recall, its monthly review load ranged from about 120 in summer to over 350 in February and March. Under birthday-month recall, every month needs about 200 combined reviews, and the number of separate review appointments falls because patients with several conditions are seen once.

QOF timing and the 31 March deadline

QOF achievement is measured on 31 March for patients registered on that date, and activity described as 'in the preceding 12 months' must fall within the 12 months ending on that 31 March[4]. For a birthday-month system, that means any review completed during the year counts, whichever month it falls in. The risk is not the birthday month itself but patients who miss their month and drift: a patient born in May who does not respond may not be chased until the year-end push.

  • Chase non-responders within the same month, not at year end.
  • Keep a catch-up session each month for patients who missed their birthday-month review.
  • Review newly diagnosed and newly registered patients when they join a register, not at their next birthday.
  • Check monthly which patients are at risk of having no review by 31 March, starting from October.

Uptake: what to expect

There is little published national evidence comparing uptake between birthday-month and condition-based recall, so be wary of anyone quoting a precise improvement. The expected benefits are practical rather than proven: a system that is easier for patients to understand, fewer patients invited several times for overlapping reviews, and non-responders who are easier to spot because each patient has one due month rather than several. Whether those benefits turn into higher uptake depends on your population, your invitation routes and how quickly you chase people who do not respond.

Measure it yourself. Before switching, record your current response rate to first invitations, the share of patients with several conditions who were seen more than once for reviews, and the number of reviews completed in January to March. Compare the same figures after twelve months. If response rates fall for a particular group, such as younger working patients, look at the invitation route and the clinic times rather than the model itself.

Explaining it to patients

Patients who are used to several separate reviews may worry that a single annual visit means less care. Explain the change in plain terms in the first invitation and on the website: one longer appointment covering all their conditions, with tests done first so results are ready, and extra check-ups in between if their clinician thinks they need them.

  • Say clearly that patients should not wait for their birthday month if they feel unwell or their symptoms change.
  • Tell patients whose review moves earlier or later in the transition year why it has moved.
  • Ask the patient participation group to read the invitation wording before it goes out.

Where birthday month struggles

  • Poorly controlled patients: someone with high HbA1c or uncontrolled blood pressure needs checks every few months, not once a year. They need clinician-set follow-ups on top of the annual review.
  • Autumn birthdays: the 2026 to 2027 adult flu programme starts on 1 October[5], and most eligible people should be vaccinated by the end of November[6]. Reviews in those months compete with flu clinics for nurse time; consider moving October and November birthdays to September.
  • Seasonal conditions: some practices prefer asthma reviews before winter. A hybrid can bring respiratory reviews forward for autumn birthdays.
  • Transition: in the first year, some patients will be reviewed early or late as they move to their birthday month. Plan the switch carefully.

How to switch to birthday-month recall

  1. Get clinical agreement

    Agree the bundles, which conditions are reviewed together, and the exceptions for poorly controlled patients.

  2. Build the searches

    One search per month finding patients with any long-term condition whose birthday falls the following month, excluding those reviewed recently.

  3. Plan the transition year

    Patients reviewed within the last six months keep their current date this year and move to their birthday month next year; others move now.

  4. Set fixed monthly sessions

    Book HCA and nurse sessions for the expected monthly volume, plus a catch-up session.

  5. Tell patients

    Explain in the first invitation: 'From this year, we will invite you once a year in your birthday month for one review of all your conditions.'

  6. Review after six months

    Check monthly volumes, response rates and QOF progress, and adjust the exceptions.

The hybrid most practices end up with

In practice, pure birthday-month recall is rare. A hybrid keeps the even workload and the single combined review, while giving clinicians control where it matters.

  1. Default: one combined review in the patient's birthday month, with tests booked first.
  2. Exception: clinician-set follow-ups for poorly controlled patients, at intervals the clinician chooses.
  3. Exception: autumn birthdays moved to September, ahead of flu clinics.
  4. Exception: new diagnoses reviewed within an agreed period of joining a register.
  5. Safety net: a monthly catch-up session and a January check of anyone not yet reviewed in the QOF year.

Decision checklist

  • Do many of your patients have more than one long-term condition? If so, birthday-month or hybrid recall saves the most visits.
  • Is your Q4 review workload far higher than the rest of the year? An even model will help.
  • Do you have the clinical system skills to build monthly searches and bundled slot types? If not, plan support first.
  • Do clinicians want tight control over timing for particular conditions? Use a hybrid with written exceptions.
  • Can you protect nurse time in October and November? If not, move autumn birthdays.

For the invitation sequence and review bundles, see booking long-term condition reviews. For year-end planning, see QOF explained, and for dental recall, see risk-based dental recall intervals.

Frequently asked questions

What is a birthday-month recall at a GP surgery?

It is a system where patients with long-term conditions are invited once a year, in their birthday month, for one combined review of all their conditions, usually with a blood test beforehand.

Is birthday-month recall better than condition-based recall?

It usually gives a more even workload and fewer visits for patients with several conditions. Condition-based recall gives more control over timing. Many practices use a hybrid of the two.

Does birthday-month recall work for QOF?

Yes, as long as patients who miss their month are chased promptly. QOF counts activity in the 12 months ending 31 March, whichever month it happens in.

References

  1. British Medical Association (2026). Pressures in general practice data analysis (opens in a new tab) ↑

  2. British Medical Association (2026). Pressures in general practice data analysis (opens in a new tab) ↑

  3. Office for National Statistics (2025). Population estimates for the UK, England, Wales, Scotland and Northern Ireland: mid-2025 (opens in a new tab) ↑

  4. North and South Essex Local Medical Committees (2026). Quality and Outcomes Framework (QOF) guidance for 2026/27: LMC summary (opens in a new tab) ↑

  5. GOV.UK (UKHSA, DHSC and NHS England) (2026). National flu immunisation programme 2026 to 2027 letter (opens in a new tab) ↑

  6. GOV.UK (UKHSA, DHSC and NHS England) (2026). National flu immunisation programme 2026 to 2027 letter (opens in a new tab) ↑

Book a demo

See Ava handle your calls.

Book a short demo. We’ll walk through your calls and workflow, and agree what Ava should take care of.

Book a demo