Procurement memo, architecture & residual-capacity pack

1. Problem / solution alignment

Problem. Multi-country and multi-partner programmes still run people, consent, delivery evidence, and claims across spreadsheets, email, and disconnected tools. Manual triangulation before central dashboards creates delay, audit risk, and weak residual capacity when staff turn over or projects close.

Solution. IMP is a multi-tenant decision-grade system of record — people, purpose-based consent, programmes, activities, milestones, evidence, staff expenses, and vendor invoices — under Altamont’s Implementation Integrity standard. Cleaner evidence trails reduce reconstruction risk for funders and secretariats while keeping methodology judgement with human advisors where required.

Why this matters for funding risk. Governed consent history, audit trails on financial claims, and export-ready structure for Power BI / federation layers reduce the chance that regional or donor reviews fail because source data cannot be reconstructed after the fact.

2. Data architecture map (evaluation view)

High-level architecture for legal and ICT review. Final deployment diagrams are issued with the security pack (especially Package 7).

┌─────────────────────────────────────────────────────────┐
│  BUYING INSTITUTION (tenant boundary)                   │
│  Org A never sees Org B · strict tenant isolation       │
├─────────────────────────────────────────────────────────┤
│  Roles: Programme · MEAL · Finance · Leadership · Admin │
├──────────────┬──────────────┬───────────────────────────┤
│ People &     │ Programmes & │ Delivery · Evidence       │
│ Consent      │ Enrolment    │ Activities · Milestones   │
├──────────────┴──────────────┴───────────────────────────┤
│ Accountability finance: expenses · vendor AP · audit    │
├─────────────────────────────────────────────────────────┤
│ Optional: country/office partitions (multi-country)     │
│ HQ roll-up ──► authorised portfolio views only          │
│ Country A ✗── read ──✗ Country B                        │
├─────────────────────────────────────────────────────────┤
│ Encryption in transit (TLS) · access controls (RBAC)    │
│ Purpose-based consent · grant/revoke history            │
│ GDPR-aligned stewardship · export / exit pathways       │
│ Hosting: shared multi-tenant · regional · or sovereign  │
└─────────────────────────────────────────────────────────┘
         │ structured exports
         ▼
  Snowflake / Power BI / NetSuite / federation dashboards

• Tenant isolation: each customer organisation is a separate tenant; no cross-tenant data access.
• Multi-country (where scoped): office-level partitions; HQ sees only authorised roll-ups; Country A cannot see Country B.
• Consent stewardship: purpose badges, grant/revoke history — not free-text spreadsheet cells.
• Hosting options: standard multi-tenant cloud; regional residency-oriented configuration (e.g. Africa / SE Asia); sovereign / high-isolation path under Package 7 with pen-test and handback pack.

3. Residual capacity clause (Implementation Integrity)