thinkhard.SI

Prompt repository Operations

Build a pre-use inspection checklist for a vehicle or piece of equipment

Operators need a short daily or pre-use checklist for a vehicle or machine that catches faults before anyone starts work.

Registry no.
OPS-029
Collection
Operations
Laid out for
Any chat model
Score
10 out of 10
Blanks to fill
8
Added

OperationsAny chat

The prompt

Score 10 of 10, Excellent

Use it when Operators need a short daily or pre-use checklist for a vehicle or machine that catches faults before anyone starts work.

  • {{equipment}}
  • {{operators}}
  • {{frequency}}
  • {{supervisor}}
  • {{manual_extract}}
  • {{requirements}}
  • {{format}}
  • {{max_items}}
Full prompt and why it works
Prompt
Build a pre-use inspection checklist for {{equipment}}, for {{operators}} to complete {{frequency}} before starting work and for {{supervisor}} to review, so faults are found and reported before the equipment is used.

The manufacturer's manual, or its inspection section:
"""
{{manual_extract}}
"""

Our own requirements (regulations or standards that apply, company rules, recent faults or incidents):
"""
{{requirements}}
"""

Where the checklist will be used (paper on a clipboard, a phone form, a tablet in the cab): {{format}}

Produce:
1. The checklist, grouped in the order an operator walks around and then uses the equipment, for example outside walk-around, cab, controls, operating test. Each item has the check, what a pass looks like, and boxes for Pass, Fail and N/A.
2. Stop items: the faults that mean the equipment must not be used until repaired, marked clearly in the checklist and also listed together at the top.
3. What to do on a fail: who to tell, how to tag the equipment out of service and where to record it, using our rules.
4. Sign-off: operator name, date, time, equipment ID, hours or mileage, and supervisor review.

Write each item as something to look at or test, for example "Tires: no cuts or bulges, tread visible across the full width" rather than "Check tires". This example shows the form only.

Keep the checklist to {{max_items}} items or fewer so it gets done properly every time, with each item under 15 words. A good checklist is one an operator can finish in a few minutes without skipping anything that matters. Use only checks the manual or our requirements support; where something seems important but neither covers it, put it in a separate list headed "Suggested additions to confirm" instead of the checklist. Do not soften or drop any check the manual marks as required. If the manual extract does not cover a section operators will need, such as attachments or the operating test, say which section is missing.

Variables

{{equipment}}
The vehicle or machine, for example "counterbalance forklift" or "delivery van".
{{operators}}
Who fills it in, for example "warehouse forklift drivers".
{{frequency}}
When it is done, for example "at the start of every shift".
{{supervisor}}
Who reviews completed checklists, for example "the shift lead".
{{manual_extract}}
The manufacturer's daily checks or inspection section, pasted or summarized.
{{requirements}}
Regulations, company rules and recent faults that the checklist must cover. Write "none" if there are none.
{{format}}
Paper, a phone form or a tablet, and whether operators wear gloves while filling it in.
{{max_items}}
The most items you want, for example 25.

Why it works

  • What good looks like. Each item says what to look at and what a pass looks like, so "check tires" can no longer be ticked without looking.
  • Length. A cap on items and words per item keeps the checklist short enough to be done properly every shift.
  • If unsure. Checks neither source supports go on a separate list to confirm, so the checklist holds only what the manual and your rules require.

How to use it

  1. Press Fill in variables and type your details into each blank. What you type stays in this browser.
  2. Copy the filled prompt into the AI tool you already use, such as ChatGPT, Claude or Gemini, or open it in the Grader or the Prompt Tester here.
  3. Before you rely on it, try it on three or four real examples. The Prompt Tester runs them all at once and shows which ones go wrong.
Use it from code

Get this prompt as JSON from the free REST API, with your own text in the blanks, or let an AI assistant fetch it through the MCP server. No key.

curl -s https://thinkhard.si/api/v1/prompts/pre-use-inspection-checklist

With the MCP server added to Claude, ChatGPT, Cursor or VS Code, call get_prompt with {"prompt": "pre-use-inspection-checklist"}, or just ask for it by name.