> ## Documentation Index
> Fetch the complete documentation index at: https://irisdocs.prescientlabs.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Engagement Management

> Control milestones, risks, client dependencies and scope without burying a small project in unnecessary bureaucracy.

Good engagement management makes delivery predictable and keeps commercial problems visible before they become crises.

## Kickoff outputs

By the end of kickoff, confirm:

* objective;
* scope and exclusions;
* deliverables;
* timeline;
* stakeholders;
* governance;
* data and access requirements;
* success criteria;
* communication cadence.

## Use a lightweight RAID log

Track:

* **Risks:** something that may happen.
* **Assumptions:** something you are planning on being true.
* **Issues:** something already affecting delivery.
* **Dependencies:** something outside the workstream that must happen.

Each item needs an owner and next action.

## Weekly update format

Keep it short:

**Status:** green / amber / red with explanation.

**Completed:** what changed this week.

**Next:** what will happen next.

**Decisions required:** from whom and by when.

**Risks / blockers:** impact and mitigation.

## Manage scope change explicitly

A useful response is:

> We can add that. It is outside the current agreed scope, so we have three options: swap it for X, extend the timeline, or add it as a small change request. Which is most useful?

## Escalate early

Do not wait until the final week to tell the sponsor that missing data or stakeholder access has made the original timeline impossible.