A Chemical Safety Register: Why Uploading a Safety Data Sheet Does Not Complete a Workplace Assessment

If you commission an app for a workshop or cleaning business, do not let “safety data sheet uploaded” mean “this work has been assessed.” A supplier document describes a chemical product. A workplace assessment considers how people actually use or encounter substances, who may be harmed and what controls the work requires. Your register should connect these records without substituting one for the other.

This article uses Great Britain's Health and Safety Executive guidance on COSHH as its reference. It is a software requirements discussion, not a chemical assessment, legal advice or permission to carry out hazardous work. Other jurisdictions need their own applicable professional and legal review.

Start with the activity, not only the purchased product

HSE explains that harmful substances are not limited to products bearing a hazardous label. Processes can produce substances, including wood dust from sanding and fumes from welding. A purchasing catalogue is therefore not necessarily a complete map of workplace substance exposure.

For the proposed app, ask the responsible assessor to define the activities and locations that need records. A substance generated during work needs a way into the register even when there is no corresponding supplier purchase or uploaded sheet. Do not make a supplier product number a mandatory prerequisite for every assessment.

An illustrative workshop might have a product record for a purchased cleaner and a separate activity record for sanding. The developer should demonstrate both without inventing a supplier document for the dust. These are examples of record design, not instructions for safely performing either activity.

Keep supplier information and local assessment connected

HSE's chemical safety data sheet page says that sheets describe chemical hazards and provide handling, storage and emergency information. It explicitly warns that a safety data sheet is not a risk assessment.

A useful record relationship connects the relevant supplier material to an assessor's account of the actual activity. Ask for a visible distinction between a received document, information awaiting review and an assessment reviewed by the responsible person. Those are proposed application states, not HSE certification categories.

The product name alone should not make every activity appear covered. If the same product is used in different work settings, the assessor decides what the assessment covers. The app should display that coverage rather than infer it from a matching attachment. Preserve the source information used for the review so a later upload does not silently rewrite its basis.

Give the assessor the right questions

HSE's assessment guidance asks who might be harmed and how. It includes exposure routes, frequency and duration, people beyond the immediate workers, existing controls, further actions, responsibility and timing.

Use those questions to shape a discussion with the assessor, not an automatic safety score. A form that records only a product hazard symbol and a PPE checkbox misses much of that context. The guidance also cautions against automatically choosing personal protective equipment as the control measure.

Ask the developer to keep an unresolved action visible with its owner. The qualified person must determine the appropriate controls and whether work may proceed under the actual arrangements. A completed form or green badge cannot make that decision on its own.

Treat changed work as a review question

HSE calls for regular assessment review and consideration of changes such as staff, process, substances or equipment, as well as problems, accidents and near misses. That is different from merely watching the age of an attached PDF.

Your proposed workflow can let staff flag a changed activity and route it to the responsible reviewer. Keep the previous assessment identifiable while clearly showing the unresolved review. Do not automatically declare a new document acceptable, or an unchanged document sufficient, because the file upload succeeded. Agree the local review arrangements with the competent adviser rather than inventing a universal interval in the software brief.

Demonstrate the boundary before buying development

Use fictional records to test a purchased product with a sheet but no local assessment, a process-generated substance without a supplier sheet, and a changed activity awaiting review. Confirm that each remains distinguishable. Then have the assessor demonstrate an approved record and its outstanding actions without exposing actual workplace documents.

Bring an empty example to a business workflow discussion. An established safety management system may already meet the need. The commissioning decision is whether the tool supports accountable activity assessment, not whether it can collect a folder of PDFs.

Primary sources and limits

HSE: Chemical safety data sheets supports the distinction between product information and assessment. HSE: How to carry out a COSHH risk assessment supports the activity, exposure, controls and review context. Record relationships, workflow states and demonstrations above are proposed software requirements. No workplace, product or control measure has been assessed or certified here.