Community Facility Handover Preparation Checklist

Write down what changes at handover, such as who holds the keys, who arranges upkeep and who a user contacts with a problem.

Listing the changes turns a vague moment into a set of specific transfers, each of which somebody has to accept.

Ask the contractor and the designer what they expect handover to consist of, and compare that with what the group has been assuming.

The two descriptions rarely match, and the gap between them is where documents and demonstrations tend to fall through.

Decide who attends from the group, and make sure it includes whoever will actually operate the facility rather than only the chair.

Whatever is explained on the site is retained only by the person who will use it, and that is seldom the person who signed the papers.

Note what the group is being asked to acknowledge receiving, and read it beforehand rather than at the meeting itself.

Accepting completed work is a matter to discuss with a qualified professional acting for the group; nothing here amounts to accepting any work.

Ask whether use may begin at handover or whether anything has to settle, cure or be confirmed first.

When a facility may be brought into use is established by the contractor, the supplier and any relevant authority, and never assumed by the group.

Record what remains outstanding at that point and who is named as responsible for each item on that list.

Outstanding items with no name attached do not get done, and the list is the last chance to attach names while everyone is present.

Walk the facility with the drawings in hand and note where what was built differs from what was drawn or discussed.

Differences are usually deliberate and well reasoned, but only if somebody asks about them while the team is still available.

Photograph everything from consistent positions, since photographs taken at this point become the group's clearest record of the starting condition.

Later disagreements about condition are settled by images far more often than by anybody's recollection of the walk round.

Write down what you notice plainly, without deciding whether it is acceptable or how it ought to be put right.

Whether anything observed is acceptable is established by a qualified professional; an owner records observations rather than reaching conclusions.

Walk the site again after heavy rain and note where water sits, where it runs and where it drains slowly.

Water behaviour is the single most useful thing an owner can observe, and it is invisible on a dry handover visit.

Look along surfaces with the light low rather than straight down at them, since that is when unevenness and marks show up.

Most surface observations are only visible at a shallow angle, which is why they are noticed after everyone has left.

Check that everything the group expected is present, including small items such as covers, keys, spares and fixings.

Small items are the most commonly missing at handover and the hardest to obtain once the contractor has moved on.

Ask for drawings showing what was actually built, including anything that ended up in a different position from the design.

Built positions matter for every future repair and addition, and the information exists only while the team still has it to hand.

Request care and cleaning instructions for every surface and material, and note which elements came with nothing at all.

The gap in the instructions is exactly where a well-meaning volunteer will later damage something with the wrong product.

Collect warranty documents and note what each one covers and who issued it, rather than assuming they all come from the main contractor.

What a warranty covers, and what would affect it, is answered by whoever issued it; ask them directly rather than relying on assumption.

Ask for a name and contact route for each element, since one contractor rarely covers everything that ends up on a site.

Groups discover this the first time something fails and nobody can say whose element it was in the first place.

Note which documents were promised but not handed over, and record who agreed to send each one.

Outstanding paperwork is the item most quietly abandoned after handover, because nobody wrote down who owed what.

Ask what information the group would need if part of the facility ever had to be opened up or altered.

Asking now produces answers; asking later produces a search through records that may no longer exist anywhere.

Ask to be shown the controls for anything powered, and record where the isolation points are located.

Anything electrical is operated and maintained according to the installer instructions and local requirements; ask a suitably qualified person first.

Have the gates, locks and any barrier demonstrated, and note which of them need a knack that would not be obvious to a newcomer.

A lock with a trick to it becomes a permanent obstacle for every user group who was not present for the demonstration.

Ask where drainage points, covers and access chambers are, and mark them on a plan the group keeps.

These are invisible within a season of use, and finding them again later usually means somebody digging speculatively.

Have everyone who will operate the facility present for the demonstration, rather than one representative who will pass it on.

Second-hand explanations lose exactly the practical detail the demonstration existed to convey.

Record the demonstration in notes or photographs, since it will be needed by somebody who was not able to be there.

Community groups turn over steadily, so anything explained only in person is lost within a few changes of volunteer.

Ask which tasks the group is expected to do itself and which need a specialist called in each time.

Groups routinely attempt specialist tasks in good faith, and that is a common route to invalidating a warranty.

Write down every upkeep task the suppliers describe, and note who in the group would realistically carry out each one.

A task without a named person is a task nobody does, and the list is only meaningful once the names are beside it.

Ask which tasks affect a warranty if they are not carried out, and obtain that answer in writing from the supplier.

Only the supplier or contractor who issued a warranty can say what upkeep it depends on; a general answer from anyone else is not reliable.

Note which tasks need equipment or materials the group does not currently have, and record what is missing.

Upkeep stalls immediately when the first task needs something nobody thought to obtain before handover.

Record what would need a specialist and how the group would go about arranging that when the time comes.

Knowing who to call is most of the work, and it is knowledge that exists only while the original team is still in contact.

Note where each task would sit in the group's own arrangements, so it belongs to somebody rather than to nobody in particular.

Upkeep attached to a named role survives committee changes; upkeep attached to goodwill does not.

Record what the suppliers say must not be used on a surface or finish, since well-meant cleaning is a frequent cause of damage.

What may be applied to any surface follows the supplier instructions for that material; ask the supplier rather than relying on general practice.

Record the contact route for reporting something after the team has left, including a name rather than only an organisation.

A general contact point absorbs reports without acting on them, whereas a named person can at least be followed up.

Ask what the contractor expects to be told about and how, and note anything they say is not theirs to deal with.

Reports sent to the wrong party are simply lost, and the boundaries are clear to the team but not to the group.

Decide who in the group does the reporting, so that several accounts of the same thing do not arrive separately.

Multiple reports of one item make the group look uncertain and give any recipient a reason to wait and see.

Ask what period the group has for raising things after handover, and record the answer in writing rather than relying on memory.

Any period for raising matters is set out in the arrangement with the contractor; ask them and check it with a qualified adviser if unclear.

Keep photographs and notes of everything raised, together with the reply received and the date it arrived.

An unanswered report cannot be pursued without evidence that it was made, and that evidence takes moments to keep.

Record what happens to the reporting route if the contractor or supplier changes hands or stops trading.

Groups usually discover the answer at the point they need it most, and by then there is nobody to ask.

Record what users say during the first sessions, since they notice things that a walk round never shows.

Users encounter the facility in motion and in the dark and in the wet, which is when its practical shortcomings appear.

Note where water, light or noise behaves differently from what was expected, and report it through the agreed route rather than informally.

Observations passed on in conversation are not records, and the group needs a trail if the matter has to be pursued.

Watch where people actually walk, and record any route appearing across grass, planting or a boundary.

A new worn line shows that the intended route does not match how the facility is used, and it appears quickly once use begins.

Note whether gates, stores and controls are being used as intended, or whether people have already found a way round them.

A workaround adopted in the first sessions becomes the permanent arrangement unless somebody notices and asks why.

Tell neighbours and user groups that the facility is now in use, and record who was told and by what means.

Neighbours who hear about a facility from the noise of it starting react differently from those told beforehand.

Record early observations in one place, so the group holds evidence rather than recollection when it raises them.

Scattered notes across several members become an argument about what was seen, instead of a clear list of what to raise.