Denety Consulting All articles

Intelex configuration8 min read

Corrective action due dates: why CAPA closes late

Four structural reasons corrective actions close late, each paired with the Intelex configuration that fixes it: typed due dates map to a Field Expression using DATEADD, a missing severity SLA maps to an SLA table read by FETCHVALUE, actions assigned to a location role nobody holds map to a role coverage audit, and escalation built as a trigger maps to a nightly notification schedule.Four structural reasons corrective actions close late, each paired with the Intelex configuration that fixes it: typed due dates map to a Field Expression using DATEADD, a missing severity SLA maps to an SLA table read by FETCHVALUE, actions assigned to a location role nobody holds map to a role coverage audit, and escalation built as a trigger maps to a nightly notification schedule.

A due date that lands on the 15th, the 30th or the last day of a quarter was chosen from a date widget. It was not derived from anything, and it carries no information about how urgent the action is. Plot twelve months of closed corrective actions and the clustering is visible in about a minute, which makes it the cheapest diagnostic available on a CAPA backlog.

Under that sit three more layers, all of them configuration rather than discipline: escalation that never fires because it was built as a trigger, actions assigned to a role nobody holds at that site, and closure criteria nobody ever wrote down.

The Intelex mechanics below come from Community KB articles, which render behind a login, and behavior is version-dependent. Confirm in your own environment before building.

Free

Read every article, in full.

  • Every article on the site, start to finish
  • Sources cited and linked on all of them
  • New pieces on Intelex configuration and EHS practice

Work email addresses only. Privacy.

Would rather not sign up? Email me and I will send it over.