NewProjects
Create a component dictionary
Use one identifier per component type, with a consistent description, unit and storage location. Separate quantities by site and store so that the same item is not counted twice.
Record each movement
Keep an issue or transfer reference, date, sending and receiving locations, quantities and responsible person. Link corrections to the original transaction instead of silently replacing its history.
Reconcile returns
Compare expected returns with received quantities. Keep damaged or unverified components separate from usable stock and route them through the appointed inspection process. HSENI highlights the need for suitable components and competent inspection.
Information checklist
- Component identifier, description and unit
- Store and site location
- Issue, transfer or return reference
- Expected and received quantity
- Condition record and responsible person
Frequently asked questions
Is this an NPScaff usage guide?
No. This is general record-organization guidance. NPScaff's public help describes scaffold requests, approvals, field tags, maps, reports and dismantling instead.
Does a stock total show what can be safely used?
No. Quantity, location and inspection status are separate records.