Most AMS relationships are judged on response times, but most AMS failures are decided earlier — in a rushed handover where knowledge walked out with the incumbent. Before we accept responsibility for a landscape, we insist on a structured transition, and we recommend the same checklist even when we are not the vendor.
First, the landscape inventory: every system, client, interface, batch job and third-party bolt-on, with owners named. Undocumented interfaces are where month-one incidents live.
Second, open-item triage: every open incident, problem and change request reviewed jointly, with the incumbent, before cutover. Anything unclear gets a written status. The alternative is inheriting a backlog you cannot interpret.
Third, knowledge capture with the calendar in mind: month-end, quarter-end and year-end procedures are rehearsed on paper with the outgoing team while they are still reachable. The first close under new support should follow a script someone has already walked through.
Fourth, access and authorisation hygiene: support users, emergency access procedures and audit requirements agreed before day one — not discovered during the first priority-one incident.
A disciplined handover takes four to eight weeks. It is the cheapest insurance an IT leader can buy: the cost of doing it properly is a rounding error against the cost of a failed month-end in month two.