Integration handover template
One page per production integration. Fill in the systems, records, schedule, credentials, failure modes, escalation contacts and the date someone last verified it, from what runs today rather than from the original build specification. The count of fields filled in, shown at the side, updates as you go.
How to use this template
Fill it in once per integration: download your answers, then choose Start again for the next one. Every field should describe production behaviour as observed, so where the answer is "we think" rather than "we checked", write that down and schedule a check. The example rows show the level of detail that is useful. Replace them with your own.
Fill it in below. Your result updates as you go.
Systems and direction
Fill in the entry column; the guidance column says what belongs in each field.
| Field | Guidance | Entry |
|---|---|---|
| Integration name | Example: CRM to commercial system, account and order sync | |
| Source system | ||
| Target system | ||
| Direction | One way, two way, or one way with exceptions (list the exceptions) | |
| Conflict rule for two way sync | Example: target system wins on address fields, source system wins on consent | |
| Hosting environment | Where the code runs, who owns that environment, and any known decommission date | |
| Code location | Repository or server path, and who has access | |
| Business owner | The person who notices when it stops | |
| Technical owner | The person who can change it |
Records and fields
Replace the example rows with your own.
| Record | Fields that cross | Mapped or transformed | Direction | Notes | |
|---|---|---|---|---|---|
Schedule
One row per trigger, with the example rows replaced by your own.
| Trigger | Frequency | Window | Typical volume | Watched by | |
|---|---|---|---|---|---|
Credentials
One row per credential the integration uses; the grey text shows what belongs in each column.
| Credential | Where it is stored | Owner | Expires on | How it is rotated | |
|---|---|---|---|---|---|
Failure modes and symptoms
Describe each failure as it looks from outside, not as the code sees it, replacing the example rows with your own.
| Failure mode | What it looks like from outside | How it is detected | First response | Fallback | |
|---|---|---|---|---|---|
Escalation
The three levels are filled in as a starting point; change them to match your arrangement.
| Level | Contact | Reach by | Expected response | |
|---|---|---|---|---|
This is the field that changes behaviour. A page with no verification date in the last quarter describes an integration in an unknown state, and unknown is the state that produced the emergency.
Last verified
| Last verified on | Verified by | What was checked | Next check due |
|---|---|---|---|
Prepaid support hours that do not expire.
One pool and a named responder, so the next question is a task and not a negotiation. It also works if you only need the move and your own team takes over afterwards.
Find the right AI starting point.
Align the business case, governance and first implementation—without starting a large programme.