Identify who requests the work, who uses its output, who supplies information and who can approve scope, spending and publication. Record responsibilities as questions to confirm rather than assumptions based on seniority. Build a small decision map that shows consultation needs, approval boundaries and an escalation route.
Ask how approval actually happens
Questions about process often reveal more than a list of job titles. Ask whether the contact can approve scope, whether spending needs another sign-off and whether legal or technical review is required before publication. Clarify whether one consolidated response will be provided or whether you are expected to reconcile separate comments. Do not assume silence from an absent stakeholder means approval.
Also identify who can reject or block an output for a specific reason. A system owner may control access even if the sponsor wants the work to proceed. An accessibility specialist may need to review an interaction. Record these dependencies with realistic notice periods. Explain any effect on schedule early, while avoiding claims that a stakeholder’s participation guarantees legal, technical or accessibility compliance.
Keep participation useful and manageable
Not everyone needs to attend every conversation. Invite people according to the question being answered and give others a clear written route to contribute. A short operational interview may be more useful than placing ten people in a general meeting. Ask whose perspective is missing, especially when the person commissioning the work does not perform the affected task or serve the people who do.
Confirm the map in a simple summary before building it into a proposal. Assign a route for unresolved disagreements and clarify who communicates final decisions. If authority changes, update the working document and explain whether previous approvals still apply. A responsibility map supports coordination, but it does not replace an agreement establishing what each party is authorized or obliged to do.
A useful map can fit into a small table: decision, accountable role, required input and response route. Keep the delivery contact in a separate field so coordination does not imply authority. Where two people share a decision, ask how they will resolve disagreement. An unresolved joint approval needs attention before a tight deadline makes the ambiguity expensive to untangle.
Fictional example: three approvals behind one contact
In a fictional project, an editor receives all messages from a programme coordinator and initially assumes that the coordinator can approve a new handbook. Discovery reveals three distinct decisions. The coordinator supplies content, the programme director approves spending and the volunteer lead confirms whether the instructions match day-to-day tasks. An external printing contact can advise on file specifications but cannot approve the editorial content.
The editor produces a decision map with one owner for each approval and a single route for consolidated comments. The coordinator remains the main contact, while the other people join only the relevant reviews. An unresolved question about publication permission goes to the director before production is scheduled. The example establishes a clearer coordination artifact; it does not claim that these fictional participants accepted terms or that the handbook was delivered successfully.
A checklist for your next step
- Map decisions before titles.
- Identify spending and scope authority.
- Confirm operational reviewers.
- Choose a route for consolidated feedback.
- Record escalation and changes.
Common questions
Should the most senior person attend discovery?
Only when their contribution is needed. Task owners and people who use the output may answer operational questions more accurately.
What if the contact does not know who approves?
Record approval authority as an unresolved dependency and agree who will identify the owner before you make commitments that require it.
Further reading
These primary resources provide related background. They do not validate the illustrative example or endorse AliveProfile.
AI-assisted drafting and automated technical checks. Examples are illustrative; no independent expert review or real-world outcome validation is claimed. Read our editorial policy.