Root cause: checking against the record

On an incident's Root cause tab, tick the causes you found first. Then press Done — check against the record: FieldTec looks at what it already holds, as it stood at the time of the incident, and asks up to five questions. Open work orders or a check that noted an issue on the equipment involved, open action items on it, earlier incidents with the same equipment or at the same site, wind recorded at the site, and an expired ticket (asked as who assigned the task and whether competency was checked).

• Each question shows what points to it and what points away. Nothing is ticked for you.
• Yes, contributed ticks the cause it names, and + Add action is there for it like any other cause. No asks why (not relevant, already covered, not enough evidence). Every question and answer stays with the investigation.
• When you tick an immediate cause, the basic causes usually behind it are offered, the job and the system first. Ticking only personal factors asks what in the job or system made them likely.
• Where the basic causes landed shows the split between job/system and personal before you sign off.
• Root cause cards: under the list, each root cause is one card read top to bottom. 1 What happened (a cause you ticked), 2 Why (an underlying cause you ticked), 3 the root cause — what was missing or wrong in the job or system — and 4 how you will fix it. Pick a why and FieldTec suggests common gaps for the root cause and suggested fixes, strongest first (change the work, then the equipment, then the rules). Tap one to fill it in, then change the words to fit. If what you write as the cause reads like a fix (“Will add…”), a note offers to move it to the fix.
• Each fix is an ordinary action item, linked to its root cause. It shows on the incident's Actions tab and in the Action Items register. A card shows Fixed once it has a fix and Needs a fix until then; Edit changes a card, and you can add more than one fix. The incident can't go for review while a root cause has no fix.
• Deleting an action item, from its bin on the root cause card or from the action itself, deletes it everywhere: the Actions tab, the register, anyone's To do, its updates and files, and the notifications about it. Who deleted it is kept on their profile under Activity.
• The worker's report (PIN) never suggests causes: it is their own account, in their own words.