One accountable lead.
A clear way up.
Every enterprise engagement starts with a governance plan: who is accountable on each side, how often we meet, what we report, and exactly how a problem reaches an Atlas principal.
Named counterparts
on both sides.
| Atlas | Your organization | Responsible for |
|---|---|---|
| Executive sponsor | Executive sponsor | Owns the relationship and the outcome; chairs the quarterly review; final level of escalation. |
| Delivery lead | Project or service owner | Single point of accountability for scope, schedule, budget and service levels; runs the weekly meeting. |
| Technical lead | IT or engineering lead | Owns architecture and technical decisions, code and configuration quality, and security controls. |
| Service desk | Named requesters | Day-to-day tickets and requests, triaged by severity. |
Weekly, monthly,
quarterly.
| Meeting | How often | Who attends | What it covers |
|---|---|---|---|
| Working session | Weekly | Delivery and technical leads, your project owner | Progress, the next two weeks, open issues and decisions needed. |
| Service review | Monthly | Delivery lead, your service owner | Service levels met, tickets and trends, risks, budget against plan. |
| Steering review | Quarterly | Executive sponsors on both sides | Outcomes against objectives, roadmap, commercial matters, anything escalated. |
The records
you can see.
- Status reportWeekly: done, next, risks and decisions needed, with a red, amber or green status you can forward.
- RAID logRisks, assumptions, issues and decisions, each with an owner and a date, shared with you.
- Change logEvery approved change to scope or production, with who approved it.
- Service reportMonthly: service levels, tickets, security and patch posture.
- RoadmapPlanned work for the next two quarters, reviewed at each steering meeting.
Three levels,
written down.
The governance plan names the person at each level and the time an issue may stay at a level before it moves up. You can escalate at any time; you never need our permission to go to the next level.
- 01
Level 1: Delivery lead
Any concern about delivery, quality or service. Most issues are settled here, in the weekly session or sooner.
- 02
Level 2: Technical lead and service manager
When a Level 1 issue is not resolved within the time set in the governance plan, or a service level is at risk.
- 03
Level 3: Atlas principal (executive sponsor)
When Level 2 cannot resolve it, or immediately for security incidents, contractual disputes or a missed critical milestone.
At the end of an engagement, the same governance covers the exit: a transition plan, documentation and knowledge handover, and return or deletion of your data as you direct.
The rest of how we operate.
Ask for a sample
governance plan.
We will share the governance plan, status report and escalation contacts we would use on your engagement.