National Lived Experience Commission

Cross-System Intelligence · System Intersections Program

System Intersections

A service may work within its own remit while the journey across services fails. The System Intersections Program examines these boundaries as part of NLEC’s method, Experience → Evidence → Intelligence → Reform.

The core question

What happens in between?

People may move between health care, housing, justice, disability services, education and income support in the same week. Each system has a mandate, a set of rules and a way of measuring performance. The combined pathway is rarely governed as one experience.

NLEC helps decision-makers see what individual systems cannot see on their own. The System Intersections Program is an operational expression of NLEC’s cross-system analytical function: examine handovers, dependencies and shared outcomes using common questions, then make the issue and its evidence legible for further scrutiny. NLEC is establishing Cross-System Lived Experience Intelligence as a national category and building national infrastructure for cross-system evidence, intelligence, reform and accountability. The Cross-System Lived Experience Intelligence page describes the analytical lens, while the National Lived Experience Evidence Repository explains how public evidence can be connected without losing context. This work is complementary to specialist peaks: their portfolio-specific expertise is vital to understanding why an intersection works—or does not.

Accountability is a permanent function across NLEC’s method, not a fifth stage. It means making evidence, reform commitments and institutional responses visible without claiming coercive or regulatory authority.

The scenarios below are illustrative examples designed to explain the concepts. They are not presented as investigated cases, verified findings or accounts from identifiable people.

Three ways a boundary can fail

The problem is not always inside one service

These categories are lenses for asking better questions, not verdicts about any institution. An inquiry must still test the evidence, listen to affected people and identify the relevant legal and operational responsibilities.

01 / 03

Transition failures

Support ends in one setting before it begins in the next. An exit date is known, but accommodation, treatment, income or practical support has not been arranged.

An example, not a finding

Illustrative scenario: a person leaves a custodial setting with a health plan but no confirmed address. Without an address, follow-up appointments and benefit processes become harder to complete.

The reform question: Who is responsible for continuity before, during and after the handover?

02 / 03

Interface failures

Services exist, but their rules or processes do not fit together. One agency’s required document may only be available after another agency has already made a decision.

An example, not a finding

Illustrative scenario: a person seeking stable housing is asked for proof of ongoing support, while the support provider requires a stable address before completing its assessment.

The reform question: Which rule or process creates the circular barrier, and who can change it?

03 / 03

Accountability gaps

Each organisation can describe its own task, yet no one is answerable for the combined outcome. A referral can be marked complete without the person receiving support.

An example, not a finding

Illustrative scenario: a hospital sends a referral to community services, which is returned as outside eligibility. Both systems record their action, while the person is left to start again.

The reform question: Who owns the outcome when every individual step appears compliant?

The NLEC diagnostic method

Cross-System Failure Diagnostic

NLEC’s six-question editorial diagnostic for reconstructing pathways, testing evidence and locating failure mechanisms across systems. The System Failure Classification Standard (SF-1–SF-5) provides qualitative categories for describing supported mechanisms.

STEP 01

Set the scope

Name the pathway, systems and period examined, and why this boundary is relevant. Do not generalise beyond the material reviewed.

STEP 02

Reconstruct the pathway

Build a dated sequence of events, decisions, handovers and information flows before assigning a class.

STEP 03

Work through the questions

Use the six questions to identify the boundary, possible mechanism, consequences and a structural intervention.

STEP 04

Record the evidence basis

For each material statement, identify its source and date, and label it as an account, source-supported observation, interpretation or open question. State relevant limits.

STEP 05

Classify with a rationale

Apply a class only when its stated mechanism is supported by the scoped material. Record why it fits; if key facts are insufficient or unresolved, leave it unclassified and state what remains open.

STEP 06

Test and identify change

Consider plausible alternative explanations and uncertainty, then describe a structural intervention aimed at the identified mechanism—not a guaranteed outcome.

Six questions for every pathway

  1. QUESTION 01

    What happened?

    Purpose: Establish the sequence before interpreting it.

    Capture: Key dates or time markers, actions, decisions and gaps; distinguish what a person reports from what a source records.

  2. QUESTION 02

    Which systems were involved?

    Purpose: Set the cross-system boundary and the scope of the account.

    Capture: Relevant services, agencies, settings or jurisdictions, their roles in this pathway, and the period examined.

  3. QUESTION 03

    Where did responsibility transfer or disappear?

    Purpose: Locate handovers and identify who was expected to act next.

    Capture: Referrals, transfers, acceptance or refusal, named task owners, and any point where ownership became unclear.

  4. QUESTION 04

    What information did one system possess that another did not?

    Purpose: Trace what was known, by whom, and when.

    Capture: Information available, sent, received or inaccessible across the boundary; record the source and date for each claim.

  5. QUESTION 05

    What was the human or public-system consequence?

    Purpose: Describe consequences without assuming their cause.

    Capture: Reported effects and source-supported service consequences separately; note duration, limits and unresolved attribution.

  6. QUESTION 06

    What structural intervention could prevent recurrence?

    Purpose: Connect the identified mechanism to a proportionate structural change.

    Capture: The process, interface or accountability change proposed, who could act on it, and what evidence would inform later review.

System Failure Classification Standard (SF-1–SF-5)

NLEC defines the System Failure Classification Standard as an editorial standard only. It is not an Australian Standard, government-endorsed, accredited or validated instrument; it is not a scoring system, legal test or statutory investigation. These qualitative thresholds support consistent description; they do not establish prevalence, culpability, causation or outcomes.

SF-1

Access Failure

Eligibility, process or practical barriers block entry to or use of a relevant system.

Assign when: Identify an access step and evidence that an eligibility, practical, administrative, communication or channel barrier prevented or materially impeded entry or use. The mechanism is the access barrier itself, not a conflict between policy settings.

Use: Use when the main break is at a service’s entry or use point. A poor experience after access, without an access barrier, is not enough for this class.

SF-2

Transition Failure

Continuity breaks around a transfer between services, settings or systems.

Assign when: Identify a specific handover or transition and a discontinuity in information, support, plan or service continuity around it. The pathway chronology should connect the break to the transfer; a change of service alone is not enough.

Use: Use when the defining issue is continuity through a handover. If systems remain active in parallel and fail to align their work, consider SF-3 instead or as a separately evidenced class.

SF-3

Coordination Failure

Active systems fail to align interdependent work, information or timing.

Assign when: Identify at least two active systems with an interdependent task or outcome, and evidence of a material mismatch in information-sharing, action or timing. Multiple systems being involved, by itself, is not enough; ownership may be clear.

Use: Use when the central problem is ineffective joint action despite ongoing involvement. If no system accepts ownership of a cross-system task, consider SF-4 as well.

SF-4

Responsibility Failure

Ownership of a cross-system task or shared outcome is absent or contested.

Assign when: Identify a task or shared outcome requiring action across a boundary and evidence that no responsible owner was clear or accepted, or that responsibility was passed on or contested. An ineffective joint response with clear ownership points more directly to SF-3.

Use: Use when the gap is who is responsible for acting, not simply how active systems coordinate. Explain which task lacked an owner and how that is supported.

SF-5

Policy-Interface Failure

Applicable policy settings conflict or leave a gap at a system interface.

Assign when: Identify the relevant settings on both sides of an interface and explain how their interaction creates incompatible requirements, a coverage gap or no workable route. A barrier under one consistently applied rule is not, by itself, a policy-interface failure.

Use: Use when the interaction between policy or eligibility settings is the mechanism. A resulting access barrier may also meet SF-1; explain the rule interaction and the access effect separately.

For every application, distinguish a person’s account, a source-supported observation, an interpretation and an open question. Record source names and dates, scope and limits, and test plausible alternative explanations. The Cross-System Failure Diagnostic is an editorial method, not a live register, a way to submit a complaint, an adjudication process or a validated tool.

From evidence to reform

From observation to responsibility

A better response crosses the same boundaries

It is not enough to tell a person which agency to call next. Reform can require shared handover standards, compatible eligibility pathways, clearer ownership when a referral fails and measures that track continuity rather than activity alone.

For a deeper examination of one transition, read NLEC’s developing From Custody to Home investigation framework. To understand how recurring patterns might be documented without treating examples as findings, see the proposed System Failure Register framework. The Cross-System Intelligence Briefs are a separate synthesis format; Reform Watch is being developed to follow public commitments and responses over time.

For institutional discussion of a cross-system question, request a briefing. The National Contributor Network provides a consent-led route for people to express interest in contributing to appropriately scoped work.

Join freeContribute expertiseRequest an executive briefingPartner with NLECCommission NLEC