Integration Inventory Template

An integration inventory lists the system connections a project depends on. It keeps “we can integrate later” from becoming an untested planning assumption.

Deployed teams can fill this out by asking system owners, vendors, analysts, and program staff how data moves today and how people expect it to move in the future.

Why It Helps

Engineering uses this template to check whether each integration is available, secure, supportable, and realistic for the timeline. It also reveals where procurement, vendor contracts, data sharing, or security approvals may be the real blocker.

Copy This Template

| Integration | Source system | Target system | Data exchanged | Direction | Method today | Desired method | Frequency | Owner | Vendor involved | Security / approval need | Unknowns |
| --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- |
| Intake to case creation | Online intake form | Legacy case system | Applicant profile, documents, submission date | One-way | CSV export and manual upload | API or scheduled import | Daily | Digital services team | No | PII review | Whether legacy import supports attachments |
| Case status to notifications | Legacy case system | Notification service | Case ID, status, email, template ID | One-way | Manual email | Event or batch job | Near real time preferred | Program operations | Maybe | Email content approval | Whether notice templates are reusable |
| Eligibility check | Legacy case system | Vendor rules engine | Case facts and eligibility decision | Two-way | Nightly SFTP | Nightly SFTP or API | Nightly | Vendor manager | Yes | DPA and security review | Contract scope for API support |

Questions to Ask Without Engineering

Question	Why it matters
Does the connection exist today?	Existing connections are easier to validate than imagined ones.
Is there documentation?	Missing docs may mean vendor dependency or reverse engineering.
Who can approve access?	Technical feasibility can stall on ownership.
What data is sensitive?	Security and privacy constraints may shape architecture.
What happens when it fails?	Operational behavior matters as much as the happy path.

What to notice: the desired method is only one column. Current method, owner, approval need, and unknowns are what make the integration real enough to review.