LearnGrokUse these prompts to turn loose inspection material into a controlled audit record. They are for operations managers who need site managers to act on facilities, safety or multi-site standards findings, then show what was done.
Start with the evidence, not the action list. Inspection notes often mix facts, assumptions and requests. Photographs can confirm a condition, but only if they are labelled well enough to connect them to an area, asset and finding.
Key point
Keep evidence separate from decisions
A photograph or note supports a finding. It does not, by itself, prove who owns the fix, what deadline applies or that an action is complete.
Run the prompts in order
Extract the findings register. Paste the inspector's notes and a photograph index into the first prompt. If images are uploaded, keep their filenames or photo numbers in the output. This gives every observation a stable
FIND-ID before wording changes during review.Compare earlier actions. Use the reconciliation prompt with the last action register. This is where you find actions that were marked complete without evidence, actions that are still relevant, and new findings that look similar to old ones but are not necessarily the same issue.
Build the live checklist and action register. Give the third prompt your confirmed owner roles and any internal due-date rules. It produces two different documents: the checklist records what was inspected, while the action register records what must happen next. Do not combine them. A failed check may create an action, but a check is not evidence that an action was completed.
Record decisions that need authority. Use the decision log where a finding has competing remedies, a temporary control, an acceptance decision, or an escalation requirement. The log should show who made the choice and what evidence will allow closure.
Create the review pack. Run the final prompt after checking the records. It gives the next review meeting one view of urgent items, open actions, pending decisions and missing evidence.
Note
Use your own standard references
Paste the relevant internal procedure, inspection criterion or maintenance rule when you have it. The model can organise supplied requirements, but it cannot establish which standard applies at your site.
Prepare the material before pasting
Give the prompts inputs that another manager could understand without attending the inspection. The minimum useful set is:
- Site name, inspection date, inspection scope and inspector.
- Notes with a location, asset or room reference for each observation.
- A photograph index, such as
IMG-014, loading bay fire door, south elevation. - The prior action register, including status, owner, due date and any completion evidence.
- A role-to-area list, for example facilities manager, site manager, cleaning contractor manager or regional operations lead.
- Any existing rule for priority, target dates, escalation or review frequency.
Remove personal details that are not needed to allocate and verify work. If an image includes people, sensitive access arrangements or unrelated customer material, use a redacted copy or describe the relevant condition in the photograph index.
Watch out
Do not convert uncertainty into a low priority
An unclear photograph, missing asset identifier or unknown requirement is an evidence gap. It needs a question or a verification task, not an arbitrary risk rating or closure decision.
Check the output before issuing it
Read the tables as a chain: evidence, finding, action, decision and closure proof. A break anywhere in that chain makes the audit difficult to defend and harder to complete.
Use this check before sending the pack to a site manager:
| If you see this | Check this | Do this next |
|---|---|---|
| A finding with no photo or note reference | Whether the inspection record supports it | Add the source reference or remove the unsupported claim |
| An action with a named owner | Whether that person or role was supplied | Change it to Owner to confirm if it was inferred |
| A closure claim | Whether dated completion evidence and verification exist | Move it to Complete subject to verification where evidence is incomplete |
| A due date | Whether a deadline rule or agreed date supports it | Replace an invented date with Due date to confirm |
| A high-priority item | Whether the action and escalation point are present | Add both before circulation |
Look closely for duplicated issues. The same blocked route may appear in a note, a photo caption and a prior action. Keep one primary finding, then cross-reference supporting material. Conversely, do not merge items merely because they occur in the same room. A damaged door closer and missing signage may require different owners and different closure evidence.
Check
The pack is ready when every open action has an ID, a linked finding, an owner or owner-to-confirm field, a status, and defined closure evidence.
Keep the records usable at the next visit
Store the findings register, action register and decision log together. Keep the IDs unchanged across review meetings. If you rewrite FIND-003, retain the ID and note why the wording changed. This lets you show whether the condition changed, rather than losing the history in a new spreadsheet.
The fields and output behaviour available to you can vary. Check the current xAI documentation overview before building a recurring workflow around uploads or document handling.
When the output does not work
If the result is too generic, the source material probably lacks location, asset or standard references. Add those details and rerun only the affected prompt. If owners or dates appear invented, remove the role list or deadline rule from the output, correct the input, then rerun the action register. If findings conflict, do not ask for a single answer. Keep both records, request the missing evidence and record the decision as pending until the responsible manager can verify it.
