[{"data":1,"prerenderedAt":4},["ShallowReactive",2],{"article-body-the-register-is-not-the-risk":3},"\nWhen a company misses a regulatory requirement, it is almost never\nbecause nobody knew it existed. The change had been published\nmonths earlier, an alerting service had flagged it, and someone had\nlogged it in the register. Detection worked, and detection was\nnever the problem.\n\nUnderstanding what the change affects is the problem. Nobody\nconnected it to the four work instructions, two product\nspecifications and one supplier contract it quietly invalidated,\nso each stayed in force until an auditor or an incident found the\ngap. Compliance teams do not miss changes. They miss what the\nchanges touch.\n\nThe register answers one question. What are the rules? The\nquestion that decides outcomes is a different one. What do the\nrules touch, in my company, today? That is a mapping question, and\nalmost nobody can answer it on demand.\n\n## Every failure mode is a mapping failure\n\nLook closely at how well-run compliance functions still produce\nmisses, and the same gap appears in three costumes.\n\nThe map is partial, because it is drawn by hand. Connecting a\nchanged requirement to the procedures, labels, permits and\ncontracts it affects is expert work, and when change outruns the\nhours available, \"everything affected\" quietly degrades to \"what\nthe reviewer thought of\".\n\nThe map is stale, because it is drawn once. A requirement judged\nnot applicable three years ago stays filed as such while the\ncompany enters a new market or acquires a site that makes it\napplicable. The world moved. The map did not, and nothing prompts\nanyone to redraw it.\n\nAnd the map stops at the drawing. A correctly mapped change still\nbecomes a change request, a training update and a document\nrevision cycle, and the journey to the shop floor takes quarters.\nA map that does not drive the fixes is a diagram of the exposure,\nnot a defence against it.\n\n## Regulators now audit the map\n\nThe bar is also rising, from \"show me the register\" to \"show me\nyour working\". Why does this requirement not apply to that site,\nand who signed off? To an inspector, a conclusion of\nnon-applicability without recorded reasoning looks the same as\nnever having looked.\n\nThat question can only be answered from the map. The register says\nthe rule exists. Only the mapping, with its reasoning recorded,\ncan say what the rule touches, what it does not, and who decided.\n\n## Three departments, one map\n\nChanges refuse to stay in one function. A new substance\nrestriction is at once a product compliance question, a trade\nquestion and an ESG question, and today each function discovers\nits slice independently, drawing its own partial map of the same\nchange on its own timeline.\n\nYet every function repeats the same four steps. Work out what kind\nof change this is. Find everything in the company it touches.\nCheck the documents against it. Send what fails to someone who\nowns fixing it. Draw the map once, against a connected model of\nyour products, sites, documents and suppliers, and one change\nreaches every affected corner in one pass, evidence included.\n\nTake last quarter's most significant regulatory change and ask how\nmany affected documents, products and contracts were identified,\nby whom, and where that is recorded. If the answer takes longer\nthan a day to assemble, the mapping is your gap, and closing it is\nwhat\n[the Prophesee Compliance Suite](/solutions/compliance/regulatory)\nis built for.\n[See what one change touches in your operation](/contact).\n",1786984937709]