ImpactMulti-Agency Environments

Coordination that never asks an authority to stop being one.

When several institutions work toward one objective, the tempting shortcut is to pool everything — one database, one login, one blurred authority. The durable form of impact is the opposite: each authority keeps its mandate, permissions, records and accountability, and coordination happens through defined, controlled exchange.

The hard constraint

A shared objective does not create shared authority.

Each participating institution answers to its own mandate and its own law. Its records are its records; its permissions are its permissions; its accountability cannot be delegated to a committee. Any system that treats coordination as data pooling has already violated the environment it was meant to serve.

The engineering answer is bounded coordination: information moves only through defined relationships, handoffs are explicit and recorded, visibility is shaped by role and authority, and an exception goes back to the institution that owns it — not into a shared pile.

Coordination without erasure

Boundaries hold. The work still moves.

Three bounded authorities, drawn conceptually. Each keeps what makes it an authority. Between them, defined exchange points let a request move under control; an exception returns to its owner; and a shared picture of status emerges beneath — without any domain giving up its records or its say.

Authority A

  • Its mandate
  • Its records
  • Its permissions

Authority B

  • Its mandate
  • Its records
  • Its permissions

Authority C

  • Its mandate
  • Its records
  • Its permissions

Shared status

One coordinated picture of where the work stands — produced by controlled exchange, not by merging records or authority.

The bounded-coordination model, drawn conceptually. Three authorities each keep their mandate, records and permissions inside their own boundary. Defined exchange points on each boundary are the only places information crosses; a request moves through those handoffs under authorization, and an exception is returned to the authority that owns it rather than absorbed. Beneath the domains, a shared status emerges — coordination the participants can all see — without any record, permission or authority being merged. The boundaries hold from the first state to the last.

What bounded coordination requires

The boundary is not an obstacle. It is the design input.

  • Explicit handoffs

    Where responsibility passes between institutions is defined, authorized and recorded — never assumed or informal.

  • Role-aware visibility

    What each participant sees follows their authority and role — shared visibility is shaped, not total.

  • Records that keep their owner

    Each institution’s records remain its own, with cross-boundary exchange leaving its own accountable trace.

  • Governance that outlasts the participants

    Institutions reorganize and people change; the coordination model is governed so the boundaries and rules survive that change.

The evidence boundary

The model here is conceptual. Deliberately.

CREA-KO’s record includes multi-agency environments where information and processes cross institutional boundaries — stated at the level each relationship permits on the Impact record. What this page does not do is depict any real institutional arrangement: the domains above are illustrative, no agencies are named or implied, and no operational structure is reproduced. That restraint is part of how this kind of work is done at all.

Describe the authorities and the objective between them.

Where mandates meet, the system has to respect every one of them. That is an engineering discipline — and the place this conversation starts.