Make a useful HazLoc evidence request

What you will practise

• Distinguish an evidence item from the broader conclusion somebody wants to draw from it.
• Write a specific missing-evidence request with a provider, reviewer and review trigger.
• Update a handover when new information contradicts the quoted product identity.

A document can answer a limited question

A project file often grows faster than the team's understanding of it. A quotation, a certificate and an email may arrive together. Treat them as separate evidence items: what does each identify, what question does it answer, and what question remains open? A folder marked complete is not a reason to skip those distinctions.

IECEx explains that its official online certificate is the controlled record and that a saved copy should be checked against it. That is a document-control step. It does not, by itself, identify an undelivered unit or settle the circumstances of its proposed use. Keep the exact issue and the date of the check attached to your note. [S1]

The practical skill here is disciplined reading. You are preparing questions for the project process; you are not replacing the person responsible for the technical decision. The fictional records below deliberately leave information missing. Your task is to make those gaps visible without discarding useful evidence.

Three questions worth keeping separate

Document coverage: which product, configuration and issue does the supplied record actually describe? Product identity: what was quoted, ordered and eventually received? Application: what does the responsible project team know about the proposed location and the assembled equipment? These are useful organising questions, not a complete selection checklist.

HSE's Great Britain guidance treats workplace explosion risk, area classification, equipment selection and competent verification as related responsibilities. A certificate is one part of the information needed for that work. This lesson provides no zoning rule, equipment-category selection rule or national market-approval route. [S2]

A weak note says 'certificate received'. A stronger note says 'the recorded online issue lists the quoted model; receipt identity and site information are still missing'. The stronger note preserves the progress made and the decision still open.

Use a five-field evidence request

Start with received evidence: name the record and its revision rather than writing 'documents'. Next write the narrow claim supported by that record. Then name the gap as a question: 'Does the delivered unit match the model listed in the recorded certificate issue?' is easier to act on than 'check compliance'.

Name both the evidence provider and the responsible reviewer. They may be different people. A supplier can provide information while a project reviewer decides what it means for the application. Finally record the next trigger, such as receipt of the unit, a design change or the next handover review. A date alone is useful only if somebody owns the action.

Avoid invented certainty. 'Not yet received', 'quoted model differs' and 'application review open' are legitimate states. Your worksheet can carry them clearly. Do not choose a trip setting, protection concept or approval status simply to fill a blank.

New evidence can reopen an apparently settled question

A handover is a living account of what is known. If an attachment is replaced or a delivered label differs from the order, retain the earlier reference and record the change. Do not silently rewrite the old note as though it had always described the new unit.

The updated record should identify the discrepancy, the evidence still required and the route for a responsible decision. Whether an item can be accepted, substituted or installed is outside this lesson. A learner should be able to explain why the existing record cannot answer that question yet.

Check your reasoning

Choose an answer to reveal formative feedback. Answers are public by design. These checks do not award a grade or certificate.