Name the responsibility first
A request for support may contain several different needs: an independent decision basis, a team to deliver a defined project, a recurring operating function or leadership with delegated authority. Choosing the form of collaboration starts with separating those needs.
Clarify the desired result, the existing internal capability, the client sponsor and the decisions that must remain with the owner or management. Then agree the people, resources and authority required. The label of the engagement should describe that arrangement, not substitute for it.
Compare four engagement forms
A development mandate addresses a defined question or project. It may produce a readiness review, a business model, an implementation plan or an agreed build programme. The scope identifies the deliverables, acceptance criteria and responsibility for the next decision.
An operating service provides a recurring function within an agreed boundary. Examples include management reporting, transformation coordination or commercial execution. The agreement defines outputs, service levels, information access, review cadence and escalation. Pricing and performance terms are separately negotiated.
A management partnership assigns defined leadership responsibilities. A named lead needs delegated authority, an agreed resource envelope and owner oversight. Reserved decisions, specialist responsibilities and the interaction with existing management remain explicit.
A joint platform creates a separately agreed business-building arrangement. Contributions, governance, economics and any ownership rights require their own agreement. A client can commission an N7X4 service without joining a platform or making an equity investment.
Separate the form from the work
ADVISE, LEAD, BUILD and OPERATE describe the kinds of work and responsibility a mandate can contain. They are not a compulsory sequence, and they are not identical to the four engagement forms. A development mandate may combine advice and project leadership; an operating service may include a small implementation workstream.
The distinction matters when scope changes. Adding ongoing operational responsibility to a project is a new commercial and governance decision. It requires appropriate capability, resources, permissions and oversight rather than an informal extension of the original brief.
Plan for review and handover
Before work starts, document who can approve changes, which measures will be reviewed and how disagreements will be resolved. Define access to information, confidentiality, the treatment of work products and the conditions for a transition or exit.
A practical review compares the agreed outputs with current evidence, decisions outstanding and the resources still required. If the arrangement no longer fits, revise it explicitly. This protects continuity and keeps accountability understandable to the people who depend on the work.
The useful outcome is a short mandate brief that a client sponsor and delivery lead can both explain: the objective, outputs, authority, resources, review rhythm and handover. Investment and regulated professional responsibilities remain separately agreed.