Measure what industrial progress creates — and who it serves.

Participation & priorities

Define the tasks, roles and shifts in scope. Involve affected workers before rollout and agree which changes would be useful.

Commitment in practice

Make allocation decisions understandable and open to human review, with workers able to challenge harmful arrangements.

Potential evidence sources

Pre-deployment participation and review records, oversight arrangements, explanation and appeal records, workload data, and worker accounts.

Questions to examine

• whether affected people participated before deployment
• what human oversight exists in practice, not on paper
• how workload, pace and discretion changed for those working with it
• whether a decision can be explained to the person it affects
• whether appeal and correction exist, and whether they change outcomes
• how benefit and risk from the system are distributed

Interpretation and conflicting evidence

Compare organisational records with affected people’s accounts within the same scope and period. Record differences, evidence quality and the reasons for human judgement.

Open questions

Were affected workers and users involved before deployment, and can material automated decisions be explained, challenged and corrected?

Proposed action

Test adjustable schedules with workers; review workload and autonomy after rollout.

Responsible role

The transformation lead, with worker representatives and the manager responsible for human review.

Participation & priorities

Trace a complete journey with service users and caseworkers, including people using assisted channels. Agree which hand-offs need to change.

Commitment in practice

Give one responsible service owner oversight of the end-to-end outcome and make information requests understandable and proportionate.

Potential evidence sources

Service journey records across departments, hand-off and contractor records, elapsed-time data, abandonment points, and accounts from users and caseworkers.

Questions to examine

• how often the same information must be provided again
• how many departmental and contractor hand-offs occur
• the elapsed time from first contact to a completed outcome
• where people abandon the process, and who they are
• whether the complete service outcome was achieved, not each step

Interpretation and conflicting evidence

Compare organisational records with affected people’s accounts within the same scope and period. Record differences, evidence quality and the reasons for human judgement.

Open questions

Can the responsible service owner show that the end-to-end journey works without transferring coordination burden to the user?

Proposed action

Test a shared hand-off protocol and confirm that users know the next step and responsible contact.

Responsible role

The commissioning authority’s service owner, with departmental leads and contracted providers.

Participation & priorities

Involve users and frontline staff in testing a task before changing channels. Include people who need language, digital or accessibility support.

Commitment in practice

Assess organisational savings alongside user effort, staff workload and access to support.

Potential evidence sources

Channel and process change records, exception and failure handling data, workload records, and accounts from users and frontline staff.

Questions to examine

• whether digital or self-service change moved unpaid time onto users
• who now does the troubleshooting when the process fails
• what documentation the user must assemble and maintain
• how workload changed for frontline staff, not only headcount
• who is excluded when the alternative channel is withdrawn

Interpretation and conflicting evidence

Compare organisational records with affected people’s accounts within the same scope and period. Record differences, evidence quality and the reasons for human judgement.

Open questions

Does the efficiency gain remain positive after user time, exclusion risk and frontline workload are included?

Proposed action

Revise the most burdensome task steps and test a usable assisted alternative alongside the digital process.

Responsible role

The service transformation lead, with accessibility and frontline operations leads.

Participation & priorities

Ask owners and repairers to trace a failed product through diagnosis, parts, warranty and repair. Agree which barriers prevent continued use.

Commitment in practice

Make repair options, parts availability and total costs clear, and connect durability and sustainability claims to evidence.

Potential evidence sources

Failure and warranty records, parts availability and pricing, repair network records, recovery data, and accounts from owners and repairers.

Questions to examine

• actual durability against the claim made at sale
• whether repair is accessible, and to whom
• whether parts exist, for how long, and at what price
• how warranty terms operate in practice rather than in wording
• the total cost to the owner of keeping the product in use
• what recovery and end-of-life treatment actually happens

Interpretation and conflicting evidence

Compare organisational records with affected people’s accounts within the same scope and period. Record differences, evidence quality and the reasons for human judgement.

Open questions

Can the sustainability claim be supported across durability, repair, warranty and end-of-life outcomes experienced after purchase?

Proposed action

Test a repair journey with owners and repairers; revise unclear parts, price and warranty information.

Responsible role

The product lifecycle lead, with aftercare, repair partners and the team responsible for product claims.

Participation & priorities

Review intended journeys with users, access advisers and maintenance staff across relevant times and conditions.

Commitment in practice

Provide usable access information and assistance, and give reported barriers a responsible owner and correction route.

Potential evidence sources

Design and accessibility records, post-occupancy measurement, maintenance records, observed use, and accounts from users and local residents.

Questions to examine

• accessibility in practice for people with different needs
• thermal, acoustic and air comfort through the year
• safety at different times of day and for different users
• how the space is actually used compared with its design intent
• whether maintenance sustains the original condition
• the experience of people whose needs were not considered in design

Interpretation and conflicting evidence

Compare organisational records with affected people’s accounts within the same scope and period. Record differences, evidence quality and the reasons for human judgement.

Open questions

Can the completed project demonstrate safe, accessible and comfortable use for the people affected, including maintenance and correction after occupation?

Proposed action

Verify a step-free journey and assistance arrangements; assign corrections for the access barriers identified.

Responsible role

The building or public-space operator, with facilities management and the commissioning authority.

Participation & priorities

Map critical dependencies with service teams and affected communities. Agree which needs take priority during reduced service.

Commitment in practice

Make continuity responsibilities, accessible communication and support for dependent users explicit and testable.

Potential evidence sources

Dependency maps, incident and recovery records, communication logs, reduced-service arrangements, and accounts from affected users and responders.

Questions to examine

• which dependencies the plan maps, and which it omits
• which users depend on the service most and can substitute least
• what happens under reduced-service rather than total-failure conditions
• whether communication reaches the people affected, in time
• who owns the response while it is happening
• how recovery is achieved, and at whose cost
• whether the disruption produced durable change in practice

Interpretation and conflicting evidence

Compare organisational records with affected people’s accounts within the same scope and period. Record differences, evidence quality and the reasons for human judgement.

Open questions

Can critical functions continue or recover for affected groups, with dependencies, responsible roles and learning tested rather than merely documented?

Proposed action

Exercise one critical dependency and test how affected people receive information and alternative support.

Responsible role

The continuity lead, with service owners, dependency providers and community contacts.

Participation & priorities

Review closure criteria with affected service users and frontline staff. Agree what resolution would mean in the person’s circumstances.

Commitment in practice

Connect case closure to evidence of an effective remedy, with a usable route to reopen or escalate unresolved problems.

Potential evidence sources

Case and closure records, escalation and reopening logs, complaint and review text, and accounts from affected people.

Questions to examine

• the basis on which the case was closed, and who decided it
• what the affected person experienced after closure
• whether escalation or reopening was available, and what it cost them
• whether an actual remedy reached the person, not only a response
• whether the same problem recurred for them or for others

Interpretation and conflicting evidence

Compare organisational records with affected people’s accounts within the same scope and period. Record differences, evidence quality and the reasons for human judgement.

Open questions

Can the organisation show that an effective remedy reached the affected person and that recurrence was examined?

Proposed action

Test closure and reopening practice against the affected person’s experience and assign correction where the problem persists.

Responsible role

The service operator’s complaints lead and the manager accountable for remedy and recurrence.