The demands and breakdowns the Framework has to answer for.
A framework is only as good as the problems it can actually examine. This page collects the situations, unresolved demands and open questions that the Framework must be able to address.
Turn a real-world breakdown into a benchmarkable question.
Examine the difference between what an organisation records, what affected people experience, and what the available evidence can support. Map the resulting challenge to the i5Benchmark Framework and identify what should be examined next.
Interactive framework demonstration Explore questions, evidence needs, responsibilities and domains through curated scenarios.
Define the situation
- Context
- Commercial serviceA commercial or public-service provider can record a complaint as completed while the original barrier, loss or harm remains.
- Stated promise or intended outcome
- The complaint has been handled and the case resolved.
- Observed breakdown
- The original problem may remain unresolved, the remedy may not have reached the person, or the same failure may recur.
- Affected people
- People using the service, and frontline staff who absorb repeat contact.
- Journey stage where the breakdown becomes visible
- Remedy
- Context
- Public serviceWhen responsibility is split across departments, agencies or contractors, people may have to repeat information, resubmit evidence and coordinate the service themselves.
- Stated promise or intended outcome
- The service will be delivered through the responsible departments.
- Observed breakdown
- The person may repeat the same account, lose time between hand-offs, receive conflicting instructions or abandon the journey without an outcome.
- Affected people
- People needing the service, particularly those with least time, language access or administrative capacity.
- Journey stage where the breakdown becomes visible
- Delivery Also affected: Response.
- Context
- Public serviceA digital or self-service process may reduce organisational cost while shifting unpaid time, troubleshooting, documentation and exclusion risk to users or frontline staff.
- Stated promise or intended outcome
- The process is faster, cheaper and easier to use.
- Observed breakdown
- Users may spend more time completing the task, repeat failed attempts, depend on informal help or lose access when an alternative channel is unavailable. Frontline staff may absorb unresolved exceptions.
- Affected people
- Users without digital access, time or confidence; frontline staff absorbing exception handling.
- Journey stage where the breakdown becomes visible
- Experience
- Context
- Technology deploymentWorkers and service users may encounter an automated system only after it has changed access, workload, monitoring or decision-making.
- Stated promise or intended outcome
- The system is approved, compliant and operating to target.
- Observed breakdown
- People may experience changed workload, monitoring, risk or access without meaningful participation, understandable explanation, usable human oversight or an effective route to challenge and correction.
- Affected people
- Workers subject to the system, and people whose cases it decides or ranks.
- Journey stage where the breakdown becomes visible
- Delivery Also affected: Response.
- Context
- Product or supply chainThe lived sustainability of a product appears in durability, repair access, spare parts, warranty practice, cost, recovery and end-of-life treatment. The purchase claim is only the starting point.
- Stated promise or intended outcome
- The product is sustainable, durable and supported after sale.
- Observed breakdown
- Repair may be unavailable, slow or uneconomic; parts may be inaccessible; warranty outcomes may not resolve the failure; disposal may replace recovery.
- Affected people
- Owners and users, independent repairers, and the communities receiving discarded products.
- Journey stage where the breakdown becomes visible
- Remedy
- Context
- Built environment and infrastructureCompletion, budget and technical compliance provide only part of the result. Accessibility, comfort, safety, actual use and maintenance determine how the project is experienced over time.
- Stated promise or intended outcome
- The project is complete, compliant and fit for use.
- Observed breakdown
- Some people may be unable to enter, navigate or use the place safely and comfortably. Problems may emerge only through actual patterns of use, maintenance or changing conditions.
- Affected people
- Disabled people, older people, children and carers; residents and workers using the space daily.
- Journey stage where the breakdown becomes visible
- Experience
- Context
- Disruption and recoveryA plan can be complete on paper while dependencies, vulnerable users, communication, reduced-service conditions, recovery and learning remain untested.
- Stated promise or intended outcome
- Critical services will continue, or recover quickly, during disruption.
- Observed breakdown
- Critical service may be unavailable or difficult to access during disruption, with unequal effects on people who have fewer alternatives or greater support needs.
- Affected people
- Users with no alternative provision, including people dependent on the service for health, income or safety.
- Journey stage where the breakdown becomes visible
- Delivery Also affected: Learning.
Describe a situation you know. The same five prompts structure any challenge, and the draft brief is assembled in your browser as you type.
Preliminary Challenge Brief
Complete the prompts above and the draft brief will appear here.
Examine the gap
Case closed
Case closed; response issued; workflow completed.
Remedy not evidenced
The original problem may remain unresolved, the remedy may not have reached the person, or the same failure may recur.
- complaint, case and closure records
- response, escalation and reopening dates
- closure reasons and remedy records
- accessibility or service tests
- accounts from affected people
- recurrence and corrective-action records
- whether closure criteria corresponded to resolution
- whether recurrence was identified and acted upon
- whether the remedy was effective in the affected person’s circumstances
The service operator holds the case, closure and recurrence records. The affected person holds the experience after closure.
The affected person, who carries the unresolved problem and the cost of escalating it, and frontline staff who absorb repeat contact.
Whether a response is evidenced is one of the things to examine. Whether an effective remedy reached the person, and whether recurrence was examined, is usually not.
Benchmark questionCan the organisation show that an effective remedy reached the affected person and that recurrence was examined?
Referral made; task completed
Referral made; departmental task completed; case transferred to the next responsible unit.
Journey coordinated by the user
The person may repeat the same account, lose time between hand-offs, receive conflicting instructions or abandon the journey without an outcome.
- referral and hand-off records
- repeat requests for the same information
- total elapsed time and waiting periods
- failed referral, abandonment and escalation records
- channel accessibility evidence
- service outcome and user account
- responsibility for gaps between organisational units
- whether the journey produced the intended outcome, not merely completed transactions
- the cumulative burden borne by the user
Each department holds its own hand-off and completion records. No single actor necessarily holds the end-to-end journey.
Service users, particularly people with complex or accessibility needs, plus community organisations that help users navigate the system.
Individual steps are evidenced. Ownership of the final outcome, and the cumulative burden, are frequently not.
Benchmark questionCan the responsible service owner show that the end-to-end journey works without transferring coordination burden to the user?
Processing time and cost reduced
Processing time reduced; transaction cost lowered; digital uptake increased.
Time and effort transferred to users
Users may spend more time completing the task, repeat failed attempts, depend on informal help or lose access when an alternative channel is unavailable. Frontline staff may absorb unresolved exceptions.
- provider processing time and cost
- user completion time
- error and repeat-attempt records
- support contacts and unresolved exceptions
- availability and use of non-digital channels
- staff workload and outcome data by relevant affected group
- distribution of savings and burdens between the organisation, staff and users
- unpaid user time and informal support
- exclusion that does not enter the completed-transaction dataset
The organisation holds cost and processing data. User time, failed attempts and informal help are largely unrecorded.
Service users, digitally excluded or time-constrained people, people requiring accessibility support, and frontline staff.
The efficiency claim is typically the evidenced side. Whether the transferred burden is evidenced is what to test, because without it the net result cannot be shown either way.
Benchmark questionDoes the efficiency gain remain positive after user time, exclusion risk and frontline workload are included?
System deployed; target achieved
System deployed; model or vendor approved; operational target achieved.
No say, and no usable route to challenge
People may experience changed workload, monitoring, risk or access without meaningful participation, understandable explanation, usable human oversight or an effective route to challenge and correction.
- purpose, procurement, design and risk records
- worker or user consultation
- change-impact and equality assessment
- human override, complaint and appeal routes
- incident and correction logs
- workload, health, safety and benefit-distribution evidence
- whether participation influenced the decision
- whether oversight is practically usable
- whether challenge and correction change outcomes
- indirect workload and behavioural effects
- distribution of productivity and financial benefits
The deploying organisation and technology supplier hold design, risk and incident records. Affected workers and users hold the experience of oversight and challenge.
Workers, job applicants, service users, supervisors, human decision-makers and groups exposed to unequal impacts.
Complaint and appeal routes may exist on paper. Whether they change an outcome, and whether learning followed, is often unevidenced.
Benchmark questionWere affected workers and users involved before deployment, and can material automated decisions be explained, challenged and corrected?
Claim substantiated at sale
Environmental claim substantiated at sale; product delivered; warranty process available.
Repair unavailable or uneconomic
Repair may be unavailable, slow or uneconomic; parts may be inaccessible; warranty outcomes may not resolve the failure; disposal may replace recovery.
- claim substantiation
- failure, return and warranty records
- repair option, completion time and cost
- spare-parts availability
- customer accounts and complaint history
- recovery or disposal records
- whether repair is practically and economically accessible
- whether the aftercare outcome is consistent with the original sustainability claim
- real-world durability across user contexts
- downstream recovery and waste effects
The producer and seller hold claim substantiation and warranty records. Repair workers and users hold what happens after failure.
Purchasers, users, repair workers, communities affected by production or waste, and people excluded by the cost or accessibility of aftercare.
A warranty process is usually documented. Whether the aftercare outcome matched the original claim is the question to put to the record.
Benchmark questionCan the sustainability claim be supported across durability, repair, warranty and end-of-life outcomes experienced after purchase?
Project completed; checks recorded
Project completed; budget and programme closed; statutory or technical checks recorded.
Some people cannot use it safely or comfortably
Some people may be unable to enter, navigate or use the place safely and comfortably. Problems may emerge only through actual patterns of use, maintenance or changing conditions.
- accessibility review and post-occupancy evaluation
- observed use and user-diversity evidence
- comfort, safety and environmental observations
- maintenance and incident records
- affected-person accounts
- complaint and corrective-action history
- reasons for non-use or avoidance
- whether corrective work resolved the experienced problem
- experience of groups not reached by formal consultation
- performance across seasons, time of day and disruption
The asset owner and operator hold completion, maintenance and incident records. Residents, visitors and maintenance staff hold the experience of use.
Residents, workers, visitors, children, older people, disabled people, maintenance staff and communities around the site.
Complaints and corrective work are recorded. Whether the correction resolved the experienced problem is frequently not established.
Benchmark questionCan the completed project demonstrate safe, accessible and comfortable use for the people affected, including maintenance and correction after occupation?
Continuity plan approved
Continuity or resilience plan approved; responsible roles named; compliance or governance checkpoint completed.
Service lost by those with fewest alternatives
Critical service may be unavailable or difficult to access during disruption, with unequal effects on people who have fewer alternatives or greater support needs.
- dependency map
- continuity plan and responsible roles
- walkthrough or tabletop exercise record
- actual incident and communication records
- continuity of critical functions
- impact by affected group
- recovery time, lessons and corrective actions
- practical accessibility of reduced service and communication
- whether lessons changed resources, responsibilities or the plan
- untested dependencies and cascading failures
- impacts on people not represented in the exercise
The continuity owner and dependency owners hold plans and exercise records. Affected communities hold the experience of losing service.
Service users, workers, suppliers, dependent communities and people especially exposed when critical functions fail.
Incidents and recovery times may be recorded. Whether lessons changed resources, responsibilities or the plan is often the missing link.
Benchmark questionCan critical functions continue or recover for affected groups, with dependencies, responsible roles and learning tested rather than merely documented?
For a situation you are describing yourself, set the organisational record against the experience of affected people, then sort the evidence into what is known, what is disputed and what is missing. The benchmark question follows from what the missing evidence prevents anyone from establishing.
Map and formulate
Challenge Brief
- Challenge title
- CH-01 · Service & Remedy
- Context
- Commercial service
- Affected stakeholders
- People using the service, and frontline staff who absorb repeat contact.
- Stated promise
- The complaint has been handled and the case resolved.
- Experienced or observed outcome
- The original problem may remain unresolved, the remedy may not have reached the person, or the same failure may recur.
- Breakdown stage
- Remedy
- Potential evidence sources
- complaint, case and closure records; response, escalation and reopening dates; closure reasons and remedy records; accessibility or service tests; accounts from affected people; recurrence and corrective-action records.
- Evidence missing or contested
- whether closure criteria corresponded to resolution; whether recurrence was identified and acted upon; whether the remedy was effective in the affected person’s circumstances.
- Responsible actors
- The service operator for closure practice; the organisation accountable for remedy and recurrence.
- Relevant Framework domains
- Human Experience · Accountability
- Relevant evidence foundations
- Normative Basis · Empirical & Technical Basis · Cultural Resonances · Lived & Local Validation
- Candidate benchmark question
- Can the organisation show that an effective remedy reached the affected person and that recurrence was examined?
- Suggested next step
- Examine closure justification against what the affected person experienced afterwards, and test whether recurrence entered a corrective action.
- Challenge title
- CH-02 · Public-Service Journey
- Context
- Public service
- Affected stakeholders
- People needing the service, particularly those with least time, language access or administrative capacity.
- Stated promise
- The service will be delivered through the responsible departments.
- Experienced or observed outcome
- The person may repeat the same account, lose time between hand-offs, receive conflicting instructions or abandon the journey without an outcome.
- Breakdown stage
- Delivery (also affected: Response)
- Potential evidence sources
- referral and hand-off records; repeat requests for the same information; total elapsed time and waiting periods; failed referral, abandonment and escalation records; channel accessibility evidence; service outcome and user account.
- Evidence missing or contested
- responsibility for gaps between organisational units; whether the journey produced the intended outcome, not merely completed transactions; the cumulative burden borne by the user.
- Responsible actors
- The commissioning authority for the end-to-end journey; each department and contractor for its own hand-off.
- Relevant Framework domains
- Human Experience · Accountability
- Relevant evidence foundations
- Normative Basis · Empirical & Technical Basis · Cultural Resonances · Lived & Local Validation
- Candidate benchmark question
- Can the responsible service owner show that the end-to-end journey works without transferring coordination burden to the user?
- Suggested next step
- Trace one complete journey end to end rather than one administrative unit, and record hand-offs, repeat requests and elapsed time.
- Challenge title
- CH-03 · Efficiency & Burden
- Context
- Public service
- Affected stakeholders
- Users without digital access, time or confidence; frontline staff absorbing exception handling.
- Stated promise
- The process is faster, cheaper and easier to use.
- Experienced or observed outcome
- Users may spend more time completing the task, repeat failed attempts, depend on informal help or lose access when an alternative channel is unavailable. Frontline staff may absorb unresolved exceptions.
- Breakdown stage
- Experience
- Potential evidence sources
- provider processing time and cost; user completion time; error and repeat-attempt records; support contacts and unresolved exceptions; availability and use of non-digital channels; staff workload and outcome data by relevant affected group.
- Evidence missing or contested
- distribution of savings and burdens between the organisation, staff and users; unpaid user time and informal support; exclusion that does not enter the completed-transaction dataset.
- Responsible actors
- The organisation deciding the channel change; the accountable owner for excluded users.
- Relevant Framework domains
- Human Experience · Responsible Innovation · Accountability
- Relevant evidence foundations
- Normative Basis · Empirical & Technical Basis · Cultural Resonances · Lived & Local Validation
- Candidate benchmark question
- Does the efficiency gain remain positive after user time, exclusion risk and frontline workload are included?
- Suggested next step
- Measure provider time and cost alongside user time and cost for the same task, and record who no longer completes it at all.
- Challenge title
- CH-04 · AI & Workplace Technology
- Context
- Technology deployment
- Affected stakeholders
- Workers subject to the system, and people whose cases it decides or ranks.
- Stated promise
- The system is approved, compliant and operating to target.
- Experienced or observed outcome
- People may experience changed workload, monitoring, risk or access without meaningful participation, understandable explanation, usable human oversight or an effective route to challenge and correction.
- Breakdown stage
- Delivery (also affected: Response)
- Potential evidence sources
- purpose, procurement, design and risk records; worker or user consultation; change-impact and equality assessment; human override, complaint and appeal routes; incident and correction logs; workload, health, safety and benefit-distribution evidence.
- Evidence missing or contested
- whether participation influenced the decision; whether oversight is practically usable; whether challenge and correction change outcomes; indirect workload and behavioural effects; distribution of productivity and financial benefits.
- Responsible actors
- The deploying organisation for participation, oversight and appeal; named decision owners for material decisions.
- Relevant Framework domains
- Responsible Innovation · Human Experience · Accountability
- Relevant evidence foundations
- Normative Basis · Empirical & Technical Basis · Cultural Resonances · Lived & Local Validation
- Candidate benchmark question
- Were affected workers and users involved before deployment, and can material automated decisions be explained, challenged and corrected?
- Suggested next step
- Test one material automated decision end to end: participation before design, the explanation given, the override used, and the correction that followed.
- Challenge title
- CH-05 · Product & Aftercare
- Context
- Product or supply chain
- Affected stakeholders
- Owners and users, independent repairers, and the communities receiving discarded products.
- Stated promise
- The product is sustainable, durable and supported after sale.
- Experienced or observed outcome
- Repair may be unavailable, slow or uneconomic; parts may be inaccessible; warranty outcomes may not resolve the failure; disposal may replace recovery.
- Breakdown stage
- Remedy
- Potential evidence sources
- claim substantiation; failure, return and warranty records; repair option, completion time and cost; spare-parts availability; customer accounts and complaint history; recovery or disposal records.
- Evidence missing or contested
- whether repair is practically and economically accessible; whether the aftercare outcome is consistent with the original sustainability claim; real-world durability across user contexts; downstream recovery and waste effects.
- Responsible actors
- The manufacturer for durability, parts and repair access; the seller for the claim made.
- Relevant Framework domains
- Sustainable Practices · Accountability · Human Experience
- Relevant evidence foundations
- Normative Basis · Empirical & Technical Basis · Cultural Resonances · Lived & Local Validation
- Candidate benchmark question
- Can the sustainability claim be supported across durability, repair, warranty and end-of-life outcomes experienced after purchase?
- Suggested next step
- Follow a failed unit through repair, warranty and recovery, and compare the outcome with the claim made at sale.
- Challenge title
- CH-06 · Buildings & Public Space
- Context
- Built environment and infrastructure
- Affected stakeholders
- Disabled people, older people, children and carers; residents and workers using the space daily.
- Stated promise
- The project is complete, compliant and fit for use.
- Experienced or observed outcome
- Some people may be unable to enter, navigate or use the place safely and comfortably. Problems may emerge only through actual patterns of use, maintenance or changing conditions.
- Breakdown stage
- Experience
- Potential evidence sources
- accessibility review and post-occupancy evaluation; observed use and user-diversity evidence; comfort, safety and environmental observations; maintenance and incident records; affected-person accounts; complaint and corrective-action history.
- Evidence missing or contested
- reasons for non-use or avoidance; whether corrective work resolved the experienced problem; experience of groups not reached by formal consultation; performance across seasons, time of day and disruption.
- Responsible actors
- The commissioning body for design intent; the operator or owner for maintenance and use.
- Relevant Framework domains
- Human Experience · Sustainable Practices · Accountability
- Relevant evidence foundations
- Normative Basis · Empirical & Technical Basis · Cultural Resonances · Lived & Local Validation
- Candidate benchmark question
- Can the completed project demonstrate safe, accessible and comfortable use for the people affected, including maintenance and correction after occupation?
- Suggested next step
- Run a post-occupancy review that reaches people not covered by the original consultation, across different seasons and times of day.
- Challenge title
- CH-07 · Continuity & Disruption
- Context
- Disruption and recovery
- Affected stakeholders
- Users with no alternative provision, including people dependent on the service for health, income or safety.
- Stated promise
- Critical services will continue, or recover quickly, during disruption.
- Experienced or observed outcome
- Critical service may be unavailable or difficult to access during disruption, with unequal effects on people who have fewer alternatives or greater support needs.
- Breakdown stage
- Delivery (also affected: Learning)
- Potential evidence sources
- dependency map; continuity plan and responsible roles; walkthrough or tabletop exercise record; actual incident and communication records; continuity of critical functions; impact by affected group; recovery time, lessons and corrective actions.
- Evidence missing or contested
- practical accessibility of reduced service and communication; whether lessons changed resources, responsibilities or the plan; untested dependencies and cascading failures; impacts on people not represented in the exercise.
- Responsible actors
- The service operator for continuity and communication; the authority accountable for essential provision.
- Relevant Framework domains
- Resilience & Adaptability · Accountability · Human Experience
- Relevant evidence foundations
- Normative Basis · Empirical & Technical Basis · Cultural Resonances · Lived & Local Validation
- Candidate benchmark question
- Can critical functions continue or recover for affected groups, with dependencies, responsible roles and learning tested rather than merely documented?
- Suggested next step
- Exercise one critical dependency to failure and record who loses service first, how they were told, and what the plan changed afterwards.
Select one of the sourced records to generate a structured Challenge Brief, or use the field list above as the template for a situation you are describing yourself.
What a challenge record contains.
Each record states the challenge, the demand or question it leaves unresolved, who and where is affected, the evidence basis available now, and which domains it engages. Competing interpretations are recorded rather than reconciled.
The Library opens with seven curated, source-informed scenarios and will expand through research and reviewed contributions.
- Challenge
- The situation as it is actually experienced, stated without attributing blame in advance.
- Unresolved demand or question
- What remains unsettled — a requirement with no accepted evidence route, a responsibility with no named owner, or a claim no one can currently test.
- Affected people and places
- Who carries the consequence, and where. Recorded specifically enough to be checked.
- Context and scale
- The sector, jurisdiction and operating conditions in which the challenge appears, and how widely it is reported.
- Related domains
- Which of the five operational domains the challenge engages, and through which requirements.
- Evidence basis and provenance
- What evidence exists now, where it came from, when, and what it cannot establish.
- Competing interpretations
- Where credible readings of the same evidence differ, both are recorded with their reasoning.
- Response pathways
- What a response would have to include to count as a response, including explanation, correction and remedy.
- Related cases
- Pilot or case records that test the challenge in a specific context, once such records exist.
- Status, date and Framework version
- The record’s own provenance: when it was written, and against which version of the Framework.
The case is closed. But has the problem been resolved?
Closing a case and resolving the underlying problem are not the same. The organisation records closure; the person experiences whether the problem has actually been resolved—and whether it returns.
- 01 Stage Promise
- 02 Stage Delivery
- 03 Stage Experience
- 04 Stage Response Case recorded as resolved
- 05 Breakdown Remedy Remedy not evidenced
- 06 Stage Learning
The journey holds until Remedy. Closure is recorded by the organisation, while recurrence is carried by the person. The question is whether a remedy actually arrived.
Case closed
Case closed; response issued; workflow completed.
Remedy not evidenced
The original problem may remain unresolved, the remedy may not have reached the person, or the same failure may recur.
- complaint, case and closure records
- response, escalation and reopening dates
- closure reasons and remedy records
- accessibility or service tests
- accounts from affected people
- recurrence and corrective-action records
- whether closure criteria corresponded to resolution
- whether recurrence was identified and acted upon
- whether the remedy was effective in the affected person’s circumstances
People using the service, and frontline staff who absorb repeat contact.
The service operator holds the case, closure and recurrence records. The affected person holds the experience after closure.
The affected person, who carries the unresolved problem and the cost of escalating it, and frontline staff who absorb repeat contact.
Whether a response is evidenced is one of the things to examine. Whether an effective remedy reached the person, and whether recurrence was examined, is usually not.
- 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
The service operator for closure practice; the organisation accountable for remedy and recurrence.
Can the organisation show that an effective remedy reached the affected person and that recurrence was examined?
Human ExperienceAccountability
Examine closure justification against what the affected person experienced afterwards, and test whether recurrence entered a corrective action.
How many times should someone have to tell the same story?
Each hand-off looks reasonable from inside one department. The cost of repetition lands entirely on the person moving between them.
- 01 Stage Promise
- 02 Breakdown Delivery Hand-offs multiply
- 03 Stage Experience Repetition absorbed by the person
- 04 Also affected Response
- 05 Stage Remedy
- 06 Stage Learning
The journey holds until Delivery. Each hand-off is defensible inside one unit. The cost of repetition accumulates only for the person moving between them.
Referral made; task completed
Referral made; departmental task completed; case transferred to the next responsible unit.
Journey coordinated by the user
The person may repeat the same account, lose time between hand-offs, receive conflicting instructions or abandon the journey without an outcome.
- referral and hand-off records
- repeat requests for the same information
- total elapsed time and waiting periods
- failed referral, abandonment and escalation records
- channel accessibility evidence
- service outcome and user account
- responsibility for gaps between organisational units
- whether the journey produced the intended outcome, not merely completed transactions
- the cumulative burden borne by the user
People needing the service, particularly those with least time, language access or administrative capacity.
Each department holds its own hand-off and completion records. No single actor necessarily holds the end-to-end journey.
Service users, particularly people with complex or accessibility needs, plus community organisations that help users navigate the system.
Individual steps are evidenced. Ownership of the final outcome, and the cumulative burden, are frequently not.
- 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
The commissioning authority for the end-to-end journey; each department and contractor for its own hand-off.
Can the responsible service owner show that the end-to-end journey works without transferring coordination burden to the user?
Human ExperienceAccountability
Trace one complete journey end to end rather than one administrative unit, and record hand-offs, repeat requests and elapsed time.
The service became more efficient. For whom?
Efficiency measured inside an organisation can be unpaid work moved outside it. The saving is real; so is the transfer.
- 01 Stage Promise
- 02 Stage Delivery Internal efficiency achieved
- 03 Breakdown Experience Time and cost transferred
- 04 Stage Response
- 05 Stage Remedy
- 06 Stage Learning
The journey holds until Experience. The saving is measured on one side of the exchange. Whether it survives once user time and exclusion are included is a separate question.
Processing time and cost reduced
Processing time reduced; transaction cost lowered; digital uptake increased.
Time and effort transferred to users
Users may spend more time completing the task, repeat failed attempts, depend on informal help or lose access when an alternative channel is unavailable. Frontline staff may absorb unresolved exceptions.
- provider processing time and cost
- user completion time
- error and repeat-attempt records
- support contacts and unresolved exceptions
- availability and use of non-digital channels
- staff workload and outcome data by relevant affected group
- distribution of savings and burdens between the organisation, staff and users
- unpaid user time and informal support
- exclusion that does not enter the completed-transaction dataset
Users without digital access, time or confidence; frontline staff absorbing exception handling.
The organisation holds cost and processing data. User time, failed attempts and informal help are largely unrecorded.
Service users, digitally excluded or time-constrained people, people requiring accessibility support, and frontline staff.
The efficiency claim is typically the evidenced side. Whether the transferred burden is evidenced is what to test, because without it the net result cannot be shown either way.
- 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
The organisation deciding the channel change; the accountable owner for excluded users.
Does the efficiency gain remain positive after user time, exclusion risk and frontline workload are included?
Human ExperienceResponsible InnovationAccountability
Measure provider time and cost alongside user time and cost for the same task, and record who no longer completes it at all.
The system is live. Who had a say — and who can challenge its decisions?
A system can be technically compliant and still leave the people it governs without a route to explanation or appeal.
- 01 Stage Promise
- 02 Breakdown Delivery System deployed
- 03 Stage Experience
- 04 Also affected Response Explanation and appeal unclear
- 05 Stage Remedy
- 06 Stage Learning
The journey holds until Delivery. Deployment is documented. Whether participation influenced the decision, and whether oversight is usable in practice, is where the account runs out.
System deployed; target achieved
System deployed; model or vendor approved; operational target achieved.
No say, and no usable route to challenge
People may experience changed workload, monitoring, risk or access without meaningful participation, understandable explanation, usable human oversight or an effective route to challenge and correction.
- purpose, procurement, design and risk records
- worker or user consultation
- change-impact and equality assessment
- human override, complaint and appeal routes
- incident and correction logs
- workload, health, safety and benefit-distribution evidence
- whether participation influenced the decision
- whether oversight is practically usable
- whether challenge and correction change outcomes
- indirect workload and behavioural effects
- distribution of productivity and financial benefits
Workers subject to the system, and people whose cases it decides or ranks.
The deploying organisation and technology supplier hold design, risk and incident records. Affected workers and users hold the experience of oversight and challenge.
Workers, job applicants, service users, supervisors, human decision-makers and groups exposed to unequal impacts.
Complaint and appeal routes may exist on paper. Whether they change an outcome, and whether learning followed, is often unevidenced.
- 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
The deploying organisation for participation, oversight and appeal; named decision owners for material decisions.
Were affected workers and users involved before deployment, and can material automated decisions be explained, challenged and corrected?
Responsible InnovationHuman ExperienceAccountability
Test one material automated decision end to end: participation before design, the explanation given, the override used, and the correction that followed.
The product was sold as sustainable. What happens when it fails?
A sustainability claim made at the point of sale is tested years later, when something breaks and repair is either possible or it is not.
- 01 Stage Promise Sustainability claim made
- 02 Stage Delivery
- 03 Stage Experience
- 04 Stage Response
- 05 Breakdown Remedy Repair route unavailable
- 06 Stage Learning
The journey holds until Remedy. The claim is tested years later, at the point of failure. Substantiation at sale says little about what happens when something breaks.
Claim substantiated at sale
Environmental claim substantiated at sale; product delivered; warranty process available.
Repair unavailable or uneconomic
Repair may be unavailable, slow or uneconomic; parts may be inaccessible; warranty outcomes may not resolve the failure; disposal may replace recovery.
- claim substantiation
- failure, return and warranty records
- repair option, completion time and cost
- spare-parts availability
- customer accounts and complaint history
- recovery or disposal records
- whether repair is practically and economically accessible
- whether the aftercare outcome is consistent with the original sustainability claim
- real-world durability across user contexts
- downstream recovery and waste effects
Owners and users, independent repairers, and the communities receiving discarded products.
The producer and seller hold claim substantiation and warranty records. Repair workers and users hold what happens after failure.
Purchasers, users, repair workers, communities affected by production or waste, and people excluded by the cost or accessibility of aftercare.
A warranty process is usually documented. Whether the aftercare outcome matched the original claim is the question to put to the record.
- 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
The manufacturer for durability, parts and repair access; the seller for the claim made.
Can the sustainability claim be supported across durability, repair, warranty and end-of-life outcomes experienced after purchase?
Sustainable PracticesAccountabilityHuman Experience
Follow a failed unit through repair, warranty and recovery, and compare the outcome with the claim made at sale.
The project is complete. Can people safely and comfortably use it?
Completion is a construction milestone. Usability is a daily condition, and it is experienced unevenly.
- 01 Stage Promise
- 02 Stage Delivery Project signed off
- 03 Breakdown Experience Use and comfort untested
- 04 Stage Response
- 05 Stage Remedy
- 06 Stage Learning
The journey holds until Experience. Completion is a moment; use is a decade. The result appears in ordinary and extreme conditions after handover.
Project completed; checks recorded
Project completed; budget and programme closed; statutory or technical checks recorded.
Some people cannot use it safely or comfortably
Some people may be unable to enter, navigate or use the place safely and comfortably. Problems may emerge only through actual patterns of use, maintenance or changing conditions.
- accessibility review and post-occupancy evaluation
- observed use and user-diversity evidence
- comfort, safety and environmental observations
- maintenance and incident records
- affected-person accounts
- complaint and corrective-action history
- reasons for non-use or avoidance
- whether corrective work resolved the experienced problem
- experience of groups not reached by formal consultation
- performance across seasons, time of day and disruption
Disabled people, older people, children and carers; residents and workers using the space daily.
The asset owner and operator hold completion, maintenance and incident records. Residents, visitors and maintenance staff hold the experience of use.
Residents, workers, visitors, children, older people, disabled people, maintenance staff and communities around the site.
Complaints and corrective work are recorded. Whether the correction resolved the experienced problem is frequently not established.
- 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
The commissioning body for design intent; the operator or owner for maintenance and use.
Can the completed project demonstrate safe, accessible and comfortable use for the people affected, including maintenance and correction after occupation?
Human ExperienceSustainable PracticesAccountability
Run a post-occupancy review that reaches people not covered by the original consultation, across different seasons and times of day.
The resilience plan is approved. Who loses service when disruption comes?
Plans describe intended capability. Disruption reveals which dependencies were unmapped and which users were treated as acceptable losses.
- 01 Stage Promise Plan approved
- 02 Breakdown Delivery Dependencies unmapped
- 03 Stage Experience
- 04 Stage Response
- 05 Stage Remedy
- 06 Also affected Learning
The journey holds until Delivery. Approval is not a test. The plan meets reality at the point where dependencies fail and some people lose service first.
Continuity plan approved
Continuity or resilience plan approved; responsible roles named; compliance or governance checkpoint completed.
Service lost by those with fewest alternatives
Critical service may be unavailable or difficult to access during disruption, with unequal effects on people who have fewer alternatives or greater support needs.
- dependency map
- continuity plan and responsible roles
- walkthrough or tabletop exercise record
- actual incident and communication records
- continuity of critical functions
- impact by affected group
- recovery time, lessons and corrective actions
- practical accessibility of reduced service and communication
- whether lessons changed resources, responsibilities or the plan
- untested dependencies and cascading failures
- impacts on people not represented in the exercise
Users with no alternative provision, including people dependent on the service for health, income or safety.
The continuity owner and dependency owners hold plans and exercise records. Affected communities hold the experience of losing service.
Service users, workers, suppliers, dependent communities and people especially exposed when critical functions fail.
Incidents and recovery times may be recorded. Whether lessons changed resources, responsibilities or the plan is often the missing link.
- 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
The service operator for continuity and communication; the authority accountable for essential provision.
Can critical functions continue or recover for affected groups, with dependencies, responsible roles and learning tested rather than merely documented?
Resilience & AdaptabilityAccountabilityHuman Experience
Exercise one critical dependency to failure and record who loses service first, how they were told, and what the plan changed afterwards.
Each scenario draws on published sources about a recognised practical challenge. Explore its questions, potential evidence sources and connections with the Framework domains.
Challenges cluster; they rarely sit in one domain.
These seven curated scenarios illustrate how practical challenges connect with Framework domains. The mappings help formulate assessment questions, identify evidence needs and guide further investigation.
| Challenge record | |||||
| · | · | · | |||
| · | · | · | |||
| · | · | ||||
| · | · | ||||
| · | · | ||||
| · | · | ||||
| · | · |
Cultural Grounding & Contextual Legitimacy applies across all five domains. It tests local intelligibility, contextual relevance, participatory legitimacy, rights compatibility and knowledge provenance for every requirement.
Select a challenge to highlight the domains it engages, or a domain to reveal the challenges connected to it.
Using the map to guide investigation.
Across the seven scenarios, Human Experience and Accountability each appear in all seven. Responsible Innovation appears where a technology or channel change is involved, Sustainable Practices where lifecycle or resource effects are material, and Resilience & Adaptability where continuity is assumed rather than tested.
Use these connections to identify which questions and evidence sources should be examined together in a specific setting. The mappings will evolve through research and reviewed contributions.
Questions the Framework cannot yet answer.
When an outcome is produced by several actors, how should responsibility be attributed without either diluting it or misassigning it?
What evidence establishes that a remedy actually reached the person affected, rather than that a process was completed?
How should unpaid time transferred to users and frontline staff be recorded, given that it is rarely measured anywhere?
What counts as adequate participation before a technology change, and who decides that it was adequate?
How should a claim be assessed when the only available evidence comes from the party making it?
When contexts disagree about what a requirement means, which disagreements indicate a framework error rather than local variation?
These are published before answers exist because a framework that hides its open questions cannot be examined. See the research agenda.