SOP Change Impact & Conflict Detection

The situation

A procedure revises, and nobody can say with confidence which other documents, training modules, and qualifications it just broke. The change control form has an impact assessment field, and the field gets filled in the only way it can be: from memory. Whoever processes the change writes down the documents they can think of, and the ones they cannot think of become next year’s findings.

This is not negligence - it is arithmetic. A corpus of hundreds of documents contains thousands of cross-references, and no human holds that graph in their head. So revisions ship with impact assessments that are sincere, signed, and incomplete, and the corpus accumulates broken references and silent conflicts at exactly the rate it accumulates changes.

What we deliver

A dependency map of the document corpus. Every cross-reference captured: which procedures cite which, which forms implement which requirements, which training modules teach which documents. The map that impact assessment has always assumed someone had.

Impact analysis on every revision. When a document revises, the analysis identifies what the change touches: conflicts the new text creates with other effective documents, references that just went stale or broke, and training impact - the modules and qualifications built on the steps that changed. Each finding carries a confidence level, so reviewers spend attention where the analysis is least certain rather than re-checking what is obvious.

Suggested references the revision may have missed. The analysis also runs in reverse: documents the revised procedure probably should reference but does not, offered for human review with accept and reject dispositions. The reviewer decides; the record shows what was offered and what was decided.

An Impact Assessment Report, queued for document control and QA. The output maps directly onto the impact assessment step your change control SOP already requires. This is not a new process bolted onto change control - it is the existing step, actually performed, with evidence instead of memory behind it.

A disposition log that doubles as governance evidence. Every finding, every accept or reject, every reviewer, every date. When an auditor asks how document changes are impact-assessed, the answer is a log of assessments actually conducted - which is also the documented proof of active document governance most sites wish they had.

As everywhere in this family: the platform detects, analyzes, and drafts. It never publishes, approves, or effectuates a change. Every disposition belongs to your qualified reviewers.

What changes

The impact assessment field stops being a memory test. Revisions ship knowing what they touch, training gets updated as part of the change instead of discovered stale by an auditor, and the corpus stops silently degrading with every change cycle. The question “what did that revision break?” gets an answer measured in minutes, with a record behind it.