Define measurement mechanism for standards compliance, logging and reporting

[edhamiltonHO]

From discussion raised in Slack by @willhiorns

How will we know whether a standard is being met?

I suspect that without a data push from within the delivery team we'll not be able to collate the information across the estate.

So the user of the standard needs to know what to do to meet the standard, and how to record whether it is met. That log of "standards met" informs the registers and heatmaps.

I think it needs to be logged by the user for later reference because log events will be spread through time, we won't test and verify all standards at the moment of the assurance gate. The snapshot summary of current state is what gets governed.

We need to define an approach to this, preferably something straightforward that can be managed in a single piece of guidance/standard, depending on the needs of people that will consume registers or other aggregate reports.

[edhamiltonHO]

This issue has been raised in internal Slack (or similar variant of), where a user wants to take the whole of SEGAS as document for dissemination/baselining (or some other purpose that has not yet been fully defined).

Think we might benefit from a downloadable table/document of standards and requirements that can be used as a checklist by teams, maybe principles and patterns too.

Possible that versioning that document would have benefit as well, could consider a release process to do that.

[mikewaldnerscottwork]

Hi @edhamiltonHO / @willhiorns
Can we have a call on how to ensure that #315 covers this? If the scope is wider, we can perhaps merge the 2 open issues. Eager to ensure we address all concerns around this area together.
I'm on A/L this week, but back on 3rd March. Happy to discuss when it works for both of you.