Engagements
An engagement is one delivery instance of a service for one customer or one internal team. It is where day-to-day work happens: hours go in, KPIs are recorded, margin is watched, risks are flagged.
What is in this section
| Page | Purpose |
|---|---|
| Engagement Overview | Sortable list of every engagement with health, margin, and status. |
| Health & Triage | Engagements that need attention now. |
| Projects & Initiatives | Project-style engagements with phases and milestones. |
| Risks & Issues | Active risk register across engagements. |
| Engagement Analytics | Deep view of a single engagement over time. |
The engagement detail page
Clicking into an engagement opens a tabbed view.
| Tab | What you see |
|---|---|
| Overview | Health score, owner, customer, contract summary. |
| Finance | Plan vs actual P&L by month, broken down by delivery party. |
| Performance | KPIs, SLA achievement, breach history. |
| Capacity | Hours by role, plan vs actual, leakage. |
| AI Usage | Token spend, model split, use cases. |
| Risks & Cases | Open and closed risks with linked decision cases. |
| Activity | Log of recordings, signals, and decisions. |
This is where check-ins happen. Operators usually live on Performance and Capacity. Service owners watch Finance and Risks. Customers see a curated subset through client portals.
How engagements connect to everything else
Almost everything in DigitalCore attaches to an engagement: stakeholders, contracts, delivery party, plans, and recorded values across Finance, Performance, Capacity, and AI Usage. That is what makes per-engagement P&L automatic.