ADM.11 - Join Providers Around the Administrative Result
Type: Architectural
Status: Stable
ADM.11:0 - Use this when
Use this pattern when you need to establish, assess or repair how several providers together supply an administrative condition to its recipient. A new colleague may have an appointment, identity confirmation and an access approval while still being unable to use the required archive.
Start where one provider depends on another. What does the receiver need for its next action, and which contribution is available? Identify the working connection and any responsibility for recovery. If the service cannot yet deliver, identify the missing contribution or undertaking and, where known, who can provide it.
Use an adequate existing connection directly. If the open question is which complete arrangement a project should use to obtain provision, use SYSE.24 with the relevant administrative conditions; this pattern supplies those conditions and identifies gaps.
ADM.11:1 - Problem frame
The practitioner is arranging contributions to a particular administrative result or a bounded class of such results. Relevant participants include the recipient, specialist decision makers, providers who perform provision, and whoever has undertaken to arrange the combined result.
The contributions can have different subjects and authorities. An appointment decision, identity result, permission grant, technical configuration and successful use remain distinct even when they concern one researcher. For the connections described in a service catalogue, establish the authority, commitments and arrangements on which this service relies.
The service owner needs enough of the arrangement to explain how the recipient’s condition will be supplied, who handles a failed join and which uncertainty prevents a promise. The account can be a short instruction or a few entries in an existing service description.
ADM.11:2 - Problem
Each provider reports completion against its local criterion. The next provider receives the wrong identifier, an expired result or a decision that does not authorize the required action. The recipient then becomes the investigator and coordinator of a service that was presented as one result.
A common form can hide the distinct decisions or move unresolved work into another queue. Conversely, duplicating every specialist function inside one service can be costly and may exceed the service owner’s authority.
ADM.11:3 - Forces
| Force | Tension |
|---|---|
| Recipient result | One usable condition may require several separately governed contributions. |
| Local competence | The receiving provider needs a usable contribution. A judgement requiring specialist competence remains with a qualified contributor. |
| Readiness | Prerequisites belong to the next action; a later result must not be demanded before the action that produces it. |
| Responsibility | Coordination, performance, ownership, permission and commitment can belong to different participants. |
| Proportion | One failed join may need one correction; an unresolved choice of a complete obtaining arrangement needs its own comparison. |
ADM.11:4 - Solution
ADM.11:4.1 - Recover the promised condition and actual undertakings
Name the recipient’s condition, scope, time and completion evidence. Recover who has undertaken to supply or arrange it and under which terms. Distinguish the desired target and expected result from what a provider has undertaken. Use OPS.13 if the promise itself needs to be established.
Identify the provider contributions needed to supply the condition or establish whether it can be supplied. Use existing assignments, permissions and adequate decisions from ADM.2–ADM.3 and ADM.8. An unassigned future provider is a proposal, not available capacity or a current undertaking.
If nobody has undertaken to resolve a combined-service failure, identify the missing assignment or commitment. Take that question to the holder of the assignment authority when known. A proposed coordinator needs an effective assignment before the service can rely on that responsibility.
ADM.11:4.2 - Inspect what each receiving action needs
At a consequential join, state the receiving action and the input it can use. Match the input to the intended participant, case, resource, configuration and effective conditions where those distinctions matter.
Use the next-action readiness rule in OPS.8. An identity check can begin when its required information, capable checker and permission are available; the identity result is an output of that action. The later grant decision may need that result. Requiring the final grant before the check would create a false circular dependency.
Read the local completion notice to see what it confirms. Check whether the receiver has the evidence, decision, resource or actual condition needed next. Retain legitimate participant descriptions and use ADM.4 or SIE when their correspondence is unresolved.
ADM.11:4.3 - Make the consequential joins executable
Where a connection is missing, identify the result the receiver needs, who can supply it, the conditions for using it and how a mismatch can be resolved. Use an adequate existing contribution, repair the connection within your authority or obtain a missing agreement or specialist result. If a necessary contribution remains unavailable, state the resulting limit on the service.
Use the existing channel when it carries the needed result. Providers may retain separate records if the receiving correspondence is adequate and the required information remains accessible under its applicable restrictions.
Distinguish transferred work from transferred responsibility. A provider may finish an assigned check while another participant retains the obligation to arrange usable access. A change to that obligation requires its actual authorized basis; forwarding the request does not supply one.
ADM.11:4.4 - Arrange continuity and recovery where failure matters
Identify the failure that can defeat the combined result: a missing specialist answer, invalid scope, delayed provider, lost correspondence or uncertain earlier effect. Identify the participant capable and authorized to resolve it, and the result the next action needs. Use the existing assignment or seek one from its holder where needed.
Keep completed contributions available within the conditions they still meet. Independent work can proceed under its own permission, as when a price inquiry is ready while booking authority is pending.
For overlapping cases, inspect relevant resource windows, priorities, repeated work and existing commitments. OPS.8 supplies operational joins and protection; OPS.12–OPS.13 supply material burden and promise questions. A shared specialist already committed elsewhere is not additional simultaneous capacity.
If the effect of an earlier attempt is unknown, use ADM.9–ADM.10 to look for evidence of the effect. If it remains unknown and another action could duplicate it, hold that action and report the unresolved condition, even if individual providers have closed their tasks.
ADM.11:4.5 - Establish what the connection supports
Use an applicable earlier check or walk a case through the contributions to establish whether the receiving provider can identify the next action. Examine a failing connection when its handling matters. For a claim about provision, use evidence that the recipient obtained the promised condition, including the recipient’s account when needed.
A description walkthrough tests the arrangement’s intelligibility. A bounded operational trial can establish actual transfer, performance and use under its observed conditions. A reliability claim needs evidence covering the providers and conditions to which it applies.
Return the usable join, its governing undertakings and limitations, or the missing provider result. If the existing arrangement cannot supply the condition and a complete obtaining choice is now live, pass these administrative facts to SYSE.24. That comparison may retain, adapt or replace the arrangement; the join diagnosis does not predetermine centralization or outsourcing.
ADM.11:5 - Archetypal Grounding
ADM.11:5.1 - Three completed contributions and a missing account correspondence
An organization undertakes to arrange Mira’s access to document D by 10:00 on 2 October. The service coordinator has the supplied assignment to resolve cross-provider gaps until that condition is established. The appointment office, identity service, authorized grant maker and archive provider retain their distinct responsibilities.
The appointment office supplies a decision effective on 1 October. The identity service returns the accepted person result for institutional identifier M. The grant maker issues a valid read grant for M and D on 2 October. The archive provider requires the corresponding account identifier to configure access.
The first three contributions are adequate within their stated conditions. The missing input is the correspondence between M and the account that will actually read D. The coordinator sends the bounded mapping question to the assigned access provider, which can recover the account binding through its authorized directory procedure.
After establishing that binding, the archive provider configures the permitted account. Mira opens D, and the available evidence supports the promised condition. The original appointment, identity result and grant remain applicable to Mira and D.
| Join | What the receiver actually uses |
|---|---|
| Appointment to grant decision | The relevant person, effective assignment and scope required by the supplied access rule. |
| Identity result to grant decision | The accepted person result for that beneficiary under the rule’s conditions. |
| Grant to archive provision | The permitted action and resource, effective time, beneficiary and supported account correspondence. |
| Archive provision to service completion | Evidence that the intended recipient can use D within the grant. |
If the provider cannot recover the mapping, the service retains that precise gap and the accountable recovery action. The coordinator’s assignment does not authorize inventing a mapping or broadening the grant.
ADM.11:5.2 - Shared provision does not establish shared capacity
Two services rely on the same specialist during a two-hour window. Each local plan assumes that the specialist is available for its full two-hour job. Together the jobs require four specialist-hours within a two-hour window.
The responsible parties use the actual service priorities and commitments to resolve the resource question. They may change timing or obtain qualified additional provision where authorized. The administrative join account supplies the affected cases, needed specialist results and obligations. A claim that a new shared-service arrangement will solve the problem remains conditional until its actual capability and timing are established.
ADM.11:6 - Bias-Annotation
The service owner can overvalue the part visible inside their own department. Follow the recipient’s use and what the receiving provider needs, including the missing input when use has failed.
An adequate direct provider arrangement may operate without another intermediary. Arrange coordination where an unresolved join requires it.
ADM.11:7 - Conformance Checklist
Recognition. The account connects the promised condition to consequential provider contributions, the receiving actions’ prerequisites and any provision for resolving a failure. If the providers cannot yet deliver the condition, the account identifies the missing input or undertaking. It distinguishes coordination from the authority and commitments of the participants.
Assurance for reliance. Use applicable observations or a bounded exercise to check the claim about the join. For an operating connection, establish that the receiver gets a usable result for the right subject and conditions. Where a mismatch can defeat the promise, check how valid earlier work survives it and who has undertaken recovery, or identify the missing undertaking. A claim about wider reliability or capacity needs evidence for that claim.
ADM.11:8 - Common Anti-Patterns and How to Avoid Them
Every department is done reports local completions while the recipient still lacks the result. Inspect the missing receiving input or usable effect.
The future output is an entry condition prevents a check from starting because its result is demanded first. Recover the prerequisites of the actual next action.
A common catalogue creates one provider substitutes publication grouping for capability and responsibility. Identify the actual contributions and obtaining relations.
ADM.11:9 - Consequences
The recipient can obtain coordinated provision with fewer unexplained returns, and providers receive narrower, usable requests. Existing specialist results can remain useful through a local failure.
The arrangement requires access to real commitments, resource conditions and recovery capabilities. It may reveal that a promised result is unsupported. The responsible parties can use that finding to reconsider the promise or how to obtain the missing contribution.
ADM.11:10 - Architectural Rationale
For each consequential connection, establish what one provider supplies, what the receiver can rely on and who has the authority and responsibility for the work. This identifies the undertakings behind the beneficiary’s result across organizational boundaries. Where a specialist judgement is needed, the receiving provider knows whose judgement it can rely on and for what.
ADM.11:11 - SoTA-Echoing
The working question is how separate providers supply one administrative condition without losing the institutional decisions and failure responsibilities between them. The June laboratory distinguishes developing this service arrangement from using it. Judge the arrangement also by the effort it requires from the participant.
SYSE.8 distinguishes ways to arrange provision. OPS.8 relates readiness to the receiving action, and OPS.13 distinguishes forecasts, objectives and commitments. GOV.UK Service Standard point 2 offers a comparison with solving a whole user problem. The authority and commitments for a particular service come from its participants and governing rules.
Use an adequate direct provider arrangement. A central portal can improve entry but does not necessarily repair result correspondence or failure responsibility. Sections 4.2–4.4 retain those joins; use SYSE.24 when choosing how to obtain the complete service.
Reopen an affected join when a provider, required input, permission, commitment, capability or recipient use changes. The examples illustrate the supplied arrangements. Establish any cost saving from the resources and work compared in the service concerned.
ADM.11:12 - Relations
ADM.1 supplies the administrative condition; ADM.2–ADM.4 supply participants, effectivity and correspondence when unsettled. ADM.5 carries reusable handling, and ADM.6 returns a provider gap to its competent resolver. The authorized providers use ADM.7–ADM.10 for needed checks, permission, provision and reconciliation.
SYSE.8 develops provider concepts, OPS.8 supplies operational joins, and SYSE.24 helps the responsible participant compare complete ways to obtain the service when that choice is needed. ADM.15 examines the resulting consequences; ADM.16 governs an actual institutional transition.