In one sentence
Instead of re-typing an incident narrative entry by entry, paste the shift notes or attach the report and let AI propose timeline entries — you untick what's wrong, append the rest, and the record is only written when you click Save Timeline.
- The AI never saves anything. It proposes entries into the editor; the save is still your Save Timeline click, same as a hand-built timeline.
- You review every entry before it's added. All candidates arrive in a checklist — untick anything wrong, then append.
- Timestamps are taken as written in the source, never invented. Vague ones like "morning shift" are kept as text, not converted into a made-up clock time.
See AI Features & Settings for the org-level prerequisites.
Running an extraction
On an NCR's Timeline tab, click AI assist. In the dialog, provide a source — either or both:
- Paste text — shift notes, emails, a report excerpt, whatever narrative you have.
- Attach a file — Word (.docx), Excel (.xlsx / .xls), PDF, .txt, or .csv, up to 15 MB. Spreadsheets are read sheet by sheet, so an incident log kept in Excel works directly.
Click Extract timeline. AI reads the source and proposes entries classified into the timeline's own four types:
| Type | Meaning |
|---|---|
| Event | Something that happened — a trip, an alarm, a failure |
| Condition | A state that was true at the time — machine in manual mode, operator new to the task |
| Decision | A choice someone made — continue the run, skip the check |
| Action | Something someone did in response — stopped the line, quarantined stock |
Review and append
The candidates appear as a checklist, each showing its type, any timestamp found in the source, a short title, and a description. Everything starts ticked — untick what's wrong or irrelevant, then click Append.
The selected entries land in the timeline editor alongside anything already there. They're ordinary entries from that point on: edit them, delete them, attach photos. Nothing is written to the record until you click Save Timeline — closing the tab without saving discards the appended entries like any other unsaved edit.
How timestamps are handled
- Dates and times are taken as written in the source. The AI is instructed never to invent one.
- When the source gives a recognizable date/time ("2026-03-02 09:15", "13:04"), it becomes the entry's timestamp.
- When the source's wording can't be parsed as a clock time ("morning shift", "sometime after lunch"), the original wording is preserved at the start of the entry's text and the timestamp defaults to when you appended it — adjust it by hand if the ordering matters.
Prerequisites and limits
The feature is AI-gated. It requires AI enabled for your org, plus the NCR timeline import per-feature toggle, both at Admin → Organization → AI Settings (see AI Features & Settings). When a prerequisite is missing, the dialog shows the reason with a link to where it's fixed.
- File size — 15 MB per file.
- Text size — very long sources are truncated at roughly 60,000 characters; split a long report into passes if needed.
- One file per run — run the assist again for additional files; each pass appends alongside what's already in the editor.
Related
- Non-conformances — the Timeline (ECFC) section covers the editor itself
- AI Features & Settings