{ "copyright": "\u00a9 2026 Matthew Breen. Licensed under CC BY 4.0. See LICENSE-CONTENT.md.", "metadata": { "version": "1.1", "title": "NGO Blockchain Use Case Catalogue", "description": "145 enriched use cases across 10 categories (A-J) with blockchain properties, technology components, trigger conditions, and context templates", "totalUseCases": 145, "categories": { "A": "Financial Operations", "B": "Identity and Credentials", "C": "Data Management and Privacy", "D": "Supply Chain and Logistics", "E": "Governance and Coordination", "F": "Fundraising and Donor Relations", "G": "Resilience and Risk Management", "H": "Land, Property and Natural Resources", "I": "Energy and Environment", "J": "Workforce and Operations" }, "note": "NGO-040 Tadamon: added 6 stub UCs (UC-C-053, UC-D-075, UC-C-054, UC-B-040, UC-A-026, UC-E-085) with full structural metadata; solutionQuestions stubbed for follow-up. NGO-040 Tadamon solutionQuestions: authored 8-12 questions per UC for the 6 Tadamon UCs (UC-C-053, UC-D-075, UC-C-054, UC-B-040, UC-A-026, UC-E-085). F3 fix 2026-04-30: bumped rangeSignals counts on UC-J-115..121 from 3 to 5 each to give Cat J UCs surfacing parity with Cat E (5+ signals) under the current bonus formula min(signalCount, severityHits.length).", "lastUpdated": "2026-04-24" }, "bCriteriaReference": { "B1": "Shared Record of Truth", "B2": "Trust Minimisation", "B3": "Provable Integrity", "B4": "Disintermediation", "B5": "Settlement Finality", "B6": "Selective Disclosure", "B7": "Programmable Compliance", "B8": "Native Digital Asset / Tokenisation" }, "useCases": [ { "id": "UC-A-001", "name": "Cross-border beneficiary payments", "category": "A", "subcategory": "Cross-Border Payments and Transfers", "description": "Send money to the people you serve in another country with fewer banks and agents in between, so more of each payment reaches them and it arrives sooner.", "bCriteria": [ "B1", "B4", "B5" ], "requiredComponents": [ { "component": "payment-rails", "description": "Blockchain network for settlement" }, { "component": "stablecoin", "description": "Regulated dollar stablecoin or local-currency stablecoin" }, { "component": "on-ramp", "description": "Fiat to crypto conversion at HQ side" }, { "component": "off-ramp", "description": "Crypto to local currency at field side" }, { "component": "beneficiary-wallet", "description": "Wallet infrastructure for recipients" }, { "component": "compliance-screening", "description": "Sanctions/AML screening" } ], "conditionalComponents": [ { "component": "smart-contracts", "condition": "If payments are conditional (attendance, milestones)", "linksTo": "UC-A-012" }, { "component": "identity-verification", "condition": "If beneficiaries need KYC", "linksTo": "UC-B-024" }, { "component": "offline-sync", "condition": "If field connectivity is limited" } ], "crossCategoryDependencies": [ "UC-B-024 if KYC required", "UC-C-045 if consent records needed" ], "p2TriggerConditions": { "description": "Activated when P2 shows high intermediary count + high fees + slow transfers to beneficiaries", "rangeSignals": [ "intermediaries >= 3", "transferCost >= 5%", "transferTime >= 4-7 days" ] }, "contextFieldsTemplate": [ { "field": "corridors", "source": "P0 countries + P2 transfer routes", "description": "Which country corridors" }, { "field": "currencies", "source": "P2 answers", "description": "Which currencies involved" }, { "field": "volume", "source": "P2 ranges", "description": "Monthly transaction count" }, { "field": "averageSize", "source": "P2 ranges", "description": "Average transaction value" }, { "field": "connectivity", "source": "P0 Q13 + P4", "description": "Field office connectivity level" }, { "field": "existingSystems", "source": "P0 Q13", "description": "Current financial systems" }, { "field": "regulatory", "source": "P0 Q19-21", "description": "Regulatory environment" } ], "implementationComplexity": "medium-high", "examples": { "note": "WFP Building Blocks (Jordan), Oxfam UnBlocked Cash", "references": [ { "name": "WFP Building Blocks", "url": "https://www.wfp.org/building-blocks", "solved": "Transferred cash to refugee populations at scale, fast and at low cost" }, { "name": "Oxfam UnBlocked Cash", "url": "https://www.oxfam.org/en/unblocked-cash-project-using-blockchain-technology-revolutionize-humanitarian-aid", "solved": "Accelerated cash delivery and reduced transaction costs in remote Pacific islands" }, { "name": "UNHCR", "url": "https://www.unhcr.org/en-us/news/press/2023/3/641c67974/unhcr-wins-award-innovative-use-blockchain-solutions-provide-cash-forcibly.html", "solved": "Distributed cash to displaced persons securely and with full transaction traceability" } ] }, "solutionQuestions": [ { "id": "corridor-count", "type": "select", "options": [ { "label": "Single country", "value": "single" }, { "label": "2\u20133 countries", "value": "2-3" }, { "label": "4\u20135 countries", "value": "4-5" }, { "label": "More than 5 countries", "value": "5-plus" } ], "propertyMapping": { "single": { "technologies": [ "Single-corridor fiat on-ramp" ], "technologyProperties": { "corridorComplexity": "Single origination country", "multiRailNeeded": "No" } }, "2-3": { "technologies": [ "Multi-corridor fiat on-ramp gateway" ], "technologyProperties": { "corridorComplexity": "2\u20133 origination countries", "multiRailNeeded": "Yes \u2014 2-3 payment rails" } }, "4-5": { "technologies": [ "Multi-corridor fiat on-ramp gateway" ], "technologyProperties": { "corridorComplexity": "4\u20135 origination countries", "multiRailNeeded": "Yes \u2014 4-5 payment rails" } }, "5-plus": { "technologies": [ "Enterprise multi-corridor on-ramp gateway" ], "technologyProperties": { "corridorComplexity": "5+ origination countries", "multiRailNeeded": "Yes \u2014 enterprise-grade multi-rail" } } }, "prefillFrom": null, "briefSection": "Payment rail requirements", "text": "How many countries does your organisation send transfer funds from?", "ngoText": "How many countries does your organisation send transfer funds from?" }, { "id": "origination-country-1", "type": "select", "options": [ { "label": "United States", "value": "united-states" }, { "label": "United Kingdom", "value": "united-kingdom" }, { "label": "Germany", "value": "germany" }, { "label": "Netherlands", "value": "netherlands" }, { "label": "Switzerland", "value": "switzerland" }, { "label": "Belgium", "value": "belgium" }, { "label": "France", "value": "france" }, { "label": "Sweden", "value": "sweden" }, { "label": "Norway", "value": "norway" }, { "label": "Denmark", "value": "denmark" }, { "label": "Canada", "value": "canada" }, { "label": "Australia", "value": "australia" }, { "label": "Japan", "value": "japan" }, { "label": "Ireland", "value": "ireland" }, { "label": "Italy", "value": "italy" }, { "label": "Spain", "value": "spain" }, { "label": "Austria", "value": "austria" }, { "label": "Finland", "value": "finland" }, { "label": "Luxembourg", "value": "luxembourg" }, { "label": "South Korea", "value": "south-korea" }, { "label": "New Zealand", "value": "new-zealand" }, { "label": "United Arab Emirates", "value": "united-arab-emirates" }, { "label": "Singapore", "value": "singapore" }, { "label": "Other", "value": "other" } ], "propertyMapping": { "united-states": { "technologies": [ "ACH/wire fiat on-ramp" ], "technologyProperties": { "onRampType": "ACH/Fedwire bank transfer", "onRampRegion": "United States", "settlementRail": "ACH / Fedwire" } }, "united-kingdom": { "technologies": [ "UK Faster Payments on-ramp" ], "technologyProperties": { "onRampType": "Faster Payments bank transfer", "onRampRegion": "United Kingdom", "settlementRail": "FPS / BACS" } }, "germany": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "netherlands": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "switzerland": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SIC/SEPA bank transfer", "onRampRegion": "Switzerland/EU", "settlementRail": "SIC / SEPA Credit Transfer" } }, "belgium": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "france": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "sweden": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "norway": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA-adjacent bank transfer", "onRampRegion": "EEA", "settlementRail": "SEPA Credit Transfer" } }, "denmark": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "canada": { "technologies": [ "Canadian EFT on-ramp" ], "technologyProperties": { "onRampType": "Interac/EFT bank transfer", "onRampRegion": "Canada", "settlementRail": "Interac / EFT" } }, "australia": { "technologies": [ "Australian NPP on-ramp" ], "technologyProperties": { "onRampType": "NPP bank transfer", "onRampRegion": "Australia", "settlementRail": "NPP / BECS" } }, "japan": { "technologies": [ "Japanese Zengin on-ramp" ], "technologyProperties": { "onRampType": "Zengin bank transfer", "onRampRegion": "Japan", "settlementRail": "Zengin System" } }, "ireland": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "italy": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "spain": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "austria": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "finland": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "luxembourg": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "south-korea": { "technologies": [ "Korean banking on-ramp" ], "technologyProperties": { "onRampType": "KFTC bank transfer", "onRampRegion": "South Korea", "settlementRail": "KFTC / BOK-Wire" } }, "new-zealand": { "technologies": [ "NZ banking on-ramp" ], "technologyProperties": { "onRampType": "SBI bank transfer", "onRampRegion": "New Zealand", "settlementRail": "SBI / ESAS" } }, "united-arab-emirates": { "technologies": [ "UAE banking on-ramp" ], "technologyProperties": { "onRampType": "UAEFTS bank transfer", "onRampRegion": "United Arab Emirates", "settlementRail": "UAEFTS / IPP" } }, "singapore": { "technologies": [ "Singapore FAST on-ramp" ], "technologyProperties": { "onRampType": "FAST bank transfer", "onRampRegion": "Singapore", "settlementRail": "FAST / MEPS+" } }, "other": { "technologies": [ "Regional fiat on-ramp" ], "technologyProperties": { "onRampType": "Local rail bank transfer", "onRampRegion": "Region-specific", "settlementRail": "Local payment network" } } }, "showIf": { "questionId": "corridor-count", "minValue": "single" }, "prefillFrom": null, "briefSection": "Payment rail requirements", "text": "Which country do you most frequently initiate transfers from?", "ngoText": "Which country do you most frequently initiate transfers from?" }, { "id": "origination-country-2", "type": "select", "options": [ { "label": "United States", "value": "united-states" }, { "label": "United Kingdom", "value": "united-kingdom" }, { "label": "Germany", "value": "germany" }, { "label": "Netherlands", "value": "netherlands" }, { "label": "Switzerland", "value": "switzerland" }, { "label": "Belgium", "value": "belgium" }, { "label": "France", "value": "france" }, { "label": "Sweden", "value": "sweden" }, { "label": "Norway", "value": "norway" }, { "label": "Denmark", "value": "denmark" }, { "label": "Canada", "value": "canada" }, { "label": "Australia", "value": "australia" }, { "label": "Japan", "value": "japan" }, { "label": "Ireland", "value": "ireland" }, { "label": "Italy", "value": "italy" }, { "label": "Spain", "value": "spain" }, { "label": "Austria", "value": "austria" }, { "label": "Finland", "value": "finland" }, { "label": "Luxembourg", "value": "luxembourg" }, { "label": "South Korea", "value": "south-korea" }, { "label": "New Zealand", "value": "new-zealand" }, { "label": "United Arab Emirates", "value": "united-arab-emirates" }, { "label": "Singapore", "value": "singapore" }, { "label": "Other", "value": "other" } ], "propertyMapping": { "united-states": { "technologies": [ "ACH/wire fiat on-ramp" ], "technologyProperties": { "onRampType": "ACH/Fedwire bank transfer", "onRampRegion": "United States", "settlementRail": "ACH / Fedwire" } }, "united-kingdom": { "technologies": [ "UK Faster Payments on-ramp" ], "technologyProperties": { "onRampType": "Faster Payments bank transfer", "onRampRegion": "United Kingdom", "settlementRail": "FPS / BACS" } }, "germany": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "netherlands": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "switzerland": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SIC/SEPA bank transfer", "onRampRegion": "Switzerland/EU", "settlementRail": "SIC / SEPA Credit Transfer" } }, "belgium": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "france": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "sweden": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "norway": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA-adjacent bank transfer", "onRampRegion": "EEA", "settlementRail": "SEPA Credit Transfer" } }, "denmark": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "canada": { "technologies": [ "Canadian EFT on-ramp" ], "technologyProperties": { "onRampType": "Interac/EFT bank transfer", "onRampRegion": "Canada", "settlementRail": "Interac / EFT" } }, "australia": { "technologies": [ "Australian NPP on-ramp" ], "technologyProperties": { "onRampType": "NPP bank transfer", "onRampRegion": "Australia", "settlementRail": "NPP / BECS" } }, "japan": { "technologies": [ "Japanese Zengin on-ramp" ], "technologyProperties": { "onRampType": "Zengin bank transfer", "onRampRegion": "Japan", "settlementRail": "Zengin System" } }, "ireland": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "italy": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "spain": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "austria": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "finland": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "luxembourg": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "south-korea": { "technologies": [ "Korean banking on-ramp" ], "technologyProperties": { "onRampType": "KFTC bank transfer", "onRampRegion": "South Korea", "settlementRail": "KFTC / BOK-Wire" } }, "new-zealand": { "technologies": [ "NZ banking on-ramp" ], "technologyProperties": { "onRampType": "SBI bank transfer", "onRampRegion": "New Zealand", "settlementRail": "SBI / ESAS" } }, "united-arab-emirates": { "technologies": [ "UAE banking on-ramp" ], "technologyProperties": { "onRampType": "UAEFTS bank transfer", "onRampRegion": "United Arab Emirates", "settlementRail": "UAEFTS / IPP" } }, "singapore": { "technologies": [ "Singapore FAST on-ramp" ], "technologyProperties": { "onRampType": "FAST bank transfer", "onRampRegion": "Singapore", "settlementRail": "FAST / MEPS+" } }, "other": { "technologies": [ "Regional fiat on-ramp" ], "technologyProperties": { "onRampType": "Local rail bank transfer", "onRampRegion": "Region-specific", "settlementRail": "Local payment network" } } }, "showIf": { "questionId": "corridor-count", "minValue": "2-3" }, "prefillFrom": null, "briefSection": "Payment rail requirements", "text": "Second most common transfer origination country (if applicable)", "ngoText": "Second most common transfer origination country (if applicable)" }, { "id": "origination-country-3", "type": "select", "options": [ { "label": "United States", "value": "united-states" }, { "label": "United Kingdom", "value": "united-kingdom" }, { "label": "Germany", "value": "germany" }, { "label": "Netherlands", "value": "netherlands" }, { "label": "Switzerland", "value": "switzerland" }, { "label": "Belgium", "value": "belgium" }, { "label": "France", "value": "france" }, { "label": "Sweden", "value": "sweden" }, { "label": "Norway", "value": "norway" }, { "label": "Denmark", "value": "denmark" }, { "label": "Canada", "value": "canada" }, { "label": "Australia", "value": "australia" }, { "label": "Japan", "value": "japan" }, { "label": "Ireland", "value": "ireland" }, { "label": "Italy", "value": "italy" }, { "label": "Spain", "value": "spain" }, { "label": "Austria", "value": "austria" }, { "label": "Finland", "value": "finland" }, { "label": "Luxembourg", "value": "luxembourg" }, { "label": "South Korea", "value": "south-korea" }, { "label": "New Zealand", "value": "new-zealand" }, { "label": "United Arab Emirates", "value": "united-arab-emirates" }, { "label": "Singapore", "value": "singapore" }, { "label": "Other", "value": "other" } ], "propertyMapping": { "united-states": { "technologies": [ "ACH/wire fiat on-ramp" ], "technologyProperties": { "onRampType": "ACH/Fedwire bank transfer", "onRampRegion": "United States", "settlementRail": "ACH / Fedwire" } }, "united-kingdom": { "technologies": [ "UK Faster Payments on-ramp" ], "technologyProperties": { "onRampType": "Faster Payments bank transfer", "onRampRegion": "United Kingdom", "settlementRail": "FPS / BACS" } }, "germany": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "netherlands": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "switzerland": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SIC/SEPA bank transfer", "onRampRegion": "Switzerland/EU", "settlementRail": "SIC / SEPA Credit Transfer" } }, "belgium": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "france": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "sweden": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "norway": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA-adjacent bank transfer", "onRampRegion": "EEA", "settlementRail": "SEPA Credit Transfer" } }, "denmark": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "canada": { "technologies": [ "Canadian EFT on-ramp" ], "technologyProperties": { "onRampType": "Interac/EFT bank transfer", "onRampRegion": "Canada", "settlementRail": "Interac / EFT" } }, "australia": { "technologies": [ "Australian NPP on-ramp" ], "technologyProperties": { "onRampType": "NPP bank transfer", "onRampRegion": "Australia", "settlementRail": "NPP / BECS" } }, "japan": { "technologies": [ "Japanese Zengin on-ramp" ], "technologyProperties": { "onRampType": "Zengin bank transfer", "onRampRegion": "Japan", "settlementRail": "Zengin System" } }, "ireland": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "italy": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "spain": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "austria": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "finland": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "luxembourg": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "south-korea": { "technologies": [ "Korean banking on-ramp" ], "technologyProperties": { "onRampType": "KFTC bank transfer", "onRampRegion": "South Korea", "settlementRail": "KFTC / BOK-Wire" } }, "new-zealand": { "technologies": [ "NZ banking on-ramp" ], "technologyProperties": { "onRampType": "SBI bank transfer", "onRampRegion": "New Zealand", "settlementRail": "SBI / ESAS" } }, "united-arab-emirates": { "technologies": [ "UAE banking on-ramp" ], "technologyProperties": { "onRampType": "UAEFTS bank transfer", "onRampRegion": "United Arab Emirates", "settlementRail": "UAEFTS / IPP" } }, "singapore": { "technologies": [ "Singapore FAST on-ramp" ], "technologyProperties": { "onRampType": "FAST bank transfer", "onRampRegion": "Singapore", "settlementRail": "FAST / MEPS+" } }, "other": { "technologies": [ "Regional fiat on-ramp" ], "technologyProperties": { "onRampType": "Local rail bank transfer", "onRampRegion": "Region-specific", "settlementRail": "Local payment network" } } }, "showIf": { "questionId": "corridor-count", "minValue": "2-3" }, "prefillFrom": null, "briefSection": "Payment rail requirements", "text": "Third transfer origination country (if applicable)", "ngoText": "Third transfer origination country (if applicable)" }, { "id": "origination-country-4", "type": "select", "options": [ { "label": "United States", "value": "united-states" }, { "label": "United Kingdom", "value": "united-kingdom" }, { "label": "Germany", "value": "germany" }, { "label": "Netherlands", "value": "netherlands" }, { "label": "Switzerland", "value": "switzerland" }, { "label": "Belgium", "value": "belgium" }, { "label": "France", "value": "france" }, { "label": "Sweden", "value": "sweden" }, { "label": "Norway", "value": "norway" }, { "label": "Denmark", "value": "denmark" }, { "label": "Canada", "value": "canada" }, { "label": "Australia", "value": "australia" }, { "label": "Japan", "value": "japan" }, { "label": "Ireland", "value": "ireland" }, { "label": "Italy", "value": "italy" }, { "label": "Spain", "value": "spain" }, { "label": "Austria", "value": "austria" }, { "label": "Finland", "value": "finland" }, { "label": "Luxembourg", "value": "luxembourg" }, { "label": "South Korea", "value": "south-korea" }, { "label": "New Zealand", "value": "new-zealand" }, { "label": "United Arab Emirates", "value": "united-arab-emirates" }, { "label": "Singapore", "value": "singapore" }, { "label": "Other", "value": "other" } ], "propertyMapping": { "united-states": { "technologies": [ "ACH/wire fiat on-ramp" ], "technologyProperties": { "onRampType": "ACH/Fedwire bank transfer", "onRampRegion": "United States", "settlementRail": "ACH / Fedwire" } }, "united-kingdom": { "technologies": [ "UK Faster Payments on-ramp" ], "technologyProperties": { "onRampType": "Faster Payments bank transfer", "onRampRegion": "United Kingdom", "settlementRail": "FPS / BACS" } }, "germany": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "netherlands": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "switzerland": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SIC/SEPA bank transfer", "onRampRegion": "Switzerland/EU", "settlementRail": "SIC / SEPA Credit Transfer" } }, "belgium": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "france": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "sweden": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "norway": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA-adjacent bank transfer", "onRampRegion": "EEA", "settlementRail": "SEPA Credit Transfer" } }, "denmark": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "canada": { "technologies": [ "Canadian EFT on-ramp" ], "technologyProperties": { "onRampType": "Interac/EFT bank transfer", "onRampRegion": "Canada", "settlementRail": "Interac / EFT" } }, "australia": { "technologies": [ "Australian NPP on-ramp" ], "technologyProperties": { "onRampType": "NPP bank transfer", "onRampRegion": "Australia", "settlementRail": "NPP / BECS" } }, "japan": { "technologies": [ "Japanese Zengin on-ramp" ], "technologyProperties": { "onRampType": "Zengin bank transfer", "onRampRegion": "Japan", "settlementRail": "Zengin System" } }, "ireland": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "italy": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "spain": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "austria": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "finland": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "luxembourg": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "south-korea": { "technologies": [ "Korean banking on-ramp" ], "technologyProperties": { "onRampType": "KFTC bank transfer", "onRampRegion": "South Korea", "settlementRail": "KFTC / BOK-Wire" } }, "new-zealand": { "technologies": [ "NZ banking on-ramp" ], "technologyProperties": { "onRampType": "SBI bank transfer", "onRampRegion": "New Zealand", "settlementRail": "SBI / ESAS" } }, "united-arab-emirates": { "technologies": [ "UAE banking on-ramp" ], "technologyProperties": { "onRampType": "UAEFTS bank transfer", "onRampRegion": "United Arab Emirates", "settlementRail": "UAEFTS / IPP" } }, "singapore": { "technologies": [ "Singapore FAST on-ramp" ], "technologyProperties": { "onRampType": "FAST bank transfer", "onRampRegion": "Singapore", "settlementRail": "FAST / MEPS+" } }, "other": { "technologies": [ "Regional fiat on-ramp" ], "technologyProperties": { "onRampType": "Local rail bank transfer", "onRampRegion": "Region-specific", "settlementRail": "Local payment network" } } }, "showIf": { "questionId": "corridor-count", "minValue": "4-5" }, "prefillFrom": null, "briefSection": "Payment rail requirements", "text": "Fourth transfer origination country (if applicable)", "ngoText": "Fourth transfer origination country (if applicable)" }, { "id": "origination-country-5", "type": "select", "options": [ { "label": "United States", "value": "united-states" }, { "label": "United Kingdom", "value": "united-kingdom" }, { "label": "Germany", "value": "germany" }, { "label": "Netherlands", "value": "netherlands" }, { "label": "Switzerland", "value": "switzerland" }, { "label": "Belgium", "value": "belgium" }, { "label": "France", "value": "france" }, { "label": "Sweden", "value": "sweden" }, { "label": "Norway", "value": "norway" }, { "label": "Denmark", "value": "denmark" }, { "label": "Canada", "value": "canada" }, { "label": "Australia", "value": "australia" }, { "label": "Japan", "value": "japan" }, { "label": "Ireland", "value": "ireland" }, { "label": "Italy", "value": "italy" }, { "label": "Spain", "value": "spain" }, { "label": "Austria", "value": "austria" }, { "label": "Finland", "value": "finland" }, { "label": "Luxembourg", "value": "luxembourg" }, { "label": "South Korea", "value": "south-korea" }, { "label": "New Zealand", "value": "new-zealand" }, { "label": "United Arab Emirates", "value": "united-arab-emirates" }, { "label": "Singapore", "value": "singapore" }, { "label": "Other", "value": "other" } ], "propertyMapping": { "united-states": { "technologies": [ "ACH/wire fiat on-ramp" ], "technologyProperties": { "onRampType": "ACH/Fedwire bank transfer", "onRampRegion": "United States", "settlementRail": "ACH / Fedwire" } }, "united-kingdom": { "technologies": [ "UK Faster Payments on-ramp" ], "technologyProperties": { "onRampType": "Faster Payments bank transfer", "onRampRegion": "United Kingdom", "settlementRail": "FPS / BACS" } }, "germany": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "netherlands": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "switzerland": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SIC/SEPA bank transfer", "onRampRegion": "Switzerland/EU", "settlementRail": "SIC / SEPA Credit Transfer" } }, "belgium": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "france": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "sweden": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "norway": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA-adjacent bank transfer", "onRampRegion": "EEA", "settlementRail": "SEPA Credit Transfer" } }, "denmark": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "canada": { "technologies": [ "Canadian EFT on-ramp" ], "technologyProperties": { "onRampType": "Interac/EFT bank transfer", "onRampRegion": "Canada", "settlementRail": "Interac / EFT" } }, "australia": { "technologies": [ "Australian NPP on-ramp" ], "technologyProperties": { "onRampType": "NPP bank transfer", "onRampRegion": "Australia", "settlementRail": "NPP / BECS" } }, "japan": { "technologies": [ "Japanese Zengin on-ramp" ], "technologyProperties": { "onRampType": "Zengin bank transfer", "onRampRegion": "Japan", "settlementRail": "Zengin System" } }, "ireland": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "italy": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "spain": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "austria": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "finland": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "luxembourg": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "south-korea": { "technologies": [ "Korean banking on-ramp" ], "technologyProperties": { "onRampType": "KFTC bank transfer", "onRampRegion": "South Korea", "settlementRail": "KFTC / BOK-Wire" } }, "new-zealand": { "technologies": [ "NZ banking on-ramp" ], "technologyProperties": { "onRampType": "SBI bank transfer", "onRampRegion": "New Zealand", "settlementRail": "SBI / ESAS" } }, "united-arab-emirates": { "technologies": [ "UAE banking on-ramp" ], "technologyProperties": { "onRampType": "UAEFTS bank transfer", "onRampRegion": "United Arab Emirates", "settlementRail": "UAEFTS / IPP" } }, "singapore": { "technologies": [ "Singapore FAST on-ramp" ], "technologyProperties": { "onRampType": "FAST bank transfer", "onRampRegion": "Singapore", "settlementRail": "FAST / MEPS+" } }, "other": { "technologies": [ "Regional fiat on-ramp" ], "technologyProperties": { "onRampType": "Local rail bank transfer", "onRampRegion": "Region-specific", "settlementRail": "Local payment network" } } }, "showIf": { "questionId": "corridor-count", "minValue": "4-5" }, "prefillFrom": null, "briefSection": "Payment rail requirements", "text": "Fifth transfer origination country (if applicable)", "ngoText": "Fifth transfer origination country (if applicable)" }, { "id": "funding-method", "type": "select", "options": [ { "label": "Bank transfer from organisation account", "value": "bank-transfer" }, { "label": "Card payment from organisation", "value": "card-payment" }, { "label": "Direct stablecoin funding (organisation already holds stablecoins)", "value": "direct-stablecoin" }, { "label": "Mixed: bank transfer for most, card for urgent payments", "value": "mixed-methods" } ], "propertyMapping": { "bank-transfer": { "technologies": [ "Bank-integrated fiat on-ramp" ], "technologyProperties": { "fundingSource": "Organisation bank account", "onRampSpeed": "1-2 business days (SEPA/ACH) or same-day (Faster Payments/wire)", "kybRequired": "Yes \u2014 organisation KYB verification" } }, "card-payment": { "technologies": [ "Card payment on-ramp" ], "technologyProperties": { "fundingSource": "Organisation payment card", "onRampSpeed": "Near-instant", "kybRequired": "Yes \u2014 card verification and organisation KYB" } }, "direct-stablecoin": { "technologies": [ "Direct stablecoin treasury funding" ], "technologyProperties": { "fundingSource": "Existing stablecoin holdings", "onRampSpeed": "Immediate (no fiat conversion needed)", "kybRequired": "Wallet verification only" } }, "mixed-methods": { "technologies": [ "Multi-method fiat on-ramp", "Card payment on-ramp" ], "technologyProperties": { "fundingSource": "Bank transfer (primary) + card (urgent)", "onRampSpeed": "Varies by method", "kybRequired": "Yes \u2014 full organisation KYB" } } }, "prefillFrom": null, "briefSection": "Payment rail requirements", "text": "How does your organisation currently fund international transfers or payments?", "ngoText": "How does your organisation currently fund international transfers or payments?" }, { "id": "beneficiary-device", "type": "select", "options": [ { "label": "Smartphones with reliable data connectivity", "value": "smartphone-connected" }, { "label": "Smartphones but with intermittent connectivity", "value": "smartphone-intermittent" }, { "label": "Feature phones only (SMS/USSD)", "value": "feature-phone" }, { "label": "No personal devices, rely on agent/kiosk access", "value": "no-device" }, { "label": "Mixed: varies significantly across beneficiary population", "value": "mixed" } ], "propertyMapping": { "smartphone-connected": { "technologies": [ "Mobile wallet application" ], "technologyProperties": { "interface": "Native mobile app", "offlineSync": "optional", "dataRequirement": "standard" } }, "smartphone-intermittent": { "technologies": [ "Mobile wallet application", "Offline-capable sync layer" ], "technologyProperties": { "interface": "Native mobile app with offline mode", "offlineSync": "required", "dataRequirement": "minimal" } }, "feature-phone": { "technologies": [ "USSD/SMS-based wallet" ], "technologyProperties": { "interface": "USSD menu or SMS commands", "offlineSync": "required", "dataRequirement": "zero-data" } }, "no-device": { "technologies": [ "Agent-assisted wallet", "Biometric authentication terminal" ], "technologyProperties": { "interface": "Agent kiosk or POS device", "offlineSync": "required", "dataRequirement": "agent-side only" } }, "mixed": { "technologies": [ "Multi-channel wallet platform" ], "technologyProperties": { "interface": "App + USSD + agent fallback", "offlineSync": "required", "dataRequirement": "adaptive" } } }, "prefillFrom": null, "briefSection": "End-user interface", "text": "What devices do your beneficiaries typically have access to in the field?", "ngoText": "What devices do your beneficiaries typically have access to in the field?" }, { "id": "avg-transaction-size", "type": "select", "options": [ { "label": "Micro-payments: under $10 USD equivalent", "value": "micro" }, { "label": "Small: $10\u2013$50 USD equivalent", "value": "small" }, { "label": "Medium: $50\u2013$200 USD equivalent", "value": "medium" }, { "label": "Large: $200\u2013$1,000 USD equivalent", "value": "large" }, { "label": "Variable: ranges widely across programmes", "value": "variable" } ], "propertyMapping": { "micro": { "technologies": [ "Layer 1 payment rail" ], "technologyProperties": { "maxTransactionFee": "sub-$0.01", "feeModel": "Fixed micro-fee, not percentage-based" } }, "small": { "technologies": [ "Layer 1 payment rail" ], "technologyProperties": { "maxTransactionFee": "sub-$0.05", "feeModel": "Fixed low fee" } }, "medium": { "technologies": [ "Layer 1 payment rail" ], "technologyProperties": { "maxTransactionFee": "sub-$0.10", "feeModel": "Fixed or low percentage" } }, "large": { "technologies": [ "Layer 1 payment rail" ], "technologyProperties": { "maxTransactionFee": "sub-$0.50", "feeModel": "Low percentage acceptable" } }, "variable": { "technologies": [ "Layer 1 payment rail" ], "technologyProperties": { "maxTransactionFee": "sub-$0.05", "feeModel": "Fixed fee preferred for predictability" } } }, "prefillFrom": "P2-CatA-Q4", "briefSection": "Payment rail requirements", "text": "What is the typical payment amount per beneficiary per disbursement?", "ngoText": "What is the typical payment amount per beneficiary per disbursement?" }, { "id": "settlement-speed", "type": "select", "options": [ { "label": "Real-time (seconds to minutes)", "value": "realtime" }, { "label": "Same day (within hours)", "value": "same-day" }, { "label": "Next business day is acceptable", "value": "next-day" }, { "label": "Within a week is fine", "value": "weekly" } ], "propertyMapping": { "realtime": { "technologies": [ "Direct payment network" ], "technologyProperties": { "settlementFinality": "under 5 seconds", "confirmationModel": "Confirmed quickly and reliably" } }, "same-day": { "technologies": [ "Direct payment network" ], "technologyProperties": { "settlementFinality": "under 1 hour", "confirmationModel": "Probabilistic acceptable" } }, "next-day": { "technologies": [ "Direct payment network" ], "technologyProperties": { "settlementFinality": "under 24 hours", "confirmationModel": "Any" } }, "weekly": { "technologies": [ "Direct payment network" ], "technologyProperties": { "settlementFinality": "flexible", "confirmationModel": "Any" } } }, "prefillFrom": "P2-CatA-Q3", "briefSection": "Payment rail requirements", "text": "How quickly do beneficiaries need to receive funds after you initiate a payment?", "ngoText": "How quickly do beneficiaries need to receive funds after you initiate a payment?" }, { "id": "last-mile-delivery", "type": "multiselect", "options": [ { "label": "Direct to bank account", "value": "bank-account" }, { "label": "Mobile money", "value": "mobile-money" }, { "label": "Cash via agents or field staff", "value": "cash-agent" }, { "label": "Cash at a bank branch", "value": "cash-bank" }, { "label": "Vouchers or e-vouchers", "value": "voucher" }, { "label": "No current system, setting up from scratch", "value": "greenfield" } ], "propertyMapping": { "bank-account": { "technologies": [ "Bank-integrated off-ramp" ], "technologyProperties": { "lastMileChannel": "Bank transfer API", "cashOutMethod": "Direct deposit" } }, "mobile-money": { "technologies": [ "Mobile money off-ramp integration" ], "technologyProperties": { "lastMileChannel": "MNO API integration", "cashOutMethod": "Mobile money wallet top-up" } }, "cash-agent": { "technologies": [ "Agent network integration", "Agent-assisted wallet" ], "technologyProperties": { "lastMileChannel": "Agent cash-out network", "cashOutMethod": "Agent-facilitated withdrawal" } }, "cash-bank": { "technologies": [ "Bank-integrated off-ramp" ], "technologyProperties": { "lastMileChannel": "Bank branch withdrawal", "cashOutMethod": "Counter collection" } }, "voucher": { "technologies": [ "Digital voucher system" ], "technologyProperties": { "lastMileChannel": "Voucher redemption network", "cashOutMethod": "Merchant redemption" } }, "greenfield": { "technologies": [ "End-to-end wallet platform", "Agent network" ], "technologyProperties": { "lastMileChannel": "New wallet ecosystem required", "cashOutMethod": "To be designed" } } }, "prefillFrom": "P0-S3-Q12", "briefSection": "Last-mile delivery", "text": "How do beneficiaries currently receive payments in the field?", "ngoText": "How do beneficiaries currently receive payments in the field?" }, { "id": "beneficiary-bank-access", "type": "select", "options": [ { "label": "Most (over 70%) have bank accounts", "value": "most-banked" }, { "label": "Some (30\u201370%) have bank accounts", "value": "partially-banked" }, { "label": "Few (under 30%) have bank accounts", "value": "mostly-unbanked" }, { "label": "Almost none: largely unbanked population", "value": "unbanked" } ], "propertyMapping": { "most-banked": { "technologies": [ "Bank-integrated off-ramp" ], "technologyProperties": { "walletType": "Bank-linked optional", "kycTier": "Full KYC likely available" } }, "partially-banked": { "technologies": [ "Hybrid wallet platform", "Bank-integrated off-ramp" ], "technologyProperties": { "walletType": "Dual-mode (bank-linked + standalone)", "kycTier": "Tiered KYC required" } }, "mostly-unbanked": { "technologies": [ "Standalone embedded wallet", "Agent network" ], "technologyProperties": { "walletType": "Non-custodial or semi-custodial wallet", "kycTier": "Simplified/tiered KYC essential" } }, "unbanked": { "technologies": [ "Embedded wallet platform", "Agent cash-out network", "Biometric authentication" ], "technologyProperties": { "walletType": "Self-custodial wallet with agent support", "kycTier": "Minimal KYC / biometric-only tier" } } }, "prefillFrom": null, "briefSection": "End-user interface", "text": "What proportion of your beneficiaries have access to a formal bank account?", "ngoText": "What proportion of your beneficiaries have access to a formal bank account?" }, { "id": "kyc-requirements", "type": "select", "options": [ { "label": "Full KYC: government ID, address proof available", "value": "full-kyc" }, { "label": "Simplified KYC: name and basic ID only", "value": "simplified-kyc" }, { "label": "Biometric-only: fingerprint or face recognition", "value": "biometric-only" }, { "label": "Community vouching / group attestation", "value": "community-vouch" }, { "label": "No formal ID available for most beneficiaries", "value": "no-id" } ], "propertyMapping": { "full-kyc": { "technologies": [ "Standard KYC module" ], "technologyProperties": { "identityVerification": "Document-based KYC", "biometricRequired": false } }, "simplified-kyc": { "technologies": [ "Tiered KYC module" ], "technologyProperties": { "identityVerification": "Simplified due diligence", "biometricRequired": false } }, "biometric-only": { "technologies": [ "Biometric authentication system" ], "technologyProperties": { "identityVerification": "Biometric enrolment", "biometricRequired": true, "biometricType": "Fingerprint and/or facial recognition" } }, "community-vouch": { "technologies": [ "Decentralised identity attestation" ], "technologyProperties": { "identityVerification": "Community-based verification", "biometricRequired": false } }, "no-id": { "technologies": [ "Biometric authentication system", "Unique beneficiary token" ], "technologyProperties": { "identityVerification": "Biometric + token-based", "biometricRequired": true, "biometricType": "Mandatory fingerprint/iris" } } }, "prefillFrom": null, "briefSection": "Identity and compliance", "text": "What identity verification is required or feasible for your beneficiary population?", "ngoText": "What identity verification is required or feasible for your beneficiary population?" }, { "id": "conditional-payments", "type": "select", "options": [ { "label": "Yes, most payments are conditional", "value": "mostly-conditional" }, { "label": "Yes, some payments have conditions", "value": "some-conditional" }, { "label": "No, all payments are unconditional cash transfers", "value": "unconditional" } ], "propertyMapping": { "mostly-conditional": { "technologies": [ "Smart contract payment automation", "Condition verification oracle" ], "technologyProperties": { "conditionality": "Smart contract-enforced conditions", "verificationMethod": "Automated trigger from data source" } }, "some-conditional": { "technologies": [ "Smart contract payment automation" ], "technologyProperties": { "conditionality": "Optional conditional logic", "verificationMethod": "Manual or automated trigger" } }, "unconditional": { "technologies": [], "technologyProperties": { "conditionality": "None required" } } }, "prefillFrom": null, "briefSection": "Payment logic", "text": "Are any of these payments conditional on beneficiary actions (e.g., attendance, training completion, milestones)?", "ngoText": "Are any of these payments conditional on beneficiary actions (e.g., attendance, training completion, milestones)?" }, { "id": "currency-pairs", "type": "multiselect", "options": [ { "label": "USD to East African currencies (KES, UGX, TZS, RWF)", "value": "usd-east-africa" }, { "label": "USD to West African currencies (NGN, GHS, XOF)", "value": "usd-west-africa" }, { "label": "USD to South/Southeast Asian currencies (BDT, PKR, MMK, PHP)", "value": "usd-south-asia" }, { "label": "EUR to African or Middle Eastern currencies", "value": "eur-africa-mena" }, { "label": "GBP to Commonwealth currencies", "value": "gbp-commonwealth" }, { "label": "USD or EUR to Latin American currencies (COP, PEN, HNL, HTG)", "value": "latam" }, { "label": "Stablecoin to local currency (via mobile money or cash-out)", "value": "stablecoin-local" }, { "label": "Multiple regions: complex multi-corridor programme", "value": "multi-region" }, { "label": "Not sure, need guidance on corridor planning", "value": "unsure" } ], "propertyMapping": { "usd-east-africa": { "technologies": [ "USD-KES/UGX/TZS corridor on-ramp" ], "technologyProperties": { "corridorRegion": "East Africa", "baseCurrency": "USD", "corridorLiquidity": "High" } }, "usd-west-africa": { "technologies": [ "USD-NGN/GHS/XOF corridor on-ramp" ], "technologyProperties": { "corridorRegion": "West Africa", "baseCurrency": "USD", "corridorLiquidity": "Medium" } }, "usd-south-asia": { "technologies": [ "USD-BDT/PKR/PHP corridor on-ramp" ], "technologyProperties": { "corridorRegion": "South/Southeast Asia", "baseCurrency": "USD", "corridorLiquidity": "Medium-High" } }, "eur-africa-mena": { "technologies": [ "EUR-Africa/MENA corridor on-ramp" ], "technologyProperties": { "corridorRegion": "Africa/MENA", "baseCurrency": "EUR", "corridorLiquidity": "Medium" } }, "gbp-commonwealth": { "technologies": [ "GBP-Commonwealth corridor on-ramp" ], "technologyProperties": { "corridorRegion": "Commonwealth", "baseCurrency": "GBP", "corridorLiquidity": "Medium" } }, "latam": { "technologies": [ "USD/EUR-LatAm corridor on-ramp" ], "technologyProperties": { "corridorRegion": "Latin America", "baseCurrency": "USD/EUR", "corridorLiquidity": "Medium" } }, "stablecoin-local": { "technologies": [ "Stablecoin-to-local off-ramp", "Mobile money integration" ], "technologyProperties": { "corridorRegion": "Variable", "baseCurrency": "Stablecoin", "corridorLiquidity": "Depends on off-ramp availability" } }, "multi-region": { "technologies": [ "Enterprise multi-corridor on-ramp gateway", "Multi-region FX management" ], "technologyProperties": { "corridorRegion": "Multiple", "baseCurrency": "Multiple", "corridorLiquidity": "Variable" } }, "unsure": { "technologies": [ "Corridor assessment needed" ], "technologyProperties": { "corridorRegion": "TBD", "baseCurrency": "TBD", "corridorLiquidity": "TBD" } } }, "prefillFrom": "P0-countries", "briefSection": "Stablecoin and FX", "text": "Which currency corridor regions do your transfers typically involve?", "ngoText": "Which currency corridor regions do your transfers typically involve?" }, { "id": "stablecoin-preference", "type": "select", "options": [ { "label": "A regulated digital dollar", "value": "usd" }, { "label": "EUR-denominated", "value": "eur" }, { "label": "Local currency stablecoin if available", "value": "local" }, { "label": "Multi-currency: need to hold and convert between several", "value": "multi" }, { "label": "Not sure, need guidance", "value": "unsure" } ], "propertyMapping": { "usd": { "technologies": [ "USD-pegged stablecoin" ], "technologyProperties": { "stablecoinType": "USD-pegged", "fxConversion": "At off-ramp only" } }, "eur": { "technologies": [ "EUR-pegged stablecoin" ], "technologyProperties": { "stablecoinType": "EUR-pegged", "fxConversion": "At off-ramp only" } }, "local": { "technologies": [ "Local currency stablecoin" ], "technologyProperties": { "stablecoinType": "Local currency peg", "fxConversion": "Minimal \u2014 native currency" } }, "multi": { "technologies": [ "Multi-stablecoin treasury", "Automated FX conversion" ], "technologyProperties": { "stablecoinType": "Multiple denominations", "fxConversion": "On-chain or at off-ramp" } }, "unsure": { "technologies": [ "USD-pegged stablecoin" ], "technologyProperties": { "stablecoinType": "USD-pegged (default recommendation)", "fxConversion": "At off-ramp" } } }, "prefillFrom": null, "briefSection": "Stablecoin and FX", "text": "What currencies do your beneficiaries need to receive payments in?", "ngoText": "What currencies do your beneficiaries need to receive payments in?", "hidden": true }, { "id": "sanctions-screening", "type": "multiselect", "options": [ { "label": "OFAC (US sanctions) screening", "value": "ofac" }, { "label": "EU sanctions list screening", "value": "eu-sanctions" }, { "label": "UN sanctions list screening", "value": "un-sanctions" }, { "label": "Local AML/CFT requirements in destination countries", "value": "local-aml" }, { "label": "Donor-specific compliance requirements", "value": "donor-specific" }, { "label": "Not sure, need guidance on requirements", "value": "unsure" } ], "propertyMapping": { "ofac": { "technologies": [ "OFAC compliance screening module" ], "technologyProperties": { "sanctionsScreening": "OFAC SDN list", "screeningFrequency": "Per-transaction" } }, "eu-sanctions": { "technologies": [ "EU sanctions screening module" ], "technologyProperties": { "sanctionsScreening": "EU consolidated list", "screeningFrequency": "Per-transaction" } }, "un-sanctions": { "technologies": [ "UN sanctions screening module" ], "technologyProperties": { "sanctionsScreening": "UN Security Council list", "screeningFrequency": "Per-transaction" } }, "local-aml": { "technologies": [ "Local AML/CFT compliance module" ], "technologyProperties": { "sanctionsScreening": "Country-specific AML", "screeningFrequency": "Per-transaction + periodic" } }, "donor-specific": { "technologies": [ "Configurable compliance rules engine" ], "technologyProperties": { "sanctionsScreening": "Custom donor rules", "screeningFrequency": "Per-transaction" } }, "unsure": { "technologies": [ "Comprehensive sanctions screening suite" ], "technologyProperties": { "sanctionsScreening": "Full multi-list screening recommended", "screeningFrequency": "Per-transaction" } } }, "prefillFrom": "P0-regulatory", "briefSection": "Identity and compliance", "text": "What sanctions and compliance screening is required for your payment corridors?", "ngoText": "What sanctions and compliance screening is required for your payment corridors?" }, { "id": "batch-vs-individual", "type": "select", "options": [ { "label": "Batch: upload a list of beneficiaries and amounts", "value": "batch" }, { "label": "Individual: one payment at a time as needed", "value": "individual" }, { "label": "Both, batch for regular disbursements, individual for ad-hoc", "value": "both" } ], "propertyMapping": { "batch": { "technologies": [ "Batch payment engine" ], "technologyProperties": { "paymentInitiation": "CSV/API batch upload", "batchSize": "Configurable" } }, "individual": { "technologies": [], "technologyProperties": { "paymentInitiation": "Single transaction UI/API" } }, "both": { "technologies": [ "Batch payment engine" ], "technologyProperties": { "paymentInitiation": "Batch + individual modes", "batchSize": "Configurable" } } }, "prefillFrom": null, "briefSection": "Payment operations", "text": "How are payments typically initiated?", "ngoText": "How are payments typically initiated?" }, { "id": "connectivity-lastmile", "type": "select", "options": [ { "label": "Reliable broadband/4G: always connected", "value": "reliable" }, { "label": "Intermittent 3G/4G: drops frequently", "value": "intermittent" }, { "label": "2G/EDGE only: very slow data", "value": "2g-only" }, { "label": "No internet, SMS/USSD network only", "value": "no-internet" }, { "label": "Completely offline: no cellular coverage at all", "value": "offline" } ], "propertyMapping": { "reliable": { "technologies": [], "technologyProperties": { "connectivityRequirement": "Online-first", "offlineCapability": "Not required" } }, "intermittent": { "technologies": [ "Offline-capable sync layer" ], "technologyProperties": { "connectivityRequirement": "Offline-first with sync", "offlineCapability": "Store-and-forward when connected" } }, "2g-only": { "technologies": [ "USSD/SMS interface", "Offline-capable sync layer" ], "technologyProperties": { "connectivityRequirement": "Zero-data capable", "offlineCapability": "USSD/SMS fallback required" } }, "no-internet": { "technologies": [ "USSD/SMS-based transaction layer" ], "technologyProperties": { "connectivityRequirement": "SMS/USSD only", "offlineCapability": "Full USSD operation" } }, "offline": { "technologies": [ "Offline transaction capability", "Bluetooth/NFC peer-to-peer" ], "technologyProperties": { "connectivityRequirement": "Fully offline", "offlineCapability": "Local device storage with periodic batch sync" } } }, "prefillFrom": "P0-connectivity", "briefSection": "Infrastructure requirements", "text": "What is the typical internet connectivity like in your last-mile delivery areas?", "ngoText": "What is the typical internet connectivity like in your last-mile delivery areas?" }, { "id": "reporting-needs", "type": "multiselect", "options": [ { "label": "Real-time transaction visibility for donors", "value": "realtime-donor" }, { "label": "Periodic summary reports (monthly/quarterly)", "value": "periodic-reports" }, { "label": "Full audit trail: every transaction traceable end-to-end", "value": "full-audit" }, { "label": "Proof of delivery to individual beneficiaries", "value": "proof-of-delivery" }, { "label": "Compliance/sanctions screening logs", "value": "compliance-logs" }, { "label": "Minimal: standard financial reporting only", "value": "minimal" } ], "propertyMapping": { "realtime-donor": { "technologies": [ "Donor reporting dashboard", "Real-time transaction feed" ], "technologyProperties": { "reportingCapability": "Real-time donor portal", "dataVisibility": "Per-transaction" } }, "periodic-reports": { "technologies": [ "Automated report generation" ], "technologyProperties": { "reportingCapability": "Scheduled report export", "dataVisibility": "Aggregated" } }, "full-audit": { "technologies": [ "Immutable audit trail", "Transaction explorer" ], "technologyProperties": { "reportingCapability": "End-to-end transaction tracing", "dataVisibility": "Full chain of custody" } }, "proof-of-delivery": { "technologies": [ "Delivery confirmation module" ], "technologyProperties": { "reportingCapability": "Beneficiary receipt confirmation", "dataVisibility": "Per-beneficiary" } }, "compliance-logs": { "technologies": [ "Compliance audit log" ], "technologyProperties": { "reportingCapability": "Screening decision records", "dataVisibility": "Per-transaction compliance" } }, "minimal": { "technologies": [], "technologyProperties": { "reportingCapability": "Standard financial reports", "dataVisibility": "Summary level" } } }, "prefillFrom": "P2-CatA-Q29", "briefSection": "Reporting and audit", "text": "What reporting or audit trail do donors require for these payments?", "ngoText": "What reporting or audit trail do donors require for these payments?" }, { "id": "sq-UC-A-001-001", "type": "single-select", "options": [ { "value": "zero-tolerance", "label": "Zero tolerance: all failures escalated immediately" }, { "value": "under-5-percent", "label": "Under 5% failure rate acceptable" }, { "value": "under-10-percent", "label": "Under 10% failure rate acceptable" }, { "value": "best-effort", "label": "Best effort: no specific threshold" } ], "propertyMapping": { "zero-tolerance": { "technologies": [ "payment-monitoring", "real-time-alerts" ], "technologyProperties": {} }, "under-5-percent": { "technologies": [ "payment-monitoring", "retry-engine" ], "technologyProperties": {} }, "under-10-percent": { "technologies": [ "payment-monitoring", "batch-reconciliation" ], "technologyProperties": {} }, "best-effort": { "technologies": [ "basic-logging" ], "technologyProperties": {} } }, "briefSection": "operations", "text": "What is the acceptable failed-payment rate before manual intervention is triggered?", "ngoText": "What is the acceptable failed-payment rate before manual intervention is triggered?" }, { "id": "sq-UC-A-001-003", "type": "single-select", "options": [ { "value": "real-time-settlement", "label": "Real-time settlement confirmation" }, { "value": "daily-batch", "label": "Daily batch reconciliation" }, { "value": "weekly-summary", "label": "Weekly summary reports" }, { "value": "monthly-aggregate", "label": "Monthly aggregate reporting" } ], "propertyMapping": { "real-time-settlement": { "technologies": [ "settlement-finality", "blockchain-verification" ], "technologyProperties": {} }, "daily-batch": { "technologies": [ "batch-reconciliation", "daily-export" ], "technologyProperties": {} }, "weekly-summary": { "technologies": [ "weekly-report-automation", "data-aggregation" ], "technologyProperties": {} }, "monthly-aggregate": { "technologies": [ "monthly-reporting", "data-aggregation" ], "technologyProperties": {} } }, "briefSection": "compliance", "prefillFrom": "P2-CatA-Q8a", "text": "What reconciliation frequency do you need with your payment service providers?", "ngoText": "What reconciliation frequency do you need with your payment service providers?" }, { "id": "beneficiary-choice", "label": "How will beneficiaries exercise choice in how they receive and use this service?", "type": "select", "briefSection": "End-user interface", "options": [ { "label": "Beneficiaries choose between delivery methods (cash, voucher, mobile money, direct)", "value": "delivery-choice" }, { "label": "Beneficiaries choose preferred merchants or service points", "value": "merchant-choice" }, { "label": "Beneficiaries control their own data sharing preferences", "value": "data-choice" }, { "label": "Multiple choice dimensions (delivery + merchant + data)", "value": "full-choice" }, { "label": "Limited choice: programme constraints determine delivery", "value": "limited" } ], "propertyMapping": { "delivery-choice": { "technologies": [], "technologyProperties": { "beneficiaryChoice": "Delivery method choice", "dignityDesign": "Beneficiaries select preferred receipt method" } }, "merchant-choice": { "technologies": [], "technologyProperties": { "beneficiaryChoice": "Merchant/service point choice", "dignityDesign": "Beneficiaries select where to redeem" } }, "data-choice": { "technologies": [], "technologyProperties": { "beneficiaryChoice": "Data sharing choice", "dignityDesign": "Beneficiaries control personal data sharing" } }, "full-choice": { "technologies": [], "technologyProperties": { "beneficiaryChoice": "Multi-dimensional choice", "dignityDesign": "Full beneficiary agency across delivery, merchant, and data" } }, "limited": { "technologies": [], "technologyProperties": { "beneficiaryChoice": "Limited by programme design", "dignityDesign": "Programme constraints; beneficiary informed of reasons" } } }, "text": "How will beneficiaries exercise choice in how they receive and use this service?" } ], "complexityFactors": { "relationships": 2, "operationalChange": 2, "dataCompliance": 3 }, "securityTier": "B", "suggestedCriteria": [ { "id": "SC-CORRIDOR", "name": "Corridor Coverage & Last-Mile Reach", "description": "Does the provider operate in the specific country corridors this programme requires? Can they reach beneficiaries in remote or underserved areas through mobile money, cash agents, or bank transfers?", "weight": 0.3, "ratingGuide": { "5": "Active in all required corridors with multiple last-mile delivery options (mobile money, cash agents, bank transfer). Proven reach in rural and refugee camp settings.", "4": "Covers most required corridors. At least two last-mile options. Some remote area experience.", "3": "Covers major corridors but gaps in one or two. Single last-mile method in some locations.", "2": "Limited corridor coverage. Only bank transfer or single mobile money provider. No remote area experience.", "1": "Minimal geographic coverage. No presence in required operating regions. No last-mile infrastructure." } }, { "id": "SC-SPEED", "name": "Settlement Speed", "description": "This measures how quickly funds reach the beneficiary after disbursement is authorised. For emergency and regular cash transfers, speed directly affects programme effectiveness.", "weight": 0.2, "ratingGuide": { "5": "Same-day settlement in all corridors. Near-instant for mobile money recipients. No manual reconciliation delays.", "4": "Same-day in most corridors. Next-day for complex routes. Minimal manual steps.", "3": "1-2 business days in most corridors. Some manual reconciliation required.", "2": "3-5 business days. Multiple intermediary steps. Manual reconciliation common.", "1": "Over 5 business days. Relies on traditional banking rails with no blockchain acceleration." } }, { "id": "SC-COST", "name": "Total Transfer Cost", "description": "All-in cost per transfer including network fees, FX spread, on/off-ramp charges, and any platform fees. For aid disbursements, every percentage point of cost is money not reaching beneficiaries.", "weight": 0.2, "ratingGuide": { "5": "Under 1% total cost including FX. Transparent fee structure. No hidden charges. Volume discounts available.", "4": "1-2% total cost. Clear fee breakdown. Competitive FX rates.", "3": "2-4% total cost. Some fee components unclear. Moderate FX spread.", "2": "4-7% total cost. Complex fee structure. Poor FX rates on minor corridors.", "1": "Over 7% total cost. Opaque pricing. Worse than existing banking alternatives." } }, { "id": "SC-COMPLIANCE-KYC", "name": "Regulatory Compliance & Sanctions Screening", "description": "The provider handles KYC/AML compliance and sanctions screening for the operating jurisdictions. For cross-border humanitarian payments, compliance failure can shut down entire programmes.", "weight": 0.2, "ratingGuide": { "5": "Licensed money transmitter in required jurisdictions. Automated sanctions screening. KYC processes adapted for displaced populations (accepts alternative documentation). Regulatory relationships established.", "4": "Licensed in most jurisdictions. Automated screening. Standard KYC with some flexibility for humanitarian context.", "3": "Licensed in key jurisdictions. Manual screening processes. Standard KYC only \u2014 no humanitarian adaptations.", "2": "Limited licensing. Relies on partner for compliance. No experience with humanitarian population KYC challenges.", "1": "No money transmission licenses. No sanctions screening. Significant compliance risk." } }, { "id": "SC-HUMANITARIAN-XP", "name": "Humanitarian Deployment Experience", "description": "The provider has deployed cross-border payment solutions in humanitarian contexts. Understanding of NGO procurement, donor reporting requirements, and field operational constraints matters as much as technology.", "weight": 0.1, "ratingGuide": { "5": "Active humanitarian cash transfer deployments at scale (e.g. WFP, UNHCR, major INGO partnerships). Understands donor reporting, beneficiary protection, and field constraints.", "4": "Deployed in humanitarian context with at least one major programme. Good understanding of NGO operational requirements.", "3": "Deployed in developing markets but not specifically humanitarian. Willing to adapt.", "2": "Primarily commercial focus. Limited understanding of humanitarian operating environment.", "1": "No developing market or humanitarian experience. Purely commercial/retail product." } } ], "procurement": { "marketMaturity": "mature", "primaryMode": "tender", "alternativeModes": [ "off-the-shelf", "integrator-led" ], "reasoning": "Multiple competing humanitarian payment platforms (humanitarian SDPs, mobile money rails, fintech disbursement); buy-not-build dominant.", "exampleProductCategories": [ "humanitarian-payment-platform", "stablecoin-disbursement-rails", "mobile-money-aggregator" ], "partnerChannels": [], "lastReviewed": "2026-05-01" } }, { "id": "UC-A-002", "name": "Staff salary payments across jurisdictions", "category": "A", "subcategory": "Cross-Border Payments and Transfers", "description": "Pay staff in several countries on time and at lower cost, without delays from banks or compliance holds along the way.", "bCriteria": [ "B4", "B5" ], "requiredComponents": [ { "component": "payment-rails", "description": "Blockchain network for settlement" }, { "component": "stablecoin", "description": "Stablecoin for salary denomination" }, { "component": "off-ramp", "description": "Crypto to local currency conversion" }, { "component": "staff-wallet", "description": "Wallet infrastructure for staff" }, { "component": "compliance-screening", "description": "Tax and regulatory compliance" } ], "conditionalComponents": [ { "component": "identity-verification", "condition": "For KYC and tax registration", "linksTo": "UC-B-029" }, { "component": "accounting-integration", "condition": "If linked to payroll systems" } ], "crossCategoryDependencies": [ "UC-B-029 for staff credential verification" ], "p2TriggerConditions": { "description": "Activated when P2 shows multiple country offices + manual payroll processing + frequent delays", "rangeSignals": [ "countries >= 3", "payrollFrequency >= bi-weekly", "processingTime >= 5 days" ] }, "contextFieldsTemplate": [ { "field": "staffCount", "source": "P0 organisational size", "description": "Number of staff across countries" }, { "field": "countries", "source": "P0 operations", "description": "Countries with staff" }, { "field": "payrollFrequency", "source": "P2 payroll practices", "description": "How often staff are paid" }, { "field": "taxCompliance", "source": "P0 Q19-21", "description": "Tax requirements per country" } ], "implementationComplexity": "medium", "examples": { "note": "Humanitarian organizations with multi-country presence", "references": [ { "name": "AZA Finance (BitPesa)", "url": "https://azafinance.com/", "solved": "Reduced cost and time for cross-border business payments across Africa" }, { "name": "Stellar / IBM World Wire", "url": "https://www.ibm.com/think/topics/cross-border-payments-blockchain", "solved": "Handled cross-border settlement and FX in multiple currencies in near real time" } ] }, "solutionQuestions": [ { "id": "corridor-count", "type": "select", "options": [ { "label": "Single country", "value": "single" }, { "label": "2\u20133 countries", "value": "2-3" }, { "label": "4\u20135 countries", "value": "4-5" }, { "label": "More than 5 countries", "value": "5-plus" } ], "propertyMapping": { "single": { "technologies": [ "Single-corridor fiat on-ramp" ], "technologyProperties": { "corridorComplexity": "Single origination country", "multiRailNeeded": "No" } }, "2-3": { "technologies": [ "Multi-corridor fiat on-ramp gateway" ], "technologyProperties": { "corridorComplexity": "2\u20133 origination countries", "multiRailNeeded": "Yes \u2014 2-3 payment rails" } }, "4-5": { "technologies": [ "Multi-corridor fiat on-ramp gateway" ], "technologyProperties": { "corridorComplexity": "4\u20135 origination countries", "multiRailNeeded": "Yes \u2014 4-5 payment rails" } }, "5-plus": { "technologies": [ "Enterprise multi-corridor on-ramp gateway" ], "technologyProperties": { "corridorComplexity": "5+ origination countries", "multiRailNeeded": "Yes \u2014 enterprise-grade multi-rail" } } }, "prefillFrom": null, "briefSection": "Payment rail requirements", "text": "How many countries does your organisation send transfer funds from?", "ngoText": "How many countries does your organisation send transfer funds from?" }, { "id": "origination-country-1", "type": "select", "options": [ { "label": "United States", "value": "united-states" }, { "label": "United Kingdom", "value": "united-kingdom" }, { "label": "Germany", "value": "germany" }, { "label": "Netherlands", "value": "netherlands" }, { "label": "Switzerland", "value": "switzerland" }, { "label": "Belgium", "value": "belgium" }, { "label": "France", "value": "france" }, { "label": "Sweden", "value": "sweden" }, { "label": "Norway", "value": "norway" }, { "label": "Denmark", "value": "denmark" }, { "label": "Canada", "value": "canada" }, { "label": "Australia", "value": "australia" }, { "label": "Japan", "value": "japan" }, { "label": "Ireland", "value": "ireland" }, { "label": "Italy", "value": "italy" }, { "label": "Spain", "value": "spain" }, { "label": "Austria", "value": "austria" }, { "label": "Finland", "value": "finland" }, { "label": "Luxembourg", "value": "luxembourg" }, { "label": "South Korea", "value": "south-korea" }, { "label": "New Zealand", "value": "new-zealand" }, { "label": "United Arab Emirates", "value": "united-arab-emirates" }, { "label": "Singapore", "value": "singapore" }, { "label": "Other", "value": "other" } ], "propertyMapping": { "united-states": { "technologies": [ "ACH/wire fiat on-ramp" ], "technologyProperties": { "onRampType": "ACH/Fedwire bank transfer", "onRampRegion": "United States", "settlementRail": "ACH / Fedwire" } }, "united-kingdom": { "technologies": [ "UK Faster Payments on-ramp" ], "technologyProperties": { "onRampType": "Faster Payments bank transfer", "onRampRegion": "United Kingdom", "settlementRail": "FPS / BACS" } }, "germany": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "netherlands": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "switzerland": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SIC/SEPA bank transfer", "onRampRegion": "Switzerland/EU", "settlementRail": "SIC / SEPA Credit Transfer" } }, "belgium": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "france": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "sweden": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "norway": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA-adjacent bank transfer", "onRampRegion": "EEA", "settlementRail": "SEPA Credit Transfer" } }, "denmark": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "canada": { "technologies": [ "Canadian EFT on-ramp" ], "technologyProperties": { "onRampType": "Interac/EFT bank transfer", "onRampRegion": "Canada", "settlementRail": "Interac / EFT" } }, "australia": { "technologies": [ "Australian NPP on-ramp" ], "technologyProperties": { "onRampType": "NPP bank transfer", "onRampRegion": "Australia", "settlementRail": "NPP / BECS" } }, "japan": { "technologies": [ "Japanese Zengin on-ramp" ], "technologyProperties": { "onRampType": "Zengin bank transfer", "onRampRegion": "Japan", "settlementRail": "Zengin System" } }, "ireland": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "italy": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "spain": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "austria": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "finland": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "luxembourg": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "south-korea": { "technologies": [ "Korean banking on-ramp" ], "technologyProperties": { "onRampType": "KFTC bank transfer", "onRampRegion": "South Korea", "settlementRail": "KFTC / BOK-Wire" } }, "new-zealand": { "technologies": [ "NZ banking on-ramp" ], "technologyProperties": { "onRampType": "SBI bank transfer", "onRampRegion": "New Zealand", "settlementRail": "SBI / ESAS" } }, "united-arab-emirates": { "technologies": [ "UAE banking on-ramp" ], "technologyProperties": { "onRampType": "UAEFTS bank transfer", "onRampRegion": "United Arab Emirates", "settlementRail": "UAEFTS / IPP" } }, "singapore": { "technologies": [ "Singapore FAST on-ramp" ], "technologyProperties": { "onRampType": "FAST bank transfer", "onRampRegion": "Singapore", "settlementRail": "FAST / MEPS+" } }, "other": { "technologies": [ "Regional fiat on-ramp" ], "technologyProperties": { "onRampType": "Local rail bank transfer", "onRampRegion": "Region-specific", "settlementRail": "Local payment network" } } }, "showIf": { "questionId": "corridor-count", "minValue": "single" }, "prefillFrom": null, "briefSection": "Payment rail requirements", "text": "Which country do you most frequently initiate transfers from?", "ngoText": "Which country do you most frequently initiate transfers from?" }, { "id": "origination-country-2", "type": "select", "options": [ { "label": "United States", "value": "united-states" }, { "label": "United Kingdom", "value": "united-kingdom" }, { "label": "Germany", "value": "germany" }, { "label": "Netherlands", "value": "netherlands" }, { "label": "Switzerland", "value": "switzerland" }, { "label": "Belgium", "value": "belgium" }, { "label": "France", "value": "france" }, { "label": "Sweden", "value": "sweden" }, { "label": "Norway", "value": "norway" }, { "label": "Denmark", "value": "denmark" }, { "label": "Canada", "value": "canada" }, { "label": "Australia", "value": "australia" }, { "label": "Japan", "value": "japan" }, { "label": "Ireland", "value": "ireland" }, { "label": "Italy", "value": "italy" }, { "label": "Spain", "value": "spain" }, { "label": "Austria", "value": "austria" }, { "label": "Finland", "value": "finland" }, { "label": "Luxembourg", "value": "luxembourg" }, { "label": "South Korea", "value": "south-korea" }, { "label": "New Zealand", "value": "new-zealand" }, { "label": "United Arab Emirates", "value": "united-arab-emirates" }, { "label": "Singapore", "value": "singapore" }, { "label": "Other", "value": "other" } ], "propertyMapping": { "united-states": { "technologies": [ "ACH/wire fiat on-ramp" ], "technologyProperties": { "onRampType": "ACH/Fedwire bank transfer", "onRampRegion": "United States", "settlementRail": "ACH / Fedwire" } }, "united-kingdom": { "technologies": [ "UK Faster Payments on-ramp" ], "technologyProperties": { "onRampType": "Faster Payments bank transfer", "onRampRegion": "United Kingdom", "settlementRail": "FPS / BACS" } }, "germany": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "netherlands": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "switzerland": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SIC/SEPA bank transfer", "onRampRegion": "Switzerland/EU", "settlementRail": "SIC / SEPA Credit Transfer" } }, "belgium": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "france": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "sweden": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "norway": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA-adjacent bank transfer", "onRampRegion": "EEA", "settlementRail": "SEPA Credit Transfer" } }, "denmark": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "canada": { "technologies": [ "Canadian EFT on-ramp" ], "technologyProperties": { "onRampType": "Interac/EFT bank transfer", "onRampRegion": "Canada", "settlementRail": "Interac / EFT" } }, "australia": { "technologies": [ "Australian NPP on-ramp" ], "technologyProperties": { "onRampType": "NPP bank transfer", "onRampRegion": "Australia", "settlementRail": "NPP / BECS" } }, "japan": { "technologies": [ "Japanese Zengin on-ramp" ], "technologyProperties": { "onRampType": "Zengin bank transfer", "onRampRegion": "Japan", "settlementRail": "Zengin System" } }, "ireland": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "italy": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "spain": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "austria": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "finland": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "luxembourg": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "south-korea": { "technologies": [ "Korean banking on-ramp" ], "technologyProperties": { "onRampType": "KFTC bank transfer", "onRampRegion": "South Korea", "settlementRail": "KFTC / BOK-Wire" } }, "new-zealand": { "technologies": [ "NZ banking on-ramp" ], "technologyProperties": { "onRampType": "SBI bank transfer", "onRampRegion": "New Zealand", "settlementRail": "SBI / ESAS" } }, "united-arab-emirates": { "technologies": [ "UAE banking on-ramp" ], "technologyProperties": { "onRampType": "UAEFTS bank transfer", "onRampRegion": "United Arab Emirates", "settlementRail": "UAEFTS / IPP" } }, "singapore": { "technologies": [ "Singapore FAST on-ramp" ], "technologyProperties": { "onRampType": "FAST bank transfer", "onRampRegion": "Singapore", "settlementRail": "FAST / MEPS+" } }, "other": { "technologies": [ "Regional fiat on-ramp" ], "technologyProperties": { "onRampType": "Local rail bank transfer", "onRampRegion": "Region-specific", "settlementRail": "Local payment network" } } }, "showIf": { "questionId": "corridor-count", "minValue": "2-3" }, "prefillFrom": null, "briefSection": "Payment rail requirements", "text": "Second most common transfer origination country (if applicable)", "ngoText": "Second most common transfer origination country (if applicable)" }, { "id": "origination-country-3", "type": "select", "options": [ { "label": "United States", "value": "united-states" }, { "label": "United Kingdom", "value": "united-kingdom" }, { "label": "Germany", "value": "germany" }, { "label": "Netherlands", "value": "netherlands" }, { "label": "Switzerland", "value": "switzerland" }, { "label": "Belgium", "value": "belgium" }, { "label": "France", "value": "france" }, { "label": "Sweden", "value": "sweden" }, { "label": "Norway", "value": "norway" }, { "label": "Denmark", "value": "denmark" }, { "label": "Canada", "value": "canada" }, { "label": "Australia", "value": "australia" }, { "label": "Japan", "value": "japan" }, { "label": "Ireland", "value": "ireland" }, { "label": "Italy", "value": "italy" }, { "label": "Spain", "value": "spain" }, { "label": "Austria", "value": "austria" }, { "label": "Finland", "value": "finland" }, { "label": "Luxembourg", "value": "luxembourg" }, { "label": "South Korea", "value": "south-korea" }, { "label": "New Zealand", "value": "new-zealand" }, { "label": "United Arab Emirates", "value": "united-arab-emirates" }, { "label": "Singapore", "value": "singapore" }, { "label": "Other", "value": "other" } ], "propertyMapping": { "united-states": { "technologies": [ "ACH/wire fiat on-ramp" ], "technologyProperties": { "onRampType": "ACH/Fedwire bank transfer", "onRampRegion": "United States", "settlementRail": "ACH / Fedwire" } }, "united-kingdom": { "technologies": [ "UK Faster Payments on-ramp" ], "technologyProperties": { "onRampType": "Faster Payments bank transfer", "onRampRegion": "United Kingdom", "settlementRail": "FPS / BACS" } }, "germany": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "netherlands": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "switzerland": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SIC/SEPA bank transfer", "onRampRegion": "Switzerland/EU", "settlementRail": "SIC / SEPA Credit Transfer" } }, "belgium": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "france": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "sweden": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "norway": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA-adjacent bank transfer", "onRampRegion": "EEA", "settlementRail": "SEPA Credit Transfer" } }, "denmark": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "canada": { "technologies": [ "Canadian EFT on-ramp" ], "technologyProperties": { "onRampType": "Interac/EFT bank transfer", "onRampRegion": "Canada", "settlementRail": "Interac / EFT" } }, "australia": { "technologies": [ "Australian NPP on-ramp" ], "technologyProperties": { "onRampType": "NPP bank transfer", "onRampRegion": "Australia", "settlementRail": "NPP / BECS" } }, "japan": { "technologies": [ "Japanese Zengin on-ramp" ], "technologyProperties": { "onRampType": "Zengin bank transfer", "onRampRegion": "Japan", "settlementRail": "Zengin System" } }, "ireland": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "italy": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "spain": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "austria": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "finland": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "luxembourg": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "south-korea": { "technologies": [ "Korean banking on-ramp" ], "technologyProperties": { "onRampType": "KFTC bank transfer", "onRampRegion": "South Korea", "settlementRail": "KFTC / BOK-Wire" } }, "new-zealand": { "technologies": [ "NZ banking on-ramp" ], "technologyProperties": { "onRampType": "SBI bank transfer", "onRampRegion": "New Zealand", "settlementRail": "SBI / ESAS" } }, "united-arab-emirates": { "technologies": [ "UAE banking on-ramp" ], "technologyProperties": { "onRampType": "UAEFTS bank transfer", "onRampRegion": "United Arab Emirates", "settlementRail": "UAEFTS / IPP" } }, "singapore": { "technologies": [ "Singapore FAST on-ramp" ], "technologyProperties": { "onRampType": "FAST bank transfer", "onRampRegion": "Singapore", "settlementRail": "FAST / MEPS+" } }, "other": { "technologies": [ "Regional fiat on-ramp" ], "technologyProperties": { "onRampType": "Local rail bank transfer", "onRampRegion": "Region-specific", "settlementRail": "Local payment network" } } }, "showIf": { "questionId": "corridor-count", "minValue": "2-3" }, "prefillFrom": null, "briefSection": "Payment rail requirements", "text": "Third transfer origination country (if applicable)", "ngoText": "Third transfer origination country (if applicable)" }, { "id": "origination-country-4", "type": "select", "options": [ { "label": "United States", "value": "united-states" }, { "label": "United Kingdom", "value": "united-kingdom" }, { "label": "Germany", "value": "germany" }, { "label": "Netherlands", "value": "netherlands" }, { "label": "Switzerland", "value": "switzerland" }, { "label": "Belgium", "value": "belgium" }, { "label": "France", "value": "france" }, { "label": "Sweden", "value": "sweden" }, { "label": "Norway", "value": "norway" }, { "label": "Denmark", "value": "denmark" }, { "label": "Canada", "value": "canada" }, { "label": "Australia", "value": "australia" }, { "label": "Japan", "value": "japan" }, { "label": "Ireland", "value": "ireland" }, { "label": "Italy", "value": "italy" }, { "label": "Spain", "value": "spain" }, { "label": "Austria", "value": "austria" }, { "label": "Finland", "value": "finland" }, { "label": "Luxembourg", "value": "luxembourg" }, { "label": "South Korea", "value": "south-korea" }, { "label": "New Zealand", "value": "new-zealand" }, { "label": "United Arab Emirates", "value": "united-arab-emirates" }, { "label": "Singapore", "value": "singapore" }, { "label": "Other", "value": "other" } ], "propertyMapping": { "united-states": { "technologies": [ "ACH/wire fiat on-ramp" ], "technologyProperties": { "onRampType": "ACH/Fedwire bank transfer", "onRampRegion": "United States", "settlementRail": "ACH / Fedwire" } }, "united-kingdom": { "technologies": [ "UK Faster Payments on-ramp" ], "technologyProperties": { "onRampType": "Faster Payments bank transfer", "onRampRegion": "United Kingdom", "settlementRail": "FPS / BACS" } }, "germany": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "netherlands": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "switzerland": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SIC/SEPA bank transfer", "onRampRegion": "Switzerland/EU", "settlementRail": "SIC / SEPA Credit Transfer" } }, "belgium": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "france": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "sweden": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "norway": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA-adjacent bank transfer", "onRampRegion": "EEA", "settlementRail": "SEPA Credit Transfer" } }, "denmark": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "canada": { "technologies": [ "Canadian EFT on-ramp" ], "technologyProperties": { "onRampType": "Interac/EFT bank transfer", "onRampRegion": "Canada", "settlementRail": "Interac / EFT" } }, "australia": { "technologies": [ "Australian NPP on-ramp" ], "technologyProperties": { "onRampType": "NPP bank transfer", "onRampRegion": "Australia", "settlementRail": "NPP / BECS" } }, "japan": { "technologies": [ "Japanese Zengin on-ramp" ], "technologyProperties": { "onRampType": "Zengin bank transfer", "onRampRegion": "Japan", "settlementRail": "Zengin System" } }, "ireland": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "italy": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "spain": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "austria": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "finland": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "luxembourg": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "south-korea": { "technologies": [ "Korean banking on-ramp" ], "technologyProperties": { "onRampType": "KFTC bank transfer", "onRampRegion": "South Korea", "settlementRail": "KFTC / BOK-Wire" } }, "new-zealand": { "technologies": [ "NZ banking on-ramp" ], "technologyProperties": { "onRampType": "SBI bank transfer", "onRampRegion": "New Zealand", "settlementRail": "SBI / ESAS" } }, "united-arab-emirates": { "technologies": [ "UAE banking on-ramp" ], "technologyProperties": { "onRampType": "UAEFTS bank transfer", "onRampRegion": "United Arab Emirates", "settlementRail": "UAEFTS / IPP" } }, "singapore": { "technologies": [ "Singapore FAST on-ramp" ], "technologyProperties": { "onRampType": "FAST bank transfer", "onRampRegion": "Singapore", "settlementRail": "FAST / MEPS+" } }, "other": { "technologies": [ "Regional fiat on-ramp" ], "technologyProperties": { "onRampType": "Local rail bank transfer", "onRampRegion": "Region-specific", "settlementRail": "Local payment network" } } }, "showIf": { "questionId": "corridor-count", "minValue": "4-5" }, "prefillFrom": null, "briefSection": "Payment rail requirements", "text": "Fourth transfer origination country (if applicable)", "ngoText": "Fourth transfer origination country (if applicable)" }, { "id": "origination-country-5", "type": "select", "options": [ { "label": "United States", "value": "united-states" }, { "label": "United Kingdom", "value": "united-kingdom" }, { "label": "Germany", "value": "germany" }, { "label": "Netherlands", "value": "netherlands" }, { "label": "Switzerland", "value": "switzerland" }, { "label": "Belgium", "value": "belgium" }, { "label": "France", "value": "france" }, { "label": "Sweden", "value": "sweden" }, { "label": "Norway", "value": "norway" }, { "label": "Denmark", "value": "denmark" }, { "label": "Canada", "value": "canada" }, { "label": "Australia", "value": "australia" }, { "label": "Japan", "value": "japan" }, { "label": "Ireland", "value": "ireland" }, { "label": "Italy", "value": "italy" }, { "label": "Spain", "value": "spain" }, { "label": "Austria", "value": "austria" }, { "label": "Finland", "value": "finland" }, { "label": "Luxembourg", "value": "luxembourg" }, { "label": "South Korea", "value": "south-korea" }, { "label": "New Zealand", "value": "new-zealand" }, { "label": "United Arab Emirates", "value": "united-arab-emirates" }, { "label": "Singapore", "value": "singapore" }, { "label": "Other", "value": "other" } ], "propertyMapping": { "united-states": { "technologies": [ "ACH/wire fiat on-ramp" ], "technologyProperties": { "onRampType": "ACH/Fedwire bank transfer", "onRampRegion": "United States", "settlementRail": "ACH / Fedwire" } }, "united-kingdom": { "technologies": [ "UK Faster Payments on-ramp" ], "technologyProperties": { "onRampType": "Faster Payments bank transfer", "onRampRegion": "United Kingdom", "settlementRail": "FPS / BACS" } }, "germany": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "netherlands": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "switzerland": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SIC/SEPA bank transfer", "onRampRegion": "Switzerland/EU", "settlementRail": "SIC / SEPA Credit Transfer" } }, "belgium": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "france": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "sweden": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "norway": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA-adjacent bank transfer", "onRampRegion": "EEA", "settlementRail": "SEPA Credit Transfer" } }, "denmark": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "canada": { "technologies": [ "Canadian EFT on-ramp" ], "technologyProperties": { "onRampType": "Interac/EFT bank transfer", "onRampRegion": "Canada", "settlementRail": "Interac / EFT" } }, "australia": { "technologies": [ "Australian NPP on-ramp" ], "technologyProperties": { "onRampType": "NPP bank transfer", "onRampRegion": "Australia", "settlementRail": "NPP / BECS" } }, "japan": { "technologies": [ "Japanese Zengin on-ramp" ], "technologyProperties": { "onRampType": "Zengin bank transfer", "onRampRegion": "Japan", "settlementRail": "Zengin System" } }, "ireland": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "italy": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "spain": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "austria": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "finland": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "luxembourg": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "south-korea": { "technologies": [ "Korean banking on-ramp" ], "technologyProperties": { "onRampType": "KFTC bank transfer", "onRampRegion": "South Korea", "settlementRail": "KFTC / BOK-Wire" } }, "new-zealand": { "technologies": [ "NZ banking on-ramp" ], "technologyProperties": { "onRampType": "SBI bank transfer", "onRampRegion": "New Zealand", "settlementRail": "SBI / ESAS" } }, "united-arab-emirates": { "technologies": [ "UAE banking on-ramp" ], "technologyProperties": { "onRampType": "UAEFTS bank transfer", "onRampRegion": "United Arab Emirates", "settlementRail": "UAEFTS / IPP" } }, "singapore": { "technologies": [ "Singapore FAST on-ramp" ], "technologyProperties": { "onRampType": "FAST bank transfer", "onRampRegion": "Singapore", "settlementRail": "FAST / MEPS+" } }, "other": { "technologies": [ "Regional fiat on-ramp" ], "technologyProperties": { "onRampType": "Local rail bank transfer", "onRampRegion": "Region-specific", "settlementRail": "Local payment network" } } }, "showIf": { "questionId": "corridor-count", "minValue": "4-5" }, "prefillFrom": null, "briefSection": "Payment rail requirements", "text": "Fifth transfer origination country (if applicable)", "ngoText": "Fifth transfer origination country (if applicable)" }, { "id": "funding-method", "type": "select", "options": [ { "label": "Bank transfer from organisation account", "value": "bank-transfer" }, { "label": "Card payment from organisation", "value": "card-payment" }, { "label": "Direct stablecoin funding (organisation already holds stablecoins)", "value": "direct-stablecoin" }, { "label": "Mixed: bank transfer for most, card for urgent payments", "value": "mixed-methods" } ], "propertyMapping": { "bank-transfer": { "technologies": [ "Bank-integrated fiat on-ramp" ], "technologyProperties": { "fundingSource": "Organisation bank account", "onRampSpeed": "1-2 business days (SEPA/ACH) or same-day (Faster Payments/wire)", "kybRequired": "Yes \u2014 organisation KYB verification" } }, "card-payment": { "technologies": [ "Card payment on-ramp" ], "technologyProperties": { "fundingSource": "Organisation payment card", "onRampSpeed": "Near-instant", "kybRequired": "Yes \u2014 card verification and organisation KYB" } }, "direct-stablecoin": { "technologies": [ "Direct stablecoin treasury funding" ], "technologyProperties": { "fundingSource": "Existing stablecoin holdings", "onRampSpeed": "Immediate (no fiat conversion needed)", "kybRequired": "Wallet verification only" } }, "mixed-methods": { "technologies": [ "Multi-method fiat on-ramp", "Card payment on-ramp" ], "technologyProperties": { "fundingSource": "Bank transfer (primary) + card (urgent)", "onRampSpeed": "Varies by method", "kybRequired": "Yes \u2014 full organisation KYB" } } }, "prefillFrom": null, "briefSection": "Payment rail requirements", "text": "How does your organisation currently fund international transfers or payments?", "ngoText": "How does your organisation currently fund international transfers or payments?" }, { "id": "staff-headcount", "type": "select", "options": [ { "label": "Under 50 staff", "value": "small" }, { "label": "50\u2013200 staff", "value": "medium" }, { "label": "200\u20131,000 staff", "value": "large" }, { "label": "Over 1,000 staff", "value": "enterprise" } ], "propertyMapping": { "small": { "technologies": [ "Layer 1 payment rail" ], "technologyProperties": { "batchSize": "Small batch" } }, "medium": { "technologies": [ "Layer 1 payment rail", "Batch payment engine" ], "technologyProperties": { "batchSize": "Medium batch" } }, "large": { "technologies": [ "Layer 1 payment rail", "Batch payment engine" ], "technologyProperties": { "batchSize": "Large batch" } }, "enterprise": { "technologies": [ "Layer 1 payment rail", "Enterprise batch engine" ], "technologyProperties": { "batchSize": "Enterprise batch with queue management" } } }, "prefillFrom": "P0-orgSize", "briefSection": "Payment rail requirements", "text": "How many staff do you pay salaries to?", "ngoText": "How many staff do you pay salaries to?" }, { "id": "payroll-country-count", "type": "select", "options": [ { "label": "1 country only", "value": "single" }, { "label": "2\u20133 countries", "value": "few" }, { "label": "4\u201310 countries", "value": "multi" }, { "label": "Over 10 countries", "value": "global" } ], "propertyMapping": { "single": { "technologies": [], "technologyProperties": { "scalability": "Single jurisdiction" } }, "few": { "technologies": [], "technologyProperties": { "scalability": "Basic multi-country" } }, "multi": { "technologies": [ "Multi-jurisdiction compliance engine" ], "technologyProperties": { "scalability": "Enterprise multi-country" } }, "global": { "technologies": [ "Multi-jurisdiction compliance engine", "Automated FX conversion" ], "technologyProperties": { "scalability": "Enterprise-grade global" } } }, "briefSection": "Payment rail requirements", "text": "How many countries do you run payroll in?", "ngoText": "How many countries do you run payroll in?" }, { "id": "staff-bank-access", "type": "select", "options": [ { "label": "Yes, all staff have local bank accounts", "value": "all-banked" }, { "label": "Most do, but some in remote locations do not", "value": "mostly-banked" }, { "label": "Many staff lack formal bank accounts", "value": "many-unbanked" }, { "label": "Varies significantly by country", "value": "varies" } ], "propertyMapping": { "all-banked": { "technologies": [ "Bank-integrated off-ramp" ], "technologyProperties": { "deliveryMethod": "Direct bank deposit", "walletRequired": false } }, "mostly-banked": { "technologies": [ "Bank-integrated off-ramp", "Mobile money off-ramp" ], "technologyProperties": { "deliveryMethod": "Bank deposit with mobile money fallback", "walletRequired": "For unbanked staff" } }, "many-unbanked": { "technologies": [ "Embedded staff wallet", "Mobile money off-ramp", "Agent network" ], "technologyProperties": { "deliveryMethod": "Multi-channel (bank + wallet + agent)", "walletRequired": true } }, "varies": { "technologies": [ "Multi-channel payment delivery" ], "technologyProperties": { "deliveryMethod": "Country-specific routing", "walletRequired": "Per-country configuration" } } }, "prefillFrom": null, "briefSection": "Last-mile delivery", "text": "Do all staff have bank accounts in their country of employment?", "ngoText": "Do all staff have bank accounts in their country of employment?" }, { "id": "salary-frequency", "type": "select", "options": [ { "label": "Monthly", "value": "monthly" }, { "label": "Bi-weekly / Fortnightly", "value": "biweekly" }, { "label": "Weekly", "value": "weekly" }, { "label": "Varies by country or contract type", "value": "varies" } ], "propertyMapping": { "monthly": { "technologies": [], "technologyProperties": { "payrollCycle": "Monthly batch", "automationLevel": "Scheduled monthly" } }, "biweekly": { "technologies": [ "Automated payroll scheduler" ], "technologyProperties": { "payrollCycle": "Bi-weekly batch", "automationLevel": "Scheduled bi-weekly" } }, "weekly": { "technologies": [ "Automated payroll scheduler" ], "technologyProperties": { "payrollCycle": "Weekly batch", "automationLevel": "Scheduled weekly" } }, "varies": { "technologies": [ "Configurable payroll scheduler" ], "technologyProperties": { "payrollCycle": "Multi-schedule", "automationLevel": "Per-country configuration" } } }, "prefillFrom": null, "briefSection": "Payment operations", "text": "How frequently are staff paid?", "ngoText": "How frequently are staff paid?" }, { "id": "salary-range", "type": "select", "options": [ { "label": "Under $500/month", "value": "low" }, { "label": "$500\u2013$2,000/month", "value": "medium" }, { "label": "$2,000\u2013$5,000/month", "value": "high" }, { "label": "Over $5,000/month", "value": "very-high" }, { "label": "Wide range, from local hires to international staff", "value": "wide-range" } ], "propertyMapping": { "low": { "technologies": [ "Layer 1 payment rail" ], "technologyProperties": { "transactionFeeRequirement": "Sub-$0.10 per transaction", "fxSpreadTolerance": "Tight \u2014 fee-sensitive" } }, "medium": { "technologies": [ "Layer 1 payment rail" ], "technologyProperties": { "transactionFeeRequirement": "Sub-$0.50 per transaction", "fxSpreadTolerance": "Moderate" } }, "high": { "technologies": [ "Layer 1 payment rail" ], "technologyProperties": { "transactionFeeRequirement": "Sub-$1.00 per transaction", "fxSpreadTolerance": "Standard" } }, "very-high": { "technologies": [ "Layer 1 payment rail" ], "technologyProperties": { "transactionFeeRequirement": "Competitive", "fxSpreadTolerance": "Standard" } }, "wide-range": { "technologies": [ "Layer 1 payment rail" ], "technologyProperties": { "transactionFeeRequirement": "Fixed fee model (not percentage)", "fxSpreadTolerance": "Tight for low-salary staff" } } }, "prefillFrom": null, "briefSection": "Payment rail requirements", "text": "What is the typical salary range per payment (in USD equivalent)?", "ngoText": "What is the typical salary range per payment (in USD equivalent)?" }, { "id": "tax-compliance", "type": "select", "options": [ { "label": "Centralised: HQ calculates all deductions", "value": "centralised" }, { "label": "Decentralised: each country office handles locally", "value": "decentralised" }, { "label": "Outsourced to payroll provider per country", "value": "outsourced" }, { "label": "Inconsistent: no standardised process", "value": "inconsistent" } ], "propertyMapping": { "centralised": { "technologies": [ "Multi-jurisdiction tax calculation engine" ], "technologyProperties": { "taxHandling": "Centralised pre-deduction", "complianceModel": "HQ-controlled" } }, "decentralised": { "technologies": [ "Country-specific tax module" ], "technologyProperties": { "taxHandling": "Local office deduction", "complianceModel": "Country-office controlled" } }, "outsourced": { "technologies": [ "Payroll provider API integration" ], "technologyProperties": { "taxHandling": "Third-party calculated", "complianceModel": "Provider integration required" } }, "inconsistent": { "technologies": [ "Multi-jurisdiction tax calculation engine" ], "technologyProperties": { "taxHandling": "Needs standardisation", "complianceModel": "Centralised recommended" } } }, "prefillFrom": null, "briefSection": "Identity and compliance", "text": "How are tax withholding and statutory deductions currently handled across countries?", "ngoText": "How are tax withholding and statutory deductions currently handled across countries?" }, { "id": "payroll-system", "type": "multiselect", "options": [ { "label": "Enterprise ERP payroll module", "value": "sap" }, { "label": "Cloud HR and payroll suite", "value": "oracle" }, { "label": "Outsourced payroll provider", "value": "payroll-provider" }, { "label": "Custom internal system", "value": "custom" }, { "label": "Spreadsheet-based", "value": "spreadsheet" }, { "label": "No centralised payroll system", "value": "none" } ], "propertyMapping": { "sap": { "technologies": [ "Enterprise ERP payroll integration" ], "technologyProperties": { "payrollIntegration": "Enterprise ERP connection", "dataSync": "Automated bi-directional" } }, "oracle": { "technologies": [ "Cloud HR and payroll suite integration" ], "technologyProperties": { "payrollIntegration": "Cloud HR suite connection", "dataSync": "Automated bi-directional" } }, "payroll-provider": { "technologies": [ "Payroll provider API integration" ], "technologyProperties": { "payrollIntegration": "Provider API", "dataSync": "API-driven" } }, "custom": { "technologies": [ "Custom API integration" ], "technologyProperties": { "payrollIntegration": "Custom system connection", "dataSync": "Bespoke" } }, "spreadsheet": { "technologies": [ "CSV import/export module" ], "technologyProperties": { "payrollIntegration": "File-based import", "dataSync": "Manual upload" } }, "none": { "technologies": [], "technologyProperties": { "payrollIntegration": "Standalone", "dataSync": "Not applicable" } } }, "prefillFrom": "P0-S3-Q13", "briefSection": "Integration requirements", "text": "What payroll or HR system is currently used?", "ngoText": "What payroll or HR system is currently used?" }, { "id": "currency-salary", "type": "select", "options": [ { "label": "Denominated and paid in same local currency", "value": "same-currency" }, { "label": "Denominated in USD/EUR, paid in local currency", "value": "hq-to-local" }, { "label": "Mix: some in HQ currency, some in local", "value": "mixed" }, { "label": "Staff choose preferred currency", "value": "staff-choice" } ], "propertyMapping": { "same-currency": { "technologies": [ "Local currency stablecoin or off-ramp" ], "technologyProperties": { "fxConversion": "Single conversion at on-ramp", "currencyRisk": "Minimal" } }, "hq-to-local": { "technologies": [ "Automated FX conversion", "Multi-currency stablecoin" ], "technologyProperties": { "fxConversion": "HQ currency \u2192 stablecoin \u2192 local currency", "currencyRisk": "FX spread management needed" } }, "mixed": { "technologies": [ "Multi-currency stablecoin", "Configurable FX engine" ], "technologyProperties": { "fxConversion": "Per-employee routing", "currencyRisk": "Multi-currency management" } }, "staff-choice": { "technologies": [ "Multi-currency stablecoin", "Self-service currency selection" ], "technologyProperties": { "fxConversion": "Employee-selected at off-ramp", "currencyRisk": "Employee bears FX risk" } } }, "prefillFrom": null, "briefSection": "Stablecoin and FX", "text": "In what currency are salaries denominated vs. what currency do staff need to receive?", "ngoText": "In what currency are salaries denominated vs. what currency do staff need to receive?" }, { "id": "staff-device-access", "type": "select", "options": [ { "label": "All staff have smartphones", "value": "smartphone" }, { "label": "Most have smartphones, some feature phones", "value": "mostly-smartphone" }, { "label": "Mix of smartphones and feature phones", "value": "mixed" }, { "label": "Varies significantly by location", "value": "varies" } ], "propertyMapping": { "smartphone": { "technologies": [ "Mobile wallet application" ], "technologyProperties": { "interface": "Native mobile app", "offlineSync": "Optional" } }, "mostly-smartphone": { "technologies": [ "Mobile wallet application", "USSD fallback" ], "technologyProperties": { "interface": "Mobile app with USSD fallback", "offlineSync": "Recommended" } }, "mixed": { "technologies": [ "Multi-channel wallet platform" ], "technologyProperties": { "interface": "App + USSD", "offlineSync": "Required" } }, "varies": { "technologies": [ "Multi-channel wallet platform" ], "technologyProperties": { "interface": "Adaptive per location", "offlineSync": "Required" } } }, "prefillFrom": null, "briefSection": "End-user interface", "text": "What devices do staff typically have access to?", "ngoText": "What devices do staff typically have access to?" }, { "id": "sq-UC-A-002-001", "type": "single-select", "options": [ { "value": "per-country-audit-trail", "label": "Per-country audit trail" }, { "value": "centralised-global-audit", "label": "Centralised global audit" }, { "value": "donor-specific-audit", "label": "Donor-specific audit" }, { "value": "statutory-only", "label": "Statutory compliance only" } ], "propertyMapping": { "per-country-audit-trail": { "technologies": [ "local-compliance-logging", "multi-jurisdictional-tracking" ], "technologyProperties": {} }, "centralised-global-audit": { "technologies": [ "centralised-audit-ledger", "cross-border-reporting" ], "technologyProperties": {} }, "donor-specific-audit": { "technologies": [ "donor-reporting-engine", "audit-filtering" ], "technologyProperties": {} }, "statutory-only": { "technologies": [ "basic-compliance-logging" ], "technologyProperties": {} } }, "briefSection": "compliance", "text": "How is payroll data currently audited across jurisdictions for tax compliance?", "ngoText": "How is payroll data currently audited across jurisdictions for tax compliance?" }, { "id": "beneficiary-choice", "label": "How will beneficiaries exercise choice in how they receive and use this service?", "type": "select", "briefSection": "End-user interface", "options": [ { "label": "Beneficiaries choose between delivery methods (cash, voucher, mobile money, direct)", "value": "delivery-choice" }, { "label": "Beneficiaries choose preferred merchants or service points", "value": "merchant-choice" }, { "label": "Beneficiaries control their own data sharing preferences", "value": "data-choice" }, { "label": "Multiple choice dimensions (delivery + merchant + data)", "value": "full-choice" }, { "label": "Limited choice: programme constraints determine delivery", "value": "limited" } ], "propertyMapping": { "delivery-choice": { "technologies": [], "technologyProperties": { "beneficiaryChoice": "Delivery method choice", "dignityDesign": "Beneficiaries select preferred receipt method" } }, "merchant-choice": { "technologies": [], "technologyProperties": { "beneficiaryChoice": "Merchant/service point choice", "dignityDesign": "Beneficiaries select where to redeem" } }, "data-choice": { "technologies": [], "technologyProperties": { "beneficiaryChoice": "Data sharing choice", "dignityDesign": "Beneficiaries control personal data sharing" } }, "full-choice": { "technologies": [], "technologyProperties": { "beneficiaryChoice": "Multi-dimensional choice", "dignityDesign": "Full beneficiary agency across delivery, merchant, and data" } }, "limited": { "technologies": [], "technologyProperties": { "beneficiaryChoice": "Limited by programme design", "dignityDesign": "Programme constraints; beneficiary informed of reasons" } } }, "text": "How will beneficiaries exercise choice in how they receive and use this service?" } ], "complexityFactors": { "relationships": 2, "operationalChange": 2, "dataCompliance": 3 }, "securityTier": "B", "suggestedCriteria": [ { "id": "SC-PAYROLL-INT", "name": "Multi-Jurisdiction Payroll Integration", "description": "The provider can handle salary payments across multiple countries with different labour laws, tax withholding, and social security requirements. Must integrate with existing payroll systems.", "weight": 0.3, "ratingGuide": { "5": "Handles payroll in 10+ countries with automated tax withholding and statutory deductions. Direct integration with major payroll platforms (enterprise suites and local providers).", "4": "Handles 5-10 countries. Automated withholding in most. Integration available with major payroll systems.", "3": "Handles key jurisdictions but requires manual tax calculations in some. CSV import/export for payroll integration.", "2": "Limited to 2-3 countries. Manual withholding everywhere. No payroll system integration.", "1": "Single-country only. No awareness of multi-jurisdiction compliance requirements." } }, { "id": "SC-STAFF-DELIVERY", "name": "Staff Payment Delivery Options", "description": "Staff can receive salaries via their preferred method (bank transfer, mobile money, or wallet) regardless of country. Staff in different locations have different banking infrastructure.", "weight": 0.25, "ratingGuide": { "5": "Bank transfer, mobile money, and wallet options in all operating countries. Staff choose their preferred method. Automatic conversion to local currency.", "4": "Bank transfer and one alternative in most countries. Good local currency support.", "3": "Bank transfer in all countries. Mobile money in some. Limited alternative options.", "2": "Bank transfer only. Limited currency support. Manual conversion needed.", "1": "Single delivery method. Requires staff to have specific banking setup." } }, { "id": "SC-FX-RATE", "name": "Foreign Exchange Rates & Transparency", "description": "FX rates are competitive and transparent. For staff salaries, unfavourable rates directly reduce take-home pay, causing retention issues in competitive markets.", "weight": 0.2, "ratingGuide": { "5": "Mid-market rates with under 0.5% spread. Real-time rate locking. Full transparency on FX costs. Historical rate data available.", "4": "Competitive rates under 1% spread. Rate shown before confirmation. Clear cost breakdown.", "3": "Moderate rates 1-2% spread. Rate disclosed but not lockable. Some transparency.", "2": "High rates 2-4% spread. Rate applied at processing time. Limited visibility.", "1": "Opaque FX. Rates significantly worse than market. No transparency." } }, { "id": "SC-RELIABILITY", "name": "Payment Reliability & Timeliness", "description": "Payments are consistently delivered on schedule. Late salary payments cause staff hardship and erode organisational trust. The provider must be reliable month after month.", "weight": 0.15, "ratingGuide": { "5": "99.5%+ on-time delivery rate. Automated scheduling with advance notice of issues. Real-time status tracking per payment.", "4": "98%+ on-time. Good scheduling. Status tracking available with minor delays.", "3": "95%+ on-time. Occasional delays in complex corridors. Basic tracking.", "2": "Below 95%. Regular delays. Limited visibility into payment status.", "1": "Unreliable delivery. Frequent delays and failures. No tracking capability." } }, { "id": "SC-STAFF-DATA", "name": "Employee Data Protection", "description": "This looks at how employee financial data is handled. Salary information is sensitive. The provider must meet data protection requirements and prevent unauthorised access.", "weight": 0.1, "ratingGuide": { "5": "GDPR-compliant. Data encrypted at rest and in transit. Access controls per-role. Data residency options. Regular security audits.", "4": "Strong data protection. Encryption. Access controls. Compliant with major frameworks.", "3": "Basic data protection measures. Encryption in transit. Standard access controls.", "2": "Minimal data protection. No encryption at rest. Limited access controls.", "1": "No data protection framework. Employee financial data potentially exposed." } } ], "procurement": { "marketMaturity": "mature", "primaryMode": "off-the-shelf", "alternativeModes": [ "rfq" ], "reasoning": "Mature global payroll SaaS market; off-the-shelf comparison fits.", "exampleProductCategories": [ "global-payroll-saas", "contractor-payments-platform" ], "partnerChannels": [], "lastReviewed": "2026-05-01" } }, { "id": "UC-A-003", "name": "Vendor and supplier payments in remote locations", "category": "A", "subcategory": "Cross-Border Payments and Transfers", "description": "Pay suppliers in remote places without relying on cash or long chains of banks and agents, so they receive usable money quickly.", "bCriteria": [ "B3", "B4", "B5" ], "requiredComponents": [ { "component": "payment-rails", "description": "Blockchain settlement network" }, { "component": "stablecoin", "description": "Stablecoin for transactions" }, { "component": "on-ramp", "description": "Fiat to crypto conversion" }, { "component": "off-ramp", "description": "Crypto to local currency" }, { "component": "vendor-wallet", "description": "Vendor wallet management" }, { "component": "compliance-screening", "description": "Vendor AML/sanctions screening" } ], "conditionalComponents": [ { "component": "smart-contracts", "condition": "If payment conditions tied to delivery/inspection", "linksTo": "UC-A-012" }, { "component": "audit-mechanism", "linksTo": "UC-A-011", "condition": "If audit trail required for procurement verification" } ], "crossCategoryDependencies": [ "UC-D-063 if last-mile delivery verification needed" ], "p2TriggerConditions": { "description": "Activated when P2 shows difficulty reaching remote vendors + cash-based payments + high friction", "rangeSignals": [ "remoteVendors >= true", "paymentMethod = cash", "vendorAccessDifficulty >= high" ] }, "contextFieldsTemplate": [ { "field": "vendorCount", "source": "P2 supplier network", "description": "Number of active vendors" }, { "field": "remoteLocations", "source": "P0 operations + P4", "description": "Geographic distribution" }, { "field": "paymentFrequency", "source": "P2 procurement cycles", "description": "How often vendors are paid" }, { "field": "existingProcurement", "source": "P0 Q13", "description": "Current procurement systems" } ], "implementationComplexity": "medium", "examples": { "note": "UNHCR cash procurement, WFP vendor networks", "references": [ { "name": "WFP Building Blocks", "url": "https://www.wfp.org/building-blocks", "solved": "Transferred cash to refugee populations at scale, fast and at low cost" }, { "name": "AZA Finance (BitPesa)", "url": "https://azafinance.com/", "solved": "Reduced cost and time for cross-border business payments across Africa" } ] }, "solutionQuestions": [ { "id": "corridor-count", "type": "select", "options": [ { "label": "Single country", "value": "single" }, { "label": "2\u20133 countries", "value": "2-3" }, { "label": "4\u20135 countries", "value": "4-5" }, { "label": "More than 5 countries", "value": "5-plus" } ], "propertyMapping": { "single": { "technologies": [ "Single-corridor fiat on-ramp" ], "technologyProperties": { "corridorComplexity": "Single origination country", "multiRailNeeded": "No" } }, "2-3": { "technologies": [ "Multi-corridor fiat on-ramp gateway" ], "technologyProperties": { "corridorComplexity": "2\u20133 origination countries", "multiRailNeeded": "Yes \u2014 2-3 payment rails" } }, "4-5": { "technologies": [ "Multi-corridor fiat on-ramp gateway" ], "technologyProperties": { "corridorComplexity": "4\u20135 origination countries", "multiRailNeeded": "Yes \u2014 4-5 payment rails" } }, "5-plus": { "technologies": [ "Enterprise multi-corridor on-ramp gateway" ], "technologyProperties": { "corridorComplexity": "5+ origination countries", "multiRailNeeded": "Yes \u2014 enterprise-grade multi-rail" } } }, "prefillFrom": null, "briefSection": "Payment rail requirements", "text": "How many countries does your organisation send transfer funds from?", "ngoText": "How many countries does your organisation send transfer funds from?" }, { "id": "origination-country-1", "type": "select", "options": [ { "label": "United States", "value": "united-states" }, { "label": "United Kingdom", "value": "united-kingdom" }, { "label": "Germany", "value": "germany" }, { "label": "Netherlands", "value": "netherlands" }, { "label": "Switzerland", "value": "switzerland" }, { "label": "Belgium", "value": "belgium" }, { "label": "France", "value": "france" }, { "label": "Sweden", "value": "sweden" }, { "label": "Norway", "value": "norway" }, { "label": "Denmark", "value": "denmark" }, { "label": "Canada", "value": "canada" }, { "label": "Australia", "value": "australia" }, { "label": "Japan", "value": "japan" }, { "label": "Ireland", "value": "ireland" }, { "label": "Italy", "value": "italy" }, { "label": "Spain", "value": "spain" }, { "label": "Austria", "value": "austria" }, { "label": "Finland", "value": "finland" }, { "label": "Luxembourg", "value": "luxembourg" }, { "label": "South Korea", "value": "south-korea" }, { "label": "New Zealand", "value": "new-zealand" }, { "label": "United Arab Emirates", "value": "united-arab-emirates" }, { "label": "Singapore", "value": "singapore" }, { "label": "Other", "value": "other" } ], "propertyMapping": { "united-states": { "technologies": [ "ACH/wire fiat on-ramp" ], "technologyProperties": { "onRampType": "ACH/Fedwire bank transfer", "onRampRegion": "United States", "settlementRail": "ACH / Fedwire" } }, "united-kingdom": { "technologies": [ "UK Faster Payments on-ramp" ], "technologyProperties": { "onRampType": "Faster Payments bank transfer", "onRampRegion": "United Kingdom", "settlementRail": "FPS / BACS" } }, "germany": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "netherlands": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "switzerland": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SIC/SEPA bank transfer", "onRampRegion": "Switzerland/EU", "settlementRail": "SIC / SEPA Credit Transfer" } }, "belgium": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "france": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "sweden": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "norway": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA-adjacent bank transfer", "onRampRegion": "EEA", "settlementRail": "SEPA Credit Transfer" } }, "denmark": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "canada": { "technologies": [ "Canadian EFT on-ramp" ], "technologyProperties": { "onRampType": "Interac/EFT bank transfer", "onRampRegion": "Canada", "settlementRail": "Interac / EFT" } }, "australia": { "technologies": [ "Australian NPP on-ramp" ], "technologyProperties": { "onRampType": "NPP bank transfer", "onRampRegion": "Australia", "settlementRail": "NPP / BECS" } }, "japan": { "technologies": [ "Japanese Zengin on-ramp" ], "technologyProperties": { "onRampType": "Zengin bank transfer", "onRampRegion": "Japan", "settlementRail": "Zengin System" } }, "ireland": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "italy": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "spain": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "austria": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "finland": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "luxembourg": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "south-korea": { "technologies": [ "Korean banking on-ramp" ], "technologyProperties": { "onRampType": "KFTC bank transfer", "onRampRegion": "South Korea", "settlementRail": "KFTC / BOK-Wire" } }, "new-zealand": { "technologies": [ "NZ banking on-ramp" ], "technologyProperties": { "onRampType": "SBI bank transfer", "onRampRegion": "New Zealand", "settlementRail": "SBI / ESAS" } }, "united-arab-emirates": { "technologies": [ "UAE banking on-ramp" ], "technologyProperties": { "onRampType": "UAEFTS bank transfer", "onRampRegion": "United Arab Emirates", "settlementRail": "UAEFTS / IPP" } }, "singapore": { "technologies": [ "Singapore FAST on-ramp" ], "technologyProperties": { "onRampType": "FAST bank transfer", "onRampRegion": "Singapore", "settlementRail": "FAST / MEPS+" } }, "other": { "technologies": [ "Regional fiat on-ramp" ], "technologyProperties": { "onRampType": "Local rail bank transfer", "onRampRegion": "Region-specific", "settlementRail": "Local payment network" } } }, "showIf": { "questionId": "corridor-count", "minValue": "single" }, "prefillFrom": null, "briefSection": "Payment rail requirements", "text": "Which country do you most frequently initiate transfers from?", "ngoText": "Which country do you most frequently initiate transfers from?" }, { "id": "origination-country-2", "type": "select", "options": [ { "label": "United States", "value": "united-states" }, { "label": "United Kingdom", "value": "united-kingdom" }, { "label": "Germany", "value": "germany" }, { "label": "Netherlands", "value": "netherlands" }, { "label": "Switzerland", "value": "switzerland" }, { "label": "Belgium", "value": "belgium" }, { "label": "France", "value": "france" }, { "label": "Sweden", "value": "sweden" }, { "label": "Norway", "value": "norway" }, { "label": "Denmark", "value": "denmark" }, { "label": "Canada", "value": "canada" }, { "label": "Australia", "value": "australia" }, { "label": "Japan", "value": "japan" }, { "label": "Ireland", "value": "ireland" }, { "label": "Italy", "value": "italy" }, { "label": "Spain", "value": "spain" }, { "label": "Austria", "value": "austria" }, { "label": "Finland", "value": "finland" }, { "label": "Luxembourg", "value": "luxembourg" }, { "label": "South Korea", "value": "south-korea" }, { "label": "New Zealand", "value": "new-zealand" }, { "label": "United Arab Emirates", "value": "united-arab-emirates" }, { "label": "Singapore", "value": "singapore" }, { "label": "Other", "value": "other" } ], "propertyMapping": { "united-states": { "technologies": [ "ACH/wire fiat on-ramp" ], "technologyProperties": { "onRampType": "ACH/Fedwire bank transfer", "onRampRegion": "United States", "settlementRail": "ACH / Fedwire" } }, "united-kingdom": { "technologies": [ "UK Faster Payments on-ramp" ], "technologyProperties": { "onRampType": "Faster Payments bank transfer", "onRampRegion": "United Kingdom", "settlementRail": "FPS / BACS" } }, "germany": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "netherlands": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "switzerland": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SIC/SEPA bank transfer", "onRampRegion": "Switzerland/EU", "settlementRail": "SIC / SEPA Credit Transfer" } }, "belgium": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "france": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "sweden": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "norway": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA-adjacent bank transfer", "onRampRegion": "EEA", "settlementRail": "SEPA Credit Transfer" } }, "denmark": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "canada": { "technologies": [ "Canadian EFT on-ramp" ], "technologyProperties": { "onRampType": "Interac/EFT bank transfer", "onRampRegion": "Canada", "settlementRail": "Interac / EFT" } }, "australia": { "technologies": [ "Australian NPP on-ramp" ], "technologyProperties": { "onRampType": "NPP bank transfer", "onRampRegion": "Australia", "settlementRail": "NPP / BECS" } }, "japan": { "technologies": [ "Japanese Zengin on-ramp" ], "technologyProperties": { "onRampType": "Zengin bank transfer", "onRampRegion": "Japan", "settlementRail": "Zengin System" } }, "ireland": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "italy": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "spain": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "austria": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "finland": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "luxembourg": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "south-korea": { "technologies": [ "Korean banking on-ramp" ], "technologyProperties": { "onRampType": "KFTC bank transfer", "onRampRegion": "South Korea", "settlementRail": "KFTC / BOK-Wire" } }, "new-zealand": { "technologies": [ "NZ banking on-ramp" ], "technologyProperties": { "onRampType": "SBI bank transfer", "onRampRegion": "New Zealand", "settlementRail": "SBI / ESAS" } }, "united-arab-emirates": { "technologies": [ "UAE banking on-ramp" ], "technologyProperties": { "onRampType": "UAEFTS bank transfer", "onRampRegion": "United Arab Emirates", "settlementRail": "UAEFTS / IPP" } }, "singapore": { "technologies": [ "Singapore FAST on-ramp" ], "technologyProperties": { "onRampType": "FAST bank transfer", "onRampRegion": "Singapore", "settlementRail": "FAST / MEPS+" } }, "other": { "technologies": [ "Regional fiat on-ramp" ], "technologyProperties": { "onRampType": "Local rail bank transfer", "onRampRegion": "Region-specific", "settlementRail": "Local payment network" } } }, "showIf": { "questionId": "corridor-count", "minValue": "2-3" }, "prefillFrom": null, "briefSection": "Payment rail requirements", "text": "Second most common transfer origination country (if applicable)", "ngoText": "Second most common transfer origination country (if applicable)" }, { "id": "origination-country-3", "type": "select", "options": [ { "label": "United States", "value": "united-states" }, { "label": "United Kingdom", "value": "united-kingdom" }, { "label": "Germany", "value": "germany" }, { "label": "Netherlands", "value": "netherlands" }, { "label": "Switzerland", "value": "switzerland" }, { "label": "Belgium", "value": "belgium" }, { "label": "France", "value": "france" }, { "label": "Sweden", "value": "sweden" }, { "label": "Norway", "value": "norway" }, { "label": "Denmark", "value": "denmark" }, { "label": "Canada", "value": "canada" }, { "label": "Australia", "value": "australia" }, { "label": "Japan", "value": "japan" }, { "label": "Ireland", "value": "ireland" }, { "label": "Italy", "value": "italy" }, { "label": "Spain", "value": "spain" }, { "label": "Austria", "value": "austria" }, { "label": "Finland", "value": "finland" }, { "label": "Luxembourg", "value": "luxembourg" }, { "label": "South Korea", "value": "south-korea" }, { "label": "New Zealand", "value": "new-zealand" }, { "label": "United Arab Emirates", "value": "united-arab-emirates" }, { "label": "Singapore", "value": "singapore" }, { "label": "Other", "value": "other" } ], "propertyMapping": { "united-states": { "technologies": [ "ACH/wire fiat on-ramp" ], "technologyProperties": { "onRampType": "ACH/Fedwire bank transfer", "onRampRegion": "United States", "settlementRail": "ACH / Fedwire" } }, "united-kingdom": { "technologies": [ "UK Faster Payments on-ramp" ], "technologyProperties": { "onRampType": "Faster Payments bank transfer", "onRampRegion": "United Kingdom", "settlementRail": "FPS / BACS" } }, "germany": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "netherlands": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "switzerland": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SIC/SEPA bank transfer", "onRampRegion": "Switzerland/EU", "settlementRail": "SIC / SEPA Credit Transfer" } }, "belgium": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "france": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "sweden": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "norway": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA-adjacent bank transfer", "onRampRegion": "EEA", "settlementRail": "SEPA Credit Transfer" } }, "denmark": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "canada": { "technologies": [ "Canadian EFT on-ramp" ], "technologyProperties": { "onRampType": "Interac/EFT bank transfer", "onRampRegion": "Canada", "settlementRail": "Interac / EFT" } }, "australia": { "technologies": [ "Australian NPP on-ramp" ], "technologyProperties": { "onRampType": "NPP bank transfer", "onRampRegion": "Australia", "settlementRail": "NPP / BECS" } }, "japan": { "technologies": [ "Japanese Zengin on-ramp" ], "technologyProperties": { "onRampType": "Zengin bank transfer", "onRampRegion": "Japan", "settlementRail": "Zengin System" } }, "ireland": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "italy": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "spain": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "austria": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "finland": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "luxembourg": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "south-korea": { "technologies": [ "Korean banking on-ramp" ], "technologyProperties": { "onRampType": "KFTC bank transfer", "onRampRegion": "South Korea", "settlementRail": "KFTC / BOK-Wire" } }, "new-zealand": { "technologies": [ "NZ banking on-ramp" ], "technologyProperties": { "onRampType": "SBI bank transfer", "onRampRegion": "New Zealand", "settlementRail": "SBI / ESAS" } }, "united-arab-emirates": { "technologies": [ "UAE banking on-ramp" ], "technologyProperties": { "onRampType": "UAEFTS bank transfer", "onRampRegion": "United Arab Emirates", "settlementRail": "UAEFTS / IPP" } }, "singapore": { "technologies": [ "Singapore FAST on-ramp" ], "technologyProperties": { "onRampType": "FAST bank transfer", "onRampRegion": "Singapore", "settlementRail": "FAST / MEPS+" } }, "other": { "technologies": [ "Regional fiat on-ramp" ], "technologyProperties": { "onRampType": "Local rail bank transfer", "onRampRegion": "Region-specific", "settlementRail": "Local payment network" } } }, "showIf": { "questionId": "corridor-count", "minValue": "2-3" }, "prefillFrom": null, "briefSection": "Payment rail requirements", "text": "Third transfer origination country (if applicable)", "ngoText": "Third transfer origination country (if applicable)" }, { "id": "origination-country-4", "type": "select", "options": [ { "label": "United States", "value": "united-states" }, { "label": "United Kingdom", "value": "united-kingdom" }, { "label": "Germany", "value": "germany" }, { "label": "Netherlands", "value": "netherlands" }, { "label": "Switzerland", "value": "switzerland" }, { "label": "Belgium", "value": "belgium" }, { "label": "France", "value": "france" }, { "label": "Sweden", "value": "sweden" }, { "label": "Norway", "value": "norway" }, { "label": "Denmark", "value": "denmark" }, { "label": "Canada", "value": "canada" }, { "label": "Australia", "value": "australia" }, { "label": "Japan", "value": "japan" }, { "label": "Ireland", "value": "ireland" }, { "label": "Italy", "value": "italy" }, { "label": "Spain", "value": "spain" }, { "label": "Austria", "value": "austria" }, { "label": "Finland", "value": "finland" }, { "label": "Luxembourg", "value": "luxembourg" }, { "label": "South Korea", "value": "south-korea" }, { "label": "New Zealand", "value": "new-zealand" }, { "label": "United Arab Emirates", "value": "united-arab-emirates" }, { "label": "Singapore", "value": "singapore" }, { "label": "Other", "value": "other" } ], "propertyMapping": { "united-states": { "technologies": [ "ACH/wire fiat on-ramp" ], "technologyProperties": { "onRampType": "ACH/Fedwire bank transfer", "onRampRegion": "United States", "settlementRail": "ACH / Fedwire" } }, "united-kingdom": { "technologies": [ "UK Faster Payments on-ramp" ], "technologyProperties": { "onRampType": "Faster Payments bank transfer", "onRampRegion": "United Kingdom", "settlementRail": "FPS / BACS" } }, "germany": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "netherlands": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "switzerland": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SIC/SEPA bank transfer", "onRampRegion": "Switzerland/EU", "settlementRail": "SIC / SEPA Credit Transfer" } }, "belgium": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "france": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "sweden": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "norway": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA-adjacent bank transfer", "onRampRegion": "EEA", "settlementRail": "SEPA Credit Transfer" } }, "denmark": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "canada": { "technologies": [ "Canadian EFT on-ramp" ], "technologyProperties": { "onRampType": "Interac/EFT bank transfer", "onRampRegion": "Canada", "settlementRail": "Interac / EFT" } }, "australia": { "technologies": [ "Australian NPP on-ramp" ], "technologyProperties": { "onRampType": "NPP bank transfer", "onRampRegion": "Australia", "settlementRail": "NPP / BECS" } }, "japan": { "technologies": [ "Japanese Zengin on-ramp" ], "technologyProperties": { "onRampType": "Zengin bank transfer", "onRampRegion": "Japan", "settlementRail": "Zengin System" } }, "ireland": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "italy": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "spain": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "austria": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "finland": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "luxembourg": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "south-korea": { "technologies": [ "Korean banking on-ramp" ], "technologyProperties": { "onRampType": "KFTC bank transfer", "onRampRegion": "South Korea", "settlementRail": "KFTC / BOK-Wire" } }, "new-zealand": { "technologies": [ "NZ banking on-ramp" ], "technologyProperties": { "onRampType": "SBI bank transfer", "onRampRegion": "New Zealand", "settlementRail": "SBI / ESAS" } }, "united-arab-emirates": { "technologies": [ "UAE banking on-ramp" ], "technologyProperties": { "onRampType": "UAEFTS bank transfer", "onRampRegion": "United Arab Emirates", "settlementRail": "UAEFTS / IPP" } }, "singapore": { "technologies": [ "Singapore FAST on-ramp" ], "technologyProperties": { "onRampType": "FAST bank transfer", "onRampRegion": "Singapore", "settlementRail": "FAST / MEPS+" } }, "other": { "technologies": [ "Regional fiat on-ramp" ], "technologyProperties": { "onRampType": "Local rail bank transfer", "onRampRegion": "Region-specific", "settlementRail": "Local payment network" } } }, "showIf": { "questionId": "corridor-count", "minValue": "4-5" }, "prefillFrom": null, "briefSection": "Payment rail requirements", "text": "Fourth transfer origination country (if applicable)", "ngoText": "Fourth transfer origination country (if applicable)" }, { "id": "origination-country-5", "type": "select", "options": [ { "label": "United States", "value": "united-states" }, { "label": "United Kingdom", "value": "united-kingdom" }, { "label": "Germany", "value": "germany" }, { "label": "Netherlands", "value": "netherlands" }, { "label": "Switzerland", "value": "switzerland" }, { "label": "Belgium", "value": "belgium" }, { "label": "France", "value": "france" }, { "label": "Sweden", "value": "sweden" }, { "label": "Norway", "value": "norway" }, { "label": "Denmark", "value": "denmark" }, { "label": "Canada", "value": "canada" }, { "label": "Australia", "value": "australia" }, { "label": "Japan", "value": "japan" }, { "label": "Ireland", "value": "ireland" }, { "label": "Italy", "value": "italy" }, { "label": "Spain", "value": "spain" }, { "label": "Austria", "value": "austria" }, { "label": "Finland", "value": "finland" }, { "label": "Luxembourg", "value": "luxembourg" }, { "label": "South Korea", "value": "south-korea" }, { "label": "New Zealand", "value": "new-zealand" }, { "label": "United Arab Emirates", "value": "united-arab-emirates" }, { "label": "Singapore", "value": "singapore" }, { "label": "Other", "value": "other" } ], "propertyMapping": { "united-states": { "technologies": [ "ACH/wire fiat on-ramp" ], "technologyProperties": { "onRampType": "ACH/Fedwire bank transfer", "onRampRegion": "United States", "settlementRail": "ACH / Fedwire" } }, "united-kingdom": { "technologies": [ "UK Faster Payments on-ramp" ], "technologyProperties": { "onRampType": "Faster Payments bank transfer", "onRampRegion": "United Kingdom", "settlementRail": "FPS / BACS" } }, "germany": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "netherlands": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "switzerland": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SIC/SEPA bank transfer", "onRampRegion": "Switzerland/EU", "settlementRail": "SIC / SEPA Credit Transfer" } }, "belgium": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "france": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "sweden": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "norway": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA-adjacent bank transfer", "onRampRegion": "EEA", "settlementRail": "SEPA Credit Transfer" } }, "denmark": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "canada": { "technologies": [ "Canadian EFT on-ramp" ], "technologyProperties": { "onRampType": "Interac/EFT bank transfer", "onRampRegion": "Canada", "settlementRail": "Interac / EFT" } }, "australia": { "technologies": [ "Australian NPP on-ramp" ], "technologyProperties": { "onRampType": "NPP bank transfer", "onRampRegion": "Australia", "settlementRail": "NPP / BECS" } }, "japan": { "technologies": [ "Japanese Zengin on-ramp" ], "technologyProperties": { "onRampType": "Zengin bank transfer", "onRampRegion": "Japan", "settlementRail": "Zengin System" } }, "ireland": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "italy": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "spain": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "austria": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "finland": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "luxembourg": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "south-korea": { "technologies": [ "Korean banking on-ramp" ], "technologyProperties": { "onRampType": "KFTC bank transfer", "onRampRegion": "South Korea", "settlementRail": "KFTC / BOK-Wire" } }, "new-zealand": { "technologies": [ "NZ banking on-ramp" ], "technologyProperties": { "onRampType": "SBI bank transfer", "onRampRegion": "New Zealand", "settlementRail": "SBI / ESAS" } }, "united-arab-emirates": { "technologies": [ "UAE banking on-ramp" ], "technologyProperties": { "onRampType": "UAEFTS bank transfer", "onRampRegion": "United Arab Emirates", "settlementRail": "UAEFTS / IPP" } }, "singapore": { "technologies": [ "Singapore FAST on-ramp" ], "technologyProperties": { "onRampType": "FAST bank transfer", "onRampRegion": "Singapore", "settlementRail": "FAST / MEPS+" } }, "other": { "technologies": [ "Regional fiat on-ramp" ], "technologyProperties": { "onRampType": "Local rail bank transfer", "onRampRegion": "Region-specific", "settlementRail": "Local payment network" } } }, "showIf": { "questionId": "corridor-count", "minValue": "4-5" }, "prefillFrom": null, "briefSection": "Payment rail requirements", "text": "Fifth transfer origination country (if applicable)", "ngoText": "Fifth transfer origination country (if applicable)" }, { "id": "funding-method", "type": "select", "options": [ { "label": "Bank transfer from organisation account", "value": "bank-transfer" }, { "label": "Card payment from organisation", "value": "card-payment" }, { "label": "Direct stablecoin funding (organisation already holds stablecoins)", "value": "direct-stablecoin" }, { "label": "Mixed: bank transfer for most, card for urgent payments", "value": "mixed-methods" } ], "propertyMapping": { "bank-transfer": { "technologies": [ "Bank-integrated fiat on-ramp" ], "technologyProperties": { "fundingSource": "Organisation bank account", "onRampSpeed": "1-2 business days (SEPA/ACH) or same-day (Faster Payments/wire)", "kybRequired": "Yes \u2014 organisation KYB verification" } }, "card-payment": { "technologies": [ "Card payment on-ramp" ], "technologyProperties": { "fundingSource": "Organisation payment card", "onRampSpeed": "Near-instant", "kybRequired": "Yes \u2014 card verification and organisation KYB" } }, "direct-stablecoin": { "technologies": [ "Direct stablecoin treasury funding" ], "technologyProperties": { "fundingSource": "Existing stablecoin holdings", "onRampSpeed": "Immediate (no fiat conversion needed)", "kybRequired": "Wallet verification only" } }, "mixed-methods": { "technologies": [ "Multi-method fiat on-ramp", "Card payment on-ramp" ], "technologyProperties": { "fundingSource": "Bank transfer (primary) + card (urgent)", "onRampSpeed": "Varies by method", "kybRequired": "Yes \u2014 full organisation KYB" } } }, "prefillFrom": null, "briefSection": "Payment rail requirements", "text": "How does your organisation currently fund international transfers or payments?", "ngoText": "How does your organisation currently fund international transfers or payments?" }, { "id": "vendor-count", "type": "select", "options": [ { "label": "Under 50 vendors", "value": "small" }, { "label": "50\u2013200 vendors", "value": "medium" }, { "label": "200\u20131,000 vendors", "value": "large" }, { "label": "Over 1,000 vendors", "value": "enterprise" } ], "propertyMapping": { "small": { "technologies": [ "Layer 1 payment rail" ], "technologyProperties": { "vendorManagement": "Basic vendor registry", "scalability": "Small-scale" } }, "medium": { "technologies": [ "Layer 1 payment rail", "Vendor management module" ], "technologyProperties": { "vendorManagement": "Structured vendor database", "scalability": "Medium-scale" } }, "large": { "technologies": [ "Layer 1 payment rail", "Vendor management platform", "Batch payment engine" ], "technologyProperties": { "vendorManagement": "Full vendor lifecycle management", "scalability": "Large-scale with batching" } }, "enterprise": { "technologies": [ "Layer 1 payment rail", "Enterprise vendor management", "Batch payment engine", "Vendor onboarding automation" ], "technologyProperties": { "vendorManagement": "Enterprise vendor platform", "scalability": "Enterprise-grade" } } }, "prefillFrom": null, "briefSection": "Payment operations", "text": "How many active vendors/suppliers do you regularly pay?", "ngoText": "How many active vendors/suppliers do you regularly pay?" }, { "id": "vendor-location-type", "type": "multiselect", "options": [ { "label": "Urban centres with banking infrastructure", "value": "urban-banked" }, { "label": "Peri-urban areas with mobile money access", "value": "peri-urban" }, { "label": "Remote rural areas with limited connectivity", "value": "remote-rural" }, { "label": "Conflict/crisis zones with minimal infrastructure", "value": "conflict-zone" }, { "label": "International suppliers (cross-border)", "value": "international" } ], "propertyMapping": { "urban-banked": { "technologies": [ "Bank-integrated off-ramp" ], "technologyProperties": { "lastMileChannel": "Bank transfer", "offlineCapability": "Not required" } }, "peri-urban": { "technologies": [ "Mobile money off-ramp" ], "technologyProperties": { "lastMileChannel": "Mobile money", "offlineCapability": "Recommended" } }, "remote-rural": { "technologies": [ "Agent network", "Offline-capable wallet", "USSD interface" ], "technologyProperties": { "lastMileChannel": "Agent cash-out or mobile money", "offlineCapability": "Required" } }, "conflict-zone": { "technologies": [ "Offline-first wallet", "Agent network", "Satellite connectivity option" ], "technologyProperties": { "lastMileChannel": "Agent-based with offline support", "offlineCapability": "Critical \u2014 must work fully offline" } }, "international": { "technologies": [ "Cross-border payment rail", "Multi-currency stablecoin" ], "technologyProperties": { "lastMileChannel": "International bank transfer or local off-ramp", "offlineCapability": "Not required" } } }, "prefillFrom": null, "briefSection": "Last-mile delivery", "text": "Where are most of your vendors located?", "ngoText": "Where are most of your vendors located?" }, { "id": "vendor-payment-current", "type": "multiselect", "options": [ { "label": "Bank transfer", "value": "bank" }, { "label": "Mobile money", "value": "mobile-money" }, { "label": "Physical cash", "value": "cash" }, { "label": "Cheque", "value": "cheque" }, { "label": "Hawala or informal transfer", "value": "informal" }, { "label": "Pre-paid cards", "value": "prepaid-cards" } ], "propertyMapping": { "bank": { "technologies": [ "Bank-integrated off-ramp" ], "technologyProperties": { "currentMethod": "Bank transfer", "migrationComplexity": "Low \u2014 similar flow" } }, "mobile-money": { "technologies": [ "Mobile money off-ramp" ], "technologyProperties": { "currentMethod": "Mobile money", "migrationComplexity": "Low \u2014 similar flow" } }, "cash": { "technologies": [ "Digital payment conversion", "Agent network", "Vendor wallet" ], "technologyProperties": { "currentMethod": "Cash", "migrationComplexity": "High \u2014 vendor onboarding needed" } }, "cheque": { "technologies": [ "Digital payment conversion" ], "technologyProperties": { "currentMethod": "Cheque", "migrationComplexity": "Medium \u2014 process change" } }, "informal": { "technologies": [ "Formal payment rail replacement", "Compliance screening" ], "technologyProperties": { "currentMethod": "Informal", "migrationComplexity": "High \u2014 formalisation required" } }, "prepaid-cards": { "technologies": [ "Digital wallet replacement" ], "technologyProperties": { "currentMethod": "Pre-paid cards", "migrationComplexity": "Medium \u2014 card to wallet transition" } } }, "prefillFrom": null, "briefSection": "Current state", "text": "How are vendors currently paid?", "ngoText": "How are vendors currently paid?" }, { "id": "vendor-payment-conditions", "type": "select", "options": [ { "label": "Yes, payment on confirmed delivery/inspection", "value": "delivery-verified" }, { "label": "Yes, milestone-based payments against contract", "value": "milestone" }, { "label": "Partial, advance + balance on delivery", "value": "partial" }, { "label": "No, payment on invoice submission", "value": "invoice-only" } ], "propertyMapping": { "delivery-verified": { "technologies": [ "Smart contract escrow", "Delivery verification oracle" ], "technologyProperties": { "paymentCondition": "Delivery-triggered release", "escrowRequired": true, "verificationMethod": "Field confirmation or IoT" } }, "milestone": { "technologies": [ "Smart contract milestone automation" ], "technologyProperties": { "paymentCondition": "Milestone-based release", "escrowRequired": true, "verificationMethod": "Milestone sign-off" } }, "partial": { "technologies": [ "Smart contract partial release" ], "technologyProperties": { "paymentCondition": "Advance + conditional balance", "escrowRequired": true, "verificationMethod": "Delivery confirmation for balance" } }, "invoice-only": { "technologies": [], "technologyProperties": { "paymentCondition": "Invoice-based", "escrowRequired": false } } }, "prefillFrom": null, "briefSection": "Payment logic", "text": "Are vendor payments tied to delivery verification or contract milestones?", "ngoText": "Are vendor payments tied to delivery verification or contract milestones?" }, { "id": "vendor-avg-payment", "type": "select", "options": [ { "label": "Under $100", "value": "micro" }, { "label": "$100\u2013$1,000", "value": "small" }, { "label": "$1,000\u2013$10,000", "value": "medium" }, { "label": "$10,000\u2013$100,000", "value": "large" }, { "label": "Over $100,000", "value": "very-large" }, { "label": "Highly variable", "value": "variable" } ], "propertyMapping": { "micro": { "technologies": [ "Layer 1 payment rail" ], "technologyProperties": { "maxTransactionFee": "Sub-$0.01", "feeModel": "Fixed micro-fee" } }, "small": { "technologies": [ "Layer 1 payment rail" ], "technologyProperties": { "maxTransactionFee": "Sub-$0.10", "feeModel": "Fixed low fee" } }, "medium": { "technologies": [ "Layer 1 payment rail" ], "technologyProperties": { "maxTransactionFee": "Sub-$1.00", "feeModel": "Fixed or low percentage" } }, "large": { "technologies": [ "Layer 1 payment rail" ], "technologyProperties": { "maxTransactionFee": "Competitive", "feeModel": "Percentage-based acceptable" } }, "very-large": { "technologies": [ "Layer 1 payment rail" ], "technologyProperties": { "maxTransactionFee": "Competitive with traditional wire", "feeModel": "Negotiable" } }, "variable": { "technologies": [ "Layer 1 payment rail" ], "technologyProperties": { "maxTransactionFee": "Fixed fee preferred", "feeModel": "Predictable fixed model" } } }, "prefillFrom": null, "briefSection": "Payment rail requirements", "text": "What is the typical vendor payment amount?", "ngoText": "What is the typical vendor payment amount?" }, { "id": "vendor-screening", "type": "multiselect", "options": [ { "label": "Sanctions/OFAC screening", "value": "sanctions" }, { "label": "Vendor identity verification", "value": "vendor-kyc" }, { "label": "Beneficial ownership checks", "value": "beneficial-ownership" }, { "label": "Conflict of interest checks", "value": "conflict-interest" }, { "label": "Donor-specific vetting requirements", "value": "donor-vetting" }, { "label": "Minimal: basic vendor registration only", "value": "minimal" } ], "propertyMapping": { "sanctions": { "technologies": [ "OFAC/sanctions screening module" ], "technologyProperties": { "vendorScreening": "Sanctions list check", "screeningFrequency": "Per-payment + periodic" } }, "vendor-kyc": { "technologies": [ "Vendor KYC module" ], "technologyProperties": { "vendorScreening": "Identity verification", "screeningFrequency": "At onboarding + annual" } }, "beneficial-ownership": { "technologies": [ "Beneficial ownership verification" ], "technologyProperties": { "vendorScreening": "Ownership structure check", "screeningFrequency": "At onboarding + material change" } }, "conflict-interest": { "technologies": [ "Conflict of interest screening" ], "technologyProperties": { "vendorScreening": "CoI declaration and check", "screeningFrequency": "At onboarding + per-contract" } }, "donor-vetting": { "technologies": [ "Configurable vetting rules engine" ], "technologyProperties": { "vendorScreening": "Donor-specific rules", "screeningFrequency": "Per donor requirement" } }, "minimal": { "technologies": [], "technologyProperties": { "vendorScreening": "Basic registration", "screeningFrequency": "At onboarding" } } }, "prefillFrom": null, "briefSection": "Identity and compliance", "text": "What due diligence or screening is required before paying a vendor?", "ngoText": "What due diligence or screening is required before paying a vendor?" }, { "id": "vendor-onboarding", "type": "select", "options": [ { "label": "Most are comfortable with smartphones and apps", "value": "tech-comfortable" }, { "label": "Can use basic mobile money but not apps", "value": "basic-mobile" }, { "label": "Limited tech skills: need very simple interface", "value": "limited-tech" }, { "label": "Varies widely, from tech-savvy to no tech at all", "value": "varies" } ], "propertyMapping": { "tech-comfortable": { "technologies": [ "Mobile wallet application" ], "technologyProperties": { "vendorInterface": "Mobile app", "onboardingSupport": "Self-service" } }, "basic-mobile": { "technologies": [ "USSD/SMS-based wallet", "Mobile money integration" ], "technologyProperties": { "vendorInterface": "USSD or mobile money", "onboardingSupport": "Guided setup" } }, "limited-tech": { "technologies": [ "Agent-assisted payment collection" ], "technologyProperties": { "vendorInterface": "Agent-facilitated or USSD", "onboardingSupport": "In-person training required" } }, "varies": { "technologies": [ "Multi-channel vendor platform" ], "technologyProperties": { "vendorInterface": "App + USSD + agent fallback", "onboardingSupport": "Tiered support model" } } }, "prefillFrom": null, "briefSection": "End-user interface", "text": "How tech-savvy are your vendors? Could they use a digital wallet?", "ngoText": "How tech-savvy are your vendors? Could they use a digital wallet?" }, { "id": "procurement-audit", "type": "select", "options": [ { "label": "Critical: donors audit individual transactions", "value": "critical" }, { "label": "Important: need to demonstrate value for money", "value": "important" }, { "label": "Standard: normal financial record-keeping", "value": "standard" }, { "label": "Not a priority currently", "value": "low" } ], "propertyMapping": { "critical": { "technologies": [ "Immutable procurement audit trail", "Transaction explorer", "Donor reporting dashboard" ], "technologyProperties": { "auditCapability": "Full end-to-end trace", "immutability": "Blockchain-anchored records" } }, "important": { "technologies": [ "Procurement audit trail", "Reporting module" ], "technologyProperties": { "auditCapability": "Detailed transaction records", "immutability": "Tamper-evident logs" } }, "standard": { "technologies": [ "Standard audit log" ], "technologyProperties": { "auditCapability": "Standard transaction records", "immutability": "Standard logging" } }, "low": { "technologies": [], "technologyProperties": { "auditCapability": "Basic records", "immutability": "Not prioritised" } } }, "prefillFrom": null, "briefSection": "Reporting and audit", "text": "How important is a transparent audit trail for procurement payments?", "ngoText": "How important is a transparent audit trail for procurement payments?" }, { "id": "sq-UC-A-003-001", "type": "single-select", "options": [ { "value": "gps-timestamp", "label": "GPS timestamp and location verification" }, { "value": "photo-verification", "label": "Photo evidence at delivery location" }, { "value": "beneficiary-confirmation", "label": "Beneficiary confirmation signature" }, { "value": "third-party-inspection", "label": "Third-party inspection verification" }, { "value": "self-reported", "label": "Self-reported by vendor" } ], "propertyMapping": { "gps-timestamp": { "technologies": [ "gps-verification", "location-tagging" ], "technologyProperties": {} }, "photo-verification": { "technologies": [ "image-capture", "timestamp-verification" ], "technologyProperties": {} }, "beneficiary-confirmation": { "technologies": [ "digital-signature", "beneficiary-device" ], "technologyProperties": {} }, "third-party-inspection": { "technologies": [ "inspection-workflow", "multi-party-verification" ], "technologyProperties": {} }, "self-reported": { "technologies": [ "simple-attestation" ], "technologyProperties": {} } }, "briefSection": "operations", "text": "What proof-of-delivery systems do you currently use before vendor payment release?", "ngoText": "What proof-of-delivery systems do you currently use before vendor payment release?" }, { "id": "beneficiary-choice", "label": "How will beneficiaries exercise choice in how they receive and use this service?", "type": "select", "briefSection": "End-user interface", "options": [ { "label": "Beneficiaries choose between delivery methods (cash, voucher, mobile money, direct)", "value": "delivery-choice" }, { "label": "Beneficiaries choose preferred merchants or service points", "value": "merchant-choice" }, { "label": "Beneficiaries control their own data sharing preferences", "value": "data-choice" }, { "label": "Multiple choice dimensions (delivery + merchant + data)", "value": "full-choice" }, { "label": "Limited choice: programme constraints determine delivery", "value": "limited" } ], "propertyMapping": { "delivery-choice": { "technologies": [], "technologyProperties": { "beneficiaryChoice": "Delivery method choice", "dignityDesign": "Beneficiaries select preferred receipt method" } }, "merchant-choice": { "technologies": [], "technologyProperties": { "beneficiaryChoice": "Merchant/service point choice", "dignityDesign": "Beneficiaries select where to redeem" } }, "data-choice": { "technologies": [], "technologyProperties": { "beneficiaryChoice": "Data sharing choice", "dignityDesign": "Beneficiaries control personal data sharing" } }, "full-choice": { "technologies": [], "technologyProperties": { "beneficiaryChoice": "Multi-dimensional choice", "dignityDesign": "Full beneficiary agency across delivery, merchant, and data" } }, "limited": { "technologies": [], "technologyProperties": { "beneficiaryChoice": "Limited by programme design", "dignityDesign": "Programme constraints; beneficiary informed of reasons" } } }, "text": "How will beneficiaries exercise choice in how they receive and use this service?" } ], "complexityFactors": { "relationships": 2, "operationalChange": 2, "dataCompliance": 2 }, "suggestedCriteria": [ { "id": "SC-REMOTE-REACH", "name": "Remote Location Payment Reach", "description": "The provider can make payments to vendors in locations with limited banking infrastructure. Remote field offices and local suppliers often lack traditional bank access.", "weight": 0.3, "ratingGuide": { "5": "Payments reach vendors in areas with no bank branches via mobile money, agent networks, or offline-capable wallets. Proven in remote/conflict-affected settings.", "4": "Good reach via mobile money in most remote areas. Some agent network coverage.", "3": "Reaches vendors in semi-urban areas. Limited options for truly remote locations.", "2": "Requires vendors to have bank accounts. No alternative delivery methods.", "1": "Urban-only coverage. No capability for remote or underbanked vendors." } }, { "id": "SC-VENDOR-ONBOARD", "name": "Vendor Onboarding Simplicity", "description": "This measures how easy it is to register new vendors. NGOs work with hundreds of local suppliers, many unfamiliar with digital payments. The onboarding process must be simple and fast.", "weight": 0.25, "ratingGuide": { "5": "SMS or app-based registration. Under 5 minutes. Minimal documentation. Works on feature phones. Available in local languages.", "4": "Simple app or web registration. Under 15 minutes. Basic documentation. Smartphone required.", "3": "Online registration requiring moderate documentation. 1-2 days to activate. Smartphone required.", "2": "Complex registration requiring multiple documents. 3-5 days. Desktop/laptop needed.", "1": "Bank-like KYC process. Weeks to activate. Requires in-person verification." } }, { "id": "SC-MULTI-CURRENCY", "name": "Multi-Currency Support", "description": "Payments can be made in vendors' local currencies. Remote suppliers need payment in the currency they transact in, not in USD or EUR.", "weight": 0.2, "ratingGuide": { "5": "Supports 20+ currencies including minor African and Asian currencies. Automatic conversion. Competitive rates.", "4": "Supports 10-20 currencies including major operating region currencies. Good conversion rates.", "3": "Supports major currencies (USD, EUR, GBP) plus a few local ones. Moderate rates.", "2": "Limited to major currencies. Vendors must accept USD/EUR or convert themselves.", "1": "Single currency only. No local currency support." } }, { "id": "SC-RECONCILIATION", "name": "Payment Reconciliation & Audit Trail", "description": "The provider generates clear payment records linked to purchase orders and invoices. NGO procurement requires audit trails connecting payments to specific goods and services.", "weight": 0.15, "ratingGuide": { "5": "Automatic reconciliation with PO/invoice matching. Exportable audit trail. Donor-ready reporting. Integration with accounting systems.", "4": "Good reconciliation tools. Exportable records. Manual matching supported with clear audit trail.", "3": "Basic payment records. CSV export. Manual reconciliation needed for PO matching.", "2": "Transaction history only. No reconciliation tools. Manual export process.", "1": "Minimal records. No export capability. No audit trail." } }, { "id": "SC-BATCH-PAY", "name": "Batch Payment Capability", "description": "The provider can process multiple vendor payments simultaneously. Paying dozens of suppliers one at a time is impractical for busy field offices.", "weight": 0.1, "ratingGuide": { "5": "Batch upload of 100+ payments via CSV/API. Scheduled batch runs. Automatic retry for failures. Per-payment status tracking.", "4": "Batch upload of 50+ payments. Good scheduling. Status tracking per batch.", "3": "Batch upload available but limited to 20-30 payments. Basic scheduling.", "2": "Small batch capability (under 10). Mostly manual individual payments.", "1": "Individual payments only. No batch processing." } } ], "procurement": { "marketMaturity": "emerging", "primaryMode": "tender", "alternativeModes": [ "integrator-led" ], "reasoning": "Some vendor payment platforms exist but remote-location specifics often require integration.", "exampleProductCategories": [ "vendor-payment-platform", "b2b-payments-rails" ], "partnerChannels": [], "lastReviewed": "2026-05-01" } }, { "id": "UC-A-004", "name": "Inter-office fund transfers across country programmes", "category": "A", "subcategory": "Internal Fund Movement", "description": "Move money between your country offices faster, and give both offices one agreed record that each transfer is complete.", "bCriteria": [ "B1", "B5" ], "requiredComponents": [ { "component": "payment-rails", "description": "Blockchain network for inter-office settlement" }, { "component": "stablecoin", "description": "Stablecoin for fund movement" }, { "component": "multi-sig-treasury", "description": "Multi-signature approval for transfers" }, { "component": "accounting-integration", "description": "Accounting system integration" } ], "conditionalComponents": [ { "component": "smart-contracts", "condition": "If transfers follow predefined rules (fund allocation policies)" } ], "crossCategoryDependencies": [], "p2TriggerConditions": { "description": "Activated when P2 shows multiple country offices + frequent inter-office transfers + approval delays", "rangeSignals": [ "officeCount >= 3", "transferFrequency >= monthly", "approvalTime >= 2-3 days" ] }, "contextFieldsTemplate": [ { "field": "officeCount", "source": "P0 organisational structure", "description": "Number of country offices" }, { "field": "transferFrequency", "source": "P2 fund management practices", "description": "How often funds are moved" }, { "field": "approvalLayers", "source": "P0 governance structure", "description": "Number of approval levels" }, { "field": "accountingSystem", "source": "P0 Q13", "description": "Current accounting system" } ], "implementationComplexity": "medium", "examples": { "note": "Large NGO treasury operations", "references": [ { "name": "Stellar / IBM World Wire", "url": "https://www.ibm.com/think/topics/cross-border-payments-blockchain", "solved": "Handled cross-border settlement and FX in multiple currencies in near real time" }, { "name": "Disberse", "url": "https://www.nesta.org.uk/feature/new-radicals-2018/disberse/", "solved": "Traced international aid fund transfers reducing intermediary costs" } ] }, "solutionQuestions": [ { "id": "corridor-count", "type": "select", "options": [ { "label": "Single country", "value": "single" }, { "label": "2\u20133 countries", "value": "2-3" }, { "label": "4\u20135 countries", "value": "4-5" }, { "label": "More than 5 countries", "value": "5-plus" } ], "propertyMapping": { "single": { "technologies": [ "Single-corridor fiat on-ramp" ], "technologyProperties": { "corridorComplexity": "Single origination country", "multiRailNeeded": "No" } }, "2-3": { "technologies": [ "Multi-corridor fiat on-ramp gateway" ], "technologyProperties": { "corridorComplexity": "2\u20133 origination countries", "multiRailNeeded": "Yes \u2014 2-3 payment rails" } }, "4-5": { "technologies": [ "Multi-corridor fiat on-ramp gateway" ], "technologyProperties": { "corridorComplexity": "4\u20135 origination countries", "multiRailNeeded": "Yes \u2014 4-5 payment rails" } }, "5-plus": { "technologies": [ "Enterprise multi-corridor on-ramp gateway" ], "technologyProperties": { "corridorComplexity": "5+ origination countries", "multiRailNeeded": "Yes \u2014 enterprise-grade multi-rail" } } }, "prefillFrom": null, "briefSection": "Payment rail requirements", "text": "How many countries does your organisation send transfer funds from?", "ngoText": "How many countries does your organisation send transfer funds from?" }, { "id": "origination-country-1", "type": "select", "options": [ { "label": "United States", "value": "united-states" }, { "label": "United Kingdom", "value": "united-kingdom" }, { "label": "Germany", "value": "germany" }, { "label": "Netherlands", "value": "netherlands" }, { "label": "Switzerland", "value": "switzerland" }, { "label": "Belgium", "value": "belgium" }, { "label": "France", "value": "france" }, { "label": "Sweden", "value": "sweden" }, { "label": "Norway", "value": "norway" }, { "label": "Denmark", "value": "denmark" }, { "label": "Canada", "value": "canada" }, { "label": "Australia", "value": "australia" }, { "label": "Japan", "value": "japan" }, { "label": "Ireland", "value": "ireland" }, { "label": "Italy", "value": "italy" }, { "label": "Spain", "value": "spain" }, { "label": "Austria", "value": "austria" }, { "label": "Finland", "value": "finland" }, { "label": "Luxembourg", "value": "luxembourg" }, { "label": "South Korea", "value": "south-korea" }, { "label": "New Zealand", "value": "new-zealand" }, { "label": "United Arab Emirates", "value": "united-arab-emirates" }, { "label": "Singapore", "value": "singapore" }, { "label": "Other", "value": "other" } ], "propertyMapping": { "united-states": { "technologies": [ "ACH/wire fiat on-ramp" ], "technologyProperties": { "onRampType": "ACH/Fedwire bank transfer", "onRampRegion": "United States", "settlementRail": "ACH / Fedwire" } }, "united-kingdom": { "technologies": [ "UK Faster Payments on-ramp" ], "technologyProperties": { "onRampType": "Faster Payments bank transfer", "onRampRegion": "United Kingdom", "settlementRail": "FPS / BACS" } }, "germany": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "netherlands": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "switzerland": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SIC/SEPA bank transfer", "onRampRegion": "Switzerland/EU", "settlementRail": "SIC / SEPA Credit Transfer" } }, "belgium": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "france": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "sweden": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "norway": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA-adjacent bank transfer", "onRampRegion": "EEA", "settlementRail": "SEPA Credit Transfer" } }, "denmark": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "canada": { "technologies": [ "Canadian EFT on-ramp" ], "technologyProperties": { "onRampType": "Interac/EFT bank transfer", "onRampRegion": "Canada", "settlementRail": "Interac / EFT" } }, "australia": { "technologies": [ "Australian NPP on-ramp" ], "technologyProperties": { "onRampType": "NPP bank transfer", "onRampRegion": "Australia", "settlementRail": "NPP / BECS" } }, "japan": { "technologies": [ "Japanese Zengin on-ramp" ], "technologyProperties": { "onRampType": "Zengin bank transfer", "onRampRegion": "Japan", "settlementRail": "Zengin System" } }, "ireland": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "italy": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "spain": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "austria": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "finland": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "luxembourg": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "south-korea": { "technologies": [ "Korean banking on-ramp" ], "technologyProperties": { "onRampType": "KFTC bank transfer", "onRampRegion": "South Korea", "settlementRail": "KFTC / BOK-Wire" } }, "new-zealand": { "technologies": [ "NZ banking on-ramp" ], "technologyProperties": { "onRampType": "SBI bank transfer", "onRampRegion": "New Zealand", "settlementRail": "SBI / ESAS" } }, "united-arab-emirates": { "technologies": [ "UAE banking on-ramp" ], "technologyProperties": { "onRampType": "UAEFTS bank transfer", "onRampRegion": "United Arab Emirates", "settlementRail": "UAEFTS / IPP" } }, "singapore": { "technologies": [ "Singapore FAST on-ramp" ], "technologyProperties": { "onRampType": "FAST bank transfer", "onRampRegion": "Singapore", "settlementRail": "FAST / MEPS+" } }, "other": { "technologies": [ "Regional fiat on-ramp" ], "technologyProperties": { "onRampType": "Local rail bank transfer", "onRampRegion": "Region-specific", "settlementRail": "Local payment network" } } }, "showIf": { "questionId": "corridor-count", "minValue": "single" }, "prefillFrom": null, "briefSection": "Payment rail requirements", "text": "Which country do you most frequently initiate transfers from?", "ngoText": "Which country do you most frequently initiate transfers from?" }, { "id": "origination-country-2", "type": "select", "options": [ { "label": "United States", "value": "united-states" }, { "label": "United Kingdom", "value": "united-kingdom" }, { "label": "Germany", "value": "germany" }, { "label": "Netherlands", "value": "netherlands" }, { "label": "Switzerland", "value": "switzerland" }, { "label": "Belgium", "value": "belgium" }, { "label": "France", "value": "france" }, { "label": "Sweden", "value": "sweden" }, { "label": "Norway", "value": "norway" }, { "label": "Denmark", "value": "denmark" }, { "label": "Canada", "value": "canada" }, { "label": "Australia", "value": "australia" }, { "label": "Japan", "value": "japan" }, { "label": "Ireland", "value": "ireland" }, { "label": "Italy", "value": "italy" }, { "label": "Spain", "value": "spain" }, { "label": "Austria", "value": "austria" }, { "label": "Finland", "value": "finland" }, { "label": "Luxembourg", "value": "luxembourg" }, { "label": "South Korea", "value": "south-korea" }, { "label": "New Zealand", "value": "new-zealand" }, { "label": "United Arab Emirates", "value": "united-arab-emirates" }, { "label": "Singapore", "value": "singapore" }, { "label": "Other", "value": "other" } ], "propertyMapping": { "united-states": { "technologies": [ "ACH/wire fiat on-ramp" ], "technologyProperties": { "onRampType": "ACH/Fedwire bank transfer", "onRampRegion": "United States", "settlementRail": "ACH / Fedwire" } }, "united-kingdom": { "technologies": [ "UK Faster Payments on-ramp" ], "technologyProperties": { "onRampType": "Faster Payments bank transfer", "onRampRegion": "United Kingdom", "settlementRail": "FPS / BACS" } }, "germany": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "netherlands": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "switzerland": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SIC/SEPA bank transfer", "onRampRegion": "Switzerland/EU", "settlementRail": "SIC / SEPA Credit Transfer" } }, "belgium": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "france": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "sweden": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "norway": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA-adjacent bank transfer", "onRampRegion": "EEA", "settlementRail": "SEPA Credit Transfer" } }, "denmark": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "canada": { "technologies": [ "Canadian EFT on-ramp" ], "technologyProperties": { "onRampType": "Interac/EFT bank transfer", "onRampRegion": "Canada", "settlementRail": "Interac / EFT" } }, "australia": { "technologies": [ "Australian NPP on-ramp" ], "technologyProperties": { "onRampType": "NPP bank transfer", "onRampRegion": "Australia", "settlementRail": "NPP / BECS" } }, "japan": { "technologies": [ "Japanese Zengin on-ramp" ], "technologyProperties": { "onRampType": "Zengin bank transfer", "onRampRegion": "Japan", "settlementRail": "Zengin System" } }, "ireland": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "italy": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "spain": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "austria": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "finland": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "luxembourg": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "south-korea": { "technologies": [ "Korean banking on-ramp" ], "technologyProperties": { "onRampType": "KFTC bank transfer", "onRampRegion": "South Korea", "settlementRail": "KFTC / BOK-Wire" } }, "new-zealand": { "technologies": [ "NZ banking on-ramp" ], "technologyProperties": { "onRampType": "SBI bank transfer", "onRampRegion": "New Zealand", "settlementRail": "SBI / ESAS" } }, "united-arab-emirates": { "technologies": [ "UAE banking on-ramp" ], "technologyProperties": { "onRampType": "UAEFTS bank transfer", "onRampRegion": "United Arab Emirates", "settlementRail": "UAEFTS / IPP" } }, "singapore": { "technologies": [ "Singapore FAST on-ramp" ], "technologyProperties": { "onRampType": "FAST bank transfer", "onRampRegion": "Singapore", "settlementRail": "FAST / MEPS+" } }, "other": { "technologies": [ "Regional fiat on-ramp" ], "technologyProperties": { "onRampType": "Local rail bank transfer", "onRampRegion": "Region-specific", "settlementRail": "Local payment network" } } }, "showIf": { "questionId": "corridor-count", "minValue": "2-3" }, "prefillFrom": null, "briefSection": "Payment rail requirements", "text": "Second most common transfer origination country (if applicable)", "ngoText": "Second most common transfer origination country (if applicable)" }, { "id": "origination-country-3", "type": "select", "options": [ { "label": "United States", "value": "united-states" }, { "label": "United Kingdom", "value": "united-kingdom" }, { "label": "Germany", "value": "germany" }, { "label": "Netherlands", "value": "netherlands" }, { "label": "Switzerland", "value": "switzerland" }, { "label": "Belgium", "value": "belgium" }, { "label": "France", "value": "france" }, { "label": "Sweden", "value": "sweden" }, { "label": "Norway", "value": "norway" }, { "label": "Denmark", "value": "denmark" }, { "label": "Canada", "value": "canada" }, { "label": "Australia", "value": "australia" }, { "label": "Japan", "value": "japan" }, { "label": "Ireland", "value": "ireland" }, { "label": "Italy", "value": "italy" }, { "label": "Spain", "value": "spain" }, { "label": "Austria", "value": "austria" }, { "label": "Finland", "value": "finland" }, { "label": "Luxembourg", "value": "luxembourg" }, { "label": "South Korea", "value": "south-korea" }, { "label": "New Zealand", "value": "new-zealand" }, { "label": "United Arab Emirates", "value": "united-arab-emirates" }, { "label": "Singapore", "value": "singapore" }, { "label": "Other", "value": "other" } ], "propertyMapping": { "united-states": { "technologies": [ "ACH/wire fiat on-ramp" ], "technologyProperties": { "onRampType": "ACH/Fedwire bank transfer", "onRampRegion": "United States", "settlementRail": "ACH / Fedwire" } }, "united-kingdom": { "technologies": [ "UK Faster Payments on-ramp" ], "technologyProperties": { "onRampType": "Faster Payments bank transfer", "onRampRegion": "United Kingdom", "settlementRail": "FPS / BACS" } }, "germany": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "netherlands": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "switzerland": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SIC/SEPA bank transfer", "onRampRegion": "Switzerland/EU", "settlementRail": "SIC / SEPA Credit Transfer" } }, "belgium": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "france": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "sweden": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "norway": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA-adjacent bank transfer", "onRampRegion": "EEA", "settlementRail": "SEPA Credit Transfer" } }, "denmark": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "canada": { "technologies": [ "Canadian EFT on-ramp" ], "technologyProperties": { "onRampType": "Interac/EFT bank transfer", "onRampRegion": "Canada", "settlementRail": "Interac / EFT" } }, "australia": { "technologies": [ "Australian NPP on-ramp" ], "technologyProperties": { "onRampType": "NPP bank transfer", "onRampRegion": "Australia", "settlementRail": "NPP / BECS" } }, "japan": { "technologies": [ "Japanese Zengin on-ramp" ], "technologyProperties": { "onRampType": "Zengin bank transfer", "onRampRegion": "Japan", "settlementRail": "Zengin System" } }, "ireland": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "italy": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "spain": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "austria": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "finland": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "luxembourg": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "south-korea": { "technologies": [ "Korean banking on-ramp" ], "technologyProperties": { "onRampType": "KFTC bank transfer", "onRampRegion": "South Korea", "settlementRail": "KFTC / BOK-Wire" } }, "new-zealand": { "technologies": [ "NZ banking on-ramp" ], "technologyProperties": { "onRampType": "SBI bank transfer", "onRampRegion": "New Zealand", "settlementRail": "SBI / ESAS" } }, "united-arab-emirates": { "technologies": [ "UAE banking on-ramp" ], "technologyProperties": { "onRampType": "UAEFTS bank transfer", "onRampRegion": "United Arab Emirates", "settlementRail": "UAEFTS / IPP" } }, "singapore": { "technologies": [ "Singapore FAST on-ramp" ], "technologyProperties": { "onRampType": "FAST bank transfer", "onRampRegion": "Singapore", "settlementRail": "FAST / MEPS+" } }, "other": { "technologies": [ "Regional fiat on-ramp" ], "technologyProperties": { "onRampType": "Local rail bank transfer", "onRampRegion": "Region-specific", "settlementRail": "Local payment network" } } }, "showIf": { "questionId": "corridor-count", "minValue": "2-3" }, "prefillFrom": null, "briefSection": "Payment rail requirements", "text": "Third transfer origination country (if applicable)", "ngoText": "Third transfer origination country (if applicable)" }, { "id": "origination-country-4", "type": "select", "options": [ { "label": "United States", "value": "united-states" }, { "label": "United Kingdom", "value": "united-kingdom" }, { "label": "Germany", "value": "germany" }, { "label": "Netherlands", "value": "netherlands" }, { "label": "Switzerland", "value": "switzerland" }, { "label": "Belgium", "value": "belgium" }, { "label": "France", "value": "france" }, { "label": "Sweden", "value": "sweden" }, { "label": "Norway", "value": "norway" }, { "label": "Denmark", "value": "denmark" }, { "label": "Canada", "value": "canada" }, { "label": "Australia", "value": "australia" }, { "label": "Japan", "value": "japan" }, { "label": "Ireland", "value": "ireland" }, { "label": "Italy", "value": "italy" }, { "label": "Spain", "value": "spain" }, { "label": "Austria", "value": "austria" }, { "label": "Finland", "value": "finland" }, { "label": "Luxembourg", "value": "luxembourg" }, { "label": "South Korea", "value": "south-korea" }, { "label": "New Zealand", "value": "new-zealand" }, { "label": "United Arab Emirates", "value": "united-arab-emirates" }, { "label": "Singapore", "value": "singapore" }, { "label": "Other", "value": "other" } ], "propertyMapping": { "united-states": { "technologies": [ "ACH/wire fiat on-ramp" ], "technologyProperties": { "onRampType": "ACH/Fedwire bank transfer", "onRampRegion": "United States", "settlementRail": "ACH / Fedwire" } }, "united-kingdom": { "technologies": [ "UK Faster Payments on-ramp" ], "technologyProperties": { "onRampType": "Faster Payments bank transfer", "onRampRegion": "United Kingdom", "settlementRail": "FPS / BACS" } }, "germany": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "netherlands": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "switzerland": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SIC/SEPA bank transfer", "onRampRegion": "Switzerland/EU", "settlementRail": "SIC / SEPA Credit Transfer" } }, "belgium": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "france": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "sweden": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "norway": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA-adjacent bank transfer", "onRampRegion": "EEA", "settlementRail": "SEPA Credit Transfer" } }, "denmark": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "canada": { "technologies": [ "Canadian EFT on-ramp" ], "technologyProperties": { "onRampType": "Interac/EFT bank transfer", "onRampRegion": "Canada", "settlementRail": "Interac / EFT" } }, "australia": { "technologies": [ "Australian NPP on-ramp" ], "technologyProperties": { "onRampType": "NPP bank transfer", "onRampRegion": "Australia", "settlementRail": "NPP / BECS" } }, "japan": { "technologies": [ "Japanese Zengin on-ramp" ], "technologyProperties": { "onRampType": "Zengin bank transfer", "onRampRegion": "Japan", "settlementRail": "Zengin System" } }, "ireland": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "italy": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "spain": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "austria": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "finland": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "luxembourg": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "south-korea": { "technologies": [ "Korean banking on-ramp" ], "technologyProperties": { "onRampType": "KFTC bank transfer", "onRampRegion": "South Korea", "settlementRail": "KFTC / BOK-Wire" } }, "new-zealand": { "technologies": [ "NZ banking on-ramp" ], "technologyProperties": { "onRampType": "SBI bank transfer", "onRampRegion": "New Zealand", "settlementRail": "SBI / ESAS" } }, "united-arab-emirates": { "technologies": [ "UAE banking on-ramp" ], "technologyProperties": { "onRampType": "UAEFTS bank transfer", "onRampRegion": "United Arab Emirates", "settlementRail": "UAEFTS / IPP" } }, "singapore": { "technologies": [ "Singapore FAST on-ramp" ], "technologyProperties": { "onRampType": "FAST bank transfer", "onRampRegion": "Singapore", "settlementRail": "FAST / MEPS+" } }, "other": { "technologies": [ "Regional fiat on-ramp" ], "technologyProperties": { "onRampType": "Local rail bank transfer", "onRampRegion": "Region-specific", "settlementRail": "Local payment network" } } }, "showIf": { "questionId": "corridor-count", "minValue": "4-5" }, "prefillFrom": null, "briefSection": "Payment rail requirements", "text": "Fourth transfer origination country (if applicable)", "ngoText": "Fourth transfer origination country (if applicable)" }, { "id": "origination-country-5", "type": "select", "options": [ { "label": "United States", "value": "united-states" }, { "label": "United Kingdom", "value": "united-kingdom" }, { "label": "Germany", "value": "germany" }, { "label": "Netherlands", "value": "netherlands" }, { "label": "Switzerland", "value": "switzerland" }, { "label": "Belgium", "value": "belgium" }, { "label": "France", "value": "france" }, { "label": "Sweden", "value": "sweden" }, { "label": "Norway", "value": "norway" }, { "label": "Denmark", "value": "denmark" }, { "label": "Canada", "value": "canada" }, { "label": "Australia", "value": "australia" }, { "label": "Japan", "value": "japan" }, { "label": "Ireland", "value": "ireland" }, { "label": "Italy", "value": "italy" }, { "label": "Spain", "value": "spain" }, { "label": "Austria", "value": "austria" }, { "label": "Finland", "value": "finland" }, { "label": "Luxembourg", "value": "luxembourg" }, { "label": "South Korea", "value": "south-korea" }, { "label": "New Zealand", "value": "new-zealand" }, { "label": "United Arab Emirates", "value": "united-arab-emirates" }, { "label": "Singapore", "value": "singapore" }, { "label": "Other", "value": "other" } ], "propertyMapping": { "united-states": { "technologies": [ "ACH/wire fiat on-ramp" ], "technologyProperties": { "onRampType": "ACH/Fedwire bank transfer", "onRampRegion": "United States", "settlementRail": "ACH / Fedwire" } }, "united-kingdom": { "technologies": [ "UK Faster Payments on-ramp" ], "technologyProperties": { "onRampType": "Faster Payments bank transfer", "onRampRegion": "United Kingdom", "settlementRail": "FPS / BACS" } }, "germany": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "netherlands": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "switzerland": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SIC/SEPA bank transfer", "onRampRegion": "Switzerland/EU", "settlementRail": "SIC / SEPA Credit Transfer" } }, "belgium": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "france": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "sweden": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "norway": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA-adjacent bank transfer", "onRampRegion": "EEA", "settlementRail": "SEPA Credit Transfer" } }, "denmark": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "canada": { "technologies": [ "Canadian EFT on-ramp" ], "technologyProperties": { "onRampType": "Interac/EFT bank transfer", "onRampRegion": "Canada", "settlementRail": "Interac / EFT" } }, "australia": { "technologies": [ "Australian NPP on-ramp" ], "technologyProperties": { "onRampType": "NPP bank transfer", "onRampRegion": "Australia", "settlementRail": "NPP / BECS" } }, "japan": { "technologies": [ "Japanese Zengin on-ramp" ], "technologyProperties": { "onRampType": "Zengin bank transfer", "onRampRegion": "Japan", "settlementRail": "Zengin System" } }, "ireland": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "italy": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "spain": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "austria": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "finland": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "luxembourg": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "south-korea": { "technologies": [ "Korean banking on-ramp" ], "technologyProperties": { "onRampType": "KFTC bank transfer", "onRampRegion": "South Korea", "settlementRail": "KFTC / BOK-Wire" } }, "new-zealand": { "technologies": [ "NZ banking on-ramp" ], "technologyProperties": { "onRampType": "SBI bank transfer", "onRampRegion": "New Zealand", "settlementRail": "SBI / ESAS" } }, "united-arab-emirates": { "technologies": [ "UAE banking on-ramp" ], "technologyProperties": { "onRampType": "UAEFTS bank transfer", "onRampRegion": "United Arab Emirates", "settlementRail": "UAEFTS / IPP" } }, "singapore": { "technologies": [ "Singapore FAST on-ramp" ], "technologyProperties": { "onRampType": "FAST bank transfer", "onRampRegion": "Singapore", "settlementRail": "FAST / MEPS+" } }, "other": { "technologies": [ "Regional fiat on-ramp" ], "technologyProperties": { "onRampType": "Local rail bank transfer", "onRampRegion": "Region-specific", "settlementRail": "Local payment network" } } }, "showIf": { "questionId": "corridor-count", "minValue": "4-5" }, "prefillFrom": null, "briefSection": "Payment rail requirements", "text": "Fifth transfer origination country (if applicable)", "ngoText": "Fifth transfer origination country (if applicable)" }, { "id": "funding-method", "type": "select", "options": [ { "label": "Bank transfer from organisation account", "value": "bank-transfer" }, { "label": "Card payment from organisation", "value": "card-payment" }, { "label": "Direct stablecoin funding (organisation already holds stablecoins)", "value": "direct-stablecoin" }, { "label": "Mixed: bank transfer for most, card for urgent payments", "value": "mixed-methods" } ], "propertyMapping": { "bank-transfer": { "technologies": [ "Bank-integrated fiat on-ramp" ], "technologyProperties": { "fundingSource": "Organisation bank account", "onRampSpeed": "1-2 business days (SEPA/ACH) or same-day (Faster Payments/wire)", "kybRequired": "Yes \u2014 organisation KYB verification" } }, "card-payment": { "technologies": [ "Card payment on-ramp" ], "technologyProperties": { "fundingSource": "Organisation payment card", "onRampSpeed": "Near-instant", "kybRequired": "Yes \u2014 card verification and organisation KYB" } }, "direct-stablecoin": { "technologies": [ "Direct stablecoin treasury funding" ], "technologyProperties": { "fundingSource": "Existing stablecoin holdings", "onRampSpeed": "Immediate (no fiat conversion needed)", "kybRequired": "Wallet verification only" } }, "mixed-methods": { "technologies": [ "Multi-method fiat on-ramp", "Card payment on-ramp" ], "technologyProperties": { "fundingSource": "Bank transfer (primary) + card (urgent)", "onRampSpeed": "Varies by method", "kybRequired": "Yes \u2014 full organisation KYB" } } }, "prefillFrom": null, "briefSection": "Payment rail requirements", "text": "How does your organisation currently fund international transfers or payments?", "ngoText": "How does your organisation currently fund international transfers or payments?" }, { "id": "office-count", "type": "select", "options": [ { "label": "2-3 offices", "value": "small" }, { "label": "4-10 offices", "value": "medium" }, { "label": "11-25 offices", "value": "large" }, { "label": "Over 25 offices", "value": "enterprise" } ], "propertyMapping": { "small": { "technologies": [ "Layer 1 payment rail", "Multi-signature wallet" ], "technologyProperties": { "networkTopology": "Hub-and-spoke", "approvalWorkflow": "Simple multi-sig" } }, "medium": { "technologies": [ "Layer 1 payment rail", "Multi-signature wallet", "Treasury management module" ], "technologyProperties": { "networkTopology": "Hub-and-spoke with regional hubs", "approvalWorkflow": "Tiered multi-sig" } }, "large": { "technologies": [ "Layer 1 payment rail", "Enterprise treasury platform", "Multi-signature wallet" ], "technologyProperties": { "networkTopology": "Multi-hub federated", "approvalWorkflow": "Role-based multi-sig" } }, "enterprise": { "technologies": [ "Layer 1 payment rail", "Enterprise treasury platform", "Automated routing engine" ], "technologyProperties": { "networkTopology": "Fully meshed with automated routing", "approvalWorkflow": "Policy-driven automated approval" } } }, "prefillFrom": "P0-orgSize", "briefSection": "Payment rail requirements", "text": "How many country offices or programme sites transfer funds between each other?", "ngoText": "How many country offices or programme sites transfer funds between each other?" }, { "id": "transfer-frequency", "type": "select", "options": [ { "label": "Weekly or more frequently", "value": "weekly" }, { "label": "Monthly", "value": "monthly" }, { "label": "Quarterly", "value": "quarterly" }, { "label": "Ad-hoc / as-needed only", "value": "adhoc" } ], "propertyMapping": { "weekly": { "technologies": [ "Automated transfer scheduling" ], "technologyProperties": { "automationLevel": "Scheduled recurring transfers", "liquidityManagement": "Pre-funded wallets recommended" } }, "monthly": { "technologies": [ "Scheduled transfer module" ], "technologyProperties": { "automationLevel": "Monthly batch scheduling", "liquidityManagement": "Standard" } }, "quarterly": { "technologies": [], "technologyProperties": { "automationLevel": "Manual initiation acceptable", "liquidityManagement": "Standard" } }, "adhoc": { "technologies": [], "technologyProperties": { "automationLevel": "On-demand initiation", "liquidityManagement": "Flexible" } } }, "prefillFrom": null, "briefSection": "Payment operations", "text": "How frequently do inter-office transfers occur?", "ngoText": "How frequently do inter-office transfers occur?" }, { "id": "transfer-size-interoffice", "type": "select", "options": [ { "label": "Under $10,000", "value": "small" }, { "label": "$10,000\u2013$100,000", "value": "medium" }, { "label": "$100,000\u2013$1,000,000", "value": "large" }, { "label": "Over $1,000,000", "value": "very-large" }, { "label": "Highly variable: ranges across all sizes depending on transfer type", "value": "variable" } ], "propertyMapping": { "small": { "technologies": [ "Layer 1 payment rail", "Stablecoin" ], "technologyProperties": { "transactionLimits": "Standard", "liquidityRequirement": "Low" } }, "medium": { "technologies": [ "Layer 1 payment rail", "Stablecoin", "Liquidity pool access" ], "technologyProperties": { "transactionLimits": "Medium", "liquidityRequirement": "Moderate \u2014 on/off-ramp liquidity check needed" } }, "large": { "technologies": [ "Layer 1 payment rail", "Stablecoin", "OTC desk or liquidity aggregator" ], "technologyProperties": { "transactionLimits": "High", "liquidityRequirement": "High \u2014 OTC or pre-arranged liquidity" } }, "very-large": { "technologies": [ "Layer 1 payment rail", "Stablecoin", "Institutional OTC desk" ], "technologyProperties": { "transactionLimits": "Institutional", "liquidityRequirement": "Institutional-grade \u2014 slippage management critical" } }, "variable": { "technologies": [ "Layer 1 payment rail", "Stablecoin", "Liquidity pool access", "OTC desk or liquidity aggregator" ], "technologyProperties": { "transactionLimits": "Variable \u2014 solution must handle full range", "liquidityRequirement": "High \u2014 must accommodate both small and large transfers" } } }, "prefillFrom": null, "briefSection": "Payment rail requirements", "text": "What is the typical size of inter-office fund transfers?", "ngoText": "What is the typical size of inter-office fund transfers?" }, { "id": "approval-workflow", "type": "select", "options": [ { "label": "Single authoriser", "value": "single" }, { "label": "Dual authorisation (maker-checker)", "value": "dual" }, { "label": "Multi-level approval (3+ signers)", "value": "multi-level" }, { "label": "Threshold-based: varies by amount", "value": "threshold" } ], "propertyMapping": { "single": { "technologies": [ "Single-signature wallet" ], "technologyProperties": { "approvalMechanism": "Single key", "signingThreshold": "1-of-1" } }, "dual": { "technologies": [ "Multi-signature wallet" ], "technologyProperties": { "approvalMechanism": "Multi-sig maker-checker", "signingThreshold": "2-of-2 or 2-of-3" } }, "multi-level": { "technologies": [ "Multi-signature wallet", "Approval workflow engine" ], "technologyProperties": { "approvalMechanism": "Sequential multi-sig", "signingThreshold": "M-of-N configurable" } }, "threshold": { "technologies": [ "Smart contract approval policy", "Multi-signature wallet" ], "technologyProperties": { "approvalMechanism": "Amount-based policy routing", "signingThreshold": "Dynamic \u2014 low:1, medium:2, high:3+" } } }, "prefillFrom": null, "briefSection": "Governance and controls", "text": "What approval process is required for inter-office transfers?", "ngoText": "What approval process is required for inter-office transfers?", "hidden": true }, { "id": "reconciliation-interoffice", "type": "select", "options": [ { "label": "Real-time automated reconciliation", "value": "realtime" }, { "label": "Manual reconciliation at month-end", "value": "monthly-manual" }, { "label": "Periodic but inconsistent", "value": "inconsistent" }, { "label": "Problematic: frequent discrepancies", "value": "problematic" } ], "propertyMapping": { "realtime": { "technologies": [], "technologyProperties": { "reconciliationNeed": "Maintain current capability", "improvementPriority": "Low" } }, "monthly-manual": { "technologies": [ "Automated reconciliation engine" ], "technologyProperties": { "reconciliationNeed": "Automate monthly process", "improvementPriority": "Medium" } }, "inconsistent": { "technologies": [ "Automated reconciliation engine", "Real-time ledger sync" ], "technologyProperties": { "reconciliationNeed": "Standardise and automate", "improvementPriority": "High" } }, "problematic": { "technologies": [ "Real-time shared ledger", "Automated reconciliation engine", "Discrepancy alerting" ], "technologyProperties": { "reconciliationNeed": "Eliminate manual reconciliation", "improvementPriority": "Critical" } } }, "prefillFrom": "P2-CatA-Q8a", "briefSection": "Reporting and audit", "text": "How is inter-office reconciliation currently handled?", "ngoText": "How is inter-office reconciliation currently handled?" }, { "id": "accounting-integration-interoffice", "type": "select", "options": [ { "label": "Yes, single centralised system", "value": "centralised" }, { "label": "Same system but separate instances per country", "value": "same-separate" }, { "label": "Different systems across offices", "value": "different" }, { "label": "Some offices have no formal system", "value": "partial" } ], "propertyMapping": { "centralised": { "technologies": [ "Single accounting system connection" ], "technologyProperties": { "integrationComplexity": "Low \u2014 single system connection", "dataSync": "Centralised" } }, "same-separate": { "technologies": [ "Multi-office accounting system connection" ], "technologyProperties": { "integrationComplexity": "Medium \u2014 multiple instances", "dataSync": "Instance-level sync" } }, "different": { "technologies": [ "Multi-system integration layer", "Data format alignment" ], "technologyProperties": { "integrationComplexity": "High \u2014 multiple connectors", "dataSync": "Normalised cross-system" } }, "partial": { "technologies": [ "Standalone ledger module", "Multi-system integration layer" ], "technologyProperties": { "integrationComplexity": "High \u2014 gap-filling required", "dataSync": "Hybrid centralised + standalone" } } }, "prefillFrom": "P0-S3-Q13", "briefSection": "Integration requirements", "text": "Do all your offices use the same accounting system?", "ngoText": "Do all your offices use the same accounting system?" }, { "id": "sq-UC-A-004-001", "type": "single-select", "options": [ { "value": "real-time-fx", "label": "Real-time FX rate conversion" }, { "value": "locked-rate", "label": "Locked rate at time of approval" }, { "value": "stablecoin-bridge", "label": "Stablecoin as bridge currency" }, { "value": "fiat-only", "label": "Fiat-only transfers (no crypto bridge)" }, { "value": "multi-hop", "label": "Multi-hop route optimization" } ], "propertyMapping": { "real-time-fx": { "technologies": [ "fx-rate-oracle", "real-time-pricing" ], "technologyProperties": {} }, "locked-rate": { "technologies": [ "rate-locking-engine", "settlement-scheduling" ], "technologyProperties": {} }, "stablecoin-bridge": { "technologies": [ "stablecoin-bridge", "on-chain-settlement" ], "technologyProperties": {} }, "fiat-only": { "technologies": [ "traditional-banking-rails", "correspondent-banking" ], "technologyProperties": {} }, "multi-hop": { "technologies": [ "route-optimization", "liquidity-aggregation" ], "technologyProperties": {} } }, "briefSection": "requirements", "text": "What currency conversion approach do you currently use for inter-office transfers?", "ngoText": "What currency conversion approach do you currently use for inter-office transfers?" }, { "id": "offramp-delivery", "type": "select", "options": [ { "label": "Mobile money", "value": "mobile-money" }, { "label": "Bank transfer to beneficiary/recipient account", "value": "bank-transfer" }, { "label": "Cash via agent network", "value": "agent-cash" }, { "label": "Mixed: depends on recipient location and access", "value": "mixed" } ], "propertyMapping": { "mobile-money": { "technologies": [ "Mobile money off-ramp integration", "MNO API gateway" ], "technologyProperties": { "lastMileChannel": "MNO API integration", "cashOutMethod": "Mobile money wallet top-up" } }, "bank-transfer": { "technologies": [ "Bank-integrated off-ramp", "Local bank API integration" ], "technologyProperties": { "lastMileChannel": "Bank transfer", "cashOutMethod": "Direct bank deposit" } }, "agent-cash": { "technologies": [ "Agent network off-ramp", "Agent cash-out network" ], "technologyProperties": { "lastMileChannel": "Agent network", "cashOutMethod": "Cash via registered agent" } }, "mixed": { "technologies": [ "Multi-channel off-ramp gateway", "Mobile money off-ramp integration", "Agent cash-out network" ], "technologyProperties": { "lastMileChannel": "Mobile money + agent + bank", "cashOutMethod": "Recipient choice" } } }, "prefillFrom": null, "briefSection": "Last-mile delivery", "text": "How will recipients receive funds at the last mile?", "ngoText": "How will recipients receive funds at the last mile?" } ], "complexityFactors": { "relationships": 1, "operationalChange": 1, "dataCompliance": 2 }, "securityTier": "B", "suggestedCriteria": [ { "id": "SC-INTERNAL-SPEED", "name": "Transfer Speed Between Offices", "description": "This measures how quickly funds can move between HQ and country offices, or between country programmes. Traditional inter-office transfers can take days through correspondent banking.", "weight": 0.25, "ratingGuide": { "5": "Near-instant transfers between any offices. No correspondent bank delays. Funds available immediately for programme use.", "4": "Same-day transfers in most corridors. Minor delays for complex routes.", "3": "1-2 day transfers. Faster than traditional banking but not instant.", "2": "2-5 day transfers. Marginal improvement over existing banking.", "1": "No speed improvement over traditional correspondent banking." } }, { "id": "SC-TREASURY-CTRL", "name": "Treasury Control & Approval Workflows", "description": "The provider supports multi-signature authorisation and approval hierarchies. Inter-office transfers require treasury oversight with configurable approval chains.", "weight": 0.25, "ratingGuide": { "5": "Configurable multi-sig (2-of-3, 3-of-5, etc.). Role-based approval chains. Spending limits per office. Real-time treasury dashboard.", "4": "Multi-sig support. Basic approval chains. Per-office limits. Good dashboard.", "3": "Dual authorisation. Fixed approval flow. Organisation-wide limits only.", "2": "Single authorisation with optional second signer. No per-office controls.", "1": "No multi-signature or approval workflows. Single-person control." } }, { "id": "SC-ACCOUNTING-INT", "name": "Accounting System Integration", "description": "The provider integrates with the organisation's accounting software. Inter-office transfers must be automatically recorded in the general ledger with correct fund coding.", "weight": 0.2, "ratingGuide": { "5": "Direct API integration with the main accounting platforms NGOs use. Automatic journal entries with fund/project coding.", "4": "Integration with 2-3 major accounting platforms. Automatic basic journal entries.", "3": "CSV/spreadsheet export formatted for accounting import. Semi-automated posting.", "2": "Transaction reports only. Manual journal entry creation required.", "1": "No export capability. All accounting recording manual." } }, { "id": "SC-FX-MANAGEMENT", "name": "Foreign Exchange Management", "description": "This looks at how the provider handles currency conversion between offices. Large organisations transfer millions across currencies. FX rates and timing matter significantly.", "weight": 0.2, "ratingGuide": { "5": "Mid-market rates. Rate locking for large transfers. Forward contracts available. Full FX cost transparency. Historical rate reporting.", "4": "Competitive rates with rate locking. Good transparency. Limited forward contracts.", "3": "Reasonable rates applied at transfer time. Cost visible but not lockable.", "2": "Above-market rates. No locking. Limited transparency on FX costs.", "1": "Poor FX rates. Opaque pricing. Significant hidden costs." } }, { "id": "SC-FUND-TRACKING", "name": "Fund Restriction & Project Code Tracking", "description": "Transfers can maintain fund restriction labels and project codes through the transfer. Restricted donor funds must remain tagged from HQ through to country office spending.", "weight": 0.1, "ratingGuide": { "5": "Metadata fields for fund codes, project codes, and restriction tags. Codes survive transfer. Reporting by fund/project across offices.", "4": "Fund code support. Tags maintained through transfer. Basic cross-office reporting.", "3": "Reference field available for coding. Manual tracking of restrictions across offices.", "2": "Free-text reference only. No structured fund tracking.", "1": "No metadata or reference capability. Transfers are anonymous." } } ], "procurement": { "marketMaturity": "emerging", "primaryMode": "tender", "alternativeModes": [ "off-the-shelf" ], "reasoning": "Inter-office treasury tools available but require multi-jurisdiction configuration.", "exampleProductCategories": [ "treasury-management-saas", "intercompany-payments-platform" ], "partnerChannels": [], "lastReviewed": "2026-05-01" } }, { "id": "UC-A-005", "name": "Emergency rapid-disbursement payments", "category": "A", "subcategory": "Emergency Response", "description": "Get cash to affected people within hours of an emergency decision, even when they are spread out and few banks are working.", "bCriteria": [ "B4", "B5", "B7" ], "requiredComponents": [ { "component": "payment-rails", "description": "Fast settlement blockchain network" }, { "component": "stablecoin", "description": "Stablecoin for rapid payments" }, { "component": "on-ramp", "description": "Quick fiat conversion" }, { "component": "off-ramp", "description": "Fast local currency conversion" }, { "component": "beneficiary-wallet", "description": "Quick wallet provisioning" }, { "component": "smart-contracts", "description": "Automated disbursement triggers" } ], "conditionalComponents": [ { "component": "offline-sync", "condition": "If connectivity is limited in emergency areas" }, { "component": "compliance-screening", "condition": "If AML/KYC required before disbursement" } ], "crossCategoryDependencies": [ "UC-C-045 if pre-consented beneficiary lists", "UC-E-069 if community targeting used" ], "p2TriggerConditions": { "description": "Activated when P2 shows emergency response work + time pressure + dispersed beneficiaries", "rangeSignals": [ "emergencyResponse >= true", "timeToFirst Payment <= 24-48 hours", "beneficiaryDispersion >= high" ] }, "contextFieldsTemplate": [ { "field": "emergencyFrequency", "source": "P0 programme types", "description": "How often emergencies occur" }, { "field": "targetBeneficiaries", "source": "P2 emergency scales", "description": "Number of people to reach" }, { "field": "disbursementAmount", "source": "P2 cash amounts", "description": "Average payment per beneficiary" }, { "field": "timeConstraints", "source": "P2 emergency response protocols", "description": "Required disbursement timeline" } ], "implementationComplexity": "medium-high", "examples": { "note": "Disaster cash assistance programmes", "references": [ { "name": "Start Network", "url": "https://startnetwork.org/blockchain", "solved": "Accelerated emergency funding payouts with enhanced transparency" }, { "name": "Mercy Corps", "url": "https://www.mercycorps.org/blog/digital-cash-supports-farmers-rebuilding", "solved": "Delivered digital cash aid fast to farmers in conflict-affected zones" }, { "name": "Oxfam UnBlocked Cash", "url": "https://www.oxfam.org/en/unblocked-cash-project-using-blockchain-technology-revolutionize-humanitarian-aid", "solved": "Accelerated cash delivery and reduced transaction costs in remote Pacific islands" } ] }, "solutionQuestions": [ { "id": "corridor-count", "type": "select", "options": [ { "label": "Single country", "value": "single" }, { "label": "2\u20133 countries", "value": "2-3" }, { "label": "4\u20135 countries", "value": "4-5" }, { "label": "More than 5 countries", "value": "5-plus" } ], "propertyMapping": { "single": { "technologies": [ "Single-corridor fiat on-ramp" ], "technologyProperties": { "corridorComplexity": "Single origination country", "multiRailNeeded": "No" } }, "2-3": { "technologies": [ "Multi-corridor fiat on-ramp gateway" ], "technologyProperties": { "corridorComplexity": "2\u20133 origination countries", "multiRailNeeded": "Yes \u2014 2-3 payment rails" } }, "4-5": { "technologies": [ "Multi-corridor fiat on-ramp gateway" ], "technologyProperties": { "corridorComplexity": "4\u20135 origination countries", "multiRailNeeded": "Yes \u2014 4-5 payment rails" } }, "5-plus": { "technologies": [ "Enterprise multi-corridor on-ramp gateway" ], "technologyProperties": { "corridorComplexity": "5+ origination countries", "multiRailNeeded": "Yes \u2014 enterprise-grade multi-rail" } } }, "prefillFrom": null, "briefSection": "Payment rail requirements", "text": "How many countries does your organisation send transfer funds from?", "ngoText": "How many countries does your organisation send transfer funds from?" }, { "id": "origination-country-1", "type": "select", "options": [ { "label": "United States", "value": "united-states" }, { "label": "United Kingdom", "value": "united-kingdom" }, { "label": "Germany", "value": "germany" }, { "label": "Netherlands", "value": "netherlands" }, { "label": "Switzerland", "value": "switzerland" }, { "label": "Belgium", "value": "belgium" }, { "label": "France", "value": "france" }, { "label": "Sweden", "value": "sweden" }, { "label": "Norway", "value": "norway" }, { "label": "Denmark", "value": "denmark" }, { "label": "Canada", "value": "canada" }, { "label": "Australia", "value": "australia" }, { "label": "Japan", "value": "japan" }, { "label": "Ireland", "value": "ireland" }, { "label": "Italy", "value": "italy" }, { "label": "Spain", "value": "spain" }, { "label": "Austria", "value": "austria" }, { "label": "Finland", "value": "finland" }, { "label": "Luxembourg", "value": "luxembourg" }, { "label": "South Korea", "value": "south-korea" }, { "label": "New Zealand", "value": "new-zealand" }, { "label": "United Arab Emirates", "value": "united-arab-emirates" }, { "label": "Singapore", "value": "singapore" }, { "label": "Other", "value": "other" } ], "propertyMapping": { "united-states": { "technologies": [ "ACH/wire fiat on-ramp" ], "technologyProperties": { "onRampType": "ACH/Fedwire bank transfer", "onRampRegion": "United States", "settlementRail": "ACH / Fedwire" } }, "united-kingdom": { "technologies": [ "UK Faster Payments on-ramp" ], "technologyProperties": { "onRampType": "Faster Payments bank transfer", "onRampRegion": "United Kingdom", "settlementRail": "FPS / BACS" } }, "germany": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "netherlands": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "switzerland": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SIC/SEPA bank transfer", "onRampRegion": "Switzerland/EU", "settlementRail": "SIC / SEPA Credit Transfer" } }, "belgium": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "france": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "sweden": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "norway": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA-adjacent bank transfer", "onRampRegion": "EEA", "settlementRail": "SEPA Credit Transfer" } }, "denmark": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "canada": { "technologies": [ "Canadian EFT on-ramp" ], "technologyProperties": { "onRampType": "Interac/EFT bank transfer", "onRampRegion": "Canada", "settlementRail": "Interac / EFT" } }, "australia": { "technologies": [ "Australian NPP on-ramp" ], "technologyProperties": { "onRampType": "NPP bank transfer", "onRampRegion": "Australia", "settlementRail": "NPP / BECS" } }, "japan": { "technologies": [ "Japanese Zengin on-ramp" ], "technologyProperties": { "onRampType": "Zengin bank transfer", "onRampRegion": "Japan", "settlementRail": "Zengin System" } }, "ireland": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "italy": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "spain": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "austria": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "finland": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "luxembourg": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "south-korea": { "technologies": [ "Korean banking on-ramp" ], "technologyProperties": { "onRampType": "KFTC bank transfer", "onRampRegion": "South Korea", "settlementRail": "KFTC / BOK-Wire" } }, "new-zealand": { "technologies": [ "NZ banking on-ramp" ], "technologyProperties": { "onRampType": "SBI bank transfer", "onRampRegion": "New Zealand", "settlementRail": "SBI / ESAS" } }, "united-arab-emirates": { "technologies": [ "UAE banking on-ramp" ], "technologyProperties": { "onRampType": "UAEFTS bank transfer", "onRampRegion": "United Arab Emirates", "settlementRail": "UAEFTS / IPP" } }, "singapore": { "technologies": [ "Singapore FAST on-ramp" ], "technologyProperties": { "onRampType": "FAST bank transfer", "onRampRegion": "Singapore", "settlementRail": "FAST / MEPS+" } }, "other": { "technologies": [ "Regional fiat on-ramp" ], "technologyProperties": { "onRampType": "Local rail bank transfer", "onRampRegion": "Region-specific", "settlementRail": "Local payment network" } } }, "showIf": { "questionId": "corridor-count", "minValue": "single" }, "prefillFrom": null, "briefSection": "Payment rail requirements", "text": "Which country do you most frequently initiate transfers from?", "ngoText": "Which country do you most frequently initiate transfers from?" }, { "id": "origination-country-2", "type": "select", "options": [ { "label": "United States", "value": "united-states" }, { "label": "United Kingdom", "value": "united-kingdom" }, { "label": "Germany", "value": "germany" }, { "label": "Netherlands", "value": "netherlands" }, { "label": "Switzerland", "value": "switzerland" }, { "label": "Belgium", "value": "belgium" }, { "label": "France", "value": "france" }, { "label": "Sweden", "value": "sweden" }, { "label": "Norway", "value": "norway" }, { "label": "Denmark", "value": "denmark" }, { "label": "Canada", "value": "canada" }, { "label": "Australia", "value": "australia" }, { "label": "Japan", "value": "japan" }, { "label": "Ireland", "value": "ireland" }, { "label": "Italy", "value": "italy" }, { "label": "Spain", "value": "spain" }, { "label": "Austria", "value": "austria" }, { "label": "Finland", "value": "finland" }, { "label": "Luxembourg", "value": "luxembourg" }, { "label": "South Korea", "value": "south-korea" }, { "label": "New Zealand", "value": "new-zealand" }, { "label": "United Arab Emirates", "value": "united-arab-emirates" }, { "label": "Singapore", "value": "singapore" }, { "label": "Other", "value": "other" } ], "propertyMapping": { "united-states": { "technologies": [ "ACH/wire fiat on-ramp" ], "technologyProperties": { "onRampType": "ACH/Fedwire bank transfer", "onRampRegion": "United States", "settlementRail": "ACH / Fedwire" } }, "united-kingdom": { "technologies": [ "UK Faster Payments on-ramp" ], "technologyProperties": { "onRampType": "Faster Payments bank transfer", "onRampRegion": "United Kingdom", "settlementRail": "FPS / BACS" } }, "germany": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "netherlands": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "switzerland": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SIC/SEPA bank transfer", "onRampRegion": "Switzerland/EU", "settlementRail": "SIC / SEPA Credit Transfer" } }, "belgium": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "france": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "sweden": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "norway": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA-adjacent bank transfer", "onRampRegion": "EEA", "settlementRail": "SEPA Credit Transfer" } }, "denmark": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "canada": { "technologies": [ "Canadian EFT on-ramp" ], "technologyProperties": { "onRampType": "Interac/EFT bank transfer", "onRampRegion": "Canada", "settlementRail": "Interac / EFT" } }, "australia": { "technologies": [ "Australian NPP on-ramp" ], "technologyProperties": { "onRampType": "NPP bank transfer", "onRampRegion": "Australia", "settlementRail": "NPP / BECS" } }, "japan": { "technologies": [ "Japanese Zengin on-ramp" ], "technologyProperties": { "onRampType": "Zengin bank transfer", "onRampRegion": "Japan", "settlementRail": "Zengin System" } }, "ireland": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "italy": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "spain": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "austria": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "finland": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "luxembourg": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "south-korea": { "technologies": [ "Korean banking on-ramp" ], "technologyProperties": { "onRampType": "KFTC bank transfer", "onRampRegion": "South Korea", "settlementRail": "KFTC / BOK-Wire" } }, "new-zealand": { "technologies": [ "NZ banking on-ramp" ], "technologyProperties": { "onRampType": "SBI bank transfer", "onRampRegion": "New Zealand", "settlementRail": "SBI / ESAS" } }, "united-arab-emirates": { "technologies": [ "UAE banking on-ramp" ], "technologyProperties": { "onRampType": "UAEFTS bank transfer", "onRampRegion": "United Arab Emirates", "settlementRail": "UAEFTS / IPP" } }, "singapore": { "technologies": [ "Singapore FAST on-ramp" ], "technologyProperties": { "onRampType": "FAST bank transfer", "onRampRegion": "Singapore", "settlementRail": "FAST / MEPS+" } }, "other": { "technologies": [ "Regional fiat on-ramp" ], "technologyProperties": { "onRampType": "Local rail bank transfer", "onRampRegion": "Region-specific", "settlementRail": "Local payment network" } } }, "showIf": { "questionId": "corridor-count", "minValue": "2-3" }, "prefillFrom": null, "briefSection": "Payment rail requirements", "text": "Second most common transfer origination country (if applicable)", "ngoText": "Second most common transfer origination country (if applicable)" }, { "id": "origination-country-3", "type": "select", "options": [ { "label": "United States", "value": "united-states" }, { "label": "United Kingdom", "value": "united-kingdom" }, { "label": "Germany", "value": "germany" }, { "label": "Netherlands", "value": "netherlands" }, { "label": "Switzerland", "value": "switzerland" }, { "label": "Belgium", "value": "belgium" }, { "label": "France", "value": "france" }, { "label": "Sweden", "value": "sweden" }, { "label": "Norway", "value": "norway" }, { "label": "Denmark", "value": "denmark" }, { "label": "Canada", "value": "canada" }, { "label": "Australia", "value": "australia" }, { "label": "Japan", "value": "japan" }, { "label": "Ireland", "value": "ireland" }, { "label": "Italy", "value": "italy" }, { "label": "Spain", "value": "spain" }, { "label": "Austria", "value": "austria" }, { "label": "Finland", "value": "finland" }, { "label": "Luxembourg", "value": "luxembourg" }, { "label": "South Korea", "value": "south-korea" }, { "label": "New Zealand", "value": "new-zealand" }, { "label": "United Arab Emirates", "value": "united-arab-emirates" }, { "label": "Singapore", "value": "singapore" }, { "label": "Other", "value": "other" } ], "propertyMapping": { "united-states": { "technologies": [ "ACH/wire fiat on-ramp" ], "technologyProperties": { "onRampType": "ACH/Fedwire bank transfer", "onRampRegion": "United States", "settlementRail": "ACH / Fedwire" } }, "united-kingdom": { "technologies": [ "UK Faster Payments on-ramp" ], "technologyProperties": { "onRampType": "Faster Payments bank transfer", "onRampRegion": "United Kingdom", "settlementRail": "FPS / BACS" } }, "germany": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "netherlands": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "switzerland": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SIC/SEPA bank transfer", "onRampRegion": "Switzerland/EU", "settlementRail": "SIC / SEPA Credit Transfer" } }, "belgium": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "france": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "sweden": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "norway": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA-adjacent bank transfer", "onRampRegion": "EEA", "settlementRail": "SEPA Credit Transfer" } }, "denmark": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "canada": { "technologies": [ "Canadian EFT on-ramp" ], "technologyProperties": { "onRampType": "Interac/EFT bank transfer", "onRampRegion": "Canada", "settlementRail": "Interac / EFT" } }, "australia": { "technologies": [ "Australian NPP on-ramp" ], "technologyProperties": { "onRampType": "NPP bank transfer", "onRampRegion": "Australia", "settlementRail": "NPP / BECS" } }, "japan": { "technologies": [ "Japanese Zengin on-ramp" ], "technologyProperties": { "onRampType": "Zengin bank transfer", "onRampRegion": "Japan", "settlementRail": "Zengin System" } }, "ireland": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "italy": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "spain": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "austria": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "finland": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "luxembourg": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "south-korea": { "technologies": [ "Korean banking on-ramp" ], "technologyProperties": { "onRampType": "KFTC bank transfer", "onRampRegion": "South Korea", "settlementRail": "KFTC / BOK-Wire" } }, "new-zealand": { "technologies": [ "NZ banking on-ramp" ], "technologyProperties": { "onRampType": "SBI bank transfer", "onRampRegion": "New Zealand", "settlementRail": "SBI / ESAS" } }, "united-arab-emirates": { "technologies": [ "UAE banking on-ramp" ], "technologyProperties": { "onRampType": "UAEFTS bank transfer", "onRampRegion": "United Arab Emirates", "settlementRail": "UAEFTS / IPP" } }, "singapore": { "technologies": [ "Singapore FAST on-ramp" ], "technologyProperties": { "onRampType": "FAST bank transfer", "onRampRegion": "Singapore", "settlementRail": "FAST / MEPS+" } }, "other": { "technologies": [ "Regional fiat on-ramp" ], "technologyProperties": { "onRampType": "Local rail bank transfer", "onRampRegion": "Region-specific", "settlementRail": "Local payment network" } } }, "showIf": { "questionId": "corridor-count", "minValue": "2-3" }, "prefillFrom": null, "briefSection": "Payment rail requirements", "text": "Third transfer origination country (if applicable)", "ngoText": "Third transfer origination country (if applicable)" }, { "id": "origination-country-4", "type": "select", "options": [ { "label": "United States", "value": "united-states" }, { "label": "United Kingdom", "value": "united-kingdom" }, { "label": "Germany", "value": "germany" }, { "label": "Netherlands", "value": "netherlands" }, { "label": "Switzerland", "value": "switzerland" }, { "label": "Belgium", "value": "belgium" }, { "label": "France", "value": "france" }, { "label": "Sweden", "value": "sweden" }, { "label": "Norway", "value": "norway" }, { "label": "Denmark", "value": "denmark" }, { "label": "Canada", "value": "canada" }, { "label": "Australia", "value": "australia" }, { "label": "Japan", "value": "japan" }, { "label": "Ireland", "value": "ireland" }, { "label": "Italy", "value": "italy" }, { "label": "Spain", "value": "spain" }, { "label": "Austria", "value": "austria" }, { "label": "Finland", "value": "finland" }, { "label": "Luxembourg", "value": "luxembourg" }, { "label": "South Korea", "value": "south-korea" }, { "label": "New Zealand", "value": "new-zealand" }, { "label": "United Arab Emirates", "value": "united-arab-emirates" }, { "label": "Singapore", "value": "singapore" }, { "label": "Other", "value": "other" } ], "propertyMapping": { "united-states": { "technologies": [ "ACH/wire fiat on-ramp" ], "technologyProperties": { "onRampType": "ACH/Fedwire bank transfer", "onRampRegion": "United States", "settlementRail": "ACH / Fedwire" } }, "united-kingdom": { "technologies": [ "UK Faster Payments on-ramp" ], "technologyProperties": { "onRampType": "Faster Payments bank transfer", "onRampRegion": "United Kingdom", "settlementRail": "FPS / BACS" } }, "germany": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "netherlands": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "switzerland": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SIC/SEPA bank transfer", "onRampRegion": "Switzerland/EU", "settlementRail": "SIC / SEPA Credit Transfer" } }, "belgium": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "france": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "sweden": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "norway": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA-adjacent bank transfer", "onRampRegion": "EEA", "settlementRail": "SEPA Credit Transfer" } }, "denmark": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "canada": { "technologies": [ "Canadian EFT on-ramp" ], "technologyProperties": { "onRampType": "Interac/EFT bank transfer", "onRampRegion": "Canada", "settlementRail": "Interac / EFT" } }, "australia": { "technologies": [ "Australian NPP on-ramp" ], "technologyProperties": { "onRampType": "NPP bank transfer", "onRampRegion": "Australia", "settlementRail": "NPP / BECS" } }, "japan": { "technologies": [ "Japanese Zengin on-ramp" ], "technologyProperties": { "onRampType": "Zengin bank transfer", "onRampRegion": "Japan", "settlementRail": "Zengin System" } }, "ireland": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "italy": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "spain": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "austria": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "finland": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "luxembourg": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "south-korea": { "technologies": [ "Korean banking on-ramp" ], "technologyProperties": { "onRampType": "KFTC bank transfer", "onRampRegion": "South Korea", "settlementRail": "KFTC / BOK-Wire" } }, "new-zealand": { "technologies": [ "NZ banking on-ramp" ], "technologyProperties": { "onRampType": "SBI bank transfer", "onRampRegion": "New Zealand", "settlementRail": "SBI / ESAS" } }, "united-arab-emirates": { "technologies": [ "UAE banking on-ramp" ], "technologyProperties": { "onRampType": "UAEFTS bank transfer", "onRampRegion": "United Arab Emirates", "settlementRail": "UAEFTS / IPP" } }, "singapore": { "technologies": [ "Singapore FAST on-ramp" ], "technologyProperties": { "onRampType": "FAST bank transfer", "onRampRegion": "Singapore", "settlementRail": "FAST / MEPS+" } }, "other": { "technologies": [ "Regional fiat on-ramp" ], "technologyProperties": { "onRampType": "Local rail bank transfer", "onRampRegion": "Region-specific", "settlementRail": "Local payment network" } } }, "showIf": { "questionId": "corridor-count", "minValue": "4-5" }, "prefillFrom": null, "briefSection": "Payment rail requirements", "text": "Fourth transfer origination country (if applicable)", "ngoText": "Fourth transfer origination country (if applicable)" }, { "id": "origination-country-5", "type": "select", "options": [ { "label": "United States", "value": "united-states" }, { "label": "United Kingdom", "value": "united-kingdom" }, { "label": "Germany", "value": "germany" }, { "label": "Netherlands", "value": "netherlands" }, { "label": "Switzerland", "value": "switzerland" }, { "label": "Belgium", "value": "belgium" }, { "label": "France", "value": "france" }, { "label": "Sweden", "value": "sweden" }, { "label": "Norway", "value": "norway" }, { "label": "Denmark", "value": "denmark" }, { "label": "Canada", "value": "canada" }, { "label": "Australia", "value": "australia" }, { "label": "Japan", "value": "japan" }, { "label": "Ireland", "value": "ireland" }, { "label": "Italy", "value": "italy" }, { "label": "Spain", "value": "spain" }, { "label": "Austria", "value": "austria" }, { "label": "Finland", "value": "finland" }, { "label": "Luxembourg", "value": "luxembourg" }, { "label": "South Korea", "value": "south-korea" }, { "label": "New Zealand", "value": "new-zealand" }, { "label": "United Arab Emirates", "value": "united-arab-emirates" }, { "label": "Singapore", "value": "singapore" }, { "label": "Other", "value": "other" } ], "propertyMapping": { "united-states": { "technologies": [ "ACH/wire fiat on-ramp" ], "technologyProperties": { "onRampType": "ACH/Fedwire bank transfer", "onRampRegion": "United States", "settlementRail": "ACH / Fedwire" } }, "united-kingdom": { "technologies": [ "UK Faster Payments on-ramp" ], "technologyProperties": { "onRampType": "Faster Payments bank transfer", "onRampRegion": "United Kingdom", "settlementRail": "FPS / BACS" } }, "germany": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "netherlands": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "switzerland": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SIC/SEPA bank transfer", "onRampRegion": "Switzerland/EU", "settlementRail": "SIC / SEPA Credit Transfer" } }, "belgium": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "france": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "sweden": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "norway": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA-adjacent bank transfer", "onRampRegion": "EEA", "settlementRail": "SEPA Credit Transfer" } }, "denmark": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "canada": { "technologies": [ "Canadian EFT on-ramp" ], "technologyProperties": { "onRampType": "Interac/EFT bank transfer", "onRampRegion": "Canada", "settlementRail": "Interac / EFT" } }, "australia": { "technologies": [ "Australian NPP on-ramp" ], "technologyProperties": { "onRampType": "NPP bank transfer", "onRampRegion": "Australia", "settlementRail": "NPP / BECS" } }, "japan": { "technologies": [ "Japanese Zengin on-ramp" ], "technologyProperties": { "onRampType": "Zengin bank transfer", "onRampRegion": "Japan", "settlementRail": "Zengin System" } }, "ireland": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "italy": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "spain": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "austria": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "finland": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "luxembourg": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "south-korea": { "technologies": [ "Korean banking on-ramp" ], "technologyProperties": { "onRampType": "KFTC bank transfer", "onRampRegion": "South Korea", "settlementRail": "KFTC / BOK-Wire" } }, "new-zealand": { "technologies": [ "NZ banking on-ramp" ], "technologyProperties": { "onRampType": "SBI bank transfer", "onRampRegion": "New Zealand", "settlementRail": "SBI / ESAS" } }, "united-arab-emirates": { "technologies": [ "UAE banking on-ramp" ], "technologyProperties": { "onRampType": "UAEFTS bank transfer", "onRampRegion": "United Arab Emirates", "settlementRail": "UAEFTS / IPP" } }, "singapore": { "technologies": [ "Singapore FAST on-ramp" ], "technologyProperties": { "onRampType": "FAST bank transfer", "onRampRegion": "Singapore", "settlementRail": "FAST / MEPS+" } }, "other": { "technologies": [ "Regional fiat on-ramp" ], "technologyProperties": { "onRampType": "Local rail bank transfer", "onRampRegion": "Region-specific", "settlementRail": "Local payment network" } } }, "showIf": { "questionId": "corridor-count", "minValue": "4-5" }, "prefillFrom": null, "briefSection": "Payment rail requirements", "text": "Fifth transfer origination country (if applicable)", "ngoText": "Fifth transfer origination country (if applicable)" }, { "id": "funding-method", "type": "select", "options": [ { "label": "Bank transfer from organisation account", "value": "bank-transfer" }, { "label": "Card payment from organisation", "value": "card-payment" }, { "label": "Direct stablecoin funding (organisation already holds stablecoins)", "value": "direct-stablecoin" }, { "label": "Mixed: bank transfer for most, card for urgent payments", "value": "mixed-methods" } ], "propertyMapping": { "bank-transfer": { "technologies": [ "Bank-integrated fiat on-ramp" ], "technologyProperties": { "fundingSource": "Organisation bank account", "onRampSpeed": "1-2 business days (SEPA/ACH) or same-day (Faster Payments/wire)", "kybRequired": "Yes \u2014 organisation KYB verification" } }, "card-payment": { "technologies": [ "Card payment on-ramp" ], "technologyProperties": { "fundingSource": "Organisation payment card", "onRampSpeed": "Near-instant", "kybRequired": "Yes \u2014 card verification and organisation KYB" } }, "direct-stablecoin": { "technologies": [ "Direct stablecoin treasury funding" ], "technologyProperties": { "fundingSource": "Existing stablecoin holdings", "onRampSpeed": "Immediate (no fiat conversion needed)", "kybRequired": "Wallet verification only" } }, "mixed-methods": { "technologies": [ "Multi-method fiat on-ramp", "Card payment on-ramp" ], "technologyProperties": { "fundingSource": "Bank transfer (primary) + card (urgent)", "onRampSpeed": "Varies by method", "kybRequired": "Yes \u2014 full organisation KYB" } } }, "prefillFrom": null, "briefSection": "Payment rail requirements", "text": "How does your organisation currently fund international transfers or payments?", "ngoText": "How does your organisation currently fund international transfers or payments?" }, { "id": "emergency-response-time", "type": "select", "options": [ { "label": "Within minutes", "value": "minutes" }, { "label": "Within hours (same day)", "value": "hours" }, { "label": "Within 24 hours", "value": "24h" }, { "label": "Within 48-72 hours", "value": "72h" } ], "propertyMapping": { "minutes": { "technologies": [ "Layer 1 payment rail", "Pre-funded liquidity pool", "Pre-registered beneficiary wallets" ], "technologyProperties": { "settlementFinality": "Under 5 seconds", "liquidityModel": "Pre-positioned funds in stablecoin", "beneficiaryPreregistration": "Required" } }, "hours": { "technologies": [ "Layer 1 payment rail", "Rapid on-ramp", "Batch disbursement engine" ], "technologyProperties": { "settlementFinality": "Under 1 hour", "liquidityModel": "Rapid conversion pipeline", "beneficiaryPreregistration": "Recommended" } }, "24h": { "technologies": [ "Layer 1 payment rail", "Standard on-ramp" ], "technologyProperties": { "settlementFinality": "Under 24 hours", "liquidityModel": "Standard conversion", "beneficiaryPreregistration": "Optional" } }, "72h": { "technologies": [ "Layer 1 payment rail" ], "technologyProperties": { "settlementFinality": "Standard", "liquidityModel": "Standard", "beneficiaryPreregistration": "Optional" } } }, "prefillFrom": null, "briefSection": "Payment rail requirements", "text": "In an emergency, how quickly do you need to get funds to beneficiaries from the moment a decision is made?", "ngoText": "In an emergency, how quickly do you need to get funds to beneficiaries from the moment a decision is made?" }, { "id": "emergency-scale", "type": "select", "options": [ { "label": "Under 500 beneficiaries", "value": "small" }, { "label": "500\u20135,000 beneficiaries", "value": "medium" }, { "label": "5,000\u201350,000 beneficiaries", "value": "large" }, { "label": "Over 50,000 beneficiaries", "value": "massive" } ], "propertyMapping": { "small": { "technologies": [ "Batch disbursement engine" ], "technologyProperties": { "throughputRequirement": "Standard", "concurrentDisbursements": "500+" } }, "medium": { "technologies": [ "Batch disbursement engine", "Queue management" ], "technologyProperties": { "throughputRequirement": "High", "concurrentDisbursements": "5,000+" } }, "large": { "technologies": [ "Enterprise batch engine", "Queue management", "Load balancer" ], "technologyProperties": { "throughputRequirement": "Enterprise-grade", "concurrentDisbursements": "50,000+" } }, "massive": { "technologies": [ "Enterprise batch engine", "Distributed queue", "Auto-scaling infrastructure" ], "technologyProperties": { "throughputRequirement": "Mass-disbursement grade", "concurrentDisbursements": "100,000+" } } }, "prefillFrom": null, "briefSection": "Payment rail requirements", "text": "In a typical emergency response, how many beneficiaries need to receive payments?", "ngoText": "In a typical emergency response, how many beneficiaries need to receive payments?" }, { "id": "emergency-beneficiary-registration", "type": "select", "options": [ { "label": "Pre-registered from existing programme lists", "value": "pre-registered" }, { "label": "Mix: some pre-registered, some registered during response", "value": "mixed" }, { "label": "Mostly registered during the emergency response", "value": "on-the-fly" }, { "label": "Varies by emergency type", "value": "varies" } ], "propertyMapping": { "pre-registered": { "technologies": [ "Beneficiary registry", "Pre-provisioned wallets" ], "technologyProperties": { "registrationModel": "Pre-enrolled beneficiary database", "walletProvisioning": "Pre-created dormant wallets" } }, "mixed": { "technologies": [ "Beneficiary registry", "Rapid enrolment module" ], "technologyProperties": { "registrationModel": "Pre-enrolled + rapid field enrolment", "walletProvisioning": "Pre-created + instant provisioning" } }, "on-the-fly": { "technologies": [ "Rapid field enrolment", "Biometric registration", "Instant wallet provisioning" ], "technologyProperties": { "registrationModel": "Field-based rapid enrolment", "walletProvisioning": "Instant wallet creation" } }, "varies": { "technologies": [ "Flexible enrolment system", "Rapid field enrolment" ], "technologyProperties": { "registrationModel": "Dual-mode (pre-enrolled + rapid)", "walletProvisioning": "Flexible" } } }, "prefillFrom": null, "briefSection": "End-user interface", "text": "Are beneficiaries typically pre-registered before an emergency, or do you register on-the-fly?", "ngoText": "Are beneficiaries typically pre-registered before an emergency, or do you register on-the-fly?" }, { "id": "emergency-conditions", "type": "select", "options": [ { "label": "Unconditional: immediate cash transfer", "value": "unconditional" }, { "label": "Triggered by verified event (flood, earthquake, etc.)", "value": "event-triggered" }, { "label": "Conditional on beneficiary being in affected area", "value": "location-conditional" }, { "label": "Multi-tranche: immediate + follow-up conditional payments", "value": "multi-tranche" } ], "propertyMapping": { "unconditional": { "technologies": [], "technologyProperties": { "conditionality": "None \u2014 immediate disbursement", "triggerMechanism": "Manual authorisation" } }, "event-triggered": { "technologies": [ "Automated automation", "External data oracle (weather, seismic)" ], "technologyProperties": { "conditionality": "Event-triggered automatic disbursement", "triggerMechanism": "Oracle data feed \u2192 Automated" } }, "location-conditional": { "technologies": [ "Geolocation verification", "Automated conditional release" ], "technologyProperties": { "conditionality": "Location-verified disbursement", "triggerMechanism": "GPS/cell tower verification" } }, "multi-tranche": { "technologies": [ "Automated phased release", "Condition verification oracle" ], "technologyProperties": { "conditionality": "Phased \u2014 immediate + conditional follow-up", "triggerMechanism": "Automatic first tranche, verified subsequent" } } }, "prefillFrom": null, "briefSection": "Payment logic", "text": "Are emergency payments unconditional or tied to conditions?", "ngoText": "Are emergency payments unconditional or tied to conditions?" }, { "id": "emergency-connectivity", "type": "select", "options": [ { "label": "Urban: reliable mobile data", "value": "urban" }, { "label": "Semi-urban: intermittent connectivity", "value": "semi-urban" }, { "label": "Rural: very limited, 2G at best", "value": "rural" }, { "label": "Disaster-affected: infrastructure may be down", "value": "disaster-affected" } ], "propertyMapping": { "urban": { "technologies": [ "Mobile wallet application" ], "technologyProperties": { "connectivityRequirement": "Online-first", "offlineCapability": "Fallback only" } }, "semi-urban": { "technologies": [ "Offline-capable wallet", "Store-and-forward sync" ], "technologyProperties": { "connectivityRequirement": "Offline-first with sync", "offlineCapability": "Required \u2014 queue transactions locally" } }, "rural": { "technologies": [ "USSD/SMS wallet", "Offline transaction capability" ], "technologyProperties": { "connectivityRequirement": "Zero-data capable", "offlineCapability": "Critical \u2014 USSD/SMS primary" } }, "disaster-affected": { "technologies": [ "Fully offline wallet", "Bluetooth/NFC peer transfer", "Satellite uplink option" ], "technologyProperties": { "connectivityRequirement": "Fully offline capable", "offlineCapability": "Critical \u2014 must operate with zero connectivity" } } }, "prefillFrom": null, "briefSection": "Infrastructure requirements", "text": "What connectivity can you expect in your typical emergency response areas?", "ngoText": "What connectivity can you expect in your typical emergency response areas?" }, { "id": "emergency-approval", "type": "select", "options": [ { "label": "Pre-authorised: funds released automatically on trigger", "value": "pre-authorised" }, { "label": "Single emergency authoriser", "value": "single" }, { "label": "Rapid dual-authorisation (2 signers)", "value": "dual-rapid" }, { "label": "Standard multi-level approval even in emergencies", "value": "standard" } ], "propertyMapping": { "pre-authorised": { "technologies": [ "Automated pre-authorisation", "Oracle trigger verification" ], "technologyProperties": { "approvalMechanism": "Pre-authorised automatic release", "signingThreshold": "0-of-N (automated)" } }, "single": { "technologies": [ "Single-signature emergency wallet" ], "technologyProperties": { "approvalMechanism": "Single emergency key", "signingThreshold": "1-of-1" } }, "dual-rapid": { "technologies": [ "Multi-signature wallet", "Mobile signing capability" ], "technologyProperties": { "approvalMechanism": "Rapid dual-sign (mobile capable)", "signingThreshold": "2-of-3" } }, "standard": { "technologies": [ "Multi-signature wallet", "Approval workflow engine" ], "technologyProperties": { "approvalMechanism": "Standard multi-level", "signingThreshold": "M-of-N per policy" } } }, "prefillFrom": null, "briefSection": "Governance and controls", "text": "What approval process is needed to trigger emergency disbursements?", "ngoText": "What approval process is needed to trigger emergency disbursements?" }, { "id": "emergency-device-beneficiary", "type": "select", "options": [ { "label": "Smartphones", "value": "smartphone" }, { "label": "Feature phones (SMS/USSD)", "value": "feature-phone" }, { "label": "No devices, need agent/kiosk distribution", "value": "no-device" }, { "label": "Devices may be lost/destroyed in disaster", "value": "devices-lost" } ], "propertyMapping": { "smartphone": { "technologies": [ "Mobile wallet application" ], "technologyProperties": { "interface": "Mobile app", "authenticationMethod": "PIN + biometric" } }, "feature-phone": { "technologies": [ "USSD/SMS-based wallet" ], "technologyProperties": { "interface": "USSD menu", "authenticationMethod": "PIN-based" } }, "no-device": { "technologies": [ "Agent-assisted distribution", "Biometric authentication terminal", "QR/token voucher system" ], "technologyProperties": { "interface": "Agent kiosk with biometric", "authenticationMethod": "Biometric or token" } }, "devices-lost": { "technologies": [ "Biometric authentication terminal", "QR/token voucher system", "Agent network" ], "technologyProperties": { "interface": "Device-independent (biometric/token/voucher)", "authenticationMethod": "Biometric preferred \u2014 no device dependency" } } }, "prefillFrom": null, "briefSection": "End-user interface", "text": "What devices do beneficiaries in emergency contexts typically have?", "ngoText": "What devices do beneficiaries in emergency contexts typically have?" }, { "id": "emergency-amount", "type": "select", "options": [ { "label": "Under $25", "value": "micro" }, { "label": "$25\u2013$100", "value": "small" }, { "label": "$100\u2013$500", "value": "medium" }, { "label": "Over $500", "value": "large" }, { "label": "Varies by emergency and programme", "value": "variable" } ], "propertyMapping": { "micro": { "technologies": [ "Layer 1 payment rail" ], "technologyProperties": { "maxTransactionFee": "Sub-$0.01", "feeModel": "Must be negligible relative to amount" } }, "small": { "technologies": [ "Layer 1 payment rail" ], "technologyProperties": { "maxTransactionFee": "Sub-$0.05", "feeModel": "Fixed micro-fee" } }, "medium": { "technologies": [ "Layer 1 payment rail" ], "technologyProperties": { "maxTransactionFee": "Sub-$0.10", "feeModel": "Fixed low fee" } }, "large": { "technologies": [ "Layer 1 payment rail" ], "technologyProperties": { "maxTransactionFee": "Sub-$0.50", "feeModel": "Fixed fee" } }, "variable": { "technologies": [ "Layer 1 payment rail" ], "technologyProperties": { "maxTransactionFee": "Sub-$0.05", "feeModel": "Fixed fee for predictability" } } }, "prefillFrom": null, "briefSection": "Payment rail requirements", "text": "What is the typical emergency payment amount per beneficiary?", "ngoText": "What is the typical emergency payment amount per beneficiary?" }, { "id": "sq-UC-A-005-001", "type": "single-select", "options": [ { "value": "mobile-money-backup", "label": "Mobile money network backup" }, { "value": "cash-via-agent", "label": "Cash delivery via trusted agent" }, { "value": "pre-loaded-cards", "label": "Pre-loaded card activation" }, { "value": "voucher-system", "label": "Physical voucher system" }, { "value": "peer-relay", "label": "direct relay network" } ], "propertyMapping": { "mobile-money-backup": { "technologies": [ "mobile-money-integration", "fallback-routing" ], "technologyProperties": {} }, "cash-via-agent": { "technologies": [ "agent-network", "physical-cash-management" ], "technologyProperties": {} }, "pre-loaded-cards": { "technologies": [ "prepaid-card-system", "card-activation-network" ], "technologyProperties": {} }, "voucher-system": { "technologies": [ "voucher-printing", "voucher-redemption-system" ], "technologyProperties": {} }, "peer-relay": { "technologies": [ "peer-network", "relay-protocol" ], "technologyProperties": {} } }, "briefSection": "operations", "text": "What fallback disbursement approach do you currently use if primary channels fail during an emergency?", "ngoText": "What fallback disbursement approach do you currently use if primary channels fail during an emergency?" }, { "id": "offramp-delivery", "type": "select", "options": [ { "label": "Mobile money", "value": "mobile-money" }, { "label": "Bank transfer to beneficiary/recipient account", "value": "bank-transfer" }, { "label": "Cash via agent network", "value": "agent-cash" }, { "label": "Mixed: depends on recipient location and access", "value": "mixed" } ], "propertyMapping": { "mobile-money": { "technologies": [ "Mobile money off-ramp integration", "MNO API gateway" ], "technologyProperties": { "lastMileChannel": "MNO API integration", "cashOutMethod": "Mobile money wallet top-up" } }, "bank-transfer": { "technologies": [ "Bank-integrated off-ramp", "Local bank API integration" ], "technologyProperties": { "lastMileChannel": "Bank transfer", "cashOutMethod": "Direct bank deposit" } }, "agent-cash": { "technologies": [ "Agent network off-ramp", "Agent cash-out network" ], "technologyProperties": { "lastMileChannel": "Agent network", "cashOutMethod": "Cash via registered agent" } }, "mixed": { "technologies": [ "Multi-channel off-ramp gateway", "Mobile money off-ramp integration", "Agent cash-out network" ], "technologyProperties": { "lastMileChannel": "Mobile money + agent + bank", "cashOutMethod": "Recipient choice" } } }, "prefillFrom": null, "briefSection": "Last-mile delivery", "text": "How will recipients receive funds at the last mile?", "ngoText": "How will recipients receive funds at the last mile?" }, { "id": "beneficiary-choice", "label": "How will beneficiaries exercise choice in how they receive and use this service?", "type": "select", "briefSection": "End-user interface", "options": [ { "label": "Beneficiaries choose between delivery methods (cash, voucher, mobile money, direct)", "value": "delivery-choice" }, { "label": "Beneficiaries choose preferred merchants or service points", "value": "merchant-choice" }, { "label": "Beneficiaries control their own data sharing preferences", "value": "data-choice" }, { "label": "Multiple choice dimensions (delivery + merchant + data)", "value": "full-choice" }, { "label": "Limited choice: programme constraints determine delivery", "value": "limited" } ], "propertyMapping": { "delivery-choice": { "technologies": [], "technologyProperties": { "beneficiaryChoice": "Delivery method choice", "dignityDesign": "Beneficiaries select preferred receipt method" } }, "merchant-choice": { "technologies": [], "technologyProperties": { "beneficiaryChoice": "Merchant/service point choice", "dignityDesign": "Beneficiaries select where to redeem" } }, "data-choice": { "technologies": [], "technologyProperties": { "beneficiaryChoice": "Data sharing choice", "dignityDesign": "Beneficiaries control personal data sharing" } }, "full-choice": { "technologies": [], "technologyProperties": { "beneficiaryChoice": "Multi-dimensional choice", "dignityDesign": "Full beneficiary agency across delivery, merchant, and data" } }, "limited": { "technologies": [], "technologyProperties": { "beneficiaryChoice": "Limited by programme design", "dignityDesign": "Programme constraints; beneficiary informed of reasons" } } }, "text": "How will beneficiaries exercise choice in how they receive and use this service?" } ], "complexityFactors": { "relationships": 2, "operationalChange": 3, "dataCompliance": 3 }, "securityTier": "B", "suggestedCriteria": [ { "id": "SC-ACTIVATION-SPEED", "name": "Activation & Deployment Speed", "description": "This measures how quickly the provider can go from zero to disbursing funds in a new emergency context. In disaster response, the window for cash distribution may be hours, not weeks.", "weight": 0.3, "ratingGuide": { "5": "Pre-positioned in key crisis regions. Can begin disbursements within 24 hours of activation. Pre-registered agent networks. Emergency protocols documented.", "4": "Can deploy within 48-72 hours. Some pre-positioning. Rapid setup procedures available.", "3": "1-2 week deployment timeline. Requires on-ground setup. Standard onboarding.", "2": "2-4 week deployment. Full onboarding required. No emergency acceleration.", "1": "Months to deploy. No rapid activation capability. Standard commercial timelines." } }, { "id": "SC-OFFLINE-PAY", "name": "Offline & Low-Connectivity Payment Capability", "description": "Payments can be processed when internet connectivity is unavailable or unreliable. Disaster zones frequently lose telecommunications infrastructure.", "weight": 0.25, "ratingGuide": { "5": "Fully offline-capable payments via USSD, NFC, or stored-value. Automatic sync when connectivity returns. No data loss.", "4": "USSD-based payments work without internet. Some features require connectivity for reconciliation.", "3": "SMS-based payment confirmation. Core transactions work on 2G. Dashboard requires internet.", "2": "Requires intermittent connectivity. Queue-and-sync model with potential delays.", "1": "Requires stable internet connection. No offline capability." } }, { "id": "SC-SCALE-BURST", "name": "Burst Capacity & Scale", "description": "The provider can handle sudden large-volume disbursements. Emergency responses may require paying thousands of beneficiaries within days.", "weight": 0.2, "ratingGuide": { "5": "Proven at 100,000+ disbursements in a single event. Auto-scaling infrastructure. No throughput degradation under load.", "4": "Handles 10,000-100,000 disbursements per event. Good scaling with minor delays at peak.", "3": "Handles 1,000-10,000 disbursements. May require staged rollout for larger numbers.", "2": "Under 1,000 disbursements per event. Significant delays at scale.", "1": "Not designed for bulk disbursement. Individual payment processing only." } }, { "id": "SC-BENEFICIARY-ID", "name": "Flexible Beneficiary Identification", "description": "The provider can disburse to beneficiaries who lack formal ID documents. In emergencies, displaced populations may have lost documentation.", "weight": 0.15, "ratingGuide": { "5": "Biometric registration (fingerprint/iris). Alternative ID acceptance (community vouching, agency cards). No government ID required. UNHCR/WFP ID integration.", "4": "Biometric option available. Accepts humanitarian agency-issued IDs. Flexible KYC for emergency context.", "3": "Accepts copies or photos of ID. Phone number registration. Some KYC flexibility.", "2": "Requires government-issued ID. Limited flexibility for displaced populations.", "1": "Strict KYC requirements. No humanitarian context adaptations. Government ID mandatory." } }, { "id": "SC-COORDINATION", "name": "Humanitarian Coordination Compatibility", "description": "The provider can integrate with humanitarian coordination systems. Emergency cash responses involve multiple agencies. Deduplication, reporting to clusters, and donor coordination are essential.", "weight": 0.1, "ratingGuide": { "5": "Integration with the beneficiary registration and field data collection platforms agencies already use. Deduplication across agencies. Cash Working Group reporting formats.", "4": "Integration with one major platform. Basic deduplication. Standard reporting exports.", "3": "API available for integration. Manual deduplication possible. Custom report generation.", "2": "CSV export only. No coordination platform integration. Manual deduplication.", "1": "Closed system. No integration, export, or coordination capability." } } ], "procurement": { "marketMaturity": "emerging", "primaryMode": "integrator-led", "alternativeModes": [ "rfq" ], "reasoning": "Rapid disbursement needs combine known products with integration; integrator absorbs deploy speed risk.", "exampleProductCategories": [ "rapid-disbursement-platform", "humanitarian-cash-rails" ], "partnerChannels": [], "lastReviewed": "2026-05-01" } }, { "id": "UC-A-006", "name": "Multi-currency treasury management", "category": "A", "subcategory": "Treasury Operations", "description": "Hold and move funds in several currencies with less manual reconciling, and keep a clear view of your position in each currency.", "bCriteria": [ "B1", "B3" ], "requiredComponents": [ { "component": "payment-rails", "description": "Multi-currency settlement" }, { "component": "stablecoin", "description": "Multiple stablecoins for different currencies" }, { "component": "currency-hedging", "description": "Currency conversion and hedging tools" }, { "component": "accounting-integration", "description": "Real-time accounting reconciliation" }, { "component": "reporting-module", "description": "Multi-currency financial reporting" } ], "conditionalComponents": [ { "component": "smart-contracts", "condition": "If automated currency conversion rules" } ], "crossCategoryDependencies": [], "p2TriggerConditions": { "description": "Activated when P2 shows multiple countries + currency volatility concerns + complex treasury", "rangeSignals": [ "countries >= 4", "currenciesUsed >= 3", "treasuryComplexity >= high" ] }, "contextFieldsTemplate": [ { "field": "currencies", "source": "P0 countries", "description": "Currencies in use" }, { "field": "treasurySize", "source": "P2 annual budget", "description": "Total funds managed" }, { "field": "volatilityExposure", "source": "P2 currency risk concerns", "description": "Currency risk exposure" }, { "field": "reportingRequirements", "source": "P0 donor requirements", "description": "Financial reporting needs" } ], "implementationComplexity": "medium-high", "examples": { "note": "Large international NGO treasury operations", "references": [ { "name": "Stellar / IBM World Wire", "url": "https://www.ibm.com/think/topics/cross-border-payments-blockchain", "solved": "Handled cross-border settlement and FX in multiple currencies in near real time" }, { "name": "AZA Finance (BitPesa)", "url": "https://azafinance.com/", "solved": "Reduced cost and time for cross-border business payments across Africa" } ] }, "solutionQuestions": [ { "id": "corridor-count", "type": "select", "options": [ { "label": "Single country", "value": "single" }, { "label": "2\u20133 countries", "value": "2-3" }, { "label": "4\u20135 countries", "value": "4-5" }, { "label": "More than 5 countries", "value": "5-plus" } ], "propertyMapping": { "single": { "technologies": [ "Single-corridor fiat on-ramp" ], "technologyProperties": { "corridorComplexity": "Single origination country", "multiRailNeeded": "No" } }, "2-3": { "technologies": [ "Multi-corridor fiat on-ramp gateway" ], "technologyProperties": { "corridorComplexity": "2\u20133 origination countries", "multiRailNeeded": "Yes \u2014 2-3 payment rails" } }, "4-5": { "technologies": [ "Multi-corridor fiat on-ramp gateway" ], "technologyProperties": { "corridorComplexity": "4\u20135 origination countries", "multiRailNeeded": "Yes \u2014 4-5 payment rails" } }, "5-plus": { "technologies": [ "Enterprise multi-corridor on-ramp gateway" ], "technologyProperties": { "corridorComplexity": "5+ origination countries", "multiRailNeeded": "Yes \u2014 enterprise-grade multi-rail" } } }, "prefillFrom": null, "briefSection": "Payment rail requirements", "text": "How many countries does your organisation send transfer funds from?", "ngoText": "How many countries does your organisation send transfer funds from?" }, { "id": "origination-country-1", "type": "select", "options": [ { "label": "United States", "value": "united-states" }, { "label": "United Kingdom", "value": "united-kingdom" }, { "label": "Germany", "value": "germany" }, { "label": "Netherlands", "value": "netherlands" }, { "label": "Switzerland", "value": "switzerland" }, { "label": "Belgium", "value": "belgium" }, { "label": "France", "value": "france" }, { "label": "Sweden", "value": "sweden" }, { "label": "Norway", "value": "norway" }, { "label": "Denmark", "value": "denmark" }, { "label": "Canada", "value": "canada" }, { "label": "Australia", "value": "australia" }, { "label": "Japan", "value": "japan" }, { "label": "Ireland", "value": "ireland" }, { "label": "Italy", "value": "italy" }, { "label": "Spain", "value": "spain" }, { "label": "Austria", "value": "austria" }, { "label": "Finland", "value": "finland" }, { "label": "Luxembourg", "value": "luxembourg" }, { "label": "South Korea", "value": "south-korea" }, { "label": "New Zealand", "value": "new-zealand" }, { "label": "United Arab Emirates", "value": "united-arab-emirates" }, { "label": "Singapore", "value": "singapore" }, { "label": "Other", "value": "other" } ], "propertyMapping": { "united-states": { "technologies": [ "ACH/wire fiat on-ramp" ], "technologyProperties": { "onRampType": "ACH/Fedwire bank transfer", "onRampRegion": "United States", "settlementRail": "ACH / Fedwire" } }, "united-kingdom": { "technologies": [ "UK Faster Payments on-ramp" ], "technologyProperties": { "onRampType": "Faster Payments bank transfer", "onRampRegion": "United Kingdom", "settlementRail": "FPS / BACS" } }, "germany": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "netherlands": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "switzerland": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SIC/SEPA bank transfer", "onRampRegion": "Switzerland/EU", "settlementRail": "SIC / SEPA Credit Transfer" } }, "belgium": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "france": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "sweden": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "norway": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA-adjacent bank transfer", "onRampRegion": "EEA", "settlementRail": "SEPA Credit Transfer" } }, "denmark": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "canada": { "technologies": [ "Canadian EFT on-ramp" ], "technologyProperties": { "onRampType": "Interac/EFT bank transfer", "onRampRegion": "Canada", "settlementRail": "Interac / EFT" } }, "australia": { "technologies": [ "Australian NPP on-ramp" ], "technologyProperties": { "onRampType": "NPP bank transfer", "onRampRegion": "Australia", "settlementRail": "NPP / BECS" } }, "japan": { "technologies": [ "Japanese Zengin on-ramp" ], "technologyProperties": { "onRampType": "Zengin bank transfer", "onRampRegion": "Japan", "settlementRail": "Zengin System" } }, "ireland": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "italy": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "spain": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "austria": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "finland": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "luxembourg": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "south-korea": { "technologies": [ "Korean banking on-ramp" ], "technologyProperties": { "onRampType": "KFTC bank transfer", "onRampRegion": "South Korea", "settlementRail": "KFTC / BOK-Wire" } }, "new-zealand": { "technologies": [ "NZ banking on-ramp" ], "technologyProperties": { "onRampType": "SBI bank transfer", "onRampRegion": "New Zealand", "settlementRail": "SBI / ESAS" } }, "united-arab-emirates": { "technologies": [ "UAE banking on-ramp" ], "technologyProperties": { "onRampType": "UAEFTS bank transfer", "onRampRegion": "United Arab Emirates", "settlementRail": "UAEFTS / IPP" } }, "singapore": { "technologies": [ "Singapore FAST on-ramp" ], "technologyProperties": { "onRampType": "FAST bank transfer", "onRampRegion": "Singapore", "settlementRail": "FAST / MEPS+" } }, "other": { "technologies": [ "Regional fiat on-ramp" ], "technologyProperties": { "onRampType": "Local rail bank transfer", "onRampRegion": "Region-specific", "settlementRail": "Local payment network" } } }, "showIf": { "questionId": "corridor-count", "minValue": "single" }, "prefillFrom": null, "briefSection": "Payment rail requirements", "text": "Which country do you most frequently initiate transfers from?", "ngoText": "Which country do you most frequently initiate transfers from?" }, { "id": "origination-country-2", "type": "select", "options": [ { "label": "United States", "value": "united-states" }, { "label": "United Kingdom", "value": "united-kingdom" }, { "label": "Germany", "value": "germany" }, { "label": "Netherlands", "value": "netherlands" }, { "label": "Switzerland", "value": "switzerland" }, { "label": "Belgium", "value": "belgium" }, { "label": "France", "value": "france" }, { "label": "Sweden", "value": "sweden" }, { "label": "Norway", "value": "norway" }, { "label": "Denmark", "value": "denmark" }, { "label": "Canada", "value": "canada" }, { "label": "Australia", "value": "australia" }, { "label": "Japan", "value": "japan" }, { "label": "Ireland", "value": "ireland" }, { "label": "Italy", "value": "italy" }, { "label": "Spain", "value": "spain" }, { "label": "Austria", "value": "austria" }, { "label": "Finland", "value": "finland" }, { "label": "Luxembourg", "value": "luxembourg" }, { "label": "South Korea", "value": "south-korea" }, { "label": "New Zealand", "value": "new-zealand" }, { "label": "United Arab Emirates", "value": "united-arab-emirates" }, { "label": "Singapore", "value": "singapore" }, { "label": "Other", "value": "other" } ], "propertyMapping": { "united-states": { "technologies": [ "ACH/wire fiat on-ramp" ], "technologyProperties": { "onRampType": "ACH/Fedwire bank transfer", "onRampRegion": "United States", "settlementRail": "ACH / Fedwire" } }, "united-kingdom": { "technologies": [ "UK Faster Payments on-ramp" ], "technologyProperties": { "onRampType": "Faster Payments bank transfer", "onRampRegion": "United Kingdom", "settlementRail": "FPS / BACS" } }, "germany": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "netherlands": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "switzerland": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SIC/SEPA bank transfer", "onRampRegion": "Switzerland/EU", "settlementRail": "SIC / SEPA Credit Transfer" } }, "belgium": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "france": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "sweden": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "norway": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA-adjacent bank transfer", "onRampRegion": "EEA", "settlementRail": "SEPA Credit Transfer" } }, "denmark": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "canada": { "technologies": [ "Canadian EFT on-ramp" ], "technologyProperties": { "onRampType": "Interac/EFT bank transfer", "onRampRegion": "Canada", "settlementRail": "Interac / EFT" } }, "australia": { "technologies": [ "Australian NPP on-ramp" ], "technologyProperties": { "onRampType": "NPP bank transfer", "onRampRegion": "Australia", "settlementRail": "NPP / BECS" } }, "japan": { "technologies": [ "Japanese Zengin on-ramp" ], "technologyProperties": { "onRampType": "Zengin bank transfer", "onRampRegion": "Japan", "settlementRail": "Zengin System" } }, "ireland": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "italy": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "spain": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "austria": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "finland": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "luxembourg": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "south-korea": { "technologies": [ "Korean banking on-ramp" ], "technologyProperties": { "onRampType": "KFTC bank transfer", "onRampRegion": "South Korea", "settlementRail": "KFTC / BOK-Wire" } }, "new-zealand": { "technologies": [ "NZ banking on-ramp" ], "technologyProperties": { "onRampType": "SBI bank transfer", "onRampRegion": "New Zealand", "settlementRail": "SBI / ESAS" } }, "united-arab-emirates": { "technologies": [ "UAE banking on-ramp" ], "technologyProperties": { "onRampType": "UAEFTS bank transfer", "onRampRegion": "United Arab Emirates", "settlementRail": "UAEFTS / IPP" } }, "singapore": { "technologies": [ "Singapore FAST on-ramp" ], "technologyProperties": { "onRampType": "FAST bank transfer", "onRampRegion": "Singapore", "settlementRail": "FAST / MEPS+" } }, "other": { "technologies": [ "Regional fiat on-ramp" ], "technologyProperties": { "onRampType": "Local rail bank transfer", "onRampRegion": "Region-specific", "settlementRail": "Local payment network" } } }, "showIf": { "questionId": "corridor-count", "minValue": "2-3" }, "prefillFrom": null, "briefSection": "Payment rail requirements", "text": "Second most common transfer origination country (if applicable)", "ngoText": "Second most common transfer origination country (if applicable)" }, { "id": "origination-country-3", "type": "select", "options": [ { "label": "United States", "value": "united-states" }, { "label": "United Kingdom", "value": "united-kingdom" }, { "label": "Germany", "value": "germany" }, { "label": "Netherlands", "value": "netherlands" }, { "label": "Switzerland", "value": "switzerland" }, { "label": "Belgium", "value": "belgium" }, { "label": "France", "value": "france" }, { "label": "Sweden", "value": "sweden" }, { "label": "Norway", "value": "norway" }, { "label": "Denmark", "value": "denmark" }, { "label": "Canada", "value": "canada" }, { "label": "Australia", "value": "australia" }, { "label": "Japan", "value": "japan" }, { "label": "Ireland", "value": "ireland" }, { "label": "Italy", "value": "italy" }, { "label": "Spain", "value": "spain" }, { "label": "Austria", "value": "austria" }, { "label": "Finland", "value": "finland" }, { "label": "Luxembourg", "value": "luxembourg" }, { "label": "South Korea", "value": "south-korea" }, { "label": "New Zealand", "value": "new-zealand" }, { "label": "United Arab Emirates", "value": "united-arab-emirates" }, { "label": "Singapore", "value": "singapore" }, { "label": "Other", "value": "other" } ], "propertyMapping": { "united-states": { "technologies": [ "ACH/wire fiat on-ramp" ], "technologyProperties": { "onRampType": "ACH/Fedwire bank transfer", "onRampRegion": "United States", "settlementRail": "ACH / Fedwire" } }, "united-kingdom": { "technologies": [ "UK Faster Payments on-ramp" ], "technologyProperties": { "onRampType": "Faster Payments bank transfer", "onRampRegion": "United Kingdom", "settlementRail": "FPS / BACS" } }, "germany": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "netherlands": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "switzerland": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SIC/SEPA bank transfer", "onRampRegion": "Switzerland/EU", "settlementRail": "SIC / SEPA Credit Transfer" } }, "belgium": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "france": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "sweden": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "norway": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA-adjacent bank transfer", "onRampRegion": "EEA", "settlementRail": "SEPA Credit Transfer" } }, "denmark": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "canada": { "technologies": [ "Canadian EFT on-ramp" ], "technologyProperties": { "onRampType": "Interac/EFT bank transfer", "onRampRegion": "Canada", "settlementRail": "Interac / EFT" } }, "australia": { "technologies": [ "Australian NPP on-ramp" ], "technologyProperties": { "onRampType": "NPP bank transfer", "onRampRegion": "Australia", "settlementRail": "NPP / BECS" } }, "japan": { "technologies": [ "Japanese Zengin on-ramp" ], "technologyProperties": { "onRampType": "Zengin bank transfer", "onRampRegion": "Japan", "settlementRail": "Zengin System" } }, "ireland": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "italy": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "spain": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "austria": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "finland": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "luxembourg": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "south-korea": { "technologies": [ "Korean banking on-ramp" ], "technologyProperties": { "onRampType": "KFTC bank transfer", "onRampRegion": "South Korea", "settlementRail": "KFTC / BOK-Wire" } }, "new-zealand": { "technologies": [ "NZ banking on-ramp" ], "technologyProperties": { "onRampType": "SBI bank transfer", "onRampRegion": "New Zealand", "settlementRail": "SBI / ESAS" } }, "united-arab-emirates": { "technologies": [ "UAE banking on-ramp" ], "technologyProperties": { "onRampType": "UAEFTS bank transfer", "onRampRegion": "United Arab Emirates", "settlementRail": "UAEFTS / IPP" } }, "singapore": { "technologies": [ "Singapore FAST on-ramp" ], "technologyProperties": { "onRampType": "FAST bank transfer", "onRampRegion": "Singapore", "settlementRail": "FAST / MEPS+" } }, "other": { "technologies": [ "Regional fiat on-ramp" ], "technologyProperties": { "onRampType": "Local rail bank transfer", "onRampRegion": "Region-specific", "settlementRail": "Local payment network" } } }, "showIf": { "questionId": "corridor-count", "minValue": "2-3" }, "prefillFrom": null, "briefSection": "Payment rail requirements", "text": "Third transfer origination country (if applicable)", "ngoText": "Third transfer origination country (if applicable)" }, { "id": "origination-country-4", "type": "select", "options": [ { "label": "United States", "value": "united-states" }, { "label": "United Kingdom", "value": "united-kingdom" }, { "label": "Germany", "value": "germany" }, { "label": "Netherlands", "value": "netherlands" }, { "label": "Switzerland", "value": "switzerland" }, { "label": "Belgium", "value": "belgium" }, { "label": "France", "value": "france" }, { "label": "Sweden", "value": "sweden" }, { "label": "Norway", "value": "norway" }, { "label": "Denmark", "value": "denmark" }, { "label": "Canada", "value": "canada" }, { "label": "Australia", "value": "australia" }, { "label": "Japan", "value": "japan" }, { "label": "Ireland", "value": "ireland" }, { "label": "Italy", "value": "italy" }, { "label": "Spain", "value": "spain" }, { "label": "Austria", "value": "austria" }, { "label": "Finland", "value": "finland" }, { "label": "Luxembourg", "value": "luxembourg" }, { "label": "South Korea", "value": "south-korea" }, { "label": "New Zealand", "value": "new-zealand" }, { "label": "United Arab Emirates", "value": "united-arab-emirates" }, { "label": "Singapore", "value": "singapore" }, { "label": "Other", "value": "other" } ], "propertyMapping": { "united-states": { "technologies": [ "ACH/wire fiat on-ramp" ], "technologyProperties": { "onRampType": "ACH/Fedwire bank transfer", "onRampRegion": "United States", "settlementRail": "ACH / Fedwire" } }, "united-kingdom": { "technologies": [ "UK Faster Payments on-ramp" ], "technologyProperties": { "onRampType": "Faster Payments bank transfer", "onRampRegion": "United Kingdom", "settlementRail": "FPS / BACS" } }, "germany": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "netherlands": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "switzerland": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SIC/SEPA bank transfer", "onRampRegion": "Switzerland/EU", "settlementRail": "SIC / SEPA Credit Transfer" } }, "belgium": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "france": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "sweden": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "norway": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA-adjacent bank transfer", "onRampRegion": "EEA", "settlementRail": "SEPA Credit Transfer" } }, "denmark": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "canada": { "technologies": [ "Canadian EFT on-ramp" ], "technologyProperties": { "onRampType": "Interac/EFT bank transfer", "onRampRegion": "Canada", "settlementRail": "Interac / EFT" } }, "australia": { "technologies": [ "Australian NPP on-ramp" ], "technologyProperties": { "onRampType": "NPP bank transfer", "onRampRegion": "Australia", "settlementRail": "NPP / BECS" } }, "japan": { "technologies": [ "Japanese Zengin on-ramp" ], "technologyProperties": { "onRampType": "Zengin bank transfer", "onRampRegion": "Japan", "settlementRail": "Zengin System" } }, "ireland": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "italy": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "spain": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "austria": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "finland": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "luxembourg": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "south-korea": { "technologies": [ "Korean banking on-ramp" ], "technologyProperties": { "onRampType": "KFTC bank transfer", "onRampRegion": "South Korea", "settlementRail": "KFTC / BOK-Wire" } }, "new-zealand": { "technologies": [ "NZ banking on-ramp" ], "technologyProperties": { "onRampType": "SBI bank transfer", "onRampRegion": "New Zealand", "settlementRail": "SBI / ESAS" } }, "united-arab-emirates": { "technologies": [ "UAE banking on-ramp" ], "technologyProperties": { "onRampType": "UAEFTS bank transfer", "onRampRegion": "United Arab Emirates", "settlementRail": "UAEFTS / IPP" } }, "singapore": { "technologies": [ "Singapore FAST on-ramp" ], "technologyProperties": { "onRampType": "FAST bank transfer", "onRampRegion": "Singapore", "settlementRail": "FAST / MEPS+" } }, "other": { "technologies": [ "Regional fiat on-ramp" ], "technologyProperties": { "onRampType": "Local rail bank transfer", "onRampRegion": "Region-specific", "settlementRail": "Local payment network" } } }, "showIf": { "questionId": "corridor-count", "minValue": "4-5" }, "prefillFrom": null, "briefSection": "Payment rail requirements", "text": "Fourth transfer origination country (if applicable)", "ngoText": "Fourth transfer origination country (if applicable)" }, { "id": "origination-country-5", "type": "select", "options": [ { "label": "United States", "value": "united-states" }, { "label": "United Kingdom", "value": "united-kingdom" }, { "label": "Germany", "value": "germany" }, { "label": "Netherlands", "value": "netherlands" }, { "label": "Switzerland", "value": "switzerland" }, { "label": "Belgium", "value": "belgium" }, { "label": "France", "value": "france" }, { "label": "Sweden", "value": "sweden" }, { "label": "Norway", "value": "norway" }, { "label": "Denmark", "value": "denmark" }, { "label": "Canada", "value": "canada" }, { "label": "Australia", "value": "australia" }, { "label": "Japan", "value": "japan" }, { "label": "Ireland", "value": "ireland" }, { "label": "Italy", "value": "italy" }, { "label": "Spain", "value": "spain" }, { "label": "Austria", "value": "austria" }, { "label": "Finland", "value": "finland" }, { "label": "Luxembourg", "value": "luxembourg" }, { "label": "South Korea", "value": "south-korea" }, { "label": "New Zealand", "value": "new-zealand" }, { "label": "United Arab Emirates", "value": "united-arab-emirates" }, { "label": "Singapore", "value": "singapore" }, { "label": "Other", "value": "other" } ], "propertyMapping": { "united-states": { "technologies": [ "ACH/wire fiat on-ramp" ], "technologyProperties": { "onRampType": "ACH/Fedwire bank transfer", "onRampRegion": "United States", "settlementRail": "ACH / Fedwire" } }, "united-kingdom": { "technologies": [ "UK Faster Payments on-ramp" ], "technologyProperties": { "onRampType": "Faster Payments bank transfer", "onRampRegion": "United Kingdom", "settlementRail": "FPS / BACS" } }, "germany": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "netherlands": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "switzerland": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SIC/SEPA bank transfer", "onRampRegion": "Switzerland/EU", "settlementRail": "SIC / SEPA Credit Transfer" } }, "belgium": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "france": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "sweden": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "norway": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA-adjacent bank transfer", "onRampRegion": "EEA", "settlementRail": "SEPA Credit Transfer" } }, "denmark": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "canada": { "technologies": [ "Canadian EFT on-ramp" ], "technologyProperties": { "onRampType": "Interac/EFT bank transfer", "onRampRegion": "Canada", "settlementRail": "Interac / EFT" } }, "australia": { "technologies": [ "Australian NPP on-ramp" ], "technologyProperties": { "onRampType": "NPP bank transfer", "onRampRegion": "Australia", "settlementRail": "NPP / BECS" } }, "japan": { "technologies": [ "Japanese Zengin on-ramp" ], "technologyProperties": { "onRampType": "Zengin bank transfer", "onRampRegion": "Japan", "settlementRail": "Zengin System" } }, "ireland": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "italy": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "spain": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "austria": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "finland": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "luxembourg": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "south-korea": { "technologies": [ "Korean banking on-ramp" ], "technologyProperties": { "onRampType": "KFTC bank transfer", "onRampRegion": "South Korea", "settlementRail": "KFTC / BOK-Wire" } }, "new-zealand": { "technologies": [ "NZ banking on-ramp" ], "technologyProperties": { "onRampType": "SBI bank transfer", "onRampRegion": "New Zealand", "settlementRail": "SBI / ESAS" } }, "united-arab-emirates": { "technologies": [ "UAE banking on-ramp" ], "technologyProperties": { "onRampType": "UAEFTS bank transfer", "onRampRegion": "United Arab Emirates", "settlementRail": "UAEFTS / IPP" } }, "singapore": { "technologies": [ "Singapore FAST on-ramp" ], "technologyProperties": { "onRampType": "FAST bank transfer", "onRampRegion": "Singapore", "settlementRail": "FAST / MEPS+" } }, "other": { "technologies": [ "Regional fiat on-ramp" ], "technologyProperties": { "onRampType": "Local rail bank transfer", "onRampRegion": "Region-specific", "settlementRail": "Local payment network" } } }, "showIf": { "questionId": "corridor-count", "minValue": "4-5" }, "prefillFrom": null, "briefSection": "Payment rail requirements", "text": "Fifth transfer origination country (if applicable)", "ngoText": "Fifth transfer origination country (if applicable)" }, { "id": "funding-method", "type": "select", "options": [ { "label": "Bank transfer from organisation account", "value": "bank-transfer" }, { "label": "Card payment from organisation", "value": "card-payment" }, { "label": "Direct stablecoin funding (organisation already holds stablecoins)", "value": "direct-stablecoin" }, { "label": "Mixed: bank transfer for most, card for urgent payments", "value": "mixed-methods" } ], "propertyMapping": { "bank-transfer": { "technologies": [ "Bank-integrated fiat on-ramp" ], "technologyProperties": { "fundingSource": "Organisation bank account", "onRampSpeed": "1-2 business days (SEPA/ACH) or same-day (Faster Payments/wire)", "kybRequired": "Yes \u2014 organisation KYB verification" } }, "card-payment": { "technologies": [ "Card payment on-ramp" ], "technologyProperties": { "fundingSource": "Organisation payment card", "onRampSpeed": "Near-instant", "kybRequired": "Yes \u2014 card verification and organisation KYB" } }, "direct-stablecoin": { "technologies": [ "Direct stablecoin treasury funding" ], "technologyProperties": { "fundingSource": "Existing stablecoin holdings", "onRampSpeed": "Immediate (no fiat conversion needed)", "kybRequired": "Wallet verification only" } }, "mixed-methods": { "technologies": [ "Multi-method fiat on-ramp", "Card payment on-ramp" ], "technologyProperties": { "fundingSource": "Bank transfer (primary) + card (urgent)", "onRampSpeed": "Varies by method", "kybRequired": "Yes \u2014 full organisation KYB" } } }, "prefillFrom": null, "briefSection": "Payment rail requirements", "text": "How does your organisation currently fund international transfers or payments?", "ngoText": "How does your organisation currently fund international transfers or payments?" }, { "id": "fx-exposure", "type": "select", "options": [ { "label": "Minimal: most operations in one currency", "value": "minimal" }, { "label": "Moderate: predictable currency needs", "value": "moderate" }, { "label": "Significant: volatile currencies, large cross-currency flows", "value": "significant" }, { "label": "Critical: operating in hyperinflationary or crisis economies", "value": "critical" } ], "propertyMapping": { "minimal": { "technologies": [ "Basic stablecoin conversion" ], "technologyProperties": { "hedgingCapability": "Not required", "stabilityMechanism": "Single stablecoin denomination" } }, "moderate": { "technologies": [ "Automated FX conversion", "Rate monitoring" ], "technologyProperties": { "hedgingCapability": "Rate alerts and timing optimisation", "stabilityMechanism": "Stablecoin-based with timed conversion" } }, "significant": { "technologies": [ "Automated FX conversion", "Hedging strategy module", "Multi-stablecoin holding" ], "technologyProperties": { "hedgingCapability": "Automated hedging via stablecoin diversification", "stabilityMechanism": "Multi-stablecoin basket or algorithmic hedge" } }, "critical": { "technologies": [ "Stablecoin safe haven", "Rapid conversion engine", "Rate monitoring with alerts" ], "technologyProperties": { "hedgingCapability": "Immediate conversion to stable assets", "stabilityMechanism": "USD/EUR stablecoin as primary store of value" } } }, "prefillFrom": null, "briefSection": "Stablecoin and FX", "text": "How significant is your FX exposure and currency risk?", "ngoText": "How significant is your FX exposure and currency risk?" }, { "id": "treasury-operations", "type": "multiselect", "options": [ { "label": "Currency conversion (buy/sell)", "value": "conversion" }, { "label": "Fund allocation across country programmes", "value": "allocation" }, { "label": "Cash position monitoring across all currencies", "value": "monitoring" }, { "label": "Automated rebalancing between currencies", "value": "rebalancing" }, { "label": "Yield generation on idle funds", "value": "yield" }, { "label": "Donor fund ring-fencing by currency", "value": "ringfencing" } ], "propertyMapping": { "conversion": { "technologies": [ "On-chain swap/DEX integration" ], "technologyProperties": { "treasuryFunction": "Currency swap", "automationLevel": "On-demand or scheduled" } }, "allocation": { "technologies": [ "Multi-wallet fund routing", "Smart contract allocation rules" ], "technologyProperties": { "treasuryFunction": "Programmatic allocation", "automationLevel": "Rule-based distribution" } }, "monitoring": { "technologies": [ "Real-time treasury dashboard", "Multi-chain balance aggregator" ], "technologyProperties": { "treasuryFunction": "Cash position monitoring", "automationLevel": "Real-time automated" } }, "rebalancing": { "technologies": [ "Automated rebalancing engine", "Smart contract triggers" ], "technologyProperties": { "treasuryFunction": "Automated rebalancing", "automationLevel": "Threshold-triggered" } }, "yield": { "technologies": [ "DeFi yield integration", "Lending protocol connection" ], "technologyProperties": { "treasuryFunction": "Yield on idle funds", "automationLevel": "Risk-managed automated" } }, "ringfencing": { "technologies": [ "Multi-wallet segregation", "Smart contract fund tagging" ], "technologyProperties": { "treasuryFunction": "Donor-specific fund isolation", "automationLevel": "Automated tagging and reporting" } } }, "prefillFrom": null, "briefSection": "Payment operations", "text": "What treasury operations do you need to perform regularly?", "ngoText": "What treasury operations do you need to perform regularly?" }, { "id": "treasury-approval", "type": "select", "options": [ { "label": "Finance team operates autonomously within policy", "value": "autonomous" }, { "label": "Dual authorisation for all treasury actions", "value": "dual" }, { "label": "Threshold-based: auto below limit, approval above", "value": "threshold" }, { "label": "Board/senior approval for all significant actions", "value": "board" } ], "propertyMapping": { "autonomous": { "technologies": [ "Policy-constrained treasury wallet" ], "technologyProperties": { "governanceModel": "Policy-based automated limits", "approvalMechanism": "Within-policy auto-execute" } }, "dual": { "technologies": [ "Multi-signature treasury wallet" ], "technologyProperties": { "governanceModel": "Dual-authorisation", "approvalMechanism": "2-of-N multi-sig" } }, "threshold": { "technologies": [ "Automated policy engine", "Multi-signature wallet" ], "technologyProperties": { "governanceModel": "Threshold-based escalation", "approvalMechanism": "Auto below threshold, multi-sig above" } }, "board": { "technologies": [ "Multi-signature wallet", "Approval queue with notifications" ], "technologyProperties": { "governanceModel": "Board-level approval", "approvalMechanism": "Senior multi-sig for all actions" } } }, "prefillFrom": null, "briefSection": "Governance and controls", "text": "What governance is required for treasury operations (conversions, allocations)?", "ngoText": "What governance is required for treasury operations (conversions, allocations)?" }, { "id": "treasury-reporting", "type": "multiselect", "options": [ { "label": "Real-time multi-currency dashboard", "value": "realtime-dashboard" }, { "label": "Daily/weekly treasury position reports", "value": "periodic-reports" }, { "label": "FX gain/loss tracking", "value": "fx-tracking" }, { "label": "Cash flow forecasting", "value": "forecasting" }, { "label": "Donor fund utilisation by currency", "value": "donor-utilisation" }, { "label": "Audit trail of all treasury actions", "value": "audit-trail" } ], "propertyMapping": { "realtime-dashboard": { "technologies": [ "Real-time treasury dashboard" ], "technologyProperties": { "reportingCapability": "Live multi-currency view", "updateFrequency": "Real-time" } }, "periodic-reports": { "technologies": [ "Automated report generation" ], "technologyProperties": { "reportingCapability": "Scheduled treasury reports", "updateFrequency": "Daily/weekly/monthly" } }, "fx-tracking": { "technologies": [ "FX gain/loss calculation engine" ], "technologyProperties": { "reportingCapability": "Realised and unrealised FX tracking", "updateFrequency": "Per-transaction" } }, "forecasting": { "technologies": [ "Cash flow forecasting module" ], "technologyProperties": { "reportingCapability": "Forward-looking cash projection", "updateFrequency": "Rolling forecast" } }, "donor-utilisation": { "technologies": [ "Donor fund tracking module" ], "technologyProperties": { "reportingCapability": "Per-donor per-currency utilisation", "updateFrequency": "Real-time with periodic summaries" } }, "audit-trail": { "technologies": [ "Immutable treasury audit log" ], "technologyProperties": { "reportingCapability": "Complete action audit trail", "updateFrequency": "Per-action" } } }, "prefillFrom": null, "briefSection": "Reporting and audit", "text": "What treasury reporting is needed?", "ngoText": "What treasury reporting is needed?" }, { "id": "on-off-ramp-needs", "type": "multiselect", "options": [ { "label": "HQ country (on-ramp: fiat \u2192 stablecoin)", "value": "hq-onramp" }, { "label": "Field countries (off-ramp: stablecoin \u2192 local fiat)", "value": "field-offramp" }, { "label": "Both directions in multiple countries", "value": "bidirectional" }, { "label": "Regional hubs only", "value": "regional-hubs" } ], "propertyMapping": { "hq-onramp": { "technologies": [ "Fiat on-ramp (HQ jurisdiction)" ], "technologyProperties": { "onRampLocations": "HQ country", "offRampLocations": "N/A for this use case", "rampType": "Bank wire to stablecoin" } }, "field-offramp": { "technologies": [ "Local currency off-ramp (multi-country)" ], "technologyProperties": { "onRampLocations": "N/A for this use case", "offRampLocations": "Field countries", "rampType": "Stablecoin to local bank/mobile money" } }, "bidirectional": { "technologies": [ "Multi-country on/off-ramp network" ], "technologyProperties": { "onRampLocations": "Multiple countries", "offRampLocations": "Multiple countries", "rampType": "Bidirectional fiat \u2194 stablecoin" } }, "regional-hubs": { "technologies": [ "Regional on/off-ramp hubs" ], "technologyProperties": { "onRampLocations": "Regional centres", "offRampLocations": "Regional centres", "rampType": "Hub-based conversion" } } }, "prefillFrom": "P0-countries", "briefSection": "Stablecoin and FX", "text": "Where do you need fiat on-ramp and off-ramp capabilities?", "ngoText": "Where do you need fiat on-ramp and off-ramp capabilities?" }, { "id": "sq-UC-A-006-001", "type": "single-select", "options": [ { "value": "fixed-percentage", "label": "Fixed percentage of portfolio" }, { "value": "var-based", "label": "Value-at-Risk (VaR) based" }, { "value": "manual-only", "label": "Manual rebalancing only" }, { "value": "donor-directed", "label": "Donor-directed thresholds" }, { "value": "tiered-by-programme", "label": "Tiered by programme criticality" } ], "propertyMapping": { "fixed-percentage": { "technologies": [ "portfolio-rebalancing-engine", "fixed-rules" ], "technologyProperties": {} }, "var-based": { "technologies": [ "risk-analytics", "statistical-modeling" ], "technologyProperties": {} }, "manual-only": { "technologies": [ "dashboard-alerts", "manual-workflow" ], "technologyProperties": {} }, "donor-directed": { "technologies": [ "donor-configuration", "rules-engine" ], "technologyProperties": {} }, "tiered-by-programme": { "technologies": [ "programme-categorization", "tiered-rules" ], "technologyProperties": {} } }, "briefSection": "requirements", "text": "What currency exposure thresholds should trigger automatic rebalancing?", "ngoText": "What currency exposure thresholds should trigger automatic rebalancing?" }, { "id": "sq-UC-A-006-003", "type": "single-select", "options": [ { "value": "max-percentage-cap", "label": "Maximum percentage cap" }, { "value": "programme-specific", "label": "Programme-specific allocation" }, { "value": "full-stablecoin", "label": "Full stablecoin settlement" }, { "value": "hedge-only", "label": "Stablecoin as hedge only" }, { "value": "treasury-discretion", "label": "Treasury officer discretion" } ], "propertyMapping": { "max-percentage-cap": { "technologies": [ "portfolio-constraints", "cap-enforcement" ], "technologyProperties": {} }, "programme-specific": { "technologies": [ "programme-fund-mapping", "allocation-engine" ], "technologyProperties": {} }, "full-stablecoin": { "technologies": [ "stablecoin-settlement", "on-chain-treasury" ], "technologyProperties": {} }, "hedge-only": { "technologies": [ "hedging-strategy", "derivative-instruments" ], "technologyProperties": {} }, "treasury-discretion": { "technologies": [ "treasury-dashboard", "manual-controls" ], "technologyProperties": {} } }, "briefSection": "requirements", "text": "What approach would you prefer for managing stablecoin exposure relative to fiat holdings?", "ngoText": "What approach would you prefer for managing stablecoin exposure relative to fiat holdings?" }, { "id": "volatility-exposure", "label": "What is your organisation's primary currency volatility concern?", "type": "select", "briefSection": "Stablecoin and FX", "options": [ { "label": "Holding funds in volatile local currencies between receipt and disbursement", "value": "holding-local" }, { "label": "FX losses during cross-border transfers", "value": "fx-transfer" }, { "label": "Multi-currency treasury with unpredictable conversion needs", "value": "multi-currency" }, { "label": "Donor currency differs from programme currency", "value": "donor-programme-mismatch" } ], "propertyMapping": { "holding-local": { "technologies": [ "Stablecoin treasury holding" ], "technologyProperties": { "hedgingNeed": "Local currency volatility protection", "stablecoinRole": "Store of value between receipt and disbursement" } }, "fx-transfer": { "technologies": [ "FX-optimised stablecoin corridor" ], "technologyProperties": { "hedgingNeed": "Transfer-time FX risk mitigation", "stablecoinRole": "Transfer medium with stable value" } }, "multi-currency": { "technologies": [ "Multi-stablecoin treasury management" ], "technologyProperties": { "hedgingNeed": "Portfolio-level currency stability", "stablecoinRole": "Multi-denomination stable value storage" } }, "donor-programme-mismatch": { "technologies": [ "Donor-to-programme currency bridge" ], "technologyProperties": { "hedgingNeed": "Donor-programme currency alignment", "stablecoinRole": "Bridge between donor and programme currencies" } } }, "text": "What is your organisation's primary currency volatility concern?" }, { "id": "hedging-current-approach", "label": "How does your organisation currently manage currency risk?", "type": "select", "briefSection": "Current state", "options": [ { "label": "No active management, we accept the FX risk", "value": "none" }, { "label": "We use forward contracts or options with our bank", "value": "traditional-hedging" }, { "label": "We try to convert quickly to minimise exposure windows", "value": "speed-conversion" }, { "label": "We hold funds in USD or EUR to avoid local currency volatility", "value": "hard-currency-holding" } ], "propertyMapping": { "none": { "technologies": [], "technologyProperties": { "currentHedging": "No active currency risk management" } }, "traditional-hedging": { "technologies": [], "technologyProperties": { "currentHedging": "Traditional banking hedging instruments" } }, "speed-conversion": { "technologies": [], "technologyProperties": { "currentHedging": "Rapid conversion to minimise exposure" } }, "hard-currency-holding": { "technologies": [], "technologyProperties": { "currentHedging": "Hard currency denomination preference" } } }, "text": "How does your organisation currently manage currency risk?" }, { "id": "stablecoin-trust-preference", "label": "What level of regulatory backing do you require for stablecoins used in treasury?", "type": "select", "briefSection": "Stablecoin and FX", "options": [ { "label": "Fully regulated, audited reserves (e.g., MiCA-compliant)", "value": "full-regulated" }, { "label": "Major stablecoins with published attestations", "value": "attested" }, { "label": "Any reputable stablecoin with reasonable backing", "value": "flexible" } ], "propertyMapping": { "full-regulated": { "technologies": [ "Regulated stablecoin (reserve-audited, MiCA/equivalent)" ], "technologyProperties": { "stablecoinTrust": "Full regulatory compliance required" } }, "attested": { "technologies": [ "Attested stablecoin (published reserve reports)" ], "technologyProperties": { "stablecoinTrust": "Published attestation acceptable" } }, "flexible": { "technologies": [ "Reputable stablecoin" ], "technologyProperties": { "stablecoinTrust": "Flexible \u2014 reputable backing sufficient" } } }, "text": "What level of regulatory backing do you require for stablecoins used in treasury?" } ], "complexityFactors": { "relationships": 1, "operationalChange": 2, "dataCompliance": 2 }, "securityTier": "B", "suggestedCriteria": [ { "id": "SC-CURRENCY-RANGE", "name": "Currency Pair Coverage", "description": "This measures how many currency pairs the provider supports, particularly the minor currencies NGOs operate in. Treasury management requires holding and converting between multiple currencies simultaneously.", "weight": 0.25, "ratingGuide": { "5": "50+ currency pairs including minor African, Asian, and Middle Eastern currencies. Stablecoin options for volatile currencies. Direct pairs (not USD-routed).", "4": "20-50 pairs including major operating region currencies. Some stablecoin options. Good direct pair coverage.", "3": "10-20 major pairs. USD-routed for minor currencies. Limited stablecoin options.", "2": "Under 10 pairs. Major currencies only. All minor currency conversions USD-routed.", "1": "USD and EUR only. No minor currency support." } }, { "id": "SC-HEDGING", "name": "Currency Hedging Tools", "description": "The provider offers hedging instruments to protect against FX volatility. NGOs with multi-year grants face significant currency risk between budget approval and expenditure.", "weight": 0.25, "ratingGuide": { "5": "Forward contracts, options, and structured hedging products. Hedging for 6-24 month horizons. Automated hedge execution. Cost-effective for NGO transaction sizes.", "4": "Forward contracts available. 3-12 month horizons. Reasonable minimums for NGO sizes.", "3": "Basic forward contracts. Short horizons (1-3 months). Higher minimums that suit only large organisations.", "2": "Spot conversion only with rate alerts. No forward instruments. Manual timing only.", "1": "No hedging capability. Spot conversion at provider's rate only." } }, { "id": "SC-TREASURY-VIS", "name": "Multi-Currency Position Visibility", "description": "The treasury team can see all currency holdings, exposures, and pending conversions in one place. Managing 5-15 currencies across country offices requires consolidated visibility.", "weight": 0.2, "ratingGuide": { "5": "Real-time dashboard showing all currency positions, unrealised gains/losses, pending conversions, and hedging coverage. Alerts for exposure thresholds.", "4": "Good dashboard with positions and pending activity. Daily updated exposure view. Basic alerting.", "3": "Per-currency balance view. Manual calculation of exposure. Periodic reports.", "2": "Individual account views. No consolidated position. Manual tracking in spreadsheets.", "1": "No position visibility. Balance inquiry only per account." } }, { "id": "SC-ACCOUNTING-TREASURY", "name": "Accounting & Reporting Integration", "description": "The provider generates treasury reports compatible with NGO accounting requirements. Fund-level currency tracking and donor-required financial reporting must be supported.", "weight": 0.2, "ratingGuide": { "5": "Direct integration with major NGO accounting platforms. Automatic FX gain/loss calculations. Fund-level currency reporting. Donor-ready reports.", "4": "Integration with 2-3 platforms. Good FX accounting. Fund-level reporting available.", "3": "CSV/spreadsheet export with currency breakdown. Manual accounting integration. Basic FX reporting.", "2": "Transaction history export only. No FX gain/loss calculation. Manual reporting.", "1": "No export or reporting capability for treasury activity." } }, { "id": "SC-LIQUIDITY", "name": "Liquidity & Conversion Reliability", "description": "The provider can reliably convert large amounts without moving the market. NGO treasury transfers can be hundreds of thousands of dollars. Liquidity depth matters.", "weight": 0.1, "ratingGuide": { "5": "Deep liquidity pools. Handles $500K+ conversions without significant slippage. Guaranteed execution. Multiple liquidity sources.", "4": "Good liquidity for $100-500K conversions. Minor slippage on large trades. Reliable execution.", "3": "Adequate for $50-100K conversions. Noticeable slippage above that. Generally reliable.", "2": "Limited liquidity. Conversions above $20K may face delays or poor rates.", "1": "Thin liquidity. Small conversion limits. Unreliable for NGO-scale treasury operations." } } ], "procurement": { "marketMaturity": "mature", "primaryMode": "off-the-shelf", "alternativeModes": [ "rfq" ], "reasoning": "Mature treasury management SaaS market.", "exampleProductCategories": [ "treasury-management-saas", "multi-currency-fx-platform" ], "partnerChannels": [], "lastReviewed": "2026-05-01" } }, { "id": "UC-A-007", "name": "Donor fund reconciliation and tracking", "category": "A", "subcategory": "Financial Reporting", "description": "Match each donor's contribution to how it was spent, with less manual work, so every donor sees figures that agree with yours.", "bCriteria": [ "B1", "B3", "B5" ], "requiredComponents": [ { "component": "payment-rails", "description": "Transparent transaction settlement" }, { "component": "accounting-integration", "description": "Accounting system integration" }, { "component": "reconciliation-engine", "description": "Automated reconciliation" }, { "component": "reporting-module", "description": "Real-time reporting" }, { "component": "audit-mechanism", "description": "Tamper-proof audit trail" } ], "conditionalComponents": [ { "component": "smart-contracts", "condition": "If fund allocation rules are automated" } ], "crossCategoryDependencies": [], "p2TriggerConditions": { "description": "Activated when P2 shows multiple donors + complex fund tracking + reconciliation challenges", "rangeSignals": [ "donors >= 5", "fundingSource = multiple", "reconciliationTime >= 1 week" ] }, "contextFieldsTemplate": [ { "field": "donorCount", "source": "P0 funding landscape", "description": "Number of major donors" }, { "field": "reportingFrequency", "source": "P0 donor agreements", "description": "Required reporting frequency" }, { "field": "fundCategories", "source": "P2 fund management", "description": "Types of restricted/unrestricted funds" }, { "field": "currentReconciliation", "source": "P0 Q13", "description": "Current reconciliation process" } ], "implementationComplexity": "medium", "examples": { "note": "NGO financial management best practices", "references": [ { "name": "Disberse", "url": "https://www.nesta.org.uk/feature/new-radicals-2018/disberse/", "solved": "Traced international aid fund transfers reducing intermediary costs" }, { "name": "UNICEF CryptoFund", "url": "https://www.unicef.org/innovation/stories/unicef-cryptofund", "solved": "Funded global tech startups addressing child welfare, transparently and at low cost" } ] }, "solutionQuestions": [ { "id": "corridor-count", "type": "select", "options": [ { "label": "Single country", "value": "single" }, { "label": "2\u20133 countries", "value": "2-3" }, { "label": "4\u20135 countries", "value": "4-5" }, { "label": "More than 5 countries", "value": "5-plus" } ], "propertyMapping": { "single": { "technologies": [ "Single-corridor fiat on-ramp" ], "technologyProperties": { "corridorComplexity": "Single origination country", "multiRailNeeded": "No" } }, "2-3": { "technologies": [ "Multi-corridor fiat on-ramp gateway" ], "technologyProperties": { "corridorComplexity": "2\u20133 origination countries", "multiRailNeeded": "Yes \u2014 2-3 payment rails" } }, "4-5": { "technologies": [ "Multi-corridor fiat on-ramp gateway" ], "technologyProperties": { "corridorComplexity": "4\u20135 origination countries", "multiRailNeeded": "Yes \u2014 4-5 payment rails" } }, "5-plus": { "technologies": [ "Enterprise multi-corridor on-ramp gateway" ], "technologyProperties": { "corridorComplexity": "5+ origination countries", "multiRailNeeded": "Yes \u2014 enterprise-grade multi-rail" } } }, "prefillFrom": null, "briefSection": "Payment rail requirements", "text": "How many countries does your organisation send transfer funds from?", "ngoText": "How many countries does your organisation send transfer funds from?" }, { "id": "origination-country-1", "type": "select", "options": [ { "label": "United States", "value": "united-states" }, { "label": "United Kingdom", "value": "united-kingdom" }, { "label": "Germany", "value": "germany" }, { "label": "Netherlands", "value": "netherlands" }, { "label": "Switzerland", "value": "switzerland" }, { "label": "Belgium", "value": "belgium" }, { "label": "France", "value": "france" }, { "label": "Sweden", "value": "sweden" }, { "label": "Norway", "value": "norway" }, { "label": "Denmark", "value": "denmark" }, { "label": "Canada", "value": "canada" }, { "label": "Australia", "value": "australia" }, { "label": "Japan", "value": "japan" }, { "label": "Ireland", "value": "ireland" }, { "label": "Italy", "value": "italy" }, { "label": "Spain", "value": "spain" }, { "label": "Austria", "value": "austria" }, { "label": "Finland", "value": "finland" }, { "label": "Luxembourg", "value": "luxembourg" }, { "label": "South Korea", "value": "south-korea" }, { "label": "New Zealand", "value": "new-zealand" }, { "label": "United Arab Emirates", "value": "united-arab-emirates" }, { "label": "Singapore", "value": "singapore" }, { "label": "Other", "value": "other" } ], "propertyMapping": { "united-states": { "technologies": [ "ACH/wire fiat on-ramp" ], "technologyProperties": { "onRampType": "ACH/Fedwire bank transfer", "onRampRegion": "United States", "settlementRail": "ACH / Fedwire" } }, "united-kingdom": { "technologies": [ "UK Faster Payments on-ramp" ], "technologyProperties": { "onRampType": "Faster Payments bank transfer", "onRampRegion": "United Kingdom", "settlementRail": "FPS / BACS" } }, "germany": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "netherlands": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "switzerland": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SIC/SEPA bank transfer", "onRampRegion": "Switzerland/EU", "settlementRail": "SIC / SEPA Credit Transfer" } }, "belgium": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "france": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "sweden": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "norway": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA-adjacent bank transfer", "onRampRegion": "EEA", "settlementRail": "SEPA Credit Transfer" } }, "denmark": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "canada": { "technologies": [ "Canadian EFT on-ramp" ], "technologyProperties": { "onRampType": "Interac/EFT bank transfer", "onRampRegion": "Canada", "settlementRail": "Interac / EFT" } }, "australia": { "technologies": [ "Australian NPP on-ramp" ], "technologyProperties": { "onRampType": "NPP bank transfer", "onRampRegion": "Australia", "settlementRail": "NPP / BECS" } }, "japan": { "technologies": [ "Japanese Zengin on-ramp" ], "technologyProperties": { "onRampType": "Zengin bank transfer", "onRampRegion": "Japan", "settlementRail": "Zengin System" } }, "ireland": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "italy": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "spain": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "austria": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "finland": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "luxembourg": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "south-korea": { "technologies": [ "Korean banking on-ramp" ], "technologyProperties": { "onRampType": "KFTC bank transfer", "onRampRegion": "South Korea", "settlementRail": "KFTC / BOK-Wire" } }, "new-zealand": { "technologies": [ "NZ banking on-ramp" ], "technologyProperties": { "onRampType": "SBI bank transfer", "onRampRegion": "New Zealand", "settlementRail": "SBI / ESAS" } }, "united-arab-emirates": { "technologies": [ "UAE banking on-ramp" ], "technologyProperties": { "onRampType": "UAEFTS bank transfer", "onRampRegion": "United Arab Emirates", "settlementRail": "UAEFTS / IPP" } }, "singapore": { "technologies": [ "Singapore FAST on-ramp" ], "technologyProperties": { "onRampType": "FAST bank transfer", "onRampRegion": "Singapore", "settlementRail": "FAST / MEPS+" } }, "other": { "technologies": [ "Regional fiat on-ramp" ], "technologyProperties": { "onRampType": "Local rail bank transfer", "onRampRegion": "Region-specific", "settlementRail": "Local payment network" } } }, "showIf": { "questionId": "corridor-count", "minValue": "single" }, "prefillFrom": null, "briefSection": "Payment rail requirements", "text": "Which country do you most frequently initiate transfers from?", "ngoText": "Which country do you most frequently initiate transfers from?" }, { "id": "origination-country-2", "type": "select", "options": [ { "label": "United States", "value": "united-states" }, { "label": "United Kingdom", "value": "united-kingdom" }, { "label": "Germany", "value": "germany" }, { "label": "Netherlands", "value": "netherlands" }, { "label": "Switzerland", "value": "switzerland" }, { "label": "Belgium", "value": "belgium" }, { "label": "France", "value": "france" }, { "label": "Sweden", "value": "sweden" }, { "label": "Norway", "value": "norway" }, { "label": "Denmark", "value": "denmark" }, { "label": "Canada", "value": "canada" }, { "label": "Australia", "value": "australia" }, { "label": "Japan", "value": "japan" }, { "label": "Ireland", "value": "ireland" }, { "label": "Italy", "value": "italy" }, { "label": "Spain", "value": "spain" }, { "label": "Austria", "value": "austria" }, { "label": "Finland", "value": "finland" }, { "label": "Luxembourg", "value": "luxembourg" }, { "label": "South Korea", "value": "south-korea" }, { "label": "New Zealand", "value": "new-zealand" }, { "label": "United Arab Emirates", "value": "united-arab-emirates" }, { "label": "Singapore", "value": "singapore" }, { "label": "Other", "value": "other" } ], "propertyMapping": { "united-states": { "technologies": [ "ACH/wire fiat on-ramp" ], "technologyProperties": { "onRampType": "ACH/Fedwire bank transfer", "onRampRegion": "United States", "settlementRail": "ACH / Fedwire" } }, "united-kingdom": { "technologies": [ "UK Faster Payments on-ramp" ], "technologyProperties": { "onRampType": "Faster Payments bank transfer", "onRampRegion": "United Kingdom", "settlementRail": "FPS / BACS" } }, "germany": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "netherlands": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "switzerland": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SIC/SEPA bank transfer", "onRampRegion": "Switzerland/EU", "settlementRail": "SIC / SEPA Credit Transfer" } }, "belgium": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "france": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "sweden": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "norway": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA-adjacent bank transfer", "onRampRegion": "EEA", "settlementRail": "SEPA Credit Transfer" } }, "denmark": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "canada": { "technologies": [ "Canadian EFT on-ramp" ], "technologyProperties": { "onRampType": "Interac/EFT bank transfer", "onRampRegion": "Canada", "settlementRail": "Interac / EFT" } }, "australia": { "technologies": [ "Australian NPP on-ramp" ], "technologyProperties": { "onRampType": "NPP bank transfer", "onRampRegion": "Australia", "settlementRail": "NPP / BECS" } }, "japan": { "technologies": [ "Japanese Zengin on-ramp" ], "technologyProperties": { "onRampType": "Zengin bank transfer", "onRampRegion": "Japan", "settlementRail": "Zengin System" } }, "ireland": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "italy": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "spain": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "austria": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "finland": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "luxembourg": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "south-korea": { "technologies": [ "Korean banking on-ramp" ], "technologyProperties": { "onRampType": "KFTC bank transfer", "onRampRegion": "South Korea", "settlementRail": "KFTC / BOK-Wire" } }, "new-zealand": { "technologies": [ "NZ banking on-ramp" ], "technologyProperties": { "onRampType": "SBI bank transfer", "onRampRegion": "New Zealand", "settlementRail": "SBI / ESAS" } }, "united-arab-emirates": { "technologies": [ "UAE banking on-ramp" ], "technologyProperties": { "onRampType": "UAEFTS bank transfer", "onRampRegion": "United Arab Emirates", "settlementRail": "UAEFTS / IPP" } }, "singapore": { "technologies": [ "Singapore FAST on-ramp" ], "technologyProperties": { "onRampType": "FAST bank transfer", "onRampRegion": "Singapore", "settlementRail": "FAST / MEPS+" } }, "other": { "technologies": [ "Regional fiat on-ramp" ], "technologyProperties": { "onRampType": "Local rail bank transfer", "onRampRegion": "Region-specific", "settlementRail": "Local payment network" } } }, "showIf": { "questionId": "corridor-count", "minValue": "2-3" }, "prefillFrom": null, "briefSection": "Payment rail requirements", "text": "Second most common transfer origination country (if applicable)", "ngoText": "Second most common transfer origination country (if applicable)" }, { "id": "origination-country-3", "type": "select", "options": [ { "label": "United States", "value": "united-states" }, { "label": "United Kingdom", "value": "united-kingdom" }, { "label": "Germany", "value": "germany" }, { "label": "Netherlands", "value": "netherlands" }, { "label": "Switzerland", "value": "switzerland" }, { "label": "Belgium", "value": "belgium" }, { "label": "France", "value": "france" }, { "label": "Sweden", "value": "sweden" }, { "label": "Norway", "value": "norway" }, { "label": "Denmark", "value": "denmark" }, { "label": "Canada", "value": "canada" }, { "label": "Australia", "value": "australia" }, { "label": "Japan", "value": "japan" }, { "label": "Ireland", "value": "ireland" }, { "label": "Italy", "value": "italy" }, { "label": "Spain", "value": "spain" }, { "label": "Austria", "value": "austria" }, { "label": "Finland", "value": "finland" }, { "label": "Luxembourg", "value": "luxembourg" }, { "label": "South Korea", "value": "south-korea" }, { "label": "New Zealand", "value": "new-zealand" }, { "label": "United Arab Emirates", "value": "united-arab-emirates" }, { "label": "Singapore", "value": "singapore" }, { "label": "Other", "value": "other" } ], "propertyMapping": { "united-states": { "technologies": [ "ACH/wire fiat on-ramp" ], "technologyProperties": { "onRampType": "ACH/Fedwire bank transfer", "onRampRegion": "United States", "settlementRail": "ACH / Fedwire" } }, "united-kingdom": { "technologies": [ "UK Faster Payments on-ramp" ], "technologyProperties": { "onRampType": "Faster Payments bank transfer", "onRampRegion": "United Kingdom", "settlementRail": "FPS / BACS" } }, "germany": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "netherlands": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "switzerland": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SIC/SEPA bank transfer", "onRampRegion": "Switzerland/EU", "settlementRail": "SIC / SEPA Credit Transfer" } }, "belgium": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "france": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "sweden": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "norway": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA-adjacent bank transfer", "onRampRegion": "EEA", "settlementRail": "SEPA Credit Transfer" } }, "denmark": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "canada": { "technologies": [ "Canadian EFT on-ramp" ], "technologyProperties": { "onRampType": "Interac/EFT bank transfer", "onRampRegion": "Canada", "settlementRail": "Interac / EFT" } }, "australia": { "technologies": [ "Australian NPP on-ramp" ], "technologyProperties": { "onRampType": "NPP bank transfer", "onRampRegion": "Australia", "settlementRail": "NPP / BECS" } }, "japan": { "technologies": [ "Japanese Zengin on-ramp" ], "technologyProperties": { "onRampType": "Zengin bank transfer", "onRampRegion": "Japan", "settlementRail": "Zengin System" } }, "ireland": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "italy": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "spain": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "austria": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "finland": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "luxembourg": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "south-korea": { "technologies": [ "Korean banking on-ramp" ], "technologyProperties": { "onRampType": "KFTC bank transfer", "onRampRegion": "South Korea", "settlementRail": "KFTC / BOK-Wire" } }, "new-zealand": { "technologies": [ "NZ banking on-ramp" ], "technologyProperties": { "onRampType": "SBI bank transfer", "onRampRegion": "New Zealand", "settlementRail": "SBI / ESAS" } }, "united-arab-emirates": { "technologies": [ "UAE banking on-ramp" ], "technologyProperties": { "onRampType": "UAEFTS bank transfer", "onRampRegion": "United Arab Emirates", "settlementRail": "UAEFTS / IPP" } }, "singapore": { "technologies": [ "Singapore FAST on-ramp" ], "technologyProperties": { "onRampType": "FAST bank transfer", "onRampRegion": "Singapore", "settlementRail": "FAST / MEPS+" } }, "other": { "technologies": [ "Regional fiat on-ramp" ], "technologyProperties": { "onRampType": "Local rail bank transfer", "onRampRegion": "Region-specific", "settlementRail": "Local payment network" } } }, "showIf": { "questionId": "corridor-count", "minValue": "2-3" }, "prefillFrom": null, "briefSection": "Payment rail requirements", "text": "Third transfer origination country (if applicable)", "ngoText": "Third transfer origination country (if applicable)" }, { "id": "origination-country-4", "type": "select", "options": [ { "label": "United States", "value": "united-states" }, { "label": "United Kingdom", "value": "united-kingdom" }, { "label": "Germany", "value": "germany" }, { "label": "Netherlands", "value": "netherlands" }, { "label": "Switzerland", "value": "switzerland" }, { "label": "Belgium", "value": "belgium" }, { "label": "France", "value": "france" }, { "label": "Sweden", "value": "sweden" }, { "label": "Norway", "value": "norway" }, { "label": "Denmark", "value": "denmark" }, { "label": "Canada", "value": "canada" }, { "label": "Australia", "value": "australia" }, { "label": "Japan", "value": "japan" }, { "label": "Ireland", "value": "ireland" }, { "label": "Italy", "value": "italy" }, { "label": "Spain", "value": "spain" }, { "label": "Austria", "value": "austria" }, { "label": "Finland", "value": "finland" }, { "label": "Luxembourg", "value": "luxembourg" }, { "label": "South Korea", "value": "south-korea" }, { "label": "New Zealand", "value": "new-zealand" }, { "label": "United Arab Emirates", "value": "united-arab-emirates" }, { "label": "Singapore", "value": "singapore" }, { "label": "Other", "value": "other" } ], "propertyMapping": { "united-states": { "technologies": [ "ACH/wire fiat on-ramp" ], "technologyProperties": { "onRampType": "ACH/Fedwire bank transfer", "onRampRegion": "United States", "settlementRail": "ACH / Fedwire" } }, "united-kingdom": { "technologies": [ "UK Faster Payments on-ramp" ], "technologyProperties": { "onRampType": "Faster Payments bank transfer", "onRampRegion": "United Kingdom", "settlementRail": "FPS / BACS" } }, "germany": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "netherlands": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "switzerland": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SIC/SEPA bank transfer", "onRampRegion": "Switzerland/EU", "settlementRail": "SIC / SEPA Credit Transfer" } }, "belgium": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "france": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "sweden": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "norway": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA-adjacent bank transfer", "onRampRegion": "EEA", "settlementRail": "SEPA Credit Transfer" } }, "denmark": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "canada": { "technologies": [ "Canadian EFT on-ramp" ], "technologyProperties": { "onRampType": "Interac/EFT bank transfer", "onRampRegion": "Canada", "settlementRail": "Interac / EFT" } }, "australia": { "technologies": [ "Australian NPP on-ramp" ], "technologyProperties": { "onRampType": "NPP bank transfer", "onRampRegion": "Australia", "settlementRail": "NPP / BECS" } }, "japan": { "technologies": [ "Japanese Zengin on-ramp" ], "technologyProperties": { "onRampType": "Zengin bank transfer", "onRampRegion": "Japan", "settlementRail": "Zengin System" } }, "ireland": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "italy": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "spain": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "austria": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "finland": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "luxembourg": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "south-korea": { "technologies": [ "Korean banking on-ramp" ], "technologyProperties": { "onRampType": "KFTC bank transfer", "onRampRegion": "South Korea", "settlementRail": "KFTC / BOK-Wire" } }, "new-zealand": { "technologies": [ "NZ banking on-ramp" ], "technologyProperties": { "onRampType": "SBI bank transfer", "onRampRegion": "New Zealand", "settlementRail": "SBI / ESAS" } }, "united-arab-emirates": { "technologies": [ "UAE banking on-ramp" ], "technologyProperties": { "onRampType": "UAEFTS bank transfer", "onRampRegion": "United Arab Emirates", "settlementRail": "UAEFTS / IPP" } }, "singapore": { "technologies": [ "Singapore FAST on-ramp" ], "technologyProperties": { "onRampType": "FAST bank transfer", "onRampRegion": "Singapore", "settlementRail": "FAST / MEPS+" } }, "other": { "technologies": [ "Regional fiat on-ramp" ], "technologyProperties": { "onRampType": "Local rail bank transfer", "onRampRegion": "Region-specific", "settlementRail": "Local payment network" } } }, "showIf": { "questionId": "corridor-count", "minValue": "4-5" }, "prefillFrom": null, "briefSection": "Payment rail requirements", "text": "Fourth transfer origination country (if applicable)", "ngoText": "Fourth transfer origination country (if applicable)" }, { "id": "origination-country-5", "type": "select", "options": [ { "label": "United States", "value": "united-states" }, { "label": "United Kingdom", "value": "united-kingdom" }, { "label": "Germany", "value": "germany" }, { "label": "Netherlands", "value": "netherlands" }, { "label": "Switzerland", "value": "switzerland" }, { "label": "Belgium", "value": "belgium" }, { "label": "France", "value": "france" }, { "label": "Sweden", "value": "sweden" }, { "label": "Norway", "value": "norway" }, { "label": "Denmark", "value": "denmark" }, { "label": "Canada", "value": "canada" }, { "label": "Australia", "value": "australia" }, { "label": "Japan", "value": "japan" }, { "label": "Ireland", "value": "ireland" }, { "label": "Italy", "value": "italy" }, { "label": "Spain", "value": "spain" }, { "label": "Austria", "value": "austria" }, { "label": "Finland", "value": "finland" }, { "label": "Luxembourg", "value": "luxembourg" }, { "label": "South Korea", "value": "south-korea" }, { "label": "New Zealand", "value": "new-zealand" }, { "label": "United Arab Emirates", "value": "united-arab-emirates" }, { "label": "Singapore", "value": "singapore" }, { "label": "Other", "value": "other" } ], "propertyMapping": { "united-states": { "technologies": [ "ACH/wire fiat on-ramp" ], "technologyProperties": { "onRampType": "ACH/Fedwire bank transfer", "onRampRegion": "United States", "settlementRail": "ACH / Fedwire" } }, "united-kingdom": { "technologies": [ "UK Faster Payments on-ramp" ], "technologyProperties": { "onRampType": "Faster Payments bank transfer", "onRampRegion": "United Kingdom", "settlementRail": "FPS / BACS" } }, "germany": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "netherlands": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "switzerland": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SIC/SEPA bank transfer", "onRampRegion": "Switzerland/EU", "settlementRail": "SIC / SEPA Credit Transfer" } }, "belgium": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "france": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "sweden": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "norway": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA-adjacent bank transfer", "onRampRegion": "EEA", "settlementRail": "SEPA Credit Transfer" } }, "denmark": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "canada": { "technologies": [ "Canadian EFT on-ramp" ], "technologyProperties": { "onRampType": "Interac/EFT bank transfer", "onRampRegion": "Canada", "settlementRail": "Interac / EFT" } }, "australia": { "technologies": [ "Australian NPP on-ramp" ], "technologyProperties": { "onRampType": "NPP bank transfer", "onRampRegion": "Australia", "settlementRail": "NPP / BECS" } }, "japan": { "technologies": [ "Japanese Zengin on-ramp" ], "technologyProperties": { "onRampType": "Zengin bank transfer", "onRampRegion": "Japan", "settlementRail": "Zengin System" } }, "ireland": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "italy": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "spain": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "austria": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "finland": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "luxembourg": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "south-korea": { "technologies": [ "Korean banking on-ramp" ], "technologyProperties": { "onRampType": "KFTC bank transfer", "onRampRegion": "South Korea", "settlementRail": "KFTC / BOK-Wire" } }, "new-zealand": { "technologies": [ "NZ banking on-ramp" ], "technologyProperties": { "onRampType": "SBI bank transfer", "onRampRegion": "New Zealand", "settlementRail": "SBI / ESAS" } }, "united-arab-emirates": { "technologies": [ "UAE banking on-ramp" ], "technologyProperties": { "onRampType": "UAEFTS bank transfer", "onRampRegion": "United Arab Emirates", "settlementRail": "UAEFTS / IPP" } }, "singapore": { "technologies": [ "Singapore FAST on-ramp" ], "technologyProperties": { "onRampType": "FAST bank transfer", "onRampRegion": "Singapore", "settlementRail": "FAST / MEPS+" } }, "other": { "technologies": [ "Regional fiat on-ramp" ], "technologyProperties": { "onRampType": "Local rail bank transfer", "onRampRegion": "Region-specific", "settlementRail": "Local payment network" } } }, "showIf": { "questionId": "corridor-count", "minValue": "4-5" }, "prefillFrom": null, "briefSection": "Payment rail requirements", "text": "Fifth transfer origination country (if applicable)", "ngoText": "Fifth transfer origination country (if applicable)" }, { "id": "funding-method", "type": "select", "options": [ { "label": "Bank transfer from organisation account", "value": "bank-transfer" }, { "label": "Card payment from organisation", "value": "card-payment" }, { "label": "Direct stablecoin funding (organisation already holds stablecoins)", "value": "direct-stablecoin" }, { "label": "Mixed: bank transfer for most, card for urgent payments", "value": "mixed-methods" } ], "propertyMapping": { "bank-transfer": { "technologies": [ "Bank-integrated fiat on-ramp" ], "technologyProperties": { "fundingSource": "Organisation bank account", "onRampSpeed": "1-2 business days (SEPA/ACH) or same-day (Faster Payments/wire)", "kybRequired": "Yes \u2014 organisation KYB verification" } }, "card-payment": { "technologies": [ "Card payment on-ramp" ], "technologyProperties": { "fundingSource": "Organisation payment card", "onRampSpeed": "Near-instant", "kybRequired": "Yes \u2014 card verification and organisation KYB" } }, "direct-stablecoin": { "technologies": [ "Direct stablecoin treasury funding" ], "technologyProperties": { "fundingSource": "Existing stablecoin holdings", "onRampSpeed": "Immediate (no fiat conversion needed)", "kybRequired": "Wallet verification only" } }, "mixed-methods": { "technologies": [ "Multi-method fiat on-ramp", "Card payment on-ramp" ], "technologyProperties": { "fundingSource": "Bank transfer (primary) + card (urgent)", "onRampSpeed": "Varies by method", "kybRequired": "Yes \u2014 full organisation KYB" } } }, "prefillFrom": null, "briefSection": "Payment rail requirements", "text": "How does your organisation currently fund international transfers or payments?", "ngoText": "How does your organisation currently fund international transfers or payments?" }, { "id": "reconciliation-pain", "type": "select", "options": [ { "label": "Matching HQ disbursements to field receipts", "value": "disbursement-matching" }, { "label": "Tracking fund usage against donor restrictions", "value": "restriction-tracking" }, { "label": "Multi-currency reconciliation across offices", "value": "multi-currency" }, { "label": "Time lag: information arrives weeks after transactions", "value": "time-lag" }, { "label": "Manual data entry errors", "value": "data-errors" } ], "propertyMapping": { "disbursement-matching": { "technologies": [ "Real-time shared ledger", "Automated matching engine" ], "technologyProperties": { "reconciliationCapability": "Automatic disbursement-to-receipt matching", "matchingSpeed": "Real-time" } }, "restriction-tracking": { "technologies": [ "Smart contract fund restriction enforcement", "Fund tagging engine" ], "technologyProperties": { "reconciliationCapability": "Automated restriction compliance checking", "matchingSpeed": "Per-transaction" } }, "multi-currency": { "technologies": [ "Multi-currency reconciliation engine", "FX rate tracking" ], "technologyProperties": { "reconciliationCapability": "Cross-currency automated matching", "matchingSpeed": "Per-transaction with rate snapshots" } }, "time-lag": { "technologies": [ "Real-time shared ledger", "Instant notification system" ], "technologyProperties": { "reconciliationCapability": "Zero-lag real-time visibility", "matchingSpeed": "Instant" } }, "data-errors": { "technologies": [ "Automated data capture", "Blockchain-anchored records" ], "technologyProperties": { "reconciliationCapability": "Eliminate manual entry via automation", "matchingSpeed": "At source \u2014 no re-entry" } } }, "prefillFrom": "P2-CatA-Q8b", "briefSection": "Current state", "text": "What is the biggest reconciliation challenge you face today?", "ngoText": "What is the biggest reconciliation challenge you face today?" }, { "id": "donor-reporting-format", "type": "multiselect", "options": [ { "label": "Donor-specific templates (each donor has own format)", "value": "donor-specific" }, { "label": "IATI standard reporting", "value": "iati" }, { "label": "Real-time dashboard access for donors", "value": "realtime-dashboard" }, { "label": "Periodic summary reports (PDF/spreadsheet)", "value": "periodic-summary" }, { "label": "Transaction-level detail export", "value": "transaction-detail" }, { "label": "No specific format required", "value": "flexible" } ], "propertyMapping": { "donor-specific": { "technologies": [ "Configurable report template engine" ], "technologyProperties": { "reportingFormat": "Per-donor custom templates", "exportFormats": "Multiple (PDF, spreadsheet, CSV)" } }, "iati": { "technologies": [ "IATI-compliant reporting module" ], "technologyProperties": { "reportingFormat": "IATI standard", "exportFormats": "IATI XML" } }, "realtime-dashboard": { "technologies": [ "Donor-facing real-time dashboard" ], "technologyProperties": { "reportingFormat": "Interactive dashboard", "exportFormats": "Web portal with export" } }, "periodic-summary": { "technologies": [ "Automated report generation" ], "technologyProperties": { "reportingFormat": "Scheduled summaries", "exportFormats": "PDF and spreadsheet" } }, "transaction-detail": { "technologies": [ "Transaction explorer", "Data export module" ], "technologyProperties": { "reportingFormat": "Transaction-level detail", "exportFormats": "CSV, spreadsheet, API" } }, "flexible": { "technologies": [ "Standard reporting module" ], "technologyProperties": { "reportingFormat": "Standard templates", "exportFormats": "PDF, spreadsheet, CSV" } } }, "prefillFrom": null, "briefSection": "Reporting and audit", "text": "What reporting formats do your donors require?", "ngoText": "What reporting formats do your donors require?" }, { "id": "fund-restrictions", "type": "select", "options": [ { "label": "Simple: restricted vs unrestricted only", "value": "simple" }, { "label": "Moderate, by programme, geography, and cost category", "value": "moderate" }, { "label": "Complex: nested restrictions with time limits and conditions", "value": "complex" }, { "label": "Very complex: different rules per donor with overlapping restrictions", "value": "very-complex" } ], "propertyMapping": { "simple": { "technologies": [ "Dual-wallet segregation (restricted/unrestricted)" ], "technologyProperties": { "restrictionEngine": "Binary tag", "enforcementLevel": "Wallet-level separation" } }, "moderate": { "technologies": [ "Multi-dimensional fund tagging", "Smart contract spending rules" ], "technologyProperties": { "restrictionEngine": "Multi-tag (programme, geography, cost)", "enforcementLevel": "Smart contract-enforced categories" } }, "complex": { "technologies": [ "Advanced restriction engine", "Time-bound smart contracts", "Conditional release logic" ], "technologyProperties": { "restrictionEngine": "Nested conditional restrictions", "enforcementLevel": "Smart contract-enforced with time/condition triggers" } }, "very-complex": { "technologies": [ "Enterprise restriction engine", "Multi-donor rule aggregation", "Conflict resolution logic" ], "technologyProperties": { "restrictionEngine": "Multi-donor overlapping rules", "enforcementLevel": "Automated rule intersection and conflict resolution" } } }, "prefillFrom": null, "briefSection": "Payment logic", "text": "How complex are donor fund restrictions that need to be tracked?", "ngoText": "How complex are donor fund restrictions that need to be tracked?" }, { "id": "reconciliation-frequency", "type": "select", "options": [ { "label": "Real-time / continuous", "value": "realtime" }, { "label": "Daily", "value": "daily" }, { "label": "Weekly", "value": "weekly" }, { "label": "Monthly", "value": "monthly" } ], "propertyMapping": { "realtime": { "technologies": [ "Real-time shared ledger", "Continuous reconciliation engine" ], "technologyProperties": { "reconciliationFrequency": "Continuous", "lagTolerance": "Zero" } }, "daily": { "technologies": [ "Automated daily reconciliation batch" ], "technologyProperties": { "reconciliationFrequency": "Daily automated", "lagTolerance": "24 hours" } }, "weekly": { "technologies": [ "Automated weekly reconciliation" ], "technologyProperties": { "reconciliationFrequency": "Weekly automated", "lagTolerance": "7 days" } }, "monthly": { "technologies": [ "Automated monthly reconciliation" ], "technologyProperties": { "reconciliationFrequency": "Monthly automated", "lagTolerance": "30 days" } } }, "prefillFrom": "P2-CatA-Q8a", "briefSection": "Payment operations", "text": "How often does reconciliation need to happen?", "ngoText": "How often does reconciliation need to happen?" }, { "id": "accounting-system-recon", "type": "select", "options": [ { "label": "Large enterprise ERP", "value": "sap" }, { "label": "Cloud ERP", "value": "oracle" }, { "label": "Small-business accounting software", "value": "quickbooks" }, { "label": "Custom/bespoke system", "value": "custom" }, { "label": "Spreadsheet-based", "value": "spreadsheet" }, { "label": "Multiple different systems across offices", "value": "multiple" } ], "propertyMapping": { "sap": { "technologies": [ "Enterprise ERP connection" ], "technologyProperties": { "erpIntegration": "Two-way enterprise ERP connection", "apiType": "Enterprise ERP API" } }, "oracle": { "technologies": [ "Cloud ERP connection" ], "technologyProperties": { "erpIntegration": "Two-way cloud ERP connection", "apiType": "REST API" } }, "quickbooks": { "technologies": [ "Accounting software connection" ], "technologyProperties": { "erpIntegration": "Accounting software sync", "apiType": "Accounting software API" } }, "custom": { "technologies": [ "Custom API integration" ], "technologyProperties": { "erpIntegration": "Custom system connection", "apiType": "Bespoke" } }, "spreadsheet": { "technologies": [ "CSV/spreadsheet import/export" ], "technologyProperties": { "erpIntegration": "File-based sync", "apiType": "CSV import/export" } }, "multiple": { "technologies": [ "Connects multiple office systems" ], "technologyProperties": { "erpIntegration": "Multi-system connection hub", "apiType": "Multiple APIs" } } }, "prefillFrom": "P0-S3-Q13", "briefSection": "Integration requirements", "text": "What accounting system do you use for reconciliation?", "ngoText": "What accounting system do you use for reconciliation?" }, { "id": "sq-UC-A-007-001", "type": "single-select", "options": [ { "value": "hard-block", "label": "Hard block: prevent non-compliant transactions" }, { "value": "soft-warning", "label": "Soft warning: alert but allow" }, { "value": "post-hoc-flag", "label": "Post-hoc flag for later review" }, { "value": "approval-workflow", "label": "Require approval for restricted use" }, { "value": "smart-contract-enforce", "label": "Automated rule enforcement" } ], "propertyMapping": { "hard-block": { "technologies": [ "transaction-validation", "restriction-enforcement" ], "technologyProperties": {} }, "soft-warning": { "technologies": [ "transaction-monitoring", "alert-system" ], "technologyProperties": {} }, "post-hoc-flag": { "technologies": [ "logging-engine", "flag-tracking" ], "technologyProperties": {} }, "approval-workflow": { "technologies": [ "approval-engine", "restriction-tracking" ], "technologyProperties": {} }, "smart-contract-enforce": { "technologies": [ "smart-contracts", "on-chain-restrictions" ], "technologyProperties": {} } }, "briefSection": "requirements", "text": "How are donor fund restrictions currently enforced at the transaction level?", "ngoText": "How are donor fund restrictions currently enforced at the transaction level?" }, { "id": "audit-mechanism-approach", "type": "select", "options": [ { "label": "Automatic checks that flag problems as they happen", "value": "automated-realtime" }, { "label": "Regular scheduled reviews with tamper-proof records", "value": "periodic-batch" }, { "label": "Ability to check any record at any time with proof it has not been altered", "value": "on-demand" }, { "label": "External auditors can log in and review records independently", "value": "third-party" } ], "propertyMapping": { "automated-realtime": { "technologies": [ "Real-time audit mechanism", "Automated anomaly detection", "Audit alert service" ], "technologyProperties": { "auditFrequency": "Continuous / real-time", "auditAccess": "System-generated alerts", "complianceReporting": "Automated" } }, "periodic-batch": { "technologies": [ "Periodic audit mechanism", "Batch verification engine", "Audit report generator" ], "technologyProperties": { "auditFrequency": "Scheduled (daily/weekly/monthly)", "auditAccess": "Generated audit reports", "complianceReporting": "Scheduled" } }, "on-demand": { "technologies": [ "On-demand audit mechanism", "Audit query interface", "Record verification service" ], "technologyProperties": { "auditFrequency": "On-demand", "auditAccess": "Query-based", "complianceReporting": "On request" } }, "third-party": { "technologies": [ "Third-party audit mechanism", "Auditor access portal", "Audit evidence export" ], "technologyProperties": { "auditFrequency": "As required by auditor", "auditAccess": "Dedicated portal with read-only access", "complianceReporting": "Auditor-directed" } } }, "prefillFrom": null, "briefSection": "Audit and verification", "text": "Who needs to verify that actions happened correctly, and how easily should they be able to check?", "ngoText": "How should auditing and verification work for this solution?" } ], "complexityFactors": { "relationships": 1, "operationalChange": 2, "dataCompliance": 1 }, "securityTier": "B", "suggestedCriteria": [ { "id": "SC-DONOR-TRACE", "name": "End-to-End Fund Traceability", "description": "Every dollar can be traced from donor receipt through to programme expenditure. Donors increasingly demand proof that their specific funds were used as intended.", "weight": 0.3, "ratingGuide": { "5": "Immutable audit trail from donor deposit to beneficiary delivery. Per-transaction fund tagging. Real-time traceability dashboard for donors. Cryptographic proof of fund flow.", "4": "Good traceability with fund tagging through major milestones. Audit trail available on request.", "3": "Fund tracking at programme level (not per-transaction). Periodic reconciliation reports.", "2": "Batch-level tracking. Manual reconciliation between donor funds and expenditure.", "1": "No fund traceability beyond basic accounting entries." } }, { "id": "SC-RECON-AUTO", "name": "Automated Reconciliation", "description": "The provider automatically matches incoming donor funds with outgoing expenditure across multiple currencies and programmes. Manual reconciliation is the biggest time drain in NGO finance.", "weight": 0.25, "ratingGuide": { "5": "Fully automated matching of inflows to outflows by fund/grant code. Multi-currency. Exception handling with alerts. Under 1% unmatched transactions.", "4": "Automated matching for 80%+ transactions. Good exception reporting. Multi-currency support.", "3": "Semi-automated with suggested matches. Manual review for complex items. Single currency automated.", "2": "Rule-based suggestions but mostly manual matching. Limited multi-currency.", "1": "No automated reconciliation. All matching done manually in spreadsheets." } }, { "id": "SC-DONOR-REPORT", "name": "Donor Reporting Formats", "description": "The provider can generate reports in the formats different donors require. Each donor has specific reporting templates, periods, and categorisation requirements.", "weight": 0.2, "ratingGuide": { "5": "Configurable report templates matching major donor formats (USAID, DFID/FCDO, EU, UN agencies). Automated scheduled generation. Multiple output formats.", "4": "Pre-built templates for 3-4 major donors. Customisable fields. Scheduled reports.", "3": "Flexible reporting with custom date ranges and categories. Manual formatting for donor-specific templates.", "2": "Standard reports only. Manual reformatting needed for donor submissions.", "1": "Minimal reporting. Transaction lists only. Extensive manual work for donor reports." } }, { "id": "SC-MULTI-GRANT", "name": "Multi-Grant Fund Segregation", "description": "The provider can track restricted, unrestricted, and designated funds from multiple donors simultaneously without commingling. Most NGOs manage 10-50+ active grants with different restrictions.", "weight": 0.15, "ratingGuide": { "5": "Unlimited fund/grant tracking. Automatic restriction enforcement (prevents spending restricted funds on unapproved items). Cross-grant reporting.", "4": "Good multi-grant tracking. Alert when spending approaches restriction limits. Cross-grant views.", "3": "Fund tagging available. Manual restriction enforcement. Per-grant reporting possible.", "2": "Basic fund coding. No restriction enforcement. Reports per fund require manual filtering.", "1": "Single fund view. No grant-level segregation. Manual tracking in external systems." } }, { "id": "SC-AUDIT-READY", "name": "Audit Readiness & Evidence", "description": "The provider produces audit-ready documentation. External audits are annual for most NGOs. The provider must generate evidence packages that auditors accept.", "weight": 0.1, "ratingGuide": { "5": "One-click audit package generation. Cryptographically verifiable records. Bank confirmation equivalents. Accepted by Big 4 audit firms.", "4": "Comprehensive audit reports. Verifiable transaction records. Good auditor acceptance.", "3": "Detailed transaction logs exportable for audit. Standard documentation. Generally accepted.", "2": "Basic transaction records. Additional documentation needed for audit satisfaction.", "1": "Insufficient documentation for audit purposes. Significant additional evidence gathering required." } } ], "procurement": { "marketMaturity": "mature", "primaryMode": "off-the-shelf", "alternativeModes": [ "rfq" ], "reasoning": "Donor management products with reconciliation features widely available.", "exampleProductCategories": [ "donor-management-saas", "grants-management-platform" ], "partnerChannels": [], "lastReviewed": "2026-05-01" } }, { "id": "UC-A-008", "name": "Real-time financial reporting across programmes", "category": "A", "subcategory": "Financial Reporting", "description": "Bring the financial records of every country programme into one report that stays current, so you do not wait for month-end consolidation.", "bCriteria": [ "B1", "B3" ], "requiredComponents": [ { "component": "accounting-integration", "description": "Real-time accounting data feeds" }, { "component": "reporting-module", "description": "Dynamic reporting dashboard" }, { "component": "data-layer", "description": "Centralized financial data layer" }, { "component": "audit-mechanism", "description": "Transaction audit trail" } ], "conditionalComponents": [ { "component": "encryption-privacy", "condition": "If sensitive financial data needs protection" } ], "crossCategoryDependencies": [ "UC-C-048 if audit trail compliance needed" ], "p2TriggerConditions": { "description": "Activated when P2 shows multiple programmes + reporting burden + need for real-time visibility", "rangeSignals": [ "programmes >= 3", "reportingFrequency >= monthly", "decisionLatency >= high" ] }, "contextFieldsTemplate": [ { "field": "programmeCount", "source": "P0 programmes", "description": "Number of active programmes" }, { "field": "reportingRecipients", "source": "P0 governance", "description": "Who needs financial data" }, { "field": "updateFrequency", "source": "P2 reporting needs", "description": "Required report frequency" }, { "field": "accountingSystem", "source": "P0 Q13", "description": "Current accounting systems" } ], "implementationComplexity": "medium", "examples": { "note": "NGO real-time financial dashboards", "references": [ { "name": "Disberse", "url": "https://www.nesta.org.uk/feature/new-radicals-2018/disberse/", "solved": "Traced international aid fund transfers reducing intermediary costs" }, { "name": "WFP Building Blocks", "url": "https://www.wfp.org/building-blocks", "solved": "Transferred cash to refugee populations at scale, fast and at low cost" } ] }, "solutionQuestions": [ { "id": "reporting-stakeholders", "type": "multiselect", "options": [ { "label": "Senior leadership / Board", "value": "leadership" }, { "label": "Country/programme directors", "value": "programme-directors" }, { "label": "Finance team", "value": "finance" }, { "label": "Donors (external)", "value": "donors" }, { "label": "Auditors", "value": "auditors" }, { "label": "Field staff", "value": "field-staff" } ], "propertyMapping": { "leadership": { "technologies": [ "Executive dashboard" ], "technologyProperties": { "accessControl": "Role-based view", "dataGranularity": "Summary/KPI level" } }, "programme-directors": { "technologies": [ "Programme-level dashboard" ], "technologyProperties": { "accessControl": "Programme-scoped access", "dataGranularity": "Programme detail" } }, "finance": { "technologies": [ "Full financial reporting suite" ], "technologyProperties": { "accessControl": "Full data access", "dataGranularity": "Transaction-level" } }, "donors": { "technologies": [ "Donor-facing portal" ], "technologyProperties": { "accessControl": "Donor-scoped read-only", "dataGranularity": "Donor-fund specific" } }, "auditors": { "technologies": [ "Audit trail explorer" ], "technologyProperties": { "accessControl": "Audit-scoped read-only", "dataGranularity": "Full transaction + metadata" } }, "field-staff": { "technologies": [ "Mobile-friendly reporting" ], "technologyProperties": { "accessControl": "Location-scoped access", "dataGranularity": "Field-office level" } } }, "prefillFrom": null, "briefSection": "Reporting and audit", "text": "Who needs access to real-time financial reports?", "ngoText": "Who needs access to real-time financial reports?" }, { "id": "reporting-dimensions", "type": "multiselect", "options": [ { "label": "By country/office", "value": "country" }, { "label": "By programme/project", "value": "programme" }, { "label": "By donor/grant", "value": "donor" }, { "label": "By cost category (staff, supplies, etc.)", "value": "cost-category" }, { "label": "By currency", "value": "currency" }, { "label": "By time period (with comparisons)", "value": "time-period" } ], "propertyMapping": { "country": { "technologies": [ "Multi-dimensional reporting engine" ], "technologyProperties": { "reportingDimension": "Geographic", "drillDown": "Country \u2192 office \u2192 team" } }, "programme": { "technologies": [ "Multi-dimensional reporting engine" ], "technologyProperties": { "reportingDimension": "Programmatic", "drillDown": "Programme \u2192 project \u2192 activity" } }, "donor": { "technologies": [ "Multi-dimensional reporting engine" ], "technologyProperties": { "reportingDimension": "Funding source", "drillDown": "Donor \u2192 grant \u2192 budget line" } }, "cost-category": { "technologies": [ "Multi-dimensional reporting engine" ], "technologyProperties": { "reportingDimension": "Cost classification", "drillDown": "Category \u2192 sub-category \u2192 line item" } }, "currency": { "technologies": [ "Multi-currency reporting engine" ], "technologyProperties": { "reportingDimension": "Currency", "drillDown": "Currency \u2192 transaction \u2192 FX rate" } }, "time-period": { "technologies": [ "Time-series reporting engine" ], "technologyProperties": { "reportingDimension": "Temporal", "drillDown": "Year \u2192 quarter \u2192 month \u2192 day" } } }, "prefillFrom": null, "briefSection": "Reporting and audit", "text": "What dimensions do you need to report across?", "ngoText": "What dimensions do you need to report across?" }, { "id": "data-sources", "type": "multiselect", "options": [ { "label": "Central ERP/accounting system", "value": "erp" }, { "label": "Country-level accounting systems", "value": "country-systems" }, { "label": "Bank statements", "value": "bank-statements" }, { "label": "Mobile money platforms", "value": "mobile-money" }, { "label": "Spreadsheets and manual records", "value": "spreadsheets" }, { "label": "Project management tools", "value": "pm-tools" } ], "propertyMapping": { "erp": { "technologies": [ "Accounting system data link" ], "technologyProperties": { "dataSource": "Central accounting system", "integrationMethod": "API sync" } }, "country-systems": { "technologies": [ "Multi-system data aggregator" ], "technologyProperties": { "dataSource": "Distributed country systems", "integrationMethod": "Multi-system connection" } }, "bank-statements": { "technologies": [ "Bank feed integration" ], "technologyProperties": { "dataSource": "Bank transaction feeds", "integrationMethod": "Open banking API or file import" } }, "mobile-money": { "technologies": [ "Mobile money API integration" ], "technologyProperties": { "dataSource": "MNO platforms", "integrationMethod": "MNO API" } }, "spreadsheets": { "technologies": [ "Spreadsheet import engine" ], "technologyProperties": { "dataSource": "Manual spreadsheets", "integrationMethod": "CSV/spreadsheet import with validation" } }, "pm-tools": { "technologies": [ "PM tool integration" ], "technologyProperties": { "dataSource": "Project management platforms", "integrationMethod": "System connection" } } }, "prefillFrom": "P0-S3-Q13", "briefSection": "Integration requirements", "text": "Where does financial data currently live that needs to be consolidated?", "ngoText": "Where does financial data currently live that needs to be consolidated?" }, { "id": "reporting-latency", "type": "select", "options": [ { "label": "Real-time, within seconds of a transaction", "value": "realtime" }, { "label": "Near real-time, within an hour", "value": "near-realtime" }, { "label": "Same-day: end of day reporting is fine", "value": "same-day" }, { "label": "Next-day is acceptable", "value": "next-day" } ], "propertyMapping": { "realtime": { "technologies": [ "Real-time event streaming", "Live dashboard" ], "technologyProperties": { "dataLatency": "Seconds", "updateMechanism": "Event-driven streaming" } }, "near-realtime": { "technologies": [ "Near real-time data updates" ], "technologyProperties": { "dataLatency": "Under 1 hour", "updateMechanism": "Micro-batch settlement" } }, "same-day": { "technologies": [ "Daily data consolidation" ], "technologyProperties": { "dataLatency": "Same day", "updateMechanism": "Scheduled batch" } }, "next-day": { "technologies": [ "Overnight batch processing" ], "technologyProperties": { "dataLatency": "T+1", "updateMechanism": "Overnight batch" } } }, "prefillFrom": null, "briefSection": "Infrastructure requirements", "text": "How close to real-time does reporting need to be?", "ngoText": "How close to real-time does reporting need to be?" }, { "id": "data-privacy-reporting", "type": "select", "options": [ { "label": "Yes, strict separation needed between sensitive and general data", "value": "strict" }, { "label": "Some, certain fields need masking for some audiences", "value": "moderate" }, { "label": "Minimal: all financial data can be seen by authorised users", "value": "minimal" }, { "label": "Nice to have, not a current requirement but would be beneficial if available", "value": "nice-to-have" } ], "propertyMapping": { "strict": { "technologies": [ "Data privacy layer", "Field-level encryption", "Role-based data masking" ], "technologyProperties": { "privacyLevel": "Strict field-level access control", "dataProtection": "Encrypted at rest and in transit with selective disclosure" } }, "moderate": { "technologies": [ "Role-based data masking" ], "technologyProperties": { "privacyLevel": "Audience-specific field masking", "dataProtection": "Standard encryption with role-based visibility" } }, "minimal": { "technologies": [], "technologyProperties": { "privacyLevel": "Standard access control", "dataProtection": "Standard encryption" } }, "nice-to-have": { "technologies": [], "technologyProperties": { "privacyLevel": "Optional \u2014 not required but desirable", "dataProtection": "Basic encryption sufficient" } } }, "prefillFrom": null, "briefSection": "Identity and compliance", "text": "Are there data privacy constraints on financial reporting (e.g., staff salaries, beneficiary payments)?", "ngoText": "Are there data privacy constraints on financial reporting (e.g., staff salaries, beneficiary payments)?" }, { "id": "sq-UC-A-008-001", "type": "single-select", "options": [ { "value": "programme-level-only", "label": "Programme level only" }, { "value": "activity-level", "label": "Activity/project level" }, { "value": "transaction-level", "label": "Transaction level" }, { "value": "line-item", "label": "Line-item detail" }, { "value": "full-audit-trail", "label": "Full audit trail" } ], "propertyMapping": { "programme-level-only": { "technologies": [ "aggregation-engine", "programme-rollup" ], "technologyProperties": {} }, "activity-level": { "technologies": [ "activity-tracking", "hierarchical-reporting" ], "technologyProperties": {} }, "transaction-level": { "technologies": [ "transaction-logging", "transaction-drilldown" ], "technologyProperties": {} }, "line-item": { "technologies": [ "line-item-tracking", "detailed-reporting" ], "technologyProperties": {} }, "full-audit-trail": { "technologies": [ "audit-logging", "full-event-history" ], "technologyProperties": {} } }, "briefSection": "user-experience", "text": "What drill-down depth should reports support?", "ngoText": "What drill-down depth should reports support?" } ], "complexityFactors": { "relationships": 2, "operationalChange": 2, "dataCompliance": 1 }, "suggestedCriteria": [ { "id": "SC-REALTIME-DASH", "name": "Real-Time Dashboard & Visualisation", "description": "The provider offers a real-time dashboard showing financial status across all programmes and country offices. Leadership needs to see consolidated spend, burn rate, and budget status instantly.", "weight": 0.3, "ratingGuide": { "5": "Real-time dashboard with programme/country/fund drill-down. Burn rate projections. Budget vs actual. Mobile-accessible. Customisable views per role.", "4": "Near-real-time (hourly updates). Good drill-down. Budget tracking. Desktop dashboard.", "3": "Daily-updated dashboard. Programme-level views. Basic budget comparison.", "2": "Weekly reporting. Limited visualisation. Manual refresh required.", "1": "No dashboard. Reports generated on request only." } }, { "id": "SC-DATA-AGG", "name": "Multi-Source Data Aggregation", "description": "The provider can pull financial data from multiple country offices, accounting systems, and bank accounts into a single view. Most NGOs don't have a single accounting system across all offices.", "weight": 0.25, "ratingGuide": { "5": "API connectors for 10+ accounting platforms and bank feeds. Automated aggregation. Currency normalisation. Data quality checks.", "4": "Connectors for major accounting platforms. Good aggregation with automatic currency conversion.", "3": "CSV import from multiple sources. Semi-automated aggregation. Manual currency conversion.", "2": "Manual data entry or single-source integration only. Limited aggregation.", "1": "Single source only. No multi-system aggregation capability." } }, { "id": "SC-REPORT-FLEX", "name": "Report Customisation & Distribution", "description": "Different stakeholders can get different report views. Country directors need local detail, donors need grant-specific views, and the board needs strategic summaries.", "weight": 0.2, "ratingGuide": { "5": "Role-based report builder. Scheduled automated distribution. Self-service for programme managers. Multiple formats (PDF, spreadsheet, interactive).", "4": "Good customisation. Scheduled distribution. 3-4 pre-built role views.", "3": "Configurable reports with filters. Manual distribution. Standard export formats.", "2": "Fixed report formats. Manual customisation via export/edit. Email distribution.", "1": "Single report format. No customisation. Manual retrieval." } }, { "id": "SC-BUDGET-TRACK", "name": "Budget Monitoring & Alerts", "description": "The provider supports budget tracking with automated alerts. Overspending or underspending on a grant line can have serious consequences for donor relationships.", "weight": 0.15, "ratingGuide": { "5": "Per-grant budget lines with real-time tracking. Automated alerts at 75%/90%/100% thresholds. Burn rate projections. Underspend warnings.", "4": "Budget tracking with alerts at key thresholds. Good burn rate visibility.", "3": "Budget vs actual comparison. Manual threshold monitoring. Basic projections.", "2": "Budget entry supported but no automated monitoring. Manual comparison required.", "1": "No budget tracking. Actuals only." } }, { "id": "SC-DATA-INTEGRITY", "name": "Data Integrity & Tamper Evidence", "description": "The provider can guarantee that reported numbers haven't been altered. For financial transparency, stakeholders need confidence that the data they see is authentic and unmodified.", "weight": 0.1, "ratingGuide": { "5": "Blockchain-anchored data integrity. Cryptographic proof of unaltered records. Independent verification possible. Full audit log of any changes.", "4": "Tamper-evident records. Change log with timestamps and user attribution. Good verification.", "3": "Access-controlled with change tracking. Standard database integrity measures.", "2": "Basic access controls. Limited change tracking. Standard database security.", "1": "No tamper protection. Data can be modified without trace." } } ], "procurement": { "marketMaturity": "mature", "primaryMode": "off-the-shelf", "alternativeModes": [ "rfq" ], "reasoning": "Real-time financial reporting baked into modern accounting SaaS.", "exampleProductCategories": [ "cloud-accounting-saas", "financial-reporting-platform" ], "partnerChannels": [], "lastReviewed": "2026-05-01" } }, { "id": "UC-A-009", "name": "Automated compliance reporting to donors", "category": "A", "subcategory": "Compliance and Reporting", "description": "Check spending against each donor's grant conditions as it happens, and produce the compliance report from that record instead of building it by hand.", "bCriteria": [ "B3", "B7" ], "requiredComponents": [ { "component": "smart-contracts", "description": "Rule-based compliance automation" }, { "component": "reporting-module", "description": "Automated report generation" }, { "component": "accounting-integration", "description": "Financial data integration" }, { "component": "audit-mechanism", "description": "Compliance audit trail" } ], "conditionalComponents": [ { "component": "identity-verification", "condition": "If beneficiary data reporting required", "linksTo": "UC-B-024" } ], "crossCategoryDependencies": [ "UC-C-048 if audit compliance needed" ], "p2TriggerConditions": { "description": "Activated when P2 shows multiple donor requirements + complex compliance rules + reporting burden", "rangeSignals": [ "donors >= 3", "complianceFrameworks >= 2", "reportingTime >= 1 week" ] }, "contextFieldsTemplate": [ { "field": "donorRequirements", "source": "P0 donor agreements", "description": "Specific compliance requirements" }, { "field": "reportingFrequency", "source": "P0 grants", "description": "Required reporting frequency" }, { "field": "dataElements", "source": "P2 donor requests", "description": "Data required in reports" } ], "implementationComplexity": "medium", "examples": { "note": "Donor accountability frameworks", "references": [ { "name": "Disberse", "url": "https://www.nesta.org.uk/feature/new-radicals-2018/disberse/", "solved": "Traced international aid fund transfers reducing intermediary costs" }, { "name": "UNICEF CryptoFund", "url": "https://www.unicef.org/innovation/stories/unicef-cryptofund", "solved": "Funded global tech startups addressing child welfare, transparently and at low cost" } ] }, "solutionQuestions": [ { "id": "donor-compliance-types", "type": "multiselect", "options": [ { "label": "Financial utilisation reports (spend vs budget)", "value": "utilisation" }, { "label": "Activity/output reports linked to spend", "value": "activity-output" }, { "label": "Sanctions screening compliance certificates", "value": "sanctions-cert" }, { "label": "Anti-fraud and anti-corruption attestations", "value": "anti-fraud" }, { "label": "Beneficiary verification reports", "value": "beneficiary-verification" }, { "label": "Audit-ready transaction logs", "value": "audit-logs" } ], "propertyMapping": { "utilisation": { "technologies": [ "Automated budget-vs-actual reporting", "Smart contract budget enforcement" ], "technologyProperties": { "complianceType": "Financial utilisation", "automationLevel": "Auto-generated from ledger data" } }, "activity-output": { "technologies": [ "Activity-cost linking engine", "Reporting module" ], "technologyProperties": { "complianceType": "Activity-linked expenditure", "automationLevel": "Semi-automated with activity data input" } }, "sanctions-cert": { "technologies": [ "Automated sanctions screening log", "Certificate generation" ], "technologyProperties": { "complianceType": "Sanctions compliance certificate", "automationLevel": "Fully automated from screening records" } }, "anti-fraud": { "technologies": [ "Anomaly detection engine", "Attestation workflow" ], "technologyProperties": { "complianceType": "Anti-fraud attestation", "automationLevel": "Automated detection + manual attestation" } }, "beneficiary-verification": { "technologies": [ "Beneficiary registry", "Verification audit trail" ], "technologyProperties": { "complianceType": "Beneficiary verification", "automationLevel": "Automated from registration records" } }, "audit-logs": { "technologies": [ "Immutable audit trail", "Transaction explorer" ], "technologyProperties": { "complianceType": "Transaction-level audit log", "automationLevel": "Fully automated \u2014 blockchain-native" } } }, "prefillFrom": null, "briefSection": "Reporting and audit", "text": "What types of compliance reports do your donors require?", "ngoText": "What types of compliance reports do your donors require?" }, { "id": "reporting-frequency-compliance", "type": "select", "options": [ { "label": "Monthly", "value": "monthly" }, { "label": "Quarterly", "value": "quarterly" }, { "label": "Annually", "value": "annually" }, { "label": "On-demand / ad-hoc", "value": "on-demand" }, { "label": "Varies by donor: multiple schedules", "value": "varies" } ], "propertyMapping": { "monthly": { "technologies": [ "Automated monthly report scheduler" ], "technologyProperties": { "reportingCadence": "Monthly automated", "leadTime": "Auto-generated by month-end" } }, "quarterly": { "technologies": [ "Automated quarterly report scheduler" ], "technologyProperties": { "reportingCadence": "Quarterly automated", "leadTime": "Auto-generated by quarter-end" } }, "annually": { "technologies": [ "Annual report generation" ], "technologyProperties": { "reportingCadence": "Annual", "leadTime": "Auto-generated with review period" } }, "on-demand": { "technologies": [ "On-demand report generation" ], "technologyProperties": { "reportingCadence": "On-demand", "leadTime": "Instant generation" } }, "varies": { "technologies": [ "Multi-schedule report engine" ], "technologyProperties": { "reportingCadence": "Per-donor configurable", "leadTime": "Automated per schedule" } } }, "prefillFrom": null, "briefSection": "Reporting and audit", "text": "How frequently are compliance reports due?", "ngoText": "How frequently are compliance reports due?" }, { "id": "compliance-rules-complexity", "type": "select", "options": [ { "label": "Simple: similar rules across all donors", "value": "simple" }, { "label": "Moderate: each donor has some specific requirements", "value": "moderate" }, { "label": "Complex: significantly different rules per donor", "value": "complex" }, { "label": "Very complex: overlapping and sometimes conflicting rules", "value": "very-complex" } ], "propertyMapping": { "simple": { "technologies": [ "Standard compliance rule engine" ], "technologyProperties": { "ruleEngine": "Template-based", "configComplexity": "Low" } }, "moderate": { "technologies": [ "Configurable compliance rule engine" ], "technologyProperties": { "ruleEngine": "Per-donor configurable", "configComplexity": "Medium" } }, "complex": { "technologies": [ "Advanced compliance rule engine", "Per-donor policy definitions" ], "technologyProperties": { "ruleEngine": "Multi-donor rule library", "configComplexity": "High" } }, "very-complex": { "technologies": [ "Enterprise compliance rule engine", "Rule conflict resolution", "Policy intersection analyser" ], "technologyProperties": { "ruleEngine": "Multi-donor with conflict detection", "configComplexity": "Very high \u2014 automated conflict resolution" } } }, "prefillFrom": null, "briefSection": "Payment logic", "text": "How complex are the compliance rules across your donor portfolio?", "ngoText": "How complex are the compliance rules across your donor portfolio?" }, { "id": "compliance-staff-time", "type": "select", "options": [ { "label": "Under 1 day/month", "value": "minimal" }, { "label": "1-5 days/month", "value": "moderate" }, { "label": "1-2 weeks/month", "value": "significant" }, { "label": "Over 2 weeks/month (near full-time)", "value": "major" } ], "propertyMapping": { "minimal": { "technologies": [], "technologyProperties": { "automationPriority": "Low", "expectedTimeSaving": "Marginal" } }, "moderate": { "technologies": [ "Semi-automated compliance reporting" ], "technologyProperties": { "automationPriority": "Medium", "expectedTimeSaving": "50-70% reduction" } }, "significant": { "technologies": [ "Automated compliance reporting suite" ], "technologyProperties": { "automationPriority": "High", "expectedTimeSaving": "70-85% reduction" } }, "major": { "technologies": [ "Fully automated compliance suite", "AI-assisted report generation" ], "technologyProperties": { "automationPriority": "Critical", "expectedTimeSaving": "85%+ reduction" } } }, "prefillFrom": null, "briefSection": "Current state", "text": "How much staff time is currently spent on compliance reporting per month?", "ngoText": "How much staff time is currently spent on compliance reporting per month?" }, { "id": "sq-UC-A-009-001", "type": "single-select", "options": [ { "value": "auto-flag-manager", "label": "Auto-flag to manager" }, { "value": "block-transaction", "label": "Block transaction immediately" }, { "value": "queue-for-review", "label": "Queue for compliance review" }, { "value": "notify-donor", "label": "Notify donor automatically" }, { "value": "multi-step-escalation", "label": "Multi-step escalation matrix" } ], "propertyMapping": { "auto-flag-manager": { "technologies": [ "notification-system", "manager-dashboard" ], "technologyProperties": {} }, "block-transaction": { "technologies": [ "transaction-blocking", "immediate-halt" ], "technologyProperties": {} }, "queue-for-review": { "technologies": [ "review-queue", "workflow-engine" ], "technologyProperties": {} }, "notify-donor": { "technologies": [ "donor-notification", "automated-alerts" ], "technologyProperties": {} }, "multi-step-escalation": { "technologies": [ "escalation-rules", "routing-engine" ], "technologyProperties": {} } }, "briefSection": "operations", "text": "What process do you currently have for escalating compliance exceptions when detected?", "ngoText": "What process do you currently have for escalating compliance exceptions when detected?" }, { "id": "accounting-integration", "type": "select", "options": [ { "label": "Direct integration with your existing accounting software", "value": "direct-erp" }, { "label": "Export-based: generate reports compatible with our accounting system", "value": "export-based" }, { "label": "Standalone ledger with manual reconciliation", "value": "standalone" }, { "label": "Not sure, need guidance on accounting integration", "value": "guidance-needed" } ], "propertyMapping": { "direct-erp": { "technologies": [ "Accounting system connection", "Automatic record updates", "Account structure alignment" ], "technologyProperties": { "integrationMethod": "Real-time connection", "reconciliation": "Automated", "reportFormat": "Compatible with your accounting system" } }, "export-based": { "technologies": [ "Accounting export module", "Report generation engine", "CSV/spreadsheet export service" ], "technologyProperties": { "integrationMethod": "Scheduled export (CSV/spreadsheet)", "reconciliation": "Semi-automated", "reportFormat": "Standard CSV/spreadsheet" } }, "standalone": { "technologies": [ "Standalone accounting ledger", "Manual reconciliation tools" ], "technologyProperties": { "integrationMethod": "Manual import/export", "reconciliation": "Manual", "reportFormat": "PDF/spreadsheet reports" } }, "guidance-needed": { "technologies": [ "Accounting integration framework" ], "technologyProperties": { "integrationMethod": "To be determined", "reconciliation": "To be determined", "reportFormat": "To be determined" } } }, "prefillFrom": null, "briefSection": "Financial integration", "text": "How should this solution integrate with your existing accounting or financial systems?", "ngoText": "How should this solution integrate with your existing accounting or financial systems?" } ], "complexityFactors": { "relationships": 2, "operationalChange": 2, "dataCompliance": 2 }, "suggestedCriteria": [ { "id": "SC-DONOR-TEMPLATE", "name": "Donor Template Library", "description": "The provider has pre-built reporting templates for major institutional donors. Each donor (USAID, EU, DFID/FCDO, SIDA, GIZ) has specific formats, timelines, and categorisation requirements.", "weight": 0.3, "ratingGuide": { "5": "Pre-built templates for 10+ major institutional donors. Automatic format adaptation. Template updates when donor requirements change.", "4": "Templates for 5-10 major donors. Good format compliance. Manual updates for requirement changes.", "3": "Templates for 3-5 donors. Customisable for others. Good general framework.", "2": "Generic template with manual adaptation for each donor. Limited pre-built options.", "1": "No donor-specific templates. All formatting manual." } }, { "id": "SC-AUTO-SCHEDULE", "name": "Automated Report Scheduling & Generation", "description": "Reports can be generated and distributed automatically on donor deadlines. Missing a donor reporting deadline can trigger grant suspension.", "weight": 0.25, "ratingGuide": { "5": "Scheduled generation per donor calendar. Automated distribution. Pre-deadline review workflow. Deadline tracking dashboard.", "4": "Scheduled generation. Email distribution. Advance reminders for review.", "3": "Scheduled generation. Manual distribution. Basic deadline tracking.", "2": "On-demand generation. Manual scheduling and distribution.", "1": "Manual report creation for each deadline. No automation." } }, { "id": "SC-DATA-MAPPING", "name": "Chart of Accounts Mapping", "description": "The provider can map the organisation's chart of accounts to different donor budget categories. Each donor uses different cost classifications. The same expense may be coded differently for different reports.", "weight": 0.2, "ratingGuide": { "5": "Multi-donor chart mapping. One transaction auto-categorised across multiple donor views. Mapping version control.", "4": "Good multi-mapping. Automatic categorisation for mapped donors. Manual for unmapped.", "3": "Per-donor mapping configuration. Semi-automatic categorisation.", "2": "Single mapping. Manual recategorisation for different donors.", "1": "No mapping capability. Manual recoding for each report." } }, { "id": "SC-VARIANCE-EXPLAIN", "name": "Variance Analysis & Narrative Support", "description": "The provider helps explain budget variances. Donors require narrative explanations for significant deviations from approved budgets: automating the identification speeds the process.", "weight": 0.15, "ratingGuide": { "5": "Automatic variance flagging with severity levels. Pre-drafted narrative suggestions based on transaction patterns. Historical variance comparison.", "4": "Automatic variance flagging. Structured input for narratives. Good historical data.", "3": "Variance calculations provided. Manual narrative writing. Basic historical comparison.", "2": "Budget vs actual numbers. Manual variance identification and explanation.", "1": "Raw numbers only. All variance analysis done externally." } }, { "id": "SC-EVIDENCE-ATTACH", "name": "Supporting Evidence Attachment", "description": "Supporting documents (receipts, contracts, photos) can be attached to transactions for donor review. Many donors require evidence packages with compliance reports.", "weight": 0.1, "ratingGuide": { "5": "Document attachment per transaction. Organised evidence packages auto-generated. Supports photos, PDFs, contracts. Version tracking.", "4": "Document attachment available. Good organisation. Standard file types.", "3": "File attachment to transactions. Manual organisation for evidence packages.", "2": "Separate document storage with manual linking to transactions.", "1": "No document attachment. Evidence managed entirely outside the system." } } ], "procurement": { "marketMaturity": "emerging", "primaryMode": "rfq", "alternativeModes": [ "off-the-shelf" ], "reasoning": "Compliance reporting platforms exist; donor-specific configuration needed.", "exampleProductCategories": [ "donor-compliance-reporting", "grants-management-platform" ], "partnerChannels": [], "lastReviewed": "2026-05-01" } }, { "id": "UC-A-010", "name": "Petty cash and field office expense management", "category": "A", "subcategory": "Internal Fund Movement", "description": "Track small cash spending in field offices in one shared record, so receipts and balances match without long reconciliation.", "bCriteria": [ "B1", "B3" ], "requiredComponents": [ { "component": "payment-rails", "description": "Small transaction settlement" }, { "component": "stablecoin", "description": "Digital petty cash" }, { "component": "accounting-integration", "description": "Expense tracking integration" }, { "component": "mobile-wallet", "description": "Mobile-friendly expense wallet" } ], "conditionalComponents": [ { "component": "offline-sync", "condition": "If field offices lack consistent connectivity" } ], "crossCategoryDependencies": [], "p2TriggerConditions": { "description": "Activated when P2 shows remote field offices + cash-based operations + low connectivity", "rangeSignals": [ "fieldOffices >= 2", "paymentMethod = cash", "connectivity = low-intermittent" ] }, "contextFieldsTemplate": [ { "field": "fieldOfficeCount", "source": "P0 operations", "description": "Number of field offices" }, { "field": "staffPerOffice", "source": "P0 staffing", "description": "Staff managing petty cash" }, { "field": "expenseVolume", "source": "P2 expense patterns", "description": "Monthly expense transactions" }, { "field": "connectivity", "source": "P4", "description": "Field office internet connectivity" } ], "implementationComplexity": "low-medium", "examples": { "note": "Field office cash management", "references": [ { "name": "AID:Tech", "url": "https://hedera.com/users/aid-tech", "solved": "Distributed aid to refugees using digital identity, transparently and verifiably" }, { "name": "Mercy Corps", "url": "https://www.mercycorps.org/blog/digital-cash-supports-farmers-rebuilding", "solved": "Delivered digital cash aid fast to farmers in conflict-affected zones" } ] }, "solutionQuestions": [ { "id": "corridor-count", "type": "select", "options": [ { "label": "Single country", "value": "single" }, { "label": "2\u20133 countries", "value": "2-3" }, { "label": "4\u20135 countries", "value": "4-5" }, { "label": "More than 5 countries", "value": "5-plus" } ], "propertyMapping": { "single": { "technologies": [ "Single-corridor fiat on-ramp" ], "technologyProperties": { "corridorComplexity": "Single origination country", "multiRailNeeded": "No" } }, "2-3": { "technologies": [ "Multi-corridor fiat on-ramp gateway" ], "technologyProperties": { "corridorComplexity": "2\u20133 origination countries", "multiRailNeeded": "Yes \u2014 2-3 payment rails" } }, "4-5": { "technologies": [ "Multi-corridor fiat on-ramp gateway" ], "technologyProperties": { "corridorComplexity": "4\u20135 origination countries", "multiRailNeeded": "Yes \u2014 4-5 payment rails" } }, "5-plus": { "technologies": [ "Enterprise multi-corridor on-ramp gateway" ], "technologyProperties": { "corridorComplexity": "5+ origination countries", "multiRailNeeded": "Yes \u2014 enterprise-grade multi-rail" } } }, "prefillFrom": null, "briefSection": "Payment rail requirements", "text": "How many countries does your organisation send transfer funds from?", "ngoText": "How many countries does your organisation send transfer funds from?" }, { "id": "origination-country-1", "type": "select", "options": [ { "label": "United States", "value": "united-states" }, { "label": "United Kingdom", "value": "united-kingdom" }, { "label": "Germany", "value": "germany" }, { "label": "Netherlands", "value": "netherlands" }, { "label": "Switzerland", "value": "switzerland" }, { "label": "Belgium", "value": "belgium" }, { "label": "France", "value": "france" }, { "label": "Sweden", "value": "sweden" }, { "label": "Norway", "value": "norway" }, { "label": "Denmark", "value": "denmark" }, { "label": "Canada", "value": "canada" }, { "label": "Australia", "value": "australia" }, { "label": "Japan", "value": "japan" }, { "label": "Ireland", "value": "ireland" }, { "label": "Italy", "value": "italy" }, { "label": "Spain", "value": "spain" }, { "label": "Austria", "value": "austria" }, { "label": "Finland", "value": "finland" }, { "label": "Luxembourg", "value": "luxembourg" }, { "label": "South Korea", "value": "south-korea" }, { "label": "New Zealand", "value": "new-zealand" }, { "label": "United Arab Emirates", "value": "united-arab-emirates" }, { "label": "Singapore", "value": "singapore" }, { "label": "Other", "value": "other" } ], "propertyMapping": { "united-states": { "technologies": [ "ACH/wire fiat on-ramp" ], "technologyProperties": { "onRampType": "ACH/Fedwire bank transfer", "onRampRegion": "United States", "settlementRail": "ACH / Fedwire" } }, "united-kingdom": { "technologies": [ "UK Faster Payments on-ramp" ], "technologyProperties": { "onRampType": "Faster Payments bank transfer", "onRampRegion": "United Kingdom", "settlementRail": "FPS / BACS" } }, "germany": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "netherlands": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "switzerland": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SIC/SEPA bank transfer", "onRampRegion": "Switzerland/EU", "settlementRail": "SIC / SEPA Credit Transfer" } }, "belgium": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "france": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "sweden": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "norway": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA-adjacent bank transfer", "onRampRegion": "EEA", "settlementRail": "SEPA Credit Transfer" } }, "denmark": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "canada": { "technologies": [ "Canadian EFT on-ramp" ], "technologyProperties": { "onRampType": "Interac/EFT bank transfer", "onRampRegion": "Canada", "settlementRail": "Interac / EFT" } }, "australia": { "technologies": [ "Australian NPP on-ramp" ], "technologyProperties": { "onRampType": "NPP bank transfer", "onRampRegion": "Australia", "settlementRail": "NPP / BECS" } }, "japan": { "technologies": [ "Japanese Zengin on-ramp" ], "technologyProperties": { "onRampType": "Zengin bank transfer", "onRampRegion": "Japan", "settlementRail": "Zengin System" } }, "ireland": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "italy": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "spain": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "austria": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "finland": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "luxembourg": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "south-korea": { "technologies": [ "Korean banking on-ramp" ], "technologyProperties": { "onRampType": "KFTC bank transfer", "onRampRegion": "South Korea", "settlementRail": "KFTC / BOK-Wire" } }, "new-zealand": { "technologies": [ "NZ banking on-ramp" ], "technologyProperties": { "onRampType": "SBI bank transfer", "onRampRegion": "New Zealand", "settlementRail": "SBI / ESAS" } }, "united-arab-emirates": { "technologies": [ "UAE banking on-ramp" ], "technologyProperties": { "onRampType": "UAEFTS bank transfer", "onRampRegion": "United Arab Emirates", "settlementRail": "UAEFTS / IPP" } }, "singapore": { "technologies": [ "Singapore FAST on-ramp" ], "technologyProperties": { "onRampType": "FAST bank transfer", "onRampRegion": "Singapore", "settlementRail": "FAST / MEPS+" } }, "other": { "technologies": [ "Regional fiat on-ramp" ], "technologyProperties": { "onRampType": "Local rail bank transfer", "onRampRegion": "Region-specific", "settlementRail": "Local payment network" } } }, "showIf": { "questionId": "corridor-count", "minValue": "single" }, "prefillFrom": null, "briefSection": "Payment rail requirements", "text": "Which country do you most frequently initiate transfers from?", "ngoText": "Which country do you most frequently initiate transfers from?" }, { "id": "origination-country-2", "type": "select", "options": [ { "label": "United States", "value": "united-states" }, { "label": "United Kingdom", "value": "united-kingdom" }, { "label": "Germany", "value": "germany" }, { "label": "Netherlands", "value": "netherlands" }, { "label": "Switzerland", "value": "switzerland" }, { "label": "Belgium", "value": "belgium" }, { "label": "France", "value": "france" }, { "label": "Sweden", "value": "sweden" }, { "label": "Norway", "value": "norway" }, { "label": "Denmark", "value": "denmark" }, { "label": "Canada", "value": "canada" }, { "label": "Australia", "value": "australia" }, { "label": "Japan", "value": "japan" }, { "label": "Ireland", "value": "ireland" }, { "label": "Italy", "value": "italy" }, { "label": "Spain", "value": "spain" }, { "label": "Austria", "value": "austria" }, { "label": "Finland", "value": "finland" }, { "label": "Luxembourg", "value": "luxembourg" }, { "label": "South Korea", "value": "south-korea" }, { "label": "New Zealand", "value": "new-zealand" }, { "label": "United Arab Emirates", "value": "united-arab-emirates" }, { "label": "Singapore", "value": "singapore" }, { "label": "Other", "value": "other" } ], "propertyMapping": { "united-states": { "technologies": [ "ACH/wire fiat on-ramp" ], "technologyProperties": { "onRampType": "ACH/Fedwire bank transfer", "onRampRegion": "United States", "settlementRail": "ACH / Fedwire" } }, "united-kingdom": { "technologies": [ "UK Faster Payments on-ramp" ], "technologyProperties": { "onRampType": "Faster Payments bank transfer", "onRampRegion": "United Kingdom", "settlementRail": "FPS / BACS" } }, "germany": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "netherlands": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "switzerland": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SIC/SEPA bank transfer", "onRampRegion": "Switzerland/EU", "settlementRail": "SIC / SEPA Credit Transfer" } }, "belgium": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "france": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "sweden": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "norway": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA-adjacent bank transfer", "onRampRegion": "EEA", "settlementRail": "SEPA Credit Transfer" } }, "denmark": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "canada": { "technologies": [ "Canadian EFT on-ramp" ], "technologyProperties": { "onRampType": "Interac/EFT bank transfer", "onRampRegion": "Canada", "settlementRail": "Interac / EFT" } }, "australia": { "technologies": [ "Australian NPP on-ramp" ], "technologyProperties": { "onRampType": "NPP bank transfer", "onRampRegion": "Australia", "settlementRail": "NPP / BECS" } }, "japan": { "technologies": [ "Japanese Zengin on-ramp" ], "technologyProperties": { "onRampType": "Zengin bank transfer", "onRampRegion": "Japan", "settlementRail": "Zengin System" } }, "ireland": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "italy": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "spain": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "austria": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "finland": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "luxembourg": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "south-korea": { "technologies": [ "Korean banking on-ramp" ], "technologyProperties": { "onRampType": "KFTC bank transfer", "onRampRegion": "South Korea", "settlementRail": "KFTC / BOK-Wire" } }, "new-zealand": { "technologies": [ "NZ banking on-ramp" ], "technologyProperties": { "onRampType": "SBI bank transfer", "onRampRegion": "New Zealand", "settlementRail": "SBI / ESAS" } }, "united-arab-emirates": { "technologies": [ "UAE banking on-ramp" ], "technologyProperties": { "onRampType": "UAEFTS bank transfer", "onRampRegion": "United Arab Emirates", "settlementRail": "UAEFTS / IPP" } }, "singapore": { "technologies": [ "Singapore FAST on-ramp" ], "technologyProperties": { "onRampType": "FAST bank transfer", "onRampRegion": "Singapore", "settlementRail": "FAST / MEPS+" } }, "other": { "technologies": [ "Regional fiat on-ramp" ], "technologyProperties": { "onRampType": "Local rail bank transfer", "onRampRegion": "Region-specific", "settlementRail": "Local payment network" } } }, "showIf": { "questionId": "corridor-count", "minValue": "2-3" }, "prefillFrom": null, "briefSection": "Payment rail requirements", "text": "Second most common transfer origination country (if applicable)", "ngoText": "Second most common transfer origination country (if applicable)" }, { "id": "origination-country-3", "type": "select", "options": [ { "label": "United States", "value": "united-states" }, { "label": "United Kingdom", "value": "united-kingdom" }, { "label": "Germany", "value": "germany" }, { "label": "Netherlands", "value": "netherlands" }, { "label": "Switzerland", "value": "switzerland" }, { "label": "Belgium", "value": "belgium" }, { "label": "France", "value": "france" }, { "label": "Sweden", "value": "sweden" }, { "label": "Norway", "value": "norway" }, { "label": "Denmark", "value": "denmark" }, { "label": "Canada", "value": "canada" }, { "label": "Australia", "value": "australia" }, { "label": "Japan", "value": "japan" }, { "label": "Ireland", "value": "ireland" }, { "label": "Italy", "value": "italy" }, { "label": "Spain", "value": "spain" }, { "label": "Austria", "value": "austria" }, { "label": "Finland", "value": "finland" }, { "label": "Luxembourg", "value": "luxembourg" }, { "label": "South Korea", "value": "south-korea" }, { "label": "New Zealand", "value": "new-zealand" }, { "label": "United Arab Emirates", "value": "united-arab-emirates" }, { "label": "Singapore", "value": "singapore" }, { "label": "Other", "value": "other" } ], "propertyMapping": { "united-states": { "technologies": [ "ACH/wire fiat on-ramp" ], "technologyProperties": { "onRampType": "ACH/Fedwire bank transfer", "onRampRegion": "United States", "settlementRail": "ACH / Fedwire" } }, "united-kingdom": { "technologies": [ "UK Faster Payments on-ramp" ], "technologyProperties": { "onRampType": "Faster Payments bank transfer", "onRampRegion": "United Kingdom", "settlementRail": "FPS / BACS" } }, "germany": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "netherlands": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "switzerland": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SIC/SEPA bank transfer", "onRampRegion": "Switzerland/EU", "settlementRail": "SIC / SEPA Credit Transfer" } }, "belgium": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "france": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "sweden": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "norway": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA-adjacent bank transfer", "onRampRegion": "EEA", "settlementRail": "SEPA Credit Transfer" } }, "denmark": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "canada": { "technologies": [ "Canadian EFT on-ramp" ], "technologyProperties": { "onRampType": "Interac/EFT bank transfer", "onRampRegion": "Canada", "settlementRail": "Interac / EFT" } }, "australia": { "technologies": [ "Australian NPP on-ramp" ], "technologyProperties": { "onRampType": "NPP bank transfer", "onRampRegion": "Australia", "settlementRail": "NPP / BECS" } }, "japan": { "technologies": [ "Japanese Zengin on-ramp" ], "technologyProperties": { "onRampType": "Zengin bank transfer", "onRampRegion": "Japan", "settlementRail": "Zengin System" } }, "ireland": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "italy": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "spain": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "austria": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "finland": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "luxembourg": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "south-korea": { "technologies": [ "Korean banking on-ramp" ], "technologyProperties": { "onRampType": "KFTC bank transfer", "onRampRegion": "South Korea", "settlementRail": "KFTC / BOK-Wire" } }, "new-zealand": { "technologies": [ "NZ banking on-ramp" ], "technologyProperties": { "onRampType": "SBI bank transfer", "onRampRegion": "New Zealand", "settlementRail": "SBI / ESAS" } }, "united-arab-emirates": { "technologies": [ "UAE banking on-ramp" ], "technologyProperties": { "onRampType": "UAEFTS bank transfer", "onRampRegion": "United Arab Emirates", "settlementRail": "UAEFTS / IPP" } }, "singapore": { "technologies": [ "Singapore FAST on-ramp" ], "technologyProperties": { "onRampType": "FAST bank transfer", "onRampRegion": "Singapore", "settlementRail": "FAST / MEPS+" } }, "other": { "technologies": [ "Regional fiat on-ramp" ], "technologyProperties": { "onRampType": "Local rail bank transfer", "onRampRegion": "Region-specific", "settlementRail": "Local payment network" } } }, "showIf": { "questionId": "corridor-count", "minValue": "2-3" }, "prefillFrom": null, "briefSection": "Payment rail requirements", "text": "Third transfer origination country (if applicable)", "ngoText": "Third transfer origination country (if applicable)" }, { "id": "origination-country-4", "type": "select", "options": [ { "label": "United States", "value": "united-states" }, { "label": "United Kingdom", "value": "united-kingdom" }, { "label": "Germany", "value": "germany" }, { "label": "Netherlands", "value": "netherlands" }, { "label": "Switzerland", "value": "switzerland" }, { "label": "Belgium", "value": "belgium" }, { "label": "France", "value": "france" }, { "label": "Sweden", "value": "sweden" }, { "label": "Norway", "value": "norway" }, { "label": "Denmark", "value": "denmark" }, { "label": "Canada", "value": "canada" }, { "label": "Australia", "value": "australia" }, { "label": "Japan", "value": "japan" }, { "label": "Ireland", "value": "ireland" }, { "label": "Italy", "value": "italy" }, { "label": "Spain", "value": "spain" }, { "label": "Austria", "value": "austria" }, { "label": "Finland", "value": "finland" }, { "label": "Luxembourg", "value": "luxembourg" }, { "label": "South Korea", "value": "south-korea" }, { "label": "New Zealand", "value": "new-zealand" }, { "label": "United Arab Emirates", "value": "united-arab-emirates" }, { "label": "Singapore", "value": "singapore" }, { "label": "Other", "value": "other" } ], "propertyMapping": { "united-states": { "technologies": [ "ACH/wire fiat on-ramp" ], "technologyProperties": { "onRampType": "ACH/Fedwire bank transfer", "onRampRegion": "United States", "settlementRail": "ACH / Fedwire" } }, "united-kingdom": { "technologies": [ "UK Faster Payments on-ramp" ], "technologyProperties": { "onRampType": "Faster Payments bank transfer", "onRampRegion": "United Kingdom", "settlementRail": "FPS / BACS" } }, "germany": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "netherlands": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "switzerland": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SIC/SEPA bank transfer", "onRampRegion": "Switzerland/EU", "settlementRail": "SIC / SEPA Credit Transfer" } }, "belgium": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "france": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "sweden": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "norway": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA-adjacent bank transfer", "onRampRegion": "EEA", "settlementRail": "SEPA Credit Transfer" } }, "denmark": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "canada": { "technologies": [ "Canadian EFT on-ramp" ], "technologyProperties": { "onRampType": "Interac/EFT bank transfer", "onRampRegion": "Canada", "settlementRail": "Interac / EFT" } }, "australia": { "technologies": [ "Australian NPP on-ramp" ], "technologyProperties": { "onRampType": "NPP bank transfer", "onRampRegion": "Australia", "settlementRail": "NPP / BECS" } }, "japan": { "technologies": [ "Japanese Zengin on-ramp" ], "technologyProperties": { "onRampType": "Zengin bank transfer", "onRampRegion": "Japan", "settlementRail": "Zengin System" } }, "ireland": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "italy": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "spain": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "austria": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "finland": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "luxembourg": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "south-korea": { "technologies": [ "Korean banking on-ramp" ], "technologyProperties": { "onRampType": "KFTC bank transfer", "onRampRegion": "South Korea", "settlementRail": "KFTC / BOK-Wire" } }, "new-zealand": { "technologies": [ "NZ banking on-ramp" ], "technologyProperties": { "onRampType": "SBI bank transfer", "onRampRegion": "New Zealand", "settlementRail": "SBI / ESAS" } }, "united-arab-emirates": { "technologies": [ "UAE banking on-ramp" ], "technologyProperties": { "onRampType": "UAEFTS bank transfer", "onRampRegion": "United Arab Emirates", "settlementRail": "UAEFTS / IPP" } }, "singapore": { "technologies": [ "Singapore FAST on-ramp" ], "technologyProperties": { "onRampType": "FAST bank transfer", "onRampRegion": "Singapore", "settlementRail": "FAST / MEPS+" } }, "other": { "technologies": [ "Regional fiat on-ramp" ], "technologyProperties": { "onRampType": "Local rail bank transfer", "onRampRegion": "Region-specific", "settlementRail": "Local payment network" } } }, "showIf": { "questionId": "corridor-count", "minValue": "4-5" }, "prefillFrom": null, "briefSection": "Payment rail requirements", "text": "Fourth transfer origination country (if applicable)", "ngoText": "Fourth transfer origination country (if applicable)" }, { "id": "origination-country-5", "type": "select", "options": [ { "label": "United States", "value": "united-states" }, { "label": "United Kingdom", "value": "united-kingdom" }, { "label": "Germany", "value": "germany" }, { "label": "Netherlands", "value": "netherlands" }, { "label": "Switzerland", "value": "switzerland" }, { "label": "Belgium", "value": "belgium" }, { "label": "France", "value": "france" }, { "label": "Sweden", "value": "sweden" }, { "label": "Norway", "value": "norway" }, { "label": "Denmark", "value": "denmark" }, { "label": "Canada", "value": "canada" }, { "label": "Australia", "value": "australia" }, { "label": "Japan", "value": "japan" }, { "label": "Ireland", "value": "ireland" }, { "label": "Italy", "value": "italy" }, { "label": "Spain", "value": "spain" }, { "label": "Austria", "value": "austria" }, { "label": "Finland", "value": "finland" }, { "label": "Luxembourg", "value": "luxembourg" }, { "label": "South Korea", "value": "south-korea" }, { "label": "New Zealand", "value": "new-zealand" }, { "label": "United Arab Emirates", "value": "united-arab-emirates" }, { "label": "Singapore", "value": "singapore" }, { "label": "Other", "value": "other" } ], "propertyMapping": { "united-states": { "technologies": [ "ACH/wire fiat on-ramp" ], "technologyProperties": { "onRampType": "ACH/Fedwire bank transfer", "onRampRegion": "United States", "settlementRail": "ACH / Fedwire" } }, "united-kingdom": { "technologies": [ "UK Faster Payments on-ramp" ], "technologyProperties": { "onRampType": "Faster Payments bank transfer", "onRampRegion": "United Kingdom", "settlementRail": "FPS / BACS" } }, "germany": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "netherlands": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "switzerland": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SIC/SEPA bank transfer", "onRampRegion": "Switzerland/EU", "settlementRail": "SIC / SEPA Credit Transfer" } }, "belgium": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "france": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "sweden": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "norway": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA-adjacent bank transfer", "onRampRegion": "EEA", "settlementRail": "SEPA Credit Transfer" } }, "denmark": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "canada": { "technologies": [ "Canadian EFT on-ramp" ], "technologyProperties": { "onRampType": "Interac/EFT bank transfer", "onRampRegion": "Canada", "settlementRail": "Interac / EFT" } }, "australia": { "technologies": [ "Australian NPP on-ramp" ], "technologyProperties": { "onRampType": "NPP bank transfer", "onRampRegion": "Australia", "settlementRail": "NPP / BECS" } }, "japan": { "technologies": [ "Japanese Zengin on-ramp" ], "technologyProperties": { "onRampType": "Zengin bank transfer", "onRampRegion": "Japan", "settlementRail": "Zengin System" } }, "ireland": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "italy": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "spain": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "austria": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "finland": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "luxembourg": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "south-korea": { "technologies": [ "Korean banking on-ramp" ], "technologyProperties": { "onRampType": "KFTC bank transfer", "onRampRegion": "South Korea", "settlementRail": "KFTC / BOK-Wire" } }, "new-zealand": { "technologies": [ "NZ banking on-ramp" ], "technologyProperties": { "onRampType": "SBI bank transfer", "onRampRegion": "New Zealand", "settlementRail": "SBI / ESAS" } }, "united-arab-emirates": { "technologies": [ "UAE banking on-ramp" ], "technologyProperties": { "onRampType": "UAEFTS bank transfer", "onRampRegion": "United Arab Emirates", "settlementRail": "UAEFTS / IPP" } }, "singapore": { "technologies": [ "Singapore FAST on-ramp" ], "technologyProperties": { "onRampType": "FAST bank transfer", "onRampRegion": "Singapore", "settlementRail": "FAST / MEPS+" } }, "other": { "technologies": [ "Regional fiat on-ramp" ], "technologyProperties": { "onRampType": "Local rail bank transfer", "onRampRegion": "Region-specific", "settlementRail": "Local payment network" } } }, "showIf": { "questionId": "corridor-count", "minValue": "4-5" }, "prefillFrom": null, "briefSection": "Payment rail requirements", "text": "Fifth transfer origination country (if applicable)", "ngoText": "Fifth transfer origination country (if applicable)" }, { "id": "funding-method", "type": "select", "options": [ { "label": "Bank transfer from organisation account", "value": "bank-transfer" }, { "label": "Card payment from organisation", "value": "card-payment" }, { "label": "Direct stablecoin funding (organisation already holds stablecoins)", "value": "direct-stablecoin" }, { "label": "Mixed: bank transfer for most, card for urgent payments", "value": "mixed-methods" } ], "propertyMapping": { "bank-transfer": { "technologies": [ "Bank-integrated fiat on-ramp" ], "technologyProperties": { "fundingSource": "Organisation bank account", "onRampSpeed": "1-2 business days (SEPA/ACH) or same-day (Faster Payments/wire)", "kybRequired": "Yes \u2014 organisation KYB verification" } }, "card-payment": { "technologies": [ "Card payment on-ramp" ], "technologyProperties": { "fundingSource": "Organisation payment card", "onRampSpeed": "Near-instant", "kybRequired": "Yes \u2014 card verification and organisation KYB" } }, "direct-stablecoin": { "technologies": [ "Direct stablecoin treasury funding" ], "technologyProperties": { "fundingSource": "Existing stablecoin holdings", "onRampSpeed": "Immediate (no fiat conversion needed)", "kybRequired": "Wallet verification only" } }, "mixed-methods": { "technologies": [ "Multi-method fiat on-ramp", "Card payment on-ramp" ], "technologyProperties": { "fundingSource": "Bank transfer (primary) + card (urgent)", "onRampSpeed": "Varies by method", "kybRequired": "Yes \u2014 full organisation KYB" } } }, "prefillFrom": null, "briefSection": "Payment rail requirements", "text": "How does your organisation currently fund international transfers or payments?", "ngoText": "How does your organisation currently fund international transfers or payments?" }, { "id": "petty-cash-amount", "type": "select", "options": [ { "label": "Under $500/month", "value": "small" }, { "label": "$500\u2013$2,000/month", "value": "medium" }, { "label": "$2,000\u2013$10,000/month", "value": "large" }, { "label": "Over $10,000/month", "value": "very-large" } ], "propertyMapping": { "small": { "technologies": [ "Stablecoin-loaded mobile wallet" ], "technologyProperties": { "fundingModel": "Pre-loaded stablecoin wallet", "refillMechanism": "Threshold-triggered top-up" } }, "medium": { "technologies": [ "Stablecoin-loaded mobile wallet", "Spending limit controls" ], "technologyProperties": { "fundingModel": "Pre-loaded with spending limits", "refillMechanism": "Approval-triggered top-up" } }, "large": { "technologies": [ "Managed field wallet", "Multi-sig approval", "Spending category limits" ], "technologyProperties": { "fundingModel": "Controlled disbursement wallet", "refillMechanism": "Dual-approval top-up" } }, "very-large": { "technologies": [ "Managed field wallet", "Multi-sig approval", "Real-time monitoring" ], "technologyProperties": { "fundingModel": "Enterprise-controlled wallet", "refillMechanism": "Policy-governed replenishment" } } }, "prefillFrom": null, "briefSection": "Payment rail requirements", "text": "What is the typical monthly petty cash float per field office?", "ngoText": "What is the typical monthly petty cash float per field office?" }, { "id": "field-connectivity-pettycash", "type": "select", "options": [ { "label": "Reliable internet", "value": "reliable" }, { "label": "Intermittent connectivity", "value": "intermittent" }, { "label": "Very limited: 2G/EDGE at best", "value": "limited" }, { "label": "Mix: varies across offices", "value": "mixed" } ], "propertyMapping": { "reliable": { "technologies": [ "Cloud-based expense management" ], "technologyProperties": { "connectivityRequirement": "Online-first", "offlineCapability": "Not required" } }, "intermittent": { "technologies": [ "Offline-capable expense app" ], "technologyProperties": { "connectivityRequirement": "Offline-first with sync", "offlineCapability": "Store locally, sync when connected" } }, "limited": { "technologies": [ "USSD/SMS expense recording", "Offline-capable app" ], "technologyProperties": { "connectivityRequirement": "Zero-data capable", "offlineCapability": "Full offline with batch sync" } }, "mixed": { "technologies": [ "Multi-mode expense app" ], "technologyProperties": { "connectivityRequirement": "Adaptive", "offlineCapability": "Required for some locations" } } }, "prefillFrom": "P0-connectivity", "briefSection": "Infrastructure requirements", "text": "What connectivity is available at your field offices?", "ngoText": "What connectivity is available at your field offices?" }, { "id": "petty-cash-approval", "type": "select", "options": [ { "label": "Field manager approves all expenses", "value": "manager" }, { "label": "Threshold-based: auto-approved below limit", "value": "threshold" }, { "label": "Post-hoc review only", "value": "post-hoc" }, { "label": "No formal approval process currently", "value": "none" } ], "propertyMapping": { "manager": { "technologies": [ "Mobile approval workflow" ], "technologyProperties": { "approvalMechanism": "Manager sign-off per expense", "controlLevel": "Pre-expenditure approval" } }, "threshold": { "technologies": [ "Automated spending limits" ], "technologyProperties": { "approvalMechanism": "Auto below threshold, manager above", "controlLevel": "Policy-automated" } }, "post-hoc": { "technologies": [ "Expense review dashboard", "Anomaly flagging" ], "technologyProperties": { "approvalMechanism": "Post-expenditure review", "controlLevel": "Detective controls" } }, "none": { "technologies": [ "Expense approval workflow", "Spending limit controls" ], "technologyProperties": { "approvalMechanism": "New workflow needed", "controlLevel": "Preventive + detective recommended" } } }, "prefillFrom": null, "briefSection": "Governance and controls", "text": "What approval workflow exists for petty cash expenditures?", "ngoText": "What approval workflow exists for petty cash expenditures?" }, { "id": "sq-UC-A-010-001", "type": "single-select", "options": [ { "value": "daily-close", "label": "Daily close" }, { "value": "weekly-reconcile", "label": "Weekly reconciliation" }, { "value": "monthly-audit", "label": "Monthly audit" }, { "value": "real-time-digital", "label": "Real-time digital tracking" }, { "value": "event-triggered", "label": "Event-triggered (handover, incident)" } ], "propertyMapping": { "daily-close": { "technologies": [ "daily-reconciliation", "cash-counting" ], "technologyProperties": {} }, "weekly-reconcile": { "technologies": [ "weekly-reporting", "variance-tracking" ], "technologyProperties": {} }, "monthly-audit": { "technologies": [ "audit-logging", "monthly-review" ], "technologyProperties": {} }, "real-time-digital": { "technologies": [ "digital-tracking", "mobile-entry" ], "technologyProperties": {} }, "event-triggered": { "technologies": [ "event-logging", "trigger-rules" ], "technologyProperties": {} } }, "briefSection": "operations", "text": "What petty cash reconciliation frequency is required?", "ngoText": "What petty cash reconciliation frequency is required?" }, { "id": "sq-UC-A-010-003", "type": "single-select", "options": [ { "value": "dual-approval", "label": "Dual approval for transactions" }, { "value": "photo-receipt-required", "label": "Photo receipt required" }, { "value": "geo-fence", "label": "Geo-fencing verification" }, { "value": "random-audit", "label": "Random spot audits" }, { "value": "spending-pattern-analysis", "label": "Spending pattern analysis" } ], "propertyMapping": { "dual-approval": { "technologies": [ "multi-party-approval", "workflow-engine" ], "technologyProperties": {} }, "photo-receipt-required": { "technologies": [ "image-capture", "receipt-verification" ], "technologyProperties": {} }, "geo-fence": { "technologies": [ "gps-verification", "location-tagging" ], "technologyProperties": {} }, "random-audit": { "technologies": [ "audit-sampling", "random-selection" ], "technologyProperties": {} }, "spending-pattern-analysis": { "technologies": [ "analytics-engine", "anomaly-detection" ], "technologyProperties": {} } }, "briefSection": "operations", "text": "What is your current fraud detection and prevention approach for petty cash?", "ngoText": "What is your current fraud detection and prevention approach for petty cash?" }, { "id": "accounting-integration", "type": "select", "options": [ { "label": "Direct integration with your existing accounting software", "value": "direct-erp" }, { "label": "Export-based: generate reports compatible with our accounting system", "value": "export-based" }, { "label": "Standalone ledger with manual reconciliation", "value": "standalone" }, { "label": "Not sure, need guidance on accounting integration", "value": "guidance-needed" } ], "propertyMapping": { "direct-erp": { "technologies": [ "Accounting system connection", "Automatic record updates", "Account structure alignment" ], "technologyProperties": { "integrationMethod": "Real-time connection", "reconciliation": "Automated", "reportFormat": "Compatible with your accounting system" } }, "export-based": { "technologies": [ "Accounting export module", "Report generation engine", "CSV/spreadsheet export service" ], "technologyProperties": { "integrationMethod": "Scheduled export (CSV/spreadsheet)", "reconciliation": "Semi-automated", "reportFormat": "Standard CSV/spreadsheet" } }, "standalone": { "technologies": [ "Standalone accounting ledger", "Manual reconciliation tools" ], "technologyProperties": { "integrationMethod": "Manual import/export", "reconciliation": "Manual", "reportFormat": "PDF/spreadsheet reports" } }, "guidance-needed": { "technologies": [ "Accounting integration framework" ], "technologyProperties": { "integrationMethod": "To be determined", "reconciliation": "To be determined", "reportFormat": "To be determined" } } }, "prefillFrom": null, "briefSection": "Financial integration", "text": "How should this solution integrate with your existing accounting or financial systems?", "ngoText": "How should this solution integrate with your existing accounting or financial systems?" }, { "id": "beneficiary-choice", "label": "How will beneficiaries exercise choice in how they receive and use this service?", "type": "select", "briefSection": "End-user interface", "options": [ { "label": "Beneficiaries choose between delivery methods (cash, voucher, mobile money, direct)", "value": "delivery-choice" }, { "label": "Beneficiaries choose preferred merchants or service points", "value": "merchant-choice" }, { "label": "Beneficiaries control their own data sharing preferences", "value": "data-choice" }, { "label": "Multiple choice dimensions (delivery + merchant + data)", "value": "full-choice" }, { "label": "Limited choice: programme constraints determine delivery", "value": "limited" } ], "propertyMapping": { "delivery-choice": { "technologies": [], "technologyProperties": { "beneficiaryChoice": "Delivery method choice", "dignityDesign": "Beneficiaries select preferred receipt method" } }, "merchant-choice": { "technologies": [], "technologyProperties": { "beneficiaryChoice": "Merchant/service point choice", "dignityDesign": "Beneficiaries select where to redeem" } }, "data-choice": { "technologies": [], "technologyProperties": { "beneficiaryChoice": "Data sharing choice", "dignityDesign": "Beneficiaries control personal data sharing" } }, "full-choice": { "technologies": [], "technologyProperties": { "beneficiaryChoice": "Multi-dimensional choice", "dignityDesign": "Full beneficiary agency across delivery, merchant, and data" } }, "limited": { "technologies": [], "technologyProperties": { "beneficiaryChoice": "Limited by programme design", "dignityDesign": "Programme constraints; beneficiary informed of reasons" } } }, "text": "How will beneficiaries exercise choice in how they receive and use this service?" } ], "complexityFactors": { "relationships": 2, "operationalChange": 2, "dataCompliance": 1 }, "suggestedCriteria": [ { "id": "SC-MOBILE-SIMPLE", "name": "Mobile-First Simplicity", "description": "Field staff can submit expenses and petty cash requests from a basic smartphone. Petty cash management must be as simple as taking a photo of a receipt and entering an amount.", "weight": 0.3, "ratingGuide": { "5": "Intuitive mobile app. Photo receipt capture with auto-extraction. One-tap submission. Works on low-end Android. Available offline.", "4": "Good mobile app. Photo capture. Simple submission flow. Requires mid-range smartphone.", "3": "Mobile web interface. Manual data entry. Receipt photo upload. Requires connectivity.", "2": "Desktop-focused with basic mobile view. Manual entry and upload.", "1": "Desktop only. No mobile expense submission capability." } }, { "id": "SC-APPROVAL-FLOW", "name": "Approval Workflow & Spending Limits", "description": "The provider supports configurable approval workflows with spending limits per role. Field offices need clear authority levels. Team leads approve up to $X, office managers up to $Y.", "weight": 0.25, "ratingGuide": { "5": "Configurable multi-level approval. Per-role spending limits. Per-category limits. Automatic escalation. Approval delegation for travel/absence.", "4": "Multi-level approval. Role-based limits. Basic escalation. Delegation available.", "3": "Two-level approval. Organisation-wide limits. Manual escalation.", "2": "Single approver. Organisation-wide limits. No automatic escalation.", "1": "No approval workflow. Manual process outside the system." } }, { "id": "SC-CASH-ADVANCE", "name": "Cash Advance & Settlement Tracking", "description": "The provider can track cash advances, settlements, and outstanding balances per staff member. Petty cash requires knowing who holds how much and what's been accounted for.", "weight": 0.2, "ratingGuide": { "5": "Full advance lifecycle tracking. Per-person balance. Automatic settlement reminders. Aging analysis for overdue advances. Multi-currency.", "4": "Good advance tracking. Balance per person. Settlement reminders. Single currency.", "3": "Advance recording and settlement. Manual balance checking. Basic reminders.", "2": "Basic advance recording. Manual tracking of outstanding amounts.", "1": "No advance tracking. Manual management in spreadsheets." } }, { "id": "SC-CATEGORY-CODE", "name": "Expense Categorisation & Project Coding", "description": "Expenses can be tagged with project codes and budget lines at point of entry. Correct coding at source prevents month-end reclassification headaches.", "weight": 0.15, "ratingGuide": { "5": "Mandatory project/fund coding at submission. Smart suggestions based on vendor/amount. Category hierarchy matching org chart of accounts.", "4": "Project coding at submission. Dropdown selections. Good alignment with accounting categories.", "3": "Project coding available. Free-text entry. Post-submission categorisation possible.", "2": "Basic categories only. No project code integration. Manual coding later.", "1": "No categorisation at point of entry. All coding done in accounting system." } }, { "id": "SC-CASH-SECURITY", "name": "Cash Handling Security & Controls", "description": "The provider helps reduce cash handling risk. Physical cash management in field offices creates fraud and theft risk: digital alternatives or controls help mitigate this.", "weight": 0.1, "ratingGuide": { "5": "Digital payment options for most petty cash purposes (mobile money, prepaid cards). Cash vault tracking. Surprise count scheduling. Segregation of duties enforced.", "4": "Some digital alternatives. Cash tracking features. Good control framework.", "3": "Cash tracking with reconciliation tools. Basic controls. Digital options limited.", "2": "Transaction recording only. No specific cash controls. No digital alternatives.", "1": "No cash management features. Paper-based tracking." } } ], "procurement": { "marketMaturity": "mature", "primaryMode": "off-the-shelf", "alternativeModes": [ "conversation-guide" ], "reasoning": "Mature expense management SaaS market.", "exampleProductCategories": [ "expense-management-saas", "field-finance-app" ], "partnerChannels": [], "lastReviewed": "2026-05-01" } }, { "id": "UC-A-011", "name": "Procurement process transparency and audit trails", "category": "A", "subcategory": "Compliance and Reporting", "description": "Keep a record of each purchasing decision, from choosing the vendor to final approval, that cannot be changed later and that auditors can check themselves.", "bCriteria": [ "B1", "B3" ], "requiredComponents": [ { "component": "record-keeping-platform", "description": "Immutable procurement records" }, { "component": "audit-mechanism", "description": "Tamper-proof audit trail" }, { "component": "accounting-integration", "description": "Purchase order tracking" }, { "component": "decision-audit-trail", "description": "Approval decision tracking" } ], "conditionalComponents": [ { "component": "smart-contracts", "condition": "If approval workflows are automated" }, { "component": "identity-verification", "condition": "If vendor identity verification needed", "linksTo": "UC-B-032" } ], "crossCategoryDependencies": [ "UC-E-074 if coordination with partners needed" ], "p2TriggerConditions": { "description": "Activated when P2 shows procurement volume + audit requirements + transparency concerns", "rangeSignals": [ "procurementVolume >= high", "auditFrequency >= annual", "transparencyConcerns >= true" ] }, "contextFieldsTemplate": [ { "field": "vendorCount", "source": "P2 supplier network", "description": "Number of vendors" }, { "field": "procurementValue", "source": "P2 spend", "description": "Annual procurement spend" }, { "field": "auditRequirements", "source": "P0 donor requirements", "description": "Required audit standards" }, { "field": "approvalLayers", "source": "P0 policies", "description": "Approval workflow steps" } ], "implementationComplexity": "medium", "examples": { "note": "Procurement governance frameworks", "references": [ { "name": "Provenance", "url": "https://www.provenance.org/news-insights/blockchain-the-solution-for-transparency-in-product-supply-chains", "solved": "Traced supply chains for ethical sourcing verification with tamper-proof records" }, { "name": "Disberse", "url": "https://www.nesta.org.uk/feature/new-radicals-2018/disberse/", "solved": "Traced international aid fund transfers reducing intermediary costs" } ] }, "solutionQuestions": [ { "id": "procurement-stages", "type": "multiselect", "options": [ { "label": "Requisition / purchase request", "value": "requisition" }, { "label": "Bid solicitation and evaluation", "value": "bidding" }, { "label": "Vendor selection and award", "value": "vendor-selection" }, { "label": "Contract signing", "value": "contract" }, { "label": "Delivery/receipt verification", "value": "delivery" }, { "label": "Invoice and payment", "value": "payment" }, { "label": "All of the above, end-to-end", "value": "end-to-end" } ], "propertyMapping": { "requisition": { "technologies": [ "Blockchain-anchored procurement records" ], "technologyProperties": { "auditScope": "Requisition stage", "recordType": "Request hash + approval" } }, "bidding": { "technologies": [ "Blockchain-anchored procurement records", "Sealed bid mechanism" ], "technologyProperties": { "auditScope": "Bid stage", "recordType": "Bid hashes + evaluation scores" } }, "vendor-selection": { "technologies": [ "Decision audit trail" ], "technologyProperties": { "auditScope": "Selection stage", "recordType": "Evaluation matrix + decision rationale" } }, "contract": { "technologies": [ "Contract hash anchoring" ], "technologyProperties": { "auditScope": "Contract stage", "recordType": "Contract hash + signatures" } }, "delivery": { "technologies": [ "Delivery verification module" ], "technologyProperties": { "auditScope": "Delivery stage", "recordType": "GRN hash + inspection records" } }, "payment": { "technologies": [ "Payment audit trail" ], "technologyProperties": { "auditScope": "Payment stage", "recordType": "Invoice hash + payment proof" } }, "end-to-end": { "technologies": [ "End-to-end procurement audit platform" ], "technologyProperties": { "auditScope": "Full lifecycle", "recordType": "All stage hashes linked" } } }, "prefillFrom": null, "briefSection": "Reporting and audit", "text": "Which procurement stages need to be captured on an tamper-proof audit trail?", "ngoText": "Which procurement stages need to be captured on an immutable audit trail?" }, { "id": "audit-access", "type": "multiselect", "options": [ { "label": "Internal auditors", "value": "internal-audit" }, { "label": "External auditors", "value": "external-audit" }, { "label": "Donors", "value": "donors" }, { "label": "Procurement team only", "value": "procurement-team" }, { "label": "Senior management", "value": "management" }, { "label": "Regulatory bodies", "value": "regulators" } ], "propertyMapping": { "internal-audit": { "technologies": [ "Role-based audit access" ], "technologyProperties": { "accessModel": "Internal audit role", "viewScope": "Full records" } }, "external-audit": { "technologies": [ "External audit portal", "Time-limited access tokens" ], "technologyProperties": { "accessModel": "External audit portal", "viewScope": "Scoped to audit period" } }, "donors": { "technologies": [ "Donor transparency portal" ], "technologyProperties": { "accessModel": "Donor-scoped read-only", "viewScope": "Donor-funded procurement only" } }, "procurement-team": { "technologies": [ "Standard role-based access" ], "technologyProperties": { "accessModel": "Procurement team access", "viewScope": "Own procurements" } }, "management": { "technologies": [ "Management dashboard" ], "technologyProperties": { "accessModel": "Senior management role", "viewScope": "Summary + exception view" } }, "regulators": { "technologies": [ "Regulatory access portal" ], "technologyProperties": { "accessModel": "Regulatory access", "viewScope": "Compliance-specific records" } } }, "prefillFrom": null, "briefSection": "Governance and controls", "text": "Who needs access to the procurement audit trail?", "ngoText": "Who needs access to the procurement audit trail?" }, { "id": "procurement-fraud-risk", "type": "select", "options": [ { "label": "High: operating in high-corruption environments", "value": "high" }, { "label": "Moderate: some risk areas", "value": "moderate" }, { "label": "Low: strong existing controls", "value": "low" }, { "label": "Unknown, lack visibility", "value": "unknown" } ], "propertyMapping": { "high": { "technologies": [ "Anomaly detection engine", "Conflict of interest screening", "Bid pattern analysis" ], "technologyProperties": { "fraudPrevention": "Advanced anomaly detection + pattern analysis", "transparency": "Full bid and evaluation transparency" } }, "moderate": { "technologies": [ "Basic anomaly detection", "Segregation of duties enforcement" ], "technologyProperties": { "fraudPrevention": "Standard anomaly flagging", "transparency": "Key decision point transparency" } }, "low": { "technologies": [ "Standard audit logging" ], "technologyProperties": { "fraudPrevention": "Basic logging and controls", "transparency": "Standard audit trail" } }, "unknown": { "technologies": [ "Anomaly detection engine", "Procurement analytics" ], "technologyProperties": { "fraudPrevention": "Detection-first approach", "transparency": "Full transparency recommended" } } }, "prefillFrom": null, "briefSection": "Identity and compliance", "text": "How significant is the fraud/collusion risk in your procurement processes?", "ngoText": "How significant is the fraud/collusion risk in your procurement processes?" }, { "id": "sq-UC-A-011-001", "type": "single-select", "options": [ { "value": "price-only", "label": "Price only" }, { "value": "technical-scoring", "label": "Technical scoring" }, { "value": "committee-votes", "label": "Committee votes" }, { "value": "all-criteria", "label": "All evaluation criteria" }, { "value": "outcome-only", "label": "Outcome only" } ], "propertyMapping": { "price-only": { "technologies": [ "price-tracking", "cost-comparison" ], "technologyProperties": {} }, "technical-scoring": { "technologies": [ "scoring-engine", "criteria-evaluation" ], "technologyProperties": {} }, "committee-votes": { "technologies": [ "voting-system", "committee-tracking" ], "technologyProperties": {} }, "all-criteria": { "technologies": [ "comprehensive-tracking", "full-audit-trail" ], "technologyProperties": {} }, "outcome-only": { "technologies": [ "outcome-logging", "award-recording" ], "technologyProperties": {} } }, "briefSection": "requirements", "text": "What bid evaluation criteria should be permanently recorded in a tamper-proof audit trail?", "ngoText": "What bid evaluation criteria should be recorded on-chain?" }, { "id": "sq-UC-A-011-003", "type": "single-select", "options": [ { "value": "justification-memo", "label": "Justification memo required" }, { "value": "approval-chain", "label": "Multi-level approval chain" }, { "value": "public-disclosure", "label": "Public disclosure" }, { "value": "donor-notification", "label": "Donor notification" }, { "value": "threshold-based", "label": "Threshold-based exceptions" } ], "propertyMapping": { "justification-memo": { "technologies": [ "document-logging", "memo-storage" ], "technologyProperties": {} }, "approval-chain": { "technologies": [ "approval-workflow", "authority-hierarchy" ], "technologyProperties": {} }, "public-disclosure": { "technologies": [ "public-registry", "disclosure-system" ], "technologyProperties": {} }, "donor-notification": { "technologies": [ "donor-alerts", "notification-system" ], "technologyProperties": {} }, "threshold-based": { "technologies": [ "rule-engine", "threshold-logic" ], "technologyProperties": {} } }, "briefSection": "compliance", "text": "How are sole-source procurement exceptions currently documented?", "ngoText": "How are sole-source procurement exceptions currently documented?" }, { "id": "accounting-integration", "type": "select", "options": [ { "label": "Direct integration with your existing accounting software", "value": "direct-erp" }, { "label": "Export-based: generate reports compatible with our accounting system", "value": "export-based" }, { "label": "Standalone ledger with manual reconciliation", "value": "standalone" }, { "label": "Not sure, need guidance on accounting integration", "value": "guidance-needed" } ], "propertyMapping": { "direct-erp": { "technologies": [ "Accounting system connection", "Automatic record updates", "Account structure alignment" ], "technologyProperties": { "integrationMethod": "Real-time connection", "reconciliation": "Automated", "reportFormat": "Compatible with your accounting system" } }, "export-based": { "technologies": [ "Accounting export module", "Report generation engine", "CSV/spreadsheet export service" ], "technologyProperties": { "integrationMethod": "Scheduled export (CSV/spreadsheet)", "reconciliation": "Semi-automated", "reportFormat": "Standard CSV/spreadsheet" } }, "standalone": { "technologies": [ "Standalone accounting ledger", "Manual reconciliation tools" ], "technologyProperties": { "integrationMethod": "Manual import/export", "reconciliation": "Manual", "reportFormat": "PDF/spreadsheet reports" } }, "guidance-needed": { "technologies": [ "Accounting integration framework" ], "technologyProperties": { "integrationMethod": "To be determined", "reconciliation": "To be determined", "reportFormat": "To be determined" } } }, "prefillFrom": null, "briefSection": "Financial integration", "text": "How should this solution integrate with your existing accounting or financial systems?", "ngoText": "How should this solution integrate with your existing accounting or financial systems?" } ], "complexityFactors": { "relationships": 2, "operationalChange": 2, "dataCompliance": 1 }, "suggestedCriteria": [ { "id": "SC-PROC-LIFECYCLE", "name": "Full Procurement Lifecycle Tracking", "description": "The provider tracks the entire procurement process from requisition through purchase order, delivery, and payment. Each step must be recorded with timestamps and approvals.", "weight": 0.3, "ratingGuide": { "5": "End-to-end workflow: requisition \u2192 approval \u2192 tender \u2192 evaluation \u2192 PO \u2192 delivery \u2192 invoice \u2192 payment. Each stage timestamped with actor identity. Immutable record.", "4": "Covers most stages. Good timestamping. Minor gaps in early stages (requisition).", "3": "PO through payment well covered. Requisition and tendering separate or manual.", "2": "Payment tracking with PO reference. Earlier stages not tracked.", "1": "Payment recording only. No procurement lifecycle visibility." } }, { "id": "SC-BID-TRANSPARENCY", "name": "Tender & Bid Transparency", "description": "The provider ensures bidding processes are transparent and tamper-evident. Procurement fraud often occurs at the bid evaluation stage. Sealed bids and evaluation criteria visibility are critical.", "weight": 0.25, "ratingGuide": { "5": "Sealed digital bids opened at deadline. Evaluation criteria published before bidding. Scorer identity recorded. Evaluation matrix immutable. Conflict-of-interest declarations.", "4": "Digital bid management with sealed opening. Evaluation tracking. Good transparency.", "3": "Bid tracking. Evaluation recording. Some manual steps in bid management.", "2": "Basic bid recording. Manual evaluation process. Limited transparency.", "1": "No bid management. Procurement decisions recorded after the fact." } }, { "id": "SC-AUDIT-TRAIL-PROC", "name": "Tamper-Evident Audit Trail", "description": "Procurement records are tamper-evident. Auditors and donors need assurance that procurement records haven't been altered after the fact to conceal irregularities.", "weight": 0.2, "ratingGuide": { "5": "Blockchain-anchored records. Cryptographic proof of integrity. Any modification creates a new version with full change history. Independent verification possible.", "4": "Tamper-evident records. Good version tracking. Change log with timestamps.", "3": "Access-controlled records. Change tracking. Standard database integrity.", "2": "Basic access controls. Limited change tracking.", "1": "Records can be modified without trace. No audit trail." } }, { "id": "SC-SUPPLIER-MGMT", "name": "Supplier Database & Due Diligence", "description": "The provider maintains a verified supplier database with due diligence records. Knowing who you're buying from, and that they've been vetted, is fundamental to procurement integrity.", "weight": 0.15, "ratingGuide": { "5": "Central supplier registry with verification status. Due diligence records attached. Sanctions screening. Performance history. Blacklist management.", "4": "Good supplier database. Verification tracking. Basic screening. Performance records.", "3": "Supplier list with basic details. Manual verification tracking. No automated screening.", "2": "Ad-hoc supplier records. No centralised database. Manual due diligence.", "1": "No supplier management. Vendors tracked only in payment records." } }, { "id": "SC-THRESHOLD-RULES", "name": "Procurement Threshold & Policy Enforcement", "description": "The provider enforces procurement policies automatically. Different purchase values require different processes (3 quotes, sealed tender, board approval). Automation prevents policy bypass.", "weight": 0.1, "ratingGuide": { "5": "Configurable threshold rules. Automatic routing (direct purchase / 3 quotes / tender). Policy compliance dashboard. Exception reporting.", "4": "Good threshold management. Automatic routing for main categories. Compliance tracking.", "3": "Threshold awareness with alerts. Semi-automatic routing. Basic compliance.", "2": "Threshold information displayed. No automatic enforcement. Manual routing.", "1": "No threshold management. All procurement policy enforcement is manual." } } ], "procurement": { "marketMaturity": "emerging", "primaryMode": "rfq", "alternativeModes": [ "integrator-led" ], "reasoning": "Procurement transparency platforms exist but customisation common.", "exampleProductCategories": [ "procurement-transparency-platform", "audit-trail-saas" ], "partnerChannels": [], "lastReviewed": "2026-05-01" } }, { "id": "UC-A-012", "name": "Smart contract-based vendor payment terms", "category": "A", "subcategory": "Cross-Border Payments and Transfers", "description": "Pay vendors automatically once the agreed delivery conditions are met, so disputes over whether a milestone was reached happen less often.", "bCriteria": [ "B5", "B7" ], "requiredComponents": [ { "component": "smart-contracts", "description": "Conditional payment logic" }, { "component": "payment-rails", "description": "Blockchain settlement" }, { "component": "stablecoin", "description": "Payment settlement currency" }, { "component": "oracle-data", "description": "External data for payment triggers" } ], "conditionalComponents": [ { "component": "iot-sensors", "condition": "If payment depends on delivery verification", "linksTo": "UC-D-053" }, { "component": "identity-verification", "condition": "If vendor KYC required", "linksTo": "UC-B-032" } ], "crossCategoryDependencies": [ "UC-D-063 if last-mile verification needed", "UC-E-072 if disputes arise" ], "p2TriggerConditions": { "description": "Activated when P2 shows complex payment terms + conditional deliverables + vendor disputes", "rangeSignals": [ "paymentTerms = complex", "conditionality >= true", "disputeFrequency >= moderate" ] }, "contextFieldsTemplate": [ { "field": "paymentConditions", "source": "P2 vendor contracts", "description": "Types of conditions" }, { "field": "verificationMethod", "source": "P2 QA processes", "description": "How conditions are verified" }, { "field": "vendorCapacity", "source": "P2 vendor assessment", "description": "Vendor technical capability" }, { "field": "disputeHistory", "source": "P2 vendor performance", "description": "Past payment disputes" } ], "implementationComplexity": "high", "examples": { "note": "Advanced supply chain automation", "references": [ { "name": "WFP Building Blocks", "url": "https://www.wfp.org/building-blocks", "solved": "Transferred cash to refugee populations at scale, fast and at low cost" }, { "name": "Provenance", "url": "https://www.provenance.org/news-insights/blockchain-the-solution-for-transparency-in-product-supply-chains", "solved": "Traced supply chains for ethical sourcing verification with tamper-proof records" } ] }, "solutionQuestions": [ { "id": "stablecoin-approach", "type": "select", "options": [ { "label": "A regulated digital dollar", "value": "usd-pegged" }, { "label": "EUR-pegged stablecoin", "value": "eur-pegged" }, { "label": "Multiple stablecoins depending on corridor", "value": "multi-stablecoin" }, { "label": "Not sure, need guidance on stablecoin selection", "value": "guidance-needed" } ], "propertyMapping": { "usd-pegged": { "technologies": [ "USD-pegged stablecoin rail", "Stablecoin settlement layer" ], "technologyProperties": { "stablecoinType": "A regulated digital dollar", "fxConversion": "At on-ramp and off-ramp points" } }, "eur-pegged": { "technologies": [ "EUR-pegged stablecoin rail", "Stablecoin settlement layer" ], "technologyProperties": { "stablecoinType": "EUR-pegged", "fxConversion": "At on-ramp and off-ramp points" } }, "multi-stablecoin": { "technologies": [ "Multi-stablecoin settlement layer", "Automated FX conversion" ], "technologyProperties": { "stablecoinType": "Multiple denominations", "fxConversion": "Digital or at off-ramp" } }, "guidance-needed": { "technologies": [ "Stablecoin settlement layer" ], "technologyProperties": { "stablecoinType": "To be determined during solution design", "fxConversion": "To be determined" } } }, "prefillFrom": null, "briefSection": "Stablecoin and FX", "text": "What stablecoin approach is preferred for this solution?", "ngoText": "What stablecoin approach is preferred for this solution?" }, { "id": "payment-term-types", "type": "multiselect", "options": [ { "label": "Payment on delivery/inspection", "value": "delivery" }, { "label": "Milestone-based payments", "value": "milestone" }, { "label": "Advance + balance on completion", "value": "advance-balance" }, { "label": "Time-based (30/60/90 day terms)", "value": "time-based" }, { "label": "Performance-linked payments", "value": "performance" }, { "label": "Retainer/recurring payments", "value": "retainer" } ], "propertyMapping": { "delivery": { "technologies": [ "Smart contract escrow", "Delivery verification oracle", "IoT/GPS verification" ], "technologyProperties": { "contractLogic": "Release on verified delivery", "verificationSource": "Field confirmation or IoT sensor", "escrowType": "Full amount held until delivery" } }, "milestone": { "technologies": [ "Smart contract milestone engine", "Milestone verification workflow" ], "technologyProperties": { "contractLogic": "Staged release on milestone completion", "verificationSource": "Manual sign-off or data trigger", "escrowType": "Tranche-based escrow" } }, "advance-balance": { "technologies": [ "Smart contract split payment", "Completion verification" ], "technologyProperties": { "contractLogic": "Immediate advance + conditional balance", "verificationSource": "Completion sign-off", "escrowType": "Balance held in escrow" } }, "time-based": { "technologies": [ "Smart contract time-lock", "Automated release scheduler" ], "technologyProperties": { "contractLogic": "Time-triggered auto-release", "verificationSource": "Block timestamp", "escrowType": "Time-locked escrow" } }, "performance": { "technologies": [ "Smart contract performance oracle", "KPI data feed" ], "technologyProperties": { "contractLogic": "KPI-triggered payment", "verificationSource": "Performance data oracle", "escrowType": "Performance-linked escrow" } }, "retainer": { "technologies": [ "Smart contract recurring payment", "Automated scheduler" ], "technologyProperties": { "contractLogic": "Scheduled recurring disbursement", "verificationSource": "Calendar/time trigger", "escrowType": "Rolling pre-funded" } } }, "prefillFrom": null, "briefSection": "Payment logic", "text": "What types of payment terms do you typically use with vendors?", "ngoText": "What types of payment terms do you typically use with vendors?" }, { "id": "delivery-verification-method", "type": "select", "options": [ { "label": "Physical inspection by field staff", "value": "physical-inspection" }, { "label": "Goods receipt note signed by warehouse", "value": "grn" }, { "label": "Third-party inspection", "value": "third-party" }, { "label": "Self-reported by vendor with evidence", "value": "self-reported" }, { "label": "No formal verification", "value": "none" } ], "propertyMapping": { "physical-inspection": { "technologies": [ "Mobile inspection app", "Photo/GPS verification" ], "technologyProperties": { "verificationMethod": "Field staff mobile confirmation", "evidenceCapture": "Photo + GPS + timestamp" } }, "grn": { "technologies": [ "Digital GRN module", "QR/barcode scanning" ], "technologyProperties": { "verificationMethod": "Digital goods receipt", "evidenceCapture": "Scan + sign-off" } }, "third-party": { "technologies": [ "Third-party verification oracle", "Multi-party attestation" ], "technologyProperties": { "verificationMethod": "Independent verification feed", "evidenceCapture": "Third-party attestation hash" } }, "self-reported": { "technologies": [ "Evidence submission portal", "Verification review workflow" ], "technologyProperties": { "verificationMethod": "Vendor-submitted evidence", "evidenceCapture": "Document/photo upload + review" } }, "none": { "technologies": [ "Verification workflow (new)" ], "technologyProperties": { "verificationMethod": "New process needed", "evidenceCapture": "To be designed" } } }, "prefillFrom": null, "briefSection": "Payment operations", "text": "How is delivery or completion currently verified before payment?", "ngoText": "How is delivery or completion currently verified before payment?" }, { "id": "contract-value-range", "type": "select", "options": [ { "label": "Under $5,000", "value": "small" }, { "label": "$5,000\u2013$50,000", "value": "medium" }, { "label": "$50,000\u2013$500,000", "value": "large" }, { "label": "Over $500,000", "value": "very-large" } ], "propertyMapping": { "small": { "technologies": [ "Simple smart contract template" ], "technologyProperties": { "contractComplexity": "Template-based", "auditRequirement": "Standard" } }, "medium": { "technologies": [ "Configurable smart contract" ], "technologyProperties": { "contractComplexity": "Configurable parameters", "auditRequirement": "Enhanced" } }, "large": { "technologies": [ "Audited smart contract", "Multi-sig governance" ], "technologyProperties": { "contractComplexity": "Custom logic with audit", "auditRequirement": "Independent smart contract audit" } }, "very-large": { "technologies": [ "Audited smart contract", "Multi-sig governance", "Dispute resolution mechanism" ], "technologyProperties": { "contractComplexity": "Full custom with dispute resolution", "auditRequirement": "Formal verification recommended" } } }, "prefillFrom": null, "briefSection": "Payment rail requirements", "text": "What is the typical contract value range for smart contract payment terms?", "ngoText": "What is the typical contract value range for smart contract payment terms?", "hidden": true }, { "id": "vendor-dispute-resolution", "type": "select", "options": [ { "label": "Vendor self-service portal to raise and track disputes", "value": "self-service" }, { "label": "Internal procurement team mediates disputes manually", "value": "internal-mediation" }, { "label": "Third-party arbitration for disputes above a threshold value", "value": "third-party" }, { "label": "Automated rules: system applies contract terms and flags exceptions", "value": "automated-rules" }, { "label": "Not sure, no formal dispute process exists yet", "value": "unsure" } ], "propertyMapping": { "self-service": { "technologies": [ "Vendor dispute portal", "Case tracking system" ], "technologyProperties": { "disputeModel": "Self-service vendor portal", "escalationPath": "Vendor-initiated", "automationLevel": "Low" } }, "internal-mediation": { "technologies": [ "Internal dispute workflow" ], "technologyProperties": { "disputeModel": "Manual internal mediation", "escalationPath": "Procurement team", "automationLevel": "None" } }, "third-party": { "technologies": [ "Third-party arbitration integration" ], "technologyProperties": { "disputeModel": "External arbitration", "escalationPath": "Threshold-based to third party", "automationLevel": "Low" } }, "automated-rules": { "technologies": [ "Automated contract enforcement", "Exception flagging engine" ], "technologyProperties": { "disputeModel": "Rule-based automation", "escalationPath": "Auto-flag then human review", "automationLevel": "High" } }, "unsure": { "technologies": [ "Dispute process design needed" ], "technologyProperties": { "disputeModel": "TBD", "escalationPath": "TBD", "automationLevel": "TBD" } } }, "prefillFrom": null, "briefSection": "Governance and controls", "text": "What happens when a vendor disputes that a milestone or delivery was completed?", "ngoText": "What happens when a vendor disputes that a milestone or delivery was completed?" }, { "id": "vendor-approval-workflow", "type": "select", "options": [ { "label": "Single approver for all vendor payments", "value": "single" }, { "label": "Dual approval (e.g. programme manager + finance)", "value": "dual" }, { "label": "Threshold-based: higher values need more approvers", "value": "threshold" }, { "label": "Fully delegated to field offices below a cap", "value": "delegated" }, { "label": "Not sure, approval rules vary or are informal", "value": "unsure" } ], "propertyMapping": { "single": { "technologies": [ "Single-signer payment release" ], "technologyProperties": { "approvalComplexity": "Single approver", "thresholdBased": "No", "fieldDelegation": "No" } }, "dual": { "technologies": [ "Dual-approval payment workflow" ], "technologyProperties": { "approvalComplexity": "Dual approval", "thresholdBased": "No", "fieldDelegation": "No" } }, "threshold": { "technologies": [ "Threshold-based multi-sig approval" ], "technologyProperties": { "approvalComplexity": "Threshold-based", "thresholdBased": "Yes", "fieldDelegation": "Partial" } }, "delegated": { "technologies": [ "Delegated approval with spending cap" ], "technologyProperties": { "approvalComplexity": "Delegated", "thresholdBased": "Yes \u2014 by cap", "fieldDelegation": "Yes" } }, "unsure": { "technologies": [ "Approval workflow design needed" ], "technologyProperties": { "approvalComplexity": "TBD", "thresholdBased": "TBD", "fieldDelegation": "TBD" } } }, "prefillFrom": null, "briefSection": "Governance and controls", "text": "What approval workflow exists for vendor payments?", "ngoText": "What approval workflow exists for vendor payments?" }, { "id": "vendor-payment-reporting", "type": "select", "options": [ { "label": "Basic payment ledger: date, amount, vendor, status", "value": "basic" }, { "label": "Contract-linked reporting: payments tied to specific contract milestones", "value": "contract-linked" }, { "label": "Donor-facing reporting: payments mapped to grant budgets and budget lines", "value": "donor-facing" }, { "label": "Full audit trail: every approval, change, and verification step recorded", "value": "full-audit" }, { "label": "Not sure, need guidance on reporting requirements", "value": "unsure" } ], "propertyMapping": { "basic": { "technologies": [ "Payment ledger" ], "technologyProperties": { "reportingDepth": "Basic", "donorVisibility": "No", "auditTrail": "Minimal" } }, "contract-linked": { "technologies": [ "Contract-payment linkage engine" ], "technologyProperties": { "reportingDepth": "Contract-linked", "donorVisibility": "Partial", "auditTrail": "Milestone-level" } }, "donor-facing": { "technologies": [ "Donor reporting dashboard", "Budget-line mapping" ], "technologyProperties": { "reportingDepth": "Donor-facing", "donorVisibility": "Yes", "auditTrail": "Budget-line level" } }, "full-audit": { "technologies": [ "Full audit trail engine", "Approval chain recorder" ], "technologyProperties": { "reportingDepth": "Full audit", "donorVisibility": "Yes", "auditTrail": "Every action logged" } }, "unsure": { "technologies": [ "Reporting requirements assessment needed" ], "technologyProperties": { "reportingDepth": "TBD", "donorVisibility": "TBD", "auditTrail": "TBD" } } }, "prefillFrom": null, "briefSection": "Reporting and audit", "text": "What vendor payment reporting do your auditors or donors require?", "ngoText": "What vendor payment reporting do your auditors or donors require?" } ], "complexityFactors": { "relationships": 3, "operationalChange": 2, "dataCompliance": 2 }, "suggestedCriteria": [ { "id": "SC-CONDITION-FLEX", "name": "Payment Condition Flexibility", "description": "This measures how flexible the smart contract payment conditions are. NGO vendor terms range from simple milestone payments to complex multi-condition releases (delivery confirmed + quality check + beneficiary verification).", "weight": 0.3, "ratingGuide": { "5": "Configurable multi-condition logic (AND/OR). Time-based, event-based, and approval-based triggers. Partial release capability. Condition templates for common NGO scenarios.", "4": "Good multi-condition support. Time and approval triggers. Partial releases. Some templates.", "3": "Basic milestone-based releases. Time or approval triggers. Full release per milestone.", "2": "Simple time-based or single-condition releases. No partial payments.", "1": "Manual payment release. No automated condition checking." } }, { "id": "SC-ORACLE-DATA", "name": "External Data Verification", "description": "Can the smart contract verify real-world conditions (delivery confirmed, goods inspected, beneficiary count verified) without relying solely on the payer's attestation?", "weight": 0.25, "ratingGuide": { "5": "Multiple verification sources: IoT sensors, third-party inspectors, beneficiary confirmation, GPS location data. Oracle feeds with dispute resolution.", "4": "Third-party verification integration. Multiple attestation sources. Good dispute handling.", "3": "Dual-party confirmation (buyer and seller). Basic third-party option. Simple dispute process.", "2": "Self-reported by seller, confirmed by buyer. No independent verification.", "1": "Single-party attestation. No external data integration." } }, { "id": "SC-DISPUTE-RESOLVE", "name": "Dispute Resolution Mechanism", "description": "This covers what happens when conditions are disputed. If a vendor claims delivery but the field office disagrees, the system needs a clear escalation and resolution process.", "weight": 0.2, "ratingGuide": { "5": "Built-in dispute workflow. Escrow during disputes. Escalation chain. Mediator assignment. Evidence submission. Resolution timeline enforcement.", "4": "Good dispute process. Escrow available. Escalation to designated arbiter.", "3": "Basic dispute flagging. Manual resolution. Payment paused during dispute.", "2": "Dispute noted but payment process continues. Manual intervention required.", "1": "No dispute mechanism. All-or-nothing payment execution." } }, { "id": "SC-VENDOR-ACCESS", "name": "Vendor-Friendly Interface", "description": "Vendors can monitor contract status, upcoming milestones, and payment schedule without technical knowledge. Vendors shouldn't need to understand blockchain to participate.", "weight": 0.15, "ratingGuide": { "5": "Vendor portal showing contract status, next milestone, expected payment date. SMS/email notifications. Works on basic smartphone. No blockchain knowledge needed.", "4": "Good vendor visibility. Portal or app. Notifications for key events.", "3": "Basic vendor view of payment status. Email notifications. Web access required.", "2": "Limited vendor visibility. Status on request only. No self-service.", "1": "No vendor-facing interface. Vendors rely on NGO communication." } }, { "id": "SC-TEMPLATE-LIB", "name": "Contract Template Library", "description": "The provider offers pre-built contract templates for common NGO procurement scenarios. Creating smart contracts from scratch is expensive. Templates for goods delivery, consulting, construction milestones etc. reduce setup cost.", "weight": 0.1, "ratingGuide": { "5": "Extensive template library covering goods, services, construction, consulting. NGO-specific terms. Customisable without coding. Version management.", "4": "Good template selection. Covers main procurement types. Easy customisation.", "3": "Basic templates for simple milestone payments. Manual setup for complex terms.", "2": "Generic template. Significant customisation needed for each contract.", "1": "No templates. Every contract built from scratch. Developer required." } } ], "procurement": { "marketMaturity": "nascent", "primaryMode": "integrator-led", "alternativeModes": [ "rfq" ], "reasoning": "Smart-contract vendor payment terms are blockchain-specific and bespoke; integrator-led delivery is the realistic pattern.", "exampleProductCategories": [ "smart-contract-payments", "programmable-payments-platform" ], "partnerChannels": [], "lastReviewed": "2026-05-01" } }, { "id": "UC-A-013", "name": "Multi-party approval workflows across time zones", "category": "A", "subcategory": "Internal Fund Movement", "description": "Let approvers in different time zones sign off one payment, each seeing the same information, without waiting for everyone to be online together.", "bCriteria": [ "B1", "B2", "B5" ], "requiredComponents": [ { "component": "smart-contracts", "description": "Multi-signature approval logic" }, { "component": "multi-sig-treasury", "description": "Multi-sig wallet infrastructure" }, { "component": "coordination-layer", "description": "Workflow coordination" } ], "conditionalComponents": [ { "component": "identity-verification", "condition": "If approver identity verification needed", "linksTo": "UC-B-029" } ], "crossCategoryDependencies": [ "UC-E-075 if governance voting involved" ], "p2TriggerConditions": { "description": "Activated when P2 shows distributed teams + approval bottlenecks + timezone challenges", "rangeSignals": [ "timezones >= 2", "approvalTime >= 2+ days", "approverGeography = distributed" ] }, "contextFieldsTemplate": [ { "field": "approvalLayers", "source": "P0 governance", "description": "Number of approval signatories" }, { "field": "timezones", "source": "P0 operations", "description": "Timezones involved" }, { "field": "approvalSLA", "source": "P2 operational needs", "description": "Required approval time" }, { "field": "approvalFrequency", "source": "P2 transaction volume", "description": "How often approvals needed" } ], "implementationComplexity": "medium", "examples": { "note": "Large NGO multi-level governance", "references": [ { "name": "WFP Building Blocks", "url": "https://www.wfp.org/building-blocks", "solved": "Transferred cash to refugee populations at scale, fast and at low cost" }, { "name": "Start Network", "url": "https://startnetwork.org/blockchain", "solved": "Accelerated emergency funding payouts with enhanced transparency" } ] }, "solutionQuestions": [ { "id": "approval-chain-length", "type": "select", "options": [ { "label": "2 approvers (maker-checker)", "value": "two" }, { "label": "3 approvers (sequential)", "value": "three" }, { "label": "4+ approvers (complex hierarchy)", "value": "complex" }, { "label": "Varies by amount and type", "value": "varies" } ], "propertyMapping": { "two": { "technologies": [ "2-of-N multi-signature wallet" ], "technologyProperties": { "signingThreshold": "2-of-2 or 2-of-3", "approvalFlow": "Parallel" } }, "three": { "technologies": [ "3-of-N multi-signature wallet", "Sequential approval engine" ], "technologyProperties": { "signingThreshold": "3-of-4 or 3-of-5", "approvalFlow": "Sequential or parallel" } }, "complex": { "technologies": [ "Hierarchical multi-sig", "Approval routing engine" ], "technologyProperties": { "signingThreshold": "M-of-N with role hierarchy", "approvalFlow": "Role-based sequential" } }, "varies": { "technologies": [ "Policy-driven approval engine", "Dynamic multi-sig" ], "technologyProperties": { "signingThreshold": "Dynamic \u2014 amount/type based", "approvalFlow": "Policy-routed" } } }, "prefillFrom": null, "briefSection": "Governance and controls", "text": "How many approvers are typically needed for financial transactions?", "ngoText": "How many approvers are typically needed for financial transactions?" }, { "id": "timezone-spread", "type": "select", "options": [ { "label": "Same or adjacent time zones (1-3 hours difference)", "value": "adjacent" }, { "label": "Moderate spread (4-8 hours)", "value": "moderate" }, { "label": "Global spread (8-12+ hours)", "value": "global" } ], "propertyMapping": { "adjacent": { "technologies": [ "Multi-sig wallet with mobile signing" ], "technologyProperties": { "timezoneHandling": "Minor \u2014 synchronous approval feasible", "timeoutMechanism": "Short timeout (hours)" } }, "moderate": { "technologies": [ "Asynchronous approval queue", "Mobile push notifications" ], "technologyProperties": { "timezoneHandling": "Async approval with notifications", "timeoutMechanism": "Medium timeout (12-24 hours)" } }, "global": { "technologies": [ "Asynchronous multi-sig", "Deadline-based escalation", "Substitute approver mechanism" ], "technologyProperties": { "timezoneHandling": "Fully async with escalation", "timeoutMechanism": "Long timeout with delegate fallback" } } }, "prefillFrom": null, "briefSection": "Governance and controls", "text": "Across how many time zones do approvers operate?", "ngoText": "Across how many time zones do approvers operate?" }, { "id": "approval-urgency", "type": "select", "options": [ { "label": "Rarely, standard timelines are fine", "value": "rarely" }, { "label": "Sometimes, emergency situations arise", "value": "sometimes" }, { "label": "Frequently, operational pace demands speed", "value": "frequently" } ], "propertyMapping": { "rarely": { "technologies": [ "Standard multi-sig wallet" ], "technologyProperties": { "expeditedPath": "Not required", "overrideMechanism": "None" } }, "sometimes": { "technologies": [ "Multi-sig with emergency override", "Reduced-quorum emergency mode" ], "technologyProperties": { "expeditedPath": "Emergency reduced-quorum", "overrideMechanism": "Pre-authorised emergency key" } }, "frequently": { "technologies": [ "Tiered approval thresholds", "Auto-approve below limit" ], "technologyProperties": { "expeditedPath": "Threshold-based auto-approve", "overrideMechanism": "Policy-driven fast track" } } }, "prefillFrom": null, "briefSection": "Governance and controls", "text": "How often do you need expedited approvals?", "ngoText": "How often do you need expedited approvals?", "hidden": true }, { "id": "approval-device", "type": "multiselect", "options": [ { "label": "Desktop/laptop (web browser)", "value": "desktop" }, { "label": "Mobile phone (app)", "value": "mobile-app" }, { "label": "Hardware security key", "value": "hardware-key" }, { "label": "Email/SMS confirmation", "value": "email-sms" } ], "propertyMapping": { "desktop": { "technologies": [ "Web-based signing interface" ], "technologyProperties": { "signingInterface": "Browser-based", "securityLevel": "Standard (password + 2FA)" } }, "mobile-app": { "technologies": [ "Mobile signing application" ], "technologyProperties": { "signingInterface": "Native mobile app", "securityLevel": "Biometric + PIN" } }, "hardware-key": { "technologies": [ "Hardware key integration" ], "technologyProperties": { "signingInterface": "Hardware security key", "securityLevel": "Hardware-grade (highest)" } }, "email-sms": { "technologies": [ "Email/SMS approval workflow" ], "technologyProperties": { "signingInterface": "Email link or SMS code", "securityLevel": "Basic (email/SMS verification)" } } }, "prefillFrom": null, "briefSection": "End-user interface", "text": "What devices do your approvers typically use to authorise transactions?", "ngoText": "What devices do your approvers typically use to authorise transactions?" }, { "id": "sq-UC-A-013-001", "type": "single-select", "options": [ { "value": "delegate-authority", "label": "Delegate to designated proxy" }, { "value": "escalate-up", "label": "Escalate to supervisor" }, { "value": "timeout-approve", "label": "Auto-approve after timeout" }, { "value": "timeout-reject", "label": "Auto-reject after timeout" }, { "value": "quorum-based", "label": "Quorum-based alternative approval" } ], "propertyMapping": { "delegate-authority": { "technologies": [ "delegation-system", "proxy-management" ], "technologyProperties": {} }, "escalate-up": { "technologies": [ "escalation-rules", "hierarchy-routing" ], "technologyProperties": {} }, "timeout-approve": { "technologies": [ "timeout-logic", "auto-approval" ], "technologyProperties": {} }, "timeout-reject": { "technologies": [ "timeout-logic", "auto-rejection" ], "technologyProperties": {} }, "quorum-based": { "technologies": [ "voting-system", "quorum-calculation" ], "technologyProperties": {} } }, "briefSection": "operations", "text": "What should happen when an approver is unavailable within the required timeframe?", "ngoText": "What should happen when an approver is unavailable within the required timeframe?" }, { "id": "smart-contract-approach", "type": "select", "options": [ { "label": "Multiple people must approve before funds are released", "value": "multiple-people-must-approve-before-fund" }, { "label": "Automatic release when predefined conditions are met (e.g., if X then release Y)", "value": "automatic-release-when-predefined-condit" }, { "label": "Funds held in escrow until milestones are confirmed", "value": "funds-held-in-escrow-until-milestones-ar" }, { "label": "Not sure, need guidance on payment controls", "value": "not-sure-need-guidance-on-payment-contro" } ], "propertyMapping": { "multi-sig": { "technologies": [ "Multi-signature smart contracts", "Approval threshold manager", "Transaction executor" ], "technologyProperties": { "contractType": "Multi-sig approval", "automationLevel": "Semi-automated (requires signatures)", "upgradeability": "Proxy pattern for upgrades" } }, "rule-based": { "technologies": [ "Rule-based smart contracts", "Condition evaluation engine", "Automated execution service" ], "technologyProperties": { "contractType": "Conditional automation", "automationLevel": "Fully automated when conditions met", "upgradeability": "Configurable rule parameters" } }, "escrow": { "technologies": [ "Escrow smart contracts", "Condition verification oracle", "Release controller" ], "technologyProperties": { "contractType": "Escrow with conditional release", "automationLevel": "Automated release on condition verification", "upgradeability": "New escrow per engagement" } }, "guidance-needed": { "technologies": [ "Smart contract framework", "Contract management service" ], "technologyProperties": { "contractType": "To be determined", "automationLevel": "To be determined", "upgradeability": "To be determined" } } }, "prefillFrom": null, "briefSection": "Smart contracts", "text": "What type of smart contract automation is needed?", "ngoText": "What type of smart contract automation is needed?", "hidden": true, "question": "What approval or release rules do you need for payments?" }, { "id": "coordination-layer-approach", "type": "select", "options": [ { "label": "Shared workspace with real-time multi-party visibility", "value": "shared-workspace" }, { "label": "Event-driven notifications across organisations", "value": "event-driven" }, { "label": "Scheduled data sync between partner systems", "value": "scheduled-sync" }, { "label": "system-connected integration between organisation systems", "value": "api-based" } ], "propertyMapping": { "shared-workspace": { "technologies": [ "Multi-party coordination layer", "Shared workspace platform", "Real-time data updates" ], "technologyProperties": { "coordinationMethod": "Shared real-time workspace", "dataSharing": "Full visibility within shared context", "latency": "Real-time" } }, "event-driven": { "technologies": [ "Event-driven coordination layer", "Cross-org notification service", "Event broker" ], "technologyProperties": { "coordinationMethod": "Event-driven notifications", "dataSharing": "Event-specific data only", "latency": "Near-real-time" } }, "scheduled-sync": { "technologies": [ "Scheduled coordination layer", "Batch data sync service", "Reconciliation engine" ], "technologyProperties": { "coordinationMethod": "Periodic batch sync", "dataSharing": "Agreed data sets", "latency": "Batch interval (hourly/daily)" } }, "api-based": { "technologies": [ "API coordination layer", "Organisation API gateway", "Data exchange protocol" ], "technologyProperties": { "coordinationMethod": "API-based request/response", "dataSharing": "Per-request basis", "latency": "On-demand" } } }, "prefillFrom": null, "briefSection": "Multi-party coordination", "text": "How do multiple parties currently coordinate decisions and actions?", "ngoText": "How do multiple parties currently coordinate decisions and actions?" } ], "complexityFactors": { "relationships": 2, "operationalChange": 2, "dataCompliance": 1 }, "suggestedCriteria": [ { "id": "SC-MULTI-SIG", "name": "Multi-Signature Configuration", "description": "This measures how configurable the multi-signature approval requirements are. Different transaction types and amounts need different approval combinations (e.g., 2-of-3 for routine, 3-of-5 for large).", "weight": 0.3, "ratingGuide": { "5": "Fully configurable M-of-N signatures. Per-transaction-type rules. Per-amount-threshold rules. Named signer groups. Signer substitution.", "4": "Good M-of-N configuration. Amount thresholds. Named signers. Basic substitution.", "3": "Fixed M-of-N options (2-of-3, 3-of-5). Amount thresholds. No substitution.", "2": "Dual signature only. Single threshold. No flexibility.", "1": "No multi-signature capability. Single-signer authorisation." } }, { "id": "SC-TIMEZONE", "name": "Asynchronous Approval Across Time Zones", "description": "Approvers can sign at different times without holding up the workflow. With signers in New York, Nairobi, and Bangkok, waiting for simultaneous availability is impractical.", "weight": 0.25, "ratingGuide": { "5": "Fully asynchronous. Approvers sign when available. Auto-expiry with re-routing. Status visible to all parties. Mobile push notifications.", "4": "Asynchronous signing. Good notification system. Status tracking. Auto-reminders.", "3": "Asynchronous with email notifications. Manual status checking. Basic reminders.", "2": "Some asynchronous support but timeouts cause restarts. Limited notifications.", "1": "Requires near-simultaneous signing. Workflow resets if not completed in one session." } }, { "id": "SC-DELEGATION", "name": "Delegation & Escalation", "description": "Approvers can delegate authority when travelling or unavailable. Without delegation, a single unavailable signer can block critical payments for days.", "weight": 0.2, "ratingGuide": { "5": "Formal delegation with date ranges. Delegate sees pending items. Original signer can override. Audit trail of delegations. Automatic escalation if no action within deadline.", "4": "Delegation available. Good escalation rules. Audit trail of delegated approvals.", "3": "Basic delegation. Manual escalation. Record of who approved (original or delegate).", "2": "Informal delegation (share credentials). No formal delegation mechanism.", "1": "No delegation. Signer must be personally available." } }, { "id": "SC-MOBILE-APPROVE", "name": "Mobile Approval Capability", "description": "Approvers can review and authorise transactions from their phone. Senior staff are frequently travelling. Mobile approval is essential for timely processing.", "weight": 0.15, "ratingGuide": { "5": "Full-featured mobile app. Review transaction details, attachments, and context. Biometric or PIN approval. Batch approve for routine items.", "4": "Good mobile app. Review and approve. Push notifications. PIN security.", "3": "Mobile web interface. Review and approve. Email notification links.", "2": "Email-based approval (approve/reject links). Limited transaction detail visible.", "1": "Desktop only. No mobile approval capability." } }, { "id": "SC-WORKFLOW-AUDIT", "name": "Approval Audit Trail", "description": "Every approval decision is recorded with timestamp, device, and signer identity. For financial governance, the approval trail is as important as the transaction itself.", "weight": 0.1, "ratingGuide": { "5": "Cryptographically signed approvals. Timestamp, device, location (optional), and signer identity recorded. Tamper-evident. Exportable for audit.", "4": "Detailed approval records. Timestamp and signer. Good export capability.", "3": "Approval records with timestamp. Basic signer identification. Standard export.", "2": "Approval/rejection recorded. Limited metadata. Manual export.", "1": "Approval status only. No detailed trail of who approved when." } } ], "procurement": { "marketMaturity": "mature", "primaryMode": "off-the-shelf", "alternativeModes": [ "rfq" ], "reasoning": "Workflow and approval SaaS market is mature.", "exampleProductCategories": [ "workflow-saas", "approval-routing-platform" ], "partnerChannels": [], "lastReviewed": "2026-05-01" } }, { "id": "UC-A-014", "name": "Restricted vs unrestricted fund segregation and tracking", "category": "A", "subcategory": "Treasury Operations", "description": "Keep each donor's restricted funds apart from general funds, and show at any time that money was spent only for its agreed purpose.", "bCriteria": [ "B1", "B3", "B7" ], "requiredComponents": [ { "component": "smart-contracts", "description": "Fund restriction logic" }, { "component": "accounting-integration", "description": "Fund allocation tracking" }, { "component": "reporting-module", "description": "Restricted fund reporting" }, { "component": "access-control", "description": "Spending authorization rules" } ], "conditionalComponents": [ { "component": "audit-mechanism", "condition": "For compliance audit trail" } ], "crossCategoryDependencies": [], "p2TriggerConditions": { "description": "Activated when P2 shows multiple donor funding types + restricted fund complexity + tracking burden", "rangeSignals": [ "fundTypes >= 3", "restrictedFunds >= true", "donorVariability >= high" ] }, "contextFieldsTemplate": [ { "field": "fundTypes", "source": "P0 funding model", "description": "Types of restricted funds" }, { "field": "donorRestrictions", "source": "P0 grant agreements", "description": "Specific restrictions" }, { "field": "trackingGranularity", "source": "P2 reporting needs", "description": "Level of tracking detail" }, { "field": "spendingRules", "source": "P0 policies", "description": "Spending approval rules" } ], "implementationComplexity": "medium", "examples": { "note": "Complex NGO fund management", "references": [ { "name": "Disberse", "url": "https://www.nesta.org.uk/feature/new-radicals-2018/disberse/", "solved": "Traced international aid fund transfers reducing intermediary costs" }, { "name": "UNICEF CryptoFund", "url": "https://www.unicef.org/innovation/stories/unicef-cryptofund", "solved": "Funded global tech startups addressing child welfare, transparently and at low cost" } ] }, "solutionQuestions": [ { "id": "fund-types", "type": "multiselect", "options": [ { "label": "Restricted by donor/grant", "value": "donor-restricted" }, { "label": "Restricted by programme/project", "value": "programme-restricted" }, { "label": "Restricted by geography/country", "value": "geography-restricted" }, { "label": "Restricted by expense category", "value": "category-restricted" }, { "label": "Time-restricted (spend by date)", "value": "time-restricted" }, { "label": "Unrestricted / core funding", "value": "unrestricted" } ], "propertyMapping": { "donor-restricted": { "technologies": [ "Smart contract fund tagging", "Per-donor wallet segregation" ], "technologyProperties": { "restrictionType": "Donor-specific", "enforcementMethod": "Smart contract spending rules" } }, "programme-restricted": { "technologies": [ "Smart contract programme tagging" ], "technologyProperties": { "restrictionType": "Programme-specific", "enforcementMethod": "Programme-scoped wallets/tags" } }, "geography-restricted": { "technologies": [ "Smart contract geography rules" ], "technologyProperties": { "restrictionType": "Geography-specific", "enforcementMethod": "Country/region-locked spending" } }, "category-restricted": { "technologies": [ "Smart contract category enforcement" ], "technologyProperties": { "restrictionType": "Category-specific", "enforcementMethod": "Expense category validation" } }, "time-restricted": { "technologies": [ "Smart contract time-lock", "Expiry alerting" ], "technologyProperties": { "restrictionType": "Time-bound", "enforcementMethod": "Time-locked with expiry notification" } }, "unrestricted": { "technologies": [ "Unrestricted fund pool" ], "technologyProperties": { "restrictionType": "None", "enforcementMethod": "Flexible allocation" } } }, "prefillFrom": null, "briefSection": "Payment logic", "text": "What types of fund restrictions do you need to enforce?", "ngoText": "What types of fund restrictions do you need to enforce?" }, { "id": "restriction-overlap", "type": "select", "options": [ { "label": "Yes, complex allocation across multiple restricted funds", "value": "complex-overlap" }, { "label": "Sometimes, occasional split charges", "value": "occasional" }, { "label": "No, each transaction is from a single fund source", "value": "no-overlap" } ], "propertyMapping": { "complex-overlap": { "technologies": [ "Multi-fund allocation engine", "Split transaction support" ], "technologyProperties": { "allocationModel": "Multi-fund split with rules", "complexity": "High \u2014 automated allocation calculation" } }, "occasional": { "technologies": [ "Split transaction support" ], "technologyProperties": { "allocationModel": "Optional split capability", "complexity": "Medium" } }, "no-overlap": { "technologies": [ "Single-source transaction model" ], "technologyProperties": { "allocationModel": "Single fund per transaction", "complexity": "Low" } } }, "prefillFrom": null, "briefSection": "Payment logic", "text": "Do fund restrictions overlap (e.g., a single spend charged to multiple restricted funds)?", "ngoText": "Do fund restrictions overlap (e.g., a single spend charged to multiple restricted funds)?" }, { "id": "fund-enforcement-level", "type": "select", "options": [ { "label": "Hard block: prevent any transaction violating restrictions", "value": "hard-block" }, { "label": "Soft warning: flag violations but allow with override", "value": "soft-warning" }, { "label": "Post-hoc detection: flag after the fact for review", "value": "post-hoc" } ], "propertyMapping": { "hard-block": { "technologies": [ "Automated enforcement", "Transaction validation layer" ], "technologyProperties": { "enforcementMode": "Preventive \u2014 transaction blocked", "overrideCapability": "Multi-sig override only" } }, "soft-warning": { "technologies": [ "Policy warning engine", "Override workflow" ], "technologyProperties": { "enforcementMode": "Warning with override option", "overrideCapability": "Authorised override with audit log" } }, "post-hoc": { "technologies": [ "Policy violation detection", "Alerting engine" ], "technologyProperties": { "enforcementMode": "Detective \u2014 post-transaction flagging", "overrideCapability": "N/A \u2014 correction workflow" } } }, "prefillFrom": null, "briefSection": "Governance and controls", "text": "Should the system prevent restricted fund misuse or just flag it?", "ngoText": "Should the system prevent restricted fund misuse or just flag it?" }, { "id": "sq-UC-A-014-001", "type": "single-select", "options": [ { "value": "auto-unrestrict-on-date", "label": "Auto-unrestrict on expiry date" }, { "value": "require-donor-approval", "label": "Require donor approval" }, { "value": "archive-and-return", "label": "Archive and return to donor" }, { "value": "roll-forward", "label": "Roll forward restriction period" }, { "value": "notify-and-await", "label": "Notify and await decision" } ], "propertyMapping": { "auto-unrestrict-on-date": { "technologies": [ "scheduled-tasks", "date-based-logic" ], "technologyProperties": {} }, "require-donor-approval": { "technologies": [ "approval-workflow", "donor-notification" ], "technologyProperties": {} }, "archive-and-return": { "technologies": [ "archival-system", "return-process" ], "technologyProperties": {} }, "roll-forward": { "technologies": [ "renewal-logic", "date-management" ], "technologyProperties": {} }, "notify-and-await": { "technologies": [ "notification-system", "workflow-queue" ], "technologyProperties": {} } }, "briefSection": "requirements", "text": "How are fund restriction expiries or modifications currently handled?", "ngoText": "How are fund restriction expiries or modifications currently handled?" }, { "id": "accounting-integration", "type": "select", "options": [ { "label": "Direct integration with your existing accounting software", "value": "direct-erp" }, { "label": "Export-based: generate reports compatible with our accounting system", "value": "export-based" }, { "label": "Standalone ledger with manual reconciliation", "value": "standalone" }, { "label": "Not sure, need guidance on accounting integration", "value": "guidance-needed" } ], "propertyMapping": { "direct-erp": { "technologies": [ "Accounting system connection", "Automatic record updates", "Account structure alignment" ], "technologyProperties": { "integrationMethod": "Real-time connection", "reconciliation": "Automated", "reportFormat": "Compatible with your accounting system" } }, "export-based": { "technologies": [ "Accounting export module", "Report generation engine", "CSV/spreadsheet export service" ], "technologyProperties": { "integrationMethod": "Scheduled export (CSV/spreadsheet)", "reconciliation": "Semi-automated", "reportFormat": "Standard CSV/spreadsheet" } }, "standalone": { "technologies": [ "Standalone accounting ledger", "Manual reconciliation tools" ], "technologyProperties": { "integrationMethod": "Manual import/export", "reconciliation": "Manual", "reportFormat": "PDF/spreadsheet reports" } }, "guidance-needed": { "technologies": [ "Accounting integration framework" ], "technologyProperties": { "integrationMethod": "To be determined", "reconciliation": "To be determined", "reportFormat": "To be determined" } } }, "prefillFrom": null, "briefSection": "Financial integration", "text": "How should this solution integrate with your existing accounting or financial systems?", "ngoText": "How should this solution integrate with your existing accounting or financial systems?" }, { "id": "reporting-approach", "type": "select", "options": [ { "label": "Automated donor/funder reporting with scheduled delivery", "value": "automated-donor" }, { "label": "Self-service dashboard with custom report builder", "value": "self-service" }, { "label": "Regulatory compliance reporting (government/authority)", "value": "regulatory" }, { "label": "Multi-audience reporting (donors, government, community)", "value": "multi-audience" } ], "propertyMapping": { "automated-donor": { "technologies": [ "Automated reporting module", "Donor report template engine", "Scheduled report delivery service" ], "technologyProperties": { "reportAudience": "Donors and funders", "frequency": "Scheduled (monthly/quarterly)", "format": "PDF/spreadsheet with blockchain verification" } }, "self-service": { "technologies": [ "Self-service reporting module", "Custom report builder", "Data visualisation engine" ], "technologyProperties": { "reportAudience": "Internal staff and managers", "frequency": "On-demand", "format": "Interactive dashboard + export" } }, "regulatory": { "technologies": [ "Regulatory reporting module", "Compliance report generator", "Authority submission gateway" ], "technologyProperties": { "reportAudience": "Government and regulatory authorities", "frequency": "As required by regulation", "format": "Authority-specified format" } }, "multi-audience": { "technologies": [ "Multi-audience reporting module", "Role-based report engine", "Report distribution service" ], "technologyProperties": { "reportAudience": "Multiple stakeholders", "frequency": "Varies by audience", "format": "Tailored per audience" } } }, "prefillFrom": null, "briefSection": "Reporting", "text": "What reporting capabilities does this solution need?", "ngoText": "What reporting capabilities does this solution need?" }, { "id": "access-control-approach", "type": "select", "options": [ { "label": "Role-based access control (RBAC)", "value": "rbac" }, { "label": "Attribute-based access control (ABAC)", "value": "abac" }, { "label": "Multi-signature access (requires multiple approvals)", "value": "multi-sig" }, { "label": "Not sure, need guidance", "value": "guidance-needed" } ], "propertyMapping": { "rbac": { "technologies": [ "Role-based access control system", "Role management service", "Access audit logger" ], "technologyProperties": { "accessModel": "Role-based (RBAC)", "granularity": "Per-role permissions", "auditability": "Full role assignment audit trail" } }, "abac": { "technologies": [ "Attribute-based access control system", "Policy decision engine", "Access audit logger" ], "technologyProperties": { "accessModel": "Attribute-based (ABAC)", "granularity": "Fine-grained attribute policies", "auditability": "Full policy evaluation audit trail" } }, "multi-sig": { "technologies": [ "Multi-signature access control", "Approval workflow engine", "Access audit logger" ], "technologyProperties": { "accessModel": "Multi-signature", "granularity": "Per-action approval thresholds", "auditability": "All approval actions on-chain" } }, "guidance-needed": { "technologies": [ "Access control framework", "Access audit logger" ], "technologyProperties": { "accessModel": "To be determined", "granularity": "To be determined", "auditability": "To be determined" } } }, "prefillFrom": null, "briefSection": "Access control", "text": "What type of access control is needed?", "ngoText": "What type of access control is needed?" } ], "complexityFactors": { "relationships": 1, "operationalChange": 2, "dataCompliance": 1 }, "suggestedCriteria": [ { "id": "SC-FUND-CLASS", "name": "Fund Classification Granularity", "description": "The provider can handle the full complexity of NGO fund classifications. Beyond restricted/unrestricted, there are temporarily restricted, board-designated, and donor-specific sub-categories.", "weight": 0.3, "ratingGuide": { "5": "Unlimited fund classifications with nesting (restricted \u2192 donor \u2192 grant \u2192 activity). Custom attributes per fund. Automatic restriction enforcement based on fund type.", "4": "Good classification depth. Multiple restriction levels. Custom attributes. Basic enforcement.", "3": "Restricted/unrestricted/designated categories. Per-donor tagging. Manual enforcement.", "2": "Simple restricted/unrestricted split. Manual tracking of sub-categories.", "1": "No fund classification. All funds treated as single pool." } }, { "id": "SC-SEGREGATION-ENFORCE", "name": "Automatic Segregation Enforcement", "description": "The provider prevents restricted fund misuse automatically. Spending restricted funds on unapproved purposes is a serious compliance violation. It shouldn't rely on human memory.", "weight": 0.25, "ratingGuide": { "5": "Hard blocks on spending restricted funds outside approved categories. Automated checking at point of entry. Override requires documented approval with audit trail.", "4": "Soft blocks with warning and approval required for exceptions. Good automated checking.", "3": "Warnings when spending approaches category limits. Manual verification encouraged.", "2": "Fund codes assigned but no spending enforcement. Post-hoc review only.", "1": "No enforcement mechanism. Segregation is purely in external accounting." } }, { "id": "SC-FUND-REPORTING", "name": "Fund-Level Financial Reporting", "description": "The provider can generate financial statements per fund classification. Donors and boards require separate reporting for restricted and unrestricted funds.", "weight": 0.2, "ratingGuide": { "5": "Per-fund income statements, balance sheets, and cash flow. Consolidated view with fund breakdown. FASB/IFRS compliant fund accounting reports.", "4": "Good per-fund reporting. Income and expenditure by fund. Consolidated views.", "3": "Per-fund expenditure reports. Manual consolidation. Basic income tracking by fund.", "2": "Transactions filterable by fund. No per-fund financial statements.", "1": "No fund-level reporting. All reporting at organisational level only." } }, { "id": "SC-INTEREST-ALLOC", "name": "Interest & Indirect Cost Allocation", "description": "The provider handles interest allocation and indirect cost distribution across funds. Interest earned on restricted funds may be restricted too, and overhead must be fairly apportioned.", "weight": 0.15, "ratingGuide": { "5": "Automatic interest allocation per fund balance. Configurable indirect cost rate allocation. NICRA/OHCR rate support. Year-end allocation tools.", "4": "Good interest allocation. Configurable overhead rates. Semi-automatic distribution.", "3": "Manual interest allocation supported. Basic overhead rate calculation.", "2": "Interest tracking available. Manual allocation. No overhead rate tools.", "1": "No interest or overhead allocation capability." } }, { "id": "SC-RELEASE-TRACKING", "name": "Fund Release & Restriction Tracking", "description": "The provider tracks when fund restrictions are released (time-based or purpose-based). Temporarily restricted funds become unrestricted when conditions are met. This must be tracked for accurate reporting.", "weight": 0.1, "ratingGuide": { "5": "Automatic restriction release tracking. Time-based auto-release. Purpose-based release with documentation. Reclassification audit trail.", "4": "Good release tracking. Semi-automatic for time-based. Manual for purpose-based.", "3": "Manual release recording. Reclassification journals supported. Basic audit trail.", "2": "Manual reclassification. Limited tracking of when restrictions were released.", "1": "No release tracking. Restriction status changes not recorded." } } ], "procurement": { "marketMaturity": "mature", "primaryMode": "off-the-shelf", "alternativeModes": [ "rfq" ], "reasoning": "Restricted-fund tracking standard in modern grants management products.", "exampleProductCategories": [ "grants-management-platform", "fund-accounting-saas" ], "partnerChannels": [], "lastReviewed": "2026-05-01" } }, { "id": "UC-A-015", "name": "Multi-year grant milestone-based disbursement automation", "category": "A", "subcategory": "Cross-Border Payments and Transfers", "description": "Release each grant instalment once the agreed milestone is confirmed, so funding does not stall while someone checks the evidence.", "bCriteria": [ "B3", "B5", "B7" ], "requiredComponents": [ { "component": "smart-contracts", "description": "Milestone-based payment logic" }, { "component": "payment-rails", "description": "Automated settlement" }, { "component": "stablecoin", "description": "Disbursement currency" }, { "component": "reporting-module", "description": "Milestone tracking" }, { "component": "decision-audit-trail", "description": "Milestone approval records" } ], "conditionalComponents": [ { "component": "oracle-data", "condition": "If milestone verification requires external data" }, { "component": "identity-verification", "condition": "If grant recipient KYC needed", "linksTo": "UC-B-024" } ], "crossCategoryDependencies": [ "UC-C-044 if beneficiary data deduplication needed" ], "p2TriggerConditions": { "description": "Activated when P2 shows multi-year grants + milestone-based funding + automation interest", "rangeSignals": [ "grantDuration >= 2+ years", "milestoneBased >= true", "automationInterest >= high" ] }, "contextFieldsTemplate": [ { "field": "grantValue", "source": "P0 grants", "description": "Total grant amount" }, { "field": "milestoneCount", "source": "P2 grant terms", "description": "Number of milestones" }, { "field": "milestoneDuration", "source": "P2 grant schedule", "description": "Time between milestones" }, { "field": "verificationProcess", "source": "P2 M&E practices", "description": "How milestones are verified" } ], "implementationComplexity": "medium-high", "examples": { "note": "Large grant management with conditions", "references": [ { "name": "Disberse", "url": "https://www.nesta.org.uk/feature/new-radicals-2018/disberse/", "solved": "Traced international aid fund transfers reducing intermediary costs" }, { "name": "Start Network", "url": "https://startnetwork.org/blockchain", "solved": "Accelerated emergency funding payouts with enhanced transparency" } ] }, "solutionQuestions": [ { "id": "corridor-count", "type": "select", "options": [ { "label": "Single country", "value": "single" }, { "label": "2\u20133 countries", "value": "2-3" }, { "label": "4\u20135 countries", "value": "4-5" }, { "label": "More than 5 countries", "value": "5-plus" } ], "propertyMapping": { "single": { "technologies": [ "Single-corridor fiat on-ramp" ], "technologyProperties": { "corridorComplexity": "Single origination country", "multiRailNeeded": "No" } }, "2-3": { "technologies": [ "Multi-corridor fiat on-ramp gateway" ], "technologyProperties": { "corridorComplexity": "2\u20133 origination countries", "multiRailNeeded": "Yes \u2014 2-3 payment rails" } }, "4-5": { "technologies": [ "Multi-corridor fiat on-ramp gateway" ], "technologyProperties": { "corridorComplexity": "4\u20135 origination countries", "multiRailNeeded": "Yes \u2014 4-5 payment rails" } }, "5-plus": { "technologies": [ "Enterprise multi-corridor on-ramp gateway" ], "technologyProperties": { "corridorComplexity": "5+ origination countries", "multiRailNeeded": "Yes \u2014 enterprise-grade multi-rail" } } }, "prefillFrom": null, "briefSection": "Payment rail requirements", "text": "How many countries does your organisation send transfer funds from?", "ngoText": "How many countries does your organisation send transfer funds from?" }, { "id": "origination-country-1", "type": "select", "options": [ { "label": "United States", "value": "united-states" }, { "label": "United Kingdom", "value": "united-kingdom" }, { "label": "Germany", "value": "germany" }, { "label": "Netherlands", "value": "netherlands" }, { "label": "Switzerland", "value": "switzerland" }, { "label": "Belgium", "value": "belgium" }, { "label": "France", "value": "france" }, { "label": "Sweden", "value": "sweden" }, { "label": "Norway", "value": "norway" }, { "label": "Denmark", "value": "denmark" }, { "label": "Canada", "value": "canada" }, { "label": "Australia", "value": "australia" }, { "label": "Japan", "value": "japan" }, { "label": "Ireland", "value": "ireland" }, { "label": "Italy", "value": "italy" }, { "label": "Spain", "value": "spain" }, { "label": "Austria", "value": "austria" }, { "label": "Finland", "value": "finland" }, { "label": "Luxembourg", "value": "luxembourg" }, { "label": "South Korea", "value": "south-korea" }, { "label": "New Zealand", "value": "new-zealand" }, { "label": "United Arab Emirates", "value": "united-arab-emirates" }, { "label": "Singapore", "value": "singapore" }, { "label": "Other", "value": "other" } ], "propertyMapping": { "united-states": { "technologies": [ "ACH/wire fiat on-ramp" ], "technologyProperties": { "onRampType": "ACH/Fedwire bank transfer", "onRampRegion": "United States", "settlementRail": "ACH / Fedwire" } }, "united-kingdom": { "technologies": [ "UK Faster Payments on-ramp" ], "technologyProperties": { "onRampType": "Faster Payments bank transfer", "onRampRegion": "United Kingdom", "settlementRail": "FPS / BACS" } }, "germany": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "netherlands": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "switzerland": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SIC/SEPA bank transfer", "onRampRegion": "Switzerland/EU", "settlementRail": "SIC / SEPA Credit Transfer" } }, "belgium": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "france": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "sweden": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "norway": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA-adjacent bank transfer", "onRampRegion": "EEA", "settlementRail": "SEPA Credit Transfer" } }, "denmark": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "canada": { "technologies": [ "Canadian EFT on-ramp" ], "technologyProperties": { "onRampType": "Interac/EFT bank transfer", "onRampRegion": "Canada", "settlementRail": "Interac / EFT" } }, "australia": { "technologies": [ "Australian NPP on-ramp" ], "technologyProperties": { "onRampType": "NPP bank transfer", "onRampRegion": "Australia", "settlementRail": "NPP / BECS" } }, "japan": { "technologies": [ "Japanese Zengin on-ramp" ], "technologyProperties": { "onRampType": "Zengin bank transfer", "onRampRegion": "Japan", "settlementRail": "Zengin System" } }, "ireland": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "italy": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "spain": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "austria": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "finland": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "luxembourg": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "south-korea": { "technologies": [ "Korean banking on-ramp" ], "technologyProperties": { "onRampType": "KFTC bank transfer", "onRampRegion": "South Korea", "settlementRail": "KFTC / BOK-Wire" } }, "new-zealand": { "technologies": [ "NZ banking on-ramp" ], "technologyProperties": { "onRampType": "SBI bank transfer", "onRampRegion": "New Zealand", "settlementRail": "SBI / ESAS" } }, "united-arab-emirates": { "technologies": [ "UAE banking on-ramp" ], "technologyProperties": { "onRampType": "UAEFTS bank transfer", "onRampRegion": "United Arab Emirates", "settlementRail": "UAEFTS / IPP" } }, "singapore": { "technologies": [ "Singapore FAST on-ramp" ], "technologyProperties": { "onRampType": "FAST bank transfer", "onRampRegion": "Singapore", "settlementRail": "FAST / MEPS+" } }, "other": { "technologies": [ "Regional fiat on-ramp" ], "technologyProperties": { "onRampType": "Local rail bank transfer", "onRampRegion": "Region-specific", "settlementRail": "Local payment network" } } }, "showIf": { "questionId": "corridor-count", "minValue": "single" }, "prefillFrom": null, "briefSection": "Payment rail requirements", "text": "Which country do you most frequently initiate transfers from?", "ngoText": "Which country do you most frequently initiate transfers from?" }, { "id": "origination-country-2", "type": "select", "options": [ { "label": "United States", "value": "united-states" }, { "label": "United Kingdom", "value": "united-kingdom" }, { "label": "Germany", "value": "germany" }, { "label": "Netherlands", "value": "netherlands" }, { "label": "Switzerland", "value": "switzerland" }, { "label": "Belgium", "value": "belgium" }, { "label": "France", "value": "france" }, { "label": "Sweden", "value": "sweden" }, { "label": "Norway", "value": "norway" }, { "label": "Denmark", "value": "denmark" }, { "label": "Canada", "value": "canada" }, { "label": "Australia", "value": "australia" }, { "label": "Japan", "value": "japan" }, { "label": "Ireland", "value": "ireland" }, { "label": "Italy", "value": "italy" }, { "label": "Spain", "value": "spain" }, { "label": "Austria", "value": "austria" }, { "label": "Finland", "value": "finland" }, { "label": "Luxembourg", "value": "luxembourg" }, { "label": "South Korea", "value": "south-korea" }, { "label": "New Zealand", "value": "new-zealand" }, { "label": "United Arab Emirates", "value": "united-arab-emirates" }, { "label": "Singapore", "value": "singapore" }, { "label": "Other", "value": "other" } ], "propertyMapping": { "united-states": { "technologies": [ "ACH/wire fiat on-ramp" ], "technologyProperties": { "onRampType": "ACH/Fedwire bank transfer", "onRampRegion": "United States", "settlementRail": "ACH / Fedwire" } }, "united-kingdom": { "technologies": [ "UK Faster Payments on-ramp" ], "technologyProperties": { "onRampType": "Faster Payments bank transfer", "onRampRegion": "United Kingdom", "settlementRail": "FPS / BACS" } }, "germany": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "netherlands": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "switzerland": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SIC/SEPA bank transfer", "onRampRegion": "Switzerland/EU", "settlementRail": "SIC / SEPA Credit Transfer" } }, "belgium": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "france": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "sweden": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "norway": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA-adjacent bank transfer", "onRampRegion": "EEA", "settlementRail": "SEPA Credit Transfer" } }, "denmark": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "canada": { "technologies": [ "Canadian EFT on-ramp" ], "technologyProperties": { "onRampType": "Interac/EFT bank transfer", "onRampRegion": "Canada", "settlementRail": "Interac / EFT" } }, "australia": { "technologies": [ "Australian NPP on-ramp" ], "technologyProperties": { "onRampType": "NPP bank transfer", "onRampRegion": "Australia", "settlementRail": "NPP / BECS" } }, "japan": { "technologies": [ "Japanese Zengin on-ramp" ], "technologyProperties": { "onRampType": "Zengin bank transfer", "onRampRegion": "Japan", "settlementRail": "Zengin System" } }, "ireland": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "italy": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "spain": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "austria": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "finland": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "luxembourg": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "south-korea": { "technologies": [ "Korean banking on-ramp" ], "technologyProperties": { "onRampType": "KFTC bank transfer", "onRampRegion": "South Korea", "settlementRail": "KFTC / BOK-Wire" } }, "new-zealand": { "technologies": [ "NZ banking on-ramp" ], "technologyProperties": { "onRampType": "SBI bank transfer", "onRampRegion": "New Zealand", "settlementRail": "SBI / ESAS" } }, "united-arab-emirates": { "technologies": [ "UAE banking on-ramp" ], "technologyProperties": { "onRampType": "UAEFTS bank transfer", "onRampRegion": "United Arab Emirates", "settlementRail": "UAEFTS / IPP" } }, "singapore": { "technologies": [ "Singapore FAST on-ramp" ], "technologyProperties": { "onRampType": "FAST bank transfer", "onRampRegion": "Singapore", "settlementRail": "FAST / MEPS+" } }, "other": { "technologies": [ "Regional fiat on-ramp" ], "technologyProperties": { "onRampType": "Local rail bank transfer", "onRampRegion": "Region-specific", "settlementRail": "Local payment network" } } }, "showIf": { "questionId": "corridor-count", "minValue": "2-3" }, "prefillFrom": null, "briefSection": "Payment rail requirements", "text": "Second most common transfer origination country (if applicable)", "ngoText": "Second most common transfer origination country (if applicable)" }, { "id": "origination-country-3", "type": "select", "options": [ { "label": "United States", "value": "united-states" }, { "label": "United Kingdom", "value": "united-kingdom" }, { "label": "Germany", "value": "germany" }, { "label": "Netherlands", "value": "netherlands" }, { "label": "Switzerland", "value": "switzerland" }, { "label": "Belgium", "value": "belgium" }, { "label": "France", "value": "france" }, { "label": "Sweden", "value": "sweden" }, { "label": "Norway", "value": "norway" }, { "label": "Denmark", "value": "denmark" }, { "label": "Canada", "value": "canada" }, { "label": "Australia", "value": "australia" }, { "label": "Japan", "value": "japan" }, { "label": "Ireland", "value": "ireland" }, { "label": "Italy", "value": "italy" }, { "label": "Spain", "value": "spain" }, { "label": "Austria", "value": "austria" }, { "label": "Finland", "value": "finland" }, { "label": "Luxembourg", "value": "luxembourg" }, { "label": "South Korea", "value": "south-korea" }, { "label": "New Zealand", "value": "new-zealand" }, { "label": "United Arab Emirates", "value": "united-arab-emirates" }, { "label": "Singapore", "value": "singapore" }, { "label": "Other", "value": "other" } ], "propertyMapping": { "united-states": { "technologies": [ "ACH/wire fiat on-ramp" ], "technologyProperties": { "onRampType": "ACH/Fedwire bank transfer", "onRampRegion": "United States", "settlementRail": "ACH / Fedwire" } }, "united-kingdom": { "technologies": [ "UK Faster Payments on-ramp" ], "technologyProperties": { "onRampType": "Faster Payments bank transfer", "onRampRegion": "United Kingdom", "settlementRail": "FPS / BACS" } }, "germany": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "netherlands": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "switzerland": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SIC/SEPA bank transfer", "onRampRegion": "Switzerland/EU", "settlementRail": "SIC / SEPA Credit Transfer" } }, "belgium": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "france": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "sweden": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "norway": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA-adjacent bank transfer", "onRampRegion": "EEA", "settlementRail": "SEPA Credit Transfer" } }, "denmark": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "canada": { "technologies": [ "Canadian EFT on-ramp" ], "technologyProperties": { "onRampType": "Interac/EFT bank transfer", "onRampRegion": "Canada", "settlementRail": "Interac / EFT" } }, "australia": { "technologies": [ "Australian NPP on-ramp" ], "technologyProperties": { "onRampType": "NPP bank transfer", "onRampRegion": "Australia", "settlementRail": "NPP / BECS" } }, "japan": { "technologies": [ "Japanese Zengin on-ramp" ], "technologyProperties": { "onRampType": "Zengin bank transfer", "onRampRegion": "Japan", "settlementRail": "Zengin System" } }, "ireland": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "italy": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "spain": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "austria": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "finland": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "luxembourg": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "south-korea": { "technologies": [ "Korean banking on-ramp" ], "technologyProperties": { "onRampType": "KFTC bank transfer", "onRampRegion": "South Korea", "settlementRail": "KFTC / BOK-Wire" } }, "new-zealand": { "technologies": [ "NZ banking on-ramp" ], "technologyProperties": { "onRampType": "SBI bank transfer", "onRampRegion": "New Zealand", "settlementRail": "SBI / ESAS" } }, "united-arab-emirates": { "technologies": [ "UAE banking on-ramp" ], "technologyProperties": { "onRampType": "UAEFTS bank transfer", "onRampRegion": "United Arab Emirates", "settlementRail": "UAEFTS / IPP" } }, "singapore": { "technologies": [ "Singapore FAST on-ramp" ], "technologyProperties": { "onRampType": "FAST bank transfer", "onRampRegion": "Singapore", "settlementRail": "FAST / MEPS+" } }, "other": { "technologies": [ "Regional fiat on-ramp" ], "technologyProperties": { "onRampType": "Local rail bank transfer", "onRampRegion": "Region-specific", "settlementRail": "Local payment network" } } }, "showIf": { "questionId": "corridor-count", "minValue": "2-3" }, "prefillFrom": null, "briefSection": "Payment rail requirements", "text": "Third transfer origination country (if applicable)", "ngoText": "Third transfer origination country (if applicable)" }, { "id": "origination-country-4", "type": "select", "options": [ { "label": "United States", "value": "united-states" }, { "label": "United Kingdom", "value": "united-kingdom" }, { "label": "Germany", "value": "germany" }, { "label": "Netherlands", "value": "netherlands" }, { "label": "Switzerland", "value": "switzerland" }, { "label": "Belgium", "value": "belgium" }, { "label": "France", "value": "france" }, { "label": "Sweden", "value": "sweden" }, { "label": "Norway", "value": "norway" }, { "label": "Denmark", "value": "denmark" }, { "label": "Canada", "value": "canada" }, { "label": "Australia", "value": "australia" }, { "label": "Japan", "value": "japan" }, { "label": "Ireland", "value": "ireland" }, { "label": "Italy", "value": "italy" }, { "label": "Spain", "value": "spain" }, { "label": "Austria", "value": "austria" }, { "label": "Finland", "value": "finland" }, { "label": "Luxembourg", "value": "luxembourg" }, { "label": "South Korea", "value": "south-korea" }, { "label": "New Zealand", "value": "new-zealand" }, { "label": "United Arab Emirates", "value": "united-arab-emirates" }, { "label": "Singapore", "value": "singapore" }, { "label": "Other", "value": "other" } ], "propertyMapping": { "united-states": { "technologies": [ "ACH/wire fiat on-ramp" ], "technologyProperties": { "onRampType": "ACH/Fedwire bank transfer", "onRampRegion": "United States", "settlementRail": "ACH / Fedwire" } }, "united-kingdom": { "technologies": [ "UK Faster Payments on-ramp" ], "technologyProperties": { "onRampType": "Faster Payments bank transfer", "onRampRegion": "United Kingdom", "settlementRail": "FPS / BACS" } }, "germany": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "netherlands": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "switzerland": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SIC/SEPA bank transfer", "onRampRegion": "Switzerland/EU", "settlementRail": "SIC / SEPA Credit Transfer" } }, "belgium": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "france": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "sweden": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "norway": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA-adjacent bank transfer", "onRampRegion": "EEA", "settlementRail": "SEPA Credit Transfer" } }, "denmark": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "canada": { "technologies": [ "Canadian EFT on-ramp" ], "technologyProperties": { "onRampType": "Interac/EFT bank transfer", "onRampRegion": "Canada", "settlementRail": "Interac / EFT" } }, "australia": { "technologies": [ "Australian NPP on-ramp" ], "technologyProperties": { "onRampType": "NPP bank transfer", "onRampRegion": "Australia", "settlementRail": "NPP / BECS" } }, "japan": { "technologies": [ "Japanese Zengin on-ramp" ], "technologyProperties": { "onRampType": "Zengin bank transfer", "onRampRegion": "Japan", "settlementRail": "Zengin System" } }, "ireland": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "italy": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "spain": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "austria": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "finland": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "luxembourg": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "south-korea": { "technologies": [ "Korean banking on-ramp" ], "technologyProperties": { "onRampType": "KFTC bank transfer", "onRampRegion": "South Korea", "settlementRail": "KFTC / BOK-Wire" } }, "new-zealand": { "technologies": [ "NZ banking on-ramp" ], "technologyProperties": { "onRampType": "SBI bank transfer", "onRampRegion": "New Zealand", "settlementRail": "SBI / ESAS" } }, "united-arab-emirates": { "technologies": [ "UAE banking on-ramp" ], "technologyProperties": { "onRampType": "UAEFTS bank transfer", "onRampRegion": "United Arab Emirates", "settlementRail": "UAEFTS / IPP" } }, "singapore": { "technologies": [ "Singapore FAST on-ramp" ], "technologyProperties": { "onRampType": "FAST bank transfer", "onRampRegion": "Singapore", "settlementRail": "FAST / MEPS+" } }, "other": { "technologies": [ "Regional fiat on-ramp" ], "technologyProperties": { "onRampType": "Local rail bank transfer", "onRampRegion": "Region-specific", "settlementRail": "Local payment network" } } }, "showIf": { "questionId": "corridor-count", "minValue": "4-5" }, "prefillFrom": null, "briefSection": "Payment rail requirements", "text": "Fourth transfer origination country (if applicable)", "ngoText": "Fourth transfer origination country (if applicable)" }, { "id": "origination-country-5", "type": "select", "options": [ { "label": "United States", "value": "united-states" }, { "label": "United Kingdom", "value": "united-kingdom" }, { "label": "Germany", "value": "germany" }, { "label": "Netherlands", "value": "netherlands" }, { "label": "Switzerland", "value": "switzerland" }, { "label": "Belgium", "value": "belgium" }, { "label": "France", "value": "france" }, { "label": "Sweden", "value": "sweden" }, { "label": "Norway", "value": "norway" }, { "label": "Denmark", "value": "denmark" }, { "label": "Canada", "value": "canada" }, { "label": "Australia", "value": "australia" }, { "label": "Japan", "value": "japan" }, { "label": "Ireland", "value": "ireland" }, { "label": "Italy", "value": "italy" }, { "label": "Spain", "value": "spain" }, { "label": "Austria", "value": "austria" }, { "label": "Finland", "value": "finland" }, { "label": "Luxembourg", "value": "luxembourg" }, { "label": "South Korea", "value": "south-korea" }, { "label": "New Zealand", "value": "new-zealand" }, { "label": "United Arab Emirates", "value": "united-arab-emirates" }, { "label": "Singapore", "value": "singapore" }, { "label": "Other", "value": "other" } ], "propertyMapping": { "united-states": { "technologies": [ "ACH/wire fiat on-ramp" ], "technologyProperties": { "onRampType": "ACH/Fedwire bank transfer", "onRampRegion": "United States", "settlementRail": "ACH / Fedwire" } }, "united-kingdom": { "technologies": [ "UK Faster Payments on-ramp" ], "technologyProperties": { "onRampType": "Faster Payments bank transfer", "onRampRegion": "United Kingdom", "settlementRail": "FPS / BACS" } }, "germany": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "netherlands": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "switzerland": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SIC/SEPA bank transfer", "onRampRegion": "Switzerland/EU", "settlementRail": "SIC / SEPA Credit Transfer" } }, "belgium": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "france": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "sweden": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "norway": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA-adjacent bank transfer", "onRampRegion": "EEA", "settlementRail": "SEPA Credit Transfer" } }, "denmark": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "canada": { "technologies": [ "Canadian EFT on-ramp" ], "technologyProperties": { "onRampType": "Interac/EFT bank transfer", "onRampRegion": "Canada", "settlementRail": "Interac / EFT" } }, "australia": { "technologies": [ "Australian NPP on-ramp" ], "technologyProperties": { "onRampType": "NPP bank transfer", "onRampRegion": "Australia", "settlementRail": "NPP / BECS" } }, "japan": { "technologies": [ "Japanese Zengin on-ramp" ], "technologyProperties": { "onRampType": "Zengin bank transfer", "onRampRegion": "Japan", "settlementRail": "Zengin System" } }, "ireland": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "italy": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "spain": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "austria": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "finland": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "luxembourg": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "south-korea": { "technologies": [ "Korean banking on-ramp" ], "technologyProperties": { "onRampType": "KFTC bank transfer", "onRampRegion": "South Korea", "settlementRail": "KFTC / BOK-Wire" } }, "new-zealand": { "technologies": [ "NZ banking on-ramp" ], "technologyProperties": { "onRampType": "SBI bank transfer", "onRampRegion": "New Zealand", "settlementRail": "SBI / ESAS" } }, "united-arab-emirates": { "technologies": [ "UAE banking on-ramp" ], "technologyProperties": { "onRampType": "UAEFTS bank transfer", "onRampRegion": "United Arab Emirates", "settlementRail": "UAEFTS / IPP" } }, "singapore": { "technologies": [ "Singapore FAST on-ramp" ], "technologyProperties": { "onRampType": "FAST bank transfer", "onRampRegion": "Singapore", "settlementRail": "FAST / MEPS+" } }, "other": { "technologies": [ "Regional fiat on-ramp" ], "technologyProperties": { "onRampType": "Local rail bank transfer", "onRampRegion": "Region-specific", "settlementRail": "Local payment network" } } }, "showIf": { "questionId": "corridor-count", "minValue": "4-5" }, "prefillFrom": null, "briefSection": "Payment rail requirements", "text": "Fifth transfer origination country (if applicable)", "ngoText": "Fifth transfer origination country (if applicable)" }, { "id": "funding-method", "type": "select", "options": [ { "label": "Bank transfer from organisation account", "value": "bank-transfer" }, { "label": "Card payment from organisation", "value": "card-payment" }, { "label": "Direct stablecoin funding (organisation already holds stablecoins)", "value": "direct-stablecoin" }, { "label": "Mixed: bank transfer for most, card for urgent payments", "value": "mixed-methods" } ], "propertyMapping": { "bank-transfer": { "technologies": [ "Bank-integrated fiat on-ramp" ], "technologyProperties": { "fundingSource": "Organisation bank account", "onRampSpeed": "1-2 business days (SEPA/ACH) or same-day (Faster Payments/wire)", "kybRequired": "Yes \u2014 organisation KYB verification" } }, "card-payment": { "technologies": [ "Card payment on-ramp" ], "technologyProperties": { "fundingSource": "Organisation payment card", "onRampSpeed": "Near-instant", "kybRequired": "Yes \u2014 card verification and organisation KYB" } }, "direct-stablecoin": { "technologies": [ "Direct stablecoin treasury funding" ], "technologyProperties": { "fundingSource": "Existing stablecoin holdings", "onRampSpeed": "Immediate (no fiat conversion needed)", "kybRequired": "Wallet verification only" } }, "mixed-methods": { "technologies": [ "Multi-method fiat on-ramp", "Card payment on-ramp" ], "technologyProperties": { "fundingSource": "Bank transfer (primary) + card (urgent)", "onRampSpeed": "Varies by method", "kybRequired": "Yes \u2014 full organisation KYB" } } }, "prefillFrom": null, "briefSection": "Payment rail requirements", "text": "How does your organisation currently fund international transfers or payments?", "ngoText": "How does your organisation currently fund international transfers or payments?" }, { "id": "stablecoin-approach", "type": "select", "options": [ { "label": "A regulated digital dollar", "value": "usd-pegged" }, { "label": "EUR-pegged stablecoin", "value": "eur-pegged" }, { "label": "Multiple stablecoins depending on corridor", "value": "multi-stablecoin" }, { "label": "Not sure, need guidance on stablecoin selection", "value": "guidance-needed" } ], "propertyMapping": { "usd-pegged": { "technologies": [ "USD-pegged stablecoin rail", "Stablecoin settlement layer" ], "technologyProperties": { "stablecoinType": "A regulated digital dollar", "fxConversion": "At on-ramp and off-ramp points" } }, "eur-pegged": { "technologies": [ "EUR-pegged stablecoin rail", "Stablecoin settlement layer" ], "technologyProperties": { "stablecoinType": "EUR-pegged", "fxConversion": "At on-ramp and off-ramp points" } }, "multi-stablecoin": { "technologies": [ "Multi-stablecoin settlement layer", "Automated FX conversion" ], "technologyProperties": { "stablecoinType": "Multiple denominations", "fxConversion": "Digital or at off-ramp" } }, "guidance-needed": { "technologies": [ "Stablecoin settlement layer" ], "technologyProperties": { "stablecoinType": "To be determined during solution design", "fxConversion": "To be determined" } } }, "prefillFrom": null, "briefSection": "Stablecoin and FX", "text": "What stablecoin approach is preferred for this solution?", "ngoText": "What stablecoin approach is preferred for this solution?" }, { "id": "grant-duration", "type": "select", "options": [ { "label": "1-2 years", "value": "short" }, { "label": "2-3 years", "value": "medium" }, { "label": "3-5 years", "value": "long" }, { "label": "Over 5 years", "value": "very-long" } ], "propertyMapping": { "short": { "technologies": [ "Smart contract milestone automation" ], "technologyProperties": { "contractDuration": "1-2 year lifecycle", "upgradeability": "Fixed contract acceptable" } }, "medium": { "technologies": [ "Smart contract milestone automation" ], "technologyProperties": { "contractDuration": "2-3 year lifecycle", "upgradeability": "Minor parameter updates needed" } }, "long": { "technologies": [ "Upgradeable smart contract", "Governance module" ], "technologyProperties": { "contractDuration": "3-5 year lifecycle", "upgradeability": "Must support amendment without redeployment" } }, "very-long": { "technologies": [ "Upgradeable smart contract framework", "Long-term governance module" ], "technologyProperties": { "contractDuration": "5+ year lifecycle", "upgradeability": "Full upgrade capability essential" } } }, "prefillFrom": null, "briefSection": "Payment logic", "text": "What is the typical grant duration for milestone-based disbursements?", "ngoText": "What is the typical grant duration for milestone-based disbursements?" }, { "id": "milestone-types", "type": "multiselect", "options": [ { "label": "Output milestones (deliverables, reports)", "value": "output" }, { "label": "Outcome milestones (impact metrics)", "value": "outcome" }, { "label": "Time-based milestones (quarterly/annual)", "value": "time-based" }, { "label": "Expenditure milestones (% of previous tranche spent)", "value": "expenditure" }, { "label": "Compliance milestones (audit completed, report submitted)", "value": "compliance" } ], "propertyMapping": { "output": { "technologies": [ "Deliverable verification workflow", "Document hash anchoring" ], "technologyProperties": { "milestoneVerification": "Deliverable submission + review", "evidenceType": "Document hash + approval signature" } }, "outcome": { "technologies": [ "Impact data oracle", "KPI tracking module" ], "technologyProperties": { "milestoneVerification": "Outcome measurement verification", "evidenceType": "Impact data from M&E system" } }, "time-based": { "technologies": [ "Automated time trigger" ], "technologyProperties": { "milestoneVerification": "Calendar-based automatic", "evidenceType": "Block timestamp" } }, "expenditure": { "technologies": [ "Expenditure monitoring module", "Automated spend tracking" ], "technologyProperties": { "milestoneVerification": "Spend rate threshold check", "evidenceType": "Ledger data \u2014 automated" } }, "compliance": { "technologies": [ "Compliance verification workflow" ], "technologyProperties": { "milestoneVerification": "Compliance document submission", "evidenceType": "Audit report hash + sign-off" } } }, "prefillFrom": null, "briefSection": "Payment logic", "text": "What types of milestones trigger disbursements?", "ngoText": "What types of milestones trigger disbursements?" }, { "id": "amendment-frequency", "type": "select", "options": [ { "label": "Rarely, terms are fixed", "value": "rarely" }, { "label": "Occasionally, annual reviews may adjust", "value": "occasionally" }, { "label": "Frequently, milestones evolve with context", "value": "frequently" } ], "propertyMapping": { "rarely": { "technologies": [ "Fixed smart contract" ], "technologyProperties": { "amendability": "Not required", "governanceModel": "Set-and-forget" } }, "occasionally": { "technologies": [ "Parameterised smart contract" ], "technologyProperties": { "amendability": "Parameter updates via multi-sig", "governanceModel": "Annual review cycle" } }, "frequently": { "technologies": [ "Upgradeable smart contract", "Amendment governance module" ], "technologyProperties": { "amendability": "Full amendment capability", "governanceModel": "Continuous governance with audit trail" } } }, "prefillFrom": null, "briefSection": "Governance and controls", "text": "How often do grant terms or milestones get amended during the grant period?", "ngoText": "How often do grant terms or milestones get amended during the grant period?", "hidden": true }, { "id": "sq-UC-A-015-001", "type": "single-select", "options": [ { "value": "self-reported", "label": "Self-reported by recipient" }, { "value": "third-party-verified", "label": "Third-party verified" }, { "value": "community-attestation", "label": "Community attestation" }, { "value": "sensor-data", "label": "Sensor or IoT data" }, { "value": "multi-party-sign-off", "label": "Multi-party sign-off" } ], "propertyMapping": { "self-reported": { "technologies": [ "attestation-system", "simple-verification" ], "technologyProperties": {} }, "third-party-verified": { "technologies": [ "verification-workflow", "auditor-integration" ], "technologyProperties": {} }, "community-attestation": { "technologies": [ "community-voting", "collective-verification" ], "technologyProperties": {} }, "sensor-data": { "technologies": [ "iot-integration", "automated-verification" ], "technologyProperties": {} }, "multi-party-sign-off": { "technologies": [ "multi-sig", "approval-workflow" ], "technologyProperties": {} } }, "briefSection": "requirements", "text": "What evidence and verification process do you currently use before triggering milestone disbursements?", "ngoText": "What evidence and verification process do you currently use before triggering milestone disbursements?" }, { "id": "offramp-delivery", "type": "select", "options": [ { "label": "Mobile money", "value": "mobile-money" }, { "label": "Bank transfer to beneficiary/recipient account", "value": "bank-transfer" }, { "label": "Cash via agent network", "value": "agent-cash" }, { "label": "Mixed: depends on recipient location and access", "value": "mixed" } ], "propertyMapping": { "mobile-money": { "technologies": [ "Mobile money off-ramp integration", "MNO API gateway" ], "technologyProperties": { "lastMileChannel": "MNO API integration", "cashOutMethod": "Mobile money wallet top-up" } }, "bank-transfer": { "technologies": [ "Bank-integrated off-ramp", "Local bank API integration" ], "technologyProperties": { "lastMileChannel": "Bank transfer", "cashOutMethod": "Direct bank deposit" } }, "agent-cash": { "technologies": [ "Agent network off-ramp", "Agent cash-out network" ], "technologyProperties": { "lastMileChannel": "Agent network", "cashOutMethod": "Cash via registered agent" } }, "mixed": { "technologies": [ "Multi-channel off-ramp gateway", "Mobile money off-ramp integration", "Agent cash-out network" ], "technologyProperties": { "lastMileChannel": "Mobile money + agent + bank", "cashOutMethod": "Recipient choice" } } }, "prefillFrom": null, "briefSection": "Last-mile delivery", "text": "How will recipients receive funds at the last mile?", "ngoText": "How will recipients receive funds at the last mile?" } ], "complexityFactors": { "relationships": 3, "operationalChange": 3, "dataCompliance": 2 }, "suggestedCriteria": [ { "id": "SC-MILESTONE-DEF", "name": "Milestone Definition & Verification", "description": "The provider can handle complex grant milestones that span years. Multi-year grants have milestones tied to outcomes (beneficiary targets), financial thresholds (burn rates), and compliance events (audits).", "weight": 0.3, "ratingGuide": { "5": "Multi-year milestone planning. Outcome, financial, and compliance milestone types. Multiple verification methods (self-report, third-party, data-driven). Milestone dependency chains.", "4": "Good milestone management across years. Multiple milestone types. Basic verification options.", "3": "Milestone tracking with date and outcome targets. Single verification method per milestone.", "2": "Simple date-based milestones. Manual verification. No outcome-based triggers.", "1": "No milestone management. Manual tracking in spreadsheets." } }, { "id": "SC-CONDITIONAL-RELEASE", "name": "Conditional Fund Release Logic", "description": "Disbursements can be automatically triggered or held based on milestone completion. Grant funds should flow when conditions are met and pause when they're not, without manual intervention.", "weight": 0.25, "ratingGuide": { "5": "Automatic disbursement on milestone verification. Conditional hold with clear reasons. Partial release for partially met milestones. Override with documented approval.", "4": "Automatic triggers. Good hold/release logic. Partial releases supported.", "3": "Semi-automatic: system recommends release, human confirms. Basic hold logic.", "2": "Manual release decisions. Milestone status tracked but not linked to disbursement.", "1": "No link between milestones and disbursement. All releases manual." } }, { "id": "SC-MULTI-YEAR-VIEW", "name": "Multi-Year Grant Lifecycle View", "description": "The provider can show the full grant lifecycle from Year 1 through completion. Programme managers need to see where they are in a 3-5 year grant: past performance, current status, and future milestones.", "weight": 0.2, "ratingGuide": { "5": "Visual timeline of entire grant. Past milestone status. Current period detail. Future milestones with projected dates. Budget burn rate projections to end of grant.", "4": "Good lifecycle view. Timeline with milestones. Current and future visibility. Budget tracking.", "3": "Current period detail with past history. Future milestones listed. Basic projections.", "2": "Current period focus. Limited historical view. No future projections.", "1": "Single-period view. No multi-year lifecycle visibility." } }, { "id": "SC-DONOR-VISIBILITY", "name": "Donor Portal / Visibility", "description": "Donors can track milestone progress and fund utilisation directly. Giving donors self-service access to progress data reduces reporting burden and builds trust.", "weight": 0.15, "ratingGuide": { "5": "Donor portal with real-time milestone status, fund utilisation, and outcome metrics. Configurable access levels. Automatic progress summaries.", "4": "Good donor portal. Milestone and budget visibility. Periodic auto-generated summaries.", "3": "Basic donor access to milestone status. Manual report sharing. Limited self-service.", "2": "Reports shared via email. No self-service donor access.", "1": "No donor visibility. All information communicated manually." } }, { "id": "SC-AMENDMENT-MGMT", "name": "Grant Amendment & Budget Revision Handling", "description": "The provider can handle grant amendments (budget reallocations, timeline extensions, milestone changes). Multi-year grants almost always require amendments. The system must track original and amended terms.", "weight": 0.1, "ratingGuide": { "5": "Formal amendment workflow. Version tracking of original and amended terms. Budget reallocation with donor approval trail. Timeline extension management.", "4": "Good amendment tracking. Version history. Budget reallocation supported.", "3": "Amendment recording. Manual version comparison. Basic reallocation.", "2": "Amendments noted but original terms overwritten. Limited history.", "1": "No amendment management. Changes made ad-hoc without tracking." } } ], "procurement": { "marketMaturity": "emerging", "primaryMode": "integrator-led", "alternativeModes": [ "rfq" ], "reasoning": "Milestone-based disbursement automation needs integration with donor and accounting systems.", "exampleProductCategories": [ "milestone-payment-automation", "grants-disbursement-platform" ], "partnerChannels": [], "lastReviewed": "2026-05-01" } }, { "id": "UC-A-016", "name": "Sub-grantee fund disbursement and tracking", "category": "A", "subcategory": "Cross-Border Payments and Transfers", "description": "See whether money passed to a partner reaches the sub-grantees and people it was meant for, and not only the first recipient.", "bCriteria": [ "B1", "B3", "B5" ], "requiredComponents": [ { "component": "payment-rails", "description": "Sub-grantee payment network" }, { "component": "stablecoin", "description": "Fund denomination" }, { "component": "accounting-integration", "description": "Fund tracking" }, { "component": "reporting-module", "description": "Sub-grantee reporting" }, { "component": "audit-mechanism", "description": "Fund deployment audit trail" } ], "conditionalComponents": [ { "component": "smart-contracts", "condition": "If disbursements are milestone-based" }, { "component": "identity-verification", "condition": "If sub-grantee KYC needed", "linksTo": "UC-B-032" } ], "crossCategoryDependencies": [ "UC-E-072 if dispute resolution with sub-grantees needed" ], "p2TriggerConditions": { "description": "Activated when P2 shows multiple sub-grantees + fund transparency needs + tracking burden", "rangeSignals": [ "subGrantees >= 3", "fundTransparency >= high", "reportingBurden >= high" ] }, "contextFieldsTemplate": [ { "field": "subGranteeCount", "source": "P0 partnerships", "description": "Number of sub-grantees" }, { "field": "totalSubGrantValue", "source": "P0 grants", "description": "Total sub-grant funding" }, { "field": "reportingFrequency", "source": "P0 grant agreements", "description": "Required reporting" }, { "field": "auditRequirements", "source": "P0 donor requirements", "description": "Audit standards" } ], "implementationComplexity": "medium", "examples": { "note": "NGO grant cascading models", "references": [ { "name": "Disberse", "url": "https://www.nesta.org.uk/feature/new-radicals-2018/disberse/", "solved": "Traced international aid fund transfers reducing intermediary costs" }, { "name": "Start Network", "url": "https://startnetwork.org/blockchain", "solved": "Accelerated emergency funding payouts with enhanced transparency" } ] }, "solutionQuestions": [ { "id": "corridor-count", "type": "select", "options": [ { "label": "Single country", "value": "single" }, { "label": "2\u20133 countries", "value": "2-3" }, { "label": "4\u20135 countries", "value": "4-5" }, { "label": "More than 5 countries", "value": "5-plus" } ], "propertyMapping": { "single": { "technologies": [ "Single-corridor fiat on-ramp" ], "technologyProperties": { "corridorComplexity": "Single origination country", "multiRailNeeded": "No" } }, "2-3": { "technologies": [ "Multi-corridor fiat on-ramp gateway" ], "technologyProperties": { "corridorComplexity": "2\u20133 origination countries", "multiRailNeeded": "Yes \u2014 2-3 payment rails" } }, "4-5": { "technologies": [ "Multi-corridor fiat on-ramp gateway" ], "technologyProperties": { "corridorComplexity": "4\u20135 origination countries", "multiRailNeeded": "Yes \u2014 4-5 payment rails" } }, "5-plus": { "technologies": [ "Enterprise multi-corridor on-ramp gateway" ], "technologyProperties": { "corridorComplexity": "5+ origination countries", "multiRailNeeded": "Yes \u2014 enterprise-grade multi-rail" } } }, "prefillFrom": null, "briefSection": "Payment rail requirements", "text": "How many countries does your organisation send transfer funds from?", "ngoText": "How many countries does your organisation send transfer funds from?" }, { "id": "origination-country-1", "type": "select", "options": [ { "label": "United States", "value": "united-states" }, { "label": "United Kingdom", "value": "united-kingdom" }, { "label": "Germany", "value": "germany" }, { "label": "Netherlands", "value": "netherlands" }, { "label": "Switzerland", "value": "switzerland" }, { "label": "Belgium", "value": "belgium" }, { "label": "France", "value": "france" }, { "label": "Sweden", "value": "sweden" }, { "label": "Norway", "value": "norway" }, { "label": "Denmark", "value": "denmark" }, { "label": "Canada", "value": "canada" }, { "label": "Australia", "value": "australia" }, { "label": "Japan", "value": "japan" }, { "label": "Ireland", "value": "ireland" }, { "label": "Italy", "value": "italy" }, { "label": "Spain", "value": "spain" }, { "label": "Austria", "value": "austria" }, { "label": "Finland", "value": "finland" }, { "label": "Luxembourg", "value": "luxembourg" }, { "label": "South Korea", "value": "south-korea" }, { "label": "New Zealand", "value": "new-zealand" }, { "label": "United Arab Emirates", "value": "united-arab-emirates" }, { "label": "Singapore", "value": "singapore" }, { "label": "Other", "value": "other" } ], "propertyMapping": { "united-states": { "technologies": [ "ACH/wire fiat on-ramp" ], "technologyProperties": { "onRampType": "ACH/Fedwire bank transfer", "onRampRegion": "United States", "settlementRail": "ACH / Fedwire" } }, "united-kingdom": { "technologies": [ "UK Faster Payments on-ramp" ], "technologyProperties": { "onRampType": "Faster Payments bank transfer", "onRampRegion": "United Kingdom", "settlementRail": "FPS / BACS" } }, "germany": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "netherlands": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "switzerland": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SIC/SEPA bank transfer", "onRampRegion": "Switzerland/EU", "settlementRail": "SIC / SEPA Credit Transfer" } }, "belgium": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "france": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "sweden": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "norway": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA-adjacent bank transfer", "onRampRegion": "EEA", "settlementRail": "SEPA Credit Transfer" } }, "denmark": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "canada": { "technologies": [ "Canadian EFT on-ramp" ], "technologyProperties": { "onRampType": "Interac/EFT bank transfer", "onRampRegion": "Canada", "settlementRail": "Interac / EFT" } }, "australia": { "technologies": [ "Australian NPP on-ramp" ], "technologyProperties": { "onRampType": "NPP bank transfer", "onRampRegion": "Australia", "settlementRail": "NPP / BECS" } }, "japan": { "technologies": [ "Japanese Zengin on-ramp" ], "technologyProperties": { "onRampType": "Zengin bank transfer", "onRampRegion": "Japan", "settlementRail": "Zengin System" } }, "ireland": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "italy": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "spain": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "austria": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "finland": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "luxembourg": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "south-korea": { "technologies": [ "Korean banking on-ramp" ], "technologyProperties": { "onRampType": "KFTC bank transfer", "onRampRegion": "South Korea", "settlementRail": "KFTC / BOK-Wire" } }, "new-zealand": { "technologies": [ "NZ banking on-ramp" ], "technologyProperties": { "onRampType": "SBI bank transfer", "onRampRegion": "New Zealand", "settlementRail": "SBI / ESAS" } }, "united-arab-emirates": { "technologies": [ "UAE banking on-ramp" ], "technologyProperties": { "onRampType": "UAEFTS bank transfer", "onRampRegion": "United Arab Emirates", "settlementRail": "UAEFTS / IPP" } }, "singapore": { "technologies": [ "Singapore FAST on-ramp" ], "technologyProperties": { "onRampType": "FAST bank transfer", "onRampRegion": "Singapore", "settlementRail": "FAST / MEPS+" } }, "other": { "technologies": [ "Regional fiat on-ramp" ], "technologyProperties": { "onRampType": "Local rail bank transfer", "onRampRegion": "Region-specific", "settlementRail": "Local payment network" } } }, "showIf": { "questionId": "corridor-count", "minValue": "single" }, "prefillFrom": null, "briefSection": "Payment rail requirements", "text": "Which country do you most frequently initiate transfers from?", "ngoText": "Which country do you most frequently initiate transfers from?" }, { "id": "origination-country-2", "type": "select", "options": [ { "label": "United States", "value": "united-states" }, { "label": "United Kingdom", "value": "united-kingdom" }, { "label": "Germany", "value": "germany" }, { "label": "Netherlands", "value": "netherlands" }, { "label": "Switzerland", "value": "switzerland" }, { "label": "Belgium", "value": "belgium" }, { "label": "France", "value": "france" }, { "label": "Sweden", "value": "sweden" }, { "label": "Norway", "value": "norway" }, { "label": "Denmark", "value": "denmark" }, { "label": "Canada", "value": "canada" }, { "label": "Australia", "value": "australia" }, { "label": "Japan", "value": "japan" }, { "label": "Ireland", "value": "ireland" }, { "label": "Italy", "value": "italy" }, { "label": "Spain", "value": "spain" }, { "label": "Austria", "value": "austria" }, { "label": "Finland", "value": "finland" }, { "label": "Luxembourg", "value": "luxembourg" }, { "label": "South Korea", "value": "south-korea" }, { "label": "New Zealand", "value": "new-zealand" }, { "label": "United Arab Emirates", "value": "united-arab-emirates" }, { "label": "Singapore", "value": "singapore" }, { "label": "Other", "value": "other" } ], "propertyMapping": { "united-states": { "technologies": [ "ACH/wire fiat on-ramp" ], "technologyProperties": { "onRampType": "ACH/Fedwire bank transfer", "onRampRegion": "United States", "settlementRail": "ACH / Fedwire" } }, "united-kingdom": { "technologies": [ "UK Faster Payments on-ramp" ], "technologyProperties": { "onRampType": "Faster Payments bank transfer", "onRampRegion": "United Kingdom", "settlementRail": "FPS / BACS" } }, "germany": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "netherlands": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "switzerland": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SIC/SEPA bank transfer", "onRampRegion": "Switzerland/EU", "settlementRail": "SIC / SEPA Credit Transfer" } }, "belgium": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "france": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "sweden": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "norway": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA-adjacent bank transfer", "onRampRegion": "EEA", "settlementRail": "SEPA Credit Transfer" } }, "denmark": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "canada": { "technologies": [ "Canadian EFT on-ramp" ], "technologyProperties": { "onRampType": "Interac/EFT bank transfer", "onRampRegion": "Canada", "settlementRail": "Interac / EFT" } }, "australia": { "technologies": [ "Australian NPP on-ramp" ], "technologyProperties": { "onRampType": "NPP bank transfer", "onRampRegion": "Australia", "settlementRail": "NPP / BECS" } }, "japan": { "technologies": [ "Japanese Zengin on-ramp" ], "technologyProperties": { "onRampType": "Zengin bank transfer", "onRampRegion": "Japan", "settlementRail": "Zengin System" } }, "ireland": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "italy": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "spain": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "austria": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "finland": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "luxembourg": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "south-korea": { "technologies": [ "Korean banking on-ramp" ], "technologyProperties": { "onRampType": "KFTC bank transfer", "onRampRegion": "South Korea", "settlementRail": "KFTC / BOK-Wire" } }, "new-zealand": { "technologies": [ "NZ banking on-ramp" ], "technologyProperties": { "onRampType": "SBI bank transfer", "onRampRegion": "New Zealand", "settlementRail": "SBI / ESAS" } }, "united-arab-emirates": { "technologies": [ "UAE banking on-ramp" ], "technologyProperties": { "onRampType": "UAEFTS bank transfer", "onRampRegion": "United Arab Emirates", "settlementRail": "UAEFTS / IPP" } }, "singapore": { "technologies": [ "Singapore FAST on-ramp" ], "technologyProperties": { "onRampType": "FAST bank transfer", "onRampRegion": "Singapore", "settlementRail": "FAST / MEPS+" } }, "other": { "technologies": [ "Regional fiat on-ramp" ], "technologyProperties": { "onRampType": "Local rail bank transfer", "onRampRegion": "Region-specific", "settlementRail": "Local payment network" } } }, "showIf": { "questionId": "corridor-count", "minValue": "2-3" }, "prefillFrom": null, "briefSection": "Payment rail requirements", "text": "Second most common transfer origination country (if applicable)", "ngoText": "Second most common transfer origination country (if applicable)" }, { "id": "origination-country-3", "type": "select", "options": [ { "label": "United States", "value": "united-states" }, { "label": "United Kingdom", "value": "united-kingdom" }, { "label": "Germany", "value": "germany" }, { "label": "Netherlands", "value": "netherlands" }, { "label": "Switzerland", "value": "switzerland" }, { "label": "Belgium", "value": "belgium" }, { "label": "France", "value": "france" }, { "label": "Sweden", "value": "sweden" }, { "label": "Norway", "value": "norway" }, { "label": "Denmark", "value": "denmark" }, { "label": "Canada", "value": "canada" }, { "label": "Australia", "value": "australia" }, { "label": "Japan", "value": "japan" }, { "label": "Ireland", "value": "ireland" }, { "label": "Italy", "value": "italy" }, { "label": "Spain", "value": "spain" }, { "label": "Austria", "value": "austria" }, { "label": "Finland", "value": "finland" }, { "label": "Luxembourg", "value": "luxembourg" }, { "label": "South Korea", "value": "south-korea" }, { "label": "New Zealand", "value": "new-zealand" }, { "label": "United Arab Emirates", "value": "united-arab-emirates" }, { "label": "Singapore", "value": "singapore" }, { "label": "Other", "value": "other" } ], "propertyMapping": { "united-states": { "technologies": [ "ACH/wire fiat on-ramp" ], "technologyProperties": { "onRampType": "ACH/Fedwire bank transfer", "onRampRegion": "United States", "settlementRail": "ACH / Fedwire" } }, "united-kingdom": { "technologies": [ "UK Faster Payments on-ramp" ], "technologyProperties": { "onRampType": "Faster Payments bank transfer", "onRampRegion": "United Kingdom", "settlementRail": "FPS / BACS" } }, "germany": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "netherlands": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "switzerland": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SIC/SEPA bank transfer", "onRampRegion": "Switzerland/EU", "settlementRail": "SIC / SEPA Credit Transfer" } }, "belgium": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "france": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "sweden": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "norway": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA-adjacent bank transfer", "onRampRegion": "EEA", "settlementRail": "SEPA Credit Transfer" } }, "denmark": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "canada": { "technologies": [ "Canadian EFT on-ramp" ], "technologyProperties": { "onRampType": "Interac/EFT bank transfer", "onRampRegion": "Canada", "settlementRail": "Interac / EFT" } }, "australia": { "technologies": [ "Australian NPP on-ramp" ], "technologyProperties": { "onRampType": "NPP bank transfer", "onRampRegion": "Australia", "settlementRail": "NPP / BECS" } }, "japan": { "technologies": [ "Japanese Zengin on-ramp" ], "technologyProperties": { "onRampType": "Zengin bank transfer", "onRampRegion": "Japan", "settlementRail": "Zengin System" } }, "ireland": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "italy": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "spain": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "austria": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "finland": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "luxembourg": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "south-korea": { "technologies": [ "Korean banking on-ramp" ], "technologyProperties": { "onRampType": "KFTC bank transfer", "onRampRegion": "South Korea", "settlementRail": "KFTC / BOK-Wire" } }, "new-zealand": { "technologies": [ "NZ banking on-ramp" ], "technologyProperties": { "onRampType": "SBI bank transfer", "onRampRegion": "New Zealand", "settlementRail": "SBI / ESAS" } }, "united-arab-emirates": { "technologies": [ "UAE banking on-ramp" ], "technologyProperties": { "onRampType": "UAEFTS bank transfer", "onRampRegion": "United Arab Emirates", "settlementRail": "UAEFTS / IPP" } }, "singapore": { "technologies": [ "Singapore FAST on-ramp" ], "technologyProperties": { "onRampType": "FAST bank transfer", "onRampRegion": "Singapore", "settlementRail": "FAST / MEPS+" } }, "other": { "technologies": [ "Regional fiat on-ramp" ], "technologyProperties": { "onRampType": "Local rail bank transfer", "onRampRegion": "Region-specific", "settlementRail": "Local payment network" } } }, "showIf": { "questionId": "corridor-count", "minValue": "2-3" }, "prefillFrom": null, "briefSection": "Payment rail requirements", "text": "Third transfer origination country (if applicable)", "ngoText": "Third transfer origination country (if applicable)" }, { "id": "origination-country-4", "type": "select", "options": [ { "label": "United States", "value": "united-states" }, { "label": "United Kingdom", "value": "united-kingdom" }, { "label": "Germany", "value": "germany" }, { "label": "Netherlands", "value": "netherlands" }, { "label": "Switzerland", "value": "switzerland" }, { "label": "Belgium", "value": "belgium" }, { "label": "France", "value": "france" }, { "label": "Sweden", "value": "sweden" }, { "label": "Norway", "value": "norway" }, { "label": "Denmark", "value": "denmark" }, { "label": "Canada", "value": "canada" }, { "label": "Australia", "value": "australia" }, { "label": "Japan", "value": "japan" }, { "label": "Ireland", "value": "ireland" }, { "label": "Italy", "value": "italy" }, { "label": "Spain", "value": "spain" }, { "label": "Austria", "value": "austria" }, { "label": "Finland", "value": "finland" }, { "label": "Luxembourg", "value": "luxembourg" }, { "label": "South Korea", "value": "south-korea" }, { "label": "New Zealand", "value": "new-zealand" }, { "label": "United Arab Emirates", "value": "united-arab-emirates" }, { "label": "Singapore", "value": "singapore" }, { "label": "Other", "value": "other" } ], "propertyMapping": { "united-states": { "technologies": [ "ACH/wire fiat on-ramp" ], "technologyProperties": { "onRampType": "ACH/Fedwire bank transfer", "onRampRegion": "United States", "settlementRail": "ACH / Fedwire" } }, "united-kingdom": { "technologies": [ "UK Faster Payments on-ramp" ], "technologyProperties": { "onRampType": "Faster Payments bank transfer", "onRampRegion": "United Kingdom", "settlementRail": "FPS / BACS" } }, "germany": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "netherlands": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "switzerland": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SIC/SEPA bank transfer", "onRampRegion": "Switzerland/EU", "settlementRail": "SIC / SEPA Credit Transfer" } }, "belgium": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "france": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "sweden": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "norway": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA-adjacent bank transfer", "onRampRegion": "EEA", "settlementRail": "SEPA Credit Transfer" } }, "denmark": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "canada": { "technologies": [ "Canadian EFT on-ramp" ], "technologyProperties": { "onRampType": "Interac/EFT bank transfer", "onRampRegion": "Canada", "settlementRail": "Interac / EFT" } }, "australia": { "technologies": [ "Australian NPP on-ramp" ], "technologyProperties": { "onRampType": "NPP bank transfer", "onRampRegion": "Australia", "settlementRail": "NPP / BECS" } }, "japan": { "technologies": [ "Japanese Zengin on-ramp" ], "technologyProperties": { "onRampType": "Zengin bank transfer", "onRampRegion": "Japan", "settlementRail": "Zengin System" } }, "ireland": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "italy": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "spain": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "austria": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "finland": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "luxembourg": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "south-korea": { "technologies": [ "Korean banking on-ramp" ], "technologyProperties": { "onRampType": "KFTC bank transfer", "onRampRegion": "South Korea", "settlementRail": "KFTC / BOK-Wire" } }, "new-zealand": { "technologies": [ "NZ banking on-ramp" ], "technologyProperties": { "onRampType": "SBI bank transfer", "onRampRegion": "New Zealand", "settlementRail": "SBI / ESAS" } }, "united-arab-emirates": { "technologies": [ "UAE banking on-ramp" ], "technologyProperties": { "onRampType": "UAEFTS bank transfer", "onRampRegion": "United Arab Emirates", "settlementRail": "UAEFTS / IPP" } }, "singapore": { "technologies": [ "Singapore FAST on-ramp" ], "technologyProperties": { "onRampType": "FAST bank transfer", "onRampRegion": "Singapore", "settlementRail": "FAST / MEPS+" } }, "other": { "technologies": [ "Regional fiat on-ramp" ], "technologyProperties": { "onRampType": "Local rail bank transfer", "onRampRegion": "Region-specific", "settlementRail": "Local payment network" } } }, "showIf": { "questionId": "corridor-count", "minValue": "4-5" }, "prefillFrom": null, "briefSection": "Payment rail requirements", "text": "Fourth transfer origination country (if applicable)", "ngoText": "Fourth transfer origination country (if applicable)" }, { "id": "origination-country-5", "type": "select", "options": [ { "label": "United States", "value": "united-states" }, { "label": "United Kingdom", "value": "united-kingdom" }, { "label": "Germany", "value": "germany" }, { "label": "Netherlands", "value": "netherlands" }, { "label": "Switzerland", "value": "switzerland" }, { "label": "Belgium", "value": "belgium" }, { "label": "France", "value": "france" }, { "label": "Sweden", "value": "sweden" }, { "label": "Norway", "value": "norway" }, { "label": "Denmark", "value": "denmark" }, { "label": "Canada", "value": "canada" }, { "label": "Australia", "value": "australia" }, { "label": "Japan", "value": "japan" }, { "label": "Ireland", "value": "ireland" }, { "label": "Italy", "value": "italy" }, { "label": "Spain", "value": "spain" }, { "label": "Austria", "value": "austria" }, { "label": "Finland", "value": "finland" }, { "label": "Luxembourg", "value": "luxembourg" }, { "label": "South Korea", "value": "south-korea" }, { "label": "New Zealand", "value": "new-zealand" }, { "label": "United Arab Emirates", "value": "united-arab-emirates" }, { "label": "Singapore", "value": "singapore" }, { "label": "Other", "value": "other" } ], "propertyMapping": { "united-states": { "technologies": [ "ACH/wire fiat on-ramp" ], "technologyProperties": { "onRampType": "ACH/Fedwire bank transfer", "onRampRegion": "United States", "settlementRail": "ACH / Fedwire" } }, "united-kingdom": { "technologies": [ "UK Faster Payments on-ramp" ], "technologyProperties": { "onRampType": "Faster Payments bank transfer", "onRampRegion": "United Kingdom", "settlementRail": "FPS / BACS" } }, "germany": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "netherlands": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "switzerland": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SIC/SEPA bank transfer", "onRampRegion": "Switzerland/EU", "settlementRail": "SIC / SEPA Credit Transfer" } }, "belgium": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "france": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "sweden": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "norway": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA-adjacent bank transfer", "onRampRegion": "EEA", "settlementRail": "SEPA Credit Transfer" } }, "denmark": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "canada": { "technologies": [ "Canadian EFT on-ramp" ], "technologyProperties": { "onRampType": "Interac/EFT bank transfer", "onRampRegion": "Canada", "settlementRail": "Interac / EFT" } }, "australia": { "technologies": [ "Australian NPP on-ramp" ], "technologyProperties": { "onRampType": "NPP bank transfer", "onRampRegion": "Australia", "settlementRail": "NPP / BECS" } }, "japan": { "technologies": [ "Japanese Zengin on-ramp" ], "technologyProperties": { "onRampType": "Zengin bank transfer", "onRampRegion": "Japan", "settlementRail": "Zengin System" } }, "ireland": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "italy": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "spain": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "austria": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "finland": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "luxembourg": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "south-korea": { "technologies": [ "Korean banking on-ramp" ], "technologyProperties": { "onRampType": "KFTC bank transfer", "onRampRegion": "South Korea", "settlementRail": "KFTC / BOK-Wire" } }, "new-zealand": { "technologies": [ "NZ banking on-ramp" ], "technologyProperties": { "onRampType": "SBI bank transfer", "onRampRegion": "New Zealand", "settlementRail": "SBI / ESAS" } }, "united-arab-emirates": { "technologies": [ "UAE banking on-ramp" ], "technologyProperties": { "onRampType": "UAEFTS bank transfer", "onRampRegion": "United Arab Emirates", "settlementRail": "UAEFTS / IPP" } }, "singapore": { "technologies": [ "Singapore FAST on-ramp" ], "technologyProperties": { "onRampType": "FAST bank transfer", "onRampRegion": "Singapore", "settlementRail": "FAST / MEPS+" } }, "other": { "technologies": [ "Regional fiat on-ramp" ], "technologyProperties": { "onRampType": "Local rail bank transfer", "onRampRegion": "Region-specific", "settlementRail": "Local payment network" } } }, "showIf": { "questionId": "corridor-count", "minValue": "4-5" }, "prefillFrom": null, "briefSection": "Payment rail requirements", "text": "Fifth transfer origination country (if applicable)", "ngoText": "Fifth transfer origination country (if applicable)" }, { "id": "funding-method", "type": "select", "options": [ { "label": "Bank transfer from organisation account", "value": "bank-transfer" }, { "label": "Card payment from organisation", "value": "card-payment" }, { "label": "Direct stablecoin funding (organisation already holds stablecoins)", "value": "direct-stablecoin" }, { "label": "Mixed: bank transfer for most, card for urgent payments", "value": "mixed-methods" } ], "propertyMapping": { "bank-transfer": { "technologies": [ "Bank-integrated fiat on-ramp" ], "technologyProperties": { "fundingSource": "Organisation bank account", "onRampSpeed": "1-2 business days (SEPA/ACH) or same-day (Faster Payments/wire)", "kybRequired": "Yes \u2014 organisation KYB verification" } }, "card-payment": { "technologies": [ "Card payment on-ramp" ], "technologyProperties": { "fundingSource": "Organisation payment card", "onRampSpeed": "Near-instant", "kybRequired": "Yes \u2014 card verification and organisation KYB" } }, "direct-stablecoin": { "technologies": [ "Direct stablecoin treasury funding" ], "technologyProperties": { "fundingSource": "Existing stablecoin holdings", "onRampSpeed": "Immediate (no fiat conversion needed)", "kybRequired": "Wallet verification only" } }, "mixed-methods": { "technologies": [ "Multi-method fiat on-ramp", "Card payment on-ramp" ], "technologyProperties": { "fundingSource": "Bank transfer (primary) + card (urgent)", "onRampSpeed": "Varies by method", "kybRequired": "Yes \u2014 full organisation KYB" } } }, "prefillFrom": null, "briefSection": "Payment rail requirements", "text": "How does your organisation currently fund international transfers or payments?", "ngoText": "How does your organisation currently fund international transfers or payments?" }, { "id": "stablecoin-approach", "type": "select", "options": [ { "label": "A regulated digital dollar", "value": "usd-pegged" }, { "label": "EUR-pegged stablecoin", "value": "eur-pegged" }, { "label": "Multiple stablecoins depending on corridor", "value": "multi-stablecoin" }, { "label": "Not sure, need guidance on stablecoin selection", "value": "guidance-needed" } ], "propertyMapping": { "usd-pegged": { "technologies": [ "USD-pegged stablecoin rail", "Stablecoin settlement layer" ], "technologyProperties": { "stablecoinType": "A regulated digital dollar", "fxConversion": "At on-ramp and off-ramp points" } }, "eur-pegged": { "technologies": [ "EUR-pegged stablecoin rail", "Stablecoin settlement layer" ], "technologyProperties": { "stablecoinType": "EUR-pegged", "fxConversion": "At on-ramp and off-ramp points" } }, "multi-stablecoin": { "technologies": [ "Multi-stablecoin settlement layer", "Automated FX conversion" ], "technologyProperties": { "stablecoinType": "Multiple denominations", "fxConversion": "Digital or at off-ramp" } }, "guidance-needed": { "technologies": [ "Stablecoin settlement layer" ], "technologyProperties": { "stablecoinType": "To be determined during solution design", "fxConversion": "To be determined" } } }, "prefillFrom": null, "briefSection": "Stablecoin and FX", "text": "What stablecoin approach is preferred for this solution?", "ngoText": "What stablecoin approach is preferred for this solution?" }, { "id": "subgrantee-capacity", "type": "select", "options": [ { "label": "Strong: formal accounting systems and qualified staff", "value": "strong" }, { "label": "Moderate: basic systems, some capacity gaps", "value": "moderate" }, { "label": "Weak: limited systems, often community-based organisations", "value": "weak" }, { "label": "Varies widely across sub-grantee portfolio", "value": "varies" } ], "propertyMapping": { "strong": { "technologies": [ "API-based reporting integration" ], "technologyProperties": { "subgranteeInterface": "API/system integration", "supportLevel": "Self-service with monitoring" } }, "moderate": { "technologies": [ "Simplified reporting portal", "Guided data entry" ], "technologyProperties": { "subgranteeInterface": "Web portal with guided workflow", "supportLevel": "Periodic support and training" } }, "weak": { "technologies": [ "Mobile-first simple reporting", "Agent-assisted data capture" ], "technologyProperties": { "subgranteeInterface": "Mobile app or USSD \u2014 ultra-simplified", "supportLevel": "Hands-on support and capacity building" } }, "varies": { "technologies": [ "Multi-tier sub-grantee platform" ], "technologyProperties": { "subgranteeInterface": "Tiered interface (API/web/mobile)", "supportLevel": "Capacity-appropriate support tiers" } } }, "prefillFrom": null, "briefSection": "End-user interface", "text": "What is the typical financial management capacity of your sub-grantees?", "ngoText": "What is the typical financial management capacity of your sub-grantees?" }, { "id": "subgrantee-reporting", "type": "multiselect", "options": [ { "label": "Financial reports (expenditure vs budget)", "value": "financial" }, { "label": "Activity/output reports", "value": "activity" }, { "label": "Supporting documents (receipts, invoices)", "value": "supporting-docs" }, { "label": "Beneficiary data", "value": "beneficiary-data" }, { "label": "Real-time spend visibility", "value": "realtime-spend" } ], "propertyMapping": { "financial": { "technologies": [ "Sub-grantee financial reporting module" ], "technologyProperties": { "reportingRequirement": "Budget vs actual", "dataCapture": "Expense categorisation" } }, "activity": { "technologies": [ "Activity reporting module" ], "technologyProperties": { "reportingRequirement": "Activity-linked expenditure", "dataCapture": "Output/activity tracking" } }, "supporting-docs": { "technologies": [ "Document upload and verification", "Receipt scanning" ], "technologyProperties": { "reportingRequirement": "Evidence documentation", "dataCapture": "Photo/scan upload with hash anchoring" } }, "beneficiary-data": { "technologies": [ "Beneficiary data module" ], "technologyProperties": { "reportingRequirement": "Beneficiary reach data", "dataCapture": "Beneficiary count and demographics" } }, "realtime-spend": { "technologies": [ "Real-time sub-grantee ledger view" ], "technologyProperties": { "reportingRequirement": "Live expenditure visibility", "dataCapture": "Per-transaction real-time feed" } } }, "prefillFrom": null, "briefSection": "Reporting and audit", "text": "What reporting do you need from sub-grantees?", "ngoText": "What reporting do you need from sub-grantees?" }, { "id": "subgrantee-disbursement-model", "type": "select", "options": [ { "label": "Advance-based: advance then liquidate", "value": "advance" }, { "label": "Reimbursement-based: sub-grantee spends first", "value": "reimbursement" }, { "label": "Milestone-based: payment on verified deliverables", "value": "milestone" }, { "label": "Mix of the above", "value": "mixed" } ], "propertyMapping": { "advance": { "technologies": [ "Smart contract advance management", "Liquidation tracking" ], "technologyProperties": { "disbursementModel": "Advance with liquidation", "cashFlowImpact": "Sub-grantee receives funds upfront" } }, "reimbursement": { "technologies": [ "Expense verification workflow", "Rapid reimbursement engine" ], "technologyProperties": { "disbursementModel": "Reimbursement after verification", "cashFlowImpact": "Sub-grantee cash flow burden" } }, "milestone": { "technologies": [ "Smart contract milestone disbursement" ], "technologyProperties": { "disbursementModel": "Milestone-triggered release", "cashFlowImpact": "Balanced \u2014 predictable triggers" } }, "mixed": { "technologies": [ "Flexible disbursement engine" ], "technologyProperties": { "disbursementModel": "Multi-modal (advance + milestone + reimbursement)", "cashFlowImpact": "Configurable per sub-grantee" } } }, "prefillFrom": null, "briefSection": "Payment logic", "text": "How are sub-grantee disbursements currently structured?", "ngoText": "How are sub-grantee disbursements currently structured?" }, { "id": "sq-UC-A-016-001", "type": "single-select", "options": [ { "value": "full-autonomy", "label": "Full autonomy" }, { "value": "spending-limits", "label": "Spending limits and thresholds" }, { "value": "pre-approval-required", "label": "Pre-approval required" }, { "value": "co-signatory", "label": "Co-signatory control" }, { "value": "escrow-with-milestones", "label": "Escrow with milestone release" } ], "propertyMapping": { "full-autonomy": { "technologies": [ "unrestricted-access", "monitoring-only" ], "technologyProperties": {} }, "spending-limits": { "technologies": [ "limit-enforcement", "threshold-checking" ], "technologyProperties": {} }, "pre-approval-required": { "technologies": [ "approval-workflow", "gatekeeper-control" ], "technologyProperties": {} }, "co-signatory": { "technologies": [ "multi-sig", "co-approval" ], "technologyProperties": {} }, "escrow-with-milestones": { "technologies": [ "escrow-system", "milestone-release" ], "technologyProperties": {} } }, "briefSection": "requirements", "text": "What financial controls should be imposed on sub-grantees based on their capacity level?", "ngoText": "What financial controls should be imposed on sub-grantees based on their capacity level?" }, { "id": "sq-UC-A-016-003", "type": "single-select", "options": [ { "value": "self-certified", "label": "Self-certified" }, { "value": "spot-audit", "label": "Spot audit" }, { "value": "third-party-audit", "label": "Third-party audit" }, { "value": "real-time-monitoring", "label": "Real-time monitoring" }, { "value": "milestone-based-review", "label": "Milestone-based review" } ], "propertyMapping": { "self-certified": { "technologies": [ "attestation-system", "self-reporting" ], "technologyProperties": {} }, "spot-audit": { "technologies": [ "audit-sampling", "field-verification" ], "technologyProperties": {} }, "third-party-audit": { "technologies": [ "auditor-network", "external-verification" ], "technologyProperties": {} }, "real-time-monitoring": { "technologies": [ "monitoring-dashboard", "continuous-tracking" ], "technologyProperties": {} }, "milestone-based-review": { "technologies": [ "milestone-tracking", "review-workflow" ], "technologyProperties": {} } }, "briefSection": "compliance", "text": "How are sub-grantee financial reports currently verified?", "ngoText": "How are sub-grantee financial reports currently verified?" }, { "id": "offramp-delivery", "type": "select", "options": [ { "label": "Mobile money", "value": "mobile-money" }, { "label": "Bank transfer to beneficiary/recipient account", "value": "bank-transfer" }, { "label": "Cash via agent network", "value": "agent-cash" }, { "label": "Mixed: depends on recipient location and access", "value": "mixed" } ], "propertyMapping": { "mobile-money": { "technologies": [ "Mobile money off-ramp integration", "MNO API gateway" ], "technologyProperties": { "lastMileChannel": "MNO API integration", "cashOutMethod": "Mobile money wallet top-up" } }, "bank-transfer": { "technologies": [ "Bank-integrated off-ramp", "Local bank API integration" ], "technologyProperties": { "lastMileChannel": "Bank transfer", "cashOutMethod": "Direct bank deposit" } }, "agent-cash": { "technologies": [ "Agent network off-ramp", "Agent cash-out network" ], "technologyProperties": { "lastMileChannel": "Agent network", "cashOutMethod": "Cash via registered agent" } }, "mixed": { "technologies": [ "Multi-channel off-ramp gateway", "Mobile money off-ramp integration", "Agent cash-out network" ], "technologyProperties": { "lastMileChannel": "Mobile money + agent + bank", "cashOutMethod": "Recipient choice" } } }, "prefillFrom": null, "briefSection": "Last-mile delivery", "text": "How will recipients receive funds at the last mile?", "ngoText": "How will recipients receive funds at the last mile?" } ], "complexityFactors": { "relationships": 3, "operationalChange": 3, "dataCompliance": 2 }, "securityTier": "B", "suggestedCriteria": [ { "id": "SC-CASCADE-TRACK", "name": "Cascading Fund Flow Tracking", "description": "The provider can track funds as they flow from the primary grantee through to sub-grantees and their expenditure. Sub-granting creates 2-3 levels of fund flow that donors expect visibility into.", "weight": 0.3, "ratingGuide": { "5": "Multi-level fund tracking (donor \u2192 grantee \u2192 sub-grantee \u2192 expenditure). Each level visible with appropriate access controls. Consolidated reporting across all levels.", "4": "Good two-level tracking. Grantee and sub-grantee visibility. Consolidated views.", "3": "Track disbursement to sub-grantees and their aggregate reporting. Limited expenditure-level detail.", "2": "Disbursement recording to sub-grantees. Sub-grantee reporting separate/manual.", "1": "No cascading fund tracking. Sub-grantee management outside the system." } }, { "id": "SC-SUB-ONBOARD", "name": "Sub-Grantee Onboarding & Capacity", "description": "This measures how easily sub-grantees can be set up on the platform. Many sub-grantees are small local organisations with limited technical capacity. The system must be accessible to them.", "weight": 0.25, "ratingGuide": { "5": "Simple web/mobile onboarding. Training materials in local languages. Minimal technical requirements. Phone-based reporting option. Guided setup wizard.", "4": "Good onboarding process. Basic training materials. Web access sufficient. Guided setup.", "3": "Standard onboarding. English-only. Web access required. Some training needed.", "2": "Complex onboarding requiring significant training. Desktop access needed.", "1": "Technical setup requiring IT support. Impractical for small local organisations." } }, { "id": "SC-SUB-REPORT", "name": "Sub-Grantee Reporting & Verification", "description": "Can sub-grantees submit financial and narrative reports through the platform? And can the primary grantee verify and consolidate these for donor reporting?", "weight": 0.2, "ratingGuide": { "5": "Sub-grantee reporting templates. Document upload. Primary grantee review/approve workflow. Auto-consolidation for donor reports. Verification checklists.", "4": "Good sub-grantee reporting. Review workflow. Semi-automatic consolidation.", "3": "Sub-grantee report submission. Manual review. Manual consolidation.", "2": "Sub-grantee reporting outside platform. Manual data entry for consolidation.", "1": "No sub-grantee reporting capability. All managed via email and spreadsheets." } }, { "id": "SC-SUB-COMPLIANCE", "name": "Sub-Grantee Compliance Monitoring", "description": "The provider helps monitor sub-grantee compliance with grant terms. Primary grantees are responsible for sub-grantee oversight. The system should flag issues early.", "weight": 0.15, "ratingGuide": { "5": "Automated compliance checks (spending rates, category limits, deadline adherence). Risk scoring per sub-grantee. Audit scheduling. Exception alerts.", "4": "Good compliance monitoring. Spending alerts. Basic risk indicators.", "3": "Manual compliance review tools. Checklists. Basic alert for missed deadlines.", "2": "Compliance tracked outside system. Platform provides data for manual review.", "1": "No compliance monitoring features." } }, { "id": "SC-SUB-DISBURSEMENT", "name": "Disbursement Mechanism Flexibility", "description": "Funds can reach sub-grantees via different channels. Sub-grantees range from organisations with bank accounts to community groups using mobile money.", "weight": 0.1, "ratingGuide": { "5": "Bank transfer, mobile money, cheque, and digital wallet options. Sub-grantee chooses preferred method. Multi-currency. Batch disbursement.", "4": "Bank and mobile money. Multiple currencies. Good batch capability.", "3": "Bank transfer primary. Mobile money in some markets. Basic batch processing.", "2": "Bank transfer only. Single currency. Individual transfers.", "1": "Single payment method. No flexibility for sub-grantee circumstances." } } ], "procurement": { "marketMaturity": "emerging", "primaryMode": "tender", "alternativeModes": [ "integrator-led" ], "reasoning": "Sub-grantee tracking products exist; integration with mainline grants management common.", "exampleProductCategories": [ "sub-grantee-tracking-platform", "grants-pass-through-saas" ], "partnerChannels": [], "lastReviewed": "2026-05-01" } }, { "id": "UC-A-017", "name": "Proof of funds deployment (donor accountability)", "category": "A", "subcategory": "Financial Reporting", "description": "Give donors evidence that funds were spent as stated, in a form they can check without relying only on your own reports.", "bCriteria": [ "B3", "B5" ], "requiredComponents": [ { "component": "payment-rails", "description": "Transparent transaction record" }, { "component": "audit-mechanism", "description": "Immutable deployment proof" }, { "component": "reporting-module", "description": "Deployment reporting" }, { "component": "data-layer", "description": "Deployment data records" } ], "conditionalComponents": [ { "component": "smart-contracts", "condition": "If automated proof generation" }, { "component": "identity-verification", "condition": "If beneficiary data in proof", "linksTo": "UC-B-024" } ], "crossCategoryDependencies": [ "UC-C-044 if beneficiary deduplication needed" ], "p2TriggerConditions": { "description": "Activated when P2 shows donor accountability focus + deployment tracking needs + reporting burden", "rangeSignals": [ "donorAccountability >= high", "deploymentTracking >= true", "reportingFrequency >= monthly" ] }, "contextFieldsTemplate": [ { "field": "deploymentMetrics", "source": "P2 donor requirements", "description": "Metrics to track" }, { "field": "beneficiaryLevel", "source": "P2 reporting granularity", "description": "Beneficiary identification" }, { "field": "reportingTimeline", "source": "P0 donor agreements", "description": "When proof is due" }, { "field": "dataIntegrity", "source": "P2 M&E practices", "description": "Current M&E system" } ], "implementationComplexity": "medium", "examples": { "note": "Donor transparency initiatives", "references": [ { "name": "Disberse", "url": "https://www.nesta.org.uk/feature/new-radicals-2018/disberse/", "solved": "Traced international aid fund transfers reducing intermediary costs" }, { "name": "WFP Building Blocks", "url": "https://www.wfp.org/building-blocks", "solved": "Transferred cash to refugee populations at scale, fast and at low cost" } ] }, "solutionQuestions": [ { "id": "corridor-count", "type": "select", "options": [ { "label": "Single country", "value": "single" }, { "label": "2\u20133 countries", "value": "2-3" }, { "label": "4\u20135 countries", "value": "4-5" }, { "label": "More than 5 countries", "value": "5-plus" } ], "propertyMapping": { "single": { "technologies": [ "Single-corridor fiat on-ramp" ], "technologyProperties": { "corridorComplexity": "Single origination country", "multiRailNeeded": "No" } }, "2-3": { "technologies": [ "Multi-corridor fiat on-ramp gateway" ], "technologyProperties": { "corridorComplexity": "2\u20133 origination countries", "multiRailNeeded": "Yes \u2014 2-3 payment rails" } }, "4-5": { "technologies": [ "Multi-corridor fiat on-ramp gateway" ], "technologyProperties": { "corridorComplexity": "4\u20135 origination countries", "multiRailNeeded": "Yes \u2014 4-5 payment rails" } }, "5-plus": { "technologies": [ "Enterprise multi-corridor on-ramp gateway" ], "technologyProperties": { "corridorComplexity": "5+ origination countries", "multiRailNeeded": "Yes \u2014 enterprise-grade multi-rail" } } }, "prefillFrom": null, "briefSection": "Payment rail requirements", "text": "How many countries does your organisation send transfer funds from?", "ngoText": "How many countries does your organisation send transfer funds from?" }, { "id": "origination-country-1", "type": "select", "options": [ { "label": "United States", "value": "united-states" }, { "label": "United Kingdom", "value": "united-kingdom" }, { "label": "Germany", "value": "germany" }, { "label": "Netherlands", "value": "netherlands" }, { "label": "Switzerland", "value": "switzerland" }, { "label": "Belgium", "value": "belgium" }, { "label": "France", "value": "france" }, { "label": "Sweden", "value": "sweden" }, { "label": "Norway", "value": "norway" }, { "label": "Denmark", "value": "denmark" }, { "label": "Canada", "value": "canada" }, { "label": "Australia", "value": "australia" }, { "label": "Japan", "value": "japan" }, { "label": "Ireland", "value": "ireland" }, { "label": "Italy", "value": "italy" }, { "label": "Spain", "value": "spain" }, { "label": "Austria", "value": "austria" }, { "label": "Finland", "value": "finland" }, { "label": "Luxembourg", "value": "luxembourg" }, { "label": "South Korea", "value": "south-korea" }, { "label": "New Zealand", "value": "new-zealand" }, { "label": "United Arab Emirates", "value": "united-arab-emirates" }, { "label": "Singapore", "value": "singapore" }, { "label": "Other", "value": "other" } ], "propertyMapping": { "united-states": { "technologies": [ "ACH/wire fiat on-ramp" ], "technologyProperties": { "onRampType": "ACH/Fedwire bank transfer", "onRampRegion": "United States", "settlementRail": "ACH / Fedwire" } }, "united-kingdom": { "technologies": [ "UK Faster Payments on-ramp" ], "technologyProperties": { "onRampType": "Faster Payments bank transfer", "onRampRegion": "United Kingdom", "settlementRail": "FPS / BACS" } }, "germany": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "netherlands": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "switzerland": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SIC/SEPA bank transfer", "onRampRegion": "Switzerland/EU", "settlementRail": "SIC / SEPA Credit Transfer" } }, "belgium": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "france": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "sweden": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "norway": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA-adjacent bank transfer", "onRampRegion": "EEA", "settlementRail": "SEPA Credit Transfer" } }, "denmark": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "canada": { "technologies": [ "Canadian EFT on-ramp" ], "technologyProperties": { "onRampType": "Interac/EFT bank transfer", "onRampRegion": "Canada", "settlementRail": "Interac / EFT" } }, "australia": { "technologies": [ "Australian NPP on-ramp" ], "technologyProperties": { "onRampType": "NPP bank transfer", "onRampRegion": "Australia", "settlementRail": "NPP / BECS" } }, "japan": { "technologies": [ "Japanese Zengin on-ramp" ], "technologyProperties": { "onRampType": "Zengin bank transfer", "onRampRegion": "Japan", "settlementRail": "Zengin System" } }, "ireland": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "italy": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "spain": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "austria": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "finland": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "luxembourg": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "south-korea": { "technologies": [ "Korean banking on-ramp" ], "technologyProperties": { "onRampType": "KFTC bank transfer", "onRampRegion": "South Korea", "settlementRail": "KFTC / BOK-Wire" } }, "new-zealand": { "technologies": [ "NZ banking on-ramp" ], "technologyProperties": { "onRampType": "SBI bank transfer", "onRampRegion": "New Zealand", "settlementRail": "SBI / ESAS" } }, "united-arab-emirates": { "technologies": [ "UAE banking on-ramp" ], "technologyProperties": { "onRampType": "UAEFTS bank transfer", "onRampRegion": "United Arab Emirates", "settlementRail": "UAEFTS / IPP" } }, "singapore": { "technologies": [ "Singapore FAST on-ramp" ], "technologyProperties": { "onRampType": "FAST bank transfer", "onRampRegion": "Singapore", "settlementRail": "FAST / MEPS+" } }, "other": { "technologies": [ "Regional fiat on-ramp" ], "technologyProperties": { "onRampType": "Local rail bank transfer", "onRampRegion": "Region-specific", "settlementRail": "Local payment network" } } }, "showIf": { "questionId": "corridor-count", "minValue": "single" }, "prefillFrom": null, "briefSection": "Payment rail requirements", "text": "Which country do you most frequently initiate transfers from?", "ngoText": "Which country do you most frequently initiate transfers from?" }, { "id": "origination-country-2", "type": "select", "options": [ { "label": "United States", "value": "united-states" }, { "label": "United Kingdom", "value": "united-kingdom" }, { "label": "Germany", "value": "germany" }, { "label": "Netherlands", "value": "netherlands" }, { "label": "Switzerland", "value": "switzerland" }, { "label": "Belgium", "value": "belgium" }, { "label": "France", "value": "france" }, { "label": "Sweden", "value": "sweden" }, { "label": "Norway", "value": "norway" }, { "label": "Denmark", "value": "denmark" }, { "label": "Canada", "value": "canada" }, { "label": "Australia", "value": "australia" }, { "label": "Japan", "value": "japan" }, { "label": "Ireland", "value": "ireland" }, { "label": "Italy", "value": "italy" }, { "label": "Spain", "value": "spain" }, { "label": "Austria", "value": "austria" }, { "label": "Finland", "value": "finland" }, { "label": "Luxembourg", "value": "luxembourg" }, { "label": "South Korea", "value": "south-korea" }, { "label": "New Zealand", "value": "new-zealand" }, { "label": "United Arab Emirates", "value": "united-arab-emirates" }, { "label": "Singapore", "value": "singapore" }, { "label": "Other", "value": "other" } ], "propertyMapping": { "united-states": { "technologies": [ "ACH/wire fiat on-ramp" ], "technologyProperties": { "onRampType": "ACH/Fedwire bank transfer", "onRampRegion": "United States", "settlementRail": "ACH / Fedwire" } }, "united-kingdom": { "technologies": [ "UK Faster Payments on-ramp" ], "technologyProperties": { "onRampType": "Faster Payments bank transfer", "onRampRegion": "United Kingdom", "settlementRail": "FPS / BACS" } }, "germany": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "netherlands": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "switzerland": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SIC/SEPA bank transfer", "onRampRegion": "Switzerland/EU", "settlementRail": "SIC / SEPA Credit Transfer" } }, "belgium": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "france": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "sweden": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "norway": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA-adjacent bank transfer", "onRampRegion": "EEA", "settlementRail": "SEPA Credit Transfer" } }, "denmark": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "canada": { "technologies": [ "Canadian EFT on-ramp" ], "technologyProperties": { "onRampType": "Interac/EFT bank transfer", "onRampRegion": "Canada", "settlementRail": "Interac / EFT" } }, "australia": { "technologies": [ "Australian NPP on-ramp" ], "technologyProperties": { "onRampType": "NPP bank transfer", "onRampRegion": "Australia", "settlementRail": "NPP / BECS" } }, "japan": { "technologies": [ "Japanese Zengin on-ramp" ], "technologyProperties": { "onRampType": "Zengin bank transfer", "onRampRegion": "Japan", "settlementRail": "Zengin System" } }, "ireland": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "italy": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "spain": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "austria": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "finland": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "luxembourg": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "south-korea": { "technologies": [ "Korean banking on-ramp" ], "technologyProperties": { "onRampType": "KFTC bank transfer", "onRampRegion": "South Korea", "settlementRail": "KFTC / BOK-Wire" } }, "new-zealand": { "technologies": [ "NZ banking on-ramp" ], "technologyProperties": { "onRampType": "SBI bank transfer", "onRampRegion": "New Zealand", "settlementRail": "SBI / ESAS" } }, "united-arab-emirates": { "technologies": [ "UAE banking on-ramp" ], "technologyProperties": { "onRampType": "UAEFTS bank transfer", "onRampRegion": "United Arab Emirates", "settlementRail": "UAEFTS / IPP" } }, "singapore": { "technologies": [ "Singapore FAST on-ramp" ], "technologyProperties": { "onRampType": "FAST bank transfer", "onRampRegion": "Singapore", "settlementRail": "FAST / MEPS+" } }, "other": { "technologies": [ "Regional fiat on-ramp" ], "technologyProperties": { "onRampType": "Local rail bank transfer", "onRampRegion": "Region-specific", "settlementRail": "Local payment network" } } }, "showIf": { "questionId": "corridor-count", "minValue": "2-3" }, "prefillFrom": null, "briefSection": "Payment rail requirements", "text": "Second most common transfer origination country (if applicable)", "ngoText": "Second most common transfer origination country (if applicable)" }, { "id": "origination-country-3", "type": "select", "options": [ { "label": "United States", "value": "united-states" }, { "label": "United Kingdom", "value": "united-kingdom" }, { "label": "Germany", "value": "germany" }, { "label": "Netherlands", "value": "netherlands" }, { "label": "Switzerland", "value": "switzerland" }, { "label": "Belgium", "value": "belgium" }, { "label": "France", "value": "france" }, { "label": "Sweden", "value": "sweden" }, { "label": "Norway", "value": "norway" }, { "label": "Denmark", "value": "denmark" }, { "label": "Canada", "value": "canada" }, { "label": "Australia", "value": "australia" }, { "label": "Japan", "value": "japan" }, { "label": "Ireland", "value": "ireland" }, { "label": "Italy", "value": "italy" }, { "label": "Spain", "value": "spain" }, { "label": "Austria", "value": "austria" }, { "label": "Finland", "value": "finland" }, { "label": "Luxembourg", "value": "luxembourg" }, { "label": "South Korea", "value": "south-korea" }, { "label": "New Zealand", "value": "new-zealand" }, { "label": "United Arab Emirates", "value": "united-arab-emirates" }, { "label": "Singapore", "value": "singapore" }, { "label": "Other", "value": "other" } ], "propertyMapping": { "united-states": { "technologies": [ "ACH/wire fiat on-ramp" ], "technologyProperties": { "onRampType": "ACH/Fedwire bank transfer", "onRampRegion": "United States", "settlementRail": "ACH / Fedwire" } }, "united-kingdom": { "technologies": [ "UK Faster Payments on-ramp" ], "technologyProperties": { "onRampType": "Faster Payments bank transfer", "onRampRegion": "United Kingdom", "settlementRail": "FPS / BACS" } }, "germany": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "netherlands": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "switzerland": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SIC/SEPA bank transfer", "onRampRegion": "Switzerland/EU", "settlementRail": "SIC / SEPA Credit Transfer" } }, "belgium": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "france": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "sweden": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "norway": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA-adjacent bank transfer", "onRampRegion": "EEA", "settlementRail": "SEPA Credit Transfer" } }, "denmark": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "canada": { "technologies": [ "Canadian EFT on-ramp" ], "technologyProperties": { "onRampType": "Interac/EFT bank transfer", "onRampRegion": "Canada", "settlementRail": "Interac / EFT" } }, "australia": { "technologies": [ "Australian NPP on-ramp" ], "technologyProperties": { "onRampType": "NPP bank transfer", "onRampRegion": "Australia", "settlementRail": "NPP / BECS" } }, "japan": { "technologies": [ "Japanese Zengin on-ramp" ], "technologyProperties": { "onRampType": "Zengin bank transfer", "onRampRegion": "Japan", "settlementRail": "Zengin System" } }, "ireland": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "italy": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "spain": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "austria": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "finland": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "luxembourg": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "south-korea": { "technologies": [ "Korean banking on-ramp" ], "technologyProperties": { "onRampType": "KFTC bank transfer", "onRampRegion": "South Korea", "settlementRail": "KFTC / BOK-Wire" } }, "new-zealand": { "technologies": [ "NZ banking on-ramp" ], "technologyProperties": { "onRampType": "SBI bank transfer", "onRampRegion": "New Zealand", "settlementRail": "SBI / ESAS" } }, "united-arab-emirates": { "technologies": [ "UAE banking on-ramp" ], "technologyProperties": { "onRampType": "UAEFTS bank transfer", "onRampRegion": "United Arab Emirates", "settlementRail": "UAEFTS / IPP" } }, "singapore": { "technologies": [ "Singapore FAST on-ramp" ], "technologyProperties": { "onRampType": "FAST bank transfer", "onRampRegion": "Singapore", "settlementRail": "FAST / MEPS+" } }, "other": { "technologies": [ "Regional fiat on-ramp" ], "technologyProperties": { "onRampType": "Local rail bank transfer", "onRampRegion": "Region-specific", "settlementRail": "Local payment network" } } }, "showIf": { "questionId": "corridor-count", "minValue": "2-3" }, "prefillFrom": null, "briefSection": "Payment rail requirements", "text": "Third transfer origination country (if applicable)", "ngoText": "Third transfer origination country (if applicable)" }, { "id": "origination-country-4", "type": "select", "options": [ { "label": "United States", "value": "united-states" }, { "label": "United Kingdom", "value": "united-kingdom" }, { "label": "Germany", "value": "germany" }, { "label": "Netherlands", "value": "netherlands" }, { "label": "Switzerland", "value": "switzerland" }, { "label": "Belgium", "value": "belgium" }, { "label": "France", "value": "france" }, { "label": "Sweden", "value": "sweden" }, { "label": "Norway", "value": "norway" }, { "label": "Denmark", "value": "denmark" }, { "label": "Canada", "value": "canada" }, { "label": "Australia", "value": "australia" }, { "label": "Japan", "value": "japan" }, { "label": "Ireland", "value": "ireland" }, { "label": "Italy", "value": "italy" }, { "label": "Spain", "value": "spain" }, { "label": "Austria", "value": "austria" }, { "label": "Finland", "value": "finland" }, { "label": "Luxembourg", "value": "luxembourg" }, { "label": "South Korea", "value": "south-korea" }, { "label": "New Zealand", "value": "new-zealand" }, { "label": "United Arab Emirates", "value": "united-arab-emirates" }, { "label": "Singapore", "value": "singapore" }, { "label": "Other", "value": "other" } ], "propertyMapping": { "united-states": { "technologies": [ "ACH/wire fiat on-ramp" ], "technologyProperties": { "onRampType": "ACH/Fedwire bank transfer", "onRampRegion": "United States", "settlementRail": "ACH / Fedwire" } }, "united-kingdom": { "technologies": [ "UK Faster Payments on-ramp" ], "technologyProperties": { "onRampType": "Faster Payments bank transfer", "onRampRegion": "United Kingdom", "settlementRail": "FPS / BACS" } }, "germany": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "netherlands": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "switzerland": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SIC/SEPA bank transfer", "onRampRegion": "Switzerland/EU", "settlementRail": "SIC / SEPA Credit Transfer" } }, "belgium": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "france": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "sweden": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "norway": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA-adjacent bank transfer", "onRampRegion": "EEA", "settlementRail": "SEPA Credit Transfer" } }, "denmark": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "canada": { "technologies": [ "Canadian EFT on-ramp" ], "technologyProperties": { "onRampType": "Interac/EFT bank transfer", "onRampRegion": "Canada", "settlementRail": "Interac / EFT" } }, "australia": { "technologies": [ "Australian NPP on-ramp" ], "technologyProperties": { "onRampType": "NPP bank transfer", "onRampRegion": "Australia", "settlementRail": "NPP / BECS" } }, "japan": { "technologies": [ "Japanese Zengin on-ramp" ], "technologyProperties": { "onRampType": "Zengin bank transfer", "onRampRegion": "Japan", "settlementRail": "Zengin System" } }, "ireland": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "italy": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "spain": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "austria": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "finland": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "luxembourg": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "south-korea": { "technologies": [ "Korean banking on-ramp" ], "technologyProperties": { "onRampType": "KFTC bank transfer", "onRampRegion": "South Korea", "settlementRail": "KFTC / BOK-Wire" } }, "new-zealand": { "technologies": [ "NZ banking on-ramp" ], "technologyProperties": { "onRampType": "SBI bank transfer", "onRampRegion": "New Zealand", "settlementRail": "SBI / ESAS" } }, "united-arab-emirates": { "technologies": [ "UAE banking on-ramp" ], "technologyProperties": { "onRampType": "UAEFTS bank transfer", "onRampRegion": "United Arab Emirates", "settlementRail": "UAEFTS / IPP" } }, "singapore": { "technologies": [ "Singapore FAST on-ramp" ], "technologyProperties": { "onRampType": "FAST bank transfer", "onRampRegion": "Singapore", "settlementRail": "FAST / MEPS+" } }, "other": { "technologies": [ "Regional fiat on-ramp" ], "technologyProperties": { "onRampType": "Local rail bank transfer", "onRampRegion": "Region-specific", "settlementRail": "Local payment network" } } }, "showIf": { "questionId": "corridor-count", "minValue": "4-5" }, "prefillFrom": null, "briefSection": "Payment rail requirements", "text": "Fourth transfer origination country (if applicable)", "ngoText": "Fourth transfer origination country (if applicable)" }, { "id": "origination-country-5", "type": "select", "options": [ { "label": "United States", "value": "united-states" }, { "label": "United Kingdom", "value": "united-kingdom" }, { "label": "Germany", "value": "germany" }, { "label": "Netherlands", "value": "netherlands" }, { "label": "Switzerland", "value": "switzerland" }, { "label": "Belgium", "value": "belgium" }, { "label": "France", "value": "france" }, { "label": "Sweden", "value": "sweden" }, { "label": "Norway", "value": "norway" }, { "label": "Denmark", "value": "denmark" }, { "label": "Canada", "value": "canada" }, { "label": "Australia", "value": "australia" }, { "label": "Japan", "value": "japan" }, { "label": "Ireland", "value": "ireland" }, { "label": "Italy", "value": "italy" }, { "label": "Spain", "value": "spain" }, { "label": "Austria", "value": "austria" }, { "label": "Finland", "value": "finland" }, { "label": "Luxembourg", "value": "luxembourg" }, { "label": "South Korea", "value": "south-korea" }, { "label": "New Zealand", "value": "new-zealand" }, { "label": "United Arab Emirates", "value": "united-arab-emirates" }, { "label": "Singapore", "value": "singapore" }, { "label": "Other", "value": "other" } ], "propertyMapping": { "united-states": { "technologies": [ "ACH/wire fiat on-ramp" ], "technologyProperties": { "onRampType": "ACH/Fedwire bank transfer", "onRampRegion": "United States", "settlementRail": "ACH / Fedwire" } }, "united-kingdom": { "technologies": [ "UK Faster Payments on-ramp" ], "technologyProperties": { "onRampType": "Faster Payments bank transfer", "onRampRegion": "United Kingdom", "settlementRail": "FPS / BACS" } }, "germany": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "netherlands": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "switzerland": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SIC/SEPA bank transfer", "onRampRegion": "Switzerland/EU", "settlementRail": "SIC / SEPA Credit Transfer" } }, "belgium": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "france": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "sweden": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "norway": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA-adjacent bank transfer", "onRampRegion": "EEA", "settlementRail": "SEPA Credit Transfer" } }, "denmark": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "canada": { "technologies": [ "Canadian EFT on-ramp" ], "technologyProperties": { "onRampType": "Interac/EFT bank transfer", "onRampRegion": "Canada", "settlementRail": "Interac / EFT" } }, "australia": { "technologies": [ "Australian NPP on-ramp" ], "technologyProperties": { "onRampType": "NPP bank transfer", "onRampRegion": "Australia", "settlementRail": "NPP / BECS" } }, "japan": { "technologies": [ "Japanese Zengin on-ramp" ], "technologyProperties": { "onRampType": "Zengin bank transfer", "onRampRegion": "Japan", "settlementRail": "Zengin System" } }, "ireland": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "italy": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "spain": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "austria": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "finland": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "luxembourg": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "south-korea": { "technologies": [ "Korean banking on-ramp" ], "technologyProperties": { "onRampType": "KFTC bank transfer", "onRampRegion": "South Korea", "settlementRail": "KFTC / BOK-Wire" } }, "new-zealand": { "technologies": [ "NZ banking on-ramp" ], "technologyProperties": { "onRampType": "SBI bank transfer", "onRampRegion": "New Zealand", "settlementRail": "SBI / ESAS" } }, "united-arab-emirates": { "technologies": [ "UAE banking on-ramp" ], "technologyProperties": { "onRampType": "UAEFTS bank transfer", "onRampRegion": "United Arab Emirates", "settlementRail": "UAEFTS / IPP" } }, "singapore": { "technologies": [ "Singapore FAST on-ramp" ], "technologyProperties": { "onRampType": "FAST bank transfer", "onRampRegion": "Singapore", "settlementRail": "FAST / MEPS+" } }, "other": { "technologies": [ "Regional fiat on-ramp" ], "technologyProperties": { "onRampType": "Local rail bank transfer", "onRampRegion": "Region-specific", "settlementRail": "Local payment network" } } }, "showIf": { "questionId": "corridor-count", "minValue": "4-5" }, "prefillFrom": null, "briefSection": "Payment rail requirements", "text": "Fifth transfer origination country (if applicable)", "ngoText": "Fifth transfer origination country (if applicable)" }, { "id": "funding-method", "type": "select", "options": [ { "label": "Bank transfer from organisation account", "value": "bank-transfer" }, { "label": "Card payment from organisation", "value": "card-payment" }, { "label": "Direct stablecoin funding (organisation already holds stablecoins)", "value": "direct-stablecoin" }, { "label": "Mixed: bank transfer for most, card for urgent payments", "value": "mixed-methods" } ], "propertyMapping": { "bank-transfer": { "technologies": [ "Bank-integrated fiat on-ramp" ], "technologyProperties": { "fundingSource": "Organisation bank account", "onRampSpeed": "1-2 business days (SEPA/ACH) or same-day (Faster Payments/wire)", "kybRequired": "Yes \u2014 organisation KYB verification" } }, "card-payment": { "technologies": [ "Card payment on-ramp" ], "technologyProperties": { "fundingSource": "Organisation payment card", "onRampSpeed": "Near-instant", "kybRequired": "Yes \u2014 card verification and organisation KYB" } }, "direct-stablecoin": { "technologies": [ "Direct stablecoin treasury funding" ], "technologyProperties": { "fundingSource": "Existing stablecoin holdings", "onRampSpeed": "Immediate (no fiat conversion needed)", "kybRequired": "Wallet verification only" } }, "mixed-methods": { "technologies": [ "Multi-method fiat on-ramp", "Card payment on-ramp" ], "technologyProperties": { "fundingSource": "Bank transfer (primary) + card (urgent)", "onRampSpeed": "Varies by method", "kybRequired": "Yes \u2014 full organisation KYB" } } }, "prefillFrom": null, "briefSection": "Payment rail requirements", "text": "How does your organisation currently fund international transfers or payments?", "ngoText": "How does your organisation currently fund international transfers or payments?" }, { "id": "proof-granularity", "type": "select", "options": [ { "label": "Programme level: show funds reached the programme", "value": "programme" }, { "label": "Activity level: show funds used for specific activities", "value": "activity" }, { "label": "Transaction level: trace every dollar to its end use", "value": "transaction" }, { "label": "Beneficiary level: show funds reached specific individuals", "value": "beneficiary" } ], "propertyMapping": { "programme": { "technologies": [ "Programme fund tracking", "Audit trail" ], "technologyProperties": { "traceabilityLevel": "Programme allocation proof", "evidenceType": "Fund flow to programme wallet" } }, "activity": { "technologies": [ "Activity-tagged transactions", "Cost allocation engine" ], "technologyProperties": { "traceabilityLevel": "Activity-level deployment proof", "evidenceType": "Activity-coded transaction records" } }, "transaction": { "technologies": [ "End-to-end transaction tracing", "Blockchain explorer" ], "technologyProperties": { "traceabilityLevel": "Full transaction chain", "evidenceType": "On-chain transaction hashes with metadata" } }, "beneficiary": { "technologies": [ "Beneficiary-level tracking", "Delivery confirmation module" ], "technologyProperties": { "traceabilityLevel": "Last-mile beneficiary proof", "evidenceType": "Beneficiary receipt confirmation + transaction hash" } } }, "prefillFrom": null, "briefSection": "Reporting and audit", "text": "At what level of granularity do donors need proof of funds deployment?", "ngoText": "At what level of granularity do donors need proof of funds deployment?" }, { "id": "proof-format", "type": "multiselect", "options": [ { "label": "Interactive dashboard with drill-down", "value": "dashboard" }, { "label": "Periodic PDF/spreadsheet reports", "value": "reports" }, { "label": "Digital transaction explorer (verify independently)", "value": "explorer" }, { "label": "API access for donor systems", "value": "api" }, { "label": "Certificate of deployment", "value": "certificate" } ], "propertyMapping": { "dashboard": { "technologies": [ "Donor accountability dashboard" ], "technologyProperties": { "presentationFormat": "Interactive web dashboard", "verificationMethod": "Visual drill-down with on-chain links" } }, "reports": { "technologies": [ "Automated proof-of-deployment report generator" ], "technologyProperties": { "presentationFormat": "Scheduled PDF/spreadsheet reports", "verificationMethod": "Report with transaction references" } }, "explorer": { "technologies": [ "Public/permissioned blockchain explorer" ], "technologyProperties": { "presentationFormat": "Self-service blockchain explorer", "verificationMethod": "Independent on-chain verification" } }, "api": { "technologies": [ "Donor API integration" ], "technologyProperties": { "presentationFormat": "Machine-readable API", "verificationMethod": "Automated data feed to donor systems" } }, "certificate": { "technologies": [ "Deployment certificate generator", "Cryptographic attestation" ], "technologyProperties": { "presentationFormat": "Signed deployment certificate", "verificationMethod": "Cryptographically signed attestation" } } }, "prefillFrom": null, "briefSection": "Reporting and audit", "text": "What formats do your donors require to verify proof of funds deployment?", "ngoText": "What formats do your donors require to verify proof of funds deployment?" }, { "id": "proof-timing", "type": "select", "options": [ { "label": "Real-time, as funds are deployed", "value": "realtime" }, { "label": "Within days of deployment", "value": "days" }, { "label": "At reporting periods (monthly/quarterly)", "value": "periodic" }, { "label": "At project/grant close-out", "value": "closeout" } ], "propertyMapping": { "realtime": { "technologies": [ "Real-time event streaming", "Live dashboard" ], "technologyProperties": { "proofLatency": "Real-time", "notificationCapability": "Push notifications on deployment" } }, "days": { "technologies": [ "Near real-time data updates" ], "technologyProperties": { "proofLatency": "T+1 to T+3", "notificationCapability": "Summary notifications" } }, "periodic": { "technologies": [ "Scheduled report generation" ], "technologyProperties": { "proofLatency": "Period-end", "notificationCapability": "Report-ready notification" } }, "closeout": { "technologies": [ "Close-out report generator" ], "technologyProperties": { "proofLatency": "End of project", "notificationCapability": "Close-out package delivery" } } }, "prefillFrom": null, "briefSection": "Payment operations", "text": "When do donors need proof of deployment?", "ngoText": "When do donors need proof of deployment?" }, { "id": "sq-UC-A-017-001", "type": "single-select", "options": [ { "value": "end-to-end-trace", "label": "End-to-end trace" }, { "value": "hop-by-hop-attestation", "label": "Hop-by-hop attestation" }, { "value": "aggregate-outcome", "label": "Aggregate outcome only" }, { "value": "detailed-waterfall", "label": "Detailed waterfall breakdown" }, { "value": "sampling-based", "label": "Sampling-based verification" } ], "propertyMapping": { "end-to-end-trace": { "technologies": [ "transaction-tracing", "full-lineage" ], "technologyProperties": {} }, "hop-by-hop-attestation": { "technologies": [ "hop-logging", "intermediate-verification" ], "technologyProperties": {} }, "aggregate-outcome": { "technologies": [ "outcome-tracking", "aggregate-reporting" ], "technologyProperties": {} }, "detailed-waterfall": { "technologies": [ "waterfall-tracking", "flow-visualization" ], "technologyProperties": {} }, "sampling-based": { "technologies": [ "audit-sampling", "statistical-verification" ], "technologyProperties": {} } }, "briefSection": "requirements", "text": "How do you currently handle multi-hop fund flows in deployment proof?", "ngoText": "How do you currently handle multi-hop fund flows in deployment proof?" }, { "id": "sq-UC-A-017-003", "type": "single-select", "options": [ { "value": "blockchain-hash", "label": "Digital fingerprint anchoring" }, { "value": "digital-signatures", "label": "Digital signatures" }, { "value": "merkle-tree", "label": "Structured proof-of-integrity verification" }, { "value": "immutable-ledger", "label": "Permanent tamper-proof register" }, { "value": "timestamped-snapshots", "label": "Timestamped snapshots" } ], "propertyMapping": { "blockchain-hash": { "technologies": [ "blockchain-anchoring", "hash-verification" ], "technologyProperties": {} }, "digital-signatures": { "technologies": [ "digital-signature", "key-management" ], "technologyProperties": {} }, "merkle-tree": { "technologies": [ "merkle-tree", "tree-verification" ], "technologyProperties": {} }, "immutable-ledger": { "technologies": [ "immutable-log", "append-only-storage" ], "technologyProperties": {} }, "timestamped-snapshots": { "technologies": [ "timestamp-service", "snapshot-storage" ], "technologyProperties": {} } }, "briefSection": "requirements", "text": "What tamper-evidence mechanism should protect deployment proof data?", "ngoText": "What tamper-evidence mechanism should protect deployment proof data?" } ], "complexityFactors": { "relationships": 2, "operationalChange": 2, "dataCompliance": 1 }, "suggestedCriteria": [ { "id": "SC-DEPLOY-PROOF", "name": "Verifiable Deployment Evidence", "description": "The provider can generate cryptographically verifiable proof that funds were deployed as intended. Donors need more than reports. They need evidence they can independently verify.", "weight": 0.3, "ratingGuide": { "5": "Blockchain-anchored proof of each deployment. Independent verification without provider access. Time-stamped, immutable, per-transaction evidence.", "4": "Strong cryptographic evidence. Verification requires provider access but is reliable.", "3": "Tamper-evident records. Audit trail. Standard verification through provider portal.", "2": "Access-controlled records. Standard reporting. No independent verification.", "1": "Reports only. No cryptographic or tamper-evident evidence." } }, { "id": "SC-DONOR-ACCESS", "name": "Donor Self-Service Verification", "description": "Donors can verify fund deployment themselves without relying on the NGO's reports. The power of proof-of-deployment is that the donor doesn't need to trust. They can verify.", "weight": 0.25, "ratingGuide": { "5": "Donor portal with drill-down from grant to individual transactions. Independent verification tool. Real-time data. No NGO intermediation needed.", "4": "Good donor portal. Transaction-level visibility. Some lag in data availability.", "3": "Donor access to summary data. Transaction detail on request. Periodic updates.", "2": "Reports provided to donors. No self-service access.", "1": "No donor-facing capability. All accountability via traditional reporting." } }, { "id": "SC-OUTCOME-LINK", "name": "Fund-to-Outcome Linkage", "description": "The provider can link financial deployment to programme outcomes. Showing that $X was spent says less than showing $X achieved Y outcomes for Z beneficiaries.", "weight": 0.2, "ratingGuide": { "5": "Financial data linked to outcome metrics and beneficiary counts. Cost-per-outcome calculations. Impact attribution visible to donors.", "4": "Good outcome linkage. Financial and programme data connected. Basic impact metrics.", "3": "Financial and programme reports available separately. Manual correlation possible.", "2": "Financial tracking only. Outcome data managed in separate system.", "1": "No outcome linkage. Purely financial deployment tracking." } }, { "id": "SC-REPORT-FORMAT-PROOF", "name": "Reporting & Export Flexibility", "description": "Proof-of-deployment evidence can be exported in formats donors recognise. Different donors want different levels of detail and different report structures.", "weight": 0.15, "ratingGuide": { "5": "Multiple export formats (PDF, spreadsheet, API). Customisable detail levels. Donor-specific templates. Embeddable verification links.", "4": "Good export options. Standard formats. Customisable detail.", "3": "PDF and spreadsheet export. Standard format. Manual customisation for donors.", "2": "Single export format. Limited customisation.", "1": "Screen-only viewing. No export capability." } }, { "id": "SC-AGGREGATION", "name": "Multi-Programme Aggregation", "description": "The provider can show fund deployment across multiple programmes and grants for a single donor. Large donors fund multiple programmes. They want a consolidated view of all their investments.", "weight": 0.1, "ratingGuide": { "5": "Cross-programme dashboard per donor. Aggregated deployment metrics. Per-programme drill-down. Portfolio-level insights.", "4": "Good cross-programme view. Aggregated data. Per-programme detail available.", "3": "Per-programme views. Manual aggregation for cross-programme analysis.", "2": "Individual programme reporting. No cross-programme capability.", "1": "No aggregation. Each programme reported independently with no donor consolidation." } } ], "procurement": { "marketMaturity": "emerging", "primaryMode": "tender", "alternativeModes": [ "rfq" ], "reasoning": "Donor accountability platforms exist with growing maturity.", "exampleProductCategories": [ "donor-accountability-platform", "impact-verification-saas" ], "partnerChannels": [], "lastReviewed": "2026-05-01" } }, { "id": "UC-A-018", "name": "Real-time expenditure tracking for donors", "category": "A", "subcategory": "Financial Reporting", "description": "Let donors see spending as it happens, rather than waiting for a quarterly report, with figures taken directly from field and payment records.", "bCriteria": [ "B1", "B3" ], "requiredComponents": [ { "component": "accounting-integration", "description": "Real-time expense feeds" }, { "component": "reporting-module", "description": "Live spending dashboard" }, { "component": "data-layer", "description": "Centralized expenditure data" }, { "component": "access-control", "description": "Donor data access rules" } ], "conditionalComponents": [ { "component": "encryption-privacy", "condition": "If sensitive programme data needs protection" } ], "crossCategoryDependencies": [ "UC-C-049 if research data involved" ], "p2TriggerConditions": { "description": "Activated when P2 shows donor transparency demands + real-time reporting needs + multiple donors", "rangeSignals": [ "donors >= 3", "transparencyDemand >= high", "reportingFrequency >= weekly" ] }, "contextFieldsTemplate": [ { "field": "donorCount", "source": "P0 donors", "description": "Number of major donors" }, { "field": "reportingFrequency", "source": "P0 donor agreements", "description": "Required update frequency" }, { "field": "dataGranularity", "source": "P2 reporting preferences", "description": "Level of detail" }, { "field": "accountingSystem", "source": "P0 Q13", "description": "Current accounting systems" } ], "implementationComplexity": "medium", "examples": { "note": "Transparent funding portals", "references": [ { "name": "Disberse", "url": "https://www.nesta.org.uk/feature/new-radicals-2018/disberse/", "solved": "Traced international aid fund transfers reducing intermediary costs" }, { "name": "UNICEF CryptoFund", "url": "https://www.unicef.org/innovation/stories/unicef-cryptofund", "solved": "Funded global tech startups addressing child welfare, transparently and at low cost" } ] }, "solutionQuestions": [ { "id": "donor-access-model", "type": "select", "options": [ { "label": "Dedicated donor portal with login", "value": "portal" }, { "label": "Shared dashboard (view-only link)", "value": "shared-link" }, { "label": "API feed into donor's own systems", "value": "api" }, { "label": "Automated email/notification summaries", "value": "notifications" } ], "propertyMapping": { "portal": { "technologies": [ "Donor portal platform", "Authentication module" ], "technologyProperties": { "accessMethod": "Authenticated web portal", "dataIsolation": "Per-donor data scoping" } }, "shared-link": { "technologies": [ "Embeddable dashboard", "Link-based access control" ], "technologyProperties": { "accessMethod": "Shareable view-only link", "dataIsolation": "Link-scoped data" } }, "api": { "technologies": [ "Donor API", "Webhook notifications" ], "technologyProperties": { "accessMethod": "RESTful API", "dataIsolation": "API key-scoped data" } }, "notifications": { "technologies": [ "Automated notification engine", "Summary generator" ], "technologyProperties": { "accessMethod": "Push notifications/email", "dataIsolation": "Per-donor filtered summaries" } } }, "prefillFrom": null, "briefSection": "Reporting and audit", "text": "How do donors currently access real-time expenditure data from your organisation?", "ngoText": "How do donors currently access real-time expenditure data from your organisation?" }, { "id": "expenditure-dimensions", "type": "multiselect", "options": [ { "label": "Budget vs actual spend", "value": "budget-vs-actual" }, { "label": "Spend by category (staff, travel, supplies, etc.)", "value": "by-category" }, { "label": "Spend by country/location", "value": "by-location" }, { "label": "Spend by activity/output", "value": "by-activity" }, { "label": "Burn rate and projected end date", "value": "burn-rate" }, { "label": "Individual transaction detail", "value": "transaction-detail" } ], "propertyMapping": { "budget-vs-actual": { "technologies": [ "Budget tracking module" ], "technologyProperties": { "analyticsCapability": "Budget variance analysis", "visualisation": "Bar/waterfall charts" } }, "by-category": { "technologies": [ "Category analytics module" ], "technologyProperties": { "analyticsCapability": "Category breakdown", "visualisation": "Pie/treemap charts" } }, "by-location": { "technologies": [ "Geographic analytics module" ], "technologyProperties": { "analyticsCapability": "Geographic spend analysis", "visualisation": "Map-based view" } }, "by-activity": { "technologies": [ "Activity-cost linking engine" ], "technologyProperties": { "analyticsCapability": "Activity-level cost analysis", "visualisation": "Activity-linked spend view" } }, "burn-rate": { "technologies": [ "Burn rate calculator", "Projection engine" ], "technologyProperties": { "analyticsCapability": "Spend velocity and projection", "visualisation": "Trend line with forecast" } }, "transaction-detail": { "technologies": [ "Transaction explorer" ], "technologyProperties": { "analyticsCapability": "Individual transaction lookup", "visualisation": "Transaction list with drill-down" } } }, "prefillFrom": null, "briefSection": "Reporting and audit", "text": "What expenditure dimensions should donors be able to see?", "ngoText": "What expenditure dimensions should donors be able to see?" }, { "id": "data-sensitivity", "type": "multiselect", "options": [ { "label": "Individual staff salaries", "value": "salaries" }, { "label": "Beneficiary personal information", "value": "beneficiary-pii" }, { "label": "Vendor/supplier identities", "value": "vendor-identities" }, { "label": "Security-related expenditures", "value": "security" }, { "label": "Nothing: full transparency to donors", "value": "nothing-hidden" } ], "propertyMapping": { "salaries": { "technologies": [ "Field-level data masking" ], "technologyProperties": { "privacyRequirement": "Salary amounts aggregated only", "maskingLevel": "Individual salary masking" } }, "beneficiary-pii": { "technologies": [ "PII anonymisation layer" ], "technologyProperties": { "privacyRequirement": "Beneficiary data anonymised", "maskingLevel": "PII stripped from donor view" } }, "vendor-identities": { "technologies": [ "Vendor anonymisation" ], "technologyProperties": { "privacyRequirement": "Vendor names masked", "maskingLevel": "Vendor category shown, identity hidden" } }, "security": { "technologies": [ "Security expenditure redaction" ], "technologyProperties": { "privacyRequirement": "Security items redacted", "maskingLevel": "Security category hidden" } }, "nothing-hidden": { "technologies": [], "technologyProperties": { "privacyRequirement": "None \u2014 full visibility", "maskingLevel": "No masking" } } }, "prefillFrom": null, "briefSection": "Identity and compliance", "text": "What expenditure data should be hidden from donors?", "ngoText": "What expenditure data should be hidden from donors?" }, { "id": "sq-UC-A-018-001", "type": "single-select", "options": [ { "value": "sync-when-connected", "label": "Sync when connected" }, { "value": "daily-batch-upload", "label": "Daily batch upload" }, { "value": "manual-entry-later", "label": "Manual entry later" }, { "value": "satellite-link", "label": "Satellite communication" }, { "value": "store-and-forward", "label": "Store and forward" } ], "propertyMapping": { "sync-when-connected": { "technologies": [ "connectivity-detection", "sync-engine" ], "technologyProperties": {} }, "daily-batch-upload": { "technologies": [ "batch-processing", "scheduled-sync" ], "technologyProperties": {} }, "manual-entry-later": { "technologies": [ "offline-form", "manual-entry-system" ], "technologyProperties": {} }, "satellite-link": { "technologies": [ "satellite-connection", "remote-connectivity" ], "technologyProperties": {} }, "store-and-forward": { "technologies": [ "local-cache", "deferred-sync" ], "technologyProperties": {} } }, "briefSection": "operations", "text": "How do you currently handle expenditure data latency for offline field operations?", "ngoText": "How do you currently handle expenditure data latency for offline field operations?" }, { "id": "sq-UC-A-018-003", "type": "single-select", "options": [ { "value": "threshold-alerts", "label": "Threshold-based alerts" }, { "value": "budget-burn-rate", "label": "Budget burn rate alerts" }, { "value": "variance-from-plan", "label": "Variance from plan" }, { "value": "no-alerts-pull-only", "label": "No alerts, pull only" }, { "value": "custom-triggers", "label": "Custom trigger rules" } ], "propertyMapping": { "threshold-alerts": { "technologies": [ "threshold-monitoring", "alert-system" ], "technologyProperties": {} }, "budget-burn-rate": { "technologies": [ "burn-rate-calculation", "rate-alerts" ], "technologyProperties": {} }, "variance-from-plan": { "technologies": [ "variance-analysis", "anomaly-detection" ], "technologyProperties": {} }, "no-alerts-pull-only": { "technologies": [ "dashboard-only", "on-demand-reporting" ], "technologyProperties": {} }, "custom-triggers": { "technologies": [ "rule-engine", "custom-logic" ], "technologyProperties": {} } }, "briefSection": "user-experience", "text": "What expenditure alerting should donors receive?", "ngoText": "What expenditure alerting should donors receive?" }, { "id": "accounting-integration", "type": "select", "options": [ { "label": "Direct integration with your existing accounting software", "value": "direct-erp" }, { "label": "Export-based: generate reports compatible with our accounting system", "value": "export-based" }, { "label": "Standalone ledger with manual reconciliation", "value": "standalone" }, { "label": "Not sure, need guidance on accounting integration", "value": "guidance-needed" } ], "propertyMapping": { "direct-erp": { "technologies": [ "Accounting system connection", "Automatic record updates", "Account structure alignment" ], "technologyProperties": { "integrationMethod": "Real-time connection", "reconciliation": "Automated", "reportFormat": "Compatible with your accounting system" } }, "export-based": { "technologies": [ "Accounting export module", "Report generation engine", "CSV/spreadsheet export service" ], "technologyProperties": { "integrationMethod": "Scheduled export (CSV/spreadsheet)", "reconciliation": "Semi-automated", "reportFormat": "Standard CSV/spreadsheet" } }, "standalone": { "technologies": [ "Standalone accounting ledger", "Manual reconciliation tools" ], "technologyProperties": { "integrationMethod": "Manual import/export", "reconciliation": "Manual", "reportFormat": "PDF/spreadsheet reports" } }, "guidance-needed": { "technologies": [ "Accounting integration framework" ], "technologyProperties": { "integrationMethod": "To be determined", "reconciliation": "To be determined", "reportFormat": "To be determined" } } }, "prefillFrom": null, "briefSection": "Financial integration", "text": "How should this solution integrate with your existing accounting or financial systems?", "ngoText": "How should this solution integrate with your existing accounting or financial systems?" } ], "complexityFactors": { "relationships": 2, "operationalChange": 2, "dataCompliance": 1 }, "suggestedCriteria": [ { "id": "SC-REALTIME-DONOR", "name": "Real-Time Donor Dashboard", "description": "Does the provider offer donors a live view of how their funds are being spent? 'Real-time' means hours or less, not monthly reports.", "weight": 0.3, "ratingGuide": { "5": "Live dashboard updated within minutes of transactions. Drill-down from total to individual expenditure. Map view of spending by location. Mobile accessible.", "4": "Near-real-time (hourly). Good drill-down. Location context. Desktop dashboard.", "3": "Daily updated dashboard. Programme-level spending. Basic geographic view.", "2": "Weekly summaries. Limited drill-down. No geographic context.", "1": "No live access. Donors rely on periodic reports." } }, { "id": "SC-GRANULARITY", "name": "Expenditure Granularity & Categorisation", "description": "This measures the level of detail at which donors can see spending. Some donors want category-level summaries, others want line-item visibility. The system should accommodate both.", "weight": 0.25, "ratingGuide": { "5": "Line-item to summary with configurable drill-down. Category, activity, location, and time dimensions. Donor chooses their detail level.", "4": "Good drill-down from summary to transaction. Multiple categorisation dimensions.", "3": "Category-level reporting with per-transaction detail available on request.", "2": "Category summaries only. Transaction detail not donor-accessible.", "1": "Total spending only. No categorisation visible to donors." } }, { "id": "SC-ACCESS-CONTROL-DONOR", "name": "Donor Access Control", "description": "Different donors can see only their funded activities. Multi-donor programmes require strict data partitioning so donors see their contribution's impact, not other donors' data.", "weight": 0.2, "ratingGuide": { "5": "Per-donor data partitioning. Donor sees only their funded activities. Shared costs allocated transparently. Multiple donor access levels configurable.", "4": "Good donor isolation. Per-fund access. Basic shared cost visibility.", "3": "Donor-specific views. Some shared programme data visible. Manual access management.", "2": "Limited access control. Donors may see other donors' data. Manual filtering.", "1": "No access control. All donors see all data or no data." } }, { "id": "SC-BENCHMARK-COMPARE", "name": "Budget vs Actual Comparison", "description": "Donors can compare actual expenditure against the approved budget in real time. Budget adherence is the most common donor concern, showing it live builds confidence.", "weight": 0.15, "ratingGuide": { "5": "Live budget vs actual by line item. Variance highlighting. Burn rate projections. Early warning for potential overruns or underspend.", "4": "Good budget comparison. Variance alerts. Basic projections.", "3": "Budget vs actual at category level. Manual variance analysis.", "2": "Budget shown alongside actuals. No variance calculation.", "1": "No budget comparison. Actuals only." } }, { "id": "SC-DATA-EXPORT-DONOR", "name": "Data Export & Integration", "description": "Donors can export tracking data into their own systems. Large institutional donors often want to pull data into their portfolio management platforms.", "weight": 0.1, "ratingGuide": { "5": "API access for donor systems. Automated data feeds. Multiple export formats. Scheduled exports.", "4": "API available. Good export formats. Manual or scheduled exports.", "3": "CSV/spreadsheet export. Standard formats. On-demand.", "2": "PDF export only. No structured data export.", "1": "No export capability. Screen viewing only." } } ], "procurement": { "marketMaturity": "emerging", "primaryMode": "rfq", "alternativeModes": [ "off-the-shelf" ], "reasoning": "Real-time donor expenditure dashboards available in newer SaaS.", "exampleProductCategories": [ "donor-dashboard-saas", "grants-management-platform" ], "partnerChannels": [], "lastReviewed": "2026-05-01" } }, { "id": "UC-A-019", "name": "Microfinance and lending to underbanked beneficiaries", "category": "A", "subcategory": "Financial Inclusion", "description": "Offer small loans to people who cannot use ordinary banks, and keep repayment records that every lender involved can rely on.", "bCriteria": [ "B4", "B8" ], "requiredComponents": [ { "component": "payment-rails", "description": "Loan disbursement network" }, { "component": "stablecoin", "description": "Loan denomination" }, { "component": "smart-contracts", "description": "Loan agreement automation" }, { "component": "beneficiary-wallet", "description": "Beneficiary loan account" }, { "component": "compliance-screening", "description": "Lending compliance" } ], "conditionalComponents": [ { "component": "identity-verification", "condition": "For KYC in lending", "linksTo": "UC-B-024" }, { "component": "oracle-data", "condition": "If credit scoring uses external data" } ], "crossCategoryDependencies": [ "UC-B-035 if skills verification for targeting", "UC-E-021 if savings groups coordination" ], "p2TriggerConditions": { "description": "Activated when P2 shows financial inclusion focus + underbanked populations + lending programmes", "rangeSignals": [ "bankingAccess <= 50%", "lendingProgramme >= true", "borrowerCount >= 100+" ] }, "contextFieldsTemplate": [ { "field": "borrowerCount", "source": "P2 programme scale", "description": "Number of borrowers" }, { "field": "loanSize", "source": "P2 loan amounts", "description": "Typical loan amounts" }, { "field": "loanTerm", "source": "P2 loan structure", "description": "Loan duration" }, { "field": "interestRate", "source": "P2 programme design", "description": "Lending rates" }, { "field": "repaymentTracking", "source": "P0 Q13", "description": "Current repayment systems" } ], "implementationComplexity": "high", "examples": { "note": "Digital microfinance platforms", "references": [ { "name": "Kiva Protocol", "url": "https://www.kiva.org/blog/kivas-next-frontier-kiva-protocol", "solved": "Microloans to entrepreneurs without traditional credit history" }, { "name": "Celo / Grameen Foundation", "url": "https://grameenfoundation.org/stories/press-releases/celo-foundation-announces-alliance-for-prosperity-to-build-financial-tools-for-5-6b-smartphone-owners", "solved": "Mobile-first financial services access for underserved populations" }, { "name": "BanQu", "url": "https://goexplorer.org/building-an-economic-identity-on-blockchain/", "solved": "Portable economic identity for refugees and marginalised populations" } ] }, "solutionQuestions": [ { "id": "stablecoin-approach", "type": "select", "options": [ { "label": "A regulated digital dollar", "value": "usd-pegged" }, { "label": "EUR-pegged stablecoin", "value": "eur-pegged" }, { "label": "Multiple stablecoins depending on corridor", "value": "multi-stablecoin" }, { "label": "Not sure, need guidance on stablecoin selection", "value": "guidance-needed" } ], "propertyMapping": { "usd-pegged": { "technologies": [ "USD-pegged stablecoin rail", "Stablecoin settlement layer" ], "technologyProperties": { "stablecoinType": "A regulated digital dollar", "fxConversion": "At on-ramp and off-ramp points" } }, "eur-pegged": { "technologies": [ "EUR-pegged stablecoin rail", "Stablecoin settlement layer" ], "technologyProperties": { "stablecoinType": "EUR-pegged", "fxConversion": "At on-ramp and off-ramp points" } }, "multi-stablecoin": { "technologies": [ "Multi-stablecoin settlement layer", "Automated FX conversion" ], "technologyProperties": { "stablecoinType": "Multiple denominations", "fxConversion": "Digital or at off-ramp" } }, "guidance-needed": { "technologies": [ "Stablecoin settlement layer" ], "technologyProperties": { "stablecoinType": "To be determined during solution design", "fxConversion": "To be determined" } } }, "prefillFrom": null, "briefSection": "Stablecoin and FX", "text": "What stablecoin approach is preferred for this solution?", "ngoText": "What stablecoin approach is preferred for this solution?" }, { "id": "lending-model", "type": "select", "options": [ { "label": "Group lending (solidarity groups)", "value": "group" }, { "label": "Individual microloans", "value": "individual" }, { "label": "Revolving loan fund", "value": "revolving" }, { "label": "Asset financing (pay-as-you-go)", "value": "asset-financing" }, { "label": "Emergency/disaster recovery loans", "value": "emergency" } ], "propertyMapping": { "group": { "technologies": [ "Group lending smart contract", "Group wallet management", "Peer guarantee mechanism" ], "technologyProperties": { "lendingModel": "Solidarity group", "guaranteeModel": "Group co-guarantee", "repaymentStructure": "Group-collected individual repayments" } }, "individual": { "technologies": [ "Individual loan smart contract", "Credit scoring module" ], "technologyProperties": { "lendingModel": "Individual microloan", "guaranteeModel": "Individual assessment", "repaymentStructure": "Direct individual repayment" } }, "revolving": { "technologies": [ "Revolving fund smart contract", "Pool management" ], "technologyProperties": { "lendingModel": "Revolving fund", "guaranteeModel": "Pool-based", "repaymentStructure": "Repayments recirculate to pool" } }, "asset-financing": { "technologies": [ "Pay-as-you-go smart contract", "IoT lock/unlock" ], "technologyProperties": { "lendingModel": "Asset-linked PAYG", "guaranteeModel": "Asset collateral (remote disable)", "repaymentStructure": "Usage-linked payments" } }, "emergency": { "technologies": [ "Emergency loan smart contract", "Rapid disbursement" ], "technologyProperties": { "lendingModel": "Emergency/recovery", "guaranteeModel": "Soft terms/social guarantee", "repaymentStructure": "Flexible/deferred" } } }, "prefillFrom": null, "briefSection": "Payment logic", "text": "What type of lending/microfinance programme do you operate or plan?", "ngoText": "What type of lending/microfinance programme do you operate or plan?" }, { "id": "loan-size", "type": "select", "options": [ { "label": "Under $50", "value": "nano" }, { "label": "$50\u2013$200", "value": "micro" }, { "label": "$200\u2013$1,000", "value": "small" }, { "label": "$1,000\u2013$5,000", "value": "medium" }, { "label": "Over $5,000", "value": "large" } ], "propertyMapping": { "nano": { "technologies": [ "Layer 1 payment rail" ], "technologyProperties": { "maxTransactionFee": "Sub-$0.001", "feeModel": "Must be negligible \u2014 sub-cent fees critical" } }, "micro": { "technologies": [ "Layer 1 payment rail" ], "technologyProperties": { "maxTransactionFee": "Sub-$0.01", "feeModel": "Sub-cent fees important" } }, "small": { "technologies": [ "Layer 1 payment rail" ], "technologyProperties": { "maxTransactionFee": "Sub-$0.05", "feeModel": "Low fixed fee" } }, "medium": { "technologies": [ "Layer 1 payment rail" ], "technologyProperties": { "maxTransactionFee": "Sub-$0.10", "feeModel": "Fixed low fee" } }, "large": { "technologies": [ "Layer 1 payment rail" ], "technologyProperties": { "maxTransactionFee": "Sub-$0.50", "feeModel": "Standard" } } }, "prefillFrom": null, "briefSection": "Payment rail requirements", "text": "What is the typical loan size?", "ngoText": "What is the typical loan size?" }, { "id": "borrower-profile", "type": "select", "options": [ { "label": "Rural farmers/agricultural workers", "value": "rural-agricultural" }, { "label": "Urban micro-entrepreneurs", "value": "urban-micro" }, { "label": "Women's savings/lending groups", "value": "womens-groups" }, { "label": "Youth/displaced populations", "value": "youth-displaced" }, { "label": "Mixed profiles", "value": "mixed" } ], "propertyMapping": { "rural-agricultural": { "technologies": [ "USSD/SMS-based wallet", "Offline capability", "Agent network" ], "technologyProperties": { "borrowerInterface": "USSD/SMS with agent support", "literacyRequirement": "Minimal \u2014 icon-based or voice", "connectivity": "Offline-first essential" } }, "urban-micro": { "technologies": [ "Mobile wallet application" ], "technologyProperties": { "borrowerInterface": "Mobile app", "literacyRequirement": "Basic smartphone literacy", "connectivity": "Online-first acceptable" } }, "womens-groups": { "technologies": [ "Group wallet with individual accounts", "USSD/SMS interface" ], "technologyProperties": { "borrowerInterface": "Group + individual view", "literacyRequirement": "Group leader training model", "connectivity": "Mixed \u2014 USSD fallback" } }, "youth-displaced": { "technologies": [ "Mobile wallet", "Simplified onboarding" ], "technologyProperties": { "borrowerInterface": "Mobile-first simplified", "literacyRequirement": "Basic digital literacy", "connectivity": "Varies \u2014 offline fallback needed" } }, "mixed": { "technologies": [ "Multi-channel platform" ], "technologyProperties": { "borrowerInterface": "App + USSD + agent", "literacyRequirement": "Tiered interface complexity", "connectivity": "Adaptive" } } }, "prefillFrom": null, "briefSection": "End-user interface", "text": "What is the typical borrower profile?", "ngoText": "What is the typical borrower profile?" }, { "id": "repayment-collection", "type": "multiselect", "options": [ { "label": "Mobile money deduction", "value": "mobile-money" }, { "label": "Direct wallet deduction (auto-debit)", "value": "auto-debit" }, { "label": "Agent-collected cash", "value": "agent-cash" }, { "label": "Bank transfer", "value": "bank" }, { "label": "Group leader collects from members", "value": "group-leader" } ], "propertyMapping": { "mobile-money": { "technologies": [ "Mobile money auto-debit integration" ], "technologyProperties": { "repaymentChannel": "Mobile money", "automationLevel": "Scheduled auto-debit" } }, "auto-debit": { "technologies": [ "Automated auto-debit", "Wallet deduction module" ], "technologyProperties": { "repaymentChannel": "Direct wallet deduction", "automationLevel": "Automatedtriggered" } }, "agent-cash": { "technologies": [ "Agent collection module", "Cash receipt digitisation" ], "technologyProperties": { "repaymentChannel": "Agent cash collection", "automationLevel": "Manual collection, digital recording" } }, "bank": { "technologies": [ "Bank debit integration" ], "technologyProperties": { "repaymentChannel": "Bank transfer/debit", "automationLevel": "Standing order or direct debit" } }, "group-leader": { "technologies": [ "Group repayment module", "Leader collection interface" ], "technologyProperties": { "repaymentChannel": "Group leader intermediation", "automationLevel": "Leader-facilitated digital recording" } } }, "prefillFrom": null, "briefSection": "Payment operations", "text": "How will loan repayments be collected?", "ngoText": "How will loan repayments be collected?" }, { "id": "credit-assessment", "type": "select", "options": [ { "label": "Traditional credit bureau check", "value": "credit-bureau" }, { "label": "Alternative data (mobile usage, transaction history)", "value": "alternative-data" }, { "label": "Group assessment/peer vouching", "value": "group-assessment" }, { "label": "Programme participation history", "value": "programme-history" }, { "label": "No credit assessment, all eligible participants receive", "value": "no-assessment" } ], "propertyMapping": { "credit-bureau": { "technologies": [ "Credit bureau API integration" ], "technologyProperties": { "creditModel": "Bureau-based scoring", "dataSource": "Credit bureau" } }, "alternative-data": { "technologies": [ "Alternative credit scoring engine", "Transaction history analyser" ], "technologyProperties": { "creditModel": "Alternative data scoring", "dataSource": "Mobile/transaction/behavioral data" } }, "group-assessment": { "technologies": [ "Group attestation module" ], "technologyProperties": { "creditModel": "Peer assessment", "dataSource": "Group member vouching" } }, "programme-history": { "technologies": [ "Programme participation tracker" ], "technologyProperties": { "creditModel": "History-based assessment", "dataSource": "Internal programme data" } }, "no-assessment": { "technologies": [], "technologyProperties": { "creditModel": "Universal eligibility", "dataSource": "Programme enrolment only" } } }, "prefillFrom": null, "briefSection": "Identity and compliance", "text": "How is creditworthiness currently assessed (or will be)?", "ngoText": "How is creditworthiness currently assessed (or will be)?" }, { "id": "sq-UC-A-019-001", "type": "single-select", "options": [ { "value": "grace-period-then-flag", "label": "Grace period then flag" }, { "value": "community-mediation", "label": "Community mediation" }, { "value": "write-off-threshold", "label": "Write-off threshold" }, { "value": "restructure-terms", "label": "Restructure loan terms" }, { "value": "escalation-to-partner", "label": "Escalation to partner" } ], "propertyMapping": { "grace-period-then-flag": { "technologies": [ "grace-period-logic", "default-flagging" ], "technologyProperties": {} }, "community-mediation": { "technologies": [ "mediation-workflow", "community-involvement" ], "technologyProperties": {} }, "write-off-threshold": { "technologies": [ "write-off-logic", "loss-accounting" ], "technologyProperties": {} }, "restructure-terms": { "technologies": [ "amendment-workflow", "loan-modification" ], "technologyProperties": {} }, "escalation-to-partner": { "technologies": [ "escalation-routing", "partner-involvement" ], "technologyProperties": {} } }, "briefSection": "operations", "text": "What default management and recovery process do you currently have?", "ngoText": "What default management and recovery process do you currently have?" }, { "id": "compliance-screening", "type": "select", "options": [ { "label": "AML/KYC screening with sanctions list checking", "value": "aml-kyc" }, { "label": "Basic identity verification only", "value": "basic-id" }, { "label": "Full regulatory compliance suite (AML + KYC + ongoing monitoring)", "value": "full-suite" }, { "label": "Not sure, need guidance", "value": "guidance-needed" } ], "propertyMapping": { "aml-kyc": { "technologies": [ "AML/KYC compliance screening", "Sanctions list checker", "PEP screening service" ], "technologyProperties": { "screeningLevel": "AML + KYC + sanctions", "frequency": "At onboarding + periodic re-screening", "dataSource": "Global sanctions and watchlists" } }, "basic-id": { "technologies": [ "Basic compliance screening", "Identity document verifier" ], "technologyProperties": { "screeningLevel": "Identity verification only", "frequency": "At onboarding", "dataSource": "Government ID databases" } }, "full-suite": { "technologies": [ "Full compliance screening suite", "Ongoing monitoring service", "Regulatory reporting module" ], "technologyProperties": { "screeningLevel": "AML + KYC + sanctions + ongoing monitoring", "frequency": "Continuous", "dataSource": "Multiple regulatory databases" } }, "guidance-needed": { "technologies": [ "Compliance screening framework" ], "technologyProperties": { "screeningLevel": "To be determined", "frequency": "To be determined", "dataSource": "To be determined" } } }, "prefillFrom": null, "briefSection": "Compliance", "text": "What level of compliance screening is required?", "ngoText": "What level of compliance screening is required?" }, { "id": "credit-history-need", "label": "Does the programme need to build credit histories for populations with no formal banking records?", "type": "select", "briefSection": "credit-history-building", "options": [ { "label": "Yes, building credit histories is a primary objective", "value": "primary" }, { "label": "Yes, as a secondary benefit of the lending programme", "value": "secondary" }, { "label": "No, we have access to existing credit data", "value": "no" } ], "propertyMapping": { "primary": { "technologies": [ "Credit history ledger", "Reputation scoring engine" ], "technologyProperties": { "creditHistoryBuilding": "Primary objective", "dataPortability": "Cross-organisation credit history needed" } }, "secondary": { "technologies": [ "Transaction-based credit scoring" ], "technologyProperties": { "creditHistoryBuilding": "Secondary benefit", "dataPortability": "Internal credit records" } }, "no": { "technologies": [], "technologyProperties": { "creditHistoryBuilding": "Not needed", "dataPortability": "Existing credit infrastructure" } } }, "text": "Does the programme need to build credit histories for populations with no formal banking records?" }, { "id": "credit-signals", "label": "What data will be used as credit signals for unbanked borrowers?", "type": "multiselect", "briefSection": "credit-history-building", "options": [ { "label": "Digital transaction history (previous loan repayments)", "value": "tx-history" }, { "label": "Savings group participation and deposit records", "value": "savings-group" }, { "label": "Community attestations (peer vouching, group guarantees)", "value": "community" }, { "label": "Mobile money transaction patterns", "value": "mobile-money" }, { "label": "Agricultural production records", "value": "agricultural" } ], "propertyMapping": { "tx-history": { "technologies": [ "On-chain credit scoring module" ], "technologyProperties": { "creditSignal": "Blockchain transaction history" } }, "savings-group": { "technologies": [ "Savings group integration module" ], "technologyProperties": { "creditSignal": "Savings group participation" } }, "community": { "technologies": [ "Community attestation engine" ], "technologyProperties": { "creditSignal": "Peer and community attestations" } }, "mobile-money": { "technologies": [ "Mobile money data connector" ], "technologyProperties": { "creditSignal": "Mobile money transaction patterns" } }, "agricultural": { "technologies": [ "Agricultural production ledger connector" ], "technologyProperties": { "creditSignal": "Agricultural production records" } } }, "text": "What data will be used as credit signals for unbanked borrowers?" }, { "id": "credit-portability", "label": "Does the credit history need to be portable across organisations or geographies?", "type": "select", "briefSection": "credit-history-building", "options": [ { "label": "Yes, borrowers should carry their credit history to any participating lender", "value": "fully-portable" }, { "label": "Partially, within a network of partner organisations", "value": "network-portable" }, { "label": "No, credit history stays within this programme", "value": "not-portable" } ], "propertyMapping": { "fully-portable": { "technologies": [ "Portable credit credential (W3C VC)", "Cross-org credit verifier" ], "technologyProperties": { "creditPortability": "Fully portable", "credentialStandard": "W3C Verifiable Credential recommended" } }, "network-portable": { "technologies": [ "Network credit sharing protocol" ], "technologyProperties": { "creditPortability": "Network-portable", "credentialStandard": "Partner network agreement" } }, "not-portable": { "technologies": [ "Internal credit ledger" ], "technologyProperties": { "creditPortability": "Internal only", "credentialStandard": "No external sharing" } } }, "text": "Does the credit history need to be portable across organisations or geographies?" }, { "id": "existing-informal-credit", "label": "What existing informal credit or savings mechanisms exist in the community?", "type": "multiselect", "briefSection": "credit-history-building", "options": [ { "label": "Village savings and loan associations (VSLAs)", "value": "vsla" }, { "label": "Rotating savings and credit associations (ROSCAs/chamas)", "value": "rosca" }, { "label": "Informal moneylenders", "value": "moneylenders" }, { "label": "Mobile money-based lending", "value": "mobile-lending" }, { "label": "No existing mechanisms", "value": "none" } ], "propertyMapping": { "vsla": { "technologies": [], "technologyProperties": { "existingCredit": "VSLAs present \u2014 integrate records" } }, "rosca": { "technologies": [], "technologyProperties": { "existingCredit": "ROSCAs present \u2014 integrate participation data" } }, "moneylenders": { "technologies": [], "technologyProperties": { "existingCredit": "Informal moneylenders \u2014 opportunity to formalise" } }, "mobile-lending": { "technologies": [], "technologyProperties": { "existingCredit": "Mobile lending present \u2014 data integration possible" } }, "none": { "technologies": [], "technologyProperties": { "existingCredit": "No existing mechanisms \u2014 greenfield" } } }, "text": "What existing informal credit or savings mechanisms exist in the community?" }, { "id": "beneficiary-choice", "label": "How will beneficiaries exercise choice in how they receive and use this service?", "type": "select", "briefSection": "End-user interface", "options": [ { "label": "Beneficiaries choose between delivery methods (cash, voucher, mobile money, direct)", "value": "delivery-choice" }, { "label": "Beneficiaries choose preferred merchants or service points", "value": "merchant-choice" }, { "label": "Beneficiaries control their own data sharing preferences", "value": "data-choice" }, { "label": "Multiple choice dimensions (delivery + merchant + data)", "value": "full-choice" }, { "label": "Limited choice: programme constraints determine delivery", "value": "limited" } ], "propertyMapping": { "delivery-choice": { "technologies": [], "technologyProperties": { "beneficiaryChoice": "Delivery method choice", "dignityDesign": "Beneficiaries select preferred receipt method" } }, "merchant-choice": { "technologies": [], "technologyProperties": { "beneficiaryChoice": "Merchant/service point choice", "dignityDesign": "Beneficiaries select where to redeem" } }, "data-choice": { "technologies": [], "technologyProperties": { "beneficiaryChoice": "Data sharing choice", "dignityDesign": "Beneficiaries control personal data sharing" } }, "full-choice": { "technologies": [], "technologyProperties": { "beneficiaryChoice": "Multi-dimensional choice", "dignityDesign": "Full beneficiary agency across delivery, merchant, and data" } }, "limited": { "technologies": [], "technologyProperties": { "beneficiaryChoice": "Limited by programme design", "dignityDesign": "Programme constraints; beneficiary informed of reasons" } } }, "text": "How will beneficiaries exercise choice in how they receive and use this service?" } ], "complexityFactors": { "relationships": 3, "operationalChange": 4, "dataCompliance": 3 }, "securityTier": "B", "suggestedCriteria": [ { "id": "SC-LENDING-PRODUCT", "name": "Lending Product Flexibility", "description": "The provider can support the range of microfinance products NGOs offer. This includes group lending, individual loans, revolving funds, and graduated lending with different terms and conditions.", "weight": 0.25, "ratingGuide": { "5": "Group lending (Grameen-style), individual loans, revolving funds, and graduated lending. Configurable terms, grace periods, and repayment schedules. Sharia-compliant options.", "4": "Multiple lending products. Good term configuration. Group and individual supported.", "3": "Basic individual and group lending. Standard term options. Limited product variety.", "2": "Single loan product with configurable terms. No group lending.", "1": "Fixed loan product. No customisation for different microfinance models." } }, { "id": "SC-BENEFICIARY-ACCESS", "name": "Beneficiary Accessibility", "description": "Underbanked beneficiaries can access the system using basic phones or agent networks. The target population often lacks smartphones and bank accounts.", "weight": 0.25, "ratingGuide": { "5": "USSD/SMS for basic phones. Agent network for cash-in/cash-out. Works without internet. Available in local languages. No bank account required.", "4": "USSD or SMS access. Some agent network. Smartphone app also available. Multi-language.", "3": "Basic smartphone app. Agent cash-out in urban areas. English plus one local language.", "2": "Smartphone required. Limited agent network. English-only interface.", "1": "Requires smartphone with internet and bank account. Urban only." } }, { "id": "SC-REPAYMENT-TRACK", "name": "Repayment Tracking & Collection", "description": "This looks at how the provider handles repayment collection and tracking. Microfinance requires managing thousands of small repayments, many via mobile money or cash, with clear default management.", "weight": 0.2, "ratingGuide": { "5": "Automated repayment collection via mobile money. Cash collection tracking through agents. Real-time portfolio status. Automated reminders (SMS). Default early-warning system.", "4": "Good automated collection. Mobile money and manual options. Portfolio tracking. Reminders.", "3": "Manual collection recording. Mobile money integration. Basic portfolio views. Manual reminders.", "2": "Basic repayment recording. Manual tracking. No automated collection or reminders.", "1": "Paper-based repayment tracking. No digital collection capability." } }, { "id": "SC-CREDIT-SCORING", "name": "Alternative Credit Assessment", "description": "The provider offers credit scoring methods for people without credit history. Traditional credit scores don't exist for underbanked populations. Alternative data (repayment history, mobile money usage, group references) is essential.", "weight": 0.2, "ratingGuide": { "5": "Alternative credit scoring using mobile money history, group lending performance, and social references. Progressive lending based on repayment track record. Community-vouching integration.", "4": "Good alternative scoring. Repayment history-based. Group performance considered.", "3": "Basic credit assessment. Repayment history from platform. Manual group evaluation.", "2": "Manual credit assessment. No scoring model. Individual evaluation.", "1": "No credit assessment capability. Fixed terms regardless of borrower profile." } }, { "id": "SC-REGULATORY-MICRO", "name": "Microfinance Regulatory Compliance", "description": "The provider handles the regulatory requirements for microfinance in target markets. Lending regulations vary dramatically. Interest rate caps, licensing, consumer protection, and reporting requirements differ per country.", "weight": 0.1, "ratingGuide": { "5": "Compliant in 5+ developing market jurisdictions. Automated interest cap enforcement. Consumer protection features. Regulatory reporting built in.", "4": "Compliant in 2-4 markets. Good regulatory features. Interest cap awareness.", "3": "Compliant in primary market. Basic regulatory features. Manual reporting.", "2": "Limited regulatory knowledge. Basic compliance features. Manual everything.", "1": "No microfinance regulatory capability. Compliance is the NGO's responsibility entirely." } } ], "procurement": { "marketMaturity": "emerging", "primaryMode": "integrator-led", "alternativeModes": [ "rfq" ], "reasoning": "Microfinance platforms exist; underbanked-beneficiary integration often bespoke.", "exampleProductCategories": [ "microfinance-platform", "digital-microcredit-rails" ], "partnerChannels": [], "lastReviewed": "2026-05-01" } }, { "id": "UC-A-020", "name": "Savings group management and record-keeping", "category": "A", "subcategory": "Financial Inclusion", "description": "Keep the savings and loan records of community savings groups in one shared record, so members and facilitators do not end up with different figures.", "bCriteria": [ "B1", "B3" ], "requiredComponents": [ { "component": "beneficiary-wallet", "description": "Group savings account" }, { "component": "smart-contracts", "description": "Savings group rules automation" }, { "component": "record-keeping-platform", "description": "Immutable savings records" }, { "component": "reporting-module", "description": "Group financial reporting" } ], "conditionalComponents": [ { "component": "identity-verification", "condition": "For member KYC", "linksTo": "UC-B-024" }, { "component": "offline-sync", "condition": "If groups lack reliable connectivity" } ], "crossCategoryDependencies": [ "UC-E-068 if group voting on fund use" ], "p2TriggerConditions": { "description": "Activated when P2 shows savings group programmes + multiple groups + record-keeping burden", "rangeSignals": [ "savingsGroups >= 10+", "memberCount >= 100+", "recordKeeping = manual" ] }, "contextFieldsTemplate": [ { "field": "groupCount", "source": "P2 programme scale", "description": "Number of savings groups" }, { "field": "memberPerGroup", "source": "P2 group composition", "description": "Members per group" }, { "field": "savingsFrequency", "source": "P2 group practices", "description": "How often members save" }, { "field": "connectivity", "source": "P4", "description": "Group member connectivity" } ], "implementationComplexity": "medium", "examples": { "note": "Community savings group platforms", "references": [ { "name": "Celo / Grameen Foundation", "url": "https://grameenfoundation.org/stories/press-releases/celo-foundation-announces-alliance-for-prosperity-to-build-financial-tools-for-5-6b-smartphone-owners", "solved": "Mobile-first financial services access for underserved populations" }, { "name": "Kiva Protocol", "url": "https://www.kiva.org/blog/kivas-next-frontier-kiva-protocol", "solved": "Microloans to entrepreneurs without traditional credit history" } ] }, "solutionQuestions": [ { "id": "group-structure", "type": "select", "options": [ { "label": "VSLA (Village Savings and Loan Association)", "value": "vsla" }, { "label": "ROSCA (Rotating Savings and Credit Association)", "value": "rosca" }, { "label": "ASCA (Accumulating Savings and Credit Association)", "value": "asca" }, { "label": "Informal savings groups (custom structure)", "value": "informal" }, { "label": "Multiple types across programmes", "value": "multiple" } ], "propertyMapping": { "vsla": { "technologies": [ "VSLA smart contract template", "Group wallet", "Share tracking module" ], "technologyProperties": { "groupModel": "VSLA cycle management", "accountingLogic": "Share-based contributions + social fund + loan tracking", "cycleManagement": "Annual cycle with share-out" } }, "rosca": { "technologies": [ "ROSCA smart contract template", "Rotation scheduler" ], "technologyProperties": { "groupModel": "ROSCA rotation management", "accountingLogic": "Fixed contribution, rotating payout", "cycleManagement": "Per-round rotation" } }, "asca": { "technologies": [ "ASCA smart contract template", "Loan management module" ], "technologyProperties": { "groupModel": "ASCA accumulation management", "accountingLogic": "Accumulated savings + interest-bearing loans", "cycleManagement": "Continuous with periodic settlement" } }, "informal": { "technologies": [ "Configurable group finance smart contract" ], "technologyProperties": { "groupModel": "Custom group rules", "accountingLogic": "Configurable contribution and distribution rules", "cycleManagement": "Custom cycle definition" } }, "multiple": { "technologies": [ "Multi-model group finance platform" ], "technologyProperties": { "groupModel": "Multi-model support", "accountingLogic": "Template-based per group type", "cycleManagement": "Type-specific" } } }, "prefillFrom": null, "briefSection": "Payment logic", "text": "What type of savings group structure do you support?", "ngoText": "What type of savings group structure do you support?" }, { "id": "group-size", "type": "select", "options": [ { "label": "5-10 members", "value": "small" }, { "label": "10-25 members", "value": "medium" }, { "label": "25-50 members", "value": "large" }, { "label": "Varies widely", "value": "varies" } ], "propertyMapping": { "small": { "technologies": [ "Group wallet with individual tracking" ], "technologyProperties": { "groupCapacity": "Small group optimised", "consensusMechanism": "Simple majority" } }, "medium": { "technologies": [ "Group wallet with individual tracking" ], "technologyProperties": { "groupCapacity": "Standard group size", "consensusMechanism": "Configurable quorum" } }, "large": { "technologies": [ "Group wallet with sub-group support" ], "technologyProperties": { "groupCapacity": "Large group with possible sub-groups", "consensusMechanism": "Representative/committee model" } }, "varies": { "technologies": [ "Flexible group management" ], "technologyProperties": { "groupCapacity": "Configurable group size", "consensusMechanism": "Adaptive" } } }, "prefillFrom": null, "briefSection": "Payment operations", "text": "What is the typical savings group size?", "ngoText": "What is the typical savings group size?" }, { "id": "group-total-count", "type": "select", "options": [ { "label": "Under 50 groups", "value": "small" }, { "label": "50-200 groups", "value": "medium" }, { "label": "200-1,000 groups", "value": "large" }, { "label": "Over 1,000 groups", "value": "very-large" } ], "propertyMapping": { "small": { "technologies": [ "Basic group management dashboard" ], "technologyProperties": { "platformScale": "Small portfolio", "monitoringCapability": "Manual oversight feasible" } }, "medium": { "technologies": [ "Group management platform", "Portfolio dashboard" ], "technologyProperties": { "platformScale": "Medium portfolio", "monitoringCapability": "Semi-automated monitoring" } }, "large": { "technologies": [ "Enterprise group management", "Automated monitoring", "Analytics engine" ], "technologyProperties": { "platformScale": "Large portfolio", "monitoringCapability": "Automated monitoring with exception alerts" } }, "very-large": { "technologies": [ "Enterprise group management", "AI-assisted monitoring", "Predictive analytics" ], "technologyProperties": { "platformScale": "Enterprise portfolio", "monitoringCapability": "Fully automated with predictive risk scoring" } } }, "prefillFrom": null, "briefSection": "Payment operations", "text": "How many savings groups does your organisation support in total?", "ngoText": "How many savings groups does your organisation support in total?" }, { "id": "member-device-access", "type": "select", "options": [ { "label": "Smartphones", "value": "smartphone" }, { "label": "Feature phones (SMS/USSD)", "value": "feature-phone" }, { "label": "Mix: group leader has smartphone, members have feature phones or none", "value": "leader-smartphone" }, { "label": "Minimal devices: need agent/facilitator support", "value": "minimal" } ], "propertyMapping": { "smartphone": { "technologies": [ "Mobile savings group app" ], "technologyProperties": { "memberInterface": "Mobile app per member", "recordKeeping": "Individual digital records" } }, "feature-phone": { "technologies": [ "USSD-based savings group interface" ], "technologyProperties": { "memberInterface": "USSD menu", "recordKeeping": "USSD-entered + server-stored" } }, "leader-smartphone": { "technologies": [ "Leader app + member USSD", "Leader-facilitated recording" ], "technologyProperties": { "memberInterface": "Leader records on behalf of group", "recordKeeping": "Leader-entered + individual USSD confirmation" } }, "minimal": { "technologies": [ "Facilitator-assisted digital recording", "Agent tablet/kiosk" ], "technologyProperties": { "memberInterface": "Facilitator/agent-entered", "recordKeeping": "Centralised with meeting-based data entry" } } }, "prefillFrom": null, "briefSection": "End-user interface", "text": "What devices do savings group members typically have?", "ngoText": "What devices do savings group members typically have?" }, { "id": "current-recordkeeping", "type": "select", "options": [ { "label": "Paper ledger books", "value": "paper" }, { "label": "Basic mobile app (non-digital ledger)", "value": "mobile-app" }, { "label": "Spreadsheets", "value": "spreadsheet" }, { "label": "Memory-based (no formal records)", "value": "memory" }, { "label": "Mix of methods", "value": "mixed" } ], "propertyMapping": { "paper": { "technologies": [ "Digital ledger replacement", "Immutable record platform" ], "technologyProperties": { "currentSystem": "Paper-based", "migrationComplexity": "Medium \u2014 digitisation training needed", "dataIntegrity": "Major improvement \u2014 eliminates manipulation risk" } }, "mobile-app": { "technologies": [ "Blockchain-anchored record layer" ], "technologyProperties": { "currentSystem": "Existing mobile app", "migrationComplexity": "Low \u2014 upgrade existing digital flow", "dataIntegrity": "Enhancement \u2014 adds immutability" } }, "spreadsheet": { "technologies": [ "Digital ledger replacement" ], "technologyProperties": { "currentSystem": "Spreadsheet-based", "migrationComplexity": "Low-medium", "dataIntegrity": "Major improvement" } }, "memory": { "technologies": [ "Digital ledger introduction", "Training programme" ], "technologyProperties": { "currentSystem": "No formal records", "migrationComplexity": "High \u2014 behaviour change required", "dataIntegrity": "Transformative" } }, "mixed": { "technologies": [ "Unified digital ledger platform" ], "technologyProperties": { "currentSystem": "Mixed methods", "migrationComplexity": "Medium \u2014 standardisation needed", "dataIntegrity": "Significant improvement" } } }, "prefillFrom": null, "briefSection": "Current state", "text": "How are savings group records currently kept?", "ngoText": "How are savings group records currently kept?" }, { "id": "sq-UC-A-020-001", "type": "single-select", "options": [ { "value": "group-vote-on-chain", "label": "Group vote digital" }, { "value": "chairperson-approval", "label": "Chairperson approval" }, { "value": "multi-sig", "label": "multi-approval requirement" }, { "value": "paper-then-digitise", "label": "Paper then digitise" }, { "value": "consensus-based", "label": "Consensus-based" } ], "propertyMapping": { "group-vote-on-chain": { "technologies": [ "voting-contract", "on-chain-voting" ], "technologyProperties": {} }, "chairperson-approval": { "technologies": [ "approval-workflow", "authority-control" ], "technologyProperties": {} }, "multi-sig": { "technologies": [ "multi-sig-wallet", "multi-party-approval" ], "technologyProperties": {} }, "paper-then-digitise": { "technologies": [ "paper-recording", "manual-digitization" ], "technologyProperties": {} }, "consensus-based": { "technologies": [ "consensus-protocol", "agreement-tracking" ], "technologyProperties": {} } }, "briefSection": "requirements", "text": "How are savings group governance decisions recorded today?", "ngoText": "How are savings group governance decisions recorded today?" }, { "id": "beneficiary-choice", "label": "How will beneficiaries exercise choice in how they receive and use this service?", "type": "select", "briefSection": "End-user interface", "options": [ { "label": "Beneficiaries choose between delivery methods (cash, voucher, mobile money, direct)", "value": "delivery-choice" }, { "label": "Beneficiaries choose preferred merchants or service points", "value": "merchant-choice" }, { "label": "Beneficiaries control their own data sharing preferences", "value": "data-choice" }, { "label": "Multiple choice dimensions (delivery + merchant + data)", "value": "full-choice" }, { "label": "Limited choice: programme constraints determine delivery", "value": "limited" } ], "propertyMapping": { "delivery-choice": { "technologies": [], "technologyProperties": { "beneficiaryChoice": "Delivery method choice", "dignityDesign": "Beneficiaries select preferred receipt method" } }, "merchant-choice": { "technologies": [], "technologyProperties": { "beneficiaryChoice": "Merchant/service point choice", "dignityDesign": "Beneficiaries select where to redeem" } }, "data-choice": { "technologies": [], "technologyProperties": { "beneficiaryChoice": "Data sharing choice", "dignityDesign": "Beneficiaries control personal data sharing" } }, "full-choice": { "technologies": [], "technologyProperties": { "beneficiaryChoice": "Multi-dimensional choice", "dignityDesign": "Full beneficiary agency across delivery, merchant, and data" } }, "limited": { "technologies": [], "technologyProperties": { "beneficiaryChoice": "Limited by programme design", "dignityDesign": "Programme constraints; beneficiary informed of reasons" } } }, "text": "How will beneficiaries exercise choice in how they receive and use this service?" } ], "complexityFactors": { "relationships": 3, "operationalChange": 3, "dataCompliance": 2 }, "suggestedCriteria": [ { "id": "SC-GROUP-MGMT", "name": "Group Governance & Management", "description": "The provider supports savings group governance (member management, share tracking, meeting records, and rule enforcement). Savings groups have constitutions with specific rules about contributions, borrowing, and payouts.", "weight": 0.3, "ratingGuide": { "5": "Full group lifecycle: formation, constitution, member roles, meeting scheduling, attendance, rule enforcement. Share purchase tracking. Payout calculations. Annual share-out management.", "4": "Good group management. Member tracking, share purchases, meeting records. Annual share-out.", "3": "Member list and share tracking. Meeting recording. Manual rule enforcement.", "2": "Basic member list and contribution tracking. No governance features.", "1": "No group management. Individual account tracking only." } }, { "id": "SC-FIELD-USABLE", "name": "Field-Level Usability", "description": "Group members and facilitators can use the system in the field. Savings groups meet under trees, in community halls, often without electricity. The tool must work in these conditions.", "weight": 0.25, "ratingGuide": { "5": "Works on basic feature phones via USSD/SMS. Offline-capable with sync. Solar-friendly (low battery usage). Available in 5+ local languages. Audio/visual guides for low-literacy users.", "4": "Basic smartphone app that works offline. 2-3 local languages. Low battery usage.", "3": "Smartphone app requiring periodic connectivity. English plus one language. Standard battery usage.", "2": "Smartphone app requiring consistent internet. English only.", "1": "Desktop/laptop required. Internet-dependent. Not usable in field settings." } }, { "id": "SC-RECORD-INTEGRITY", "name": "Record Integrity & Dispute Prevention", "description": "Savings records are tamper-evident. Disputes about who contributed what are the primary cause of savings group failure. The system must prevent record manipulation and provide clear evidence.", "weight": 0.2, "ratingGuide": { "5": "Blockchain-anchored records per transaction. Each member can verify their own records. Group consensus on changes. Cryptographic integrity. Facilitator cannot unilaterally alter records.", "4": "Tamper-evident records. Member verification available. Good change tracking.", "3": "Access-controlled records. Change log. Standard integrity measures.", "2": "Basic digital records. Administrator can modify. Limited change tracking.", "1": "Editable records with no audit trail. Same dispute risk as paper-based." } }, { "id": "SC-LOAN-SOCIAL", "name": "Internal Lending & Social Fund Management", "description": "The provider handles the lending and social fund components of savings groups. Most groups lend to members from the savings pool and maintain a separate social/emergency fund.", "weight": 0.15, "ratingGuide": { "5": "Internal loan tracking with configurable interest. Social fund contributions and disbursements. Outstanding loan dashboard. Repayment scheduling and reminders.", "4": "Good loan and social fund tracking. Interest calculation. Basic repayment tracking.", "3": "Loan recording. Interest calculation. Social fund as a separate balance.", "2": "Basic loan recording. Manual interest calculation. No social fund feature.", "1": "No internal lending capability. Savings tracking only." } }, { "id": "SC-PROGRAMME-OVERSIGHT", "name": "Programme-Level Oversight", "description": "The facilitating NGO can see aggregate data across multiple savings groups. Programme managers need portfolio views: how many groups, total savings, default rates, growth trends.", "weight": 0.1, "ratingGuide": { "5": "Portfolio dashboard across all groups. Aggregate savings, lending, and default metrics. Group performance comparison. Trend analysis. Exportable for donor reporting.", "4": "Good portfolio view. Key aggregate metrics. Group comparison. Standard exports.", "3": "Per-group views with manual aggregation. Basic summary statistics.", "2": "Individual group data only. Manual compilation for programme view.", "1": "No programme-level oversight. Each group managed independently." } } ], "procurement": { "marketMaturity": "nascent", "primaryMode": "integrator-led", "alternativeModes": [ "conversation-guide" ], "reasoning": "Savings group digital records are emerging; small-scale or bespoke implementations common.", "exampleProductCategories": [ "village-savings-app", "community-finance-platform" ], "partnerChannels": [], "lastReviewed": "2026-05-01" } }, { "id": "UC-A-021", "name": "Forecast-based financing (anticipatory action)", "category": "A", "subcategory": "Emergency Response", "description": "Release funds automatically when a forecast passes an agreed warning level, so help reaches people before a flood or drought hits.", "bCriteria": [ "B5", "B7" ], "requiredComponents": [ { "component": "smart-contracts", "description": "Forecast-triggered payments" }, { "component": "payment-rails", "description": "Settlement network" }, { "component": "stablecoin", "description": "Payment currency" }, { "component": "oracle-data", "description": "Weather/disaster forecast data" } ], "conditionalComponents": [ { "component": "identity-verification", "condition": "For beneficiary KYC", "linksTo": "UC-B-024" } ], "crossCategoryDependencies": [ "UC-E-069 if community targeting used" ], "p2TriggerConditions": { "description": "Activated when P2 shows disaster/climate risk focus + forecast-based models + anticipatory approach", "rangeSignals": [ "disasterRisk >= high", "forecastCapacity >= true", "anticipatoryApproach >= true" ] }, "contextFieldsTemplate": [ { "field": "hazardTypes", "source": "P0 risk context", "description": "Types of disasters" }, { "field": "leadTime", "source": "P2 forecast windows", "description": "Time before impact" }, { "field": "beneficiaries", "source": "P2 programme scale", "description": "Number of beneficiaries" }, { "field": "paymentTrigger", "source": "P2 forecast thresholds", "description": "Trigger thresholds" }, { "field": "verificationMethod", "source": "P2 verification approach", "description": "How triggers are verified" } ], "implementationComplexity": "high", "examples": { "note": "WFP anticipatory action, forecast-based financing pilots", "references": [ { "name": "Start Network", "url": "https://startnetwork.org/blockchain", "solved": "Accelerated emergency funding payouts with enhanced transparency" }, { "name": "WFP Building Blocks", "url": "https://www.wfp.org/building-blocks", "solved": "Transferred cash to refugee populations at scale, fast and at low cost" } ] }, "solutionQuestions": [ { "id": "corridor-count", "type": "select", "options": [ { "label": "Single country", "value": "single" }, { "label": "2\u20133 countries", "value": "2-3" }, { "label": "4\u20135 countries", "value": "4-5" }, { "label": "More than 5 countries", "value": "5-plus" } ], "propertyMapping": { "single": { "technologies": [ "Single-corridor fiat on-ramp" ], "technologyProperties": { "corridorComplexity": "Single origination country", "multiRailNeeded": "No" } }, "2-3": { "technologies": [ "Multi-corridor fiat on-ramp gateway" ], "technologyProperties": { "corridorComplexity": "2\u20133 origination countries", "multiRailNeeded": "Yes \u2014 2-3 payment rails" } }, "4-5": { "technologies": [ "Multi-corridor fiat on-ramp gateway" ], "technologyProperties": { "corridorComplexity": "4\u20135 origination countries", "multiRailNeeded": "Yes \u2014 4-5 payment rails" } }, "5-plus": { "technologies": [ "Enterprise multi-corridor on-ramp gateway" ], "technologyProperties": { "corridorComplexity": "5+ origination countries", "multiRailNeeded": "Yes \u2014 enterprise-grade multi-rail" } } }, "prefillFrom": null, "briefSection": "Payment rail requirements", "text": "How many countries does your organisation send transfer funds from?", "ngoText": "How many countries does your organisation send transfer funds from?" }, { "id": "origination-country-1", "type": "select", "options": [ { "label": "United States", "value": "united-states" }, { "label": "United Kingdom", "value": "united-kingdom" }, { "label": "Germany", "value": "germany" }, { "label": "Netherlands", "value": "netherlands" }, { "label": "Switzerland", "value": "switzerland" }, { "label": "Belgium", "value": "belgium" }, { "label": "France", "value": "france" }, { "label": "Sweden", "value": "sweden" }, { "label": "Norway", "value": "norway" }, { "label": "Denmark", "value": "denmark" }, { "label": "Canada", "value": "canada" }, { "label": "Australia", "value": "australia" }, { "label": "Japan", "value": "japan" }, { "label": "Ireland", "value": "ireland" }, { "label": "Italy", "value": "italy" }, { "label": "Spain", "value": "spain" }, { "label": "Austria", "value": "austria" }, { "label": "Finland", "value": "finland" }, { "label": "Luxembourg", "value": "luxembourg" }, { "label": "South Korea", "value": "south-korea" }, { "label": "New Zealand", "value": "new-zealand" }, { "label": "United Arab Emirates", "value": "united-arab-emirates" }, { "label": "Singapore", "value": "singapore" }, { "label": "Other", "value": "other" } ], "propertyMapping": { "united-states": { "technologies": [ "ACH/wire fiat on-ramp" ], "technologyProperties": { "onRampType": "ACH/Fedwire bank transfer", "onRampRegion": "United States", "settlementRail": "ACH / Fedwire" } }, "united-kingdom": { "technologies": [ "UK Faster Payments on-ramp" ], "technologyProperties": { "onRampType": "Faster Payments bank transfer", "onRampRegion": "United Kingdom", "settlementRail": "FPS / BACS" } }, "germany": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "netherlands": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "switzerland": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SIC/SEPA bank transfer", "onRampRegion": "Switzerland/EU", "settlementRail": "SIC / SEPA Credit Transfer" } }, "belgium": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "france": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "sweden": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "norway": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA-adjacent bank transfer", "onRampRegion": "EEA", "settlementRail": "SEPA Credit Transfer" } }, "denmark": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "canada": { "technologies": [ "Canadian EFT on-ramp" ], "technologyProperties": { "onRampType": "Interac/EFT bank transfer", "onRampRegion": "Canada", "settlementRail": "Interac / EFT" } }, "australia": { "technologies": [ "Australian NPP on-ramp" ], "technologyProperties": { "onRampType": "NPP bank transfer", "onRampRegion": "Australia", "settlementRail": "NPP / BECS" } }, "japan": { "technologies": [ "Japanese Zengin on-ramp" ], "technologyProperties": { "onRampType": "Zengin bank transfer", "onRampRegion": "Japan", "settlementRail": "Zengin System" } }, "ireland": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "italy": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "spain": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "austria": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "finland": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "luxembourg": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "south-korea": { "technologies": [ "Korean banking on-ramp" ], "technologyProperties": { "onRampType": "KFTC bank transfer", "onRampRegion": "South Korea", "settlementRail": "KFTC / BOK-Wire" } }, "new-zealand": { "technologies": [ "NZ banking on-ramp" ], "technologyProperties": { "onRampType": "SBI bank transfer", "onRampRegion": "New Zealand", "settlementRail": "SBI / ESAS" } }, "united-arab-emirates": { "technologies": [ "UAE banking on-ramp" ], "technologyProperties": { "onRampType": "UAEFTS bank transfer", "onRampRegion": "United Arab Emirates", "settlementRail": "UAEFTS / IPP" } }, "singapore": { "technologies": [ "Singapore FAST on-ramp" ], "technologyProperties": { "onRampType": "FAST bank transfer", "onRampRegion": "Singapore", "settlementRail": "FAST / MEPS+" } }, "other": { "technologies": [ "Regional fiat on-ramp" ], "technologyProperties": { "onRampType": "Local rail bank transfer", "onRampRegion": "Region-specific", "settlementRail": "Local payment network" } } }, "showIf": { "questionId": "corridor-count", "minValue": "single" }, "prefillFrom": null, "briefSection": "Payment rail requirements", "text": "Which country do you most frequently initiate transfers from?", "ngoText": "Which country do you most frequently initiate transfers from?" }, { "id": "origination-country-2", "type": "select", "options": [ { "label": "United States", "value": "united-states" }, { "label": "United Kingdom", "value": "united-kingdom" }, { "label": "Germany", "value": "germany" }, { "label": "Netherlands", "value": "netherlands" }, { "label": "Switzerland", "value": "switzerland" }, { "label": "Belgium", "value": "belgium" }, { "label": "France", "value": "france" }, { "label": "Sweden", "value": "sweden" }, { "label": "Norway", "value": "norway" }, { "label": "Denmark", "value": "denmark" }, { "label": "Canada", "value": "canada" }, { "label": "Australia", "value": "australia" }, { "label": "Japan", "value": "japan" }, { "label": "Ireland", "value": "ireland" }, { "label": "Italy", "value": "italy" }, { "label": "Spain", "value": "spain" }, { "label": "Austria", "value": "austria" }, { "label": "Finland", "value": "finland" }, { "label": "Luxembourg", "value": "luxembourg" }, { "label": "South Korea", "value": "south-korea" }, { "label": "New Zealand", "value": "new-zealand" }, { "label": "United Arab Emirates", "value": "united-arab-emirates" }, { "label": "Singapore", "value": "singapore" }, { "label": "Other", "value": "other" } ], "propertyMapping": { "united-states": { "technologies": [ "ACH/wire fiat on-ramp" ], "technologyProperties": { "onRampType": "ACH/Fedwire bank transfer", "onRampRegion": "United States", "settlementRail": "ACH / Fedwire" } }, "united-kingdom": { "technologies": [ "UK Faster Payments on-ramp" ], "technologyProperties": { "onRampType": "Faster Payments bank transfer", "onRampRegion": "United Kingdom", "settlementRail": "FPS / BACS" } }, "germany": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "netherlands": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "switzerland": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SIC/SEPA bank transfer", "onRampRegion": "Switzerland/EU", "settlementRail": "SIC / SEPA Credit Transfer" } }, "belgium": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "france": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "sweden": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "norway": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA-adjacent bank transfer", "onRampRegion": "EEA", "settlementRail": "SEPA Credit Transfer" } }, "denmark": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "canada": { "technologies": [ "Canadian EFT on-ramp" ], "technologyProperties": { "onRampType": "Interac/EFT bank transfer", "onRampRegion": "Canada", "settlementRail": "Interac / EFT" } }, "australia": { "technologies": [ "Australian NPP on-ramp" ], "technologyProperties": { "onRampType": "NPP bank transfer", "onRampRegion": "Australia", "settlementRail": "NPP / BECS" } }, "japan": { "technologies": [ "Japanese Zengin on-ramp" ], "technologyProperties": { "onRampType": "Zengin bank transfer", "onRampRegion": "Japan", "settlementRail": "Zengin System" } }, "ireland": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "italy": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "spain": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "austria": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "finland": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "luxembourg": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "south-korea": { "technologies": [ "Korean banking on-ramp" ], "technologyProperties": { "onRampType": "KFTC bank transfer", "onRampRegion": "South Korea", "settlementRail": "KFTC / BOK-Wire" } }, "new-zealand": { "technologies": [ "NZ banking on-ramp" ], "technologyProperties": { "onRampType": "SBI bank transfer", "onRampRegion": "New Zealand", "settlementRail": "SBI / ESAS" } }, "united-arab-emirates": { "technologies": [ "UAE banking on-ramp" ], "technologyProperties": { "onRampType": "UAEFTS bank transfer", "onRampRegion": "United Arab Emirates", "settlementRail": "UAEFTS / IPP" } }, "singapore": { "technologies": [ "Singapore FAST on-ramp" ], "technologyProperties": { "onRampType": "FAST bank transfer", "onRampRegion": "Singapore", "settlementRail": "FAST / MEPS+" } }, "other": { "technologies": [ "Regional fiat on-ramp" ], "technologyProperties": { "onRampType": "Local rail bank transfer", "onRampRegion": "Region-specific", "settlementRail": "Local payment network" } } }, "showIf": { "questionId": "corridor-count", "minValue": "2-3" }, "prefillFrom": null, "briefSection": "Payment rail requirements", "text": "Second most common transfer origination country (if applicable)", "ngoText": "Second most common transfer origination country (if applicable)" }, { "id": "origination-country-3", "type": "select", "options": [ { "label": "United States", "value": "united-states" }, { "label": "United Kingdom", "value": "united-kingdom" }, { "label": "Germany", "value": "germany" }, { "label": "Netherlands", "value": "netherlands" }, { "label": "Switzerland", "value": "switzerland" }, { "label": "Belgium", "value": "belgium" }, { "label": "France", "value": "france" }, { "label": "Sweden", "value": "sweden" }, { "label": "Norway", "value": "norway" }, { "label": "Denmark", "value": "denmark" }, { "label": "Canada", "value": "canada" }, { "label": "Australia", "value": "australia" }, { "label": "Japan", "value": "japan" }, { "label": "Ireland", "value": "ireland" }, { "label": "Italy", "value": "italy" }, { "label": "Spain", "value": "spain" }, { "label": "Austria", "value": "austria" }, { "label": "Finland", "value": "finland" }, { "label": "Luxembourg", "value": "luxembourg" }, { "label": "South Korea", "value": "south-korea" }, { "label": "New Zealand", "value": "new-zealand" }, { "label": "United Arab Emirates", "value": "united-arab-emirates" }, { "label": "Singapore", "value": "singapore" }, { "label": "Other", "value": "other" } ], "propertyMapping": { "united-states": { "technologies": [ "ACH/wire fiat on-ramp" ], "technologyProperties": { "onRampType": "ACH/Fedwire bank transfer", "onRampRegion": "United States", "settlementRail": "ACH / Fedwire" } }, "united-kingdom": { "technologies": [ "UK Faster Payments on-ramp" ], "technologyProperties": { "onRampType": "Faster Payments bank transfer", "onRampRegion": "United Kingdom", "settlementRail": "FPS / BACS" } }, "germany": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "netherlands": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "switzerland": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SIC/SEPA bank transfer", "onRampRegion": "Switzerland/EU", "settlementRail": "SIC / SEPA Credit Transfer" } }, "belgium": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "france": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "sweden": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "norway": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA-adjacent bank transfer", "onRampRegion": "EEA", "settlementRail": "SEPA Credit Transfer" } }, "denmark": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "canada": { "technologies": [ "Canadian EFT on-ramp" ], "technologyProperties": { "onRampType": "Interac/EFT bank transfer", "onRampRegion": "Canada", "settlementRail": "Interac / EFT" } }, "australia": { "technologies": [ "Australian NPP on-ramp" ], "technologyProperties": { "onRampType": "NPP bank transfer", "onRampRegion": "Australia", "settlementRail": "NPP / BECS" } }, "japan": { "technologies": [ "Japanese Zengin on-ramp" ], "technologyProperties": { "onRampType": "Zengin bank transfer", "onRampRegion": "Japan", "settlementRail": "Zengin System" } }, "ireland": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "italy": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "spain": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "austria": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "finland": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "luxembourg": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "south-korea": { "technologies": [ "Korean banking on-ramp" ], "technologyProperties": { "onRampType": "KFTC bank transfer", "onRampRegion": "South Korea", "settlementRail": "KFTC / BOK-Wire" } }, "new-zealand": { "technologies": [ "NZ banking on-ramp" ], "technologyProperties": { "onRampType": "SBI bank transfer", "onRampRegion": "New Zealand", "settlementRail": "SBI / ESAS" } }, "united-arab-emirates": { "technologies": [ "UAE banking on-ramp" ], "technologyProperties": { "onRampType": "UAEFTS bank transfer", "onRampRegion": "United Arab Emirates", "settlementRail": "UAEFTS / IPP" } }, "singapore": { "technologies": [ "Singapore FAST on-ramp" ], "technologyProperties": { "onRampType": "FAST bank transfer", "onRampRegion": "Singapore", "settlementRail": "FAST / MEPS+" } }, "other": { "technologies": [ "Regional fiat on-ramp" ], "technologyProperties": { "onRampType": "Local rail bank transfer", "onRampRegion": "Region-specific", "settlementRail": "Local payment network" } } }, "showIf": { "questionId": "corridor-count", "minValue": "2-3" }, "prefillFrom": null, "briefSection": "Payment rail requirements", "text": "Third transfer origination country (if applicable)", "ngoText": "Third transfer origination country (if applicable)" }, { "id": "origination-country-4", "type": "select", "options": [ { "label": "United States", "value": "united-states" }, { "label": "United Kingdom", "value": "united-kingdom" }, { "label": "Germany", "value": "germany" }, { "label": "Netherlands", "value": "netherlands" }, { "label": "Switzerland", "value": "switzerland" }, { "label": "Belgium", "value": "belgium" }, { "label": "France", "value": "france" }, { "label": "Sweden", "value": "sweden" }, { "label": "Norway", "value": "norway" }, { "label": "Denmark", "value": "denmark" }, { "label": "Canada", "value": "canada" }, { "label": "Australia", "value": "australia" }, { "label": "Japan", "value": "japan" }, { "label": "Ireland", "value": "ireland" }, { "label": "Italy", "value": "italy" }, { "label": "Spain", "value": "spain" }, { "label": "Austria", "value": "austria" }, { "label": "Finland", "value": "finland" }, { "label": "Luxembourg", "value": "luxembourg" }, { "label": "South Korea", "value": "south-korea" }, { "label": "New Zealand", "value": "new-zealand" }, { "label": "United Arab Emirates", "value": "united-arab-emirates" }, { "label": "Singapore", "value": "singapore" }, { "label": "Other", "value": "other" } ], "propertyMapping": { "united-states": { "technologies": [ "ACH/wire fiat on-ramp" ], "technologyProperties": { "onRampType": "ACH/Fedwire bank transfer", "onRampRegion": "United States", "settlementRail": "ACH / Fedwire" } }, "united-kingdom": { "technologies": [ "UK Faster Payments on-ramp" ], "technologyProperties": { "onRampType": "Faster Payments bank transfer", "onRampRegion": "United Kingdom", "settlementRail": "FPS / BACS" } }, "germany": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "netherlands": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "switzerland": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SIC/SEPA bank transfer", "onRampRegion": "Switzerland/EU", "settlementRail": "SIC / SEPA Credit Transfer" } }, "belgium": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "france": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "sweden": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "norway": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA-adjacent bank transfer", "onRampRegion": "EEA", "settlementRail": "SEPA Credit Transfer" } }, "denmark": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "canada": { "technologies": [ "Canadian EFT on-ramp" ], "technologyProperties": { "onRampType": "Interac/EFT bank transfer", "onRampRegion": "Canada", "settlementRail": "Interac / EFT" } }, "australia": { "technologies": [ "Australian NPP on-ramp" ], "technologyProperties": { "onRampType": "NPP bank transfer", "onRampRegion": "Australia", "settlementRail": "NPP / BECS" } }, "japan": { "technologies": [ "Japanese Zengin on-ramp" ], "technologyProperties": { "onRampType": "Zengin bank transfer", "onRampRegion": "Japan", "settlementRail": "Zengin System" } }, "ireland": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "italy": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "spain": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "austria": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "finland": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "luxembourg": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "south-korea": { "technologies": [ "Korean banking on-ramp" ], "technologyProperties": { "onRampType": "KFTC bank transfer", "onRampRegion": "South Korea", "settlementRail": "KFTC / BOK-Wire" } }, "new-zealand": { "technologies": [ "NZ banking on-ramp" ], "technologyProperties": { "onRampType": "SBI bank transfer", "onRampRegion": "New Zealand", "settlementRail": "SBI / ESAS" } }, "united-arab-emirates": { "technologies": [ "UAE banking on-ramp" ], "technologyProperties": { "onRampType": "UAEFTS bank transfer", "onRampRegion": "United Arab Emirates", "settlementRail": "UAEFTS / IPP" } }, "singapore": { "technologies": [ "Singapore FAST on-ramp" ], "technologyProperties": { "onRampType": "FAST bank transfer", "onRampRegion": "Singapore", "settlementRail": "FAST / MEPS+" } }, "other": { "technologies": [ "Regional fiat on-ramp" ], "technologyProperties": { "onRampType": "Local rail bank transfer", "onRampRegion": "Region-specific", "settlementRail": "Local payment network" } } }, "showIf": { "questionId": "corridor-count", "minValue": "4-5" }, "prefillFrom": null, "briefSection": "Payment rail requirements", "text": "Fourth transfer origination country (if applicable)", "ngoText": "Fourth transfer origination country (if applicable)" }, { "id": "origination-country-5", "type": "select", "options": [ { "label": "United States", "value": "united-states" }, { "label": "United Kingdom", "value": "united-kingdom" }, { "label": "Germany", "value": "germany" }, { "label": "Netherlands", "value": "netherlands" }, { "label": "Switzerland", "value": "switzerland" }, { "label": "Belgium", "value": "belgium" }, { "label": "France", "value": "france" }, { "label": "Sweden", "value": "sweden" }, { "label": "Norway", "value": "norway" }, { "label": "Denmark", "value": "denmark" }, { "label": "Canada", "value": "canada" }, { "label": "Australia", "value": "australia" }, { "label": "Japan", "value": "japan" }, { "label": "Ireland", "value": "ireland" }, { "label": "Italy", "value": "italy" }, { "label": "Spain", "value": "spain" }, { "label": "Austria", "value": "austria" }, { "label": "Finland", "value": "finland" }, { "label": "Luxembourg", "value": "luxembourg" }, { "label": "South Korea", "value": "south-korea" }, { "label": "New Zealand", "value": "new-zealand" }, { "label": "United Arab Emirates", "value": "united-arab-emirates" }, { "label": "Singapore", "value": "singapore" }, { "label": "Other", "value": "other" } ], "propertyMapping": { "united-states": { "technologies": [ "ACH/wire fiat on-ramp" ], "technologyProperties": { "onRampType": "ACH/Fedwire bank transfer", "onRampRegion": "United States", "settlementRail": "ACH / Fedwire" } }, "united-kingdom": { "technologies": [ "UK Faster Payments on-ramp" ], "technologyProperties": { "onRampType": "Faster Payments bank transfer", "onRampRegion": "United Kingdom", "settlementRail": "FPS / BACS" } }, "germany": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "netherlands": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "switzerland": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SIC/SEPA bank transfer", "onRampRegion": "Switzerland/EU", "settlementRail": "SIC / SEPA Credit Transfer" } }, "belgium": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "france": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "sweden": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "norway": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA-adjacent bank transfer", "onRampRegion": "EEA", "settlementRail": "SEPA Credit Transfer" } }, "denmark": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "canada": { "technologies": [ "Canadian EFT on-ramp" ], "technologyProperties": { "onRampType": "Interac/EFT bank transfer", "onRampRegion": "Canada", "settlementRail": "Interac / EFT" } }, "australia": { "technologies": [ "Australian NPP on-ramp" ], "technologyProperties": { "onRampType": "NPP bank transfer", "onRampRegion": "Australia", "settlementRail": "NPP / BECS" } }, "japan": { "technologies": [ "Japanese Zengin on-ramp" ], "technologyProperties": { "onRampType": "Zengin bank transfer", "onRampRegion": "Japan", "settlementRail": "Zengin System" } }, "ireland": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "italy": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "spain": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "austria": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "finland": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "luxembourg": { "technologies": [ "SEPA-integrated fiat on-ramp" ], "technologyProperties": { "onRampType": "SEPA bank transfer", "onRampRegion": "EU/EEA", "settlementRail": "SEPA Credit Transfer" } }, "south-korea": { "technologies": [ "Korean banking on-ramp" ], "technologyProperties": { "onRampType": "KFTC bank transfer", "onRampRegion": "South Korea", "settlementRail": "KFTC / BOK-Wire" } }, "new-zealand": { "technologies": [ "NZ banking on-ramp" ], "technologyProperties": { "onRampType": "SBI bank transfer", "onRampRegion": "New Zealand", "settlementRail": "SBI / ESAS" } }, "united-arab-emirates": { "technologies": [ "UAE banking on-ramp" ], "technologyProperties": { "onRampType": "UAEFTS bank transfer", "onRampRegion": "United Arab Emirates", "settlementRail": "UAEFTS / IPP" } }, "singapore": { "technologies": [ "Singapore FAST on-ramp" ], "technologyProperties": { "onRampType": "FAST bank transfer", "onRampRegion": "Singapore", "settlementRail": "FAST / MEPS+" } }, "other": { "technologies": [ "Regional fiat on-ramp" ], "technologyProperties": { "onRampType": "Local rail bank transfer", "onRampRegion": "Region-specific", "settlementRail": "Local payment network" } } }, "showIf": { "questionId": "corridor-count", "minValue": "4-5" }, "prefillFrom": null, "briefSection": "Payment rail requirements", "text": "Fifth transfer origination country (if applicable)", "ngoText": "Fifth transfer origination country (if applicable)" }, { "id": "funding-method", "type": "select", "options": [ { "label": "Bank transfer from organisation account", "value": "bank-transfer" }, { "label": "Card payment from organisation", "value": "card-payment" }, { "label": "Direct stablecoin funding (organisation already holds stablecoins)", "value": "direct-stablecoin" }, { "label": "Mixed: bank transfer for most, card for urgent payments", "value": "mixed-methods" } ], "propertyMapping": { "bank-transfer": { "technologies": [ "Bank-integrated fiat on-ramp" ], "technologyProperties": { "fundingSource": "Organisation bank account", "onRampSpeed": "1-2 business days (SEPA/ACH) or same-day (Faster Payments/wire)", "kybRequired": "Yes \u2014 organisation KYB verification" } }, "card-payment": { "technologies": [ "Card payment on-ramp" ], "technologyProperties": { "fundingSource": "Organisation payment card", "onRampSpeed": "Near-instant", "kybRequired": "Yes \u2014 card verification and organisation KYB" } }, "direct-stablecoin": { "technologies": [ "Direct stablecoin treasury funding" ], "technologyProperties": { "fundingSource": "Existing stablecoin holdings", "onRampSpeed": "Immediate (no fiat conversion needed)", "kybRequired": "Wallet verification only" } }, "mixed-methods": { "technologies": [ "Multi-method fiat on-ramp", "Card payment on-ramp" ], "technologyProperties": { "fundingSource": "Bank transfer (primary) + card (urgent)", "onRampSpeed": "Varies by method", "kybRequired": "Yes \u2014 full organisation KYB" } } }, "prefillFrom": null, "briefSection": "Payment rail requirements", "text": "How does your organisation currently fund international transfers or payments?", "ngoText": "How does your organisation currently fund international transfers or payments?" }, { "id": "stablecoin-approach", "type": "select", "options": [ { "label": "A regulated digital dollar", "value": "usd-pegged" }, { "label": "EUR-pegged stablecoin", "value": "eur-pegged" }, { "label": "Multiple stablecoins depending on corridor", "value": "multi-stablecoin" }, { "label": "Not sure, need guidance on stablecoin selection", "value": "guidance-needed" } ], "propertyMapping": { "usd-pegged": { "technologies": [ "USD-pegged stablecoin rail", "Stablecoin settlement layer" ], "technologyProperties": { "stablecoinType": "A regulated digital dollar", "fxConversion": "At on-ramp and off-ramp points" } }, "eur-pegged": { "technologies": [ "EUR-pegged stablecoin rail", "Stablecoin settlement layer" ], "technologyProperties": { "stablecoinType": "EUR-pegged", "fxConversion": "At on-ramp and off-ramp points" } }, "multi-stablecoin": { "technologies": [ "Multi-stablecoin settlement layer", "Automated FX conversion" ], "technologyProperties": { "stablecoinType": "Multiple denominations", "fxConversion": "Digital or at off-ramp" } }, "guidance-needed": { "technologies": [ "Stablecoin settlement layer" ], "technologyProperties": { "stablecoinType": "To be determined during solution design", "fxConversion": "To be determined" } } }, "prefillFrom": null, "briefSection": "Stablecoin and FX", "text": "What stablecoin approach is preferred for this solution?", "ngoText": "What stablecoin approach is preferred for this solution?" }, { "id": "trigger-data-source", "type": "multiselect", "options": [ { "label": "Weather/climate forecasts (drought, flood, cyclone)", "value": "weather" }, { "label": "Food security indicators (IPC/CH classifications)", "value": "food-security" }, { "label": "Epidemiological data (disease outbreak)", "value": "epidemiological" }, { "label": "Conflict/displacement early warnings", "value": "conflict" }, { "label": "Market price data (commodity prices)", "value": "market-prices" }, { "label": "Seismic/volcanic activity", "value": "seismic" } ], "propertyMapping": { "weather": { "technologies": [ "Weather data oracle", "Automated trigger engine" ], "technologyProperties": { "oracleType": "Meteorological data feed", "triggerMechanism": "Threshold-based weather parameter trigger", "dataSource": "National weather services / satellite data" } }, "food-security": { "technologies": [ "Food security data oracle", "Automated trigger engine" ], "technologyProperties": { "oracleType": "Food security classification feed", "triggerMechanism": "IPC phase threshold trigger", "dataSource": "IPC/CH and famine early-warning systems" } }, "epidemiological": { "technologies": [ "Health data oracle", "Automated trigger engine" ], "technologyProperties": { "oracleType": "Epidemiological data feed", "triggerMechanism": "Outbreak threshold trigger", "dataSource": "WHO/national health data" } }, "conflict": { "technologies": [ "Conflict early warning oracle" ], "technologyProperties": { "oracleType": "Conflict indicator feed", "triggerMechanism": "Risk score threshold", "dataSource": "Conflict-event monitoring data" } }, "market-prices": { "technologies": [ "Market price oracle", "Automated trigger engine" ], "technologyProperties": { "oracleType": "Commodity price feed", "triggerMechanism": "Price deviation threshold", "dataSource": "Market data providers" } }, "seismic": { "technologies": [ "Seismic data oracle" ], "technologyProperties": { "oracleType": "Seismic activity feed", "triggerMechanism": "Magnitude/proximity threshold", "dataSource": "USGS/national seismic networks" } } }, "prefillFrom": null, "briefSection": "Payment logic", "text": "What data sources should trigger anticipatory financing?", "ngoText": "What data sources should trigger anticipatory financing?" }, { "id": "pre-positioning", "type": "select", "options": [ { "label": "Pre-funded stablecoin pool earmarked for triggers", "value": "pre-funded" }, { "label": "Rapid mobilisation from treasury on trigger", "value": "rapid-mobilise" }, { "label": "Donor pre-commitment with draw-down on trigger", "value": "donor-commitment" }, { "label": "Insurance-like pool with premium contributions", "value": "insurance-pool" } ], "propertyMapping": { "pre-funded": { "technologies": [ "Pre-funded smart contract escrow", "Trigger-release mechanism" ], "technologyProperties": { "fundingModel": "Pre-positioned stablecoin pool", "releaseSpeed": "Instant on trigger", "capitalEfficiency": "Funds locked until trigger" } }, "rapid-mobilise": { "technologies": [ "Rapid on-ramp", "Treasury release mechanism" ], "technologyProperties": { "fundingModel": "Treasury-backed rapid conversion", "releaseSpeed": "Hours (on-ramp dependent)", "capitalEfficiency": "Funds available for other use until trigger" } }, "donor-commitment": { "technologies": [ "Donor commitment smart contract", "Draw-down mechanism" ], "technologyProperties": { "fundingModel": "Donor committed draw-down", "releaseSpeed": "Per donor agreement terms", "capitalEfficiency": "High \u2014 committed but not deployed" } }, "insurance-pool": { "technologies": [ "Risk pool smart contract", "Premium management" ], "technologyProperties": { "fundingModel": "Contributory risk pool", "releaseSpeed": "Instant from pool", "capitalEfficiency": "Shared risk across contributors" } } }, "prefillFrom": null, "briefSection": "Payment rail requirements", "text": "How are funds currently pre-positioned for anticipatory action?", "ngoText": "How are funds currently pre-positioned for anticipatory action?" }, { "id": "disbursement-target", "type": "select", "options": [ { "label": "Pre-registered beneficiaries in at-risk areas", "value": "pre-registered" }, { "label": "Community organisations/local partners", "value": "community-orgs" }, { "label": "Government disaster agencies", "value": "government" }, { "label": "Field offices for local response", "value": "field-offices" }, { "label": "Mix depending on trigger type", "value": "mixed" } ], "propertyMapping": { "pre-registered": { "technologies": [ "Pre-registered beneficiary wallet network", "Geographic targeting" ], "technologyProperties": { "targetingMechanism": "Pre-enrolled beneficiary list + geographic filter", "walletPreProvisioning": "Required" } }, "community-orgs": { "technologies": [ "Partner wallet network", "Fund allocation rules" ], "technologyProperties": { "targetingMechanism": "Partner organisation routing", "walletPreProvisioning": "Partner wallets pre-configured" } }, "government": { "technologies": [ "Government agency wallet integration" ], "technologyProperties": { "targetingMechanism": "Government channel routing", "walletPreProvisioning": "Institutional wallet setup" } }, "field-offices": { "technologies": [ "Field office wallet network" ], "technologyProperties": { "targetingMechanism": "Internal field office routing", "walletPreProvisioning": "Office wallets pre-funded" } }, "mixed": { "technologies": [ "Multi-channel disbursement router" ], "technologyProperties": { "targetingMechanism": "Trigger-type-based routing rules", "walletPreProvisioning": "All channels pre-configured" } } }, "prefillFrom": null, "briefSection": "Last-mile delivery", "text": "Who receives the anticipatory financing when triggered?", "ngoText": "Who receives the anticipatory financing when triggered?" }, { "id": "sq-UC-A-021-001", "type": "single-select", "options": [ { "value": "accept-as-cost", "label": "Accept as programme cost" }, { "value": "partial-recovery", "label": "Partial recovery" }, { "value": "insurance-backed", "label": "Insurance-backed recovery" }, { "value": "adjust-future-thresholds", "label": "Adjust future thresholds" }, { "value": "community-redistribution", "label": "Community redistribution" } ], "propertyMapping": { "accept-as-cost": { "technologies": [ "cost-absorption", "expense-tracking" ], "technologyProperties": {} }, "partial-recovery": { "technologies": [ "recovery-workflow", "fund-clawback" ], "technologyProperties": {} }, "insurance-backed": { "technologies": [ "insurance-integration", "claim-system" ], "technologyProperties": {} }, "adjust-future-thresholds": { "technologies": [ "threshold-adjustment", "rules-update" ], "technologyProperties": {} }, "community-redistribution": { "technologies": [ "redistribution-workflow", "community-approval" ], "technologyProperties": {} } }, "briefSection": "operations", "text": "How do you currently handle false-trigger events when funds have been released?", "ngoText": "How do you currently handle false-trigger events when funds have been released?" }, { "id": "beneficiary-choice", "label": "How will beneficiaries exercise choice in how they receive and use this service?", "type": "select", "briefSection": "End-user interface", "options": [ { "label": "Beneficiaries choose between delivery methods (cash, voucher, mobile money, direct)", "value": "delivery-choice" }, { "label": "Beneficiaries choose preferred merchants or service points", "value": "merchant-choice" }, { "label": "Beneficiaries control their own data sharing preferences", "value": "data-choice" }, { "label": "Multiple choice dimensions (delivery + merchant + data)", "value": "full-choice" }, { "label": "Limited choice: programme constraints determine delivery", "value": "limited" } ], "propertyMapping": { "delivery-choice": { "technologies": [], "technologyProperties": { "beneficiaryChoice": "Delivery method choice", "dignityDesign": "Beneficiaries select preferred receipt method" } }, "merchant-choice": { "technologies": [], "technologyProperties": { "beneficiaryChoice": "Merchant/service point choice", "dignityDesign": "Beneficiaries select where to redeem" } }, "data-choice": { "technologies": [], "technologyProperties": { "beneficiaryChoice": "Data sharing choice", "dignityDesign": "Beneficiaries control personal data sharing" } }, "full-choice": { "technologies": [], "technologyProperties": { "beneficiaryChoice": "Multi-dimensional choice", "dignityDesign": "Full beneficiary agency across delivery, merchant, and data" } }, "limited": { "technologies": [], "technologyProperties": { "beneficiaryChoice": "Limited by programme design", "dignityDesign": "Programme constraints; beneficiary informed of reasons" } } }, "text": "How will beneficiaries exercise choice in how they receive and use this service?" } ], "complexityFactors": { "relationships": 4, "operationalChange": 3, "dataCompliance": 3 }, "suggestedCriteria": [ { "id": "SC-TRIGGER-MODEL", "name": "Forecast Trigger Model Integration", "description": "The provider can integrate with weather/climate forecast models to automatically trigger pre-positioned fund releases. Anticipatory action requires disbursing BEFORE a disaster based on forecast probability thresholds.", "weight": 0.3, "ratingGuide": { "5": "Direct integration with global flood and weather forecast services and national met services. Configurable probability thresholds. Multi-indicator triggers. Automatic fund activation on trigger.", "4": "Integration with major forecast providers. Configurable triggers. Semi-automatic activation.", "3": "Manual forecast data input. Configurable thresholds. System recommends activation. Human confirms.", "2": "Manual trigger based on external forecast assessment. No forecast system integration.", "1": "No forecast integration. Standard manual disbursement process." } }, { "id": "SC-PRE-POSITION", "name": "Pre-Positioned Fund Management", "description": "The provider can hold pre-positioned funds earmarked for specific forecast triggers. Anticipatory action funds must be ring-fenced and instantly available when triggered, not subject to normal approval delays.", "weight": 0.25, "ratingGuide": { "5": "Dedicated pre-positioned fund pools per forecast window. Instant release on trigger. Automatic return to pool if trigger window passes without activation. Multi-season fund management.", "4": "Pre-positioned funds with trigger release. Good fund management across seasons.", "3": "Earmarked funds with expedited release. Some manual steps on activation.", "2": "Funds available but standard release process. Faster than normal but not instant.", "1": "No pre-positioning capability. Standard fund release timelines." } }, { "id": "SC-RAPID-DISBURSE", "name": "Rapid Mass Disbursement", "description": "This measures how quickly funds can reach beneficiaries once triggered. The value of anticipatory action depends on speed. Money must arrive before the disaster, not after.", "weight": 0.2, "ratingGuide": { "5": "Pre-registered beneficiary lists. Disbursement within hours of trigger. 10,000+ beneficiaries per event. Mobile money, cash, or voucher delivery.", "4": "Disbursement within 24 hours. Good scale capability. Multiple delivery channels.", "3": "Disbursement within 48-72 hours. Moderate scale. Primary channel only.", "2": "1-2 week disbursement. Standard process with priority queuing.", "1": "No rapid disbursement capability. Standard timelines regardless of trigger." } }, { "id": "SC-FALSE-TRIGGER", "name": "False Trigger Management", "description": "This looks at how the provider handles false triggers (forecast indicated disaster but it didn't materialise). Anticipatory action faces the inherent risk of acting on forecasts that don't verify. The system needs clear protocols.", "weight": 0.15, "ratingGuide": { "5": "Automatic tracking of trigger-to-event verification. False trigger reporting for model improvement. Fund recovery/reallocation protocols. Learning loop with forecast providers.", "4": "Good trigger verification tracking. Recovery protocols. Basic reporting.", "3": "Manual trigger verification. Recovery recorded. Standard post-event review.", "2": "Basic record of trigger events. Manual assessment of accuracy.", "1": "No false trigger management. No systematic learning." } }, { "id": "SC-EVIDENCE-AA", "name": "Anticipatory Action Evidence & Reporting", "description": "The provider can generate evidence that anticipatory action was cost-effective compared to emergency response. Donors need proof that pre-disaster spending saved money and protected lives.", "weight": 0.1, "ratingGuide": { "5": "Cost-effectiveness analysis tools. Comparison with historical emergency response costs. Beneficiary impact tracking. Publication-ready evidence reports.", "4": "Good cost comparison tools. Beneficiary tracking. Standard reporting.", "3": "Basic cost tracking. Manual comparison with emergency response. Standard reports.", "2": "Expenditure records only. Manual analysis needed for cost-effectiveness.", "1": "No evidence generation capability. All analysis done externally." } } ], "procurement": { "marketMaturity": "nascent", "primaryMode": "integrator-led", "alternativeModes": [ "consortium" ], "reasoning": "Forecast-based financing is research-stage in many contexts; consortium pilots common.", "exampleProductCategories": [ "anticipatory-action-platform", "parametric-finance-rails" ], "partnerChannels": [], "lastReviewed": "2026-05-01" } }, { "id": "UC-A-022", "name": "Parametric insurance for beneficiaries", "category": "A", "subcategory": "Risk Management", "description": "Pay out insurance to beneficiaries automatically when a measured event, such as low rainfall or a flood level, is reached, with no claims process.", "bCriteria": [ "B5", "B7", "B8" ], "requiredComponents": [ { "component": "smart-contracts", "description": "Parametric payout triggers" }, { "component": "payment-rails", "description": "Insurance payout settlement" }, { "component": "stablecoin", "description": "Payout currency" }, { "component": "oracle-data", "description": "Parametric data feed (weather, etc.)" } ], "conditionalComponents": [ { "component": "identity-verification", "condition": "For beneficiary KYC", "linksTo": "UC-B-024" } ], "crossCategoryDependencies": [], "p2TriggerConditions": { "description": "Activated when P2 shows disaster risk + insurance interest + parametric feasibility", "rangeSignals": [ "disasterRisk >= high", "insuranceInterest >= true", "parametricData >= available" ] }, "contextFieldsTemplate": [ { "field": "beneficiaries", "source": "P2 programme scale", "description": "Number of insured beneficiaries" }, { "field": "parametricTrigger", "source": "P2 insurance design", "description": "What triggers payouts" }, { "field": "payoutAmount", "source": "P2 insurance parameters", "description": "Payout value" }, { "field": "verificationData", "source": "P2 data sources", "description": "Source of trigger data" } ], "implementationComplexity": "medium-high", "examples": { "note": "R4D parametric insurance initiatives, humanitarian insurance pilots", "references": [ { "name": "Etherisc", "url": "https://etherisc.com/", "solved": "Automated parametric insurance payouts for smallholders on weather events" }, { "name": "ACRE Africa", "url": "https://acreafrica.com/reimagining-agriculture-insurance-using-blockchain-technology/", "solved": "Reduced insurance costs and automated claims for smallholder farmers" } ] }, "solutionQuestions": [ { "id": "stablecoin-approach", "type": "select", "options": [ { "label": "A regulated digital dollar", "value": "usd-pegged" }, { "label": "EUR-pegged stablecoin", "value": "eur-pegged" }, { "label": "Multiple stablecoins depending on corridor", "value": "multi-stablecoin" }, { "label": "Not sure, need guidance on stablecoin selection", "value": "guidance-needed" } ], "propertyMapping": { "usd-pegged": { "technologies": [ "USD-pegged stablecoin rail", "Stablecoin settlement layer" ], "technologyProperties": { "stablecoinType": "A regulated digital dollar", "fxConversion": "At on-ramp and off-ramp points" } }, "eur-pegged": { "technologies": [ "EUR-pegged stablecoin rail", "Stablecoin settlement layer" ], "technologyProperties": { "stablecoinType": "EUR-pegged", "fxConversion": "At on-ramp and off-ramp points" } }, "multi-stablecoin": { "technologies": [ "Multi-stablecoin settlement layer", "Automated FX conversion" ], "technologyProperties": { "stablecoinType": "Multiple denominations", "fxConversion": "Digital or at off-ramp" } }, "guidance-needed": { "technologies": [ "Stablecoin settlement layer" ], "technologyProperties": { "stablecoinType": "To be determined during solution design", "fxConversion": "To be determined" } } }, "prefillFrom": null, "briefSection": "Stablecoin and FX", "text": "What stablecoin approach is preferred for this solution?", "ngoText": "What stablecoin approach is preferred for this solution?" }, { "id": "insured-risk", "type": "multiselect", "options": [ { "label": "Drought (rainfall deficit)", "value": "drought" }, { "label": "Flood (excess rainfall/river level)", "value": "flood" }, { "label": "Cyclone/hurricane/typhoon", "value": "cyclone" }, { "label": "Crop failure (yield-based)", "value": "crop-failure" }, { "label": "Livestock mortality", "value": "livestock" }, { "label": "Earthquake", "value": "earthquake" } ], "propertyMapping": { "drought": { "technologies": [ "Rainfall data oracle", "Parametric smart contract" ], "technologyProperties": { "parameterType": "Rainfall deficit measurement", "dataSource": "Weather stations / satellite rainfall estimates", "triggerDefinition": "Rainfall below threshold over defined period" } }, "flood": { "technologies": [ "Flood data oracle", "Parametric smart contract" ], "technologyProperties": { "parameterType": "Rainfall excess or river level", "dataSource": "Hydrological monitoring / satellite", "triggerDefinition": "Rainfall/level above threshold" } }, "cyclone": { "technologies": [ "Storm tracking oracle", "Parametric smart contract" ], "technologyProperties": { "parameterType": "Wind speed / storm category", "dataSource": "Meteorological services", "triggerDefinition": "Storm category/windspeed threshold in defined area" } }, "crop-failure": { "technologies": [ "Vegetation index oracle (NDVI)", "Parametric smart contract" ], "technologyProperties": { "parameterType": "Vegetation index deviation", "dataSource": "Satellite imagery (NDVI)", "triggerDefinition": "NDVI below threshold at key growth stage" } }, "livestock": { "technologies": [ "Forage index oracle", "Mortality data oracle" ], "technologyProperties": { "parameterType": "Forage availability index", "dataSource": "Satellite forage monitoring", "triggerDefinition": "Forage index below threshold" } }, "earthquake": { "technologies": [ "Seismic data oracle", "Parametric smart contract" ], "technologyProperties": { "parameterType": "Earthquake magnitude/intensity", "dataSource": "Seismic monitoring networks", "triggerDefinition": "Magnitude above threshold within radius" } } }, "prefillFrom": null, "briefSection": "Payment logic", "text": "What risk are beneficiaries being insured against?", "ngoText": "What risk are beneficiaries being insured against?" }, { "id": "premium-funding", "type": "select", "options": [ { "label": "Fully subsidised by donor/programme", "value": "fully-subsidised" }, { "label": "Partially subsidised, beneficiary pays a portion", "value": "partially-subsidised" }, { "label": "Fully paid by beneficiaries", "value": "beneficiary-paid" }, { "label": "Government co-funded", "value": "government-cofunded" } ], "propertyMapping": { "fully-subsidised": { "technologies": [ "Premium pool smart contract", "Donor fund allocation" ], "technologyProperties": { "premiumModel": "Fully subsidised from programme funds", "collectionMechanism": "No beneficiary collection needed" } }, "partially-subsidised": { "technologies": [ "Premium collection module", "Subsidy matching smart contract" ], "technologyProperties": { "premiumModel": "Co-payment (beneficiary + subsidy)", "collectionMechanism": "Beneficiary premium collection + subsidy top-up" } }, "beneficiary-paid": { "technologies": [ "Premium collection module", "Mobile payment integration" ], "technologyProperties": { "premiumModel": "Full beneficiary premium", "collectionMechanism": "Mobile money/wallet deduction" } }, "government-cofunded": { "technologies": [ "Multi-party premium smart contract" ], "technologyProperties": { "premiumModel": "Government + programme co-funding", "collectionMechanism": "Multi-source premium pooling" } } }, "prefillFrom": null, "briefSection": "Payment rail requirements", "text": "How are insurance premiums funded?", "ngoText": "How are insurance premiums funded?" }, { "id": "payout-speed", "type": "select", "options": [ { "label": "Within hours of trigger", "value": "hours" }, { "label": "Within 1-3 days", "value": "days" }, { "label": "Within a week", "value": "week" }, { "label": "Within a month", "value": "month" } ], "propertyMapping": { "hours": { "technologies": [ "Pre-funded payout pool", "Automatic disbursement engine" ], "technologyProperties": { "payoutSpeed": "Hours", "liquidityPrePositioning": "Full pre-funding in stablecoin required" } }, "days": { "technologies": [ "Rapid disbursement engine" ], "technologyProperties": { "payoutSpeed": "1-3 days", "liquidityPrePositioning": "Partial pre-funding or rapid conversion" } }, "week": { "technologies": [ "Standard disbursement engine" ], "technologyProperties": { "payoutSpeed": "Within 7 days", "liquidityPrePositioning": "Standard treasury management" } }, "month": { "technologies": [ "Standard disbursement engine" ], "technologyProperties": { "payoutSpeed": "Within 30 days", "liquidityPrePositioning": "Standard" } } }, "prefillFrom": null, "briefSection": "Payment operations", "text": "How quickly should payouts reach beneficiaries after a trigger event?", "ngoText": "How quickly should payouts reach beneficiaries after a trigger event?" }, { "id": "beneficiary-count-insurance", "type": "select", "options": [ { "label": "Under 1,000", "value": "small" }, { "label": "1,000\u201310,000", "value": "medium" }, { "label": "10,000\u2013100,000", "value": "large" }, { "label": "Over 100,000", "value": "very-large" } ], "propertyMapping": { "small": { "technologies": [ "Basic parametric insurance platform" ], "technologyProperties": { "platformScale": "Small pilot", "enrolmentComplexity": "Manual feasible" } }, "medium": { "technologies": [ "Parametric insurance platform", "Batch enrolment" ], "technologyProperties": { "platformScale": "Medium programme", "enrolmentComplexity": "Semi-automated" } }, "large": { "technologies": [ "Enterprise parametric insurance platform", "Automated enrolment", "Mass payout engine" ], "technologyProperties": { "platformScale": "Large programme", "enrolmentComplexity": "Fully automated" } }, "very-large": { "technologies": [ "Enterprise parametric platform", "Mass enrolment", "Distributed payout engine" ], "technologyProperties": { "platformScale": "National-scale", "enrolmentComplexity": "Fully automated with self-service" } } }, "prefillFrom": null, "briefSection": "Payment operations", "text": "How many beneficiaries would be covered by the insurance programme?", "ngoText": "How many beneficiaries would be covered by the insurance programme?" }, { "id": "sq-UC-A-022-001", "type": "single-select", "options": [ { "value": "government-weather-agency", "label": "Government weather agency" }, { "value": "satellite-imagery", "label": "Satellite imagery" }, { "value": "iot-sensors", "label": "IoT sensors" }, { "value": "index-provider", "label": "Index provider" }, { "value": "multi-source-consensus", "label": "Multi-source consensus" } ], "propertyMapping": { "government-weather-agency": { "technologies": [ "weather-api", "government-feed" ], "technologyProperties": {} }, "satellite-imagery": { "technologies": [ "satellite-data", "image-analysis" ], "technologyProperties": {} }, "iot-sensors": { "technologies": [ "iot-network", "sensor-integration" ], "technologyProperties": {} }, "index-provider": { "technologies": [ "index-api", "data-feed" ], "technologyProperties": {} }, "multi-source-consensus": { "technologies": [ "oracle-network", "consensus-mechanism" ], "technologyProperties": {} } }, "briefSection": "requirements", "text": "What oracle data source should determine trigger events?", "ngoText": "What oracle data source should determine trigger events?" }, { "id": "beneficiary-choice", "label": "How will beneficiaries exercise choice in how they receive and use this service?", "type": "select", "briefSection": "End-user interface", "options": [ { "label": "Beneficiaries choose between delivery methods (cash, voucher, mobile money, direct)", "value": "delivery-choice" }, { "label": "Beneficiaries choose preferred merchants or service points", "value": "merchant-choice" }, { "label": "Beneficiaries control their own data sharing preferences", "value": "data-choice" }, { "label": "Multiple choice dimensions (delivery + merchant + data)", "value": "full-choice" }, { "label": "Limited choice: programme constraints determine delivery", "value": "limited" } ], "propertyMapping": { "delivery-choice": { "technologies": [], "technologyProperties": { "beneficiaryChoice": "Delivery method choice", "dignityDesign": "Beneficiaries select preferred receipt method" } }, "merchant-choice": { "technologies": [], "technologyProperties": { "beneficiaryChoice": "Merchant/service point choice", "dignityDesign": "Beneficiaries select where to redeem" } }, "data-choice": { "technologies": [], "technologyProperties": { "beneficiaryChoice": "Data sharing choice", "dignityDesign": "Beneficiaries control personal data sharing" } }, "full-choice": { "technologies": [], "technologyProperties": { "beneficiaryChoice": "Multi-dimensional choice", "dignityDesign": "Full beneficiary agency across delivery, merchant, and data" } }, "limited": { "technologies": [], "technologyProperties": { "beneficiaryChoice": "Limited by programme design", "dignityDesign": "Programme constraints; beneficiary informed of reasons" } } }, "text": "How will beneficiaries exercise choice in how they receive and use this service?" } ], "complexityFactors": { "relationships": 4, "operationalChange": 3, "dataCompliance": 3 }, "suggestedCriteria": [ { "id": "SC-PARAM-CONFIG", "name": "Parametric Trigger Configuration", "description": "The provider can configure parametric triggers for different hazard types. Parametric insurance pays out based on objective measurements (rainfall below X mm, earthquake above Y magnitude), not loss assessment.", "weight": 0.3, "ratingGuide": { "5": "Multi-hazard parametric triggers (drought, flood, cyclone, earthquake). Configurable thresholds per location. Composite indices. Basis risk analysis tools.", "4": "Multiple hazard types. Good threshold configuration. Basic basis risk awareness.", "3": "2-3 hazard types. Standard thresholds. Limited customisation per location.", "2": "Single hazard type. Fixed thresholds. No basis risk analysis.", "1": "No parametric trigger capability. Manual loss assessment model." } }, { "id": "SC-DATA-ORACLE", "name": "Data Source Integration (Oracles)", "description": "This looks at the objective data sources the provider uses to determine trigger events. The reliability of parametric insurance depends entirely on the quality and independence of trigger data.", "weight": 0.25, "ratingGuide": { "5": "Multiple independent data sources (satellite, ground stations, government met services). Data quality validation. Source redundancy. Transparent methodology.", "4": "Good data sources with some redundancy. Transparent methodology. Reliable feeds.", "3": "Single reliable data source per hazard. Documented methodology. Standard feeds.", "2": "Single data source. Limited documentation. Feed reliability concerns.", "1": "No integrated data sources. Manual trigger determination." } }, { "id": "SC-AUTO-PAYOUT", "name": "Automatic Payout Execution", "description": "Payouts are triggered and delivered automatically when the parametric threshold is breached. The whole point of parametric insurance is speed. Eliminate the claims assessment delay.", "weight": 0.2, "ratingGuide": { "5": "Fully automatic payout within 24-48 hours of trigger. No claims process. Pre-registered beneficiary delivery. Multiple channels (mobile money, bank, cash agent).", "4": "Automatic trigger. Payout within 72 hours. Good delivery options.", "3": "Automatic trigger detection. Semi-automatic payout (human confirmation). 1 week delivery.", "2": "Trigger flags for manual review. Payout initiated manually. Standard delivery timeline.", "1": "Manual trigger assessment. Standard insurance claims process. Weeks to pay." } }, { "id": "SC-PREMIUM-MANAGE", "name": "Premium Collection & Management", "description": "The provider can handle premium collection from beneficiaries or premium subsidies from donors/governments. Humanitarian parametric insurance often involves subsidised premiums with complex funding structures.", "weight": 0.15, "ratingGuide": { "5": "Flexible premium models: beneficiary-paid, donor-subsidised, blended. Mobile money collection. Premium instalment plans. Donor contribution tracking.", "4": "Good premium flexibility. Mobile collection. Subsidy tracking.", "3": "Standard premium collection. Basic subsidy recording. Limited instalment options.", "2": "Fixed premium model. Bank collection only. Manual subsidy tracking.", "1": "No premium management. Fully subsidised only with external tracking." } }, { "id": "SC-ACTUARIAL", "name": "Actuarial & Pricing Support", "description": "The provider offers actuarial tools for product design and pricing. Setting parametric insurance parameters and premiums requires historical hazard data analysis and risk modelling.", "weight": 0.1, "ratingGuide": { "5": "Built-in actuarial modelling. Historical hazard frequency analysis. Premium pricing tools. Basis risk quantification. Product design support.", "4": "Good pricing tools. Historical data analysis. Basic actuarial support.", "3": "Historical data access. Manual pricing with guidance. Partnership with actuaries.", "2": "Basic historical data. No pricing tools. External actuarial support required.", "1": "No actuarial capability. All product design and pricing done externally." } } ], "procurement": { "marketMaturity": "nascent", "primaryMode": "integrator-led", "alternativeModes": [ "consortium" ], "reasoning": "Parametric insurance for beneficiaries is emerging; risk pooling often consortium-shaped.", "exampleProductCategories": [ "parametric-insurance-platform", "climate-insurance-rails" ], "partnerChannels": [], "lastReviewed": "2026-05-01" } }, { "id": "UC-A-023", "name": "Community currencies and complementary currency systems", "category": "A", "subcategory": "Financial Inclusion", "description": "Set up a local payment system that keeps spending inside a community, for places where cash is scarce or the local economy is weak.", "bCriteria": [ "B2", "B4", "B8" ], "requiredComponents": [ { "component": "token-engine", "description": "Blockchain-based token creation and management" }, { "component": "community-governance", "description": "Rules engine for token issuance, redemption, and expiry" }, { "component": "merchant-network", "description": "Local merchant onboarding and acceptance infrastructure" }, { "component": "beneficiary-wallet", "description": "Wallet for community members to hold and transact tokens" } ], "conditionalComponents": [ { "component": "off-ramp", "condition": "If tokens are redeemable for fiat currency", "linksTo": "" }, { "component": "identity-verification", "condition": "If KYC required for token holders" } ], "crossCategoryDependencies": [ "UC-B-024 if beneficiary identity verification needed" ], "p2TriggerConditions": { "description": "Activated when P2 identifies cash scarcity, local economic stagnation, aid dependency, circular economy needs, or community resilience goals", "rangeSignals": [ "cashScarcity >= moderate", "localEconomicActivity <= low", "aidDependency >= high", "communityResilience priority" ] }, "contextFieldsTemplate": [ { "field": "communitySize", "source": "P2 answers", "description": "Number of households or individuals in target community" }, { "field": "existingEconomicActivity", "source": "P2 answers", "description": "Current local trade and commerce patterns" }, { "field": "merchantCount", "source": "P2 answers", "description": "Number of local merchants willing to accept tokens" }, { "field": "governanceStructure", "source": "P0 + P2", "description": "Community leadership and decision-making structure" } ], "implementationComplexity": "high", "examples": { "note": "ICRC/Grassroots Economics community inclusion currencies in Kenya (21x multiplier); Red Cross Cameroon scaling", "references": [ { "name": "Grassroots Economics / ICRC Kenya", "url": "https://www.grassrootseconomics.org/", "solved": "Reported a 21x multiplier effect on cash transfers through community inclusion currencies in Nairobi and Mombasa" }, { "name": "Red Cross Cameroon CIC", "url": "https://www.icrc.org/en/document/blockchain-humanitarian-action", "solved": "Scaling community currencies to stimulate local economic activity in displacement settings" }, { "name": "Sarafu Network", "url": "https://www.grassrootseconomics.org/pages/sarafu-network.html", "solved": "Operational community currency network since 2020 in multiple Kenyan communities" } ] }, "solutionQuestions": [ { "id": "community-size", "label": "How large is the target community for the currency?", "type": "select", "briefSection": "token-design", "options": [ { "label": "Small (under 500 households)", "value": "small" }, { "label": "Medium (500\u20132,000 households)", "value": "medium" }, { "label": "Large (2,000\u201310,000 households)", "value": "large" }, { "label": "Very large (10,000+ households)", "value": "very-large" } ], "propertyMapping": { "small": { "technologies": [ "Simple token ledger" ], "technologyProperties": { "communityScale": "Under 500 households", "tokenComplexity": "Low" } }, "medium": { "technologies": [ "Scalable token platform" ], "technologyProperties": { "communityScale": "500\u20132,000 households", "tokenComplexity": "Medium" } }, "large": { "technologies": [ "Enterprise token platform with merchant integration" ], "technologyProperties": { "communityScale": "2,000\u201310,000 households", "tokenComplexity": "High" } }, "very-large": { "technologies": [ "Multi-community token infrastructure" ], "technologyProperties": { "communityScale": "10,000+ households", "tokenComplexity": "Very high" } } }, "text": "How large is the target community for the currency?" }, { "id": "token-backing-model", "label": "How will the community currency be backed?", "type": "select", "briefSection": "token-design", "options": [ { "label": "Backed by fiat reserve (1:1 or fractional)", "value": "fiat-backed" }, { "label": "Backed by goods/services commitments from merchants", "value": "goods-backed" }, { "label": "Mutual credit (no external backing: community trust)", "value": "mutual-credit" }, { "label": "Hybrid (partial fiat backing + community commitment)", "value": "hybrid" } ], "propertyMapping": { "fiat-backed": { "technologies": [ "Reserve-backed token engine", "Fiat custody" ], "technologyProperties": { "backingModel": "Fiat reserve", "regulatoryBurden": "Higher \u2014 may be classified as e-money" } }, "goods-backed": { "technologies": [ "Commitment-backed token engine" ], "technologyProperties": { "backingModel": "Goods and services commitments", "regulatoryBurden": "Lower \u2014 typically voucher classification" } }, "mutual-credit": { "technologies": [ "Mutual credit engine" ], "technologyProperties": { "backingModel": "Community trust / mutual obligation", "regulatoryBurden": "Varies \u2014 regulatory grey area in many jurisdictions" } }, "hybrid": { "technologies": [ "Hybrid-backed token engine", "Partial fiat custody" ], "technologyProperties": { "backingModel": "Hybrid fiat + community backing", "regulatoryBurden": "Medium \u2014 depends on fiat proportion" } } }, "text": "How will the community currency be backed?" }, { "id": "token-expiry-demurrage", "label": "Should the currency have built-in incentives for circulation (e.g., expiry or demurrage)?", "type": "select", "briefSection": "token-design", "options": [ { "label": "Yes, tokens expire after a set period to encourage spending", "value": "expiry" }, { "label": "Yes, demurrage (tokens lose value over time) to discourage hoarding", "value": "demurrage" }, { "label": "No, tokens retain value indefinitely", "value": "no-decay" }, { "label": "Unsure, need guidance", "value": "unsure" } ], "propertyMapping": { "expiry": { "technologies": [ "Time-limited token contract" ], "technologyProperties": { "circulationIncentive": "Token expiry", "economicDesign": "Encourages spending, discourages hoarding" } }, "demurrage": { "technologies": [ "Demurrage token contract" ], "technologyProperties": { "circulationIncentive": "Demurrage (decay over time)", "economicDesign": "Graduated spending incentive" } }, "no-decay": { "technologies": [ "Standard persistent token" ], "technologyProperties": { "circulationIncentive": "None", "economicDesign": "Store of value permitted" } }, "unsure": { "technologies": [ "Configurable token engine" ], "technologyProperties": { "circulationIncentive": "To be determined", "economicDesign": "Requires economic design consultation" } } }, "text": "Should the currency have built-in incentives for circulation (e.g., expiry or demurrage)?" }, { "id": "governance-model", "label": "Who will govern the currency (issuance rules, redemption, disputes)?", "type": "select", "briefSection": "community-governance", "options": [ { "label": "Community committee or council", "value": "community" }, { "label": "NGO-managed with community input", "value": "ngo-led" }, { "label": "Shared governance (NGO + community + local authority)", "value": "shared" }, { "label": "Fully automated rules (code-based governance)", "value": "automated" } ], "propertyMapping": { "community": { "technologies": [ "Community governance module", "Multi-sig treasury" ], "technologyProperties": { "governanceModel": "Community-led", "decisionMaking": "Community committee controls issuance and rules" } }, "ngo-led": { "technologies": [ "Managed governance module" ], "technologyProperties": { "governanceModel": "NGO-managed", "decisionMaking": "NGO controls with community consultation" } }, "shared": { "technologies": [ "Multi-stakeholder governance module", "Role-based access" ], "technologyProperties": { "governanceModel": "Shared governance", "decisionMaking": "Multi-party approval for key decisions" } }, "automated": { "technologies": [ "Smart contract governance", "Algorithmic issuance" ], "technologyProperties": { "governanceModel": "Automated", "decisionMaking": "Rules encoded in smart contracts" } } }, "text": "Who will govern the currency (issuance rules, redemption, disputes)?" }, { "id": "merchant-network-size", "label": "How many local merchants or service providers would accept the currency?", "type": "select", "briefSection": "merchant-network", "options": [ { "label": "Under 20 merchants", "value": "small" }, { "label": "20\u2013100 merchants", "value": "medium" }, { "label": "100\u2013500 merchants", "value": "large" }, { "label": "500+ merchants", "value": "very-large" } ], "propertyMapping": { "small": { "technologies": [ "Simple merchant registry" ], "technologyProperties": { "merchantScale": "Under 20", "networkComplexity": "Low" } }, "medium": { "technologies": [ "Merchant onboarding platform" ], "technologyProperties": { "merchantScale": "20\u2013100", "networkComplexity": "Medium" } }, "large": { "technologies": [ "Merchant management platform", "POS integration" ], "technologyProperties": { "merchantScale": "100\u2013500", "networkComplexity": "High" } }, "very-large": { "technologies": [ "Enterprise merchant network", "Multi-location POS" ], "technologyProperties": { "merchantScale": "500+", "networkComplexity": "Very high" } } }, "text": "How many local merchants or service providers would accept the currency?" }, { "id": "redemption-model", "label": "Can community currency be exchanged back to fiat or other assets?", "type": "select", "briefSection": "redemption-model", "options": [ { "label": "Yes, open redemption to fiat at any time", "value": "open" }, { "label": "Yes, but with conditions (minimum period, fees, limits)", "value": "conditional" }, { "label": "No, currency circulates only within the community economy", "value": "closed" }, { "label": "Partial, NGO provides periodic buyback windows", "value": "periodic" } ], "propertyMapping": { "open": { "technologies": [ "Open redemption gateway", "Fiat liquidity pool" ], "technologyProperties": { "redemptionModel": "Open", "liquidityRequirement": "High \u2014 must maintain fiat reserve" } }, "conditional": { "technologies": [ "Conditional redemption gateway" ], "technologyProperties": { "redemptionModel": "Conditional", "liquidityRequirement": "Medium \u2014 buffer reserve needed" } }, "closed": { "technologies": [ "Closed-loop token system" ], "technologyProperties": { "redemptionModel": "Closed loop", "liquidityRequirement": "None \u2014 no fiat backing required" } }, "periodic": { "technologies": [ "Periodic buyback mechanism" ], "technologyProperties": { "redemptionModel": "Periodic buyback", "liquidityRequirement": "Predictable \u2014 based on buyback schedule" } } }, "text": "Can community currency be exchanged back to fiat or other assets?" }, { "id": "regulatory-environment", "label": "What is the regulatory environment for alternative currencies in the target country?", "type": "select", "briefSection": "regulatory-context", "options": [ { "label": "Supportive: government has enabled community currencies or e-money", "value": "supportive" }, { "label": "Neutral: no specific regulation, not prohibited", "value": "neutral" }, { "label": "Restrictive: regulations may limit token-based currencies", "value": "restrictive" }, { "label": "Unknown, the regulatory position needs assessment", "value": "unknown" } ], "propertyMapping": { "supportive": { "technologies": [], "technologyProperties": { "regulatoryContext": "Supportive environment", "complianceBurden": "Low \u2014 align with existing frameworks" } }, "neutral": { "technologies": [], "technologyProperties": { "regulatoryContext": "No specific regulation", "complianceBurden": "Medium \u2014 proactive engagement recommended" } }, "restrictive": { "technologies": [ "Compliance wrapper", "Regulatory reporting module" ], "technologyProperties": { "regulatoryContext": "Restrictive environment", "complianceBurden": "High \u2014 legal counsel essential" } }, "unknown": { "technologies": [], "technologyProperties": { "regulatoryContext": "Assessment needed", "complianceBurden": "Unknown \u2014 regulatory analysis required pre-deployment" } } }, "text": "What is the regulatory environment for alternative currencies in the target country?" }, { "id": "beneficiary-choice", "label": "How will beneficiaries exercise choice in how they receive and use this service?", "type": "select", "briefSection": "End-user interface", "options": [ { "label": "Beneficiaries choose between delivery methods (cash, voucher, mobile money, direct)", "value": "delivery-choice" }, { "label": "Beneficiaries choose preferred merchants or service points", "value": "merchant-choice" }, { "label": "Beneficiaries control their own data sharing preferences", "value": "data-choice" }, { "label": "Multiple choice dimensions (delivery + merchant + data)", "value": "full-choice" }, { "label": "Limited choice: programme constraints determine delivery", "value": "limited" } ], "propertyMapping": { "delivery-choice": { "technologies": [], "technologyProperties": { "beneficiaryChoice": "Delivery method choice", "dignityDesign": "Beneficiaries select preferred receipt method" } }, "merchant-choice": { "technologies": [], "technologyProperties": { "beneficiaryChoice": "Merchant/service point choice", "dignityDesign": "Beneficiaries select where to redeem" } }, "data-choice": { "technologies": [], "technologyProperties": { "beneficiaryChoice": "Data sharing choice", "dignityDesign": "Beneficiaries control personal data sharing" } }, "full-choice": { "technologies": [], "technologyProperties": { "beneficiaryChoice": "Multi-dimensional choice", "dignityDesign": "Full beneficiary agency across delivery, merchant, and data" } }, "limited": { "technologies": [], "technologyProperties": { "beneficiaryChoice": "Limited by programme design", "dignityDesign": "Programme constraints; beneficiary informed of reasons" } } }, "text": "How will beneficiaries exercise choice in how they receive and use this service?" } ], "complexityFactors": { "relationships": 3, "operationalChange": 4, "dataCompliance": 2 }, "suggestedCriteria": [ { "id": "SC-TOKEN-DESIGN", "name": "Token Design & Economic Model", "description": "The provider can implement different community currency models. Community currencies vary widely. Some are backed by national currency, some by community assets, some use demurrage (holding fees) to encourage circulation.", "weight": 0.3, "ratingGuide": { "5": "Configurable token economics: backing models (fiat, asset, mutual credit), demurrage, bonding curves, exchange rate mechanisms. Simulation tools for economic design.", "4": "Multiple economic models supported. Good configuration. Basic simulation.", "3": "2-3 pre-built models. Configurable parameters. No simulation.", "2": "Single currency model. Limited parameter adjustment.", "1": "Fixed token design. No economic model customisation." } }, { "id": "SC-COMMUNITY-ACCESS", "name": "Community Accessibility", "description": "Community members can transact using basic phones without internet. Community currencies serve populations that are often financially excluded. The technology must not create a new barrier to participation.", "weight": 0.25, "ratingGuide": { "5": "USSD/SMS transactions on feature phones. NFC tap-to-pay option. No internet required. Multi-language. Visual/audio interface for low-literacy users.", "4": "USSD or SMS capability. Basic smartphone app. Offline transactions. Multi-language.", "3": "Basic smartphone app with offline capability. 2 languages.", "2": "Smartphone app requiring internet. Single language.", "1": "Internet-dependent application. Smartphone required. English only." } }, { "id": "SC-MERCHANT-NET", "name": "Merchant Network Management", "description": "The provider supports building and managing the merchant acceptance network. A community currency is only useful if local shops accept it. The system needs merchant onboarding, settlement, and conversion tools.", "weight": 0.2, "ratingGuide": { "5": "Merchant onboarding tools. POS integration (paper or digital). Settlement to national currency. Merchant dashboard. Analytics on spending patterns. Merchant incentive management.", "4": "Good merchant tools. Basic POS. Settlement available. Merchant reporting.", "3": "Merchant registration. Manual settlement. Basic transaction tracking.", "2": "Merchant list. No settlement tools. Manual conversion process.", "1": "No merchant management. Peer-to-peer only." } }, { "id": "SC-GOVERNANCE-CC", "name": "Community Governance Tools", "description": "The provider supports community governance of the currency. Community currencies need democratic oversight. Decisions about money supply, merchant policies, and redemption rules should involve the community.", "weight": 0.15, "ratingGuide": { "5": "Built-in governance: voting on currency parameters, transparent money supply dashboard, community proposal system, elected committee tools.", "4": "Good governance tools. Voting capability. Supply transparency. Basic proposal system.", "3": "Transparent money supply data. Manual governance processes. Basic voting.", "2": "Money supply visible. Governance decisions made outside the system.", "1": "No governance tools. Centralised management with no community oversight." } }, { "id": "SC-IMPACT-CC", "name": "Economic Impact Measurement", "description": "The provider can measure the multiplier effect and economic impact of the community currency. Donors and programme managers need evidence that the currency is stimulating local economic activity.", "weight": 0.1, "ratingGuide": { "5": "Velocity tracking (how often currency circulates). Multiplier calculation. Sector analysis (where spending flows). Beneficiary income impact. Geographic heat maps.", "4": "Good velocity and circulation metrics. Basic multiplier. Sector breakdown.", "3": "Transaction volume and frequency data. Manual impact analysis possible.", "2": "Basic transaction counts. No economic analysis tools.", "1": "No impact measurement capability." } } ], "procurement": { "marketMaturity": "nascent", "primaryMode": "integrator-led", "alternativeModes": [ "internal-build" ], "reasoning": "Community currencies are typically bespoke or research projects.", "exampleProductCategories": [ "community-currency-platform", "complementary-currency-rails" ], "partnerChannels": [], "lastReviewed": "2026-05-01" } }, { "id": "UC-A-024", "name": "Currency hedging and stability (stablecoin alternatives)", "category": "A", "subcategory": "Treasury Operations", "description": "Protect the value of your funds where the local currency is losing value or hard to exchange, and ordinary protection is not available.", "bCriteria": [ "B4", "B5", "B6", "B7" ], "requiredComponents": [ { "component": "stablecoin-treasury", "description": "Treasury allocation held in one or more regulated or over-collateralised stablecoins as a hedge against local-currency depreciation" }, { "component": "wallet-infra", "description": "Custodial or non-custodial wallets for holding and signing stablecoin movements" }, { "component": "identity-verification", "description": "Verified signatory identities and role-based treasury permissions" }, { "component": "audit-mechanism", "description": "On-chain audit trail plus off-chain reconciliation to programme accounting" }, { "component": "compliance-rules-engine", "description": "Policy layer encoding sanctions, AML, stablecoin-issuer compliance and jurisdictional restrictions" } ], "conditionalComponents": [ { "component": "multi-sig", "condition": "If treasury movement requires multi-party authorisation above a threshold" }, { "component": "smart-contracts", "condition": "If automated allocation rules (target %, rebalancing triggers, programmatic conversion) are required" }, { "component": "on-off-ramp", "condition": "If the programme needs fiat-to-stablecoin and stablecoin-to-fiat conversion at scale in destination countries" }, { "component": "privacy-tech", "condition": "If beneficiary or programme information attached to treasury flows must be protected from public-chain observers" } ], "crossCategoryDependencies": [ "UC-A-006 for traditional multi-currency treasury and hedging \u2014 UC-A-024 is the stablecoin-alternative path to the same outcome", "UC-F-082 for cryptocurrency and digital-asset donations \u2014 inbound crypto flows can feed the stablecoin treasury", "UC-F-080 for transparent fund flow tracking \u2014 the shared ledger makes treasury flows auditable" ], "p2TriggerConditions": { "description": "Activated when P2 shows operations in hyperinflationary / currency-controlled jurisdictions, material FX exposure, or donor pressure for alternative value-preservation instruments.", "rangeSignals": [ "operatingCurrencyStability <= unstable", "fxExposure >= material", "crossBorderTransferVolume >= significant", "localBankingAccess <= constrained" ] }, "contextFieldsTemplate": [ { "field": "operatingJurisdictions", "source": "P0 operations", "description": "Jurisdictions where the org operates. Each carries its own regulatory stance on stablecoins" }, { "field": "localCurrencyStability", "source": "P0 context + P2", "description": "Inflation / devaluation profile of operating currencies" }, { "field": "fxExposure", "source": "P2 CatA", "description": "Annual FX exposure and observed loss from depreciation / spread" }, { "field": "treasuryGovernance", "source": "P0 governance", "description": "Who can authorise treasury movement, approval thresholds, board oversight" }, { "field": "donorAcceptance", "source": "P2 CatF", "description": "Donor stance on holding funds in stablecoins. Some donors require fiat-only" } ], "implementationComplexity": "medium-high", "examples": { "note": "Stablecoins have moved from experimental to production for humanitarian cash programming in hyperinflationary and sanctions-constrained contexts, most visibly the UNHCR USDC pilot in Ukraine. Traditional fiat alternatives (CBDCs, regulated e-money) remain limited in availability.", "references": [ { "name": "Circle USDC (regulated USD stablecoin)", "url": "https://www.circle.com/usdc", "solved": "Regulated, fiat-backed stablecoin with published attestations, the reference instrument for NGO stablecoin treasury." }, { "name": "MakerDAO / DAI", "url": "https://makerdao.com", "solved": "Decentralised over-collateralised stablecoin, an alternative model where issuer risk is distributed rather than concentrated at a single custodian." }, { "name": "UNHCR Ukraine USDC cash assistance pilot", "url": "https://www.unhcr.org/news/press-releases/unhcr-and-stellar-development-foundation-launch-groundbreaking-payment", "solved": "Production deployment of USDC-based assistance in Ukraine, which demonstrates operational feasibility of stablecoin treasury for humanitarian response in a currency-unstable environment." }, { "name": "Stellar Development Foundation \u2014 disbursement infrastructure", "url": "https://stellar.org", "solved": "Reference infrastructure for stablecoin-based humanitarian disbursement with low-cost on/off-ramps." } ] }, "solutionQuestions": [ { "id": "stablecoin-mix", "type": "select", "options": [ { "label": "A single regulated stablecoin", "value": "single-regulated" }, { "label": "Multiple regulated stablecoins for issuer diversification", "value": "multi-regulated" }, { "label": "A mix of regulated and over-collateralised decentralised stablecoins", "value": "mixed" }, { "label": "Jurisdiction-specific regulated stablecoins (e.g. a euro stablecoin in EU corridors)", "value": "jurisdictional" } ], "propertyMapping": { "single-regulated": { "technologies": [ "Single-issuer custody", "Regulated-stablecoin wallet" ], "technologyProperties": { "issuerRisk": "concentrated", "operationalComplexity": "low", "regulatoryClarity": "high" } }, "multi-regulated": { "technologies": [ "Multi-issuer custody", "Allocation engine" ], "technologyProperties": { "issuerRisk": "diversified", "operationalComplexity": "moderate", "regulatoryClarity": "high" } }, "mixed": { "technologies": [ "Multi-asset custody", "Algorithmic allocation" ], "technologyProperties": { "issuerRisk": "distributed across centralised + decentralised", "operationalComplexity": "high", "regulatoryClarity": "mixed" } }, "jurisdictional": { "technologies": [ "Multi-currency stablecoin wallet", "Corridor-specific routing" ], "technologyProperties": { "issuerRisk": "per-jurisdiction", "operationalComplexity": "high", "regulatoryClarity": "per-jurisdiction-high" } } }, "prefillFrom": null, "briefSection": "Stablecoin portfolio", "text": "What stablecoin mix should the treasury hold?", "ngoText": "What stablecoin mix should the treasury hold?" }, { "id": "custody-model", "type": "select", "options": [ { "label": "Third-party regulated custodian (exchange / qualified custodian)", "value": "custodian" }, { "label": "Self-custody with multi-sig wallet", "value": "self-multisig" }, { "label": "Hybrid: operational self-custody, reserve in custodian", "value": "hybrid" }, { "label": "Smart-contract vault with role-based access", "value": "sc-vault" } ], "propertyMapping": { "custodian": { "technologies": [ "Qualified custodian integration", "Custodian API / reporting" ], "technologyProperties": { "counterpartyRisk": "custodian", "operationalOverhead": "low", "insurance": "available" } }, "self-multisig": { "technologies": [ "Multi-sig wallet", "Hardware security modules", "Key ceremony processes" ], "technologyProperties": { "counterpartyRisk": "none (self-custody)", "operationalOverhead": "high", "insurance": "limited" } }, "hybrid": { "technologies": [ "Multi-sig + custodian", "Segregated hot / cold allocation" ], "technologyProperties": { "counterpartyRisk": "split", "operationalOverhead": "moderate", "insurance": "partial" } }, "sc-vault": { "technologies": [ "Smart-contract vault", "Role-based access contracts", "Audit integration" ], "technologyProperties": { "counterpartyRisk": "protocol", "operationalOverhead": "moderate", "insurance": "emerging" } } }, "prefillFrom": null, "briefSection": "Custody", "text": "How should the stablecoin treasury be held?", "ngoText": "How should the stablecoin treasury be held?" }, { "id": "rebalancing-policy", "type": "select", "options": [ { "label": "Manual: treasury makes allocation decisions ad hoc", "value": "manual" }, { "label": "Policy-driven manual: documented policy, manual execution", "value": "policy-manual" }, { "label": "Rule-based semi-automated: thresholds trigger human review", "value": "rule-semi-auto" }, { "label": "Fully automated via smart contract", "value": "smart-contract" } ], "propertyMapping": { "manual": { "technologies": [ "Manual allocation workflow" ], "technologyProperties": { "responseTime": "days", "consistency": "variable", "auditability": "weak" } }, "policy-manual": { "technologies": [ "Allocation policy", "Manual execution workflow" ], "technologyProperties": { "responseTime": "hours-to-days", "consistency": "strong", "auditability": "moderate" } }, "rule-semi-auto": { "technologies": [ "Threshold monitoring", "Human-in-loop workflow" ], "technologyProperties": { "responseTime": "minutes-to-hours", "consistency": "strong", "auditability": "strong" } }, "smart-contract": { "technologies": [ "Allocation smart contract", "Oracle price feeds", "Automated execution" ], "technologyProperties": { "responseTime": "seconds-to-minutes", "consistency": "deterministic", "auditability": "very-strong" } } }, "prefillFrom": null, "briefSection": "Rebalancing and allocation", "text": "How should allocation and rebalancing between stablecoins and fiat be governed?", "ngoText": "How should allocation and rebalancing between stablecoins and fiat be governed?" }, { "id": "on-off-ramp-strategy", "type": "select", "options": [ { "label": "HQ-only ramping (convert in banking jurisdiction, move fiat out)", "value": "hq-only" }, { "label": "In-country ramping via licensed local exchanges", "value": "in-country-exchange" }, { "label": "Direct stablecoin-to-mobile-money corridors", "value": "mobile-money" }, { "label": "Mixed per corridor based on available infrastructure", "value": "mixed" } ], "propertyMapping": { "hq-only": { "technologies": [ "HQ banking integration", "Outbound fiat rails" ], "technologyProperties": { "onRampCost": "low at HQ", "endpointCoverage": "weak", "regulatoryClarity": "HQ-side" } }, "in-country-exchange": { "technologies": [ "Local exchange integration", "Licensing management" ], "technologyProperties": { "onRampCost": "moderate", "endpointCoverage": "moderate", "regulatoryClarity": "per-jurisdiction" } }, "mobile-money": { "technologies": [ "Mobile-money integration", "Corridor-specific rails" ], "technologyProperties": { "onRampCost": "low to beneficiary", "endpointCoverage": "strong in select corridors", "regulatoryClarity": "per-operator" } }, "mixed": { "technologies": [ "Multi-corridor rail router", "Corridor-specific workflow" ], "technologyProperties": { "onRampCost": "variable", "endpointCoverage": "strong", "regulatoryClarity": "mixed" } } }, "prefillFrom": null, "briefSection": "On/off-ramp strategy", "text": "How should the treasury convert between stablecoins and local currency in each operating corridor?", "ngoText": "How should the treasury convert between stablecoins and local currency in each operating corridor?" }, { "id": "donor-acceptance-model", "type": "select", "options": [ { "label": "No stablecoin treasury, donor restrictions prohibit it", "value": "prohibited" }, { "label": "Stablecoin treasury disclosed and accepted in donor agreements", "value": "disclosed-accepted" }, { "label": "Specific donors fund stablecoin pilots; others remain fiat-only", "value": "segmented" }, { "label": "Donor-agnostic: treasury policy independent of donor preferences", "value": "agnostic" } ], "propertyMapping": { "prohibited": { "technologies": [], "technologyProperties": { "donorAlignment": "strong", "innovationSpace": "none", "operationalImpact": "status-quo" } }, "disclosed-accepted": { "technologies": [ "Donor-agreement templates", "Disclosure workflow" ], "technologyProperties": { "donorAlignment": "strong", "innovationSpace": "broad", "operationalImpact": "moderate" } }, "segmented": { "technologies": [ "Fund-segregation accounting", "Per-donor reporting" ], "technologyProperties": { "donorAlignment": "mixed", "innovationSpace": "bounded", "operationalImpact": "moderate-high" } }, "agnostic": { "technologies": [ "Independent treasury policy", "Risk-disclosure reporting" ], "technologyProperties": { "donorAlignment": "at-risk", "innovationSpace": "broad", "operationalImpact": "low" } } }, "prefillFrom": null, "briefSection": "Donor alignment", "text": "How does donor acceptance shape the treasury model?", "ngoText": "How does donor acceptance shape the treasury model?" } ], "complexityFactors": { "relationships": 3, "operationalChange": 4, "dataCompliance": 4 }, "suggestedCriteria": [ { "id": "SC-PEG-STABILITY", "name": "Peg Stability and Issuer Quality", "description": "How credible is the chosen stablecoin's peg (considering reserve composition, attestation frequency, regulatory oversight, and historical de-peg events)?", "weight": 0.25, "ratingGuide": { "5": "Full-reserve, regulator-audited, monthly or more frequent attestations, proven peg resilience through multiple market stresses.", "4": "Fully reserved with quarterly attestations, no material de-peg events in the last 24 months.", "3": "Mostly reserved with periodic attestations, minor peg deviations under stress.", "2": "Over-collateralised decentralised or partially reserved; peg has broken briefly under stress.", "1": "Algorithmic / under-reserved / history of significant de-pegs." } }, { "id": "SC-REGULATORY-FIT", "name": "Regulatory Fit Across Operating Jurisdictions", "description": "Is the stablecoin treasury model legal and operationally viable in every jurisdiction the org operates in, including destination countries?", "weight": 0.25, "ratingGuide": { "5": "Explicitly permitted and regulated in all operating jurisdictions; well-defined licensing and reporting obligations met.", "4": "Permitted in most jurisdictions with clear licensing; ambiguous but not prohibited elsewhere.", "3": "Legal in HQ jurisdiction and major corridors; grey areas in some field jurisdictions.", "2": "Permissioned in HQ; several field jurisdictions prohibit or restrict \u2014 workarounds required.", "1": "Prohibited or effectively unusable in the org's operating corridors." } }, { "id": "SC-CUSTODY-RESILIENCE", "name": "Custody and Operational Security", "description": "How resilient is the custody architecture against theft, key loss, custodian insolvency, and operational errors?", "weight": 0.2, "ratingGuide": { "5": "Multi-sig with geographically distributed signers, HSM-backed keys, documented key ceremony, insured custodian for reserves, regular tabletop exercises.", "4": "Multi-sig with multiple signers, standard HSM, tested recovery procedures.", "3": "Multi-sig with documented signer roster, basic key management.", "2": "Single custodian with standard insurance.", "1": "Single-signer wallet or uninsured custodian." } }, { "id": "SC-RAMP-RESILIENCE", "name": "On/Off-Ramp Resilience in Operating Corridors", "description": "Can the programme reliably convert between stablecoin and local currency at the edges, including under stress (exchange outage, capital controls, sanctions shock)?", "weight": 0.15, "ratingGuide": { "5": "Redundant ramps per corridor with documented fallback; tested under stress; capacity exceeds programme peak.", "4": "Multiple ramps per major corridor; capacity sufficient; fallback documented.", "3": "Single ramp per corridor with basic fallback plan.", "2": "Single ramp per corridor; limited fallback.", "1": "Dependent on a single provider corridor-wide; no tested fallback." } }, { "id": "SC-DONOR-TRANSPARENCY", "name": "Donor Transparency on Treasury Risk", "description": "Does the programme disclose stablecoin treasury risk and reporting to donors at a level that maintains trust and aligns with donor accountability obligations?", "weight": 0.15, "ratingGuide": { "5": "Proactive disclosure including peg risk, custody risk, regulatory risk; aligned with donor-specific reporting; covered in audit opinion.", "4": "Standard disclosure with quarterly reporting.", "3": "Disclosure at annual audit; on-request reporting.", "2": "Minimal disclosure; treasury model not specifically covered in donor reports.", "1": "Undisclosed stablecoin holdings." } } ], "procurement": { "marketMaturity": "emerging", "primaryMode": "rfq", "alternativeModes": [ "off-the-shelf" ], "reasoning": "Currency hedging via stablecoin alternatives is emerging but viable products exist.", "exampleProductCategories": [ "stablecoin-treasury-platform", "fx-hedging-platform" ], "partnerChannels": [], "lastReviewed": "2026-05-01" } }, { "id": "UC-A-025", "name": "Insurance for field staff and organisational assets", "category": "A", "subcategory": "Risk Management", "description": "Pay claims for staff and equipment faster, based on agreed evidence, where commercial insurers serve fragile or conflict-affected areas poorly.", "bCriteria": [ "B3", "B4", "B5", "B7" ], "requiredComponents": [ { "component": "smart-contracts", "description": "Parametric trigger and claim-adjudication logic (flight-status medevac, security-alert kidnap/evacuation, weather-triggered asset damage)" }, { "component": "oracle-data", "description": "Trusted external data feeds (flight APIs, weather services, security incident feeds, news/NLP sources, IoT telemetry)" }, { "component": "identity-verification", "description": "Staff roster and asset registry with verifiable credentials linking each insured entity to policy terms" }, { "component": "audit-mechanism", "description": "Tamper-evident record of incident, evidence, trigger evaluation, and payout for regulator / donor / re-insurance accountability" }, { "component": "payment-rails", "description": "Payout settlement layer (stablecoin or fiat rail) capable of reaching affected staff or asset repair counterparties within hours" } ], "conditionalComponents": [ { "component": "iot-sensors", "condition": "If physical-asset coverage requires continuous condition telemetry (vehicles, generators, refrigeration, premises)" }, { "component": "privacy-tech", "condition": "If medical / security claim data must be kept confidential from pool members, re-insurers, or public ledger observers" }, { "component": "multi-sig", "condition": "If high-value claims (e.g. > USD 250k asset loss, kidnap/ransom) require multi-party authorisation for payout" }, { "component": "kyc-platform", "condition": "If the policy uses an NGO-mutual pool and pool members must be KYC-verified (see UC-F-090)" } ], "crossCategoryDependencies": [ "UC-A-022 for parametric-insurance mechanics applied to beneficiaries - shared smart-contract and oracle patterns", "UC-A-024 for stablecoin treasury - payout currency rail and value stability for premium reserves", "UC-F-090 for pool-member KYC when using NGO-mutual models" ], "p2TriggerConditions": { "description": "Activated when P2 indicates material field-staff deployment, significant physical-asset base, insurance gaps, or poor claim-settlement experience.", "rangeSignals": [ "internationalStaffCount >= material", "operationalRisk >= high", "insuranceGap == present", "claimSettlementFriction >= moderate" ] }, "contextFieldsTemplate": [ { "field": "staffFootprint", "source": "P2 CatJ", "description": "Field-deployed staff by country, role, and risk tier" }, { "field": "assetInventory", "source": "P0 asset register", "description": "Organisational assets in scope (vehicles, ICT, premises, generators, equipment)" }, { "field": "currentCoverage", "source": "P0 insurance schedule", "description": "Existing policies (travel, medevac, K&R, property, cyber) and coverage gaps" }, { "field": "incidentHistory", "source": "P0 / P2 CatG+CatJ", "description": "Incident and claim history over the last 24-36 months" }, { "field": "riskAppetite", "source": "Board / exec policy", "description": "Self-insurance tolerance, deductibles, catastrophe caps" } ], "implementationComplexity": "medium-high", "examples": { "note": "Parametric insurance is a mature blockchain pattern (Etherisc, Arbol, Lemonade). NGO-specific field-risk cover is historically broker-mediated and illiquid; sovereign parametric pools (ARC) and humanitarian parametric pilots (Oxfam R4) have proved feasibility for disaster risk. On-chain mutuals (Nexus Mutual) demonstrate capital-efficient peer pooling without traditional reinsurance. The UC sits in a market where underwriting capacity for fragile-state staff and asset risk is scarce - blockchain's value is strongest at the disintermediation and settlement-speed layers.", "references": [ { "name": "Etherisc - decentralised insurance protocol", "url": "https://etherisc.com", "solved": "Reference implementation for parametric triggers, smart-contract claim adjudication, and stablecoin payouts, directly transferable to field-staff medevac and asset-damage policies." }, { "name": "Nexus Mutual - on-chain mutual insurance", "url": "https://nexusmutual.io", "solved": "Peer-pooled capital and claim voting model, the template for an NGO-mutual that disintermediates traditional reinsurance for field risk." }, { "name": "Oxfam R4 Rural Resilience Initiative", "url": "https://www.oxfamamerica.org/explore/issues/economic-well-being/r4-resilience-initiative", "solved": "Humanitarian parametric insurance at scale, an operational precedent for applying parametric mechanics to NGO-adjacent risk." }, { "name": "African Risk Capacity (ARC)", "url": "https://www.arc.int", "solved": "Sovereign-level parametric pool with weather-triggered payouts, operational evidence that parametric structures settle fast and survive catastrophe events." } ] }, "solutionQuestions": [ { "id": "coverage-scope", "type": "select", "options": [ { "label": "Field staff only (travel, medevac, accident, K&R)", "value": "staff" }, { "label": "Organisational assets only (vehicles, equipment, premises)", "value": "assets" }, { "label": "Both - separate policies per risk class", "value": "both-separate" }, { "label": "Integrated programme - staff and assets in one mutual / pool", "value": "both-integrated" } ], "propertyMapping": { "staff": { "technologies": [ "Travel / medevac oracle feeds", "Staff roster credentials" ], "technologyProperties": { "payoutLatency": "hours-to-days", "dataSensitivity": "high (medical)", "regulatoryComplexity": "high (health)" } }, "assets": { "technologies": [ "Asset register", "IoT telemetry", "Weather / incident feeds" ], "technologyProperties": { "payoutLatency": "days-to-weeks", "dataSensitivity": "low", "regulatoryComplexity": "moderate" } }, "both-separate": { "technologies": [ "Both stacks operated independently" ], "technologyProperties": { "payoutLatency": "mixed", "dataSensitivity": "segregated", "regulatoryComplexity": "high" } }, "both-integrated": { "technologies": [ "Shared pool contract", "Cross-class risk accounting", "Unified claim engine" ], "technologyProperties": { "payoutLatency": "hours-to-days", "dataSensitivity": "mixed with privacy layer", "regulatoryComplexity": "very-high" } } }, "prefillFrom": null, "briefSection": "Coverage scope", "text": "What risk class does the policy need to cover?", "ngoText": "What risk class does the policy need to cover?" }, { "id": "underwriting-model", "type": "select", "options": [ { "label": "Traditional broker-mediated commercial policy", "value": "broker" }, { "label": "Self-insurance with internal reserve", "value": "self-insured" }, { "label": "NGO-mutual / peer pool (cross-NGO risk sharing)", "value": "mutual" }, { "label": "Parametric on-chain policy with external capital providers", "value": "parametric-external" } ], "propertyMapping": { "broker": { "technologies": [ "Broker portal", "Policy schedule", "Claim submission workflow" ], "technologyProperties": { "disintermediation": "none", "cost": "high (broker + reinsurer margins)", "speedToPayout": "weeks-to-months" } }, "self-insured": { "technologies": [ "Reserve fund", "Claim adjudication committee" ], "technologyProperties": { "disintermediation": "full internal", "cost": "capital-tied-up", "speedToPayout": "internal-approval-dependent" } }, "mutual": { "technologies": [ "Mutual pool smart contract", "Member governance", "Premium engine" ], "technologyProperties": { "disintermediation": "strong (peer risk sharing)", "cost": "moderate, shared margins", "speedToPayout": "hours-to-days on trigger" } }, "parametric-external": { "technologies": [ "Parametric policy contract", "External capital via tokenised cover" ], "technologyProperties": { "disintermediation": "strong", "cost": "market-priced by capital providers", "speedToPayout": "minutes-to-hours on trigger" } } }, "prefillFrom": null, "briefSection": "Underwriting model", "text": "Who underwrites the risk?", "ngoText": "Who underwrites the risk?" }, { "id": "trigger-mechanism", "type": "select", "options": [ { "label": "Indemnity - adjuster assesses loss after the fact", "value": "indemnity" }, { "label": "Parametric - objective data trigger (weather, flight data, security alert)", "value": "parametric" }, { "label": "Hybrid - parametric fast-pay with indemnity top-up", "value": "hybrid" }, { "label": "Attestation-based - trusted third-party attestation triggers payout", "value": "attestation" } ], "propertyMapping": { "indemnity": { "technologies": [ "Adjuster workflow", "Evidence upload" ], "technologyProperties": { "disputeRisk": "high", "payoutLatency": "weeks-to-months", "basisRisk": "low" } }, "parametric": { "technologies": [ "Oracle feeds", "Trigger-evaluator contract", "Payout contract" ], "technologyProperties": { "disputeRisk": "low", "payoutLatency": "minutes-to-hours", "basisRisk": "moderate - parametric may under/over-pay vs actual loss" } }, "hybrid": { "technologies": [ "Parametric fast-pay rail", "Indemnity top-up workflow" ], "technologyProperties": { "disputeRisk": "low on parametric portion", "payoutLatency": "mixed", "basisRisk": "reduced by top-up" } }, "attestation": { "technologies": [ "Attestor registry", "Signed attestation", "Payout contract" ], "technologyProperties": { "disputeRisk": "attestor-dependent", "payoutLatency": "hours-to-days", "basisRisk": "low" } } }, "prefillFrom": null, "briefSection": "Trigger mechanism", "text": "How is a claim triggered?", "ngoText": "How is a claim triggered?" }, { "id": "payout-currency-model", "type": "select", "options": [ { "label": "Local fiat via bank rail", "value": "local-fiat" }, { "label": "USD via traditional wire", "value": "usd-wire" }, { "label": "Stablecoin direct to wallet", "value": "stablecoin" }, { "label": "Multi-rail - stablecoin with fiat off-ramp options", "value": "multi-rail" } ], "propertyMapping": { "local-fiat": { "technologies": [ "Local bank rail" ], "technologyProperties": { "speedToFunds": "days", "accessibility": "broad local", "stability": "local-currency-risk" } }, "usd-wire": { "technologies": [ "Correspondent banking" ], "technologyProperties": { "speedToFunds": "days-to-weeks", "accessibility": "limited in fragile states", "stability": "USD" } }, "stablecoin": { "technologies": [ "Stablecoin rail", "Wallet delivery" ], "technologyProperties": { "speedToFunds": "minutes-to-hours", "accessibility": "wallet-dependent", "stability": "USD-peg" } }, "multi-rail": { "technologies": [ "Stablecoin primary", "Fiat off-ramp network" ], "technologyProperties": { "speedToFunds": "hours", "accessibility": "broad", "stability": "USD-peg with local fiat option" } } }, "prefillFrom": null, "briefSection": "Payout currency", "text": "How should payouts settle?", "ngoText": "How should payouts settle?" }, { "id": "evidence-integrity-model", "type": "select", "options": [ { "label": "Document upload with org signatures", "value": "docs" }, { "label": "Hashed evidence anchored on-chain", "value": "anchored" }, { "label": "Verifiable credentials from authorised attestors (medics, security firms)", "value": "vc-attestors" }, { "label": "Oracle-only - no per-claim evidence required", "value": "oracle-only" } ], "propertyMapping": { "docs": { "technologies": [ "Document store", "Manual review" ], "technologyProperties": { "tamperEvidence": "weak", "auditability": "org-trust-dependent", "scalability": "manual" } }, "anchored": { "technologies": [ "Evidence hashing service", "On-chain anchor" ], "technologyProperties": { "tamperEvidence": "strong", "auditability": "external verifiers", "scalability": "moderate" } }, "vc-attestors": { "technologies": [ "Attestor trust registry", "VC verification service" ], "technologyProperties": { "tamperEvidence": "strong", "auditability": "strong cryptographic", "scalability": "strong" } }, "oracle-only": { "technologies": [ "Oracle feeds" ], "technologyProperties": { "tamperEvidence": "oracle-dependent", "auditability": "machine-verifiable", "scalability": "very-strong" } } }, "prefillFrom": null, "briefSection": "Evidence integrity", "text": "How is claim evidence proved unaltered?", "ngoText": "How is claim evidence proved unaltered?" } ], "complexityFactors": { "relationships": 4, "operationalChange": 3, "dataCompliance": 4 }, "suggestedCriteria": [ { "id": "SC-PAYOUT-SPEED", "name": "Time to Payout After Trigger Event", "description": "How quickly do funds reach the affected staff member or asset repair counterparty once the triggering event has occurred?", "weight": 0.25, "ratingGuide": { "5": "Minutes to hours - smart-contract payout on oracle confirmation, direct to wallet.", "4": "Same-day payout via stablecoin rail with automated adjudication.", "3": "1-5 business days via established rail.", "2": "1-4 weeks via broker / adjuster workflow.", "1": "Months - typical fragile-state commercial-claims settlement." } }, { "id": "SC-BASIS-RISK", "name": "Basis Risk Between Trigger and Actual Loss", "description": "This measures how closely the trigger (parametric, attestation, or oracle) matches actual experienced loss. High basis risk = payouts may systematically under-cover real harm.", "weight": 0.2, "ratingGuide": { "5": "Negligible - trigger is the loss (e.g. flight cancellation = medevac need).", "4": "Hybrid parametric + indemnity top-up closes gaps.", "3": "Parametric calibrated with historical loss data; residual gap acceptable.", "2": "Parametric with material over/under-pay risk.", "1": "Parametric trigger weakly correlated with actual loss." } }, { "id": "SC-EVIDENCE-INTEGRITY", "name": "Claim Evidence Integrity", "description": "Can claim evidence - incident reports, medical attestations, asset damage proof - be proved unaltered at any point after the event?", "weight": 0.2, "ratingGuide": { "5": "Cryptographic evidence anchoring with verifiable-credential attestors; any auditor can independently verify.", "4": "Hashed evidence with on-chain anchors; manual attestor signatures.", "3": "Document control with access logs; tamper-evident at database layer.", "2": "Document upload with manual review.", "1": "Ad-hoc - evidence scattered across email, paper, photos." } }, { "id": "SC-MARKET-ACCESS", "name": "Underwriting Market Access", "description": "Does the structure give the NGO access to underwriting capacity that traditional commercial insurance cannot reach - particularly for fragile-state, K&R, and catastrophe risks?", "weight": 0.2, "ratingGuide": { "5": "Accesses NGO-mutual or DeFi capital markets - capacity independent of traditional reinsurance cycles.", "4": "Blends commercial and mutual capacity; meaningful disintermediation.", "3": "Uses standard commercial market with improved evidence / data sharing.", "2": "Entirely commercial market with broker dependency.", "1": "No underwriting access - self-insured from reserves only." } }, { "id": "SC-REGULATORY-FIT", "name": "Insurance-Regulatory Fit", "description": "The structure survives regulatory review in the jurisdictions it operates across. Insurance is heavily regulated - DeFi-native structures can be non-compliant in many markets.", "weight": 0.15, "ratingGuide": { "5": "Licensed structure in all material jurisdictions; on-chain component operates as a permitted ancillary.", "4": "Licensed in primary jurisdictions; DeFi component isolated to compatible venues.", "3": "Commercial policy with blockchain-assisted evidence - regulator-neutral.", "2": "Pool model with unclear regulatory status in some jurisdictions.", "1": "DeFi-native structure with no licensed fallback - regulatory tail risk." } } ], "procurement": { "marketMaturity": "mature", "primaryMode": "off-the-shelf", "alternativeModes": [ "conversation-guide" ], "reasoning": "Insurance brokerage market is mature; existing relationships often present.", "exampleProductCategories": [ "insurance-broker-platform", "staff-insurance-saas" ], "partnerChannels": [], "lastReviewed": "2026-05-01" } }, { "id": "UC-B-024", "name": "Beneficiary registration (refugees, stateless, undocumented)", "category": "B", "subcategory": "Identity Registration", "description": "Register each person once and let every programme and partner recognise the same record, so nobody is counted twice or left without an identity.", "bCriteria": [ "B1", "B2", "B6" ], "requiredComponents": [ { "component": "identity-protocol", "description": "Decentralized identity framework" }, { "component": "credential-issuance", "description": "Verifiable credential issuance" }, { "component": "verification-mechanism", "description": "Proof of identity without revealing data" }, { "component": "holder-app", "description": "Wallet for beneficiary identity credentials" }, { "component": "biometric-capture", "description": "Fingerprint/iris capture for registration" }, { "component": "consent-management", "description": "Consent for data sharing" } ], "conditionalComponents": [ { "component": "privacy-tech", "condition": "If zero-knowledge proofs needed for privacy" }, { "component": "registration-hardware", "condition": "If mobile registration units needed in remote areas" } ], "crossCategoryDependencies": [ "UC-C-045 for consent records", "UC-C-043 for deduplication" ], "p2TriggerConditions": { "description": "Activated when P2 shows refugee/displaced populations + identity gaps + multi-programme presence", "rangeSignals": [ "displacedPopulation >= high", "identityDocumentation <= 50%", "multiProgrammeEnrolment >= true" ] }, "contextFieldsTemplate": [ { "field": "beneficiaryCount", "source": "P2 programme scale", "description": "Number to register" }, { "field": "identityDocStatus", "source": "P0 context + P2", "description": "Baseline ID documentation" }, { "field": "biometricCapability", "source": "P4", "description": "Biometric registration capability" }, { "field": "privacyConcerns", "source": "P0 Q19-21 + P5", "description": "Regulatory privacy requirements" }, { "field": "portability", "source": "P2 data needs", "description": "Need for portable identity" } ], "implementationComplexity": "high", "examples": { "note": "IRC Evernym pilots, UNHCR identity initiatives", "references": [ { "name": "IRC-Evernym Self-Sovereign Identity Pilot", "url": "https://www.rescue.org/article/irc-and-evernym-partner-digital-identity", "solved": "Provided self-sovereign digital identity to refugees without government-issued ID, enabling service access across organisations" }, { "name": "UNHCR PRIMES Biometric Identity", "url": "https://www.unhcr.org/registration-and-identity", "solved": "Registered millions of refugees worldwide through biometrics, for identity verification and aid distribution" }, { "name": "iRespond Biometric Identity for Stateless", "url": "https://www.irespond.org/", "solved": "Biometric identity for stateless populations in Thailand and Myanmar using iris scanning" } ] }, "solutionQuestions": [ { "id": "identity-doc-status", "type": "select", "options": [ { "label": "Most have some form of government-issued ID", "value": "some-id" }, { "label": "Majority have expired or damaged ID documents", "value": "expired-id" }, { "label": "Most are undocumented or stateless, no formal ID", "value": "undocumented" }, { "label": "Mixed: some documented, many not", "value": "mixed-status" } ], "propertyMapping": { "some-id": { "technologies": [ "Decentralised identifier (DID) framework", "Government ID system connection" ], "technologyProperties": { "identityModel": "DID anchored to existing government ID", "verificationComplexity": "low", "bootstrapRequirement": "ID scanning + verification" } }, "expired-id": { "technologies": [ "Decentralised identifier (DID) framework", "Document verification engine", "Biometric identity anchor" ], "technologyProperties": { "identityModel": "DID with biometric fallback for expired docs", "verificationComplexity": "medium", "bootstrapRequirement": "Document + biometric capture" } }, "undocumented": { "technologies": [ "Self-sovereign identity (SSI) platform", "Biometric identity anchor", "Witness attestation protocol" ], "technologyProperties": { "identityModel": "Biometric-first SSI with community attestation", "verificationComplexity": "high", "bootstrapRequirement": "Biometric enrolment + community attestation" } }, "mixed-status": { "technologies": [ "Decentralised identifier (DID) framework", "Multi-modal identity verification", "Biometric identity anchor" ], "technologyProperties": { "identityModel": "Adaptive DID supporting ID scan + biometric + attestation", "verificationComplexity": "medium-high", "bootstrapRequirement": "Multiple enrolment pathways" } } }, "prefillFrom": null, "briefSection": "Identity protocol", "text": "What is the current identity documentation status of the target beneficiary population?", "ngoText": "What is the current identity documentation status of the target beneficiary population?" }, { "id": "registration-scale", "type": "select", "options": [ { "label": "Under 5,000 beneficiaries", "value": "small" }, { "label": "5,000\u201350,000 beneficiaries", "value": "medium" }, { "label": "50,000\u2013500,000 beneficiaries", "value": "large" }, { "label": "Over 500,000 beneficiaries", "value": "massive" } ], "propertyMapping": { "small": { "technologies": [ "Mobile registration application" ], "technologyProperties": { "scalability": "Single-instance deployment", "throughput": "Standard", "registrationModel": "Tablet-based field registration" } }, "medium": { "technologies": [ "Mobile registration application", "Cloud-anchored identity ledger" ], "technologyProperties": { "scalability": "Multi-site deployment", "throughput": "Moderate batch processing", "registrationModel": "Distributed field teams" } }, "large": { "technologies": [ "Enterprise registration platform", "Distributed identity ledger", "Batch processing engine" ], "technologyProperties": { "scalability": "High-availability cluster", "throughput": "High-volume batch + real-time", "registrationModel": "Multi-site + mobile units" } }, "massive": { "technologies": [ "Enterprise registration platform", "Sharded identity ledger", "Batch processing engine", "Registration queue management" ], "technologyProperties": { "scalability": "Horizontally scaled infrastructure", "throughput": "Ultra-high volume", "registrationModel": "Mass registration centres + mobile" } } }, "prefillFrom": null, "briefSection": "Identity protocol", "text": "What is the approximate scale of beneficiary registration needed?", "ngoText": "What is the approximate scale of beneficiary registration needed?" }, { "id": "biometric-modality", "type": "select", "options": [ { "label": "Fingerprint capture is feasible and accepted", "value": "fingerprint" }, { "label": "Iris scanning is preferred (e.g., UNHCR contexts)", "value": "iris" }, { "label": "Facial recognition is most practical", "value": "facial" }, { "label": "Multiple biometrics needed for reliability", "value": "multi-modal" }, { "label": "Biometrics are not feasible (cultural/practical barriers)", "value": "no-biometric" } ], "propertyMapping": { "fingerprint": { "technologies": [ "Fingerprint scanner hardware", "Fingerprint template engine" ], "technologyProperties": { "biometricModality": "Fingerprint", "captureDevice": "Portable USB scanner or mobile device", "templateFormat": "ISO 19794-2", "privacyModel": "On-device template extraction" } }, "iris": { "technologies": [ "Iris scanner hardware", "Iris recognition engine" ], "technologyProperties": { "biometricModality": "Iris", "captureDevice": "Handheld iris scanner", "templateFormat": "ISO 19794-6", "privacyModel": "Encrypted iris template" } }, "facial": { "technologies": [ "Facial recognition engine", "Mobile camera capture module" ], "technologyProperties": { "biometricModality": "Facial recognition", "captureDevice": "Standard mobile camera", "templateFormat": "ISO 19794-5", "privacyModel": "On-device facial embedding" } }, "multi-modal": { "technologies": [ "Multi-modal biometric platform", "Biometric fusion engine" ], "technologyProperties": { "biometricModality": "Fingerprint + iris or facial", "captureDevice": "Multi-modal capture kit", "templateFormat": "Multiple ISO standards", "privacyModel": "Fused biometric template" } }, "no-biometric": { "technologies": [ "Community attestation protocol", "Knowledge-based identity verification" ], "technologyProperties": { "biometricModality": "None \u2014 attestation-based", "captureDevice": "Mobile device only", "templateFormat": "N/A", "privacyModel": "Witness-based verification" } } }, "prefillFrom": null, "briefSection": "Biometric and capture", "text": "What biometric modalities are feasible in your operating context?", "ngoText": "What biometric modalities are feasible in your operating context?", "hidden": true }, { "id": "privacy-requirements", "type": "select", "options": [ { "label": "Standard data protection (encrypted storage, access controls)", "value": "standard" }, { "label": "Enhanced privacy (zero-knowledge proofs for verification)", "value": "zkp" }, { "label": "Maximum privacy (no central data store, beneficiary-held only)", "value": "self-sovereign" }, { "label": "Regulatory-driven (GDPR, national data protection laws apply)", "value": "regulatory" } ], "propertyMapping": { "standard": { "technologies": [ "Encrypted identity vault", "Role-based access control" ], "technologyProperties": { "privacyLevel": "Standard encryption + RBAC", "dataResidency": "Centralised encrypted store", "verificationPrivacy": "Full credential revealed to verifier" } }, "zkp": { "technologies": [ "Zero-knowledge proof verification engine", "Selective disclosure protocol" ], "technologyProperties": { "privacyLevel": "ZKP-enabled selective disclosure", "dataResidency": "Holder-side with ZK proofs", "verificationPrivacy": "Only required attributes revealed" } }, "self-sovereign": { "technologies": [ "Self-sovereign identity (SSI) platform", "Decentralised data vault", "Peer-to-peer credential exchange" ], "technologyProperties": { "privacyLevel": "Full self-sovereignty \u2014 no central store", "dataResidency": "Beneficiary device only", "verificationPrivacy": "Holder controls all disclosures" } }, "regulatory": { "technologies": [ "GDPR-compliant identity platform", "Data protection impact assessment module", "Consent management engine" ], "technologyProperties": { "privacyLevel": "Regulatory compliance (GDPR/national law)", "dataResidency": "Jurisdiction-aware storage", "verificationPrivacy": "Lawful basis required for each disclosure" } } }, "prefillFrom": null, "briefSection": "Verification and privacy", "text": "What level of privacy protection is required for beneficiary identity data?", "ngoText": "What level of privacy protection is required for beneficiary identity data?" }, { "id": "credential-portability", "type": "select", "options": [ { "label": "Single-organisation use only", "value": "single-org" }, { "label": "Shared across implementing partners in same programme", "value": "multi-partner" }, { "label": "Portable across organisations and programmes", "value": "cross-org" }, { "label": "Cross-border portability needed", "value": "cross-border" } ], "propertyMapping": { "single-org": { "technologies": [ "Verifiable credential (VC) issuance engine" ], "technologyProperties": { "portabilityScope": "Internal only", "interoperability": "Proprietary format acceptable", "credentialFormat": "Organisation-specific VC" } }, "multi-partner": { "technologies": [ "Verifiable credential (VC) issuance engine", "Shared credential schema registry" ], "technologyProperties": { "portabilityScope": "Partner consortium", "interoperability": "Shared schemas required", "credentialFormat": "W3C Verifiable Credential" } }, "cross-org": { "technologies": [ "W3C Verifiable Credential platform", "DID resolver network", "Credential schema registry" ], "technologyProperties": { "portabilityScope": "Multi-organisation", "interoperability": "W3C VC + DID standards", "credentialFormat": "W3C VC with JSON-LD" } }, "cross-border": { "technologies": [ "W3C Verifiable Credential platform", "Cross-border DID resolution", "Credential translation layer" ], "technologyProperties": { "portabilityScope": "International", "interoperability": "W3C VC + eIDAS alignment", "credentialFormat": "W3C VC with multi-language support" } } }, "prefillFrom": null, "briefSection": "Interoperability", "text": "Do beneficiary credentials need to be portable across organisations or borders?", "ngoText": "Do beneficiary credentials need to be portable across organisations or borders?" }, { "id": "holder-device", "type": "select", "options": [ { "label": "Smartphones with reliable connectivity", "value": "smartphone" }, { "label": "Feature phones (SMS/USSD only)", "value": "feature-phone" }, { "label": "No personal device, rely on printed/card credentials", "value": "no-device" }, { "label": "Mixed: some smartphones, many without devices", "value": "mixed" } ], "propertyMapping": { "smartphone": { "technologies": [ "Mobile identity wallet application" ], "technologyProperties": { "holderInterface": "Native mobile wallet app", "credentialStorage": "Secure enclave on device", "backupRecovery": "Cloud backup with encryption" } }, "feature-phone": { "technologies": [ "SMS-based credential retrieval", "USSD identity menu" ], "technologyProperties": { "holderInterface": "USSD/SMS credential access", "credentialStorage": "Server-side with SMS verification", "backupRecovery": "PIN + phone number recovery" } }, "no-device": { "technologies": [ "QR-code identity card", "NFC-enabled smart card", "Paper credential with verification code" ], "technologyProperties": { "holderInterface": "Physical card or paper credential", "credentialStorage": "Printed QR/NFC card", "backupRecovery": "Reissue from registration authority" } }, "mixed": { "technologies": [ "Multi-channel identity platform", "Mobile wallet + card fallback" ], "technologyProperties": { "holderInterface": "App + card + SMS fallback", "credentialStorage": "Adaptive \u2014 device or card", "backupRecovery": "Multi-channel recovery" } } }, "prefillFrom": null, "briefSection": "Holder experience", "text": "What devices do beneficiaries have access to for holding their identity credentials?", "ngoText": "What devices do beneficiaries have access to for holding their identity credentials?" }, { "id": "deduplication-approach", "type": "select", "options": [ { "label": "Biometric deduplication (fingerprint/iris matching)", "value": "biometric-dedup" }, { "label": "Demographic matching (name, DOB, location)", "value": "demographic" }, { "label": "Privacy-preserving deduplication (hashed matching)", "value": "privacy-preserving" }, { "label": "No deduplication needed, single-site registration", "value": "none" } ], "propertyMapping": { "biometric-dedup": { "technologies": [ "Biometric deduplication engine", "1:N biometric matching service" ], "technologyProperties": { "deduplicationMethod": "Biometric 1:N matching", "accuracy": "High (>99.5%)", "privacyImpact": "Requires centralised biometric gallery" } }, "demographic": { "technologies": [ "Probabilistic record linkage engine", "Fuzzy matching algorithm" ], "technologyProperties": { "deduplicationMethod": "Demographic probabilistic matching", "accuracy": "Medium (85-95%)", "privacyImpact": "Requires shared demographic data" } }, "privacy-preserving": { "technologies": [ "Privacy-preserving record linkage", "Secure multi-party computation module" ], "technologyProperties": { "deduplicationMethod": "Cryptographic hash matching", "accuracy": "Medium-high (90-97%)", "privacyImpact": "No raw data shared between parties" } }, "none": { "technologies": [ "Single-site registration platform" ], "technologyProperties": { "deduplicationMethod": "Not required", "accuracy": "N/A", "privacyImpact": "None" } } }, "prefillFrom": null, "briefSection": "Identity protocol", "text": "What deduplication rate is acceptable for duplicate registrations across sites and programmes?", "ngoText": "What deduplication rate is acceptable for duplicate registrations across sites and programmes?" }, { "id": "consent-model", "type": "select", "options": [ { "label": "Opt-in consent at registration with blanket programme use", "value": "opt-in-blanket" }, { "label": "Granular consent: beneficiaries choose what data to share with whom", "value": "granular" }, { "label": "Guardian/proxy consent (for children or incapacitated individuals)", "value": "guardian" }, { "label": "Community consent model (collective consent for group registration)", "value": "community" } ], "propertyMapping": { "opt-in-blanket": { "technologies": [ "Digital consent capture module" ], "technologyProperties": { "consentModel": "Single opt-in at registration", "consentGranularity": "Programme-wide", "withdrawalMechanism": "Full withdrawal only" } }, "granular": { "technologies": [ "Granular consent management engine", "Consent ledger" ], "technologyProperties": { "consentModel": "Per-field, per-recipient consent", "consentGranularity": "Individual data element level", "withdrawalMechanism": "Selective withdrawal per recipient" } }, "guardian": { "technologies": [ "Guardian consent protocol", "Age-appropriate consent workflow" ], "technologyProperties": { "consentModel": "Guardian/proxy consent with child assent", "consentGranularity": "Programme-level with guardian override", "withdrawalMechanism": "Guardian-initiated or age-triggered transfer" } }, "community": { "technologies": [ "Community consent framework", "Group registration consent module" ], "technologyProperties": { "consentModel": "Community representative consent", "consentGranularity": "Group-level with individual opt-out", "withdrawalMechanism": "Individual opt-out from group consent" } } }, "prefillFrom": null, "briefSection": "Consent and governance", "text": "What consent model is required for beneficiary data collection and sharing?", "ngoText": "What consent model is required for beneficiary data collection and sharing?" }, { "id": "credential-types", "type": "select", "options": [ { "label": "Basic identity (name, photo, biometric anchor)", "value": "basic-id" }, { "label": "Identity + programme enrolment proof", "value": "id-plus-enrolment" }, { "label": "Full verifiable identity with multiple attributes", "value": "full-vc" }, { "label": "Foundational identity (government-grade, civil registry pathway)", "value": "foundational" } ], "propertyMapping": { "basic-id": { "technologies": [ "Basic verifiable credential issuance" ], "technologyProperties": { "credentialScope": "Name, photo, biometric hash", "credentialLifecycle": "Issue \u2192 verify", "revocability": "Issuer-revocable" } }, "id-plus-enrolment": { "technologies": [ "Verifiable credential issuance engine", "Programme enrolment credential" ], "technologyProperties": { "credentialScope": "Identity + programme membership", "credentialLifecycle": "Issue \u2192 use \u2192 renew", "revocability": "Programme-exit triggers revocation" } }, "full-vc": { "technologies": [ "W3C Verifiable Credential platform", "Multi-attribute credential schema", "Credential status registry" ], "technologyProperties": { "credentialScope": "Full identity with demographic, biometric, programme attributes", "credentialLifecycle": "Issue \u2192 present \u2192 verify \u2192 revoke \u2192 renew", "revocability": "Granular attribute-level revocation" } }, "foundational": { "technologies": [ "Civil registry integration layer", "Government credential bridge", "W3C Verifiable Credential platform" ], "technologyProperties": { "credentialScope": "Government-grade identity for civil registration", "credentialLifecycle": "Issue \u2192 verify \u2192 government recognition pathway", "revocability": "Government authority revocation" } } }, "prefillFrom": null, "briefSection": "Credential issuance", "text": "What types of identity documents do your beneficiaries typically have?", "ngoText": "What types of identity documents do your beneficiaries typically have?" }, { "id": "verification-frequency", "type": "select", "options": [ { "label": "One-time registration, rarely re-verified", "value": "one-time" }, { "label": "Periodic verification (monthly/quarterly distributions)", "value": "periodic" }, { "label": "Frequent verification (every service interaction)", "value": "frequent" }, { "label": "Continuous verification (real-time access control)", "value": "continuous" } ], "propertyMapping": { "one-time": { "technologies": [ "Registration verification module" ], "technologyProperties": { "verificationFrequency": "At registration only", "verificationSpeed": "Not time-critical", "cachingStrategy": "Full credential cache" } }, "periodic": { "technologies": [ "Scheduled verification engine", "Batch verification processor" ], "technologyProperties": { "verificationFrequency": "Monthly/quarterly", "verificationSpeed": "Within distribution window", "cachingStrategy": "Cached with periodic refresh" } }, "frequent": { "technologies": [ "Real-time credential verification API", "QR/NFC verification scanner" ], "technologyProperties": { "verificationFrequency": "Per-interaction", "verificationSpeed": "Sub-5-second response", "cachingStrategy": "Short-lived cache" } }, "continuous": { "technologies": [ "Continuous authentication platform", "Presence verification engine" ], "technologyProperties": { "verificationFrequency": "Real-time continuous", "verificationSpeed": "Sub-second", "cachingStrategy": "No caching \u2014 live verification" } } }, "prefillFrom": null, "briefSection": "Verification and privacy", "text": "How often does verification need to happen?", "ngoText": "How often does verification need to happen?" }, { "id": "government-integration", "type": "select", "options": [ { "label": "No government integration needed, standalone humanitarian system", "value": "standalone" }, { "label": "One-way feed to government registry (e.g., birth registration)", "value": "one-way" }, { "label": "Two-way integration with national identity systems", "value": "two-way" }, { "label": "Government-led system with humanitarian layer", "value": "gov-led" } ], "propertyMapping": { "standalone": { "technologies": [ "Standalone identity platform" ], "technologyProperties": { "governmentIntegration": "None", "interoperabilityStandard": "Humanitarian standards only", "dataSharing": "Within humanitarian ecosystem" } }, "one-way": { "technologies": [ "Government registry API connection", "Data export module" ], "technologyProperties": { "governmentIntegration": "One-way data push", "interoperabilityStandard": "Government API compliance", "dataSharing": "Humanitarian \u2192 government" } }, "two-way": { "technologies": [ "Government identity bridge", "Two-way data updates", "National ID verification API" ], "technologyProperties": { "governmentIntegration": "Full bidirectional", "interoperabilityStandard": "National ID standards + W3C VC", "dataSharing": "Bidirectional with consent" } }, "gov-led": { "technologies": [ "Government identity platform extension", "Humanitarian access layer" ], "technologyProperties": { "governmentIntegration": "Government-hosted", "interoperabilityStandard": "National standards", "dataSharing": "Government controls data flow" } } }, "prefillFrom": null, "briefSection": "Interoperability", "text": "Does your system need to connect to government identity or registry systems?", "ngoText": "Does your system need to connect to government identity or registry systems?" }, { "id": "reporting-needs", "type": "select", "options": [ { "label": "Basic registration statistics (totals, demographics)", "value": "basic-stats" }, { "label": "Donor reporting with anonymised identity metrics", "value": "donor-reporting" }, { "label": "Full audit trail of all identity operations", "value": "full-audit" }, { "label": "Regulatory compliance reporting (data protection authority)", "value": "regulatory" } ], "propertyMapping": { "basic-stats": { "technologies": [ "Registration analytics dashboard" ], "technologyProperties": { "reportingScope": "Aggregate statistics", "auditDepth": "Summary only", "reportingFrequency": "On-demand" } }, "donor-reporting": { "technologies": [ "Anonymised reporting engine", "Donor dashboard module" ], "technologyProperties": { "reportingScope": "Anonymised programme metrics", "auditDepth": "Aggregated with anonymisation", "reportingFrequency": "Monthly/quarterly" } }, "full-audit": { "technologies": [ "Immutable audit trail", "Identity operation logger", "Audit query interface" ], "technologyProperties": { "reportingScope": "Complete identity lifecycle audit", "auditDepth": "Every operation logged immutably", "reportingFrequency": "Real-time + periodic" } }, "regulatory": { "technologies": [ "Regulatory compliance reporting module", "Data protection audit trail", "Breach notification engine" ], "technologyProperties": { "reportingScope": "Regulatory compliance evidence", "auditDepth": "Full compliance audit trail", "reportingFrequency": "As required by regulation" } } }, "prefillFrom": null, "briefSection": "Reporting and audit", "text": "What identity programme reporting is needed?", "ngoText": "What identity programme reporting is needed?" }, { "id": "sq-UC-B-024-001", "type": "single-select", "options": [ { "value": "local-device-storage-sync-later", "label": "Local device storage, sync later" }, { "value": "paper-backup-digitise", "label": "Paper backup, digitise later" }, { "value": "mesh-network", "label": "Mesh network synchronisation" }, { "value": "satellite-upload", "label": "Satellite upload" }, { "value": "pre-cached-registry", "label": "Pre-cached registry" } ], "propertyMapping": { "local-device-storage-sync-later": { "technologies": [ "local-storage", "sync-engine" ], "technologyProperties": {} }, "paper-backup-digitise": { "technologies": [ "paper-forms", "ocr-digitization" ], "technologyProperties": {} }, "mesh-network": { "technologies": [ "mesh-networking", "peer-sync" ], "technologyProperties": {} }, "satellite-upload": { "technologies": [ "satellite-modem", "remote-sync" ], "technologyProperties": {} }, "pre-cached-registry": { "technologies": [ "offline-cache", "registry-replica" ], "technologyProperties": {} } }, "briefSection": "operations", "text": "What percentage of beneficiary registrations typically happen offline?", "ngoText": "What percentage of beneficiary registrations typically happen offline?" }, { "id": "holder-access-method", "type": "select", "options": [ { "label": "Mobile wallet app (smartphone required)", "value": "mobile-wallet" }, { "label": "Physical smart card with NFC or QR code", "value": "smart-card" }, { "label": "SMS/USSD-based access (feature phone compatible)", "value": "sms-ussd" }, { "label": "Hybrid: mobile app for those with smartphones, card for others", "value": "hybrid" } ], "propertyMapping": { "mobile-wallet": { "technologies": [ "Mobile holder app", "Credential wallet SDK", "Biometric authentication module" ], "technologyProperties": { "holderDevice": "Smartphone (Android/iOS)", "authMethod": "PIN + biometric", "offlineAccess": "Cached credentials available offline" } }, "smart-card": { "technologies": [ "Smart card holder platform", "Card provisioning service", "Card reader/NFC verifier" ], "technologyProperties": { "holderDevice": "Physical smart card", "authMethod": "Card + PIN", "offlineAccess": "Card-based presentation works offline" } }, "sms-ussd": { "technologies": [ "SMS/USSD holder interface", "Feature phone credential access", "OTP verification service" ], "technologyProperties": { "holderDevice": "Feature phone (SMS/USSD)", "authMethod": "OTP via SMS", "offlineAccess": "Limited \u2014 requires network for SMS" } }, "hybrid": { "technologies": [ "Mobile holder app", "Smart card holder platform", "Multi-channel credential access" ], "technologyProperties": { "holderDevice": "Smartphone + physical card fallback", "authMethod": "Biometric (mobile) or PIN (card)", "offlineAccess": "Both channels support offline presentation" } } }, "prefillFrom": null, "briefSection": "Credential access", "text": "How will individuals access and present their credentials or identity documents?", "ngoText": "How will individuals access and present their credentials or identity documents?" }, { "id": "beneficiary-choice", "label": "How will beneficiaries exercise choice in how they receive and use this service?", "type": "select", "briefSection": "Holder experience", "options": [ { "label": "Beneficiaries choose between delivery methods (cash, voucher, mobile money, direct)", "value": "delivery-choice" }, { "label": "Beneficiaries choose preferred merchants or service points", "value": "merchant-choice" }, { "label": "Beneficiaries control their own data sharing preferences", "value": "data-choice" }, { "label": "Multiple choice dimensions (delivery + merchant + data)", "value": "full-choice" }, { "label": "Limited choice: programme constraints determine delivery", "value": "limited" } ], "propertyMapping": { "delivery-choice": { "technologies": [], "technologyProperties": { "beneficiaryChoice": "Delivery method choice", "dignityDesign": "Beneficiaries select preferred receipt method" } }, "merchant-choice": { "technologies": [], "technologyProperties": { "beneficiaryChoice": "Merchant/service point choice", "dignityDesign": "Beneficiaries select where to redeem" } }, "data-choice": { "technologies": [], "technologyProperties": { "beneficiaryChoice": "Data sharing choice", "dignityDesign": "Beneficiaries control personal data sharing" } }, "full-choice": { "technologies": [], "technologyProperties": { "beneficiaryChoice": "Multi-dimensional choice", "dignityDesign": "Full beneficiary agency across delivery, merchant, and data" } }, "limited": { "technologies": [], "technologyProperties": { "beneficiaryChoice": "Limited by programme design", "dignityDesign": "Programme constraints; beneficiary informed of reasons" } } }, "text": "How will beneficiaries exercise choice in how they receive and use this service?" } ], "complexityFactors": { "relationships": 4, "operationalChange": 4, "dataCompliance": 5 }, "securityTier": "C", "suggestedCriteria": [ { "id": "SC-IDENTITY-PRIVACY", "name": "Identity Privacy Strength", "description": "The provider can prove identity attributes (eligibility, status) without revealing the underlying personal data. Critical for refugees and stateless persons.", "weight": 0.35, "ratingGuide": { "5": "Zero-knowledge proofs verify identity claims without revealing any personal data. Mathematically provable non-disclosure.", "4": "Multi-party computation splits identity verification across parties \u2014 no single party sees full identity.", "3": "Encrypted identity with trusted execution environment. Hardware-protected but not mathematically provable.", "2": "Encrypted storage with role-based access controls. Identity data accessible to authorised parties.", "1": "Centralised identity database with basic access controls. All data visible to system operators." } }, { "id": "SC-NO-DEANON", "name": "De-anonymisation Protection", "description": "This looks at whether authorities or hostile actors can compel the system to reveal refugee identities. For populations fleeing persecution, protocol-level privacy with no backdoor is essential.", "weight": 0.25, "ratingGuide": { "5": "Protocol-level privacy \u2014 no entity, including the provider, can de-anonymise individuals. No master key exists.", "4": "Privacy by default. De-anonymisation requires the individual's active, informed consent.", "3": "Provider holds encryption keys but has strong legal protections and published transparency reports.", "2": "Built-in identity verification layer (e.g. KYC) that could be compelled by government order.", "1": "Provider or third party can access identity data under legal compulsion without individual's knowledge." } }, { "id": "SC-FIELD-ENROL", "name": "Offline Enrolment & Verification", "description": "Registration and identity verification can happen in camps and field settings without reliable internet. Refugee registration often occurs in connectivity-constrained environments.", "weight": 0.2, "ratingGuide": { "5": "Full offline enrolment with portable proof generation. Sync when connectivity available. Works in fully disconnected camps.", "4": "Offline enrolment with periodic batch sync. Tolerates multi-day connectivity outages.", "3": "Requires periodic connectivity but handles intermittent outages gracefully. Queue-and-sync model.", "2": "Needs reliable internet for enrolment but not constant connection. Fails gracefully on dropout.", "1": "Requires constant connectivity for both enrolment and verification. Unusable in camp settings." } }, { "id": "SC-BIOMETRIC-INCLUSIVE", "name": "Biometric Inclusivity & Security", "description": "Does the biometric capture work across diverse populations including children, elderly, and people with disabilities? Are biometric templates stored securely?", "weight": 0.1, "ratingGuide": { "5": "Multiple biometric modalities (fingerprint, iris, face). Handles children, elderly, manual labourers. Templates encrypted and never stored raw.", "4": "Two or more modalities with good demographic coverage. Encrypted template storage.", "3": "Single modality (e.g. fingerprint only) with fallback for edge cases. Encrypted storage.", "2": "Single modality, limited demographic coverage. Some edge cases unsupported.", "1": "Basic biometric capture with poor inclusivity. Raw biometric data stored or transmitted." } }, { "id": "SC-CROSS-ORG-VERIFY", "name": "Cross-Organisation Verification", "description": "Can multiple agencies (UNHCR, WFP, UNICEF, local partners) verify a beneficiary's identity without sharing a centralised database?", "weight": 0.1, "ratingGuide": { "5": "Decentralised verification \u2014 each agency verifies independently using portable credentials. No shared database required.", "4": "Federated verification with minimal data sharing. Agencies see only what they need.", "3": "Shared verification service but agencies maintain separate records. Some data centralisation.", "2": "Agencies must query a central registry for verification. Single point of failure.", "1": "Full database sharing required. All agencies see all data." } } ], "procurement": { "marketMaturity": "emerging", "primaryMode": "integrator-led", "alternativeModes": [ "tender" ], "reasoning": "Refugee registration platforms exist (run by UN agencies and partners) but integration is complex.", "exampleProductCategories": [ "refugee-registration-platform", "digital-identity-rails" ], "partnerChannels": [], "lastReviewed": "2026-05-01" } }, { "id": "UC-B-025", "name": "Birth registration for children born in displacement", "category": "B", "subcategory": "Identity Registration", "description": "Record the births of children born in displacement and give families a certificate that services and authorities in other places will accept.", "bCriteria": [ "B1", "B3", "B6" ], "requiredComponents": [ { "component": "identity-protocol", "description": "Birth record protocol" }, { "component": "credential-issuance", "description": "Birth certificate issuance" }, { "component": "verification-mechanism", "description": "Proof of birth registration" }, { "component": "record-keeping-platform", "description": "Immutable birth records" }, { "component": "biometric-capture", "description": "Biometric capture of infant" } ], "conditionalComponents": [ { "component": "identity-verification", "condition": "If parental identity verification needed" }, { "component": "interoperability-layer", "condition": "If linking to national vital statistics" } ], "crossCategoryDependencies": [ "UC-B-027 if family relationship verification needed" ], "p2TriggerConditions": { "description": "Activated when P2 shows displacement settings + birth registration gaps + children born in camps", "rangeSignals": [ "displacementContext >= true", "birthsPerMonth >= 10+", "registrationCapacity <= low" ] }, "contextFieldsTemplate": [ { "field": "birthsExpected", "source": "P2 beneficiary demographics", "description": "Anticipated births" }, { "field": "countryContext", "source": "P0 countries", "description": "Vital registration environment" }, { "field": "parentIdentity", "source": "P2 registration practices", "description": "Parental ID availability" }, { "field": "recognitionGoal", "source": "P2 programme objectives", "description": "Official recognition pathway" } ], "implementationComplexity": "high", "examples": { "note": "UNHCR birth registration programmes", "references": [ { "name": "UNICEF Birth Registration Programme", "url": "https://www.unicef.org/protection/birth-registration", "solved": "Digital birth registration for children in displacement, feeding into national CRVS systems" }, { "name": "Kiva Protocol (Sierra Leone)", "url": "https://www.kiva.org/protocol", "solved": "National digital identity infrastructure in Sierra Leone, including birth registration" }, { "name": "AID:Tech Birth Registration Pilot", "url": "https://aid.technology/", "solved": "Blockchain-based birth registration for children in refugee camps" } ] }, "solutionQuestions": [ { "id": "birth-registration-context", "type": "select", "options": [ { "label": "Government civil registry is functional and accessible", "value": "functional-registry" }, { "label": "Civil registry exists but is inaccessible to displaced populations", "value": "inaccessible-registry" }, { "label": "Civil registry is non-functional or destroyed (conflict/disaster)", "value": "non-functional" }, { "label": "No formal civil registry system exists", "value": "no-registry" } ], "propertyMapping": { "functional-registry": { "technologies": [ "Civil registry API connection", "Birth record credential issuance" ], "technologyProperties": { "registryIntegration": "Direct API to government registry", "legalRecognition": "Immediate legal recognition", "dataFlow": "Humanitarian \u2192 government registry" } }, "inaccessible-registry": { "technologies": [ "Interim birth record platform", "Government registry bridge", "Advocacy documentation module" ], "technologyProperties": { "registryIntegration": "Parallel system with future bridge", "legalRecognition": "Interim record pending recognition", "dataFlow": "Humanitarian record \u2192 future government transfer" } }, "non-functional": { "technologies": [ "Standalone birth record ledger", "Community attestation protocol", "Evidence preservation engine" ], "technologyProperties": { "registryIntegration": "Standalone with evidence preservation", "legalRecognition": "Humanitarian attestation for future claims", "dataFlow": "Self-contained with export capability" } }, "no-registry": { "technologies": [ "Foundational birth record platform", "Community witness attestation", "International recognition module" ], "technologyProperties": { "registryIntegration": "None \u2014 foundational system", "legalRecognition": "Community-attested with international standards", "dataFlow": "Independent ledger with portability" } } }, "prefillFrom": null, "briefSection": "Identity protocol", "text": "What is the legal recognition environment for birth registration in your operating countries?", "ngoText": "What is the legal recognition environment for birth registration in your operating countries?" }, { "id": "birth-capture-method", "type": "select", "options": [ { "label": "Health facility-based registration (births in clinics/hospitals)", "value": "facility-based" }, { "label": "Community health worker reporting (home births)", "value": "community-hw" }, { "label": "Mobile registration teams visiting communities", "value": "mobile-teams" }, { "label": "Mixed: facility + community + mobile registration", "value": "mixed" } ], "propertyMapping": { "facility-based": { "technologies": [ "Health facility birth registration module", "EHR integration layer" ], "technologyProperties": { "capturePoint": "Health facility", "captureAgent": "Health staff", "evidenceType": "Clinical record + witness" } }, "community-hw": { "technologies": [ "Community health worker mobile app", "Offline birth registration module" ], "technologyProperties": { "capturePoint": "Community/home", "captureAgent": "Community health worker", "evidenceType": "CHW attestation + family witness" } }, "mobile-teams": { "technologies": [ "Mobile registration toolkit", "Portable biometric capture device" ], "technologyProperties": { "capturePoint": "Mobile registration point", "captureAgent": "Registration team", "evidenceType": "Team attestation + biometric" } }, "mixed": { "technologies": [ "Multi-channel birth registration platform", "Offline-capable mobile registration", "Health facility connection" ], "technologyProperties": { "capturePoint": "Multiple \u2014 facility + community + mobile", "captureAgent": "Health staff + CHW + registration teams", "evidenceType": "Adaptive \u2014 clinical or community attestation" } } }, "prefillFrom": null, "briefSection": "Credential issuance", "text": "How are birth events currently captured and documented in your operating environment?", "ngoText": "How are birth events currently captured and documented in your operating environment?" }, { "id": "infant-biometric", "type": "select", "options": [ { "label": "Parental biometric link (identity anchored to mother/father)", "value": "parental-link" }, { "label": "Infant footprint capture", "value": "footprint" }, { "label": "Photo-based identity with parental attestation", "value": "photo-attestation" }, { "label": "No biometric, document-based registration only", "value": "document-only" } ], "propertyMapping": { "parental-link": { "technologies": [ "Parent-child identity linkage protocol", "Parental biometric verification" ], "technologyProperties": { "infantIdentification": "Linked to parental biometric", "reliability": "High (dependent on parent ID quality)", "ageTransition": "Transfer to child biometric at age threshold" } }, "footprint": { "technologies": [ "Infant footprint capture device", "Footprint template engine" ], "technologyProperties": { "infantIdentification": "Infant plantar footprint", "reliability": "Medium (grows/changes quickly)", "ageTransition": "Re-enrolment with fingerprint at age 5+" } }, "photo-attestation": { "technologies": [ "Photo identity capture", "Parental attestation protocol" ], "technologyProperties": { "infantIdentification": "Facial photo + parental witness", "reliability": "Medium-low (infant appearance changes)", "ageTransition": "Photo refresh + biometric addition" } }, "document-only": { "technologies": [ "Document-based birth record system" ], "technologyProperties": { "infantIdentification": "Paper-based with parental data", "reliability": "Low (no biometric anchor)", "ageTransition": "Biometric addition at first contact" } } }, "prefillFrom": null, "briefSection": "Biometric and capture", "text": "What identification method will be used for newborns?", "ngoText": "What identification method will be used for newborns?" }, { "id": "parental-identity", "type": "select", "options": [ { "label": "Most parents have verified identity documents", "value": "verified-parents" }, { "label": "Parents have humanitarian registration but no government ID", "value": "humanitarian-id" }, { "label": "Many parents are undocumented themselves", "value": "undocumented-parents" }, { "label": "Mixed: some documented, some not", "value": "mixed" } ], "propertyMapping": { "verified-parents": { "technologies": [ "Parent identity verification module" ], "technologyProperties": { "parentalVerification": "Government ID scan + biometric match", "parentalIdGap": "Low", "dependencyOnB025": "Minimal" } }, "humanitarian-id": { "technologies": [ "Humanitarian ID verification bridge", "Cross-reference beneficiary registry" ], "technologyProperties": { "parentalVerification": "Humanitarian registration lookup", "parentalIdGap": "Medium", "dependencyOnB025": "High \u2014 use existing registration" } }, "undocumented-parents": { "technologies": [ "Combined parent-child registration workflow", "Community attestation for parents" ], "technologyProperties": { "parentalVerification": "Community witness + biometric capture", "parentalIdGap": "High \u2014 requires parallel parent registration", "dependencyOnB025": "Critical \u2014 enrol parents simultaneously" } }, "mixed": { "technologies": [ "Adaptive parental verification module", "Multi-pathway parent identity" ], "technologyProperties": { "parentalVerification": "Adaptive \u2014 gov ID / humanitarian ID / attestation", "parentalIdGap": "Variable", "dependencyOnB025": "Integrated workflow recommended" } } }, "prefillFrom": null, "briefSection": "Identity protocol", "text": "What is the expected parental identity documentation situation?", "ngoText": "What is the expected parental identity documentation situation?" }, { "id": "birth-cert-format", "type": "select", "options": [ { "label": "Digital verifiable credential only", "value": "digital-only" }, { "label": "Digital credential + printed certificate", "value": "digital-print" }, { "label": "Printed certificate with QR verification code", "value": "print-qr" }, { "label": "Government-format certificate (matching national template)", "value": "gov-format" } ], "propertyMapping": { "digital-only": { "technologies": [ "Digital birth certificate credential", "Mobile credential wallet" ], "technologyProperties": { "certificateFormat": "W3C Verifiable Credential", "physicalOutput": "None", "verificationMethod": "Digital presentation" } }, "digital-print": { "technologies": [ "Digital birth certificate credential", "Certificate printing module", "Mobile credential wallet" ], "technologyProperties": { "certificateFormat": "Digital VC + printed copy", "physicalOutput": "Printed certificate with QR code", "verificationMethod": "Digital or QR scan" } }, "print-qr": { "technologies": [ "Certificate printing module", "QR code verification system" ], "technologyProperties": { "certificateFormat": "Printed with embedded QR", "physicalOutput": "Physical certificate", "verificationMethod": "QR code scan" } }, "gov-format": { "technologies": [ "Government template certificate engine", "Official format compliance module" ], "technologyProperties": { "certificateFormat": "National government template", "physicalOutput": "Official-format printed certificate", "verificationMethod": "Government verification channel" } } }, "prefillFrom": null, "briefSection": "Credential issuance", "text": "What birth certificate format does your operating environment require?", "ngoText": "What birth certificate format does your operating environment require?" }, { "id": "birth-privacy", "type": "select", "options": [ { "label": "Standard access control (role-based, encrypted)", "value": "standard" }, { "label": "Enhanced child protection (restricted access, anonymised)", "value": "child-protection" }, { "label": "Maximum privacy (parental consent for every access)", "value": "max-privacy" } ], "propertyMapping": { "standard": { "technologies": [ "Encrypted record store", "Role-based access control" ], "technologyProperties": { "privacyLevel": "Standard RBAC + encryption", "childProtection": "Basic access controls", "consentRequirement": "Registration consent covers all use" } }, "child-protection": { "technologies": [ "Child-sensitive data vault", "Anonymised analytics layer", "Access audit trail" ], "technologyProperties": { "privacyLevel": "Enhanced child protection protocols", "childProtection": "Restricted access + anonymisation", "consentRequirement": "Parental consent with child-specific safeguards" } }, "max-privacy": { "technologies": [ "Parental consent gateway", "Zero-knowledge age/identity verification", "Minimal disclosure protocol" ], "technologyProperties": { "privacyLevel": "Maximum \u2014 parental consent gateway", "childProtection": "Full parental control", "consentRequirement": "Per-access parental authorisation" } } }, "prefillFrom": null, "briefSection": "Consent and governance", "text": "What privacy protections are needed for birth records?", "ngoText": "What privacy protections are needed for birth records?" }, { "id": "vital-stats-integration", "type": "select", "options": [ { "label": "Yes, direct integration with national vital statistics system", "value": "direct-integration" }, { "label": "Yes, but through an intermediary (UNICEF, WHO)", "value": "intermediary" }, { "label": "Not currently, design for future integration", "value": "future-ready" }, { "label": "No, standalone humanitarian record only", "value": "standalone" } ], "propertyMapping": { "direct-integration": { "technologies": [ "National vital statistics API connection", "CRVS data export module" ], "technologyProperties": { "statsIntegration": "Direct API to national CRVS", "dataStandard": "National vital statistics format", "reportingCadence": "Real-time or daily batch" } }, "intermediary": { "technologies": [ "UNICEF/WHO data reporting module", "Standardised vital statistics export" ], "technologyProperties": { "statsIntegration": "Through UNICEF/WHO reporting", "dataStandard": "WHO vital registration standard", "reportingCadence": "Monthly/quarterly" } }, "future-ready": { "technologies": [ "Standards-compliant data export", "CRVS-ready data schema" ], "technologyProperties": { "statsIntegration": "Future-ready with export capability", "dataStandard": "CRVS-compatible schema", "reportingCadence": "On-demand export" } }, "standalone": { "technologies": [ "Internal reporting module" ], "technologyProperties": { "statsIntegration": "None", "dataStandard": "Internal format", "reportingCadence": "Internal only" } } }, "prefillFrom": null, "briefSection": "Interoperability", "text": "Does birth registration need to feed into national vital statistics?", "ngoText": "Does birth registration need to feed into national vital statistics?" }, { "id": "birth-connectivity", "type": "select", "options": [ { "label": "Reliable internet at all registration points", "value": "connected" }, { "label": "Intermittent: needs offline capability with sync", "value": "intermittent" }, { "label": "Fully offline: remote areas with no connectivity", "value": "offline" }, { "label": "Mixed: facilities connected, community sites offline", "value": "mixed" } ], "propertyMapping": { "connected": { "technologies": [ "Cloud-hosted registration platform" ], "technologyProperties": { "connectivity": "Online", "offlineCapability": "Not required", "syncModel": "Real-time" } }, "intermittent": { "technologies": [ "Offline-first registration module", "Sync queue manager" ], "technologyProperties": { "connectivity": "Intermittent", "offlineCapability": "Required", "syncModel": "Store-and-forward" } }, "offline": { "technologies": [ "Fully offline registration toolkit", "SD-card data transfer module" ], "technologyProperties": { "connectivity": "None at point of registration", "offlineCapability": "Full offline workflow", "syncModel": "Physical media or periodic batch upload" } }, "mixed": { "technologies": [ "Adaptive registration platform", "Offline-capable mobile app" ], "technologyProperties": { "connectivity": "Mixed", "offlineCapability": "Required for community sites", "syncModel": "Adaptive \u2014 real-time or queued" } } }, "prefillFrom": null, "briefSection": "Infrastructure requirements", "text": "What connectivity is available at birth registration points?", "ngoText": "What connectivity is available at birth registration points?" }, { "id": "birth-reporting", "type": "select", "options": [ { "label": "Basic counts and demographics for programme reporting", "value": "basic" }, { "label": "Detailed analytics with gender, location, age disaggregation", "value": "detailed" }, { "label": "Donor accountability reporting with anonymised data", "value": "donor" }, { "label": "Full audit trail for regulatory compliance", "value": "full-audit" } ], "propertyMapping": { "basic": { "technologies": [ "Basic reporting dashboard" ], "technologyProperties": { "reportingLevel": "Aggregate counts", "disaggregation": "Basic (gender, location)", "auditTrail": "Minimal" } }, "detailed": { "technologies": [ "Analytics engine", "Disaggregated reporting module" ], "technologyProperties": { "reportingLevel": "Detailed disaggregated", "disaggregation": "Gender, location, age, nationality, disability", "auditTrail": "Standard" } }, "donor": { "technologies": [ "Anonymised donor reporting engine", "Impact metrics dashboard" ], "technologyProperties": { "reportingLevel": "Anonymised programme metrics", "disaggregation": "Anonymised disaggregation", "auditTrail": "Donor-grade audit" } }, "full-audit": { "technologies": [ "Immutable audit trail", "Regulatory compliance reporting" ], "technologyProperties": { "reportingLevel": "Complete audit trail", "disaggregation": "Full with privacy controls", "auditTrail": "Every operation logged" } } }, "prefillFrom": null, "briefSection": "Reporting and audit", "text": "What reporting is needed for the birth registration programme?", "ngoText": "What reporting is needed for the birth registration programme?" }, { "id": "beneficiary-choice", "label": "How will beneficiaries exercise choice in how they receive and use this service?", "type": "select", "briefSection": "Holder experience", "options": [ { "label": "Beneficiaries choose between delivery methods (cash, voucher, mobile money, direct)", "value": "delivery-choice" }, { "label": "Beneficiaries choose preferred merchants or service points", "value": "merchant-choice" }, { "label": "Beneficiaries control their own data sharing preferences", "value": "data-choice" }, { "label": "Multiple choice dimensions (delivery + merchant + data)", "value": "full-choice" }, { "label": "Limited choice: programme constraints determine delivery", "value": "limited" } ], "propertyMapping": { "delivery-choice": { "technologies": [], "technologyProperties": { "beneficiaryChoice": "Delivery method choice", "dignityDesign": "Beneficiaries select preferred receipt method" } }, "merchant-choice": { "technologies": [], "technologyProperties": { "beneficiaryChoice": "Merchant/service point choice", "dignityDesign": "Beneficiaries select where to redeem" } }, "data-choice": { "technologies": [], "technologyProperties": { "beneficiaryChoice": "Data sharing choice", "dignityDesign": "Beneficiaries control personal data sharing" } }, "full-choice": { "technologies": [], "technologyProperties": { "beneficiaryChoice": "Multi-dimensional choice", "dignityDesign": "Full beneficiary agency across delivery, merchant, and data" } }, "limited": { "technologies": [], "technologyProperties": { "beneficiaryChoice": "Limited by programme design", "dignityDesign": "Programme constraints; beneficiary informed of reasons" } } }, "text": "How will beneficiaries exercise choice in how they receive and use this service?" } ], "complexityFactors": { "relationships": 4, "operationalChange": 3, "dataCompliance": 5 }, "securityTier": "C", "suggestedCriteria": [ { "id": "SC-CHILD-PRIVACY", "name": "Child Identity Privacy", "description": "Children's identity records are protected from birth with privacy-preserving technology. Birth records create lifelong identity trails. Early privacy is critical.", "weight": 0.3, "ratingGuide": { "5": "Birth record creates a privacy-preserving credential from day one. Child's data never stored in cleartext. ZKP-based verification of birth facts.", "4": "Encrypted birth records with selective disclosure. Only authorised parties can verify specific attributes.", "3": "Encrypted storage with access controls. Birth data protected but accessible to system operators.", "2": "Standard database security for birth records. Data accessible to authorised staff.", "1": "Birth records stored in cleartext. Minimal access controls." } }, { "id": "SC-NO-BACKDOOR-CHILD", "name": "De-anonymisation Protection for Children", "description": "This checks whether the system can be compelled to reveal a child's identity or family relationships. Children born in displacement are particularly vulnerable to persecution and trafficking.", "weight": 0.25, "ratingGuide": { "5": "Protocol-level privacy \u2014 no entity can de-anonymise the child. No master key. Parental links protected.", "4": "Privacy by default. De-anonymisation requires guardian consent and active participation.", "3": "Provider holds keys but strong legal protections exist. Transparency reports published.", "2": "Built-in identity layer that could be compelled. Child's identity could be revealed by court order.", "1": "System operator or government can access child records without guardian knowledge." } }, { "id": "SC-LEGAL-PATHWAY", "name": "Legal Recognition Pathway", "description": "The digital birth can record translate into official civil registration. A blockchain birth record has no value if it's never recognised by a government.", "weight": 0.2, "ratingGuide": { "5": "Active government partnerships for digital-to-civil registration. Proven pathway from digital record to legal birth certificate.", "4": "Government engagement and pilot programmes for recognition. Clear roadmap to legal status.", "3": "Technical capability for government integration. Some government awareness but no formal pathway yet.", "2": "Digital record only. No government integration planned but exportable in standard formats.", "1": "Proprietary format. No path to official recognition. Digital-only with no legal standing." } }, { "id": "SC-FIELD-BIRTH-REG", "name": "Field Registration Capability", "description": "Can births be registered at point of delivery (health facilities, community health worker visits, or mobile registration teams) without connectivity?", "weight": 0.15, "ratingGuide": { "5": "Full offline registration by health workers or community teams. Automatic sync. Works on basic smartphones.", "4": "Offline registration with periodic sync. Supports multiple registration pathways (facility, mobile, community).", "3": "Requires intermittent connectivity. Registration queued during outages.", "2": "Needs reliable connection for registration. Only works at facilities with internet.", "1": "Requires constant connectivity. Registration only at connected offices." } }, { "id": "SC-PARENTAL-LINK", "name": "Parental Link Verification", "description": "Parent-child relationships can be verified without revealing both identities. Prevents family separation while protecting individual privacy.", "weight": 0.1, "ratingGuide": { "5": "Privacy-preserving family linking \u2014 prove parent-child relationship without revealing either identity. ZKP or equivalent.", "4": "Encrypted family graph with selective disclosure of relationship claims only.", "3": "Family links verified through trusted intermediary. Some data shared with verifier.", "2": "Both parent and child identities revealed during link verification.", "1": "No privacy-preserving family linking capability. Full identity exposure required." } } ], "procurement": { "marketMaturity": "nascent", "primaryMode": "integrator-led", "alternativeModes": [ "consortium" ], "reasoning": "Birth registration in displacement is emerging policy area; mostly bespoke.", "exampleProductCategories": [ "civil-registration-platform", "digital-identity-rails" ], "partnerChannels": [], "lastReviewed": "2026-05-01" } }, { "id": "UC-B-026", "name": "Death registration and inheritance documentation", "category": "B", "subcategory": "Identity Registration", "description": "Keep a reliable record of deaths, so widows and orphans can claim benefits and inheritance without waiting for disputed paperwork to be settled.", "bCriteria": [ "B1", "B3" ], "requiredComponents": [ { "component": "record-keeping-platform", "description": "Death records ledger" }, { "component": "credential-issuance", "description": "Death certificate issuance" }, { "component": "verification-mechanism", "description": "Proof of death" }, { "component": "consent-management", "description": "Inheritance consent records" } ], "conditionalComponents": [ { "component": "identity-verification", "condition": "For next of kin verification" }, { "component": "privacy-tech", "condition": "If privacy needed in inheritance matters" } ], "crossCategoryDependencies": [ "UC-B-027 for family relationships" ], "p2TriggerConditions": { "description": "Activated when P2 shows emergency/crisis settings + inheritance disputes + beneficiary changes", "rangeSignals": [ "emergencyContext >= true", "inheritanceDisputes >= true", "beneficiaryTurnover >= high" ] }, "contextFieldsTemplate": [ { "field": "deathsExpected", "source": "P2 demographics", "description": "Expected deaths" }, { "field": "inheritanceComplexity", "source": "P2 family structures", "description": "Family composition" }, { "field": "culturalContext", "source": "P0 Q19-21", "description": "Cultural inheritance practices" }, { "field": "documentationGaps", "source": "P0 context", "description": "Current documentation barriers" } ], "implementationComplexity": "medium", "examples": { "note": "Vital registration in humanitarian settings", "references": [ { "name": "WHO Civil Registration and Vital Statistics", "url": "https://www.who.int/data/data-collection-tools/civil-registration-and-vital-statistics", "solved": "Standards and guidelines for death registration in humanitarian settings" }, { "name": "ICRC Missing Persons Documentation", "url": "https://www.icrc.org/en/document/missing-persons", "solved": "Documentation of deaths and missing persons in conflict, maintaining chain of custody for accountability" } ] }, "solutionQuestions": [ { "id": "death-registration-context", "type": "select", "options": [ { "label": "Conflict-related deaths requiring documentation for accountability", "value": "conflict" }, { "label": "Natural disaster mortality documentation", "value": "disaster" }, { "label": "Routine deaths in displacement settings needing formal registration", "value": "routine-displacement" }, { "label": "Epidemic/pandemic mortality tracking", "value": "epidemic" } ], "propertyMapping": { "conflict": { "technologies": [ "Conflict mortality documentation platform", "Evidence chain-of-custody engine", "Witness attestation protocol" ], "technologyProperties": { "registrationContext": "Conflict \u2014 legal accountability focus", "evidenceStandard": "Court-admissible chain of custody", "sensitivityLevel": "Maximum \u2014 security considerations" } }, "disaster": { "technologies": [ "Disaster mortality tracking platform", "Rapid identification module" ], "technologyProperties": { "registrationContext": "Disaster \u2014 mass casualty management", "evidenceStandard": "Disaster victim identification (DVI) standards", "sensitivityLevel": "High \u2014 mass event handling" } }, "routine-displacement": { "technologies": [ "Death record issuance platform", "Civil registry integration layer" ], "technologyProperties": { "registrationContext": "Routine vital registration in displacement", "evidenceStandard": "Civil registration standard", "sensitivityLevel": "Standard" } }, "epidemic": { "technologies": [ "Epidemic mortality surveillance platform", "Aggregate mortality reporting" ], "technologyProperties": { "registrationContext": "Epidemic \u2014 public health surveillance", "evidenceStandard": "WHO mortality coding (ICD)", "sensitivityLevel": "High \u2014 public health data" } } }, "prefillFrom": null, "briefSection": "Identity protocol", "text": "What is the context for death registration in your operating environment?", "ngoText": "What is the context for death registration in your operating environment?" }, { "id": "inheritance-documentation", "type": "select", "options": [ { "label": "Yes, formal inheritance documentation is critical", "value": "formal-inheritance" }, { "label": "Yes, but informal/customary inheritance practices apply", "value": "customary" }, { "label": "Inheritance tracking for programme asset transfer only", "value": "programme-assets" }, { "label": "No inheritance documentation needed", "value": "no-inheritance" } ], "propertyMapping": { "formal-inheritance": { "technologies": [ "Inheritance documentation module", "Legal heir verification engine", "Asset registry linkage" ], "technologyProperties": { "inheritanceModel": "Formal legal inheritance chain", "heirVerification": "Identity + relationship verification", "assetLinkage": "Linked to property/asset registry" } }, "customary": { "technologies": [ "Customary inheritance documentation", "Community elder attestation protocol" ], "technologyProperties": { "inheritanceModel": "Customary/traditional inheritance", "heirVerification": "Community attestation", "assetLinkage": "Community-acknowledged inheritance" } }, "programme-assets": { "technologies": [ "Programme asset transfer module", "Beneficiary transfer workflow" ], "technologyProperties": { "inheritanceModel": "Programme benefit transfer", "heirVerification": "Household member verification", "assetLinkage": "Programme enrolment transfer" } }, "no-inheritance": { "technologies": [ "Death record platform" ], "technologyProperties": { "inheritanceModel": "Not applicable", "heirVerification": "Not required", "assetLinkage": "None" } } }, "prefillFrom": null, "briefSection": "Credential issuance", "text": "Is inheritance and property rights documentation needed alongside death registration?", "ngoText": "Is inheritance and property rights documentation needed alongside death registration?" }, { "id": "death-verification", "type": "select", "options": [ { "label": "Medical certification (health facility or medical examiner)", "value": "medical" }, { "label": "Community witness attestation with verification", "value": "community-witness" }, { "label": "Field staff documentation with evidence capture", "value": "field-staff" }, { "label": "Multiple methods depending on context", "value": "multi-method" } ], "propertyMapping": { "medical": { "technologies": [ "Medical death certification module", "Cause-of-death coding engine" ], "technologyProperties": { "verificationMethod": "Medical professional certification", "evidenceCapture": "Clinical documentation", "causeCoding": "ICD mortality coding" } }, "community-witness": { "technologies": [ "Community witness verification protocol", "Multi-witness attestation engine" ], "technologyProperties": { "verificationMethod": "Community witness (minimum 2 witnesses)", "evidenceCapture": "Witness statements + timestamps", "causeCoding": "Verbal autopsy" } }, "field-staff": { "technologies": [ "Field documentation application", "Photo/evidence capture module" ], "technologyProperties": { "verificationMethod": "Field staff documentation", "evidenceCapture": "Photographic + narrative evidence", "causeCoding": "Field assessment" } }, "multi-method": { "technologies": [ "Adaptive death verification platform", "Multi-source evidence correlation" ], "technologyProperties": { "verificationMethod": "Adaptive \u2014 medical or community or field", "evidenceCapture": "Multi-source evidence chain", "causeCoding": "Best available method" } } }, "prefillFrom": null, "briefSection": "Verification and privacy", "text": "How are death events currently verified and documented?", "ngoText": "How are death events currently verified and documented?" }, { "id": "death-privacy", "type": "select", "options": [ { "label": "Standard privacy with cultural sensitivity training", "value": "standard-cultural" }, { "label": "High sensitivity: restricted access, anonymised reporting", "value": "high-sensitivity" }, { "label": "Conflict context: security considerations for data holders", "value": "security-sensitive" } ], "propertyMapping": { "standard-cultural": { "technologies": [ "Culturally-sensitive data interface", "Role-based access control" ], "technologyProperties": { "privacyLevel": "Standard with cultural protocols", "accessRestriction": "Role-based", "reportingAnonymisation": "Standard anonymisation" } }, "high-sensitivity": { "technologies": [ "Restricted-access data vault", "Anonymised analytics layer" ], "technologyProperties": { "privacyLevel": "Highly restricted", "accessRestriction": "Need-to-know basis", "reportingAnonymisation": "Full anonymisation" } }, "security-sensitive": { "technologies": [ "Security-hardened data platform", "Encrypted evidence vault", "Dead man's switch data protection" ], "technologyProperties": { "privacyLevel": "Maximum \u2014 security context", "accessRestriction": "Encrypted + physical security", "reportingAnonymisation": "Anonymised with security review" } } }, "prefillFrom": null, "briefSection": "Consent and governance", "text": "What privacy and cultural sensitivity considerations apply to death records?", "ngoText": "What privacy and cultural sensitivity considerations apply to death records?" }, { "id": "death-reporting", "type": "select", "options": [ { "label": "Internal programme reporting only", "value": "internal" }, { "label": "National vital statistics contribution", "value": "vital-stats" }, { "label": "International humanitarian mortality reporting", "value": "international" }, { "label": "Legal/accountability reporting (courts, commissions)", "value": "legal" } ], "propertyMapping": { "internal": { "technologies": [ "Internal reporting dashboard" ], "technologyProperties": { "reportingScope": "Organisation internal", "dataStandard": "Internal format", "reportingFrequency": "On-demand" } }, "vital-stats": { "technologies": [ "National vital statistics export module", "CRVS integration layer" ], "technologyProperties": { "reportingScope": "National vital statistics", "dataStandard": "National CRVS format", "reportingFrequency": "Monthly batch" } }, "international": { "technologies": [ "WHO mortality reporting module", "Humanitarian mortality surveillance" ], "technologyProperties": { "reportingScope": "International humanitarian", "dataStandard": "WHO standards", "reportingFrequency": "Weekly during crisis" } }, "legal": { "technologies": [ "Legal evidence export module", "Court-admissible documentation engine" ], "technologyProperties": { "reportingScope": "Legal proceedings", "dataStandard": "Court-admissible format", "reportingFrequency": "On-demand with chain of custody" } } }, "prefillFrom": null, "briefSection": "Reporting and audit", "text": "What death registration reporting is required?", "ngoText": "What death registration reporting is required?" }, { "id": "death-connectivity", "type": "select", "options": [ { "label": "Reliable internet connectivity", "value": "connected" }, { "label": "Intermittent connectivity with offline capability needed", "value": "intermittent" }, { "label": "Fully offline: remote or conflict areas", "value": "offline" } ], "propertyMapping": { "connected": { "technologies": [ "Cloud-hosted registration platform" ], "technologyProperties": { "connectivity": "Online", "offlineCapability": "Not required", "syncModel": "Real-time" } }, "intermittent": { "technologies": [ "Offline-first registration application", "Sync queue manager" ], "technologyProperties": { "connectivity": "Intermittent", "offlineCapability": "Required", "syncModel": "Store-and-forward" } }, "offline": { "technologies": [ "Fully offline registration toolkit", "Secure offline evidence storage" ], "technologyProperties": { "connectivity": "None", "offlineCapability": "Full offline workflow", "syncModel": "Physical transfer or periodic batch" } } }, "prefillFrom": null, "briefSection": "Infrastructure requirements", "text": "What connectivity is available at death registration points?", "ngoText": "What connectivity is available at death registration points?" }, { "id": "consent-management-approach", "type": "select", "options": [ { "label": "Granular consent: individuals control each data element shared", "value": "granular" }, { "label": "Tiered consent: pre-defined levels (basic, standard, full)", "value": "tiered" }, { "label": "Blanket consent with opt-out for specific data categories", "value": "blanket-optout" }, { "label": "Guardian/proxy consent for vulnerable populations", "value": "guardian-proxy" } ], "propertyMapping": { "granular": { "technologies": [ "Granular consent management platform", "Consent ledger", "Privacy-preserving disclosure engine" ], "technologyProperties": { "consentGranularity": "Per-attribute", "consentStorage": "Digital consent receipts", "revocation": "Real-time revocable" } }, "tiered": { "technologies": [ "Tiered consent management system", "Consent ledger", "Pre-defined disclosure profiles" ], "technologyProperties": { "consentGranularity": "Pre-defined tiers", "consentStorage": "Digital consent receipts", "revocation": "Tier-level revocation" } }, "blanket-optout": { "technologies": [ "Consent management platform", "Consent ledger", "Opt-out tracking service" ], "technologyProperties": { "consentGranularity": "Broad with category opt-outs", "consentStorage": "Digital consent records", "revocation": "Category-level opt-out" } }, "guardian-proxy": { "technologies": [ "Guardian consent management platform", "Consent ledger", "Proxy delegation service" ], "technologyProperties": { "consentGranularity": "Guardian-managed on behalf of individual", "consentStorage": "Digital with guardian chain of authority", "revocation": "Guardian or individual (when able)" } } }, "prefillFrom": null, "briefSection": "Privacy and consent", "text": "How do you currently manage consent for beneficiary data collection and sharing?", "ngoText": "How do you currently manage consent for beneficiary data collection and sharing?" }, { "id": "beneficiary-choice", "label": "How will beneficiaries exercise choice in how they receive and use this service?", "type": "select", "briefSection": "Holder experience", "options": [ { "label": "Beneficiaries choose between delivery methods (cash, voucher, mobile money, direct)", "value": "delivery-choice" }, { "label": "Beneficiaries choose preferred merchants or service points", "value": "merchant-choice" }, { "label": "Beneficiaries control their own data sharing preferences", "value": "data-choice" }, { "label": "Multiple choice dimensions (delivery + merchant + data)", "value": "full-choice" }, { "label": "Limited choice: programme constraints determine delivery", "value": "limited" } ], "propertyMapping": { "delivery-choice": { "technologies": [], "technologyProperties": { "beneficiaryChoice": "Delivery method choice", "dignityDesign": "Beneficiaries select preferred receipt method" } }, "merchant-choice": { "technologies": [], "technologyProperties": { "beneficiaryChoice": "Merchant/service point choice", "dignityDesign": "Beneficiaries select where to redeem" } }, "data-choice": { "technologies": [], "technologyProperties": { "beneficiaryChoice": "Data sharing choice", "dignityDesign": "Beneficiaries control personal data sharing" } }, "full-choice": { "technologies": [], "technologyProperties": { "beneficiaryChoice": "Multi-dimensional choice", "dignityDesign": "Full beneficiary agency across delivery, merchant, and data" } }, "limited": { "technologies": [], "technologyProperties": { "beneficiaryChoice": "Limited by programme design", "dignityDesign": "Programme constraints; beneficiary informed of reasons" } } }, "text": "How will beneficiaries exercise choice in how they receive and use this service?" } ], "complexityFactors": { "relationships": 3, "operationalChange": 2, "dataCompliance": 4 }, "securityTier": "B", "suggestedCriteria": [ { "id": "SC-EVIDENCE-INTEGRITY", "name": "Evidence Chain Integrity", "description": "The system can maintain a tamper-proof chain of evidence for death circumstances, documentation, and inheritance claims. Critical for conflict and disaster mortality.", "weight": 0.3, "ratingGuide": { "5": "Cryptographic evidence chain with timestamped, immutable records. Multi-party attestation. Independently verifiable.", "4": "Tamper-evident record keeping with audit trail. Evidence integrity provable to third parties.", "3": "Secure storage with access logging. Tampering detectable but not independently provable.", "2": "Standard database with audit logs. Evidence integrity relies on operator trust.", "1": "No chain of custody tracking. Records can be modified without detection." } }, { "id": "SC-SENSITIVITY-HANDLING", "name": "Privacy & Sensitivity Handling", "description": "The system handles conflict-related and disaster mortality data with appropriate sensitivity. Includes selective disclosure of cause and circumstances.", "weight": 0.25, "ratingGuide": { "5": "Selective disclosure \u2014 prove death occurred without revealing circumstances. Graduated access levels for different stakeholders.", "4": "Encrypted records with role-based access. Sensitive details (cause, circumstances) separately protected.", "3": "Access controls distinguish between administrative and sensitive data. Some selective disclosure.", "2": "All death record details visible to authorised staff. No graduated access.", "1": "All data visible to all system users. No sensitivity classification." } }, { "id": "SC-LEGAL-DEATH-CERT", "name": "Legal System Integration", "description": "The digital death can record translate to official death certificates recognised by host and origin countries. Needed for inheritance, insurance, and legal proceedings.", "weight": 0.2, "ratingGuide": { "5": "Active government partnerships. Digital death records accepted as legal evidence. Multi-country recognition.", "4": "Government pilot programmes. Clear pathway to legal recognition in key jurisdictions.", "3": "Exportable in standard civil registration formats. Some government engagement.", "2": "Digital record only. Can be printed but no formal legal pathway.", "1": "Proprietary format. No legal recognition pathway." } }, { "id": "SC-INHERITANCE-TRACK", "name": "Inheritance Rights Documentation", "description": "The system can link death records to inheritance documentation, asset claims, and succession rights. Critical for displaced families.", "weight": 0.15, "ratingGuide": { "5": "Integrated inheritance workflow \u2014 death record automatically triggers rights documentation. Smart contract for conditional asset release.", "4": "Death record links to inheritance claims. Structured workflow for succession documentation.", "3": "Death records can reference inheritance documents. Manual linking required.", "2": "Death records standalone. Inheritance documentation is a separate process.", "1": "No inheritance tracking capability." } }, { "id": "SC-MULTI-AUTHORITY-VERIFY", "name": "Multi-Authority Verification", "description": "Can multiple parties (hospitals, religious leaders, community elders, government) attest to death records without centralised database access?", "weight": 0.1, "ratingGuide": { "5": "Decentralised multi-party attestation. Each authority verifies independently. No shared database required.", "4": "Federated attestation with minimal data sharing between authorities.", "3": "Shared verification service. Authorities submit attestations to central system.", "2": "Single-authority verification. One entity controls the record.", "1": "No multi-authority support. Single point of attestation." } } ], "procurement": { "marketMaturity": "nascent", "primaryMode": "integrator-led", "alternativeModes": [ "rfq" ], "reasoning": "Death registration with inheritance documentation is emerging; few mature products.", "exampleProductCategories": [ "civil-registration-platform", "vital-records-saas" ], "partnerChannels": [], "lastReviewed": "2026-05-01" } }, { "id": "UC-B-027", "name": "Marriage and family status documentation", "category": "B", "subcategory": "Identity Registration", "description": "Record marriages and family relationships in a way that other organisations and countries accept, so families can claim household and spousal benefits.", "bCriteria": [ "B1", "B3" ], "requiredComponents": [ { "component": "record-keeping-platform", "description": "Marriage/family status records" }, { "component": "credential-issuance", "description": "Marriage certificate issuance" }, { "component": "verification-mechanism", "description": "Proof of marriage/family status" }, { "component": "consent-management", "description": "Consent for family status changes" } ], "conditionalComponents": [ { "component": "identity-verification", "condition": "For all parties to marriage" }, { "component": "privacy-tech", "condition": "If sensitive family information needs protection" } ], "crossCategoryDependencies": [ "UC-B-024 for individual identities" ], "p2TriggerConditions": { "description": "Activated when P2 shows displacement settings + family composition targeting + spousal benefits", "rangeSignals": [ "familyBasedAssistance >= true", "familyCompositionTracking >= true", "spousalBenefits >= true" ] }, "contextFieldsTemplate": [ { "field": "familyCount", "source": "P2 beneficiary data", "description": "Families to register" }, { "field": "marriageDocumentation", "source": "P0 context", "description": "Marriage record availability" }, { "field": "familyComposition", "source": "P2 targeting", "description": "Types of family structures" }, { "field": "culturalandReligious", "source": "P0 Q19-21", "description": "Religious/cultural marriage contexts" } ], "implementationComplexity": "medium", "examples": { "note": "Humanitarian family documentation", "references": [ { "name": "UNHCR Family Relationship Documentation", "url": "https://www.unhcr.org/registration-guidance", "solved": "Family composition documentation for refugee populations across multiple cultural contexts" }, { "name": "Plan International Birth and Family Registration", "url": "https://plan-international.org/birth-registration", "solved": "Birth and family registration campaigns in displacement settings" } ] }, "solutionQuestions": [ { "id": "marriage-type", "type": "select", "options": [ { "label": "Civil/legal marriages requiring formal registration", "value": "civil" }, { "label": "Religious marriages needing documentation for legal purposes", "value": "religious" }, { "label": "Customary/traditional marriages and unions", "value": "customary" }, { "label": "Multiple types: civil, religious, and customary", "value": "multiple" } ], "propertyMapping": { "civil": { "technologies": [ "Civil marriage registration platform", "Government registry connection" ], "technologyProperties": { "marriageType": "Civil/legal", "legalRecognition": "Government registry integration", "verificationStandard": "Legal witness requirement" } }, "religious": { "technologies": [ "Religious authority attestation module", "Multi-faith registration protocol" ], "technologyProperties": { "marriageType": "Religious", "legalRecognition": "Religious authority attestation", "verificationStandard": "Religious authority witness" } }, "customary": { "technologies": [ "Community attestation protocol", "Elder/chief witness module" ], "technologyProperties": { "marriageType": "Customary/traditional", "legalRecognition": "Community attestation", "verificationStandard": "Community elder witness" } }, "multiple": { "technologies": [ "Multi-type marriage registration platform", "Adaptive attestation engine" ], "technologyProperties": { "marriageType": "Multiple types supported", "legalRecognition": "Adaptive \u2014 civil + religious + customary", "verificationStandard": "Context-appropriate witnesses" } } }, "prefillFrom": null, "briefSection": "Identity protocol", "text": "What types of marriages/unions need to be documented?", "ngoText": "What types of marriages/unions need to be documented?" }, { "id": "family-composition", "type": "select", "options": [ { "label": "Nuclear families (couple + children)", "value": "nuclear" }, { "label": "Extended family relationships (including dependents)", "value": "extended" }, { "label": "Complex family structures (polygamous, blended, guardian)", "value": "complex" }, { "label": "All structures, highly diverse family compositions", "value": "all" } ], "propertyMapping": { "nuclear": { "technologies": [ "Family relationship graph (simple)", "Household credential issuance" ], "technologyProperties": { "familyModel": "Nuclear family", "relationshipComplexity": "Low", "dependentTracking": "Direct children only" } }, "extended": { "technologies": [ "Extended family relationship graph", "Multi-generational linkage module" ], "technologyProperties": { "familyModel": "Extended family", "relationshipComplexity": "Medium", "dependentTracking": "Multi-generational dependents" } }, "complex": { "technologies": [ "Complex family graph engine", "Multi-household linkage protocol" ], "technologyProperties": { "familyModel": "Complex \u2014 polygamous, blended, guardian", "relationshipComplexity": "High", "dependentTracking": "Multi-household, multi-spouse" } }, "all": { "technologies": [ "Universal family relationship platform", "Adaptive family graph engine" ], "technologyProperties": { "familyModel": "All structures supported", "relationshipComplexity": "Adaptive", "dependentTracking": "Universal dependent mapping" } } }, "prefillFrom": null, "briefSection": "Credential issuance", "text": "What family structures need to be documented?", "ngoText": "What family structures need to be documented?" }, { "id": "family-credential-use", "type": "select", "options": [ { "label": "Programme enrolment (family-based targeting)", "value": "programme-enrolment" }, { "label": "Legal documentation (marriage certificates, family books)", "value": "legal-docs" }, { "label": "Inheritance and property rights claims", "value": "inheritance" }, { "label": "Cross-border family reunification", "value": "reunification" } ], "propertyMapping": { "programme-enrolment": { "technologies": [ "Family verification credential", "Household targeting module" ], "technologyProperties": { "credentialUse": "Programme targeting and enrolment", "verificationFrequency": "At each distribution/service point", "credentialContent": "Family composition + dependency status" } }, "legal-docs": { "technologies": [ "Legal certificate issuance engine", "Official document template module" ], "technologyProperties": { "credentialUse": "Legal documentation", "verificationFrequency": "On-demand for legal proceedings", "credentialContent": "Full marriage/family certificate" } }, "inheritance": { "technologies": [ "Inheritance eligibility credential", "Property rights linkage module" ], "technologyProperties": { "credentialUse": "Inheritance and property claims", "verificationFrequency": "At claim time", "credentialContent": "Family relationship proof + heir status" } }, "reunification": { "technologies": [ "Family reunification credential", "Cross-border family verification" ], "technologyProperties": { "credentialUse": "Family reunification documentation", "verificationFrequency": "At border/processing points", "credentialContent": "Verified family relationship proof" } } }, "prefillFrom": null, "briefSection": "Verification and privacy", "text": "How will family status credentials be used?", "ngoText": "How will family status credentials be used?" }, { "id": "family-privacy", "type": "select", "options": [ { "label": "Standard privacy: encrypted with role-based access", "value": "standard" }, { "label": "High sensitivity: GBV risk requires restricted access", "value": "gbv-sensitive" }, { "label": "Cultural sensitivity: community norms around family disclosure", "value": "cultural" } ], "propertyMapping": { "standard": { "technologies": [ "Encrypted family record store", "Role-based access control" ], "technologyProperties": { "privacyLevel": "Standard encryption + RBAC", "sensitiveFields": "Standard protection", "disclosureControl": "Role-based" } }, "gbv-sensitive": { "technologies": [ "GBV-sensitive data vault", "Restricted access protocol", "Emergency override mechanism" ], "technologyProperties": { "privacyLevel": "Maximum \u2014 GBV protection protocols", "sensitiveFields": "Relationship status hidden from non-authorised", "disclosureControl": "Case-by-case with protection officer" } }, "cultural": { "technologies": [ "Culturally-adaptive privacy module", "Community-norm privacy settings" ], "technologyProperties": { "privacyLevel": "Culturally appropriate", "sensitiveFields": "Context-dependent sensitivity", "disclosureControl": "Community-norm aligned" } } }, "prefillFrom": null, "briefSection": "Consent and governance", "text": "What privacy considerations apply to family status data?", "ngoText": "What privacy considerations apply to family status data?" }, { "id": "family-connectivity", "type": "select", "options": [ { "label": "Reliable internet connectivity", "value": "connected" }, { "label": "Intermittent connectivity", "value": "intermittent" }, { "label": "Fully offline: remote areas", "value": "offline" } ], "propertyMapping": { "connected": { "technologies": [ "Cloud-hosted family registration platform" ], "technologyProperties": { "connectivity": "Online", "syncModel": "Real-time", "offlineCapability": "Not required" } }, "intermittent": { "technologies": [ "Offline-first registration application", "Sync queue manager" ], "technologyProperties": { "connectivity": "Intermittent", "syncModel": "Store-and-forward", "offlineCapability": "Required" } }, "offline": { "technologies": [ "Fully offline registration toolkit" ], "technologyProperties": { "connectivity": "None", "syncModel": "Batch upload", "offlineCapability": "Full offline workflow" } } }, "prefillFrom": null, "briefSection": "Infrastructure requirements", "text": "What connectivity is available for family registration activities?", "ngoText": "What connectivity is available for family registration activities?" }, { "id": "family-reporting", "type": "select", "options": [ { "label": "Internal programme reporting", "value": "internal" }, { "label": "Vital statistics contribution", "value": "vital-stats" }, { "label": "Protection case reporting", "value": "protection" } ], "propertyMapping": { "internal": { "technologies": [ "Internal reporting dashboard" ], "technologyProperties": { "reportingScope": "Programme internal", "auditDepth": "Standard", "reportingFormat": "Internal templates" } }, "vital-stats": { "technologies": [ "Vital statistics export module" ], "technologyProperties": { "reportingScope": "National vital statistics", "auditDepth": "CRVS-compliant", "reportingFormat": "National standard" } }, "protection": { "technologies": [ "Protection reporting module", "Anonymised case analytics" ], "technologyProperties": { "reportingScope": "Protection cluster reporting", "auditDepth": "Case-level with anonymisation", "reportingFormat": "Protection standards" } } }, "prefillFrom": null, "briefSection": "Reporting and audit", "text": "What reporting is needed for family status documentation?", "ngoText": "What reporting is needed for family status documentation?" }, { "id": "consent-management-approach", "type": "select", "options": [ { "label": "Granular consent: individuals control each data element shared", "value": "granular" }, { "label": "Tiered consent: pre-defined levels (basic, standard, full)", "value": "tiered" }, { "label": "Blanket consent with opt-out for specific data categories", "value": "blanket-optout" }, { "label": "Guardian/proxy consent for vulnerable populations", "value": "guardian-proxy" } ], "propertyMapping": { "granular": { "technologies": [ "Granular consent management platform", "Consent ledger", "Privacy-preserving disclosure engine" ], "technologyProperties": { "consentGranularity": "Per-attribute", "consentStorage": "Digital consent receipts", "revocation": "Real-time revocable" } }, "tiered": { "technologies": [ "Tiered consent management system", "Consent ledger", "Pre-defined disclosure profiles" ], "technologyProperties": { "consentGranularity": "Pre-defined tiers", "consentStorage": "Digital consent receipts", "revocation": "Tier-level revocation" } }, "blanket-optout": { "technologies": [ "Consent management platform", "Consent ledger", "Opt-out tracking service" ], "technologyProperties": { "consentGranularity": "Broad with category opt-outs", "consentStorage": "Digital consent records", "revocation": "Category-level opt-out" } }, "guardian-proxy": { "technologies": [ "Guardian consent management platform", "Consent ledger", "Proxy delegation service" ], "technologyProperties": { "consentGranularity": "Guardian-managed on behalf of individual", "consentStorage": "Digital with guardian chain of authority", "revocation": "Guardian or individual (when able)" } } }, "prefillFrom": null, "briefSection": "Privacy and consent", "text": "How do you currently manage consent for beneficiary data collection and sharing?", "ngoText": "How do you currently manage consent for beneficiary data collection and sharing?" }, { "id": "beneficiary-choice", "label": "How will beneficiaries exercise choice in how they receive and use this service?", "type": "select", "briefSection": "Holder experience", "options": [ { "label": "Beneficiaries choose between delivery methods (cash, voucher, mobile money, direct)", "value": "delivery-choice" }, { "label": "Beneficiaries choose preferred merchants or service points", "value": "merchant-choice" }, { "label": "Beneficiaries control their own data sharing preferences", "value": "data-choice" }, { "label": "Multiple choice dimensions (delivery + merchant + data)", "value": "full-choice" }, { "label": "Limited choice: programme constraints determine delivery", "value": "limited" } ], "propertyMapping": { "delivery-choice": { "technologies": [], "technologyProperties": { "beneficiaryChoice": "Delivery method choice", "dignityDesign": "Beneficiaries select preferred receipt method" } }, "merchant-choice": { "technologies": [], "technologyProperties": { "beneficiaryChoice": "Merchant/service point choice", "dignityDesign": "Beneficiaries select where to redeem" } }, "data-choice": { "technologies": [], "technologyProperties": { "beneficiaryChoice": "Data sharing choice", "dignityDesign": "Beneficiaries control personal data sharing" } }, "full-choice": { "technologies": [], "technologyProperties": { "beneficiaryChoice": "Multi-dimensional choice", "dignityDesign": "Full beneficiary agency across delivery, merchant, and data" } }, "limited": { "technologies": [], "technologyProperties": { "beneficiaryChoice": "Limited by programme design", "dignityDesign": "Programme constraints; beneficiary informed of reasons" } } }, "text": "How will beneficiaries exercise choice in how they receive and use this service?" } ], "complexityFactors": { "relationships": 3, "operationalChange": 2, "dataCompliance": 4 }, "securityTier": "B", "suggestedCriteria": [ { "id": "SC-CULTURAL-PLURALISM", "name": "Cultural & Legal Pluralism Support", "description": "Does the system handle diverse marriage types (civil, religious, customary) and family structures (nuclear, extended, polygamous) across different cultural and legal contexts?", "weight": 0.25, "ratingGuide": { "5": "Supports all marriage types and family structures. Configurable per jurisdiction. Handles polygamy, extended family, and blended families.", "4": "Supports most marriage types. Family structure modelling handles common variations.", "3": "Supports civil and religious marriage. Limited customary or complex family structure support.", "2": "Primarily designed for civil marriage in Western legal frameworks. Limited cultural adaptability.", "1": "Single marriage type only. No cultural variation support." } }, { "id": "SC-FAMILY-PRIVACY", "name": "Privacy & Selective Disclosure", "description": "Family relationships can be proved without revealing all family details. A person should be able to prove marital status without disclosing spouse's identity or full family tree.", "weight": 0.25, "ratingGuide": { "5": "Zero-knowledge family proofs \u2014 prove marital status or relationship without revealing identities. Granular selective disclosure.", "4": "Selective disclosure of specific relationships. Verifier sees only the claimed relationship.", "3": "Encrypted family graph with role-based access. Some selective disclosure capability.", "2": "Family data accessible to authorised parties. Limited ability to restrict what is revealed.", "1": "Full family details visible during any verification." } }, { "id": "SC-CROSS-JURISDICTION", "name": "Cross-Jurisdiction Recognition", "description": "Family status credentials are verifiable across different countries and legal systems. Displaced families need documentation that works beyond their country of origin.", "weight": 0.2, "ratingGuide": { "5": "Multi-jurisdiction credential framework. Government partnerships for cross-border recognition. Handles conflicting family laws.", "4": "Credentials exportable in internationally recognised formats. Some government engagement.", "3": "Standard credential format. Portable but not yet formally recognised across borders.", "2": "Credentials valid in single jurisdiction. Export possible but unverified abroad.", "1": "Proprietary format. No cross-jurisdiction capability." } }, { "id": "SC-FAMILY-GRAPH", "name": "Family Graph Integrity", "description": "Family relationships can be accurately tracked and verified without building a centralised family database. Prevents data misuse while maintaining relationship integrity.", "weight": 0.15, "ratingGuide": { "5": "Decentralised family graph \u2014 relationships verified without centralised storage. Each family member controls their own relationship claims.", "4": "Encrypted family graph with distributed storage. No single point of access to all relationships.", "3": "Centralised but encrypted family database. Access controls protect against misuse.", "2": "Standard database with basic access controls. Family data centralised.", "1": "Unprotected family relationship data in centralised system." } }, { "id": "SC-FIELD-USABILITY", "name": "Field Usability", "description": "The system can be used in camp settings by non-literate or low-literacy users. Marriage and family documentation often involves elderly community leaders and non-literate populations.", "weight": 0.15, "ratingGuide": { "5": "Designed for low-literacy users. Voice guidance, pictorial interfaces, works on basic phones. Offline-capable in camps.", "4": "Accessible interface with offline capability. Supports multiple languages and low-literacy modes.", "3": "Smartphone-based with offline sync. Requires basic literacy.", "2": "Web-based interface. Requires connectivity and digital literacy.", "1": "Desktop application requiring training and constant connectivity." } } ], "procurement": { "marketMaturity": "nascent", "primaryMode": "integrator-led", "alternativeModes": [ "rfq" ], "reasoning": "Marriage and family status documentation is jurisdiction-specific.", "exampleProductCategories": [ "vital-records-saas", "digital-identity-rails" ], "partnerChannels": [], "lastReviewed": "2026-05-01" } }, { "id": "UC-B-028", "name": "Portable service history across borders and organisations", "category": "B", "subcategory": "Credential Portability", "description": "Let a person carry their record of help received from one country or organisation to the next, so they do not have to prove it again.", "bCriteria": [ "B1", "B6" ], "requiredComponents": [ { "component": "identity-protocol", "description": "Portable identity protocol" }, { "component": "credential-issuance", "description": "Service history credentials" }, { "component": "holder-app", "description": "Personal wallet for service records" }, { "component": "interoperability-layer", "description": "Cross-organisation credential exchange" }, { "component": "verification-mechanism", "description": "Verifiable service attestations" } ], "conditionalComponents": [ { "component": "privacy-tech", "condition": "If selective disclosure needed" } ], "crossCategoryDependencies": [], "p2TriggerConditions": { "description": "Activated when P2 shows beneficiary mobility + service continuity needs + multi-organisation referrals", "rangeSignals": [ "beneficiaryMobility >= high", "servicePortability >= important", "multiOrgReferral >= true" ] }, "contextFieldsTemplate": [ { "field": "serviceTypes", "source": "P2 service portfolio", "description": "Types of services provided" }, { "field": "partnerOrganisations", "source": "P0 partnerships", "description": "Organisations involved" }, { "field": "beneficiaryMobility", "source": "P0 context + P4", "description": "Geographic movement patterns" }, { "field": "interoperabilityGoal", "source": "P2 coordination needs", "description": "Cross-org data sharing needs" } ], "implementationComplexity": "medium-high", "examples": { "note": "Portable credentials initiatives, displacement context", "references": [ { "name": "Gravity Earth Portable Credentials", "url": "https://www.gravity.earth/", "solved": "Portable digital credentials for refugees moving across borders, enabling service continuity" }, { "name": "Tykn Digital Identity for Refugees", "url": "https://tykn.tech/", "solved": "Portable service records for displaced populations across multiple agencies" }, { "name": "Kiva Protocol", "url": "https://www.kiva.org/protocol", "solved": "National digital identity platform enabling portable service access in Sierra Leone" } ] }, "solutionQuestions": [ { "id": "service-types", "type": "select", "options": [ { "label": "Health services (vaccinations, treatments, referrals)", "value": "health" }, { "label": "Education services (enrolment, completion, grades)", "value": "education" }, { "label": "Cash/voucher assistance (distributions received)", "value": "cash-assistance" }, { "label": "Multiple service types across sectors", "value": "multi-sector" } ], "propertyMapping": { "health": { "technologies": [ "Health service credential engine", "Medical record verifiable credential" ], "technologyProperties": { "serviceScope": "Health sector", "credentialTypes": "Vaccination records, treatment history, referral chain", "dataStandard": "HL7 FHIR + W3C VC" } }, "education": { "technologies": [ "Education credential engine", "Academic record verifiable credential" ], "technologyProperties": { "serviceScope": "Education sector", "credentialTypes": "Enrolment, completion, assessment results", "dataStandard": "Open Badges + W3C VC" } }, "cash-assistance": { "technologies": [ "Distribution record credential", "Entitlement tracking credential" ], "technologyProperties": { "serviceScope": "Cash/voucher assistance", "credentialTypes": "Distribution receipts, entitlement balance", "dataStandard": "Humanitarian cash transfer standard" } }, "multi-sector": { "technologies": [ "Universal service credential platform", "Multi-sector credential schema registry" ], "technologyProperties": { "serviceScope": "Cross-sector (health + education + cash + protection)", "credentialTypes": "Unified service history across sectors", "dataStandard": "W3C VC with sector-specific extensions" } } }, "prefillFrom": null, "briefSection": "Credential issuance", "text": "What types of services need to be tracked in the portable history?", "ngoText": "What types of services need to be tracked in the portable history?" }, { "id": "portability-scope", "type": "select", "options": [ { "label": "Within a single country across multiple organisations", "value": "national" }, { "label": "Across 2-3 neighbouring countries (regional)", "value": "regional" }, { "label": "Global portability for mobile populations", "value": "global" } ], "propertyMapping": { "national": { "technologies": [ "National credential exchange network", "DID resolver (national)" ], "technologyProperties": { "portabilityScope": "National", "exchangeProtocol": "National interoperability standard", "didResolution": "National DID registry" } }, "regional": { "technologies": [ "Regional credential exchange network", "Cross-border DID resolution" ], "technologyProperties": { "portabilityScope": "Regional (multi-country)", "exchangeProtocol": "Regional interoperability agreement", "didResolution": "Regional DID resolver federation" } }, "global": { "technologies": [ "Global credential exchange platform", "Universal DID resolver", "Credential translation service" ], "technologyProperties": { "portabilityScope": "Global", "exchangeProtocol": "W3C DID + VC global standards", "didResolution": "Universal DID resolver" } } }, "prefillFrom": null, "briefSection": "Interoperability", "text": "How widely do credentials need to be recognised?", "ngoText": "How widely do credentials need to be recognised?" }, { "id": "holder-control", "type": "select", "options": [ { "label": "Full user-controlled portable control: beneficiary decides what to share", "value": "full-control" }, { "label": "Shared control: beneficiary consents, organisation manages", "value": "shared-control" }, { "label": "Organisation-managed with beneficiary visibility", "value": "org-managed" } ], "propertyMapping": { "full-control": { "technologies": [ "Self-sovereign service wallet", "Selective disclosure engine", "Peer-to-peer credential exchange" ], "technologyProperties": { "holderControl": "Full \u2014 beneficiary-held credentials", "sharingModel": "Beneficiary-initiated selective disclosure", "consentModel": "Beneficiary controls all sharing" } }, "shared-control": { "technologies": [ "Managed credential wallet", "Consent-based sharing engine" ], "technologyProperties": { "holderControl": "Shared \u2014 consent-based access", "sharingModel": "Consent-gated organisation access", "consentModel": "Explicit consent per sharing request" } }, "org-managed": { "technologies": [ "Organisation-managed credential store", "Beneficiary access portal" ], "technologyProperties": { "holderControl": "Limited \u2014 organisation managed", "sharingModel": "Organisation-to-organisation with notification", "consentModel": "Registration consent covers sharing" } } }, "prefillFrom": null, "briefSection": "Holder experience", "text": "How much control should beneficiaries have over their service history?", "ngoText": "How much control should beneficiaries have over their service history?" }, { "id": "history-verification", "type": "select", "options": [ { "label": "Secure digital verification against issuer (real-time check)", "value": "cryptographic-real-time" }, { "label": "Secure digital verification with cached trust (offline capable)", "value": "cryptographic-cached" }, { "label": "Issuer contact for high-value verifications only", "value": "issuer-contact" } ], "propertyMapping": { "cryptographic-real-time": { "technologies": [ "Real-time credential verification API", "Revocation status checker" ], "technologyProperties": { "verificationMethod": "Real-time cryptographic check", "offlineVerification": "Not supported", "verificationSpeed": "Sub-second" } }, "cryptographic-cached": { "technologies": [ "Cached credential verification engine", "Offline verification module" ], "technologyProperties": { "verificationMethod": "Cryptographic with cached revocation status", "offlineVerification": "Supported with cached trust", "verificationSpeed": "Sub-second (online or offline)" } }, "issuer-contact": { "technologies": [ "Issuer verification API", "Trust escalation protocol" ], "technologyProperties": { "verificationMethod": "Issuer contact for high-value, crypto for routine", "offlineVerification": "Routine only", "verificationSpeed": "Variable (minutes for issuer contact)" } } }, "prefillFrom": null, "briefSection": "Verification and privacy", "text": "How is service history currently verified when presented?", "ngoText": "How is service history currently verified when presented?" }, { "id": "history-device", "type": "select", "options": [ { "label": "Smartphone wallet application", "value": "smartphone" }, { "label": "Physical card with QR/NFC (no smartphone needed)", "value": "physical-card" }, { "label": "Cloud-based: accessible from any device", "value": "cloud-based" }, { "label": "Mixed: smartphone + card fallback", "value": "mixed" } ], "propertyMapping": { "smartphone": { "technologies": [ "Mobile service history wallet" ], "technologyProperties": { "holderDevice": "Smartphone", "credentialPresentation": "QR code display or NFC", "offlineAccess": "On-device storage" } }, "physical-card": { "technologies": [ "Smart card credential platform", "QR-code credential card printer" ], "technologyProperties": { "holderDevice": "Physical card", "credentialPresentation": "QR scan or NFC tap", "offlineAccess": "Card-stored credentials" } }, "cloud-based": { "technologies": [ "Cloud credential vault", "Web-based credential portal" ], "technologyProperties": { "holderDevice": "Any device with browser", "credentialPresentation": "Web portal + QR generation", "offlineAccess": "Requires connectivity" } }, "mixed": { "technologies": [ "Multi-channel credential platform", "Smartphone wallet + card fallback" ], "technologyProperties": { "holderDevice": "Smartphone or physical card", "credentialPresentation": "App or card", "offlineAccess": "Both supported" } } }, "prefillFrom": null, "briefSection": "Holder experience", "text": "What devices will beneficiaries use to carry and present their service history?", "ngoText": "What devices will beneficiaries use to carry and present their service history?" }, { "id": "history-privacy", "type": "select", "options": [ { "label": "Full history shared: no selective disclosure needed", "value": "full-share" }, { "label": "Sector-level selection (share health but not cash records)", "value": "sector-level" }, { "label": "Attribute-level selection (share vaccination status without details)", "value": "attribute-level" }, { "label": "Zero-knowledge proofs (prove eligibility without revealing data)", "value": "zkp" } ], "propertyMapping": { "full-share": { "technologies": [ "Standard credential presentation" ], "technologyProperties": { "disclosureLevel": "Full credential shared", "privacyTech": "None \u2014 full disclosure", "zkpRequired": false } }, "sector-level": { "technologies": [ "Sector-based credential bundling", "Selective presentation engine" ], "technologyProperties": { "disclosureLevel": "Sector-level selection", "privacyTech": "Credential bundle selection", "zkpRequired": false } }, "attribute-level": { "technologies": [ "Attribute-level selective disclosure", "Credential derivation engine" ], "technologyProperties": { "disclosureLevel": "Individual attribute selection", "privacyTech": "Derived credential presentation", "zkpRequired": false } }, "zkp": { "technologies": [ "Zero-knowledge proof engine", "ZKP credential verification" ], "technologyProperties": { "disclosureLevel": "Zero-knowledge \u2014 prove without revealing", "privacyTech": "ZK-SNARK or BBS+ signatures", "zkpRequired": true } } }, "prefillFrom": null, "briefSection": "Verification and privacy", "text": "What selective disclosure capabilities do you currently have?", "ngoText": "What selective disclosure capabilities do you currently have?" }, { "id": "history-connectivity", "type": "select", "options": [ { "label": "Reliable internet at verification points", "value": "connected" }, { "label": "Intermittent: offline verification needed sometimes", "value": "intermittent" }, { "label": "Fully offline verification required", "value": "offline" } ], "propertyMapping": { "connected": { "technologies": [ "Online verification platform" ], "technologyProperties": { "connectivity": "Online", "offlineVerification": "Not required", "revocationCheck": "Real-time" } }, "intermittent": { "technologies": [ "Offline-capable verification module", "Cached revocation list" ], "technologyProperties": { "connectivity": "Intermittent", "offlineVerification": "Required", "revocationCheck": "Cached \u2014 periodic refresh" } }, "offline": { "technologies": [ "Fully offline verification engine", "Device-cached trust anchors" ], "technologyProperties": { "connectivity": "Offline", "offlineVerification": "Full offline", "revocationCheck": "Batch updated when connected" } } }, "prefillFrom": null, "briefSection": "Infrastructure requirements", "text": "What connectivity is available where credentials will be presented?", "ngoText": "What connectivity is available where credentials will be presented?" }, { "id": "history-reporting", "type": "select", "options": [ { "label": "Basic usage statistics (presentations, verifications)", "value": "basic-stats" }, { "label": "Service coverage analytics (gaps, duplications)", "value": "coverage" }, { "label": "Cross-organisation coordination insights", "value": "coordination" } ], "propertyMapping": { "basic-stats": { "technologies": [ "Usage analytics dashboard" ], "technologyProperties": { "analyticsScope": "Basic usage metrics", "crossOrgInsight": "None", "reportingFrequency": "On-demand" } }, "coverage": { "technologies": [ "Service coverage analytics engine", "Gap analysis module" ], "technologyProperties": { "analyticsScope": "Coverage and gap analysis", "crossOrgInsight": "Anonymised overlap detection", "reportingFrequency": "Monthly" } }, "coordination": { "technologies": [ "Cross-organisation coordination dashboard", "Anonymised service mapping" ], "technologyProperties": { "analyticsScope": "Multi-organisation service landscape", "crossOrgInsight": "Service overlap + gap identification", "reportingFrequency": "Real-time dashboard" } } }, "prefillFrom": null, "briefSection": "Reporting and audit", "text": "What service history analytics do you currently have?", "ngoText": "What service history analytics do you currently have?" }, { "id": "holder-access-method", "type": "select", "options": [ { "label": "Mobile wallet app (smartphone required)", "value": "mobile-wallet" }, { "label": "Physical smart card with NFC or QR code", "value": "smart-card" }, { "label": "SMS/USSD-based access (feature phone compatible)", "value": "sms-ussd" }, { "label": "Hybrid: mobile app for those with smartphones, card for others", "value": "hybrid" } ], "propertyMapping": { "mobile-wallet": { "technologies": [ "Mobile holder app", "Credential wallet SDK", "Biometric authentication module" ], "technologyProperties": { "holderDevice": "Smartphone (Android/iOS)", "authMethod": "PIN + biometric", "offlineAccess": "Cached credentials available offline" } }, "smart-card": { "technologies": [ "Smart card holder platform", "Card provisioning service", "Card reader/NFC verifier" ], "technologyProperties": { "holderDevice": "Physical smart card", "authMethod": "Card + PIN", "offlineAccess": "Card-based presentation works offline" } }, "sms-ussd": { "technologies": [ "SMS/USSD holder interface", "Feature phone credential access", "OTP verification service" ], "technologyProperties": { "holderDevice": "Feature phone (SMS/USSD)", "authMethod": "OTP via SMS", "offlineAccess": "Limited \u2014 requires network for SMS" } }, "hybrid": { "technologies": [ "Mobile holder app", "Smart card holder platform", "Multi-channel credential access" ], "technologyProperties": { "holderDevice": "Smartphone + physical card fallback", "authMethod": "Biometric (mobile) or PIN (card)", "offlineAccess": "Both channels support offline presentation" } } }, "prefillFrom": null, "briefSection": "Credential access", "text": "How will individuals access and present their credentials or identity documents?", "ngoText": "How will individuals access and present their credentials or identity documents?" }, { "id": "beneficiary-choice", "label": "How will beneficiaries exercise choice in how they receive and use this service?", "type": "select", "briefSection": "Holder experience", "options": [ { "label": "Beneficiaries choose between delivery methods (cash, voucher, mobile money, direct)", "value": "delivery-choice" }, { "label": "Beneficiaries choose preferred merchants or service points", "value": "merchant-choice" }, { "label": "Beneficiaries control their own data sharing preferences", "value": "data-choice" }, { "label": "Multiple choice dimensions (delivery + merchant + data)", "value": "full-choice" }, { "label": "Limited choice: programme constraints determine delivery", "value": "limited" } ], "propertyMapping": { "delivery-choice": { "technologies": [], "technologyProperties": { "beneficiaryChoice": "Delivery method choice", "dignityDesign": "Beneficiaries select preferred receipt method" } }, "merchant-choice": { "technologies": [], "technologyProperties": { "beneficiaryChoice": "Merchant/service point choice", "dignityDesign": "Beneficiaries select where to redeem" } }, "data-choice": { "technologies": [], "technologyProperties": { "beneficiaryChoice": "Data sharing choice", "dignityDesign": "Beneficiaries control personal data sharing" } }, "full-choice": { "technologies": [], "technologyProperties": { "beneficiaryChoice": "Multi-dimensional choice", "dignityDesign": "Full beneficiary agency across delivery, merchant, and data" } }, "limited": { "technologies": [], "technologyProperties": { "beneficiaryChoice": "Limited by programme design", "dignityDesign": "Programme constraints; beneficiary informed of reasons" } } }, "text": "How will beneficiaries exercise choice in how they receive and use this service?" } ], "complexityFactors": { "relationships": 4, "operationalChange": 3, "dataCompliance": 4 }, "securityTier": "B", "suggestedCriteria": [ { "id": "SC-CREDENTIAL-EXCHANGE", "name": "Cross-Organisation Credential Exchange", "description": "Can service history credentials be easily shared between UNHCR, WFP, UNICEF, and local partners without building a shared database?", "weight": 0.3, "ratingGuide": { "5": "Standards-based credential exchange (W3C VC). Any compliant organisation can verify. No bilateral agreements needed.", "4": "Federated exchange within registered partner networks. New partners onboarded easily.", "3": "Credential sharing between pre-configured partner pairs. Each new partnership requires setup.", "2": "Export/import capability but manual processes required for sharing.", "1": "No cross-organisation sharing. Records locked to issuing organisation." } }, { "id": "SC-SELECTIVE-HISTORY", "name": "Selective Disclosure of Service History", "description": "Can a beneficiary share relevant service history (e.g. vaccination record) without revealing everything (e.g. cash assistance amounts, protection case notes)?", "weight": 0.25, "ratingGuide": { "5": "Granular selective disclosure \u2014 share individual service records independently. ZKP-based attribute proofs.", "4": "Category-level disclosure (health, education, cash). Can share one category without revealing others.", "3": "Service history can be filtered before sharing. Some fields redactable.", "2": "All-or-nothing sharing. Full history shared or none at all.", "1": "No selective disclosure. Full service record visible to any verifier." } }, { "id": "SC-OFFLINE-VERIFY", "name": "Offline Verification", "description": "Can credentials be verified at border crossings, field offices, or distribution points without internet connectivity?", "weight": 0.15, "ratingGuide": { "5": "Fully offline verification via portable proofs (QR code, NFC). No connectivity needed for any verification step.", "4": "Offline verification with periodic online sync for revocation checks.", "3": "Cached verification lists work offline for recent credentials. Older records need connectivity.", "2": "Online verification preferred. Limited offline fallback.", "1": "Requires constant connectivity for all verification." } }, { "id": "SC-DATA-CONTINUITY", "name": "Data Completeness & Continuity", "description": "Does the system prevent gaps in service history when beneficiaries move between organisations, countries, or programmes?", "weight": 0.15, "ratingGuide": { "5": "Continuous credential chain. Transfers between systems create no gaps. Full audit trail of custody transfers.", "4": "Minimal gap risk. Automated handoff protocols between organisations.", "3": "Some gap risk during transfers. Manual reconciliation available.", "2": "Gaps common during transfers. Requires re-registration at new organisation.", "1": "No continuity mechanism. Each organisation starts from scratch." } }, { "id": "SC-HUMANITARIAN-SYS", "name": "Humanitarian System Integration", "description": "Does the system integrate with the existing humanitarian registration and case management platforms that already hold beneficiary data?", "weight": 0.15, "ratingGuide": { "5": "Native connectors to the major humanitarian registration and case management platforms. Bi-directional sync.", "4": "API-based integration with 2-3 major platforms. One-directional at minimum.", "3": "Generic API available. Integration possible but requires custom development.", "2": "CSV/file-based import/export only. No live integration.", "1": "Proprietary system. No integration capability." } } ], "procurement": { "marketMaturity": "emerging", "primaryMode": "integrator-led", "alternativeModes": [ "tender" ], "reasoning": "Cross-border service history requires interagency integration.", "exampleProductCategories": [ "portable-credentials-platform", "digital-identity-rails" ], "partnerChannels": [], "lastReviewed": "2026-05-01" } }, { "id": "UC-B-029", "name": "Staff credential verification across jurisdictions", "category": "B", "subcategory": "Professional Credentials", "description": "Let staff prove their qualifications in each country where they work, and let employers check them quickly instead of writing to the issuing body.", "bCriteria": [ "B1", "B3", "B6" ], "requiredComponents": [ { "component": "credential-issuance", "description": "Professional credential issuance" }, { "component": "verification-mechanism", "description": "Verifiable credential verification" }, { "component": "holder-app", "description": "Staff credential wallet" }, { "component": "interoperability-layer", "description": "Cross-border credential recognition" } ], "conditionalComponents": [ { "component": "privacy-tech", "condition": "For selective disclosure of qualifications" } ], "crossCategoryDependencies": [], "p2TriggerConditions": { "description": "Activated when P2 shows multi-country staffing + credential portability needs + hiring verification", "rangeSignals": [ "countries >= 2", "staffCount >= 20+", "credentialVerification >= burdensome" ] }, "contextFieldsTemplate": [ { "field": "staffCount", "source": "P0 staffing", "description": "Number of staff" }, { "field": "credentialTypes", "source": "P0 HR requirements", "description": "Required qualifications" }, { "field": "jurisdictions", "source": "P0 operations", "description": "Countries of operation" }, { "field": "verificationsPerYear", "source": "P0 onboarding", "description": "Hiring frequency" } ], "implementationComplexity": "medium", "examples": { "note": "Professional credential verification", "references": [ { "name": "Dock.io Verifiable Credentials", "url": "https://www.dock.io/verifiable-credentials", "solved": "Verifiable professional credential issuance and verification across organisations" }, { "name": "Learning Machine (Hyland Credentials)", "url": "https://www.hylandcredentials.com/", "solved": "Blockchain-verified professional and academic credentials portable across jurisdictions" } ] }, "solutionQuestions": [ { "id": "credential-types-staff", "type": "select", "options": [ { "label": "Professional qualifications (degrees, certifications)", "value": "professional" }, { "label": "Security clearances and background checks", "value": "security" }, { "label": "Safeguarding training and compliance", "value": "safeguarding" }, { "label": "All of the above, comprehensive credential verification", "value": "comprehensive" } ], "propertyMapping": { "professional": { "technologies": [ "Professional credential verification engine", "University/institution DID registry" ], "technologyProperties": { "credentialScope": "Professional qualifications", "verificationSource": "Issuing institutions", "verificationDepth": "Certificate authenticity + currency" } }, "security": { "technologies": [ "Background check credential platform", "Security clearance verification module" ], "technologyProperties": { "credentialScope": "Security clearances", "verificationSource": "Background check agencies", "verificationDepth": "Full background verification + ongoing monitoring" } }, "safeguarding": { "technologies": [ "Safeguarding compliance credential engine", "Training completion verifier" ], "technologyProperties": { "credentialScope": "Safeguarding compliance", "verificationSource": "Training providers + HR systems", "verificationDepth": "Completion + currency + renewal tracking" } }, "comprehensive": { "technologies": [ "Unified staff credential platform", "Multi-source verification engine", "Credential aggregation wallet" ], "technologyProperties": { "credentialScope": "Full \u2014 professional + security + safeguarding", "verificationSource": "Multiple institutional sources", "verificationDepth": "Comprehensive with ongoing monitoring" } } }, "prefillFrom": null, "briefSection": "Credential issuance", "text": "What types of staff credentials need to be verified?", "ngoText": "What types of staff credentials need to be verified?" }, { "id": "jurisdiction-count", "type": "select", "options": [ { "label": "Single country: domestic operations", "value": "single" }, { "label": "2-5 countries: regional operations", "value": "regional" }, { "label": "5-20 countries: multi-regional operations", "value": "multi-regional" }, { "label": "20+ countries: global operations", "value": "global" } ], "propertyMapping": { "single": { "technologies": [ "Domestic credential verification platform" ], "technologyProperties": { "jurisdictionScope": "Single country", "regulatoryComplexity": "Low", "credentialTranslation": "Not required" } }, "regional": { "technologies": [ "Regional credential exchange network", "Multi-jurisdiction verification engine" ], "technologyProperties": { "jurisdictionScope": "Regional (2-5 countries)", "regulatoryComplexity": "Medium", "credentialTranslation": "Regional equivalency mapping" } }, "multi-regional": { "technologies": [ "Multi-regional credential platform", "Credential equivalency engine", "International verification network" ], "technologyProperties": { "jurisdictionScope": "Multi-regional (5-20 countries)", "regulatoryComplexity": "High", "credentialTranslation": "Multi-standard equivalency" } }, "global": { "technologies": [ "Global credential verification platform", "Universal credential translator", "International institution registry" ], "technologyProperties": { "jurisdictionScope": "Global (20+ countries)", "regulatoryComplexity": "Very high", "credentialTranslation": "Universal translation with local compliance" } } }, "prefillFrom": null, "briefSection": "Interoperability", "text": "How many jurisdictions does staff credential verification need to span?", "ngoText": "How many jurisdictions does staff credential verification need to span?" }, { "id": "staff-verification-frequency", "type": "select", "options": [ { "label": "At hiring/onboarding only", "value": "onboarding" }, { "label": "Annual re-verification", "value": "annual" }, { "label": "Continuous monitoring for expiry/revocation", "value": "continuous" } ], "propertyMapping": { "onboarding": { "technologies": [ "Onboarding verification workflow" ], "technologyProperties": { "verificationFrequency": "Once at onboarding", "monitoringType": "None after initial check", "expiryAlert": "Manual tracking" } }, "annual": { "technologies": [ "Scheduled re-verification engine", "Expiry tracking module" ], "technologyProperties": { "verificationFrequency": "Annual", "monitoringType": "Scheduled batch re-verification", "expiryAlert": "Automated annual reminder" } }, "continuous": { "technologies": [ "Continuous credential monitoring service", "Revocation alert engine", "Credential status subscription" ], "technologyProperties": { "verificationFrequency": "Continuous real-time", "monitoringType": "Live revocation + expiry monitoring", "expiryAlert": "Real-time alerts" } } }, "prefillFrom": null, "briefSection": "Verification and privacy", "text": "How frequently are staff credentials verified?", "ngoText": "How frequently are staff credentials verified?" }, { "id": "staff-holder-interface", "type": "select", "options": [ { "label": "Mobile app for staff credential management", "value": "mobile-app" }, { "label": "Web portal integrated with HR system", "value": "web-hr" }, { "label": "Both mobile app and web portal", "value": "both" } ], "propertyMapping": { "mobile-app": { "technologies": [ "Staff credential wallet app" ], "technologyProperties": { "staffInterface": "Mobile application", "hrIntegration": "API sync with HR", "selfService": "Full self-service credential management" } }, "web-hr": { "technologies": [ "HR-integrated credential portal", "HRIS connection module" ], "technologyProperties": { "staffInterface": "Web portal in HRIS", "hrIntegration": "Native HRIS integration", "selfService": "Web-based self-service" } }, "both": { "technologies": [ "Staff credential wallet app", "HR-integrated credential portal" ], "technologyProperties": { "staffInterface": "Mobile app + web portal", "hrIntegration": "Dual-channel HRIS integration", "selfService": "Full mobile + web self-service" } } }, "prefillFrom": null, "briefSection": "Holder experience", "text": "How will staff interact with their credential wallet?", "ngoText": "How will staff interact with their credential wallet?" }, { "id": "staff-reporting", "type": "select", "options": [ { "label": "HR compliance dashboard (credential status overview)", "value": "hr-dashboard" }, { "label": "Donor compliance reporting (staff qualification evidence)", "value": "donor-compliance" }, { "label": "Regulatory audit trail (full verification history)", "value": "regulatory-audit" } ], "propertyMapping": { "hr-dashboard": { "technologies": [ "HR credential compliance dashboard" ], "technologyProperties": { "reportingScope": "Internal HR", "complianceView": "Staff credential status overview", "auditDepth": "Summary" } }, "donor-compliance": { "technologies": [ "Donor compliance reporting module", "Staff qualification evidence export" ], "technologyProperties": { "reportingScope": "Donor accountability", "complianceView": "Qualified staff metrics by programme", "auditDepth": "Aggregated evidence" } }, "regulatory-audit": { "technologies": [ "Regulatory audit trail", "Full verification history logger" ], "technologyProperties": { "reportingScope": "Regulatory compliance", "complianceView": "Complete verification audit trail", "auditDepth": "Every verification logged" } } }, "prefillFrom": null, "briefSection": "Reporting and audit", "text": "What credential compliance reporting is needed?", "ngoText": "What credential compliance reporting is needed?" }, { "id": "staff-privacy", "type": "select", "options": [ { "label": "Standard HR data protection", "value": "standard" }, { "label": "GDPR/strict data protection (EU staff or EU-funded)", "value": "gdpr" }, { "label": "Security-sensitive (conflict zones, sensitive roles)", "value": "security-sensitive" } ], "propertyMapping": { "standard": { "technologies": [ "Encrypted credential store", "Role-based access control" ], "technologyProperties": { "privacyLevel": "Standard HR data protection", "dataResidency": "Organisation-managed", "accessControl": "Role-based" } }, "gdpr": { "technologies": [ "GDPR-compliant credential platform", "Data minimisation engine", "Right-to-erasure module" ], "technologyProperties": { "privacyLevel": "GDPR compliance", "dataResidency": "EU-compliant hosting", "accessControl": "Consent-based with data subject rights" } }, "security-sensitive": { "technologies": [ "Security-hardened credential vault", "Compartmentalised access control" ], "technologyProperties": { "privacyLevel": "Security-hardened", "dataResidency": "Air-gapped where needed", "accessControl": "Need-to-know compartmentalised" } } }, "prefillFrom": null, "briefSection": "Consent and governance", "text": "What privacy requirements apply to staff credential data?", "ngoText": "What privacy requirements apply to staff credential data?" }, { "id": "holder-access-method", "type": "select", "options": [ { "label": "Mobile wallet app (smartphone required)", "value": "mobile-wallet" }, { "label": "Physical smart card with NFC or QR code", "value": "smart-card" }, { "label": "SMS/USSD-based access (feature phone compatible)", "value": "sms-ussd" }, { "label": "Hybrid: mobile app for those with smartphones, card for others", "value": "hybrid" } ], "propertyMapping": { "mobile-wallet": { "technologies": [ "Mobile holder app", "Credential wallet SDK", "Biometric authentication module" ], "technologyProperties": { "holderDevice": "Smartphone (Android/iOS)", "authMethod": "PIN + biometric", "offlineAccess": "Cached credentials available offline" } }, "smart-card": { "technologies": [ "Smart card holder platform", "Card provisioning service", "Card reader/NFC verifier" ], "technologyProperties": { "holderDevice": "Physical smart card", "authMethod": "Card + PIN", "offlineAccess": "Card-based presentation works offline" } }, "sms-ussd": { "technologies": [ "SMS/USSD holder interface", "Feature phone credential access", "OTP verification service" ], "technologyProperties": { "holderDevice": "Feature phone (SMS/USSD)", "authMethod": "OTP via SMS", "offlineAccess": "Limited \u2014 requires network for SMS" } }, "hybrid": { "technologies": [ "Mobile holder app", "Smart card holder platform", "Multi-channel credential access" ], "technologyProperties": { "holderDevice": "Smartphone + physical card fallback", "authMethod": "Biometric (mobile) or PIN (card)", "offlineAccess": "Both channels support offline presentation" } } }, "prefillFrom": null, "briefSection": "Credential access", "text": "How will individuals access and present their credentials or identity documents?", "ngoText": "How will individuals access and present their credentials or identity documents?" } ], "complexityFactors": { "relationships": 2, "operationalChange": 2, "dataCompliance": 3 }, "suggestedCriteria": [ { "id": "SC-VERIFY-SPEED", "name": "Verification Speed & Reliability", "description": "This measures how quickly staff credentials can be verified during hiring, deployment, or partner due diligence. Operational urgency varies from routine to emergency deployment.", "weight": 0.25, "ratingGuide": { "5": "Real-time verification (under 30 seconds). Automated checks against source registries. 99.9% uptime.", "4": "Near-instant verification (under 5 minutes). Reliable automated process.", "3": "Verification within hours. Some manual steps involved.", "2": "Verification takes 1-2 business days. Primarily manual process.", "1": "Multi-day verification. Fully manual, paper-based process." } }, { "id": "SC-MULTI-JURISDICTION-COV", "name": "Multi-Jurisdiction Coverage", "description": "The system verifies credentials across all countries where the NGO operates. International staff may hold qualifications from multiple jurisdictions.", "weight": 0.25, "ratingGuide": { "5": "Covers 50+ countries. Direct registry connections in major humanitarian operating regions (Middle East, East Africa, South/Southeast Asia).", "4": "Covers 20-50 countries. Good coverage of key operating regions.", "3": "Covers 10-20 countries. Some gaps in less common jurisdictions.", "2": "Covers 5-10 countries. Significant geographic limitations.", "1": "Single country or region only." } }, { "id": "SC-CONTINUOUS-MONITOR", "name": "Continuous Monitoring & Alerts", "description": "The system proactively alerts when credentials expire, are revoked, or when background check status changes. Critical for safeguarding compliance.", "weight": 0.2, "ratingGuide": { "5": "Real-time monitoring with instant alerts on expiry, revocation, or status change. Automated renewal reminders.", "4": "Daily monitoring with alerts. Renewal tracking dashboard.", "3": "Weekly or monthly batch checks. Manual expiry tracking.", "2": "Point-in-time checks only. No ongoing monitoring.", "1": "One-time verification. No monitoring after initial check." } }, { "id": "SC-SAFEGUARDING", "name": "Safeguarding Compliance", "description": "The system meets child protection and safeguarding standards. Includes DBS/police checks, safeguarding training verification, and incident flagging.", "weight": 0.15, "ratingGuide": { "5": "Comprehensive safeguarding framework. Criminal record checks, safeguarding training, incident reporting all integrated. Meets Inter-Agency Standing Committee standards.", "4": "Safeguarding checks integrated. Covers criminal records and training verification.", "3": "Basic safeguarding checks available. Some manual processes.", "2": "Criminal record check only. No safeguarding training verification.", "1": "No safeguarding-specific capabilities." } }, { "id": "SC-HR-INTEGRATION", "name": "HR System Integration", "description": "Does the system connect to existing HR, payroll, and staff management platforms used by the organisation?", "weight": 0.15, "ratingGuide": { "5": "Native connectors to major HR platforms. Bi-directional sync.", "4": "API integration with 2-3 major HR platforms.", "3": "Generic API. Integration possible with custom development.", "2": "CSV/file-based export to HR systems.", "1": "No integration capability. Standalone system." } } ], "procurement": { "marketMaturity": "emerging", "primaryMode": "tender", "alternativeModes": [ "off-the-shelf" ], "reasoning": "HR credential verification platforms growing; suitable for tender.", "exampleProductCategories": [ "hr-credential-verification", "workforce-credentialing-saas" ], "partnerChannels": [], "lastReviewed": "2026-05-01" } }, { "id": "UC-B-030", "name": "Volunteer identity and background verification", "category": "B", "subcategory": "Identity Verification", "description": "Check a volunteer's identity and background once, and let your other sites and partners accept the result, so checks are not repeated.", "bCriteria": [ "B1", "B3", "B6" ], "requiredComponents": [ { "component": "identity-protocol", "description": "Volunteer identity verification" }, { "component": "credential-issuance", "description": "Volunteer credentials" }, { "component": "verification-mechanism", "description": "Background check proofs" }, { "component": "consent-management", "description": "Volunteer consent records" } ], "conditionalComponents": [ { "component": "privacy-tech", "condition": "If sensitive background information" }, { "component": "biometric-capture", "condition": "For face verification" } ], "crossCategoryDependencies": [], "p2TriggerConditions": { "description": "Activated when P2 shows large volunteer base + background check needs + child protection concerns", "rangeSignals": [ "volunteers >= 50+", "backgroundCheck >= required", "childContact >= true" ] }, "contextFieldsTemplate": [ { "field": "volunteerCount", "source": "P2 programme scale", "description": "Number of volunteers" }, { "field": "checkTypes", "source": "P0 safeguarding policies", "description": "Background check requirements" }, { "field": "childSafeguarding", "source": "P0 Q19-21", "description": "Child protection requirements" }, { "field": "verificationSpeed", "source": "P2 onboarding", "description": "Required verification timeline" } ], "implementationComplexity": "medium", "examples": { "note": "Humanitarian volunteer screening", "references": [ { "name": "Volunteer Screening with Verifiable Credentials", "url": "https://www.w3.org/TR/vc-data-model/", "solved": "W3C Verifiable Credentials standard used for portable volunteer screening across organisations" }, { "name": "InterAction NGO Safeguarding Standards", "url": "https://www.interaction.org/", "solved": "Standards for volunteer and staff screening in humanitarian settings" } ] }, "solutionQuestions": [ { "id": "background-check-scope", "type": "select", "options": [ { "label": "Identity verification only", "value": "identity-only" }, { "label": "Identity + criminal record check", "value": "criminal" }, { "label": "Identity + criminal + safeguarding (working with children)", "value": "safeguarding" }, { "label": "Comprehensive (identity + criminal + safeguarding + references)", "value": "comprehensive" } ], "propertyMapping": { "identity-only": { "technologies": [ "Identity verification module" ], "technologyProperties": { "checkScope": "Identity only", "complianceLevel": "Basic", "checkDuration": "Minutes" } }, "criminal": { "technologies": [ "Identity verification module", "Criminal record check connection" ], "technologyProperties": { "checkScope": "Identity + criminal", "complianceLevel": "Standard", "checkDuration": "Hours to days" } }, "safeguarding": { "technologies": [ "Identity verification module", "Criminal record check connection", "Safeguarding clearance engine", "Child protection registry check" ], "technologyProperties": { "checkScope": "Identity + criminal + child protection", "complianceLevel": "Enhanced (child safeguarding)", "checkDuration": "Days" } }, "comprehensive": { "technologies": [ "Comprehensive verification platform", "Multi-source background check engine", "Reference verification module" ], "technologyProperties": { "checkScope": "Full \u2014 identity + criminal + safeguarding + references", "complianceLevel": "Maximum", "checkDuration": "Days to weeks" } } }, "prefillFrom": null, "briefSection": "Verification and privacy", "text": "What background checks are required for your volunteers?", "ngoText": "What background checks are required for your volunteers?" }, { "id": "volunteer-credential-use", "type": "select", "options": [ { "label": "Access control to programmes/sites only", "value": "access-control" }, { "label": "Presented to beneficiaries/communities for trust", "value": "community-trust" }, { "label": "Shared with partner organisations", "value": "partner-sharing" }, { "label": "All of the above", "value": "all" } ], "propertyMapping": { "access-control": { "technologies": [ "Volunteer access credential", "Site access control integration" ], "technologyProperties": { "credentialUse": "Internal access control", "presentationContext": "At programme sites", "sharingScope": "Internal only" } }, "community-trust": { "technologies": [ "Community-facing volunteer credential", "Visual verification card" ], "technologyProperties": { "credentialUse": "Community trust building", "presentationContext": "Field interactions", "sharingScope": "Public-facing credential" } }, "partner-sharing": { "technologies": [ "Portable volunteer credential", "Inter-organisation verification API" ], "technologyProperties": { "credentialUse": "Cross-organisation portability", "presentationContext": "Partner onboarding", "sharingScope": "Partner consortium" } }, "all": { "technologies": [ "Multi-purpose volunteer credential platform", "Tiered credential presentation" ], "technologyProperties": { "credentialUse": "Access + community + partner", "presentationContext": "Adaptive", "sharingScope": "Internal + external" } } }, "prefillFrom": null, "briefSection": "Credential issuance", "text": "How will volunteer credentials be used after verification?", "ngoText": "How will volunteer credentials be used after verification?" }, { "id": "volunteer-privacy", "type": "select", "options": [ { "label": "Standard: verified status shared, details private", "value": "standard" }, { "label": "High privacy: privacy-preserving verification of clearance", "value": "zkp-clearance" }, { "label": "Tiered: different levels depending on the role sensitivity", "value": "tiered" }, { "label": "Not sure, need guidance on volunteer data privacy", "value": "unsure" } ], "propertyMapping": { "standard": { "technologies": [ "Status-only credential (pass/fail)", "Encrypted detail storage" ], "technologyProperties": { "privacyLevel": "Status shared, details encrypted", "disclosureModel": "Binary clearance status", "backgroundDetailAccess": "HR only" } }, "zkp-clearance": { "technologies": [ "Zero-knowledge clearance proof", "Privacy-preserving verification" ], "technologyProperties": { "privacyLevel": "ZKP \u2014 prove cleared without details", "disclosureModel": "Zero-knowledge proof of clearance", "backgroundDetailAccess": "Never disclosed" } }, "tiered": { "technologies": [ "Role-based credential disclosure", "Tiered verification" ], "technologyProperties": { "privacyLevel": "Role-dependent disclosure", "disclosureModel": "Tiered based on role sensitivity", "backgroundDetailAccess": "Varies by role" } }, "unsure": { "technologies": [ "Privacy assessment needed" ], "technologyProperties": { "privacyLevel": "TBD", "disclosureModel": "TBD", "backgroundDetailAccess": "TBD" } } }, "prefillFrom": null, "briefSection": "Consent and governance", "text": "What privacy level is needed for volunteer background data?", "ngoText": "What privacy level is needed for volunteer background data?" }, { "id": "volunteer-reporting", "type": "select", "options": [ { "label": "Basic volunteer status dashboard", "value": "basic" }, { "label": "Compliance tracking with expiry alerts", "value": "compliance" }, { "label": "Full audit trail for safeguarding compliance", "value": "full-audit" } ], "propertyMapping": { "basic": { "technologies": [ "Volunteer status dashboard" ], "technologyProperties": { "reportingScope": "Aggregate status", "alerting": "None", "auditDepth": "Summary" } }, "compliance": { "technologies": [ "Compliance tracking dashboard", "Expiry alert engine" ], "technologyProperties": { "reportingScope": "Credential status + expiry", "alerting": "Automated expiry alerts", "auditDepth": "Standard" } }, "full-audit": { "technologies": [ "Safeguarding audit trail", "Full verification history" ], "technologyProperties": { "reportingScope": "Complete safeguarding compliance", "alerting": "Real-time non-compliance alerts", "auditDepth": "Every verification logged" } } }, "prefillFrom": null, "briefSection": "Reporting and audit", "text": "What volunteer credential reporting do you currently have?", "ngoText": "What volunteer credential reporting do you currently have?" }, { "id": "sq-UC-B-030-001", "type": "single-select", "options": [ { "value": "instant-revocation", "label": "Instant revocation" }, { "value": "grace-period", "label": "Grace period" }, { "value": "suspend-pending-review", "label": "Suspend pending review" }, { "value": "automatic-expiry", "label": "Automatic expiry" }, { "value": "multi-party-revocation", "label": "Multi-party revocation" } ], "propertyMapping": { "instant-revocation": { "technologies": [ "revocation-system", "immediate-deactivation" ], "technologyProperties": {} }, "grace-period": { "technologies": [ "grace-period-logic", "scheduled-revocation" ], "technologyProperties": {} }, "suspend-pending-review": { "technologies": [ "suspension-system", "review-workflow" ], "technologyProperties": {} }, "automatic-expiry": { "technologies": [ "expiry-logic", "scheduled-expiry" ], "technologyProperties": {} }, "multi-party-revocation": { "technologies": [ "multi-sig-revocation", "approval-required" ], "technologyProperties": {} } }, "briefSection": "operations", "text": "What credential revocation process is needed when a volunteer's status changes?", "ngoText": "What credential revocation process is needed when a volunteer's status changes?" }, { "id": "consent-management-approach", "type": "select", "options": [ { "label": "Granular consent: individuals control each data element shared", "value": "granular" }, { "label": "Tiered consent: pre-defined levels (basic, standard, full)", "value": "tiered" }, { "label": "Blanket consent with opt-out for specific data categories", "value": "blanket-optout" }, { "label": "Guardian/proxy consent for vulnerable populations", "value": "guardian-proxy" } ], "propertyMapping": { "granular": { "technologies": [ "Granular consent management platform", "Consent ledger", "Privacy-preserving disclosure engine" ], "technologyProperties": { "consentGranularity": "Per-attribute", "consentStorage": "Digital consent receipts", "revocation": "Real-time revocable" } }, "tiered": { "technologies": [ "Tiered consent management system", "Consent ledger", "Pre-defined disclosure profiles" ], "technologyProperties": { "consentGranularity": "Pre-defined tiers", "consentStorage": "Digital consent receipts", "revocation": "Tier-level revocation" } }, "blanket-optout": { "technologies": [ "Consent management platform", "Consent ledger", "Opt-out tracking service" ], "technologyProperties": { "consentGranularity": "Broad with category opt-outs", "consentStorage": "Digital consent records", "revocation": "Category-level opt-out" } }, "guardian-proxy": { "technologies": [ "Guardian consent management platform", "Consent ledger", "Proxy delegation service" ], "technologyProperties": { "consentGranularity": "Guardian-managed on behalf of individual", "consentStorage": "Digital with guardian chain of authority", "revocation": "Guardian or individual (when able)" } } }, "prefillFrom": null, "briefSection": "Privacy and consent", "text": "How do you currently manage consent for beneficiary data collection and sharing?", "ngoText": "How do you currently manage consent for beneficiary data collection and sharing?" } ], "complexityFactors": { "relationships": 2, "operationalChange": 2, "dataCompliance": 3 }, "suggestedCriteria": [ { "id": "SC-BACKGROUND-THOROUGH", "name": "Background Check Thoroughness", "description": "This measures how comprehensive the background checks are. Includes criminal records, safeguarding history, reference checks, and sanctions screening.", "weight": 0.3, "ratingGuide": { "5": "Comprehensive multi-source checks: criminal records (multi-jurisdiction), safeguarding databases, reference verification, sanctions lists, social media screening.", "4": "Criminal records + safeguarding + reference checks across key jurisdictions.", "3": "Criminal record and basic reference checks. Limited jurisdiction coverage.", "2": "Single-jurisdiction criminal record check only.", "1": "Basic identity verification only. No background screening." } }, { "id": "SC-VOLUNTEER-SPEED", "name": "Onboarding Verification Speed", "description": "This measures how quickly volunteers can be verified and cleared. Volunteer programmes often need rapid onboarding for seasonal or emergency surges.", "weight": 0.2, "ratingGuide": { "5": "Under 24 hours for standard checks. Express pathway (under 4 hours) for pre-screened returning volunteers.", "4": "1-3 days for full background check. Returning volunteers fast-tracked.", "3": "3-7 days standard processing. Some expedited options.", "2": "1-2 weeks processing time. No expedited pathway.", "1": "Over 2 weeks. Fully manual process." } }, { "id": "SC-CHILD-PROTECT", "name": "Child Protection Standards", "description": "Does the system meet organisational and legal safeguarding requirements for volunteers working with children and vulnerable adults?", "weight": 0.2, "ratingGuide": { "5": "Purpose-built for safeguarding. Meets Keeping Children Safe standards. Tiered clearance levels. Automatic flagging of concerns.", "4": "Comprehensive safeguarding checks. Meets major national standards (DBS, Working with Children Check).", "3": "Basic safeguarding checks. Meets minimum legal requirements.", "2": "Safeguarding flagged but not enforced. Organisation must manage compliance.", "1": "No safeguarding-specific features." } }, { "id": "SC-VOLUNTEER-PORTABLE", "name": "Credential Portability", "description": "Volunteers can reuse their verification across different organisations. Reduces duplicate screening when volunteers work with multiple NGOs.", "weight": 0.15, "ratingGuide": { "5": "Portable credentials accepted by multiple organisations. Volunteer controls sharing. Industry-standard format.", "4": "Credentials shareable within partner networks. Verification recognised by member organisations.", "3": "Credentials exportable. Receiving organisation may require additional checks.", "2": "Limited portability. Most checks must be repeated at each organisation.", "1": "No portability. Full re-screening required at every organisation." } }, { "id": "SC-PRIVACY-COMPLIANCE", "name": "Privacy & Data Compliance", "description": "The system handles sensitive background check data in compliance with GDPR and local data protection laws. Criminal record data is specially protected under most frameworks.", "weight": 0.15, "ratingGuide": { "5": "GDPR Article 10 compliant (special category criminal data). Data minimisation. Automated retention/deletion schedules. Privacy impact assessment included.", "4": "Strong privacy controls. Data retention policies. Compliant with major frameworks.", "3": "Basic privacy compliance. Data protection but manual retention management.", "2": "Limited privacy controls. Relies on organisation to manage data retention.", "1": "No specific privacy features for sensitive background data." } } ], "procurement": { "marketMaturity": "emerging", "primaryMode": "rfq", "alternativeModes": [ "off-the-shelf" ], "reasoning": "Volunteer ID and background verification SaaS available.", "exampleProductCategories": [ "volunteer-management-saas", "background-check-platform" ], "partnerChannels": [], "lastReviewed": "2026-05-01" } }, { "id": "UC-B-031", "name": "Health worker and teacher certification verification", "category": "B", "subcategory": "Professional Credentials", "description": "Confirm that a health worker's or teacher's licence is genuine and current, without a slow exchange with the licensing body each time.", "bCriteria": [ "B1", "B3", "B6" ], "requiredComponents": [ { "component": "credential-issuance", "description": "Professional certification issuance" }, { "component": "verification-mechanism", "description": "License verification proofs" }, { "component": "holder-app", "description": "Professional credential wallet" }, { "component": "interoperability-layer", "description": "Verification against registries" } ], "conditionalComponents": [ { "component": "identity-verification", "condition": "For initial credential issuance" }, { "component": "privacy-tech", "condition": "If sensitive performance data" } ], "crossCategoryDependencies": [], "p2TriggerConditions": { "description": "Activated when P2 shows health/education delivery + credential verification needs + distributed workers", "rangeSignals": [ "workersCount >= 10+", "credentialVerification >= critical", "distributedDelivery >= true" ] }, "contextFieldsTemplate": [ { "field": "workerType", "source": "P0 programmes", "description": "Health workers or teachers" }, { "field": "workerCount", "source": "P2 scale", "description": "Number of workers" }, { "field": "certificationStandards", "source": "P0 Q19-21", "description": "Required certifications" }, { "field": "verificationFrequency", "source": "P2 M&E", "description": "Ongoing verification needs" } ], "implementationComplexity": "medium", "examples": { "note": "Health and education credential verification", "references": [ { "name": "Blockcerts (MIT/Hyland)", "url": "https://www.blockcerts.org/", "solved": "Open standard for blockchain-verified professional and academic certificates" }, { "name": "WHO Health Workforce Registry Guidelines", "url": "https://www.who.int/hrh/resources/en/", "solved": "Standards for health workforce credential verification across humanitarian settings" } ] }, "solutionQuestions": [ { "id": "worker-type", "type": "select", "options": [ { "label": "Community health workers (CHWs)", "value": "chw" }, { "label": "Qualified health professionals (nurses, doctors)", "value": "health-professional" }, { "label": "Teachers and education staff", "value": "teachers" }, { "label": "Mixed, both health workers and educators", "value": "mixed" } ], "propertyMapping": { "chw": { "technologies": [ "CHW certification platform", "Training completion credential engine" ], "technologyProperties": { "workerType": "Community health workers", "certificationSource": "Training programmes", "verificationComplexity": "Low-medium (training-based)" } }, "health-professional": { "technologies": [ "Professional license verification platform", "National registry connection", "Continuing education tracker" ], "technologyProperties": { "workerType": "Health professionals", "certificationSource": "National licensing bodies", "verificationComplexity": "High (multi-jurisdiction licensing)" } }, "teachers": { "technologies": [ "Teacher certification platform", "Education authority connection" ], "technologyProperties": { "workerType": "Teachers/educators", "certificationSource": "Education authorities", "verificationComplexity": "Medium (national certification standards)" } }, "mixed": { "technologies": [ "Multi-profession certification platform", "Adaptive verification engine" ], "technologyProperties": { "workerType": "Health + education staff", "certificationSource": "Multiple authorities", "verificationComplexity": "High (multi-profession, multi-jurisdiction)" } } }, "prefillFrom": null, "briefSection": "Credential issuance", "text": "What type of professional workers need certification verification?", "ngoText": "What type of professional workers need certification verification?" }, { "id": "cert-verification-source", "type": "select", "options": [ { "label": "Paper certificates checked manually", "value": "paper-manual" }, { "label": "National/regional registries exist but are hard to access", "value": "registry-inaccessible" }, { "label": "No formal registry, rely on employer references", "value": "no-registry" }, { "label": "Digital registries available in some but not all countries", "value": "partial-digital" } ], "propertyMapping": { "paper-manual": { "technologies": [ "Document digitisation module", "Certificate OCR and verification engine" ], "technologyProperties": { "currentState": "Paper-based", "digitisationNeeded": "Full digitisation", "verificationGap": "No tamper-proofing" } }, "registry-inaccessible": { "technologies": [ "Registry API connection", "Cached registry mirror" ], "technologyProperties": { "currentState": "Registry exists but inaccessible", "digitisationNeeded": "Bridge to existing registry", "verificationGap": "Access barriers" } }, "no-registry": { "technologies": [ "Credential issuance platform", "Employer attestation module", "Training record credential engine" ], "technologyProperties": { "currentState": "No formal registry", "digitisationNeeded": "Build from scratch", "verificationGap": "No authoritative source" } }, "partial-digital": { "technologies": [ "Multi-source verification aggregator", "Registry federation layer" ], "technologyProperties": { "currentState": "Partial digital coverage", "digitisationNeeded": "Gap-fill for non-digital", "verificationGap": "Inconsistent coverage" } } }, "prefillFrom": null, "briefSection": "Verification and privacy", "text": "How are certifications currently verified?", "ngoText": "How are certifications currently verified?" }, { "id": "cert-portability", "type": "select", "options": [ { "label": "Single-country verification only", "value": "single-country" }, { "label": "Regional portability (neighbouring countries)", "value": "regional" }, { "label": "International portability for mobile workforce", "value": "international" } ], "propertyMapping": { "single-country": { "technologies": [ "National certification credential platform" ], "technologyProperties": { "portability": "Domestic only", "equivalencyMapping": "Not required", "interoperability": "National standards" } }, "regional": { "technologies": [ "Regional credential exchange", "Certification equivalency engine" ], "technologyProperties": { "portability": "Regional", "equivalencyMapping": "Regional mutual recognition", "interoperability": "Regional agreement standards" } }, "international": { "technologies": [ "International credential platform", "WHO/UNESCO equivalency alignment tool", "Universal credential translator" ], "technologyProperties": { "portability": "International", "equivalencyMapping": "International equivalency (WHO/UNESCO)", "interoperability": "W3C VC global standards" } } }, "prefillFrom": null, "briefSection": "Interoperability", "text": "Do professional certifications need to be recognised across borders?", "ngoText": "Do professional certifications need to be recognised across borders?" }, { "id": "cert-renewal-tracking", "type": "select", "options": [ { "label": "One-time verification: no renewal tracking", "value": "one-time" }, { "label": "Annual renewal tracking with alerts", "value": "annual-renewal" }, { "label": "Continuing professional development (CPD) credit tracking", "value": "cpd-tracking" } ], "propertyMapping": { "one-time": { "technologies": [ "Static credential issuance" ], "technologyProperties": { "renewalTracking": "None", "cpdTracking": "None", "alerting": "None" } }, "annual-renewal": { "technologies": [ "Credential lifecycle management", "Renewal alert engine" ], "technologyProperties": { "renewalTracking": "Annual renewal cycle", "cpdTracking": "Basic", "alerting": "Automated renewal reminders" } }, "cpd-tracking": { "technologies": [ "CPD credit tracking platform", "Micro-credential issuance engine", "Learning management integration" ], "technologyProperties": { "renewalTracking": "Continuous CPD-based", "cpdTracking": "Full CPD credit tracking", "alerting": "CPD compliance alerts" } } }, "prefillFrom": null, "briefSection": "Credential issuance", "text": "Is ongoing certification renewal and continuing education tracking needed?", "ngoText": "Is ongoing certification renewal and continuing education tracking needed?" }, { "id": "cert-reporting", "type": "select", "options": [ { "label": "Programme staffing compliance dashboard", "value": "programme" }, { "label": "Donor reporting on qualified staff metrics", "value": "donor" }, { "label": "Regulatory compliance reporting to health/education authorities", "value": "regulatory" } ], "propertyMapping": { "programme": { "technologies": [ "Staffing compliance dashboard" ], "technologyProperties": { "reportingScope": "Internal programme", "metrics": "Qualified vs unqualified staff ratios", "auditDepth": "Summary" } }, "donor": { "technologies": [ "Donor reporting module", "Staff qualification metrics engine" ], "technologyProperties": { "reportingScope": "Donor accountability", "metrics": "Qualified staff metrics per programme", "auditDepth": "Aggregated evidence" } }, "regulatory": { "technologies": [ "Regulatory reporting module", "Authority data exchange" ], "technologyProperties": { "reportingScope": "Health/education authority", "metrics": "Full certification compliance", "auditDepth": "Individual-level for authorities" } } }, "prefillFrom": null, "briefSection": "Reporting and audit", "text": "What certification compliance reporting is needed?", "ngoText": "What certification compliance reporting is needed?" }, { "id": "holder-access-method", "type": "select", "options": [ { "label": "Mobile wallet app (smartphone required)", "value": "mobile-wallet" }, { "label": "Physical smart card with NFC or QR code", "value": "smart-card" }, { "label": "SMS/USSD-based access (feature phone compatible)", "value": "sms-ussd" }, { "label": "Hybrid: mobile app for those with smartphones, card for others", "value": "hybrid" } ], "propertyMapping": { "mobile-wallet": { "technologies": [ "Mobile holder app", "Credential wallet SDK", "Biometric authentication module" ], "technologyProperties": { "holderDevice": "Smartphone (Android/iOS)", "authMethod": "PIN + biometric", "offlineAccess": "Cached credentials available offline" } }, "smart-card": { "technologies": [ "Smart card holder platform", "Card provisioning service", "Card reader/NFC verifier" ], "technologyProperties": { "holderDevice": "Physical smart card", "authMethod": "Card + PIN", "offlineAccess": "Card-based presentation works offline" } }, "sms-ussd": { "technologies": [ "SMS/USSD holder interface", "Feature phone credential access", "OTP verification service" ], "technologyProperties": { "holderDevice": "Feature phone (SMS/USSD)", "authMethod": "OTP via SMS", "offlineAccess": "Limited \u2014 requires network for SMS" } }, "hybrid": { "technologies": [ "Mobile holder app", "Smart card holder platform", "Multi-channel credential access" ], "technologyProperties": { "holderDevice": "Smartphone + physical card fallback", "authMethod": "Biometric (mobile) or PIN (card)", "offlineAccess": "Both channels support offline presentation" } } }, "prefillFrom": null, "briefSection": "Credential access", "text": "How will individuals access and present their credentials or identity documents?", "ngoText": "How will individuals access and present their credentials or identity documents?" } ], "complexityFactors": { "relationships": 3, "operationalChange": 2, "dataCompliance": 3 }, "suggestedCriteria": [ { "id": "SC-REGISTRY-CONNECT", "name": "Professional Registry Connectivity", "description": "Does the system connect to national and regional professional registries (medical boards, teaching councils) for real-time credential verification?", "weight": 0.3, "ratingGuide": { "5": "Direct API connections to 20+ national registries. Real-time verification against source. Automated status updates.", "4": "Connections to 10-20 registries. Near-real-time verification.", "3": "Connections to 5-10 registries. Batch verification supported.", "2": "Limited registry connections. Manual verification for most jurisdictions.", "1": "No registry connections. Credential verification is entirely manual." } }, { "id": "SC-CPD-TRACKING", "name": "Continuing Professional Development Tracking", "description": "Does the system track ongoing training, certification renewal, and professional development requirements for health workers and teachers?", "weight": 0.2, "ratingGuide": { "5": "Automated CPD tracking. Links to training providers. Renewal reminders. CPD credit accumulation dashboard.", "4": "CPD hours logged with evidence attachments. Renewal reminders.", "3": "Basic CPD recording. Manual tracking of hours and requirements.", "2": "Initial certification only. No ongoing development tracking.", "1": "No CPD tracking capability." } }, { "id": "SC-MULTI-COUNTRY-QUAL", "name": "Multi-Country Qualification Recognition", "description": "The system maps professional qualifications across different national standards. A nurse qualified in Kenya may need credential recognition in Jordan.", "weight": 0.2, "ratingGuide": { "5": "Automated qualification mapping across national frameworks. Equivalency assessment built in.", "4": "Mapping between major national systems. Manual review for complex cases.", "3": "Basic equivalency tables available. Primarily manual mapping.", "2": "Single-country qualification tracking. No cross-country mapping.", "1": "No multi-country capability." } }, { "id": "SC-VERIFY-ACCESSIBILITY", "name": "Verification Speed & Accessibility", "description": "This measures how quickly and easily credentials can be verified in field settings. Health facilities and schools in remote areas need fast verification.", "weight": 0.15, "ratingGuide": { "5": "Instant QR code verification. Works offline. Mobile-first design for field use.", "4": "Fast verification (under 1 minute). Works on smartphones with intermittent connectivity.", "3": "Verification within minutes. Requires connectivity.", "2": "Online-only verification. Web-based interface.", "1": "Manual verification process. Requires office access and connectivity." } }, { "id": "SC-TECH-MATURITY-CERT", "name": "Technical Maturity", "description": "The system is production-ready with proven deployments. Health and education certification verification requires reliable, well-supported technology.", "weight": 0.15, "ratingGuide": { "5": "Production deployments across multiple countries. Comprehensive documentation. Dedicated support team. 99.9% uptime SLA.", "4": "Multiple production deployments. Good documentation and support.", "3": "Pilot deployments or limited production use. Adequate documentation.", "2": "Beta stage. Sparse documentation.", "1": "Prototype only. No production deployments." } } ], "procurement": { "marketMaturity": "emerging", "primaryMode": "tender", "alternativeModes": [ "off-the-shelf" ], "reasoning": "Medical and teacher credentialing platforms exist with good reach.", "exampleProductCategories": [ "medical-credentialing-platform", "teacher-credentialing-saas" ], "partnerChannels": [], "lastReviewed": "2026-05-01" } }, { "id": "UC-B-032", "name": "Implementing partner staff verification", "category": "B", "subcategory": "Partner Verification", "description": "Check the identity and qualifications of partner staff and subcontractors once, in a form that you and your other partners can rely on.", "bCriteria": [ "B1", "B3", "B2" ], "requiredComponents": [ { "component": "identity-protocol", "description": "Partner staff identity verification" }, { "component": "credential-issuance", "description": "Partner staff credentials" }, { "component": "verification-mechanism", "description": "Background check verification" }, { "component": "consent-management", "description": "Consent for background checks" } ], "conditionalComponents": [ { "component": "privacy-tech", "condition": "For sensitive personnel data" } ], "crossCategoryDependencies": [], "p2TriggerConditions": { "description": "Activated when P2 shows partner-implemented programmes + staff vetting concerns + risk mitigation", "rangeSignals": [ "partners >= 3", "partneredStaff >= 10+", "vestingBurden >= high" ] }, "contextFieldsTemplate": [ { "field": "partnerCount", "source": "P0 partnerships", "description": "Number of implementing partners" }, { "field": "staffCount", "source": "P2 partner staffing", "description": "Partner staff numbers" }, { "field": "vestingStandards", "source": "P0 Q19-21", "description": "Required vetting standards" }, { "field": "riskProfile", "source": "P0 context", "description": "Organisational risk context" } ], "implementationComplexity": "medium", "examples": { "note": "Partner due diligence and vetting", "references": [ { "name": "UN Partner Portal Verification", "url": "https://www.unpartnerportal.org/", "solved": "Standardised partner verification and due diligence across UN agencies" }, { "name": "CHS Alliance Safeguarding Vetting", "url": "https://www.chsalliance.org/", "solved": "Standards for partner staff vetting and safeguarding in humanitarian sector" } ] }, "solutionQuestions": [ { "id": "partner-vetting-scope", "type": "select", "options": [ { "label": "Identity verification + sanctions screening", "value": "identity-sanctions" }, { "label": "Full background checks including criminal records", "value": "full-background" }, { "label": "Safeguarding-level checks (working with vulnerable populations)", "value": "safeguarding" }, { "label": "Counter-terrorism compliance checks", "value": "ct-compliance" } ], "propertyMapping": { "identity-sanctions": { "technologies": [ "Identity verification module", "Sanctions screening engine" ], "technologyProperties": { "vettingScope": "Identity + sanctions", "screeningLists": "UN, OFAC, EU sanctions", "complianceLevel": "Standard" } }, "full-background": { "technologies": [ "Background check platform", "Criminal record check connection", "Sanctions screening engine" ], "technologyProperties": { "vettingScope": "Full background + criminal + sanctions", "screeningLists": "Sanctions + criminal databases", "complianceLevel": "Enhanced" } }, "safeguarding": { "technologies": [ "Safeguarding verification platform", "Child protection registry connection", "Enhanced background check engine" ], "technologyProperties": { "vettingScope": "Safeguarding-enhanced", "screeningLists": "Sanctions + criminal + child protection registers", "complianceLevel": "Maximum (child safeguarding)" } }, "ct-compliance": { "technologies": [ "Counter-terrorism screening platform", "Enhanced due diligence engine", "Ongoing monitoring service" ], "technologyProperties": { "vettingScope": "CT compliance + sanctions + background", "screeningLists": "CT lists + sanctions + PEP databases", "complianceLevel": "Counter-terrorism compliance" } } }, "prefillFrom": null, "briefSection": "Verification and privacy", "text": "What vetting is required for implementing partner staff?", "ngoText": "What vetting is required for implementing partner staff?" }, { "id": "partner-count", "type": "select", "options": [ { "label": "1-5 partners, under 50 staff total", "value": "small" }, { "label": "5-20 partners, 50-500 staff", "value": "medium" }, { "label": "20-100 partners, 500-5,000 staff", "value": "large" }, { "label": "100+ partners, 5,000+ staff", "value": "massive" } ], "propertyMapping": { "small": { "technologies": [ "Basic partner verification workflow" ], "technologyProperties": { "scalability": "Manual + digital", "throughput": "Individual processing", "partnerOnboarding": "Custom per partner" } }, "medium": { "technologies": [ "Partner verification platform" ], "technologyProperties": { "scalability": "Semi-automated", "throughput": "Batch processing", "partnerOnboarding": "Standardised workflow" } }, "large": { "technologies": [ "Enterprise partner verification platform", "Bulk screening engine" ], "technologyProperties": { "scalability": "Automated", "throughput": "High-volume batch", "partnerOnboarding": "Self-service portal" } }, "massive": { "technologies": [ "Enterprise partner verification platform", "Continuous screening service", "Partner self-service portal" ], "technologyProperties": { "scalability": "Enterprise-grade", "throughput": "Continuous processing", "partnerOnboarding": "Fully self-service" } } }, "prefillFrom": null, "briefSection": "Identity protocol", "text": "How many implementing partners and partner staff need verification?", "ngoText": "How many implementing partners and partner staff need verification?" }, { "id": "partner-credential-sharing", "type": "select", "options": [ { "label": "Yes, accept verified credentials from trusted partners", "value": "accept-trusted" }, { "label": "Partial, accept some checks, redo others", "value": "partial-accept" }, { "label": "No, full independent verification required", "value": "independent" } ], "propertyMapping": { "accept-trusted": { "technologies": [ "Cross-organisation credential trust framework", "Trusted issuer registry" ], "technologyProperties": { "trustModel": "Federated trust \u2014 accept partner credentials", "reverification": "None if from trusted issuer", "efficiencyGain": "High \u2014 avoid duplicate checks" } }, "partial-accept": { "technologies": [ "Selective credential acceptance engine", "Supplementary verification module" ], "technologyProperties": { "trustModel": "Partial trust \u2014 accept some, supplement others", "reverification": "For specific check types", "efficiencyGain": "Medium" } }, "independent": { "technologies": [ "Independent verification platform" ], "technologyProperties": { "trustModel": "Zero trust \u2014 full independent verification", "reverification": "Complete for every partner staff", "efficiencyGain": "Low \u2014 no credential reuse" } } }, "prefillFrom": null, "briefSection": "Interoperability", "text": "Can partner staff credentials from other organisations be trusted and reused?", "ngoText": "Can partner staff credentials from other organisations be trusted and reused?" }, { "id": "partner-monitoring", "type": "select", "options": [ { "label": "One-time verification at onboarding", "value": "one-time" }, { "label": "Periodic re-screening (annual)", "value": "periodic" }, { "label": "Continuous monitoring with real-time alerts", "value": "continuous" } ], "propertyMapping": { "one-time": { "technologies": [ "Onboarding verification workflow" ], "technologyProperties": { "monitoringType": "None after onboarding", "alerting": "None", "riskMitigation": "Point-in-time only" } }, "periodic": { "technologies": [ "Periodic re-screening engine", "Batch re-verification service" ], "technologyProperties": { "monitoringType": "Annual batch re-screening", "alerting": "Post-screening results", "riskMitigation": "Periodic risk refresh" } }, "continuous": { "technologies": [ "Continuous monitoring service", "Real-time sanctions alert engine", "Credential revocation watcher" ], "technologyProperties": { "monitoringType": "Continuous real-time", "alerting": "Immediate alerts on changes", "riskMitigation": "Real-time risk mitigation" } } }, "prefillFrom": null, "briefSection": "Consent and governance", "text": "Is ongoing monitoring of partner staff credentials needed?", "ngoText": "Is ongoing monitoring of partner staff credentials needed?" }, { "id": "partner-reporting", "type": "select", "options": [ { "label": "Internal compliance dashboard", "value": "internal" }, { "label": "Donor compliance evidence", "value": "donor" }, { "label": "Regulatory compliance audit trail", "value": "regulatory" } ], "propertyMapping": { "internal": { "technologies": [ "Partner compliance dashboard" ], "technologyProperties": { "reportingScope": "Internal management", "auditDepth": "Summary", "complianceEvidence": "Dashboard view" } }, "donor": { "technologies": [ "Donor compliance reporting module" ], "technologyProperties": { "reportingScope": "Donor accountability", "auditDepth": "Aggregated per partner", "complianceEvidence": "Exportable compliance reports" } }, "regulatory": { "technologies": [ "Regulatory audit trail", "Full verification history" ], "technologyProperties": { "reportingScope": "Regulatory compliance", "auditDepth": "Individual-level audit trail", "complianceEvidence": "Court-admissible records" } } }, "prefillFrom": null, "briefSection": "Reporting and audit", "text": "What partner verification reporting is required?", "ngoText": "What partner verification reporting is required?" }, { "id": "consent-management-approach", "type": "select", "options": [ { "label": "Granular consent: individuals control each data element shared", "value": "granular" }, { "label": "Tiered consent: pre-defined levels (basic, standard, full)", "value": "tiered" }, { "label": "Blanket consent with opt-out for specific data categories", "value": "blanket-optout" }, { "label": "Guardian/proxy consent for vulnerable populations", "value": "guardian-proxy" } ], "propertyMapping": { "granular": { "technologies": [ "Granular consent management platform", "Consent ledger", "Privacy-preserving disclosure engine" ], "technologyProperties": { "consentGranularity": "Per-attribute", "consentStorage": "Digital consent receipts", "revocation": "Real-time revocable" } }, "tiered": { "technologies": [ "Tiered consent management system", "Consent ledger", "Pre-defined disclosure profiles" ], "technologyProperties": { "consentGranularity": "Pre-defined tiers", "consentStorage": "Digital consent receipts", "revocation": "Tier-level revocation" } }, "blanket-optout": { "technologies": [ "Consent management platform", "Consent ledger", "Opt-out tracking service" ], "technologyProperties": { "consentGranularity": "Broad with category opt-outs", "consentStorage": "Digital consent records", "revocation": "Category-level opt-out" } }, "guardian-proxy": { "technologies": [ "Guardian consent management platform", "Consent ledger", "Proxy delegation service" ], "technologyProperties": { "consentGranularity": "Guardian-managed on behalf of individual", "consentStorage": "Digital with guardian chain of authority", "revocation": "Guardian or individual (when able)" } } }, "prefillFrom": null, "briefSection": "Privacy and consent", "text": "How do you currently manage consent for beneficiary data collection and sharing?", "ngoText": "How do you currently manage consent for beneficiary data collection and sharing?" } ], "complexityFactors": { "relationships": 3, "operationalChange": 2, "dataCompliance": 3 }, "suggestedCriteria": [ { "id": "SC-SANCTIONS-SCREENING", "name": "Sanctions & Compliance Screening", "description": "The system screens against international sanctions lists, counter-terrorism databases, and debarment lists. Required for donor compliance.", "weight": 0.3, "ratingGuide": { "5": "Real-time screening against OFAC, UN, EU, and national sanctions lists. Automatic updates. Fuzzy name matching. PEP screening included.", "4": "Screening against major sanctions lists. Regular updates. Good name matching.", "3": "Screening against primary lists (OFAC, UN). Manual updates or delayed refresh.", "2": "Basic screening against one major list. Limited name matching.", "1": "No sanctions screening capability." } }, { "id": "SC-PARTNER-TRUST", "name": "Multi-Partner Trust Framework", "description": "Credentials can be shared across a partner network without each organisation re-verifying from scratch. Reduces duplicate screening across consortia.", "weight": 0.25, "ratingGuide": { "5": "Federated trust network. Partners mutually recognise verification. Credential delegation and endorsement supported.", "4": "Partner-to-partner credential sharing with configurable trust levels.", "3": "Credentials shareable. Receiving partner may require supplementary checks.", "2": "Credentials exportable but mostly re-verified by each partner.", "1": "No trust framework. Full re-verification required at every partner." } }, { "id": "SC-VERIFICATION-DEPTH", "name": "Verification Depth", "description": "Does the system support multiple levels of verification, from basic identity to full security clearance, appropriate to different partner roles?", "weight": 0.15, "ratingGuide": { "5": "Tiered verification (identity \u2192 background \u2192 security clearance \u2192 enhanced vetting). Each level independently attestable.", "4": "3-4 verification tiers. Clear escalation pathway.", "3": "2 tiers (basic and enhanced). Adequate for most partner types.", "2": "Single verification level. Same depth for all roles.", "1": "Basic identity check only." } }, { "id": "SC-AUDIT-TRAIL-COMPLIANCE", "name": "Audit Trail for Donor Compliance", "description": "The system maintains a verifiable record of who was verified, by whom, and when. Donors and auditors require this for due diligence reporting.", "weight": 0.15, "ratingGuide": { "5": "Immutable audit trail. Timestamped, cryptographically signed verification records. Export for donor reports.", "4": "Comprehensive audit logging. Verification history searchable and exportable.", "3": "Basic audit logs. Verification events recorded.", "2": "Limited logging. Some verification events not captured.", "1": "No audit trail." } }, { "id": "SC-DEPLOY-SIMPLICITY", "name": "Deployment Simplicity", "description": "How easily can the system be deployed across diverse implementing partners with varying technical capacity?", "weight": 0.15, "ratingGuide": { "5": "Cloud-based SaaS. No installation required. Self-service partner onboarding. Multi-language interface.", "4": "Easy deployment. Minimal IT requirements. Guided setup for new partners.", "3": "Moderate setup required. IT support needed for onboarding.", "2": "Complex deployment. Dedicated IT team required.", "1": "On-premises installation. Significant infrastructure requirements." } } ], "procurement": { "marketMaturity": "emerging", "primaryMode": "rfq", "alternativeModes": [ "off-the-shelf" ], "reasoning": "Implementing partner staff verification overlaps with HR tooling.", "exampleProductCategories": [ "partner-due-diligence-platform", "workforce-verification-saas" ], "partnerChannels": [], "lastReviewed": "2026-05-01" } }, { "id": "UC-B-033", "name": "Educational credentials for displaced students", "category": "B", "subcategory": "Credential Portability", "description": "Give displaced students proof of what they have studied that schools and universities will accept, even when their original papers were lost.", "bCriteria": [ "B1", "B6" ], "requiredComponents": [ { "component": "credential-issuance", "description": "Academic credential issuance" }, { "component": "verification-mechanism", "description": "Proof of academic achievement" }, { "component": "holder-app", "description": "Student digital wallet" }, { "component": "interoperability-layer", "description": "Cross-school/system credential exchange" } ], "conditionalComponents": [ { "component": "identity-verification", "condition": "For student identity verification" }, { "component": "privacy-tech", "condition": "For academic privacy" } ], "crossCategoryDependencies": [ "UC-B-024 for student identity" ], "p2TriggerConditions": { "description": "Activated when P2 shows displaced students + school transitions + credential gaps", "rangeSignals": [ "studentCount >= 100+", "schoolTransitions >= frequent", "credentialRecognition >= challenging" ] }, "contextFieldsTemplate": [ { "field": "studentCount", "source": "P2 education programme", "description": "Number of students" }, { "field": "educationLevels", "source": "P2 student demographics", "description": "Grade levels" }, { "field": "schoolSystems", "source": "P0 countries", "description": "Education systems involved" }, { "field": "previousCredentials", "source": "P2 student backgrounds", "description": "Prior school records" } ], "implementationComplexity": "medium", "examples": { "note": "Education in emergencies, UNHCR education programmes", "references": [ { "name": "UNESCO Connected Learning", "url": "https://en.unesco.org/themes/education-emergencies", "solved": "Framework for recognising and credentialing education in displacement contexts" }, { "name": "Blockcerts for Education", "url": "https://www.blockcerts.org/", "solved": "Open standard for issuing blockchain-verified academic credentials portable across borders" }, { "name": "UNHCR DAFI Scholarship Programme", "url": "https://www.unhcr.org/dafi-scholarships.html", "solved": "Higher education credential portability for refugee students" } ] }, "solutionQuestions": [ { "id": "education-level", "type": "select", "options": [ { "label": "Primary school (ages 6-12)", "value": "primary" }, { "label": "Secondary school (ages 12-18)", "value": "secondary" }, { "label": "Both primary and secondary", "value": "both" }, { "label": "Post-secondary / higher education", "value": "post-secondary" } ], "propertyMapping": { "primary": { "technologies": [ "Primary education credential platform", "Grade-level attestation engine" ], "technologyProperties": { "educationLevel": "Primary", "credentialType": "Grade completion certificates", "assessmentIntegration": "Teacher attestation" } }, "secondary": { "technologies": [ "Secondary education credential platform", "Examination result credential engine" ], "technologyProperties": { "educationLevel": "Secondary", "credentialType": "Subject completion + examination results", "assessmentIntegration": "Formal examination linking" } }, "both": { "technologies": [ "Multi-level education credential platform", "Progressive credential chain" ], "technologyProperties": { "educationLevel": "Primary + secondary", "credentialType": "Full K-12 credential chain", "assessmentIntegration": "Teacher attestation + examination" } }, "post-secondary": { "technologies": [ "Higher education credential platform", "Degree attestation engine", "Transcript verification module" ], "technologyProperties": { "educationLevel": "Post-secondary", "credentialType": "Degrees, diplomas, transcripts", "assessmentIntegration": "University registry linking" } } }, "prefillFrom": null, "briefSection": "Credential issuance", "text": "What education levels need credential support?", "ngoText": "What education levels need credential support?" }, { "id": "education-portability", "type": "select", "options": [ { "label": "Host country education system only", "value": "host-country" }, { "label": "Country of origin education system (for return)", "value": "origin-country" }, { "label": "Multiple country systems (regional portability)", "value": "regional" }, { "label": "International recognition (for resettlement)", "value": "international" } ], "propertyMapping": { "host-country": { "technologies": [ "Host country curriculum mapping", "Local education authority connection" ], "technologyProperties": { "portabilityScope": "Host country", "curriculumMapping": "Host country curriculum", "recognitionPath": "Local education authority" } }, "origin-country": { "technologies": [ "Origin country credential bridge", "Cross-system curriculum equivalency" ], "technologyProperties": { "portabilityScope": "Country of origin", "curriculumMapping": "Origin country curriculum", "recognitionPath": "Origin education ministry" } }, "regional": { "technologies": [ "Regional education credential exchange", "Multi-curriculum mapping engine" ], "technologyProperties": { "portabilityScope": "Regional (multiple countries)", "curriculumMapping": "Multi-curriculum equivalency", "recognitionPath": "Regional education frameworks" } }, "international": { "technologies": [ "International education credential platform", "UNESCO equivalency framework", "International transcript service" ], "technologyProperties": { "portabilityScope": "International", "curriculumMapping": "UNESCO ISCED framework", "recognitionPath": "International credential evaluation" } } }, "prefillFrom": null, "briefSection": "Interoperability", "text": "What education systems need to recognise these credentials?", "ngoText": "What education systems need to recognise these credentials?" }, { "id": "education-prior-records", "type": "select", "options": [ { "label": "Most students have prior school records from origin country", "value": "records-available" }, { "label": "Records exist but are inaccessible (left behind, destroyed)", "value": "records-inaccessible" }, { "label": "Most students have no prior educational documentation", "value": "no-records" }, { "label": "Mixed: some have records, many do not", "value": "mixed" } ], "propertyMapping": { "records-available": { "technologies": [ "Record digitisation module", "Prior credential verification engine" ], "technologyProperties": { "priorRecordStatus": "Available", "recordRecovery": "Digitise existing", "placementApproach": "Record-based placement" } }, "records-inaccessible": { "technologies": [ "Competency assessment platform", "Prior learning recognition engine" ], "technologyProperties": { "priorRecordStatus": "Exists but inaccessible", "recordRecovery": "Assessment-based reconstruction", "placementApproach": "Competency assessment + placement" } }, "no-records": { "technologies": [ "Competency assessment platform", "Fresh credential bootstrapping", "Age-appropriate placement engine" ], "technologyProperties": { "priorRecordStatus": "None", "recordRecovery": "Start fresh with assessment", "placementApproach": "Assessment + age-appropriate placement" } }, "mixed": { "technologies": [ "Adaptive placement platform", "Multi-pathway credential entry" ], "technologyProperties": { "priorRecordStatus": "Mixed", "recordRecovery": "Adaptive \u2014 record review or assessment", "placementApproach": "Dual pathway (records or assessment)" } } }, "prefillFrom": null, "briefSection": "Verification and privacy", "text": "What is the status of students' prior educational records?", "ngoText": "What is the status of students' prior educational records?" }, { "id": "education-holder-device", "type": "select", "options": [ { "label": "Family smartphone (parent manages)", "value": "family-phone" }, { "label": "Printed certificate with QR verification code", "value": "printed-qr" }, { "label": "School-managed digital records (students access via portal)", "value": "school-managed" }, { "label": "Mixed: digital + printed", "value": "mixed" } ], "propertyMapping": { "family-phone": { "technologies": [ "Family education wallet app", "Parent/guardian credential manager" ], "technologyProperties": { "holderInterface": "Family smartphone app", "credentialAccess": "Parent-managed", "transferMechanism": "QR display or digital share" } }, "printed-qr": { "technologies": [ "Printed credential module", "QR verification system" ], "technologyProperties": { "holderInterface": "Printed certificate with QR", "credentialAccess": "Physical document", "transferMechanism": "QR code scan" } }, "school-managed": { "technologies": [ "School credential management portal", "Transcript request module" ], "technologyProperties": { "holderInterface": "Web portal", "credentialAccess": "School-managed with student/family login", "transferMechanism": "Authorised transcript release" } }, "mixed": { "technologies": [ "Multi-channel credential platform" ], "technologyProperties": { "holderInterface": "App + printed + portal", "credentialAccess": "Adaptive", "transferMechanism": "Digital or physical" } } }, "prefillFrom": null, "briefSection": "Holder experience", "text": "How will students/families access and present credentials?", "ngoText": "How will students/families access and present credentials?" }, { "id": "education-privacy", "type": "select", "options": [ { "label": "Standard student data protection", "value": "standard" }, { "label": "Enhanced child protection (displacement-sensitive)", "value": "enhanced" }, { "label": "Maximum privacy (conflict context: risk to child/family)", "value": "maximum" } ], "propertyMapping": { "standard": { "technologies": [ "Student data encryption module", "Role-based access control" ], "technologyProperties": { "privacyLevel": "Standard student data protection", "childSpecific": "Age-appropriate consent", "accessControl": "Teacher + parent + admin" } }, "enhanced": { "technologies": [ "Enhanced child data protection platform", "Anonymised analytics" ], "technologyProperties": { "privacyLevel": "Enhanced \u2014 displacement-sensitive", "childSpecific": "Displacement-aware privacy protocols", "accessControl": "Restricted with child protection oversight" } }, "maximum": { "technologies": [ "Security-hardened child data vault", "Pseudonymised records" ], "technologyProperties": { "privacyLevel": "Maximum \u2014 conflict-sensitive", "childSpecific": "Pseudonymised identity", "accessControl": "Need-to-know with security review" } } }, "prefillFrom": null, "briefSection": "Consent and governance", "text": "What child data privacy protections do you currently have?", "ngoText": "What child data privacy protections do you currently have?" }, { "id": "education-connectivity", "type": "select", "options": [ { "label": "Reliable internet", "value": "connected" }, { "label": "Intermittent connectivity", "value": "intermittent" }, { "label": "Fully offline: remote or camp-based schools", "value": "offline" } ], "propertyMapping": { "connected": { "technologies": [ "Cloud-hosted education platform" ], "technologyProperties": { "connectivity": "Online", "offlineCapability": "Not required", "syncModel": "Real-time" } }, "intermittent": { "technologies": [ "Offline-first education platform", "Sync queue" ], "technologyProperties": { "connectivity": "Intermittent", "offlineCapability": "Required", "syncModel": "Store-and-forward" } }, "offline": { "technologies": [ "Fully offline education credential toolkit" ], "technologyProperties": { "connectivity": "None", "offlineCapability": "Full offline workflow", "syncModel": "Batch upload" } } }, "prefillFrom": null, "briefSection": "Infrastructure requirements", "text": "What connectivity is available at schools and learning centres?", "ngoText": "What connectivity is available at schools and learning centres?" }, { "id": "education-reporting", "type": "select", "options": [ { "label": "Enrolment and completion statistics", "value": "basic" }, { "label": "Learning outcome tracking and analytics", "value": "outcome-tracking" }, { "label": "Donor reporting with education impact metrics", "value": "donor-impact" } ], "propertyMapping": { "basic": { "technologies": [ "Education statistics dashboard" ], "technologyProperties": { "reportingScope": "Enrolment and completion", "metrics": "Headcount, completion rates", "disaggregation": "Gender, age, nationality" } }, "outcome-tracking": { "technologies": [ "Learning analytics engine", "Outcome tracking dashboard" ], "technologyProperties": { "reportingScope": "Learning outcomes", "metrics": "Assessment results, progression rates", "disaggregation": "Full disaggregation + longitudinal" } }, "donor-impact": { "technologies": [ "Donor education impact reporting module" ], "technologyProperties": { "reportingScope": "Donor accountability", "metrics": "Impact metrics (access, retention, learning)", "disaggregation": "Anonymised for donor reports" } } }, "prefillFrom": null, "briefSection": "Reporting and audit", "text": "What education programme reporting do you currently have?", "ngoText": "What education programme reporting do you currently have?" }, { "id": "holder-access-method", "type": "select", "options": [ { "label": "Mobile wallet app (smartphone required)", "value": "mobile-wallet" }, { "label": "Physical smart card with NFC or QR code", "value": "smart-card" }, { "label": "SMS/USSD-based access (feature phone compatible)", "value": "sms-ussd" }, { "label": "Hybrid: mobile app for those with smartphones, card for others", "value": "hybrid" } ], "propertyMapping": { "mobile-wallet": { "technologies": [ "Mobile holder app", "Credential wallet SDK", "Biometric authentication module" ], "technologyProperties": { "holderDevice": "Smartphone (Android/iOS)", "authMethod": "PIN + biometric", "offlineAccess": "Cached credentials available offline" } }, "smart-card": { "technologies": [ "Smart card holder platform", "Card provisioning service", "Card reader/NFC verifier" ], "technologyProperties": { "holderDevice": "Physical smart card", "authMethod": "Card + PIN", "offlineAccess": "Card-based presentation works offline" } }, "sms-ussd": { "technologies": [ "SMS/USSD holder interface", "Feature phone credential access", "OTP verification service" ], "technologyProperties": { "holderDevice": "Feature phone (SMS/USSD)", "authMethod": "OTP via SMS", "offlineAccess": "Limited \u2014 requires network for SMS" } }, "hybrid": { "technologies": [ "Mobile holder app", "Smart card holder platform", "Multi-channel credential access" ], "technologyProperties": { "holderDevice": "Smartphone + physical card fallback", "authMethod": "Biometric (mobile) or PIN (card)", "offlineAccess": "Both channels support offline presentation" } } }, "prefillFrom": null, "briefSection": "Credential access", "text": "How will individuals access and present their credentials or identity documents?", "ngoText": "How will individuals access and present their credentials or identity documents?" }, { "id": "beneficiary-choice", "label": "How will beneficiaries exercise choice in how they receive and use this service?", "type": "select", "briefSection": "Holder experience", "options": [ { "label": "Beneficiaries choose between delivery methods (cash, voucher, mobile money, direct)", "value": "delivery-choice" }, { "label": "Beneficiaries choose preferred merchants or service points", "value": "merchant-choice" }, { "label": "Beneficiaries control their own data sharing preferences", "value": "data-choice" }, { "label": "Multiple choice dimensions (delivery + merchant + data)", "value": "full-choice" }, { "label": "Limited choice: programme constraints determine delivery", "value": "limited" } ], "propertyMapping": { "delivery-choice": { "technologies": [], "technologyProperties": { "beneficiaryChoice": "Delivery method choice", "dignityDesign": "Beneficiaries select preferred receipt method" } }, "merchant-choice": { "technologies": [], "technologyProperties": { "beneficiaryChoice": "Merchant/service point choice", "dignityDesign": "Beneficiaries select where to redeem" } }, "data-choice": { "technologies": [], "technologyProperties": { "beneficiaryChoice": "Data sharing choice", "dignityDesign": "Beneficiaries control personal data sharing" } }, "full-choice": { "technologies": [], "technologyProperties": { "beneficiaryChoice": "Multi-dimensional choice", "dignityDesign": "Full beneficiary agency across delivery, merchant, and data" } }, "limited": { "technologies": [], "technologyProperties": { "beneficiaryChoice": "Limited by programme design", "dignityDesign": "Programme constraints; beneficiary informed of reasons" } } }, "text": "How will beneficiaries exercise choice in how they receive and use this service?" } ], "complexityFactors": { "relationships": 3, "operationalChange": 2, "dataCompliance": 4 }, "securityTier": "B", "suggestedCriteria": [ { "id": "SC-CREDENTIAL-PORTABLE", "name": "Credential Portability & Recognition", "description": "Educational credentials are recognised and verifiable across different countries' education systems. Displaced students need credentials that work beyond their country of origin.", "weight": 0.3, "ratingGuide": { "5": "Internationally recognised credential format. Government partnerships for cross-border academic recognition. W3C VC compliant.", "4": "Credentials accepted by multiple national education systems. Active recognition agreements.", "3": "Standard credential format. Portable but requires manual equivalency assessment.", "2": "Credentials verifiable within issuing country only. Export possible but recognition uncertain.", "1": "Proprietary format. No portability or recognition pathway." } }, { "id": "SC-SELECTIVE-ACADEMIC", "name": "Selective Disclosure", "description": "Can a student share their grade level or completion status without revealing all academic records, personal details, or institutional history?", "weight": 0.2, "ratingGuide": { "5": "Granular selective disclosure \u2014 prove grade level, completion, or specific subjects without revealing full transcript or personal data.", "4": "Category-level disclosure. Can share academic level without revealing detailed grades.", "3": "Some fields redactable before sharing. Moderate control over what is disclosed.", "2": "Full transcript shared during any verification. Limited redaction capability.", "1": "All academic records and personal data visible to any verifier." } }, { "id": "SC-CURRICULUM-MAP", "name": "Curriculum Mapping Capability", "description": "The system can map qualifications between different education systems (e.g. Jordanian Grade 8 to Kenyan Standard 8). Displaced students often move between incompatible school systems.", "weight": 0.2, "ratingGuide": { "5": "Automated curriculum mapping across multiple national systems. Learning outcomes aligned. Placement recommendations generated.", "4": "Mapping between major education systems with manual review for edge cases.", "3": "Basic equivalency tables. Manual mapping required for non-standard cases.", "2": "No automated mapping. Provides raw credential data for manual assessment.", "1": "No curriculum mapping capability. Credentials from different systems incomparable." } }, { "id": "SC-PRIOR-LEARNING", "name": "Prior Learning Recognition", "description": "The system can capture and certify informal, non-standard, or interrupted education. Many displaced students have learning that doesn't fit formal grade structures.", "weight": 0.15, "ratingGuide": { "5": "Comprehensive prior learning assessment framework. Portfolio-based, competency-based, and experiential learning all supported.", "4": "Supports competency-based credentials alongside formal qualifications. Assessment tools included.", "3": "Can record informal learning but limited assessment framework.", "2": "Primarily formal credential tracking. Informal learning noted but not certified.", "1": "Formal credentials only. No mechanism for non-standard education pathways." } }, { "id": "SC-INSTITUTIONAL-ACCEPT", "name": "Institutional Acceptance", "description": "Do universities, employers, and vocational training institutions actually accept and verify credentials from this system?", "weight": 0.15, "ratingGuide": { "5": "Active partnerships with universities and employers. Verified acceptance in multiple countries. Credential verification API used by institutions.", "4": "Accepted by several institutions. Growing network of verifiers.", "3": "Some institutional acceptance. Credentials used in pilot programmes.", "2": "Limited acceptance. Individual institutions may choose to recognise credentials.", "1": "No institutional acceptance. Credentials not recognised beyond the issuing platform." } } ], "procurement": { "marketMaturity": "emerging", "primaryMode": "tender", "alternativeModes": [ "off-the-shelf" ], "reasoning": "Educational credential platforms (open-standard and consortium models) are emerging.", "exampleProductCategories": [ "educational-credentials-platform", "digital-diploma-rails" ], "partnerChannels": [], "lastReviewed": "2026-05-01" } }, { "id": "UC-B-034", "name": "Vocational training certificates", "category": "B", "subcategory": "Professional Credentials", "description": "Issue training certificates that employers can confirm are genuine within seconds, so participants' skills are recognised when they apply for work.", "bCriteria": [ "B1", "B3", "B6" ], "requiredComponents": [ { "component": "credential-issuance", "description": "Vocational certificate issuance" }, { "component": "verification-mechanism", "description": "Proof of skills certification" }, { "component": "holder-app", "description": "Trainee credential wallet" }, { "component": "interoperability-layer", "description": "Employer credential recognition" } ], "conditionalComponents": [ { "component": "identity-verification", "condition": "For trainee identity" }, { "component": "privacy-tech", "condition": "For selective skill disclosure" } ], "crossCategoryDependencies": [], "p2TriggerConditions": { "description": "Activated when P2 shows vocational training + employment focus + credential recognition needs", "rangeSignals": [ "trainingProgrammes >= 3", "trainees >= 50+", "employmentPlacement >= goal" ] }, "contextFieldsTemplate": [ { "field": "trainingTypes", "source": "P2 TVET programmes", "description": "Types of vocational training" }, { "field": "trainees", "source": "P2 programme scale", "description": "Number of trainees" }, { "field": "employerRecognition", "source": "P2 labour market", "description": "Employer credential needs" }, { "field": "certificationStandards", "source": "P0 Q19-21", "description": "Required standards" } ], "implementationComplexity": "medium", "examples": { "note": "Skills credentialing for employment", "references": [ { "name": "ConsenSys Social Impact Skills Credentials", "url": "https://consensys.io/social-impact", "solved": "Blockchain-verified vocational credentials for vulnerable populations" }, { "name": "Open Badges Standard", "url": "https://openbadges.org/", "solved": "Open standard for digital skill badges recognised across platforms and employers" } ] }, "solutionQuestions": [ { "id": "voc-training-types", "type": "select", "options": [ { "label": "Technical skills (construction, plumbing, electrical)", "value": "technical" }, { "label": "Digital/IT skills (computer literacy, coding)", "value": "digital" }, { "label": "Livelihood skills (agriculture, tailoring, small business)", "value": "livelihood" }, { "label": "Multiple skill categories", "value": "multiple" } ], "propertyMapping": { "technical": { "technologies": [ "Technical skills credential platform", "Practical assessment verifier" ], "technologyProperties": { "trainingDomain": "Technical/trade skills", "assessmentType": "Practical + theoretical", "industryAlignment": "Trade certification standards" } }, "digital": { "technologies": [ "Digital skills credential platform", "Online assessment integration" ], "technologyProperties": { "trainingDomain": "Digital/IT skills", "assessmentType": "Project-based + exam", "industryAlignment": "Industry certification mapping" } }, "livelihood": { "technologies": [ "Livelihood skills credential platform", "Community-based assessment module" ], "technologyProperties": { "trainingDomain": "Livelihood skills", "assessmentType": "Practical demonstration", "industryAlignment": "Local market relevance" } }, "multiple": { "technologies": [ "Multi-domain vocational credential platform", "Universal skills taxonomy" ], "technologyProperties": { "trainingDomain": "Multiple domains", "assessmentType": "Domain-appropriate", "industryAlignment": "Multi-sector mapping" } } }, "prefillFrom": null, "briefSection": "Credential issuance", "text": "What types of vocational training need certification?", "ngoText": "What types of vocational training need certification?" }, { "id": "voc-employer-recognition", "type": "select", "options": [ { "label": "QR code scan for instant verification", "value": "qr-verification" }, { "label": "Online verification portal for employers", "value": "online-portal" }, { "label": "Integration with national qualification frameworks", "value": "nqf-integration" }, { "label": "Peer-to-peer credential sharing (no central lookup)", "value": "p2p" } ], "propertyMapping": { "qr-verification": { "technologies": [ "QR code credential verification", "Instant verification API" ], "technologyProperties": { "employerInterface": "QR code scan", "verificationSpeed": "Instant", "integrationDepth": "Standalone" } }, "online-portal": { "technologies": [ "Employer verification portal", "Credential lookup API" ], "technologyProperties": { "employerInterface": "Web portal", "verificationSpeed": "Seconds", "integrationDepth": "Portal-based lookup" } }, "nqf-integration": { "technologies": [ "National qualifications framework connection", "Equivalency mapping engine" ], "technologyProperties": { "employerInterface": "Through national framework", "verificationSpeed": "Variable", "integrationDepth": "National framework aligned" } }, "p2p": { "technologies": [ "Peer-to-peer credential exchange", "Self-verifying credential" ], "technologyProperties": { "employerInterface": "Direct credential presentation", "verificationSpeed": "Instant (offline capable)", "integrationDepth": "No central dependency" } } }, "prefillFrom": null, "briefSection": "Interoperability", "text": "What systems do employers currently use to verify and recognise vocational certificates?", "ngoText": "What systems do employers currently use to verify and recognise vocational certificates?" }, { "id": "voc-micro-credentials", "type": "select", "options": [ { "label": "Single certificate per training programme", "value": "single-cert" }, { "label": "Modular: stackable micro-credentials building to full certification", "value": "modular" }, { "label": "Competency-based: badge for each verified skill", "value": "competency-badges" } ], "propertyMapping": { "single-cert": { "technologies": [ "Single credential issuance engine" ], "technologyProperties": { "credentialModel": "Single programme certificate", "stackability": "None", "progressTracking": "Binary (complete/incomplete)" } }, "modular": { "technologies": [ "Micro-credential issuance platform", "Credential stacking engine", "Learning pathway tracker" ], "technologyProperties": { "credentialModel": "Stackable micro-credentials", "stackability": "Modules \u2192 full certification", "progressTracking": "Progressive completion" } }, "competency-badges": { "technologies": [ "Open Badges platform", "Competency assessment engine", "Skills portfolio builder" ], "technologyProperties": { "credentialModel": "Competency-based badges", "stackability": "Skills portfolio", "progressTracking": "Skill-level granularity" } } }, "prefillFrom": null, "briefSection": "Credential issuance", "text": "Are modular/micro-credentials needed (stackable skills)?", "ngoText": "Are modular/micro-credentials needed (stackable skills)?" }, { "id": "voc-holder-device", "type": "select", "options": [ { "label": "Smartphone wallet app", "value": "smartphone" }, { "label": "Printed certificate with QR code", "value": "printed" }, { "label": "Both digital and printed", "value": "both" } ], "propertyMapping": { "smartphone": { "technologies": [ "Skills wallet mobile app" ], "technologyProperties": { "holderInterface": "Mobile app", "presentation": "QR display or digital share", "offlineAccess": "On-device storage" } }, "printed": { "technologies": [ "Certificate printing module", "QR verification system" ], "technologyProperties": { "holderInterface": "Printed certificate", "presentation": "QR code scan", "offlineAccess": "Physical document" } }, "both": { "technologies": [ "Skills wallet mobile app", "Certificate printing module" ], "technologyProperties": { "holderInterface": "Mobile + printed", "presentation": "Digital or physical", "offlineAccess": "Both supported" } } }, "prefillFrom": null, "briefSection": "Holder experience", "text": "How will trainees access and present their certificates?", "ngoText": "How will trainees access and present their certificates?" }, { "id": "voc-reporting", "type": "select", "options": [ { "label": "Training completion statistics", "value": "completion" }, { "label": "Employment outcome tracking", "value": "employment" }, { "label": "Donor impact reporting with livelihoods metrics", "value": "donor-impact" } ], "propertyMapping": { "completion": { "technologies": [ "Training analytics dashboard" ], "technologyProperties": { "reportingScope": "Completion statistics", "metrics": "Enrolment, completion, certification rates", "outcomeTracking": "None" } }, "employment": { "technologies": [ "Employment outcome tracker", "Post-training follow-up module" ], "technologyProperties": { "reportingScope": "Completion + employment outcomes", "metrics": "Certification + employment rates", "outcomeTracking": "Post-training employment monitoring" } }, "donor-impact": { "technologies": [ "Donor impact reporting engine", "Livelihoods metrics dashboard" ], "technologyProperties": { "reportingScope": "Full impact chain", "metrics": "Training \u2192 certification \u2192 employment \u2192 income", "outcomeTracking": "Longitudinal impact tracking" } } }, "prefillFrom": null, "briefSection": "Reporting and audit", "text": "What training programme reporting do you currently have?", "ngoText": "What training programme reporting do you currently have?" }, { "id": "holder-access-method", "type": "select", "options": [ { "label": "Mobile wallet app (smartphone required)", "value": "mobile-wallet" }, { "label": "Physical smart card with NFC or QR code", "value": "smart-card" }, { "label": "SMS/USSD-based access (feature phone compatible)", "value": "sms-ussd" }, { "label": "Hybrid: mobile app for those with smartphones, card for others", "value": "hybrid" } ], "propertyMapping": { "mobile-wallet": { "technologies": [ "Mobile holder app", "Credential wallet SDK", "Biometric authentication module" ], "technologyProperties": { "holderDevice": "Smartphone (Android/iOS)", "authMethod": "PIN + biometric", "offlineAccess": "Cached credentials available offline" } }, "smart-card": { "technologies": [ "Smart card holder platform", "Card provisioning service", "Card reader/NFC verifier" ], "technologyProperties": { "holderDevice": "Physical smart card", "authMethod": "Card + PIN", "offlineAccess": "Card-based presentation works offline" } }, "sms-ussd": { "technologies": [ "SMS/USSD holder interface", "Feature phone credential access", "OTP verification service" ], "technologyProperties": { "holderDevice": "Feature phone (SMS/USSD)", "authMethod": "OTP via SMS", "offlineAccess": "Limited \u2014 requires network for SMS" } }, "hybrid": { "technologies": [ "Mobile holder app", "Smart card holder platform", "Multi-channel credential access" ], "technologyProperties": { "holderDevice": "Smartphone + physical card fallback", "authMethod": "Biometric (mobile) or PIN (card)", "offlineAccess": "Both channels support offline presentation" } } }, "prefillFrom": null, "briefSection": "Credential access", "text": "How will individuals access and present their credentials or identity documents?", "ngoText": "How will individuals access and present their credentials or identity documents?" }, { "id": "beneficiary-choice", "label": "How will beneficiaries exercise choice in how they receive and use this service?", "type": "select", "briefSection": "Holder experience", "options": [ { "label": "Beneficiaries choose between delivery methods (cash, voucher, mobile money, direct)", "value": "delivery-choice" }, { "label": "Beneficiaries choose preferred merchants or service points", "value": "merchant-choice" }, { "label": "Beneficiaries control their own data sharing preferences", "value": "data-choice" }, { "label": "Multiple choice dimensions (delivery + merchant + data)", "value": "full-choice" }, { "label": "Limited choice: programme constraints determine delivery", "value": "limited" } ], "propertyMapping": { "delivery-choice": { "technologies": [], "technologyProperties": { "beneficiaryChoice": "Delivery method choice", "dignityDesign": "Beneficiaries select preferred receipt method" } }, "merchant-choice": { "technologies": [], "technologyProperties": { "beneficiaryChoice": "Merchant/service point choice", "dignityDesign": "Beneficiaries select where to redeem" } }, "data-choice": { "technologies": [], "technologyProperties": { "beneficiaryChoice": "Data sharing choice", "dignityDesign": "Beneficiaries control personal data sharing" } }, "full-choice": { "technologies": [], "technologyProperties": { "beneficiaryChoice": "Multi-dimensional choice", "dignityDesign": "Full beneficiary agency across delivery, merchant, and data" } }, "limited": { "technologies": [], "technologyProperties": { "beneficiaryChoice": "Limited by programme design", "dignityDesign": "Programme constraints; beneficiary informed of reasons" } } }, "text": "How will beneficiaries exercise choice in how they receive and use this service?" } ], "complexityFactors": { "relationships": 2, "operationalChange": 2, "dataCompliance": 2 }, "suggestedCriteria": [ { "id": "SC-EMPLOYER-ACCEPT", "name": "Employer Acceptance & Verification", "description": "Employers actually trust and use these credentials for hiring decisions. The system must bridge the gap between humanitarian training and formal employment.", "weight": 0.25, "ratingGuide": { "5": "Active employer partnerships. Verification API or QR code used in hiring processes. Employer endorsement programme.", "4": "Growing employer network. Credentials verified by employers in key sectors.", "3": "Some employer acceptance. Credentials used in pilot employment programmes.", "2": "Limited employer awareness. Credentials supplementary to traditional CVs.", "1": "No employer acceptance. Credentials not recognised in job markets." } }, { "id": "SC-NQF-ALIGNMENT", "name": "National Qualification Framework Alignment", "description": "Are vocational certificates mapped to national qualification frameworks (NQFs) in countries where beneficiaries seek employment?", "weight": 0.25, "ratingGuide": { "5": "Aligned with NQFs in 5+ countries. Formal recognition agreements. Automatic equivalency mapping.", "4": "Aligned with 2-4 national frameworks. Some formal recognition.", "3": "Mapped to one national framework. Others in progress.", "2": "Aware of NQF requirements but not yet aligned.", "1": "No NQF mapping or alignment." } }, { "id": "SC-MICRO-CREDENTIAL", "name": "Modular Micro-Credential Support", "description": "The system can issue partial qualifications, skill modules, and stackable credentials. Displaced learners often complete training in fragments.", "weight": 0.2, "ratingGuide": { "5": "Full micro-credential framework. Modular skill units stack toward full qualifications. Learning pathways visualised.", "4": "Micro-credentials supported. Can combine modules toward certificates.", "3": "Partial credential recording. Limited stacking capability.", "2": "Full qualification certificates only. No partial recording.", "1": "Single credential type. No modularity." } }, { "id": "SC-LEARNER-PORTABLE", "name": "Learner Portability & Ownership", "description": "Does the learner own and control their credentials? Can they share credentials without the training provider's ongoing involvement?", "weight": 0.15, "ratingGuide": { "5": "Learner-held credentials (W3C VC). Fully portable. Training provider not needed for verification. Learner controls sharing.", "4": "Learner receives digital credentials. Shareable but verification routes through platform.", "3": "Credentials accessible to learner. Sharing requires platform account.", "2": "Credentials held by training provider. Learner must request verification letters.", "1": "No learner access to credentials. Provider controls all verification." } }, { "id": "SC-FIELD-DEPLOY-VOC", "name": "Field Deployment Readiness", "description": "Can the system be used in humanitarian training settings (community centres, camps, mobile training units) with limited infrastructure?", "weight": 0.15, "ratingGuide": { "5": "Designed for field training. Offline credential issuance. Works on basic smartphones. Batch sync.", "4": "Works in low-connectivity settings. Smartphone-based. Intermittent sync.", "3": "Requires periodic connectivity. Smartphone or tablet needed.", "2": "Needs reliable internet. Computer-based.", "1": "Cloud-only. Requires constant connectivity and desktop access." } } ], "procurement": { "marketMaturity": "emerging", "primaryMode": "rfq", "alternativeModes": [ "off-the-shelf" ], "reasoning": "Vocational training certificate platforms growing.", "exampleProductCategories": [ "training-credentials-platform", "skills-passport-saas" ], "partnerChannels": [], "lastReviewed": "2026-05-01" } }, { "id": "UC-B-035", "name": "Skills attestation and competency verification", "category": "B", "subcategory": "Professional Credentials", "description": "Record the skills a participant has shown, and let employers confirm that the record came from a credible assessment.", "bCriteria": [ "B1", "B3", "B6" ], "requiredComponents": [ { "component": "credential-issuance", "description": "Competency credentials" }, { "component": "verification-mechanism", "description": "Skill assessment proofs" }, { "component": "holder-app", "description": "Skills wallet" }, { "component": "interoperability-layer", "description": "Credential exchange with employers" } ], "conditionalComponents": [ { "component": "privacy-tech", "condition": "For selective disclosure of skills" } ], "crossCategoryDependencies": [], "p2TriggerConditions": { "description": "Activated when P2 shows livelihoods focus + skills targeting + employer engagement", "rangeSignals": [ "livelihoodProgramme >= true", "skillsVetting >= important", "employerEngagement >= true" ] }, "contextFieldsTemplate": [ { "field": "beneficiaries", "source": "P2 programme scale", "description": "Number of participants" }, { "field": "skillTypes", "source": "P2 training content", "description": "Types of skills" }, { "field": "assessmentMethods", "source": "P2 M&E", "description": "Skill assessment approach" }, { "field": "employerRecognition", "source": "P2 labour market", "description": "Employer acceptance" } ], "implementationComplexity": "medium", "examples": { "note": "Skills credentialing and labour market integration", "references": [ { "name": "Velocity Network Foundation", "url": "https://www.velocitynetwork.foundation/", "solved": "Verifiable career credentials and skills attestation for global workforce" }, { "name": "Open Badges (IMS Global)", "url": "https://openbadges.org/", "solved": "Open standard for granular skill and competency badge issuance and verification" } ] }, "solutionQuestions": [ { "id": "skills-assessment-method", "type": "select", "options": [ { "label": "Formal examination or test", "value": "formal-exam" }, { "label": "Practical demonstration observed by assessor", "value": "practical-demo" }, { "label": "Portfolio of evidence (work samples)", "value": "portfolio" }, { "label": "Peer assessment and community attestation", "value": "peer-assessment" } ], "propertyMapping": { "formal-exam": { "technologies": [ "Examination credential engine", "Test result verification" ], "technologyProperties": { "assessmentMethod": "Formal examination", "assessorType": "Certified examiner", "evidenceType": "Examination scores" } }, "practical-demo": { "technologies": [ "Practical assessment credential", "Assessor attestation module" ], "technologyProperties": { "assessmentMethod": "Practical demonstration", "assessorType": "Qualified assessor", "evidenceType": "Assessor evaluation record" } }, "portfolio": { "technologies": [ "Portfolio-based credential platform", "Evidence submission module" ], "technologyProperties": { "assessmentMethod": "Portfolio assessment", "assessorType": "Portfolio reviewer", "evidenceType": "Work samples + reflections" } }, "peer-assessment": { "technologies": [ "Peer attestation protocol", "Multi-witness skill verification" ], "technologyProperties": { "assessmentMethod": "Peer/community attestation", "assessorType": "Community peers/employers", "evidenceType": "Multiple peer attestations" } } }, "prefillFrom": null, "briefSection": "Verification and privacy", "text": "How are skills and competencies assessed?", "ngoText": "How are skills and competencies assessed?" }, { "id": "skills-taxonomy", "type": "select", "options": [ { "label": "ESCO (European Skills/Competences/Occupations)", "value": "esco" }, { "label": "National qualifications framework of operating country", "value": "national" }, { "label": "Custom competency framework designed for programme", "value": "custom" }, { "label": "International labour market standards (ILO)", "value": "ilo" } ], "propertyMapping": { "esco": { "technologies": [ "ESCO-aligned skills taxonomy", "ESCO skill mapping engine" ], "technologyProperties": { "taxonomyStandard": "ESCO", "interoperability": "European labour market", "skillGranularity": "Fine-grained competency level" } }, "national": { "technologies": [ "National skills framework adapter", "Local qualification mapping" ], "technologyProperties": { "taxonomyStandard": "National framework", "interoperability": "Host country labour market", "skillGranularity": "National standard levels" } }, "custom": { "technologies": [ "Custom competency framework builder", "Programme-specific skill taxonomy" ], "technologyProperties": { "taxonomyStandard": "Custom", "interoperability": "Limited to programme/partners", "skillGranularity": "Programme-defined" } }, "ilo": { "technologies": [ "ILO skills framework adapter", "International occupational classification" ], "technologyProperties": { "taxonomyStandard": "ILO/ISCO", "interoperability": "Global labour market", "skillGranularity": "Occupational classification" } } }, "prefillFrom": null, "briefSection": "Credential issuance", "text": "What skills classification system should be used?", "ngoText": "What skills classification system should be used?" }, { "id": "skills-selective-disclosure", "type": "select", "options": [ { "label": "Full skill profile shared with potential employers", "value": "full-disclosure" }, { "label": "Selective: choose which skills to present per opportunity", "value": "selective" }, { "label": "Zero-knowledge: prove skill level without revealing details", "value": "zkp" } ], "propertyMapping": { "full-disclosure": { "technologies": [ "Full skills portfolio presentation" ], "technologyProperties": { "disclosureModel": "Full profile", "privacyTech": "None needed", "presentationFormat": "Complete skills portfolio" } }, "selective": { "technologies": [ "Selective skill presentation engine", "Credential bundling module" ], "technologyProperties": { "disclosureModel": "Selective per opportunity", "privacyTech": "Credential selection", "presentationFormat": "Curated skill bundle" } }, "zkp": { "technologies": [ "Zero-knowledge skill proof engine", "ZKP credential verification" ], "technologyProperties": { "disclosureModel": "Zero-knowledge proofs", "privacyTech": "ZK-SNARK or BBS+ signatures", "presentationFormat": "Proof of skill level without details" } } }, "prefillFrom": null, "briefSection": "Holder experience", "text": "Do skill holders need to selectively disclose specific competencies?", "ngoText": "Do skill holders need to selectively disclose specific competencies?" }, { "id": "skills-employer-integration", "type": "select", "options": [ { "label": "QR scan for instant verification", "value": "qr-scan" }, { "label": "Job platform integration (LinkedIn-style)", "value": "job-platform" }, { "label": "Employer API for bulk verification", "value": "employer-api" } ], "propertyMapping": { "qr-scan": { "technologies": [ "QR verification scanner", "Instant credential check API" ], "technologyProperties": { "employerAccess": "QR scan", "integrationDepth": "Standalone verification", "verificationSpeed": "Instant" } }, "job-platform": { "technologies": [ "Job platform credential connection", "Skills marketplace integration" ], "technologyProperties": { "employerAccess": "Through job platforms", "integrationDepth": "Platform API integration", "verificationSpeed": "Automatic on profile" } }, "employer-api": { "technologies": [ "Employer verification API", "Bulk credential check service" ], "technologyProperties": { "employerAccess": "API integration", "integrationDepth": "Deep employer system integration", "verificationSpeed": "Automated batch" } } }, "prefillFrom": null, "briefSection": "Interoperability", "text": "How will employers check and verify skills credentials?", "ngoText": "How will employers check and verify skills credentials?" }, { "id": "skills-reporting", "type": "select", "options": [ { "label": "Skills attainment statistics", "value": "attainment" }, { "label": "Labour market outcome tracking", "value": "labour-market" }, { "label": "Full impact chain (training \u2192 skills \u2192 employment \u2192 income)", "value": "full-impact" } ], "propertyMapping": { "attainment": { "technologies": [ "Skills analytics dashboard" ], "technologyProperties": { "reportingScope": "Attainment metrics", "outcomeTracking": "None", "impactMeasurement": "Outputs only" } }, "labour-market": { "technologies": [ "Labour market outcome tracker", "Employment follow-up module" ], "technologyProperties": { "reportingScope": "Attainment + employment", "outcomeTracking": "Employment outcomes", "impactMeasurement": "Outcomes" } }, "full-impact": { "technologies": [ "Full impact chain tracker", "Longitudinal livelihoods analytics" ], "technologyProperties": { "reportingScope": "Full impact chain", "outcomeTracking": "Employment + income + wellbeing", "impactMeasurement": "Longitudinal impact" } } }, "prefillFrom": null, "briefSection": "Reporting and audit", "text": "What skills programme reporting do you currently have?", "ngoText": "What skills programme reporting do you currently have?" }, { "id": "holder-access-method", "type": "select", "options": [ { "label": "Mobile wallet app (smartphone required)", "value": "mobile-wallet" }, { "label": "Physical smart card with NFC or QR code", "value": "smart-card" }, { "label": "SMS/USSD-based access (feature phone compatible)", "value": "sms-ussd" }, { "label": "Hybrid: mobile app for those with smartphones, card for others", "value": "hybrid" } ], "propertyMapping": { "mobile-wallet": { "technologies": [ "Mobile holder app", "Credential wallet SDK", "Biometric authentication module" ], "technologyProperties": { "holderDevice": "Smartphone (Android/iOS)", "authMethod": "PIN + biometric", "offlineAccess": "Cached credentials available offline" } }, "smart-card": { "technologies": [ "Smart card holder platform", "Card provisioning service", "Card reader/NFC verifier" ], "technologyProperties": { "holderDevice": "Physical smart card", "authMethod": "Card + PIN", "offlineAccess": "Card-based presentation works offline" } }, "sms-ussd": { "technologies": [ "SMS/USSD holder interface", "Feature phone credential access", "OTP verification service" ], "technologyProperties": { "holderDevice": "Feature phone (SMS/USSD)", "authMethod": "OTP via SMS", "offlineAccess": "Limited \u2014 requires network for SMS" } }, "hybrid": { "technologies": [ "Mobile holder app", "Smart card holder platform", "Multi-channel credential access" ], "technologyProperties": { "holderDevice": "Smartphone + physical card fallback", "authMethod": "Biometric (mobile) or PIN (card)", "offlineAccess": "Both channels support offline presentation" } } }, "prefillFrom": null, "briefSection": "Credential access", "text": "How will individuals access and present their credentials or identity documents?", "ngoText": "How will individuals access and present their credentials or identity documents?" }, { "id": "beneficiary-choice", "label": "How will beneficiaries exercise choice in how they receive and use this service?", "type": "select", "briefSection": "Holder experience", "options": [ { "label": "Beneficiaries choose between delivery methods (cash, voucher, mobile money, direct)", "value": "delivery-choice" }, { "label": "Beneficiaries choose preferred merchants or service points", "value": "merchant-choice" }, { "label": "Beneficiaries control their own data sharing preferences", "value": "data-choice" }, { "label": "Multiple choice dimensions (delivery + merchant + data)", "value": "full-choice" }, { "label": "Limited choice: programme constraints determine delivery", "value": "limited" } ], "propertyMapping": { "delivery-choice": { "technologies": [], "technologyProperties": { "beneficiaryChoice": "Delivery method choice", "dignityDesign": "Beneficiaries select preferred receipt method" } }, "merchant-choice": { "technologies": [], "technologyProperties": { "beneficiaryChoice": "Merchant/service point choice", "dignityDesign": "Beneficiaries select where to redeem" } }, "data-choice": { "technologies": [], "technologyProperties": { "beneficiaryChoice": "Data sharing choice", "dignityDesign": "Beneficiaries control personal data sharing" } }, "full-choice": { "technologies": [], "technologyProperties": { "beneficiaryChoice": "Multi-dimensional choice", "dignityDesign": "Full beneficiary agency across delivery, merchant, and data" } }, "limited": { "technologies": [], "technologyProperties": { "beneficiaryChoice": "Limited by programme design", "dignityDesign": "Programme constraints; beneficiary informed of reasons" } } }, "text": "How will beneficiaries exercise choice in how they receive and use this service?" } ], "complexityFactors": { "relationships": 2, "operationalChange": 2, "dataCompliance": 2 }, "suggestedCriteria": [ { "id": "SC-ASSESSMENT-FLEX", "name": "Assessment Method Flexibility", "description": "Does the system support diverse assessment approaches (formal exams, practical demonstrations, portfolio review, peer assessment, and observed competency)?", "weight": 0.25, "ratingGuide": { "5": "Supports all major assessment types: exams, practicals, portfolios, peer review, workplace observation. Configurable per skill.", "4": "Supports 3-4 assessment types. Good flexibility for different skill domains.", "3": "Supports 2 assessment types (e.g. exam + practical).", "2": "Single assessment method (e.g. written exam only).", "1": "No assessment framework. Simple pass/fail recording only." } }, { "id": "SC-STANDARDS-TAXONOMY", "name": "Skills Taxonomy Alignment", "description": "The system maps to recognised competency frameworks (ESCO, ILO, national frameworks). Standardised taxonomies enable credential portability and employer recognition.", "weight": 0.25, "ratingGuide": { "5": "Multi-framework mapping (ESCO + ILO + national). Automatic cross-referencing. Custom taxonomy support.", "4": "Aligned with one major framework (ESCO or national). Mapping to others available.", "3": "Basic taxonomy alignment. Partial mapping to recognised standards.", "2": "Custom taxonomy only. No alignment to recognised frameworks.", "1": "No skills taxonomy. Free-text skill descriptions." } }, { "id": "SC-EMPLOYER-API", "name": "Employer Verification Integration", "description": "Employers can verify specific skills quickly during hiring. API, QR code scanning, or other instant verification methods.", "weight": 0.2, "ratingGuide": { "5": "Instant QR code verification. Employer API. Skills visible in job platform integrations (LinkedIn, local platforms).", "4": "QR code or link verification. Employer can see verified skills in seconds.", "3": "Online verification portal. Employer manually checks credentials.", "2": "PDF certificate download. Employer must contact issuer to verify.", "1": "No employer-facing verification mechanism." } }, { "id": "SC-SELECTIVE-SKILLS", "name": "Selective Disclosure", "description": "Can a person share specific skills or competencies without revealing all their credentials, training history, or personal information?", "weight": 0.15, "ratingGuide": { "5": "Granular selective disclosure \u2014 share individual skills without revealing anything else. Privacy-preserving proofs.", "4": "Share skill categories selectively. Some personal data hidden.", "3": "Can choose which credentials to share but all details of selected credentials are visible.", "2": "Full skills profile shared during any verification.", "1": "No selective disclosure. All data exposed." } }, { "id": "SC-DEPLOY-MATURITY", "name": "Deployment Maturity", "description": "Is the system production-ready with proven deployments in similar contexts?", "weight": 0.15, "ratingGuide": { "5": "Production deployments in humanitarian or development contexts. Comprehensive documentation. Active support.", "4": "Multiple deployments in education/employment sectors. Good documentation.", "3": "Pilot deployments. Adequate documentation.", "2": "Beta stage with limited testing.", "1": "Prototype only." } } ], "procurement": { "marketMaturity": "emerging", "primaryMode": "rfq", "alternativeModes": [ "off-the-shelf" ], "reasoning": "Skills attestation platforms growing alongside credentials market.", "exampleProductCategories": [ "skills-attestation-platform", "competency-verification-saas" ], "partnerChannels": [], "lastReviewed": "2026-05-01" } }, { "id": "UC-B-036", "name": "Community governance participation eligibility", "category": "B", "subcategory": "Eligibility Verification", "description": "Show who is eligible to take part in a community decision, so results are less likely to be disputed, without exposing members' personal details.", "bCriteria": [ "B1", "B6" ], "requiredComponents": [ { "component": "credential-issuance", "description": "Eligibility credentials" }, { "component": "verification-mechanism", "description": "Proof of eligibility" }, { "component": "identity-protocol", "description": "Community member identity" } ], "conditionalComponents": [ { "component": "privacy-tech", "condition": "If sensitive eligibility criteria" } ], "crossCategoryDependencies": [ "UC-E-068 for voting mechanisms" ], "p2TriggerConditions": { "description": "Activated when P2 shows community governance + participation verification + accountability concerns", "rangeSignals": [ "communityGovernance >= true", "participationTracking >= important", "accountabilityFocus >= high" ] }, "contextFieldsTemplate": [ { "field": "communities", "source": "P0 operations", "description": "Number of communities" }, { "field": "eligibilityCriteria", "source": "P2 governance design", "description": "Participation eligibility rules" }, { "field": "participants", "source": "P2 community size", "description": "Expected participants" }, { "field": "governanceType", "source": "P2 governance structure", "description": "Type of governance" } ], "implementationComplexity": "medium", "examples": { "note": "Community-based governance and participation", "references": [ { "name": "Voatz Blockchain Voting", "url": "https://voatz.com/", "solved": "Blockchain-based voting with identity verification for community governance" }, { "name": "Democracy Earth", "url": "https://democracy.earth/", "solved": "Decentralised governance participation with verifiable eligibility" } ] }, "solutionQuestions": [ { "id": "eligibility-criteria", "type": "select", "options": [ { "label": "Residency in community (geographic-based)", "value": "residency" }, { "label": "Programme beneficiary status", "value": "beneficiary-status" }, { "label": "Age and legal capacity", "value": "age-capacity" }, { "label": "Multiple criteria (residency + age + status)", "value": "multiple" } ], "propertyMapping": { "residency": { "technologies": [ "Residency verification credential", "Geographic attestation module" ], "technologyProperties": { "eligibilityBasis": "Geographic residency", "verificationMethod": "Community attestation of residency", "renewalCycle": "Periodic residency re-verification" } }, "beneficiary-status": { "technologies": [ "Programme enrolment credential", "Status verification engine" ], "technologyProperties": { "eligibilityBasis": "Programme beneficiary status", "verificationMethod": "Enrolment record lookup", "renewalCycle": "Linked to programme enrolment" } }, "age-capacity": { "technologies": [ "Age verification credential", "Capacity assessment module" ], "technologyProperties": { "eligibilityBasis": "Age and legal capacity", "verificationMethod": "Age credential or ZKP age proof", "renewalCycle": "One-time (age threshold)" } }, "multiple": { "technologies": [ "Composite eligibility credential engine", "Multi-factor verification" ], "technologyProperties": { "eligibilityBasis": "Residency + age + programme status", "verificationMethod": "Multi-credential composite check", "renewalCycle": "Per-criterion renewal" } } }, "prefillFrom": null, "briefSection": "Credential issuance", "text": "What determines eligibility for community governance participation?", "ngoText": "What determines eligibility for community governance participation?" }, { "id": "governance-privacy", "type": "select", "options": [ { "label": "Eligibility is publicly verifiable (transparent)", "value": "public" }, { "label": "Private eligibility: verify without revealing personal data", "value": "private-verify" }, { "label": "Anonymous participation: zero-knowledge eligibility proof", "value": "anonymous" } ], "propertyMapping": { "public": { "technologies": [ "Public eligibility registry", "Open voter roll" ], "technologyProperties": { "privacyLevel": "Public", "anonymity": "None \u2014 named participation", "verificationTransparency": "Fully transparent" } }, "private-verify": { "technologies": [ "Selective disclosure eligibility proof", "Privacy-preserving verification" ], "technologyProperties": { "privacyLevel": "Private \u2014 verify without revealing data", "anonymity": "Pseudonymous participation", "verificationTransparency": "Verified but private" } }, "anonymous": { "technologies": [ "Zero-knowledge eligibility proof", "Anonymous credential engine" ], "technologyProperties": { "privacyLevel": "Anonymous", "anonymity": "Full anonymity with eligibility proof", "verificationTransparency": "ZKP-verified eligibility" } } }, "prefillFrom": null, "briefSection": "Verification and privacy", "text": "What privacy protections are needed for governance participation?", "ngoText": "What privacy protections are needed for governance participation?" }, { "id": "governance-reporting", "type": "select", "options": [ { "label": "Participation rates and demographics", "value": "participation" }, { "label": "Governance process audit trail", "value": "audit" }, { "label": "Community feedback and satisfaction", "value": "feedback" } ], "propertyMapping": { "participation": { "technologies": [ "Participation analytics dashboard" ], "technologyProperties": { "reportingScope": "Participation metrics", "disaggregation": "Gender, age, location", "auditDepth": "Aggregate" } }, "audit": { "technologies": [ "Governance audit trail", "Process integrity verifier" ], "technologyProperties": { "reportingScope": "Full governance process", "disaggregation": "Individual-level (anonymised)", "auditDepth": "Complete process audit" } }, "feedback": { "technologies": [ "Community feedback module", "Satisfaction survey engine" ], "technologyProperties": { "reportingScope": "Participation + satisfaction", "disaggregation": "Community-level", "auditDepth": "Feedback summaries" } } }, "prefillFrom": null, "briefSection": "Reporting and audit", "text": "What participation reporting do you currently have?", "ngoText": "What participation reporting do you currently have?" }, { "id": "comm-gov-participant-count", "type": "select", "options": [ { "label": "2\u20135 parties", "value": "small" }, { "label": "6\u201315 parties", "value": "medium" }, { "label": "16\u201350 parties", "value": "large" }, { "label": "Over 50 parties", "value": "enterprise" } ], "propertyMapping": { "small": { "technologies": [ "Simple shared ledger" ], "technologyProperties": { "consensusComplexity": "Low", "governanceModel": "Direct" } }, "medium": { "technologies": [ "Permissioned network", "Role-based access" ], "technologyProperties": { "consensusComplexity": "Medium", "governanceModel": "Committee-based" } }, "large": { "technologies": [ "Scalable permissioned network", "Delegated consensus" ], "technologyProperties": { "consensusComplexity": "High", "governanceModel": "Delegated" } }, "enterprise": { "technologies": [ "Enterprise consortium platform", "Federated consensus" ], "technologyProperties": { "consensusComplexity": "Very high", "governanceModel": "Federated" } } }, "prefillFrom": null, "briefSection": "Governance mechanism", "text": "How many organisations or stakeholders participate in community governance?", "ngoText": "How many organisations or stakeholders participate in community governance?" }, { "id": "sq-UC-B-036-001", "type": "single-select", "options": [ { "value": "credential-scan", "label": "Credential scan" }, { "value": "biometric-match", "label": "Biometric match" }, { "value": "community-attestation", "label": "Community attestation" }, { "value": "token-based", "label": "Token-based verification" }, { "value": "pre-approved-roster", "label": "Pre-approved roster" } ], "propertyMapping": { "credential-scan": { "technologies": [ "credential-reader", "verification-system" ], "technologyProperties": {} }, "biometric-match": { "technologies": [ "biometric-system", "matching-engine" ], "technologyProperties": {} }, "community-attestation": { "technologies": [ "voting-system", "community-verification" ], "technologyProperties": {} }, "token-based": { "technologies": [ "token-verification", "blockchain-token" ], "technologyProperties": {} }, "pre-approved-roster": { "technologies": [ "roster-system", "list-checking" ], "technologyProperties": {} } }, "briefSection": "requirements", "text": "How is eligibility currently verified at the moment of governance participation?", "ngoText": "How is eligibility currently verified at the moment of governance participation?" }, { "id": "sq-UC-B-036-003", "type": "single-select", "options": [ { "value": "on-chain-nullifier", "label": "Digital one-time-use voting token" }, { "value": "physical-token-surrender", "label": "Physical token surrender" }, { "value": "biometric-dedup", "label": "Biometric deduplication" }, { "value": "time-locked-credential", "label": "Time-locked credential" }, { "value": "public-roll-call", "label": "Public roll call" } ], "propertyMapping": { "on-chain-nullifier": { "technologies": [ "nullifier-contract", "blockchain-state" ], "technologyProperties": {} }, "physical-token-surrender": { "technologies": [ "token-management", "physical-control" ], "technologyProperties": {} }, "biometric-dedup": { "technologies": [ "biometric-database", "dedup-engine" ], "technologyProperties": {} }, "time-locked-credential": { "technologies": [ "time-lock", "credential-binding" ], "technologyProperties": {} }, "public-roll-call": { "technologies": [ "public-ledger", "participation-log" ], "technologyProperties": {} } }, "briefSection": "requirements", "text": "How is governance participation currently recorded to prevent double-voting?", "ngoText": "How is governance participation currently recorded to prevent double-voting?" } ], "complexityFactors": { "relationships": 2, "operationalChange": 2, "dataCompliance": 3 }, "suggestedCriteria": [ { "id": "SC-ELIGIBILITY-PRIVACY", "name": "Eligibility Verification Without Identity Exposure", "description": "Can the system prove someone is eligible to participate in governance (by residency, status, age) without revealing who they are?", "weight": 0.3, "ratingGuide": { "5": "Zero-knowledge eligibility proofs. Prove residency/status/age without revealing identity. Unlinkable across votes.", "4": "Pseudonymous eligibility verification. Identity hidden from other participants but known to system.", "3": "Encrypted eligibility check. Verifier can confirm eligibility but with some identity leakage.", "2": "Eligibility verified but identity visible to governance administrators.", "1": "Full identity required for participation. No privacy protection." } }, { "id": "SC-DOUBLE-PREVENTION", "name": "Double-Participation Prevention", "description": "Can the system prevent the same person from registering or voting twice without linking all their actions to their identity?", "weight": 0.25, "ratingGuide": { "5": "Cryptographic uniqueness proofs. Duplicate prevention without identity linking. Provably one-person-one-vote.", "4": "Pseudonymous deduplication. Duplicates detected without full identity exposure.", "3": "Identity-based deduplication with privacy protections. Administrators see identities.", "2": "Basic deduplication using identifying information.", "1": "No deduplication mechanism. Double voting/registration possible." } }, { "id": "SC-PARTICIPATION-MODELS", "name": "Multiple Participation Models", "description": "Does the system support different governance models (public voting, private-verify, anonymous ballot, weighted voting, delegated voting)?", "weight": 0.15, "ratingGuide": { "5": "Configurable per-decision: public, private, anonymous, weighted, delegated, and quorum-based models all supported.", "4": "3-4 participation models available. Configurable per governance event.", "3": "2 models (e.g. public and anonymous voting).", "2": "Single participation model only.", "1": "No formal governance mechanism. Ad-hoc participation." } }, { "id": "SC-COMMUNITY-ACCESS", "name": "Community Accessibility", "description": "Can diverse community members participate, including non-literate individuals, people with disabilities, and those with limited digital skills?", "weight": 0.15, "ratingGuide": { "5": "Multiple input modes: voice, pictorial, assisted, SMS-based. Accessibility standards met. Works on basic phones.", "4": "Accessible interface. Multiple language support. Works on smartphones.", "3": "Smartphone app with good UX. Requires basic digital literacy.", "2": "Web-based interface. Requires computer and digital literacy.", "1": "Complex interface. Requires training and equipment." } }, { "id": "SC-AUDIT-TRANSPARENT", "name": "Audit & Transparency", "description": "Can the governance process be independently verified as fair without compromising individual voter privacy?", "weight": 0.15, "ratingGuide": { "5": "Publicly verifiable election integrity. Cryptographic proofs of fair counting. Individual privacy preserved.", "4": "Audit trail available to independent observers. Results verifiable.", "3": "Audit trail maintained internally. Available on request.", "2": "Basic logging of governance events. Limited auditability.", "1": "No audit mechanism. Results cannot be independently verified." } } ], "procurement": { "marketMaturity": "nascent", "primaryMode": "integrator-led", "alternativeModes": [ "conversation-guide" ], "reasoning": "Community governance eligibility is highly local; bespoke common.", "exampleProductCategories": [ "community-governance-platform", "local-eligibility-rails" ], "partnerChannels": [], "lastReviewed": "2026-05-01" } }, { "id": "UC-B-037", "name": "Consent records and data sharing permissions", "category": "B", "subcategory": "Consent Management", "description": "Keep a record of what each person agreed to share and with whom, so partners can see the permission and the person can change it.", "bCriteria": [ "B1", "B3", "B6" ], "requiredComponents": [ { "component": "consent-management", "description": "Consent record system" }, { "component": "record-keeping-platform", "description": "Immutable consent records" }, { "component": "credential-issuance", "description": "Consent proof credentials" }, { "component": "verification-mechanism", "description": "Proof of consent" } ], "conditionalComponents": [ { "component": "holder-app", "condition": "If beneficiary-managed consent" }, { "component": "privacy-tech", "condition": "For privacy-preserving consent" } ], "crossCategoryDependencies": [ "UC-C-045 for data sharing consent management" ], "p2TriggerConditions": { "description": "Activated when P2 shows data sensitivity + multi-org sharing + consent management burden", "rangeSignals": [ "dataSensitivity >= high", "multiOrgSharing >= true", "consentManagement >= complex" ] }, "contextFieldsTemplate": [ { "field": "beneficiaries", "source": "P2 programme scale", "description": "Beneficiaries with consent needs" }, { "field": "dataTypes", "source": "P2 data collection", "description": "Types of data collected" }, { "field": "sharingOrganisations", "source": "P0 partnerships", "description": "Data sharing partners" }, { "field": "consentGranularity", "source": "P2 data governance", "description": "Consent specificity required" } ], "implementationComplexity": "medium", "examples": { "note": "GDPR compliance, humanitarian data sharing", "references": [ { "name": "Sovrin Foundation Consent Framework", "url": "https://sovrin.org/", "solved": "Self-sovereign consent management framework for privacy-preserving data sharing" }, { "name": "OCHA Centre for Humanitarian Data", "url": "https://centre.humdata.org/", "solved": "Data responsibility guidelines and consent frameworks for humanitarian data sharing" } ] }, "solutionQuestions": [ { "id": "consent-granularity", "type": "select", "options": [ { "label": "Programme-level consent (blanket consent for all data within programme)", "value": "programme-level" }, { "label": "Purpose-level consent (consent per data use purpose)", "value": "purpose-level" }, { "label": "Field-level consent (consent per individual data element)", "value": "field-level" }, { "label": "Recipient-level consent (consent per data sharing partner)", "value": "recipient-level" } ], "propertyMapping": { "programme-level": { "technologies": [ "Programme consent module" ], "technologyProperties": { "granularity": "Programme-wide", "consentObjects": "Entire data profile", "managementComplexity": "Low" } }, "purpose-level": { "technologies": [ "Purpose-based consent engine", "Consent purpose registry" ], "technologyProperties": { "granularity": "Per-purpose", "consentObjects": "Data grouped by purpose", "managementComplexity": "Medium" } }, "field-level": { "technologies": [ "Field-level consent engine", "Granular data access controller" ], "technologyProperties": { "granularity": "Per-field", "consentObjects": "Individual data elements", "managementComplexity": "High" } }, "recipient-level": { "technologies": [ "Recipient consent manager", "Partner-specific consent engine" ], "technologyProperties": { "granularity": "Per-recipient", "consentObjects": "Data bundles per sharing partner", "managementComplexity": "Medium-high" } } }, "prefillFrom": null, "briefSection": "Consent and governance", "text": "What level of consent granularity is needed?", "ngoText": "What level of consent granularity is needed?" }, { "id": "consent-immutability", "type": "select", "options": [ { "label": "Permanent tamper-proof ledger (digital ledger-anchored consent trail)", "value": "immutable-ledger" }, { "label": "Auditable database with tamper-evident logging", "value": "auditable-db" }, { "label": "Beneficiary-held consent credentials (user-controlled portable)", "value": "beneficiary-held" } ], "propertyMapping": { "immutable-ledger": { "technologies": [ "Consent ledger (blockchain-anchored)", "Timestamped consent proof" ], "technologyProperties": { "storageModel": "Blockchain-anchored immutable ledger", "tamperProof": "Cryptographic proof of consent", "disputeResolution": "Immutable audit trail" } }, "auditable-db": { "technologies": [ "Tamper-evident consent database", "Append-only consent log" ], "technologyProperties": { "storageModel": "Auditable database", "tamperProof": "Tamper-evident logging", "disputeResolution": "Log-based audit" } }, "beneficiary-held": { "technologies": [ "Self-sovereign consent credential", "Beneficiary consent wallet" ], "technologyProperties": { "storageModel": "Beneficiary-held credentials", "tamperProof": "Cryptographically signed consent", "disputeResolution": "Holder presents consent proof" } } }, "prefillFrom": null, "briefSection": "Identity protocol", "text": "How are consent records currently stored and proven in your operations?", "ngoText": "How are consent records currently stored and proven in your operations?" }, { "id": "consent-withdrawal", "type": "select", "options": [ { "label": "Full withdrawal (all data sharing stopped)", "value": "full-withdrawal" }, { "label": "Selective withdrawal (withdraw specific consents)", "value": "selective" }, { "label": "Right to erasure (data deletion on withdrawal)", "value": "right-to-erasure" } ], "propertyMapping": { "full-withdrawal": { "technologies": [ "Consent withdrawal engine", "Data access revocation module" ], "technologyProperties": { "withdrawalModel": "Full programme withdrawal", "withdrawalEffect": "All data sharing stopped", "dataRetention": "Archived per legal requirement" } }, "selective": { "technologies": [ "Selective withdrawal engine", "Granular access revocation" ], "technologyProperties": { "withdrawalModel": "Per-purpose or per-recipient", "withdrawalEffect": "Specific sharing stopped", "dataRetention": "Retained for non-withdrawn purposes" } }, "right-to-erasure": { "technologies": [ "Data erasure engine", "Distributed deletion protocol", "Erasure confirmation module" ], "technologyProperties": { "withdrawalModel": "Full withdrawal + data deletion", "withdrawalEffect": "Data erased across all systems", "dataRetention": "Deleted (with legal exceptions)" } } }, "prefillFrom": null, "briefSection": "Consent and governance", "text": "How is consent withdrawal currently handled?", "ngoText": "How is consent withdrawal currently handled?" }, { "id": "consent-beneficiary-interface", "type": "select", "options": [ { "label": "Through field staff at service points", "value": "staff-mediated" }, { "label": "Self-service via mobile app", "value": "self-service-app" }, { "label": "USSD/SMS-based consent management", "value": "ussd-sms" }, { "label": "Mixed channels", "value": "mixed" } ], "propertyMapping": { "staff-mediated": { "technologies": [ "Staff consent management interface", "Consent capture workflow" ], "technologyProperties": { "beneficiaryInterface": "Staff-mediated", "selfService": "No \u2014 staff assists", "accessibilityLevel": "Field-appropriate" } }, "self-service-app": { "technologies": [ "Consent management mobile app", "Self-service consent dashboard" ], "technologyProperties": { "beneficiaryInterface": "Mobile app", "selfService": "Full self-service", "accessibilityLevel": "Smartphone required" } }, "ussd-sms": { "technologies": [ "USSD consent menu", "SMS consent commands" ], "technologyProperties": { "beneficiaryInterface": "USSD/SMS", "selfService": "Basic self-service", "accessibilityLevel": "Any phone" } }, "mixed": { "technologies": [ "Multi-channel consent platform" ], "technologyProperties": { "beneficiaryInterface": "App + SMS + staff", "selfService": "Adaptive", "accessibilityLevel": "Universal" } } }, "prefillFrom": null, "briefSection": "Holder experience", "text": "How will beneficiaries manage their consent preferences?", "ngoText": "How will beneficiaries manage their consent preferences?" }, { "id": "consent-reporting", "type": "select", "options": [ { "label": "Internal compliance dashboard", "value": "internal" }, { "label": "Data protection authority reporting (GDPR Art. 30)", "value": "dpa-reporting" }, { "label": "Donor data protection compliance evidence", "value": "donor-compliance" } ], "propertyMapping": { "internal": { "technologies": [ "Consent compliance dashboard" ], "technologyProperties": { "reportingScope": "Internal oversight", "complianceStandard": "Organisational policy", "auditReadiness": "Basic" } }, "dpa-reporting": { "technologies": [ "GDPR Article 30 reporting module", "Processing activities register" ], "technologyProperties": { "reportingScope": "Data protection authority", "complianceStandard": "GDPR/national data protection", "auditReadiness": "DPA audit-ready" } }, "donor-compliance": { "technologies": [ "Donor data compliance module", "Consent metrics dashboard" ], "technologyProperties": { "reportingScope": "Donor accountability", "complianceStandard": "Donor data protection requirements", "auditReadiness": "Donor audit-ready" } } }, "prefillFrom": null, "briefSection": "Reporting and audit", "text": "What consent compliance reporting is needed?", "ngoText": "What consent compliance reporting is needed?" }, { "id": "verification-mechanism", "type": "select", "options": [ { "label": "digitally verified (signature-based proof)", "value": "cryptographic" }, { "label": "Multi-party attestation (multiple parties vouch)", "value": "multi-party" }, { "label": "Biometric verification", "value": "biometric" }, { "label": "Document-based verification with hash proof", "value": "document-hash" } ], "propertyMapping": { "cryptographic": { "technologies": [ "Cryptographic verification mechanism", "Digital signature service", "Proof verification API" ], "technologyProperties": { "verificationMethod": "Cryptographic signature", "trustModel": "Issuer signature verification", "offlineCapable": "Yes" } }, "multi-party": { "technologies": [ "Multi-party verification mechanism", "Attestation collection service", "Threshold verification engine" ], "technologyProperties": { "verificationMethod": "Multi-party attestation", "trustModel": "Quorum of trusted attesters", "offlineCapable": "Partial \u2014 cached attestations" } }, "biometric": { "technologies": [ "Biometric verification mechanism", "Biometric matching service", "Liveness detection module" ], "technologyProperties": { "verificationMethod": "Biometric match", "trustModel": "Biometric template comparison", "offlineCapable": "Yes \u2014 on-device matching" } }, "document-hash": { "technologies": [ "Document verification mechanism", "Hash comparison service", "Document authenticity checker" ], "technologyProperties": { "verificationMethod": "Document hash comparison", "trustModel": "Original document hash Digital", "offlineCapable": "Partial" } } }, "prefillFrom": null, "briefSection": "Verification", "text": "How are credentials or records currently verified?", "ngoText": "How are credentials or records currently verified?" }, { "id": "beneficiary-choice", "label": "How will beneficiaries exercise choice in how they receive and use this service?", "type": "select", "briefSection": "Holder experience", "options": [ { "label": "Beneficiaries choose between delivery methods (cash, voucher, mobile money, direct)", "value": "delivery-choice" }, { "label": "Beneficiaries choose preferred merchants or service points", "value": "merchant-choice" }, { "label": "Beneficiaries control their own data sharing preferences", "value": "data-choice" }, { "label": "Multiple choice dimensions (delivery + merchant + data)", "value": "full-choice" }, { "label": "Limited choice: programme constraints determine delivery", "value": "limited" } ], "propertyMapping": { "delivery-choice": { "technologies": [], "technologyProperties": { "beneficiaryChoice": "Delivery method choice", "dignityDesign": "Beneficiaries select preferred receipt method" } }, "merchant-choice": { "technologies": [], "technologyProperties": { "beneficiaryChoice": "Merchant/service point choice", "dignityDesign": "Beneficiaries select where to redeem" } }, "data-choice": { "technologies": [], "technologyProperties": { "beneficiaryChoice": "Data sharing choice", "dignityDesign": "Beneficiaries control personal data sharing" } }, "full-choice": { "technologies": [], "technologyProperties": { "beneficiaryChoice": "Multi-dimensional choice", "dignityDesign": "Full beneficiary agency across delivery, merchant, and data" } }, "limited": { "technologies": [], "technologyProperties": { "beneficiaryChoice": "Limited by programme design", "dignityDesign": "Programme constraints; beneficiary informed of reasons" } } }, "text": "How will beneficiaries exercise choice in how they receive and use this service?" } ], "complexityFactors": { "relationships": 2, "operationalChange": 3, "dataCompliance": 4 }, "suggestedCriteria": [ { "id": "SC-CONSENT-GRANULARITY", "name": "Consent Granularity", "description": "This measures the level of consent control the system supports. From broad programme-level consent to fine-grained field-level and recipient-specific permissions.", "weight": 0.25, "ratingGuide": { "5": "Field-level and recipient-specific consent. Beneficiary controls exactly which data fields are shared with which organisations.", "4": "Purpose-level consent. Different consent for health, cash, protection. Per-organisation controls.", "3": "Programme-level consent with some purpose distinctions.", "2": "Broad programme-level consent only. All-or-nothing for each programme.", "1": "Single consent covering all data and all purposes." } }, { "id": "SC-BENEFICIARY-CONTROL", "name": "Beneficiary Control & Withdrawal", "description": "Beneficiaries can easily understand, manage, and withdraw their consent. Must be accessible to non-literate populations.", "weight": 0.25, "ratingGuide": { "5": "Beneficiary-held consent credentials. Easy visual consent management. One-tap withdrawal. Multi-language with pictorial/voice support.", "4": "Digital consent dashboard accessible to beneficiaries. Clear withdrawal mechanism.", "3": "Consent viewable by beneficiaries. Withdrawal possible but requires assistance.", "2": "Consent managed by organisation on beneficiary's behalf. Withdrawal requires formal request.", "1": "No beneficiary-facing consent management. Organisation controls all consent." } }, { "id": "SC-TAMPER-PROOF", "name": "Tamper-Proof Record Keeping", "description": "Is the consent record immutable? Can anyone prove that consent was given (or withdrawn) at a specific time without the record being altered?", "weight": 0.2, "ratingGuide": { "5": "Blockchain-anchored consent records. Cryptographically timestamped. Independently verifiable by any party.", "4": "Tamper-evident record keeping. Audit trail with integrity proofs.", "3": "Secure database with audit logging. Tampering detectable internally.", "2": "Standard database with basic logging. Tampering possible but logged.", "1": "No tamper protection. Records can be modified without detection." } }, { "id": "SC-CROSS-ORG-CONSENT", "name": "Cross-Organisation Consent Sharing", "description": "Can partner organisations verify that consent exists without accessing a centralised consent database?", "weight": 0.15, "ratingGuide": { "5": "Decentralised consent verification. Partners verify consent proofs without accessing centralised records. Beneficiary-portable.", "4": "Federated consent queries. Partners check consent status through shared protocol.", "3": "API-based consent checks. Partners query central system.", "2": "Consent status shared manually between organisations.", "1": "No cross-organisation consent sharing. Each organisation manages separately." } }, { "id": "SC-REGULATORY-CONSENT", "name": "Regulatory Compliance", "description": "Does the system comply with GDPR, local data protection laws, and humanitarian data protection principles for consent management?", "weight": 0.15, "ratingGuide": { "5": "GDPR Article 7 compliant. Meets ICRC data protection standards. Automated compliance reporting. Privacy impact assessment built in.", "4": "Strong regulatory compliance. GDPR-ready. Data protection principles embedded.", "3": "Basic GDPR compliance. Manual compliance reporting.", "2": "Aware of data protection requirements but limited compliance features.", "1": "No regulatory compliance features." } } ], "procurement": { "marketMaturity": "emerging", "primaryMode": "off-the-shelf", "alternativeModes": [ "rfq" ], "reasoning": "Consent management SaaS market is maturing.", "exampleProductCategories": [ "consent-management-saas", "privacy-records-platform" ], "partnerChannels": [], "lastReviewed": "2026-05-01" } }, { "id": "UC-B-038", "name": "Age verification for child protection programmes", "category": "B", "subcategory": "Eligibility Verification", "description": "Confirm that a child meets an age requirement without storing or sharing more about the child than needed, and keep the answer consistent across programmes.", "bCriteria": [ "B3", "B6" ], "requiredComponents": [ { "component": "verification-mechanism", "description": "Age verification without revealing exact birthdate" }, { "component": "credential-issuance", "description": "Age range credentials" }, { "component": "consent-management", "description": "Child/guardian consent" } ], "conditionalComponents": [ { "component": "biometric-capture", "condition": "If facial age estimation used" }, { "component": "privacy-tech", "condition": "For privacy-preserving age proof" } ], "crossCategoryDependencies": [], "p2TriggerConditions": { "description": "Activated when P2 shows child protection focus + age-based targeting + privacy concerns", "rangeSignals": [ "childProtection >= true", "ageTargeting >= critical", "privacyConcerns >= high" ] }, "contextFieldsTemplate": [ { "field": "children", "source": "P2 programme scale", "description": "Number of children" }, { "field": "ageGroups", "source": "P2 eligibility criteria", "description": "Target age ranges" }, { "field": "privacyRequirements", "source": "P0 Q19-21 + P5", "description": "Child data protection rules" }, { "field": "verificationMethod", "source": "P2 M&E practices", "description": "Age verification approach" } ], "implementationComplexity": "medium", "examples": { "note": "Child protection and safeguarding", "references": [ { "name": "Yoti Age Verification", "url": "https://www.yoti.com/business/age-verification/", "solved": "Privacy-preserving age verification using facial estimation technology" }, { "name": "UNICEF Child Protection", "url": "https://www.unicef.org/protection", "solved": "Child protection programme standards including age verification protocols" } ] }, "solutionQuestions": [ { "id": "age-verification-method", "type": "select", "options": [ { "label": "Document-based (birth certificate, ID with DOB)", "value": "document-based" }, { "label": "AI-based facial age estimation", "value": "ai-estimation" }, { "label": "Community attestation (community members verify age)", "value": "community-attestation" }, { "label": "Skeletal/dental age assessment (medical)", "value": "medical-assessment" } ], "propertyMapping": { "document-based": { "technologies": [ "Document-based age verification", "DOB credential engine" ], "technologyProperties": { "verificationMethod": "Document scan + DOB extraction", "accuracy": "High (if documents available)", "invasiveness": "Low" } }, "ai-estimation": { "technologies": [ "Facial age estimation AI", "Privacy-preserving age classifier" ], "technologyProperties": { "verificationMethod": "AI facial age estimation", "accuracy": "Medium (\u00b12-3 years)", "invasiveness": "Low (photo only)" } }, "community-attestation": { "technologies": [ "Community age attestation protocol", "Multi-witness age verification" ], "technologyProperties": { "verificationMethod": "Community witness attestation", "accuracy": "Variable (depends on witnesses)", "invasiveness": "Low (social process)" } }, "medical-assessment": { "technologies": [ "Medical age assessment module" ], "technologyProperties": { "verificationMethod": "Medical assessment referral", "accuracy": "Medium-high (\u00b11-2 years)", "invasiveness": "High (medical procedure)" } } }, "prefillFrom": null, "briefSection": "Verification and privacy", "text": "How do you currently verify someone's age?", "ngoText": "How do you currently verify someone's age?" }, { "id": "age-proof-type", "type": "select", "options": [ { "label": "Exact date of birth credential", "value": "exact-dob" }, { "label": "Age range credential (e.g., under-18, 12-15)", "value": "age-range" }, { "label": "Binary proof (over/under threshold, no age revealed)", "value": "binary-proof" } ], "propertyMapping": { "exact-dob": { "technologies": [ "DOB verifiable credential", "Date-based age calculation" ], "technologyProperties": { "credentialContent": "Exact date of birth", "privacyLevel": "Full DOB disclosed", "verificationPrecision": "Exact age" } }, "age-range": { "technologies": [ "Age range credential engine", "Band-based age classification" ], "technologyProperties": { "credentialContent": "Age range only", "privacyLevel": "DOB not disclosed \u2014 range only", "verificationPrecision": "Age band (e.g., 12-15)" } }, "binary-proof": { "technologies": [ "Zero-knowledge age proof", "Threshold age verification" ], "technologyProperties": { "credentialContent": "Binary over/under threshold", "privacyLevel": "Maximum \u2014 no age data revealed", "verificationPrecision": "Binary (eligible/not)" } } }, "prefillFrom": null, "briefSection": "Credential issuance", "text": "What type of age documentation do people in your context typically have?", "ngoText": "What type of age documentation do people in your context typically have?" }, { "id": "child-consent", "type": "select", "options": [ { "label": "Guardian consent required for all verification", "value": "guardian-required" }, { "label": "Guardian consent + child assent (age-appropriate)", "value": "guardian-plus-assent" }, { "label": "Mature minor self-consent (for older adolescents)", "value": "mature-minor" } ], "propertyMapping": { "guardian-required": { "technologies": [ "Guardian consent gateway", "Parental authorisation module" ], "technologyProperties": { "consentModel": "Guardian consent required", "childParticipation": "Guardian-mediated", "ageThreshold": "All children regardless of age" } }, "guardian-plus-assent": { "technologies": [ "Age-appropriate consent workflow", "Child assent module" ], "technologyProperties": { "consentModel": "Guardian consent + child assent", "childParticipation": "Age-appropriate participation", "ageThreshold": "Assent from age 7+" } }, "mature-minor": { "technologies": [ "Mature minor assessment module", "Graduated consent engine" ], "technologyProperties": { "consentModel": "Graduated \u2014 guardian for young, self-consent for mature minors", "childParticipation": "Self-consent above maturity threshold", "ageThreshold": "Self-consent from age 16+" } } }, "prefillFrom": null, "briefSection": "Consent and governance", "text": "What consent model is needed for verifying children's ages?", "ngoText": "What consent model is needed for verifying children's ages?" }, { "id": "child-data-protection", "type": "select", "options": [ { "label": "Standard child data protection (encrypted, access-controlled)", "value": "standard" }, { "label": "Enhanced protection (no central age data stored)", "value": "enhanced" }, { "label": "Maximum protection (zero-knowledge: no data retained)", "value": "maximum" } ], "propertyMapping": { "standard": { "technologies": [ "Encrypted child data store", "Child-specific access controls" ], "technologyProperties": { "dataProtectionLevel": "Standard encryption + child-specific RBAC", "dataRetention": "Stored securely with access controls", "complianceStandard": "National child protection laws" } }, "enhanced": { "technologies": [ "Decentralised age credential", "No-central-store architecture" ], "technologyProperties": { "dataProtectionLevel": "Enhanced \u2014 no central age data", "dataRetention": "Credential-based (no central store)", "complianceStandard": "GDPR children's provisions" } }, "maximum": { "technologies": [ "Zero-knowledge age verification", "Ephemeral verification (no data retained)" ], "technologyProperties": { "dataProtectionLevel": "Maximum \u2014 zero data retention", "dataRetention": "None \u2014 ephemeral verification", "complianceStandard": "Maximum child protection" } } }, "prefillFrom": null, "briefSection": "Identity protocol", "text": "What level of data protection is required for children's records?", "ngoText": "What level of data protection is required for children's records?" }, { "id": "age-reporting", "type": "select", "options": [ { "label": "Aggregate statistics (number of children verified by age group)", "value": "aggregate" }, { "label": "Safeguarding compliance reporting", "value": "safeguarding" }, { "label": "Full child protection audit trail", "value": "full-audit" } ], "propertyMapping": { "aggregate": { "technologies": [ "Age verification statistics dashboard" ], "technologyProperties": { "reportingScope": "Aggregate counts", "disaggregation": "Age group, gender, location", "auditDepth": "Summary only" } }, "safeguarding": { "technologies": [ "Safeguarding compliance module", "Age verification compliance dashboard" ], "technologyProperties": { "reportingScope": "Safeguarding compliance", "disaggregation": "Programme-level compliance", "auditDepth": "Compliance evidence" } }, "full-audit": { "technologies": [ "Child protection audit trail", "Full verification history" ], "technologyProperties": { "reportingScope": "Complete audit trail", "disaggregation": "Individual-level (anonymised)", "auditDepth": "Every verification logged" } } }, "prefillFrom": null, "briefSection": "Reporting and audit", "text": "What age verification reporting is needed?", "ngoText": "What age verification reporting is needed?" }, { "id": "beneficiary-choice", "label": "How will beneficiaries exercise choice in how they receive and use this service?", "type": "select", "briefSection": "Holder experience", "options": [ { "label": "Beneficiaries choose between delivery methods (cash, voucher, mobile money, direct)", "value": "delivery-choice" }, { "label": "Beneficiaries choose preferred merchants or service points", "value": "merchant-choice" }, { "label": "Beneficiaries control their own data sharing preferences", "value": "data-choice" }, { "label": "Multiple choice dimensions (delivery + merchant + data)", "value": "full-choice" }, { "label": "Limited choice: programme constraints determine delivery", "value": "limited" } ], "propertyMapping": { "delivery-choice": { "technologies": [], "technologyProperties": { "beneficiaryChoice": "Delivery method choice", "dignityDesign": "Beneficiaries select preferred receipt method" } }, "merchant-choice": { "technologies": [], "technologyProperties": { "beneficiaryChoice": "Merchant/service point choice", "dignityDesign": "Beneficiaries select where to redeem" } }, "data-choice": { "technologies": [], "technologyProperties": { "beneficiaryChoice": "Data sharing choice", "dignityDesign": "Beneficiaries control personal data sharing" } }, "full-choice": { "technologies": [], "technologyProperties": { "beneficiaryChoice": "Multi-dimensional choice", "dignityDesign": "Full beneficiary agency across delivery, merchant, and data" } }, "limited": { "technologies": [], "technologyProperties": { "beneficiaryChoice": "Limited by programme design", "dignityDesign": "Programme constraints; beneficiary informed of reasons" } } }, "text": "How will beneficiaries exercise choice in how they receive and use this service?" } ], "complexityFactors": { "relationships": 3, "operationalChange": 2, "dataCompliance": 5 }, "securityTier": "C", "suggestedCriteria": [ { "id": "SC-AGE-PROOF-PRIVACY", "name": "Privacy-Preserving Age Proof", "description": "Can the system prove a person is over or under an age threshold without revealing their date of birth, identity, or underlying evidence?", "weight": 0.35, "ratingGuide": { "5": "Zero-knowledge age proof \u2014 binary over/under response with no additional data revealed. Mathematically provable.", "4": "Age-range credential (e.g. '12-17') without revealing exact age. Selective disclosure.", "3": "Encrypted age verification \u2014 verifier sees age range but not underlying documents.", "2": "Age verified but date of birth or identity shared with verifier.", "1": "Full identity and documentation revealed for age check." } }, { "id": "SC-NO-BACKDOOR-MINOR", "name": "De-anonymisation Protection for Minors", "description": "This checks whether the system can be compelled to reveal a child's identity. In child protection contexts, exposure could lead to trafficking, forced recruitment, or persecution.", "weight": 0.25, "ratingGuide": { "5": "Protocol-level privacy \u2014 no entity can de-anonymise the child. Verification proofs contain zero identifying information.", "4": "Privacy by default. De-anonymisation requires guardian consent and active participation.", "3": "Provider holds keys but with strong legal protections and child-specific safeguards.", "2": "Identity could be revealed under court order or government compulsion.", "1": "System operator can access child identity records at any time." } }, { "id": "SC-MULTI-EVIDENCE", "name": "Multiple Evidence Pathway Support", "description": "Age can be established through multiple methods. Many children lack birth certificates. The system must support alternative evidence (AI estimation, community attestation, medical assessment).", "weight": 0.15, "ratingGuide": { "5": "Supports 4+ evidence types: documents, AI facial estimation, community attestation, medical assessment. Weighted composite scoring.", "4": "Supports 3 evidence types with configurable weighting.", "3": "Supports 2 evidence types (e.g. documents + one alternative).", "2": "Primarily document-based with limited fallback options.", "1": "Document-only. No alternative evidence pathways for undocumented children." } }, { "id": "SC-GUARDIAN-CONSENT", "name": "Guardian Consent Integration", "description": "This looks at how guardian consent is captured, verified, and recorded for age verification of children. Must comply with child protection principles.", "weight": 0.15, "ratingGuide": { "5": "Privacy-preserving guardian consent \u2014 consent recorded without revealing guardian identity. Withdrawal mechanism built in.", "4": "Digital consent capture with guardian verification. Clear withdrawal process.", "3": "Consent captured but guardian verification is basic. Withdrawal possible but manual.", "2": "Paper-based consent only. No digital capture or withdrawal mechanism.", "1": "No guardian consent mechanism. Age verification proceeds without consent framework." } }, { "id": "SC-PROTECTION-DEPLOY", "name": "Child Protection Field Readiness", "description": "The system can be deployed rapidly in protection contexts. Works on mobile devices, in low-connectivity settings, and integrates with child protection case management.", "weight": 0.1, "ratingGuide": { "5": "Purpose-built for child protection. Offline-capable, mobile-first, integrates with CPIMS+ or equivalent. Rapid deployment kit.", "4": "Adaptable to protection contexts. Works offline on smartphones. Some integration capability.", "3": "General-purpose verification adaptable to protection. Requires customisation.", "2": "Primarily designed for formal settings. Limited mobile or offline capability.", "1": "Desktop-only, requires constant connectivity. No protection-context features." } } ], "procurement": { "marketMaturity": "nascent", "primaryMode": "integrator-led", "alternativeModes": [ "consortium" ], "reasoning": "Age verification for child protection is sensitive; integration with safeguarding processes critical.", "exampleProductCategories": [ "child-protection-platform", "privacy-preserving-age-verification" ], "partnerChannels": [], "lastReviewed": "2026-05-01" } }, { "id": "UC-C-039", "name": "Medical records (private but verifiable)", "category": "C", "subcategory": "Health Data Management", "description": "Let a clinic share a patient's records with another provider who can confirm they are genuine and unchanged, while the patient controls which parts are seen.", "bCriteria": [ "B3", "B6" ], "requiredComponents": [ { "component": "data-layer", "description": "Distributed health records storage" }, { "component": "encryption-privacy", "description": "End-to-end encryption for medical data" }, { "component": "access-control", "description": "Granular access control for health records" }, { "component": "verification-mechanism", "description": "Proof of medical record existence" } ], "conditionalComponents": [ { "component": "consent-management", "condition": "For patient consent to data access", "linksTo": "UC-B-037" }, { "component": "privacy-tech", "condition": "For zero-knowledge proofs of medical facts" } ], "crossCategoryDependencies": [ "UC-B-037 for consent", "UC-C-045 for consent audit" ], "p2TriggerConditions": { "description": "Activated when P2 shows health programmes + privacy concerns + verifiable data needs", "rangeSignals": [ "healthProgrammes >= true", "privacySensitivity >= high", "verifiableEvidence >= needed" ] }, "contextFieldsTemplate": [ { "field": "patients", "source": "P2 health programme scale", "description": "Number of patients" }, { "field": "dataTypes", "source": "P2 health services", "description": "Types of health records" }, { "field": "privacyRegulation", "source": "P0 Q19-21", "description": "Health data privacy laws" }, { "field": "dataAccessNeeds", "source": "P2 referrals", "description": "Who needs to access records" } ], "implementationComplexity": "high", "examples": { "note": "Decentralized health records, patient data ownership", "references": [ { "name": "Verifiable Credentials Data Model (W3C)", "url": "https://www.w3.org/TR/vc-data-model/", "solved": "Standard format for tamper-evident medical credentials and patient identity" }, { "name": "MedRec (MIT Media Lab)", "url": "https://medrec.media.mit.edu/", "solved": "Blockchain-based personal health record system with patient-centric control and provider interoperability" }, { "name": "Guardtime KSI Blockchain for Healthcare", "url": "https://guardtime.com/healthcare", "solved": "Immutable audit trails and data integrity verification for medical records without storing data on-chain" } ] }, "solutionQuestions": [ { "id": "health-data-architecture", "type": "select", "options": [ { "label": "Centralized hospital database system", "value": "centralized-database" }, { "label": "Paper records with manual access", "value": "paper-records" }, { "label": "Multiple disconnected clinic systems", "value": "disconnected-systems" }, { "label": "Cloud-based EHR system", "value": "cloud-ehr" }, { "label": "Mix of digital and paper records", "value": "hybrid-records" } ], "propertyMapping": { "centralized-database": { "technologies": [ "FHIR-compliant health data store" ], "technologyProperties": { "dataModel": "HL7 FHIR standard", "storageLocation": "Centralized with blockchain audit", "interoperability": "REST API endpoints" } }, "paper-records": { "technologies": [ "Document scanning and digitization layer", "FHIR-compliant health data store" ], "technologyProperties": { "dataModel": "Scanned documents with metadata", "storageLocation": "Distributed storage with hash verification", "archiveCapability": "Long-term preservation" } }, "disconnected-systems": { "technologies": [ "Health data interoperability gateway", "FHIR mapping engine" ], "technologyProperties": { "dataModel": "Unified FHIR model", "synchronization": "Periodic batch sync with conflict resolution", "clinicIntegration": "Multiple API connectors" } }, "cloud-ehr": { "technologies": [ "FHIR-compliant health data store", "Cloud storage integration layer" ], "technologyProperties": { "dataModel": "HL7 FHIR standard", "storageLocation": "Multi-cloud with redundancy", "compliance": "HIPAA-compliant encryption" } }, "hybrid-records": { "technologies": [ "Document scanning and digitization layer", "FHIR-compliant health data store", "Hybrid record management system" ], "technologyProperties": { "dataModel": "Mixed digital and scanned", "storageLocation": "Distributed with audit trail", "unificationCapability": "Gradual digitization" } } }, "prefillFrom": null, "briefSection": "Data architecture", "text": "How do you currently store and manage patient health records?", "ngoText": "How do you currently store and manage patient health records?", "hidden": true }, { "id": "access-control-model", "type": "select", "options": [ { "label": "Patient controls all access (explicit consent per access)", "value": "patient-controlled" }, { "label": "Role-based access (doctors, nurses, admins)", "value": "role-based" }, { "label": "Attribute-based access (credentials, time, location)", "value": "attribute-based" }, { "label": "Time-limited access (emergency override with audit)", "value": "time-limited" }, { "label": "Hierarchical access (consulting physicians can grant access)", "value": "hierarchical" } ], "propertyMapping": { "patient-controlled": { "technologies": [ "Automated access control", "Consent management interface" ], "technologyProperties": { "consentModel": "Explicit per-transaction consent", "accessLogging": "Immutable audit trail", "revokeCapability": "Real-time access revocation" } }, "role-based": { "technologies": [ "Role-based access control (RBAC) engine", "Provider registry" ], "technologyProperties": { "roleDefinition": "Standardized healthcare roles", "providerAuth": "Digital identity verification", "auditTrail": "Comprehensive access logging" } }, "attribute-based": { "technologies": [ "Attribute-based access control (ABAC) engine", "Verifiable credentials" ], "technologyProperties": { "attributeSource": "Self-sovereign identity", "policyLanguage": "Attribute evaluation rules", "contextAwareness": "Location, time, device context" } }, "time-limited": { "technologies": [ "Time-locked smart contract", "Emergency access protocol" ], "technologyProperties": { "normalAccess": "Scheduled, time-bound grants", "emergencyOverride": "Break-glass with immediate audit", "auditThreshold": "Real-time notification" } }, "hierarchical": { "technologies": [ "Hierarchical delegation smart contract", "Credential chain verification" ], "technologyProperties": { "delegationDepth": "Multi-level provider chain", "credentialVerification": "Transitive trust verification", "accessScope": "Inherited and delegated permissions" } } }, "prefillFrom": null, "briefSection": "Access control", "text": "Who currently has access to medical records, and how is that controlled?", "ngoText": "Who currently has access to medical records, and how is that controlled?" }, { "id": "consent-granularity", "type": "select", "options": [ { "label": "Broad consent (all data to all providers)", "value": "broad-consent" }, { "label": "Per-record type consent (consent for each data category)", "value": "per-type-consent" }, { "label": "Per-purpose consent (specific use cases like diagnosis vs. research)", "value": "per-purpose-consent" }, { "label": "Granular per-field consent (consent for specific data elements)", "value": "granular-consent" }, { "label": "Dynamic consent (real-time requests and decisions)", "value": "dynamic-consent" } ], "propertyMapping": { "broad-consent": { "technologies": [ "Simple consent registry", "Basic consent interface" ], "technologyProperties": { "scope": "All data to authorized providers", "updateFrequency": "Annual review", "revokeProcess": "Manual revocation only" } }, "per-type-consent": { "technologies": [ "Consent management system (CMS)", "Data classification engine" ], "technologyProperties": { "categories": "FHIR resource types", "granularity": "Per resource category", "withdrawalOption": "Per-category withdrawal" } }, "per-purpose-consent": { "technologies": [ "Purpose-based consent engine", "Use case registry" ], "technologyProperties": { "purposes": "Clinical, research, public health", "purposeVerification": "Provider attestation", "consentLifecycle": "Purpose-specific expiry" } }, "granular-consent": { "technologies": [ "Granular consent management platform", "Data element tagging engine" ], "technologyProperties": { "granularity": "Individual FHIR elements", "consentModel": "Patient-specified inclusions/exclusions", "scalability": "Handles millions of elements" } }, "dynamic-consent": { "technologies": [ "Dynamic consent decision platform", "Real-time consent request interface" ], "technologyProperties": { "requestTiming": "Just-in-time consent requests", "responseTime": "Synchronous or asynchronous", "auditTrail": "Complete consent history" } } }, "prefillFrom": null, "briefSection": "Consent management", "text": "What is your current consent granularity requirement? (Do you consent per record, per data category, or blanket?)", "ngoText": "What is your current consent granularity requirement? (Do you consent per record, per data category, or blanket?)" }, { "id": "interoperability-systems", "type": "select", "options": [ { "label": "National health information exchange (HIE)", "value": "national-hie" }, { "label": "Regional hospital networks only", "value": "regional-networks" }, { "label": "International medical tourism and cross-border care", "value": "international" }, { "label": "Public health surveillance systems", "value": "public-health" }, { "label": "Research and data analytics networks", "value": "research-networks" } ], "propertyMapping": { "national-hie": { "technologies": [ "FHIR REST API gateway", "National HIE connection" ], "technologyProperties": { "standard": "HL7 FHIR with national extensions", "governance": "National health authority compliance", "dataMapping": "Standardized national data model" } }, "regional-networks": { "technologies": [ "Regional FHIR gateway", "Hospital system integrator" ], "technologyProperties": { "standard": "HL7 FHIR core", "scopeGeography": "Regional jurisdiction", "integrationPattern": "Hub-and-spoke or peer-to-peer" } }, "international": { "technologies": [ "International FHIR translation engine", "Multi-jurisdiction consent coordinator" ], "technologyProperties": { "standard": "HL7 FHIR with international extensions", "jurisdictions": "GDPR, HIPAA, local regulations", "dataResidency": "Jurisdiction-specific storage" } }, "public-health": { "technologies": [ "Public health data transformer", "Disease surveillance integration" ], "technologyProperties": { "dataMinimization": "Aggregate or de-identified only", "reporting": "Automated disease surveillance", "privacyPreservation": "Differential privacy or aggregation" } }, "research-networks": { "technologies": [ "Research data access platform", "De-identification and anonymization engine" ], "technologyProperties": { "accessControl": "IRB-approved research protocols", "dataFormat": "De-identified FHIR or custom format", "auditLogging": "Complete research access audit" } } }, "prefillFrom": null, "briefSection": "Interoperability", "text": "What health systems or networks do you need to interoperate with?", "ngoText": "What health systems or networks do you need to interoperate with?" }, { "id": "offline-capability", "type": "select", "options": [ { "label": "Full offline access with sync when connectivity returns", "value": "full-offline" }, { "label": "Read-only offline access with online updates only", "value": "read-only-offline" }, { "label": "Cached records only for current patient", "value": "cached-only" }, { "label": "Always requires connectivity; offline not needed", "value": "online-only" }, { "label": "Hybrid: critical data cached, rest online", "value": "hybrid-offline" } ], "propertyMapping": { "full-offline": { "technologies": [ "Offline-capable data sync layer", "Conflict resolution engine" ], "technologyProperties": { "syncMechanism": "Eventual consistency with CRDTs", "storageLocal": "Encrypted local database", "conflictResolution": "Last-write-wins or policy-based" } }, "read-only-offline": { "technologies": [ "Read-only cache layer", "Online verification on reconnect" ], "technologyProperties": { "cacheRefresh": "Manual sync on reconnection", "dataFreshness": "As-of last sync timestamp", "writeProtection": "No local writes allowed" } }, "cached-only": { "technologies": [ "Current patient cache", "Quick sync mechanism" ], "technologyProperties": { "cacheSize": "Active patient data only", "autoSync": "On each patient switch", "expiryPolicy": "Time-based cache expiry" } }, "online-only": { "technologies": [ "Low-bandwidth FHIR client", "Connectivity monitoring" ], "technologyProperties": { "requiredBandwidth": "Minimal (e.g., GPRS capable)", "timeout": "User-friendly error messaging", "fallback": "No fallback; connectivity required" } }, "hybrid-offline": { "technologies": [ "Intelligent cache with offline mode", "Sync prioritization engine" ], "technologyProperties": { "priorityData": "Recent records, emergency summaries", "syncStrategy": "Background sync with priority queue", "bandwidth": "Adaptive based on connectivity" } } }, "prefillFrom": null, "briefSection": "Infrastructure requirements", "text": "Do you need to support offline access to medical records in remote areas?", "ngoText": "Do you need to support offline access to medical records in remote areas?" }, { "id": "audit-compliance", "type": "select", "options": [ { "label": "Basic access logs (who accessed what and when)", "value": "basic-logs" }, { "label": "HIPAA-compliant audit trail with protected data integrity", "value": "hipaa-audit" }, { "label": "GDPR-compliant with data processing agreements", "value": "gdpr-audit" }, { "label": "Real-time alert system for suspicious access patterns", "value": "realtime-alerts" }, { "label": "Tamper-proof permanent tamper-proof audit on digital ledger", "value": "blockchain-audit" } ], "propertyMapping": { "basic-logs": { "technologies": [ "Audit logging service", "Log storage" ], "technologyProperties": { "logContent": "UserID, timestamp, action, record ID", "retention": "Minimum 1 year", "queryCapability": "Search by user, date, action" } }, "hipaa-audit": { "technologies": [ "HIPAA-compliant audit system", "Access control list auditor" ], "technologyProperties": { "logProtection": "Encrypted and access-controlled logs", "nonRepudiation": "Digital signatures on audit records", "externalAudit": "Third-party audit capability" } }, "gdpr-audit": { "technologies": [ "GDPR data processing audit system", "Right-to-be-forgotten tracker" ], "technologyProperties": { "consentTracking": "Linked to consent records", "dataLineage": "Processing history per data element", "rightsManagement": "Automated right-to-access requests" } }, "realtime-alerts": { "technologies": [ "Real-time anomaly detection engine", "Alert notification service" ], "technologyProperties": { "detectionMethod": "Machine learning based", "alertThreshold": "Configurable risk scores", "responseWorkflow": "Automated incident response" } }, "blockchain-audit": { "technologies": [ "Blockchain audit ledger", "Smart contract event logging" ], "technologyProperties": { "immutability": "Cryptographic proof of non-tampering", "transparency": "Verifiable by auditors", "retention": "Permanent blockchain record" } } }, "prefillFrom": null, "briefSection": "Reporting and audit", "text": "What audit and compliance logging do you need for regulatory requirements?", "ngoText": "What audit and compliance logging do you need for regulatory requirements?" }, { "id": "privacy-approach", "type": "select", "options": [ { "label": "End-to-end encryption with role-based decryption", "value": "e2e-role-based" }, { "label": "Zero-knowledge proofs (verify without revealing data)", "value": "zkp" }, { "label": "privacy-preserving computation (data stays encrypted during analysis)", "value": "homomorphic" }, { "label": "Standard encryption with access control lists", "value": "standard-acl" } ], "propertyMapping": { "e2e-role-based": { "technologies": [ "End-to-end encryption layer", "Role-based decryption service", "Key management system" ], "technologyProperties": { "privacyMethod": "End-to-end encryption", "dataVisibility": "Only authorised roles can decrypt", "complianceLevel": "GDPR/HIPAA compatible" } }, "zkp": { "technologies": [ "Zero-knowledge proof privacy layer", "ZKP verification circuit", "Privacy-preserving query engine" ], "technologyProperties": { "privacyMethod": "Zero-knowledge proofs", "dataVisibility": "Verification without data exposure", "complianceLevel": "Maximum privacy \u2014 data never revealed" } }, "homomorphic": { "technologies": [ "Homomorphic encryption layer", "Encrypted computation engine", "Secure aggregation service" ], "technologyProperties": { "privacyMethod": "Homomorphic encryption", "dataVisibility": "Computations on encrypted data", "complianceLevel": "Maximum privacy for analytics" } }, "standard-acl": { "technologies": [ "Standard encryption privacy layer", "Access control list manager", "Encryption key rotation service" ], "technologyProperties": { "privacyMethod": "AES-256 encryption with ACLs", "dataVisibility": "Controlled by access control lists", "complianceLevel": "Standard data protection" } } }, "prefillFrom": null, "briefSection": "Data privacy", "text": "What level of privacy protection is needed for sensitive data?", "ngoText": "What level of privacy protection is needed for sensitive data?" }, { "id": "beneficiary-choice", "label": "How will beneficiaries exercise choice in how they receive and use this service?", "type": "select", "briefSection": "Consent management", "options": [ { "label": "Beneficiaries choose between delivery methods (cash, voucher, mobile money, direct)", "value": "delivery-choice" }, { "label": "Beneficiaries choose preferred merchants or service points", "value": "merchant-choice" }, { "label": "Beneficiaries control their own data sharing preferences", "value": "data-choice" }, { "label": "Multiple choice dimensions (delivery + merchant + data)", "value": "full-choice" }, { "label": "Limited choice: programme constraints determine delivery", "value": "limited" } ], "propertyMapping": { "delivery-choice": { "technologies": [], "technologyProperties": { "beneficiaryChoice": "Delivery method choice", "dignityDesign": "Beneficiaries select preferred receipt method" } }, "merchant-choice": { "technologies": [], "technologyProperties": { "beneficiaryChoice": "Merchant/service point choice", "dignityDesign": "Beneficiaries select where to redeem" } }, "data-choice": { "technologies": [], "technologyProperties": { "beneficiaryChoice": "Data sharing choice", "dignityDesign": "Beneficiaries control personal data sharing" } }, "full-choice": { "technologies": [], "technologyProperties": { "beneficiaryChoice": "Multi-dimensional choice", "dignityDesign": "Full beneficiary agency across delivery, merchant, and data" } }, "limited": { "technologies": [], "technologyProperties": { "beneficiaryChoice": "Limited by programme design", "dignityDesign": "Programme constraints; beneficiary informed of reasons" } } }, "text": "How will beneficiaries exercise choice in how they receive and use this service?" } ], "complexityFactors": { "relationships": 3, "operationalChange": 3, "dataCompliance": 5 }, "securityTier": "C", "suggestedCriteria": [ { "id": "SC-C039-PRIVACY", "name": "Medical Data Privacy Strength", "description": "The provider can prove health data was never revealed to unauthorised parties. Evaluate cryptographic privacy guarantees for sensitive medical information.", "weight": 0.3, "ratingGuide": { "5": "Zero-knowledge proofs verify medical facts (e.g. vaccination status, clearance) without revealing underlying health data. Mathematically provable non-disclosure.", "4": "Multi-party computation splits medical records across parties \u2014 no single entity sees complete health data. Requires multi-party availability.", "3": "Trusted execution environment processes health data in hardware-isolated enclaves. Strong but relies on hardware trust assumptions.", "2": "Standard encryption at rest and in transit with role-based access controls. No mathematical proof that data wasn't accessed.", "1": "Basic access controls only. Medical data accessible to system administrators or via court orders with no cryptographic protection." } }, { "id": "SC-C039-SELECTIVE", "name": "Selective Disclosure Capability", "description": "Patients or providers can share specific medical facts without exposing the full record. Essential for cross-provider referrals and insurance verification.", "weight": 0.25, "ratingGuide": { "5": "Granular selective disclosure \u2014 share individual data points (e.g. 'vaccinated against measles') without revealing any other medical history. Patient controls each disclosure.", "4": "Category-level disclosure \u2014 share groups of related data (e.g. 'immunisation history') while keeping other categories private.", "3": "Record-level disclosure \u2014 share entire records selectively but cannot break down individual fields within a record.", "2": "Binary disclosure \u2014 either full access to a record or no access. No partial sharing capability.", "1": "No selective disclosure. Sharing any medical data requires exposing the complete medical file." } }, { "id": "SC-C039-INTEROP", "name": "Health System Interoperability", "description": "The solution integrates with existing health information systems (national health information systems, electronic medical records, HL7 FHIR). Critical for adoption in humanitarian health programmes.", "weight": 0.2, "ratingGuide": { "5": "Native HL7 FHIR support plus proven integrations with national health information systems and open-source electronic medical record systems. Tested in humanitarian health contexts.", "4": "HL7 FHIR compliant with API connectors for major health information systems. Some humanitarian deployments.", "3": "Standard health data formats supported (HL7, CDA) but requires custom integration work for humanitarian systems.", "2": "Generic API available but no native health data standards support. Significant integration effort required.", "1": "Proprietary data format only. No health system interoperability without complete custom development." } }, { "id": "SC-C039-CONSENT", "name": "Patient Consent Integration", "description": "This measures how well the solution handles patient consent for data access, withdrawal of consent, and consent audit trails. Medical data requires explicit informed consent.", "weight": 0.15, "ratingGuide": { "5": "Built-in consent management with granular per-record consent, time-limited access, automatic revocation, and full consent audit trail.", "4": "Consent management integrated \u2014 supports grant/revoke per provider with audit logging. Manual time-limit configuration.", "3": "Basic consent recording \u2014 captures consent events but limited revocation automation. Audit trail present.", "2": "Consent tracked externally \u2014 system supports access control but consent management is a separate process.", "1": "No consent mechanism. Access control is purely administrative with no patient-facing consent features." } }, { "id": "SC-C039-FIELD", "name": "Field Clinic Viability", "description": "The solution can operate in remote field clinics with unreliable power and connectivity. Medical records must be accessible where care is delivered.", "weight": 0.1, "ratingGuide": { "5": "Fully offline-capable. Local verification and record access work without connectivity. Syncs when connection available.", "4": "Intermittent connectivity sufficient. Caches recent records locally and batch-syncs. Tolerates multi-day outages.", "3": "Requires periodic connectivity (daily) but handles temporary outages. Read access works offline for cached records.", "2": "Needs reliable internet for most operations. Limited offline read-only mode.", "1": "Requires constant connectivity. No offline capability \u2014 unusable in remote field settings." } } ], "procurement": { "marketMaturity": "emerging", "primaryMode": "tender", "alternativeModes": [ "integrator-led" ], "reasoning": "FHIR-based EHR products mature for clinical contexts; humanitarian profile may need integration.", "exampleProductCategories": [ "ehr-platform", "fhir-clinical-records" ], "partnerChannels": [], "lastReviewed": "2026-05-01" } }, { "id": "UC-C-040", "name": "Vaccination history and immunisation records", "category": "C", "subcategory": "Health Data Management", "description": "Keep vaccination records that follow a person between clinics and countries, and that health workers can confirm are genuine without seeing the whole medical file.", "bCriteria": [ "B3", "B6" ], "requiredComponents": [ { "component": "data-layer", "description": "Distributed immunisation records" }, { "component": "encryption-privacy", "description": "Encrypted vaccination data" }, { "component": "access-control", "description": "Access controls for health records" }, { "component": "credential-issuance", "description": "Verifiable vaccination credentials" } ], "conditionalComponents": [ { "component": "consent-management", "condition": "For vaccination record access", "linksTo": "UC-B-037" }, { "component": "identity-verification", "condition": "For patient identity verification" }, { "component": "interoperability-layer", "condition": "If linking with national health systems" } ], "crossCategoryDependencies": [ "UC-B-024 for beneficiary identity" ], "p2TriggerConditions": { "description": "Activated when P2 shows immunisation programmes + portable records need + multi-clinic access", "rangeSignals": [ "immunisationCampaign >= true", "portabilityNeeded >= true", "multiClinicAccess >= true" ] }, "contextFieldsTemplate": [ { "field": "beneficiaries", "source": "P2 immunisation scale", "description": "Number of vaccinated" }, { "field": "vaccinationTypes", "source": "P2 health programmes", "description": "Vaccines administered" }, { "field": "clinics", "source": "P0 health sites", "description": "Vaccination facilities" }, { "field": "dataUse", "source": "P2 monitoring needs", "description": "Uses for vaccination data" } ], "implementationComplexity": "medium-high", "examples": { "note": "WHO vaccination records, digital health credentials", "references": [ { "name": "WHO DDCC: Digital Documentation of COVID-19 Certificates", "url": "https://www.who.int/initiatives/ddcc", "solved": "International standards for verifiable vaccination credentials with offline QR codes and privacy-preserving data models" }, { "name": "The EU Digital COVID Certificate", "url": "https://ec.europa.eu/info/live-work-travel-eu/coronavirus-response/digital-covid-certificate_en", "solved": "EU-wide interoperable vaccination certificate system with cross-border recognition and cryptographic verification" }, { "name": "Verifiable Credentials Implementation Consortium (VC-IMPL)", "url": "https://www.w3.org/groups/cg/veriable-credentials/", "solved": "W3C standards and implementations for portable, verifiable vaccination credentials" } ] }, "solutionQuestions": [ { "id": "provider-access-model", "type": "select", "options": [ { "label": "Direct query to patient's vaccination wallet", "value": "wallet-direct" }, { "label": "Centralized registry lookup by provider", "value": "centralized-registry" }, { "label": "Patient-mediated sharing (patient grants one-time access)", "value": "patient-mediated" }, { "label": "Provider network with service-to-service APIs", "value": "service-api" }, { "label": "Offline credential sharing (credential shown to provider)", "value": "offline-sharing" } ], "propertyMapping": { "wallet-direct": { "technologies": [ "Personal vaccination wallet", "Direct provider API query" ], "technologyProperties": { "queryProtocol": "REST API over TLS", "authentication": "OAuth 2.0 or mutual TLS", "dataReturned": "Vaccination records filtered by patient consent" } }, "centralized-registry": { "technologies": [ "National immunisation registry", "Provider lookup API" ], "technologyProperties": { "dataHub": "Government-operated registry", "providerAuth": "Licensed provider credentials", "queryOptimization": "Real-time lookup with caching" } }, "patient-mediated": { "technologies": [ "Consent management platform", "One-time access token generator" ], "technologyProperties": { "tokenGeneration": "Time-limited, single-use access tokens", "revokeCapability": "Patient can cancel at any time", "auditTrail": "Logged who accessed when" } }, "service-api": { "technologies": [ "Healthcare provider network gateway", "Federated identity management" ], "technologyProperties": { "networkType": "Closed provider network", "synchronization": "Periodic or event-driven sync", "networkGovernance": "Shared governance rules" } }, "offline-sharing": { "technologies": [ "Portable credential format", "Offline verification mechanism" ], "technologyProperties": { "portability": "QR code or document with embedded signature", "verification": "Provider verifies signature locally", "networkDependency": "Zero network requirement" } } }, "prefillFrom": null, "briefSection": "Access control", "text": "What system would you need for provider access to vaccination records?", "ngoText": "What system would you need for provider access to vaccination records?" }, { "id": "cross-border-portability", "type": "select", "options": [ { "label": "Regional (e.g., East Africa Community travel)", "value": "regional-travel" }, { "label": "International (visa, residency, work permits)", "value": "international-travel" }, { "label": "Refugee or displaced persons context", "value": "refugee-context" }, { "label": "No cross-border requirement; domestic only", "value": "domestic-only" }, { "label": "Medical tourism (treatment in multiple countries)", "value": "medical-tourism" } ], "propertyMapping": { "regional-travel": { "technologies": [ "Regional immunisation harmonization platform", "Multi-country verifiable credential" ], "technologyProperties": { "jurisdictions": "Regional economic community standards", "recognition": "Mutual recognition agreement", "dataStandard": "Harmonized regional vaccination codes" } }, "international-travel": { "technologies": [ "WHO-endorsed credential format", "International SOS integration" ], "technologyProperties": { "standard": "WHO-aligned vaccination data model", "portability": "Widely recognized credential format", "linguisticSupport": "Multi-language credential" } }, "refugee-context": { "technologies": [ "Portable verifiable credential", "UNHCR interoperability standards" ], "technologyProperties": { "resilience": "Works without connectivity", "privacy": "Minimal identifier exposure", "recognition": "Humanitarian-focused acceptance" } }, "domestic-only": { "technologies": [ "Domestic immunisation registry", "National standard format" ], "technologyProperties": { "standard": "Country-specific vaccination coding", "scope": "Single jurisdiction", "compliance": "National regulatory requirements" } }, "medical-tourism": { "technologies": [ "Multi-country credential converter", "International healthcare network" ], "technologyProperties": { "standardMapping": "Country-to-country vaccine mapping", "providerNetworks": "Private hospital chains", "dataFormat": "Multiple credential formats supported" } } }, "prefillFrom": null, "briefSection": "Interoperability", "text": "Do you need to support cross-border sharing of vaccination records, and what jurisdictions are involved?", "ngoText": "Do you need to support cross-border sharing of vaccination records, and what jurisdictions are involved?" }, { "id": "record-verification", "type": "select", "options": [ { "label": "Checking signatures or stamps from the issuing clinic", "value": "checking-signatures-or-stamps-from-the-i" }, { "label": "Cross-referencing against a central health registry", "value": "cross-referencing-against-a-central-heal" }, { "label": "Third-party review or notarisation", "value": "third-party-review-or-notarisation" }, { "label": "Multiple organisations confirm the same record", "value": "multiple-organisations-confirm-the-same-" }, { "label": "No verification process currently, records are trusted at face value", "value": "no-verification-process-currently-record" } ], "propertyMapping": { "issuer-signature": { "technologies": [ "Digital signature verifier", "Public key registry" ], "technologyProperties": { "signatureAlgorithm": "ECDSA-SHA256 or EdDSA", "keyRegistry": "Healthcare authority public keys", "verificationTime": "Milliseconds" } }, "blockchain-anchor": { "technologies": [ "Blockchain anchoring service", "Merkle proof validator" ], "technologyProperties": { "chainType": "Public blockchain", "dataOnChain": "Hash of credential only", "verificationProof": "Merkle proof against block root" } }, "cert-revocation": { "technologies": [ "OCSP responder", "Certificate Revocation List (CRL)" ], "technologyProperties": { "checkMethod": "Online (OCSP) or offline (CRL)", "responseTime": "Real-time for OCSP", "coverage": "Detects revoked issuer certificates" } }, "notarization": { "technologies": [ "Licensed notary service", "Notary registry" ], "technologyProperties": { "authority": "Government-licensed notary", "attestation": "Notary signature on vaccination record", "trustLevel": "High in legal contexts" } }, "multi-signature": { "technologies": [ "Multi-signature contract", "Multiple issuer coordination" ], "technologyProperties": { "signatoryCount": "2-3 healthcare authorities", "requiredSignatures": "All or M-of-N threshold", "consensus": "Distributed trust model" } } }, "prefillFrom": null, "briefSection": "Data integrity", "text": "What verification process do you currently use or require for vaccination records?", "ngoText": "What verification process do you currently use or require for vaccination records?", "question": "How do you currently verify that vaccination records are authentic and unaltered?" }, { "id": "consent-withdrawal", "type": "select", "options": [ { "label": "Immediate withdrawal with retroactive effect", "value": "immediate-retroactive" }, { "label": "Immediate withdrawal, but past accesses remain valid", "value": "immediate-prospective" }, { "label": "Withdrawal with notice period (e.g., 30 days)", "value": "notice-period" }, { "label": "No withdrawal once consent given", "value": "no-withdrawal" }, { "label": "Withdrawal by credential expiry only", "value": "expiry-only" } ], "propertyMapping": { "immediate-retroactive": { "technologies": [ "Consent revocation smart contract", "Retroactive access revoker" ], "technologyProperties": { "revokeSpeed": "Immediate", "retroactiveEffect": "Invalidates all past accesses", "dataDisposal": "Accessed copies must be deleted", "compliance": "GDPR right to be forgotten" } }, "immediate-prospective": { "technologies": [ "Consent revocation engine", "Access history logger" ], "technologyProperties": { "revokeSpeed": "Immediate", "scope": "Future accesses only", "pastAccessLog": "Immutable record of past access", "compromise": "Balances privacy and practicality" } }, "notice-period": { "technologies": [ "Scheduled consent revocation", "Notification service" ], "technologyProperties": { "noticePeriod": "30 days (configurable)", "delayedEffect": "Withdrawal takes effect after notice", "stakeholderNotification": "All parties notified of revocation" } }, "no-withdrawal": { "technologies": [ "Irrevocable consent contract", "One-time consent" ], "technologyProperties": { "consentType": "Perpetual or time-limited", "revocation": "Not supported", "useCase": "Government reporting, historical record" } }, "expiry-only": { "technologies": [ "Time-limited credential system", "Automatic credential expiry" ], "technologyProperties": { "expiryMechanism": "Embedded expiry date in credential", "revokeBeforeExpiry": "Not possible", "credentialRenewal": "Patient must re-consent" } } }, "prefillFrom": null, "briefSection": "Consent management", "text": "What is your current approach to consent withdrawal for vaccination record sharing?", "ngoText": "What is your current approach to consent withdrawal for vaccination record sharing?" }, { "id": "multi-clinic-sync", "type": "select", "options": [ { "label": "Centralized registry with periodic sync", "value": "centralized-sync" }, { "label": "Real-time push updates to all clinics", "value": "realtime-push" }, { "label": "Patient-mediated sync (patient downloads and shares)", "value": "patient-mediated-sync" }, { "label": "Federated query (each clinic queries directly)", "value": "federated-query" }, { "label": "No sync; each clinic keeps separate records", "value": "no-sync" } ], "propertyMapping": { "centralized-sync": { "technologies": [ "Central immunisation registry", "Batch sync service" ], "technologyProperties": { "syncFrequency": "Daily or hourly batch", "dataConsistency": "Eventual consistency", "conflictResolution": "Last-write-wins or manual review" } }, "realtime-push": { "technologies": [ "Event-driven sync platform", "Pub/sub message broker" ], "technologyProperties": { "messaging": "Event stream (message queue)", "latency": "Sub-second propagation", "reliability": "At-least-once delivery" } }, "patient-mediated-sync": { "technologies": [ "Patient data export tool", "Universal portable file format" ], "technologyProperties": { "format": "FHIR bundle or encrypted JSON", "portability": "Patient controls sharing", "recipient": "Any clinic patient chooses" } }, "federated-query": { "technologies": [ "Federated query engine", "Cross-clinic lookup protocol" ], "technologyProperties": { "queryPattern": "Query-response between clinics", "consistency": "Real-time but dependent on clinic availability", "privacy": "Minimal data exposure per query" } }, "no-sync": { "technologies": [ "Local clinic database only", "Paper-based record sharing" ], "technologyProperties": { "scope": "Single clinic only", "dataOwnership": "Clinic-owned records", "patientResponsibility": "Patient reports history" } } }, "prefillFrom": null, "briefSection": "Interoperability", "text": "How do you currently synchronize vaccination records across your clinics?", "ngoText": "How do you currently synchronize vaccination records across your clinics?" }, { "id": "offline-verification", "type": "select", "options": [ { "label": "Fully offline verification (secure digital check only)", "value": "fully-offline" }, { "label": "Offline with cached revocation list", "value": "offline-cached" }, { "label": "Online verification required", "value": "online-required" }, { "label": "Hybrid: offline for valid checks, online for revocation", "value": "hybrid-offline" }, { "label": "Not applicable; online always available", "value": "not-applicable" } ], "propertyMapping": { "fully-offline": { "technologies": [ "Self-contained credential format", "Embedded signature verification" ], "technologyProperties": { "credentialFormat": "Self-signed or issuer-signed", "verificationMethod": "Public key included in credential", "trustAssumption": "Issuer key is known to verifier" } }, "offline-cached": { "technologies": [ "Cached revocation list", "Offline revocation checker" ], "technologyProperties": { "cacheType": "CRL or revocation bitmap", "updateFrequency": "Periodic download when online", "staleness": "Acceptable 24-48 hours" } }, "online-required": { "technologies": [ "Online OCSP responder", "Certificate validation service" ], "technologyProperties": { "validation": "Real-time certificate check", "connectivity": "Internet required", "fallback": "Rejection if offline" } }, "hybrid-offline": { "technologies": [ "Signature verification module", "Cached revocation list" ], "technologyProperties": { "offlineCheck": "Signature verification without network", "revocationCheck": "Online only if cached list unavailable", "userExperience": "Graceful degradation" } }, "not-applicable": { "technologies": [ "Online-only validation", "Real-time server check" ], "technologyProperties": { "connectivity": "Always available in context", "validation": "Complete server-side verification" } } }, "prefillFrom": null, "briefSection": "Infrastructure requirements", "text": "Do you need vaccination credentials to be verifiable in offline settings?", "ngoText": "Do you need vaccination credentials to be verifiable in offline settings?" }, { "id": "privacy-approach", "type": "select", "options": [ { "label": "End-to-end encryption with role-based decryption", "value": "e2e-role-based" }, { "label": "Zero-knowledge proofs (verify without revealing data)", "value": "zkp" }, { "label": "privacy-preserving computation (data stays encrypted during analysis)", "value": "homomorphic" }, { "label": "Standard encryption with access control lists", "value": "standard-acl" } ], "propertyMapping": { "e2e-role-based": { "technologies": [ "End-to-end encryption layer", "Role-based decryption service", "Key management system" ], "technologyProperties": { "privacyMethod": "End-to-end encryption", "dataVisibility": "Only authorised roles can decrypt", "complianceLevel": "GDPR/HIPAA compatible" } }, "zkp": { "technologies": [ "Zero-knowledge proof privacy layer", "ZKP verification circuit", "Privacy-preserving query engine" ], "technologyProperties": { "privacyMethod": "Zero-knowledge proofs", "dataVisibility": "Verification without data exposure", "complianceLevel": "Maximum privacy \u2014 data never revealed" } }, "homomorphic": { "technologies": [ "Homomorphic encryption layer", "Encrypted computation engine", "Secure aggregation service" ], "technologyProperties": { "privacyMethod": "Homomorphic encryption", "dataVisibility": "Computations on encrypted data", "complianceLevel": "Maximum privacy for analytics" } }, "standard-acl": { "technologies": [ "Standard encryption privacy layer", "Access control list manager", "Encryption key rotation service" ], "technologyProperties": { "privacyMethod": "AES-256 encryption with ACLs", "dataVisibility": "Controlled by access control lists", "complianceLevel": "Standard data protection" } } }, "prefillFrom": null, "briefSection": "Data privacy", "text": "What level of privacy protection is needed for sensitive data?", "ngoText": "What level of privacy protection is needed for sensitive data?" }, { "id": "beneficiary-choice", "label": "How will beneficiaries exercise choice in how they receive and use this service?", "type": "select", "briefSection": "Consent management", "options": [ { "label": "Beneficiaries choose between delivery methods (cash, voucher, mobile money, direct)", "value": "delivery-choice" }, { "label": "Beneficiaries choose preferred merchants or service points", "value": "merchant-choice" }, { "label": "Beneficiaries control their own data sharing preferences", "value": "data-choice" }, { "label": "Multiple choice dimensions (delivery + merchant + data)", "value": "full-choice" }, { "label": "Limited choice: programme constraints determine delivery", "value": "limited" } ], "propertyMapping": { "delivery-choice": { "technologies": [], "technologyProperties": { "beneficiaryChoice": "Delivery method choice", "dignityDesign": "Beneficiaries select preferred receipt method" } }, "merchant-choice": { "technologies": [], "technologyProperties": { "beneficiaryChoice": "Merchant/service point choice", "dignityDesign": "Beneficiaries select where to redeem" } }, "data-choice": { "technologies": [], "technologyProperties": { "beneficiaryChoice": "Data sharing choice", "dignityDesign": "Beneficiaries control personal data sharing" } }, "full-choice": { "technologies": [], "technologyProperties": { "beneficiaryChoice": "Multi-dimensional choice", "dignityDesign": "Full beneficiary agency across delivery, merchant, and data" } }, "limited": { "technologies": [], "technologyProperties": { "beneficiaryChoice": "Limited by programme design", "dignityDesign": "Programme constraints; beneficiary informed of reasons" } } }, "text": "How will beneficiaries exercise choice in how they receive and use this service?" } ], "complexityFactors": { "relationships": 3, "operationalChange": 3, "dataCompliance": 4 }, "suggestedCriteria": [ { "id": "SC-C040-CRED", "name": "Verifiable Credential Issuance", "description": "Can the solution issue portable, cryptographically verifiable vaccination credentials that are recognised across borders and systems?", "weight": 0.3, "ratingGuide": { "5": "W3C Verifiable Credentials standard with cross-border recognition. Proven in WHO SMART Health Cards or similar international frameworks.", "4": "Verifiable credentials issued with strong cryptographic proof. Recognised by multiple national health systems.", "3": "Digital certificates issued with tamper-proof verification but limited cross-border recognition.", "2": "Digital records with basic integrity checks but not in a portable credential format.", "1": "Paper-equivalent digital records with no cryptographic verification capability." } }, { "id": "SC-C040-INTEROP", "name": "National Health System Integration", "description": "How well does the solution integrate with national immunisation registries, national health information systems, and WHO reporting requirements?", "weight": 0.25, "ratingGuide": { "5": "Proven integration with national immunisation registries in multiple countries. National health information system connector and WHO reporting built in.", "4": "National health information system integration available. Connects to at least one national registry. WHO reporting supported via export.", "3": "Standard health data formats (HL7 FHIR) supported. Integration with national systems requires configuration.", "2": "Generic API but no pre-built health system connectors. Manual data export for reporting.", "1": "Standalone system with no interoperability. Manual data entry required for national reporting." } }, { "id": "SC-C040-SCALE", "name": "Mass Vaccination Campaign Support", "description": "Can the solution handle high-throughput registration during mass vaccination campaigns with hundreds of records per hour per site?", "weight": 0.2, "ratingGuide": { "5": "Designed for mass campaigns \u2014 handles 500+ registrations/hour/site. Batch processing, offline queuing, and rapid data entry interfaces.", "4": "Handles 200+ registrations/hour with efficient data entry. Supports batch upload and queue management.", "3": "Standard registration workflow \u2014 handles 50-100 registrations/hour. No specific mass campaign optimisations.", "2": "Individual registration only \u2014 each record requires multiple steps. Slow for campaign contexts.", "1": "Complex registration process unsuitable for field campaigns. Designed for clinical settings only." } }, { "id": "SC-C040-LIFECYCLE", "name": "Multi-dose Schedule Tracking", "description": "Does the solution track multi-dose vaccination schedules, send reminders, and flag overdue or missed doses across the full immunisation lifecycle?", "weight": 0.15, "ratingGuide": { "5": "Full lifecycle management \u2014 multi-dose schedules, automated reminders, catch-up schedules, and contraindication alerts. WHO EPI schedule built in.", "4": "Multi-dose tracking with reminders. Supports standard vaccination schedules. Manual contraindication checks.", "3": "Records doses and tracks schedule compliance. Basic overdue flagging but no automated reminders.", "2": "Records individual doses but no schedule intelligence. Manual tracking of multi-dose compliance.", "1": "Single-event recording only. No schedule awareness or dose-sequence tracking." } }, { "id": "SC-C040-PRIVACY", "name": "Beneficiary Privacy Safeguards", "description": "The solution protects beneficiary identity while enabling vaccination verification. Important when vaccinating undocumented or displaced populations.", "weight": 0.1, "ratingGuide": { "5": "Vaccination verified without revealing identity. Supports pseudonymous records for undocumented populations. No identity prerequisite.", "4": "Privacy-preserving verification available. Minimal identity data required. Supports anonymous or pseudonymous registration.", "3": "Standard data protection with encryption and access controls. Identity required but well-protected.", "2": "Basic data protection. Full identity required for registration. Standard security measures.", "1": "Identity data stored in plaintext or weakly protected. No special provisions for vulnerable populations." } } ], "procurement": { "marketMaturity": "emerging", "primaryMode": "tender", "alternativeModes": [ "off-the-shelf" ], "reasoning": "Vaccination record platforms grew through pandemic response.", "exampleProductCategories": [ "immunisation-records-platform", "digital-health-passport" ], "partnerChannels": [], "lastReviewed": "2026-05-01" } }, { "id": "UC-C-041", "name": "Mental health and psychosocial support records", "category": "C", "subcategory": "Health Data Management", "description": "Keep counselling and support records private, with the person deciding which providers see which sessions, so fear of exposure does not stop them seeking help.", "bCriteria": [ "B3", "B6" ], "requiredComponents": [ { "component": "data-layer", "description": "Confidential MHPSS records storage" }, { "component": "encryption-privacy", "description": "Encrypted MHPSS data" }, { "component": "access-control", "description": "Strict access controls" }, { "component": "consent-management", "description": "Explicit consent for MHPSS data" } ], "conditionalComponents": [ { "component": "privacy-tech", "condition": "For privacy-preserving MHPSS verification" }, { "component": "anonymisation-tools", "condition": "If data aggregation needed" } ], "crossCategoryDependencies": [ "UC-C-045 for consent audit trails" ], "p2TriggerConditions": { "description": "Activated when P2 shows MHPSS services + privacy concerns + referral coordination", "rangeSignals": [ "mhpssServices >= true", "privacyConcerns >= critical", "referralNeedsFull" ] }, "contextFieldsTemplate": [ { "field": "beneficiaries", "source": "P2 MHPSS scale", "description": "Number of clients" }, { "field": "providers", "source": "P0 MHPSS staff", "description": "MHPSS providers" }, { "field": "riskLevel", "source": "P0 context", "description": "Operational security level" }, { "field": "privacyStandards", "source": "P0 Q19-21", "description": "Required privacy standards" } ], "implementationComplexity": "high", "examples": { "note": "IASC MHPSS standards, trauma-informed care", "references": [ { "name": "UN Guidelines on Mental Health and Psychosocial Support in Emergencies", "url": "https://www.who.int/publications/i/item/9789240026759", "solved": "International standards for confidential MHPSS data collection and client protection in crisis contexts" }, { "name": "OpenMRS (Open Medical Record System) - Mental Health Module", "url": "https://openmrs.org/", "solved": "Open-source health information system with privacy-first design and role-based access control for sensitive records" }, { "name": "Verifiable Credentials in Health - EU eHealth Network", "url": "https://ec.europa.eu/health/ehealth_en", "solved": "Digital credentialing with privacy-preserving selective disclosure for health information sharing" } ] }, "solutionQuestions": [ { "id": "mhpss-data-sensitivity", "type": "select", "options": [ { "label": "Non-identifying (e.g., symptom checklists, general counseling notes)", "value": "non-identifying" }, { "label": "Client-identifying but without detailed diagnoses", "value": "client-identifying" }, { "label": "Detailed diagnoses and treatment history", "value": "detailed-clinical" }, { "label": "Trauma narratives and crisis information", "value": "trauma-crisis" }, { "label": "Suicide risk assessments and safety plans", "value": "suicide-risk" } ], "propertyMapping": { "non-identifying": { "technologies": [ "Basic encryption at rest", "TLS in transit" ], "technologyProperties": { "encryption": "AES-256", "keyLocation": "Server-side HSM", "accessControl": "Role-based" } }, "client-identifying": { "technologies": [ "End-to-end encryption", "Key management service" ], "technologyProperties": { "encryption": "Client-side AES-256", "keyExchange": "ECDH", "keyRecovery": "Provider backup key escrow" } }, "detailed-clinical": { "technologies": [ "Enhanced end-to-end encryption", "Zero-knowledge proof layer" ], "technologyProperties": { "encryption": "AES-256 with authenticated encryption", "proofSystem": "zk-SNARKs for sensitive queries", "auditLogging": "Immutable access log" } }, "trauma-crisis": { "technologies": [ "Maximum security end-to-end encryption", "Hardware security module integration" ], "technologyProperties": { "encryption": "AES-256-GCM with additional AEAD", "keyStorage": "Client-side cold storage option", "dataMinimization": "Encrypt specific high-sensitivity fields" } }, "suicide-risk": { "technologies": [ "Crisis-grade encryption", "Emergency override with immediate audit" ], "technologyProperties": { "encryption": "Maximum strength encryption", "accessControl": "Strict permission with real-time alerting", "emergencyBreak": "Break-glass access logged immediately" } } }, "prefillFrom": null, "briefSection": "Privacy and encryption", "text": "What is the highest sensitivity level of MHPSS data you collect?", "ngoText": "What is the highest sensitivity level of MHPSS data you collect?" }, { "id": "provider-types", "type": "select", "options": [ { "label": "Licensed mental health professionals only (psychologists, psychiatrists)", "value": "licensed-mh" }, { "label": "Broader team (counselors, social workers, case managers)", "value": "broader-team" }, { "label": "Medical providers with consent (nurses, doctors for holistic care)", "value": "medical-integration" }, { "label": "Multi-sector partners (protection, legal services)", "value": "multisector" }, { "label": "Para-professionals and community health workers (with limited access)", "value": "para-professionals" } ], "propertyMapping": { "licensed-mh": { "technologies": [ "Credential verification service", "Strict role-based access control" ], "technologyProperties": { "credentialVerification": "License verification with regulatory body", "accessLevel": "Full record access", "auditLevel": "Detailed per-access logging" } }, "broader-team": { "technologies": [ "Differentiated role-based access control", "Credential hierarchy system" ], "technologyProperties": { "roles": "Multiple privilege levels per role", "scopeControl": "Different roles see different field subsets", "teamCoordination": "Shared patient care records" } }, "medical-integration": { "technologies": [ "Federated access control", "Consent-based record sharing" ], "technologyProperties": { "consentModel": "Per-provider access consent", "recordSubsets": "Medical providers see summary only", "dataMinimization": "Only necessary medical context" } }, "multisector": { "technologies": [ "Multi-sector access framework", "Purpose-based access control" ], "technologyProperties": { "purposes": "Clinical, legal, protection, research", "purposeVerification": "Service provider attestation", "dataMapping": "Different sector views of same record" } }, "para-professionals": { "technologies": [ "Limited-scope access interface", "Supervised access with monitoring" ], "technologyProperties": { "accessScope": "Predefined field subset only", "supervision": "Supervisor approval for sensitive access", "trainingVerification": "Certified training requirement" } } }, "prefillFrom": null, "briefSection": "Access control", "text": "What types of providers need access to MHPSS records?", "ngoText": "What types of providers need access to MHPSS records?" }, { "id": "anonymization-reporting", "type": "select", "options": [ { "label": "Aggregate statistics only (no individual records)", "value": "aggregate-only" }, { "label": "De-identified but linkable (pseudonymized)", "value": "pseudonymized" }, { "label": "Fully anonymized (irreversible removal of identifiers)", "value": "fully-anonymous" }, { "label": "Differential privacy (statistical noise added)", "value": "differential-privacy" }, { "label": "No reporting; data kept strictly confidential", "value": "no-reporting" } ], "propertyMapping": { "aggregate-only": { "technologies": [ "Aggregate query engine", "Secure multi-party computation" ], "technologyProperties": { "queryType": "Pre-defined aggregate queries (count, sum, avg)", "minDataset": "Minimum 5-10 records per aggregate", "outputFormat": "Statistics only, no individual records" } }, "pseudonymized": { "technologies": [ "Pseudonymization engine", "Identifier mapping service" ], "technologyProperties": { "mapping": "Reversible one-way hash with separate key", "linkability": "Can be re-identified with master key", "auditControl": "Access to mapping locked down" } }, "fully-anonymous": { "technologies": [ "Irreversible anonymization", "Record suppression for uniqueness" ], "technologyProperties": { "anonymization": "Cryptographic hash, identifiers removed", "reversal": "Mathematically irreversible", "risk": "k-anonymity >= 5" } }, "differential-privacy": { "technologies": [ "Differential privacy engine", "Noise injection layer" ], "technologyProperties": { "noiseLevel": "Configurable epsilon parameter", "queryType": "Aggregate or targeted analysis", "privacyGuarantee": "Formal privacy bound" } }, "no-reporting": { "technologies": [ "No analytics infrastructure", "Access control prevents export" ], "technologyProperties": { "reporting": "Prohibited", "analysis": "None except clinical care", "dataUse": "Clinical care only" } } }, "prefillFrom": null, "briefSection": "Reporting and audit", "text": "What anonymization requirements do you have for GBV survivor records in your reporting?", "ngoText": "What anonymization requirements do you have for GBV survivor records in your reporting?" }, { "id": "explicit-consent-model", "type": "select", "options": [ { "label": "Explicit written consent at service start", "value": "written-consent" }, { "label": "Explicit verbal consent (recorded and documented)", "value": "verbal-consent" }, { "label": "Dynamic consent (re-consent at each session)", "value": "dynamic-consent" }, { "label": "Separate consent for different use cases (clinical vs. research)", "value": "use-based-consent" }, { "label": "Implied consent (consent as part of service enrollment)", "value": "implied-consent" } ], "propertyMapping": { "written-consent": { "technologies": [ "Consent form management system", "Digital signature capture" ], "technologyProperties": { "format": "Physical or digital document", "signing": "In-person or e-signature", "retention": "Scanned and stored securely" } }, "verbal-consent": { "technologies": [ "Audio consent recording", "Consent transcript system" ], "technologyProperties": { "recording": "Encrypted audio capture", "transcript": "AI-transcribed and reviewed", "witness": "Optional counselor witness" } }, "dynamic-consent": { "technologies": [ "Session-based consent platform", "Push notification consent requests" ], "technologyProperties": { "timing": "At start of each service interaction", "scope": "Session-specific consent", "revocation": "Can withdraw before session" } }, "use-based-consent": { "technologies": [ "Purpose-based consent system", "Granular consent management" ], "technologyProperties": { "purposes": "Separate consents for clinical, research, reporting", "withdrawal": "Independent per-purpose withdrawal", "defaultAsk": "Opt-in for non-essential uses" } }, "implied-consent": { "technologies": [ "Service enrollment consent", "Terms acceptance logging" ], "technologyProperties": { "legality": "May not be acceptable in some jurisdictions", "documentation": "Enrollment agreement with data notice", "riskMitigation": "Additional explicit notices for sensitive uses" } } }, "prefillFrom": null, "briefSection": "Consent management", "text": "What is your current consent process for GBV case management data?", "ngoText": "What is your current consent process for GBV case management data?" }, { "id": "crisis-protocols", "type": "select", "options": [ { "label": "Emergency break-glass access with immediate audit and client notification", "value": "break-glass-notify" }, { "label": "Break-glass access with post-hoc review and potential client notification", "value": "break-glass-review" }, { "label": "Limited emergency protocols (specific authorized providers only)", "value": "limited-emergency" }, { "label": "No emergency override; standard consent required always", "value": "no-override" }, { "label": "Client-specified emergency contacts with pre-authorized access", "value": "pre-authorized-emergency" } ], "propertyMapping": { "break-glass-notify": { "technologies": [ "Break-glass access contract", "Real-time client notification service" ], "technologyProperties": { "accessMode": "Temporarily unlock all access", "notification": "Immediate SMS/email to client", "logging": "Immutable log of break-glass use", "followUp": "Mandatory session with client after" } }, "break-glass-review": { "technologies": [ "Break-glass access with oversight", "Review queue system" ], "technologyProperties": { "accessMode": "Temporary elevated access", "review": "Clinical supervisor must review within 24h", "notification": "Client notified after access", "consequence": "Policy violation if unjustified" } }, "limited-emergency": { "technologies": [ "Emergency responder registry", "Limited-scope emergency access" ], "technologyProperties": { "authorizedRoles": "Crisis team, supervisor, emergency services", "scope": "Suicide risk assessment and safety plan only", "accessDuration": "24-48 hours" } }, "no-override": { "technologies": [ "Standard access control enforcement", "No exceptions mechanism" ], "technologyProperties": { "accessControl": "No break-glass capability", "consequence": "Must obtain consent or use legal process", "ethics": "Respects autonomy absolutely" } }, "pre-authorized-emergency": { "technologies": [ "Emergency contact registry", "Pre-delegated access tokens" ], "technologyProperties": { "contacts": "Client designates emergency contacts", "preAuth": "Pre-authorized, doesn't require active consent", "scope": "Client-defined data access scope", "revocation": "Client can update emergency contacts anytime" } } }, "prefillFrom": null, "briefSection": "Access control", "text": "What is your current crisis response protocol for GBV case data?", "ngoText": "What is your current crisis response protocol for GBV case data?" }, { "id": "data-retention-deletion", "type": "select", "options": [ { "label": "Minimum retention: delete after treatment ends", "value": "minimum-retention" }, { "label": "Standard retention: 5-7 years after last contact", "value": "standard-retention" }, { "label": "Extended retention: until client turns 18 (for minors)", "value": "extended-minors" }, { "label": "Permanent retention: archived for life", "value": "permanent-retention" }, { "label": "Client-controlled: client can request deletion anytime", "value": "client-controlled" } ], "propertyMapping": { "minimum-retention": { "technologies": [ "Automated record deletion service", "Retention policy engine" ], "technologyProperties": { "retentionPeriod": "Until discharge + 30 days", "deletion": "Cryptographic shredding", "backup": "Deletion from all backups", "useCase": "Crisis counseling" } }, "standard-retention": { "technologies": [ "Retention schedule system", "Scheduled deletion task" ], "technologyProperties": { "retentionPeriod": "5-7 years from last contact", "trigger": "Automatic deletion on date", "audit": "Log showing deletion executed", "default": "Most mental health practices" } }, "extended-minors": { "technologies": [ "Age-aware retention system", "Legal guardian notification" ], "technologyProperties": { "minorRetention": "Until age 18 + 5 years", "adultRetention": "5-7 years from last contact", "guardianNotification": "Notice before deletion" } }, "permanent-retention": { "technologies": [ "Long-term archive system", "Cold storage activation" ], "technologyProperties": { "storage": "Permanent archival", "encryption": "Enhanced encryption for archives", "access": "Limited to clinical care only" } }, "client-controlled": { "technologies": [ "Right-to-deletion interface", "Deletion request processing" ], "technologyProperties": { "requestMethod": "Client can request anytime", "compliance": "GDPR right to be forgotten", "immediacy": "Deletion within days" } } }, "prefillFrom": null, "briefSection": "Data integrity", "text": "What is your policy for retaining and deleting MHPSS records?", "ngoText": "What is your policy for retaining and deleting MHPSS records?" }, { "id": "multi-language-cultural", "type": "select", "options": [ { "label": "Records in client's primary language with translation service", "value": "multilingual" }, { "label": "Notes include cultural context and community-specific practices", "value": "cultural-context" }, { "label": "Community-designed data model reflecting local healing traditions", "value": "community-designed" }, { "label": "Interpreter notes and cross-cultural competency documentation", "value": "interpreter-docs" }, { "label": "Standard clinical model only; cultural factors noted informally", "value": "clinical-standard" } ], "propertyMapping": { "multilingual": { "technologies": [ "Multilingual data store", "Professional translation API" ], "technologyProperties": { "languages": "Client-selected primary language", "translation": "Professional mental health translators", "terminology": "Language-specific diagnostic terms" } }, "cultural-context": { "technologies": [ "Cultural metadata schema", "Context annotation interface" ], "technologyProperties": { "metadata": "Community, cultural background fields", "annotation": "Counselor adds cultural notes", "viewConfiguration": "Cultural factors highlighted in view" } }, "community-designed": { "technologies": [ "Community-developed data model", "Customizable field schema" ], "technologyProperties": { "design": "Co-designed with community", "terminology": "Community-approved terms", "flexibility": "Custom fields for cultural practices" } }, "interpreter-docs": { "technologies": [ "Interpreter note field", "Cross-cultural competency tracker" ], "technologyProperties": { "interpreterInfo": "Name, certification of interpreter", "notes": "Dedicated field for interpretation issues", "competencyTracking": "Counselor's cultural competency level" } }, "clinical-standard": { "technologies": [ "Standard clinical documentation", "Optional cultural note field" ], "technologyProperties": { "format": "DSM-5 or ICD-11 based", "culturalNote": "Free-text field for cultural factors", "standardization": "No special cultural structure" } } }, "prefillFrom": null, "briefSection": "Data architecture", "text": "What languages and cultural contexts do you need to support?", "ngoText": "What languages and cultural contexts do you need to support?" }, { "id": "interagency-safety", "type": "select", "options": [ { "label": "No sharing; strict confidentiality within single agency", "value": "no-sharing" }, { "label": "Minimal sharing: safety summary only, not detailed records", "value": "summary-sharing" }, { "label": "Conditional sharing: only with explicit client consent per instance", "value": "conditional-sharing" }, { "label": "Coordinated cross-agency query: other agencies query without full record access", "value": "federated-query" }, { "label": "De-identified sharing: aggregated, never individual records", "value": "deidentified-sharing" } ], "propertyMapping": { "no-sharing": { "technologies": [ "Strict access control", "No inter-agency API" ], "technologyProperties": { "accessScope": "Single organization only", "shareMethod": "Manual referral letter only", "dataSharing": "Prohibited" } }, "summary-sharing": { "technologies": [ "Clinical summary extractor", "Redaction engine" ], "technologyProperties": { "summaryFields": "Diagnosis, current treatment, risk level", "excludedFields": "Sensitive details, trauma narratives", "recipient": "Care coordinator agency" } }, "conditional-sharing": { "technologies": [ "Per-instance consent platform", "Consent verification on access" ], "technologyProperties": { "consentModel": "Just-in-time consent request", "scope": "Client specifies what can be shared", "duration": "One-time or time-limited" } }, "federated-query": { "technologies": [ "Federated query engine", "No full-record export" ], "technologyProperties": { "queryType": "Predicate queries (e.g., 'current risk level')", "dataReturn": "Query result only, not full record", "privacy": "Minimal information disclosure" } }, "deidentified-sharing": { "technologies": [ "De-identification engine", "Aggregate analysis platform" ], "technologyProperties": { "deIdentification": "Irreversible removal of identifiers", "aggregation": "Only aggregate statistics", "purpose": "Coordinated care planning aggregates" } } }, "prefillFrom": null, "briefSection": "Interoperability", "text": "What are your data sharing agreements with other agencies for GBV cases?", "ngoText": "What are your data sharing agreements with other agencies for GBV cases?" }, { "id": "audit-and-oversight", "type": "select", "options": [ { "label": "Client-visible audit log (client can see who accessed when)", "value": "client-visible-audit" }, { "label": "Supervisor review of all access (human oversight)", "value": "supervisor-review" }, { "label": "Real-time anomaly alerts (automatic detection of suspicious access)", "value": "anomaly-alerts" }, { "label": "Monthly audit reports shared with client", "value": "monthly-reports" }, { "label": "Permanent tamper-proof digital ledger audit trail", "value": "blockchain-audit" } ], "propertyMapping": { "client-visible-audit": { "technologies": [ "Client-facing audit log interface", "Notification service" ], "technologyProperties": { "visibility": "Client can view access log anytime", "detail": "Who, when, why (purpose)", "notification": "Optional push alerts on new access" } }, "supervisor-review": { "technologies": [ "Access review queue", "Supervisor dashboard" ], "technologyProperties": { "frequency": "Daily or weekly review", "approval": "Supervisor must approve access", "anomalyFlag": "Unusual access highlighted" } }, "anomaly-alerts": { "technologies": [ "Machine learning anomaly detector", "Alert service" ], "technologyProperties": { "detection": "Out-of-hours access, multiple accesses", "alertThreshold": "Configurable risk score", "responseAction": "Immediate notification and investigation" } }, "monthly-reports": { "technologies": [ "Audit report generator", "Email delivery service" ], "technologyProperties": { "frequency": "Monthly", "content": "All accesses, anomalies, compliance", "format": "Human-readable report to client" } }, "blockchain-audit": { "technologies": [ "Blockchain audit ledger", "Automated event logging" ], "technologyProperties": { "immutability": "Tamper-proof record", "transparency": "Cryptographically verifiable", "verification": "Anyone can verify integrity" } } }, "prefillFrom": null, "briefSection": "Reporting and audit", "text": "What audit and oversight mechanisms should monitor MHPSS record access?", "ngoText": "What audit and oversight mechanisms should monitor MHPSS record access?" }, { "id": "beneficiary-choice", "label": "How will beneficiaries exercise choice in how they receive and use this service?", "type": "select", "briefSection": "Consent management", "options": [ { "label": "Beneficiaries choose between delivery methods (cash, voucher, mobile money, direct)", "value": "delivery-choice" }, { "label": "Beneficiaries choose preferred merchants or service points", "value": "merchant-choice" }, { "label": "Beneficiaries control their own data sharing preferences", "value": "data-choice" }, { "label": "Multiple choice dimensions (delivery + merchant + data)", "value": "full-choice" }, { "label": "Limited choice: programme constraints determine delivery", "value": "limited" } ], "propertyMapping": { "delivery-choice": { "technologies": [], "technologyProperties": { "beneficiaryChoice": "Delivery method choice", "dignityDesign": "Beneficiaries select preferred receipt method" } }, "merchant-choice": { "technologies": [], "technologyProperties": { "beneficiaryChoice": "Merchant/service point choice", "dignityDesign": "Beneficiaries select where to redeem" } }, "data-choice": { "technologies": [], "technologyProperties": { "beneficiaryChoice": "Data sharing choice", "dignityDesign": "Beneficiaries control personal data sharing" } }, "full-choice": { "technologies": [], "technologyProperties": { "beneficiaryChoice": "Multi-dimensional choice", "dignityDesign": "Full beneficiary agency across delivery, merchant, and data" } }, "limited": { "technologies": [], "technologyProperties": { "beneficiaryChoice": "Limited by programme design", "dignityDesign": "Programme constraints; beneficiary informed of reasons" } } }, "text": "How will beneficiaries exercise choice in how they receive and use this service?" } ], "complexityFactors": { "relationships": 2, "operationalChange": 2, "dataCompliance": 5 }, "securityTier": "C", "suggestedCriteria": [ { "id": "SC-C041-CONFID", "name": "Clinical Confidentiality Guarantees", "description": "The solution provides the highest level of data confidentiality appropriate for MHPSS records. These records carry severe stigma risk and potential danger to clients if exposed.", "weight": 0.35, "ratingGuide": { "5": "Zero-knowledge architecture \u2014 MHPSS data provably inaccessible to anyone except the treating clinician and client. No admin backdoor. Designed for contexts where data exposure could endanger lives.", "4": "End-to-end encryption with client-held keys. Provider cannot access data without client participation. Strong legal protections.", "3": "Strong encryption with provider-managed keys. Access limited to treating clinician. Admin access possible under strict protocols.", "2": "Standard role-based access control with encrypted storage. Multiple staff members can access records.", "1": "Basic access controls. Records accessible to organisation administrators. Insufficient for MHPSS sensitivity." } }, { "id": "SC-C041-STIGMA", "name": "Anti-stigma Data Architecture", "description": "The data model prevents inference of MHPSS engagement from metadata alone. In many contexts, the mere fact of receiving mental health support carries stigma.", "weight": 0.25, "ratingGuide": { "5": "MHPSS records are architecturally indistinguishable from other service records. No metadata leaks \u2014 record type, access patterns, and system identifiers reveal nothing about mental health engagement.", "4": "Minimal metadata exposure. Record types are generic. Access patterns obscured through padding or batching.", "3": "Record types are labelled but access is restricted. An authorised user could infer MHPSS engagement from record metadata.", "2": "Standard record categorisation. MHPSS records identifiable by type but access-controlled.", "1": "MHPSS records clearly labelled and categorised. Anyone with system access can identify who is receiving mental health support." } }, { "id": "SC-C041-TRAUMA", "name": "Trauma-informed Design", "description": "The solution is designed with trauma-informed principles. MHPSS clients may have complex relationships with technology, authority, and data collection.", "weight": 0.15, "ratingGuide": { "5": "Purpose-built for MHPSS with trauma-informed UX. Client controls all data. Easy withdrawal. Designed with input from MHPSS practitioners and lived-experience experts.", "4": "Configurable for MHPSS use. Supports client data ownership, easy opt-out, and minimises data collection. Practitioner-friendly.", "3": "General-purpose system adaptable for MHPSS. Standard consent and withdrawal processes. No trauma-specific design features.", "2": "System usable for MHPSS but not designed for it. Complex consent processes. Data minimisation requires workarounds.", "1": "System designed for general record-keeping. No consideration of trauma-informed principles or client agency." } }, { "id": "SC-C041-AGGREGATE", "name": "Safe Aggregation for Programme Reporting", "description": "Can MHPSS data be aggregated for programme reporting (donor requirements, IASC standards) without risking individual identification?", "weight": 0.15, "ratingGuide": { "5": "Differential privacy or secure aggregation produces programme statistics with formal privacy guarantees. Individual records provably protected.", "4": "Aggregation with k-anonymity protections. Small-group suppression prevents re-identification. Configurable thresholds.", "3": "Standard aggregation with basic anonymisation. Small cohort risks addressed through manual review.", "2": "Manual aggregation process. Anonymisation is a policy requirement rather than a technical guarantee.", "1": "No aggregation features. Individual-level data must be manually processed for reporting." } }, { "id": "SC-C041-CONTINUITY", "name": "Care Continuity Across Providers", "description": "Can MHPSS records be securely transferred when clients move between service providers (common in displacement contexts)?", "weight": 0.1, "ratingGuide": { "5": "Client-portable records with consent-based transfer. Works across different providers and systems. Client controls what transfers.", "4": "Secure record transfer between providers on the same platform. Client consent required. Selective sharing supported.", "3": "Export/import capability for record transfer. Requires both providers to use compatible systems.", "2": "Manual record transfer via encrypted export. Provider-initiated, not client-controlled.", "1": "No transfer mechanism. Records locked to the originating provider system." } } ], "procurement": { "marketMaturity": "nascent", "primaryMode": "integrator-led", "alternativeModes": [ "consortium" ], "reasoning": "Mental health records are sensitive; bespoke implementations common with sector-specific NGO partners.", "exampleProductCategories": [ "mhpss-records-platform", "clinical-records-protected" ], "partnerChannels": [], "lastReviewed": "2026-05-01" } }, { "id": "UC-C-042", "name": "Gender-based violence and protection case data", "category": "C", "subcategory": "Protection Data Management", "description": "Protect survivors' case files so that only the people a survivor approves can see them, with a trustworthy record of who looked and when.", "bCriteria": [ "B3", "B6" ], "requiredComponents": [ { "component": "data-layer", "description": "Confidential GBV case records" }, { "component": "encryption-privacy", "description": "End-to-end encrypted case data" }, { "component": "access-control", "description": "Role-based access control" }, { "component": "consent-management", "description": "Survivor consent for data access" } ], "conditionalComponents": [ { "component": "privacy-tech", "condition": "For privacy-preserving evidence" }, { "component": "anonymisation-tools", "condition": "For data aggregation and analysis" } ], "crossCategoryDependencies": [ "UC-C-045 for consent audit" ], "p2TriggerConditions": { "description": "Activated when P2 shows GBV focus + survivor protection + inter-agency coordination", "rangeSignals": [ "gbvServices >= true", "survivorProtection >= critical", "multiAgency >= true" ] }, "contextFieldsTemplate": [ { "field": "survivors", "source": "P2 programme scale", "description": "Number of cases" }, { "field": "riskLevel", "source": "P0 security context", "description": "Security risk level" }, { "field": "caseWorkers", "source": "P0 staffing", "description": "Case management staff" }, { "field": "dataSharing", "source": "P2 coordination", "description": "Inter-agency data needs" } ], "implementationComplexity": "high", "examples": { "note": "GBV information management, IASC guidelines", "references": [ { "name": "GBV Information Management System (GBV IMS)", "url": "https://gbvims.com/", "solved": "Purpose-built system for confidential GBV case management with role-based access, survivor data controls, and compliance with international GBV standards" }, { "name": "IOM Data Protection Manual for Counter-Trafficking Operations", "url": "https://www.iom.int/", "solved": "Protocols for protecting trafficking survivor data with emphasis on survivor safety, perpetrator prevention, and secure inter-agency coordination" }, { "name": "Tella - Mobile Documentation Tool for Human Rights", "url": "https://tella.io/", "solved": "Encrypted mobile documentation with evidence preservation for protection programmes and human rights work" } ] }, "solutionQuestions": [ { "id": "survivor-data-control", "type": "select", "options": [ { "label": "Yes, survivor controls all access (even staff need permission)", "value": "survivor-controlled" }, { "label": "Survivor controls sharing outside organization", "value": "survivor-external-control" }, { "label": "Organization controls access based on role, survivor notified", "value": "role-controlled-notify" }, { "label": "Organization controls access, survivor cannot override", "value": "org-controlled" }, { "label": "Case-by-case: depends on survivor capacity and safety assessment", "value": "case-specific" } ], "propertyMapping": { "survivor-controlled": { "technologies": [ "Survivor-centric access control system", "Consent management interface" ], "technologyProperties": { "accessGrant": "Survivor explicitly grants each permission", "scope": "Granular per field or document", "revocation": "Real-time access revocation" } }, "survivor-external-control": { "technologies": [ "External sharing gate", "Organization role-based access" ], "technologyProperties": { "internalAccess": "Staff access by role", "externalAccess": "Survivor must approve", "consentUI": "Survivor-friendly consent interface" } }, "role-controlled-notify": { "technologies": [ "Role-based access with notification", "Consent log" ], "technologyProperties": { "accessByRole": "Staff roles determine access", "notification": "Survivor notified of all access", "challenge": "Survivor can challenge inappropriate access" } }, "org-controlled": { "technologies": [ "Role-based access control", "Audit logging" ], "technologyProperties": { "accessControl": "Organization policy enforced", "transparency": "Survivor can view access log", "limitation": "No survivor veto" } }, "case-specific": { "technologies": [ "Safety assessment tool", "Dynamic access control" ], "technologyProperties": { "assessment": "Intake worker assesses survivor capacity", "controlLevel": "Adjusted based on assessment", "review": "Periodically reassessed" } } }, "prefillFrom": null, "briefSection": "Access control", "text": "Should survivors have primary control over who accesses their case data?", "ngoText": "Should survivors have primary control over who accesses their case data?" }, { "id": "end-to-end-encryption-gbv", "type": "select", "options": [ { "label": "Maximum: end-to-end encryption with survivor-held keys", "value": "e2e-survivor-keys" }, { "label": "Strong: end-to-end encryption with organizational key escrow", "value": "e2e-org-escrow" }, { "label": "Standard: AES-256 at rest, TLS in transit", "value": "standard-encryption" }, { "label": "Lightweight: encryption sufficient for local regulations", "value": "lightweight" }, { "label": "Risk-based: encryption level depends on threat assessment", "value": "risk-based" } ], "propertyMapping": { "e2e-survivor-keys": { "technologies": [ "Survivor-managed encryption", "Key management client" ], "technologyProperties": { "keyLocation": "Survivor device only", "keyExchange": "ECDH with forward secrecy", "keyRecovery": "No recovery without survivor" } }, "e2e-org-escrow": { "technologies": [ "Organization key escrow system", "Multi-party computation" ], "technologyProperties": { "keyManagement": "Organization and survivor both hold parts", "threshold": "2-of-2 required for access", "recovery": "Survivor consent needed for recovery" } }, "standard-encryption": { "technologies": [ "AES-256 encryption module", "TLS transport" ], "technologyProperties": { "encryption": "AES-256-GCM", "keyLocation": "HSM-backed server storage", "keyRotation": "Automatic periodic rotation" } }, "lightweight": { "technologies": [ "Mobile-optimized encryption", "ChaCha20-Poly1305" ], "technologyProperties": { "algorithm": "ChaCha20-Poly1305", "deviceOptimization": "Low CPU and battery impact", "strength": "Still cryptographically sound" } }, "risk-based": { "technologies": [ "Threat assessment module", "Dynamic encryption config" ], "technologyProperties": { "threatLevel": "High-risk: max encryption, low-risk: standard", "assessment": "Based on known perpetrator, context", "review": "Periodic threat reassessment" } } }, "prefillFrom": null, "briefSection": "Privacy and encryption", "text": "What level of encryption must GBV case records have?", "ngoText": "What level of encryption must GBV case records have?" }, { "id": "safe-case-data-storage", "type": "select", "options": [ { "label": "Only locally (no cloud, minimize external exposure)", "value": "local-only" }, { "label": "Local with encrypted cloud backup (survivor-controlled encryption)", "value": "local-plus-encrypted-cloud" }, { "label": "Distributed storage (data fragments in multiple locations)", "value": "distributed-storage" }, { "label": "Private cloud (organization's own infrastructure)", "value": "private-cloud" }, { "label": "Zero-knowledge cloud (provider cannot see data)", "value": "zero-knowledge-cloud" } ], "propertyMapping": { "local-only": { "technologies": [ "Local encrypted database", "Physical security measures" ], "technologyProperties": { "storage": "Single local server", "backup": "External drive or tape (encrypted)", "resilience": "Single point of failure risk" } }, "local-plus-encrypted-cloud": { "technologies": [ "Local primary storage", "End-to-end encrypted cloud backup" ], "technologyProperties": { "primary": "Local for active use", "backup": "Cloud for disaster recovery", "encryption": "Survivor-held encryption key" } }, "distributed-storage": { "technologies": [ "Shamir secret sharing", "Multi-location storage nodes" ], "technologyProperties": { "sharding": "Data split into M-of-N shares", "threshold": "Requires N shares to reconstruct", "resilience": "Can lose N-1 nodes" } }, "private-cloud": { "technologies": [ "Self-hosted cloud infrastructure", "Private cloud platform" ], "technologyProperties": { "ownership": "Organization owns infrastructure", "dataResidency": "Known location (jurisdiction control)", "availability": "Higher than on-premise" } }, "zero-knowledge-cloud": { "technologies": [ "Zero-knowledge storage service", "End-to-end encryption" ], "technologyProperties": { "provider": "Cannot access data (encrypted throughout)", "example": "Providers that hold only encrypted data they cannot read", "trust": "Relies on provider's technical design" } } }, "prefillFrom": null, "briefSection": "Infrastructure requirements", "text": "Where should sensitive GBV case records be stored?", "ngoText": "Where should sensitive GBV case records be stored?" }, { "id": "evidence-preservation", "type": "select", "options": [ { "label": "Digital signatures and hash verification for authenticity", "value": "digital-signature" }, { "label": "Digital timestamping for permanent tamper-proof proof of existence", "value": "blockchain-timestamp" }, { "label": "Third-party notarization and witness signatures", "value": "notarization" }, { "label": "Chain of custody documentation with secure handoff", "value": "chain-of-custody" }, { "label": "Multiple of the above (layered evidence preservation)", "value": "layered-preservation" } ], "propertyMapping": { "digital-signature": { "technologies": [ "Digital signature module", "Certificate authority" ], "technologyProperties": { "algorithm": "ECDSA-SHA256 or RSA", "keyManagement": "HSM-protected signing keys", "verification": "Public key verification" } }, "blockchain-timestamp": { "technologies": [ "Blockchain timestamping service", "Merkle proof generator" ], "technologyProperties": { "chainType": "Public blockchain for trustlessness", "dataOnChain": "Hash of record", "proof": "Merkle path to block root" } }, "notarization": { "technologies": [ "Notary service integration", "Notary directory" ], "technologyProperties": { "authority": "Licensed notary public", "attestation": "Notary signature and seal", "legalWeight": "High in court proceedings" } }, "chain-of-custody": { "technologies": [ "Evidence tracking system", "Custody transfer audit" ], "technologyProperties": { "transfers": "Logged handoffs between handlers", "integrity": "Each handler verifies integrity", "legalStandard": "Meets forensic standards" } }, "layered-preservation": { "technologies": [ "Multi-method preservation system", "Evidence metadata store" ], "technologyProperties": { "methods": "Combination of signature, blockchain, notary", "redundancy": "Multiple proof methods for robustness", "legalRobustness": "Highest legal defensibility" } } }, "prefillFrom": null, "briefSection": "Data integrity", "text": "What evidence preservation requirements do you have for GBV cases?", "ngoText": "What evidence preservation requirements do you have for GBV cases?" }, { "id": "gbv-ims-integration", "type": "select", "options": [ { "label": "Yes, full integration with GBV IMS data standards", "value": "full-gbv-ims" }, { "label": "Partial integration (core data elements compatible)", "value": "partial-gbv-ims" }, { "label": "No integration; use own case management system", "value": "no-integration" }, { "label": "Export capability to GBV IMS format only", "value": "export-only" }, { "label": "Multiple systems: GBV IMS plus local system", "value": "multiple-systems" } ], "propertyMapping": { "full-gbv-ims": { "technologies": [ "GBV IMS data model", "GBV IMS connection" ], "technologyProperties": { "dataModel": "GBV IMS-compliant schema", "synchronization": "Two-way sync with central GBV IMS", "standardCompliance": "Full compliance with GBV IMS" } }, "partial-gbv-ims": { "technologies": [ "GBV IMS core adapter", "Mapping engine" ], "technologyProperties": { "coreFields": "IMS core data elements mapped", "customFields": "Organization's additional fields", "compatibility": "Can export to GBV IMS" } }, "no-integration": { "technologies": [ "Custom case management system", "Case archival" ], "technologyProperties": { "dataModel": "Organization-designed", "interop": "Manual data entry to external systems", "standardization": "Internal standards only" } }, "export-only": { "technologies": [ "GBV IMS export module", "Bulk export capability" ], "technologyProperties": { "export": "Periodic export to GBV IMS", "sync": "One-way export only", "frequency": "Daily or weekly" } }, "multiple-systems": { "technologies": [ "Dual system setup", "Inter-system synchronization" ], "technologyProperties": { "sync": "Keeping GBV IMS and local system in sync", "governance": "Clear responsibility separation", "dataConsistency": "Eventual consistency model" } } }, "prefillFrom": null, "briefSection": "Interoperability", "text": "Do you need to integrate with the GBV Information Management System (GBV IMS)?", "ngoText": "Do you need to integrate with the GBV Information Management System (GBV IMS)?" }, { "id": "consent-withdrawal-gbv", "type": "select", "options": [ { "label": "Immediate deletion (all records destroyed)", "value": "immediate-delete" }, { "label": "Anonymization (identifiers removed, data retained for learning)", "value": "anonymize" }, { "label": "Restricted access (data locked, only accessed with new consent)", "value": "restricted-access" }, { "label": "Archive and seal (stored but not accessed without legal process)", "value": "archive-seal" }, { "label": "Survivor chooses: delete or anonymize per instance", "value": "survivor-choice" } ], "propertyMapping": { "immediate-delete": { "technologies": [ "Secure deletion service", "Cryptographic shredding" ], "technologyProperties": { "deletion": "Irreversible data destruction", "backups": "Deleted from all backups", "timeframe": "Immediate", "evidence": "Deletion certificate issued" } }, "anonymize": { "technologies": [ "Irreversible anonymization", "Record suppression" ], "technologyProperties": { "anonymization": "Identifiers cryptographically removed", "aggregation": "Can be used for aggregate learning", "reversal": "Impossible to re-identify" } }, "restricted-access": { "technologies": [ "Restricted data store", "Re-consent requirement" ], "technologyProperties": { "access": "Locked after withdrawal", "reopening": "Requires new explicit consent", "retention": "Indefinite until deletion requested" } }, "archive-seal": { "technologies": [ "Sealed archive system", "Legal hold override" ], "technologyProperties": { "storage": "Physically secured archive", "access": "Only with court order", "retention": "Per legal hold period" } }, "survivor-choice": { "technologies": [ "Withdrawal choice interface", "Conditional deletion engine" ], "technologyProperties": { "choice": "Survivor selects delete or anonymize", "execution": "Executed per choice", "flexibility": "Different choices for different records" } } }, "prefillFrom": null, "briefSection": "Consent management", "text": "What is your approach to consent withdrawal for GBV evidence?", "ngoText": "What is your approach to consent withdrawal for GBV evidence?" }, { "id": "safe-referral-pathways", "type": "select", "options": [ { "label": "Referral with survivor consent and encrypted information transfer", "value": "consent-encrypted-referral" }, { "label": "Survivor-mediated referral (survivor carries info to referral service)", "value": "survivor-mediated" }, { "label": "Referral via trusted intermediary (known safe provider)", "value": "trusted-intermediary" }, { "label": "No direct referral; survivor contacts services independently", "value": "survivor-initiated" }, { "label": "Service network with pre-established trust and data sharing", "value": "trusted-network" } ], "propertyMapping": { "consent-encrypted-referral": { "technologies": [ "Referral consent system", "Encrypted referral data transfer" ], "technologyProperties": { "consent": "Survivor explicitly consents to referral", "encryption": "End-to-end encrypted transfer", "dataMinimization": "Only necessary information shared" } }, "survivor-mediated": { "technologies": [ "Survivor information packet generator", "Encrypted portable format" ], "technologyProperties": { "format": "Encrypted document or USB key", "portability": "Survivor carries to referral service", "opening": "Referral service verifies survivor identity" } }, "trusted-intermediary": { "technologies": [ "Intermediary verification system", "Trusted partner directory" ], "technologyProperties": { "intermediary": "Known safe person or organization", "verification": "Verified identity and reputation", "dataTransfer": "Secure transfer via intermediary" } }, "survivor-initiated": { "technologies": [ "Service directory", "Survivor contact information" ], "technologyProperties": { "independence": "Survivor independently contacts service", "noDataShare": "No data shared by original provider", "autonomy": "Maximizes survivor control" } }, "trusted-network": { "technologies": [ "Service network protocol", "Pre-established data sharing" ], "technologyProperties": { "network": "Vetted service providers", "sharing": "Pre-agreed data sharing standards", "governance": "Collective governance and oversight" } } }, "prefillFrom": null, "briefSection": "Interoperability", "text": "What are your current safe referral pathways for GBV survivors?", "ngoText": "What are your current safe referral pathways for GBV survivors?" }, { "id": "audit-reporting-gbv", "type": "select", "options": [ { "label": "Survivor-visible access log (survivor can see all access)", "value": "survivor-visible" }, { "label": "Organization audit for compliance (staff oversight)", "value": "org-audit" }, { "label": "Aggregate reporting (no individual case details)", "value": "aggregate-reporting" }, { "label": "External audit by independent body", "value": "external-audit" }, { "label": "No audit (maximum privacy, minimal oversight)", "value": "no-audit" } ], "propertyMapping": { "survivor-visible": { "technologies": [ "Client-facing audit interface", "Real-time access notifications" ], "technologyProperties": { "visibility": "Survivor can view who accessed what", "notification": "Alert on each access", "challenge": "Survivor can challenge inappropriate access" } }, "org-audit": { "technologies": [ "Internal audit logging", "Supervisor review queue" ], "technologyProperties": { "logging": "Comprehensive access logging", "review": "Regular supervisor audits", "enforcement": "Policy violations have consequences" } }, "aggregate-reporting": { "technologies": [ "Aggregate statistics engine", "Privacy-preserving reporting" ], "technologyProperties": { "reporting": "Aggregate counts and statistics", "deidentification": "No individual cases in reports", "compliance": "Meets confidentiality standards" } }, "external-audit": { "technologies": [ "Third-party audit platform", "Independent auditor access" ], "technologyProperties": { "auditor": "External, independent auditor", "access": "Full access to audit logs", "reporting": "Public audit reports" } }, "no-audit": { "technologies": [ "No audit infrastructure", "Access logs not reviewed" ], "technologyProperties": { "privacy": "Maximum confidentiality", "tradeoff": "No accountability oversight", "useCase": "High-risk situations only" } } }, "prefillFrom": null, "briefSection": "Reporting and audit", "text": "What audit and reporting requirements do you have for GBV cases?", "ngoText": "What audit and reporting requirements do you have for GBV cases?" }, { "id": "beneficiary-choice", "label": "How will beneficiaries exercise choice in how they receive and use this service?", "type": "select", "briefSection": "Consent management", "options": [ { "label": "Beneficiaries choose between delivery methods (cash, voucher, mobile money, direct)", "value": "delivery-choice" }, { "label": "Beneficiaries choose preferred merchants or service points", "value": "merchant-choice" }, { "label": "Beneficiaries control their own data sharing preferences", "value": "data-choice" }, { "label": "Multiple choice dimensions (delivery + merchant + data)", "value": "full-choice" }, { "label": "Limited choice: programme constraints determine delivery", "value": "limited" } ], "propertyMapping": { "delivery-choice": { "technologies": [], "technologyProperties": { "beneficiaryChoice": "Delivery method choice", "dignityDesign": "Beneficiaries select preferred receipt method" } }, "merchant-choice": { "technologies": [], "technologyProperties": { "beneficiaryChoice": "Merchant/service point choice", "dignityDesign": "Beneficiaries select where to redeem" } }, "data-choice": { "technologies": [], "technologyProperties": { "beneficiaryChoice": "Data sharing choice", "dignityDesign": "Beneficiaries control personal data sharing" } }, "full-choice": { "technologies": [], "technologyProperties": { "beneficiaryChoice": "Multi-dimensional choice", "dignityDesign": "Full beneficiary agency across delivery, merchant, and data" } }, "limited": { "technologies": [], "technologyProperties": { "beneficiaryChoice": "Limited by programme design", "dignityDesign": "Programme constraints; beneficiary informed of reasons" } } }, "text": "How will beneficiaries exercise choice in how they receive and use this service?" } ], "complexityFactors": { "relationships": 2, "operationalChange": 2, "dataCompliance": 5 }, "securityTier": "C", "suggestedCriteria": [ { "id": "SC-C042-SAFETY", "name": "Survivor Safety Architecture", "description": "The solution protects survivors from re-identification, data leaks, or system compromise that could endanger lives. GBV data exposure can result in honour violence, retaliation, or social exclusion.", "weight": 0.35, "ratingGuide": { "5": "Zero-knowledge architecture with no admin backdoor. Designed specifically for GBV data. Emergency data destruction capability. No metadata leakage of case involvement.", "4": "End-to-end encryption with survivor-controlled access. Case worker access requires survivor participation. Emergency lockdown available.", "3": "Strong encryption with strict role-based access. Limited to assigned case worker. Organisation admin access under emergency protocol only.", "2": "Standard encryption with role-based access. Multiple staff can access case files. No emergency destruction capability.", "1": "Basic access controls. Case data accessible to administrators. No special GBV-specific protections." } }, { "id": "SC-C042-GBVIMS", "name": "GBV Information Management Compliance", "description": "Does the solution align with GBVIMS (GBV Information Management System) standards, IASC GBV guidelines, and survivor-centred approaches?", "weight": 0.25, "ratingGuide": { "5": "Purpose-built for GBVIMS. Supports standard incident classifications, age/sex disaggregation, and survivor-centred workflow. Endorsed by GBV coordination bodies.", "4": "GBVIMS-compatible data model. Supports standard classifications and reporting. Aligns with IASC guidelines.", "3": "Adaptable to GBVIMS requirements with configuration. Standard humanitarian case management features.", "2": "General case management system. GBVIMS alignment requires significant customisation.", "1": "No awareness of GBV-specific standards or survivor-centred practice requirements." } }, { "id": "SC-C042-CONSENT", "name": "Survivor-centred Consent Model", "description": "The consent model reflects survivor agency. GBV survivors must control who accesses their data, with easy and complete withdrawal at any time.", "weight": 0.2, "ratingGuide": { "5": "Survivor controls all access decisions. Granular per-field consent. Instant revocation with verified data deletion. Informed consent process designed with GBV practitioners.", "4": "Survivor consent required for all access. Revocation supported with data retention controls. Clear consent documentation.", "3": "Standard consent management. Revocation possible but may not be immediate. Data retention governed by policy.", "2": "Consent recorded but access controlled by case workers. Revocation requires administrative process.", "1": "No survivor-centred consent. Data governance is organisational, not survivor-driven." } }, { "id": "SC-C042-AGGREGATE", "name": "Safe Statistical Reporting", "description": "Can GBV case data be aggregated for donor and coordination reporting without any possibility of individual case identification?", "weight": 0.1, "ratingGuide": { "5": "Secure aggregation with formal privacy guarantees. Suppresses small cohorts automatically. Outputs only aggregate statistics with no linkage to individual cases.", "4": "Aggregation with k-anonymity. Small group suppression. Configurable minimum cohort sizes.", "3": "Standard aggregation with manual anonymisation review. Risk of small-cohort re-identification if not carefully managed.", "2": "Basic count/summary reporting. Anonymisation is manual and error-prone.", "1": "No aggregation features. Individual case data must be manually counted for reporting." } }, { "id": "SC-C042-FORENSIC", "name": "Evidence Integrity for Legal Proceedings", "description": "If survivors choose to pursue legal action, can the system produce tamper-proof evidence records that are admissible in judicial proceedings?", "weight": 0.1, "ratingGuide": { "5": "Cryptographic timestamps and chain-of-custody proofs. Admissible in international courts. Evidence sealed at time of recording with non-repudiation.", "4": "Tamper-proof records with cryptographic integrity. Designed to support legal proceedings. Chain of custody documented.", "3": "Audit trail provides evidence of record integrity. Usable in legal contexts but not purpose-designed for it.", "2": "Standard database records with timestamps. Limited forensic value.", "1": "No evidence integrity features. Records can be questioned in legal proceedings." } } ], "procurement": { "marketMaturity": "nascent", "primaryMode": "integrator-led", "alternativeModes": [ "consortium" ], "reasoning": "GBV/protection case data is highly sensitive; bespoke deployments only.", "exampleProductCategories": [ "protection-case-management", "gbv-records-platform" ], "partnerChannels": [], "lastReviewed": "2026-05-01" } }, { "id": "UC-C-043", "name": "Beneficiary deduplication across programmes and organisations", "category": "C", "subcategory": "Data Integrity", "description": "Find out whether a person is already registered with another programme or agency without sharing their full details, so aid is not given twice.", "bCriteria": [ "B1", "B2", "B6" ], "requiredComponents": [ { "component": "identity-protocol", "description": "Privacy-preserving identity matching" }, { "component": "data-layer", "description": "Deduplicated beneficiary register" }, { "component": "privacy-tech", "description": "Privacy-preserving record linkage" }, { "component": "verification-mechanism", "description": "Proof of deduplication" } ], "conditionalComponents": [ { "component": "anonymisation-tools", "condition": "For blind matching without exposing data" } ], "crossCategoryDependencies": [ "UC-B-024 for beneficiary identity" ], "p2TriggerConditions": { "description": "Activated when P2 shows multiple programmes + duplication concerns + multi-org coordination", "rangeSignals": [ "programmes >= 2+", "duplicationConcerns >= true", "multiOrg >= true" ] }, "contextFieldsTemplate": [ { "field": "beneficiaries", "source": "P2 programme scale", "description": "Total beneficiaries" }, { "field": "programmes", "source": "P0 programmes", "description": "Number of programmes" }, { "field": "dataElements", "source": "P2 matching", "description": "Fields for matching" }, { "field": "partners", "source": "P0 partnerships", "description": "Organisations involved" } ], "implementationComplexity": "high", "examples": { "note": "Humanitarian deduplication efforts, privacy-preserving matching", "references": [ { "name": "Worldbank ID4D (Identification for Development) Initiative", "url": "https://id4d.worldbank.org/", "solved": "Guidelines for beneficiary identification and deduplication in development programmes with privacy-preserving matching" }, { "name": "UNICEF Rapid Beneficiary Identification (RBI) Protocol", "url": "https://www.unicef.org/", "solved": "Standardised protocols for identifying and deduplicating vulnerable populations across programmes" }, { "name": "Privacy-Preserving Record Linkage (PPRL) - Open Standards", "url": "https://github.com/aehall/pprl", "solved": "Open-source implementations of secure multi-party computation matching for privacy-preserving deduplication" } ] }, "solutionQuestions": [ { "id": "matching-algorithm", "type": "select", "options": [ { "label": "Deterministic: exact field matches (name, ID, DOB)", "value": "deterministic" }, { "label": "Probabilistic: similarity scoring with threshold", "value": "probabilistic" }, { "label": "Privacy-preserving: secure multi-party computation matching", "value": "secure-mpc" }, { "label": "Biometric: fingerprint or iris matching across programs", "value": "biometric" }, { "label": "Hybrid: combination of above methods", "value": "hybrid" } ], "propertyMapping": { "deterministic": { "technologies": [ "Exact-match deduplication engine", "Record linkage module" ], "technologyProperties": { "matchCriteria": "Full name + DOB + ID or phonenumber exact match", "falsePositives": "Low (0-5%)", "falseNegatives": "High (30-50% if data incomplete)" } }, "probabilistic": { "technologies": [ "Similarity scoring engine", "Fuzzy matching algorithm" ], "technologyProperties": { "algorithm": "Levenshtein distance, Soundex, or ML-based", "threshold": "Configurable (e.g., 95% similarity)", "accuracy": "Medium-high with good training data" } }, "secure-mpc": { "technologies": [ "Secure multi-party computation platform", "Privacy-preserving linkage" ], "technologyProperties": { "privacy": "No program sees other program's raw data", "computation": "Comparison done in encrypted domain", "performance": "Slower than direct matching" } }, "biometric": { "technologies": [ "Biometric matching service", "Fingerprint or iris database" ], "technologyProperties": { "modality": "Fingerprint or iris scan", "accuracy": "Very high (99%+)", "infrastructure": "Requires biometric capture devices" } }, "hybrid": { "technologies": [ "Multi-algorithm deduplication engine", "Confidence scoring" ], "technologyProperties": { "approach": "Combines deterministic, probabilistic, and biometric", "confidence": "Combined confidence score", "accuracy": "Highest overall accuracy" } } }, "prefillFrom": null, "briefSection": "Data architecture", "text": "How do you currently identify duplicate beneficiary records across programmes?", "ngoText": "How do you currently identify duplicate beneficiary records across programmes?" }, { "id": "privacy-tech-choice", "type": "select", "options": [ { "label": "privacy-preserving computation (data stays encrypted during analysis)", "value": "homomorphic" }, { "label": "Secure multi-party computation (distributed trust)", "value": "multiparty-computation" }, { "label": "Differential privacy (add statistical noise)", "value": "differential-privacy" }, { "label": "Trusted execution environment (hardware secure enclave)", "value": "tee" }, { "label": "None: centralized matching with access control", "value": "none-central" } ], "propertyMapping": { "homomorphic": { "technologies": [ "Homomorphic encryption engine", "Encrypted computation processor" ], "technologyProperties": { "computation": "Queries run on encrypted data", "decryption": "Only beneficiary can decrypt results", "performance": "1000-10000x slower than plaintext" } }, "multiparty-computation": { "technologies": [ "MPC coordination service", "Secure computation infrastructure" ], "technologyProperties": { "parties": "2-N program operators", "sharing": "Secret sharing of beneficiary records", "conclusion": "Only joint result revealed" } }, "differential-privacy": { "technologies": [ "Differential privacy engine", "Noise injection layer" ], "technologyProperties": { "noiseLevel": "Configurable epsilon (privacy budget)", "accuracy": "Trade-off between privacy and accuracy", "guarantee": "Formal privacy bound" } }, "tee": { "technologies": [ "Trusted execution environment", "Hardware secure enclave" ], "technologyProperties": { "enclave": "Isolated CPU enclave for computation", "attestation": "Hardware attestation of execution", "risk": "Hardware vulnerabilities possible" } }, "none-central": { "technologies": [ "Centralized deduplication database", "Role-based access control" ], "technologyProperties": { "location": "Single trusted database", "access": "Restricted to authorized staff", "risk": "Single point of failure and compromise" } } }, "prefillFrom": null, "briefSection": "Privacy and encryption", "text": "What privacy-preserving technology should protect beneficiary privacy during matching?", "ngoText": "What privacy-preserving technology should protect beneficiary privacy during matching?" }, { "id": "cross-org-coordination", "type": "select", "options": [ { "label": "Central authority checks (government or lead agency manages a shared registry)", "value": "central-authority-checks-government-or-l" }, { "label": "Each organisation queries others directly before enrolling", "value": "each-organisation-queries-others-directl" }, { "label": "Organisations share beneficiary lists periodically and cross-check", "value": "organisations-share-beneficiary-lists-pe" }, { "label": "No coordination currently, each programme manages its own enrolment independently", "value": "no-coordination-currently-each-programme" } ], "propertyMapping": { "central-authority": { "technologies": [ "National beneficiary registry", "Deduplication service" ], "technologyProperties": { "registry": "Government-operated", "submission": "Programs submit beneficiary lists", "matching": "Central authority performs matching" } }, "federated-registry": { "technologies": [ "Federated query engine", "Shared registry with access controls" ], "technologyProperties": { "registry": "Shared database accessible to all programs", "query": "Each program queries for matches", "governance": "Shared governance of registry" } }, "peer-to-peer": { "technologies": [ "P2P matching protocol", "Direct program linkage" ], "technologyProperties": { "communication": "Direct API between programs", "coordination": "No central authority", "trust": "Based on peer agreements" } }, "manual-sharing": { "technologies": [ "Data export/import tools", "Manual review process" ], "technologyProperties": { "frequency": "Periodic (monthly or quarterly)", "format": "Encrypted spreadsheet or secure file transfer", "review": "Human review of potential matches" } }, "no-coordination": { "technologies": [ "Local deduplication only", "No cross-program matching" ], "technologyProperties": { "scope": "Single program only", "duplication": "Beneficiary may enroll in multiple programs", "limitation": "No cross-program deduplication benefit" } } }, "prefillFrom": null, "briefSection": "Interoperability", "text": "How do you currently coordinate deduplication across organizations?", "ngoText": "How do you currently coordinate deduplication across organizations?", "hidden": true, "question": "How do you currently coordinate with other organisations to avoid enrolling the same beneficiaries in multiple programmes?" }, { "id": "deduplication-proof", "type": "select", "options": [ { "label": "Audit trail log (who matched what, when)", "value": "audit-trail" }, { "label": "Secure digital proof (hash of matches on digital ledger)", "value": "crypto-proof" }, { "label": "Third-party audit (independent verification)", "value": "third-party" }, { "label": "Beneficiary transparency (beneficiary sees own matches)", "value": "beneficiary-transparency" }, { "label": "Multi-signature approval (multiple parties sign off)", "value": "multi-signature" } ], "propertyMapping": { "audit-trail": { "technologies": [ "Audit logging system", "Log integrity protection" ], "technologyProperties": { "logging": "Complete log of all matching decisions", "protection": "Immutable log storage", "retention": "Permanent retention" } }, "crypto-proof": { "technologies": [ "Blockchain anchoring service", "Merkle proof generator" ], "technologyProperties": { "proofType": "Hash of match results anchored to blockchain", "verifiability": "Anyone can verify integrity", "immutability": "Permanent record" } }, "third-party": { "technologies": [ "Independent audit service", "Audit certification" ], "technologyProperties": { "auditor": "External independent auditor", "scope": "Full review of matching algorithm and process", "certification": "Published audit report" } }, "beneficiary-transparency": { "technologies": [ "Beneficiary match interface", "Notification system" ], "technologyProperties": { "visibility": "Beneficiary can see all their identified matches", "challenge": "Beneficiary can dispute matches", "feedback": "Used to improve matching" } }, "multi-signature": { "technologies": [ "Multi-signature approval workflow", "Coordinator validation" ], "technologyProperties": { "signatories": "2-3 independent organizations", "approval": "All must sign off on match results", "accountability": "Distributed responsibility" } } }, "prefillFrom": null, "briefSection": "Data integrity", "text": "What method do you currently use to prove deduplication of beneficiary records?", "ngoText": "What method do you currently use to prove deduplication of beneficiary records?" }, { "id": "duplicate-resolution", "type": "select", "options": [ { "label": "Automatic merge (combine records, deactivate duplicate)", "value": "auto-merge" }, { "label": "Manual review and merge (human decision)", "value": "manual-merge" }, { "label": "Flag for investigation (mark as potential duplicate, no action)", "value": "flag-investigate" }, { "label": "Notify beneficiary (let them decide)", "value": "notify-beneficiary" }, { "label": "Ring-fencing (keep separate but link for alerts)", "value": "ring-fencing" } ], "propertyMapping": { "auto-merge": { "technologies": [ "Automatic record merger", "Conflict resolution engine" ], "technologyProperties": { "merging": "Automatic combination of records", "deactivation": "Duplicate marked inactive", "auditTrail": "Record merge decision logged" } }, "manual-merge": { "technologies": [ "Manual review interface", "Merge approval workflow" ], "technologyProperties": { "review": "Human caseworker reviews match", "decision": "Worker decides to merge or not", "merging": "Manual merge if approved" } }, "flag-investigate": { "technologies": [ "Duplicate flagging system", "Flagging interface" ], "technologyProperties": { "flag": "Marked as potential duplicate", "noAction": "Both records remain active", "investigation": "Staff can investigate when time permits" } }, "notify-beneficiary": { "technologies": [ "Beneficiary notification system", "Beneficiary portal" ], "technologyProperties": { "notification": "Beneficiary notified of potential duplicate", "choice": "Beneficiary decides merge or not", "control": "Beneficiary has agency" } }, "ring-fencing": { "technologies": [ "Duplicate linking system", "Fraud alert system" ], "technologyProperties": { "linking": "Records linked but kept separate", "alerts": "Alert if duplicate tries to access", "benefit": "Prevent double-dipping while preserving data" } } }, "prefillFrom": null, "briefSection": "Data integrity", "text": "When duplicates are detected, what is your current policy for resolving conflicting data? (Primary source always wins / manual review / newest record)", "ngoText": "When duplicates are detected, what is your current policy for resolving conflicting data? (Primary source always wins / manual review / newest record)" }, { "id": "beneficiary-consent-dedup", "type": "select", "options": [ { "label": "Yes, explicit consent required for matching", "value": "explicit-consent" }, { "label": "Implied consent (part of program enrollment)", "value": "implied-consent" }, { "label": "Notification only (beneficiary informed but no consent)", "value": "notification" }, { "label": "Opt-out (beneficiary can refuse deduplication)", "value": "opt-out" }, { "label": "No choice (required for program participation)", "value": "no-choice" } ], "propertyMapping": { "explicit-consent": { "technologies": [ "Consent management system", "Consent interface" ], "technologyProperties": { "consentType": "Specific consent for deduplication", "timing": "Obtained before matching", "documentation": "Consent agreement retained" } }, "implied-consent": { "technologies": [ "Service enrollment consent", "Terms and conditions" ], "technologyProperties": { "integration": "Part of standard enrollment", "documentation": "Mentioned in program terms", "presumption": "Enrollment implies consent" } }, "notification": { "technologies": [ "Notification system", "Information dissemination" ], "technologyProperties": { "method": "Email, SMS, or in-person notification", "timing": "Before or after matching", "feedback": "Optional beneficiary response" } }, "opt-out": { "technologies": [ "Opt-out mechanism", "Exclusion list" ], "technologyProperties": { "optOut": "Beneficiary can exclude themselves", "timing": "Anytime before matching", "consequence": "May limit program participation" } }, "no-choice": { "technologies": [ "Mandatory program policy", "No opt-out" ], "technologyProperties": { "requirement": "Required for program", "choice": "No alternative", "justification": "Fraud prevention necessary" } } }, "prefillFrom": null, "briefSection": "Consent management", "text": "Should beneficiaries consent to participation in deduplication?", "ngoText": "Should beneficiaries consent to participation in deduplication?" }, { "id": "data-retention-dedup", "type": "select", "options": [ { "label": "Only during active enrollment (deleted on exit)", "value": "active-enrollment-only" }, { "label": "5-7 years for audit and fraud prevention", "value": "five-years" }, { "label": "Indefinite retention for historical tracking", "value": "indefinite" }, { "label": "Beneficiary-controlled (beneficiary can request deletion)", "value": "beneficiary-controlled" }, { "label": "Risk-based (retention depends on fraud risk)", "value": "risk-based" } ], "propertyMapping": { "active-enrollment-only": { "technologies": [ "Automatic deletion on exit", "Retention policy engine" ], "technologyProperties": { "deletion": "Automatic on program exit", "timing": "Immediate or with notice period", "compliance": "Minimal data retention" } }, "five-years": { "technologies": [ "Retention schedule system", "Automatic archival" ], "technologyProperties": { "retentionPeriod": "5-7 years from last enrollment", "archival": "Moved to cold storage after use", "deletion": "Automatic deletion after period" } }, "indefinite": { "technologies": [ "Permanent archive system", "Long-term storage" ], "technologyProperties": { "retention": "Permanent", "storage": "Secure archive", "access": "Limited to authorized historical queries" } }, "beneficiary-controlled": { "technologies": [ "Right-to-deletion interface", "Data deletion service" ], "technologyProperties": { "request": "Beneficiary can request deletion anytime", "compliance": "GDPR right to be forgotten", "immediacy": "Deletion within days" } }, "risk-based": { "technologies": [ "Risk assessment tool", "Dynamic retention policy" ], "technologyProperties": { "riskAssessment": "Higher-risk cases retained longer", "periodReview": "Periodic risk reassessment", "customization": "Per-case retention decision" } } }, "prefillFrom": null, "briefSection": "Data integrity", "text": "How long should deduplication records and beneficiary data be retained?", "ngoText": "How long should deduplication records and beneficiary data be retained?" }, { "id": "dedup-error-correction", "type": "select", "options": [ { "label": "Automatic reversal (records unmerged with full history restore)", "value": "auto-reversal" }, { "label": "Manual unmerge process (human decision to split records)", "value": "manual-unmerge" }, { "label": "Create separate record (keep merged, create new clean record)", "value": "new-record" }, { "label": "Appeal process (beneficiary can appeal to dispute match)", "value": "appeal-process" }, { "label": "No correction; merged records kept (minimal remedy)", "value": "no-correction" } ], "propertyMapping": { "auto-reversal": { "technologies": [ "Automated unmerge system", "Data restoration from backup" ], "technologyProperties": { "unmerge": "Automatic separation of records", "restoration": "Full data history restored", "speed": "Immediate correction" } }, "manual-unmerge": { "technologies": [ "Manual unmerge interface", "Caseworker review" ], "technologyProperties": { "review": "Caseworker reviews merge decision", "unmerge": "Manual splitting if error confirmed", "timeline": "24-48 hour resolution" } }, "new-record": { "technologies": [ "New record creation", "Merged record linking" ], "technologyProperties": { "approach": "Keep merged, create new separate record", "linking": "Note relationship between records", "drawback": "Doesn't fully restore original separation" } }, "appeal-process": { "technologies": [ "Appeal submission interface", "Review and decision system" ], "technologyProperties": { "submission": "Beneficiary submits appeal", "review": "Independent review of match", "decision": "Merge reversed if appeal granted" } }, "no-correction": { "technologies": [ "No remedial system", "Limited appeal" ], "technologyProperties": { "consequence": "Incorrect merge not easily corrected", "appeal": "Very limited or no appeal process", "risk": "Ongoing harm to beneficiary" } } }, "prefillFrom": null, "briefSection": "Data integrity", "text": "What happens if someone is incorrectly identified as a duplicate?", "ngoText": "What happens if someone is incorrectly identified as a duplicate?" }, { "id": "beneficiary-choice", "label": "How will beneficiaries exercise choice in how they receive and use this service?", "type": "select", "briefSection": "Consent management", "options": [ { "label": "Beneficiaries choose between delivery methods (cash, voucher, mobile money, direct)", "value": "delivery-choice" }, { "label": "Beneficiaries choose preferred merchants or service points", "value": "merchant-choice" }, { "label": "Beneficiaries control their own data sharing preferences", "value": "data-choice" }, { "label": "Multiple choice dimensions (delivery + merchant + data)", "value": "full-choice" }, { "label": "Limited choice: programme constraints determine delivery", "value": "limited" } ], "propertyMapping": { "delivery-choice": { "technologies": [], "technologyProperties": { "beneficiaryChoice": "Delivery method choice", "dignityDesign": "Beneficiaries select preferred receipt method" } }, "merchant-choice": { "technologies": [], "technologyProperties": { "beneficiaryChoice": "Merchant/service point choice", "dignityDesign": "Beneficiaries select where to redeem" } }, "data-choice": { "technologies": [], "technologyProperties": { "beneficiaryChoice": "Data sharing choice", "dignityDesign": "Beneficiaries control personal data sharing" } }, "full-choice": { "technologies": [], "technologyProperties": { "beneficiaryChoice": "Multi-dimensional choice", "dignityDesign": "Full beneficiary agency across delivery, merchant, and data" } }, "limited": { "technologies": [], "technologyProperties": { "beneficiaryChoice": "Limited by programme design", "dignityDesign": "Programme constraints; beneficiary informed of reasons" } } }, "text": "How will beneficiaries exercise choice in how they receive and use this service?" } ], "complexityFactors": { "relationships": 4, "operationalChange": 3, "dataCompliance": 4 }, "securityTier": "B", "suggestedCriteria": [ { "id": "SC-C043-MATCHING", "name": "Privacy-preserving Record Matching", "description": "Can the solution identify duplicate beneficiaries across organisations without either party revealing their beneficiary data to the other?", "weight": 0.35, "ratingGuide": { "5": "Zero-knowledge matching \u2014 generates cryptographic proofs that records match without revealing any underlying data. Neither party learns anything about non-matching records.", "4": "Secure multi-party computation for matching. Data remains with each organisation but matching is computed jointly. Minimal leakage.", "3": "Privacy-preserving record linkage using hashed identifiers. Some inference risk from match/no-match patterns.", "2": "Matching via a trusted third party who sees both datasets. Privacy depends on third-party trustworthiness.", "1": "Requires organisations to share beneficiary lists for central matching. Full data exposure." } }, { "id": "SC-C043-ACCURACY", "name": "Matching Accuracy and False Positive Rate", "description": "This measures how accurate the deduplication algorithm is. False positives deny services to legitimate beneficiaries; false negatives waste resources on duplicates.", "weight": 0.25, "ratingGuide": { "5": "Configurable matching thresholds with documented accuracy rates. False positive rate below 1% in field testing. Supports fuzzy matching for name transliteration and spelling variations.", "4": "Strong matching accuracy with fuzzy matching support. False positive rate below 3%. Handles common data quality issues.", "3": "Standard matching algorithms. Reasonable accuracy with clean data. Struggles with name transliteration and incomplete records.", "2": "Basic exact-match deduplication. High false negative rate with messy humanitarian data. No fuzzy matching.", "1": "Simple string matching only. Fails with any data quality variation. Unsuitable for humanitarian contexts." } }, { "id": "SC-C043-MULTI", "name": "Multi-organisation Scalability", "description": "The solution can scale to deduplication across 5, 10, or 50+ organisations simultaneously. Humanitarian coordination involves many actors.", "weight": 0.15, "ratingGuide": { "5": "Handles 50+ organisations simultaneously with sub-linear computation growth. Tested in large-scale humanitarian coordination.", "4": "Scales to 20+ organisations. Performance acceptable for cluster-level coordination.", "3": "Handles bilateral deduplication well. Multi-party (5-10 orgs) possible but requires sequential processing.", "2": "Designed for bilateral comparison only. Multi-party requires repeated bilateral runs.", "1": "Single-organisation deduplication only. No cross-organisation capability." } }, { "id": "SC-C043-OFFLINE", "name": "Field Office Connectivity Tolerance", "description": "Can deduplication work with intermittent connectivity between field offices and central coordination?", "weight": 0.15, "ratingGuide": { "5": "Generates portable deduplication proofs that work offline. Field offices can verify against cached proofs. Syncs when connectivity available.", "4": "Batch deduplication runs tolerate intermittent connectivity. Results cached locally. Periodic sync sufficient.", "3": "Requires connectivity for deduplication runs but tolerates temporary outages. Results available offline once computed.", "2": "Needs reliable internet for deduplication. Offline access to previous results only.", "1": "Requires all parties online simultaneously. Unusable in low-connectivity field settings." } }, { "id": "SC-C043-GOVERNANCE", "name": "Data Governance and Dispute Resolution", "description": "How does the solution handle governance of shared deduplication results? Who decides what happens when a duplicate is found? What appeals process exists?", "weight": 0.1, "ratingGuide": { "5": "Built-in governance framework with configurable rules per organisation. Dispute resolution workflow. Audit trail of all deduplication decisions. Supports appeals.", "4": "Governance rules configurable. Match results require mutual agreement before action. Decision audit trail.", "3": "Standard governance \u2014 matches flagged for human review. Basic workflow for resolving disputes.", "2": "Matches reported to a coordinator. No built-in dispute resolution. Manual governance.", "1": "No governance features. Deduplication results are final with no appeal or review mechanism." } } ], "procurement": { "marketMaturity": "emerging", "primaryMode": "integrator-led", "alternativeModes": [ "consortium" ], "reasoning": "Beneficiary deduplication systems exist in the UN system; integration with multi-organisation workflows is complex.", "exampleProductCategories": [ "beneficiary-deduplication-platform", "identity-resolution-saas" ], "partnerChannels": [], "lastReviewed": "2026-05-01" } }, { "id": "UC-C-044", "name": "Impact data integrity and verification", "category": "C", "subcategory": "Data Integrity", "description": "Make reported results, such as people served or outcomes reached, hard to change after the fact and easy for donors and auditors to check.", "bCriteria": [ "B3" ], "requiredComponents": [ { "component": "data-layer", "description": "Immutable impact data records" }, { "component": "audit-mechanism", "description": "Tamper-proof audit trail" }, { "component": "verification-mechanism", "description": "Data verification proofs" } ], "conditionalComponents": [ { "component": "smart-contracts", "condition": "If automated impact verification" }, { "component": "oracle-data", "condition": "If external impact data" } ], "crossCategoryDependencies": [], "p2TriggerConditions": { "description": "Activated when P2 shows impact measurement + donor accountability + data integrity concerns", "rangeSignals": [ "impactTracking >= critical", "donorReporting >= monthly", "dataIntegrity >= concern" ] }, "contextFieldsTemplate": [ { "field": "indicators", "source": "P2 M&E framework", "description": "Impact indicators tracked" }, { "field": "beneficiaries", "source": "P2 programme scale", "description": "Beneficiaries tracked" }, { "field": "dataCollection", "source": "P2 M&E methods", "description": "Data collection approach" }, { "field": "reportingFrequency", "source": "P0 donor agreements", "description": "Required reporting" } ], "implementationComplexity": "medium", "examples": { "note": "M&E blockchain integration, data integrity", "references": [ { "name": "Open Data Kit (ODK) - Robust Data Collection", "url": "https://getodk.org/", "solved": "Open-source mobile data collection with built-in integrity checks, offline capability, and audit trails" }, { "name": "Humanitarian Data Exchange (HDX) - Data Standards", "url": "https://data.humdata.org/", "solved": "International standards for humanitarian impact data quality and integrity verification" }, { "name": "International Initiative for Impact Evaluation (3ie) - Evidence Standards", "url": "https://www.3ieimpact.org/", "solved": "Impact evaluation methodologies including randomised controlled trials and verification protocols" } ] }, "solutionQuestions": [ { "id": "data-collection-integrity", "type": "select", "options": [ { "label": "Enumerator authentication with timestamp and GPS", "value": "enumerator-gps" }, { "label": "digitally verified verification of data", "value": "hash-verification" }, { "label": "Random field audits and beneficiary verification calls", "value": "random-audit" }, { "label": "Multi-person data collection (redundant verification)", "value": "multi-person" }, { "label": "Computer vision verification (photo/video proof)", "value": "computer-vision" } ], "propertyMapping": { "enumerator-gps": { "technologies": [ "GPS location capture", "Enumerator authentication module" ], "technologyProperties": { "verification": "Timestamp + GPS coordinates on each record", "enumeratorAuth": "Biometric or PIN authentication", "geofencing": "Verify enumerator was at site" } }, "hash-verification": { "technologies": [ "Cryptographic hash module", "Integrity verification" ], "technologyProperties": { "hashing": "SHA-256 hash of collected data", "verification": "Hash compared to reference", "immutability": "Detect any data modification" } }, "random-audit": { "technologies": [ "Random sampling system", "Verification call system" ], "technologyProperties": { "sampling": "Random 10-20% beneficiary verification", "method": "Phone call or in-person verification", "resolution": "Investigation if discrepancy found" } }, "multi-person": { "technologies": [ "Multi-enumerator data collection", "Consensus algorithm" ], "technologyProperties": { "redundancy": "2-3 enumerators collect same data", "consensus": "Agreement required for data to pass", "fraud": "Hard to collude between multiple people" } }, "computer-vision": { "technologies": [ "Photo/video capture", "AI image verification" ], "technologyProperties": { "capture": "Photo or video of beneficiary/asset", "analysis": "AI verifies photo authenticity and relevance", "timestamp": "Photo metadata includes GPS and time" } } }, "prefillFrom": null, "briefSection": "Data architecture", "text": "How do you currently ensure data collected in the field is accurate?", "ngoText": "How do you currently ensure data collected in the field is accurate?" }, { "id": "automated-rules-checking", "type": "select", "options": [ { "label": "Yes, hard rules that reject impossible data", "value": "hard-rules" }, { "label": "Yes, soft rules that flag suspicious data for review", "value": "soft-rules" }, { "label": "Yes, AI-based anomaly detection", "value": "ai-anomaly" }, { "label": "Minimal: only check for missing required fields", "value": "minimal-rules" }, { "label": "No: trust enumerators without automated checks", "value": "no-rules" } ], "propertyMapping": { "hard-rules": { "technologies": [ "Rule engine", "Validation framework" ], "technologyProperties": { "rules": "Hard-coded business rules", "example": "Age > 0 and < 120, enrollment date < today", "action": "Reject data that fails rules" } }, "soft-rules": { "technologies": [ "Flagging engine", "Review queue system" ], "technologyProperties": { "rules": "Suspicious but not impossible (e.g., age > 100)", "action": "Flag for human review", "resolution": "Human decision to accept or reject" } }, "ai-anomaly": { "technologies": [ "Machine learning anomaly detector", "AI training system" ], "technologyProperties": { "training": "Trained on known fraudulent vs. legitimate data", "detection": "Identifies unusual patterns", "adaptation": "Learns from new fraud types" } }, "minimal-rules": { "technologies": [ "Required field validator", "Format checker" ], "technologyProperties": { "validation": "Only basic required field checks", "leniency": "Accepts plausible but questionable data", "trust": "Relies on enumerator competence" } }, "no-rules": { "technologies": [ "No automated validation", "Direct submission" ], "technologyProperties": { "validation": "None", "trust": "Complete trust in enumerator", "risk": "High fraud risk" } } }, "prefillFrom": null, "briefSection": "Data integrity", "text": "What automated validation rules do you currently apply to impact data?", "ngoText": "What automated validation rules do you currently apply to impact data?" }, { "id": "external-verification-proof", "type": "select", "options": [ { "label": "Third-party digital signature on verification report", "value": "digital-signature" }, { "label": "Photo/video evidence with metadata proof", "value": "photo-evidence" }, { "label": "Beneficiary attestation (signed consent to impact claim)", "value": "beneficiary-attestation" }, { "label": "automated rules with automatic payout on verification", "value": "smart-contract" }, { "label": "Simple text documentation (minimal proof)", "value": "text-documentation" } ], "propertyMapping": { "digital-signature": { "technologies": [ "Digital signature module", "Certificate authority" ], "technologyProperties": { "signature": "Third-party signs verification report", "verification": "Public key verification", "nonRepudiation": "Third-party cannot deny verification" } }, "photo-evidence": { "technologies": [ "Photo capture with metadata", "Geolocation and timestamp" ], "technologyProperties": { "capture": "Photo with GPS and timestamp metadata", "analysis": "AI analysis to verify photo authenticity", "proof": "Cryptographic hash of photo" } }, "beneficiary-attestation": { "technologies": [ "Beneficiary signature capture", "Consent interface" ], "technologyProperties": { "attestation": "Beneficiary signs verification document", "authenticity": "Digital signature or biometric", "dispute": "Beneficiary can dispute if falsified" } }, "smart-contract": { "technologies": [ "Automated verification oracle", "Automated payout" ], "technologyProperties": { "oracle": "Third party reports verification", "contract": "Automatedautomatically pays on verification", "security": "Blockchain ensures integrity" } }, "text-documentation": { "technologies": [ "Document storage", "Audit trail" ], "technologyProperties": { "documentation": "Text report of verification", "storage": "Secure storage with access control", "proof": "Minimal cryptographic proof" } } }, "prefillFrom": null, "briefSection": "Data integrity", "text": "What process would you need for documenting external verification of impact?", "ngoText": "What process would you need for documenting external verification of impact?" }, { "id": "offline-data-collection", "type": "select", "options": [ { "label": "Checksum verification (data integrity check on sync)", "value": "checksum" }, { "label": "Timestamp verification (validate data was collected offline)", "value": "timestamp" }, { "label": "Enumerator re-authentication (require auth on sync)", "value": "reauthentication" }, { "label": "Random verification subset (re-verify sample on sync)", "value": "random-subset" }, { "label": "No special verification for offline data", "value": "no-verification" } ], "propertyMapping": { "checksum": { "technologies": [ "Checksum calculation", "Integrity verification" ], "technologyProperties": { "checksum": "CRC or cryptographic hash of data", "verification": "Recomputed on sync and compared", "detection": "Detects corruption in transit" } }, "timestamp": { "technologies": [ "Offline timestamp module", "Server timestamp verification" ], "technologyProperties": { "timestamping": "Record when data created offline", "verification": "Compare against server clock on sync", "detection": "Catch backdated data" } }, "reauthentication": { "technologies": [ "Biometric or PIN re-authentication", "Session verification" ], "technologyProperties": { "authentication": "Require enumerator auth on sync", "verification": "Confirms enumerator ownership of data", "security": "Prevents unauthorized data submission" } }, "random-subset": { "technologies": [ "Random sampling system", "Verification callback" ], "technologyProperties": { "sampling": "10-20% sample of offline records", "reverification": "Call beneficiary to reverify", "resolution": "Investigate if discrepancy found" } }, "no-verification": { "technologies": [ "Direct sync", "No special checks" ], "technologyProperties": { "trust": "Trust offline data as-is", "risk": "Offline data may be tampered", "efficiency": "Faster sync" } } }, "prefillFrom": null, "briefSection": "Data integrity", "text": "How do you currently verify offline-collected data upon sync?", "ngoText": "How do you currently verify offline-collected data upon sync?" }, { "id": "compliance-reporting", "type": "select", "options": [ { "label": "Raw data export with full audit trail", "value": "raw-with-audit" }, { "label": "Aggregate statistics with privacy protection", "value": "aggregate-stats" }, { "label": "Digitally-backed verifiable reports", "value": "blockchain-reports" }, { "label": "Third-party certified reports", "value": "certified-reports" }, { "label": "Simple CSV export (minimal compliance)", "value": "simple-csv" } ], "propertyMapping": { "raw-with-audit": { "technologies": [ "Data export tool", "Audit trail attachment" ], "technologyProperties": { "export": "Raw data with all fields", "auditTrail": "Complete change history included", "format": "JSON or CSV with metadata" } }, "aggregate-stats": { "technologies": [ "Aggregate query engine", "Privacy filter" ], "technologyProperties": { "aggregation": "Counts, sums, averages", "privacy": "No individual records exposed", "compliance": "GDPR/HIPAA compliant" } }, "blockchain-reports": { "technologies": [ "Blockchain reporting service", "Verifiable report generator" ], "technologyProperties": { "anchoring": "Report hash anchored to blockchain", "verification": "Anyone can verify report integrity", "immutability": "Report cannot be modified" } }, "certified-reports": { "technologies": [ "Third-party auditor", "Report certification" ], "technologyProperties": { "auditor": "Independent third-party certifies report", "certification": "Digital signature of auditor", "trust": "High trust in report accuracy" } }, "simple-csv": { "technologies": [ "CSV export tool", "Basic filtering" ], "technologyProperties": { "format": "Comma-separated values", "security": "Basic encryption only", "compliance": "Minimal compliance features" } } }, "prefillFrom": null, "briefSection": "Reporting and audit", "text": "What are your impact data reporting requirements from donors and regulators?", "ngoText": "What are your impact data reporting requirements from donors and regulators?" } ], "complexityFactors": { "relationships": 2, "operationalChange": 2, "dataCompliance": 1 }, "suggestedCriteria": [ { "id": "SC-C044-IMMUT", "name": "Data Immutability Guarantees", "description": "This measures how strongly the solution guarantees that impact data cannot be altered after recording. Donors need confidence that reported numbers reflect actual activities.", "weight": 0.3, "ratingGuide": { "5": "Cryptographic immutability with public verification. Any stakeholder can independently verify data hasn't been altered. Anchored to public blockchain.", "4": "Cryptographic hashing with tamper-evident storage. Alterations detectable through hash chain verification.", "3": "Append-only ledger with access-controlled modifications. Audit trail captures all changes but relies on system integrity.", "2": "Standard database with change logging. Modifications tracked but logs could theoretically be altered by administrators.", "1": "Standard database with no immutability guarantees. Data can be modified without trace." } }, { "id": "SC-C044-VERIFY", "name": "Independent Verification Mechanisms", "description": "Can donors, evaluators, or third parties independently verify impact claims without relying on the reporting organisation's systems?", "weight": 0.25, "ratingGuide": { "5": "Third-party verification built in \u2014 attestation framework for independent evaluators. Donors can verify claims using public proofs without organisation involvement.", "4": "Independent verification portal. Evaluators can cross-reference claims against recorded data. Limited to authorised verifiers.", "3": "Audit export with integrity proofs. Third parties can verify exports but cannot independently query the source system.", "2": "Standard audit reports generated by the system. Verification depends on trust in the reporting organisation.", "1": "Self-reported impact data with no independent verification capability." } }, { "id": "SC-C044-INTEGRATE", "name": "M&E System Integration", "description": "How well does the solution integrate with existing monitoring and evaluation tools (data collection, health information and reporting dashboards)?", "weight": 0.2, "ratingGuide": { "5": "Native connectors for major M&E platforms. Automated data flow from collection to blockchain-secured storage.", "4": "API integrations with major M&E tools. Supports automated data ingestion. Some manual configuration needed.", "3": "Standard APIs available. Integration with M&E tools possible but requires custom development.", "2": "CSV/spreadsheet import/export. Manual data transfer between M&E tools and the blockchain layer.", "1": "Standalone system. No integration capability. Requires duplicate data entry." } }, { "id": "SC-C044-COSTEFF", "name": "Cost Per Verified Data Point", "description": "This measures the total cost of securing and verifying each data point relative to programme budgets. Impact verification must not consume disproportionate resources.", "weight": 0.15, "ratingGuide": { "5": "Negligible per-transaction cost. Designed for high-volume humanitarian data. Free or near-free verification queries.", "4": "Low per-transaction cost suitable for large M&E datasets. Predictable pricing model.", "3": "Moderate cost. Affordable for medium-scale programmes. May require selective data recording for cost control.", "2": "Per-transaction fees that add up at scale. Cost-prohibitive for small programmes or high-frequency data.", "1": "High infrastructure and per-transaction costs. Only viable for large, well-funded programmes." } }, { "id": "SC-C044-DONOR", "name": "Donor Reporting Compatibility", "description": "Does the solution produce outputs compatible with major donor reporting requirements (USAID, DFID/FCDO, EU, UN)?", "weight": 0.1, "ratingGuide": { "5": "Pre-built report templates for major donors. IATI standard support. Automated reporting with blockchain-verified integrity stamps.", "4": "Configurable reporting aligned with major donor formats. IATI export available. Verification proofs attachable to reports.", "3": "Standard reporting with customisable templates. Manual alignment with donor formats. Integrity proofs available on request.", "2": "Basic reporting output. Donor format compliance requires manual reformatting.", "1": "No reporting features. Data must be manually extracted and formatted for donor reporting." } } ], "procurement": { "marketMaturity": "emerging", "primaryMode": "rfq", "alternativeModes": [ "off-the-shelf" ], "reasoning": "Impact data integrity products exist with growing maturity.", "exampleProductCategories": [ "impact-data-platform", "m-and-e-saas" ], "partnerChannels": [], "lastReviewed": "2026-05-01" } }, { "id": "UC-C-045", "name": "Consent management and audit trails", "category": "C", "subcategory": "Data Governance", "description": "Record what each person agreed to, when and in what form, so you can prove it later and apply any change they make across every system.", "bCriteria": [ "B1", "B3", "B6" ], "requiredComponents": [ { "component": "consent-management", "description": "Consent record system" }, { "component": "record-keeping-platform", "description": "Immutable consent ledger" }, { "component": "audit-mechanism", "description": "Consent audit trail" }, { "component": "access-control", "description": "Consent-based data access" } ], "conditionalComponents": [ { "component": "credential-issuance", "condition": "If consent proof credentials needed" }, { "component": "privacy-tech", "condition": "For privacy-preserving consent verification" } ], "crossCategoryDependencies": [ "UC-B-037 for consent credentials" ], "p2TriggerConditions": { "description": "Activated when P2 shows data sensitivity + consent complexity + multi-org sharing", "rangeSignals": [ "dataSensitivity >= high", "consentComplexity >= true", "multiOrgSharing >= true" ] }, "contextFieldsTemplate": [ { "field": "beneficiaries", "source": "P2 programme scale", "description": "Beneficiaries with consent" }, { "field": "dataTypes", "source": "P2 data types", "description": "Types of consented data" }, { "field": "sharingOrganisations", "source": "P0 partnerships", "description": "Data sharing partners" }, { "field": "consentGranularity", "source": "P2 data governance", "description": "Consent specificity" } ], "implementationComplexity": "medium", "examples": { "note": "GDPR consent management, humanitarian data ethics", "references": [ { "name": "EU GDPR Article 6-8 - Lawfulness and Consent Requirements", "url": "https://gdpr-info.eu/articles/lawfulness/", "solved": "Legal framework for valid consent, withdrawal rights, and granular consent management in data processing" }, { "name": "WHO Guidance on Informed Consent for Health Research", "url": "https://www.who.int/publications/m/item/guidance-on-informed-consent-for-health-related-research", "solved": "International standards for ethical consent in health research with special provisions for vulnerable populations" }, { "name": "Hyperledger Indy Verifiable Credentials for Consent", "url": "https://www.hyperledger.org/use/indy", "solved": "Blockchain-based verifiable consent credentials with immutable audit trails and self-sovereign identity" } ] }, "solutionQuestions": [ { "id": "consent-granularity-level", "type": "select", "options": [ { "label": "Broad: single consent for all data use", "value": "broad-consent" }, { "label": "Per-purpose: separate consent for each use (clinical, research, reporting)", "value": "per-purpose" }, { "label": "Per-data-type: consent for each data category (name, health, location)", "value": "per-datatype" }, { "label": "Per-field: granular consent for each individual data field", "value": "per-field" }, { "label": "Dynamic: just-in-time consent requests at point of use", "value": "dynamic" } ], "propertyMapping": { "broad-consent": { "technologies": [ "Simple consent form", "Consent database" ], "technologyProperties": { "complexity": "Simple single form", "withdrawal": "Withdraw all consent at once", "default": "Standard for most programs" } }, "per-purpose": { "technologies": [ "Purpose-based consent engine", "Use case registry" ], "technologyProperties": { "purposes": "Clinical care, research, public health", "granularity": "Separate consent per purpose", "withdrawal": "Can withdraw per-purpose" } }, "per-datatype": { "technologies": [ "Data classification system", "Multi-consent interface" ], "technologyProperties": { "categories": "Health, location, contact, demographic", "granularity": "Consent per category", "flexibility": "Balance between control and complexity" } }, "per-field": { "technologies": [ "Field-level consent system", "Granular consent UI" ], "technologyProperties": { "granularity": "Individual FHIR elements", "control": "Maximum beneficiary control", "complexity": "Very complex UI/UX" } }, "dynamic": { "technologies": [ "Just-in-time consent platform", "Real-time consent requests" ], "technologyProperties": { "timing": "Ask at point of data use", "frequency": "May ask multiple times", "responsiveness": "Synchronous or asynchronous" } } }, "prefillFrom": null, "briefSection": "Consent management", "text": "At what level of detail do you obtain consent from beneficiaries?", "ngoText": "At what level of detail do you obtain consent from beneficiaries?" }, { "id": "consent-withdrawal-mechanism", "type": "select", "options": [ { "label": "Self-service portal (beneficiary withdraws directly)", "value": "self-service" }, { "label": "Phone or in-person request (staff processes withdrawal)", "value": "phone-inperson" }, { "label": "Automatic expiry (consent expires on date)", "value": "auto-expiry" }, { "label": "Hard-stop withdrawal (retroactive effect on past access)", "value": "hard-stop" }, { "label": "No withdrawal (consent cannot be withdrawn once given)", "value": "no-withdrawal" } ], "propertyMapping": { "self-service": { "technologies": [ "Beneficiary portal", "Withdrawal interface" ], "technologyProperties": { "access": "24/7 withdrawal capability", "immediacy": "Effective immediately", "confirmation": "Confirmation email sent" } }, "phone-inperson": { "technologies": [ "Call center integration", "Withdrawal processing" ], "technologyProperties": { "method": "Phone call or in-person visit", "verification": "Identity verification required", "timeline": "24-48 hour processing" } }, "auto-expiry": { "technologies": [ "Consent expiry scheduler", "Automatic deactivation" ], "technologyProperties": { "expiry": "Consent automatically expires on date", "renewal": "Can renew before expiry", "passive": "Beneficiary doesn't need to act" } }, "hard-stop": { "technologies": [ "Retroactive withdrawal system", "Historical access revoker" ], "technologyProperties": { "effect": "Withdraws from retroactively effective date", "dataDisposal": "Require deletion of accessed copies", "legality": "Not always legally permissible" } }, "no-withdrawal": { "technologies": [ "Immutable consent", "One-time consent" ], "technologyProperties": { "flexibility": "None (commitment)", "useCase": "Legal requirements or permanent programs", "risk": "Reduces beneficiary autonomy" } } }, "prefillFrom": null, "briefSection": "Consent management", "text": "What is your current approach to consent withdrawal in your programmes?", "ngoText": "What is your current approach to consent withdrawal in your programmes?" }, { "id": "consent-audit-logging", "type": "select", "options": [ { "label": "Permanent tamper-proof digital ledger consent ledger", "value": "blockchain-consent" }, { "label": "Append-only database (no modification possible)", "value": "append-only-db" }, { "label": "Digital signatures on consent records", "value": "digital-signatures" }, { "label": "Standard access logs (can be modified)", "value": "standard-logs" }, { "label": "No specific consent audit (separate from data access)", "value": "no-audit" } ], "propertyMapping": { "blockchain-consent": { "technologies": [ "Blockchain consent ledger", "Smart contract consent tracking" ], "technologyProperties": { "immutability": "Cannot modify consent history", "transparency": "Anyone can verify consent", "permanence": "Permanent record" } }, "append-only-db": { "technologies": [ "Append-only database", "Log-structured storage" ], "technologyProperties": { "writes": "Only appends; no overwrites", "history": "Complete consent history preserved", "integrity": "Cannot retroactively modify" } }, "digital-signatures": { "technologies": [ "Digital signature module", "PKI infrastructure" ], "technologyProperties": { "signing": "Consent record signed by consenting party", "verification": "Signature verifiable with public key", "nonRepudiation": "Cannot deny consent" } }, "standard-logs": { "technologies": [ "Standard audit logging", "Log storage" ], "technologyProperties": { "logging": "Consent recorded in standard audit log", "modification": "Can be modified by administrators", "risk": "Lower integrity guarantee" } }, "no-audit": { "technologies": [ "No specific consent audit", "Data access logs only" ], "technologyProperties": { "tracking": "Consent not specifically logged", "verification": "Difficult to prove consent given", "limitation": "Poor for compliance" } } }, "prefillFrom": null, "briefSection": "Reporting and audit", "text": "How do you currently track and log consent decisions?", "ngoText": "How do you currently track and log consent decisions?" }, { "id": "consent-documentation", "type": "select", "options": [ { "label": "Video recording of consent conversation", "value": "video-recording" }, { "label": "Digital signature on consent form", "value": "digital-signature" }, { "label": "Consent form with witness signatures", "value": "witnessed-consent" }, { "label": "Simple checkbox consent (no specific evidence)", "value": "checkbox-consent" }, { "label": "Implicit consent (no documentation)", "value": "implicit-consent" } ], "propertyMapping": { "video-recording": { "technologies": [ "Video capture and encryption", "Secure video storage" ], "technologyProperties": { "recording": "Encrypted video of consent discussion", "proof": "Highest evidence of consent", "privacy": "Video storage itself privacy risk" } }, "digital-signature": { "technologies": [ "Digital signature capture", "PKI infrastructure" ], "technologyProperties": { "signature": "Beneficiary signs electronically", "verification": "Signature verifiable", "evidence": "High-quality legal evidence" } }, "witnessed-consent": { "technologies": [ "Witness signature capture", "Consent form routing" ], "technologyProperties": { "witness": "Independent witness signs", "evidence": "Third-party attestation", "formality": "High-formality consent" } }, "checkbox-consent": { "technologies": [ "Web form with checkbox", "Timestamp logging" ], "technologyProperties": { "evidence": "Checkbox click with timestamp", "documentation": "Minimal but recorded", "legalStanding": "May be insufficient in some jurisdictions" } }, "implicit-consent": { "technologies": [ "Service enrollment", "Implied consent" ], "technologyProperties": { "documentation": "None", "evidence": "Enrollment in service implies consent", "legality": "Not acceptable in many jurisdictions" } } }, "prefillFrom": null, "briefSection": "Consent management", "text": "What documentation format and medium do you currently use for consent?", "ngoText": "What documentation format and medium do you currently use for consent?" }, { "id": "consent-for-minors", "type": "select", "options": [ { "label": "Parental/guardian consent required for all minors", "value": "parental-consent" }, { "label": "Minor assent + guardian consent (dual agreement)", "value": "dual-consent" }, { "label": "Mature minor standard (minor can consent if mature enough)", "value": "mature-minor" }, { "label": "Age-based threshold (consent at specific age)", "value": "age-threshold" }, { "label": "No specific minor protections (same as adults)", "value": "no-minor-protection" } ], "propertyMapping": { "parental-consent": { "technologies": [ "Guardian identification system", "Parental consent form" ], "technologyProperties": { "requirement": "Parent/guardian must consent", "verification": "Parent identity verified", "scope": "Guardian controls all consent decisions" } }, "dual-consent": { "technologies": [ "Minor assent interface", "Guardian consent form" ], "technologyProperties": { "minorInput": "Child signs assent form", "guardianInput": "Guardian also consents", "understanding": "Both understand implications" } }, "mature-minor": { "technologies": [ "Maturity assessment tool", "Conditional consent" ], "technologyProperties": { "assessment": "Social worker assesses maturity", "criteria": "Intelligence, understanding of implications", "flexibility": "Allows some minors to self-consent" } }, "age-threshold": { "technologies": [ "Age verification system", "Age-based consent logic" ], "technologyProperties": { "threshold": "Automatic consent capacity at age X (e.g., 16)", "transition": "Clear age boundary", "simplicity": "Easy to implement" } }, "no-minor-protection": { "technologies": [ "Standard consent system", "No special minor rules" ], "technologyProperties": { "protection": "None", "risk": "Minors may not understand implications", "legal": "May violate child protection laws" } } }, "prefillFrom": null, "briefSection": "Consent management", "text": "What is your current process for obtaining consent from minors?", "ngoText": "What is your current process for obtaining consent from minors?" }, { "id": "third-party-data-sharing-consent", "type": "select", "options": [ { "label": "Separate explicit consent for each third-party recipient", "value": "per-recipient-consent" }, { "label": "Category-based consent (consent for 'research partners' as group)", "value": "category-consent" }, { "label": "Broad consent (all third-party sharing approved in one consent)", "value": "broad-thirdparty" }, { "label": "Anonymous/de-identified (no consent needed)", "value": "deidentified-no-consent" }, { "label": "No third-party sharing (data stays internal)", "value": "no-sharing" } ], "propertyMapping": { "per-recipient-consent": { "technologies": [ "Recipient-specific consent form", "Recipient registry" ], "technologyProperties": { "specificity": "Specific organization name and purpose", "control": "Maximum beneficiary control", "complexity": "Consent for each new recipient" } }, "category-consent": { "technologies": [ "Category definition system", "Category-based consent" ], "technologyProperties": { "categories": "Types of recipients (e.g., 'approved research institutions')", "flexibility": "Can add recipients in category without re-consent", "clarity": "Category definition must be clear" } }, "broad-thirdparty": { "technologies": [ "Broad third-party consent form", "Recipient list" ], "technologyProperties": { "scope": "Blanket approval for third-party sharing", "simplicity": "Simple for beneficiary", "control": "Less control for beneficiary" } }, "deidentified-no-consent": { "technologies": [ "De-identification engine", "Privacy-preserving disclosure" ], "technologyProperties": { "deidentification": "Identifiers irreversibly removed", "legalBasis": "De-identified data may not need consent", "privacy": "Beneficiary privacy protected" } }, "no-sharing": { "technologies": [ "Data containment policy", "No API for third-party access" ], "technologyProperties": { "sharing": "Prohibited", "privacy": "Maximum privacy", "limitation": "Cannot share data even with consent" } } }, "prefillFrom": null, "briefSection": "Consent management", "text": "What third parties do you currently share beneficiary data with, and what consent do you have?", "ngoText": "What third parties do you currently share beneficiary data with, and what consent do you have?" }, { "id": "consent-breach-notification", "type": "select", "options": [ { "label": "Mandatory beneficiary notification (immediately)", "value": "immediate-notification" }, { "label": "Delayed notification (only after investigation)", "value": "delayed-notification" }, { "label": "Notification if data actually misused (no notification for breach alone)", "value": "conditional-notification" }, { "label": "No notification obligation", "value": "no-notification" }, { "label": "Notification to authorities only (not beneficiary)", "value": "authority-notification" } ], "propertyMapping": { "immediate-notification": { "technologies": [ "Breach detection system", "Notification service" ], "technologyProperties": { "detection": "Breach identified", "timing": "Notification sent immediately", "channels": "Email, SMS, in-person", "transparency": "Full disclosure of breach" } }, "delayed-notification": { "technologies": [ "Incident investigation system", "Delayed notification" ], "technologyProperties": { "investigation": "Full investigation before notification", "timeline": "30-60 day investigation period", "communication": "Notification after investigation complete" } }, "conditional-notification": { "technologies": [ "Breach impact assessment", "Conditional notification logic" ], "technologyProperties": { "condition": "Only notify if data actually misused", "assessment": "Determine likelihood of harm", "notification": "If harm likely, notify beneficiary" } }, "no-notification": { "technologies": [ "No notification system", "Breach logging only" ], "technologyProperties": { "notification": "Beneficiary not notified", "logging": "Breach logged internally", "risk": "Beneficiary unaware of breach" } }, "authority-notification": { "technologies": [ "Regulatory notification system", "Authority reporting" ], "technologyProperties": { "authorities": "Data protection authority, regulators", "beneficiary": "Not notified", "transparency": "Public record of breaches" } } }, "prefillFrom": null, "briefSection": "Reporting and audit", "text": "What is your current process for handling and notifying beneficiaries of data breaches?", "ngoText": "What is your current process for handling and notifying beneficiaries of data breaches?" } ], "complexityFactors": { "relationships": 2, "operationalChange": 3, "dataCompliance": 4 }, "suggestedCriteria": [ { "id": "SC-C045-GRANULAR", "name": "Consent Granularity and Flexibility", "description": "How granular is the consent model? Can beneficiaries give consent per data type, per purpose, per recipient, and per time period?", "weight": 0.3, "ratingGuide": { "5": "Multi-dimensional consent \u2014 per data type, per purpose, per recipient, with time limits. Supports conditional consent and automatic expiry. Beneficiary controls all dimensions.", "4": "Consent per data type and per recipient. Time-limited consent supported. Most humanitarian consent scenarios covered.", "3": "Consent per service or programme. Basic recipient controls. Manual expiry management.", "2": "Binary consent per organisation \u2014 all or nothing for each partner. No per-purpose or per-data-type controls.", "1": "Single blanket consent for all data uses. No granularity or time limits." } }, { "id": "SC-C045-AUDIT", "name": "Consent Audit Trail Completeness", "description": "Does the system maintain a complete, tamper-proof record of all consent events (grants, modifications, withdrawals, and access based on consent)?", "weight": 0.25, "ratingGuide": { "5": "Immutable audit trail of every consent event with cryptographic timestamps. Records who accessed data under which consent. Independently verifiable.", "4": "Complete consent event logging with tamper-evident storage. Access events linked to consent grants.", "3": "Consent events logged with standard timestamps. Access logging separate but linkable.", "2": "Consent grants and withdrawals logged. Access events not linked to consent records.", "1": "Basic consent recording with no audit trail of consent-based data access." } }, { "id": "SC-C045-WITHDRAW", "name": "Consent Withdrawal Effectiveness", "description": "When consent is withdrawn, how quickly and completely is data access actually revoked? Can the system prove that no access occurred after withdrawal?", "weight": 0.2, "ratingGuide": { "5": "Instant revocation with cryptographic proof of non-access after withdrawal. Automated downstream propagation to all data consumers.", "4": "Near-instant revocation across the system. Propagation to downstream consumers within hours. Audit proof of revocation timing.", "3": "Revocation effective within 24 hours. Manual verification that downstream consumers complied.", "2": "Revocation recorded but enforcement depends on each data consumer checking consent status. No automated propagation.", "1": "Withdrawal recorded but no automated enforcement. Data consumers may continue access until manually notified." } }, { "id": "SC-C045-COMPLIANCE", "name": "Regulatory Framework Alignment", "description": "Does the solution align with relevant data protection regulations (GDPR, national data protection laws) and humanitarian data standards?", "weight": 0.15, "ratingGuide": { "5": "GDPR-compliant by design with support for multiple regulatory frameworks. Humanitarian data ethics standards (OCHA, IASC) built in.", "4": "GDPR-aligned with configurable compliance rules. Awareness of humanitarian data protection principles.", "3": "Standard data protection features. Compliance requires configuration and policy alignment.", "2": "Basic data protection. Regulatory compliance requires significant customisation.", "1": "No regulatory awareness. Compliance is entirely the organisation's responsibility to configure." } }, { "id": "SC-C045-UX", "name": "Beneficiary Consent Experience", "description": "How accessible is the consent process for beneficiaries with limited literacy, limited technology access, or language barriers?", "weight": 0.1, "ratingGuide": { "5": "Multi-modal consent (voice, visual, written) in multiple languages. Designed for low-literacy populations. Mobile-first. Tested with humanitarian beneficiary populations.", "4": "Multi-language support with visual consent workflows. Mobile-friendly. Accessible to moderately literate populations.", "3": "Standard digital consent forms. Multi-language support available. Requires basic literacy and device access.", "2": "Text-based consent forms. Single language or limited translation. Requires literacy and device access.", "1": "Complex digital consent process. Inaccessible to populations with limited literacy or technology access." } } ], "procurement": { "marketMaturity": "mature", "primaryMode": "off-the-shelf", "alternativeModes": [ "rfq" ], "reasoning": "Consent management market is mature.", "exampleProductCategories": [ "consent-management-saas", "privacy-records-platform" ], "partnerChannels": [], "lastReviewed": "2026-05-01" } }, { "id": "UC-C-046", "name": "Inter-agency data sharing without centralisation", "category": "C", "subcategory": "Data Governance", "description": "Let several agencies share beneficiary data with each other without any one agency holding everything, and without one agency having to trust another.", "bCriteria": [ "B1", "B2", "B6" ], "requiredComponents": [ { "component": "interoperability-protocol", "description": "Decentralized data sharing protocol" }, { "component": "data-layer", "description": "Distributed data repositories" }, { "component": "encryption-privacy", "description": "Encrypted inter-agency data" }, { "component": "access-control", "description": "Granular access controls" } ], "conditionalComponents": [ { "component": "privacy-tech", "condition": "For privacy-preserving data queries" }, { "component": "consent-management", "condition": "For consent-based data access" } ], "crossCategoryDependencies": [ "UC-C-045 for consent audit" ], "p2TriggerConditions": { "description": "Activated when P2 shows multi-org data needs + no central authority + privacy concerns", "rangeSignals": [ "agencies >= 3+", "centralAuthority >= false", "privacyConcerns >= high" ] }, "contextFieldsTemplate": [ { "field": "agencies", "source": "P0 partnerships", "description": "Participating organisations" }, { "field": "dataTypes", "source": "P2 coordination needs", "description": "Data to be shared" }, { "field": "beneficiaries", "source": "P2 programmes", "description": "Shared beneficiaries" }, { "field": "governance", "source": "P0 agreements", "description": "Data sharing governance" } ], "implementationComplexity": "high", "examples": { "note": "Humanitarian data exchange, decentralized coordination", "references": [ { "name": "International Data Spaces (IDS) - Secure Data Sharing Standard", "url": "https://www.internationaldataspaces.org/", "solved": "Framework for peer-to-peer data sharing with sovereignty, governance, and trust mechanisms without centralisation" }, { "name": "OPAL (Open Platform for Applied Learning) - Federated Query Protocol", "url": "https://opal.opalytics.com/", "solved": "Federated query engine allowing analytics without centralising sensitive data" }, { "name": "Humanitarian Data Exchange (HDX) - Decentralized Data Sharing", "url": "https://data.humdata.org/", "solved": "Standard protocols for humanitarian agencies to share data with attribution and usage tracking without centralised database" } ] }, "solutionQuestions": [ { "id": "data-sharing-architecture", "type": "select", "options": [ { "label": "Through a central coordinating body that manages shared data", "value": "through-a-central-coordinating-body-that" }, { "label": "Direct sharing between organisations (bilateral agreements)", "value": "direct-sharing-between-organisations-bil" }, { "label": "Each organisation publishes data that others can access", "value": "each-organisation-publishes-data-that-ot" }, { "label": "Periodic manual sharing (email, USB, spreadsheets)", "value": "periodic-manual-sharing-email-usb-spread" }, { "label": "Combination of approaches depending on the data type", "value": "combination-of-approaches-depending-on-t" }, { "label": "No data sharing currently, each organisation works independently", "value": "no-data-sharing-currently-each-organisat" } ], "propertyMapping": { "federated-query": { "technologies": [ "Federated query engine", "Distributed query processor" ], "technologyProperties": { "queryType": "Query runs across multiple databases", "integration": "Query coordinator at requesting agency", "dataLocation": "Data remains at source", "latency": "Higher latency (multiple queries)" } }, "peer-to-peer": { "technologies": [ "P2P protocol", "Direct agency connectors" ], "technologyProperties": { "connections": "Direct point-to-point links", "scalability": "O(n\u00b2) connections for n agencies", "simplicity": "Simple but doesn't scale" } }, "data-mesh": { "technologies": [ "Data domain platforms", "Standard domain APIs" ], "technologyProperties": { "domains": "Each agency owns data domain", "api": "Standard REST/GraphQL API per domain", "discovery": "Service registry for domain discovery", "governance": "Federated governance model" } }, "blockchain-registry": { "technologies": [ "Blockchain record locator", "Smart contracts for directory" ], "technologyProperties": { "registry": "Decentralized directory of data", "discovery": "Find data location on blockchain", "immutability": "Registry cannot be censored" } }, "hybrid-mesh": { "technologies": [ "Lightweight registry", "P2P query network" ], "technologyProperties": { "registry": "Minimal central metadata only", "dataLocations": "Direct P2P for data sharing", "scalability": "Balances decentralization and efficiency" } } }, "prefillFrom": null, "briefSection": "Data architecture", "text": "What data systems do you currently use for sharing within and across organizations?", "ngoText": "What data systems do you currently use for sharing within and across organizations?", "question": "How do organisations in your context currently share data with each other?" }, { "id": "access-control-shared-data", "type": "select", "options": [ { "label": "Source agency controls (data owner decides who can access)", "value": "source-control" }, { "label": "Recipient agency controls (requester authenticated locally)", "value": "recipient-control" }, { "label": "Shared governance (both agencies must approve)", "value": "shared-governance" }, { "label": "Beneficiary-mediated (beneficiary grants access)", "value": "beneficiary-mediated" }, { "label": "No access control (open to all agencies)", "value": "no-access-control" } ], "propertyMapping": { "source-control": { "technologies": [ "Data provider access policy", "Policy enforcement at source" ], "technologyProperties": { "policy": "Data owner (source agency) defines access", "enforcement": "Source agency enforces policy", "flexibility": "Only source can grant access" } }, "recipient-control": { "technologies": [ "Local access control", "Recipient authentication" ], "technologyProperties": { "control": "Recipient agency manages their staff's access", "authentication": "Local credentials required", "limitation": "Source doesn't control who sees data" } }, "shared-governance": { "technologies": [ "Multi-party approval system", "Bilateral authorization" ], "technologyProperties": { "approval": "Both agencies must agree", "governance": "Shared decision-making", "complexity": "Slower approval process" } }, "beneficiary-mediated": { "technologies": [ "Beneficiary consent platform", "Delegated access tokens" ], "technologyProperties": { "consent": "Beneficiary grants access to agencies", "tokens": "Time-limited access tokens", "control": "Beneficiary controls access" } }, "no-access-control": { "technologies": [ "Open data sharing", "No restrictions" ], "technologyProperties": { "access": "Any agency can access", "privacy": "High privacy risk", "useCase": "Only for aggregate/de-identified data" } } }, "prefillFrom": null, "briefSection": "Access control", "text": "What access control model do you currently use for shared data?", "ngoText": "What access control model do you currently use for shared data?" }, { "id": "data-sovereignty-residence", "type": "select", "options": [ { "label": "Data stays in country of origin (no cross-border export)", "value": "domestic-only" }, { "label": "Cross-border allowed but with explicit consent per country", "value": "cross-border-consent" }, { "label": "Regional data sharing with regional governance", "value": "regional-sharing" }, { "label": "Global sharing with local copies in-country", "value": "global-with-local" }, { "label": "Data mobility: beneficiary controls location", "value": "beneficiary-controlled" } ], "propertyMapping": { "domestic-only": { "technologies": [ "Geofencing control", "Data residency enforcement" ], "technologyProperties": { "restriction": "No cross-border data transfer", "enforcement": "Technical control preventing export", "scope": "Single country only" } }, "cross-border-consent": { "technologies": [ "Consent management with jurisdiction", "Cross-border notification" ], "technologyProperties": { "consent": "Explicit consent for each cross-border transfer", "notification": "Beneficiary notified of location change", "compliance": "Per-jurisdiction data law" } }, "regional-sharing": { "technologies": [ "Regional governance framework", "Regional data agreements" ], "technologyProperties": { "scope": "Regional economic community (e.g., ECOWAS)", "sharing": "Data shared within region", "governance": "Regional oversight body" } }, "global-with-local": { "technologies": [ "Local cache system", "Distributed storage" ], "technologyProperties": { "global": "Data shared globally", "local": "Local copy kept in-country", "compliance": "Meets data residency law" } }, "beneficiary-controlled": { "technologies": [ "Beneficiary location preferences", "Portable data" ], "technologyProperties": { "preference": "Beneficiary specifies where data stored", "portability": "Beneficiary can move data", "autonomy": "Maximum control" } } }, "prefillFrom": null, "briefSection": "Interoperability", "text": "What are your data residency and sovereignty requirements?", "ngoText": "What are your data residency and sovereignty requirements?" }, { "id": "trust-framework", "type": "select", "options": [ { "label": "Government-backed accreditation (agencies licensed by government)", "value": "govt-accredited" }, { "label": "NGO/sector coalition (voluntary peer governance)", "value": "coalition-governance" }, { "label": "digital trust (digitally verified, no central authority)", "value": "blockchain-trust" }, { "label": "Mutual agreements (bilateral or trilateral contracts)", "value": "bilateral-agreements" }, { "label": "No formal trust framework (trust based on relationships)", "value": "no-framework" } ], "propertyMapping": { "govt-accredited": { "technologies": [ "Government licensing system", "Accreditation verification" ], "technologyProperties": { "accreditation": "Government-issued credentials", "standards": "Government-defined data standards", "oversight": "Government agency oversight" } }, "coalition-governance": { "technologies": [ "Coalition standards body", "Peer certification" ], "technologyProperties": { "governance": "Sector-led governance body", "standards": "Industry standards", "certification": "Peer-reviewed certification" } }, "blockchain-trust": { "technologies": [ "Blockchain trust ledger", "Automated governance" ], "technologyProperties": { "verification": "Cryptographic verification", "decentralization": "No central authority", "immutability": "Trust decisions recorded permanently" } }, "bilateral-agreements": { "technologies": [ "Contract management", "Bilateral MOU system" ], "technologyProperties": { "governance": "Pair-wise agreements", "scalability": "Doesn't scale (O(n\u00b2) agreements)", "flexibility": "Customized per relationship" } }, "no-framework": { "technologies": [ "No formal system", "Relationship-based" ], "technologyProperties": { "trust": "Based on reputation and relationships", "formality": "Informal", "risk": "No recourse if trust violated" } } }, "prefillFrom": null, "briefSection": "Interoperability", "text": "What agreements or frameworks govern data sharing between your agencies?", "ngoText": "What agreements or frameworks govern data sharing between your agencies?" }, { "id": "query-protocol-standard", "type": "select", "options": [ { "label": "health data standard (health data standard with REST)", "value": "fhir-api" }, { "label": "flexible query (flexible query language)", "value": "graphql" }, { "label": "semantic query (semantic web standard)", "value": "sparql" }, { "label": "Custom protocol (agency-specific API)", "value": "custom-protocol" }, { "label": "Manual data export (periodic file exchange)", "value": "manual-export" } ], "propertyMapping": { "fhir-api": { "technologies": [ "FHIR API server", "REST endpoints" ], "technologyProperties": { "standard": "HL7 FHIR R4", "scope": "Health data focused", "adoption": "Wide adoption in health sector" } }, "graphql": { "technologies": [ "GraphQL server", "Query executor" ], "technologyProperties": { "flexibility": "Query any fields needed", "complexity": "Complex query language", "efficiency": "Efficient data retrieval" } }, "sparql": { "technologies": [ "SPARQL endpoint", "RDF knowledge graph" ], "technologyProperties": { "standard": "W3C semantic web standard", "semantics": "Rich semantic queries", "adoption": "Limited NGO adoption" } }, "custom-protocol": { "technologies": [ "Custom REST API", "Agency-specific design" ], "technologyProperties": { "flexibility": "Fully customized", "standardization": "No inter-agency standard", "integration": "Each agency integrates differently" } }, "manual-export": { "technologies": [ "Data export tool", "Secure file transfer" ], "technologyProperties": { "automation": "Manual and periodic", "frequency": "Daily or weekly batches", "realtime": "Not real-time" } } }, "prefillFrom": null, "briefSection": "Interoperability", "text": "How do other agencies currently access or query your shared data?", "ngoText": "How do other agencies currently access or query your shared data?" }, { "id": "data-quality-standards", "type": "select", "options": [ { "label": "Shared data standards (all agencies use same schema)", "value": "shared-standards" }, { "label": "Mapping between standards (each agency's format mapped to others)", "value": "mapping-layer" }, { "label": "Quality certification (agencies must meet quality baseline)", "value": "certification" }, { "label": "Consumer responsibility (receiving agency validates data)", "value": "consumer-validates" }, { "label": "No specific quality requirements", "value": "no-requirements" } ], "propertyMapping": { "shared-standards": { "technologies": [ "Unified data schema", "Validation against schema" ], "technologyProperties": { "schema": "Single standard (e.g., FHIR) for all", "validation": "Data validated against schema", "enforcement": "Mandatory schema adherence" } }, "mapping-layer": { "technologies": [ "Data transformation engine", "Schema mapping" ], "technologyProperties": { "mapping": "Automatic transformation between formats", "flexibility": "Each agency keeps own format", "accuracy": "Mapping may lose information" } }, "certification": { "technologies": [ "Data quality audit", "Certification system" ], "technologyProperties": { "baseline": "Minimum quality requirements", "audit": "Regular quality audits", "certification": "Public certification of quality" } }, "consumer-validates": { "technologies": [ "Validation framework at consumer", "Quality checking" ], "technologyProperties": { "responsibility": "Receiving agency validates", "trust": "Trust varies by source", "flexibility": "Different quality levels accepted" } }, "no-requirements": { "technologies": [ "No quality control", "Accept as-is" ], "technologyProperties": { "quality": "Highly variable", "risk": "Low-quality data may be used", "consequence": "Poor decision-making" } } }, "prefillFrom": null, "briefSection": "Data integrity", "text": "What data quality standards do you require from shared data sources?", "ngoText": "What data quality standards do you require from shared data sources?", "hidden": true }, { "id": "audit-trail-sharing", "type": "select", "options": [ { "label": "Source agency logs (data owner logs all access)", "value": "source-logging" }, { "label": "Distributed logging (each agency logs their accesses)", "value": "distributed-logging" }, { "label": "Shared digital audit (permanent tamper-proof audit trail)", "value": "blockchain-audit" }, { "label": "End-to-end encryption with access notifications", "value": "encryption-notification" }, { "label": "No specific audit for shared access", "value": "no-audit" } ], "propertyMapping": { "source-logging": { "technologies": [ "Data provider audit log", "Access logging at source" ], "technologyProperties": { "logging": "Source logs who accessed what", "transparency": "Requesting agency can see access log", "compliance": "High audit visibility" } }, "distributed-logging": { "technologies": [ "Independent audit logs", "Log correlation" ], "technologyProperties": { "logging": "Each agency logs their staff's accesses", "correlation": "Logs correlated to reconstruct query", "complexity": "More complex audit trail" } }, "blockchain-audit": { "technologies": [ "Blockchain access ledger", "Smart contract logging" ], "technologyProperties": { "logging": "All accesses recorded on blockchain", "immutability": "Cannot be modified", "transparency": "Both agencies can verify" } }, "encryption-notification": { "technologies": [ "E2E encryption with notifications", "Access alerts" ], "technologyProperties": { "notification": "Data requester sends alert to data owner", "logging": "Minimal server-side logging", "privacy": "Protects server from knowing content" } }, "no-audit": { "technologies": [ "No audit logging", "No access tracking" ], "technologyProperties": { "logging": "None", "accountability": "None", "risk": "No accountability for access" } } }, "prefillFrom": null, "briefSection": "Reporting and audit", "text": "How do you currently track who accessed shared data and when?", "ngoText": "How do you currently track who accessed shared data and when?" } ], "complexityFactors": { "relationships": 4, "operationalChange": 4, "dataCompliance": 4 }, "securityTier": "B", "suggestedCriteria": [ { "id": "SC-C046-DECENTRAL", "name": "Genuine Decentralisation", "description": "Does each agency retain full control of its own data while enabling shared queries? Or does 'decentralised' just mean distributed replicas of a central database?", "weight": 0.3, "ratingGuide": { "5": "True federated architecture \u2014 each agency hosts its own data node. Shared queries execute without data leaving the originating agency. No central data store.", "4": "Decentralised storage with each agency controlling its node. Shared data layer for metadata/indexes only. Data stays local for queries.", "3": "Distributed replicas with agency-level access controls. Data is replicated but access is partitioned.", "2": "Central platform with agency-level data partitions. Data is logically separated but physically centralised.", "1": "Centralised database with agency login accounts. All data stored and controlled by a single operator." } }, { "id": "SC-C046-QUERY", "name": "Cross-agency Query Capability", "description": "Agencies can run meaningful queries across datasets without accessing each other's raw data. For example, counting shared beneficiaries or aggregating outcomes.", "weight": 0.25, "ratingGuide": { "5": "Privacy-preserving queries (MPC, homomorphic encryption, or ZKP) compute aggregate answers across agencies without revealing individual records.", "4": "Federated queries with privacy controls. Aggregate results returned. Row-level data stays with originating agency.", "3": "Shared query interface with access controls. Agencies can query shared datasets but need pre-approved query templates.", "2": "Data must be exported and manually combined for cross-agency analysis. No live cross-agency querying.", "1": "No cross-agency query capability. Each agency's data is siloed." } }, { "id": "SC-C046-GOVERN", "name": "Data Sharing Governance Framework", "description": "Does the solution include built-in governance for data sharing agreements, access rules, and dispute resolution between agencies?", "weight": 0.2, "ratingGuide": { "5": "Built-in data sharing agreement management. Smart contract-enforced rules. Multi-party governance with dispute resolution. Audit trail of all sharing decisions.", "4": "Configurable sharing rules per agency pair. Agreement templates. Audit trail of sharing events.", "3": "Basic sharing rules configurable. Manual agreement management. Sharing events logged.", "2": "Sharing controlled by admin configuration. No agreement management features.", "1": "No governance features. Sharing is all-or-nothing with no configurable rules." } }, { "id": "SC-C046-STANDARDS", "name": "Humanitarian Data Standards Support", "description": "Does the solution support humanitarian data exchange standards (IATI, HDX, HXL) for interoperability between agencies using different systems?", "weight": 0.15, "ratingGuide": { "5": "Native support for IATI, HDX, and HXL standards. Automatic data harmonisation across different agency formats.", "4": "Supports major humanitarian data standards. Import/export in standard formats. Basic data harmonisation.", "3": "Standard data formats (JSON, CSV) with configurable mappings to humanitarian standards.", "2": "Proprietary data format with export to standard formats. Import requires custom mapping.", "1": "Proprietary format only. No humanitarian data standard support." } }, { "id": "SC-C046-ONBOARD", "name": "Agency Onboarding Simplicity", "description": "This measures how difficult it is for a new agency to join the data sharing network. Humanitarian coordination requires rapid partner engagement.", "weight": 0.1, "ratingGuide": { "5": "Self-service onboarding. New agency operational within hours. Minimal IT requirements. Cloud or on-premise deployment options.", "4": "Guided onboarding within days. Standard IT infrastructure sufficient. Support documentation comprehensive.", "3": "Onboarding requires weeks of configuration. Moderate IT requirements. Some training needed.", "2": "Complex onboarding requiring specialist support. Significant IT infrastructure required.", "1": "Months-long onboarding with custom development. Enterprise IT infrastructure required." } } ], "procurement": { "marketMaturity": "nascent", "primaryMode": "consortium", "alternativeModes": [ "integrator-led" ], "reasoning": "Inter-agency data sharing without centralisation is research-stage; consortium structures fit.", "exampleProductCategories": [ "federated-data-platform", "data-trust-platform" ], "partnerChannels": [], "lastReviewed": "2026-05-01" } }, { "id": "UC-C-047", "name": "Referral pathway tracking across service providers", "category": "C", "subcategory": "Service Coordination", "description": "Follow a referral from the first service to the next provider, so you can see whether the person arrived and received the help they needed.", "bCriteria": [ "B1", "B3", "B6" ], "requiredComponents": [ { "component": "coordination-layer", "description": "Referral tracking system" }, { "component": "record-keeping-platform", "description": "Referral records" }, { "component": "access-control", "description": "Provider access to referrals" }, { "component": "verification-mechanism", "description": "Proof of referral completion" } ], "conditionalComponents": [ { "component": "consent-management", "condition": "For beneficiary consent to referral", "linksTo": "UC-C-045" }, { "component": "identity-verification", "condition": "For provider identity verification" } ], "crossCategoryDependencies": [ "UC-B-028 for portable service history" ], "p2TriggerConditions": { "description": "Activated when P2 shows multi-service coordination + referral gaps + service continuity needs", "rangeSignals": [ "services >= 3+", "referralGaps >= concern", "serviceCoordination >= important" ] }, "contextFieldsTemplate": [ { "field": "beneficiaries", "source": "P2 programme scale", "description": "Beneficiaries needing referrals" }, { "field": "providers", "source": "P0 partnerships + services", "description": "Service providers" }, { "field": "referralTypes", "source": "P2 service needs", "description": "Types of referrals" }, { "field": "trackingGranularity", "source": "P2 coordination", "description": "Referral tracking detail" } ], "implementationComplexity": "medium", "examples": { "note": "Integrated case management, service coordination", "references": [ { "name": "OpenMRS Referral Module", "url": "https://openmrs.org/", "solved": "Open-source health system with built-in referral tracking and inter-provider coordination" }, { "name": "Primero Platform - Case Management", "url": "https://www.primero.org/", "solved": "UNICEF-led open-source platform for managing protection referrals with inter-agency coordination" }, { "name": "Care Coordination Hub Standards (HL7 FHIR Care Coordination)", "url": "https://www.hl7.org/fhir/carecoordination-module.html", "solved": "FHIR standards for referral and care coordination workflows between healthcare providers" } ] }, "solutionQuestions": [ { "id": "referral-tracking-mechanism", "type": "select", "options": [ { "label": "Shared referral registry (all referrals in central database)", "value": "shared-registry" }, { "label": "Digital tracking (permanent tamper-proof referral register)", "value": "blockchain-tracking" }, { "label": "Unique referral tokens (beneficiary carries proof)", "value": "referral-tokens" }, { "label": "Provider-to-provider notification (direct handoff)", "value": "direct-handoff" }, { "label": "Beneficiary self-reporting (no tracking system)", "value": "self-reporting" } ], "propertyMapping": { "shared-registry": { "technologies": [ "Referral management system", "Shared database" ], "technologyProperties": { "storage": "Central database of all referrals", "access": "All providers can query status", "synchronization": "Real-time referral status" } }, "blockchain-tracking": { "technologies": [ "Blockchain referral ledger", "Smart contracts" ], "technologyProperties": { "immutability": "Referral events recorded on blockchain", "transparency": "All parties can see referral history", "nonRepudiation": "Provider cannot deny receiving referral" } }, "referral-tokens": { "technologies": [ "Token generation system", "Referral credential" ], "technologyProperties": { "token": "Unique referral ID given to beneficiary", "portability": "Beneficiary presents at receiving provider", "verification": "Receiving provider verifies token" } }, "direct-handoff": { "technologies": [ "Provider-to-provider API", "Direct notification" ], "technologyProperties": { "notification": "Referring provider notifies recipient", "confirmation": "Recipient confirms receipt", "directness": "No intermediate system" } }, "self-reporting": { "technologies": [ "Beneficiary communication", "No system" ], "technologyProperties": { "tracking": "None", "reliability": "Low (depends on beneficiary compliance)", "risk": "Referral may be lost" } } }, "prefillFrom": null, "briefSection": "Data architecture", "text": "How do you currently track referrals between service providers?", "ngoText": "How do you currently track referrals between service providers?" }, { "id": "referral-completion-proof", "type": "select", "options": [ { "label": "Automated confirmation (recipient system sends confirmation)", "value": "automated-confirmation" }, { "label": "Manual confirmation (staff at recipient confirms)", "value": "manual-confirmation" }, { "label": "Beneficiary confirmation (beneficiary confirms service received)", "value": "beneficiary-confirmation" }, { "label": "Photo/video proof (evidence of service delivery)", "value": "photo-proof" }, { "label": "No completion verification", "value": "no-verification" } ], "propertyMapping": { "automated-confirmation": { "technologies": [ "Confirmation API", "Automated messaging" ], "technologyProperties": { "confirmation": "System automatically sends when service recorded", "timing": "Real-time confirmation", "reliability": "High (system enforced)" } }, "manual-confirmation": { "technologies": [ "Manual confirmation interface", "Staff workflow" ], "technologyProperties": { "confirmation": "Staff at recipient manually confirms", "timing": "May be delayed", "flexibility": "Can explain delays or issues" } }, "beneficiary-confirmation": { "technologies": [ "Beneficiary survey platform", "Feedback interface" ], "technologyProperties": { "confirmation": "Beneficiary confirms receipt of service", "timing": "Post-service confirmation", "bias": "May be reluctant to report bad service" } }, "photo-proof": { "technologies": [ "Photo/video capture", "Timestamp with metadata" ], "technologyProperties": { "proof": "Physical evidence of service delivery", "verification": "AI analysis to confirm authenticity", "privacy": "May expose beneficiary identity" } }, "no-verification": { "technologies": [ "No verification system", "Trust-based" ], "technologyProperties": { "verification": "None", "trust": "Assumes referral completed", "risk": "Completion unknown" } } }, "prefillFrom": null, "briefSection": "Data integrity", "text": "How do you currently document that a referral was completed?", "ngoText": "How do you currently document that a referral was completed?" }, { "id": "follow-up-tracking", "type": "select", "options": [ { "label": "Automated follow-up (system triggers reminders)", "value": "automated-followup" }, { "label": "Manual follow-up (staff contacts beneficiary)", "value": "manual-followup" }, { "label": "Beneficiary self-reporting (outcome survey)", "value": "self-report" }, { "label": "Inter-provider follow-up (recipient provider reports outcome)", "value": "provider-report" }, { "label": "No follow-up tracking", "value": "no-followup" } ], "propertyMapping": { "automated-followup": { "technologies": [ "Automated reminder system", "Scheduled notifications" ], "technologyProperties": { "triggering": "System sends reminders at intervals", "timing": "7, 14, 30 days post-referral", "automation": "Fully automated" } }, "manual-followup": { "technologies": [ "Follow-up task management", "Staff worklist" ], "technologyProperties": { "tracking": "Staff tracks and performs follow-up", "timing": "Flexible timing", "humanTouch": "Personal contact possible" } }, "self-report": { "technologies": [ "Outcomes survey platform", "Beneficiary feedback" ], "technologyProperties": { "survey": "Beneficiary completes survey", "outcomes": "Self-reported outcomes", "bias": "May over-report positive outcomes" } }, "provider-report": { "technologies": [ "Provider outcome reporting", "Inter-provider messaging" ], "technologyProperties": { "reporting": "Recipient provider reports outcomes", "coordination": "Provider-to-provider communication", "accuracy": "Professional assessment" } }, "no-followup": { "technologies": [ "No follow-up system", "No tracking" ], "technologyProperties": { "tracking": "None", "outcomes": "Unknown", "risk": "No idea if service helped" } } }, "prefillFrom": null, "briefSection": "Interoperability", "text": "How do you currently track follow-up actions on referrals?", "ngoText": "How do you currently track follow-up actions on referrals?" }, { "id": "referral-data-consent", "type": "select", "options": [ { "label": "Broad consent (beneficiary consents to all provider sharing)", "value": "broad-consent" }, { "label": "Per-provider consent (consent for each provider separately)", "value": "per-provider-consent" }, { "label": "Just-in-time consent (ask at each referral)", "value": "jit-consent" }, { "label": "Implicit consent (service enrollment implies consent)", "value": "implicit-consent" }, { "label": "No consent requirement (service delivery overrides privacy)", "value": "no-consent" } ], "propertyMapping": { "broad-consent": { "technologies": [ "Broad consent form", "Multi-provider authorization" ], "technologyProperties": { "scope": "Consent for all providers in network", "simplicity": "Single consent covers all", "limitation": "Beneficiary may not trust all providers" } }, "per-provider-consent": { "technologies": [ "Provider-specific consent", "Consent per referral" ], "technologyProperties": { "specificity": "Consent for each provider", "control": "Fine-grained control", "complexity": "More consent forms" } }, "jit-consent": { "technologies": [ "Just-in-time consent platform", "Consent at referral time" ], "technologyProperties": { "timing": "Consent requested at referral", "relevance": "Timely and relevant to beneficiary", "responsiveness": "May delay referral" } }, "implicit-consent": { "technologies": [ "Service enrollment consent", "Terms of service" ], "technologyProperties": { "consent": "Enrollment in service implies consent", "documentation": "Mentioned in ToS", "legality": "May not be acceptable everywhere" } }, "no-consent": { "technologies": [ "No consent system", "Service delivery priority" ], "technologyProperties": { "priority": "Service delivery overrides privacy", "ethics": "Questionable ethical standing", "risk": "Violates privacy principles" } } }, "prefillFrom": null, "briefSection": "Consent management", "text": "What consent should govern referral data sharing between providers?", "ngoText": "What consent should govern referral data sharing between providers?" }, { "id": "safe-referral-handling", "type": "select", "options": [ { "label": "Encrypted end-to-end (provider can't see data)", "value": "e2e-encrypted" }, { "label": "TLS in transit, encrypted at rest", "value": "standard-encryption" }, { "label": "Minimal data sharing (only essential info)", "value": "minimal-sharing" }, { "label": "Provider-specific redaction (hide sensitive fields)", "value": "redaction" }, { "label": "No encryption; trust network security", "value": "no-encryption" } ], "propertyMapping": { "e2e-encrypted": { "technologies": [ "End-to-end encryption layer", "Key management" ], "technologyProperties": { "encryption": "Data encrypted end-to-end", "decryption": "Only recipient can decrypt", "intermediaries": "Cannot read referral data" } }, "standard-encryption": { "technologies": [ "TLS 1.3", "AES-256 at rest" ], "technologyProperties": { "transport": "TLS 1.3 in transit", "storage": "AES-256-GCM at rest", "trust": "Trusts provider infrastructure" } }, "minimal-sharing": { "technologies": [ "Data minimization filter", "Field-level control" ], "technologyProperties": { "sharing": "Only essential fields shared", "filtering": "Sensitive fields removed", "privacy": "Reduced data exposure" } }, "redaction": { "technologies": [ "Redaction engine", "Field masking" ], "technologyProperties": { "redaction": "Sensitive fields masked or redacted", "flexibility": "Different redaction per provider type", "visibility": "Provider sees only relevant data" } }, "no-encryption": { "technologies": [ "No encryption", "Network trust" ], "technologyProperties": { "trust": "Trust network perimeter", "risk": "High if network compromised", "simplicity": "No encryption overhead" } } }, "prefillFrom": null, "briefSection": "Privacy and encryption", "text": "What is your current process for ensuring safe referrals?", "ngoText": "What is your current process for ensuring safe referrals?" }, { "id": "multi-provider-coordination", "type": "select", "options": [ { "label": "Linear referral chain (provider A \u2192 B \u2192 C)", "value": "linear-chain" }, { "label": "Hub-and-spoke (coordinator manages multiple referrals)", "value": "hub-spoke" }, { "label": "Parallel referrals (multiple providers simultaneously)", "value": "parallel" }, { "label": "Feedback loop (providers inform each other of outcomes)", "value": "feedback-loop" }, { "label": "No coordination (independent referrals)", "value": "no-coordination" } ], "propertyMapping": { "linear-chain": { "technologies": [ "Referral chain tracker", "Sequential workflow" ], "technologyProperties": { "flow": "A \u2192 B \u2192 C in sequence", "complexity": "Simple but sequential", "speed": "Takes time as referrals cascade" } }, "hub-spoke": { "technologies": [ "Case coordination platform", "Central coordinator role" ], "technologyProperties": { "coordination": "One coordinator manages referrals", "efficiency": "Parallel referrals possible", "communication": "All communication through coordinator" } }, "parallel": { "technologies": [ "Multi-referral management", "Parallel workflow" ], "technologyProperties": { "timing": "Multiple providers engaged simultaneously", "efficiency": "Fast parallel service delivery", "coordination": "More complex coordination" } }, "feedback-loop": { "technologies": [ "Inter-provider communication", "Outcome sharing" ], "technologyProperties": { "communication": "Providers share outcomes and feedback", "learning": "Improved care through coordination", "trust": "Requires high trust between providers" } }, "no-coordination": { "technologies": [ "Independent referrals", "No coordination" ], "technologyProperties": { "coordination": "None", "redundancy": "Services may duplicate", "efficiency": "Low coordination" } } }, "prefillFrom": null, "briefSection": "Interoperability", "text": "How do you currently coordinate with multiple service providers on referrals?", "ngoText": "How do you currently coordinate with multiple service providers on referrals?" }, { "id": "referral-audit-trail", "type": "select", "options": [ { "label": "Permanent tamper-proof referral ledger (digital ledger audit trail)", "value": "blockchain-ledger" }, { "label": "Timestamped audit log (each event logged with time)", "value": "audit-log" }, { "label": "Beneficiary path map (visual referral pathway)", "value": "journey-map" }, { "label": "Provider accountability log (who referred to whom)", "value": "accountability-log" }, { "label": "No audit trail (minimal documentation)", "value": "no-audit" } ], "propertyMapping": { "blockchain-ledger": { "technologies": [ "Blockchain referral ledger", "Smart contracts" ], "technologyProperties": { "ledger": "All referral events on blockchain", "immutability": "Cannot be modified", "transparency": "All parties can view" } }, "audit-log": { "technologies": [ "Audit logging system", "Timestamped entries" ], "technologyProperties": { "logging": "Each referral event timestamped", "retention": "Permanent log", "searching": "Query by date, provider, beneficiary" } }, "journey-map": { "technologies": [ "Journey visualization tool", "Referral pathway diagram" ], "technologyProperties": { "visualization": "Visual map of referral pathway", "clarity": "Clear understanding of journey", "gaps": "Can identify dropped referrals" } }, "accountability-log": { "technologies": [ "Provider accountability tracker", "Referral outcome log" ], "technologyProperties": { "tracking": "Who referred to whom and outcome", "accountability": "Provider performance metrics", "incentives": "Can be used for provider evaluation" } }, "no-audit": { "technologies": [ "No audit system", "Minimal documentation" ], "technologyProperties": { "tracking": "Minimal", "accountability": "None", "risk": "Cannot verify referral happened" } } }, "prefillFrom": null, "briefSection": "Reporting and audit", "text": "How do you currently maintain an audit trail of referral activities?", "ngoText": "How do you currently maintain an audit trail of referral activities?" }, { "id": "beneficiary-choice", "label": "How will beneficiaries exercise choice in how they receive and use this service?", "type": "select", "briefSection": "Consent management", "options": [ { "label": "Beneficiaries choose between delivery methods (cash, voucher, mobile money, direct)", "value": "delivery-choice" }, { "label": "Beneficiaries choose preferred merchants or service points", "value": "merchant-choice" }, { "label": "Beneficiaries control their own data sharing preferences", "value": "data-choice" }, { "label": "Multiple choice dimensions (delivery + merchant + data)", "value": "full-choice" }, { "label": "Limited choice: programme constraints determine delivery", "value": "limited" } ], "propertyMapping": { "delivery-choice": { "technologies": [], "technologyProperties": { "beneficiaryChoice": "Delivery method choice", "dignityDesign": "Beneficiaries select preferred receipt method" } }, "merchant-choice": { "technologies": [], "technologyProperties": { "beneficiaryChoice": "Merchant/service point choice", "dignityDesign": "Beneficiaries select where to redeem" } }, "data-choice": { "technologies": [], "technologyProperties": { "beneficiaryChoice": "Data sharing choice", "dignityDesign": "Beneficiaries control personal data sharing" } }, "full-choice": { "technologies": [], "technologyProperties": { "beneficiaryChoice": "Multi-dimensional choice", "dignityDesign": "Full beneficiary agency across delivery, merchant, and data" } }, "limited": { "technologies": [], "technologyProperties": { "beneficiaryChoice": "Limited by programme design", "dignityDesign": "Programme constraints; beneficiary informed of reasons" } } }, "text": "How will beneficiaries exercise choice in how they receive and use this service?" } ], "complexityFactors": { "relationships": 3, "operationalChange": 3, "dataCompliance": 4 }, "securityTier": "B", "suggestedCriteria": [ { "id": "SC-C047-TRACK", "name": "End-to-end Referral Visibility", "description": "Can the system track a referral from initiation through to service delivery and outcome, across multiple providers, without losing the chain?", "weight": 0.3, "ratingGuide": { "5": "Complete referral lifecycle tracking \u2014 initiation, acceptance, service delivery, outcome, and follow-up \u2014 across unlimited providers. Real-time status visible to authorised parties.", "4": "Tracks referral through key stages across providers. Status updates at each handoff. Minor gaps in outcome tracking.", "3": "Tracks referral initiation and acceptance. Service delivery and outcome tracking requires manual input by receiving provider.", "2": "Records referral sent and received. No automatic tracking of downstream steps.", "1": "One-way referral recording only. No tracking after initial referral is sent." } }, { "id": "SC-C047-PRIVACY", "name": "Beneficiary Privacy in Referral Data", "description": "The solution shares only the minimum necessary information with each provider in the referral chain. Receiving providers should only see data relevant to their service.", "weight": 0.25, "ratingGuide": { "5": "Purpose-specific data disclosure \u2014 each provider in the chain sees only the data fields relevant to their service. Controlled by consent and configurable per referral type.", "4": "Data segmentation per provider role. Standard referral forms limit disclosure. Beneficiary can review what's shared.", "3": "Role-based access to referral data. Standard fields shared with all providers in the chain. Some customisation possible.", "2": "Full referral record shared with receiving providers. No field-level disclosure control.", "1": "All case data accompanies the referral. No data minimisation." } }, { "id": "SC-C047-COORD", "name": "Multi-provider Coordination", "description": "Does the solution support complex referral pathways where a beneficiary needs services from multiple providers simultaneously or sequentially?", "weight": 0.2, "ratingGuide": { "5": "Supports parallel and sequential multi-provider referrals. Coordination dashboard shows all active referrals per beneficiary. Prevents duplicate referrals.", "4": "Handles multi-provider referrals with status tracking. Basic coordination view. Duplicate detection available.", "3": "Supports sequential referrals (A\u2192B\u2192C). Parallel referrals managed as separate chains.", "2": "Bilateral referrals only (A\u2192B). Multi-provider chains require separate referral records.", "1": "Single-hop referrals only. No multi-provider pathway support." } }, { "id": "SC-C047-OUTCOME", "name": "Outcome Measurement and Feedback", "description": "Can the system capture whether the referred service was actually received and whether it addressed the beneficiary's need?", "weight": 0.15, "ratingGuide": { "5": "Built-in outcome tracking with beneficiary feedback. Service completion verified. Outcome data feeds back to referral quality metrics.", "4": "Outcome recording by receiving provider. Completion rates tracked. Basic quality indicators.", "3": "Service delivery confirmed by receiving provider. No outcome quality measurement.", "2": "Manual outcome recording. Referral marked as complete/incomplete but no quality data.", "1": "No outcome tracking. Referral status ends at 'sent' or 'received'." } }, { "id": "SC-C047-INTEROP", "name": "Case Management System Integration", "description": "Does the solution integrate with existing humanitarian case management systems?", "weight": 0.1, "ratingGuide": { "5": "Native integration with the major humanitarian case management platforms. Referrals flow seamlessly between systems.", "4": "API integration with major humanitarian platforms. Referral data exchange automated for supported systems.", "3": "Standard API available. Integration with case management systems requires custom connector development.", "2": "CSV/spreadsheet export/import for referral data. Manual data transfer between systems.", "1": "Standalone system with no integration capability." } } ], "procurement": { "marketMaturity": "emerging", "primaryMode": "rfq", "alternativeModes": [ "off-the-shelf" ], "reasoning": "Referral pathway tracking SaaS available in social services markets.", "exampleProductCategories": [ "case-referral-platform", "social-services-saas" ], "partnerChannels": [], "lastReviewed": "2026-05-01" } }, { "id": "UC-C-048", "name": "Audit trail maintenance for compliance", "category": "C", "subcategory": "Compliance and Audit", "description": "Keep logs of who accessed or changed data in a form that nobody inside the organisation can alter or delete, so auditors can rely on them.", "bCriteria": [ "B3" ], "requiredComponents": [ { "component": "audit-mechanism", "description": "Immutable audit trail" }, { "component": "record-keeping-platform", "description": "Audit record ledger" }, { "component": "access-control", "description": "Audit log protection" } ], "conditionalComponents": [ { "component": "smart-contracts", "condition": "If automated compliance rules" } ], "crossCategoryDependencies": [], "p2TriggerConditions": { "description": "Activated when P2 shows audit requirements + compliance burden + audit concerns", "rangeSignals": [ "auditRequirements >= strict", "complianceBurden >= high", "auditConcerns >= true" ] }, "contextFieldsTemplate": [ { "field": "auditStandards", "source": "P0 donor requirements", "description": "Required audit standards" }, { "field": "dataTypes", "source": "P2 operations", "description": "Data to be audited" }, { "field": "retentionPeriod", "source": "P0 Q19-21", "description": "Audit record retention" }, { "field": "auditFrequency", "source": "P0 governance", "description": "Audit frequency" } ], "implementationComplexity": "medium", "examples": { "note": "Compliance frameworks, audit standards", "references": [ { "name": "HIPAA Security Rule - Audit Controls (164.312(b))", "url": "https://www.hipaa.org/", "solved": "Regulatory requirement for audit trails and compliance monitoring in health systems" }, { "name": "ISO 27001 - Access Control and Audit Logging", "url": "https://www.iso.org/standard/54534.html", "solved": "International standards for audit trail implementation and access control management" }, { "name": "Ethereum Event Logging - Smart Contract Auditing", "url": "https://docs.soliditylang.org/en/latest/contracts.html#events", "solved": "Blockchain-based immutable event logging for transparent audit trails" } ] }, "solutionQuestions": [ { "id": "audit-trail-immutability", "type": "select", "options": [ { "label": "Append-only database (no deletion or modification)", "value": "append-only" }, { "label": "Digital anchoring (fingerprint on permanent tamper-proof register)", "value": "blockchain" }, { "label": "digitally verified chain (each log linked to previous)", "value": "hash-chain" }, { "label": "Hardware security module (HSM-protected signing)", "value": "hsm" }, { "label": "No specific immutability mechanism", "value": "none" } ], "propertyMapping": { "append-only": { "technologies": [ "Append-only database", "Write-once storage" ], "technologyProperties": { "writes": "Only appends allowed; no overwrites", "deletion": "Logical deletion only (marked as deleted)", "recovery": "Full history preserved" } }, "blockchain": { "technologies": [ "Blockchain anchoring service", "Hash on-chain" ], "technologyProperties": { "anchoring": "Audit log hash anchored to blockchain", "immutability": "Cannot be retroactively modified", "verification": "Merkle proof of integrity" } }, "hash-chain": { "technologies": [ "Cryptographic hash chain", "Linked hashes" ], "technologyProperties": { "chaining": "Each entry hash includes previous entry's hash", "tampering": "Any modification breaks chain", "efficiency": "No external system needed" } }, "hsm": { "technologies": [ "Hardware security module", "HSM key management" ], "technologyProperties": { "signing": "Audit logs signed with HSM key", "tamperProof": "Physical tamper protection", "compliance": "Meets high security standards" } }, "none": { "technologies": [ "Standard logging", "No immutability" ], "technologyProperties": { "mutability": "Logs can be modified by admin", "risk": "High tampering risk", "compliance": "Poor compliance" } } }, "prefillFrom": null, "briefSection": "Data integrity", "text": "What level of audit trail immutability would you need?", "ngoText": "What level of audit trail immutability would you need?" }, { "id": "audit-access-control", "type": "select", "options": [ { "label": "Restricted to auditors and compliance team only", "value": "auditors-only" }, { "label": "Data subject (beneficiary) can view own access logs", "value": "data-subject" }, { "label": "Service administrator and supervisors", "value": "admin-supervisors" }, { "label": "External auditors and regulators", "value": "external" }, { "label": "No access control (audit logs public)", "value": "no-control" } ], "propertyMapping": { "auditors-only": { "technologies": [ "Role-based access control", "Auditor credentials" ], "technologyProperties": { "access": "Only certified auditors", "verification": "Credential verification", "logging": "Log access to audit logs" } }, "data-subject": { "technologies": [ "Beneficiary audit interface", "Filtered view" ], "technologyProperties": { "visibility": "Beneficiary sees own data's access log", "notification": "Alerted to unusual access", "control": "Can challenge inappropriate access" } }, "admin-supervisors": { "technologies": [ "Organizational role-based access", "Supervisor override" ], "technologyProperties": { "roles": "Admin and supervisor roles", "delegation": "Can delegate audit review", "responsibility": "Organizational accountability" } }, "external": { "technologies": [ "Regulatory access portal", "Third-party audit" ], "technologyProperties": { "access": "Auditors and regulators", "verification": "Government credentials verified", "transparency": "External oversight" } }, "no-control": { "technologies": [ "Public audit logs", "No access restrictions" ], "technologyProperties": { "transparency": "Complete transparency", "privacy": "High privacy risk", "compliance": "Violates privacy laws" } } }, "prefillFrom": null, "briefSection": "Access control", "text": "Who should have access to audit logs?", "ngoText": "Who should have access to audit logs?" }, { "id": "audit-retention", "type": "select", "options": [ { "label": "Minimum: 1 year from last log entry", "value": "one-year" }, { "label": "Standard: 7 years for regulatory compliance", "value": "seven-years" }, { "label": "Extended: 10 years for medical records", "value": "ten-years" }, { "label": "Permanent: indefinite retention", "value": "permanent" }, { "label": "Minimal: deleted once audit complete", "value": "minimal" } ], "propertyMapping": { "one-year": { "technologies": [ "Retention schedule system", "Automatic deletion" ], "technologyProperties": { "retention": "1 year from last entry", "deletion": "Auto-delete after period", "regulation": "May not meet compliance" } }, "seven-years": { "technologies": [ "7-year retention schedule", "Archive system" ], "technologyProperties": { "retention": "7 years from last entry", "archive": "Moved to cold storage after use", "standard": "Standard regulatory requirement" } }, "ten-years": { "technologies": [ "10-year retention schedule", "Long-term archive" ], "technologyProperties": { "retention": "10 years (medical record standard)", "archive": "Secure long-term storage", "compliance": "Meets health care standards" } }, "permanent": { "technologies": [ "Permanent archival", "Indefinite storage" ], "technologyProperties": { "retention": "Permanent", "storage": "Secure archive", "access": "Limited to authorized queries" } }, "minimal": { "technologies": [ "Deletion immediately", "No retention" ], "technologyProperties": { "retention": "None after audit", "deletion": "Immediate", "risk": "Cannot audit historical access" } } }, "prefillFrom": null, "briefSection": "Reporting and audit", "text": "How long should audit logs be retained?", "ngoText": "How long should audit logs be retained?" }, { "id": "audit-reporting", "type": "select", "options": [ { "label": "Automated compliance reports (daily/weekly)", "value": "automated-reports" }, { "label": "Manual audit by compliance team (monthly)", "value": "manual-audit" }, { "label": "Red-flag alerting (immediate notification of violations)", "value": "red-flag-alerts" }, { "label": "Annual certification (third-party audit)", "value": "annual-cert" }, { "label": "No specific reporting (audit logs kept but not reviewed)", "value": "no-reporting" } ], "propertyMapping": { "automated-reports": { "technologies": [ "Report generation system", "Email distribution" ], "technologyProperties": { "frequency": "Daily, weekly, or monthly", "content": "Summary of access patterns, violations", "automation": "Fully automated" } }, "manual-audit": { "technologies": [ "Manual review interface", "Audit checklist" ], "technologyProperties": { "frequency": "Monthly or quarterly", "review": "Human review of audit logs", "depth": "Detailed analysis" } }, "red-flag-alerts": { "technologies": [ "Anomaly detection engine", "Alert service" ], "technologyProperties": { "detection": "Detects suspicious access", "alerting": "Immediate notification", "threshold": "Configurable risk score" } }, "annual-cert": { "technologies": [ "Third-party auditor", "Certification" ], "technologyProperties": { "frequency": "Annual", "auditor": "Independent external auditor", "certification": "Publishes compliance certificate" } }, "no-reporting": { "technologies": [ "No reporting system", "Logs kept" ], "technologyProperties": { "reporting": "None", "oversight": "None", "risk": "Violations may go unnoticed" } } }, "prefillFrom": null, "briefSection": "Reporting and audit", "text": "What audit reporting requirements do you have from donors or regulators?", "ngoText": "What audit reporting requirements do you have from donors or regulators?" }, { "id": "audit-trail-stakeholders", "type": "select", "options": [ { "label": "Internal only (1\u20132 teams)", "value": "internal" }, { "label": "Internal + 1\u20133 external partners", "value": "few-external" }, { "label": "Multiple external stakeholders (4\u201310)", "value": "multi-external" }, { "label": "Ecosystem-wide (donors, partners, beneficiaries, regulators)", "value": "ecosystem" } ], "propertyMapping": { "internal": { "technologies": [ "Private ledger" ], "technologyProperties": { "accessControl": "Simple role-based", "networkType": "Private" } }, "few-external": { "technologies": [ "Permissioned network", "Selective data sharing" ], "technologyProperties": { "accessControl": "Partner-level permissions", "networkType": "Consortium" } }, "multi-external": { "technologies": [ "Permissioned network", "Multi-party access layer" ], "technologyProperties": { "accessControl": "Granular role-based", "networkType": "Consortium" } }, "ecosystem": { "technologies": [ "Permissioned public network", "Data marketplace" ], "technologyProperties": { "accessControl": "Multi-tier with public layer", "networkType": "Hybrid public-private" } } }, "prefillFrom": null, "briefSection": "Governance and access", "text": "How many distinct parties need visibility into the audit trail data?", "ngoText": "How many distinct parties need visibility into the audit trail data?" }, { "id": "sq-UC-C-048-001", "type": "single-select", "options": [ { "value": "7-year-minimum", "label": "7-year minimum retention" }, { "value": "donor-specific-terms", "label": "Donor-specific terms" }, { "value": "indefinite-immutable", "label": "Indefinite permanent tamper-proof storage" }, { "value": "tiered-by-sensitivity", "label": "Tiered by sensitivity" }, { "value": "regulatory-minimum", "label": "Regulatory minimum only" } ], "propertyMapping": { "7-year-minimum": { "technologies": [ "retention-policy", "7-year-archival" ], "technologyProperties": {} }, "donor-specific-terms": { "technologies": [ "configurable-retention", "donor-tracking" ], "technologyProperties": {} }, "indefinite-immutable": { "technologies": [ "immutable-storage", "permanent-archive" ], "technologyProperties": {} }, "tiered-by-sensitivity": { "technologies": [ "classification-system", "tiered-archival" ], "technologyProperties": {} }, "regulatory-minimum": { "technologies": [ "regulatory-tracking", "minimum-retention" ], "technologyProperties": {} } }, "briefSection": "compliance", "text": "What retention and archival policy should apply to audit trail data?", "ngoText": "What retention and archival policy should apply to audit trail data?" } ], "complexityFactors": { "relationships": 1, "operationalChange": 2, "dataCompliance": 2 }, "suggestedCriteria": [ { "id": "SC-C048-TAMPER", "name": "Tamper-proof Record Integrity", "description": "This measures how strongly the solution guarantees that audit records cannot be altered, deleted, or backdated. Compliance audits require provable record integrity.", "weight": 0.3, "ratingGuide": { "5": "Cryptographic hash chain with public anchoring. Any modification detectable by any party. Mathematically impossible to alter records without detection.", "4": "Cryptographic hash chain within the system. Tamper-evident storage. Alterations detectable through internal verification.", "3": "Append-only ledger with write-once storage. Modifications create new entries rather than overwriting. Admin could theoretically bypass.", "2": "Standard database with change logging. Logs tamper-evident but stored in the same system as the data.", "1": "Standard database with no immutability guarantees. Records can be modified or deleted." } }, { "id": "SC-C048-COMPLETE", "name": "Audit Trail Completeness", "description": "Does the system capture all compliance-relevant events (data access, modifications, system configuration changes, user actions, and automated processes)?", "weight": 0.25, "ratingGuide": { "5": "Captures every system event with full context \u2014 who, what, when, why, and from where. Includes automated process actions and system configuration changes.", "4": "Comprehensive event capture for data access and modifications. User actions and key system events logged. Some automated processes may lack detail.", "3": "Standard audit logging \u2014 data modifications and user logins captured. Access events partially logged.", "2": "Basic modification logging. Login/logout events. No access-level tracking.", "1": "Minimal logging \u2014 only captures explicit save/update events." } }, { "id": "SC-C048-SEARCH", "name": "Audit Trail Queryability", "description": "Compliance officers can efficiently search, filter, and analyse audit records. Auditors need to answer specific questions quickly, not wade through raw logs.", "weight": 0.2, "ratingGuide": { "5": "Full-featured audit analytics \u2014 search by entity, user, date range, event type. Pre-built compliance reports. Visual timeline of entity history.", "4": "Searchable audit interface with filters. Standard reports available. Custom queries supported.", "3": "Basic search and filter on audit logs. Reports require manual construction.", "2": "Chronological log viewer. Limited search. No analytical features.", "1": "Raw log files only. Requires technical expertise to extract information." } }, { "id": "SC-C048-FRAMEWORK", "name": "Compliance Framework Alignment", "description": "Does the solution align with relevant compliance frameworks (IPSAS, donor-specific requirements, national regulations) used in the humanitarian sector?", "weight": 0.15, "ratingGuide": { "5": "Pre-configured for IPSAS and major donor compliance requirements. Templates for USAID, EU, DFID/FCDO audits. Configurable for national regulations.", "4": "Aligns with major accounting standards. Configurable compliance rules. Some donor-specific templates.", "3": "General compliance features. Can be configured for specific frameworks with effort.", "2": "Basic record-keeping suitable for compliance but no framework-specific features.", "1": "No compliance awareness. Audit trail exists but requires manual alignment with any framework." } }, { "id": "SC-C048-RETENTION", "name": "Record Retention and Lifecycle Management", "description": "Does the solution manage record retention periods, archival, and secure disposal in line with compliance requirements?", "weight": 0.1, "ratingGuide": { "5": "Configurable retention policies per record type. Automated archival and certified disposal. Retention compliance dashboard.", "4": "Retention periods configurable. Automated archival. Disposal with audit proof.", "3": "Manual retention management with reminders. Archival supported. Disposal logged.", "2": "Records retained indefinitely. Manual archival. No automated retention management.", "1": "No retention management. Records accumulate with no lifecycle controls." } } ], "procurement": { "marketMaturity": "mature", "primaryMode": "off-the-shelf", "alternativeModes": [ "rfq" ], "reasoning": "Audit trail tooling is a mature SaaS feature.", "exampleProductCategories": [ "audit-trail-saas", "compliance-records-platform" ], "partnerChannels": [], "lastReviewed": "2026-05-01" } }, { "id": "UC-C-049", "name": "Research data with beneficiary privacy protection", "category": "C", "subcategory": "Data Privacy", "description": "Let researchers check that programme data has not been manipulated without seeing who the people are, and let participants withdraw their consent.", "bCriteria": [ "B3", "B6" ], "requiredComponents": [ { "component": "data-layer", "description": "Research data storage" }, { "component": "encryption-privacy", "description": "Encrypted research data" }, { "component": "anonymisation-tools", "description": "Data anonymisation" }, { "component": "access-control", "description": "Granular research access" } ], "conditionalComponents": [ { "component": "privacy-tech", "condition": "For differential privacy in research" }, { "component": "consent-management", "condition": "For research consent management" } ], "crossCategoryDependencies": [], "p2TriggerConditions": { "description": "Activated when P2 shows research activities + privacy requirements + beneficiary protection", "rangeSignals": [ "researchProgramme >= true", "privacyRequirements >= strict", "ethicsReview >= required" ] }, "contextFieldsTemplate": [ { "field": "researchType", "source": "P2 research focus", "description": "Type of research" }, { "field": "beneficiaryData", "source": "P2 data collection", "description": "Beneficiary data used" }, { "field": "publications", "source": "P2 research outcomes", "description": "Intended publications" }, { "field": "ethicsApproval", "source": "P0 governance", "description": "Research ethics requirements" } ], "implementationComplexity": "medium-high", "examples": { "note": "Research ethics, beneficiary privacy", "references": [ { "name": "FAIR Data Principles with Privacy", "url": "https://www.go-fair.org/fair-principles/", "solved": "Framework for making research data Findable, Accessible, Interoperable, and Reusable while respecting privacy" }, { "name": "SAFETAG - Security Assessment Framework", "url": "https://safetag.org/", "solved": "NGO-focused framework for assessing research data security and ethics" }, { "name": "Five Safes Framework - TMA", "url": "https://www.ons.gov.uk/methodology/methodologicalpublications/generalmethodology/datagovernance/thefivesafesframework", "solved": "Framework for balancing data access with privacy: safe people, safe projects, safe settings, safe data, safe outputs" } ] }, "solutionQuestions": [ { "id": "research-data-de-identification", "type": "select", "options": [ { "label": "Full anonymization (irreversible identifier removal)", "value": "full-anonymization" }, { "label": "Pseudonymization (reversible, keyed lookup)", "value": "pseudonymization" }, { "label": "Differential privacy (statistical noise added)", "value": "differential-privacy" }, { "label": "K-anonymity (indistinguishable within groups of k)", "value": "k-anonymity" }, { "label": "Data aggregation (group-level statistics only)", "value": "aggregation" } ], "propertyMapping": { "full-anonymization": { "technologies": [ "Irreversible anonymization engine", "Record suppression" ], "technologyProperties": { "anonymization": "Identifiers cryptographically removed", "reversal": "Mathematically irreversible", "risk": "k-anonymity check >= 5" } }, "pseudonymization": { "technologies": [ "Pseudonym generator", "Mapping service" ], "technologyProperties": { "mapping": "One-way hash with separate key", "reversal": "Can be reversed with master key", "control": "Access to key restricted" } }, "differential-privacy": { "technologies": [ "Differential privacy engine", "Noise injection" ], "technologyProperties": { "noise": "Statistical noise added", "privacy": "Formal privacy bound (epsilon)", "accuracy": "Trade-off with utility" } }, "k-anonymity": { "technologies": [ "K-anonymity generalization", "Quasi-identifier suppression" ], "technologyProperties": { "k": "Each record indistinguishable from k-1 others", "generalization": "Age ranges, location regions", "verification": "Automated k-anonymity check" } }, "aggregation": { "technologies": [ "Aggregate statistics engine", "Group-level analysis" ], "technologyProperties": { "aggregation": "Only summary statistics released", "identifiability": "No individual records", "granularity": "Groups of 5-10+ minimum" } } }, "prefillFrom": null, "briefSection": "Privacy and encryption", "text": "What de-identification method should protect research data?", "ngoText": "What de-identification method should protect research data?" }, { "id": "ethics-approval-process", "type": "select", "options": [ { "label": "IRB/REC approval required before access", "value": "irb-approval" }, { "label": "Expedited review for low-risk research", "value": "expedited-review" }, { "label": "Data governance committee review", "value": "dgc-review" }, { "label": "Community consultation (community must approve)", "value": "community-consent" }, { "label": "No specific ethics requirement", "value": "no-ethics" } ], "propertyMapping": { "irb-approval": { "technologies": [ "IRB review system", "Protocol management" ], "technologyProperties": { "requirement": "Full Institutional Review Board approval", "duration": "30-90 day review", "documentation": "Formal approval letter" } }, "expedited-review": { "technologies": [ "Expedited review track", "Fast-track approval" ], "technologyProperties": { "criteria": "Low-risk research (observational, already de-identified)", "duration": "7-14 day review", "approval": "Streamlined approval" } }, "dgc-review": { "technologies": [ "Data governance committee", "Review system" ], "technologyProperties": { "committee": "Data governance committee (not IRB)", "criteria": "Data usage and privacy impact", "timing": "Flexible timing" } }, "community-consent": { "technologies": [ "Community engagement platform", "Consent gathering" ], "technologyProperties": { "approval": "Community must approve research", "process": "Community consultation meetings", "benefit": "Ensures community benefit" } }, "no-ethics": { "technologies": [ "No ethics review", "No approval required" ], "technologyProperties": { "review": "None", "risk": "Unethical research possible", "compliance": "Poor" } } }, "prefillFrom": null, "briefSection": "Consent management", "text": "What ethics review process should govern research use?", "ngoText": "What ethics review process should govern research use?" }, { "id": "secondary-use-restrictions", "type": "select", "options": [ { "label": "Purpose-limitation (data only for approved research)", "value": "purpose-limited" }, { "label": "Re-consent required (new consent for each use)", "value": "re-consent" }, { "label": "Broad consent (all research uses covered)", "value": "broad-research-consent" }, { "label": "Data marketplace (commercialization permitted)", "value": "data-marketplace" }, { "label": "No restrictions (open use)", "value": "open-use" } ], "propertyMapping": { "purpose-limited": { "technologies": [ "Use-restriction enforcement", "Purpose-based access control" ], "technologyProperties": { "restriction": "Data only for approved research", "enforcement": "Technical control preventing other use", "scope": "Specific research question approved" } }, "re-consent": { "technologies": [ "Secondary consent system", "Researcher notification" ], "technologyProperties": { "consent": "New consent for each secondary use", "process": "Contact beneficiary for new consent", "burden": "High beneficiary contact burden" } }, "broad-research-consent": { "technologies": [ "Broad research consent form", "Open research use" ], "technologyProperties": { "scope": "All future research uses covered", "simplicity": "Single consent for broad use", "limitation": "Beneficiary cannot limit specific uses" } }, "data-marketplace": { "technologies": [ "Data marketplace platform", "Commercial transaction" ], "technologyProperties": { "commercialization": "Data can be sold", "royalty": "Beneficiary may receive payment", "ethics": "Raises significant ethical issues" } }, "open-use": { "technologies": [ "Public data release", "Open license" ], "technologyProperties": { "use": "Unlimited use by anyone", "privacy": "Only if fully anonymized", "benefit": "Maximizes research benefit" } } }, "prefillFrom": null, "briefSection": "Consent management", "text": "What restrictions do you have on secondary uses of beneficiary data?", "ngoText": "What restrictions do you have on secondary uses of beneficiary data?" }, { "id": "publication-privacy", "type": "select", "options": [ { "label": "Pre-publication review (check for identifiable data)", "value": "pre-publication" }, { "label": "De-identification verification (confirm anonymity)", "value": "deidentification-check" }, { "label": "External privacy review (third-party checks)", "value": "external-review" }, { "label": "Community review (community approves publication)", "value": "community-review" }, { "label": "No publication review", "value": "no-review" } ], "propertyMapping": { "pre-publication": { "technologies": [ "Publication review checklist", "Manuscript review" ], "technologyProperties": { "review": "Manuscript reviewed before publication", "check": "Verify no identifiable data included", "delay": "Can delay publication" } }, "deidentification-check": { "technologies": [ "De-identification validator", "Expert review" ], "technologyProperties": { "verification": "Confirm data truly de-identified", "experts": "Expert reviewer checks manuscript", "certification": "De-identification certificate" } }, "external-review": { "technologies": [ "Third-party privacy auditor", "External review" ], "technologyProperties": { "reviewer": "Independent third-party", "impartiality": "Unbiased privacy assessment", "authority": "Can block publication" } }, "community-review": { "technologies": [ "Community review process", "Community veto" ], "technologyProperties": { "review": "Community reviews publication", "approval": "Community can reject publication", "power": "Community has final say" } }, "no-review": { "technologies": [ "No review process", "Direct publication" ], "technologyProperties": { "review": "None", "risk": "Privacy breaches possible", "consequence": "Identifiable information published" } } }, "prefillFrom": null, "briefSection": "Reporting and audit", "text": "What are your publication and privacy requirements for programme data?", "ngoText": "What are your publication and privacy requirements for programme data?" }, { "id": "research-privacy-stakeholders", "type": "select", "options": [ { "label": "Internal only (1\u20132 teams)", "value": "internal" }, { "label": "Internal + 1\u20133 external partners", "value": "few-external" }, { "label": "Multiple external stakeholders (4\u201310)", "value": "multi-external" }, { "label": "Ecosystem-wide (donors, partners, beneficiaries, regulators)", "value": "ecosystem" } ], "propertyMapping": { "internal": { "technologies": [ "Private ledger" ], "technologyProperties": { "accessControl": "Simple role-based", "networkType": "Private" } }, "few-external": { "technologies": [ "Permissioned network", "Selective data sharing" ], "technologyProperties": { "accessControl": "Partner-level permissions", "networkType": "Consortium" } }, "multi-external": { "technologies": [ "Permissioned network", "Multi-party access layer" ], "technologyProperties": { "accessControl": "Granular role-based", "networkType": "Consortium" } }, "ecosystem": { "technologies": [ "Permissioned public network", "Data marketplace" ], "technologyProperties": { "accessControl": "Multi-tier with public layer", "networkType": "Hybrid public-private" } } }, "prefillFrom": null, "briefSection": "Governance and access", "text": "How many distinct parties need visibility into the research data data?", "ngoText": "How many distinct parties need visibility into the research data data?" }, { "id": "anonymisation-approach", "type": "select", "options": [ { "label": "Full data anonymisation (irreversible)", "value": "full-anonymisation" }, { "label": "Pseudonymisation (reversible by authorised parties)", "value": "pseudonymisation" }, { "label": "Differential privacy (statistical noise injection)", "value": "differential-privacy" }, { "label": "Selective redaction (remove specific identifiers)", "value": "selective-redaction" } ], "propertyMapping": { "full-anonymisation": { "technologies": [ "Full anonymisation engine", "Identity stripping service", "Anonymised data store" ], "technologyProperties": { "method": "Irreversible anonymisation", "reIdentificationRisk": "Minimal", "dataUtility": "Aggregate analysis only" } }, "pseudonymisation": { "technologies": [ "Pseudonymisation engine", "Key-managed re-identification service", "Anonymisation tools" ], "technologyProperties": { "method": "Pseudonymisation with secure key vault", "reIdentificationRisk": "Controlled \u2014 authorised parties only", "dataUtility": "Individual-level analysis with controls" } }, "differential-privacy": { "technologies": [ "Differential privacy engine", "Statistical noise injection", "Anonymisation tools" ], "technologyProperties": { "method": "Differential privacy", "reIdentificationRisk": "Mathematically bounded", "dataUtility": "Statistical analysis with privacy guarantees" } }, "selective-redaction": { "technologies": [ "Selective redaction engine", "PII detection service", "Anonymisation tools" ], "technologyProperties": { "method": "Selective PII redaction", "reIdentificationRisk": "Moderate \u2014 depends on data context", "dataUtility": "Near-full with identifiers removed" } } }, "prefillFrom": null, "briefSection": "Data anonymisation", "text": "How should personal data be anonymised or protected?", "ngoText": "How should personal data be anonymised or protected?" } ], "complexityFactors": { "relationships": 2, "operationalChange": 2, "dataCompliance": 4 }, "securityTier": "B", "suggestedCriteria": [ { "id": "SC-C049-ANON", "name": "Data Anonymisation Rigour", "description": "This measures how strong the anonymisation is. Re-identification attacks can be resisted. Research data on vulnerable populations must withstand sophisticated de-anonymisation attempts.", "weight": 0.3, "ratingGuide": { "5": "Formal differential privacy guarantees with configurable epsilon. Provable resistance to re-identification including linkage attacks. Published privacy analysis.", "4": "K-anonymity and l-diversity implemented. Configurable privacy parameters. Tested against common re-identification attacks.", "3": "Standard anonymisation \u2014 removes direct identifiers. Quasi-identifier suppression or generalisation available.", "2": "Basic de-identification \u2014 removes names and obvious identifiers. No protection against quasi-identifier linkage.", "1": "Pseudonymisation only \u2014 reversible mapping. No true anonymisation." } }, { "id": "SC-C049-ACCESS", "name": "Tiered Research Access Controls", "description": "Does the solution support different access levels for different research purposes, from aggregate statistics to record-level data with varying privacy protections?", "weight": 0.25, "ratingGuide": { "5": "Multi-tier access: public aggregate statistics, restricted anonymised microdata, highly restricted identifiable data. Each tier with appropriate privacy controls. Ethics committee approval integration.", "4": "Three access tiers with configurable privacy levels. Approval workflows for higher-tier access.", "3": "Two access levels \u2014 aggregate and detailed. Manual approval for detailed access.", "2": "Single access level with role-based controls. No tiered privacy approach.", "1": "Binary access \u2014 full data or no data. No tiered access model." } }, { "id": "SC-C049-CONSENT", "name": "Research Consent Management", "description": "Does the solution manage research-specific consent (informed consent for studies, withdrawal rights, and consent scope limitations)?", "weight": 0.2, "ratingGuide": { "5": "Research-specific consent workflows with IRB/ethics integration. Consent tied to specific studies. Automatic data removal on withdrawal. Supports broad and narrow consent models.", "4": "Study-specific consent tracking. Withdrawal supported with data removal. Ethics approval linked to data access.", "3": "General consent management adaptable for research. Withdrawal possible but manual. No ethics board integration.", "2": "Basic consent recording. Research consent not differentiated from general consent.", "1": "No research-specific consent features." } }, { "id": "SC-C049-REPRO", "name": "Research Reproducibility Support", "description": "Does the solution support research reproducibility (versioned datasets, data provenance tracking, and methodology documentation)?", "weight": 0.15, "ratingGuide": { "5": "Versioned datasets with full provenance chain. Every transformation documented. Researchers can reproduce analyses from the exact dataset version used.", "4": "Dataset versioning and basic provenance tracking. Snapshots available for reproducibility.", "3": "Point-in-time data exports. Manual versioning. Some provenance metadata.", "2": "Current-state data access only. No versioning. Manual documentation of data state.", "1": "No versioning, provenance, or reproducibility features." } }, { "id": "SC-C049-ETHICS", "name": "Ethical Review Integration", "description": "The solution integrates with institutional review board (IRB) or ethics committee processes. Research on vulnerable populations requires ethical oversight.", "weight": 0.1, "ratingGuide": { "5": "Built-in IRB workflow \u2014 data access gated by ethics approval. Approval status tracked. Automatic access revocation when approvals expire.", "4": "Ethics approval documented in system. Data access linked to approval status. Manual expiry management.", "3": "Ethics approval recorded as metadata. No enforcement link between approval and data access.", "2": "Ethics documentation stored separately. No system-level integration.", "1": "No ethics review integration." } } ], "procurement": { "marketMaturity": "emerging", "primaryMode": "rfq", "alternativeModes": [ "integrator-led" ], "reasoning": "Privacy-preserving research data platforms emerging.", "exampleProductCategories": [ "research-data-platform", "privacy-preserving-analytics" ], "partnerChannels": [], "lastReviewed": "2026-05-01" } }, { "id": "UC-C-050", "name": "Beneficiary feedback data integrity", "category": "C", "subcategory": "Data Integrity", "description": "Keep feedback from the people you serve in a form that staff and management cannot quietly change, so donors and evaluators can trust what was said.", "bCriteria": [ "B3" ], "requiredComponents": [ { "component": "data-layer", "description": "Feedback record storage" }, { "component": "audit-mechanism", "description": "Tamper-proof feedback records" }, { "component": "verification-mechanism", "description": "Authenticity verification" } ], "conditionalComponents": [ { "component": "consent-management", "condition": "For feedback consent" }, { "component": "anonymisation-tools", "condition": "For feedback anonymisation" } ], "crossCategoryDependencies": [], "p2TriggerConditions": { "description": "Activated when P2 shows feedback programmes + accountability focus + feedback integrity concerns", "rangeSignals": [ "feedbackProgramme >= true", "accountability >= high", "feedbackVolume >= 100+" ] }, "contextFieldsTemplate": [ { "field": "feedbackChannels", "source": "P2 community engagement", "description": "Feedback collection methods" }, { "field": "respondents", "source": "P2 programme scale", "description": "Number of respondents" }, { "field": "dataUse", "source": "P2 feedback cycle", "description": "How feedback is used" }, { "field": "integrityRisks", "source": "P0 context", "description": "Feedback manipulation concerns" } ], "implementationComplexity": "low-medium", "examples": { "note": "Community feedback mechanisms", "references": [ { "name": "RAND Corporation - Feedback Quality Standards", "url": "https://www.rand.org/", "solved": "Research-backed standards for ensuring feedback authenticity and preventing manipulation" }, { "name": "Listening to the Lowest Rung (L2R) - Oxfam", "url": "https://www.oxfam.org/en/", "solved": "Framework for authentic beneficiary feedback collection with anti-manipulation safeguards" }, { "name": "Voice and Accountability in Development - ODI", "url": "https://www.odi.org/", "solved": "Evidence on authentic feedback mechanisms and preventing beneficiary capture in feedback systems" } ] }, "solutionQuestions": [ { "id": "feedback-data-format", "type": "select", "options": [ { "label": "Structured surveys (standardized questionnaires)", "value": "structured-survey" }, { "label": "Free-text feedback (open narrative)", "value": "free-text" }, { "label": "Mixed (structured + free-text)", "value": "mixed-format" }, { "label": "Mobile-friendly short surveys", "value": "mobile-surveys" }, { "label": "Voice/video feedback (recorded)", "value": "voice-video" } ], "propertyMapping": { "structured-survey": { "technologies": [ "Survey platform", "Standardized questionnaire" ], "technologyProperties": { "format": "Likert scale, multiple choice", "analysis": "Easy quantitative analysis", "standardization": "Comparable across beneficiaries" } }, "free-text": { "technologies": [ "Text feedback interface", "Text storage" ], "technologyProperties": { "format": "Open narrative feedback", "analysis": "Qualitative analysis needed", "nuance": "Captures detailed feedback" } }, "mixed-format": { "technologies": [ "Hybrid feedback form", "Mixed analysis" ], "technologyProperties": { "format": "Structured + free-text", "analysis": "Both quantitative and qualitative", "completeness": "Best of both approaches" } }, "mobile-surveys": { "technologies": [ "Mobile survey app", "SMS surveys" ], "technologyProperties": { "delivery": "Via SMS or mobile app", "brevity": "Short questions (5-10)", "response": "High response rates" } }, "voice-video": { "technologies": [ "Voice/video recording", "Media storage" ], "technologyProperties": { "format": "Audio or video clips", "transcription": "AI transcription to text", "authenticity": "Captures tone and emotion" } } }, "prefillFrom": null, "briefSection": "Data architecture", "text": "What format do you currently use to collect and store feedback data?", "ngoText": "What format do you currently use to collect and store feedback data?" }, { "id": "feedback-authenticity", "type": "select", "options": [ { "label": "Beneficiary authentication (biometric or PIN)", "value": "authentication" }, { "label": "Random sample verification (call back and verify)", "value": "sample-verification" }, { "label": "Timestamp with location (GPS proof)", "value": "timestamp-location" }, { "label": "Digital timestamping (permanent tamper-proof proof)", "value": "blockchain-timestamp" }, { "label": "No verification (trust feedback)", "value": "no-verification" } ], "propertyMapping": { "authentication": { "technologies": [ "Beneficiary authentication", "Biometric or PIN" ], "technologyProperties": { "method": "Fingerprint, face, or PIN authentication", "proof": "Authenticator signs feedback", "nonRepudiation": "Beneficiary cannot deny feedback" } }, "sample-verification": { "technologies": [ "Random call-back system", "Verification script" ], "technologyProperties": { "sampling": "10-20% random verification", "method": "Phone call to verify feedback given", "resolution": "Investigate if discrepancy found" } }, "timestamp-location": { "technologies": [ "GPS location capture", "Timestamp logging" ], "technologyProperties": { "location": "GPS coordinates when feedback given", "timestamp": "Exact time feedback submitted", "verification": "Verify beneficiary was at location" } }, "blockchain-timestamp": { "technologies": [ "Blockchain timestamping", "Hash anchoring" ], "technologyProperties": { "timestamp": "Feedback hash anchored to blockchain", "immutability": "Cannot be backdated", "transparency": "Verifiable timestamp" } }, "no-verification": { "technologies": [ "No verification system", "Accept as-is" ], "technologyProperties": { "verification": "None", "risk": "Fabricated feedback possible", "consequence": "Decision-making on false data" } } }, "prefillFrom": null, "briefSection": "Data integrity", "text": "How do you currently verify that feedback is authentic?", "ngoText": "How do you currently verify that feedback is authentic?" }, { "id": "feedback-anonymity", "type": "select", "options": [ { "label": "Fully anonymous (no identification possible)", "value": "fully-anonymous" }, { "label": "Pseudonymous (coded identifier, linked separately)", "value": "pseudonymous" }, { "label": "Identified (attribution to beneficiary)", "value": "identified" }, { "label": "Optional: beneficiary chooses", "value": "optional" }, { "label": "Anonymous in reporting (identified internally only)", "value": "reporting-anon" } ], "propertyMapping": { "fully-anonymous": { "technologies": [ "Anonymous feedback collection", "No identification" ], "technologyProperties": { "identification": "Zero ability to identify feedback source", "protection": "Complete privacy", "consequence": "Cannot follow up with beneficiary" } }, "pseudonymous": { "technologies": [ "Pseudonym assignment", "Mapping service" ], "technologyProperties": { "identification": "Coded ID (e.g., 'Beneficiary-847')", "reversal": "Can be reversed with master key (restricted access)", "balance": "Privacy with some accountability" } }, "identified": { "technologies": [ "Identified feedback form", "Attribution" ], "technologyProperties": { "attribution": "Feedback attributed to named beneficiary", "accountability": "High accountability", "risk": "Beneficiary may self-censor" } }, "optional": { "technologies": [ "Optional identification field", "Choice control" ], "technologyProperties": { "choice": "Beneficiary chooses named or anonymous", "flexibility": "Accommodates different preferences", "balance": "Best of both worlds" } }, "reporting-anon": { "technologies": [ "Identified collection, anonymous reporting", "Reporting anonymization" ], "technologyProperties": { "collection": "Collected with identification", "reporting": "Presented as anonymous in reports", "audit": "Internal audit trail maintained" } } }, "prefillFrom": null, "briefSection": "Privacy and encryption", "text": "Should beneficiary feedback be anonymous or identified?", "ngoText": "Should beneficiary feedback be anonymous or identified?" }, { "id": "feedback-manipulation-prevention", "type": "select", "options": [ { "label": "Multiple feedback rounds (cross-check consistency)", "value": "multiple-rounds" }, { "label": "Machine learning anomaly detection (flag suspicious patterns)", "value": "ml-detection" }, { "label": "Independent collectors (no staff collecting from own beneficiaries)", "value": "independent-collectors" }, { "label": "Third-party verification (external evaluators)", "value": "third-party" }, { "label": "No specific protection (assume honesty)", "value": "no-protection" } ], "propertyMapping": { "multiple-rounds": { "technologies": [ "Longitudinal feedback system", "Consistency checker" ], "technologyProperties": { "rounds": "Feedback collected multiple times", "comparison": "Compare consistency across rounds", "detection": "Major changes suggest manipulation" } }, "ml-detection": { "technologies": [ "ML anomaly detection", "Feedback analysis" ], "technologyProperties": { "training": "Trained on known manipulated feedback", "detection": "Identifies suspicious patterns", "adaptation": "Learns new manipulation types" } }, "independent-collectors": { "technologies": [ "External feedback collector network", "Collector assignment" ], "technologyProperties": { "collectors": "Not program staff", "independence": "No relationship with beneficiary", "benefit": "Reduces beneficiary pressure to please" } }, "third-party": { "technologies": [ "Third-party evaluator", "External assessment" ], "technologyProperties": { "evaluation": "Independent external evaluator", "impartiality": "No program bias", "credibility": "High credibility assessment" } }, "no-protection": { "technologies": [ "No protection mechanism", "Accept feedback as-is" ], "technologyProperties": { "manipulation": "Possible", "risk": "Fabricated feedback not detected", "consequence": "Misleading findings" } } }, "prefillFrom": null, "briefSection": "Data integrity", "text": "What is your current approach to preventing feedback manipulation?", "ngoText": "What is your current approach to preventing feedback manipulation?" }, { "id": "beneficiary-feedback-stakeholders", "type": "select", "options": [ { "label": "Internal only (1\u20132 teams)", "value": "internal" }, { "label": "Internal + 1\u20133 external partners", "value": "few-external" }, { "label": "Multiple external stakeholders (4\u201310)", "value": "multi-external" }, { "label": "Ecosystem-wide (donors, partners, beneficiaries, regulators)", "value": "ecosystem" } ], "propertyMapping": { "internal": { "technologies": [ "Private ledger" ], "technologyProperties": { "accessControl": "Simple role-based", "networkType": "Private" } }, "few-external": { "technologies": [ "Permissioned network", "Selective data sharing" ], "technologyProperties": { "accessControl": "Partner-level permissions", "networkType": "Consortium" } }, "multi-external": { "technologies": [ "Permissioned network", "Multi-party access layer" ], "technologyProperties": { "accessControl": "Granular role-based", "networkType": "Consortium" } }, "ecosystem": { "technologies": [ "Permissioned public network", "Data marketplace" ], "technologyProperties": { "accessControl": "Multi-tier with public layer", "networkType": "Hybrid public-private" } } }, "prefillFrom": null, "briefSection": "Governance and access", "text": "How many distinct parties need visibility into the beneficiary feedback data data?", "ngoText": "How many distinct parties need visibility into the beneficiary feedback data data?" }, { "id": "beneficiary-choice", "label": "How will beneficiaries exercise choice in how they receive and use this service?", "type": "select", "briefSection": "Consent management", "options": [ { "label": "Beneficiaries choose between delivery methods (cash, voucher, mobile money, direct)", "value": "delivery-choice" }, { "label": "Beneficiaries choose preferred merchants or service points", "value": "merchant-choice" }, { "label": "Beneficiaries control their own data sharing preferences", "value": "data-choice" }, { "label": "Multiple choice dimensions (delivery + merchant + data)", "value": "full-choice" }, { "label": "Limited choice: programme constraints determine delivery", "value": "limited" } ], "propertyMapping": { "delivery-choice": { "technologies": [], "technologyProperties": { "beneficiaryChoice": "Delivery method choice", "dignityDesign": "Beneficiaries select preferred receipt method" } }, "merchant-choice": { "technologies": [], "technologyProperties": { "beneficiaryChoice": "Merchant/service point choice", "dignityDesign": "Beneficiaries select where to redeem" } }, "data-choice": { "technologies": [], "technologyProperties": { "beneficiaryChoice": "Data sharing choice", "dignityDesign": "Beneficiaries control personal data sharing" } }, "full-choice": { "technologies": [], "technologyProperties": { "beneficiaryChoice": "Multi-dimensional choice", "dignityDesign": "Full beneficiary agency across delivery, merchant, and data" } }, "limited": { "technologies": [], "technologyProperties": { "beneficiaryChoice": "Limited by programme design", "dignityDesign": "Programme constraints; beneficiary informed of reasons" } } }, "text": "How will beneficiaries exercise choice in how they receive and use this service?" } ], "complexityFactors": { "relationships": 2, "operationalChange": 2, "dataCompliance": 2 }, "suggestedCriteria": [ { "id": "SC-C050-AUTHENTIC", "name": "Feedback Authenticity Verification", "description": "Can the system verify that feedback genuinely came from beneficiaries rather than being fabricated or manipulated by staff?", "weight": 0.3, "ratingGuide": { "5": "Cryptographic proof of feedback origin without revealing identity. Prevents fabrication while protecting anonymity. Time-stamped and location-verified.", "4": "Feedback linked to verified beneficiary interaction. Difficult to fabricate. Timestamp and basic origin verification.", "3": "Feedback submitted through authenticated channels. Some protection against fabrication but not cryptographic.", "2": "Feedback collected through standard forms. Basic authentication. Staff could plausibly submit fabricated feedback.", "1": "Unverified feedback collection. No mechanism to distinguish genuine from fabricated responses." } }, { "id": "SC-C050-ANON", "name": "Anonymous Feedback Protection", "description": "Beneficiaries can provide genuinely anonymous feedback. Anonymity is critical for honest feedback, especially when feedback may be critical of service providers.", "weight": 0.25, "ratingGuide": { "5": "Cryptographically anonymous \u2014 system can prove feedback is from a legitimate beneficiary without identifying them. Even system administrators cannot link feedback to individuals.", "4": "Strong anonymity with technical protections. Pseudonymous submission. De-anonymisation extremely difficult.", "3": "Anonymous submission option available. System stores minimal metadata. De-anonymisation unlikely but theoretically possible.", "2": "Feedback nominally anonymous but metadata (timestamps, locations, device IDs) could enable identification.", "1": "All feedback linked to identified beneficiaries. No anonymous submission option." } }, { "id": "SC-C050-TAMPER", "name": "Feedback Record Immutability", "description": "This looks at whether feedback can be altered or selectively deleted once it is recorded. Accountability requires that negative feedback cannot be suppressed.", "weight": 0.2, "ratingGuide": { "5": "Cryptographic immutability. Feedback cannot be altered or deleted by anyone including system administrators. Deletions detectable.", "4": "Tamper-evident storage. Modifications create visible audit entries. Deletion logged and detectable.", "3": "Append-only storage for feedback records. Modifications tracked. Admin deletion possible but logged.", "2": "Standard database with change logging. Deletion by admin possible and logged but logs and records in same system.", "1": "Standard database. Feedback can be modified or deleted without trace." } }, { "id": "SC-C050-CHANNEL", "name": "Multi-channel Feedback Collection", "description": "Does the solution support multiple feedback channels (SMS, voice, mobile app, in-person) to reach beneficiaries with varying technology access?", "weight": 0.15, "ratingGuide": { "5": "SMS, voice (IVR), mobile app, web, and in-person collection. All channels feed into the same tamper-proof system. Designed for low-connectivity and low-literacy populations.", "4": "Multiple digital channels (SMS, app, web) with in-person option. Unified data store. Most beneficiary contexts covered.", "3": "Two to three channels (e.g. app and SMS). Unified storage. Some populations may be excluded.", "2": "Single digital channel (app or web). In-person collection requires manual data entry.", "1": "Single channel only. Significant portions of the beneficiary population likely excluded." } }, { "id": "SC-C050-ACTION", "name": "Feedback-to-Action Workflow", "description": "The solution helps organisations act on feedback. Integrity without action is meaningless. The system should close the feedback loop.", "weight": 0.1, "ratingGuide": { "5": "Automated triage, escalation rules, response tracking, and closure verification. Feedback loop completion rates tracked. Beneficiaries notified of outcomes.", "4": "Triage and assignment workflow. Response tracking. Basic completion metrics.", "3": "Feedback categorisation and assignment. Manual tracking of responses.", "2": "Feedback stored for review. No workflow for response or follow-up.", "1": "Feedback collected but no mechanism for organisational response." } } ], "procurement": { "marketMaturity": "mature", "primaryMode": "off-the-shelf", "alternativeModes": [ "conversation-guide" ], "reasoning": "Beneficiary feedback SaaS market is mature.", "exampleProductCategories": [ "feedback-platform", "community-engagement-saas" ], "partnerChannels": [], "lastReviewed": "2026-05-01" } }, { "id": "UC-C-051", "name": "Needs assessment data integrity", "category": "C", "subcategory": "Data Integrity", "description": "Keep needs assessment results in a form that cannot be changed unnoticed, so donors and partners can trust the figures used to target aid.", "bCriteria": [ "B3" ], "requiredComponents": [ { "component": "data-layer", "description": "Assessment data storage" }, { "component": "audit-mechanism", "description": "Data collection audit trail" }, { "component": "verification-mechanism", "description": "Assessment authenticity" } ], "conditionalComponents": [ { "component": "smart-contracts", "condition": "If automated assessment rules" }, { "component": "oracle-data", "condition": "If external verification data" } ], "crossCategoryDependencies": [], "p2TriggerConditions": { "description": "Activated when P2 shows baseline assessment + data integrity concerns + targeting validation", "rangeSignals": [ "assessments >= true", "integrityRisks >= true", "targetingAccuracy >= important" ] }, "contextFieldsTemplate": [ { "field": "beneficiaries", "source": "P2 assessment scope", "description": "Number assessed" }, { "field": "indicators", "source": "P2 needs assessment", "description": "Assessed indicators" }, { "field": "dataCollection", "source": "P2 M&E methods", "description": "Collection methodology" }, { "field": "integrityRisks", "source": "P0 context", "description": "Potential manipulation risks" } ], "implementationComplexity": "low-medium", "examples": { "note": "Needs assessment quality standards", "references": [ { "name": "World Bank Poverty Measurement Toolkit", "url": "https://www.worldbank.org/en/topic/poverty", "solved": "Standards for needs assessment data collection with quality assurance" }, { "name": "UNICEF MICS (Multiple Indicator Cluster Survey)", "url": "https://mics.unicef.org/", "solved": "Standardised survey methodology with field quality control protocols for needs assessment" }, { "name": "ODK (Open Data Kit) - Data Quality Module", "url": "https://getodk.org/", "solved": "Open-source tools for offline data collection with built-in quality checks and verification" } ] }, "solutionQuestions": [ { "id": "needs-assessment-data-collection", "type": "select", "options": [ { "label": "Offline-first mobile app (collect without connectivity)", "value": "offline-mobile" }, { "label": "Web-based platform (cloud-based, real-time)", "value": "web-platform" }, { "label": "Paper forms with digital transcription", "value": "paper-digital" }, { "label": "Oral interviews with transcript", "value": "oral-interviews" }, { "label": "Hybrid (multiple collection methods)", "value": "hybrid-collection" } ], "propertyMapping": { "offline-mobile": { "technologies": [ "Offline-capable mobile app", "Local encryption" ], "technologyProperties": { "collection": "App works offline", "encryption": "Local encryption of data", "sync": "Sync when connectivity available", "security": "Data protected on device" } }, "web-platform": { "technologies": [ "Web form platform", "TLS encryption" ], "technologyProperties": { "collection": "Real-time web-based", "encryption": "TLS in transit, encryption at rest", "requirement": "Connectivity required", "scalability": "Easily scalable" } }, "paper-digital": { "technologies": [ "Paper forms", "OCR transcription" ], "technologyProperties": { "collection": "Physical paper forms", "transcription": "AI-based OCR or manual entry", "archival": "Paper archived, digital stored" } }, "oral-interviews": { "technologies": [ "Audio recording", "Transcript generation" ], "technologyProperties": { "collection": "Enumerator conducts interview", "recording": "Audio recorded with consent", "transcription": "AI or manual transcription" } }, "hybrid-collection": { "technologies": [ "Multi-channel collection platform", "Data unification" ], "technologyProperties": { "methods": "Multiple collection methods", "unification": "Unified database from all sources", "flexibility": "Accommodates different contexts" } } }, "prefillFrom": null, "briefSection": "Data architecture", "text": "How do you currently collect and store needs assessment data?", "ngoText": "How do you currently collect and store needs assessment data?" }, { "id": "assessment-authenticity", "type": "select", "options": [ { "label": "Consistency checks (compare against other surveys)", "value": "consistency-checks" }, { "label": "Beneficiary re-interview (verify responses)", "value": "reinterview" }, { "label": "Community cross-checks (community confirms data)", "value": "community-checks" }, { "label": "Sensor verification (e.g., measure income via WiFi access)", "value": "sensor-verify" }, { "label": "No verification (trust data as submitted)", "value": "no-verification" } ], "propertyMapping": { "consistency-checks": { "technologies": [ "Data consistency engine", "Statistical analyzer" ], "technologyProperties": { "checking": "Compare against similar beneficiaries", "flagging": "Flag outliers and inconsistencies", "investigation": "Investigate suspicious data" } }, "reinterview": { "technologies": [ "Re-interview system", "Survey comparison" ], "technologyProperties": { "reinterview": "Random sample re-interviewed", "comparison": "Responses compared with original", "resolution": "Investigate major discrepancies" } }, "community-checks": { "technologies": [ "Community validation system", "Community review" ], "technologyProperties": { "validation": "Community members review data", "consensus": "Community confirms or disputes", "perspective": "Leverages community knowledge" } }, "sensor-verify": { "technologies": [ "IoT sensors", "Indirect verification" ], "technologyProperties": { "sensors": "Measure indicators (e.g., WiFi for wealth)", "correlation": "Compare sensor data with survey", "privacy": "Indirect data less privacy-invasive" } }, "no-verification": { "technologies": [ "No verification", "Accept as-is" ], "technologyProperties": { "verification": "None", "risk": "Fabricated data not detected", "consequence": "Poor targeting" } } }, "prefillFrom": null, "briefSection": "Data integrity", "text": "How do you currently verify the authenticity of needs assessment data?", "ngoText": "How do you currently verify the authenticity of needs assessment data?" }, { "id": "assessment-data-retention", "type": "select", "options": [ { "label": "Until program ends (then delete)", "value": "program-duration" }, { "label": "2-3 years for impact evaluation", "value": "three-years" }, { "label": "5-7 years for audit and compliance", "value": "five-years" }, { "label": "Permanent archival for longitudinal research", "value": "permanent" }, { "label": "Beneficiary-controlled (beneficiary can request deletion)", "value": "beneficiary-controlled" } ], "propertyMapping": { "program-duration": { "technologies": [ "Program lifecycle management", "Auto-deletion on exit" ], "technologyProperties": { "retention": "Active program duration only", "deletion": "Deleted when program ends", "privacy": "Minimal long-term storage" } }, "three-years": { "technologies": [ "3-year retention schedule", "Archive system" ], "technologyProperties": { "retention": "3 years from collection", "impact": "Allows mid-term impact evaluation", "deletion": "Automatic deletion after period" } }, "five-years": { "technologies": [ "5-year retention schedule", "Compliance archive" ], "technologyProperties": { "retention": "5-7 years standard", "audit": "Audit trail preserved", "deletion": "Moved to archive after 7 years" } }, "permanent": { "technologies": [ "Permanent archive", "Cold storage" ], "technologyProperties": { "retention": "Permanent", "useCase": "Longitudinal research possible", "access": "Limited to research purposes" } }, "beneficiary-controlled": { "technologies": [ "Right-to-deletion interface", "Deletion service" ], "technologyProperties": { "request": "Beneficiary can request deletion", "compliance": "GDPR right to be forgotten", "immediacy": "Deletion within days" } } }, "prefillFrom": null, "briefSection": "Data integrity", "text": "How long should needs assessment data be retained?", "ngoText": "How long should needs assessment data be retained?" }, { "id": "needs-assessment-stakeholders", "type": "select", "options": [ { "label": "Internal only (1\u20132 teams)", "value": "internal" }, { "label": "Internal + 1\u20133 external partners", "value": "few-external" }, { "label": "Multiple external stakeholders (4\u201310)", "value": "multi-external" }, { "label": "Ecosystem-wide (donors, partners, beneficiaries, regulators)", "value": "ecosystem" } ], "propertyMapping": { "internal": { "technologies": [ "Private ledger" ], "technologyProperties": { "accessControl": "Simple role-based", "networkType": "Private" } }, "few-external": { "technologies": [ "Permissioned network", "Selective data sharing" ], "technologyProperties": { "accessControl": "Partner-level permissions", "networkType": "Consortium" } }, "multi-external": { "technologies": [ "Permissioned network", "Multi-party access layer" ], "technologyProperties": { "accessControl": "Granular role-based", "networkType": "Consortium" } }, "ecosystem": { "technologies": [ "Permissioned public network", "Data marketplace" ], "technologyProperties": { "accessControl": "Multi-tier with public layer", "networkType": "Hybrid public-private" } } }, "prefillFrom": null, "briefSection": "Governance and access", "text": "How many distinct parties need visibility into the needs assessment data data?", "ngoText": "How many distinct parties need visibility into the needs assessment data data?" }, { "id": "sq-UC-C-051-003", "type": "single-select", "options": [ { "value": "triangulation-with-secondary-data", "label": "Triangulation with secondary data" }, { "value": "household-revisit", "label": "Household revisit" }, { "value": "community-validation", "label": "Community validation" }, { "value": "statistical-outlier-detection", "label": "Statistical outlier detection" }, { "value": "enumerator-cross-check", "label": "Enumerator cross-check" } ], "propertyMapping": { "triangulation-with-secondary-data": { "technologies": [ "data-integration", "correlation-analysis" ], "technologyProperties": {} }, "household-revisit": { "technologies": [ "revisit-sampling", "verification-survey" ], "technologyProperties": {} }, "community-validation": { "technologies": [ "community-verification", "feedback-loop" ], "technologyProperties": {} }, "statistical-outlier-detection": { "technologies": [ "statistical-analysis", "anomaly-detection" ], "technologyProperties": {} }, "enumerator-cross-check": { "technologies": [ "peer-review", "enumerator-validation" ], "technologyProperties": {} } }, "briefSection": "requirements", "text": "What cross-validation should be applied to needs assessment responses?", "ngoText": "What cross-validation should be applied to needs assessment responses?" }, { "id": "audit-mechanism-approach", "type": "select", "options": [ { "label": "Automatic checks that flag problems as they happen", "value": "automated-realtime" }, { "label": "Regular scheduled reviews with tamper-proof records", "value": "periodic-batch" }, { "label": "Ability to check any record at any time with proof it has not been altered", "value": "on-demand" }, { "label": "External auditors can log in and review records independently", "value": "third-party" } ], "propertyMapping": { "automated-realtime": { "technologies": [ "Real-time audit mechanism", "Automated anomaly detection", "Audit alert service" ], "technologyProperties": { "auditFrequency": "Continuous / real-time", "auditAccess": "System-generated alerts", "complianceReporting": "Automated" } }, "periodic-batch": { "technologies": [ "Periodic audit mechanism", "Batch verification engine", "Audit report generator" ], "technologyProperties": { "auditFrequency": "Scheduled (daily/weekly/monthly)", "auditAccess": "Generated audit reports", "complianceReporting": "Scheduled" } }, "on-demand": { "technologies": [ "On-demand audit mechanism", "Audit query interface", "Record verification service" ], "technologyProperties": { "auditFrequency": "On-demand", "auditAccess": "Query-based", "complianceReporting": "On request" } }, "third-party": { "technologies": [ "Third-party audit mechanism", "Auditor access portal", "Audit evidence export" ], "technologyProperties": { "auditFrequency": "As required by auditor", "auditAccess": "Dedicated portal with read-only access", "complianceReporting": "Auditor-directed" } } }, "prefillFrom": null, "briefSection": "Audit and verification", "text": "Who needs to verify that actions happened correctly, and how easily should they be able to check?", "ngoText": "How should auditing and verification work for this solution?" }, { "id": "beneficiary-choice", "label": "How will beneficiaries exercise choice in how they receive and use this service?", "type": "select", "briefSection": "Consent management", "options": [ { "label": "Beneficiaries choose between delivery methods (cash, voucher, mobile money, direct)", "value": "delivery-choice" }, { "label": "Beneficiaries choose preferred merchants or service points", "value": "merchant-choice" }, { "label": "Beneficiaries control their own data sharing preferences", "value": "data-choice" }, { "label": "Multiple choice dimensions (delivery + merchant + data)", "value": "full-choice" }, { "label": "Limited choice: programme constraints determine delivery", "value": "limited" } ], "propertyMapping": { "delivery-choice": { "technologies": [], "technologyProperties": { "beneficiaryChoice": "Delivery method choice", "dignityDesign": "Beneficiaries select preferred receipt method" } }, "merchant-choice": { "technologies": [], "technologyProperties": { "beneficiaryChoice": "Merchant/service point choice", "dignityDesign": "Beneficiaries select where to redeem" } }, "data-choice": { "technologies": [], "technologyProperties": { "beneficiaryChoice": "Data sharing choice", "dignityDesign": "Beneficiaries control personal data sharing" } }, "full-choice": { "technologies": [], "technologyProperties": { "beneficiaryChoice": "Multi-dimensional choice", "dignityDesign": "Full beneficiary agency across delivery, merchant, and data" } }, "limited": { "technologies": [], "technologyProperties": { "beneficiaryChoice": "Limited by programme design", "dignityDesign": "Programme constraints; beneficiary informed of reasons" } } }, "text": "How will beneficiaries exercise choice in how they receive and use this service?" } ], "complexityFactors": { "relationships": 2, "operationalChange": 2, "dataCompliance": 2 }, "suggestedCriteria": [ { "id": "SC-C051-COLLECT", "name": "Field Data Collection Integrity", "description": "Does the solution ensure that needs assessment data is accurately captured in field conditions, preventing transcription errors, timestamp manipulation, and location spoofing?", "weight": 0.3, "ratingGuide": { "5": "Automated integrity checks at point of collection \u2014 GPS verification, timestamp anchoring, photo/audio evidence, enumerator identity verification. Tamper-proof from the moment of capture.", "4": "GPS and timestamp captured automatically. Basic integrity checks. Enumerator tracking. Some tamper protections at collection point.", "3": "Standard mobile data collection with GPS and timestamps. No active integrity verification at collection point.", "2": "Digital forms with manual location and time entry. No automated integrity checks.", "1": "Paper-based or basic digital forms with no integrity protections at collection." } }, { "id": "SC-C051-CHAIN", "name": "Data Chain of Custody", "description": "Every step from collection to analysis to reporting is tracked. Needs assessment data often passes through multiple hands and systems before informing decisions.", "weight": 0.25, "ratingGuide": { "5": "Complete chain of custody \u2014 every transformation, aggregation, and transfer cryptographically logged. Original data preserved alongside processed versions.", "4": "Key processing steps logged with integrity proofs. Original and processed data linked. Major transformations tracked.", "3": "Processing steps logged. Version history maintained. Some gaps in transformation tracking.", "2": "Final processed data stored with basic provenance metadata. Processing steps not individually tracked.", "1": "Only final processed data available. No chain of custody from collection to analysis." } }, { "id": "SC-C051-TOOL", "name": "Assessment Tool Integration", "description": "Does the solution integrate with the standard needs assessment and survey data collection tools used by humanitarian organisations?", "weight": 0.2, "ratingGuide": { "5": "Native integration with the standard survey data collection tools. Data flows automatically from collection tool to integrity layer. No workflow disruption.", "4": "API integration with major assessment tools. Automated data import with minor configuration.", "3": "Standard import formats supported. Integration requires custom connector development.", "2": "CSV/spreadsheet import. Manual data transfer from assessment tools.", "1": "Standalone system. No integration with existing assessment tools." } }, { "id": "SC-C051-CROSS", "name": "Cross-assessment Comparison Integrity", "description": "Can the solution verify that data from multiple assessments (baseline, midline, endline) was collected consistently and hasn't been manipulated to show artificial improvement?", "weight": 0.15, "ratingGuide": { "5": "Temporal integrity \u2014 baseline data locked at collection time. Midline/endline cannot retroactively alter baselines. Methodology consistency verified automatically.", "4": "Assessment versions locked after collection. Cross-assessment comparison with integrity proofs. Methodology changes documented.", "3": "Historical assessments preserved. Comparison possible but methodology consistency is manually verified.", "2": "Previous assessment data available for comparison but no integrity guarantees on historical data.", "1": "No cross-assessment integrity features. Each assessment standalone." } }, { "id": "SC-C051-QUALITY", "name": "Data Quality Assurance", "description": "Does the solution include built-in data quality checks (outlier detection, consistency validation, and completeness monitoring during and after collection)?", "weight": 0.1, "ratingGuide": { "5": "Real-time quality checks during collection. Automated outlier detection, consistency rules, and completeness monitoring. Quality scores per enumerator and per region.", "4": "Post-collection quality checks with automated outlier detection. Completeness monitoring. Quality metrics available.", "3": "Basic validation rules (range checks, required fields). Manual quality review process.", "2": "Standard form validation only. No analytical quality checks.", "1": "No data quality features beyond basic form submission." } } ], "procurement": { "marketMaturity": "mature", "primaryMode": "off-the-shelf", "alternativeModes": [ "conversation-guide" ], "reasoning": "Needs assessment tooling included in many M&E SaaS.", "exampleProductCategories": [ "needs-assessment-platform", "m-and-e-saas" ], "partnerChannels": [], "lastReviewed": "2026-05-01" } }, { "id": "UC-D-052", "name": "Medicine authenticity verification (anti-counterfeiting)", "category": "D", "subcategory": "Product Authentication", "description": "Let clinics and distributors check that a medicine is genuine and came from the stated manufacturer, to keep counterfeit or substandard stock out of the supply chain.", "bCriteria": [ "B3", "B4" ], "requiredComponents": [ { "component": "tracking-platform", "description": "Medicine lot tracking" }, { "component": "qr-barcode", "description": "QR codes on medicine packaging" }, { "component": "provenance-verification", "description": "Authenticity verification" }, { "component": "audit-mechanism", "description": "Distribution audit trail" } ], "conditionalComponents": [ { "component": "iot-sensors", "condition": "If temperature monitoring during transport" } ], "crossCategoryDependencies": [ "UC-D-053 if cold chain monitoring needed" ], "p2TriggerConditions": { "description": "Activated when P2 shows medicine procurement + counterfeiting concerns + supply chain opacity", "rangeSignals": [ "medicineVolume >= high", "counterfeitRisk >= high", "supplyChainTransparency <= low" ] }, "contextFieldsTemplate": [ { "field": "medicineTypes", "source": "P2 health programmes", "description": "Types of medicines" }, { "field": "suppliers", "source": "P2 supply chain", "description": "Number of suppliers" }, { "field": "volume", "source": "P2 procurement", "description": "Annual medicine volume" }, { "field": "riskAreas", "source": "P0 context", "description": "Counterfeiting risk level" } ], "implementationComplexity": "medium", "examples": { "note": "Pharmaceuticals supply chain, WHO medicine authentication", "references": [ { "name": "World Health Organization (WHO) Medicines Authentication", "url": "https://www.who.int/medicines/anti-counterfeiting", "solved": "Established global standards for medicine authentication and supply chain verification" }, { "name": "Verify Project by Roche", "url": "https://www.roche.com/sustainability/supply-chain-transparency", "solved": "Implemented blockchain-based medicine authenticity verification for 15+ countries" }, { "name": "Ulusom Technology - Pharmaceutical Supply Chain", "url": "https://ulusom.com/pharmaceutical-traceability", "solved": "End-to-end medicine tracking with QR serialisation for NGO programmes" } ] }, "solutionQuestions": [ { "id": "medicine-tracking-granularity", "type": "select", "options": [ { "label": "Individual unit/blister pack", "value": "individual-unit" }, { "label": "Batch/lot level", "value": "batch-level" }, { "label": "Carton/case level", "value": "carton-level" } ], "propertyMapping": { "individual-unit": { "technologies": [ "Item-level serialisation engine", "Unique identifier generation system" ], "technologyProperties": { "serialisationFormat": "GTIN-14", "trackingResolution": "unit-level", "dataCarrier": "QR or barcode per unit" } }, "batch-level": { "technologies": [ "Batch tracking platform", "Lot numbering engine" ], "technologyProperties": { "serialisationFormat": "Batch/Lot ID", "trackingResolution": "batch-level", "dataCarrier": "QR code per batch" } }, "carton-level": { "technologies": [ "Case-level tracking system", "Logistics management engine" ], "technologyProperties": { "serialisationFormat": "Case ID", "trackingResolution": "carton-level", "dataCarrier": "Barcode per case" } } }, "prefillFrom": null, "briefSection": "Tracking and provenance", "text": "At what granularity level do you currently track medicines in your supply chain?", "ngoText": "At what granularity level do you currently track medicines in your supply chain?" }, { "id": "verification-points-count", "type": "select", "options": [ { "label": "2-3 critical verification points", "value": "minimal-points" }, { "label": "5-7 verification points", "value": "moderate-points" }, { "label": "10+ verification points throughout supply chain", "value": "comprehensive-points" } ], "propertyMapping": { "minimal-points": { "technologies": [ "Verification checkpoint system", "Supply chain audit engine" ], "technologyProperties": { "checkpointCount": "2-3", "locations": [ "factory", "distributor", "pharmacy" ], "automationLevel": "manual-verification" } }, "moderate-points": { "technologies": [ "Multi-checkpoint verification platform", "Intermediate audit system" ], "technologyProperties": { "checkpointCount": "5-7", "locations": [ "factory", "warehouse", "distributor", "regional", "pharmacy" ], "automationLevel": "semi-automated" } }, "comprehensive-points": { "technologies": [ "End-to-end verification network", "Continuous monitoring platform" ], "technologyProperties": { "checkpointCount": "10+", "locations": [ "all-nodes" ], "automationLevel": "fully-automated" } } }, "prefillFrom": null, "briefSection": "Verification and authentication", "text": "How many verification points are currently in your medicine supply chain?", "ngoText": "How many verification points are currently in your medicine supply chain?" }, { "id": "counterfeit-risk-level", "type": "select", "options": [ { "label": "Low risk - established manufacturers", "value": "low-risk" }, { "label": "Medium risk - variable supplier base", "value": "medium-risk" }, { "label": "High risk - known counterfeiting areas", "value": "high-risk" } ], "propertyMapping": { "low-risk": { "technologies": [ "Standard authenticity verification", "Basic tracking platform" ], "technologyProperties": { "verificationFrequency": "periodic", "riskMitigation": "standard-controls", "investmentLevel": "minimal" } }, "medium-risk": { "technologies": [ "Enhanced authentication system", "Advanced tracking platform" ], "technologyProperties": { "verificationFrequency": "regular", "riskMitigation": "advanced-controls", "investmentLevel": "moderate" } }, "high-risk": { "technologies": [ "Advanced anti-counterfeiting technology", "Real-time verification platform" ], "technologyProperties": { "verificationFrequency": "continuous", "riskMitigation": "maximum-controls", "investmentLevel": "high" } } }, "prefillFrom": null, "briefSection": "Quality assurance", "text": "What is your assessed counterfeit risk level for your medicines?", "ngoText": "What is your assessed counterfeit risk level for your medicines?" }, { "id": "reporting-requirements", "type": "select", "options": [ { "label": "Basic inventory and distribution reporting", "value": "basic-reporting" }, { "label": "Regulatory compliance reporting", "value": "regulatory-reporting" }, { "label": "Real-time transparency and stakeholder reporting", "value": "realtime-reporting" } ], "propertyMapping": { "basic-reporting": { "technologies": [ "Standard reporting engine", "Audit trail system" ], "technologyProperties": { "reportingFrequency": "monthly", "stakeHolders": [ "internal-teams" ], "complianceStandard": "internal-policy" } }, "regulatory-reporting": { "technologies": [ "Regulatory compliance reporting platform", "Audit documentation system" ], "technologyProperties": { "reportingFrequency": "quarterly", "stakeHolders": [ "regulators", "internal-teams" ], "complianceStandard": "WHO, national-regulations" } }, "realtime-reporting": { "technologies": [ "Real-time analytics dashboard", "Stakeholder notification system" ], "technologyProperties": { "reportingFrequency": "real-time", "stakeHolders": [ "all-stakeholders", "donors", "beneficiaries" ], "complianceStandard": "international-standards" } } }, "prefillFrom": null, "briefSection": "Reporting and audit", "text": "What reporting and audit requirements must be met?", "ngoText": "What reporting and audit requirements must be met?" }, { "id": "supply-chain-transparency", "type": "select", "options": [ { "label": "Internal transparency only", "value": "internal-only" }, { "label": "Healthcare provider visibility", "value": "provider-visibility" }, { "label": "Full transparency to patients and public", "value": "full-transparency" } ], "propertyMapping": { "internal-only": { "technologies": [ "Internal tracking system", "Staff access control" ], "technologyProperties": { "accessControl": "role-based", "publicVisibility": "none", "dataSharing": "internal-only" } }, "provider-visibility": { "technologies": [ "Provider portal platform", "Controlled data sharing system" ], "technologyProperties": { "accessControl": "provider-authenticated", "publicVisibility": "limited", "dataSharing": "provider-access" } }, "full-transparency": { "technologies": [ "Public verification platform", "Patient information system" ], "technologyProperties": { "accessControl": "public", "publicVisibility": "full", "dataSharing": "public-access" } } }, "prefillFrom": null, "briefSection": "Tracking and provenance", "text": "How transparent is your current medicine supply chain to end users?", "ngoText": "How transparent is your current medicine supply chain to end users?", "hidden": true }, { "id": "item-tracking-method", "type": "select", "options": [ { "label": "QR codes printed on items or packaging", "value": "qr-codes" }, { "label": "NFC tags embedded in items", "value": "nfc-tags" }, { "label": "Barcode labels with batch scanning", "value": "barcode" }, { "label": "Mixed: QR for high-value items, barcode for bulk", "value": "mixed" } ], "propertyMapping": { "qr-codes": { "technologies": [ "QR code generation service", "QR/barcode scanning app", "Item-level tracking ledger" ], "technologyProperties": { "trackingGranularity": "Per-item or per-batch", "scanMethod": "Mobile phone camera / QR scanner", "offlineCapable": "Yes \u2014 scan and sync when connected" } }, "nfc-tags": { "technologies": [ "NFC tag provisioning", "NFC reader integration", "Item-level tracking ledger" ], "technologyProperties": { "trackingGranularity": "Per-item", "scanMethod": "NFC-enabled device", "offlineCapable": "Yes \u2014 NFC works offline" } }, "barcode": { "technologies": [ "Barcode generation service", "QR/barcode scanning app", "Batch tracking ledger" ], "technologyProperties": { "trackingGranularity": "Per-batch", "scanMethod": "Barcode scanner / mobile camera", "offlineCapable": "Yes \u2014 scan and sync" } }, "mixed": { "technologies": [ "QR code generation service", "Barcode generation service", "QR/barcode scanning app", "Multi-level tracking ledger" ], "technologyProperties": { "trackingGranularity": "Mixed \u2014 item-level for high-value, batch for bulk", "scanMethod": "Mobile phone camera / scanner", "offlineCapable": "Yes" } } }, "prefillFrom": null, "briefSection": "Item tracking", "text": "How will physical items be tracked and scanned in the field?", "ngoText": "How will physical items be tracked and scanned in the field?" } ], "complexityFactors": { "relationships": 3, "operationalChange": 2, "dataCompliance": 3 }, "suggestedCriteria": [ { "id": "SC-SERIAL", "name": "Serialisation & Track-and-Trace Capability", "description": "The provider can assign and verify unique identifiers at the individual medicine pack level throughout the supply chain. Serialisation is the backbone of anti-counterfeiting. Without per-unit tracking, authenticity claims are meaningless.", "weight": 0.3, "ratingGuide": { "5": "GS1-compliant serialisation at item level. Unique identifiers per pack with full chain-of-custody tracking from manufacturer to last-mile dispensary. Aggregation hierarchy (pack \u2192 case \u2192 pallet) supported.", "4": "Item-level serialisation with tracking across most supply chain nodes. GS1-aligned but may lack full aggregation hierarchy.", "3": "Batch-level serialisation only. Can verify authenticity of a batch but not individual packs. Basic chain-of-custody.", "2": "Simple lot-level tracking. No per-unit identifiers. Limited to verifying shipment origin only.", "1": "No serialisation capability. Relies on paper-based certificates of authenticity with no digital verification." } }, { "id": "SC-VERIFY-UX", "name": "Point-of-Dispensing Verification", "description": "This measures how easily field health workers or pharmacists can verify medicine authenticity at the point of care. In humanitarian contexts, verification must work on low-end smartphones with poor connectivity.", "weight": 0.25, "ratingGuide": { "5": "Simple smartphone scan (QR/barcode) returns instant authenticity confirmation. Works offline with cached verification data. Multilingual interface. No specialist hardware required.", "4": "Smartphone-based verification with occasional connectivity needed. Clear pass/fail result. Supports major local languages.", "3": "Requires internet connectivity for each verification. Works on smartphones but UX is technical. English-only interface.", "2": "Requires dedicated scanner hardware. Online-only verification. Technical output requiring interpretation.", "1": "No point-of-dispensing verification. Authenticity can only be checked by querying a web portal with batch numbers." } }, { "id": "SC-PHARMA-REG", "name": "Pharmaceutical Regulatory Compliance", "description": "The provider complies with relevant pharmaceutical traceability regulations (WHO guidelines, national drug regulatory authority requirements, EU FMD, US DSCSA concepts). Regulatory alignment ensures the solution is accepted by health authorities.", "weight": 0.2, "ratingGuide": { "5": "Compliant with WHO Model Guidance on traceability. Pre-integrated with national drug regulatory authority systems in operating countries. Supports DSCSA/FMD data formats.", "4": "Aligns with WHO guidelines. Can export data in regulatory formats. Some national system integrations.", "3": "Designed with pharmaceutical compliance in mind but not yet certified. Manual regulatory reporting.", "2": "Generic supply chain tool adapted for pharmaceuticals. Limited awareness of pharma-specific regulations.", "1": "No pharmaceutical regulatory compliance. General-purpose tracking with no pharma adaptations." } }, { "id": "SC-COUNTERFEIT-DETECT", "name": "Counterfeit Detection & Alert Mechanism", "description": "This covers what happens when a suspected counterfeit is detected. The system must not only verify. It must trigger actionable alerts to health authorities, quarantine suspect stock, and support investigation workflows.", "weight": 0.15, "ratingGuide": { "5": "Automated alert cascade: flags suspect product, notifies upstream supplier, alerts health authority, and quarantines related batches. Investigation workflow with evidence packaging for regulatory action.", "4": "Automated alerts to designated contacts when suspect product detected. Quarantine recommendation generated. Basic investigation support.", "3": "Manual alert process triggered by failed verification. Email notifications. No automated quarantine or investigation tools.", "2": "Failed verification shows error but no alert workflow. Relies on user to take manual action and report.", "1": "No alert mechanism. Failed verifications are logged but not actioned." } }, { "id": "SC-MULTI-SUPPLIER", "name": "Multi-Supplier & Multi-Manufacturer Onboarding", "description": "The provider can onboard multiple pharmaceutical manufacturers and suppliers onto the same verification platform. NGOs typically procure from diverse sources. The system must work across suppliers.", "weight": 0.1, "ratingGuide": { "5": "Open platform supporting unlimited manufacturers. Self-service supplier onboarding portal. Handles diverse packaging formats and existing serialisation schemes. Interoperable with other traceability systems.", "4": "Supports multiple manufacturers with managed onboarding. Accommodates different barcode/QR formats. Good interoperability.", "3": "Supports 5-10 manufacturers. Onboarding requires provider assistance. Limited barcode format flexibility.", "2": "Designed for 1-3 manufacturers. Significant custom work to add new suppliers. Proprietary identifiers only.", "1": "Single-manufacturer solution. Cannot accommodate multi-source procurement." } } ], "procurement": { "marketMaturity": "emerging", "primaryMode": "tender", "alternativeModes": [ "integrator-led" ], "reasoning": "Anti-counterfeit medicine platforms exist with growing maturity.", "exampleProductCategories": [ "pharma-traceability-platform", "anti-counterfeit-rails" ], "partnerChannels": [], "lastReviewed": "2026-05-01" } }, { "id": "UC-D-053", "name": "Cold chain monitoring for vaccines and medicines", "category": "D", "subcategory": "Cold Chain Management", "description": "Record temperatures from the factory to the clinic, so you know quickly whether vaccines or medicines were spoiled and which batches to discard.", "bCriteria": [ "B3", "B5" ], "requiredComponents": [ { "component": "tracking-platform", "description": "Vaccine lot tracking" }, { "component": "iot-sensors", "description": "Temperature sensors on vaccine shipments" }, { "component": "cold-chain-monitors", "description": "Real-time cold chain monitoring" }, { "component": "audit-mechanism", "description": "Cold chain integrity audit" } ], "conditionalComponents": [ { "component": "smart-contracts", "condition": "If automated quality alerts based on temperature" } ], "crossCategoryDependencies": [ "UC-D-054 if expiry tracking needed" ], "p2TriggerConditions": { "description": "Activated when P2 shows vaccination campaigns + temperature-sensitive delivery + chain integrity concerns", "rangeSignals": [ "vaccinations >= 1000+", "coldChainDependency >= critical", "temperatureRisks >= high" ] }, "contextFieldsTemplate": [ { "field": "vaccineTypes", "source": "P2 immunisation", "description": "Vaccines distributed" }, { "field": "beneficiaries", "source": "P2 coverage targets", "description": "People to vaccinate" }, { "field": "coldStorage", "source": "P0 Q13 + P4", "description": "Cold chain infrastructure" }, { "field": "temperature", "source": "P2 storage requirements", "description": "Temperature requirements" } ], "implementationComplexity": "high", "examples": { "note": "GAVI vaccine tracking, cold chain monitoring", "references": [ { "name": "GAVI Alliance - Cold Chain Monitoring", "url": "https://www.gavi.org/programmes-impact/supply-chain", "solved": "Established IoT cold chain monitoring for vaccine distribution across 40+ countries" }, { "name": "IBM Vaccine Insight Platform", "url": "https://www.ibm.com/blockchain/vaccine-distribution", "solved": "Blockchain-based cold chain tracking for COVID-19 vaccine distribution" }, { "name": "Last Mile Health - Cold Chain Technology", "url": "https://lastmilehealth.org/programs/health-technology", "solved": "Real-time IoT monitoring for vaccine integrity in rural Africa" } ] }, "solutionQuestions": [ { "id": "cold-chain-temperature-requirement", "type": "select", "options": [ { "label": "Standard 2-8\u00b0C refrigeration", "value": "standard-2-8" }, { "label": "Ultra-cold -20\u00b0C to -30\u00b0C", "value": "ultra-cold-20-30" }, { "label": "Ultra-cold -60\u00b0C to -80\u00b0C (mRNA vaccines)", "value": "ultra-cold-60-80" } ], "propertyMapping": { "standard-2-8": { "technologies": [ "Standard cold chain sensor network", "Refrigeration monitoring system" ], "technologyProperties": { "sensorType": "Digital temperature probe", "alertThreshold": "\u00b12\u00b0C", "equipmentCost": "standard" } }, "ultra-cold-20-30": { "technologies": [ "Ultra-cold monitoring platform", "Deep freezer sensor network" ], "technologyProperties": { "sensorType": "Low-temperature sensor probe", "alertThreshold": "\u00b15\u00b0C", "equipmentCost": "high" } }, "ultra-cold-60-80": { "technologies": [ "Cryogenic monitoring system", "Specialised ultra-cold sensor array" ], "technologyProperties": { "sensorType": "Cryogenic temperature sensor", "alertThreshold": "\u00b110\u00b0C", "equipmentCost": "very-high" } } }, "prefillFrom": null, "briefSection": "Sensor and IoT", "text": "What temperature range must be maintained for your cold chain?", "ngoText": "What temperature range must be maintained for your cold chain?" }, { "id": "iot-sensor-type-selection", "type": "select", "options": [ { "label": "Passive temperature data loggers", "value": "passive-loggers" }, { "label": "Active IoT sensors with wireless connectivity", "value": "active-iot-sensors" }, { "label": "Hybrid sensors with digital ledger integration", "value": "hybrid-blockchain-sensors" } ], "propertyMapping": { "passive-loggers": { "technologies": [ "Temperature data logger system", "Manual verification platform" ], "technologyProperties": { "connectivity": "none", "dataTransfer": "manual-scan", "batteryLife": "multi-year", "cost": "low" } }, "active-iot-sensors": { "technologies": [ "IoT cold chain sensor network", "Real-time monitoring platform" ], "technologyProperties": { "connectivity": "cellular-or-wifi", "dataTransfer": "real-time", "batteryLife": "months-to-years", "cost": "moderate" } }, "hybrid-blockchain-sensors": { "technologies": [ "Blockchain-integrated IoT sensors", "Distributed ledger verification system" ], "technologyProperties": { "connectivity": "multi-modal", "dataTransfer": "immutable-real-time", "batteryLife": "optimised", "cost": "high" } } }, "prefillFrom": null, "briefSection": "Sensor and IoT", "text": "Which IoT sensor type is most suitable for vaccine monitoring?", "ngoText": "Which IoT sensor type is most suitable for vaccine monitoring?" }, { "id": "alert-mechanism-type", "type": "select", "options": [ { "label": "SMS and email notifications", "value": "sms-email-alerts" }, { "label": "In-app push notifications and dashboard alerts", "value": "app-dashboard-alerts" }, { "label": "Automated escalation with supervisor notification", "value": "automated-escalation" } ], "propertyMapping": { "sms-email-alerts": { "technologies": [ "SMS notification system", "Email alert platform" ], "technologyProperties": { "alertLatency": "5-15 minutes", "responseTime": "manual", "coverage": "basic", "reliability": "moderate" } }, "app-dashboard-alerts": { "technologies": [ "Mobile app alert system", "Real-time dashboard platform" ], "technologyProperties": { "alertLatency": "1-2 minutes", "responseTime": "semi-automated", "coverage": "comprehensive", "reliability": "high" } }, "automated-escalation": { "technologies": [ "Intelligent alert escalation system", "Automated response platform" ], "technologyProperties": { "alertLatency": "seconds", "responseTime": "fully-automated", "coverage": "complete", "reliability": "very-high" } } }, "prefillFrom": null, "briefSection": "Verification and authentication", "text": "What alert mechanism do you currently use for vaccine delivery issues?", "ngoText": "What alert mechanism do you currently use for vaccine delivery issues?" }, { "id": "health-system-integration", "type": "select", "options": [ { "label": "Manual data entry and reporting", "value": "manual-integration" }, { "label": "API integration with existing HIS systems", "value": "api-integration" }, { "label": "Full synchronisation with national health databases", "value": "full-sync-national" } ], "propertyMapping": { "manual-integration": { "technologies": [ "Data entry system", "Reporting platform" ], "technologyProperties": { "integrationLevel": "minimal", "dataSync": "manual", "automationLevel": "none", "staffRequirement": "high" } }, "api-integration": { "technologies": [ "API gateway platform", "Health information system connection" ], "technologyProperties": { "integrationLevel": "moderate", "dataSync": "periodic", "automationLevel": "semi-automated", "staffRequirement": "low" } }, "full-sync-national": { "technologies": [ "National health database integration", "Real-time synchronisation platform" ], "technologyProperties": { "integrationLevel": "complete", "dataSync": "real-time", "automationLevel": "fully-automated", "staffRequirement": "minimal" } } }, "prefillFrom": null, "briefSection": "Infrastructure requirements", "text": "What health system do you currently integrate with for vaccine delivery?", "ngoText": "What health system do you currently integrate with for vaccine delivery?" }, { "id": "vaccine-lot-tracking-method", "type": "select", "options": [ { "label": "Manual batch records and documentation", "value": "manual-records" }, { "label": "Barcode/QR scanning with digital tracking", "value": "barcode-tracking" }, { "label": "Tamper-proof digital lot tracking", "value": "blockchain-lots" } ], "propertyMapping": { "manual-records": { "technologies": [ "Paper-based documentation system", "Archive management" ], "technologyProperties": { "dataFormat": "paper-and-spreadsheet", "traceability": "limited", "auditCapability": "manual", "riskOfError": "high" } }, "barcode-tracking": { "technologies": [ "Barcode management engine", "Digital inventory platform" ], "technologyProperties": { "dataFormat": "structured-database", "traceability": "batch-level", "auditCapability": "semi-automated", "riskOfError": "moderate" } }, "blockchain-lots": { "technologies": [ "Blockchain lot tracking system", "Distributed ledger platform" ], "technologyProperties": { "dataFormat": "immutable-ledger", "traceability": "lot-to-dose", "auditCapability": "fully-automated", "riskOfError": "minimal" } } }, "prefillFrom": null, "briefSection": "Tracking and provenance", "text": "How do you currently track vaccine lots in your programmes?", "ngoText": "How do you currently track vaccine lots in your programmes?" }, { "id": "quality-assurance-cold-chain", "type": "select", "options": [ { "label": "Visual indicators and manual inspections", "value": "visual-inspection" }, { "label": "Automated sensor verification with reports", "value": "automated-verification" }, { "label": "Real-time monitoring with predictive analytics", "value": "predictive-analytics" } ], "propertyMapping": { "visual-inspection": { "technologies": [ "Visual indicator system", "Inspection checklist platform" ], "technologyProperties": { "verificationMethod": "manual-observation", "frequency": "periodic", "accuracy": "moderate", "scalability": "limited" } }, "automated-verification": { "technologies": [ "Automated temperature verification engine", "QA reporting system" ], "technologyProperties": { "verificationMethod": "sensor-based", "frequency": "continuous", "accuracy": "high", "scalability": "good" } }, "predictive-analytics": { "technologies": [ "Predictive analytics platform", "Machine learning quality system" ], "technologyProperties": { "verificationMethod": "ai-driven", "frequency": "real-time", "accuracy": "very-high", "scalability": "excellent" } } }, "prefillFrom": null, "briefSection": "Quality assurance", "text": "What quality assurance mechanisms should verify cold chain integrity?", "ngoText": "What quality assurance mechanisms should verify cold chain integrity?" }, { "id": "cold-chain-documentation", "type": "select", "options": [ { "label": "Paper-based temperature logs", "value": "paper-logs" }, { "label": "Digital records with audit trails", "value": "digital-records" }, { "label": "Tamper-proof digital records", "value": "blockchain-records" } ], "propertyMapping": { "paper-logs": { "technologies": [ "Manual record keeping system", "Archive storage" ], "technologyProperties": { "recordFormat": "paper", "auditTrail": "none", "accessControl": "limited", "searchability": "poor" } }, "digital-records": { "technologies": [ "Digital record management system", "Version control platform" ], "technologyProperties": { "recordFormat": "digital-database", "auditTrail": "basic", "accessControl": "role-based", "searchability": "good" } }, "blockchain-records": { "technologies": [ "Blockchain document system", "Immutable record platform" ], "technologyProperties": { "recordFormat": "blockchain-ledger", "auditTrail": "complete", "accessControl": "cryptographic", "searchability": "excellent" } } }, "prefillFrom": null, "briefSection": "Reporting and audit", "text": "How do you currently document cold-chain compliance?", "ngoText": "How do you currently document cold-chain compliance?" }, { "id": "sq-UC-D-053-001", "type": "single-select", "options": [ { "value": "national-health-authority", "label": "National health authority" }, { "value": "who-pqs", "label": "WHO PQS" }, { "value": "gavi", "label": "GAVI" }, { "value": "donor-specific", "label": "Donor-specific requirements" }, { "value": "internal-only", "label": "Internal only" } ], "propertyMapping": { "national-health-authority": { "technologies": [ "national-reporting", "regulatory-submission" ], "technologyProperties": {} }, "who-pqs": { "technologies": [ "who-reporting", "pqs-integration" ], "technologyProperties": {} }, "gavi": { "technologies": [ "gavi-reporting", "donor-reporting" ], "technologyProperties": {} }, "donor-specific": { "technologies": [ "donor-reporting", "custom-format" ], "technologyProperties": {} }, "internal-only": { "technologies": [ "internal-logging", "audit-trail" ], "technologyProperties": {} } }, "briefSection": "compliance", "text": "What regulatory reporting is required for cold chain excursions?", "ngoText": "What regulatory reporting is required for cold chain excursions?" } ], "complexityFactors": { "relationships": 3, "operationalChange": 4, "dataCompliance": 3 }, "suggestedCriteria": [ { "id": "SC-COLDCHAIN-IOT", "name": "Cold Chain IoT Sensor Integration", "description": "The provider supports continuous temperature monitoring via IoT sensors throughout the vaccine supply chain. Vaccines require unbroken cold chain from manufacturer to point of administration. Gaps of even hours can destroy potency.", "weight": 0.3, "ratingGuide": { "5": "Continuous temperature logging at configurable intervals (\u22645 min). Supports WHO PQS-prequalified sensors. GPS co-location with temperature data. Battery life >30 days. Automatic data upload when connectivity available.", "4": "Continuous logging at \u226415 min intervals. Compatible with major cold chain sensor brands. GPS tracking. Battery life >14 days.", "3": "Periodic temperature logging (hourly). Limited sensor compatibility. Manual data upload required at waypoints.", "2": "Point-in-time temperature checks at handoff nodes only. No continuous monitoring. Basic sensor support.", "1": "No IoT sensor integration. Relies on visual temperature indicators (VVMs) or manual logbook entries." } }, { "id": "SC-EXCURSION-ALERT", "name": "Temperature Excursion Alerting & Response", "description": "This measures how quickly the system detects and alerts on temperature excursions. For vaccines, a delayed alert means wasted doses and potentially vaccinating with ineffective product. Sub-minute detection and escalation is the gold standard.", "weight": 0.25, "ratingGuide": { "5": "Real-time excursion detection (<1 min). Multi-channel alerts (SMS, app push, email, dashboard). Automated escalation chain if primary contact doesn't acknowledge. Excursion severity classification. Decision-support for use/discard based on VVM and stability data.", "4": "Near-real-time detection (<5 min). Multi-channel alerts. Acknowledgement tracking. Basic severity classification.", "3": "Detection within 15-30 minutes. Single-channel alerts. Manual severity assessment required.", "2": "Detection at next data sync point (could be hours). Email-only alerts. No severity classification.", "1": "No automated alerting. Temperature excursions discovered on manual log review." } }, { "id": "SC-WHO-EPI", "name": "EPI & WHO Protocol Compliance", "description": "The system aligns with WHO Expanded Programme on Immunisation (EPI) standards, including temperature ranges per vaccine type, VVM correlation, and reporting formats. Compliance ensures acceptance by national immunisation programmes and GAVI.", "weight": 0.2, "ratingGuide": { "5": "Pre-configured with WHO-recommended temperature ranges for all EPI vaccines. VVM stage correlation. Generates WHO/UNICEF Joint Reporting Form data. Compatible with national EPI logistics management systems.", "4": "Configurable temperature ranges per vaccine type. VVM data capture. Can export in WHO-compatible formats. Some EPI system integrations.", "3": "Supports custom temperature ranges but not pre-configured for EPI. Manual VVM recording. Standard export formats only.", "2": "Single temperature range for all products. No VVM integration. Generic reporting only.", "1": "No awareness of vaccine-specific temperature requirements. General cold chain tool with no EPI alignment." } }, { "id": "SC-OFFLINE-FIELD", "name": "Offline & Low-Connectivity Field Operation", "description": "The system can continue monitoring and logging in areas with poor or no connectivity. Vaccine campaigns often reach remote areas where cellular coverage is absent for days. Data integrity must survive connectivity gaps.", "weight": 0.15, "ratingGuide": { "5": "Full offline operation: sensors log locally with encrypted storage, sync automatically when connectivity restored. No data loss during outages. Offline verification of vaccine status. Mesh networking between nearby devices.", "4": "Sensors log locally during connectivity gaps. Automatic sync on reconnection. Offline status checks possible. No mesh networking.", "3": "Local logging during short outages (<24h). Manual sync required. Limited offline functionality.", "2": "Buffers data for short gaps (<4h) but may lose data on extended outages. No offline verification.", "1": "Requires continuous connectivity. Data gaps during outages. No offline capability." } }, { "id": "SC-DOSE-TRACE", "name": "Dose-Level Traceability & Wastage Reporting", "description": "The system can track vaccines from shipment receipt through to individual dose administration, including wastage tracking. End-to-end traceability is essential for accountability reporting to GAVI and donors.", "weight": 0.1, "ratingGuide": { "5": "Vial-level tracking from receipt to administration. Automatic wastage calculation (opened multi-dose vials, temperature-damaged stock, expired doses). Integration with immunisation registers. Donor-ready accountability reports.", "4": "Batch-level tracking to point of use. Wastage recording per facility. Standard accountability reporting.", "3": "Shipment-level tracking to facility. Manual wastage recording. Basic reporting.", "2": "Tracks to distribution point only. No wastage tracking. Minimal reporting.", "1": "No post-delivery tracking. Cannot report on utilisation or wastage." } } ], "procurement": { "marketMaturity": "mature", "primaryMode": "off-the-shelf", "alternativeModes": [ "rfq" ], "reasoning": "Cold chain monitoring is mature SaaS+IoT market.", "exampleProductCategories": [ "cold-chain-monitoring-platform", "iot-temperature-tracking" ], "partnerChannels": [], "lastReviewed": "2026-05-01" } }, { "id": "UC-D-055", "name": "Nutrition supplement tracking", "category": "D", "subcategory": "Inventory Management", "description": "Follow nutrition supplements from warehouse to clinic, so you can compare what was sent with what arrived and check that quality was kept.", "bCriteria": [ "B1", "B3" ], "requiredComponents": [ { "component": "tracking-platform", "description": "Supplement distribution tracking" }, { "component": "qr-barcode", "description": "Supplement batch tracking" }, { "component": "inventory-integration", "description": "Stock level tracking" }, { "component": "audit-mechanism", "description": "Distribution audit trail" } ], "conditionalComponents": [ { "component": "smart-contracts", "condition": "If automated supplement allocation" } ], "crossCategoryDependencies": [], "p2TriggerConditions": { "description": "Activated when P2 shows nutrition programmes + large beneficiary base + distribution verification", "rangeSignals": [ "nutritionProgramme >= true", "beneficiaries >= 100+", "distributionVerification >= important" ] }, "contextFieldsTemplate": [ { "field": "beneficiaries", "source": "P2 programme scale", "description": "Beneficiaries served" }, { "field": "supplementTypes", "source": "P2 nutrition design", "description": "Types of supplements" }, { "field": "distributionFrequency", "source": "P2 programme schedule", "description": "Distribution frequency" }, { "field": "compliance", "source": "P2 M&E", "description": "Compliance monitoring" } ], "implementationComplexity": "low-medium", "examples": { "note": "Nutrition programme management", "references": [ { "name": "UNICEF Nutrition Program Tracking", "url": "https://www.unicef.org/nutrition/index_tracking.html", "solved": "Nutrition supplement distribution tracking in 30+ countries" }, { "name": "Helen Keller International - Micronutrient Programs", "url": "https://www.hki.org/work/micronutrient-programs", "solved": "Implemented supply tracking for vitamin supplementation across West Africa" } ] }, "solutionQuestions": [ { "id": "distribution-model-type", "type": "select", "options": [ { "label": "Direct distribution from central warehouse", "value": "direct-distribution" }, { "label": "Multi-tier distribution through partners", "value": "multi-tier-distribution" }, { "label": "Community health worker led distribution", "value": "chw-distribution" } ], "propertyMapping": { "direct-distribution": { "technologies": [ "Centralized distribution platform", "Direct tracking system" ], "technologyProperties": { "numberOfTiers": "1", "distributionPartners": "1-5", "complexityLevel": "simple", "trackingPoints": "2-3" } }, "multi-tier-distribution": { "technologies": [ "Multi-tier distribution platform", "Network coordination system" ], "technologyProperties": { "numberOfTiers": "3-5", "distributionPartners": "10+", "complexityLevel": "moderate", "trackingPoints": "5-8" } }, "chw-distribution": { "technologies": [ "CHW management platform", "Mobile distribution tracking" ], "technologyProperties": { "numberOfTiers": "2-3", "distributionPartners": "50-500", "complexityLevel": "complex", "trackingPoints": "3-5" } } }, "prefillFrom": null, "briefSection": "Tracking and provenance", "text": "What is your primary distribution model?", "ngoText": "What is your primary distribution model?" }, { "id": "beneficiary-verification-method", "type": "select", "options": [ { "label": "Manual signature or thumbprint on receipt", "value": "manual-receipt" }, { "label": "Digital confirmation via mobile phone", "value": "digital-confirmation" }, { "label": "Biometric verification with photo documentation", "value": "biometric-verification" } ], "propertyMapping": { "manual-receipt": { "technologies": [ "Receipt documentation system", "Paper tracking" ], "technologyProperties": { "verificationAccuracy": "moderate", "fraudRisk": "moderate", "administrativeOverhead": "high", "scalability": "limited" } }, "digital-confirmation": { "technologies": [ "Mobile verification platform", "SMS confirmation system" ], "technologyProperties": { "verificationAccuracy": "high", "fraudRisk": "low", "administrativeOverhead": "low", "scalability": "good" } }, "biometric-verification": { "technologies": [ "Biometric verification system", "Photo documentation platform" ], "technologyProperties": { "verificationAccuracy": "very-high", "fraudRisk": "very-low", "administrativeOverhead": "low", "scalability": "excellent" } } }, "prefillFrom": null, "briefSection": "Last-mile verification", "text": "What is your current method for verifying beneficiary identity?", "ngoText": "What is your current method for verifying beneficiary identity?" }, { "id": "compliance-tracking", "type": "select", "options": [ { "label": "Basic inventory and distribution logs", "value": "basic-compliance" }, { "label": "Nutritional outcome tracking and impact metrics", "value": "outcome-tracking" }, { "label": "Regulatory compliance with quality and safety standards", "value": "regulatory-compliance" } ], "propertyMapping": { "basic-compliance": { "technologies": [ "Basic tracking system", "Distribution log platform" ], "technologyProperties": { "dataFields": "distribution-dates-recipients", "reportingFrequency": "monthly", "complianceLevel": "minimal", "auditRequirement": "internal" } }, "outcome-tracking": { "technologies": [ "Impact measurement platform", "Nutrition outcome tracking" ], "technologyProperties": { "dataFields": "health-metrics-beneficiary-ids", "reportingFrequency": "quarterly", "complianceLevel": "moderate", "auditRequirement": "annual-external" } }, "regulatory-compliance": { "technologies": [ "Regulatory compliance platform", "Quality assurance system" ], "technologyProperties": { "dataFields": "complete-supply-chain-audit", "reportingFrequency": "real-time", "complianceLevel": "high", "auditRequirement": "continuous" } } }, "prefillFrom": null, "briefSection": "Reporting and audit", "text": "What compliance requirements must be tracked?", "ngoText": "What compliance requirements must be tracked?" }, { "id": "nutrition-reporting-stakeholder", "type": "select", "options": [ { "label": "Internal management only", "value": "internal-only" }, { "label": "Donors and implementing partners", "value": "donors-partners" }, { "label": "Full transparency to all stakeholders including beneficiaries", "value": "full-transparency" } ], "propertyMapping": { "internal-only": { "technologies": [ "Internal reporting system", "Staff dashboard" ], "technologyProperties": { "reportingParties": "staff-only", "frequencyOfReports": "internal-schedule", "dataGranularity": "aggregate", "accessControl": "role-based" } }, "donors-partners": { "technologies": [ "Stakeholder reporting platform", "Donor dashboard system" ], "technologyProperties": { "reportingParties": "donors-and-partners", "frequencyOfReports": "quarterly-annual", "dataGranularity": "summary-level", "accessControl": "authenticated-access" } }, "full-transparency": { "technologies": [ "Public accountability platform", "Impact dashboard" ], "technologyProperties": { "reportingParties": "all-stakeholders", "frequencyOfReports": "real-time", "dataGranularity": "transaction-level", "accessControl": "public-access" } } }, "prefillFrom": null, "briefSection": "Reporting and audit", "text": "Who needs to receive distribution and impact reports?", "ngoText": "Who needs to receive distribution and impact reports?" }, { "id": "nutrition-stakeholders", "type": "select", "options": [ { "label": "Internal only (1\u20132 teams)", "value": "internal" }, { "label": "Internal + 1\u20133 external partners", "value": "few-external" }, { "label": "Multiple external stakeholders (4\u201310)", "value": "multi-external" }, { "label": "Ecosystem-wide (donors, partners, beneficiaries, regulators)", "value": "ecosystem" } ], "propertyMapping": { "internal": { "technologies": [ "Private ledger" ], "technologyProperties": { "accessControl": "Simple role-based", "networkType": "Private" } }, "few-external": { "technologies": [ "Permissioned network", "Selective data sharing" ], "technologyProperties": { "accessControl": "Partner-level permissions", "networkType": "Consortium" } }, "multi-external": { "technologies": [ "Permissioned network", "Multi-party access layer" ], "technologyProperties": { "accessControl": "Granular role-based", "networkType": "Consortium" } }, "ecosystem": { "technologies": [ "Permissioned public network", "Data marketplace" ], "technologyProperties": { "accessControl": "Multi-tier with public layer", "networkType": "Hybrid public-private" } } }, "prefillFrom": null, "briefSection": "Governance and access", "text": "How many distinct parties need visibility into the nutrition supply chain data?", "ngoText": "How many distinct parties need visibility into the nutrition supply chain data?" }, { "id": "item-tracking-method", "type": "select", "options": [ { "label": "QR codes printed on items or packaging", "value": "qr-codes" }, { "label": "NFC tags embedded in items", "value": "nfc-tags" }, { "label": "Barcode labels with batch scanning", "value": "barcode" }, { "label": "Mixed: QR for high-value items, barcode for bulk", "value": "mixed" } ], "propertyMapping": { "qr-codes": { "technologies": [ "QR code generation service", "QR/barcode scanning app", "Item-level tracking ledger" ], "technologyProperties": { "trackingGranularity": "Per-item or per-batch", "scanMethod": "Mobile phone camera / QR scanner", "offlineCapable": "Yes \u2014 scan and sync when connected" } }, "nfc-tags": { "technologies": [ "NFC tag provisioning", "NFC reader integration", "Item-level tracking ledger" ], "technologyProperties": { "trackingGranularity": "Per-item", "scanMethod": "NFC-enabled device", "offlineCapable": "Yes \u2014 NFC works offline" } }, "barcode": { "technologies": [ "Barcode generation service", "QR/barcode scanning app", "Batch tracking ledger" ], "technologyProperties": { "trackingGranularity": "Per-batch", "scanMethod": "Barcode scanner / mobile camera", "offlineCapable": "Yes \u2014 scan and sync" } }, "mixed": { "technologies": [ "QR code generation service", "Barcode generation service", "QR/barcode scanning app", "Multi-level tracking ledger" ], "technologyProperties": { "trackingGranularity": "Mixed \u2014 item-level for high-value, batch for bulk", "scanMethod": "Mobile phone camera / scanner", "offlineCapable": "Yes" } } }, "prefillFrom": null, "briefSection": "Item tracking", "text": "How will physical items be tracked and scanned in the field?", "ngoText": "How will physical items be tracked and scanned in the field?" }, { "id": "inventory-integration", "type": "select", "options": [ { "label": "Integration with existing warehouse management system", "value": "wms-integration" }, { "label": "Standalone digital ledger inventory ledger", "value": "standalone" }, { "label": "Spreadsheet-based with digital verification layer", "value": "spreadsheet-bridge" }, { "label": "Not sure, need guidance", "value": "guidance-needed" } ], "propertyMapping": { "wms-integration": { "technologies": [ "WMS inventory integration", "Inventory system connection", "Stock level verification" ], "technologyProperties": { "integrationMethod": "API to existing WMS", "stockTracking": "Real-time sync", "reconciliation": "Automated" } }, "standalone": { "technologies": [ "Blockchain inventory management system", "Stock tracking ledger", "Inventory verification service" ], "technologyProperties": { "integrationMethod": "Standalone", "stockTracking": "Digital inventory records", "reconciliation": "Blockchain-verified" } }, "spreadsheet-bridge": { "technologies": [ "Spreadsheet inventory bridge", "CSV import/export module", "Inventory verification service" ], "technologyProperties": { "integrationMethod": "CSV/spreadsheet import with hash verification", "stockTracking": "Periodic sync", "reconciliation": "Semi-automated" } }, "guidance-needed": { "technologies": [ "Inventory integration framework" ], "technologyProperties": { "integrationMethod": "To be determined", "stockTracking": "To be determined", "reconciliation": "To be determined" } } }, "prefillFrom": null, "briefSection": "Inventory management", "text": "How are inventory and stock levels currently tracked?", "ngoText": "How are inventory and stock levels currently tracked?" }, { "id": "audit-mechanism-approach", "type": "select", "options": [ { "label": "Automatic checks that flag problems as they happen", "value": "automated-realtime" }, { "label": "Regular scheduled reviews with tamper-proof records", "value": "periodic-batch" }, { "label": "Ability to check any record at any time with proof it has not been altered", "value": "on-demand" }, { "label": "External auditors can log in and review records independently", "value": "third-party" } ], "propertyMapping": { "automated-realtime": { "technologies": [ "Real-time audit mechanism", "Automated anomaly detection", "Audit alert service" ], "technologyProperties": { "auditFrequency": "Continuous / real-time", "auditAccess": "System-generated alerts", "complianceReporting": "Automated" } }, "periodic-batch": { "technologies": [ "Periodic audit mechanism", "Batch verification engine", "Audit report generator" ], "technologyProperties": { "auditFrequency": "Scheduled (daily/weekly/monthly)", "auditAccess": "Generated audit reports", "complianceReporting": "Scheduled" } }, "on-demand": { "technologies": [ "On-demand audit mechanism", "Audit query interface", "Record verification service" ], "technologyProperties": { "auditFrequency": "On-demand", "auditAccess": "Query-based", "complianceReporting": "On request" } }, "third-party": { "technologies": [ "Third-party audit mechanism", "Auditor access portal", "Audit evidence export" ], "technologyProperties": { "auditFrequency": "As required by auditor", "auditAccess": "Dedicated portal with read-only access", "complianceReporting": "Auditor-directed" } } }, "prefillFrom": null, "briefSection": "Audit and verification", "text": "Who needs to verify that actions happened correctly, and how easily should they be able to check?", "ngoText": "How should auditing and verification work for this solution?" } ], "complexityFactors": { "relationships": 2, "operationalChange": 2, "dataCompliance": 1 }, "suggestedCriteria": [ { "id": "SC-BENEFICIARY-LINK", "name": "Beneficiary-Level Distribution Tracking", "description": "The system can track which beneficiaries received which supplements, when, and in what quantities. Nutrition programmes require individual-level accountability to prevent duplication and ensure coverage.", "weight": 0.3, "ratingGuide": { "5": "Individual beneficiary tracking linked to nutrition programme enrollment. Tracks receipt per distribution cycle. Flags missed distributions and double-collection. Integrates with beneficiary registration systems.", "4": "Individual tracking with manual beneficiary ID entry. Duplicate detection. Basic programme enrollment linkage.", "3": "Household-level tracking. Manual recording of distributions. Limited duplicate detection.", "2": "Aggregate distribution tracking by site only. No individual beneficiary linkage.", "1": "No distribution tracking beyond dispatch from warehouse." } }, { "id": "SC-NUTRITION-QUALITY", "name": "Product Quality & Storage Compliance", "description": "The system monitors storage conditions relevant to nutrition supplements (temperature, humidity, pest protection). RUTF, micronutrient powders, and therapeutic milk have specific storage requirements that affect efficacy.", "weight": 0.2, "ratingGuide": { "5": "Configurable storage parameter monitoring per product type. Alerts for temperature/humidity excursions. Pest incident logging. Quality inspection checklists at receipt. Links storage conditions to product efficacy data.", "4": "Temperature monitoring with alerts. Product-specific storage guidelines. Receipt inspection workflow.", "3": "Basic temperature logging. Generic storage guidelines. Manual inspection recording.", "2": "No environmental monitoring. Paper-based storage compliance.", "1": "No storage compliance features." } }, { "id": "SC-PROGRAMME-REPORT", "name": "Nutrition Programme Reporting", "description": "The system can generate reports aligned with nutrition cluster standards (CMAM, BSFP, TSFP reporting requirements). Nutrition coordinators need data formatted for cluster reporting, not raw inventory data.", "weight": 0.2, "ratingGuide": { "5": "Pre-built templates for CMAM/BSFP/TSFP reporting. Tracks admissions, defaults, recoveries linked to supplement distribution. Compatible with nutrition cluster (UNICEF/WFP) reporting tools.", "4": "Configurable reports that can match cluster formats. Links distribution to programme outcomes. Exportable.", "3": "Standard distribution reports. Manual formatting needed for cluster reporting. No outcome linkage.", "2": "Basic inventory reports only. No nutrition programme context.", "1": "No reporting beyond stock levels." } }, { "id": "SC-PIPELINE-VISIBILITY", "name": "Supply Pipeline Visibility", "description": "Programme managers can see incoming supply pipeline (what's been ordered, what's in transit, what's arriving when). Stockouts of therapeutic food can be fatal; pipeline visibility prevents gaps.", "weight": 0.2, "ratingGuide": { "5": "End-to-end pipeline dashboard from procurement to delivery. Arrival date forecasting. Automatic stockout risk alerts based on consumption rates vs. pipeline. Integration with procurement systems.", "4": "Pipeline tracking from dispatch. Arrival estimates. Stockout warnings based on current stock levels. Manual procurement data entry.", "3": "In-transit tracking visible. No forecasting. Stockout alerts based on fixed reorder points.", "2": "Stock levels visible but no pipeline information. Reactive stockout detection only.", "1": "No pipeline visibility. Stock information only available via physical counts." } }, { "id": "SC-FIELD-USABILITY", "name": "Field-Level Usability", "description": "Frontline nutrition workers can use the system without extensive training. Nutrition programmes rely on community health workers with varying tech literacy operating in difficult conditions.", "weight": 0.1, "ratingGuide": { "5": "Icon-driven mobile interface designed for low-literacy users. Pictorial product identification. Works offline. <30 min training. Available in major humanitarian languages. Minimal data entry per transaction.", "4": "Simple mobile interface. Visual aids. Offline capable. 1-2 hours training. Multi-language support.", "3": "Mobile-friendly but text-heavy. Requires connectivity for most functions. Half-day training. English plus one local language.", "2": "Complex interface requiring training. Desktop-preferred. English only.", "1": "Technical interface designed for logistics professionals. Impractical for community health workers." } } ], "procurement": { "marketMaturity": "emerging", "primaryMode": "rfq", "alternativeModes": [ "off-the-shelf" ], "reasoning": "Nutrition supplement tracking overlaps with general supply chain SaaS.", "exampleProductCategories": [ "supply-chain-saas", "nutrition-tracking-platform" ], "partnerChannels": [], "lastReviewed": "2026-05-01" } }, { "id": "UC-D-056", "name": "Food aid tracking from source to beneficiary", "category": "D", "subcategory": "Supply Chain Tracking", "description": "Follow food aid from its source to the household that receives it, so you can see where food goes missing along the way.", "bCriteria": [ "B1", "B3", "B5" ], "requiredComponents": [ { "component": "tracking-platform", "description": "End-to-end food tracking" }, { "component": "qr-barcode", "description": "Food lot identification" }, { "component": "provenance-verification", "description": "Source verification" }, { "component": "last-mile-verification", "description": "Beneficiary receipt verification" } ], "conditionalComponents": [ { "component": "iot-sensors", "condition": "If quality/condition monitoring" }, { "component": "audit-mechanism", "condition": "Distribution audit trail" } ], "crossCategoryDependencies": [ "UC-A-017 if proof of deployment needed" ], "p2TriggerConditions": { "description": "Activated when P2 shows food aid programmes + distribution verification needs + accountability", "rangeSignals": [ "foodAid >= true", "beneficiaries >= 1000+", "verificationComplexity >= high" ] }, "contextFieldsTemplate": [ { "field": "beneficiaries", "source": "P2 programme scale", "description": "Food aid recipients" }, { "field": "foodTypes", "source": "P2 food baskets", "description": "Types of food aid" }, { "field": "distribution", "source": "P2 logistics", "description": "Distribution frequency" }, { "field": "donors", "source": "P0 funding", "description": "Donor accountability needs" } ], "implementationComplexity": "high", "examples": { "note": "WFP food tracking, supply chain transparency", "references": [ { "name": "World Food Programme - Supply Chain Tracking", "url": "https://www.wfp.org/supply-chain-innovation", "solved": "End-to-end food aid tracking across 50+ countries with blockchain integration" }, { "name": "FAO Traceability Framework", "url": "https://www.fao.org/food-safety/food-control/traceability", "solved": "Established food origin verification standards for humanitarian programmes" }, { "name": "Mercy Corps - Supply Chain Visibility", "url": "https://www.mercycorps.org/research-resources/supply-chain-management", "solved": "Implemented real-time food distribution tracking in emergency response" } ] }, "solutionQuestions": [ { "id": "supply-chain-length", "type": "select", "options": [ { "label": "Short chain (2-3 hops: source, warehouse, beneficiary)", "value": "short-chain" }, { "label": "Medium chain (4-6 hops: source, port, warehouse, district, health center, beneficiary)", "value": "medium-chain" }, { "label": "Long chain (7+ hops: international, port, regional, district, local, partner, beneficiary)", "value": "long-chain" } ], "propertyMapping": { "short-chain": { "technologies": [ "Basic tracking platform", "Direct recipient system" ], "technologyProperties": { "nodeCount": "2-3", "trackingCheckpoints": "2-3", "automationLevel": "manual", "complexityLevel": "simple" } }, "medium-chain": { "technologies": [ "Multi-node tracking platform", "Hub coordination system" ], "technologyProperties": { "nodeCount": "4-6", "trackingCheckpoints": "4-6", "automationLevel": "semi-automated", "complexityLevel": "moderate" } }, "long-chain": { "technologies": [ "Complex supply chain management system", "Cross-border coordination platform" ], "technologyProperties": { "nodeCount": "7+", "trackingCheckpoints": "7+", "automationLevel": "fully-automated", "complexityLevel": "complex" } } }, "prefillFrom": null, "briefSection": "Tracking and provenance", "text": "What is the length of your food aid supply chain?", "ngoText": "What is the length of your food aid supply chain?" }, { "id": "food-tracking-granularity", "type": "select", "options": [ { "label": "Container/shipment level", "value": "container-level" }, { "label": "Batch/commodity lot level", "value": "batch-level" }, { "label": "Individual package/ration level", "value": "package-level" } ], "propertyMapping": { "container-level": { "technologies": [ "Shipping container tracking", "Logistics platform" ], "technologyProperties": { "trackingUnit": "container", "labelingCost": "very-low", "administrativeOverhead": "low", "traceabilityResolution": "container-only" } }, "batch-level": { "technologies": [ "Batch tracking engine", "Commodity management system" ], "technologyProperties": { "trackingUnit": "batch-or-lot", "labelingCost": "low", "administrativeOverhead": "moderate", "traceabilityResolution": "batch-level" } }, "package-level": { "technologies": [ "Package-level serialisation", "Individual ration tracking" ], "technologyProperties": { "trackingUnit": "individual-package", "labelingCost": "high", "administrativeOverhead": "high", "traceabilityResolution": "package-level" } } }, "prefillFrom": null, "briefSection": "Tracking and provenance", "text": "At what granularity should food aid be tracked?", "ngoText": "At what granularity should food aid be tracked?" }, { "id": "food-quality-monitoring", "type": "select", "options": [ { "label": "Manual visual inspections at checkpoints", "value": "visual-inspection" }, { "label": "Temperature and humidity monitoring with IoT sensors", "value": "iot-monitoring" }, { "label": "Continuous quality assurance with testing protocols", "value": "continuous-qa" } ], "propertyMapping": { "visual-inspection": { "technologies": [ "Inspection checklist system", "Quality observation platform" ], "technologyProperties": { "monitoringFrequency": "periodic", "dataAccuracy": "subjective", "scalability": "limited", "costEffectiveness": "high" } }, "iot-monitoring": { "technologies": [ "Food storage IoT sensor network", "Environmental monitoring platform" ], "technologyProperties": { "monitoringFrequency": "continuous", "dataAccuracy": "objective", "scalability": "good", "costEffectiveness": "moderate" } }, "continuous-qa": { "technologies": [ "Quality assurance testing platform", "Microbiology lab integration" ], "technologyProperties": { "monitoringFrequency": "systematic", "dataAccuracy": "scientific", "scalability": "excellent", "costEffectiveness": "low" } } }, "prefillFrom": null, "briefSection": "Quality assurance", "text": "How do you currently monitor food quality in your supply chain?", "ngoText": "How do you currently monitor food quality in your supply chain?" }, { "id": "donor-transparency-level", "type": "select", "options": [ { "label": "Post-delivery reporting only", "value": "post-delivery" }, { "label": "Real-time updates at major checkpoints", "value": "realtime-checkpoints" }, { "label": "Complete end-to-end visibility with beneficiary verification", "value": "complete-visibility" } ], "propertyMapping": { "post-delivery": { "technologies": [ "Post-delivery reporting system", "Summary reporting platform" ], "technologyProperties": { "reportingFrequency": "monthly", "dataVisibility": "summary-level", "updateFrequency": "batch", "donorDashboard": "no" } }, "realtime-checkpoints": { "technologies": [ "Real-time checkpoint notification", "Donor tracking dashboard" ], "technologyProperties": { "reportingFrequency": "per-checkpoint", "dataVisibility": "location-and-status", "updateFrequency": "real-time", "donorDashboard": "basic" } }, "complete-visibility": { "technologies": [ "End-to-end supply chain visibility platform", "Beneficiary verification system" ], "technologyProperties": { "reportingFrequency": "real-time", "dataVisibility": "transaction-level", "updateFrequency": "continuous", "donorDashboard": "advanced" } } }, "prefillFrom": null, "briefSection": "Reporting and audit", "text": "What level of transparency should donors have?", "ngoText": "What level of transparency should donors have?" }, { "id": "last-mile-food-verification", "type": "select", "options": [ { "label": "Manual handover documentation with signature", "value": "manual-handover" }, { "label": "Digital receipt with beneficiary ID and timestamp", "value": "digital-receipt" }, { "label": "Biometric verification with photo and location confirmation", "value": "biometric-verification" } ], "propertyMapping": { "manual-handover": { "technologies": [ "Handover documentation system", "Physical receipt form" ], "technologyProperties": { "verificationMethod": "signature-or-thumbprint", "fraudRisk": "moderate", "beneficiaryDataCapture": "name-and-signature", "scalability": "limited" } }, "digital-receipt": { "technologies": [ "Mobile receipt system", "Beneficiary ID platform" ], "technologyProperties": { "verificationMethod": "digital-confirmation", "fraudRisk": "low", "beneficiaryDataCapture": "id-and-phone", "scalability": "good" } }, "biometric-verification": { "technologies": [ "Biometric verification platform", "GPS location system", "Photo documentation" ], "technologyProperties": { "verificationMethod": "multi-factor", "fraudRisk": "very-low", "beneficiaryDataCapture": "biometric-gps-photo", "scalability": "excellent" } } }, "prefillFrom": null, "briefSection": "Last-mile verification", "text": "How do you currently verify food quality at the point of distribution?", "ngoText": "How do you currently verify food quality at the point of distribution?" }, { "id": "food-source-verification", "type": "select", "options": [ { "label": "Supplier documentation and invoices", "value": "documentation" }, { "label": "Digital tracking from farm/producer", "value": "blockchain-tracking" }, { "label": "Third-party certification and inspection", "value": "third-party-cert" } ], "propertyMapping": { "documentation": { "technologies": [ "Document management system", "Invoice tracking" ], "technologyProperties": { "verificationDepth": "supplier-level", "fraudPrevention": "moderate", "traceabilityToOrigin": "limited", "maintenanceCost": "low" } }, "blockchain-tracking": { "technologies": [ "Farm-to-distribution blockchain system", "Producer verification platform" ], "technologyProperties": { "verificationDepth": "origin-level", "fraudPrevention": "high", "traceabilityToOrigin": "complete", "maintenanceCost": "high" } }, "third-party-cert": { "technologies": [ "Certification verification platform", "Third-party auditor system" ], "technologyProperties": { "verificationDepth": "independent-verification", "fraudPrevention": "very-high", "traceabilityToOrigin": "certified", "maintenanceCost": "high" } } }, "prefillFrom": null, "briefSection": "Verification and authentication", "text": "How do you currently verify the source of your food supplies?", "ngoText": "How do you currently verify the source of your food supplies?" }, { "id": "item-tracking-method", "type": "select", "options": [ { "label": "QR codes printed on items or packaging", "value": "qr-codes" }, { "label": "NFC tags embedded in items", "value": "nfc-tags" }, { "label": "Barcode labels with batch scanning", "value": "barcode" }, { "label": "Mixed: QR for high-value items, barcode for bulk", "value": "mixed" } ], "propertyMapping": { "qr-codes": { "technologies": [ "QR code generation service", "QR/barcode scanning app", "Item-level tracking ledger" ], "technologyProperties": { "trackingGranularity": "Per-item or per-batch", "scanMethod": "Mobile phone camera / QR scanner", "offlineCapable": "Yes \u2014 scan and sync when connected" } }, "nfc-tags": { "technologies": [ "NFC tag provisioning", "NFC reader integration", "Item-level tracking ledger" ], "technologyProperties": { "trackingGranularity": "Per-item", "scanMethod": "NFC-enabled device", "offlineCapable": "Yes \u2014 NFC works offline" } }, "barcode": { "technologies": [ "Barcode generation service", "QR/barcode scanning app", "Batch tracking ledger" ], "technologyProperties": { "trackingGranularity": "Per-batch", "scanMethod": "Barcode scanner / mobile camera", "offlineCapable": "Yes \u2014 scan and sync" } }, "mixed": { "technologies": [ "QR code generation service", "Barcode generation service", "QR/barcode scanning app", "Multi-level tracking ledger" ], "technologyProperties": { "trackingGranularity": "Mixed \u2014 item-level for high-value, batch for bulk", "scanMethod": "Mobile phone camera / scanner", "offlineCapable": "Yes" } } }, "prefillFrom": null, "briefSection": "Item tracking", "text": "How will physical items be tracked and scanned in the field?", "ngoText": "How will physical items be tracked and scanned in the field?" } ], "complexityFactors": { "relationships": 3, "operationalChange": 3, "dataCompliance": 2 }, "suggestedCriteria": [ { "id": "SC-PROVENANCE-CHAIN", "name": "End-to-End Provenance Tracking", "description": "The system can trace food aid from source (donor, procurement, or local purchase) through every logistics node to final beneficiary receipt. Full provenance is essential for donor accountability and diversion detection.", "weight": 0.3, "ratingGuide": { "5": "Full chain-of-custody from source to beneficiary with immutable records at every handoff. Tracks splits, repackaging, and consolidation. Supports diverse entry points (imported commodity, local purchase, in-kind donation). Diversion detection via quantity reconciliation.", "4": "Source-to-distribution-site tracking with handoff records. Handles splits and consolidation. Basic quantity reconciliation.", "3": "Tracks from warehouse receipt to distribution site. Limited upstream visibility. Manual reconciliation.", "2": "Warehouse-to-dispatch tracking only. No upstream provenance. No beneficiary-level confirmation.", "1": "Dispatch records only. No chain-of-custody visibility." } }, { "id": "SC-LAST-MILE-PROOF", "name": "Last-Mile Delivery Proof", "description": "This looks at how the system confirms that food reached the intended beneficiaries. Last-mile verification is the most critical and most difficult part of food aid accountability.", "weight": 0.25, "ratingGuide": { "5": "Multiple verification methods: biometric confirmation, QR-code beneficiary cards, digital signatures, photo evidence. Works offline. Anti-fraud features (GPS stamp, timestamp, duplicate detection). Real-time reconciliation against distribution lists.", "4": "QR/card-based beneficiary confirmation. GPS and timestamp. Offline capable. Reconciliation against beneficiary lists.", "3": "Digital signature or token-based confirmation. Requires connectivity. Basic reconciliation.", "2": "Paper-based sign-off digitised after distribution. No real-time verification. Manual list reconciliation.", "1": "No beneficiary-level delivery proof. Aggregate distribution estimates only." } }, { "id": "SC-SCALE-WFP", "name": "Scale & Humanitarian Logistics Integration", "description": "The system can operate at WFP/large-NGO scale (millions of beneficiaries, multiple countries, thousands of distribution points). Integration with humanitarian logistics coordination systems is essential.", "weight": 0.2, "ratingGuide": { "5": "Proven at >1M beneficiary scale. Multi-country deployment. Integration with the logistics and registration systems of the large UN agencies, or equivalent. Handles complex logistics networks (sea, air, road, last-mile).", "4": "Handles 100K-1M beneficiaries. Multi-country capable. API integration with major humanitarian logistics systems.", "3": "Handles 10K-100K beneficiaries. Single-country deployment. CSV-based data exchange with logistics systems.", "2": "Handles <10K beneficiaries. Single-site operation. No logistics system integration.", "1": "Prototype or pilot scale only. Not tested beyond single community." } }, { "id": "SC-DIVERSION-DETECT", "name": "Diversion & Leakage Detection", "description": "The system proactively identifies discrepancies that may indicate diversion or leakage. Food aid diversion is a major risk. The system should flag quantity mismatches, unusual patterns, and ghost beneficiaries.", "weight": 0.15, "ratingGuide": { "5": "Automated anomaly detection: quantity discrepancies at each node, unusual distribution patterns, ghost beneficiary detection, statistical outlier flagging. Investigation workflow with audit trail.", "4": "Quantity reconciliation at each handoff with automated variance alerts. Basic pattern analysis. Audit trail.", "3": "End-of-chain quantity comparison (dispatched vs. distributed). Manual variance investigation. Basic audit log.", "2": "Manual reconciliation on request. No automated flagging. Limited audit trail.", "1": "No diversion detection capability. Relies entirely on external audit." } }, { "id": "SC-COMMODITY-FLEX", "name": "Commodity Type Flexibility", "description": "Can the system handle the full range of food aid commodities (bulk grain, fortified blended foods, ready-to-use supplementary foods, cash/voucher equivalents, and fresh food from local markets)?", "weight": 0.1, "ratingGuide": { "5": "Supports all commodity types including bulk (MT), packaged (units), vouchers, and cash transfers. Configurable units of measure. Handles commodity substitution and equivalence calculations.", "4": "Supports bulk and packaged commodities. Basic voucher tracking. Configurable units.", "3": "Handles standard packaged food commodities. Limited bulk tracking. No voucher integration.", "2": "Single commodity type (e.g. packaged only). Fixed units of measure.", "1": "Minimal commodity management. Single product tracking only." } } ], "procurement": { "marketMaturity": "emerging", "primaryMode": "integrator-led", "alternativeModes": [ "rfq" ], "reasoning": "Food aid end-to-end tracking requires integration across supply chain stages.", "exampleProductCategories": [ "food-aid-traceability-platform", "supply-chain-saas" ], "partnerChannels": [], "lastReviewed": "2026-05-01" } }, { "id": "UC-D-057", "name": "Donated goods provenance verification", "category": "D", "subcategory": "Product Authentication", "description": "Show where donated goods came from, so donors can see they came from the stated source and you can turn away goods of doubtful origin.", "bCriteria": [ "B3", "B4" ], "requiredComponents": [ { "component": "provenance-verification", "description": "Donation source verification" }, { "component": "qr-barcode", "description": "Donation tracking" }, { "component": "audit-mechanism", "description": "Donation audit trail" } ], "conditionalComponents": [ { "component": "smart-contracts", "condition": "If conditional donation acceptance" } ], "crossCategoryDependencies": [], "p2TriggerConditions": { "description": "Activated when P2 shows in-kind donations + donor verification needs + quality concerns", "rangeSignals": [ "inKindDonations >= significant", "donorVerification >= important", "qualityConcerns >= true" ] }, "contextFieldsTemplate": [ { "field": "donors", "source": "P0 donor base", "description": "Number of donors" }, { "field": "goodsTypes", "source": "P2 in-kind offers", "description": "Types of goods" }, { "field": "volume", "source": "P2 donations", "description": "Annual donation volume" }, { "field": "integrityRisks", "source": "P0 context", "description": "Donation authenticity concerns" } ], "implementationComplexity": "low-medium", "examples": { "note": "In-kind donation management", "references": [ { "name": "Logistics Cluster - Donation Management", "url": "https://www.logcluster.org/en/document/donation-guidelines", "solved": "Established provenance verification standards for NGO donations" }, { "name": "Direct Relief - In-Kind Donation Tracking", "url": "https://www.directrelief.org/impact/supply-chain", "solved": "Tracked donated medical goods across 70+ countries" } ] }, "solutionQuestions": [ { "id": "donation-types-accepted", "type": "select", "options": [ { "label": "Single category (e.g., medical supplies only)", "value": "single-category" }, { "label": "Multiple categories (medicines, equipment, supplies)", "value": "multiple-categories" }, { "label": "Mixed and unstructured donations", "value": "mixed-donations" } ], "propertyMapping": { "single-category": { "technologies": [ "Single-type donation system", "Category-specific tracking" ], "technologyProperties": { "classificationComplexity": "simple", "verificationRequirements": "standardised", "cataloguingEffort": "low", "processingSpeed": "fast" } }, "multiple-categories": { "technologies": [ "Multi-category donation platform", "Classification engine" ], "technologyProperties": { "classificationComplexity": "moderate", "verificationRequirements": "category-specific", "cataloguingEffort": "moderate", "processingSpeed": "moderate" } }, "mixed-donations": { "technologies": [ "Flexible donation management platform", "AI-powered classification system" ], "technologyProperties": { "classificationComplexity": "complex", "verificationRequirements": "case-by-case", "cataloguingEffort": "high", "processingSpeed": "slow" } } }, "prefillFrom": null, "briefSection": "Tracking and provenance", "text": "What types of donated goods do you accept?", "ngoText": "What types of donated goods do you accept?" }, { "id": "provenance-verification-depth", "type": "select", "options": [ { "label": "Donor name and date only", "value": "donor-basic" }, { "label": "Donor verification plus manufacturing information", "value": "donor-plus-mfg" }, { "label": "Complete origin traceability from manufacturer", "value": "complete-origin" } ], "propertyMapping": { "donor-basic": { "technologies": [ "Donation receipt system", "Donor registration platform" ], "technologyProperties": { "verificationProcess": "basic", "recordingRequirement": "minimal", "fraudRisk": "moderate", "administrativeOverhead": "low" } }, "donor-plus-mfg": { "technologies": [ "Enhanced donor verification", "Product information system" ], "technologyProperties": { "verificationProcess": "moderate", "recordingRequirement": "intermediate", "fraudRisk": "low", "administrativeOverhead": "moderate" } }, "complete-origin": { "technologies": [ "Full traceability platform", "Manufacturing provenance system" ], "technologyProperties": { "verificationProcess": "comprehensive", "recordingRequirement": "complete", "fraudRisk": "very-low", "administrativeOverhead": "high" } } }, "prefillFrom": null, "briefSection": "Verification and authentication", "text": "How deep should provenance verification go?", "ngoText": "How deep should provenance verification go?" }, { "id": "donation-verification-standard", "type": "select", "options": [ { "label": "Basic acceptance criteria", "value": "basic-criteria" }, { "label": "NGO-specific standards (e.g., SPHERE standards)", "value": "ngo-standards" }, { "label": "International quality and safety certification", "value": "international-cert" } ], "propertyMapping": { "basic-criteria": { "technologies": [ "Basic quality checklist", "Acceptance criteria system" ], "technologyProperties": { "complianceFramework": "organisational-policy", "externalValidation": "none", "costOfCompliance": "low", "acceptanceRate": "high" } }, "ngo-standards": { "technologies": [ "NGO standards compliance platform", "SPHERE standards verification" ], "technologyProperties": { "complianceFramework": "ngo-standards", "externalValidation": "ngo-partners", "costOfCompliance": "moderate", "acceptanceRate": "moderate" } }, "international-cert": { "technologies": [ "International certification verification", "Quality assurance platform" ], "technologyProperties": { "complianceFramework": "iso-who-standards", "externalValidation": "certifier", "costOfCompliance": "high", "acceptanceRate": "low" } } }, "prefillFrom": null, "briefSection": "Quality assurance", "text": "What verification standard should be applied?", "ngoText": "What verification standard should be applied?", "hidden": true }, { "id": "donated-goods-volume", "type": "select", "options": [ { "label": "Under 1,000 items", "value": "small" }, { "label": "1,000\u201310,000 items", "value": "medium" }, { "label": "10,000\u2013100,000 items", "value": "large" }, { "label": "Over 100,000 items", "value": "enterprise" } ], "propertyMapping": { "small": { "technologies": [ "Simple ledger" ], "technologyProperties": { "scalability": "Standard", "throughput": "Low" } }, "medium": { "technologies": [ "Standard tracking platform" ], "technologyProperties": { "scalability": "Standard", "throughput": "Medium" } }, "large": { "technologies": [ "High-throughput tracking platform", "Batch processing" ], "technologyProperties": { "scalability": "High", "throughput": "High \u2014 batch optimised" } }, "enterprise": { "technologies": [ "Enterprise tracking platform", "Layer 2 scaling" ], "technologyProperties": { "scalability": "Enterprise", "throughput": "Very high \u2014 L2 required" } } }, "prefillFrom": null, "briefSection": "Infrastructure requirements", "text": "What is the monthly volume of donated goods you need to track?", "ngoText": "What is the monthly volume of donated goods you need to track?" }, { "id": "donated-goods-stakeholders", "type": "select", "options": [ { "label": "Internal only (1\u20132 teams)", "value": "internal" }, { "label": "Internal + 1\u20133 external partners", "value": "few-external" }, { "label": "Multiple external stakeholders (4\u201310)", "value": "multi-external" }, { "label": "Ecosystem-wide (donors, partners, beneficiaries, regulators)", "value": "ecosystem" } ], "propertyMapping": { "internal": { "technologies": [ "Private ledger" ], "technologyProperties": { "accessControl": "Simple role-based", "networkType": "Private" } }, "few-external": { "technologies": [ "Permissioned network", "Selective data sharing" ], "technologyProperties": { "accessControl": "Partner-level permissions", "networkType": "Consortium" } }, "multi-external": { "technologies": [ "Permissioned network", "Multi-party access layer" ], "technologyProperties": { "accessControl": "Granular role-based", "networkType": "Consortium" } }, "ecosystem": { "technologies": [ "Permissioned public network", "Data marketplace" ], "technologyProperties": { "accessControl": "Multi-tier with public layer", "networkType": "Hybrid public-private" } } }, "prefillFrom": null, "briefSection": "Governance and access", "text": "How many distinct parties need visibility into the donated goods provenance data?", "ngoText": "How many distinct parties need visibility into the donated goods provenance data?" }, { "id": "item-tracking-method", "type": "select", "options": [ { "label": "QR codes printed on items or packaging", "value": "qr-codes" }, { "label": "NFC tags embedded in items", "value": "nfc-tags" }, { "label": "Barcode labels with batch scanning", "value": "barcode" }, { "label": "Mixed: QR for high-value items, barcode for bulk", "value": "mixed" } ], "propertyMapping": { "qr-codes": { "technologies": [ "QR code generation service", "QR/barcode scanning app", "Item-level tracking ledger" ], "technologyProperties": { "trackingGranularity": "Per-item or per-batch", "scanMethod": "Mobile phone camera / QR scanner", "offlineCapable": "Yes \u2014 scan and sync when connected" } }, "nfc-tags": { "technologies": [ "NFC tag provisioning", "NFC reader integration", "Item-level tracking ledger" ], "technologyProperties": { "trackingGranularity": "Per-item", "scanMethod": "NFC-enabled device", "offlineCapable": "Yes \u2014 NFC works offline" } }, "barcode": { "technologies": [ "Barcode generation service", "QR/barcode scanning app", "Batch tracking ledger" ], "technologyProperties": { "trackingGranularity": "Per-batch", "scanMethod": "Barcode scanner / mobile camera", "offlineCapable": "Yes \u2014 scan and sync" } }, "mixed": { "technologies": [ "QR code generation service", "Barcode generation service", "QR/barcode scanning app", "Multi-level tracking ledger" ], "technologyProperties": { "trackingGranularity": "Mixed \u2014 item-level for high-value, batch for bulk", "scanMethod": "Mobile phone camera / scanner", "offlineCapable": "Yes" } } }, "prefillFrom": null, "briefSection": "Item tracking", "text": "How will physical items be tracked and scanned in the field?", "ngoText": "How will physical items be tracked and scanned in the field?" }, { "id": "audit-mechanism-approach", "type": "select", "options": [ { "label": "Automatic checks that flag problems as they happen", "value": "automated-realtime" }, { "label": "Regular scheduled reviews with tamper-proof records", "value": "periodic-batch" }, { "label": "Ability to check any record at any time with proof it has not been altered", "value": "on-demand" }, { "label": "External auditors can log in and review records independently", "value": "third-party" } ], "propertyMapping": { "automated-realtime": { "technologies": [ "Real-time audit mechanism", "Automated anomaly detection", "Audit alert service" ], "technologyProperties": { "auditFrequency": "Continuous / real-time", "auditAccess": "System-generated alerts", "complianceReporting": "Automated" } }, "periodic-batch": { "technologies": [ "Periodic audit mechanism", "Batch verification engine", "Audit report generator" ], "technologyProperties": { "auditFrequency": "Scheduled (daily/weekly/monthly)", "auditAccess": "Generated audit reports", "complianceReporting": "Scheduled" } }, "on-demand": { "technologies": [ "On-demand audit mechanism", "Audit query interface", "Record verification service" ], "technologyProperties": { "auditFrequency": "On-demand", "auditAccess": "Query-based", "complianceReporting": "On request" } }, "third-party": { "technologies": [ "Third-party audit mechanism", "Auditor access portal", "Audit evidence export" ], "technologyProperties": { "auditFrequency": "As required by auditor", "auditAccess": "Dedicated portal with read-only access", "complianceReporting": "Auditor-directed" } } }, "prefillFrom": null, "briefSection": "Audit and verification", "text": "Who needs to verify that actions happened correctly, and how easily should they be able to check?", "ngoText": "How should auditing and verification work for this solution?" } ], "complexityFactors": { "relationships": 2, "operationalChange": 1, "dataCompliance": 1 }, "suggestedCriteria": [ { "id": "SC-DONOR-PROVENANCE", "name": "Donor-to-Receipt Provenance Chain", "description": "The system can establish and verify the provenance of donated goods from the donor through logistics to receipt by the NGO. Provenance verification prevents misrepresentation of donated goods quality, origin, or donor intent.", "weight": 0.3, "ratingGuide": { "5": "Complete provenance chain from donor declaration through shipping, customs, and receipt. Donor-attested quality/specifications recorded immutably. Supports corporate, government, and individual donations. Multi-party verification at each transfer.", "4": "Donor information captured with shipping documentation. Provenance chain from port of entry to receipt. Good documentation workflow.", "3": "Donor information recorded at receipt. Basic shipping records linked. Limited upstream verification.", "2": "Receipt-only recording with donor name. No verification of donor claims about quality or origin.", "1": "No provenance tracking. Goods received with paper documentation only." } }, { "id": "SC-QUALITY-INSPECT", "name": "Quality Verification & Inspection Workflow", "description": "The system supports structured quality inspection of donated goods against donor specifications. In-kind donations often arrive in varying condition: systematic quality assessment protects beneficiaries.", "weight": 0.25, "ratingGuide": { "5": "Configurable inspection checklists per goods category. Photo/video evidence capture. Grade classification (acceptable, conditional, reject). Links inspection results to provenance record. Generates donor feedback on quality issues.", "4": "Standard inspection templates. Photo evidence. Accept/reject classification. Linked to inventory records.", "3": "Basic inspection recording. Text-based notes. Simple pass/fail. Manual linkage to inventory.", "2": "Free-text inspection notes only. No structured assessment. No photographic evidence.", "1": "No inspection workflow. Goods accepted as-is with no quality documentation." } }, { "id": "SC-DONOR-REPORT", "name": "Donor Acknowledgement & Reporting", "description": "The system can generate proof-of-receipt and utilisation reports for donors. Donors giving goods in-kind need acknowledgement for tax purposes and accountability.", "weight": 0.2, "ratingGuide": { "5": "Automated donor receipts with blockchain-anchored proof. Utilisation tracking showing where goods were deployed. Tax-documentation-ready valuations. Donor portal for self-service reporting.", "4": "Automated receipts. Utilisation reports per donation. Standard valuation methods. Email-based reporting.", "3": "Receipt generation on request. Basic utilisation summaries. Manual valuation.", "2": "Manual receipt generation. No utilisation tracking. No valuation support.", "1": "No donor reporting capability." } }, { "id": "SC-GOODS-CLASS", "name": "Goods Classification & Cataloguing", "description": "Can the system catalogue diverse donated goods (medical equipment, vehicles, building materials, IT equipment, textiles) with appropriate classification schemas?", "weight": 0.15, "ratingGuide": { "5": "Flexible classification supporting multiple taxonomies (UN OCHA relief items, customs HS codes, organisational categories). Custom attributes per category. Photographic catalogue. Barcode/RFID tagging.", "4": "Configurable category structure. Standard humanitarian goods classification. Photo support. Barcode tagging.", "3": "Fixed category list covering major goods types. Basic attribute capture. Manual cataloguing.", "2": "Minimal categorisation. Free-text description. No structured attributes.", "1": "No goods classification. Single-type tracking only." } }, { "id": "SC-REGULATORY-CUSTOMS", "name": "Customs & Import Compliance Documentation", "description": "The system helps manage customs documentation for imported donated goods. Customs clearance is a major bottleneck for in-kind donations. Proper documentation prevents delays and duties.", "weight": 0.1, "ratingGuide": { "5": "Customs documentation generation (packing lists, commercial invoices, duty exemption applications). Pre-configured for humanitarian exemption regimes. Tracks clearance status. Integrates with customs authorities where available.", "4": "Standard customs document templates. Tracks clearance status. Knowledge of humanitarian exemptions.", "3": "Basic document generation. Manual customs tracking. General import documentation.", "2": "Document storage only. No customs-specific features.", "1": "No customs documentation support." } } ], "procurement": { "marketMaturity": "emerging", "primaryMode": "rfq", "alternativeModes": [ "off-the-shelf" ], "reasoning": "Donated goods provenance overlaps with general traceability SaaS.", "exampleProductCategories": [ "provenance-platform", "supply-chain-saas" ], "partnerChannels": [], "lastReviewed": "2026-05-01" } }, { "id": "UC-D-058", "name": "In-kind donation tracking and valuation", "category": "D", "subcategory": "Inventory Management", "description": "Record gifts of goods from donor to beneficiary and agree their value with the donor, so there are fewer disputes over what was given.", "bCriteria": [ "B1", "B3" ], "requiredComponents": [ { "component": "tracking-platform", "description": "In-kind donation tracking" }, { "component": "inventory-integration", "description": "Donation inventory management" }, { "component": "audit-mechanism", "description": "Valuation audit trail" }, { "component": "reporting-module", "description": "Donation reporting" } ], "conditionalComponents": [ { "component": "accounting-integration", "condition": "If donation value accounting" } ], "crossCategoryDependencies": [], "p2TriggerConditions": { "description": "Activated when P2 shows significant in-kind donations + valuation complexity + reporting burden", "rangeSignals": [ "inKindVolume >= significant", "valuationComplexity >= true", "reportingBurden >= high" ] }, "contextFieldsTemplate": [ { "field": "donorCount", "source": "P0 donors", "description": "Number of donors" }, { "field": "goodsTypes", "source": "P2 donations", "description": "Types of goods donated" }, { "field": "volume", "source": "P2 annual donations", "description": "Annual donation volume" }, { "field": "valuationMethod", "source": "P2 accounting", "description": "Valuation methodology" } ], "implementationComplexity": "medium", "examples": { "note": "NGO donation management", "references": [ { "name": "Direct Relief - Donation Valuation System", "url": "https://www.directrelief.org/about/financial-reports", "solved": "Developed in-kind donation valuation methodology for NGO programmes" }, { "name": "Charitable Resource Center - Donation Accounting", "url": "https://www.charitableresource.org/donation-tracking", "solved": "Integrated donation tracking with GAAP accounting standards" } ] }, "solutionQuestions": [ { "id": "donation-valuation-method", "type": "select", "options": [ { "label": "Fair market value at time of donation", "value": "fair-market-value" }, { "label": "Replacement cost in programme location", "value": "replacement-cost" }, { "label": "Cost as assessed by independent appraiser", "value": "independent-appraisal" } ], "propertyMapping": { "fair-market-value": { "technologies": [ "Market value assessment system", "Real-time pricing engine" ], "technologyProperties": { "valuationDataSource": "market-prices", "updateFrequency": "periodic", "objectivity": "high", "administrativeEffort": "low" } }, "replacement-cost": { "technologies": [ "Local cost analysis platform", "Contextual pricing engine" ], "technologyProperties": { "valuationDataSource": "local-suppliers", "updateFrequency": "regular", "objectivity": "moderate", "administrativeEffort": "moderate" } }, "independent-appraisal": { "technologies": [ "Appraiser coordination platform", "Expert valuation system" ], "technologyProperties": { "valuationDataSource": "expert-assessment", "updateFrequency": "per-donation", "objectivity": "very-high", "administrativeEffort": "high" } } }, "prefillFrom": null, "briefSection": "Tracking and provenance", "text": "Which valuation method should be used for donated goods?", "ngoText": "Which valuation method should be used for donated goods?" }, { "id": "accounting-system-integration", "type": "select", "options": [ { "label": "Manual entry into accounting ledgers", "value": "manual-entry" }, { "label": "Automated integration with bookkeeping software", "value": "api-integration" }, { "label": "Real-time digital ledger-based accounting", "value": "blockchain-accounting" } ], "propertyMapping": { "manual-entry": { "technologies": [ "Manual accounting entry", "Ledger management" ], "technologyProperties": { "automationLevel": "none", "errorRate": "moderate", "reconciliationEffort": "high", "costPerDonation": "moderate" } }, "api-integration": { "technologies": [ "Accounting software connection", "Automated posting engine" ], "technologyProperties": { "automationLevel": "high", "errorRate": "low", "reconciliationEffort": "low", "costPerDonation": "low" } }, "blockchain-accounting": { "technologies": [ "Blockchain accounting system", "Distributed ledger platform" ], "technologyProperties": { "automationLevel": "fully-automated", "errorRate": "none", "reconciliationEffort": "minimal", "costPerDonation": "high-initial-setup" } } }, "prefillFrom": null, "briefSection": "Inventory management", "text": "What accounting system do you currently use for supply chain tracking?", "ngoText": "What accounting system do you currently use for supply chain tracking?" }, { "id": "donor-impact-reporting", "type": "select", "options": [ { "label": "Financial receipt and valuation only", "value": "financial-receipt" }, { "label": "Usage tracking and programme allocation", "value": "usage-tracking" }, { "label": "Impact measurement with beneficiary outcomes", "value": "impact-measurement" } ], "propertyMapping": { "financial-receipt": { "technologies": [ "Tax receipt generation system", "Valuation report platform" ], "technologyProperties": { "reportingContent": "value-only", "frequencyOfReporting": "quarterly", "stakeHolderRelevance": "financial", "reportingComplexity": "simple" } }, "usage-tracking": { "technologies": [ "Donation usage tracking", "Programme allocation system" ], "technologyProperties": { "reportingContent": "usage-and-allocation", "frequencyOfReporting": "monthly", "stakeHolderRelevance": "programme-related", "reportingComplexity": "moderate" } }, "impact-measurement": { "technologies": [ "Impact measurement platform", "Outcome tracking system" ], "technologyProperties": { "reportingContent": "value-usage-impact", "frequencyOfReporting": "real-time", "stakeHolderRelevance": "comprehensive", "reportingComplexity": "high" } } }, "prefillFrom": null, "briefSection": "Reporting and audit", "text": "What donor reporting should show impact of donations?", "ngoText": "What donor reporting should show impact of donations?" }, { "id": "donation-tracking-scale", "type": "select", "options": [ { "label": "Small volume (< 100 donations/year)", "value": "small-scale" }, { "label": "Medium volume (100-1000 donations/year)", "value": "medium-scale" }, { "label": "Large volume (> 1000 donations/year)", "value": "large-scale" } ], "propertyMapping": { "small-scale": { "technologies": [ "Simple donation log", "Spreadsheet system" ], "technologyProperties": { "systemComplexity": "basic", "automationLevel": "minimal", "staffingNeeds": "part-time", "investmentRequired": "low" } }, "medium-scale": { "technologies": [ "Donation management platform", "Valuation engine" ], "technologyProperties": { "systemComplexity": "moderate", "automationLevel": "semi-automated", "staffingNeeds": "dedicated-staff", "investmentRequired": "moderate" } }, "large-scale": { "technologies": [ "Enterprise donation management system", "Automated processing platform" ], "technologyProperties": { "systemComplexity": "advanced", "automationLevel": "fully-automated", "staffingNeeds": "specialized-team", "investmentRequired": "high" } } }, "prefillFrom": null, "briefSection": "Inventory management", "text": "What scale of donation volume needs to be tracked?", "ngoText": "What scale of donation volume needs to be tracked?", "hidden": true }, { "id": "in-kind-stakeholders", "type": "select", "options": [ { "label": "Internal only (1\u20132 teams)", "value": "internal" }, { "label": "Internal + 1\u20133 external partners", "value": "few-external" }, { "label": "Multiple external stakeholders (4\u201310)", "value": "multi-external" }, { "label": "Ecosystem-wide (donors, partners, beneficiaries, regulators)", "value": "ecosystem" } ], "propertyMapping": { "internal": { "technologies": [ "Private ledger" ], "technologyProperties": { "accessControl": "Simple role-based", "networkType": "Private" } }, "few-external": { "technologies": [ "Permissioned network", "Selective data sharing" ], "technologyProperties": { "accessControl": "Partner-level permissions", "networkType": "Consortium" } }, "multi-external": { "technologies": [ "Permissioned network", "Multi-party access layer" ], "technologyProperties": { "accessControl": "Granular role-based", "networkType": "Consortium" } }, "ecosystem": { "technologies": [ "Permissioned public network", "Data marketplace" ], "technologyProperties": { "accessControl": "Multi-tier with public layer", "networkType": "Hybrid public-private" } } }, "prefillFrom": null, "briefSection": "Governance and access", "text": "How many distinct parties need visibility into the in-kind donation data?", "ngoText": "How many distinct parties need visibility into the in-kind donation data?" }, { "id": "inventory-integration", "type": "select", "options": [ { "label": "Integration with existing warehouse management system", "value": "wms-integration" }, { "label": "Standalone digital ledger inventory ledger", "value": "standalone" }, { "label": "Spreadsheet-based with digital verification layer", "value": "spreadsheet-bridge" }, { "label": "Not sure, need guidance", "value": "guidance-needed" } ], "propertyMapping": { "wms-integration": { "technologies": [ "WMS inventory integration", "Inventory system connection", "Stock level verification" ], "technologyProperties": { "integrationMethod": "API to existing WMS", "stockTracking": "Real-time sync", "reconciliation": "Automated" } }, "standalone": { "technologies": [ "Blockchain inventory management system", "Stock tracking ledger", "Inventory verification service" ], "technologyProperties": { "integrationMethod": "Standalone", "stockTracking": "Digital inventory records", "reconciliation": "Blockchain-verified" } }, "spreadsheet-bridge": { "technologies": [ "Spreadsheet inventory bridge", "CSV import/export module", "Inventory verification service" ], "technologyProperties": { "integrationMethod": "CSV/spreadsheet import with hash verification", "stockTracking": "Periodic sync", "reconciliation": "Semi-automated" } }, "guidance-needed": { "technologies": [ "Inventory integration framework" ], "technologyProperties": { "integrationMethod": "To be determined", "stockTracking": "To be determined", "reconciliation": "To be determined" } } }, "prefillFrom": null, "briefSection": "Inventory management", "text": "How are inventory and stock levels currently tracked?", "ngoText": "How are inventory and stock levels currently tracked?" }, { "id": "audit-mechanism-approach", "type": "select", "options": [ { "label": "Automatic checks that flag problems as they happen", "value": "automated-realtime" }, { "label": "Regular scheduled reviews with tamper-proof records", "value": "periodic-batch" }, { "label": "Ability to check any record at any time with proof it has not been altered", "value": "on-demand" }, { "label": "External auditors can log in and review records independently", "value": "third-party" } ], "propertyMapping": { "automated-realtime": { "technologies": [ "Real-time audit mechanism", "Automated anomaly detection", "Audit alert service" ], "technologyProperties": { "auditFrequency": "Continuous / real-time", "auditAccess": "System-generated alerts", "complianceReporting": "Automated" } }, "periodic-batch": { "technologies": [ "Periodic audit mechanism", "Batch verification engine", "Audit report generator" ], "technologyProperties": { "auditFrequency": "Scheduled (daily/weekly/monthly)", "auditAccess": "Generated audit reports", "complianceReporting": "Scheduled" } }, "on-demand": { "technologies": [ "On-demand audit mechanism", "Audit query interface", "Record verification service" ], "technologyProperties": { "auditFrequency": "On-demand", "auditAccess": "Query-based", "complianceReporting": "On request" } }, "third-party": { "technologies": [ "Third-party audit mechanism", "Auditor access portal", "Audit evidence export" ], "technologyProperties": { "auditFrequency": "As required by auditor", "auditAccess": "Dedicated portal with read-only access", "complianceReporting": "Auditor-directed" } } }, "prefillFrom": null, "briefSection": "Audit and verification", "text": "Who needs to verify that actions happened correctly, and how easily should they be able to check?", "ngoText": "How should auditing and verification work for this solution?" }, { "id": "reporting-approach", "type": "select", "options": [ { "label": "Automated donor/funder reporting with scheduled delivery", "value": "automated-donor" }, { "label": "Self-service dashboard with custom report builder", "value": "self-service" }, { "label": "Regulatory compliance reporting (government/authority)", "value": "regulatory" }, { "label": "Multi-audience reporting (donors, government, community)", "value": "multi-audience" } ], "propertyMapping": { "automated-donor": { "technologies": [ "Automated reporting module", "Donor report template engine", "Scheduled report delivery service" ], "technologyProperties": { "reportAudience": "Donors and funders", "frequency": "Scheduled (monthly/quarterly)", "format": "PDF/spreadsheet with blockchain verification" } }, "self-service": { "technologies": [ "Self-service reporting module", "Custom report builder", "Data visualisation engine" ], "technologyProperties": { "reportAudience": "Internal staff and managers", "frequency": "On-demand", "format": "Interactive dashboard + export" } }, "regulatory": { "technologies": [ "Regulatory reporting module", "Compliance report generator", "Authority submission gateway" ], "technologyProperties": { "reportAudience": "Government and regulatory authorities", "frequency": "As required by regulation", "format": "Authority-specified format" } }, "multi-audience": { "technologies": [ "Multi-audience reporting module", "Role-based report engine", "Report distribution service" ], "technologyProperties": { "reportAudience": "Multiple stakeholders", "frequency": "Varies by audience", "format": "Tailored per audience" } } }, "prefillFrom": null, "briefSection": "Reporting", "text": "What reporting capabilities does this solution need?", "ngoText": "What reporting capabilities does this solution need?" } ], "complexityFactors": { "relationships": 2, "operationalChange": 2, "dataCompliance": 1 }, "suggestedCriteria": [ { "id": "SC-VALUATION-METHOD", "name": "Fair Market Valuation Methodology", "description": "The system supports defensible fair market valuation of in-kind donations. Accurate valuation is critical for financial reporting, donor tax receipts, and programme cost analysis. Overvaluation is a common audit finding.", "weight": 0.3, "ratingGuide": { "5": "Multiple valuation methods (fair market value, replacement cost, donor-declared value) with audit-ready justification. Market price reference databases. Automated valuation for common categories. Conforms to ASC 958 / IAS 20 / relevant accounting standards.", "4": "Configurable valuation methods with documentation. Market price references for major categories. Accounting standard alignment.", "3": "Standard valuation template. Manual market price research. Basic accounting standard compliance.", "2": "Single valuation method (donor-declared). No market price verification. Limited compliance documentation.", "1": "No valuation support. Goods tracked by quantity only, not value." } }, { "id": "SC-LIFECYCLE-TRACK", "name": "Donation Lifecycle Tracking", "description": "The system can track donated goods from receipt through storage, allocation to programmes, deployment, and final disposition. Full lifecycle tracking ensures accountability for every donated item.", "weight": 0.25, "ratingGuide": { "5": "Complete lifecycle: receipt \u2192 inspection \u2192 valuation \u2192 storage \u2192 allocation \u2192 deployment \u2192 disposition/disposal. Status tracking at each stage. Handles partial allocations and transfers between programmes. Disposal documentation.", "4": "Lifecycle tracking from receipt to deployment. Allocation by programme. Basic disposition recording.", "3": "Receipt to allocation tracking. Manual deployment recording. Limited disposition tracking.", "2": "Receipt and current location tracking only. No programme allocation linkage.", "1": "Receipt recording only. No lifecycle tracking." } }, { "id": "SC-DONOR-RESTRICT", "name": "Donor Restriction & Earmarking Compliance", "description": "The system can enforce donor restrictions on how donated goods are used (specific programmes, geographies, beneficiary groups). Violating donor restrictions has legal and reputational consequences.", "weight": 0.2, "ratingGuide": { "5": "Configurable donor restrictions per donation (programme, geography, beneficiary type, time period). System enforces restrictions during allocation. Alerts on attempted non-compliant use. Restriction compliance reporting.", "4": "Donor restriction recording with allocation warnings. Basic compliance checks. Restriction reports available.", "3": "Donor restrictions noted in records. Manual compliance checking during allocation. Basic reporting.", "2": "Free-text restriction notes. No automated compliance. No restriction-specific reporting.", "1": "No donor restriction tracking." } }, { "id": "SC-FINANCIAL-INTEG", "name": "Financial System Integration", "description": "The system can integrate with the NGO's financial/accounting system to flow donation values into the general ledger. In-kind donations often represent significant assets that must be properly accounted for.", "weight": 0.15, "ratingGuide": { "5": "Pre-built integrations with major NGO accounting systems. Automated journal entries for receipt, depreciation, and disposal. Multi-currency support.", "4": "API-based integration capability. Standard accounting export formats (CSV, XML). Automated journal entry generation.", "3": "Accounting-formatted export files. Manual import to financial system. Basic journal entry templates.", "2": "Value reports exportable to spreadsheet. Manual accounting entry required.", "1": "No financial system integration. Separate tracking from financial records." } }, { "id": "SC-AUDIT-READY", "name": "Audit Trail & Compliance Documentation", "description": "The system maintains an audit-ready trail of all donation transactions, valuations, allocations, and dispositions. In-kind donation management is frequently audited by donors and regulators.", "weight": 0.1, "ratingGuide": { "5": "Immutable audit trail for every transaction. Timestamped, user-attributed entries. Document attachment (photos, receipts, certificates). Audit workspace for external auditors with read-only access. Compliance with major donor audit requirements (USAID, ECHO, DFID).", "4": "Complete audit trail with user attribution. Document attachments. Exportable audit reports. Role-based access for auditors.", "3": "Transaction log with timestamps. Basic document linkage. Manual audit report generation.", "2": "Basic transaction log. Limited documentation. No auditor access features.", "1": "No audit trail. Relies on paper records." } } ], "procurement": { "marketMaturity": "emerging", "primaryMode": "rfq", "alternativeModes": [ "off-the-shelf" ], "reasoning": "In-kind donation valuation tools exist alongside general inventory SaaS.", "exampleProductCategories": [ "in-kind-donation-platform", "inventory-saas" ], "partnerChannels": [], "lastReviewed": "2026-05-01" } }, { "id": "UC-D-059", "name": "Shelter materials and non-food item tracking", "category": "D", "subcategory": "Inventory Management", "description": "Count shelter materials and household items out of the warehouse and into the hands of families, to spot diversion or losses early.", "bCriteria": [ "B1", "B3" ], "requiredComponents": [ { "component": "tracking-platform", "description": "NFI tracking system" }, { "component": "qr-barcode", "description": "NFI item identification" }, { "component": "inventory-integration", "description": "Inventory management" }, { "component": "audit-mechanism", "description": "Distribution audit trail" } ], "conditionalComponents": [ { "component": "last-mile-verification", "condition": "If beneficiary receipt verification" } ], "crossCategoryDependencies": [], "p2TriggerConditions": { "description": "Activated when P2 shows shelter/NFI distributions + high volume + tracking needs", "rangeSignals": [ "distributions >= frequent", "volumePerDistribution >= large", "trackingBurden >= high" ] }, "contextFieldsTemplate": [ { "field": "beneficiaries", "source": "P2 programme scale", "description": "People receiving NFI" }, { "field": "items", "source": "P2 NFI kit contents", "description": "Types of items" }, { "field": "distributionFrequency", "source": "P2 programme schedule", "description": "How often distributed" }, { "field": "replenishment", "source": "P2 logistics", "description": "Replenishment approach" } ], "implementationComplexity": "low-medium", "examples": { "note": "NFI management in emergencies", "references": [ { "name": "UNHCR NFI Tracking System", "url": "https://www.unhcr.org/supplies-and-services/nfi", "solved": "Established NFI distribution and tracking standards for 80+ countries" }, { "name": "International Rescue Committee - Shelter Materials", "url": "https://www.rescue.org/topics/emergency-shelter", "solved": "Implemented NFI tracking across emergency response operations" } ] }, "solutionQuestions": [ { "id": "shelter-nfi-item-types", "type": "select", "options": [ { "label": "Shelter materials only", "value": "shelter-only" }, { "label": "NFI core items (blankets, mats, pots)", "value": "nfi-core" }, { "label": "Extended NFI (tools, hygiene, cooking, lighting)", "value": "nfi-extended" } ], "propertyMapping": { "shelter-only": { "technologies": [ "Shelter material tracking", "Construction component system" ], "technologyProperties": { "itemCount": "5-10", "trackingComplexity": "simple", "dataFields": "type-quantity-location", "catalogueSize": "small" } }, "nfi-core": { "technologies": [ "NFI inventory system", "Essential items tracker" ], "technologyProperties": { "itemCount": "10-20", "trackingComplexity": "moderate", "dataFields": "category-subcategory-quantity", "catalogueSize": "medium" } }, "nfi-extended": { "technologies": [ "Extended NFI management platform", "Comprehensive inventory system" ], "technologyProperties": { "itemCount": "30+", "trackingComplexity": "complex", "dataFields": "full-item-hierarchy", "catalogueSize": "large" } } }, "prefillFrom": null, "briefSection": "Inventory management", "text": "What types of shelter and NFI items are tracked?", "ngoText": "What types of shelter and NFI items are tracked?" }, { "id": "nfi-distribution-model", "type": "select", "options": [ { "label": "Centralized distribution events", "value": "centralized-events" }, { "label": "Partner organization distribution", "value": "partner-distribution" }, { "label": "Community-based distribution networks", "value": "community-networks" } ], "propertyMapping": { "centralized-events": { "technologies": [ "Event-based distribution platform", "Central warehouse system" ], "technologyProperties": { "numberOfDistributionPoints": "1-3", "frequencyOfDistribution": "periodic", "beneficiaryVerification": "event-based", "scalability": "limited" } }, "partner-distribution": { "technologies": [ "Partner coordination platform", "Multi-site distribution system" ], "technologyProperties": { "numberOfDistributionPoints": "5-20", "frequencyOfDistribution": "regular", "beneficiaryVerification": "partner-verified", "scalability": "good" } }, "community-networks": { "technologies": [ "Community distribution network", "Grassroots coordination platform" ], "technologyProperties": { "numberOfDistributionPoints": "50+", "frequencyOfDistribution": "continuous", "beneficiaryVerification": "community-verified", "scalability": "excellent" } } }, "prefillFrom": null, "briefSection": "Tracking and provenance", "text": "How are shelter/NFI items distributed to beneficiaries?", "ngoText": "How are shelter/NFI items distributed to beneficiaries?" }, { "id": "nfi-beneficiary-verification", "type": "select", "options": [ { "label": "Name and ID check against list", "value": "name-id-check" }, { "label": "Digital beneficiary registry with mobile verification", "value": "digital-registry" }, { "label": "Biometric verification with photo ID", "value": "biometric-id" } ], "propertyMapping": { "name-id-check": { "technologies": [ "List-based verification system", "Manual checklist" ], "technologyProperties": { "verificationAccuracy": "moderate", "fraudRisk": "moderate", "adminOverhead": "high", "scalability": "limited" } }, "digital-registry": { "technologies": [ "Digital beneficiary registry", "Mobile verification application" ], "technologyProperties": { "verificationAccuracy": "high", "fraudRisk": "low", "adminOverhead": "low", "scalability": "good" } }, "biometric-id": { "technologies": [ "Biometric verification system", "Photographic identity platform" ], "technologyProperties": { "verificationAccuracy": "very-high", "fraudRisk": "very-low", "adminOverhead": "low", "scalability": "excellent" } } }, "prefillFrom": null, "briefSection": "Last-mile verification", "text": "How are beneficiaries verified at distribution?", "ngoText": "How are beneficiaries verified at distribution?" }, { "id": "nfi-replenishment-planning", "type": "select", "options": [ { "label": "Manual reordering based on stock checks", "value": "manual-reorder" }, { "label": "Automated alerts at reorder point", "value": "automated-alerts" }, { "label": "Predictive demand forecasting", "value": "predictive-demand" } ], "propertyMapping": { "manual-reorder": { "technologies": [ "Manual inventory checklist", "Order management" ], "technologyProperties": { "reorderFrequency": "monthly", "automationLevel": "none", "stockoutRisk": "high", "adminEffort": "high" } }, "automated-alerts": { "technologies": [ "Inventory alert system", "Automated reorder platform" ], "technologyProperties": { "reorderFrequency": "threshold-based", "automationLevel": "partial", "stockoutRisk": "low", "adminEffort": "low" } }, "predictive-demand": { "technologies": [ "Demand forecasting engine", "Predictive analytics platform" ], "technologyProperties": { "reorderFrequency": "optimised", "automationLevel": "full", "stockoutRisk": "minimal", "adminEffort": "minimal" } } }, "prefillFrom": null, "briefSection": "Inventory management", "text": "How do you currently plan and track NFI replenishment?", "ngoText": "How do you currently plan and track NFI replenishment?" }, { "id": "shelter-nfi-stakeholders", "type": "select", "options": [ { "label": "Internal only (1\u20132 teams)", "value": "internal" }, { "label": "Internal + 1\u20133 external partners", "value": "few-external" }, { "label": "Multiple external stakeholders (4\u201310)", "value": "multi-external" }, { "label": "Ecosystem-wide (donors, partners, beneficiaries, regulators)", "value": "ecosystem" } ], "propertyMapping": { "internal": { "technologies": [ "Private ledger" ], "technologyProperties": { "accessControl": "Simple role-based", "networkType": "Private" } }, "few-external": { "technologies": [ "Permissioned network", "Selective data sharing" ], "technologyProperties": { "accessControl": "Partner-level permissions", "networkType": "Consortium" } }, "multi-external": { "technologies": [ "Permissioned network", "Multi-party access layer" ], "technologyProperties": { "accessControl": "Granular role-based", "networkType": "Consortium" } }, "ecosystem": { "technologies": [ "Permissioned public network", "Data marketplace" ], "technologyProperties": { "accessControl": "Multi-tier with public layer", "networkType": "Hybrid public-private" } } }, "prefillFrom": null, "briefSection": "Governance and access", "text": "How many distinct parties need visibility into the shelter and NFI distribution data?", "ngoText": "How many distinct parties need visibility into the shelter and NFI distribution data?" }, { "id": "item-tracking-method", "type": "select", "options": [ { "label": "QR codes printed on items or packaging", "value": "qr-codes" }, { "label": "NFC tags embedded in items", "value": "nfc-tags" }, { "label": "Barcode labels with batch scanning", "value": "barcode" }, { "label": "Mixed: QR for high-value items, barcode for bulk", "value": "mixed" } ], "propertyMapping": { "qr-codes": { "technologies": [ "QR code generation service", "QR/barcode scanning app", "Item-level tracking ledger" ], "technologyProperties": { "trackingGranularity": "Per-item or per-batch", "scanMethod": "Mobile phone camera / QR scanner", "offlineCapable": "Yes \u2014 scan and sync when connected" } }, "nfc-tags": { "technologies": [ "NFC tag provisioning", "NFC reader integration", "Item-level tracking ledger" ], "technologyProperties": { "trackingGranularity": "Per-item", "scanMethod": "NFC-enabled device", "offlineCapable": "Yes \u2014 NFC works offline" } }, "barcode": { "technologies": [ "Barcode generation service", "QR/barcode scanning app", "Batch tracking ledger" ], "technologyProperties": { "trackingGranularity": "Per-batch", "scanMethod": "Barcode scanner / mobile camera", "offlineCapable": "Yes \u2014 scan and sync" } }, "mixed": { "technologies": [ "QR code generation service", "Barcode generation service", "QR/barcode scanning app", "Multi-level tracking ledger" ], "technologyProperties": { "trackingGranularity": "Mixed \u2014 item-level for high-value, batch for bulk", "scanMethod": "Mobile phone camera / scanner", "offlineCapable": "Yes" } } }, "prefillFrom": null, "briefSection": "Item tracking", "text": "How will physical items be tracked and scanned in the field?", "ngoText": "How will physical items be tracked and scanned in the field?" }, { "id": "audit-mechanism-approach", "type": "select", "options": [ { "label": "Automatic checks that flag problems as they happen", "value": "automated-realtime" }, { "label": "Regular scheduled reviews with tamper-proof records", "value": "periodic-batch" }, { "label": "Ability to check any record at any time with proof it has not been altered", "value": "on-demand" }, { "label": "External auditors can log in and review records independently", "value": "third-party" } ], "propertyMapping": { "automated-realtime": { "technologies": [ "Real-time audit mechanism", "Automated anomaly detection", "Audit alert service" ], "technologyProperties": { "auditFrequency": "Continuous / real-time", "auditAccess": "System-generated alerts", "complianceReporting": "Automated" } }, "periodic-batch": { "technologies": [ "Periodic audit mechanism", "Batch verification engine", "Audit report generator" ], "technologyProperties": { "auditFrequency": "Scheduled (daily/weekly/monthly)", "auditAccess": "Generated audit reports", "complianceReporting": "Scheduled" } }, "on-demand": { "technologies": [ "On-demand audit mechanism", "Audit query interface", "Record verification service" ], "technologyProperties": { "auditFrequency": "On-demand", "auditAccess": "Query-based", "complianceReporting": "On request" } }, "third-party": { "technologies": [ "Third-party audit mechanism", "Auditor access portal", "Audit evidence export" ], "technologyProperties": { "auditFrequency": "As required by auditor", "auditAccess": "Dedicated portal with read-only access", "complianceReporting": "Auditor-directed" } } }, "prefillFrom": null, "briefSection": "Audit and verification", "text": "Who needs to verify that actions happened correctly, and how easily should they be able to check?", "ngoText": "How should auditing and verification work for this solution?" } ], "complexityFactors": { "relationships": 2, "operationalChange": 2, "dataCompliance": 1 }, "suggestedCriteria": [ { "id": "SC-NFI-KIT", "name": "Kit Composition & BOM Management", "description": "The system can manage Non-Food Item kits as bills of materials, tracking individual components while distributing as assembled kits. NFI distributions involve standardised kits (hygiene kits, shelter kits, winterisation kits) with specific component lists.", "weight": 0.25, "ratingGuide": { "5": "Full BOM management: define kit compositions, track component inventory separately, auto-calculate kit availability from components, handle substitutions. Supports multiple kit configurations (family size variants, climate variants). Kit assembly/disassembly tracking.", "4": "Kit composition defined with component tracking. Kit availability calculation. Basic substitution support. Size variants.", "3": "Kit templates defined. Component tracking at aggregate level. Manual availability calculation.", "2": "Kits tracked as single items. No component-level visibility. No substitution support.", "1": "No kit management. Individual items tracked without kit concept." } }, { "id": "SC-DISTRIBUTION-PLAN", "name": "Distribution Planning & Targeting", "description": "The system can support needs-based distribution planning, matching available NFI stock to assessed needs by location, family size, and vulnerability. Distribution planning prevents both shortfalls and oversupply.", "weight": 0.25, "ratingGuide": { "5": "Needs assessment integration. Distribution plans based on registered households, family size, vulnerability score. Gap analysis (stock vs. need). Prioritisation rules. Multi-round distribution tracking (prevents duplication). Map-based planning.", "4": "Household-based distribution planning. Gap analysis. Basic prioritisation. Duplication prevention. List-based planning.", "3": "Site-level distribution planning. Manual needs matching. Basic duplication checks.", "2": "Aggregate allocation by site. No household-level planning. No duplication prevention.", "1": "No distribution planning. Stock dispatched on request without needs matching." } }, { "id": "SC-EMERGENCY-SPEED", "name": "Emergency Deployment Speed", "description": "This measures how quickly the system can be deployed in a new emergency. Shelter and NFI distributions often occur in the first 72 hours of a crisis response when there's no time for lengthy system setup.", "weight": 0.2, "ratingGuide": { "5": "Pre-configured emergency templates. Deploy in <4 hours. Offline-first mobile app. Works with no existing infrastructure. Pre-loaded standard NFI catalogues (UNHCR, IFRC). Rapid beneficiary registration.", "4": "Deploy in <24 hours. Emergency templates available. Mobile app with offline capability. Standard NFI catalogues.", "3": "Deploy in 1-3 days. Some pre-configuration needed. Mobile capable but setup required.", "2": "Deploy in 1-2 weeks. Significant configuration needed. Desktop-first system.", "1": "Lengthy implementation (>2 weeks). Not designed for emergency deployment." } }, { "id": "SC-BENEFICIARY-VERIFY", "name": "Beneficiary Receipt Verification", "description": "This looks at how the system confirms that NFIs reached the intended beneficiaries. Receipt verification prevents diversion and provides accountability evidence.", "weight": 0.2, "ratingGuide": { "5": "Multiple verification methods (QR beneficiary card, biometric, digital signature). GPS-stamped receipt. Photo evidence option. Real-time reconciliation against distribution lists. Anti-fraud checks (duplicate detection, geographic anomalies).", "4": "Card-based or digital verification. GPS stamp. Reconciliation against lists. Basic anti-fraud.", "3": "Digital sign-off by beneficiary or representative. Manual list reconciliation.", "2": "Paper-based sign-off digitised post-distribution. No real-time verification.", "1": "No beneficiary-level receipt verification." } }, { "id": "SC-DONOR-COMPLY", "name": "Multi-Donor Compliance & Reporting", "description": "The system can track which donor funded which NFI stock and generate donor-specific distribution reports. NFI programmes often blend stock from multiple donors with different reporting requirements.", "weight": 0.1, "ratingGuide": { "5": "Stock tagged by donor/funding source. Donor-specific distribution reports generated automatically. Handles co-mingled stock with proportional attribution. Compliance with major humanitarian donor reporting formats.", "4": "Stock donor-tagged. Donor-specific reports available. Basic co-mingling rules. Standard reporting formats.", "3": "Donor recorded at receipt. Aggregate donor reports. Manual co-mingled stock attribution.", "2": "Donor noted in records but no donor-specific reporting. Manual attribution.", "1": "No donor tracking or donor-specific reporting." } } ], "procurement": { "marketMaturity": "emerging", "primaryMode": "rfq", "alternativeModes": [ "off-the-shelf" ], "reasoning": "Shelter/NFI tracking overlaps with general humanitarian inventory SaaS.", "exampleProductCategories": [ "humanitarian-inventory-saas", "nfi-tracking-platform" ], "partnerChannels": [], "lastReviewed": "2026-05-01" } }, { "id": "UC-D-060", "name": "Water, sanitation and hygiene supplies verification", "category": "D", "subcategory": "Inventory Management", "description": "Follow water, sanitation and hygiene supplies from manufacturer to community, so you can catch substandard or contaminated items before they are used.", "bCriteria": [ "B1", "B3" ], "requiredComponents": [ { "component": "tracking-platform", "description": "WASH supply tracking" }, { "component": "qr-barcode", "description": "Supply batch tracking" }, { "component": "inventory-integration", "description": "Stock management" }, { "component": "quality-assurance", "description": "Quality verification" } ], "conditionalComponents": [ { "component": "iot-sensors", "condition": "If water quality monitoring" } ], "crossCategoryDependencies": [], "p2TriggerConditions": { "description": "Activated when P2 shows WASH programmes + supply verification + quality assurance", "rangeSignals": [ "washProgramme >= true", "beneficiaries >= 1000+", "qualityAssurance >= important" ] }, "contextFieldsTemplate": [ { "field": "beneficiaries", "source": "P2 WASH coverage", "description": "People served" }, { "field": "supplyTypes", "source": "P2 WASH interventions", "description": "Types of supplies" }, { "field": "locations", "source": "P0 WASH sites", "description": "WASH facility locations" }, { "field": "quality", "source": "P2 quality standards", "description": "Quality requirements" } ], "implementationComplexity": "low-medium", "examples": { "note": "WASH supply chain management", "references": [ { "name": "UNICEF WASH Supply Chain", "url": "https://www.unicef.org/wash/supply-chain", "solved": "Managed WASH supplies distribution to 50+ countries" }, { "name": "Oxfam WASH Programmes", "url": "https://www.oxfam.org/en/what-we-do/water-sanitation-hygiene", "solved": "Implemented WASH supply tracking in emergency situations" } ] }, "solutionQuestions": [ { "id": "wash-supply-types", "type": "select", "options": [ { "label": "Water supply systems only", "value": "water-only" }, { "label": "Water and sanitation supplies", "value": "water-sanitation" }, { "label": "Comprehensive WASH (water, sanitation, hygiene)", "value": "comprehensive-wash" } ], "propertyMapping": { "water-only": { "technologies": [ "Water supply tracking", "Pump and storage monitoring" ], "technologyProperties": { "productCategories": "3-5", "trackingComplexity": "simple", "suppliersInvolved": "1-5", "maintenanceRequirement": "routine" } }, "water-sanitation": { "technologies": [ "Water and sanitation inventory system", "Dual-track platform" ], "technologyProperties": { "productCategories": "8-12", "trackingComplexity": "moderate", "suppliersInvolved": "5-15", "maintenanceRequirement": "complex" } }, "comprehensive-wash": { "technologies": [ "Comprehensive WASH management system", "Integrated WASH platform" ], "technologyProperties": { "productCategories": "15+", "trackingComplexity": "high", "suppliersInvolved": "15+", "maintenanceRequirement": "very-complex" } } }, "prefillFrom": null, "briefSection": "Inventory management", "text": "Which WASH supply categories are covered?", "ngoText": "Which WASH supply categories are covered?" }, { "id": "wash-quality-testing", "type": "select", "options": [ { "label": "Visual inspection only", "value": "visual-test" }, { "label": "Basic functionality testing", "value": "functionality-test" }, { "label": "Laboratory water quality testing", "value": "lab-testing" } ], "propertyMapping": { "visual-test": { "technologies": [ "Visual inspection checklist", "Compliance observation system" ], "technologyProperties": { "testingCost": "low", "testingFrequency": "per-delivery", "qualityAssurance": "basic", "technicalExpertise": "minimal" } }, "functionality-test": { "technologies": [ "Functionality test platform", "Performance verification system" ], "technologyProperties": { "testingCost": "moderate", "testingFrequency": "periodic", "qualityAssurance": "good", "technicalExpertise": "moderate" } }, "lab-testing": { "technologies": [ "Water quality testing lab", "Laboratory analysis platform" ], "technologyProperties": { "testingCost": "high", "testingFrequency": "sample-based", "qualityAssurance": "high", "technicalExpertise": "high" } } }, "prefillFrom": null, "briefSection": "Quality assurance", "text": "What quality testing is required for WASH supplies?", "ngoText": "What quality testing is required for WASH supplies?" }, { "id": "wash-distribution-model", "type": "select", "options": [ { "label": "Centralized warehouse distribution", "value": "centralized-warehouse" }, { "label": "Hub-and-spoke network distribution", "value": "hub-and-spoke" }, { "label": "Community-based distribution", "value": "community-based" } ], "propertyMapping": { "centralized-warehouse": { "technologies": [ "Centralized inventory system", "Direct distribution platform" ], "technologyProperties": { "distributionHubs": "1", "deliveryTime": "slow", "costEfficiency": "moderate", "coverageArea": "limited" } }, "hub-and-spoke": { "technologies": [ "Hub-and-spoke network", "Regional distribution platform" ], "technologyProperties": { "distributionHubs": "3-10", "deliveryTime": "moderate", "costEfficiency": "good", "coverageArea": "regional" } }, "community-based": { "technologies": [ "Community distribution network", "Grassroots supply platform" ], "technologyProperties": { "distributionHubs": "50+", "deliveryTime": "fast", "costEfficiency": "variable", "coverageArea": "extensive" } } }, "prefillFrom": null, "briefSection": "Tracking and provenance", "text": "What distribution model is used for WASH supplies?", "ngoText": "What distribution model is used for WASH supplies?" }, { "id": "wash-volume", "type": "select", "options": [ { "label": "Under 1,000 items", "value": "small" }, { "label": "1,000\u201310,000 items", "value": "medium" }, { "label": "10,000\u2013100,000 items", "value": "large" }, { "label": "Over 100,000 items", "value": "enterprise" } ], "propertyMapping": { "small": { "technologies": [ "Simple ledger" ], "technologyProperties": { "scalability": "Standard", "throughput": "Low" } }, "medium": { "technologies": [ "Standard tracking platform" ], "technologyProperties": { "scalability": "Standard", "throughput": "Medium" } }, "large": { "technologies": [ "High-throughput tracking platform", "Batch processing" ], "technologyProperties": { "scalability": "High", "throughput": "High \u2014 batch optimised" } }, "enterprise": { "technologies": [ "Enterprise tracking platform", "Layer 2 scaling" ], "technologyProperties": { "scalability": "Enterprise", "throughput": "Very high \u2014 L2 required" } } }, "prefillFrom": null, "briefSection": "Infrastructure requirements", "text": "What is the monthly volume of WASH supplies you need to track?", "ngoText": "What is the monthly volume of WASH supplies you need to track?" }, { "id": "wash-stakeholders", "type": "select", "options": [ { "label": "Internal only (1\u20132 teams)", "value": "internal" }, { "label": "Internal + 1\u20133 external partners", "value": "few-external" }, { "label": "Multiple external stakeholders (4\u201310)", "value": "multi-external" }, { "label": "Ecosystem-wide (donors, partners, beneficiaries, regulators)", "value": "ecosystem" } ], "propertyMapping": { "internal": { "technologies": [ "Private ledger" ], "technologyProperties": { "accessControl": "Simple role-based", "networkType": "Private" } }, "few-external": { "technologies": [ "Permissioned network", "Selective data sharing" ], "technologyProperties": { "accessControl": "Partner-level permissions", "networkType": "Consortium" } }, "multi-external": { "technologies": [ "Permissioned network", "Multi-party access layer" ], "technologyProperties": { "accessControl": "Granular role-based", "networkType": "Consortium" } }, "ecosystem": { "technologies": [ "Permissioned public network", "Data marketplace" ], "technologyProperties": { "accessControl": "Multi-tier with public layer", "networkType": "Hybrid public-private" } } }, "prefillFrom": null, "briefSection": "Governance and access", "text": "How many distinct parties need visibility into the WASH supply chain data?", "ngoText": "How many distinct parties need visibility into the WASH supply chain data?" }, { "id": "sq-UC-D-060-001", "type": "single-select", "options": [ { "value": "point-of-use-testing", "label": "Point-of-use testing" }, { "value": "source-testing", "label": "Source water testing" }, { "value": "distribution-point-testing", "label": "Distribution point testing" }, { "value": "no-water-testing", "label": "No water testing" }, { "value": "periodic-sampling", "label": "Periodic sampling" } ], "propertyMapping": { "point-of-use-testing": { "technologies": [ "field-testing-kit", "beneficiary-testing" ], "technologyProperties": {} }, "source-testing": { "technologies": [ "water-lab", "source-monitoring" ], "technologyProperties": {} }, "distribution-point-testing": { "technologies": [ "distribution-testing", "facility-monitoring" ], "technologyProperties": {} }, "no-water-testing": { "technologies": [ "supply-only", "no-testing" ], "technologyProperties": {} }, "periodic-sampling": { "technologies": [ "sampling-protocol", "laboratory-analysis" ], "technologyProperties": {} } }, "briefSection": "requirements", "text": "What water quality testing results should be linked to WASH supply distribution records?", "ngoText": "What water quality testing results should be linked to WASH supply distribution records?" }, { "id": "item-tracking-method", "type": "select", "options": [ { "label": "QR codes printed on items or packaging", "value": "qr-codes" }, { "label": "NFC tags embedded in items", "value": "nfc-tags" }, { "label": "Barcode labels with batch scanning", "value": "barcode" }, { "label": "Mixed: QR for high-value items, barcode for bulk", "value": "mixed" } ], "propertyMapping": { "qr-codes": { "technologies": [ "QR code generation service", "QR/barcode scanning app", "Item-level tracking ledger" ], "technologyProperties": { "trackingGranularity": "Per-item or per-batch", "scanMethod": "Mobile phone camera / QR scanner", "offlineCapable": "Yes \u2014 scan and sync when connected" } }, "nfc-tags": { "technologies": [ "NFC tag provisioning", "NFC reader integration", "Item-level tracking ledger" ], "technologyProperties": { "trackingGranularity": "Per-item", "scanMethod": "NFC-enabled device", "offlineCapable": "Yes \u2014 NFC works offline" } }, "barcode": { "technologies": [ "Barcode generation service", "QR/barcode scanning app", "Batch tracking ledger" ], "technologyProperties": { "trackingGranularity": "Per-batch", "scanMethod": "Barcode scanner / mobile camera", "offlineCapable": "Yes \u2014 scan and sync" } }, "mixed": { "technologies": [ "QR code generation service", "Barcode generation service", "QR/barcode scanning app", "Multi-level tracking ledger" ], "technologyProperties": { "trackingGranularity": "Mixed \u2014 item-level for high-value, batch for bulk", "scanMethod": "Mobile phone camera / scanner", "offlineCapable": "Yes" } } }, "prefillFrom": null, "briefSection": "Item tracking", "text": "How will physical items be tracked and scanned in the field?", "ngoText": "How will physical items be tracked and scanned in the field?" } ], "complexityFactors": { "relationships": 2, "operationalChange": 2, "dataCompliance": 1 }, "suggestedCriteria": [ { "id": "SC-QUALITY-ASSURANCE", "name": "Product Quality & Standards Verification", "description": "The system can verify that WASH supplies meet quality standards (water purification tablets meeting WHO specifications, soap meeting hygiene standards, latrine materials meeting structural requirements). Sub-standard WASH supplies can endanger health.", "weight": 0.3, "ratingGuide": { "5": "Configurable quality standards per product category aligned with WHO/Sphere standards. Batch testing records linked to supply records. Certificate of analysis capture. Automated flagging of non-compliant batches. Supplier quality scoring over time.", "4": "Quality checklist per product type. Test record linkage. Certificate capture. Basic compliance flagging.", "3": "Generic quality inspection workflow. Manual standard reference. Basic certificate recording.", "2": "Free-text quality notes. No structured quality standards. No certificate management.", "1": "No quality verification features." } }, { "id": "SC-CONSUMPTION-TRACK", "name": "Consumption Rate Tracking & Replenishment", "description": "The system can track consumption rates and trigger replenishment. WASH supplies are consumables. Running out of water treatment chemicals or hygiene items creates immediate health risks.", "weight": 0.25, "ratingGuide": { "5": "Automatic consumption rate calculation per site. Predictive replenishment based on population, season, and usage patterns. Stockout risk alerts with lead-time awareness. Integration with procurement for automated reorder suggestions.", "4": "Consumption tracking by site. Reorder point alerts. Basic demand forecasting. Manual procurement linkage.", "3": "Monthly consumption reporting. Fixed reorder points. Manual replenishment planning.", "2": "Periodic stock counts. No consumption rate analysis. Reactive replenishment.", "1": "No consumption tracking. Physical inspection only." } }, { "id": "SC-WATER-QUALITY-IOT", "name": "Water Quality Monitoring Integration", "description": "The system can integrate water quality test results with supply chain data. For water treatment supplies, efficacy verification (residual chlorine levels, turbidity, bacterial counts) closes the accountability loop.", "weight": 0.2, "ratingGuide": { "5": "IoT water quality sensor integration (chlorine, turbidity, pH). Links test results to specific treatment supply batches. Automated alerts on out-of-range results. Dashboard correlating supply usage with water quality outcomes.", "4": "Manual water quality test data entry linked to supply records. Alerts on poor results. Basic correlation analysis.", "3": "Water quality data captured separately. Manual linkage to supply records. Basic reporting.", "2": "Water quality and supply data in separate systems. No correlation.", "1": "No water quality monitoring integration." } }, { "id": "SC-SITE-MAPPING", "name": "Geographic Distribution & Site Mapping", "description": "The system can map WASH supply distribution across sites and identify coverage gaps. WASH programmes operate across dispersed sites. Geographic visibility prevents some sites being oversupplied while others go without.", "weight": 0.15, "ratingGuide": { "5": "GIS-integrated mapping of all distribution sites. Stock levels overlaid on maps. Coverage gap analysis against population data. Route optimisation for deliveries. Cluster coordination data sharing.", "4": "Map-based view of sites with stock levels. Basic gap identification. Location-based reporting.", "3": "Site list with coordinates. Map visualisation of site locations. Manual gap analysis.", "2": "Site names and regions. No mapping. Manual geographic analysis.", "1": "No geographic awareness. Flat site list only." } }, { "id": "SC-SPHERE-COMPLY", "name": "Sphere Standards Compliance Tracking", "description": "The system helps track compliance with Sphere humanitarian standards for WASH (minimum quantities per person, quality thresholds, access distances). Sphere compliance is the benchmark for WASH programme adequacy.", "weight": 0.1, "ratingGuide": { "5": "Sphere WASH indicators pre-configured (litres/person/day, items per household, maximum distance to water point). Automatic compliance calculation per site. Dashboard showing Sphere compliance status. Reporting for cluster coordination.", "4": "Sphere indicators configurable. Compliance tracking per site. Basic dashboard. Standard reporting.", "3": "Sphere reference values available. Manual compliance calculation. Periodic reporting.", "2": "No Sphere-specific features. General tracking that can be manually compared to standards.", "1": "No standards compliance tracking." } } ], "procurement": { "marketMaturity": "emerging", "primaryMode": "rfq", "alternativeModes": [ "off-the-shelf" ], "reasoning": "WASH supplies tracking included in many humanitarian inventory products.", "exampleProductCategories": [ "wash-supply-platform", "humanitarian-inventory-saas" ], "partnerChannels": [], "lastReviewed": "2026-05-01" } }, { "id": "UC-D-061", "name": "Equipment and asset lifecycle tracking", "category": "D", "subcategory": "Asset Management", "description": "Keep one record for each piece of equipment showing where it is and how it has been maintained, even as it moves between sites.", "bCriteria": [ "B1", "B3" ], "requiredComponents": [ { "component": "tracking-platform", "description": "Asset lifecycle tracking" }, { "component": "qr-barcode", "description": "Asset identification" }, { "component": "audit-mechanism", "description": "Asset movement audit trail" }, { "component": "inventory-integration", "description": "Asset inventory" } ], "conditionalComponents": [ { "component": "iot-sensors", "condition": "If asset condition monitoring" }, { "component": "smart-contracts", "condition": "If automated maintenance schedules" } ], "crossCategoryDependencies": [], "p2TriggerConditions": { "description": "Activated when P2 shows high asset volume + depreciation tracking + maintenance burden", "rangeSignals": [ "assetValue >= significant", "maintenanceBurden >= high", "depreciation >= complex" ] }, "contextFieldsTemplate": [ { "field": "assetTypes", "source": "P0 assets", "description": "Types of assets" }, { "field": "assetValue", "source": "P0 fixed assets", "description": "Total asset value" }, { "field": "locations", "source": "P0 operations", "description": "Asset locations" }, { "field": "maintenanceNeeds", "source": "P2 asset management", "description": "Maintenance requirements" } ], "implementationComplexity": "medium", "examples": { "note": "NGO asset management systems", "references": [ { "name": "WHO Medical Equipment Management", "url": "https://www.who.int/equipment-and-technologies", "solved": "Established asset lifecycle management framework for health equipment" }, { "name": "UNICEF Asset Management", "url": "https://www.unicef.org/supply-logistics/asset-management", "solved": "Implemented equipment tracking across 150+ country programmes" } ] }, "solutionQuestions": [ { "id": "asset-types-classification", "type": "select", "options": [ { "label": "Single asset category", "value": "single-category" }, { "label": "Multiple categories (medical, vehicles, generators)", "value": "multiple-categories" }, { "label": "Hierarchical classification with detailed sub-categories", "value": "hierarchical-classification" } ], "propertyMapping": { "single-category": { "technologies": [ "Simple asset tracking", "Single-type register" ], "technologyProperties": { "assetTypes": "1-3", "dataFields": "basic", "trackingComplexity": "simple", "reportingComplexity": "simple" } }, "multiple-categories": { "technologies": [ "Multi-category asset platform", "Category-based tracking" ], "technologyProperties": { "assetTypes": "4-8", "dataFields": "category-specific", "trackingComplexity": "moderate", "reportingComplexity": "moderate" } }, "hierarchical-classification": { "technologies": [ "Advanced asset management system", "Hierarchical taxonomy engine" ], "technologyProperties": { "assetTypes": "20+", "dataFields": "comprehensive", "trackingComplexity": "high", "reportingComplexity": "high" } } }, "prefillFrom": null, "briefSection": "Inventory management", "text": "How do you currently classify and categorize assets in your programme?", "ngoText": "How do you currently classify and categorize assets in your programme?" }, { "id": "asset-lifecycle-depth", "type": "select", "options": [ { "label": "Acquisition and disposal only", "value": "basic-lifecycle" }, { "label": "Acquisition, maintenance, and disposal", "value": "maintenance-lifecycle" }, { "label": "Complete lifecycle with maintenance history and depreciation", "value": "full-lifecycle" } ], "propertyMapping": { "basic-lifecycle": { "technologies": [ "Basic asset registry", "Acquisition and disposal log" ], "technologyProperties": { "dataTracking": "acquisition-disposal", "maintenanceRecords": "none", "depreciationTracking": "none", "reportingFields": "minimal" } }, "maintenance-lifecycle": { "technologies": [ "Asset lifecycle platform", "Maintenance tracking system" ], "technologyProperties": { "dataTracking": "acquisition-maintenance-disposal", "maintenanceRecords": "basic", "depreciationTracking": "annual", "reportingFields": "comprehensive" } }, "full-lifecycle": { "technologies": [ "Enterprise asset management system", "Comprehensive lifecycle platform" ], "technologyProperties": { "dataTracking": "complete-history", "maintenanceRecords": "detailed", "depreciationTracking": "real-time", "reportingFields": "complete" } } }, "prefillFrom": null, "briefSection": "Tracking and provenance", "text": "How deep should asset lifecycle tracking be?", "ngoText": "How deep should asset lifecycle tracking be?", "hidden": true }, { "id": "asset-maintenance-tracking", "type": "select", "options": [ { "label": "Manual maintenance log kept with asset", "value": "manual-log" }, { "label": "Digital maintenance schedule and records", "value": "digital-schedule" }, { "label": "Predictive maintenance with IoT sensors", "value": "predictive-maintenance" } ], "propertyMapping": { "manual-log": { "technologies": [ "Paper maintenance log", "Manual record keeping" ], "technologyProperties": { "recordAccuracy": "variable", "maintenanceScheduling": "manual", "breakdownPrevention": "reactive", "dataAccessibility": "limited" } }, "digital-schedule": { "technologies": [ "Digital maintenance scheduling platform", "Work order system" ], "technologyProperties": { "recordAccuracy": "high", "maintenanceScheduling": "automated", "breakdownPrevention": "preventive", "dataAccessibility": "good" } }, "predictive-maintenance": { "technologies": [ "IoT asset monitoring system", "Predictive analytics engine" ], "technologyProperties": { "recordAccuracy": "very-high", "maintenanceScheduling": "ai-optimised", "breakdownPrevention": "predictive", "dataAccessibility": "real-time" } } }, "prefillFrom": null, "briefSection": "Infrastructure requirements", "text": "How do you currently track asset maintenance?", "ngoText": "How do you currently track asset maintenance?" }, { "id": "asset-depreciation-method", "type": "select", "options": [ { "label": "Straight-line depreciation", "value": "straight-line" }, { "label": "Accelerated depreciation (declining balance)", "value": "accelerated" }, { "label": "Usage-based depreciation", "value": "usage-based" } ], "propertyMapping": { "straight-line": { "technologies": [ "Standard depreciation calculator", "Accounting integration" ], "technologyProperties": { "calculationMethod": "time-based", "accountingStandard": "ifrs-gaap", "reportingFrequency": "annual", "complexityLevel": "simple" } }, "accelerated": { "technologies": [ "Accelerated depreciation engine", "Tax-efficient calculator" ], "technologyProperties": { "calculationMethod": "declining-balance", "accountingStandard": "ifrs-gaap", "reportingFrequency": "annual", "complexityLevel": "moderate" } }, "usage-based": { "technologies": [ "Usage tracking system", "Usage-based depreciation calculator" ], "technologyProperties": { "calculationMethod": "usage-based", "accountingStandard": "custom", "reportingFrequency": "continuous", "complexityLevel": "high" } } }, "prefillFrom": null, "briefSection": "Reporting and audit", "text": "Which depreciation method should be applied?", "ngoText": "Which depreciation method should be applied?", "hidden": true }, { "id": "asset-custody-chain", "type": "select", "options": [ { "label": "Single custodian per asset location", "value": "single-custodian" }, { "label": "Custodian transfer log", "value": "transfer-log" }, { "label": "Real-time tracking with location history", "value": "realtime-tracking" } ], "propertyMapping": { "single-custodian": { "technologies": [ "Custodian assignment system", "Location registry" ], "technologyProperties": { "custodyRecording": "static", "transferProcess": "manual", "locationAccuracy": "office-level", "auditTrail": "limited" } }, "transfer-log": { "technologies": [ "Custody transfer platform", "Handover documentation system" ], "technologyProperties": { "custodyRecording": "dynamic", "transferProcess": "documented", "locationAccuracy": "facility-level", "auditTrail": "complete" } }, "realtime-tracking": { "technologies": [ "GPS tracking system", "Real-time location platform" ], "technologyProperties": { "custodyRecording": "continuous", "transferProcess": "automated", "locationAccuracy": "precise", "auditTrail": "comprehensive" } } }, "prefillFrom": null, "briefSection": "Tracking and provenance", "text": "How do you currently track who has custody of assets as they move through your supply chain?", "ngoText": "How do you currently track who has custody of assets as they move through your supply chain?" }, { "id": "item-tracking-method", "type": "select", "options": [ { "label": "QR codes printed on items or packaging", "value": "qr-codes" }, { "label": "NFC tags embedded in items", "value": "nfc-tags" }, { "label": "Barcode labels with batch scanning", "value": "barcode" }, { "label": "Mixed: QR for high-value items, barcode for bulk", "value": "mixed" } ], "propertyMapping": { "qr-codes": { "technologies": [ "QR code generation service", "QR/barcode scanning app", "Item-level tracking ledger" ], "technologyProperties": { "trackingGranularity": "Per-item or per-batch", "scanMethod": "Mobile phone camera / QR scanner", "offlineCapable": "Yes \u2014 scan and sync when connected" } }, "nfc-tags": { "technologies": [ "NFC tag provisioning", "NFC reader integration", "Item-level tracking ledger" ], "technologyProperties": { "trackingGranularity": "Per-item", "scanMethod": "NFC-enabled device", "offlineCapable": "Yes \u2014 NFC works offline" } }, "barcode": { "technologies": [ "Barcode generation service", "QR/barcode scanning app", "Batch tracking ledger" ], "technologyProperties": { "trackingGranularity": "Per-batch", "scanMethod": "Barcode scanner / mobile camera", "offlineCapable": "Yes \u2014 scan and sync" } }, "mixed": { "technologies": [ "QR code generation service", "Barcode generation service", "QR/barcode scanning app", "Multi-level tracking ledger" ], "technologyProperties": { "trackingGranularity": "Mixed \u2014 item-level for high-value, batch for bulk", "scanMethod": "Mobile phone camera / scanner", "offlineCapable": "Yes" } } }, "prefillFrom": null, "briefSection": "Item tracking", "text": "How will physical items be tracked and scanned in the field?", "ngoText": "How will physical items be tracked and scanned in the field?" }, { "id": "audit-mechanism-approach", "type": "select", "options": [ { "label": "Automatic checks that flag problems as they happen", "value": "automated-realtime" }, { "label": "Regular scheduled reviews with tamper-proof records", "value": "periodic-batch" }, { "label": "Ability to check any record at any time with proof it has not been altered", "value": "on-demand" }, { "label": "External auditors can log in and review records independently", "value": "third-party" } ], "propertyMapping": { "automated-realtime": { "technologies": [ "Real-time audit mechanism", "Automated anomaly detection", "Audit alert service" ], "technologyProperties": { "auditFrequency": "Continuous / real-time", "auditAccess": "System-generated alerts", "complianceReporting": "Automated" } }, "periodic-batch": { "technologies": [ "Periodic audit mechanism", "Batch verification engine", "Audit report generator" ], "technologyProperties": { "auditFrequency": "Scheduled (daily/weekly/monthly)", "auditAccess": "Generated audit reports", "complianceReporting": "Scheduled" } }, "on-demand": { "technologies": [ "On-demand audit mechanism", "Audit query interface", "Record verification service" ], "technologyProperties": { "auditFrequency": "On-demand", "auditAccess": "Query-based", "complianceReporting": "On request" } }, "third-party": { "technologies": [ "Third-party audit mechanism", "Auditor access portal", "Audit evidence export" ], "technologyProperties": { "auditFrequency": "As required by auditor", "auditAccess": "Dedicated portal with read-only access", "complianceReporting": "Auditor-directed" } } }, "prefillFrom": null, "briefSection": "Audit and verification", "text": "Who needs to verify that actions happened correctly, and how easily should they be able to check?", "ngoText": "How should auditing and verification work for this solution?" } ], "complexityFactors": { "relationships": 1, "operationalChange": 2, "dataCompliance": 1 }, "suggestedCriteria": [ { "id": "SC-ASSET-REGISTER", "name": "Comprehensive Asset Register & Tagging", "description": "The system maintains a complete asset register with unique identification for every tracked item. A reliable asset register is foundational. Without unique tagging and a complete register, lifecycle tracking is impossible.", "weight": 0.25, "ratingGuide": { "5": "Comprehensive asset register with unique IDs (QR, RFID, or barcode). Supports hierarchical assets (vehicle with components). Photo documentation. Custodian assignment. Location tracking. Bulk import from existing registers. Configurable asset categories and attributes.", "4": "Complete register with unique IDs and barcode/QR tagging. Photo support. Custodian tracking. Good category flexibility.", "3": "Asset register with manual ID assignment. Basic categorisation. Location recorded. No photo/barcode.", "2": "Spreadsheet-like register. No unique identification system. Basic fields only.", "1": "No structured asset register. Paper-based or ad hoc tracking." } }, { "id": "SC-MAINTENANCE-SCHED", "name": "Maintenance Scheduling & History", "description": "The system can schedule preventive maintenance, track maintenance history, and manage work orders. Unplanned equipment failures disrupt programmes. Preventive maintenance extends asset life and reduces downtime.", "weight": 0.25, "ratingGuide": { "5": "Automated maintenance scheduling based on time, usage, or condition triggers. Work order creation and tracking. Full maintenance history per asset. Cost tracking per maintenance event. Spare parts inventory linkage. Mobile work order completion.", "4": "Calendar-based maintenance scheduling. Work order system. Maintenance history. Cost recording. Mobile-friendly.", "3": "Manual maintenance reminders. Basic history recording. No work order system. Cost tracking at aggregate level.", "2": "Maintenance events recorded after the fact. No scheduling. No cost tracking.", "1": "No maintenance management features." } }, { "id": "SC-DEPRECIATION", "name": "Depreciation & Financial Reporting", "description": "The system calculates asset depreciation and generate financial reports. NGO assets must be properly depreciated for financial statements and donor reporting.", "weight": 0.2, "ratingGuide": { "5": "Multiple depreciation methods (straight-line, declining balance, units of production). Automated monthly calculations. Integration with accounting systems. Donor-specific asset reports. Asset impairment recording. Disposal gain/loss calculation.", "4": "Standard depreciation methods. Automated calculations. Accounting export. Basic donor reporting.", "3": "Straight-line depreciation. Manual calculation triggers. Spreadsheet export for accounting.", "2": "Purchase cost recorded. No automated depreciation. Manual financial calculations.", "1": "No financial tracking. Asset values not managed." } }, { "id": "SC-DISPOSAL-MGMT", "name": "Disposal & Transfer Management", "description": "The system can manage end-of-life processes (disposal, sale, donation, or transfer to another entity). Proper disposal documentation prevents audit findings and ensures donor compliance.", "weight": 0.15, "ratingGuide": { "5": "Configurable disposal workflows (sale, donation, scrap, transfer). Approval chains. Disposal documentation with photos and justification. Environmental compliance for hazardous items. Proceeds tracking. Complete decommissioning audit trail.", "4": "Disposal workflow with approval. Documentation and justification required. Basic environmental flags. Audit trail.", "3": "Disposal recording with reason. Manual approval process. Basic documentation.", "2": "Assets marked as disposed. Minimal documentation. No approval workflow.", "1": "No disposal management. Assets removed from register with no documentation." } }, { "id": "SC-MULTI-OFFICE", "name": "Multi-Office & Field-Site Visibility", "description": "The system can provide visibility across all office and field locations. NGOs operate assets across many sites. HQ needs consolidated visibility while field offices need local control.", "weight": 0.15, "ratingGuide": { "5": "Multi-site deployment with consolidated global view. Inter-office transfer management. Location hierarchy (country \u2192 region \u2192 site). Role-based access per location. Offline field-site capability. Real-time asset location status.", "4": "Multi-site support with centralised reporting. Transfer tracking between sites. Location hierarchy. Online operation required.", "3": "Multi-site asset lists. Manual transfer recording. Basic location filtering. Centralised system.", "2": "Single-site focus with manual consolidation across sites. No transfer management.", "1": "Single-site system only. No multi-location support." } } ], "procurement": { "marketMaturity": "mature", "primaryMode": "off-the-shelf", "alternativeModes": [ "rfq" ], "reasoning": "Asset lifecycle tracking is mature SaaS market.", "exampleProductCategories": [ "asset-management-saas", "equipment-tracking-platform" ], "partnerChannels": [], "lastReviewed": "2026-05-01" } }, { "id": "UC-D-062", "name": "Fleet and vehicle management", "category": "D", "subcategory": "Asset Management", "description": "Keep one shared record of each vehicle's fuel use and repairs, so the people who drive vehicles and the people who maintain them work from the same figures.", "bCriteria": [ "B1", "B3" ], "requiredComponents": [ { "component": "tracking-platform", "description": "Vehicle tracking" }, { "component": "iot-sensors", "description": "GPS and telemetry sensors" }, { "component": "audit-mechanism", "description": "Vehicle usage audit trail" }, { "component": "inventory-integration", "description": "Fleet inventory" } ], "conditionalComponents": [ { "component": "smart-contracts", "condition": "If automated maintenance scheduling" } ], "crossCategoryDependencies": [], "p2TriggerConditions": { "description": "Activated when P2 shows fleet operations + fuel tracking + maintenance management", "rangeSignals": [ "vehicles >= 5+", "fuelCosts >= significant", "maintenanceTracking >= important" ] }, "contextFieldsTemplate": [ { "field": "vehicleCount", "source": "P0 fleet", "description": "Number of vehicles" }, { "field": "routes", "source": "P0 operations", "description": "Operating routes" }, { "field": "fuelTracking", "source": "P2 cost management", "description": "Fuel management priority" }, { "field": "maintenance", "source": "P2 fleet management", "description": "Maintenance needs" } ], "implementationComplexity": "medium", "examples": { "note": "Fleet management systems", "references": [ { "name": "UNHCR Fleet Management", "url": "https://www.unhcr.org/logistics/fleet-management", "solved": "Managed 1000+ vehicle fleet across 50+ countries" }, { "name": "Oxfam Fleet Operations", "url": "https://www.oxfam.org/en/corporate-information", "solved": "Implemented GPS and fuel tracking for NGO fleet" } ] }, "solutionQuestions": [ { "id": "fleet-size-scale", "type": "select", "options": [ { "label": "Small fleet (1-5 vehicles)", "value": "small-fleet" }, { "label": "Medium fleet (6-30 vehicles)", "value": "medium-fleet" }, { "label": "Large fleet (30+ vehicles)", "value": "large-fleet" } ], "propertyMapping": { "small-fleet": { "technologies": [ "Basic vehicle register", "Simple log system" ], "technologyProperties": { "systemComplexity": "minimal", "automationLevel": "none", "staffingNeeds": "part-time", "investmentRequired": "low" } }, "medium-fleet": { "technologies": [ "Fleet management platform", "Vehicle tracking system" ], "technologyProperties": { "systemComplexity": "moderate", "automationLevel": "semi-automated", "staffingNeeds": "dedicated-staff", "investmentRequired": "moderate" } }, "large-fleet": { "technologies": [ "Enterprise fleet management system", "Advanced analytics platform" ], "technologyProperties": { "systemComplexity": "advanced", "automationLevel": "fully-automated", "staffingNeeds": "specialized-team", "investmentRequired": "high" } } }, "prefillFrom": null, "briefSection": "Inventory management", "text": "What is the size of your fleet?", "ngoText": "What is the size of your fleet?" }, { "id": "vehicle-tracking-requirements", "type": "select", "options": [ { "label": "GPS location tracking only", "value": "gps-only" }, { "label": "GPS plus fuel and maintenance data", "value": "gps-fuel-maintenance" }, { "label": "Comprehensive telematics (GPS, fuel, maintenance, driver behavior)", "value": "full-telematics" } ], "propertyMapping": { "gps-only": { "technologies": [ "GPS tracking system", "Location monitoring platform" ], "technologyProperties": { "dataCollected": "location-only", "sensorTypes": "gps", "updateFrequency": "periodic", "dataUseCase": "route-tracking" } }, "gps-fuel-maintenance": { "technologies": [ "GPS fleet telemetry platform", "Fuel monitoring system" ], "technologyProperties": { "dataCollected": "location-fuel-maintenance", "sensorTypes": "gps-obd", "updateFrequency": "regular", "dataUseCase": "efficiency-and-maintenance" } }, "full-telematics": { "technologies": [ "Comprehensive telematics platform", "Driver behavior monitoring system" ], "technologyProperties": { "dataCollected": "all-metrics", "sensorTypes": "gps-obd-accelerometer-camera", "updateFrequency": "real-time", "dataUseCase": "complete-fleet-optimization" } } }, "prefillFrom": null, "briefSection": "Sensor and IoT", "text": "What vehicle tracking data is required?", "ngoText": "What vehicle tracking data is required?" }, { "id": "driver-management-level", "type": "select", "options": [ { "label": "Basic driver registry and license tracking", "value": "basic-registry" }, { "label": "Driver performance monitoring and training", "value": "performance-monitoring" }, { "label": "Advanced driver assessment with behavior analytics", "value": "advanced-analytics" } ], "propertyMapping": { "basic-registry": { "technologies": [ "Driver registry system", "License verification" ], "technologyProperties": { "dataTracked": "name-license-status", "monitoringLevel": "compliance", "improvementPrograms": "none", "reportingFrequency": "annual" } }, "performance-monitoring": { "technologies": [ "Driver performance platform", "Training management system" ], "technologyProperties": { "dataTracked": "performance-metrics", "monitoringLevel": "continuous", "improvementPrograms": "training", "reportingFrequency": "monthly" } }, "advanced-analytics": { "technologies": [ "Advanced driver analytics platform", "Behavior analytics engine" ], "technologyProperties": { "dataTracked": "comprehensive-behavior", "monitoringLevel": "real-time", "improvementPrograms": "personalized", "reportingFrequency": "continuous" } } }, "prefillFrom": null, "briefSection": "Tracking and provenance", "text": "What level of driver management is required?", "ngoText": "What level of driver management is required?" }, { "id": "fleet-size", "type": "select", "options": [ { "label": "Under 20 vehicles", "value": "small" }, { "label": "20\u2013100 vehicles", "value": "medium" }, { "label": "100\u2013500 vehicles", "value": "large" }, { "label": "Over 500 vehicles", "value": "enterprise" } ], "propertyMapping": { "small": { "technologies": [ "Simple fleet tracker" ], "technologyProperties": { "sensorDensity": "Low", "dataVolume": "Low" } }, "medium": { "technologies": [ "Fleet management platform" ], "technologyProperties": { "sensorDensity": "Medium", "dataVolume": "Medium" } }, "large": { "technologies": [ "Enterprise fleet platform", "IoT gateway" ], "technologyProperties": { "sensorDensity": "High", "dataVolume": "High" } }, "enterprise": { "technologies": [ "Enterprise fleet platform", "IoT gateway", "Edge computing" ], "technologyProperties": { "sensorDensity": "High", "dataVolume": "Very high" } } }, "prefillFrom": null, "briefSection": "Infrastructure requirements", "text": "How many vehicles are in the fleet to be tracked?", "ngoText": "How many vehicles are in the fleet to be tracked?" }, { "id": "sq-UC-D-062-001", "type": "single-select", "options": [ { "value": "fuel-card-tracking", "label": "Fuel card tracking" }, { "value": "gps-geofence", "label": "GPS geofencing" }, { "value": "driver-id-match", "label": "Driver ID matching" }, { "value": "consumption-anomaly-detection", "label": "Consumption anomaly detection" }, { "value": "manual-log-only", "label": "Manual log only" } ], "propertyMapping": { "fuel-card-tracking": { "technologies": [ "fuel-card-integration", "transaction-tracking" ], "technologyProperties": {} }, "gps-geofence": { "technologies": [ "gps-system", "geofencing-rules" ], "technologyProperties": {} }, "driver-id-match": { "technologies": [ "driver-identification", "access-control" ], "technologyProperties": {} }, "consumption-anomaly-detection": { "technologies": [ "analytics-engine", "anomaly-detection" ], "technologyProperties": {} }, "manual-log-only": { "technologies": [ "paper-logging", "manual-tracking" ], "technologyProperties": {} } }, "briefSection": "operations", "text": "What fuel management and anti-theft measures do you currently have?", "ngoText": "What fuel management and anti-theft measures do you currently have?" }, { "id": "sq-UC-D-062-003", "type": "single-select", "options": [ { "value": "mileage-based", "label": "Mileage-based" }, { "value": "time-based", "label": "Time-based" }, { "value": "predictive-from-telematics", "label": "Predictive from telematics" }, { "value": "driver-reported", "label": "Driver-reported" }, { "value": "hybrid-mileage-and-condition", "label": "Hybrid mileage and condition" } ], "propertyMapping": { "mileage-based": { "technologies": [ "mileage-tracking", "interval-scheduling" ], "technologyProperties": {} }, "time-based": { "technologies": [ "calendar-scheduling", "time-intervals" ], "technologyProperties": {} }, "predictive-from-telematics": { "technologies": [ "telematics-analysis", "predictive-maintenance" ], "technologyProperties": {} }, "driver-reported": { "technologies": [ "driver-feedback", "issue-reporting" ], "technologyProperties": {} }, "hybrid-mileage-and-condition": { "technologies": [ "combined-monitoring", "condition-assessment" ], "technologyProperties": {} } }, "briefSection": "operations", "text": "What maintenance scheduling approach do you currently use?", "ngoText": "What maintenance scheduling approach do you currently use?" }, { "id": "iot-sensor-approach", "type": "select", "options": [ { "label": "GPS/location tracking devices", "value": "gps-location" }, { "label": "Environmental sensors (temperature, humidity, etc.)", "value": "environmental" }, { "label": "Smart meters (energy, water usage)", "value": "smart-meters" }, { "label": "Mobile phone-based data collection (photos, GPS, manual entry)", "value": "mobile-collection" } ], "propertyMapping": { "gps-location": { "technologies": [ "GPS tracking IoT devices", "IoT sensor data gateway", "Location verification oracle" ], "technologyProperties": { "sensorType": "GPS/GNSS trackers", "dataFrequency": "Configurable (real-time to daily)", "connectivity": "Cellular/satellite" } }, "environmental": { "technologies": [ "Environmental IoT sensors", "IoT sensor data gateway", "Threshold alert service" ], "technologyProperties": { "sensorType": "Temperature, humidity, air quality sensors", "dataFrequency": "Continuous with threshold alerts", "connectivity": "LoRaWAN/cellular" } }, "smart-meters": { "technologies": [ "Smart meter IoT integration", "IoT sensor data gateway", "Usage verification service" ], "technologyProperties": { "sensorType": "Smart meters (energy/water)", "dataFrequency": "Hourly/daily readings", "connectivity": "LoRaWAN/cellular/Wi-Fi" } }, "mobile-collection": { "technologies": [ "Mobile data collection app", "IoT sensor proxy layer", "Photo/GPS verification service" ], "technologyProperties": { "sensorType": "Smartphone (camera, GPS, manual entry)", "dataFrequency": "Event-driven (field visits)", "connectivity": "Offline-first with sync" } } }, "prefillFrom": null, "briefSection": "Data collection", "text": "What type of sensor or data collection devices will be used?", "ngoText": "What type of sensor or data collection devices will be used?" }, { "id": "audit-mechanism-approach", "type": "select", "options": [ { "label": "Automatic checks that flag problems as they happen", "value": "automated-realtime" }, { "label": "Regular scheduled reviews with tamper-proof records", "value": "periodic-batch" }, { "label": "Ability to check any record at any time with proof it has not been altered", "value": "on-demand" }, { "label": "External auditors can log in and review records independently", "value": "third-party" } ], "propertyMapping": { "automated-realtime": { "technologies": [ "Real-time audit mechanism", "Automated anomaly detection", "Audit alert service" ], "technologyProperties": { "auditFrequency": "Continuous / real-time", "auditAccess": "System-generated alerts", "complianceReporting": "Automated" } }, "periodic-batch": { "technologies": [ "Periodic audit mechanism", "Batch verification engine", "Audit report generator" ], "technologyProperties": { "auditFrequency": "Scheduled (daily/weekly/monthly)", "auditAccess": "Generated audit reports", "complianceReporting": "Scheduled" } }, "on-demand": { "technologies": [ "On-demand audit mechanism", "Audit query interface", "Record verification service" ], "technologyProperties": { "auditFrequency": "On-demand", "auditAccess": "Query-based", "complianceReporting": "On request" } }, "third-party": { "technologies": [ "Third-party audit mechanism", "Auditor access portal", "Audit evidence export" ], "technologyProperties": { "auditFrequency": "As required by auditor", "auditAccess": "Dedicated portal with read-only access", "complianceReporting": "Auditor-directed" } } }, "prefillFrom": null, "briefSection": "Audit and verification", "text": "Who needs to verify that actions happened correctly, and how easily should they be able to check?", "ngoText": "How should auditing and verification work for this solution?" } ], "complexityFactors": { "relationships": 1, "operationalChange": 2, "dataCompliance": 1 }, "suggestedCriteria": [ { "id": "SC-VEHICLE-TRACK", "name": "Real-Time Vehicle Tracking & Telematics", "description": "The system provides real-time GPS tracking and telematics data for the vehicle fleet. In humanitarian contexts, vehicle tracking also serves safety and security purposes. Knowing where vehicles are during security incidents saves lives.", "weight": 0.25, "ratingGuide": { "5": "Real-time GPS tracking with <1 min update frequency. Telematics data (speed, engine status, fuel level). Geofencing with alerts. Security panic button integration. Historical route replay. Works with low-bandwidth satellite tracking for remote areas.", "4": "Real-time GPS tracking. Basic telematics. Geofencing. Historical routes. Cellular-based tracking.", "3": "Periodic GPS updates (every 5-15 min). Location history. Basic speed monitoring. No geofencing.", "2": "Daily location logging. Manual odometer and fuel recording. No real-time tracking.", "1": "No vehicle tracking. Paper-based logbooks only." } }, { "id": "SC-FUEL-MGMT", "name": "Fuel Management & Fraud Prevention", "description": "The system can track fuel consumption, detect anomalies, and prevent fuel fraud. Fuel is one of the largest fleet costs for NGOs and one of the most common areas of fraud.", "weight": 0.25, "ratingGuide": { "5": "Automated fuel tracking via telematics (fuel level sensors). Consumption rate analysis per vehicle. Anomaly detection (sudden drops indicating siphoning, consumption exceeding norms). Fuel card integration. Refuelling verification with GPS/timestamp.", "4": "Fuel tracking with sensor data. Basic anomaly alerts. Fuel card integration. Consumption reporting.", "3": "Manual fuel entry with odometer verification. Consumption rate calculation. Basic variance flagging.", "2": "Fuel receipt recording. Monthly fuel reports. No anomaly detection.", "1": "No fuel management. Paper-based fuel logs." } }, { "id": "SC-FLEET-MAINT", "name": "Preventive Maintenance & Compliance", "description": "The system manages preventive maintenance schedules, track compliance, and reduce vehicle downtime. Fleet maintenance compliance is critical for safety and for meeting insurance/donor requirements.", "weight": 0.2, "ratingGuide": { "5": "Automated maintenance scheduling by mileage, time, and engine hours. Compliance dashboard showing overdue services. Work order system with mechanic assignment. Parts inventory management. Vehicle health scoring. Insurance and registration renewal tracking.", "4": "Mileage/time-based scheduling. Overdue alerts. Work orders. Basic parts tracking. Compliance reporting.", "3": "Calendar-based maintenance reminders. Manual work order process. Service history recording.", "2": "Maintenance logged after completion. No scheduling or reminders. Basic service history.", "1": "No maintenance management. Paper-based service records." } }, { "id": "SC-DRIVER-SAFETY", "name": "Driver Behaviour & Safety Monitoring", "description": "The system can monitor driver behaviour (speeding, harsh braking, after-hours use) and support safety management. Road accidents are a leading cause of humanitarian worker injury and death.", "weight": 0.15, "ratingGuide": { "5": "Real-time driver behaviour scoring (speed, acceleration, braking, cornering). After-hours and unauthorised use alerts. Driver ID via key fob or app. Safety incident reporting linked to telematics data. Driver training recommendations.", "4": "Speed monitoring and harsh event detection. After-hours alerts. Driver assignment tracking. Basic safety reporting.", "3": "Speed limit alerts. Basic driver assignment. Manual incident recording.", "2": "Periodic speed reports. No real-time monitoring. Manual driver logs.", "1": "No driver behaviour monitoring." } }, { "id": "SC-FLEET-TCO", "name": "Total Cost of Ownership & Reporting", "description": "The system calculates total cost of ownership per vehicle and generate fleet analytics. Understanding per-vehicle and per-kilometre costs helps NGOs optimise fleet size and make replace-vs-repair decisions.", "weight": 0.15, "ratingGuide": { "5": "Complete TCO tracking: fuel, maintenance, insurance, depreciation, tyres per vehicle. Cost-per-km analysis. Replace-vs-repair decision support. Fleet utilisation analytics. Donor-attributable cost reporting. Benchmarking across vehicle types.", "4": "Major cost categories tracked per vehicle. Cost-per-km reporting. Basic utilisation metrics. Donor cost allocation.", "3": "Fuel and maintenance costs per vehicle. Manual cost analysis. Aggregate fleet reporting.", "2": "Total fleet costs. No per-vehicle breakdown. Basic financial reporting.", "1": "No cost tracking. Financial data managed outside the fleet system." } } ], "procurement": { "marketMaturity": "mature", "primaryMode": "off-the-shelf", "alternativeModes": [ "rfq" ], "reasoning": "Fleet management is a mature SaaS market.", "exampleProductCategories": [ "fleet-management-saas", "vehicle-tracking-platform" ], "partnerChannels": [], "lastReviewed": "2026-05-01" } }, { "id": "UC-D-063", "name": "Last-mile delivery verification", "category": "D", "subcategory": "Delivery Verification", "description": "Confirm that goods reached the intended person, with proof that is hard to fake, rather than relying only on signed paper receipts.", "bCriteria": [ "B3", "B5" ], "requiredComponents": [ { "component": "last-mile-verification", "description": "Delivery confirmation system" }, { "component": "qr-barcode", "description": "Delivery documentation" }, { "component": "mobile-wallet", "description": "Mobile delivery proof" }, { "component": "audit-mechanism", "description": "Delivery audit trail" } ], "conditionalComponents": [ { "component": "biometric-capture", "condition": "If thumbprint delivery confirmation" }, { "component": "identity-verification", "condition": "For beneficiary verification" } ], "crossCategoryDependencies": [ "UC-B-024 for beneficiary identity verification" ], "p2TriggerConditions": { "description": "Activated when P2 shows distribution programmes + delivery verification needs + accountability", "rangeSignals": [ "distributions >= frequent", "beneficiaryVerification >= important", "fraudConcerns >= true" ] }, "contextFieldsTemplate": [ { "field": "beneficiaries", "source": "P2 programme scale", "description": "Deliveries per month" }, { "field": "locations", "source": "P0 operations + P4", "description": "Delivery locations" }, { "field": "verification", "source": "P2 M&E", "description": "Verification requirements" }, { "field": "fraud", "source": "P0 context", "description": "Fraud/diversion concerns" } ], "implementationComplexity": "medium", "examples": { "note": "Last-mile delivery verification in emergencies", "references": [ { "name": "WFP Last Mile Verification", "url": "https://www.wfp.org/innovation/delivering-impact", "solved": "Implemented biometric delivery verification for 100,000+ beneficiaries" }, { "name": "GiveDirectly Mobile Money Transfer", "url": "https://www.givedirectly.org/technology", "solved": "Used mobile verification for last-mile cash delivery verification" }, { "name": "Mercy Corps Delivery Tracking", "url": "https://www.mercycorps.org/research-resources/delivery-verification", "solved": "Developed delivery verification system for emergency response" } ] }, "solutionQuestions": [ { "id": "delivery-verification-method", "type": "select", "options": [ { "label": "Signature or thumbprint on receipt", "value": "signature-receipt" }, { "label": "QR code scanning by beneficiary", "value": "qr-scanning" }, { "label": "Biometric verification with photo", "value": "biometric-photo" } ], "propertyMapping": { "signature-receipt": { "technologies": [ "Digital signature platform", "Receipt documentation system" ], "technologyProperties": { "verificationAccuracy": "moderate", "fraudRisk": "moderate", "technicalComplexity": "low", "beneficiaryBarrier": "low" } }, "qr-scanning": { "technologies": [ "QR code platform", "Mobile scanning application" ], "technologyProperties": { "verificationAccuracy": "high", "fraudRisk": "low", "technicalComplexity": "moderate", "beneficiaryBarrier": "moderate" } }, "biometric-photo": { "technologies": [ "Biometric verification system", "Photo documentation platform" ], "technologyProperties": { "verificationAccuracy": "very-high", "fraudRisk": "very-low", "technicalComplexity": "high", "beneficiaryBarrier": "high" } } }, "prefillFrom": null, "briefSection": "Verification and authentication", "text": "Which verification method should be used for delivery?", "ngoText": "Which verification method should be used for delivery?" }, { "id": "beneficiary-id-system", "type": "select", "options": [ { "label": "Basic list with name and location", "value": "basic-list" }, { "label": "Digital registry with unique ID", "value": "digital-id" }, { "label": "Biometric registry with multi-modal data", "value": "biometric-registry" } ], "propertyMapping": { "basic-list": { "technologies": [ "Beneficiary list system", "Paper or spreadsheet registry" ], "technologyProperties": { "uniqueIdentifier": "none", "dataFields": "name-location-household", "updateFrequency": "static", "scalability": "limited" } }, "digital-id": { "technologies": [ "Digital beneficiary registry", "Unique ID generator" ], "technologyProperties": { "uniqueIdentifier": "sequential-or-random", "dataFields": "comprehensive", "updateFrequency": "periodic", "scalability": "good" } }, "biometric-registry": { "technologies": [ "Biometric registration system", "Multi-modal identity platform" ], "technologyProperties": { "uniqueIdentifier": "biometric-based", "dataFields": "comprehensive-biometric", "updateFrequency": "continuous", "scalability": "excellent" } } }, "prefillFrom": null, "briefSection": "Last-mile verification", "text": "How are beneficiaries identified and registered?", "ngoText": "How are beneficiaries identified and registered?" }, { "id": "delivery-scale-volume", "type": "select", "options": [ { "label": "Small scale (< 1000 deliveries/month)", "value": "small-scale" }, { "label": "Medium scale (1000-10000 deliveries/month)", "value": "medium-scale" }, { "label": "Large scale (10000+ deliveries/month)", "value": "large-scale" } ], "propertyMapping": { "small-scale": { "technologies": [ "Basic delivery log", "Simple tracking system" ], "technologyProperties": { "systemComplexity": "simple", "automationLevel": "minimal", "staffingNeeds": "part-time", "investmentRequired": "low" } }, "medium-scale": { "technologies": [ "Delivery management platform", "Mobile application" ], "technologyProperties": { "systemComplexity": "moderate", "automationLevel": "semi-automated", "staffingNeeds": "dedicated-staff", "investmentRequired": "moderate" } }, "large-scale": { "technologies": [ "Enterprise delivery platform", "Advanced analytics system" ], "technologyProperties": { "systemComplexity": "advanced", "automationLevel": "fully-automated", "staffingNeeds": "specialized-team", "investmentRequired": "high" } } }, "prefillFrom": null, "briefSection": "Infrastructure requirements", "text": "What is the expected delivery volume?", "ngoText": "What is the expected delivery volume?" }, { "id": "fraud-prevention-mechanism", "type": "select", "options": [ { "label": "Documentation and random spot checks", "value": "spot-checks" }, { "label": "Digital verification with supervisor review", "value": "digital-review" }, { "label": "Real-time monitoring with digital ledger confirmation", "value": "blockchain-monitoring" } ], "propertyMapping": { "spot-checks": { "technologies": [ "Audit sampling system", "Verification checklist" ], "technologyProperties": { "detectionRate": "moderate", "deterrentEffect": "moderate", "costPerVerification": "low", "administrativeOverhead": "moderate" } }, "digital-review": { "technologies": [ "Digital verification platform", "Supervisory review system" ], "technologyProperties": { "detectionRate": "high", "deterrentEffect": "high", "costPerVerification": "moderate", "administrativeOverhead": "low" } }, "blockchain-monitoring": { "technologies": [ "Blockchain confirmation system", "Real-time audit platform" ], "technologyProperties": { "detectionRate": "very-high", "deterrentEffect": "very-high", "costPerVerification": "high", "administrativeOverhead": "minimal" } } }, "prefillFrom": null, "briefSection": "Quality assurance", "text": "What approach would you need for preventing and detecting supply chain fraud?", "ngoText": "What approach would you need for preventing and detecting supply chain fraud?" }, { "id": "last-mile-stakeholders", "type": "select", "options": [ { "label": "Internal only (1\u20132 teams)", "value": "internal" }, { "label": "Internal + 1\u20133 external partners", "value": "few-external" }, { "label": "Multiple external stakeholders (4\u201310)", "value": "multi-external" }, { "label": "Ecosystem-wide (donors, partners, beneficiaries, regulators)", "value": "ecosystem" } ], "propertyMapping": { "internal": { "technologies": [ "Private ledger" ], "technologyProperties": { "accessControl": "Simple role-based", "networkType": "Private" } }, "few-external": { "technologies": [ "Permissioned network", "Selective data sharing" ], "technologyProperties": { "accessControl": "Partner-level permissions", "networkType": "Consortium" } }, "multi-external": { "technologies": [ "Permissioned network", "Multi-party access layer" ], "technologyProperties": { "accessControl": "Granular role-based", "networkType": "Consortium" } }, "ecosystem": { "technologies": [ "Permissioned public network", "Data marketplace" ], "technologyProperties": { "accessControl": "Multi-tier with public layer", "networkType": "Hybrid public-private" } } }, "prefillFrom": null, "briefSection": "Governance and access", "text": "How many distinct parties need visibility into the last-mile delivery data?", "ngoText": "How many distinct parties need visibility into the last-mile delivery data?" }, { "id": "item-tracking-method", "type": "select", "options": [ { "label": "QR codes printed on items or packaging", "value": "qr-codes" }, { "label": "NFC tags embedded in items", "value": "nfc-tags" }, { "label": "Barcode labels with batch scanning", "value": "barcode" }, { "label": "Mixed: QR for high-value items, barcode for bulk", "value": "mixed" } ], "propertyMapping": { "qr-codes": { "technologies": [ "QR code generation service", "QR/barcode scanning app", "Item-level tracking ledger" ], "technologyProperties": { "trackingGranularity": "Per-item or per-batch", "scanMethod": "Mobile phone camera / QR scanner", "offlineCapable": "Yes \u2014 scan and sync when connected" } }, "nfc-tags": { "technologies": [ "NFC tag provisioning", "NFC reader integration", "Item-level tracking ledger" ], "technologyProperties": { "trackingGranularity": "Per-item", "scanMethod": "NFC-enabled device", "offlineCapable": "Yes \u2014 NFC works offline" } }, "barcode": { "technologies": [ "Barcode generation service", "QR/barcode scanning app", "Batch tracking ledger" ], "technologyProperties": { "trackingGranularity": "Per-batch", "scanMethod": "Barcode scanner / mobile camera", "offlineCapable": "Yes \u2014 scan and sync" } }, "mixed": { "technologies": [ "QR code generation service", "Barcode generation service", "QR/barcode scanning app", "Multi-level tracking ledger" ], "technologyProperties": { "trackingGranularity": "Mixed \u2014 item-level for high-value, batch for bulk", "scanMethod": "Mobile phone camera / scanner", "offlineCapable": "Yes" } } }, "prefillFrom": null, "briefSection": "Item tracking", "text": "How will physical items be tracked and scanned in the field?", "ngoText": "How will physical items be tracked and scanned in the field?" } ], "complexityFactors": { "relationships": 3, "operationalChange": 3, "dataCompliance": 2 }, "suggestedCriteria": [ { "id": "SC-RECEIPT-PROOF", "name": "Proof of Delivery to Beneficiary", "description": "This measures how strongly the system proves that items were delivered to the intended beneficiary. Last-mile delivery is the highest-risk point for diversion. Proof must be strong enough to withstand audit scrutiny.", "weight": 0.3, "ratingGuide": { "5": "Multi-factor delivery proof: beneficiary identity verification (biometric, ID card, QR token) + GPS location stamp + timestamp + item verification (scan delivered items) + digital signature. Anti-replay protections. Offline-capable with tamper-evident sync.", "4": "Identity verification + GPS + timestamp + digital signature. Offline capable. Anti-fraud protections.", "3": "Digital signature or token verification + GPS. Requires connectivity for verification.", "2": "Paper-based sign-off captured digitally after the fact. GPS from delivery agent only.", "1": "No delivery verification beyond dispatch records." } }, { "id": "SC-BENEFICIARY-LIST", "name": "Distribution List Management & Reconciliation", "description": "The system can manage beneficiary distribution lists, handle walk-ins, and reconcile planned vs. actual distributions. Distribution list integrity is the foundation of accountable delivery.", "weight": 0.25, "ratingGuide": { "5": "Pre-loaded distribution lists synced from beneficiary registration. Real-time reconciliation during distribution. Walk-in registration workflow. Undistributed beneficiary follow-up lists. Cross-distribution duplicate detection. Supports split distributions (partial collection).", "4": "Distribution list management. Real-time reconciliation. Walk-in handling. Duplicate detection. Basic follow-up lists.", "3": "Pre-loaded lists with post-distribution reconciliation. Manual walk-in recording. Basic duplicate checking.", "2": "Paper lists digitised after distribution. Manual reconciliation. No walk-in or duplicate management.", "1": "No distribution list management. Open distribution with manual head counts." } }, { "id": "SC-OFFLINE-DISTRIBUTE", "name": "Offline Distribution Capability", "description": "The full distribution workflow can operate without internet connectivity. Last-mile distribution points are frequently in areas with zero connectivity. The system must work fully offline.", "weight": 0.2, "ratingGuide": { "5": "Complete offline operation: beneficiary lookup, identity verification, item scanning, receipt capture, GPS logging. All data encrypted locally. Automatic conflict-free sync when connectivity restored. Supports multi-device offline distribution at same site.", "4": "Full offline distribution workflow. Encrypted local storage. Auto-sync. Single-device per site offline.", "3": "Basic offline distribution recording. Manual sync required. Some features unavailable offline.", "2": "Can record deliveries offline but cannot verify beneficiary identity. Limited offline features.", "1": "Requires internet connectivity. Cannot operate offline." } }, { "id": "SC-EXCEPTION-MGMT", "name": "Exception & Complaint Management", "description": "The system handles distribution exceptions (refused items, damaged goods, proxy collection, complaints). Real distributions are messy; the system must accommodate edge cases without breaking accountability.", "weight": 0.15, "ratingGuide": { "5": "Structured exception workflows: refusal with reason, damage documentation with photos, authorised proxy collection with linked identity, beneficiary complaint recording with investigation tracking. Exception analytics and pattern detection.", "4": "Exception recording with categories. Proxy collection support. Complaint logging. Basic reporting.", "3": "Free-text exception notes. Manual proxy authorisation. Complaint recording without tracking.", "2": "Exceptions noted in comments. No structured handling. No complaint system.", "1": "No exception handling. Deviations from plan not captured." } }, { "id": "SC-REALTIME-DASHBOARD", "name": "Real-Time Distribution Monitoring Dashboard", "description": "Supervisors and programme managers can monitor distribution progress in real time. Knowing distribution status across multiple sites during a distribution day enables rapid response to bottlenecks or issues.", "weight": 0.1, "ratingGuide": { "5": "Live dashboard showing per-site distribution progress. Map-based view. Alert on stalled distributions. Comparative analytics (planned vs. actual vs. time). Multi-level views (site, region, programme). Mobile-accessible for field supervisors.", "4": "Dashboard with periodic updates. Site-level progress. Basic alerts. Desktop and mobile views.", "3": "Aggregate progress reporting with hourly updates. Site-level summaries. Desktop only.", "2": "End-of-day distribution reports. No real-time visibility.", "1": "No distribution monitoring. Data available only after full reconciliation." } } ], "procurement": { "marketMaturity": "emerging", "primaryMode": "integrator-led", "alternativeModes": [ "rfq" ], "reasoning": "Last-mile delivery verification often combines product + integration.", "exampleProductCategories": [ "last-mile-delivery-platform", "supply-chain-saas" ], "partnerChannels": [], "lastReviewed": "2026-05-01" } }, { "id": "UC-D-064", "name": "Local procurement verification", "category": "D", "subcategory": "Procurement", "description": "Record what was bought locally and from whom, so each purchase can be followed from vendor selection to the final recipient.", "bCriteria": [ "B1", "B3" ], "requiredComponents": [ { "component": "tracking-platform", "description": "Procurement tracking" }, { "component": "qr-barcode", "description": "Vendor/product identification" }, { "component": "audit-mechanism", "description": "Procurement audit trail" }, { "component": "provenance-verification", "description": "Local source verification" } ], "conditionalComponents": [ { "component": "smart-contracts", "condition": "If automated vendor approval" } ], "crossCategoryDependencies": [ "UC-A-011 if transparency audits needed" ], "p2TriggerConditions": { "description": "Activated when P2 shows local procurement focus + transparency needs + vendor vetting", "rangeSignals": [ "localProcurement >= true", "transparency >= important", "vendorCount >= 10+" ] }, "contextFieldsTemplate": [ { "field": "vendors", "source": "P2 supplier network", "description": "Local vendors" }, { "field": "procurementVolume", "source": "P2 spend", "description": "Annual local spend" }, { "field": "products", "source": "P2 items procured", "description": "Products procured" }, { "field": "transparencyGoal", "source": "P2 development impact", "description": "Local economic development" } ], "implementationComplexity": "medium", "examples": { "note": "Local procurement and market support", "references": [ { "name": "UNDP Local Procurement", "url": "https://www.undp.org/business-services/procuring-locally", "solved": "Established local procurement standards for UN programmes" }, { "name": "Oxfam Fair Trade Procurement", "url": "https://www.oxfam.org.uk/what-we-do/fair-pay", "solved": "Implemented fair price verification system for local suppliers" } ] }, "solutionQuestions": [ { "id": "vendor-verification-depth", "type": "select", "options": [ { "label": "Basic registration and business verification", "value": "basic-verification" }, { "label": "Financial and compliance screening", "value": "compliance-screening" }, { "label": "Comprehensive due diligence with site visits", "value": "comprehensive-due-diligence" } ], "propertyMapping": { "basic-verification": { "technologies": [ "Vendor registration system", "Business verification platform" ], "technologyProperties": { "verificationProcess": "document-based", "durationDays": "3-5", "costPerVendor": "low", "reliabilityScore": "moderate" } }, "compliance-screening": { "technologies": [ "Compliance screening platform", "Financial assessment system" ], "technologyProperties": { "verificationProcess": "multi-step", "durationDays": "7-14", "costPerVendor": "moderate", "reliabilityScore": "high" } }, "comprehensive-due-diligence": { "technologies": [ "Due diligence platform", "Site assessment system" ], "technologyProperties": { "verificationProcess": "comprehensive", "durationDays": "14-30", "costPerVendor": "high", "reliabilityScore": "very-high" } } }, "prefillFrom": null, "briefSection": "Verification and authentication", "text": "How deep should vendor verification be?", "ngoText": "How deep should vendor verification be?" }, { "id": "local-sourcing-requirement", "type": "select", "options": [ { "label": "No specific requirement (open market)", "value": "open-market" }, { "label": "Preference for local vendors (20-50%)", "value": "preference" }, { "label": "Mandate for local sourcing (70-100%)", "value": "mandate" } ], "propertyMapping": { "open-market": { "technologies": [ "Open procurement platform", "Vendor comparison system" ], "technologyProperties": { "vendorPool": "global", "priceOptimisation": "maximum", "localEconomicImpact": "minimal", "complexity": "simple" } }, "preference": { "technologies": [ "Preferential procurement platform", "Local vendor incentive system" ], "technologyProperties": { "vendorPool": "mixed", "priceOptimisation": "moderate", "localEconomicImpact": "good", "complexity": "moderate" } }, "mandate": { "technologies": [ "Local procurement mandate system", "Community vendor platform" ], "technologyProperties": { "vendorPool": "local-only", "priceOptimisation": "limited", "localEconomicImpact": "high", "complexity": "high" } } }, "prefillFrom": null, "briefSection": "Tracking and provenance", "text": "What local sourcing requirement should be enforced?", "ngoText": "What local sourcing requirement should be enforced?" }, { "id": "price-transparency-mechanism", "type": "select", "options": [ { "label": "Negotiated pricing per contract", "value": "negotiated" }, { "label": "Market rate comparison and approval", "value": "market-comparison" }, { "label": "Public price list with cost-plus limitation", "value": "public-pricing" } ], "propertyMapping": { "negotiated": { "technologies": [ "Contract management system", "Negotiation tracking" ], "technologyProperties": { "priceVisibility": "internal", "complianceCheck": "procurement-manager", "fraudRisk": "moderate", "administrativeOverhead": "low" } }, "market-comparison": { "technologies": [ "Market rate comparison platform", "Price benchmark system" ], "technologyProperties": { "priceVisibility": "comparative", "complianceCheck": "automated", "fraudRisk": "low", "administrativeOverhead": "moderate" } }, "public-pricing": { "technologies": [ "Public price list platform", "Cost control system" ], "technologyProperties": { "priceVisibility": "public", "complianceCheck": "automated", "fraudRisk": "very-low", "administrativeOverhead": "high" } } }, "prefillFrom": null, "briefSection": "Reporting and audit", "text": "What is your current approach to price transparency in your supply chain?", "ngoText": "What is your current approach to price transparency in your supply chain?", "hidden": true }, { "id": "local-proc-volume", "type": "select", "options": [ { "label": "Under 1,000 items", "value": "small" }, { "label": "1,000\u201310,000 items", "value": "medium" }, { "label": "10,000\u2013100,000 items", "value": "large" }, { "label": "Over 100,000 items", "value": "enterprise" } ], "propertyMapping": { "small": { "technologies": [ "Simple ledger" ], "technologyProperties": { "scalability": "Standard", "throughput": "Low" } }, "medium": { "technologies": [ "Standard tracking platform" ], "technologyProperties": { "scalability": "Standard", "throughput": "Medium" } }, "large": { "technologies": [ "High-throughput tracking platform", "Batch processing" ], "technologyProperties": { "scalability": "High", "throughput": "High \u2014 batch optimised" } }, "enterprise": { "technologies": [ "Enterprise tracking platform", "Layer 2 scaling" ], "technologyProperties": { "scalability": "Enterprise", "throughput": "Very high \u2014 L2 required" } } }, "prefillFrom": null, "briefSection": "Infrastructure requirements", "text": "What is the monthly volume of local procurement transactions you need to track?", "ngoText": "What is the monthly volume of local procurement transactions you need to track?" }, { "id": "local-proc-stakeholders", "type": "select", "options": [ { "label": "Internal only (1\u20132 teams)", "value": "internal" }, { "label": "Internal + 1\u20133 external partners", "value": "few-external" }, { "label": "Multiple external stakeholders (4\u201310)", "value": "multi-external" }, { "label": "Ecosystem-wide (donors, partners, beneficiaries, regulators)", "value": "ecosystem" } ], "propertyMapping": { "internal": { "technologies": [ "Private ledger" ], "technologyProperties": { "accessControl": "Simple role-based", "networkType": "Private" } }, "few-external": { "technologies": [ "Permissioned network", "Selective data sharing" ], "technologyProperties": { "accessControl": "Partner-level permissions", "networkType": "Consortium" } }, "multi-external": { "technologies": [ "Permissioned network", "Multi-party access layer" ], "technologyProperties": { "accessControl": "Granular role-based", "networkType": "Consortium" } }, "ecosystem": { "technologies": [ "Permissioned public network", "Data marketplace" ], "technologyProperties": { "accessControl": "Multi-tier with public layer", "networkType": "Hybrid public-private" } } }, "prefillFrom": null, "briefSection": "Governance and access", "text": "How many distinct parties need visibility into the procurement data?", "ngoText": "How many distinct parties need visibility into the procurement data?" }, { "id": "item-tracking-method", "type": "select", "options": [ { "label": "QR codes printed on items or packaging", "value": "qr-codes" }, { "label": "NFC tags embedded in items", "value": "nfc-tags" }, { "label": "Barcode labels with batch scanning", "value": "barcode" }, { "label": "Mixed: QR for high-value items, barcode for bulk", "value": "mixed" } ], "propertyMapping": { "qr-codes": { "technologies": [ "QR code generation service", "QR/barcode scanning app", "Item-level tracking ledger" ], "technologyProperties": { "trackingGranularity": "Per-item or per-batch", "scanMethod": "Mobile phone camera / QR scanner", "offlineCapable": "Yes \u2014 scan and sync when connected" } }, "nfc-tags": { "technologies": [ "NFC tag provisioning", "NFC reader integration", "Item-level tracking ledger" ], "technologyProperties": { "trackingGranularity": "Per-item", "scanMethod": "NFC-enabled device", "offlineCapable": "Yes \u2014 NFC works offline" } }, "barcode": { "technologies": [ "Barcode generation service", "QR/barcode scanning app", "Batch tracking ledger" ], "technologyProperties": { "trackingGranularity": "Per-batch", "scanMethod": "Barcode scanner / mobile camera", "offlineCapable": "Yes \u2014 scan and sync" } }, "mixed": { "technologies": [ "QR code generation service", "Barcode generation service", "QR/barcode scanning app", "Multi-level tracking ledger" ], "technologyProperties": { "trackingGranularity": "Mixed \u2014 item-level for high-value, batch for bulk", "scanMethod": "Mobile phone camera / scanner", "offlineCapable": "Yes" } } }, "prefillFrom": null, "briefSection": "Item tracking", "text": "How will physical items be tracked and scanned in the field?", "ngoText": "How will physical items be tracked and scanned in the field?" }, { "id": "audit-mechanism-approach", "type": "select", "options": [ { "label": "Automatic checks that flag problems as they happen", "value": "automated-realtime" }, { "label": "Regular scheduled reviews with tamper-proof records", "value": "periodic-batch" }, { "label": "Ability to check any record at any time with proof it has not been altered", "value": "on-demand" }, { "label": "External auditors can log in and review records independently", "value": "third-party" } ], "propertyMapping": { "automated-realtime": { "technologies": [ "Real-time audit mechanism", "Automated anomaly detection", "Audit alert service" ], "technologyProperties": { "auditFrequency": "Continuous / real-time", "auditAccess": "System-generated alerts", "complianceReporting": "Automated" } }, "periodic-batch": { "technologies": [ "Periodic audit mechanism", "Batch verification engine", "Audit report generator" ], "technologyProperties": { "auditFrequency": "Scheduled (daily/weekly/monthly)", "auditAccess": "Generated audit reports", "complianceReporting": "Scheduled" } }, "on-demand": { "technologies": [ "On-demand audit mechanism", "Audit query interface", "Record verification service" ], "technologyProperties": { "auditFrequency": "On-demand", "auditAccess": "Query-based", "complianceReporting": "On request" } }, "third-party": { "technologies": [ "Third-party audit mechanism", "Auditor access portal", "Audit evidence export" ], "technologyProperties": { "auditFrequency": "As required by auditor", "auditAccess": "Dedicated portal with read-only access", "complianceReporting": "Auditor-directed" } } }, "prefillFrom": null, "briefSection": "Audit and verification", "text": "Who needs to verify that actions happened correctly, and how easily should they be able to check?", "ngoText": "How should auditing and verification work for this solution?" } ], "complexityFactors": { "relationships": 2, "operationalChange": 2, "dataCompliance": 1 }, "suggestedCriteria": [ { "id": "SC-VENDOR-VERIFY", "name": "Vendor Identity & Eligibility Verification", "description": "The system can verify local vendor identity, business registration, and eligibility (not on sanctions lists, meets minimum quality standards). Local procurement fraud often involves fictitious or ineligible vendors.", "weight": 0.3, "ratingGuide": { "5": "Vendor registration with document verification (business licence, tax ID). Automated sanctions and debarment list screening. Conflict-of-interest checks. Vendor performance history. Digital identity verification for sole traders. Multi-source verification.", "4": "Vendor registration with document upload. Sanctions screening integration. Basic conflict-of-interest flag. Performance tracking.", "3": "Vendor registration with manual document review. Manual sanctions checking. Basic vendor records.", "2": "Vendor name and contact recorded. No verification of identity or eligibility.", "1": "No vendor verification. Procurement based on field officer selection with no system checks." } }, { "id": "SC-PRICE-BENCHMARK", "name": "Price Benchmarking & Market Analysis", "description": "The system supports price benchmarking against local market rates. Overpayment in local procurement (whether through collusion, inflation, or ignorance of local prices) is a major audit finding.", "weight": 0.25, "ratingGuide": { "5": "Market price database with regular updates. Automated price comparison against benchmarks. Variance alerts when quotes exceed market rates. Historical price trend analysis. Supports market assessment survey data integration.", "4": "Price benchmarking with manual market data entry. Variance alerts. Historical pricing. Basic trend analysis.", "3": "Price comparison across quotes received. No external market benchmark. Historical records.", "2": "Prices recorded. Manual comparison only. No benchmarking.", "1": "No price analysis capability." } }, { "id": "SC-PROCUREMENT-TRAIL", "name": "Procurement Process Audit Trail", "description": "The system captures the complete procurement process, from requisition through quotation, evaluation, award, delivery, and payment. An unbroken audit trail is the primary defence against procurement fraud.", "weight": 0.2, "ratingGuide": { "5": "End-to-end digital trail: requisition \u2192 approval \u2192 RFQ/tender \u2192 bid receipt \u2192 evaluation \u2192 award \u2192 PO \u2192 delivery verification \u2192 goods receipt \u2192 invoice matching \u2192 payment authorisation. All steps timestamped with user attribution. Document attachments at every stage.", "4": "Major procurement steps captured digitally. Approval workflow. Document attachments. Good audit trail.", "3": "Key steps recorded (PO, receipt, payment). Some manual processes between. Basic audit trail.", "2": "PO and payment recorded. Limited process documentation. Gaps in audit trail.", "1": "Minimal procurement records. Paper-based process." } }, { "id": "SC-LOCAL-ECONOMY", "name": "Local Economy Impact Tracking", "description": "The system can track and report on the impact of local procurement on the local economy. Donors increasingly want evidence that local procurement supports economic development rather than distorting markets.", "weight": 0.15, "ratingGuide": { "5": "Tracks procurement spend by vendor size, location, gender of business owner, sector. Economic impact analytics (jobs supported, local multiplier estimates). Donor impact reports. Integration with programme outcome data.", "4": "Vendor demographic tracking (size, location, ownership). Spend analysis by category. Basic impact reporting.", "3": "Local vs. non-local spend tracking. Basic vendor categorisation. Standard reporting.", "2": "Total procurement spend recorded. No vendor analysis. Manual impact assessment.", "1": "No local economy tracking." } }, { "id": "SC-QUALITY-RECEIPT", "name": "Quality Verification at Receipt", "description": "The system supports goods receipt inspection to verify that delivered items match procurement specifications. Receiving sub-standard goods without proper inspection wastes procurement effort and harms beneficiaries.", "weight": 0.1, "ratingGuide": { "5": "Structured receipt inspection workflow linked to PO specifications. Photo evidence capture. Quality grading with accept/reject/partial-accept. Automated supplier quality scoring based on receipt results. Non-conformance reporting workflow.", "4": "Receipt inspection checklist linked to PO. Photo evidence. Accept/reject with reasons. Supplier quality tracking.", "3": "Receipt confirmation with basic inspection notes. Manual PO comparison. Simple accept/reject.", "2": "Quantity confirmation only. No quality inspection workflow.", "1": "No receipt inspection. Goods accepted without verification." } } ], "procurement": { "marketMaturity": "emerging", "primaryMode": "rfq", "alternativeModes": [ "off-the-shelf" ], "reasoning": "Local procurement verification overlaps with procurement transparency tools.", "exampleProductCategories": [ "local-procurement-platform", "procurement-saas" ], "partnerChannels": [], "lastReviewed": "2026-05-01" } }, { "id": "UC-D-065", "name": "Warehouse inventory management", "category": "D", "subcategory": "Inventory Management", "description": "Keep stock records across several warehouses in step with each other, so counts agree without manual checking.", "bCriteria": [ "B1", "B3" ], "requiredComponents": [ { "component": "inventory-integration", "description": "Warehouse management system" }, { "component": "tracking-platform", "description": "Stock tracking" }, { "component": "qr-barcode", "description": "Item identification" }, { "component": "audit-mechanism", "description": "Stock movement audit" } ], "conditionalComponents": [ { "component": "smart-contracts", "condition": "If automated stock replenishment" }, { "component": "iot-sensors", "condition": "If location/quantity sensors" } ], "crossCategoryDependencies": [], "p2TriggerConditions": { "description": "Activated when P2 shows warehouse operations + inventory burden + stock accuracy concerns", "rangeSignals": [ "warehouseCount >= 1+", "skuCount >= 100+", "stockAccuracy <= concern" ] }, "contextFieldsTemplate": [ { "field": "warehouseCount", "source": "P0 logistics", "description": "Number of warehouses" }, { "field": "itemTypes", "source": "P2 inventory", "description": "Types of items stored" }, { "field": "volume", "source": "P2 logistics", "description": "Average inventory volume" }, { "field": "systemCurrent", "source": "P0 Q13", "description": "Current warehouse system" } ], "implementationComplexity": "medium", "examples": { "note": "Supply chain management systems", "references": [ { "name": "UNHCR Warehouse Operations", "url": "https://www.unhcr.org/supply-operations", "solved": "Managed warehouse inventory across 100+ locations globally" }, { "name": "World Vision Warehouse Systems", "url": "https://www.worldvision.org/our-work/supply-chain", "solved": "Implemented WMS for multi-warehouse network management" } ] }, "solutionQuestions": [ { "id": "warehouse-facility-count", "type": "select", "options": [ { "label": "Single warehouse", "value": "single-warehouse" }, { "label": "Multi-warehouse network (2-5 facilities)", "value": "multi-warehouse" }, { "label": "Complex distribution network (5+ facilities)", "value": "complex-network" } ], "propertyMapping": { "single-warehouse": { "technologies": [ "Single warehouse management system", "Inventory control" ], "technologyProperties": { "systemComplexity": "simple", "coordinationOverhead": "none", "scalability": "limited", "investmentRequired": "low" } }, "multi-warehouse": { "technologies": [ "Multi-warehouse management platform", "Inventory synchronisation" ], "technologyProperties": { "systemComplexity": "moderate", "coordinationOverhead": "moderate", "scalability": "good", "investmentRequired": "moderate" } }, "complex-network": { "technologies": [ "Enterprise warehouse network system", "Distributed inventory platform" ], "technologyProperties": { "systemComplexity": "advanced", "coordinationOverhead": "high", "scalability": "excellent", "investmentRequired": "high" } } }, "prefillFrom": null, "briefSection": "Infrastructure requirements", "text": "How many warehouse facilities need to be managed?", "ngoText": "How many warehouse facilities need to be managed?" }, { "id": "item-volume-and-variety", "type": "select", "options": [ { "label": "Low volume, limited variety (100-500 items)", "value": "low-volume" }, { "label": "Medium volume and variety (500-5000 items)", "value": "medium-volume" }, { "label": "High volume and variety (5000+ items)", "value": "high-volume" } ], "propertyMapping": { "low-volume": { "technologies": [ "Simple inventory system", "Spreadsheet or basic database" ], "technologyProperties": { "systemComplexity": "simple", "automationLevel": "minimal", "staffingNeeds": "part-time", "investmentRequired": "low" } }, "medium-volume": { "technologies": [ "Warehouse management system", "Inventory platform" ], "technologyProperties": { "systemComplexity": "moderate", "automationLevel": "semi-automated", "staffingNeeds": "dedicated-staff", "investmentRequired": "moderate" } }, "high-volume": { "technologies": [ "Enterprise WMS platform", "Advanced logistics system" ], "technologyProperties": { "systemComplexity": "advanced", "automationLevel": "fully-automated", "staffingNeeds": "specialized-team", "investmentRequired": "high" } } }, "prefillFrom": null, "briefSection": "Inventory management", "text": "What is the inventory volume and variety?", "ngoText": "What is the inventory volume and variety?" }, { "id": "existing-wms-integration", "type": "select", "options": [ { "label": "No integration, standalone system", "value": "standalone" }, { "label": "API integration with existing WMS", "value": "api-integration" }, { "label": "Full replacement of existing WMS", "value": "full-replacement" } ], "propertyMapping": { "standalone": { "technologies": [ "Independent inventory system", "Manual synchronisation" ], "technologyProperties": { "integrationComplexity": "none", "dataConsistency": "manual-sync", "implementationTime": "short", "maintenanceCost": "low" } }, "api-integration": { "technologies": [ "WMS API connection", "Data synchronisation platform" ], "technologyProperties": { "integrationComplexity": "moderate", "dataConsistency": "periodic-sync", "implementationTime": "medium", "maintenanceCost": "moderate" } }, "full-replacement": { "technologies": [ "Enterprise warehouse management system", "Complete platform migration" ], "technologyProperties": { "integrationComplexity": "high", "dataConsistency": "real-time", "implementationTime": "long", "maintenanceCost": "high" } } }, "prefillFrom": null, "briefSection": "Infrastructure requirements", "text": "Should the system integrate with existing WMS?", "ngoText": "Should the system integrate with existing WMS?" }, { "id": "warehouse-automation-level", "type": "select", "options": [ { "label": "Manual operations and record keeping", "value": "manual-operations" }, { "label": "Semi-automated with barcoding", "value": "semi-automated" }, { "label": "Fully automated with RFID and robotics", "value": "fully-automated" } ], "propertyMapping": { "manual-operations": { "technologies": [ "Manual inventory management", "Paper-based record system" ], "technologyProperties": { "operationSpeed": "slow", "accuracyRate": "moderate", "laborCost": "high", "investmentCost": "low" } }, "semi-automated": { "technologies": [ "Barcode scanning system", "Automated data capture" ], "technologyProperties": { "operationSpeed": "moderate", "accuracyRate": "high", "laborCost": "moderate", "investmentCost": "moderate" } }, "fully-automated": { "technologies": [ "RFID tracking system", "Automated retrieval system", "Warehouse robotics" ], "technologyProperties": { "operationSpeed": "fast", "accuracyRate": "very-high", "laborCost": "low", "investmentCost": "high" } } }, "prefillFrom": null, "briefSection": "Infrastructure requirements", "text": "What level of warehouse automation is desired?", "ngoText": "What level of warehouse automation is desired?" }, { "id": "warehouse-count", "type": "select", "options": [ { "label": "1\u20133 locations", "value": "small" }, { "label": "4\u201310 locations", "value": "medium" }, { "label": "11\u201330 locations", "value": "large" }, { "label": "Over 30 locations", "value": "enterprise" } ], "propertyMapping": { "small": { "technologies": [ "Simple inventory ledger" ], "technologyProperties": { "networkScale": "Small", "syncComplexity": "Low" } }, "medium": { "technologies": [ "Multi-site inventory platform" ], "technologyProperties": { "networkScale": "Medium", "syncComplexity": "Medium" } }, "large": { "technologies": [ "Enterprise inventory platform", "Regional hub sync" ], "technologyProperties": { "networkScale": "Large", "syncComplexity": "High" } }, "enterprise": { "technologies": [ "Enterprise inventory platform", "Automated routing", "Regional hub sync" ], "technologyProperties": { "networkScale": "Enterprise", "syncComplexity": "Very high" } } }, "prefillFrom": null, "briefSection": "Infrastructure requirements", "text": "How many warehouse or storage locations need to be connected?", "ngoText": "How many warehouse or storage locations need to be connected?", "hidden": true }, { "id": "audit-mechanism-approach", "type": "select", "options": [ { "label": "Automatic checks that flag problems as they happen", "value": "automated-realtime" }, { "label": "Regular scheduled reviews with tamper-proof records", "value": "periodic-batch" }, { "label": "Ability to check any record at any time with proof it has not been altered", "value": "on-demand" }, { "label": "External auditors can log in and review records independently", "value": "third-party" } ], "propertyMapping": { "automated-realtime": { "technologies": [ "Real-time audit mechanism", "Automated anomaly detection", "Audit alert service" ], "technologyProperties": { "auditFrequency": "Continuous / real-time", "auditAccess": "System-generated alerts", "complianceReporting": "Automated" } }, "periodic-batch": { "technologies": [ "Periodic audit mechanism", "Batch verification engine", "Audit report generator" ], "technologyProperties": { "auditFrequency": "Scheduled (daily/weekly/monthly)", "auditAccess": "Generated audit reports", "complianceReporting": "Scheduled" } }, "on-demand": { "technologies": [ "On-demand audit mechanism", "Audit query interface", "Record verification service" ], "technologyProperties": { "auditFrequency": "On-demand", "auditAccess": "Query-based", "complianceReporting": "On request" } }, "third-party": { "technologies": [ "Third-party audit mechanism", "Auditor access portal", "Audit evidence export" ], "technologyProperties": { "auditFrequency": "As required by auditor", "auditAccess": "Dedicated portal with read-only access", "complianceReporting": "Auditor-directed" } } }, "prefillFrom": null, "briefSection": "Audit and verification", "text": "Who needs to verify that actions happened correctly, and how easily should they be able to check?", "ngoText": "How should auditing and verification work for this solution?" } ], "complexityFactors": { "relationships": 1, "operationalChange": 2, "dataCompliance": 1 }, "suggestedCriteria": [ { "id": "SC-INVENTORY-ACCURACY", "name": "Inventory Accuracy & Stock Control", "description": "This measures how accurately the system maintains inventory records and which controls ensure accuracy. Inventory inaccuracy leads to stockouts (items recorded but not present) or hidden surplus (items present but unrecorded).", "weight": 0.25, "ratingGuide": { "5": "Real-time inventory accuracy with barcode/RFID scanning at every movement. Cycle counting workflows. Variance investigation and adjustment approvals. Stock accuracy KPI tracking (target >98%). Bin-location management for precise storage location.", "4": "Scan-based movements. Periodic cycle counts. Adjustment approval workflow. Location-level tracking.", "3": "Manual entry with periodic physical counts. Basic adjustment recording. Warehouse-level tracking.", "2": "Periodic stock counts with manual ledger. No real-time accuracy. No location tracking.", "1": "Paper-based stock cards. No system accuracy controls." } }, { "id": "SC-WAREHOUSE-OPS", "name": "Warehouse Operations Workflow", "description": "The system supports core warehouse operations (receiving, put-away, picking, packing, and dispatch). Operational efficiency reduces labour costs and speeds up humanitarian response.", "weight": 0.25, "ratingGuide": { "5": "Full WMS workflow: goods receipt with inspection \u2192 put-away with location suggestion \u2192 wave/batch picking \u2192 packing with verification \u2192 dispatch with proof of shipment. Mobile-directed operations. Performance metrics (pick rate, dock-to-stock time).", "4": "Core workflows supported: receipt, picking, dispatch. Mobile capability. Basic performance tracking.", "3": "Receipt, dispatch, and stock count workflows. Desktop-based. Manual location management.", "2": "Receipt and dispatch recording. No pick/pack workflow. Manual processes.", "1": "Ledger-style recording of in/out only. No operational workflows." } }, { "id": "SC-MULTI-WAREHOUSE", "name": "Multi-Warehouse & Inter-Facility Transfer", "description": "The system can manage inventory across multiple warehouses and coordinate inter-facility transfers. Humanitarian operations typically involve a network of warehouses: central, regional, and forward staging areas.", "weight": 0.2, "ratingGuide": { "5": "Unlimited warehouses with hierarchy. Inter-facility transfer workflow with in-transit visibility. Consolidation and redistribution planning. Central dashboard with drill-down to individual warehouse. Network-wide stock optimisation suggestions.", "4": "Multi-warehouse support. Transfer management with tracking. Consolidated reporting. Basic redistribution planning.", "3": "Multiple warehouses as separate entities. Transfer recording. Aggregate reporting across warehouses.", "2": "Designed for single warehouse. Manual coordination across locations.", "1": "Single warehouse only. No multi-site capability." } }, { "id": "SC-REPORTING-ANALYTICS", "name": "Reporting & Demand Analytics", "description": "The system provides inventory analytics (consumption trends, seasonal patterns, reorder point recommendations, and pipeline visibility). Data-driven inventory management reduces waste and prevents stockouts.", "weight": 0.2, "ratingGuide": { "5": "Consumption trend analysis with forecasting. Seasonal demand patterns. Automatic reorder point calculation. Pipeline visibility (on-order, in-transit). ABC classification. Donor-attributable reporting. Customisable dashboards.", "4": "Consumption reporting with basic trends. Configurable reorder points. Pipeline tracking. Standard dashboards.", "3": "Monthly consumption reports. Fixed reorder points. Manual pipeline tracking. Standard reports.", "2": "Current stock level reports. No trend analysis. No reorder recommendations.", "1": "Minimal reporting. Stock counts only." } }, { "id": "SC-HUMANITARIAN-ADAPT", "name": "Humanitarian Warehouse Adaptability", "description": "Is the system adapted to humanitarian warehousing realities (temporary structures, high staff turnover, mixed storage conditions, surge capacity requirements)?", "weight": 0.1, "ratingGuide": { "5": "Designed for humanitarian warehousing. Supports temporary/mobile warehouses. Quick setup (<1 day). Intuitive for high-turnover staff. Works in low-infrastructure settings (no WiFi requirement). Handles surge volumes. Sphere logistics standards reference.", "4": "Adaptable to humanitarian settings. Quick setup. Simple interface. Offline capability. Handles variable volumes.", "3": "Commercial WMS adaptable to humanitarian use. Standard setup time. Some training required.", "2": "Commercial WMS with minimal humanitarian adaptation. Significant setup and training.", "1": "Enterprise WMS unsuitable for humanitarian field conditions." } } ], "procurement": { "marketMaturity": "mature", "primaryMode": "off-the-shelf", "alternativeModes": [ "rfq" ], "reasoning": "Warehouse inventory management is mature SaaS market.", "exampleProductCategories": [ "warehouse-management-saas", "inventory-saas" ], "partnerChannels": [], "lastReviewed": "2026-05-01" } }, { "id": "UC-D-066", "name": "Expiry tracking and waste reduction", "category": "D", "subcategory": "Inventory Management", "description": "Track expiry dates across storage sites, so items are used or redistributed before they expire and you know what happened to any that did.", "bCriteria": [ "B1", "B3" ], "requiredComponents": [ { "component": "tracking-platform", "description": "Expiry date tracking" }, { "component": "qr-barcode", "description": "Expiry information encoding" }, { "component": "inventory-integration", "description": "Inventory expiry alerts" }, { "component": "alert-mechanism", "description": "Automated expiry warnings" } ], "conditionalComponents": [ { "component": "smart-contracts", "condition": "If automated removal of expired items" } ], "crossCategoryDependencies": [], "p2TriggerConditions": { "description": "Activated when P2 shows significant waste + expiry concerns + efficiency focus", "rangeSignals": [ "wasteRate >= significant", "expiryLosses >= concern", "efficiencyFocus >= true" ] }, "contextFieldsTemplate": [ { "field": "itemTypes", "source": "P2 inventory", "description": "Items with expiry dates" }, { "field": "wasteRate", "source": "P2 efficiency", "description": "Current waste percentage" }, { "field": "locations", "source": "P0 logistics", "description": "Storage locations" }, { "field": "costSavings", "source": "P2 targets", "description": "Waste reduction target" }, { "field": "supplyTypes", "source": "P2 health programmes", "description": "Medical supplies tracked" }, { "field": "volume", "source": "P2 annual consumption", "description": "Annual supply volume" }, { "field": "wasteConcern", "source": "P2 efficiency", "description": "Waste reduction priority" } ], "implementationComplexity": "low-medium", "examples": { "note": "Inventory efficiency and waste reduction", "references": [ { "name": "WHO Shelf-Life and Storage Management", "url": "https://www.who.int/medicines/publications/pharmacopeial", "solved": "Established guidance for medicine expiry tracking in resource-limited settings" }, { "name": "Project Last Mile - Inventory Optimization", "url": "https://www.projectlastmile.com/solutions/inventory-management", "solved": "Reduced medical supply waste by 45% in 8 African countries" }, { "name": "WHO Medicines Shelf-Life Management", "url": "https://www.who.int/publications/stability-testing", "solved": "Established expiry tracking standards for NGO medical supply programmes" } ] }, "solutionQuestions": [ { "id": "expiry-item-types-scope", "type": "select", "options": [ { "label": "Medicines and medical supplies only", "value": "medical-only" }, { "label": "Medicines, food, and perishables", "value": "medicines-food" }, { "label": "Comprehensive (all time-sensitive items)", "value": "comprehensive" } ], "propertyMapping": { "medical-only": { "technologies": [ "Medicine expiry tracking", "Pharmaceutical inventory" ], "technologyProperties": { "itemCategories": "1", "trackingRequirement": "lot-and-expiry", "regulatoryCompliance": "high", "dataFields": "pharmaceutical-specific" } }, "medicines-food": { "technologies": [ "Multi-category expiry system", "Food and medicine tracking" ], "technologyProperties": { "itemCategories": "2-3", "trackingRequirement": "batch-and-expiry", "regulatoryCompliance": "high", "dataFields": "comprehensive" } }, "comprehensive": { "technologies": [ "Universal expiry tracking platform", "Time-sensitive inventory system" ], "technologyProperties": { "itemCategories": "10+", "trackingRequirement": "complete-lifecycle", "regulatoryCompliance": "varies", "dataFields": "complete" } } }, "prefillFrom": null, "briefSection": "Inventory management", "text": "What types of items with expiry dates need tracking?", "ngoText": "What types of items with expiry dates need tracking?" }, { "id": "waste-reduction-targets", "type": "select", "options": [ { "label": "No specific target (current state acceptable)", "value": "no-target" }, { "label": "Reduce waste by 25-50%", "value": "moderate-target" }, { "label": "Aggressive target: reduce waste by 75%+", "value": "aggressive-target" } ], "propertyMapping": { "no-target": { "technologies": [ "Basic expiry tracking", "Standard inventory management" ], "technologyProperties": { "improvementFocus": "minimal", "investmentRequired": "low", "operationalChange": "minimal", "expectedOutcome": "status-quo" } }, "moderate-target": { "technologies": [ "Expiry prediction engine", "FIFO inventory management system" ], "technologyProperties": { "improvementFocus": "significant", "investmentRequired": "moderate", "operationalChange": "moderate", "expectedOutcome": "25-50% reduction" } }, "aggressive-target": { "technologies": [ "Advanced demand forecasting", "Predictive expiry system", "Automated FIFO engine" ], "technologyProperties": { "improvementFocus": "transformative", "investmentRequired": "high", "operationalChange": "substantial", "expectedOutcome": "75%+ reduction" } } }, "prefillFrom": null, "briefSection": "Quality assurance", "text": "What waste reduction targets are being set?", "ngoText": "What waste reduction targets are being set?" }, { "id": "expiry-alert-mechanism-type", "type": "select", "options": [ { "label": "Manual monthly reviews", "value": "manual-review" }, { "label": "Automated email/SMS alerts at 90-30 days", "value": "automated-email-sms" }, { "label": "Real-time dashboard with predictive warnings", "value": "realtime-predictive" } ], "propertyMapping": { "manual-review": { "technologies": [ "Monthly review schedule", "Spreadsheet tracking" ], "technologyProperties": { "alertFrequency": "monthly", "automationLevel": "none", "responseTime": "days", "missedExpiryRisk": "high" } }, "automated-email-sms": { "technologies": [ "Expiry alert engine", "Multi-channel notification system" ], "technologyProperties": { "alertFrequency": "scheduled", "automationLevel": "automated", "responseTime": "hours", "missedExpiryRisk": "low" } }, "realtime-predictive": { "technologies": [ "Real-time analytics dashboard", "Predictive expiry model" ], "technologyProperties": { "alertFrequency": "continuous", "automationLevel": "fully-automated", "responseTime": "minutes", "missedExpiryRisk": "minimal" } } }, "prefillFrom": null, "briefSection": "Last-mile verification", "text": "What alert mechanism should warn of approaching expiry?", "ngoText": "What alert mechanism should warn of approaching expiry?" }, { "id": "fifo-enforcement-method", "type": "select", "options": [ { "label": "Manual FIFO compliance verification", "value": "manual-fifo" }, { "label": "Barcode-based FIFO sequencing", "value": "barcode-fifo" }, { "label": "Automated FIFO enforcement with alerts", "value": "automated-fifo" } ], "propertyMapping": { "manual-fifo": { "technologies": [ "FIFO compliance checklist", "Manual shelf arrangement" ], "technologyProperties": { "complianceRate": "moderate", "enforcementLevel": "manual", "staffTraining": "basic", "reliabilityScore": "moderate" } }, "barcode-fifo": { "technologies": [ "Barcode sequencing system", "FIFO order platform" ], "technologyProperties": { "complianceRate": "high", "enforcementLevel": "guided", "staffTraining": "moderate", "reliabilityScore": "high" } }, "automated-fifo": { "technologies": [ "Automated FIFO sequencing engine", "Location-based routing system" ], "technologyProperties": { "complianceRate": "very-high", "enforcementLevel": "enforced", "staffTraining": "minimal", "reliabilityScore": "very-high" } } }, "prefillFrom": null, "briefSection": "Inventory management", "text": "How do you currently enforce FIFO (first-in-first-out) in your inventory?", "ngoText": "How do you currently enforce FIFO (first-in-first-out) in your inventory?" }, { "id": "sq-UC-D-066-003", "type": "single-select", "options": [ { "value": "photo-evidence", "label": "Photo evidence" }, { "value": "witness-attestation", "label": "Witness attestation" }, { "value": "weight-volume-record", "label": "Weight/volume record" }, { "value": "environmental-disposal-cert", "label": "Environmental disposal certificate" }, { "value": "donor-notification", "label": "Donor notification" } ], "propertyMapping": { "photo-evidence": { "technologies": [ "image-capture", "photo-logging" ], "technologyProperties": {} }, "witness-attestation": { "technologies": [ "witness-system", "signature-capture" ], "technologyProperties": {} }, "weight-volume-record": { "technologies": [ "measurement-system", "waste-tracking" ], "technologyProperties": {} }, "environmental-disposal-cert": { "technologies": [ "disposal-partner", "certification-system" ], "technologyProperties": {} }, "donor-notification": { "technologies": [ "donor-alerts", "waste-reporting" ], "technologyProperties": {} } }, "briefSection": "compliance", "text": "What waste documentation is required for expired items?", "ngoText": "What waste documentation is required for expired items?" }, { "id": "supply-volume-scale", "type": "select", "options": [ { "label": "Low volume (< 10,000 units/year)", "value": "low-volume" }, { "label": "Medium volume (10,000 - 100,000 units/year)", "value": "medium-volume" }, { "label": "High volume (> 100,000 units/year)", "value": "high-volume" } ], "propertyMapping": { "low-volume": { "technologies": [ "Manual inventory tracking", "Spreadsheet-based system" ], "technologyProperties": { "automationLevel": "minimal", "systemComplexity": "simple", "investmentRequired": "low", "staffingNeeds": "part-time" } }, "medium-volume": { "technologies": [ "Inventory management platform", "Expiry alert engine" ], "technologyProperties": { "automationLevel": "semi-automated", "systemComplexity": "moderate", "investmentRequired": "moderate", "staffingNeeds": "dedicated-staff" } }, "high-volume": { "technologies": [ "Enterprise inventory management system", "Automated expiry tracking platform" ], "technologyProperties": { "automationLevel": "fully-automated", "systemComplexity": "advanced", "investmentRequired": "high", "staffingNeeds": "specialized-team" } } }, "prefillFrom": null, "briefSection": "Inventory management", "text": "What is the annual volume of medical supplies to be tracked?", "ngoText": "What is the annual volume of medical supplies to be tracked?" }, { "id": "tracking-granularity-supply", "type": "select", "options": [ { "label": "Batch/box level tracking only", "value": "batch-only" }, { "label": "Individual item tracking", "value": "individual-items" }, { "label": "Hybrid batch and sampling approach", "value": "hybrid-approach" } ], "propertyMapping": { "batch-only": { "technologies": [ "Batch tracking system", "Lot-level inventory engine" ], "technologyProperties": { "trackingUnit": "batch-or-box", "dataCarrier": "label-per-batch", "labelingCost": "low", "administrativeOverhead": "low" } }, "individual-items": { "technologies": [ "Item-level tracking platform", "Serialisation engine" ], "technologyProperties": { "trackingUnit": "individual-item", "dataCarrier": "label-per-item", "labelingCost": "high", "administrativeOverhead": "high" } }, "hybrid-approach": { "technologies": [ "Hybrid tracking system", "Intelligent sampling platform" ], "technologyProperties": { "trackingUnit": "batch-plus-sample", "dataCarrier": "selective-labeling", "labelingCost": "moderate", "administrativeOverhead": "moderate" } } }, "prefillFrom": null, "briefSection": "Inventory management", "text": "Should supplies be tracked at batch or individual item level?", "ngoText": "Should supplies be tracked at batch or individual item level?" }, { "id": "sq-UC-D-066-004", "type": "single-select", "options": [ { "value": "temperature-only", "label": "Temperature only" }, { "value": "temperature-humidity", "label": "Temperature and humidity" }, { "value": "full-environmental", "label": "Full environmental monitoring" }, { "value": "gps-location", "label": "GPS location tracking" }, { "value": "none-expiry-only", "label": "Expiry only" } ], "propertyMapping": { "temperature-only": { "technologies": [ "temperature-sensor", "temp-monitoring" ], "technologyProperties": {} }, "temperature-humidity": { "technologies": [ "sensor-array", "environmental-monitoring" ], "technologyProperties": {} }, "full-environmental": { "technologies": [ "comprehensive-monitoring", "multi-parameter-tracking" ], "technologyProperties": {} }, "gps-location": { "technologies": [ "gps-tracking", "location-monitoring" ], "technologyProperties": {} }, "none-expiry-only": { "technologies": [ "simple-tracking", "date-based-only" ], "technologyProperties": {} } }, "briefSection": "requirements", "text": "What temperature and storage condition monitoring is needed alongside expiry tracking?", "ngoText": "What temperature and storage condition monitoring is needed alongside expiry tracking?" }, { "id": "item-tracking-method", "type": "select", "options": [ { "label": "QR codes printed on items or packaging", "value": "qr-codes" }, { "label": "NFC tags embedded in items", "value": "nfc-tags" }, { "label": "Barcode labels with batch scanning", "value": "barcode" }, { "label": "Mixed: QR for high-value items, barcode for bulk", "value": "mixed" } ], "propertyMapping": { "qr-codes": { "technologies": [ "QR code generation service", "QR/barcode scanning app", "Item-level tracking ledger" ], "technologyProperties": { "trackingGranularity": "Per-item or per-batch", "scanMethod": "Mobile phone camera / QR scanner", "offlineCapable": "Yes \u2014 scan and sync when connected" } }, "nfc-tags": { "technologies": [ "NFC tag provisioning", "NFC reader integration", "Item-level tracking ledger" ], "technologyProperties": { "trackingGranularity": "Per-item", "scanMethod": "NFC-enabled device", "offlineCapable": "Yes \u2014 NFC works offline" } }, "barcode": { "technologies": [ "Barcode generation service", "QR/barcode scanning app", "Batch tracking ledger" ], "technologyProperties": { "trackingGranularity": "Per-batch", "scanMethod": "Barcode scanner / mobile camera", "offlineCapable": "Yes \u2014 scan and sync" } }, "mixed": { "technologies": [ "QR code generation service", "Barcode generation service", "QR/barcode scanning app", "Multi-level tracking ledger" ], "technologyProperties": { "trackingGranularity": "Mixed \u2014 item-level for high-value, batch for bulk", "scanMethod": "Mobile phone camera / scanner", "offlineCapable": "Yes" } } }, "prefillFrom": null, "briefSection": "Item tracking", "text": "How will physical items be tracked and scanned in the field?", "ngoText": "How will physical items be tracked and scanned in the field?" } ], "complexityFactors": { "relationships": 1, "operationalChange": 2, "dataCompliance": 1 }, "suggestedCriteria": [ { "id": "SC-EXPIRY-VISIBILITY", "name": "Expiry Date Visibility & Alerting", "description": "The system provides clear, actionable visibility into expiry dates across all stock, with tiered alerts. Early warning enables redistribution or accelerated use before expiry. Late warning means waste.", "weight": 0.3, "ratingGuide": { "5": "Dashboard showing all stock by expiry timeline (traffic light: green/amber/red). Configurable multi-tier alerts (e.g., 180/90/60/30 days). Alerts pushed to relevant staff by role. Expiry risk quantified in financial terms. Forecasting of future waste based on consumption rates.", "4": "Expiry dashboard with traffic light. Multi-tier alerts. Role-based notifications. Basic waste forecasting.", "3": "Expiry reports sortable by date. Single threshold alert. Email notifications.", "2": "Expiry dates recorded but no proactive alerting. Manual review required.", "1": "No expiry visibility. Physical inspection only." } }, { "id": "SC-REDISTRIBUTION", "name": "Near-Expiry Redistribution Engine", "description": "The system can suggest or facilitate redistribution of near-expiry stock to high-consumption sites. Redistribution is the primary waste prevention mechanism. Items approaching expiry at a low-consumption site can still be used at a high-consumption site.", "weight": 0.25, "ratingGuide": { "5": "Automated redistribution recommendations based on consumption rates, lead times, and remaining shelf life. Transfer workflow with logistics coordination. Network-wide optimisation. Tracks redistribution outcomes (items saved vs. wasted). Partner organisation sharing for items the NGO cannot use.", "4": "Redistribution suggestions based on stock levels and expiry. Transfer workflow. Basic outcome tracking.", "3": "Near-expiry list shared across sites. Manual transfer coordination. No consumption-based matching.", "2": "Near-expiry stock flagged but no redistribution support. Manual coordination outside system.", "1": "No redistribution capability." } }, { "id": "SC-WASTE-ANALYTICS", "name": "Waste Root Cause Analytics", "description": "The system analyses why waste occurs (over-ordering, slow distribution, wrong product mix, storage failures) and provide actionable insights. Reducing waste requires understanding its causes.", "weight": 0.2, "ratingGuide": { "5": "Root cause categorisation for all waste events (overstock, slow consumption, storage failure, damage, recall). Trend analysis by cause, location, product category. Actionable recommendations (adjust reorder quantities, change supplier, improve storage). Benchmark waste rates across sites.", "4": "Waste categorisation with cause codes. Trend reports. Basic recommendations. Site comparison.", "3": "Waste recording with reason codes. Aggregate cause analysis. Standard reporting.", "2": "Waste quantity recorded. Free-text reason. No cause analysis.", "1": "No waste analytics. Total write-off figures only." } }, { "id": "SC-DISPOSAL-COMPLY", "name": "Compliant Disposal Documentation", "description": "The system manages the disposal process for expired items (documentation, approval, environmental compliance, and financial write-off). Improper disposal of expired medicines or chemicals is both an environmental and audit risk.", "weight": 0.15, "ratingGuide": { "5": "Disposal workflow with approval chain. Method selection (incineration, landfill, return to supplier) with environmental compliance guidance. Disposal certificates. Photo documentation. Financial write-off integration. Regulatory reporting where required.", "4": "Disposal workflow with approval. Method recording. Documentation requirements. Financial write-off.", "3": "Disposal recording with reason and approval. Basic documentation. Manual financial adjustment.", "2": "Disposal noted in records. Minimal documentation. No approval workflow.", "1": "No disposal process. Items removed from inventory with no documentation." } }, { "id": "SC-DEMAND-FORECAST", "name": "Demand Forecasting & Procurement Optimisation", "description": "The system can forecast demand to prevent future over-ordering. The best waste reduction happens upstream: ordering the right quantities in the first place.", "weight": 0.1, "ratingGuide": { "5": "Statistical demand forecasting using historical consumption. Seasonal adjustment. Lead-time-aware reorder points. Recommended order quantities. Integration with procurement/supply planning. Scenario modelling (programme expansion, seasonal surge).", "4": "Consumption-based demand forecasting. Configurable reorder points. Order quantity suggestions.", "3": "Average consumption calculation. Fixed reorder points. Manual order planning.", "2": "Historical consumption data available. No forecasting. Manual procurement decisions.", "1": "No demand data. Procurement based on guesswork or blanket allocation." } } ], "procurement": { "marketMaturity": "mature", "primaryMode": "off-the-shelf", "alternativeModes": [ "rfq" ], "reasoning": "Expiry tracking is included in mature inventory products.", "exampleProductCategories": [ "inventory-saas", "expiry-tracking-platform" ], "partnerChannels": [], "lastReviewed": "2026-05-01" } }, { "id": "UC-D-067", "name": "Smallholder farmer market access and fair trade verification", "category": "D", "subcategory": "Market Access and Livelihoods", "description": "Help small farmers show where and how their produce was grown, so they can reach buyers and earn fair prices with fewer middlemen.", "bCriteria": [ "B1", "B3", "B5" ], "requiredComponents": [ { "component": "provenance-ledger", "description": "Blockchain record of production origin and conditions" }, { "component": "attestation-engine", "description": "Quality and fair-trade condition verification" }, { "component": "buyer-gateway", "description": "Integration with premium market buyers and certification bodies" }, { "component": "farmer-payment-rail", "description": "Payment pipeline from buyer to smallholder" } ], "conditionalComponents": [ { "component": "field-data-capture", "condition": "If production data is captured at farm level" }, { "component": "identity-verification", "condition": "If farmer identity needs to be verified for certification" } ], "crossCategoryDependencies": [ "UC-A-001 if farmer payments use stablecoin rails", "UC-B-035 for skills attestation and farmer certification" ], "p2TriggerConditions": { "description": "Activated when P2 identifies market access barriers for smallholders, inability to prove fair trade or organic status, low prices due to lack of documentation, or agricultural supply chain opacity", "rangeSignals": [ "marketAccessBarrier >= significant", "documentationGap >= moderate", "priceDisadvantage >= measurable", "supplyChainTransparency <= low" ] }, "contextFieldsTemplate": [ { "field": "cropType", "source": "P2 answers", "description": "Primary crop or product" }, { "field": "farmerCount", "source": "P2 answers", "description": "Number of smallholder farmers" }, { "field": "targetMarket", "source": "P2 answers", "description": "Target premium market (fair trade, organic, direct trade)" }, { "field": "existingDocumentation", "source": "P2 answers", "description": "Current production documentation practices" } ], "implementationComplexity": "medium-high", "examples": { "note": "Mercy Corps/WEIA Colombia smallholder coffee; multiple East African agri-chain pilots", "references": [ { "name": "WEIA / Mercy Corps Colombia", "url": "https://www.mercycorps.org/", "solved": "Gained premium prices for smallholder coffee producers in Colombia through blockchain traceability" }, { "name": "Farmer Connect (IBM)", "url": "https://www.farmerconnect.com/", "solved": "Coffee supply chain traceability from farm to cup with consumer-facing verification" }, { "name": "AgriLedger", "url": "https://www.agriledger.com/", "solved": "Blockchain-based provenance and fair payment for smallholder farmers in developing economies" } ] }, "solutionQuestions": [ { "id": "farmer-count", "label": "How many smallholder farmers would participate in the programme?", "type": "select", "briefSection": "provenance-recording", "options": [ { "label": "Under 100 farmers", "value": "small" }, { "label": "100\u2013500 farmers", "value": "medium" }, { "label": "500\u20135,000 farmers", "value": "large" }, { "label": "5,000+ farmers", "value": "very-large" } ], "propertyMapping": { "small": { "technologies": [ "Basic provenance ledger" ], "technologyProperties": { "farmerScale": "Under 100", "onboardingComplexity": "Low" } }, "medium": { "technologies": [ "Scalable provenance platform" ], "technologyProperties": { "farmerScale": "100\u2013500", "onboardingComplexity": "Medium" } }, "large": { "technologies": [ "Enterprise provenance platform", "Cooperative management module" ], "technologyProperties": { "farmerScale": "500\u20135,000", "onboardingComplexity": "High" } }, "very-large": { "technologies": [ "Multi-cooperative provenance infrastructure" ], "technologyProperties": { "farmerScale": "5,000+", "onboardingComplexity": "Very high" } } }, "text": "How many smallholder farmers would participate in the programme?" }, { "id": "certification-target", "label": "Which market certification or standard are you targeting?", "type": "multiselect", "briefSection": "quality-attestation", "options": [ { "label": "Fair Trade certification", "value": "fair-trade" }, { "label": "Organic certification", "value": "organic" }, { "label": "Direct trade / specialty market", "value": "direct-trade" }, { "label": "Rainforest Alliance / sustainability", "value": "sustainability" }, { "label": "No specific certification, general provenance", "value": "general" } ], "propertyMapping": { "fair-trade": { "technologies": [ "Fair Trade attestation module" ], "technologyProperties": { "certificationTarget": "Fair Trade", "verificationRequirements": "Labour conditions, pricing, community premium" } }, "organic": { "technologies": [ "Organic attestation module" ], "technologyProperties": { "certificationTarget": "Organic", "verificationRequirements": "Input tracking, soil testing, no-spray verification" } }, "direct-trade": { "technologies": [ "Direct trade provenance module" ], "technologyProperties": { "certificationTarget": "Direct trade", "verificationRequirements": "Farm-to-buyer traceability" } }, "sustainability": { "technologies": [ "Sustainability attestation module" ], "technologyProperties": { "certificationTarget": "Sustainability standard", "verificationRequirements": "Environmental and social criteria" } }, "general": { "technologies": [ "General provenance module" ], "technologyProperties": { "certificationTarget": "General provenance", "verificationRequirements": "Origin and basic production conditions" } } }, "text": "Which market certification or standard are you targeting?" }, { "id": "buyer-integration", "label": "How will buyers access and verify the provenance data?", "type": "select", "briefSection": "buyer-integration", "options": [ { "label": "Consumer-facing QR code on product packaging", "value": "consumer-qr" }, { "label": "B2B API integration with buyer procurement systems", "value": "b2b-api" }, { "label": "Certification body verification portal", "value": "cert-portal" }, { "label": "All of the above", "value": "all" } ], "propertyMapping": { "consumer-qr": { "technologies": [ "Consumer verification app", "QR code generation" ], "technologyProperties": { "buyerAccess": "Consumer-facing QR", "integrationComplexity": "Low" } }, "b2b-api": { "technologies": [ "Buyer integration API", "Procurement system connector" ], "technologyProperties": { "buyerAccess": "B2B API", "integrationComplexity": "Medium" } }, "cert-portal": { "technologies": [ "Certification verification portal" ], "technologyProperties": { "buyerAccess": "Certification body portal", "integrationComplexity": "Medium" } }, "all": { "technologies": [ "Consumer verification app", "Buyer integration API", "Certification verification portal" ], "technologyProperties": { "buyerAccess": "Multi-channel", "integrationComplexity": "High" } } }, "text": "How will buyers access and verify the provenance data?" }, { "id": "farmer-payment-method", "label": "How will farmers receive payments from premium buyers?", "type": "select", "briefSection": "farmer-payment", "options": [ { "label": "Mobile money (existing mobile money account)", "value": "mobile-money" }, { "label": "Stablecoin to farmer wallet", "value": "stablecoin" }, { "label": "Bank transfer through cooperative", "value": "bank-cooperative" }, { "label": "Cash through agent network", "value": "cash-agent" } ], "propertyMapping": { "mobile-money": { "technologies": [ "Mobile money payment rail" ], "technologyProperties": { "farmerPayment": "Mobile money", "paymentSpeed": "Near-instant" } }, "stablecoin": { "technologies": [ "Stablecoin payment rail", "Farmer wallet" ], "technologyProperties": { "farmerPayment": "Stablecoin", "paymentSpeed": "Same-day" } }, "bank-cooperative": { "technologies": [ "Cooperative bank transfer module" ], "technologyProperties": { "farmerPayment": "Bank via cooperative", "paymentSpeed": "T+1 to T+3" } }, "cash-agent": { "technologies": [ "Cash agent distribution network" ], "technologyProperties": { "farmerPayment": "Cash agent", "paymentSpeed": "Depends on agent availability" } } }, "text": "How will farmers receive payments from premium buyers?" }, { "id": "local-infrastructure", "label": "What technology infrastructure exists at the farm level?", "type": "select", "briefSection": "local-infrastructure", "options": [ { "label": "Smartphones with mobile data common among farmers", "value": "smartphone" }, { "label": "Feature phones only: SMS/USSD required", "value": "feature-phone" }, { "label": "Limited phone access: cooperative/agent intermediary needed", "value": "intermediary" }, { "label": "Mixed: some smartphone, some feature phone, some no phone", "value": "mixed" } ], "propertyMapping": { "smartphone": { "technologies": [ "Smartphone data capture app" ], "technologyProperties": { "farmInfrastructure": "Smartphone with data", "captureMethod": "Direct farmer app" } }, "feature-phone": { "technologies": [ "USSD/SMS data capture" ], "technologyProperties": { "farmInfrastructure": "Feature phone only", "captureMethod": "USSD/SMS interface" } }, "intermediary": { "technologies": [ "Agent-assisted data capture", "Offline-capable tablet" ], "technologyProperties": { "farmInfrastructure": "Limited \u2014 intermediary needed", "captureMethod": "Agent/cooperative staff" } }, "mixed": { "technologies": [ "Multi-modal data capture (app + USSD + agent)" ], "technologyProperties": { "farmInfrastructure": "Mixed", "captureMethod": "Multi-channel" } } }, "text": "What technology infrastructure exists at the farm level?" } ], "complexityFactors": { "relationships": 3, "operationalChange": 3, "dataCompliance": 2 }, "suggestedCriteria": [ { "id": "SC-FARMER-PROVENANCE", "name": "Farm-to-Buyer Provenance & Traceability", "description": "The system can trace agricultural products from individual smallholder farms through aggregation, processing, and sale to the buyer. Provenance is what enables premium pricing. A buyer paying for 'fair trade organic coffee' needs proof it came from certified farmers.", "weight": 0.3, "ratingGuide": { "5": "Individual farm-level traceability through aggregation, processing, and export. Handles complex product transformations (cherry \u2192 green \u2192 roasted coffee). Batch splitting and merging tracked. QR-code consumer-facing provenance story. Integration with certification bodies.", "4": "Farm-level to buyer traceability. Handles basic processing steps. Batch tracking. Provenance data exportable.", "3": "Cooperative-level traceability. Individual farmer contribution recorded but not traced through processing. Basic batch tracking.", "2": "Regional origin tracking only. No farm-level traceability. Aggregate batch records.", "1": "No provenance tracking. Origin claims based on paper certificates only." } }, { "id": "SC-FAIR-PRICE", "name": "Fair Price Verification & Payment Transparency", "description": "The system verifies that farmers receive fair prices and that premium payments (fair trade, organic) actually reach the producer. Price transparency is the core value proposition. Farmers must be able to see and verify what they were paid relative to market and premium rates.", "weight": 0.25, "ratingGuide": { "5": "Records farmgate price paid to each farmer. Compares against market reference prices and fair trade minimum prices. Premium payment tracking (how much of buyer premium reaches farmer). Farmer-facing price transparency (SMS or app notification of payment breakdown). Historical price analytics.", "4": "Price recording per farmer. Market price comparison. Premium tracking at cooperative level. Farmer payment notifications.", "3": "Average price paid recorded. Basic market comparison. Aggregate premium reporting.", "2": "Total payment to cooperative recorded. No individual farmer price tracking. No market comparison.", "1": "No price tracking or transparency." } }, { "id": "SC-CERTIFICATION", "name": "Certification & Standards Compliance", "description": "The system can support certification processes (Fair Trade, Organic, Rainforest Alliance, UTZ) and maintain compliance evidence. Certification is what opens premium markets. The system must make audit preparation effortless.", "weight": 0.2, "ratingGuide": { "5": "Pre-configured compliance checklists for major certifications. Internal audit tools. Non-conformance tracking and corrective action. Audit-ready documentation packages. Certification body data sharing (where supported). Group certification management for smallholders.", "4": "Certification compliance tracking. Audit documentation. Non-conformance recording. Group management. Major certification support.", "3": "Basic compliance checklists. Document storage for audit evidence. Manual audit preparation.", "2": "Certification status recorded. No compliance tracking tools. Manual audit process.", "1": "No certification management." } }, { "id": "SC-FARMER-ONBOARD", "name": "Farmer Registration & Accessibility", "description": "Smallholder farmers with limited literacy and technology can access meaningfully participate in the system. If the solution only works for tech-savvy cooperatives but not individual farmers, it fails its core purpose.", "weight": 0.15, "ratingGuide": { "5": "Low-literacy-friendly farmer registration (icon-based, voice input, photo ID). USSD/SMS interface for feature phone users. Works in low/no connectivity. Available in local languages. Training embedded in workflow. Farmer can check their own records via basic phone.", "4": "Simple mobile app for farmer data capture. SMS notifications. Offline capable. Multi-language. Community facilitator workflow.", "3": "Mobile-friendly registration by cooperative staff. Farmer-facing SMS for key information. Basic language support.", "2": "Desktop-based registration. Cooperative-managed. No farmer-facing interface.", "1": "Technical system accessible only to buyers or export offices. No farmer participation." } }, { "id": "SC-MARKET-CONNECT", "name": "Market Linkage & Buyer Discovery", "description": "The system helps connect verified smallholders to buyers willing to pay premiums. Traceability without market access delivers no value to farmers.", "weight": 0.1, "ratingGuide": { "5": "Buyer marketplace or matchmaking feature. Verified farmer profiles visible to registered buyers. Order management and contract facilitation. Trade finance or pre-payment support. Market information service (prices, demand signals) for farmers.", "4": "Buyer discovery portal. Farmer profiles with production data. Basic order management. Market price information.", "3": "Farmer data exportable for buyer due diligence. No active matchmaking. Manual order process.", "2": "System focused on traceability only. No buyer-facing features. Market access is external.", "1": "No market linkage. Pure record-keeping system." } } ], "procurement": { "marketMaturity": "nascent", "primaryMode": "integrator-led", "alternativeModes": [ "consortium" ], "reasoning": "Smallholder fair-trade verification is emerging; consortium and integrator-led pilots common.", "exampleProductCategories": [ "fair-trade-platform", "smallholder-traceability-rails" ], "partnerChannels": [], "lastReviewed": "2026-05-01" } }, { "id": "UC-D-068", "name": "Aid diversion detection and prevention", "category": "D", "subcategory": "Distribution Integrity", "description": "Spot and trace aid that goes missing between the warehouse and the beneficiary, and identify at which point in the chain it was lost.", "bCriteria": [ "B2", "B3", "B5", "B7" ], "requiredComponents": [ { "component": "tracking-platform", "description": "End-to-end commodity tracking system with tamper-evident handoff records" }, { "component": "qr-barcode", "description": "Unique item-level or batch-level identifiers for scan-based custody transfer" }, { "component": "last-mile-verification", "description": "Beneficiary-side confirmation that what was dispatched actually arrived" }, { "component": "audit-mechanism", "description": "Cryptographic audit trail linking dispatch, transit, handoff and receipt events" }, { "component": "anomaly-detection", "description": "Rule-based or pattern-based alerts for unusual diversion signals (short deliveries, missing scans, geo-outliers)" } ], "conditionalComponents": [ { "component": "identity-verification", "condition": "If beneficiaries must be individually identified to confirm they received their entitlement" }, { "component": "biometric-capture", "condition": "If thumbprint or facial verification is required at handover to deter collusion" }, { "component": "iot-sensors", "condition": "If GPS/telematics on vehicles or containers is required to detect route deviation" }, { "component": "smart-contracts", "condition": "If funder disbursement or partner payment is tied to confirmed non-diverted delivery" } ], "crossCategoryDependencies": [ "UC-B-024 for beneficiary identity verification when per-recipient confirmation is required", "UC-D-063 for last-mile delivery verification \u2014 aid diversion detection sits on top of delivery verification", "UC-E-072 for programme outcome verification when diversion is being investigated retrospectively" ], "p2TriggerConditions": { "description": "Activated when P2 indicates losses/diversion in the supply chain, recurring fraud or diversion incidents, or distribution programmes at scale with multiple handoffs.", "rangeSignals": [ "supplyChainFailurePoint == last-mile-diversion", "supplyChainProblemRate >= 5-15%", "visibilityGaps includes field-distribution OR partner-handover", "qualityIncidents >= recurring" ] }, "contextFieldsTemplate": [ { "field": "distributionVolume", "source": "P2 CatD Q1a", "description": "Monthly distribution transactions: scale driver" }, { "field": "partnerCount", "source": "P2 CatD Q1c", "description": "Number of intermediaries between dispatch and beneficiary" }, { "field": "problemRate", "source": "P2 CatD Q1b", "description": "Share of distributions with known problems (loss, diversion, substitution)" }, { "field": "failurePoint", "source": "P2 CatD Q8", "description": "Single biggest point of failure in the supply chain" }, { "field": "visibilityGaps", "source": "P2 CatD Q6", "description": "Where in the chain the org currently loses sight of goods" } ], "implementationComplexity": "medium-high", "examples": { "note": "Diversion detection through immutable handoff records and anomaly surfacing; precedent in cash-programming fraud controls and humanitarian commodity audits.", "references": [ { "name": "WFP Building Blocks", "url": "https://innovation.wfp.org/project/building-blocks", "solved": "Cash-based transfers with cryptographic redemption records, which eliminated duplicate and fraudulent beneficiary claims at scale." }, { "name": "USAID OIG audits of aid diversion", "url": "https://oig.usaid.gov", "solved": "Documented pattern analysis of diversion across multi-partner programmes, which motivates the move to verifiable handoff chains." }, { "name": "UNHCR Cash-Based Interventions policy", "url": "https://www.unhcr.org/what-we-do/respond-emergencies/cash-based-interventions", "solved": "Standardised verification requirements for multi-partner delivery; blockchain-compatible audit model." } ] }, "solutionQuestions": [ { "id": "diversion-detection-trigger", "type": "select", "options": [ { "label": "Post-hoc audits only (sample and investigate)", "value": "post-hoc" }, { "label": "Distribution-day reconciliation (same-day exception review)", "value": "same-day" }, { "label": "Real-time anomaly alerts during distribution", "value": "real-time" } ], "propertyMapping": { "post-hoc": { "technologies": [ "Audit sampling platform", "Reconciliation dashboard" ], "technologyProperties": { "detectionLatency": "weeks-to-months", "deterrentEffect": "moderate", "operationalOverhead": "low", "investigationCost": "high" } }, "same-day": { "technologies": [ "Reconciliation platform", "Exception workflow" ], "technologyProperties": { "detectionLatency": "hours-to-days", "deterrentEffect": "high", "operationalOverhead": "moderate", "investigationCost": "moderate" } }, "real-time": { "technologies": [ "Event-streaming platform", "Anomaly rules engine", "Immutable handoff ledger" ], "technologyProperties": { "detectionLatency": "seconds-to-minutes", "deterrentEffect": "very-high", "operationalOverhead": "high", "investigationCost": "low" } } }, "prefillFrom": null, "briefSection": "Detection strategy", "text": "When should diversion be detected, after the fact, during distribution, or in real time?", "ngoText": "When should diversion be detected, after the fact, during distribution, or in real time?" }, { "id": "item-tracking-method", "type": "select", "options": [ { "label": "QR codes printed on items or packaging", "value": "qr-codes" }, { "label": "NFC tags embedded in items", "value": "nfc-tags" }, { "label": "Barcode labels with batch scanning", "value": "barcode" }, { "label": "Mixed: QR for high-value items, barcode for bulk", "value": "mixed" } ], "propertyMapping": { "qr-codes": { "technologies": [ "QR code generation service", "QR/barcode scanning app", "Item-level tracking ledger" ], "technologyProperties": { "trackingGranularity": "Per-item or per-batch", "scanMethod": "Mobile phone camera / QR scanner", "offlineCapable": "Yes \u2014 scan and sync when connected" } }, "nfc-tags": { "technologies": [ "NFC tag provisioning", "NFC reader integration", "Item-level tracking ledger" ], "technologyProperties": { "trackingGranularity": "Per-item", "scanMethod": "NFC-enabled device", "offlineCapable": "Yes \u2014 NFC works offline" } }, "barcode": { "technologies": [ "Barcode generation service", "QR/barcode scanning app", "Batch tracking ledger" ], "technologyProperties": { "trackingGranularity": "Per-batch", "scanMethod": "Barcode scanner / mobile camera", "offlineCapable": "Yes \u2014 scan and sync" } }, "mixed": { "technologies": [ "QR code generation service", "Barcode generation service", "QR/barcode scanning app", "Multi-level tracking ledger" ], "technologyProperties": { "trackingGranularity": "Mixed \u2014 item-level for high-value, batch for bulk", "scanMethod": "Mobile phone camera / scanner", "offlineCapable": "Yes" } } }, "prefillFrom": null, "briefSection": "Item tracking", "text": "How will physical items be tracked and scanned in the field?", "ngoText": "How will physical items be tracked and scanned in the field?" }, { "id": "fraud-prevention-mechanism", "type": "select", "options": [ { "label": "Documentation and random spot checks", "value": "spot-checks" }, { "label": "Digital verification with supervisor review", "value": "digital-review" }, { "label": "Real-time monitoring with digital ledger confirmation", "value": "blockchain-monitoring" } ], "propertyMapping": { "spot-checks": { "technologies": [ "Audit sampling system", "Verification checklist" ], "technologyProperties": { "detectionRate": "moderate", "deterrentEffect": "moderate", "costPerVerification": "low", "administrativeOverhead": "moderate" } }, "digital-review": { "technologies": [ "Digital verification platform", "Supervisory review system" ], "technologyProperties": { "detectionRate": "high", "deterrentEffect": "high", "costPerVerification": "moderate", "administrativeOverhead": "low" } }, "blockchain-monitoring": { "technologies": [ "Blockchain confirmation system", "Real-time audit platform" ], "technologyProperties": { "detectionRate": "very-high", "deterrentEffect": "very-high", "costPerVerification": "high", "administrativeOverhead": "minimal" } } }, "prefillFrom": null, "briefSection": "Quality assurance", "text": "What approach would you need for preventing and detecting supply chain fraud?", "ngoText": "What approach would you need for preventing and detecting supply chain fraud?" }, { "id": "last-mile-stakeholders", "type": "select", "options": [ { "label": "Internal only (1\u20132 teams)", "value": "internal" }, { "label": "Internal + 1\u20133 external partners", "value": "few-external" }, { "label": "Multiple external stakeholders (4\u201310)", "value": "multi-external" }, { "label": "Ecosystem-wide (donors, partners, beneficiaries, regulators)", "value": "ecosystem" } ], "propertyMapping": { "internal": { "technologies": [ "Private ledger" ], "technologyProperties": { "accessControl": "Simple role-based", "networkType": "Private" } }, "few-external": { "technologies": [ "Permissioned network", "Selective data sharing" ], "technologyProperties": { "accessControl": "Partner-level permissions", "networkType": "Consortium" } }, "multi-external": { "technologies": [ "Permissioned network", "Multi-party access layer" ], "technologyProperties": { "accessControl": "Granular role-based", "networkType": "Consortium" } }, "ecosystem": { "technologies": [ "Permissioned public network", "Data marketplace" ], "technologyProperties": { "accessControl": "Multi-tier with public layer", "networkType": "Hybrid public-private" } } }, "prefillFrom": null, "briefSection": "Governance and access", "text": "How many distinct parties need visibility into the distribution data?", "ngoText": "How many distinct parties need visibility into the distribution data?" }, { "id": "diversion-consequence-model", "type": "select", "options": [ { "label": "Internal reporting and policy review", "value": "internal-report" }, { "label": "Partner contract penalties (withheld payment, termination)", "value": "partner-penalty" }, { "label": "Automated disbursement freeze until remediation verified", "value": "auto-freeze" }, { "label": "Referral to donor / external investigator", "value": "external-referral" } ], "propertyMapping": { "internal-report": { "technologies": [ "Incident log", "Management reporting" ], "technologyProperties": { "enforcementStrength": "weak", "automationLevel": "none", "recoveryRate": "low" } }, "partner-penalty": { "technologies": [ "Contract management system", "Payment hold workflow" ], "technologyProperties": { "enforcementStrength": "moderate", "automationLevel": "partial", "recoveryRate": "moderate" } }, "auto-freeze": { "technologies": [ "Smart contract disbursement gate", "Remediation evidence ledger" ], "technologyProperties": { "enforcementStrength": "strong", "automationLevel": "full", "recoveryRate": "high" } }, "external-referral": { "technologies": [ "Case management platform", "Evidence chain-of-custody ledger" ], "technologyProperties": { "enforcementStrength": "strong", "automationLevel": "partial", "recoveryRate": "variable" } } }, "prefillFrom": null, "briefSection": "Consequences and enforcement", "text": "What should happen when diversion is detected?", "ngoText": "What should happen when diversion is detected?" } ], "complexityFactors": { "relationships": 3, "operationalChange": 3, "dataCompliance": 2 }, "suggestedCriteria": [ { "id": "SC-HANDOFF-INTEGRITY", "name": "Custody Handoff Integrity", "description": "This measures how reliably the system records each change of custody (warehouse \u2192 transporter \u2192 partner \u2192 distribution point \u2192 beneficiary) so that tampering is detectable. Diversion almost always happens at an unobserved handoff.", "weight": 0.3, "ratingGuide": { "5": "Cryptographically signed handoff at every custody change with party identity + timestamp + GPS + item-level match. Replay-resistant. Offline-capable with tamper-evident sync. Any missing handoff blocks downstream events.", "4": "Signed handoffs at every custody change. Timestamp + GPS + item-level match. Sync on reconnect.", "3": "Digital handoff records at major custody changes. Item counts match at each step but not item-level.", "2": "Paper sign-offs digitised after the fact. Handoffs may be reconstructed post-hoc.", "1": "No systematic custody tracking. Dispatch and delivery events logged, handoffs are not." } }, { "id": "SC-ANOMALY-DETECTION", "name": "Diversion Anomaly Surfacing", "description": "This measures how quickly and reliably the system surfaces patterns that look like diversion (short deliveries, missing scans, time/geo anomalies, recipient duplication). Detection latency is a direct driver of loss magnitude.", "weight": 0.25, "ratingGuide": { "5": "Real-time rule engine running on the handoff stream. Configurable thresholds per programme. Cross-distribution pattern detection (same beneficiary, same transporter, same day clusters). Automated case creation for investigation.", "4": "Daily anomaly reports with configurable rules. Exception queue for investigators. Geo-outlier and short-delivery detection.", "3": "Weekly summary reports. Manual review required. Basic threshold rules (delivery count vs. plan).", "2": "Ad-hoc analysis when something is suspected. No standing detection.", "1": "No anomaly detection. Diversion only surfaces through complaints or external audit." } }, { "id": "SC-PARTNER-ACCOUNTABILITY", "name": "Partner Accountability Framework", "description": "The system can attribute diversion events to specific parties in the chain, and does it support contractual or legal consequences. Deterrence requires that diversion carries consequences traceable to the responsible party.", "weight": 0.2, "ratingGuide": { "5": "Per-party accountability ledger. Partner-specific diversion rates and trends visible in consortium dashboards. Contractual triggers (payment holds, termination) wired to ledger events. Evidence packages auto-generated for external investigation.", "4": "Per-party diversion metrics. Manual contract-trigger workflow. Evidence assembly supported.", "3": "Aggregate diversion metrics by programme. Partner attribution requires investigation.", "2": "Incident logs attribute to individuals but not system-wide.", "1": "No attribution framework. Diversion is known to occur but not to whom." } }, { "id": "SC-BENEFICIARY-FEEDBACK", "name": "Beneficiary Feedback Channel", "description": "The system provides a trusted, retaliation-resistant way for beneficiaries to report short deliveries or diversion. Beneficiary testimony is often the only ground truth, but requires safe reporting channels.", "weight": 0.15, "ratingGuide": { "5": "Anonymous and authenticated reporting channels with cryptographic linkage to specific distributions. Beneficiary testimony surfaces in anomaly review. Retaliation protections and independent investigation workflow.", "4": "Authenticated feedback linked to distributions. Basic retaliation protections. Feedback enters anomaly queue.", "3": "Generic feedback channel (hotline, app). Not linked to specific distributions.", "2": "Informal feedback through partners. Not systematised.", "1": "No beneficiary feedback mechanism." } }, { "id": "SC-REMEDIATION-WORKFLOW", "name": "Remediation and Recovery Workflow", "description": "Once diversion is detected, the system supports recovery of diverted goods, replacement delivery to affected beneficiaries, and closure of the incident. Detection without remediation is theatre.", "weight": 0.1, "ratingGuide": { "5": "End-to-end remediation workflow: investigation \u2192 finding \u2192 consequence enforcement \u2192 replacement delivery \u2192 affected-beneficiary notification \u2192 closure. Linked to partner accountability and beneficiary channels. Metrics on recovery rate and time-to-remediate.", "4": "Case management for remediation. Replacement delivery supported. Basic metrics.", "3": "Incidents recorded with outcomes. Remediation is manual and inconsistent.", "2": "Incident logging only. Follow-through is programme-specific.", "1": "No remediation workflow. Detected diversion typically ends at a report." } } ], "procurement": { "marketMaturity": "emerging", "primaryMode": "integrator-led", "alternativeModes": [ "rfq" ], "reasoning": "Aid diversion detection blends supply chain and forensic tooling.", "exampleProductCategories": [ "aid-diversion-detection", "forensic-tracking-platform" ], "partnerChannels": [], "lastReviewed": "2026-05-01" } }, { "id": "UC-D-069", "name": "Beneficiary receipt confirmation (proof of delivery)", "category": "D", "subcategory": "Delivery Verification", "description": "Record that a named person received what was meant for them, in a form donors accept as proof before they release the next payment.", "bCriteria": [ "B2", "B3", "B5", "B6" ], "requiredComponents": [ { "component": "last-mile-verification", "description": "Bidirectional confirmation: beneficiary attests receipt, record propagates up the chain" }, { "component": "identity-verification", "description": "Links receipt to a registered beneficiary so the attestation is attributable" }, { "component": "mobile-wallet", "description": "Beneficiary-side store of receipt (so the beneficiary holds a verifiable copy, not just the org)" }, { "component": "qr-barcode", "description": "Scannable delivery-event code tying receipt to a specific dispatch event" }, { "component": "audit-mechanism", "description": "Cryptographic audit trail linking dispatch \u2192 handoff \u2192 attested receipt" } ], "conditionalComponents": [ { "component": "biometric-capture", "condition": "If thumbprint/face verification is required at receipt to prevent proxy collection" }, { "component": "sms-fallback", "condition": "If feature-phone beneficiaries need to confirm via SMS or USSD" }, { "component": "smart-contracts", "condition": "If beneficiary confirmation is the trigger for donor tranche release or partner payment" } ], "crossCategoryDependencies": [ "UC-B-024 for beneficiary identity verification \u2014 receipt is only trustable if the signer's identity is established", "UC-D-063 for org-side dispatch and delivery records \u2014 receipt confirmation sits on top of delivery verification", "UC-D-068 for aid diversion detection \u2014 attested receipts are the primary signal for diversion anomaly detection" ], "p2TriggerConditions": { "description": "Activated when P2 shows beneficiary-verification gaps, donor requirements for proof of receipt, or tranche-based funding tied to confirmed delivery.", "rangeSignals": [ "beneficiaryVerification >= important", "supplyChainFailurePoint == last-mile-diversion", "supplyChainProblemRate >= 5-15%", "donorReceiptRequirement == required" ] }, "contextFieldsTemplate": [ { "field": "beneficiaries", "source": "P2 programme scale", "description": "Distributions per month requiring beneficiary-attested receipt" }, { "field": "locations", "source": "P0 operations + P4", "description": "Distribution locations and connectivity profile" }, { "field": "identityGranularity", "source": "P2 CatB + CatD", "description": "Level of beneficiary identity resolution available for attestation" }, { "field": "receiptTrigger", "source": "P2 CatD + donor context", "description": "Whether receipt triggers further fund flow or is informational" }, { "field": "privacyConstraints", "source": "P0 + donor context", "description": "Beneficiary-protection constraints (vulnerable populations, conflict settings)" } ], "implementationComplexity": "medium", "examples": { "note": "Beneficiary-attested proof of delivery with cryptographically linked receipts; precedent in biometric beneficiary management and mobile-money delivery confirmation.", "references": [ { "name": "WFP SCOPE beneficiary management platform", "url": "https://usermanual.scope.wfp.org", "solved": "Beneficiary-side attestation linked to identity records at scale, a model for receipt provenance with privacy controls." }, { "name": "GiveDirectly \u2014 mobile cash delivery confirmation", "url": "https://www.givedirectly.org", "solved": "Beneficiary-side mobile confirmation of delivered cash; demonstrates SMS/app receipt pathways that can be cryptographically anchored." }, { "name": "Mercy Corps delivery verification programmes", "url": "https://www.mercycorps.org", "solved": "Field-level delivery verification systems with beneficiary attestation for emergency programming." } ] }, "solutionQuestions": [ { "id": "receipt-channel", "type": "select", "options": [ { "label": "Paper receipt with signature/thumbprint", "value": "paper" }, { "label": "SMS or USSD confirmation from beneficiary", "value": "sms" }, { "label": "Mobile app with beneficiary login", "value": "mobile-app" }, { "label": "Mixed: paper as fallback, digital as default", "value": "mixed" } ], "propertyMapping": { "paper": { "technologies": [ "Paper receipt forms", "Digitisation pipeline (scan and transcribe)" ], "technologyProperties": { "beneficiaryBarrier": "low", "attestationLatency": "days", "tamperRisk": "high", "privacyProfile": "physical-only" } }, "sms": { "technologies": [ "SMS gateway", "USSD menu platform", "Receipt ingestion service" ], "technologyProperties": { "beneficiaryBarrier": "low", "attestationLatency": "minutes", "tamperRisk": "moderate", "privacyProfile": "carrier-mediated" } }, "mobile-app": { "technologies": [ "Beneficiary mobile app", "Offline-capable receipt store", "Sync service" ], "technologyProperties": { "beneficiaryBarrier": "moderate", "attestationLatency": "seconds", "tamperRisk": "low", "privacyProfile": "app-mediated with local keys" } }, "mixed": { "technologies": [ "Paper fallback", "SMS gateway", "Mobile app", "Unified receipt ingestion" ], "technologyProperties": { "beneficiaryBarrier": "adaptive", "attestationLatency": "varies", "tamperRisk": "mixed", "privacyProfile": "mixed" } } }, "prefillFrom": null, "briefSection": "Attestation channel", "text": "How will beneficiaries confirm receipt of what they were sent?", "ngoText": "How will beneficiaries confirm receipt of what they were sent?" }, { "id": "receipt-cryptographic-model", "type": "select", "options": [ { "label": "Plain record: timestamp and ID, no cryptographic binding", "value": "plain" }, { "label": "Signed record: org signs the receipt after capture", "value": "org-signed" }, { "label": "Beneficiary-signed: beneficiary's key signs the attestation", "value": "beneficiary-signed" }, { "label": "Anchored: hash of receipt batch committed to a shared ledger", "value": "anchored" } ], "propertyMapping": { "plain": { "technologies": [ "Receipt database" ], "technologyProperties": { "tamperEvidence": "none", "nonRepudiation": "weak", "verificationCost": "low", "beneficiaryAgency": "none" } }, "org-signed": { "technologies": [ "Signing service (org-held keys)", "Receipt database" ], "technologyProperties": { "tamperEvidence": "moderate", "nonRepudiation": "org-side only", "verificationCost": "low", "beneficiaryAgency": "none" } }, "beneficiary-signed": { "technologies": [ "Beneficiary key provisioning", "On-device signing", "Receipt database" ], "technologyProperties": { "tamperEvidence": "strong", "nonRepudiation": "mutual", "verificationCost": "moderate", "beneficiaryAgency": "high" } }, "anchored": { "technologies": [ "Receipt batch hasher", "Ledger commit service", "Merkle inclusion proof API" ], "technologyProperties": { "tamperEvidence": "very-strong", "nonRepudiation": "verifiable by any party", "verificationCost": "moderate", "beneficiaryAgency": "medium" } } }, "prefillFrom": null, "briefSection": "Cryptographic binding", "text": "How strongly should the receipt be cryptographically bound so that it cannot be fabricated or repudiated later?", "ngoText": "How strongly should the receipt be cryptographically bound so that it cannot be fabricated or repudiated later?" }, { "id": "delivery-verification-method", "type": "select", "options": [ { "label": "Signature or thumbprint on receipt", "value": "signature-receipt" }, { "label": "QR code scanning by beneficiary", "value": "qr-scanning" }, { "label": "Biometric verification with photo", "value": "biometric-photo" } ], "propertyMapping": { "signature-receipt": { "technologies": [ "Digital signature platform", "Receipt documentation system" ], "technologyProperties": { "verificationAccuracy": "moderate", "fraudRisk": "moderate", "technicalComplexity": "low", "beneficiaryBarrier": "low" } }, "qr-scanning": { "technologies": [ "QR code platform", "Mobile scanning application" ], "technologyProperties": { "verificationAccuracy": "high", "fraudRisk": "low", "technicalComplexity": "moderate", "beneficiaryBarrier": "moderate" } }, "biometric-photo": { "technologies": [ "Biometric verification system", "Photo documentation platform" ], "technologyProperties": { "verificationAccuracy": "very-high", "fraudRisk": "very-low", "technicalComplexity": "high", "beneficiaryBarrier": "high" } } }, "prefillFrom": null, "briefSection": "Verification and authentication", "text": "Which verification method should be used for delivery?", "ngoText": "Which verification method should be used for delivery?" }, { "id": "beneficiary-id-system", "type": "select", "options": [ { "label": "Basic list with name and location", "value": "basic-list" }, { "label": "Digital registry with unique ID", "value": "digital-id" }, { "label": "Biometric registry with multi-modal data", "value": "biometric-registry" } ], "propertyMapping": { "basic-list": { "technologies": [ "Beneficiary list system", "Paper or spreadsheet registry" ], "technologyProperties": { "uniqueIdentifier": "none", "dataFields": "name-location-household", "updateFrequency": "static", "scalability": "limited" } }, "digital-id": { "technologies": [ "Digital beneficiary registry", "Unique ID generator" ], "technologyProperties": { "uniqueIdentifier": "sequential-or-random", "dataFields": "comprehensive", "updateFrequency": "periodic", "scalability": "good" } }, "biometric-registry": { "technologies": [ "Biometric registration system", "Multi-modal identity platform" ], "technologyProperties": { "uniqueIdentifier": "biometric-based", "dataFields": "comprehensive-biometric", "updateFrequency": "continuous", "scalability": "excellent" } } }, "prefillFrom": null, "briefSection": "Beneficiary identification", "text": "How are beneficiaries identified and registered?", "ngoText": "How are beneficiaries identified and registered?" }, { "id": "receipt-consequence", "type": "select", "options": [ { "label": "Informational only: receipt closes the delivery record", "value": "informational" }, { "label": "Reporting driver: receipts feed donor reports and M&E", "value": "reporting" }, { "label": "Partner payment trigger: receipt releases partner payment", "value": "partner-payment" }, { "label": "Donor tranche trigger: receipt releases next donor disbursement", "value": "donor-tranche" } ], "propertyMapping": { "informational": { "technologies": [ "Receipt log", "Reporting dashboard" ], "technologyProperties": { "enforcementStrength": "none", "automationLevel": "none", "settlementFinality": "not-applicable" } }, "reporting": { "technologies": [ "Receipt aggregation service", "Donor reporting pipeline" ], "technologyProperties": { "enforcementStrength": "weak", "automationLevel": "partial", "settlementFinality": "weak" } }, "partner-payment": { "technologies": [ "Payment workflow", "Receipt-gate logic", "Contract management" ], "technologyProperties": { "enforcementStrength": "moderate", "automationLevel": "partial", "settlementFinality": "moderate" } }, "donor-tranche": { "technologies": [ "Smart-contract tranche gate", "Verifiable receipt proof", "Disbursement workflow" ], "technologyProperties": { "enforcementStrength": "strong", "automationLevel": "full", "settlementFinality": "strong" } } }, "prefillFrom": null, "briefSection": "Consequence of the receipt", "text": "What happens once a beneficiary-attested receipt is recorded?", "ngoText": "What happens once a beneficiary-attested receipt is recorded?" } ], "complexityFactors": { "relationships": 3, "operationalChange": 3, "dataCompliance": 3 }, "suggestedCriteria": [ { "id": "SC-ATTESTATION-AUTHENTICITY", "name": "Beneficiary Attestation Authenticity", "description": "Can the system prove that the confirmation came from the registered beneficiary (not a proxy, not fabricated) at the time and place claimed?", "weight": 0.3, "ratingGuide": { "5": "Beneficiary-held key signs the receipt at capture time with tamper-evident GPS + time + identity link; replay-resistant; offline-capable.", "4": "On-device cryptographic attestation tied to identity record. Strong but reliant on org-provisioned keys.", "3": "Digital receipt tied to beneficiary ID with org signing. Good, but attestation is mediated by the org.", "2": "Paper/manual receipt digitised after capture. Attribution plausible but not cryptographically proven.", "1": "No reliable linkage from receipt to specific beneficiary." } }, { "id": "SC-RECEIPT-INTEGRITY", "name": "Receipt Integrity Over Time", "description": "Once created, can a receipt be tampered with, deleted or back-dated by any party in the chain?", "weight": 0.25, "ratingGuide": { "5": "Receipts anchored to a shared ledger with Merkle proofs; tampering is detectable by any external verifier without access to the org's systems.", "4": "Immutable append-only receipt store with signed entries; tampering by non-privileged parties infeasible.", "3": "Database with audit logs; tampering is detectable through forensic audit but not prevented in-system.", "2": "Database with routine backups; tampering possible between backups.", "1": "Receipts can be edited without audit trail." } }, { "id": "SC-BENEFICIARY-PRIVACY", "name": "Beneficiary Privacy and Data Minimisation", "description": "Does the receipt carry only what's required, with selective-disclosure or data-minimisation protections for vulnerable beneficiaries?", "weight": 0.2, "ratingGuide": { "5": "Zero-knowledge or selective-disclosure receipts; only the claim 'beneficiary X of cohort Y received entitlement' is publicly verifiable, identity is hidden from non-privileged verifiers.", "4": "Receipts use pseudonymous IDs with privilege-separated identity resolution; default view exposes no PII.", "3": "Receipts carry minimal identifying info with access controls.", "2": "Receipts carry full identifying info but within an access-controlled system.", "1": "Receipts expose identifying info by default to all parties in the chain." } }, { "id": "SC-SETTLEMENT-FINALITY", "name": "Settlement Finality of the Receipt", "description": "How strongly does the system prevent reversal, duplication or replay of a confirmed receipt, especially when that receipt triggers further fund flow?", "weight": 0.15, "ratingGuide": { "5": "Smart-contract enforced: confirmed receipt is single-use, atomically linked to tranche release, reversals require multi-party consensus.", "4": "Receipt is single-use in the system; reversals require supervisor approval with audit log.", "3": "Receipt is single-use but enforcement is administrative.", "2": "Duplicate/replay possible but detectable after the fact.", "1": "No enforcement \u2014 receipts can be replayed or reversed silently." } }, { "id": "SC-BENEFICIARY-ACCESS", "name": "Beneficiary Access to Their Own Receipts", "description": "Beneficiaries can see, hold and demonstrate receipt of what they received, independent of the org. This is a rights/agency criterion alongside audit.", "weight": 0.1, "ratingGuide": { "5": "Beneficiary holds a cryptographic copy in a wallet or paper equivalent; can independently prove receipt to third parties.", "4": "Beneficiary receives a copy (SMS, app, printed) that can be verified against the org's ledger.", "3": "Beneficiary receives a physical receipt; verification requires the org.", "2": "Beneficiary has no retained copy but can request one.", "1": "No beneficiary-side record. Only the org holds proof." } } ], "procurement": { "marketMaturity": "emerging", "primaryMode": "rfq", "alternativeModes": [ "off-the-shelf" ], "reasoning": "Beneficiary receipt confirmation has product market in cash and voucher verticals.", "exampleProductCategories": [ "proof-of-delivery-platform", "beneficiary-confirmation-saas" ], "partnerChannels": [], "lastReviewed": "2026-05-01" } }, { "id": "UC-D-070", "name": "Conflict mineral and material tracking", "category": "D", "subcategory": "Supply Chain Compliance", "description": "Trace materials back to their source, so donors and regulators can see they did not come from a conflict zone or a banned supplier.", "bCriteria": [ "B1", "B3", "B6", "B7" ], "requiredComponents": [ { "component": "provenance-ledger", "description": "Shared origin record for materials traversing mine/smelter/refiner/manufacturer stages" }, { "component": "qr-barcode", "description": "Batch-level or lot-level identifiers tying physical material to ledger entries" }, { "component": "identity-verification", "description": "Verified identity of origin sites (mines, cooperatives) and intermediate processors (smelters)" }, { "component": "audit-mechanism", "description": "Cryptographic audit trail linking origin claims \u2192 chain-of-custody \u2192 end-use certification" }, { "component": "compliance-rules-engine", "description": "Policy layer encoding 3TG / EU conflict-minerals / ESG rules that evaluate provenance claims against regulatory schemas" } ], "conditionalComponents": [ { "component": "iot-sensors", "condition": "If geo-tagging of extraction sites or transport corridors is required" }, { "component": "smart-contracts", "condition": "If payment to suppliers is gated on verified non-conflict origin" }, { "component": "privacy-tech", "condition": "If supplier identities must be protected from public view while still allowing compliance verification" }, { "component": "third-party-attestation", "condition": "If independent audit bodies (e.g. ITSCI, RMI-audited smelter programme) must counter-sign provenance claims" } ], "crossCategoryDependencies": [ "UC-D-057 for donated goods provenance \u2014 shared provenance primitives", "UC-D-058 for in-kind donation tracking \u2014 in-kind donations of equipment carry conflict-mineral exposure", "UC-F-086 for ESG / ethical-sourcing donor reporting \u2014 compliance evidence flows into donor reports" ], "p2TriggerConditions": { "description": "Activated when P2 indicates procurement exposure to conflict-mineral regulation, ESG reporting pressure from donors, or programming in artisanal mining communities.", "rangeSignals": [ "procurementCategories includes electronics OR vehicles OR solar-equipment", "donorEsgRequirement >= required", "programmingContext includes artisanal-mining-communities", "supplierTransparency <= weak" ] }, "contextFieldsTemplate": [ { "field": "materialScope", "source": "P0 procurement + P2", "description": "Materials in scope: 3TG (tin, tantalum, tungsten, gold), cobalt, lithium, broader ESG-sensitive materials" }, { "field": "tierDepth", "source": "P0 procurement", "description": "How far upstream the traceability must reach (smelter / mine / community)" }, { "field": "regulatoryJurisdiction", "source": "P0 legal context", "description": "Which regulatory regimes apply (EU Regulation 2017/821, Dodd-Frank s1502, UK ESG disclosure)" }, { "field": "supplierCount", "source": "P2 procurement scale", "description": "Number of distinct tier-1 suppliers with conflict-mineral exposure" }, { "field": "evidenceCurrentState", "source": "P0 + P2", "description": "Current evidence model: self-attestation, third-party audit, no evidence" } ], "implementationComplexity": "high", "examples": { "note": "Multi-tier supply-chain traceability with regulatory compliance overlays; strong precedent in the mining and electronics industry, less mature in humanitarian procurement.", "references": [ { "name": "Responsible Minerals Initiative (RMI)", "url": "https://www.responsiblemineralsinitiative.org", "solved": "Industry-standard smelter-level audit and certification framework, which defines what 'conflict-free' provenance evidence looks like." }, { "name": "EU Conflict Minerals Regulation (2017/821)", "url": "https://policy.trade.ec.europa.eu/development-and-sustainability/conflict-minerals-regulation_en", "solved": "Regulatory schema for 3TG importer due diligence, which defines the compliance rules a programmable-compliance layer must encode." }, { "name": "ICGLR Regional Certification Mechanism", "url": "https://icglrcertification.org", "solved": "Regional certification for minerals from the Great Lakes region, which demonstrates multi-state provenance ledger with third-party attestation." }, { "name": "IBM \u2014 responsible sourcing and supply-chain traceability", "url": "https://www.ibm.com", "solved": "Reference blockchain implementations for minerals provenance (notably cobalt), which demonstrate commercial feasibility of multi-party ledgers for regulated commodities." } ] }, "solutionQuestions": [ { "id": "material-scope", "type": "select", "options": [ { "label": "3TG only (tin, tantalum, tungsten, gold)", "value": "3tg" }, { "label": "3TG + cobalt", "value": "3tg-cobalt" }, { "label": "Broader ESG-sensitive materials (lithium, rare earths, timber, textiles)", "value": "broad-esg" }, { "label": "Single-material focus (programme-specific)", "value": "single" } ], "propertyMapping": { "3tg": { "technologies": [ "3TG provenance schema", "RMI smelter list integration" ], "technologyProperties": { "schemaComplexity": "moderate", "ecosystemMaturity": "high", "auditCost": "moderate" } }, "3tg-cobalt": { "technologies": [ "3TG + cobalt schema", "Extended smelter audit integration" ], "technologyProperties": { "schemaComplexity": "moderate-high", "ecosystemMaturity": "moderate", "auditCost": "high" } }, "broad-esg": { "technologies": [ "Multi-material provenance schema", "Custom audit integrations" ], "technologyProperties": { "schemaComplexity": "high", "ecosystemMaturity": "emerging", "auditCost": "very-high" } }, "single": { "technologies": [ "Bespoke provenance schema" ], "technologyProperties": { "schemaComplexity": "low-moderate", "ecosystemMaturity": "varies", "auditCost": "varies" } } }, "prefillFrom": null, "briefSection": "Scope", "text": "Which materials fall within the scope of the traceability programme?", "ngoText": "Which materials fall within the scope of the traceability programme?" }, { "id": "tracing-depth", "type": "select", "options": [ { "label": "Smelter-level (smelter \u2192 downstream)", "value": "smelter" }, { "label": "Mine-to-smelter (origin-to-processor)", "value": "mine-to-smelter" }, { "label": "Mine-to-product (full end-to-end)", "value": "end-to-end" }, { "label": "Community-level (including artisanal producer cooperatives)", "value": "community" } ], "propertyMapping": { "smelter": { "technologies": [ "Smelter registry integration", "Downstream batch tracking" ], "technologyProperties": { "coverage": "partial", "dataCollectionCost": "moderate", "regulatoryMatch": "Dodd-Frank compatible" } }, "mine-to-smelter": { "technologies": [ "Mine registry", "Transport chain-of-custody", "Smelter integration" ], "technologyProperties": { "coverage": "strong", "dataCollectionCost": "high", "regulatoryMatch": "EU regulation compatible" } }, "end-to-end": { "technologies": [ "Full provenance ledger", "End-product BOM integration" ], "technologyProperties": { "coverage": "complete", "dataCollectionCost": "very-high", "regulatoryMatch": "ESG reporting compatible" } }, "community": { "technologies": [ "Producer cooperative registry", "Artisanal certification integration" ], "technologyProperties": { "coverage": "deep-at-origin", "dataCollectionCost": "high", "regulatoryMatch": "fair-trade compatible" } } }, "prefillFrom": null, "briefSection": "Traceability depth", "text": "How far upstream does the traceability need to extend?", "ngoText": "How far upstream does the traceability need to extend?" }, { "id": "compliance-gate", "type": "select", "options": [ { "label": "Reporting only: provenance data informs reports but doesn't block procurement", "value": "report-only" }, { "label": "Soft gate: non-compliance triggers review but not rejection", "value": "soft-gate" }, { "label": "Payment gate: payment withheld until compliance verified", "value": "payment-gate" }, { "label": "Hard gate: non-compliant material refused at receipt", "value": "hard-gate" } ], "propertyMapping": { "report-only": { "technologies": [ "Reporting pipeline", "Compliance dashboard" ], "technologyProperties": { "enforcement": "none", "automation": "partial", "risk": "regulatory exposure remains" } }, "soft-gate": { "technologies": [ "Exception workflow", "Compliance review queue" ], "technologyProperties": { "enforcement": "weak", "automation": "partial", "risk": "depends on review" } }, "payment-gate": { "technologies": [ "Smart-contract payment release", "Compliance-rules engine" ], "technologyProperties": { "enforcement": "strong", "automation": "full", "risk": "low" } }, "hard-gate": { "technologies": [ "Receipt-side compliance check", "Reject workflow", "Supplier feedback loop" ], "technologyProperties": { "enforcement": "very-strong", "automation": "full", "risk": "very-low but supply-chain disruption possible" } } }, "prefillFrom": null, "briefSection": "Compliance enforcement", "text": "What should happen when provenance fails compliance?", "ngoText": "What should happen when provenance fails compliance?" }, { "id": "evidence-model", "type": "select", "options": [ { "label": "Supplier self-attestation (declaration only)", "value": "self-attest" }, { "label": "Third-party audited (independent auditor counter-signs)", "value": "third-party" }, { "label": "Cryptographic attestation (signed provenance records at each tier)", "value": "crypto-attest" }, { "label": "Hybrid: supplier attestation anchored + third-party audit", "value": "hybrid" } ], "propertyMapping": { "self-attest": { "technologies": [ "Supplier declaration portal", "Attestation ledger" ], "technologyProperties": { "trustLevel": "weak", "costPerAttestation": "very-low", "tamperResistance": "weak" } }, "third-party": { "technologies": [ "Auditor integration", "Attestation registry", "Audit finding workflow" ], "technologyProperties": { "trustLevel": "strong", "costPerAttestation": "high", "tamperResistance": "strong (audit-gated)" } }, "crypto-attest": { "technologies": [ "Per-tier signing keys", "Provenance ledger", "Signature verification service" ], "technologyProperties": { "trustLevel": "very-strong-in-technical-terms", "costPerAttestation": "moderate", "tamperResistance": "very-strong" } }, "hybrid": { "technologies": [ "Per-tier signing", "Auditor counter-sign integration", "Anchored provenance ledger" ], "technologyProperties": { "trustLevel": "very-strong", "costPerAttestation": "high", "tamperResistance": "very-strong" } } }, "prefillFrom": null, "briefSection": "Evidence model", "text": "What evidence is required to back a provenance claim?", "ngoText": "What evidence is required to back a provenance claim?" }, { "id": "supplier-disclosure-model", "type": "select", "options": [ { "label": "Full public disclosure of suppliers and origins", "value": "public" }, { "label": "Disclosed to donor/regulator only under NDA", "value": "nda" }, { "label": "Selective disclosure: claims verifiable, identities hidden", "value": "selective" }, { "label": "Internal only, not disclosed outside the org", "value": "internal" } ], "propertyMapping": { "public": { "technologies": [ "Public provenance portal" ], "technologyProperties": { "verifiability": "very-high", "supplierRisk": "high", "privacyTech": "not required" } }, "nda": { "technologies": [ "Access-controlled portal", "NDA workflow" ], "technologyProperties": { "verifiability": "moderate", "supplierRisk": "low", "privacyTech": "standard access control" } }, "selective": { "technologies": [ "Selective-disclosure proofs", "Zero-knowledge attestation" ], "technologyProperties": { "verifiability": "high", "supplierRisk": "low", "privacyTech": "required" } }, "internal": { "technologies": [ "Internal system" ], "technologyProperties": { "verifiability": "low-external", "supplierRisk": "very-low", "privacyTech": "not required" } } }, "prefillFrom": null, "briefSection": "Disclosure model", "text": "Who needs to be able to verify provenance, and how much can be disclosed publicly?", "ngoText": "Who needs to be able to verify provenance, and how much can be disclosed publicly?" } ], "complexityFactors": { "relationships": 4, "operationalChange": 3, "dataCompliance": 4 }, "suggestedCriteria": [ { "id": "SC-ORIGIN-PROVENANCE", "name": "Strength of Origin Provenance", "description": "How reliably can the system prove the true origin of material down to mine or producer cooperative, resisting substitution and laundering?", "weight": 0.3, "ratingGuide": { "5": "Mine-level cryptographic attestation with geo-tagged capture at extraction and signed chain-of-custody at every handoff; laundering-resistant by construction.", "4": "Mine-to-smelter tracking with third-party audited mine registries; strong but not cryptographically end-to-end.", "3": "Smelter-level audits (RMI-style) with supplier self-attestation below smelter.", "2": "Supplier self-attestation only; spot audits.", "1": "No upstream visibility \u2014 reliance on supplier declaration." } }, { "id": "SC-REGULATORY-FIT", "name": "Regulatory Compliance Fit", "description": "How well does the evidence model fit specific regulatory schemas (EU 2017/821, Dodd-Frank s1502, upcoming ESG mandates) and donor ESG requirements?", "weight": 0.25, "ratingGuide": { "5": "Compliance rules engine produces auditor-ready evidence packages mapped to each relevant regulation; automatic regulatory updates.", "4": "Evidence covers major regulations; annual manual refresh of rules.", "3": "Evidence covers the primary regulation of the org's jurisdiction.", "2": "Evidence supports reporting but not formal audit.", "1": "Evidence is not aligned with any regulatory schema." } }, { "id": "SC-SUPPLIER-PRIVACY", "name": "Supplier Identity Protection", "description": "Does the system allow external verifiers to confirm compliance without exposing supplier identities or commercial relationships that could put suppliers at risk?", "weight": 0.2, "ratingGuide": { "5": "Zero-knowledge proofs over provenance data \u2014 claims verifiable, identities undisclosed. Supplier risk near zero.", "4": "Selective-disclosure layer with privilege-separated verification.", "3": "Access-controlled disclosure to named verifiers under NDA.", "2": "Public disclosure with some redaction.", "1": "Full supplier identity required in public records." } }, { "id": "SC-ENFORCEMENT-COUPLING", "name": "Compliance Enforcement Coupling", "description": "How tightly is compliance evidence wired to consequence (payment release, shipment acceptance, donor reporting)?", "weight": 0.15, "ratingGuide": { "5": "Smart-contract payment gate and receipt-side rejection workflow; evidence is atomically linked to consequence.", "4": "Automated payment-hold workflow with evidence; manual override possible.", "3": "Evidence feeds procurement-review workflow; enforcement is manual.", "2": "Evidence is reported but not linked to action.", "1": "Evidence collected but no consequence." } }, { "id": "SC-ECOSYSTEM-INTEROP", "name": "Ecosystem Interoperability", "description": "Does the system integrate with industry-standard provenance schemas and audit programmes (RMI, ITSCI, ICGLR) rather than reinventing them?", "weight": 0.1, "ratingGuide": { "5": "Bi-directional integration with RMI/ITSCI/ICGLR feeds; schema alignment with industry standards; mutual recognition of attestations.", "4": "One-way integration (consume industry data) with schema alignment.", "3": "Schema mostly aligned; manual data ingress.", "2": "Bespoke schema with lossy mapping to industry.", "1": "Proprietary schema with no interoperability." } } ], "procurement": { "marketMaturity": "emerging", "primaryMode": "tender", "alternativeModes": [ "integrator-led" ], "reasoning": "Conflict mineral tracking has dedicated commercial platforms.", "exampleProductCategories": [ "mineral-traceability-platform", "conflict-sourcing-rails" ], "partnerChannels": [], "lastReviewed": "2026-05-01" } }, { "id": "UC-D-071", "name": "Customs and import documentation", "category": "D", "subcategory": "Cross-Border Operations", "description": "Keep import and customs paperwork in one record that all parties can check has not been altered, to reduce delays and disputes at the border.", "bCriteria": [ "B1", "B3", "B4", "B7" ], "requiredComponents": [ { "component": "document-ledger", "description": "Shared customs-document record across NGO, freight forwarder, customs authority, and destination partner" }, { "component": "qr-barcode", "description": "Consignment identifiers binding physical shipment to the document ledger" }, { "component": "identity-verification", "description": "Verified authorised agents (licensed customs brokers, NGO authorised signatories)" }, { "component": "audit-mechanism", "description": "Cryptographic audit trail linking declarations, supporting documents, duty assessments, and release authorisations" }, { "component": "compliance-rules-engine", "description": "Policy layer encoding HS codes, duty-exemption schemas, sanctions lists, and dual-use screening" } ], "conditionalComponents": [ { "component": "smart-contracts", "condition": "If humanitarian duty-exemption or fee-waiver is gated on verified consignment type" }, { "component": "iot-sensors", "condition": "If in-transit shipment tracking or cold-chain compliance must be attached to the customs record" }, { "component": "e-signature", "condition": "If destination-country customs accepts cryptographic signatures in lieu of wet-ink declarations" }, { "component": "privacy-tech", "condition": "If sanctions-screening proofs are required without exposing beneficiary or supplier identities" } ], "crossCategoryDependencies": [ "UC-D-057 for donated goods provenance \u2014 customs declarations often require origin evidence", "UC-D-058 for in-kind donation tracking \u2014 in-kind imports drive most NGO customs volume and duty-exemption work", "UC-F-084 for automated donor reporting \u2014 customs events are inputs to donor reporting on aid-in-kind" ], "p2TriggerConditions": { "description": "Activated when P2 shows frequent cross-border operations, duty-exemption complexity, or customs delays affecting programme delivery.", "rangeSignals": [ "crossBorderShipments >= frequent", "dutyExemptionStatus == complex", "customsDelays >= material-impact", "importVolume >= significant" ] }, "contextFieldsTemplate": [ { "field": "jurisdictions", "source": "P0 operations", "description": "Origin and destination jurisdictions. Each has its own customs regime" }, { "field": "importVolume", "source": "P2 CatD Q1a", "description": "Annual number of import consignments" }, { "field": "dutyExemptionStatus", "source": "P0 legal + P2", "description": "Whether the org has humanitarian / diplomatic / NGO-specific duty exemption status" }, { "field": "paperVsDigital", "source": "P2 CatD", "description": "Current balance of paper vs digital customs documentation" }, { "field": "brokerEcosystem", "source": "P0 operations", "description": "In-house brokers vs outsourced freight forwarders vs mixed model" } ], "implementationComplexity": "high", "examples": { "note": "Blockchain-for-trade has strong B1/B3 precedent but commercial adoption has been uneven \u2014 TradeLens (Maersk/IBM) demonstrated feasibility but was shuttered in 2022. WCO digital trade frameworks and UNCTAD ASYCUDA remain the practical integration points for NGOs.", "references": [ { "name": "TradeLens (historical precedent, shuttered 2022)", "url": "https://www.maersk.com", "solved": "Proved feasibility of multi-party consortium ledger for shipping and customs documentation at scale. The failure was commercial (insufficient competitor buy-in), with lessons for any successor effort." }, { "name": "World Customs Organization \u2014 Single Window and digital trade", "url": "https://www.wcoomd.org", "solved": "Defines digital customs interoperability standards (Data Model, SAFE Framework), the schema layer any NGO customs ledger must align with." }, { "name": "UNCTAD ASYCUDA", "url": "https://www.asycuda.net", "solved": "Production customs management system used in 100+ countries, a practical integration target for NGO customs workflows in destination jurisdictions." }, { "name": "IRU TIR electronic transit system (eTIR)", "url": "https://www.iru.org", "solved": "Cross-border transit with digital guarantees, which demonstrates digital-first multi-jurisdiction workflow with customs authorities in the loop." } ] }, "solutionQuestions": [ { "id": "customs-integration-target", "type": "select", "options": [ { "label": "No integration, documents still paper-first, ledger is internal record only", "value": "internal-only" }, { "label": "National Single Window integration in origin/destination country", "value": "single-window" }, { "label": "ASYCUDA or equivalent customs-authority system", "value": "asycuda" }, { "label": "Multi-country: broker-based with ad-hoc integrations", "value": "broker-based" }, { "label": "Full consortium ledger including customs authorities", "value": "consortium" } ], "propertyMapping": { "internal-only": { "technologies": [ "Internal document ledger" ], "technologyProperties": { "externalIntegration": "none", "authorityAcceptance": "none", "adoptionFriction": "low" } }, "single-window": { "technologies": [ "Single-window API adapter", "Document translation layer" ], "technologyProperties": { "externalIntegration": "per-country", "authorityAcceptance": "formal", "adoptionFriction": "moderate" } }, "asycuda": { "technologies": [ "ASYCUDA integration", "Document translation" ], "technologyProperties": { "externalIntegration": "ASYCUDA countries", "authorityAcceptance": "formal", "adoptionFriction": "moderate" } }, "broker-based": { "technologies": [ "Broker portal", "Multi-country document translation" ], "technologyProperties": { "externalIntegration": "via broker", "authorityAcceptance": "indirect", "adoptionFriction": "low-moderate" } }, "consortium": { "technologies": [ "Permissioned consortium ledger", "Multi-authority governance", "Translation layer" ], "technologyProperties": { "externalIntegration": "direct multi-authority", "authorityAcceptance": "requires agreement", "adoptionFriction": "high" } } }, "prefillFrom": null, "briefSection": "Customs authority integration", "text": "Which customs ecosystem does the system need to integrate with?", "ngoText": "Which customs ecosystem does the system need to integrate with?" }, { "id": "duty-exemption-mechanism", "type": "select", "options": [ { "label": "Case-by-case manual exemption application per shipment", "value": "manual" }, { "label": "Pre-approved exemption category with per-shipment paperwork", "value": "pre-approved" }, { "label": "Digital exemption record with authority-signed attestation", "value": "digital-attested" }, { "label": "Smart-contract exemption verification with automated release", "value": "smart-contract" } ], "propertyMapping": { "manual": { "technologies": [ "Exemption application workflow", "Paper document pipeline" ], "technologyProperties": { "processingTime": "days-to-weeks", "errorRate": "moderate", "adoptionBarrier": "low" } }, "pre-approved": { "technologies": [ "Pre-approval registry", "Per-shipment paperwork template" ], "technologyProperties": { "processingTime": "hours-to-days", "errorRate": "moderate", "adoptionBarrier": "low" } }, "digital-attested": { "technologies": [ "Digital exemption registry", "Authority signing service" ], "technologyProperties": { "processingTime": "minutes-to-hours", "errorRate": "low", "adoptionBarrier": "moderate" } }, "smart-contract": { "technologies": [ "Smart-contract exemption gate", "Programmable compliance rules", "Authority signature verification" ], "technologyProperties": { "processingTime": "seconds-to-minutes", "errorRate": "very-low", "adoptionBarrier": "high" } } }, "prefillFrom": null, "briefSection": "Duty exemption", "text": "How should duty-exemption claims be verified and released?", "ngoText": "How should duty-exemption claims be verified and released?" }, { "id": "document-authentication", "type": "select", "options": [ { "label": "Wet-ink paper with scan-and-store", "value": "wet-ink" }, { "label": "PDF with typed signatures", "value": "pdf-sig" }, { "label": "E-signature with cryptographic signing", "value": "esign" }, { "label": "Ledger-anchored documents with verifiable issuance", "value": "ledger-anchored" } ], "propertyMapping": { "wet-ink": { "technologies": [ "Document scanner pipeline", "Document store" ], "technologyProperties": { "tamperResistance": "weak", "verifiability": "local-only", "recognisedByAuthorities": "always" } }, "pdf-sig": { "technologies": [ "PDF signing tool", "Document store" ], "technologyProperties": { "tamperResistance": "moderate", "verifiability": "local-only", "recognisedByAuthorities": "varies" } }, "esign": { "technologies": [ "Commercial e-signature platform", "Certificate store" ], "technologyProperties": { "tamperResistance": "strong", "verifiability": "by-recipient", "recognisedByAuthorities": "many" } }, "ledger-anchored": { "technologies": [ "Document hasher", "Ledger commit service", "Verifiable credential issuer" ], "technologyProperties": { "tamperResistance": "very-strong", "verifiability": "anyone", "recognisedByAuthorities": "emerging" } } }, "prefillFrom": null, "briefSection": "Document authenticity", "text": "How should customs documents be authenticated?", "ngoText": "How should customs documents be authenticated?" }, { "id": "exception-handling-model", "type": "select", "options": [ { "label": "Email-based escalation to broker and NGO ops", "value": "email" }, { "label": "Case-management platform with SLA tracking", "value": "case-mgmt" }, { "label": "Integrated exception workflow linked to ledger entries", "value": "integrated" }, { "label": "Authority-participating workflow with shared resolution ledger", "value": "authority-shared" } ], "propertyMapping": { "email": { "technologies": [ "Email + spreadsheet tracking" ], "technologyProperties": { "resolutionLatency": "days-to-weeks", "visibility": "low", "auditability": "weak" } }, "case-mgmt": { "technologies": [ "Case management platform", "SLA tooling" ], "technologyProperties": { "resolutionLatency": "hours-to-days", "visibility": "internal", "auditability": "moderate" } }, "integrated": { "technologies": [ "Exception workflow service", "Ledger linkage" ], "technologyProperties": { "resolutionLatency": "minutes-to-hours", "visibility": "internal + broker", "auditability": "strong" } }, "authority-shared": { "technologies": [ "Multi-party workflow", "Shared resolution ledger" ], "technologyProperties": { "resolutionLatency": "variable", "visibility": "all parties", "auditability": "very-strong" } } }, "prefillFrom": null, "briefSection": "Exception handling", "text": "How are customs exceptions (misclassification, missing docs, duty disputes) resolved?", "ngoText": "How are customs exceptions (misclassification, missing docs, duty disputes) resolved?" }, { "id": "data-jurisdiction", "type": "select", "options": [ { "label": "All data stored in origin country", "value": "origin-only" }, { "label": "Data stored in destination country only", "value": "destination-only" }, { "label": "Dual storage in origin and destination", "value": "dual" }, { "label": "Distributed ledger with per-jurisdiction access controls", "value": "distributed" } ], "propertyMapping": { "origin-only": { "technologies": [ "Origin-country data store" ], "technologyProperties": { "dataSovereignty": "origin", "crossBorderAccess": "weak", "complianceComplexity": "low" } }, "destination-only": { "technologies": [ "Destination-country data store" ], "technologyProperties": { "dataSovereignty": "destination", "crossBorderAccess": "weak", "complianceComplexity": "low" } }, "dual": { "technologies": [ "Dual-region data store", "Sync service" ], "technologyProperties": { "dataSovereignty": "dual", "crossBorderAccess": "moderate", "complianceComplexity": "moderate" } }, "distributed": { "technologies": [ "Distributed ledger", "Per-jurisdiction access controls", "Selective-disclosure layer" ], "technologyProperties": { "dataSovereignty": "per-record", "crossBorderAccess": "strong", "complianceComplexity": "high" } } }, "prefillFrom": null, "briefSection": "Data sovereignty", "text": "Where do customs-document records need to be stored to satisfy each jurisdiction's data-sovereignty rules?", "ngoText": "Where do customs-document records need to be stored to satisfy each jurisdiction's data-sovereignty rules?" } ], "complexityFactors": { "relationships": 4, "operationalChange": 3, "dataCompliance": 4 }, "suggestedCriteria": [ { "id": "SC-AUTHORITY-INTEGRATION", "name": "Customs Authority Integration Depth", "description": "How formally does the system connect with the customs authorities whose acceptance defines success (mere internal record, Single Window integration, or multi-authority consortium)?", "weight": 0.3, "ratingGuide": { "5": "Multi-authority consortium ledger with signed release from the relevant customs authority as part of the ledger state. Direct acceptance.", "4": "Single Window / ASYCUDA integration with bi-directional document flow; authority systems consume the ledger output.", "3": "One-way integration \u2014 system feeds authority systems but doesn't receive.", "2": "No direct integration; broker acts as bridge.", "1": "Internal-only record with no authority linkage." } }, { "id": "SC-DUTY-EXEMPTION-ENFORCEMENT", "name": "Duty Exemption Enforcement", "description": "How tightly is the humanitarian/NGO duty-exemption claim enforced and verified, especially to prevent fraudulent or disputed exemptions that delay shipments?", "weight": 0.2, "ratingGuide": { "5": "Smart-contract exemption gate with authority-signed attestation; exemption is atomically verifiable and the shipment cannot clear without it.", "4": "Digital exemption registry with authority signing; exemption-check automated.", "3": "Pre-approved exemption category with per-shipment manual validation.", "2": "Case-by-case manual application.", "1": "No exemption framework; full duty paid on every consignment." } }, { "id": "SC-DOCUMENT-TAMPER-EVIDENCE", "name": "Document Tamper Evidence", "description": "Can a customs document be verified after the fact as unaltered since its original issuance and signing?", "weight": 0.2, "ratingGuide": { "5": "Ledger-anchored documents with cryptographic proof of issuance and integrity; any party can verify without trusting a custodian.", "4": "E-signed documents with public-key verification; requires trust in the signing platform.", "3": "PDF signatures with internal verification.", "2": "Scanned wet-ink documents with audit logs.", "1": "Paper-first documents with no post-hoc integrity check." } }, { "id": "SC-EXCEPTION-RESOLUTION", "name": "Exception Resolution Speed and Auditability", "description": "When a consignment is held, misclassified, or duty-disputed, how fast and auditable is the resolution workflow?", "weight": 0.15, "ratingGuide": { "5": "Multi-party workflow with shared resolution ledger; all parties see the same state; median resolution hours not days.", "4": "Integrated exception workflow with broker + NGO + case-management tool.", "3": "Case-management platform with SLA tracking.", "2": "Email escalation with manual tracking.", "1": "Ad-hoc \u2014 resolved by whichever person remembers." } }, { "id": "SC-SOVEREIGNTY-COMPLIANCE", "name": "Data Sovereignty Compliance", "description": "Does the data architecture satisfy each jurisdiction's sovereignty rules (data residency, access, redaction) without creating silos that block cross-border workflows?", "weight": 0.15, "ratingGuide": { "5": "Per-record jurisdictional residency with selective cross-border visibility via access-controlled ledger; satisfies each jurisdiction while enabling workflow.", "4": "Dual-region storage with sync; satisfies origin and destination.", "3": "Single-jurisdiction storage with manual export for cross-border.", "2": "Single-jurisdiction storage, cross-border friction known and accepted.", "1": "No sovereignty strategy \u2014 risk of non-compliance in some corridors." } } ], "procurement": { "marketMaturity": "mature", "primaryMode": "off-the-shelf", "alternativeModes": [ "rfq" ], "reasoning": "Customs and import documentation is a mature broker SaaS market.", "exampleProductCategories": [ "customs-broker-saas", "trade-documentation-platform" ], "partnerChannels": [], "lastReviewed": "2026-05-01" } }, { "id": "UC-E-068", "name": "Voting and decision-making for consortia", "category": "E", "subcategory": "Multi-Agency Coordination", "description": "Run votes and group decisions across partners and locations with a count that everyone can check, so results are not disputed.", "bCriteria": [ "B1", "B2", "B5" ], "requiredComponents": [ { "component": "voting-mechanism", "description": "Transparent voting system" }, { "component": "record-keeping-platform", "description": "Immutable vote records" }, { "component": "decision-audit-trail", "description": "Vote audit trail" }, { "component": "identity-protocol", "description": "Voter identity verification" } ], "conditionalComponents": [ { "component": "smart-contracts", "condition": "If automated vote counting/tally" }, { "component": "privacy-tech", "condition": "For secret ballot voting" } ], "crossCategoryDependencies": [ "UC-B-036 for voter eligibility verification" ], "p2TriggerConditions": { "description": "Activated when P2 shows community governance + voting transparency + accountability concerns", "rangeSignals": [ "communityGovernance >= true", "votingFrequency >= regular", "transparencyConcern >= high" ] }, "contextFieldsTemplate": [ { "field": "communities", "source": "P0 operations", "description": "Number of communities" }, { "field": "voters", "source": "P2 community size", "description": "Number of voters" }, { "field": "decisions", "source": "P2 governance", "description": "Types of decisions voted on" }, { "field": "votingFrequency", "source": "P2 governance schedule", "description": "How often voting occurs" } ], "implementationComplexity": "medium", "examples": { "note": "Community-based decision making", "references": [ { "name": "Polkadot Governance", "url": "https://wiki.polkadot.network/docs/learn-governance", "solved": "Transparent on-chain voting with multiple voting tracks and community participation" }, { "name": "Aragon DAO Voting Framework", "url": "https://aragon.org/governance", "solved": "Customisable voting mechanisms with delegation and multi-stage processes" }, { "name": "Liquid Democracy and Delegative Voting", "url": "https://en.wikipedia.org/wiki/Delegative_democracy", "solved": "Hybrid model allowing direct voting or delegation to trusted representatives" } ] }, "solutionQuestions": [ { "id": "voting-method", "type": "select", "options": [ { "label": "Simple majority (51%+)", "value": "simple-majority" }, { "label": "Supermajority or consensus-based (66%+ or 75%+)", "value": "supermajority" }, { "label": "Weighted voting (stake-based or role-based)", "value": "weighted-voting" }, { "label": "Multi-stage or tiered voting", "value": "tiered-voting" }, { "label": "Delegated voting (proxy-based)", "value": "delegated-voting" } ], "propertyMapping": { "simple-majority": { "technologies": [ "Smart contract voting engine", "Distributed ledger" ], "technologyProperties": { "consensus": "Simple majority threshold", "automaticTally": "true", "transparencyLevel": "Full public visibility" } }, "supermajority": { "technologies": [ "Smart contract voting engine", "Quorum consensus" ], "technologyProperties": { "consensus": "Supermajority threshold (66-75%)", "automaticTally": "true", "deliberationRequired": "true" } }, "weighted-voting": { "technologies": [ "Tokenized voting protocol", "Identity verification" ], "technologyProperties": { "votingPower": "Stake-based or role-based", "identityBinding": "true", "auditTrail": "Cryptographic proof" } }, "tiered-voting": { "technologies": [ "Multi-layer consensus mechanism", "Smart contracts" ], "technologyProperties": { "stages": "Multiple rounds", "escalationLogic": "true", "transparencyPerStage": "Conditional" } }, "delegated-voting": { "technologies": [ "Proxy voting mechanism", "Identity management" ], "technologyProperties": { "delegationTracking": "Immutable log", "revokeCapability": "true", "representativeVerification": "Required" } } }, "prefillFrom": null, "briefSection": "Governance mechanism", "text": "How many distinct stakeholder groups participate in your decision-making (e.g., board, staff, community, beneficiaries, partner organizations)? Do these groups have different decision-making authority or voice level?", "ngoText": "How many distinct stakeholder groups participate in your decision-making (e.g., board, staff, community, beneficiaries, partner organizations)? Do these groups have different decision-making authority or voice level?" }, { "id": "ballot-secrecy", "type": "select", "options": [ { "label": "Public voting with full transparency", "value": "public-voting" }, { "label": "Private voting with aggregated results only", "value": "private-aggregated" }, { "label": "Secret ballot with zero-knowledge proofs", "value": "secret-ballot-zkp" }, { "label": "Hybrid model (some votes public, some private)", "value": "hybrid-secrecy" } ], "propertyMapping": { "public-voting": { "technologies": [ "Public ledger", "Blockchain explorer" ], "technologyProperties": { "privacyLevel": "None", "auditability": "Complete transaction history", "voter_anonymity": "false" } }, "private-aggregated": { "technologies": [ "Private channels", "Commitment scheme" ], "technologyProperties": { "privacyLevel": "Medium", "resultsPublished": "Aggregated only", "voteEncryption": "Threshold encryption" } }, "secret-ballot-zkp": { "technologies": [ "Zero-knowledge proofs", "Homomorphic encryption" ], "technologyProperties": { "privacyLevel": "High", "voter_anonymity": "true", "verifiability": "Cryptographic proof without disclosure" } }, "hybrid-secrecy": { "technologies": [ "Mixed encryption schemes", "Conditional disclosure" ], "technologyProperties": { "privacyTiers": "Multiple levels", "flexibleAccess": "true", "complianceAdjustable": "true" } } }, "prefillFrom": null, "briefSection": "Voting and consensus", "text": "Are there local political sensitivities, power dynamics, or safety concerns where voters might face consequences if their voting preference were publicly known?", "ngoText": "Are there local political sensitivities, power dynamics, or safety concerns where voters might face consequences if their voting preference were publicly known?", "hidden": true }, { "id": "voting-scale", "type": "select", "options": [ { "label": "Small (up to 50 voters)", "value": "small-scale" }, { "label": "Medium (50\u2013500 voters)", "value": "medium-scale" }, { "label": "Large (500\u20135,000 voters)", "value": "large-scale" }, { "label": "Very large (5,000+ voters)", "value": "very-large-scale" } ], "propertyMapping": { "small-scale": { "technologies": [ "Lightweight consensus layer", "Smart contract platform" ], "technologyProperties": { "throughput": "High per-participant", "computationalComplexity": "Low", "networkLoad": "Minimal" } }, "medium-scale": { "technologies": [ "Optimized consensus mechanism", "Layer 2 solution" ], "technologyProperties": { "batchProcessing": "true", "throughput": "Moderate aggregation", "latency": "Sub-minute" } }, "large-scale": { "technologies": [ "Sharding or rollup architecture", "Sidechain voting" ], "technologyProperties": { "parallelProcessing": "true", "scalabilityMechanism": "Shard-based", "finalityTime": "Minutes" } }, "very-large-scale": { "technologies": [ "Hierarchical consensus", "Cross-chain voting bridge" ], "technologyProperties": { "delegatedVoting": "true", "samplingVerification": "Statistical proof", "throughput": "Thousands per block" } } }, "prefillFrom": null, "briefSection": "Governance mechanism", "text": "What scale of voting participants do you anticipate?", "ngoText": "What scale of voting participants do you anticipate?" }, { "id": "dispute-resolution", "type": "select", "options": [ { "label": "Permanent tamper-proof result acceptance with no appeal", "value": "immutable-final" }, { "label": "Governance council review and override capability", "value": "council-review" }, { "label": "Mandatory recount with digitally verified", "value": "cryptographic-recount" }, { "label": "Escalation to community arbitration", "value": "community-arbitration" }, { "label": "Time-locked grace period for challenge submission", "value": "grace-period-challenge" } ], "propertyMapping": { "immutable-final": { "technologies": [ "Blockchain immutability", "Cryptographic finality" ], "technologyProperties": { "reversibility": "false", "trustModel": "Cryptographic trust", "governance": "No override" } }, "council-review": { "technologies": [ "Multi-signature governance", "Escrow mechanism" ], "technologyProperties": { "reviewersRequired": "3-5 council members", "timeWindow": "7-14 days", "transparentLogging": "true" } }, "cryptographic-recount": { "technologies": [ "Verifiable random function", "Proof-of-work verification" ], "technologyProperties": { "verifiability": "Complete computational proof", "costBarrier": "Computational commitment", "transparentProcess": "true" } }, "community-arbitration": { "technologies": [ "Arbitration protocol", "Community DAO voting" ], "technologyProperties": { "participantSelection": "Random or stakeholder-based", "bindingDecision": "Automatedenforcement", "appealLevel": "1-2 levels" } }, "grace-period-challenge": { "technologies": [ "Time-lock mechanism", "Challenge submission contract" ], "technologyProperties": { "challengeWindow": "24-72 hours", "evidenceRequirement": "Cryptographic proof", "automatedEnforcement": "true" } } }, "prefillFrom": null, "briefSection": "Voting and consensus", "text": "In your experience, how often do voting outcomes get challenged or disputed? When a challenge occurs, what is the acceptable timeframe for final decision/resolution?", "ngoText": "In your experience, how often do voting outcomes get challenged or disputed? When a challenge occurs, what is the acceptable timeframe for final decision/resolution?" }, { "id": "decision-audit-trail", "type": "select", "options": [ { "label": "Full decision log: every vote, rationale, and outcome recorded", "value": "full-log" }, { "label": "Outcome-only: record final decisions and who approved", "value": "outcome-only" }, { "label": "Anonymised voting with verifiable tallies", "value": "anonymised-voting" }, { "label": "Not sure, need guidance", "value": "guidance-needed" } ], "propertyMapping": { "full-log": { "technologies": [ "Full decision audit trail", "Deliberation recording service", "Decision verification portal" ], "technologyProperties": { "recordGranularity": "Every vote, rationale, outcome", "transparency": "Full \u2014 all participants can verify", "privacy": "Named votes on record" } }, "outcome-only": { "technologies": [ "Outcome-based decision audit trail", "Approval chain logger", "Decision verification portal" ], "technologyProperties": { "recordGranularity": "Final decisions and approvers only", "transparency": "Outcome transparency", "privacy": "Deliberations private, outcomes public" } }, "anonymised-voting": { "technologies": [ "Anonymised decision audit trail", "Zero-knowledge voting module", "Tally verification service" ], "technologyProperties": { "recordGranularity": "Verifiable tallies without individual votes", "transparency": "Outcome verifiable, individual votes private", "privacy": "Full voter privacy" } }, "guidance-needed": { "technologies": [ "Decision audit trail framework", "Decision verification portal" ], "technologyProperties": { "recordGranularity": "To be determined", "transparency": "To be determined", "privacy": "To be determined" } } }, "prefillFrom": null, "briefSection": "Decision transparency", "text": "How are governance decisions currently recorded and verified?", "ngoText": "How are governance decisions currently recorded and verified?" } ], "complexityFactors": { "relationships": 4, "operationalChange": 3, "dataCompliance": 2 }, "suggestedCriteria": [ { "id": "SC-VOTE-INTEGRITY", "name": "Vote Integrity & Tamper Resistance", "description": "The provider can guarantee that cast votes cannot be altered, deleted, or duplicated after submission. Immutability of the voting record is the foundational requirement.", "weight": 0.3, "ratingGuide": { "5": "Cryptographically sealed vote records on immutable ledger. Mathematical proof that no vote was altered post-submission. Independent audit verification available.", "4": "Blockchain-based vote storage with strong tamper evidence. Merkle-proof verification for individual votes. Minor rollback scenarios documented and mitigated.", "3": "Append-only database with integrity checks. Tamper detection exists but relies on trusted administrators for some operations.", "2": "Centralised vote storage with audit logs. Tamper detection depends on administrator honesty. No cryptographic proof of integrity.", "1": "Votes stored in editable database with no integrity guarantees. Administrator can modify records without detection." } }, { "id": "SC-VOTE-PRIVACY", "name": "Ballot Secrecy & Voter Privacy", "description": "Voters can cast their preference without anyone, including system administrators, being able to link a specific vote to a specific person. Critical where power dynamics or political sensitivities exist.", "weight": 0.25, "ratingGuide": { "5": "Zero-knowledge proof or homomorphic encryption ensures ballot secrecy. Even system operators cannot link votes to voters. Mathematically verified.", "4": "Strong encryption with threshold decryption \u2014 no single party can de-anonymise. Requires collusion of multiple independent parties to break secrecy.", "3": "Votes encrypted but a single trusted party holds decryption keys. Secrecy depends on operational trust rather than mathematical guarantees.", "2": "Pseudonymous voting \u2014 votes not directly linked to names but linkable through metadata analysis or insider access.", "1": "Votes are publicly attributable to individual voters. No privacy mechanism." } }, { "id": "SC-VOTE-VERIFY", "name": "Result Verifiability & Transparency", "description": "Can any stakeholder independently verify that the announced result matches the actual votes cast, without needing to trust a central authority?", "weight": 0.2, "ratingGuide": { "5": "Universally verifiable \u2014 any observer can independently confirm the tally is correct using publicly available cryptographic proofs. End-to-end verifiability.", "4": "Designated verifiers (e.g., elected auditors) can confirm results. Verification tools provided but require some technical knowledge.", "3": "Results published with summary statistics. Spot-check auditing possible but full independent verification not supported.", "2": "Results announced by central authority with limited supporting evidence. Recount possible only by the same authority.", "1": "No verification mechanism. Stakeholders must trust the result announcer entirely." } }, { "id": "SC-VOTE-ACCESS", "name": "Inclusive Participation & Accessibility", "description": "The voting mechanism can accommodate participants with limited literacy, limited technology access, or who are in remote/offline locations. Governance mechanisms that exclude vulnerable voices undermine their purpose.", "weight": 0.15, "ratingGuide": { "5": "Multiple access channels (SMS, USSD, paper ballot with digital bridge, mobile app). Offline voting with later sync. Tested with low-literacy populations.", "4": "Mobile-friendly interface with offline capability. Supports low-bandwidth environments. Available in local languages.", "3": "Web-based interface that works on basic smartphones. Requires intermittent connectivity. Single language or limited localisation.", "2": "Desktop/laptop required. Reliable internet needed. English-only interface.", "1": "Requires specialised hardware or technical knowledge. No accommodation for low-resource contexts." } }, { "id": "SC-VOTE-DISPUTE", "name": "Dispute Resolution & Auditability", "description": "If a voting outcome is challenged, the system provides sufficient evidence to resolve disputes fairly. Includes recount capability, audit trails, and challenge mechanisms.", "weight": 0.1, "ratingGuide": { "5": "Built-in challenge mechanism with cryptographic recount capability. Full audit trail of every step. Time-locked challenge windows with automated evidence compilation.", "4": "Comprehensive audit trail supports manual recount. Challenge submission process defined. Evidence exportable for external review.", "3": "Audit logs available but recount requires administrator intervention. Challenge process exists but is informal.", "2": "Limited audit trail. Dispute resolution depends on administrator goodwill. No formal challenge mechanism.", "1": "No audit trail or dispute mechanism. Results are final with no recourse." } } ], "procurement": { "marketMaturity": "emerging", "primaryMode": "off-the-shelf", "alternativeModes": [ "rfq" ], "reasoning": "Voting and decision-making SaaS available in governance vertical.", "exampleProductCategories": [ "governance-saas", "board-voting-platform" ], "partnerChannels": [], "lastReviewed": "2026-05-01" } }, { "id": "UC-E-069", "name": "Community-based targeting verification", "category": "E", "subcategory": "Beneficiary Targeting", "description": "Keep a record of how communities chose who receives help, so the choices can be checked and cannot be altered under pressure.", "bCriteria": [ "B1", "B3" ], "requiredComponents": [ { "component": "record-keeping-platform", "description": "Targeting decisions record" }, { "component": "decision-audit-trail", "description": "Selection decision audit trail" }, { "component": "accountability-tools", "description": "Community accountability mechanisms" }, { "component": "verification-mechanism", "description": "Targeting verification proofs" } ], "conditionalComponents": [ { "component": "smart-contracts", "condition": "If automated targeting rules" } ], "crossCategoryDependencies": [ "UC-C-043 for beneficiary deduplication" ], "p2TriggerConditions": { "description": "Activated when P2 shows community-based targeting + fairness concerns + verification needs", "rangeSignals": [ "targetingMethod = community-based", "fairnessConcerns >= true", "auditRequirement >= true" ] }, "contextFieldsTemplate": [ { "field": "beneficiaries", "source": "P2 programme scale", "description": "Number to target" }, { "field": "targetingCriteria", "source": "P2 targeting rules", "description": "Eligibility criteria" }, { "field": "communities", "source": "P0 operations", "description": "Communities involved" }, { "field": "disputes", "source": "P0 context", "description": "Expected targeting disputes" } ], "implementationComplexity": "medium", "examples": { "note": "Community-based targeting, beneficiary selection", "references": [ { "name": "Targeting Best Practices in Humanitarian Response", "url": "https://www.alnap.org/system/files/content/resource/files/main/alnap-ngo-targeting-standards.pdf", "solved": "Standardised targeting methodology with community consultation and accountability mechanisms" }, { "name": "Blockchain for Beneficiary Verification", "url": "https://www.worldbank.org/en/topic/ict", "solved": "Immutable record of targeting decisions with transparent audit trails" }, { "name": "Community-Based Targeting Review Framework", "url": "https://www.interaction.org/blog/community-based-targeting/", "solved": "Community participation in verification with documented feedback and dispute resolution" } ] }, "solutionQuestions": [ { "id": "targeting-method", "type": "select", "options": [ { "label": "Needs-based assessment with objective criteria", "value": "needs-assessment" }, { "label": "Community wealth ranking or participatory assessment", "value": "community-ranking" }, { "label": "Vulnerable group identification (elderly, disabled, etc.)", "value": "vulnerable-groups" }, { "label": "Geographic or sectoral targeting", "value": "geographic-sectoral" }, { "label": "Hybrid multi-criteria approach", "value": "hybrid-multicriteria" } ], "propertyMapping": { "needs-assessment": { "technologies": [ "Data registry", "Audit trail ledger" ], "technologyProperties": { "criteriaDefinition": "Predefined objective metrics", "verificationProcess": "Multi-step validation", "appealMechanism": "Evidence-based challenge" } }, "community-ranking": { "technologies": [ "Community consensus platform", "Decision log" ], "technologyProperties": { "participationTracking": "Voter identity recorded", "deliberationLog": "Full reasoning stored", "transparencyMode": "Community-visible" } }, "vulnerable-groups": { "technologies": [ "Classification registry", "Confidentiality layer" ], "technologyProperties": { "sensitiveDataHandling": "Encrypted segregation", "accessControl": "Role-based permissions", "auditability": "Anonymized log" } }, "geographic-sectoral": { "technologies": [ "Spatial data registry", "Hierarchical ledger" ], "technologyProperties": { "geographicCoding": "Standardized taxonomy", "sectorMapping": "Classification schema", "transparencyGeometry": "Boundary-based disclosure" } }, "hybrid-multicriteria": { "technologies": [ "Weighted scoring contract", "Multi-signature verification" ], "technologyProperties": { "scoringAlgorithm": "Transparent weighting", "criteriaAudit": "Immutable criteria log", "resultVerification": "Multi-party validation" } } }, "prefillFrom": null, "briefSection": "Transparency and accountability", "text": "What targeting methodology does your community use?", "ngoText": "What targeting methodology does your community use?" }, { "id": "community-participation", "type": "select", "options": [ { "label": "Open community assembly with consensus decision", "value": "open-assembly" }, { "label": "Representative committee (elected or designated)", "value": "representative-committee" }, { "label": "Asynchronous feedback period with public comments", "value": "asynchronous-feedback" }, { "label": "Stakeholder rounds with documented responses", "value": "stakeholder-rounds" } ], "propertyMapping": { "open-assembly": { "technologies": [ "Community assembly protocol", "Consensus ledger" ], "technologyProperties": { "participantTracking": "Identity verified", "votingMethod": "Simple or supermajority", "documentationLevel": "Full verbatim record" } }, "representative-committee": { "technologies": [ "Governance registry", "Multi-signature endorsement" ], "technologyProperties": { "membershipCriteria": "Predefined selection process", "termLength": "Fixed or rolling", "accountabilityMechanism": "Revocation vote" } }, "asynchronous-feedback": { "technologies": [ "Comment registry", "Timestamped submission log" ], "technologyProperties": { "commentPeriod": "7-21 days", "responseObligation": "Issue tracker", "publicVisibility": "true" } }, "stakeholder-rounds": { "technologies": [ "Staged feedback platform", "Interview log" ], "technologyProperties": { "roundSequence": "Multiple planned rounds", "responseTracking": "Documented feedback loop", "stakeholderCategories": "Segmented groups" } } }, "prefillFrom": null, "briefSection": "Coordination platform", "text": "How do community members currently participate in verification?", "ngoText": "How do community members currently participate in verification?" }, { "id": "dispute-handling", "type": "select", "options": [ { "label": "Community reconsideration with appeal submission", "value": "community-reconsideration" }, { "label": "Independent review panel with documented decision", "value": "review-panel" }, { "label": "Mediation by trusted third party", "value": "mediation" }, { "label": "Immediate re-verification with transparent criteria audit", "value": "reverification" } ], "propertyMapping": { "community-reconsideration": { "technologies": [ "Community assembly", "Appeal submission contract" ], "technologyProperties": { "appealWindow": "14-30 days", "newEvidenceAllowed": "true", "majorityThreshold": "60%+" } }, "review-panel": { "technologies": [ "Panel registry", "Decision log with attestation" ], "technologyProperties": { "panelSize": "3-5 members", "expertise": "Multi-disciplinary", "bindingDecision": "true" } }, "mediation": { "technologies": [ "Mediator directory", "Dispute resolution protocol" ], "technologyProperties": { "mediatorSelection": "Mutually agreed or randomized", "settlementLog": "Confidential until agreed", "enforcementMechanism": "Smart contract escrow" } }, "reverification": { "technologies": [ "Criteria audit contract", "Re-assessment ledger" ], "technologyProperties": { "criteriaCheck": "Automated or manual", "evidenceReview": "New documentation allowed", "resultFinality": "Binding on second assessment" } } }, "prefillFrom": null, "briefSection": "Transparency and accountability", "text": "How are disputes currently resolved in your governance structures?", "ngoText": "How are disputes currently resolved in your governance structures?" }, { "id": "targeting-transparency", "type": "select", "options": [ { "label": "Full public criteria and selected beneficiary list", "value": "full-public" }, { "label": "Criteria public; beneficiary list for community review only", "value": "criteria-public-list-community" }, { "label": "Aggregated statistics; no individual names published", "value": "aggregated-stats" }, { "label": "Reasons for selection transparent; identities private", "value": "reasons-public-identity-private" } ], "propertyMapping": { "full-public": { "technologies": [ "Public ledger", "Blockchain explorer" ], "technologyProperties": { "accessControl": "No restrictions", "dataRetention": "Permanent", "privacyConsiderations": "Minimal" } }, "criteria-public-list-community": { "technologies": [ "Public criteria ledger", "Permissioned list access" ], "technologyProperties": { "criteriaVisibility": "Unrestricted", "beneficiaryListAccess": "Token-gated or invited", "accessLog": "Tracked" } }, "aggregated-stats": { "technologies": [ "Privacy-preserving statistics", "Differential privacy" ], "technologyProperties": { "granularity": "Region or sector level", "noiseMechanism": "Noise added for anonymity", "queryLimit": "Restricted query types" } }, "reasons-public-identity-private": { "technologies": [ "Anonymized decision ledger", "Zero-knowledge proof" ], "technologyProperties": { "reasoningTransparency": "Full explanations", "identityAnonymization": "Hash-based or encrypted", "verifiability": "Proof without disclosure" } } }, "prefillFrom": null, "briefSection": "Transparency and accountability", "text": "Do your donors require visibility into which beneficiaries were selected and why? Do community members demand to see the targeting criteria and decisions?", "ngoText": "Do your donors require visibility into which beneficiaries were selected and why? Do community members demand to see the targeting criteria and decisions?" }, { "id": "community-targeting-participant-count", "type": "select", "options": [ { "label": "2\u20135 parties", "value": "small" }, { "label": "6\u201315 parties", "value": "medium" }, { "label": "16\u201350 parties", "value": "large" }, { "label": "Over 50 parties", "value": "enterprise" } ], "propertyMapping": { "small": { "technologies": [ "Simple shared ledger" ], "technologyProperties": { "consensusComplexity": "Low", "governanceModel": "Direct" } }, "medium": { "technologies": [ "Permissioned network", "Role-based access" ], "technologyProperties": { "consensusComplexity": "Medium", "governanceModel": "Committee-based" } }, "large": { "technologies": [ "Scalable permissioned network", "Delegated consensus" ], "technologyProperties": { "consensusComplexity": "High", "governanceModel": "Delegated" } }, "enterprise": { "technologies": [ "Enterprise consortium platform", "Federated consensus" ], "technologyProperties": { "consensusComplexity": "Very high", "governanceModel": "Federated" } } }, "prefillFrom": null, "briefSection": "Governance mechanism", "text": "How many organisations or stakeholders participate in community targeting?", "ngoText": "How many organisations or stakeholders participate in community targeting?" }, { "id": "accountability-approach", "type": "select", "options": [ { "label": "Public dashboard with real-time transparency metrics", "value": "public-dashboard" }, { "label": "Stakeholder-restricted reporting portal", "value": "stakeholder-portal" }, { "label": "Community-facing feedback and verification system", "value": "community-facing" }, { "label": "Automated compliance scoring and alerts", "value": "automated-scoring" } ], "propertyMapping": { "public-dashboard": { "technologies": [ "Public accountability dashboard", "Transparency metrics engine", "Accountability reporting tools" ], "technologyProperties": { "visibility": "Public / open access", "updateFrequency": "Real-time or daily", "feedbackLoop": "Public comment / rating system" } }, "stakeholder-portal": { "technologies": [ "Stakeholder accountability portal", "Role-based reporting engine", "Accountability reporting tools" ], "technologyProperties": { "visibility": "Registered stakeholders only", "updateFrequency": "On-demand with scheduled reports", "feedbackLoop": "Stakeholder feedback channel" } }, "community-facing": { "technologies": [ "Community accountability platform", "Beneficiary feedback module", "Accountability reporting tools" ], "technologyProperties": { "visibility": "Community members and beneficiaries", "updateFrequency": "Event-driven", "feedbackLoop": "SMS/app-based feedback collection" } }, "automated-scoring": { "technologies": [ "Automated accountability scoring engine", "Compliance alert service", "Accountability reporting tools" ], "technologyProperties": { "visibility": "Internal with escalation alerts", "updateFrequency": "Continuous monitoring", "feedbackLoop": "Automated alerts on non-compliance" } } }, "prefillFrom": null, "briefSection": "Accountability", "text": "What accountability and transparency mechanisms are needed?", "ngoText": "What accountability and transparency mechanisms are needed?", "hidden": true } ], "complexityFactors": { "relationships": 3, "operationalChange": 3, "dataCompliance": 2 }, "suggestedCriteria": [ { "id": "SC-TARGET-FAIR", "name": "Targeting Fairness & Bias Prevention", "description": "Does the provider's system prevent manipulation of beneficiary selection, ensuring that targeting criteria are applied consistently and that no individual or group can unfairly influence who is included or excluded?", "weight": 0.3, "ratingGuide": { "5": "Algorithmic targeting with transparent criteria recorded on-chain. Community verification of selections. Statistical bias detection built in. Appeals mechanism for exclusions.", "4": "Criteria-based targeting with immutable audit trail. Community spot-checks supported. Bias monitoring through demographic analysis.", "3": "Targeting criteria documented and logged. Some community oversight but limited systematic bias detection.", "2": "Targeting decisions recorded but criteria application not independently verifiable. Limited community input.", "1": "Targeting decisions opaque. No audit trail of selection criteria or community verification." } }, { "id": "SC-TARGET-COMM", "name": "Community Participation in Verification", "description": "Affected communities can meaningfully participate in verifying that targeting decisions are accurate and fair. Community-based verification is essential for legitimacy in humanitarian targeting.", "weight": 0.25, "ratingGuide": { "5": "Structured community verification process with designated community validators. Mobile-accessible feedback loops. Verification results recorded immutably. Communities can flag errors in real time.", "4": "Community review periods with accessible feedback channels. Verification input recorded and tracked. Response to community flags within defined timeframes.", "3": "Community consulted periodically but input is advisory rather than binding. Some feedback channels exist but not systematically tracked.", "2": "Community informed of targeting decisions but limited input mechanism. Feedback collection sporadic.", "1": "No community participation in targeting verification. Decisions made entirely by programme staff." } }, { "id": "SC-TARGET-TRANS", "name": "Decision Transparency & Audit Trail", "description": "Is every targeting decision (inclusion, exclusion, and appeals outcome) recorded with sufficient detail to support accountability reviews and donor audits?", "weight": 0.2, "ratingGuide": { "5": "Every targeting decision logged with criteria applied, data used, decision-maker identity, and timestamp. Immutable record. Exportable for external audit. Supports real-time donor dashboards.", "4": "Comprehensive decision logging with most metadata. Tamper-evident storage. Audit-ready export formats.", "3": "Key decisions logged but some metadata missing (e.g., criteria weights or data sources). Periodic audit reports rather than real-time access.", "2": "Summary-level logging only. Individual decisions not traceable. Audit support requires manual data extraction.", "1": "No systematic decision logging. Targeting records maintained informally or not at all." } }, { "id": "SC-TARGET-PRIV", "name": "Beneficiary Privacy in Verification", "description": "Does the verification process protect sensitive beneficiary data, ensuring that community validators can confirm targeting accuracy without accessing personal details they should not see?", "weight": 0.15, "ratingGuide": { "5": "Zero-knowledge or privacy-preserving verification \u2014 validators confirm eligibility without seeing underlying personal data. Cryptographic privacy guarantees.", "4": "Role-based access with minimal disclosure. Validators see only the data relevant to their verification role. Strong access controls and audit logging.", "3": "Data access restricted but validators may see more personal data than strictly necessary. Access logging in place.", "2": "Beneficiary data broadly accessible to verification participants. Basic access controls but no minimisation principle.", "1": "All personal data visible to all participants in the targeting process. No privacy protections." } }, { "id": "SC-TARGET-GRIEV", "name": "Grievance Mechanism & Appeals Process", "description": "Can individuals who believe they were wrongly excluded (or wrongly included) submit appeals that are tracked, investigated, and resolved transparently?", "weight": 0.1, "ratingGuide": { "5": "Built-in grievance submission (multiple channels including anonymous). Every appeal tracked on-chain with status updates. Resolution timelines enforced. Outcome data feeds back into targeting improvement.", "4": "Structured appeals process with tracking. Multiple submission channels. Resolution timelines defined. Outcomes recorded.", "3": "Appeals process exists but tracking is manual. Single submission channel. Resolution timelines advisory.", "2": "Informal appeals possible but no systematic tracking. Resolution depends on staff availability.", "1": "No appeals mechanism. Targeting decisions are final." } } ], "procurement": { "marketMaturity": "emerging", "primaryMode": "rfq", "alternativeModes": [ "off-the-shelf" ], "reasoning": "Community-based targeting platforms exist with humanitarian profiles.", "exampleProductCategories": [ "targeting-platform", "community-engagement-saas" ], "partnerChannels": [], "lastReviewed": "2026-05-01" } }, { "id": "UC-E-070", "name": "Grant allocation across multiple partners", "category": "E", "subcategory": "Grant Management", "description": "Show how a shared fund was divided among partners and when each received its share, so partners can see the process was fair.", "bCriteria": [ "B1", "B3", "B5" ], "requiredComponents": [ { "component": "record-keeping-platform", "description": "Grant allocation records" }, { "component": "decision-audit-trail", "description": "Allocation decision audit trail" }, { "component": "accounting-integration", "description": "Fund disbursement tracking" }, { "component": "reporting-module", "description": "Allocation reporting" } ], "conditionalComponents": [ { "component": "smart-contracts", "condition": "If automated allocation rules" } ], "crossCategoryDependencies": [ "UC-A-016 for sub-grantee tracking" ], "p2TriggerConditions": { "description": "Activated when P2 shows multi-partner grants + allocation complexity + fairness concerns", "rangeSignals": [ "partners >= 3+", "allocationComplexity >= high", "fairness >= important" ] }, "contextFieldsTemplate": [ { "field": "partners", "source": "P0 partnerships", "description": "Number of partners" }, { "field": "grantValue", "source": "P0 budget", "description": "Total grant value" }, { "field": "criteria", "source": "P2 allocation rules", "description": "Allocation criteria" }, { "field": "reportingNeeds", "source": "P0 donor agreements", "description": "Reporting requirements" } ], "implementationComplexity": "medium", "examples": { "note": "Multi-partner grant management", "references": [ { "name": "Global Fund Grant Management System", "url": "https://www.theglobalfund.org/en/", "solved": "Multi-partner fund allocation with performance-based adjustment and transparent reporting" }, { "name": "World Bank RETF (Results, Evidence and Learning Trust Fund)", "url": "https://www.worldbank.org/en/programs/sief-trust-fund", "solved": "Dynamic allocation model responsive to partner performance metrics" }, { "name": "Gimlet Transparent Fund Distribution", "url": "https://blockchain.gitcoin.co/", "solved": "Algorithmic fund allocation with community oversight and transparent on-chain records" } ] }, "solutionQuestions": [ { "id": "allocation-model", "type": "select", "options": [ { "label": "Fixed proportion model (e.g., 40% to partner A, 60% to partner B)", "value": "fixed-proportion" }, { "label": "Performance-based allocation with KPI weighting", "value": "performance-based" }, { "label": "Needs-based allocation determined by partner capacity", "value": "needs-based" }, { "label": "Competitive funding model with proposal evaluation", "value": "competitive-funding" }, { "label": "Dynamic allocation adjusting quarterly based on metrics", "value": "dynamic-allocation" } ], "propertyMapping": { "fixed-proportion": { "technologies": [ "Automated distribution", "Multi-beneficiary wallet" ], "technologyProperties": { "allocationLogic": "Static percentages", "updateFrequency": "Manual override only", "transparency": "Fixed formula in contract" } }, "performance-based": { "technologies": [ "KPI oracle integration", "Score-weighted smart contract" ], "technologyProperties": { "kpiTracking": "Real-time from oracle", "weightCalculation": "Predetermined coefficients", "incentiveAlignment": "Direct allocation-performance link" } }, "needs-based": { "technologies": [ "Capacity assessment ledger", "Dynamic allocation contract" ], "technologyProperties": { "needsEvaluation": "Quarterly assessment", "fairnessMetric": "Capacity-adjusted distribution", "participationRequired": "Partner input" } }, "competitive-funding": { "technologies": [ "Proposal submission platform", "Evaluation smart contract" ], "technologyProperties": { "evaluationProcess": "Multi-round scoring", "scoringCriteria": "Transparent rubric", "fundingDecision": "Automated payout on approval" } }, "dynamic-allocation": { "technologies": [ "Real-time metrics engine", "Trigger-based adjustment contract" ], "technologyProperties": { "dataFrequency": "Monthly or quarterly", "adjustmentTriggers": "Performance thresholds", "reallocationLatency": "Immediate to next cycle" } } }, "prefillFrom": null, "briefSection": "Reporting and audit", "text": "How are grants currently allocated across partners?", "ngoText": "How are grants currently allocated across partners?" }, { "id": "decision-making", "type": "select", "options": [ { "label": "Headquarters leadership decision with documented rationale", "value": "hq-leadership" }, { "label": "Multi-stakeholder committee with voting mechanism", "value": "committee-voting" }, { "label": "Consensus-based agreement with all partners signing off", "value": "consensus-agreement" }, { "label": "Algorithmic formula with human review override", "value": "algorithmic-with-review" } ], "propertyMapping": { "hq-leadership": { "technologies": [ "Decision record ledger", "Digital signature attestation" ], "technologyProperties": { "decisionLog": "Immutable record with justification", "authorityValidation": "Cryptographic signature", "revisionCapability": "Noted in audit trail" } }, "committee-voting": { "technologies": [ "Governance committee registry", "Multi-signature voting contract" ], "technologyProperties": { "committeeComposition": "Defined roster", "votingThreshold": "Simple or supermajority", "votingTransparency": "Recorded per member" } }, "consensus-agreement": { "technologies": [ "Consent registry", "Multi-signature endorsement" ], "technologyProperties": { "consensusDefinition": "All parties or supermajority", "timeAllowance": "Days for agreement", "blockingMechanism": "Any party can escalate" } }, "algorithmic-with-review": { "technologies": [ "Automated allocation engine", "Override governance" ], "technologyProperties": { "algorithmTransparency": "Code auditable", "humanOverride": "Requires multi-sig approval", "auditLog": "Override reasons tracked" } } }, "prefillFrom": null, "briefSection": "Governance mechanism", "text": "How will allocation decisions be made and approved?", "ngoText": "How will allocation decisions be made and approved?" }, { "id": "fund-tracking-granularity", "type": "select", "options": [ { "label": "Activity level (individual project or program)", "value": "activity-level" }, { "label": "Budget line level (salary, supplies, transport, etc.)", "value": "budget-line" }, { "label": "Transaction level (every receipt or invoice)", "value": "transaction-level" }, { "label": "Milestone level (fund released on achievement)", "value": "milestone-level" }, { "label": "High-level monitoring (monthly or quarterly reporting)", "value": "highlevel-monthly" } ], "propertyMapping": { "activity-level": { "technologies": [ "Activity registry ledger", "Project tracking" ], "technologyProperties": { "dataPoints": "Per activity costs", "updateFrequency": "Activity completion", "granularity": "Medium" } }, "budget-line": { "technologies": [ "Budget allocation ledger", "Expenditure tracking" ], "technologyProperties": { "chartOfAccounts": "Standardized GL coding", "variance": "Budget vs. actual", "reconciledFrequency": "Monthly" } }, "transaction-level": { "technologies": [ "Transaction ledger", "Invoice/receipt blockchain" ], "technologyProperties": { "dataPoints": "Every payment detail", "documentAttachment": "Immutable linking", "granularity": "Maximum" } }, "milestone-level": { "technologies": [ "Milestone escrow contract", "Verification oracle" ], "technologyProperties": { "releaseCondition": "Milestone achievement proof", "holdingMechanism": "Automatedescrow", "progressTracking": "Stage-by-stage" } }, "highlevel-monthly": { "technologies": [ "Monthly reporting ledger", "Aggregated summary contract" ], "technologyProperties": { "reportingCadence": "Monthly snapshots", "dataPoints": "Summary-level only", "auditableDetail": "Supporting docs on request" } } }, "prefillFrom": null, "briefSection": "Reporting and audit", "text": "At what granularity will you track fund usage across partners?", "ngoText": "At what granularity will you track fund usage across partners?" }, { "id": "allocation-reporting", "type": "select", "options": [ { "label": "Public dashboard with real-time fund visibility", "value": "public-dashboard" }, { "label": "Confidential partner reports with authenticated access", "value": "partner-reports" }, { "label": "Periodic audit reports with third-party certification", "value": "audit-reports" }, { "label": "Disaggregated data export for analysis and learning", "value": "disaggregated-data" } ], "propertyMapping": { "public-dashboard": { "technologies": [ "Blockchain explorer", "Public-facing portal" ], "technologyProperties": { "accessControl": "Unrestricted", "updateFrequency": "Real-time Digital", "visualization": "Interactive charts" } }, "partner-reports": { "technologies": [ "Permissioned report generation", "Encrypted communication" ], "technologyProperties": { "accessControl": "Role-based authenticated", "reportFormat": "Customized per partner", "deliveryMethod": "Secure messaging" } }, "audit-reports": { "technologies": [ "Audit log ledger", "Third-party attestation smart contract" ], "technologyProperties": { "auditFrequency": "Quarterly or annual", "attestation": "Cryptographic signature", "scopeDocumentation": "Full audit trail" } }, "disaggregated-data": { "technologies": [ "Data export protocol", "Privacy-preserving anonymization" ], "technologyProperties": { "granularity": "Transactional or activity-level", "privacyMeasure": "Aggregation or differential privacy", "accessFormat": "CSV, JSON, or data API" } } }, "prefillFrom": null, "briefSection": "Reporting and audit", "text": "How will allocation decisions and fund flows be reported?", "ngoText": "How will allocation decisions and fund flows be reported?" }, { "id": "allocation-flexibility", "type": "select", "options": [ { "label": "No mid-cycle changes; allocations locked until next cycle", "value": "no-changes" }, { "label": "Emergency reallocation with documented justification", "value": "emergency-reallocation" }, { "label": "Quarterly rebalancing based on partner request", "value": "quarterly-rebalancing" }, { "label": "Continuous adjustment within predefined thresholds", "value": "continuous-adjustment" } ], "propertyMapping": { "no-changes": { "technologies": [ "Immutable allocation contract", "Time-locked schedule" ], "technologyProperties": { "flexibility": "None", "governanceRequired": "Full reset for change", "predictability": "High" } }, "emergency-reallocation": { "technologies": [ "Emergency governance mechanism", "Override contract" ], "technologyProperties": { "triggerCriteria": "Documented emergency", "approvalRequired": "Multi-sig from leadership", "documentationRequired": "Mandatory justification" } }, "quarterly-rebalancing": { "technologies": [ "Scheduled rebalancing contract", "Request submission ledger" ], "technologyProperties": { "requestWindow": "30 days before quarter-end", "approvalProcess": "Committee review", "implementationLag": "One quarter" } }, "continuous-adjustment": { "technologies": [ "Dynamic allocation smart contract", "Real-time trigger contract" ], "technologyProperties": { "adjustmentThreshold": "Max \u00b110% per month", "approvalRequired": "Automated below threshold", "operationalFlexibility": "Maximum" } } }, "prefillFrom": null, "briefSection": "Reporting and audit", "text": "How much flexibility exists to adjust allocations during a funding cycle?", "ngoText": "How much flexibility exists to adjust allocations during a funding cycle?" } ], "complexityFactors": { "relationships": 3, "operationalChange": 3, "dataCompliance": 2 }, "suggestedCriteria": [ { "id": "SC-GRANT-TRANS", "name": "Allocation Transparency & Decision Audit", "description": "Can all consortium members and donors see exactly how grant funds were allocated, what criteria were applied, and who approved each allocation decision?", "weight": 0.3, "ratingGuide": { "5": "Every allocation decision recorded on-chain with criteria, scores, approver identities, and timestamps. Real-time visibility for all authorised stakeholders. Immutable record.", "4": "Comprehensive allocation logging with decision rationale. Near-real-time visibility. Tamper-evident storage.", "3": "Allocation decisions documented but not all metadata captured. Periodic reports rather than real-time access.", "2": "Summary-level allocation records. Individual decision rationale not systematically captured.", "1": "Allocation decisions opaque. No systematic record of criteria application or approvals." } }, { "id": "SC-GRANT-TRACK", "name": "Fund Flow Tracking & Traceability", "description": "Can the system trace every unit of funding from donor origin through intermediary allocation to final expenditure at the partner level?", "weight": 0.25, "ratingGuide": { "5": "End-to-end fund traceability from donor to expenditure. Every transfer logged with source, destination, amount, and purpose. Real-time balance visibility across all partners.", "4": "Fund flows tracked at allocation and disbursement levels. Partner-level expenditure reporting integrated. Minor gaps in real-time visibility.", "3": "Allocation and disbursement tracked. Partner expenditure reported periodically but not integrated into the same system.", "2": "Allocation tracked but downstream fund flows require manual reconciliation. Significant reporting delays.", "1": "No systematic fund flow tracking beyond initial allocation. Downstream use of funds unknown to allocator." } }, { "id": "SC-GRANT-FAIR", "name": "Equitable Allocation & Bias Prevention", "description": "Does the system help ensure that allocation decisions follow stated criteria rather than favouritism, and that smaller or less-connected partners are not systematically disadvantaged?", "weight": 0.2, "ratingGuide": { "5": "Criteria-weighted scoring algorithm with full transparency. Historical allocation analysis to detect patterns of bias. Automatic flagging of allocation anomalies.", "4": "Structured scoring against published criteria. Allocation history visible to all partners. Periodic equity reviews supported by data.", "3": "Criteria documented and applied but scoring process partially subjective. Some allocation history available.", "2": "Criteria exist but application is inconsistent and not independently verifiable.", "1": "No structured allocation criteria. Decisions appear arbitrary to partners." } }, { "id": "SC-GRANT-MULTI", "name": "Multi-Partner Coordination & Reporting", "description": "Can the system coordinate reporting requirements across multiple implementing partners with different capacities, formats, and reporting cycles?", "weight": 0.15, "ratingGuide": { "5": "Unified reporting framework that accommodates different partner capacities. Automated data collection from partner systems. Consolidated donor reporting with partner-level drill-down.", "4": "Standardised reporting templates with flexible submission methods. Semi-automated consolidation. Supports partners with varying technical capacity.", "3": "Common reporting format but manual consolidation. Partners with limited capacity require support to comply.", "2": "Ad-hoc reporting with minimal standardisation. Consolidation is labour-intensive.", "1": "No coordinated reporting framework. Each partner reports independently with no consolidation." } }, { "id": "SC-GRANT-COMPLY", "name": "Donor Compliance & Audit Readiness", "description": "Does the system produce audit-ready records that satisfy major humanitarian donor requirements (USAID, DFID/FCDO, EU, UN pooled funds)?", "weight": 0.1, "ratingGuide": { "5": "Pre-configured compliance templates for major donors. Automated audit trail generation. Supports concurrent multi-donor reporting with different requirements.", "4": "Configurable compliance reporting. Audit trail comprehensive and exportable. Tested against at least two major donor frameworks.", "3": "General audit trail that can be adapted for compliance. Requires some manual formatting for specific donor requirements.", "2": "Basic transaction records available but significant manual effort to produce compliant reports.", "1": "No compliance-oriented reporting. Audit preparation requires rebuilding records from scratch." } } ], "procurement": { "marketMaturity": "emerging", "primaryMode": "rfq", "alternativeModes": [ "integrator-led" ], "reasoning": "Grant allocation across partners overlaps with grants management SaaS.", "exampleProductCategories": [ "grants-management-platform", "consortium-finance-saas" ], "partnerChannels": [], "lastReviewed": "2026-05-01" } }, { "id": "UC-E-071", "name": "Programme outcome verification", "category": "E", "subcategory": "Programme Outcomes", "description": "Keep what partners report about results exactly as first submitted, so inflated or later-edited figures can be spotted.", "bCriteria": [ "B1", "B3" ], "requiredComponents": [ { "component": "record-keeping-platform", "description": "Performance records" }, { "component": "accountability-tools", "description": "Performance accountability" }, { "component": "audit-mechanism", "description": "Performance audit trail" }, { "component": "reporting-module", "description": "Performance reporting" } ], "conditionalComponents": [ { "component": "smart-contracts", "condition": "If automated performance bonuses/penalties" } ], "crossCategoryDependencies": [], "p2TriggerConditions": { "description": "Activated when P2 shows partner-implemented programmes + performance management focus", "rangeSignals": [ "partners >= 3+", "performanceTracking >= important", "incentiveStructure >= true" ] }, "contextFieldsTemplate": [ { "field": "partners", "source": "P0 partnerships", "description": "Number of implementing partners" }, { "field": "indicators", "source": "P2 M&E", "description": "Performance indicators" }, { "field": "reportingFrequency", "source": "P0 agreements", "description": "Reporting frequency" }, { "field": "consequences", "source": "P0 policies", "description": "Performance consequences" } ], "implementationComplexity": "medium", "examples": { "note": "Partner performance management", "references": [ { "name": "UN OCHA Performance Monitoring Framework", "url": "https://www.unocha.org/about-us/accountability-framework", "solved": "Standardised performance indicators with automated monitoring and escalation triggers" }, { "name": "Results-Based Management in Development Cooperation", "url": "https://www.oecd.org/development/results-development/", "solved": "Outcome-based KPI framework with verification and consequence mechanisms" }, { "name": "Blockchain-Based Performance Contracts", "url": "https://www.cato.org/cato-journal/fall-2020/performance-based-governance", "solved": "Automated performance-linked fund release using smart contracts and oracles" } ] }, "solutionQuestions": [ { "id": "kpi-types", "type": "select", "options": [ { "label": "Output metrics (beneficiaries reached, activities completed)", "value": "output-metrics" }, { "label": "Outcome metrics (behavior change, impact achieved)", "value": "outcome-metrics" }, { "label": "Process metrics (timeliness, quality, compliance)", "value": "process-metrics" }, { "label": "Financial metrics (budget variance, cost per unit)", "value": "financial-metrics" }, { "label": "Mixed portfolio across multiple metric types", "value": "mixed-portfolio" } ], "propertyMapping": { "output-metrics": { "technologies": [ "Output registry ledger", "Activity tracking blockchain" ], "technologyProperties": { "dataSource": "Direct reports or sensors", "verifiability": "Checkable against records", "lag": "Short delay for aggregation" } }, "outcome-metrics": { "technologies": [ "Outcome measurement protocol", "Survey or assessment ledger" ], "technologyProperties": { "dataSource": "Evaluations, surveys, field assessments", "causality": "Proxy measurements", "lag": "Longer delay required" } }, "process-metrics": { "technologies": [ "Compliance ledger", "Audit event log" ], "technologyProperties": { "measurability": "Observable adherence", "dataSource": "Process logs", "objectivity": "Clear pass/fail criteria" } }, "financial-metrics": { "technologies": [ "Financial transaction ledger", "Budget variance contract" ], "technologyProperties": { "dataSource": "Accounting system", "updateFrequency": "Monthly reconciliation", "auditability": "Full receipt documentation" } }, "mixed-portfolio": { "technologies": [ "Multi-metric scoring contract", "Weighted KPI aggregation" ], "technologyProperties": { "weighting": "Predefined coefficients", "balancing": "Multiple dimensions scored", "transparency": "Composite formula public" } } }, "prefillFrom": null, "briefSection": "Partner verification", "text": "What KPIs will measure partner performance?", "ngoText": "What KPIs will measure partner performance?" }, { "id": "verification-method", "type": "select", "options": [ { "label": "Partner self-reporting with spot checks", "value": "self-report-checks" }, { "label": "Third-party monitoring and evaluation", "value": "third-party-m-and-e" }, { "label": "Direct automated measurement (sensors, systems, automated checks)", "value": "automated-measurement" }, { "label": "Community verification with independent witnesses", "value": "community-verification" }, { "label": "Hybrid approach combining multiple methods", "value": "hybrid-verification" } ], "propertyMapping": { "self-report-checks": { "technologies": [ "Reporting portal", "Spot-check ledger", "Random verification" ], "technologyProperties": { "reportingFrequency": "Monthly or quarterly", "spotCheckRate": "5-10% of activities", "documentationRequired": "Supporting evidence" } }, "third-party-m-and-e": { "technologies": [ "M&E contractor registry", "Field report ledger" ], "technologyProperties": { "evaluation": "Independent assessors", "coverageRate": "10-25% of partners", "reportFormat": "Standardized assessment" } }, "automated-measurement": { "technologies": [ "IoT sensor network", "API data feed", "Automated measurement" ], "technologyProperties": { "realTime": "Continuous monitoring", "dataFidelity": "High accuracy", "manipulationResistance": "Tamper-evident sensors" } }, "community-verification": { "technologies": [ "Community monitor registry", "Witness attestation protocol" ], "technologyProperties": { "participantSelection": "Community members", "training": "Standardized assessment", "incentiveModel": "Compensation or recognition" } }, "hybrid-verification": { "technologies": [ "Multi-method verification contract", "Evidence aggregation" ], "technologyProperties": { "methodCombination": "2-3 verification approaches", "weightingLogic": "Predefined combination rule", "reliabilityEnhancement": "Redundancy and triangulation" } } }, "prefillFrom": null, "briefSection": "Partner verification", "text": "How will KPI achievement be verified?", "ngoText": "How will KPI achievement be verified?" }, { "id": "performance-consequences", "type": "select", "options": [ { "label": "Supportive improvement plan with technical assistance", "value": "support-plan" }, { "label": "Performance-based budget adjustment (e.g., 10% reduction)", "value": "budget-adjustment" }, { "label": "Automatic fund withholding until recovery plan achieved", "value": "automatic-withholding" }, { "label": "Partnership termination with formal exit process", "value": "partnership-termination" }, { "label": "Tiered response escalating by severity of underperformance", "value": "tiered-response" } ], "propertyMapping": { "support-plan": { "technologies": [ "Performance improvement protocol", "Support ledger" ], "technologyProperties": { "triggerThreshold": "Below 70% of target", "supportDuration": "3-6 months", "escalationPath": "To tiered system if no progress" } }, "budget-adjustment": { "technologies": [ "Performance-linked allocation contract", "Automatic fund adjustment" ], "technologyProperties": { "adjustmentFormula": "% reduction per % shortfall", "automaticity": "Algorithmic reduction", "appealProcess": "Documented challenge" } }, "automatic-withholding": { "technologies": [ "Escrow smart contract", "Release condition verification" ], "technologyProperties": { "holdingMechanism": "Funds in escrow", "releaseCondition": "Performance improvement plan signed", "dueDiligence": "Manual approval required" } }, "partnership-termination": { "technologies": [ "Termination protocol", "Exit ledger", "Knowledge transfer" ], "technologyProperties": { "noticeRequired": "60-90 days", "finalSettlement": "Documented transition", "publicRecording": "Termination reason logged" } }, "tiered-response": { "technologies": [ "Escalation smart contract", "Performance threshold triggers" ], "technologyProperties": { "tier1": "Warning at 70% of target", "tier2": "Support plan and 10% reduction", "tier3": "Fund withholding", "tier4": "Partnership termination" } } }, "prefillFrom": null, "briefSection": "Partner verification", "text": "What are the consequences of not meeting KPI targets?", "ngoText": "What are the consequences of not meeting KPI targets?" }, { "id": "reporting-frequency", "type": "select", "options": [ { "label": "Real-time or continuous monitoring dashboard", "value": "realtime-dashboard" }, { "label": "Weekly performance snapshots", "value": "weekly-reports" }, { "label": "Monthly performance reports", "value": "monthly-reports" }, { "label": "Quarterly comprehensive reviews", "value": "quarterly-reviews" }, { "label": "Annual evaluations with mid-term review optional", "value": "annual-evaluation" } ], "propertyMapping": { "realtime-dashboard": { "technologies": [ "Real-time monitoring contract", "Dashboard API" ], "technologyProperties": { "dataLatency": "Minutes", "accessControl": "Role-based viewing", "alerting": "Automated threshold notifications" } }, "weekly-reports": { "technologies": [ "Weekly aggregation contract", "Report generation bot" ], "technologyProperties": { "refreshCycle": "Every 7 days", "automatedGeneration": "true", "distributionChannel": "Email or portal" } }, "monthly-reports": { "technologies": [ "Monthly reporting ledger", "Reconciliation protocol" ], "technologyProperties": { "refreshCycle": "Monthly", "reconciliation": "Required at period end", "standardFormat": "Template-based" } }, "quarterly-reviews": { "technologies": [ "Quarterly review ceremony", "Deep-dive ledger" ], "technologyProperties": { "reviewFormat": "Video conference or meeting", "analysisDepth": "Comprehensive", "documentationRequired": "Meeting notes and decisions" } }, "annual-evaluation": { "technologies": [ "Annual evaluation protocol", "Mid-year optional checkpoint" ], "technologyProperties": { "evaluationDepth": "Comprehensive assessment", "timingFlexibility": "Annual cycle", "midYearOption": "Discretionary check-in" } } }, "prefillFrom": null, "briefSection": "Reporting and audit", "text": "When a partner's performance is below expectations, do disputes arise about whether the data is accurate or whether the metrics are fair?", "ngoText": "When a partner's performance is below expectations, do disputes arise about whether the data is accurate or whether the metrics are fair?" }, { "id": "partner-perf-participant-count", "type": "select", "options": [ { "label": "2\u20135 parties", "value": "small" }, { "label": "6\u201315 parties", "value": "medium" }, { "label": "16\u201350 parties", "value": "large" }, { "label": "Over 50 parties", "value": "enterprise" } ], "propertyMapping": { "small": { "technologies": [ "Simple shared ledger" ], "technologyProperties": { "consensusComplexity": "Low", "governanceModel": "Direct" } }, "medium": { "technologies": [ "Permissioned network", "Role-based access" ], "technologyProperties": { "consensusComplexity": "Medium", "governanceModel": "Committee-based" } }, "large": { "technologies": [ "Scalable permissioned network", "Delegated consensus" ], "technologyProperties": { "consensusComplexity": "High", "governanceModel": "Delegated" } }, "enterprise": { "technologies": [ "Enterprise consortium platform", "Federated consensus" ], "technologyProperties": { "consensusComplexity": "Very high", "governanceModel": "Federated" } } }, "prefillFrom": null, "briefSection": "Governance mechanism", "text": "How many organisations or stakeholders participate in partner performance reviews?", "ngoText": "How many organisations or stakeholders participate in partner performance reviews?" }, { "id": "partner-perf-decision-freq", "type": "select", "options": [ { "label": "Daily or more", "value": "daily" }, { "label": "Weekly", "value": "weekly" }, { "label": "Monthly", "value": "monthly" }, { "label": "Quarterly or less", "value": "quarterly" } ], "propertyMapping": { "daily": { "technologies": [ "Automated record creation", "Real-time sync" ], "technologyProperties": { "throughput": "High", "automation": "Required" } }, "weekly": { "technologies": [ "Scheduled sync" ], "technologyProperties": { "throughput": "Medium", "automation": "Recommended" } }, "monthly": { "technologies": [ "Batch processing acceptable" ], "technologyProperties": { "throughput": "Low", "automation": "Optional" } }, "quarterly": { "technologies": [], "technologyProperties": { "throughput": "Minimal", "automation": "Not required" } } }, "prefillFrom": null, "briefSection": "Coordination platform", "text": "How frequently are partner performance decisions or records created?", "ngoText": "How frequently are partner performance decisions or records created?" }, { "id": "accountability-approach", "type": "select", "options": [ { "label": "Public dashboard with real-time transparency metrics", "value": "public-dashboard" }, { "label": "Stakeholder-restricted reporting portal", "value": "stakeholder-portal" }, { "label": "Community-facing feedback and verification system", "value": "community-facing" }, { "label": "Automated compliance scoring and alerts", "value": "automated-scoring" } ], "propertyMapping": { "public-dashboard": { "technologies": [ "Public accountability dashboard", "Transparency metrics engine", "Accountability reporting tools" ], "technologyProperties": { "visibility": "Public / open access", "updateFrequency": "Real-time or daily", "feedbackLoop": "Public comment / rating system" } }, "stakeholder-portal": { "technologies": [ "Stakeholder accountability portal", "Role-based reporting engine", "Accountability reporting tools" ], "technologyProperties": { "visibility": "Registered stakeholders only", "updateFrequency": "On-demand with scheduled reports", "feedbackLoop": "Stakeholder feedback channel" } }, "community-facing": { "technologies": [ "Community accountability platform", "Beneficiary feedback module", "Accountability reporting tools" ], "technologyProperties": { "visibility": "Community members and beneficiaries", "updateFrequency": "Event-driven", "feedbackLoop": "SMS/app-based feedback collection" } }, "automated-scoring": { "technologies": [ "Automated accountability scoring engine", "Compliance alert service", "Accountability reporting tools" ], "technologyProperties": { "visibility": "Internal with escalation alerts", "updateFrequency": "Continuous monitoring", "feedbackLoop": "Automated alerts on non-compliance" } } }, "prefillFrom": null, "briefSection": "Accountability", "text": "What accountability and transparency mechanisms are needed?", "ngoText": "What accountability and transparency mechanisms are needed?", "hidden": true } ], "complexityFactors": { "relationships": 2, "operationalChange": 2, "dataCompliance": 2 }, "suggestedCriteria": [ { "id": "SC-PERF-VERIFY", "name": "Independent Performance Verification", "description": "Can the system verify partner-reported performance data against independent sources or third-party attestations, rather than relying solely on self-reporting?", "weight": 0.3, "ratingGuide": { "5": "Multi-source verification: partner reports cross-checked against beneficiary feedback, field monitoring data, and third-party attestations. Discrepancies flagged automatically.", "4": "At least two independent data sources for verification. Automated discrepancy detection for key metrics. Third-party attestation supported.", "3": "Partner self-reporting with periodic independent spot-checks. Some automated consistency checking.", "2": "Primarily self-reported data with manual review. Independent verification occasional and resource-intensive.", "1": "Entirely self-reported with no independent verification mechanism." } }, { "id": "SC-PERF-IMMUT", "name": "Tamper-Proof Performance Records", "description": "Are performance records stored immutably so that neither the reporting partner nor the lead agency can retroactively alter historical performance data?", "weight": 0.25, "ratingGuide": { "5": "All performance data timestamped and stored on immutable ledger. Any corrections logged as amendments \u2014 original data preserved. Full version history.", "4": "Blockchain-anchored records with tamper evidence. Corrections require multi-party approval and are logged with rationale.", "3": "Append-only storage with integrity checks. Corrections possible but logged. Some reliance on trusted administrators.", "2": "Database with audit logging but records technically editable. Tampering detectable only through log review.", "1": "Records stored in editable systems with no integrity guarantees or audit trail." } }, { "id": "SC-PERF-KPI", "name": "KPI Framework Flexibility & Relevance", "description": "Can the system accommodate diverse performance indicators across different partner types, programme areas, and donor requirements, without forcing a one-size-fits-all framework?", "weight": 0.2, "ratingGuide": { "5": "Fully configurable KPI framework. Custom indicators per partner/programme. Supports quantitative and qualitative metrics. Maps to multiple donor frameworks simultaneously.", "4": "Configurable indicators with pre-built templates for common programme types. Supports both quantitative and qualitative measures.", "3": "Standardised KPI set with some customisation. Primarily quantitative metrics. Single donor framework alignment.", "2": "Fixed KPI framework with limited customisation. Primarily output-focused metrics.", "1": "Rigid, pre-defined metrics that cannot be adapted to different contexts or partner types." } }, { "id": "SC-PERF-CONSQ", "name": "Consequence Management & Escalation", "description": "Does the system support structured responses to performance issues, from early warning through escalation to remediation, rather than binary pass/fail judgements?", "weight": 0.15, "ratingGuide": { "5": "Automated early warning triggers. Graduated escalation pathways (flag \u2192 review \u2192 action plan \u2192 remediation \u2192 termination). Every step recorded with evidence and timelines.", "4": "Alert system for performance thresholds. Defined escalation steps with tracking. Action plans documented and progress monitored.", "3": "Performance issues flagged but escalation process partially manual. Some tracking of remediation actions.", "2": "Performance issues identified but response is ad-hoc. Limited tracking of follow-up actions.", "1": "No systematic consequence management. Performance issues addressed reactively if at all." } }, { "id": "SC-PERF-FAIR", "name": "Fair & Contextual Assessment", "description": "Does the system account for operating context (conflict, natural disaster, access constraints) when assessing partner performance, rather than applying uniform benchmarks regardless of conditions?", "weight": 0.1, "ratingGuide": { "5": "Context-adjusted benchmarks with documented rationale. Partners assessed against peers in similar operating environments. Contextual factors recorded alongside performance data.", "4": "Context factors captured and considered in assessment. Peer grouping by operating environment. Some automated adjustment.", "3": "Context documented but adjustment is discretionary. Assessors can note mitigating factors.", "2": "Uniform benchmarks with informal allowance for context. No systematic contextual adjustment.", "1": "Rigid benchmarks applied uniformly regardless of operating context." } } ], "procurement": { "marketMaturity": "emerging", "primaryMode": "rfq", "alternativeModes": [ "integrator-led" ], "reasoning": "Programme outcome verification overlaps with M&E SaaS.", "exampleProductCategories": [ "m-and-e-saas", "outcome-verification-platform" ], "partnerChannels": [], "lastReviewed": "2026-05-01" } }, { "id": "UC-E-072", "name": "Whistleblower protection mechanisms", "category": "E", "subcategory": "Accountability and Integrity", "description": "Let staff and community members report concerns without revealing who they are, with a record that nobody can quietly alter or delete.", "bCriteria": [ "B1", "B2", "B6" ], "requiredComponents": [ { "component": "anonymisation-tools", "description": "Anonymous reporting system" }, { "component": "record-keeping-platform", "description": "Confidential complaint records" }, { "component": "access-control", "description": "Restricted complaint access" }, { "component": "dispute-resolution", "description": "Complaint investigation tracking" } ], "conditionalComponents": [ { "component": "encryption-privacy", "condition": "For end-to-end encrypted complaints" }, { "component": "privacy-tech", "condition": "For whistleblower identity protection" } ], "crossCategoryDependencies": [], "p2TriggerConditions": { "description": "Activated when P2 shows fraud/corruption concerns + reporting systems + protection needs", "rangeSignals": [ "fraudRisk >= true", "reportingSystem >= needed", "protectionConcern >= high" ] }, "contextFieldsTemplate": [ { "field": "staffCount", "source": "P0 staffing", "description": "Number of staff" }, { "field": "riskLevel", "source": "P0 context", "description": "Fraud/corruption risk" }, { "field": "reportingChannels", "source": "P0 Q19-21", "description": "Available reporting channels" }, { "field": "protectionNeed", "source": "P0 context", "description": "Whistleblower protection need" } ], "implementationComplexity": "high", "examples": { "note": "Ethical reporting and whistleblower protection", "references": [ { "name": "Transparency International Whistleblower Protection Handbook", "url": "https://www.transparency.org/en/publications/exporting-corruption", "solved": "Framework for anonymous reporting channels and investigator independence" }, { "name": "SecureDrop Protocol (Freedom of the Press Foundation)", "url": "https://securedrop.org/", "solved": "Open-source whistleblower reporting platform with Tor anonymity and encrypted storage" }, { "name": "Blockchain-Based Anonymous Reporting in NGOs", "url": "https://www.oecd.org/dac/development-effectiveness/", "solved": "Immutable incident logging with pseudonymous investigation trails and protection mechanisms" } ] }, "solutionQuestions": [ { "id": "anonymity-level", "type": "select", "options": [ { "label": "Complete anonymity: no identifying information collected", "value": "complete-anonymity" }, { "label": "Pseudonymity: known to trusted coordinator but not publicly", "value": "pseudonymity" }, { "label": "Optional disclosure: whistleblower chooses to identify or remain anonymous", "value": "optional-disclosure" }, { "label": "Delayed disclosure: identity known to investigators only, public reporting anonymous", "value": "delayed-disclosure" } ], "propertyMapping": { "complete-anonymity": { "technologies": [ "Anonymous communication channel", "Privacy-preserving identity verification" ], "technologyProperties": { "identityCollection": "None", "correlationResistance": "High", "investigationTracking": "Possible by determined actor" } }, "pseudonymity": { "technologies": [ "Pseudonymous wallet", "Encrypted coordinator key" ], "technologyProperties": { "coordinatorKnowledge": "Trusted coordinator holds mapping", "publicVisibility": "Pseudonym only", "revealCondition": "Court order or legal requirement" } }, "optional-disclosure": { "technologies": [ "User-controlled disclosure", "Encryption envelope system" ], "technologyProperties": { "choiceControl": "Reporter decides", "revocation": "Can be withdrawn pre-publication", "flexibility": "High adaptability" } }, "delayed-disclosure": { "technologies": [ "Time-locked encryption", "Investigator access control" ], "technologyProperties": { "investigatorAccess": "Immediate to identity", "publicAccess": "Delayed or never", "timeDelay": "6-12 months or investigation conclusion" } } }, "prefillFrom": null, "briefSection": "Access control", "text": "Given the retaliation risk in your context, can investigations proceed without revealing the whistleblower's identity?", "ngoText": "Given the retaliation risk in your context, can investigations proceed without revealing the whistleblower's identity?" }, { "id": "reporting-channel", "type": "select", "options": [ { "label": "Web-based submission form with end-to-end encryption", "value": "encrypted-web-form" }, { "label": "SMS or voice hotline accessible from any phone", "value": "voice-sms-hotline" }, { "label": "In-person drop box or physical submission mechanism", "value": "physical-dropbox" }, { "label": "Multiple channels with whistleblower choosing preferred method", "value": "multi-channel" } ], "propertyMapping": { "encrypted-web-form": { "technologies": [ "TLS/SSL encryption", "Anonymous submission channel" ], "technologyProperties": { "accessibility": "Internet required", "userFriendliness": "Browser-based", "technicalRequired": "Moderate", "documentUpload": "Supported with encryption" } }, "voice-sms-hotline": { "technologies": [ "Encrypted VoIP", "SMS gateway with encryption" ], "technologyProperties": { "accessibility": "Any mobile phone", "literacy": "Non-text option available", "liveOperator": "Human transcription required", "coverage": "Must work offline areas" } }, "physical-dropbox": { "technologies": [ "Secure physical container", "Sealed document protocol" ], "technologyProperties": { "accessControl": "Limited custodians", "chainOfCustody": "Documented handling", "location": "Safe and accessible place" } }, "multi-channel": { "technologies": [ "Multiple submission protocols", "Channel aggregation platform" ], "technologyProperties": { "channelOptions": "2-4 choices", "integration": "Central reporting registry", "userChoice": "Full discretion" } } }, "prefillFrom": null, "briefSection": "Access control", "text": "What reporting channels will whistleblowers use?", "ngoText": "What reporting channels will whistleblowers use?" }, { "id": "investigation-workflow", "type": "select", "options": [ { "label": "Independent ombudsman or third-party investigator", "value": "independent-investigator" }, { "label": "Internal investigation team with conflict-of-interest safeguards", "value": "internal-investigation" }, { "label": "Multi-party investigation committee with external member", "value": "committee-investigation" }, { "label": "Forensic analysis with evidence ledger and reporting timeline", "value": "forensic-analysis" } ], "propertyMapping": { "independent-investigator": { "technologies": [ "Third-party investigator registry", "Incident ledger" ], "technologyProperties": { "investigatorIndependence": "No organizational affiliation", "reportingLine": "External board or donor", "confidentiality": "Privileged investigation log" } }, "internal-investigation": { "technologies": [ "Investigation protocol", "Conflict screening" ], "technologyProperties": { "conflictCheck": "Automated disqualification logic", "transparency": "Investigation process documented", "oversight": "Board review before closure" } }, "committee-investigation": { "technologies": [ "Investigation committee registry", "Multi-party approval" ], "technologyProperties": { "composition": "4-5 members with external chair", "externalMember": "Required majority vote", "processDocumentation": "Verbatim meeting records" } }, "forensic-analysis": { "technologies": [ "Digital forensics platform", "Evidence blockchain", "Timeline contract" ], "technologyProperties": { "evidenceCollection": "Tamper-evident chain of custody", "analysisDepth": "Deep technical examination", "reporting": "Forensic evidence report" } } }, "prefillFrom": null, "briefSection": "Access control", "text": "What investigation workflow will handle reported concerns?", "ngoText": "What investigation workflow will handle reported concerns?" }, { "id": "protection-mechanisms", "type": "select", "options": [ { "label": "Legal protections enshrined in policy and employment contracts", "value": "policy-legal-protection" }, { "label": "Monitoring for retaliation with rapid intervention", "value": "retaliation-monitoring" }, { "label": "Physical security measures or relocation if needed", "value": "physical-security" }, { "label": "Financial protection (insurance or compensation fund)", "value": "financial-protection" }, { "label": "Comprehensive package combining multiple protections", "value": "comprehensive-package" } ], "propertyMapping": { "policy-legal-protection": { "technologies": [ "Anti-retaliation policy ledger", "Legal contract registry" ], "technologyProperties": { "policyBinding": "Contractual obligation", "communicationFrequency": "Annual policy reminder", "enforcementMechanism": "Disciplinary code violations" } }, "retaliation-monitoring": { "technologies": [ "Retaliation incident tracking", "Quarterly safety assessment" ], "technologyProperties": { "monitoringFrequency": "Quarterly interviews", "escalationTrigger": "Suspicious negative action", "rapidResponse": "Within 48 hours" } }, "physical-security": { "technologies": [ "Security assessment protocol", "Relocation authorization" ], "technologyProperties": { "riskAssessment": "Based on threat level", "securityMeasure": "Safe house or transfer", "costCoverage": "Organization pays" } }, "financial-protection": { "technologies": [ "Whistleblower insurance contract", "Compensation fund" ], "technologyProperties": { "insuranceCoverage": "Legal fees and lost income", "fundAmount": "Predefined limits", "claimProcess": "Documented and expedited" } }, "comprehensive-package": { "technologies": [ "Protection protocol suite", "Multi-layer safeguard system" ], "technologyProperties": { "protections": "Policy + monitoring + physical + financial", "coordinationProcess": "Integrated protection plan", "responsiveness": "Tailored to individual risk" } } }, "prefillFrom": null, "briefSection": "Access control", "text": "What protection mechanisms will prevent retaliation against whistleblowers?", "ngoText": "What protection mechanisms will prevent retaliation against whistleblowers?" }, { "id": "reporting-encryption", "type": "select", "options": [ { "label": "End-to-end encryption (E2E) with reporter and investigator keys only", "value": "e2e-encryption" }, { "label": "Hybrid encryption with centralized key management and access logs", "value": "hybrid-encryption" }, { "label": "Hardware security module (HSM) for key storage", "value": "hsm-security" }, { "label": "Multi-signature decryption requiring multiple custodians", "value": "multisig-decryption" } ], "propertyMapping": { "e2e-encryption": { "technologies": [ "TLS 1.3 or modern crypto", "PGP or an end-to-end encrypted messaging protocol" ], "technologyProperties": { "keyManagement": "Distributed to authorized parties", "serverAccess": "Encrypted at rest and in transit", "forwardSecrecy": "Perfect forward secrecy" } }, "hybrid-encryption": { "technologies": [ "Symmetric key encryption", "Key management server", "Access audit log" ], "technologyProperties": { "keyRotation": "Quarterly or on personnel changes", "accessLog": "Immutable record of decryption", "escrowArrangement": "Backup keys held by trusted party" } }, "hsm-security": { "technologies": [ "Hardware security module", "FIPS 140-2 certified" ], "technologyProperties": { "keyProtection": "Never exposed in software", "tamperDetection": "Automatic key erasure on breach", "accessControl": "Cryptographic authentication" } }, "multisig-decryption": { "technologies": [ "Threshold cryptography", "Multi-party computation" ], "technologyProperties": { "threshold": "3-of-5 custodians required", "keyStorage": "Shards distributed", "fraudDetection": "Any unauthorized attempt flagged" } } }, "prefillFrom": null, "briefSection": "Access control", "text": "What encryption and confidentiality standards will protect reports?", "ngoText": "What encryption and confidentiality standards will protect reports?", "hidden": true }, { "id": "anonymisation-approach", "type": "select", "options": [ { "label": "Full data anonymisation (irreversible)", "value": "full-anonymisation" }, { "label": "Pseudonymisation (reversible by authorised parties)", "value": "pseudonymisation" }, { "label": "Differential privacy (statistical noise injection)", "value": "differential-privacy" }, { "label": "Selective redaction (remove specific identifiers)", "value": "selective-redaction" } ], "propertyMapping": { "full-anonymisation": { "technologies": [ "Full anonymisation engine", "Identity stripping service", "Anonymised data store" ], "technologyProperties": { "method": "Irreversible anonymisation", "reIdentificationRisk": "Minimal", "dataUtility": "Aggregate analysis only" } }, "pseudonymisation": { "technologies": [ "Pseudonymisation engine", "Key-managed re-identification service", "Anonymisation tools" ], "technologyProperties": { "method": "Pseudonymisation with secure key vault", "reIdentificationRisk": "Controlled \u2014 authorised parties only", "dataUtility": "Individual-level analysis with controls" } }, "differential-privacy": { "technologies": [ "Differential privacy engine", "Statistical noise injection", "Anonymisation tools" ], "technologyProperties": { "method": "Differential privacy", "reIdentificationRisk": "Mathematically bounded", "dataUtility": "Statistical analysis with privacy guarantees" } }, "selective-redaction": { "technologies": [ "Selective redaction engine", "PII detection service", "Anonymisation tools" ], "technologyProperties": { "method": "Selective PII redaction", "reIdentificationRisk": "Moderate \u2014 depends on data context", "dataUtility": "Near-full with identifiers removed" } } }, "prefillFrom": null, "briefSection": "Data anonymisation", "text": "How should personal data be anonymised or protected?", "ngoText": "How should personal data be anonymised or protected?" }, { "id": "dispute-resolution", "type": "select", "options": [ { "label": "digital arbitration with automated rules enforcement", "value": "on-chain-arb" }, { "label": "External mediation with digital outcome recording", "value": "mediation" }, { "label": "Multi-tier: automated resolution, then escalation to human mediator", "value": "multi-tier" }, { "label": "Not sure, need guidance", "value": "guidance-needed" } ], "propertyMapping": { "on-chain-arb": { "technologies": [ "On-chain dispute resolution system", "Arbitration smart contract", "Dispute evidence locker" ], "technologyProperties": { "resolutionMethod": "Automatedarbitration", "enforcement": "Automatic via Automated", "appealProcess": "Digital appeal to higher arbiter" } }, "mediation": { "technologies": [ "Off-chain dispute resolution system", "Mediation workflow platform", "Dispute evidence locker" ], "technologyProperties": { "resolutionMethod": "Human mediator", "enforcement": "Agreement recorded Digital", "appealProcess": "Escalation to formal adjudication" } }, "multi-tier": { "technologies": [ "Multi-tier dispute resolution system", "Automated resolution engine", "Human escalation service" ], "technologyProperties": { "resolutionMethod": "Auto-resolve simple, escalate complex", "enforcement": "Automatedfor auto, agreement for mediated", "appealProcess": "Multi-tier escalation" } }, "guidance-needed": { "technologies": [ "Dispute resolution framework" ], "technologyProperties": { "resolutionMethod": "To be determined", "enforcement": "To be determined", "appealProcess": "To be determined" } } }, "prefillFrom": null, "briefSection": "Dispute resolution", "text": "How is disputes currently resolved within this system?", "ngoText": "How is disputes currently resolved within this system?" } ], "complexityFactors": { "relationships": 2, "operationalChange": 2, "dataCompliance": 4 }, "securityTier": "C", "suggestedCriteria": [ { "id": "SC-WB-ANON", "name": "Reporter Anonymity & Unlinkability", "description": "The system can guarantee that a whistleblower's identity cannot be determined, even by system administrators, investigators, or through metadata analysis. For TIER-C protection, this must be a mathematical guarantee.", "weight": 0.35, "ratingGuide": { "5": "Zero-knowledge proof of report submission \u2014 system can verify the reporter is a legitimate insider without learning their identity. No metadata linking possible. Onion routing or equivalent for submission channel.", "4": "Strong cryptographic anonymisation with no single point of de-anonymisation. Metadata stripped. Multiple independent submission channels.", "3": "Pseudonymous reporting with encryption. Single trusted party could theoretically de-anonymise. Metadata partially scrubbed.", "2": "Confidential reporting \u2014 identity known to a designated person who promises confidentiality. No cryptographic guarantee.", "1": "Reporter identity visible to investigators or administrators. Protection depends entirely on policy compliance." } }, { "id": "SC-WB-NODOOR", "name": "No Backdoor / De-anonymisation Resistance", "description": "This looks at whether any entity (the NGO itself, a government, a court order, or a hostile actor) can compel the system to reveal the reporter's identity. For whistleblowers in conflict zones or authoritarian contexts, this is life-or-death.", "weight": 0.25, "ratingGuide": { "5": "Protocol-level anonymity \u2014 mathematically impossible to de-anonymise even under compulsion. No entity holds identity keys. System designed so that compliance with a court order is technically infeasible.", "4": "De-anonymisation requires cooperation of multiple independent parties in different jurisdictions. Single-point compulsion insufficient.", "3": "Provider holds anonymisation keys but has strong legal protections, warrant canary, and data minimisation. De-anonymisation possible but resisted.", "2": "Identity recoverable by provider under legal compulsion. Single jurisdiction controls access.", "1": "Provider or NGO can reveal identity at will. No structural protection against de-anonymisation." } }, { "id": "SC-WB-CHANNEL", "name": "Secure Reporting Channel & Evidence Handling", "description": "Does the system provide a secure channel for submitting reports and evidence that protects content from interception, tampering, and metadata leakage during transmission and storage?", "weight": 0.2, "ratingGuide": { "5": "End-to-end encrypted submission with zero-knowledge storage. Evidence encrypted client-side before upload. No plaintext ever touches server. Secure deletion of processing artifacts.", "4": "End-to-end encryption for submission and storage. Evidence integrity verified on receipt. Minimal server-side processing of plaintext.", "3": "Transport encryption (TLS) with server-side encryption at rest. Evidence stored encrypted but server has decryption keys for processing.", "2": "Transport encryption only. Evidence stored in accessible format on provider servers.", "1": "No encryption. Reports and evidence transmitted and stored in plaintext." } }, { "id": "SC-WB-FOLLOW", "name": "Anonymous Follow-Up & Two-Way Communication", "description": "Investigators can communicate with the reporter for clarification or updates WITHOUT the reporter having to reveal their identity. Two-way anonymous communication is critical for effective investigation.", "weight": 0.12, "ratingGuide": { "5": "Built-in anonymous messaging system. Reporter can check for and respond to investigator questions using a one-time access code. No identity linkage possible. Notification without identification.", "4": "Secure message drop with pseudonymous access. Reporter must actively check for messages but identity remains protected.", "3": "One-way anonymous submission with option to provide a contact method. Follow-up possible but reduces anonymity.", "2": "Follow-up requires reporter to identify themselves to a designated contact person.", "1": "No follow-up mechanism. One-way submission only. Investigation proceeds without reporter input." } }, { "id": "SC-WB-RETALIATION", "name": "Anti-Retaliation Safeguards & Monitoring", "description": "Does the system include mechanisms to detect and prevent retaliation against reporters, including monitoring for suspicious access patterns, employment changes, or other indicators of reprisal?", "weight": 0.08, "ratingGuide": { "5": "Automated retaliation monitoring: tracks access patterns to report metadata, flags unusual personnel actions near report dates, generates alerts. Independent oversight mechanism.", "4": "Access logging with anomaly detection for report-adjacent data. Defined retaliation indicators monitored. Regular review process.", "3": "Basic access logging for report data. Manual monitoring for retaliation indicators. Defined but infrequent review.", "2": "Anti-retaliation policy exists but no systematic monitoring. Detection relies on reporter self-reporting.", "1": "No anti-retaliation mechanisms beyond policy statements." } } ], "procurement": { "marketMaturity": "emerging", "primaryMode": "tender", "alternativeModes": [ "integrator-led", "rfq" ], "reasoning": "TIER-C critical security: whistleblower mechanisms require formal procurement with strong evaluation. Mature SaaS market exists, but tier prevents direct off-the-shelf adoption.", "exampleProductCategories": [ "whistleblower-platform", "protection-reporting-saas" ], "partnerChannels": [], "lastReviewed": "2026-05-01" } }, { "id": "UC-E-073", "name": "Cross-NGO beneficiary coordination (avoiding gaps and overlaps)", "category": "E", "subcategory": "Inter-Agency Coordination", "description": "Let organisations see who is already receiving help from whom, so people are not assisted twice or missed, without exposing personal details.", "bCriteria": [ "B1", "B2", "B6" ], "requiredComponents": [ { "component": "coordination-layer", "description": "Inter-agency coordination platform" }, { "component": "record-keeping-platform", "description": "Shared beneficiary records" }, { "component": "interoperability-protocol", "description": "Data interoperability" }, { "component": "access-control", "description": "Privacy-preserving data sharing" } ], "conditionalComponents": [ { "component": "privacy-tech", "condition": "For privacy-preserving beneficiary matching" } ], "crossCategoryDependencies": [ "UC-C-043 for beneficiary deduplication" ], "p2TriggerConditions": { "description": "Activated when P2 shows multi-org beneficiary focus + duplication concerns + coordination needs", "rangeSignals": [ "organisations >= 3+", "duplicationConcern >= true", "coordination >= important" ] }, "contextFieldsTemplate": [ { "field": "organisations", "source": "P0 partnerships", "description": "Number of NGOs" }, { "field": "beneficiaries", "source": "P2 programmes", "description": "Total beneficiary reach" }, { "field": "overlapRate", "source": "P2 assessment", "description": "Expected beneficiary overlap" }, { "field": "dataSharing", "source": "P0 agreements", "description": "Data sharing arrangements" } ], "implementationComplexity": "high", "examples": { "note": "Humanitarian coordination, cluster approaches", "references": [ { "name": "InterAction NGO Consortium Standards", "url": "https://www.interaction.org/article/standards/", "solved": "Collaborative standards for NGO data sharing and beneficiary coordination" }, { "name": "Common Humanitarian Data Standard (CHDS)", "url": "https://humanitarian.id/", "solved": "Standardised beneficiary deduplication protocol across humanitarian NGOs" }, { "name": "Hedera Hashgraph Multi-Party Governance", "url": "https://www.hedera.com/learning/governance", "solved": "Decentralised governance model for multi-stakeholder platforms" } ] }, "solutionQuestions": [ { "id": "coordination-scope", "type": "select", "options": [ { "label": "Information sharing only (data exchange without joint decision-making)", "value": "information-sharing" }, { "label": "Collaborative deduplication (shared beneficiary database)", "value": "shared-deduplication" }, { "label": "Joint beneficiary selection and targeting decisions", "value": "joint-targeting" }, { "label": "Integrated service delivery (co-implementation of programs)", "value": "integrated-delivery" } ], "propertyMapping": { "information-sharing": { "technologies": [ "Distributed ledger with read-only access", "API data feeds" ], "technologyProperties": { "accessControl": "Query-only permissions", "dataLatency": "Daily or weekly sync", "ownershipModel": "Each NGO owns their records" } }, "shared-deduplication": { "technologies": [ "Unified beneficiary registry", "Record matching algorithm" ], "technologyProperties": { "matchingCriteria": "Name, ID, biometrics", "duplicationDetection": "Automated fuzzy matching", "resolutionProcess": "NGOs decide which record canonical" } }, "joint-targeting": { "technologies": [ "Shared targeting ledger", "Multi-party decision voting" ], "technologyProperties": { "governanceModel": "Consensus or majority rule", "appealProcess": "Dispute resolution mechanism", "privacyBoundary": "Individual NGO data compartmentalized" } }, "integrated-delivery": { "technologies": [ "Unified service ledger", "Interoperability protocols" ], "technologyProperties": { "serviceCoordination": "Complementary non-duplicate services", "beneficiaryTracking": "Cross-NGO journey", "outcomeAggregation": "Collective impact measurement" } } }, "prefillFrom": null, "briefSection": "Coordination platform", "text": "What is the scope of cross-NGO coordination?", "ngoText": "What is the scope of cross-NGO coordination?" }, { "id": "data-sharing-model", "type": "select", "options": [ { "label": "Centralized database with role-based access control", "value": "centralized-database" }, { "label": "Shared digital register with selective data visibility", "value": "distributed-visibility" }, { "label": "Hashed or anonymized data with zero-knowledge proofs", "value": "anonymized-zk" }, { "label": "Query service without raw data sharing (federated learning)", "value": "federated-queries" } ], "propertyMapping": { "centralized-database": { "technologies": [ "Central database server", "Role-based access control" ], "technologyProperties": { "accessLog": "Immutable audit trail", "encryption": "At-rest and in-transit", "backupProcedure": "Documented retention policy" } }, "distributed-visibility": { "technologies": [ "Blockchain ledger", "Selective disclosure smart contract" ], "technologyProperties": { "recordOwnership": "Originating NGO", "visibilityRules": "Policy-defined sharing", "revocationCapability": "Withdraw consent" } }, "anonymized-zk": { "technologies": [ "Zero-knowledge proof system", "Hashing function" ], "technologyProperties": { "identifierRemoval": "Cryptographic hashing", "verifiability": "Proof without disclosure", "linkedIdentification": "Impossible without key" } }, "federated-queries": { "technologies": [ "Federated query engine", "Local data remains local" ], "technologyProperties": { "dataLocation": "Each NGO retains records", "queryResponse": "Aggregated result only", "computationModel": "Distributed without centralization" } } }, "prefillFrom": null, "briefSection": "Coordination platform", "text": "How will NGOs share beneficiary data securely?", "ngoText": "How will NGOs share beneficiary data securely?" }, { "id": "privacy-preservation", "type": "select", "options": [ { "label": "Minimal data sharing (only necessary fields for deduplication)", "value": "minimal-data" }, { "label": "Differential privacy (statistical noise added)", "value": "differential-privacy" }, { "label": "Secure multi-party computation (no single party sees raw data)", "value": "secure-mpc" }, { "label": "privacy-preserving computation (data stays encrypted during analysis) (computation on encrypted data)", "value": "homomorphic-encryption" } ], "propertyMapping": { "minimal-data": { "technologies": [ "Data minimization policy", "Field-level access control" ], "technologyProperties": { "dataFields": "Only name, ID, location", "auxiliaryData": "Never shared", "simplicityBenefit": "Easy to understand" } }, "differential-privacy": { "technologies": [ "Noise injection mechanism", "Privacy budget tracking" ], "technologyProperties": { "noiseMagnitude": "Calibrated to epsilon-delta", "queryLimits": "Budget exhaustion after K queries", "mathematicalGuarantee": "Formal privacy proof" } }, "secure-mpc": { "technologies": [ "Multiparty computation protocol", "Threshold secret sharing" ], "technologyProperties": { "computation": "Distributed across parties", "dataFusion": "No single party sees joined data", "overhead": "Higher computational cost" } }, "homomorphic-encryption": { "technologies": [ "Fully or partially homomorphic encryption", "Encrypted computation" ], "technologyProperties": { "computation": "On encrypted data directly", "rawDataAccess": "None required by other party", "scalability": "Limited by computational overhead" } } }, "prefillFrom": null, "briefSection": "Transparency and accountability", "text": "What privacy preservation techniques will protect beneficiary data?", "ngoText": "What privacy preservation techniques will protect beneficiary data?" }, { "id": "deduplication-logic", "type": "select", "options": [ { "label": "Deterministic matching on unique ID (national ID, biometric)", "value": "deterministic-id" }, { "label": "Probabilistic matching on name, age, location with human review", "value": "probabilistic-review" }, { "label": "Biometric matching (fingerprint or facial recognition)", "value": "biometric-matching" }, { "label": "Federated matching service without beneficiary data in one place", "value": "federated-matching" } ], "propertyMapping": { "deterministic-id": { "technologies": [ "ID database", "Deterministic hash matching" ], "technologyProperties": { "accuracy": "High (>99%) with valid IDs", "coverage": "Requires universal ID system", "falsePositives": "Minimal" } }, "probabilistic-review": { "technologies": [ "Record linkage algorithm", "Manual review queue" ], "technologyProperties": { "confidenceThreshold": "Matches above 85% score", "humanReview": "Lower-confidence matches reviewed", "errorRate": "Depends on review quality" } }, "biometric-matching": { "technologies": [ "Biometric enrollment", "Fingerprint or facial recognition database" ], "technologyProperties": { "accuracy": "High with quality enrollment", "privacyBurden": "Biometric data storage required", "costPerBeneficiary": "Higher than ID-based" } }, "federated-matching": { "technologies": [ "Distributed matching algorithm", "Interoperability standards" ], "technologyProperties": { "dataSharing": "No consolidated raw data", "matchResult": "Yes/no only, not merged record", "scalability": "High with distributed computation" } } }, "prefillFrom": null, "briefSection": "Coordination platform", "text": "How will beneficiary deduplication logic work?", "ngoText": "How will beneficiary deduplication logic work?" }, { "id": "cross-ngo-governance", "type": "select", "options": [ { "label": "Steering committee with rotating NGO representation", "value": "steering-committee" }, { "label": "Democratic voting (one NGO, one vote) on shared decisions", "value": "democratic-voting" }, { "label": "Consensus requirement (unanimous agreement or fallback to status quo)", "value": "consensus-based" }, { "label": "Arbitration by neutral third party on contested issues", "value": "third-party-arbitration" } ], "propertyMapping": { "steering-committee": { "technologies": [ "Committee registry", "Meeting protocol ledger" ], "technologyProperties": { "rotationSchedule": "Annual chair rotation", "quorum": "50% + 1 of NGOs", "decisionRecording": "Minutes in blockchain" } }, "democratic-voting": { "technologies": [ "Automated voting", "One-NGO-one-vote mechanism" ], "technologyProperties": { "votingPower": "Equal across all NGOs", "majorityThreshold": "50% + 1", "transparency": "Vote counts public per issue" } }, "consensus-based": { "technologies": [ "Consensus protocol", "Escalation to status quo" ], "technologyProperties": { "requirementLevel": "Full unanimity", "blockerRights": "Any NGO can block", "deescalation": "Mediation before fallback" } }, "third-party-arbitration": { "technologies": [ "Arbitration clause contract", "Neutral arbitrator registry" ], "technologyProperties": { "arbitratorSelection": "Pre-agreed list or random", "bindingDecision": "All parties agree in advance", "appealRight": "Limited or none" } } }, "prefillFrom": null, "briefSection": "Governance mechanism", "text": "How is governance and conflict resolution currently handled across NGOs?", "ngoText": "How is governance and conflict resolution currently handled across NGOs?" }, { "id": "coordination-layer-approach", "type": "select", "options": [ { "label": "Shared workspace with real-time multi-party visibility", "value": "shared-workspace" }, { "label": "Event-driven notifications across organisations", "value": "event-driven" }, { "label": "Scheduled data sync between partner systems", "value": "scheduled-sync" }, { "label": "system-connected integration between organisation systems", "value": "api-based" } ], "propertyMapping": { "shared-workspace": { "technologies": [ "Multi-party coordination layer", "Shared workspace platform", "Real-time data updates" ], "technologyProperties": { "coordinationMethod": "Shared real-time workspace", "dataSharing": "Full visibility within shared context", "latency": "Real-time" } }, "event-driven": { "technologies": [ "Event-driven coordination layer", "Cross-org notification service", "Event broker" ], "technologyProperties": { "coordinationMethod": "Event-driven notifications", "dataSharing": "Event-specific data only", "latency": "Near-real-time" } }, "scheduled-sync": { "technologies": [ "Scheduled coordination layer", "Batch data sync service", "Reconciliation engine" ], "technologyProperties": { "coordinationMethod": "Periodic batch sync", "dataSharing": "Agreed data sets", "latency": "Batch interval (hourly/daily)" } }, "api-based": { "technologies": [ "API coordination layer", "Organisation API gateway", "Data exchange protocol" ], "technologyProperties": { "coordinationMethod": "API-based request/response", "dataSharing": "Per-request basis", "latency": "On-demand" } } }, "prefillFrom": null, "briefSection": "Multi-party coordination", "text": "How do multiple parties currently coordinate decisions and actions?", "ngoText": "How do multiple parties currently coordinate decisions and actions?" } ], "complexityFactors": { "relationships": 4, "operationalChange": 4, "dataCompliance": 4 }, "suggestedCriteria": [ { "id": "SC-COORD-DEDUP", "name": "Privacy-Preserving Deduplication", "description": "The system can detect that the same beneficiary is registered with multiple organisations WITHOUT requiring any organisation to share their beneficiary database. This is the core technical challenge of cross-NGO coordination.", "weight": 0.3, "ratingGuide": { "5": "Zero-knowledge or cryptographic deduplication \u2014 proves overlap exists without revealing any personal data between organisations. Each NGO retains full data sovereignty.", "4": "Privacy-preserving record linkage using hashed identifiers or secure multi-party computation. Minimal data exposure between parties.", "3": "Pseudonymised matching \u2014 hashed identifiers shared but with some re-identification risk through linkage attacks.", "2": "Trusted third party holds consolidated data for deduplication. Data sovereignty partially ceded.", "1": "Organisations must share beneficiary lists directly for deduplication. Full data exposure." } }, { "id": "SC-COORD-SOVR", "name": "Data Sovereignty & Organisational Autonomy", "description": "Does each participating NGO retain full control over their own data, with the coordination layer accessing only what is strictly necessary for gap/overlap detection?", "weight": 0.25, "ratingGuide": { "5": "Full data sovereignty \u2014 each NGO's data stays within their own systems. Coordination layer sees only cryptographic proofs, never raw data. Any NGO can withdraw without data loss.", "4": "Data remains with originating NGO. Coordination layer accesses minimal derived data (hashes, tokens). Clear data deletion on withdrawal.", "3": "Some data replicated to coordination layer but access restricted. Data ownership documented. Withdrawal process defined but complex.", "2": "Significant data centralisation in coordination platform. Organisational autonomy limited by platform dependencies.", "1": "Full data centralisation required. Organisations cede control to coordination platform." } }, { "id": "SC-COORD-INTEROP", "name": "Interoperability Across Diverse Systems", "description": "Can the coordination layer work with the varied registration and case management systems that different NGOs actually use (field data collection tools, case management systems, spreadsheets)?", "weight": 0.2, "ratingGuide": { "5": "Pre-built connectors for major humanitarian platforms. API-based integration. Supports custom system integration. Works with spreadsheet/CSV as fallback.", "4": "API integration with multiple systems. Standard data exchange formats. Some manual configuration for less common systems.", "3": "Supports standard data formats (CSV, JSON) with import/export. Limited native integrations. Manual data preparation for some systems.", "2": "Single integration method. Requires all partners to adapt their data to the platform's format.", "1": "No integration capability. Requires manual re-entry of data from other systems." } }, { "id": "SC-COORD-CONSENT", "name": "Beneficiary Consent & Data Protection", "description": "Does the system ensure that beneficiaries have given informed consent for their data to be used in cross-organisation coordination, and can they withdraw consent?", "weight": 0.15, "ratingGuide": { "5": "Granular consent management \u2014 beneficiaries can consent to specific coordination uses while refusing others. Consent recorded immutably. Withdrawal automated across all participating NGOs.", "4": "Informed consent recorded with purpose limitation. Withdrawal process defined and tracked. Consent status visible to all parties.", "3": "Consent captured at registration but not granular. Withdrawal possible but requires manual processing across organisations.", "2": "Blanket consent assumed or buried in programme enrolment. Withdrawal process unclear.", "1": "No consent mechanism for cross-organisation data use." } }, { "id": "SC-COORD-GAPS", "name": "Gap Detection & Coverage Mapping", "description": "Beyond deduplication, can the system identify underserved populations or geographic areas where NO organisation is providing needed services?", "weight": 0.1, "ratingGuide": { "5": "Automated coverage mapping with gap analysis. Identifies underserved populations by geography, demographics, and service type. Real-time dashboard. Alerts for emerging gaps.", "4": "Coverage analysis across participating organisations. Geographic and service-type gap identification. Periodic reports.", "3": "Aggregate coverage data available. Basic gap identification through manual analysis of coordination data.", "2": "Overlap detection only. No systematic gap analysis capability.", "1": "No coverage mapping or gap detection. System only identifies duplicates." } } ], "procurement": { "marketMaturity": "nascent", "primaryMode": "consortium", "alternativeModes": [ "integrator-led" ], "reasoning": "Cross-NGO beneficiary coordination is research-stage; consortium structures common.", "exampleProductCategories": [ "interagency-coordination-platform", "cross-org-deduplication-rails" ], "partnerChannels": [], "lastReviewed": "2026-05-01" } }, { "id": "UC-E-074", "name": "Cluster coordination record-keeping", "category": "E", "subcategory": "Coordination", "description": "Keep the decisions and actions from coordination meetings in a record that cannot be edited afterwards, so everyone agrees on what was decided.", "bCriteria": [ "B1", "B3" ], "requiredComponents": [ { "component": "record-keeping-platform", "description": "Cluster coordination records" }, { "component": "coordination-layer", "description": "Cluster coordination system" }, { "component": "decision-audit-trail", "description": "Cluster decision audit trail" }, { "component": "reporting-module", "description": "Cluster reporting" } ], "conditionalComponents": [ { "component": "smart-contracts", "condition": "If automated cluster decisions" } ], "crossCategoryDependencies": [], "p2TriggerConditions": { "description": "Activated when P2 shows cluster participation + coordination records + transparency needs", "rangeSignals": [ "clusterParticipation >= true", "documentationBurden >= high", "transparencyNeeded >= true" ] }, "contextFieldsTemplate": [ { "field": "clusters", "source": "P0 cluster involvement", "description": "Clusters participated in" }, { "field": "meetings", "source": "P2 coordination frequency", "description": "Meeting frequency" }, { "field": "decisions", "source": "P2 cluster scope", "description": "Type of decisions made" }, { "field": "members", "source": "P0 partnerships", "description": "Cluster member organisations" } ], "implementationComplexity": "low-medium", "examples": { "note": "Humanitarian cluster coordination", "references": [ { "name": "IASC (Inter-Agency Standing Committee) Cluster Coordination", "url": "https://www.humanitarianresponse.info/en/coordination/clusters", "solved": "Standardised cluster coordination model with decision documentation and information sharing" }, { "name": "Humanitarian Response Platform", "url": "https://www.humanitarianresponse.info/", "solved": "Centralised platform for cluster messaging, documents, and decision tracking" }, { "name": "Blockchain-Based Cluster Coordination", "url": "https://www.unwfp.org/technology/blockchain", "solved": "Decentralised record-keeping for multi-organisation cluster decisions" } ] }, "solutionQuestions": [ { "id": "cluster-type", "type": "select", "options": [ { "label": "Geographic cluster (all NGOs in a region/country)", "value": "geographic-cluster" }, { "label": "Sectoral cluster (all NGOs in health, food security, shelter, etc.)", "value": "sectoral-cluster" }, { "label": "Emergency response cluster (ad-hoc coalitions for crisis response)", "value": "emergency-cluster" }, { "label": "Multi-level cluster (regional and sectoral combined)", "value": "multilevel-cluster" } ], "propertyMapping": { "geographic-cluster": { "technologies": [ "Geolocation registry", "Country/region coordination ledger" ], "technologyProperties": { "boundaryDefinition": "Geographic coordinates or admin boundaries", "membershipRule": "Operations in geography", "scalability": "Fixed per region" } }, "sectoral-cluster": { "technologies": [ "Sector classification registry", "Sectoral coordination ledger" ], "technologyProperties": { "sectorDefinition": "Health, WASH, FSL, Protection, etc.", "crossClusterLinks": "Connectivity to other sectors", "specialization": "Sector-specific standards" } }, "emergency-cluster": { "technologies": [ "Emergency trigger protocol", "Dynamic cluster formation" ], "technologyProperties": { "activationCriteria": "Crisis declaration", "membershipDuration": "Crisis period only", "rapidFormation": "Days to activate" } }, "multilevel-cluster": { "technologies": [ "Hierarchical cluster registry", "Cross-cluster coordination ledger" ], "technologyProperties": { "nesting": "Regional clusters within sectoral", "communication": "Both vertical and horizontal", "complexity": "High governance overhead" } } }, "prefillFrom": null, "briefSection": "Coordination platform", "text": "What type of cluster coordination are you managing?", "ngoText": "What type of cluster coordination are you managing?" }, { "id": "decision-recording", "type": "select", "options": [ { "label": "Meeting minutes ledger with consensus recorded", "value": "meeting-minutes" }, { "label": "Voting record with member consent documented", "value": "voting-record" }, { "label": "Action item tracker with assignment and completion log", "value": "action-tracker" }, { "label": "automated rules recording decisions automatically digital", "value": "smart-contract-record" } ], "propertyMapping": { "meeting-minutes": { "technologies": [ "Meeting notes ledger", "Attendance registry" ], "technologyProperties": { "recordFormat": "Verbatim or summary", "distributionFrequency": "Within 48 hours", "amendmentProcess": "30-day comment period" } }, "voting-record": { "technologies": [ "Voting ledger", "Member consent attestation" ], "technologyProperties": { "votingMethod": "Show of hands, roll call, or secret", "resultRecording": "Vote counts public", "personalVote": "Optional: member vote recorded" } }, "action-tracker": { "technologies": [ "Action item registry", "Completion verification ledger" ], "technologyProperties": { "assignmentTracking": "Owner and deadline recorded", "statusUpdates": "Weekly or biweekly", "completionVerification": "Evidence required" } }, "smart-contract-record": { "technologies": [ "Decision smart contract", "Blockchain timestamp" ], "technologyProperties": { "automatedRecording": "Digital immediately", "immutability": "Permanent record", "transparencyLevel": "Full history visible" } } }, "prefillFrom": null, "briefSection": "Coordination platform", "text": "How will cluster decisions be recorded and tracked?", "ngoText": "How will cluster decisions be recorded and tracked?" }, { "id": "information-sharing", "type": "select", "options": [ { "label": "Strategic only: policies, decisions, coordination documents", "value": "strategic-only" }, { "label": "Operational: activities, locations, beneficiary numbers", "value": "operational" }, { "label": "Real-time: immediate incident reports and urgent updates", "value": "realtime" }, { "label": "Tiered sharing: members choose what to share at what level", "value": "tiered-sharing" } ], "propertyMapping": { "strategic-only": { "technologies": [ "Strategic documents registry", "Read-only access" ], "technologyProperties": { "dataTypes": "Policies and decisions", "accessControl": "All cluster members", "sensitivity": "Low confidentiality requirement" } }, "operational": { "technologies": [ "Activity registry", "Beneficiary tracking ledger" ], "technologyProperties": { "dataTypes": "Activities, locations, beneficiary counts", "granularity": "Activity level", "updateFrequency": "Monthly or quarterly" } }, "realtime": { "technologies": [ "Incident reporting system", "Alert protocol" ], "technologyProperties": { "reportingLatency": "Hours to immediate", "urgencyLevels": "Critical, high, medium, low", "accessControl": "Security clearance required" } }, "tiered-sharing": { "technologies": [ "Consent management contract", "Privacy control interface" ], "technologyProperties": { "granularity": "Member-defined sharing preferences", "flexibility": "Change permissions anytime", "transparency": "Other members see access log" } } }, "prefillFrom": null, "briefSection": "Coordination platform", "text": "What information will be shared among cluster members?", "ngoText": "What information will be shared among cluster members?" }, { "id": "cluster-participant-count", "type": "select", "options": [ { "label": "2\u20135 parties", "value": "small" }, { "label": "6\u201315 parties", "value": "medium" }, { "label": "16\u201350 parties", "value": "large" }, { "label": "Over 50 parties", "value": "enterprise" } ], "propertyMapping": { "small": { "technologies": [ "Simple shared ledger" ], "technologyProperties": { "consensusComplexity": "Low", "governanceModel": "Direct" } }, "medium": { "technologies": [ "Permissioned network", "Role-based access" ], "technologyProperties": { "consensusComplexity": "Medium", "governanceModel": "Committee-based" } }, "large": { "technologies": [ "Scalable permissioned network", "Delegated consensus" ], "technologyProperties": { "consensusComplexity": "High", "governanceModel": "Delegated" } }, "enterprise": { "technologies": [ "Enterprise consortium platform", "Federated consensus" ], "technologyProperties": { "consensusComplexity": "Very high", "governanceModel": "Federated" } } }, "prefillFrom": null, "briefSection": "Governance mechanism", "text": "How many organisations or stakeholders participate in cluster coordination?", "ngoText": "How many organisations or stakeholders participate in cluster coordination?" }, { "id": "cluster-decision-freq", "type": "select", "options": [ { "label": "Daily or more", "value": "daily" }, { "label": "Weekly", "value": "weekly" }, { "label": "Monthly", "value": "monthly" }, { "label": "Quarterly or less", "value": "quarterly" } ], "propertyMapping": { "daily": { "technologies": [ "Automated record creation", "Real-time sync" ], "technologyProperties": { "throughput": "High", "automation": "Required" } }, "weekly": { "technologies": [ "Scheduled sync" ], "technologyProperties": { "throughput": "Medium", "automation": "Recommended" } }, "monthly": { "technologies": [ "Batch processing acceptable" ], "technologyProperties": { "throughput": "Low", "automation": "Optional" } }, "quarterly": { "technologies": [], "technologyProperties": { "throughput": "Minimal", "automation": "Not required" } } }, "prefillFrom": null, "briefSection": "Coordination platform", "text": "How frequently are cluster coordination decisions or records created?", "ngoText": "How frequently are cluster coordination decisions or records created?" } ], "complexityFactors": { "relationships": 3, "operationalChange": 2, "dataCompliance": 1 }, "suggestedCriteria": [ { "id": "SC-CLUST-IMMUT", "name": "Immutable Decision Record", "description": "Are cluster meeting decisions, action items, and commitments recorded in a way that cannot be retroactively altered, ensuring accountability for what was agreed?", "weight": 0.3, "ratingGuide": { "5": "Every decision timestamped and stored on immutable ledger. Action items linked to responsible parties. Amendments logged as separate entries \u2014 original record preserved.", "4": "Blockchain-anchored decision records. Corrections require documented rationale and multi-party approval.", "3": "Append-only decision log with integrity checks. Some administrative override capability but logged.", "2": "Decision records stored in editable documents with version history. Integrity depends on document management discipline.", "1": "Meeting minutes in editable format with no version control or integrity guarantees." } }, { "id": "SC-CLUST-TRACK", "name": "Action Item Tracking & Accountability", "description": "Can the system track commitments made in cluster meetings through to completion, making it visible when organisations have or have not delivered on their pledges?", "weight": 0.25, "ratingGuide": { "5": "Automated action item tracking from assignment to completion. Status visible to all cluster members. Overdue items flagged automatically. Historical completion rates per organisation visible.", "4": "Structured action tracking with status updates. Visibility across cluster members. Periodic overdue reminders.", "3": "Action items recorded with responsible parties. Manual status tracking. Periodic review in cluster meetings.", "2": "Action items noted in meeting minutes but no systematic tracking. Follow-up depends on cluster lead initiative.", "1": "No action item tracking beyond meeting minutes." } }, { "id": "SC-CLUST-ACCESS", "name": "Multi-Agency Access & Information Sharing", "description": "Can the system provide appropriate access to cluster records for all participating organisations, including late-joining members, while protecting operationally sensitive information?", "weight": 0.2, "ratingGuide": { "5": "Role-based access with granular permissions. Full history accessible to authorised new members. Sensitive information compartmentalised. Works across different organisational IT environments.", "4": "Tiered access control. Historical records available to new members. Basic information classification supported.", "3": "Shared access platform with basic permissions. Historical access for new members may be limited. Single access tier.", "2": "Records shared via email or file sharing. Access management informal. Historical records difficult to locate.", "1": "No systematic information sharing. Records maintained by cluster lead only." } }, { "id": "SC-CLUST-STANDARD", "name": "Humanitarian Standards Alignment", "description": "Does the system align with established humanitarian coordination standards (OCHA cluster approach, IASC guidelines, Sphere Standards) and reporting requirements?", "weight": 0.15, "ratingGuide": { "5": "Pre-configured for OCHA cluster reporting requirements. Supports 3W/4W reporting, IASC coordination frameworks, and Sphere Standards monitoring. Tested in active humanitarian responses.", "4": "Supports major humanitarian reporting formats. Configurable for different cluster types. Some active response deployment experience.", "3": "General coordination platform adaptable to humanitarian context. Manual configuration for specific standards.", "2": "Generic project management tool not specifically designed for humanitarian coordination. Requires significant customisation.", "1": "No awareness of humanitarian coordination standards or requirements." } }, { "id": "SC-CLUST-FIELD", "name": "Field Operability & Low-Resource Environments", "description": "Can the system function in the challenging connectivity and infrastructure environments typical of humanitarian responses, including offline access and low-bandwidth operation?", "weight": 0.1, "ratingGuide": { "5": "Full offline functionality with automatic sync. Works on basic devices (feature phones, low-end smartphones). Sub-100kbps bandwidth sufficient. Tested in active crisis responses.", "4": "Offline read access with queued updates. Mobile-optimised. Functions on intermittent connectivity.", "3": "Low-bandwidth web interface. Some offline caching. Requires periodic connectivity for updates.", "2": "Standard web application requiring reliable internet. Mobile-responsive but bandwidth-heavy.", "1": "Desktop-only, requires high-speed internet. Not suitable for field environments." } } ], "procurement": { "marketMaturity": "mature", "primaryMode": "off-the-shelf", "alternativeModes": [ "rfq" ], "reasoning": "Cluster coordination overlaps with general workflow and document SaaS.", "exampleProductCategories": [ "workflow-saas", "document-management-platform" ], "partnerChannels": [], "lastReviewed": "2026-05-01" } }, { "id": "UC-E-075", "name": "Beneficiary feedback and complaints mechanisms", "category": "E", "subcategory": "Community Engagement", "description": "Give people a way to raise complaints and see that they were received and acted on, with a record that cannot be lost or changed.", "bCriteria": [ "B1", "B3" ], "requiredComponents": [ { "component": "accountability-tools", "description": "Feedback collection system" }, { "component": "record-keeping-platform", "description": "Feedback records" }, { "component": "reporting-module", "description": "Feedback reporting and analysis" }, { "component": "decision-audit-trail", "description": "Feedback action audit trail" } ], "conditionalComponents": [ { "component": "anonymisation-tools", "condition": "If anonymous feedback needed" } ], "crossCategoryDependencies": [], "p2TriggerConditions": { "description": "Activated when P2 shows accountability focus + community voice need + feedback integration", "rangeSignals": [ "accountability >= high", "communityVoice >= important", "feedbackUse >= systematic" ] }, "contextFieldsTemplate": [ { "field": "beneficiaries", "source": "P2 programme scale", "description": "Community members" }, { "field": "channels", "source": "P2 engagement methods", "description": "Feedback collection methods" }, { "field": "frequency", "source": "P2 feedback cycle", "description": "Feedback collection frequency" }, { "field": "actionRequired", "source": "P2 commitments", "description": "Commitment to act on feedback" } ], "implementationComplexity": "low-medium", "examples": { "note": "Community accountability mechanisms", "references": [ { "name": "USAID Community Feedback and Response (CFR) Initiative", "url": "https://www.usaid.gov/accountability/community-feedback", "solved": "Multi-channel feedback collection with tracked responses and community accountability" }, { "name": "Humanitarian Feedback Portal", "url": "https://feedback.humanitarianresponse.info/", "solved": "Platform for communities to provide feedback on humanitarian assistance with response tracking" }, { "name": "Blockchain Feedback System for Social Programs", "url": "https://www.worldbank.org/en/topic/ict", "solved": "Immutable feedback record with public accountability on action taken" } ] }, "solutionQuestions": [ { "id": "feedback-channels", "type": "select", "options": [ { "label": "Community meetings and focus group discussions", "value": "community-meetings" }, { "label": "Anonymous suggestion boxes (physical or digital)", "value": "suggestion-boxes" }, { "label": "SMS-based feedback polls accessible via any phone", "value": "sms-feedback" }, { "label": "Mobile application for structured feedback and surveys", "value": "mobile-app" }, { "label": "Multi-channel approach (combination of above)", "value": "multi-channel" } ], "propertyMapping": { "community-meetings": { "technologies": [ "Meeting attendance ledger", "Notes transcription" ], "technologyProperties": { "frequency": "Quarterly or as-needed", "inclusivity": "Open to all community members", "documentation": "Meeting summary recorded" } }, "suggestion-boxes": { "technologies": [ "Anonymous submission system", "Anonymity verification" ], "technologyProperties": { "anonymity": "Complete identity protection", "accessControl": "Limited custodians", "chainOfCustody": "Documented handling" } }, "sms-feedback": { "technologies": [ "SMS gateway", "Response aggregation system" ], "technologyProperties": { "accessibility": "Any mobile phone", "language": "Multiple language support", "costBarrier": "Low or free" } }, "mobile-app": { "technologies": [ "Mobile feedback application", "Response tracking" ], "technologyProperties": { "userFriendliness": "Simple interface for low literacy", "dataCollection": "Structured surveys", "offline": "Stores responses when offline" } }, "multi-channel": { "technologies": [ "Feedback aggregation platform", "Channel integration" ], "technologyProperties": { "channelCount": "3+ options", "accessibilityTier": "Reaches all literacy levels", "integration": "All responses in one system" } } }, "prefillFrom": null, "briefSection": "Transparency and accountability", "text": "Do donors or community members require visibility into feedback received and how it shaped program changes?", "ngoText": "Do donors or community members require visibility into feedback received and how it shaped program changes?" }, { "id": "feedback-anonymity", "type": "select", "options": [ { "label": "Full anonymity: no identifying information collected", "value": "full-anonymity" }, { "label": "Optional anonymity: submitter can choose to identify", "value": "optional-anonymity" }, { "label": "Contact information for follow-up but not for enforcement", "value": "contact-follow-up" }, { "label": "Identified feedback with protection against retaliation", "value": "identified-protected" } ], "propertyMapping": { "full-anonymity": { "technologies": [ "Anonymous submission protocol", "No ID collection" ], "technologyProperties": { "identityCollection": "None", "correlationResistance": "High", "traceability": "Impossible" } }, "optional-anonymity": { "technologies": [ "User-controlled disclosure", "Optional identity field" ], "technologyProperties": { "userChoice": "Individual decides", "followUp": "Possible for identified feedback", "defaultBehavior": "Anonymous unless opted in" } }, "contact-follow-up": { "technologies": [ "Contact information collection", "Separate from feedback" ], "technologyProperties": { "collectionPurpose": "Follow-up only", "enforcement": "Not used for action against submitter", "transparency": "Clear policy stated" } }, "identified-protected": { "technologies": [ "Identity verification", "Retaliation protection protocol" ], "technologyProperties": { "identification": "Required for accountability", "protectionMeasures": "Anti-retaliation safeguards", "transparency": "Feedback submitter known to management" } } }, "prefillFrom": null, "briefSection": "Transparency and accountability", "text": "What anonymity level will be offered for feedback?", "ngoText": "What anonymity level will be offered for feedback?" }, { "id": "response-tracking", "type": "select", "options": [ { "label": "Feedback response log with documented action plan", "value": "response-log" }, { "label": "Public dashboard showing feedback received and status", "value": "public-dashboard" }, { "label": "Periodic feedback report shared back with community", "value": "feedback-report" }, { "label": "Automated tracking system with community notifications", "value": "automated-tracking" } ], "propertyMapping": { "response-log": { "technologies": [ "Response ledger", "Action plan documentation" ], "technologyProperties": { "trackingFormat": "Feedback \u2192 Response \u2192 Action", "timelineRecording": "Dates and deadlines", "ownershipAssignment": "Responsible person assigned" } }, "public-dashboard": { "technologies": [ "Community feedback dashboard", "Status visualization" ], "technologyProperties": { "accessControl": "Open to all community members", "updateFrequency": "Real-time or daily", "statusCategories": "Received, In progress, Completed" } }, "feedback-report": { "technologies": [ "Aggregated feedback report", "Periodic distribution" ], "technologyProperties": { "reportingFrequency": "Quarterly or semi-annual", "contentCoverage": "Summary of themes and responses", "communicationMethod": "Community meetings or printed copies" } }, "automated-tracking": { "technologies": [ "Feedback management system", "Notification bot" ], "technologyProperties": { "automatedNotification": "Submitter updated on status", "updateFrequency": "On action completion", "transparency": "What was done and why" } } }, "prefillFrom": null, "briefSection": "Transparency and accountability", "text": "How will feedback responses and actions be tracked?", "ngoText": "How will feedback responses and actions be tracked?" }, { "id": "comm-feedback-participant-count", "type": "select", "options": [ { "label": "2\u20135 parties", "value": "small" }, { "label": "6\u201315 parties", "value": "medium" }, { "label": "16\u201350 parties", "value": "large" }, { "label": "Over 50 parties", "value": "enterprise" } ], "propertyMapping": { "small": { "technologies": [ "Simple shared ledger" ], "technologyProperties": { "consensusComplexity": "Low", "governanceModel": "Direct" } }, "medium": { "technologies": [ "Permissioned network", "Role-based access" ], "technologyProperties": { "consensusComplexity": "Medium", "governanceModel": "Committee-based" } }, "large": { "technologies": [ "Scalable permissioned network", "Delegated consensus" ], "technologyProperties": { "consensusComplexity": "High", "governanceModel": "Delegated" } }, "enterprise": { "technologies": [ "Enterprise consortium platform", "Federated consensus" ], "technologyProperties": { "consensusComplexity": "Very high", "governanceModel": "Federated" } } }, "prefillFrom": null, "briefSection": "Governance mechanism", "text": "How many organisations or stakeholders participate in the feedback process?", "ngoText": "How many organisations or stakeholders participate in the feedback process?" }, { "id": "sq-UC-E-075-003", "type": "single-select", "options": [ { "value": "24-hour-acknowledgement", "label": "24-hour acknowledgement" }, { "value": "72-hour-response", "label": "72-hour response" }, { "value": "weekly-review", "label": "Weekly review" }, { "value": "no-sla-best-effort", "label": "No SLA, best effort" }, { "value": "tiered-by-severity", "label": "Tiered by severity" } ], "propertyMapping": { "24-hour-acknowledgement": { "technologies": [ "timer-system", "auto-acknowledgement" ], "technologyProperties": {} }, "72-hour-response": { "technologies": [ "sla-tracking", "escalation-reminder" ], "technologyProperties": {} }, "weekly-review": { "technologies": [ "batch-processing", "weekly-schedule" ], "technologyProperties": {} }, "no-sla-best-effort": { "technologies": [ "basic-tracking", "no-sla" ], "technologyProperties": {} }, "tiered-by-severity": { "technologies": [ "sla-rules", "severity-tiers" ], "technologyProperties": {} } }, "briefSection": "operations", "text": "What response time commitments should be tracked for feedback resolution?", "ngoText": "What response time commitments should be tracked for feedback resolution?" }, { "id": "accountability-approach", "type": "select", "options": [ { "label": "Public dashboard with real-time transparency metrics", "value": "public-dashboard" }, { "label": "Stakeholder-restricted reporting portal", "value": "stakeholder-portal" }, { "label": "Community-facing feedback and verification system", "value": "community-facing" }, { "label": "Automated compliance scoring and alerts", "value": "automated-scoring" } ], "propertyMapping": { "public-dashboard": { "technologies": [ "Public accountability dashboard", "Transparency metrics engine", "Accountability reporting tools" ], "technologyProperties": { "visibility": "Public / open access", "updateFrequency": "Real-time or daily", "feedbackLoop": "Public comment / rating system" } }, "stakeholder-portal": { "technologies": [ "Stakeholder accountability portal", "Role-based reporting engine", "Accountability reporting tools" ], "technologyProperties": { "visibility": "Registered stakeholders only", "updateFrequency": "On-demand with scheduled reports", "feedbackLoop": "Stakeholder feedback channel" } }, "community-facing": { "technologies": [ "Community accountability platform", "Beneficiary feedback module", "Accountability reporting tools" ], "technologyProperties": { "visibility": "Community members and beneficiaries", "updateFrequency": "Event-driven", "feedbackLoop": "SMS/app-based feedback collection" } }, "automated-scoring": { "technologies": [ "Automated accountability scoring engine", "Compliance alert service", "Accountability reporting tools" ], "technologyProperties": { "visibility": "Internal with escalation alerts", "updateFrequency": "Continuous monitoring", "feedbackLoop": "Automated alerts on non-compliance" } } }, "prefillFrom": null, "briefSection": "Accountability", "text": "What accountability and transparency mechanisms are needed?", "ngoText": "What accountability and transparency mechanisms are needed?", "hidden": true }, { "id": "reporting-approach", "type": "select", "options": [ { "label": "Automated donor/funder reporting with scheduled delivery", "value": "automated-donor" }, { "label": "Self-service dashboard with custom report builder", "value": "self-service" }, { "label": "Regulatory compliance reporting (government/authority)", "value": "regulatory" }, { "label": "Multi-audience reporting (donors, government, community)", "value": "multi-audience" } ], "propertyMapping": { "automated-donor": { "technologies": [ "Automated reporting module", "Donor report template engine", "Scheduled report delivery service" ], "technologyProperties": { "reportAudience": "Donors and funders", "frequency": "Scheduled (monthly/quarterly)", "format": "PDF/spreadsheet with blockchain verification" } }, "self-service": { "technologies": [ "Self-service reporting module", "Custom report builder", "Data visualisation engine" ], "technologyProperties": { "reportAudience": "Internal staff and managers", "frequency": "On-demand", "format": "Interactive dashboard + export" } }, "regulatory": { "technologies": [ "Regulatory reporting module", "Compliance report generator", "Authority submission gateway" ], "technologyProperties": { "reportAudience": "Government and regulatory authorities", "frequency": "As required by regulation", "format": "Authority-specified format" } }, "multi-audience": { "technologies": [ "Multi-audience reporting module", "Role-based report engine", "Report distribution service" ], "technologyProperties": { "reportAudience": "Multiple stakeholders", "frequency": "Varies by audience", "format": "Tailored per audience" } } }, "prefillFrom": null, "briefSection": "Reporting", "text": "What reporting capabilities does this solution need?", "ngoText": "What reporting capabilities does this solution need?" }, { "id": "decision-audit-trail", "type": "select", "options": [ { "label": "Full decision log: every vote, rationale, and outcome recorded", "value": "full-log" }, { "label": "Outcome-only: record final decisions and who approved", "value": "outcome-only" }, { "label": "Anonymised voting with verifiable tallies", "value": "anonymised-voting" }, { "label": "Not sure, need guidance", "value": "guidance-needed" } ], "propertyMapping": { "full-log": { "technologies": [ "Full decision audit trail", "Deliberation recording service", "Decision verification portal" ], "technologyProperties": { "recordGranularity": "Every vote, rationale, outcome", "transparency": "Full \u2014 all participants can verify", "privacy": "Named votes on record" } }, "outcome-only": { "technologies": [ "Outcome-based decision audit trail", "Approval chain logger", "Decision verification portal" ], "technologyProperties": { "recordGranularity": "Final decisions and approvers only", "transparency": "Outcome transparency", "privacy": "Deliberations private, outcomes public" } }, "anonymised-voting": { "technologies": [ "Anonymised decision audit trail", "Zero-knowledge voting module", "Tally verification service" ], "technologyProperties": { "recordGranularity": "Verifiable tallies without individual votes", "transparency": "Outcome verifiable, individual votes private", "privacy": "Full voter privacy" } }, "guidance-needed": { "technologies": [ "Decision audit trail framework", "Decision verification portal" ], "technologyProperties": { "recordGranularity": "To be determined", "transparency": "To be determined", "privacy": "To be determined" } } }, "prefillFrom": null, "briefSection": "Decision transparency", "text": "How are governance decisions currently recorded and verified?", "ngoText": "How are governance decisions currently recorded and verified?" } ], "complexityFactors": { "relationships": 2, "operationalChange": 2, "dataCompliance": 2 }, "suggestedCriteria": [ { "id": "SC-FB-ANON", "name": "Feedback Anonymity & Safety", "description": "Community members can provide honest feedback, including complaints about staff or programme failures, without fear of identification or retaliation. Anonymity is essential for genuine accountability.", "weight": 0.3, "ratingGuide": { "5": "Cryptographically anonymous feedback submission. Even system administrators cannot link feedback to individuals. Multiple anonymous channels (SMS, voice, digital). Anti-retaliation monitoring.", "4": "Strong pseudonymous feedback with encrypted submission. Multiple channels. De-anonymisation requires extraordinary measures.", "3": "Confidential feedback \u2014 identity known to designated staff member who commits to confidentiality. Some anonymous channels available.", "2": "Feedback collected with names but confidentiality promised. Limited anonymous options.", "1": "All feedback attributable to named individuals. No anonymity protection." } }, { "id": "SC-FB-CLOSE", "name": "Feedback Loop Closure & Response Tracking", "description": "The system ensures that every piece of feedback receives a response, and that communities can see that their input led to action. Unclosed feedback loops erode trust rapidly.", "weight": 0.25, "ratingGuide": { "5": "Every feedback item tracked from receipt through investigation to resolution. Community-facing dashboard showing aggregate response rates and actions taken. Automated escalation for overdue items.", "4": "Structured tracking with status visibility. Response timelines defined and monitored. Regular reporting to communities on actions taken.", "3": "Feedback logged and tracked. Responses provided but community visibility limited. Periodic summaries shared.", "2": "Feedback collected but tracking is informal. Response provided when possible but no systematic follow-up.", "1": "Feedback collected with no systematic tracking or response mechanism." } }, { "id": "SC-FB-ACCESS", "name": "Inclusive Multi-Channel Access", "description": "Can community members provide feedback through channels appropriate to their context, including non-digital options for communities with limited technology access?", "weight": 0.2, "ratingGuide": { "5": "Multiple integrated channels: SMS/USSD, voice/IVR, in-person (with digital capture), mobile app, web. All channels feed into unified tracking. Local language support.", "4": "Three or more channels including at least one non-digital option. Unified tracking across channels. Some local language support.", "3": "Two channels (e.g., mobile app + SMS). Tracking may differ between channels. Limited language support.", "2": "Single digital channel (app or web form). Requires smartphone and internet access.", "1": "Single channel requiring technical knowledge. Not accessible to most community members." } }, { "id": "SC-FB-IMMUT", "name": "Feedback Record Integrity", "description": "Are feedback records stored immutably, ensuring that complaints cannot be deleted or altered by the staff or organisation being complained about?", "weight": 0.15, "ratingGuide": { "5": "All feedback cryptographically timestamped and stored on immutable ledger. Deletion impossible. Any status changes logged with full audit trail.", "4": "Append-only storage with tamper detection. Status changes logged. Deletion requires multi-party authorisation and is logged.", "3": "Database with audit logging. Deletion restricted but technically possible for administrators.", "2": "Standard database storage. Deletion possible by authorised staff. Audit trail may have gaps.", "1": "Editable records with no integrity guarantees. Feedback can be deleted without trace." } }, { "id": "SC-FB-ANALYSE", "name": "Pattern Analysis & Systemic Issue Detection", "description": "Can the system aggregate feedback to identify systemic issues (patterns across locations, time periods, or programme areas that indicate structural problems rather than isolated incidents)?", "weight": 0.1, "ratingGuide": { "5": "Automated pattern detection with trend analysis. Geographic and temporal clustering. Severity escalation for systemic issues. Dashboard for programme managers and senior leadership.", "4": "Categorised feedback with filtering and aggregation. Manual analysis supported by good data structure. Periodic trend reports.", "3": "Feedback categorised by type. Basic filtering and counting. Manual analysis required for pattern identification.", "2": "Feedback stored as unstructured text. Analysis requires manual review of individual entries.", "1": "No analytical capability. Feedback reviewed only as individual items." } } ], "procurement": { "marketMaturity": "mature", "primaryMode": "off-the-shelf", "alternativeModes": [ "conversation-guide" ], "reasoning": "Beneficiary feedback SaaS market is mature.", "exampleProductCategories": [ "feedback-platform", "community-engagement-saas" ], "partnerChannels": [], "lastReviewed": "2026-05-01" } }, { "id": "UC-E-076", "name": "Local partner capacity verification", "category": "E", "subcategory": "Partner Due Diligence", "description": "Check and record the qualifications and training of local partners, so you can confirm their claims instead of relying on documents alone.", "bCriteria": [ "B1", "B3", "B6" ], "requiredComponents": [ { "component": "record-keeping-platform", "description": "Partner capacity records" }, { "component": "verification-mechanism", "description": "Capacity verification proofs" }, { "component": "credential-issuance", "description": "Capacity credentials" }, { "component": "accountability-tools", "description": "Capacity accountability" } ], "conditionalComponents": [ { "component": "smart-contracts", "condition": "If automated capacity assessment" } ], "crossCategoryDependencies": [ "UC-B-032 for partner staff verification" ], "p2TriggerConditions": { "description": "Activated when P2 shows local partner focus + capacity development + verification needs", "rangeSignals": [ "localPartners >= 3+", "capacityFocus >= true", "verificationNeeded >= true" ] }, "contextFieldsTemplate": [ { "field": "partners", "source": "P0 partnerships", "description": "Number of local partners" }, { "field": "capacityAreas", "source": "P2 capacity needs", "description": "Areas assessed" }, { "field": "assessmentFrequency", "source": "P2 monitoring", "description": "Assessment frequency" }, { "field": "supportNeeds", "source": "P2 capacity building", "description": "Capacity building areas" } ], "implementationComplexity": "medium", "examples": { "note": "Partner capacity assessment and development", "references": [ { "name": "NGO Capacity Development Assessment Framework (UNDP)", "url": "https://www.undp.org/content/dam/undp/documents/about/publications/Institutional_Capacity.pdf", "solved": "Standardised multi-domain capacity assessment with baseline and progress tracking" }, { "name": "Organizational Capacity Assessment Tool (OCAT)", "url": "https://www.civicusalliance.org/engage/ocat/", "solved": "Structured assessment of organisational management and governance capacity" }, { "name": "Blockchain Certification and Credentials", "url": "https://www.blockcerts.org/", "solved": "Immutable verifiable credentials for capacity certifications" } ] }, "solutionQuestions": [ { "id": "capacity-domains", "type": "select", "options": [ { "label": "Technical capacity (programme design, M&E, sector expertise)", "value": "technical-capacity" }, { "label": "Organizational capacity (governance, HR, finance, systems)", "value": "organizational-capacity" }, { "label": "Financial management capacity (budgeting, accounting, controls)", "value": "financial-capacity" }, { "label": "Compliance capacity (legal, regulatory, safeguarding)", "value": "compliance-capacity" }, { "label": "Holistic assessment across all domains", "value": "holistic-assessment" } ], "propertyMapping": { "technical-capacity": { "technologies": [ "Technical skills registry", "Expertise verification" ], "technologyProperties": { "assessmentFocus": "Program design and implementation", "verificationMethod": "Portfolio review or test", "updateFrequency": "Annual" } }, "organizational-capacity": { "technologies": [ "Organizational structure registry", "Systems audit" ], "technologyProperties": { "assessmentFocus": "Policies, procedures, staffing", "verificationMethod": "Document review and interviews", "updateFrequency": "Biennial" } }, "financial-capacity": { "technologies": [ "Financial management systems audit", "Controls testing" ], "technologyProperties": { "assessmentFocus": "Accounting controls and procedures", "verificationMethod": "External audit or assessment", "updateFrequency": "Annual" } }, "compliance-capacity": { "technologies": [ "Compliance status registry", "Certification ledger" ], "technologyProperties": { "assessmentFocus": "Legal compliance and safeguarding", "verificationMethod": "Regulatory check and self-assessment", "updateFrequency": "Annual" } }, "holistic-assessment": { "technologies": [ "Comprehensive capacity assessment", "Multi-domain scoring" ], "technologyProperties": { "assessmentScope": "All domains weighted", "verificationMethod": "External assessment", "updateFrequency": "Annual" } } }, "prefillFrom": null, "briefSection": "Partner verification", "text": "What capacity domains will you assess for partners?", "ngoText": "What capacity domains will you assess for partners?" }, { "id": "assessment-method", "type": "select", "options": [ { "label": "Self-assessment questionnaire with spot checks", "value": "self-assessment" }, { "label": "External assessment by qualified assessor", "value": "external-assessment" }, { "label": "Peer review by similar organizations", "value": "peer-review" }, { "label": "Continuous monitoring with real-time feedback", "value": "continuous-monitoring" } ], "propertyMapping": { "self-assessment": { "technologies": [ "Self-assessment form", "Spot-check verification" ], "technologyProperties": { "costBenefit": "Low cost", "selfAwareness": "Organization learns about own capacity", "reliability": "Moderate (self-reporting bias)" } }, "external-assessment": { "technologies": [ "Assessor registry", "Assessment ledger" ], "technologyProperties": { "assessorQualification": "Certified or experienced", "objectivity": "High", "cost": "Higher expense" } }, "peer-review": { "technologies": [ "Peer reviewer registry", "Cross-organization assessment" ], "technologyProperties": { "peer": "Similar sized or sectoral organizations", "learning": "Peer exchange opportunity", "costShare": "Can be reciprocal" } }, "continuous-monitoring": { "technologies": [ "Real-time monitoring dashboard", "Feedback system" ], "technologyProperties": { "frequency": "Ongoing assessment", "responsiveness": "Rapid improvement feedback", "automation": "Reduced manual assessment" } } }, "prefillFrom": null, "briefSection": "Partner verification", "text": "How will partner capacity be assessed?", "ngoText": "How will partner capacity be assessed?" }, { "id": "capacity-development-tracking", "type": "select", "options": [ { "label": "Baseline and annual reassessment with comparison", "value": "baseline-reassessment" }, { "label": "Progress against agreed capacity development plan", "value": "development-plan" }, { "label": "Competency milestones with achievement verification", "value": "competency-milestones" }, { "label": "Capability maturity model progression (Level 1-5)", "value": "maturity-model" } ], "propertyMapping": { "baseline-reassessment": { "technologies": [ "Baseline assessment record", "Reassessment ledger" ], "technologyProperties": { "comparisonMethod": "Score change over time", "timeInterval": "Annual", "visibility": "Transparent results" } }, "development-plan": { "technologies": [ "Capacity development plan registry", "Progress tracking" ], "technologyProperties": { "planFormat": "SMART goals and actions", "accountability": "Partner owns implementation", "reviewCycle": "Quarterly review meetings" } }, "competency-milestones": { "technologies": [ "Milestone registry", "Achievement verification" ], "technologyProperties": { "verification": "Evidence-based confirmation", "granularity": "Specific competency level", "motivation": "Clear target achievement" } }, "maturity-model": { "technologies": [ "Capability maturity model scale", "Level assessment" ], "technologyProperties": { "levels": "Level 1 (initial) through Level 5 (optimized)", "assessment": "Defined criteria per level", "progressTracking": "Path to higher maturity" } } }, "prefillFrom": null, "briefSection": "Partner verification", "text": "How will partner capacity development progress be tracked?", "ngoText": "How will partner capacity development progress be tracked?" }, { "id": "partner-cap-participant-count", "type": "select", "options": [ { "label": "2\u20135 parties", "value": "small" }, { "label": "6\u201315 parties", "value": "medium" }, { "label": "16\u201350 parties", "value": "large" }, { "label": "Over 50 parties", "value": "enterprise" } ], "propertyMapping": { "small": { "technologies": [ "Simple shared ledger" ], "technologyProperties": { "consensusComplexity": "Low", "governanceModel": "Direct" } }, "medium": { "technologies": [ "Permissioned network", "Role-based access" ], "technologyProperties": { "consensusComplexity": "Medium", "governanceModel": "Committee-based" } }, "large": { "technologies": [ "Scalable permissioned network", "Delegated consensus" ], "technologyProperties": { "consensusComplexity": "High", "governanceModel": "Delegated" } }, "enterprise": { "technologies": [ "Enterprise consortium platform", "Federated consensus" ], "technologyProperties": { "consensusComplexity": "Very high", "governanceModel": "Federated" } } }, "prefillFrom": null, "briefSection": "Governance mechanism", "text": "How many organisations or stakeholders participate in capacity verification?", "ngoText": "How many organisations or stakeholders participate in capacity verification?" }, { "id": "partner-cap-decision-freq", "type": "select", "options": [ { "label": "Daily or more", "value": "daily" }, { "label": "Weekly", "value": "weekly" }, { "label": "Monthly", "value": "monthly" }, { "label": "Quarterly or less", "value": "quarterly" } ], "propertyMapping": { "daily": { "technologies": [ "Automated record creation", "Real-time sync" ], "technologyProperties": { "throughput": "High", "automation": "Required" } }, "weekly": { "technologies": [ "Scheduled sync" ], "technologyProperties": { "throughput": "Medium", "automation": "Recommended" } }, "monthly": { "technologies": [ "Batch processing acceptable" ], "technologyProperties": { "throughput": "Low", "automation": "Optional" } }, "quarterly": { "technologies": [], "technologyProperties": { "throughput": "Minimal", "automation": "Not required" } } }, "prefillFrom": null, "briefSection": "Coordination platform", "text": "How frequently are capacity assessments decisions or records created?", "ngoText": "How frequently are capacity assessments decisions or records created?" }, { "id": "credential-issuance-approach", "type": "select", "options": [ { "label": "Centralised issuer (single trusted authority issues credentials)", "value": "centralised" }, { "label": "Delegated issuance (authority delegates to field offices/partners)", "value": "delegated" }, { "label": "Peer attestation (multiple organisations co-attest)", "value": "peer-attestation" }, { "label": "Not sure, need guidance", "value": "guidance-needed" } ], "propertyMapping": { "centralised": { "technologies": [ "Centralised credential issuance platform", "Issuer key management", "Credential status registry" ], "technologyProperties": { "issuerModel": "Single trusted authority", "scalability": "Bottleneck at central issuer", "trustLevel": "High \u2014 single point of trust" } }, "delegated": { "technologies": [ "Delegated credential issuance platform", "Delegation chain manager", "Credential status registry" ], "technologyProperties": { "issuerModel": "Delegated to authorised sub-issuers", "scalability": "High \u2014 distributed issuance", "trustLevel": "High \u2014 delegation chain verifiable" } }, "peer-attestation": { "technologies": [ "Peer credential issuance platform", "Multi-party attestation service", "Credential status registry" ], "technologyProperties": { "issuerModel": "Co-attestation by multiple parties", "scalability": "Moderate \u2014 requires multiple parties", "trustLevel": "High \u2014 multi-party consensus" } }, "guidance-needed": { "technologies": [ "Credential issuance framework", "Credential status registry" ], "technologyProperties": { "issuerModel": "To be determined", "scalability": "To be determined", "trustLevel": "To be determined" } } }, "prefillFrom": null, "briefSection": "Credential issuance", "text": "How are training credentials currently issued?", "ngoText": "How are training credentials currently issued?" }, { "id": "accountability-approach", "type": "select", "options": [ { "label": "Public dashboard with real-time transparency metrics", "value": "public-dashboard" }, { "label": "Stakeholder-restricted reporting portal", "value": "stakeholder-portal" }, { "label": "Community-facing feedback and verification system", "value": "community-facing" }, { "label": "Automated compliance scoring and alerts", "value": "automated-scoring" } ], "propertyMapping": { "public-dashboard": { "technologies": [ "Public accountability dashboard", "Transparency metrics engine", "Accountability reporting tools" ], "technologyProperties": { "visibility": "Public / open access", "updateFrequency": "Real-time or daily", "feedbackLoop": "Public comment / rating system" } }, "stakeholder-portal": { "technologies": [ "Stakeholder accountability portal", "Role-based reporting engine", "Accountability reporting tools" ], "technologyProperties": { "visibility": "Registered stakeholders only", "updateFrequency": "On-demand with scheduled reports", "feedbackLoop": "Stakeholder feedback channel" } }, "community-facing": { "technologies": [ "Community accountability platform", "Beneficiary feedback module", "Accountability reporting tools" ], "technologyProperties": { "visibility": "Community members and beneficiaries", "updateFrequency": "Event-driven", "feedbackLoop": "SMS/app-based feedback collection" } }, "automated-scoring": { "technologies": [ "Automated accountability scoring engine", "Compliance alert service", "Accountability reporting tools" ], "technologyProperties": { "visibility": "Internal with escalation alerts", "updateFrequency": "Continuous monitoring", "feedbackLoop": "Automated alerts on non-compliance" } } }, "prefillFrom": null, "briefSection": "Accountability", "text": "What accountability and transparency mechanisms are needed?", "ngoText": "What accountability and transparency mechanisms are needed?", "hidden": true } ], "complexityFactors": { "relationships": 2, "operationalChange": 2, "dataCompliance": 2 }, "suggestedCriteria": [ { "id": "SC-CAP-CRED", "name": "Verifiable Credentials & Attestations", "description": "Can the system issue and verify cryptographic credentials that attest to a partner's demonstrated capacities, creating a portable, tamper-proof capacity record?", "weight": 0.3, "ratingGuide": { "5": "W3C Verifiable Credentials or equivalent standard. Partner capacities attested by multiple independent assessors. Credentials portable across organisations and verifiable without contacting the issuer.", "4": "Cryptographic credentials issued by authorised assessors. Verification possible through the platform. Credentials transferable between programmes.", "3": "Digital capacity records with integrity checks. Verification requires platform access. Limited portability.", "2": "Capacity assessments recorded in database. Verification requires contacting the assessing organisation.", "1": "Paper-based or informal capacity records. No digital verification mechanism." } }, { "id": "SC-CAP-EVIDENCE", "name": "Evidence-Based Assessment", "description": "Does the system support capacity verification through objective evidence (financial audits, programme reports, beneficiary outcomes) rather than self-declaration alone?", "weight": 0.25, "ratingGuide": { "5": "Multi-source evidence integration: financial audits, programme data, beneficiary feedback, third-party assessments. Automated cross-referencing of claims against evidence.", "4": "Structured evidence collection for each capacity domain. Multiple evidence types accepted. Some automated consistency checking.", "3": "Evidence submission supported but verification is manual. Standard evidence requirements defined.", "2": "Self-declaration with option to attach supporting documents. No systematic verification.", "1": "Capacity claims accepted at face value with no evidence requirement." } }, { "id": "SC-CAP-PROGRESS", "name": "Capacity Development Tracking", "description": "Can the system track capacity changes over time (showing improvement, stagnation, or regression) to support targeted capacity-strengthening investments?", "weight": 0.2, "ratingGuide": { "5": "Longitudinal capacity tracking with trend visualisation. Baseline, milestone, and current assessments compared. Capacity development plans linked to tracked progress. Predictive analytics for capacity gaps.", "4": "Time-series capacity data with comparison across assessment periods. Development plans tracked against milestones.", "3": "Multiple assessment snapshots stored. Manual comparison possible. Development plans documented but not systematically tracked.", "2": "Point-in-time assessments only. Historical data available but not structured for comparison.", "1": "Single assessment with no tracking of changes over time." } }, { "id": "SC-CAP-FAIR", "name": "Assessment Fairness & Contextual Sensitivity", "description": "Does the system account for the different operating contexts, sizes, and histories of local partners, avoiding standards that systematically disadvantage smaller or newer organisations?", "weight": 0.15, "ratingGuide": { "5": "Context-adjusted assessment frameworks. Partner benchmarked against peers in similar contexts. Capacity domains weighted by programme requirements. Growth trajectory valued alongside absolute capacity.", "4": "Assessment criteria adaptable by partner type and context. Some peer benchmarking. Contextual notes captured alongside scores.", "3": "Standard framework with optional contextual modifiers. Assessor discretion for context adjustment.", "2": "Uniform assessment criteria regardless of partner context. Informal allowance for size/context.", "1": "One-size-fits-all assessment that systematically disadvantages smaller or newer organisations." } }, { "id": "SC-CAP-INTEROP", "name": "Cross-Organisation Credential Recognition", "description": "Can capacity credentials issued by one organisation be recognised and accepted by others, reducing redundant assessments and enabling partners to build cumulative track records?", "weight": 0.1, "ratingGuide": { "5": "Standardised credential format recognised across major humanitarian actors. Mutual recognition agreements supported. Partner controls which credentials to share. Credential registry searchable by other organisations.", "4": "Credentials shareable and verifiable by other organisations on the platform. Some mutual recognition. Partner consent required for sharing.", "3": "Credentials exportable in standard format. Recognition depends on receiving organisation's policy. Manual verification process.", "2": "Assessment reports shareable as documents. No structured credential recognition.", "1": "Assessments entirely siloed. No mechanism for cross-organisation recognition." } } ], "procurement": { "marketMaturity": "emerging", "primaryMode": "rfq", "alternativeModes": [ "off-the-shelf" ], "reasoning": "Local partner capacity verification overlaps with due-diligence platforms.", "exampleProductCategories": [ "partner-due-diligence-platform", "capacity-assessment-saas" ], "partnerChannels": [], "lastReviewed": "2026-05-01" } }, { "id": "UC-E-077", "name": "Consortium fund allocation tracking", "category": "E", "subcategory": "Grant Management", "description": "Record how consortium funds were allocated and passed to implementing partners, so members can compare actual use with the agreed plan.", "bCriteria": [ "B1", "B3", "B5" ], "requiredComponents": [ { "component": "record-keeping-platform", "description": "Consortium allocation records" }, { "component": "accounting-integration", "description": "Fund tracking" }, { "component": "decision-audit-trail", "description": "Allocation decision audit" }, { "component": "reporting-module", "description": "Consortium reporting" } ], "conditionalComponents": [ { "component": "smart-contracts", "condition": "If automated fund release" } ], "crossCategoryDependencies": [ "UC-A-007 for fund reconciliation" ], "p2TriggerConditions": { "description": "Activated when P2 shows consortium leadership + complex fund flows + accountability needs", "rangeSignals": [ "consortiumRole >= lead", "fundComplexity >= high", "reportingBurden >= significant" ] }, "contextFieldsTemplate": [ { "field": "members", "source": "P0 partnerships", "description": "Consortium member organisations" }, { "field": "funding", "source": "P0 budget", "description": "Total consortium funding" }, { "field": "allocation", "source": "P2 fund distribution", "description": "Allocation methodology" }, { "field": "reporting", "source": "P0 donor agreements", "description": "Reporting requirements" } ], "implementationComplexity": "medium-high", "examples": { "note": "Consortium fund management", "references": [ { "name": "Global Fund Consortium Management Framework", "url": "https://www.theglobalfund.org/en/", "solved": "Multi-partner consortium fund management with tracked allocation decisions and transparent reporting" }, { "name": "START Fund (Rapid Response to Crises)", "url": "https://startnetwork.org/", "solved": "Consortium pooled funding model with fast allocation decisions and member oversight" }, { "name": "Ethereum Decentralized Autonomous Organizations (DAOs)", "url": "https://ethereum.org/en/dao/", "solved": "Blockchain-based multi-member governance for fund allocation and spending decisions" } ] }, "solutionQuestions": [ { "id": "consortium-model", "type": "select", "options": [ { "label": "Hub-and-spoke (lead agency distributes to partners)", "value": "hub-and-spoke" }, { "label": "Equal partnership (all members contribute equally)", "value": "equal-partnership" }, { "label": "Tiered membership (different contribution levels)", "value": "tiered-membership" }, { "label": "Pooled funding (joint fund managed collaboratively)", "value": "pooled-funding" } ], "propertyMapping": { "hub-and-spoke": { "technologies": [ "Lead agency allocation contract", "Distribution ledger" ], "technologyProperties": { "decisionAuthority": "Concentrated at hub", "allocationProcess": "Hub decides distribution", "partnerRole": "Implementation focused" } }, "equal-partnership": { "technologies": [ "Equal share registry", "Consensus governance" ], "technologyProperties": { "fundingShare": "Equal allocation", "decisionMaking": "Consensus or voting", "contribution": "All members equal value" } }, "tiered-membership": { "technologies": [ "Membership tier registry", "Weighted fund distribution" ], "technologyProperties": { "tiers": "Gold, silver, bronze etc.", "fundingShare": "Proportional to tier", "influence": "Voting power linked to tier" } }, "pooled-funding": { "technologies": [ "Joint fund smart contract", "Collaborative governance" ], "technologyProperties": { "fundControl": "Jointly owned and managed", "distributionDecision": "Committee or consensus", "transparencyLevel": "Full visibility" } } }, "prefillFrom": null, "briefSection": "Governance mechanism", "text": "What consortium operational model will you use?", "ngoText": "What consortium operational model will you use?" }, { "id": "fund-flow-tracking", "type": "select", "options": [ { "label": "High-level: monthly consortium-to-partner disbursements only", "value": "high-level" }, { "label": "Mid-level: activity-level spending by each partner", "value": "mid-level" }, { "label": "Detailed: transaction-level tracking with receipts", "value": "detailed" }, { "label": "Real-time: continuous digital recording of all transactions", "value": "realtime" } ], "propertyMapping": { "high-level": { "technologies": [ "Monthly disbursement ledger", "Bank reconciliation" ], "technologyProperties": { "granularity": "Aggregate per partner", "frequency": "Monthly reporting", "auditability": "Summary-level audit" } }, "mid-level": { "technologies": [ "Activity registry", "Quarterly activity reporting" ], "technologyProperties": { "granularity": "Activity level", "frequency": "Quarterly reporting", "detailLevel": "Activity-level costs" } }, "detailed": { "technologies": [ "Transaction ledger", "Receipt documentation blockchain" ], "technologyProperties": { "granularity": "Transaction level", "documentation": "Invoices and receipts", "auditability": "Full transaction audit" } }, "realtime": { "technologies": [ "On-chain transaction recording", "Streaming ledger" ], "technologyProperties": { "timing": "Immediate recording", "visibility": "Real-time transparency", "updateFrequency": "Per transaction" } } }, "prefillFrom": null, "briefSection": "Reporting and audit", "text": "At what level of detail will fund flows be tracked?", "ngoText": "At what level of detail will fund flows be tracked?" }, { "id": "consortium-decision-making", "type": "select", "options": [ { "label": "Lead organization decides with consultation", "value": "lead-decides" }, { "label": "Steering committee consensus with documented decision", "value": "committee-consensus" }, { "label": "Member voting with documented results", "value": "member-voting" }, { "label": "automated rules formula with no discretionary override", "value": "formula-based" } ], "propertyMapping": { "lead-decides": { "technologies": [ "Decision notice ledger", "Consultation log" ], "technologyProperties": { "authority": "Lead organization signature", "consultation": "Input requested but not binding", "transparency": "Rationale published" } }, "committee-consensus": { "technologies": [ "Committee decision registry", "Consensus agreement" ], "technologyProperties": { "committee": "5-7 member steering committee", "decision": "Unanimous or supermajority", "documentation": "Minutes and decision log" } }, "member-voting": { "technologies": [ "Voting registry", "Vote recording contract" ], "technologyProperties": { "votingMethod": "Democratic one-member-one-vote", "recordedVotes": "Per member visible", "threshold": "Majority or supermajority" } }, "formula-based": { "technologies": [ "Allocation formula smart contract", "Automatic distribution" ], "technologyProperties": { "discretion": "None", "formulation": "Predefined algorithm", "transparency": "Formula code auditable" } } }, "prefillFrom": null, "briefSection": "Governance mechanism", "text": "How are major consortium allocation decisions currently made?", "ngoText": "How are major consortium allocation decisions currently made?" }, { "id": "consortium-reporting", "type": "select", "options": [ { "label": "Quarterly reports to lead donor only", "value": "donor-reports" }, { "label": "Monthly dashboard accessible to all consortium members", "value": "member-dashboard" }, { "label": "Public annual report with anonymized activity data", "value": "public-report" }, { "label": "Real-time public register of all fund flows and decisions", "value": "public-ledger" } ], "propertyMapping": { "donor-reports": { "technologies": [ "Donor reporting template", "Confidential distribution" ], "technologyProperties": { "frequency": "Quarterly", "audience": "Donor and consortium leadership", "transparency": "Internal only" } }, "member-dashboard": { "technologies": [ "Member-accessible dashboard", "Real-time data refresh" ], "technologyProperties": { "frequency": "Monthly snapshots", "access": "Consortium members authenticated", "granularity": "Activity-level visibility" } }, "public-report": { "technologies": [ "Annual report publication", "Anonymized data export" ], "technologyProperties": { "frequency": "Annual", "audience": "Public", "granularity": "Aggregated activity data" } }, "public-ledger": { "technologies": [ "Public blockchain ledger", "Immutable transaction record" ], "technologyProperties": { "frequency": "Real-time updates", "audience": "Completely open", "granularity": "Transaction level (anonymized)" } } }, "prefillFrom": null, "briefSection": "Reporting and audit", "text": "Does your donor, government oversight body, or consortium governance require that all allocation decisions and fund flows be transparently documented and auditable?", "ngoText": "Does your donor, government oversight body, or consortium governance require that all allocation decisions and fund flows be transparently documented and auditable?" }, { "id": "consortium-participant-count", "type": "select", "options": [ { "label": "2\u20135 parties", "value": "small" }, { "label": "6\u201315 parties", "value": "medium" }, { "label": "16\u201350 parties", "value": "large" }, { "label": "Over 50 parties", "value": "enterprise" } ], "propertyMapping": { "small": { "technologies": [ "Simple shared ledger" ], "technologyProperties": { "consensusComplexity": "Low", "governanceModel": "Direct" } }, "medium": { "technologies": [ "Permissioned network", "Role-based access" ], "technologyProperties": { "consensusComplexity": "Medium", "governanceModel": "Committee-based" } }, "large": { "technologies": [ "Scalable permissioned network", "Delegated consensus" ], "technologyProperties": { "consensusComplexity": "High", "governanceModel": "Delegated" } }, "enterprise": { "technologies": [ "Enterprise consortium platform", "Federated consensus" ], "technologyProperties": { "consensusComplexity": "Very high", "governanceModel": "Federated" } } }, "prefillFrom": null, "briefSection": "Governance mechanism", "text": "How many organisations or stakeholders participate in consortium fund allocation?", "ngoText": "How many organisations or stakeholders participate in consortium fund allocation?" }, { "id": "accounting-integration", "type": "select", "options": [ { "label": "Direct integration with your existing accounting software", "value": "direct-erp" }, { "label": "Export-based: generate reports compatible with our accounting system", "value": "export-based" }, { "label": "Standalone ledger with manual reconciliation", "value": "standalone" }, { "label": "Not sure, need guidance on accounting integration", "value": "guidance-needed" } ], "propertyMapping": { "direct-erp": { "technologies": [ "Accounting system connection", "Automatic record updates", "Account structure alignment" ], "technologyProperties": { "integrationMethod": "Real-time connection", "reconciliation": "Automated", "reportFormat": "Compatible with your accounting system" } }, "export-based": { "technologies": [ "Accounting export module", "Report generation engine", "CSV/spreadsheet export service" ], "technologyProperties": { "integrationMethod": "Scheduled export (CSV/spreadsheet)", "reconciliation": "Semi-automated", "reportFormat": "Standard CSV/spreadsheet" } }, "standalone": { "technologies": [ "Standalone accounting ledger", "Manual reconciliation tools" ], "technologyProperties": { "integrationMethod": "Manual import/export", "reconciliation": "Manual", "reportFormat": "PDF/spreadsheet reports" } }, "guidance-needed": { "technologies": [ "Accounting integration framework" ], "technologyProperties": { "integrationMethod": "To be determined", "reconciliation": "To be determined", "reportFormat": "To be determined" } } }, "prefillFrom": null, "briefSection": "Financial integration", "text": "How should this solution integrate with your existing accounting or financial systems?", "ngoText": "How should this solution integrate with your existing accounting or financial systems?" } ], "complexityFactors": { "relationships": 3, "operationalChange": 3, "dataCompliance": 2 }, "suggestedCriteria": [ { "id": "SC-CFUND-TRACE", "name": "End-to-End Fund Traceability", "description": "Can every unit of consortium funding be traced from the pooled fund through sub-allocation to final expenditure, with a complete, immutable chain of custody?", "weight": 0.3, "ratingGuide": { "5": "Full fund traceability on distributed ledger: pooling, allocation decisions, disbursements, sub-grants, and expenditures all linked. Real-time balance visibility at every level. Immutable chain of custody.", "4": "Comprehensive tracking from pool to partner expenditure. Most transactions on-chain. Near-real-time visibility. Minor gaps at lowest expenditure levels.", "3": "Allocation and disbursement tracked. Partner-level expenditure reported but not integrated into the same ledger.", "2": "Fund pool and initial allocations tracked. Downstream tracking requires manual consolidation from partner reports.", "1": "No integrated fund traceability. Each consortium member tracks their allocation independently." } }, { "id": "SC-CFUND-DECIDE", "name": "Allocation Decision Transparency", "description": "Are consortium funding decisions, who gets how much and why, recorded with full rationale, visible to all members, and protected from retroactive alteration?", "weight": 0.25, "ratingGuide": { "5": "Every allocation decision recorded with criteria scores, committee votes, rationale, and dissenting views. Visible to all consortium members in real time. Immutable record.", "4": "Allocation decisions logged with criteria and approvals. Visible to members with minor delay. Tamper-evident storage.", "3": "Decision outcomes recorded with summary rationale. Available to members on request. Some metadata missing.", "2": "Allocation outcomes communicated but detailed rationale not systematically recorded.", "1": "Allocation decisions opaque. Members informed of their allocation without process visibility." } }, { "id": "SC-CFUND-MULTI", "name": "Multi-Donor & Multi-Currency Support", "description": "Can the system handle contributions from multiple donors with different currencies, reporting requirements, and earmarking conditions, maintaining separation where required while enabling consolidated oversight?", "weight": 0.2, "ratingGuide": { "5": "Multi-donor, multi-currency support with earmarking enforcement. Automated exchange rate handling. Concurrent compliance with different donor requirements. Consolidated and donor-specific reporting.", "4": "Multiple donors and currencies supported. Earmarking tracked. Reporting configurable per donor. Some manual currency reconciliation.", "3": "Multiple donors accommodated but single operating currency. Basic earmarking. Standard reporting adaptable per donor.", "2": "Single donor or pooled fund structure. Limited earmarking capability. One-size-fits-all reporting.", "1": "Single donor, single currency only. No earmarking or donor-specific reporting." } }, { "id": "SC-CFUND-GOV", "name": "Consortium Governance & Voting Integration", "description": "Does the system support the consortium's governance structure, including voting mechanisms for allocation decisions, quorum tracking, and role-based authorisations?", "weight": 0.15, "ratingGuide": { "5": "Configurable governance rules: voting thresholds, quorum requirements, role-based permissions, delegation. Governance actions recorded on-chain. Smart contract enforcement of governance rules.", "4": "Voting and approval workflows built in. Quorum tracked. Role-based access. Governance actions logged with audit trail.", "3": "Basic approval workflows. Role-based access. Governance decisions recorded but enforcement is policy-based rather than system-enforced.", "2": "Manual governance processes with system used for record-keeping only. Limited role-based access.", "1": "No governance support. System is purely financial tracking with no decision-making infrastructure." } }, { "id": "SC-CFUND-AUDIT", "name": "Audit Readiness & External Verification", "description": "Can the system produce audit-ready documentation that satisfies both consortium-level and individual donor audit requirements?", "weight": 0.1, "ratingGuide": { "5": "Automated audit report generation. Supports concurrent audits from multiple donors. Full transaction history exportable. Cryptographic proof of record integrity. Tested by major audit firms.", "4": "Comprehensive audit trail with export capability. Supports standard audit frameworks. Report customisation per donor.", "3": "Audit trail available with standard export. Some manual preparation needed for specific donor requirements.", "2": "Transaction records available but audit report generation requires significant manual effort.", "1": "No audit-ready output. Audit preparation requires rebuilding records from multiple sources." } } ], "procurement": { "marketMaturity": "emerging", "primaryMode": "integrator-led", "alternativeModes": [ "rfq" ], "reasoning": "Consortium fund allocation needs integration across partner finance systems.", "exampleProductCategories": [ "consortium-finance-platform", "grants-allocation-saas" ], "partnerChannels": [], "lastReviewed": "2026-05-01" } }, { "id": "UC-E-078", "name": "Inter-agency coordination records", "category": "E", "subcategory": "Multi-Agency Coordination", "description": "Give agencies one shared record of who is doing what in an operation, so aid is not duplicated and no agency has to hand over its data.", "bCriteria": [ "B1", "B2", "B4", "B5" ], "requiredComponents": [ { "component": "coordination-protocol", "description": "Shared blockchain layer for multi-agency data coordination" }, { "component": "data-sovereignty-layer", "description": "Ensures each agency retains control of their own data" }, { "component": "assistance-registry", "description": "Shared record of which beneficiaries received which assistance" }, { "component": "interoperability-gateway", "description": "Connects to agency-specific systems and existing coordination mechanisms" } ], "conditionalComponents": [ { "component": "consent-engine", "condition": "If beneficiary consent is tracked per-agency", "linksTo": "" }, { "component": "identity-verification", "condition": "If beneficiary deduplication requires identity matching" } ], "crossCategoryDependencies": [ "UC-B-024 if beneficiary identity verification needed", "UC-C-043 for beneficiary deduplication", "UC-C-046 for inter-agency data sharing" ], "p2TriggerConditions": { "description": "Activated when P2 identifies inter-agency coordination failures, duplicate aid delivery, data sharing barriers between organisations, or crisis response requiring multi-agency operations", "rangeSignals": [ "coordinatingAgencies >= 3", "duplicateDeliveryRisk >= moderate", "dataSharingBarriers >= significant", "crisisResponseCoordination required" ] }, "contextFieldsTemplate": [ { "field": "agencyCount", "source": "P2 answers", "description": "Number of organisations that need to coordinate" }, { "field": "assistanceTypes", "source": "P2 answers", "description": "Types of assistance being tracked (food, cash, shelter, health)" }, { "field": "geographicScope", "source": "P0 + P2", "description": "Geographic area of coordination" }, { "field": "existingCoordination", "source": "P2 answers", "description": "Current coordination mechanisms (OCHA clusters, bilateral agreements)" } ], "implementationComplexity": "high", "examples": { "note": "WFP Building Blocks coordinated 65+ agencies in Ukraine, preventing ~$270M in duplicate aid", "references": [ { "name": "WFP Building Blocks (Ukraine)", "url": "https://www.wfp.org/building-blocks", "solved": "Coordinated 65+ aid organisations in Ukraine, preventing ~$270M in overlapping aid delivery while maintaining data sovereignty" }, { "name": "WFP Building Blocks (Jordan)", "url": "https://www.wfp.org/building-blocks", "solved": "Blockchain-based beneficiary assistance coordination for Syrian refugees in Azraq and Zaatari camps" }, { "name": "OCHA Centre for Humdata", "url": "https://centre.humdata.org/", "solved": "Demonstrated need for privacy-preserving inter-agency data coordination in humanitarian crises" } ] }, "solutionQuestions": [ { "id": "agency-count", "label": "How many organisations need to coordinate through this system?", "type": "select", "briefSection": "coordination-requirements", "options": [ { "label": "2\u20135 agencies", "value": "small" }, { "label": "6\u201320 agencies", "value": "medium" }, { "label": "21\u201350 agencies", "value": "large" }, { "label": "50+ agencies", "value": "very-large" } ], "propertyMapping": { "small": { "technologies": [ "Multi-party coordination ledger" ], "technologyProperties": { "coordinationScale": "2\u20135 agencies", "consensusComplexity": "Low" } }, "medium": { "technologies": [ "Scalable coordination protocol" ], "technologyProperties": { "coordinationScale": "6\u201320 agencies", "consensusComplexity": "Medium" } }, "large": { "technologies": [ "Enterprise coordination platform", "Delegated consensus" ], "technologyProperties": { "coordinationScale": "21\u201350 agencies", "consensusComplexity": "High" } }, "very-large": { "technologies": [ "Crisis-scale coordination infrastructure" ], "technologyProperties": { "coordinationScale": "50+ agencies", "consensusComplexity": "Very high \u2014 requires hierarchical coordination" } } }, "text": "How many organisations need to coordinate through this system?" }, { "id": "assistance-types", "label": "What types of assistance need to be tracked across agencies?", "type": "multiselect", "briefSection": "assistance-tracking", "options": [ { "label": "Cash and voucher assistance (CVA)", "value": "cash" }, { "label": "Food distribution", "value": "food" }, { "label": "Shelter and NFI", "value": "shelter" }, { "label": "Health services", "value": "health" }, { "label": "Education", "value": "education" }, { "label": "Protection services", "value": "protection" } ], "propertyMapping": { "cash": { "technologies": [ "CVA tracking module" ], "technologyProperties": { "assistanceType": "Cash and voucher assistance" } }, "food": { "technologies": [ "In-kind distribution tracker" ], "technologyProperties": { "assistanceType": "Food distribution" } }, "shelter": { "technologies": [ "NFI distribution tracker" ], "technologyProperties": { "assistanceType": "Shelter and non-food items" } }, "health": { "technologies": [ "Health service registry" ], "technologyProperties": { "assistanceType": "Health services" } }, "education": { "technologies": [ "Education service tracker" ], "technologyProperties": { "assistanceType": "Education services" } }, "protection": { "technologies": [ "Protection case tracker" ], "technologyProperties": { "assistanceType": "Protection services" } } }, "text": "What types of assistance need to be tracked across agencies?" }, { "id": "data-sovereignty-model", "label": "What data sovereignty model is required?", "type": "select", "briefSection": "data-sovereignty", "options": [ { "label": "Each agency controls their own data; shared layer shows only deduplication hashes", "value": "hash-only" }, { "label": "Shared layer shows assistance type and date but not beneficiary details", "value": "metadata-shared" }, { "label": "Full data sharing with role-based access controls", "value": "full-sharing" }, { "label": "Configurable per agency (some share more, some less)", "value": "configurable" } ], "propertyMapping": { "hash-only": { "technologies": [ "Privacy-preserving hash registry", "Zero-knowledge deduplication" ], "technologyProperties": { "dataSovereignty": "Maximum \u2014 hash-only shared layer", "privacyLevel": "Highest" } }, "metadata-shared": { "technologies": [ "Metadata coordination layer", "Encrypted beneficiary references" ], "technologyProperties": { "dataSovereignty": "High \u2014 metadata shared, details retained", "privacyLevel": "High" } }, "full-sharing": { "technologies": [ "Shared data platform", "Role-based access control" ], "technologyProperties": { "dataSovereignty": "Standard \u2014 full sharing with RBAC", "privacyLevel": "Standard" } }, "configurable": { "technologies": [ "Configurable data sharing layer", "Per-agency privacy settings" ], "technologyProperties": { "dataSovereignty": "Flexible \u2014 per-agency configuration", "privacyLevel": "Variable" } } }, "text": "What data sovereignty model is required?" }, { "id": "existing-coordination", "label": "What existing coordination mechanisms does this need to integrate with?", "type": "multiselect", "briefSection": "interoperability", "options": [ { "label": "OCHA cluster coordination system", "value": "ocha" }, { "label": "Bilateral data sharing agreements between specific agencies", "value": "bilateral" }, { "label": "Existing beneficiary registration systems", "value": "registration-systems" }, { "label": "No existing coordination mechanisms", "value": "none" } ], "propertyMapping": { "ocha": { "technologies": [ "OCHA integration adapter" ], "technologyProperties": { "existingCoordination": "OCHA cluster system" } }, "bilateral": { "technologies": [ "Bilateral agreement digitiser" ], "technologyProperties": { "existingCoordination": "Bilateral data sharing agreements" } }, "registration-systems": { "technologies": [ "Registration system connector" ], "technologyProperties": { "existingCoordination": "Existing beneficiary registration systems" } }, "none": { "technologies": [], "technologyProperties": { "existingCoordination": "No existing mechanisms \u2014 greenfield" } } }, "text": "What existing coordination mechanisms does this need to integrate with?" }, { "id": "beneficiary-consent-model", "label": "How will beneficiary consent for data sharing across agencies be managed?", "type": "select", "briefSection": "beneficiary-consent", "options": [ { "label": "Opt-in: beneficiaries explicitly consent to cross-agency data sharing", "value": "opt-in" }, { "label": "Opt-out: sharing is default with right to withdraw", "value": "opt-out" }, { "label": "No personal data shared, only anonymised/hashed records on shared layer", "value": "no-pii" }, { "label": "Granular consent per agency and data type", "value": "granular" } ], "propertyMapping": { "opt-in": { "technologies": [ "Consent management engine", "Consent record ledger" ], "technologyProperties": { "consentModel": "Opt-in", "consentComplexity": "Medium" } }, "opt-out": { "technologies": [ "Default-share consent module" ], "technologyProperties": { "consentModel": "Opt-out with withdrawal right", "consentComplexity": "Low" } }, "no-pii": { "technologies": [ "Anonymisation layer" ], "technologyProperties": { "consentModel": "No PII shared", "consentComplexity": "Minimal \u2014 privacy by design" } }, "granular": { "technologies": [ "Granular consent engine", "Per-agency consent dashboard" ], "technologyProperties": { "consentModel": "Granular per-agency", "consentComplexity": "High" } } }, "text": "How will beneficiary consent for data sharing across agencies be managed?" } ], "complexityFactors": { "relationships": 5, "operationalChange": 3, "dataCompliance": 4 }, "suggestedCriteria": [ { "id": "SC-INTER-SOVR", "name": "Data Sovereignty & Agency Autonomy", "description": "Does each agency retain full control over their own data, with the coordination layer operating on derived or encrypted data rather than requiring centralisation?", "weight": 0.3, "ratingGuide": { "5": "Full data sovereignty \u2014 each agency's data remains in their systems. Coordination operates on cryptographic proofs or privacy-preserving computations. Any agency can disconnect without data loss.", "4": "Minimal data replication to coordination layer. Clear data ownership. Agency controls what is shared. Clean disconnection process.", "3": "Some data centralisation for coordination but access controlled. Agency retains primary copy. Withdrawal involves data migration.", "2": "Significant data centralisation. Agency autonomy limited by platform dependencies. Withdrawal complex.", "1": "Full data centralisation required. Agencies cede data control to coordination platform." } }, { "id": "SC-INTER-INTEROP", "name": "System Interoperability & Standards", "description": "Can the coordination layer integrate with the diverse information systems that different agencies actually use, without requiring all agencies to adopt the same platform?", "weight": 0.25, "ratingGuide": { "5": "Standards-based integration (IATI, HXLM, FTS). Pre-built connectors for major humanitarian platforms. API-first architecture. Supports agencies from WFP-scale to small local NGOs.", "4": "API-based integration with standard data exchange formats. Connectors for common platforms. Manual integration path for others.", "3": "Standard import/export formats supported. Integration requires some technical configuration per agency.", "2": "Limited integration. Most agencies must use the coordination platform directly rather than through their own systems.", "1": "No interoperability. All agencies must adopt the same platform for coordination." } }, { "id": "SC-INTER-SCALE", "name": "Scalability & Multi-Level Coordination", "description": "Can the system scale from a few agencies in a single location to dozens of agencies across multiple countries, supporting both local and global coordination structures?", "weight": 0.2, "ratingGuide": { "5": "Hierarchical coordination layers (local \u2192 national \u2192 regional \u2192 global). Supports hundreds of agencies. Performance maintained at scale. Federated architecture avoids bottlenecks.", "4": "Multi-level coordination supported. Dozens of agencies manageable. Performance tested at scale. Some federation capability.", "3": "Supports multiple agencies at single coordination level. Scaling requires additional infrastructure. Performance adequate for medium-scale responses.", "2": "Works well for small groups (5-10 agencies). Performance degrades significantly with more participants.", "1": "Designed for bilateral coordination only. Cannot support multi-agency coordination." } }, { "id": "SC-INTER-BENEFIT", "name": "Beneficiary-Centric Coordination", "description": "Does the coordination layer prioritise beneficiary outcomes, ensuring that coordination data is used to improve service delivery rather than just satisfying bureaucratic requirements?", "weight": 0.15, "ratingGuide": { "5": "Beneficiary outcome tracking integrated into coordination. Service delivery gaps and overlaps visible in real time. Referral pathways across agencies supported and tracked.", "4": "Service delivery coverage visible across agencies. Referral tracking. Some outcome measurement integration.", "3": "Coordination data includes service delivery information. Gap analysis possible through manual review.", "2": "Coordination focused on agency activities and resources. Beneficiary perspective available only through aggregated reports.", "1": "Purely administrative coordination. No beneficiary-outcome orientation." } }, { "id": "SC-INTER-CONSENT", "name": "Beneficiary Consent & Protection", "description": "Does the system ensure that coordination of beneficiary information respects consent requirements and data protection standards, particularly for vulnerable populations?", "weight": 0.1, "ratingGuide": { "5": "Granular consent management per agency and purpose. Privacy-preserving coordination \u2014 beneficiary data not exposed between agencies without consent. GDPR/humanitarian data protection standards built in.", "4": "Consent tracked per coordination use. Data minimisation enforced. Protection standards configurable. Consent withdrawal supported.", "3": "Consent captured at registration. Data sharing governed by inter-agency agreements. Some data minimisation.", "2": "Blanket consent or organisational agreements replace individual consent. Limited data protection controls.", "1": "No beneficiary consent mechanism for inter-agency data coordination." } } ], "procurement": { "marketMaturity": "nascent", "primaryMode": "consortium", "alternativeModes": [ "integrator-led" ], "reasoning": "Inter-agency coordination records are typically bespoke or sector-led.", "exampleProductCategories": [ "interagency-coordination-platform", "cluster-records-saas" ], "partnerChannels": [], "lastReviewed": "2026-05-01" } }, { "id": "UC-E-079", "name": "Digital public goods infrastructure", "category": "E", "subcategory": "Shared Infrastructure", "description": "Build shared systems that several independent organisations can use and rely on, without any one organisation controlling them.", "bCriteria": [ "B1", "B2", "B4" ], "requiredComponents": [ { "component": "shared-registry", "description": "Shared blockchain infrastructure that multiple organisations build upon" }, { "component": "governance-framework", "description": "Multi-stakeholder governance for shared infrastructure decisions" }, { "component": "interoperability-standard", "description": "Open standards enabling cross-organisation integration" }, { "component": "data-protection-layer", "description": "Privacy and data protection across shared infrastructure" } ], "conditionalComponents": [ { "component": "sustainability-model", "condition": "If the infrastructure needs a self-sustaining funding mechanism" }, { "component": "identity-verification", "condition": "If shared identity infrastructure is part of the public good" } ], "crossCategoryDependencies": [ "UC-B-024 if shared identity registry", "UC-C-046 for inter-agency data sharing patterns", "UC-E-068 for multi-stakeholder governance patterns" ], "p2TriggerConditions": { "description": "Activated when P2 identifies sector-wide duplication of effort, need for shared infrastructure, desire to contribute to public goods, or interoperability barriers between agency-specific systems", "rangeSignals": [ "sectorDuplication >= significant", "interoperabilityBarriers >= moderate", "publicGoodAlignment >= strong", "multiStakeholderNeed >= 3 organisations" ] }, "contextFieldsTemplate": [ { "field": "infrastructureType", "source": "P2 answers", "description": "Type of shared infrastructure (identity, credentials, data, registry)" }, { "field": "participatingOrgs", "source": "P2 answers", "description": "Number and type of participating organisations" }, { "field": "dpgAlignment", "source": "P2 answers", "description": "Alignment with Digital Public Goods Alliance standards" }, { "field": "sustainabilityModel", "source": "P2 answers", "description": "How the infrastructure will be sustained long-term" } ], "implementationComplexity": "high", "examples": { "note": "UNDP 40+ government DLT pilots; UNICEF Venture Fund blockchain investments; DPG Alliance", "references": [ { "name": "UNDP Blockchain Academy", "url": "https://www.undp.org/", "solved": "Training 40+ governments on integrating blockchain into digital public infrastructure" }, { "name": "UNICEF Venture Fund", "url": "https://www.unicef.org/innovation/venturefund", "solved": "Investing in open-source blockchain projects contributing to digital public goods" }, { "name": "Digital Public Goods Alliance", "url": "https://digitalpublicgoods.net/", "solved": "Framework for recognising and promoting open-source digital public goods including blockchain-based solutions" } ] }, "solutionQuestions": [ { "id": "infrastructure-type", "label": "What type of shared infrastructure is being built?", "type": "select", "briefSection": "infrastructure-type", "options": [ { "label": "Shared identity registry (multiple agencies verify against)", "value": "identity" }, { "label": "Shared beneficiary status system (coordination layer)", "value": "beneficiary-status" }, { "label": "Open credential framework (portable across organisations)", "value": "credentials" }, { "label": "Shared data infrastructure (common data layer)", "value": "data-layer" }, { "label": "Shared payment infrastructure (common settlement rail)", "value": "payment" } ], "propertyMapping": { "identity": { "technologies": [ "Shared identity registry", "DID resolver service" ], "technologyProperties": { "infrastructureType": "Shared identity", "dpgCategory": "Identity and registration" } }, "beneficiary-status": { "technologies": [ "Beneficiary status registry", "Cross-agency coordination layer" ], "technologyProperties": { "infrastructureType": "Beneficiary coordination", "dpgCategory": "Humanitarian coordination" } }, "credentials": { "technologies": [ "Open credential framework", "Cross-org credential verifier" ], "technologyProperties": { "infrastructureType": "Portable credentials", "dpgCategory": "Education and workforce" } }, "data-layer": { "technologies": [ "Shared data infrastructure", "Federated data mesh" ], "technologyProperties": { "infrastructureType": "Common data layer", "dpgCategory": "Data and analytics" } }, "payment": { "technologies": [ "Shared settlement rail", "Multi-org payment infrastructure" ], "technologyProperties": { "infrastructureType": "Common payment rail", "dpgCategory": "Financial inclusion" } } }, "text": "What type of shared infrastructure is being built?" }, { "id": "governance-model-dpg", "label": "How will the shared infrastructure be governed?", "type": "select", "briefSection": "governance-model", "options": [ { "label": "Equal voice: each partner has the same say (consortium model)", "value": "equal-voice-each-partner-has-the-same-sa" }, { "label": "Independent governing body makes decisions (foundation model)", "value": "independent-governing-body-makes-decisio" }, { "label": "One lead agency with an advisory board of partners", "value": "one-lead-agency-with-an-advisory-board-o" }, { "label": "Not sure, need guidance on governance structure", "value": "not-sure-need-guidance-on-governance-str" } ], "propertyMapping": { "consortium": { "technologies": [ "Consortium governance module", "Multi-sig decision contracts" ], "technologyProperties": { "governanceModel": "Consortium \u2014 equal voice", "decisionMaking": "Consensus or super-majority" } }, "foundation": { "technologies": [ "Foundation governance framework" ], "technologyProperties": { "governanceModel": "Independent foundation", "decisionMaking": "Board-level with stakeholder input" } }, "lead-agency": { "technologies": [ "Lead agency governance module", "Advisory board portal" ], "technologyProperties": { "governanceModel": "Lead agency with advisory", "decisionMaking": "Lead agency with consultation" } }, "dao": { "technologies": [ "DAO governance contracts", "Token-weighted voting" ], "technologyProperties": { "governanceModel": "DAO / on-chain", "decisionMaking": "Token or stake-weighted voting" } } }, "text": "How will the shared infrastructure be governed?", "question": "How should partner organisations share decision-making for this shared infrastructure?" }, { "id": "sustainability-funding", "label": "How will the infrastructure be funded and sustained long-term?", "type": "select", "briefSection": "sustainability", "options": [ { "label": "Donor-funded with transition plan to self-sustaining", "value": "donor-transition" }, { "label": "Usage-based fees from participating organisations", "value": "usage-fees" }, { "label": "Government-funded as national digital infrastructure", "value": "government" }, { "label": "Open-source community maintained", "value": "open-source" } ], "propertyMapping": { "donor-transition": { "technologies": [], "technologyProperties": { "sustainabilityModel": "Donor-funded with transition plan", "fundingRisk": "Medium \u2014 transition execution risk" } }, "usage-fees": { "technologies": [ "Usage metering and billing module" ], "technologyProperties": { "sustainabilityModel": "Usage-based fees", "fundingRisk": "Low if adoption sufficient" } }, "government": { "technologies": [ "Government integration layer" ], "technologyProperties": { "sustainabilityModel": "Government-funded", "fundingRisk": "Low if politically stable" } }, "open-source": { "technologies": [], "technologyProperties": { "sustainabilityModel": "Open-source community", "fundingRisk": "High \u2014 volunteer dependency" } } }, "text": "How will the infrastructure be funded and sustained long-term?" }, { "id": "interop-standards", "label": "Which interoperability standards should the infrastructure align with?", "type": "multiselect", "briefSection": "interoperability", "options": [ { "label": "UN agencies (OCHA, UNHCR, WFP systems)", "value": "un-agencies-ocha-unhcr-wfp-systems-" }, { "label": "Government registries and national databases", "value": "government-registries-and-national-datab" }, { "label": "Other NGO and civil society systems", "value": "other-ngo-and-civil-society-systems" }, { "label": "Health information systems", "value": "health-information-systems" }, { "label": "Multiple types: need broad compatibility", "value": "multiple-types-need-broad-compatibility" }, { "label": "Not sure, need guidance", "value": "not-sure-need-guidance" } ], "propertyMapping": { "w3c-vc": { "technologies": [ "W3C VC/DID implementation" ], "technologyProperties": { "interopStandard": "W3C Verifiable Credentials" } }, "iati": { "technologies": [ "IATI reporting adapter" ], "technologyProperties": { "interopStandard": "IATI" } }, "fhir": { "technologies": [ "FHIR data adapter" ], "technologyProperties": { "interopStandard": "HL7 FHIR" } }, "dpg-standard": { "technologies": [ "DPG Standard compliance module" ], "technologyProperties": { "interopStandard": "Digital Public Goods Standard" } }, "custom": { "technologies": [ "Custom API layer" ], "technologyProperties": { "interopStandard": "Custom APIs" } } }, "text": "Which interoperability standards should the infrastructure align with?", "question": "Which other organisations or systems does this infrastructure need to work with?" }, { "id": "data-protection-model", "label": "What data protection framework applies to the shared infrastructure?", "type": "select", "briefSection": "data-protection", "options": [ { "label": "GDPR or equivalent national data protection law", "value": "gdpr" }, { "label": "Humanitarian data protection principles (OCHA, ICRC)", "value": "humanitarian" }, { "label": "Multiple jurisdictions: need federated compliance", "value": "multi-jurisdiction" }, { "label": "No formal framework yet, need to establish", "value": "none" } ], "propertyMapping": { "gdpr": { "technologies": [ "GDPR compliance module", "Data processing agreement framework" ], "technologyProperties": { "dataProtection": "GDPR or equivalent", "complianceComplexity": "Medium" } }, "humanitarian": { "technologies": [ "Humanitarian data protection module" ], "technologyProperties": { "dataProtection": "Humanitarian principles (OCHA/ICRC)", "complianceComplexity": "Medium" } }, "multi-jurisdiction": { "technologies": [ "Federated compliance engine", "Multi-jurisdiction data routing" ], "technologyProperties": { "dataProtection": "Multi-jurisdiction federated", "complianceComplexity": "High" } }, "none": { "technologies": [], "technologyProperties": { "dataProtection": "Framework to be established", "complianceComplexity": "Requires legal consultation" } } }, "text": "What data protection framework applies to the shared infrastructure?" } ], "complexityFactors": { "relationships": 4, "operationalChange": 3, "dataCompliance": 2 }, "suggestedCriteria": [ { "id": "SC-DPG-OPEN", "name": "Open Standards & Interoperability", "description": "Does the infrastructure use open standards, open-source components, and open data formats, ensuring it can serve as genuine public goods infrastructure rather than creating vendor lock-in?", "weight": 0.3, "ratingGuide": { "5": "Fully open-source with active community. Open data standards (W3C, IETF, OASIS). Open APIs. Listed on Digital Public Goods Alliance registry or equivalent. No proprietary dependencies.", "4": "Core infrastructure open-source. Open APIs and standard data formats. Some proprietary components but replaceable. Active developer community.", "3": "Open APIs with published documentation. Source code partially open. Standard data formats supported but some proprietary elements.", "2": "Proprietary platform with published APIs. Limited open-source components. Vendor migration possible but costly.", "1": "Fully proprietary. No open APIs or standards. Complete vendor lock-in." } }, { "id": "SC-DPG-GOV", "name": "Inclusive Governance Model", "description": "Is the infrastructure governed by a multi-stakeholder model that gives voice to implementing organisations, beneficiary representatives, and the broader community, beyond the technology provider?", "weight": 0.25, "ratingGuide": { "5": "Multi-stakeholder governance body with representation from civil society, government, technical community, and end users. Transparent decision-making. Community veto on critical changes. Independent from any single funder.", "4": "Governance board with diverse representation. Community input mechanisms. Major decisions require stakeholder consultation. Some funder influence but balanced.", "3": "Advisory board with stakeholder representatives. Governance decisions primarily by core team with community input opportunities.", "2": "Technology provider governs with stakeholder consultation on major decisions only. Limited community voice.", "1": "Unilateral governance by technology provider or single funder. No stakeholder input mechanism." } }, { "id": "SC-DPG-SUSTAIN", "name": "Financial Sustainability & Independence", "description": "Does the infrastructure have a credible long-term funding model that does not depend on a single donor or commercial entity, ensuring continuity of public goods infrastructure?", "weight": 0.2, "ratingGuide": { "5": "Diversified funding: multiple donors, earned revenue, endowment or reserve fund. Multi-year commitments. Infrastructure survives any single funder withdrawal. Public funding component.", "4": "Multiple funding sources with at least 2-year runway. Revenue model emerging. Would survive loss of largest funder.", "3": "Two or three funding sources. 1-year runway. Heavy dependence on primary funder but alternatives being developed.", "2": "Single primary funder with short-term commitment. Sustainability plan exists on paper but untested.", "1": "Entirely dependent on single funder with no sustainability plan. Infrastructure at risk of abandonment." } }, { "id": "SC-DPG-PROTECT", "name": "Data Protection & Privacy by Design", "description": "Does the infrastructure embed data protection and privacy at the architectural level, particularly important for public goods infrastructure that may handle data from vulnerable populations across jurisdictions?", "weight": 0.15, "ratingGuide": { "5": "Privacy by design at architecture level. Data minimisation enforced by system design. Supports multiple jurisdictional requirements. Privacy impact assessments embedded in development process.", "4": "Strong data protection with configurable privacy controls. Supports GDPR and humanitarian data protection standards. Regular privacy audits.", "3": "Data protection features included. Standard encryption and access controls. Single privacy framework (e.g., GDPR) supported.", "2": "Basic data protection. Encryption in transit. Access controls but privacy not a design priority.", "1": "Minimal data protection. Privacy considerations not embedded in architecture." } }, { "id": "SC-DPG-ADOPT", "name": "Adoption Support & Capacity Building", "description": "Does the provider support adoption through documentation, training, and capacity building, recognising that public goods infrastructure must be usable by organisations with varying technical capacity?", "weight": 0.1, "ratingGuide": { "5": "Comprehensive documentation in multiple languages. Training programme for implementers. Active support community. Deployment guides for low-resource contexts. Dedicated onboarding support.", "4": "Good documentation with training materials. Support community active. Deployment guides available. Some onboarding assistance.", "3": "Technical documentation adequate. Training available but limited. Community support emerging.", "2": "Minimal documentation. Training only through direct engagement with provider. No self-service deployment.", "1": "No documentation or training support. Implementation requires direct provider involvement." } } ], "procurement": { "marketMaturity": "nascent", "primaryMode": "consortium", "alternativeModes": [ "internal-build" ], "reasoning": "Digital public goods infrastructure is research-stage by definition.", "exampleProductCategories": [ "dpi-platform", "public-goods-infrastructure" ], "partnerChannels": [], "lastReviewed": "2026-05-01" } }, { "id": "UC-F-080", "name": "Transparent fund flow tracking", "category": "F", "subcategory": "Donor Transparency", "description": "Show donors the path their money took, from the first deposit to the final beneficiary, without staff compiling the figures by hand.", "bCriteria": [ "B1", "B3", "B4" ], "requiredComponents": [ "donation-platform", "fund-tracking", "audit-trail", "reporting-automation" ], "conditionalComponents": [ "smart-contracts", "payment-gateway" ], "crossCategoryDependencies": [], "p2TriggerConditions": { "description": "Activated when P2 shows multiple stakeholders sharing funds with low trust between parties and regulatory reporting requirements", "rangeSignals": [ "multiStakeholder >=2", "dataSharing >=3", "trustLevel <=2", "regulatoryRequired = true" ] }, "contextFieldsTemplate": [ "number_of_donors", "annual_donation_volume", "geographic_distribution", "number_of_implementation_locations", "existing_accounting_systems", "donor_transparency_requirements", "regulatory_audit_frequency", "currency_types" ], "implementationComplexity": "medium", "examples": { "note": "Similar to Give Directly's transparency portal but decentralized", "references": [ { "name": "Disberse", "url": "https://disberse.com", "solved": "Tracked humanitarian fund flows through implementing partners using blockchain-based audit trails; piloted with multiple INGOs." }, { "name": "Giveth", "url": "https://giveth.io", "solved": "Open-source platform for transparent on-chain donation tracking from donor through to project execution." }, { "name": "WFP Building Blocks", "url": "https://innovation.wfp.org/project/building-blocks", "solved": "Documented multi-million-dollar fund flow with reduced reconciliation overhead across implementing-partner network." } ] }, "propertyMapping": {}, "solutionQuestions": [ { "id": "fund-flow-granularity", "type": "select", "options": [ { "label": "Transaction-level tracking with donor identifiers", "value": "transaction-level-identified" }, { "label": "Aggregated fund flows (pooled reporting)", "value": "aggregated-pooled" }, { "label": "Real-time transaction visibility with privacy controls", "value": "realtime-privacy-controlled" } ], "propertyMapping": { "transaction-level-identified": { "technologies": [ "audit-trail", "donation-platform" ], "technologyProperties": { "granularity": "per-transaction", "visibilityLevel": "donor-identified", "auditDepth": "full-chain" } }, "aggregated-pooled": { "technologies": [ "fund-tracking", "reporting-automation" ], "technologyProperties": { "granularity": "aggregated", "visibilityLevel": "anonymized", "auditDepth": "summary-level" } }, "realtime-privacy-controlled": { "technologies": [ "audit-trail", "donation-platform", "smart-contracts" ], "technologyProperties": { "granularity": "per-transaction", "visibilityLevel": "privacy-controlled", "updateFrequency": "real-time" } } }, "prefillFrom": null, "briefSection": "Transparency level", "text": "What level of fund flow granularity is required for donor transparency?", "ngoText": "What level of fund flow granularity is required for donor transparency?", "hidden": true }, { "id": "transparency-stakeholders", "type": "select", "options": [ { "label": "Individual donors only (personal dashboard)", "value": "individual-donors" }, { "label": "Regulators and compliance teams", "value": "regulators-compliance" }, { "label": "Public transparency (digital ledger published)", "value": "public-blockchain" }, { "label": "Multi-stakeholder (donors + regulators + public)", "value": "multi-stakeholder-tiered" } ], "propertyMapping": { "individual-donors": { "technologies": [ "donation-platform", "reporting-automation" ], "technologyProperties": { "accessControl": "donor-personal", "dataVisibility": "individual-contributions", "reportingFormat": "dashboard" } }, "regulators-compliance": { "technologies": [ "audit-trail", "smart-contracts" ], "technologyProperties": { "accessControl": "role-based", "dataVisibility": "full-transaction-history", "reportingFormat": "audit-report" } }, "public-blockchain": { "technologies": [ "audit-trail", "fund-tracking" ], "technologyProperties": { "accessControl": "public", "dataVisibility": "anonymized-flow", "immutability": "distributed-ledger" } }, "multi-stakeholder-tiered": { "technologies": [ "audit-trail", "donation-platform", "smart-contracts" ], "technologyProperties": { "accessControl": "tiered-rbac", "dataVisibility": "multi-level", "redactionRules": "selective-disclosure" } } }, "prefillFrom": null, "briefSection": "Donor experience", "text": "Who needs to access the fund flow transparency information?", "ngoText": "Who needs to access the fund flow transparency information?" }, { "id": "reporting-frequency", "type": "select", "options": [ { "label": "Real-time digital settlement (minutes)", "value": "realtime-settlement" }, { "label": "Daily batched reports", "value": "daily-batch" }, { "label": "Weekly consolidated summary", "value": "weekly-consolidated" } ], "propertyMapping": { "realtime-settlement": { "technologies": [ "audit-trail", "smart-contracts" ], "technologyProperties": { "reportingFrequency": "real-time", "settlementSpeed": "minutes", "updateMechanism": "event-driven" } }, "daily-batch": { "technologies": [ "reporting-automation", "fund-tracking" ], "technologyProperties": { "reportingFrequency": "daily", "batchWindow": "24-hour", "automationLevel": "scheduled" } }, "weekly-consolidated": { "technologies": [ "reporting-automation", "donation-platform" ], "technologyProperties": { "reportingFrequency": "weekly", "aggregationPeriod": "7-day", "detailLevel": "summary" } } }, "prefillFrom": null, "briefSection": "Reporting automation", "text": "What reporting frequency is needed for fund flow updates?", "ngoText": "What reporting frequency is needed for fund flow updates?" }, { "id": "multi-currency-support", "type": "select", "options": [ { "label": "Single base currency (convert at intake)", "value": "single-base-currency" }, { "label": "Preserve original currency (dual-track accounting)", "value": "preserve-original-currency" }, { "label": "Stablecoin bridge (normalising across stablecoins)", "value": "stablecoin-bridge" } ], "propertyMapping": { "single-base-currency": { "technologies": [ "donation-platform", "fund-tracking" ], "technologyProperties": { "currencyHandling": "unified-conversion", "conversionPoint": "at-intake", "reportingCurrency": "base-only" } }, "preserve-original-currency": { "technologies": [ "audit-trail", "fund-tracking" ], "technologyProperties": { "currencyHandling": "multi-currency-ledger", "conversionTracking": "rate-locked", "reportingCurrency": "original-plus-base" } }, "stablecoin-bridge": { "technologies": [ "smart-contracts", "donation-platform" ], "technologyProperties": { "currencyHandling": "stablecoin-normalized", "bridgeAsset": "stablecoin", "reportingCurrency": "stablecoin-equivalent" } } }, "prefillFrom": null, "briefSection": "Fund tracking", "text": "What currencies do you currently need to support in your operations?", "ngoText": "What currencies do you currently need to support in your operations?" }, { "id": "donor-access-permissions", "type": "select", "options": [ { "label": "Full donor control (opt-in transparency)", "value": "donor-opt-in-control" }, { "label": "Organization-wide transparency policy", "value": "org-policy-transparency" }, { "label": "Regulatory requirement (mandatory disclosure)", "value": "regulatory-mandatory" } ], "propertyMapping": { "donor-opt-in-control": { "technologies": [ "donation-platform", "smart-contracts" ], "technologyProperties": { "controlModel": "donor-controlled", "defaultPrivacy": "private", "sharingMechanism": "explicit-consent" } }, "org-policy-transparency": { "technologies": [ "audit-trail", "fund-tracking" ], "technologyProperties": { "controlModel": "policy-driven", "defaultPrivacy": "public-per-policy", "sharingMechanism": "automated-per-governance" } }, "regulatory-mandatory": { "technologies": [ "audit-trail", "smart-contracts" ], "technologyProperties": { "controlModel": "compliance-enforced", "disclosureRequirement": "mandatory", "auditability": "regulatory-proof" } } }, "prefillFrom": null, "briefSection": "Compliance and audit", "text": "What control should donors have over their fund flow data visibility?", "ngoText": "What control should donors have over their fund flow data visibility?" }, { "id": "beneficiary-choice", "label": "How will beneficiaries exercise choice in how they receive and use this service?", "type": "select", "briefSection": "Donor experience", "options": [ { "label": "Beneficiaries choose between delivery methods (cash, voucher, mobile money, direct)", "value": "delivery-choice" }, { "label": "Beneficiaries choose preferred merchants or service points", "value": "merchant-choice" }, { "label": "Beneficiaries control their own data sharing preferences", "value": "data-choice" }, { "label": "Multiple choice dimensions (delivery + merchant + data)", "value": "full-choice" }, { "label": "Limited choice: programme constraints determine delivery", "value": "limited" } ], "propertyMapping": { "delivery-choice": { "technologies": [], "technologyProperties": { "beneficiaryChoice": "Delivery method choice", "dignityDesign": "Beneficiaries select preferred receipt method" } }, "merchant-choice": { "technologies": [], "technologyProperties": { "beneficiaryChoice": "Merchant/service point choice", "dignityDesign": "Beneficiaries select where to redeem" } }, "data-choice": { "technologies": [], "technologyProperties": { "beneficiaryChoice": "Data sharing choice", "dignityDesign": "Beneficiaries control personal data sharing" } }, "full-choice": { "technologies": [], "technologyProperties": { "beneficiaryChoice": "Multi-dimensional choice", "dignityDesign": "Full beneficiary agency across delivery, merchant, and data" } }, "limited": { "technologies": [], "technologyProperties": { "beneficiaryChoice": "Limited by programme design", "dignityDesign": "Programme constraints; beneficiary informed of reasons" } } }, "text": "How will beneficiaries exercise choice in how they receive and use this service?" } ], "complexityFactors": { "relationships": 2, "operationalChange": 2, "dataCompliance": 2 }, "suggestedCriteria": [ { "id": "SC-FUND-TRANSPARENCY", "name": "End-to-End Fund Flow Visibility", "description": "The provider can show every step of a donation's path from donor to final beneficiary. For fund flow tracking, the core value proposition is complete transparency. Partial visibility defeats the purpose.", "weight": 0.3, "ratingGuide": { "5": "Real-time tracking from donor payment to beneficiary receipt with every intermediary step visible. Donors can see exactly where their money is at any point. Immutable audit trail with timestamps.", "4": "Near-complete visibility with minor gaps (e.g., last-mile delivery tracked but with slight delay). Donor dashboard shows fund status within 24 hours.", "3": "Tracks major milestones (donation received, disbursed, delivered) but intermediary steps opaque. Summary-level reporting rather than transaction-level.", "2": "Basic receipt confirmation and final delivery report only. No visibility into how funds move between receipt and disbursement.", "1": "No real-time tracking. Manual reporting only. Donors receive periodic summary statements with no transaction-level detail." } }, { "id": "SC-AUDIT-INTEGRITY", "name": "Audit Trail Immutability & Compliance", "description": "The system produces audit records that satisfy charity regulators and external auditors. Fund flow data must be tamper-evident and exportable in formats auditors recognise.", "weight": 0.25, "ratingGuide": { "5": "Blockchain-anchored audit trail with cryptographic proof of each transaction. Exportable in standard audit formats (XBRL, CSV). Tested with Big 4 or equivalent audit firms. Meets IFRS/GAAP charity accounting requirements.", "4": "Immutable records with export capability. Compatible with major accounting standards. Has been used in at least one external audit.", "3": "Tamper-evident logs but export requires custom formatting. Compatible with one major accounting standard. Not yet tested in formal audit.", "2": "Digital records with basic integrity checks but not cryptographically immutable. Manual preparation needed for audit submission.", "1": "No immutability guarantees. Records could be altered without detection. No audit-ready export capability." } }, { "id": "SC-DONOR-EXPERIENCE", "name": "Donor-Facing Portal & Accessibility", "description": "This measures how easy it is for donors of varying technical ability to access transparency information. A transparency system only works if donors actually use it. Includes dashboard quality, notification options, and multi-language support.", "weight": 0.2, "ratingGuide": { "5": "Intuitive donor portal with personalised dashboard, mobile-friendly, multi-language. Push notifications for fund milestones. Accessible to non-technical donors. API for major donors wanting programmatic access.", "4": "Clean donor dashboard with key metrics. Mobile responsive. At least 2 languages. Email notifications for major events.", "3": "Functional donor view but requires some navigation. Desktop-optimised. Single language. Manual report downloads available.", "2": "Basic web interface with limited personalisation. Donors can view aggregate data but not their specific contributions easily.", "1": "No donor-facing interface. Transparency data only accessible to organisation staff or via manual report requests." } }, { "id": "SC-INTEGRATION-EXISTING", "name": "Integration with Existing Fundraising Systems", "description": "The provider can connect with the NGO's current donation platforms, CRM, and accounting systems. Most NGOs already have fundraising infrastructure. The transparency layer must work alongside it, not replace it.", "weight": 0.15, "ratingGuide": { "5": "Pre-built connectors for major donor management and accounting platforms. Webhook support for custom integrations. Data sync is bidirectional and real-time.", "4": "Connectors for 2-3 major fundraising/accounting platforms. API available for custom integration. Sync may have minor delays.", "3": "API-based integration possible but requires development work. One pre-built connector. Batch data import/export supported.", "2": "CSV import/export only. No live API. Integration requires manual data transfer on a scheduled basis.", "1": "Standalone system with no integration capability. All data must be entered manually or the existing system must be replaced." } }, { "id": "SC-MULTI-CURRENCY", "name": "Multi-Currency & Cross-Border Tracking", "description": "The system can track donations received in multiple currencies and across jurisdictions while maintaining accurate fund flow records. Many NGOs receive international donations that must be tracked through currency conversions.", "weight": 0.1, "ratingGuide": { "5": "Supports 10+ currencies with automatic FX rate recording at each conversion point. Tracks cross-border fund movements with jurisdiction-specific compliance flags. Stablecoin bridge option available.", "4": "Supports major currencies (USD, EUR, GBP + 3-5 others). FX rates captured at transaction time. Basic cross-border tracking.", "3": "Supports 3-5 currencies. Manual FX rate entry for some conversions. Cross-border tracking at summary level.", "2": "Dual currency only (e.g., USD + one local currency). FX tracking is approximate. No jurisdiction-specific features.", "1": "Single currency only. No FX tracking. Cross-border donations require manual reconciliation outside the system." } } ], "procurement": { "marketMaturity": "emerging", "primaryMode": "tender", "alternativeModes": [ "off-the-shelf" ], "reasoning": "Transparent fund flow platforms growing with maturity.", "exampleProductCategories": [ "fund-flow-platform", "financial-transparency-saas" ], "partnerChannels": [], "lastReviewed": "2026-05-01" } }, { "id": "UC-F-081", "name": "Fractional and micro-donation enabling", "category": "F", "subcategory": "Donation Mechanisms", "description": "Let many small gifts be pooled to cut payment fees, while each donor can still see what their share paid for.", "bCriteria": [ "B1", "B8" ], "requiredComponents": [ "donation-platform", "smart-contracts", "payment-gateway" ], "conditionalComponents": [ "fund-tracking" ], "crossCategoryDependencies": [], "p2TriggerConditions": { "description": "Activated when P2 shows micro-finance activity, large donor base, and need for automated processing of small donations", "rangeSignals": [ "microfinanceComponent >=2", "donorBase >=4", "automationLevel >=3" ] }, "contextFieldsTemplate": [ "minimum_donation_amount", "target_pooled_amounts", "expected_donor_count", "transaction_frequency", "digital_payment_infrastructure", "fee_tolerance" ], "implementationComplexity": "low", "examples": { "note": "Combines with DeFi pooling mechanisms", "references": [ { "name": "GiveDirectly", "url": "https://www.givedirectly.org", "solved": "Direct cash transfer model demonstrating granular donation-to-recipient traceability at scale." }, { "name": "Endaoment", "url": "https://endaoment.org", "solved": "Crypto-native donor-advised fund supporting fractional grants from any-size donors to verified non-profits." }, { "name": "BitGive Foundation", "url": "https://www.bitgivefoundation.org", "solved": "Pioneered transparent micro-donation flows in cryptocurrency for global humanitarian causes." } ] }, "propertyMapping": {}, "solutionQuestions": [ { "id": "minimum-donation-amount", "type": "select", "options": [ { "label": "Micro-donations ($0.01 - $0.99)", "value": "micro-cent-level" }, { "label": "Small donations ($1 - $10)", "value": "small-amount" }, { "label": "Fractional shares of larger campaigns ($0.50 - $5 per share)", "value": "fractional-share-pooling" } ], "propertyMapping": { "micro-cent-level": { "technologies": [ "smart-contracts", "payment-gateway" ], "technologyProperties": { "minimumAmount": "0.01-usd", "feeStructure": "percentage-plus-flat", "feasibility": "requires-stablecoin" } }, "small-amount": { "technologies": [ "donation-platform", "payment-gateway" ], "technologyProperties": { "minimumAmount": "1-usd", "feeStructure": "percentage-based", "processingSimplicity": "standard-gateway" } }, "fractional-share-pooling": { "technologies": [ "smart-contracts", "donation-platform" ], "technologyProperties": { "minimumAmount": "fractional-pool-share", "poolingMechanism": "dynamic-aggregation", "shareTokenization": "enabled" } } }, "prefillFrom": null, "briefSection": "Infrastructure requirements", "text": "What is the minimum donation amount to support?", "ngoText": "What is the minimum donation amount to support?" }, { "id": "donation-pooling-mechanism", "type": "select", "options": [ { "label": "Daily settlement (small donations grouped and processed together)", "value": "smart-contract-batch" }, { "label": "Accumulate until threshold then transfer (e.g. send when total reaches $50)", "value": "threshold-accumulation" }, { "label": "Pooled fund management (donations combined for efficiency)", "value": "amm-liquidity-pool" } ], "propertyMapping": { "smart-contract-batch": { "technologies": [ "smart-contracts", "donation-platform" ], "technologyProperties": { "poolingMethod": "time-based-batching", "batchFrequency": "daily-or-threshold", "settlement": "bundled-transaction" } }, "threshold-accumulation": { "technologies": [ "donation-platform", "payment-gateway" ], "technologyProperties": { "poolingMethod": "amount-threshold", "triggerThreshold": "configurable", "userControl": "manual-or-auto" } }, "amm-liquidity-pool": { "technologies": [ "smart-contracts", "donation-platform" ], "technologyProperties": { "poolingMethod": "continuous-liquidity-pool", "gasOptimization": "advanced", "complexity": "high-technical" } } }, "prefillFrom": null, "briefSection": "Smart contract logic", "text": "Can your current payment system handle automated recurring payments from individual donors? What payment methods do micro-donors prefer (card, mobile money, digital currency)?", "ngoText": "Can your current payment system handle automated recurring payments from individual donors? What payment methods do micro-donors prefer (card, mobile money, crypto)?", "hidden": true }, { "id": "fee-handling-structure", "type": "select", "options": [ { "label": "Donor covers fee (displayed upfront)", "value": "donor-bears-fee" }, { "label": "Organization covers fee (net processing cost)", "value": "org-covers-fee" }, { "label": "Fee waived at threshold (e.g., free below $5)", "value": "threshold-waived-fees" }, { "label": "Community subsidy pool (other donors cover fees)", "value": "community-subsidy-pool" } ], "propertyMapping": { "donor-bears-fee": { "technologies": [ "donation-platform", "payment-gateway" ], "technologyProperties": { "feeModel": "fee-transparent", "feeImpact": "reduces-net-donation", "transparency": "explicit-at-checkout" } }, "org-covers-fee": { "technologies": [ "donation-platform", "smart-contracts" ], "technologyProperties": { "feeModel": "org-subsidy", "subsidyMechanism": "smart-contract-escrow", "sustainability": "requires-margin" } }, "threshold-waived-fees": { "technologies": [ "smart-contracts", "donation-platform" ], "technologyProperties": { "feeModel": "conditional-waiver", "waiveThreshold": "configurable", "incentiveStructure": "gamified-giving" } }, "community-subsidy-pool": { "technologies": [ "smart-contracts", "donation-platform" ], "technologyProperties": { "feeModel": "community-funded", "redistributionMechanism": "smart-contract-allocation", "fairness": "proportional-benefit" } } }, "prefillFrom": null, "briefSection": "Infrastructure requirements", "text": "How do you currently handle and allocate transaction fees?", "ngoText": "How do you currently handle and allocate transaction fees?", "hidden": true }, { "id": "supported-payment-methods", "type": "select", "options": [ { "label": "Fiat credit/debit card gateway", "value": "fiat-card-gateway" }, { "label": "Cryptocurrency wallet direct transfer", "value": "crypto-wallet-direct" }, { "label": "Mobile money", "value": "mobile-money-integration" }, { "label": "Multi-method support (hybrid)", "value": "hybrid-multi-method" } ], "propertyMapping": { "fiat-card-gateway": { "technologies": [ "payment-gateway", "donation-platform" ], "technologyProperties": { "paymentType": "fiat-card", "processing": "traditional-gateway", "userBase": "broad-accessibility" } }, "crypto-wallet-direct": { "technologies": [ "smart-contracts", "donation-platform" ], "technologyProperties": { "paymentType": "native-crypto", "userBase": "crypto-native", "gasOptimization": "required" } }, "mobile-money-integration": { "technologies": [ "payment-gateway", "donation-platform" ], "technologyProperties": { "paymentType": "mobile-money", "regionRelevance": "emerging-markets", "liquidityProvider": "required" } }, "hybrid-multi-method": { "technologies": [ "payment-gateway", "smart-contracts", "donation-platform" ], "technologyProperties": { "paymentType": "multi-method", "integration": "modular-adapters", "userChoice": "full-flexibility" } } }, "prefillFrom": null, "briefSection": "Donation infrastructure", "text": "Which payment methods should be supported for micro-donations?", "ngoText": "Which payment methods should be supported for micro-donations?" }, { "id": "micro-donation-compliance", "type": "multiselect", "options": [ { "label": "Tax deductibility receipting", "value": "tax" }, { "label": "Anti-money laundering (AML) / Know Your Donor", "value": "aml" }, { "label": "Cross-border fund transfer regulations", "value": "cross-border" }, { "label": "Cryptocurrency-specific regulations", "value": "crypto-reg" }, { "label": "No specific compliance requirements", "value": "none" } ], "propertyMapping": { "tax": { "technologies": [ "Automated receipt generation" ], "technologyProperties": { "complianceModule": "Tax receipting", "regulatoryRisk": "Low" } }, "aml": { "technologies": [ "KYC/AML screening module" ], "technologyProperties": { "complianceModule": "AML screening", "regulatoryRisk": "Medium" } }, "cross-border": { "technologies": [ "Cross-border compliance module" ], "technologyProperties": { "complianceModule": "Transfer regulations", "regulatoryRisk": "High" } }, "crypto-reg": { "technologies": [ "Crypto compliance framework" ], "technologyProperties": { "complianceModule": "Crypto regulations", "regulatoryRisk": "High" } }, "none": { "technologies": [], "technologyProperties": { "complianceModule": "None required", "regulatoryRisk": "Low" } } }, "prefillFrom": null, "briefSection": "Compliance and audit", "text": "What financial compliance requirements apply to micro-donations?", "ngoText": "What financial compliance requirements apply to micro-donations?" }, { "id": "sq-UC-F-089-001", "type": "single-select", "options": [ { "value": "fixed-threshold-release", "label": "Fixed threshold release" }, { "value": "time-based-batching", "label": "Time-based batching" }, { "value": "project-goal-reached", "label": "Project goal reached" }, { "value": "donor-directed-timing", "label": "Donor-directed timing" }, { "value": "hybrid-threshold-and-time", "label": "Hybrid threshold and time" } ], "propertyMapping": { "fixed-threshold-release": { "technologies": [ "threshold-logic", "auto-release" ], "technologyProperties": {} }, "time-based-batching": { "technologies": [ "batch-scheduler", "time-based-release" ], "technologyProperties": {} }, "project-goal-reached": { "technologies": [ "goal-tracking", "completion-trigger" ], "technologyProperties": {} }, "donor-directed-timing": { "technologies": [ "donor-control", "manual-trigger" ], "technologyProperties": {} }, "hybrid-threshold-and-time": { "technologies": [ "combined-logic", "dual-trigger" ], "technologyProperties": {} } }, "briefSection": "requirements", "text": "What is the minimum amount and frequency needed before donor funds should be available to beneficiaries (e.g., daily threshold, weekly batching)?", "ngoText": "What is the minimum amount and frequency needed before donor funds should be available to beneficiaries (e.g., daily threshold, weekly batching)?" }, { "id": "beneficiary-choice", "label": "How will beneficiaries exercise choice in how they receive and use this service?", "type": "select", "briefSection": "Donor experience", "options": [ { "label": "Beneficiaries choose between delivery methods (cash, voucher, mobile money, direct)", "value": "delivery-choice" }, { "label": "Beneficiaries choose preferred merchants or service points", "value": "merchant-choice" }, { "label": "Beneficiaries control their own data sharing preferences", "value": "data-choice" }, { "label": "Multiple choice dimensions (delivery + merchant + data)", "value": "full-choice" }, { "label": "Limited choice: programme constraints determine delivery", "value": "limited" } ], "propertyMapping": { "delivery-choice": { "technologies": [], "technologyProperties": { "beneficiaryChoice": "Delivery method choice", "dignityDesign": "Beneficiaries select preferred receipt method" } }, "merchant-choice": { "technologies": [], "technologyProperties": { "beneficiaryChoice": "Merchant/service point choice", "dignityDesign": "Beneficiaries select where to redeem" } }, "data-choice": { "technologies": [], "technologyProperties": { "beneficiaryChoice": "Data sharing choice", "dignityDesign": "Beneficiaries control personal data sharing" } }, "full-choice": { "technologies": [], "technologyProperties": { "beneficiaryChoice": "Multi-dimensional choice", "dignityDesign": "Full beneficiary agency across delivery, merchant, and data" } }, "limited": { "technologies": [], "technologyProperties": { "beneficiaryChoice": "Limited by programme design", "dignityDesign": "Programme constraints; beneficiary informed of reasons" } } }, "text": "How will beneficiaries exercise choice in how they receive and use this service?" } ], "complexityFactors": { "relationships": 2, "operationalChange": 2, "dataCompliance": 2 }, "suggestedCriteria": [ { "id": "SC-MICRO-FEE", "name": "Transaction Fee Efficiency for Small Amounts", "description": "The provider can process very small donations without fees consuming a disproportionate share. For micro-donations, a $2 fee on a $5 gift makes the system unviable. Fee structure is the make-or-break criterion.", "weight": 0.3, "ratingGuide": { "5": "Sub-1% fees on donations as small as $1. Layer-2 or batching solutions that amortise gas costs across multiple micro-transactions. Transparent fee display to donors.", "4": "1-3% fees on small donations ($1-$10). Batching reduces per-transaction cost. Fee clearly shown before donor commits.", "3": "3-5% fees on small donations. Some batching capability but not fully optimised. Minimum viable for donations above $5.", "2": "5-10% fees on small donations. No batching \u2014 each micro-donation processed individually. Only viable for donations above $10.", "1": "Fees exceed 10% for small donations. Fixed per-transaction charges make micro-donations economically unviable." } }, { "id": "SC-POOLING", "name": "Donation Pooling & Aggregation", "description": "This measures how effectively the system pools small donations into meaningful amounts while maintaining individual attribution. Pooling is what makes micro-donations practical: donors give small but the NGO receives usable sums.", "weight": 0.25, "ratingGuide": { "5": "Automated smart contract pooling with configurable thresholds. Individual donor attribution preserved within pools. Real-time pool status visible to donors. Multiple pooling strategies (time-based, threshold-based, campaign-based).", "4": "Automated pooling with threshold triggers. Individual attribution maintained. Donors notified when pool disburses. 2-3 pooling options.", "3": "Daily batch pooling with basic attribution. Donors see their contribution in aggregate reports. Single pooling strategy.", "2": "Manual pooling by NGO staff. Attribution tracked in separate records. Donors see pooled totals only.", "1": "No pooling capability. Each micro-donation processed as standalone transaction, resulting in high per-unit costs." } }, { "id": "SC-DONOR-ONBOARDING", "name": "Donor Onboarding Simplicity", "description": "This measures how easy it is for a first-time donor to make a micro-donation. Micro-donation success depends on impulse giving. If signup takes more than 60 seconds or requires a crypto wallet, most donors will abandon.", "weight": 0.2, "ratingGuide": { "5": "One-click donation with no account creation required. Supports mobile wallets, card, and mobile money. Guest checkout with optional account creation after. Under 30 seconds to complete.", "4": "Minimal signup (email only). 3-4 payment methods supported. Under 60 seconds to first donation.", "3": "Basic account creation required (email + password). Card and one alternative payment method. 1-2 minutes to first donation.", "2": "Full registration required before donating. Card payment only. 3-5 minute onboarding process.", "1": "Requires crypto wallet setup or complex registration. Technical knowledge assumed. Most casual donors will abandon." } }, { "id": "SC-DONOR-TRACKING", "name": "Individual Donation Tracking & Receipting", "description": "Each micro-donor can see where their specific contribution went, even within a pooled fund. The system can generate tax receipts for small amounts. Attribution and receipting build the trust that drives repeat micro-giving.", "weight": 0.15, "ratingGuide": { "5": "Each donor sees their proportional impact within pooled funds. Automated tax receipts generated per jurisdiction. Annual giving summaries. Blockchain-verified proof of donation available.", "4": "Donor dashboard shows contribution history and proportional impact. Tax receipts for donations above threshold. Annual summary available.", "3": "Donor receives confirmation emails with basic tracking. Tax receipts available on request. Aggregate impact shown.", "2": "Email receipt only. No ongoing tracking. Tax receipts require manual request to NGO.", "1": "No individual tracking after donation. No automated receipting. Donor has no visibility into fund use." } }, { "id": "SC-SCALE-VOLUME", "name": "High-Volume Transaction Processing", "description": "The system can handle thousands of simultaneous micro-donations during campaign peaks without degradation. Micro-donation campaigns often spike during events. The system must handle bursts.", "weight": 0.1, "ratingGuide": { "5": "Handles 10,000+ transactions per minute during peaks. Auto-scaling infrastructure. No degradation during campaign surges. Proven at scale in live campaigns.", "4": "Handles 1,000-10,000 transactions per minute. Minimal latency increase during peaks. Tested under load.", "3": "Handles hundreds of transactions per minute. Some queuing during peak campaigns. Recovers within minutes.", "2": "Handles tens of transactions per minute. Noticeable slowdowns during campaigns. May require manual scaling.", "1": "Single-digit transactions per minute. System bottlenecks during any campaign activity. Not suitable for public fundraising campaigns." } } ], "procurement": { "marketMaturity": "emerging", "primaryMode": "off-the-shelf", "alternativeModes": [ "rfq" ], "reasoning": "Fractional and micro-donation platforms growing.", "exampleProductCategories": [ "micro-donation-platform", "giving-platform" ], "partnerChannels": [], "lastReviewed": "2026-05-01" } }, { "id": "UC-F-082", "name": "Cryptocurrency and digital asset donations", "category": "F", "subcategory": "Donation Mechanisms", "description": "Accept donations made in cryptocurrency, and record when and at what rate each one was changed into ordinary money.", "bCriteria": [ "B3", "B8", "B4" ], "requiredComponents": [ "crypto-acceptance", "payment-gateway", "fund-tracking", "audit-trail" ], "conditionalComponents": [ "smart-contracts", "donation-platform" ], "crossCategoryDependencies": [], "p2TriggerConditions": { "description": "Activated when P2 shows significant cryptocurrency involvement, diverse digital asset holdings, and volatility management challenges", "rangeSignals": [ "cryptocurrencyInvolvement >=3", "assetDiversification >=2", "volatilityManagement >=2" ] }, "contextFieldsTemplate": [ "accepted_cryptocurrencies", "conversion_mechanism", "stablecoin_preference", "regulatory_jurisdiction", "kyc_aml_requirements", "volatility_hedging_strategy", "exchange_rate_lock_period" ], "implementationComplexity": "high", "examples": { "note": "UNICEF, Save the Children already accepting crypto; requires compliance layer", "references": [ { "name": "The Giving Block", "url": "https://thegivingblock.com", "solved": "Crypto donation infrastructure used by over 2,000 non-profits including UNICEF, Save the Children, American Cancer Society." }, { "name": "Endaoment", "url": "https://endaoment.org", "solved": "Crypto-native 501(c)(3) infrastructure enabling tax-receipted digital asset donations." }, { "name": "BitPay for Nonprofits", "url": "https://bitpay.com/non-profit", "solved": "Payment processing layer for non-profits accepting crypto donations across multiple chains." } ] }, "propertyMapping": {}, "solutionQuestions": [ { "id": "accepted-token-types", "text": "What types of digital assets would you like to accept as donations?", "ngoText": "What types of digital assets would you like to accept as donations?", "type": "select", "briefSection": "Fund tracking", "options": [ { "value": "stablecoin-only", "label": "Stablecoins only" }, { "value": "stablecoin-plus-btc", "label": "Stablecoins plus one major non-stablecoin asset" }, { "value": "top-10", "label": "Top 10 assets by market capitalisation" }, { "value": "top-25", "label": "Top 25 assets by market capitalisation" }, { "value": "all-assets", "label": "All digital assets (no restrictions)" } ], "propertyMapping": { "stablecoin-only": { "technologies": [ "stablecoin-custody" ], "technologyProperties": { "acceptedAssets": "Stablecoins only" } }, "stablecoin-plus-btc": { "technologies": [ "stablecoin-custody", "bitcoin-custody" ], "technologyProperties": { "acceptedAssets": "Stablecoins plus one major non-stablecoin asset" } }, "top-10": { "technologies": [ "multi-asset-custody", "exchange-integration" ], "technologyProperties": { "acceptedAssets": "Top 10 assets by market cap" } }, "top-25": { "technologies": [ "multi-asset-custody", "exchange-integration", "portfolio-management" ], "technologyProperties": { "acceptedAssets": "Top 25 assets by market cap" } }, "all-assets": { "technologies": [ "multi-asset-custody", "exchange-integration", "portfolio-management", "defi-integration" ], "technologyProperties": { "acceptedAssets": "All digital assets (unrestricted)" } } }, "hidden": true }, { "id": "accepted-crypto-types", "type": "select", "options": [ { "label": "One major non-stablecoin asset only", "value": "bitcoin-only" }, { "label": "Major digital asset networks and tokens", "value": "ethereum-ecosystem" }, { "label": "Stablecoins only", "value": "stablecoin-only" }, { "label": "Multi-chain support (major networks, lower-cost networks, high-speed networks)", "value": "multi-chain-support" }, { "label": "Donor choice (any major crypto accepted)", "value": "donor-choice-flexible" } ], "propertyMapping": { "bitcoin-only": { "technologies": [ "crypto-acceptance", "payment-gateway" ], "technologyProperties": { "assetType": "bitcoin-btc", "volatility": "high", "liquidity": "maximum", "exchangeComplexity": "standard" } }, "ethereum-ecosystem": { "technologies": [ "crypto-acceptance", "smart-contracts" ], "technologyProperties": { "assetType": "ethereum-native", "tokenVariety": "multiple-standards", "liquidityAccess": "dex-based", "gasConsideration": "network-dependent" } }, "stablecoin-only": { "technologies": [ "crypto-acceptance", "payment-gateway" ], "technologyProperties": { "assetType": "stablecoin-usd-pegged", "volatility": "minimal", "accounting": "simplified", "donorFriction": "reduced" } }, "multi-chain-support": { "technologies": [ "crypto-acceptance", "smart-contracts", "payment-gateway" ], "technologyProperties": { "assetType": "multi-chain-diverse", "bridgeRequirement": "cross-chain-enabled", "liquiditySources": "aggregated", "complexity": "high-integration" } }, "donor-choice-flexible": { "technologies": [ "crypto-acceptance", "payment-gateway", "smart-contracts" ], "technologyProperties": { "assetType": "permissive-open", "conversionEngine": "real-time-oracle", "flexibility": "maximum-donor-choice", "riskManagement": "required" } } }, "prefillFrom": null, "briefSection": "Donation infrastructure", "text": "Which cryptocurrency types should be accepted for donations?", "ngoText": "Which cryptocurrency types should be accepted for donations?", "hidden": true }, { "id": "crypto-conversion-strategy", "type": "select", "options": [ { "label": "Immediate conversion at receipt (minimize volatility exposure)", "value": "immediate-conversion" }, { "label": "Time-delayed conversion (batched weekly/monthly)", "value": "batched-delayed-conversion" }, { "label": "Donor choice (keep crypto or auto-convert)", "value": "donor-choice-conversion" }, { "label": "automated escrow (hold crypto for time-release)", "value": "escrow-time-release" } ], "propertyMapping": { "immediate-conversion": { "technologies": [ "payment-gateway", "crypto-acceptance" ], "technologyProperties": { "conversionTiming": "immediate-receipt", "volatilityExposure": "minimal-org", "donorValue": "locked-at-donation", "donorFriction": "high-gas-cost" } }, "batched-delayed-conversion": { "technologies": [ "payment-gateway", "smart-contracts" ], "technologyProperties": { "conversionTiming": "scheduled-batch", "batchFrequency": "weekly-monthly", "volatilityExposure": "moderate-org", "feeOptimization": "higher" } }, "donor-choice-conversion": { "technologies": [ "crypto-acceptance", "smart-contracts" ], "technologyProperties": { "conversionTiming": "donor-elected", "flexibility": "full-choice", "accountingComplexity": "high", "donorControl": "maximum" } }, "escrow-time-release": { "technologies": [ "smart-contracts", "crypto-acceptance" ], "technologyProperties": { "conversionTiming": "programmatic-release", "hedgingMechanism": "smart-contract-programmed", "volatilityManagement": "algorithmic", "complexity": "advanced" } } }, "prefillFrom": null, "briefSection": "Fund tracking", "text": "If you received cryptocurrency, how would you want to convert it to usable currency?", "ngoText": "If you received cryptocurrency, how would you want to convert it to usable currency?" }, { "id": "kyc-aml-requirements", "type": "select", "options": [ { "label": "No KYC (permissionless acceptance)", "value": "no-kyc-permissionless" }, { "label": "Light KYC (name + email verification)", "value": "light-kyc-basic" }, { "label": "Full KYC (identity + source of funds verification)", "value": "full-kyc-comprehensive" }, { "label": "Tiered KYC (escalating requirements by amount)", "value": "tiered-kyc-progressive" } ], "propertyMapping": { "no-kyc-permissionless": { "technologies": [ "crypto-acceptance", "donation-platform" ], "technologyProperties": { "complianceLevel": "minimal", "riskProfile": "high", "userFriction": "zero", "jurisdictionRisk": "variable" } }, "light-kyc-basic": { "technologies": [ "crypto-acceptance", "donation-platform" ], "technologyProperties": { "complianceLevel": "basic-identity", "thresholdAmount": "3000-usd-annual", "verification": "email-sms", "donorFriction": "low" } }, "full-kyc-comprehensive": { "technologies": [ "crypto-acceptance", "payment-gateway" ], "technologyProperties": { "complianceLevel": "aml-kyc-full", "verification": "document-based", "sourceOfFunds": "verified", "donorFriction": "high" } }, "tiered-kyc-progressive": { "technologies": [ "crypto-acceptance", "smart-contracts" ], "technologyProperties": { "complianceLevel": "risk-based", "tierThresholds": "configurable", "verification": "progressive-escalation", "balance": "usability-compliance" } } }, "prefillFrom": null, "briefSection": "Compliance and audit", "text": "What KYC/AML compliance is required for crypto donations?", "ngoText": "What KYC/AML compliance is required for crypto donations?" }, { "id": "volatility-hedging-strategy", "type": "select", "options": [ { "label": "No hedging (accept volatility risk)", "value": "no-hedging-accept-risk" }, { "label": "Immediate stablecoin conversion (pass risk to exchange)", "value": "immediate-stablecoin" }, { "label": "Futures/options hedge (advanced derivatives)", "value": "derivatives-hedge" }, { "label": "Donor contribution to volatility buffer fund", "value": "volatility-buffer-pool" } ], "propertyMapping": { "no-hedging-accept-risk": { "technologies": [ "crypto-acceptance", "fund-tracking" ], "technologyProperties": { "hedgingStrategy": "none", "volatilityManagement": "passthrough", "riskProfile": "organization-bears-all", "simplicity": "highest" } }, "immediate-stablecoin": { "technologies": [ "payment-gateway", "crypto-acceptance" ], "technologyProperties": { "hedgingStrategy": "conversion-to-stable", "riskTransfer": "to-exchange", "volatilityExposure": "minimal-org", "cost": "exchange-fees" } }, "derivatives-hedge": { "technologies": [ "smart-contracts", "crypto-acceptance" ], "technologyProperties": { "hedgingStrategy": "derivatives-based", "instruments": "futures-options", "complexity": "high-financial", "counterpartyRisk": "required-monitoring" } }, "volatility-buffer-pool": { "technologies": [ "smart-contracts", "donation-platform" ], "technologyProperties": { "hedgingStrategy": "collective-buffer", "bufferMechanism": "shared-pool", "fairness": "proportional-allocation", "donorEducation": "required" } } }, "prefillFrom": null, "briefSection": "Infrastructure requirements", "text": "What approach would you prefer for managing volatility risk from cryptocurrency donations?", "ngoText": "What approach would you prefer for managing volatility risk from cryptocurrency donations?" }, { "id": "tax-compliance-reporting", "type": "select", "options": [ { "label": "Donor-managed tax compliance (no org reporting)", "value": "donor-self-report" }, { "label": "Automated donor tax reports (1098-C style)", "value": "automated-donor-tax-reports" }, { "label": "FMV assessment + org reporting (IRS Form 8949)", "value": "fmv-assessment-org-reporting" }, { "label": "Automated tax calculations", "value": "smart-contract-tax-automation" }, { "label": "Stablecoin-only (simplified tax treatment)", "value": "stablecoin-simplified-tax" } ], "propertyMapping": { "donor-self-report": { "technologies": [ "donation-platform", "audit-trail" ], "technologyProperties": { "reportingResponsibility": "donor", "documentation": "transaction-records-provided", "orgLiability": "minimal", "clarity": "low" } }, "automated-donor-tax-reports": { "technologies": [ "reporting-automation", "donation-platform" ], "technologyProperties": { "reportingResponsibility": "shared", "automationLevel": "full", "compliance": "tax-report-standard", "infrastructure": "tax-report-generation" } }, "fmv-assessment-org-reporting": { "technologies": [ "reporting-automation", "audit-trail" ], "technologyProperties": { "reportingResponsibility": "organization", "fmvDetermination": "fair-market-value", "compliance": "irs-section-170", "donorComplexity": "detailed-reporting" } }, "smart-contract-tax-automation": { "technologies": [ "smart-contracts", "reporting-automation" ], "technologyProperties": { "reportingResponsibility": "automated-contract", "taxCalculation": "programmatic", "compliance": "jurisdiction-aware", "complexity": "requires-oracle" } }, "stablecoin-simplified-tax": { "technologies": [ "crypto-acceptance", "donation-platform" ], "technologyProperties": { "reportingResponsibility": "standard-donation", "taxTreatment": "simplified", "compliance": "no-gains-no-losses", "donorFriction": "minimal" } } }, "prefillFrom": null, "briefSection": "Compliance and audit", "text": "What tax compliance and reporting approach would you need for cryptocurrency donations?", "ngoText": "What tax compliance and reporting approach would you need for cryptocurrency donations?" }, { "id": "crypto-donation-redemption", "type": "select", "options": [ { "label": "No redemption (irrevocable donation)", "value": "no-redemption-irrevocable" }, { "label": "Limited redemption window (30-90 days)", "value": "limited-redemption-window" }, { "label": "Conditional redemption (not used yet)", "value": "conditional-redemption-unused" } ], "propertyMapping": { "no-redemption-irrevocable": { "technologies": [ "donation-platform", "audit-trail" ], "technologyProperties": { "redemptionPolicy": "none", "donationFinality": "irrevocable", "taxTreatment": "standard-charitable", "organizationSecurability": "highest" } }, "limited-redemption-window": { "technologies": [ "smart-contracts", "donation-platform" ], "technologyProperties": { "redemptionPolicy": "time-limited", "redemptionWindow": "30-90-days", "verification": "manual-approval", "operationalComplexity": "moderate" } }, "conditional-redemption-unused": { "technologies": [ "smart-contracts", "donation-platform" ], "technologyProperties": { "redemptionPolicy": "conditional-unused", "condition": "funds-not-deployed", "transparency": "real-time-status", "taxImplications": "complex" } } }, "prefillFrom": null, "briefSection": "Smart contract logic", "text": "Should donors be able to redeem their crypto donations?", "ngoText": "Should donors be able to redeem their crypto donations?", "hidden": true }, { "id": "crypto-acceptance-count", "label": "How many different cryptocurrencies/tokens does the NGO need to accept?", "type": "select", "briefSection": "donation-acceptance", "options": [ { "label": "Major coins only", "value": "major-only" }, { "label": "Top 10\u201320 cryptocurrencies", "value": "top-20" }, { "label": "Wide acceptance (50+ tokens including ERC-20s)", "value": "wide" }, { "label": "All major chains and tokens (80+)", "value": "all" } ], "propertyMapping": { "major-only": { "technologies": [ "Basic crypto donation wallet" ], "technologyProperties": { "acceptanceScope": "Major coins only", "walletComplexity": "Low" } }, "top-20": { "technologies": [ "Multi-chain donation wallet" ], "technologyProperties": { "acceptanceScope": "Top 10\u201320 cryptocurrencies", "walletComplexity": "Medium" } }, "wide": { "technologies": [ "Multi-chain donation aggregator" ], "technologyProperties": { "acceptanceScope": "50+ tokens", "walletComplexity": "High" } }, "all": { "technologies": [ "Universal crypto donation platform" ], "technologyProperties": { "acceptanceScope": "80+ chains and tokens", "walletComplexity": "Very high" } } }, "text": "How many different cryptocurrencies/tokens does the NGO need to accept?" }, { "id": "conversion-strategy-detail", "label": "What is the conversion strategy for received crypto donations?", "type": "select", "briefSection": "conversion-strategy", "options": [ { "label": "Immediate conversion to fiat (minimise volatility risk)", "value": "immediate-fiat" }, { "label": "Immediate conversion to stablecoin (held as a regulated stablecoin)", "value": "immediate-stable" }, { "label": "Hold as crypto with periodic conversion", "value": "hold-periodic" }, { "label": "Hybrid: immediate conversion for operations, hold portion as reserve", "value": "hybrid" } ], "propertyMapping": { "immediate-fiat": { "technologies": [ "Auto-conversion engine (crypto to fiat)", "Banking integration" ], "technologyProperties": { "conversionStrategy": "Immediate fiat conversion", "volatilityExposure": "Minimal" } }, "immediate-stable": { "technologies": [ "Auto-conversion engine (crypto to stablecoin)" ], "technologyProperties": { "conversionStrategy": "Immediate stablecoin conversion", "volatilityExposure": "Low" } }, "hold-periodic": { "technologies": [ "Crypto treasury management", "Scheduled conversion module" ], "technologyProperties": { "conversionStrategy": "Hold with periodic conversion", "volatilityExposure": "High" } }, "hybrid": { "technologies": [ "Hybrid treasury engine", "Split-conversion rules" ], "technologyProperties": { "conversionStrategy": "Hybrid (immediate + reserve)", "volatilityExposure": "Medium" } } }, "text": "What is the conversion strategy for received crypto donations?" }, { "id": "aml-screening-donations", "label": "What AML/sanctions screening is needed for donation source addresses?", "type": "select", "briefSection": "compliance-screening", "options": [ { "label": "Full digital analytics screening of all incoming addresses", "value": "full-screening" }, { "label": "Screening above a threshold amount", "value": "threshold" }, { "label": "Basic sanctions list check only", "value": "basic" }, { "label": "Unsure, need compliance guidance", "value": "unsure" } ], "propertyMapping": { "full-screening": { "technologies": [ "Blockchain analytics integration", "Real-time AML screening" ], "technologyProperties": { "amlScreening": "Full \u2014 all incoming addresses", "complianceBurden": "High" } }, "threshold": { "technologies": [ "Threshold-based AML screening" ], "technologyProperties": { "amlScreening": "Threshold-based (above specified amount)", "complianceBurden": "Medium" } }, "basic": { "technologies": [ "Sanctions list screening module" ], "technologyProperties": { "amlScreening": "Basic sanctions list check", "complianceBurden": "Low" } }, "unsure": { "technologies": [], "technologyProperties": { "amlScreening": "Compliance assessment needed", "complianceBurden": "To be determined" } } }, "text": "What AML/sanctions screening is needed for donation source addresses?" }, { "id": "tax-receipt-requirements", "label": "What tax receipt/documentation requirements exist for crypto donations?", "type": "select", "briefSection": "tax-documentation", "options": [ { "label": "Must issue tax receipts with fair market value at time of donation", "value": "full-receipt" }, { "label": "Tax receipt needed only for donations above a threshold", "value": "threshold-receipt" }, { "label": "No tax receipt requirement (jurisdiction doesn't recognise crypto donations)", "value": "no-receipt" }, { "label": "Multiple jurisdictions with different requirements", "value": "multi-jurisdiction" } ], "propertyMapping": { "full-receipt": { "technologies": [ "Crypto tax receipt engine", "Fair market value oracle" ], "technologyProperties": { "taxDocumentation": "Full receipt with FMV required", "jurisdictionalComplexity": "Standard" } }, "threshold-receipt": { "technologies": [ "Threshold-based tax receipt module" ], "technologyProperties": { "taxDocumentation": "Threshold-based receipts", "jurisdictionalComplexity": "Standard" } }, "no-receipt": { "technologies": [], "technologyProperties": { "taxDocumentation": "No receipt required", "jurisdictionalComplexity": "Low" } }, "multi-jurisdiction": { "technologies": [ "Multi-jurisdiction tax compliance engine" ], "technologyProperties": { "taxDocumentation": "Multi-jurisdiction requirements", "jurisdictionalComplexity": "High" } } }, "text": "What tax receipt/documentation requirements exist for crypto donations?" }, { "id": "donation-channel", "label": "Is the NGO accepting crypto donations directly or through a third-party processor?", "type": "select", "briefSection": "donation-acceptance", "options": [ { "label": "Direct: NGO manages its own donation wallets", "value": "direct" }, { "label": "Third-party processor handles acceptance and conversion", "value": "third-party" }, { "label": "Hybrid: direct for major coins, processor for others", "value": "hybrid" }, { "label": "Undecided: need to evaluate options", "value": "undecided" } ], "propertyMapping": { "direct": { "technologies": [ "Self-managed donation wallet infrastructure", "Multi-sig custody" ], "technologyProperties": { "donationChannel": "Direct \u2014 self-managed wallets", "operationalBurden": "High \u2014 requires crypto expertise" } }, "third-party": { "technologies": [ "Crypto donation processor integration" ], "technologyProperties": { "donationChannel": "Third-party processor", "operationalBurden": "Low \u2014 processor handles operations" } }, "hybrid": { "technologies": [ "Hybrid donation infrastructure" ], "technologyProperties": { "donationChannel": "Hybrid \u2014 direct + processor", "operationalBurden": "Medium" } }, "undecided": { "technologies": [], "technologyProperties": { "donationChannel": "To be determined", "operationalBurden": "Evaluation needed" } } }, "text": "Is the NGO accepting crypto donations directly or through a third-party processor?" }, { "id": "beneficiary-choice", "label": "How will beneficiaries exercise choice in how they receive and use this service?", "type": "select", "briefSection": "Donor experience", "options": [ { "label": "Beneficiaries choose between delivery methods (cash, voucher, mobile money, direct)", "value": "delivery-choice" }, { "label": "Beneficiaries choose preferred merchants or service points", "value": "merchant-choice" }, { "label": "Beneficiaries control their own data sharing preferences", "value": "data-choice" }, { "label": "Multiple choice dimensions (delivery + merchant + data)", "value": "full-choice" }, { "label": "Limited choice: programme constraints determine delivery", "value": "limited" } ], "propertyMapping": { "delivery-choice": { "technologies": [], "technologyProperties": { "beneficiaryChoice": "Delivery method choice", "dignityDesign": "Beneficiaries select preferred receipt method" } }, "merchant-choice": { "technologies": [], "technologyProperties": { "beneficiaryChoice": "Merchant/service point choice", "dignityDesign": "Beneficiaries select where to redeem" } }, "data-choice": { "technologies": [], "technologyProperties": { "beneficiaryChoice": "Data sharing choice", "dignityDesign": "Beneficiaries control personal data sharing" } }, "full-choice": { "technologies": [], "technologyProperties": { "beneficiaryChoice": "Multi-dimensional choice", "dignityDesign": "Full beneficiary agency across delivery, merchant, and data" } }, "limited": { "technologies": [], "technologyProperties": { "beneficiaryChoice": "Limited by programme design", "dignityDesign": "Programme constraints; beneficiary informed of reasons" } } }, "text": "How will beneficiaries exercise choice in how they receive and use this service?" } ], "complexityFactors": { "relationships": 2, "operationalChange": 3, "dataCompliance": 3 }, "suggestedCriteria": [ { "id": "SC-CRYPTO-COMPLIANCE", "name": "Cryptocurrency Regulatory Compliance", "description": "The provider handles the complicated regulation of accepting crypto donations across jurisdictions. Charity crypto acceptance involves tax reporting, AML/KYC, and jurisdiction-specific rules that vary widely.", "weight": 0.3, "ratingGuide": { "5": "Licensed or registered in multiple jurisdictions for crypto operations. Automated KYC/AML screening for crypto donors. Tax receipt generation per jurisdiction (e.g., IRS 8283 for US, HMRC for UK). Sanctions screening on wallet addresses. Legal opinion available.", "4": "Compliant in 2-3 major jurisdictions. KYC/AML screening integrated. Tax receipts for major markets. Sanctions list checking.", "3": "Compliant in one jurisdiction. Basic KYC for large donations. Tax receipts for one market. Manual sanctions checking.", "2": "Limited compliance infrastructure. KYC only for very large donations. Tax reporting is NGO's responsibility. No wallet screening.", "1": "No regulatory compliance framework. NGO assumes all compliance risk. No KYC/AML, no tax reporting, no sanctions screening." } }, { "id": "SC-CONVERSION", "name": "Crypto-to-Fiat Conversion & Volatility Protection", "description": "This measures how quickly and cost-effectively donated crypto assets can be converted to usable fiat currency. NGOs need programme funds in fiat. Holding volatile crypto exposes them to price risk that donors and boards won't accept.", "weight": 0.25, "ratingGuide": { "5": "Instant auto-conversion to fiat at donation time. Sub-1% conversion spread. Multiple fiat currency options. Donor sees exact fiat equivalent before confirming. Rate-lock guarantee.", "4": "Conversion within hours. 1-2% spread. Major fiat currencies supported. Donor shown estimated fiat value.", "3": "Same-day conversion. 2-4% spread. USD/EUR conversion available. Some price slippage risk on large donations.", "2": "1-3 day conversion. 4-7% spread. Single fiat currency. Material price exposure between donation and conversion.", "1": "Manual conversion required via exchange. Multi-day process. Large spread. Full volatility exposure. NGO needs crypto exchange expertise." } }, { "id": "SC-ASSET-BREADTH", "name": "Supported Asset Range & Chain Coverage", "description": "This measures how many cryptocurrencies and blockchain networks the provider supports. Crypto donors hold diverse assets. Limiting acceptance to one or two tokens significantly reduces the donor pool.", "weight": 0.2, "ratingGuide": { "5": "Supports 50+ assets across 10+ chains. Includes the major tokens plus stablecoins. NFT donations accepted. Automatic chain detection.", "4": "Supports 20-50 assets across 5-10 chains. All major tokens and stablecoins. Clear documentation on supported assets.", "3": "Supports 10-20 assets across 3-5 chains. Major tokens covered. Stablecoin support. Limited altcoin coverage.", "2": "Supports 3-10 assets on 1-2 chains. The two largest assets plus a few others. No NFT support.", "1": "Supports only 1-2 assets (e.g., a single asset only). Single chain. Severely limits potential donor base." } }, { "id": "SC-DONOR-TAX", "name": "Donor Tax Benefit & Valuation Documentation", "description": "The provider can generate proper fair market value documentation at time of donation for donor tax deductions. Crypto donors often donate specifically for the tax benefit of gifting appreciated assets: incorrect valuation documentation eliminates their incentive.", "weight": 0.15, "ratingGuide": { "5": "Automated FMV capture at exact donation timestamp across all supported assets. Generates jurisdiction-appropriate tax documentation (US IRS forms, UK Self Assessment, etc.). Integrates with donor tax software. Qualified appraisal facilitation for large donations.", "4": "FMV captured at donation time for major assets. Tax documentation for 2-3 jurisdictions. Donor receives formatted receipt within 24 hours.", "3": "FMV captured but may have minor timing discrepancies. Tax receipt for one jurisdiction. Manual process for non-standard assets.", "2": "Approximate FMV based on daily average. Basic receipt only \u2014 donor's accountant must prepare tax forms. Single jurisdiction.", "1": "No FMV documentation. Donor responsible for all valuation and tax documentation. Receipt shows crypto amount only, not fiat equivalent." } }, { "id": "SC-CUSTODY-SECURITY", "name": "Custody & Wallet Security", "description": "This looks at how donated crypto assets are secured between receipt and conversion. Even brief custody periods create security responsibility. A breach of donated crypto is both a financial and reputational catastrophe for an NGO.", "weight": 0.1, "ratingGuide": { "5": "Institutional-grade custody (insured, SOC 2 audited). Multi-signature controls. Auto-conversion minimises custody window. Insurance covers full asset value. Cold storage for any held assets.", "4": "Qualified custodian with insurance. Multi-sig or MPC wallet security. Conversion within hours reduces exposure. Partial insurance coverage.", "3": "Reputable custody solution with basic insurance. Standard wallet security. Same-day conversion target. Some insurance coverage.", "2": "Self-custody with basic security measures. No insurance. Conversion is manual. NGO bears full custody risk.", "1": "No custody infrastructure. Crypto sent to basic hot wallet. No insurance, no multi-sig, no audit. Unacceptable risk for charitable funds." } } ], "procurement": { "marketMaturity": "mature", "primaryMode": "off-the-shelf", "alternativeModes": [ "rfq" ], "reasoning": "Crypto donation platforms are mature in giving vertical.", "exampleProductCategories": [ "crypto-giving-platform", "digital-asset-donation-rails" ], "partnerChannels": [], "lastReviewed": "2026-05-01" } }, { "id": "UC-F-083", "name": "Impact verification tied to specific donations", "category": "F", "subcategory": "Donor Transparency", "description": "Link each donor's gift to the results it helped achieve, and let the donor check those results for themselves.", "bCriteria": [ "B1", "B3", "B6" ], "requiredComponents": [ "impact-verification", "reporting-automation", "audit-trail", "donation-platform" ], "conditionalComponents": [ "smart-contracts", "fund-tracking" ], "crossCategoryDependencies": [ "UC-G-098", "UC-G-098" ], "p2TriggerConditions": { "description": "Activated when P2 shows multi-stakeholder fund flows with high data sharing needs, impact measurement requirements, and donor engagement expectations", "rangeSignals": [ "multiStakeholder >=2", "dataSharing >=3", "impactMeasurement >=3", "donorEngagement >=3" ] }, "contextFieldsTemplate": [ "impact_metrics_defined", "measurement_frequency", "third_party_verification_needed", "number_of_beneficiaries", "geographic_verification_capacity", "baseline_data_availability", "data_privacy_requirements" ], "implementationComplexity": "high", "examples": { "note": "Addresses donor skepticism; requires robust impact definition", "references": [ { "name": "ixo Foundation", "url": "https://www.ixo.world", "solved": "Impact-as-a-token framework where verified impact claims back tokenised donations." }, { "name": "Atlas Network", "url": "https://www.atlasnetwork.org", "solved": "Outcome-based grant verification linking funder reporting to verified intervention outputs." }, { "name": "RootProject", "url": "https://www.rootproject.co", "solved": "Project-level outcome verification tying donor contributions to specific implementation milestones." } ] }, "propertyMapping": {}, "solutionQuestions": [ { "id": "impact-measurement-methodology", "type": "select", "options": [ { "label": "Output metrics (direct deliverables counted)", "value": "output-metrics-direct" }, { "label": "Outcome metrics (beneficiary behavior change)", "value": "outcome-metrics-behavior" }, { "label": "Cost per impact unit ($/life saved, $/QALYs)", "value": "cost-per-impact-unit" }, { "label": "Theory of Change pathway (logical chain)", "value": "theory-of-change-pathway" }, { "label": "Randomized controlled trials (RCT gold standard)", "value": "rct-gold-standard" } ], "propertyMapping": { "output-metrics-direct": { "technologies": [ "impact-verification", "reporting-automation" ], "technologyProperties": { "measurementType": "output-counting", "attribution": "proportional-contribution", "verification": "activity-logs", "complexity": "low" } }, "outcome-metrics-behavior": { "technologies": [ "impact-verification", "audit-trail" ], "technologyProperties": { "measurementType": "outcome-based", "attribution": "causal-inference", "timeframe": "medium-term", "verification": "baseline-endline" } }, "cost-per-impact-unit": { "technologies": [ "reporting-automation", "impact-verification" ], "technologyProperties": { "measurementType": "cost-effectiveness", "unit": "standardized-metric", "benchmark": "evidence-based", "donorTransparency": "comparative" } }, "theory-of-change-pathway": { "technologies": [ "impact-verification", "donation-platform" ], "technologyProperties": { "measurementType": "toc-aligned", "indicators": "multiple-layers", "timeframe": "long-term", "complexity": "high-narrative" } }, "rct-gold-standard": { "technologies": [ "impact-verification", "audit-trail" ], "technologyProperties": { "measurementType": "rct-based", "rigor": "highest", "cost": "high-per-unit", "timeframe": "long-term-multi-year" } } }, "prefillFrom": null, "briefSection": "Impact verification", "text": "What methodology should be used to measure and attribute impact?", "ngoText": "What methodology should be used to measure and attribute impact?" }, { "id": "impact-verification-method", "type": "select", "options": [ { "label": "Self-reported by beneficiaries (lowest cost)", "value": "self-reported-beneficiary" }, { "label": "Field staff verification (direct observation)", "value": "field-staff-observation" }, { "label": "Third-party independent verification", "value": "third-party-independent" }, { "label": "Digitally recorded data (tamper-proof verification)", "value": "blockchain-onchain-data" }, { "label": "Sensor/IoT data (environmental measurement)", "value": "sensor-iot-data" } ], "propertyMapping": { "self-reported-beneficiary": { "technologies": [ "impact-verification", "donation-platform" ], "technologyProperties": { "verificationMethod": "beneficiary-self-report", "bias": "social-desirability-high", "cost": "lowest", "scalability": "highest" } }, "field-staff-observation": { "technologies": [ "impact-verification", "audit-trail" ], "technologyProperties": { "verificationMethod": "in-person-verification", "bias": "moderate", "cost": "moderate-high", "coverage": "limited-by-capacity" } }, "third-party-independent": { "technologies": [ "impact-verification", "reporting-automation" ], "technologyProperties": { "verificationMethod": "independent-audit", "bias": "neutral-external", "cost": "highest", "credibility": "maximum" } }, "blockchain-onchain-data": { "technologies": [ "smart-contracts", "impact-verification" ], "technologyProperties": { "verificationMethod": "distributed-ledger", "immutability": "cryptographic", "realtime": "possible", "techBarrier": "high" } }, "sensor-iot-data": { "technologies": [ "impact-verification", "audit-trail" ], "technologyProperties": { "verificationMethod": "sensor-based", "objectivity": "highest", "infrastructure": "required", "costCurve": "high-initial-low-marginal" } } }, "prefillFrom": null, "briefSection": "Impact verification", "text": "What method would you prefer for verifying impact outcomes?", "ngoText": "What method would you prefer for verifying impact outcomes?" }, { "id": "third-party-verification-involvement", "type": "select", "options": [ { "label": "No third party (organization self-reports)", "value": "no-third-party-self-report" }, { "label": "Advisory role (review and guidance only)", "value": "advisory-guidance-only" }, { "label": "Audit role (independent verification + certification)", "value": "audit-certification" }, { "label": "Collaborative partnership (shared measurement)", "value": "collaborative-partnership" } ], "propertyMapping": { "no-third-party-self-report": { "technologies": [ "impact-verification", "donation-platform" ], "technologyProperties": { "thirdPartyRole": "none", "credibility": "organization-dependent", "cost": "lowest", "donorTrust": "variable" } }, "advisory-guidance-only": { "technologies": [ "impact-verification", "reporting-automation" ], "technologyProperties": { "thirdPartyRole": "advisory", "scope": "methodology-review", "independence": "partial", "cost": "low-moderate" } }, "audit-certification": { "technologies": [ "impact-verification", "audit-trail" ], "technologyProperties": { "thirdPartyRole": "independent-auditor", "scope": "full-verification", "independence": "full", "cost": "high", "credibility": "highest" } }, "collaborative-partnership": { "technologies": [ "impact-verification", "donation-platform" ], "technologyProperties": { "thirdPartyRole": "collaborative-partner", "scope": "joint-measurement", "independence": "none-aligned", "cost": "moderate", "innovation": "high" } } }, "prefillFrom": null, "briefSection": "Impact verification", "text": "What role should third parties play in impact verification?", "ngoText": "What role should third parties play in impact verification?" }, { "id": "impact-data-granularity", "type": "select", "options": [ { "label": "Aggregate program level (donor sees program outcome only)", "value": "aggregate-program-level" }, { "label": "Beneficiary cohort level (my $100 helped X people)", "value": "beneficiary-cohort-level" }, { "label": "Individual beneficiary linkage (donor identifies person)", "value": "individual-beneficiary-link" }, { "label": "Outcome timeline (track beneficiary progress over months)", "value": "outcome-timeline-tracking" } ], "propertyMapping": { "aggregate-program-level": { "technologies": [ "reporting-automation", "impact-verification" ], "technologyProperties": { "granularity": "program-aggregate", "attribution": "probabilistic-share", "privacy": "maximum", "donorSpecificity": "low" } }, "beneficiary-cohort-level": { "technologies": [ "impact-verification", "donation-platform" ], "technologyProperties": { "granularity": "cohort-beneficiary", "attribution": "cost-per-beneficiary", "privacy": "anonymized", "donorConnection": "moderate" } }, "individual-beneficiary-link": { "technologies": [ "impact-verification", "audit-trail" ], "technologyProperties": { "granularity": "individual-beneficiary", "attribution": "one-to-one-direct", "privacy": "reduced-requires-consent", "donorConnection": "maximum" } }, "outcome-timeline-tracking": { "technologies": [ "impact-verification", "reporting-automation" ], "technologyProperties": { "granularity": "temporal-outcome-series", "timeframe": "months-to-years", "engagement": "ongoing-followup", "complexity": "high" } } }, "prefillFrom": null, "briefSection": "Impact verification", "text": "How granular should impact data be linked to individual donations?", "ngoText": "How granular should impact data be linked to individual donations?" }, { "id": "impact-verification-timeline", "type": "select", "options": [ { "label": "Immediate (within 30 days of program delivery)", "value": "immediate-30-days" }, { "label": "Medium-term (3-6 months post-delivery)", "value": "medium-term-3-6-months" }, { "label": "Long-term (12+ months for sustained impact)", "value": "longterm-12-plus-months" }, { "label": "Ongoing real-time monitoring (continuous verification)", "value": "ongoing-realtime-monitoring" } ], "propertyMapping": { "immediate-30-days": { "technologies": [ "impact-verification", "donation-platform" ], "technologyProperties": { "timeframeToVerification": "0-30-days", "immediacy": "high-donor-engagement", "measurementType": "early-output-focused", "donorSatisfaction": "quick-feedback" } }, "medium-term-3-6-months": { "technologies": [ "impact-verification", "reporting-automation" ], "technologyProperties": { "timeframeToVerification": "3-6-months", "immediacy": "moderate", "measurementType": "early-outcome-behavior", "evidenceQuality": "improved" } }, "longterm-12-plus-months": { "technologies": [ "impact-verification", "audit-trail" ], "technologyProperties": { "timeframeToVerification": "12-plus-months", "immediacy": "low-delayed-feedback", "measurementType": "true-outcome-sustained", "evidenceQuality": "highest-rigor" } }, "ongoing-realtime-monitoring": { "technologies": [ "smart-contracts", "impact-verification" ], "technologyProperties": { "timeframeToVerification": "continuous", "dataFrequency": "real-time-streaming", "engagement": "maximum-transparent", "techComplexity": "highest" } } }, "prefillFrom": null, "briefSection": "Reporting automation", "text": "When should impact verification be conducted relative to the donation?", "ngoText": "When should impact verification be conducted relative to the donation?" }, { "id": "beneficiary-choice", "label": "How will beneficiaries exercise choice in how they receive and use this service?", "type": "select", "briefSection": "Donor experience", "options": [ { "label": "Beneficiaries choose between delivery methods (cash, voucher, mobile money, direct)", "value": "delivery-choice" }, { "label": "Beneficiaries choose preferred merchants or service points", "value": "merchant-choice" }, { "label": "Beneficiaries control their own data sharing preferences", "value": "data-choice" }, { "label": "Multiple choice dimensions (delivery + merchant + data)", "value": "full-choice" }, { "label": "Limited choice: programme constraints determine delivery", "value": "limited" } ], "propertyMapping": { "delivery-choice": { "technologies": [], "technologyProperties": { "beneficiaryChoice": "Delivery method choice", "dignityDesign": "Beneficiaries select preferred receipt method" } }, "merchant-choice": { "technologies": [], "technologyProperties": { "beneficiaryChoice": "Merchant/service point choice", "dignityDesign": "Beneficiaries select where to redeem" } }, "data-choice": { "technologies": [], "technologyProperties": { "beneficiaryChoice": "Data sharing choice", "dignityDesign": "Beneficiaries control personal data sharing" } }, "full-choice": { "technologies": [], "technologyProperties": { "beneficiaryChoice": "Multi-dimensional choice", "dignityDesign": "Full beneficiary agency across delivery, merchant, and data" } }, "limited": { "technologies": [], "technologyProperties": { "beneficiaryChoice": "Limited by programme design", "dignityDesign": "Programme constraints; beneficiary informed of reasons" } } }, "text": "How will beneficiaries exercise choice in how they receive and use this service?" } ], "complexityFactors": { "relationships": 3, "operationalChange": 3, "dataCompliance": 2 }, "suggestedCriteria": [ { "id": "SC-IMPACT-ATTRIBUTION", "name": "Donation-to-Impact Attribution Accuracy", "description": "The provider can link a specific donor's contribution to a specific measurable outcome. The core promise is 'your $50 provided clean water for 3 families', not vague aggregate impact. Attribution methodology must be defensible.", "weight": 0.3, "ratingGuide": { "5": "Individual donation-to-outcome traceability with verifiable chain of evidence. Attribution methodology documented and third-party validated. Handles partial attribution for pooled funds proportionally. Blockchain-anchored proof of impact delivery.", "4": "Strong attribution linking donations to specific projects/outcomes. Proportional attribution for pooled funds. Methodology documented. Evidence chain mostly verifiable.", "3": "Project-level attribution (your donation went to this project) but not outcome-level. Pooled fund attribution is approximate. Basic methodology documented.", "2": "Category-level attribution only (your donation went to education programmes). No individual outcome linking. Generic impact statements.", "1": "No attribution capability. Donors receive aggregate organisational impact reports with no connection to their specific contribution." } }, { "id": "SC-VERIFICATION-METHOD", "name": "Impact Verification Methodology & Independence", "description": "This looks at how impact claims are verified, and by whom. Self-reported impact is the status quo that blockchain-verified impact is meant to improve. The verification chain must include independent elements.", "weight": 0.25, "ratingGuide": { "5": "Multi-source verification combining field data (GPS, photos, biometrics), third-party auditors, and beneficiary confirmation. Oracle network or independent data feeds. Verification methodology published and peer-reviewed.", "4": "Third-party verification with field evidence. At least two independent data sources per impact claim. Regular spot-check audits.", "3": "Field staff verification with photo/GPS evidence uploaded to blockchain. Single verification source but with tamper-evident recording.", "2": "Self-reported by implementing partner with basic evidence (photos). No independent verification. Blockchain records the claim but doesn't verify it.", "1": "Purely self-reported impact. No evidence collection infrastructure. Blockchain adds nothing beyond a database entry." } }, { "id": "SC-IMPACT-METRICS", "name": "Impact Metric Framework & Standardisation", "description": "The provider uses or supports recognised impact measurement frameworks. Standardised metrics enable comparison across projects and build donor confidence through familiarity.", "weight": 0.2, "ratingGuide": { "5": "Supports IRIS+, SDG indicators, and custom metrics. Pre-built templates for common impact areas (health, education, WASH, livelihoods). Benchmarking against sector averages. Data exportable in IATI format.", "4": "Supports one major framework (IRIS+ or SDG indicators) plus custom metrics. Templates for 3-5 impact areas. Some benchmarking capability.", "3": "Custom metric definition with basic templating. SDG alignment tags available. No formal benchmarking. Basic export capability.", "2": "Freeform metric entry. No framework alignment. No templates. Metrics inconsistent across projects.", "1": "No structured metric framework. Impact described in narrative text only. No quantitative measurement capability." } }, { "id": "SC-DONOR-STORYTELLING", "name": "Donor-Facing Impact Presentation", "description": "This measures how compellingly the system presents verified impact to donors. Verified data is useless if donors never see it or can't understand it. The presentation must drive donor satisfaction and repeat giving.", "weight": 0.15, "ratingGuide": { "5": "Rich impact stories combining verified data with beneficiary narratives (consent-based). Interactive donor dashboard with maps, timelines, and photo evidence. Shareable impact certificates. Mobile-optimised.", "4": "Donor dashboard with visual impact summaries, maps, and key metrics. Email impact updates with verified data. Shareable summary cards.", "3": "Basic donor dashboard with metric tables and charts. Periodic email reports. PDF impact certificates available.", "2": "Static impact reports emailed to donors. Data presented in tables. No interactive elements. Desktop only.", "1": "No donor-facing impact presentation. Verified data stays in back-end systems. Donors receive generic annual reports." } }, { "id": "SC-PRIVACY-BENEFICIARY", "name": "Beneficiary Privacy & Consent Management", "description": "This looks at how the system protects beneficiary privacy while providing donor transparency. Impact verification requires beneficiary data. The system must balance transparency with protection of vulnerable populations.", "weight": 0.1, "ratingGuide": { "5": "Granular consent management per beneficiary. Data anonymisation with selective disclosure. Privacy-preserving verification (can prove impact without revealing identity). Compliant with GDPR and humanitarian data protection standards.", "4": "Beneficiary consent collected and recorded. Anonymised data used in donor reports. Privacy controls configurable per programme. GDPR-aware design.", "3": "Basic consent process. Aggregated data in donor reports (no individual beneficiary details). Some privacy controls available.", "2": "Generic programme-level consent. Limited anonymisation. Some beneficiary details may be visible in impact reports.", "1": "No consent management. Beneficiary data exposed in transparency reports. No anonymisation. Privacy risk to vulnerable populations." } } ], "procurement": { "marketMaturity": "emerging", "primaryMode": "rfq", "alternativeModes": [ "integrator-led" ], "reasoning": "Impact verification tied to donations is emerging product space.", "exampleProductCategories": [ "impact-attribution-platform", "donor-traceability-saas" ], "partnerChannels": [], "lastReviewed": "2026-05-01" } }, { "id": "UC-F-084", "name": "Automated donor reporting", "category": "F", "subcategory": "Reporting", "description": "Produce donor reports on spending and results directly from your records, so staff spend less time compiling them each quarter.", "bCriteria": [ "B1", "B3", "B7" ], "requiredComponents": [ "reporting-automation", "fund-tracking", "audit-trail" ], "conditionalComponents": [ "smart-contracts", "donation-platform" ], "crossCategoryDependencies": [], "p2TriggerConditions": { "description": "Activated when P2 shows frequent reporting obligations, data quality concerns, and need for automated donor report generation", "rangeSignals": [ "reportingFrequency >=2", "dataQuality >=3", "automationLevel >=3" ] }, "contextFieldsTemplate": [ "reporting_frequency_required", "number_of_reports_per_year", "donor_segment_preferences", "granularity_of_reporting", "existing_reporting_tools", "compliance_report_requirements" ], "implementationComplexity": "low", "examples": { "note": "Immediate benefit; reduces manual reporting burden", "references": [ { "name": "WFP Building Blocks", "url": "https://innovation.wfp.org/project/building-blocks", "solved": "Generated structured donor reports across multi-country cash transfer programmes from on-chain transaction records." }, { "name": "Disberse", "url": "https://disberse.com", "solved": "Automated reporting from fund-flow records to multi-format donor templates." }, { "name": "Sphere Standards alignment", "url": "https://spherestandards.org", "solved": "Reference framework for the reporting categories that automated donor reports must populate." } ] }, "propertyMapping": {}, "solutionQuestions": [ { "id": "report-frequency", "type": "select", "options": [ { "label": "Real-time (immediate after each transaction)", "value": "realtime-per-transaction" }, { "label": "Daily summary reports", "value": "daily-summary" }, { "label": "Monthly consolidated report", "value": "monthly-consolidated" }, { "label": "Annual impact report with year-end tax documentation", "value": "annual-tax-compliant" } ], "propertyMapping": { "realtime-per-transaction": { "technologies": [ "reporting-automation", "donation-platform" ], "technologyProperties": { "frequency": "real-time", "automationLevel": "event-driven", "userExperience": "immediate-feedback", "updateMethod": "push-notification" } }, "daily-summary": { "technologies": [ "reporting-automation", "fund-tracking" ], "technologyProperties": { "frequency": "daily", "batchWindow": "nightly", "aggregation": "per-day", "deliveryMethod": "email-dashboard" } }, "monthly-consolidated": { "technologies": [ "reporting-automation", "audit-trail" ], "technologyProperties": { "frequency": "monthly", "batchWindow": "end-of-month", "aggregation": "full-month", "detailLevel": "summary-plus-details" } }, "annual-tax-compliant": { "technologies": [ "reporting-automation", "donation-platform" ], "technologyProperties": { "frequency": "annual", "taxCompliance": "form-8949-compatible", "detailLevel": "comprehensive", "legalRequirement": "yes" } } }, "prefillFrom": null, "briefSection": "Reporting automation", "text": "How frequently should donor reports be generated and delivered?", "ngoText": "How frequently should donor reports be generated and delivered?" }, { "id": "report-format", "type": "select", "options": [ { "label": "Email summaries (text-based)", "value": "email-text-summary" }, { "label": "Dashboard portal (self-service web view)", "value": "dashboard-portal" }, { "label": "PDF downloadable documents", "value": "pdf-downloadable" }, { "label": "Multi-format (email + dashboard + PDF)", "value": "multi-format-comprehensive" } ], "propertyMapping": { "email-text-summary": { "technologies": [ "reporting-automation", "donation-platform" ], "technologyProperties": { "format": "email-plain-text", "accessibility": "high", "renderingComplexity": "low", "deviceCompatibility": "universal" } }, "dashboard-portal": { "technologies": [ "donation-platform", "reporting-automation" ], "technologyProperties": { "format": "web-dashboard-interactive", "userControl": "on-demand-viewing", "visualization": "interactive-charts", "accessibility": "html5-compatible" } }, "pdf-downloadable": { "technologies": [ "reporting-automation", "audit-trail" ], "technologyProperties": { "format": "pdf-archivable", "recordKeeping": "storage-friendly", "sharing": "email-attachment-ready", "legalValue": "documented" } }, "multi-format-comprehensive": { "technologies": [ "reporting-automation", "donation-platform" ], "technologyProperties": { "format": "multi-channel", "donorChoice": "preferred-format-selection", "complexity": "moderate-integration", "userSatisfaction": "highest" } } }, "prefillFrom": null, "briefSection": "Reporting automation", "text": "What formats should reports be delivered in?", "ngoText": "What formats should reports be delivered in?" }, { "id": "automation-level", "type": "select", "options": [ { "label": "Fully automated (no human intervention)", "value": "fully-automated" }, { "label": "Mostly automated with QA review (spot checks)", "value": "mostly-automated-qa-review" }, { "label": "Semi-automated (template + auto-fill + manual review)", "value": "semi-automated-hybrid" }, { "label": "Donor self-service generation (system + user control)", "value": "self-service-donor-generated" } ], "propertyMapping": { "fully-automated": { "technologies": [ "reporting-automation", "smart-contracts" ], "technologyProperties": { "automationLevel": "end-to-end", "humanReview": "none-required", "errorDetection": "automated-flags", "scalability": "unlimited" } }, "mostly-automated-qa-review": { "technologies": [ "reporting-automation", "audit-trail" ], "technologyProperties": { "automationLevel": "high-90-percent", "humanReview": "sampling-based", "quality": "high-confidence", "cost": "low-operations" } }, "semi-automated-hybrid": { "technologies": [ "reporting-automation", "donation-platform" ], "technologyProperties": { "automationLevel": "moderate-50-percent", "humanReview": "required-per-report", "personalization": "high-manual-touch", "cost": "moderate-operations" } }, "self-service-donor-generated": { "technologies": [ "donation-platform", "reporting-automation" ], "technologyProperties": { "automationLevel": "user-initiated", "donorControl": "full-customization", "frequency": "on-demand", "complexity": "user-must-understand" } } }, "prefillFrom": null, "briefSection": "Reporting automation", "text": "How much of the reporting process should be automated?", "ngoText": "How much of the reporting process should be automated?", "hidden": true }, { "id": "report-personalization", "type": "select", "options": [ { "label": "Generic template (same report for all donors)", "value": "generic-template" }, { "label": "Donation-specific (show only my donations and impact)", "value": "donation-specific-personalized" }, { "label": "Preference-based (donor selects what to see)", "value": "preference-based-choice" }, { "label": "AI-personalized (ML-optimized content per donor)", "value": "ai-personalized-ml" } ], "propertyMapping": { "generic-template": { "technologies": [ "reporting-automation", "donation-platform" ], "technologyProperties": { "personalization": "none-generic", "complexity": "lowest", "production": "fastest", "donorSatisfaction": "moderate" } }, "donation-specific-personalized": { "technologies": [ "reporting-automation", "donation-platform" ], "technologyProperties": { "personalization": "donation-filtered", "relevance": "high", "complexity": "moderate", "engagement": "improved" } }, "preference-based-choice": { "technologies": [ "donation-platform", "reporting-automation" ], "technologyProperties": { "personalization": "donor-controlled-settings", "flexibility": "maximum", "complexity": "moderate", "userControl": "explicit-choice" } }, "ai-personalized-ml": { "technologies": [ "reporting-automation", "smart-contracts" ], "technologyProperties": { "personalization": "ai-ml-based", "optimization": "engagement-maximized", "complexity": "highest-technical", "privacyConsideration": "required" } } }, "prefillFrom": null, "briefSection": "Donor experience", "text": "How personalized should donor reports be?", "ngoText": "How personalized should donor reports be?" }, { "id": "sq-UC-F-089-001", "type": "single-select", "options": [ { "value": "beneficiary-reach", "label": "Beneficiary reach" }, { "value": "cost-per-outcome", "label": "Cost per outcome" }, { "value": "programme-milestones", "label": "Programme milestones" }, { "value": "geographic-coverage", "label": "Geographic coverage" }, { "value": "custom-donor-kpis", "label": "Custom donor KPIs" } ], "propertyMapping": { "beneficiary-reach": { "technologies": [ "reach-calculation", "impact-metrics" ], "technologyProperties": {} }, "cost-per-outcome": { "technologies": [ "cost-analysis", "efficiency-metrics" ], "technologyProperties": {} }, "programme-milestones": { "technologies": [ "milestone-tracking", "progress-reporting" ], "technologyProperties": {} }, "geographic-coverage": { "technologies": [ "geospatial-analysis", "coverage-mapping" ], "technologyProperties": {} }, "custom-donor-kpis": { "technologies": [ "custom-calculation", "donor-dashboard" ], "technologyProperties": {} } }, "briefSection": "requirements", "text": "What impact metrics should be automatically calculated and included in reports?", "ngoText": "What impact metrics should be automatically calculated and included in reports?" } ], "complexityFactors": { "relationships": 1, "operationalChange": 2, "dataCompliance": 1 }, "suggestedCriteria": [ { "id": "SC-REPORT-AUTOMATION", "name": "Report Generation Automation & Scheduling", "description": "This measures how much of the reporting process is automated rather than manual. The entire point of this use case is reducing the hours staff spend compiling donor reports. Full automation with customisable schedules is the goal.", "weight": 0.3, "ratingGuide": { "5": "Fully automated report generation triggered by schedule or event. Customisable templates per donor segment. Auto-distribution via email, portal, and API. Zero manual intervention for standard reports. Exception alerts for anomalies.", "4": "Automated generation with minor manual review step. Configurable schedules. Auto-distribution to most donors. 90%+ automation rate.", "3": "Semi-automated: system generates draft reports, staff reviews and sends. Scheduled generation but manual distribution. 50-70% automation.", "2": "System provides data dashboards but reports must be manually compiled and formatted. Scheduled data exports but manual report assembly.", "1": "No automation. Staff manually query data, compile reports in Word/spreadsheet, and email individually. Current NGO baseline." } }, { "id": "SC-REPORT-CUSTOMISATION", "name": "Report Customisation by Donor Segment", "description": "Different donors can receive different report formats and levels of detail. An institutional donor (USAID, DFID) needs different reporting than an individual donor giving $50/month. One-size-fits-all reporting satisfies nobody.", "weight": 0.25, "ratingGuide": { "5": "Unlimited custom templates by donor segment. Institutional donors get compliance-ready reports (matching their grant reporting requirements). Individual donors get visual impact summaries. Corporate donors get CSR-formatted reports. Each donor can set preferences.", "4": "3-5 report templates covering major segments (institutional, corporate, individual, foundation). Some customisation within templates. Donor preference capture.", "3": "2-3 report templates. Basic segmentation (large vs small donors). Limited customisation options within templates.", "2": "Single report template with minor formatting variations. No donor segmentation. Same report to all donors.", "1": "No templating. Each report is created from scratch or is a generic organisation-wide update." } }, { "id": "SC-DATA-ACCURACY", "name": "Data Accuracy & Real-Time Freshness", "description": "This measures how current and accurate the data in generated reports is. Blockchain-sourced reporting should provide near-real-time data pulled directly from the ledger, not manually reconciled spreadsheet data that's weeks old.", "weight": 0.2, "ratingGuide": { "5": "Real-time data pulled directly from blockchain and integrated systems. Automatic reconciliation. Data freshness guarantee (reports reflect state within minutes). Audit trail showing data source for each figure.", "4": "Near-real-time with data updated daily. Automated reconciliation with minor exceptions handled. Clear data timestamp on reports.", "3": "Data updated weekly. Semi-automated reconciliation. Some manual data entry for non-integrated sources. Data age disclosed.", "2": "Data updated monthly. Significant manual reconciliation required. Mix of automated and manually entered data. Data lag of weeks.", "1": "Data compiled manually from multiple sources. No automated reconciliation. Data may be months old. Accuracy depends entirely on staff diligence." } }, { "id": "SC-COMPLIANCE-REPORTING", "name": "Regulatory & Grant Compliance Report Formats", "description": "The system can generate reports in formats required by major institutional donors and charity regulators. Many NGOs spend significant time reformatting data for each funder's required template.", "weight": 0.15, "ratingGuide": { "5": "Pre-built templates for major institutional donors (USAID, DFID/FCDO, EU, World Bank). Charity Commission / IRS Form 990 compatible outputs. IATI-format export. Custom compliance template builder.", "4": "Templates for 3-5 major donors. One regulatory format supported. IATI export available. Custom template creation possible.", "3": "Templates for 1-2 major donors. Basic regulatory format. CSV/PDF export for manual adaptation to other formats.", "2": "Generic report format. Manual reformatting needed for every institutional donor. No regulatory-specific outputs.", "1": "No structured export. Reports are visual dashboards only \u2014 staff must manually transcribe data into donor-required formats." } }, { "id": "SC-MULTI-CHANNEL", "name": "Multi-Channel Report Delivery", "description": "Reports can be delivered through the channels donors prefer (portal, email, API, mobile push). Different donor segments have different access preferences and the system should accommodate all of them.", "weight": 0.1, "ratingGuide": { "5": "Portal, email, API, mobile app, SMS summary, and webhook integration. Donor selects preferred channels. Delivery confirmation tracking. Accessible formats (PDF, HTML, plain text).", "4": "Portal, email, and API delivery. Donor preference capture. PDF and HTML formats. Basic delivery tracking.", "3": "Email and portal delivery. Single format (PDF). No delivery tracking. No donor preference management.", "2": "Email delivery only with PDF attachment. No portal. No API access. No format options.", "1": "Manual delivery only. Staff emails reports individually or donors must log into a system to download." } } ], "procurement": { "marketMaturity": "mature", "primaryMode": "off-the-shelf", "alternativeModes": [ "rfq" ], "reasoning": "Automated donor reporting is mature SaaS feature.", "exampleProductCategories": [ "donor-reporting-saas", "grants-management-platform" ], "partnerChannels": [], "lastReviewed": "2026-05-01" } }, { "id": "UC-F-085", "name": "Crowdfunding with built-in accountability", "category": "F", "subcategory": "Fundraising Mechanisms", "description": "Run crowdfunding campaigns where money is released as milestones are met, and backers can follow how their gift was used.", "bCriteria": [ "B1", "B3", "B7" ], "requiredComponents": [ "donation-platform", "smart-contracts", "impact-verification", "payment-gateway" ], "conditionalComponents": [ "fund-tracking", "reporting-automation" ], "crossCategoryDependencies": [], "p2TriggerConditions": { "description": "Activated when P2 shows broad donor base with structured campaigns and milestone-based accountability requirements", "rangeSignals": [ "donorBase >=3", "campaignStructure >=2", "milestoneTracking >=2" ] }, "contextFieldsTemplate": [ "campaign_target_amount", "number_of_milestones", "milestone_verification_method", "campaign_duration", "expected_donor_count", "dispute_resolution_process" ], "implementationComplexity": "medium", "examples": { "note": "Combines fundraising with escrow and milestone release", "references": [ { "name": "Gitcoin Grants", "url": "https://www.gitcoin.co/grants", "solved": "Quadratic funding model running open public-goods crowdfunding rounds with on-chain accountability." }, { "name": "Aragon DAOs", "url": "https://aragon.org", "solved": "Smart-contract-governed organisations enabling crowd-funded projects with built-in spending controls." }, { "name": "Akoin Foundation", "url": "https://www.akoin.io", "solved": "African-focused crowdfunding platform linking donations to verified community projects." } ] }, "propertyMapping": {}, "solutionQuestions": [ { "id": "milestone-based-model", "type": "select", "options": [ { "label": "Fixed milestones (50% at design, 50% at delivery)", "value": "fixed-milestone-tranches" }, { "label": "Measurable outcome milestones (verified deliverables)", "value": "measurable-outcome-verified" }, { "label": "Flexible tranches (campaign decides schedule)", "value": "flexible-campaign-defined" } ], "propertyMapping": { "fixed-milestone-tranches": { "technologies": [ "smart-contracts", "donation-platform" ], "technologyProperties": { "milestoneModel": "predefined-fixed", "releaseSchedule": "event-triggered", "flexibility": "low", "predictability": "high" } }, "measurable-outcome-verified": { "technologies": [ "smart-contracts", "impact-verification" ], "technologyProperties": { "milestoneModel": "outcome-driven", "verification": "required-before-release", "flexibility": "moderate", "rigor": "high" } }, "flexible-campaign-defined": { "technologies": [ "smart-contracts", "donation-platform" ], "technologyProperties": { "milestoneModel": "organization-defined", "governance": "campaign-creator-decides", "flexibility": "high", "transparency": "requires-documentation" } } }, "prefillFrom": null, "briefSection": "Smart contract logic", "text": "What milestones do you currently track in your programmes for outcome-based funding?", "ngoText": "What milestones do you currently track in your programmes for outcome-based funding?" }, { "id": "escrow-mechanism", "type": "select", "options": [ { "label": "Full escrow (all funds held until final milestone)", "value": "full-escrow-final" }, { "label": "Milestone escrow (held until each milestone met)", "value": "milestone-escrow-progressive" }, { "label": "No escrow (funds released immediately)", "value": "no-escrow-immediate-release" } ], "propertyMapping": { "full-escrow-final": { "technologies": [ "smart-contracts", "donation-platform" ], "technologyProperties": { "escrowScope": "complete-campaign", "riskProtection": "maximum-donor", "organizationCertainty": "conditional", "complexity": "high" } }, "milestone-escrow-progressive": { "technologies": [ "smart-contracts", "donation-platform" ], "technologyProperties": { "escrowScope": "per-milestone", "riskProtection": "progressive-release", "organizationCertainty": "incremental", "complexity": "moderate" } }, "no-escrow-immediate-release": { "technologies": [ "donation-platform", "audit-trail" ], "technologyProperties": { "escrowScope": "none", "organizationLiquidity": "immediate", "donorRisk": "high", "simplicity": "highest" } } }, "prefillFrom": null, "briefSection": "Infrastructure requirements", "text": "Should funds be held in escrow until milestones are met?", "ngoText": "Should funds be held in escrow until milestones are met?" }, { "id": "dispute-resolution-mechanism", "type": "select", "options": [ { "label": "Campaign creator self-certification (honour system)", "value": "campaign-creator-self-certification-hono" }, { "label": "Community or donor voting on whether milestones were met", "value": "community-or-donor-voting-on-whether-mil" }, { "label": "Third-party independent review and arbitration", "value": "third-party-independent-review-and-arbit" }, { "label": "Automated verification against predefined objective criteria", "value": "automated-verification-against-predefine" }, { "label": "No clear process currently, disputes handled ad hoc", "value": "no-clear-process-currently-disputes-hand" } ], "propertyMapping": { "self-certification-honor": { "technologies": [ "smart-contracts", "donation-platform" ], "technologyProperties": { "disputeResolution": "trust-based", "verification": "self-reported", "fairness": "depends-on-creator", "cost": "lowest" } }, "community-voting-consensus": { "technologies": [ "smart-contracts", "donation-platform" ], "technologyProperties": { "disputeResolution": "decentralized-voting", "mechanism": "donor-governance", "legitimacy": "democratic", "manipulation": "possible" } }, "third-party-arbitration": { "technologies": [ "smart-contracts", "donation-platform" ], "technologyProperties": { "disputeResolution": "independent-arbitrator", "fairness": "neutral-expert", "cost": "moderate-high", "finality": "binding" } }, "oracle-automated-verification": { "technologies": [ "smart-contracts", "impact-verification" ], "technologyProperties": { "disputeResolution": "oracle-based", "automation": "fully-programmable", "subjectivity": "eliminated", "reliability": "depends-on-oracle" } } }, "prefillFrom": null, "briefSection": "Smart contract logic", "text": "How are disputes over milestone achievement currently resolved?", "ngoText": "How are disputes over milestone achievement currently resolved?", "hidden": true, "question": "How are disputes over milestone achievement currently resolved?" }, { "id": "campaign-management-features", "type": "select", "options": [ { "label": "Basic (timeline + progress bar + updates)", "value": "basic-timeline-progress" }, { "label": "Advanced (milestone tracking + budget allocation + reporting)", "value": "advanced-comprehensive" }, { "label": "Premium (analytics + stakeholder notifications + compliance)", "value": "premium-full-featured" } ], "propertyMapping": { "basic-timeline-progress": { "technologies": [ "donation-platform", "reporting-automation" ], "technologyProperties": { "features": "minimal-essential", "manageability": "simple", "functionality": "basic-tracking", "cost": "lowest" } }, "advanced-comprehensive": { "technologies": [ "donation-platform", "fund-tracking" ], "technologyProperties": { "features": "comprehensive-toolkit", "manageability": "detailed-control", "transparency": "granular-visibility", "cost": "moderate" } }, "premium-full-featured": { "technologies": [ "donation-platform", "reporting-automation", "smart-contracts" ], "technologyProperties": { "features": "full-enterprise-suite", "manageability": "professional-grade", "governance": "compliance-ready", "cost": "highest" } } }, "prefillFrom": null, "briefSection": "Donation infrastructure", "text": "What campaign management capabilities should be provided?", "ngoText": "What campaign management capabilities should be provided?", "hidden": true }, { "id": "crowdfund-compliance", "type": "multiselect", "options": [ { "label": "Tax deductibility receipting", "value": "tax" }, { "label": "Anti-money laundering (AML) / Know Your Donor", "value": "aml" }, { "label": "Cross-border fund transfer regulations", "value": "cross-border" }, { "label": "Cryptocurrency-specific regulations", "value": "crypto-reg" }, { "label": "No specific compliance requirements", "value": "none" } ], "propertyMapping": { "tax": { "technologies": [ "Automated receipt generation" ], "technologyProperties": { "complianceModule": "Tax receipting", "regulatoryRisk": "Low" } }, "aml": { "technologies": [ "KYC/AML screening module" ], "technologyProperties": { "complianceModule": "AML screening", "regulatoryRisk": "Medium" } }, "cross-border": { "technologies": [ "Cross-border compliance module" ], "technologyProperties": { "complianceModule": "Transfer regulations", "regulatoryRisk": "High" } }, "crypto-reg": { "technologies": [ "Crypto compliance framework" ], "technologyProperties": { "complianceModule": "Crypto regulations", "regulatoryRisk": "High" } }, "none": { "technologies": [], "technologyProperties": { "complianceModule": "None required", "regulatoryRisk": "Low" } } }, "prefillFrom": null, "briefSection": "Compliance and audit", "text": "What financial compliance requirements apply to crowdfunding?", "ngoText": "What financial compliance requirements apply to crowdfunding?" }, { "id": "sq-UC-F-089-001", "type": "single-select", "options": [ { "value": "full-refund", "label": "Full refund" }, { "value": "partial-allocation", "label": "Partial allocation to cause" }, { "value": "donor-choice-redirect", "label": "Donor choice to redirect" }, { "value": "keep-for-mission", "label": "Keep for mission" }, { "value": "escrow-until-decision", "label": "Escrow until decision" } ], "propertyMapping": { "full-refund": { "technologies": [ "refund-system", "donor-reimbursement" ], "technologyProperties": {} }, "partial-allocation": { "technologies": [ "allocation-engine", "partial-distribution" ], "technologyProperties": {} }, "donor-choice-redirect": { "technologies": [ "choice-system", "redirect-workflow" ], "technologyProperties": {} }, "keep-for-mission": { "technologies": [ "retention-policy", "general-fund" ], "technologyProperties": {} }, "escrow-until-decision": { "technologies": [ "escrow-system", "decision-workflow" ], "technologyProperties": {} } }, "briefSection": "operations", "text": "What happens to funds if a campaign fails to reach its goal?", "ngoText": "What happens to funds if a campaign fails to reach its goal?" }, { "id": "payment-gateway-type", "type": "select", "options": [ { "label": "Crypto-native payment gateway (accept crypto donations directly)", "value": "crypto-native" }, { "label": "Fiat-to-crypto gateway (donors pay in fiat, converted to crypto)", "value": "fiat-to-crypto" }, { "label": "Multi-currency gateway (accept both fiat and crypto)", "value": "multi-currency" }, { "label": "Not sure, need guidance", "value": "guidance-needed" } ], "propertyMapping": { "crypto-native": { "technologies": [ "Crypto payment gateway", "Wallet address generation", "Donation tracking ledger" ], "technologyProperties": { "acceptedCurrencies": "Cryptocurrency only", "donorExperience": "Crypto wallet required", "conversionHandling": "N/A \u2014 stays in crypto" } }, "fiat-to-crypto": { "technologies": [ "Fiat-to-crypto payment gateway", "On-ramp conversion service", "Donation tracking ledger" ], "technologyProperties": { "acceptedCurrencies": "Fiat (converted to crypto)", "donorExperience": "Standard card/bank payment", "conversionHandling": "Automatic conversion at point of donation" } }, "multi-currency": { "technologies": [ "Multi-currency payment gateway", "Currency routing engine", "Donation tracking ledger" ], "technologyProperties": { "acceptedCurrencies": "Fiat + cryptocurrency", "donorExperience": "Choice of payment method", "conversionHandling": "Donor chooses method" } }, "guidance-needed": { "technologies": [ "Payment gateway framework", "Donation tracking ledger" ], "technologyProperties": { "acceptedCurrencies": "To be determined", "donorExperience": "To be determined", "conversionHandling": "To be determined" } } }, "prefillFrom": null, "briefSection": "Payment processing", "text": "What type of payment gateway is needed for donations?", "ngoText": "What type of payment gateway is needed for donations?" }, { "id": "beneficiary-choice", "label": "How will beneficiaries exercise choice in how they receive and use this service?", "type": "select", "briefSection": "Donor experience", "options": [ { "label": "Beneficiaries choose between delivery methods (cash, voucher, mobile money, direct)", "value": "delivery-choice" }, { "label": "Beneficiaries choose preferred merchants or service points", "value": "merchant-choice" }, { "label": "Beneficiaries control their own data sharing preferences", "value": "data-choice" }, { "label": "Multiple choice dimensions (delivery + merchant + data)", "value": "full-choice" }, { "label": "Limited choice: programme constraints determine delivery", "value": "limited" } ], "propertyMapping": { "delivery-choice": { "technologies": [], "technologyProperties": { "beneficiaryChoice": "Delivery method choice", "dignityDesign": "Beneficiaries select preferred receipt method" } }, "merchant-choice": { "technologies": [], "technologyProperties": { "beneficiaryChoice": "Merchant/service point choice", "dignityDesign": "Beneficiaries select where to redeem" } }, "data-choice": { "technologies": [], "technologyProperties": { "beneficiaryChoice": "Data sharing choice", "dignityDesign": "Beneficiaries control personal data sharing" } }, "full-choice": { "technologies": [], "technologyProperties": { "beneficiaryChoice": "Multi-dimensional choice", "dignityDesign": "Full beneficiary agency across delivery, merchant, and data" } }, "limited": { "technologies": [], "technologyProperties": { "beneficiaryChoice": "Limited by programme design", "dignityDesign": "Programme constraints; beneficiary informed of reasons" } } }, "text": "How will beneficiaries exercise choice in how they receive and use this service?" } ], "complexityFactors": { "relationships": 2, "operationalChange": 2, "dataCompliance": 2 }, "suggestedCriteria": [ { "id": "SC-MILESTONE-RELEASE", "name": "Milestone-Based Fund Release Mechanism", "description": "The provider can implement smart contract-based escrow that releases funds only when campaign milestones are verified. This is the core accountability feature. Funds are held until the NGO proves progress.", "weight": 0.3, "ratingGuide": { "5": "Smart contract escrow with configurable milestone conditions. Multiple verification triggers (third-party oracle, multi-sig approval, automated data feed). Partial release capability. Automatic refund if milestones missed. Dispute resolution built in.", "4": "Smart contract escrow with milestone triggers. Manual verification by designated approvers. Partial release supported. Refund mechanism available.", "3": "Basic escrow with time-based or manual release triggers. Milestones tracked but release is semi-manual. Refund process exists but is manual.", "2": "Funds held in escrow but released on NGO request with basic reporting. No smart contract enforcement. Milestone tracking separate from fund release.", "1": "No escrow capability. Funds released to NGO immediately. Milestone tracking is purely informational with no fund control." } }, { "id": "SC-CAMPAIGN-TRANSPARENCY", "name": "Campaign Progress Transparency", "description": "Donors can see real-time campaign progress including funds raised, milestones achieved, and fund disbursement. Public transparency during a campaign builds momentum and trust simultaneously.", "weight": 0.25, "ratingGuide": { "5": "Real-time public dashboard showing funds raised, milestone status, fund release events, and impact updates. Donor activity feed. Social sharing integration. Blockchain verification links for each milestone.", "4": "Public campaign page with near-real-time totals and milestone progress. Fund release events shown. Basic social sharing.", "3": "Campaign page with daily-updated totals and milestone checklist. Fund releases shown with delay. Limited social features.", "2": "Basic campaign page with fundraising total. Milestone updates posted manually by NGO. No real-time elements.", "1": "No public campaign transparency. Donors contribute and receive email updates only if NGO sends them." } }, { "id": "SC-DONOR-PROTECTION", "name": "Donor Protection & Refund Mechanisms", "description": "This covers what happens to donor funds if a campaign fails or milestones aren't met. Crowdfunding with accountability means donors have recourse. This is what distinguishes blockchain-based crowdfunding from traditional.", "weight": 0.2, "ratingGuide": { "5": "Automatic refund to original payment method if campaign target not met or milestones failed. Partial refund for partially completed campaigns. Donor vote mechanism for disputed milestones. Clear terms published before campaign launch.", "4": "Refund mechanism for failed campaigns. Partial refund capability. Dispute process with defined timeline. Terms published.", "3": "Refund for completely failed campaigns (target not reached). Manual process for partial situations. Basic dispute process.", "2": "Refund possible but entirely manual. No automatic triggers. Dispute resolution at NGO's discretion.", "1": "No refund mechanism. All donations are final regardless of campaign outcome. No donor recourse." } }, { "id": "SC-CAMPAIGN-TOOLS", "name": "Campaign Creation & Management Tools", "description": "This measures how easy it is for NGO staff to set up and manage crowdfunding campaigns. If campaign creation requires developer assistance or smart contract knowledge, the NGO can't run campaigns independently.", "weight": 0.15, "ratingGuide": { "5": "No-code campaign builder with drag-and-drop. Milestone definition wizard. Template library for common campaign types. Built-in media upload, storytelling tools. A/B testing for campaign pages.", "4": "Visual campaign builder. Guided milestone setup. Some templates available. Media upload supported. Basic analytics.", "3": "Form-based campaign creation. Manual milestone configuration. Basic page customisation. Image upload. Standard analytics.", "2": "Technical setup required for each campaign. Developer needed for milestone configuration. Limited customisation.", "1": "Fully custom development required for each campaign. No self-service tools. NGO dependent on provider for every campaign." } }, { "id": "SC-PAYMENT-FLEXIBILITY", "name": "Payment Method Flexibility", "description": "Donors can contribute via their preferred payment method (card, mobile money, crypto, bank transfer). Crowdfunding success depends on removing friction for the broadest possible donor base.", "weight": 0.1, "ratingGuide": { "5": "Card, mobile money, bank transfer, crypto, mobile wallets. Regional payment methods supported. One-click recurring pledges. Guest checkout available.", "4": "Card, mobile money, bank transfer, and crypto. 2-3 regional methods. Recurring pledges supported.", "3": "Card and bank transfer. One mobile money provider. Basic crypto acceptance. Manual recurring setup.", "2": "Card payment only. No mobile money. No crypto. No regional methods.", "1": "Bank transfer only. No card processing. Severely limits donor participation." } } ], "procurement": { "marketMaturity": "mature", "primaryMode": "off-the-shelf", "alternativeModes": [ "rfq" ], "reasoning": "Crowdfunding platforms with built-in accountability widely available.", "exampleProductCategories": [ "crowdfunding-platform", "accountability-giving-saas" ], "partnerChannels": [], "lastReviewed": "2026-05-01" } }, { "id": "UC-F-086", "name": "Corporate giving with verified impact metrics", "category": "F", "subcategory": "Corporate Partnerships", "description": "Track corporate gifts against the company's own giving goals, and report the verified results back to each company.", "bCriteria": [ "B1", "B3", "B6" ], "requiredComponents": [ "donation-platform", "impact-verification", "reporting-automation", "audit-trail" ], "conditionalComponents": [ "smart-contracts", "fund-tracking" ], "crossCategoryDependencies": [ "UC-I-114" ], "p2TriggerConditions": { "description": "Activated when P2 shows corporate donor relationships requiring verified impact metrics, regulatory compliance, and regular reporting", "rangeSignals": [ "multiStakeholder >=2", "impactMeasurement >=3", "regulatoryRequired = true", "reportingFrequency >=2" ] }, "contextFieldsTemplate": [ "number_of_corporate_partners", "average_donation_size", "csr_reporting_standards", "third_party_audit_frequency", "impact_metric_granularity", "sustainability_goals_alignment" ], "implementationComplexity": "high", "examples": { "note": "Aligns with SDG reporting and ESG frameworks", "references": [ { "name": "Benevity", "url": "https://benevity.com", "solved": "Corporate-giving platform serving Fortune 500 employee-giving and matching programmes; explored blockchain integrations for impact verification." }, { "name": "Salesforce.org Philanthropy Cloud", "url": "https://www.salesforce.org", "solved": "Corporate philanthropy infrastructure with auditable giving records and verified impact reporting." }, { "name": "Microsoft Philanthropies", "url": "https://www.microsoft.com/en-us/corporate-responsibility/philanthropies", "solved": "Reference example of corporate giving with structured impact metrics and reporting." } ] }, "propertyMapping": {}, "solutionQuestions": [ { "id": "csr-standards-alignment", "type": "select", "options": [ { "label": "UN SDGs (17 Sustainable Development Goals)", "value": "un-sdgs-alignment" }, { "label": "SASB (Sustainability Accounting Standards Board)", "value": "sasb-standards" }, { "label": "GRI Standards (Global Reporting Initiative)", "value": "gri-standards" }, { "label": "Custom corporate framework (company-specific priorities)", "value": "custom-corporate-framework" }, { "label": "Multi-standard compliance (SDGs + SASB + GRI)", "value": "multi-standard-compliance" } ], "propertyMapping": { "un-sdgs-alignment": { "technologies": [ "donation-platform", "reporting-automation" ], "technologyProperties": { "standard": "un-sdgs-17goals", "framework": "international-consensus", "alignment": "goal-based-mapping", "recognition": "global" } }, "sasb-standards": { "technologies": [ "reporting-automation", "audit-trail" ], "technologyProperties": { "standard": "sasb-materiality-based", "framework": "investor-focused", "alignment": "industry-specific", "recognition": "institutional-investors" } }, "gri-standards": { "technologies": [ "reporting-automation", "impact-verification" ], "technologyProperties": { "standard": "gri-comprehensive", "framework": "stakeholder-inclusive", "alignment": "impact-reporting", "recognition": "corporate-sustainability" } }, "custom-corporate-framework": { "technologies": [ "donation-platform", "smart-contracts" ], "technologyProperties": { "standard": "proprietary-company", "flexibility": "maximum", "alignment": "company-values", "uniqueness": "tailored" } }, "multi-standard-compliance": { "technologies": [ "reporting-automation", "impact-verification" ], "technologyProperties": { "standard": "integrated-frameworks", "flexibility": "adaptable", "complexity": "highest", "scope": "comprehensive-coverage" } } }, "prefillFrom": null, "briefSection": "Compliance and audit", "text": "Which CSR/ESG standards should donations align with?", "ngoText": "Which CSR/ESG standards should donations align with?", "hidden": true }, { "id": "esg-alignment-verification", "type": "select", "options": [ { "label": "Self-assessment by organization", "value": "self-assessment-org" }, { "label": "Corporate due diligence (company reviews NGO)", "value": "corporate-due-diligence" }, { "label": "Third-party ESG audit certification", "value": "third-party-esg-audit" }, { "label": "Digitally recorded compliance (automated, tamper-proof records)", "value": "blockchain-compliance-proof" } ], "propertyMapping": { "self-assessment-org": { "technologies": [ "donation-platform", "reporting-automation" ], "technologyProperties": { "verificationMethod": "self-reported", "rigor": "low", "cost": "lowest", "credibility": "corporate-dependent" } }, "corporate-due-diligence": { "technologies": [ "impact-verification", "audit-trail" ], "technologyProperties": { "verificationMethod": "corporate-verified", "rigor": "moderate", "cost": "moderate", "alignment": "corporate-requirements" } }, "third-party-esg-audit": { "technologies": [ "impact-verification", "reporting-automation" ], "technologyProperties": { "verificationMethod": "independent-esg-auditor", "rigor": "high", "cost": "high", "credibility": "institutional" } }, "blockchain-compliance-proof": { "technologies": [ "smart-contracts", "audit-trail" ], "technologyProperties": { "verificationMethod": "on-chain-immutable", "transparency": "cryptographically-proven", "cost": "moderate", "innovation": "cutting-edge" } } }, "prefillFrom": null, "briefSection": "Impact verification", "text": "How do you currently verify ESG alignment in your programmes?", "ngoText": "How do you currently verify ESG alignment in your programmes?", "hidden": true }, { "id": "impact-granularity-corporate", "type": "select", "options": [ { "label": "High-level summary (total contribution + 1 headline outcome)", "value": "highlevel-summary-1outcome" }, { "label": "Detailed program impact (contributions + multiple outcomes)", "value": "detailed-program-impact" }, { "label": "Beneficiary-level detail (individual stories + metrics)", "value": "beneficiary-level-detail" }, { "label": "Real-time dashboard (live tracking of all contributions)", "value": "realtime-live-dashboard" } ], "propertyMapping": { "highlevel-summary-1outcome": { "technologies": [ "reporting-automation", "donation-platform" ], "technologyProperties": { "granularity": "executive-summary", "complexity": "low-reading", "timeRequired": "minimal", "targetAudience": "c-suite" } }, "detailed-program-impact": { "technologies": [ "reporting-automation", "impact-verification" ], "technologyProperties": { "granularity": "program-detailed", "metrics": "multiple-outcomes", "depth": "comprehensive", "targetAudience": "csr-team" } }, "beneficiary-level-detail": { "technologies": [ "impact-verification", "audit-trail" ], "technologyProperties": { "granularity": "individual-beneficiary", "storytelling": "human-centered", "emotionalEngagement": "high", "complexity": "high-detailed" } }, "realtime-live-dashboard": { "technologies": [ "reporting-automation", "smart-contracts" ], "technologyProperties": { "granularity": "continuous-realtime", "updateFrequency": "live-streaming", "engagement": "maximum-interactive", "technology": "advanced-integration" } } }, "prefillFrom": null, "briefSection": "Impact verification", "text": "How granular should impact reporting be for corporate donors?", "ngoText": "How granular should impact reporting be for corporate donors?" }, { "id": "audit-reporting-requirements", "type": "select", "options": [ { "label": "Annual financial audit (standard nonprofit requirement)", "value": "annual-financial-audit" }, { "label": "Enhanced impact audit (financial + impact verification)", "value": "enhanced-impact-audit" }, { "label": "Continuous compliance monitoring (quarterly checks)", "value": "continuous-quarterly-monitoring" }, { "label": "Real-time digital audit trail (permanent tamper-proof record)", "value": "realtime-blockchain-audit" } ], "propertyMapping": { "annual-financial-audit": { "technologies": [ "audit-trail", "reporting-automation" ], "technologyProperties": { "auditFrequency": "annual", "scope": "financial-statements", "requirement": "legal-compliance", "assurance": "moderate" } }, "enhanced-impact-audit": { "technologies": [ "impact-verification", "audit-trail" ], "technologyProperties": { "auditFrequency": "annual", "scope": "financial-plus-impact", "rigor": "high-assurance", "cost": "moderate-high" } }, "continuous-quarterly-monitoring": { "technologies": [ "audit-trail", "reporting-automation" ], "technologyProperties": { "auditFrequency": "quarterly", "scope": "rolling-compliance", "proactiveness": "preventive", "cost": "high-ongoing" } }, "realtime-blockchain-audit": { "technologies": [ "smart-contracts", "audit-trail" ], "technologyProperties": { "auditFrequency": "continuous-real-time", "transparency": "cryptographic-proof", "trustLess": "verification-automated", "innovation": "distributed-ledger" } } }, "prefillFrom": null, "briefSection": "Compliance and audit", "text": "What audit and reporting requirements should be met?", "ngoText": "What audit and reporting requirements should be met?" }, { "id": "corporate-reporting-channels", "type": "select", "options": [ { "label": "Annual impact report (printed + PDF)", "value": "annual-report-print-pdf" }, { "label": "Interactive web dashboard (real-time metrics)", "value": "interactive-dashboard-realtime" }, { "label": "ESG report integration (embedded in corporate ESG reporting)", "value": "esg-report-integration" }, { "label": "Multi-channel (annual + dashboard + custom reports)", "value": "multichannel-comprehensive" } ], "propertyMapping": { "annual-report-print-pdf": { "technologies": [ "reporting-automation", "donation-platform" ], "technologyProperties": { "deliveryChannel": "print-digital-annual", "frequency": "annual", "format": "comprehensive-bound", "readership": "executive-board" } }, "interactive-dashboard-realtime": { "technologies": [ "reporting-automation", "smart-contracts" ], "technologyProperties": { "deliveryChannel": "web-portal-interactive", "frequency": "continuous", "accessibility": "corporate-portal", "engagement": "self-serve-analytics" } }, "esg-report-integration": { "technologies": [ "reporting-automation", "impact-verification" ], "technologyProperties": { "deliveryChannel": "corporate-esg-framework", "integration": "aligned-corporate-narrative", "scope": "multi-program-aggregated", "audience": "investors-stakeholders" } }, "multichannel-comprehensive": { "technologies": [ "reporting-automation", "donation-platform", "smart-contracts" ], "technologyProperties": { "deliveryChannel": "omnichannel", "flexibility": "on-demand-customizable", "audience": "all-stakeholder-types", "satisfaction": "maximum" } } }, "prefillFrom": null, "briefSection": "Reporting automation", "text": "What reporting channels do your corporate donors require for ESG?", "ngoText": "What reporting channels do your corporate donors require for ESG?" } ], "complexityFactors": { "relationships": 3, "operationalChange": 2, "dataCompliance": 2 }, "suggestedCriteria": [ { "id": "SC-CSR-ALIGNMENT", "name": "CSR/ESG Framework Alignment & Reporting", "description": "The provider can generate reports that align with corporate CSR and ESG reporting frameworks. Corporate donors need impact data formatted for their sustainability reports: GRI, SASB, SDG, CDP. If the NGO can't feed their reporting pipeline, the partnership stalls.", "weight": 0.3, "ratingGuide": { "5": "Pre-built outputs for GRI, SASB, CDP, and UN Global Compact. SDG indicator mapping with verified metrics. Corporate sustainability report data feeds via API. Custom framework template builder. ESG audit support.", "4": "Supports 2-3 major frameworks (GRI, SDG, one other). API data export for corporate systems. SDG mapping for all tracked metrics.", "3": "SDG alignment reporting. One additional framework supported. PDF/CSV export for manual integration into corporate reports.", "2": "Basic impact reports with SDG tags. No framework-specific formatting. Corporate team must reformat data manually.", "1": "Generic impact reports with no framework alignment. Corporate partner cannot use data in CSR/ESG reporting without significant manual rework." } }, { "id": "SC-VERIFIED-IMPACT", "name": "Third-Party Verified Impact Metrics", "description": "The system supports independent verification of impact claims that corporate partners can reference in their reporting. Corporate donors face reputational risk from unverified impact claims. 'greenwashing' accusations can damage both the corporate and the NGO.", "weight": 0.25, "ratingGuide": { "5": "Independent third-party verification integrated into platform. Audit-ready evidence chains. Blockchain-anchored verification timestamps. Corporate partner can directly access verification records. Accredited verifiers available.", "4": "Third-party verification available for key metrics. Evidence documentation maintained. Verification records accessible to corporate partners.", "3": "Self-verification with documented methodology. Third-party audit possible but not integrated. Basic evidence trail.", "2": "Self-reported metrics with basic documentation. No third-party verification infrastructure. Corporate partner must commission own verification.", "1": "Unverified self-reported impact. No evidence chain. Corporate partner cannot defensibly cite metrics." } }, { "id": "SC-CORPORATE-PORTAL", "name": "Corporate Partner Portal & Dashboard", "description": "The provider offers a dedicated portal where corporate partners can track their giving portfolio, access reports, and manage their CSR programme. Corporate giving is managed by teams with dashboards, not individual donors checking email.", "weight": 0.2, "ratingGuide": { "5": "Dedicated corporate portal with portfolio view across all supported NGOs/projects. Real-time impact dashboard. Team access with role-based permissions. Budget tracking against CSR commitments. Board-ready presentation exports.", "4": "Corporate dashboard with project-level views. Multi-user access. Budget tracking. Quarterly report auto-generation.", "3": "Basic partner login with contribution history and impact summaries. Single user access. Manual report requests.", "2": "Same donor interface as individuals. No corporate-specific features. No portfolio view.", "1": "No portal. Corporate partner receives email reports only. No self-service access to data." } }, { "id": "SC-GRANT-MANAGEMENT", "name": "Multi-Year Grant & Pledge Management", "description": "The system can handle multi-year corporate commitments with phased disbursements, matching conditions, and milestone-linked payments. Corporate giving is structured differently from individual donations. It involves pledges, tranches, and conditions.", "weight": 0.15, "ratingGuide": { "5": "Multi-year pledge management with scheduled disbursements. Conditional release based on milestones or matching triggers. Automated reminders for upcoming tranches. Historical pledge tracking and forecasting.", "4": "Multi-year tracking with manual disbursement scheduling. Basic conditional release. Reminder system. Pledge history maintained.", "3": "Annual pledge tracking. Manual tranche processing. Basic reminders. Pledge history available.", "2": "Single donation tracking only. Multi-year commitments tracked in external spreadsheet. No tranche management.", "1": "No pledge management. Each corporate donation treated as one-off. No multi-year tracking capability." } }, { "id": "SC-EMPLOYEE-GIVING", "name": "Employee Giving & Payroll Integration", "description": "The platform supports employee giving programmes where corporate staff donate (often with employer matching) through payroll deduction. Many corporate partnerships include employee engagement components.", "weight": 0.1, "ratingGuide": { "5": "Payroll deduction integration with major HRIS/payroll systems. Employee giving portal with project selection. Employer matching automation. Individual tax receipts per employee. Campaign gamification features.", "4": "API-based payroll integration. Employee portal with basic project selection. Matching tracked automatically. Individual receipts.", "3": "Batch upload of payroll deductions. Basic employee interface. Matching tracked manually. Aggregate receipts per pay period.", "2": "Employee donations processed individually (no payroll integration). Matching tracked in spreadsheet. Generic receipts.", "1": "No employee giving features. All corporate donations processed as single organisational gifts." } } ], "procurement": { "marketMaturity": "emerging", "primaryMode": "rfq", "alternativeModes": [ "integrator-led" ], "reasoning": "Corporate giving impact verification is growing area.", "exampleProductCategories": [ "corporate-giving-platform", "csr-impact-saas" ], "partnerChannels": [], "lastReviewed": "2026-05-01" } }, { "id": "UC-F-087", "name": "Recurring donation automation", "category": "F", "subcategory": "Donation Mechanisms", "description": "Collect regular donations automatically and keep a running total for each donor, applying your screening rules to every gift.", "bCriteria": [ "B7", "B1" ], "requiredComponents": [ "smart-contracts", "donation-platform", "payment-gateway" ], "conditionalComponents": [ "reporting-automation", "fund-tracking" ], "crossCategoryDependencies": [], "p2TriggerConditions": { "description": "Activated when P2 shows high automation needs for recurring donations and donor retention challenges", "rangeSignals": [ "automationLevel >=3", "donorRetention >=2" ] }, "contextFieldsTemplate": [ "recurring_donation_frequency", "expected_recurring_donor_percentage", "average_recurring_amount", "churn_rate_baseline", "payment_method_diversity" ], "implementationComplexity": "low", "examples": { "note": "Standard fintech pattern; improves donor retention", "references": [ { "name": "Endaoment", "url": "https://endaoment.org", "solved": "Recurring crypto donation infrastructure with smart-contract-managed scheduling." }, { "name": "The Giving Block", "url": "https://thegivingblock.com", "solved": "Recurring crypto donation rails for 2,000+ nonprofits with automated tax-receipt issuance." } ] }, "propertyMapping": {}, "solutionQuestions": [ { "id": "payment-scheduling", "type": "select", "options": [ { "label": "Fixed monthly amounts (monthly recurring)", "value": "monthly-fixed-amount" }, { "label": "Flexible frequency (weekly/bi-weekly/monthly/quarterly)", "value": "flexible-frequency-choice" }, { "label": "Variable amounts (fixed schedule, donor can adjust)", "value": "variable-amount-adjustable" }, { "label": "Smart scheduling (AI-optimized gift timing)", "value": "smart-ai-optimized-timing" } ], "propertyMapping": { "monthly-fixed-amount": { "technologies": [ "smart-contracts", "payment-gateway" ], "technologyProperties": { "frequency": "monthly", "amount": "fixed-donor-defined", "predictability": "high-for-budgeting", "simplicity": "standard-subscription" } }, "flexible-frequency-choice": { "technologies": [ "smart-contracts", "donation-platform" ], "technologyProperties": { "frequency": "donor-configurable", "options": "multiple-intervals", "flexibility": "high", "processing": "batch-optimized" } }, "variable-amount-adjustable": { "technologies": [ "donation-platform", "payment-gateway" ], "technologyProperties": { "frequency": "scheduled-regular", "amount": "donor-changeable", "flexibility": "high-amount", "administration": "simple-override" } }, "smart-ai-optimized-timing": { "technologies": [ "smart-contracts", "donation-platform" ], "technologyProperties": { "frequency": "algorithmically-optimized", "optimization": "ml-based-timing", "personalization": "ai-driven", "ethics": "donor-consent-required" } } }, "prefillFrom": null, "briefSection": "Infrastructure requirements", "text": "What payment scheduling options should be offered?", "ngoText": "What payment scheduling options should be offered?" }, { "id": "donor-management-features", "type": "select", "options": [ { "label": "Basic (pause/resume/cancel)", "value": "basic-pause-resume-cancel" }, { "label": "Advanced (pause/resume/change amount/change frequency)", "value": "advanced-full-control" }, { "label": "Premium (all + scheduled changes + seasonal adjustments)", "value": "premium-scheduling-advanced" } ], "propertyMapping": { "basic-pause-resume-cancel": { "technologies": [ "donation-platform", "payment-gateway" ], "technologyProperties": { "features": "essential-controls", "complexity": "low", "donorControl": "basic-lifecycle", "operationalBurden": "minimal" } }, "advanced-full-control": { "technologies": [ "smart-contracts", "donation-platform" ], "technologyProperties": { "features": "comprehensive-management", "flexibility": "high-donor-empowerment", "complexity": "moderate", "donorSatisfaction": "high" } }, "premium-scheduling-advanced": { "technologies": [ "smart-contracts", "donation-platform" ], "technologyProperties": { "features": "enterprise-automation", "scheduling": "complex-rules-engine", "sophistication": "high", "cost": "moderate-platform" } } }, "prefillFrom": null, "briefSection": "Donor experience", "text": "What donor management capabilities do you currently have?", "ngoText": "What donor management capabilities do you currently have?" }, { "id": "retention-engagement-features", "type": "select", "options": [ { "label": "Milestone notifications (donor sees impact of their giving)", "value": "milestone-impact-notifications" }, { "label": "Incentive rewards (matching, tiers, badges)", "value": "incentive-rewards-gamified" }, { "label": "Personalized engagement (content + timing tailored to donor)", "value": "personalized-engagement" }, { "label": "Community features (connect with other donors)", "value": "community-donor-network" } ], "propertyMapping": { "milestone-impact-notifications": { "technologies": [ "donation-platform", "reporting-automation" ], "technologyProperties": { "feature": "impact-awareness-notifications", "frequency": "event-driven", "engagement": "emotional-connection", "retention": "improves-loyalty" } }, "incentive-rewards-gamified": { "technologies": [ "smart-contracts", "donation-platform" ], "technologyProperties": { "feature": "gamification-incentives", "mechanics": "points-badges-tiers", "engagement": "game-like-motivation", "psychology": "behavior-modification" } }, "personalized-engagement": { "technologies": [ "donation-platform", "reporting-automation" ], "technologyProperties": { "feature": "ai-personalized-outreach", "customization": "donor-specific-content", "timing": "optimal-engagement-windows", "privacy": "requires-consent" } }, "community-donor-network": { "technologies": [ "donation-platform", "smart-contracts" ], "technologyProperties": { "feature": "social-community-building", "connection": "peer-to-peer-engagement", "virality": "network-effects", "moderation": "community-management-required" } } }, "prefillFrom": null, "briefSection": "Donor experience", "text": "What features support donor retention and engagement?", "ngoText": "What features support donor retention and engagement?" }, { "id": "recurring-compliance", "type": "multiselect", "options": [ { "label": "Tax deductibility receipting", "value": "tax" }, { "label": "Anti-money laundering (AML) / Know Your Donor", "value": "aml" }, { "label": "Cross-border fund transfer regulations", "value": "cross-border" }, { "label": "Cryptocurrency-specific regulations", "value": "crypto-reg" }, { "label": "No specific compliance requirements", "value": "none" } ], "propertyMapping": { "tax": { "technologies": [ "Automated receipt generation" ], "technologyProperties": { "complianceModule": "Tax receipting", "regulatoryRisk": "Low" } }, "aml": { "technologies": [ "KYC/AML screening module" ], "technologyProperties": { "complianceModule": "AML screening", "regulatoryRisk": "Medium" } }, "cross-border": { "technologies": [ "Cross-border compliance module" ], "technologyProperties": { "complianceModule": "Transfer regulations", "regulatoryRisk": "High" } }, "crypto-reg": { "technologies": [ "Crypto compliance framework" ], "technologyProperties": { "complianceModule": "Crypto regulations", "regulatoryRisk": "High" } }, "none": { "technologies": [], "technologyProperties": { "complianceModule": "None required", "regulatoryRisk": "Low" } } }, "prefillFrom": null, "briefSection": "Compliance and audit", "text": "What financial compliance requirements apply to recurring donations?", "ngoText": "What financial compliance requirements apply to recurring donations?" }, { "id": "sq-UC-F-089-003", "type": "single-select", "options": [ { "value": "monthly-impact-update", "label": "Monthly impact update" }, { "value": "annual-summary", "label": "Annual summary" }, { "value": "milestone-notifications", "label": "Milestone notifications" }, { "value": "minimal-receipt-only", "label": "Minimal receipt only" }, { "value": "personalised-story", "label": "Personalised story" } ], "propertyMapping": { "monthly-impact-update": { "technologies": [ "monthly-report", "automated-narrative" ], "technologyProperties": {} }, "annual-summary": { "technologies": [ "annual-reporting", "annual-schedule" ], "technologyProperties": {} }, "milestone-notifications": { "technologies": [ "milestone-alerts", "event-triggers" ], "technologyProperties": {} }, "minimal-receipt-only": { "technologies": [ "receipt-system", "basic-notification" ], "technologyProperties": {} }, "personalised-story": { "technologies": [ "story-system", "personalization-engine" ], "technologyProperties": {} } }, "briefSection": "user-experience", "text": "What donor communication should be triggered by recurring donation events?", "ngoText": "What donor communication should be triggered by recurring donation events?" }, { "id": "beneficiary-choice", "label": "How will beneficiaries exercise choice in how they receive and use this service?", "type": "select", "briefSection": "Donor experience", "options": [ { "label": "Beneficiaries choose between delivery methods (cash, voucher, mobile money, direct)", "value": "delivery-choice" }, { "label": "Beneficiaries choose preferred merchants or service points", "value": "merchant-choice" }, { "label": "Beneficiaries control their own data sharing preferences", "value": "data-choice" }, { "label": "Multiple choice dimensions (delivery + merchant + data)", "value": "full-choice" }, { "label": "Limited choice: programme constraints determine delivery", "value": "limited" } ], "propertyMapping": { "delivery-choice": { "technologies": [], "technologyProperties": { "beneficiaryChoice": "Delivery method choice", "dignityDesign": "Beneficiaries select preferred receipt method" } }, "merchant-choice": { "technologies": [], "technologyProperties": { "beneficiaryChoice": "Merchant/service point choice", "dignityDesign": "Beneficiaries select where to redeem" } }, "data-choice": { "technologies": [], "technologyProperties": { "beneficiaryChoice": "Data sharing choice", "dignityDesign": "Beneficiaries control personal data sharing" } }, "full-choice": { "technologies": [], "technologyProperties": { "beneficiaryChoice": "Multi-dimensional choice", "dignityDesign": "Full beneficiary agency across delivery, merchant, and data" } }, "limited": { "technologies": [], "technologyProperties": { "beneficiaryChoice": "Limited by programme design", "dignityDesign": "Programme constraints; beneficiary informed of reasons" } } }, "text": "How will beneficiaries exercise choice in how they receive and use this service?" } ], "complexityFactors": { "relationships": 1, "operationalChange": 1, "dataCompliance": 2 }, "suggestedCriteria": [ { "id": "SC-RECURRING-RELIABILITY", "name": "Payment Processing Reliability & Recovery", "description": "This measures how reliably the system processes recurring payments and how it handles failures. Failed recurring charges are the #1 cause of donor churn in subscription giving. Smart retry logic and payment method updating are essential.", "weight": 0.3, "ratingGuide": { "5": "99.9%+ payment success rate. Intelligent retry logic (varies timing and amount). Automatic card updater for expired cards. Donor-friendly failure notifications with one-click update. Multiple fallback payment methods. Churn prediction alerts.", "4": "99%+ success rate. Retry logic with 2-3 attempts. Card updater integration. Email notifications on failure. Fallback payment option.", "3": "98%+ success rate. Basic retry (same time, 3 attempts). Manual card update process. Email notification on final failure.", "2": "95%+ success rate. Single retry attempt. No card updater. Donor must manually re-subscribe after failure.", "1": "No retry logic. Failed payment cancels subscription immediately. No notification. High involuntary churn." } }, { "id": "SC-DONOR-FLEXIBILITY", "name": "Donor Self-Service & Flexibility", "description": "Donors can easily modify their recurring gifts (change amount, frequency, pause, resume, or redirect to different projects). Donor control reduces cancellations because donors adjust rather than quit.", "weight": 0.25, "ratingGuide": { "5": "Full self-service portal: change amount, frequency, payment method, project allocation. Pause/resume without cancellation. Gift redirection between projects. Annual giving commitment option. Mobile-friendly.", "4": "Self-service for amount, frequency, and payment method changes. Pause/resume available. Project change possible. Web-based portal.", "3": "Self-service for basic changes (amount, payment method). Pause requires contacting NGO. Limited project flexibility.", "2": "Donors must contact NGO for any changes. Email-based modification process. 2-3 day processing time.", "1": "No modification capability. Donor must cancel and re-subscribe for any change. No self-service." } }, { "id": "SC-ENGAGEMENT-RETENTION", "name": "Donor Engagement & Retention Features", "description": "The platform includes features that maintain recurring donor engagement and reduce voluntary churn. Automated giving becomes invisible giving. The system needs to keep donors connected to their impact to prevent cancellation.", "weight": 0.2, "ratingGuide": { "5": "Personalised impact updates tied to recurring gift milestones. Anniversary and total-giving celebrations. Donor upgrade suggestions based on giving patterns. Community features connecting recurring givers. Churn risk scoring with automated intervention.", "4": "Regular impact updates personalised to donor's supported projects. Milestone acknowledgments. Basic upgrade prompts. Engagement analytics.", "3": "Periodic generic impact updates. Annual giving summary. No personalisation. Basic retention reporting.", "2": "Monthly receipt emails only. No impact connection. No engagement features. Standard churn reporting.", "1": "Transaction confirmation only. No ongoing engagement. No retention features. Donor forgotten after signup." } }, { "id": "SC-TRANSPARENCY-RECURRING", "name": "Recurring Gift Transparency & Tracking", "description": "Recurring donors can see a cumulative view of their giving history and ongoing impact. Blockchain-based tracking should show donors the compound effect of their sustained giving over time.", "weight": 0.15, "ratingGuide": { "5": "Cumulative giving dashboard showing total contributed, projects funded, and cumulative impact metrics. Blockchain-verified giving history. Year-over-year comparison. Shareable giving profile.", "4": "Giving history with running totals and impact summaries. Verified transaction history. Annual summaries.", "3": "Transaction history with totals. Basic impact summary per year. Standard giving receipts.", "2": "List of past transactions. No cumulative impact view. Individual receipts only.", "1": "No giving history. Donor has no visibility into past recurring donations or cumulative impact." } }, { "id": "SC-PAYMENT-METHODS", "name": "Payment Method Diversity", "description": "The platform supports the payment methods donors prefer for recurring giving. Direct debit, card-on-file, mobile money, and crypto subscriptions each serve different donor segments.", "weight": 0.1, "ratingGuide": { "5": "Direct debit (ACH/SEPA/BECS), card-on-file, mobile money recurring, crypto recurring (token streaming), mobile wallet recurring. 5+ methods across regions.", "4": "Direct debit, card-on-file, mobile money. 3-4 methods. Covers major donor markets.", "3": "Card-on-file and direct debit. 2 methods. Adequate for most Western donors.", "2": "Card-on-file only. Single method. Limits donor base in regions where card penetration is low.", "1": "Manual bank transfer only. No automated recurring payment capability." } } ], "procurement": { "marketMaturity": "mature", "primaryMode": "off-the-shelf", "alternativeModes": [ "rfq" ], "reasoning": "Recurring donation automation is core feature in giving SaaS.", "exampleProductCategories": [ "donation-automation-platform", "recurring-giving-saas" ], "partnerChannels": [], "lastReviewed": "2026-05-01" } }, { "id": "UC-F-088", "name": "Donor-advised fund integration", "category": "F", "subcategory": "Fundraising Mechanisms", "description": "Receive gifts that come through donor-advised funds, and show the fund sponsor and the donor how the money was used.", "bCriteria": [ "B1", "B3", "B4" ], "requiredComponents": [ "donation-platform", "fund-tracking", "audit-trail", "reporting-automation" ], "conditionalComponents": [ "smart-contracts" ], "crossCategoryDependencies": [], "p2TriggerConditions": { "description": "Activated when P2 shows high-net-worth donor relationships with advisory needs and complex fund allocation requirements", "rangeSignals": [ "highNetWorthDonors >=2", "advisoryCapability >=2", "fundAllocation >=3" ] }, "contextFieldsTemplate": [ "daf_platform_partners", "average_daf_grant_size", "number_of_daf_relationships", "regulatory_jurisdiction", "tax_reporting_requirements", "grant_timing_requirements" ], "implementationComplexity": "medium", "examples": { "note": "Requires interoperability with established DAF platforms", "references": [ { "name": "Endaoment", "url": "https://endaoment.org", "solved": "First fully on-chain donor-advised fund (DAF) infrastructure with smart-contract-managed grants to verified non-profits." }, { "name": "Fidelity Charitable", "url": "https://www.fidelitycharitable.org", "solved": "Largest US donor-advised fund operator; reference for the DAF model that blockchain implementations replicate." } ] }, "propertyMapping": {}, "solutionQuestions": [ { "id": "daf-platform-integration", "type": "select", "options": [ { "label": "API integration (real-time grant recommendations)", "value": "api-realtime-integration" }, { "label": "Manual grant requests (DAF sponsor approval workflow)", "value": "manual-grant-workflow" }, { "label": "Pre-approved grants (qualified NGO in DAF donor networks)", "value": "preapproved-qualified-ngo" }, { "label": "Multi-DAF aggregator (integrated with multiple sponsors)", "value": "multi-daf-aggregator" } ], "propertyMapping": { "api-realtime-integration": { "technologies": [ "donation-platform", "smart-contracts" ], "technologyProperties": { "integrationMethod": "api-automated", "timing": "real-time-synced", "recommendation": "instant-visibility", "sophistication": "high-technical" } }, "manual-grant-workflow": { "technologies": [ "donation-platform", "audit-trail" ], "technologyProperties": { "integrationMethod": "manual-application", "process": "formal-grant-request", "approval": "daf-sponsor-review", "timeline": "days-to-weeks" } }, "preapproved-qualified-ngo": { "technologies": [ "donation-platform", "smart-contracts" ], "technologyProperties": { "integrationMethod": "pre-vetted-listing", "discovery": "daf-donor-search", "frictionless": "one-click-recommend", "status": "requires-qualification" } }, "multi-daf-aggregator": { "technologies": [ "donation-platform", "smart-contracts" ], "technologyProperties": { "integrationMethod": "multi-platform-aggregate", "coverage": "broader-daf-reach", "complexity": "highest-integration", "impact": "maximum-daf-accessibility" } } }, "prefillFrom": null, "briefSection": "Donation infrastructure", "text": "Which DAF platform do you currently use or plan to use?", "ngoText": "Which DAF platform do you currently use or plan to use?" }, { "id": "tax-reporting-for-daf", "type": "select", "options": [ { "label": "Standard grant letter (recipient-issued)", "value": "standard-grant-letter" }, { "label": "Automated tax forms (1098-T or custom)", "value": "automated-tax-forms" }, { "label": "DAF platform handles tax reporting (passthrough)", "value": "daf-platform-passthrough" } ], "propertyMapping": { "standard-grant-letter": { "technologies": [ "reporting-automation", "donation-platform" ], "technologyProperties": { "reportingMethod": "grant-acknowledgement-letter", "preparation": "ngo-generated", "taxRole": "donor-handles-tax", "simplicity": "standard" } }, "automated-tax-forms": { "technologies": [ "reporting-automation", "donation-platform" ], "technologyProperties": { "reportingMethod": "automated-form-generation", "accuracy": "system-calculated", "compliance": "tax-standard-compliant", "speed": "real-time-available" } }, "daf-platform-passthrough": { "technologies": [ "donation-platform", "audit-trail" ], "technologyProperties": { "reportingMethod": "daf-responsible", "ngoRole": "acknowledge-only", "coordination": "daf-manages-process", "burden": "minimal-for-ngo" } } }, "prefillFrom": null, "briefSection": "Compliance and audit", "text": "What are your current tax reporting requirements for DAF transactions?", "ngoText": "What are your current tax reporting requirements for DAF transactions?" }, { "id": "grant-timing-flexibility", "type": "select", "options": [ { "label": "Immediate grants (funds received within days)", "value": "immediate-grant-days" }, { "label": "Scheduled grants (NGO proposes timeline)", "value": "scheduled-ngo-timeline" }, { "label": "DAF advisor discretion (no fixed timeline)", "value": "daf-advisor-discretion" } ], "propertyMapping": { "immediate-grant-days": { "technologies": [ "donation-platform", "payment-gateway" ], "technologyProperties": { "timing": "rapid-settlement", "dafAdvantage": "faster-than-direct-giving", "cashFlow": "immediate-available", "certainty": "instant" } }, "scheduled-ngo-timeline": { "technologies": [ "smart-contracts", "donation-platform" ], "technologyProperties": { "timing": "ngo-configured-schedule", "flexibility": "programmatic-release", "alignment": "project-milestone-based", "automation": "smart-contract-triggered" } }, "daf-advisor-discretion": { "technologies": [ "donation-platform", "audit-trail" ], "technologyProperties": { "timing": "discretionary-unscheduled", "donor-control": "advisor-decides", "unpredictability": "high-for-ngo", "flexibility": "maximum-for-daf-holder" } } }, "prefillFrom": null, "briefSection": "Fund tracking", "text": "What flexibility should be offered for grant timing?", "ngoText": "What flexibility should be offered for grant timing?" }, { "id": "sq-UC-F-089-001", "type": "single-select", "options": [ { "value": "api-direct", "label": "Direct API integration" }, { "value": "csv-batch", "label": "CSV batch upload" }, { "value": "manual-entry", "label": "Manual entry" }, { "value": "payment-processor-bridge", "label": "Payment processor bridge" }, { "value": "multi-platform", "label": "Multi-platform support" } ], "propertyMapping": { "api-direct": { "technologies": [ "api-integration", "direct-connection" ], "technologyProperties": {} }, "csv-batch": { "technologies": [ "csv-import", "batch-processing" ], "technologyProperties": {} }, "manual-entry": { "technologies": [ "form-system", "manual-input" ], "technologyProperties": {} }, "payment-processor-bridge": { "technologies": [ "payment-api", "gateway-integration" ], "technologyProperties": {} }, "multi-platform": { "technologies": [ "multi-connection", "platform-agnostic" ], "technologyProperties": {} } }, "briefSection": "requirements", "text": "Are there high-net-worth individuals in your supporter base who you know use donor-advised funds for charitable giving?", "ngoText": "Are there high-net-worth individuals in your supporter base who you know use donor-advised funds for charitable giving?" }, { "id": "sq-UC-F-089-006", "type": "single-select", "options": [ { "value": "annual-expenditure-report", "label": "Annual expenditure report" }, { "value": "real-time-utilisation", "label": "Real-time utilisation" }, { "value": "impact-narrative", "label": "Impact narrative" }, { "value": "financial-statement", "label": "Financial statement" }, { "value": "no-reporting-required", "label": "No reporting required" } ], "propertyMapping": { "annual-expenditure-report": { "technologies": [ "annual-reporting", "export-system" ], "technologyProperties": {} }, "real-time-utilisation": { "technologies": [ "dashboard-sync", "real-time-reporting" ], "technologyProperties": {} }, "impact-narrative": { "technologies": [ "narrative-system", "report-generation" ], "technologyProperties": {} }, "financial-statement": { "technologies": [ "financial-reporting", "statement-generation" ], "technologyProperties": {} }, "no-reporting-required": { "technologies": [ "minimal-tracking", "no-reporting" ], "technologyProperties": {} } }, "briefSection": "compliance", "text": "What reporting back to DAF platforms is required?", "ngoText": "What reporting back to DAF platforms is required?" } ], "complexityFactors": { "relationships": 2, "operationalChange": 2, "dataCompliance": 2 }, "suggestedCriteria": [ { "id": "SC-DAF-INTEGRATION", "name": "DAF Platform Interoperability", "description": "The provider can connect with major donor-advised fund platforms for automated grant processing. DAFs hold $230B+ in assets. Integration removes friction that prevents grants from being recommended.", "weight": 0.3, "ratingGuide": { "5": "Direct API integration with top 5 DAF platforms. Automated grant recommendation processing. Real-time grant status tracking. Bi-directional data flow (grant status back to DAF portal). Pre-approved charity profile maintained across platforms.", "4": "Integration with 2-3 major DAF platforms. Semi-automated grant processing. Status tracking available. Charity profile on major platforms.", "3": "Integration with one major DAF platform. Manual processing for others. Basic status tracking. Charity profile requires manual maintenance.", "2": "No platform integration. DAF grants processed as standard donations. Manual matching of grants to DAF records.", "1": "No DAF awareness. Grants arrive as anonymous donations. No tracking back to DAF source. Acknowledgment letters must be sent manually." } }, { "id": "SC-GRANT-TRANSPARENCY", "name": "Grant Allocation Transparency for DAF Advisors", "description": "DAF advisors can see how their recommended grants are being used. DAF donors are typically high-net-worth and expect detailed stewardship reporting. Blockchain transparency is a strong differentiator here.", "weight": 0.25, "ratingGuide": { "5": "Dedicated advisor portal showing grant allocation, fund flow, and impact metrics per grant. Blockchain-verified spending trail. Customisable update frequency. Portfolio view across multiple grants. Shareable with financial advisors.", "4": "Advisor-accessible dashboard with grant-level reporting. Fund flow transparency. Quarterly updates. Impact metrics per grant.", "3": "Standard donor portal with grant-level filtering. Basic fund usage reports. Semi-annual updates.", "2": "Generic donor communications. No grant-specific tracking. DAF advisors treated same as individual donors.", "1": "No advisor-facing transparency. Grant acknowledgment letter only. No ongoing stewardship." } }, { "id": "SC-TAX-COMPLIANCE-DAF", "name": "DAF-Specific Tax & Regulatory Compliance", "description": "The provider handles the specific compliance requirements of DAF grants (contemporaneous written acknowledgments, grant purpose restrictions, expenditure responsibility for international grants). DAF compliance is more complex than standard donation receipting.", "weight": 0.2, "ratingGuide": { "5": "Automated contemporaneous acknowledgment per IRS requirements. Expenditure responsibility tracking for international grants. Grant purpose restriction enforcement. Excess business holdings monitoring. Annual compliance reporting to DAF sponsor.", "4": "Automated acknowledgments. Expenditure responsibility tracking. Grant purpose recorded and monitored. Basic compliance reporting.", "3": "Acknowledgment generation (semi-manual). Basic expenditure tracking. Grant purpose recorded but not enforced. Manual compliance reporting.", "2": "Standard donation receipt (not DAF-specific). No expenditure responsibility tracking. Manual compliance processes.", "1": "No DAF-specific compliance features. NGO must handle all DAF regulatory requirements manually." } }, { "id": "SC-ADVISOR-ENGAGEMENT", "name": "DAF Advisor Relationship Management", "description": "The system supports ongoing relationship management with DAF advisors to encourage repeat grant recommendations. DAF advisors often support the same charities year after year, but only if stewardship is excellent.", "weight": 0.15, "ratingGuide": { "5": "DAF advisor CRM with giving history, preferences, and engagement tracking. Automated stewardship sequences. Personalised impact updates. Grant anniversary reminders. Wealth screening integration for prospect identification.", "4": "Advisor profiles with giving history. Automated update sequences. Impact reports tailored to advisor interests. Basic prospect identification.", "3": "Basic advisor records. Manual stewardship process. Standard impact reports. No prospect identification.", "2": "DAF advisors tracked as regular donors. No special relationship management features.", "1": "No advisor relationship management. Each grant treated as independent transaction." } }, { "id": "SC-FUND-DESIGNATION", "name": "Fund Designation & Restriction Management", "description": "The system can handle DAF grants with specific fund designations and restrictions. DAF advisors often specify how grants should be used. The system must track and enforce these restrictions transparently.", "weight": 0.1, "ratingGuide": { "5": "Flexible fund designation with smart contract enforcement. Multiple restriction types (project, geography, purpose). Automatic compliance monitoring. Blockchain-verified spending against restrictions. Exception workflow for necessary changes.", "4": "Fund designation tracking with automated monitoring. Common restriction types supported. Compliance reporting. Change request process.", "3": "Basic designation tracking. Manual compliance monitoring. Standard restriction categories. Manual reporting.", "2": "Designation recorded in notes field. No automated tracking or enforcement. Manual compliance checking.", "1": "No fund designation capability. All grants treated as unrestricted. Restriction tracking done outside the system." } } ], "procurement": { "marketMaturity": "mature", "primaryMode": "off-the-shelf", "alternativeModes": [ "rfq" ], "reasoning": "Donor-advised fund integration is mature in DAF platforms.", "exampleProductCategories": [ "daf-platform", "donor-advised-fund-rails" ], "partnerChannels": [], "lastReviewed": "2026-05-01" } }, { "id": "UC-F-089", "name": "Gift matching verification", "category": "F", "subcategory": "Fundraising Mechanisms", "description": "Confirm that a matching gift promised by a company or individual was actually paid, and let everyone involved see the same record.", "bCriteria": [ "B1", "B3", "B7" ], "requiredComponents": [ "smart-contracts", "donation-platform", "audit-trail", "matching-engine" ], "conditionalComponents": [ "reporting-automation" ], "crossCategoryDependencies": [], "p2TriggerConditions": { "description": "Activated when P2 shows gift matching programmes with rule complexity and broad donor base requiring verification", "rangeSignals": [ "matchingProgram >=2", "matchingRules >=2", "donorBase >=3" ] }, "contextFieldsTemplate": [ "number_of_matchers", "matching_ratio_rules", "campaign_matching_limits", "matching_fund_source", "verification_timing", "dispute_cases_baseline" ], "implementationComplexity": "low", "examples": { "note": "Smart contract verifies matching conditions automatically", "references": [ { "name": "Benevity", "url": "https://benevity.com", "solved": "Corporate gift-matching infrastructure with verification of donation eligibility and matching ratios." }, { "name": "Bright Funds", "url": "https://www.brightfunds.org", "solved": "Corporate-giving platform with built-in matching verification and disbursement audit trails." } ] }, "propertyMapping": {}, "solutionQuestions": [ { "id": "matching-rule-configuration", "type": "select", "options": [ { "label": "1:1 fixed match (every $1 matched by $1)", "value": "onetoone-fixed-match" }, { "label": "Tiered matching (higher match % for larger gifts)", "value": "tiered-progressive-match" }, { "label": "Budget-capped matching (match until cap reached)", "value": "budget-capped-match" }, { "label": "Time-limited matching (match available only during campaign)", "value": "time-limited-campaign-match" } ], "propertyMapping": { "onetoone-fixed-match": { "technologies": [ "smart-contracts", "donation-platform" ], "technologyProperties": { "matchType": "fixed-ratio", "ratio": "1-to-1", "simplicity": "highest", "understandability": "instant" } }, "tiered-progressive-match": { "technologies": [ "smart-contracts", "donation-platform" ], "technologyProperties": { "matchType": "progressive-tiered", "incentive": "larger-gifts-more-leverage", "complexity": "moderate", "motivation": "encourages-larger-donations" } }, "budget-capped-match": { "technologies": [ "smart-contracts", "donation-platform" ], "technologyProperties": { "matchType": "limited-pool", "budgetControl": "matcher-defined-total", "fairness": "first-come-first-served", "transparency": "requires-clear-communication" } }, "time-limited-campaign-match": { "technologies": [ "smart-contracts", "donation-platform" ], "technologyProperties": { "matchType": "temporal-limited", "timing": "campaign-period-specific", "urgency": "creates-deadline-effect", "engagement": "boosts-participation" } } }, "prefillFrom": null, "briefSection": "Smart contract logic", "text": "What are your current matching fund rules and ratios?", "ngoText": "What are your current matching fund rules and ratios?" }, { "id": "match-verification-method", "type": "select", "options": [ { "label": "Manual matcher attestation (honor system)", "value": "manual-attestation-honor" }, { "label": "Bank transfer verification (match funds confirmed received)", "value": "bank-transfer-confirmed" }, { "label": "Automated escrow (match funds locked until verified)", "value": "smart-contract-escrow" }, { "label": "Third-party matcher verification (independent confirmation)", "value": "third-party-verification" } ], "propertyMapping": { "manual-attestation-honor": { "technologies": [ "donation-platform", "audit-trail" ], "technologyProperties": { "verificationMethod": "trust-based-certification", "automation": "none-manual-entry", "cost": "lowest", "reliability": "depends-on-matcher" } }, "bank-transfer-confirmed": { "technologies": [ "payment-gateway", "donation-platform" ], "technologyProperties": { "verificationMethod": "bank-reconciliation", "automation": "high-ach-eft-verify", "certainty": "high-confirmed-funds", "cost": "moderate" } }, "smart-contract-escrow": { "technologies": [ "smart-contracts", "donation-platform" ], "technologyProperties": { "verificationMethod": "automated-on-chain", "security": "cryptographic-proof", "timing": "immediate-settlement", "cost": "blockchain-gas-fees" } }, "third-party-verification": { "technologies": [ "donation-platform", "audit-trail" ], "technologyProperties": { "verificationMethod": "external-auditor", "rigor": "highest-third-party", "cost": "highest-professional", "credibility": "maximum" } } }, "prefillFrom": null, "briefSection": "Infrastructure requirements", "text": "How do you currently verify that matching fund requirements are met?", "ngoText": "How do you currently verify that matching fund requirements are met?" }, { "id": "matcher-management", "type": "select", "options": [ { "label": "Single corporate matcher (one sponsor)", "value": "single-corporate-matcher" }, { "label": "Multiple individual matchers (crowdsourced matching)", "value": "multiple-individual-matchers" }, { "label": "Matching pool (aggregated from multiple sources)", "value": "matching-pool-aggregated" } ], "propertyMapping": { "single-corporate-matcher": { "technologies": [ "donation-platform", "fund-tracking" ], "technologyProperties": { "matcherScalability": "one-sponsor", "complexity": "lowest", "relationship": "dedicated-partnership", "marketing": "opportunity-for-co-branding" } }, "multiple-individual-matchers": { "technologies": [ "smart-contracts", "donation-platform" ], "technologyProperties": { "matcherScalability": "distributed-matchers", "participation": "crowd-sourced-matching", "complexity": "moderate-coordination", "reach": "broader-matcher-pool" } }, "matching-pool-aggregated": { "technologies": [ "smart-contracts", "donation-platform" ], "technologyProperties": { "matcherScalability": "pooled-distributed", "fungibility": "all-matching-combined", "attribution": "simplified-no-individual-tracking", "efficiency": "highest" } } }, "prefillFrom": null, "briefSection": "Donor experience", "text": "How do you currently manage and track matching fund providers?", "ngoText": "How do you currently manage and track matching fund providers?" }, { "id": "gift-match-compliance", "type": "multiselect", "options": [ { "label": "Tax deductibility receipting", "value": "tax" }, { "label": "Anti-money laundering (AML) / Know Your Donor", "value": "aml" }, { "label": "Cross-border fund transfer regulations", "value": "cross-border" }, { "label": "Cryptocurrency-specific regulations", "value": "crypto-reg" }, { "label": "No specific compliance requirements", "value": "none" } ], "propertyMapping": { "tax": { "technologies": [ "Automated receipt generation" ], "technologyProperties": { "complianceModule": "Tax receipting", "regulatoryRisk": "Low" } }, "aml": { "technologies": [ "KYC/AML screening module" ], "technologyProperties": { "complianceModule": "AML screening", "regulatoryRisk": "Medium" } }, "cross-border": { "technologies": [ "Cross-border compliance module" ], "technologyProperties": { "complianceModule": "Transfer regulations", "regulatoryRisk": "High" } }, "crypto-reg": { "technologies": [ "Crypto compliance framework" ], "technologyProperties": { "complianceModule": "Crypto regulations", "regulatoryRisk": "High" } }, "none": { "technologies": [], "technologyProperties": { "complianceModule": "None required", "regulatoryRisk": "Low" } } }, "prefillFrom": null, "briefSection": "Compliance and audit", "text": "What financial compliance requirements apply to gift matching?", "ngoText": "What financial compliance requirements apply to gift matching?" }, { "id": "sq-UC-F-089-003", "type": "single-select", "options": [ { "value": "bank-confirmation", "label": "Bank confirmation" }, { "value": "blockchain-verification", "label": "Digital verification" }, { "value": "matcher-attestation", "label": "Matcher attestation" }, { "value": "third-party-escrow", "label": "Third-party escrow" }, { "value": "trust-based", "label": "Trust-based" } ], "propertyMapping": { "bank-confirmation": { "technologies": [ "bank-api", "transaction-confirmation" ], "technologyProperties": {} }, "blockchain-verification": { "technologies": [ "blockchain-check", "transaction-verification" ], "technologyProperties": {} }, "matcher-attestation": { "technologies": [ "attestation-system", "signature-verification" ], "technologyProperties": {} }, "third-party-escrow": { "technologies": [ "escrow-system", "intermediary" ], "technologyProperties": {} }, "trust-based": { "technologies": [ "basic-confirmation", "trust-model" ], "technologyProperties": {} } }, "briefSection": "compliance", "text": "What verification is needed to confirm the matcher has actually transferred matched funds?", "ngoText": "What verification is needed to confirm the matcher has actually transferred matched funds?" }, { "id": "matching-engine-type", "type": "select", "options": [ { "label": "Automated 1:1 matching (each gift auto-matched)", "value": "auto-1to1" }, { "label": "Pool-based matching (matching fund pool, allocated proportionally)", "value": "pool-based" }, { "label": "Tiered matching (different match rates based on criteria)", "value": "tiered" }, { "label": "Not sure, need guidance", "value": "guidance-needed" } ], "propertyMapping": { "auto-1to1": { "technologies": [ "Automated gift matching engine", "Match verification smart contract", "Match reporting service" ], "technologyProperties": { "matchType": "1:1 automated matching", "transparency": "Each match verifiable Digital", "matchRatio": "Configurable (1:1, 2:1, etc.)" } }, "pool-based": { "technologies": [ "Pool-based matching engine", "Matching fund allocation smart contract", "Match reporting service" ], "technologyProperties": { "matchType": "Pool-based proportional allocation", "transparency": "Pool balance and allocations Digital", "matchRatio": "Proportional to pool size" } }, "tiered": { "technologies": [ "Tiered matching engine", "Criteria-based match calculator", "Match reporting service" ], "technologyProperties": { "matchType": "Tiered by criteria", "transparency": "Match criteria and rates Digital", "matchRatio": "Varies by tier" } }, "guidance-needed": { "technologies": [ "Gift matching engine framework", "Match reporting service" ], "technologyProperties": { "matchType": "To be determined", "transparency": "To be determined", "matchRatio": "To be determined" } } }, "prefillFrom": null, "briefSection": "Gift matching", "text": "How does gift matching currently work for this fundraising solution?", "ngoText": "How does gift matching currently work for this fundraising solution?" }, { "id": "beneficiary-choice", "label": "How will beneficiaries exercise choice in how they receive and use this service?", "type": "select", "briefSection": "Donor experience", "options": [ { "label": "Beneficiaries choose between delivery methods (cash, voucher, mobile money, direct)", "value": "delivery-choice" }, { "label": "Beneficiaries choose preferred merchants or service points", "value": "merchant-choice" }, { "label": "Beneficiaries control their own data sharing preferences", "value": "data-choice" }, { "label": "Multiple choice dimensions (delivery + merchant + data)", "value": "full-choice" }, { "label": "Limited choice: programme constraints determine delivery", "value": "limited" } ], "propertyMapping": { "delivery-choice": { "technologies": [], "technologyProperties": { "beneficiaryChoice": "Delivery method choice", "dignityDesign": "Beneficiaries select preferred receipt method" } }, "merchant-choice": { "technologies": [], "technologyProperties": { "beneficiaryChoice": "Merchant/service point choice", "dignityDesign": "Beneficiaries select where to redeem" } }, "data-choice": { "technologies": [], "technologyProperties": { "beneficiaryChoice": "Data sharing choice", "dignityDesign": "Beneficiaries control personal data sharing" } }, "full-choice": { "technologies": [], "technologyProperties": { "beneficiaryChoice": "Multi-dimensional choice", "dignityDesign": "Full beneficiary agency across delivery, merchant, and data" } }, "limited": { "technologies": [], "technologyProperties": { "beneficiaryChoice": "Limited by programme design", "dignityDesign": "Programme constraints; beneficiary informed of reasons" } } }, "text": "How will beneficiaries exercise choice in how they receive and use this service?" } ], "complexityFactors": { "relationships": 2, "operationalChange": 2, "dataCompliance": 1 }, "suggestedCriteria": [ { "id": "SC-MATCH-VERIFICATION", "name": "Automated Match Verification & Execution", "description": "The system can automatically verify that a donation qualifies for matching and trigger the matched gift. Manual matching verification is slow, error-prone, and often results in unclaimed matches. Smart contract automation is the core value.", "weight": 0.3, "ratingGuide": { "5": "Smart contract verifies matching eligibility in real-time against configurable rules (ratio, caps, eligibility criteria, time windows). Matched gift executed automatically upon verification. Multi-matcher support (corporate + individual matchers on same campaign). Blockchain-anchored proof of match.", "4": "Automated rule checking with near-real-time match execution. Configurable matching rules. Supports 2-3 matcher types. Verification audit trail.", "3": "Semi-automated: system flags eligible donations, matcher or admin approves. Basic rule configuration. Single matcher per campaign. Match recorded after approval.", "2": "Manual verification by NGO staff against matcher's criteria. Match tracked in system after manual entry. Significant processing delay.", "1": "Fully manual matching. NGO staff compiles eligible donations, submits to matcher, waits for payment. Weeks of delay. High administrative burden." } }, { "id": "SC-MATCH-TRANSPARENCY", "name": "Match Status Transparency for All Parties", "description": "Donors, matchers, and the NGO all can see match status in real-time. Donors want to know their gift was matched. Matchers want to see their commitment being used. NGOs need to track outstanding matches.", "weight": 0.25, "ratingGuide": { "5": "Real-time match status visible to donor ('Your gift was matched!'), matcher (portfolio of matched donations with running total), and NGO (match programme dashboard). Push notifications on match events. Public match tracker for campaigns. Blockchain-verified match records.", "4": "Match status visible to all parties within hours. Notifications to donor and matcher. NGO dashboard with match tracking. Basic public display.", "3": "Match confirmation sent to donor by email. Matcher receives periodic reports. NGO has match tracking report. No real-time visibility.", "2": "Donor notified at end of campaign about matched total. Matcher receives summary report. NGO tracks manually.", "1": "No match status visibility. Donors don't know if their gift was matched. Matcher receives final total only. NGO reconciles manually at campaign end." } }, { "id": "SC-MATCH-RULES", "name": "Matching Rule Flexibility & Configuration", "description": "This measures how flexible the matching rule engine is. Different matchers have different matching formulae: 1:1, 2:1, caps per donor, caps per campaign, time-limited matches, category-restricted matches. The system must handle this variety without custom development.", "weight": 0.2, "ratingGuide": { "5": "Configurable matching ratios (any ratio), per-donor caps, per-campaign caps, time windows, donor eligibility filters, category restrictions, geographic restrictions. Multiple active matching rules simultaneously. No-code rule builder.", "4": "Common ratios (1:1, 2:1, 3:1), per-campaign caps, time windows, basic eligibility filters. Visual rule configuration. Multiple rules supported.", "3": "Standard ratios with per-campaign caps. Time-limited matching supported. Basic configuration interface. Single rule set per campaign.", "2": "Fixed matching ratios (1:1 or 2:1 only). Single cap. No time-based rules. Configuration requires support.", "1": "Hardcoded 1:1 matching only. No caps, no time limits, no eligibility rules. Any customisation requires development." } }, { "id": "SC-MATCH-REPORTING", "name": "Match Programme Reporting & Analytics", "description": "The system can generate reports showing match programme performance for both the NGO and the matcher. Matchers need to report to their boards on matching programme impact. NGOs need to measure matching programme ROI.", "weight": 0.15, "ratingGuide": { "5": "Comprehensive analytics: match utilisation rate, average time to match, donor acquisition via matching, match programme ROI, matcher-specific impact reports. Exportable for matcher's board presentation. Year-over-year comparison. Predictive analytics for match fund depletion.", "4": "Match utilisation tracking, donor response metrics, matcher impact reports. Exportable data. Period comparison available.", "3": "Basic match totals and utilisation rate. Standard reports for matcher. Campaign-level summary. Manual export.", "2": "Total matched and unmatched donation amounts. No analytics. Manual report compilation for matcher.", "1": "No match-specific reporting. NGO must manually calculate match totals from transaction records." } }, { "id": "SC-MATCH-FRAUD", "name": "Match Fraud Prevention", "description": "The system prevents fraudulent matching claims (duplicate donations, self-matching, circular donations, or exceeding match caps). Smart contract enforcement should make match fraud structurally impossible.", "weight": 0.1, "ratingGuide": { "5": "Smart contract prevents duplicate matching, self-matching (same entity on both sides), and cap overruns structurally. Donor identity verification prevents circular donations. Anomaly detection for suspicious patterns. All prevention measures transparent and auditable.", "4": "Automated duplicate detection. Self-matching prevention. Cap enforcement. Basic anomaly alerts. Audit trail for all match decisions.", "3": "Duplicate detection and cap enforcement automated. Self-matching prevention requires manual review. Basic audit trail.", "2": "Cap enforcement only. Duplicate detection is manual. No self-matching prevention. Limited audit trail.", "1": "No fraud prevention. Matching claims taken at face value. No duplicate detection. No cap enforcement in system." } } ], "procurement": { "marketMaturity": "mature", "primaryMode": "off-the-shelf", "alternativeModes": [ "rfq" ], "reasoning": "Gift matching is built into mature giving SaaS.", "exampleProductCategories": [ "matching-gift-platform", "giving-saas" ], "partnerChannels": [], "lastReviewed": "2026-05-01" } }, { "id": "UC-F-090", "name": "Donor identity verification for anti-money laundering compliance", "category": "F", "subcategory": "Compliance and Due Diligence", "description": "Check donors' identities once and give regulators and partners proof of the result, without passing on the underlying personal details.", "bCriteria": [ "B2", "B3", "B6", "B7" ], "requiredComponents": [ { "component": "identity-verification", "description": "Donor identity capture and verification workflow (ID document, liveness, beneficial-owner resolution for entities)" }, { "component": "kyc-platform", "description": "KYC/KYB tooling integrated with sanctions, PEP, and adverse-media data sources" }, { "component": "audit-mechanism", "description": "Cryptographic audit trail linking donor, verification events, screening results, and disposition decisions" }, { "component": "compliance-rules-engine", "description": "Policy layer encoding AML/CFT thresholds, screening rules, and jurisdictional requirements (FATF VASP, OFAC, local NCTL)" }, { "component": "verifiable-credentials", "description": "Reusable verifiable credentials for verified donors to avoid re-verification across NGOs / platforms" } ], "conditionalComponents": [ { "component": "biometric-capture", "condition": "If liveness / face-match is required as part of verification" }, { "component": "sanctions-screening", "condition": "If continuous (not just onboarding) sanctions, PEP and adverse-media screening is required" }, { "component": "privacy-tech", "condition": "If the system must prove compliance (e.g. 'donor is verified and not on sanctions list') without exposing donor identity" }, { "component": "smart-contracts", "condition": "If donation acceptance is gated on a verifiable, on-chain KYC attestation (particularly relevant for crypto donations)" } ], "crossCategoryDependencies": [ "UC-B-024 for beneficiary/donor identity primitives \u2014 shared identity infrastructure", "UC-F-082 for cryptocurrency and digital-asset donations \u2014 on-chain KYC attestations are most valuable for crypto flows", "UC-A-024 for stablecoin treasury \u2014 AML controls extend from donor inflow through treasury and outflow" ], "p2TriggerConditions": { "description": "Activated when P2 indicates large-donor exposure, significant crypto or anonymous-source donations, multi-jurisdictional AML exposure, or recent regulatory scrutiny.", "rangeSignals": [ "majorDonorCount >= material", "cryptoDonationVolume >= material", "jurisdictionalAmlExposure >= moderate", "regulatoryScrutinyHistory == present" ] }, "contextFieldsTemplate": [ { "field": "donorProfile", "source": "P2 CatF", "description": "Mix of individual, corporate, foundation, anonymous, and crypto donors" }, { "field": "jurisdictions", "source": "P0 + P2", "description": "Jurisdictions the org is subject to (HQ) and from which donations are accepted" }, { "field": "thresholds", "source": "Legal / policy", "description": "Monetary thresholds that trigger enhanced due diligence (CDD / EDD)" }, { "field": "currentKyc", "source": "P0 compliance", "description": "Current KYC depth, tooling, and coverage across donor segments" }, { "field": "incidentHistory", "source": "P0 compliance", "description": "Past incidents (rejected donations, regulatory findings, reputational events)" } ], "implementationComplexity": "high", "examples": { "note": "NGO AML is governed by FATF Recommendation 8 (NPO sector) and local equivalents. Crypto-donation flows additionally bring FATF VASP requirements, OFAC Specially Designated Nationals lists, and the 'travel rule' into scope. Mature blockchain-analytics ecosystems (Chainalysis, TRM Labs, Elliptic) de-risk crypto acceptance materially.", "references": [ { "name": "Chainalysis \u2014 blockchain analytics for compliance", "url": "https://www.chainalysis.com", "solved": "Transaction-level risk scoring and sanctions screening for on-chain donations, reference tooling for NGOs accepting crypto." }, { "name": "OFAC Sanctions lists (SDN, NS-PLC)", "url": "https://ofac.treasury.gov", "solved": "Authoritative US sanctions reference, the lookup any NGO-facing KYC system must reconcile against." }, { "name": "FATF \u2014 Guidance for a risk-based approach to virtual assets and VASPs", "url": "https://www.fatf-gafi.org/en/publications/Fatfrecommendations/Guidance-rba-virtual-assets-2021.html", "solved": "International standard for AML/CFT in the virtual-asset space, which defines the rule schema a compliance engine must encode for crypto donations." }, { "name": "FATF Recommendation 8 \u2014 non-profit organisations", "url": "https://www.fatf-gafi.org/en/topics/fatf-recommendations.html", "solved": "Baseline AML/CFT guidance specifically for the NPO sector, the regulatory floor for NGO donor due diligence." } ] }, "solutionQuestions": [ { "id": "kyc-depth", "type": "select", "options": [ { "label": "Light: basic identity capture, threshold-triggered verification", "value": "light" }, { "label": "Standard CDD: ID verification and sanctions screening at onboarding", "value": "standard-cdd" }, { "label": "Enhanced CDD for high-risk donors", "value": "ecdd" }, { "label": "Continuous: ongoing monitoring and re-verification", "value": "continuous" } ], "propertyMapping": { "light": { "technologies": [ "Identity capture form", "Threshold monitor" ], "technologyProperties": { "coverage": "limited", "cost": "low", "regulatoryFit": "minimum-baseline" } }, "standard-cdd": { "technologies": [ "KYC vendor integration", "Sanctions screening at onboarding" ], "technologyProperties": { "coverage": "broad", "cost": "moderate", "regulatoryFit": "strong for standard donors" } }, "ecdd": { "technologies": [ "Enhanced KYC vendor", "PEP and adverse-media screening", "Beneficial-owner resolution" ], "technologyProperties": { "coverage": "deep", "cost": "high", "regulatoryFit": "strong for high-risk" } }, "continuous": { "technologies": [ "Continuous screening platform", "Ongoing risk monitoring", "Alert workflow" ], "technologyProperties": { "coverage": "continuous", "cost": "very-high", "regulatoryFit": "very-strong" } } }, "prefillFrom": null, "briefSection": "Due diligence depth", "text": "What level of donor due diligence is required?", "ngoText": "What level of donor due diligence is required?" }, { "id": "verification-source", "type": "select", "options": [ { "label": "Self-declared identity with no verification", "value": "self" }, { "label": "Government ID with manual review", "value": "gov-id-manual" }, { "label": "Commercial identity-verification provider", "value": "commercial" }, { "label": "Verifiable credentials from accredited issuers", "value": "vc" } ], "propertyMapping": { "self": { "technologies": [ "Self-declaration form" ], "technologyProperties": { "verificationStrength": "weak", "cost": "very-low", "fraudRisk": "high" } }, "gov-id-manual": { "technologies": [ "Document capture", "Manual review workflow" ], "technologyProperties": { "verificationStrength": "moderate", "cost": "moderate-labour", "fraudRisk": "moderate" } }, "commercial": { "technologies": [ "KYC vendor API", "Automated document check", "Liveness detection" ], "technologyProperties": { "verificationStrength": "strong", "cost": "per-verification fee", "fraudRisk": "low" } }, "vc": { "technologies": [ "Verifiable-credential wallet", "Issuer trust registry", "Credential verification service" ], "technologyProperties": { "verificationStrength": "strong + reusable", "cost": "low after ecosystem adoption", "fraudRisk": "low" } } }, "prefillFrom": null, "briefSection": "Verification source", "text": "Where does the identity verification evidence come from?", "ngoText": "Where does the identity verification evidence come from?" }, { "id": "credential-model", "type": "select", "options": [ { "label": "Centralised database record (legacy KYC)", "value": "centralised" }, { "label": "Portable verifiable credential in donor-held wallet", "value": "vc-portable" }, { "label": "Zero-knowledge proof (prove verified, don't expose identity)", "value": "zk" }, { "label": "Hybrid: centralised record + ZK proof for public-chain donations", "value": "hybrid" } ], "propertyMapping": { "centralised": { "technologies": [ "KYC database", "Access control" ], "technologyProperties": { "privacyPreservation": "weak", "portability": "none", "interNgoReuse": "none" } }, "vc-portable": { "technologies": [ "VC issuer", "Donor wallet", "Verification service" ], "technologyProperties": { "privacyPreservation": "moderate", "portability": "strong", "interNgoReuse": "strong" } }, "zk": { "technologies": [ "ZK proof issuer", "Proof verification service" ], "technologyProperties": { "privacyPreservation": "strong", "portability": "strong", "interNgoReuse": "strong" } }, "hybrid": { "technologies": [ "KYC database", "ZK proof issuer", "Verification service" ], "technologyProperties": { "privacyPreservation": "strong on-chain / moderate off-chain", "portability": "moderate", "interNgoReuse": "moderate" } } }, "prefillFrom": null, "briefSection": "Credential model", "text": "How should verified-donor status be represented?", "ngoText": "How should verified-donor status be represented?" }, { "id": "sanctions-screening-frequency", "type": "select", "options": [ { "label": "Onboarding only", "value": "onboarding" }, { "label": "Onboarding + annual re-screen", "value": "annual" }, { "label": "Onboarding + quarterly re-screen", "value": "quarterly" }, { "label": "Continuous monitoring", "value": "continuous" } ], "propertyMapping": { "onboarding": { "technologies": [ "Onboarding screening integration" ], "technologyProperties": { "detectionLatency": "list-update-gap", "cost": "lowest", "regulatoryFit": "minimum" } }, "annual": { "technologies": [ "Onboarding + annual batch screening" ], "technologyProperties": { "detectionLatency": "up to 12 months", "cost": "low", "regulatoryFit": "moderate" } }, "quarterly": { "technologies": [ "Onboarding + quarterly batch screening" ], "technologyProperties": { "detectionLatency": "up to 3 months", "cost": "moderate", "regulatoryFit": "strong" } }, "continuous": { "technologies": [ "Continuous monitoring platform", "Alert workflow", "Case management" ], "technologyProperties": { "detectionLatency": "hours-to-days", "cost": "high", "regulatoryFit": "very-strong" } } }, "prefillFrom": null, "briefSection": "Screening frequency", "text": "How frequently should sanctions and adverse-media screening run?", "ngoText": "How frequently should sanctions and adverse-media screening run?" }, { "id": "alert-handling-model", "type": "select", "options": [ { "label": "Manual case review per alert", "value": "manual" }, { "label": "Triage tooling with manual resolution", "value": "triage" }, { "label": "Automated low-risk closure + manual escalation", "value": "auto-escalation" }, { "label": "Automated blocking with smart-contract enforcement for on-chain donations", "value": "smart-contract-block" } ], "propertyMapping": { "manual": { "technologies": [ "Case management", "Email/ticket workflow" ], "technologyProperties": { "resolutionSpeed": "slow", "falsePositiveCost": "high", "enforcement": "weak" } }, "triage": { "technologies": [ "Triage platform", "Risk scoring", "Case management" ], "technologyProperties": { "resolutionSpeed": "moderate", "falsePositiveCost": "moderate", "enforcement": "moderate" } }, "auto-escalation": { "technologies": [ "Auto-resolution rules", "Escalation workflow" ], "technologyProperties": { "resolutionSpeed": "fast", "falsePositiveCost": "low", "enforcement": "strong" } }, "smart-contract-block": { "technologies": [ "On-chain sanctions oracle", "Donation-gate smart contract" ], "technologyProperties": { "resolutionSpeed": "real-time", "falsePositiveCost": "visible", "enforcement": "very-strong" } } }, "prefillFrom": null, "briefSection": "Alert handling", "text": "How should AML alerts be handled?", "ngoText": "How should AML alerts be handled?" } ], "complexityFactors": { "relationships": 3, "operationalChange": 4, "dataCompliance": 5 }, "suggestedCriteria": [ { "id": "SC-REGULATORY-COMPLETENESS", "name": "Regulatory Scope Coverage", "description": "How comprehensively does the system cover the regulatory regimes the NGO is exposed to (FATF R.8, OFAC, local NCTL requirements, FATF VASP for crypto)?", "weight": 0.3, "ratingGuide": { "5": "All applicable regimes encoded; rules engine updated automatically when regulators publish changes; coverage gaps explicitly tracked.", "4": "All major regimes encoded; manual quarterly refresh.", "3": "Primary regime (HQ jurisdiction) covered; others manually applied.", "2": "Ad-hoc coverage \u2014 rules applied case by case.", "1": "No regulatory rule framework; manual judgement per donor." } }, { "id": "SC-DONOR-PRIVACY", "name": "Donor Privacy and Data Minimisation", "description": "Does the KYC flow collect the minimum data required, protect it appropriately, and enable proof-of-verification without exposing underlying identity?", "weight": 0.25, "ratingGuide": { "5": "ZK or verifiable-credential model: proof-of-verified without identity disclosure. Data minimisation by construction.", "4": "Centralised record with strong access controls and selective disclosure to external verifiers.", "3": "Centralised record with role-based access; disclosure on request.", "2": "Centralised record with limited access controls.", "1": "Broad exposure of donor identity data across the org." } }, { "id": "SC-SCREENING-LATENCY", "name": "Screening Latency and Freshness", "description": "How quickly after a sanctions list update or adverse-media event is an affected donor flagged?", "weight": 0.15, "ratingGuide": { "5": "Continuous monitoring with hours-to-days detection; automated alert and case creation.", "4": "Quarterly re-screening with automated alerts on hits.", "3": "Annual re-screening with batch alerts.", "2": "Onboarding-only screening; re-screening ad hoc.", "1": "No re-screening after onboarding." } }, { "id": "SC-AUDIT-TAMPER-EVIDENCE", "name": "Audit Trail Tamper Evidence", "description": "Can verification events, screening outcomes, and disposition decisions be proved unaltered after the fact, critical for regulatory examination and internal accountability?", "weight": 0.15, "ratingGuide": { "5": "Cryptographic audit ledger with anchor commitments; any regulator or auditor can verify without trusting a custodian.", "4": "Append-only audit log with signed entries.", "3": "Database audit log with routine backups.", "2": "Database with standard audit.", "1": "No dedicated audit trail." } }, { "id": "SC-OPERATIONAL-EFFICIENCY", "name": "Operational Efficiency of the Flow", "description": "Does the verification flow minimise friction for legitimate donors while blocking ineligible donations at the earliest opportunity?", "weight": 0.15, "ratingGuide": { "5": "Reusable verifiable credentials for returning donors; automated low-risk closure; block enforced at donation entry.", "4": "Streamlined onboarding with risk-based verification; automated escalation.", "3": "Standard onboarding flow with manual review where required.", "2": "Uniform heavy-touch onboarding; high legitimate-donor friction.", "1": "Inconsistent \u2014 some donors over-verified, others under-verified." } } ], "procurement": { "marketMaturity": "mature", "primaryMode": "off-the-shelf", "alternativeModes": [ "rfq" ], "reasoning": "Donor AML verification is mature KYC SaaS feature.", "exampleProductCategories": [ "kyc-saas", "aml-screening-platform" ], "partnerChannels": [], "lastReviewed": "2026-05-01" } }, { "id": "UC-G-090", "name": "Early warning systems with automated fund release triggers", "category": "G", "subcategory": "Anticipatory Financing", "description": "Release funds automatically when an early warning reaches an agreed level, so money is in place before the crisis arrives.", "bCriteria": [ "B7", "B1", "B3" ], "requiredComponents": [ "early-warning-system", "trigger-mechanism", "fund-release-automation", "parametric-oracle" ], "conditionalComponents": [ "smart-contracts", "timestamping-service" ], "crossCategoryDependencies": [ "UC-F-089" ], "p2TriggerConditions": { "description": "Activated when P2 shows anticipatory action programmes with automated threshold-based triggers and rapid funding requirements", "rangeSignals": [ "anticipatoryAction >=3", "automationLevel >=3", "thresholdBased >=2", "rapidFunding >=3" ] }, "contextFieldsTemplate": [ "early_warning_indicator_types", "data_source_reliability", "trigger_threshold_values", "fund_release_speed_requirement", "number_of_trigger_scenarios", "historical_trigger_frequency", "oracle_data_providers" ], "implementationComplexity": "high", "examples": { "note": "World Food Programme's anticipatory action mechanisms", "references": [ { "name": "Etherisc", "url": "https://etherisc.com", "solved": "Parametric crop and disaster insurance triggered by oracle-anchored weather data; deployed with farmer cooperatives in Kenya and Sri Lanka." }, { "name": "Lemonade Crypto Climate Coalition", "url": "https://www.lemonade.com/foundation/crypto-climate", "solved": "Parametric climate insurance for smallholder farmers using on-chain weather triggers." }, { "name": "Oxfam UnBlocked Cash", "url": "https://policy-practice.oxfam.org/", "solved": "Pre-positioned crypto-rails for rapid disbursement to vulnerable populations on disaster-trigger events." } ] }, "propertyMapping": {}, "solutionQuestions": [ { "id": "early-warning-data-sources", "type": "select", "options": [ { "label": "Weather/Meteorological data", "value": "weather-data" }, { "label": "Seismic/Geological sensors", "value": "seismic-data" }, { "label": "Conflict/Security intelligence", "value": "conflict-data" } ], "prefillFrom": null, "briefSection": "Trigger and oracle", "propertyMapping": { "weather-data": { "technologies": [ "Weather data feed", "API3 parametric feeds" ], "technologyProperties": { "dataRefreshRate": "hourly", "providerType": "Distributed-oracle" } }, "seismic-data": { "technologies": [ "IoT sensor network", "USGS data integration" ], "technologyProperties": { "sensorType": "seismic-accelerometer", "refreshRate": "real-time" } }, "conflict-data": { "technologies": [ "Satellite earth-observation feeds", "Armed Conflict Location Event database" ], "technologyProperties": { "updateFrequency": "daily", "sourceVerification": "crowdsourced-verified" } } }, "text": "What type of early warning data sources are required?", "ngoText": "What type of early warning data sources are required?" }, { "id": "trigger-threshold-setting", "type": "select", "options": [ { "label": "Fixed parametric thresholds (e.g., rainfall >150mm)", "value": "fixed-thresholds" }, { "label": "Dynamic thresholds based on historical patterns", "value": "dynamic-thresholds" }, { "label": "Expert consensus-based thresholds", "value": "consensus-thresholds" } ], "prefillFrom": null, "briefSection": "Trigger and oracle", "propertyMapping": { "fixed-thresholds": { "technologies": [ "Smart contract conditions", "Parametric trigger engine" ], "technologyProperties": { "updateMechanism": "governance-voted", "auditTrail": "immutable" } }, "dynamic-thresholds": { "technologies": [ "Machine learning models", "Historical data analytics" ], "technologyProperties": { "modelType": "time-series-forecasting", "retrainingFrequency": "quarterly" } }, "consensus-thresholds": { "technologies": [ "Multi-sig approval", "Expert panel DAO" ], "technologyProperties": { "votingMechanism": "quadratic-voting", "approvalQuorum": "66%" } } }, "text": "For trigger thresholds: do you prefer fixed values set by policy, automatic adjustment based on historical data patterns, or regular expert consensus review?", "ngoText": "For trigger thresholds: do you prefer fixed values set by policy, automatic adjustment based on historical data patterns, or regular expert consensus review?" }, { "id": "fund-release-speed", "type": "select", "options": [ { "label": "Instant (minutes, automated settlement)", "value": "instant-release" }, { "label": "Fast (hours, with automated verification)", "value": "fast-release" }, { "label": "Moderate (24 hours, with manual final approval)", "value": "moderate-release" } ], "prefillFrom": null, "briefSection": "Fund release mechanism", "propertyMapping": { "instant-release": { "technologies": [ "Automated automation", "Layer-2 settlement" ], "technologyProperties": { "settlementTime": "<5 minutes", "confirmations": "1" } }, "fast-release": { "technologies": [ "Automated with delay", "Cross-chain bridge" ], "technologyProperties": { "settlementTime": "1-6 hours", "verificationSteps": "2" } }, "moderate-release": { "technologies": [ "Multi-sig approval", "Time-lock contract" ], "technologyProperties": { "settlementTime": "12-24 hours", "approvalRequired": "authorized-signers" } } }, "text": "What fund release speed is required after trigger activation?", "ngoText": "What fund release speed is required after trigger activation?" }, { "id": "false-positive-tolerance", "type": "select", "options": [ { "label": "Very low (<1%): Cost of false trigger is critical", "value": "very-low-tolerance" }, { "label": "Low (1-5%): Multiple verification sources required", "value": "low-tolerance" }, { "label": "Moderate (5-15%): Speed prioritized over absolute certainty", "value": "moderate-tolerance" } ], "prefillFrom": null, "briefSection": "Data integrity", "propertyMapping": { "very-low-tolerance": { "technologies": [ "Multi-source validation", "Evidence aggregation" ], "technologyProperties": { "requiredConfirm": "3+ independent sources", "waitPeriod": "48 hours" } }, "low-tolerance": { "technologies": [ "Dual-source verification", "Decentralised off-chain data reporting" ], "technologyProperties": { "requiredConfirm": "2 sources", "verificationDelay": "2-12 hours" } }, "moderate-tolerance": { "technologies": [ "Single oracle with reputation", "Insurance backstop" ], "technologyProperties": { "requiredConfirm": "1 verified source", "contingency": "reimbursement-fund" } } }, "text": "What is acceptable tolerance for false positive triggers?", "ngoText": "What is acceptable tolerance for false positive triggers?" }, { "id": "multi-trigger-scenarios", "type": "select", "options": [ { "label": "Single trigger: One condition activates release", "value": "single-trigger" }, { "label": "Multi-trigger (AND): All conditions must be met", "value": "multi-trigger-and" }, { "label": "Multi-trigger (OR): Any condition activates release", "value": "multi-trigger-or" } ], "prefillFrom": null, "briefSection": "Trigger and oracle", "propertyMapping": { "single-trigger": { "technologies": [ "Simple smart contract", "Boolean logic" ], "technologyProperties": { "complexity": "low", "gasEfficiency": "high" } }, "multi-trigger-and": { "technologies": [ "Complex smart contract", "Condition aggregation" ], "technologyProperties": { "logicType": "intersection", "evaluationFrequency": "per-block" } }, "multi-trigger-or": { "technologies": [ "Parametric trigger engine", "Event router" ], "technologyProperties": { "logicType": "union", "prioritization": "severity-based" } } }, "text": "Are there multiple independent trigger scenarios?", "ngoText": "Are there multiple independent trigger scenarios?" }, { "id": "early-warning-source", "type": "select", "options": [ { "label": "Weather and climate data feeds from national or global weather services", "value": "climate-data" }, { "label": "Conflict and security data feeds from monitoring services", "value": "conflict-data" }, { "label": "Health and epidemic data feeds from public health surveillance services", "value": "health-data" }, { "label": "Multiple data sources combined", "value": "multi-source" } ], "propertyMapping": { "climate-data": { "technologies": [ "Climate early warning system", "Weather data oracle", "Forecast-to-action pipeline" ], "technologyProperties": { "dataSource": "Meteorological services (global and national met offices)", "alertType": "Extreme weather, drought, flood forecasts", "leadTime": "3-14 days depending on event type" } }, "conflict-data": { "technologies": [ "Conflict early warning system", "Security data oracle", "Risk assessment pipeline" ], "technologyProperties": { "dataSource": "Conflict monitoring services", "alertType": "Escalation indicators, displacement risk", "leadTime": "Days to weeks depending on context" } }, "health-data": { "technologies": [ "Health early warning system", "Epidemic data oracle", "Health alert pipeline" ], "technologyProperties": { "dataSource": "Health surveillance (WHO, national health authorities)", "alertType": "Disease outbreak, epidemic threshold", "leadTime": "Days to weeks" } }, "multi-source": { "technologies": [ "Multi-source early warning system", "Data aggregation oracle", "Compound risk assessment engine" ], "technologyProperties": { "dataSource": "Multiple feeds (climate + conflict + health)", "alertType": "Compound risk assessment", "leadTime": "Varies by data source" } } }, "prefillFrom": null, "briefSection": "Early warning", "text": "What data sources should feed the early warning system?", "ngoText": "What data sources should feed the early warning system?" } ], "complexityFactors": { "relationships": 4, "operationalChange": 3, "dataCompliance": 2 }, "suggestedCriteria": [ { "id": "SC-G090-DATASRC", "name": "Early Warning Data Source Integration", "description": "This measures how reliably the system ingests and validates data from meteorological, seismological, and other early warning data providers. Integration breadth and data quality validation determine whether triggers fire accurately.", "weight": 0.25, "ratingGuide": { "5": "Integrates with 3+ authoritative data sources (e.g. WMO, national met services, famine early-warning systems). Automated data quality validation with anomaly detection. Redundant data feeds ensure continuity if one source fails.", "4": "Integrates with 2-3 authoritative sources. Automated validation on primary feed. Backup data source configured but not fully automated.", "3": "Single authoritative data source with automated ingestion. Basic validation rules. No redundancy \u2014 outage in source delays triggers.", "2": "Data ingestion requires manual configuration per event type. Limited validation. Single point of failure in data pipeline.", "1": "Manual data entry from external sources. No automated ingestion or validation. Trigger accuracy entirely dependent on operator input." } }, { "id": "SC-G090-TRIGGER", "name": "Trigger Mechanism Accuracy & Calibration", "description": "This measures how well calibrated the automated trigger thresholds are. In anticipatory financing, false positives waste scarce funds while false negatives defeat the purpose. The system must support threshold tuning based on historical data.", "weight": 0.25, "ratingGuide": { "5": "Parametric triggers calibrated against 10+ years of historical data. Back-testing tools available. False positive rate documented and below 15%. Thresholds adjustable per scenario without code changes.", "4": "Triggers calibrated against 5+ years of data. Back-testing available. False positive rate below 25%. Threshold adjustment requires minor configuration.", "3": "Triggers set based on expert judgment with some historical validation. No formal back-testing. Threshold changes require technical support.", "2": "Fixed thresholds with no historical calibration. No back-testing capability. Threshold changes require development work.", "1": "Thresholds are hardcoded or arbitrary. No calibration process. No visibility into false positive/negative rates." } }, { "id": "SC-G090-SPEED", "name": "Fund Release Speed Post-Trigger", "description": "This measures how quickly funds are released and available for disbursement once an early warning threshold is breached and a trigger fires. In anticipatory action, hours matter. The entire value proposition depends on speed.", "weight": 0.25, "ratingGuide": { "5": "Funds released within 4 hours of trigger activation. Fully automated pipeline from trigger to disbursement authorisation. No manual approval bottlenecks in the critical path.", "4": "Funds released within 24 hours. Automated trigger-to-release with a single human confirmation step. Clear escalation if confirmation is delayed.", "3": "Funds released within 48 hours. Trigger generates a request that requires manual approval and processing. Some automation in downstream steps.", "2": "Release takes 3-5 days. Trigger is informational only \u2014 release still follows traditional approval workflows. Limited automation.", "1": "Trigger notification only. Fund release follows entirely manual processes with no acceleration. Effectively same speed as reactive funding." } }, { "id": "SC-G090-ORACLE", "name": "Oracle Reliability & Tamper Resistance", "description": "This measures how reliable the parametric oracle is that bridges real-world data to the smart contract trigger. Oracle failure or manipulation could release funds erroneously or block legitimate releases.", "weight": 0.15, "ratingGuide": { "5": "Decentralised oracle network with multiple independent data attestors. Cryptographic proof of data provenance. Failover mechanisms if primary oracle is unavailable. Audit trail of all oracle submissions.", "4": "Oracle with 2+ independent data sources and consensus mechanism. Signed data submissions. Monitoring and alerting on oracle health.", "3": "Single oracle provider with signed data feeds. Basic health monitoring. No failover \u2014 oracle downtime blocks triggers.", "2": "Centralised oracle with no independent verification. No cryptographic attestation. Limited monitoring.", "1": "Manual data submission to smart contract. No oracle infrastructure. Data provenance not verifiable." } }, { "id": "SC-G090-SCENARIO", "name": "Multi-Scenario Flexibility", "description": "The system can handle multiple disaster types and trigger scenarios simultaneously. Programmes often need to configure triggers for floods, droughts, and cyclones in the same geography with different thresholds and fund pools.", "weight": 0.1, "ratingGuide": { "5": "Supports unlimited concurrent trigger scenarios across disaster types. Each scenario independently configurable with its own thresholds, fund pools, and beneficiary lists. Scenario templates for common disaster types.", "4": "Supports 5+ concurrent scenarios. Independent configuration per scenario. Some templates available.", "3": "Supports 3-5 concurrent scenarios. Configuration requires some shared parameters. No templates \u2014 each setup from scratch.", "2": "Supports 1-2 scenarios at a time. Scenarios share fund pools or thresholds. Adding new scenarios requires significant setup.", "1": "Single scenario only. Cannot run parallel triggers for different disaster types. Complete reconfiguration needed to switch scenarios." } } ], "procurement": { "marketMaturity": "nascent", "primaryMode": "integrator-led", "alternativeModes": [ "consortium" ], "reasoning": "Early warning + auto fund release is research-stage in most contexts.", "exampleProductCategories": [ "early-warning-platform", "automated-disbursement-rails" ], "partnerChannels": [], "lastReviewed": "2026-05-01" } }, { "id": "UC-G-091", "name": "Disaster response fund pre-positioning", "category": "G", "subcategory": "Disaster Response", "description": "Set funds aside before a disaster so they are released as soon as one is declared, without waiting for fresh approvals.", "bCriteria": [ "B7", "B1", "B5" ], "requiredComponents": [ "fund-release-automation", "trigger-mechanism", "smart-contracts", "timestamping-service" ], "conditionalComponents": [ "early-warning-system", "parametric-oracle" ], "crossCategoryDependencies": [], "p2TriggerConditions": { "description": "Activated when P2 shows disaster-prone contexts with rapid funding needs and pre-positioned fund requirements", "rangeSignals": [ "rapidFunding >=3", "disasterFrequency >=2", "preFunding >=3" ] }, "contextFieldsTemplate": [ "disaster_types_covered", "geographic_risk_areas", "pre_positioned_fund_amount", "activation_authority", "disaster_declaration_source", "number_of_deployment_locations", "fund_vesting_timeline" ], "implementationComplexity": "medium", "examples": { "note": "Parametric insurance model applied to humanitarian funding", "references": [ { "name": "OCHA CERF", "url": "https://cerf.un.org", "solved": "Central Emergency Response Fund, pooled donor commitments for rapid disbursement on confirmed disasters; reference model for pre-positioning." }, { "name": "Start Fund", "url": "https://startnetwork.org/start-fund", "solved": "Pre-positioned member-pool with 72-hour rapid release on humanitarian crisis triggers." }, { "name": "IFRC DREF", "url": "https://www.ifrc.org/disaster-response-emergency-fund", "solved": "Disaster Relief Emergency Fund providing pre-positioned response funding to Red Cross and Red Crescent national societies." } ] }, "propertyMapping": {}, "solutionQuestions": [ { "id": "disaster-types-covered", "type": "select", "options": [ { "label": "Earthquakes (magnitude-based)", "value": "earthquakes" }, { "label": "Cyclones/Hurricanes (wind speed metrics)", "value": "cyclones" }, { "label": "Floods (rainfall and water level)", "value": "floods" } ], "prefillFrom": null, "briefSection": "Trigger and oracle", "propertyMapping": { "earthquakes": { "technologies": [ "USGS earthquake API", "Parametric indexing" ], "technologyProperties": { "triggerMagnitude": ">=5.5", "verificationSource": "seismic-stations" } }, "cyclones": { "technologies": [ "National weather service feeds", "Weather data feed" ], "technologyProperties": { "triggerSpeed": ">=150 km/h", "forecastHorizon": "48-72 hours" } }, "floods": { "technologies": [ "River level sensors", "Satellite precipitation data" ], "technologyProperties": { "threshold": "100-year flood level", "sensorDensity": "regional coverage" } } }, "text": "Which disaster types will trigger fund release?", "ngoText": "Which disaster types will trigger fund release?" }, { "id": "activation-authority", "type": "select", "options": [ { "label": "Fully automated on parametric trigger", "value": "fully-automated" }, { "label": "multi-party approval from designated organizations", "value": "multi-sig" }, { "label": "Government disaster authority (with digital verification)", "value": "government-authority" } ], "prefillFrom": null, "briefSection": "Fund release mechanism", "propertyMapping": { "fully-automated": { "technologies": [ "Automated automation", "No human intervention" ], "technologyProperties": { "approvalRequired": "none", "decentralization": "maximum" } }, "multi-sig": { "technologies": [ "Multi-signature wallet", "Governance DAO" ], "technologyProperties": { "signerCount": "3-5", "approvalQuorum": "2/3" } }, "government-authority": { "technologies": [ "Government digital signature", "Official declaration API" ], "technologyProperties": { "verificationMethod": "cryptographic-signature", "backupApproval": "international-monitoring" } } }, "text": "Who currently has the authority to activate emergency fund releases?", "ngoText": "Who currently has the authority to activate emergency fund releases?" }, { "id": "pre-positioned-fund-amount", "type": "select", "options": [ { "label": "Fixed pool per disaster type", "value": "fixed-pool" }, { "label": "Needs-based assessment per geographic region", "value": "needs-based" }, { "label": "Insurance layer approach with co-insurance", "value": "insurance-backed" } ], "prefillFrom": null, "briefSection": "Fund release mechanism", "propertyMapping": { "fixed-pool": { "technologies": [ "Escrow contract", "Time-locked vault" ], "technologyProperties": { "replenishmentMechanism": "automatic-reserve", "governance": "quarterly-review" } }, "needs-based": { "technologies": [ "Historical impact modeling", "Population density data" ], "technologyProperties": { "dataSource": "World Bank/UN data", "recalculationFrequency": "annual" } }, "insurance-backed": { "technologies": [ "ReInsurer integration", "Insurance DAO" ], "technologyProperties": { "coverageType": "parametric-insurance", "reinsuranceBridge": "live" } } }, "text": "For pre-positioned funds, should amounts be: fixed based on annual budget, recalculated yearly based on population and historical costs, or managed through insurance/reinsurance partnerships?", "ngoText": "For pre-positioned funds, should amounts be: fixed based on annual budget, recalculated yearly based on population and historical costs, or managed through insurance/reinsurance partnerships?" }, { "id": "deployment-speed", "type": "select", "options": [ { "label": "Same-day deployment (6-12 hours)", "value": "same-day" }, { "label": "24-48 hour deployment with local coordination", "value": "48-hour" }, { "label": "One-week deployment with full beneficiary verification", "value": "one-week" } ], "prefillFrom": null, "briefSection": "Fund release mechanism", "propertyMapping": { "same-day": { "technologies": [ "Mobile money integration", "CBDC infrastructure" ], "technologyProperties": { "distributionChannel": "existing-networks", "setupTime": "minimal" } }, "48-hour": { "technologies": [ "Local NGO partnerships", "Ground verification" ], "technologyProperties": { "coordinationOverhead": "moderate", "trustAssessment": "real-time" } }, "one-week": { "technologies": [ "Full KYC integration", "Biometric verification" ], "technologyProperties": { "verificationLevel": "high-assurance", "fraudPrevention": "multi-layer" } } }, "text": "What deployment speed is achievable to disaster areas?", "ngoText": "What deployment speed is achievable to disaster areas?" }, { "id": "geographic-coverage", "type": "select", "options": [ { "label": "Single high-risk country/region", "value": "single-region" }, { "label": "Multi-country (sub-regional: e.g., Sahel, SE Asia)", "value": "sub-regional" }, { "label": "Global network with localized pools", "value": "global" } ], "prefillFrom": "NGO-P0-S1-Q7", "briefSection": "Infrastructure requirements", "propertyMapping": { "single-region": { "technologies": [ "Regional fund management", "Local blockchain node" ], "technologyProperties": { "nodesRequired": "1-3", "redundancy": "backup-regional" } }, "sub-regional": { "technologies": [ "Multi-country contract", "Cross-border settlement" ], "technologyProperties": { "currencyHandling": "multi-currency", "localPartners": "5-15" } }, "global": { "technologies": [ "Global DAO governance", "Layer-2 regional hubs" ], "technologyProperties": { "regions": "15+", "coordination": "smart-contract-orchestrated" } } }, "text": "What geographic scope will be covered by pre-positioned funds?", "ngoText": "What geographic scope will be covered by pre-positioned funds?" }, { "id": "trigger-mechanism", "type": "select", "options": [ { "label": "Oracle-based: external data feeds trigger automated actions", "value": "oracle-based" }, { "label": "Threshold-based: predefined conditions trigger automated release", "value": "threshold" }, { "label": "multi-party approval: requires multiple parties to authorise", "value": "multi-sig" }, { "label": "Hybrid: automated triggers with human override capability", "value": "hybrid" } ], "propertyMapping": { "oracle-based": { "technologies": [ "Oracle-based trigger mechanism", "External data feed connection", "Automated trigger executor" ], "technologyProperties": { "triggerSource": "External data oracle", "automationLevel": "Fully automated", "overrideCapability": "Emergency pause only" } }, "threshold": { "technologies": [ "Threshold-based trigger mechanism", "Condition monitoring engine", "Automated release controller" ], "technologyProperties": { "triggerSource": "Predefined thresholds", "automationLevel": "Fully automated above threshold", "overrideCapability": "Threshold adjustment by authorised parties" } }, "multi-sig": { "technologies": [ "Multi-signature trigger mechanism", "Approval workflow engine", "Multi-party authorisation service" ], "technologyProperties": { "triggerSource": "Multi-party approval", "automationLevel": "Human-initiated", "overrideCapability": "N/A \u2014 requires quorum" } }, "hybrid": { "technologies": [ "Hybrid trigger mechanism", "Automated monitoring with approval gateway", "Human override controller" ], "technologyProperties": { "triggerSource": "Automated + manual fallback", "automationLevel": "Automated with human review option", "overrideCapability": "Full human override" } } }, "prefillFrom": null, "briefSection": "Trigger and automation", "text": "How does automated triggers and fund releases currently work?", "ngoText": "How does automated triggers and fund releases currently work?" }, { "id": "timestamping-approach", "type": "select", "options": [ { "label": "Digital timestamping (each event anchored with tamper-proof proof)", "value": "on-chain" }, { "label": "Batch anchoring (events collected, periodically anchored)", "value": "batch-anchoring" }, { "label": "Trusted third-party timestamping authority", "value": "trusted-authority" }, { "label": "Not sure, need guidance on timestamping approach", "value": "guidance-needed" } ], "propertyMapping": { "on-chain": { "technologies": [ "On-chain timestamping service", "Event hash generation", "Timestamp verification API" ], "technologyProperties": { "timestampMethod": "Per-event Digital anchoring", "latency": "Near-instant (block confirmation time)", "legalAdmissibility": "Strong \u2014 independent blockchain proof" } }, "batch-anchoring": { "technologies": [ "Batch timestamping service", "Merkle tree aggregation", "Timestamp verification API" ], "technologyProperties": { "timestampMethod": "Periodic batch anchoring (hourly/daily)", "latency": "Batch interval", "legalAdmissibility": "Strong \u2014 Merkle proof to blockchain" } }, "trusted-authority": { "technologies": [ "Trusted timestamping authority integration", "RFC 3161 timestamping service", "Timestamp verification API" ], "technologyProperties": { "timestampMethod": "Trusted third-party authority", "latency": "Near-instant", "legalAdmissibility": "Varies by jurisdiction" } }, "guidance-needed": { "technologies": [ "Timestamping service framework", "Timestamp verification API" ], "technologyProperties": { "timestampMethod": "To be determined", "latency": "To be determined", "legalAdmissibility": "To be determined" } } }, "prefillFrom": null, "briefSection": "Evidence and timestamping", "text": "How is events and evidence currently timestamped for this solution?", "ngoText": "How is events and evidence currently timestamped for this solution?" } ], "complexityFactors": { "relationships": 2, "operationalChange": 2, "dataCompliance": 2 }, "suggestedCriteria": [ { "id": "SC-G091-ACTIVATE", "name": "Activation Speed & Reliability", "description": "This measures how quickly pre-positioned funds become available after a disaster declaration or activation event. The core value of pre-positioning is eliminating delays. If activation is slow, the pre-positioning adds cost without benefit.", "weight": 0.3, "ratingGuide": { "5": "Funds available within 2 hours of verified disaster declaration. Fully automated activation from declaration source to fund unlock. 99.9% uptime on activation pathway including during past disaster events.", "4": "Funds available within 12 hours. Automated activation with one manual verification step. High availability with documented uptime.", "3": "Funds available within 24-48 hours. Declaration triggers a workflow but release requires manual steps. Activation tested but not in live disaster conditions.", "2": "Funds available within 3-5 days. Declaration is informational \u2014 release follows standard approval chain. No acceleration over traditional funding.", "1": "No automated activation. Pre-positioned funds require the same manual processes as regular disbursement. Pre-positioning is in name only." } }, { "id": "SC-G091-DEPLOY", "name": "Multi-Location Deployment Reach", "description": "Funds can be pre-positioned and activated across multiple geographic locations simultaneously. Disasters rarely respect administrative boundaries. The system must support distributed fund pools with location-specific activation.", "weight": 0.2, "ratingGuide": { "5": "Supports pre-positioned funds across 10+ locations with independent activation per location. Location-specific fund pools, thresholds, and beneficiary lists. Proven in multi-country disaster responses.", "4": "Supports 5-10 locations with independent activation. Some shared configuration between locations. Tested in multi-location scenarios.", "3": "Supports 3-5 locations. Activation can be location-specific but fund pools may be shared. Limited multi-location testing.", "2": "Supports 1-2 locations. Activation is all-or-nothing \u2014 cannot release for one location without affecting others.", "1": "Single location only. No geographic distribution capability. Must redeploy for each new location." } }, { "id": "SC-G091-DECLARE", "name": "Declaration Source Integration", "description": "This measures how well the system integrates with official disaster declaration sources (government agencies, UN OCHA, IFRC). Relying on manual declaration forwarding introduces delays and potential errors.", "weight": 0.2, "ratingGuide": { "5": "Direct API integration with 2+ official declaration sources (e.g. GDACS, national disaster authorities, OCHA). Automated parsing of declaration severity levels. Supports multiple declaration formats and protocols.", "4": "API integration with one official source. Automated parsing. Can accept manual declarations as backup.", "3": "Structured intake of declarations (e.g. webhook or email parsing) but no direct API to official sources. Some manual verification needed.", "2": "Manual entry of disaster declarations into the system. No automated intake from official sources.", "1": "No integration with declaration sources. Activation relies entirely on internal decision-making with no external validation." } }, { "id": "SC-G091-SECURITY", "name": "Fund Security During Pre-Positioning", "description": "This measures how secure the pre-positioned funds are during the dormant period between setup and activation. Locked funds must be protected from unauthorised access, yet immediately accessible when activated.", "weight": 0.2, "ratingGuide": { "5": "Multi-signature or threshold-based access controls on pre-positioned funds. Smart contract escrow with time-locked or condition-locked release. Independent audit of fund security. Full transparency on fund status at all times.", "4": "Smart contract-based locking with multi-sig controls. Regular security audits. Real-time fund status dashboard.", "3": "Funds held in escrow with standard access controls. Periodic rather than real-time visibility. Annual security review.", "2": "Funds held in standard accounts with role-based access. No smart contract enforcement. Limited visibility into fund status.", "1": "Funds held with minimal controls. No escrow or locking mechanism. Risk of premature or unauthorised access." } }, { "id": "SC-G091-RESILIENCE", "name": "System Resilience During Crisis", "description": "The activation system remains operational when infrastructure is disrupted by the disaster itself. Systems that fail precisely when needed most provide false confidence.", "weight": 0.1, "ratingGuide": { "5": "Tested under simulated infrastructure failure (power, connectivity, DNS). Offline activation capability with sync-on-reconnect. Geographically distributed infrastructure. Documented disaster recovery with RTO under 1 hour.", "4": "Redundant infrastructure across 2+ regions. Degraded-mode operation possible without full connectivity. RTO under 4 hours.", "3": "Cloud-hosted with standard availability guarantees. No offline capability. Dependent on internet connectivity for activation.", "2": "Single-region deployment. No redundancy. Activation blocked if hosting region is affected by the disaster.", "1": "No disaster recovery planning. System availability during crisis events is unknown and untested." } } ], "procurement": { "marketMaturity": "emerging", "primaryMode": "integrator-led", "alternativeModes": [ "rfq" ], "reasoning": "Disaster fund pre-positioning has emerging product space.", "exampleProductCategories": [ "pre-positioning-platform", "disaster-finance-rails" ], "partnerChannels": [], "lastReviewed": "2026-05-01" } }, { "id": "UC-G-092", "name": "Anticipatory action fund release mechanisms", "category": "G", "subcategory": "Anticipatory Financing", "description": "Release funds before a crisis occurs, based on forecasts, and let funders and implementers check that the agreed trigger was really met.", "bCriteria": [ "B7", "B1", "B3" ], "requiredComponents": [ "trigger-mechanism", "fund-release-automation", "early-warning-system", "parametric-oracle" ], "conditionalComponents": [ "smart-contracts", "risk-modelling" ], "crossCategoryDependencies": [ "UC-G-098" ], "p2TriggerConditions": { "description": "Activated when P2 shows anticipatory action programmes with high automation and predictive capability requirements", "rangeSignals": [ "anticipatoryAction >=3", "automationLevel >=3", "predictiveCapability >=3" ] }, "contextFieldsTemplate": [ "predictive_model_accuracy", "lead_time_available", "fund_amount_thresholds", "activation_decision_maker", "beneficiary_identification_timing", "rapid_deployment_capacity", "false_alarm_tolerance" ], "implementationComplexity": "high", "examples": { "note": "Red Cross anticipatory action frameworks", "references": [ { "name": "Start Network anticipatory action", "url": "https://startnetwork.org/anticipation", "solved": "Pre-positioned funds released on forecast triggers (drought, flood) before disaster impact materialises; pioneered the operational model." }, { "name": "FAO Forecast-based Financing", "url": "https://www.fao.org/anticipatory-action", "solved": "Trigger-based release of pre-positioned funds for early agricultural intervention in drought-vulnerable regions." }, { "name": "WFP Anticipatory Action", "url": "https://www.wfp.org/anticipatory-action", "solved": "Multi-country anticipatory cash transfers triggered by climate forecasting models." } ] }, "propertyMapping": {}, "solutionQuestions": [ { "id": "lead-time-requirement", "type": "select", "options": [ { "label": "Long lead time (2-8 weeks): Crisis predicted well in advance", "value": "long-lead" }, { "label": "Medium lead time (1-2 weeks): Shorter warning window", "value": "medium-lead" }, { "label": "Very short lead time (24-72 hours): Near real-time", "value": "very-short-lead" } ], "prefillFrom": null, "briefSection": "Trigger and oracle", "propertyMapping": { "long-lead": { "technologies": [ "Seasonal climate models", "Strategic planning DAO" ], "technologyProperties": { "forecastAccuracy": "70-80%", "deploymentComplexity": "moderate" } }, "medium-lead": { "technologies": [ "Medium-range forecasts", "Rapid activation protocol" ], "technologyProperties": { "forecastAccuracy": "60-75%", "responseTime": "6-48 hours" } }, "very-short-lead": { "technologies": [ "Nowcasting", "Emergency protocol automation" ], "technologyProperties": { "forecastAccuracy": "50-65%", "pre-positioning": "required" } } }, "text": "What lead time is available for anticipatory action?", "ngoText": "What lead time is available for anticipatory action?" }, { "id": "beneficiary-identification", "type": "select", "options": [ { "label": "Pre-registered: Beneficiary list confirmed beforehand", "value": "pre-registered" }, { "label": "Dynamic identification: Beneficiaries identified post-trigger", "value": "dynamic" }, { "label": "Hybrid: Pre-registered with emergency flexibility", "value": "hybrid-id" } ], "prefillFrom": null, "briefSection": "Evidence capture", "propertyMapping": { "pre-registered": { "technologies": [ "Biometric registry", "Smart contract allowlist" ], "technologyProperties": { "verificationTime": "at-trigger", "updateFrequency": "quarterly" } }, "dynamic": { "technologies": [ "Rapid beneficiary assessment", "Mobile verification" ], "technologyProperties": { "assessmentTime": "24-72 hours", "verificationMethod": "field-teams" } }, "hybrid-id": { "technologies": [ "Core registry", "Rapid enrollment capability" ], "technologyProperties": { "baselineList": "verified-population", "emergencyAddition": "48-hour-process" } } }, "text": "When are beneficiaries identified in anticipatory process?", "ngoText": "When are beneficiaries identified in anticipatory process?" }, { "id": "false-alarm-management", "type": "select", "options": [ { "label": "Full refund: Unused funds returned to donor", "value": "full-refund" }, { "label": "Contingency reserve: Funds roll to next period/location", "value": "contingency-reserve" }, { "label": "Learning investment: Unused funds fund preparedness/training", "value": "learning-investment" } ], "prefillFrom": null, "briefSection": "Monitoring and alerts", "propertyMapping": { "full-refund": { "technologies": [ "Escrow smart contract", "Automatic reversal" ], "technologyProperties": { "refundMechanism": "automatic-48h-post-disarm", "feesApplied": "minimal" } }, "contingency-reserve": { "technologies": [ "Multi-sig DAO governance", "Reserve fund contract" ], "technologyProperties": { "rolloverMechanism": "discretionary", "holdingPeriod": "90-days" } }, "learning-investment": { "technologies": [ "Impact measurement DAO", "Earmarked fund transfer" ], "technologyProperties": { "reallocation": "community-voted", "reportingFrequency": "quarterly" } } }, "text": "If anticipatory action triggers but conditions improve and funds aren't needed, what should happen: return to donors, allocate to reserves for next period, repurpose to other programs, or keep as hedging buffer?", "ngoText": "If anticipatory action triggers but conditions improve and funds aren't needed, what should happen: return to donors, allocate to reserves for next period, repurpose to other programs, or keep as hedging buffer?" }, { "id": "trigger-transparency", "type": "select", "options": [ { "label": "Full transparency: All trigger data and decisions digital", "value": "full-transparent" }, { "label": "Selective transparency: Trigger logic public, data private", "value": "selective" }, { "label": "Confidential: Trigger process withheld to prevent manipulation", "value": "confidential" } ], "prefillFrom": null, "briefSection": "Monitoring and alerts", "propertyMapping": { "full-transparent": { "technologies": [ "Automated public events", "On-chain voting" ], "technologyProperties": { "dataPublicity": "unrestricted", "auditTrail": "immutable" } }, "selective": { "technologies": [ "Zero-knowledge proofs", "Encrypted data feeds" ], "technologyProperties": { "dataEncryption": "end-to-end", "logicTransparency": "full" } }, "confidential": { "technologies": [ "Trusted oracle", "Expert committee" ], "technologyProperties": { "accessControl": "multi-sig-only", "auditLog": "encrypted" } } }, "text": "How transparent is the anticipatory trigger process?", "ngoText": "How transparent is the anticipatory trigger process?" }, { "id": "trigger-mechanism", "type": "select", "options": [ { "label": "Oracle-based: external data feeds trigger automated actions", "value": "oracle-based" }, { "label": "Threshold-based: predefined conditions trigger automated release", "value": "threshold" }, { "label": "multi-party approval: requires multiple parties to authorise", "value": "multi-sig" }, { "label": "Hybrid: automated triggers with human override capability", "value": "hybrid" } ], "propertyMapping": { "oracle-based": { "technologies": [ "Oracle-based trigger mechanism", "External data feed connection", "Automated trigger executor" ], "technologyProperties": { "triggerSource": "External data oracle", "automationLevel": "Fully automated", "overrideCapability": "Emergency pause only" } }, "threshold": { "technologies": [ "Threshold-based trigger mechanism", "Condition monitoring engine", "Automated release controller" ], "technologyProperties": { "triggerSource": "Predefined thresholds", "automationLevel": "Fully automated above threshold", "overrideCapability": "Threshold adjustment by authorised parties" } }, "multi-sig": { "technologies": [ "Multi-signature trigger mechanism", "Approval workflow engine", "Multi-party authorisation service" ], "technologyProperties": { "triggerSource": "Multi-party approval", "automationLevel": "Human-initiated", "overrideCapability": "N/A \u2014 requires quorum" } }, "hybrid": { "technologies": [ "Hybrid trigger mechanism", "Automated monitoring with approval gateway", "Human override controller" ], "technologyProperties": { "triggerSource": "Automated + manual fallback", "automationLevel": "Automated with human review option", "overrideCapability": "Full human override" } } }, "prefillFrom": null, "briefSection": "Trigger and automation", "text": "How does automated triggers and fund releases currently work?", "ngoText": "How does automated triggers and fund releases currently work?" }, { "id": "early-warning-source", "type": "select", "options": [ { "label": "Weather and climate data feeds from national or global weather services", "value": "climate-data" }, { "label": "Conflict and security data feeds from monitoring services", "value": "conflict-data" }, { "label": "Health and epidemic data feeds from public health surveillance services", "value": "health-data" }, { "label": "Multiple data sources combined", "value": "multi-source" } ], "propertyMapping": { "climate-data": { "technologies": [ "Climate early warning system", "Weather data oracle", "Forecast-to-action pipeline" ], "technologyProperties": { "dataSource": "Meteorological services (global and national met offices)", "alertType": "Extreme weather, drought, flood forecasts", "leadTime": "3-14 days depending on event type" } }, "conflict-data": { "technologies": [ "Conflict early warning system", "Security data oracle", "Risk assessment pipeline" ], "technologyProperties": { "dataSource": "Conflict monitoring services", "alertType": "Escalation indicators, displacement risk", "leadTime": "Days to weeks depending on context" } }, "health-data": { "technologies": [ "Health early warning system", "Epidemic data oracle", "Health alert pipeline" ], "technologyProperties": { "dataSource": "Health surveillance (WHO, national health authorities)", "alertType": "Disease outbreak, epidemic threshold", "leadTime": "Days to weeks" } }, "multi-source": { "technologies": [ "Multi-source early warning system", "Data aggregation oracle", "Compound risk assessment engine" ], "technologyProperties": { "dataSource": "Multiple feeds (climate + conflict + health)", "alertType": "Compound risk assessment", "leadTime": "Varies by data source" } } }, "prefillFrom": null, "briefSection": "Early warning", "text": "What data sources should feed the early warning system?", "ngoText": "What data sources should feed the early warning system?" } ], "complexityFactors": { "relationships": 4, "operationalChange": 3, "dataCompliance": 2 }, "suggestedCriteria": [ { "id": "SC-G092-PREDICT", "name": "Predictive Model Integration Quality", "description": "This measures how effectively the system integrates predictive models to trigger pre-disaster fund releases. The lead time between prediction and impact determines whether anticipatory action is possible at all.", "weight": 0.25, "ratingGuide": { "5": "Integrates with established predictive models (e.g. global flood forecasting for floods, IRI for drought). Documented lead times of 7+ days for primary hazards. Model accuracy metrics published and above 70% hit rate. Supports ensemble model inputs.", "4": "Integrates with 1-2 established models. Lead times of 3-7 days. Accuracy metrics tracked internally. Single model input per hazard.", "3": "Accepts predictive data but does not directly integrate with modelling platforms. Lead time depends on manual data input timing. Accuracy tracking informal.", "2": "Uses simple threshold-based predictions rather than established models. Limited lead time. No accuracy tracking.", "1": "No predictive capability. System is reactive \u2014 triggers only after impact is observed. Not suitable for anticipatory action." } }, { "id": "SC-G092-FALSEALARM", "name": "False Alarm Cost Management", "description": "This looks at how the system balances the cost of acting on false alarms against the cost of missing real events. Anticipatory action inherently involves uncertainty. The system must support configurable risk tolerance and track false alarm costs.", "weight": 0.2, "ratingGuide": { "5": "Configurable false alarm tolerance per scenario (e.g. 'act on 60% probability'). Tracks cumulative false alarm costs and acts-in-vain ratios. Decision-support dashboard showing cost-benefit of different thresholds. Institutional learning loop.", "4": "Configurable probability thresholds. Tracks false alarms per scenario. Reporting on acts-in-vain available but not real-time.", "3": "Fixed probability thresholds with manual override capability. False alarms recorded but not systematically analysed.", "2": "Binary trigger with no probability weighting. No false alarm tracking. No mechanism to adjust risk tolerance.", "1": "No false alarm consideration. System either fires or doesn't with no nuance. No record of past trigger accuracy." } }, { "id": "SC-G092-RAPID", "name": "Rapid Beneficiary Identification & Disbursement", "description": "This measures how quickly intended beneficiaries can be identified and funds disbursed once a pre-disaster trigger fires. Anticipatory action often operates in windows of days. Beneficiary targeting and disbursement must be pre-planned and fast.", "weight": 0.25, "ratingGuide": { "5": "Pre-registered beneficiary lists linked to trigger scenarios. Disbursement begins within hours of trigger. Supports mobile money, cash agents, and voucher modalities. Beneficiary verification built into disbursement flow.", "4": "Pre-registered lists available. Disbursement within 24 hours. Supports 2+ disbursement modalities. Basic verification.", "3": "Beneficiary lists exist but require manual activation. Disbursement within 48-72 hours. Single disbursement modality.", "2": "Beneficiary identification begins only after trigger fires. Disbursement takes 5+ days. Manual processes throughout.", "1": "No pre-registered beneficiaries. Targeting and disbursement follow standard non-anticipatory timelines. No speed advantage." } }, { "id": "SC-G092-HITL", "name": "Human-in-the-Loop Decision Support", "description": "The system supports human oversight of automated trigger decisions without becoming a bottleneck. In anticipatory action, fully automated releases carry reputational risk, but slow approvals defeat the purpose.", "weight": 0.15, "ratingGuide": { "5": "Tiered approval model: small releases automated, larger releases require rapid human confirmation with clear SLAs (e.g. 2-hour response window). Escalation paths if approver is unavailable. Decision context automatically compiled for approvers.", "4": "Human confirmation step with pre-compiled decision brief. Clear escalation path. Approval SLA defined but not enforced by system.", "3": "Human approval required for all releases. System provides data but no compiled decision brief. No escalation if approver delays.", "2": "Human approval required via email or manual process. No decision support. Approval delays directly delay release.", "1": "No structured approval process. Either fully automated with no oversight, or fully manual with no system support." } }, { "id": "SC-G092-COORD", "name": "Humanitarian Coordination System Interoperability", "description": "The system can share trigger alerts and release data with humanitarian coordination platforms (OCHA, cluster system, CERF). Anticipatory action operates within broader humanitarian response. Isolated systems create coordination gaps.", "weight": 0.15, "ratingGuide": { "5": "API-based integration with OCHA coordination platforms. Automated notification to relevant cluster leads on trigger activation. Data formatted for CERF/DREF reporting. Supports IATI standard for fund flow reporting.", "4": "Structured data export compatible with OCHA formats. Manual notification to clusters with standardised templates. Supports one reporting standard.", "3": "Data exportable in standard formats (CSV, JSON) but no direct integration. Cluster notification is manual and ad hoc.", "2": "Data export available but requires custom formatting. No standard humanitarian data formats supported.", "1": "No data export or integration capability. Trigger and release information siloed within the system." } } ], "procurement": { "marketMaturity": "nascent", "primaryMode": "integrator-led", "alternativeModes": [ "consortium" ], "reasoning": "Anticipatory action mechanisms are research-stage.", "exampleProductCategories": [ "anticipatory-action-platform", "parametric-trigger-rails" ], "partnerChannels": [], "lastReviewed": "2026-05-01" } }, { "id": "UC-G-093", "name": "Climate adaptation financing", "category": "G", "subcategory": "Climate Finance", "description": "Track climate adaptation funding from donor to project, with results that funders can check for themselves rather than taking your reports on trust.", "bCriteria": [ "B1", "B3", "B6" ], "requiredComponents": [ "evidence-platform", "data-integrity-layer", "parametric-oracle", "timestamping-service" ], "conditionalComponents": [ "smart-contracts", "risk-modelling" ], "crossCategoryDependencies": [ "UC-I-114", "UC-I-114" ], "p2TriggerConditions": { "description": "Activated when P2 shows climate adaptation financing needs with impact measurement requirements and regulatory obligations", "rangeSignals": [ "climateAdaptation >=3", "impactMeasurement >=3", "regulatoryRequired = true" ] }, "contextFieldsTemplate": [ "climate_risk_assessment", "adaptation_project_types", "monitoring_frequency", "resilience_metric_definitions", "fund_sources", "geographic_scope", "community_participation_level" ], "implementationComplexity": "high", "examples": { "note": "Green Climate Fund methodology integration", "references": [ { "name": "Adaptation Fund (UNFCCC)", "url": "https://www.adaptation-fund.org", "solved": "Climate adaptation finance for developing countries with monitoring and verification requirements." }, { "name": "Green Climate Fund", "url": "https://www.greenclimate.fund", "solved": "Largest dedicated climate finance fund with results-based disbursement model." }, { "name": "Climate Bonds Initiative", "url": "https://www.climatebonds.net", "solved": "Standards body for verifiable green bond issuance, defining the integrity criteria climate financing tools must meet." } ] }, "propertyMapping": {}, "solutionQuestions": [ { "id": "climate-risk-types", "type": "select", "options": [ { "label": "Slow-onset risks (sea-level rise, desertification, glacier melt)", "value": "slow-onset" }, { "label": "Acute weather events (droughts, floods, heat waves)", "value": "acute-weather" }, { "label": "Compound climate risks (multi-hazard cascades)", "value": "compound-risks" } ], "prefillFrom": null, "briefSection": "Evidence capture", "propertyMapping": { "slow-onset": { "technologies": [ "Satellite monitoring", "Parametric indexing" ], "technologyProperties": { "monitoringFrequency": "annual", "dataSource": "Public climate data programmes and IPCC assessments" } }, "acute-weather": { "technologies": [ "Real-time weather feeds", "Parametric triggers" ], "technologyProperties": { "updateFrequency": "daily", "thresholdMetric": "SPI/NDVI" } }, "compound-risks": { "technologies": [ "Multi-factor risk aggregation", "Machine learning models" ], "technologyProperties": { "riskFactors": "3+", "interdependencyModel": "correlation-based" } } }, "text": "Which climate risks are you targeting for adaptation financing?", "ngoText": "Which climate risks are you targeting for adaptation financing?" }, { "id": "adaptation-project-monitoring", "type": "select", "options": [ { "label": "On-ground monitoring: Field teams + community reporting", "value": "on-ground" }, { "label": "Satellite monitoring: Remote sensing + change detection", "value": "satellite" }, { "label": "Hybrid: Satellite baseline + community verification", "value": "hybrid-monitoring" } ], "prefillFrom": null, "briefSection": "Monitoring and alerts", "propertyMapping": { "on-ground": { "technologies": [ "Mobile data collection", "Decentralised evidence vault" ], "technologyProperties": { "reportingFrequency": "monthly", "verificationMethod": "GPS-timestamped" } }, "satellite": { "technologies": [ "Open satellite imagery", "Deep learning classification" ], "technologyProperties": { "updateFrequency": "10-day cycle", "resolution": "10-20 meters" } }, "hybrid-monitoring": { "technologies": [ "Satellite + decentralised storage", "Community DAO validation" ], "technologyProperties": { "baselineFrequency": "quarterly-satellite", "verificationFrequency": "monthly-ground" } } }, "text": "How are adaptation project outcomes monitored and verified?", "ngoText": "How are adaptation project outcomes monitored and verified?" }, { "id": "resilience-metrics", "type": "select", "options": [ { "label": "Outcome-based: Community resilience scores (survey-driven)", "value": "outcome-based" }, { "label": "Impact-based: Ecosystem metrics (NDVI, soil health, water)", "value": "impact-based" }, { "label": "Process-based: Activity completion and resource uptake", "value": "process-based" } ], "prefillFrom": null, "briefSection": "Reporting and audit", "propertyMapping": { "outcome-based": { "technologies": [ "RIMA-II framework", "Blockchain survey DAO" ], "technologyProperties": { "surveyFrequency": "annual", "sample": "statistical" } }, "impact-based": { "technologies": [ "Satellite indices", "IoT soil sensors" ], "technologyProperties": { "measurementInterval": "monthly", "historicalBaseline": "3-5 years" } }, "process-based": { "technologies": [ "Automated progress tracking", "Tokenized milestones" ], "technologyProperties": { "trackingGranularity": "weekly", "auditTrail": "automatic" } } }, "text": "What resilience metrics define project success?", "ngoText": "What resilience metrics define project success?" }, { "id": "mrv-mechanism", "type": "select", "options": [ { "label": "Centralized: Single implementing organization reports", "value": "centralized" }, { "label": "distributed: Multiple verification nodes validate", "value": "decentralized" }, { "label": "Open MRV: Community validation + transparent digital ledger record", "value": "open-mrv" } ], "prefillFrom": null, "briefSection": "Reporting and audit", "propertyMapping": { "centralized": { "technologies": [ "Organization dashboard", "Annual reporting" ], "technologyProperties": { "verificationParty": "independent-auditor", "reportingFrequency": "annual" } }, "decentralized": { "technologies": [ "Oracle network", "Consensus verification" ], "technologyProperties": { "validatorCount": "3-5", "approvalQuorum": "66%" } }, "open-mrv": { "technologies": [ "Public smart contract", "Community DAO verification" ], "technologyProperties": { "transparency": "full", "participationLevel": "permissionless" } } }, "text": "What MRV (Monitoring, Reporting, Verification) structure is employed?", "ngoText": "What MRV (Monitoring, Reporting, Verification) structure is employed?" }, { "id": "climate-data-integration", "type": "select", "options": [ { "label": "IPCC/UNFCCC data feeds", "value": "ipcc-unfccc" }, { "label": "National meteorological/climate agencies", "value": "national-agencies" }, { "label": "Peer-reviewed climate datasets from public climate programmes", "value": "peer-reviewed" } ], "prefillFrom": null, "briefSection": "Data integrity", "propertyMapping": { "ipcc-unfccc": { "technologies": [ "IPCC API integration", "UNFCCC reporting standards" ], "technologyProperties": { "authorityType": "official-UN", "updateCycle": "annual-assessment" } }, "national-agencies": { "technologies": [ "National weather API", "Climate model access" ], "technologyProperties": { "jurisdictionSpecific": "true", "dataFreshness": "real-time" } }, "peer-reviewed": { "technologies": [ "Public open climate data", "National weather service feeds" ], "technologyProperties": { "qualityAssurance": "scientific-peer-review", "updateFrequency": "variable" } } }, "text": "What climate data sources does your adaptation monitoring currently use?", "ngoText": "What climate data sources does your adaptation monitoring currently use?" }, { "id": "timestamping-approach", "type": "select", "options": [ { "label": "Digital timestamping (each event anchored with tamper-proof proof)", "value": "on-chain" }, { "label": "Batch anchoring (events collected, periodically anchored)", "value": "batch-anchoring" }, { "label": "Trusted third-party timestamping authority", "value": "trusted-authority" }, { "label": "Not sure, need guidance on timestamping approach", "value": "guidance-needed" } ], "propertyMapping": { "on-chain": { "technologies": [ "On-chain timestamping service", "Event hash generation", "Timestamp verification API" ], "technologyProperties": { "timestampMethod": "Per-event Digital anchoring", "latency": "Near-instant (block confirmation time)", "legalAdmissibility": "Strong \u2014 independent blockchain proof" } }, "batch-anchoring": { "technologies": [ "Batch timestamping service", "Merkle tree aggregation", "Timestamp verification API" ], "technologyProperties": { "timestampMethod": "Periodic batch anchoring (hourly/daily)", "latency": "Batch interval", "legalAdmissibility": "Strong \u2014 Merkle proof to blockchain" } }, "trusted-authority": { "technologies": [ "Trusted timestamping authority integration", "RFC 3161 timestamping service", "Timestamp verification API" ], "technologyProperties": { "timestampMethod": "Trusted third-party authority", "latency": "Near-instant", "legalAdmissibility": "Varies by jurisdiction" } }, "guidance-needed": { "technologies": [ "Timestamping service framework", "Timestamp verification API" ], "technologyProperties": { "timestampMethod": "To be determined", "latency": "To be determined", "legalAdmissibility": "To be determined" } } }, "prefillFrom": null, "briefSection": "Evidence and timestamping", "text": "How is events and evidence currently timestamped for this solution?", "ngoText": "How is events and evidence currently timestamped for this solution?" } ], "complexityFactors": { "relationships": 3, "operationalChange": 3, "dataCompliance": 2 }, "suggestedCriteria": [ { "id": "SC-G093-OUTCOME", "name": "Resilience Outcome Measurement Capability", "description": "The system can define, track, and verify climate resilience outcomes over time. Climate adaptation is measured in years and decades. The platform must support long-horizon outcome tracking with verifiable evidence.", "weight": 0.25, "ratingGuide": { "5": "Supports custom resilience metric definitions aligned with GCF results frameworks. Automated data collection from IoT sensors, satellite imagery, or field surveys. Longitudinal tracking across multi-year project cycles. Outcome data cryptographically timestamped.", "4": "Pre-built resilience metric templates. Supports automated and manual data collection. Multi-year tracking. Timestamping on key milestones.", "3": "Basic metric tracking with manual data entry. Supports annual reporting cycles. No automated data collection. Limited longitudinal analysis.", "2": "Tracks financial disbursement but not adaptation outcomes. Reporting is activity-based rather than outcome-based.", "1": "No outcome tracking capability. System handles fund flow only with no connection to climate results." } }, { "id": "SC-G093-CLIMATE", "name": "Climate Data & Risk Assessment Integration", "description": "This measures how well the platform integrates with climate risk data sources to inform financing decisions and track environmental change. Adaptation financing must be grounded in climate science as well as financial flows.", "weight": 0.2, "ratingGuide": { "5": "Integrates with satellite data providers, national climate services, and global datasets (e.g. CMIP6 projections). Supports overlay of climate risk maps with project locations. Automated risk re-assessment on new data.", "4": "Integrates with 1-2 climate data sources. Risk mapping available. Periodic rather than automated risk updates.", "3": "Climate risk data can be uploaded manually. Basic mapping capability. No direct integration with climate data providers.", "2": "Climate risk referenced in project descriptions but not systematically tracked or integrated into the platform.", "1": "No climate data integration. Financing decisions and tracking are climate-blind." } }, { "id": "SC-G093-DONOR", "name": "Donor & Regulatory Reporting Compliance", "description": "The platform generates reports aligned with major climate fund requirements (GCF, GEF, Adaptation Fund) and emerging regulatory frameworks. Climate finance faces intense scrutiny. Reporting that does not meet donor standards blocks future funding.", "weight": 0.25, "ratingGuide": { "5": "Built-in report templates for GCF, GEF, and Adaptation Fund. Supports IATI and OECD DAC Rio marker tagging. Automated generation of results frameworks, disbursement reports, and audit-ready documentation.", "4": "Report templates for one major climate fund. Supports IATI tagging. Semi-automated report generation with manual review.", "3": "Generic financial reporting with climate finance fields available. Reports require significant manual adaptation for specific fund requirements.", "2": "Standard financial reporting only. No climate-specific reporting fields or templates. Manual report creation for each donor.", "1": "No reporting capability beyond basic transaction records. All donor reporting done outside the system." } }, { "id": "SC-G093-COMMUNITY", "name": "Community Participation Verification", "description": "The platform can capture and verify community participation in adaptation project design and implementation. Effective climate adaptation is locally led. Verifiable evidence of community engagement is increasingly required by funders.", "weight": 0.15, "ratingGuide": { "5": "Supports structured community consultation records with participant verification (e.g. digital attendance, consent records). Links community input to project design decisions with audit trail. Supports local language documentation.", "4": "Community consultation records captured with basic verification. Linkage to project decisions documented. Single-language support.", "3": "Community participation recorded as narrative reports. No participant-level verification. Limited traceability to project decisions.", "2": "Community participation claimed in reports but not systematically documented or verified in the platform.", "1": "No community participation tracking. Platform focused entirely on financial flows with no stakeholder engagement features." } }, { "id": "SC-G093-LONGTERM", "name": "Multi-Year Project Lifecycle Support", "description": "The platform can manage adaptation projects across their full lifecycle, from proposal through multi-year implementation to long-term monitoring. Climate adaptation projects typically span 5-10+ years.", "weight": 0.15, "ratingGuide": { "5": "Supports full project lifecycle from proposal to 10+ year monitoring. Phase-gated disbursement tied to milestone verification. Adaptive management features allow mid-course corrections with full audit trail.", "4": "Supports proposal through 5+ year implementation. Milestone-based disbursement. Some adaptive management capability.", "3": "Supports project implementation up to 3 years. Annual reporting cycles. Disbursement scheduling but not milestone-gated.", "2": "Supports single-year project cycles. No multi-year tracking. Each year essentially treated as a new project.", "1": "No project lifecycle management. Platform handles individual transactions with no project framing." } } ], "procurement": { "marketMaturity": "nascent", "primaryMode": "integrator-led", "alternativeModes": [ "consortium" ], "reasoning": "Climate adaptation financing platforms emerging.", "exampleProductCategories": [ "climate-finance-platform", "adaptation-funding-rails" ], "partnerChannels": [], "lastReviewed": "2026-05-01" } }, { "id": "UC-G-094", "name": "Conflict-sensitive resource allocation", "category": "G", "subcategory": "Conflict Management", "description": "Record how resources were shared among groups in conflict areas, and show that each decision was made to avoid doing harm.", "bCriteria": [ "B1", "B3", "B6" ], "requiredComponents": [ "evidence-platform", "data-integrity-layer", "audit-trail" ], "conditionalComponents": [ "smart-contracts", "timestamping-service" ], "crossCategoryDependencies": [ "UC-H-106", "UC-J-121" ], "p2TriggerConditions": { "description": "Activated when P2 shows conflict-affected contexts requiring do-no-harm compliance and multi-stakeholder resource allocation", "rangeSignals": [ "conflictContext >=3", "doNoHarmRequired = true", "multiStakeholder >=2" ] }, "contextFieldsTemplate": [ "conflict_sensitivity_framework", "actor_mapping_completeness", "geographic_conflict_intensity", "do_no_harm_screening_frequency", "stakeholder_consultation_process", "grievance_mechanism_availability" ], "implementationComplexity": "medium", "examples": { "note": "Combines with HLP and land disputes tracking", "references": [ { "name": "ICRC conflict programmes", "url": "https://www.icrc.org", "solved": "Reference standard for conflict-sensitive resource allocation across active and post-conflict environments." }, { "name": "Norwegian Refugee Council", "url": "https://www.nrc.no", "solved": "Conflict-sensitive aid delivery in Syria, Ukraine, Yemen with documented allocation methodologies." }, { "name": "Mercy Corps Conflict & Stability", "url": "https://www.mercycorps.org/our-work/conflict-stability", "solved": "Conflict-sensitive programming framework with built-in do-no-harm verification." } ] }, "propertyMapping": {}, "solutionQuestions": [ { "id": "conflict-sensitivity-framework", "type": "select", "options": [ { "label": "Do No Harm (CDA) framework", "value": "do-no-harm" }, { "label": "OECD DAC conflict sensitivity guidelines", "value": "oecd-dac" }, { "label": "Locally-developed framework (community-specific)", "value": "local-framework" } ], "prefillFrom": null, "briefSection": "Evidence capture", "propertyMapping": { "do-no-harm": { "technologies": [ "CDA checklist automation", "Risk flag contract" ], "technologyProperties": { "riskCategories": "10+", "assessmentStandard": "internationally-recognized" } }, "oecd-dac": { "technologies": [ "OECD guideline tracker", "Multi-sig governance" ], "technologyProperties": { "complianceCheckpoints": "3", "riskLevel": "high-medium-low" } }, "local-framework": { "technologies": [ "Custom Automated logic", "Community DAO" ], "technologyProperties": { "frameworkOrigin": "participatory-design", "updateCycle": "annual-review" } } }, "text": "What conflict sensitivity approach currently guides your allocation decisions?", "ngoText": "What conflict sensitivity approach currently guides your allocation decisions?" }, { "id": "do-no-harm-screening", "type": "select", "options": [ { "label": "Pre-implementation: One-time baseline assessment", "value": "pre-implementation" }, { "label": "Ongoing: Quarterly or monthly reviews", "value": "ongoing-periodic" }, { "label": "Adaptive: Triggered by conflict escalation alerts", "value": "adaptive-trigger" } ], "prefillFrom": null, "briefSection": "Monitoring and alerts", "propertyMapping": { "pre-implementation": { "technologies": [ "Initial risk assessment", "Blockchain record" ], "technologyProperties": { "screenerQualification": "trained-staff", "documentationLevel": "high" } }, "ongoing-periodic": { "technologies": [ "Recurring assessment DAO", "Timestamped evidence" ], "technologyProperties": { "reviewFrequency": "quarterly", "updateMechanism": "automated-reminder" } }, "adaptive-trigger": { "technologies": [ "Conflict monitor feed", "Dynamic protocol" ], "technologyProperties": { "triggerSources": "news-API-security-data", "immediateReview": "true" } } }, "text": "When and how frequently is do-no-harm screening conducted?", "ngoText": "When and how frequently is do-no-harm screening conducted?" }, { "id": "stakeholder-mapping", "type": "select", "options": [ { "label": "Basic: Direct beneficiaries + implementing partner", "value": "basic-stakeholders" }, { "label": "Extended: All community members + local authorities", "value": "extended-stakeholders" }, { "label": "Comprehensive: All actors including armed groups/spoilers", "value": "comprehensive-stakeholders" } ], "prefillFrom": null, "briefSection": "Evidence capture", "propertyMapping": { "basic-stakeholders": { "technologies": [ "Beneficiary registry", "Partner verification" ], "technologyProperties": { "consultationLevel": "direct-beneficiary", "documentationMethod": "timestamped-records" } }, "extended-stakeholders": { "technologies": [ "Community DAO", "Government liaison" ], "technologyProperties": { "participationScope": "town-hall-level", "votingMechanism": "consensus-driven" } }, "comprehensive-stakeholders": { "technologies": [ "Multi-actor engagement DAO", "Conflict analysis feed" ], "technologyProperties": { "inclusivity": "all-political-actors", "confidentiality": "anonymized-where-needed" } } }, "text": "How many stakeholder groups need to be involved in approval or consultation for allocation decisions?", "ngoText": "How many stakeholder groups need to be involved in approval or consultation for allocation decisions?" }, { "id": "grievance-mechanism", "type": "select", "options": [ { "label": "Centralized: Submit complaints to implementing org", "value": "centralized-grievance" }, { "label": "digital: digital grievance automated rules", "value": "blockchain-grievance" }, { "label": "Community-mediated: Local reconciliation + escalation path", "value": "community-grievance" } ], "prefillFrom": null, "briefSection": "Reporting and audit", "propertyMapping": { "centralized-grievance": { "technologies": [ "Complaint hotline", "SMS feedback" ], "technologyProperties": { "responseTime": "30-days", "anonymity": "supported" } }, "blockchain-grievance": { "technologies": [ "Grievance smart contract", "Decentralised evidence storage" ], "technologyProperties": { "transparency": "case-tracking-Digital", "immutability": "tamper-proof-record" } }, "community-grievance": { "technologies": [ "Community DAO mediation", "Escalation protocol" ], "technologyProperties": { "firstInstance": "community-elders", "appealLevel": "independent-review" } } }, "text": "What grievance and accountability mechanism is in place?", "ngoText": "What grievance and accountability mechanism is in place?" }, { "id": "conflict-alloc-participant-count", "type": "select", "options": [ { "label": "2\u20135 parties", "value": "small" }, { "label": "6\u201315 parties", "value": "medium" }, { "label": "16\u201350 parties", "value": "large" }, { "label": "Over 50 parties", "value": "enterprise" } ], "propertyMapping": { "small": { "technologies": [ "Simple shared ledger" ], "technologyProperties": { "consensusComplexity": "Low", "governanceModel": "Direct" } }, "medium": { "technologies": [ "Permissioned network", "Role-based access" ], "technologyProperties": { "consensusComplexity": "Medium", "governanceModel": "Committee-based" } }, "large": { "technologies": [ "Scalable permissioned network", "Delegated consensus" ], "technologyProperties": { "consensusComplexity": "High", "governanceModel": "Delegated" } }, "enterprise": { "technologies": [ "Enterprise consortium platform", "Federated consensus" ], "technologyProperties": { "consensusComplexity": "Very high", "governanceModel": "Federated" } } }, "prefillFrom": null, "briefSection": "Governance mechanism", "text": "How many organisations or stakeholders participate in conflict-sensitive allocation?", "ngoText": "How many organisations or stakeholders participate in conflict-sensitive allocation?" }, { "id": "evidence-platform-approach", "type": "select", "options": [ { "label": "distributed storage/distributed storage with digital ledger tamper-proof verification", "value": "ipfs-anchored" }, { "label": "Cloud storage with periodic digital ledger proof checkpoints", "value": "cloud-anchored" }, { "label": "Digital metadata with separate encrypted file storage", "value": "hybrid-storage" }, { "label": "Not sure, need guidance on evidence storage", "value": "guidance-needed" } ], "propertyMapping": { "ipfs-anchored": { "technologies": [ "Decentralised-storage evidence platform", "Data integrity verification layer", "Content-addressed storage service" ], "technologyProperties": { "storageMethod": "Decentralised storage network", "integrityProof": "Content hash on blockchain", "redundancy": "Distributed across multiple nodes" } }, "cloud-anchored": { "technologies": [ "Cloud evidence platform", "Data integrity verification layer", "Periodic proof checkpoint service" ], "technologyProperties": { "storageMethod": "Commercial cloud storage", "integrityProof": "Periodic Merkle root on blockchain", "redundancy": "Cloud provider redundancy" } }, "hybrid-storage": { "technologies": [ "Hybrid evidence platform", "Data integrity verification layer", "Encrypted off-chain storage" ], "technologyProperties": { "storageMethod": "Digital metadata + encrypted off-chain files", "integrityProof": "Digital hash per document", "redundancy": "Configurable" } }, "guidance-needed": { "technologies": [ "Evidence platform framework", "Data integrity verification layer" ], "technologyProperties": { "storageMethod": "To be determined", "integrityProof": "To be determined", "redundancy": "To be determined" } } }, "prefillFrom": null, "briefSection": "Evidence and data integrity", "text": "How is evidence and documents currently stored and verified?", "ngoText": "How is evidence and documents currently stored and verified?" }, { "id": "audit-trail-approach", "type": "select", "options": [ { "label": "Donors and external auditors need to independently verify any action at any time", "value": "donors-and-external-auditors-need-to-ind" }, { "label": "External auditors check periodically: summary reports and spot-checks are sufficient", "value": "external-auditors-check-periodically-sum" }, { "label": "Key milestones and approvals need independent verification; routine actions just need internal records", "value": "key-milestones-and-approvals-need-indepe" }, { "label": "Internal team records are sufficient: we mainly need our own staff to be able to look back", "value": "internal-team-records-are-sufficient-we-" }, { "label": "Not sure, need guidance on audit requirements", "value": "not-sure-need-guidance-on-audit-requirem" } ], "propertyMapping": { "full-immutable": { "technologies": [ "Immutable audit trail", "On-chain event logging", "Audit trail verification service" ], "technologyProperties": { "auditGranularity": "Every action", "storageApproach": "Full on-chain logging", "tamperEvidence": "Cryptographic hash chain" } }, "key-events": { "technologies": [ "Milestone-based audit trail", "Approval chain logger", "Audit trail verification service" ], "technologyProperties": { "auditGranularity": "Key milestones and approvals only", "storageApproach": "Selective on-chain logging", "tamperEvidence": "Merkle root anchoring" } }, "hybrid": { "technologies": [ "Hybrid audit trail system", "Off-chain storage with hash anchoring", "Audit trail verification service" ], "technologyProperties": { "auditGranularity": "Metadata on-chain, full records off-chain", "storageApproach": "Decentralised/off-chain storage with on-chain hash proofs", "tamperEvidence": "Hash anchoring to blockchain" } }, "guidance-needed": { "technologies": [ "Audit trail framework", "Audit trail verification service" ], "technologyProperties": { "auditGranularity": "To be determined during solution design", "storageApproach": "To be determined", "tamperEvidence": "To be determined" } } }, "prefillFrom": null, "briefSection": "Audit and evidence", "text": "What level of audit trail does this solution require?", "ngoText": "What level of audit trail does this solution require?", "hidden": true, "question": "Who needs to verify that actions in this system happened correctly, and how easily should they be able to check?" } ], "complexityFactors": { "relationships": 3, "operationalChange": 3, "dataCompliance": 4 }, "suggestedCriteria": [ { "id": "SC-G094-DNH", "name": "Do-No-Harm Screening Capability", "description": "The system can systematically screen resource allocation decisions for conflict sensitivity. In conflict-affected contexts, resource distribution itself can fuel or mitigate conflict. Screening must be structured, not ad hoc.", "weight": 0.25, "ratingGuide": { "5": "Built-in do-no-harm screening framework triggered automatically on each allocation decision. Configurable screening criteria per conflict context. Flags high-risk allocations for review. Full audit trail of screening decisions and overrides.", "4": "Structured screening triggered on allocations above a threshold. Configurable criteria. Flagging system. Screening results recorded.", "3": "Screening checklist available but manually initiated. Standard criteria not customisable per context. Results recorded as free text.", "2": "Screening is a manual process outside the system. Platform records allocation decisions but not the conflict sensitivity analysis.", "1": "No do-no-harm screening capability. Allocation decisions made without systematic conflict sensitivity consideration." } }, { "id": "SC-G094-ACTOR", "name": "Conflict Actor Mapping & Analysis", "description": "The platform supports mapping of conflict actors, power dynamics, and relationships to inform allocation decisions. Resource allocation in conflict contexts requires understanding who benefits, who is excluded, and what perceptions this creates.", "weight": 0.2, "ratingGuide": { "5": "Integrated actor mapping with relationship visualization. Links actor analysis to allocation zones. Supports regular updates as conflict dynamics shift. Restricted access controls on sensitive actor data.", "4": "Actor mapping capability with basic relationship tracking. Links to allocation areas. Periodic update workflow. Access controls in place.", "3": "Actor data captured as structured records but no mapping or relationship visualization. Manual linkage to allocations.", "2": "Actor information recorded in narrative form. No structured data. No connection to allocation decisions in the system.", "1": "No actor mapping or analysis capability. Allocation decisions uninformed by conflict actor dynamics." } }, { "id": "SC-G094-AUDIT", "name": "Allocation Audit Trail Integrity", "description": "Allocation decisions, their rationale, and any subsequent modifications are recorded in a tamper-evident audit trail. In conflict settings, allegations of bias in resource distribution are common: immutable records protect programme integrity.", "weight": 0.25, "ratingGuide": { "5": "Every allocation decision recorded with rationale, approver, timestamp, and conflict sensitivity screening result. Tamper-evident logging (hash-chained or blockchain-anchored). Modification history preserved. Audit trail exportable for independent review.", "4": "Allocation decisions logged with rationale and approver. Tamper-evident storage. Modification history available. Export capability.", "3": "Decisions logged with basic metadata. Standard database storage (not tamper-evident). Some modification tracking.", "2": "Allocation amounts recorded but not decision rationale or screening results. No tamper evidence. Limited modification history.", "1": "No audit trail. Allocation decisions not systematically recorded. No ability to demonstrate fairness of past decisions." } }, { "id": "SC-G094-GRIEVANCE", "name": "Grievance Mechanism Integration", "description": "The platform supports a grievance mechanism for communities to report perceived unfairness in resource allocation. In conflict-affected settings, a functioning grievance channel is both an accountability tool and an early warning system.", "weight": 0.15, "ratingGuide": { "5": "Built-in grievance intake (multiple channels: SMS, web, in-person digitisation). Grievances linked to specific allocations. Tracking workflow from intake to resolution. Anonymity options for reporters in high-risk contexts.", "4": "Grievance intake via web form linked to allocations. Tracking workflow. Anonymity option available.", "3": "Grievance recording capability but not linked to specific allocations. Basic tracking. No anonymity features.", "2": "Grievances recorded externally and referenced in the system as attachments. No structured intake or tracking.", "1": "No grievance mechanism. No channel for communities to raise concerns about allocation decisions." } }, { "id": "SC-G094-ADAPTIVE", "name": "Adaptive Allocation Logic", "description": "Allocation rules can be adjusted in response to changing conflict dynamics without rebuilding the system. Conflict contexts are inherently volatile. Allocation criteria that were appropriate last month may be harmful this month.", "weight": 0.15, "ratingGuide": { "5": "Allocation rules configurable by authorised users without developer intervention. Supports scenario modelling before changes go live. Change history tracked with rationale. Rules can be paused instantly if a new conflict event occurs.", "4": "Allocation rules adjustable through admin interface. Preview capability before changes. Change history recorded.", "3": "Allocation rules can be changed but require technical support. No preview or modelling. Changes recorded.", "2": "Allocation logic hardcoded with limited parameterisation. Changes require development cycle. Poor change documentation.", "1": "Fixed allocation logic. No ability to adapt to changing conditions. System must be rebuilt for new conflict dynamics." } } ], "securityTier": "B", "procurement": { "marketMaturity": "nascent", "primaryMode": "integrator-led", "alternativeModes": [ "consortium" ], "reasoning": "Conflict-sensitive resource allocation is research-stage.", "exampleProductCategories": [ "conflict-sensitive-allocation-platform", "peace-building-finance-rails" ], "partnerChannels": [], "lastReviewed": "2026-05-01" } }, { "id": "UC-G-095", "name": "Evidence preservation for human rights documentation", "category": "G", "subcategory": "Human Rights", "description": "Keep records of human rights violations in a form that cannot be altered, with a clear account of who handled them, so they can serve as evidence.", "bCriteria": [ "B3", "B6", "B1" ], "requiredComponents": [ "evidence-platform", "data-integrity-layer", "timestamping-service", "audit-trail" ], "conditionalComponents": [ "smart-contracts" ], "crossCategoryDependencies": [ "UC-G-098" ], "p2TriggerConditions": { "description": "Activated when P2 shows human rights documentation needs with chain of custody requirements and legal evidence standards", "rangeSignals": [ "humanRightsDocumentation >=3", "chainOfCustodyRequired = true", "legalEvidence >=2" ] }, "contextFieldsTemplate": [ "evidence_types", "number_of_witnesses", "geographic_documentation_scope", "legal_jurisdiction", "confidentiality_requirements", "access_control_granularity", "archival_duration" ], "implementationComplexity": "high", "examples": { "note": "Blockchain4Humanity and similar initiatives", "references": [ { "name": "eyeWitness to Atrocities", "url": "https://www.eyewitness.global", "solved": "Mobile app with cryptographic chain-of-custody for human rights documentation; admissible in international courts." }, { "name": "Truepic", "url": "https://truepic.com", "solved": "Image authenticity verification used by human rights organisations and humanitarian responders." }, { "name": "Witness.org", "url": "https://www.witness.org", "solved": "Pioneer in video documentation methodology for human rights cases, including cryptographic verification approaches." } ] }, "propertyMapping": {}, "solutionQuestions": [ { "id": "evidence-types", "type": "select", "options": [ { "label": "Photo/video documentation", "value": "media-evidence" }, { "label": "Written reports and documents", "value": "document-evidence" }, { "label": "Witness testimony and victim statements", "value": "testimony-evidence" } ], "prefillFrom": null, "briefSection": "Evidence capture", "propertyMapping": { "media-evidence": { "technologies": [ "Decentralised media vault", "Cryptographic hashing" ], "technologyProperties": { "hashAlgorithm": "SHA-256", "metadata": "EXIF-timestamp-preserved" } }, "document-evidence": { "technologies": [ "Timestamping service", "PDF signature verification" ], "technologyProperties": { "signatureType": "digital-signature", "archivalFormat": "PDF-A" } }, "testimony-evidence": { "technologies": [ "Audio timestamping", "Cryptographic proof" ], "technologyProperties": { "recordingFormat": "encrypted-audio", "verificationLevel": "voice-print" } } }, "text": "What types of evidence are captured and preserved?", "ngoText": "What types of evidence are captured and preserved?" }, { "id": "chain-of-custody", "type": "select", "options": [ { "label": "Manual log: Paper/digital handover records", "value": "manual-log" }, { "label": "automated rules: Automated custody transfers digital", "value": "smart-contract" }, { "label": "Hybrid: QR codes + digital verification", "value": "hybrid-custody" } ], "prefillFrom": null, "briefSection": "Chain of custody", "propertyMapping": { "manual-log": { "technologies": [ "Timestamped logbook", "Witness signatures" ], "technologyProperties": { "verificationMethod": "human-review", "admissibility": "conditional" } }, "smart-contract": { "technologies": [ "Evidence chain-of-custody contract", "Multi-sig approval" ], "technologyProperties": { "transferAuthorization": "cryptographic-signature", "auditTrail": "immutable" } }, "hybrid-custody": { "technologies": [ "QR code timestamping", "Blockchain anchor" ], "technologyProperties": { "physicalVerification": "QR-scan", "digitalVerification": "Digital-record" } } }, "text": "How is chain of custody currently maintained and verified?", "ngoText": "How is chain of custody currently maintained and verified?" }, { "id": "legal-admissibility", "type": "select", "options": [ { "label": "Domestic courts (national jurisdiction)", "value": "domestic-courts" }, { "label": "International tribunals (ICC/ad-hoc courts)", "value": "int-tribunals" }, { "label": "Truth commissions and investigative bodies", "value": "truth-commission" } ], "prefillFrom": null, "briefSection": "Data integrity", "propertyMapping": { "domestic-courts": { "technologies": [ "National law compliance", "Certified auditor" ], "technologyProperties": { "jurisdictionType": "national", "certificationRequired": "true" } }, "int-tribunals": { "technologies": [ "ICC evidence guidelines", "Forensic validation" ], "technologyProperties": { "standard": "ICC-Rules-of-Evidence", "expertReview": "required" } }, "truth-commission": { "technologies": [ "Commission-specific protocols", "Credibility assessment" ], "technologyProperties": { "admissionStandard": "investigation-support", "strictEvidence": "false" } } }, "text": "What legal jurisdiction standards must evidence meet?", "ngoText": "What legal jurisdiction standards must evidence meet?" }, { "id": "confidentiality-protection", "type": "select", "options": [ { "label": "Full encryption: End-to-end encryption of all evidence", "value": "full-encryption" }, { "label": "Selective disclosure: Only authorized parties can view", "value": "selective-disclosure" }, { "label": "Anonymization: PII redacted with verified preservation", "value": "anonymization" } ], "prefillFrom": null, "briefSection": "Data integrity", "propertyMapping": { "full-encryption": { "technologies": [ "AES-256 encryption", "Key management service" ], "technologyProperties": { "encryptionStandard": "government-grade", "keyHolders": "multiple-independent" } }, "selective-disclosure": { "technologies": [ "Zero-knowledge proofs", "Attribute-based access control" ], "technologyProperties": { "proofType": "zkSNARK", "accessRules": "attribute-based" } }, "anonymization": { "technologies": [ "Differential privacy", "De-identification algorithm" ], "technologyProperties": { "privacyLevel": "epsilon=1.0", "reversibility": "only-key-holders" } } }, "text": "How do you currently protect the confidentiality of sensitive information?", "ngoText": "How do you currently protect the confidentiality of sensitive information?" }, { "id": "long-term-archival", "type": "select", "options": [ { "label": "Centralized archive: Single trusted repository", "value": "centralized-archive" }, { "label": "Distributed: Multiple copies across independent storage providers", "value": "distributed-archive" }, { "label": "Hybrid: Institutional + distributed backup", "value": "hybrid-archive" } ], "prefillFrom": null, "briefSection": "Reporting and audit", "propertyMapping": { "centralized-archive": { "technologies": [ "Institutional archive", "Backup redundancy" ], "technologyProperties": { "backupCopies": "3+", "geoRedundancy": "true" } }, "distributed-archive": { "technologies": [ "Decentralised permanent storage", "Pay-once permanent storage" ], "technologyProperties": { "permanence": "indefinite", "redundancy": "automatic-replication" } }, "hybrid-archive": { "technologies": [ "Primary institutional archive", "Decentralised storage backup" ], "technologyProperties": { "primaryStorage": "institutional", "backupLayer": "Distributed" } } }, "text": "How is long-term archival and accessibility ensured?", "ngoText": "How is long-term archival and accessibility ensured?" }, { "id": "evidence-platform-approach", "type": "select", "options": [ { "label": "distributed storage/distributed storage with digital ledger tamper-proof verification", "value": "ipfs-anchored" }, { "label": "Cloud storage with periodic digital ledger proof checkpoints", "value": "cloud-anchored" }, { "label": "Digital metadata with separate encrypted file storage", "value": "hybrid-storage" }, { "label": "Not sure, need guidance on evidence storage", "value": "guidance-needed" } ], "propertyMapping": { "ipfs-anchored": { "technologies": [ "Decentralised-storage evidence platform", "Data integrity verification layer", "Content-addressed storage service" ], "technologyProperties": { "storageMethod": "Decentralised storage network", "integrityProof": "Content hash on blockchain", "redundancy": "Distributed across multiple nodes" } }, "cloud-anchored": { "technologies": [ "Cloud evidence platform", "Data integrity verification layer", "Periodic proof checkpoint service" ], "technologyProperties": { "storageMethod": "Commercial cloud storage", "integrityProof": "Periodic Merkle root on blockchain", "redundancy": "Cloud provider redundancy" } }, "hybrid-storage": { "technologies": [ "Hybrid evidence platform", "Data integrity verification layer", "Encrypted off-chain storage" ], "technologyProperties": { "storageMethod": "Digital metadata + encrypted off-chain files", "integrityProof": "Digital hash per document", "redundancy": "Configurable" } }, "guidance-needed": { "technologies": [ "Evidence platform framework", "Data integrity verification layer" ], "technologyProperties": { "storageMethod": "To be determined", "integrityProof": "To be determined", "redundancy": "To be determined" } } }, "prefillFrom": null, "briefSection": "Evidence and data integrity", "text": "How is evidence and documents currently stored and verified?", "ngoText": "How is evidence and documents currently stored and verified?" } ], "complexityFactors": { "relationships": 3, "operationalChange": 2, "dataCompliance": 5 }, "securityTier": "C", "suggestedCriteria": [ { "id": "SC-G095-CHAIN", "name": "Chain of Custody Integrity", "description": "The system maintains a cryptographically verifiable chain of custody from evidence capture to storage. Human rights evidence that cannot demonstrate an unbroken chain of custody may be inadmissible in legal proceedings.", "weight": 0.3, "ratingGuide": { "5": "End-to-end chain of custody from capture device to archive. Each custodial transfer cryptographically signed and timestamped. Hash verification at every handoff point. Tamper detection on stored evidence. Compliant with international evidence handling standards.", "4": "Chain of custody from ingestion to archive (not from capture device). Cryptographic signing at each transfer. Hash verification. Tamper detection on storage.", "3": "Chain of custody tracked from upload to archive. Hashing on upload and storage. No capture-device-level provenance. Basic tamper detection.", "2": "Evidence stored with upload timestamp and uploader identity. No cryptographic chain between custodial handoffs. Limited tamper detection.", "1": "Evidence files stored with basic metadata. No chain of custody tracking. No cryptographic integrity verification." } }, { "id": "SC-G095-LEGAL", "name": "Legal Admissibility Standards Compliance", "description": "Does the evidence handling meet standards required by international tribunals and courts? The Berkeley Protocol for digital open source investigations sets emerging benchmarks, does the system align?", "weight": 0.25, "ratingGuide": { "5": "Explicitly aligned with Berkeley Protocol on Digital Open Source Investigations. Metadata preservation meets ICC evidence standards. Expert testimony support package for chain of custody demonstration. Used in actual legal proceedings.", "4": "Aligned with Berkeley Protocol principles. Metadata preservation comprehensive. Documentation sufficient for legal testimony. Not yet tested in proceedings.", "3": "Aware of legal admissibility requirements. Metadata preserved but not systematically structured for court presentation. No alignment with specific protocols.", "2": "Evidence stored securely but not designed for legal admissibility. Metadata preservation is inconsistent. No legal standards alignment.", "1": "No consideration of legal admissibility. Evidence handling would not withstand legal challenge to integrity or provenance." } }, { "id": "SC-G095-PROTECT", "name": "Source & Witness Protection Controls", "description": "This measures how effectively the system protects the identity and safety of sources and witnesses. In human rights documentation, exposure of sources can lead to retaliation, imprisonment, or death.", "weight": 0.2, "ratingGuide": { "5": "Granular access controls with need-to-know enforcement. Automatic metadata stripping (EXIF, geolocation) on ingestion with original preserved in restricted archive. Pseudonymisation and anonymisation tools built in. Compartmentalised access \u2014 no single user can access all evidence.", "4": "Role-based access controls. Metadata stripping available. Pseudonymisation supported. Access compartmentalisation configurable.", "3": "Role-based access. Manual metadata stripping possible. No built-in pseudonymisation. All authorised users see all evidence.", "2": "Basic password-protected access. No metadata stripping. No anonymisation tools. Evidence accessible to all system users.", "1": "Minimal access controls. Source-identifying metadata retained and visible. No protection mechanisms for witnesses." } }, { "id": "SC-G095-ARCHIVE", "name": "Long-Term Archival Durability", "description": "Evidence can be preserved reliably for decades. Human rights cases may take 10-20+ years to reach prosecution. Evidence must survive storage provider changes, format obsolescence, and organisational transitions.", "weight": 0.15, "ratingGuide": { "5": "Multi-provider redundant storage (3+ independent locations). Format migration strategy documented. Organisational continuity plan if maintaining organisation ceases. Periodic integrity verification (bitrot detection). 20+ year demonstrated or designed archival capability.", "4": "Redundant storage across 2+ providers. Format migration planned. Integrity verification scheduled. Designed for 10+ year retention.", "3": "Redundant storage with single provider (multi-region). No format migration plan. Annual integrity checks. 5+ year retention commitment.", "2": "Single-location storage. No redundancy plan. No format migration strategy. Retention dependent on ongoing subscription/funding.", "1": "No archival strategy. Evidence stored on operational infrastructure with no long-term retention planning. Data loss risk on platform change." } }, { "id": "SC-G095-OFFLINE", "name": "Offline Evidence Collection Capability", "description": "Evidence can be securely captured and queued in environments with no internet connectivity. Human rights violations often occur in remote areas or during communication shutdowns. Connectivity cannot be a prerequisite.", "weight": 0.1, "ratingGuide": { "5": "Purpose-built offline capture app with local encryption and integrity hashing. Automatic sync with chain of custody preservation when connectivity resumes. Supports photo, video, audio, and text. Offline capture timestamps verified against trusted time source on sync.", "4": "Offline capture with local encryption. Sync on reconnection with basic chain of custody. Supports major media types. Timestamp from device clock.", "3": "Evidence can be captured offline but must be manually uploaded. Integrity hashing on upload only (not at capture). Some metadata may be lost.", "2": "Limited offline capability. Text notes can be saved but media requires connectivity. Manual upload with no integrity guarantees.", "1": "No offline capability. Evidence collection requires active internet connection. Cannot operate during communication shutdowns." } } ], "procurement": { "marketMaturity": "nascent", "primaryMode": "integrator-led", "alternativeModes": [ "consortium" ], "reasoning": "Human rights evidence preservation is bespoke; legal-tech partners typical.", "exampleProductCategories": [ "human-rights-evidence-platform", "legal-tech-evidence-rails" ], "partnerChannels": [], "lastReviewed": "2026-05-01" } }, { "id": "UC-G-096", "name": "Atrocity documentation with chain of custody", "category": "G", "subcategory": "Human Rights", "description": "Document atrocities with a secure record of who held the evidence at each step, so it can be relied on in court or by truth commissions.", "bCriteria": [ "B3", "B6", "B1" ], "requiredComponents": [ "evidence-platform", "data-integrity-layer", "timestamping-service", "audit-trail" ], "conditionalComponents": [ "smart-contracts" ], "crossCategoryDependencies": [ "UC-G-098" ], "p2TriggerConditions": { "description": "Activated when P2 shows atrocity documentation requirements with legal proceedings needs and strict chain of custody obligations", "rangeSignals": [ "atrocityDocumentation >=3", "legalProceedings >=2", "chainOfCustodyRequired = true" ] }, "contextFieldsTemplate": [ "documentation_standard", "evidence_integrity_verification_method", "legal_admissibility_requirements", "investigative_body_partnerships", "confidentiality_level", "long_term_archival_need", "multi_jurisdiction_support" ], "implementationComplexity": "high", "examples": { "note": "International Criminal Court evidence standards", "references": [ { "name": "International Criminal Court", "url": "https://www.icc-cpi.int", "solved": "Sets evidentiary standards for atrocity documentation; eyeWitness to Atrocities developed for ICC admissibility." }, { "name": "eyeWitness to Atrocities", "url": "https://www.eyewitness.global", "solved": "Chain-of-custody documentation specifically designed for international criminal court admissibility." }, { "name": "Bellingcat", "url": "https://www.bellingcat.com", "solved": "Open-source investigation methodology for atrocity documentation including verifiable provenance for digital evidence." } ] }, "propertyMapping": {}, "solutionQuestions": [ { "id": "documentation-standard", "type": "select", "options": [ { "label": "ICC Evidence Procedures and Standards", "value": "icc-standard" }, { "label": "UN Human Rights investigation guidelines", "value": "un-guidelines" }, { "label": "Nexus Institute protocol (multi-jurisdiction)", "value": "nexus-protocol" } ], "prefillFrom": null, "briefSection": "Evidence capture", "propertyMapping": { "icc-standard": { "technologies": [ "ICC guidelines compliance", "Forensic certification" ], "technologyProperties": { "certificationBody": "ICC-approved", "auditFrequency": "annual" } }, "un-guidelines": { "technologies": [ "UN protocols integration", "Expert verification" ], "technologyProperties": { "guideline": "UN-Office-of-HR", "reviewLevel": "international" } }, "nexus-protocol": { "technologies": [ "Multi-standard validator", "Cross-jurisdiction checker" ], "technologyProperties": { "harmonization": "multiple-standards", "jurisdictionSpecific": "true" } } }, "text": "What documentation standards does your resilience programme require?", "ngoText": "What documentation standards does your resilience programme require?", "hidden": true }, { "id": "evidence-integrity-verification", "type": "select", "options": [ { "label": "Digital fingerprinting and timestamping", "value": "crypto-hash" }, { "label": "Digital forensics: Bit-level verification", "value": "digital-forensics" }, { "label": "Provenance chain: Full metadata + witness verification", "value": "provenance-chain" } ], "prefillFrom": null, "briefSection": "Chain of custody", "propertyMapping": { "crypto-hash": { "technologies": [ "SHA-256 hashing", "Cryptographic timestamping service" ], "technologyProperties": { "hashAlgorithm": "SHA-256", "timeserver": "trusted-third-party" } }, "digital-forensics": { "technologies": [ "Forensic imaging", "Expert certification" ], "technologyProperties": { "imagingStandard": "ISO-27043", "expertReview": "required" } }, "provenance-chain": { "technologies": [ "Metadata blockchain", "Witness signature" ], "technologyProperties": { "metadataPreservation": "complete", "verificationWitnesses": "3+" } } }, "text": "For evidence integrity verification, do you need: digital tamper-proof verification, legal notarization, or multiple witness signatures?", "ngoText": "For evidence integrity verification, do you need: cryptographic proof (hash verification), legal notarization, or multiple witness signatures?" }, { "id": "multi-jurisdiction-support", "type": "select", "options": [ { "label": "Single jurisdiction: Evidence format for one legal system", "value": "single-jurisdiction" }, { "label": "Multi-format: Evidence packaged for multiple jurisdictions", "value": "multi-format" }, { "label": "Universal admissibility: Standardized format accepted everywhere", "value": "universal-format" } ], "prefillFrom": null, "briefSection": "Reporting and audit", "propertyMapping": { "single-jurisdiction": { "technologies": [ "Jurisdiction-specific formatting", "Local law compliance" ], "technologyProperties": { "targetJurisdiction": "single", "translation": "if-required" } }, "multi-format": { "technologies": [ "Format converter", "Jurisdiction validator" ], "technologyProperties": { "supportedJurisdictions": "5+", "certificationLevel": "each-jurisdiction" } }, "universal-format": { "technologies": [ "Universal evidence standard", "International court protocol" ], "technologyProperties": { "standard": "internationally-agreed", "recognitionScope": "global" } } }, "text": "Evidence will be used in which jurisdiction contexts: a single national court, regional tribunal (e.g., ICC), multiple different national courts, or international/hybrid tribunal?", "ngoText": "Evidence will be used in which jurisdiction contexts: a single national court, regional tribunal (e.g., ICC), multiple different national courts, or international/hybrid tribunal?" }, { "id": "investigator-access", "type": "select", "options": [ { "label": "Open access: All investigators can view evidence", "value": "open-access" }, { "label": "Restricted: Access approved by managing organization", "value": "restricted-access" }, { "label": "Tiered: Access depends on investigator role/tribunal", "value": "tiered-access" } ], "prefillFrom": null, "briefSection": "Data integrity", "propertyMapping": { "open-access": { "technologies": [ "Public repository", "Credential verification" ], "technologyProperties": { "accessControl": "credential-based", "auditLogging": "complete" } }, "restricted-access": { "technologies": [ "Multi-sig access approval", "DAO governance" ], "technologyProperties": { "approvalRequired": "multi-sig", "purposeJustification": "required" } }, "tiered-access": { "technologies": [ "Role-based access control", "Attribute verification" ], "technologyProperties": { "roles": [ "local-prosecutor", "international-tribunal", "truth-commission" ], "permissionLevel": "role-dependent" } } }, "text": "What access rights do investigators have to evidence?", "ngoText": "What access rights do investigators have to evidence?" }, { "id": "atrocity-doc-evidence-volume", "type": "select", "options": [ { "label": "Under 100 records", "value": "small" }, { "label": "100\u20131,000 records", "value": "medium" }, { "label": "1,000\u201310,000 records", "value": "large" }, { "label": "Over 10,000 records", "value": "mass" } ], "propertyMapping": { "small": { "technologies": [ "Simple evidence store" ], "technologyProperties": { "storageRequirement": "Low", "archivalPeriod": "Standard" } }, "medium": { "technologies": [ "Evidence management platform" ], "technologyProperties": { "storageRequirement": "Medium", "archivalPeriod": "Long-term" } }, "large": { "technologies": [ "Scalable evidence platform", "Distributed storage" ], "technologyProperties": { "storageRequirement": "High", "archivalPeriod": "Long-term" } }, "mass": { "technologies": [ "Enterprise evidence platform", "Decentralised or permanent-storage network" ], "technologyProperties": { "storageRequirement": "Very high", "archivalPeriod": "Permanent" } } }, "prefillFrom": null, "briefSection": "Evidence capture", "text": "What volume of atrocity documentation evidence needs to be captured and preserved?", "ngoText": "What volume of atrocity documentation evidence needs to be captured and preserved?" }, { "id": "audit-trail-approach", "type": "select", "options": [ { "label": "Donors and external auditors need to independently verify any action at any time", "value": "donors-and-external-auditors-need-to-ind" }, { "label": "External auditors check periodically: summary reports and spot-checks are sufficient", "value": "external-auditors-check-periodically-sum" }, { "label": "Key milestones and approvals need independent verification; routine actions just need internal records", "value": "key-milestones-and-approvals-need-indepe" }, { "label": "Internal team records are sufficient: we mainly need our own staff to be able to look back", "value": "internal-team-records-are-sufficient-we-" }, { "label": "Not sure, need guidance on audit requirements", "value": "not-sure-need-guidance-on-audit-requirem" } ], "propertyMapping": { "full-immutable": { "technologies": [ "Immutable audit trail", "On-chain event logging", "Audit trail verification service" ], "technologyProperties": { "auditGranularity": "Every action", "storageApproach": "Full on-chain logging", "tamperEvidence": "Cryptographic hash chain" } }, "key-events": { "technologies": [ "Milestone-based audit trail", "Approval chain logger", "Audit trail verification service" ], "technologyProperties": { "auditGranularity": "Key milestones and approvals only", "storageApproach": "Selective on-chain logging", "tamperEvidence": "Merkle root anchoring" } }, "hybrid": { "technologies": [ "Hybrid audit trail system", "Off-chain storage with hash anchoring", "Audit trail verification service" ], "technologyProperties": { "auditGranularity": "Metadata on-chain, full records off-chain", "storageApproach": "Decentralised/off-chain storage with on-chain hash proofs", "tamperEvidence": "Hash anchoring to blockchain" } }, "guidance-needed": { "technologies": [ "Audit trail framework", "Audit trail verification service" ], "technologyProperties": { "auditGranularity": "To be determined during solution design", "storageApproach": "To be determined", "tamperEvidence": "To be determined" } } }, "prefillFrom": null, "briefSection": "Audit and evidence", "text": "What level of audit trail does this solution require?", "ngoText": "What level of audit trail does this solution require?", "hidden": true, "question": "Who needs to verify that actions in this system happened correctly, and how easily should they be able to check?" } ], "complexityFactors": { "relationships": 3, "operationalChange": 2, "dataCompliance": 5 }, "securityTier": "C", "suggestedCriteria": [ { "id": "SC-G096-ICC", "name": "International Criminal Court Standards Alignment", "description": "The system meets the evidentiary standards of the ICC and other international criminal tribunals. Atrocity documentation that fails admissibility challenges wastes years of dangerous collection work.", "weight": 0.3, "ratingGuide": { "5": "Evidence handling explicitly designed for ICC Rules of Procedure and Evidence. Chain of custody documentation meets Rome Statute requirements. System has been reviewed by international criminal law practitioners. Export formats suitable for OTP submissions.", "4": "Designed with ICC standards in mind. Chain of custody documentation comprehensive. Reviewed by legal experts but not ICC-specific practitioners.", "3": "General legal evidence standards applied. Chain of custody present but not tailored to ICC requirements. Legal review conducted but not specific to international criminal law.", "2": "Standard evidence storage. Chain of custody basic. No alignment with any specific international tribunal standards.", "1": "No legal standards applied. Evidence storage is operational only. Documentation would not be considered for tribunal proceedings." } }, { "id": "SC-G096-FORENSIC", "name": "Evidence Integrity & Forensic Readiness", "description": "Evidence integrity can be independently verified through forensic examination. For atrocity cases, defence teams will challenge evidence authenticity. The system must support forensic validation of every piece of evidence.", "weight": 0.25, "ratingGuide": { "5": "Multiple hash algorithms (SHA-256+) applied at capture, transfer, and storage. Signed timestamps from trusted third-party time authority. Forensic export package includes full hash chain, access logs, and verification instructions. Supports standard forensic tools for validation.", "4": "SHA-256 hashing at all stages. Signed timestamps. Forensic export available. Compatible with common forensic tools.", "3": "Hashing at upload and storage. Timestamps from system clock (not third-party authority). Basic export of integrity data.", "2": "Hashing at storage only. No signed timestamps. Limited integrity metadata available for forensic review.", "1": "No forensic readiness. Evidence files stored without integrity hashing. No capability for independent forensic verification." } }, { "id": "SC-G096-CONFID", "name": "Confidentiality & Classification Controls", "description": "The system supports multi-level classification and need-to-know access for atrocity evidence. Premature disclosure can endanger witnesses, compromise investigations, and alert perpetrators.", "weight": 0.2, "ratingGuide": { "5": "Multi-level classification system (e.g. Confidential, Restricted, Public). Mandatory access control enforced at evidence and field level. Classification can be upgraded or downgraded with full audit trail. Supports sealed evidence that even administrators cannot access without multi-party authorisation.", "4": "Classification levels with role-based access enforcement. Field-level restrictions available. Classification changes audited.", "3": "Basic classification (e.g. Sensitive/Non-sensitive). Role-based access. No field-level restrictions. Classification changes logged.", "2": "Single access level for all evidence. Administrator has full access. No classification system.", "1": "No access controls or classification. All system users see all evidence. No confidentiality protections." } }, { "id": "SC-G096-JURIS", "name": "Multi-Jurisdictional Evidence Handling", "description": "The system can manage evidence that may be relevant to proceedings in multiple jurisdictions with differing legal requirements. Atrocity cases often involve ICC, national courts, and truth commissions simultaneously.", "weight": 0.15, "ratingGuide": { "5": "Evidence tagged with applicable jurisdictions. Export packages configurable per jurisdiction's evidence rules. Supports simultaneous sharing with multiple legal bodies under different access constraints. Tracks which evidence has been shared with which body.", "4": "Jurisdiction tagging available. Export configurable for 2-3 jurisdiction types. Sharing tracking implemented.", "3": "Single export format. Jurisdiction noted in metadata but does not affect handling. Basic sharing records.", "2": "No jurisdictional differentiation. Evidence handled identically regardless of intended legal use.", "1": "No awareness of jurisdictional requirements. Evidence management does not consider legal proceedings context." } }, { "id": "SC-G096-PARTNER", "name": "Investigative Body Interoperability", "description": "The system can exchange evidence securely with investigative bodies (ICC OTP, UN fact-finding missions, national prosecutors). Isolated evidence archives are useless if evidence cannot be securely transmitted to those who need it for prosecution.", "weight": 0.1, "ratingGuide": { "5": "Secure evidence transfer protocol tested with investigative bodies. Supports bulk evidence packages with chain of custody documentation. End-to-end encrypted transfer. Receiving body can independently verify integrity. Proven use in actual investigations.", "4": "Secure transfer capability with end-to-end encryption. Chain of custody preserved in transfer. Tested in practice but not with major investigative bodies.", "3": "Encrypted export and transfer available. Chain of custody documentation included. Not tested with receiving bodies' intake systems.", "2": "Evidence exportable but transfer security depends on external tools (e.g. email encryption). Chain of custody may break during transfer.", "1": "No secure transfer capability. Evidence must be extracted and transmitted manually with no integrity guarantees." } } ], "procurement": { "marketMaturity": "nascent", "primaryMode": "integrator-led", "alternativeModes": [ "consortium" ], "reasoning": "Atrocity documentation platforms exist in legal-tech but bespoke for humanitarian.", "exampleProductCategories": [ "atrocity-documentation-platform", "chain-of-custody-rails" ], "partnerChannels": [], "lastReviewed": "2026-05-01" } }, { "id": "UC-G-097", "name": "Witness testimony timestamping", "category": "G", "subcategory": "Human Rights", "description": "Fix the date and time of each witness statement, so that nobody can later change it or claim it was made at another time.", "bCriteria": [ "B3", "B6" ], "requiredComponents": [ "timestamping-service", "data-integrity-layer", "audit-trail" ], "conditionalComponents": [ "evidence-platform" ], "crossCategoryDependencies": [ "UC-G-098", "UC-G-098" ], "p2TriggerConditions": { "description": "Activated when P2 shows witness documentation needs with legal evidence requirements and confidentiality concerns", "rangeSignals": [ "witnessDocumentation >=2", "legalEvidence >=2", "confidentiality >=2" ] }, "contextFieldsTemplate": [ "number_of_witnesses", "testimony_collection_locations", "confidentiality_requirements", "legal_jurisdiction", "verification_requirement", "access_control_level" ], "implementationComplexity": "low", "examples": { "note": "Technical building block; can be integrated with evidence platform", "references": [ { "name": "OpenTimestamps", "url": "https://opentimestamps.org", "solved": "Free Bitcoin-anchored timestamping service used by journalists and human-rights organisations for evidence preservation." }, { "name": "eyeWitness to Atrocities", "url": "https://www.eyewitness.global", "solved": "Witness testimony capture with cryptographic timestamping designed for legal admissibility." }, { "name": "Truepic", "url": "https://truepic.com", "solved": "Provenance-verified content capture with timestamping at moment of recording." } ] }, "propertyMapping": {}, "solutionQuestions": [ { "id": "testimony-format", "type": "select", "options": [ { "label": "Audio recording (encrypted digital file)", "value": "audio-format" }, { "label": "Video recording (with face/identifier verification)", "value": "video-format" }, { "label": "Transcript + independent notarization", "value": "transcript-format" } ], "prefillFrom": null, "briefSection": "Evidence capture", "propertyMapping": { "audio-format": { "technologies": [ "AES-256 audio encryption", "MP3/WAV format" ], "technologyProperties": { "codec": "lossless-audio", "bitrate": "320kbps" } }, "video-format": { "technologies": [ "Biometric capture", "Video timestamping" ], "technologyProperties": { "resolution": "1080p+", "biometric": "facial-recognition" } }, "transcript-format": { "technologies": [ "Certified transcript", "Digital notarization" ], "technologyProperties": { "notary": "independent-third-party", "language": "original-language" } } }, "text": "In what format is witness testimony recorded?", "ngoText": "In what format is witness testimony recorded?" }, { "id": "verification-level", "type": "select", "options": [ { "label": "Self-declaration: Witness provides name/ID only", "value": "self-declaration" }, { "label": "Document verification: Passport/ID scan + liveness check", "value": "doc-verification" }, { "label": "Biometric + cross-reference: Fingerprint/facial + registry check", "value": "biometric-cross-ref" } ], "prefillFrom": null, "briefSection": "Data integrity", "propertyMapping": { "self-declaration": { "technologies": [ "Simple identity claim", "Timestamp record" ], "technologyProperties": { "verificationLevel": "low", "fraudRisk": "high" } }, "doc-verification": { "technologies": [ "OCR document scan", "Liveness detection" ], "technologyProperties": { "documentCheck": "automated", "livenessMethod": "face-detection" } }, "biometric-cross-ref": { "technologies": [ "Fingerprint scanner", "Facial recognition", "Database cross-check" ], "technologyProperties": { "biometricType": "multi-modal", "confidenceThreshold": "99%" } } }, "text": "What level of witness verification is performed?", "ngoText": "What level of witness verification is performed?" }, { "id": "witness-evidence-volume", "type": "select", "options": [ { "label": "Under 100 records", "value": "small" }, { "label": "100\u20131,000 records", "value": "medium" }, { "label": "1,000\u201310,000 records", "value": "large" }, { "label": "Over 10,000 records", "value": "mass" } ], "propertyMapping": { "small": { "technologies": [ "Simple evidence store" ], "technologyProperties": { "storageRequirement": "Low", "archivalPeriod": "Standard" } }, "medium": { "technologies": [ "Evidence management platform" ], "technologyProperties": { "storageRequirement": "Medium", "archivalPeriod": "Long-term" } }, "large": { "technologies": [ "Scalable evidence platform", "Distributed storage" ], "technologyProperties": { "storageRequirement": "High", "archivalPeriod": "Long-term" } }, "mass": { "technologies": [ "Enterprise evidence platform", "Decentralised or permanent-storage network" ], "technologyProperties": { "storageRequirement": "Very high", "archivalPeriod": "Permanent" } } }, "prefillFrom": null, "briefSection": "Evidence capture", "text": "What volume of witness testimony evidence needs to be captured and preserved?", "ngoText": "What volume of witness testimony evidence needs to be captured and preserved?" }, { "id": "witness-stakeholders", "type": "select", "options": [ { "label": "Internal only (1\u20132 teams)", "value": "internal" }, { "label": "Internal + 1\u20133 external partners", "value": "few-external" }, { "label": "Multiple external stakeholders (4\u201310)", "value": "multi-external" }, { "label": "Ecosystem-wide (donors, partners, beneficiaries, regulators)", "value": "ecosystem" } ], "propertyMapping": { "internal": { "technologies": [ "Private ledger" ], "technologyProperties": { "accessControl": "Simple role-based", "networkType": "Private" } }, "few-external": { "technologies": [ "Permissioned network", "Selective data sharing" ], "technologyProperties": { "accessControl": "Partner-level permissions", "networkType": "Consortium" } }, "multi-external": { "technologies": [ "Permissioned network", "Multi-party access layer" ], "technologyProperties": { "accessControl": "Granular role-based", "networkType": "Consortium" } }, "ecosystem": { "technologies": [ "Permissioned public network", "Data marketplace" ], "technologyProperties": { "accessControl": "Multi-tier with public layer", "networkType": "Hybrid public-private" } } }, "prefillFrom": null, "briefSection": "Governance and access", "text": "How many distinct parties need visibility into the testimony evidence data?", "ngoText": "How many distinct parties need visibility into the testimony evidence data?" }, { "id": "sq-UC-G-098-001", "type": "single-select", "options": [ { "value": "pseudonymous-with-key-escrow", "label": "Pseudonymous with key escrow" }, { "value": "sealed-identity-court-only", "label": "Sealed identity: court only" }, { "value": "fully-anonymous", "label": "Fully anonymous" }, { "value": "tiered-disclosure", "label": "Tiered disclosure" }, { "value": "witness-controlled-revelation", "label": "Witness-controlled revelation" } ], "propertyMapping": { "pseudonymous-with-key-escrow": { "technologies": [ "pseudonym-system", "key-escrow" ], "technologyProperties": {} }, "sealed-identity-court-only": { "technologies": [ "sealed-system", "court-access" ], "technologyProperties": {} }, "fully-anonymous": { "technologies": [ "anonymization-system", "identifier-removal" ], "technologyProperties": {} }, "tiered-disclosure": { "technologies": [ "disclosure-rules", "access-tiers" ], "technologyProperties": {} }, "witness-controlled-revelation": { "technologies": [ "witness-control", "reveal-system" ], "technologyProperties": {} } }, "briefSection": "requirements", "text": "For witness protection, do you need: complete anonymity with verification by trusted third party, pseudonymity with audit trail for investigators, or identifiable access only to authorized parties?", "ngoText": "For witness protection, do you need: complete anonymity with verification by trusted third party, pseudonymity with audit trail for investigators, or identifiable access only to authorized parties?" }, { "id": "audit-trail-approach", "type": "select", "options": [ { "label": "Donors and external auditors need to independently verify any action at any time", "value": "donors-and-external-auditors-need-to-ind" }, { "label": "External auditors check periodically: summary reports and spot-checks are sufficient", "value": "external-auditors-check-periodically-sum" }, { "label": "Key milestones and approvals need independent verification; routine actions just need internal records", "value": "key-milestones-and-approvals-need-indepe" }, { "label": "Internal team records are sufficient: we mainly need our own staff to be able to look back", "value": "internal-team-records-are-sufficient-we-" }, { "label": "Not sure, need guidance on audit requirements", "value": "not-sure-need-guidance-on-audit-requirem" } ], "propertyMapping": { "full-immutable": { "technologies": [ "Immutable audit trail", "On-chain event logging", "Audit trail verification service" ], "technologyProperties": { "auditGranularity": "Every action", "storageApproach": "Full on-chain logging", "tamperEvidence": "Cryptographic hash chain" } }, "key-events": { "technologies": [ "Milestone-based audit trail", "Approval chain logger", "Audit trail verification service" ], "technologyProperties": { "auditGranularity": "Key milestones and approvals only", "storageApproach": "Selective on-chain logging", "tamperEvidence": "Merkle root anchoring" } }, "hybrid": { "technologies": [ "Hybrid audit trail system", "Off-chain storage with hash anchoring", "Audit trail verification service" ], "technologyProperties": { "auditGranularity": "Metadata on-chain, full records off-chain", "storageApproach": "Decentralised/off-chain storage with on-chain hash proofs", "tamperEvidence": "Hash anchoring to blockchain" } }, "guidance-needed": { "technologies": [ "Audit trail framework", "Audit trail verification service" ], "technologyProperties": { "auditGranularity": "To be determined during solution design", "storageApproach": "To be determined", "tamperEvidence": "To be determined" } } }, "prefillFrom": null, "briefSection": "Audit and evidence", "text": "What level of audit trail does this solution require?", "ngoText": "What level of audit trail does this solution require?", "hidden": true, "question": "Who needs to verify that actions in this system happened correctly, and how easily should they be able to check?" } ], "complexityFactors": { "relationships": 2, "operationalChange": 1, "dataCompliance": 5 }, "securityTier": "C", "suggestedCriteria": [ { "id": "SC-G097-CRYPTO", "name": "Timestamping Cryptographic Strength", "description": "This measures how strong the cryptographic timestamping implementation is. Timestamps that can be forged or backdated undermine the entire purpose. The system must use established standards and trusted time sources.", "weight": 0.25, "ratingGuide": { "5": "RFC 3161 compliant timestamping with trusted third-party Time Stamping Authority (TSA). SHA-256 or stronger hashing. TSA independently auditable. Supports multiple TSA providers for redundancy. Timestamps anchored to blockchain for additional immutability.", "4": "RFC 3161 compliant with single TSA. SHA-256 hashing. TSA audit reports available. No blockchain anchoring.", "3": "Cryptographic timestamping using system-managed keys (not third-party TSA). SHA-256 hashing. Self-signed timestamps.", "2": "Timestamps generated by application server. No cryptographic proof. No independent time source verification.", "1": "File system or database timestamps only. Easily modifiable. No cryptographic integrity. Timestamps provide no evidentiary value." } }, { "id": "SC-G097-WITNESS", "name": "Witness Identity Protection", "description": "The timestamping system protects witness identity while maintaining the evidentiary value of the timestamp. Witnesses of human rights violations face retaliation risks. The system must decouple identity from testimony where needed.", "weight": 0.25, "ratingGuide": { "5": "Supports fully anonymous timestamping (no identity metadata in timestamp). Optional pseudonymous mode with identity sealed and recoverable only through multi-party authorisation. Zero-knowledge proof that a timestamp was created by an authorised collector without revealing identity.", "4": "Pseudonymous timestamping with sealed identity. Identity recoverable with 2+ authorised parties. Witness metadata encrypted separately from testimony content.", "3": "Witness identity can be omitted from timestamp records. No pseudonymous mode. Identity, if recorded, stored in same system as testimony.", "2": "Witness identity required for timestamping. Identity stored alongside testimony with standard access controls.", "1": "Witness identity embedded in timestamp metadata. No separation possible. Identity exposure inherent in evidence presentation." } }, { "id": "SC-G097-VERIFY", "name": "Independent Verification Simplicity", "description": "This measures how easily a third party (court, investigator, journalist) can independently verify that a testimony existed at the claimed time without needing access to the full system. Verification that requires the issuing system undermines trust.", "weight": 0.2, "ratingGuide": { "5": "Any third party can verify timestamps using only the timestamp token and a public verification service. No account or system access required. Verification instructions publishable. Supports verification against public blockchain anchor.", "4": "Third party can verify with timestamp token and provider's public verification endpoint. No account needed. Clear verification documentation.", "3": "Verification requires an account on the provider's platform. Verification process documented but not publicly accessible.", "2": "Verification requires contacting the provider to confirm timestamp validity. No self-service verification.", "1": "No independent verification possible. Timestamps can only be validated by the system that created them." } }, { "id": "SC-G097-FIELD", "name": "Field Deployability & Low-Resource Operation", "description": "The timestamping system can operate in low-resource field environments typical of human rights documentation. Witness testimony is often collected in conflict zones, refugee camps, or remote areas with limited power and connectivity.", "weight": 0.2, "ratingGuide": { "5": "Runs on standard smartphones with offline timestamping capability. Local cryptographic proof generated offline. Sync with TSA on reconnection to obtain trusted third-party timestamp. Minimal storage and battery requirements.", "4": "Smartphone-based with offline capability. Local hash generated offline. TSA timestamp obtained on sync. Moderate resource requirements.", "3": "Smartphone-based but requires connectivity for timestamping. Works on low-bandwidth connections. No offline timestamping.", "2": "Requires laptop or desktop with internet connection. Not designed for field deployment.", "1": "Server-side only. No field collection capability. Testimony must be brought to the system for timestamping." } }, { "id": "SC-G097-INTEGRATE", "name": "Evidence Platform Composability", "description": "This measures how well the timestamping service integrates as a component within broader evidence preservation systems (UC-G-095, UC-G-096). Timestamping in isolation has limited value. It must compose into larger documentation workflows.", "weight": 0.1, "ratingGuide": { "5": "Published API for integration with evidence platforms. Supports batch timestamping for bulk evidence ingestion. Timestamp tokens include metadata hooks for evidence management systems. Proven integration with 2+ evidence platforms.", "4": "API available. Batch timestamping supported. Standard metadata format. Integrated with at least one evidence platform.", "3": "API available but limited to single-item timestamping. Metadata format proprietary. Integration requires custom development.", "2": "Export timestamps as files for manual import to other systems. No API. No batch processing.", "1": "Standalone system with no integration capability. Timestamps exist only within the timestamping platform." } } ], "procurement": { "marketMaturity": "nascent", "primaryMode": "integrator-led", "alternativeModes": [ "rfq" ], "reasoning": "Witness testimony timestamping platforms emerging in legal-tech.", "exampleProductCategories": [ "testimony-timestamping-platform", "legal-tech-evidence-rails" ], "partnerChannels": [], "lastReviewed": "2026-05-01" } }, { "id": "UC-G-098", "name": "Displacement tracking and verification", "category": "G", "subcategory": "Population Movement", "description": "Keep checked records of where displaced people came from and where they went, shared safely across the organisations helping them.", "bCriteria": [ "B1", "B3", "B6" ], "requiredComponents": [ "evidence-platform", "data-integrity-layer", "timestamping-service" ], "conditionalComponents": [ "smart-contracts" ], "crossCategoryDependencies": [ "UC-H-106" ], "p2TriggerConditions": { "description": "Activated when P2 shows displacement contexts with multi-stakeholder coordination needs and sensitive data handling requirements", "rangeSignals": [ "displacementContext >=3", "multiStakeholder >=2", "dataSensitivity >=3" ] }, "contextFieldsTemplate": [ "displaced_population_estimate", "geographic_origin_coverage", "destination_tracking_scope", "registration_touchpoints", "privacy_protection_level", "aid_eligibility_verification", "data_sharing_permissions" ], "implementationComplexity": "high", "examples": { "note": "UNHCR displacement data integration", "references": [ { "name": "UNHCR PRIMES", "url": "https://www.unhcr.org/registration", "solved": "Population Registration and Identity Management Ecosystem; reference standard for refugee and IDP registration." }, { "name": "IOM DTM", "url": "https://dtm.iom.int", "solved": "Displacement Tracking Matrix; primary tool for global displacement monitoring across humanitarian operations." }, { "name": "iRespond", "url": "https://www.irespond.org", "solved": "Biometric identity for displaced populations with explicit consent and portability design." } ] }, "propertyMapping": {}, "solutionQuestions": [ { "id": "population-scale", "type": "select", "options": [ { "label": "Small-scale: <10,000 individuals", "value": "small-scale" }, { "label": "Medium-scale: 10,000-100,000 individuals", "value": "medium-scale" }, { "label": "Large-scale: >100,000 individuals", "value": "large-scale" } ], "prefillFrom": null, "briefSection": "Evidence capture", "propertyMapping": { "small-scale": { "technologies": [ "Centralized database", "Manual tracking" ], "technologyProperties": { "infrastructure": "low-tech-compatible", "scalability": "limited" } }, "medium-scale": { "technologies": [ "Distributed ledger", "Mobile data collection" ], "technologyProperties": { "nodes": "5-10", "capacity": "high" } }, "large-scale": { "technologies": [ "Scalable blockchain (Layer-2)", "Mass biometric registration" ], "technologyProperties": { "throughput": "1000+ registrations/day", "indexing": "optimized" } } }, "text": "What scale of displaced population will be tracked?", "ngoText": "What scale of displaced population will be tracked?" }, { "id": "tracking-scope", "type": "select", "options": [ { "label": "Origin only: Record where people came from", "value": "origin-only" }, { "label": "Origin + destination: Beginning and end point tracking", "value": "origin-destination" }, { "label": "Full path: Origin, transit, destination, and ongoing", "value": "full-journey" } ], "prefillFrom": "NGO-P0-S1-Q7", "briefSection": "Monitoring and alerts", "propertyMapping": { "origin-only": { "technologies": [ "Baseline registration", "Geographic mapping" ], "technologyProperties": { "dataCollection": "single-point", "complexity": "low" } }, "origin-destination": { "technologies": [ "Multi-touchpoint registration", "Location verification" ], "technologyProperties": { "registrationPoints": "2", "verificationMethod": "biometric" } }, "full-journey": { "technologies": [ "Continuous tracking", "Mobile check-in system" ], "technologyProperties": { "touchPoints": "5+", "realTimeMonitoring": "true" } } }, "text": "What tracking scope is covered (origin, transit, destination)?", "ngoText": "What tracking scope is covered (origin, transit, destination)?" }, { "id": "registration-touchpoints", "type": "select", "options": [ { "label": "Centralized: Fixed registration sites (camps, offices)", "value": "centralized-sites" }, { "label": "Mobile: Field teams conduct registration at communities", "value": "mobile-teams" }, { "label": "Multi-channel: Fixed + mobile + self-service online", "value": "multi-channel" } ], "prefillFrom": null, "briefSection": "Infrastructure requirements", "propertyMapping": { "centralized-sites": { "technologies": [ "Stationary registration centers", "Biometric kiosks" ], "technologyProperties": { "siteCount": "1-3", "accessibility": "geographic-limited" } }, "mobile-teams": { "technologies": [ "Mobile data collection app", "Offline-first sync" ], "technologyProperties": { "coverage": "dispersed-settlements", "connectivity": "intermittent" } }, "multi-channel": { "technologies": [ "Omnichannel registration", "USSD/web interface" ], "technologyProperties": { "channels": [ "fixed-site", "mobile-team", "self-service" ], "accessibility": "maximum" } } }, "text": "Where and when are registration touchpoints located?", "ngoText": "Where and when are registration touchpoints located?" }, { "id": "privacy-protection", "type": "select", "options": [ { "label": "Minimal data: Only essential identifiers stored", "value": "minimal-data" }, { "label": "Encrypted storage: Data encrypted at rest and in transit", "value": "encrypted-storage" }, { "label": "privacy-preserving verification: Verification without data exposure", "value": "zero-knowledge" } ], "prefillFrom": null, "briefSection": "Data integrity", "propertyMapping": { "minimal-data": { "technologies": [ "Data minimization policy", "Limited fields" ], "technologyProperties": { "dataPoints": "3-5", "retentionPeriod": "12-months" } }, "encrypted-storage": { "technologies": [ "AES-256 encryption", "TLS transport" ], "technologyProperties": { "encryptionStandard": "government-grade", "keyManagement": "independent-holders" } }, "zero-knowledge": { "technologies": [ "zkSNARK proofs", "Selective disclosure" ], "technologyProperties": { "dataExposure": "none", "proofVerification": "Digital" } } }, "text": "How is personal data privacy protected in displacement tracking?", "ngoText": "How is personal data privacy protected in displacement tracking?" }, { "id": "data-sharing-permissions", "type": "select", "options": [ { "label": "Closed: Data shared only with direct implementing partners", "value": "closed-sharing" }, { "label": "Semi-open: Aggregated data shared with authorized organizations", "value": "semi-open" }, { "label": "Open: De-identified data available for research/analysis", "value": "open-sharing" } ], "prefillFrom": null, "briefSection": "Reporting and audit", "propertyMapping": { "closed-sharing": { "technologies": [ "Access control list", "Multi-sig approvals" ], "technologyProperties": { "partnerCount": "fixed-list", "shareApproval": "individual-consent" } }, "semi-open": { "technologies": [ "Data aggregation", "Differential privacy" ], "technologyProperties": { "dataFormat": "anonymized-aggregate", "accessTier": "registered-partners" } }, "open-sharing": { "technologies": [ "Public dataset", "De-identification algorithm" ], "technologyProperties": { "publicAccess": "true", "reIdentificationRisk": "<0.5%" } } }, "text": "What data do you currently share with humanitarian partners, and how?", "ngoText": "What data do you currently share with humanitarian partners, and how?" }, { "id": "evidence-platform-approach", "type": "select", "options": [ { "label": "distributed storage/distributed storage with digital ledger tamper-proof verification", "value": "ipfs-anchored" }, { "label": "Cloud storage with periodic digital ledger proof checkpoints", "value": "cloud-anchored" }, { "label": "Digital metadata with separate encrypted file storage", "value": "hybrid-storage" }, { "label": "Not sure, need guidance on evidence storage", "value": "guidance-needed" } ], "propertyMapping": { "ipfs-anchored": { "technologies": [ "Decentralised-storage evidence platform", "Data integrity verification layer", "Content-addressed storage service" ], "technologyProperties": { "storageMethod": "Decentralised storage network", "integrityProof": "Content hash on blockchain", "redundancy": "Distributed across multiple nodes" } }, "cloud-anchored": { "technologies": [ "Cloud evidence platform", "Data integrity verification layer", "Periodic proof checkpoint service" ], "technologyProperties": { "storageMethod": "Commercial cloud storage", "integrityProof": "Periodic Merkle root on blockchain", "redundancy": "Cloud provider redundancy" } }, "hybrid-storage": { "technologies": [ "Hybrid evidence platform", "Data integrity verification layer", "Encrypted off-chain storage" ], "technologyProperties": { "storageMethod": "Digital metadata + encrypted off-chain files", "integrityProof": "Digital hash per document", "redundancy": "Configurable" } }, "guidance-needed": { "technologies": [ "Evidence platform framework", "Data integrity verification layer" ], "technologyProperties": { "storageMethod": "To be determined", "integrityProof": "To be determined", "redundancy": "To be determined" } } }, "prefillFrom": null, "briefSection": "Evidence and data integrity", "text": "How is evidence and documents currently stored and verified?", "ngoText": "How is evidence and documents currently stored and verified?" }, { "id": "timestamping-approach", "type": "select", "options": [ { "label": "Digital timestamping (each event anchored with tamper-proof proof)", "value": "on-chain" }, { "label": "Batch anchoring (events collected, periodically anchored)", "value": "batch-anchoring" }, { "label": "Trusted third-party timestamping authority", "value": "trusted-authority" }, { "label": "Not sure, need guidance on timestamping approach", "value": "guidance-needed" } ], "propertyMapping": { "on-chain": { "technologies": [ "On-chain timestamping service", "Event hash generation", "Timestamp verification API" ], "technologyProperties": { "timestampMethod": "Per-event Digital anchoring", "latency": "Near-instant (block confirmation time)", "legalAdmissibility": "Strong \u2014 independent blockchain proof" } }, "batch-anchoring": { "technologies": [ "Batch timestamping service", "Merkle tree aggregation", "Timestamp verification API" ], "technologyProperties": { "timestampMethod": "Periodic batch anchoring (hourly/daily)", "latency": "Batch interval", "legalAdmissibility": "Strong \u2014 Merkle proof to blockchain" } }, "trusted-authority": { "technologies": [ "Trusted timestamping authority integration", "RFC 3161 timestamping service", "Timestamp verification API" ], "technologyProperties": { "timestampMethod": "Trusted third-party authority", "latency": "Near-instant", "legalAdmissibility": "Varies by jurisdiction" } }, "guidance-needed": { "technologies": [ "Timestamping service framework", "Timestamp verification API" ], "technologyProperties": { "timestampMethod": "To be determined", "latency": "To be determined", "legalAdmissibility": "To be determined" } } }, "prefillFrom": null, "briefSection": "Evidence and timestamping", "text": "How is events and evidence currently timestamped for this solution?", "ngoText": "How is events and evidence currently timestamped for this solution?" } ], "complexityFactors": { "relationships": 4, "operationalChange": 3, "dataCompliance": 5 }, "securityTier": "B", "suggestedCriteria": [ { "id": "SC-G098-PRIVACY", "name": "Privacy-Preserving Data Collection", "description": "This measures how effectively the system protects the personal data of displaced populations during collection, storage, and sharing. Displaced persons are among the most vulnerable data subjects. Breaches can lead to targeting, discrimination, or refoulement.", "weight": 0.3, "ratingGuide": { "5": "Privacy-by-design architecture. Data minimisation enforced \u2014 collects only what is operationally necessary. Supports pseudonymised and anonymised datasets for sharing. Consent management built in with multilingual support. Compliant with UNHCR data protection policy and GDPR principles.", "4": "Data minimisation configurable. Pseudonymisation available. Consent tracking present. Aligned with UNHCR data protection principles.", "3": "Standard data protection (encryption at rest and in transit). Consent recorded. No built-in data minimisation or pseudonymisation.", "2": "Basic encryption. Consent recorded informally. No data minimisation enforcement. Full personal data stored by default.", "1": "No privacy protections. Personal data of displaced persons stored in plaintext. No consent management." } }, { "id": "SC-G098-INTEROP", "name": "Humanitarian Data Sharing & Interoperability", "description": "The system can share displacement data with UNHCR, IOM, and other humanitarian actors while maintaining data governance. Displacement tracking is inherently multi-agency. Siloed systems create duplicate registrations and aid gaps.", "weight": 0.25, "ratingGuide": { "5": "Supports interoperability with UN agency registration systems. Data sharing agreements enforceable within the platform (who can see what, for how long). Supports HDX (Humanitarian Data Exchange) format exports. De-identification for aggregate sharing. Real-time or near-real-time data exchange.", "4": "Interoperable with one major system (UNHCR or IOM). Data sharing controls configurable. Standard format exports. Near-real-time exchange.", "3": "Data exportable in standard formats. Sharing controls basic (all or nothing). No direct system integration. Batch export only.", "2": "Custom export format. Manual data sharing process. Limited controls on shared data usage.", "1": "No data sharing capability. Data locked within the system. Partner agencies must re-collect information." } }, { "id": "SC-G098-REGISTER", "name": "Multi-Touchpoint Registration Coverage", "description": "The system can capture and reconcile displacement data from multiple registration points (border crossings, transit centres, camps, urban areas). Displaced persons interact with multiple systems. Deduplication and data reconciliation are essential.", "weight": 0.2, "ratingGuide": { "5": "Supports 10+ concurrent registration points with real-time deduplication. Biometric or multi-factor identity matching to prevent duplicate registration. Handles both planned (camp registration) and unplanned (spontaneous arrival) touchpoints. Works across urban and camp settings.", "4": "Supports 5+ registration points. Near-real-time deduplication. Identity matching with basic biometrics or document verification.", "3": "Supports multiple registration points with batch deduplication. Manual identity matching. Designed primarily for camp settings.", "2": "Supports 1-2 registration points. Deduplication requires manual review. Not designed for mobile or urban registration.", "1": "Single registration point only. No deduplication. No ability to reconcile records from different locations." } }, { "id": "SC-G098-AID", "name": "Aid Eligibility Verification", "description": "Displacement status can be verified and linked to aid eligibility without revealing unnecessary personal information. The connection between displacement verification and aid delivery is where tracking creates tangible value for affected populations.", "weight": 0.15, "ratingGuide": { "5": "Displacement status verification linked to aid distribution systems. Supports selective disclosure \u2014 aid provider confirms eligibility without accessing full displacement record. Prevents double-dipping across aid programmes. Real-time eligibility checking.", "4": "Displacement status linked to aid eligibility. Basic selective disclosure. Cross-programme duplicate checking. Near-real-time verification.", "3": "Displacement records available for aid eligibility determination. No selective disclosure \u2014 aid providers see full record. Manual duplicate checking.", "2": "Displacement records separate from aid systems. Manual verification process. No cross-programme coordination.", "1": "No linkage between displacement tracking and aid delivery. Eligibility determined through separate processes entirely." } }, { "id": "SC-G098-FIELD", "name": "Offline & Field Durability", "description": "The system can operate in displacement contexts where connectivity is intermittent or absent. Registration points at borders, transit camps, and remote areas often lack reliable internet. The system must function regardless.", "weight": 0.1, "ratingGuide": { "5": "Full offline registration capability with local data storage and encryption. Automatic sync and deduplication on reconnection. Works on low-cost Android devices. Battery-efficient operation. Field-tested in actual displacement responses.", "4": "Offline registration with local encryption. Sync on reconnection. Works on mid-range smartphones. Tested in field conditions.", "3": "Limited offline capability (can capture data but no local deduplication). Requires connectivity for most operations. Works on standard devices.", "2": "Requires connectivity for registration. Can cache form data briefly during dropouts. Requires laptop or tablet.", "1": "No offline capability. Full internet required. Cannot operate in typical displacement response field conditions." } } ], "procurement": { "marketMaturity": "emerging", "primaryMode": "integrator-led", "alternativeModes": [ "rfq" ], "reasoning": "Displacement tracking platforms exist (DTM/IDMC) with growing maturity.", "exampleProductCategories": [ "displacement-tracking-platform", "idp-records-rails" ], "partnerChannels": [], "lastReviewed": "2026-05-01" } }, { "id": "UC-H-099", "name": "Land registry and title documentation (post-conflict/disaster)", "category": "H", "subcategory": "Land Registration", "description": "Create or rebuild land registers in areas hit by conflict or disaster, so people can show that they own their land.", "bCriteria": [ "B1", "B3", "B4" ], "requiredComponents": [ "registry-platform", "title-documentation", "mapping-integration", "government-interoperability" ], "conditionalComponents": [ "dispute-resolution-layer", "community-validation" ], "crossCategoryDependencies": [ "UC-H-106", "UC-G-098" ], "p2TriggerConditions": { "description": "Activated when P2 shows land disputes in post-conflict or disaster settings with absent or destroyed registries and government engagement", "rangeSignals": [ "landDisputes >=3", "registryExistent <=1", "governmentEngagement >=2" ] }, "contextFieldsTemplate": [ "land_parcels_to_register", "geographic_area_size", "existing_documentation_quality", "government_capacity", "customary_vs_statutory_balance", "dispute_prevalence_rate", "mapping_technology_available" ], "implementationComplexity": "high", "examples": { "note": "Puntland land registry, Rwanda post-genocide work", "references": [ { "name": "Medici Land Governance Registry", "description": "Blockchain-based land registration system in East Africa with government integration", "year": 2020, "relevance": "high", "technologies": [ "Hyperledger Fabric", "Government APIs" ] }, { "name": "Bitland Ghana Property Registry", "description": "Decentralised land title documentation platform for property rights verification", "year": 2015, "relevance": "high", "technologies": [ "Bitcoin", "Metadata Storage" ] }, { "name": "Rwanda Post-Genocide Land Cadastre Digitization", "description": "Government-led digitisation of land records after conflict with community validation", "year": 2012, "relevance": "high", "technologies": [ "GIS", "Government Systems" ] } ] }, "briefSection": "Registry platform", "solutionQuestions": [ { "id": "registry-model", "type": "select", "options": [ { "label": "Centralized government land registry with digital ledger audit trail", "value": "centralized-audit" }, { "label": "Distributed land registry ledger with multi-stakeholder validation", "value": "distributed-multi" }, { "label": "Hybrid model with centralized storage and distributed verification", "value": "hybrid-verification" } ], "prefillFrom": null, "briefSection": "Registry platform", "propertyMapping": { "centralized-audit": { "technologies": [ "Permissioned shared ledger", "Government Land Information System" ], "technologyProperties": { "architecture": "centralized", "auditLayer": "distributed ledger", "dataGovernance": "state-controlled" } }, "distributed-multi": { "technologies": [ "Permissioned ledger with need-to-know data sharing", "Audited smart contract library" ], "technologyProperties": { "architecture": "distributed", "consensus": "notary-based", "stakeholders": "multiple" } }, "hybrid-verification": { "technologies": [ "Public smart-contract network", "Decentralised content-addressed storage" ], "technologyProperties": { "architecture": "hybrid", "storage": "Distributed", "verification": "blockchain-based" } } }, "text": "How do you currently maintain land or property records in your context?", "ngoText": "How do you currently maintain land or property records in your context?" }, { "id": "land-surveying-tech", "type": "select", "options": [ { "label": "Satellite-verified boundary engine with SAR/optical imagery", "value": "satellite-verified" }, { "label": "GPS and drone-based surveying with real-time boundary mapping", "value": "gps-drone-survey" }, { "label": "GIS and digital record system with historical boundary tracking", "value": "gis-blockchain-layer" }, { "label": "Community-annotated maps with participatory boundary validation", "value": "community-annotated" } ], "prefillFrom": null, "briefSection": "Mapping and geospatial", "propertyMapping": { "satellite-verified": { "technologies": [ "Open satellite imagery", "Commercial high-resolution satellite imagery" ], "technologyProperties": { "resolution": "5-10m", "updateFrequency": "monthly", "automatedBoundaryDetection": "yes" } }, "gps-drone-survey": { "technologies": [ "RTK-GPS", "DJI Enterprise" ], "technologyProperties": { "accuracy": "2-5cm", "realTime": "yes", "droneOrtho": "enabled" } }, "gis-blockchain-layer": { "technologies": [ "QGIS", "PostGIS", "Public smart-contract network" ], "technologyProperties": { "gisIntegration": "native", "boundaryVersioning": "yes", "historicalTracking": "enabled" } }, "community-annotated": { "technologies": [ "OpenStreetMap", "Web mapping platform" ], "technologyProperties": { "crowdsourced": "yes", "participatory": "yes", "validation": "consensus-based" } } }, "text": "For land surveying, what technology and precision is needed: GPS/handheld devices, drone/UAV mapping, satellite imagery, or traditional surveying?", "ngoText": "For land surveying, what technology and precision is needed: GPS/handheld devices, drone/UAV mapping, satellite imagery, or traditional surveying?" }, { "id": "government-integration", "type": "select", "options": [ { "label": "Direct connection to government systems and data feeds", "value": "api-integration" }, { "label": "Digital system with regulatory approval workflows", "value": "blockchain-interop" }, { "label": "Notarized digital ledger proofs submitted to government registry", "value": "notarized-proofs" } ], "prefillFrom": null, "briefSection": "Government interoperability", "propertyMapping": { "api-integration": { "technologies": [ "REST APIs", "OAuth 2.0" ], "technologyProperties": { "apiStandard": "REST", "authentication": "OAuth2", "dataSync": "real-time" } }, "blockchain-interop": { "technologies": [ "Permissioned shared ledger", "Smart Contracts" ], "technologyProperties": { "governance": "blockchain-based", "approvalWorkflow": "automated", "regulatoryCompliance": "yes" } }, "notarized-proofs": { "technologies": [ "Public smart-contract network", "Verifiable Credentials" ], "technologyProperties": { "notarization": "yes", "trustAnchor": "blockchain", "governmentAcceptance": "required" } } }, "text": "Is government land agency integration: required by law, optional but preferred, or not part of your scope?", "ngoText": "Is government land agency integration: required by law, optional but preferred, or not part of your scope?", "hidden": true }, { "id": "dispute-handling-mechanism", "type": "select", "options": [ { "label": "Multi-tiered resolution: automated for clear cases, escalation for complex ones", "value": "multi-tiered-resolution-automated-for-cl" }, { "label": "Community mediation with government appeal pathway", "value": "community-mediation-with-government-appe" }, { "label": "Formal adjudication with structured evidence collection", "value": "formal-adjudication-with-structured-evid" }, { "label": "Not sure, need guidance", "value": "not-sure-need-guidance" } ], "prefillFrom": null, "briefSection": "Dispute resolution", "propertyMapping": { "multi-tier-arbitration": { "technologies": [ "Smart Contracts", "Oasis Protocol" ], "technologyProperties": { "tiers": "three-level", "evidenceChain": "immutable", "arbitrationAutomation": "partial" } }, "community-mediation": { "technologies": [ "Blockchain Evidence Trail", "Smart Contracts" ], "technologyProperties": { "mediationSupport": "yes", "appealPath": "linear", "documentedOutcomes": "yes" } }, "automated-consensus": { "technologies": [ "Smart Contracts", "Oracle Network" ], "technologyProperties": { "automation": "yes", "consensusRequired": "yes", "manualOverride": "enabled" } } }, "text": "For disputes, do you currently have: formal court processes, community elders/traditional mechanisms, administrative appeal, or none? Which should the system support?", "ngoText": "For disputes, do you currently have: formal court processes, community elders/traditional mechanisms, administrative appeal, or none? Which should the system support?", "question": "For disputes, what mechanisms does the system need to support?" }, { "id": "documentation-quality-baseline", "type": "select", "options": [ { "label": "Multi-source document verification with confidence scoring", "value": "doc-confidence-scoring" }, { "label": "Forensic document analysis with digital ledger timestamping", "value": "forensic-analysis" }, { "label": "Legacy system migration with verification checkpoint layers", "value": "legacy-migration" } ], "prefillFrom": null, "briefSection": "Registry platform", "propertyMapping": { "doc-confidence-scoring": { "technologies": [ "OCR Technology", "Machine Learning" ], "technologyProperties": { "multiSource": "yes", "confidenceScoring": "enabled", "documentTypes": "heterogeneous" } }, "forensic-analysis": { "technologies": [ "Blockchain Timestamps", "Digital Forensics" ], "technologyProperties": { "authenticity": "verified", "tamperDetection": "yes", "historicalProof": "yes" } }, "legacy-migration": { "technologies": [ "Data Migration Tools", "Smart Contracts" ], "technologyProperties": { "legacyIntegration": "yes", "checkpoints": "multiple", "validationAutomation": "high" } } }, "text": "What baseline would you need for documentation quality in land and resource management?", "ngoText": "What baseline would you need for documentation quality in land and resource management?" }, { "id": "post-conflict-recovery-framework", "type": "select", "options": [ { "label": "Transitional justice model with truth commission digital ledger archive", "value": "transitional-justice" }, { "label": "Reparations tracking with digitally certified land claims", "value": "reparations-tracking" }, { "label": "Community-led restitution with elder council mediation and digital records", "value": "community-led" }, { "label": "Combined approach: government law + community testimony + documented ownership", "value": "combined" }, { "label": "Not sure, context-dependent, need guidance", "value": "unsure" } ], "prefillFrom": null, "briefSection": "Registry platform", "propertyMapping": { "transitional-justice": { "technologies": [ "Immutable Ledger", "ZK-Proofs" ], "technologyProperties": { "truthArchive": "permanent", "privacyPreserving": "yes", "lustrationSupport": "yes" } }, "reparations-tracking": { "technologies": [ "ERC-20 Tokens", "Smart Contracts" ], "technologyProperties": { "tokenizedClaims": "yes", "reparationsAutomation": "yes", "beneficiaryTracking": "yes" } }, "community-led": { "technologies": [ "Community mediation platform", "Elder council decision log" ], "technologyProperties": { "restitutionModel": "Community-led", "mediationAuthority": "Elder council", "evidenceBase": "Testimony + community consensus" } }, "combined": { "technologies": [ "Multi-source evidence platform", "Hybrid dispute resolution" ], "technologyProperties": { "restitutionModel": "Combined", "mediationAuthority": "Multi-tier", "evidenceBase": "Government records + testimony + ownership docs" } }, "unsure": { "technologies": [ "Restitution framework assessment needed" ], "technologyProperties": { "restitutionModel": "TBD", "mediationAuthority": "TBD", "evidenceBase": "TBD" } } }, "text": "For post-conflict restitution, should decisions be guided by: pre-conflict ownership records, claimant testimony, community consensus, government restitution law, or combination?", "ngoText": "For post-conflict restitution, should decisions be guided by: pre-conflict ownership records, claimant testimony, community consensus, government restitution law, or combination?" }, { "id": "registry-platform-approach", "type": "select", "options": [ { "label": "Government-integrated registry (supplement existing land authority)", "value": "gov-integrated" }, { "label": "Standalone digital ledger registry (parallel to government system)", "value": "standalone-chain" }, { "label": "Community-managed registry with local authority endorsement", "value": "community-managed" }, { "label": "Not sure, need guidance on registry approach", "value": "guidance-needed" } ], "propertyMapping": { "gov-integrated": { "technologies": [ "Government-integrated registry platform", "Authority system connection", "Registry verification service" ], "technologyProperties": { "legalStatus": "Government-recognised", "managedBy": "Government authority with blockchain backend", "disputeResolution": "Through existing legal channels" } }, "standalone-chain": { "technologies": [ "Standalone blockchain registry platform", "Decentralised registry service", "Registry verification service" ], "technologyProperties": { "legalStatus": "Evidence-grade (may require legal framework)", "managedBy": "NGO/consortium-operated", "disputeResolution": "Automatedarbitration + legal" } }, "community-managed": { "technologies": [ "Community registry platform", "Local authority endorsement module", "Registry verification service" ], "technologyProperties": { "legalStatus": "Community-endorsed with local authority backing", "managedBy": "Community with NGO facilitation", "disputeResolution": "Community governance + mediation" } }, "guidance-needed": { "technologies": [ "Registry platform framework", "Registry verification service" ], "technologyProperties": { "legalStatus": "To be determined", "managedBy": "To be determined", "disputeResolution": "To be determined" } } }, "prefillFrom": null, "briefSection": "Registry design", "text": "What type of registry platform is appropriate for this context?", "ngoText": "What type of registry platform is appropriate for this context?" }, { "id": "title-documentation-approach", "type": "select", "options": [ { "label": "Formal title deeds with digital ledger registration", "value": "formal-deeds" }, { "label": "Occupancy certificates (intermediate documentation)", "value": "occupancy-certs" }, { "label": "Customary rights documentation with community attestation", "value": "customary-rights" }, { "label": "Progressive titling: start informal, formalise over time", "value": "progressive" } ], "propertyMapping": { "formal-deeds": { "technologies": [ "Formal title documentation system", "Title deed generation service", "Title verification portal" ], "technologyProperties": { "documentType": "Formal title deed", "legalRecognition": "Full legal title", "issuingAuthority": "Government land authority" } }, "occupancy-certs": { "technologies": [ "Occupancy certificate system", "Intermediate title documentation", "Title verification portal" ], "technologyProperties": { "documentType": "Occupancy/use certificate", "legalRecognition": "Intermediate \u2014 use rights", "issuingAuthority": "Local authority or NGO-facilitated" } }, "customary-rights": { "technologies": [ "Customary rights documentation system", "Community attestation module", "Title verification portal" ], "technologyProperties": { "documentType": "Customary rights record", "legalRecognition": "Community-endorsed (varies by jurisdiction)", "issuingAuthority": "Community elders/leaders + NGO witness" } }, "progressive": { "technologies": [ "Progressive titling platform", "Multi-stage title documentation", "Title verification portal" ], "technologyProperties": { "documentType": "Progressive \u2014 informal to formal", "legalRecognition": "Incremental formalisation", "issuingAuthority": "Community \u2192 local authority \u2192 government" } } }, "prefillFrom": null, "briefSection": "Title documentation", "text": "What type of title or rights documentation is appropriate?", "ngoText": "What type of title or rights documentation is appropriate?" }, { "id": "mapping-integration", "type": "select", "options": [ { "label": "GIS/satellite mapping integration", "value": "gis-satellite" }, { "label": "Community-drawn boundary mapping", "value": "community-mapping" }, { "label": "Government cadastral system integration", "value": "cadastral" }, { "label": "Mobile GPS-based mapping", "value": "mobile-gps" } ], "propertyMapping": { "gis-satellite": { "technologies": [ "GIS mapping integration", "Satellite imagery service", "Boundary verification engine" ], "technologyProperties": { "mappingMethod": "GIS + satellite imagery", "accuracy": "Sub-metre (with RTK GPS)", "legalRecognition": "Depends on jurisdiction" } }, "community-mapping": { "technologies": [ "Community mapping platform", "Participatory boundary tool", "Community attestation module" ], "technologyProperties": { "mappingMethod": "Community-drawn on mobile/tablet", "accuracy": "Approximate (community agreed)", "legalRecognition": "Community-endorsed" } }, "cadastral": { "technologies": [ "Cadastral mapping integration", "Government system connection", "Parcel verification service" ], "technologyProperties": { "mappingMethod": "Government cadastral data", "accuracy": "Official survey accuracy", "legalRecognition": "Government-recognised" } }, "mobile-gps": { "technologies": [ "Mobile GPS mapping tool", "Walk-the-boundary capture app", "GPS coordinate verification" ], "technologyProperties": { "mappingMethod": "Mobile GPS walk-the-boundary", "accuracy": "3-10 metre (consumer GPS)", "legalRecognition": "Evidence-grade (not survey-grade)" } } }, "prefillFrom": null, "briefSection": "Mapping and spatial data", "text": "How are land or boundaries currently mapped?", "ngoText": "How are land or boundaries currently mapped?" } ], "complexityFactors": { "relationships": 5, "operationalChange": 4, "dataCompliance": 4 }, "securityTier": "B", "suggestedCriteria": [ { "id": "SC-GOV-RECOGNITION", "name": "Government Legal Recognition", "description": "Titles issued through this system are legally recognised by the national land authority. In post-conflict settings, parallel registries that lack government recognition leave holders vulnerable to future disputes.", "weight": 0.3, "ratingGuide": { "5": "Formal MOU or legislation recognising blockchain-issued titles as equivalent to government-issued titles. Provider has existing government partnerships in target jurisdictions.", "4": "Government engagement underway with strong likelihood of recognition. Provider has achieved legal recognition in comparable jurisdictions.", "3": "System designed for government interoperability but recognition not yet secured. Provider has experience navigating government approval processes.", "2": "Parallel system with no government engagement. Titles have evidentiary value only. No pathway to formal recognition articulated.", "1": "No government relationship. System operates entirely outside national land administration framework. Titles have no legal standing." } }, { "id": "SC-LONGEVITY", "name": "Record Longevity & Persistence", "description": "Land records can survive decades of political change, technology migration, and organisational transitions. Land registries must outlast any single government, NGO programme, or technology provider.", "weight": 0.25, "ratingGuide": { "5": "Decentralised storage with no single point of failure. Open data formats with documented migration paths. Records anchored to multiple independent chains. Provider has a 10+ year sustainability plan or records are self-sovereign.", "4": "Distributed storage across multiple nodes. Open standards. Clear data export and migration capability. 5+ year operational track record.", "3": "Replicated storage with backup strategy. Proprietary format but documented export. Provider sustainability plan exists but untested.", "2": "Centralised storage with backup. Proprietary format. Data export possible but not straightforward. Provider viability uncertain beyond 3 years.", "1": "Single-server storage. Proprietary locked-in format. No data portability. Provider is a startup with no sustainability plan." } }, { "id": "SC-DISPUTE-RESOLUTION", "name": "Dispute Resolution Integration", "description": "The system supports the full lifecycle of land disputes, from claim filing through evidence gathering to resolution and enforcement. Post-conflict land registries without dispute resolution mechanisms create new conflicts.", "weight": 0.2, "ratingGuide": { "5": "Integrated multi-tier dispute workflow: community mediation, administrative review, and formal adjudication. Immutable evidence chain. Support for overlapping and competing claims. Tested in post-conflict settings.", "4": "Dispute tracking with evidence management and escalation pathways. Supports multiple claim types. Some post-conflict deployment experience.", "3": "Basic dispute logging and tracking. Evidence attachment capability. Single resolution pathway. No post-conflict-specific features.", "2": "Dispute flagging only \u2014 no resolution workflow. Evidence stored separately. Manual tracking required for resolution.", "1": "No dispute handling. System assumes clean title issuance only. Competing claims cannot be recorded." } }, { "id": "SC-GIS-MAPPING", "name": "Geospatial & Boundary Mapping", "description": "The system can capture, store, and verify land boundaries using appropriate technology for the context, from satellite imagery to community-drawn maps. Post-conflict areas often lack survey infrastructure.", "weight": 0.15, "ratingGuide": { "5": "Multiple mapping methods supported (satellite, drone, GPS, community sketch). GIS integration with boundary versioning. Handles overlapping boundaries and progressive refinement from approximate to survey-grade.", "4": "GPS and GIS integration with at least two mapping methods. Boundary versioning supported. Can work with imprecise initial boundaries.", "3": "Single GIS integration method. GPS coordinate capture. Static boundary records without versioning.", "2": "Manual coordinate entry only. No GIS integration. Boundaries stored as text descriptions rather than geospatial data.", "1": "No spatial data capability. Title records are text-only with no boundary information." } }, { "id": "SC-COMMUNITY-CONSENT", "name": "Community Consent & Participation", "description": "The registration processes include meaningful community participation and consent. Land registration imposed without community buy-in, especially in post-conflict settings, risks formalising unjust seizures or excluding vulnerable groups.", "weight": 0.1, "ratingGuide": { "5": "Structured community validation workflows with public objection periods, elder/leader attestation, and gender-inclusive participation requirements. Multi-language support. Accessible to illiterate participants.", "4": "Community notification and objection period built in. Leader attestation supported. Some accessibility features for non-literate participants.", "3": "Community notification included but passive (posted notice). No structured objection workflow. Assumes literate participants.", "2": "Minimal community involvement. Registration is primarily administrative. No objection mechanism.", "1": "No community participation. Top-down registration only. No safeguards against formalising contested or unjust claims." } } ], "procurement": { "marketMaturity": "nascent", "primaryMode": "consortium", "alternativeModes": [ "integrator-led" ], "reasoning": "Land registry post-conflict is research-stage; consortium with state involvement common.", "exampleProductCategories": [ "land-registry-platform", "property-rights-rails" ], "partnerChannels": [], "lastReviewed": "2026-05-01" } }, { "id": "UC-H-100", "name": "Property rights documentation for displaced populations", "category": "H", "subcategory": "Displaced Persons", "description": "Record and check property claims made by displaced people, without exposing where they are now to the authorities they fled.", "bCriteria": [ "B1", "B3", "B6" ], "requiredComponents": [ "claims-management", "title-documentation", "evidence-platform", "audit-trail" ], "conditionalComponents": [ "dispute-resolution-layer", "government-interoperability" ], "crossCategoryDependencies": [ "UC-G-098", "UC-H-106" ], "p2TriggerConditions": { "description": "Activated when P2 shows displaced populations with property disputes and claims management challenges", "rangeSignals": [ "displacementContext >=3", "propertyDisputes >=3", "claimsManagement >=2" ] }, "contextFieldsTemplate": [ "displaced_population_estimate", "property_claim_types", "documentation_evidence_availability", "verification_methodology", "dispute_resolution_process", "government_recognition_status", "durable_solution_timeline" ], "implementationComplexity": "high", "examples": { "note": "IDMC and NRC property documentation", "references": [ { "name": "International Committee of the Red Cross Property Restitution System", "description": "ICRC framework for documenting displaced property claims across conflict zones", "year": 2015, "relevance": "high", "technologies": [ "Database Systems", "Case Management" ] }, { "name": "Bitland Ghana Displaced Persons Project", "description": "Blockchain-based property rights documentation for internally displaced persons", "year": 2017, "relevance": "high", "technologies": [ "Blockchain", "Mobile Registration" ] }, { "name": "UN-Habitat Housing Rights Documentation", "description": "Standardised property claim documentation and verification methodology", "year": 2018, "relevance": "medium", "technologies": [ "Documentation Standards", "Government Systems" ] } ] }, "briefSection": "Title documentation", "solutionQuestions": [ { "id": "claim-documentation-method", "type": "select", "options": [ { "label": "Digital claim forms with secure signing and timestamping", "value": "digital-signed-forms" }, { "label": "Multimedia affidavit system with photo/video evidence attachment", "value": "multimedia-affidavit" }, { "label": "Independent identity verification with portable personal credentials", "value": "ssi-credentials" } ], "prefillFrom": null, "briefSection": "Title documentation", "propertyMapping": { "digital-signed-forms": { "technologies": [ "PKI", "Blockchain Timestamps" ], "technologyProperties": { "digitallySigned": "yes", "tamperProof": "yes", "languageSupport": "multilingual" } }, "multimedia-affidavit": { "technologies": [ "Decentralised content-addressed storage", "Content Addressing" ], "technologyProperties": { "mediaTypes": "photo-video-audio", "contentAddressing": "yes", "metadata": "preserved" } }, "ssi-credentials": { "technologies": [ "DID", "Verifiable Credentials" ], "technologyProperties": { "identityModel": "self-sovereign", "privacyPreserving": "yes", "interoperable": "yes" } } }, "text": "For land claims, what evidence and documentation does your context typically have: government title deeds, written customary agreements, community witness testimony, oral history, or combination?", "ngoText": "For land claims, what evidence and documentation does your context typically have: government title deeds, written customary agreements, community witness testimony, oral history, or combination?" }, { "id": "evidence-types-acceptance", "type": "select", "options": [ { "label": "Documentary evidence (deeds, certificates, government records)", "value": "documentary-evidence" }, { "label": "Witness testimony with credibility scoring and cross-verification", "value": "witness-testimony" }, { "label": "Satellite/geospatial evidence with possession history mapping", "value": "geospatial-evidence" }, { "label": "Biometric identity linking with genealogical/familial documentation", "value": "biometric-genealogy" } ], "prefillFrom": null, "briefSection": "Title documentation", "propertyMapping": { "documentary-evidence": { "technologies": [ "Document Verification", "OCR" ], "technologyProperties": { "documentTypes": "heterogeneous", "authenticity": "verified", "automation": "high" } }, "witness-testimony": { "technologies": [ "Identity Verification", "Blockchain Records" ], "technologyProperties": { "credibilityScoring": "yes", "multipleWitnesses": "required", "conflictDetection": "yes" } }, "geospatial-evidence": { "technologies": [ "Open satellite imagery", "QGIS" ], "technologyProperties": { "temporalAnalysis": "yes", "possessionHistory": "mapped", "resolution": "10-30m" } }, "biometric-genealogy": { "technologies": [ "Biometric Registry", "Smart Contracts" ], "technologyProperties": { "privacyPreserving": "yes", "familyTracking": "yes", "uniqueIdentification": "yes" } } }, "text": "Which evidence types should be accepted for displaced property claims?", "ngoText": "Which evidence types should be accepted for displaced property claims?" }, { "id": "verification-process-design", "type": "select", "options": [ { "label": "Multi-stakeholder verification consortium with independent auditors", "value": "consortium-verification" }, { "label": "Community-based verification with peer review mechanism", "value": "community-verification" }, { "label": "Government agency verification with digital ledger attestation trail", "value": "government-attestation" } ], "prefillFrom": null, "briefSection": "Community validation", "propertyMapping": { "consortium-verification": { "technologies": [ "Smart Contracts", "Consensus Protocols" ], "technologyProperties": { "stakeholders": "multiple", "auditTrail": "immutable", "transparency": "high" } }, "community-verification": { "technologies": [ "Proof of Authority", "Governance Tokens" ], "technologyProperties": { "communityDriven": "yes", "peerReview": "yes", "incentives": "enabled" } }, "government-attestation": { "technologies": [ "Government Certificates", "Blockchain" ], "technologyProperties": { "officialAuthority": "yes", "attestationChain": "immutable", "appealProcess": "yes" } } }, "text": "What process would you need for verifying land and resource claims?", "ngoText": "What process would you need for verifying land and resource claims?" }, { "id": "government-recognition-pathway", "type": "select", "options": [ { "label": "Digital evidence submitted as proof in government recognition process", "value": "blockchain-evidence-submission" }, { "label": "automated rules-mediated claims with government certification output", "value": "smart-contract-mediation" }, { "label": "Notarized claims with official government land registry submission", "value": "notarized-registry-submission" } ], "prefillFrom": null, "briefSection": "Government interoperability", "propertyMapping": { "blockchain-evidence-submission": { "technologies": [ "Blockchain Proofs", "Verifiable Credentials" ], "technologyProperties": { "legalRecognition": "supported", "evidenceFormat": "standardized", "governmentIntegration": "yes" } }, "smart-contract-mediation": { "technologies": [ "Smart Contracts", "Oracle Networks" ], "technologyProperties": { "automatedCertification": "yes", "governmentIntegration": "yes", "appealMechanism": "yes" } }, "notarized-registry-submission": { "technologies": [ "Notarization Services", "Government Registry APIs" ], "technologyProperties": { "officialNotarization": "yes", "directSubmission": "yes", "confirmation": "automated" } } }, "text": "What is your goal: formal government registration, government recognition, or community-based documentation?", "ngoText": "What is your goal: formal government registration, government recognition, or community-based documentation?" }, { "id": "claim-portability-framework", "type": "select", "options": [ { "label": "Cross-border claim reciprocity with bilateral agreements", "value": "bilateral-reciprocity" }, { "label": "Standardized verifiable credential format for international transfer", "value": "vc-standard-transfer" }, { "label": "Single jurisdiction only: no cross-border recognition needed", "value": "single-jurisdiction" }, { "label": "Regional recognition within a country (e.g. across states or provinces)", "value": "regional" }, { "label": "Not sure, the displacement context makes this unclear", "value": "unsure" } ], "prefillFrom": null, "briefSection": "Title documentation", "propertyMapping": { "bilateral-reciprocity": { "technologies": [ "Smart Contracts", "Interoperability Protocols" ], "technologyProperties": { "crossBorder": "yes", "agreementAutomation": "yes", "reciprocal": "yes" } }, "vc-standard-transfer": { "technologies": [ "W3C Verifiable Credentials", "DID" ], "technologyProperties": { "standardFormat": "W3C-VC", "internationalization": "yes", "transferable": "yes" } }, "single-jurisdiction": { "technologies": [ "Local registry integration" ], "technologyProperties": { "jurisdictionScope": "Single", "crossBorderNeeded": "No", "formatStandard": "Local" } }, "regional": { "technologies": [ "Regional registry interoperability" ], "technologyProperties": { "jurisdictionScope": "Regional/sub-national", "crossBorderNeeded": "No \u2014 within country", "formatStandard": "National standard" } }, "unsure": { "technologies": [ "Jurisdiction assessment needed" ], "technologyProperties": { "jurisdictionScope": "TBD", "crossBorderNeeded": "TBD", "formatStandard": "TBD" } } }, "text": "Do land claims need to be recognised across multiple jurisdictions?", "ngoText": "Do land claims need to be recognised across multiple jurisdictions?" }, { "id": "claims-management-approach", "type": "select", "options": [ { "label": "Formal claims process with adjudication workflow", "value": "formal-adjudication" }, { "label": "Community-based mediation with digital ledger record", "value": "community-mediation" }, { "label": "Self-service claims portal with document upload", "value": "self-service" }, { "label": "Hybrid: self-service intake with formal adjudication", "value": "hybrid" } ], "propertyMapping": { "formal-adjudication": { "technologies": [ "Formal claims management system", "Adjudication workflow engine", "Claims tracking ledger" ], "technologyProperties": { "processType": "Formal adjudication", "evidenceHandling": "Document upload with hash verification", "resolutionMethod": "Authority-adjudicated" } }, "community-mediation": { "technologies": [ "Community claims management platform", "Mediation workflow module", "Claims tracking ledger" ], "technologyProperties": { "processType": "Community mediation", "evidenceHandling": "Witness testimony + document upload", "resolutionMethod": "Community-mediated agreement" } }, "self-service": { "technologies": [ "Self-service claims portal", "Document upload and verification", "Claims tracking ledger" ], "technologyProperties": { "processType": "Self-service with review", "evidenceHandling": "Claimant-uploaded evidence", "resolutionMethod": "Administrative review" } }, "hybrid": { "technologies": [ "Hybrid claims management system", "Multi-stage claims workflow", "Claims tracking ledger" ], "technologyProperties": { "processType": "Self-service intake \u2192 formal adjudication", "evidenceHandling": "Progressive evidence collection", "resolutionMethod": "Escalation from self-service to formal" } } }, "prefillFrom": null, "briefSection": "Claims and disputes", "text": "How should claims and disputes be managed?", "ngoText": "How should claims and disputes be managed?" }, { "id": "title-documentation-approach", "type": "select", "options": [ { "label": "Formal title deeds with digital ledger registration", "value": "formal-deeds" }, { "label": "Occupancy certificates (intermediate documentation)", "value": "occupancy-certs" }, { "label": "Customary rights documentation with community attestation", "value": "customary-rights" }, { "label": "Progressive titling: start informal, formalise over time", "value": "progressive" } ], "propertyMapping": { "formal-deeds": { "technologies": [ "Formal title documentation system", "Title deed generation service", "Title verification portal" ], "technologyProperties": { "documentType": "Formal title deed", "legalRecognition": "Full legal title", "issuingAuthority": "Government land authority" } }, "occupancy-certs": { "technologies": [ "Occupancy certificate system", "Intermediate title documentation", "Title verification portal" ], "technologyProperties": { "documentType": "Occupancy/use certificate", "legalRecognition": "Intermediate \u2014 use rights", "issuingAuthority": "Local authority or NGO-facilitated" } }, "customary-rights": { "technologies": [ "Customary rights documentation system", "Community attestation module", "Title verification portal" ], "technologyProperties": { "documentType": "Customary rights record", "legalRecognition": "Community-endorsed (varies by jurisdiction)", "issuingAuthority": "Community elders/leaders + NGO witness" } }, "progressive": { "technologies": [ "Progressive titling platform", "Multi-stage title documentation", "Title verification portal" ], "technologyProperties": { "documentType": "Progressive \u2014 informal to formal", "legalRecognition": "Incremental formalisation", "issuingAuthority": "Community \u2192 local authority \u2192 government" } } }, "prefillFrom": null, "briefSection": "Title documentation", "text": "What type of title or rights documentation is appropriate?", "ngoText": "What type of title or rights documentation is appropriate?" }, { "id": "evidence-platform-approach", "type": "select", "options": [ { "label": "distributed storage/distributed storage with digital ledger tamper-proof verification", "value": "ipfs-anchored" }, { "label": "Cloud storage with periodic digital ledger proof checkpoints", "value": "cloud-anchored" }, { "label": "Digital metadata with separate encrypted file storage", "value": "hybrid-storage" }, { "label": "Not sure, need guidance on evidence storage", "value": "guidance-needed" } ], "propertyMapping": { "ipfs-anchored": { "technologies": [ "Decentralised-storage evidence platform", "Data integrity verification layer", "Content-addressed storage service" ], "technologyProperties": { "storageMethod": "Decentralised storage network", "integrityProof": "Content hash on blockchain", "redundancy": "Distributed across multiple nodes" } }, "cloud-anchored": { "technologies": [ "Cloud evidence platform", "Data integrity verification layer", "Periodic proof checkpoint service" ], "technologyProperties": { "storageMethod": "Commercial cloud storage", "integrityProof": "Periodic Merkle root on blockchain", "redundancy": "Cloud provider redundancy" } }, "hybrid-storage": { "technologies": [ "Hybrid evidence platform", "Data integrity verification layer", "Encrypted off-chain storage" ], "technologyProperties": { "storageMethod": "Digital metadata + encrypted off-chain files", "integrityProof": "Digital hash per document", "redundancy": "Configurable" } }, "guidance-needed": { "technologies": [ "Evidence platform framework", "Data integrity verification layer" ], "technologyProperties": { "storageMethod": "To be determined", "integrityProof": "To be determined", "redundancy": "To be determined" } } }, "prefillFrom": null, "briefSection": "Evidence and data integrity", "text": "How is evidence and documents currently stored and verified?", "ngoText": "How is evidence and documents currently stored and verified?" }, { "id": "audit-trail-approach", "type": "select", "options": [ { "label": "Donors and external auditors need to independently verify any action at any time", "value": "donors-and-external-auditors-need-to-ind" }, { "label": "External auditors check periodically: summary reports and spot-checks are sufficient", "value": "external-auditors-check-periodically-sum" }, { "label": "Key milestones and approvals need independent verification; routine actions just need internal records", "value": "key-milestones-and-approvals-need-indepe" }, { "label": "Internal team records are sufficient: we mainly need our own staff to be able to look back", "value": "internal-team-records-are-sufficient-we-" }, { "label": "Not sure, need guidance on audit requirements", "value": "not-sure-need-guidance-on-audit-requirem" } ], "propertyMapping": { "full-immutable": { "technologies": [ "Immutable audit trail", "On-chain event logging", "Audit trail verification service" ], "technologyProperties": { "auditGranularity": "Every action", "storageApproach": "Full on-chain logging", "tamperEvidence": "Cryptographic hash chain" } }, "key-events": { "technologies": [ "Milestone-based audit trail", "Approval chain logger", "Audit trail verification service" ], "technologyProperties": { "auditGranularity": "Key milestones and approvals only", "storageApproach": "Selective on-chain logging", "tamperEvidence": "Merkle root anchoring" } }, "hybrid": { "technologies": [ "Hybrid audit trail system", "Off-chain storage with hash anchoring", "Audit trail verification service" ], "technologyProperties": { "auditGranularity": "Metadata on-chain, full records off-chain", "storageApproach": "Decentralised/off-chain storage with on-chain hash proofs", "tamperEvidence": "Hash anchoring to blockchain" } }, "guidance-needed": { "technologies": [ "Audit trail framework", "Audit trail verification service" ], "technologyProperties": { "auditGranularity": "To be determined during solution design", "storageApproach": "To be determined", "tamperEvidence": "To be determined" } } }, "prefillFrom": null, "briefSection": "Audit and evidence", "text": "What level of audit trail does this solution require?", "ngoText": "What level of audit trail does this solution require?", "hidden": true, "question": "Who needs to verify that actions in this system happened correctly, and how easily should they be able to check?" } ], "complexityFactors": { "relationships": 4, "operationalChange": 3, "dataCompliance": 4 }, "securityTier": "C", "suggestedCriteria": [ { "id": "SC-DISPLACEMENT-EVIDENCE", "name": "Evidence Flexibility for Displaced Claimants", "description": "Can the system accept diverse evidence types (oral testimony, photos, witness statements, satellite imagery, community attestation) given that displaced persons rarely have formal title deeds?", "weight": 0.25, "ratingGuide": { "5": "Accepts multimedia evidence (photo, video, audio testimony). Supports witness corroboration workflows. Satellite imagery comparison (pre/post displacement). Confidence scoring for evidence strength. Multilingual and accessible to non-literate claimants.", "4": "Multiple evidence types accepted. Witness statements supported. Some multimedia capability. Evidence strength indicators.", "3": "Document upload with basic categorisation. Witness statements as text only. No confidence scoring or multimedia support.", "2": "Document-only evidence. Requires scanned paper records. No support for oral testimony or alternative evidence.", "1": "Formal title deed or government record required. No accommodation for displaced persons who have lost documentation." } }, { "id": "SC-PROTECTION-SAFEGUARDS", "name": "Claimant Protection & Privacy", "description": "The system protects displaced claimants from retaliation, discrimination, or further dispossession. Property claims by IDPs and refugees can expose them to threats from occupants or hostile authorities.", "weight": 0.25, "ratingGuide": { "5": "Selective disclosure \u2014 claimant identity protected from opposing parties until adjudication. Encrypted personal data. No government access to individual records without consent. Audit log of all access. Designed for hostile-authority contexts.", "4": "Strong encryption and access controls. Claimant data compartmentalised. Identity protection during initial claim phases. Audit logging.", "3": "Standard data encryption. Role-based access control. Claimant identity visible to system administrators. Basic access logging.", "2": "Minimal privacy protection. Claimant data accessible to all system users. No selective disclosure capability.", "1": "No privacy features. All claims and claimant identities publicly visible. Unsuitable for conflict-affected populations." } }, { "id": "SC-RETURN-RESTITUTION", "name": "Return & Restitution Pathway Support", "description": "The system supports the full restitution process, from claim filing through verification, adjudication, and eventual return or compensation. Claims tracking without resolution pathways creates false hope.", "weight": 0.2, "ratingGuide": { "5": "End-to-end restitution workflow: claim \u2192 verification \u2192 adjudication \u2192 enforcement \u2192 return/compensation. Smart contract-based conditional transfers. Integration with compensation fund management. Tracks durable solution outcomes.", "4": "Claim-to-adjudication workflow complete. Compensation tracking included. Some enforcement mechanism. Outcome monitoring.", "3": "Claim filing and verification workflow. Adjudication tracking as manual status updates. No automated compensation or enforcement.", "2": "Claim registration only. Verification and adjudication handled entirely outside the system. Manual status tracking.", "1": "Static claim database. No workflow progression. No restitution pathway modelling." } }, { "id": "SC-CROSS-BORDER-CLAIMS", "name": "Cross-Border & Multi-Agency Interoperability", "description": "The system can operate across borders and share claim data between agencies (UNHCR, NRC, ICRC, government land authorities) without centralising sensitive data. Displaced populations cross borders, and their claims span jurisdictions.", "weight": 0.2, "ratingGuide": { "5": "Federated data sharing across agencies without centralised database. Cross-border claim matching. Standards-based interoperability (e.g. OCHA HXL). Proven multi-agency deployment. Handles different legal frameworks per jurisdiction.", "4": "Multi-agency data sharing with access controls. Cross-border capability demonstrated. API-based integration with major humanitarian platforms.", "3": "Data export/import between agencies. Single-jurisdiction focus but extensible. Manual data sharing processes documented.", "2": "Standalone system. Data sharing requires manual extraction. No multi-agency or cross-border features.", "1": "Siloed system with no interoperability. Proprietary data format. Cannot share data across agencies or borders." } }, { "id": "SC-GENDER-INCLUSION", "name": "Gender & Vulnerable Group Inclusion", "description": "The system actively supports property claims by women, orphans, and other groups who face systemic barriers to land rights. Displacement often strips away the informal protections these groups relied on.", "weight": 0.1, "ratingGuide": { "5": "Gender-disaggregated claim tracking. Joint titling and secondary rights support. Specific workflows for widow, orphan, and female-headed household claims. Accessibility features for non-literate claimants. Gender impact reporting.", "4": "Joint titling supported. Gender-disaggregated data. Some specific features for vulnerable group claims. Accessibility features present.", "3": "Joint titling possible but not default. Gender data captured. No specific vulnerable group workflows.", "2": "Individual titling only. No gender disaggregation. System assumes single (typically male) claimant.", "1": "No consideration for gender or vulnerable groups. System design may actively disadvantage women or secondary rights holders." } } ], "procurement": { "marketMaturity": "nascent", "primaryMode": "consortium", "alternativeModes": [ "integrator-led" ], "reasoning": "Property rights for displaced populations is research-stage; consortium typical.", "exampleProductCategories": [ "displaced-property-platform", "land-tenure-rails" ], "partnerChannels": [], "lastReviewed": "2026-05-01" } }, { "id": "UC-H-101", "name": "Housing, land, and property (HLP) claims tracking", "category": "H", "subcategory": "Claims Management", "description": "Follow each housing, land and property claim through checking and decision, so every organisation involved sees the same status and evidence.", "bCriteria": [ "B1", "B3", "B7" ], "requiredComponents": [ "claims-management", "dispute-resolution-layer", "audit-trail" ], "conditionalComponents": [ "smart-contracts", "community-validation" ], "crossCategoryDependencies": [ "UC-H-106", "UC-H-106" ], "p2TriggerConditions": { "description": "Activated when P2 shows complex property claims processes with multi-stakeholder involvement and dispute resolution needs", "rangeSignals": [ "claimsProcessManagement >=3", "multiStakeholder >=3", "disputeResolution >=2" ] }, "contextFieldsTemplate": [ "estimated_claims_volume", "claim_types_covered", "verification_entities", "resolution_timeline", "stakeholder_representation", "appeals_process_required", "fund_allocation_mechanism" ], "implementationComplexity": "medium", "examples": { "note": "OHCHR HLP framework implementation", "references": [ { "name": "OHCHR HLP Framework Implementation Study", "description": "Standardised HLP claims tracking and resolution process documentation", "year": 2019, "relevance": "high", "technologies": [ "Documentation Framework", "Process Design" ] }, { "name": "Lebanon Property Claims Commission Blockchain Pilot", "description": "Blockchain-based HLP claims tracking with government integration", "year": 2020, "relevance": "high", "technologies": [ "Hyperledger", "Government Systems" ] }, { "name": "Colombia Conflict Victim Claims Registry", "description": "Large-scale HLP claims management and verification system", "year": 2016, "relevance": "medium", "technologies": [ "Database Systems", "Government Integration" ] } ] }, "briefSection": "Mapping and geospatial", "solutionQuestions": [ { "id": "claim-volume-capacity", "type": "select", "options": [ { "label": "Small-scale deployment (< 10,000 claims) with rapid throughput", "value": "small-scale" }, { "label": "Medium-scale deployment (10,000-100,000 claims) with performance scaling", "value": "medium-scale" }, { "label": "Large-scale deployment (>100,000 claims) with enterprise digital ledger", "value": "large-scale" } ], "prefillFrom": null, "briefSection": "Registry platform", "propertyMapping": { "small-scale": { "technologies": [ "Public smart-contract network", "Standard Smart Contracts" ], "technologyProperties": { "maxCapacity": 10000, "throughput": "high", "scalability": "vertical" } }, "medium-scale": { "technologies": [ "Low-cost public smart-contract network", "Layer-2 scaling network" ], "technologyProperties": { "maxCapacity": 100000, "throughput": "very-high", "scalability": "horizontal" } }, "large-scale": { "technologies": [ "Permissioned shared ledger", "Private Networks" ], "technologyProperties": { "maxCapacity": 1000000, "throughput": "extreme", "scalability": "enterprise" } } }, "text": "What is the expected claim volume and system capacity design?", "ngoText": "What is the expected claim volume and system capacity design?" }, { "id": "resolution-mechanism-design", "type": "select", "options": [ { "label": "Fast-track resolution for straightforward cases with independent validation", "value": "fast-track-resolution-for-straightforwar" }, { "label": "Phased resolution with verification stages and checkpoint reviews", "value": "phased-resolution-with-verification-stag" }, { "label": "Government-moderated resolution with formal evidence documentation", "value": "government-moderated-resolution-with-for" } ], "prefillFrom": null, "briefSection": "Dispute resolution", "propertyMapping": { "fast-track-automated": { "technologies": [ "Smart Contracts", "Oracle Networks" ], "technologyProperties": { "automationLevel": "high", "resolutionTime": "30-days", "appealWindow": "7-days" } }, "phased-resolution": { "technologies": [ "Workflow Contracts", "Smart Contracts" ], "technologyProperties": { "phases": "three", "checkpoints": "multiple", "transparency": "high" } }, "government-moderated": { "technologies": [ "Blockchain Records", "Government Integration" ], "technologyProperties": { "moderatorRole": "government", "evidenceChain": "immutable", "appeals": "yes" } } }, "text": "For resolving disputed claims, do you use: individual adjudication, negotiated settlement, third-party arbitration, community consensus, or combination?", "ngoText": "For resolving disputed claims, do you use: individual adjudication, negotiated settlement, third-party arbitration, community consensus, or combination?", "question": "For resolving disputed claims, what approach fits your context: fast-track resolution, phased review with checkpoints, or government-moderated with formal evidence?" }, { "id": "stakeholder-representation-model", "type": "select", "options": [ { "label": "Representative committee with veto power and consensus requirement", "value": "committee-consensus" }, { "label": "Weighted voting system with stakeholder token allocation", "value": "weighted-voting" }, { "label": "Rotating stakeholder roles with periodic review and rotation", "value": "rotating-roles" } ], "prefillFrom": null, "briefSection": "Community validation", "propertyMapping": { "committee-consensus": { "technologies": [ "Multi-sig Wallets", "DAO Governance" ], "technologyProperties": { "structure": "committee-based", "consensus": "required", "veto": "enabled" } }, "weighted-voting": { "technologies": [ "Governance Tokens", "Smart Contracts" ], "technologyProperties": { "votingModel": "weighted", "transparency": "yes", "delegationSupport": "yes" } }, "rotating-roles": { "technologies": [ "Time-locked Smart Contracts", "Governance" ], "technologyProperties": { "rotationPeriod": "6-months", "roleAutomation": "yes", "equitability": "yes" } } }, "text": "Who should represent stakeholders in claim resolution: individual claimants, community leaders, formal legal representatives, international observers, or combination?", "ngoText": "Who should represent stakeholders in claim resolution: individual claimants, community leaders, formal legal representatives, international observers, or combination?" }, { "id": "appeals-escalation-process", "type": "select", "options": [ { "label": "Single appeals authority with independent review criteria", "value": "single-appeals-authority" }, { "label": "Three-tier appeals with escalation to arbitration", "value": "three-tier-appeals" }, { "label": "Digitally recorded appeals with transparent outcome documentation", "value": "blockchain-appeals" } ], "prefillFrom": null, "briefSection": "Dispute resolution", "propertyMapping": { "single-appeals-authority": { "technologies": [ "Smart Contracts", "Verifiable Credentials" ], "technologyProperties": { "appealLevels": "one", "reviewIndependence": "high", "timeLimit": "30-days" } }, "three-tier-appeals": { "technologies": [ "Smart Contracts", "Arbitration Oracles" ], "technologyProperties": { "appealLevels": "three", "escalation": "automated", "finalArbitration": "yes" } }, "blockchain-appeals": { "technologies": [ "Immutable Ledger", "Public Records" ], "technologyProperties": { "recordingLevel": "complete", "transparency": "public", "precedentTracking": "yes" } } }, "text": "What appeals and escalation process should be established?", "ngoText": "What appeals and escalation process should be established?", "hidden": true }, { "id": "hlp-participant-count", "type": "select", "options": [ { "label": "2\u20135 parties", "value": "small" }, { "label": "6\u201315 parties", "value": "medium" }, { "label": "16\u201350 parties", "value": "large" }, { "label": "Over 50 parties", "value": "enterprise" } ], "propertyMapping": { "small": { "technologies": [ "Simple shared ledger" ], "technologyProperties": { "consensusComplexity": "Low", "governanceModel": "Direct" } }, "medium": { "technologies": [ "Permissioned network", "Role-based access" ], "technologyProperties": { "consensusComplexity": "Medium", "governanceModel": "Committee-based" } }, "large": { "technologies": [ "Scalable permissioned network", "Delegated consensus" ], "technologyProperties": { "consensusComplexity": "High", "governanceModel": "Delegated" } }, "enterprise": { "technologies": [ "Enterprise consortium platform", "Federated consensus" ], "technologyProperties": { "consensusComplexity": "Very high", "governanceModel": "Federated" } } }, "prefillFrom": null, "briefSection": "Governance mechanism", "text": "How many organisations or stakeholders participate in HLP claims?", "ngoText": "How many organisations or stakeholders participate in HLP claims?" }, { "id": "sq-UC-H-106-001", "type": "single-select", "options": [ { "value": "documentary-title", "label": "Documentary title" }, { "value": "witness-testimony", "label": "Witness testimony" }, { "value": "satellite-imagery", "label": "Satellite imagery" }, { "value": "community-attestation", "label": "Community attestation" }, { "value": "cadastral-records", "label": "Cadastral records" }, { "value": "combination-scoring", "label": "Combination scoring" } ], "propertyMapping": { "documentary-title": { "technologies": [ "document-verification", "title-registry" ], "technologyProperties": {} }, "witness-testimony": { "technologies": [ "testimony-system", "witness-verification" ], "technologyProperties": {} }, "satellite-imagery": { "technologies": [ "satellite-data", "image-analysis" ], "technologyProperties": {} }, "community-attestation": { "technologies": [ "community-verification", "attestation-system" ], "technologyProperties": {} }, "cadastral-records": { "technologies": [ "cadastral-api", "government-records" ], "technologyProperties": {} }, "combination-scoring": { "technologies": [ "scoring-engine", "evidence-weighting" ], "technologyProperties": {} } }, "briefSection": "requirements", "text": "What evidence types should be accepted to support HLP claims?", "ngoText": "What evidence types should be accepted to support HLP claims?" }, { "id": "claims-management-approach", "type": "select", "options": [ { "label": "Formal claims process with adjudication workflow", "value": "formal-adjudication" }, { "label": "Community-based mediation with digital ledger record", "value": "community-mediation" }, { "label": "Self-service claims portal with document upload", "value": "self-service" }, { "label": "Hybrid: self-service intake with formal adjudication", "value": "hybrid" } ], "propertyMapping": { "formal-adjudication": { "technologies": [ "Formal claims management system", "Adjudication workflow engine", "Claims tracking ledger" ], "technologyProperties": { "processType": "Formal adjudication", "evidenceHandling": "Document upload with hash verification", "resolutionMethod": "Authority-adjudicated" } }, "community-mediation": { "technologies": [ "Community claims management platform", "Mediation workflow module", "Claims tracking ledger" ], "technologyProperties": { "processType": "Community mediation", "evidenceHandling": "Witness testimony + document upload", "resolutionMethod": "Community-mediated agreement" } }, "self-service": { "technologies": [ "Self-service claims portal", "Document upload and verification", "Claims tracking ledger" ], "technologyProperties": { "processType": "Self-service with review", "evidenceHandling": "Claimant-uploaded evidence", "resolutionMethod": "Administrative review" } }, "hybrid": { "technologies": [ "Hybrid claims management system", "Multi-stage claims workflow", "Claims tracking ledger" ], "technologyProperties": { "processType": "Self-service intake \u2192 formal adjudication", "evidenceHandling": "Progressive evidence collection", "resolutionMethod": "Escalation from self-service to formal" } } }, "prefillFrom": null, "briefSection": "Claims and disputes", "text": "How should claims and disputes be managed?", "ngoText": "How should claims and disputes be managed?" }, { "id": "dispute-resolution", "type": "select", "options": [ { "label": "Formal process with binding decisions and enforcement", "value": "formal-process-with-binding-decisions-an" }, { "label": "Mediation first, then escalation to formal adjudication if unresolved", "value": "mediation-first-then-escalation-to-forma" }, { "label": "Community-led resolution with outcomes recorded for accountability", "value": "community-led-resolution-with-outcomes-r" }, { "label": "Automated initial resolution (clear-cut cases) with human review for complex ones", "value": "automated-initial-resolution-clear-cut-c" }, { "label": "Not sure, need guidance", "value": "not-sure-need-guidance" } ], "propertyMapping": { "on-chain-arb": { "technologies": [ "On-chain dispute resolution system", "Arbitration smart contract", "Dispute evidence locker" ], "technologyProperties": { "resolutionMethod": "Smart contract arbitration", "enforcement": "Automatic via smart contract", "appealProcess": "On-chain appeal to higher arbiter" } }, "mediation": { "technologies": [ "Off-chain dispute resolution system", "Mediation workflow platform", "Dispute evidence locker" ], "technologyProperties": { "resolutionMethod": "Human mediator", "enforcement": "Agreement recorded on-chain", "appealProcess": "Escalation to formal adjudication" } }, "multi-tier": { "technologies": [ "Multi-tier dispute resolution system", "Automated resolution engine", "Human escalation service" ], "technologyProperties": { "resolutionMethod": "Auto-resolve simple, escalate complex", "enforcement": "Smart contract for auto, agreement for mediated", "appealProcess": "Multi-tier escalation" } }, "guidance-needed": { "technologies": [ "Dispute resolution framework" ], "technologyProperties": { "resolutionMethod": "To be determined", "enforcement": "To be determined", "appealProcess": "To be determined" } } }, "prefillFrom": null, "briefSection": "Dispute resolution", "text": "How should disputes be resolved within this system?", "ngoText": "How should disputes be resolved within this system?", "hidden": true, "question": "How should disputes be resolved?" }, { "id": "audit-trail-approach", "type": "select", "options": [ { "label": "Donors and external auditors need to independently verify any action at any time", "value": "donors-and-external-auditors-need-to-ind" }, { "label": "External auditors check periodically: summary reports and spot-checks are sufficient", "value": "external-auditors-check-periodically-sum" }, { "label": "Key milestones and approvals need independent verification; routine actions just need internal records", "value": "key-milestones-and-approvals-need-indepe" }, { "label": "Internal team records are sufficient: we mainly need our own staff to be able to look back", "value": "internal-team-records-are-sufficient-we-" }, { "label": "Not sure, need guidance on audit requirements", "value": "not-sure-need-guidance-on-audit-requirem" } ], "propertyMapping": { "full-immutable": { "technologies": [ "Immutable audit trail", "On-chain event logging", "Audit trail verification service" ], "technologyProperties": { "auditGranularity": "Every action", "storageApproach": "Full on-chain logging", "tamperEvidence": "Cryptographic hash chain" } }, "key-events": { "technologies": [ "Milestone-based audit trail", "Approval chain logger", "Audit trail verification service" ], "technologyProperties": { "auditGranularity": "Key milestones and approvals only", "storageApproach": "Selective on-chain logging", "tamperEvidence": "Merkle root anchoring" } }, "hybrid": { "technologies": [ "Hybrid audit trail system", "Off-chain storage with hash anchoring", "Audit trail verification service" ], "technologyProperties": { "auditGranularity": "Metadata on-chain, full records off-chain", "storageApproach": "Decentralised/off-chain storage with on-chain hash proofs", "tamperEvidence": "Hash anchoring to blockchain" } }, "guidance-needed": { "technologies": [ "Audit trail framework", "Audit trail verification service" ], "technologyProperties": { "auditGranularity": "To be determined during solution design", "storageApproach": "To be determined", "tamperEvidence": "To be determined" } } }, "prefillFrom": null, "briefSection": "Audit and evidence", "text": "What level of audit trail does this solution require?", "ngoText": "What level of audit trail does this solution require?", "hidden": true, "question": "Who needs to verify that actions in this system happened correctly, and how easily should they be able to check?" } ], "complexityFactors": { "relationships": 4, "operationalChange": 3, "dataCompliance": 4 }, "securityTier": "B", "suggestedCriteria": [ { "id": "SC-CLAIMS-VOLUME", "name": "Claims Volume & Processing Throughput", "description": "The system can handle the expected volume of HLP claims, which can reach tens of thousands in post-conflict settings, without becoming a bottleneck. Slow processing creates backlogs that undermine confidence in the entire process.", "weight": 0.25, "ratingGuide": { "5": "Tested at 50,000+ concurrent claims. Automated triage and categorisation. Batch processing for bulk claims. Sub-second search across full claims database. Horizontal scaling for surge capacity.", "4": "Handles 10,000-50,000 claims. Semi-automated triage. Reasonable search performance. Can scale with infrastructure investment.", "3": "Handles 1,000-10,000 claims. Manual triage with digital tracking. Search slows at higher volumes. Scaling requires significant rework.", "2": "Handles under 1,000 claims. Fully manual processing. No triage automation. Performance degrades with volume.", "1": "Spreadsheet-level capacity. Cannot handle systematic claims processing. No concurrent user support." } }, { "id": "SC-EVIDENCE-CHAIN", "name": "Immutable Evidence Chain & Audit Trail", "description": "The system maintains a tamper-proof record of all evidence, decisions, and status changes for each claim. HLP claims may be reopened years later. The evidence chain must be unimpeachable.", "weight": 0.25, "ratingGuide": { "5": "Every document, decision, and status change cryptographically timestamped and chained. Evidence cannot be altered or deleted. Full audit trail with actor attribution. Independently verifiable by any party. Anchored to public blockchain.", "4": "Tamper-evident logging for all claim events. Cryptographic timestamps. Audit trail with user attribution. Verification possible by authorised parties.", "3": "Database logging of claim events. Timestamps present but not cryptographically secured. Audit trail exists but could theoretically be altered by administrators.", "2": "Basic activity logging. No cryptographic integrity. Audit trail is incomplete \u2014 some events not captured.", "1": "No audit trail. Claim records can be modified without trace. Evidence integrity cannot be verified." } }, { "id": "SC-RESOLUTION-WORKFLOW", "name": "Multi-Track Resolution Workflow", "description": "Does the system support different resolution pathways for different claim types (mediation for simple disputes, formal adjudication for contested claims, administrative restitution for systematic displacement)?", "weight": 0.2, "ratingGuide": { "5": "Multiple resolution tracks configurable per claim type. Automated routing based on claim characteristics. Mediation, administrative, and judicial tracks with distinct workflows. Inter-track escalation and de-escalation. Outcome enforcement tracking.", "4": "Two or more resolution tracks. Semi-automated routing. Escalation between tracks supported. Outcome tracking included.", "3": "Single resolution track with manual branching. Claims can be escalated but no distinct workflow per track. Basic outcome recording.", "2": "Linear single-track workflow. All claims follow the same process regardless of complexity. No escalation mechanism.", "1": "No resolution workflow. System tracks claims but not resolution processes. Outcomes recorded manually outside the system." } }, { "id": "SC-STAKEHOLDER-ACCESS", "name": "Multi-Stakeholder Access & Transparency", "description": "Claimants, community leaders, government officials, and humanitarian agencies all can access appropriate views of claim status without compromising sensitive data. Trust in the HLP process depends on transparency.", "weight": 0.2, "ratingGuide": { "5": "Role-based dashboards for claimants, mediators, adjudicators, government, and oversight bodies. Real-time status visibility. Public aggregate statistics. Sensitive data protected by role. Mobile-accessible claimant portal.", "4": "Multiple role-based views. Claimant status checking supported. Government reporting available. Most data appropriately compartmentalised.", "3": "Administrator and claimant views. Basic status reporting. Government access via data exports. Limited role differentiation.", "2": "Single administrative view. Claimants cannot check their own status. Government access requires manual reports.", "1": "No external access. Single-user administrative interface. No transparency or claimant self-service." } }, { "id": "SC-LEGAL-FRAMEWORK", "name": "Legal Framework Adaptability", "description": "The system can adapt to different national HLP legal frameworks and transitional justice mechanisms. Every post-conflict context has unique legal conditions. A rigid system designed for one jurisdiction will fail in another.", "weight": 0.1, "ratingGuide": { "5": "Fully configurable claim types, evidence requirements, and resolution pathways per jurisdiction. Multi-legal-framework support within single deployment. Handles statutory, customary, and Islamic land law. Adapts to transitional justice commission rules.", "4": "Configurable claim types and basic workflow adaptation. Supports two or more legal frameworks. Can accommodate most transitional justice requirements.", "3": "Some configuration possible. Primary legal framework hard-coded with override options. Major jurisdiction changes require vendor support.", "2": "Minimal configuration. Built for one legal framework. Adapting to a different jurisdiction requires significant redevelopment.", "1": "Fixed legal framework assumptions. Cannot accommodate different national laws or transitional justice requirements." } } ], "procurement": { "marketMaturity": "nascent", "primaryMode": "consortium", "alternativeModes": [ "integrator-led" ], "reasoning": "HLP claims tracking is research-stage in most contexts.", "exampleProductCategories": [ "hlp-claims-platform", "land-tenure-rails" ], "partnerChannels": [], "lastReviewed": "2026-05-01" } }, { "id": "UC-H-102", "name": "Customary land rights documentation", "category": "H", "subcategory": "Land Rights", "description": "Record customary land rights in a way that respects traditional leaders and that the community, the government and outside bodies can all check.", "bCriteria": [ "B1", "B3", "B2" ], "requiredComponents": [ "registry-platform", "title-documentation", "community-validation", "audit-trail" ], "conditionalComponents": [ "government-interoperability", "dispute-resolution-layer" ], "crossCategoryDependencies": [ "UC-H-106", "UC-H-106" ], "p2TriggerConditions": { "description": "Activated when P2 shows customary land governance systems with community participation needs and overlapping claim systems", "rangeSignals": [ "customaryGovernance >=3", "communityParticipation >=3", "multipleClaimSystems >=2" ] }, "contextFieldsTemplate": [ "number_of_communities", "customary_governance_structure", "land_parcels_under_customary_tenure", "government_recognition_level", "documentation_traditional_method", "conflict_with_statutory_law", "community_validation_process" ], "implementationComplexity": "high", "examples": { "note": "Works with UNESCO and community-based organizations", "references": [ { "name": "Medici Land Governance East Africa Project", "description": "Blockchain documentation of customary land rights with elder council validation", "year": 2019, "relevance": "high", "technologies": [ "Hyperledger Fabric", "Community Governance" ] }, { "name": "UNESCO Intangible Cultural Heritage Documentation Platform", "description": "Digital preservation of traditional land tenure systems and oral histories", "year": 2018, "relevance": "medium", "technologies": [ "Digital Archive", "Metadata Standards" ] }, { "name": "Indigenous Land and Territory Mapping with GIS", "description": "Customary boundary mapping with ethnographic and genealogical documentation", "year": 2017, "relevance": "high", "technologies": [ "GIS", "Participatory Mapping" ] } ] }, "briefSection": "Community validation", "solutionQuestions": [ { "id": "customary-documentation-approach", "type": "select", "options": [ { "label": "Oral history digitization with recorded testimony and digital archive", "value": "oral-history-digital" }, { "label": "Customary tenure tokenisation platform with community-issued tokens", "value": "customary-tokens" }, { "label": "GPS boundary mapping with ethnographic and genealogical metadata", "value": "gps-ethnographic" }, { "label": "Photographic documentation with digital temporal proof", "value": "photo-blockchain" } ], "prefillFrom": null, "briefSection": "Community validation", "propertyMapping": { "oral-history-digital": { "technologies": [ "Video Recording", "Decentralised archive" ], "technologyProperties": { "mediaFormat": "audio-video", "languagePreservation": "yes", "permanentArchive": "yes" } }, "customary-tokens": { "technologies": [ "ERC-721", "Smart Contracts" ], "technologyProperties": { "tokenStandard": "ERC-721", "communityIssued": "yes", "transferability": "customizable" } }, "gps-ethnographic": { "technologies": [ "RTK-GPS", "Anthropological Database" ], "technologyProperties": { "accuracy": "2-5m", "metadata": "rich", "historicalContext": "yes" } }, "photo-blockchain": { "technologies": [ "Blockchain Timestamps", "Decentralised content-addressed storage" ], "technologyProperties": { "photoSeries": "temporal", "tampering": "detected", "locationProof": "yes" } } }, "text": "What documentation approach works best for customary land rights in your context?", "ngoText": "What documentation approach works best for customary land rights in your context?" }, { "id": "government-recognition-integration", "type": "select", "options": [ { "label": "Parallel digital ledger registry with government co-validation", "value": "parallel-registry-covalidation" }, { "label": "Government-issued certificates based on community attestations", "value": "gov-certificates-community" }, { "label": "Customary system preservation with digital ledger documentation only", "value": "customary-only" } ], "prefillFrom": null, "briefSection": "Government interoperability", "propertyMapping": { "parallel-registry-covalidation": { "technologies": [ "Blockchain", "Government Integration" ], "technologyProperties": { "parallelRegistry": "yes", "coValidation": "yes", "legalBinding": "conditional" } }, "gov-certificates-community": { "technologies": [ "Government Certification", "Blockchain Evidence" ], "technologyProperties": { "certificateFormat": "digital", "evidence": "blockchain-backed", "legally": "binding" } }, "customary-only": { "technologies": [ "Immutable Ledger", "Community Registry" ], "technologyProperties": { "governmentIntegration": "minimal", "autonomy": "high", "culturalPreservation": "yes" } } }, "text": "Is government integration required, desired, or not applicable for your approach?", "ngoText": "Is government integration required, desired, or not applicable for your approach?" }, { "id": "conflict-resolution-mechanisms", "type": "select", "options": [ { "label": "Customary law priority with government appeal pathway", "value": "customary-priority" }, { "label": "Dual-track system with customary and statutory parallel recognition", "value": "dual-track" }, { "label": "Harmonized framework through government legal reform and integration", "value": "harmonized-reform" } ], "prefillFrom": null, "briefSection": "Dispute resolution", "propertyMapping": { "customary-priority": { "technologies": [ "Smart Contracts", "Appeal System" ], "technologyProperties": { "jurisdiction": "customary-first", "appeal": "yes", "legalRecognition": "context-dependent" } }, "dual-track": { "technologies": [ "Blockchain Channels", "Interoperability" ], "technologyProperties": { "system": "parallel", "recognition": "dual", "resolution": "collaborative" } }, "harmonized-reform": { "technologies": [ "Smart Contracts", "Government Integration" ], "technologyProperties": { "legalFusion": "yes", "reformProcess": "ongoing", "recognition": "full" } } }, "text": "How are conflicts over land claims currently resolved in your communities?", "ngoText": "How are conflicts over land claims currently resolved in your communities?" }, { "id": "cultural-preservation-safeguards", "type": "select", "options": [ { "label": "Indigenous technology requirements with local administration authority", "value": "indigenous-tech-local" }, { "label": "Cultural protocol embedding in automated rules code", "value": "cultural-protocol-code" }, { "label": "Community-controlled access: elders or traditional authorities approve any changes", "value": "community-controlled" }, { "label": "Formal legal protections combined with digital documentation of customary rules", "value": "legal-plus-digital" }, { "label": "Not sure, need to consult community leaders first", "value": "unsure" } ], "prefillFrom": null, "briefSection": "Community validation", "propertyMapping": { "indigenous-tech-local": { "technologies": [ "Community-run Nodes", "Open Source" ], "technologyProperties": { "technologyControl": "local", "administration": "community", "dataSovereignty": "yes" } }, "cultural-protocol-code": { "technologies": [ "Smart Contracts", "Governance Logic" ], "technologyProperties": { "protocolEmbedding": "yes", "customRules": "enforced", "adaptation": "flexible" } }, "community-controlled": { "technologies": [ "Community access gateway", "Elder approval workflow" ], "technologyProperties": { "safeguardModel": "Community-controlled", "approvalAuthority": "Traditional authorities", "digitalRole": "Record-keeping only" } }, "legal-plus-digital": { "technologies": [ "Legal compliance layer", "Customary rule digitisation" ], "technologyProperties": { "safeguardModel": "Legal + digital documentation", "approvalAuthority": "Dual \u2014 legal and traditional", "digitalRole": "Documentation and enforcement" } }, "unsure": { "technologies": [ "Cultural safeguard assessment needed" ], "technologyProperties": { "safeguardModel": "TBD", "approvalAuthority": "TBD", "digitalRole": "TBD" } } }, "text": "What safeguards exist to protect cultural and governance practices?", "ngoText": "What safeguards exist to protect cultural and governance practices?" }, { "id": "title-documentation-approach", "type": "select", "options": [ { "label": "Formal title deeds with digital ledger registration", "value": "formal-deeds" }, { "label": "Occupancy certificates (intermediate documentation)", "value": "occupancy-certs" }, { "label": "Customary rights documentation with community attestation", "value": "customary-rights" }, { "label": "Progressive titling: start informal, formalise over time", "value": "progressive" } ], "propertyMapping": { "formal-deeds": { "technologies": [ "Formal title documentation system", "Title deed generation service", "Title verification portal" ], "technologyProperties": { "documentType": "Formal title deed", "legalRecognition": "Full legal title", "issuingAuthority": "Government land authority" } }, "occupancy-certs": { "technologies": [ "Occupancy certificate system", "Intermediate title documentation", "Title verification portal" ], "technologyProperties": { "documentType": "Occupancy/use certificate", "legalRecognition": "Intermediate \u2014 use rights", "issuingAuthority": "Local authority or NGO-facilitated" } }, "customary-rights": { "technologies": [ "Customary rights documentation system", "Community attestation module", "Title verification portal" ], "technologyProperties": { "documentType": "Customary rights record", "legalRecognition": "Community-endorsed (varies by jurisdiction)", "issuingAuthority": "Community elders/leaders + NGO witness" } }, "progressive": { "technologies": [ "Progressive titling platform", "Multi-stage title documentation", "Title verification portal" ], "technologyProperties": { "documentType": "Progressive \u2014 informal to formal", "legalRecognition": "Incremental formalisation", "issuingAuthority": "Community \u2192 local authority \u2192 government" } } }, "prefillFrom": null, "briefSection": "Title documentation", "text": "What type of title or rights documentation is appropriate?", "ngoText": "What type of title or rights documentation is appropriate?" }, { "id": "audit-trail-approach", "type": "select", "options": [ { "label": "Donors and external auditors need to independently verify any action at any time", "value": "donors-and-external-auditors-need-to-ind" }, { "label": "External auditors check periodically: summary reports and spot-checks are sufficient", "value": "external-auditors-check-periodically-sum" }, { "label": "Key milestones and approvals need independent verification; routine actions just need internal records", "value": "key-milestones-and-approvals-need-indepe" }, { "label": "Internal team records are sufficient: we mainly need our own staff to be able to look back", "value": "internal-team-records-are-sufficient-we-" }, { "label": "Not sure, need guidance on audit requirements", "value": "not-sure-need-guidance-on-audit-requirem" } ], "propertyMapping": { "full-immutable": { "technologies": [ "Immutable audit trail", "On-chain event logging", "Audit trail verification service" ], "technologyProperties": { "auditGranularity": "Every action", "storageApproach": "Full on-chain logging", "tamperEvidence": "Cryptographic hash chain" } }, "key-events": { "technologies": [ "Milestone-based audit trail", "Approval chain logger", "Audit trail verification service" ], "technologyProperties": { "auditGranularity": "Key milestones and approvals only", "storageApproach": "Selective on-chain logging", "tamperEvidence": "Merkle root anchoring" } }, "hybrid": { "technologies": [ "Hybrid audit trail system", "Off-chain storage with hash anchoring", "Audit trail verification service" ], "technologyProperties": { "auditGranularity": "Metadata on-chain, full records off-chain", "storageApproach": "Decentralised/off-chain storage with on-chain hash proofs", "tamperEvidence": "Hash anchoring to blockchain" } }, "guidance-needed": { "technologies": [ "Audit trail framework", "Audit trail verification service" ], "technologyProperties": { "auditGranularity": "To be determined during solution design", "storageApproach": "To be determined", "tamperEvidence": "To be determined" } } }, "prefillFrom": null, "briefSection": "Audit and evidence", "text": "What level of audit trail does this solution require?", "ngoText": "What level of audit trail does this solution require?", "hidden": true, "question": "Who needs to verify that actions in this system happened correctly, and how easily should they be able to check?" } ], "complexityFactors": { "relationships": 4, "operationalChange": 3, "dataCompliance": 3 }, "suggestedCriteria": [ { "id": "SC-CUSTOMARY-RESPECT", "name": "Respect for Customary Governance Structures", "description": "The system works within existing traditional authority structures rather than replacing them. Digitising customary land rights without involving traditional leaders undermines the very governance systems that maintain social order.", "weight": 0.3, "ratingGuide": { "5": "System designed around customary governance workflows. Elder/chief attestation built into registration. Community assembly validation supported. Oral testimony capture alongside written records. Proven deployment with indigenous communities.", "4": "Customary authority roles defined in system. Elder attestation included. Community validation workflows present. Some experience with traditional governance integration.", "3": "Community leader sign-off possible but not central to workflow. System primarily designed for statutory registration with customary adaptations added.", "2": "Individual-focused registration. Community leaders can be listed as contacts but have no governance role in the system. No customary workflow support.", "1": "Purely statutory registration model. No accommodation for customary governance. Would override or undermine traditional authority structures." } }, { "id": "SC-COMMUNAL-TENURE", "name": "Communal & Collective Tenure Support", "description": "The system can record communal land rights (shared grazing, seasonal access, overlapping use rights) not just individual parcels. Most customary land tenure involves collective rights that don't fit Western individual-title models.", "weight": 0.25, "ratingGuide": { "5": "Native support for communal, clan, family, and seasonal use rights. Overlapping rights on same land area. Hierarchical rights (community \u2192 clan \u2192 household). Seasonal and conditional access rules. Group identity management.", "4": "Communal and family tenure types supported. Basic overlapping rights. Group registration possible. Some seasonal use rights tracking.", "3": "Group registration possible but limited. Rights are per-parcel, not overlapping. No seasonal or conditional use rights.", "2": "Individual title only with workaround for group registration (e.g. single registered entity). No overlapping or seasonal rights.", "1": "Individual parcels only. No communal tenure concept. System fundamentally incompatible with collective land rights." } }, { "id": "SC-ORAL-DOCUMENTATION", "name": "Oral & Non-Written Evidence Capture", "description": "The system can capture and preserve oral histories, boundary walk testimony, and community consensus as legitimate evidence. In customary systems, oral tradition is the primary form of land documentation.", "weight": 0.2, "ratingGuide": { "5": "Audio/video testimony recording with transcription. Boundary walk recording with GPS trace. Community consensus capture with witness attestation. Multilingual support. Oral evidence given equal status to written records.", "4": "Audio recording supported. GPS boundary walks captured. Witness attestation included. Evidence categorisation distinguishes oral from written without hierarchy.", "3": "Text-based testimony transcription only. GPS coordinates captured. Written attestation required (no native audio/video).", "2": "Written documentation required. Oral testimony must be transcribed externally before entry. No multimedia evidence support.", "1": "Written title deeds or government records only. No accommodation for oral traditions or non-written evidence." } }, { "id": "SC-STATUTORY-BRIDGE", "name": "Customary-to-Statutory Bridge", "description": "Documented customary rights can be progressively formalised into statutory recognition where communities desire this. The system should enable, not force, a pathway from customary to formal legal recognition.", "weight": 0.15, "ratingGuide": { "5": "Progressive formalisation pathway built in: customary documentation \u2192 intermediate certification \u2192 formal title. Communities choose their own pace. Government API integration for formal registration when ready. Dual validity (customary + statutory) supported.", "4": "Clear upgrade path from customary to statutory. Government system integration available. Communities can remain at customary level if preferred.", "3": "Data export compatible with government systems. Manual process to convert customary records to statutory applications. No in-system progression.", "2": "Customary records stored separately from statutory. No conversion pathway. Two parallel systems.", "1": "Customary records cannot interface with statutory systems. No bridge between traditional documentation and formal legal recognition." } }, { "id": "SC-FIELD-USABILITY", "name": "Field Usability in Remote Communities", "description": "The system can be used in rural and remote settings with limited infrastructure. Customary land documentation happens in villages, not offices. The technology must work where the communities are.", "weight": 0.1, "ratingGuide": { "5": "Full offline operation with sync-when-connected. Works on basic smartphones. Multi-language interface including local languages. Pictographic navigation for non-literate users. Solar-powered operation tested. Community facilitator training programme included.", "4": "Offline data capture with periodic sync. Works on mid-range smartphones. Multiple language support. Basic accessibility features for non-literate users.", "3": "Limited offline capability (view but not create). Requires reliable smartphone. Major languages only. Assumes literate users.", "2": "Requires internet connection. Desktop or tablet focused. Single language. Designed for office use.", "1": "Always-online requirement. Desktop-only. English-only. Cannot operate in field settings." } } ], "procurement": { "marketMaturity": "nascent", "primaryMode": "consortium", "alternativeModes": [ "integrator-led" ], "reasoning": "Customary land rights documentation is bespoke and consortium-led.", "exampleProductCategories": [ "customary-land-platform", "indigenous-rights-rails" ], "partnerChannels": [], "lastReviewed": "2026-05-01" } }, { "id": "UC-H-103", "name": "Natural resource extraction tracking", "category": "H", "subcategory": "Natural Resources", "description": "Track how much is extracted from natural resources, and where, so communities and regulators can compare it with company reports.", "bCriteria": [ "B1", "B3", "B4" ], "requiredComponents": [ "registry-platform", "audit-trail", "iot-sensors", "verification-layer" ], "conditionalComponents": [ "monitoring-platform", "smart-contracts" ], "crossCategoryDependencies": [ "UC-I-114", "UC-I-114" ], "p2TriggerConditions": { "description": "Activated when P2 shows natural resource extraction with environmental monitoring needs and supply chain tracking requirements", "rangeSignals": [ "resourceExtraction >=3", "environmentalMonitoring >=2", "supplyChainTracking >=2" ] }, "contextFieldsTemplate": [ "resource_types_extracted", "extraction_volume_baseline", "environmental_impact_assessment_frequency", "monitoring_technology_available", "local_community_involvement", "regulatory_compliance_requirements", "benefit_sharing_mechanism" ], "implementationComplexity": "high", "examples": { "note": "Mining and logging certification chains", "references": [ { "name": "Everledger Diamond Provenance Blockchain", "description": "Supply chain transparency for conflict-free mineral extraction and trading", "year": 2015, "relevance": "high", "technologies": [ "Hyperledger", "Diamond Tracking" ] }, { "name": "FAO Resource Extraction Monitoring Framework", "description": "Government and community monitoring of natural resource extraction with impact assessment", "year": 2018, "relevance": "high", "technologies": [ "Satellite Monitoring", "Environmental Assessment" ] }, { "name": "Forestry Stewardship Council FSC Blockchain Integration", "description": "Timber extraction tracking with sustainability certification on blockchain", "year": 2019, "relevance": "high", "technologies": [ "Smart Contracts", "Certification Integration" ] } ] }, "briefSection": "Government interoperability", "solutionQuestions": [ { "id": "resource-type-tracking", "type": "select", "options": [ { "label": "Mineral extraction ledger with commodity type and volume tracking", "value": "mineral-ledger" }, { "label": "Timber and forestry tracking with species and sustainability metrics", "value": "timber-sustainability" }, { "label": "Oil and gas resource ledger with environmental impact scoring", "value": "oil-gas-impact" }, { "label": "Multi-resource agile taxonomy with flexible commodity classification", "value": "multi-resource-agile" } ], "prefillFrom": null, "briefSection": "Mapping and geospatial", "propertyMapping": { "mineral-ledger": { "technologies": [ "Smart Contracts", "Supply Chain Oracles" ], "technologyProperties": { "resourceCategory": "minerals", "volumeAccuracy": "high", "commodityStandards": "ICMM" } }, "timber-sustainability": { "technologies": [ "IoT Sensors", "Geolocation" ], "technologyProperties": { "resourceCategory": "forestry", "sustainability": "yes", "traceability": "supply-chain" } }, "oil-gas-impact": { "technologies": [ "Smart Contracts", "Environmental Oracles" ], "technologyProperties": { "resourceCategory": "hydrocarbons", "impactTracking": "yes", "carbonFootprint": "measured" } }, "multi-resource-agile": { "technologies": [ "Ontology Smart Contracts", "RDF Data" ], "technologyProperties": { "resourceFlexibility": "high", "taxonomy": "extensible", "interoperability": "yes" } } }, "text": "What resource type tracking and categorization should be used?", "ngoText": "What resource type tracking and categorization should be used?" }, { "id": "monitoring-methodology", "type": "select", "options": [ { "label": "sensor device networks with real-time extraction volume data", "value": "iot-realtime" }, { "label": "Satellite remote sensing with automated change detection", "value": "satellite-detection" }, { "label": "Manual audits with digital ledger-recorded inspection outcomes", "value": "manual-audits-blockchain" }, { "label": "Hybrid IoT-satellite monitoring with cross-validation", "value": "hybrid-monitoring" } ], "prefillFrom": null, "briefSection": "Mapping and geospatial", "propertyMapping": { "iot-realtime": { "technologies": [ "IoT Sensors", "LoRaWAN" ], "technologyProperties": { "realTime": "yes", "sensorDensity": "high", "dataFrequency": "1-minute" } }, "satellite-detection": { "technologies": [ "Open satellite imagery", "Machine Learning" ], "technologyProperties": { "resolution": "10-30m", "changeDetection": "automated", "updateFrequency": "daily" } }, "manual-audits-blockchain": { "technologies": [ "Audit Trail", "Blockchain Records" ], "technologyProperties": { "auditFrequency": "quarterly", "transparency": "high", "immutability": "yes" } }, "hybrid-monitoring": { "technologies": [ "IoT Sensors", "Open satellite imagery", "Smart Contracts" ], "technologyProperties": { "integration": "cross-validation", "accuracy": "highest", "redundancy": "yes" } } }, "text": "For monitoring extraction, what methods are feasible: satellite/remote sensing, ground-based observer patrols, extraction site meters, or community self-reporting?", "ngoText": "For monitoring extraction, what methods are feasible: satellite/remote sensing, ground-based observer patrols, extraction site meters, or community self-reporting?" }, { "id": "community-involvement-model", "type": "select", "options": [ { "label": "Community monitors with mobile app reporting and incentives", "value": "community-monitors" }, { "label": "Participatory verification with digitally-mediated community voting", "value": "participatory-verification" }, { "label": "Community-controlled monitoring dashboard with real-time data access", "value": "community-dashboard" } ], "prefillFrom": null, "briefSection": "Community validation", "propertyMapping": { "community-monitors": { "technologies": [ "Mobile App", "Blockchain Incentives" ], "technologyProperties": { "communityRole": "monitors", "reporting": "mobile-enabled", "incentiveToken": "yes" } }, "participatory-verification": { "technologies": [ "Smart Contracts", "DAO Governance" ], "technologyProperties": { "participation": "active", "verification": "community-based", "decisionAutomation": "yes" } }, "community-dashboard": { "technologies": [ "Data Visualization", "Blockchain Data" ], "technologyProperties": { "transparency": "high", "realTimeAccess": "yes", "controlLevel": "full" } } }, "text": "How is your community currently involved in land and resource governance?", "ngoText": "How is your community currently involved in land and resource governance?" }, { "id": "environmental-impact-assessment", "type": "select", "options": [ { "label": "Automated environmental compliance scoring with oracle data feeds", "value": "auto-compliance-scoring" }, { "label": "Satellite-verified environmental impact with AI analysis", "value": "satellite-ai-impact" }, { "label": "Biodiversity monitoring with digital ledger-recorded audit trail", "value": "biodiversity-audit" } ], "prefillFrom": null, "briefSection": "Reporting and audit", "propertyMapping": { "auto-compliance-scoring": { "technologies": [ "Oracle Networks", "Environmental Sensors" ], "technologyProperties": { "automationLevel": "high", "complianceMetrics": "standardized", "penalties": "automated" } }, "satellite-ai-impact": { "technologies": [ "Open satellite imagery", "Machine Learning" ], "technologyProperties": { "impactMetrics": "satellite-derived", "AI": "yes", "visualization": "yes" } }, "biodiversity-audit": { "technologies": [ "Environmental Monitoring", "Blockchain" ], "technologyProperties": { "biodiversityTracking": "yes", "auditTrail": "immutable", "compensationTracking": "yes" } } }, "text": "For environmental monitoring, what should be tracked: extraction volume only, environmental indicators (water quality, vegetation), biodiversity surveys, or combination?", "ngoText": "For environmental monitoring, what should be tracked: extraction volume only, environmental indicators (water quality, vegetation), biodiversity surveys, or combination?" }, { "id": "supply-chain-provenance", "type": "select", "options": [ { "label": "Full supply chain transparency ledger from extraction to market", "value": "full-transparency-ledger" }, { "label": "Conflict minerals certification with digital ledger attestation", "value": "conflict-minerals-cert" }, { "label": "Targeted traceability at key handover points (mine, processor, exporter)", "value": "key-handover" }, { "label": "Community-verified origin documentation with local authority sign-off", "value": "community-verified" }, { "label": "Not sure, need to assess what is feasible in our extraction context", "value": "unsure" } ], "prefillFrom": null, "briefSection": "Reporting and audit", "propertyMapping": { "full-transparency-ledger": { "technologies": [ "Permissioned shared ledger", "Supply Chain Tracking" ], "technologyProperties": { "transparency": "complete", "participants": "all", "immutability": "yes" } }, "conflict-minerals-cert": { "technologies": [ "Verifiable Credentials", "Blockchain" ], "technologyProperties": { "certification": "yes", "conflictFree": "verified", "compliance": "ICGLR" } }, "key-handover": { "technologies": [ "Checkpoint-based tracking", "Handover verification" ], "technologyProperties": { "provenanceDepth": "Key handover points", "verificationModel": "Checkpoint stamps", "conflictScreening": "At export stage" } }, "community-verified": { "technologies": [ "Community origin verification", "Local authority attestation" ], "technologyProperties": { "provenanceDepth": "Origin to first sale", "verificationModel": "Community + authority sign-off", "conflictScreening": "At source" } }, "unsure": { "technologies": [ "Provenance feasibility assessment needed" ], "technologyProperties": { "provenanceDepth": "TBD", "verificationModel": "TBD", "conflictScreening": "TBD" } } }, "text": "What supply chain provenance and anti-conflict mechanisms should be used?", "ngoText": "What supply chain provenance and anti-conflict mechanisms should be used?" }, { "id": "registry-platform-approach", "type": "select", "options": [ { "label": "Government-integrated registry (supplement existing land authority)", "value": "gov-integrated" }, { "label": "Standalone digital ledger registry (parallel to government system)", "value": "standalone-chain" }, { "label": "Community-managed registry with local authority endorsement", "value": "community-managed" }, { "label": "Not sure, need guidance on registry approach", "value": "guidance-needed" } ], "propertyMapping": { "gov-integrated": { "technologies": [ "Government-integrated registry platform", "Authority system connection", "Registry verification service" ], "technologyProperties": { "legalStatus": "Government-recognised", "managedBy": "Government authority with blockchain backend", "disputeResolution": "Through existing legal channels" } }, "standalone-chain": { "technologies": [ "Standalone blockchain registry platform", "Decentralised registry service", "Registry verification service" ], "technologyProperties": { "legalStatus": "Evidence-grade (may require legal framework)", "managedBy": "NGO/consortium-operated", "disputeResolution": "Automatedarbitration + legal" } }, "community-managed": { "technologies": [ "Community registry platform", "Local authority endorsement module", "Registry verification service" ], "technologyProperties": { "legalStatus": "Community-endorsed with local authority backing", "managedBy": "Community with NGO facilitation", "disputeResolution": "Community governance + mediation" } }, "guidance-needed": { "technologies": [ "Registry platform framework", "Registry verification service" ], "technologyProperties": { "legalStatus": "To be determined", "managedBy": "To be determined", "disputeResolution": "To be determined" } } }, "prefillFrom": null, "briefSection": "Registry design", "text": "What type of registry platform is appropriate for this context?", "ngoText": "What type of registry platform is appropriate for this context?" }, { "id": "verification-layer", "type": "select", "options": [ { "label": "Automated verification against digital records", "value": "automated" }, { "label": "Third-party verification with digital proof", "value": "third-party" }, { "label": "Community-based verification with attestation", "value": "community" }, { "label": "Not sure, need guidance", "value": "guidance-needed" } ], "propertyMapping": { "automated": { "technologies": [ "Automated verification layer", "On-chain record checker", "Verification result cache" ], "technologyProperties": { "verificationSpeed": "Instant", "trustModel": "Digital data verification", "humanInvolvement": "None" } }, "third-party": { "technologies": [ "Third-party verification layer", "Auditor access API", "Verification certificate service" ], "technologyProperties": { "verificationSpeed": "Hours to days", "trustModel": "Trusted third-party auditor", "humanInvolvement": "Third-party auditor" } }, "community": { "technologies": [ "Community verification layer", "Attestation collection service", "Verification quorum engine" ], "technologyProperties": { "verificationSpeed": "Days (community process)", "trustModel": "Community consensus", "humanInvolvement": "Community members" } }, "guidance-needed": { "technologies": [ "Verification layer framework" ], "technologyProperties": { "verificationSpeed": "To be determined", "trustModel": "To be determined", "humanInvolvement": "To be determined" } } }, "prefillFrom": null, "briefSection": "Verification", "text": "How is records or claims currently independently verified?", "ngoText": "How is records or claims currently independently verified?" } ], "complexityFactors": { "relationships": 4, "operationalChange": 3, "dataCompliance": 3 }, "suggestedCriteria": [ { "id": "SC-EXTRACTION-MONITORING", "name": "Real-Time Extraction Monitoring", "description": "The system can track extraction volumes and activities in real time through sensor integration, satellite monitoring, or verified field reporting. Without independent monitoring, extraction data is only as trustworthy as the extracting company.", "weight": 0.3, "ratingGuide": { "5": "IoT sensor integration (weight stations, flow meters). Satellite change detection for surface mining/deforestation. Automated anomaly alerts. Multi-source data triangulation. Real-time dashboard for all stakeholders.", "4": "IoT integration for key measurement points. Periodic satellite monitoring. Automated alerts for threshold breaches. Stakeholder reporting dashboards.", "3": "Manual field reporting with digital forms. Periodic satellite imagery review. Basic volume tracking. Reports generated on schedule.", "2": "Self-reported extraction data from operators. No independent verification. Periodic manual audits only.", "1": "No monitoring capability. System records reported data without any verification mechanism." } }, { "id": "SC-ENVIRONMENTAL-IMPACT", "name": "Environmental Impact Documentation", "description": "The system captures and tracks environmental impact data (deforestation, water contamination, habitat disruption) alongside extraction volumes. Environmental accountability requires linking extraction activities to their consequences.", "weight": 0.25, "ratingGuide": { "5": "Integrated environmental monitoring: water quality, air quality, biodiversity indicators, land cover change. Baseline comparison capability. Environmental impact linked to specific extraction activities. Automated compliance threshold alerts. Public environmental dashboard.", "4": "Key environmental indicators tracked. Baseline comparison available. Extraction-to-impact linkage for major indicators. Compliance monitoring.", "3": "Basic environmental data capture (manual entry). Some baseline tracking. Environmental reports generated separately from extraction data.", "2": "Environmental data stored as attachments. No structured tracking. No baseline comparison or trend analysis.", "1": "No environmental data capability. System tracks extraction volumes only with no environmental context." } }, { "id": "SC-CHAIN-OF-CUSTODY", "name": "Chain of Custody & Provenance", "description": "The system can track resources from extraction point through processing to final destination. For conflict minerals and high-value resources, provenance tracking prevents laundering of illegally extracted materials.", "weight": 0.2, "ratingGuide": { "5": "End-to-end chain of custody from extraction to final sale. Cryptographic provenance tagging. Batch splitting/merging with full traceability. Integration with international certification schemes (EITI, Kimberley Process). Anti-laundering detection algorithms.", "4": "Multi-stage chain of custody. Batch tracking with provenance records. Integration with at least one certification scheme. Basic anomaly detection.", "3": "Two-stage tracking (extraction + first sale). Batch records maintained. Manual integration with certification bodies.", "2": "Extraction-point documentation only. No downstream tracking. No certification integration.", "1": "No chain of custody. System records extraction events only with no provenance tracking." } }, { "id": "SC-COMMUNITY-OVERSIGHT", "name": "Community Access & Oversight", "description": "Affected communities can independently monitor extraction activities and access relevant data. Community oversight is essential for accountability but often blocked by information asymmetry.", "weight": 0.15, "ratingGuide": { "5": "Community-facing dashboard with extraction volumes, environmental data, and benefit sharing status. Mobile-accessible in local languages. Community reporting (grievance) mechanism. Independent verification access. Real-time alerts for community-defined thresholds.", "4": "Community portal with key extraction and environmental data. Mobile accessible. Grievance submission supported. Some local language support.", "3": "Periodic community reports generated. Data available on request. Basic grievance mechanism. Single language.", "2": "Community access limited to annual reports. No real-time data. No grievance mechanism.", "1": "No community access. All data held by operators and regulators only." } }, { "id": "SC-REGULATORY-COMPLIANCE", "name": "Regulatory & Licensing Integration", "description": "Does the system integrate with national mining/forestry licensing systems and meet international transparency standards (EITI, Kimberley Process)?", "weight": 0.1, "ratingGuide": { "5": "Direct integration with national licensing authorities. EITI reporting templates built in. Automated compliance checking against license conditions. Multi-jurisdiction support. Real-time regulatory reporting.", "4": "API integration with major licensing systems. EITI-compatible reporting. Automated licence condition monitoring. Works in multiple jurisdictions.", "3": "Data export compatible with regulatory reporting. Manual EITI report preparation. Licence tracking within system. Single jurisdiction focus.", "2": "Standalone system. Regulatory reports prepared manually from exported data. No licence integration.", "1": "No regulatory awareness. System does not track licensing or compliance requirements." } } ], "procurement": { "marketMaturity": "emerging", "primaryMode": "tender", "alternativeModes": [ "integrator-led" ], "reasoning": "Natural resource extraction tracking has commercial product space.", "exampleProductCategories": [ "extractives-tracking-platform", "resource-provenance-rails" ], "partnerChannels": [], "lastReviewed": "2026-05-01" } }, { "id": "UC-H-104", "name": "Community benefit sharing from resources", "category": "H", "subcategory": "Benefit Sharing", "description": "Calculate and record the share of resource income owed to affected communities, so members can check that each payment was correct.", "bCriteria": [ "B1", "B3", "B7" ], "requiredComponents": [ "smart-contracts", "audit-trail", "registry-platform" ], "conditionalComponents": [ "reporting-automation" ], "crossCategoryDependencies": [ "UC-H-106", "UC-F-089" ], "p2TriggerConditions": { "description": "Activated when P2 shows resource extraction with community benefit-sharing requirements and need for automated distribution", "rangeSignals": [ "resourceExtraction >=3", "communityBenefit >=3", "automationLevel >=2" ] }, "contextFieldsTemplate": [ "benefit_sharing_mechanism", "percentage_allocation_rule", "number_of_beneficiary_communities", "payment_frequency", "dispute_mechanism", "transparency_reporting_level" ], "implementationComplexity": "medium", "examples": { "note": "EITI and revenue transparency initiatives", "references": [ { "name": "World Bank Extractive Industries Transparency Initiative EITI", "description": "Government and company benefit-sharing reporting standards with community stakeholder engagement", "year": 2018, "relevance": "high", "technologies": [ "Reporting Standards", "Multi-stakeholder Governance" ] }, { "name": "FAO Community-Based Benefit Sharing Framework", "description": "Natural resource benefit distribution mechanisms with local community participation", "year": 2017, "relevance": "high", "technologies": [ "Framework Design", "Community Systems" ] }, { "name": "Blockchain-Based Royalty Distribution System for Mining", "description": "Automated smart contract payments to local communities from resource extraction", "year": 2020, "relevance": "medium", "technologies": [ "Smart Contracts", "Payment Automation" ] } ] }, "briefSection": "Infrastructure requirements", "solutionQuestions": [ { "id": "sharing-mechanism-design", "type": "select", "options": [ { "label": "Per-transaction royalty with percentage-based distribution", "value": "transaction-royalty" }, { "label": "Annual profit-sharing with community stakeholder voting", "value": "annual-profit-sharing" }, { "label": "Trust-based fund management with elected community trustees", "value": "trust-fund-model" } ], "prefillFrom": null, "briefSection": "Registry platform", "propertyMapping": { "transaction-royalty": { "technologies": [ "Smart Contracts", "Automated Oracles" ], "technologyProperties": { "distribution": "percentage-based", "frequency": "real-time", "automation": "full" } }, "annual-profit-sharing": { "technologies": [ "DAO Governance", "Smart Contracts" ], "technologyProperties": { "distributionFrequency": "annual", "voting": "yes", "transparency": "high" } }, "trust-fund-model": { "technologies": [ "Multi-sig Wallets", "Governance Smart Contracts" ], "technologyProperties": { "trusteeRole": "elected", "fundManagement": "delegated", "oversight": "community" } } }, "text": "For benefit-sharing, should distributions be: based on population share, land contribution, active participation in decision-making, or other criteria?", "ngoText": "For benefit-sharing, should distributions be: based on population share, land contribution, active participation in decision-making, or other criteria?" }, { "id": "payment-model-options", "type": "select", "options": [ { "label": "Direct fiat currency transfers with bank integration", "value": "fiat-transfers" }, { "label": "Stablecoin payments with community wallet infrastructure", "value": "stablecoin-payments" }, { "label": "Community benefit tokens with secondary market trading", "value": "benefit-tokens" } ], "prefillFrom": null, "briefSection": "Infrastructure requirements", "propertyMapping": { "fiat-transfers": { "technologies": [ "Bank APIs", "Blockchain Bridge" ], "technologyProperties": { "currency": "fiat", "integration": "banking", "volatility": "none" } }, "stablecoin-payments": { "technologies": [ "Regulated dollar stablecoin", "Community Wallets" ], "technologyProperties": { "currency": "stablecoin", "volatility": "low", "accessibility": "high" } }, "benefit-tokens": { "technologies": [ "ERC-20 Tokens", "DEX Integration" ], "technologyProperties": { "tokenization": "yes", "trading": "allowed", "value": "market-determined" } } }, "text": "What payment and currency model should be adopted?", "ngoText": "What payment and currency model should be adopted?" }, { "id": "transparency-mechanism", "type": "select", "options": [ { "label": "Public digital ledger ledger with real-time transaction visibility", "value": "public-ledger" }, { "label": "Private register with privacy-preserving verification", "value": "private-zkproof" }, { "label": "Quarterly auditable reports with digital ledger-anchored timestamps", "value": "quarterly-audits" } ], "prefillFrom": null, "briefSection": "Reporting and audit", "propertyMapping": { "public-ledger": { "technologies": [ "Public Blockchain", "Blockchain Explorer" ], "technologyProperties": { "transparency": "complete", "realTime": "yes", "auditability": "full" } }, "private-zkproof": { "technologies": [ "Zero-Knowledge Proofs", "Private Ledger" ], "technologyProperties": { "privacy": "high", "verifiability": "yes", "transparency": "selective" } }, "quarterly-audits": { "technologies": [ "Audit Reports", "Blockchain Anchoring" ], "technologyProperties": { "auditFrequency": "quarterly", "immutability": "yes", "verification": "independent" } } }, "text": "What transparency mechanisms do you currently use for land and resource data?", "ngoText": "What transparency mechanisms do you currently use for land and resource data?" }, { "id": "benefit-share-participant-count", "type": "select", "options": [ { "label": "2\u20135 parties", "value": "small" }, { "label": "6\u201315 parties", "value": "medium" }, { "label": "16\u201350 parties", "value": "large" }, { "label": "Over 50 parties", "value": "enterprise" } ], "propertyMapping": { "small": { "technologies": [ "Simple shared ledger" ], "technologyProperties": { "consensusComplexity": "Low", "governanceModel": "Direct" } }, "medium": { "technologies": [ "Permissioned network", "Role-based access" ], "technologyProperties": { "consensusComplexity": "Medium", "governanceModel": "Committee-based" } }, "large": { "technologies": [ "Scalable permissioned network", "Delegated consensus" ], "technologyProperties": { "consensusComplexity": "High", "governanceModel": "Delegated" } }, "enterprise": { "technologies": [ "Enterprise consortium platform", "Federated consensus" ], "technologyProperties": { "consensusComplexity": "Very high", "governanceModel": "Federated" } } }, "prefillFrom": null, "briefSection": "Governance mechanism", "text": "How many organisations or stakeholders participate in benefit sharing?", "ngoText": "How many organisations or stakeholders participate in benefit sharing?", "hidden": true }, { "id": "benefit-share-compliance", "type": "multiselect", "options": [ { "label": "Tax deductibility receipting", "value": "tax" }, { "label": "Anti-money laundering (AML) / Know Your Donor", "value": "aml" }, { "label": "Cross-border fund transfer regulations", "value": "cross-border" }, { "label": "Cryptocurrency-specific regulations", "value": "crypto-reg" }, { "label": "No specific compliance requirements", "value": "none" } ], "propertyMapping": { "tax": { "technologies": [ "Automated receipt generation" ], "technologyProperties": { "complianceModule": "Tax receipting", "regulatoryRisk": "Low" } }, "aml": { "technologies": [ "KYC/AML screening module" ], "technologyProperties": { "complianceModule": "AML screening", "regulatoryRisk": "Medium" } }, "cross-border": { "technologies": [ "Cross-border compliance module" ], "technologyProperties": { "complianceModule": "Transfer regulations", "regulatoryRisk": "High" } }, "crypto-reg": { "technologies": [ "Crypto compliance framework" ], "technologyProperties": { "complianceModule": "Crypto regulations", "regulatoryRisk": "High" } }, "none": { "technologies": [], "technologyProperties": { "complianceModule": "None required", "regulatoryRisk": "Low" } } }, "prefillFrom": null, "briefSection": "Compliance and audit", "text": "What financial compliance requirements apply to community benefit sharing?", "ngoText": "What financial compliance requirements apply to community benefit sharing?" } ], "complexityFactors": { "relationships": 3, "operationalChange": 3, "dataCompliance": 2 }, "suggestedCriteria": [ { "id": "SC-DISTRIBUTION-TRANSPARENCY", "name": "Benefit Distribution Transparency", "description": "All stakeholders (communities, companies, and government) can independently verify that benefit sharing payments match agreed-upon formulas. Opaque distribution breeds distrust and conflict.", "weight": 0.3, "ratingGuide": { "5": "Real-time benefit calculation visible to all parties. Formula-to-payment audit trail. Community-accessible dashboard showing extraction revenue, formula application, and payment status. Independent verification possible without relying on any single party.", "4": "Benefit calculations transparent to authorised stakeholders. Payment tracking with formula reference. Community reporting available with some delay.", "3": "Payment tracking with periodic reporting. Formula documented but not automatically linked to calculations. Stakeholder access via reports.", "2": "Payment records maintained centrally. Beneficiaries notified of amounts but cannot verify calculations. Annual reporting only.", "1": "No transparency. Payments recorded internally by distributing entity only. Beneficiaries have no visibility into calculations." } }, { "id": "SC-FORMULA-ENFORCEMENT", "name": "Automated Formula Compliance", "description": "The system can automatically calculate and enforce benefit sharing formulas, whether percentage-of-revenue, per-tonne royalties, or development fund allocations. Manual calculation introduces errors and creates opportunities for manipulation.", "weight": 0.25, "ratingGuide": { "5": "Smart contract-based automatic calculation and distribution. Multiple formula types supported (percentage, per-unit, tiered, conditional). Automatic trigger when extraction data is confirmed. Handles multi-beneficiary splits. Formula changes require multi-party approval.", "4": "Automated calculation with manual disbursement approval. Multiple formula types. Trigger-based calculation. Multi-beneficiary support.", "3": "Semi-automated calculation with manual verification. Standard formula types. Manual trigger. Basic multi-beneficiary splits.", "2": "Manual calculation with system recording. Single formula type. Calculations done externally and entered into system.", "1": "No calculation capability. System records payments only, not formulas or entitlements." } }, { "id": "SC-COMMUNITY-PARTICIPATION", "name": "Community Decision-Making Integration", "description": "The system supports community governance of how benefits are allocated and spent. Benefit sharing without community voice in spending decisions reduces communities to passive recipients.", "weight": 0.2, "ratingGuide": { "5": "Community budgeting and prioritisation tools. Voting/consensus mechanisms for spending decisions. Development fund tracking against community-chosen priorities. Participatory monitoring of funded projects. Feedback mechanism for community satisfaction.", "4": "Community input mechanism for spending priorities. Fund tracking by priority area. Basic participatory monitoring. Feedback collection.", "3": "Community consultation recorded. Fund allocation by pre-set categories. Limited participatory monitoring.", "2": "Spending decisions made by external parties. Community informed of allocations but not consulted. No participatory monitoring.", "1": "No community participation. Benefits distributed and spent without community input." } }, { "id": "SC-PAYMENT-DELIVERY", "name": "Last-Mile Payment Delivery", "description": "Benefits can actually reach intended recipients in remote resource-extraction areas. Payment channels must work where extraction happens, often areas with limited banking infrastructure.", "weight": 0.15, "ratingGuide": { "5": "Multiple payment channels (mobile money, bank transfer, community fund accounts). Works in areas with no banking infrastructure. Real-time payment confirmation to recipients. Handles individual and community-level payments. Low transaction costs.", "4": "Mobile money and bank transfer options. Payment confirmation. Community and individual payment support. Reasonable transaction costs.", "3": "Bank transfer primary with mobile money as option. Payment tracking. Individual or community payments (not both natively).", "2": "Bank transfer only. Requires recipients to have bank accounts. Payment confirmation delayed.", "1": "Cash-based or manual transfer only. No digital payment integration. No payment confirmation system." } }, { "id": "SC-EXTRACTION-LINKAGE", "name": "Extraction-to-Benefit Data Linkage", "description": "Benefit distribution is directly linked to verified extraction data. Without a provable connection between what was extracted and what was shared, communities cannot hold extractors accountable.", "weight": 0.1, "ratingGuide": { "5": "Direct on-chain linkage between verified extraction volumes and benefit calculations. Any stakeholder can trace from extraction event through revenue to distribution. Cross-references with UC-H-103 extraction monitoring data.", "4": "Extraction data feeds into benefit calculation. Linkage auditable. Regular reconciliation between extraction and distribution records.", "3": "Extraction data imported manually into benefit system. Periodic reconciliation. Linkage exists but requires manual verification.", "2": "Extraction and benefit data in separate systems. Reconciliation annual and manual.", "1": "No linkage between extraction and benefit data. Benefits distributed based on reported (unverified) extraction figures." } } ], "procurement": { "marketMaturity": "nascent", "primaryMode": "integrator-led", "alternativeModes": [ "consortium" ], "reasoning": "Community benefit sharing platforms are emerging.", "exampleProductCategories": [ "benefit-sharing-platform", "community-finance-rails" ], "partnerChannels": [], "lastReviewed": "2026-05-01" } }, { "id": "UC-H-105", "name": "Water rights management", "category": "H", "subcategory": "Water Resources", "description": "Allocate water between farms and towns by agreed rules, so everyone can see who received what during a shortage.", "bCriteria": [ "B1", "B3", "B7" ], "requiredComponents": [ "registry-platform", "smart-contracts", "audit-trail" ], "conditionalComponents": [ "iot-sensors", "monitoring-platform" ], "crossCategoryDependencies": [ "UC-H-106" ], "p2TriggerConditions": { "description": "Activated when P2 shows water scarcity contexts with multiple competing water users and regulatory compliance requirements", "rangeSignals": [ "waterScarcity >=2", "multipleWaterUsers >=3", "regulatoryRequired = true" ] }, "contextFieldsTemplate": [ "water_allocation_methodology", "competing_user_types", "seasonal_variation_degree", "measurement_infrastructure", "dispute_frequency", "regulatory_jurisdiction", "drought_contingency_plan" ], "implementationComplexity": "high", "examples": { "note": "Irrigation management and IWRM integration", "references": [ { "name": "Water Allocation Smart Contracts for Agricultural Basin Management", "description": "Blockchain-based water rights allocation and measurement system with seasonal adjustment", "year": 2019, "relevance": "high", "technologies": [ "Smart Contracts", "IoT Sensors" ] }, { "name": "UNESCO International Water Law Framework", "description": "Transboundary water management principles and allocation methodologies", "year": 2015, "relevance": "high", "technologies": [ "Legal Framework", "Policy Design" ] }, { "name": "FAO Water and Agriculture Program", "description": "Global framework for water allocation, competing uses management, and drought contingency planning", "year": 2018, "relevance": "high", "technologies": [ "Allocation Methodology", "Monitoring Framework" ] } ] }, "briefSection": "Reporting and audit", "solutionQuestions": [ { "id": "water-allocation-methodology", "type": "select", "options": [ { "label": "Volumetric allocation with automated seasonal adjustment rules", "value": "volumetric-allocation" }, { "label": "Priority-based water rights with junior/senior tier management", "value": "priority-tiers" }, { "label": "Proportional-need allocation with environmental flow requirements", "value": "proportional-need" } ], "prefillFrom": null, "briefSection": "Registry platform", "propertyMapping": { "volumetric-allocation": { "technologies": [ "Smart Contracts", "Oracle Networks" ], "technologyProperties": { "allocationModel": "volumetric", "seasonalAdjustment": "yes", "automation": "yes" } }, "priority-tiers": { "technologies": [ "Blockchain Tiers", "Smart Contracts" ], "technologyProperties": { "priorityModel": "multi-tier", "juniorSenior": "yes", "enforcement": "automated" } }, "proportional-need": { "technologies": [ "Smart Contracts", "Environmental Oracles" ], "technologyProperties": { "model": "proportional", "needBased": "yes", "environmentalFlow": "protected" } } }, "text": "For water allocation, should rights be based on: historical use patterns, proportional population share, seasonal rotation, priority to downstream users, or other criteria?", "ngoText": "For water allocation, should rights be based on: historical use patterns, proportional population share, seasonal rotation, priority to downstream users, or other criteria?" }, { "id": "seasonal-variation-adaptation", "type": "select", "options": [ { "label": "Dynamic allocation adjustment based on real-time water availability", "value": "dynamic-adjustment" }, { "label": "Proportional reduction mechanism during drought conditions", "value": "proportional-reduction" }, { "label": "Seasonal quota system with carry-over rights and banking", "value": "seasonal-banking" } ], "prefillFrom": null, "briefSection": "Infrastructure requirements", "propertyMapping": { "dynamic-adjustment": { "technologies": [ "Oracle Networks", "Smart Contracts" ], "technologyProperties": { "adjustmentFrequency": "real-time", "dataSource": "hydrological-sensors", "fairness": "algorithm-based" } }, "proportional-reduction": { "technologies": [ "Smart Contracts", "Water Level Sensors" ], "technologyProperties": { "reductionModel": "proportional", "thresholds": "predefined", "stakeholderNotification": "automatic" } }, "seasonal-banking": { "technologies": [ "Smart Contracts", "Token Banking" ], "technologyProperties": { "quotaModel": "seasonal", "carryOver": "allowed", "bankingPeriod": "1-2 years" } } }, "text": "How do you currently adapt water allocation for seasonal variations?", "ngoText": "How do you currently adapt water allocation for seasonal variations?" }, { "id": "measurement-infrastructure", "type": "select", "options": [ { "label": "Flow meter networks with IoT data streams to digital ledger", "value": "iot-flow-meters" }, { "label": "Satellite remote sensing with water level tracking", "value": "satellite-water-level" }, { "label": "Manual meter reading with digital ledger-recorded audit trail", "value": "manual-meter-audit" }, { "label": "Hybrid IoT-satellite monitoring with cross-validation protocols", "value": "hybrid-water-monitoring" } ], "prefillFrom": null, "briefSection": "Infrastructure requirements", "propertyMapping": { "iot-flow-meters": { "technologies": [ "IoT Sensors", "LoRaWAN", "Smart Contracts" ], "technologyProperties": { "measurement": "real-time", "accuracy": "high", "reportingFrequency": "1-minute" } }, "satellite-water-level": { "technologies": [ "Open satellite ocean and land monitoring", "Altimetry Data" ], "technologyProperties": { "resolution": "300m", "updateFrequency": "27-days", "largeScale": "yes" } }, "manual-meter-audit": { "technologies": [ "Blockchain Records", "Digital Meters" ], "technologyProperties": { "readingFrequency": "monthly", "auditTrail": "immutable", "tamperDetection": "yes" } }, "hybrid-water-monitoring": { "technologies": [ "IoT Sensors", "Open satellite ocean and land monitoring", "Smart Contracts" ], "technologyProperties": { "coverage": "comprehensive", "redundancy": "yes", "crossValidation": "yes" } } }, "text": "For water measurement, what methods are currently available or feasible in your context?", "ngoText": "For water measurement, what methods are currently available or feasible in your context?" }, { "id": "drought-contingency-planning", "type": "select", "options": [ { "label": "Automated drought trigger with pre-programmed allocation reduction", "value": "automated-drought-trigger" }, { "label": "Emergency water council activation with rapid stakeholder convening", "value": "emergency-council" }, { "label": "Water banking and strategic reserve mechanism with emergency release protocols", "value": "water-banking" } ], "prefillFrom": null, "briefSection": "Infrastructure requirements", "propertyMapping": { "automated-drought-trigger": { "technologies": [ "Smart Contracts", "Oracle Networks" ], "technologyProperties": { "triggerCondition": "automated", "activation": "instant", "reduction": "predetermined" } }, "emergency-council": { "technologies": [ "Smart Contracts", "Notification System" ], "technologyProperties": { "convening": "rapid", "stakeholders": "all", "transparency": "high" } }, "water-banking": { "technologies": [ "Water Storage Smart Contracts", "Supply Chain Oracles" ], "technologyProperties": { "banking": "yes", "reserves": "strategic", "emergencyRelease": "automated" } } }, "text": "What drought contingency and emergency response approach do you currently use?", "ngoText": "What drought contingency and emergency response approach do you currently use?" }, { "id": "transboundary-water-coordination", "type": "select", "options": [ { "label": "Bilateral/multilateral agreement framework with digital verification", "value": "multilateral-agreement" }, { "label": "Shared ledger system with all riparian states as validators", "value": "shared-ledger-riparian" }, { "label": "No transboundary issues, single jurisdiction water management", "value": "single-jurisdiction" }, { "label": "Informal cooperation between neighbouring communities across borders", "value": "informal-cooperation" }, { "label": "Not sure, transboundary aspects are unclear or emerging", "value": "unsure" } ], "prefillFrom": null, "briefSection": "Government interoperability", "propertyMapping": { "multilateral-agreement": { "technologies": [ "Smart Contracts", "Multi-sig Governance" ], "technologyProperties": { "agreements": "international", "enforcement": "blockchain-based", "transparency": "yes" } }, "shared-ledger-riparian": { "technologies": [ "Consortium Blockchain", "Multi-sig Validation" ], "technologyProperties": { "ledgerOwnership": "shared", "validators": "all-riparian", "consensus": "required" } }, "single-jurisdiction": { "technologies": [ "Local water management platform" ], "technologyProperties": { "transboundaryScope": "None", "coordinationModel": "Single jurisdiction", "verificationNeeded": "Local only" } }, "informal-cooperation": { "technologies": [ "Cross-community data sharing", "Informal agreement tracking" ], "technologyProperties": { "transboundaryScope": "Neighbouring communities", "coordinationModel": "Informal bilateral", "verificationNeeded": "Community-level" } }, "unsure": { "technologies": [ "Transboundary assessment needed" ], "technologyProperties": { "transboundaryScope": "TBD", "coordinationModel": "TBD", "verificationNeeded": "TBD" } } }, "text": "What coordination mechanisms do you have for transboundary water resources?", "ngoText": "What coordination mechanisms do you have for transboundary water resources?" }, { "id": "registry-platform-approach", "type": "select", "options": [ { "label": "Government-integrated registry (supplement existing land authority)", "value": "gov-integrated" }, { "label": "Standalone digital ledger registry (parallel to government system)", "value": "standalone-chain" }, { "label": "Community-managed registry with local authority endorsement", "value": "community-managed" }, { "label": "Not sure, need guidance on registry approach", "value": "guidance-needed" } ], "propertyMapping": { "gov-integrated": { "technologies": [ "Government-integrated registry platform", "Authority system connection", "Registry verification service" ], "technologyProperties": { "legalStatus": "Government-recognised", "managedBy": "Government authority with blockchain backend", "disputeResolution": "Through existing legal channels" } }, "standalone-chain": { "technologies": [ "Standalone blockchain registry platform", "Decentralised registry service", "Registry verification service" ], "technologyProperties": { "legalStatus": "Evidence-grade (may require legal framework)", "managedBy": "NGO/consortium-operated", "disputeResolution": "Automatedarbitration + legal" } }, "community-managed": { "technologies": [ "Community registry platform", "Local authority endorsement module", "Registry verification service" ], "technologyProperties": { "legalStatus": "Community-endorsed with local authority backing", "managedBy": "Community with NGO facilitation", "disputeResolution": "Community governance + mediation" } }, "guidance-needed": { "technologies": [ "Registry platform framework", "Registry verification service" ], "technologyProperties": { "legalStatus": "To be determined", "managedBy": "To be determined", "disputeResolution": "To be determined" } } }, "prefillFrom": null, "briefSection": "Registry design", "text": "What type of registry platform is appropriate for this context?", "ngoText": "What type of registry platform is appropriate for this context?" }, { "id": "audit-trail-approach", "type": "select", "options": [ { "label": "Donors and external auditors need to independently verify any action at any time", "value": "donors-and-external-auditors-need-to-ind" }, { "label": "External auditors check periodically: summary reports and spot-checks are sufficient", "value": "external-auditors-check-periodically-sum" }, { "label": "Key milestones and approvals need independent verification; routine actions just need internal records", "value": "key-milestones-and-approvals-need-indepe" }, { "label": "Internal team records are sufficient: we mainly need our own staff to be able to look back", "value": "internal-team-records-are-sufficient-we-" }, { "label": "Not sure, need guidance on audit requirements", "value": "not-sure-need-guidance-on-audit-requirem" } ], "propertyMapping": { "full-immutable": { "technologies": [ "Immutable audit trail", "On-chain event logging", "Audit trail verification service" ], "technologyProperties": { "auditGranularity": "Every action", "storageApproach": "Full on-chain logging", "tamperEvidence": "Cryptographic hash chain" } }, "key-events": { "technologies": [ "Milestone-based audit trail", "Approval chain logger", "Audit trail verification service" ], "technologyProperties": { "auditGranularity": "Key milestones and approvals only", "storageApproach": "Selective on-chain logging", "tamperEvidence": "Merkle root anchoring" } }, "hybrid": { "technologies": [ "Hybrid audit trail system", "Off-chain storage with hash anchoring", "Audit trail verification service" ], "technologyProperties": { "auditGranularity": "Metadata on-chain, full records off-chain", "storageApproach": "Decentralised/off-chain storage with on-chain hash proofs", "tamperEvidence": "Hash anchoring to blockchain" } }, "guidance-needed": { "technologies": [ "Audit trail framework", "Audit trail verification service" ], "technologyProperties": { "auditGranularity": "To be determined during solution design", "storageApproach": "To be determined", "tamperEvidence": "To be determined" } } }, "prefillFrom": null, "briefSection": "Audit and evidence", "text": "What level of audit trail does this solution require?", "ngoText": "What level of audit trail does this solution require?", "hidden": true, "question": "Who needs to verify that actions in this system happened correctly, and how easily should they be able to check?" } ], "complexityFactors": { "relationships": 4, "operationalChange": 3, "dataCompliance": 3 }, "suggestedCriteria": [ { "id": "SC-ALLOCATION-RULES", "name": "Rules-Based Water Allocation", "description": "Can the system enforce transparent, configurable water allocation rules (priority-based, proportional, seasonal, or needs-based) rather than informal or opaque distribution?", "weight": 0.3, "ratingGuide": { "5": "Smart contract-based allocation with configurable priority rules. Supports priority-based, proportional, rotational, and seasonal allocation schemes. Automatic adjustment for drought conditions. Multi-stakeholder rule governance. Proven deployment in water-scarce settings.", "4": "Rule-based allocation with configurable parameters. Multiple allocation schemes supported. Drought adjustment capability. Stakeholder input on rule changes.", "3": "Fixed allocation rules with manual adjustment capability. One or two allocation schemes. Seasonal variation handled through manual rule updates.", "2": "Static allocation table. No rule engine. Changes require system modification. No seasonal or emergency adjustment.", "1": "No allocation rules. System records water use only, with no allocation or entitlement management." } }, { "id": "SC-MEASUREMENT-INTEGRATION", "name": "Water Measurement & Metering Integration", "description": "The system can integrate with physical water measurement infrastructure (flow meters, rain gauges, groundwater level sensors) for verified usage data. Allocation rules are meaningless without accurate measurement.", "weight": 0.25, "ratingGuide": { "5": "Direct IoT integration with flow meters, level sensors, and weather stations. Real-time usage data. Automated anomaly detection (over-extraction, equipment failure). Handles multiple measurement technologies. Calibration tracking and data quality scoring.", "4": "IoT integration for major measurement points. Near-real-time data. Basic anomaly alerts. Supports common meter protocols.", "3": "Manual meter reading entry with digital forms. Periodic data upload. Basic usage tracking. Limited IoT support.", "2": "Manual entry of estimated usage. No meter integration. Periodic volume estimates only.", "1": "No measurement integration. Allocation tracking based on entitlements only, not actual usage." } }, { "id": "SC-COMPETING-USERS", "name": "Multi-User Conflict Prevention", "description": "The system manages competing demands (agriculture, domestic, industrial, environmental) with transparent prioritisation and early warning. Water conflicts escalate rapidly in scarce conditions.", "weight": 0.2, "ratingGuide": { "5": "Multi-user type management with configurable priority hierarchy. Scarcity early warning system based on supply/demand modelling. Automated curtailment notifications by priority level. Dispute logging and resolution tracking. Historical usage pattern analysis.", "4": "User type categorisation with priority levels. Basic scarcity alerts. Curtailment notification supported. Dispute tracking included.", "3": "User categories tracked. Manual scarcity assessment. Curtailment decisions made manually with system notification. Basic dispute recording.", "2": "All users treated equally. No priority hierarchy. No scarcity modelling. Disputes handled outside system.", "1": "Single-user-type design. No competing demand management. No scarcity awareness." } }, { "id": "SC-SEASONAL-DROUGHT", "name": "Seasonal & Drought Adaptability", "description": "Can the system dynamically adjust allocations based on changing water availability (seasonal patterns, drought declarations, upstream events) without manual reconfiguration each time?", "weight": 0.15, "ratingGuide": { "5": "Automatic allocation adjustment based on supply data feeds. Drought stage escalation with pre-defined curtailment rules. Seasonal pattern modelling. Upstream event propagation (dam release, upstream extraction). Climate forecast integration.", "4": "Semi-automatic adjustment with administrator approval. Drought stage management. Seasonal rule switching. Basic upstream impact awareness.", "3": "Manual seasonal allocation changes. Drought response requires administrator intervention. No upstream event integration.", "2": "Fixed annual allocations. Drought requires complete re-allocation manually. No seasonal awareness.", "1": "Static allocations with no adaptability. System cannot respond to changing water conditions." } }, { "id": "SC-ENVIRONMENTAL-FLOW", "name": "Environmental Flow & Ecosystem Protection", "description": "The system enforces minimum environmental flow requirements and ecosystem water needs alongside human allocation. Sustainable water management requires protecting the water source itself.", "weight": 0.1, "ratingGuide": { "5": "Environmental flow as a non-negotiable allocation. Ecosystem health indicators integrated. Automatic human allocation reduction if environmental minimums threatened. Biodiversity monitoring linkage. Compliance with national environmental flow standards.", "4": "Environmental flow tracked as a priority allocation. Basic ecosystem indicators. Alerts when environmental minimums approached. Standards compliance reporting.", "3": "Environmental flow recorded as a separate allocation category. Manual monitoring. Compliance checked periodically.", "2": "Environmental flow noted in system but not enforced. No monitoring. Compliance is aspirational only.", "1": "No environmental flow concept. System allocates all available water to human users." } } ], "procurement": { "marketMaturity": "nascent", "primaryMode": "consortium", "alternativeModes": [ "integrator-led" ], "reasoning": "Water rights management is mostly research-stage.", "exampleProductCategories": [ "water-rights-platform", "natural-resource-rails" ], "partnerChannels": [], "lastReviewed": "2026-05-01" } }, { "id": "UC-H-106", "name": "Fishing rights and marine resource access", "category": "H", "subcategory": "Marine Resources", "description": "Manage fishing licences and catch records so that communities with traditional fishing rights and government agencies work from the same figures.", "bCriteria": [ "B1", "B3", "B4" ], "requiredComponents": [ "registry-platform", "audit-trail", "iot-sensors" ], "conditionalComponents": [ "smart-contracts", "monitoring-platform" ], "crossCategoryDependencies": [ "UC-I-114" ], "p2TriggerConditions": { "description": "Activated when P2 shows marine resource management with catch tracking needs and multiple stakeholder groups", "rangeSignals": [ "marineResourceManagement >=3", "catchTracking >=2", "multipleStakeholders >=3" ] }, "contextFieldsTemplate": [ "fishing_community_size", "total_allowable_catch", "license_allocation_rules", "geographic_fishing_areas", "catch_monitoring_method", "enforcement_capacity", "ecosystem_sustainability_monitoring" ], "implementationComplexity": "high", "examples": { "note": "FAO small-scale fisheries tracking", "references": [ { "name": "FAO Global Record of Fishing Vessels", "description": "International catch documentation and vessel monitoring for sustainable fisheries management", "year": 2018, "relevance": "high", "technologies": [ "Catch Documentation", "VMS Monitoring" ] }, { "name": "Blockchain-Based Catch Documentation System", "description": "Smart contract-mediated fishing rights, quota tracking, and supply chain transparency", "year": 2020, "relevance": "high", "technologies": [ "Smart Contracts", "Blockchain Records" ] }, { "name": "Marine Stewardship Council Certified Fisheries", "description": "Sustainability certification framework with blockchain integration for market access", "year": 2019, "relevance": "high", "technologies": [ "Certification", "Blockchain Integration" ] } ] }, "briefSection": "Infrastructure requirements", "solutionQuestions": [ { "id": "fishing-license-model", "type": "select", "options": [ { "label": "Individual transferable quotas as digital ledger tokens", "value": "itq-tokens" }, { "label": "Community fishing licenses with collective catch allocation", "value": "community-licenses" }, { "label": "Area-based management zones with spatial fishing rights NFTs", "value": "area-based-nfts" }, { "label": "Species-specific licenses with differential rights per species", "value": "species-specific" } ], "prefillFrom": null, "briefSection": "Registry platform", "propertyMapping": { "itq-tokens": { "technologies": [ "ERC-20 Tokens", "Smart Contracts" ], "technologyProperties": { "tokenStandard": "ERC-20", "tradeable": "yes", "quotaTracking": "automated" } }, "community-licenses": { "technologies": [ "DAO Governance", "Smart Contracts" ], "technologyProperties": { "licenseType": "community", "allocation": "collective", "distribution": "voted" } }, "area-based-nfts": { "technologies": [ "ERC-721 NFTs", "GIS Integration" ], "technologyProperties": { "tokenStandard": "ERC-721", "geographic": "yes", "exclusivity": "spatial" } }, "species-specific": { "technologies": [ "Smart Contracts", "Conditional Tokens" ], "technologyProperties": { "speciesTracking": "yes", "conditionalRights": "yes", "flexibility": "high" } } }, "text": "For fishing rights, should licensing be based on: traditional fishing families, gear-based limits, area-based zones, species-based restrictions, or combination?", "ngoText": "For fishing rights, should licensing be based on: traditional fishing families, gear-based limits, area-based zones, species-based restrictions, or combination?" }, { "id": "catch-monitoring-system", "type": "select", "options": [ { "label": "Vessel monitoring system with digital ledger catch reporting", "value": "vms-blockchain" }, { "label": "Electronic catch documentation system with photo verification", "value": "ecd-photo-verification" }, { "label": "Port-based monitoring with weight verification and digital ledger audit", "value": "port-monitoring" }, { "label": "Autonomous observer drones with AI catch species identification", "value": "observer-drones-ai" } ], "prefillFrom": null, "briefSection": "Mapping and geospatial", "propertyMapping": { "vms-blockchain": { "technologies": [ "VMS Satellite", "Blockchain" ], "technologyProperties": { "realTime": "yes", "location": "tracked", "catchData": "blockchain-recorded" } }, "ecd-photo-verification": { "technologies": [ "Mobile App", "Photo Verification", "Blockchain" ], "technologyProperties": { "documentation": "electronic", "photoProof": "required", "species": "identified" } }, "port-monitoring": { "technologies": [ "IoT Scales", "Blockchain", "Government Systems" ], "technologyProperties": { "monitoringLocation": "ports", "verification": "automated", "transparency": "high" } }, "observer-drones-ai": { "technologies": [ "Drone Surveillance", "Machine Learning" ], "technologyProperties": { "automation": "high", "speciesID": "AI-powered", "accuracy": "95%" } } }, "text": "What catch monitoring is currently feasible in your context?", "ngoText": "What catch monitoring is currently feasible in your context?" }, { "id": "enforcement-mechanisms", "type": "select", "options": [ { "label": "Automated penalties when quota violations are detected", "value": "automated-penalties-when-quota-violation" }, { "label": "Official enforcement with digital evidence chain for prosecution", "value": "official-enforcement-with-digital-eviden" }, { "label": "Community monitoring with incentives for compliance", "value": "community-monitoring-with-incentives-for" }, { "label": "Insurance-based approach with performance bonds and automated claims", "value": "insurance-based-approach-with-performanc" }, { "label": "Not sure, need guidance", "value": "not-sure-need-guidance" } ], "prefillFrom": null, "briefSection": "Reporting and audit", "propertyMapping": { "auto-penalties": { "technologies": [ "Smart Contracts", "Oracle Networks" ], "technologyProperties": { "penaltyExecution": "automated", "immediacy": "yes", "appealProcess": "enabled" } }, "coast-guard-blockchain": { "technologies": [ "Blockchain Records", "Government Integration" ], "technologyProperties": { "enforcementAgent": "coast-guard", "evidenceChain": "immutable", "legalProof": "yes" } }, "community-monitoring": { "technologies": [ "Blockchain Incentives", "Governance Tokens" ], "technologyProperties": { "monitoring": "community-based", "reporting": "incentivized", "reputation": "tracked" } }, "catch-insurance": { "technologies": [ "Insurance Contracts", "Smart Contracts" ], "technologyProperties": { "bondRequirement": "yes", "automatedClaims": "yes", "enforcement": "financial" } } }, "text": "What enforcement mechanisms should be implemented?", "ngoText": "What enforcement mechanisms should be implemented?", "question": "What enforcement mechanisms are needed and feasible in your context?" }, { "id": "sustainability-compliance", "type": "select", "options": [ { "label": "Ecosystem health indicators with oracle-triggered license suspension", "value": "ecosystem-health-oracle" }, { "label": "Seasonal fishing closures with automated rules enforcement", "value": "seasonal-closures" }, { "label": "Endangered species protection with digitally verified catch exclusion", "value": "endangered-protection" } ], "prefillFrom": null, "briefSection": "Reporting and audit", "propertyMapping": { "ecosystem-health-oracle": { "technologies": [ "Environmental Oracles", "Smart Contracts" ], "technologyProperties": { "healthMetrics": "tracked", "oracleTriggers": "yes", "suspensionAutomation": "yes" } }, "seasonal-closures": { "technologies": [ "Smart Contracts", "Time-locked Functions" ], "technologyProperties": { "seasonalRules": "coded", "enforcement": "automated", "breeding": "protected" } }, "endangered-protection": { "technologies": [ "Smart Contracts", "Species Database" ], "technologyProperties": { "speciesProtection": "yes", "exclusion": "enforced", "penalties": "strict" } } }, "text": "What sustainability standards must your land/resource management comply with?", "ngoText": "What sustainability standards must your land/resource management comply with?" }, { "id": "market-access-sustainability", "type": "select", "options": [ { "label": "Supply chain certification with digital proof of sustainability", "value": "supply-chain-cert" }, { "label": "Digitally certified sustainable seafood with market tracking and transparency", "value": "tokenized-seafood" }, { "label": "Dynamic fishing license pricing based on sustainability compliance score", "value": "dynamic-pricing" } ], "prefillFrom": null, "briefSection": "Infrastructure requirements", "propertyMapping": { "supply-chain-cert": { "technologies": [ "Blockchain Certificates", "Supply Chain Tracking" ], "technologyProperties": { "certification": "yes", "verification": "blockchain-backed", "market": "premium" } }, "tokenized-seafood": { "technologies": [ "ERC-721 NFTs", "Supply Chain" ], "technologyProperties": { "tokenization": "yes", "traceability": "complete", "marketPremium": "yes" } }, "dynamic-pricing": { "technologies": [ "Smart Contracts", "Oracle Networks" ], "technologyProperties": { "pricingModel": "dynamic", "complianceMetric": "tracked", "incentive": "market-based" } } }, "text": "How do you currently ensure market access for sustainable products?", "ngoText": "How do you currently ensure market access for sustainable products?" }, { "id": "stakeholder-participation", "type": "select", "options": [ { "label": "Multi-stakeholder governance body with proportional voting rights", "value": "multi-stakeholder-governance" }, { "label": "Co-management committee with digitally recorded decisions", "value": "co-management-committee" }, { "label": "Advisory board with community consultation (decisions recorded but not binding votes)", "value": "advisory-board" }, { "label": "Government-led with community input sessions", "value": "govt-led" }, { "label": "Not sure, stakeholder engagement model still being designed", "value": "unsure" } ], "prefillFrom": null, "briefSection": "Community validation", "propertyMapping": { "co-management-committee": { "technologies": [ "Smart Contracts", "Governance Logs" ], "technologyProperties": { "comanagement": "yes", "decisionRecording": "blockchain", "transparency": "yes" } }, "multi-stakeholder-governance": { "technologies": [ "DAO Governance", "Governance Tokens" ], "technologyProperties": { "stakeholders": "multiple", "votingModel": "proportional", "transparency": "high" } }, "advisory-board": { "technologies": [ "Consultation tracking platform", "Decision audit trail" ], "technologyProperties": { "stakeholders": "Advisory", "votingModel": "Consultative (non-binding)", "transparency": "Medium" } }, "govt-led": { "technologies": [ "Government decision platform", "Community input portal" ], "technologyProperties": { "stakeholders": "Government-led", "votingModel": "Government authority with input", "transparency": "Varies" } }, "unsure": { "technologies": [ "Stakeholder engagement design needed" ], "technologyProperties": { "stakeholders": "TBD", "votingModel": "TBD", "transparency": "TBD" } } }, "text": "How are stakeholders currently involved in sustainability decisions?", "ngoText": "How are stakeholders currently involved in sustainability decisions?" }, { "id": "registry-platform-approach", "type": "select", "options": [ { "label": "Government-integrated registry (supplement existing land authority)", "value": "gov-integrated" }, { "label": "Standalone digital ledger registry (parallel to government system)", "value": "standalone-chain" }, { "label": "Community-managed registry with local authority endorsement", "value": "community-managed" }, { "label": "Not sure, need guidance on registry approach", "value": "guidance-needed" } ], "propertyMapping": { "gov-integrated": { "technologies": [ "Government-integrated registry platform", "Authority system connection", "Registry verification service" ], "technologyProperties": { "legalStatus": "Government-recognised", "managedBy": "Government authority with blockchain backend", "disputeResolution": "Through existing legal channels" } }, "standalone-chain": { "technologies": [ "Standalone blockchain registry platform", "Decentralised registry service", "Registry verification service" ], "technologyProperties": { "legalStatus": "Evidence-grade (may require legal framework)", "managedBy": "NGO/consortium-operated", "disputeResolution": "Automatedarbitration + legal" } }, "community-managed": { "technologies": [ "Community registry platform", "Local authority endorsement module", "Registry verification service" ], "technologyProperties": { "legalStatus": "Community-endorsed with local authority backing", "managedBy": "Community with NGO facilitation", "disputeResolution": "Community governance + mediation" } }, "guidance-needed": { "technologies": [ "Registry platform framework", "Registry verification service" ], "technologyProperties": { "legalStatus": "To be determined", "managedBy": "To be determined", "disputeResolution": "To be determined" } } }, "prefillFrom": null, "briefSection": "Registry design", "text": "What type of registry platform is appropriate for this context?", "ngoText": "What type of registry platform is appropriate for this context?" }, { "id": "audit-trail-approach", "type": "select", "options": [ { "label": "Donors and external auditors need to independently verify any action at any time", "value": "donors-and-external-auditors-need-to-ind" }, { "label": "External auditors check periodically: summary reports and spot-checks are sufficient", "value": "external-auditors-check-periodically-sum" }, { "label": "Key milestones and approvals need independent verification; routine actions just need internal records", "value": "key-milestones-and-approvals-need-indepe" }, { "label": "Internal team records are sufficient: we mainly need our own staff to be able to look back", "value": "internal-team-records-are-sufficient-we-" }, { "label": "Not sure, need guidance on audit requirements", "value": "not-sure-need-guidance-on-audit-requirem" } ], "propertyMapping": { "full-immutable": { "technologies": [ "Immutable audit trail", "On-chain event logging", "Audit trail verification service" ], "technologyProperties": { "auditGranularity": "Every action", "storageApproach": "Full on-chain logging", "tamperEvidence": "Cryptographic hash chain" } }, "key-events": { "technologies": [ "Milestone-based audit trail", "Approval chain logger", "Audit trail verification service" ], "technologyProperties": { "auditGranularity": "Key milestones and approvals only", "storageApproach": "Selective on-chain logging", "tamperEvidence": "Merkle root anchoring" } }, "hybrid": { "technologies": [ "Hybrid audit trail system", "Off-chain storage with hash anchoring", "Audit trail verification service" ], "technologyProperties": { "auditGranularity": "Metadata on-chain, full records off-chain", "storageApproach": "Decentralised/off-chain storage with on-chain hash proofs", "tamperEvidence": "Hash anchoring to blockchain" } }, "guidance-needed": { "technologies": [ "Audit trail framework", "Audit trail verification service" ], "technologyProperties": { "auditGranularity": "To be determined during solution design", "storageApproach": "To be determined", "tamperEvidence": "To be determined" } } }, "prefillFrom": null, "briefSection": "Audit and evidence", "text": "What level of audit trail does this solution require?", "ngoText": "What level of audit trail does this solution require?", "hidden": true, "question": "Who needs to verify that actions in this system happened correctly, and how easily should they be able to check?" }, { "id": "iot-sensor-approach", "type": "select", "options": [ { "label": "GPS/location tracking devices", "value": "gps-location" }, { "label": "Environmental sensors (temperature, humidity, etc.)", "value": "environmental" }, { "label": "Smart meters (energy, water usage)", "value": "smart-meters" }, { "label": "Mobile phone-based data collection (photos, GPS, manual entry)", "value": "mobile-collection" } ], "propertyMapping": { "gps-location": { "technologies": [ "GPS tracking IoT devices", "IoT sensor data gateway", "Location verification oracle" ], "technologyProperties": { "sensorType": "GPS/GNSS trackers", "dataFrequency": "Configurable (real-time to daily)", "connectivity": "Cellular/satellite" } }, "environmental": { "technologies": [ "Environmental IoT sensors", "IoT sensor data gateway", "Threshold alert service" ], "technologyProperties": { "sensorType": "Temperature, humidity, air quality sensors", "dataFrequency": "Continuous with threshold alerts", "connectivity": "LoRaWAN/cellular" } }, "smart-meters": { "technologies": [ "Smart meter IoT integration", "IoT sensor data gateway", "Usage verification service" ], "technologyProperties": { "sensorType": "Smart meters (energy/water)", "dataFrequency": "Hourly/daily readings", "connectivity": "LoRaWAN/cellular/Wi-Fi" } }, "mobile-collection": { "technologies": [ "Mobile data collection app", "IoT sensor proxy layer", "Photo/GPS verification service" ], "technologyProperties": { "sensorType": "Smartphone (camera, GPS, manual entry)", "dataFrequency": "Event-driven (field visits)", "connectivity": "Offline-first with sync" } } }, "prefillFrom": null, "briefSection": "Data collection", "text": "What type of sensor or data collection devices will be used?", "ngoText": "What type of sensor or data collection devices will be used?" } ], "complexityFactors": { "relationships": 4, "operationalChange": 3, "dataCompliance": 3 }, "suggestedCriteria": [ { "id": "SC-LICENSE-MANAGEMENT", "name": "Fishing License & Permit Management", "description": "The system can issue, track, renew, and enforce fishing licenses with clear entitlements per license holder. License management is the foundation of fisheries governance. Without it, catch limits are unenforceable.", "weight": 0.25, "ratingGuide": { "5": "Full license lifecycle management: application, issuance, renewal, suspension, revocation. Per-license entitlements (area, species, gear type, quota). Digital license verification in the field. Integration with national fisheries authority. Multi-species and multi-zone support.", "4": "License issuance and tracking. Entitlement management. Digital verification supported. Single fisheries authority integration. Multi-zone capability.", "3": "License registry with basic entitlement tracking. Manual verification. Data export for authority reporting. Single-zone focus.", "2": "License list with holder details. No entitlement management. Paper-based verification. Manual reporting.", "1": "No license management. System tracks catch data only without linking to license entitlements." } }, { "id": "SC-CATCH-MONITORING", "name": "Catch Monitoring & Quota Tracking", "description": "The system can track catch volumes against quotas in near-real-time. Overfishing happens quickly. Weekly or monthly reporting is too slow to prevent quota breaches.", "weight": 0.25, "ratingGuide": { "5": "Real-time catch reporting via mobile at landing sites. Automatic quota deduction per landing. Species-level catch recording. Overfishing alerts before quota exhaustion. Integration with vessel monitoring systems (VMS). Community catch monitors supported.", "4": "Daily catch reporting with quota tracking. Species-level recording. Quota approach alerts. Basic VMS integration. Mobile reporting supported.", "3": "Regular catch reporting with manual quota comparison. Aggregated species data. Periodic quota status reporting. Desktop-based entry.", "2": "Periodic catch surveys entered manually. No real-time quota tracking. Species data estimated. Reports generated quarterly.", "1": "No catch monitoring. System manages licenses only with no link to actual fishing activity." } }, { "id": "SC-COMMUNITY-ACCESS-RIGHTS", "name": "Customary & Community Access Rights", "description": "The system recognises and protects traditional fishing rights alongside formal licensing. Small-scale and artisanal fishers often have customary access rights that predate, and should coexist with, formal fisheries management.", "weight": 0.2, "ratingGuide": { "5": "Customary fishing zones and seasonal access rights documented and enforced alongside commercial licenses. Community-defined no-take zones. Traditional knowledge integration for species management. Priority access for small-scale artisanal fishers. Community governance of customary zones.", "4": "Customary access zones recognised. Small-scale fisher priority. Community zone management. Basic seasonal access rules.", "3": "Small-scale fisher category in licensing. Community zones recorded but not enforced through system. Limited seasonal access management.", "2": "Single license type for all fishers. No customary right recognition. Commercial and artisanal treated identically.", "1": "Commercial licensing only. No accommodation for small-scale, artisanal, or customary fishing rights." } }, { "id": "SC-MARINE-SUSTAINABILITY", "name": "Ecosystem Sustainability & Stock Management", "description": "The system integrates fisheries data with ecosystem health indicators to support sustainable management. Fishing rights without ecological limits lead to stock collapse.", "weight": 0.2, "ratingGuide": { "5": "Stock assessment data integration. Catch-per-unit-effort tracking. Spawning season automatic closures. Marine protected area enforcement. Biodiversity indicators. Sustainable yield modelling. Scientific data feeds from fisheries research institutions.", "4": "Basic stock indicators tracked. CPUE monitoring. Seasonal closure management. MPA tracking. Some scientific data integration.", "3": "Catch trend analysis. Manual seasonal closures. MPA boundaries recorded. No stock modelling or scientific data integration.", "2": "Aggregate catch totals only. No ecological indicators. Closures managed outside system.", "1": "No sustainability features. System tracks fishing activity without any ecological context." } }, { "id": "SC-LANDING-SITE-USABILITY", "name": "Landing Site & Field Usability", "description": "The system can be used at fish landing sites, often remote coastal or lakeside locations with limited infrastructure. If catch data cannot be captured where fishing happens, monitoring data will be incomplete and delayed.", "weight": 0.1, "ratingGuide": { "5": "Full offline operation with landing-site sync. Works on basic waterproof smartphones. Photo/weight capture at landing. Multi-language including local fishing community languages. Solar-powered operation. Community monitor training programme.", "4": "Offline data capture with periodic sync. Mid-range smartphone support. Basic photo/weight capture. Multiple language support.", "3": "Limited offline capability. Requires internet for most functions. Smartphone required. Major languages only.", "2": "Online-only. Desktop or tablet. Single language. Data entry at office, not landing site.", "1": "Always-online desktop application. Cannot be used at landing sites. Data entry entirely disconnected from fishing activity." } } ], "procurement": { "marketMaturity": "nascent", "primaryMode": "consortium", "alternativeModes": [ "integrator-led" ], "reasoning": "Fishing and marine resource access is bespoke and consortium-led.", "exampleProductCategories": [ "marine-rights-platform", "fisheries-management-rails" ], "partnerChannels": [], "lastReviewed": "2026-05-01" } }, { "id": "UC-I-107", "name": "Renewable energy certificate tracking and trading", "category": "I", "subcategory": "Energy Certificates", "description": "Issue and trade renewable energy certificates so buyers can be sure each one is backed by real generation and has not been sold twice.", "bCriteria": [ "B1", "B3", "B8" ], "requiredComponents": [ "certificate-registry", "iot-sensors", "trading-mechanism", "verification-layer" ], "conditionalComponents": [ "smart-contracts", "monitoring-platform" ], "crossCategoryDependencies": [], "p2TriggerConditions": { "description": "Activated when P2 shows renewable energy generation with certificate trading needs and multiple market participants", "rangeSignals": [ "renewableEnergyGeneration >=3", "certificateTrading >=2", "marketParticipants >=3" ] }, "contextFieldsTemplate": [ "energy_generation_capacity", "generation_technology_types", "geographic_certificate_scheme", "monitoring_infrastructure", "trading_volume_baseline", "price_discovery_mechanism", "regulatory_framework" ], "implementationComplexity": "medium", "examples": { "note": "IREC and regional renewable energy credit systems", "references": [ { "name": "Energy Web Foundation (EWF)", "description": "Decentralised energy system operating on EnergyWeb Chain; produces tokenised renewable energy certificates", "url": "https://www.energyweb.org/" }, { "name": "Toucan Protocol", "description": "Carbon credit tokenisation and retirement mechanism; provides template for certificate-to-token conversion", "url": "https://toucan.earth/" }, { "name": "I-REC Registry", "description": "International renewable energy credit standard; blockchain integration for transparent tracking", "url": "https://www.irecglobal.com/" } ] }, "propertyMapping": { "renewableEnergyTokenization": { "technologies": [ "Tokenised renewable energy certificate (TREC)", "Energy-sector shared ledger" ], "technologyProperties": { "certificateStandard": "I-REC", "tokenStandard": "ERC-1155", "generationVerification": "Real-time IoT + oracle" } } }, "solutionQuestions": [ { "id": "certificate-standard", "type": "select", "options": [ { "label": "I-REC (International Renewable Energy Certificates)", "value": "i-rec" }, { "label": "GO (Guarantee of Origin - EU)", "value": "go" }, { "label": "REC (Renewable Energy Credits - US)", "value": "rec" } ], "prefillFrom": null, "briefSection": "Certificate and registry", "propertyMapping": { "i-rec": { "technologies": [ "Tokenised renewable energy certificate (TREC)", "Blockchain registry" ], "technologyProperties": { "standard": "I-REC", "registryType": "Decentralized ledger", "certificateGranularity": "MWh-level tokenization" } }, "go": { "technologies": [ "EnergyWeb Token (EWT)", "On-chain GO registry" ], "technologyProperties": { "standard": "GO", "registryType": "Energy-sector blockchain network", "certificateGranularity": "1 certificate = 1 MWh" } }, "rec": { "technologies": [ "CREDO token", "Smart contract registry" ], "technologyProperties": { "standard": "REC", "registryType": "Regional blockchain", "certificateGranularity": "1 REC = 1 MWh" } } }, "text": "Which renewable energy certificate standard applies?", "ngoText": "Which renewable energy certificate standard applies?", "hidden": true }, { "id": "generation-monitoring", "type": "select", "options": [ { "label": "Real-time IoT metering with direct digital ledger feed", "value": "iot-realtime" }, { "label": "Periodic meter readings with manual submission", "value": "manual-periodic" }, { "label": "Aggregated data from generation facilities", "value": "aggregated" } ], "prefillFrom": null, "briefSection": "Monitoring and verification", "propertyMapping": { "iot-realtime": { "technologies": [ "IoT smart meters", "Oracle network", "Automated reporting" ], "technologyProperties": { "monitoringFrequency": "Real-time (15-minute intervals)", "dataIntegrity": "Cryptographic proofs", "automationLevel": "Fully automated" } }, "manual-periodic": { "technologies": [ "SCADA systems", "Manual API submission", "Verification layer" ], "technologyProperties": { "monitoringFrequency": "Daily or monthly", "dataIntegrity": "Operator-signed attestations", "automationLevel": "Semi-automated" } }, "aggregated": { "technologies": [ "Data aggregator platform", "Batch submissions", "Certificate batching" ], "technologyProperties": { "monitoringFrequency": "Monthly batches", "dataIntegrity": "Third-party verified", "automationLevel": "Aggregator-managed" } } }, "text": "Do you have real-time IoT metering infrastructure available, or must you use periodic manual submissions?", "ngoText": "Do you have real-time IoT metering infrastructure available, or must you use periodic manual submissions?" }, { "id": "trading-mechanism", "type": "select", "options": [ { "label": "direct OTC trading with settlement", "value": "p2p-otc" }, { "label": "Centralized marketplace with clearing", "value": "cex-clearing" }, { "label": "Hybrid DEX with liquidity pools", "value": "dex-liquidity" }, { "label": "Auction-based trading mechanism", "value": "auction" } ], "prefillFrom": null, "briefSection": "Trading mechanism", "propertyMapping": { "p2p-otc": { "technologies": [ "Automated escrow", "Decentralized exchange protocol", "Atomic settlement" ], "technologyProperties": { "tradingModel": "Direct peer-to-peer", "priceDiscovery": "Bilateral negotiation", "settlement": "Atomic swap with ledger finality" } }, "cex-clearing": { "technologies": [ "Order book system", "Clearing smart contracts", "Custody solution" ], "technologyProperties": { "tradingModel": "Centralized order matching", "priceDiscovery": "Order book price discovery", "settlement": "T+1 clearance and settlement" } }, "dex-liquidity": { "technologies": [ "Automated Market Maker (AMM)", "Liquidity pools", "Flash trading protection" ], "technologyProperties": { "tradingModel": "Continuous Digital exchange", "priceDiscovery": "Algorithm-driven pricing", "settlement": "Instant Digital settlement" } }, "auction": { "technologies": [ "Automated auction", "Batch settlement", "Price oracle" ], "technologyProperties": { "tradingModel": "Dutch auction or blind bid auction", "priceDiscovery": "Auction clearing price", "settlement": "Batch settlement post-auction" } } }, "text": "How frequently will certificates be traded? (daily peer-to-peer, weekly, or monthly batch auctions?)", "ngoText": "How frequently will certificates be traded? (daily peer-to-peer, weekly, or monthly batch auctions?)" }, { "id": "registry-model", "type": "select", "options": [ { "label": "Centralized registry with digital ledger settlement layer", "value": "centralized-registry" }, { "label": "Fully digital registry with digital tokens", "value": "onchain-erc1155" }, { "label": "coordinated across organisations registry across multiple digital ledgers", "value": "federated-registry" } ], "prefillFrom": null, "briefSection": "Certificate and registry", "propertyMapping": { "centralized-registry": { "technologies": [ "Central registry database", "Blockchain settlement", "Verification API" ], "technologyProperties": { "registryArchitecture": "Centralized database with blockchain validation", "uniquenessGuarantee": "Registry-enforced single issuance", "doubleSpendPrevention": "Registry state machine" } }, "onchain-erc1155": { "technologies": [ "ERC-1155 smart contracts", "NFT-backed certificates", "Decentralized minting" ], "technologyProperties": { "registryArchitecture": "Fully Digital token standard", "uniquenessGuarantee": "Cryptographic uniqueness via token ID", "doubleSpendPrevention": "Blockchain consensus" } }, "federated-registry": { "technologies": [ "Cross-chain bridge", "Interoperability protocol", "Wrapped certificates" ], "technologyProperties": { "registryArchitecture": "Multi-chain federated nodes", "uniquenessGuarantee": "Bridge-enforced single canonical version", "doubleSpendPrevention": "Cross-chain lock mechanism" } } }, "text": "Do certificates need to be tradeable internationally, or will they operate within a single country?", "ngoText": "Do certificates need to be tradeable internationally, or will they operate within a single country?" }, { "id": "rec-verification-std", "type": "select", "options": [ { "label": "Gold Standard", "value": "gold-standard" }, { "label": "Verra / VCS", "value": "verra" }, { "label": "National or regional standard", "value": "national" }, { "label": "Custom or internal methodology", "value": "custom" }, { "label": "Not yet determined", "value": "tbd" } ], "propertyMapping": { "gold-standard": { "technologies": [ "Gold Standard registry integration" ], "technologyProperties": { "verificationProtocol": "Gold Standard", "certificationLevel": "International" } }, "verra": { "technologies": [ "Verra VCS registry integration" ], "technologyProperties": { "verificationProtocol": "Verra VCS", "certificationLevel": "International" } }, "national": { "technologies": [ "National registry connection" ], "technologyProperties": { "verificationProtocol": "National standard", "certificationLevel": "National" } }, "custom": { "technologies": [ "Custom verification engine" ], "technologyProperties": { "verificationProtocol": "Custom", "certificationLevel": "Internal" } }, "tbd": { "technologies": [ "Flexible verification framework" ], "technologyProperties": { "verificationProtocol": "To be determined", "certificationLevel": "Flexible" } } }, "prefillFrom": null, "briefSection": "Monitoring and verification", "text": "What verification standards or methodologies apply to renewable energy certificates?", "ngoText": "What verification standards or methodologies apply to renewable energy certificates?" }, { "id": "rec-monitoring-freq", "type": "select", "options": [ { "label": "Real-time / continuous", "value": "realtime" }, { "label": "Daily", "value": "daily" }, { "label": "Weekly or monthly", "value": "periodic" }, { "label": "Seasonally or annually", "value": "seasonal" } ], "propertyMapping": { "realtime": { "technologies": [ "IoT sensor integration", "Real-time sensor feed" ], "technologyProperties": { "dataFrequency": "Continuous", "sensorIntegration": "Required" } }, "daily": { "technologies": [ "Automated daily capture", "Sensor or manual" ], "technologyProperties": { "dataFrequency": "Daily", "sensorIntegration": "Recommended" } }, "periodic": { "technologies": [ "Scheduled data capture" ], "technologyProperties": { "dataFrequency": "Periodic", "sensorIntegration": "Optional" } }, "seasonal": { "technologies": [ "Manual data entry acceptable" ], "technologyProperties": { "dataFrequency": "Seasonal", "sensorIntegration": "Not required" } } }, "prefillFrom": null, "briefSection": "Environmental data", "text": "How frequently does energy generation monitoring data need to be captured?", "ngoText": "How frequently does energy generation monitoring data need to be captured?" }, { "id": "iot-sensor-approach", "type": "select", "options": [ { "label": "GPS/location tracking devices", "value": "gps-location" }, { "label": "Environmental sensors (temperature, humidity, etc.)", "value": "environmental" }, { "label": "Smart meters (energy, water usage)", "value": "smart-meters" }, { "label": "Mobile phone-based data collection (photos, GPS, manual entry)", "value": "mobile-collection" } ], "propertyMapping": { "gps-location": { "technologies": [ "GPS tracking IoT devices", "IoT sensor data gateway", "Location verification oracle" ], "technologyProperties": { "sensorType": "GPS/GNSS trackers", "dataFrequency": "Configurable (real-time to daily)", "connectivity": "Cellular/satellite" } }, "environmental": { "technologies": [ "Environmental IoT sensors", "IoT sensor data gateway", "Threshold alert service" ], "technologyProperties": { "sensorType": "Temperature, humidity, air quality sensors", "dataFrequency": "Continuous with threshold alerts", "connectivity": "LoRaWAN/cellular" } }, "smart-meters": { "technologies": [ "Smart meter IoT integration", "IoT sensor data gateway", "Usage verification service" ], "technologyProperties": { "sensorType": "Smart meters (energy/water)", "dataFrequency": "Hourly/daily readings", "connectivity": "LoRaWAN/cellular/Wi-Fi" } }, "mobile-collection": { "technologies": [ "Mobile data collection app", "IoT sensor proxy layer", "Photo/GPS verification service" ], "technologyProperties": { "sensorType": "Smartphone (camera, GPS, manual entry)", "dataFrequency": "Event-driven (field visits)", "connectivity": "Offline-first with sync" } } }, "prefillFrom": null, "briefSection": "Data collection", "text": "What type of sensor or data collection devices will be used?", "ngoText": "What type of sensor or data collection devices will be used?" } ], "complexityFactors": { "relationships": 3, "operationalChange": 2, "dataCompliance": 2 }, "suggestedCriteria": [ { "id": "SC-STANDARD-COMPLIANCE", "name": "Certificate Standard Compliance", "description": "Does the provider support the applicable renewable energy certificate standards (I-REC, Guarantee of Origin, US RECs) including issuance rules, retirement protocols, and registry interoperability?", "weight": 0.25, "ratingGuide": { "5": "Full compliance with multiple international REC standards (I-REC, GO, US REC). Automated issuance and retirement aligned with standard rules. Interoperable with existing national registries.", "4": "Compliant with one major standard. Supports issuance and retirement workflows. Limited cross-registry interoperability but roadmap in place.", "3": "Partially compliant with a recognised standard. Manual steps required for issuance or retirement. No registry interoperability yet.", "2": "Custom certificate format loosely based on standards. No formal compliance validation. Requires manual reconciliation with official registries.", "1": "No alignment with any recognised REC standard. Proprietary certificate model incompatible with existing markets." } }, { "id": "SC-DOUBLE-COUNTING", "name": "Double-Counting Prevention", "description": "How reliably does the system prevent the same MWh of renewable generation from being claimed, sold, or retired more than once across registries and jurisdictions?", "weight": 0.25, "ratingGuide": { "5": "Cryptographic uniqueness per certificate with on-chain lifecycle tracking (issuance \u2192 transfer \u2192 retirement). Cross-registry deduplication. Automatic retirement upon use. Auditable chain of custody from meter to claim.", "4": "On-chain uniqueness enforcement within the platform. Retirement is final and irreversible. Cross-registry checks available but require manual initiation.", "3": "Platform-level uniqueness but no cross-registry deduplication. Retirement is recorded but reversal not technically blocked.", "2": "Database-level uniqueness only. No cryptographic binding to generation data. Cross-platform double-counting possible.", "1": "No systematic prevention. Certificates can be duplicated or claimed multiple times without detection." } }, { "id": "SC-METERING-INTEGRATION", "name": "Generation Metering Integration", "description": "Can the platform ingest real-time or periodic generation data from smart meters and IoT devices to automatically verify energy production before certificate issuance?", "weight": 0.2, "ratingGuide": { "5": "Direct API integration with major smart meter brands. Real-time data ingestion (15-min intervals). Automated certificate minting triggered by verified generation data. Anomaly detection on meter readings.", "4": "Supports IoT data feeds via standard protocols (MQTT, REST). Near-real-time ingestion. Certificate issuance requires generation data but may need manual trigger.", "3": "Accepts batch uploads of meter data (CSV, API). Daily or weekly data sync. Generation verification before issuance but no real-time feed.", "2": "Manual meter reading entry only. No automated verification against generation data. Certificate issuance decoupled from metering.", "1": "No metering integration. Certificates issued based on self-reported data with no verification." } }, { "id": "SC-TRADING-MECHANISM", "name": "Trading & Settlement Capability", "description": "Does the platform support efficient trading of certificates between parties with fair price discovery, transparent settlement, and compliance with energy market regulations?", "weight": 0.2, "ratingGuide": { "5": "Built-in marketplace with order book or auction mechanism. Atomic settlement (trade and transfer in single transaction). Price transparency and market data APIs. Compliant with energy trading regulations in target jurisdictions.", "4": "Peer-to-peer trading with escrow-based settlement. Price negotiation tools. Compliance framework for at least one jurisdiction.", "3": "Basic transfer mechanism between registered parties. Manual settlement. Limited price discovery. Regulatory compliance not yet validated.", "2": "Transfer possible but no marketplace features. Bilateral agreements handled off-platform. No settlement automation.", "1": "No trading functionality. Certificates are issued and retired but cannot be transferred between parties." } }, { "id": "SC-AUDIT-TRANSPARENCY", "name": "Audit Trail & Reporting", "description": "Does the platform provide a complete, tamper-evident audit trail from energy generation through certificate issuance, trading, and retirement that satisfies regulatory and donor reporting requirements?", "weight": 0.1, "ratingGuide": { "5": "Complete chain of custody visible on-chain. Export-ready reports for regulatory bodies (e.g. UNFCCC, national energy agencies). Automatic compliance reporting. Third-party audit access with read-only permissions.", "4": "Full audit trail with exportable reports. Covers issuance-to-retirement lifecycle. Supports common reporting formats.", "3": "Audit trail available but requires manual compilation for reports. Covers main lifecycle events but gaps in transfer history.", "2": "Basic transaction logs. No structured reporting. Significant manual effort to compile audit documentation.", "1": "No meaningful audit trail. Records are fragmented or mutable. Cannot satisfy external audit requirements." } } ], "procurement": { "marketMaturity": "mature", "primaryMode": "off-the-shelf", "alternativeModes": [ "rfq" ], "reasoning": "Renewable energy certificate tracking is mature commercial market.", "exampleProductCategories": [ "rec-tracking-platform", "energy-certificate-rails" ], "partnerChannels": [], "lastReviewed": "2026-05-01" } }, { "id": "UC-I-108", "name": "Carbon credit registry and marketplace", "category": "I", "subcategory": "Carbon Markets", "description": "Keep one trusted list of carbon credits and who owns them, so buyers can see that no credit has been sold twice.", "bCriteria": [ "B1", "B3", "B8", "B4" ], "requiredComponents": [ "carbon-marketplace", "certificate-registry", "verification-layer", "trading-mechanism" ], "conditionalComponents": [ "smart-contracts", "parametric-oracle" ], "crossCategoryDependencies": [ "UC-I-114", "UC-I-114" ], "p2TriggerConditions": { "description": "Activated when P2 shows carbon offset programmes with multiple market participants and significant trading volume", "rangeSignals": [ "carbonOffsets >=3", "marketParticipants >=3", "tradingVolume >=2" ] }, "contextFieldsTemplate": [ "carbon_project_types", "baseline_emission_level", "monitoring_frequency", "verification_standard", "trading_volume_baseline", "price_discovery_need", "regulatory_compliance_requirements" ], "implementationComplexity": "high", "examples": { "note": "Verra and Gold Standard carbon credit issuance", "references": [ { "name": "Toucan Protocol", "description": "Decentralised carbon credit tokenisation enabling on-chain trading and retirement of verified carbon credits", "url": "https://toucan.earth/" }, { "name": "Flowcarbon", "description": "Tokenises carbon credits for DeFi integration; enables instant trading and programmatic retirement", "url": "https://flowcarbon.com/" }, { "name": "Regen Network", "description": "Blockchain-based carbon credit issuance for ecological regeneration projects with on-chain MRV", "url": "https://www.regen.network/" } ] }, "propertyMapping": { "onChainCarbonCreditRetirementEngine": { "technologies": [ "Carbon credit tokenisation protocol", "Carbon credit tokenization", "On-chain retirement mechanism" ], "technologyProperties": { "creditStandard": "Verra VCS or Gold Standard", "mrvApproach": "Satellite-based with oracle validation", "marketplaceModel": "AMM-based spot trading", "retirementStandard": "ERC-1155 token burn" } } }, "solutionQuestions": [ { "id": "carbon-methodology", "type": "select", "options": [ { "label": "Verra Verified Carbon Standard (VCS)", "value": "verra-vcs" }, { "label": "Gold Standard Framework", "value": "gold-standard" }, { "label": "Plan Vivo Community Standards", "value": "plan-vivo" }, { "label": "Nature-based Solutions (NbS) Standard", "value": "nbs-standard" } ], "prefillFrom": null, "briefSection": "Reporting and audit", "propertyMapping": { "verra-vcs": { "technologies": [ "Verra protocol integration", "MRV smart contracts", "Decentralized verification" ], "technologyProperties": { "methodology": "Verra VCS", "projectTypes": "Renewable energy, energy efficiency, forestry", "verificationCycles": "24-36 months" } }, "gold-standard": { "technologies": [ "Gold Standard API integration", "SDG impact tracking", "On-chain verification" ], "technologyProperties": { "methodology": "Gold Standard", "projectTypes": "SDG-aligned sustainable development", "verificationCycles": "24 months" } }, "plan-vivo": { "technologies": [ "Plan Vivo protocol", "Community verification layer", "Participatory monitoring" ], "technologyProperties": { "methodology": "Plan Vivo", "projectTypes": "Community-based land use projects", "verificationCycles": "12-24 months" } }, "nbs-standard": { "technologies": [ "NbS oracle network", "Biodiversity data feeds", "Carbon sequestration modeling" ], "technologyProperties": { "methodology": "Nature-based Solutions", "projectTypes": "Reforestation, wetlands, agriculture", "verificationCycles": "36 months" } } }, "text": "Which carbon credit methodology framework?", "ngoText": "Which carbon credit methodology framework?", "hidden": true }, { "id": "mrv-approach", "type": "select", "options": [ { "label": "Satellite-based monitoring with automated reporting", "value": "satellite-auto" }, { "label": "On-site IoT sensors with third-party audit", "value": "iot-audit" }, { "label": "Hybrid approach combining multiple data sources", "value": "hybrid-mrv" } ], "prefillFrom": null, "briefSection": "Monitoring and verification", "propertyMapping": { "satellite-auto": { "technologies": [ "Satellite imagery oracle", "Automated analytics", "Smart contract reporting" ], "technologyProperties": { "monitoringMethod": "Satellite + GIS analysis", "reportingFrequency": "Monthly automated reports", "verificationLatency": "30-60 days" } }, "iot-audit": { "technologies": [ "IoT sensor networks", "Auditor attestation", "Data validation oracle" ], "technologyProperties": { "monitoringMethod": "Continuous IoT + periodic audit", "reportingFrequency": "Quarterly audited reports", "verificationLatency": "90 days" } }, "hybrid-mrv": { "technologies": [ "Multi-source data aggregator", "Cross-validation oracle", "Consensus mechanism" ], "technologyProperties": { "monitoringMethod": "Satellite + IoT + ground surveys + historical data", "reportingFrequency": "Semi-annual consolidated reports", "verificationLatency": "120 days" } } }, "text": "What data collection infrastructure do you currently have? (manual field surveys, automated sensors, satellite monitoring?)", "ngoText": "What data collection infrastructure do you currently have? (manual field surveys, automated sensors, satellite monitoring?)" }, { "id": "credit-pricing", "type": "select", "options": [ { "label": "Market-driven supply-demand pricing", "value": "market-driven" }, { "label": "Methodology cost baseline with risk premium", "value": "cost-plus-premium" }, { "label": "Regulatory or policy-set floor price", "value": "regulatory-floor" } ], "prefillFrom": null, "briefSection": "Oracle and data feeds", "propertyMapping": { "market-driven": { "technologies": [ "Order book exchange", "Price discovery oracle", "Market maker incentives" ], "technologyProperties": { "pricingMechanism": "Supply-demand equilibrium", "priceVolatility": "Market-dependent (dynamic)", "pricingLatency": "Real-time or periodic" } }, "cost-plus-premium": { "technologies": [ "Baseline cost oracle", "Risk assessment engine", "Premium calculator" ], "technologyProperties": { "pricingMechanism": "Floor price (cost) + methodology premium", "priceVolatility": "Bounded by cost floor and premium caps", "pricingLatency": "Recalculated per verification cycle" } }, "regulatory-floor": { "technologies": [ "Governance oracle", "Policy parameter contract", "Price enforcement" ], "technologyProperties": { "pricingMechanism": "Policy-mandated minimum price", "priceVolatility": "Minimum price enforced by governance", "pricingLatency": "Updated via governance vote" } } }, "text": "Are credits sold at prevailing market prices or do you need auction-based price discovery?", "ngoText": "Are credits sold at prevailing market prices or do you need auction-based price discovery?" }, { "id": "certificate-registry", "type": "select", "options": [ { "label": "Public registry (anyone can verify certificates)", "value": "public" }, { "label": "Permissioned registry (only authorised parties can verify)", "value": "permissioned" }, { "label": "Integration with existing standard registries (e.g. Verra, Gold Standard)", "value": "existing-standard" }, { "label": "Not sure, need guidance", "value": "guidance-needed" } ], "propertyMapping": { "public": { "technologies": [ "Public certificate registry", "Certificate verification API", "Registry explorer portal" ], "technologyProperties": { "visibility": "Public", "standard": "Custom or open standard", "tradability": "Depends on certificate type" } }, "permissioned": { "technologies": [ "Permissioned certificate registry", "Access-controlled verification API", "Registry management portal" ], "technologyProperties": { "visibility": "Permissioned", "standard": "Custom", "tradability": "Within permissioned network" } }, "existing-standard": { "technologies": [ "Standard certificate registry integration", "Cross-registry bridge", "Certificate verification API" ], "technologyProperties": { "visibility": "Per standard registry rules", "standard": "Verra/Gold Standard/etc.", "tradability": "Per standard marketplace rules" } }, "guidance-needed": { "technologies": [ "Certificate registry framework", "Certificate verification API" ], "technologyProperties": { "visibility": "To be determined", "standard": "To be determined", "tradability": "To be determined" } } }, "prefillFrom": null, "briefSection": "Certificate management", "text": "What type of certificate tracking do you need?", "ngoText": "What type of certificate tracking do you need?" }, { "id": "credit-stakeholder-access", "type": "select", "options": [ { "label": "Project developer only: internal registry management", "value": "internal" }, { "label": "Project developer + verification body", "value": "developer-verifier" }, { "label": "Multiple parties: buyers, verifiers, regulators all need access", "value": "multi-party" }, { "label": "Public registry: anyone can view credit status and retirement", "value": "public" }, { "label": "Not sure, need guidance on access model", "value": "unsure" } ], "propertyMapping": { "internal": { "technologies": [ "Private registry platform" ], "technologyProperties": { "accessModel": "Internal only", "stakeholderCount": "1", "publicVisibility": "None" } }, "developer-verifier": { "technologies": [ "Shared registry with role-based access" ], "technologyProperties": { "accessModel": "Developer + verifier", "stakeholderCount": "2", "publicVisibility": "Limited" } }, "multi-party": { "technologies": [ "Multi-party registry platform", "Role-based access control" ], "technologyProperties": { "accessModel": "Multi-stakeholder", "stakeholderCount": "3+", "publicVisibility": "Selective" } }, "public": { "technologies": [ "Public registry with transparency dashboard" ], "technologyProperties": { "accessModel": "Public", "stakeholderCount": "Open", "publicVisibility": "Full" } }, "unsure": { "technologies": [ "Access model design needed" ], "technologyProperties": { "accessModel": "TBD", "stakeholderCount": "TBD", "publicVisibility": "TBD" } } }, "prefillFrom": null, "briefSection": "Infrastructure requirements", "text": "How many parties need to view, trade, or verify credits in the registry?", "ngoText": "How many parties need to view, trade, or verify credits in the registry?" }, { "id": "credit-trading-rules", "type": "select", "options": [ { "label": "Credits are retired on use: no secondary trading", "value": "retire-only" }, { "label": "Credits can be traded once before retirement", "value": "single-trade" }, { "label": "Open secondary market: credits can be traded multiple times", "value": "open-market" }, { "label": "Bundled trading: credits packaged with other environmental assets", "value": "bundled" }, { "label": "Not sure, trading model still being determined", "value": "unsure" } ], "propertyMapping": { "retire-only": { "technologies": [ "Retirement-only registry" ], "technologyProperties": { "tradingModel": "No trading \u2014 retire on use", "marketComplexity": "Low", "secondaryMarket": "No" } }, "single-trade": { "technologies": [ "Single-transfer registry", "Ownership transfer engine" ], "technologyProperties": { "tradingModel": "Single transfer", "marketComplexity": "Low-Medium", "secondaryMarket": "Limited" } }, "open-market": { "technologies": [ "Carbon marketplace", "Order matching engine", "Settlement layer" ], "technologyProperties": { "tradingModel": "Open secondary market", "marketComplexity": "High", "secondaryMarket": "Yes" } }, "bundled": { "technologies": [ "Asset bundling engine", "Multi-asset marketplace" ], "technologyProperties": { "tradingModel": "Bundled asset trading", "marketComplexity": "High", "secondaryMarket": "Yes \u2014 multi-asset" } }, "unsure": { "technologies": [ "Trading model assessment needed" ], "technologyProperties": { "tradingModel": "TBD", "marketComplexity": "TBD", "secondaryMarket": "TBD" } } }, "prefillFrom": null, "briefSection": "Trading mechanism", "text": "Once credits are issued, can they be traded or are they retired on first use?", "ngoText": "Once credits are issued, can they be traded or are they retired on first use?" }, { "id": "credit-registry-reporting", "type": "select", "options": [ { "label": "Standard registry reports (issuance, retirement, balance)", "value": "standard" }, { "label": "Donor/funder reporting with impact metrics linked to credits", "value": "donor-impact" }, { "label": "Regulatory compliance reporting (national carbon accounting)", "value": "regulatory" }, { "label": "Full transparency: public dashboard showing all credit lifecycle events", "value": "full-transparency" }, { "label": "Not sure, need guidance on reporting requirements", "value": "unsure" } ], "propertyMapping": { "standard": { "technologies": [ "Registry reporting module" ], "technologyProperties": { "reportingDepth": "Standard", "publicDashboard": "No", "regulatoryCompliance": "Basic" } }, "donor-impact": { "technologies": [ "Impact-linked reporting", "Donor dashboard" ], "technologyProperties": { "reportingDepth": "Donor-facing with impact", "publicDashboard": "Partial", "regulatoryCompliance": "Basic" } }, "regulatory": { "technologies": [ "Regulatory reporting engine", "National carbon accounting integration" ], "technologyProperties": { "reportingDepth": "Regulatory", "publicDashboard": "No", "regulatoryCompliance": "Full" } }, "full-transparency": { "technologies": [ "Public transparency dashboard", "Full lifecycle event log" ], "technologyProperties": { "reportingDepth": "Full transparency", "publicDashboard": "Yes", "regulatoryCompliance": "Full" } }, "unsure": { "technologies": [ "Reporting assessment needed" ], "technologyProperties": { "reportingDepth": "TBD", "publicDashboard": "TBD", "regulatoryCompliance": "TBD" } } }, "prefillFrom": null, "briefSection": "Reporting and audit", "text": "What registry reporting is required for your carbon credit programme?", "ngoText": "What registry reporting is required for your carbon credit programme?" } ], "complexityFactors": { "relationships": 3, "operationalChange": 2, "dataCompliance": 2 }, "suggestedCriteria": [ { "id": "SC-METHODOLOGY-COMPLIANCE", "name": "Carbon Methodology Compliance", "description": "Does the platform align with established carbon credit methodologies (Verra VCS, Gold Standard, national standards) including additionality requirements, baseline calculations, and MRV protocols?", "weight": 0.25, "ratingGuide": { "5": "Supports multiple recognised methodologies (Verra, Gold Standard, Plan Vivo). Automated baseline calculation and additionality checks built into issuance workflow. MRV protocols embedded. Direct registry integration.", "4": "Supports at least one major methodology. Additionality and baseline tools available. MRV workflow supported but some manual steps.", "3": "Loosely aligned with one methodology. Manual additionality assessment. Basic MRV support. No direct registry integration.", "2": "Custom methodology not aligned with recognised standards. No additionality verification. MRV handled entirely off-platform.", "1": "No methodology framework. Credits issued without additionality, baseline, or MRV requirements." } }, { "id": "SC-DOUBLE-COUNTING-CARBON", "name": "Double-Counting & Retirement Integrity", "description": "How does the system prevent the same emission reduction from being counted, sold, or claimed by multiple parties, including across Article 6 corresponding adjustments?", "weight": 0.25, "ratingGuide": { "5": "Cryptographic uniqueness per credit. Permanent on-chain retirement (irreversible burn). Cross-registry deduplication including Verra/Gold Standard bridge checks. Article 6 corresponding adjustment tracking built in.", "4": "On-chain uniqueness and permanent retirement. Cross-registry checks for one major standard. Corresponding adjustment awareness but not automated.", "3": "Platform-level uniqueness. Retirement recorded on-chain but no cross-registry verification. No corresponding adjustment tracking.", "2": "Database-level uniqueness only. Credits can exist in multiple systems. Retirement is reversible.", "1": "No deduplication mechanism. Same emission reduction can generate multiple credits without detection." } }, { "id": "SC-MRV-INTEGRATION", "name": "MRV Data Integration", "description": "Can the platform integrate monitoring, reporting, and verification data from field sensors, satellite imagery, and manual surveys to support credit issuance with verified impact data?", "weight": 0.2, "ratingGuide": { "5": "Multi-source MRV ingestion: satellite imagery, IoT sensors, field survey apps. Automated anomaly detection. Data integrity verification before credit issuance. Supports dMRV (digital MRV) standards.", "4": "Supports at least two MRV data sources (e.g. sensors + manual). Automated verification for primary source. Data integrity checks on ingestion.", "3": "Single MRV data source supported (typically manual). Basic verification. No satellite or automated sensor integration.", "2": "MRV data entered manually with no verification. No integration with monitoring infrastructure.", "1": "No MRV integration. Credits issued without supporting impact data." } }, { "id": "SC-MARKET-ACCESS", "name": "Market Access & Liquidity", "description": "Does the platform provide access to carbon credit buyers, trading infrastructure, and price discovery mechanisms that enable projects to monetise their credits effectively?", "weight": 0.2, "ratingGuide": { "5": "Active marketplace with established buyer network. Multiple trading mechanisms (spot, forward, auction). Real-time price data. Integration with voluntary and compliance markets.", "4": "Marketplace with growing buyer base. At least two trading mechanisms. Price benchmarking available.", "3": "Basic listing and matching service. Limited buyer network. Single trading mechanism. No real-time pricing.", "2": "Directory-only \u2014 connects sellers and buyers but no trading infrastructure. Off-platform transactions.", "1": "No marketplace or buyer access. Credits issued but no monetisation pathway." } }, { "id": "SC-PROJECT-TRANSPARENCY", "name": "Project Transparency & Traceability", "description": "Can credit buyers trace each credit back to a specific project with verified location, methodology, vintage, and impact data, building buyer confidence and preventing greenwashing?", "weight": 0.1, "ratingGuide": { "5": "Full project-to-credit traceability on-chain. Project location, methodology, vintage, co-benefits, and verification reports publicly accessible. Real-time project monitoring dashboards. Third-party verification status visible.", "4": "Credit-to-project linking with key metadata visible. Verification reports accessible on request. Project data updated periodically.", "3": "Basic project information linked to credits. Limited metadata. Verification status available but reports not on-platform.", "2": "Credits linked to project name only. No detailed metadata or verification data accessible to buyers.", "1": "No project traceability. Credits are fungible with no link to specific emission reduction activities." } } ], "procurement": { "marketMaturity": "emerging", "primaryMode": "tender", "alternativeModes": [ "integrator-led" ], "reasoning": "Carbon credit registries growing rapidly with multiple commercial offerings.", "exampleProductCategories": [ "carbon-credit-platform", "carbon-marketplace-rails" ], "partnerChannels": [], "lastReviewed": "2026-05-01" } }, { "id": "UC-I-109", "name": "Green energy provenance for climate finance", "category": "I", "subcategory": "Climate Finance", "description": "Show that a green energy project needed the funding and has not been paid for twice, without revealing sensitive project details.", "bCriteria": [ "B1", "B3", "B6" ], "requiredComponents": [ "certificate-registry", "verification-layer", "audit-trail", "monitoring-platform" ], "conditionalComponents": [ "smart-contracts", "parametric-oracle" ], "crossCategoryDependencies": [ "UC-G-098", "UC-I-114" ], "p2TriggerConditions": { "description": "Activated when P2 shows green energy projects seeking climate finance eligibility with additionality proof requirements", "rangeSignals": [ "greenEnergyProjects >=3", "climateFinanceEligibility >=3", "additionalityProof >=2" ] }, "contextFieldsTemplate": [ "project_technology_type", "installed_capacity", "baseline_energy_scenario", "monitoring_data_sources", "financer_requirements", "climate_finance_instrument", "verification_standard" ], "implementationComplexity": "high", "examples": { "note": "Green Climate Fund documentation requirements", "references": [ { "name": "Energy Web Foundation", "description": "Decentralised energy system providing real-time renewable energy tracking for climate finance applications", "url": "https://www.energyweb.org/" }, { "name": "Regen Network", "description": "Blockchain-based platform for ecological regeneration with climate finance eligibility verification", "url": "https://www.regen.network/" }, { "name": "Celo Regenerative Finance", "description": "Climate-focused blockchain supporting green energy projects and climate finance instruments", "url": "https://celo.org/" } ] }, "propertyMapping": { "greenEnergyProvenanceOracleNetwork": { "technologies": [ "Energy-sector data oracles", "Climate finance compliance oracle", "Additionality verification engine" ], "technologyProperties": { "energyType": "Renewable (solar, wind, hydro)", "provenanceMethod": "Real-time or batch attestation", "financeStandard": "GCF or Green Bond eligible", "verificationMethod": "Decentralized oracle consensus" } } }, "solutionQuestions": [ { "id": "energy-type", "type": "select", "options": [ { "label": "Solar photovoltaic generation", "value": "solar-pv" }, { "label": "Wind power generation", "value": "wind" }, { "label": "Hydroelectric generation", "value": "hydro" }, { "label": "Mixed renewable portfolio", "value": "mixed-renewable" } ], "prefillFrom": null, "briefSection": "Environmental data", "propertyMapping": { "solar-pv": { "technologies": [ "Solar irradiance sensor oracle", "Inverter data feeds", "Performance monitoring" ], "technologyProperties": { "energyType": "Solar PV", "generationProfile": "Intermittent (weather-dependent)", "financeEligibility": "IRENA-certified renewable" } }, "wind": { "technologies": [ "SCADA wind monitoring", "Wind speed oracle", "Availability tracking" ], "technologyProperties": { "energyType": "Wind power", "generationProfile": "Variable (weather-dependent)", "financeEligibility": "IRENA-certified renewable" } }, "hydro": { "technologies": [ "Hydro flow meter oracle", "Water discharge data", "Seasonal monitoring" ], "technologyProperties": { "energyType": "Hydroelectric", "generationProfile": "Semi-predictable (seasonal)", "financeEligibility": "Conditional on environmental compliance" } }, "mixed-renewable": { "technologies": [ "Multi-source aggregator", "Portfolio data oracle", "Blended tracking" ], "technologyProperties": { "energyType": "Mixed renewable sources", "generationProfile": "Aggregated smoothing across sources", "financeEligibility": "Based on component project eligibility" } } }, "text": "What renewable energy types are tracked?", "ngoText": "What renewable energy types are tracked?" }, { "id": "provenance-chain", "type": "select", "options": [ { "label": "Real-time meter-to-market provenance with atomic settlement", "value": "realtime-provenance" }, { "label": "Batch provenance bundles with periodic attestation", "value": "batch-provenance" }, { "label": "Additionality verification with counterfactual modeling", "value": "additionality-verification" } ], "prefillFrom": null, "briefSection": "Provenance chain", "propertyMapping": { "realtime-provenance": { "technologies": [ "IoT smart meters", "Energy transmission oracle", "Atomic settlement contract" ], "technologyProperties": { "provenanceTracking": "Generation timestamp to consumer ID", "granularity": "Per-transaction or per-block level", "settlement": "T+0 atomic swap with energy delivery" } }, "batch-provenance": { "technologies": [ "Aggregator platform", "Monthly attestation", "Bundle smart contracts" ], "technologyProperties": { "provenanceTracking": "Generation month to consumer cohort", "granularity": "Monthly bundle tracking", "settlement": "Monthly batch settlement" } }, "additionality-verification": { "technologies": [ "Counterfactual modeling oracle", "Baseline comparison", "Additionality oracle" ], "technologyProperties": { "provenanceTracking": "Generation provenance + additionality proof", "granularity": "Project-level impact assessment", "settlement": "Settlement contingent on additionality confirmation" } } }, "text": "How many distinct steps/handoff points in your energy supply chain from generation to end-beneficiary?", "ngoText": "How many distinct steps/handoff points in your energy supply chain from generation to end-beneficiary?" }, { "id": "financer-requirements", "type": "select", "options": [ { "label": "Green Bond eligibility per ICMA guidelines", "value": "green-bond-icma" }, { "label": "GCF (Green Climate Fund) eligibility criteria", "value": "gcf-eligible" }, { "label": "Paris Agreement Article 6 mechanism compliance", "value": "paris-article6" }, { "label": "Voluntary carbon market (VCM) eligibility", "value": "vcm-standard" } ], "prefillFrom": null, "briefSection": "Oracle and data feeds", "propertyMapping": { "green-bond-icma": { "technologies": [ "Green Bond oracle", "ICMA compliance checker", "Second opinion integration" ], "technologyProperties": { "framework": "ICMA Green Bond Principles", "eligibleProjectTypes": "Renewable energy, energy efficiency, clean transport", "verificationFrequency": "Annual independent verification" } }, "gcf-eligible": { "technologies": [ "GCF accreditation oracle", "Impact measurement engine", "Co-benefit tracking" ], "technologyProperties": { "framework": "GCF Accreditation Standards", "eligibleProjectTypes": "Climate mitigation + adaptation projects", "verificationFrequency": "Project baseline + mid-term + final evaluation" } }, "paris-article6": { "technologies": [ "Article 6 oracle", "ITMO tracking", "International registry link" ], "technologyProperties": { "framework": "Paris Agreement Article 6 (Nationally Determined Contributions)", "eligibleProjectTypes": "Emissions reduction projects within national programs", "verificationFrequency": "In-country verification + international audit" } }, "vcm-standard": { "technologies": [ "VCM standard oracle", "Third-party validator", "Certification registry" ], "technologyProperties": { "framework": "Verra, Gold Standard, or Plan Vivo", "eligibleProjectTypes": "Community-based and project-based climate mitigation", "verificationFrequency": "Baseline + periodic audits + retirement verification" } } }, "text": "What climate finance eligibility criteria must be met?", "ngoText": "What climate finance eligibility criteria must be met?" }, { "id": "verification-standard", "type": "select", "options": [ { "label": "Third-party independent auditor verification", "value": "third-party-audit" }, { "label": "distributed oracle consensus verification", "value": "oracle-consensus" }, { "label": "Automated satellite imagery and data validation", "value": "satellite-validation" } ], "prefillFrom": null, "briefSection": "Reporting and audit", "propertyMapping": { "third-party-audit": { "technologies": [ "Auditor attestation", "Automated verification", "Reputation oracle" ], "technologyProperties": { "verificationMethod": "Annual or periodic independent audit", "auditorQualifications": "Accredited by GCF or equivalent", "verificationLatency": "60-90 days" } }, "oracle-consensus": { "technologies": [ "Multiple oracle feeds", "Consensus mechanism", "Slashing for bad data" ], "technologyProperties": { "verificationMethod": "Distributed oracle consensus", "auditorQualifications": "Registered oracle node operators", "verificationLatency": "15-30 days" } }, "satellite-validation": { "technologies": [ "Satellite imagery oracle", "ML-based validation", "Anomaly detection" ], "technologyProperties": { "verificationMethod": "Continuous satellite monitoring + ML validation", "auditorQualifications": "Geospatial data scientists", "verificationLatency": "7-14 days" } } }, "text": "What verification standard is applied?", "ngoText": "What verification standard is applied?" }, { "id": "green-energy-monitoring-freq", "type": "select", "options": [ { "label": "Real-time / continuous", "value": "realtime" }, { "label": "Daily", "value": "daily" }, { "label": "Weekly or monthly", "value": "periodic" }, { "label": "Seasonally or annually", "value": "seasonal" } ], "propertyMapping": { "realtime": { "technologies": [ "IoT sensor integration", "Real-time sensor feed" ], "technologyProperties": { "dataFrequency": "Continuous", "sensorIntegration": "Required" } }, "daily": { "technologies": [ "Automated daily capture", "Sensor or manual" ], "technologyProperties": { "dataFrequency": "Daily", "sensorIntegration": "Recommended" } }, "periodic": { "technologies": [ "Scheduled data capture" ], "technologyProperties": { "dataFrequency": "Periodic", "sensorIntegration": "Optional" } }, "seasonal": { "technologies": [ "Manual data entry acceptable" ], "technologyProperties": { "dataFrequency": "Seasonal", "sensorIntegration": "Not required" } } }, "prefillFrom": null, "briefSection": "Environmental data", "text": "How frequently does energy provenance monitoring data need to be captured?", "ngoText": "How frequently does energy provenance monitoring data need to be captured?" } ], "complexityFactors": { "relationships": 3, "operationalChange": 2, "dataCompliance": 2 }, "suggestedCriteria": [ { "id": "SC-ADDITIONALITY-PROOF", "name": "Additionality & Provenance Verification", "description": "Can the platform prove that green energy generation is additional (would not have occurred without the intervention) and trace energy provenance from generation source to end-use claim?", "weight": 0.3, "ratingGuide": { "5": "Automated additionality assessment using baseline data and counterfactual analysis. End-to-end provenance from generation meter to climate finance claim. Cryptographic proof linking specific generation to specific claim.", "4": "Additionality framework with supporting documentation workflow. Provenance tracking covers generation to certificate. Some manual steps in claim linkage.", "3": "Basic additionality documentation supported. Provenance covers generation and issuance but gaps in downstream tracking.", "2": "Additionality assessed off-platform. Limited provenance \u2014 certificates not linked to specific generation data.", "1": "No additionality assessment. No provenance tracking. Green claims unsupported by verifiable data." } }, { "id": "SC-CLIMATE-FINANCE-ALIGNMENT", "name": "Climate Finance Eligibility Alignment", "description": "Does the platform produce documentation and data outputs aligned with climate finance requirements (Green Climate Fund, climate bonds, Article 6 mechanisms)?", "weight": 0.25, "ratingGuide": { "5": "Pre-built templates for GCF, GEF, climate bond certification. Automated generation of eligibility documentation. Corresponding adjustment tracking for Article 6. Accepted by at least one major climate finance institution.", "4": "Supports documentation for one major climate finance framework. Semi-automated report generation. Article 6 awareness.", "3": "Outputs can be adapted for climate finance applications with manual effort. No pre-built templates. Basic reporting.", "2": "Data available but not formatted for climate finance. Significant manual effort to compile eligibility documentation.", "1": "No alignment with climate finance requirements. Platform outputs not suitable for institutional applications." } }, { "id": "SC-MONITORING-INTEGRITY", "name": "Continuous Monitoring & Data Integrity", "description": "Does the platform ensure ongoing monitoring of green energy projects with tamper-evident data capture that maintains integrity over multi-year climate finance commitment periods?", "weight": 0.2, "ratingGuide": { "5": "Real-time monitoring with IoT and satellite integration. Tamper-evident data chain from sensor to ledger. Automated deviation alerts. Data integrity maintained over 10+ year commitment periods.", "4": "Regular monitoring (daily/weekly) with automated data capture. On-chain data integrity. Alert system for anomalies. Multi-year data retention.", "3": "Periodic monitoring (monthly) with some automated capture. Basic data integrity checks. Manual anomaly review.", "2": "Quarterly or annual monitoring only. Manual data entry. No tamper-evidence. Limited historical data retention.", "1": "No ongoing monitoring. Single-point verification at project registration only." } }, { "id": "SC-MULTI-STAKEHOLDER", "name": "Multi-Stakeholder Access & Governance", "description": "Can the platform serve multiple stakeholders (project developers, financiers, verifiers, regulators) with appropriate access levels and governance structures for climate finance oversight?", "weight": 0.15, "ratingGuide": { "5": "Role-based access for all stakeholder types. Verifier workflow with independent sign-off. Financier dashboards with portfolio-level reporting. Regulator read-only audit access. Governance rules enforced on-chain.", "4": "Multiple roles supported. Verifier and financier access available. Basic governance controls.", "3": "Two or three role types. Limited verifier workflow. Financier reporting requires manual extraction.", "2": "Single admin role with shared access. No role-based permissions. Governance handled off-platform.", "1": "Single-user platform. No multi-stakeholder support." } }, { "id": "SC-INTEROPERABILITY", "name": "Registry & Standard Interoperability", "description": "Can the platform exchange data with existing energy registries, carbon registries, and climate finance platforms to avoid creating isolated data silos?", "weight": 0.1, "ratingGuide": { "5": "Bidirectional API integration with major registries (I-REC, Verra, Gold Standard). Cross-platform data exchange standards. Interoperable with climate finance reporting systems (UNFCCC, GCF).", "4": "API integration with at least one major registry. Data export in standard formats. Basic interoperability with reporting systems.", "3": "Data export available but no live registry integration. Standard data formats for manual import/export.", "2": "Proprietary data format. CSV export only. Manual reconciliation required with external systems.", "1": "Closed system. No data export or integration capability." } } ], "procurement": { "marketMaturity": "emerging", "primaryMode": "tender", "alternativeModes": [ "integrator-led" ], "reasoning": "Green energy provenance is growing area for climate finance.", "exampleProductCategories": [ "energy-provenance-platform", "climate-finance-rails" ], "partnerChannels": [], "lastReviewed": "2026-05-01" } }, { "id": "UC-I-110", "name": "Environmental monitoring data integrity", "category": "I", "subcategory": "Environmental Data", "description": "Make sure environmental readings from many sensors cannot be changed after the fact, and spot gaps that suggest a fault or tampering.", "bCriteria": [ "B1", "B3" ], "requiredComponents": [ "data-integrity-layer", "iot-sensors", "monitoring-platform", "timestamping-service" ], "conditionalComponents": [ "parametric-oracle" ], "crossCategoryDependencies": [ "UC-G-098", "UC-H-106" ], "p2TriggerConditions": { "description": "Activated when P2 shows distributed environmental monitoring with data quality concerns and multiple data sources", "rangeSignals": [ "distributedMonitoring >=3", "dataQuality >=3", "multipleDataSources >=3" ] }, "contextFieldsTemplate": [ "number_of_monitoring_points", "sensor_types", "data_update_frequency", "geographic_coverage", "data_accuracy_requirement", "real_time_vs_periodic", "data_sharing_scope" ], "implementationComplexity": "high", "examples": { "note": "IoT sensor networks with blockchain verification", "references": [ { "name": "Regen Network", "description": "Blockchain platform for verifying environmental monitoring data integrity with IoT sensor integration", "url": "https://www.regen.network/" }, { "name": "OriginStamp / Timestamp Authority", "description": "Cryptographic timestamping and data integrity verification on blockchain", "url": "https://www.originstamp.org/" }, { "name": "IOTICS (Digital Twins)", "description": "IoT data integrity and secure sharing across environmental monitoring networks", "url": "https://www.iotics.io/" } ] }, "propertyMapping": { "environmentalDataIntegrityOracle": { "technologies": [ "IoT sensor network", "Multi-sensor consensus", "Cryptographic attestation" ], "technologyProperties": { "sensorCoverage": "Multi-modal environmental monitoring", "dataFrequency": "Real-time to daily aggregation", "integrityVerification": "Cryptographic signatures + consensus", "alerting": "Automated threshold-based or governance-escalated" } } }, "solutionQuestions": [ { "id": "sensor-types", "type": "select", "options": [ { "label": "Air quality sensors (particulates, gas)", "value": "air-quality" }, { "label": "Water quality sensors (pH, turbidity, dissolved oxygen)", "value": "water-quality" }, { "label": "Soil and biological sensors (moisture, temperature, nutrient)", "value": "soil-biomonitor" }, { "label": "Multi-modal sensor network (mixed environmental)", "value": "multimodal-sensors" } ], "prefillFrom": null, "briefSection": "Environmental data", "propertyMapping": { "air-quality": { "technologies": [ "PM2.5/PM10 sensors", "Gas sensors (NO2, CO)", "IoT sensor nodes" ], "technologyProperties": { "sensorType": "Air quality monitoring", "dataAccuracy": "\u00b110-15% typical", "costPerNode": "$500-2000" } }, "water-quality": { "technologies": [ "Multi-parameter water sensor", "Submersible sensors", "Data logger" ], "technologyProperties": { "sensorType": "Water quality monitoring", "dataAccuracy": "\u00b15% typical", "costPerNode": "$1000-5000" } }, "soil-biomonitor": { "technologies": [ "Soil moisture sensors", "Soil temperature probes", "Nutrient sensors" ], "technologyProperties": { "sensorType": "Soil and agronomic monitoring", "dataAccuracy": "\u00b13-8%", "costPerNode": "$200-1000" } }, "multimodal-sensors": { "technologies": [ "Heterogeneous sensor array", "Gateway aggregator", "Cross-sensor validation" ], "technologyProperties": { "sensorType": "Integrated environmental monitoring", "dataAccuracy": "\u00b15-10% after validation", "costPerNode": "$2000-5000" } } }, "text": "What environmental sensor types provide data?", "ngoText": "What environmental sensor types provide data?" }, { "id": "data-frequency", "type": "select", "options": [ { "label": "Real-time streaming (< 5 minute intervals)", "value": "realtime-stream" }, { "label": "Hourly aggregated readings", "value": "hourly-aggregate" }, { "label": "Daily batch reporting with secure digital proofs", "value": "daily-batch" } ], "prefillFrom": null, "briefSection": "Monitoring and verification", "propertyMapping": { "realtime-stream": { "technologies": [ "Continuous data transmission", "MQTT or similar protocol", "Real-time blockchain feed" ], "technologyProperties": { "reportingInterval": "< 5 minutes", "dataLatency": "< 1 minute to blockchain", "infrastructure": "High-bandwidth continuous connection" } }, "hourly-aggregate": { "technologies": [ "Hourly data aggregation", "Summary statistics calculation", "Periodic submission" ], "technologyProperties": { "reportingInterval": "1 hour", "dataLatency": "1-6 hours to blockchain", "infrastructure": "Standard IoT with periodic sync" } }, "daily-batch": { "technologies": [ "Daily aggregation", "Merkle root commitment", "Batch smart contract submission" ], "technologyProperties": { "reportingInterval": "24 hours", "dataLatency": "1-2 days to blockchain", "infrastructure": "Energy-efficient batch processing" } } }, "text": "What data reporting frequency is required?", "ngoText": "What data reporting frequency is required?" }, { "id": "integrity-verification", "type": "select", "options": [ { "label": "Secure digital signatures with key rotation", "value": "crypto-signatures" }, { "label": "Multi-sensor consensus with outlier detection", "value": "multiSensor-consensus" }, { "label": "Hardware attestation with TPM/Secure Enclave", "value": "hardware-attestation" }, { "label": "Zero-knowledge proofs of data correctness", "value": "zk-proofs" } ], "prefillFrom": null, "briefSection": "Monitoring and verification", "propertyMapping": { "crypto-signatures": { "technologies": [ "ECDSA or EdDSA signatures", "Hardware security module", "Key rotation oracle" ], "technologyProperties": { "verificationMethod": "Public key cryptography", "signatureStandard": "FIPS 186-4 compliant", "keyRotation": "Quarterly or on-demand" } }, "multiSensor-consensus": { "technologies": [ "Multi-sensor data feeds", "Statistical consensus algorithm", "Anomaly detection engine" ], "technologyProperties": { "verificationMethod": "Consensus across redundant sensors", "toleranceThreshold": "\u00b15-10% variance acceptable", "automationLevel": "Fully automated flag and alert" } }, "hardware-attestation": { "technologies": [ "Trusted Platform Module (TPM)", "Secure Enclave", "Remote attestation oracle" ], "technologyProperties": { "verificationMethod": "Hardware-backed cryptographic attestation", "trustAnchor": "Device manufacturer certificate", "integrityLevel": "Tamper-evident verification" } }, "zk-proofs": { "technologies": [ "zk-SNARK or zk-STARK", "Proof generation oracle", "Verification smart contract" ], "technologyProperties": { "verificationMethod": "Mathematical proof of data validity", "privacyLevel": "Data withheld, only validity proof disclosed", "computationalCost": "Moderate (proof generation time)" } } }, "text": "What is your acceptable error margin for environmental measurements? (e.g., +/- 2%, or max 5% data loss per month?)", "ngoText": "What is your acceptable error margin for environmental measurements? (e.g., +/- 2%, or max 5% data loss per month?)" }, { "id": "data-sharing", "type": "select", "options": [ { "label": "Public digital register with anonymized data", "value": "public-anon" }, { "label": "Private network with role-based access controls", "value": "private-rbac" }, { "label": "Separate data store with digitally verified summaries", "value": "ofchain-lake" } ], "prefillFrom": null, "briefSection": "Environmental data", "propertyMapping": { "public-anon": { "technologies": [ "Public blockchain", "Data anonymization", "Differential privacy" ], "technologyProperties": { "sharingModel": "Publicly auditable, privately anonymous", "accessControl": "Anonymous with cryptographic proof of observation", "dataRetention": "Permanent immutable record" } }, "private-rbac": { "technologies": [ "Permissioned blockchain", "Access control list (ACL)", "Role-based permissions" ], "technologyProperties": { "sharingModel": "Access by authorized stakeholders only", "accessControl": "RBAC with cryptographic enforcement", "dataRetention": "Retention per stakeholder agreement" } }, "ofchain-lake": { "technologies": [ "Encrypted data lake (cloud object storage or decentralised storage)", "Merkle root commitment", "Key distribution oracle" ], "technologyProperties": { "sharingModel": "Data stored off-chain, integrity proven Digital", "accessControl": "Key-based access to encrypted data", "dataRetention": "Long-term archival with tiered access" } } }, "text": "Who receives your environmental data and what sensitivity constraints apply?", "ngoText": "Who receives your environmental data and what sensitivity constraints apply?" }, { "id": "alert-mechanisms", "type": "select", "options": [ { "label": "Automated threshold alerts with automated rules execution", "value": "threshold-alerts" }, { "label": "Multi-step manual approval with governance timelock", "value": "governance-approval" }, { "label": "Hybrid automated + escalation to data steward", "value": "hybrid-alert" } ], "prefillFrom": null, "briefSection": "Reporting and audit", "propertyMapping": { "threshold-alerts": { "technologies": [ "Threshold smart contracts", "Event log triggering", "Automated response executor" ], "technologyProperties": { "alertType": "Automated threshold breach", "responseTime": "< 1 minute", "escalationPath": "Automatic to Digital governance" } }, "governance-approval": { "technologies": [ "Governance proposal", "Multisig verification", "Timelock delay contract" ], "technologyProperties": { "alertType": "Alert requiring governance approval", "responseTime": "24-72 hours for governance review", "escalationPath": "Manual governance vote with timelock enforcement" } }, "hybrid-alert": { "technologies": [ "Alert service", "Human-in-loop approval", "Steward notification oracle" ], "technologyProperties": { "alertType": "Automated flag to data steward for review", "responseTime": "1-6 hours for steward response", "escalationPath": "Steward approval triggers automated response" } } }, "text": "What triggers alerts in your monitoring system?", "ngoText": "What triggers alerts in your monitoring system?" } ], "complexityFactors": { "relationships": 3, "operationalChange": 2, "dataCompliance": 2 }, "suggestedCriteria": [ { "id": "SC-DATA-TAMPER-EVIDENCE", "name": "Data Tamper-Evidence & Immutability", "description": "Does the platform provide cryptographic proof that environmental monitoring data has not been altered after collection, ensuring readings are trustworthy for regulatory and scientific use?", "weight": 0.3, "ratingGuide": { "5": "Cryptographic hashing at point of capture (sensor-level). On-chain timestamping within minutes of collection. Merkle tree verification for batch data. Tamper detection alerts. Data provenance chain from sensor to report.", "4": "Hashing at data gateway level. On-chain anchoring within hours. Batch verification available. Tamper detection for major alterations.", "3": "Server-side hashing after data ingestion. Daily on-chain anchoring. Basic integrity checks but no real-time tamper detection.", "2": "Database-level checksums only. No cryptographic proofs. Anchoring infrequent or manual.", "1": "No data integrity measures. Readings stored in mutable database with no verification." } }, { "id": "SC-SENSOR-INTEGRATION", "name": "IoT Sensor Network Integration", "description": "Can the platform integrate with diverse environmental sensor types (air quality, water quality, soil, weather, noise) across distributed field locations with varying connectivity?", "weight": 0.25, "ratingGuide": { "5": "Supports 5+ sensor types via standard IoT protocols (MQTT, LoRaWAN, NB-IoT). Auto-discovery and onboarding of new sensors. Handles intermittent connectivity with local buffering and sync. Edge computing for pre-processing.", "4": "Supports 3-4 sensor types. Standard protocol support. Offline buffering for connectivity gaps. Manual sensor onboarding.", "3": "Supports 1-2 sensor types. REST API integration. Basic offline handling. Each sensor type requires custom configuration.", "2": "Single sensor type supported. Requires constant connectivity. No standard protocol support.", "1": "No direct sensor integration. Manual data entry only." } }, { "id": "SC-DATA-QUALITY", "name": "Data Quality & Anomaly Detection", "description": "Does the platform validate incoming sensor data for quality, detect anomalies or sensor malfunctions, and flag questionable readings before they are committed to the permanent record?", "weight": 0.2, "ratingGuide": { "5": "Automated range validation, outlier detection, and cross-sensor correlation. ML-based anomaly detection. Flagging workflow with human review before commitment. Sensor health monitoring and calibration alerts.", "4": "Rule-based validation and outlier detection. Flagging for out-of-range readings. Sensor health alerts. Manual review workflow.", "3": "Basic range checks on ingestion. Manual outlier review. No cross-sensor correlation. Limited sensor health monitoring.", "2": "Minimal validation \u2014 accepts most readings without checks. No anomaly detection.", "1": "No data quality controls. All readings accepted and committed without validation." } }, { "id": "SC-REGULATORY-REPORTING", "name": "Regulatory & Scientific Reporting", "description": "Can the platform generate reports that meet environmental regulatory requirements and scientific data standards, with proper metadata, uncertainty quantification, and chain of custody?", "weight": 0.15, "ratingGuide": { "5": "Pre-built templates for major environmental regulations. Scientific metadata standards (ISO 19115, SensorML). Uncertainty quantification. Chain of custody documentation. Automatic submission to regulatory portals.", "4": "Report templates for at least one regulatory framework. Standard metadata. Basic uncertainty reporting. Manual submission.", "3": "Generic report generation. Some metadata support. No uncertainty quantification. Manual formatting for regulatory submission.", "2": "Data export only \u2014 no report generation. User must build reports externally.", "1": "No reporting capability. Data must be manually extracted and formatted." } }, { "id": "SC-LONG-TERM-PERSISTENCE", "name": "Long-Term Data Persistence & Access", "description": "Can environmental monitoring data be reliably stored and accessed over multi-decade timescales required for climate science, regulatory compliance, and longitudinal environmental studies?", "weight": 0.1, "ratingGuide": { "5": "Decentralised storage with redundancy guarantees. Data accessible for 20+ years with format migration strategy. Decentralised permanent-storage networks for archival. Open data formats ensuring future readability.", "4": "10+ year retention with redundant storage. Defined data format and migration plan. Cloud + blockchain anchoring.", "3": "5-10 year retention. Cloud storage with backups. No formal format migration plan. On-chain hashes provide verification but not full data retrieval.", "2": "1-5 year retention. Single storage provider. No long-term access guarantees.", "1": "No long-term persistence strategy. Data at risk of loss if provider discontinues service." } } ], "procurement": { "marketMaturity": "emerging", "primaryMode": "integrator-led", "alternativeModes": [ "rfq" ], "reasoning": "Environmental monitoring data integrity platforms emerging.", "exampleProductCategories": [ "environmental-monitoring-platform", "data-integrity-saas" ], "partnerChannels": [], "lastReviewed": "2026-05-01" } }, { "id": "UC-I-111", "name": "Circular economy and waste tracking", "category": "I", "subcategory": "Waste Management", "description": "Follow waste from collection through recycling to reuse, so each party can check the quantities and types reported at every stage.", "bCriteria": [ "B1", "B3", "B4" ], "requiredComponents": [ "registry-platform", "audit-trail", "usage-tracking", "iot-sensors" ], "conditionalComponents": [ "smart-contracts" ], "crossCategoryDependencies": [], "p2TriggerConditions": { "description": "Activated when P2 shows supply chain visibility needs with circular economy goals and waste tracking requirements", "rangeSignals": [ "supplyChainVisibility >=3", "circularEconomyGoals >=2", "wasteTracking >=2" ] }, "contextFieldsTemplate": [ "waste_stream_types", "participating_entities", "collection_touchpoints", "geographic_scope", "material_flow_visibility_requirement", "reuse_recovery_targets" ], "implementationComplexity": "medium", "examples": { "note": "Ellen MacArthur Foundation circular economy initiatives", "references": [ { "name": "Circularise", "description": "Blockchain-based circular economy platform tracking plastic waste through supply chains", "url": "https://www.circularise.com/" }, { "name": "WasteChain", "description": "Waste management and circular economy tracking on blockchain with material traceability", "url": "https://www.wastechain.io/" }, { "name": "Regen Network", "description": "Broader circular and regenerative economy tracking platform with material flow verification", "url": "https://www.regen.network/" } ] }, "propertyMapping": { "circularEconomyTrackingRegistry": { "technologies": [ "Waste tracking ledger", "Material flow oracle", "Circular economy smart contracts" ], "technologyProperties": { "wasteTypes": "Multi-stream (plastic, organic, e-waste, construction)", "trackingLevel": "Batch-level with aggregate reporting", "circularMechanism": "Feedback loops to producers or material banking", "complianceModel": "Producer EPR with token incentives" } } }, "solutionQuestions": [ { "id": "waste-streams", "type": "select", "options": [ { "label": "Plastic and packaging waste", "value": "plastic-packaging" }, { "label": "Organic and biodegradable waste", "value": "organic-biodegradable" }, { "label": "Electronic waste (e-waste)", "value": "electronic-waste" }, { "label": "Construction and demolition waste", "value": "construction-demolition" }, { "label": "Mixed waste streams with composition analysis", "value": "mixed-composition" } ], "prefillFrom": null, "briefSection": "Environmental data", "propertyMapping": { "plastic-packaging": { "technologies": [ "Waste composition scanner", "Plastic type classifier", "Collection tracking" ], "technologyProperties": { "wasteCategory": "Plastic and packaging", "recyclability": "Recyclable through industrial process", "marketValue": "Moderate (varies by type)" } }, "organic-biodegradable": { "technologies": [ "Biodegradable waste sensor", "Compost tracking", "Decomposition monitoring" ], "technologyProperties": { "wasteCategory": "Organic and food waste", "recyclability": "Compostable/anaerobic digestion", "marketValue": "Low direct value (compost or biogas)" } }, "electronic-waste": { "technologies": [ "e-waste serial tracking", "Component extraction oracle", "Recovery verification" ], "technologyProperties": { "wasteCategory": "Electronic and hazardous", "recyclability": "Partial (precious metals, rare earths)", "marketValue": "High (precious materials)" } }, "construction-demolition": { "technologies": [ "Building waste tracking", "Material composition analysis", "Salvage registry" ], "technologyProperties": { "wasteCategory": "Construction and demolition", "recyclability": "High (concrete, steel, wood)", "marketValue": "Moderate (material-dependent)" } }, "mixed-composition": { "technologies": [ "Waste composition AI scanner", "Multi-stream separation oracle", "Aggregate tracking" ], "technologyProperties": { "wasteCategory": "Mixed waste with composition breakdown", "recyclability": "Variable by component", "marketValue": "Mixed-value aggregation" } } }, "text": "What waste streams are tracked?", "ngoText": "What waste streams are tracked?" }, { "id": "tracking-granularity", "type": "select", "options": [ { "label": "Individual item tracking with unique identifiers", "value": "item-level" }, { "label": "Batch tracking with bulk weight certificates", "value": "batch-weight" }, { "label": "Facility-level aggregate tracking", "value": "facility-aggregate" } ], "prefillFrom": null, "briefSection": "Monitoring and verification", "propertyMapping": { "item-level": { "technologies": [ "QR code or RFID tagging", "Item-level ledger", "Supply chain oracle" ], "technologyProperties": { "granularity": "Per-item tracking (1000+ items)", "identificationMethod": "QR codes, RFID, NFC tags", "trackingLifecycle": "Cradle-to-grave per item" } }, "batch-weight": { "technologies": [ "Weight scale IoT", "Batch manifest", "Certification oracle" ], "technologyProperties": { "granularity": "Per-batch (100+ kg batches)", "identificationMethod": "Batch manifests with weight certification", "trackingLifecycle": "Batch provenance from source to facility" } }, "facility-aggregate": { "technologies": [ "Facility-wide weighbridge", "Monthly reporting", "Facility oracle" ], "technologyProperties": { "granularity": "Per-facility aggregate (tons/month)", "identificationMethod": "Facility intake manifests", "trackingLifecycle": "Facility-level inflow and outflow" } } }, "text": "What tracking granularity is required?", "ngoText": "What tracking granularity is required?" }, { "id": "material-flow", "type": "select", "options": [ { "label": "Linear chain-of-custody with digital handoffs", "value": "linear-custody" }, { "label": "Circular loop with feedback to producers", "value": "circular-feedback" }, { "label": "Material bank with dynamic allocation", "value": "material-bank" } ], "prefillFrom": null, "briefSection": "Monitoring and verification", "propertyMapping": { "linear-custody": { "technologies": [ "Digital signature handoff", "Chain-of-custody smart contract", "Custody transfer oracle" ], "technologyProperties": { "flowModel": "Linear: Collection -> Transport -> Facility -> Recycling", "handoffVerification": "Cryptographic signature per transfer", "settingTime": "24-48 hours per custody transfer" } }, "circular-feedback": { "technologies": [ "Producer responsibility oracle", "Feedback loop smart contract", "Design-for-recycling registry" ], "technologyProperties": { "flowModel": "Circular: Producer -> Use -> Collection -> Recycling -> Producer", "feedbackMechanism": "Recycled material composition data to producer", "improvementCycle": "Quarterly design-for-recycling analysis" } }, "material-bank": { "technologies": [ "Material inventory smart contract", "Dynamic allocation oracle", "Material marketplace" ], "technologyProperties": { "flowModel": "Material bank: Recycled stock available for diverse applications", "allocationMechanism": "On-demand matching to buyer specifications", "matchingTime": "< 1 week from inquiry to allocation" } } }, "text": "How many distinct stages in your waste recycling flow? (collection -> sorting -> reprocessing -> redistribution?)", "ngoText": "How many distinct stages in your waste recycling flow? (collection -> sorting -> reprocessing -> redistribution?)" }, { "id": "recovery-targets", "type": "select", "options": [ { "label": "Producer extended responsibility with token rewards", "value": "producer-epr-rewards" }, { "label": "Mandatory recovery percentages with penalties", "value": "mandatory-recovery" }, { "label": "Market-based recovery credits trading", "value": "recovery-credits" } ], "prefillFrom": null, "briefSection": "Carbon accounting", "propertyMapping": { "producer-epr-rewards": { "technologies": [ "Accounting system automation", "Recovery rate oracle", "Reward token distribution" ], "technologyProperties": { "targetMechanism": "Producer responsible for material recovery", "targetMetric": "Annual recovery rate (% of units sold)", "incentiveModel": "Tokens awarded for exceeding targets" } }, "mandatory-recovery": { "technologies": [ "Governance-set targets", "Penalty oracle", "Enforcement smart contract" ], "technologyProperties": { "targetMechanism": "Mandatory by regulation or agreement", "targetMetric": "Fixed recovery percentage (e.g., 70%)", "penaltyModel": "Fines or credits withheld for non-compliance" } }, "recovery-credits": { "technologies": [ "Recovery credit token", "Credit trading marketplace", "Compliance oracle" ], "technologyProperties": { "targetMechanism": "Facilities earn credits per unit recovered", "targetMetric": "System-wide recovery target", "tradingModel": "Credits tradeable among producers/recyclers" } } }, "text": "What is your target waste recovery rate and timeline to achieve it?", "ngoText": "What is your target waste recovery rate and timeline to achieve it?" }, { "id": "circular-volume", "type": "select", "options": [ { "label": "Under 1,000 items", "value": "small" }, { "label": "1,000\u201310,000 items", "value": "medium" }, { "label": "10,000\u2013100,000 items", "value": "large" }, { "label": "Over 100,000 items", "value": "enterprise" } ], "propertyMapping": { "small": { "technologies": [ "Simple ledger" ], "technologyProperties": { "scalability": "Standard", "throughput": "Low" } }, "medium": { "technologies": [ "Standard tracking platform" ], "technologyProperties": { "scalability": "Standard", "throughput": "Medium" } }, "large": { "technologies": [ "High-throughput tracking platform", "Batch processing" ], "technologyProperties": { "scalability": "High", "throughput": "High \u2014 batch optimised" } }, "enterprise": { "technologies": [ "Enterprise tracking platform", "Layer 2 scaling" ], "technologyProperties": { "scalability": "Enterprise", "throughput": "Very high \u2014 L2 required" } } }, "prefillFrom": null, "briefSection": "Infrastructure requirements", "text": "What is the monthly volume of waste/recycling items you need to track?", "ngoText": "What is the monthly volume of waste/recycling items you need to track?" }, { "id": "circular-monitoring-freq", "type": "select", "options": [ { "label": "Real-time / continuous", "value": "realtime" }, { "label": "Daily", "value": "daily" }, { "label": "Weekly or monthly", "value": "periodic" }, { "label": "Seasonally or annually", "value": "seasonal" } ], "propertyMapping": { "realtime": { "technologies": [ "IoT sensor integration", "Real-time sensor feed" ], "technologyProperties": { "dataFrequency": "Continuous", "sensorIntegration": "Required" } }, "daily": { "technologies": [ "Automated daily capture", "Sensor or manual" ], "technologyProperties": { "dataFrequency": "Daily", "sensorIntegration": "Recommended" } }, "periodic": { "technologies": [ "Scheduled data capture" ], "technologyProperties": { "dataFrequency": "Periodic", "sensorIntegration": "Optional" } }, "seasonal": { "technologies": [ "Manual data entry acceptable" ], "technologyProperties": { "dataFrequency": "Seasonal", "sensorIntegration": "Not required" } } }, "prefillFrom": null, "briefSection": "Environmental data", "text": "How frequently does waste and recycling monitoring data need to be captured?", "ngoText": "How frequently does waste and recycling monitoring data need to be captured?" }, { "id": "audit-trail-approach", "type": "select", "options": [ { "label": "Full permanent audit trail: every action logged digitally", "value": "full-immutable" }, { "label": "Key events only: milestones and approvals logged digital", "value": "key-events" }, { "label": "Hybrid: key details logged digitally, full records stored separately with tamper-proof links", "value": "hybrid" }, { "label": "Not sure, need guidance on audit trail design", "value": "guidance-needed" } ], "propertyMapping": { "full-immutable": { "technologies": [ "Immutable audit trail", "On-chain event logging", "Audit trail verification service" ], "technologyProperties": { "auditGranularity": "Every action", "storageApproach": "Full Digital logging", "tamperEvidence": "Cryptographic hash chain" } }, "key-events": { "technologies": [ "Milestone-based audit trail", "Approval chain logger", "Audit trail verification service" ], "technologyProperties": { "auditGranularity": "Key milestones and approvals only", "storageApproach": "Selective Digital logging", "tamperEvidence": "Merkle root anchoring" } }, "hybrid": { "technologies": [ "Hybrid audit trail system", "Off-chain storage with hash anchoring", "Audit trail verification service" ], "technologyProperties": { "auditGranularity": "Metadata Digital, full records off-chain", "storageApproach": "Decentralised/off-chain storage with digital hash proofs", "tamperEvidence": "Hash anchoring to blockchain" } }, "guidance-needed": { "technologies": [ "Audit trail framework", "Audit trail verification service" ], "technologyProperties": { "auditGranularity": "To be determined during solution design", "storageApproach": "To be determined", "tamperEvidence": "To be determined" } } }, "prefillFrom": null, "briefSection": "Audit and evidence", "text": "What level of record-keeping and evidence trail do you need for this process?", "ngoText": "What level of record-keeping and evidence trail do you need for this process?" }, { "id": "iot-sensor-approach", "type": "select", "options": [ { "label": "GPS/location tracking devices", "value": "gps-location" }, { "label": "Environmental sensors (temperature, humidity, etc.)", "value": "environmental" }, { "label": "Smart meters (energy, water usage)", "value": "smart-meters" }, { "label": "Mobile phone-based data collection (photos, GPS, manual entry)", "value": "mobile-collection" } ], "propertyMapping": { "gps-location": { "technologies": [ "GPS tracking IoT devices", "IoT sensor data gateway", "Location verification oracle" ], "technologyProperties": { "sensorType": "GPS/GNSS trackers", "dataFrequency": "Configurable (real-time to daily)", "connectivity": "Cellular/satellite" } }, "environmental": { "technologies": [ "Environmental IoT sensors", "IoT sensor data gateway", "Threshold alert service" ], "technologyProperties": { "sensorType": "Temperature, humidity, air quality sensors", "dataFrequency": "Continuous with threshold alerts", "connectivity": "LoRaWAN/cellular" } }, "smart-meters": { "technologies": [ "Smart meter IoT integration", "IoT sensor data gateway", "Usage verification service" ], "technologyProperties": { "sensorType": "Smart meters (energy/water)", "dataFrequency": "Hourly/daily readings", "connectivity": "LoRaWAN/cellular/Wi-Fi" } }, "mobile-collection": { "technologies": [ "Mobile data collection app", "IoT sensor proxy layer", "Photo/GPS verification service" ], "technologyProperties": { "sensorType": "Smartphone (camera, GPS, manual entry)", "dataFrequency": "Event-driven (field visits)", "connectivity": "Offline-first with sync" } } }, "prefillFrom": null, "briefSection": "Data collection", "text": "What type of sensor or data collection devices will be used?", "ngoText": "What type of sensor or data collection devices will be used?" } ], "complexityFactors": { "relationships": 3, "operationalChange": 2, "dataCompliance": 1 }, "suggestedCriteria": [ { "id": "SC-MATERIAL-TRACEABILITY", "name": "Material Flow Traceability", "description": "Can the platform track materials through the full circular economy lifecycle (from initial product, through collection, sorting, reprocessing, and back to new product) with verifiable chain of custody?", "weight": 0.3, "ratingGuide": { "5": "End-to-end material traceability across all lifecycle stages. Unique material IDs persist through reprocessing. Multi-party handoff verification. Supports material composition tracking through transformation (e.g. mixed plastics \u2192 specific resin types).", "4": "Tracking across 3-4 lifecycle stages. Material IDs maintained through most handoffs. Composition tracking for primary materials.", "3": "Tracking for collection and sorting stages. Material IDs lost at reprocessing. Basic handoff logging.", "2": "Collection tracking only. No downstream visibility. Single-stage tracking.", "1": "No material traceability. Waste volumes recorded in aggregate only." } }, { "id": "SC-MULTI-PARTY", "name": "Multi-Party Coordination", "description": "Does the platform support coordination between the many actors in circular economy systems (collectors, sorters, recyclers, manufacturers, municipalities, and regulators) each with different data needs?", "weight": 0.2, "ratingGuide": { "5": "Role-based access for all stakeholder types. Shared data layer with privacy controls per party. Automated handoff notifications. Dispute resolution workflow. Municipality and regulator dashboards.", "4": "Multiple roles supported with appropriate access. Handoff workflows between parties. Basic dispute handling. Regulator reporting.", "3": "Two or three party types. Manual handoff coordination. Shared visibility but limited access controls.", "2": "Single operator platform with viewer access for others. No multi-party workflows.", "1": "Single-user system. No multi-party support." } }, { "id": "SC-METRICS-VERIFICATION", "name": "Circularity Metrics & Verification", "description": "Can the platform calculate and verify circularity metrics (recovery rates, recycled content percentages, waste diversion rates) with supporting evidence that satisfies reporting requirements?", "weight": 0.2, "ratingGuide": { "5": "Automated calculation of standard circularity metrics (Ellen MacArthur Foundation indicators, EU Circular Economy Monitoring Framework). On-chain verification of metric inputs. Third-party audit support. Real-time dashboard.", "4": "Standard metric calculations with verified input data. Supports at least one recognised framework. Periodic reporting.", "3": "Basic metric calculation from tracked data. Manual verification. Custom metrics only \u2014 no standard framework alignment.", "2": "Data available for metric calculation but computation done externally. No verification of inputs.", "1": "No metric calculation. Raw data only, if available." } }, { "id": "SC-IOT-WASTE", "name": "Collection & Sorting Infrastructure Integration", "description": "Can the platform integrate with physical infrastructure (smart bins, sorting facilities, weighbridges, RFID/barcode systems) to capture waste flow data at point of generation?", "weight": 0.2, "ratingGuide": { "5": "Integration with smart bins (fill-level sensors), weighbridges, RFID/barcode scanners, and sorting facility systems. Real-time data capture. Automated material classification via sensors or AI.", "4": "Supports weighbridge and barcode/RFID integration. Near-real-time data capture. Manual material classification with system support.", "3": "Barcode/QR code scanning for collection tracking. Manual weighing with digital entry. Limited sensor integration.", "2": "Manual data entry at collection points. QR codes for basic tracking. No sensor integration.", "1": "No physical infrastructure integration. Paper-based record keeping." } }, { "id": "SC-INCENTIVE-MECHANISM", "name": "Incentive & Compliance Mechanism", "description": "Does the platform support incentive mechanisms (deposit-return, recycling credits, EPR compliance) that motivate participation in circular economy programmes?", "weight": 0.1, "ratingGuide": { "5": "Built-in token or credit system for recycling incentives. Deposit-return scheme support. EPR (Extended Producer Responsibility) compliance tracking. Automated reward distribution based on verified recycling actions.", "4": "Incentive tracking and distribution. Supports at least one incentive model. Basic EPR reporting.", "3": "Records incentive-eligible actions. Manual reward distribution. Compliance data available but not automated.", "2": "Basic activity logging that could support incentives. No built-in incentive mechanism.", "1": "No incentive or compliance features." } } ], "procurement": { "marketMaturity": "emerging", "primaryMode": "rfq", "alternativeModes": [ "off-the-shelf" ], "reasoning": "Circular economy and waste tracking has growing product market.", "exampleProductCategories": [ "circular-economy-platform", "waste-tracking-saas" ], "partnerChannels": [], "lastReviewed": "2026-05-01" } }, { "id": "UC-I-112", "name": "Reforestation verification", "category": "I", "subcategory": "Reforestation", "description": "Check that planted trees exist and are surviving, using satellite images and visits on the ground, so funders can trust the results.", "bCriteria": [ "B1", "B3", "B6" ], "requiredComponents": [ "certificate-registry", "verification-layer", "monitoring-platform", "timestamping-service" ], "conditionalComponents": [ "parametric-oracle", "iot-sensors" ], "crossCategoryDependencies": [ "UC-I-114", "UC-I-114" ], "p2TriggerConditions": { "description": "Activated when P2 shows reforestation projects with carbon offset needs and impact measurement requirements", "rangeSignals": [ "reforestationProjects >=3", "carbonOffset >=2", "impactMeasurement >=3" ] }, "contextFieldsTemplate": [ "area_reforested", "tree_species_planted", "survival_rate_monitoring", "satellite_imagery_frequency", "on_ground_validation_frequency", "monitoring_duration", "carbon_sequestration_estimation" ], "implementationComplexity": "high", "examples": { "note": "Rainforest Foundation and satellite monitoring integration", "references": [ { "name": "Regen Network", "description": "Reforestation and carbon sequestration tracking with satellite-based verification and on-chain carbon credit issuance", "url": "https://www.regen.network/" }, { "name": "Toucan Protocol", "description": "Carbon credit tokenisation for reforestation projects with automated verification mechanisms", "url": "https://toucan.earth/" }, { "name": "VerifyForest", "description": "Satellite-based forest monitoring and carbon credit verification for reforestation projects", "url": "https://verifyforest.com/" } ] }, "propertyMapping": { "satelliteVerifiedReforestationOracle": { "technologies": [ "Satellite imagery oracle", "ML tree detection", "Carbon sequestration modeling" ], "technologyProperties": { "monitoringApproach": "Hybrid satellite + drone + ground surveys", "survivalTracking": "Annual drone DBH measurements", "carbonEstimation": "Allometric equations from field data", "verificationCycle": "Annual with 5-year comprehensive audit" } } }, "solutionQuestions": [ { "id": "monitoring-method", "type": "select", "options": [ { "label": "Satellite imagery with ML-based tree detection", "value": "satellite-ml" }, { "label": "Drone-based aerial surveys with photogrammetry", "value": "drone-survey" }, { "label": "Ground-based surveys with GPS tree mapping", "value": "ground-survey" }, { "label": "Hybrid satellite + drone + ground survey", "value": "hybrid-monitoring" } ], "prefillFrom": null, "briefSection": "Monitoring and verification", "propertyMapping": { "satellite-ml": { "technologies": [ "Satellite imagery oracle", "ML tree classifier", "Vegetation index analysis" ], "technologyProperties": { "monitoringMethod": "Optical/SAR satellite with deep learning", "spatialResolution": "3-10 meter resolution", "updateFrequency": "Quarterly satellite passes", "detectionAccuracy": "85-95% tree identification" } }, "drone-survey": { "technologies": [ "UAV/drone fleet", "Photogrammetry processing", "Tree inventory oracle" ], "technologyProperties": { "monitoringMethod": "High-resolution drone imagery with 3D reconstruction", "spatialResolution": "5cm resolution possible", "updateFrequency": "Semi-annual drone surveys", "detectionAccuracy": "95%+ individual tree identification" } }, "ground-survey": { "technologies": [ "Ground crew with GPS/RTK", "Tree inventory database", "QR-tagged saplings" ], "technologyProperties": { "monitoringMethod": "Manual ground survey with GPS coordinates", "spatialResolution": "Individual tree location accuracy (\u00b12m)", "updateFrequency": "Annual on-site survey", "detectionAccuracy": "100% for tagged trees" } }, "hybrid-monitoring": { "technologies": [ "Satellite baseline", "Drone verification", "Ground truth sampling", "Consensus oracle" ], "technologyProperties": { "monitoringMethod": "Layered approach (satellite -> drone -> spot checks)", "spatialResolution": "Satellite: 10m; Drone: 5cm; Ground: \u00b12m", "updateFrequency": "Satellite quarterly, drone semi-annual, ground annual", "detectionAccuracy": "Hybrid ensemble (95%+ confidence)" } } }, "text": "What reforestation monitoring method is used?", "ngoText": "What reforestation monitoring method is used?" }, { "id": "tree-survival-tracking", "type": "select", "options": [ { "label": "Year-over-year satellite vegetation index comparison", "value": "satellite-ndvi" }, { "label": "Drone-based DBH (diameter at breast height) measurement", "value": "drone-dbh" }, { "label": "QR-tagged sapling verification with IoT sensors", "value": "qr-iot-sensors" } ], "prefillFrom": null, "briefSection": "Monitoring and verification", "propertyMapping": { "satellite-ndvi": { "technologies": [ "NDVI satellite analysis", "Vegetation health oracle", "Growth trend analysis" ], "technologyProperties": { "survivalMetric": "NDVI (Normalized Difference Vegetation Index)", "trackingMethod": "Quarterly NDVI comparison to baseline", "survivalConfidence": "75-85% confidence for live tree presence" } }, "drone-dbh": { "technologies": [ "Drone photogrammetry", "Automated DBH extraction", "Growth rate oracle" ], "technologyProperties": { "survivalMetric": "DBH (diameter) and height measurements", "trackingMethod": "Annual drone survey with 3D measurements", "survivalConfidence": "90%+ accuracy for individual trees" } }, "qr-iot-sensors": { "technologies": [ "QR-tagged saplings", "Soil moisture sensor", "Growth rate sensors" ], "technologyProperties": { "survivalMetric": "Direct sensor data on growth conditions", "trackingMethod": "Real-time IoT monitoring of sapling health", "survivalConfidence": "99% for monitored saplings" } } }, "text": "How frequently must tree survival be measured? (quarterly, annually?) And what accuracy is required?", "ngoText": "How frequently must tree survival be measured? (quarterly, annually?) And what accuracy is required?" }, { "id": "carbon-sequestration", "type": "select", "options": [ { "label": "Allometric equations from tree measurements", "value": "allometric-equations" }, { "label": "Growth model projections with uncertainty bounds", "value": "growth-model" }, { "label": "Direct biomass measurement via destructive sampling", "value": "destructive-sampling" }, { "label": "Remote sensing carbon stock mapping (GEDI/LiDAR)", "value": "remote-sensing-lidar" } ], "prefillFrom": null, "briefSection": "Carbon accounting", "propertyMapping": { "allometric-equations": { "technologies": [ "DBH measurement oracle", "Species-specific allometric calculator", "Carbon content oracle" ], "technologyProperties": { "estimationMethod": "Allometric equation: AGB = a \u00d7 DBH^b", "accuracy": "\u00b115-25% confidence interval", "calculation": "Automated from drone/survey measurements" } }, "growth-model": { "technologies": [ "Forest growth model", "Climate data oracle", "Uncertainty quantification" ], "technologyProperties": { "estimationMethod": "Process-based or empirical growth model", "accuracy": "\u00b120-30% confidence interval", "calculation": "Modeled sequestration over 30-year period" } }, "destructive-sampling": { "technologies": [ "Periodic destructive harvest sampling", "Lab biomass analysis", "Regression oracle" ], "technologyProperties": { "estimationMethod": "Direct measurement on sample trees", "accuracy": "\u00b15-10% confidence interval", "calculation": "Scaling from sample to project area" } }, "remote-sensing-lidar": { "technologies": [ "LiDAR/GEDI satellite data", "Carbon stock mapping oracle", "Calibration with ground truth" ], "technologyProperties": { "estimationMethod": "LiDAR-derived aboveground biomass", "accuracy": "\u00b120% at project scale", "calculation": "Satellite biomass maps with field validation" } } }, "text": "What carbon sequestration methodology does your climate standard require?", "ngoText": "What carbon sequestration methodology does your climate standard require?", "hidden": true }, { "id": "verification-frequency", "type": "select", "options": [ { "label": "Continuous satellite monitoring with real-time alerts", "value": "continuous-satellite" }, { "label": "Annual verification with third-party audit", "value": "annual-audit" }, { "label": "Verification every 5 years with conservative additionality", "value": "5year-verification" } ], "prefillFrom": null, "briefSection": "Reporting and audit", "propertyMapping": { "continuous-satellite": { "technologies": [ "Daily satellite passes", "Anomaly detection oracle", "Real-time alerting" ], "technologyProperties": { "verificationFrequency": "Continuous monitoring", "alertLatency": "< 24 hours for anomalies", "costPerVerification": "Low (automated satellite)", "applicability": "Large-scale projects" } }, "annual-audit": { "technologies": [ "Annual drone survey", "Third-party validator", "Audit attestation oracle" ], "technologyProperties": { "verificationFrequency": "Annual", "auditLatency": "60-90 days", "costPerVerification": "Moderate ($5-20K per project)", "applicability": "Medium-scale projects" } }, "5year-verification": { "technologies": [ "5-year survey cycle", "Conservative baseline", "Withholding ratio" ], "technologyProperties": { "verificationFrequency": "Every 5 years", "auditLatency": "90-180 days", "costPerVerification": "Lower (amortized over 5 years)", "applicability": "Landscape-scale or baseline projects" } } }, "text": "What verification frequency is required?", "ngoText": "What verification frequency is required?", "hidden": true }, { "id": "reforest-verification-std", "type": "select", "options": [ { "label": "Gold Standard", "value": "gold-standard" }, { "label": "Verra / VCS", "value": "verra" }, { "label": "National or regional standard", "value": "national" }, { "label": "Custom or internal methodology", "value": "custom" }, { "label": "Not yet determined", "value": "tbd" } ], "propertyMapping": { "gold-standard": { "technologies": [ "Gold Standard registry integration" ], "technologyProperties": { "verificationProtocol": "Gold Standard", "certificationLevel": "International" } }, "verra": { "technologies": [ "Verra VCS registry integration" ], "technologyProperties": { "verificationProtocol": "Verra VCS", "certificationLevel": "International" } }, "national": { "technologies": [ "National registry connection" ], "technologyProperties": { "verificationProtocol": "National standard", "certificationLevel": "National" } }, "custom": { "technologies": [ "Custom verification engine" ], "technologyProperties": { "verificationProtocol": "Custom", "certificationLevel": "Internal" } }, "tbd": { "technologies": [ "Flexible verification framework" ], "technologyProperties": { "verificationProtocol": "To be determined", "certificationLevel": "Flexible" } } }, "prefillFrom": null, "briefSection": "Monitoring and verification", "text": "What verification standards or methodologies apply to reforestation?", "ngoText": "What verification standards or methodologies apply to reforestation?" }, { "id": "reforest-monitoring-freq", "type": "select", "options": [ { "label": "Real-time / continuous", "value": "realtime" }, { "label": "Daily", "value": "daily" }, { "label": "Weekly or monthly", "value": "periodic" }, { "label": "Seasonally or annually", "value": "seasonal" } ], "propertyMapping": { "realtime": { "technologies": [ "IoT sensor integration", "Real-time sensor feed" ], "technologyProperties": { "dataFrequency": "Continuous", "sensorIntegration": "Required" } }, "daily": { "technologies": [ "Automated daily capture", "Sensor or manual" ], "technologyProperties": { "dataFrequency": "Daily", "sensorIntegration": "Recommended" } }, "periodic": { "technologies": [ "Scheduled data capture" ], "technologyProperties": { "dataFrequency": "Periodic", "sensorIntegration": "Optional" } }, "seasonal": { "technologies": [ "Manual data entry acceptable" ], "technologyProperties": { "dataFrequency": "Seasonal", "sensorIntegration": "Not required" } } }, "prefillFrom": null, "briefSection": "Environmental data", "text": "How frequently does reforestation progress monitoring data need to be captured?", "ngoText": "How frequently does reforestation progress monitoring data need to be captured?" }, { "id": "monitoring-platform-approach", "type": "select", "options": [ { "label": "Satellite imagery with AI analysis", "value": "satellite-ai" }, { "label": "Ground-based monitoring with field agents", "value": "ground-based" }, { "label": "Community-based monitoring with mobile reporting", "value": "community-based" }, { "label": "Combined satellite + ground truth verification", "value": "combined" } ], "propertyMapping": { "satellite-ai": { "technologies": [ "Satellite monitoring platform", "AI image analysis engine", "Monitoring verification service" ], "technologyProperties": { "monitoringMethod": "Satellite imagery + AI", "frequency": "Weekly/monthly satellite passes", "coverage": "Large area \u2014 regional/national" } }, "ground-based": { "technologies": [ "Ground-based monitoring platform", "Field agent data collection app", "Monitoring verification service" ], "technologyProperties": { "monitoringMethod": "Field agent visits + sensors", "frequency": "Scheduled site visits", "coverage": "Site-specific" } }, "community-based": { "technologies": [ "Community monitoring platform", "Mobile reporting module", "Monitoring verification service" ], "technologyProperties": { "monitoringMethod": "Community reporters with mobile", "frequency": "Ongoing community reporting", "coverage": "Community-defined areas" } }, "combined": { "technologies": [ "Multi-layer monitoring platform", "Satellite + ground truth integration", "Monitoring verification service" ], "technologyProperties": { "monitoringMethod": "Satellite overview + ground truth", "frequency": "Satellite weekly + field visits monthly", "coverage": "Full coverage with spot verification" } } }, "prefillFrom": null, "briefSection": "Monitoring and verification", "text": "What monitoring approach do you currently use verify outcomes on the ground?", "ngoText": "What monitoring approach do you currently use verify outcomes on the ground?" }, { "id": "timestamping-approach", "type": "select", "options": [ { "label": "Digital timestamping (each event anchored with tamper-proof proof)", "value": "on-chain" }, { "label": "Batch anchoring (events collected, periodically anchored)", "value": "batch-anchoring" }, { "label": "Trusted third-party timestamping authority", "value": "trusted-authority" }, { "label": "Not sure, need guidance on timestamping approach", "value": "guidance-needed" } ], "propertyMapping": { "on-chain": { "technologies": [ "On-chain timestamping service", "Event hash generation", "Timestamp verification API" ], "technologyProperties": { "timestampMethod": "Per-event Digital anchoring", "latency": "Near-instant (block confirmation time)", "legalAdmissibility": "Strong \u2014 independent blockchain proof" } }, "batch-anchoring": { "technologies": [ "Batch timestamping service", "Merkle tree aggregation", "Timestamp verification API" ], "technologyProperties": { "timestampMethod": "Periodic batch anchoring (hourly/daily)", "latency": "Batch interval", "legalAdmissibility": "Strong \u2014 Merkle proof to blockchain" } }, "trusted-authority": { "technologies": [ "Trusted timestamping authority integration", "RFC 3161 timestamping service", "Timestamp verification API" ], "technologyProperties": { "timestampMethod": "Trusted third-party authority", "latency": "Near-instant", "legalAdmissibility": "Varies by jurisdiction" } }, "guidance-needed": { "technologies": [ "Timestamping service framework", "Timestamp verification API" ], "technologyProperties": { "timestampMethod": "To be determined", "latency": "To be determined", "legalAdmissibility": "To be determined" } } }, "prefillFrom": null, "briefSection": "Evidence and timestamping", "text": "How is events and evidence currently timestamped for this solution?", "ngoText": "How is events and evidence currently timestamped for this solution?" } ], "complexityFactors": { "relationships": 3, "operationalChange": 2, "dataCompliance": 2 }, "suggestedCriteria": [ { "id": "SC-REMOTE-SENSING", "name": "Remote Sensing & Satellite Integration", "description": "Can the platform integrate satellite imagery and remote sensing data to independently verify tree planting, survival, and growth at scale without relying solely on self-reported field data?", "weight": 0.3, "ratingGuide": { "5": "Automated satellite imagery analysis (open and commercial imagery). Multi-temporal comparison for growth tracking. NDVI and canopy cover analysis. Change detection for deforestation alerts. Resolution sufficient for individual plot verification.", "4": "Satellite integration with at least one provider. Periodic imagery analysis (quarterly). Canopy cover metrics. Manual change detection.", "3": "Supports satellite data upload and display but no automated analysis. Annual imagery review. Basic before/after comparison.", "2": "Satellite data referenced but not integrated into platform. Manual image comparison.", "1": "No satellite or remote sensing capability. Relies entirely on self-reported data." } }, { "id": "SC-CARBON-SEQUESTRATION", "name": "Carbon Sequestration Quantification", "description": "Does the platform apply recognised methodologies to calculate carbon sequestered by reforested areas, with appropriate biomass models, growth curves, and uncertainty factors?", "weight": 0.25, "ratingGuide": { "5": "Implements recognised methodologies (AR-ACM0003, Gold Standard A/R, Verra VM0007). Species-specific allometric equations. Above and below-ground biomass. Leakage and permanence risk buffers. Automated calculation from monitoring data.", "4": "Supports one major methodology with automated calculation. Species-specific models for common species. Basic leakage accounting.", "3": "Generic biomass model with manual methodology application. Limited species-specific data. No automated leakage calculation.", "2": "Simplified carbon estimates (e.g. flat tonnes per hectare). No recognised methodology. No leakage or permanence accounting.", "1": "No carbon quantification. Tree count only with no sequestration estimate." } }, { "id": "SC-GROUND-TRUTH", "name": "Ground-Truth Verification", "description": "Does the platform support on-the-ground verification through field surveys, photo evidence, GPS-tagged observations, or community-based monitoring to complement remote sensing?", "weight": 0.2, "ratingGuide": { "5": "Mobile app for field teams with GPS-tagged photo capture. Structured survey forms. Community monitoring tools. Cross-validation between satellite and ground data. Timestamped and geolocated evidence on-chain.", "4": "Mobile data collection with GPS and photos. Structured forms. Evidence anchored on-chain. No community monitoring module.", "3": "GPS-tagged field reports uploaded manually. Basic photo evidence. Limited on-chain anchoring.", "2": "Paper-based field surveys digitised after collection. No GPS tagging. No on-chain evidence.", "1": "No ground-truth verification capability." } }, { "id": "SC-PERMANENCE", "name": "Permanence & Long-Term Monitoring", "description": "Does the platform address the permanence challenge, ensuring reforested areas are maintained over the 20-40 year commitment periods required by carbon credit standards?", "weight": 0.15, "ratingGuide": { "5": "Automated long-term monitoring with deforestation alerts. Buffer pool management for permanence risk. Smart contract-based conditional credit release over commitment period. Historical data maintained for full project lifetime.", "4": "Ongoing monitoring with periodic deforestation checks. Buffer pool tracking. Multi-year data retention. Manual credit release schedule.", "3": "Annual monitoring commitment. Basic deforestation detection. 10-year data retention. No buffer pool management.", "2": "Monitoring for initial crediting period only. No deforestation alerts. Limited data retention.", "1": "No long-term monitoring. Single verification at planting time." } }, { "id": "SC-COMMUNITY-BENEFIT", "name": "Community Co-Benefits & Safeguards", "description": "Does the platform track social and environmental co-benefits (livelihoods, biodiversity, water) and safeguards (FPIC, land rights) alongside carbon, as required by quality credit standards?", "weight": 0.1, "ratingGuide": { "5": "Structured tracking of co-benefits across categories (livelihoods, biodiversity, water, gender). FPIC documentation and land rights verification. SDG alignment reporting. Community feedback mechanisms. Meets CCB or SD VISta standards.", "4": "Tracks 2-3 co-benefit categories. FPIC documentation supported. Basic SDG mapping. Community engagement logging.", "3": "Generic co-benefit reporting. FPIC awareness but no structured workflow. Manual SDG mapping.", "2": "Co-benefits mentioned in project description but not systematically tracked. No safeguard verification.", "1": "No co-benefit or safeguard tracking. Carbon-only focus." } } ], "procurement": { "marketMaturity": "emerging", "primaryMode": "tender", "alternativeModes": [ "integrator-led" ], "reasoning": "Reforestation verification platforms with growing maturity.", "exampleProductCategories": [ "reforestation-platform", "forest-monitoring-rails" ], "partnerChannels": [], "lastReviewed": "2026-05-01" } }, { "id": "UC-I-113", "name": "Biodiversity conservation tracking", "category": "I", "subcategory": "Biodiversity", "description": "Record wildlife and plant observations from field surveys and cameras, so conservation managers can trust the data and spot false or duplicate reports.", "bCriteria": [ "B1", "B3" ], "requiredComponents": [ "monitoring-platform", "iot-sensors", "data-integrity-layer", "timestamping-service" ], "conditionalComponents": [ "parametric-oracle", "certificate-registry" ], "crossCategoryDependencies": [ "UC-H-106", "UC-I-114" ], "p2TriggerConditions": { "description": "Activated when P2 shows biodiversity monitoring with protected area management and multi-species tracking needs", "rangeSignals": [ "biodiversityMonitoring >=3", "protectedAreas >=2", "multipleSpeciesTracking >=2" ] }, "contextFieldsTemplate": [ "species_monitored", "protected_area_size", "monitoring_points_count", "data_collection_frequency", "geographic_distribution", "stakeholder_collaboration", "conservation_outcome_metrics" ], "implementationComplexity": "high", "examples": { "note": "IUCN monitoring and conservation tracking", "references": [ { "name": "Regen Network", "description": "Biodiversity monitoring and conservation data platform with blockchain-verified contributions", "url": "https://www.regen.network/" }, { "name": "Bionode", "description": "Decentralised biodiversity data network for researchers and conservation organisations", "url": "https://bionode.io/" }, { "name": "Toucan Protocol", "description": "Biodiversity-linked carbon credits connecting conservation outcomes to tokenised finance", "url": "https://toucan.earth/" } ] }, "propertyMapping": { "biodiversityConservationTrackingNetwork": { "technologies": [ "Camera trap AI", "Satellite forest monitoring", "Community data platform" ], "technologyProperties": { "speciesMonitoring": "Multi-method (camera, acoustic, eDNA, citizen science)", "areaManagement": "Satellite deforestation + ranger patrol tracking", "dataStandards": "IUCN-compatible with flexible local adaptation", "collaborationModel": "Public ledger with role-based access and contribution incentives" } } }, "solutionQuestions": [ { "id": "species-monitoring", "type": "select", "options": [ { "label": "Camera trap networks with AI image classification", "value": "camera-trap-ai" }, { "label": "Acoustic monitoring with bioacoustic classification", "value": "acoustic-monitoring" }, { "label": "eDNA sampling with genetic analysis", "value": "edna-sampling" }, { "label": "Community-based monitoring with citizen science", "value": "citizen-science" } ], "prefillFrom": null, "briefSection": "Monitoring and verification", "propertyMapping": { "camera-trap-ai": { "technologies": [ "Motion-triggered camera traps", "ML species classifier", "Wildlife data oracle" ], "technologyProperties": { "monitoringMethod": "Continuous passive monitoring", "speciesIdentification": "95%+ for common species", "populationEstimation": "Capture-recapture from photo records", "dataLatency": "Real-time event logging" } }, "acoustic-monitoring": { "technologies": [ "Autonomous recording units (ARUs)", "Bioacoustic ML classifier", "Species call oracle" ], "technologyProperties": { "monitoringMethod": "Continuous acoustic recording", "speciesIdentification": "85%+ for vocalization-based species", "populationEstimation": "Call frequency and timing patterns", "dataLatency": "Batch processing (daily/weekly)" } }, "edna-sampling": { "technologies": [ "eDNA sample collection", "Metabarcoding lab analysis", "Species registry" ], "technologyProperties": { "monitoringMethod": "Environmental DNA from soil/water", "speciesIdentification": "Presence/absence for all species", "populationEstimation": "Relative abundance from read counts", "dataLatency": "2-4 weeks for lab results" } }, "citizen-science": { "technologies": [ "Mobile app for sightings", "Community validation oracle", "Data quality checks" ], "technologyProperties": { "monitoringMethod": "Citizen observers report sightings", "speciesIdentification": "Photo-verified by trained community", "populationEstimation": "Occupancy modeling from occurrence data", "dataLatency": "Real-time mobile app submission" } } }, "text": "How are species populations monitored?", "ngoText": "How are species populations monitored?" }, { "id": "protected-area-management", "type": "select", "options": [ { "label": "Satellite deforestation monitoring with alert system", "value": "satellite-deforestation" }, { "label": "GPS ranger patrol tracking with geofencing", "value": "gps-patrol-tracking" }, { "label": "Community-based area management with land rights registry", "value": "community-management" } ], "prefillFrom": null, "briefSection": "Monitoring and verification", "propertyMapping": { "satellite-deforestation": { "technologies": [ "Satellite forest loss detection", "Real-time alert oracle", "Ranger dispatch system" ], "technologyProperties": { "managementMetric": "Forest integrity tracking", "alertLatency": "< 48 hours for forest loss", "responseProtocol": "Automated alert to ranger enforcement team", "complianceVerification": "Periodic enforcement patrol confirmation" } }, "gps-patrol-tracking": { "technologies": [ "GPS-tracked ranger patrols", "Geofence smart contract", "Patrol coverage oracle" ], "technologyProperties": { "managementMetric": "Ranger patrol coverage of protected area", "trackingGranularity": "Real-time patrol location and duration", "complianceVerification": "Automated patrol coverage analysis", "incentiveModel": "Token rewards for patrol completion" } }, "community-management": { "technologies": [ "Land rights smart contract", "Community governance", "Boundary oracle" ], "technologyProperties": { "managementMetric": "Community stewardship of protected area", "governanceModel": "Decentralized governance by community", "rightRegistration": "Blockchain-verified land rights", "incentiveModel": "Direct revenue from conservation credits" } } }, "text": "How many management authorities/jurisdictions oversee your protected areas?", "ngoText": "How many management authorities/jurisdictions oversee your protected areas?" }, { "id": "data-collection", "type": "select", "options": [ { "label": "Standardized biodiversity protocols (IUCN, BirdLife)", "value": "iucn-birdlife-protocols" }, { "label": "Flexible schema with validation rules per ecosystem", "value": "flexible-schema" }, { "label": "Minimal schema with automated harmonization post-collection", "value": "minimal-schema" } ], "prefillFrom": null, "briefSection": "Environmental data", "propertyMapping": { "iucn-birdlife-protocols": { "technologies": [ "IUCN classification oracle", "Protocol validation", "Data standardization contract" ], "technologyProperties": { "standardization": "IUCN Red List and BirdLife taxonomy", "dataInteroperability": "Cross-compatible with global registries", "validationMethod": "Automated schema validation", "onboardingEase": "Medium (requires protocol training)" } }, "flexible-schema": { "technologies": [ "Ecosystem-specific schema", "Flexible validation", "Data harmonization oracle" ], "technologyProperties": { "standardization": "Custom per ecosystem type", "dataInteroperability": "Requires mapping between schemas", "validationMethod": "Rule-based ecosystem-specific checks", "onboardingEase": "Easier (flexible requirements)" } }, "minimal-schema": { "technologies": [ "Minimal data schema", "Post-hoc harmonization ML", "Data cleaning oracle" ], "technologyProperties": { "standardization": "Minimal core schema; ML harmonization later", "dataInteroperability": "Automated ML mapping to standards", "validationMethod": "ML-based outlier and format detection", "onboardingEase": "Easiest (minimal upfront standardization)" } } }, "text": "What biodiversity data sources are you currently using?", "ngoText": "What biodiversity data sources are you currently using?" }, { "id": "stakeholder-collaboration", "type": "select", "options": [ { "label": "Public register with role-based access control", "value": "public-rbac" }, { "label": "Multi-stakeholder consortium with consensus-based updates", "value": "consortium-consensus" }, { "label": "Distributed data repository with verifiable contribution records", "value": "data-lake-proofs" } ], "prefillFrom": null, "briefSection": "Reporting and audit", "propertyMapping": { "public-rbac": { "technologies": [ "Public blockchain", "Role-based access control", "Identity oracle" ], "technologyProperties": { "collaborationModel": "Public transparency with permissioned viewing", "dataSharingRules": "Stakeholder role determines visibility", "updateRights": "Authorized entities can submit data", "incentiveModel": "Token rewards for data contribution" } }, "consortium-consensus": { "technologies": [ "Permissioned blockchain", "Multisig validation", "Consensus oracle" ], "technologyProperties": { "collaborationModel": "Consortium of trusted stakeholders", "dataSharingRules": "Shared repository with multi-stakeholder governance", "updateRights": "Changes require consensus from validators", "incentiveModel": "Governance participation tokens" } }, "data-lake-proofs": { "technologies": [ "Decentralised storage", "Contribution proof oracle", "Zero-knowledge proof of contribution" ], "technologyProperties": { "collaborationModel": "Decentralized storage with attribution proofs", "dataSharingRules": "Contributor-controlled access permissions", "updateRights": "Append-only or versioned updates with signatures", "incentiveModel": "Contribution reward tokens" } } }, "text": "How many distinct stakeholder organizations need collaborative data access?", "ngoText": "How many distinct stakeholder organizations need collaborative data access?" }, { "id": "biodiversity-verification-std", "type": "select", "options": [ { "label": "Gold Standard", "value": "gold-standard" }, { "label": "Verra / VCS", "value": "verra" }, { "label": "National or regional standard", "value": "national" }, { "label": "Custom or internal methodology", "value": "custom" }, { "label": "Not yet determined", "value": "tbd" } ], "propertyMapping": { "gold-standard": { "technologies": [ "Gold Standard registry integration" ], "technologyProperties": { "verificationProtocol": "Gold Standard", "certificationLevel": "International" } }, "verra": { "technologies": [ "Verra VCS registry integration" ], "technologyProperties": { "verificationProtocol": "Verra VCS", "certificationLevel": "International" } }, "national": { "technologies": [ "National registry connection" ], "technologyProperties": { "verificationProtocol": "National standard", "certificationLevel": "National" } }, "custom": { "technologies": [ "Custom verification engine" ], "technologyProperties": { "verificationProtocol": "Custom", "certificationLevel": "Internal" } }, "tbd": { "technologies": [ "Flexible verification framework" ], "technologyProperties": { "verificationProtocol": "To be determined", "certificationLevel": "Flexible" } } }, "prefillFrom": null, "briefSection": "Monitoring and verification", "text": "What verification standards apply to your biodiversity conservation work?", "ngoText": "What verification standards apply to your biodiversity conservation work?" }, { "id": "biodiversity-monitoring-freq", "type": "select", "options": [ { "label": "Real-time / continuous", "value": "realtime" }, { "label": "Daily", "value": "daily" }, { "label": "Weekly or monthly", "value": "periodic" }, { "label": "Seasonally or annually", "value": "seasonal" } ], "propertyMapping": { "realtime": { "technologies": [ "IoT sensor integration", "Real-time sensor feed" ], "technologyProperties": { "dataFrequency": "Continuous", "sensorIntegration": "Required" } }, "daily": { "technologies": [ "Automated daily capture", "Sensor or manual" ], "technologyProperties": { "dataFrequency": "Daily", "sensorIntegration": "Recommended" } }, "periodic": { "technologies": [ "Scheduled data capture" ], "technologyProperties": { "dataFrequency": "Periodic", "sensorIntegration": "Optional" } }, "seasonal": { "technologies": [ "Manual data entry acceptable" ], "technologyProperties": { "dataFrequency": "Seasonal", "sensorIntegration": "Not required" } } }, "prefillFrom": null, "briefSection": "Environmental data", "text": "How frequently does biodiversity monitoring data need to be captured?", "ngoText": "How frequently does biodiversity monitoring data need to be captured?" }, { "id": "monitoring-platform-approach", "type": "select", "options": [ { "label": "Satellite imagery with AI analysis", "value": "satellite-ai" }, { "label": "Ground-based monitoring with field agents", "value": "ground-based" }, { "label": "Community-based monitoring with mobile reporting", "value": "community-based" }, { "label": "Combined satellite + ground truth verification", "value": "combined" } ], "propertyMapping": { "satellite-ai": { "technologies": [ "Satellite monitoring platform", "AI image analysis engine", "Monitoring verification service" ], "technologyProperties": { "monitoringMethod": "Satellite imagery + AI", "frequency": "Weekly/monthly satellite passes", "coverage": "Large area \u2014 regional/national" } }, "ground-based": { "technologies": [ "Ground-based monitoring platform", "Field agent data collection app", "Monitoring verification service" ], "technologyProperties": { "monitoringMethod": "Field agent visits + sensors", "frequency": "Scheduled site visits", "coverage": "Site-specific" } }, "community-based": { "technologies": [ "Community monitoring platform", "Mobile reporting module", "Monitoring verification service" ], "technologyProperties": { "monitoringMethod": "Community reporters with mobile", "frequency": "Ongoing community reporting", "coverage": "Community-defined areas" } }, "combined": { "technologies": [ "Multi-layer monitoring platform", "Satellite + ground truth integration", "Monitoring verification service" ], "technologyProperties": { "monitoringMethod": "Satellite overview + ground truth", "frequency": "Satellite weekly + field visits monthly", "coverage": "Full coverage with spot verification" } } }, "prefillFrom": null, "briefSection": "Monitoring and verification", "text": "What monitoring approach do you currently use verify outcomes on the ground?", "ngoText": "What monitoring approach do you currently use verify outcomes on the ground?" }, { "id": "iot-sensor-approach", "type": "select", "options": [ { "label": "GPS/location tracking devices", "value": "gps-location" }, { "label": "Environmental sensors (temperature, humidity, etc.)", "value": "environmental" }, { "label": "Smart meters (energy, water usage)", "value": "smart-meters" }, { "label": "Mobile phone-based data collection (photos, GPS, manual entry)", "value": "mobile-collection" } ], "propertyMapping": { "gps-location": { "technologies": [ "GPS tracking IoT devices", "IoT sensor data gateway", "Location verification oracle" ], "technologyProperties": { "sensorType": "GPS/GNSS trackers", "dataFrequency": "Configurable (real-time to daily)", "connectivity": "Cellular/satellite" } }, "environmental": { "technologies": [ "Environmental IoT sensors", "IoT sensor data gateway", "Threshold alert service" ], "technologyProperties": { "sensorType": "Temperature, humidity, air quality sensors", "dataFrequency": "Continuous with threshold alerts", "connectivity": "LoRaWAN/cellular" } }, "smart-meters": { "technologies": [ "Smart meter IoT integration", "IoT sensor data gateway", "Usage verification service" ], "technologyProperties": { "sensorType": "Smart meters (energy/water)", "dataFrequency": "Hourly/daily readings", "connectivity": "LoRaWAN/cellular/Wi-Fi" } }, "mobile-collection": { "technologies": [ "Mobile data collection app", "IoT sensor proxy layer", "Photo/GPS verification service" ], "technologyProperties": { "sensorType": "Smartphone (camera, GPS, manual entry)", "dataFrequency": "Event-driven (field visits)", "connectivity": "Offline-first with sync" } } }, "prefillFrom": null, "briefSection": "Data collection", "text": "What type of sensor or data collection devices will be used?", "ngoText": "What type of sensor or data collection devices will be used?" }, { "id": "timestamping-approach", "type": "select", "options": [ { "label": "Digital timestamping (each event anchored with tamper-proof proof)", "value": "on-chain" }, { "label": "Batch anchoring (events collected, periodically anchored)", "value": "batch-anchoring" }, { "label": "Trusted third-party timestamping authority", "value": "trusted-authority" }, { "label": "Not sure, need guidance on timestamping approach", "value": "guidance-needed" } ], "propertyMapping": { "on-chain": { "technologies": [ "On-chain timestamping service", "Event hash generation", "Timestamp verification API" ], "technologyProperties": { "timestampMethod": "Per-event Digital anchoring", "latency": "Near-instant (block confirmation time)", "legalAdmissibility": "Strong \u2014 independent blockchain proof" } }, "batch-anchoring": { "technologies": [ "Batch timestamping service", "Merkle tree aggregation", "Timestamp verification API" ], "technologyProperties": { "timestampMethod": "Periodic batch anchoring (hourly/daily)", "latency": "Batch interval", "legalAdmissibility": "Strong \u2014 Merkle proof to blockchain" } }, "trusted-authority": { "technologies": [ "Trusted timestamping authority integration", "RFC 3161 timestamping service", "Timestamp verification API" ], "technologyProperties": { "timestampMethod": "Trusted third-party authority", "latency": "Near-instant", "legalAdmissibility": "Varies by jurisdiction" } }, "guidance-needed": { "technologies": [ "Timestamping service framework", "Timestamp verification API" ], "technologyProperties": { "timestampMethod": "To be determined", "latency": "To be determined", "legalAdmissibility": "To be determined" } } }, "prefillFrom": null, "briefSection": "Evidence and timestamping", "text": "How is events and evidence currently timestamped for this solution?", "ngoText": "How is events and evidence currently timestamped for this solution?" } ], "complexityFactors": { "relationships": 3, "operationalChange": 2, "dataCompliance": 2 }, "suggestedCriteria": [ { "id": "SC-SPECIES-MONITORING", "name": "Species & Habitat Monitoring Integration", "description": "Can the platform integrate diverse biodiversity monitoring methods (camera traps, acoustic sensors, eDNA, transect surveys, citizen science) into a unified data layer with taxonomic rigour?", "weight": 0.3, "ratingGuide": { "5": "Supports 4+ monitoring methods (camera traps, acoustics, eDNA, surveys, citizen science). Taxonomic backbone integration (GBIF, IUCN Red List). Automated species identification via AI. Standardised observation records (Darwin Core).", "4": "Supports 2-3 monitoring methods. Taxonomic validation against one major database. Semi-automated identification. Standard data formats.", "3": "Single monitoring method well supported. Manual species identification. Basic taxonomic structure.", "2": "Generic data entry for observations. No taxonomic validation. No integration with monitoring equipment.", "1": "No biodiversity monitoring capability. Free-text records only." } }, { "id": "SC-CONSERVATION-OUTCOME", "name": "Conservation Outcome Measurement", "description": "Can the platform measure and verify conservation outcomes using recognised indicators (species population trends, habitat extent, threat reduction) rather than just tracking activities?", "weight": 0.25, "ratingGuide": { "5": "Calculates recognised biodiversity indicators (Shannon diversity, species richness, IUCN threat status trends). Baseline-to-current comparison. Counterfactual analysis. Outcome verification by independent assessors. Aligned with GBF targets.", "4": "Tracks key biodiversity indicators with trend analysis. Baseline comparison. Supports at least one recognised framework (KBA, OECM).", "3": "Basic indicator tracking (species counts, area protected). No trend analysis. Manual outcome assessment.", "2": "Activity tracking only (patrols conducted, area surveyed). No outcome measurement.", "1": "No measurement framework. Narrative reports only." } }, { "id": "SC-DATA-INTEGRITY-BIO", "name": "Data Integrity & Evidence Chain", "description": "Does the platform ensure biodiversity observations are tamper-evident and provenance-tracked, creating a trustworthy evidence base for conservation claims and biodiversity credit issuance?", "weight": 0.2, "ratingGuide": { "5": "Cryptographic hashing of observations at point of capture. GPS, timestamp, and observer identity anchored on-chain. Photo/audio evidence with integrity proof. Full chain of custody from field observation to published dataset.", "4": "On-chain anchoring of observation records. GPS and timestamp verification. Evidence files stored with integrity checks.", "3": "Server-side integrity checks. GPS and timestamp recorded but not cryptographically verified. Basic evidence storage.", "2": "Database records with no integrity proofs. Metadata recorded but not verified.", "1": "No data integrity measures. Observations are editable with no audit trail." } }, { "id": "SC-MULTI-JURISDICTION", "name": "Cross-Jurisdiction & Multi-Stakeholder Coordination", "description": "Can the platform coordinate conservation data across multiple management authorities, jurisdictions, and partner organisations while respecting data sovereignty and sensitive species location protections?", "weight": 0.15, "ratingGuide": { "5": "Multi-authority data sharing with granular access controls. Sensitive species location masking (automatic fuzzing for threatened species). Data sovereignty rules per jurisdiction. Federated architecture \u2014 each authority owns their data.", "4": "Multi-organisation data sharing. Basic access controls. Manual sensitive species protection. Shared database with partitioned access.", "3": "Data sharing via export/import between organisations. Limited access controls. No automatic sensitive species protection.", "2": "Single-organisation platform. Data sharing requires manual file exchange.", "1": "No multi-stakeholder support. Single-user system." } }, { "id": "SC-BIODIVERSITY-CREDIT", "name": "Biodiversity Credit & Finance Readiness", "description": "Is the platform positioned to support emerging biodiversity credit markets by linking verified conservation outcomes to tradeable credits or conservation finance instruments?", "weight": 0.1, "ratingGuide": { "5": "Biodiversity credit issuance based on verified outcomes. Alignment with emerging standards (Biodiversity Credit Alliance, Verra Nature Framework). Credit lifecycle tracking (issuance, transfer, retirement). Integration with conservation finance platforms.", "4": "Framework for credit issuance with verified outcome data. Awareness of emerging standards. Basic credit lifecycle tracking.", "3": "Outcome data suitable for credit applications but no built-in credit mechanism. Manual credit issuance process.", "2": "Data could theoretically support credits but platform has no credit-related features.", "1": "No biodiversity credit or finance features." } } ], "procurement": { "marketMaturity": "emerging", "primaryMode": "rfq", "alternativeModes": [ "integrator-led" ], "reasoning": "Biodiversity conservation tracking platforms emerging.", "exampleProductCategories": [ "biodiversity-platform", "conservation-tracking-rails" ], "partnerChannels": [], "lastReviewed": "2026-05-01" } }, { "id": "UC-I-114", "name": "Clean cookstove distribution and usage verification", "category": "I", "subcategory": "Clean Energy", "description": "Track where clean cookstoves were delivered and whether households really use them, so you can measure the effect of the programme.", "bCriteria": [ "B1", "B3", "B8" ], "requiredComponents": [ "usage-tracking", "iot-sensors", "certificate-registry", "monitoring-platform" ], "conditionalComponents": [ "smart-contracts", "payment-collection" ], "crossCategoryDependencies": [ "UC-I-114" ], "p2TriggerConditions": { "description": "Activated when P2 shows cookstove distribution programmes with usage verification challenges and impact measurement needs", "rangeSignals": [ "cookstoveDistribution >=3", "usageVerification >=3", "impactMeasurement >=2" ] }, "contextFieldsTemplate": [ "stove_models_distributed", "number_of_beneficiaries", "monitoring_technology", "usage_patterns_expected", "carbon_reduction_estimate", "health_impact_measurement", "payment_model" ], "implementationComplexity": "medium", "examples": { "note": "Global Alliance for Clean Cookstoves work", "references": [ { "name": "Toucan Protocol", "description": "Tokenises carbon credits from clean cookstove programmes for blockchain-based payment distribution", "url": "https://toucan.earth/" }, { "name": "Celo for Clean Energy", "description": "Mobile-based payment platform for clean cookstove distribution and usage incentive programmes", "url": "https://celo.org/" }, { "name": "Gold Standard Smart Cookstove Protocol", "description": "Standardised verification and tokenisation of clean cookstove climate mitigation outcomes", "url": "https://www.goldstandard.org/" } ] }, "propertyMapping": { "iotEnabledCookstoveUsageMonitor": { "technologies": [ "IoT stove sensor", "Usage analytics oracle", "Carbon accounting contract" ], "technologyProperties": { "usageMonitoring": "Real-time IoT temperature + periodic spot checks", "carbonReductionEstimation": "UNFCCC default factors or measured fuel consumption", "distributionTracking": "Serial number registry with blockchain transfer history", "paymentModel": "Monthly usage-based stablecoin payments or carbon revenue sharing" } } }, "solutionQuestions": [ { "id": "usage-monitoring", "type": "select", "options": [ { "label": "IoT temperature/humidity sensor on stove", "value": "iot-sensor" }, { "label": "Periodic household surveys and self-reporting", "value": "survey-self-report" }, { "label": "Hybrid IoT sensors + spot checks", "value": "hybrid-iot-checks" } ], "prefillFrom": null, "briefSection": "Monitoring and verification", "propertyMapping": { "iot-sensor": { "technologies": [ "IoT stove sensor", "Cellular/LoRaWAN transmission", "Usage analytics oracle" ], "technologyProperties": { "monitoringMethod": "Real-time IoT sensor on cookstove", "usageTracking": "Continuous temperature monitoring indicates active use", "dataLatency": "Real-time or daily aggregation", "costPerUnit": "$5-15 for sensor + connectivity" } }, "survey-self-report": { "technologies": [ "Quarterly/annual survey", "Mobile survey app", "Data validation oracle" ], "technologyProperties": { "monitoringMethod": "Periodic survey of stove user", "usageTracking": "Self-reported usage frequency and duration", "dataLatency": "Quarterly to annual", "costPerUnit": "$2-5 per survey" } }, "hybrid-iot-checks": { "technologies": [ "IoT sensor with periodic field verification", "Spot check surveys", "Calibration oracle" ], "technologyProperties": { "monitoringMethod": "IoT baseline + quarterly field verification", "usageTracking": "IoT continuous with human validation", "dataLatency": "Real-time IoT with quarterly human confirmation", "costPerUnit": "$7-20 including spot checks" } } }, "text": "How is cookstove usage monitored?", "ngoText": "How is cookstove usage monitored?" }, { "id": "carbon-reduction-verification", "type": "select", "options": [ { "label": "Default emission factors from UNFCCC methodology", "value": "unfccc-default" }, { "label": "Fuel consumption measurement with combustion analysis", "value": "fuel-consumption" }, { "label": "Biochar production measurement for sequestration credit", "value": "biochar-sequestration" } ], "prefillFrom": null, "briefSection": "Carbon accounting", "propertyMapping": { "unfccc-default": { "technologies": [ "UNFCCC methodology oracle", "Default factor lookup", "Calculation engine" ], "technologyProperties": { "estimationMethod": "UNFCCC default emission factors per stove type", "accuracy": "\u00b130-50% confidence interval", "calculation": "Automatic from stove type and usage hours", "applicability": "Large-scale baseline projections" } }, "fuel-consumption": { "technologies": [ "Fuel scale measurement", "Combustion efficiency test", "Carbon content oracle" ], "technologyProperties": { "estimationMethod": "Direct measurement of fuel use reduction vs. baseline", "accuracy": "\u00b115-25% confidence interval", "calculation": "Measured fuel savings \u00d7 carbon content of baseline fuel", "applicability": "Medium-scale projects with fuel availability" } }, "biochar-sequestration": { "technologies": [ "Biochar weight measurement", "Carbon content analysis", "Permanence oracle" ], "technologyProperties": { "estimationMethod": "Direct biochar production from cookstove", "accuracy": "\u00b110-20% confidence interval (for stored biochar)", "calculation": "Biochar weight \u00d7 carbon content \u00d7 permanence discount", "applicability": "Biochar-focused clean cookstove programs" } } }, "text": "How do you verify carbon reduction? (direct testing, usage-based calculation, audits?)", "ngoText": "How do you verify carbon reduction? (direct testing, usage-based calculation, audits?)" }, { "id": "distribution-tracking", "type": "select", "options": [ { "label": "Unique serial number registry with transfer history", "value": "serial-registry" }, { "label": "Batch distribution certificates with bulk handoff", "value": "batch-certificates" }, { "label": "Household geolocation with mobile payment verification", "value": "geolocation-payment" } ], "prefillFrom": null, "briefSection": "Infrastructure requirements", "propertyMapping": { "serial-registry": { "technologies": [ "Serial number blockchain registry", "Transfer smart contract", "Possession oracle" ], "technologyProperties": { "distributionTracking": "Each stove has unique serial and owner record", "transferTracking": "Blockchain record of possession transfers", "verificationMethod": "Cryptographic ownership proof", "applicability": "Individual stove-level tracking" } }, "batch-certificates": { "technologies": [ "Batch manifest", "Distributor-signed certificate", "Bulk transfer oracle" ], "technologyProperties": { "distributionTracking": "Batches of stoves tracked by quantity", "transferTracking": "Distributor -> Implementer -> Household", "verificationMethod": "Signed manifests and photos", "applicability": "Large-scale rapid distribution" } }, "geolocation-payment": { "technologies": [ "Mobile payment receipt", "Geolocation GPS verification", "Payment oracle" ], "technologyProperties": { "distributionTracking": "Household location where stove was received", "transferTracking": "Stove distribution completion verified by payment", "verificationMethod": "Mobile money transaction + GPS at delivery", "applicability": "Field-based distribution with mobile money integration" } } }, "text": "How is cookstove distribution tracked?", "ngoText": "How is cookstove distribution tracked?" }, { "id": "payment-model", "type": "select", "options": [ { "label": "One-time subsidy at distribution", "value": "onetime-subsidy" }, { "label": "Monthly usage-based payments via IoT verification", "value": "monthly-iot-payments" }, { "label": "Carbon credit revenue sharing with automated rules distribution", "value": "carbon-revenue-share" } ], "prefillFrom": null, "briefSection": "Trading mechanism", "propertyMapping": { "onetime-subsidy": { "technologies": [ "Upfront stove subsidy", "Distribution payment", "Recipient verification" ], "technologyProperties": { "paymentTiming": "One-time at installation", "paymentAmount": "$50-200 per stove", "incentiveAlignment": "Household incentivized to take stove", "usageIncentive": "Limited (one-time only)" } }, "monthly-iot-payments": { "technologies": [ "IoT usage data", "Automated payment", "Stablecoin transfer" ], "technologyProperties": { "paymentTiming": "Monthly based on verified usage", "paymentAmount": "$5-20 per month for threshold usage", "incentiveAlignment": "Household incentivized to use stove continuously", "usageIncentive": "High (ongoing usage rewards)" } }, "carbon-revenue-share": { "technologies": [ "Carbon credit tokenization", "Revenue oracle", "Automated revenue distribution" ], "technologyProperties": { "paymentTiming": "Periodic (quarterly/semi-annual) based on carbon credits sold", "paymentAmount": "Variable based on credit price ($1-10 per monthly carbon credit)", "incentiveAlignment": "Household shares in climate finance value", "usageIncentive": "Very high (direct climate finance participation)" } } }, "text": "What payment model incentivizes usage?", "ngoText": "What payment model incentivizes usage?" }, { "id": "cookstove-volume", "type": "select", "options": [ { "label": "Under 1,000 items", "value": "small" }, { "label": "1,000\u201310,000 items", "value": "medium" }, { "label": "10,000\u2013100,000 items", "value": "large" }, { "label": "Over 100,000 items", "value": "enterprise" } ], "propertyMapping": { "small": { "technologies": [ "Simple ledger" ], "technologyProperties": { "scalability": "Standard", "throughput": "Low" } }, "medium": { "technologies": [ "Standard tracking platform" ], "technologyProperties": { "scalability": "Standard", "throughput": "Medium" } }, "large": { "technologies": [ "High-throughput tracking platform", "Batch processing" ], "technologyProperties": { "scalability": "High", "throughput": "High \u2014 batch optimised" } }, "enterprise": { "technologies": [ "Enterprise tracking platform", "Layer 2 scaling" ], "technologyProperties": { "scalability": "Enterprise", "throughput": "Very high \u2014 L2 required" } } }, "prefillFrom": null, "briefSection": "Infrastructure requirements", "text": "What is the monthly volume of cookstoves distributed you need to track?", "ngoText": "What is the monthly volume of cookstoves distributed you need to track?" }, { "id": "iot-sensor-approach", "type": "select", "options": [ { "label": "GPS/location tracking devices", "value": "gps-location" }, { "label": "Environmental sensors (temperature, humidity, etc.)", "value": "environmental" }, { "label": "Smart meters (energy, water usage)", "value": "smart-meters" }, { "label": "Mobile phone-based data collection (photos, GPS, manual entry)", "value": "mobile-collection" } ], "propertyMapping": { "gps-location": { "technologies": [ "GPS tracking IoT devices", "IoT sensor data gateway", "Location verification oracle" ], "technologyProperties": { "sensorType": "GPS/GNSS trackers", "dataFrequency": "Configurable (real-time to daily)", "connectivity": "Cellular/satellite" } }, "environmental": { "technologies": [ "Environmental IoT sensors", "IoT sensor data gateway", "Threshold alert service" ], "technologyProperties": { "sensorType": "Temperature, humidity, air quality sensors", "dataFrequency": "Continuous with threshold alerts", "connectivity": "LoRaWAN/cellular" } }, "smart-meters": { "technologies": [ "Smart meter IoT integration", "IoT sensor data gateway", "Usage verification service" ], "technologyProperties": { "sensorType": "Smart meters (energy/water)", "dataFrequency": "Hourly/daily readings", "connectivity": "LoRaWAN/cellular/Wi-Fi" } }, "mobile-collection": { "technologies": [ "Mobile data collection app", "IoT sensor proxy layer", "Photo/GPS verification service" ], "technologyProperties": { "sensorType": "Smartphone (camera, GPS, manual entry)", "dataFrequency": "Event-driven (field visits)", "connectivity": "Offline-first with sync" } } }, "prefillFrom": null, "briefSection": "Data collection", "text": "What type of sensor or data collection devices will be used?", "ngoText": "What type of sensor or data collection devices will be used?" } ], "complexityFactors": { "relationships": 3, "operationalChange": 3, "dataCompliance": 2 }, "suggestedCriteria": [ { "id": "SC-USAGE-VERIFICATION", "name": "Actual Usage Verification", "description": "Can the platform verify that distributed cookstoves are actually being used (not just distributed), using sensor data, usage telemetry, or structured field verification?", "weight": 0.3, "ratingGuide": { "5": "IoT temperature/usage sensors embedded in stoves transmitting usage data. Automated usage pattern analysis. Anomaly detection for non-use or sensor tampering. Cross-validation with fuel purchase data or household surveys.", "4": "Sensor-based usage monitoring with periodic data transmission. Usage pattern recognition. Manual anomaly review.", "3": "Mobile-based usage surveys with GPS and photo evidence. Periodic household visits. No sensor data.", "2": "Self-reported usage via SMS or app. No independent verification.", "1": "No usage verification. Distribution equals assumed usage." } }, { "id": "SC-CARBON-METHODOLOGY-COOK", "name": "Carbon Reduction Quantification", "description": "Does the platform calculate emission reductions from cookstove usage using recognised methodologies, linking verified usage data to creditable carbon savings?", "weight": 0.25, "ratingGuide": { "5": "Implements Gold Standard Metered Energy Cooking or equivalent. Usage-based emission calculation (not distribution-based). Suppressed demand accounting for LDC contexts. Automated credit quantification from usage data. Leakage and uncertainty buffers.", "4": "Recognised methodology applied. Usage data feeds into calculation. Basic suppressed demand consideration. Semi-automated quantification.", "3": "Standard methodology but calculation based on distribution numbers with usage adjustment factor. Manual calculation.", "2": "Simplified emission estimate per stove distributed. No usage-based adjustment. No recognised methodology.", "1": "No carbon quantification. Stove count only." } }, { "id": "SC-DISTRIBUTION-TRACKING", "name": "Distribution & Beneficiary Tracking", "description": "Can the platform track stove distribution from manufacturer through supply chain to individual households, with beneficiary registration that prevents double-counting?", "weight": 0.2, "ratingGuide": { "5": "Unique stove ID (QR/RFID) tracked from factory to household. Beneficiary registration with deduplication. GPS-tagged delivery confirmation. Supply chain visibility for all intermediaries. Warranty and replacement tracking.", "4": "Stove ID tracking with beneficiary registration. GPS delivery confirmation. Basic supply chain visibility. Deduplication checks.", "3": "Batch-level tracking to distribution point. Beneficiary registration but limited deduplication. No individual stove-to-household linking.", "2": "Aggregate distribution numbers by region. Basic beneficiary lists. No individual stove tracking.", "1": "No distribution tracking beyond initial shipment." } }, { "id": "SC-FIELD-VIABILITY", "name": "Field Deployment Viability", "description": "Is the platform practical for deployment in rural, low-connectivity, low-literacy settings where clean cookstove programmes typically operate?", "weight": 0.15, "ratingGuide": { "5": "Works offline with sync when connected. SMS/USSD fallback for feature phone users. Multilingual with local language support. Low-bandwidth data transmission. Solar-powered sensor options. Pictographic UI for low-literacy users.", "4": "Offline capability with periodic sync. Mobile app works on basic smartphones. Multiple language support. Low-bandwidth optimised.", "3": "Mobile app requires intermittent connectivity. Single local language plus English. Moderate data requirements.", "2": "Requires reliable internet. English only. Smartphone required. Standard data consumption.", "1": "Desktop/web only. Requires constant connectivity. No field deployment consideration." } }, { "id": "SC-IMPACT-COBENEFIT", "name": "Health & Social Impact Measurement", "description": "Does the platform capture co-benefits beyond carbon (indoor air quality improvement, time savings, fuel cost savings, and gender-specific impacts) as required by quality credit standards?", "weight": 0.1, "ratingGuide": { "5": "Structured tracking of health impacts (HAP reduction), time savings, fuel savings, and gender metrics. Household survey integration. SDG alignment reporting. Meets Gold Standard SDG Impact requirements.", "4": "Tracks 2-3 co-benefit categories with structured data collection. Basic SDG mapping.", "3": "Generic co-benefit questions in surveys. Manual impact reporting. No structured metrics.", "2": "Co-benefits mentioned in project documentation but not systematically measured.", "1": "No co-benefit measurement. Carbon-only focus." } } ], "procurement": { "marketMaturity": "emerging", "primaryMode": "rfq", "alternativeModes": [ "integrator-led" ], "reasoning": "Clean cookstove distribution and usage verification has growing product space.", "exampleProductCategories": [ "clean-cookstove-platform", "energy-access-saas" ], "partnerChannels": [], "lastReviewed": "2026-05-01" } }, { "id": "UC-J-115", "name": "Volunteer management and hour tracking", "category": "J", "subcategory": "Volunteer Management", "description": "Record volunteer hours and activities in a way that volunteers and managers both accept, so credit goes to the right people.", "bCriteria": [ "B1", "B3", "B7" ], "requiredComponents": [ "credential-management", "timesheet-system", "audit-trail" ], "conditionalComponents": [ "smart-contracts" ], "crossCategoryDependencies": [], "p2TriggerConditions": { "description": "Activated when P2 shows volunteer programmes at scale with hour tracking needs and accountability requirements", "rangeSignals": [ "volunteerPrograms >=2", "volunteerCount >=3", "hourTracking >=2", "accountabilityRequired >=2", "complianceRequired >=2" ] }, "contextFieldsTemplate": [ "number_of_volunteers", "geographic_locations", "activity_types", "hourly_verification_method", "incentive_structure", "impact_measurement_mechanism", "volunteer_privacy_needs" ], "implementationComplexity": "low", "examples": { "note": "Simple implementation; blockchain adds tamper-proof record", "references": [ { "name": "Better Impact", "url": "https://www.betterimpact.com", "solved": "Volunteer management platform widely used by INGOs for hour tracking and recognition." }, { "name": "Open Badges (1EdTech)", "url": "https://www.1edtech.org/standards/open-badges", "solved": "Open standard for issuing portable, verifiable digital credentials for skills and contributions, including volunteer hours." } ] }, "solutionQuestions": [ { "id": "volunteer-tracking-method", "type": "select", "options": [ { "label": "Manual timesheet submission", "value": "manual-timesheet" }, { "label": "Digitally verified volunteer credentials", "value": "blockchain-verified" }, { "label": "Digital badges and attestations", "value": "digital-badges" } ], "prefillFrom": null, "briefSection": "Tracking and records", "propertyMapping": { "manual-timesheet": { "technologies": [ "Timesheet Smart Contract" ], "technologyProperties": { "automatedValidation": false, "manualApprovalRequired": true, "auditTrailEnabled": true } }, "blockchain-verified": { "technologies": [ "Verifiable Credentials", "Audit Trail" ], "technologyProperties": { "credentialStandard": "W3C-VC", "tamperProof": true, "instantVerification": true } }, "digital-badges": { "technologies": [ "Credential Management", "Smart Contract" ], "technologyProperties": { "interoperableBadges": true, "automaticIssuance": true, "portableCredentials": true } } }, "text": "How are volunteer hours currently tracked and verified?", "ngoText": "How are volunteer hours currently tracked and verified?" }, { "id": "verification-approach", "type": "select", "options": [ { "label": "Supervisor attestation with permanent tamper-proof record", "value": "supervisor-attestation" }, { "label": "Multi-party consensus verification", "value": "multi-party-consensus" }, { "label": "Real-time location and activity verification", "value": "location-activity-verify" } ], "prefillFrom": null, "briefSection": "Verification mechanism", "propertyMapping": { "supervisor-attestation": { "technologies": [ "Audit Trail", "Digital Signature" ], "technologyProperties": { "signingRequired": true, "nonRepudiation": true, "timestampVerified": true } }, "multi-party-consensus": { "technologies": [ "Smart Contract", "Governance Token" ], "technologyProperties": { "consensusRequired": true, "minimumValidators": 3, "automatedDispute": true } }, "location-activity-verify": { "technologies": [ "Geofencing", "IoT Oracle" ], "technologyProperties": { "gpsEnabled": true, "beaconBased": true, "liveTracking": true } } }, "text": "What fraud tolerance level for volunteer time reporting? (self-reported with review vs requiring external verification?)", "ngoText": "What fraud tolerance level for volunteer time reporting? (self-reported with review vs requiring external verification?)" }, { "id": "impact-measurement", "type": "select", "options": [ { "label": "Hours-based impact calculation", "value": "hours-based" }, { "label": "Outcome-driven impact metrics with digital proof", "value": "outcome-driven" }, { "label": "digital impact rewards", "value": "tokenized-rewards" } ], "prefillFrom": null, "briefSection": "Reporting and audit", "propertyMapping": { "hours-based": { "technologies": [ "Timesheet System", "Smart Contract" ], "technologyProperties": { "hourlyTracking": true, "automatedCalculation": true, "beneficiaryLinked": true } }, "outcome-driven": { "technologies": [ "Oracle Feed", "Data Aggregation" ], "technologyProperties": { "metricsTracked": 5, "realTimeUpdates": true, "immutableProof": true } }, "tokenized-rewards": { "technologies": [ "Stablecoin", "NFT" ], "technologyProperties": { "rewardsAutomated": true, "redeemable": true, "impactVerifiable": true } } }, "text": "What volunteer impact metrics must you report? (hours, beneficiaries served, cost equivalent?)", "ngoText": "What volunteer impact metrics must you report? (hours, beneficiaries served, cost equivalent?)" }, { "id": "reporting-mechanism", "type": "select", "options": [ { "label": "Weekly aggregated reports with signed attestation", "value": "weekly-aggregated" }, { "label": "Real-time digital ledger event logging", "value": "realtime-logging" }, { "label": "Donor-facing impact dashboard with verified data", "value": "donor-dashboard" } ], "prefillFrom": null, "briefSection": "Reporting and audit", "propertyMapping": { "weekly-aggregated": { "technologies": [ "Audit Trail", "Automated Report" ], "technologyProperties": { "reportingFrequency": "weekly", "cryptographicProof": true, "immutableArchive": true } }, "realtime-logging": { "technologies": [ "Event Streaming", "Distributed Ledger" ], "technologyProperties": { "eventBased": true, "instantVisibility": true, "queryable": true } }, "donor-dashboard": { "technologies": [ "Data Analytics", "Credential Portal" ], "technologyProperties": { "realTimeDashboard": true, "verifiableLinks": true, "publiclyShareable": true } } }, "text": "What reporting structure is required for volunteer activities?", "ngoText": "What reporting structure is required for volunteer activities?" }, { "id": "volunteer-staff-count", "type": "select", "options": [ { "label": "Under 50", "value": "small" }, { "label": "50\u2013200", "value": "medium" }, { "label": "200\u20131,000", "value": "large" }, { "label": "Over 1,000", "value": "enterprise" } ], "propertyMapping": { "small": { "technologies": [ "Simple record system" ], "technologyProperties": { "scalability": "Standard", "selfService": "Optional" } }, "medium": { "technologies": [ "HR integration platform" ], "technologyProperties": { "scalability": "Standard", "selfService": "Recommended" } }, "large": { "technologies": [ "Scalable workforce platform", "Self-service portal" ], "technologyProperties": { "scalability": "High", "selfService": "Required" } }, "enterprise": { "technologies": [ "Enterprise workforce platform", "Self-service portal", "API-first" ], "technologyProperties": { "scalability": "Enterprise", "selfService": "Required" } } }, "prefillFrom": null, "briefSection": "Infrastructure requirements", "text": "How many staff or individuals need to be tracked in volunteer management?", "ngoText": "How many staff or individuals need to be tracked in volunteer management?" }, { "id": "volunteer-jurisdictions", "type": "select", "options": [ { "label": "Single country", "value": "single" }, { "label": "2\u20135 countries", "value": "few" }, { "label": "6\u201315 countries", "value": "many" }, { "label": "Over 15 countries", "value": "global" } ], "propertyMapping": { "single": { "technologies": [], "technologyProperties": { "jurisdictionalComplexity": "Low", "dataResidency": "Single" } }, "few": { "technologies": [ "Multi-jurisdiction compliance" ], "technologyProperties": { "jurisdictionalComplexity": "Medium", "dataResidency": "Multi-region" } }, "many": { "technologies": [ "Multi-jurisdiction compliance", "Data residency management" ], "technologyProperties": { "jurisdictionalComplexity": "High", "dataResidency": "Distributed" } }, "global": { "technologies": [ "Global compliance framework", "Data residency management", "Multi-language support" ], "technologyProperties": { "jurisdictionalComplexity": "Very high", "dataResidency": "Global distributed" } } }, "prefillFrom": "P0-orgSize", "briefSection": "Compliance and jurisdictions", "text": "How many jurisdictions or countries does volunteer operations span?", "ngoText": "How many jurisdictions or countries does volunteer operations span?" } ], "complexityFactors": { "relationships": 1, "operationalChange": 1, "dataCompliance": 1 }, "suggestedCriteria": [ { "id": "SC-HOUR-INTEGRITY", "name": "Hour-Record Integrity & Tamper Resistance", "description": "Volunteer hours can be recorded immutably with cryptographic proof so that donors and auditors trust the data. In volunteer management, inflated or fabricated hours undermine programme credibility.", "weight": 0.25, "ratingGuide": { "5": "Every hour entry is hash-anchored on-chain with supervisor co-signature. Full tamper-evident audit trail. Attempted edits are logged with original preserved. Third-party audit verification in under 5 minutes.", "4": "Hour entries anchored on-chain with single attestation. Audit trail covers all modifications. Verification possible but may take manual steps.", "3": "Hours stored in an append-only database with periodic blockchain anchoring (e.g. daily batch). Basic tamper detection but no real-time alerting.", "2": "Digital records without blockchain anchoring. Editable logs with version history but no cryptographic proof. Manual audit process.", "1": "Paper-based or editable spreadsheet records. No integrity mechanism. No audit trail for modifications." } }, { "id": "SC-VOL-PRIVACY", "name": "Volunteer Privacy & Data Minimisation", "description": "The system protects volunteer personal data while still enabling hour verification and impact reporting. Volunteers may be in vulnerable situations where data exposure creates risk.", "weight": 0.2, "ratingGuide": { "5": "Zero-knowledge proofs or selective disclosure for hour verification. Volunteers control what data is shared with which parties. GDPR-compliant with right-to-erasure support. No PII stored on-chain.", "4": "Pseudonymous on-chain records with off-chain PII. Role-based access controls. Volunteers can see who accessed their data. Compliant with major privacy frameworks.", "3": "Basic pseudonymisation. Central administrator controls access. Privacy policy exists but limited volunteer control over their own data.", "2": "Volunteer names and hours visible to all system users. Minimal access controls. No data minimisation strategy.", "1": "All volunteer data publicly visible. No privacy controls. PII stored on-chain with no deletion capability." } }, { "id": "SC-IMPACT-ATTRIBUTION", "name": "Impact Attribution & Reporting", "description": "The system can link volunteer hours to measurable programme outcomes for donor reporting. Transparent impact attribution is a key blockchain value-add for volunteer programmes.", "weight": 0.2, "ratingGuide": { "5": "Automated linkage between hours logged and outcome metrics. Real-time impact dashboards. Donor-facing reports generated from on-chain data with verifiable provenance.", "4": "Hours linked to programme activities with semi-automated outcome mapping. Periodic report generation from verified data.", "3": "Hours tracked separately from outcomes. Manual correlation possible. Reports reference blockchain records but linkage is indirect.", "2": "Basic hour totals available. No structured linkage to outcomes. Reports compiled manually from exported data.", "1": "No impact attribution capability. Hours and outcomes tracked in separate unconnected systems." } }, { "id": "SC-SCALE-ONBOARD", "name": "Scalability & Volunteer Onboarding", "description": "The system can handle large volunteer pools with varying technical literacy. Complex onboarding processes deter volunteers and create administrative burden.", "weight": 0.2, "ratingGuide": { "5": "Supports 10,000+ volunteers. Mobile-first interface requiring no blockchain knowledge. Onboarding under 5 minutes. Works offline with sync. Multi-language support.", "4": "Supports thousands of volunteers. Simple mobile or web interface. Onboarding under 15 minutes. Basic offline capability.", "3": "Supports hundreds of volunteers. Web interface with moderate learning curve. Onboarding requires brief training session. Online-only.", "2": "Supports small volunteer pools (<100). Desktop-focused interface. Requires significant training. Assumes reliable internet.", "1": "Prototype-scale only. Technical expertise required to participate. No mobile support. Lengthy onboarding." } }, { "id": "SC-CREDENTIAL-PORT", "name": "Credential Portability & Recognition", "description": "Volunteers can carry verified hour records and skills credentials to other organisations. Portable credentials incentivise volunteering and enable cross-organisation recognition.", "weight": 0.15, "ratingGuide": { "5": "W3C Verifiable Credentials issued for hours and skills. Credentials held in volunteer's own wallet. Recognised by partner organisations. Interoperable with Open Badges and EU Digital Credential frameworks.", "4": "Verifiable credentials issued. Volunteer-held. Recognised by some partner organisations. Partial interoperability with standards.", "3": "Exportable digital certificates. Organisation-specific format but machine-readable. Manual verification by other parties.", "2": "PDF certificates issued. Not machine-verifiable. Organisation-specific format requiring manual confirmation.", "1": "No portable credentials. Hour records locked within the issuing organisation's system. No export capability." } } ], "procurement": { "marketMaturity": "mature", "primaryMode": "off-the-shelf", "alternativeModes": [ "rfq" ], "reasoning": "Volunteer management SaaS is mature.", "exampleProductCategories": [ "volunteer-management-saas", "hour-tracking-platform" ], "partnerChannels": [], "lastReviewed": "2026-05-01" } }, { "id": "UC-J-116", "name": "Staff deployment records across locations", "category": "J", "subcategory": "Operations", "description": "Keep reliable records of where staff are deployed across field locations, so headquarters and field offices hold the same information.", "bCriteria": [ "B1", "B3", "B4" ], "requiredComponents": [ "deployment-tracking", "audit-trail", "credential-management" ], "conditionalComponents": [ "smart-contracts" ], "crossCategoryDependencies": [ "UC-J-121" ], "p2TriggerConditions": { "description": "Activated when P2 shows multi-location operations with staff mobility and accountability requirements", "rangeSignals": [ "multiLocationOperations >=3", "staffMobility >=2", "accountabilityRequired >=2", "dutyOfCareRequired = true", "emergencyOperations >=3" ] }, "contextFieldsTemplate": [ "number_of_locations", "staff_count", "deployment_frequency", "role_specifications", "duration_tracking_need", "cross_border_deployment", "regulatory_requirements" ], "implementationComplexity": "low", "examples": { "note": "Basic operational transparency", "references": [ { "name": "International SOS", "url": "https://www.internationalsos.com", "solved": "Reference platform for global staff tracking, security alerts, and emergency response coordination across international organisations." }, { "name": "Restless Development", "url": "https://restlessdevelopment.org", "solved": "Multi-country deployment-tracking model for youth and volunteer programmes in challenging contexts." } ] }, "solutionQuestions": [ { "id": "deployment-tracking-method", "type": "select", "options": [ { "label": "Central HR database with location updates", "value": "central-db-updates" }, { "label": "Digitally recorded deployment events", "value": "blockchain-events" }, { "label": "Real-time GPS and check-in verification", "value": "gps-checkin-verify" } ], "prefillFrom": null, "briefSection": "Tracking and records", "propertyMapping": { "central-db-updates": { "technologies": [ "Audit Trail", "Digital Signature" ], "technologyProperties": { "centralizedRecord": true, "locationTimestamp": true, "immutableHistory": true } }, "blockchain-events": { "technologies": [ "Distributed Ledger", "Smart Contract" ], "technologyProperties": { "eventBased": true, "multiLocationSync": true, "consensusVerified": true } }, "gps-checkin-verify": { "technologies": [ "Geofencing Oracle", "Mobile App" ], "technologyProperties": { "liveLocationTracking": true, "checkInRequired": true, "automatedRecording": true } } }, "text": "What system tracks staff deployment across locations?", "ngoText": "What system tracks staff deployment across locations?" }, { "id": "cross-border-deployment", "type": "select", "options": [ { "label": "Domestic deployment only", "value": "domestic-only" }, { "label": "International deployments with verifiable visas and permits", "value": "intl-visa-permits" }, { "label": "Rapid deployment across regions with compliance automation", "value": "rapid-intl-deployment" } ], "prefillFrom": null, "briefSection": "Tracking and records", "propertyMapping": { "domestic-only": { "technologies": [ "Audit Trail" ], "technologyProperties": { "regulatoryScope": "local", "documentationRequired": false, "complianceLevel": "basic" } }, "intl-visa-permits": { "technologies": [ "Credential Management", "Government Oracle" ], "technologyProperties": { "visaIntegration": true, "permitTracking": true, "expiryAlerts": true } }, "rapid-intl-deployment": { "technologies": [ "Smart Contract Orchestration", "Compliance Engine" ], "technologyProperties": { "automatedCompliance": true, "regulatorySync": true, "rapidApprovalWorkflow": true } } }, "text": "Are staff deployed across national borders requiring regulatory documentation?", "ngoText": "Are staff deployed across national borders requiring regulatory documentation?" }, { "id": "role-specifications", "type": "select", "options": [ { "label": "Manual role assignment with documentation", "value": "manual-assignment" }, { "label": "Digitally verified role credentials", "value": "blockchain-role-cred" }, { "label": "Dynamic role binding with automated competency checks", "value": "dynamic-competency" } ], "prefillFrom": null, "briefSection": "Credential management", "propertyMapping": { "manual-assignment": { "technologies": [ "Credential Management" ], "technologyProperties": { "manualAssignment": true, "documentationRequired": true, "updateFrequency": "quarterly" } }, "blockchain-role-cred": { "technologies": [ "Verifiable Credentials", "Smart Contract" ], "technologyProperties": { "roleVerified": true, "competencyProven": true, "automatedValidation": true } }, "dynamic-competency": { "technologies": [ "Governance Token", "Oracle Feed" ], "technologyProperties": { "continuousMonitoring": true, "skillValidation": true, "automatedAdjustment": true } } }, "text": "How many distinct staff roles exist, and what competency verification is required?", "ngoText": "How many distinct staff roles exist, and what competency verification is required?" }, { "id": "deployment-reporting", "type": "select", "options": [ { "label": "Monthly staff location reports", "value": "monthly-reports" }, { "label": "Real-time deployment dashboard for management", "value": "realtime-dashboard" }, { "label": "Compliance reporting with digitally verified attendance", "value": "compliance-verified" } ], "prefillFrom": null, "briefSection": "Reporting and audit", "propertyMapping": { "monthly-reports": { "technologies": [ "Audit Trail", "Report Generator" ], "technologyProperties": { "reportingFrequency": "monthly", "locationBased": true, "archiveRequired": true } }, "realtime-dashboard": { "technologies": [ "Data Aggregation", "Live Analytics" ], "technologyProperties": { "realTimeVisibility": true, "locationAccuracy": "precise", "alertsEnabled": true } }, "compliance-verified": { "technologies": [ "Smart Contract Report", "Audit Trail" ], "technologyProperties": { "complianceAutomated": true, "attendanceVerified": true, "regulatoryReady": true } } }, "text": "What reporting requirements exist for deployment records?", "ngoText": "What reporting requirements exist for deployment records?" }, { "id": "staff-deploy-staff-count", "type": "select", "options": [ { "label": "Under 50", "value": "small" }, { "label": "50\u2013200", "value": "medium" }, { "label": "200\u20131,000", "value": "large" }, { "label": "Over 1,000", "value": "enterprise" } ], "propertyMapping": { "small": { "technologies": [ "Simple record system" ], "technologyProperties": { "scalability": "Standard", "selfService": "Optional" } }, "medium": { "technologies": [ "HR integration platform" ], "technologyProperties": { "scalability": "Standard", "selfService": "Recommended" } }, "large": { "technologies": [ "Scalable workforce platform", "Self-service portal" ], "technologyProperties": { "scalability": "High", "selfService": "Required" } }, "enterprise": { "technologies": [ "Enterprise workforce platform", "Self-service portal", "API-first" ], "technologyProperties": { "scalability": "Enterprise", "selfService": "Required" } } }, "prefillFrom": null, "briefSection": "Infrastructure requirements", "text": "How many staff or individuals need to be tracked in staff deployment?", "ngoText": "How many staff or individuals need to be tracked in staff deployment?" }, { "id": "staff-deploy-jurisdictions", "type": "select", "options": [ { "label": "Single country", "value": "single" }, { "label": "2\u20135 countries", "value": "few" }, { "label": "6\u201315 countries", "value": "many" }, { "label": "Over 15 countries", "value": "global" } ], "propertyMapping": { "single": { "technologies": [], "technologyProperties": { "jurisdictionalComplexity": "Low", "dataResidency": "Single" } }, "few": { "technologies": [ "Multi-jurisdiction compliance" ], "technologyProperties": { "jurisdictionalComplexity": "Medium", "dataResidency": "Multi-region" } }, "many": { "technologies": [ "Multi-jurisdiction compliance", "Data residency management" ], "technologyProperties": { "jurisdictionalComplexity": "High", "dataResidency": "Distributed" } }, "global": { "technologies": [ "Global compliance framework", "Data residency management", "Multi-language support" ], "technologyProperties": { "jurisdictionalComplexity": "Very high", "dataResidency": "Global distributed" } } }, "prefillFrom": "P0-orgSize", "briefSection": "Compliance and jurisdictions", "text": "How many jurisdictions or countries does staff deployment span?", "ngoText": "How many jurisdictions or countries does staff deployment span?" }, { "id": "deployment-tracking", "type": "select", "options": [ { "label": "GPS-based location tracking with check-in/check-out", "value": "gps-checkin" }, { "label": "QR code check-in at deployment sites", "value": "qr-checkin" }, { "label": "Manager-attested deployment records", "value": "manager-attested" }, { "label": "Self-reported with supervisor verification", "value": "self-report" } ], "propertyMapping": { "gps-checkin": { "technologies": [ "GPS deployment tracking system", "Location-verified check-in app", "Deployment record ledger" ], "technologyProperties": { "trackingMethod": "GPS location + check-in/out", "verificationLevel": "Automated GPS verification", "privacyControl": "Location tracked during work hours only" } }, "qr-checkin": { "technologies": [ "QR-based deployment tracking", "Site QR code system", "Deployment record ledger" ], "technologyProperties": { "trackingMethod": "QR code scan at site", "verificationLevel": "Physical presence at QR location", "privacyControl": "Scan events only \u2014 no continuous tracking" } }, "manager-attested": { "technologies": [ "Manager-attested deployment tracking", "Attestation workflow", "Deployment record ledger" ], "technologyProperties": { "trackingMethod": "Manager attestation", "verificationLevel": "Manager-verified", "privacyControl": "No location tracking" } }, "self-report": { "technologies": [ "Self-reported deployment tracking", "Supervisor verification module", "Deployment record ledger" ], "technologyProperties": { "trackingMethod": "Self-report + supervisor sign-off", "verificationLevel": "Two-party verification", "privacyControl": "Self-declared only" } } }, "prefillFrom": null, "briefSection": "Staff deployment", "text": "How should staff deployments be tracked and verified?", "ngoText": "How should staff deployments be tracked and verified?" } ], "complexityFactors": { "relationships": 2, "operationalChange": 2, "dataCompliance": 2 }, "suggestedCriteria": [ { "id": "SC-DEPLOY-VERIFY", "name": "Deployment Record Verifiability", "description": "Staff deployment records can be independently verified across multiple field locations. In multi-site NGO operations, accurate deployment records are essential for donor accountability and duty-of-care compliance.", "weight": 0.25, "ratingGuide": { "5": "Each deployment record cryptographically signed by both deploying office and receiving location. On-chain timestamp and location attestation. Third-party verification without contacting either office.", "4": "Deployment records anchored on-chain with single-office attestation. Receiving location confirms via separate transaction. Verification possible with minor manual steps.", "3": "Deployment records stored centrally with periodic blockchain anchoring. Verification requires contacting central HR. Basic tamper detection.", "2": "Digital deployment records without blockchain verification. Editable by administrators. Cross-location verification requires manual coordination.", "1": "Paper-based or spreadsheet deployment tracking. No verifiability. Records inconsistent across locations." } }, { "id": "SC-CROSS-LOC-SYNC", "name": "Cross-Location Data Synchronisation", "description": "The system maintains consistent deployment data across field offices with intermittent connectivity. Field locations in humanitarian settings often have unreliable internet.", "weight": 0.25, "ratingGuide": { "5": "Conflict-free replicated data across all locations. Offline-capable with automatic sync on reconnection. Guaranteed eventual consistency with blockchain finality. Sub-hour sync in normal conditions.", "4": "Reliable sync across locations with offline queuing. Consistency achieved within hours. Conflict resolution for simultaneous edits.", "3": "Centralised system with periodic sync to field offices. Daily synchronisation. Manual conflict resolution needed occasionally.", "2": "Manual data entry at each location. Weekly or ad-hoc synchronisation via file exchange. Frequent inconsistencies.", "1": "No cross-location synchronisation. Each office maintains independent records. Consolidation requires manual aggregation." } }, { "id": "SC-ROLE-TRACK", "name": "Role & Assignment Tracking Granularity", "description": "The system can track where staff are deployed, with their specific roles, skill requirements, and assignment durations. Granular tracking enables better workforce planning.", "weight": 0.2, "ratingGuide": { "5": "Full role taxonomy with skills mapping. Assignment start/end dates, extensions, and role changes all recorded on-chain. Workforce planning analytics from verified data.", "4": "Role and skill tracking with on-chain records. Assignment timeline captured. Basic workforce analytics available.", "3": "Role recorded at deployment. Changes tracked but not on-chain. Limited analytics from deployment data.", "2": "Basic location assignment only. Role tracked in separate HR system. No integrated view.", "1": "Location-only tracking. No role, skill, or duration data captured in the system." } }, { "id": "SC-HR-INTEGRATE", "name": "HR System Integration", "description": "The solution integrates with existing HR and payroll systems. Standalone deployment tracking that doesn't connect to HR processes creates duplicate data entry and inconsistencies.", "weight": 0.15, "ratingGuide": { "5": "API integration with major HRIS platforms. Bidirectional sync of deployment data. Automated payroll location updates.", "4": "API integration with at least two major HRIS platforms. One-way sync with manual override. Structured data export for payroll.", "3": "CSV/file-based integration with HR systems. Semi-automated import/export. Some manual reconciliation required.", "2": "Manual data export only. No direct integration. HR team must re-enter deployment data.", "1": "No integration capability. Completely standalone system with no data exchange." } }, { "id": "SC-DEPLOY-PRIVACY", "name": "Staff Location Data Protection", "description": "This looks at how sensitive staff location data is protected. Deployment records reveal where staff are stationed, which in conflict zones can create security risks if exposed.", "weight": 0.15, "ratingGuide": { "5": "Encrypted location data with need-to-know access controls. On-chain records contain only hashed references. Tiered visibility \u2014 HQ sees all, field offices see their staff only. Emergency override protocols.", "4": "Encrypted records with role-based access. Location specificity adjustable (country vs. site level). Access logging for all queries.", "3": "Access-controlled central database. Basic encryption. Location data visible to all authenticated users within the organisation.", "2": "Password-protected system with minimal access differentiation. Location data accessible to broad user groups.", "1": "No access controls on location data. Staff deployment locations visible to all system users. No encryption." } } ], "procurement": { "marketMaturity": "mature", "primaryMode": "off-the-shelf", "alternativeModes": [ "rfq" ], "reasoning": "HRIS and staff deployment records are mature SaaS market.", "exampleProductCategories": [ "hris-platform", "staff-deployment-saas" ], "partnerChannels": [], "lastReviewed": "2026-05-01" } }, { "id": "UC-J-117", "name": "Training completion records", "category": "J", "subcategory": "Training", "description": "Keep training records that staff can carry with them and show to a new employer or partner, without you verifying them each time.", "bCriteria": [ "B1", "B3" ], "requiredComponents": [ "training-records", "credential-management", "verification-platform" ], "conditionalComponents": [ "smart-contracts" ], "crossCategoryDependencies": [ "UC-J-121", "UC-J-121" ], "p2TriggerConditions": { "description": "Activated when P2 shows training programmes with credential portability needs and verification requirements", "rangeSignals": [ "trainingPrograms >=2", "credentialPortability >=2", "verificationRequired >=2", "accessControl >=3" ] }, "contextFieldsTemplate": [ "training_types", "number_of_trainees_annually", "credential_types", "expiration_requirements", "verification_entity_count", "geographic_recognition_scope" ], "implementationComplexity": "low", "examples": { "note": "Verifiable credentials standard (W3C)", "references": [ { "name": "Credly", "url": "https://www.credly.com", "solved": "Digital credential platform used widely for training-completion records with portable, verifiable credentials." }, { "name": "Accredible", "url": "https://www.accredible.com", "solved": "Verifiable credential issuance for training programmes and professional development with blockchain-anchored options." }, { "name": "Open Badges (1EdTech)", "url": "https://www.1edtech.org/standards/open-badges", "solved": "Open standard for portable training credentials adopted by humanitarian sector training providers." } ] }, "solutionQuestions": [ { "id": "credential-format", "type": "select", "options": [ { "label": "Paper certificates checked in person", "value": "paper-certificates-checked-in-person" }, { "label": "Digital documents (PDF, email) shared and reviewed manually", "value": "digital-documents-pdf-email-shared-and-r" }, { "label": "Online registry or database lookup to confirm validity", "value": "online-registry-or-database-lookup-to-co" }, { "label": "No standard process, it varies by employer and jurisdiction", "value": "no-standard-process-it-varies-by-employe" }, { "label": "Not sure, varies across our operating contexts", "value": "not-sure-varies-across-our-operating-con" } ], "prefillFrom": null, "briefSection": "Credential management", "propertyMapping": { "digital-certs": { "technologies": [ "Document Management" ], "technologyProperties": { "portable": true, "digitallySigned": true, "nonInteroperable": true } }, "w3c-verifiable": { "technologies": [ "Verifiable Credentials", "Credential Wallet" ], "technologyProperties": { "standardBased": true, "cryptographicallySignable": true, "interoperable": true } }, "nft-badges": { "technologies": [ "NFT", "Smart Contract" ], "technologyProperties": { "uniqueProof": true, "transferable": true, "permanentRecord": true } } }, "text": "What credential formats do employers and regulators in your context accept?", "ngoText": "What credential formats do employers and regulators in your context accept?", "question": "How are professional qualifications and training certificates currently verified in your operating context?" }, { "id": "verification-entity", "type": "select", "options": [ { "label": "Internal training department only", "value": "internal-only" }, { "label": "Multiple accredited training institutions", "value": "multi-accredited" }, { "label": "Third-party independent assessor with digital ledger attestation", "value": "third-party-attest" } ], "prefillFrom": null, "briefSection": "Verification mechanism", "propertyMapping": { "internal-only": { "technologies": [ "Credential Management" ], "technologyProperties": { "issuerCount": 1, "verificationCentralized": true, "privateNetwork": true } }, "multi-accredited": { "technologies": [ "Verifiable Credentials", "Credential Registry" ], "technologyProperties": { "issuerCount": "3+", "accreditationVerified": true, "publicRegistry": true } }, "third-party-attest": { "technologies": [ "External data feed", "Verifiable Credentials" ], "technologyProperties": { "independentVerification": true, "blockchainBacked": true, "disintermediatedTrust": true } } }, "text": "Who is authorized to issue and verify training credentials?", "ngoText": "Who is authorized to issue and verify training credentials?" }, { "id": "expiration-tracking", "type": "select", "options": [ { "label": "Manual expiry date in documents", "value": "manual-expiry" }, { "label": "automated rules automated expiry and renewal prompts", "value": "smart-contract-expiry" }, { "label": "Digitally verified recertification with progressive disclosure", "value": "blockchain-recert" } ], "prefillFrom": null, "briefSection": "Credential management", "propertyMapping": { "manual-expiry": { "technologies": [ "Document Management" ], "technologyProperties": { "automatedAlerts": false, "manualTracking": true, "renewalReminders": "manual" } }, "smart-contract-expiry": { "technologies": [ "Smart Contract", "Credential Management" ], "technologyProperties": { "automatedAlerts": true, "renewalTriggered": true, "complianceEnforced": true } }, "blockchain-recert": { "technologies": [ "Verifiable Credentials", "Privacy Oracle" ], "technologyProperties": { "continuousCertification": true, "selectiveDisclosure": true, "riskBasedRenewal": true } } }, "text": "How are training credential expiration and renewal tracked?", "ngoText": "How are training credential expiration and renewal tracked?" }, { "id": "recognition-scope", "type": "select", "options": [ { "label": "Single organization only", "value": "single-org" }, { "label": "National or regional NGO consortium", "value": "regional-consortium" }, { "label": "International recognition via digital ledger credential registry", "value": "intl-blockchain" } ], "prefillFrom": null, "briefSection": "Verification mechanism", "propertyMapping": { "single-org": { "technologies": [ "Credential Management" ], "technologyProperties": { "recognitionScope": "internal", "portability": "low", "networkEffect": "none" } }, "regional-consortium": { "technologies": [ "Verifiable Credentials", "Federated Network" ], "technologyProperties": { "recognitionScope": "regional", "portability": "high", "trustNetwork": "established" } }, "intl-blockchain": { "technologies": [ "Distributed Credential Registry", "Interoperability Layer" ], "technologyProperties": { "recognitionScope": "global", "portability": "universal", "standardsCompliant": true } } }, "text": "What is the geographic and institutional recognition scope for training?", "ngoText": "What is the geographic and institutional recognition scope for training?" }, { "id": "training-staff-count", "type": "select", "options": [ { "label": "Under 50", "value": "small" }, { "label": "50\u2013200", "value": "medium" }, { "label": "200\u20131,000", "value": "large" }, { "label": "Over 1,000", "value": "enterprise" } ], "propertyMapping": { "small": { "technologies": [ "Simple record system" ], "technologyProperties": { "scalability": "Standard", "selfService": "Optional" } }, "medium": { "technologies": [ "HR integration platform" ], "technologyProperties": { "scalability": "Standard", "selfService": "Recommended" } }, "large": { "technologies": [ "Scalable workforce platform", "Self-service portal" ], "technologyProperties": { "scalability": "High", "selfService": "Required" } }, "enterprise": { "technologies": [ "Enterprise workforce platform", "Self-service portal", "API-first" ], "technologyProperties": { "scalability": "Enterprise", "selfService": "Required" } } }, "prefillFrom": null, "briefSection": "Infrastructure requirements", "text": "How many staff or individuals need to be tracked in training tracking?", "ngoText": "How many staff or individuals need to be tracked in training tracking?" }, { "id": "training-jurisdictions", "type": "select", "options": [ { "label": "Single country", "value": "single" }, { "label": "2\u20135 countries", "value": "few" }, { "label": "6\u201315 countries", "value": "many" }, { "label": "Over 15 countries", "value": "global" } ], "propertyMapping": { "single": { "technologies": [], "technologyProperties": { "jurisdictionalComplexity": "Low", "dataResidency": "Single" } }, "few": { "technologies": [ "Multi-jurisdiction compliance" ], "technologyProperties": { "jurisdictionalComplexity": "Medium", "dataResidency": "Multi-region" } }, "many": { "technologies": [ "Multi-jurisdiction compliance", "Data residency management" ], "technologyProperties": { "jurisdictionalComplexity": "High", "dataResidency": "Distributed" } }, "global": { "technologies": [ "Global compliance framework", "Data residency management", "Multi-language support" ], "technologyProperties": { "jurisdictionalComplexity": "Very high", "dataResidency": "Global distributed" } } }, "prefillFrom": "P0-orgSize", "briefSection": "Compliance and jurisdictions", "text": "How many jurisdictions or countries does training programmes span?", "ngoText": "How many jurisdictions or countries does training programmes span?" }, { "id": "training-records", "type": "select", "options": [ { "label": "Digital certificates with digital verification", "value": "digital-certs" }, { "label": "LMS integration (link to existing learning management system)", "value": "lms-integration" }, { "label": "Standalone training record ledger", "value": "standalone" }, { "label": "Not sure, need guidance", "value": "guidance-needed" } ], "propertyMapping": { "digital-certs": { "technologies": [ "Blockchain training records", "Digital certificate issuance", "Training verification portal" ], "technologyProperties": { "recordType": "Verifiable digital certificates", "portability": "Holder-controlled, shareable anywhere", "verification": "Instant cryptographic verification" } }, "lms-integration": { "technologies": [ "LMS-integrated training records", "LMS API connection", "Training verification portal" ], "technologyProperties": { "recordType": "Synced from existing LMS", "portability": "Within LMS + blockchain backup", "verification": "Cross-referenced with LMS" } }, "standalone": { "technologies": [ "Standalone training record system", "Manual entry interface", "Training verification portal" ], "technologyProperties": { "recordType": "Manually entered records", "portability": "Blockchain-based portability", "verification": "Digital record check" } }, "guidance-needed": { "technologies": [ "Training records framework", "Training verification portal" ], "technologyProperties": { "recordType": "To be determined", "portability": "To be determined", "verification": "To be determined" } } }, "prefillFrom": null, "briefSection": "Training and certification", "text": "How are training completion records currently managed?", "ngoText": "How are training completion records currently managed?" } ], "complexityFactors": { "relationships": 1, "operationalChange": 1, "dataCompliance": 1 }, "suggestedCriteria": [ { "id": "SC-CRED-STANDARD", "name": "Credential Standard Compliance", "description": "The system issues training credentials in recognised standards like W3C Verifiable Credentials or Open Badges. Standard-compliant credentials are essential for cross-organisational and cross-border recognition.", "weight": 0.25, "ratingGuide": { "5": "Full W3C Verifiable Credentials compliance. Also supports Open Badges 3.0 and EU European Digital Credentials. Credential schema registered in public registry. Machine-readable and human-readable formats.", "4": "W3C VC compliant. Supports one additional standard. Credentials machine-verifiable. Schema documented.", "3": "Proprietary credential format but with export to W3C VC or Open Badges. Semi-automated conversion. Verification requires provider platform.", "2": "Proprietary digital certificates. Not standards-compliant. Manual verification only through issuing platform.", "1": "No digital credentials issued. Paper certificates or non-verifiable PDFs only." } }, { "id": "SC-TRAIN-VERIFY", "name": "Training Completion Verification", "description": "This measures how reliably third parties can verify that an individual completed specific training. Verification must be possible without contacting the issuing organisation directly.", "weight": 0.25, "ratingGuide": { "5": "Instant verification via QR code, URL, or DID resolution. Verification checks credential signature, issuer authority, revocation status, and expiry. No issuer involvement needed. Batch verification for HR onboarding.", "4": "Verification via URL or API call. Checks signature and expiry. Issuer not needed for basic verification. Individual credential checks.", "3": "Verification possible through issuer's online portal. Requires credential ID lookup. Issuer platform must be online.", "2": "Verification only by contacting the issuing organisation. Email or phone-based confirmation. Slow turnaround.", "1": "No verification mechanism. Reliance on paper documents or self-reported completion." } }, { "id": "SC-LEARNER-CONTROL", "name": "Learner Credential Ownership", "description": "Learners hold and control their own credentials, or are records locked within the training provider's system. Learner-held credentials enable portability and reduce dependency on any single provider.", "weight": 0.2, "ratingGuide": { "5": "Credentials issued directly to learner's digital wallet. Learner controls sharing, can present selectively, and retains access even if issuer goes offline. Supports multiple wallet providers.", "4": "Credentials downloadable to learner's device. Can be shared independently. Access maintained if issuer platform changes. Single wallet provider supported.", "3": "Credentials accessible via learner login on issuer platform. Can be exported but not natively portable. Issuer platform dependency for ongoing access.", "2": "Credentials stored only on issuer platform. Learner can view but not independently share or export in verifiable format.", "1": "No learner access to digital credentials. Records held entirely by issuing organisation. Learner must request copies." } }, { "id": "SC-EXPIRY-RENEWAL", "name": "Expiry & Renewal Management", "description": "The system handles credential expiry, renewal reminders, and re-certification workflows. Many training certifications have validity periods and lapsed credentials create compliance risk.", "weight": 0.15, "ratingGuide": { "5": "Automated expiry tracking with configurable advance notifications. Renewal workflows integrated. Expired credentials automatically flagged in verification. Credential versioning for updated curricula.", "4": "Expiry dates encoded in credentials. Automated reminders to holders. Verification shows expiry status. Manual renewal initiation.", "3": "Expiry dates tracked in system. Email reminders available. Verification does not automatically check expiry \u2014 requires manual review.", "2": "Expiry dates recorded but no automated tracking or reminders. Manual review process for renewals.", "1": "No expiry tracking. Credentials issued without validity periods. No renewal workflow." } }, { "id": "SC-INSTITUTION-TRUST", "name": "Institutional Trust & Issuer Authority", "description": "This looks at how the system establishes that the training provider is a legitimate, recognised institution. Without trust in the issuer, verifiable credentials lose their value.", "weight": 0.15, "ratingGuide": { "5": "Issuers registered in a governance framework with vetting process. Issuer DIDs anchored on-chain. Trusted issuer registries (e.g. EBSI, sector-specific lists) integrated. Revocation of issuer authority supported.", "4": "Issuer identity verified and published. DID-based issuer identification. Listed in at least one recognised registry. Issuer status queryable.", "3": "Issuer identified by domain-linked credentials. Basic vetting at onboarding. No ongoing authority monitoring or registry integration.", "2": "Issuer self-asserts identity. No external vetting. Credential consumers must independently verify issuer legitimacy.", "1": "No issuer identification mechanism. Credentials cannot be attributed to a verified institution." } } ], "procurement": { "marketMaturity": "mature", "primaryMode": "off-the-shelf", "alternativeModes": [ "rfq" ], "reasoning": "Learning management systems are mature.", "exampleProductCategories": [ "lms-platform", "training-records-saas" ], "partnerChannels": [], "lastReviewed": "2026-05-01" } }, { "id": "UC-J-118", "name": "Safeguarding training verification", "category": "J", "subcategory": "Safeguarding", "description": "Confirm that staff completed safeguarding training and passed any assessment, in a form that employers and funders can check.", "bCriteria": [ "B1", "B3", "B6" ], "requiredComponents": [ "safeguarding-records", "training-records", "verification-platform", "credential-management" ], "conditionalComponents": [ "smart-contracts" ], "crossCategoryDependencies": [ "UC-J-121", "UC-J-121" ], "p2TriggerConditions": { "description": "Activated when P2 shows mandatory safeguarding requirements with staff verification obligations and regulatory compliance", "rangeSignals": [ "safeguardingRequired = true", "staffVerification >=3", "regulatoryRequired = true", "dutyOfCareRequired = true", "accountabilityRequired >=2" ] }, "contextFieldsTemplate": [ "safeguarding_training_standard", "staff_categories_required", "training_frequency", "assessment_method", "verification_stakeholders", "confidentiality_requirements", "access_control_rules" ], "implementationComplexity": "medium", "examples": { "note": "Child safeguarding and adult protection standards", "references": [ { "name": "Misconduct Disclosure Scheme", "url": "https://www.schr.info/the-misconduct-disclosure-scheme", "solved": "Inter-agency safeguarding-misconduct disclosure scheme run by the Steering Committee for Humanitarian Response with pooled employer-records." }, { "name": "Bond UK Safeguarding", "url": "https://www.bond.org.uk/safeguarding", "solved": "Sector-wide safeguarding standards and training-verification framework for UK INGO membership." }, { "name": "CHS Alliance", "url": "https://www.chsalliance.org", "solved": "Core Humanitarian Standard verification body with structured training and certification model." } ] }, "solutionQuestions": [ { "id": "training-standard", "type": "select", "options": [ { "label": "Internal organizational safeguarding policy", "value": "internal-policy" }, { "label": "National safeguarding standards (NSPCC, Local Authority guidance)", "value": "national-standards" }, { "label": "International safeguarding standards with digital verification", "value": "intl-standards-verified" } ], "prefillFrom": null, "briefSection": "Verification mechanism", "propertyMapping": { "internal-policy": { "technologies": [ "Training Records" ], "technologyProperties": { "standard": "proprietary", "regulatory": "internal", "thirdPartyRecognition": false } }, "national-standards": { "technologies": [ "Compliance Engine", "Training Records" ], "technologyProperties": { "standard": "national", "regulatory": "approved", "thirdPartyRecognition": true } }, "intl-standards-verified": { "technologies": [ "Verifiable Credentials", "Standards Oracle" ], "technologyProperties": { "standard": "international", "regulatory": "multiJurisdiction", "blockchainVerified": true } } }, "text": "What are your current training standards for your workforce?", "ngoText": "What are your current training standards for your workforce?" }, { "id": "assessment-method", "type": "select", "options": [ { "label": "Training attendance with manual assessment notes", "value": "attendance-manual" }, { "label": "Automated online quiz with instant digital ledger recording", "value": "online-quiz-blockchain" }, { "label": "Competency-based assessment with signed supervisor attestation", "value": "competency-supervisor" } ], "prefillFrom": null, "briefSection": "Verification mechanism", "propertyMapping": { "attendance-manual": { "technologies": [ "Training Records" ], "technologyProperties": { "automatedAssessment": false, "manualReview": true, "documentationRequired": true } }, "online-quiz-blockchain": { "technologies": [ "Smart Contract", "Assessment Platform" ], "technologyProperties": { "automatedScoring": true, "instantRecording": true, "tamperProof": true } }, "competency-supervisor": { "technologies": [ "Verifiable Credentials", "Digital Signature" ], "technologyProperties": { "competencyBased": true, "supervisorVerified": true, "evidenceRequired": true } } }, "text": "What competency verification level do your safeguarding standards require? (attendance only, testing, practical eval?)", "ngoText": "What competency verification level do your safeguarding standards require? (attendance only, testing, practical eval?)" }, { "id": "renewal-tracking", "type": "select", "options": [ { "label": "Annual manual reminder emails", "value": "manual-reminders" }, { "label": "automated rules automated expiry with forced re-enrollment", "value": "smart-contract-enforce" }, { "label": "Progressive disclosure of credential status with renewal prompts", "value": "progressive-disclosure" } ], "prefillFrom": null, "briefSection": "Credential management", "propertyMapping": { "manual-reminders": { "technologies": [ "Notification System" ], "technologyProperties": { "automationLevel": "low", "complianceEnforcement": "weak", "reminderFrequency": "annual" } }, "smart-contract-enforce": { "technologies": [ "Smart Contract", "Access Control" ], "technologyProperties": { "automationLevel": "high", "complianceEnforced": true, "accessRestriction": true } }, "progressive-disclosure": { "technologies": [ "Verifiable Credentials", "Privacy Engine" ], "technologyProperties": { "selectiveDisclosure": true, "riskBasedRenewal": true, "privacyPreserving": true } } }, "text": "How is safeguarding training renewal tracked and enforced?", "ngoText": "How is safeguarding training renewal tracked and enforced?" }, { "id": "non-compliance-handling", "type": "select", "options": [ { "label": "Suspension of duties pending retraining", "value": "duty-suspension" }, { "label": "Automated access revocation when training lapses", "value": "auto-revocation" }, { "label": "Escalated alerts to safeguarding board with digital evidence", "value": "escalation-alerts" } ], "prefillFrom": null, "briefSection": "Alert and notification", "propertyMapping": { "duty-suspension": { "technologies": [ "Access Control", "Audit Trail" ], "technologyProperties": { "enforcementMechanism": "manual", "documentationRequired": true, "immediateAction": false } }, "auto-revocation": { "technologies": [ "Smart Contract", "Identity Management" ], "technologyProperties": { "enforcementMechanism": "automated", "immediateAction": true, "compensatingControls": true } }, "escalation-alerts": { "technologies": [ "Alert System", "Audit Trail" ], "technologyProperties": { "escalationAutomated": true, "evidenceImmutable": true, "boardNotification": true } } }, "text": "How is non-compliance with safeguarding training handled?", "ngoText": "How is non-compliance with safeguarding training handled?" }, { "id": "confidentiality-requirements", "type": "select", "options": [ { "label": "Centralized records with restricted access control", "value": "centralized-restricted" }, { "label": "Zero-knowledge proofs for verification without disclosure", "value": "zero-knowledge-proof" }, { "label": "Selective disclosure credentials with consent-based sharing", "value": "consent-sharing" } ], "prefillFrom": null, "briefSection": "Credential management", "propertyMapping": { "centralized-restricted": { "technologies": [ "Access Control", "Encryption" ], "technologyProperties": { "dataLocation": "centralized", "accessControl": "role-based", "privacyLevel": "protected" } }, "zero-knowledge-proof": { "technologies": [ "Zero-Knowledge Proof", "Privacy Oracle" ], "technologyProperties": { "disclosureRequired": "minimal", "verificationPossible": true, "privacyMaximized": true } }, "consent-sharing": { "technologies": [ "Verifiable Credentials", "Consent Engine" ], "technologyProperties": { "consentRequired": true, "selectiveDisclosure": true, "auditableSharing": true } } }, "text": "How are confidentiality requirements balanced with verification needs?", "ngoText": "How are confidentiality requirements balanced with verification needs?" } ], "complexityFactors": { "relationships": 2, "operationalChange": 2, "dataCompliance": 3 }, "suggestedCriteria": [ { "id": "SC-COMPLIANCE-PROOF", "name": "Safeguarding Compliance Proof", "description": "The organisation can prove (to regulators, donors, and partners) that all relevant staff have current, valid safeguarding training. Non-compliance carries severe reputational and legal consequences.", "weight": 0.3, "ratingGuide": { "5": "Real-time compliance dashboard showing training status for all staff. Automated proof generation for audits. On-chain attestations with cryptographic verification. Gap analysis identifying non-compliant individuals instantly.", "4": "Compliance reporting with verified training records. Audit-ready reports generated on demand. On-chain records for most training events. Near-real-time status.", "3": "Compliance tracking with periodic reporting. Records verifiable but require manual compilation. Reports generated weekly or monthly.", "2": "Basic training completion records. Manual compliance checking. Reports compiled ad-hoc with significant effort.", "1": "No systematic compliance tracking. Paper records or scattered spreadsheets. Compliance status unknown without extensive manual review." } }, { "id": "SC-ASSESS-INTEGRITY", "name": "Assessment Integrity & Competency Verification", "description": "The system ensures that safeguarding assessments are completed legitimately and that competency is genuinely demonstrated. Rubber-stamped safeguarding training defeats its protective purpose.", "weight": 0.25, "ratingGuide": { "5": "Assessment responses recorded with timestamps and identity verification. Anti-cheating measures (randomised questions, time limits). Competency thresholds enforced. Assessment data anchored on-chain for non-repudiation.", "4": "Assessment completion recorded with identity check. Basic integrity measures. Minimum score requirements. Blockchain-anchored completion records.", "3": "Assessment completion tracked. Self-paced with basic completion verification. Records stored centrally with periodic blockchain anchoring.", "2": "Completion-only tracking (no assessment scoring). Self-attestation of training participation. No integrity measures.", "1": "No assessment component. Training completion assumed based on attendance or self-report." } }, { "id": "SC-RENEWAL-ENFORCE", "name": "Mandatory Renewal & Escalation", "description": "The system enforces mandatory renewal periods and escalate when training lapses. Safeguarding training must be renewed regularly and lapses require immediate action.", "weight": 0.2, "ratingGuide": { "5": "Automated renewal enforcement with configurable validity periods. Escalation chain: reminder \u2192 manager alert \u2192 access restriction \u2192 senior leadership notification. Integration with access control to restrict duties for lapsed staff.", "4": "Automated renewal tracking with manager notifications. Escalation to HR for overdue renewals. Renewal deadlines visible in compliance dashboard.", "3": "Renewal dates tracked with email reminders. Manager notification for overdue training. No automated access restrictions.", "2": "Renewal periods recorded but reminders are manual. No escalation process. Lapses discovered only during periodic audits.", "1": "No renewal tracking. No escalation mechanism. Lapsed training goes undetected." } }, { "id": "SC-CONFID-PROTECT", "name": "Confidentiality & Sensitive Data Handling", "description": "The system protects the confidentiality of safeguarding-related records, including incident reports or disclosure information. Safeguarding data is among the most sensitive information an NGO holds.", "weight": 0.15, "ratingGuide": { "5": "Encrypted storage with strict need-to-know access. Safeguarding officer-only access to sensitive records. On-chain records contain only non-sensitive attestations (completion, expiry). Full GDPR compliance with data retention policies.", "4": "Encrypted storage. Role-based access limiting sensitive data visibility. On-chain records anonymised. Retention policies defined.", "3": "Access-controlled system. Safeguarding records separated from general training data. Basic encryption. Retention policies informal.", "2": "Safeguarding records in general training database. Limited access differentiation. No specific confidentiality measures.", "1": "No confidentiality controls. Safeguarding records accessible to all system users. No data protection considerations." } }, { "id": "SC-CROSS-ORG-RECOG", "name": "Cross-Organisation Recognition", "description": "Safeguarding training is recognised across partner organisations and coalitions. Staff moving between NGOs or working in consortia should not need to retake equivalent training.", "weight": 0.1, "ratingGuide": { "5": "Mutual recognition agreements encoded in system. Credentials accepted by major NGO coalitions and UN agencies. Equivalency mapping between different safeguarding curricula. Verified credentials portable across organisations.", "4": "Credentials recognised by several partner organisations. Partial equivalency mapping. Portable format but acceptance varies.", "3": "Credentials shareable with partners. Recognition at individual organisation discretion. No formal equivalency framework.", "2": "Credentials issued but not designed for cross-organisation use. Partners must contact issuer to verify.", "1": "No portability. Training records locked within issuing organisation. Staff must retake training at each new employer." } } ], "procurement": { "marketMaturity": "mature", "primaryMode": "off-the-shelf", "alternativeModes": [ "rfq" ], "reasoning": "Safeguarding training tracking is part of mature LMS market.", "exampleProductCategories": [ "safeguarding-platform", "lms-platform" ], "partnerChannels": [], "lastReviewed": "2026-05-01" } }, { "id": "UC-J-119", "name": "Security clearance and access management", "category": "J", "subcategory": "Security", "description": "Manage who is cleared to enter which sites and systems, and keep a record of every access decision that cannot be changed.", "bCriteria": [ "B1", "B3", "B7" ], "requiredComponents": [ "credential-management", "audit-trail", "smart-contracts" ], "conditionalComponents": [ "background-check-integration" ], "crossCategoryDependencies": [ "UC-J-121" ], "p2TriggerConditions": { "description": "Activated when P2 shows high security requirements with access control complexity and higher risk levels", "rangeSignals": [ "securityRequirements >=3", "accessControl >=3", "riskLevel >=2", "complianceRequired >=2", "dutyOfCareRequired = true" ] }, "contextFieldsTemplate": [ "clearance_levels", "staff_requiring_clearance", "background_check_frequency", "access_areas_count", "permission_escalation_rules", "review_frequency", "revocation_process" ], "implementationComplexity": "medium", "examples": { "note": "Integrates with HR and access control systems", "references": [ { "name": "International SOS", "url": "https://www.internationalsos.com", "solved": "Security access management for staff working in high-risk locations; reference platform for the operational pattern." }, { "name": "GISF (Global Interagency Security Forum)", "url": "https://gisf.ngo", "solved": "Security framework body whose access-management standards are referenced across humanitarian operations." } ] }, "solutionQuestions": [ { "id": "clearance-levels", "type": "select", "options": [ { "label": "Single access level (all staff identical)", "value": "single-level" }, { "label": "Multi-tier clearance (basic, confidential, secret)", "value": "multi-tier" }, { "label": "Fine-grained permission model with geofenced access control", "value": "fine-grained-geo" } ], "prefillFrom": null, "briefSection": "Access control", "propertyMapping": { "single-level": { "technologies": [ "Access Control" ], "technologyProperties": { "clearanceLevels": 1, "complexity": "low", "differentiation": "none" } }, "multi-tier": { "technologies": [ "Access Control", "Credential Management" ], "technologyProperties": { "clearanceLevels": 3, "complexity": "medium", "roleBasedAccess": true } }, "fine-grained-geo": { "technologies": [ "Smart Contract", "Geofencing Engine" ], "technologyProperties": { "clearanceLevels": "5+", "complexity": "high", "contextAware": true } } }, "text": "How many clearance levels are needed?", "ngoText": "How many clearance levels are needed?" }, { "id": "background-check-depth", "type": "select", "options": [ { "label": "Reference checks only", "value": "references-only" }, { "label": "Standard background check with criminal records", "value": "standard-criminal" }, { "label": "Enhanced check with financial, employment, and health screening", "value": "enhanced-screening" } ], "prefillFrom": null, "briefSection": "Verification mechanism", "propertyMapping": { "references-only": { "technologies": [ "Verification Platform" ], "technologyProperties": { "verificationDepth": "light", "timeTaken": "1-2 weeks", "cost": "low" } }, "standard-criminal": { "technologies": [ "Government Oracle", "Credential Management" ], "technologyProperties": { "verificationDepth": "standard", "timeTaken": "2-4 weeks", "complianceLevel": "medium" } }, "enhanced-screening": { "technologies": [ "Oracle Network", "Privacy Engine" ], "technologyProperties": { "verificationDepth": "deep", "timeTaken": "4-8 weeks", "dataSourcesIntegrated": "5+" } } }, "text": "What depth of background verification is required for your staff?", "ngoText": "What depth of background verification is required for your staff?" }, { "id": "access-control-model", "type": "select", "options": [ { "label": "Role-Based Access Control (RBAC)", "value": "rbac" }, { "label": "Attribute-Based Access Control (ABAC) with automated policy enforcement", "value": "abac-smart" }, { "label": "Verified access with zero-trust architecture", "value": "blockchain-zerotrust" } ], "prefillFrom": null, "briefSection": "Access control", "propertyMapping": { "rbac": { "technologies": [ "Access Control" ], "technologyProperties": { "model": "role-based", "dynamicAdjustment": false, "automationLevel": "medium" } }, "abac-smart": { "technologies": [ "Smart Contract", "Identity Management" ], "technologyProperties": { "model": "attribute-based", "dynamicAdjustment": true, "contextAware": true } }, "blockchain-zerotrust": { "technologies": [ "Distributed Ledger", "Cryptographic Verification" ], "technologyProperties": { "model": "Distributed", "trustModel": "zero-trust", "verification": "continuous" } } }, "text": "Who currently has access to medical records, and how is that controlled?", "ngoText": "Who currently has access to medical records, and how is that controlled?" }, { "id": "permission-escalation", "type": "select", "options": [ { "label": "Manager approval with manual documentation", "value": "manager-approval" }, { "label": "automated rules-enforced escalation with tiered authorization", "value": "smart-escalation" }, { "label": "Risk-aware escalation with continuous re-verification", "value": "risk-aware-escalation" } ], "prefillFrom": null, "briefSection": "Alert and notification", "propertyMapping": { "manager-approval": { "technologies": [ "Workflow Engine" ], "technologyProperties": { "automatedApproval": false, "auditTrail": true, "complianceLogging": true } }, "smart-escalation": { "technologies": [ "Smart Contract", "Multi-Signature" ], "technologyProperties": { "automatedEscalation": true, "multipleSignaturesRequired": true, "timeBasedExpiry": true } }, "risk-aware-escalation": { "technologies": [ "Risk Engine", "Oracle Feed" ], "technologyProperties": { "riskAssessment": "automated", "continuousMonitoring": true, "automatedRevocation": true } } }, "text": "How are higher-level permission requests handled?", "ngoText": "How are higher-level permission requests handled?" }, { "id": "review-cycle", "type": "select", "options": [ { "label": "Annual formal review", "value": "annual-review" }, { "label": "Quarterly risk-based review with automated rules triggers", "value": "quarterly-risk" }, { "label": "Continuous monitoring with real-time re-verification", "value": "continuous-monitoring" } ], "prefillFrom": null, "briefSection": "Compliance verification", "propertyMapping": { "annual-review": { "technologies": [ "Audit Trail" ], "technologyProperties": { "reviewFrequency": "annual", "automatedReminders": true, "documentationRequired": true } }, "quarterly-risk": { "technologies": [ "Smart Contract", "Risk Scoring" ], "technologyProperties": { "reviewFrequency": "quarterly", "riskBased": true, "automatedTriggers": true } }, "continuous-monitoring": { "technologies": [ "Oracle Network", "Blockchain Audit" ], "technologyProperties": { "monitoringContinuous": true, "reVerificationAutomated": true, "alertsInstant": true } } }, "text": "How frequently are clearances reviewed?", "ngoText": "How frequently are clearances reviewed?" } ], "complexityFactors": { "relationships": 2, "operationalChange": 2, "dataCompliance": 3 }, "securityTier": "B", "suggestedCriteria": [ { "id": "SC-CLEARANCE-VERIFY", "name": "Clearance Status Verification", "description": "Authorised parties can instantly verify an individual's current clearance level without exposing underlying investigation details. Security clearance verification must be fast and privacy-preserving.", "weight": 0.3, "ratingGuide": { "5": "Zero-knowledge proof of clearance level without revealing investigation details. Instant verification via DID resolution. Real-time revocation reflected. Supports tiered disclosure \u2014 different verifiers see different detail levels.", "4": "Instant clearance level verification via API or credential presentation. Revocation status current. Investigation details not exposed. Single disclosure level.", "3": "Verification through issuer portal. Clearance level confirmed but with some delay. Revocation status may lag by hours.", "2": "Verification requires contacting security office. Manual confirmation process. Days-long turnaround.", "1": "No digital verification. Paper-based clearance documentation. Verification requires physical document inspection." } }, { "id": "SC-ACCESS-GRANULAR", "name": "Granular Access Control Enforcement", "description": "The system can enforce access restrictions at a granular level based on clearance (physical locations, digital systems, document classifications). Access management must be precise and auditable.", "weight": 0.25, "ratingGuide": { "5": "Smart-contract-enforced access policies. Clearance level automatically gates physical access (badge systems), digital systems (SSO integration), and document access. Policy changes propagate instantly across all enforcement points.", "4": "Clearance-based access enforcement for digital systems and documents. Physical access integration via API. Policy updates within hours.", "3": "Clearance data available to access control systems via export. Manual policy configuration. Physical access managed separately.", "2": "Clearance records inform manual access decisions. No automated enforcement. Security team manually configures each system.", "1": "No integration between clearance records and access systems. Access managed entirely independently." } }, { "id": "SC-AUDIT-TRAIL", "name": "Immutable Audit Trail", "description": "All clearance grants, revocations, access attempts, and permission changes are recorded in a tamper-proof audit trail. Security clearance management requires comprehensive, non-repudiable logging.", "weight": 0.2, "ratingGuide": { "5": "Every event \u2014 grant, revocation, access attempt, denial, escalation, review \u2014 recorded on-chain with timestamps and actor identity. Real-time anomaly detection. Audit reports generated automatically for compliance reviews.", "4": "Clearance lifecycle events recorded on-chain. Access attempts logged. Audit reports available on demand. Basic anomaly flagging.", "3": "Clearance changes recorded on-chain. Access attempts logged in separate system. Manual audit report compilation.", "2": "Clearance changes logged in database. Access attempts partially tracked. No blockchain anchoring. Manual audit process.", "1": "Minimal logging. No systematic record of access attempts or clearance changes. Audit not feasible." } }, { "id": "SC-REVIEW-CYCLE", "name": "Periodic Review & Re-evaluation Workflow", "description": "The system enforces periodic clearance reviews and manage the re-evaluation workflow. Clearances must be periodically reviewed and can be downgraded or revoked based on changing circumstances.", "weight": 0.15, "ratingGuide": { "5": "Automated review scheduling with configurable periods per clearance level. Workflow includes review initiation, assessor assignment, decision recording, and notification. Overdue reviews trigger escalation and temporary access suspension.", "4": "Automated review reminders. Structured workflow for reassessment. Escalation for overdue reviews. No automatic access suspension.", "3": "Review dates tracked with reminders. Semi-structured workflow. Manual escalation for overdue reviews.", "2": "Review dates recorded but tracking is manual. No structured workflow. Reviews often overdue.", "1": "No periodic review mechanism. Clearances granted indefinitely without reassessment." } }, { "id": "SC-BACKGROUND-INT", "name": "Background Check Integration", "description": "The system integrates with background check providers or databases to inform clearance decisions. Manual background checking is slow, error-prone, and does not scale across jurisdictions.", "weight": 0.1, "ratingGuide": { "5": "API integration with multiple background check providers across jurisdictions. Automated screening against sanctions lists and watchlists. Results fed directly into clearance workflow. Continuous monitoring for status changes.", "4": "Integration with at least one background check provider. Sanctions list screening automated. Results linked to clearance records. Periodic rescreening.", "3": "Structured intake of background check results from external providers. Sanctions list checking via manual upload. Results stored alongside clearance records.", "2": "Background check results manually entered. No provider integration. Sanctions screening manual and periodic.", "1": "No integration with background check processes. Clearance decisions made without systematic screening." } } ], "procurement": { "marketMaturity": "mature", "primaryMode": "tender", "alternativeModes": [ "off-the-shelf" ], "reasoning": "Security clearance platforms have mature commercial offerings.", "exampleProductCategories": [ "clearance-management-platform", "access-management-saas" ], "partnerChannels": [], "lastReviewed": "2026-05-01" } }, { "id": "UC-J-120", "name": "Duty of care / staff location tracking in emergencies", "category": "J", "subcategory": "Duty of Care", "description": "Track where staff are during an emergency, and raise an alert automatically when someone has not checked in.", "bCriteria": [ "B1", "B3", "B7" ], "requiredComponents": [ "deployment-tracking", "smart-contracts", "audit-trail" ], "conditionalComponents": [ "alert-system" ], "crossCategoryDependencies": [ "UC-G-098", "UC-J-121" ], "p2TriggerConditions": { "description": "Activated when P2 shows emergency operations with staff safety obligations and duty of care requirements", "rangeSignals": [ "emergencyOperations >=3", "staffSafety >=3", "dutyOfCareRequired = true", "accessControl >=3" ] }, "contextFieldsTemplate": [ "conflict_exposure_level", "disaster_risk_level", "staff_count_at_risk", "geographic_hotspots", "check_in_frequency", "alert_escalation_rules", "privacy_vs_safety_balance" ], "implementationComplexity": "high", "examples": { "note": "Integration with security and emergency response systems", "references": [ { "name": "International SOS", "url": "https://www.internationalsos.com", "solved": "Reference platform for staff location tracking and duty-of-care response in emergencies." }, { "name": "ICRC Duty of Care", "url": "https://www.icrc.org", "solved": "Duty-of-care framework including staff location and emergency-response protocols." }, { "name": "InsideNGO Duty of Care", "url": "https://www.humentum.org", "solved": "Humentum (formerly InsideNGO) sector framework for duty-of-care implementation across INGOs." } ] }, "solutionQuestions": [ { "id": "alert-escalation", "type": "select", "options": [ { "label": "Manual escalation through phone tree", "value": "manual-phonetree" }, { "label": "automated rules-triggered automated alerts to command center", "value": "auto-alerts" }, { "label": "AI-powered risk assessment with context-aware escalation", "value": "ai-risk-escalation" } ], "prefillFrom": null, "briefSection": "Alert and notification", "propertyMapping": { "manual-phonetree": { "technologies": [ "Communication System" ], "technologyProperties": { "automationLevel": "low", "responseTime": "5-15 minutes", "reliability": "human-dependent" } }, "auto-alerts": { "technologies": [ "Smart Contract", "Notification Engine" ], "technologyProperties": { "responseTime": "seconds", "automatedEscalation": true, "multiChannelAlert": true } }, "ai-risk-escalation": { "technologies": [ "AI Risk Engine", "Smart Contract" ], "technologyProperties": { "riskAssessment": "real-time", "contextAware": true, "escalationOptimized": true } } }, "text": "How are emergency alerts currently escalated?", "ngoText": "How are emergency alerts currently escalated?" }, { "id": "privacy-balance", "type": "select", "options": [ { "label": "Opt-in location tracking during emergencies only", "value": "opt-in-emergencies" }, { "label": "Geofenced monitoring with selective disclosure", "value": "geofence-selective" }, { "label": "privacy-preserving verification verification (location proof without exact coordinates)", "value": "zkp-location" } ], "prefillFrom": null, "briefSection": "Access control", "propertyMapping": { "opt-in-emergencies": { "technologies": [ "Consent Engine", "Mobile App" ], "technologyProperties": { "consentRequired": true, "emergencyOnly": true, "locationRetention": "temporary" } }, "geofence-selective": { "technologies": [ "Geofencing Engine", "Privacy Oracle" ], "technologyProperties": { "granularity": "area-based", "selectiveDisclosure": true, "realTimeOptional": false } }, "zkp-location": { "technologies": [ "Zero-Knowledge Proof", "Smart Contract" ], "technologyProperties": { "exactCoordinates": false, "proofOfPresence": true, "privacyMaximized": true } } }, "text": "How is the privacy vs. safety balance achieved?", "ngoText": "How is the privacy vs. safety balance achieved?" }, { "id": "emergency-protocol", "type": "select", "options": [ { "label": "Manual check-in with supervisor confirmation", "value": "manual-checkin" }, { "label": "Automated safe/unsafe status via digital ledger with multi-source verification", "value": "auto-status-verify" }, { "label": "distributed autonomous duty-of-care contract with medical/security integration", "value": "dao-duty-care" } ], "prefillFrom": null, "briefSection": "Compliance verification", "propertyMapping": { "manual-checkin": { "technologies": [ "Communication System" ], "technologyProperties": { "responsiblePerson": "supervisor", "timeRequired": "10-20 minutes", "documentationManual": true } }, "auto-status-verify": { "technologies": [ "Smart Contract", "Multi-Oracle" ], "technologyProperties": { "automatedStatus": true, "multiSourceVerification": true, "immutableRecord": true } }, "dao-duty-care": { "technologies": [ "DAO Smart Contract", "Emergency Oracle" ], "technologyProperties": { "medicalIntegration": true, "securityIntegration": true, "automatedResponse": true } } }, "text": "What is your current emergency procedure for verifying duty of care?", "ngoText": "What is your current emergency procedure for verifying duty of care?" }, { "id": "geographic-coverage", "type": "select", "options": [ { "label": "Urban areas with reliable mobile and internet coverage", "value": "urban-areas-with-reliable-mobile-and-int" }, { "label": "Remote areas where internet connectivity is unreliable or intermittent", "value": "remote-areas-where-internet-connectivity" }, { "label": "High-risk zones where normal communications infrastructure may be unavailable", "value": "high-risk-zones-where-normal-communicati" }, { "label": "Mix of all the above across different deployment locations", "value": "mix-of-all-the-above-across-different-de" } ], "prefillFrom": null, "briefSection": "Infrastructure requirements", "propertyMapping": { "urban-coverage": { "technologies": [ "GPS Oracle" ], "technologyProperties": { "coverage": "4G/5G", "redundancy": "single", "offlineFallback": "limited" } }, "remote-mesh": { "technologies": [ "Mesh Network", "Offline Sync" ], "technologyProperties": { "coverage": "sparse", "redundancy": "multi-hop", "dataSync": "eventual-consistency" } }, "highrisk-satellite": { "technologies": [ "Satellite Communication", "Edge Computing" ], "technologyProperties": { "coverage": "global", "redundancy": "satellite+cellular", "latency": "low" } } }, "text": "What geographic areas and connectivity scenarios are covered?", "ngoText": "What geographic areas and connectivity scenarios are covered?", "question": "What geographic areas and connectivity conditions do you need to cover?" }, { "id": "coverage-requirements", "type": "select", "options": [ { "label": "Best effort, no guaranteed SLA", "value": "best-effort" }, { "label": "99% coverage with 5-minute response time SLA", "value": "99-percent-sla" }, { "label": "99.9% coverage with sub-minute alerts and automated escalation", "value": "999-percent-sla" } ], "prefillFrom": null, "briefSection": "Infrastructure requirements", "propertyMapping": { "best-effort": { "technologies": [ "Tracking System" ], "technologyProperties": { "slaRequired": false, "coverageTarget": "70%+", "responseTime": "unknown" } }, "99-percent-sla": { "technologies": [ "Monitored Tracking", "SLA Enforcement" ], "technologyProperties": { "coverageTarget": "99%", "responseTimeSLA": "5min", "complianceMonitored": true } }, "999-percent-sla": { "technologies": [ "Redundant Systems", "Smart Contract SLA" ], "technologyProperties": { "coverageTarget": "99.9%", "responseTimeSLA": "<1min", "automatedEscalation": true } } }, "text": "What coverage percentage and response time are required?", "ngoText": "What coverage percentage and response time are required?" }, { "id": "audit-trail-approach", "type": "select", "options": [ { "label": "Full permanent audit trail: every action logged digitally", "value": "full-immutable" }, { "label": "Key events only: milestones and approvals logged digital", "value": "key-events" }, { "label": "Hybrid: key details logged digitally, full records stored separately with tamper-proof links", "value": "hybrid" }, { "label": "Not sure, need guidance on audit trail design", "value": "guidance-needed" } ], "propertyMapping": { "full-immutable": { "technologies": [ "Immutable audit trail", "On-chain event logging", "Audit trail verification service" ], "technologyProperties": { "auditGranularity": "Every action", "storageApproach": "Full Digital logging", "tamperEvidence": "Cryptographic hash chain" } }, "key-events": { "technologies": [ "Milestone-based audit trail", "Approval chain logger", "Audit trail verification service" ], "technologyProperties": { "auditGranularity": "Key milestones and approvals only", "storageApproach": "Selective Digital logging", "tamperEvidence": "Merkle root anchoring" } }, "hybrid": { "technologies": [ "Hybrid audit trail system", "Off-chain storage with hash anchoring", "Audit trail verification service" ], "technologyProperties": { "auditGranularity": "Metadata Digital, full records off-chain", "storageApproach": "Decentralised/off-chain storage with digital hash proofs", "tamperEvidence": "Hash anchoring to blockchain" } }, "guidance-needed": { "technologies": [ "Audit trail framework", "Audit trail verification service" ], "technologyProperties": { "auditGranularity": "To be determined during solution design", "storageApproach": "To be determined", "tamperEvidence": "To be determined" } } }, "prefillFrom": null, "briefSection": "Audit and evidence", "text": "What level of record-keeping and evidence trail do you need for this process?", "ngoText": "What level of record-keeping and evidence trail do you need for this process?" } ], "complexityFactors": { "relationships": 2, "operationalChange": 3, "dataCompliance": 4 }, "securityTier": "B", "suggestedCriteria": [ { "id": "SC-REALTIME-LOCATE", "name": "Real-Time Location Awareness", "description": "The system can determine staff locations during an emergency with sufficient accuracy and timeliness for duty-of-care response. Minutes matter in crisis situations. Delayed or inaccurate location data can cost lives.", "weight": 0.3, "ratingGuide": { "5": "Real-time staff location tracking via mobile app with GPS. Last-known-location cached for offline scenarios. Location accuracy within 100m. Emergency check-in triggers within minutes. Blockchain-anchored location attestations for accountability.", "4": "Near-real-time location (within 30 minutes). Mobile check-in system. Last-known-location stored. Location accuracy within 1km in most areas.", "3": "Periodic location updates (daily check-in). Last deployment location known. Emergency roll-call initiated manually. Hours-level accuracy.", "2": "Deployment location on record but not real-time. Staff must self-report during emergencies. Significant gaps in coverage.", "1": "No location tracking capability. Staff locations unknown during emergencies. Manual phone tree only." } }, { "id": "SC-PRIVACY-BALANCE", "name": "Privacy vs. Safety Balance", "description": "The system balances staff location privacy with duty-of-care obligations. Continuous surveillance erodes trust, but organisations have legal obligations to protect staff in high-risk environments.", "weight": 0.25, "ratingGuide": { "5": "Tiered privacy model: normal mode (no tracking), elevated mode (periodic check-in), emergency mode (continuous tracking). Staff consent framework with clear opt-in/opt-out by context. Privacy impact assessment documented. On-chain audit of who accessed location data and when.", "4": "Context-dependent tracking with staff awareness. Emergency override clearly defined. Staff can see who viewed their location. Consent-based approach.", "3": "Basic privacy controls. Tracking active during field deployments. Staff informed but limited control. Access logs available on request.", "2": "Continuous tracking with minimal privacy controls. Staff aware but cannot limit access. No audit of location data access.", "1": "Surveillance-style tracking with no privacy considerations. Staff not informed of data use. No access controls on location data." } }, { "id": "SC-ALERT-ESCALATION", "name": "Automated Alert & Escalation", "description": "The system generates automated alerts when staff may be at risk, and escalate appropriately through the duty-of-care chain. Manual monitoring fails at scale and during out-of-hours crises.", "weight": 0.2, "ratingGuide": { "5": "Geofence-triggered alerts for danger zones. Missed check-in escalation: staff \u2192 line manager \u2192 security team \u2192 senior leadership. Integration with external crisis databases (UNDSS, travel advisories). Smart-contract-enforced escalation timelines.", "4": "Automated alerts for missed check-ins. Multi-level escalation chain. Integration with at least one crisis data source. Configurable alert thresholds.", "3": "Automated missed check-in alerts to security team. Basic escalation. Manual crisis data monitoring. Email/SMS notifications.", "2": "Manual monitoring with alert capability. Single-level notification. No integration with external crisis data.", "1": "No automated alerting. Entirely manual monitoring. Escalation depends on individual initiative." } }, { "id": "SC-OFFLINE-RESILIENCE", "name": "Offline & Low-Connectivity Resilience", "description": "The system functions in environments with poor or no internet connectivity. Emergency situations often coincide with infrastructure disruption. The system must work when it is needed most.", "weight": 0.15, "ratingGuide": { "5": "Full offline capability with local data storage. SMS/satellite fallback for check-ins. Automatic sync when connectivity resumes. Mesh networking between nearby devices. Blockchain anchoring queued for reconnection.", "4": "Core functions offline. SMS check-in fallback. Data cached locally with sync on reconnection. No mesh networking.", "3": "Limited offline capability. SMS-based check-in available. Data sync requires manual trigger. Some features unavailable offline.", "2": "Primarily online. Basic SMS fallback for emergencies only. Significant feature loss without internet.", "1": "Online-only. No offline capability. No fallback communication channels. System useless during connectivity disruptions." } }, { "id": "SC-ACCOUNTABILITY-RECORD", "name": "Duty-of-Care Accountability Record", "description": "The system creates an immutable record of all duty-of-care actions taken during emergencies. Post-incident review and legal liability require proof of what was done, when, and by whom.", "weight": 0.1, "ratingGuide": { "5": "Complete on-chain record of every alert, response action, communication attempt, and decision during emergencies. Timestamped, attributed, and tamper-proof. Post-incident reports auto-generated. Meets legal evidentiary standards.", "4": "Key actions and decisions recorded on-chain. Communications logged. Post-incident reporting with verified data. Good evidentiary value.", "3": "Actions logged in central system with periodic blockchain anchoring. Manual post-incident report compilation from logs.", "2": "Basic incident logging. Records editable. Post-incident review relies on personal recollections supplemented by partial logs.", "1": "No systematic record of emergency response actions. Post-incident review based entirely on memory and ad-hoc communications." } } ], "procurement": { "marketMaturity": "emerging", "primaryMode": "tender", "alternativeModes": [ "integrator-led" ], "reasoning": "Duty of care location tracking has growing product space.", "exampleProductCategories": [ "duty-of-care-platform", "location-tracking-rails" ], "partnerChannels": [], "lastReviewed": "2026-05-01" } }, { "id": "UC-J-121", "name": "Contractor and consultant verification", "category": "J", "subcategory": "Vendor Management", "description": "Check contractors' and consultants' qualifications and track record, including problems known to other organisations, before you engage them.", "bCriteria": [ "B1", "B3", "B6" ], "requiredComponents": [ "credential-management", "verification-platform", "audit-trail" ], "conditionalComponents": [ "smart-contracts", "background-check-integration" ], "crossCategoryDependencies": [ "UC-J-121" ], "p2TriggerConditions": { "description": "Activated when P2 shows significant contractor engagement with performance tracking needs and compliance requirements", "rangeSignals": [ "contractorEngagement >=3", "performanceTracking >=2", "complianceRequired >=2", "accountabilityRequired >=2" ] }, "contextFieldsTemplate": [ "contractor_types", "annual_contractor_count", "qualification_requirements", "performance_metrics_tracked", "compliance_standards", "reference_checking_process", "background_verification_depth" ], "implementationComplexity": "medium", "examples": { "note": "Vendor management and performance tracking", "references": [ { "name": "SAP Ariba", "url": "https://www.ariba.com", "solved": "Enterprise contractor onboarding and verification platform widely used by larger NGOs." }, { "name": "Misconduct Disclosure Scheme", "url": "https://www.schr.info/the-misconduct-disclosure-scheme", "solved": "Inter-agency disclosure scheme covering contractor and consultant misconduct records alongside employee records." }, { "name": "GuideStar / Candid", "url": "https://candid.org", "solved": "Reference platform for verifying non-profit contractor legitimacy and capacity." } ] }, "solutionQuestions": [ { "id": "verification-depth", "type": "select", "options": [ { "label": "Basic portfolio and reference check", "value": "basic-portfolio" }, { "label": "Digitally verified qualifications and past client attestations", "value": "blockchain-verified" }, { "label": "Deep verification with background check and compliance screening", "value": "deep-compliance" } ], "prefillFrom": null, "briefSection": "Verification mechanism", "propertyMapping": { "basic-portfolio": { "technologies": [ "Verification Platform" ], "technologyProperties": { "verificationDepth": "light", "timeTaken": "1 week", "cost": "low" } }, "blockchain-verified": { "technologies": [ "Verifiable Credentials", "Client Attestation" ], "technologyProperties": { "verificationDepth": "medium", "timeTaken": "2 weeks", "trustScore": "automated" } }, "deep-compliance": { "technologies": [ "Government Oracle", "Compliance Engine" ], "technologyProperties": { "verificationDepth": "deep", "timeTaken": "3-4 weeks", "complianceLevel": "high" } } }, "text": "What depth of contractor verification is required?", "ngoText": "What depth of contractor verification is required?" }, { "id": "qualification-tracking", "type": "select", "options": [ { "label": "Static documentation files", "value": "static-docs" }, { "label": "Digital credential wallet with continuous re-verification", "value": "blockchain-wallet" }, { "label": "Automated qualification lifecycle management", "value": "smart-contract-lifecycle" } ], "prefillFrom": null, "briefSection": "Credential management", "propertyMapping": { "static-docs": { "technologies": [ "Document Management" ], "technologyProperties": { "automatedUpdates": false, "manualRefresh": "annual", "currentnessRisk": "high" } }, "blockchain-wallet": { "technologies": [ "Verifiable Credentials", "Credential Wallet" ], "technologyProperties": { "automatedUpdates": true, "expiryAlerts": true, "continuousSync": true } }, "smart-contract-lifecycle": { "technologies": [ "Smart Contract", "Credential Management" ], "technologyProperties": { "lifecycleAutomated": true, "renewalEnforced": true, "accessControl": "conditional" } } }, "text": "What contractor qualifications require periodic renewal and at what frequency?", "ngoText": "What contractor qualifications require periodic renewal and at what frequency?" }, { "id": "performance-history", "type": "select", "options": [ { "label": "Spreadsheet or document-based performance records", "value": "spreadsheet-or-document-based-performanc" }, { "label": "Formal performance management system with ratings and reviews", "value": "formal-performance-management-system-wit" }, { "label": "Project-based assessment (cost, quality, timeliness, compliance) recorded per engagement", "value": "project-based-assessment-cost-quality-ti" }, { "label": "No formal tracking, performance assessed informally", "value": "no-formal-tracking-performance-assessed-" }, { "label": "Not sure, need to establish a process", "value": "not-sure-need-to-establish-a-process" } ], "prefillFrom": null, "briefSection": "Reporting and audit", "propertyMapping": { "spreadsheet-records": { "technologies": [ "Document Management" ], "technologyProperties": { "dataIntegrity": "manual", "queryability": "limited", "audit": "manual" } }, "blockchain-ledger": { "technologies": [ "Distributed Ledger", "Rating System" ], "technologyProperties": { "dataImmutable": true, "clientRatings": true, "reputationScore": "automated" } }, "smart-reputation": { "technologies": [ "Smart Contract", "Oracle Network" ], "technologyProperties": { "reputationDynamic": true, "multiSourceData": true, "automatedAdjustment": true } } }, "text": "What contractor performance metrics do you track? (cost, quality, timeliness, compliance?)", "ngoText": "What contractor performance metrics do you track? (cost, quality, timeliness, compliance?)", "question": "How do you currently track contractor and consultant performance?" }, { "id": "reference-checking", "type": "select", "options": [ { "label": "Manual phone/email reference checks", "value": "manual-checks" }, { "label": "Digitally signed client attestations", "value": "blockchain-attest" }, { "label": "Distributed verification network with peer-reviewed ratings", "value": "decentralized-consensus" } ], "prefillFrom": null, "briefSection": "Verification mechanism", "propertyMapping": { "manual-checks": { "technologies": [ "Communication System" ], "technologyProperties": { "automationLevel": "low", "timeRequired": "3-5 days", "reliability": "variable" } }, "blockchain-attest": { "technologies": [ "Verifiable Credentials", "Digital Signature" ], "technologyProperties": { "nonRepudiation": true, "immutable": true, "instantVerification": true } }, "decentralized-consensus": { "technologies": [ "DAO", "Consensus Mechanism" ], "technologyProperties": { "transparentVerification": true, "collusion": "resistant", "ratingBias": "mitigated" } } }, "text": "Do you verify contractor references, and how formally? (informal calls vs formal attestations?)", "ngoText": "Do you verify contractor references, and how formally? (informal calls vs formal attestations?)" }, { "id": "contractor-staff-count", "type": "select", "options": [ { "label": "Under 50", "value": "small" }, { "label": "50\u2013200", "value": "medium" }, { "label": "200\u20131,000", "value": "large" }, { "label": "Over 1,000", "value": "enterprise" } ], "propertyMapping": { "small": { "technologies": [ "Simple record system" ], "technologyProperties": { "scalability": "Standard", "selfService": "Optional" } }, "medium": { "technologies": [ "HR integration platform" ], "technologyProperties": { "scalability": "Standard", "selfService": "Recommended" } }, "large": { "technologies": [ "Scalable workforce platform", "Self-service portal" ], "technologyProperties": { "scalability": "High", "selfService": "Required" } }, "enterprise": { "technologies": [ "Enterprise workforce platform", "Self-service portal", "API-first" ], "technologyProperties": { "scalability": "Enterprise", "selfService": "Required" } } }, "prefillFrom": null, "briefSection": "Infrastructure requirements", "text": "How many staff or individuals need to be tracked in contractor verification?", "ngoText": "How many staff or individuals need to be tracked in contractor verification?" }, { "id": "contractor-jurisdictions", "type": "select", "options": [ { "label": "Single country", "value": "single" }, { "label": "2\u20135 countries", "value": "few" }, { "label": "6\u201315 countries", "value": "many" }, { "label": "Over 15 countries", "value": "global" } ], "propertyMapping": { "single": { "technologies": [], "technologyProperties": { "jurisdictionalComplexity": "Low", "dataResidency": "Single" } }, "few": { "technologies": [ "Multi-jurisdiction compliance" ], "technologyProperties": { "jurisdictionalComplexity": "Medium", "dataResidency": "Multi-region" } }, "many": { "technologies": [ "Multi-jurisdiction compliance", "Data residency management" ], "technologyProperties": { "jurisdictionalComplexity": "High", "dataResidency": "Distributed" } }, "global": { "technologies": [ "Global compliance framework", "Data residency management", "Multi-language support" ], "technologyProperties": { "jurisdictionalComplexity": "Very high", "dataResidency": "Global distributed" } } }, "prefillFrom": "P0-orgSize", "briefSection": "Compliance and jurisdictions", "text": "How many jurisdictions or countries does contractor engagement span?", "ngoText": "How many jurisdictions or countries does contractor engagement span?" }, { "id": "audit-trail-approach", "type": "select", "options": [ { "label": "Full permanent audit trail: every action logged digitally", "value": "full-immutable" }, { "label": "Key events only: milestones and approvals logged digital", "value": "key-events" }, { "label": "Hybrid: key details logged digitally, full records stored separately with tamper-proof links", "value": "hybrid" }, { "label": "Not sure, need guidance on audit trail design", "value": "guidance-needed" } ], "propertyMapping": { "full-immutable": { "technologies": [ "Immutable audit trail", "On-chain event logging", "Audit trail verification service" ], "technologyProperties": { "auditGranularity": "Every action", "storageApproach": "Full Digital logging", "tamperEvidence": "Cryptographic hash chain" } }, "key-events": { "technologies": [ "Milestone-based audit trail", "Approval chain logger", "Audit trail verification service" ], "technologyProperties": { "auditGranularity": "Key milestones and approvals only", "storageApproach": "Selective Digital logging", "tamperEvidence": "Merkle root anchoring" } }, "hybrid": { "technologies": [ "Hybrid audit trail system", "Off-chain storage with hash anchoring", "Audit trail verification service" ], "technologyProperties": { "auditGranularity": "Metadata Digital, full records off-chain", "storageApproach": "Decentralised/off-chain storage with digital hash proofs", "tamperEvidence": "Hash anchoring to blockchain" } }, "guidance-needed": { "technologies": [ "Audit trail framework", "Audit trail verification service" ], "technologyProperties": { "auditGranularity": "To be determined during solution design", "storageApproach": "To be determined", "tamperEvidence": "To be determined" } } }, "prefillFrom": null, "briefSection": "Audit and evidence", "text": "What level of record-keeping and evidence trail do you need for this process?", "ngoText": "What level of record-keeping and evidence trail do you need for this process?" } ], "complexityFactors": { "relationships": 2, "operationalChange": 2, "dataCompliance": 2 }, "suggestedCriteria": [ { "id": "SC-QUAL-VERIFY", "name": "Qualification & Credential Verification", "description": "Contractor qualifications can be verified independently without relying on self-reported claims. Fraudulent credentials are a significant risk in contractor procurement, especially across jurisdictions.", "weight": 0.3, "ratingGuide": { "5": "Real-time verification of contractor credentials against issuing institutions via W3C VC or equivalent. Automated checks at onboarding and periodic re-verification. Supports multi-jurisdiction credential frameworks. Fraud detection for suspicious credentials.", "4": "Credential verification against registries or issuer APIs. Automated onboarding checks. Supports major credential formats. Manual re-verification at contract renewal.", "3": "Credential verification through issuer portal lookups. Semi-automated onboarding check. Limited to specific jurisdictions or credential types.", "2": "Credential copies collected and reviewed manually. Spot-check verification by contacting issuers. No systematic re-verification.", "1": "Self-reported credentials accepted at face value. No verification process. Reliance on references only." } }, { "id": "SC-PERF-HISTORY", "name": "Performance History & Reputation", "description": "The system maintains a verifiable record of contractor performance across engagements. Past performance is the strongest predictor of future delivery, but contractor performance data is often siloed within individual organisations.", "weight": 0.25, "ratingGuide": { "5": "On-chain performance ratings from multiple client organisations. Standardised evaluation framework. Contractors can present verified track record to new clients. Privacy-preserving \u2014 contractors consent to which ratings are visible. Dispute resolution mechanism.", "4": "Performance records from current organisation anchored on-chain. Contractors can request portable performance credentials. Ratings verified and tamper-proof.", "3": "Internal performance tracking with blockchain-anchored summaries. Not portable across organisations. Contractors can reference but not independently prove performance.", "2": "Performance tracked in procurement system. No blockchain anchoring. Records available internally only. Manual reference process.", "1": "No systematic performance tracking. Ad-hoc feedback. No historical record. Each engagement starts from zero." } }, { "id": "SC-COMPLIANCE-SCREEN", "name": "Compliance & Due Diligence Screening", "description": "The system automates contractor compliance checks including sanctions screening, conflict-of-interest detection, and regulatory compliance. NGOs face donor and regulatory requirements for contractor due diligence.", "weight": 0.2, "ratingGuide": { "5": "Automated sanctions list screening (OFAC, UN, EU). Conflict-of-interest checks against staff and board. Beneficial ownership verification. Continuous monitoring for status changes. Compliance attestations on-chain.", "4": "Automated sanctions screening against major lists. Basic conflict-of-interest checks. Compliance records on-chain. Periodic re-screening.", "3": "Sanctions screening at onboarding via manual process or basic tool. Conflict-of-interest self-declaration. Compliance records in central database.", "2": "Manual sanctions list checking at onboarding only. Self-declared compliance. No ongoing monitoring.", "1": "No compliance screening. Contractors onboarded without due diligence. No sanctions or conflict-of-interest checks." } }, { "id": "SC-CONTRACT-LIFECYCLE", "name": "Contract Lifecycle Transparency", "description": "The system provides transparent, auditable records of the full contractor lifecycle, from procurement through delivery to payment. Transparency in contractor management reduces fraud and supports donor accountability.", "weight": 0.15, "ratingGuide": { "5": "Complete procurement-to-payment lifecycle on-chain: tender, selection rationale, contract terms, milestone delivery, payment triggers. Smart contract-enforced milestone payments. Full audit trail for donor reporting.", "4": "Key lifecycle events recorded on-chain: contract award, deliverables, payments. Audit trail for major decisions. Semi-automated milestone tracking.", "3": "Contract and payment records stored centrally with blockchain anchoring at key points. Manual milestone tracking. Audit reports compiled from multiple sources.", "2": "Contract documents stored digitally. Payment records in finance system. No integrated lifecycle view. Manual audit compilation.", "1": "Paper-based or fragmented digital records. No integrated contractor lifecycle view. Audit requires extensive manual effort." } }, { "id": "SC-MULTI-JURIS", "name": "Multi-Jurisdiction Contractor Management", "description": "The system can handle contractors operating across multiple legal jurisdictions with varying regulatory requirements. NGOs frequently engage contractors across borders where labour laws, tax obligations, and compliance requirements differ.", "weight": 0.1, "ratingGuide": { "5": "Jurisdiction-aware compliance engine. Automatically applies relevant regulations per contractor location. Supports multi-currency payment records. Tax documentation requirements flagged per jurisdiction. Cross-border credential verification.", "4": "Jurisdiction-specific compliance templates for major operating regions. Multi-currency support. Manual regulatory requirement lookups supplemented by system guidance.", "3": "Basic jurisdiction tagging. Compliance requirements documented but not enforced by system. Single-currency records with manual conversion.", "2": "Single-jurisdiction focus. Other jurisdictions handled as exceptions. Manual compliance for non-primary jurisdictions.", "1": "No jurisdiction awareness. Single regulatory framework assumed. Cross-border contractor management entirely manual." } } ], "procurement": { "marketMaturity": "mature", "primaryMode": "off-the-shelf", "alternativeModes": [ "rfq" ], "reasoning": "Contractor and consultant verification is mature vendor management SaaS.", "exampleProductCategories": [ "vendor-management-saas", "contractor-verification-platform" ], "partnerChannels": [], "lastReviewed": "2026-05-01" } }, { "id": "UC-E-080", "name": "Board decision recording and verification", "category": "E", "subcategory": "Board Governance", "description": "Keep a record of board decisions and who approved them that cannot be changed later, for trustees in different countries and for auditors.", "bCriteria": [ "B3", "B6", "B7" ], "requiredComponents": [ { "component": "identity-verification", "description": "Verifiable-credential identities for directors / trustees, tying each vote to a specific person without exposing personal data" }, { "component": "audit-mechanism", "description": "Tamper-evident log of motions, votes, rationales, and recusal records" }, { "component": "smart-contracts", "description": "Quorum, super-majority, and conflict-recusal rules executed programmatically" }, { "component": "consent-management", "description": "Selective disclosure of confidential decisions to authorised parties (donors, regulators, subsequent boards)" } ], "conditionalComponents": [ { "component": "privacy-tech", "condition": "If commercially sensitive or safeguarding-related votes need to remain confidential from non-members" }, { "component": "multi-sig", "condition": "If high-materiality decisions (CEO appointment, spend > threshold) require multi-party cryptographic sign-off" } ], "crossCategoryDependencies": [ "UC-E-082 for Conflict-of-Interest declarations that feed recusal logic", "UC-E-068 for consortium voting patterns that extend beyond a single board", "UC-C-048 for linked audit-trail maintenance" ], "p2TriggerConditions": { "description": "Activated when governance maturity + multi-jurisdiction trustees + donor / regulator audit demand combine.", "rangeSignals": [ "trusteeCount >= 5", "multiJurisdictionBoard == true", "donorAuditRequests >= annual" ] }, "contextFieldsTemplate": [ { "field": "trusteeCount", "source": "P0 Q9", "description": "Number of directors / trustees" }, { "field": "meetingFrequency", "source": "P2 CatE", "description": "Board meeting cadence" }, { "field": "decisionVolume", "source": "P2 CatE", "description": "Number of formal decisions per cycle" }, { "field": "confidentialityTier", "source": "P0 Q20-21", "description": "Regulatory and donor confidentiality obligations" } ], "implementationComplexity": "medium", "examples": { "note": "Board-attested governance records \u2014 emerging from DAO tooling applied to traditional NGO boards.", "references": [ { "name": "Aragon Govern", "url": "https://aragon.org/", "solved": "On-chain proposal, vote, and execution with cryptographic director attestation; adapted by charity pilots for trustee sign-off" }, { "name": "Microsoft ION DIDs for corporate governance", "url": "https://identity.foundation/ion/", "solved": "Decentralised identifiers for director identity anchoring across multi-jurisdiction boards" }, { "name": "UN CEB Digital Cooperation Office", "url": "https://unsceb.org/digital-cooperation", "solved": "UN system-wide governance records with cryptographic attestation pilots" } ] }, "solutionQuestions": [ { "id": "board-attestation-depth", "type": "select", "options": [ { "label": "Simple signed minutes (one signer per meeting)", "value": "simple" }, { "label": "Per-director vote recording (each director signs their vote)", "value": "per-director" }, { "label": "Full smart-contract quorum with auto-executed consequences", "value": "smart-contract" } ], "propertyMapping": { "simple": { "technologies": [ "Hash-anchored meeting-minute service", "Single-signer DID" ], "technologyProperties": { "attestationModel": "Single cryptographic signature anchoring the minute", "complexity": "low" } }, "per-director": { "technologies": [ "Per-director verifiable-credential platform", "Vote-capture DApp", "Hash-anchoring service" ], "technologyProperties": { "attestationModel": "Per-director DID signature per vote", "complexity": "medium" } }, "smart-contract": { "technologies": [ "Governance smart-contract framework", "Per-director DID", "Oracle for off-chain triggers" ], "technologyProperties": { "attestationModel": "Programmatic quorum and execution", "complexity": "high" } } }, "prefillFrom": null, "briefSection": "Governance model", "text": "What level of director attestation do you need for recorded decisions?", "ngoText": "What level of director attestation do you need for recorded decisions?" }, { "id": "board-confidentiality", "type": "select", "options": [ { "label": "Decisions are public once passed", "value": "public" }, { "label": "Decisions public; rationales confidential to directors + auditors", "value": "hybrid" }, { "label": "All content confidential (HR, safeguarding, commercial)", "value": "confidential" } ], "propertyMapping": { "public": { "technologies": [ "Public blockchain anchor" ], "technologyProperties": { "confidentiality": "Public ledger", "privacy": "none required" } }, "hybrid": { "technologies": [ "Hybrid on-chain decision + off-chain encrypted rationale store", "Selective-disclosure credential scheme" ], "technologyProperties": { "confidentiality": "Hybrid", "privacy": "Selective disclosure" } }, "confidential": { "technologies": [ "Private / permissioned ledger", "Zero-knowledge proof attestation" ], "technologyProperties": { "confidentiality": "Full", "privacy": "ZK proofs for audit demonstration" } } }, "prefillFrom": null, "briefSection": "Confidentiality", "text": "What confidentiality requirements apply to board decisions?", "ngoText": "What confidentiality requirements apply to board decisions?" }, { "id": "board-jurisdictions", "type": "select", "options": [ { "label": "Single jurisdiction: one e-signature regime", "value": "single" }, { "label": "2-5 jurisdictions", "value": "multi-small" }, { "label": "6+ jurisdictions with complex cross-border rules", "value": "multi-large" } ], "propertyMapping": { "single": { "technologies": [ "Standard DID framework" ], "technologyProperties": { "legalContext": "Single-regime", "eSignatureCompliance": "eIDAS or equivalent" } }, "multi-small": { "technologies": [ "Multi-jurisdiction compatible DID framework", "eIDAS / UETA / UNCITRAL-aligned signing layer" ], "technologyProperties": { "legalContext": "Multi-regime", "eSignatureCompliance": "Multi-scheme" } }, "multi-large": { "technologies": [ "Multi-jurisdiction DID framework", "Per-jurisdiction compliance adapter", "Legal-opinion registry" ], "technologyProperties": { "legalContext": "Global", "eSignatureCompliance": "Complex multi-scheme" } } }, "prefillFrom": null, "briefSection": "Regulatory context", "text": "Are directors in multiple legal jurisdictions with different attestation / e-signature laws?", "ngoText": "Are directors in multiple legal jurisdictions with different attestation / e-signature laws?" }, { "id": "board-auto-consequences", "type": "select", "options": [ { "label": "No, decisions are recorded; execution is manual", "value": "manual" }, { "label": "Some decisions trigger specific downstream actions (e.g., payments above threshold)", "value": "selective" }, { "label": "Most decisions execute programmatically (DAO-style governance)", "value": "programmatic" } ], "propertyMapping": { "manual": { "technologies": [ "Record-only ledger" ], "technologyProperties": { "execution": "Manual" } }, "selective": { "technologies": [ "Smart-contract trigger layer", "Payment rail integration" ], "technologyProperties": { "execution": "Selective automation", "triggers": "Thresholded" } }, "programmatic": { "technologies": [ "Governance smart-contract framework", "Multi-rail execution layer", "Oracle integration" ], "technologyProperties": { "execution": "Programmatic", "governance": "DAO-analog" } } }, "prefillFrom": null, "briefSection": "Decision execution", "text": "Do board decisions need to trigger downstream actions automatically?", "ngoText": "Do board decisions need to trigger downstream actions automatically?" }, { "id": "board-audience-audit", "type": "select", "options": [ { "label": "Internal audit only", "value": "internal" }, { "label": "Internal + donors / funders with stake", "value": "donor" }, { "label": "Internal + regulators + donors + public (where consented)", "value": "full" } ], "propertyMapping": { "internal": { "technologies": [ "Private ledger", "Internal-auditor verifier" ], "technologyProperties": { "audience": "Internal" } }, "donor": { "technologies": [ "Permissioned ledger", "Donor-verifier app", "Selective-disclosure VC" ], "technologyProperties": { "audience": "Internal + donor" } }, "full": { "technologies": [ "Hybrid public-anchor ledger", "Multi-audience verifier suite", "Selective-disclosure VC" ], "technologyProperties": { "audience": "Multi-stakeholder" } } }, "prefillFrom": null, "briefSection": "Audience", "text": "Who needs verifiable access to the decision record?", "ngoText": "Who needs verifiable access to the decision record?" } ], "complexityFactors": { "relationships": 3, "operationalChange": 2, "dataCompliance": 3 }, "complexityNotes": [ "Director count and geographic distribution", "Confidentiality tier (public / hybrid / confidential)", "Volume of decisions per cycle", "Legal eIDAS / UETA / UNCITRAL compliance requirements" ], "suggestedCriteria": [ "B3", "B6", "B7" ], "procurement": { "marketMaturity": "mature", "primaryMode": "off-the-shelf", "alternativeModes": [ "rfq" ], "reasoning": "Board decision-recording SaaS is mature in governance vertical.", "exampleProductCategories": [ "board-management-saas", "governance-records-platform" ], "partnerChannels": [], "lastReviewed": "2026-05-01" } }, { "id": "UC-E-081", "name": "Policy version control and attestation", "category": "E", "subcategory": "Compliance and Policy Management", "description": "Keep every version of each policy and record who confirmed they have read the current one, so you can show donors that staff are up to date.", "bCriteria": [ "B3", "B6", "B7" ], "requiredComponents": [ { "component": "audit-mechanism", "description": "Tamper-evident policy version history with content hashes" }, { "component": "identity-verification", "description": "Verifiable credentials for staff and third-party attestors" }, { "component": "credential-issuance", "description": "Attestation credentials issued when a staff member or partner acknowledges a policy" }, { "component": "smart-contracts", "description": "Renewal cycles, expiry, and re-attestation rules enforced programmatically" } ], "conditionalComponents": [ { "component": "privacy-tech", "condition": "If attestations to sensitive policies (safeguarding, PSEA) must not disclose attestor identity to non-authorised parties" }, { "component": "interoperability-layer", "condition": "If attestation credentials must be portable across multiple agencies (e.g., consortium-wide safeguarding compliance)" } ], "crossCategoryDependencies": [ "UC-B-029 for staff credential management that policy attestations attach to", "UC-E-083 for standards compliance which depends on current policy adherence", "UC-C-048 for general compliance audit-trail anchoring" ], "p2TriggerConditions": { "description": "Activated when organisation has substantial policy portfolio, high staff / partner turnover, and donor or regulator demands proof of live attestation.", "rangeSignals": [ "policyCount >= 10", "staffAttestationCycle <= annual", "donorComplianceProof == required" ] }, "contextFieldsTemplate": [ { "field": "policyPortfolioSize", "source": "P2 CatE", "description": "Count of active policies requiring attestation" }, { "field": "attestationFrequency", "source": "P0 Q20", "description": "How often staff / partners must re-attest" }, { "field": "attestorPopulation", "source": "P0 staff + partners", "description": "Number of individuals who must attest" }, { "field": "donorComplianceTier", "source": "P0 Q21", "description": "Degree of proof donors require" } ], "implementationComplexity": "medium", "examples": { "note": "Versioned policy attestation \u2014 adapted from enterprise compliance-attestation tooling.", "references": [ { "name": "Hyland Credentials (Learning Machine) for employee attestations", "url": "https://www.hylandcredentials.com/", "solved": "Issuing verifiable credentials when staff complete policy training or attestation cycles; portable across employer changes" }, { "name": "ISO 27001 attestation chains", "url": "https://www.iso.org/isoiec-27001-information-security.html", "solved": "Standards body pattern for versioned policy acceptance with audit evidence" }, { "name": "OpenAttestation framework (GovTech SG)", "url": "https://www.openattestation.com/", "solved": "Document-attestation framework with hash anchoring adapted to policy documents and sign-off chains" } ] }, "solutionQuestions": [ { "id": "policy-scope", "type": "select", "options": [ { "label": "Safeguarding / PSEA only", "value": "safeguarding" }, { "label": "HR, safeguarding, and code of conduct", "value": "hr-core" }, { "label": "All staff-facing and partner-facing policies (comprehensive)", "value": "comprehensive" } ], "propertyMapping": { "safeguarding": { "technologies": [ "Safeguarding-attestation credential issuer", "Staff VC wallet" ], "technologyProperties": { "scope": "Safeguarding-only", "complexity": "low" } }, "hr-core": { "technologies": [ "Multi-policy attestation issuer", "Per-staff VC collection", "Renewal scheduler" ], "technologyProperties": { "scope": "HR-core", "complexity": "medium" } }, "comprehensive": { "technologies": [ "Enterprise policy attestation platform", "Multi-role VC issuer", "Renewal + expiry smart-contract logic" ], "technologyProperties": { "scope": "Comprehensive", "complexity": "high" } } }, "prefillFrom": null, "briefSection": "Scope", "text": "Which policy categories will use cryptographic attestation?", "ngoText": "Which policy categories will use cryptographic attestation?" }, { "id": "policy-attestor-pop", "type": "select", "options": [ { "label": "Under 100", "value": "small" }, { "label": "100-1,000", "value": "medium" }, { "label": "1,000-10,000", "value": "large" }, { "label": "Over 10,000 (large INGO with partners)", "value": "massive" } ], "propertyMapping": { "small": { "technologies": [ "Single-issuer attestation app" ], "technologyProperties": { "scale": "Small" } }, "medium": { "technologies": [ "Multi-tenant attestation platform", "Role-based attestation workflows" ], "technologyProperties": { "scale": "Medium" } }, "large": { "technologies": [ "Enterprise attestation platform", "Delegated issuance", "Batch renewal" ], "technologyProperties": { "scale": "Large" } }, "massive": { "technologies": [ "Enterprise platform with sharded issuance", "Automated renewal pipelines", "Partner-delegated issuance" ], "technologyProperties": { "scale": "Massive" } } }, "prefillFrom": null, "briefSection": "Scale", "text": "Roughly how many people need to attest?", "ngoText": "Roughly how many people need to attest?" }, { "id": "policy-portability", "type": "select", "options": [ { "label": "No, internal only", "value": "internal" }, { "label": "Yes, consortium-wide recognition", "value": "consortium" }, { "label": "Yes, sector-wide (e.g., CHS Alliance safeguarding passport)", "value": "sector" } ], "propertyMapping": { "internal": { "technologies": [ "Internal VC ecosystem" ], "technologyProperties": { "portability": "None" } }, "consortium": { "technologies": [ "W3C VC interoperability layer", "Cross-org DID registry", "Consortium trust framework" ], "technologyProperties": { "portability": "Consortium" } }, "sector": { "technologies": [ "Sector-wide trust registry", "W3C VC framework", "Cross-border legal trust anchors" ], "technologyProperties": { "portability": "Sector-wide" } } }, "prefillFrom": null, "briefSection": "Portability", "text": "Do attestations need to be portable across organisations (e.g., consortium-wide safeguarding)?", "ngoText": "Do attestations need to be portable across organisations (e.g., consortium-wide safeguarding)?" }, { "id": "policy-renewal-rigour", "type": "select", "options": [ { "label": "Annual blanket re-attestation", "value": "annual" }, { "label": "Event-driven (on policy change) + annual floor", "value": "event-driven" }, { "label": "Continuous attestation with expiry enforcement", "value": "continuous" } ], "propertyMapping": { "annual": { "technologies": [ "Scheduled renewal reminder service" ], "technologyProperties": { "renewal": "Annual" } }, "event-driven": { "technologies": [ "Event-driven renewal smart-contract", "Policy-version subscription service" ], "technologyProperties": { "renewal": "Event-driven" } }, "continuous": { "technologies": [ "Short-lived VC issuance", "Real-time expiry monitoring", "Access-revocation smart-contract" ], "technologyProperties": { "renewal": "Continuous" } } }, "prefillFrom": null, "briefSection": "Renewal", "text": "How rigorously do attestations need to be renewed?", "ngoText": "How rigorously do attestations need to be renewed?" }, { "id": "policy-proof-target", "type": "select", "options": [ { "label": "HR and compliance team only", "value": "internal" }, { "label": "Donors / funders during audit", "value": "donor" }, { "label": "Regulators + donors + public (where appropriate)", "value": "multi" } ], "propertyMapping": { "internal": { "technologies": [ "Internal verifier tooling" ], "technologyProperties": { "proofTarget": "Internal" } }, "donor": { "technologies": [ "Donor verifier portal", "Selective-disclosure VC" ], "technologyProperties": { "proofTarget": "Donor" } }, "multi": { "technologies": [ "Multi-audience verifier suite", "Public status anchor", "Selective-disclosure controls" ], "technologyProperties": { "proofTarget": "Multi-stakeholder" } } }, "prefillFrom": null, "briefSection": "Proof audience", "text": "Who needs to verify attestation status?", "ngoText": "Who needs to verify attestation status?" } ], "complexityFactors": { "relationships": 3, "operationalChange": 2, "dataCompliance": 2 }, "complexityNotes": [ "Policy portfolio breadth", "Attestor population size", "Cross-organisation portability requirements", "Renewal cycle frequency" ], "suggestedCriteria": [ "B3", "B6", "B7" ], "procurement": { "marketMaturity": "mature", "primaryMode": "off-the-shelf", "alternativeModes": [ "rfq" ], "reasoning": "Policy version control is part of standard document management SaaS.", "exampleProductCategories": [ "policy-management-saas", "document-management-platform" ], "partnerChannels": [], "lastReviewed": "2026-05-01" } }, { "id": "UC-E-082", "name": "Conflict of interest declaration management", "category": "E", "subcategory": "Governance and Accountability", "description": "Record conflict of interest declarations from trustees and decision-makers with dates, and keep them private where needed but available to auditors.", "bCriteria": [ "B3", "B6", "B7" ], "requiredComponents": [ { "component": "identity-verification", "description": "Director / senior-staff VC identities binding declarations to specific individuals" }, { "component": "audit-mechanism", "description": "Tamper-evident declaration history with timestamps" }, { "component": "privacy-tech", "description": "Selective disclosure: regulators and audit see full detail, operational systems see only the recusal flag" }, { "component": "smart-contracts", "description": "Auto-recusal logic that blocks the declarant from decisions where the declared interest applies" } ], "conditionalComponents": [ { "component": "consent-management", "condition": "If declarants want to selectively reveal detail to specific donors or auditors on request" }, { "component": "interoperability-layer", "condition": "If declarations need to be recognised across consortium members (shared governance)" } ], "crossCategoryDependencies": [ "UC-E-080 for board-decision recording which consumes CoI declarations for recusal", "UC-E-070 for grant allocation where CoI affects partner selection", "UC-E-072 for whistleblower pathways when CoI is discovered post-hoc" ], "p2TriggerConditions": { "description": "Activated when organisation has institutional trustees, grant-making authority, or donor contracts requiring CoI audit trails.", "rangeSignals": [ "grantMakingAuthority == true", "institutionalTrustees >= 3", "donorCoIAttestation == required" ] }, "contextFieldsTemplate": [ { "field": "declarantCount", "source": "P0 staff + trustees", "description": "People required to declare (trustees, senior leadership, grant-decision staff)" }, { "field": "declarationFrequency", "source": "P2 CatE", "description": "Renewal cadence" }, { "field": "confidentialityRequirement", "source": "P0 Q20", "description": "Privacy obligations on the content of declarations" } ], "implementationComplexity": "medium", "examples": { "note": "CoI declaration tooling \u2014 draws from public-sector integrity systems.", "references": [ { "name": "UK Charity Commission conflict-of-interest guidance", "url": "https://www.gov.uk/government/publications/conflicts-of-interest-a-guide-for-charity-trustees-cc29", "solved": "Regulatory framing and declaration discipline for charity trustees, the target operating model that blockchain attestation implements" }, { "name": "OECD Trust in Government public-sector declarations", "url": "https://www.oecd.org/governance/trust-in-government/", "solved": "Structured declaration schema for senior public officials with public-audit verification" }, { "name": "EU Transparency Register", "url": "https://ec.europa.eu/transparency/regdoc/", "solved": "Versioned, publicly-verifiable declaration records at scale" } ] }, "solutionQuestions": [ { "id": "coi-declarant-scope", "type": "select", "options": [ { "label": "Trustees / directors only", "value": "trustees" }, { "label": "Trustees + senior leadership", "value": "senior" }, { "label": "Trustees + leadership + all grant-decision staff", "value": "comprehensive" } ], "propertyMapping": { "trustees": { "technologies": [ "Trustee VC wallet", "Single-role declaration app" ], "technologyProperties": { "scope": "Trustees-only", "complexity": "low" } }, "senior": { "technologies": [ "Multi-role VC framework", "Delegated declaration app" ], "technologyProperties": { "scope": "Senior", "complexity": "medium" } }, "comprehensive": { "technologies": [ "Enterprise declaration platform", "Role-based schema", "Recusal smart-contract" ], "technologyProperties": { "scope": "Comprehensive", "complexity": "high" } } }, "prefillFrom": null, "briefSection": "Scope", "text": "Who is required to submit CoI declarations?", "ngoText": "Who is required to submit CoI declarations?" }, { "id": "coi-confidentiality", "type": "select", "options": [ { "label": "Public register: declarations fully visible", "value": "public" }, { "label": "Confidential, only regulators and internal compliance see full text", "value": "confidential" }, { "label": "Layered: public declaration-of-existence + confidential detail", "value": "layered" } ], "propertyMapping": { "public": { "technologies": [ "Public declaration anchor" ], "technologyProperties": { "confidentiality": "Public" } }, "confidential": { "technologies": [ "Selective-disclosure VC", "Regulator-verifier tooling" ], "technologyProperties": { "confidentiality": "Confidential" } }, "layered": { "technologies": [ "Layered attestation schema", "ZK proof of no-conflict for operational systems" ], "technologyProperties": { "confidentiality": "Layered" } } }, "prefillFrom": null, "briefSection": "Confidentiality", "text": "What level of confidentiality applies to declaration content?", "ngoText": "What level of confidentiality applies to declaration content?" }, { "id": "coi-auto-recusal", "type": "select", "options": [ { "label": "Manual: declaration is recorded; recusal is human-managed", "value": "manual" }, { "label": "Advisory: system flags potential conflicts for humans to review", "value": "advisory" }, { "label": "Programmatic: smart-contract blocks the declarant from signing", "value": "programmatic" } ], "propertyMapping": { "manual": { "technologies": [ "Record-only declaration platform" ], "technologyProperties": { "automation": "None" } }, "advisory": { "technologies": [ "Conflict-flag engine", "Declaration-to-decision matcher" ], "technologyProperties": { "automation": "Advisory" } }, "programmatic": { "technologies": [ "Recusal smart-contract", "Decision-authorisation integration", "Conflict-match oracle" ], "technologyProperties": { "automation": "Programmatic" } } }, "prefillFrom": null, "briefSection": "Automation", "text": "Should declared conflicts automatically block the declarant from affected decisions?", "ngoText": "Should declared conflicts automatically block the declarant from affected decisions?" }, { "id": "coi-renewal", "type": "select", "options": [ { "label": "Annual", "value": "annual" }, { "label": "On material change only", "value": "material-change" }, { "label": "Both annual and on change", "value": "both" } ], "propertyMapping": { "annual": { "technologies": [ "Annual renewal scheduler" ], "technologyProperties": { "renewal": "Annual" } }, "material-change": { "technologies": [ "Change-triggered renewal prompt" ], "technologyProperties": { "renewal": "Event-driven" } }, "both": { "technologies": [ "Hybrid scheduler + event trigger" ], "technologyProperties": { "renewal": "Hybrid" } } }, "prefillFrom": null, "briefSection": "Renewal", "text": "How often must declarations be refreshed?", "ngoText": "How often must declarations be refreshed?" }, { "id": "coi-audit-target", "type": "select", "options": [ { "label": "Internal audit only", "value": "internal" }, { "label": "External auditor + internal", "value": "external" }, { "label": "Regulator + external auditor + donor (layered)", "value": "multi" } ], "propertyMapping": { "internal": { "technologies": [ "Internal-auditor verifier" ], "technologyProperties": { "auditAudience": "Internal" } }, "external": { "technologies": [ "External-auditor verifier portal", "Selective-disclosure proofs" ], "technologyProperties": { "auditAudience": "External" } }, "multi": { "technologies": [ "Multi-audience verifier suite", "Layered disclosure schema" ], "technologyProperties": { "auditAudience": "Multi" } } }, "prefillFrom": null, "briefSection": "Audit audience", "text": "Who audits the declaration register?", "ngoText": "Who audits the declaration register?" } ], "complexityFactors": { "relationships": 2, "operationalChange": 3, "dataCompliance": 3 }, "complexityNotes": [ "Declarant population size", "Confidentiality tier", "Level of recusal automation required", "Renewal cadence" ], "suggestedCriteria": [ "B3", "B6", "B7" ], "procurement": { "marketMaturity": "mature", "primaryMode": "off-the-shelf", "alternativeModes": [ "rfq" ], "reasoning": "Conflict of interest management is mature governance SaaS feature.", "exampleProductCategories": [ "governance-saas", "compliance-management-platform" ], "partnerChannels": [], "lastReviewed": "2026-05-01" } }, { "id": "UC-E-083", "name": "Standards compliance and accreditation certification", "category": "E", "subcategory": "Compliance and Standards", "description": "Keep a record of your standards certifications and their expiry dates that donors can check themselves, so a lapse does not interrupt funding.", "bCriteria": [ "B3", "B6", "B7" ], "requiredComponents": [ { "component": "credential-issuance", "description": "Verifiable credentials issued by standards bodies and accreditors certifying compliance status" }, { "component": "verification-mechanism", "description": "Real-time verification for donors, regulators, partners" }, { "component": "audit-mechanism", "description": "Audit evidence trail underlying each certification" }, { "component": "smart-contracts", "description": "Renewal cycles, certification expiry, and lapse triggers" } ], "conditionalComponents": [ { "component": "interoperability-layer", "condition": "If the NGO holds certifications from multiple bodies (CHS, Sphere, ISO 9001, sector-specific) that donors need to cross-verify" }, { "component": "privacy-tech", "condition": "If audit evidence underlying a certification must remain confidential while the certificate itself is public" } ], "crossCategoryDependencies": [ "UC-E-076 for partner capacity verification where standards compliance is the qualification", "UC-E-081 for policy attestation that underpins many standards", "UC-F-084 for donor reporting where certification status is a line item" ], "p2TriggerConditions": { "description": "Activated when NGO holds multiple standards certifications, donors require proof of status, or certification lapses have previously caused funding disruption.", "rangeSignals": [ "certificationCount >= 2", "donorCertificationRequirement == required", "certificationLapseImpact >= material" ] }, "contextFieldsTemplate": [ { "field": "certificationPortfolio", "source": "P2 CatE", "description": "List of active standards certifications" }, { "field": "certifyingBodies", "source": "P0 Q20", "description": "Issuing organisations" }, { "field": "renewalBurden", "source": "P2 CatE", "description": "Effort currently spent on renewal / audit cycles" } ], "implementationComplexity": "medium", "examples": { "note": "Standards certification anchoring \u2014 adapted from industry compliance-credential pilots.", "references": [ { "name": "Core Humanitarian Standard (CHS) Alliance verification scheme", "url": "https://www.chsalliance.org/get-support/chs-verification/", "solved": "Sector-wide certification cycle that blockchain attestation would anchor, for real-time verification of CHS-verified status" }, { "name": "ISO blockchain-based certification pilots (ISO / TC 307)", "url": "https://www.iso.org/committee/6266604.html", "solved": "ISO technical committee work on blockchain anchoring of ISO certifications" }, { "name": "IRIS+ impact standards (GIIN)", "url": "https://iris.thegiin.org/", "solved": "Standards-body verifiable-credential issuance for impact metrics" } ] }, "solutionQuestions": [ { "id": "standards-portfolio", "type": "select", "options": [ { "label": "1-2 (single primary standard)", "value": "small" }, { "label": "3-5 (mix of sector and quality standards)", "value": "medium" }, { "label": "6+ (comprehensive certification programme)", "value": "large" } ], "propertyMapping": { "small": { "technologies": [ "Single-certification VC" ], "technologyProperties": { "portfolio": "Small" } }, "medium": { "technologies": [ "Multi-certification VC wallet", "Cross-standard registry" ], "technologyProperties": { "portfolio": "Medium" } }, "large": { "technologies": [ "Enterprise certification platform", "Multi-issuer interoperability layer", "Certification analytics" ], "technologyProperties": { "portfolio": "Large" } } }, "prefillFrom": null, "briefSection": "Portfolio", "text": "How many standards certifications does your organisation maintain?", "ngoText": "How many standards certifications does your organisation maintain?" }, { "id": "standards-certifier-relationship", "type": "select", "options": [ { "label": "Self-attestation + hash-anchor", "value": "self-attest" }, { "label": "Hybrid: standards body issues certificate, NGO anchors on blockchain", "value": "hybrid" }, { "label": "Standards body native VC issuance", "value": "native" } ], "propertyMapping": { "self-attest": { "technologies": [ "Self-sovereign credential issuance", "Hash-anchoring to public ledger" ], "technologyProperties": { "attestationModel": "Self-attest" } }, "hybrid": { "technologies": [ "Hybrid VC anchor service", "Cert-to-VC conversion pipeline" ], "technologyProperties": { "attestationModel": "Hybrid" } }, "native": { "technologies": [ "Standards-body VC issuer", "Native verifier ecosystem" ], "technologyProperties": { "attestationModel": "Native VC" } } }, "prefillFrom": null, "briefSection": "Issuer relationship", "text": "Are the standards bodies ready to issue blockchain credentials, or is the NGO self-attesting?", "ngoText": "Are the standards bodies ready to issue blockchain credentials, or is the NGO self-attesting?" }, { "id": "standards-evidence-privacy", "type": "select", "options": [ { "label": "Public: full evidence open", "value": "public" }, { "label": "Private: evidence confidential, only certification status public", "value": "private" }, { "label": "Selective: evidence selectively disclosed to specific auditors", "value": "selective" } ], "propertyMapping": { "public": { "technologies": [ "Public evidence repository" ], "technologyProperties": { "evidence": "Public" } }, "private": { "technologies": [ "Private evidence store", "Public certification anchor" ], "technologyProperties": { "evidence": "Private" } }, "selective": { "technologies": [ "Selective-disclosure VC", "Auditor-verifier portal" ], "technologyProperties": { "evidence": "Selective" } } }, "prefillFrom": null, "briefSection": "Evidence privacy", "text": "How should the audit evidence underlying a certification be handled?", "ngoText": "How should the audit evidence underlying a certification be handled?" }, { "id": "standards-renewal-burden", "type": "select", "options": [ { "label": "Manageable: standard annual audit", "value": "manageable" }, { "label": "Heavy: audit windows disrupt operations", "value": "heavy" }, { "label": "Severe: certification lapses have caused funding freezes", "value": "severe" } ], "propertyMapping": { "manageable": { "technologies": [ "Standard renewal scheduler" ], "technologyProperties": { "renewalBurden": "Low" } }, "heavy": { "technologies": [ "Continuous-evidence pipeline", "Automated audit-artefact aggregator" ], "technologyProperties": { "renewalBurden": "Medium" } }, "severe": { "technologies": [ "Pre-emptive expiry alerting", "Evidence-continuity smart-contract", "Auto-renewal where permitted" ], "technologyProperties": { "renewalBurden": "High" } } }, "prefillFrom": null, "briefSection": "Renewal", "text": "How disruptive are current certification renewal cycles?", "ngoText": "How disruptive are current certification renewal cycles?" }, { "id": "standards-verifier-audience", "type": "select", "options": [ { "label": "Donors during grant-making", "value": "donors" }, { "label": "Partners during consortium formation", "value": "partners" }, { "label": "Public-facing (published compliance dashboard)", "value": "public" } ], "propertyMapping": { "donors": { "technologies": [ "Donor verifier portal" ], "technologyProperties": { "audience": "Donor" } }, "partners": { "technologies": [ "Partner verifier app", "Consortium trust registry" ], "technologyProperties": { "audience": "Partner" } }, "public": { "technologies": [ "Public compliance dashboard", "Status-API service" ], "technologyProperties": { "audience": "Public" } } }, "prefillFrom": null, "briefSection": "Verifier audience", "text": "Who most frequently needs to verify your certification status?", "ngoText": "Who most frequently needs to verify your certification status?" } ], "complexityFactors": { "relationships": 4, "operationalChange": 2, "dataCompliance": 2 }, "complexityNotes": [ "Certification portfolio breadth", "Issuer readiness for native VC issuance", "Evidence-privacy requirements", "Renewal-cycle disruption history" ], "suggestedCriteria": [ "B3", "B6", "B7" ], "procurement": { "marketMaturity": "emerging", "primaryMode": "rfq", "alternativeModes": [ "off-the-shelf" ], "reasoning": "Standards compliance certification platforms exist.", "exampleProductCategories": [ "compliance-certification-platform", "accreditation-saas" ], "partnerChannels": [], "lastReviewed": "2026-05-01" } }, { "id": "UC-D-072", "name": "Ethical sourcing verification", "category": "D", "subcategory": "Supply Chain Compliance", "description": "Check that suppliers meet your ethical sourcing rules, and keep the evidence in a record that donors and auditors can inspect.", "bCriteria": [ "B1", "B3", "B4", "B7" ], "requiredComponents": [ { "component": "identity-verification", "description": "Supplier DIDs linking each tier of the supply chain to a verifiable counterparty" }, { "component": "audit-mechanism", "description": "Tamper-evident sourcing-event ledger (farm \u2192 processor \u2192 exporter \u2192 NGO procurement)" }, { "component": "credential-issuance", "description": "Fair-Trade, Rainforest Alliance, SA8000, or equivalent certifications attached to specific batches" }, { "component": "oracle-data", "description": "Third-party audit and certification feeds" } ], "conditionalComponents": [ { "component": "iot-sensors", "condition": "If commodity-specific sensor data (e.g., temperature, geo-tracking) is part of the integrity claim" }, { "component": "privacy-tech", "condition": "If supplier-confidential pricing or relationships must remain masked while sourcing claims remain verifiable" } ], "crossCategoryDependencies": [ "UC-D-057 for donated-goods provenance which shares the supplier DID layer", "UC-D-073 for food-safety tracking that extends this with recall and contamination flows", "UC-E-076 for partner capacity verification when suppliers are evaluated against standards" ], "p2TriggerConditions": { "description": "Activated when procurement volumes are material, donor or media scrutiny on sourcing is high, or past supplier-integrity failures have caused reputational damage.", "rangeSignals": [ "procurementVolume >= significant", "donorEthicalSourcingRequirement == required", "supplierIntegrityIncidents >= 1" ] }, "contextFieldsTemplate": [ { "field": "commodityCategories", "source": "P2 CatD", "description": "Categories of goods procured (food, textiles, health products, etc.)" }, { "field": "supplyChainTiers", "source": "P2 CatD", "description": "Depth of supply chain visibility required" }, { "field": "certificationStandards", "source": "P0 Q20", "description": "Applicable ethical-sourcing standards" }, { "field": "supplierCount", "source": "P2 CatD", "description": "Approximate supplier population" } ], "implementationComplexity": "high", "examples": { "note": "Ethical sourcing \u2014 mature pattern from enterprise supply-chain tech with growing humanitarian adoption.", "references": [ { "name": "Provenance", "url": "https://www.provenance.org/", "solved": "Ethical claims platform used by FMCG and retail brands; adapted patterns for humanitarian procurement" }, { "name": "IBM Food Trust", "url": "https://www.ibm.com/products/supply-chain-intelligence-suite/food-trust", "solved": "Supply-chain provenance at scale with multi-party verification, including WFP food-aid pilots" }, { "name": "Fair Trade Federation blockchain pilots", "url": "https://www.fairtradefederation.org/", "solved": "Certification body issuing verifiable credentials for Fair Trade status at batch level" }, { "name": "Everledger", "url": "https://everledger.io/", "solved": "High-value-goods provenance model (diamonds, wine); applicable pattern for humanitarian high-value items" } ] }, "solutionQuestions": [ { "id": "sourcing-scope", "type": "select", "options": [ { "label": "Single commodity class (e.g. food, or textiles)", "value": "single" }, { "label": "Multiple commodity classes", "value": "multi" }, { "label": "Full procurement portfolio", "value": "full" } ], "propertyMapping": { "single": { "technologies": [ "Single-commodity provenance platform" ], "technologyProperties": { "scope": "Single", "complexity": "medium" } }, "multi": { "technologies": [ "Multi-commodity provenance platform", "Category-specific audit layers" ], "technologyProperties": { "scope": "Multi", "complexity": "high" } }, "full": { "technologies": [ "Enterprise procurement-integrity platform", "Category-agnostic ledger", "Multi-certification issuer network" ], "technologyProperties": { "scope": "Full", "complexity": "very high" } } }, "prefillFrom": null, "briefSection": "Scope", "text": "Which commodities are in scope for ethical-sourcing verification?", "ngoText": "Which commodities are in scope for ethical-sourcing verification?" }, { "id": "sourcing-tier-depth", "type": "select", "options": [ { "label": "Tier 1 only (direct supplier)", "value": "tier1" }, { "label": "Tier 1 + 2 (supplier + their inputs)", "value": "tier2" }, { "label": "Full chain to origin (farm / factory level)", "value": "full" } ], "propertyMapping": { "tier1": { "technologies": [ "Supplier VC platform", "First-tier audit integration" ], "technologyProperties": { "tierDepth": "1" } }, "tier2": { "technologies": [ "Multi-tier provenance ledger", "Cross-tier event chain" ], "technologyProperties": { "tierDepth": "2" } }, "full": { "technologies": [ "Origin-level IoT + provenance integration", "Farmer / artisan VC issuance", "Multi-hop verification" ], "technologyProperties": { "tierDepth": "Full" } } }, "prefillFrom": null, "briefSection": "Tier depth", "text": "How many tiers of the supply chain need verifiable visibility?", "ngoText": "How many tiers of the supply chain need verifiable visibility?" }, { "id": "sourcing-standards", "type": "select", "options": [ { "label": "Single standard (e.g. Fair Trade only)", "value": "single-std" }, { "label": "Multiple standards (Fair Trade + Rainforest Alliance + SA8000)", "value": "multi-std" }, { "label": "Custom NGO ethical framework + external standards", "value": "custom" } ], "propertyMapping": { "single-std": { "technologies": [ "Single-certifier VC issuer" ], "technologyProperties": { "standards": "Single" } }, "multi-std": { "technologies": [ "Multi-certifier registry", "Cross-standard trust framework" ], "technologyProperties": { "standards": "Multi" } }, "custom": { "technologies": [ "Custom certification schema", "External-standards bridge layer", "Audit evidence aggregator" ], "technologyProperties": { "standards": "Custom + external" } } }, "prefillFrom": null, "briefSection": "Standards", "text": "Which ethical standards apply?", "ngoText": "Which ethical standards apply?" }, { "id": "sourcing-evidence-model", "type": "select", "options": [ { "label": "Supplier self-declaration (lowest assurance)", "value": "self" }, { "label": "Third-party certifier audits", "value": "third-party" }, { "label": "Continuous IoT + audit + worker attestation", "value": "continuous" } ], "propertyMapping": { "self": { "technologies": [ "Self-attestation VC" ], "technologyProperties": { "evidenceModel": "Self" } }, "third-party": { "technologies": [ "Certifier VC issuance", "Audit-artefact anchoring" ], "technologyProperties": { "evidenceModel": "Third-party" } }, "continuous": { "technologies": [ "IoT telemetry network", "Worker attestation app", "Audit ledger" ], "technologyProperties": { "evidenceModel": "Continuous" } } }, "prefillFrom": null, "briefSection": "Evidence", "text": "Where does verification evidence come from?", "ngoText": "Where does verification evidence come from?" }, { "id": "sourcing-consumer-disclosure", "type": "select", "options": [ { "label": "Internal only: procurement team reference", "value": "internal" }, { "label": "Donor-facing: available on request during audit", "value": "donor" }, { "label": "Public: beneficiary and donor-facing provenance dashboard", "value": "public" } ], "propertyMapping": { "internal": { "technologies": [ "Internal procurement dashboard" ], "technologyProperties": { "disclosure": "Internal" } }, "donor": { "technologies": [ "Donor verifier portal", "Batch-level claim display" ], "technologyProperties": { "disclosure": "Donor" } }, "public": { "technologies": [ "Public provenance dashboard", "QR-code per batch", "Consumer-facing DApp" ], "technologyProperties": { "disclosure": "Public" } } }, "prefillFrom": null, "briefSection": "Public disclosure", "text": "How is sourcing integrity communicated to donors and the public?", "ngoText": "How is sourcing integrity communicated to donors and the public?" } ], "complexityFactors": { "relationships": 4, "operationalChange": 4, "dataCompliance": 3 }, "complexityNotes": [ "Commodity scope", "Supply-chain tier depth required", "Standards portfolio", "Evidence-model rigour" ], "suggestedCriteria": [ { "id": "SC-SOURCING-CHAIN", "name": "Provenance chain completeness", "description": "The system captures every transformation step from origin to final NGO procurement, with attestations at each step. Without complete chain, ethical claims fail at the weakest link.", "weight": 0.3, "ratingGuide": { "5": "Every supply-chain step has on-chain attestation from a verified party. Origin to procurement traceable.", "4": "Major steps captured; minor handoffs documented.", "3": "Origin and final-tier captured; intermediate steps gap-filled by retailer attestation.", "2": "Spot-check approach; sampling provides limited assurance.", "1": "Self-declaration only." } }, { "id": "SC-SOURCING-AUDIT", "name": "Third-party audit integration", "description": "Third-party auditors (certification bodies and supply-chain traceability platforms) are integrated into the system as attestors. Independent audit is the credibility anchor.", "weight": 0.25, "ratingGuide": { "5": "Multiple independent auditors integrated; their attestations on-chain.", "4": "Primary auditor integrated; secondary auditors via reports.", "3": "Auditor reports referenced in system; not directly integrated.", "2": "Auditor reports kept separately; cross-reference manual.", "1": "No third-party audit integration." } }, { "id": "SC-SOURCING-DECENTRALISATION", "name": "Producer-side data sovereignty", "description": "Producers control their own attestation records rather than depending on a central operator. Decentralisation protects producers from operator capture.", "weight": 0.2, "ratingGuide": { "5": "Producers hold credentials in cooperative wallets; portable across buyers.", "4": "Producers attest via cooperative-controlled tools; records portable.", "3": "Buyer-controlled records; producers see but don't own.", "2": "Producer records held by aggregator; weak portability.", "1": "Producer records held entirely by buyer or operator." } }, { "id": "SC-SOURCING-PROGRAMMATIC", "name": "Programmatic compliance verification", "description": "The system automatically verifies compliance with NGO sourcing policies (forced-labour-free, conflict-free, fair-price thresholds). Manual verification scales poorly.", "weight": 0.15, "ratingGuide": { "5": "Sourcing policies encoded as smart contracts; auto-flagging of violations.", "4": "Automated policy checks; human review for edge cases.", "3": "Periodic compliance audits with system-pulled data.", "2": "Manual compliance review with system data.", "1": "Manual compliance audit; system data not directly used." } }, { "id": "SC-SOURCING-SCALE", "name": "Multi-supplier scalability", "description": "The system handles the actual scale of NGO procurement (multiple suppliers, multiple commodity types, periodic re-tender). Real procurement is fragmented.", "weight": 0.1, "ratingGuide": { "5": "Multi-supplier orchestration; new suppliers onboarded in days.", "4": "Multiple suppliers; onboarding manual but efficient.", "3": "Single-supplier optimisation; multi-supplier requires per-relationship setup.", "2": "Single-supplier focus; expansion is project-by-project.", "1": "Hard-coded to one supplier relationship." } } ], "procurement": { "marketMaturity": "emerging", "primaryMode": "tender", "alternativeModes": [ "off-the-shelf" ], "reasoning": "Ethical sourcing verification platforms exist.", "exampleProductCategories": [ "ethical-sourcing-platform", "supplier-verification-saas" ], "partnerChannels": [], "lastReviewed": "2026-05-01" } }, { "id": "UC-D-073", "name": "Food safety and quality tracking", "category": "D", "subcategory": "Quality Assurance", "description": "Track the safety and quality checks on food aid from production to distribution, so contaminated or poor-quality food is found before it reaches people.", "bCriteria": [ "B3", "B4", "B7" ], "requiredComponents": [ { "component": "audit-mechanism", "description": "Tamper-evident log of food safety events (lab tests, temperature excursions, quality failures)" }, { "component": "oracle-data", "description": "Laboratory test results, temperature sensors, inspection feeds" }, { "component": "smart-contracts", "description": "Recall trigger logic and quarantine propagation rules" }, { "component": "identity-verification", "description": "Batch-level identifiers tying safety events to specific shipments and beneficiary populations" } ], "conditionalComponents": [ { "component": "iot-sensors", "condition": "If cold-chain monitoring is part of safety assurance (integrates with UC-D-053)" }, { "component": "privacy-tech", "condition": "If supplier-confidential quality-failure data must be kept from competitors while still being auditable by donors and regulators" } ], "crossCategoryDependencies": [ "UC-D-053 for cold chain monitoring that feeds safety events", "UC-D-056 for food-aid tracking at the supply-chain level", "UC-D-072 for ethical-sourcing verification sharing supplier identity layer" ], "p2TriggerConditions": { "description": "Activated for food-aid operations at scale where contamination / quality failures have potential beneficiary-safety impact.", "rangeSignals": [ "foodAidVolume >= material", "qualityIncidentHistory >= 1", "recallCapability == required" ] }, "contextFieldsTemplate": [ { "field": "foodAidCategories", "source": "P2 CatD", "description": "Types of food commodities distributed (grain, therapeutic nutrition, fortified food, etc.)" }, { "field": "batchVolumes", "source": "P2 CatD", "description": "Typical batch sizes and distribution frequency" }, { "field": "testingInfrastructure", "source": "P0 / P2", "description": "Laboratory and inspection capacity" }, { "field": "recallReach", "source": "P2 CatD", "description": "Ability to reach beneficiaries for recall notification" } ], "implementationComplexity": "high", "examples": { "note": "Food safety tracking \u2014 adapted from commercial FMCG / retail traceability with humanitarian-context adjustments for offline and low-literacy environments.", "references": [ { "name": "IBM Food Trust (WFP pilots)", "url": "https://www.ibm.com/products/supply-chain-intelligence-suite/food-trust", "solved": "Food traceability at scale including WFP food-aid pilots; pattern for recall propagation" }, { "name": "WHO food-safety blockchain initiatives", "url": "https://www.who.int/news-room/fact-sheets/detail/food-safety", "solved": "WHO work on traceable food-safety reporting across member states" }, { "name": "Codex Alimentarius traceability principles", "url": "http://www.fao.org/fao-who-codexalimentarius/", "solved": "Target traceability requirements the blockchain implementation must satisfy" } ] }, "solutionQuestions": [ { "id": "foodsafety-scope", "type": "select", "options": [ { "label": "Contamination / pathogen tracking only", "value": "contamination" }, { "label": "Contamination + spoilage / temperature excursions", "value": "spoilage" }, { "label": "Comprehensive (contamination, spoilage, quality, nutritional integrity)", "value": "comprehensive" } ], "propertyMapping": { "contamination": { "technologies": [ "Lab-test integration", "Contamination-event ledger" ], "technologyProperties": { "scope": "Contamination" } }, "spoilage": { "technologies": [ "Lab + IoT temperature integration", "Multi-event ledger" ], "technologyProperties": { "scope": "Safety + spoilage" } }, "comprehensive": { "technologies": [ "Enterprise food-safety platform", "Multi-sensor + lab aggregation", "Nutritional testing integration" ], "technologyProperties": { "scope": "Comprehensive" } } }, "prefillFrom": null, "briefSection": "Scope", "text": "Which food-safety domains are in scope?", "ngoText": "Which food-safety domains are in scope?" }, { "id": "foodsafety-recall-speed", "type": "select", "options": [ { "label": "Days (manual coordination)", "value": "days" }, { "label": "Hours (semi-automated)", "value": "hours" }, { "label": "Real-time (automated recall + beneficiary notification)", "value": "realtime" } ], "propertyMapping": { "days": { "technologies": [ "Batch-to-distribution registry" ], "technologyProperties": { "recallSpeed": "Days" } }, "hours": { "technologies": [ "Recall-propagation smart-contract", "Distribution-point messaging service" ], "technologyProperties": { "recallSpeed": "Hours" } }, "realtime": { "technologies": [ "Real-time recall smart-contract", "SMS / offline beneficiary notification", "Geo-targeted recall messaging" ], "technologyProperties": { "recallSpeed": "Real-time" } } }, "prefillFrom": null, "briefSection": "Recall capability", "text": "How quickly do you need to propagate a recall once triggered?", "ngoText": "How quickly do you need to propagate a recall once triggered?" }, { "id": "foodsafety-evidence-source", "type": "select", "options": [ { "label": "Supplier certificates only", "value": "certs" }, { "label": "Supplier certs + independent sampling", "value": "sampling" }, { "label": "Continuous IoT + lab + inspection", "value": "continuous" } ], "propertyMapping": { "certs": { "technologies": [ "Supplier-certificate VC" ], "technologyProperties": { "evidence": "Supplier" } }, "sampling": { "technologies": [ "Lab integration", "Sampling-event ledger" ], "technologyProperties": { "evidence": "Supplier + lab" } }, "continuous": { "technologies": [ "IoT telemetry", "Lab integration", "Inspection app", "Multi-source aggregator" ], "technologyProperties": { "evidence": "Continuous" } } }, "prefillFrom": null, "briefSection": "Evidence source", "text": "Where does safety evidence come from?", "ngoText": "Where does safety evidence come from?" }, { "id": "foodsafety-beneficiary-reach", "type": "select", "options": [ { "label": "No, distribution-point notification only", "value": "no" }, { "label": "Partial, SMS or mobile messaging where available", "value": "partial" }, { "label": "Yes, direct beneficiary comms (mobile, wristband, voucher app)", "value": "full" } ], "propertyMapping": { "no": { "technologies": [ "Distribution-point messaging" ], "technologyProperties": { "beneficiaryReach": "Indirect" } }, "partial": { "technologies": [ "SMS notification service", "Distribution + direct hybrid" ], "technologyProperties": { "beneficiaryReach": "Hybrid" } }, "full": { "technologies": [ "Beneficiary-direct messaging", "Mobile app notification", "Voucher-linked recall" ], "technologyProperties": { "beneficiaryReach": "Direct" } } }, "prefillFrom": null, "briefSection": "Beneficiary reach", "text": "Can beneficiaries be reached directly during a recall?", "ngoText": "Can beneficiaries be reached directly during a recall?" }, { "id": "foodsafety-audit-target", "type": "select", "options": [ { "label": "Internal QA only", "value": "internal" }, { "label": "Regulators + donors + internal", "value": "external" }, { "label": "Public (full consumer-facing transparency)", "value": "public" } ], "propertyMapping": { "internal": { "technologies": [ "Internal QA dashboard" ], "technologyProperties": { "auditTarget": "Internal" } }, "external": { "technologies": [ "Multi-audience verifier", "Regulator-facing anchor" ], "technologyProperties": { "auditTarget": "External" } }, "public": { "technologies": [ "Public food-safety dashboard", "Beneficiary-facing disclosure app" ], "technologyProperties": { "auditTarget": "Public" } } }, "prefillFrom": null, "briefSection": "Audit target", "text": "Who needs to audit safety events?", "ngoText": "Who needs to audit safety events?" } ], "complexityFactors": { "relationships": 4, "operationalChange": 4, "dataCompliance": 3 }, "complexityNotes": [ "Food-aid volume and complexity", "Recall-speed requirement", "Evidence infrastructure", "Beneficiary-reach capability" ], "suggestedCriteria": [ { "id": "SC-FOOD-COLDCHAIN", "name": "Cold-chain integrity capture", "description": "The system captures cold-chain breach events with timestamp, location, and severity. Cold chain failures are the primary food-safety failure mode in humanitarian contexts.", "weight": 0.3, "ratingGuide": { "5": "IoT-anchored real-time temperature, humidity, location. Breach alerts within minutes.", "4": "Periodic IoT checks; manual logging for non-IoT segments.", "3": "Manual logging at handoff points; IoT for primary leg only.", "2": "Spot-check temperature logging; gaps common.", "1": "No systematic cold-chain monitoring." } }, { "id": "SC-FOOD-SAFETY-CERT", "name": "Food-safety certification chain", "description": "Food-safety certifications (HACCP, ISO 22000, country-specific) are tracked from supplier to delivery. Certification chain is the regulatory anchor.", "weight": 0.25, "ratingGuide": { "5": "Certifications anchored at every chain step; verifiable on demand.", "4": "Supplier-level certifications strong; downstream cert tracking partial.", "3": "Annual supplier audit; downstream verification manual.", "2": "Supplier self-declaration; periodic audit.", "1": "No systematic certification tracking." } }, { "id": "SC-FOOD-RECALL", "name": "Recall and traceback speed", "description": "The system can identify all affected lots and locations within hours of a contamination event. Speed of recall is the operational test.", "weight": 0.2, "ratingGuide": { "5": "Lot-level traceback in minutes; affected recipients alerted same day.", "4": "Lot-level traceback in hours; recipient alert in days.", "3": "Batch-level traceback in days; recipient alert via implementing partners.", "2": "Manual traceback exercise; takes weeks.", "1": "Recall capability informal at best." } }, { "id": "SC-FOOD-MULTI-PARTY", "name": "Multi-party verification fitness", "description": "Suppliers, NGO operators, and end recipients all can verify food-safety claims independently. Multi-party verification is what the architecture is for.", "weight": 0.15, "ratingGuide": { "5": "All parties verify independently with cryptographic guarantees.", "4": "Suppliers and NGO verify; recipients trust by reputation.", "3": "NGO has full visibility; others see summaries.", "2": "Single-party visibility; others trust the operator.", "1": "Trust-by-statement only." } }, { "id": "SC-FOOD-FIELD", "name": "Field-condition robustness", "description": "The monitoring works in last-mile humanitarian field conditions (heat, dust, intermittent power). Field durability is the binding constraint.", "weight": 0.1, "ratingGuide": { "5": "Ruggedised IoT, solar-powered, low-bandwidth sync, field-tested.", "4": "Field-grade equipment; some failure rate accepted.", "3": "Standard equipment with field-mod; visible failure rate.", "2": "Office-grade equipment retro-fitted; high failure rate.", "1": "Not field-fit." } } ], "procurement": { "marketMaturity": "mature", "primaryMode": "off-the-shelf", "alternativeModes": [ "rfq" ], "reasoning": "Food safety platforms are mature in commercial markets.", "exampleProductCategories": [ "food-safety-platform", "quality-tracking-saas" ], "partnerChannels": [], "lastReviewed": "2026-05-01" } }, { "id": "UC-C-052", "name": "Whistleblower and reporting channel integrity", "category": "C", "subcategory": "Accountability and Integrity", "description": "Show that reports sent through your whistleblowing channel are not lost, delayed or altered, so people trust it enough to use it.", "bCriteria": [ "B3", "B4", "B6" ], "requiredComponents": [ { "component": "audit-mechanism", "description": "Tamper-evident submission log (hash of report + timestamp anchored to public ledger)" }, { "component": "privacy-tech", "description": "Zero-knowledge submission so reporter identity cannot be inferred by the hosting organisation or ledger observers" }, { "component": "smart-contracts", "description": "Retention-policy enforcement and deliverability-proof logic" }, { "component": "consent-management", "description": "Reporter-controlled selective disclosure to investigators" } ], "conditionalComponents": [ { "component": "interoperability-layer", "condition": "If reports must be routed across consortium members or to external oversight bodies" }, { "component": "identity-verification", "condition": "If certain report classes require verified-reporter identity (e.g. staff-only channels) while still protecting anonymity from the organisation" } ], "crossCategoryDependencies": [ "UC-E-072 for whistleblower protection (identity shielding) which this UC complements by protecting the channel itself", "UC-E-082 for CoI declarations that may reveal motives behind retaliation", "UC-C-048 for audit-trail maintenance shared with this UC" ], "p2TriggerConditions": { "description": "Activated for organisations with established whistleblower / reporting channels under scrutiny for channel integrity failures (lost reports, delayed investigation, suspected tampering).", "rangeSignals": [ "whistleblowerChannelActive == true", "reportVolumeAnnual >= material", "pastIntegrityIncidents >= 1" ] }, "contextFieldsTemplate": [ { "field": "reportTypes", "source": "P2 CatC", "description": "Categories of reports accepted (safeguarding, fraud, HR, operational)" }, { "field": "reporterPopulation", "source": "P0 staff + beneficiaries", "description": "Who can submit reports" }, { "field": "retentionRequirements", "source": "P0 Q20", "description": "Legal retention periods by report type" }, { "field": "investigatorModel", "source": "P2 CatC", "description": "Internal, external, or hybrid investigation" } ], "implementationComplexity": "medium", "examples": { "note": "Reporting-channel integrity \u2014 emerging from secure-journalism and public-sector whistleblower tooling.", "references": [ { "name": "GlobaLeaks", "url": "https://www.globaleaks.org/", "solved": "Open-source whistleblower platform used by media and NGOs; pattern for secure submission with hash anchoring" }, { "name": "SecureDrop (Freedom of the Press Foundation)", "url": "https://securedrop.org/", "solved": "Newsroom-grade anonymous-submission pattern with integrity guarantees" }, { "name": "EU Whistleblower Directive technical guidance", "url": "https://eur-lex.europa.eu/eli/dir/2019/1937/oj", "solved": "Regulatory target for channel integrity requirements in EU member-state NGOs" } ] }, "solutionQuestions": [ { "id": "wb-identity-model", "type": "select", "options": [ { "label": "Fully anonymous (no identity at all)", "value": "anon" }, { "label": "Pseudonymous (organisation-blind but consistent reporter identity for follow-up)", "value": "pseudonymous" }, { "label": "Verified reporter with identity shielded from investigator until escalation", "value": "verified-shielded" } ], "propertyMapping": { "anon": { "technologies": [ "Anonymous-submission gateway", "Tor-based submission" ], "technologyProperties": { "identityModel": "Anonymous" } }, "pseudonymous": { "technologies": [ "Pseudonymous-credential scheme", "Zero-knowledge identity proof" ], "technologyProperties": { "identityModel": "Pseudonymous" } }, "verified-shielded": { "technologies": [ "Escrowed-identity VC", "Controlled-reveal smart-contract" ], "technologyProperties": { "identityModel": "Verified-shielded" } } }, "prefillFrom": null, "briefSection": "Identity", "text": "What identity model applies to reports?", "ngoText": "What identity model applies to reports?" }, { "id": "wb-channel-integrity-level", "type": "select", "options": [ { "label": "Hash-anchored submission log", "value": "hash" }, { "label": "Hash + deliverability proof (investigator cannot deny receipt)", "value": "deliverability" }, { "label": "Full end-to-end cryptographic integrity (submission, deliverability, retention, tamper-evidence)", "value": "full" } ], "propertyMapping": { "hash": { "technologies": [ "Hash-anchoring service", "Public-ledger commitment" ], "technologyProperties": { "integrityLevel": "Basic" } }, "deliverability": { "technologies": [ "Deliverability-proof smart-contract", "Investigator-receipt credential" ], "technologyProperties": { "integrityLevel": "Deliverability" } }, "full": { "technologies": [ "End-to-end integrity platform", "Retention smart-contract", "Multi-party tamper-evidence" ], "technologyProperties": { "integrityLevel": "Full" } } }, "prefillFrom": null, "briefSection": "Channel integrity", "text": "What integrity guarantees does the channel need?", "ngoText": "What integrity guarantees does the channel need?" }, { "id": "wb-retention", "type": "select", "options": [ { "label": "Short (< 12 months, basic compliance)", "value": "short" }, { "label": "Medium (12-60 months, typical EU Directive)", "value": "medium" }, { "label": "Long (indefinite for safeguarding / ongoing investigations)", "value": "long" } ], "propertyMapping": { "short": { "technologies": [ "Short-retention ledger" ], "technologyProperties": { "retention": "Short" } }, "medium": { "technologies": [ "Retention smart-contract", "Expiry-triggered purge" ], "technologyProperties": { "retention": "Medium" } }, "long": { "technologies": [ "Long-retention ledger", "Legal-hold smart-contract" ], "technologyProperties": { "retention": "Long" } } }, "prefillFrom": null, "briefSection": "Retention", "text": "What retention policy applies?", "ngoText": "What retention policy applies?" }, { "id": "wb-investigator-model", "type": "select", "options": [ { "label": "Internal only", "value": "internal" }, { "label": "External independent party", "value": "external" }, { "label": "Tiered (internal first, external escalation)", "value": "tiered" } ], "propertyMapping": { "internal": { "technologies": [ "Internal-investigator portal" ], "technologyProperties": { "investigatorModel": "Internal" } }, "external": { "technologies": [ "External-investigator verifier", "Chain-of-custody VC" ], "technologies_comment": "", "technologyProperties": { "investigatorModel": "External" } }, "tiered": { "technologies": [ "Tiered-investigator routing", "Escalation smart-contract" ], "technologyProperties": { "investigatorModel": "Tiered" } } }, "prefillFrom": null, "briefSection": "Investigator model", "text": "Who investigates submitted reports?", "ngoText": "Who investigates submitted reports?" }, { "id": "wb-cross-org", "type": "select", "options": [ { "label": "No, single-org channel", "value": "single" }, { "label": "Yes, consortium-wide common channel", "value": "consortium" }, { "label": "Yes, with external-oversight escalation (regulator, ombudsman)", "value": "oversight" } ], "propertyMapping": { "single": { "technologies": [ "Single-org submission platform" ], "technologyProperties": { "crossOrg": "No" } }, "consortium": { "technologies": [ "Consortium-shared channel", "Cross-org routing smart-contract", "Multi-org trust framework" ], "technologyProperties": { "crossOrg": "Consortium" } }, "oversight": { "technologies": [ "External-oversight bridge", "Regulator-verifier integration" ], "technologyProperties": { "crossOrg": "Oversight" } } }, "prefillFrom": null, "briefSection": "Cross-org", "text": "Do reports need to be routable to other agencies (consortium-wide whistleblowing)?", "ngoText": "Do reports need to be routable to other agencies (consortium-wide whistleblowing)?" } ], "complexityFactors": { "relationships": 3, "operationalChange": 3, "dataCompliance": 4 }, "complexityNotes": [ "Identity model", "Integrity guarantees required", "Retention span", "Cross-organisation routing" ], "suggestedCriteria": [ { "id": "SC-WHISTLE-INTEGRITY", "name": "Report integrity and tamper-evidence", "description": "Whistleblower reports are cryptographically sealed at submission with a tamper-evident audit log. Without integrity guarantees, the channel cannot be trusted to whistleblowers.", "weight": 0.3, "ratingGuide": { "5": "On-chain hash with timestamp; any modification visible. Independent verification possible.", "4": "Strong audit log; modifications logged but not cryptographically prevented.", "3": "Standard application audit; trust in the operator.", "2": "Limited audit; modifications not consistently logged.", "1": "No tamper-evidence." } }, { "id": "SC-WHISTLE-ANONYMITY", "name": "Reporter anonymity protection", "description": "Whistleblowers can report without exposing identity to the institution being reported. Anonymity is the functional requirement.", "weight": 0.25, "ratingGuide": { "5": "Cryptographic anonymity; metadata also protected; legal counsel mediated.", "4": "Pseudonymous reporting; metadata limited.", "3": "Anonymous web form; metadata captured for ops.", "2": "Hotline with PII captured 'for follow-up'.", "1": "Direct identification required." } }, { "id": "SC-WHISTLE-INDEPENDENT", "name": "Independent oversight integration", "description": "Reports are forwarded automatically to independent oversight (board ombudsperson, external counsel). Without independent eyes, internal capture is the failure mode.", "weight": 0.2, "ratingGuide": { "5": "Reports auto-forwarded to multiple independent reviewers; no internal-only path possible.", "4": "Independent reviewer involved by default; can be bypassed in clear cases.", "3": "Independent review for serious cases; routine reports handled internally.", "2": "Independent review on request only.", "1": "All reports handled internally." } }, { "id": "SC-WHISTLE-RETALIATION", "name": "Retaliation protection mechanism", "description": "The system actively protects reporters from retaliation through structural design (not just policy). Retaliation is the dominant failure mode of internal whistleblower channels.", "weight": 0.15, "ratingGuide": { "5": "Reporter identity never reaches the institution; complete cryptographic separation.", "4": "Reporter identity protected by procedural firewall and HR policy.", "3": "Policy-based protection; vulnerability exists.", "2": "Limited protection; legal counsel only on serious cases.", "1": "No structural protection." } }, { "id": "SC-WHISTLE-USABILITY", "name": "Reporter accessibility", "description": "People who can need to report (staff, beneficiaries, partners) actually use the channel. An inaccessible channel is theatre.", "weight": 0.1, "ratingGuide": { "5": "Multi-channel (web, app, SMS, voice); multi-language; trained intake.", "4": "Multi-channel; accessibility tested.", "3": "Web form and email; basic accessibility.", "2": "Single-channel; limited accessibility.", "1": "Hard to find; reports rare." } } ], "procurement": { "marketMaturity": "emerging", "primaryMode": "rfq", "alternativeModes": [ "off-the-shelf" ], "reasoning": "Whistleblower channel SaaS market is growing.", "exampleProductCategories": [ "whistleblower-platform", "ethics-reporting-saas" ], "partnerChannels": [], "lastReviewed": "2026-05-01" } }, { "id": "UC-B-039", "name": "Cross-agency credential portability for humanitarian workforce", "category": "B", "subcategory": "Interagency Workforce Credentials", "description": "Let humanitarian staff carry verified qualifications between agencies, so a secondment or surge deployment does not mean every credential is checked again.", "bCriteria": [ "B1", "B3", "B6", "B7" ], "requiredComponents": [ { "component": "credential-issuance", "description": "Verifiable credentials issued by HR, training providers, certification bodies, and clearance agencies covering qualifications, safeguarding training, background checks, and deployment history" }, { "component": "verification-mechanism", "description": "Instant verification by new employer (UN agency, INGO, local partner) without contacting each issuer" }, { "component": "holder-app", "description": "Staff wallet for credential storage and selective disclosure" }, { "component": "interoperability-layer", "description": "W3C VC + DID framework enabling cross-organisation credential recognition" }, { "component": "identity-verification", "description": "Staff DID anchored to government or strong HR identity" } ], "conditionalComponents": [ { "component": "privacy-tech", "condition": "If sensitive attestations (medical clearance, vaccination status, PSEA history) need selective disclosure" }, { "component": "consent-management", "condition": "For staff-controlled disclosure to potential new employers" } ], "crossCategoryDependencies": [ "UC-B-029 for single-org staff credential verification \u2014 this UC extends the pattern cross-organisation", "UC-B-031 for health worker / teacher credential portability (beneficiary-facing analog)", "UC-E-076 for partner capacity verification where workforce credentials are part of the assessment" ], "p2TriggerConditions": { "description": "Activated for organisations with material inter-organisation staff mobility (surge rosters, secondments, cluster deployments) and high hire-volume where credential re-verification is burdensome.", "rangeSignals": [ "interOrgStaffMobility >= regular", "annualHireVolume >= material", "surgeRosterParticipation == true" ] }, "contextFieldsTemplate": [ { "field": "workforceMobility", "source": "P2 CatB / P0 Q18", "description": "Frequency of staff movement between agencies" }, { "field": "hireVolumeAnnual", "source": "P0 Q7 + P2 CatB", "description": "Annual hires requiring credential verification" }, { "field": "credentialTypes", "source": "P0 HR", "description": "Categories of credentials in scope" }, { "field": "consortiumMembership", "source": "P0 Q18", "description": "Cluster, consortium, or surge-roster participation" } ], "implementationComplexity": "high", "examples": { "note": "Cross-agency workforce credential portability \u2014 building on established VC infrastructure (UNDP LACChain) and enterprise credential-portability patterns (Velocity Network).", "references": [ { "name": "UNDP LACChain workforce credentials", "url": "https://www.lacchain.net/", "solved": "UN agency live blockchain-network pilot for academic and workforce credential portability across Latin American member states" }, { "name": "Velocity Network Foundation", "url": "https://www.velocitynetwork.foundation/", "solved": "Enterprise workforce credential portability standard adoptable by humanitarian consortia; employers issue and accept credentials via shared layer" }, { "name": "Hyland Credentials (Learning Machine)", "url": "https://www.hylandcredentials.com/", "solved": "Mature VC issuance platform used by universities, training providers, and enterprise HR, a pattern applied to humanitarian training providers (DisasterReady, Kaya)" }, { "name": "ILO Skills Passport / refugee qualifications", "url": "https://www.ilo.org/skills/projects/skills-for-employment/lang--en/index.htm", "solved": "ILO and UNHCR work on portable skills credentials for refugee and displaced populations, a pattern adaptable to humanitarian workforce" } ] }, "solutionQuestions": [ { "id": "credentials-in-scope", "type": "select", "options": [ { "label": "Professional qualifications only (degrees, certs)", "value": "professional" }, { "label": "Professional + safeguarding / PSEA attestations", "value": "safeguarding" }, { "label": "Comprehensive (professional + safeguarding + clearance + deployment history + medical)", "value": "comprehensive" } ], "propertyMapping": { "professional": { "technologies": [ "Professional VC issuer", "University / institution DID registry" ], "technologyProperties": { "scope": "Professional", "complexity": "medium" } }, "safeguarding": { "technologies": [ "Multi-issuer VC platform", "Safeguarding registry" ], "technologyProperties": { "scope": "Professional + safeguarding", "complexity": "medium" } }, "comprehensive": { "technologies": [ "Enterprise VC platform", "Multi-source issuer network", "Selective-disclosure layer" ], "technologyProperties": { "scope": "Comprehensive", "complexity": "high" } } }, "prefillFrom": null, "briefSection": "Scope", "text": "Which credential types are in scope for cross-agency portability?", "ngoText": "Which credential types are in scope for cross-agency portability?" }, { "id": "portability-reach", "type": "select", "options": [ { "label": "Within a specific consortium (e.g., Start Network, ACT Alliance)", "value": "consortium" }, { "label": "UN-family agencies (UNHCR, UNICEF, WFP, UNDP, UNFPA)", "value": "un-family" }, { "label": "Full humanitarian ecosystem (UN + INGO + local partners)", "value": "ecosystem" } ], "propertyMapping": { "consortium": { "technologies": [ "Consortium-trust framework", "Consortium DID registry" ], "technologyProperties": { "reach": "Consortium" } }, "un-family": { "technologies": [ "UN inter-agency trust framework", "Cross-agency VC schema" ], "technologyProperties": { "reach": "UN family" } }, "ecosystem": { "technologies": [ "Humanitarian-wide trust registry", "Multi-tier VC interoperability", "Local-issuer accreditation layer" ], "technologyProperties": { "reach": "Ecosystem" } } }, "prefillFrom": null, "briefSection": "Reach", "text": "How far should portability extend?", "ngoText": "How far should portability extend?" }, { "id": "issuer-readiness", "type": "select", "options": [ { "label": "Mostly paper / PDF certificates today", "value": "paper" }, { "label": "Mixed: some digital certificates, some paper", "value": "mixed" }, { "label": "Mostly digital, some VC pilots", "value": "digital" } ], "propertyMapping": { "paper": { "technologies": [ "PDF-to-VC conversion pipeline", "Hash-anchor service" ], "technologyProperties": { "issuerReadiness": "Paper" } }, "mixed": { "technologies": [ "Hybrid VC issuance", "Multi-source aggregator" ], "technologyProperties": { "issuerReadiness": "Mixed" } }, "digital": { "technologies": [ "Native VC issuance SDK", "Enterprise issuer onboarding" ], "technologyProperties": { "issuerReadiness": "Digital" } } }, "prefillFrom": null, "briefSection": "Issuer readiness", "text": "How ready are credential issuers (HR departments, training providers) for VC issuance?", "ngoText": "How ready are credential issuers (HR departments, training providers) for VC issuance?" }, { "id": "staff-wallet-model", "type": "select", "options": [ { "label": "Cloud-custody wallet (agency-hosted)", "value": "cloud" }, { "label": "Self-custody mobile wallet", "value": "self" }, { "label": "Hybrid: self-custody with agency-assisted recovery", "value": "hybrid" } ], "propertyMapping": { "cloud": { "technologies": [ "Cloud VC wallet service", "Agency SSO integration" ], "technologyProperties": { "walletModel": "Cloud" } }, "self": { "technologies": [ "Mobile VC wallet app", "Secure-enclave key management" ], "technologyProperties": { "walletModel": "Self-custody" } }, "hybrid": { "technologies": [ "Self-custody mobile wallet", "Social recovery mechanism", "Agency backup service" ], "technologyProperties": { "walletModel": "Hybrid" } } }, "prefillFrom": null, "briefSection": "Holder model", "text": "How will staff hold their credentials?", "ngoText": "How will staff hold their credentials?" }, { "id": "verification-latency", "type": "select", "options": [ { "label": "Days acceptable", "value": "days" }, { "label": "Hours (emergency deployment)", "value": "hours" }, { "label": "Minutes (surge-roster activation)", "value": "minutes" } ], "propertyMapping": { "days": { "technologies": [ "Batch verification service" ], "technologyProperties": { "verificationSpeed": "Days" } }, "hours": { "technologies": [ "Real-time verifier API", "Cached credential service" ], "technologyProperties": { "verificationSpeed": "Hours" } }, "minutes": { "technologies": [ "Instant-verification DApp", "Pre-cached credential index", "Cryptographic presentation protocol" ], "technologyProperties": { "verificationSpeed": "Minutes" } } }, "prefillFrom": null, "briefSection": "Verification latency", "text": "How fast does verification need to be (onboarding speed)?", "ngoText": "How fast does verification need to be (onboarding speed)?" } ], "complexityFactors": { "relationships": 4, "operationalChange": 4, "dataCompliance": 4 }, "complexityNotes": [ "Credential breadth", "Portability reach (consortium / UN / ecosystem)", "Issuer VC readiness", "Verification-speed requirement" ], "suggestedCriteria": [ { "id": "SC-CRED-PORTABILITY", "name": "Cross-agency credential portability", "description": "Credentials issued by one agency (UNHCR, UNICEF, IOM) can be verified by another without re-enrolment. Portability is the use case's reason for existing.", "weight": 0.3, "ratingGuide": { "5": "Credentials portable across all major agencies; verification real-time.", "4": "Portable across most agencies; some require attestation handshake.", "3": "Bilateral portability; trilateral requires extra step.", "2": "Pilot portability; broader rollout pending.", "1": "Single-agency credential." } }, { "id": "SC-CRED-PRIVACY", "name": "Selective disclosure architecture", "description": "The credential system enables selective disclosure (prove a fact without revealing all attributes). Privacy is non-negotiable for vulnerable populations.", "weight": 0.25, "ratingGuide": { "5": "Zero-knowledge proofs; reveal only what verifier strictly needs.", "4": "Selective attribute disclosure; standard schemes.", "3": "Field-level redaction; verifier sees subset.", "2": "Limited redaction; full credential typically exposed.", "1": "All-or-nothing disclosure." } }, { "id": "SC-CRED-LIFECYCLE", "name": "Credential lifecycle management", "description": "The system handles issuance, rotation, revocation, and expiration cleanly. Lifecycle management is operationally critical.", "weight": 0.2, "ratingGuide": { "5": "Full lifecycle automation; revocation propagates immediately.", "4": "Automated issuance and rotation; revocation manual but quick.", "3": "Periodic lifecycle review; revocation by request.", "2": "Static credentials; lifecycle handled outside system.", "1": "No lifecycle management." } }, { "id": "SC-CRED-DECENTRAL", "name": "Holder-controlled architecture", "description": "Beneficiaries hold their credentials independently of any single agency. Holder control protects from agency capture and supports portability.", "weight": 0.15, "ratingGuide": { "5": "Beneficiary holds credentials in personal wallet; uses across agencies.", "4": "Beneficiary controls; agencies attest but don't hold.", "3": "Issuing agency holds; beneficiary copies on request.", "2": "Issuing agency primary holder; beneficiary peripheral.", "1": "Agency-controlled credential." } }, { "id": "SC-CRED-INTEROP", "name": "Standards conformance", "description": "The system conforms to credential interoperability standards (W3C VC, DID). Conformance is what makes future integration possible.", "weight": 0.1, "ratingGuide": { "5": "Full W3C VC + DID conformance; standards-based interop demonstrated.", "4": "Standards-based with minor extensions.", "3": "Inspired by standards; not strictly conformant.", "2": "Custom format with documented schema.", "1": "Proprietary format." } } ], "procurement": { "marketMaturity": "emerging", "primaryMode": "tender", "alternativeModes": [ "integrator-led" ], "reasoning": "Cross-agency credential portability has emerging product market.", "exampleProductCategories": [ "humanitarian-workforce-credentialing", "interagency-credentials-rails" ], "partnerChannels": [], "lastReviewed": "2026-05-01" } }, { "id": "UC-F-091", "name": "Pooled fund disbursement tracking (UN-managed funds)", "category": "F", "subcategory": "Pooled Fund Management", "description": "Track money from UN pooled funds and similar pooled grants down to the final recipients, so you can meet donor audit requirements.", "bCriteria": [ "B3", "B4", "B7" ], "requiredComponents": [ { "component": "payment-rails", "description": "Disbursement rail from pool manager to implementing agencies with each hop recorded" }, { "component": "audit-mechanism", "description": "Tamper-evident fund-flow ledger: donor \u2192 pool \u2192 implementing agency \u2192 sub-grantee \u2192 field \u2192 beneficiaries" }, { "component": "smart-contracts", "description": "Programmatic release conditions tied to milestones, allocation rules, and audit events" }, { "component": "identity-verification", "description": "Agency and sub-grantee DIDs with pool-membership credentials" }, { "component": "multi-sig", "description": "Multi-party authorisation for allocation and disbursement decisions" } ], "conditionalComponents": [ { "component": "privacy-tech", "condition": "If operational-sensitive transfer paths must remain confidential while aggregate flows remain auditable" }, { "component": "oracle-data", "condition": "For linking field evidence (distribution events, beneficiary counts) to disbursement triggers" } ], "crossCategoryDependencies": [ "UC-F-080 for transparent fund-flow tracking \u2014 general pattern, this UC is pooled-fund-specific", "UC-F-084 for automated donor reporting that consumes this UC's flow data", "UC-E-077 for consortium fund allocation where pool membership overlaps with consortium" ], "p2TriggerConditions": { "description": "Activated for NGOs participating in UN pooled funds (CERF, CBPFs, MPTFO) or receiving institutional pooled funding, particularly where disbursement tracking is a donor audit requirement.", "rangeSignals": [ "pooledFundParticipation == true", "unSubGranteeStatus == true", "donorAuditIntensity >= moderate" ] }, "contextFieldsTemplate": [ { "field": "pooledFundsReceived", "source": "P0 Q15 + P2 CatF", "description": "List of active pooled funds" }, { "field": "annualDisbursementVolume", "source": "P0 Q14a + P2 CatF", "description": "Annual pooled-fund volume" }, { "field": "subGranteeCount", "source": "P0 Q17b", "description": "Onward sub-grantee count" }, { "field": "poolGovernanceRole", "source": "P2 CatE", "description": "Observer, member, or manager role in pool governance" } ], "implementationComplexity": "high", "examples": { "note": "Pooled-fund disbursement tracking \u2014 active area for UN system experimentation, with UNICEF CERF pilots and MPTFO interest.", "references": [ { "name": "UN Multi-Partner Trust Fund Office (MPTFO)", "url": "https://mptf.undp.org/", "solved": "Existing pooled-fund infrastructure that blockchain would augment with real-time flow visibility and cryptographic allocation proofs" }, { "name": "UNICEF CERF rapid-response tracking", "url": "https://www.unocha.org/cerf", "solved": "Pooled-fund use case with strict rapid-allocation and audit requirements, a target operating model for blockchain-anchored tracking" }, { "name": "IATI standard (International Aid Transparency Initiative)", "url": "https://iatistandard.org/", "solved": "Target reporting standard that blockchain-anchored flow data would satisfy natively" }, { "name": "WFP Building Blocks", "url": "https://innovation.wfp.org/project/building-blocks", "solved": "Showed in practice that blockchain-anchored humanitarian disbursement works at scale (cash transfers in Jordan); extensible to pooled-fund settlement patterns" } ] }, "solutionQuestions": [ { "id": "pooledfund-depth", "type": "select", "options": [ { "label": "First-tier only (pool \u2192 agency)", "value": "tier1" }, { "label": "Second-tier (pool \u2192 agency \u2192 sub-grantee)", "value": "tier2" }, { "label": "Full chain to beneficiary (pool \u2192 agency \u2192 sub-grantee \u2192 field \u2192 beneficiary)", "value": "full" } ], "propertyMapping": { "tier1": { "technologies": [ "First-tier disbursement ledger" ], "technologyProperties": { "depth": "Tier 1", "complexity": "medium" } }, "tier2": { "technologies": [ "Multi-tier disbursement ledger", "Sub-grantee DID registry" ], "technologyProperties": { "depth": "Tier 2", "complexity": "high" } }, "full": { "technologies": [ "End-to-end disbursement platform", "Beneficiary identity layer integration (see UC-B-024)" ], "technologyProperties": { "depth": "Full chain", "complexity": "very high" } } }, "prefillFrom": null, "briefSection": "Depth", "text": "How deep into the sub-grantee chain does disbursement tracking need to go?", "ngoText": "How deep into the sub-grantee chain does disbursement tracking need to go?" }, { "id": "pooledfund-release-logic", "type": "select", "options": [ { "label": "Manual approval by pool manager", "value": "manual" }, { "label": "Milestone-triggered (released on evidence)", "value": "milestone" }, { "label": "Hybrid (milestone + manual override for sensitive cases)", "value": "hybrid" } ], "propertyMapping": { "manual": { "technologies": [ "Manual approval portal", "Multi-sig approval layer" ], "technologyProperties": { "releaseLogic": "Manual" } }, "milestone": { "technologies": [ "Milestone smart-contract", "Evidence-oracle integration" ], "technologyProperties": { "releaseLogic": "Milestone" } }, "hybrid": { "technologies": [ "Hybrid release smart-contract", "Override governance layer" ], "technologyProperties": { "releaseLogic": "Hybrid" } } }, "prefillFrom": null, "briefSection": "Release logic", "text": "How are disbursements released?", "ngoText": "How are disbursements released?" }, { "id": "pooledfund-audience", "type": "select", "options": [ { "label": "Pool governance body (internal)", "value": "internal" }, { "label": "Pool governance + external donor audit", "value": "external" }, { "label": "Public transparency (IATI-compliant public register)", "value": "public" } ], "propertyMapping": { "internal": { "technologies": [ "Pool-member verifier portal" ], "technologyProperties": { "auditAudience": "Pool-internal" } }, "external": { "technologies": [ "External-auditor verifier", "Selective-disclosure proofs" ], "technologyProperties": { "auditAudience": "External" } }, "public": { "technologies": [ "Public disbursement dashboard", "IATI-bridge exporter" ], "technologyProperties": { "auditAudience": "Public" } } }, "prefillFrom": null, "briefSection": "Audit audience", "text": "Who audits the disbursement ledger?", "ngoText": "Who audits the disbursement ledger?" }, { "id": "pooledfund-confidentiality", "type": "select", "options": [ { "label": "Full transparency", "value": "transparent" }, { "label": "Transparent aggregates, confidential specific transfers (e.g., sensitive contexts)", "value": "hybrid" }, { "label": "Confidential ledger with aggregate attestations", "value": "confidential" } ], "propertyMapping": { "transparent": { "technologies": [ "Public ledger" ], "technologyProperties": { "confidentiality": "None" } }, "hybrid": { "technologies": [ "Hybrid ledger", "Selective-disclosure commitment scheme" ], "technologyProperties": { "confidentiality": "Hybrid" } }, "confidential": { "technologies": [ "Permissioned ledger", "Zero-knowledge aggregate proofs" ], "technologyProperties": { "confidentiality": "Full" } } }, "prefillFrom": null, "briefSection": "Confidentiality", "text": "What confidentiality applies to individual transfers?", "ngoText": "What confidentiality applies to individual transfers?" }, { "id": "pooledfund-donor-dashboard", "type": "select", "options": [ { "label": "Periodic reports (existing IATI format)", "value": "report" }, { "label": "Real-time dashboard (donor-facing)", "value": "dashboard" }, { "label": "Donor-embedded verifier (donor runs their own verification)", "value": "embedded" } ], "propertyMapping": { "report": { "technologies": [ "Report generator", "IATI exporter" ], "technologyProperties": { "donorInterface": "Report" } }, "dashboard": { "technologies": [ "Donor dashboard app", "Live disbursement API" ], "technologyProperties": { "donorInterface": "Dashboard" } }, "embedded": { "technologies": [ "Donor verifier SDK", "Cryptographic proof library" ], "technologyProperties": { "donorInterface": "Embedded" } } }, "prefillFrom": null, "briefSection": "Donor interface", "text": "What donor interface is required?", "ngoText": "What donor interface is required?" } ], "complexityFactors": { "relationships": 5, "operationalChange": 4, "dataCompliance": 3 }, "complexityNotes": [ "Disbursement depth (tiers tracked)", "Release logic automation", "Audit audience breadth", "Confidentiality tiering" ], "suggestedCriteria": [ { "id": "SC-POOLED-ALLOCATION", "name": "Allocation transparency", "description": "Pooled-fund allocation decisions (which agency, which crisis) are recorded with the rationale. Allocation transparency is what donors require.", "weight": 0.3, "ratingGuide": { "5": "Every allocation recorded with rationale, evidence, and approver. Donor-auditable.", "4": "Allocations recorded with summary rationale.", "3": "Periodic allocation reports.", "2": "Annual allocation summary.", "1": "Allocation rationale not systematically captured." } }, { "id": "SC-POOLED-FLOW", "name": "Disbursement flow tracking", "description": "Donors can trace pooled-fund money from contribution through allocation to operational use. End-to-end traceability is the structural test.", "weight": 0.25, "ratingGuide": { "5": "Real-time donor-to-implementation tracing; lot-level for cash, line-item for in-kind.", "4": "Quarterly tracing reports; lot-level summaries.", "3": "Annual trace reports; aggregate-level.", "2": "Custodian-only visibility; donors see summaries.", "1": "Disbursement details opaque to donors." } }, { "id": "SC-POOLED-MULTI-DONOR", "name": "Multi-donor reporting structure", "description": "The system handles the actual reporting needs of CERF, CBPFs, and MPTFO (different formats, periodicity, depth). Multi-donor handling is the operational test.", "weight": 0.2, "ratingGuide": { "5": "Donor-specific report templates auto-generated from canonical record. Each donor served in their format.", "4": "Common record; donor-specific exports semi-automated.", "3": "Common record; manual report generation per donor.", "2": "Per-donor data silos; reconciliation manual.", "1": "Each donor handled separately end-to-end." } }, { "id": "SC-POOLED-SPEED", "name": "Disbursement speed", "description": "The system supports rapid disbursement when crisis events trigger. CERF's rapid-response window is one of its core values.", "weight": 0.15, "ratingGuide": { "5": "Trigger-to-disbursement under 72 hours; documented track record.", "4": "Under one week typical.", "3": "Under two weeks typical.", "2": "Variable; weeks to months.", "1": "Speed not a feature." } }, { "id": "SC-POOLED-COMPLIANCE", "name": "Donor compliance and safeguarding", "description": "The system supports donor-specific compliance requirements (sanctions screening, due diligence, safeguarding). Compliance failures lose donors.", "weight": 0.1, "ratingGuide": { "5": "Automated screening; documented compliance per donor; auditable.", "4": "Screening per allocation; compliance reviewed annually.", "3": "Manual screening at onboarding; periodic review.", "2": "Compliance largely manual.", "1": "Compliance ad-hoc." } } ], "procurement": { "marketMaturity": "nascent", "primaryMode": "consortium", "alternativeModes": [ "integrator-led" ], "reasoning": "Pooled fund disbursement (CERF, CBPFs) is interagency-led; consortium fits.", "exampleProductCategories": [ "pooled-fund-platform", "interagency-finance-rails" ], "partnerChannels": [], "lastReviewed": "2026-05-01" } }, { "id": "UC-I-115", "name": "Co-financed measurement and verification registry (multi-funder climate and conservation programmes)", "category": "I", "subcategory": "Multi-funder measurement and verification", "description": "Keep one shared record of results from climate and conservation programmes with several funders, so each funder sees its share and no result is counted twice.", "bCriteria": [ "B3", "B4", "B6", "B7" ], "requiredComponents": [ { "component": "audit-mechanism", "description": "Tamper-evident registry of MRV (Monitoring, Reporting, Verification) events across multiple funders" }, { "component": "oracle-data", "description": "Remote-sensing feeds (carbon-rating and satellite analytics providers), field-verification, IoT sensors" }, { "component": "credential-issuance", "description": "MRV verifier credentials (Verra VCS, Gold Standard, Plan Vivo)" }, { "component": "smart-contracts", "description": "Double-counting prevention logic across multiple funder allocations" }, { "component": "identity-verification", "description": "Funder, implementer, and verifier DIDs" } ], "conditionalComponents": [ { "component": "privacy-tech", "condition": "If competitively-sensitive methodology details must remain confidential while outcomes remain verifiable" }, { "component": "iot-sensors", "condition": "For continuous field-level monitoring (soil carbon, biomass, water)" } ], "crossCategoryDependencies": [ "UC-E-073 for Cross-NGO beneficiary coordination \u2014 this UC extends the coordination pattern to climate outcomes", "UC-F-080 for fund-flow tracking \u2014 complements MRV with funding provenance", "UC-I-112 (and surrounding Cat I UCs) for single-funder MRV that this UC federates" ], "p2TriggerConditions": { "description": "Activated for organisations running climate, conservation, or reforestation programmes with multiple funders / carbon buyers, particularly where double-counting or attribution conflicts have been an issue.", "rangeSignals": [ "climateProgrammeActive == true", "multiFunderCoFinancing == true", "carbonOrCreditIssuance == true" ] }, "contextFieldsTemplate": [ { "field": "programmeTypes", "source": "P2 CatI", "description": "Reforestation, peatland restoration, clean cookstoves, etc." }, { "field": "funderCount", "source": "P0 Q15 + P2 CatI", "description": "Number of distinct funders / buyers" }, { "field": "mrvStandard", "source": "P2 CatI", "description": "Verra VCS, Gold Standard, Plan Vivo, bespoke" }, { "field": "verificationModality", "source": "P2 CatI", "description": "Remote-sensing, field, hybrid" } ], "implementationComplexity": "high", "examples": { "note": "Multi-funder MRV \u2014 active emerging pattern in carbon markets; applicable to climate-finance co-financing between aid donors and carbon buyers.", "references": [ { "name": "Pachama", "url": "https://pachama.com/", "solved": "Remote-sensing MRV platform with blockchain-anchored attestations; pattern for multi-funder evidence aggregation" }, { "name": "Sylvera", "url": "https://www.sylvera.com/", "solved": "Independent rating of carbon projects with evidence-anchoring approach applicable to NGO co-financing" }, { "name": "Verra VCS registry", "url": "https://verra.org/programs/verified-carbon-standard/", "solved": "Target verification standard; emerging blockchain-bridge pilots for cross-registry federation" }, { "name": "Plan Vivo blockchain pilots", "url": "https://www.planvivo.org/", "solved": "Standards body with active pilots for anchoring MRV evidence, a useful pattern for NGO-facing climate programmes" } ] }, "solutionQuestions": [ { "id": "mrv-funder-count", "type": "select", "options": [ { "label": "2-3 (small co-financing arrangement)", "value": "small" }, { "label": "4-10 (mid-scale pool)", "value": "medium" }, { "label": "10+ (large co-financing or carbon-market scale)", "value": "large" } ], "propertyMapping": { "small": { "technologies": [ "Shared MRV ledger", "Multi-funder attestation" ], "technologyProperties": { "funderScale": "Small" } }, "medium": { "technologies": [ "Federated MRV platform", "Cross-funder allocation smart-contract" ], "technologyProperties": { "funderScale": "Medium" } }, "large": { "technologies": [ "Enterprise multi-funder MRV platform", "Registry federation layer", "Automated allocation reconciliation" ], "technologyProperties": { "funderScale": "Large" } } }, "prefillFrom": null, "briefSection": "Funder scale", "text": "How many distinct funders / buyers co-finance the programme?", "ngoText": "How many distinct funders / buyers co-finance the programme?" }, { "id": "mrv-evidence-source", "type": "select", "options": [ { "label": "Field verification only", "value": "field" }, { "label": "Remote-sensing only (satellite, aerial)", "value": "remote" }, { "label": "Hybrid (remote + field + IoT + community)", "value": "hybrid" } ], "propertyMapping": { "field": { "technologies": [ "Field-verification app", "Verifier credential issuance" ], "technologyProperties": { "evidenceSource": "Field" } }, "remote": { "technologies": [ "Remote-sensing integration (carbon-rating and satellite analytics providers)" ], "technologyProperties": { "evidenceSource": "Remote-sensing" } }, "hybrid": { "technologies": [ "Multi-source aggregation platform", "Remote + field + IoT feeds", "Community attestation layer" ], "technologyProperties": { "evidenceSource": "Hybrid" } } }, "prefillFrom": null, "briefSection": "Evidence", "text": "What MRV evidence sources do you need to aggregate?", "ngoText": "What MRV evidence sources do you need to aggregate?" }, { "id": "mrv-double-count-risk", "type": "select", "options": [ { "label": "Low: funders cover different outcomes", "value": "low" }, { "label": "Moderate: overlapping outcome claims possible", "value": "moderate" }, { "label": "High: funders claim same outcomes (carbon credits)", "value": "high" } ], "propertyMapping": { "low": { "technologies": [ "Simple allocation ledger" ], "technologyProperties": { "doubleCountRisk": "Low" } }, "moderate": { "technologies": [ "Allocation smart-contract", "Exclusive-claim registry" ], "technologyProperties": { "doubleCountRisk": "Moderate" } }, "high": { "technologies": [ "Carbon-registry federation layer", "Retirement smart-contract", "Cross-registry reconciliation" ], "technologyProperties": { "doubleCountRisk": "High" } } }, "prefillFrom": null, "briefSection": "Double-count", "text": "How significant is double-counting risk across funders?", "ngoText": "How significant is double-counting risk across funders?" }, { "id": "mrv-verifier-model", "type": "select", "options": [ { "label": "Single third-party verifier (e.g. Verra VVB)", "value": "single-verifier" }, { "label": "Multi-verifier consensus", "value": "multi-verifier" }, { "label": "Community + verifier hybrid", "value": "community-hybrid" } ], "propertyMapping": { "single-verifier": { "technologies": [ "Single-verifier credential issuance" ], "technologyProperties": { "verifierModel": "Single" } }, "multi-verifier": { "technologies": [ "Multi-verifier credential aggregation", "Consensus smart-contract" ], "technologyProperties": { "verifierModel": "Multi-consensus" } }, "community-hybrid": { "technologies": [ "Community attestation credential", "Verifier-weighted scoring", "Hybrid consensus" ], "technologyProperties": { "verifierModel": "Hybrid" } } }, "prefillFrom": null, "briefSection": "Verifier model", "text": "Who verifies outcomes?", "ngoText": "Who verifies outcomes?" }, { "id": "mrv-disclosure", "type": "select", "options": [ { "label": "Aggregated public disclosure (anonymised)", "value": "aggregate" }, { "label": "Full public disclosure (open MRV)", "value": "full-public" }, { "label": "Funder-private, public aggregate", "value": "hybrid" } ], "propertyMapping": { "aggregate": { "technologies": [ "Public aggregate dashboard" ], "technologyProperties": { "disclosure": "Aggregate" } }, "full-public": { "technologies": [ "Public MRV registry", "Open-data exporter" ], "technologyProperties": { "disclosure": "Full public" } }, "hybrid": { "technologies": [ "Hybrid disclosure model", "Funder-only verifier portal", "Public aggregate" ], "technologyProperties": { "disclosure": "Hybrid" } } }, "prefillFrom": null, "briefSection": "Disclosure", "text": "What disclosure level applies to MRV evidence?", "ngoText": "What disclosure level applies to MRV evidence?" } ], "complexityFactors": { "relationships": 5, "operationalChange": 4, "dataCompliance": 3 }, "complexityNotes": [ "Funder count", "Evidence-source integration", "Double-counting risk level", "Verifier-consensus model" ], "suggestedCriteria": [ { "id": "SC-MRV-DATA", "name": "MRV data integrity", "description": "Monitoring, reporting, and verification data is captured with measurement traceability and tamper-evidence. MRV integrity is the carbon market's foundation.", "weight": 0.3, "ratingGuide": { "5": "Sensor-anchored real-time data; cryptographic seals on every measurement; field equipment certified.", "4": "Calibrated equipment; periodic data integrity audits.", "3": "Standard measurement equipment; data review periodic.", "2": "Spot measurements; gaps interpolated.", "1": "Estimates rather than measurements." } }, { "id": "SC-MRV-MULTI-FUNDER", "name": "Multi-funder reporting", "description": "The registry handles co-financed projects with multiple funders, each requiring distinct attribution. Co-financing is the use case's defining feature.", "weight": 0.25, "ratingGuide": { "5": "Per-funder attribution at every measurement; auto-generated reports.", "4": "Funder attribution at project level; report aggregation.", "3": "Project-level attribution; funder reports manual.", "2": "Funder attribution by separate ledger; reconciliation manual.", "1": "Single-funder optimisation; co-financing handled outside." } }, { "id": "SC-MRV-VERIFICATION", "name": "Independent verifier integration", "description": "Independent verifiers (registry standards bodies and independent carbon-rating providers) are integrated into the system as attestors. Without independent verification, the market doesn't accept the credits.", "weight": 0.2, "ratingGuide": { "5": "Multiple verifiers integrated; their attestations on-chain.", "4": "Primary verifier integrated; others by reference.", "3": "Verifier reports referenced; not directly integrated.", "2": "Verifier reports kept separately; cross-reference manual.", "1": "No verifier integration." } }, { "id": "SC-MRV-TIME", "name": "Time-series fidelity", "description": "The system maintains time-series fidelity (continuous measurements vs sampled snapshots). Carbon claims are time-bound.", "weight": 0.15, "ratingGuide": { "5": "Continuous measurement; minute-resolution data preserved.", "4": "Daily resolution; continuous monitoring infrastructure.", "3": "Weekly or monthly snapshots; gaps interpolated.", "2": "Quarterly snapshots; significant interpolation.", "1": "Annual snapshots only." } }, { "id": "SC-MRV-COMMUNITY", "name": "Community attribution and benefit-sharing", "description": "The registry tracks community-level attribution and benefit-sharing for projects (especially indigenous-led). Without community attribution, the credit lacks legitimacy.", "weight": 0.1, "ratingGuide": { "5": "Community-level attribution at every project; benefit-share recorded.", "4": "Project-level community attribution; benefit-share documented.", "3": "Community attribution policy; tracking variable.", "2": "Community attribution informal.", "1": "Community attribution absent." } } ], "procurement": { "marketMaturity": "nascent", "primaryMode": "consortium", "alternativeModes": [ "integrator-led" ], "reasoning": "Co-financed MRV registries are research-stage interagency efforts.", "exampleProductCategories": [ "mrv-registry-platform", "climate-finance-consortium-rails" ], "partnerChannels": [], "lastReviewed": "2026-05-01" } }, { "id": "UC-D-074", "name": "Pooled humanitarian commodity claims and replenishment (UN humanitarian response depots, World Food Programme hubs)", "category": "D", "subcategory": "Shared Logistics Infrastructure", "description": "Record claims on, and refills of, shared humanitarian stockpiles, so each agency can see what it drew and what it owes.", "bCriteria": [ "B1", "B3", "B4", "B7" ], "requiredComponents": [ { "component": "audit-mechanism", "description": "Tamper-evident commodity ledger. Each drawdown, delivery, and replenishment recorded" }, { "component": "smart-contracts", "description": "Claim allocation, replenishment rules, settlement calculations" }, { "component": "identity-verification", "description": "Member-agency DIDs with drawdown entitlements" }, { "component": "oracle-data", "description": "Inventory feeds from physical stockpile management systems" }, { "component": "payment-rails", "description": "Inter-agency settlement rail for replenishment" } ], "conditionalComponents": [ { "component": "iot-sensors", "condition": "For cold-chain or condition monitoring of specific commodity classes" }, { "component": "privacy-tech", "condition": "If member-agency operational details (quantities drawn per crisis) must remain confidential while aggregate pool integrity is verifiable" } ], "crossCategoryDependencies": [ "UC-D-065 for warehouse inventory management \u2014 this UC extends across multiple-owner warehouses", "UC-D-068 (and surrounding Cat D UCs) for single-org logistics \u2014 this UC federates", "UC-E-074 for cluster coordination records where UNHRD / WFP hubs are part of cluster logistics" ], "p2TriggerConditions": { "description": "Activated for agencies that access shared humanitarian stockpiles (UNHRD depots, WFP Global Logistics Cluster hubs, regional pre-positioning arrangements) or manage them for others.", "rangeSignals": [ "sharedStockpileAccess == true", "humanitarianResponseParticipation == true", "clusterLogisticsMembership == true" ] }, "contextFieldsTemplate": [ { "field": "stockpilesAccessed", "source": "P2 CatD", "description": "List of shared stockpiles used" }, { "field": "annualDrawdownVolume", "source": "P2 CatD", "description": "Approximate volume of shared commodity drawdown" }, { "field": "replenishmentModel", "source": "P2 CatD", "description": "In-kind, cash, or credit-based replenishment" }, { "field": "governanceRole", "source": "P0 Q18", "description": "Member, user, or manager role" } ], "implementationComplexity": "high", "examples": { "note": "Pooled humanitarian commodity operations \u2014 live at UNHRD; blockchain would formalise claim/replenishment integrity currently handled through operational trust and reconciliation.", "references": [ { "name": "UN Humanitarian Response Depot (UNHRD)", "url": "https://unhrd.org/", "solved": "Existing shared humanitarian stockpile infrastructure, the target operating model that the blockchain integrity layer augments" }, { "name": "WFP Global Logistics Cluster", "url": "https://logcluster.org/", "solved": "Cluster-coordinated logistics including shared warehousing; pattern for multi-agency commodity tracking" }, { "name": "Kuehne Foundation humanitarian supply chain research", "url": "https://www.kuehne-stiftung.org/", "solved": "Research and practical pilots for humanitarian-logistics blockchain applications" }, { "name": "IFRC pre-positioning network", "url": "https://www.ifrc.org/", "solved": "Decentralised national-society pre-positioning pattern with inter-society settlement, a live use case for blockchain-anchored claims" } ] }, "solutionQuestions": [ { "id": "commodity-pool-scope", "type": "select", "options": [ { "label": "Single stockpile (e.g., UNHRD Brindisi only)", "value": "single" }, { "label": "Multiple hubs under single operator (UNHRD network)", "value": "multi-same-operator" }, { "label": "Multiple pools across operators (UNHRD + WFP + national)", "value": "multi-operator" } ], "propertyMapping": { "single": { "technologies": [ "Single-pool ledger" ], "technologyProperties": { "scope": "Single" } }, "multi-same-operator": { "technologies": [ "Multi-hub federated ledger" ], "technologyProperties": { "scope": "Multi-hub" } }, "multi-operator": { "technologies": [ "Cross-operator interoperability layer", "Federated claim ledger" ], "technologyProperties": { "scope": "Multi-operator" } } }, "prefillFrom": null, "briefSection": "Scope", "text": "How many stockpiles / hubs does the agency interact with?", "ngoText": "How many stockpiles / hubs does the agency interact with?" }, { "id": "commodity-drawdown-volume", "type": "select", "options": [ { "label": "Low (<50 tonnes or 500 tonnes or USD 1M+)", "value": "high" } ], "propertyMapping": { "low": { "technologies": [ "Basic drawdown ledger" ], "technologyProperties": { "volume": "Low" } }, "moderate": { "technologies": [ "Standard commodity ledger", "Scheduled reconciliation" ], "technologyProperties": { "volume": "Moderate" } }, "high": { "technologies": [ "Enterprise commodity platform", "Real-time reconciliation", "Multi-commodity sharding" ], "technologyProperties": { "volume": "High" } } }, "prefillFrom": null, "briefSection": "Volume", "text": "What is the annual drawdown volume?", "ngoText": "What is the annual drawdown volume?" }, { "id": "commodity-replenishment", "type": "select", "options": [ { "label": "In-kind (replace what you take)", "value": "in-kind" }, { "label": "Cash-based (pay for drawdowns)", "value": "cash" }, { "label": "Hybrid (credit-based with periodic reconciliation)", "value": "hybrid" } ], "propertyMapping": { "in-kind": { "technologies": [ "In-kind tracking ledger" ], "technologyProperties": { "replenishment": "In-kind" } }, "cash": { "technologies": [ "Cash-settlement ledger", "Payment-rail integration" ], "technologyProperties": { "replenishment": "Cash" } }, "hybrid": { "technologies": [ "Credit ledger", "Periodic reconciliation smart-contract", "Multi-mode settlement" ], "technologyProperties": { "replenishment": "Hybrid" } } }, "prefillFrom": null, "briefSection": "Replenishment", "text": "How is commodity replenishment handled?", "ngoText": "How is commodity replenishment handled?" }, { "id": "commodity-integrity-events", "type": "select", "options": [ { "label": "Drawdown and return only", "value": "basic" }, { "label": "Drawdown + return + expiry / condition changes", "value": "moderate" }, { "label": "Full (drawdown, return, expiry, condition, quality, cold-chain, recall)", "value": "full" } ], "propertyMapping": { "basic": { "technologies": [ "Basic event ledger" ], "technologyProperties": { "integrity": "Basic" } }, "moderate": { "technologies": [ "Extended event ledger", "Condition-monitoring integration" ], "technologyProperties": { "integrity": "Moderate" } }, "full": { "technologies": [ "Comprehensive event platform", "IoT integration", "Quality-attestation layer" ], "technologyProperties": { "integrity": "Full" } } }, "prefillFrom": null, "briefSection": "Integrity", "text": "Which integrity events must be tracked?", "ngoText": "Which integrity events must be tracked?" }, { "id": "commodity-audit-audience", "type": "select", "options": [ { "label": "Pool manager only", "value": "manager" }, { "label": "Pool manager + member agencies", "value": "members" }, { "label": "Pool + members + donors + public (full transparency)", "value": "public" } ], "propertyMapping": { "manager": { "technologies": [ "Manager portal" ], "technologyProperties": { "auditAudience": "Manager" } }, "members": { "technologies": [ "Multi-member verifier", "Role-based disclosure" ], "technologyProperties": { "auditAudience": "Members" } }, "public": { "technologies": [ "Public commodity dashboard", "Multi-audience verifier" ], "technologyProperties": { "auditAudience": "Public" } } }, "prefillFrom": null, "briefSection": "Audit", "text": "Who audits pool integrity?", "ngoText": "Who audits pool integrity?" } ], "complexityFactors": { "relationships": 4, "operationalChange": 4, "dataCompliance": 3 }, "complexityNotes": [ "Stockpile/hub count", "Drawdown volume", "Replenishment model", "Integrity-event scope" ], "suggestedCriteria": [ { "id": "SC-COMMODITY-CLAIMS", "name": "Claim-tracking integrity", "description": "Pooled humanitarian commodity claims are recorded with cryptographic seals at every handoff (storage, distribution, replenishment). Claim integrity is the central operational concern.", "weight": 0.3, "ratingGuide": { "5": "Every claim cryptographically anchored; full audit trail.", "4": "Claims tracked digitally; key handoffs signed.", "3": "Claims logged; periodic reconciliation.", "2": "Manual claim ledger.", "1": "Claims handled per-incident." } }, { "id": "SC-COMMODITY-MULTI-PARTY", "name": "Multi-agency coordination fitness", "description": "The system handles UNHRD, WFP Hubs, and other humanitarian commodity custodians with consistent cross-agency views. Multi-agency consistency is the use case's reason.", "weight": 0.25, "ratingGuide": { "5": "All major custodians integrated; real-time cross-agency view.", "4": "Most custodians integrated; periodic sync.", "3": "Bilateral integrations; trilateral requires extra step.", "2": "Pilot integrations only.", "1": "Single-agency view." } }, { "id": "SC-COMMODITY-REPLENISH", "name": "Replenishment automation", "description": "The system automates replenishment cycles based on consumption signals. Manual replenishment is the operational pain.", "weight": 0.2, "ratingGuide": { "5": "Auto-triggered replenishment with donor confirmation; documented track record.", "4": "Replenishment alerts auto-generated; ordering manual but fast.", "3": "Periodic stock review; manual replenishment.", "2": "Reactive replenishment after stockout.", "1": "Replenishment ad-hoc." } }, { "id": "SC-COMMODITY-PROVENANCE", "name": "Provenance attestation chain", "description": "The system maintains provenance attestation from donor or supplier through to recipient. Provenance closes the trust loop.", "weight": 0.15, "ratingGuide": { "5": "Provenance from origin to recipient; verifiable at any step.", "4": "Provenance to distribution; recipient-side verification weaker.", "3": "Origin and major handoffs documented.", "2": "Origin documented; intermediate handoffs gap.", "1": "Provenance not tracked." } }, { "id": "SC-COMMODITY-FIELD", "name": "Field operations robustness", "description": "The system works in the actual conditions of UN warehousing (rapid mobilisation, austere environments, high churn). Field durability is binding.", "weight": 0.1, "ratingGuide": { "5": "Field-tested at scale; austere-environment proven; high turnover handled.", "4": "Field-tested; some friction in austere environments.", "3": "Designed for field conditions; limited live testing.", "2": "Office-grade with field adaptation.", "1": "Not field-fit." } } ], "procurement": { "marketMaturity": "nascent", "primaryMode": "consortium", "alternativeModes": [ "integrator-led" ], "reasoning": "UNHRD-style pooled commodity claims are research-stage in interagency form.", "exampleProductCategories": [ "humanitarian-commodity-platform", "pooled-fund-platform" ], "partnerChannels": [], "lastReviewed": "2026-05-01" } }, { "id": "UC-E-084", "name": "Shared implementing-partner due diligence and sanctions screening", "category": "E", "subcategory": "Multi-Agency Partner Due Diligence", "description": "Let agencies in a consortium share the results of partner checks and sanctions screening, so each partner is vetted once instead of by every agency.", "bCriteria": [ "B3", "B4", "B6", "B7" ], "requiredComponents": [ { "component": "audit-mechanism", "description": "Tamper-evident DD record. Each agency's findings about a partner contribute to a shared record" }, { "component": "credential-issuance", "description": "DD-outcome credentials (risk rating, sanctions screen, governance check)" }, { "component": "identity-verification", "description": "Partner DIDs with verifiable legal identity" }, { "component": "smart-contracts", "description": "Sanctions-screening rule execution; renewal and expiry logic" }, { "component": "oracle-data", "description": "Sanctions list feeds (OFAC, UN, EU), corporate registry data" } ], "conditionalComponents": [ { "component": "privacy-tech", "condition": "If individual agency findings must remain confidential while aggregate DD status is shareable" }, { "component": "consent-management", "condition": "For partner-controlled disclosure of DD findings to potential new funder agencies" } ], "crossCategoryDependencies": [ "UC-E-076 for local partner capacity verification \u2014 DD is a superset of capacity", "UC-F-090 for donor identity verification \u2014 same underlying DID / VC infrastructure", "UC-E-077 for consortium fund allocation that depends on DD outcomes" ], "p2TriggerConditions": { "description": "Activated for agencies working through implementing partners with sanctions-compliance obligations and where DD duplication across consortium members is a known cost.", "rangeSignals": [ "partnerHeavyDelivery == true", "sanctionsComplianceObligation == true", "consortiumMembership >= active" ] }, "contextFieldsTemplate": [ { "field": "partnerCount", "source": "P0 Q17b", "description": "Implementing-partner count" }, { "field": "ddFrequency", "source": "P2 CatE", "description": "Current DD refresh cadence" }, { "field": "sanctionsRegimes", "source": "P0 Q21", "description": "OFAC, UN, EU, national obligations" }, { "field": "ddSharingAppetite", "source": "P0 Q19", "description": "Willingness to share DD findings with peer agencies" } ], "implementationComplexity": "medium", "examples": { "note": "Shared DD infrastructure \u2014 emerging pattern in consortium working groups; target of BOND and NetHope discussions.", "references": [ { "name": "BOND NGO due-diligence working group", "url": "https://www.bond.org.uk/groups/due-diligence", "solved": "UK INGO network with active discussion of shared DD; target standard the blockchain platform would implement" }, { "name": "NetHope partner verification initiatives", "url": "https://nethope.org/", "solved": "Technical NGO network with active work on partner-verification tooling across member agencies" }, { "name": "FCDO due-diligence guidance for partners", "url": "https://www.gov.uk/government/publications/due-diligence-for-funded-work", "solved": "Donor standard for DD; target compliance the shared DD platform must achieve" }, { "name": "UN Global Compact partner-risk model", "url": "https://www.unglobalcompact.org/", "solved": "Multi-stakeholder risk framework applicable to humanitarian partner DD" } ] }, "solutionQuestions": [ { "id": "dd-scope", "type": "select", "options": [ { "label": "Sanctions screening only", "value": "sanctions" }, { "label": "Sanctions + corporate registry + basic governance", "value": "basic" }, { "label": "Comprehensive (sanctions + governance + financial + safeguarding + track record)", "value": "comprehensive" } ], "propertyMapping": { "sanctions": { "technologies": [ "Sanctions screening service", "Sanctions-outcome credential" ], "technologyProperties": { "scope": "Sanctions", "complexity": "low" } }, "basic": { "technologies": [ "DD-aggregator platform", "Multi-source credential issuance" ], "technologyProperties": { "scope": "Basic", "complexity": "medium" } }, "comprehensive": { "technologies": [ "Enterprise DD platform", "Multi-dimension credential schema", "Findings-contribution smart-contract" ], "technologyProperties": { "scope": "Comprehensive", "complexity": "high" } } }, "prefillFrom": null, "briefSection": "Scope", "text": "Which DD domains are in scope for sharing?", "ngoText": "Which DD domains are in scope for sharing?" }, { "id": "dd-consortium-reach", "type": "select", "options": [ { "label": "Small consortium (2-5 peer agencies)", "value": "small" }, { "label": "Medium consortium (6-15 agencies)", "value": "medium" }, { "label": "Sector-wide (16+ agencies or UN-family)", "value": "sector" } ], "propertyMapping": { "small": { "technologies": [ "Small-consortium trust framework" ], "technologyProperties": { "reach": "Small" } }, "medium": { "technologies": [ "Multi-party trust framework", "Role-based contribution rules" ], "technologyProperties": { "reach": "Medium" } }, "sector": { "technologies": [ "Sector-wide trust registry", "Multi-tier contribution model" ], "technologyProperties": { "reach": "Sector-wide" } } }, "prefillFrom": null, "briefSection": "Reach", "text": "Which agencies contribute to and consume shared DD?", "ngoText": "Which agencies contribute to and consume shared DD?" }, { "id": "dd-finding-sensitivity", "type": "select", "options": [ { "label": "Open: all findings shared as-is", "value": "open" }, { "label": "Outcome-shared, evidence-confidential", "value": "outcome-only" }, { "label": "Tiered (outcome public, evidence per-agency only)", "value": "tiered" } ], "propertyMapping": { "open": { "technologies": [ "Open findings ledger" ], "technologyProperties": { "sensitivity": "Open" } }, "outcome-only": { "technologies": [ "Selective-disclosure VC", "Outcome-attestation layer" ], "technologyProperties": { "sensitivity": "Outcome-only" } }, "tiered": { "technologies": [ "Tiered disclosure schema", "Per-agency evidence store" ], "technologyProperties": { "sensitivity": "Tiered" } } }, "prefillFrom": null, "briefSection": "Sensitivity", "text": "How are agency-specific DD findings handled?", "ngoText": "How are agency-specific DD findings handled?" }, { "id": "dd-refresh-model", "type": "select", "options": [ { "label": "Annual blanket refresh", "value": "annual" }, { "label": "Risk-based (high-risk partners more often)", "value": "risk-based" }, { "label": "Continuous monitoring (real-time sanctions + event-triggered)", "value": "continuous" } ], "propertyMapping": { "annual": { "technologies": [ "Annual refresh scheduler" ], "technologyProperties": { "refresh": "Annual" } }, "risk-based": { "technologies": [ "Risk-tier refresh logic", "Adaptive scheduler" ], "technologyProperties": { "refresh": "Risk-based" } }, "continuous": { "technologies": [ "Continuous-monitoring smart-contract", "Real-time sanctions oracle", "Event-triggered alerts" ], "technologyProperties": { "refresh": "Continuous" } } }, "prefillFrom": null, "briefSection": "Refresh", "text": "How often is DD refreshed?", "ngoText": "How often is DD refreshed?" }, { "id": "dd-partner-control", "type": "select", "options": [ { "label": "No, agency-only visibility", "value": "agency-only" }, { "label": "Partial, partner sees rating but not findings", "value": "partial" }, { "label": "Full: partner holds DD credential and presents selectively", "value": "full" } ], "propertyMapping": { "agency-only": { "technologies": [ "Agency-side DD portal" ], "technologyProperties": { "partnerControl": "None" } }, "partial": { "technologies": [ "Partner-status portal", "Restricted disclosure" ], "technologyProperties": { "partnerControl": "Partial" } }, "full": { "technologies": [ "Partner VC wallet", "Partner-controlled disclosure", "Trust-framework recognition" ], "technologyProperties": { "partnerControl": "Full" } } }, "prefillFrom": null, "briefSection": "Partner control", "text": "Can the partner itself see and present their DD status?", "ngoText": "Can the partner itself see and present their DD status?" } ], "complexityFactors": { "relationships": 4, "operationalChange": 3, "dataCompliance": 4 }, "complexityNotes": [ "DD scope breadth", "Consortium reach", "Finding-sensitivity model", "Refresh model (annual vs continuous)" ], "suggestedCriteria": [ "B3", "B4", "B6", "B7" ], "procurement": { "marketMaturity": "emerging", "primaryMode": "consortium", "alternativeModes": [ "integrator-led" ], "reasoning": "Shared partner due diligence benefits from consortium structures.", "exampleProductCategories": [ "due-diligence-consortium-platform", "sanctions-screening-shared-saas" ], "partnerChannels": [], "lastReviewed": "2026-05-01" } }, { "id": "UC-C-053", "name": "Livestock traceability for pastoralists", "category": "C", "subcategory": "Cross-Border Supply Chain Provenance", "description": "Keep a record of each animal's vaccinations and movements that buyers and border officials accept, so herders can sell across borders.", "bCriteria": [ "B2", "B3", "B5" ], "requiredComponents": [ { "component": "animal-id", "description": "Per-animal identifier (ear tag, RFID bolus, or muzzle biometric)" }, { "component": "attestation-ledger", "description": "Shared ledger for vaccination, ownership transfer, and movement events" }, { "component": "cooperative-anchor", "description": "Cooperative-mediated identity layer for pastoralist households" }, { "component": "offline-capture", "description": "Field-capable offline data capture for veterinary and market events" }, { "component": "cross-border-bridge", "description": "Cross-border attestation read access for neighbouring states' livestock services" } ], "conditionalComponents": [ { "component": "halal-chain", "condition": "If exporting to Gulf meat markets" }, { "component": "insurance-payout", "condition": "If livestock insurance is bundled", "linksTo": "UC-E-072" }, { "component": "smart-contracts", "condition": "If automated payout on attested loss" } ], "crossCategoryDependencies": [ "UC-B-024 if cooperative-mediated identity required", "UC-E-072 if parametric livestock insurance is part of solution" ], "p2TriggerConditions": { "description": "Activated when P0 indicates pastoralist beneficiaries + cross-border operating geography + agricultural / livelihoods focus", "rangeSignals": [ "primaryBeneficiary contains 'Pastoralists'", "operatingContext in {post_conflict, active_conflict, mixed}", "primarySectors includes livestock or agriculture" ] }, "contextFieldsTemplate": [ { "field": "beneficiaryGroup", "source": "P0 NGO-P0-S1-Q9", "description": "Pastoralist sub-population characteristics" }, { "field": "operatingContext", "source": "P0 NGO-P0-S1-Q3", "description": "FCV context shapes data risk" }, { "field": "crossBorderCorridors", "source": "P0 NGO-P0-S1-Q7", "description": "Which neighbouring states' livestock services need to read" }, { "field": "connectivity", "source": "P0 NGO-P0-S3-Q13", "description": "Field connectivity for offline-first design" }, { "field": "powerContext", "source": "P0 NGO-P0-S3-Q13b", "description": "Power constraints for device charging" }, { "field": "cooperativeStructure", "source": "P0 NGO-P0-S5-Q17a", "description": "Cooperative anchor for member-level attestation" } ], "implementationComplexity": "high", "examples": { "note": "Tadamon cohort UC. Limited mature precedent; partial precedents include FAO digital livestock identification pilots, AgriDigital provenance, and IsDB-funded pastoralist insurance schemes.", "references": [ { "name": "FAO digital livestock identification (Africa)", "url": "https://www.fao.org/animal-production/en/", "solved": "Animal-level identification standards for vaccination tracking" }, { "name": "AU-IBAR cross-border SOPs", "url": "https://www.au-ibar.org/", "solved": "Cross-border movement coordination for pastoralist livestock" } ] }, "solutionQuestions": [ { "id": "herd-scale", "type": "select", "options": [ { "label": "Fewer than 1,000 animals", "value": "under-1000" }, { "label": "1,000 to 10,000 animals", "value": "1k-10k" }, { "label": "10,000 to 100,000 animals", "value": "10k-100k" }, { "label": "Over 100,000 animals", "value": "over-100k" } ], "propertyMapping": { "under-1000": { "technologies": [ "Lightweight tag system, manual scan" ], "technologyProperties": { "scaleClass": "small", "tagBudget": "$1-3 per animal" } }, "1k-10k": { "technologies": [ "RFID ear tag with cooperative scanning station" ], "technologyProperties": { "scaleClass": "medium", "tagBudget": "$3-5 per animal" } }, "10k-100k": { "technologies": [ "RFID + cooperative aggregation hub", "Mobile vet scanning" ], "technologyProperties": { "scaleClass": "large", "tagBudget": "$2-4 per animal at volume" } }, "over-100k": { "technologies": [ "RFID + cooperative aggregation hub", "Centralised scanning at markets" ], "technologyProperties": { "scaleClass": "national", "tagBudget": "Tender-driven" } } } }, { "id": "tagging-method", "type": "select", "options": [ { "label": "Printed ear tag with batch ID", "value": "ear-tag-printed" }, { "label": "Rumen RFID bolus", "value": "rfid-bolus" }, { "label": "Electronic ear tag (RFID)", "value": "rfid-eartag" }, { "label": "Muzzle biometric capture", "value": "muzzle-biometric" } ], "propertyMapping": { "ear-tag-printed": { "technologies": [ "Printed ear tags", "Mobile QR scanner" ], "technologyProperties": { "durability": "1-3 years", "tamperResistance": "low" } }, "rfid-bolus": { "technologies": [ "Rumen bolus", "Handheld RFID reader" ], "technologyProperties": { "durability": "lifetime", "tamperResistance": "high \u2014 internal placement" } }, "rfid-eartag": { "technologies": [ "RFID ear tag", "Handheld RFID reader" ], "technologyProperties": { "durability": "5-10 years", "tamperResistance": "medium" } }, "muzzle-biometric": { "technologies": [ "Muzzle biometric capture (smartphone)" ], "technologyProperties": { "durability": "lifetime", "tamperResistance": "high \u2014 biometric" } } } }, { "id": "cross-border-corridors", "type": "select", "options": [ { "label": "Operations are not cross-border", "value": "none" }, { "label": "Two neighbouring states", "value": "two-states" }, { "label": "Three or more neighbouring states", "value": "three-plus" }, { "label": "Cross-border movement passes through contested or active-conflict zones", "value": "contested" } ], "propertyMapping": { "none": { "technologies": [ "Single-state ledger" ], "technologyProperties": { "crossBorder": "no" } }, "two-states": { "technologies": [ "Bilateral ledger read access" ], "technologyProperties": { "crossBorder": "bilateral" } }, "three-plus": { "technologies": [ "Multi-state ledger consortium" ], "technologyProperties": { "crossBorder": "multilateral", "governanceComplexity": "high" } }, "contested": { "technologies": [ "Off-chain detail, on-chain anchor only" ], "technologyProperties": { "crossBorder": "contested", "honestNoTrigger": "review protection threat model before deploy" } } } }, { "id": "attestation-authority", "type": "multi-select", "options": [ { "label": "Government veterinary service", "value": "vet-service" }, { "label": "Cooperative or producer association", "value": "cooperative" }, { "label": "Implementing CSO", "value": "ngo" }, { "label": "Private veterinary practitioners", "value": "private-vet" }, { "label": "Livestock market authority", "value": "market-authority" } ] }, { "id": "market-destination", "type": "select", "options": [ { "label": "Local markets only", "value": "local-only" }, { "label": "National markets and slaughter", "value": "national" }, { "label": "Regional export (Gulf, neighbouring states)", "value": "regional-export" }, { "label": "Global export with halal certification", "value": "global-export" } ], "propertyMapping": { "local-only": { "technologies": [ "Basic provenance" ], "technologyProperties": { "halalChain": "no" } }, "national": { "technologies": [ "Provenance + slaughter attestation" ], "technologyProperties": { "halalChain": "no" } }, "regional-export": { "technologies": [ "Provenance + halal slaughter chain" ], "technologyProperties": { "halalChain": "yes \u2014 Gulf standards", "regulatoryReview": "SANIPES-equivalent" } }, "global-export": { "technologies": [ "Provenance + halal chain + global cert" ], "technologyProperties": { "halalChain": "yes \u2014 global standards", "regulatoryReview": "OIE + halal certification body" } } } }, { "id": "insurance-bundled", "type": "select", "options": [ { "label": "No insurance bundled", "value": "no" }, { "label": "Planning to add insurance later", "value": "planned" }, { "label": "Yes, parametric livestock insurance", "value": "yes-parametric" }, { "label": "Yes, indemnity insurance with attested loss", "value": "yes-indemnity" } ], "propertyMapping": { "no": { "technologies": [], "technologyProperties": { "insuranceLayer": "none" } }, "planned": { "technologies": [ "Reserve insurance integration capacity" ], "technologyProperties": { "insuranceLayer": "planned" } }, "yes-parametric": { "technologies": [ "Parametric oracle (rainfall, vegetation index)" ], "technologyProperties": { "insuranceLayer": "parametric", "linksTo": "UC-E-072" } }, "yes-indemnity": { "technologies": [ "Loss attestation workflow", "Veterinary verification" ], "technologyProperties": { "insuranceLayer": "indemnity" } } } }, { "id": "connectivity-field", "type": "select", "options": [ { "label": "Smartphone with mobile data at field sites", "value": "smartphone-data" }, { "label": "Smartphone with SMS only at field sites", "value": "smartphone-sms" }, { "label": "Feature phone (USSD/SMS) only", "value": "feature-phone" }, { "label": "Mostly offline, data uploaded at urban hubs", "value": "offline-only" } ], "propertyMapping": { "smartphone-data": { "technologies": [ "Native mobile app with sync" ], "technologyProperties": { "offlineFirst": "soft" } }, "smartphone-sms": { "technologies": [ "SMS-confirmation app + offline cache" ], "technologyProperties": { "offlineFirst": "yes" } }, "feature-phone": { "technologies": [ "USSD interface", "Cooperative-mediated entry" ], "technologyProperties": { "offlineFirst": "yes", "uxLayer": "USSD" } }, "offline-only": { "technologies": [ "Offline-first PWA", "Store-and-forward sync" ], "technologyProperties": { "offlineFirst": "hard", "syncWindow": "weekly+" } } } }, { "id": "data-minimisation-position", "type": "select", "options": [ { "label": "Strict, only animal-level data on-chain, no household location", "value": "strict" }, { "label": "Aggregated cooperative-level data on-chain", "value": "aggregated" }, { "label": "Animal + household + grazing-route data on-chain", "value": "full-context" }, { "label": "Not yet decided, needs threat model", "value": "undecided" } ], "propertyMapping": { "strict": { "technologies": [ "Animal-only on-chain", "Off-chain household record" ], "technologyProperties": { "protectionRating": "strong" } }, "aggregated": { "technologies": [ "Cooperative-mediated identity" ], "technologyProperties": { "protectionRating": "moderate" } }, "full-context": { "technologies": [ "Full provenance on-chain" ], "technologyProperties": { "protectionRating": "weak", "honestNoTrigger": "review protection threat model in FCV contexts" } }, "undecided": { "technologies": [ "Hold until decision" ], "technologyProperties": { "protectionRating": "unknown", "blockerForDeploy": "yes \u2014 must decide before any deploy" } } } }, { "id": "vaccination-integration", "type": "select", "options": [ { "label": "No vaccination integration", "value": "none" }, { "label": "Manual logging of vaccination events", "value": "manual" }, { "label": "Integrated with national vaccination campaign system", "value": "integrated" }, { "label": "Integrated with FAO / AU-IBAR programmes", "value": "integrated-fao" } ] } ], "_solutionQuestionsStatus": "v0.1 \u2014 authored 2026-04-24 NGO-040 follow-up; depth 8-12 questions per UC focused on decision-relevant choices; additional questions can be added as the cohort surfaces gaps", "complexityFactors": { "relationships": 5, "operationalChange": 4, "dataCompliance": 4 }, "complexityNotes": { "relationships": "Cooperative + veterinary service + cross-border state coordination + buyer / insurer / regulator. Five-party minimum.", "data": "Sensitive household-asset data; requires data minimisation in FCV contexts. Honest-no triggers if Q3 indicates active conflict and protection threat model is poorly specified.", "dependencies": "Physical tagging precondition; certification-authority engagement; cross-border legal framework." }, "securityTier": "A", "suggestedCriteria": [ { "id": "SC-LIVESTOCK-IDENTITY", "name": "Animal identification fidelity", "description": "Each tracked animal has a unique, verifiable identifier that holds up in field conditions (pastoralist mobility, dust, harsh weather). Identifier fidelity is the trace's anchor.", "weight": 0.3, "ratingGuide": { "5": "RFID, biometric (muzzle pattern), or tamper-evident ear tag with field-readable verification. Backup identifier present.", "4": "Single robust identifier per animal; field readable.", "3": "Ear tag or simple RFID; durability variable.", "2": "Visual tag; high replacement rate.", "1": "No persistent identifier." } }, { "id": "SC-LIVESTOCK-VETERINARY", "name": "Veterinary attestation pathway", "description": "Veterinary events (vaccinations, treatments, disease status) are recorded by attesting veterinary staff at point of contact. Without veterinary attestation, the chain has no health-event data.", "weight": 0.25, "ratingGuide": { "5": "Veterinary staff attest in-field via device. Cryptographic signing per event. Real-time chain update.", "4": "Veterinary records entered same-day from field notes; signed by vet.", "3": "Periodic batch update of veterinary events; signed at office.", "2": "Annual vaccination records; movement records absent.", "1": "No systematic veterinary record." } }, { "id": "SC-LIVESTOCK-CROSSBORDER", "name": "Cross-border movement handling", "description": "The system handles animals crossing national borders without losing record continuity. Cross-border handling is where centralised national systems fail.", "weight": 0.2, "ratingGuide": { "5": "Records portable across borders; receiving authorities verify on arrival; chain continues.", "4": "Receiving authorities can verify; records carry but slow re-issue.", "3": "Records carried as paper certificate at border crossing.", "2": "Border crossings result in record fragmentation.", "1": "No cross-border record continuity." } }, { "id": "SC-LIVESTOCK-MARKET", "name": "Market-side verification utility", "description": "Buyers and markets accept the credentials as basis for premium pricing or market access. Without market acceptance, the trace is operational overhead with no economic return.", "weight": 0.15, "ratingGuide": { "5": "Major buyers and export markets require credentials; documented price differential.", "4": "Some buyers accept credentials; price differential emerging.", "3": "Pilot buyer integration; market response uncertain.", "2": "Buyers aware of credentials but pricing unchanged.", "1": "Credentials are paperwork with no market value." } }, { "id": "SC-LIVESTOCK-OFFLINE", "name": "Offline-capable field operation", "description": "The system works where pastoralists actually are (low-connectivity, mobile, intermittent power). Field reality is the binding constraint.", "weight": 0.1, "ratingGuide": { "5": "Full offline-first design; sync when connectivity returns; local cryptographic verification possible.", "4": "Mostly offline; sync within hours of connectivity.", "3": "Online required for major events; offline for routine.", "2": "Limited offline capability; significant gaps when disconnected.", "1": "Online-only system; not field-fit." } } ], "tadamonCohort": true, "procurement": { "marketMaturity": "emerging", "primaryMode": "integrator-led", "alternativeModes": [ "rfq" ], "reasoning": "Livestock traceability with Tadamon framing benefits from cohort partner routing.", "exampleProductCategories": [ "livestock-traceability-platform", "pastoralist-records-rails" ], "partnerChannels": [ "tadamon" ], "lastReviewed": "2026-05-01" } }, { "id": "UC-D-075", "name": "Food voucher tokenisation", "category": "D", "subcategory": "Conditional Aid Distribution and Voucher Systems", "description": "Give families vouchers that can only be spent on eligible food at approved vendors, and settle vendors' claims without manual reconciliation.", "bCriteria": [ "B1", "B3", "B4" ], "requiredComponents": [ { "component": "voucher-token", "description": "Tokenised voucher with embedded restriction rules (eligible items, vendor whitelist, expiry, transferability)" }, { "component": "beneficiary-id", "description": "Beneficiary identifier for issuance and deduplication" }, { "component": "vendor-network", "description": "Enrolled vendor network with verification and reimbursement" }, { "component": "redemption-ux", "description": "Vendor-side redemption UX (app, SMS, USSD, QR, biometric) and offline support" }, { "component": "reconciliation-ledger", "description": "Audit trail for issuance, redemption, and donor reporting" } ], "conditionalComponents": [ { "component": "cluster-deduplication", "condition": "If multiple implementing partners share the geography" }, { "component": "veridian-integration", "condition": "If beneficiaries hold verifiable digital identity credentials", "linksTo": "UC-B-024" }, { "component": "smart-contracts", "condition": "If conditional release rules apply" } ], "crossCategoryDependencies": [ "UC-A-007 if pure cash transfer alternative is also evaluated", "UC-B-024 if portable beneficiary identity is the identifier layer" ], "p2TriggerConditions": { "description": "Activated when P2 shows in-kind / voucher distribution model, multiple implementing partners, vendor network of 20+", "rangeSignals": [ "distributionModel includes vouchers", "implementingPartners >= 2", "vendorNetworkSize >= 20" ] }, "contextFieldsTemplate": [ { "field": "voucherProgramme", "source": "P1 NGO-P1-S1-Q2", "description": "Whether voucher delivery is part of operational model" }, { "field": "vendorNetwork", "source": "P2 answers", "description": "Enrolled vendor count and reimbursement terms" }, { "field": "beneficiaryIdStrategy", "source": "P0 NGO-P0-S5-Q25b", "description": "Verifiable credential or alternative identifier" }, { "field": "clusterMembership", "source": "P0 NGO-P0-S4-Q24", "description": "Food Security Cluster participation" }, { "field": "connectivity", "source": "P0 NGO-P0-S3-Q13", "description": "Online vs offline redemption design" }, { "field": "regulatory", "source": "P0 NGO-P0-S6-Q21", "description": "Digital voucher regulatory permission" } ], "implementationComplexity": "medium-high", "examples": { "note": "Strong precedent in WFP Building Blocks (Jordan, Bangladesh), Oxfam UnBlocked Cash, and several IsDB-funded food security programmes.", "references": [ { "name": "WFP Building Blocks", "url": "https://www.wfp.org/building-blocks", "solved": "Cluster-level deduplication + voucher reconciliation at scale" }, { "name": "Oxfam UnBlocked Cash", "url": "https://www.oxfam.org/en/unblocked-cash-project-using-blockchain-technology-revolutionize-humanitarian-aid", "solved": "Voucher delivery in remote islands with offline redemption" } ] }, "solutionQuestions": [ { "id": "voucher-volume", "type": "select", "options": [ { "label": "Fewer than 1,000 households per cycle", "value": "under-1k" }, { "label": "1,000 to 10,000 households per cycle", "value": "1k-10k" }, { "label": "10,000 to 100,000 households per cycle", "value": "10k-100k" }, { "label": "Over 100,000 households per cycle", "value": "over-100k" } ], "propertyMapping": { "under-1k": { "technologies": [ "Lightweight token contract" ], "technologyProperties": { "scaleClass": "small" } }, "1k-10k": { "technologies": [ "Token contract + vendor reconciliation" ], "technologyProperties": { "scaleClass": "medium" } }, "10k-100k": { "technologies": [ "Token contract + cluster deduplication" ], "technologyProperties": { "scaleClass": "large" } }, "over-100k": { "technologies": [ "Token contract + cluster dedup + national integration" ], "technologyProperties": { "scaleClass": "national" } } } }, { "id": "vendor-network-size", "type": "select", "options": [ { "label": "Fewer than 20 enrolled vendors", "value": "under-20" }, { "label": "20 to 100 vendors", "value": "20-100" }, { "label": "100 to 500 vendors", "value": "100-500" }, { "label": "Over 500 vendors", "value": "over-500" } ], "propertyMapping": { "under-20": { "technologies": [ "Closed-loop voucher system (no blockchain needed)" ], "technologyProperties": { "blockchainFit": "weak \u2014 non-blockchain better" } }, "20-100": { "technologies": [ "Tokenised voucher with vendor app" ], "technologyProperties": { "blockchainFit": "moderate" } }, "100-500": { "technologies": [ "Tokenised voucher with vendor network platform" ], "technologyProperties": { "blockchainFit": "strong" } }, "over-500": { "technologies": [ "Tokenised voucher with multi-vendor platform" ], "technologyProperties": { "blockchainFit": "strong", "deduplicationValue": "high" } } } }, { "id": "redemption-ux", "type": "multi-select", "options": [ { "label": "Vendor smartphone app", "value": "vendor-app" }, { "label": "SMS confirmation code", "value": "sms-code" }, { "label": "USSD interface", "value": "ussd" }, { "label": "QR code at vendor", "value": "qr" }, { "label": "Beneficiary biometric", "value": "biometric" } ] }, { "id": "offline-redemption", "type": "select", "options": [ { "label": "Not required: vendor connectivity is reliable", "value": "not-required" }, { "label": "Required for intermittent connectivity", "value": "intermittent" }, { "label": "Required: frequent multi-day outages", "value": "frequent" }, { "label": "Default mode: assume offline, sync opportunistically", "value": "default" } ], "propertyMapping": { "not-required": { "technologies": [ "Online-only redemption" ], "technologyProperties": { "offlineCapability": "no" } }, "intermittent": { "technologies": [ "Online with offline fallback" ], "technologyProperties": { "offlineCapability": "soft" } }, "frequent": { "technologies": [ "Offline-first redemption + reconciliation" ], "technologyProperties": { "offlineCapability": "hard" } }, "default": { "technologies": [ "Offline-default with cryptographic settlement at sync" ], "technologyProperties": { "offlineCapability": "default" } } } }, { "id": "voucher-restrictions", "type": "multi-select", "options": [ { "label": "Eligible food items list", "value": "eligible-items" }, { "label": "Vendor whitelist", "value": "vendor-whitelist" }, { "label": "Expiry date", "value": "expiry" }, { "label": "Transferable within household", "value": "transferability-household" }, { "label": "Non-transferable", "value": "non-transferable" }, { "label": "Geographic restriction (specific markets)", "value": "geographic" } ] }, { "id": "beneficiary-identifier", "type": "select", "options": [ { "label": "New beneficiary ID issued by CSO", "value": "new-id" }, { "label": "National ID linkage", "value": "national-id" }, { "label": "Verifiable digital identity credential (if available)", "value": "veridian" }, { "label": "Biometric identifier", "value": "biometric" }, { "label": "Mobile phone number", "value": "phone-based" } ], "propertyMapping": { "new-id": { "technologies": [ "CSO-issued credentials" ], "technologyProperties": { "identityLayer": "csoIssued" } }, "national-id": { "technologies": [ "National ID lookup" ], "technologyProperties": { "identityLayer": "stateIssued", "exclusionRisk": "potentially-high" } }, "veridian": { "technologies": [ "Ledger-anchored verifiable credential" ], "technologyProperties": { "identityLayer": "veridian", "linksTo": "UC-B-040" } }, "biometric": { "technologies": [ "Biometric capture and verification" ], "technologyProperties": { "identityLayer": "biometric", "protectionConcern": "high" } }, "phone-based": { "technologies": [ "Phone number as ID" ], "technologyProperties": { "identityLayer": "phoneBased", "exclusionRisk": "moderate" } } } }, { "id": "cluster-deduplication", "type": "select", "options": [ { "label": "Single-implementer programme: no cluster overlap", "value": "none" }, { "label": "Manual cluster reconciliation", "value": "manual" }, { "label": "Planning shared deduplication with other partners", "value": "planned" }, { "label": "Active cluster-level deduplication via Food Security Cluster", "value": "active" } ] }, { "id": "donor-reporting-granularity", "type": "select", "options": [ { "label": "Statistical sampling", "value": "statistical" }, { "label": "Aggregate transaction reports", "value": "aggregate" }, { "label": "Transaction-level audit trail", "value": "transaction-level" }, { "label": "Real-time donor dashboard", "value": "real-time" } ] }, { "id": "regulatory-permission", "type": "select", "options": [ { "label": "Digital vouchers permitted explicitly", "value": "clear" }, { "label": "Operating under regulatory grace", "value": "operating-under-grace" }, { "label": "Regulatory status ambiguous", "value": "ambiguous" }, { "label": "Digital vouchers prohibited: programme cannot deploy", "value": "prohibited" } ], "propertyMapping": { "clear": { "technologies": [], "technologyProperties": { "regulatoryRisk": "low" } }, "operating-under-grace": { "technologies": [], "technologyProperties": { "regulatoryRisk": "moderate" } }, "ambiguous": { "technologies": [], "technologyProperties": { "regulatoryRisk": "high", "actionRequired": "regulatory engagement before deploy" } }, "prohibited": { "technologies": [], "technologyProperties": { "regulatoryRisk": "blocker", "honestNoTrigger": "yes" } } } } ], "_solutionQuestionsStatus": "v0.1 \u2014 authored 2026-04-24 NGO-040 follow-up; depth 8-12 questions per UC focused on decision-relevant choices; additional questions can be added as the cohort surfaces gaps", "complexityFactors": { "relationships": 4, "operationalChange": 3, "dataCompliance": 4 }, "complexityNotes": { "relationships": "CSO + donor + vendors + cluster partners + regulator. Reimbursement floats and vendor onboarding are operationally heavy.", "data": "Beneficiary identifier sensitivity; vendor transaction privacy. Cluster-level data sharing agreements required.", "dependencies": "Vendor enrolment scale; mobile / SMS reach at beneficiary level; donor approval for digital voucher instruments." }, "securityTier": "B", "suggestedCriteria": [ { "id": "SC-VOUCHER-RULES", "name": "Restriction-rule enforcement fidelity", "description": "The system enforces voucher restrictions (eligible items, vendor whitelist, expiry, household-internal transferability) automatically at point of use. Programmatic enforcement is the architectural advantage.", "weight": 0.3, "ratingGuide": { "5": "All restrictions enforced on-chain; vendor cannot accept non-compliant redemption.", "4": "Most restrictions enforced; complex rules need vendor confirmation.", "3": "Restrictions in policy; vendor-side checking via app or list.", "2": "Restrictions enforced post-hoc via reconciliation.", "1": "Restrictions advisory; enforcement manual." } }, { "id": "SC-VOUCHER-PORTABILITY", "name": "Recipient portability", "description": "Vouchers follow displaced or refugee recipients across borders, settlements, and service providers. Portability across agencies and settlements is the core differentiator of this pattern.", "weight": 0.25, "ratingGuide": { "5": "Vouchers fully portable across borders and service providers; recipient holds credentials independently.", "4": "Within-country portability strong; cross-border possible with handoffs.", "3": "Portable across NGOs in same camp/settlement; not cross-border.", "2": "Vouchers tied to specific operator; portability requires re-issue.", "1": "No portability." } }, { "id": "SC-VOUCHER-VENDOR", "name": "Vendor network capability", "description": "Vendor partners are technically capable of accepting tokenised vouchers in real-world conditions (intermittent connectivity, low-tech POS). Vendor capability is the binding constraint.", "weight": 0.2, "ratingGuide": { "5": "All vendors equipped; offline-capable acceptance with sync; multi-language.", "4": "Most vendors equipped; some offline capability.", "3": "Vendors mostly online-only; offline gaps cause refusal.", "2": "Vendor capability inconsistent; significant friction.", "1": "Vendors paper-only; tokenised approach not viable." } }, { "id": "SC-VOUCHER-RECONCILIATION", "name": "Reconciliation speed and accuracy", "description": "Voucher redemption is reconciled across vendors and donors quickly and accurately. Reconciliation friction is the operational pain that justifies the architecture.", "weight": 0.15, "ratingGuide": { "5": "Real-time reconciliation; automated dispute resolution; donor reports current.", "4": "Daily reconciliation; rare disputes resolved within hours.", "3": "Weekly reconciliation; some disputes take days.", "2": "Monthly reconciliation; disputes routine.", "1": "Periodic manual reconciliation; chronic disputes." } }, { "id": "SC-VOUCHER-PROTECTION", "name": "Beneficiary protection design", "description": "The system protects recipient privacy and safety, especially in FCV and refugee contexts. Protection is non-negotiable for the cohort.", "weight": 0.1, "ratingGuide": { "5": "Pseudonymous credentials; minimal data exposure to vendors; donor sees aggregates only.", "4": "Selective disclosure; vendor sees what's needed.", "3": "Standard data minimisation; some exposure to vendors.", "2": "Vendor sees full beneficiary profile.", "1": "Beneficiary identity widely exposed in the redemption flow." } } ], "tadamonCohort": true, "procurement": { "marketMaturity": "emerging", "primaryMode": "integrator-led", "alternativeModes": [ "tender" ], "reasoning": "Food voucher tokenisation has growing product market and Tadamon cohort routing.", "exampleProductCategories": [ "food-voucher-platform", "cash-and-voucher-saas" ], "partnerChannels": [ "tadamon" ], "lastReviewed": "2026-05-01" } }, { "id": "UC-C-054", "name": "Seed system integrity", "category": "C", "subcategory": "Agricultural Input Supply Chain Verification", "description": "Let farmers check that seed is genuine and certified, so counterfeit or wrongly labelled seed does not reach them.", "bCriteria": [ "B2", "B3" ], "requiredComponents": [ { "component": "certification-attestation", "description": "Certifying authority attestation per certified seed batch" }, { "component": "batch-marking", "description": "Unique batch ID printed or QR-tagged on seed packaging" }, { "component": "intermediate-attestation", "description": "Wholesaler and retailer receipt attestations forming a chain" }, { "component": "farmer-verification", "description": "Farmer-side verification UX (SMS, USSD, QR-plus-smartphone)" } ], "conditionalComponents": [ { "component": "tamper-evident-packaging", "condition": "If physical tampering is a known threat" }, { "component": "counterfeit-response", "condition": "If verification mismatch reporting is operational" } ], "crossCategoryDependencies": [ "UC-B-040 if farmer cooperative anchors the verification chain" ], "p2TriggerConditions": { "description": "Activated when P2 shows agricultural input supply chain + counterfeit problem + certification authority partnership", "rangeSignals": [ "primarySectors includes agriculture", "supplyChainProblem includes 'counterfeit' or 'adulterated'", "cropType includes hybrid cereals or certified pulses" ] }, "contextFieldsTemplate": [ { "field": "cropType", "source": "P2 answers", "description": "Which crops have material counterfeit problems" }, { "field": "certificationAuthority", "source": "P0 NGO-P0-S5-Q18", "description": "National seed certification body engagement" }, { "field": "agroDealerNetwork", "source": "P2 answers", "description": "Final-mile retail partner network" }, { "field": "farmerLiteracy", "source": "P0 NGO-P0-S1-Q9", "description": "Beneficiary literacy and device access" }, { "field": "connectivity", "source": "P0 NGO-P0-S3-Q13", "description": "Farmer-side verification reach" } ], "implementationComplexity": "medium", "examples": { "note": "Tadamon cohort UC. Partial precedents: Bayer Field View, Ghana Cocoa Board traceability pilots.", "references": [ { "name": "Ghana Cocoa Board traceability pilots", "url": "https://cocobod.gh/", "solved": "Crop-batch provenance from farm to export" }, { "name": "Bayer Field View digital agriculture", "url": "https://climate.com/", "solved": "Input verification for smallholders" } ] }, "solutionQuestions": [ { "id": "crop-type", "type": "multi-select", "options": [ { "label": "Hybrid cereals (maize, rice, sorghum hybrids)", "value": "hybrid-cereals" }, { "label": "Certified pulses (improved beans, lentils)", "value": "certified-pulses" }, { "label": "Vegetable hybrids", "value": "vegetable-hybrids" }, { "label": "Traditional / open-pollinated varieties", "value": "traditional" }, { "label": "Cash crops (cotton, coffee, tobacco)", "value": "cash-crop" } ] }, { "id": "counterfeit-severity", "type": "select", "options": [ { "label": "Not a material problem in our context", "value": "not-material" }, { "label": "Emerging concern", "value": "emerging" }, { "label": "Recurring problem affecting yield", "value": "recurring" }, { "label": "Widespread: major cause of yield failure", "value": "widespread" } ], "propertyMapping": { "not-material": { "technologies": [], "technologyProperties": { "blockchainFit": "weak \u2014 no problem to solve", "honestNoTrigger": "yes" } }, "emerging": { "technologies": [ "Lightweight verification" ], "technologyProperties": { "blockchainFit": "moderate" } }, "recurring": { "technologies": [ "Full provenance chain" ], "technologyProperties": { "blockchainFit": "strong" } }, "widespread": { "technologies": [ "Full provenance + counterfeit response process" ], "technologyProperties": { "blockchainFit": "strong", "responseProcessNeeded": "yes" } } } }, { "id": "certification-authority", "type": "select", "options": [ { "label": "National seed certification body engaged", "value": "national-engaged" }, { "label": "National authority receptive but not yet engaged", "value": "national-receptive" }, { "label": "Private certification (e.g. seed company internal)", "value": "private" }, { "label": "No certification authority available, would need to establish", "value": "none" } ], "propertyMapping": { "national-engaged": { "technologies": [ "Authority-attested batches" ], "technologyProperties": { "governanceStrength": "high" } }, "national-receptive": { "technologies": [ "Pilot pending engagement" ], "technologyProperties": { "governanceStrength": "moderate" } }, "private": { "technologies": [ "Private certification chain" ], "technologyProperties": { "governanceStrength": "moderate" } }, "none": { "technologies": [], "technologyProperties": { "governanceStrength": "blocker", "honestNoTrigger": "yes \u2014 authority required" } } } }, { "id": "batch-marking", "type": "select", "options": [ { "label": "Printed batch code on packaging", "value": "printed-code" }, { "label": "QR code on packaging", "value": "qr-code" }, { "label": "NFC tag on packaging", "value": "nfc" }, { "label": "Tamper-evident packaging with cryptographic seal", "value": "tamper-evident" } ] }, { "id": "intermediate-attestation-coverage", "type": "select", "options": [ { "label": "Certification authority only", "value": "certifier-only" }, { "label": "Certification + wholesaler", "value": "certifier-wholesaler" }, { "label": "Certification + wholesaler + retailer", "value": "full-chain" }, { "label": "Full chain + cooperative branch", "value": "full-plus-coop" } ] }, { "id": "farmer-verification-method", "type": "select", "options": [ { "label": "SMS verification (text the code)", "value": "sms" }, { "label": "USSD code lookup", "value": "ussd" }, { "label": "QR scan with smartphone", "value": "qr-smartphone" }, { "label": "Extension officer verifies on farmer's behalf", "value": "extension-officer" } ], "propertyMapping": { "sms": { "technologies": [ "SMS gateway" ], "technologyProperties": { "farmerDeviceFloor": "feature phone" } }, "ussd": { "technologies": [ "USSD service" ], "technologyProperties": { "farmerDeviceFloor": "feature phone" } }, "qr-smartphone": { "technologies": [ "QR + smartphone app" ], "technologyProperties": { "farmerDeviceFloor": "smartphone" } }, "extension-officer": { "technologies": [ "Officer-side app" ], "technologyProperties": { "farmerDeviceFloor": "none \u2014 proxy verification" } } } }, { "id": "agro-dealer-network", "type": "select", "options": [ { "label": "Formal national network", "value": "formal" }, { "label": "Cooperative-led retail", "value": "cooperative-led" }, { "label": "Informal retail (markets, individual sellers)", "value": "informal" }, { "label": "Mixed formal + informal", "value": "mixed" } ] }, { "id": "counterfeit-response-process", "type": "select", "options": [ { "label": "No formal process", "value": "none" }, { "label": "Internal CSO follow-up", "value": "internal-only" }, { "label": "Refer to regulator", "value": "regulatory-referral" }, { "label": "Public recall and regulator referral", "value": "public-recall" } ] } ], "_solutionQuestionsStatus": "v0.1 \u2014 authored 2026-04-24 NGO-040 follow-up; depth 8-12 questions per UC focused on decision-relevant choices; additional questions can be added as the cohort surfaces gaps", "complexityFactors": { "relationships": 4, "operationalChange": 3, "dataCompliance": 2 }, "complexityNotes": { "relationships": "Certification authority + seed companies + agro-dealers + farmer cooperatives. Authority engagement is the bottleneck.", "data": "Batch identifiers; not individually sensitive. Counterfeit reports may be commercially sensitive.", "dependencies": "Certification authority cooperation; agro-dealer incentive to participate; farmer device penetration." }, "securityTier": "B", "suggestedCriteria": [ { "id": "SC-SEED-CERTIFY", "name": "Certifying-authority attestation chain", "description": "Every batch of certified seed carries an attestation chain from the certifying authority through to the farmer's hand. Without this chain, the integrity claim is hollow.", "weight": 0.3, "ratingGuide": { "5": "Cryptographic attestation from authority through wholesaler, retailer, to farmer. Each step verifiable.", "4": "Authority signs batch certificate; retailer attests delivery; farmer verifies.", "3": "Authority certifies batch; downstream chain manual.", "2": "Authority issues paper certificate only.", "1": "Self-declaration by retailer or wholesaler." } }, { "id": "SC-SEED-FARMER-VERIFY", "name": "Farmer-side verification accessibility", "description": "Farmers can verify a seed pack's certification at point of purchase via their own device or low-tech channel (SMS, USSD, QR). Farmer verification is the user-side validation.", "weight": 0.25, "ratingGuide": { "5": "QR code on every pack; smartphone app or SMS verifies in seconds. Multi-language support.", "4": "QR code with verification app; SMS fallback for feature phones.", "3": "Code-based verification via SMS or USSD only.", "2": "Verification possible via call to authority or retailer.", "1": "No farmer-accessible verification." } }, { "id": "SC-SEED-COUNTERFEIT", "name": "Counterfeit detection rate", "description": "The system detects and surfaces counterfeit or mis-labelled batches in operation. Detection rate is the practical effectiveness measure.", "weight": 0.2, "ratingGuide": { "5": "Real-time detection of duplicate or expired codes; alerts to authority and farmers.", "4": "Counterfeit detection within days of market entry.", "3": "Periodic audits surface counterfeit batches.", "2": "Counterfeit detected only on farmer complaint.", "1": "No counterfeit detection mechanism." } }, { "id": "SC-SEED-CROSSBORDER", "name": "Cross-border verification consistency", "description": "The certification carries meaning when seeds cross borders. Cross-border seed trade is large and currently weakly verified.", "weight": 0.15, "ratingGuide": { "5": "Multi-jurisdiction recognition; receiving authority verifies; chain continues.", "4": "Bilateral recognition agreements; verification possible cross-border.", "3": "Domestic certification; cross-border traders carry paper certificates.", "2": "Cross-border certification handled by importing authority separately.", "1": "Cross-border certification fails or is not pursued." } }, { "id": "SC-SEED-ECONOMIC", "name": "Farmer income protection", "description": "Verifiable certification translates to measurable farmer income protection. Income protection is the ultimate outcome the system serves.", "weight": 0.1, "ratingGuide": { "5": "Documented reduction in counterfeit-related yield loss; documented price benefit for verified seed.", "4": "Anecdotal income improvement; price differential emerging.", "3": "Farmer satisfaction surveys positive; income data not yet collected.", "2": "Farmers value the system but income unchanged.", "1": "No measurable economic impact." } } ], "tadamonCohort": true, "procurement": { "marketMaturity": "nascent", "primaryMode": "integrator-led", "alternativeModes": [ "consortium" ], "reasoning": "Seed system integrity is research-stage in most contexts; cohort partner routing recommended.", "exampleProductCategories": [ "seed-system-platform", "agricultural-traceability-rails" ], "partnerChannels": [ "tadamon" ], "lastReviewed": "2026-05-01" } }, { "id": "UC-B-040", "name": "Farmer cooperative registry and member digital ID", "category": "B", "subcategory": "Cooperative and Group Identity Verification", "description": "Give each cooperative member a verified record of membership and contributions that buyers and lenders can check without paper logs.", "bCriteria": [ "B1", "B2", "B5" ], "requiredComponents": [ { "component": "cooperative-registry", "description": "Registry of cooperatives with verifiable anchors (national authority, donor, or CSO issuer)" }, { "component": "member-credential", "description": "Per-member credential proving membership, tenure, role" }, { "component": "participation-attestation", "description": "Attestations of participation, output contribution, training events" }, { "component": "credential-verification", "description": "Reader interface for buyers, donors, and financiers" } ], "conditionalComponents": [ { "component": "veridian-anchor", "condition": "If verifiable credentials are the member ID layer", "linksTo": "UC-D-075" }, { "component": "national-id-linkage", "condition": "If state ID coverage is reliable and accessible" }, { "component": "women-specific-design", "condition": "If women-led cooperative is the primary use case" } ], "crossCategoryDependencies": [ "UC-B-024 as parent identity concept", "UC-A-026 if Islamic finance lending is bundled" ], "p2TriggerConditions": { "description": "Activated when P0 shows cooperative-based beneficiary structure or women-led cooperative focus", "rangeSignals": [ "primaryBeneficiary contains 'Smallholder farmers' or 'Women-led households'", "operatingModel includes cooperative", "donorEcosystem includes Islamic finance OR cluster" ] }, "contextFieldsTemplate": [ { "field": "cooperativeAnchor", "source": "P0 NGO-P0-S5-Q18", "description": "Credential issuer with legitimacy in the member community" }, { "field": "memberCount", "source": "P2 answers", "description": "Cooperative member scale" }, { "field": "womenSpecific", "source": "P0 NGO-P0-S1-Q9", "description": "Whether women-led cooperative design applies" }, { "field": "credentialReaders", "source": "P0 NGO-P0-S4-Q24", "description": "Who reads (buyers, donors, financiers)" }, { "field": "regulatory", "source": "P0 NGO-P0-S6-Q21", "description": "National cooperative regulator stance" } ], "implementationComplexity": "medium", "examples": { "note": "Tadamon cohort UC. Partial precedents: Self-Sovereign Identity pilots in agricultural cooperatives (Kiva, ID2020 partners).", "references": [ { "name": "Kiva Protocol (Sierra Leone)", "url": "https://www.kiva.org/protocol", "solved": "National-scale credential issuance for financial inclusion" }, { "name": "ID2020 agricultural cooperative pilots", "url": "https://id2020.org/", "solved": "Member-level credentialing in smallholder contexts" } ] }, "solutionQuestions": [ { "id": "cooperative-count", "type": "select", "options": [ { "label": "Fewer than 10 cooperatives", "value": "under-10" }, { "label": "10 to 50 cooperatives", "value": "10-50" }, { "label": "50 to 500 cooperatives", "value": "50-500" }, { "label": "Over 500 cooperatives", "value": "over-500" } ] }, { "id": "members-per-cooperative", "type": "select", "options": [ { "label": "Average under 50 members", "value": "under-50" }, { "label": "50 to 500 members", "value": "50-500" }, { "label": "500 to 5,000 members", "value": "500-5000" }, { "label": "Over 5,000 members", "value": "over-5000" } ] }, { "id": "issuer-model", "type": "select", "options": [ { "label": "Implementing CSO is the credential issuer", "value": "cso-issuer" }, { "label": "National cooperative authority is the issuer", "value": "government-issuer" }, { "label": "Each cooperative issues its own credentials", "value": "cooperative-issuer" }, { "label": "Federated: CSO + government + cooperative jointly issue", "value": "federated" } ], "propertyMapping": { "cso-issuer": { "technologies": [ "CSO-issuer credential service" ], "technologyProperties": { "governanceLocus": "cso", "scalabilityCeiling": "moderate" } }, "government-issuer": { "technologies": [ "Government-issuer integration" ], "technologyProperties": { "governanceLocus": "state", "scalabilityCeiling": "high" } }, "cooperative-issuer": { "technologies": [ "Distributed cooperative issuer", "Federation registry" ], "technologyProperties": { "governanceLocus": "cooperative", "scalabilityCeiling": "low at start" } }, "federated": { "technologies": [ "Federated trust architecture" ], "technologyProperties": { "governanceLocus": "federated", "complexityClass": "high" } } } }, { "id": "member-credential-claims", "type": "multi-select", "options": [ { "label": "Active membership status", "value": "membership-status" }, { "label": "Membership tenure", "value": "tenure" }, { "label": "Role within cooperative (officer, member)", "value": "role" }, { "label": "Aggregated output contribution history", "value": "output-history" }, { "label": "Training and capacity-building completed", "value": "training-completed" } ] }, { "id": "women-specific-design", "type": "select", "options": [ { "label": "Not a women-led cooperative focus", "value": "not-applicable" }, { "label": "Aware of women-specific needs but no specific design", "value": "aware" }, { "label": "Women-specific design integrated", "value": "integrated" }, { "label": "Women-only cooperatives are the primary focus", "value": "women-only" } ] }, { "id": "buyers-readers", "type": "multi-select", "options": [ { "label": "Agribusiness buyers verifying cooperative legitimacy", "value": "agribusiness-buyers" }, { "label": "Banks or microfinance verifying member eligibility", "value": "financial-institutions" }, { "label": "Donor programmes verifying member-level reach", "value": "donors" }, { "label": "Government extension and subsidy programmes", "value": "government" }, { "label": "Export buyers verifying cooperative standards", "value": "export-buyers" } ] }, { "id": "national-id-linkage", "type": "select", "options": [ { "label": "Required and accessible", "value": "required-and-available" }, { "label": "Optional: members may link if they wish", "value": "optional" }, { "label": "Not required for credential validity", "value": "not-required" }, { "label": "National ID coverage for women is weak: explicit alternative needed", "value": "women-exclusionary" } ], "propertyMapping": { "women-exclusionary": { "technologies": [ "Cooperative-anchored alternative ID" ], "technologyProperties": { "exclusionRiskMitigation": "yes" } } } }, { "id": "revocation-process", "type": "select", "options": [ { "label": "Issuer revokes unilaterally", "value": "issuer-only" }, { "label": "Dispute resolution before revocation", "value": "dispute-resolved" }, { "label": "Member appeal rights to independent body", "value": "appeal-rights" }, { "label": "No revocation process, credentials are perpetual", "value": "none" } ] }, { "id": "islamic-finance-bundling", "type": "select", "options": [ { "label": "No Islamic finance instrument bundled", "value": "none" }, { "label": "Qard hasan lending bundled", "value": "qard-hasan" }, { "label": "Takaful coverage bundled", "value": "takaful" }, { "label": "Zakat distribution bundled", "value": "zakat" }, { "label": "Multiple Islamic finance instruments", "value": "multiple" } ], "propertyMapping": { "qard-hasan": { "technologies": [ "Lending integration" ], "technologyProperties": { "linksTo": "UC-A-026" } }, "zakat": { "technologies": [ "Zakat eligibility integration" ], "technologyProperties": { "linksTo": "UC-A-026" } }, "multiple": { "technologies": [ "Multi-instrument integration" ], "technologyProperties": { "linksTo": "UC-A-026" } } } } ], "_solutionQuestionsStatus": "v0.1 \u2014 authored 2026-04-24 NGO-040 follow-up; depth 8-12 questions per UC focused on decision-relevant choices; additional questions can be added as the cohort surfaces gaps", "complexityFactors": { "relationships": 4, "operationalChange": 3, "dataCompliance": 3 }, "complexityNotes": { "relationships": "Cooperatives + national authority + donors + buyers / financiers. Cooperative leadership buy-in is the critical path.", "data": "Member-level personal data; minimisation important. Women members particularly sensitive in some contexts.", "dependencies": "Issuer legitimacy; member-side verification reach; national regulator stance." }, "securityTier": "A", "suggestedCriteria": [ { "id": "SC-COOP-MEMBERSHIP", "name": "Member identity completeness", "description": "The registry captures every active member with verifiable identity, history, and contribution. Without complete membership, the registry's downstream use (lender attestation, buyer verification) collapses.", "weight": 0.3, "ratingGuide": { "5": "Every member registered with biometric or strong credential, full participation history. Real-time updates.", "4": "Most members with strong credentials; manual catch-up for new joiners.", "3": "Member list maintained with periodic updates; gaps after seasonal turnover.", "2": "Member list approximate; updates lag months.", "1": "Cooperative leader's memory is the registry." } }, { "id": "SC-COOP-PORTABILITY", "name": "Member-controlled portability", "description": "Members can carry their credentials when they move between cooperatives or to a new buyer relationship. Member-controlled portability is the architectural difference from a centralised cooperative database.", "weight": 0.25, "ratingGuide": { "5": "Members hold their credentials in a personal wallet. Move freely across cooperatives without losing standing.", "4": "Federation-issued credentials portable between member cooperatives.", "3": "Credentials issued by individual cooperative; transferable on request.", "2": "Records held by cooperative; member must re-register elsewhere.", "1": "No portable record." } }, { "id": "SC-COOP-GENDER", "name": "Gender-protective record design", "description": "The registry protects women members from disenfranchisement (loss of share on relative's death, exclusion from credit history). Gender-protective design is critical in many target geographies.", "weight": 0.2, "ratingGuide": { "5": "Member identity decoupled from family identity. Co-op share carried by individual, not family unit.", "4": "Individual member identity primary; family relationships annotated.", "3": "Family-based registration with documented protections for women.", "2": "Family-based registration; protections informal.", "1": "Family-based registration; women effectively absent from records." } }, { "id": "SC-COOP-AUDIT", "name": "Audit and accountability framework", "description": "The registry is subject to formal audit (external or apex-body) that the cooperative is accountable to. Without audit, the registry is unilaterally reportable and weak.", "weight": 0.15, "ratingGuide": { "5": "Annual external audit; accountability to apex federation; published audit report.", "4": "Internal audit with apex-body oversight; informal external review.", "3": "Internal records audit; no external review.", "2": "Periodic accounting audit only.", "1": "No formal audit." } }, { "id": "SC-COOP-STAKEHOLDER", "name": "Counterparty integration", "description": "Downstream counterparties (input suppliers, off-takers, lenders, NGOs) recognise and verify the registry credentials. An unrecognised registry is a database with no users.", "weight": 0.1, "ratingGuide": { "5": "Multiple counterparty types verify credentials at point of interaction. Embedded in their workflows.", "4": "Some counterparties verify; others rely on cooperative attestation.", "3": "Pilot counterparty integrations only.", "2": "Counterparty interest expressed but not integrated.", "1": "Cooperative-internal use only." } } ], "tadamonCohort": true, "procurement": { "marketMaturity": "emerging", "primaryMode": "integrator-led", "alternativeModes": [ "rfq" ], "reasoning": "Farmer cooperative registries with Tadamon framing benefit from cohort partner routing.", "exampleProductCategories": [ "cooperative-registry-platform", "smallholder-id-rails" ], "partnerChannels": [ "tadamon" ], "lastReviewed": "2026-05-01" } }, { "id": "UC-A-026", "name": "Zakat and interest-free loan (qard hasan) distribution transparency", "category": "A", "subcategory": "Religious Finance and Asnaf Distribution", "description": "Record zakat (religious giving) and qard hasan (interest-free loan) payments to eligible recipients so donors and religious supervisors can check them, without revealing who received them.", "bCriteria": [ "B1", "B3", "B6" ], "requiredComponents": [ { "component": "eligibility-attestation", "description": "Asnaf-category eligibility attestation by trusted local authority" }, { "component": "disbursement-record", "description": "On-chain disbursement attestation, recipient-pseudonymous by default" }, { "component": "donor-reporting", "description": "Donor-side category-aggregated reporting interface" }, { "component": "shariah-audit", "description": "Shariah board audit interface for distribution oversight" } ], "conditionalComponents": [ { "component": "qard-hasan-repayment", "condition": "If qard hasan loans are part of the model" }, { "component": "right-to-be-forgotten", "condition": "If recipient-identifying data is retained" }, { "component": "veridian-pseudonymous-id", "condition": "If verifiable credentials anchor recipient pseudonyms", "linksTo": "UC-B-040" } ], "crossCategoryDependencies": [ "UC-A-007 if conventional cash rails are blended", "UC-D-075 if zakat funds flow through voucher distribution" ], "p2TriggerConditions": { "description": "Activated when P0 shows Islamic finance instruments in funding ecosystem AND religious authority engagement", "rangeSignals": [ "donorEcosystem includes 'Islamic finance instruments'", "annualFlow >= USD 100k", "religiousAuthorityEngagement = true" ] }, "contextFieldsTemplate": [ { "field": "instrumentType", "source": "P1 NGO-P1-S1-Q2 + TADAMON-P1-Q1", "description": "Zakat / qard hasan / waqf / mixed" }, { "field": "shariahBoard", "source": "P0 NGO-P0-S5-Q18", "description": "Shariah supervisory board engagement" }, { "field": "asnafCategories", "source": "P2 answers", "description": "Which asnaf categories are addressed" }, { "field": "donorScale", "source": "P0 NGO-P0-S4-Q14a", "description": "Annual flow for overhead justification" }, { "field": "regulatoryContext", "source": "P0 NGO-P0-S6-Q21", "description": "National regulation of blockchain financial records" } ], "implementationComplexity": "high", "examples": { "note": "Tadamon cohort UC. Anchor UC for Islamic finance overlay. Precedents: BAZNAS Indonesia digital zakat pilots, Stellar-based qard hasan experiments.", "references": [ { "name": "BAZNAS Indonesia digital zakat", "url": "https://baznas.go.id/", "solved": "Made zakat collection and distribution transparent at national scale" }, { "name": "IsDB Sustainable Development Goals reports on Islamic finance", "url": "https://www.isdb.org/", "solved": "Cross-border Islamic finance flow accountability" } ] }, "solutionQuestions": [ { "id": "instrument-mix", "type": "multi-select", "options": [ { "label": "Zakat (obligatory alms)", "value": "zakat" }, { "label": "Qard hasan (interest-free loans)", "value": "qard-hasan" }, { "label": "Waqf (endowment)", "value": "waqf" }, { "label": "Sadaqah (voluntary alms)", "value": "sadaqah" }, { "label": "Sukuk (Islamic bonds)", "value": "sukuk" } ] }, { "id": "annual-flow-scale", "type": "select", "options": [ { "label": "Under USD 100,000 annually", "value": "under-100k" }, { "label": "USD 100,000 to 1 million", "value": "100k-1m" }, { "label": "USD 1 million to 10 million", "value": "1m-10m" }, { "label": "Over USD 10 million", "value": "over-10m" } ], "propertyMapping": { "under-100k": { "technologies": [ "Lightweight ledger" ], "technologyProperties": { "overheadJustification": "weak \u2014 manual systems may be sufficient", "honestNoCandidate": "true" } }, "100k-1m": { "technologies": [ "Standard zakat distribution stack" ], "technologyProperties": { "overheadJustification": "moderate" } }, "1m-10m": { "technologies": [ "Multi-corridor zakat platform" ], "technologyProperties": { "overheadJustification": "strong" } }, "over-10m": { "technologies": [ "National-scale zakat platform" ], "technologyProperties": { "overheadJustification": "strong" } } } }, { "id": "asnaf-categories-addressed", "type": "multi-select", "options": [ { "label": "The poor (al-fuqara)", "value": "fuqara" }, { "label": "The destitute (al-masakin)", "value": "masakin" }, { "label": "Zakat administrators (al-amilin alayha)", "value": "amilin" }, { "label": "Reverts (al-muallafa qulubuhum)", "value": "muallafa" }, { "label": "Captives (fi al-riqab)", "value": "riqab" }, { "label": "The indebted (al-gharimin)", "value": "gharimin" }, { "label": "In the path of God (fi sabilillah)", "value": "fi-sabilillah" }, { "label": "Travellers (ibn al-sabil)", "value": "ibn-sabil" } ] }, { "id": "eligibility-attestor", "type": "select", "options": [ { "label": "Local religious scholar / imam", "value": "local-scholar" }, { "label": "Community vetting committee", "value": "vetting-committee" }, { "label": "Established zakat authority (BAZNAS, MUIS, etc.)", "value": "zakat-authority" }, { "label": "CSO internal staff (least preferred)", "value": "cso-internal" }, { "label": "Multiple attestors with quorum requirement", "value": "multiple" } ], "propertyMapping": { "local-scholar": { "technologies": [ "Local-attestor signing" ], "technologyProperties": { "legitimacy": "high in local community" } }, "vetting-committee": { "technologies": [ "Multi-signature attestation" ], "technologyProperties": { "legitimacy": "high" } }, "zakat-authority": { "technologies": [ "Authority-anchored attestation" ], "technologyProperties": { "legitimacy": "highest" } }, "cso-internal": { "technologies": [ "CSO attestation" ], "technologyProperties": { "legitimacy": "weak", "concernRaised": "yes \u2014 religious legitimacy gap" } } } }, { "id": "recipient-pseudonymity", "type": "select", "options": [ { "label": "Strict pseudonymity: no recipient identity exposed to donors", "value": "strict" }, { "label": "Aggregated reporting only", "value": "aggregated" }, { "label": "Identity visible to attestor and shariah board only", "value": "authority-only" }, { "label": "Full disclosure to donor", "value": "full-disclosure" } ], "propertyMapping": { "strict": { "technologies": [ "Pseudonymous identifier", "Zero-knowledge proofs" ], "technologyProperties": { "protectionRating": "strong" } }, "aggregated": { "technologies": [ "Aggregated category reporting" ], "technologyProperties": { "protectionRating": "strong" } }, "authority-only": { "technologies": [ "Selective disclosure" ], "technologyProperties": { "protectionRating": "moderate" } }, "full-disclosure": { "technologies": [], "technologyProperties": { "protectionRating": "weak", "concernRaised": "yes \u2014 recipient dignity" } } } }, { "id": "disbursement-mechanism", "type": "multi-select", "options": [ { "label": "Direct cash transfer", "value": "direct-cash" }, { "label": "Voucher to specific vendors", "value": "voucher" }, { "label": "In-kind goods", "value": "in-kind" }, { "label": "Repayable loan (qard hasan)", "value": "loan-repayable" }, { "label": "Microenterprise grant (zakat-funded)", "value": "microenterprise-grant" } ] }, { "id": "shariah-supervision-model", "type": "select", "options": [ { "label": "Internal shariah supervisory board", "value": "internal-board" }, { "label": "External shariah scholars retained", "value": "external-scholars" }, { "label": "National shariah supervisory body", "value": "national-body" }, { "label": "No shariah supervision, programme-killing veto", "value": "none" } ], "propertyMapping": { "none": { "technologies": [], "technologyProperties": { "deployBlocker": "yes \u2014 shariah supervision is preconditional" } } } }, { "id": "right-to-be-forgotten", "type": "select", "options": [ { "label": "On by default: eligibility records expire", "value": "default-on" }, { "label": "On request from recipient", "value": "on-request" }, { "label": "Anonymisation after distribution complete", "value": "anonymisation" }, { "label": "Perpetual records (high concern in this context)", "value": "perpetual" } ] }, { "id": "blended-conventional-funding", "type": "select", "options": [ { "label": "Pure Islamic finance", "value": "none" }, { "label": "Complementary conventional funding", "value": "complementary" }, { "label": "Majority conventional with Islamic component", "value": "majority-conventional" }, { "label": "Blended approximately equally", "value": "blended-equally" } ] } ], "_solutionQuestionsStatus": "v0.1 \u2014 authored 2026-04-24 NGO-040 follow-up; depth 8-12 questions per UC focused on decision-relevant choices; additional questions can be added as the cohort surfaces gaps", "complexityFactors": { "relationships": 4, "operationalChange": 4, "dataCompliance": 5 }, "complexityNotes": { "relationships": "CSO + zakat fund + shariah board + recipients + donors. Religious authority is a programme-killing veto if not engaged.", "data": "Recipient eligibility data is highly sensitive; asnaf-status attestation must protect dignity. Permanence vs right-to-be-forgotten tension.", "dependencies": "Shariah board sign-off; eligibility attestation legitimacy; regulatory permission for blockchain financial records." }, "securityTier": "A", "suggestedCriteria": [ { "id": "SC-ZAKAT-AUDIT", "name": "Distribution audit completeness", "description": "The system produces a complete and tamper-evident record of every zakat or qard hasan disbursement, traceable from source pool to eligible recipient. Audit completeness is the integrity-property core for distribution transparency claims.", "weight": 0.3, "ratingGuide": { "5": "Cryptographically anchored disbursement records. Every flow auditable end-to-end with mathematical proof. External attestation embedded.", "4": "Digital ledger with strong audit log. Donor and shariah board can independently verify any disbursement against eligibility records.", "3": "Periodic batch audit. Records reconciled quarterly with limited mid-cycle visibility.", "2": "Annual audit only. Quarterly summaries aggregate-level only.", "1": "Internal records, no external verification. Donors trust the institution but cannot verify." } }, { "id": "SC-ZAKAT-SHARIAH", "name": "Shariah supervision integration", "description": "Shariah supervision is embedded in the distribution workflow with credential-level attestation. Without active shariah oversight, the asnaf-eligibility claim lacks its primary independent witness.", "weight": 0.25, "ratingGuide": { "5": "Active shariah board with on-chain or signed attestation per disbursement batch. Recorded position on each asnaf category.", "4": "Designated supervisor reviews and signs off batches. Records cite supervisor identity.", "3": "External shariah advisory consulted for policy, not per-disbursement.", "2": "Shariah review at programme level only, not per-distribution.", "1": "No formal shariah supervision." } }, { "id": "SC-ZAKAT-PRIVACY", "name": "Recipient privacy with verifiable distribution", "description": "The system can prove distribution occurred without exposing recipient identity to donors or analysts. Selective disclosure is essential for vulnerable populations and protective for donor accountability.", "weight": 0.2, "ratingGuide": { "5": "Pseudonymous credentials with cryptographic proof of asnaf eligibility. Donor sees aggregate proof, not individual identity.", "4": "Recipient identifier hashed; donor sees pseudonyms with verifiable distribution.", "3": "Recipient names redacted in donor reports; full identity in internal records only.", "2": "Limited redaction; recipient details visible to donor on request.", "1": "Recipient details fully exposed in donor reports." } }, { "id": "SC-ZAKAT-MULTI-DONOR", "name": "Multi-donor reporting fitness", "description": "The system produces reports tailored to different donor types (private philanthropic, state, multilateral) without re-keying data. Multi-donor reporting is where verifiable architectures justify the setup cost.", "weight": 0.15, "ratingGuide": { "5": "Donor-specific report templates auto-generate from canonical record. Each donor sees their data in their format.", "4": "One canonical record, donor-specific exports via configured templates.", "3": "Manual report generation per donor, but data pulled from one source.", "2": "Separate reports per donor, partly inconsistent with each other.", "1": "Manual report generation, inconsistent across donor types." } }, { "id": "SC-ZAKAT-LEGAL", "name": "Jurisdictional and Islamic finance compliance", "description": "The system handles multi-jurisdictional zakat law and Islamic finance contract compliance (qard hasan repayment, asnaf classification). Inconsistent legal handling creates donor and recipient risk.", "weight": 0.1, "ratingGuide": { "5": "Per-jurisdiction compliance modules; AAOIFI and OIC fiqh guidance embedded; legal audit annual.", "4": "Standard compliance approach across jurisdictions; legal advisory engaged.", "3": "Compliance handled at programme level, not system-embedded.", "2": "Ad-hoc compliance handling.", "1": "No documented compliance framework." } } ], "tadamonCohort": true, "procurement": { "marketMaturity": "nascent", "primaryMode": "integrator-led", "alternativeModes": [ "consortium" ], "reasoning": "Zakat distribution with Islamic-finance compliance is bespoke; integrator-led with cohort partner channel.", "exampleProductCategories": [ "islamic-finance-platform", "zakat-distribution-rails" ], "partnerChannels": [ "tadamon" ], "lastReviewed": "2026-05-01" } }, { "id": "UC-E-085", "name": "Anticipatory action trigger proof", "category": "E", "subcategory": "Climate and Crisis Response \u2014 Anticipatory Action", "description": "Show that the agreed trigger for early funding, such as a rainfall level, was reached, with a record that partners and funders can check.", "bCriteria": [ "B2", "B4", "B7" ], "requiredComponents": [ { "component": "trigger-data-oracle", "description": "Attested oracle writing observations from data provider (famine early-warning system, IPC, satellite, meteorological service)" }, { "component": "trigger-rule", "description": "Explicit, published trigger rule re-runnable by any partner" }, { "component": "evaluation-record", "description": "On-chain evaluation outcome record" }, { "component": "disbursement-authorisation", "description": "Conditional disbursement authorisation contingent on recorded outcome" } ], "conditionalComponents": [ { "component": "smart-contracts", "condition": "If automated disbursement is permitted" }, { "component": "override-process", "condition": "If anomalous-case manual override is required" }, { "component": "waqf-financing", "condition": "If pre-positioned fund is waqf-structured", "linksTo": "UC-A-026" } ], "crossCategoryDependencies": [ "UC-E-072 for parametric insurance pairing", "UC-A-007 for disbursement rails" ], "p2TriggerConditions": { "description": "Activated when P0 shows climate-vulnerable or displacement-prone geography + anticipatory action in response model + donor support for FbF / CERF-AA", "rangeSignals": [ "operatingContext in {post_conflict, active_conflict, mixed}", "donorEcosystem includes 'cluster' OR 'UN system'", "responseModel includes anticipatory_action" ] }, "contextFieldsTemplate": [ { "field": "triggerDataSource", "source": "P2 answers", "description": "Which data provider + attestor identity" }, { "field": "triggerRule", "source": "P2 answers", "description": "Threshold + window + fallback specification" }, { "field": "prePositionedFund", "source": "P0 NGO-P0-S4-Q14a + Q24", "description": "Fund existence and source" }, { "field": "disbursementMechanism", "source": "P2 answers", "description": "Direct, vendor, or CSO float" }, { "field": "auditFrequency", "source": "P0 NGO-P0-S4-Q24", "description": "Donor expectations for re-evaluation" } ], "implementationComplexity": "high", "examples": { "note": "Tadamon cohort UC. Aligns with FbF (Forecast-based Financing), CERF-AA (Anticipatory Action), Start Network anticipatory pilots.", "references": [ { "name": "Forecast-based Financing (FbF)", "url": "https://www.anticipation-hub.org/", "solved": "Pre-event disbursement on weather/climate triggers" }, { "name": "CERF Anticipatory Action", "url": "https://cerf.un.org/our-work/anticipatory-action", "solved": "UN-coordinated anticipatory funding" }, { "name": "Start Network anticipatory action pilots", "url": "https://startnetwork.org/", "solved": "NGO-led anticipatory pooled funds" } ] }, "solutionQuestions": [ { "id": "trigger-type", "type": "multi-select", "options": [ { "label": "Drought (rainfall, NDVI, soil moisture)", "value": "drought" }, { "label": "Flood (river levels, satellite, forecast rainfall)", "value": "flood" }, { "label": "Storm and cyclone (forecast track + intensity)", "value": "storm" }, { "label": "Conflict-displacement (population movement)", "value": "displacement" }, { "label": "Food insecurity (IPC, market price spikes)", "value": "food-insecurity" }, { "label": "Disease outbreak surveillance", "value": "disease-outbreak" } ] }, { "id": "data-provider", "type": "multi-select", "options": [ { "label": "Famine early-warning system", "value": "fews-net" }, { "label": "IPC (Integrated Food Security Phase Classification)", "value": "ipc" }, { "label": "UN-OCHA / Centre for Humanitarian Data", "value": "ocha" }, { "label": "National meteorological service", "value": "met-service" }, { "label": "Commercial satellite providers", "value": "satellite-commercial" }, { "label": "Academic research institutes", "value": "research-institute" } ] }, { "id": "oracle-attestation", "type": "select", "options": [ { "label": "Data provider attests directly", "value": "data-provider-attests" }, { "label": "Third-party aggregator attests on provider's behalf", "value": "third-party-aggregator" }, { "label": "Multi-source quorum (median or majority of sources)", "value": "multi-source-quorum" }, { "label": "Manual attestation by authorised partner", "value": "manual-attestation" } ], "propertyMapping": { "data-provider-attests": { "technologies": [ "Direct provider oracle" ], "technologyProperties": { "trustModel": "high" } }, "multi-source-quorum": { "technologies": [ "Quorum oracle" ], "technologyProperties": { "trustModel": "highest" } }, "manual-attestation": { "technologies": [ "Manual oracle" ], "technologyProperties": { "trustModel": "moderate", "speedTrade": "yes \u2014 manual is slower" } } } }, { "id": "rule-specification", "type": "select", "options": [ { "label": "Simple threshold (e.g. rainfall < X mm)", "value": "simple-threshold" }, { "label": "Compound rule (multiple thresholds + windows)", "value": "compound" }, { "label": "Model-based (forecast model output)", "value": "model-based" }, { "label": "Bespoke partner-agreed rule", "value": "bespoke" } ] }, { "id": "disbursement-amount-mechanism", "type": "select", "options": [ { "label": "Flat amount per household", "value": "flat-per-household" }, { "label": "Tiered by trigger severity", "value": "tiered-by-severity" }, { "label": "Scaled by historical loss data", "value": "scaled-by-historical" }, { "label": "Manual allocation per case", "value": "manual-allocation" } ] }, { "id": "disbursement-rail", "type": "select", "options": [ { "label": "Direct mobile money to beneficiary", "value": "direct-mobile-money" }, { "label": "Vendor-redeemable voucher", "value": "vendor-voucher" }, { "label": "CSO float for distribution", "value": "cso-float" }, { "label": "Partner cooperative or government channel", "value": "partner-cooperative" } ] }, { "id": "pre-positioned-fund-status", "type": "select", "options": [ { "label": "Yes, fund pre-positioned and ready", "value": "yes-funded" }, { "label": "Partially funded; gap to close", "value": "partially" }, { "label": "Planned; not yet funded", "value": "planned" }, { "label": "Not yet a pre-positioned fund, anticipatory action cannot fire", "value": "not-yet" } ], "propertyMapping": { "yes-funded": { "technologies": [ "Standard rail" ], "technologyProperties": { "fundReady": "yes" } }, "partially": { "technologies": [ "Phased deployment" ], "technologyProperties": { "fundReady": "partial" } }, "planned": { "technologies": [ "Plan + advocacy" ], "technologyProperties": { "fundReady": "planned" } }, "not-yet": { "technologies": [], "technologyProperties": { "fundReady": "no", "deployBlocker": "yes" } } } }, { "id": "override-rights", "type": "select", "options": [ { "label": "No override, automated only", "value": "none" }, { "label": "Partner organisations can veto activation", "value": "partner-veto" }, { "label": "Donor must confirm before disbursement", "value": "donor-confirmation" }, { "label": "Two-step: trigger fires, partner confirms, then disburse", "value": "two-step" } ] }, { "id": "partner-coordination-strength", "type": "select", "options": [ { "label": "Strong: formal coordination mechanism", "value": "strong" }, { "label": "Moderate: bilateral agreements", "value": "moderate" }, { "label": "Weak: informal alignment only", "value": "weak" }, { "label": "Absent: partners cannot agree on shared trigger", "value": "absent" } ], "propertyMapping": { "absent": { "technologies": [], "technologyProperties": { "deployBlocker": "yes \u2014 coordination is preconditional" } } } }, { "id": "waqf-integration", "type": "select", "options": [ { "label": "No waqf component", "value": "none" }, { "label": "Planning waqf-financed pool", "value": "planned" }, { "label": "Waqf is the primary financing mechanism", "value": "active" } ] } ], "_solutionQuestionsStatus": "v0.1 \u2014 authored 2026-04-24 NGO-040 follow-up; depth 8-12 questions per UC focused on decision-relevant choices; additional questions can be added as the cohort surfaces gaps", "complexityFactors": { "relationships": 4, "operationalChange": 3, "dataCompliance": 3 }, "complexityNotes": { "relationships": "Data provider + implementing partners + donor + host government. Trigger-rule consensus is the critical coordination challenge.", "data": "Trigger data is generally public (climate, displacement) but disbursement records may identify beneficiaries.", "dependencies": "Pre-positioned fund existence; oracle relationship; donor permission for automated disbursement." }, "securityTier": "B", "suggestedCriteria": [ "B2", "B4", "B7", "trigger-rule-consensus", "pre-positioned-fund-required" ], "tadamonCohort": true, "procurement": { "marketMaturity": "nascent", "primaryMode": "integrator-led", "alternativeModes": [ "consortium" ], "reasoning": "Anticipatory action triggers are research-stage; Tadamon cohort routing recommended.", "exampleProductCategories": [ "anticipatory-action-platform", "parametric-trigger-rails" ], "partnerChannels": [ "tadamon" ], "lastReviewed": "2026-05-01" } } ] }