A Compliance Hub, and a Pipeline for What Changes Next

The problem

Two questions were hard to answer at the same time: which regulations actually apply to us, and where does the data that evidences them come from. Obligations lived in one place, the data in another, and the link between them lived in people's heads. When a rule changed, working out what it touched meant starting from scratch.

Our solution

We mapped the regulations that apply and traced where each underlying data source actually comes from, then brought both into a single compliance hub so an obligation and the data that evidences it sit together.

Above the hub runs a pipeline for new regulatory changes. When one arrives it is impact-assessed against the hub and a gap analysis follows, so the output is not a notification that something changed but a view of what needs to change because of it.

Results

• Regulations and their data sources held in one hub rather than separately
• New regulatory changes arrive through a pipeline instead of being found late
• Each change carries an impact assessment and a gap analysis of what must change
• The mapping is reusable, so the next change is assessed against it rather than from scratch

Why it worked

The mapping is the asset. Once each obligation is joined to the data that evidences it, assessing a new rule becomes a question you can answer against something, rather than an investigation you start again every time.