Cloudflare and service protection
What can a council portal safely cache on Cloudflare?
Separate public notices, time-sensitive updates and private portal responses. Give suppliers a cache decision table and a repeatable sign-off exercise.

A public timetable, a cancellation notice and a signed-in customer receipt can all live on the same website. Serving a saved copy is helpful for the timetable. A stale cancellation creates confusion. A receipt belongs to one person. Buy a caching policy that treats each of those pages deliberately.
Classify pages by audience and freshness
Ask the content owner for examples of material that changes slowly, material that needs urgent correction and material created for one person. For each example, record who may see it, how long it may remain out of date and how a correction reaches readers. Agree those values with the person who handles calls when information is wrong.
A library opening-hours page might tolerate a routine publishing delay. A same-day closure may need an immediate correction. If both come from the same template, the editor needs a practical way to meet the shorter deadline. Include the home page and any summary cards that repeat the notice.
Write down what the browser and the edge may store
Cloudflare’s Origin Cache Control documentation distinguishes reuse by a shared cache from handling in the visitor’s browser. Ask the developer to document the response headers and any edge rules that alter them. An administrator should be able to tell which instruction wins for a specific page.
Use fictitious receipts for two different test accounts. After signing in normally, each user should see only their own receipt. Have the delivery team provide evidence that personalised responses are excluded from shared caching and that changing a global performance setting cannot silently undo the rule.
Review a correction from the editor’s seat
Have a tester publish an invented closure, edit its time and check when the public notice changes across the list and detail pages. Include a visitor with a previously opened page. Write down when refreshing or reopening that page becomes necessary and explain the behaviour to service staff.
Put the tested examples and observed results in the handover. Assign responsibility for updating the table when a new signed-in feature is released. The same tests can then catch an accidental change without relying on someone remembering why the original cache policy was written.