Facility Defect Reporting Planning Checklist

Decide the one route a report is meant to take, and accept that an informal second route will always be used unless the first is easier.

People report to whoever they happen to know, and that only changes when the official route is genuinely less effort.

Put the reporting route where the facility is, rather than only on a page somebody has to remember to go and look at.

The moment of noticing happens on site, and a route that is not visible there loses most of what it would have collected.

Write the route in words a first-time visitor understands without knowing who runs the facility or what anything is called.

Regular users need no wording at all; the wording exists entirely for everybody else.

Note how somebody reports something while standing at the facility with no signal, no phone to hand or nothing to write with.

This is a common situation at outdoor and remote facilities, and it is usually not thought about until reports fail to arrive.

Decide whether people may report anonymously, and note what you lose if nobody can go back with a follow-up question.

Anonymity raises the number of reports and lowers what can be done with each, which is a trade worth making deliberately.

Send a report through your own route and follow where it actually lands, rather than assuming it arrives where it was meant to.

Routes that were set up correctly and then broke silently are extremely common, and nothing announces the failure.

Note who is told the route exists, including regular users, casual visitors, cleaners, coaches and visiting contractors.

Each of these groups is at the facility at a different moment and notices genuinely different things.

Ask for what was seen, exactly where it was and when it was noticed, and resist adding much beyond that.

These three are what make a report actionable, and each further question measurably reduces how many are completed.

Ask for a photograph with enough of the surroundings in it to locate the item without the reporter being present.

A close-up with nothing identifiable around it means somebody has to go looking, which is often where a report stalls.

Ask whether the reporter has noticed it before, since that separates something new from something long-standing.

This one question does more to prioritise a list than any scale of seriousness you could offer.

Ask what the person was doing at the time, because that frequently explains what made the thing noticeable at all.

Something felt underfoot during play and something seen from the gate are different pieces of information.

Avoid asking a reporter to rate how serious something is, and ask what they saw instead.

How serious something is at a facility is established by a suitably qualified professional, not gathered from whoever happened to notice it.

Ask for a contact detail only if somebody will genuinely use it to go back with a question.

Collecting contacts nobody uses adds friction to the form and creates an expectation of a reply that never comes.

Keep the whole thing short enough that somebody standing outside in the cold with wet hands will actually finish it.

That is the real setting most reports are made in, and forms are almost never designed for it.

Name the destination as a role rather than as an individual, so the route survives a change of committee or a change of arrangement.

Routes pointing at a named person are the single most common way a reporting arrangement quietly dies.

Decide who reads reports when the usual person is unavailable, and check that they can actually reach the same place.

Access that was never tested is access that does not exist at the moment it is needed.

Note what happens to a report arriving when nobody is looking, since the honest answer of nothing until somebody checks is still worth knowing.

Knowing the gap exists lets you say something to reporters rather than leaving them to assume it was received and read.

Agree who acknowledges a report and roughly what that acknowledgement says.

An acknowledgement takes very little effort and is the main reason somebody bothers to report a second time.

Decide what a receiver does with a report they do not understand, so that it is passed on rather than quietly parked.

A report that is not understood is passed to the installer or a suitably qualified professional, not interpreted by whoever received it.

Note which reports go straight out to a specialist without waiting for anybody to discuss them first.

Which subjects warrant immediate attention is established with the installer, a qualified professional and the relevant authority before opening, not decided as each report arrives.

Record who received each report, because reports dealt with personally and never written down are the ones that vanish entirely.

A helpful person handling something quietly is how a facility loses its whole reporting history.

Record the report in the reporter's own words, and keep any view formed about it as a clearly separate line.

The original wording often contains the detail that turns out to matter, and summarising it away is irreversible.

Note that concluding a report needs nothing further is itself a decision, and write down that it was taken and by whom.

Concluding that a reported item needs no action is a judgement; where there is any doubt it belongs with a suitably qualified professional rather than with the operator.

Decide which categories a report is sorted into, and keep those descriptive of what was seen rather than ordered by how serious anybody thinks it is.

Descriptive sorting groups reports usefully without anybody having to make a judgement they are not qualified to make.

Note the subjects that are never handled through this route at all, particularly anything concerning injury, harm to a person or the wellbeing of a child.

Injury, harm and safeguarding matters go immediately to qualified professionals and the relevant authority, and are never held in a facility reporting record.

Agree what the receiver adds to a report, such as whether anybody went and looked and what they found when they did.

Without this the record shows what was reported but not what was known afterwards, which is half the story.

Keep reports that turned out to be nothing, since a pattern only becomes visible if the quiet entries are still there.

Deleting the unremarkable reports is how three mentions of one corner become three separate isolated incidents.

Note where a report about somebody's behaviour rather than about the facility is sent, and keep it out of the facility record.

Reports concerning a person are handled separately with the appropriate qualified professionals, and nothing in a facility checklist governs how they are dealt with.

Keep reports about the same location together, so several separate mentions of one corner are visible as a single thing.

Reports arriving apart from each other are almost never connected mentally, however obvious the link looks in hindsight.

Note when reports cluster around a particular use, a particular part of the facility or particular weather conditions.

The clustering is frequently the most informative thing in the record and it is invisible in individual entries.

Record which subjects stopped being reported as well as those that continue, since something that quietly ended may have been dealt with by somebody unknown.

Silence can mean resolved or it can mean that people gave up, and the two look identical unless you look.

Look for the thing nobody reports because everybody assumes it is already known about.

Long-standing conditions become invisible to regular users, which is exactly why casual visitors are worth listening to.

Note how many separate people mentioned something, without treating that number as a measure of how serious it is.

Frequency of reporting reflects who uses a facility and when; it is not a substitute for an assessment by a suitably qualified professional.

Decide at what point a repeated report becomes a question for a professional rather than simply another entry in the record.

Without an agreed trigger, repeats accumulate indefinitely because each one individually looks minor.

Keep the record in a form that can be read from beginning to end, not only searched one word at a time.

Patterns are found by reading, and a record that can only be queried hides exactly what you were hoping to find.

Tell the reporter what happened, even when the answer is that somebody went and looked and nothing followed from it.

The absence of a reply is read as the absence of interest, which is how a facility goes quiet before it goes wrong.

Note that once people conclude nothing comes of reporting, they stop, and the record then shows a facility with no problems.

A sudden fall in reports is worth investigating as a sign about the route rather than as good news about the facility.

Decide what is shown at the facility about things already reported, so the same item does not arrive repeatedly from different people.

Visible acknowledgement of a known item saves duplicate reports and, more importantly, keeps people confident that reporting works.

Agree who tells users when something reported has changed how the facility may be used, and on whose instruction that is said.

Restricting or stopping use of any part of a facility follows advice from a suitably qualified professional and the relevant local requirements, not from the operator's own reading of a report.

Keep a short note of what the reporter was told, so a second conversation starts from the same place rather than from scratch.

This matters most with the persistent reporters, who are usually the ones noticing genuine things.

Ask regular users occasionally whether they ever reported something that never reached you.

This is the only reliable way to discover that a route has been broken for some time.

Note what the reporting wording says about matters the route does not cover, so people are directed elsewhere rather than nowhere.

Ask qualified professionals and the relevant authority what your reporting wording should say about emergencies, injury and safeguarding, rather than drafting that part yourself.