AI Summaries: What They Are and How They Work
Core can write a plain-English summary of each completed job, each inspection with a finding, and each item's inspection history. What gets written, when, and the rules the AI works under.
Last updated
AI summaries turn the records your inspectors have already made into short paragraphs that a client, an authoriser or the next inspector can read in a few seconds. The AI reads the record and writes it up. It does not inspect anything, and it has no say in whether an item passes or fails.
AI summaries are a paid add-on and are off by default. To have them switched on for your account, email support@coreinspection.com.
The three summaries
| Summary | Written for | Length | Covers |
|---|---|---|---|
| Job summary | Your client | One paragraph, up to 5 sentences | How many items were inspected, passed and failed, the failures grouped by equipment type and common cause, and anything the inspector noted on passed items |
| Inspection summary | The client's site manager | Up to 3 sentences | What was examined, the recorded result, and what the inspector found or noted |
| Equipment history summary | The inspector about to examine the item | Up to 4 sentences | Past failures, repairs, parts replaced and things an earlier inspector marked to monitor, with their dates |
Here is the kind of inspection summary a failed chain hoist examination produces (illustrative, with made-up data):
The 3.2 t chain hoist (serial KR-CH-0005) failed its 6-monthly thorough examination on 2 October 2026 because its brake was slipping under load. The inspector recorded an existing or imminent danger and that the hoist is not safe to operate, and that it is to be scrapped and replaced.
When summaries are written
Core checks for newly completed jobs every few minutes. When a job is marked Complete, Core writes:
- a job summary,
- an inspection summary for each inspection on the job that failed or carries an inspector comment of its own,
- a history summary for each item on the job whose history has something in it worth reading (a past failure, or a comment that is not the same stock comment every time).
Equipment history summaries are also written ahead of a visit. When an Active job is due to start within 14 days, Core writes history summaries for that client's equipment, across all of the client's sites, so they are on the technician's device before the job starts.
Only jobs completed after the feature was switched on for your account are summarised. Older jobs are not backfilled.
If a job is changed while it is still unapproved (an inspection is corrected, a comment is added), its summaries are rewritten to match. Once the job is Approved, its job and inspection summaries are fixed.
What the AI is not asked to do
Some summaries are not written by AI at all. If every item on a job passed and nobody left a note, Core writes the sentence itself from the counts ("42 items were inspected on job 10482: 42 passed and 0 failed"). The same applies to a one- or two-item job where the only comment is one of your standard ones. Those summaries do not carry the AI-generated label, because no AI was involved.
Core works out your standard comments for itself. A comment that appears on a large share of your inspections ("Inspected and found fit for purpose", for example) is treated as a stock phrase and is not reported as a finding.
The rules the AI works under
Every summary is written under the same fixed instructions.
- It uses only what is in the record. It does not add findings, advice or opinions of its own, and it does not tell the reader what to do next.
- It never changes or softens a result. A fail is reported as a fail, in the inspector's terms. The inspector's recommendations are reported as the inspector's.
- It does not count. Core calculates every count (items inspected, passed, failed, not seen) and gives the numbers to the AI to write around.
- Every number is checked. After the summary is written, Core compares every number in it against the record. If a number appears that is not in the record, the summary is thrown away and written again. If the second attempt also fails the check, no summary is shown.
- Unclear comments are quoted, not interpreted. If an inspector's comment uses a code or abbreviation the AI does not recognise, it quotes the comment exactly.
- Failures are never left out. A failed inspection always gets a summary, and if there are more findings than fit, the summary says that further defects are recorded.
- Internal-only checklist items are left out. Anything you have marked as internal on an inspection template is not included.
Summaries are written in the language of the inspector's comments.
How AI-written text is marked
Anywhere a summary written by AI appears, it carries an AI-generated label: on the web pages, in the mobile app, on the customer portal and on any certificate or report that prints it. If an authoriser has edited the text, the label reads "AI-generated, edited by" followed by their name.
Who is responsible for the summary
The inspection record is the legal record: the checklist answers, the result, the inspector's comments and the signature. A summary is a reading aid on top of it. It is worth having an authoriser read each summary before the job is approved, and Core puts it in front of them at that point. See Reviewing and editing AI summaries.