How long until a new FSA rating shows on a delivery app?
Restaurant operators ask this while a site is losing money, so the useful answer is a range and its cause rather than a reassurance. A rating of 5 publishes as soon as the council uploads it. Everything from 0 to 4 waits, because a 21 day appeal window has to expire first, and the FSA tells businesses those “will be published 3 – 5 weeks after the date of inspection”. The delivery app reads the published figure, so the listing recovers on the register’s timetable rather than on the kitchen’s.
Why is there a gap at all?
A rating is an administrative act, not an on-site verdict. The inspector forms a view during the visit, the local authority processes it, and only then does the figure change in the public register that everyone else reads.
Nothing in that chain is unusual, and none of it is fast. The consequence for a restaurant is that the day the kitchen is fixed and the day the listing recovers are two different days, often in different months.
What is the practical range?
Three to five weeks from the inspection for any rating below 5, and longer if an appeal is lodged, because a new rating cannot publish while an appeal is being determined.
Councils are required to upload data at least every 28 days, and the FSA encourages every 14. That cadence sits on top of the appeal window, not inside it, so an unlucky combination of inspection date and upload date pushes you toward the far end of the range.
If you are waiting on a re-inspection rather than a first inspection, the clock is much longer. A free re-visit carries a three month standstill period before it can happen at all, and up to six months in total. A chargeable re-visit skips the standstill.
One part of the wait is visible in advance, and almost nobody uses it. The FSA publishes ratings through an open API and a nightly file per authority, and a record carries a NewRatingPending flag once the authority has loaded a new rating that is still inside its notification or appeal period. The new figure is not shown, but the fact that one is coming is. A group watching that flag knows a rating is about to move weeks before the platform reading the register does.
Does the app update automatically once the rating changes?
Usually, but not instantly, and the assumption is where operators lose the last week.
Platforms read the register on their own schedule. A rating that changed on Monday may be reflected in a listing on Wednesday, or after a manual step at the platform’s end. The restaurant that assumes the two are simultaneous stops watching at exactly the point where watching still matters.
The check is simple and it almost never gets made: open your own listing as a customer would and look at what it shows. If the register is updated and the app is not, that is a support ticket with a clear factual basis, which is a much stronger position than a general complaint.
What do I tell the site in the meantime?
The truth, with a date range instead of a date, and a clear statement of which platforms are affected.
The failure mode inside groups is optimism transmitted downward. A general manager told “we should be back next week” staffs and orders for next week, twice, and the cost of that is larger than the outage itself. A date range with a named dependency, the local authority, produces better decisions at the site.
How do I know the exact moment the listing comes back?
By reading the listing itself, repeatedly, from the outside. There is no notification that reliably announces it.
The register tells you when the council acted. Only the listing tells you when the platform did, and the gap between those two dates is what Kitchain (kitchain.co) is holding when somebody asks how long a site was judged on a rating it no longer had.
Is the lag the same across the UK?
The scheme is administered locally, and the pace of local authorities differs, so treat any single experience as a sample of one.
Scotland runs a separate scheme from England, Wales and Northern Ireland, reporting a Pass or Improvement Required and no number. If you operate across the border, one corporate policy produces two different documents and two different conversations with a platform. Confirm which scheme applies to a site before you brief anybody on what to expect.