Working artifacts
Documents that make the next decision easier.
Ce dossier est aussi tenu en français. Livrables →
The value of advisory work should remain visible after the meeting. These are the practical artifact types a mandate may include, always confirmed in scope.
Discuss the right output → These examples describe document types; the engagement confirms which are required. Each artifact carries one meaning across both languages.
01 Decision briefNote de décision
A concise record for the person approving the work. The brief states the business question, evidence reviewed, viable options, meaningful trade-offs, selected direction, accountable owner, and next review condition. It is accepted when the approver can state what was decided and what still remains open.
- Reader: business sponsor and affected owners
- Update trigger: material evidence or constraint changes
- Closure: decision accepted, rejected, or returned for more evidence
Decision registerRegistre de décisions
A controlled list of choices that still need attention. The register prevents material calls from disappearing into meeting notes. Each entry records status, owner, dependencies, evidence gap, due condition, and the meeting or authority that can close it. It is not a log of every technical task.
- Open, conditional, accepted, deferred, or closed status
- Named decision owner—not only a delivery assignee
- Reason and review trigger retained for deferrals
Priority roadmapFeuille de route prioritaire
A sequence that shows why order matters. Initiatives are grouped into now, next, and later with dependencies, internal effort, decision gates, and review points. Budget ranges appear only where scope supports them; unknowns remain visible instead of being converted into false precision.
- Foundation and obligation before attractive change
- Internal capacity shown beside provider effort
- Stop and acceptance conditions for near-term work
Responsibility mapCarte des responsabilités
A practical boundary between leadership, staff, and providers. The map states who approves, supplies evidence, performs work, verifies completion, and owns the system afterward. A provider receives only the context relevant to its scope; the map does not transfer executive accountability or grant access by default.
Bilingual decision recordTrace de décision bilingue
Shared meaning without creating two competing versions. A bilingual output can explain the recommendation and responsibilities in both languages while preserving exact contract, licence, or product terms in their source language. The mandate identifies the reference wording when precision matters and the owner who resolves any ambiguity.
Handoff setEnsemble de transfert
Enough context for the next owner to continue safely. Depending on scope, handoff can combine the accepted decision, open questions, responsibility map, next review, and implementation constraints. The receiving owner confirms acceptance. Runbooks, configuration records, or implementation instructions are included only when explicitly scoped.