Delivery Point Assessment

This assessment is one step in the Cold Chain and Transport programme, scoped to the delivery point itself. Using it to cover the journey, the vehicle or the load turns it into a form that reports on everything and nothing.

ISO 39001 cl.6.1 requires the organisation to address risks arising from factors it does not directly control, which is exactly the position a driver is in at someone else's site. The clauses below map that requirement onto the assessment's sections.

The obligation to look after a driver on someone else's premises does not disappear at the gate. Three frameworks make that explicit in different ways.

Filling in every field is the easy part. The judgement calls below are what decide whether the record would survive a real incident investigation or a certification audit.

Patterns that recur across delivery point assessments, and what each one is actually telling the workspace.

A distribution centre delivered to for two years scored Reversing Required: Yes and Banksman Provided: Yes on its original assessment, set up on the first delivery and never reopened. The banksman had been a temporary arrangement the customer used during a refit, and had not run since.

A reversing driver clipped a loading bay pillar on a delivery eighteen months later. The investigation found the assessment on file no longer matched how the site actually operated, and that nothing in the record had forced a review in between — the only defined trigger was 'first delivery and after incidents', and there had been no incident to force the second look until this one.

The form is the easy part. Keeping it current, routing it to the right owner and holding the evidence together across sites is the work that actually slips.

KnowFleet

Holds the delivery point assessment against the customer register and the journey library, and flags when a site is overdue its review or has an incident with no follow-up assessment.

KnowSafe

Carries the incident and near-miss log a delivery point assessment should be checked against before Incident History At This Point gets marked No from memory.

KnowLogistics

Tracks which delivery points are active, how often they're visited, and which ones a driver has raised a concern about that never made it into a formal assessment.

Ella

Coordinates the crew, rolls completion and exceptions into one view, and holds every write for your approval before it touches a record.

Residual band

A scoring model that reflects the risk remaining after existing controls are accounted for, rather than the raw hazard. Low is good on this template — a low band means the controls in place are judged sufficient for the residual risk left over.

Singleton record

A record type set up once per subject — here, once per delivery point — and maintained over time, rather than created fresh for every event. Other templates and registers refer back to the single record rather than each holding their own copy.

Banksman

A person positioned to guide a vehicle during a reversing or manoeuvring operation, typically where sightlines from the cab are inadequate. Their presence, or absence, is one of the clearest indicators of how a reversing hazard is actually being controlled at a site.

Safe System (ISO 39001)

The approach underlying ISO 39001, which treats road safety as an interaction of road users, vehicles, speeds and roads or sites, none of which is expected to fail in isolation without the others compensating. A delivery point assessment is one input into that system for the 'site' factor.

CAPA

Corrective and Preventive Action — the record raised to close out a finding. On this template, an Action Required: Yes answer is only as good as the CAPA ID it links to; without one, the finding has nowhere to be tracked to closure.