MHE inspection: Daily Pre-Use Checks for Forklifts and Materials Handling Equipment
A practical guide to examining forklifts before use, acting on defects and keeping records that distinguish equipment safety from production-quality decisions.

On this page · 11 sections
- 1What MHE inspection covers—and what it does not
- 2Regulatory mapping: US powered trucks and Great Britain guidance
- 3Train operators to recognise defects and escalate uncertainty
- 4Run the pre-use check without creating a new hazard
- 5Manage defects from stopped use to human-authorised return
- 6Keep an inspection record that supports a defensible decision
- 7Connect inspection, maintenance and production without losing control
- 8Failure modes that make completed checklists unreliable
- 9Measure safe decisions, not just checklist completion
- 10Three worked cases across regulated manufacturing environments
- 11Implementation and review checklist for a workable inspection programme
How does MHE Daily Inspection apply to your shop floor?
Pick your industry and scale — Ask V5 rewrites the definition in your context, gives a worked example, and shows what V5 does on day one.
01What MHE inspection covers—and what it does not
MHE inspection is a pre-use examination of materials handling equipment to identify defects or conditions that could make its intended operation unsafe. Common search terms include MHE daily inspection, forklift pre-use inspection and forklift daily checklist. The checklist structures the examination; completing a form is not, by itself, an inspection. The useful output is a decision about intended use, supported by actual observations.
MHE is an operational umbrella term covering equipment such as forklifts, powered pallet trucks and manual handling aids. It is not a reason to apply one legal regime or checklist to every equipment type. Keep these equipment-management activities distinct:
| Activity | Main question | Typical evidence | Boundary |
|---|---|---|---|
| Pre-use inspection | Whether the equipment appears suitable for intended use | Item results and observations | Not a repair activity |
| Planned maintenance | What servicing or replacement is due | Service record | Not a substitute for the pre-use decision |
| Periodic thorough examination | What a defined examination establishes | Examination report | Not the same task as an operator walkaround |
| Workplace assessment | Whether the route and operating environment are suitable | Hazard assessment | Not a vehicle-condition check |
These are functional distinctions, not universal examination requirements or intervals. Maintenance history in a CMMS answers a different question from today's pre-use observations. For the separate Great Britain lifting-equipment topic, see LOLER thorough examination.
As site practice, shape the checklist around the truck model, attachments, power source and intended operating conditions, using the equipment instructions. An electric pallet truck and a combustion-powered counterbalance truck need different prompts; an attachment can introduce additional inspection points. Keep each prompt relevant to an observable condition and the resulting use decision, rather than collecting generic ticks that conceal what was actually examined.
02Regulatory mapping: US powered trucks and Great Britain guidance
Map the inspection programme by equipment and jurisdiction before choosing a checklist. “MHE” is an operational umbrella term, not a reason to apply one country’s powered-truck timetable to every handling asset. Product-related risks form a separate planning layer.
US: examination timing for covered industrial trucks
For covered industrial trucks, 29 CFR 1910.178(q)(7) requires examination before placement in service. Examination must occur at least daily; where trucks are used on a round-the-clock basis, the provision says they must be examined “after each shift.”
Keep that wording distinct from the site’s handover procedure. A site may organise a forklift pre-shift check around incoming operators, but should map that schedule explicitly against the before-service, daily and after-each-shift requirements rather than describe OSHA’s wording as “before every shift.”
Great Britain: identify the passage and its authority
HSE L117 includes Approved Code of Practice text and guidance on operator training for stacking rider-operated lift trucks. Do not label the whole publication as legislation. The inspection passage in L117 paragraph 162 is guidance: it advises the operator to check the lift truck at the beginning of each shift, follow the vehicle handbook and document the results.
| Jurisdiction and equipment | Authority type | Examination approach | Scope boundary |
|---|---|---|---|
| US industrial trucks within 1910.178 scope | Binding federal regulation | Timing explained above | Check applicability to the equipment |
| Great Britain rider-operated lift trucks | L117 ACOP and guidance publication | Paragraph 162 guidance explained above | Do not relabel guidance as OSHA law |
| Other equipment or jurisdictions | Confirm the applicable current framework | Equipment-specific arrangements | No imported US timetable |
For other Great Britain work-equipment questions, consult HSE’s PUWER overview and check the applicable current legal text for scope. Use the table as an applicability screen, not as a determination that a particular asset falls within a particular framework.
Product context: risk-based overlays
Food and supplement sites may add hygiene observations connected to spillage and cross-contamination control. Pharma and device sites may review controlled-area suitability and potential packaging impact. Chemical operations may need operating-environment and substance-specific assessment. These are illustrative, site-specific planning considerations—not new universal inspection laws, GMP record mandates or determinations that equipment is suitable for a particular use.
03Train operators to recognise defects and escalate uncertainty
In the US, the training duty is set by 29 CFR 1910.178(l). Paragraph (l)(1)(i) requires the employer to “ensure that each powered industrial truck operator is competent to operate a powered industrial truck safely, as demonstrated by the successful completion of the training and evaluation specified in this paragraph (l)”, and (l)(1)(ii) requires that training to be completed before an employee is permitted to operate a truck, except for training purposes. As a recommended site practice, keep equipment-check instruction, permission to operate and permission to perform repairs as separate decisions in the warehouse training matrix. Completing inspection instruction should not itself grant either operating or repair permission. Repair authority is addressed in the defect-control section.
The inspection link is explicit. Among the truck-related topics in the initial training programme, (l)(3)(i)(J) lists “Any vehicle inspection and maintenance that the operator will be required to perform”. Paragraph (l)(3) also allows the employer to omit topics it “can demonstrate are not applicable to safe operation of the truck in the employer's workplace”, so the pre-use checklist taught should match the trucks and attachments the operator will actually use. Under (l)(2)(ii), training combines formal instruction, practical training and “evaluation of the operator's performance in the workplace”, delivered by people with the knowledge, training and experience to train and evaluate operators ((l)(2)(iii)).
Refresher training is event-driven under (l)(4)(ii): it is required when an operator has been observed operating unsafely, has been involved in an accident or near-miss, receives an evaluation showing unsafe operation, is assigned a different type of truck, or when a workplace condition changes in a way that could affect safe operation. Separately, (l)(4)(iii) requires an evaluation of each operator's performance “at least once every three years”. Missed or poorly performed pre-use checks found during audits are therefore useful evidence for the unsafe-operation and evaluation triggers, not a separate training rule.
Certification under (l)(6) is a distinct record: the employer certifies each operator has been trained and evaluated, and the certification “shall include the name of the operator, the date of the training, the date of the evaluation, and the identity of the person(s) performing the training or evaluation.” Keep that certification separate from daily inspection records; one proves competence, the other proves a specific truck was examined before a specific shift.
Practical instruction should demonstrate how to identify the correct truck and attachment, use its checklist, recognise abnormal conditions, stop an unsafe test and report uncertainty to the designated site contact. Assess these tasks through observation rather than relying solely on a completed attendance record; capture the observed task and assessment result in the training record. Use realistic defect photographs, scenarios or safely isolated equipment without asking trainees to operate unsafe equipment. These are recommended inspection-competence practices, not a statement of statutory training content.
04Run the pre-use check without creating a new hazard
Use the following as a proposed site procedure, adapted to the equipment. Start with the asset identity, fitted attachment identity, operating context and outstanding defect status. Confirm that the equipment instructions and applicable checklist version match that configuration before observations begin. An unresolved status is a reason to seek clarification, not assume availability.
Schedule examinations using the regulatory distinctions covered above. Identify any additional operator-handover checks separately as site policy. A configurable forklift pre-shift check should distinguish stationary observations from functional checks rather than present every item as one uninterrupted test.
| Check group | Example observations | Applicability or stop condition |
|---|---|---|
| Tyres and wheels | Visible damage or abnormal condition | Equipment-specific instructions |
| Forks, mast and attachment | Visible damage, security and abnormal condition | No operator dismantling |
| Hydraulic and other fluid systems | Visible leaks | No touching suspected pressurised leaks |
| Power source | Battery, connector or fuel-system observations appropriate to the truck | No intrusive servicing |
| Operator position and protective features | Condition and function where fitted | Model-specific |
| Controlled functional checks | Steering, braking, warning and lifting functions where safe | Stop if an earlier observation makes testing unsafe |
These categories are illustrative, not a complete technical inspection standard. Take acceptance criteria, technical limits and test methods from the equipment instructions; do not substitute generic wear or pressure thresholds. Before functional checks, establish a suitable clear area and follow the instructed equipment setup. Do not operate a suspect function merely to complete its checklist row.
Use explicit results: acceptable, defect observed, not applicable and not checked. Require a reason for the last two; neither should silently become a pass. Record observations rather than diagnoses—for example, “fluid visible beneath mast” rather than “seal failure.” Refer technical assessment to appropriate personnel. Uncertainty should remain visible for review, not be resolved by guessing.
Proposed workflow
Identification → status review → stationary inspection → safe functional checks → outcome recording → use when acceptable. Defect or unresolved safety concern at any stage → stop the affected sequence → record outcome → defect control → reassessment → repeat relevant checks only when safe → human-authorised use when acceptable.
The defect branch bypasses unsafe testing; it does not require completing every functional check before escalation.
- Identify equipmentConfirm asset, attachment and operating context.
- Review statusCheck unresolved defects and handover information.
- Inspect stationaryFollow the handbook; stop on safety concerns.
- Test safelyRun only checks safe to perform.
- Record outcomeSave observations, item results and operator identity.
- Control defectsPrevent use; arrange notification and corrective work.
- Confirm returnAfter correction, a designated person documents reassessment.
05Manage defects from stopped use to human-authorised return
Binding US requirements
For powered industrial trucks covered by the US rule, 29 CFR 1910.178(q)(7) prohibits placement in service when the examination shows a condition adversely affecting vehicle safety. It also requires discovered defects to be immediately reported and corrected.
If a truck is found to need repair, be defective or be unsafe at any time, 29 CFR 1910.178(p)(1) requires removal from service until safe operating condition is restored. 29 CFR 1910.178(q)(1) reserves repairs to authorised personnel.
Recommended site controls
Translate those requirements into a controlled handover within the site's forklift safety programme. The following are operational recommendations, not a prescribed OSHA workflow:
- Make unavailability visible at the truck and wherever equipment is allocated. Use site-approved physical or access controls to prevent unintended use; a dashboard status alone is insufficient.
- Notify the supervisor and responsible maintenance role. Identify the truck, observed symptom and circumstances, then link the finding to corrective work and any relevant deviation record.
- Escalate uncertain safety implications for competent assessment. Do not let an operator improvise a lower severity rating simply to keep the truck available.
- After correction, have a designated person record the reassessment and return-to-service decision, including who decided, when, and the basis for acceptance.
Closing a maintenance ticket alone is not the site's acceptance criterion. The designated person should confirm that the corrective work addresses the reported condition and that appropriate reassessment supports return. Keep the unavailable status in place until that human decision is recorded and communicated to those allocating or operating the truck.
06Keep an inspection record that supports a defensible decision
Design the record to reconstruct what was checked, what was found and who made the resulting decision. The following is a recommended evidence set, not a universal statutory format or signature method.
| Record content | What it helps establish |
|---|---|
| Asset and attachment identity | Which truck and fitted attachment the inspection covered. |
| Checklist version | Which questions and acceptance criteria applied at that event. |
| Operator identity; shift or inspection event | Who performed the check and which operating period or event it covered. |
| Actual start and completion times | When checking occurred, rather than when someone entered or uploaded the record. |
| Item-level results and observations | What was examined, including failed, unperformed or inapplicable items and explanations. |
| Overall outcome and defect references | The inspection conclusion and traceable links to findings requiring action. |
| Subsequent reassessment or return decision | Who decided what, when, and on what basis after the original inspection. |
Preserve the sequence of events
Preserve original observations when correcting a record. Identify the correction, its author, time and reason using attributable recording. Keep inspection times distinct from entry or upload times, especially for delayed entries. Link photographs to the relevant observation where useful; a photograph does not prove that every check occurred. These controls support data integrity on paper or electronically.
Use a documented site retention schedule informed by applicable obligations and business needs. Apply retention and archiving principles to linked records and attachments rather than assigning an unsupported universal duration.
Reference data model
Equipment → Inspection through asset_id; Inspection → ChecklistVersion; Inspection → multiple ItemResult records; finding → DefectAction → corrective work and human return decision.
This vendor-neutral reference model is not an application database specification. Keep later actions linked to the original finding without overwriting the inspection outcome, so reviewers can follow the decision sequence.
Equipment
Identifies the truck and fitted attachment.
- asset_id
- equipment_type
- attachment_id
- location_id
- availability_status
Checklist Version
Preserves the applicable questions and revision.
- checklist_version_id
- equipment_type
- effective_from
- item_ids
Inspection
Records who checked which truck and when.
- inspection_id
- asset_id
- checklist_version_id
- operator_id
- shift_id
- started_at
- completed_at
- outcome
Item Result
Holds one response and its supporting observation.
- inspection_id
- item_id
- result
- observation
- evidence_ref
Defect and Corrective Action
Links repairs and human-authorised return to the finding.
- defect_id
- asset_id
- inspection_id
- work_order_id
- repair_notes
- reassessment_result
- authorised_by
- returned_at
07Connect inspection, maintenance and production without losing control
Assign one authoritative system or controlled record to each information type. The following are vendor-neutral design recommendations, not legal requirements or claims about a particular product’s integrations. Define these boundaries before configuring MES–CMMS integration:
- Equipment identity: use an asset register with a stable identifier carried into every inspection, work order and production reference.
- Inspection outcome: designate the controlled inspection record as the authority for findings and completion.
- Maintenance work: designate the CMMS or controlled maintenance log as the authority for repair activity and outstanding work.
- Equipment availability: designate a controlled status record, with named decision owners and rules for resolving inspection and maintenance findings.
Define explicit transitions between inspection pending, available and unavailable, including who may authorise each change and what evidence is needed. A production-system copy of status should not silently overrule an unresolved inspection or maintenance finding. Closing a work order should not, by itself, change availability.
During an outage, use controlled paper or another approved fallback. Preserve actual inspection times separately from later entry or transmission times. On recovery, reconcile duplicate events and investigate conflicting status updates; do not reopen equipment solely because a delayed “available” message arrives. Treat unknown or stale availability conservatively as not available for assignment until the responsible person resolves it. Test recovery with delayed, duplicated and out-of-order messages before relying on the interface.
08Failure modes that make completed checklists unreliable
A completed form can conceal an inspection that never established the truck’s condition. Use this qualitative failure-mode review as operational practice, not as a ranking of incident frequency.
| Failure mode | Why the record becomes unreliable | Control |
|---|---|---|
| Wrong truck selected | Results attach to another asset. | Confirm physical asset identity against the record. |
| Reused checklist answers | Current conditions are not observed. | Require a fresh inspection event. |
| Unsuitable generic form | Attachment or power-source risks are omitted. | Maintain applicable checklist variants. |
| Not-checked recorded as acceptable | Incomplete work appears complete. | Separate acceptable, defective, not-checked and not-applicable response states. |
| Cosmetic ticket closure | Correction lacks supporting reassessment. | Use the return decision described above. |
Supervisory review should sample observation quality and decision quality, not merely the presence of a tick or signature. During a shop-floor observation, compare what the operator examines with what the record says, and ask how an uncertain finding would be handled. Include apparently routine checks in the sample rather than reviewing only reported defects.
Avoid incentives that reward zero reported defects or unrealistically short checks. Repeated identical answers, unusually brief completion times or sudden drops in defect reporting can guide exception-based review. These patterns are review signals, not proof of misconduct: discuss the circumstances before drawing conclusions about the operator or changing the workflow.
09Measure safe decisions, not just checklist completion
For site reporting, define an inspection event as one scheduled truck/check occasion; a recurrence as the same coded finding returning after closure; and an unavailable truck as one not ready for its planned task at the observation time. Fix populations and reporting periods before calculating rates. These are proposed operational measures, not regulatory thresholds.
| Measure | Calculation or definition | Interpretation limit |
|---|---|---|
| On-time inspection completion | Events completed by the site's applicable deadline ÷ events due | Not a measure of condition. |
| Ready-for-use proportion | Available trucks ÷ planned trucks at a stated time | Not a universal compliance score. |
| Unresolved-defect age | Elapsed time since reporting for each open finding | Review by safety significance, not average alone. |
| Repeat finding rate | Recurrences ÷ relevant inspections over a defined period | Requires consistent defect coding. |
| Reconciliation backlog | Count of records awaiting resolution | Separate information delay from inspection delay. |
Report incomplete and cancelled events explicitly, including their denominator treatment. Keep actual completion timestamps separate from ingestion timestamps, as illustrated in the worked cases. Apply this distinction when reviewing contemporaneous recording and investigating apparently late records.
10Three worked cases across regulated manufacturing environments
These hypothetical cases use assumed figures, not customer outcomes. Each separates the inspection event from the operational decision it supports; the percentages answer different questions and should retain their stated denominators.
Case 1: Food warehouse—completed does not mean available
Assume 10 trucks are planned for one operating period and all 10 inspection events are completed. Two trucks have findings treated as safety-affecting and follow the defect-control process above. Assume the remaining eight trucks are available at the dispatch decision point. The units are trucks and inspection events.
Inspection completion is 10 / 10 × 100 = 100%; truck availability is 8 / 10 × 100 = 80%. Dispatch updates the production schedule board, reallocating movements only to available trucks suited to the loads and routes. Work that cannot be accommodated is delayed or rescheduled. A completed inspection on either unavailable truck records a decision against use, not permission to dispatch it. Nor does 80% truck availability establish 80% handling capacity: truck capabilities, travel distances and operator coverage may differ.
Case 2: Continuous pharma warehouse—inspection time versus upload time
Assume five trucks are already in established service and three shifts fall within a defined 24-hour reporting window. Using the after-shift cadence discussed above gives 5 × 3 = 15 inspection events; pre-service examination is managed separately. All 15 events are documented on time through the site’s controlled process. Twelve records meet a separately assumed upload target; three arrive 20 minutes after that target. Units are trucks, shifts, events and minutes.
Inspection timeliness is 15 / 15 × 100 = 100%; upload timeliness is 12 / 15 × 100 = 80%. Reconciliation matches each delayed upload to its original controlled record, truck identity and shift, retaining the actual examination and upload times. A process event log can provide a useful reconciliation structure. The reviewer records the delay explanation without backdating. Here, late upload is an information-transfer issue, not evidence of a missed examination. If an original record cannot be reconciled, investigate that uncertainty rather than assuming this example’s conclusion applies.
Case 3: Chemical tote transfer—possible contact is not proven contamination
Assume eight tote movements, each involving a different tote, are logged between 09:00 and 11:00. A hydraulic leak is first observed at 11:00, and the truck enters the defect process above. During a separate product-impact review, three of those eight totes are identified as having possible exterior contact. Units are tote movements and clock times.
The proportion flagged for possible exterior contact is 3 / 8 × 100 = 37.5%, not a contamination rate. Review packaging condition, contact evidence and movement history through the site’s spillage and cross-contamination controls. Discovery at 11:00 does not establish when the leak began, so consider whether the review window needs extending. Exterior contact alone does not prove that contents were contaminated. Equipment return and product disposition remain separate human decisions, supported by their respective assessments.
11Implementation and review checklist for a workable inspection programme
Use this proposed site-owned sequence to deploy the controls described above. It is not a statutory checklist or certification scheme.
Before deployment
- Inventory equipment and attachments; use “What MHE inspection covers” to define boundaries.
- Resolve jurisdiction and equipment scope using “Regulatory mapping”.
- Assign programme ownership, including responsibility for unresolved actions.
- Align checklist variants with equipment instructions; follow the execution section.
- Define inspection events and scheduling using the regulatory mapping and execution sections.
- Establish practical operator instruction using the operator-training section.
- Document defect escalation and human return-to-service authority using the defects section.
- Configure records and fallback arrangements using the inspection-records and design sections.
- Test reporting with representative operators, supervisors and maintenance users before rollout.
During programme review
- Sample physical condition against recent inspection records.
- Trace one finding through corrective work and reassessment.
- Test an outage and a duplicate-record scenario against the design arrangements.
- Inspect KPI denominator quality using the measures defined above.
- Review after equipment, attachment, operating-environment or incident-related changes; connect resulting revisions to change control.
Choose review frequency through site risk assessment, not a universal interval. Record the rationale and outstanding risks in the quality risk register, with owners and follow-up dates.
Frequently asked questions
Q.How should checks be scheduled for a forklift used only occasionally?+
As site practice, schedule the check around the next intended use rather than relying on the last completed checklist. Identify trucks returning from storage so the operator can check for deterioration, leaks and battery condition before starting work. Keep pre-use checks separate from servicing: UK HSE guidance in L117 paragraph 163 recommends consulting the manufacturer about maintenance regimes for seldom-used trucks. A CMMS can help organise those servicing dates independently of operating hours.
Q.Does a change of operator mean another inspection is needed?+
Distinguish a shift change from a mid-shift handover. UK HSE guidance in L117 paragraph 162 recommends an operator check at the beginning of each shift, following the vehicle handbook and documenting results. For a mid-shift change, set a site handover rule covering the existing inspection, newly reported damage and any intervening impact or abnormal behaviour. Use the shift handover report to communicate changes; an earlier signature should not replace the incoming operator’s assessment of current condition.
Q.Who should set inspection-record retention periods, and on what basis?+
Assign ownership jointly to site safety, maintenance and records management, with quality involvement where inspection records support product investigations. As records-management practice, base the period on applicable legal obligations, insurer or contractual conditions, incident-investigation needs and links to maintenance history. Document which record categories the schedule covers and suspend routine disposal when an investigation or legal hold applies. Do not automatically copy the retention period for batch records; use a defined retention and archiving process.
Q.Can a paper checklist be used when the inspection system is offline?+
A practical contingency is a controlled paper checklist under an approved outage procedure. Include the truck identifier, checklist version, actual inspection date and time, inspector, findings and any operating restriction. Make defect information available immediately rather than waiting for system recovery. When service returns, reconcile the paper records, identify any transcription and preserve the original according to the site procedure. Apply attributable recording so reviewers can distinguish who inspected the truck from who entered the data later.
Q.What should happen if a defect is discovered halfway through a shift?+
As a site response, stop the task safely and report the defect promptly; do not wait for the next scheduled checklist. If safe operation is in doubt, prevent further use pending competent assessment. Record the symptoms, truck identity, time and any load or location needing attention. Use an equipment hold tag or equivalent visible control, supported by the site’s isolation arrangements. The designated responsible person should confirm the disposition and any return-to-service checks before the truck is used again.
Q.Is permission to operate a forklift the same as authorisation to repair it?+
No. UK HSE guidance in L117 paragraph 164 says operators should not perform repairs or adjustments unless suitably qualified and authorised. Translate that distinction into the site’s warehouse training matrix: identify who may inspect, report defects, perform specified maintenance and approve return to service. Define any permitted operator tasks explicitly rather than treating driving permission as general maintenance authority. A driver who notices a loose component should report it, not assume tightening it is an authorised task.
Q.Can one checklist cover a powered pallet truck, a manual pallet jack and a forklift?+
One controlled template can work as site practice if it branches by equipment type and configuration. Share identification and defect-reporting fields, then provide relevant checks: load wheels and lowering controls for a manual jack; battery connections and fitted travel-safety devices for a powered pallet truck; mast, chains and fitted attachments for a forklift. Build each branch from manufacturer instructions. Within standard work, prevent irrelevant items from defaulting to ‘pass’ and distinguish ‘not fitted’ from ‘not checked’.
Q.Can a truck pass its safety inspection but still be unsuitable for a hygiene-controlled area?+
Yes. As a site-control distinction, mechanical safety and hygiene suitability answer different questions. A truck may function correctly yet carry soil on its wheels, residues from another handling area or debris on load-contact surfaces. Define area-entry criteria around the product and contamination risks, including cleaning status, permitted routes and dedicated equipment where appropriate. Link these decisions to spillage and cross-contamination control. Record hygiene restrictions separately so a safety pass is not mistaken for permission to enter every production area.
Primary sources
Want to see how MHE Daily Inspection could fit into your own records and workflows? Explore the related V5 pages or talk to our team about what applies to your operation.
