Institutional Mandates in Europe - Diligence Consulting

Q: How are the fees of a Mandate calibrated?

Fees are set on a case-by-case basis after Arche, once the institutional reading has made the perimeter readable. They depend on the complexity of the trajectory, the number of jurisdictions involved, the anticipated regulatory density, and the responsibilities engaged.

Each Reading reveals what the system sees before the market discovers it.

Mandates · Trajectory governance

MandatesThree governed engagements

The space between determination and exposure.

Most institutions are not rejected.
They expose themselves before their architecture holds.
Mandates govern the space between determination and exposure.

Determination establishes. Architecture transforms. Execution deploys. Governance preserves continuity.

Enter under the Arch

Arché is purchased. Mandates are authorised.

Diligence Consulting Mandates, Architecture and governed execution after Arché

Principle of access

Mandates are not purchased. They are authorised.

A Mandate is never the entry point. It is the governed continuation of a determination. Arché reads the structure. The Mandate builds it. The order is not negotiable.

The trajectory begins in France. It extends across Europe.

An institution does not commission an Architecture Mandate as one commissions a deliverable. It gains access because a prior reading has determined that its trajectory can be defended, or must be defended better.

Service does not precede diagnosis. Execution does not precede authorisation.

Arché does not determine whether a Mandate exists.
It determines which Mandate becomes necessary.

A GO may authorise deployment. A NOT YET often authorises architecture. Both may lead to a Mandate.

A common misunderstanding

The most frequent reading of a NOT YET is the wrong one.

A NOT YET does not close the trajectory.
It frequently opens its architectural phase.

Institutions often read a NOT YET determination as a refusal. It is rarely that. In most cases, a NOT YET identifies precisely what the structure requires to become defensible, and authorises the Mandate that produces it.

The objective of an Arché determination is not to reject. It is to determine the conditions under which entry remains governable. A NOT YET is the determination that opens the architectural phase. A GO is the determination that opens deployment. Both produce trajectories the House can sign.

A determination does not measure readiness. It maps which architecture remains to be built.

authorises a deployment Mandate. The architecture holds; what remains is governed execution.

NOT YET

often authorises a transformative Mandate. The architecture must be built before exposure begins.

NO GO

closes the trajectory under current conditions. The structure cannot be defended in its present configuration.

Most trajectories do not require more execution. They require more architecture.

Mandate I · The heart of the Maison

Institutional Architecture

The Transformative Mandate

The Mandate most frequently authorised after a NOT YET determination.

Trigger

A NOT YET to be reconfigured toward a defensible trajectory, or a conditional GO requiring architectural consolidation.

Function

To transform a potential trajectory into a defensible one. Governance coherence, recognition pathways, sequencing discipline, institutional legibility.

Deliverable

Documented institutional architecture, ordered regulatory sequence, framed recognition positions, controlled exposure.

Engagement

On trajectory. No exposure before architectural validation.

Three calibrated levels

Architecture EssentielleA focused reconfiguration

Architecture InstitutionnelleA complete trajectory

Architecture SouveraineA multi-juridictional structure

Each Architecture Mandate is calibrated personally after Arché. Fees are not published.

Structure before deployment.

Mandate II · The deployment that follows

Governed Execution

Trigger

A GO determination, or a closed Architecture Mandate. The structure is validated.

Function

To deploy what Architecture has transformed. Coordination, filings, sequencing, exposure control during delivery.

Engagement

On deployment. The perimeter is defined by Architecture, never beyond.

Execution Standard

Execution Complexe

Execution Stratégique

Execution carries what Architecture has transformed.

The horizon

What holds defensibility through time is not execution. It is governance.

A limited number of Governance engagements are authorised each year. They are not published.

Institutional sequence

Determination · Architecture · Execution · Exposure

Step 0, Required

Arché

Written determination. GO, NOT YET, or NO GO. No Mandate before.

Step 1

Architecture

Structure the trajectory. Make the institution readable and governable.

Step 2

Execution

Deploy under discipline. Exposure control, sequence held.

Step 3

Exposure

Visibility only after validation. Never before.

Raison d’être · I

Public commitments close doors

A lease, an announcement, a signed partnership, an executive recruitment: each public exposure creates traceability. Once visible, contradictions cannot be corrected without public cost.

Cross-border failures are almost never a single event. They are an accumulation of avoidable reversals. Architecture exists so that the sequence holds.

Raison d’être · II

Recognition timelines do not accelerate

RNCP, Qualiopi, rectoral, or European timelines rarely align with optimistic financial projections. When delays drift, capital is locked in and governance is exposed.

A sequence governed by a Mandate does not accelerate anything. It protects capital and credibility while timelines do their work.

For whom

Mandates address:

Institutions that have received a GO and wish to deploy under sequencing discipline.
Institutions that have received a NOT YET and recognise that the architectural phase is now required.
Boards whose decision engages an assignable personal responsibility.
Structures accepting sequencing discipline before public exposure.

Mandates address institutions ready to be governed, not accompanied.

Not for

Mandates are not for:

Institutions seeking operational acceleration without prior determination.
Actors wishing to bypass Arché to shorten the sequence.
Structures confusing deliverable with defensibility.

A Mandate does not replace a decision. It governs a decision already taken under reading.

Principle

Arché is purchased.
Mandates are authorised.

Arché is the only published threshold. Its fee is fixed because it is a seuil. Its value lies in what it makes possible after, not in what it produces in itself.

Mandates are different. They are not products. They are governed engagements. Their perimeter, their duration, and their depth depend on what Arché has determined. They are not priced. They are calibrated.

A Mandate is not a volume of hours. It is a governance of trajectory.

No fee is published. Each Mandate is determined personally after Arché.

Questions on Mandates

Frequent readings

Can one directly access a Mandate without first passing through Arché?

No. No exception. A Mandate is authorised by a determination, not commissioned as a service. The rule is not commercial. It is doctrinal: without a prior institutional reading, no architecture can be defensible. Bypassing Arché weakens the trajectory before it even begins. Enter under the Arch →

Does a NOT YET determination mean the trajectory is rejected?

No. A NOT YET is not a refusal. It is a determination that the current structure cannot yet be defended under public exposure, and identifies what the architectural phase must address. In most cases, a NOT YET authorises a Mandate I, the Transformative Mandate. Its function is precisely to build what was missing for the trajectory to become defensible.

How are the fees of a Mandate calibrated?

Fees are set on a case-by-case basis after Arché, once the institutional reading has made the perimeter readable. They depend on the complexity of the trajectory, the number of jurisdictions involved, the anticipated regulatory density, and the responsibilities engaged. They stand in the register of institutional mandates with strong engagement, never in that of time-based consulting.

What is the difference between an Architecture Mandate and strategic consulting?

Strategic consulting produces recommendations. An Architecture Mandate produces a defensible trajectory. Consulting accompanies; the Mandate engages structural responsibility over the sequence. Consulting can be multiplied; a Mandate cannot coexist with exposure drift. Architecture is not a deliverable. It is an institutional framework that holds under regulatory and reputational scrutiny.

Is there a Mandate after Architecture and Execution?

Yes, an horizon. Governance preserves defensibility through time, once the trajectory is deployed. It is not a published offer. It is authorised on a limited basis, once an institution has crossed Arché, structured itself through Architecture, and deployed through Execution. Few institutions reach this stage. None reach it before.