# Tender questions The questions that fill a tender. Generated from the catalogue and `tender-questions.json` by `tools/build-pack.py`. Do not edit by hand. A tender is written for one use case whose verdict is yes or yes with conditions. Ask, in this order: the use case's own questions (the ones marked to show only if an earlier answer allows it are skipped otherwise), then the three about how it will be used, then the six about the whole organisation, which you ask once however many tenders follow. Record the label of the answer the person chose, which is the text before the square brackets. Where a question allows several answers, record them all. Each question has a requirement type. The type decides the minimum a bid should meet: - residency: Every copy stays in the place named. - privacy: Encrypted and collected with consent, under a data processing agreement. - legal-checks: The bid names the rules and how it meets them. - audit-trail: Every action logged with author and time, and exportable. - offline: Core tasks work offline and sync safely. - integration: Published interfaces, tested against live systems. - usability: Least experienced users manage after a short briefing. - scale: Proven at the stated volume, with room to grow. - money: Cost and time per transaction, every fee listed. - governance: Roles and approvals written down and changeable by the issuer. - delivery-model: Roles after go-live are clear, with 12 months of support priced. - training: Included, in the users' language, with reusable materials. - budget: Fits the stated budget, with extra costs listed separately. - exit: Data exportable in an open format at any time. - credentials: Identity and credential steps shown working in the pilot. - devices: Tested on the devices and networks at the pilot site. - general: The bid explains how it is met. Hard gates. A requirement is MUST only when its question is a hard gate and the answer asks for something. Every other requirement starts as SHOULD, and the issuer can change any of them in the review. A question marked hard gate below becomes a MUST requirement when its answer asks for something. If every answer chosen says none, not required or not sure (a label that starts with "no", "none", "not required", "not needed", "no restriction", "optional", "unsure", "not sure", "not yet" or "undecided"), it stays a SHOULD. Everything else starts as SHOULD. The person can change any of them in the review. ## How it will be used (one set per use case) ### P5-UC-INTEGRATION Ask: Which existing systems must this connect to? Help: Pick every one that applies. A rough answer is fine. Answer: pick all that apply Requirement type: integration Statement: Connects to: {answer}. Options: - Accounting system [erp] - Beneficiary or case records [beneficiary] - Mobile money operators [mobile-money] - Banks and payment systems [banking] - Identity systems [identity] - Supply chain systems [supply-chain] - Donor reporting systems [reporting] - None, it stands alone [none] ### P5-UC-PERSONAL-DATA Ask: Will it handle personal data? Help: Personal data is anything that says who a person is or what they received. Answer: pick one Requirement type: privacy Statement: Personal data: {answer}. Hard gate: yes. It stays a SHOULD if the answer is only [limited] or [none] or [unsure]. Options: - Yes, sensitive records about people [significant] - Yes, a little, such as staff or contact details [limited] - No, only operational data [none] - Not sure yet [unsure] ### P5-UC-USER-TECH Ask: Who will use it day to day? Help: Pick every group. The least experienced group sets how simple it must be. Answer: pick all that apply Requirement type: usability Statement: Used by: {answer}. Options: - Technical staff [technical] - Office staff [office] - Field staff with basic phones [field] - The people you serve, some with little digital experience [beneficiaries] - A mix of groups [mixed] - Someone else [other] ## About the whole organisation (ask once) ### P5-IR-DATA-RESIDENCY Ask: Where must the data be kept? Help: Think of any law or contract that says where data may be stored. Answer: pick one Requirement type: residency Statement: Data is kept: {answer}. Hard gate: yes. It stays a SHOULD if the answer is only [no-restriction] or [unsure]. Options: - Inside the EU or the wider European Economic Area [eu-eea] - Inside the country of operation [local-required] - Where a donor requires [donor-specific] - No restriction [no-restriction] - Not sure yet [unsure] ### P5-IR-AUDIT-AUDIENCES Ask: Who must be able to check the records? Help: Pick every group that needs to verify transactions or records. Answer: pick all that apply Requirement type: audit-trail Statement: Records can be checked by: {answer}. Options: - Internal audit [internal-audit] - External auditors [external-auditors] - Donors [donors] - Regulators [regulators] - Partner organisations [partners] - The people the records are about [beneficiaries] ### P5-IR-IMPL-MODEL Ask: Who should run it once it is live? Help: Pick the arrangement you would prefer. You can change it after the bids arrive. Answer: pick one Requirement type: delivery-model Statement: Operating model: {answer}. Options: - The supplier runs everything [full-service] - Supplier hosts, your team runs it daily [managed] - Supplier builds, trains, then hands over [build-transfer] - Your team builds alongside the supplier [co-development] - No preference yet [no-preference] ### P5-IR-TRAINING Ask: Who needs training from the supplier? Help: Pick every group. Answer: pick all that apply Requirement type: training Statement: Training needed: {answer}. Options: - A briefing for leaders [executive] - Training for administrators [admin] - Training for daily users [user] - Training for field staff [field] - Orientation for the people you serve [beneficiary] - Technical set-up training [technical] - Train-the-trainer for your staff [train-trainer] ### P5-IR-BUDGET Ask: What is the budget for the first year? Help: Include set-up and the first year of running it. You can leave this out of the tender in the review. Answer: pick one Requirement type: budget Statement: First-year budget: {answer}. Options: - Under $5,000 [under-5k] - $5,000 to $15,000 [5k-15k] - $15,000 to $50,000 [15k-50k] - $50,000 to $150,000 [50k-150k] - Over $150,000 [over-150k] - Flexible, depends on the value shown [flexible] ### P5-IR-LOCKIN Ask: How easy must it be to switch supplier later? Help: Think of the day you want to take it in-house or move to another supplier. Answer: pick one Requirement type: exit Statement: Switching supplier later: {answer}. Options: - Open standards and full data export [critical] - Prefer open standards, some closed parts fine [important] - Best solution wins, switching is secondary [neutral] - Happy to commit long term [not-concerned] ## The use cases ### UC-A-001: Cross-border beneficiary payments Security level: Higher. #### UC-A-001 / corridor-count Ask: How many countries does your organisation send transfer funds from? Answer: pick one Requirement type: scale - Single country [single] - 2–3 countries [2-3] - 4–5 countries [4-5] - More than 5 countries [5-plus] #### UC-A-001 / origination-country-1 Ask: Which country do you most frequently initiate transfers from? Answer: pick one Show only if the answer to corridor-count is single or more. Requirement type: money - United States [united-states] - United Kingdom [united-kingdom] - Germany [germany] - Netherlands [netherlands] - Switzerland [switzerland] - Belgium [belgium] - France [france] - Sweden [sweden] - Norway [norway] - Denmark [denmark] - Canada [canada] - Australia [australia] - Japan [japan] - Ireland [ireland] - Italy [italy] - Spain [spain] - Austria [austria] - Finland [finland] - Luxembourg [luxembourg] - South Korea [south-korea] - New Zealand [new-zealand] - United Arab Emirates [united-arab-emirates] - Singapore [singapore] - Other [other] #### UC-A-001 / origination-country-2 Ask: Second most common transfer origination country (if applicable) Answer: pick one Show only if the answer to corridor-count is 2-3 or more. Requirement type: money - United States [united-states] - United Kingdom [united-kingdom] - Germany [germany] - Netherlands [netherlands] - Switzerland [switzerland] - Belgium [belgium] - France [france] - Sweden [sweden] - Norway [norway] - Denmark [denmark] - Canada [canada] - Australia [australia] - Japan [japan] - Ireland [ireland] - Italy [italy] - Spain [spain] - Austria [austria] - Finland [finland] - Luxembourg [luxembourg] - South Korea [south-korea] - New Zealand [new-zealand] - United Arab Emirates [united-arab-emirates] - Singapore [singapore] - Other [other] #### UC-A-001 / origination-country-3 Ask: Third transfer origination country (if applicable) Answer: pick one Show only if the answer to corridor-count is 2-3 or more. Requirement type: money - United States [united-states] - United Kingdom [united-kingdom] - Germany [germany] - Netherlands [netherlands] - Switzerland [switzerland] - Belgium [belgium] - France [france] - Sweden [sweden] - Norway [norway] - Denmark [denmark] - Canada [canada] - Australia [australia] - Japan [japan] - Ireland [ireland] - Italy [italy] - Spain [spain] - Austria [austria] - Finland [finland] - Luxembourg [luxembourg] - South Korea [south-korea] - New Zealand [new-zealand] - United Arab Emirates [united-arab-emirates] - Singapore [singapore] - Other [other] #### UC-A-001 / origination-country-4 Ask: Fourth transfer origination country (if applicable) Answer: pick one Show only if the answer to corridor-count is 4-5 or more. Requirement type: money - United States [united-states] - United Kingdom [united-kingdom] - Germany [germany] - Netherlands [netherlands] - Switzerland [switzerland] - Belgium [belgium] - France [france] - Sweden [sweden] - Norway [norway] - Denmark [denmark] - Canada [canada] - Australia [australia] - Japan [japan] - Ireland [ireland] - Italy [italy] - Spain [spain] - Austria [austria] - Finland [finland] - Luxembourg [luxembourg] - South Korea [south-korea] - New Zealand [new-zealand] - United Arab Emirates [united-arab-emirates] - Singapore [singapore] - Other [other] #### UC-A-001 / origination-country-5 Ask: Fifth transfer origination country (if applicable) Answer: pick one Show only if the answer to corridor-count is 4-5 or more. Requirement type: money - United States [united-states] - United Kingdom [united-kingdom] - Germany [germany] - Netherlands [netherlands] - Switzerland [switzerland] - Belgium [belgium] - France [france] - Sweden [sweden] - Norway [norway] - Denmark [denmark] - Canada [canada] - Australia [australia] - Japan [japan] - Ireland [ireland] - Italy [italy] - Spain [spain] - Austria [austria] - Finland [finland] - Luxembourg [luxembourg] - South Korea [south-korea] - New Zealand [new-zealand] - United Arab Emirates [united-arab-emirates] - Singapore [singapore] - Other [other] #### UC-A-001 / funding-method Ask: How does your organisation currently fund international transfers or payments? Answer: pick one Requirement type: money - Bank transfer from organisation account [bank-transfer] - Card payment from organisation [card-payment] - Direct stablecoin funding (organisation already holds stablecoins) [direct-stablecoin] - Mixed: bank transfer for most, card for urgent payments [mixed-methods] #### UC-A-001 / beneficiary-device Ask: What devices do your beneficiaries typically have access to in the field? Answer: pick one Requirement type: devices - Smartphones with reliable data connectivity [smartphone-connected] - Smartphones but with intermittent connectivity [smartphone-intermittent] - Feature phones only (SMS/USSD) [feature-phone] - No personal devices, rely on agent/kiosk access [no-device] - Mixed: varies significantly across beneficiary population [mixed] #### UC-A-001 / avg-transaction-size Ask: What is the typical payment amount per beneficiary per disbursement? Answer: pick one Requirement type: scale - Micro-payments: under $10 USD equivalent [micro] - Small: $10–$50 USD equivalent [small] - Medium: $50–$200 USD equivalent [medium] - Large: $200–$1,000 USD equivalent [large] - Variable: ranges widely across programmes [variable] #### UC-A-001 / settlement-speed Ask: How quickly do beneficiaries need to receive funds after you initiate a payment? Answer: pick one Requirement type: money - Real-time (seconds to minutes) [realtime] - Same day (within hours) [same-day] - Next business day is acceptable [next-day] - Within a week is fine [weekly] #### UC-A-001 / last-mile-delivery Ask: How do beneficiaries currently receive payments in the field? Answer: pick all that apply Requirement type: general - Direct to bank account [bank-account] - Mobile money [mobile-money] - Cash via agents or field staff [cash-agent] - Cash at a bank branch [cash-bank] - Vouchers or e-vouchers [voucher] - No current system, setting up from scratch [greenfield] #### UC-A-001 / beneficiary-bank-access Ask: What proportion of your beneficiaries have access to a formal bank account? Answer: pick one Requirement type: usability - Most (over 70%) have bank accounts [most-banked] - Some (30–70%) have bank accounts [partially-banked] - Few (under 30%) have bank accounts [mostly-unbanked] - Almost none: largely unbanked population [unbanked] #### UC-A-001 / kyc-requirements Ask: What identity verification is required or feasible for your beneficiary population? Answer: pick one Requirement type: legal-checks. Hard gate: yes - Full KYC: government ID, address proof available [full-kyc] - Simplified KYC: name and basic ID only [simplified-kyc] - Biometric-only: fingerprint or face recognition [biometric-only] - Community vouching / group attestation [community-vouch] - No formal ID available for most beneficiaries [no-id] #### UC-A-001 / conditional-payments Ask: Are any of these payments conditional on beneficiary actions (e.g., attendance, training completion, milestones)? Answer: pick one Requirement type: money - Yes, most payments are conditional [mostly-conditional] - Yes, some payments have conditions [some-conditional] - No, all payments are unconditional cash transfers [unconditional] #### UC-A-001 / currency-pairs Ask: Which currency corridor regions do your transfers typically involve? Answer: pick all that apply Requirement type: money - USD to East African currencies (KES, UGX, TZS, RWF) [usd-east-africa] - USD to West African currencies (NGN, GHS, XOF) [usd-west-africa] - USD to South/Southeast Asian currencies (BDT, PKR, MMK, PHP) [usd-south-asia] - EUR to African or Middle Eastern currencies [eur-africa-mena] - GBP to Commonwealth currencies [gbp-commonwealth] - USD or EUR to Latin American currencies (COP, PEN, HNL, HTG) [latam] - Stablecoin to local currency (via mobile money or cash-out) [stablecoin-local] - Multiple regions: complex multi-corridor programme [multi-region] - Not sure, need guidance on corridor planning [unsure] #### UC-A-001 / sanctions-screening Ask: What sanctions and compliance screening is required for your payment corridors? Answer: pick all that apply Requirement type: legal-checks. Hard gate: yes - OFAC (US sanctions) screening [ofac] - EU sanctions list screening [eu-sanctions] - UN sanctions list screening [un-sanctions] - Local AML/CFT requirements in destination countries [local-aml] - Donor-specific compliance requirements [donor-specific] - Not sure, need guidance on requirements [unsure] #### UC-A-001 / batch-vs-individual Ask: How are payments typically initiated? Answer: pick one Requirement type: money - Batch: upload a list of beneficiaries and amounts [batch] - Individual: one payment at a time as needed [individual] - Both, batch for regular disbursements, individual for ad-hoc [both] #### UC-A-001 / connectivity-lastmile Ask: What is the typical internet connectivity like in your last-mile delivery areas? Answer: pick one Requirement type: offline - Reliable broadband/4G: always connected [reliable] - Intermittent 3G/4G: drops frequently [intermittent] - 2G/EDGE only: very slow data [2g-only] - No internet, SMS/USSD network only [no-internet] - Completely offline: no cellular coverage at all [offline] #### UC-A-001 / reporting-needs Ask: What reporting or audit trail do donors require for these payments? Answer: pick all that apply Requirement type: audit-trail - Real-time transaction visibility for donors [realtime-donor] - Periodic summary reports (monthly/quarterly) [periodic-reports] - Full audit trail: every transaction traceable end-to-end [full-audit] - Proof of delivery to individual beneficiaries [proof-of-delivery] - Compliance/sanctions screening logs [compliance-logs] - Minimal: standard financial reporting only [minimal] #### UC-A-001 / sq-UC-A-001-001 Ask: What is the acceptable failed-payment rate before manual intervention is triggered? Answer: pick one Requirement type: general - Zero tolerance: all failures escalated immediately [zero-tolerance] - Under 5% failure rate acceptable [under-5-percent] - Under 10% failure rate acceptable [under-10-percent] - Best effort: no specific threshold [best-effort] #### UC-A-001 / sq-UC-A-001-003 Ask: What reconciliation frequency do you need with your payment service providers? Answer: pick one Requirement type: legal-checks - Real-time settlement confirmation [real-time-settlement] - Daily batch reconciliation [daily-batch] - Weekly summary reports [weekly-summary] - Monthly aggregate reporting [monthly-aggregate] #### UC-A-001 / beneficiary-choice Ask: How will beneficiaries exercise choice in how they receive and use this service? Answer: pick one Requirement type: usability - Beneficiaries choose between delivery methods (cash, voucher, mobile money, direct) [delivery-choice] - Beneficiaries choose preferred merchants or service points [merchant-choice] - Beneficiaries control their own data sharing preferences [data-choice] - Multiple choice dimensions (delivery + merchant + data) [full-choice] - Limited choice: programme constraints determine delivery [limited] ### UC-A-002: Staff salary payments across jurisdictions Security level: Higher. #### UC-A-002 / corridor-count Ask: How many countries does your organisation send transfer funds from? Answer: pick one Requirement type: scale - Single country [single] - 2–3 countries [2-3] - 4–5 countries [4-5] - More than 5 countries [5-plus] #### UC-A-002 / origination-country-1 Ask: Which country do you most frequently initiate transfers from? Answer: pick one Show only if the answer to corridor-count is single or more. Requirement type: money - United States [united-states] - United Kingdom [united-kingdom] - Germany [germany] - Netherlands [netherlands] - Switzerland [switzerland] - Belgium [belgium] - France [france] - Sweden [sweden] - Norway [norway] - Denmark [denmark] - Canada [canada] - Australia [australia] - Japan [japan] - Ireland [ireland] - Italy [italy] - Spain [spain] - Austria [austria] - Finland [finland] - Luxembourg [luxembourg] - South Korea [south-korea] - New Zealand [new-zealand] - United Arab Emirates [united-arab-emirates] - Singapore [singapore] - Other [other] #### UC-A-002 / origination-country-2 Ask: Second most common transfer origination country (if applicable) Answer: pick one Show only if the answer to corridor-count is 2-3 or more. Requirement type: money - United States [united-states] - United Kingdom [united-kingdom] - Germany [germany] - Netherlands [netherlands] - Switzerland [switzerland] - Belgium [belgium] - France [france] - Sweden [sweden] - Norway [norway] - Denmark [denmark] - Canada [canada] - Australia [australia] - Japan [japan] - Ireland [ireland] - Italy [italy] - Spain [spain] - Austria [austria] - Finland [finland] - Luxembourg [luxembourg] - South Korea [south-korea] - New Zealand [new-zealand] - United Arab Emirates [united-arab-emirates] - Singapore [singapore] - Other [other] #### UC-A-002 / origination-country-3 Ask: Third transfer origination country (if applicable) Answer: pick one Show only if the answer to corridor-count is 2-3 or more. Requirement type: money - United States [united-states] - United Kingdom [united-kingdom] - Germany [germany] - Netherlands [netherlands] - Switzerland [switzerland] - Belgium [belgium] - France [france] - Sweden [sweden] - Norway [norway] - Denmark [denmark] - Canada [canada] - Australia [australia] - Japan [japan] - Ireland [ireland] - Italy [italy] - Spain [spain] - Austria [austria] - Finland [finland] - Luxembourg [luxembourg] - South Korea [south-korea] - New Zealand [new-zealand] - United Arab Emirates [united-arab-emirates] - Singapore [singapore] - Other [other] #### UC-A-002 / origination-country-4 Ask: Fourth transfer origination country (if applicable) Answer: pick one Show only if the answer to corridor-count is 4-5 or more. Requirement type: money - United States [united-states] - United Kingdom [united-kingdom] - Germany [germany] - Netherlands [netherlands] - Switzerland [switzerland] - Belgium [belgium] - France [france] - Sweden [sweden] - Norway [norway] - Denmark [denmark] - Canada [canada] - Australia [australia] - Japan [japan] - Ireland [ireland] - Italy [italy] - Spain [spain] - Austria [austria] - Finland [finland] - Luxembourg [luxembourg] - South Korea [south-korea] - New Zealand [new-zealand] - United Arab Emirates [united-arab-emirates] - Singapore [singapore] - Other [other] #### UC-A-002 / origination-country-5 Ask: Fifth transfer origination country (if applicable) Answer: pick one Show only if the answer to corridor-count is 4-5 or more. Requirement type: money - United States [united-states] - United Kingdom [united-kingdom] - Germany [germany] - Netherlands [netherlands] - Switzerland [switzerland] - Belgium [belgium] - France [france] - Sweden [sweden] - Norway [norway] - Denmark [denmark] - Canada [canada] - Australia [australia] - Japan [japan] - Ireland [ireland] - Italy [italy] - Spain [spain] - Austria [austria] - Finland [finland] - Luxembourg [luxembourg] - South Korea [south-korea] - New Zealand [new-zealand] - United Arab Emirates [united-arab-emirates] - Singapore [singapore] - Other [other] #### UC-A-002 / funding-method Ask: How does your organisation currently fund international transfers or payments? Answer: pick one Requirement type: money - Bank transfer from organisation account [bank-transfer] - Card payment from organisation [card-payment] - Direct stablecoin funding (organisation already holds stablecoins) [direct-stablecoin] - Mixed: bank transfer for most, card for urgent payments [mixed-methods] #### UC-A-002 / staff-headcount Ask: How many staff do you pay salaries to? Answer: pick one Requirement type: money - Under 50 staff [small] - 50–200 staff [medium] - 200–1,000 staff [large] - Over 1,000 staff [enterprise] #### UC-A-002 / payroll-country-count Ask: How many countries do you run payroll in? Answer: pick one Requirement type: scale - 1 country only [single] - 2–3 countries [few] - 4–10 countries [multi] - Over 10 countries [global] #### UC-A-002 / staff-bank-access Ask: Do all staff have bank accounts in their country of employment? Answer: pick one Requirement type: general - Yes, all staff have local bank accounts [all-banked] - Most do, but some in remote locations do not [mostly-banked] - Many staff lack formal bank accounts [many-unbanked] - Varies significantly by country [varies] #### UC-A-002 / salary-frequency Ask: How frequently are staff paid? Answer: pick one Requirement type: money - Monthly [monthly] - Bi-weekly / Fortnightly [biweekly] - Weekly [weekly] - Varies by country or contract type [varies] #### UC-A-002 / salary-range Ask: What is the typical salary range per payment (in USD equivalent)? Answer: pick one Requirement type: money - Under $500/month [low] - $500–$2,000/month [medium] - $2,000–$5,000/month [high] - Over $5,000/month [very-high] - Wide range, from local hires to international staff [wide-range] #### UC-A-002 / tax-compliance Ask: How are tax withholding and statutory deductions currently handled across countries? Answer: pick one Requirement type: legal-checks - Centralised: HQ calculates all deductions [centralised] - Decentralised: each country office handles locally [decentralised] - Outsourced to payroll provider per country [outsourced] - Inconsistent: no standardised process [inconsistent] #### UC-A-002 / payroll-system Ask: What payroll or HR system is currently used? Answer: pick all that apply Requirement type: integration - Enterprise ERP payroll module [sap] - Cloud HR and payroll suite [oracle] - Outsourced payroll provider [payroll-provider] - Custom internal system [custom] - Spreadsheet-based [spreadsheet] - No centralised payroll system [none] #### UC-A-002 / currency-salary Ask: In what currency are salaries denominated vs. what currency do staff need to receive? Answer: pick one Requirement type: money - Denominated and paid in same local currency [same-currency] - Denominated in USD/EUR, paid in local currency [hq-to-local] - Mix: some in HQ currency, some in local [mixed] - Staff choose preferred currency [staff-choice] #### UC-A-002 / staff-device-access Ask: What devices do staff typically have access to? Answer: pick one Requirement type: devices - All staff have smartphones [smartphone] - Most have smartphones, some feature phones [mostly-smartphone] - Mix of smartphones and feature phones [mixed] - Varies significantly by location [varies] #### UC-A-002 / sq-UC-A-002-001 Ask: How is payroll data currently audited across jurisdictions for tax compliance? Answer: pick one Requirement type: legal-checks - Per-country audit trail [per-country-audit-trail] - Centralised global audit [centralised-global-audit] - Donor-specific audit [donor-specific-audit] - Statutory compliance only [statutory-only] #### UC-A-002 / beneficiary-choice Ask: How will beneficiaries exercise choice in how they receive and use this service? Answer: pick one Requirement type: usability - Beneficiaries choose between delivery methods (cash, voucher, mobile money, direct) [delivery-choice] - Beneficiaries choose preferred merchants or service points [merchant-choice] - Beneficiaries control their own data sharing preferences [data-choice] - Multiple choice dimensions (delivery + merchant + data) [full-choice] - Limited choice: programme constraints determine delivery [limited] ### UC-A-003: Vendor and supplier payments in remote locations Security level: Standard. #### UC-A-003 / corridor-count Ask: How many countries does your organisation send transfer funds from? Answer: pick one Requirement type: scale - Single country [single] - 2–3 countries [2-3] - 4–5 countries [4-5] - More than 5 countries [5-plus] #### UC-A-003 / origination-country-1 Ask: Which country do you most frequently initiate transfers from? Answer: pick one Show only if the answer to corridor-count is single or more. Requirement type: money - United States [united-states] - United Kingdom [united-kingdom] - Germany [germany] - Netherlands [netherlands] - Switzerland [switzerland] - Belgium [belgium] - France [france] - Sweden [sweden] - Norway [norway] - Denmark [denmark] - Canada [canada] - Australia [australia] - Japan [japan] - Ireland [ireland] - Italy [italy] - Spain [spain] - Austria [austria] - Finland [finland] - Luxembourg [luxembourg] - South Korea [south-korea] - New Zealand [new-zealand] - United Arab Emirates [united-arab-emirates] - Singapore [singapore] - Other [other] #### UC-A-003 / origination-country-2 Ask: Second most common transfer origination country (if applicable) Answer: pick one Show only if the answer to corridor-count is 2-3 or more. Requirement type: money - United States [united-states] - United Kingdom [united-kingdom] - Germany [germany] - Netherlands [netherlands] - Switzerland [switzerland] - Belgium [belgium] - France [france] - Sweden [sweden] - Norway [norway] - Denmark [denmark] - Canada [canada] - Australia [australia] - Japan [japan] - Ireland [ireland] - Italy [italy] - Spain [spain] - Austria [austria] - Finland [finland] - Luxembourg [luxembourg] - South Korea [south-korea] - New Zealand [new-zealand] - United Arab Emirates [united-arab-emirates] - Singapore [singapore] - Other [other] #### UC-A-003 / origination-country-3 Ask: Third transfer origination country (if applicable) Answer: pick one Show only if the answer to corridor-count is 2-3 or more. Requirement type: money - United States [united-states] - United Kingdom [united-kingdom] - Germany [germany] - Netherlands [netherlands] - Switzerland [switzerland] - Belgium [belgium] - France [france] - Sweden [sweden] - Norway [norway] - Denmark [denmark] - Canada [canada] - Australia [australia] - Japan [japan] - Ireland [ireland] - Italy [italy] - Spain [spain] - Austria [austria] - Finland [finland] - Luxembourg [luxembourg] - South Korea [south-korea] - New Zealand [new-zealand] - United Arab Emirates [united-arab-emirates] - Singapore [singapore] - Other [other] #### UC-A-003 / origination-country-4 Ask: Fourth transfer origination country (if applicable) Answer: pick one Show only if the answer to corridor-count is 4-5 or more. Requirement type: money - United States [united-states] - United Kingdom [united-kingdom] - Germany [germany] - Netherlands [netherlands] - Switzerland [switzerland] - Belgium [belgium] - France [france] - Sweden [sweden] - Norway [norway] - Denmark [denmark] - Canada [canada] - Australia [australia] - Japan [japan] - Ireland [ireland] - Italy [italy] - Spain [spain] - Austria [austria] - Finland [finland] - Luxembourg [luxembourg] - South Korea [south-korea] - New Zealand [new-zealand] - United Arab Emirates [united-arab-emirates] - Singapore [singapore] - Other [other] #### UC-A-003 / origination-country-5 Ask: Fifth transfer origination country (if applicable) Answer: pick one Show only if the answer to corridor-count is 4-5 or more. Requirement type: money - United States [united-states] - United Kingdom [united-kingdom] - Germany [germany] - Netherlands [netherlands] - Switzerland [switzerland] - Belgium [belgium] - France [france] - Sweden [sweden] - Norway [norway] - Denmark [denmark] - Canada [canada] - Australia [australia] - Japan [japan] - Ireland [ireland] - Italy [italy] - Spain [spain] - Austria [austria] - Finland [finland] - Luxembourg [luxembourg] - South Korea [south-korea] - New Zealand [new-zealand] - United Arab Emirates [united-arab-emirates] - Singapore [singapore] - Other [other] #### UC-A-003 / funding-method Ask: How does your organisation currently fund international transfers or payments? Answer: pick one Requirement type: money - Bank transfer from organisation account [bank-transfer] - Card payment from organisation [card-payment] - Direct stablecoin funding (organisation already holds stablecoins) [direct-stablecoin] - Mixed: bank transfer for most, card for urgent payments [mixed-methods] #### UC-A-003 / vendor-count Ask: How many active vendors/suppliers do you regularly pay? Answer: pick one Requirement type: scale - Under 50 vendors [small] - 50–200 vendors [medium] - 200–1,000 vendors [large] - Over 1,000 vendors [enterprise] #### UC-A-003 / vendor-location-type Ask: Where are most of your vendors located? Answer: pick all that apply Requirement type: general - Urban centres with banking infrastructure [urban-banked] - Peri-urban areas with mobile money access [peri-urban] - Remote rural areas with limited connectivity [remote-rural] - Conflict/crisis zones with minimal infrastructure [conflict-zone] - International suppliers (cross-border) [international] #### UC-A-003 / vendor-payment-current Ask: How are vendors currently paid? Answer: pick all that apply Requirement type: money - Bank transfer [bank] - Mobile money [mobile-money] - Physical cash [cash] - Cheque [cheque] - Hawala or informal transfer [informal] - Pre-paid cards [prepaid-cards] #### UC-A-003 / vendor-payment-conditions Ask: Are vendor payments tied to delivery verification or contract milestones? Answer: pick one Requirement type: money - Yes, payment on confirmed delivery/inspection [delivery-verified] - Yes, milestone-based payments against contract [milestone] - Partial, advance + balance on delivery [partial] - No, payment on invoice submission [invoice-only] #### UC-A-003 / vendor-avg-payment Ask: What is the typical vendor payment amount? Answer: pick one Requirement type: money - Under $100 [micro] - $100–$1,000 [small] - $1,000–$10,000 [medium] - $10,000–$100,000 [large] - Over $100,000 [very-large] - Highly variable [variable] #### UC-A-003 / vendor-screening Ask: What due diligence or screening is required before paying a vendor? Answer: pick all that apply Requirement type: legal-checks - Sanctions/OFAC screening [sanctions] - Vendor identity verification [vendor-kyc] - Beneficial ownership checks [beneficial-ownership] - Conflict of interest checks [conflict-interest] - Donor-specific vetting requirements [donor-vetting] - Minimal: basic vendor registration only [minimal] #### UC-A-003 / vendor-onboarding Ask: How tech-savvy are your vendors? Could they use a digital wallet? Answer: pick one Requirement type: usability - Most are comfortable with smartphones and apps [tech-comfortable] - Can use basic mobile money but not apps [basic-mobile] - Limited tech skills: need very simple interface [limited-tech] - Varies widely, from tech-savvy to no tech at all [varies] #### UC-A-003 / procurement-audit Ask: How important is a transparent audit trail for procurement payments? Answer: pick one Requirement type: audit-trail - Critical: donors audit individual transactions [critical] - Important: need to demonstrate value for money [important] - Standard: normal financial record-keeping [standard] - Not a priority currently [low] #### UC-A-003 / sq-UC-A-003-001 Ask: What proof-of-delivery systems do you currently use before vendor payment release? Answer: pick one Requirement type: general - GPS timestamp and location verification [gps-timestamp] - Photo evidence at delivery location [photo-verification] - Beneficiary confirmation signature [beneficiary-confirmation] - Third-party inspection verification [third-party-inspection] - Self-reported by vendor [self-reported] #### UC-A-003 / beneficiary-choice Ask: How will beneficiaries exercise choice in how they receive and use this service? Answer: pick one Requirement type: usability - Beneficiaries choose between delivery methods (cash, voucher, mobile money, direct) [delivery-choice] - Beneficiaries choose preferred merchants or service points [merchant-choice] - Beneficiaries control their own data sharing preferences [data-choice] - Multiple choice dimensions (delivery + merchant + data) [full-choice] - Limited choice: programme constraints determine delivery [limited] ### UC-A-004: Inter-office fund transfers across country programmes Security level: Higher. #### UC-A-004 / corridor-count Ask: How many countries does your organisation send transfer funds from? Answer: pick one Requirement type: scale - Single country [single] - 2–3 countries [2-3] - 4–5 countries [4-5] - More than 5 countries [5-plus] #### UC-A-004 / origination-country-1 Ask: Which country do you most frequently initiate transfers from? Answer: pick one Show only if the answer to corridor-count is single or more. Requirement type: money - United States [united-states] - United Kingdom [united-kingdom] - Germany [germany] - Netherlands [netherlands] - Switzerland [switzerland] - Belgium [belgium] - France [france] - Sweden [sweden] - Norway [norway] - Denmark [denmark] - Canada [canada] - Australia [australia] - Japan [japan] - Ireland [ireland] - Italy [italy] - Spain [spain] - Austria [austria] - Finland [finland] - Luxembourg [luxembourg] - South Korea [south-korea] - New Zealand [new-zealand] - United Arab Emirates [united-arab-emirates] - Singapore [singapore] - Other [other] #### UC-A-004 / origination-country-2 Ask: Second most common transfer origination country (if applicable) Answer: pick one Show only if the answer to corridor-count is 2-3 or more. Requirement type: money - United States [united-states] - United Kingdom [united-kingdom] - Germany [germany] - Netherlands [netherlands] - Switzerland [switzerland] - Belgium [belgium] - France [france] - Sweden [sweden] - Norway [norway] - Denmark [denmark] - Canada [canada] - Australia [australia] - Japan [japan] - Ireland [ireland] - Italy [italy] - Spain [spain] - Austria [austria] - Finland [finland] - Luxembourg [luxembourg] - South Korea [south-korea] - New Zealand [new-zealand] - United Arab Emirates [united-arab-emirates] - Singapore [singapore] - Other [other] #### UC-A-004 / origination-country-3 Ask: Third transfer origination country (if applicable) Answer: pick one Show only if the answer to corridor-count is 2-3 or more. Requirement type: money - United States [united-states] - United Kingdom [united-kingdom] - Germany [germany] - Netherlands [netherlands] - Switzerland [switzerland] - Belgium [belgium] - France [france] - Sweden [sweden] - Norway [norway] - Denmark [denmark] - Canada [canada] - Australia [australia] - Japan [japan] - Ireland [ireland] - Italy [italy] - Spain [spain] - Austria [austria] - Finland [finland] - Luxembourg [luxembourg] - South Korea [south-korea] - New Zealand [new-zealand] - United Arab Emirates [united-arab-emirates] - Singapore [singapore] - Other [other] #### UC-A-004 / origination-country-4 Ask: Fourth transfer origination country (if applicable) Answer: pick one Show only if the answer to corridor-count is 4-5 or more. Requirement type: money - United States [united-states] - United Kingdom [united-kingdom] - Germany [germany] - Netherlands [netherlands] - Switzerland [switzerland] - Belgium [belgium] - France [france] - Sweden [sweden] - Norway [norway] - Denmark [denmark] - Canada [canada] - Australia [australia] - Japan [japan] - Ireland [ireland] - Italy [italy] - Spain [spain] - Austria [austria] - Finland [finland] - Luxembourg [luxembourg] - South Korea [south-korea] - New Zealand [new-zealand] - United Arab Emirates [united-arab-emirates] - Singapore [singapore] - Other [other] #### UC-A-004 / origination-country-5 Ask: Fifth transfer origination country (if applicable) Answer: pick one Show only if the answer to corridor-count is 4-5 or more. Requirement type: money - United States [united-states] - United Kingdom [united-kingdom] - Germany [germany] - Netherlands [netherlands] - Switzerland [switzerland] - Belgium [belgium] - France [france] - Sweden [sweden] - Norway [norway] - Denmark [denmark] - Canada [canada] - Australia [australia] - Japan [japan] - Ireland [ireland] - Italy [italy] - Spain [spain] - Austria [austria] - Finland [finland] - Luxembourg [luxembourg] - South Korea [south-korea] - New Zealand [new-zealand] - United Arab Emirates [united-arab-emirates] - Singapore [singapore] - Other [other] #### UC-A-004 / funding-method Ask: How does your organisation currently fund international transfers or payments? Answer: pick one Requirement type: money - Bank transfer from organisation account [bank-transfer] - Card payment from organisation [card-payment] - Direct stablecoin funding (organisation already holds stablecoins) [direct-stablecoin] - Mixed: bank transfer for most, card for urgent payments [mixed-methods] #### UC-A-004 / office-count Ask: How many country offices or programme sites transfer funds between each other? Answer: pick one Requirement type: scale - 2-3 offices [small] - 4-10 offices [medium] - 11-25 offices [large] - Over 25 offices [enterprise] #### UC-A-004 / transfer-frequency Ask: How frequently do inter-office transfers occur? Answer: pick one Requirement type: money - Weekly or more frequently [weekly] - Monthly [monthly] - Quarterly [quarterly] - Ad-hoc / as-needed only [adhoc] #### UC-A-004 / transfer-size-interoffice Ask: What is the typical size of inter-office fund transfers? Answer: pick one Requirement type: scale - Under $10,000 [small] - $10,000–$100,000 [medium] - $100,000–$1,000,000 [large] - Over $1,000,000 [very-large] - Highly variable: ranges across all sizes depending on transfer type [variable] #### UC-A-004 / reconciliation-interoffice Ask: How is inter-office reconciliation currently handled? Answer: pick one Requirement type: audit-trail - Real-time automated reconciliation [realtime] - Manual reconciliation at month-end [monthly-manual] - Periodic but inconsistent [inconsistent] - Problematic: frequent discrepancies [problematic] #### UC-A-004 / accounting-integration-interoffice Ask: Do all your offices use the same accounting system? Answer: pick one Requirement type: integration - Yes, single centralised system [centralised] - Same system but separate instances per country [same-separate] - Different systems across offices [different] - Some offices have no formal system [partial] #### UC-A-004 / sq-UC-A-004-001 Ask: What currency conversion approach do you currently use for inter-office transfers? Answer: pick one Requirement type: general - Real-time FX rate conversion [real-time-fx] - Locked rate at time of approval [locked-rate] - Stablecoin as bridge currency [stablecoin-bridge] - Fiat-only transfers (no crypto bridge) [fiat-only] - Multi-hop route optimization [multi-hop] #### UC-A-004 / offramp-delivery Ask: How will recipients receive funds at the last mile? Answer: pick one Requirement type: general - Mobile money [mobile-money] - Bank transfer to beneficiary/recipient account [bank-transfer] - Cash via agent network [agent-cash] - Mixed: depends on recipient location and access [mixed] ### UC-A-005: Emergency rapid-disbursement payments Security level: Higher. #### UC-A-005 / corridor-count Ask: How many countries does your organisation send transfer funds from? Answer: pick one Requirement type: scale - Single country [single] - 2–3 countries [2-3] - 4–5 countries [4-5] - More than 5 countries [5-plus] #### UC-A-005 / origination-country-1 Ask: Which country do you most frequently initiate transfers from? Answer: pick one Show only if the answer to corridor-count is single or more. Requirement type: money - United States [united-states] - United Kingdom [united-kingdom] - Germany [germany] - Netherlands [netherlands] - Switzerland [switzerland] - Belgium [belgium] - France [france] - Sweden [sweden] - Norway [norway] - Denmark [denmark] - Canada [canada] - Australia [australia] - Japan [japan] - Ireland [ireland] - Italy [italy] - Spain [spain] - Austria [austria] - Finland [finland] - Luxembourg [luxembourg] - South Korea [south-korea] - New Zealand [new-zealand] - United Arab Emirates [united-arab-emirates] - Singapore [singapore] - Other [other] #### UC-A-005 / origination-country-2 Ask: Second most common transfer origination country (if applicable) Answer: pick one Show only if the answer to corridor-count is 2-3 or more. Requirement type: money - United States [united-states] - United Kingdom [united-kingdom] - Germany [germany] - Netherlands [netherlands] - Switzerland [switzerland] - Belgium [belgium] - France [france] - Sweden [sweden] - Norway [norway] - Denmark [denmark] - Canada [canada] - Australia [australia] - Japan [japan] - Ireland [ireland] - Italy [italy] - Spain [spain] - Austria [austria] - Finland [finland] - Luxembourg [luxembourg] - South Korea [south-korea] - New Zealand [new-zealand] - United Arab Emirates [united-arab-emirates] - Singapore [singapore] - Other [other] #### UC-A-005 / origination-country-3 Ask: Third transfer origination country (if applicable) Answer: pick one Show only if the answer to corridor-count is 2-3 or more. Requirement type: money - United States [united-states] - United Kingdom [united-kingdom] - Germany [germany] - Netherlands [netherlands] - Switzerland [switzerland] - Belgium [belgium] - France [france] - Sweden [sweden] - Norway [norway] - Denmark [denmark] - Canada [canada] - Australia [australia] - Japan [japan] - Ireland [ireland] - Italy [italy] - Spain [spain] - Austria [austria] - Finland [finland] - Luxembourg [luxembourg] - South Korea [south-korea] - New Zealand [new-zealand] - United Arab Emirates [united-arab-emirates] - Singapore [singapore] - Other [other] #### UC-A-005 / origination-country-4 Ask: Fourth transfer origination country (if applicable) Answer: pick one Show only if the answer to corridor-count is 4-5 or more. Requirement type: money - United States [united-states] - United Kingdom [united-kingdom] - Germany [germany] - Netherlands [netherlands] - Switzerland [switzerland] - Belgium [belgium] - France [france] - Sweden [sweden] - Norway [norway] - Denmark [denmark] - Canada [canada] - Australia [australia] - Japan [japan] - Ireland [ireland] - Italy [italy] - Spain [spain] - Austria [austria] - Finland [finland] - Luxembourg [luxembourg] - South Korea [south-korea] - New Zealand [new-zealand] - United Arab Emirates [united-arab-emirates] - Singapore [singapore] - Other [other] #### UC-A-005 / origination-country-5 Ask: Fifth transfer origination country (if applicable) Answer: pick one Show only if the answer to corridor-count is 4-5 or more. Requirement type: money - United States [united-states] - United Kingdom [united-kingdom] - Germany [germany] - Netherlands [netherlands] - Switzerland [switzerland] - Belgium [belgium] - France [france] - Sweden [sweden] - Norway [norway] - Denmark [denmark] - Canada [canada] - Australia [australia] - Japan [japan] - Ireland [ireland] - Italy [italy] - Spain [spain] - Austria [austria] - Finland [finland] - Luxembourg [luxembourg] - South Korea [south-korea] - New Zealand [new-zealand] - United Arab Emirates [united-arab-emirates] - Singapore [singapore] - Other [other] #### UC-A-005 / funding-method Ask: How does your organisation currently fund international transfers or payments? Answer: pick one Requirement type: money - Bank transfer from organisation account [bank-transfer] - Card payment from organisation [card-payment] - Direct stablecoin funding (organisation already holds stablecoins) [direct-stablecoin] - Mixed: bank transfer for most, card for urgent payments [mixed-methods] #### UC-A-005 / emergency-response-time Ask: In an emergency, how quickly do you need to get funds to beneficiaries from the moment a decision is made? Answer: pick one Requirement type: money - Within minutes [minutes] - Within hours (same day) [hours] - Within 24 hours [24h] - Within 48-72 hours [72h] #### UC-A-005 / emergency-scale Ask: In a typical emergency response, how many beneficiaries need to receive payments? Answer: pick one Requirement type: scale - Under 500 beneficiaries [small] - 500–5,000 beneficiaries [medium] - 5,000–50,000 beneficiaries [large] - Over 50,000 beneficiaries [massive] #### UC-A-005 / emergency-beneficiary-registration Ask: Are beneficiaries typically pre-registered before an emergency, or do you register on-the-fly? Answer: pick one Requirement type: credentials - Pre-registered from existing programme lists [pre-registered] - Mix: some pre-registered, some registered during response [mixed] - Mostly registered during the emergency response [on-the-fly] - Varies by emergency type [varies] #### UC-A-005 / emergency-conditions Ask: Are emergency payments unconditional or tied to conditions? Answer: pick one Requirement type: money - Unconditional: immediate cash transfer [unconditional] - Triggered by verified event (flood, earthquake, etc.) [event-triggered] - Conditional on beneficiary being in affected area [location-conditional] - Multi-tranche: immediate + follow-up conditional payments [multi-tranche] #### UC-A-005 / emergency-connectivity Ask: What connectivity can you expect in your typical emergency response areas? Answer: pick one Requirement type: offline - Urban: reliable mobile data [urban] - Semi-urban: intermittent connectivity [semi-urban] - Rural: very limited, 2G at best [rural] - Disaster-affected: infrastructure may be down [disaster-affected] #### UC-A-005 / emergency-approval Ask: What approval process is needed to trigger emergency disbursements? Answer: pick one Requirement type: governance - Pre-authorised: funds released automatically on trigger [pre-authorised] - Single emergency authoriser [single] - Rapid dual-authorisation (2 signers) [dual-rapid] - Standard multi-level approval even in emergencies [standard] #### UC-A-005 / emergency-device-beneficiary Ask: What devices do beneficiaries in emergency contexts typically have? Answer: pick one Requirement type: devices - Smartphones [smartphone] - Feature phones (SMS/USSD) [feature-phone] - No devices, need agent/kiosk distribution [no-device] - Devices may be lost/destroyed in disaster [devices-lost] #### UC-A-005 / emergency-amount Ask: What is the typical emergency payment amount per beneficiary? Answer: pick one Requirement type: money - Under $25 [micro] - $25–$100 [small] - $100–$500 [medium] - Over $500 [large] - Varies by emergency and programme [variable] #### UC-A-005 / sq-UC-A-005-001 Ask: What fallback disbursement approach do you currently use if primary channels fail during an emergency? Answer: pick one Requirement type: general - Mobile money network backup [mobile-money-backup] - Cash delivery via trusted agent [cash-via-agent] - Pre-loaded card activation [pre-loaded-cards] - Physical voucher system [voucher-system] - direct relay network [peer-relay] #### UC-A-005 / offramp-delivery Ask: How will recipients receive funds at the last mile? Answer: pick one Requirement type: general - Mobile money [mobile-money] - Bank transfer to beneficiary/recipient account [bank-transfer] - Cash via agent network [agent-cash] - Mixed: depends on recipient location and access [mixed] #### UC-A-005 / beneficiary-choice Ask: How will beneficiaries exercise choice in how they receive and use this service? Answer: pick one Requirement type: usability - Beneficiaries choose between delivery methods (cash, voucher, mobile money, direct) [delivery-choice] - Beneficiaries choose preferred merchants or service points [merchant-choice] - Beneficiaries control their own data sharing preferences [data-choice] - Multiple choice dimensions (delivery + merchant + data) [full-choice] - Limited choice: programme constraints determine delivery [limited] ### UC-A-006: Multi-currency treasury management Security level: Higher. #### UC-A-006 / corridor-count Ask: How many countries does your organisation send transfer funds from? Answer: pick one Requirement type: scale - Single country [single] - 2–3 countries [2-3] - 4–5 countries [4-5] - More than 5 countries [5-plus] #### UC-A-006 / origination-country-1 Ask: Which country do you most frequently initiate transfers from? Answer: pick one Show only if the answer to corridor-count is single or more. Requirement type: money - United States [united-states] - United Kingdom [united-kingdom] - Germany [germany] - Netherlands [netherlands] - Switzerland [switzerland] - Belgium [belgium] - France [france] - Sweden [sweden] - Norway [norway] - Denmark [denmark] - Canada [canada] - Australia [australia] - Japan [japan] - Ireland [ireland] - Italy [italy] - Spain [spain] - Austria [austria] - Finland [finland] - Luxembourg [luxembourg] - South Korea [south-korea] - New Zealand [new-zealand] - United Arab Emirates [united-arab-emirates] - Singapore [singapore] - Other [other] #### UC-A-006 / origination-country-2 Ask: Second most common transfer origination country (if applicable) Answer: pick one Show only if the answer to corridor-count is 2-3 or more. Requirement type: money - United States [united-states] - United Kingdom [united-kingdom] - Germany [germany] - Netherlands [netherlands] - Switzerland [switzerland] - Belgium [belgium] - France [france] - Sweden [sweden] - Norway [norway] - Denmark [denmark] - Canada [canada] - Australia [australia] - Japan [japan] - Ireland [ireland] - Italy [italy] - Spain [spain] - Austria [austria] - Finland [finland] - Luxembourg [luxembourg] - South Korea [south-korea] - New Zealand [new-zealand] - United Arab Emirates [united-arab-emirates] - Singapore [singapore] - Other [other] #### UC-A-006 / origination-country-3 Ask: Third transfer origination country (if applicable) Answer: pick one Show only if the answer to corridor-count is 2-3 or more. Requirement type: money - United States [united-states] - United Kingdom [united-kingdom] - Germany [germany] - Netherlands [netherlands] - Switzerland [switzerland] - Belgium [belgium] - France [france] - Sweden [sweden] - Norway [norway] - Denmark [denmark] - Canada [canada] - Australia [australia] - Japan [japan] - Ireland [ireland] - Italy [italy] - Spain [spain] - Austria [austria] - Finland [finland] - Luxembourg [luxembourg] - South Korea [south-korea] - New Zealand [new-zealand] - United Arab Emirates [united-arab-emirates] - Singapore [singapore] - Other [other] #### UC-A-006 / origination-country-4 Ask: Fourth transfer origination country (if applicable) Answer: pick one Show only if the answer to corridor-count is 4-5 or more. Requirement type: money - United States [united-states] - United Kingdom [united-kingdom] - Germany [germany] - Netherlands [netherlands] - Switzerland [switzerland] - Belgium [belgium] - France [france] - Sweden [sweden] - Norway [norway] - Denmark [denmark] - Canada [canada] - Australia [australia] - Japan [japan] - Ireland [ireland] - Italy [italy] - Spain [spain] - Austria [austria] - Finland [finland] - Luxembourg [luxembourg] - South Korea [south-korea] - New Zealand [new-zealand] - United Arab Emirates [united-arab-emirates] - Singapore [singapore] - Other [other] #### UC-A-006 / origination-country-5 Ask: Fifth transfer origination country (if applicable) Answer: pick one Show only if the answer to corridor-count is 4-5 or more. Requirement type: money - United States [united-states] - United Kingdom [united-kingdom] - Germany [germany] - Netherlands [netherlands] - Switzerland [switzerland] - Belgium [belgium] - France [france] - Sweden [sweden] - Norway [norway] - Denmark [denmark] - Canada [canada] - Australia [australia] - Japan [japan] - Ireland [ireland] - Italy [italy] - Spain [spain] - Austria [austria] - Finland [finland] - Luxembourg [luxembourg] - South Korea [south-korea] - New Zealand [new-zealand] - United Arab Emirates [united-arab-emirates] - Singapore [singapore] - Other [other] #### UC-A-006 / funding-method Ask: How does your organisation currently fund international transfers or payments? Answer: pick one Requirement type: money - Bank transfer from organisation account [bank-transfer] - Card payment from organisation [card-payment] - Direct stablecoin funding (organisation already holds stablecoins) [direct-stablecoin] - Mixed: bank transfer for most, card for urgent payments [mixed-methods] #### UC-A-006 / fx-exposure Ask: How significant is your FX exposure and currency risk? Answer: pick one Requirement type: money - Minimal: most operations in one currency [minimal] - Moderate: predictable currency needs [moderate] - Significant: volatile currencies, large cross-currency flows [significant] - Critical: operating in hyperinflationary or crisis economies [critical] #### UC-A-006 / treasury-operations Ask: What treasury operations do you need to perform regularly? Answer: pick all that apply Requirement type: money - Currency conversion (buy/sell) [conversion] - Fund allocation across country programmes [allocation] - Cash position monitoring across all currencies [monitoring] - Automated rebalancing between currencies [rebalancing] - Yield generation on idle funds [yield] - Donor fund ring-fencing by currency [ringfencing] #### UC-A-006 / treasury-approval Ask: What governance is required for treasury operations (conversions, allocations)? Answer: pick one Requirement type: money - Finance team operates autonomously within policy [autonomous] - Dual authorisation for all treasury actions [dual] - Threshold-based: auto below limit, approval above [threshold] - Board/senior approval for all significant actions [board] #### UC-A-006 / treasury-reporting Ask: What treasury reporting is needed? Answer: pick all that apply Requirement type: audit-trail - Real-time multi-currency dashboard [realtime-dashboard] - Daily/weekly treasury position reports [periodic-reports] - FX gain/loss tracking [fx-tracking] - Cash flow forecasting [forecasting] - Donor fund utilisation by currency [donor-utilisation] - Audit trail of all treasury actions [audit-trail] #### UC-A-006 / on-off-ramp-needs Ask: Where do you need fiat on-ramp and off-ramp capabilities? Answer: pick all that apply Requirement type: money - HQ country (on-ramp: fiat → stablecoin) [hq-onramp] - Field countries (off-ramp: stablecoin → local fiat) [field-offramp] - Both directions in multiple countries [bidirectional] - Regional hubs only [regional-hubs] #### UC-A-006 / sq-UC-A-006-001 Ask: What currency exposure thresholds should trigger automatic rebalancing? Answer: pick one Requirement type: general - Fixed percentage of portfolio [fixed-percentage] - Value-at-Risk (VaR) based [var-based] - Manual rebalancing only [manual-only] - Donor-directed thresholds [donor-directed] - Tiered by programme criticality [tiered-by-programme] #### UC-A-006 / sq-UC-A-006-003 Ask: What approach would you prefer for managing stablecoin exposure relative to fiat holdings? Answer: pick one Requirement type: general - Maximum percentage cap [max-percentage-cap] - Programme-specific allocation [programme-specific] - Full stablecoin settlement [full-stablecoin] - Stablecoin as hedge only [hedge-only] - Treasury officer discretion [treasury-discretion] #### UC-A-006 / volatility-exposure Ask: What is your organisation's primary currency volatility concern? Answer: pick one Requirement type: money - Holding funds in volatile local currencies between receipt and disbursement [holding-local] - FX losses during cross-border transfers [fx-transfer] - Multi-currency treasury with unpredictable conversion needs [multi-currency] - Donor currency differs from programme currency [donor-programme-mismatch] #### UC-A-006 / hedging-current-approach Ask: How does your organisation currently manage currency risk? Answer: pick one Requirement type: money - No active management, we accept the FX risk [none] - We use forward contracts or options with our bank [traditional-hedging] - We try to convert quickly to minimise exposure windows [speed-conversion] - We hold funds in USD or EUR to avoid local currency volatility [hard-currency-holding] #### UC-A-006 / stablecoin-trust-preference Ask: What level of regulatory backing do you require for stablecoins used in treasury? Answer: pick one Requirement type: money - Fully regulated, audited reserves (e.g., MiCA-compliant) [full-regulated] - Major stablecoins with published attestations [attested] - Any reputable stablecoin with reasonable backing [flexible] ### UC-A-007: Donor fund reconciliation and tracking Security level: Higher. #### UC-A-007 / corridor-count Ask: How many countries does your organisation send transfer funds from? Answer: pick one Requirement type: scale - Single country [single] - 2–3 countries [2-3] - 4–5 countries [4-5] - More than 5 countries [5-plus] #### UC-A-007 / origination-country-1 Ask: Which country do you most frequently initiate transfers from? Answer: pick one Show only if the answer to corridor-count is single or more. Requirement type: money - United States [united-states] - United Kingdom [united-kingdom] - Germany [germany] - Netherlands [netherlands] - Switzerland [switzerland] - Belgium [belgium] - France [france] - Sweden [sweden] - Norway [norway] - Denmark [denmark] - Canada [canada] - Australia [australia] - Japan [japan] - Ireland [ireland] - Italy [italy] - Spain [spain] - Austria [austria] - Finland [finland] - Luxembourg [luxembourg] - South Korea [south-korea] - New Zealand [new-zealand] - United Arab Emirates [united-arab-emirates] - Singapore [singapore] - Other [other] #### UC-A-007 / origination-country-2 Ask: Second most common transfer origination country (if applicable) Answer: pick one Show only if the answer to corridor-count is 2-3 or more. Requirement type: money - United States [united-states] - United Kingdom [united-kingdom] - Germany [germany] - Netherlands [netherlands] - Switzerland [switzerland] - Belgium [belgium] - France [france] - Sweden [sweden] - Norway [norway] - Denmark [denmark] - Canada [canada] - Australia [australia] - Japan [japan] - Ireland [ireland] - Italy [italy] - Spain [spain] - Austria [austria] - Finland [finland] - Luxembourg [luxembourg] - South Korea [south-korea] - New Zealand [new-zealand] - United Arab Emirates [united-arab-emirates] - Singapore [singapore] - Other [other] #### UC-A-007 / origination-country-3 Ask: Third transfer origination country (if applicable) Answer: pick one Show only if the answer to corridor-count is 2-3 or more. Requirement type: money - United States [united-states] - United Kingdom [united-kingdom] - Germany [germany] - Netherlands [netherlands] - Switzerland [switzerland] - Belgium [belgium] - France [france] - Sweden [sweden] - Norway [norway] - Denmark [denmark] - Canada [canada] - Australia [australia] - Japan [japan] - Ireland [ireland] - Italy [italy] - Spain [spain] - Austria [austria] - Finland [finland] - Luxembourg [luxembourg] - South Korea [south-korea] - New Zealand [new-zealand] - United Arab Emirates [united-arab-emirates] - Singapore [singapore] - Other [other] #### UC-A-007 / origination-country-4 Ask: Fourth transfer origination country (if applicable) Answer: pick one Show only if the answer to corridor-count is 4-5 or more. Requirement type: money - United States [united-states] - United Kingdom [united-kingdom] - Germany [germany] - Netherlands [netherlands] - Switzerland [switzerland] - Belgium [belgium] - France [france] - Sweden [sweden] - Norway [norway] - Denmark [denmark] - Canada [canada] - Australia [australia] - Japan [japan] - Ireland [ireland] - Italy [italy] - Spain [spain] - Austria [austria] - Finland [finland] - Luxembourg [luxembourg] - South Korea [south-korea] - New Zealand [new-zealand] - United Arab Emirates [united-arab-emirates] - Singapore [singapore] - Other [other] #### UC-A-007 / origination-country-5 Ask: Fifth transfer origination country (if applicable) Answer: pick one Show only if the answer to corridor-count is 4-5 or more. Requirement type: money - United States [united-states] - United Kingdom [united-kingdom] - Germany [germany] - Netherlands [netherlands] - Switzerland [switzerland] - Belgium [belgium] - France [france] - Sweden [sweden] - Norway [norway] - Denmark [denmark] - Canada [canada] - Australia [australia] - Japan [japan] - Ireland [ireland] - Italy [italy] - Spain [spain] - Austria [austria] - Finland [finland] - Luxembourg [luxembourg] - South Korea [south-korea] - New Zealand [new-zealand] - United Arab Emirates [united-arab-emirates] - Singapore [singapore] - Other [other] #### UC-A-007 / funding-method Ask: How does your organisation currently fund international transfers or payments? Answer: pick one Requirement type: money - Bank transfer from organisation account [bank-transfer] - Card payment from organisation [card-payment] - Direct stablecoin funding (organisation already holds stablecoins) [direct-stablecoin] - Mixed: bank transfer for most, card for urgent payments [mixed-methods] #### UC-A-007 / reconciliation-pain Ask: What is the biggest reconciliation challenge you face today? Answer: pick one Requirement type: audit-trail - Matching HQ disbursements to field receipts [disbursement-matching] - Tracking fund usage against donor restrictions [restriction-tracking] - Multi-currency reconciliation across offices [multi-currency] - Time lag: information arrives weeks after transactions [time-lag] - Manual data entry errors [data-errors] #### UC-A-007 / donor-reporting-format Ask: What reporting formats do your donors require? Answer: pick all that apply Requirement type: audit-trail - Donor-specific templates (each donor has own format) [donor-specific] - IATI standard reporting [iati] - Real-time dashboard access for donors [realtime-dashboard] - Periodic summary reports (PDF/spreadsheet) [periodic-summary] - Transaction-level detail export [transaction-detail] - No specific format required [flexible] #### UC-A-007 / fund-restrictions Ask: How complex are donor fund restrictions that need to be tracked? Answer: pick one Requirement type: money - Simple: restricted vs unrestricted only [simple] - Moderate, by programme, geography, and cost category [moderate] - Complex: nested restrictions with time limits and conditions [complex] - Very complex: different rules per donor with overlapping restrictions [very-complex] #### UC-A-007 / reconciliation-frequency Ask: How often does reconciliation need to happen? Answer: pick one Requirement type: audit-trail - Real-time / continuous [realtime] - Daily [daily] - Weekly [weekly] - Monthly [monthly] #### UC-A-007 / accounting-system-recon Ask: What accounting system do you use for reconciliation? Answer: pick one Requirement type: integration - Large enterprise ERP [sap] - Cloud ERP [oracle] - Small-business accounting software [quickbooks] - Custom/bespoke system [custom] - Spreadsheet-based [spreadsheet] - Multiple different systems across offices [multiple] #### UC-A-007 / sq-UC-A-007-001 Ask: How are donor fund restrictions currently enforced at the transaction level? Answer: pick one Requirement type: general - Hard block: prevent non-compliant transactions [hard-block] - Soft warning: alert but allow [soft-warning] - Post-hoc flag for later review [post-hoc-flag] - Require approval for restricted use [approval-workflow] - Automated rule enforcement [smart-contract-enforce] #### UC-A-007 / audit-mechanism-approach Ask: How should auditing and verification work for this solution? Answer: pick one Requirement type: audit-trail - Automatic checks that flag problems as they happen [automated-realtime] - Regular scheduled reviews with tamper-proof records [periodic-batch] - Ability to check any record at any time with proof it has not been altered [on-demand] - External auditors can log in and review records independently [third-party] ### UC-A-008: Real-time financial reporting across programmes Security level: Standard. #### UC-A-008 / reporting-stakeholders Ask: Who needs access to real-time financial reports? Answer: pick all that apply Requirement type: audit-trail - Senior leadership / Board [leadership] - Country/programme directors [programme-directors] - Finance team [finance] - Donors (external) [donors] - Auditors [auditors] - Field staff [field-staff] #### UC-A-008 / reporting-dimensions Ask: What dimensions do you need to report across? Answer: pick all that apply Requirement type: audit-trail - By country/office [country] - By programme/project [programme] - By donor/grant [donor] - By cost category (staff, supplies, etc.) [cost-category] - By currency [currency] - By time period (with comparisons) [time-period] #### UC-A-008 / data-sources Ask: Where does financial data currently live that needs to be consolidated? Answer: pick all that apply Requirement type: integration - Central ERP/accounting system [erp] - Country-level accounting systems [country-systems] - Bank statements [bank-statements] - Mobile money platforms [mobile-money] - Spreadsheets and manual records [spreadsheets] - Project management tools [pm-tools] #### UC-A-008 / reporting-latency Ask: How close to real-time does reporting need to be? Answer: pick one Requirement type: audit-trail - Real-time, within seconds of a transaction [realtime] - Near real-time, within an hour [near-realtime] - Same-day: end of day reporting is fine [same-day] - Next-day is acceptable [next-day] #### UC-A-008 / data-privacy-reporting Ask: Are there data privacy constraints on financial reporting (e.g., staff salaries, beneficiary payments)? Answer: pick one Requirement type: privacy - Yes, strict separation needed between sensitive and general data [strict] - Some, certain fields need masking for some audiences [moderate] - Minimal: all financial data can be seen by authorised users [minimal] - Nice to have, not a current requirement but would be beneficial if available [nice-to-have] #### UC-A-008 / sq-UC-A-008-001 Ask: What drill-down depth should reports support? Answer: pick one Requirement type: usability - Programme level only [programme-level-only] - Activity/project level [activity-level] - Transaction level [transaction-level] - Line-item detail [line-item] - Full audit trail [full-audit-trail] ### UC-A-009: Automated compliance reporting to donors Security level: Standard. #### UC-A-009 / donor-compliance-types Ask: What types of compliance reports do your donors require? Answer: pick all that apply Requirement type: legal-checks - Financial utilisation reports (spend vs budget) [utilisation] - Activity/output reports linked to spend [activity-output] - Sanctions screening compliance certificates [sanctions-cert] - Anti-fraud and anti-corruption attestations [anti-fraud] - Beneficiary verification reports [beneficiary-verification] - Audit-ready transaction logs [audit-logs] #### UC-A-009 / reporting-frequency-compliance Ask: How frequently are compliance reports due? Answer: pick one Requirement type: legal-checks - Monthly [monthly] - Quarterly [quarterly] - Annually [annually] - On-demand / ad-hoc [on-demand] - Varies by donor: multiple schedules [varies] #### UC-A-009 / compliance-rules-complexity Ask: How complex are the compliance rules across your donor portfolio? Answer: pick one Requirement type: legal-checks - Simple: similar rules across all donors [simple] - Moderate: each donor has some specific requirements [moderate] - Complex: significantly different rules per donor [complex] - Very complex: overlapping and sometimes conflicting rules [very-complex] #### UC-A-009 / compliance-staff-time Ask: How much staff time is currently spent on compliance reporting per month? Answer: pick one Requirement type: legal-checks - Under 1 day/month [minimal] - 1-5 days/month [moderate] - 1-2 weeks/month [significant] - Over 2 weeks/month (near full-time) [major] #### UC-A-009 / sq-UC-A-009-001 Ask: What process do you currently have for escalating compliance exceptions when detected? Answer: pick one Requirement type: general - Auto-flag to manager [auto-flag-manager] - Block transaction immediately [block-transaction] - Queue for compliance review [queue-for-review] - Notify donor automatically [notify-donor] - Multi-step escalation matrix [multi-step-escalation] #### UC-A-009 / accounting-integration Ask: How should this solution integrate with your existing accounting or financial systems? Answer: pick one Requirement type: integration - Direct integration with your existing accounting software [direct-erp] - Export-based: generate reports compatible with our accounting system [export-based] - Standalone ledger with manual reconciliation [standalone] - Not sure, need guidance on accounting integration [guidance-needed] ### UC-A-010: Petty cash and field office expense management Security level: Standard. #### UC-A-010 / corridor-count Ask: How many countries does your organisation send transfer funds from? Answer: pick one Requirement type: scale - Single country [single] - 2–3 countries [2-3] - 4–5 countries [4-5] - More than 5 countries [5-plus] #### UC-A-010 / origination-country-1 Ask: Which country do you most frequently initiate transfers from? Answer: pick one Show only if the answer to corridor-count is single or more. Requirement type: money - United States [united-states] - United Kingdom [united-kingdom] - Germany [germany] - Netherlands [netherlands] - Switzerland [switzerland] - Belgium [belgium] - France [france] - Sweden [sweden] - Norway [norway] - Denmark [denmark] - Canada [canada] - Australia [australia] - Japan [japan] - Ireland [ireland] - Italy [italy] - Spain [spain] - Austria [austria] - Finland [finland] - Luxembourg [luxembourg] - South Korea [south-korea] - New Zealand [new-zealand] - United Arab Emirates [united-arab-emirates] - Singapore [singapore] - Other [other] #### UC-A-010 / origination-country-2 Ask: Second most common transfer origination country (if applicable) Answer: pick one Show only if the answer to corridor-count is 2-3 or more. Requirement type: money - United States [united-states] - United Kingdom [united-kingdom] - Germany [germany] - Netherlands [netherlands] - Switzerland [switzerland] - Belgium [belgium] - France [france] - Sweden [sweden] - Norway [norway] - Denmark [denmark] - Canada [canada] - Australia [australia] - Japan [japan] - Ireland [ireland] - Italy [italy] - Spain [spain] - Austria [austria] - Finland [finland] - Luxembourg [luxembourg] - South Korea [south-korea] - New Zealand [new-zealand] - United Arab Emirates [united-arab-emirates] - Singapore [singapore] - Other [other] #### UC-A-010 / origination-country-3 Ask: Third transfer origination country (if applicable) Answer: pick one Show only if the answer to corridor-count is 2-3 or more. Requirement type: money - United States [united-states] - United Kingdom [united-kingdom] - Germany [germany] - Netherlands [netherlands] - Switzerland [switzerland] - Belgium [belgium] - France [france] - Sweden [sweden] - Norway [norway] - Denmark [denmark] - Canada [canada] - Australia [australia] - Japan [japan] - Ireland [ireland] - Italy [italy] - Spain [spain] - Austria [austria] - Finland [finland] - Luxembourg [luxembourg] - South Korea [south-korea] - New Zealand [new-zealand] - United Arab Emirates [united-arab-emirates] - Singapore [singapore] - Other [other] #### UC-A-010 / origination-country-4 Ask: Fourth transfer origination country (if applicable) Answer: pick one Show only if the answer to corridor-count is 4-5 or more. Requirement type: money - United States [united-states] - United Kingdom [united-kingdom] - Germany [germany] - Netherlands [netherlands] - Switzerland [switzerland] - Belgium [belgium] - France [france] - Sweden [sweden] - Norway [norway] - Denmark [denmark] - Canada [canada] - Australia [australia] - Japan [japan] - Ireland [ireland] - Italy [italy] - Spain [spain] - Austria [austria] - Finland [finland] - Luxembourg [luxembourg] - South Korea [south-korea] - New Zealand [new-zealand] - United Arab Emirates [united-arab-emirates] - Singapore [singapore] - Other [other] #### UC-A-010 / origination-country-5 Ask: Fifth transfer origination country (if applicable) Answer: pick one Show only if the answer to corridor-count is 4-5 or more. Requirement type: money - United States [united-states] - United Kingdom [united-kingdom] - Germany [germany] - Netherlands [netherlands] - Switzerland [switzerland] - Belgium [belgium] - France [france] - Sweden [sweden] - Norway [norway] - Denmark [denmark] - Canada [canada] - Australia [australia] - Japan [japan] - Ireland [ireland] - Italy [italy] - Spain [spain] - Austria [austria] - Finland [finland] - Luxembourg [luxembourg] - South Korea [south-korea] - New Zealand [new-zealand] - United Arab Emirates [united-arab-emirates] - Singapore [singapore] - Other [other] #### UC-A-010 / funding-method Ask: How does your organisation currently fund international transfers or payments? Answer: pick one Requirement type: money - Bank transfer from organisation account [bank-transfer] - Card payment from organisation [card-payment] - Direct stablecoin funding (organisation already holds stablecoins) [direct-stablecoin] - Mixed: bank transfer for most, card for urgent payments [mixed-methods] #### UC-A-010 / petty-cash-amount Ask: What is the typical monthly petty cash float per field office? Answer: pick one Requirement type: money - Under $500/month [small] - $500–$2,000/month [medium] - $2,000–$10,000/month [large] - Over $10,000/month [very-large] #### UC-A-010 / field-connectivity-pettycash Ask: What connectivity is available at your field offices? Answer: pick one Requirement type: offline - Reliable internet [reliable] - Intermittent connectivity [intermittent] - Very limited: 2G/EDGE at best [limited] - Mix: varies across offices [mixed] #### UC-A-010 / petty-cash-approval Ask: What approval workflow exists for petty cash expenditures? Answer: pick one Requirement type: governance - Field manager approves all expenses [manager] - Threshold-based: auto-approved below limit [threshold] - Post-hoc review only [post-hoc] - No formal approval process currently [none] #### UC-A-010 / sq-UC-A-010-001 Ask: What petty cash reconciliation frequency is required? Answer: pick one Requirement type: general - Daily close [daily-close] - Weekly reconciliation [weekly-reconcile] - Monthly audit [monthly-audit] - Real-time digital tracking [real-time-digital] - Event-triggered (handover, incident) [event-triggered] #### UC-A-010 / sq-UC-A-010-003 Ask: What is your current fraud detection and prevention approach for petty cash? Answer: pick one Requirement type: general - Dual approval for transactions [dual-approval] - Photo receipt required [photo-receipt-required] - Geo-fencing verification [geo-fence] - Random spot audits [random-audit] - Spending pattern analysis [spending-pattern-analysis] #### UC-A-010 / accounting-integration Ask: How should this solution integrate with your existing accounting or financial systems? Answer: pick one Requirement type: integration - Direct integration with your existing accounting software [direct-erp] - Export-based: generate reports compatible with our accounting system [export-based] - Standalone ledger with manual reconciliation [standalone] - Not sure, need guidance on accounting integration [guidance-needed] #### UC-A-010 / beneficiary-choice Ask: How will beneficiaries exercise choice in how they receive and use this service? Answer: pick one Requirement type: usability - Beneficiaries choose between delivery methods (cash, voucher, mobile money, direct) [delivery-choice] - Beneficiaries choose preferred merchants or service points [merchant-choice] - Beneficiaries control their own data sharing preferences [data-choice] - Multiple choice dimensions (delivery + merchant + data) [full-choice] - Limited choice: programme constraints determine delivery [limited] ### UC-A-011: Procurement process transparency and audit trails Security level: Standard. #### UC-A-011 / procurement-stages Ask: Which procurement stages need to be captured on an immutable audit trail? Answer: pick all that apply Requirement type: audit-trail - Requisition / purchase request [requisition] - Bid solicitation and evaluation [bidding] - Vendor selection and award [vendor-selection] - Contract signing [contract] - Delivery/receipt verification [delivery] - Invoice and payment [payment] - All of the above, end-to-end [end-to-end] #### UC-A-011 / audit-access Ask: Who needs access to the procurement audit trail? Answer: pick all that apply Requirement type: audit-trail - Internal auditors [internal-audit] - External auditors [external-audit] - Donors [donors] - Procurement team only [procurement-team] - Senior management [management] - Regulatory bodies [regulators] #### UC-A-011 / procurement-fraud-risk Ask: How significant is the fraud/collusion risk in your procurement processes? Answer: pick one Requirement type: legal-checks - High: operating in high-corruption environments [high] - Moderate: some risk areas [moderate] - Low: strong existing controls [low] - Unknown, lack visibility [unknown] #### UC-A-011 / sq-UC-A-011-001 Ask: What bid evaluation criteria should be recorded on-chain? Answer: pick one Requirement type: general - Price only [price-only] - Technical scoring [technical-scoring] - Committee votes [committee-votes] - All evaluation criteria [all-criteria] - Outcome only [outcome-only] #### UC-A-011 / sq-UC-A-011-003 Ask: How are sole-source procurement exceptions currently documented? Answer: pick one Requirement type: legal-checks - Justification memo required [justification-memo] - Multi-level approval chain [approval-chain] - Public disclosure [public-disclosure] - Donor notification [donor-notification] - Threshold-based exceptions [threshold-based] #### UC-A-011 / accounting-integration Ask: How should this solution integrate with your existing accounting or financial systems? Answer: pick one Requirement type: integration - Direct integration with your existing accounting software [direct-erp] - Export-based: generate reports compatible with our accounting system [export-based] - Standalone ledger with manual reconciliation [standalone] - Not sure, need guidance on accounting integration [guidance-needed] ### UC-A-012: Smart contract-based vendor payment terms Security level: Standard. #### UC-A-012 / stablecoin-approach Ask: What stablecoin approach is preferred for this solution? Answer: pick one Requirement type: money - A regulated digital dollar [usd-pegged] - EUR-pegged stablecoin [eur-pegged] - Multiple stablecoins depending on corridor [multi-stablecoin] - Not sure, need guidance on stablecoin selection [guidance-needed] #### UC-A-012 / payment-term-types Ask: What types of payment terms do you typically use with vendors? Answer: pick all that apply Requirement type: money - Payment on delivery/inspection [delivery] - Milestone-based payments [milestone] - Advance + balance on completion [advance-balance] - Time-based (30/60/90 day terms) [time-based] - Performance-linked payments [performance] - Retainer/recurring payments [retainer] #### UC-A-012 / delivery-verification-method Ask: How is delivery or completion currently verified before payment? Answer: pick one Requirement type: credentials - Physical inspection by field staff [physical-inspection] - Goods receipt note signed by warehouse [grn] - Third-party inspection [third-party] - Self-reported by vendor with evidence [self-reported] - No formal verification [none] #### UC-A-012 / vendor-dispute-resolution Ask: What happens when a vendor disputes that a milestone or delivery was completed? Answer: pick one Requirement type: governance - Vendor self-service portal to raise and track disputes [self-service] - Internal procurement team mediates disputes manually [internal-mediation] - Third-party arbitration for disputes above a threshold value [third-party] - Automated rules: system applies contract terms and flags exceptions [automated-rules] - Not sure, no formal dispute process exists yet [unsure] #### UC-A-012 / vendor-approval-workflow Ask: What approval workflow exists for vendor payments? Answer: pick one Requirement type: governance - Single approver for all vendor payments [single] - Dual approval (e.g. programme manager + finance) [dual] - Threshold-based: higher values need more approvers [threshold] - Fully delegated to field offices below a cap [delegated] - Not sure, approval rules vary or are informal [unsure] #### UC-A-012 / vendor-payment-reporting Ask: What vendor payment reporting do your auditors or donors require? Answer: pick one Requirement type: audit-trail - Basic payment ledger: date, amount, vendor, status [basic] - Contract-linked reporting: payments tied to specific contract milestones [contract-linked] - Donor-facing reporting: payments mapped to grant budgets and budget lines [donor-facing] - Full audit trail: every approval, change, and verification step recorded [full-audit] - Not sure, need guidance on reporting requirements [unsure] ### UC-A-013: Multi-party approval workflows across time zones Security level: Standard. #### UC-A-013 / approval-chain-length Ask: How many approvers are typically needed for financial transactions? Answer: pick one Requirement type: governance - 2 approvers (maker-checker) [two] - 3 approvers (sequential) [three] - 4+ approvers (complex hierarchy) [complex] - Varies by amount and type [varies] #### UC-A-013 / timezone-spread Ask: Across how many time zones do approvers operate? Answer: pick one Requirement type: governance - Same or adjacent time zones (1-3 hours difference) [adjacent] - Moderate spread (4-8 hours) [moderate] - Global spread (8-12+ hours) [global] #### UC-A-013 / approval-device Ask: What devices do your approvers typically use to authorise transactions? Answer: pick all that apply Requirement type: devices - Desktop/laptop (web browser) [desktop] - Mobile phone (app) [mobile-app] - Hardware security key [hardware-key] - Email/SMS confirmation [email-sms] #### UC-A-013 / sq-UC-A-013-001 Ask: What should happen when an approver is unavailable within the required timeframe? Answer: pick one Requirement type: general - Delegate to designated proxy [delegate-authority] - Escalate to supervisor [escalate-up] - Auto-approve after timeout [timeout-approve] - Auto-reject after timeout [timeout-reject] - Quorum-based alternative approval [quorum-based] #### UC-A-013 / coordination-layer-approach Ask: How do multiple parties currently coordinate decisions and actions? Answer: pick one Requirement type: governance - Shared workspace with real-time multi-party visibility [shared-workspace] - Event-driven notifications across organisations [event-driven] - Scheduled data sync between partner systems [scheduled-sync] - system-connected integration between organisation systems [api-based] ### UC-A-014: Restricted vs unrestricted fund segregation and tracking Security level: Standard. #### UC-A-014 / fund-types Ask: What types of fund restrictions do you need to enforce? Answer: pick all that apply Requirement type: money - Restricted by donor/grant [donor-restricted] - Restricted by programme/project [programme-restricted] - Restricted by geography/country [geography-restricted] - Restricted by expense category [category-restricted] - Time-restricted (spend by date) [time-restricted] - Unrestricted / core funding [unrestricted] #### UC-A-014 / restriction-overlap Ask: Do fund restrictions overlap (e.g., a single spend charged to multiple restricted funds)? Answer: pick one Requirement type: money - Yes, complex allocation across multiple restricted funds [complex-overlap] - Sometimes, occasional split charges [occasional] - No, each transaction is from a single fund source [no-overlap] #### UC-A-014 / fund-enforcement-level Ask: Should the system prevent restricted fund misuse or just flag it? Answer: pick one Requirement type: governance - Hard block: prevent any transaction violating restrictions [hard-block] - Soft warning: flag violations but allow with override [soft-warning] - Post-hoc detection: flag after the fact for review [post-hoc] #### UC-A-014 / sq-UC-A-014-001 Ask: How are fund restriction expiries or modifications currently handled? Answer: pick one Requirement type: general - Auto-unrestrict on expiry date [auto-unrestrict-on-date] - Require donor approval [require-donor-approval] - Archive and return to donor [archive-and-return] - Roll forward restriction period [roll-forward] - Notify and await decision [notify-and-await] #### UC-A-014 / accounting-integration Ask: How should this solution integrate with your existing accounting or financial systems? Answer: pick one Requirement type: integration - Direct integration with your existing accounting software [direct-erp] - Export-based: generate reports compatible with our accounting system [export-based] - Standalone ledger with manual reconciliation [standalone] - Not sure, need guidance on accounting integration [guidance-needed] #### UC-A-014 / reporting-approach Ask: What reporting capabilities does this solution need? Answer: pick one Requirement type: audit-trail - Automated donor/funder reporting with scheduled delivery [automated-donor] - Self-service dashboard with custom report builder [self-service] - Regulatory compliance reporting (government/authority) [regulatory] - Multi-audience reporting (donors, government, community) [multi-audience] #### UC-A-014 / access-control-approach Ask: What type of access control is needed? Answer: pick one Requirement type: privacy - Role-based access control (RBAC) [rbac] - Attribute-based access control (ABAC) [abac] - Multi-signature access (requires multiple approvals) [multi-sig] - Not sure, need guidance [guidance-needed] ### UC-A-015: Multi-year grant milestone-based disbursement automation Security level: Standard. #### UC-A-015 / corridor-count Ask: How many countries does your organisation send transfer funds from? Answer: pick one Requirement type: scale - Single country [single] - 2–3 countries [2-3] - 4–5 countries [4-5] - More than 5 countries [5-plus] #### UC-A-015 / origination-country-1 Ask: Which country do you most frequently initiate transfers from? Answer: pick one Show only if the answer to corridor-count is single or more. Requirement type: money - United States [united-states] - United Kingdom [united-kingdom] - Germany [germany] - Netherlands [netherlands] - Switzerland [switzerland] - Belgium [belgium] - France [france] - Sweden [sweden] - Norway [norway] - Denmark [denmark] - Canada [canada] - Australia [australia] - Japan [japan] - Ireland [ireland] - Italy [italy] - Spain [spain] - Austria [austria] - Finland [finland] - Luxembourg [luxembourg] - South Korea [south-korea] - New Zealand [new-zealand] - United Arab Emirates [united-arab-emirates] - Singapore [singapore] - Other [other] #### UC-A-015 / origination-country-2 Ask: Second most common transfer origination country (if applicable) Answer: pick one Show only if the answer to corridor-count is 2-3 or more. Requirement type: money - United States [united-states] - United Kingdom [united-kingdom] - Germany [germany] - Netherlands [netherlands] - Switzerland [switzerland] - Belgium [belgium] - France [france] - Sweden [sweden] - Norway [norway] - Denmark [denmark] - Canada [canada] - Australia [australia] - Japan [japan] - Ireland [ireland] - Italy [italy] - Spain [spain] - Austria [austria] - Finland [finland] - Luxembourg [luxembourg] - South Korea [south-korea] - New Zealand [new-zealand] - United Arab Emirates [united-arab-emirates] - Singapore [singapore] - Other [other] #### UC-A-015 / origination-country-3 Ask: Third transfer origination country (if applicable) Answer: pick one Show only if the answer to corridor-count is 2-3 or more. Requirement type: money - United States [united-states] - United Kingdom [united-kingdom] - Germany [germany] - Netherlands [netherlands] - Switzerland [switzerland] - Belgium [belgium] - France [france] - Sweden [sweden] - Norway [norway] - Denmark [denmark] - Canada [canada] - Australia [australia] - Japan [japan] - Ireland [ireland] - Italy [italy] - Spain [spain] - Austria [austria] - Finland [finland] - Luxembourg [luxembourg] - South Korea [south-korea] - New Zealand [new-zealand] - United Arab Emirates [united-arab-emirates] - Singapore [singapore] - Other [other] #### UC-A-015 / origination-country-4 Ask: Fourth transfer origination country (if applicable) Answer: pick one Show only if the answer to corridor-count is 4-5 or more. Requirement type: money - United States [united-states] - United Kingdom [united-kingdom] - Germany [germany] - Netherlands [netherlands] - Switzerland [switzerland] - Belgium [belgium] - France [france] - Sweden [sweden] - Norway [norway] - Denmark [denmark] - Canada [canada] - Australia [australia] - Japan [japan] - Ireland [ireland] - Italy [italy] - Spain [spain] - Austria [austria] - Finland [finland] - Luxembourg [luxembourg] - South Korea [south-korea] - New Zealand [new-zealand] - United Arab Emirates [united-arab-emirates] - Singapore [singapore] - Other [other] #### UC-A-015 / origination-country-5 Ask: Fifth transfer origination country (if applicable) Answer: pick one Show only if the answer to corridor-count is 4-5 or more. Requirement type: money - United States [united-states] - United Kingdom [united-kingdom] - Germany [germany] - Netherlands [netherlands] - Switzerland [switzerland] - Belgium [belgium] - France [france] - Sweden [sweden] - Norway [norway] - Denmark [denmark] - Canada [canada] - Australia [australia] - Japan [japan] - Ireland [ireland] - Italy [italy] - Spain [spain] - Austria [austria] - Finland [finland] - Luxembourg [luxembourg] - South Korea [south-korea] - New Zealand [new-zealand] - United Arab Emirates [united-arab-emirates] - Singapore [singapore] - Other [other] #### UC-A-015 / funding-method Ask: How does your organisation currently fund international transfers or payments? Answer: pick one Requirement type: money - Bank transfer from organisation account [bank-transfer] - Card payment from organisation [card-payment] - Direct stablecoin funding (organisation already holds stablecoins) [direct-stablecoin] - Mixed: bank transfer for most, card for urgent payments [mixed-methods] #### UC-A-015 / stablecoin-approach Ask: What stablecoin approach is preferred for this solution? Answer: pick one Requirement type: money - A regulated digital dollar [usd-pegged] - EUR-pegged stablecoin [eur-pegged] - Multiple stablecoins depending on corridor [multi-stablecoin] - Not sure, need guidance on stablecoin selection [guidance-needed] #### UC-A-015 / grant-duration Ask: What is the typical grant duration for milestone-based disbursements? Answer: pick one Requirement type: money - 1-2 years [short] - 2-3 years [medium] - 3-5 years [long] - Over 5 years [very-long] #### UC-A-015 / milestone-types Ask: What types of milestones trigger disbursements? Answer: pick all that apply Requirement type: money - Output milestones (deliverables, reports) [output] - Outcome milestones (impact metrics) [outcome] - Time-based milestones (quarterly/annual) [time-based] - Expenditure milestones (% of previous tranche spent) [expenditure] - Compliance milestones (audit completed, report submitted) [compliance] #### UC-A-015 / sq-UC-A-015-001 Ask: What evidence and verification process do you currently use before triggering milestone disbursements? Answer: pick one Requirement type: general - Self-reported by recipient [self-reported] - Third-party verified [third-party-verified] - Community attestation [community-attestation] - Sensor or IoT data [sensor-data] - Multi-party sign-off [multi-party-sign-off] #### UC-A-015 / offramp-delivery Ask: How will recipients receive funds at the last mile? Answer: pick one Requirement type: general - Mobile money [mobile-money] - Bank transfer to beneficiary/recipient account [bank-transfer] - Cash via agent network [agent-cash] - Mixed: depends on recipient location and access [mixed] ### UC-A-016: Sub-grantee fund disbursement and tracking Security level: Higher. #### UC-A-016 / corridor-count Ask: How many countries does your organisation send transfer funds from? Answer: pick one Requirement type: scale - Single country [single] - 2–3 countries [2-3] - 4–5 countries [4-5] - More than 5 countries [5-plus] #### UC-A-016 / origination-country-1 Ask: Which country do you most frequently initiate transfers from? Answer: pick one Show only if the answer to corridor-count is single or more. Requirement type: money - United States [united-states] - United Kingdom [united-kingdom] - Germany [germany] - Netherlands [netherlands] - Switzerland [switzerland] - Belgium [belgium] - France [france] - Sweden [sweden] - Norway [norway] - Denmark [denmark] - Canada [canada] - Australia [australia] - Japan [japan] - Ireland [ireland] - Italy [italy] - Spain [spain] - Austria [austria] - Finland [finland] - Luxembourg [luxembourg] - South Korea [south-korea] - New Zealand [new-zealand] - United Arab Emirates [united-arab-emirates] - Singapore [singapore] - Other [other] #### UC-A-016 / origination-country-2 Ask: Second most common transfer origination country (if applicable) Answer: pick one Show only if the answer to corridor-count is 2-3 or more. Requirement type: money - United States [united-states] - United Kingdom [united-kingdom] - Germany [germany] - Netherlands [netherlands] - Switzerland [switzerland] - Belgium [belgium] - France [france] - Sweden [sweden] - Norway [norway] - Denmark [denmark] - Canada [canada] - Australia [australia] - Japan [japan] - Ireland [ireland] - Italy [italy] - Spain [spain] - Austria [austria] - Finland [finland] - Luxembourg [luxembourg] - South Korea [south-korea] - New Zealand [new-zealand] - United Arab Emirates [united-arab-emirates] - Singapore [singapore] - Other [other] #### UC-A-016 / origination-country-3 Ask: Third transfer origination country (if applicable) Answer: pick one Show only if the answer to corridor-count is 2-3 or more. Requirement type: money - United States [united-states] - United Kingdom [united-kingdom] - Germany [germany] - Netherlands [netherlands] - Switzerland [switzerland] - Belgium [belgium] - France [france] - Sweden [sweden] - Norway [norway] - Denmark [denmark] - Canada [canada] - Australia [australia] - Japan [japan] - Ireland [ireland] - Italy [italy] - Spain [spain] - Austria [austria] - Finland [finland] - Luxembourg [luxembourg] - South Korea [south-korea] - New Zealand [new-zealand] - United Arab Emirates [united-arab-emirates] - Singapore [singapore] - Other [other] #### UC-A-016 / origination-country-4 Ask: Fourth transfer origination country (if applicable) Answer: pick one Show only if the answer to corridor-count is 4-5 or more. Requirement type: money - United States [united-states] - United Kingdom [united-kingdom] - Germany [germany] - Netherlands [netherlands] - Switzerland [switzerland] - Belgium [belgium] - France [france] - Sweden [sweden] - Norway [norway] - Denmark [denmark] - Canada [canada] - Australia [australia] - Japan [japan] - Ireland [ireland] - Italy [italy] - Spain [spain] - Austria [austria] - Finland [finland] - Luxembourg [luxembourg] - South Korea [south-korea] - New Zealand [new-zealand] - United Arab Emirates [united-arab-emirates] - Singapore [singapore] - Other [other] #### UC-A-016 / origination-country-5 Ask: Fifth transfer origination country (if applicable) Answer: pick one Show only if the answer to corridor-count is 4-5 or more. Requirement type: money - United States [united-states] - United Kingdom [united-kingdom] - Germany [germany] - Netherlands [netherlands] - Switzerland [switzerland] - Belgium [belgium] - France [france] - Sweden [sweden] - Norway [norway] - Denmark [denmark] - Canada [canada] - Australia [australia] - Japan [japan] - Ireland [ireland] - Italy [italy] - Spain [spain] - Austria [austria] - Finland [finland] - Luxembourg [luxembourg] - South Korea [south-korea] - New Zealand [new-zealand] - United Arab Emirates [united-arab-emirates] - Singapore [singapore] - Other [other] #### UC-A-016 / funding-method Ask: How does your organisation currently fund international transfers or payments? Answer: pick one Requirement type: money - Bank transfer from organisation account [bank-transfer] - Card payment from organisation [card-payment] - Direct stablecoin funding (organisation already holds stablecoins) [direct-stablecoin] - Mixed: bank transfer for most, card for urgent payments [mixed-methods] #### UC-A-016 / stablecoin-approach Ask: What stablecoin approach is preferred for this solution? Answer: pick one Requirement type: money - A regulated digital dollar [usd-pegged] - EUR-pegged stablecoin [eur-pegged] - Multiple stablecoins depending on corridor [multi-stablecoin] - Not sure, need guidance on stablecoin selection [guidance-needed] #### UC-A-016 / subgrantee-capacity Ask: What is the typical financial management capacity of your sub-grantees? Answer: pick one Requirement type: usability - Strong: formal accounting systems and qualified staff [strong] - Moderate: basic systems, some capacity gaps [moderate] - Weak: limited systems, often community-based organisations [weak] - Varies widely across sub-grantee portfolio [varies] #### UC-A-016 / subgrantee-reporting Ask: What reporting do you need from sub-grantees? Answer: pick all that apply Requirement type: audit-trail - Financial reports (expenditure vs budget) [financial] - Activity/output reports [activity] - Supporting documents (receipts, invoices) [supporting-docs] - Beneficiary data [beneficiary-data] - Real-time spend visibility [realtime-spend] #### UC-A-016 / subgrantee-disbursement-model Ask: How are sub-grantee disbursements currently structured? Answer: pick one Requirement type: money - Advance-based: advance then liquidate [advance] - Reimbursement-based: sub-grantee spends first [reimbursement] - Milestone-based: payment on verified deliverables [milestone] - Mix of the above [mixed] #### UC-A-016 / sq-UC-A-016-001 Ask: What financial controls should be imposed on sub-grantees based on their capacity level? Answer: pick one Requirement type: general - Full autonomy [full-autonomy] - Spending limits and thresholds [spending-limits] - Pre-approval required [pre-approval-required] - Co-signatory control [co-signatory] - Escrow with milestone release [escrow-with-milestones] #### UC-A-016 / sq-UC-A-016-003 Ask: How are sub-grantee financial reports currently verified? Answer: pick one Requirement type: legal-checks - Self-certified [self-certified] - Spot audit [spot-audit] - Third-party audit [third-party-audit] - Real-time monitoring [real-time-monitoring] - Milestone-based review [milestone-based-review] #### UC-A-016 / offramp-delivery Ask: How will recipients receive funds at the last mile? Answer: pick one Requirement type: general - Mobile money [mobile-money] - Bank transfer to beneficiary/recipient account [bank-transfer] - Cash via agent network [agent-cash] - Mixed: depends on recipient location and access [mixed] ### UC-A-017: Proof of funds deployment (donor accountability) Security level: Standard. #### UC-A-017 / corridor-count Ask: How many countries does your organisation send transfer funds from? Answer: pick one Requirement type: scale - Single country [single] - 2–3 countries [2-3] - 4–5 countries [4-5] - More than 5 countries [5-plus] #### UC-A-017 / origination-country-1 Ask: Which country do you most frequently initiate transfers from? Answer: pick one Show only if the answer to corridor-count is single or more. Requirement type: money - United States [united-states] - United Kingdom [united-kingdom] - Germany [germany] - Netherlands [netherlands] - Switzerland [switzerland] - Belgium [belgium] - France [france] - Sweden [sweden] - Norway [norway] - Denmark [denmark] - Canada [canada] - Australia [australia] - Japan [japan] - Ireland [ireland] - Italy [italy] - Spain [spain] - Austria [austria] - Finland [finland] - Luxembourg [luxembourg] - South Korea [south-korea] - New Zealand [new-zealand] - United Arab Emirates [united-arab-emirates] - Singapore [singapore] - Other [other] #### UC-A-017 / origination-country-2 Ask: Second most common transfer origination country (if applicable) Answer: pick one Show only if the answer to corridor-count is 2-3 or more. Requirement type: money - United States [united-states] - United Kingdom [united-kingdom] - Germany [germany] - Netherlands [netherlands] - Switzerland [switzerland] - Belgium [belgium] - France [france] - Sweden [sweden] - Norway [norway] - Denmark [denmark] - Canada [canada] - Australia [australia] - Japan [japan] - Ireland [ireland] - Italy [italy] - Spain [spain] - Austria [austria] - Finland [finland] - Luxembourg [luxembourg] - South Korea [south-korea] - New Zealand [new-zealand] - United Arab Emirates [united-arab-emirates] - Singapore [singapore] - Other [other] #### UC-A-017 / origination-country-3 Ask: Third transfer origination country (if applicable) Answer: pick one Show only if the answer to corridor-count is 2-3 or more. Requirement type: money - United States [united-states] - United Kingdom [united-kingdom] - Germany [germany] - Netherlands [netherlands] - Switzerland [switzerland] - Belgium [belgium] - France [france] - Sweden [sweden] - Norway [norway] - Denmark [denmark] - Canada [canada] - Australia [australia] - Japan [japan] - Ireland [ireland] - Italy [italy] - Spain [spain] - Austria [austria] - Finland [finland] - Luxembourg [luxembourg] - South Korea [south-korea] - New Zealand [new-zealand] - United Arab Emirates [united-arab-emirates] - Singapore [singapore] - Other [other] #### UC-A-017 / origination-country-4 Ask: Fourth transfer origination country (if applicable) Answer: pick one Show only if the answer to corridor-count is 4-5 or more. Requirement type: money - United States [united-states] - United Kingdom [united-kingdom] - Germany [germany] - Netherlands [netherlands] - Switzerland [switzerland] - Belgium [belgium] - France [france] - Sweden [sweden] - Norway [norway] - Denmark [denmark] - Canada [canada] - Australia [australia] - Japan [japan] - Ireland [ireland] - Italy [italy] - Spain [spain] - Austria [austria] - Finland [finland] - Luxembourg [luxembourg] - South Korea [south-korea] - New Zealand [new-zealand] - United Arab Emirates [united-arab-emirates] - Singapore [singapore] - Other [other] #### UC-A-017 / origination-country-5 Ask: Fifth transfer origination country (if applicable) Answer: pick one Show only if the answer to corridor-count is 4-5 or more. Requirement type: money - United States [united-states] - United Kingdom [united-kingdom] - Germany [germany] - Netherlands [netherlands] - Switzerland [switzerland] - Belgium [belgium] - France [france] - Sweden [sweden] - Norway [norway] - Denmark [denmark] - Canada [canada] - Australia [australia] - Japan [japan] - Ireland [ireland] - Italy [italy] - Spain [spain] - Austria [austria] - Finland [finland] - Luxembourg [luxembourg] - South Korea [south-korea] - New Zealand [new-zealand] - United Arab Emirates [united-arab-emirates] - Singapore [singapore] - Other [other] #### UC-A-017 / funding-method Ask: How does your organisation currently fund international transfers or payments? Answer: pick one Requirement type: money - Bank transfer from organisation account [bank-transfer] - Card payment from organisation [card-payment] - Direct stablecoin funding (organisation already holds stablecoins) [direct-stablecoin] - Mixed: bank transfer for most, card for urgent payments [mixed-methods] #### UC-A-017 / proof-granularity Ask: At what level of granularity do donors need proof of funds deployment? Answer: pick one Requirement type: audit-trail - Programme level: show funds reached the programme [programme] - Activity level: show funds used for specific activities [activity] - Transaction level: trace every dollar to its end use [transaction] - Beneficiary level: show funds reached specific individuals [beneficiary] #### UC-A-017 / proof-format Ask: What formats do your donors require to verify proof of funds deployment? Answer: pick all that apply Requirement type: audit-trail - Interactive dashboard with drill-down [dashboard] - Periodic PDF/spreadsheet reports [reports] - Digital transaction explorer (verify independently) [explorer] - API access for donor systems [api] - Certificate of deployment [certificate] #### UC-A-017 / proof-timing Ask: When do donors need proof of deployment? Answer: pick one Requirement type: audit-trail - Real-time, as funds are deployed [realtime] - Within days of deployment [days] - At reporting periods (monthly/quarterly) [periodic] - At project/grant close-out [closeout] #### UC-A-017 / sq-UC-A-017-001 Ask: How do you currently handle multi-hop fund flows in deployment proof? Answer: pick one Requirement type: general - End-to-end trace [end-to-end-trace] - Hop-by-hop attestation [hop-by-hop-attestation] - Aggregate outcome only [aggregate-outcome] - Detailed waterfall breakdown [detailed-waterfall] - Sampling-based verification [sampling-based] #### UC-A-017 / sq-UC-A-017-003 Ask: What tamper-evidence mechanism should protect deployment proof data? Answer: pick one Requirement type: general - Digital fingerprint anchoring [blockchain-hash] - Digital signatures [digital-signatures] - Structured proof-of-integrity verification [merkle-tree] - Permanent tamper-proof register [immutable-ledger] - Timestamped snapshots [timestamped-snapshots] ### UC-A-018: Real-time expenditure tracking for donors Security level: Standard. #### UC-A-018 / donor-access-model Ask: How do donors currently access real-time expenditure data from your organisation? Answer: pick one Requirement type: audit-trail - Dedicated donor portal with login [portal] - Shared dashboard (view-only link) [shared-link] - API feed into donor's own systems [api] - Automated email/notification summaries [notifications] #### UC-A-018 / expenditure-dimensions Ask: What expenditure dimensions should donors be able to see? Answer: pick all that apply Requirement type: audit-trail - Budget vs actual spend [budget-vs-actual] - Spend by category (staff, travel, supplies, etc.) [by-category] - Spend by country/location [by-location] - Spend by activity/output [by-activity] - Burn rate and projected end date [burn-rate] - Individual transaction detail [transaction-detail] #### UC-A-018 / data-sensitivity Ask: What expenditure data should be hidden from donors? Answer: pick all that apply Requirement type: legal-checks - Individual staff salaries [salaries] - Beneficiary personal information [beneficiary-pii] - Vendor/supplier identities [vendor-identities] - Security-related expenditures [security] - Nothing: full transparency to donors [nothing-hidden] #### UC-A-018 / sq-UC-A-018-001 Ask: How do you currently handle expenditure data latency for offline field operations? Answer: pick one Requirement type: general - Sync when connected [sync-when-connected] - Daily batch upload [daily-batch-upload] - Manual entry later [manual-entry-later] - Satellite communication [satellite-link] - Store and forward [store-and-forward] #### UC-A-018 / sq-UC-A-018-003 Ask: What expenditure alerting should donors receive? Answer: pick one Requirement type: usability - Threshold-based alerts [threshold-alerts] - Budget burn rate alerts [budget-burn-rate] - Variance from plan [variance-from-plan] - No alerts, pull only [no-alerts-pull-only] - Custom trigger rules [custom-triggers] #### UC-A-018 / accounting-integration Ask: How should this solution integrate with your existing accounting or financial systems? Answer: pick one Requirement type: integration - Direct integration with your existing accounting software [direct-erp] - Export-based: generate reports compatible with our accounting system [export-based] - Standalone ledger with manual reconciliation [standalone] - Not sure, need guidance on accounting integration [guidance-needed] ### UC-A-019: Microfinance and lending to underbanked beneficiaries Security level: Higher. #### UC-A-019 / stablecoin-approach Ask: What stablecoin approach is preferred for this solution? Answer: pick one Requirement type: money - A regulated digital dollar [usd-pegged] - EUR-pegged stablecoin [eur-pegged] - Multiple stablecoins depending on corridor [multi-stablecoin] - Not sure, need guidance on stablecoin selection [guidance-needed] #### UC-A-019 / lending-model Ask: What type of lending/microfinance programme do you operate or plan? Answer: pick one Requirement type: money - Group lending (solidarity groups) [group] - Individual microloans [individual] - Revolving loan fund [revolving] - Asset financing (pay-as-you-go) [asset-financing] - Emergency/disaster recovery loans [emergency] #### UC-A-019 / loan-size Ask: What is the typical loan size? Answer: pick one Requirement type: scale - Under $50 [nano] - $50–$200 [micro] - $200–$1,000 [small] - $1,000–$5,000 [medium] - Over $5,000 [large] #### UC-A-019 / borrower-profile Ask: What is the typical borrower profile? Answer: pick one Requirement type: usability - Rural farmers/agricultural workers [rural-agricultural] - Urban micro-entrepreneurs [urban-micro] - Women's savings/lending groups [womens-groups] - Youth/displaced populations [youth-displaced] - Mixed profiles [mixed] #### UC-A-019 / repayment-collection Ask: How will loan repayments be collected? Answer: pick all that apply Requirement type: money - Mobile money deduction [mobile-money] - Direct wallet deduction (auto-debit) [auto-debit] - Agent-collected cash [agent-cash] - Bank transfer [bank] - Group leader collects from members [group-leader] #### UC-A-019 / credit-assessment Ask: How is creditworthiness currently assessed (or will be)? Answer: pick one Requirement type: legal-checks - Traditional credit bureau check [credit-bureau] - Alternative data (mobile usage, transaction history) [alternative-data] - Group assessment/peer vouching [group-assessment] - Programme participation history [programme-history] - No credit assessment, all eligible participants receive [no-assessment] #### UC-A-019 / sq-UC-A-019-001 Ask: What default management and recovery process do you currently have? Answer: pick one Requirement type: general - Grace period then flag [grace-period-then-flag] - Community mediation [community-mediation] - Write-off threshold [write-off-threshold] - Restructure loan terms [restructure-terms] - Escalation to partner [escalation-to-partner] #### UC-A-019 / compliance-screening Ask: What level of compliance screening is required? Answer: pick one Requirement type: legal-checks - AML/KYC screening with sanctions list checking [aml-kyc] - Basic identity verification only [basic-id] - Full regulatory compliance suite (AML + KYC + ongoing monitoring) [full-suite] - Not sure, need guidance [guidance-needed] #### UC-A-019 / credit-history-need Ask: Does the programme need to build credit histories for populations with no formal banking records? Answer: pick one Requirement type: money - Yes, building credit histories is a primary objective [primary] - Yes, as a secondary benefit of the lending programme [secondary] - No, we have access to existing credit data [no] #### UC-A-019 / credit-signals Ask: What data will be used as credit signals for unbanked borrowers? Answer: pick all that apply Requirement type: money - Digital transaction history (previous loan repayments) [tx-history] - Savings group participation and deposit records [savings-group] - Community attestations (peer vouching, group guarantees) [community] - Mobile money transaction patterns [mobile-money] - Agricultural production records [agricultural] #### UC-A-019 / credit-portability Ask: Does the credit history need to be portable across organisations or geographies? Answer: pick one Requirement type: money - Yes, borrowers should carry their credit history to any participating lender [fully-portable] - Partially, within a network of partner organisations [network-portable] - No, credit history stays within this programme [not-portable] #### UC-A-019 / existing-informal-credit Ask: What existing informal credit or savings mechanisms exist in the community? Answer: pick all that apply Requirement type: money - Village savings and loan associations (VSLAs) [vsla] - Rotating savings and credit associations (ROSCAs/chamas) [rosca] - Informal moneylenders [moneylenders] - Mobile money-based lending [mobile-lending] - No existing mechanisms [none] #### UC-A-019 / beneficiary-choice Ask: How will beneficiaries exercise choice in how they receive and use this service? Answer: pick one Requirement type: usability - Beneficiaries choose between delivery methods (cash, voucher, mobile money, direct) [delivery-choice] - Beneficiaries choose preferred merchants or service points [merchant-choice] - Beneficiaries control their own data sharing preferences [data-choice] - Multiple choice dimensions (delivery + merchant + data) [full-choice] - Limited choice: programme constraints determine delivery [limited] ### UC-A-020: Savings group management and record-keeping Security level: Standard. #### UC-A-020 / group-structure Ask: What type of savings group structure do you support? Answer: pick one Requirement type: money - VSLA (Village Savings and Loan Association) [vsla] - ROSCA (Rotating Savings and Credit Association) [rosca] - ASCA (Accumulating Savings and Credit Association) [asca] - Informal savings groups (custom structure) [informal] - Multiple types across programmes [multiple] #### UC-A-020 / group-size Ask: What is the typical savings group size? Answer: pick one Requirement type: scale - 5-10 members [small] - 10-25 members [medium] - 25-50 members [large] - Varies widely [varies] #### UC-A-020 / group-total-count Ask: How many savings groups does your organisation support in total? Answer: pick one Requirement type: scale - Under 50 groups [small] - 50-200 groups [medium] - 200-1,000 groups [large] - Over 1,000 groups [very-large] #### UC-A-020 / member-device-access Ask: What devices do savings group members typically have? Answer: pick one Requirement type: devices - Smartphones [smartphone] - Feature phones (SMS/USSD) [feature-phone] - Mix: group leader has smartphone, members have feature phones or none [leader-smartphone] - Minimal devices: need agent/facilitator support [minimal] #### UC-A-020 / current-recordkeeping Ask: How are savings group records currently kept? Answer: pick one Requirement type: general - Paper ledger books [paper] - Basic mobile app (non-digital ledger) [mobile-app] - Spreadsheets [spreadsheet] - Memory-based (no formal records) [memory] - Mix of methods [mixed] #### UC-A-020 / sq-UC-A-020-001 Ask: How are savings group governance decisions recorded today? Answer: pick one Requirement type: general - Group vote digital [group-vote-on-chain] - Chairperson approval [chairperson-approval] - multi-approval requirement [multi-sig] - Paper then digitise [paper-then-digitise] - Consensus-based [consensus-based] #### UC-A-020 / beneficiary-choice Ask: How will beneficiaries exercise choice in how they receive and use this service? Answer: pick one Requirement type: usability - Beneficiaries choose between delivery methods (cash, voucher, mobile money, direct) [delivery-choice] - Beneficiaries choose preferred merchants or service points [merchant-choice] - Beneficiaries control their own data sharing preferences [data-choice] - Multiple choice dimensions (delivery + merchant + data) [full-choice] - Limited choice: programme constraints determine delivery [limited] ### UC-A-021: Forecast-based financing (anticipatory action) Security level: Standard. #### UC-A-021 / corridor-count Ask: How many countries does your organisation send transfer funds from? Answer: pick one Requirement type: scale - Single country [single] - 2–3 countries [2-3] - 4–5 countries [4-5] - More than 5 countries [5-plus] #### UC-A-021 / origination-country-1 Ask: Which country do you most frequently initiate transfers from? Answer: pick one Show only if the answer to corridor-count is single or more. Requirement type: money - United States [united-states] - United Kingdom [united-kingdom] - Germany [germany] - Netherlands [netherlands] - Switzerland [switzerland] - Belgium [belgium] - France [france] - Sweden [sweden] - Norway [norway] - Denmark [denmark] - Canada [canada] - Australia [australia] - Japan [japan] - Ireland [ireland] - Italy [italy] - Spain [spain] - Austria [austria] - Finland [finland] - Luxembourg [luxembourg] - South Korea [south-korea] - New Zealand [new-zealand] - United Arab Emirates [united-arab-emirates] - Singapore [singapore] - Other [other] #### UC-A-021 / origination-country-2 Ask: Second most common transfer origination country (if applicable) Answer: pick one Show only if the answer to corridor-count is 2-3 or more. Requirement type: money - United States [united-states] - United Kingdom [united-kingdom] - Germany [germany] - Netherlands [netherlands] - Switzerland [switzerland] - Belgium [belgium] - France [france] - Sweden [sweden] - Norway [norway] - Denmark [denmark] - Canada [canada] - Australia [australia] - Japan [japan] - Ireland [ireland] - Italy [italy] - Spain [spain] - Austria [austria] - Finland [finland] - Luxembourg [luxembourg] - South Korea [south-korea] - New Zealand [new-zealand] - United Arab Emirates [united-arab-emirates] - Singapore [singapore] - Other [other] #### UC-A-021 / origination-country-3 Ask: Third transfer origination country (if applicable) Answer: pick one Show only if the answer to corridor-count is 2-3 or more. Requirement type: money - United States [united-states] - United Kingdom [united-kingdom] - Germany [germany] - Netherlands [netherlands] - Switzerland [switzerland] - Belgium [belgium] - France [france] - Sweden [sweden] - Norway [norway] - Denmark [denmark] - Canada [canada] - Australia [australia] - Japan [japan] - Ireland [ireland] - Italy [italy] - Spain [spain] - Austria [austria] - Finland [finland] - Luxembourg [luxembourg] - South Korea [south-korea] - New Zealand [new-zealand] - United Arab Emirates [united-arab-emirates] - Singapore [singapore] - Other [other] #### UC-A-021 / origination-country-4 Ask: Fourth transfer origination country (if applicable) Answer: pick one Show only if the answer to corridor-count is 4-5 or more. Requirement type: money - United States [united-states] - United Kingdom [united-kingdom] - Germany [germany] - Netherlands [netherlands] - Switzerland [switzerland] - Belgium [belgium] - France [france] - Sweden [sweden] - Norway [norway] - Denmark [denmark] - Canada [canada] - Australia [australia] - Japan [japan] - Ireland [ireland] - Italy [italy] - Spain [spain] - Austria [austria] - Finland [finland] - Luxembourg [luxembourg] - South Korea [south-korea] - New Zealand [new-zealand] - United Arab Emirates [united-arab-emirates] - Singapore [singapore] - Other [other] #### UC-A-021 / origination-country-5 Ask: Fifth transfer origination country (if applicable) Answer: pick one Show only if the answer to corridor-count is 4-5 or more. Requirement type: money - United States [united-states] - United Kingdom [united-kingdom] - Germany [germany] - Netherlands [netherlands] - Switzerland [switzerland] - Belgium [belgium] - France [france] - Sweden [sweden] - Norway [norway] - Denmark [denmark] - Canada [canada] - Australia [australia] - Japan [japan] - Ireland [ireland] - Italy [italy] - Spain [spain] - Austria [austria] - Finland [finland] - Luxembourg [luxembourg] - South Korea [south-korea] - New Zealand [new-zealand] - United Arab Emirates [united-arab-emirates] - Singapore [singapore] - Other [other] #### UC-A-021 / funding-method Ask: How does your organisation currently fund international transfers or payments? Answer: pick one Requirement type: money - Bank transfer from organisation account [bank-transfer] - Card payment from organisation [card-payment] - Direct stablecoin funding (organisation already holds stablecoins) [direct-stablecoin] - Mixed: bank transfer for most, card for urgent payments [mixed-methods] #### UC-A-021 / stablecoin-approach Ask: What stablecoin approach is preferred for this solution? Answer: pick one Requirement type: money - A regulated digital dollar [usd-pegged] - EUR-pegged stablecoin [eur-pegged] - Multiple stablecoins depending on corridor [multi-stablecoin] - Not sure, need guidance on stablecoin selection [guidance-needed] #### UC-A-021 / trigger-data-source Ask: What data sources should trigger anticipatory financing? Answer: pick all that apply Requirement type: money - Weather/climate forecasts (drought, flood, cyclone) [weather] - Food security indicators (IPC/CH classifications) [food-security] - Epidemiological data (disease outbreak) [epidemiological] - Conflict/displacement early warnings [conflict] - Market price data (commodity prices) [market-prices] - Seismic/volcanic activity [seismic] #### UC-A-021 / pre-positioning Ask: How are funds currently pre-positioned for anticipatory action? Answer: pick one Requirement type: money - Pre-funded stablecoin pool earmarked for triggers [pre-funded] - Rapid mobilisation from treasury on trigger [rapid-mobilise] - Donor pre-commitment with draw-down on trigger [donor-commitment] - Insurance-like pool with premium contributions [insurance-pool] #### UC-A-021 / disbursement-target Ask: Who receives the anticipatory financing when triggered? Answer: pick one Requirement type: money - Pre-registered beneficiaries in at-risk areas [pre-registered] - Community organisations/local partners [community-orgs] - Government disaster agencies [government] - Field offices for local response [field-offices] - Mix depending on trigger type [mixed] #### UC-A-021 / sq-UC-A-021-001 Ask: How do you currently handle false-trigger events when funds have been released? Answer: pick one Requirement type: general - Accept as programme cost [accept-as-cost] - Partial recovery [partial-recovery] - Insurance-backed recovery [insurance-backed] - Adjust future thresholds [adjust-future-thresholds] - Community redistribution [community-redistribution] #### UC-A-021 / beneficiary-choice Ask: How will beneficiaries exercise choice in how they receive and use this service? Answer: pick one Requirement type: usability - Beneficiaries choose between delivery methods (cash, voucher, mobile money, direct) [delivery-choice] - Beneficiaries choose preferred merchants or service points [merchant-choice] - Beneficiaries control their own data sharing preferences [data-choice] - Multiple choice dimensions (delivery + merchant + data) [full-choice] - Limited choice: programme constraints determine delivery [limited] ### UC-A-022: Parametric insurance for beneficiaries Security level: Standard. #### UC-A-022 / stablecoin-approach Ask: What stablecoin approach is preferred for this solution? Answer: pick one Requirement type: money - A regulated digital dollar [usd-pegged] - EUR-pegged stablecoin [eur-pegged] - Multiple stablecoins depending on corridor [multi-stablecoin] - Not sure, need guidance on stablecoin selection [guidance-needed] #### UC-A-022 / insured-risk Ask: What risk are beneficiaries being insured against? Answer: pick all that apply Requirement type: money - Drought (rainfall deficit) [drought] - Flood (excess rainfall/river level) [flood] - Cyclone/hurricane/typhoon [cyclone] - Crop failure (yield-based) [crop-failure] - Livestock mortality [livestock] - Earthquake [earthquake] #### UC-A-022 / premium-funding Ask: How are insurance premiums funded? Answer: pick one Requirement type: money - Fully subsidised by donor/programme [fully-subsidised] - Partially subsidised, beneficiary pays a portion [partially-subsidised] - Fully paid by beneficiaries [beneficiary-paid] - Government co-funded [government-cofunded] #### UC-A-022 / payout-speed Ask: How quickly should payouts reach beneficiaries after a trigger event? Answer: pick one Requirement type: money - Within hours of trigger [hours] - Within 1-3 days [days] - Within a week [week] - Within a month [month] #### UC-A-022 / beneficiary-count-insurance Ask: How many beneficiaries would be covered by the insurance programme? Answer: pick one Requirement type: scale - Under 1,000 [small] - 1,000–10,000 [medium] - 10,000–100,000 [large] - Over 100,000 [very-large] #### UC-A-022 / sq-UC-A-022-001 Ask: What oracle data source should determine trigger events? Answer: pick one Requirement type: general - Government weather agency [government-weather-agency] - Satellite imagery [satellite-imagery] - IoT sensors [iot-sensors] - Index provider [index-provider] - Multi-source consensus [multi-source-consensus] #### UC-A-022 / beneficiary-choice Ask: How will beneficiaries exercise choice in how they receive and use this service? Answer: pick one Requirement type: usability - Beneficiaries choose between delivery methods (cash, voucher, mobile money, direct) [delivery-choice] - Beneficiaries choose preferred merchants or service points [merchant-choice] - Beneficiaries control their own data sharing preferences [data-choice] - Multiple choice dimensions (delivery + merchant + data) [full-choice] - Limited choice: programme constraints determine delivery [limited] ### UC-A-023: Community currencies and complementary currency systems Security level: Standard. #### UC-A-023 / community-size Ask: How large is the target community for the currency? Answer: pick one Requirement type: scale - Small (under 500 households) [small] - Medium (500–2,000 households) [medium] - Large (2,000–10,000 households) [large] - Very large (10,000+ households) [very-large] #### UC-A-023 / token-backing-model Ask: How will the community currency be backed? Answer: pick one Requirement type: general - Backed by fiat reserve (1:1 or fractional) [fiat-backed] - Backed by goods/services commitments from merchants [goods-backed] - Mutual credit (no external backing: community trust) [mutual-credit] - Hybrid (partial fiat backing + community commitment) [hybrid] #### UC-A-023 / token-expiry-demurrage Ask: Should the currency have built-in incentives for circulation (e.g., expiry or demurrage)? Answer: pick one Requirement type: general - Yes, tokens expire after a set period to encourage spending [expiry] - Yes, demurrage (tokens lose value over time) to discourage hoarding [demurrage] - No, tokens retain value indefinitely [no-decay] - Unsure, need guidance [unsure] #### UC-A-023 / governance-model Ask: Who will govern the currency (issuance rules, redemption, disputes)? Answer: pick one Requirement type: governance - Community committee or council [community] - NGO-managed with community input [ngo-led] - Shared governance (NGO + community + local authority) [shared] - Fully automated rules (code-based governance) [automated] #### UC-A-023 / merchant-network-size Ask: How many local merchants or service providers would accept the currency? Answer: pick one Requirement type: scale - Under 20 merchants [small] - 20–100 merchants [medium] - 100–500 merchants [large] - 500+ merchants [very-large] #### UC-A-023 / redemption-model Ask: Can community currency be exchanged back to fiat or other assets? Answer: pick one Requirement type: usability - Yes, open redemption to fiat at any time [open] - Yes, but with conditions (minimum period, fees, limits) [conditional] - No, currency circulates only within the community economy [closed] - Partial, NGO provides periodic buyback windows [periodic] #### UC-A-023 / regulatory-environment Ask: What is the regulatory environment for alternative currencies in the target country? Answer: pick one Requirement type: legal-checks - Supportive: government has enabled community currencies or e-money [supportive] - Neutral: no specific regulation, not prohibited [neutral] - Restrictive: regulations may limit token-based currencies [restrictive] - Unknown, the regulatory position needs assessment [unknown] #### UC-A-023 / beneficiary-choice Ask: How will beneficiaries exercise choice in how they receive and use this service? Answer: pick one Requirement type: usability - Beneficiaries choose between delivery methods (cash, voucher, mobile money, direct) [delivery-choice] - Beneficiaries choose preferred merchants or service points [merchant-choice] - Beneficiaries control their own data sharing preferences [data-choice] - Multiple choice dimensions (delivery + merchant + data) [full-choice] - Limited choice: programme constraints determine delivery [limited] ### UC-A-024: Currency hedging and stability (stablecoin alternatives) Security level: Standard. #### UC-A-024 / stablecoin-mix Ask: What stablecoin mix should the treasury hold? Answer: pick one Requirement type: money - A single regulated stablecoin [single-regulated] - Multiple regulated stablecoins for issuer diversification [multi-regulated] - A mix of regulated and over-collateralised decentralised stablecoins [mixed] - Jurisdiction-specific regulated stablecoins (e.g. a euro stablecoin in EU corridors) [jurisdictional] #### UC-A-024 / custody-model Ask: How should the stablecoin treasury be held? Answer: pick one Requirement type: audit-trail - Third-party regulated custodian (exchange / qualified custodian) [custodian] - Self-custody with multi-sig wallet [self-multisig] - Hybrid: operational self-custody, reserve in custodian [hybrid] - Smart-contract vault with role-based access [sc-vault] #### UC-A-024 / rebalancing-policy Ask: How should allocation and rebalancing between stablecoins and fiat be governed? Answer: pick one Requirement type: general - Manual: treasury makes allocation decisions ad hoc [manual] - Policy-driven manual: documented policy, manual execution [policy-manual] - Rule-based semi-automated: thresholds trigger human review [rule-semi-auto] - Fully automated via smart contract [smart-contract] #### UC-A-024 / on-off-ramp-strategy Ask: How should the treasury convert between stablecoins and local currency in each operating corridor? Answer: pick one Requirement type: money - HQ-only ramping (convert in banking jurisdiction, move fiat out) [hq-only] - In-country ramping via licensed local exchanges [in-country-exchange] - Direct stablecoin-to-mobile-money corridors [mobile-money] - Mixed per corridor based on available infrastructure [mixed] #### UC-A-024 / donor-acceptance-model Ask: How does donor acceptance shape the treasury model? Answer: pick one Requirement type: general - No stablecoin treasury, donor restrictions prohibit it [prohibited] - Stablecoin treasury disclosed and accepted in donor agreements [disclosed-accepted] - Specific donors fund stablecoin pilots; others remain fiat-only [segmented] - Donor-agnostic: treasury policy independent of donor preferences [agnostic] ### UC-A-025: Insurance for field staff and organisational assets Security level: Standard. #### UC-A-025 / coverage-scope Ask: What risk class does the policy need to cover? Answer: pick one Requirement type: general - Field staff only (travel, medevac, accident, K&R) [staff] - Organisational assets only (vehicles, equipment, premises) [assets] - Both - separate policies per risk class [both-separate] - Integrated programme - staff and assets in one mutual / pool [both-integrated] #### UC-A-025 / underwriting-model Ask: Who underwrites the risk? Answer: pick one Requirement type: general - Traditional broker-mediated commercial policy [broker] - Self-insurance with internal reserve [self-insured] - NGO-mutual / peer pool (cross-NGO risk sharing) [mutual] - Parametric on-chain policy with external capital providers [parametric-external] #### UC-A-025 / trigger-mechanism Ask: How is a claim triggered? Answer: pick one Requirement type: general - Indemnity - adjuster assesses loss after the fact [indemnity] - Parametric - objective data trigger (weather, flight data, security alert) [parametric] - Hybrid - parametric fast-pay with indemnity top-up [hybrid] - Attestation-based - trusted third-party attestation triggers payout [attestation] #### UC-A-025 / payout-currency-model Ask: How should payouts settle? Answer: pick one Requirement type: money - Local fiat via bank rail [local-fiat] - USD via traditional wire [usd-wire] - Stablecoin direct to wallet [stablecoin] - Multi-rail - stablecoin with fiat off-ramp options [multi-rail] #### UC-A-025 / evidence-integrity-model Ask: How is claim evidence proved unaltered? Answer: pick one Requirement type: audit-trail - Document upload with org signatures [docs] - Hashed evidence anchored on-chain [anchored] - Verifiable credentials from authorised attestors (medics, security firms) [vc-attestors] - Oracle-only - no per-claim evidence required [oracle-only] ### UC-A-026: Zakat and interest-free loan (qard hasan) distribution transparency Security level: Standard. #### UC-A-026 / instrument-mix Ask: Which kinds of giving does this cover? Answer: pick all that apply Requirement type: general - Zakat (obligatory alms) [zakat] - Qard hasan (interest-free loans) [qard-hasan] - Waqf (endowment) [waqf] - Sadaqah (voluntary alms) [sadaqah] - Sukuk (Islamic bonds) [sukuk] #### UC-A-026 / annual-flow-scale Ask: How much moves through the programme each year? Answer: pick one Requirement type: scale - Under USD 100,000 annually [under-100k] - USD 100,000 to 1 million [100k-1m] - USD 1 million to 10 million [1m-10m] - Over USD 10 million [over-10m] #### UC-A-026 / asnaf-categories-addressed Ask: Which groups of recipients does the programme serve? Answer: pick all that apply Requirement type: general - The poor (al-fuqara) [fuqara] - The destitute (al-masakin) [masakin] - Zakat administrators (al-amilin alayha) [amilin] - Reverts (al-muallafa qulubuhum) [muallafa] - Captives (fi al-riqab) [riqab] - The indebted (al-gharimin) [gharimin] - In the path of God (fi sabilillah) [fi-sabilillah] - Travellers (ibn al-sabil) [ibn-sabil] #### UC-A-026 / eligibility-attestor Ask: Who confirms that a recipient is eligible? Answer: pick one Requirement type: governance - Local religious scholar / imam [local-scholar] - Community vetting committee [vetting-committee] - Established zakat authority (BAZNAS, MUIS, etc.) [zakat-authority] - CSO internal staff (least preferred) [cso-internal] - Multiple attestors with quorum requirement [multiple] #### UC-A-026 / recipient-pseudonymity Ask: How much of a recipient's identity may donors see? Answer: pick one Requirement type: privacy - Strict pseudonymity: no recipient identity exposed to donors [strict] - Aggregated reporting only [aggregated] - Identity visible to attestor and shariah board only [authority-only] - Full disclosure to donor [full-disclosure] #### UC-A-026 / disbursement-mechanism Ask: How will recipients be paid or supported? Answer: pick all that apply Requirement type: money - Direct cash transfer [direct-cash] - Voucher to specific vendors [voucher] - In-kind goods [in-kind] - Repayable loan (qard hasan) [loan-repayable] - Microenterprise grant (zakat-funded) [microenterprise-grant] #### UC-A-026 / shariah-supervision-model Ask: Who oversees the programme under Islamic law? Answer: pick one Requirement type: governance - Internal shariah supervisory board [internal-board] - External shariah scholars retained [external-scholars] - National shariah supervisory body [national-body] - No shariah supervision, programme-killing veto [none] #### UC-A-026 / right-to-be-forgotten Ask: How long are recipient records kept? Answer: pick one Requirement type: privacy - On by default: eligibility records expire [default-on] - On request from recipient [on-request] - Anonymisation after distribution complete [anonymisation] - Perpetual records (high concern in this context) [perpetual] #### UC-A-026 / blended-conventional-funding Ask: How much conventional funding is mixed in? Answer: pick one Requirement type: money - Pure Islamic finance [none] - Complementary conventional funding [complementary] - Majority conventional with Islamic component [majority-conventional] - Blended approximately equally [blended-equally] ### UC-B-024: Beneficiary registration (refugees, stateless, undocumented) Security level: Critical. #### UC-B-024 / identity-doc-status Ask: What is the current identity documentation status of the target beneficiary population? Answer: pick one Requirement type: credentials - Most have some form of government-issued ID [some-id] - Majority have expired or damaged ID documents [expired-id] - Most are undocumented or stateless, no formal ID [undocumented] - Mixed: some documented, many not [mixed-status] #### UC-B-024 / registration-scale Ask: What is the approximate scale of beneficiary registration needed? Answer: pick one Requirement type: scale - Under 5,000 beneficiaries [small] - 5,000–50,000 beneficiaries [medium] - 50,000–500,000 beneficiaries [large] - Over 500,000 beneficiaries [massive] #### UC-B-024 / privacy-requirements Ask: What level of privacy protection is required for beneficiary identity data? Answer: pick one Requirement type: privacy - Standard data protection (encrypted storage, access controls) [standard] - Enhanced privacy (zero-knowledge proofs for verification) [zkp] - Maximum privacy (no central data store, beneficiary-held only) [self-sovereign] - Regulatory-driven (GDPR, national data protection laws apply) [regulatory] #### UC-B-024 / credential-portability Ask: Do beneficiary credentials need to be portable across organisations or borders? Answer: pick one Requirement type: integration - Single-organisation use only [single-org] - Shared across implementing partners in same programme [multi-partner] - Portable across organisations and programmes [cross-org] - Cross-border portability needed [cross-border] #### UC-B-024 / holder-device Ask: What devices do beneficiaries have access to for holding their identity credentials? Answer: pick one Requirement type: devices - Smartphones with reliable connectivity [smartphone] - Feature phones (SMS/USSD only) [feature-phone] - No personal device, rely on printed/card credentials [no-device] - Mixed: some smartphones, many without devices [mixed] #### UC-B-024 / deduplication-approach Ask: What deduplication rate is acceptable for duplicate registrations across sites and programmes? Answer: pick one Requirement type: credentials - Biometric deduplication (fingerprint/iris matching) [biometric-dedup] - Demographic matching (name, DOB, location) [demographic] - Privacy-preserving deduplication (hashed matching) [privacy-preserving] - No deduplication needed, single-site registration [none] #### UC-B-024 / consent-model Ask: What consent model is required for beneficiary data collection and sharing? Answer: pick one Requirement type: privacy - Opt-in consent at registration with blanket programme use [opt-in-blanket] - Granular consent: beneficiaries choose what data to share with whom [granular] - Guardian/proxy consent (for children or incapacitated individuals) [guardian] - Community consent model (collective consent for group registration) [community] #### UC-B-024 / credential-types Ask: What types of identity documents do your beneficiaries typically have? Answer: pick one Requirement type: credentials - Basic identity (name, photo, biometric anchor) [basic-id] - Identity + programme enrolment proof [id-plus-enrolment] - Full verifiable identity with multiple attributes [full-vc] - Foundational identity (government-grade, civil registry pathway) [foundational] #### UC-B-024 / verification-frequency Ask: How often does verification need to happen? Answer: pick one Requirement type: privacy - One-time registration, rarely re-verified [one-time] - Periodic verification (monthly/quarterly distributions) [periodic] - Frequent verification (every service interaction) [frequent] - Continuous verification (real-time access control) [continuous] #### UC-B-024 / government-integration Ask: Does your system need to connect to government identity or registry systems? Answer: pick one Requirement type: integration - No government integration needed, standalone humanitarian system [standalone] - One-way feed to government registry (e.g., birth registration) [one-way] - Two-way integration with national identity systems [two-way] - Government-led system with humanitarian layer [gov-led] #### UC-B-024 / reporting-needs Ask: What identity programme reporting is needed? Answer: pick one Requirement type: audit-trail - Basic registration statistics (totals, demographics) [basic-stats] - Donor reporting with anonymised identity metrics [donor-reporting] - Full audit trail of all identity operations [full-audit] - Regulatory compliance reporting (data protection authority) [regulatory] #### UC-B-024 / sq-UC-B-024-001 Ask: What percentage of beneficiary registrations typically happen offline? Answer: pick one Requirement type: general - Local device storage, sync later [local-device-storage-sync-later] - Paper backup, digitise later [paper-backup-digitise] - Mesh network synchronisation [mesh-network] - Satellite upload [satellite-upload] - Pre-cached registry [pre-cached-registry] #### UC-B-024 / holder-access-method Ask: How will individuals access and present their credentials or identity documents? Answer: pick one Requirement type: credentials - Mobile wallet app (smartphone required) [mobile-wallet] - Physical smart card with NFC or QR code [smart-card] - SMS/USSD-based access (feature phone compatible) [sms-ussd] - Hybrid: mobile app for those with smartphones, card for others [hybrid] #### UC-B-024 / beneficiary-choice Ask: How will beneficiaries exercise choice in how they receive and use this service? Answer: pick one Requirement type: usability - Beneficiaries choose between delivery methods (cash, voucher, mobile money, direct) [delivery-choice] - Beneficiaries choose preferred merchants or service points [merchant-choice] - Beneficiaries control their own data sharing preferences [data-choice] - Multiple choice dimensions (delivery + merchant + data) [full-choice] - Limited choice: programme constraints determine delivery [limited] ### UC-B-025: Birth registration for children born in displacement Security level: Critical. #### UC-B-025 / birth-registration-context Ask: What is the legal recognition environment for birth registration in your operating countries? Answer: pick one Requirement type: credentials - Government civil registry is functional and accessible [functional-registry] - Civil registry exists but is inaccessible to displaced populations [inaccessible-registry] - Civil registry is non-functional or destroyed (conflict/disaster) [non-functional] - No formal civil registry system exists [no-registry] #### UC-B-025 / birth-capture-method Ask: How are birth events currently captured and documented in your operating environment? Answer: pick one Requirement type: credentials - Health facility-based registration (births in clinics/hospitals) [facility-based] - Community health worker reporting (home births) [community-hw] - Mobile registration teams visiting communities [mobile-teams] - Mixed: facility + community + mobile registration [mixed] #### UC-B-025 / infant-biometric Ask: What identification method will be used for newborns? Answer: pick one Requirement type: credentials - Parental biometric link (identity anchored to mother/father) [parental-link] - Infant footprint capture [footprint] - Photo-based identity with parental attestation [photo-attestation] - No biometric, document-based registration only [document-only] #### UC-B-025 / parental-identity Ask: What is the expected parental identity documentation situation? Answer: pick one Requirement type: credentials - Most parents have verified identity documents [verified-parents] - Parents have humanitarian registration but no government ID [humanitarian-id] - Many parents are undocumented themselves [undocumented-parents] - Mixed: some documented, some not [mixed] #### UC-B-025 / birth-cert-format Ask: What birth certificate format does your operating environment require? Answer: pick one Requirement type: integration - Digital verifiable credential only [digital-only] - Digital credential + printed certificate [digital-print] - Printed certificate with QR verification code [print-qr] - Government-format certificate (matching national template) [gov-format] #### UC-B-025 / birth-privacy Ask: What privacy protections are needed for birth records? Answer: pick one Requirement type: privacy - Standard access control (role-based, encrypted) [standard] - Enhanced child protection (restricted access, anonymised) [child-protection] - Maximum privacy (parental consent for every access) [max-privacy] #### UC-B-025 / vital-stats-integration Ask: Does birth registration need to feed into national vital statistics? Answer: pick one Requirement type: integration - Yes, direct integration with national vital statistics system [direct-integration] - Yes, but through an intermediary (UNICEF, WHO) [intermediary] - Not currently, design for future integration [future-ready] - No, standalone humanitarian record only [standalone] #### UC-B-025 / birth-connectivity Ask: What connectivity is available at birth registration points? Answer: pick one Requirement type: offline - Reliable internet at all registration points [connected] - Intermittent: needs offline capability with sync [intermittent] - Fully offline: remote areas with no connectivity [offline] - Mixed: facilities connected, community sites offline [mixed] #### UC-B-025 / birth-reporting Ask: What reporting is needed for the birth registration programme? Answer: pick one Requirement type: audit-trail - Basic counts and demographics for programme reporting [basic] - Detailed analytics with gender, location, age disaggregation [detailed] - Donor accountability reporting with anonymised data [donor] - Full audit trail for regulatory compliance [full-audit] #### UC-B-025 / beneficiary-choice Ask: How will beneficiaries exercise choice in how they receive and use this service? Answer: pick one Requirement type: usability - Beneficiaries choose between delivery methods (cash, voucher, mobile money, direct) [delivery-choice] - Beneficiaries choose preferred merchants or service points [merchant-choice] - Beneficiaries control their own data sharing preferences [data-choice] - Multiple choice dimensions (delivery + merchant + data) [full-choice] - Limited choice: programme constraints determine delivery [limited] ### UC-B-026: Death registration and inheritance documentation Security level: Higher. #### UC-B-026 / death-registration-context Ask: What is the context for death registration in your operating environment? Answer: pick one Requirement type: credentials - Conflict-related deaths requiring documentation for accountability [conflict] - Natural disaster mortality documentation [disaster] - Routine deaths in displacement settings needing formal registration [routine-displacement] - Epidemic/pandemic mortality tracking [epidemic] #### UC-B-026 / inheritance-documentation Ask: Is inheritance and property rights documentation needed alongside death registration? Answer: pick one Requirement type: credentials - Yes, formal inheritance documentation is critical [formal-inheritance] - Yes, but informal/customary inheritance practices apply [customary] - Inheritance tracking for programme asset transfer only [programme-assets] - No inheritance documentation needed [no-inheritance] #### UC-B-026 / death-verification Ask: How are death events currently verified and documented? Answer: pick one Requirement type: privacy - Medical certification (health facility or medical examiner) [medical] - Community witness attestation with verification [community-witness] - Field staff documentation with evidence capture [field-staff] - Multiple methods depending on context [multi-method] #### UC-B-026 / death-privacy Ask: What privacy and cultural sensitivity considerations apply to death records? Answer: pick one Requirement type: privacy - Standard privacy with cultural sensitivity training [standard-cultural] - High sensitivity: restricted access, anonymised reporting [high-sensitivity] - Conflict context: security considerations for data holders [security-sensitive] #### UC-B-026 / death-reporting Ask: What death registration reporting is required? Answer: pick one Requirement type: audit-trail - Internal programme reporting only [internal] - National vital statistics contribution [vital-stats] - International humanitarian mortality reporting [international] - Legal/accountability reporting (courts, commissions) [legal] #### UC-B-026 / death-connectivity Ask: What connectivity is available at death registration points? Answer: pick one Requirement type: offline - Reliable internet connectivity [connected] - Intermittent connectivity with offline capability needed [intermittent] - Fully offline: remote or conflict areas [offline] #### UC-B-026 / consent-management-approach Ask: How do you currently manage consent for beneficiary data collection and sharing? Answer: pick one Requirement type: privacy - Granular consent: individuals control each data element shared [granular] - Tiered consent: pre-defined levels (basic, standard, full) [tiered] - Blanket consent with opt-out for specific data categories [blanket-optout] - Guardian/proxy consent for vulnerable populations [guardian-proxy] #### UC-B-026 / beneficiary-choice Ask: How will beneficiaries exercise choice in how they receive and use this service? Answer: pick one Requirement type: usability - Beneficiaries choose between delivery methods (cash, voucher, mobile money, direct) [delivery-choice] - Beneficiaries choose preferred merchants or service points [merchant-choice] - Beneficiaries control their own data sharing preferences [data-choice] - Multiple choice dimensions (delivery + merchant + data) [full-choice] - Limited choice: programme constraints determine delivery [limited] ### UC-B-027: Marriage and family status documentation Security level: Higher. #### UC-B-027 / marriage-type Ask: What types of marriages/unions need to be documented? Answer: pick one Requirement type: credentials - Civil/legal marriages requiring formal registration [civil] - Religious marriages needing documentation for legal purposes [religious] - Customary/traditional marriages and unions [customary] - Multiple types: civil, religious, and customary [multiple] #### UC-B-027 / family-composition Ask: What family structures need to be documented? Answer: pick one Requirement type: credentials - Nuclear families (couple + children) [nuclear] - Extended family relationships (including dependents) [extended] - Complex family structures (polygamous, blended, guardian) [complex] - All structures, highly diverse family compositions [all] #### UC-B-027 / family-credential-use Ask: How will family status credentials be used? Answer: pick one Requirement type: privacy - Programme enrolment (family-based targeting) [programme-enrolment] - Legal documentation (marriage certificates, family books) [legal-docs] - Inheritance and property rights claims [inheritance] - Cross-border family reunification [reunification] #### UC-B-027 / family-privacy Ask: What privacy considerations apply to family status data? Answer: pick one Requirement type: privacy - Standard privacy: encrypted with role-based access [standard] - High sensitivity: GBV risk requires restricted access [gbv-sensitive] - Cultural sensitivity: community norms around family disclosure [cultural] #### UC-B-027 / family-connectivity Ask: What connectivity is available for family registration activities? Answer: pick one Requirement type: offline - Reliable internet connectivity [connected] - Intermittent connectivity [intermittent] - Fully offline: remote areas [offline] #### UC-B-027 / family-reporting Ask: What reporting is needed for family status documentation? Answer: pick one Requirement type: audit-trail - Internal programme reporting [internal] - Vital statistics contribution [vital-stats] - Protection case reporting [protection] #### UC-B-027 / consent-management-approach Ask: How do you currently manage consent for beneficiary data collection and sharing? Answer: pick one Requirement type: privacy - Granular consent: individuals control each data element shared [granular] - Tiered consent: pre-defined levels (basic, standard, full) [tiered] - Blanket consent with opt-out for specific data categories [blanket-optout] - Guardian/proxy consent for vulnerable populations [guardian-proxy] #### UC-B-027 / beneficiary-choice Ask: How will beneficiaries exercise choice in how they receive and use this service? Answer: pick one Requirement type: usability - Beneficiaries choose between delivery methods (cash, voucher, mobile money, direct) [delivery-choice] - Beneficiaries choose preferred merchants or service points [merchant-choice] - Beneficiaries control their own data sharing preferences [data-choice] - Multiple choice dimensions (delivery + merchant + data) [full-choice] - Limited choice: programme constraints determine delivery [limited] ### UC-B-028: Portable service history across borders and organisations Security level: Higher. #### UC-B-028 / service-types Ask: What types of services need to be tracked in the portable history? Answer: pick one Requirement type: credentials - Health services (vaccinations, treatments, referrals) [health] - Education services (enrolment, completion, grades) [education] - Cash/voucher assistance (distributions received) [cash-assistance] - Multiple service types across sectors [multi-sector] #### UC-B-028 / portability-scope Ask: How widely do credentials need to be recognised? Answer: pick one Requirement type: integration - Within a single country across multiple organisations [national] - Across 2-3 neighbouring countries (regional) [regional] - Global portability for mobile populations [global] #### UC-B-028 / holder-control Ask: How much control should beneficiaries have over their service history? Answer: pick one Requirement type: usability - Full user-controlled portable control: beneficiary decides what to share [full-control] - Shared control: beneficiary consents, organisation manages [shared-control] - Organisation-managed with beneficiary visibility [org-managed] #### UC-B-028 / history-verification Ask: How is service history currently verified when presented? Answer: pick one Requirement type: privacy - Secure digital verification against issuer (real-time check) [cryptographic-real-time] - Secure digital verification with cached trust (offline capable) [cryptographic-cached] - Issuer contact for high-value verifications only [issuer-contact] #### UC-B-028 / history-device Ask: What devices will beneficiaries use to carry and present their service history? Answer: pick one Requirement type: devices - Smartphone wallet application [smartphone] - Physical card with QR/NFC (no smartphone needed) [physical-card] - Cloud-based: accessible from any device [cloud-based] - Mixed: smartphone + card fallback [mixed] #### UC-B-028 / history-privacy Ask: What selective disclosure capabilities do you currently have? Answer: pick one Requirement type: privacy - Full history shared: no selective disclosure needed [full-share] - Sector-level selection (share health but not cash records) [sector-level] - Attribute-level selection (share vaccination status without details) [attribute-level] - Zero-knowledge proofs (prove eligibility without revealing data) [zkp] #### UC-B-028 / history-connectivity Ask: What connectivity is available where credentials will be presented? Answer: pick one Requirement type: offline - Reliable internet at verification points [connected] - Intermittent: offline verification needed sometimes [intermittent] - Fully offline verification required [offline] #### UC-B-028 / history-reporting Ask: What service history analytics do you currently have? Answer: pick one Requirement type: audit-trail - Basic usage statistics (presentations, verifications) [basic-stats] - Service coverage analytics (gaps, duplications) [coverage] - Cross-organisation coordination insights [coordination] #### UC-B-028 / holder-access-method Ask: How will individuals access and present their credentials or identity documents? Answer: pick one Requirement type: credentials - Mobile wallet app (smartphone required) [mobile-wallet] - Physical smart card with NFC or QR code [smart-card] - SMS/USSD-based access (feature phone compatible) [sms-ussd] - Hybrid: mobile app for those with smartphones, card for others [hybrid] #### UC-B-028 / beneficiary-choice Ask: How will beneficiaries exercise choice in how they receive and use this service? Answer: pick one Requirement type: usability - Beneficiaries choose between delivery methods (cash, voucher, mobile money, direct) [delivery-choice] - Beneficiaries choose preferred merchants or service points [merchant-choice] - Beneficiaries control their own data sharing preferences [data-choice] - Multiple choice dimensions (delivery + merchant + data) [full-choice] - Limited choice: programme constraints determine delivery [limited] ### UC-B-029: Staff credential verification across jurisdictions Security level: Standard. #### UC-B-029 / credential-types-staff Ask: What types of staff credentials need to be verified? Answer: pick one Requirement type: credentials - Professional qualifications (degrees, certifications) [professional] - Security clearances and background checks [security] - Safeguarding training and compliance [safeguarding] - All of the above, comprehensive credential verification [comprehensive] #### UC-B-029 / jurisdiction-count Ask: How many jurisdictions does staff credential verification need to span? Answer: pick one Requirement type: residency - Single country: domestic operations [single] - 2-5 countries: regional operations [regional] - 5-20 countries: multi-regional operations [multi-regional] - 20+ countries: global operations [global] #### UC-B-029 / staff-verification-frequency Ask: How frequently are staff credentials verified? Answer: pick one Requirement type: privacy - At hiring/onboarding only [onboarding] - Annual re-verification [annual] - Continuous monitoring for expiry/revocation [continuous] #### UC-B-029 / staff-holder-interface Ask: How will staff interact with their credential wallet? Answer: pick one Requirement type: usability - Mobile app for staff credential management [mobile-app] - Web portal integrated with HR system [web-hr] - Both mobile app and web portal [both] #### UC-B-029 / staff-reporting Ask: What credential compliance reporting is needed? Answer: pick one Requirement type: audit-trail - HR compliance dashboard (credential status overview) [hr-dashboard] - Donor compliance reporting (staff qualification evidence) [donor-compliance] - Regulatory audit trail (full verification history) [regulatory-audit] #### UC-B-029 / staff-privacy Ask: What privacy requirements apply to staff credential data? Answer: pick one Requirement type: privacy - Standard HR data protection [standard] - GDPR/strict data protection (EU staff or EU-funded) [gdpr] - Security-sensitive (conflict zones, sensitive roles) [security-sensitive] #### UC-B-029 / holder-access-method Ask: How will individuals access and present their credentials or identity documents? Answer: pick one Requirement type: credentials - Mobile wallet app (smartphone required) [mobile-wallet] - Physical smart card with NFC or QR code [smart-card] - SMS/USSD-based access (feature phone compatible) [sms-ussd] - Hybrid: mobile app for those with smartphones, card for others [hybrid] ### UC-B-030: Volunteer identity and background verification Security level: Standard. #### UC-B-030 / background-check-scope Ask: What background checks are required for your volunteers? Answer: pick one Requirement type: privacy - Identity verification only [identity-only] - Identity + criminal record check [criminal] - Identity + criminal + safeguarding (working with children) [safeguarding] - Comprehensive (identity + criminal + safeguarding + references) [comprehensive] #### UC-B-030 / volunteer-credential-use Ask: How will volunteer credentials be used after verification? Answer: pick one Requirement type: credentials - Access control to programmes/sites only [access-control] - Presented to beneficiaries/communities for trust [community-trust] - Shared with partner organisations [partner-sharing] - All of the above [all] #### UC-B-030 / volunteer-privacy Ask: What privacy level is needed for volunteer background data? Answer: pick one Requirement type: privacy - Standard: verified status shared, details private [standard] - High privacy: privacy-preserving verification of clearance [zkp-clearance] - Tiered: different levels depending on the role sensitivity [tiered] - Not sure, need guidance on volunteer data privacy [unsure] #### UC-B-030 / volunteer-reporting Ask: What volunteer credential reporting do you currently have? Answer: pick one Requirement type: audit-trail - Basic volunteer status dashboard [basic] - Compliance tracking with expiry alerts [compliance] - Full audit trail for safeguarding compliance [full-audit] #### UC-B-030 / sq-UC-B-030-001 Ask: What credential revocation process is needed when a volunteer's status changes? Answer: pick one Requirement type: general - Instant revocation [instant-revocation] - Grace period [grace-period] - Suspend pending review [suspend-pending-review] - Automatic expiry [automatic-expiry] - Multi-party revocation [multi-party-revocation] #### UC-B-030 / consent-management-approach Ask: How do you currently manage consent for beneficiary data collection and sharing? Answer: pick one Requirement type: privacy - Granular consent: individuals control each data element shared [granular] - Tiered consent: pre-defined levels (basic, standard, full) [tiered] - Blanket consent with opt-out for specific data categories [blanket-optout] - Guardian/proxy consent for vulnerable populations [guardian-proxy] ### UC-B-031: Health worker and teacher certification verification Security level: Standard. #### UC-B-031 / worker-type Ask: What type of professional workers need certification verification? Answer: pick one Requirement type: credentials - Community health workers (CHWs) [chw] - Qualified health professionals (nurses, doctors) [health-professional] - Teachers and education staff [teachers] - Mixed, both health workers and educators [mixed] #### UC-B-031 / cert-verification-source Ask: How are certifications currently verified? Answer: pick one Requirement type: privacy - Paper certificates checked manually [paper-manual] - National/regional registries exist but are hard to access [registry-inaccessible] - No formal registry, rely on employer references [no-registry] - Digital registries available in some but not all countries [partial-digital] #### UC-B-031 / cert-portability Ask: Do professional certifications need to be recognised across borders? Answer: pick one Requirement type: integration - Single-country verification only [single-country] - Regional portability (neighbouring countries) [regional] - International portability for mobile workforce [international] #### UC-B-031 / cert-renewal-tracking Ask: Is ongoing certification renewal and continuing education tracking needed? Answer: pick one Requirement type: credentials - One-time verification: no renewal tracking [one-time] - Annual renewal tracking with alerts [annual-renewal] - Continuing professional development (CPD) credit tracking [cpd-tracking] #### UC-B-031 / cert-reporting Ask: What certification compliance reporting is needed? Answer: pick one Requirement type: audit-trail - Programme staffing compliance dashboard [programme] - Donor reporting on qualified staff metrics [donor] - Regulatory compliance reporting to health/education authorities [regulatory] #### UC-B-031 / holder-access-method Ask: How will individuals access and present their credentials or identity documents? Answer: pick one Requirement type: credentials - Mobile wallet app (smartphone required) [mobile-wallet] - Physical smart card with NFC or QR code [smart-card] - SMS/USSD-based access (feature phone compatible) [sms-ussd] - Hybrid: mobile app for those with smartphones, card for others [hybrid] ### UC-B-032: Implementing partner staff verification Security level: Standard. #### UC-B-032 / partner-vetting-scope Ask: What vetting is required for implementing partner staff? Answer: pick one Requirement type: privacy - Identity verification + sanctions screening [identity-sanctions] - Full background checks including criminal records [full-background] - Safeguarding-level checks (working with vulnerable populations) [safeguarding] - Counter-terrorism compliance checks [ct-compliance] #### UC-B-032 / partner-count Ask: How many implementing partners and partner staff need verification? Answer: pick one Requirement type: scale - 1-5 partners, under 50 staff total [small] - 5-20 partners, 50-500 staff [medium] - 20-100 partners, 500-5,000 staff [large] - 100+ partners, 5,000+ staff [massive] #### UC-B-032 / partner-credential-sharing Ask: Can partner staff credentials from other organisations be trusted and reused? Answer: pick one Requirement type: integration - Yes, accept verified credentials from trusted partners [accept-trusted] - Partial, accept some checks, redo others [partial-accept] - No, full independent verification required [independent] #### UC-B-032 / partner-monitoring Ask: Is ongoing monitoring of partner staff credentials needed? Answer: pick one Requirement type: privacy - One-time verification at onboarding [one-time] - Periodic re-screening (annual) [periodic] - Continuous monitoring with real-time alerts [continuous] #### UC-B-032 / partner-reporting Ask: What partner verification reporting is required? Answer: pick one Requirement type: audit-trail - Internal compliance dashboard [internal] - Donor compliance evidence [donor] - Regulatory compliance audit trail [regulatory] #### UC-B-032 / consent-management-approach Ask: How do you currently manage consent for beneficiary data collection and sharing? Answer: pick one Requirement type: privacy - Granular consent: individuals control each data element shared [granular] - Tiered consent: pre-defined levels (basic, standard, full) [tiered] - Blanket consent with opt-out for specific data categories [blanket-optout] - Guardian/proxy consent for vulnerable populations [guardian-proxy] ### UC-B-033: Educational credentials for displaced students Security level: Higher. #### UC-B-033 / education-level Ask: What education levels need credential support? Answer: pick one Requirement type: credentials - Primary school (ages 6-12) [primary] - Secondary school (ages 12-18) [secondary] - Both primary and secondary [both] - Post-secondary / higher education [post-secondary] #### UC-B-033 / education-portability Ask: What education systems need to recognise these credentials? Answer: pick one Requirement type: integration - Host country education system only [host-country] - Country of origin education system (for return) [origin-country] - Multiple country systems (regional portability) [regional] - International recognition (for resettlement) [international] #### UC-B-033 / education-prior-records Ask: What is the status of students' prior educational records? Answer: pick one Requirement type: privacy - Most students have prior school records from origin country [records-available] - Records exist but are inaccessible (left behind, destroyed) [records-inaccessible] - Most students have no prior educational documentation [no-records] - Mixed: some have records, many do not [mixed] #### UC-B-033 / education-holder-device Ask: How will students/families access and present credentials? Answer: pick one Requirement type: devices - Family smartphone (parent manages) [family-phone] - Printed certificate with QR verification code [printed-qr] - School-managed digital records (students access via portal) [school-managed] - Mixed: digital + printed [mixed] #### UC-B-033 / education-privacy Ask: What child data privacy protections do you currently have? Answer: pick one Requirement type: privacy - Standard student data protection [standard] - Enhanced child protection (displacement-sensitive) [enhanced] - Maximum privacy (conflict context: risk to child/family) [maximum] #### UC-B-033 / education-connectivity Ask: What connectivity is available at schools and learning centres? Answer: pick one Requirement type: offline - Reliable internet [connected] - Intermittent connectivity [intermittent] - Fully offline: remote or camp-based schools [offline] #### UC-B-033 / education-reporting Ask: What education programme reporting do you currently have? Answer: pick one Requirement type: audit-trail - Enrolment and completion statistics [basic] - Learning outcome tracking and analytics [outcome-tracking] - Donor reporting with education impact metrics [donor-impact] #### UC-B-033 / holder-access-method Ask: How will individuals access and present their credentials or identity documents? Answer: pick one Requirement type: credentials - Mobile wallet app (smartphone required) [mobile-wallet] - Physical smart card with NFC or QR code [smart-card] - SMS/USSD-based access (feature phone compatible) [sms-ussd] - Hybrid: mobile app for those with smartphones, card for others [hybrid] #### UC-B-033 / beneficiary-choice Ask: How will beneficiaries exercise choice in how they receive and use this service? Answer: pick one Requirement type: usability - Beneficiaries choose between delivery methods (cash, voucher, mobile money, direct) [delivery-choice] - Beneficiaries choose preferred merchants or service points [merchant-choice] - Beneficiaries control their own data sharing preferences [data-choice] - Multiple choice dimensions (delivery + merchant + data) [full-choice] - Limited choice: programme constraints determine delivery [limited] ### UC-B-034: Vocational training certificates Security level: Standard. #### UC-B-034 / voc-training-types Ask: What types of vocational training need certification? Answer: pick one Requirement type: credentials - Technical skills (construction, plumbing, electrical) [technical] - Digital/IT skills (computer literacy, coding) [digital] - Livelihood skills (agriculture, tailoring, small business) [livelihood] - Multiple skill categories [multiple] #### UC-B-034 / voc-employer-recognition Ask: What systems do employers currently use to verify and recognise vocational certificates? Answer: pick one Requirement type: integration - QR code scan for instant verification [qr-verification] - Online verification portal for employers [online-portal] - Integration with national qualification frameworks [nqf-integration] - Peer-to-peer credential sharing (no central lookup) [p2p] #### UC-B-034 / voc-micro-credentials Ask: Are modular/micro-credentials needed (stackable skills)? Answer: pick one Requirement type: credentials - Single certificate per training programme [single-cert] - Modular: stackable micro-credentials building to full certification [modular] - Competency-based: badge for each verified skill [competency-badges] #### UC-B-034 / voc-holder-device Ask: How will trainees access and present their certificates? Answer: pick one Requirement type: devices - Smartphone wallet app [smartphone] - Printed certificate with QR code [printed] - Both digital and printed [both] #### UC-B-034 / voc-reporting Ask: What training programme reporting do you currently have? Answer: pick one Requirement type: audit-trail - Training completion statistics [completion] - Employment outcome tracking [employment] - Donor impact reporting with livelihoods metrics [donor-impact] #### UC-B-034 / holder-access-method Ask: How will individuals access and present their credentials or identity documents? Answer: pick one Requirement type: credentials - Mobile wallet app (smartphone required) [mobile-wallet] - Physical smart card with NFC or QR code [smart-card] - SMS/USSD-based access (feature phone compatible) [sms-ussd] - Hybrid: mobile app for those with smartphones, card for others [hybrid] #### UC-B-034 / beneficiary-choice Ask: How will beneficiaries exercise choice in how they receive and use this service? Answer: pick one Requirement type: usability - Beneficiaries choose between delivery methods (cash, voucher, mobile money, direct) [delivery-choice] - Beneficiaries choose preferred merchants or service points [merchant-choice] - Beneficiaries control their own data sharing preferences [data-choice] - Multiple choice dimensions (delivery + merchant + data) [full-choice] - Limited choice: programme constraints determine delivery [limited] ### UC-B-035: Skills attestation and competency verification Security level: Standard. #### UC-B-035 / skills-assessment-method Ask: How are skills and competencies assessed? Answer: pick one Requirement type: privacy - Formal examination or test [formal-exam] - Practical demonstration observed by assessor [practical-demo] - Portfolio of evidence (work samples) [portfolio] - Peer assessment and community attestation [peer-assessment] #### UC-B-035 / skills-taxonomy Ask: What skills classification system should be used? Answer: pick one Requirement type: credentials - ESCO (European Skills/Competences/Occupations) [esco] - National qualifications framework of operating country [national] - Custom competency framework designed for programme [custom] - International labour market standards (ILO) [ilo] #### UC-B-035 / skills-selective-disclosure Ask: Do skill holders need to selectively disclose specific competencies? Answer: pick one Requirement type: usability - Full skill profile shared with potential employers [full-disclosure] - Selective: choose which skills to present per opportunity [selective] - Zero-knowledge: prove skill level without revealing details [zkp] #### UC-B-035 / skills-employer-integration Ask: How will employers check and verify skills credentials? Answer: pick one Requirement type: integration - QR scan for instant verification [qr-scan] - Job platform integration (LinkedIn-style) [job-platform] - Employer API for bulk verification [employer-api] #### UC-B-035 / skills-reporting Ask: What skills programme reporting do you currently have? Answer: pick one Requirement type: audit-trail - Skills attainment statistics [attainment] - Labour market outcome tracking [labour-market] - Full impact chain (training → skills → employment → income) [full-impact] #### UC-B-035 / holder-access-method Ask: How will individuals access and present their credentials or identity documents? Answer: pick one Requirement type: credentials - Mobile wallet app (smartphone required) [mobile-wallet] - Physical smart card with NFC or QR code [smart-card] - SMS/USSD-based access (feature phone compatible) [sms-ussd] - Hybrid: mobile app for those with smartphones, card for others [hybrid] #### UC-B-035 / beneficiary-choice Ask: How will beneficiaries exercise choice in how they receive and use this service? Answer: pick one Requirement type: usability - Beneficiaries choose between delivery methods (cash, voucher, mobile money, direct) [delivery-choice] - Beneficiaries choose preferred merchants or service points [merchant-choice] - Beneficiaries control their own data sharing preferences [data-choice] - Multiple choice dimensions (delivery + merchant + data) [full-choice] - Limited choice: programme constraints determine delivery [limited] ### UC-B-036: Community governance participation eligibility Security level: Standard. #### UC-B-036 / eligibility-criteria Ask: What determines eligibility for community governance participation? Answer: pick one Requirement type: credentials - Residency in community (geographic-based) [residency] - Programme beneficiary status [beneficiary-status] - Age and legal capacity [age-capacity] - Multiple criteria (residency + age + status) [multiple] #### UC-B-036 / governance-privacy Ask: What privacy protections are needed for governance participation? Answer: pick one Requirement type: privacy - Eligibility is publicly verifiable (transparent) [public] - Private eligibility: verify without revealing personal data [private-verify] - Anonymous participation: zero-knowledge eligibility proof [anonymous] #### UC-B-036 / governance-reporting Ask: What participation reporting do you currently have? Answer: pick one Requirement type: audit-trail - Participation rates and demographics [participation] - Governance process audit trail [audit] - Community feedback and satisfaction [feedback] #### UC-B-036 / comm-gov-participant-count Ask: How many organisations or stakeholders participate in community governance? Answer: pick one Requirement type: scale - 2–5 parties [small] - 6–15 parties [medium] - 16–50 parties [large] - Over 50 parties [enterprise] #### UC-B-036 / sq-UC-B-036-001 Ask: How is eligibility currently verified at the moment of governance participation? Answer: pick one Requirement type: general - Credential scan [credential-scan] - Biometric match [biometric-match] - Community attestation [community-attestation] - Token-based verification [token-based] - Pre-approved roster [pre-approved-roster] #### UC-B-036 / sq-UC-B-036-003 Ask: How is governance participation currently recorded to prevent double-voting? Answer: pick one Requirement type: general - Digital one-time-use voting token [on-chain-nullifier] - Physical token surrender [physical-token-surrender] - Biometric deduplication [biometric-dedup] - Time-locked credential [time-locked-credential] - Public roll call [public-roll-call] ### UC-B-037: Consent records and data sharing permissions Security level: Standard. #### UC-B-037 / consent-granularity Ask: What level of consent granularity is needed? Answer: pick one Requirement type: privacy - Programme-level consent (blanket consent for all data within programme) [programme-level] - Purpose-level consent (consent per data use purpose) [purpose-level] - Field-level consent (consent per individual data element) [field-level] - Recipient-level consent (consent per data sharing partner) [recipient-level] #### UC-B-037 / consent-immutability Ask: How are consent records currently stored and proven in your operations? Answer: pick one Requirement type: privacy - Permanent tamper-proof ledger (digital ledger-anchored consent trail) [immutable-ledger] - Auditable database with tamper-evident logging [auditable-db] - Beneficiary-held consent credentials (user-controlled portable) [beneficiary-held] #### UC-B-037 / consent-withdrawal Ask: How is consent withdrawal currently handled? Answer: pick one Requirement type: privacy - Full withdrawal (all data sharing stopped) [full-withdrawal] - Selective withdrawal (withdraw specific consents) [selective] - Right to erasure (data deletion on withdrawal) [right-to-erasure] #### UC-B-037 / consent-beneficiary-interface Ask: How will beneficiaries manage their consent preferences? Answer: pick one Requirement type: privacy - Through field staff at service points [staff-mediated] - Self-service via mobile app [self-service-app] - USSD/SMS-based consent management [ussd-sms] - Mixed channels [mixed] #### UC-B-037 / consent-reporting Ask: What consent compliance reporting is needed? Answer: pick one Requirement type: privacy - Internal compliance dashboard [internal] - Data protection authority reporting (GDPR Art. 30) [dpa-reporting] - Donor data protection compliance evidence [donor-compliance] #### UC-B-037 / verification-mechanism Ask: How are credentials or records currently verified? Answer: pick one Requirement type: credentials - digitally verified (signature-based proof) [cryptographic] - Multi-party attestation (multiple parties vouch) [multi-party] - Biometric verification [biometric] - Document-based verification with hash proof [document-hash] #### UC-B-037 / beneficiary-choice Ask: How will beneficiaries exercise choice in how they receive and use this service? Answer: pick one Requirement type: usability - Beneficiaries choose between delivery methods (cash, voucher, mobile money, direct) [delivery-choice] - Beneficiaries choose preferred merchants or service points [merchant-choice] - Beneficiaries control their own data sharing preferences [data-choice] - Multiple choice dimensions (delivery + merchant + data) [full-choice] - Limited choice: programme constraints determine delivery [limited] ### UC-B-038: Age verification for child protection programmes Security level: Critical. #### UC-B-038 / age-verification-method Ask: How do you currently verify someone's age? Answer: pick one Requirement type: privacy - Document-based (birth certificate, ID with DOB) [document-based] - AI-based facial age estimation [ai-estimation] - Community attestation (community members verify age) [community-attestation] - Skeletal/dental age assessment (medical) [medical-assessment] #### UC-B-038 / age-proof-type Ask: What type of age documentation do people in your context typically have? Answer: pick one Requirement type: audit-trail - Exact date of birth credential [exact-dob] - Age range credential (e.g., under-18, 12-15) [age-range] - Binary proof (over/under threshold, no age revealed) [binary-proof] #### UC-B-038 / child-consent Ask: What consent model is needed for verifying children's ages? Answer: pick one Requirement type: privacy. Hard gate: yes - Guardian consent required for all verification [guardian-required] - Guardian consent + child assent (age-appropriate) [guardian-plus-assent] - Mature minor self-consent (for older adolescents) [mature-minor] #### UC-B-038 / child-data-protection Ask: What level of data protection is required for children's records? Answer: pick one Requirement type: privacy. Hard gate: yes - Standard child data protection (encrypted, access-controlled) [standard] - Enhanced protection (no central age data stored) [enhanced] - Maximum protection (zero-knowledge: no data retained) [maximum] #### UC-B-038 / age-reporting Ask: What age verification reporting is needed? Answer: pick one Requirement type: audit-trail - Aggregate statistics (number of children verified by age group) [aggregate] - Safeguarding compliance reporting [safeguarding] - Full child protection audit trail [full-audit] #### UC-B-038 / beneficiary-choice Ask: How will beneficiaries exercise choice in how they receive and use this service? Answer: pick one Requirement type: usability - Beneficiaries choose between delivery methods (cash, voucher, mobile money, direct) [delivery-choice] - Beneficiaries choose preferred merchants or service points [merchant-choice] - Beneficiaries control their own data sharing preferences [data-choice] - Multiple choice dimensions (delivery + merchant + data) [full-choice] - Limited choice: programme constraints determine delivery [limited] ### UC-B-039: Cross-agency credential portability for humanitarian workforce Security level: Standard. #### UC-B-039 / credentials-in-scope Ask: Which credential types are in scope for cross-agency portability? Answer: pick one Requirement type: credentials - Professional qualifications only (degrees, certs) [professional] - Professional + safeguarding / PSEA attestations [safeguarding] - Comprehensive (professional + safeguarding + clearance + deployment history + medical) [comprehensive] #### UC-B-039 / portability-reach Ask: How far should portability extend? Answer: pick one Requirement type: general - Within a specific consortium (e.g., Start Network, ACT Alliance) [consortium] - UN-family agencies (UNHCR, UNICEF, WFP, UNDP, UNFPA) [un-family] - Full humanitarian ecosystem (UN + INGO + local partners) [ecosystem] #### UC-B-039 / issuer-readiness Ask: How ready are credential issuers (HR departments, training providers) for VC issuance? Answer: pick one Requirement type: governance - Mostly paper / PDF certificates today [paper] - Mixed: some digital certificates, some paper [mixed] - Mostly digital, some VC pilots [digital] #### UC-B-039 / staff-wallet-model Ask: How will staff hold their credentials? Answer: pick one Requirement type: usability - Cloud-custody wallet (agency-hosted) [cloud] - Self-custody mobile wallet [self] - Hybrid: self-custody with agency-assisted recovery [hybrid] #### UC-B-039 / verification-latency Ask: How fast does verification need to be (onboarding speed)? Answer: pick one Requirement type: credentials - Days acceptable [days] - Hours (emergency deployment) [hours] - Minutes (surge-roster activation) [minutes] ### UC-B-040: Farmer cooperative registry and member digital ID Security level: Standard. #### UC-B-040 / cooperative-count Ask: How many cooperatives will take part? Answer: pick one Requirement type: scale - Fewer than 10 cooperatives [under-10] - 10 to 50 cooperatives [10-50] - 50 to 500 cooperatives [50-500] - Over 500 cooperatives [over-500] #### UC-B-040 / members-per-cooperative Ask: How many members does a typical cooperative have? Answer: pick one Requirement type: scale - Average under 50 members [under-50] - 50 to 500 members [50-500] - 500 to 5,000 members [500-5000] - Over 5,000 members [over-5000] #### UC-B-040 / issuer-model Ask: Who will issue the membership credentials? Answer: pick one Requirement type: governance - Implementing CSO is the credential issuer [cso-issuer] - National cooperative authority is the issuer [government-issuer] - Each cooperative issues its own credentials [cooperative-issuer] - Federated: CSO + government + cooperative jointly issue [federated] #### UC-B-040 / member-credential-claims Ask: What should a membership credential say? Answer: pick all that apply Requirement type: credentials - Active membership status [membership-status] - Membership tenure [tenure] - Role within cooperative (officer, member) [role] - Aggregated output contribution history [output-history] - Training and capacity-building completed [training-completed] #### UC-B-040 / women-specific-design Ask: How much should the design focus on women members? Answer: pick one Requirement type: general - Not a women-led cooperative focus [not-applicable] - Aware of women-specific needs but no specific design [aware] - Women-specific design integrated [integrated] - Women-only cooperatives are the primary focus [women-only] #### UC-B-040 / buyers-readers Ask: Who will need to check a member's credential? Answer: pick all that apply Requirement type: general - Agribusiness buyers verifying cooperative legitimacy [agribusiness-buyers] - Banks or microfinance verifying member eligibility [financial-institutions] - Donor programmes verifying member-level reach [donors] - Government extension and subsidy programmes [government] - Export buyers verifying cooperative standards [export-buyers] #### UC-B-040 / national-id-linkage Ask: Must members link a national ID? Answer: pick one Requirement type: general - Required and accessible [required-and-available] - Optional: members may link if they wish [optional] - Not required for credential validity [not-required] - National ID coverage for women is weak: explicit alternative needed [women-exclusionary] #### UC-B-040 / revocation-process Ask: How will a credential be withdrawn? Answer: pick one Requirement type: governance - Issuer revokes unilaterally [issuer-only] - Dispute resolution before revocation [dispute-resolved] - Member appeal rights to independent body [appeal-rights] - No revocation process, credentials are perpetual [none] #### UC-B-040 / islamic-finance-bundling Ask: Will an Islamic finance product come with the credential? Answer: pick one Requirement type: general - No Islamic finance instrument bundled [none] - Qard hasan lending bundled [qard-hasan] - Takaful coverage bundled [takaful] - Zakat distribution bundled [zakat] - Multiple Islamic finance instruments [multiple] ### UC-C-039: Medical records (private but verifiable) Security level: Critical. #### UC-C-039 / access-control-model Ask: Who currently has access to medical records, and how is that controlled? Answer: pick one Requirement type: privacy - Patient controls all access (explicit consent per access) [patient-controlled] - Role-based access (doctors, nurses, admins) [role-based] - Attribute-based access (credentials, time, location) [attribute-based] - Time-limited access (emergency override with audit) [time-limited] - Hierarchical access (consulting physicians can grant access) [hierarchical] #### UC-C-039 / consent-granularity Ask: What is your current consent granularity requirement? (Do you consent per record, per data category, or blanket?) Answer: pick one Requirement type: privacy - Broad consent (all data to all providers) [broad-consent] - Per-record type consent (consent for each data category) [per-type-consent] - Per-purpose consent (specific use cases like diagnosis vs. research) [per-purpose-consent] - Granular per-field consent (consent for specific data elements) [granular-consent] - Dynamic consent (real-time requests and decisions) [dynamic-consent] #### UC-C-039 / interoperability-systems Ask: What health systems or networks do you need to interoperate with? Answer: pick one Requirement type: integration - National health information exchange (HIE) [national-hie] - Regional hospital networks only [regional-networks] - International medical tourism and cross-border care [international] - Public health surveillance systems [public-health] - Research and data analytics networks [research-networks] #### UC-C-039 / offline-capability Ask: Do you need to support offline access to medical records in remote areas? Answer: pick one Requirement type: offline - Full offline access with sync when connectivity returns [full-offline] - Read-only offline access with online updates only [read-only-offline] - Cached records only for current patient [cached-only] - Always requires connectivity; offline not needed [online-only] - Hybrid: critical data cached, rest online [hybrid-offline] #### UC-C-039 / audit-compliance Ask: What audit and compliance logging do you need for regulatory requirements? Answer: pick one Requirement type: legal-checks - Basic access logs (who accessed what and when) [basic-logs] - HIPAA-compliant audit trail with protected data integrity [hipaa-audit] - GDPR-compliant with data processing agreements [gdpr-audit] - Real-time alert system for suspicious access patterns [realtime-alerts] - Tamper-proof permanent tamper-proof audit on digital ledger [blockchain-audit] #### UC-C-039 / privacy-approach Ask: What level of privacy protection is needed for sensitive data? Answer: pick one Requirement type: privacy - End-to-end encryption with role-based decryption [e2e-role-based] - Zero-knowledge proofs (verify without revealing data) [zkp] - privacy-preserving computation (data stays encrypted during analysis) [homomorphic] - Standard encryption with access control lists [standard-acl] #### UC-C-039 / beneficiary-choice Ask: How will beneficiaries exercise choice in how they receive and use this service? Answer: pick one Requirement type: privacy - Beneficiaries choose between delivery methods (cash, voucher, mobile money, direct) [delivery-choice] - Beneficiaries choose preferred merchants or service points [merchant-choice] - Beneficiaries control their own data sharing preferences [data-choice] - Multiple choice dimensions (delivery + merchant + data) [full-choice] - Limited choice: programme constraints determine delivery [limited] ### UC-C-040: Vaccination history and immunisation records Security level: Standard. #### UC-C-040 / provider-access-model Ask: What system would you need for provider access to vaccination records? Answer: pick one Requirement type: privacy - Direct query to patient's vaccination wallet [wallet-direct] - Centralized registry lookup by provider [centralized-registry] - Patient-mediated sharing (patient grants one-time access) [patient-mediated] - Provider network with service-to-service APIs [service-api] - Offline credential sharing (credential shown to provider) [offline-sharing] #### UC-C-040 / cross-border-portability Ask: Do you need to support cross-border sharing of vaccination records, and what jurisdictions are involved? Answer: pick one Requirement type: integration - Regional (e.g., East Africa Community travel) [regional-travel] - International (visa, residency, work permits) [international-travel] - Refugee or displaced persons context [refugee-context] - No cross-border requirement; domestic only [domestic-only] - Medical tourism (treatment in multiple countries) [medical-tourism] #### UC-C-040 / record-verification Ask: What verification process do you currently use or require for vaccination records? Answer: pick one Requirement type: audit-trail - Checking signatures or stamps from the issuing clinic [checking-signatures-or-stamps-from-the-i] - Cross-referencing against a central health registry [cross-referencing-against-a-central-heal] - Third-party review or notarisation [third-party-review-or-notarisation] - Multiple organisations confirm the same record [multiple-organisations-confirm-the-same-] - No verification process currently, records are trusted at face value [no-verification-process-currently-record] #### UC-C-040 / consent-withdrawal Ask: What is your current approach to consent withdrawal for vaccination record sharing? Answer: pick one Requirement type: privacy - Immediate withdrawal with retroactive effect [immediate-retroactive] - Immediate withdrawal, but past accesses remain valid [immediate-prospective] - Withdrawal with notice period (e.g., 30 days) [notice-period] - No withdrawal once consent given [no-withdrawal] - Withdrawal by credential expiry only [expiry-only] #### UC-C-040 / multi-clinic-sync Ask: How do you currently synchronize vaccination records across your clinics? Answer: pick one Requirement type: integration - Centralized registry with periodic sync [centralized-sync] - Real-time push updates to all clinics [realtime-push] - Patient-mediated sync (patient downloads and shares) [patient-mediated-sync] - Federated query (each clinic queries directly) [federated-query] - No sync; each clinic keeps separate records [no-sync] #### UC-C-040 / offline-verification Ask: Do you need vaccination credentials to be verifiable in offline settings? Answer: pick one Requirement type: offline - Fully offline verification (secure digital check only) [fully-offline] - Offline with cached revocation list [offline-cached] - Online verification required [online-required] - Hybrid: offline for valid checks, online for revocation [hybrid-offline] - Not applicable; online always available [not-applicable] #### UC-C-040 / privacy-approach Ask: What level of privacy protection is needed for sensitive data? Answer: pick one Requirement type: privacy - End-to-end encryption with role-based decryption [e2e-role-based] - Zero-knowledge proofs (verify without revealing data) [zkp] - privacy-preserving computation (data stays encrypted during analysis) [homomorphic] - Standard encryption with access control lists [standard-acl] #### UC-C-040 / beneficiary-choice Ask: How will beneficiaries exercise choice in how they receive and use this service? Answer: pick one Requirement type: privacy - Beneficiaries choose between delivery methods (cash, voucher, mobile money, direct) [delivery-choice] - Beneficiaries choose preferred merchants or service points [merchant-choice] - Beneficiaries control their own data sharing preferences [data-choice] - Multiple choice dimensions (delivery + merchant + data) [full-choice] - Limited choice: programme constraints determine delivery [limited] ### UC-C-041: Mental health and psychosocial support records Security level: Critical. #### UC-C-041 / mhpss-data-sensitivity Ask: What is the highest sensitivity level of MHPSS data you collect? Answer: pick one Requirement type: privacy - Non-identifying (e.g., symptom checklists, general counseling notes) [non-identifying] - Client-identifying but without detailed diagnoses [client-identifying] - Detailed diagnoses and treatment history [detailed-clinical] - Trauma narratives and crisis information [trauma-crisis] - Suicide risk assessments and safety plans [suicide-risk] #### UC-C-041 / provider-types Ask: What types of providers need access to MHPSS records? Answer: pick one Requirement type: privacy - Licensed mental health professionals only (psychologists, psychiatrists) [licensed-mh] - Broader team (counselors, social workers, case managers) [broader-team] - Medical providers with consent (nurses, doctors for holistic care) [medical-integration] - Multi-sector partners (protection, legal services) [multisector] - Para-professionals and community health workers (with limited access) [para-professionals] #### UC-C-041 / anonymization-reporting Ask: What anonymization requirements do you have for GBV survivor records in your reporting? Answer: pick one Requirement type: privacy - Aggregate statistics only (no individual records) [aggregate-only] - De-identified but linkable (pseudonymized) [pseudonymized] - Fully anonymized (irreversible removal of identifiers) [fully-anonymous] - Differential privacy (statistical noise added) [differential-privacy] - No reporting; data kept strictly confidential [no-reporting] #### UC-C-041 / explicit-consent-model Ask: What is your current consent process for GBV case management data? Answer: pick one Requirement type: privacy - Explicit written consent at service start [written-consent] - Explicit verbal consent (recorded and documented) [verbal-consent] - Dynamic consent (re-consent at each session) [dynamic-consent] - Separate consent for different use cases (clinical vs. research) [use-based-consent] - Implied consent (consent as part of service enrollment) [implied-consent] #### UC-C-041 / crisis-protocols Ask: What is your current crisis response protocol for GBV case data? Answer: pick one Requirement type: privacy - Emergency break-glass access with immediate audit and client notification [break-glass-notify] - Break-glass access with post-hoc review and potential client notification [break-glass-review] - Limited emergency protocols (specific authorized providers only) [limited-emergency] - No emergency override; standard consent required always [no-override] - Client-specified emergency contacts with pre-authorized access [pre-authorized-emergency] #### UC-C-041 / data-retention-deletion Ask: What is your policy for retaining and deleting MHPSS records? Answer: pick one Requirement type: privacy - Minimum retention: delete after treatment ends [minimum-retention] - Standard retention: 5-7 years after last contact [standard-retention] - Extended retention: until client turns 18 (for minors) [extended-minors] - Permanent retention: archived for life [permanent-retention] - Client-controlled: client can request deletion anytime [client-controlled] #### UC-C-041 / multi-language-cultural Ask: What languages and cultural contexts do you need to support? Answer: pick one Requirement type: usability - Records in client's primary language with translation service [multilingual] - Notes include cultural context and community-specific practices [cultural-context] - Community-designed data model reflecting local healing traditions [community-designed] - Interpreter notes and cross-cultural competency documentation [interpreter-docs] - Standard clinical model only; cultural factors noted informally [clinical-standard] #### UC-C-041 / interagency-safety Ask: What are your data sharing agreements with other agencies for GBV cases? Answer: pick one Requirement type: integration - No sharing; strict confidentiality within single agency [no-sharing] - Minimal sharing: safety summary only, not detailed records [summary-sharing] - Conditional sharing: only with explicit client consent per instance [conditional-sharing] - Coordinated cross-agency query: other agencies query without full record access [federated-query] - De-identified sharing: aggregated, never individual records [deidentified-sharing] #### UC-C-041 / audit-and-oversight Ask: What audit and oversight mechanisms should monitor MHPSS record access? Answer: pick one Requirement type: audit-trail - Client-visible audit log (client can see who accessed when) [client-visible-audit] - Supervisor review of all access (human oversight) [supervisor-review] - Real-time anomaly alerts (automatic detection of suspicious access) [anomaly-alerts] - Monthly audit reports shared with client [monthly-reports] - Permanent tamper-proof digital ledger audit trail [blockchain-audit] #### UC-C-041 / beneficiary-choice Ask: How will beneficiaries exercise choice in how they receive and use this service? Answer: pick one Requirement type: privacy - Beneficiaries choose between delivery methods (cash, voucher, mobile money, direct) [delivery-choice] - Beneficiaries choose preferred merchants or service points [merchant-choice] - Beneficiaries control their own data sharing preferences [data-choice] - Multiple choice dimensions (delivery + merchant + data) [full-choice] - Limited choice: programme constraints determine delivery [limited] ### UC-C-042: Gender-based violence and protection case data Security level: Critical. #### UC-C-042 / survivor-data-control Ask: Should survivors have primary control over who accesses their case data? Answer: pick one Requirement type: privacy - Yes, survivor controls all access (even staff need permission) [survivor-controlled] - Survivor controls sharing outside organization [survivor-external-control] - Organization controls access based on role, survivor notified [role-controlled-notify] - Organization controls access, survivor cannot override [org-controlled] - Case-by-case: depends on survivor capacity and safety assessment [case-specific] #### UC-C-042 / end-to-end-encryption-gbv Ask: What level of encryption must GBV case records have? Answer: pick one Requirement type: privacy. Hard gate: yes - Maximum: end-to-end encryption with survivor-held keys [e2e-survivor-keys] - Strong: end-to-end encryption with organizational key escrow [e2e-org-escrow] - Standard: AES-256 at rest, TLS in transit [standard-encryption] - Lightweight: encryption sufficient for local regulations [lightweight] - Risk-based: encryption level depends on threat assessment [risk-based] #### UC-C-042 / safe-case-data-storage Ask: Where should sensitive GBV case records be stored? Answer: pick one Requirement type: residency - Only locally (no cloud, minimize external exposure) [local-only] - Local with encrypted cloud backup (survivor-controlled encryption) [local-plus-encrypted-cloud] - Distributed storage (data fragments in multiple locations) [distributed-storage] - Private cloud (organization's own infrastructure) [private-cloud] - Zero-knowledge cloud (provider cannot see data) [zero-knowledge-cloud] #### UC-C-042 / evidence-preservation Ask: What evidence preservation requirements do you have for GBV cases? Answer: pick one Requirement type: audit-trail - Digital signatures and hash verification for authenticity [digital-signature] - Digital timestamping for permanent tamper-proof proof of existence [blockchain-timestamp] - Third-party notarization and witness signatures [notarization] - Chain of custody documentation with secure handoff [chain-of-custody] - Multiple of the above (layered evidence preservation) [layered-preservation] #### UC-C-042 / gbv-ims-integration Ask: Do you need to integrate with the GBV Information Management System (GBV IMS)? Answer: pick one Requirement type: integration - Yes, full integration with GBV IMS data standards [full-gbv-ims] - Partial integration (core data elements compatible) [partial-gbv-ims] - No integration; use own case management system [no-integration] - Export capability to GBV IMS format only [export-only] - Multiple systems: GBV IMS plus local system [multiple-systems] #### UC-C-042 / consent-withdrawal-gbv Ask: What is your approach to consent withdrawal for GBV evidence? Answer: pick one Requirement type: privacy - Immediate deletion (all records destroyed) [immediate-delete] - Anonymization (identifiers removed, data retained for learning) [anonymize] - Restricted access (data locked, only accessed with new consent) [restricted-access] - Archive and seal (stored but not accessed without legal process) [archive-seal] - Survivor chooses: delete or anonymize per instance [survivor-choice] #### UC-C-042 / safe-referral-pathways Ask: What are your current safe referral pathways for GBV survivors? Answer: pick one Requirement type: integration - Referral with survivor consent and encrypted information transfer [consent-encrypted-referral] - Survivor-mediated referral (survivor carries info to referral service) [survivor-mediated] - Referral via trusted intermediary (known safe provider) [trusted-intermediary] - No direct referral; survivor contacts services independently [survivor-initiated] - Service network with pre-established trust and data sharing [trusted-network] #### UC-C-042 / audit-reporting-gbv Ask: What audit and reporting requirements do you have for GBV cases? Answer: pick one Requirement type: audit-trail - Survivor-visible access log (survivor can see all access) [survivor-visible] - Organization audit for compliance (staff oversight) [org-audit] - Aggregate reporting (no individual case details) [aggregate-reporting] - External audit by independent body [external-audit] - No audit (maximum privacy, minimal oversight) [no-audit] #### UC-C-042 / beneficiary-choice Ask: How will beneficiaries exercise choice in how they receive and use this service? Answer: pick one Requirement type: privacy - Beneficiaries choose between delivery methods (cash, voucher, mobile money, direct) [delivery-choice] - Beneficiaries choose preferred merchants or service points [merchant-choice] - Beneficiaries control their own data sharing preferences [data-choice] - Multiple choice dimensions (delivery + merchant + data) [full-choice] - Limited choice: programme constraints determine delivery [limited] ### UC-C-043: Beneficiary deduplication across programmes and organisations Security level: Higher. #### UC-C-043 / matching-algorithm Ask: How do you currently identify duplicate beneficiary records across programmes? Answer: pick one Requirement type: general - Deterministic: exact field matches (name, ID, DOB) [deterministic] - Probabilistic: similarity scoring with threshold [probabilistic] - Privacy-preserving: secure multi-party computation matching [secure-mpc] - Biometric: fingerprint or iris matching across programs [biometric] - Hybrid: combination of above methods [hybrid] #### UC-C-043 / privacy-tech-choice Ask: What privacy-preserving technology should protect beneficiary privacy during matching? Answer: pick one Requirement type: privacy - privacy-preserving computation (data stays encrypted during analysis) [homomorphic] - Secure multi-party computation (distributed trust) [multiparty-computation] - Differential privacy (add statistical noise) [differential-privacy] - Trusted execution environment (hardware secure enclave) [tee] - None: centralized matching with access control [none-central] #### UC-C-043 / deduplication-proof Ask: What method do you currently use to prove deduplication of beneficiary records? Answer: pick one Requirement type: audit-trail - Audit trail log (who matched what, when) [audit-trail] - Secure digital proof (hash of matches on digital ledger) [crypto-proof] - Third-party audit (independent verification) [third-party] - Beneficiary transparency (beneficiary sees own matches) [beneficiary-transparency] - Multi-signature approval (multiple parties sign off) [multi-signature] #### UC-C-043 / duplicate-resolution Ask: When duplicates are detected, what is your current policy for resolving conflicting data? (Primary source always wins / manual review / newest record) Answer: pick one Requirement type: audit-trail - Automatic merge (combine records, deactivate duplicate) [auto-merge] - Manual review and merge (human decision) [manual-merge] - Flag for investigation (mark as potential duplicate, no action) [flag-investigate] - Notify beneficiary (let them decide) [notify-beneficiary] - Ring-fencing (keep separate but link for alerts) [ring-fencing] #### UC-C-043 / beneficiary-consent-dedup Ask: Should beneficiaries consent to participation in deduplication? Answer: pick one Requirement type: privacy - Yes, explicit consent required for matching [explicit-consent] - Implied consent (part of program enrollment) [implied-consent] - Notification only (beneficiary informed but no consent) [notification] - Opt-out (beneficiary can refuse deduplication) [opt-out] - No choice (required for program participation) [no-choice] #### UC-C-043 / data-retention-dedup Ask: How long should deduplication records and beneficiary data be retained? Answer: pick one Requirement type: privacy - Only during active enrollment (deleted on exit) [active-enrollment-only] - 5-7 years for audit and fraud prevention [five-years] - Indefinite retention for historical tracking [indefinite] - Beneficiary-controlled (beneficiary can request deletion) [beneficiary-controlled] - Risk-based (retention depends on fraud risk) [risk-based] #### UC-C-043 / dedup-error-correction Ask: What happens if someone is incorrectly identified as a duplicate? Answer: pick one Requirement type: audit-trail - Automatic reversal (records unmerged with full history restore) [auto-reversal] - Manual unmerge process (human decision to split records) [manual-unmerge] - Create separate record (keep merged, create new clean record) [new-record] - Appeal process (beneficiary can appeal to dispute match) [appeal-process] - No correction; merged records kept (minimal remedy) [no-correction] #### UC-C-043 / beneficiary-choice Ask: How will beneficiaries exercise choice in how they receive and use this service? Answer: pick one Requirement type: privacy - Beneficiaries choose between delivery methods (cash, voucher, mobile money, direct) [delivery-choice] - Beneficiaries choose preferred merchants or service points [merchant-choice] - Beneficiaries control their own data sharing preferences [data-choice] - Multiple choice dimensions (delivery + merchant + data) [full-choice] - Limited choice: programme constraints determine delivery [limited] ### UC-C-044: Impact data integrity and verification Security level: Standard. #### UC-C-044 / data-collection-integrity Ask: How do you currently ensure data collected in the field is accurate? Answer: pick one Requirement type: audit-trail - Enumerator authentication with timestamp and GPS [enumerator-gps] - digitally verified verification of data [hash-verification] - Random field audits and beneficiary verification calls [random-audit] - Multi-person data collection (redundant verification) [multi-person] - Computer vision verification (photo/video proof) [computer-vision] #### UC-C-044 / automated-rules-checking Ask: What automated validation rules do you currently apply to impact data? Answer: pick one Requirement type: audit-trail - Yes, hard rules that reject impossible data [hard-rules] - Yes, soft rules that flag suspicious data for review [soft-rules] - Yes, AI-based anomaly detection [ai-anomaly] - Minimal: only check for missing required fields [minimal-rules] - No: trust enumerators without automated checks [no-rules] #### UC-C-044 / external-verification-proof Ask: What process would you need for documenting external verification of impact? Answer: pick one Requirement type: audit-trail - Third-party digital signature on verification report [digital-signature] - Photo/video evidence with metadata proof [photo-evidence] - Beneficiary attestation (signed consent to impact claim) [beneficiary-attestation] - automated rules with automatic payout on verification [smart-contract] - Simple text documentation (minimal proof) [text-documentation] #### UC-C-044 / offline-data-collection Ask: How do you currently verify offline-collected data upon sync? Answer: pick one Requirement type: audit-trail - Checksum verification (data integrity check on sync) [checksum] - Timestamp verification (validate data was collected offline) [timestamp] - Enumerator re-authentication (require auth on sync) [reauthentication] - Random verification subset (re-verify sample on sync) [random-subset] - No special verification for offline data [no-verification] #### UC-C-044 / compliance-reporting Ask: What are your impact data reporting requirements from donors and regulators? Answer: pick one Requirement type: legal-checks - Raw data export with full audit trail [raw-with-audit] - Aggregate statistics with privacy protection [aggregate-stats] - Digitally-backed verifiable reports [blockchain-reports] - Third-party certified reports [certified-reports] - Simple CSV export (minimal compliance) [simple-csv] ### UC-C-045: Consent management and audit trails Security level: Standard. #### UC-C-045 / consent-granularity-level Ask: At what level of detail do you obtain consent from beneficiaries? Answer: pick one Requirement type: privacy - Broad: single consent for all data use [broad-consent] - Per-purpose: separate consent for each use (clinical, research, reporting) [per-purpose] - Per-data-type: consent for each data category (name, health, location) [per-datatype] - Per-field: granular consent for each individual data field [per-field] - Dynamic: just-in-time consent requests at point of use [dynamic] #### UC-C-045 / consent-withdrawal-mechanism Ask: What is your current approach to consent withdrawal in your programmes? Answer: pick one Requirement type: privacy - Self-service portal (beneficiary withdraws directly) [self-service] - Phone or in-person request (staff processes withdrawal) [phone-inperson] - Automatic expiry (consent expires on date) [auto-expiry] - Hard-stop withdrawal (retroactive effect on past access) [hard-stop] - No withdrawal (consent cannot be withdrawn once given) [no-withdrawal] #### UC-C-045 / consent-audit-logging Ask: How do you currently track and log consent decisions? Answer: pick one Requirement type: privacy - Permanent tamper-proof digital ledger consent ledger [blockchain-consent] - Append-only database (no modification possible) [append-only-db] - Digital signatures on consent records [digital-signatures] - Standard access logs (can be modified) [standard-logs] - No specific consent audit (separate from data access) [no-audit] #### UC-C-045 / consent-documentation Ask: What documentation format and medium do you currently use for consent? Answer: pick one Requirement type: privacy - Video recording of consent conversation [video-recording] - Digital signature on consent form [digital-signature] - Consent form with witness signatures [witnessed-consent] - Simple checkbox consent (no specific evidence) [checkbox-consent] - Implicit consent (no documentation) [implicit-consent] #### UC-C-045 / consent-for-minors Ask: What is your current process for obtaining consent from minors? Answer: pick one Requirement type: privacy. Hard gate: yes - Parental/guardian consent required for all minors [parental-consent] - Minor assent + guardian consent (dual agreement) [dual-consent] - Mature minor standard (minor can consent if mature enough) [mature-minor] - Age-based threshold (consent at specific age) [age-threshold] - No specific minor protections (same as adults) [no-minor-protection] #### UC-C-045 / third-party-data-sharing-consent Ask: What third parties do you currently share beneficiary data with, and what consent do you have? Answer: pick one Requirement type: privacy - Separate explicit consent for each third-party recipient [per-recipient-consent] - Category-based consent (consent for 'research partners' as group) [category-consent] - Broad consent (all third-party sharing approved in one consent) [broad-thirdparty] - Anonymous/de-identified (no consent needed) [deidentified-no-consent] - No third-party sharing (data stays internal) [no-sharing] #### UC-C-045 / consent-breach-notification Ask: What is your current process for handling and notifying beneficiaries of data breaches? Answer: pick one Requirement type: privacy - Mandatory beneficiary notification (immediately) [immediate-notification] - Delayed notification (only after investigation) [delayed-notification] - Notification if data actually misused (no notification for breach alone) [conditional-notification] - No notification obligation [no-notification] - Notification to authorities only (not beneficiary) [authority-notification] ### UC-C-046: Inter-agency data sharing without centralisation Security level: Higher. #### UC-C-046 / data-sharing-architecture Ask: What data systems do you currently use for sharing within and across organizations? Answer: pick one Requirement type: general - Through a central coordinating body that manages shared data [through-a-central-coordinating-body-that] - Direct sharing between organisations (bilateral agreements) [direct-sharing-between-organisations-bil] - Each organisation publishes data that others can access [each-organisation-publishes-data-that-ot] - Periodic manual sharing (email, USB, spreadsheets) [periodic-manual-sharing-email-usb-spread] - Combination of approaches depending on the data type [combination-of-approaches-depending-on-t] - No data sharing currently, each organisation works independently [no-data-sharing-currently-each-organisat] #### UC-C-046 / access-control-shared-data Ask: What access control model do you currently use for shared data? Answer: pick one Requirement type: privacy - Source agency controls (data owner decides who can access) [source-control] - Recipient agency controls (requester authenticated locally) [recipient-control] - Shared governance (both agencies must approve) [shared-governance] - Beneficiary-mediated (beneficiary grants access) [beneficiary-mediated] - No access control (open to all agencies) [no-access-control] #### UC-C-046 / data-sovereignty-residence Ask: What are your data residency and sovereignty requirements? Answer: pick one Requirement type: residency. Hard gate: yes - Data stays in country of origin (no cross-border export) [domestic-only] - Cross-border allowed but with explicit consent per country [cross-border-consent] - Regional data sharing with regional governance [regional-sharing] - Global sharing with local copies in-country [global-with-local] - Data mobility: beneficiary controls location [beneficiary-controlled] #### UC-C-046 / trust-framework Ask: What agreements or frameworks govern data sharing between your agencies? Answer: pick one Requirement type: integration - Government-backed accreditation (agencies licensed by government) [govt-accredited] - NGO/sector coalition (voluntary peer governance) [coalition-governance] - digital trust (digitally verified, no central authority) [blockchain-trust] - Mutual agreements (bilateral or trilateral contracts) [bilateral-agreements] - No formal trust framework (trust based on relationships) [no-framework] #### UC-C-046 / query-protocol-standard Ask: How do other agencies currently access or query your shared data? Answer: pick one Requirement type: integration - health data standard (health data standard with REST) [fhir-api] - flexible query (flexible query language) [graphql] - semantic query (semantic web standard) [sparql] - Custom protocol (agency-specific API) [custom-protocol] - Manual data export (periodic file exchange) [manual-export] #### UC-C-046 / audit-trail-sharing Ask: How do you currently track who accessed shared data and when? Answer: pick one Requirement type: audit-trail - Source agency logs (data owner logs all access) [source-logging] - Distributed logging (each agency logs their accesses) [distributed-logging] - Shared digital audit (permanent tamper-proof audit trail) [blockchain-audit] - End-to-end encryption with access notifications [encryption-notification] - No specific audit for shared access [no-audit] ### UC-C-047: Referral pathway tracking across service providers Security level: Higher. #### UC-C-047 / referral-tracking-mechanism Ask: How do you currently track referrals between service providers? Answer: pick one Requirement type: general - Shared referral registry (all referrals in central database) [shared-registry] - Digital tracking (permanent tamper-proof referral register) [blockchain-tracking] - Unique referral tokens (beneficiary carries proof) [referral-tokens] - Provider-to-provider notification (direct handoff) [direct-handoff] - Beneficiary self-reporting (no tracking system) [self-reporting] #### UC-C-047 / referral-completion-proof Ask: How do you currently document that a referral was completed? Answer: pick one Requirement type: audit-trail - Automated confirmation (recipient system sends confirmation) [automated-confirmation] - Manual confirmation (staff at recipient confirms) [manual-confirmation] - Beneficiary confirmation (beneficiary confirms service received) [beneficiary-confirmation] - Photo/video proof (evidence of service delivery) [photo-proof] - No completion verification [no-verification] #### UC-C-047 / follow-up-tracking Ask: How do you currently track follow-up actions on referrals? Answer: pick one Requirement type: integration - Automated follow-up (system triggers reminders) [automated-followup] - Manual follow-up (staff contacts beneficiary) [manual-followup] - Beneficiary self-reporting (outcome survey) [self-report] - Inter-provider follow-up (recipient provider reports outcome) [provider-report] - No follow-up tracking [no-followup] #### UC-C-047 / referral-data-consent Ask: What consent should govern referral data sharing between providers? Answer: pick one Requirement type: privacy - Broad consent (beneficiary consents to all provider sharing) [broad-consent] - Per-provider consent (consent for each provider separately) [per-provider-consent] - Just-in-time consent (ask at each referral) [jit-consent] - Implicit consent (service enrollment implies consent) [implicit-consent] - No consent requirement (service delivery overrides privacy) [no-consent] #### UC-C-047 / safe-referral-handling Ask: What is your current process for ensuring safe referrals? Answer: pick one Requirement type: privacy - Encrypted end-to-end (provider can't see data) [e2e-encrypted] - TLS in transit, encrypted at rest [standard-encryption] - Minimal data sharing (only essential info) [minimal-sharing] - Provider-specific redaction (hide sensitive fields) [redaction] - No encryption; trust network security [no-encryption] #### UC-C-047 / multi-provider-coordination Ask: How do you currently coordinate with multiple service providers on referrals? Answer: pick one Requirement type: integration - Linear referral chain (provider A → B → C) [linear-chain] - Hub-and-spoke (coordinator manages multiple referrals) [hub-spoke] - Parallel referrals (multiple providers simultaneously) [parallel] - Feedback loop (providers inform each other of outcomes) [feedback-loop] - No coordination (independent referrals) [no-coordination] #### UC-C-047 / referral-audit-trail Ask: How do you currently maintain an audit trail of referral activities? Answer: pick one Requirement type: audit-trail - Permanent tamper-proof referral ledger (digital ledger audit trail) [blockchain-ledger] - Timestamped audit log (each event logged with time) [audit-log] - Beneficiary path map (visual referral pathway) [journey-map] - Provider accountability log (who referred to whom) [accountability-log] - No audit trail (minimal documentation) [no-audit] #### UC-C-047 / beneficiary-choice Ask: How will beneficiaries exercise choice in how they receive and use this service? Answer: pick one Requirement type: privacy - Beneficiaries choose between delivery methods (cash, voucher, mobile money, direct) [delivery-choice] - Beneficiaries choose preferred merchants or service points [merchant-choice] - Beneficiaries control their own data sharing preferences [data-choice] - Multiple choice dimensions (delivery + merchant + data) [full-choice] - Limited choice: programme constraints determine delivery [limited] ### UC-C-048: Audit trail maintenance for compliance Security level: Standard. #### UC-C-048 / audit-trail-immutability Ask: What level of audit trail immutability would you need? Answer: pick one Requirement type: audit-trail - Append-only database (no deletion or modification) [append-only] - Digital anchoring (fingerprint on permanent tamper-proof register) [blockchain] - digitally verified chain (each log linked to previous) [hash-chain] - Hardware security module (HSM-protected signing) [hsm] - No specific immutability mechanism [none] #### UC-C-048 / audit-access-control Ask: Who should have access to audit logs? Answer: pick one Requirement type: privacy - Restricted to auditors and compliance team only [auditors-only] - Data subject (beneficiary) can view own access logs [data-subject] - Service administrator and supervisors [admin-supervisors] - External auditors and regulators [external] - No access control (audit logs public) [no-control] #### UC-C-048 / audit-retention Ask: How long should audit logs be retained? Answer: pick one Requirement type: privacy - Minimum: 1 year from last log entry [one-year] - Standard: 7 years for regulatory compliance [seven-years] - Extended: 10 years for medical records [ten-years] - Permanent: indefinite retention [permanent] - Minimal: deleted once audit complete [minimal] #### UC-C-048 / audit-reporting Ask: What audit reporting requirements do you have from donors or regulators? Answer: pick one Requirement type: audit-trail - Automated compliance reports (daily/weekly) [automated-reports] - Manual audit by compliance team (monthly) [manual-audit] - Red-flag alerting (immediate notification of violations) [red-flag-alerts] - Annual certification (third-party audit) [annual-cert] - No specific reporting (audit logs kept but not reviewed) [no-reporting] #### UC-C-048 / audit-trail-stakeholders Ask: How many distinct parties need visibility into the audit trail data? Answer: pick one Requirement type: audit-trail - Internal only (1–2 teams) [internal] - Internal + 1–3 external partners [few-external] - Multiple external stakeholders (4–10) [multi-external] - Ecosystem-wide (donors, partners, beneficiaries, regulators) [ecosystem] #### UC-C-048 / sq-UC-C-048-001 Ask: What retention and archival policy should apply to audit trail data? Answer: pick one Requirement type: legal-checks - 7-year minimum retention [7-year-minimum] - Donor-specific terms [donor-specific-terms] - Indefinite permanent tamper-proof storage [indefinite-immutable] - Tiered by sensitivity [tiered-by-sensitivity] - Regulatory minimum only [regulatory-minimum] ### UC-C-049: Research data with beneficiary privacy protection Security level: Higher. #### UC-C-049 / research-data-de-identification Ask: What de-identification method should protect research data? Answer: pick one Requirement type: privacy - Full anonymization (irreversible identifier removal) [full-anonymization] - Pseudonymization (reversible, keyed lookup) [pseudonymization] - Differential privacy (statistical noise added) [differential-privacy] - K-anonymity (indistinguishable within groups of k) [k-anonymity] - Data aggregation (group-level statistics only) [aggregation] #### UC-C-049 / ethics-approval-process Ask: What ethics review process should govern research use? Answer: pick one Requirement type: privacy - IRB/REC approval required before access [irb-approval] - Expedited review for low-risk research [expedited-review] - Data governance committee review [dgc-review] - Community consultation (community must approve) [community-consent] - No specific ethics requirement [no-ethics] #### UC-C-049 / secondary-use-restrictions Ask: What restrictions do you have on secondary uses of beneficiary data? Answer: pick one Requirement type: privacy - Purpose-limitation (data only for approved research) [purpose-limited] - Re-consent required (new consent for each use) [re-consent] - Broad consent (all research uses covered) [broad-research-consent] - Data marketplace (commercialization permitted) [data-marketplace] - No restrictions (open use) [open-use] #### UC-C-049 / publication-privacy Ask: What are your publication and privacy requirements for programme data? Answer: pick one Requirement type: privacy - Pre-publication review (check for identifiable data) [pre-publication] - De-identification verification (confirm anonymity) [deidentification-check] - External privacy review (third-party checks) [external-review] - Community review (community approves publication) [community-review] - No publication review [no-review] #### UC-C-049 / research-privacy-stakeholders Ask: How many distinct parties need visibility into the research data data? Answer: pick one Requirement type: privacy - Internal only (1–2 teams) [internal] - Internal + 1–3 external partners [few-external] - Multiple external stakeholders (4–10) [multi-external] - Ecosystem-wide (donors, partners, beneficiaries, regulators) [ecosystem] #### UC-C-049 / anonymisation-approach Ask: How should personal data be anonymised or protected? Answer: pick one Requirement type: privacy - Full data anonymisation (irreversible) [full-anonymisation] - Pseudonymisation (reversible by authorised parties) [pseudonymisation] - Differential privacy (statistical noise injection) [differential-privacy] - Selective redaction (remove specific identifiers) [selective-redaction] ### UC-C-050: Beneficiary feedback data integrity Security level: Standard. #### UC-C-050 / feedback-data-format Ask: What format do you currently use to collect and store feedback data? Answer: pick one Requirement type: integration - Structured surveys (standardized questionnaires) [structured-survey] - Free-text feedback (open narrative) [free-text] - Mixed (structured + free-text) [mixed-format] - Mobile-friendly short surveys [mobile-surveys] - Voice/video feedback (recorded) [voice-video] #### UC-C-050 / feedback-authenticity Ask: How do you currently verify that feedback is authentic? Answer: pick one Requirement type: audit-trail - Beneficiary authentication (biometric or PIN) [authentication] - Random sample verification (call back and verify) [sample-verification] - Timestamp with location (GPS proof) [timestamp-location] - Digital timestamping (permanent tamper-proof proof) [blockchain-timestamp] - No verification (trust feedback) [no-verification] #### UC-C-050 / feedback-anonymity Ask: Should beneficiary feedback be anonymous or identified? Answer: pick one Requirement type: privacy - Fully anonymous (no identification possible) [fully-anonymous] - Pseudonymous (coded identifier, linked separately) [pseudonymous] - Identified (attribution to beneficiary) [identified] - Optional: beneficiary chooses [optional] - Anonymous in reporting (identified internally only) [reporting-anon] #### UC-C-050 / feedback-manipulation-prevention Ask: What is your current approach to preventing feedback manipulation? Answer: pick one Requirement type: audit-trail - Multiple feedback rounds (cross-check consistency) [multiple-rounds] - Machine learning anomaly detection (flag suspicious patterns) [ml-detection] - Independent collectors (no staff collecting from own beneficiaries) [independent-collectors] - Third-party verification (external evaluators) [third-party] - No specific protection (assume honesty) [no-protection] #### UC-C-050 / beneficiary-feedback-stakeholders Ask: How many distinct parties need visibility into the beneficiary feedback data data? Answer: pick one Requirement type: usability - Internal only (1–2 teams) [internal] - Internal + 1–3 external partners [few-external] - Multiple external stakeholders (4–10) [multi-external] - Ecosystem-wide (donors, partners, beneficiaries, regulators) [ecosystem] #### UC-C-050 / beneficiary-choice Ask: How will beneficiaries exercise choice in how they receive and use this service? Answer: pick one Requirement type: privacy - Beneficiaries choose between delivery methods (cash, voucher, mobile money, direct) [delivery-choice] - Beneficiaries choose preferred merchants or service points [merchant-choice] - Beneficiaries control their own data sharing preferences [data-choice] - Multiple choice dimensions (delivery + merchant + data) [full-choice] - Limited choice: programme constraints determine delivery [limited] ### UC-C-051: Needs assessment data integrity Security level: Standard. #### UC-C-051 / needs-assessment-data-collection Ask: How do you currently collect and store needs assessment data? Answer: pick one Requirement type: general - Offline-first mobile app (collect without connectivity) [offline-mobile] - Web-based platform (cloud-based, real-time) [web-platform] - Paper forms with digital transcription [paper-digital] - Oral interviews with transcript [oral-interviews] - Hybrid (multiple collection methods) [hybrid-collection] #### UC-C-051 / assessment-authenticity Ask: How do you currently verify the authenticity of needs assessment data? Answer: pick one Requirement type: audit-trail - Consistency checks (compare against other surveys) [consistency-checks] - Beneficiary re-interview (verify responses) [reinterview] - Community cross-checks (community confirms data) [community-checks] - Sensor verification (e.g., measure income via WiFi access) [sensor-verify] - No verification (trust data as submitted) [no-verification] #### UC-C-051 / assessment-data-retention Ask: How long should needs assessment data be retained? Answer: pick one Requirement type: privacy - Until program ends (then delete) [program-duration] - 2-3 years for impact evaluation [three-years] - 5-7 years for audit and compliance [five-years] - Permanent archival for longitudinal research [permanent] - Beneficiary-controlled (beneficiary can request deletion) [beneficiary-controlled] #### UC-C-051 / needs-assessment-stakeholders Ask: How many distinct parties need visibility into the needs assessment data data? Answer: pick one Requirement type: usability - Internal only (1–2 teams) [internal] - Internal + 1–3 external partners [few-external] - Multiple external stakeholders (4–10) [multi-external] - Ecosystem-wide (donors, partners, beneficiaries, regulators) [ecosystem] #### UC-C-051 / sq-UC-C-051-003 Ask: What cross-validation should be applied to needs assessment responses? Answer: pick one Requirement type: general - Triangulation with secondary data [triangulation-with-secondary-data] - Household revisit [household-revisit] - Community validation [community-validation] - Statistical outlier detection [statistical-outlier-detection] - Enumerator cross-check [enumerator-cross-check] #### UC-C-051 / audit-mechanism-approach Ask: How should auditing and verification work for this solution? Answer: pick one Requirement type: audit-trail - Automatic checks that flag problems as they happen [automated-realtime] - Regular scheduled reviews with tamper-proof records [periodic-batch] - Ability to check any record at any time with proof it has not been altered [on-demand] - External auditors can log in and review records independently [third-party] #### UC-C-051 / beneficiary-choice Ask: How will beneficiaries exercise choice in how they receive and use this service? Answer: pick one Requirement type: privacy - Beneficiaries choose between delivery methods (cash, voucher, mobile money, direct) [delivery-choice] - Beneficiaries choose preferred merchants or service points [merchant-choice] - Beneficiaries control their own data sharing preferences [data-choice] - Multiple choice dimensions (delivery + merchant + data) [full-choice] - Limited choice: programme constraints determine delivery [limited] ### UC-C-052: Whistleblower and reporting channel integrity Security level: Standard. #### UC-C-052 / wb-identity-model Ask: What identity model applies to reports? Answer: pick one Requirement type: credentials - Fully anonymous (no identity at all) [anon] - Pseudonymous (organisation-blind but consistent reporter identity for follow-up) [pseudonymous] - Verified reporter with identity shielded from investigator until escalation [verified-shielded] #### UC-C-052 / wb-channel-integrity-level Ask: What integrity guarantees does the channel need? Answer: pick one Requirement type: audit-trail - Hash-anchored submission log [hash] - Hash + deliverability proof (investigator cannot deny receipt) [deliverability] - Full end-to-end cryptographic integrity (submission, deliverability, retention, tamper-evidence) [full] #### UC-C-052 / wb-retention Ask: What retention policy applies? Answer: pick one Requirement type: privacy - Short (< 12 months, basic compliance) [short] - Medium (12-60 months, typical EU Directive) [medium] - Long (indefinite for safeguarding / ongoing investigations) [long] #### UC-C-052 / wb-investigator-model Ask: Who investigates submitted reports? Answer: pick one Requirement type: general - Internal only [internal] - External independent party [external] - Tiered (internal first, external escalation) [tiered] #### UC-C-052 / wb-cross-org Ask: Do reports need to be routable to other agencies (consortium-wide whistleblowing)? Answer: pick one Requirement type: general - No, single-org channel [single] - Yes, consortium-wide common channel [consortium] - Yes, with external-oversight escalation (regulator, ombudsman) [oversight] ### UC-C-053: Livestock traceability for pastoralists Security level: Standard. #### UC-C-053 / herd-scale Ask: How many animals will the system cover? Answer: pick one Requirement type: scale - Fewer than 1,000 animals [under-1000] - 1,000 to 10,000 animals [1k-10k] - 10,000 to 100,000 animals [10k-100k] - Over 100,000 animals [over-100k] #### UC-C-053 / tagging-method Ask: How will each animal be tagged? Answer: pick one Requirement type: devices - Printed ear tag with batch ID [ear-tag-printed] - Rumen RFID bolus [rfid-bolus] - Electronic ear tag (RFID) [rfid-eartag] - Muzzle biometric capture [muzzle-biometric] #### UC-C-053 / cross-border-corridors Ask: Do animals cross borders on their way to market? Answer: pick one Requirement type: money - Operations are not cross-border [none] - Two neighbouring states [two-states] - Three or more neighbouring states [three-plus] - Cross-border movement passes through contested or active-conflict zones [contested] #### UC-C-053 / attestation-authority Ask: Who will vouch for an animal's records? Answer: pick all that apply Requirement type: credentials - Government veterinary service [vet-service] - Cooperative or producer association [cooperative] - Implementing CSO [ngo] - Private veterinary practitioners [private-vet] - Livestock market authority [market-authority] #### UC-C-053 / market-destination Ask: Where do the animals end up for sale? Answer: pick one Requirement type: general - Local markets only [local-only] - National markets and slaughter [national] - Regional export (Gulf, neighbouring states) [regional-export] - Global export with halal certification [global-export] #### UC-C-053 / insurance-bundled Ask: Will livestock insurance be part of this? Answer: pick one Requirement type: money - No insurance bundled [no] - Planning to add insurance later [planned] - Yes, parametric livestock insurance [yes-parametric] - Yes, indemnity insurance with attested loss [yes-indemnity] #### UC-C-053 / connectivity-field Ask: What phone and data access do people have at field sites? Answer: pick one Requirement type: offline - Smartphone with mobile data at field sites [smartphone-data] - Smartphone with SMS only at field sites [smartphone-sms] - Feature phone (USSD/SMS) only [feature-phone] - Mostly offline, data uploaded at urban hubs [offline-only] #### UC-C-053 / data-minimisation-position Ask: How much data about animals and households should be recorded? Answer: pick one Requirement type: privacy - Strict, only animal-level data on-chain, no household location [strict] - Aggregated cooperative-level data on-chain [aggregated] - Animal + household + grazing-route data on-chain [full-context] - Not yet decided, needs threat model [undecided] #### UC-C-053 / vaccination-integration Ask: How should vaccination records fit in? Answer: pick one Requirement type: integration - No vaccination integration [none] - Manual logging of vaccination events [manual] - Integrated with national vaccination campaign system [integrated] - Integrated with FAO / AU-IBAR programmes [integrated-fao] ### UC-C-054: Seed system integrity Security level: Higher. #### UC-C-054 / crop-type Ask: Which crops does this cover? Answer: pick all that apply Requirement type: general - Hybrid cereals (maize, rice, sorghum hybrids) [hybrid-cereals] - Certified pulses (improved beans, lentils) [certified-pulses] - Vegetable hybrids [vegetable-hybrids] - Traditional / open-pollinated varieties [traditional] - Cash crops (cotton, coffee, tobacco) [cash-crop] #### UC-C-054 / counterfeit-severity Ask: How big is the problem of fake seed? Answer: pick one Requirement type: general - Not a material problem in our context [not-material] - Emerging concern [emerging] - Recurring problem affecting yield [recurring] - Widespread: major cause of yield failure [widespread] #### UC-C-054 / certification-authority Ask: Is there a seed certification body you can work with? Answer: pick one Requirement type: credentials - National seed certification body engaged [national-engaged] - National authority receptive but not yet engaged [national-receptive] - Private certification (e.g. seed company internal) [private] - No certification authority available, would need to establish [none] #### UC-C-054 / batch-marking Ask: How will each seed batch be marked? Answer: pick one Requirement type: money - Printed batch code on packaging [printed-code] - QR code on packaging [qr-code] - NFC tag on packaging [nfc] - Tamper-evident packaging with cryptographic seal [tamper-evident] #### UC-C-054 / intermediate-attestation-coverage Ask: Who in the supply chain confirms the seed on its way to the farmer? Answer: pick one Requirement type: credentials - Certification authority only [certifier-only] - Certification + wholesaler [certifier-wholesaler] - Certification + wholesaler + retailer [full-chain] - Full chain + cooperative branch [full-plus-coop] #### UC-C-054 / farmer-verification-method Ask: How will farmers check that their seed is genuine? Answer: pick one Requirement type: credentials - SMS verification (text the code) [sms] - USSD code lookup [ussd] - QR scan with smartphone [qr-smartphone] - Extension officer verifies on farmer's behalf [extension-officer] #### UC-C-054 / agro-dealer-network Ask: What kind of dealers sell the seed? Answer: pick one Requirement type: general - Formal national network [formal] - Cooperative-led retail [cooperative-led] - Informal retail (markets, individual sellers) [informal] - Mixed formal + informal [mixed] #### UC-C-054 / counterfeit-response-process Ask: What happens now when fake seed is found? Answer: pick one Requirement type: general - No formal process [none] - Internal CSO follow-up [internal-only] - Refer to regulator [regulatory-referral] - Public recall and regulator referral [public-recall] ### UC-D-052: Medicine authenticity verification (anti-counterfeiting) Security level: Standard. #### UC-D-052 / medicine-tracking-granularity Ask: At what granularity level do you currently track medicines in your supply chain? Answer: pick one Requirement type: audit-trail - Individual unit/blister pack [individual-unit] - Batch/lot level [batch-level] - Carton/case level [carton-level] #### UC-D-052 / verification-points-count Ask: How many verification points are currently in your medicine supply chain? Answer: pick one Requirement type: scale - 2-3 critical verification points [minimal-points] - 5-7 verification points [moderate-points] - 10+ verification points throughout supply chain [comprehensive-points] #### UC-D-052 / counterfeit-risk-level Ask: What is your assessed counterfeit risk level for your medicines? Answer: pick one Requirement type: general - Low risk - established manufacturers [low-risk] - Medium risk - variable supplier base [medium-risk] - High risk - known counterfeiting areas [high-risk] #### UC-D-052 / reporting-requirements Ask: What reporting and audit requirements must be met? Answer: pick one Requirement type: audit-trail - Basic inventory and distribution reporting [basic-reporting] - Regulatory compliance reporting [regulatory-reporting] - Real-time transparency and stakeholder reporting [realtime-reporting] #### UC-D-052 / item-tracking-method Ask: How will physical items be tracked and scanned in the field? Answer: pick one Requirement type: devices - QR codes printed on items or packaging [qr-codes] - NFC tags embedded in items [nfc-tags] - Barcode labels with batch scanning [barcode] - Mixed: QR for high-value items, barcode for bulk [mixed] ### UC-D-053: Cold chain monitoring for vaccines and medicines Security level: Standard. #### UC-D-053 / cold-chain-temperature-requirement Ask: What temperature range must be maintained for your cold chain? Answer: pick one Requirement type: devices - Standard 2-8°C refrigeration [standard-2-8] - Ultra-cold -20°C to -30°C [ultra-cold-20-30] - Ultra-cold -60°C to -80°C (mRNA vaccines) [ultra-cold-60-80] #### UC-D-053 / iot-sensor-type-selection Ask: Which IoT sensor type is most suitable for vaccine monitoring? Answer: pick one Requirement type: devices - Passive temperature data loggers [passive-loggers] - Active IoT sensors with wireless connectivity [active-iot-sensors] - Hybrid sensors with digital ledger integration [hybrid-blockchain-sensors] #### UC-D-053 / alert-mechanism-type Ask: What alert mechanism do you currently use for vaccine delivery issues? Answer: pick one Requirement type: credentials - SMS and email notifications [sms-email-alerts] - In-app push notifications and dashboard alerts [app-dashboard-alerts] - Automated escalation with supervisor notification [automated-escalation] #### UC-D-053 / health-system-integration Ask: What health system do you currently integrate with for vaccine delivery? Answer: pick one Requirement type: integration - Manual data entry and reporting [manual-integration] - API integration with existing HIS systems [api-integration] - Full synchronisation with national health databases [full-sync-national] #### UC-D-053 / vaccine-lot-tracking-method Ask: How do you currently track vaccine lots in your programmes? Answer: pick one Requirement type: audit-trail - Manual batch records and documentation [manual-records] - Barcode/QR scanning with digital tracking [barcode-tracking] - Tamper-proof digital lot tracking [blockchain-lots] #### UC-D-053 / quality-assurance-cold-chain Ask: What quality assurance mechanisms should verify cold chain integrity? Answer: pick one Requirement type: general - Visual indicators and manual inspections [visual-inspection] - Automated sensor verification with reports [automated-verification] - Real-time monitoring with predictive analytics [predictive-analytics] #### UC-D-053 / cold-chain-documentation Ask: How do you currently document cold-chain compliance? Answer: pick one Requirement type: audit-trail - Paper-based temperature logs [paper-logs] - Digital records with audit trails [digital-records] - Tamper-proof digital records [blockchain-records] #### UC-D-053 / sq-UC-D-053-001 Ask: What regulatory reporting is required for cold chain excursions? Answer: pick one Requirement type: legal-checks - National health authority [national-health-authority] - WHO PQS [who-pqs] - GAVI [gavi] - Donor-specific requirements [donor-specific] - Internal only [internal-only] ### UC-D-055: Nutrition supplement tracking Security level: Standard. #### UC-D-055 / distribution-model-type Ask: What is your primary distribution model? Answer: pick one Requirement type: audit-trail - Direct distribution from central warehouse [direct-distribution] - Multi-tier distribution through partners [multi-tier-distribution] - Community health worker led distribution [chw-distribution] #### UC-D-055 / beneficiary-verification-method Ask: What is your current method for verifying beneficiary identity? Answer: pick one Requirement type: credentials - Manual signature or thumbprint on receipt [manual-receipt] - Digital confirmation via mobile phone [digital-confirmation] - Biometric verification with photo documentation [biometric-verification] #### UC-D-055 / compliance-tracking Ask: What compliance requirements must be tracked? Answer: pick one Requirement type: legal-checks - Basic inventory and distribution logs [basic-compliance] - Nutritional outcome tracking and impact metrics [outcome-tracking] - Regulatory compliance with quality and safety standards [regulatory-compliance] #### UC-D-055 / nutrition-reporting-stakeholder Ask: Who needs to receive distribution and impact reports? Answer: pick one Requirement type: audit-trail - Internal management only [internal-only] - Donors and implementing partners [donors-partners] - Full transparency to all stakeholders including beneficiaries [full-transparency] #### UC-D-055 / nutrition-stakeholders Ask: How many distinct parties need visibility into the nutrition supply chain data? Answer: pick one Requirement type: usability - Internal only (1–2 teams) [internal] - Internal + 1–3 external partners [few-external] - Multiple external stakeholders (4–10) [multi-external] - Ecosystem-wide (donors, partners, beneficiaries, regulators) [ecosystem] #### UC-D-055 / item-tracking-method Ask: How will physical items be tracked and scanned in the field? Answer: pick one Requirement type: devices - QR codes printed on items or packaging [qr-codes] - NFC tags embedded in items [nfc-tags] - Barcode labels with batch scanning [barcode] - Mixed: QR for high-value items, barcode for bulk [mixed] #### UC-D-055 / inventory-integration Ask: How are inventory and stock levels currently tracked? Answer: pick one Requirement type: integration - Integration with existing warehouse management system [wms-integration] - Standalone digital ledger inventory ledger [standalone] - Spreadsheet-based with digital verification layer [spreadsheet-bridge] - Not sure, need guidance [guidance-needed] #### UC-D-055 / audit-mechanism-approach Ask: How should auditing and verification work for this solution? Answer: pick one Requirement type: audit-trail - Automatic checks that flag problems as they happen [automated-realtime] - Regular scheduled reviews with tamper-proof records [periodic-batch] - Ability to check any record at any time with proof it has not been altered [on-demand] - External auditors can log in and review records independently [third-party] ### UC-D-056: Food aid tracking from source to beneficiary Security level: Standard. #### UC-D-056 / supply-chain-length Ask: What is the length of your food aid supply chain? Answer: pick one Requirement type: audit-trail - Short chain (2-3 hops: source, warehouse, beneficiary) [short-chain] - Medium chain (4-6 hops: source, port, warehouse, district, health center, beneficiary) [medium-chain] - Long chain (7+ hops: international, port, regional, district, local, partner, beneficiary) [long-chain] #### UC-D-056 / food-tracking-granularity Ask: At what granularity should food aid be tracked? Answer: pick one Requirement type: audit-trail - Container/shipment level [container-level] - Batch/commodity lot level [batch-level] - Individual package/ration level [package-level] #### UC-D-056 / food-quality-monitoring Ask: How do you currently monitor food quality in your supply chain? Answer: pick one Requirement type: general - Manual visual inspections at checkpoints [visual-inspection] - Temperature and humidity monitoring with IoT sensors [iot-monitoring] - Continuous quality assurance with testing protocols [continuous-qa] #### UC-D-056 / donor-transparency-level Ask: What level of transparency should donors have? Answer: pick one Requirement type: audit-trail - Post-delivery reporting only [post-delivery] - Real-time updates at major checkpoints [realtime-checkpoints] - Complete end-to-end visibility with beneficiary verification [complete-visibility] #### UC-D-056 / last-mile-food-verification Ask: How do you currently verify food quality at the point of distribution? Answer: pick one Requirement type: credentials - Manual handover documentation with signature [manual-handover] - Digital receipt with beneficiary ID and timestamp [digital-receipt] - Biometric verification with photo and location confirmation [biometric-verification] #### UC-D-056 / food-source-verification Ask: How do you currently verify the source of your food supplies? Answer: pick one Requirement type: credentials - Supplier documentation and invoices [documentation] - Digital tracking from farm/producer [blockchain-tracking] - Third-party certification and inspection [third-party-cert] #### UC-D-056 / item-tracking-method Ask: How will physical items be tracked and scanned in the field? Answer: pick one Requirement type: devices - QR codes printed on items or packaging [qr-codes] - NFC tags embedded in items [nfc-tags] - Barcode labels with batch scanning [barcode] - Mixed: QR for high-value items, barcode for bulk [mixed] ### UC-D-057: Donated goods provenance verification Security level: Standard. #### UC-D-057 / donation-types-accepted Ask: What types of donated goods do you accept? Answer: pick one Requirement type: audit-trail - Single category (e.g., medical supplies only) [single-category] - Multiple categories (medicines, equipment, supplies) [multiple-categories] - Mixed and unstructured donations [mixed-donations] #### UC-D-057 / provenance-verification-depth Ask: How deep should provenance verification go? Answer: pick one Requirement type: audit-trail - Donor name and date only [donor-basic] - Donor verification plus manufacturing information [donor-plus-mfg] - Complete origin traceability from manufacturer [complete-origin] #### UC-D-057 / donated-goods-volume Ask: What is the monthly volume of donated goods you need to track? Answer: pick one Requirement type: scale - Under 1,000 items [small] - 1,000–10,000 items [medium] - 10,000–100,000 items [large] - Over 100,000 items [enterprise] #### UC-D-057 / donated-goods-stakeholders Ask: How many distinct parties need visibility into the donated goods provenance data? Answer: pick one Requirement type: usability - Internal only (1–2 teams) [internal] - Internal + 1–3 external partners [few-external] - Multiple external stakeholders (4–10) [multi-external] - Ecosystem-wide (donors, partners, beneficiaries, regulators) [ecosystem] #### UC-D-057 / item-tracking-method Ask: How will physical items be tracked and scanned in the field? Answer: pick one Requirement type: devices - QR codes printed on items or packaging [qr-codes] - NFC tags embedded in items [nfc-tags] - Barcode labels with batch scanning [barcode] - Mixed: QR for high-value items, barcode for bulk [mixed] #### UC-D-057 / audit-mechanism-approach Ask: How should auditing and verification work for this solution? Answer: pick one Requirement type: audit-trail - Automatic checks that flag problems as they happen [automated-realtime] - Regular scheduled reviews with tamper-proof records [periodic-batch] - Ability to check any record at any time with proof it has not been altered [on-demand] - External auditors can log in and review records independently [third-party] ### UC-D-058: In-kind donation tracking and valuation Security level: Standard. #### UC-D-058 / donation-valuation-method Ask: Which valuation method should be used for donated goods? Answer: pick one Requirement type: audit-trail - Fair market value at time of donation [fair-market-value] - Replacement cost in programme location [replacement-cost] - Cost as assessed by independent appraiser [independent-appraisal] #### UC-D-058 / accounting-system-integration Ask: What accounting system do you currently use for supply chain tracking? Answer: pick one Requirement type: integration - Manual entry into accounting ledgers [manual-entry] - Automated integration with bookkeeping software [api-integration] - Real-time digital ledger-based accounting [blockchain-accounting] #### UC-D-058 / donor-impact-reporting Ask: What donor reporting should show impact of donations? Answer: pick one Requirement type: audit-trail - Financial receipt and valuation only [financial-receipt] - Usage tracking and programme allocation [usage-tracking] - Impact measurement with beneficiary outcomes [impact-measurement] #### UC-D-058 / in-kind-stakeholders Ask: How many distinct parties need visibility into the in-kind donation data? Answer: pick one Requirement type: usability - Internal only (1–2 teams) [internal] - Internal + 1–3 external partners [few-external] - Multiple external stakeholders (4–10) [multi-external] - Ecosystem-wide (donors, partners, beneficiaries, regulators) [ecosystem] #### UC-D-058 / inventory-integration Ask: How are inventory and stock levels currently tracked? Answer: pick one Requirement type: integration - Integration with existing warehouse management system [wms-integration] - Standalone digital ledger inventory ledger [standalone] - Spreadsheet-based with digital verification layer [spreadsheet-bridge] - Not sure, need guidance [guidance-needed] #### UC-D-058 / audit-mechanism-approach Ask: How should auditing and verification work for this solution? Answer: pick one Requirement type: audit-trail - Automatic checks that flag problems as they happen [automated-realtime] - Regular scheduled reviews with tamper-proof records [periodic-batch] - Ability to check any record at any time with proof it has not been altered [on-demand] - External auditors can log in and review records independently [third-party] #### UC-D-058 / reporting-approach Ask: What reporting capabilities does this solution need? Answer: pick one Requirement type: audit-trail - Automated donor/funder reporting with scheduled delivery [automated-donor] - Self-service dashboard with custom report builder [self-service] - Regulatory compliance reporting (government/authority) [regulatory] - Multi-audience reporting (donors, government, community) [multi-audience] ### UC-D-059: Shelter materials and non-food item tracking Security level: Standard. #### UC-D-059 / shelter-nfi-item-types Ask: What types of shelter and NFI items are tracked? Answer: pick one Requirement type: general - Shelter materials only [shelter-only] - NFI core items (blankets, mats, pots) [nfi-core] - Extended NFI (tools, hygiene, cooking, lighting) [nfi-extended] #### UC-D-059 / nfi-distribution-model Ask: How are shelter/NFI items distributed to beneficiaries? Answer: pick one Requirement type: audit-trail - Centralized distribution events [centralized-events] - Partner organization distribution [partner-distribution] - Community-based distribution networks [community-networks] #### UC-D-059 / nfi-beneficiary-verification Ask: How are beneficiaries verified at distribution? Answer: pick one Requirement type: credentials - Name and ID check against list [name-id-check] - Digital beneficiary registry with mobile verification [digital-registry] - Biometric verification with photo ID [biometric-id] #### UC-D-059 / nfi-replenishment-planning Ask: How do you currently plan and track NFI replenishment? Answer: pick one Requirement type: general - Manual reordering based on stock checks [manual-reorder] - Automated alerts at reorder point [automated-alerts] - Predictive demand forecasting [predictive-demand] #### UC-D-059 / shelter-nfi-stakeholders Ask: How many distinct parties need visibility into the shelter and NFI distribution data? Answer: pick one Requirement type: usability - Internal only (1–2 teams) [internal] - Internal + 1–3 external partners [few-external] - Multiple external stakeholders (4–10) [multi-external] - Ecosystem-wide (donors, partners, beneficiaries, regulators) [ecosystem] #### UC-D-059 / item-tracking-method Ask: How will physical items be tracked and scanned in the field? Answer: pick one Requirement type: devices - QR codes printed on items or packaging [qr-codes] - NFC tags embedded in items [nfc-tags] - Barcode labels with batch scanning [barcode] - Mixed: QR for high-value items, barcode for bulk [mixed] #### UC-D-059 / audit-mechanism-approach Ask: How should auditing and verification work for this solution? Answer: pick one Requirement type: audit-trail - Automatic checks that flag problems as they happen [automated-realtime] - Regular scheduled reviews with tamper-proof records [periodic-batch] - Ability to check any record at any time with proof it has not been altered [on-demand] - External auditors can log in and review records independently [third-party] ### UC-D-060: Water, sanitation and hygiene supplies verification Security level: Standard. #### UC-D-060 / wash-supply-types Ask: Which WASH supply categories are covered? Answer: pick one Requirement type: general - Water supply systems only [water-only] - Water and sanitation supplies [water-sanitation] - Comprehensive WASH (water, sanitation, hygiene) [comprehensive-wash] #### UC-D-060 / wash-quality-testing Ask: What quality testing is required for WASH supplies? Answer: pick one Requirement type: general - Visual inspection only [visual-test] - Basic functionality testing [functionality-test] - Laboratory water quality testing [lab-testing] #### UC-D-060 / wash-distribution-model Ask: What distribution model is used for WASH supplies? Answer: pick one Requirement type: audit-trail - Centralized warehouse distribution [centralized-warehouse] - Hub-and-spoke network distribution [hub-and-spoke] - Community-based distribution [community-based] #### UC-D-060 / wash-volume Ask: What is the monthly volume of WASH supplies you need to track? Answer: pick one Requirement type: scale - Under 1,000 items [small] - 1,000–10,000 items [medium] - 10,000–100,000 items [large] - Over 100,000 items [enterprise] #### UC-D-060 / wash-stakeholders Ask: How many distinct parties need visibility into the WASH supply chain data? Answer: pick one Requirement type: usability - Internal only (1–2 teams) [internal] - Internal + 1–3 external partners [few-external] - Multiple external stakeholders (4–10) [multi-external] - Ecosystem-wide (donors, partners, beneficiaries, regulators) [ecosystem] #### UC-D-060 / sq-UC-D-060-001 Ask: What water quality testing results should be linked to WASH supply distribution records? Answer: pick one Requirement type: general - Point-of-use testing [point-of-use-testing] - Source water testing [source-testing] - Distribution point testing [distribution-point-testing] - No water testing [no-water-testing] - Periodic sampling [periodic-sampling] #### UC-D-060 / item-tracking-method Ask: How will physical items be tracked and scanned in the field? Answer: pick one Requirement type: devices - QR codes printed on items or packaging [qr-codes] - NFC tags embedded in items [nfc-tags] - Barcode labels with batch scanning [barcode] - Mixed: QR for high-value items, barcode for bulk [mixed] ### UC-D-061: Equipment and asset lifecycle tracking Security level: Standard. #### UC-D-061 / asset-types-classification Ask: How do you currently classify and categorize assets in your programme? Answer: pick one Requirement type: general - Single asset category [single-category] - Multiple categories (medical, vehicles, generators) [multiple-categories] - Hierarchical classification with detailed sub-categories [hierarchical-classification] #### UC-D-061 / asset-maintenance-tracking Ask: How do you currently track asset maintenance? Answer: pick one Requirement type: general - Manual maintenance log kept with asset [manual-log] - Digital maintenance schedule and records [digital-schedule] - Predictive maintenance with IoT sensors [predictive-maintenance] #### UC-D-061 / asset-custody-chain Ask: How do you currently track who has custody of assets as they move through your supply chain? Answer: pick one Requirement type: audit-trail - Single custodian per asset location [single-custodian] - Custodian transfer log [transfer-log] - Real-time tracking with location history [realtime-tracking] #### UC-D-061 / item-tracking-method Ask: How will physical items be tracked and scanned in the field? Answer: pick one Requirement type: devices - QR codes printed on items or packaging [qr-codes] - NFC tags embedded in items [nfc-tags] - Barcode labels with batch scanning [barcode] - Mixed: QR for high-value items, barcode for bulk [mixed] #### UC-D-061 / audit-mechanism-approach Ask: How should auditing and verification work for this solution? Answer: pick one Requirement type: audit-trail - Automatic checks that flag problems as they happen [automated-realtime] - Regular scheduled reviews with tamper-proof records [periodic-batch] - Ability to check any record at any time with proof it has not been altered [on-demand] - External auditors can log in and review records independently [third-party] ### UC-D-062: Fleet and vehicle management Security level: Standard. #### UC-D-062 / fleet-size-scale Ask: What is the size of your fleet? Answer: pick one Requirement type: scale - Small fleet (1-5 vehicles) [small-fleet] - Medium fleet (6-30 vehicles) [medium-fleet] - Large fleet (30+ vehicles) [large-fleet] #### UC-D-062 / vehicle-tracking-requirements Ask: What vehicle tracking data is required? Answer: pick one Requirement type: devices - GPS location tracking only [gps-only] - GPS plus fuel and maintenance data [gps-fuel-maintenance] - Comprehensive telematics (GPS, fuel, maintenance, driver behavior) [full-telematics] #### UC-D-062 / driver-management-level Ask: What level of driver management is required? Answer: pick one Requirement type: audit-trail - Basic driver registry and license tracking [basic-registry] - Driver performance monitoring and training [performance-monitoring] - Advanced driver assessment with behavior analytics [advanced-analytics] #### UC-D-062 / fleet-size Ask: How many vehicles are in the fleet to be tracked? Answer: pick one Requirement type: scale - Under 20 vehicles [small] - 20–100 vehicles [medium] - 100–500 vehicles [large] - Over 500 vehicles [enterprise] #### UC-D-062 / sq-UC-D-062-001 Ask: What fuel management and anti-theft measures do you currently have? Answer: pick one Requirement type: general - Fuel card tracking [fuel-card-tracking] - GPS geofencing [gps-geofence] - Driver ID matching [driver-id-match] - Consumption anomaly detection [consumption-anomaly-detection] - Manual log only [manual-log-only] #### UC-D-062 / sq-UC-D-062-003 Ask: What maintenance scheduling approach do you currently use? Answer: pick one Requirement type: general - Mileage-based [mileage-based] - Time-based [time-based] - Predictive from telematics [predictive-from-telematics] - Driver-reported [driver-reported] - Hybrid mileage and condition [hybrid-mileage-and-condition] #### UC-D-062 / iot-sensor-approach Ask: What type of sensor or data collection devices will be used? Answer: pick one Requirement type: devices - GPS/location tracking devices [gps-location] - Environmental sensors (temperature, humidity, etc.) [environmental] - Smart meters (energy, water usage) [smart-meters] - Mobile phone-based data collection (photos, GPS, manual entry) [mobile-collection] #### UC-D-062 / audit-mechanism-approach Ask: How should auditing and verification work for this solution? Answer: pick one Requirement type: audit-trail - Automatic checks that flag problems as they happen [automated-realtime] - Regular scheduled reviews with tamper-proof records [periodic-batch] - Ability to check any record at any time with proof it has not been altered [on-demand] - External auditors can log in and review records independently [third-party] ### UC-D-063: Last-mile delivery verification Security level: Standard. #### UC-D-063 / delivery-verification-method Ask: Which verification method should be used for delivery? Answer: pick one Requirement type: credentials - Signature or thumbprint on receipt [signature-receipt] - QR code scanning by beneficiary [qr-scanning] - Biometric verification with photo [biometric-photo] #### UC-D-063 / beneficiary-id-system Ask: How are beneficiaries identified and registered? Answer: pick one Requirement type: integration - Basic list with name and location [basic-list] - Digital registry with unique ID [digital-id] - Biometric registry with multi-modal data [biometric-registry] #### UC-D-063 / delivery-scale-volume Ask: What is the expected delivery volume? Answer: pick one Requirement type: scale - Small scale (< 1000 deliveries/month) [small-scale] - Medium scale (1000-10000 deliveries/month) [medium-scale] - Large scale (10000+ deliveries/month) [large-scale] #### UC-D-063 / fraud-prevention-mechanism Ask: What approach would you need for preventing and detecting supply chain fraud? Answer: pick one Requirement type: general - Documentation and random spot checks [spot-checks] - Digital verification with supervisor review [digital-review] - Real-time monitoring with digital ledger confirmation [blockchain-monitoring] #### UC-D-063 / last-mile-stakeholders Ask: How many distinct parties need visibility into the last-mile delivery data? Answer: pick one Requirement type: usability - Internal only (1–2 teams) [internal] - Internal + 1–3 external partners [few-external] - Multiple external stakeholders (4–10) [multi-external] - Ecosystem-wide (donors, partners, beneficiaries, regulators) [ecosystem] #### UC-D-063 / item-tracking-method Ask: How will physical items be tracked and scanned in the field? Answer: pick one Requirement type: devices - QR codes printed on items or packaging [qr-codes] - NFC tags embedded in items [nfc-tags] - Barcode labels with batch scanning [barcode] - Mixed: QR for high-value items, barcode for bulk [mixed] ### UC-D-064: Local procurement verification Security level: Standard. #### UC-D-064 / vendor-verification-depth Ask: How deep should vendor verification be? Answer: pick one Requirement type: credentials - Basic registration and business verification [basic-verification] - Financial and compliance screening [compliance-screening] - Comprehensive due diligence with site visits [comprehensive-due-diligence] #### UC-D-064 / local-sourcing-requirement Ask: What local sourcing requirement should be enforced? Answer: pick one Requirement type: audit-trail - No specific requirement (open market) [open-market] - Preference for local vendors (20-50%) [preference] - Mandate for local sourcing (70-100%) [mandate] #### UC-D-064 / local-proc-volume Ask: What is the monthly volume of local procurement transactions you need to track? Answer: pick one Requirement type: scale - Under 1,000 items [small] - 1,000–10,000 items [medium] - 10,000–100,000 items [large] - Over 100,000 items [enterprise] #### UC-D-064 / local-proc-stakeholders Ask: How many distinct parties need visibility into the procurement data? Answer: pick one Requirement type: usability - Internal only (1–2 teams) [internal] - Internal + 1–3 external partners [few-external] - Multiple external stakeholders (4–10) [multi-external] - Ecosystem-wide (donors, partners, beneficiaries, regulators) [ecosystem] #### UC-D-064 / item-tracking-method Ask: How will physical items be tracked and scanned in the field? Answer: pick one Requirement type: devices - QR codes printed on items or packaging [qr-codes] - NFC tags embedded in items [nfc-tags] - Barcode labels with batch scanning [barcode] - Mixed: QR for high-value items, barcode for bulk [mixed] #### UC-D-064 / audit-mechanism-approach Ask: How should auditing and verification work for this solution? Answer: pick one Requirement type: audit-trail - Automatic checks that flag problems as they happen [automated-realtime] - Regular scheduled reviews with tamper-proof records [periodic-batch] - Ability to check any record at any time with proof it has not been altered [on-demand] - External auditors can log in and review records independently [third-party] ### UC-D-065: Warehouse inventory management Security level: Standard. #### UC-D-065 / warehouse-facility-count Ask: How many warehouse facilities need to be managed? Answer: pick one Requirement type: scale - Single warehouse [single-warehouse] - Multi-warehouse network (2-5 facilities) [multi-warehouse] - Complex distribution network (5+ facilities) [complex-network] #### UC-D-065 / item-volume-and-variety Ask: What is the inventory volume and variety? Answer: pick one Requirement type: scale - Low volume, limited variety (100-500 items) [low-volume] - Medium volume and variety (500-5000 items) [medium-volume] - High volume and variety (5000+ items) [high-volume] #### UC-D-065 / existing-wms-integration Ask: Should the system integrate with existing WMS? Answer: pick one Requirement type: integration - No integration, standalone system [standalone] - API integration with existing WMS [api-integration] - Full replacement of existing WMS [full-replacement] #### UC-D-065 / warehouse-automation-level Ask: What level of warehouse automation is desired? Answer: pick one Requirement type: general - Manual operations and record keeping [manual-operations] - Semi-automated with barcoding [semi-automated] - Fully automated with RFID and robotics [fully-automated] #### UC-D-065 / audit-mechanism-approach Ask: How should auditing and verification work for this solution? Answer: pick one Requirement type: audit-trail - Automatic checks that flag problems as they happen [automated-realtime] - Regular scheduled reviews with tamper-proof records [periodic-batch] - Ability to check any record at any time with proof it has not been altered [on-demand] - External auditors can log in and review records independently [third-party] ### UC-D-066: Expiry tracking and waste reduction Security level: Standard. #### UC-D-066 / expiry-item-types-scope Ask: What types of items with expiry dates need tracking? Answer: pick one Requirement type: general - Medicines and medical supplies only [medical-only] - Medicines, food, and perishables [medicines-food] - Comprehensive (all time-sensitive items) [comprehensive] #### UC-D-066 / waste-reduction-targets Ask: What waste reduction targets are being set? Answer: pick one Requirement type: general - No specific target (current state acceptable) [no-target] - Reduce waste by 25-50% [moderate-target] - Aggressive target: reduce waste by 75%+ [aggressive-target] #### UC-D-066 / expiry-alert-mechanism-type Ask: What alert mechanism should warn of approaching expiry? Answer: pick one Requirement type: credentials - Manual monthly reviews [manual-review] - Automated email/SMS alerts at 90-30 days [automated-email-sms] - Real-time dashboard with predictive warnings [realtime-predictive] #### UC-D-066 / fifo-enforcement-method Ask: How do you currently enforce FIFO (first-in-first-out) in your inventory? Answer: pick one Requirement type: general - Manual FIFO compliance verification [manual-fifo] - Barcode-based FIFO sequencing [barcode-fifo] - Automated FIFO enforcement with alerts [automated-fifo] #### UC-D-066 / sq-UC-D-066-003 Ask: What waste documentation is required for expired items? Answer: pick one Requirement type: legal-checks - Photo evidence [photo-evidence] - Witness attestation [witness-attestation] - Weight/volume record [weight-volume-record] - Environmental disposal certificate [environmental-disposal-cert] - Donor notification [donor-notification] #### UC-D-066 / supply-volume-scale Ask: What is the annual volume of medical supplies to be tracked? Answer: pick one Requirement type: scale - Low volume (< 10,000 units/year) [low-volume] - Medium volume (10,000 - 100,000 units/year) [medium-volume] - High volume (> 100,000 units/year) [high-volume] #### UC-D-066 / tracking-granularity-supply Ask: Should supplies be tracked at batch or individual item level? Answer: pick one Requirement type: general - Batch/box level tracking only [batch-only] - Individual item tracking [individual-items] - Hybrid batch and sampling approach [hybrid-approach] #### UC-D-066 / sq-UC-D-066-004 Ask: What temperature and storage condition monitoring is needed alongside expiry tracking? Answer: pick one Requirement type: general - Temperature only [temperature-only] - Temperature and humidity [temperature-humidity] - Full environmental monitoring [full-environmental] - GPS location tracking [gps-location] - Expiry only [none-expiry-only] #### UC-D-066 / item-tracking-method Ask: How will physical items be tracked and scanned in the field? Answer: pick one Requirement type: devices - QR codes printed on items or packaging [qr-codes] - NFC tags embedded in items [nfc-tags] - Barcode labels with batch scanning [barcode] - Mixed: QR for high-value items, barcode for bulk [mixed] ### UC-D-067: Smallholder farmer market access and fair trade verification Security level: Standard. #### UC-D-067 / farmer-count Ask: How many smallholder farmers would participate in the programme? Answer: pick one Requirement type: audit-trail - Under 100 farmers [small] - 100–500 farmers [medium] - 500–5,000 farmers [large] - 5,000+ farmers [very-large] #### UC-D-067 / certification-target Ask: Which market certification or standard are you targeting? Answer: pick all that apply Requirement type: credentials - Fair Trade certification [fair-trade] - Organic certification [organic] - Direct trade / specialty market [direct-trade] - Rainforest Alliance / sustainability [sustainability] - No specific certification, general provenance [general] #### UC-D-067 / buyer-integration Ask: How will buyers access and verify the provenance data? Answer: pick one Requirement type: integration - Consumer-facing QR code on product packaging [consumer-qr] - B2B API integration with buyer procurement systems [b2b-api] - Certification body verification portal [cert-portal] - All of the above [all] #### UC-D-067 / farmer-payment-method Ask: How will farmers receive payments from premium buyers? Answer: pick one Requirement type: money - Mobile money (existing mobile money account) [mobile-money] - Stablecoin to farmer wallet [stablecoin] - Bank transfer through cooperative [bank-cooperative] - Cash through agent network [cash-agent] #### UC-D-067 / local-infrastructure Ask: What technology infrastructure exists at the farm level? Answer: pick one Requirement type: general - Smartphones with mobile data common among farmers [smartphone] - Feature phones only: SMS/USSD required [feature-phone] - Limited phone access: cooperative/agent intermediary needed [intermediary] - Mixed: some smartphone, some feature phone, some no phone [mixed] ### UC-D-068: Aid diversion detection and prevention Security level: Standard. #### UC-D-068 / diversion-detection-trigger Ask: When should diversion be detected, after the fact, during distribution, or in real time? Answer: pick one Requirement type: general - Post-hoc audits only (sample and investigate) [post-hoc] - Distribution-day reconciliation (same-day exception review) [same-day] - Real-time anomaly alerts during distribution [real-time] #### UC-D-068 / item-tracking-method Ask: How will physical items be tracked and scanned in the field? Answer: pick one Requirement type: devices - QR codes printed on items or packaging [qr-codes] - NFC tags embedded in items [nfc-tags] - Barcode labels with batch scanning [barcode] - Mixed: QR for high-value items, barcode for bulk [mixed] #### UC-D-068 / fraud-prevention-mechanism Ask: What approach would you need for preventing and detecting supply chain fraud? Answer: pick one Requirement type: general - Documentation and random spot checks [spot-checks] - Digital verification with supervisor review [digital-review] - Real-time monitoring with digital ledger confirmation [blockchain-monitoring] #### UC-D-068 / last-mile-stakeholders Ask: How many distinct parties need visibility into the distribution data? Answer: pick one Requirement type: usability - Internal only (1–2 teams) [internal] - Internal + 1–3 external partners [few-external] - Multiple external stakeholders (4–10) [multi-external] - Ecosystem-wide (donors, partners, beneficiaries, regulators) [ecosystem] #### UC-D-068 / diversion-consequence-model Ask: What should happen when diversion is detected? Answer: pick one Requirement type: general - Internal reporting and policy review [internal-report] - Partner contract penalties (withheld payment, termination) [partner-penalty] - Automated disbursement freeze until remediation verified [auto-freeze] - Referral to donor / external investigator [external-referral] ### UC-D-069: Beneficiary receipt confirmation (proof of delivery) Security level: Standard. #### UC-D-069 / receipt-channel Ask: How will beneficiaries confirm receipt of what they were sent? Answer: pick one Requirement type: credentials - Paper receipt with signature/thumbprint [paper] - SMS or USSD confirmation from beneficiary [sms] - Mobile app with beneficiary login [mobile-app] - Mixed: paper as fallback, digital as default [mixed] #### UC-D-069 / receipt-cryptographic-model Ask: How strongly should the receipt be cryptographically bound so that it cannot be fabricated or repudiated later? Answer: pick one Requirement type: general - Plain record: timestamp and ID, no cryptographic binding [plain] - Signed record: org signs the receipt after capture [org-signed] - Beneficiary-signed: beneficiary's key signs the attestation [beneficiary-signed] - Anchored: hash of receipt batch committed to a shared ledger [anchored] #### UC-D-069 / delivery-verification-method Ask: Which verification method should be used for delivery? Answer: pick one Requirement type: credentials - Signature or thumbprint on receipt [signature-receipt] - QR code scanning by beneficiary [qr-scanning] - Biometric verification with photo [biometric-photo] #### UC-D-069 / beneficiary-id-system Ask: How are beneficiaries identified and registered? Answer: pick one Requirement type: integration - Basic list with name and location [basic-list] - Digital registry with unique ID [digital-id] - Biometric registry with multi-modal data [biometric-registry] #### UC-D-069 / receipt-consequence Ask: What happens once a beneficiary-attested receipt is recorded? Answer: pick one Requirement type: general - Informational only: receipt closes the delivery record [informational] - Reporting driver: receipts feed donor reports and M&E [reporting] - Partner payment trigger: receipt releases partner payment [partner-payment] - Donor tranche trigger: receipt releases next donor disbursement [donor-tranche] ### UC-D-070: Conflict mineral and material tracking Security level: Standard. #### UC-D-070 / material-scope Ask: Which materials fall within the scope of the traceability programme? Answer: pick one Requirement type: general - 3TG only (tin, tantalum, tungsten, gold) [3tg] - 3TG + cobalt [3tg-cobalt] - Broader ESG-sensitive materials (lithium, rare earths, timber, textiles) [broad-esg] - Single-material focus (programme-specific) [single] #### UC-D-070 / tracing-depth Ask: How far upstream does the traceability need to extend? Answer: pick one Requirement type: general - Smelter-level (smelter → downstream) [smelter] - Mine-to-smelter (origin-to-processor) [mine-to-smelter] - Mine-to-product (full end-to-end) [end-to-end] - Community-level (including artisanal producer cooperatives) [community] #### UC-D-070 / compliance-gate Ask: What should happen when provenance fails compliance? Answer: pick one Requirement type: legal-checks - Reporting only: provenance data informs reports but doesn't block procurement [report-only] - Soft gate: non-compliance triggers review but not rejection [soft-gate] - Payment gate: payment withheld until compliance verified [payment-gate] - Hard gate: non-compliant material refused at receipt [hard-gate] #### UC-D-070 / evidence-model Ask: What evidence is required to back a provenance claim? Answer: pick one Requirement type: audit-trail - Supplier self-attestation (declaration only) [self-attest] - Third-party audited (independent auditor counter-signs) [third-party] - Cryptographic attestation (signed provenance records at each tier) [crypto-attest] - Hybrid: supplier attestation anchored + third-party audit [hybrid] #### UC-D-070 / supplier-disclosure-model Ask: Who needs to be able to verify provenance, and how much can be disclosed publicly? Answer: pick one Requirement type: general - Full public disclosure of suppliers and origins [public] - Disclosed to donor/regulator only under NDA [nda] - Selective disclosure: claims verifiable, identities hidden [selective] - Internal only, not disclosed outside the org [internal] ### UC-D-071: Customs and import documentation Security level: Standard. #### UC-D-071 / customs-integration-target Ask: Which customs ecosystem does the system need to integrate with? Answer: pick one Requirement type: integration - No integration, documents still paper-first, ledger is internal record only [internal-only] - National Single Window integration in origin/destination country [single-window] - ASYCUDA or equivalent customs-authority system [asycuda] - Multi-country: broker-based with ad-hoc integrations [broker-based] - Full consortium ledger including customs authorities [consortium] #### UC-D-071 / duty-exemption-mechanism Ask: How should duty-exemption claims be verified and released? Answer: pick one Requirement type: general - Case-by-case manual exemption application per shipment [manual] - Pre-approved exemption category with per-shipment paperwork [pre-approved] - Digital exemption record with authority-signed attestation [digital-attested] - Smart-contract exemption verification with automated release [smart-contract] #### UC-D-071 / document-authentication Ask: How should customs documents be authenticated? Answer: pick one Requirement type: general - Wet-ink paper with scan-and-store [wet-ink] - PDF with typed signatures [pdf-sig] - E-signature with cryptographic signing [esign] - Ledger-anchored documents with verifiable issuance [ledger-anchored] #### UC-D-071 / exception-handling-model Ask: How are customs exceptions (misclassification, missing docs, duty disputes) resolved? Answer: pick one Requirement type: general - Email-based escalation to broker and NGO ops [email] - Case-management platform with SLA tracking [case-mgmt] - Integrated exception workflow linked to ledger entries [integrated] - Authority-participating workflow with shared resolution ledger [authority-shared] #### UC-D-071 / data-jurisdiction Ask: Where do customs-document records need to be stored to satisfy each jurisdiction's data-sovereignty rules? Answer: pick one Requirement type: residency. Hard gate: yes - All data stored in origin country [origin-only] - Data stored in destination country only [destination-only] - Dual storage in origin and destination [dual] - Distributed ledger with per-jurisdiction access controls [distributed] ### UC-D-072: Ethical sourcing verification Security level: Standard. #### UC-D-072 / sourcing-scope Ask: Which commodities are in scope for ethical-sourcing verification? Answer: pick one Requirement type: general - Single commodity class (e.g. food, or textiles) [single] - Multiple commodity classes [multi] - Full procurement portfolio [full] #### UC-D-072 / sourcing-tier-depth Ask: How many tiers of the supply chain need verifiable visibility? Answer: pick one Requirement type: general - Tier 1 only (direct supplier) [tier1] - Tier 1 + 2 (supplier + their inputs) [tier2] - Full chain to origin (farm / factory level) [full] #### UC-D-072 / sourcing-standards Ask: Which ethical standards apply? Answer: pick one Requirement type: general - Single standard (e.g. Fair Trade only) [single-std] - Multiple standards (Fair Trade + Rainforest Alliance + SA8000) [multi-std] - Custom NGO ethical framework + external standards [custom] #### UC-D-072 / sourcing-evidence-model Ask: Where does verification evidence come from? Answer: pick one Requirement type: audit-trail - Supplier self-declaration (lowest assurance) [self] - Third-party certifier audits [third-party] - Continuous IoT + audit + worker attestation [continuous] #### UC-D-072 / sourcing-consumer-disclosure Ask: How is sourcing integrity communicated to donors and the public? Answer: pick one Requirement type: general - Internal only: procurement team reference [internal] - Donor-facing: available on request during audit [donor] - Public: beneficiary and donor-facing provenance dashboard [public] ### UC-D-073: Food safety and quality tracking Security level: Standard. #### UC-D-073 / foodsafety-scope Ask: Which food-safety domains are in scope? Answer: pick one Requirement type: general - Contamination / pathogen tracking only [contamination] - Contamination + spoilage / temperature excursions [spoilage] - Comprehensive (contamination, spoilage, quality, nutritional integrity) [comprehensive] #### UC-D-073 / foodsafety-recall-speed Ask: How quickly do you need to propagate a recall once triggered? Answer: pick one Requirement type: money - Days (manual coordination) [days] - Hours (semi-automated) [hours] - Real-time (automated recall + beneficiary notification) [realtime] #### UC-D-073 / foodsafety-evidence-source Ask: Where does safety evidence come from? Answer: pick one Requirement type: audit-trail - Supplier certificates only [certs] - Supplier certs + independent sampling [sampling] - Continuous IoT + lab + inspection [continuous] #### UC-D-073 / foodsafety-beneficiary-reach Ask: Can beneficiaries be reached directly during a recall? Answer: pick one Requirement type: general - No, distribution-point notification only [no] - Partial, SMS or mobile messaging where available [partial] - Yes, direct beneficiary comms (mobile, wristband, voucher app) [full] #### UC-D-073 / foodsafety-audit-target Ask: Who needs to audit safety events? Answer: pick one Requirement type: audit-trail - Internal QA only [internal] - Regulators + donors + internal [external] - Public (full consumer-facing transparency) [public] ### UC-D-074: Pooled humanitarian commodity claims and replenishment (UN humanitarian response depots, World Food Programme hubs) Security level: Standard. #### UC-D-074 / commodity-pool-scope Ask: How many stockpiles / hubs does the agency interact with? Answer: pick one Requirement type: general - Single stockpile (e.g., UNHRD Brindisi only) [single] - Multiple hubs under single operator (UNHRD network) [multi-same-operator] - Multiple pools across operators (UNHRD + WFP + national) [multi-operator] #### UC-D-074 / commodity-drawdown-volume Ask: What is the annual drawdown volume? Answer: pick one Requirement type: scale - Low (<50 tonnes or 500 tonnes or USD 1M+) [high] #### UC-D-074 / commodity-replenishment Ask: How is commodity replenishment handled? Answer: pick one Requirement type: general - In-kind (replace what you take) [in-kind] - Cash-based (pay for drawdowns) [cash] - Hybrid (credit-based with periodic reconciliation) [hybrid] #### UC-D-074 / commodity-integrity-events Ask: Which integrity events must be tracked? Answer: pick one Requirement type: audit-trail - Drawdown and return only [basic] - Drawdown + return + expiry / condition changes [moderate] - Full (drawdown, return, expiry, condition, quality, cold-chain, recall) [full] #### UC-D-074 / commodity-audit-audience Ask: Who audits pool integrity? Answer: pick one Requirement type: audit-trail - Pool manager only [manager] - Pool manager + member agencies [members] - Pool + members + donors + public (full transparency) [public] ### UC-D-075: Food voucher tokenisation Security level: Higher. #### UC-D-075 / voucher-volume Ask: How many households will receive vouchers in each cycle? Answer: pick one Requirement type: scale - Fewer than 1,000 households per cycle [under-1k] - 1,000 to 10,000 households per cycle [1k-10k] - 10,000 to 100,000 households per cycle [10k-100k] - Over 100,000 households per cycle [over-100k] #### UC-D-075 / vendor-network-size Ask: How many vendors will take part? Answer: pick one Requirement type: scale - Fewer than 20 enrolled vendors [under-20] - 20 to 100 vendors [20-100] - 100 to 500 vendors [100-500] - Over 500 vendors [over-500] #### UC-D-075 / redemption-ux Ask: How will vendors confirm a voucher? Answer: pick all that apply Requirement type: usability - Vendor smartphone app [vendor-app] - SMS confirmation code [sms-code] - USSD interface [ussd] - QR code at vendor [qr] - Beneficiary biometric [biometric] #### UC-D-075 / offline-redemption Ask: How often must vendors redeem vouchers without a connection? Answer: pick one Requirement type: offline - Not required: vendor connectivity is reliable [not-required] - Required for intermittent connectivity [intermittent] - Required: frequent multi-day outages [frequent] - Default mode: assume offline, sync opportunistically [default] #### UC-D-075 / voucher-restrictions Ask: What limits will vouchers carry? Answer: pick all that apply Requirement type: general - Eligible food items list [eligible-items] - Vendor whitelist [vendor-whitelist] - Expiry date [expiry] - Transferable within household [transferability-household] - Non-transferable [non-transferable] - Geographic restriction (specific markets) [geographic] #### UC-D-075 / beneficiary-identifier Ask: How will each household be identified? Answer: pick one Requirement type: credentials - New beneficiary ID issued by CSO [new-id] - National ID linkage [national-id] - Verifiable digital identity credential (if available) [veridian] - Biometric identifier [biometric] - Mobile phone number [phone-based] #### UC-D-075 / cluster-deduplication Ask: How will you avoid double support from other partners? Answer: pick one Requirement type: credentials - Single-implementer programme: no cluster overlap [none] - Manual cluster reconciliation [manual] - Planning shared deduplication with other partners [planned] - Active cluster-level deduplication via Food Security Cluster [active] #### UC-D-075 / donor-reporting-granularity Ask: How detailed must donor reporting be? Answer: pick one Requirement type: audit-trail - Statistical sampling [statistical] - Aggregate transaction reports [aggregate] - Transaction-level audit trail [transaction-level] - Real-time donor dashboard [real-time] #### UC-D-075 / regulatory-permission Ask: Are digital vouchers allowed where you work? Answer: pick one Requirement type: legal-checks - Digital vouchers permitted explicitly [clear] - Operating under regulatory grace [operating-under-grace] - Regulatory status ambiguous [ambiguous] - Digital vouchers prohibited: programme cannot deploy [prohibited] ### UC-E-068: Voting and decision-making for consortia Security level: Standard. #### UC-E-068 / voting-method Ask: 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? Answer: pick one Requirement type: governance - Simple majority (51%+) [simple-majority] - Supermajority or consensus-based (66%+ or 75%+) [supermajority] - Weighted voting (stake-based or role-based) [weighted-voting] - Multi-stage or tiered voting [tiered-voting] - Delegated voting (proxy-based) [delegated-voting] #### UC-E-068 / voting-scale Ask: What scale of voting participants do you anticipate? Answer: pick one Requirement type: scale - Small (up to 50 voters) [small-scale] - Medium (50–500 voters) [medium-scale] - Large (500–5,000 voters) [large-scale] - Very large (5,000+ voters) [very-large-scale] #### UC-E-068 / dispute-resolution Ask: 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? Answer: pick one Requirement type: governance - Permanent tamper-proof result acceptance with no appeal [immutable-final] - Governance council review and override capability [council-review] - Mandatory recount with digitally verified [cryptographic-recount] - Escalation to community arbitration [community-arbitration] - Time-locked grace period for challenge submission [grace-period-challenge] #### UC-E-068 / decision-audit-trail Ask: How are governance decisions currently recorded and verified? Answer: pick one Requirement type: audit-trail - Full decision log: every vote, rationale, and outcome recorded [full-log] - Outcome-only: record final decisions and who approved [outcome-only] - Anonymised voting with verifiable tallies [anonymised-voting] - Not sure, need guidance [guidance-needed] ### UC-E-069: Community-based targeting verification Security level: Standard. #### UC-E-069 / targeting-method Ask: What targeting methodology does your community use? Answer: pick one Requirement type: general - Needs-based assessment with objective criteria [needs-assessment] - Community wealth ranking or participatory assessment [community-ranking] - Vulnerable group identification (elderly, disabled, etc.) [vulnerable-groups] - Geographic or sectoral targeting [geographic-sectoral] - Hybrid multi-criteria approach [hybrid-multicriteria] #### UC-E-069 / community-participation Ask: How do community members currently participate in verification? Answer: pick one Requirement type: governance - Open community assembly with consensus decision [open-assembly] - Representative committee (elected or designated) [representative-committee] - Asynchronous feedback period with public comments [asynchronous-feedback] - Stakeholder rounds with documented responses [stakeholder-rounds] #### UC-E-069 / dispute-handling Ask: How are disputes currently resolved in your governance structures? Answer: pick one Requirement type: governance - Community reconsideration with appeal submission [community-reconsideration] - Independent review panel with documented decision [review-panel] - Mediation by trusted third party [mediation] - Immediate re-verification with transparent criteria audit [reverification] #### UC-E-069 / targeting-transparency Ask: Do your donors require visibility into which beneficiaries were selected and why? Do community members demand to see the targeting criteria and decisions? Answer: pick one Requirement type: general - Full public criteria and selected beneficiary list [full-public] - Criteria public; beneficiary list for community review only [criteria-public-list-community] - Aggregated statistics; no individual names published [aggregated-stats] - Reasons for selection transparent; identities private [reasons-public-identity-private] #### UC-E-069 / community-targeting-participant-count Ask: How many organisations or stakeholders participate in community targeting? Answer: pick one Requirement type: scale - 2–5 parties [small] - 6–15 parties [medium] - 16–50 parties [large] - Over 50 parties [enterprise] ### UC-E-070: Grant allocation across multiple partners Security level: Standard. #### UC-E-070 / allocation-model Ask: How are grants currently allocated across partners? Answer: pick one Requirement type: audit-trail - Fixed proportion model (e.g., 40% to partner A, 60% to partner B) [fixed-proportion] - Performance-based allocation with KPI weighting [performance-based] - Needs-based allocation determined by partner capacity [needs-based] - Competitive funding model with proposal evaluation [competitive-funding] - Dynamic allocation adjusting quarterly based on metrics [dynamic-allocation] #### UC-E-070 / decision-making Ask: How will allocation decisions be made and approved? Answer: pick one Requirement type: governance - Headquarters leadership decision with documented rationale [hq-leadership] - Multi-stakeholder committee with voting mechanism [committee-voting] - Consensus-based agreement with all partners signing off [consensus-agreement] - Algorithmic formula with human review override [algorithmic-with-review] #### UC-E-070 / fund-tracking-granularity Ask: At what granularity will you track fund usage across partners? Answer: pick one Requirement type: audit-trail - Activity level (individual project or program) [activity-level] - Budget line level (salary, supplies, transport, etc.) [budget-line] - Transaction level (every receipt or invoice) [transaction-level] - Milestone level (fund released on achievement) [milestone-level] - High-level monitoring (monthly or quarterly reporting) [highlevel-monthly] #### UC-E-070 / allocation-reporting Ask: How will allocation decisions and fund flows be reported? Answer: pick one Requirement type: audit-trail - Public dashboard with real-time fund visibility [public-dashboard] - Confidential partner reports with authenticated access [partner-reports] - Periodic audit reports with third-party certification [audit-reports] - Disaggregated data export for analysis and learning [disaggregated-data] #### UC-E-070 / allocation-flexibility Ask: How much flexibility exists to adjust allocations during a funding cycle? Answer: pick one Requirement type: audit-trail - No mid-cycle changes; allocations locked until next cycle [no-changes] - Emergency reallocation with documented justification [emergency-reallocation] - Quarterly rebalancing based on partner request [quarterly-rebalancing] - Continuous adjustment within predefined thresholds [continuous-adjustment] ### UC-E-071: Programme outcome verification Security level: Standard. #### UC-E-071 / kpi-types Ask: What KPIs will measure partner performance? Answer: pick one Requirement type: credentials - Output metrics (beneficiaries reached, activities completed) [output-metrics] - Outcome metrics (behavior change, impact achieved) [outcome-metrics] - Process metrics (timeliness, quality, compliance) [process-metrics] - Financial metrics (budget variance, cost per unit) [financial-metrics] - Mixed portfolio across multiple metric types [mixed-portfolio] #### UC-E-071 / verification-method Ask: How will KPI achievement be verified? Answer: pick one Requirement type: credentials - Partner self-reporting with spot checks [self-report-checks] - Third-party monitoring and evaluation [third-party-m-and-e] - Direct automated measurement (sensors, systems, automated checks) [automated-measurement] - Community verification with independent witnesses [community-verification] - Hybrid approach combining multiple methods [hybrid-verification] #### UC-E-071 / performance-consequences Ask: What are the consequences of not meeting KPI targets? Answer: pick one Requirement type: credentials - Supportive improvement plan with technical assistance [support-plan] - Performance-based budget adjustment (e.g., 10% reduction) [budget-adjustment] - Automatic fund withholding until recovery plan achieved [automatic-withholding] - Partnership termination with formal exit process [partnership-termination] - Tiered response escalating by severity of underperformance [tiered-response] #### UC-E-071 / reporting-frequency Ask: When a partner's performance is below expectations, do disputes arise about whether the data is accurate or whether the metrics are fair? Answer: pick one Requirement type: audit-trail - Real-time or continuous monitoring dashboard [realtime-dashboard] - Weekly performance snapshots [weekly-reports] - Monthly performance reports [monthly-reports] - Quarterly comprehensive reviews [quarterly-reviews] - Annual evaluations with mid-term review optional [annual-evaluation] #### UC-E-071 / partner-perf-participant-count Ask: How many organisations or stakeholders participate in partner performance reviews? Answer: pick one Requirement type: scale - 2–5 parties [small] - 6–15 parties [medium] - 16–50 parties [large] - Over 50 parties [enterprise] #### UC-E-071 / partner-perf-decision-freq Ask: How frequently are partner performance decisions or records created? Answer: pick one Requirement type: governance - Daily or more [daily] - Weekly [weekly] - Monthly [monthly] - Quarterly or less [quarterly] ### UC-E-072: Whistleblower protection mechanisms Security level: Critical. #### UC-E-072 / anonymity-level Ask: Given the retaliation risk in your context, can investigations proceed without revealing the whistleblower's identity? Answer: pick one Requirement type: privacy - Complete anonymity: no identifying information collected [complete-anonymity] - Pseudonymity: known to trusted coordinator but not publicly [pseudonymity] - Optional disclosure: whistleblower chooses to identify or remain anonymous [optional-disclosure] - Delayed disclosure: identity known to investigators only, public reporting anonymous [delayed-disclosure] #### UC-E-072 / reporting-channel Ask: What reporting channels will whistleblowers use? Answer: pick one Requirement type: privacy - Web-based submission form with end-to-end encryption [encrypted-web-form] - SMS or voice hotline accessible from any phone [voice-sms-hotline] - In-person drop box or physical submission mechanism [physical-dropbox] - Multiple channels with whistleblower choosing preferred method [multi-channel] #### UC-E-072 / investigation-workflow Ask: What investigation workflow will handle reported concerns? Answer: pick one Requirement type: privacy - Independent ombudsman or third-party investigator [independent-investigator] - Internal investigation team with conflict-of-interest safeguards [internal-investigation] - Multi-party investigation committee with external member [committee-investigation] - Forensic analysis with evidence ledger and reporting timeline [forensic-analysis] #### UC-E-072 / protection-mechanisms Ask: What protection mechanisms will prevent retaliation against whistleblowers? Answer: pick one Requirement type: privacy - Legal protections enshrined in policy and employment contracts [policy-legal-protection] - Monitoring for retaliation with rapid intervention [retaliation-monitoring] - Physical security measures or relocation if needed [physical-security] - Financial protection (insurance or compensation fund) [financial-protection] - Comprehensive package combining multiple protections [comprehensive-package] #### UC-E-072 / anonymisation-approach Ask: How should personal data be anonymised or protected? Answer: pick one Requirement type: privacy - Full data anonymisation (irreversible) [full-anonymisation] - Pseudonymisation (reversible by authorised parties) [pseudonymisation] - Differential privacy (statistical noise injection) [differential-privacy] - Selective redaction (remove specific identifiers) [selective-redaction] #### UC-E-072 / dispute-resolution Ask: How is disputes currently resolved within this system? Answer: pick one Requirement type: governance - digital arbitration with automated rules enforcement [on-chain-arb] - External mediation with digital outcome recording [mediation] - Multi-tier: automated resolution, then escalation to human mediator [multi-tier] - Not sure, need guidance [guidance-needed] ### UC-E-073: Cross-NGO beneficiary coordination (avoiding gaps and overlaps) Security level: Standard. #### UC-E-073 / coordination-scope Ask: What is the scope of cross-NGO coordination? Answer: pick one Requirement type: governance - Information sharing only (data exchange without joint decision-making) [information-sharing] - Collaborative deduplication (shared beneficiary database) [shared-deduplication] - Joint beneficiary selection and targeting decisions [joint-targeting] - Integrated service delivery (co-implementation of programs) [integrated-delivery] #### UC-E-073 / data-sharing-model Ask: How will NGOs share beneficiary data securely? Answer: pick one Requirement type: governance - Centralized database with role-based access control [centralized-database] - Shared digital register with selective data visibility [distributed-visibility] - Hashed or anonymized data with zero-knowledge proofs [anonymized-zk] - Query service without raw data sharing (federated learning) [federated-queries] #### UC-E-073 / privacy-preservation Ask: What privacy preservation techniques will protect beneficiary data? Answer: pick one Requirement type: privacy - Minimal data sharing (only necessary fields for deduplication) [minimal-data] - Differential privacy (statistical noise added) [differential-privacy] - Secure multi-party computation (no single party sees raw data) [secure-mpc] - privacy-preserving computation (data stays encrypted during analysis) (computation on encrypted data) [homomorphic-encryption] #### UC-E-073 / deduplication-logic Ask: How will beneficiary deduplication logic work? Answer: pick one Requirement type: credentials - Deterministic matching on unique ID (national ID, biometric) [deterministic-id] - Probabilistic matching on name, age, location with human review [probabilistic-review] - Biometric matching (fingerprint or facial recognition) [biometric-matching] - Federated matching service without beneficiary data in one place [federated-matching] #### UC-E-073 / cross-ngo-governance Ask: How is governance and conflict resolution currently handled across NGOs? Answer: pick one Requirement type: governance - Steering committee with rotating NGO representation [steering-committee] - Democratic voting (one NGO, one vote) on shared decisions [democratic-voting] - Consensus requirement (unanimous agreement or fallback to status quo) [consensus-based] - Arbitration by neutral third party on contested issues [third-party-arbitration] #### UC-E-073 / coordination-layer-approach Ask: How do multiple parties currently coordinate decisions and actions? Answer: pick one Requirement type: governance - Shared workspace with real-time multi-party visibility [shared-workspace] - Event-driven notifications across organisations [event-driven] - Scheduled data sync between partner systems [scheduled-sync] - system-connected integration between organisation systems [api-based] ### UC-E-074: Cluster coordination record-keeping Security level: Standard. #### UC-E-074 / cluster-type Ask: What type of cluster coordination are you managing? Answer: pick one Requirement type: governance - Geographic cluster (all NGOs in a region/country) [geographic-cluster] - Sectoral cluster (all NGOs in health, food security, shelter, etc.) [sectoral-cluster] - Emergency response cluster (ad-hoc coalitions for crisis response) [emergency-cluster] - Multi-level cluster (regional and sectoral combined) [multilevel-cluster] #### UC-E-074 / decision-recording Ask: How will cluster decisions be recorded and tracked? Answer: pick one Requirement type: governance - Meeting minutes ledger with consensus recorded [meeting-minutes] - Voting record with member consent documented [voting-record] - Action item tracker with assignment and completion log [action-tracker] - automated rules recording decisions automatically digital [smart-contract-record] #### UC-E-074 / information-sharing Ask: What information will be shared among cluster members? Answer: pick one Requirement type: integration - Strategic only: policies, decisions, coordination documents [strategic-only] - Operational: activities, locations, beneficiary numbers [operational] - Real-time: immediate incident reports and urgent updates [realtime] - Tiered sharing: members choose what to share at what level [tiered-sharing] #### UC-E-074 / cluster-participant-count Ask: How many organisations or stakeholders participate in cluster coordination? Answer: pick one Requirement type: scale - 2–5 parties [small] - 6–15 parties [medium] - 16–50 parties [large] - Over 50 parties [enterprise] #### UC-E-074 / cluster-decision-freq Ask: How frequently are cluster coordination decisions or records created? Answer: pick one Requirement type: governance - Daily or more [daily] - Weekly [weekly] - Monthly [monthly] - Quarterly or less [quarterly] ### UC-E-075: Beneficiary feedback and complaints mechanisms Security level: Standard. #### UC-E-075 / feedback-channels Ask: Do donors or community members require visibility into feedback received and how it shaped program changes? Answer: pick one Requirement type: general - Community meetings and focus group discussions [community-meetings] - Anonymous suggestion boxes (physical or digital) [suggestion-boxes] - SMS-based feedback polls accessible via any phone [sms-feedback] - Mobile application for structured feedback and surveys [mobile-app] - Multi-channel approach (combination of above) [multi-channel] #### UC-E-075 / feedback-anonymity Ask: What anonymity level will be offered for feedback? Answer: pick one Requirement type: privacy - Full anonymity: no identifying information collected [full-anonymity] - Optional anonymity: submitter can choose to identify [optional-anonymity] - Contact information for follow-up but not for enforcement [contact-follow-up] - Identified feedback with protection against retaliation [identified-protected] #### UC-E-075 / response-tracking Ask: How will feedback responses and actions be tracked? Answer: pick one Requirement type: general - Feedback response log with documented action plan [response-log] - Public dashboard showing feedback received and status [public-dashboard] - Periodic feedback report shared back with community [feedback-report] - Automated tracking system with community notifications [automated-tracking] #### UC-E-075 / comm-feedback-participant-count Ask: How many organisations or stakeholders participate in the feedback process? Answer: pick one Requirement type: scale - 2–5 parties [small] - 6–15 parties [medium] - 16–50 parties [large] - Over 50 parties [enterprise] #### UC-E-075 / sq-UC-E-075-003 Ask: What response time commitments should be tracked for feedback resolution? Answer: pick one Requirement type: general - 24-hour acknowledgement [24-hour-acknowledgement] - 72-hour response [72-hour-response] - Weekly review [weekly-review] - No SLA, best effort [no-sla-best-effort] - Tiered by severity [tiered-by-severity] #### UC-E-075 / reporting-approach Ask: What reporting capabilities does this solution need? Answer: pick one Requirement type: audit-trail - Automated donor/funder reporting with scheduled delivery [automated-donor] - Self-service dashboard with custom report builder [self-service] - Regulatory compliance reporting (government/authority) [regulatory] - Multi-audience reporting (donors, government, community) [multi-audience] #### UC-E-075 / decision-audit-trail Ask: How are governance decisions currently recorded and verified? Answer: pick one Requirement type: audit-trail - Full decision log: every vote, rationale, and outcome recorded [full-log] - Outcome-only: record final decisions and who approved [outcome-only] - Anonymised voting with verifiable tallies [anonymised-voting] - Not sure, need guidance [guidance-needed] ### UC-E-076: Local partner capacity verification Security level: Standard. #### UC-E-076 / capacity-domains Ask: What capacity domains will you assess for partners? Answer: pick one Requirement type: credentials - Technical capacity (programme design, M&E, sector expertise) [technical-capacity] - Organizational capacity (governance, HR, finance, systems) [organizational-capacity] - Financial management capacity (budgeting, accounting, controls) [financial-capacity] - Compliance capacity (legal, regulatory, safeguarding) [compliance-capacity] - Holistic assessment across all domains [holistic-assessment] #### UC-E-076 / assessment-method Ask: How will partner capacity be assessed? Answer: pick one Requirement type: credentials - Self-assessment questionnaire with spot checks [self-assessment] - External assessment by qualified assessor [external-assessment] - Peer review by similar organizations [peer-review] - Continuous monitoring with real-time feedback [continuous-monitoring] #### UC-E-076 / capacity-development-tracking Ask: How will partner capacity development progress be tracked? Answer: pick one Requirement type: credentials - Baseline and annual reassessment with comparison [baseline-reassessment] - Progress against agreed capacity development plan [development-plan] - Competency milestones with achievement verification [competency-milestones] - Capability maturity model progression (Level 1-5) [maturity-model] #### UC-E-076 / partner-cap-participant-count Ask: How many organisations or stakeholders participate in capacity verification? Answer: pick one Requirement type: scale - 2–5 parties [small] - 6–15 parties [medium] - 16–50 parties [large] - Over 50 parties [enterprise] #### UC-E-076 / partner-cap-decision-freq Ask: How frequently are capacity assessments decisions or records created? Answer: pick one Requirement type: governance - Daily or more [daily] - Weekly [weekly] - Monthly [monthly] - Quarterly or less [quarterly] #### UC-E-076 / credential-issuance-approach Ask: How are training credentials currently issued? Answer: pick one Requirement type: credentials - Centralised issuer (single trusted authority issues credentials) [centralised] - Delegated issuance (authority delegates to field offices/partners) [delegated] - Peer attestation (multiple organisations co-attest) [peer-attestation] - Not sure, need guidance [guidance-needed] ### UC-E-077: Consortium fund allocation tracking Security level: Standard. #### UC-E-077 / consortium-model Ask: What consortium operational model will you use? Answer: pick one Requirement type: governance - Hub-and-spoke (lead agency distributes to partners) [hub-and-spoke] - Equal partnership (all members contribute equally) [equal-partnership] - Tiered membership (different contribution levels) [tiered-membership] - Pooled funding (joint fund managed collaboratively) [pooled-funding] #### UC-E-077 / fund-flow-tracking Ask: At what level of detail will fund flows be tracked? Answer: pick one Requirement type: audit-trail - High-level: monthly consortium-to-partner disbursements only [high-level] - Mid-level: activity-level spending by each partner [mid-level] - Detailed: transaction-level tracking with receipts [detailed] - Real-time: continuous digital recording of all transactions [realtime] #### UC-E-077 / consortium-decision-making Ask: How are major consortium allocation decisions currently made? Answer: pick one Requirement type: governance - Lead organization decides with consultation [lead-decides] - Steering committee consensus with documented decision [committee-consensus] - Member voting with documented results [member-voting] - automated rules formula with no discretionary override [formula-based] #### UC-E-077 / consortium-reporting Ask: Does your donor, government oversight body, or consortium governance require that all allocation decisions and fund flows be transparently documented and auditable? Answer: pick one Requirement type: audit-trail - Quarterly reports to lead donor only [donor-reports] - Monthly dashboard accessible to all consortium members [member-dashboard] - Public annual report with anonymized activity data [public-report] - Real-time public register of all fund flows and decisions [public-ledger] #### UC-E-077 / consortium-participant-count Ask: How many organisations or stakeholders participate in consortium fund allocation? Answer: pick one Requirement type: scale - 2–5 parties [small] - 6–15 parties [medium] - 16–50 parties [large] - Over 50 parties [enterprise] #### UC-E-077 / accounting-integration Ask: How should this solution integrate with your existing accounting or financial systems? Answer: pick one Requirement type: integration - Direct integration with your existing accounting software [direct-erp] - Export-based: generate reports compatible with our accounting system [export-based] - Standalone ledger with manual reconciliation [standalone] - Not sure, need guidance on accounting integration [guidance-needed] ### UC-E-078: Inter-agency coordination records Security level: Standard. #### UC-E-078 / agency-count Ask: How many organisations need to coordinate through this system? Answer: pick one Requirement type: scale - 2–5 agencies [small] - 6–20 agencies [medium] - 21–50 agencies [large] - 50+ agencies [very-large] #### UC-E-078 / assistance-types Ask: What types of assistance need to be tracked across agencies? Answer: pick all that apply Requirement type: general - Cash and voucher assistance (CVA) [cash] - Food distribution [food] - Shelter and NFI [shelter] - Health services [health] - Education [education] - Protection services [protection] #### UC-E-078 / data-sovereignty-model Ask: What data sovereignty model is required? Answer: pick one Requirement type: residency. Hard gate: yes - Each agency controls their own data; shared layer shows only deduplication hashes [hash-only] - Shared layer shows assistance type and date but not beneficiary details [metadata-shared] - Full data sharing with role-based access controls [full-sharing] - Configurable per agency (some share more, some less) [configurable] #### UC-E-078 / existing-coordination Ask: What existing coordination mechanisms does this need to integrate with? Answer: pick all that apply Requirement type: integration - OCHA cluster coordination system [ocha] - Bilateral data sharing agreements between specific agencies [bilateral] - Existing beneficiary registration systems [registration-systems] - No existing coordination mechanisms [none] #### UC-E-078 / beneficiary-consent-model Ask: How will beneficiary consent for data sharing across agencies be managed? Answer: pick one Requirement type: privacy - Opt-in: beneficiaries explicitly consent to cross-agency data sharing [opt-in] - Opt-out: sharing is default with right to withdraw [opt-out] - No personal data shared, only anonymised/hashed records on shared layer [no-pii] - Granular consent per agency and data type [granular] ### UC-E-079: Digital public goods infrastructure Security level: Standard. #### UC-E-079 / infrastructure-type Ask: What type of shared infrastructure is being built? Answer: pick one Requirement type: general - Shared identity registry (multiple agencies verify against) [identity] - Shared beneficiary status system (coordination layer) [beneficiary-status] - Open credential framework (portable across organisations) [credentials] - Shared data infrastructure (common data layer) [data-layer] - Shared payment infrastructure (common settlement rail) [payment] #### UC-E-079 / governance-model-dpg Ask: How will the shared infrastructure be governed? Answer: pick one Requirement type: governance - Equal voice: each partner has the same say (consortium model) [equal-voice-each-partner-has-the-same-sa] - Independent governing body makes decisions (foundation model) [independent-governing-body-makes-decisio] - One lead agency with an advisory board of partners [one-lead-agency-with-an-advisory-board-o] - Not sure, need guidance on governance structure [not-sure-need-guidance-on-governance-str] #### UC-E-079 / sustainability-funding Ask: How will the infrastructure be funded and sustained long-term? Answer: pick one Requirement type: money - Donor-funded with transition plan to self-sustaining [donor-transition] - Usage-based fees from participating organisations [usage-fees] - Government-funded as national digital infrastructure [government] - Open-source community maintained [open-source] #### UC-E-079 / interop-standards Ask: Which interoperability standards should the infrastructure align with? Answer: pick all that apply Requirement type: integration - UN agencies (OCHA, UNHCR, WFP systems) [un-agencies-ocha-unhcr-wfp-systems-] - Government registries and national databases [government-registries-and-national-datab] - Other NGO and civil society systems [other-ngo-and-civil-society-systems] - Health information systems [health-information-systems] - Multiple types: need broad compatibility [multiple-types-need-broad-compatibility] - Not sure, need guidance [not-sure-need-guidance] #### UC-E-079 / data-protection-model Ask: What data protection framework applies to the shared infrastructure? Answer: pick one Requirement type: general - GDPR or equivalent national data protection law [gdpr] - Humanitarian data protection principles (OCHA, ICRC) [humanitarian] - Multiple jurisdictions: need federated compliance [multi-jurisdiction] - No formal framework yet, need to establish [none] ### UC-E-080: Board decision recording and verification Security level: Standard. #### UC-E-080 / board-attestation-depth Ask: What level of director attestation do you need for recorded decisions? Answer: pick one Requirement type: credentials - Simple signed minutes (one signer per meeting) [simple] - Per-director vote recording (each director signs their vote) [per-director] - Full smart-contract quorum with auto-executed consequences [smart-contract] #### UC-E-080 / board-confidentiality Ask: What confidentiality requirements apply to board decisions? Answer: pick one Requirement type: privacy - Decisions are public once passed [public] - Decisions public; rationales confidential to directors + auditors [hybrid] - All content confidential (HR, safeguarding, commercial) [confidential] #### UC-E-080 / board-jurisdictions Ask: Are directors in multiple legal jurisdictions with different attestation / e-signature laws? Answer: pick one Requirement type: residency - Single jurisdiction: one e-signature regime [single] - 2-5 jurisdictions [multi-small] - 6+ jurisdictions with complex cross-border rules [multi-large] #### UC-E-080 / board-auto-consequences Ask: Do board decisions need to trigger downstream actions automatically? Answer: pick one Requirement type: general - No, decisions are recorded; execution is manual [manual] - Some decisions trigger specific downstream actions (e.g., payments above threshold) [selective] - Most decisions execute programmatically (DAO-style governance) [programmatic] #### UC-E-080 / board-audience-audit Ask: Who needs verifiable access to the decision record? Answer: pick one Requirement type: audit-trail - Internal audit only [internal] - Internal + donors / funders with stake [donor] - Internal + regulators + donors + public (where consented) [full] ### UC-E-081: Policy version control and attestation Security level: Standard. #### UC-E-081 / policy-scope Ask: Which policy categories will use cryptographic attestation? Answer: pick one Requirement type: general - Safeguarding / PSEA only [safeguarding] - HR, safeguarding, and code of conduct [hr-core] - All staff-facing and partner-facing policies (comprehensive) [comprehensive] #### UC-E-081 / policy-attestor-pop Ask: Roughly how many people need to attest? Answer: pick one Requirement type: scale - Under 100 [small] - 100-1,000 [medium] - 1,000-10,000 [large] - Over 10,000 (large INGO with partners) [massive] #### UC-E-081 / policy-portability Ask: Do attestations need to be portable across organisations (e.g., consortium-wide safeguarding)? Answer: pick one Requirement type: general - No, internal only [internal] - Yes, consortium-wide recognition [consortium] - Yes, sector-wide (e.g., CHS Alliance safeguarding passport) [sector] #### UC-E-081 / policy-renewal-rigour Ask: How rigorously do attestations need to be renewed? Answer: pick one Requirement type: general - Annual blanket re-attestation [annual] - Event-driven (on policy change) + annual floor [event-driven] - Continuous attestation with expiry enforcement [continuous] #### UC-E-081 / policy-proof-target Ask: Who needs to verify attestation status? Answer: pick one Requirement type: audit-trail - HR and compliance team only [internal] - Donors / funders during audit [donor] - Regulators + donors + public (where appropriate) [multi] ### UC-E-082: Conflict of interest declaration management Security level: Standard. #### UC-E-082 / coi-declarant-scope Ask: Who is required to submit CoI declarations? Answer: pick one Requirement type: general - Trustees / directors only [trustees] - Trustees + senior leadership [senior] - Trustees + leadership + all grant-decision staff [comprehensive] #### UC-E-082 / coi-confidentiality Ask: What level of confidentiality applies to declaration content? Answer: pick one Requirement type: privacy - Public register: declarations fully visible [public] - Confidential, only regulators and internal compliance see full text [confidential] - Layered: public declaration-of-existence + confidential detail [layered] #### UC-E-082 / coi-auto-recusal Ask: Should declared conflicts automatically block the declarant from affected decisions? Answer: pick one Requirement type: general - Manual: declaration is recorded; recusal is human-managed [manual] - Advisory: system flags potential conflicts for humans to review [advisory] - Programmatic: smart-contract blocks the declarant from signing [programmatic] #### UC-E-082 / coi-renewal Ask: How often must declarations be refreshed? Answer: pick one Requirement type: general - Annual [annual] - On material change only [material-change] - Both annual and on change [both] #### UC-E-082 / coi-audit-target Ask: Who audits the declaration register? Answer: pick one Requirement type: audit-trail - Internal audit only [internal] - External auditor + internal [external] - Regulator + external auditor + donor (layered) [multi] ### UC-E-083: Standards compliance and accreditation certification Security level: Standard. #### UC-E-083 / standards-portfolio Ask: How many standards certifications does your organisation maintain? Answer: pick one Requirement type: general - 1-2 (single primary standard) [small] - 3-5 (mix of sector and quality standards) [medium] - 6+ (comprehensive certification programme) [large] #### UC-E-083 / standards-certifier-relationship Ask: Are the standards bodies ready to issue blockchain credentials, or is the NGO self-attesting? Answer: pick one Requirement type: governance - Self-attestation + hash-anchor [self-attest] - Hybrid: standards body issues certificate, NGO anchors on blockchain [hybrid] - Standards body native VC issuance [native] #### UC-E-083 / standards-evidence-privacy Ask: How should the audit evidence underlying a certification be handled? Answer: pick one Requirement type: privacy - Public: full evidence open [public] - Private: evidence confidential, only certification status public [private] - Selective: evidence selectively disclosed to specific auditors [selective] #### UC-E-083 / standards-renewal-burden Ask: How disruptive are current certification renewal cycles? Answer: pick one Requirement type: general - Manageable: standard annual audit [manageable] - Heavy: audit windows disrupt operations [heavy] - Severe: certification lapses have caused funding freezes [severe] #### UC-E-083 / standards-verifier-audience Ask: Who most frequently needs to verify your certification status? Answer: pick one Requirement type: general - Donors during grant-making [donors] - Partners during consortium formation [partners] - Public-facing (published compliance dashboard) [public] ### UC-E-084: Shared implementing-partner due diligence and sanctions screening Security level: Standard. #### UC-E-084 / dd-scope Ask: Which DD domains are in scope for sharing? Answer: pick one Requirement type: general - Sanctions screening only [sanctions] - Sanctions + corporate registry + basic governance [basic] - Comprehensive (sanctions + governance + financial + safeguarding + track record) [comprehensive] #### UC-E-084 / dd-consortium-reach Ask: Which agencies contribute to and consume shared DD? Answer: pick one Requirement type: general - Small consortium (2-5 peer agencies) [small] - Medium consortium (6-15 agencies) [medium] - Sector-wide (16+ agencies or UN-family) [sector] #### UC-E-084 / dd-finding-sensitivity Ask: How are agency-specific DD findings handled? Answer: pick one Requirement type: general - Open: all findings shared as-is [open] - Outcome-shared, evidence-confidential [outcome-only] - Tiered (outcome public, evidence per-agency only) [tiered] #### UC-E-084 / dd-refresh-model Ask: How often is DD refreshed? Answer: pick one Requirement type: general - Annual blanket refresh [annual] - Risk-based (high-risk partners more often) [risk-based] - Continuous monitoring (real-time sanctions + event-triggered) [continuous] #### UC-E-084 / dd-partner-control Ask: Can the partner itself see and present their DD status? Answer: pick one Requirement type: general - No, agency-only visibility [agency-only] - Partial, partner sees rating but not findings [partial] - Full: partner holds DD credential and presents selectively [full] ### UC-E-085: Anticipatory action trigger proof Security level: Higher. #### UC-E-085 / trigger-type Ask: Which kinds of events should trigger action? Answer: pick all that apply Requirement type: general - Drought (rainfall, NDVI, soil moisture) [drought] - Flood (river levels, satellite, forecast rainfall) [flood] - Storm and cyclone (forecast track + intensity) [storm] - Conflict-displacement (population movement) [displacement] - Food insecurity (IPC, market price spikes) [food-insecurity] - Disease outbreak surveillance [disease-outbreak] #### UC-E-085 / data-provider Ask: Which data sources will confirm an event? Answer: pick all that apply Requirement type: general - Famine early-warning system [fews-net] - IPC (Integrated Food Security Phase Classification) [ipc] - UN-OCHA / Centre for Humanitarian Data [ocha] - National meteorological service [met-service] - Commercial satellite providers [satellite-commercial] - Academic research institutes [research-institute] #### UC-E-085 / oracle-attestation Ask: How will the data be confirmed before money moves? Answer: pick one Requirement type: credentials - Data provider attests directly [data-provider-attests] - Third-party aggregator attests on provider's behalf [third-party-aggregator] - Multi-source quorum (median or majority of sources) [multi-source-quorum] - Manual attestation by authorised partner [manual-attestation] #### UC-E-085 / rule-specification Ask: How will the trigger rule be written? Answer: pick one Requirement type: general - Simple threshold (e.g. rainfall < X mm) [simple-threshold] - Compound rule (multiple thresholds + windows) [compound] - Model-based (forecast model output) [model-based] - Bespoke partner-agreed rule [bespoke] #### UC-E-085 / disbursement-amount-mechanism Ask: How will the amount per household be set? Answer: pick one Requirement type: money - Flat amount per household [flat-per-household] - Tiered by trigger severity [tiered-by-severity] - Scaled by historical loss data [scaled-by-historical] - Manual allocation per case [manual-allocation] #### UC-E-085 / disbursement-rail Ask: How will the money reach people? Answer: pick one Requirement type: money - Direct mobile money to beneficiary [direct-mobile-money] - Vendor-redeemable voucher [vendor-voucher] - CSO float for distribution [cso-float] - Partner cooperative or government channel [partner-cooperative] #### UC-E-085 / pre-positioned-fund-status Ask: Is the money already set aside? Answer: pick one Requirement type: general - Yes, fund pre-positioned and ready [yes-funded] - Partially funded; gap to close [partially] - Planned; not yet funded [planned] - Not yet a pre-positioned fund, anticipatory action cannot fire [not-yet] #### UC-E-085 / override-rights Ask: Who can stop or change a payout? Answer: pick one Requirement type: governance - No override, automated only [none] - Partner organisations can veto activation [partner-veto] - Donor must confirm before disbursement [donor-confirmation] - Two-step: trigger fires, partner confirms, then disburse [two-step] #### UC-E-085 / partner-coordination-strength Ask: How well do partners agree on the trigger? Answer: pick one Requirement type: governance - Strong: formal coordination mechanism [strong] - Moderate: bilateral agreements [moderate] - Weak: informal alignment only [weak] - Absent: partners cannot agree on shared trigger [absent] #### UC-E-085 / waqf-integration Ask: Is an endowment (waqf) part of the funding? Answer: pick one Requirement type: integration - No waqf component [none] - Planning waqf-financed pool [planned] - Waqf is the primary financing mechanism [active] ### UC-F-080: Transparent fund flow tracking Security level: Standard. #### UC-F-080 / transparency-stakeholders Ask: Who needs to access the fund flow transparency information? Answer: pick one Requirement type: usability - Individual donors only (personal dashboard) [individual-donors] - Regulators and compliance teams [regulators-compliance] - Public transparency (digital ledger published) [public-blockchain] - Multi-stakeholder (donors + regulators + public) [multi-stakeholder-tiered] #### UC-F-080 / reporting-frequency Ask: What reporting frequency is needed for fund flow updates? Answer: pick one Requirement type: audit-trail - Real-time digital settlement (minutes) [realtime-settlement] - Daily batched reports [daily-batch] - Weekly consolidated summary [weekly-consolidated] #### UC-F-080 / multi-currency-support Ask: What currencies do you currently need to support in your operations? Answer: pick one Requirement type: money - Single base currency (convert at intake) [single-base-currency] - Preserve original currency (dual-track accounting) [preserve-original-currency] - Stablecoin bridge (normalising across stablecoins) [stablecoin-bridge] #### UC-F-080 / donor-access-permissions Ask: What control should donors have over their fund flow data visibility? Answer: pick one Requirement type: legal-checks - Full donor control (opt-in transparency) [donor-opt-in-control] - Organization-wide transparency policy [org-policy-transparency] - Regulatory requirement (mandatory disclosure) [regulatory-mandatory] #### UC-F-080 / beneficiary-choice Ask: How will beneficiaries exercise choice in how they receive and use this service? Answer: pick one Requirement type: general - Beneficiaries choose between delivery methods (cash, voucher, mobile money, direct) [delivery-choice] - Beneficiaries choose preferred merchants or service points [merchant-choice] - Beneficiaries control their own data sharing preferences [data-choice] - Multiple choice dimensions (delivery + merchant + data) [full-choice] - Limited choice: programme constraints determine delivery [limited] ### UC-F-081: Fractional and micro-donation enabling Security level: Standard. #### UC-F-081 / minimum-donation-amount Ask: What is the minimum donation amount to support? Answer: pick one Requirement type: general - Micro-donations ($0.01 - $0.99) [micro-cent-level] - Small donations ($1 - $10) [small-amount] - Fractional shares of larger campaigns ($0.50 - $5 per share) [fractional-share-pooling] #### UC-F-081 / supported-payment-methods Ask: Which payment methods should be supported for micro-donations? Answer: pick one Requirement type: money - Fiat credit/debit card gateway [fiat-card-gateway] - Cryptocurrency wallet direct transfer [crypto-wallet-direct] - Mobile money [mobile-money-integration] - Multi-method support (hybrid) [hybrid-multi-method] #### UC-F-081 / micro-donation-compliance Ask: What financial compliance requirements apply to micro-donations? Answer: pick all that apply Requirement type: legal-checks - Tax deductibility receipting [tax] - Anti-money laundering (AML) / Know Your Donor [aml] - Cross-border fund transfer regulations [cross-border] - Cryptocurrency-specific regulations [crypto-reg] - No specific compliance requirements [none] #### UC-F-081 / sq-UC-F-089-001 Ask: What is the minimum amount and frequency needed before donor funds should be available to beneficiaries (e.g., daily threshold, weekly batching)? Answer: pick one Requirement type: general - Fixed threshold release [fixed-threshold-release] - Time-based batching [time-based-batching] - Project goal reached [project-goal-reached] - Donor-directed timing [donor-directed-timing] - Hybrid threshold and time [hybrid-threshold-and-time] #### UC-F-081 / beneficiary-choice Ask: How will beneficiaries exercise choice in how they receive and use this service? Answer: pick one Requirement type: general - Beneficiaries choose between delivery methods (cash, voucher, mobile money, direct) [delivery-choice] - Beneficiaries choose preferred merchants or service points [merchant-choice] - Beneficiaries control their own data sharing preferences [data-choice] - Multiple choice dimensions (delivery + merchant + data) [full-choice] - Limited choice: programme constraints determine delivery [limited] ### UC-F-082: Cryptocurrency and digital asset donations Security level: Standard. #### UC-F-082 / crypto-conversion-strategy Ask: If you received cryptocurrency, how would you want to convert it to usable currency? Answer: pick one Requirement type: general - Immediate conversion at receipt (minimize volatility exposure) [immediate-conversion] - Time-delayed conversion (batched weekly/monthly) [batched-delayed-conversion] - Donor choice (keep crypto or auto-convert) [donor-choice-conversion] - automated escrow (hold crypto for time-release) [escrow-time-release] #### UC-F-082 / kyc-aml-requirements Ask: What KYC/AML compliance is required for crypto donations? Answer: pick one Requirement type: legal-checks. Hard gate: yes - No KYC (permissionless acceptance) [no-kyc-permissionless] - Light KYC (name + email verification) [light-kyc-basic] - Full KYC (identity + source of funds verification) [full-kyc-comprehensive] - Tiered KYC (escalating requirements by amount) [tiered-kyc-progressive] #### UC-F-082 / volatility-hedging-strategy Ask: What approach would you prefer for managing volatility risk from cryptocurrency donations? Answer: pick one Requirement type: money - No hedging (accept volatility risk) [no-hedging-accept-risk] - Immediate stablecoin conversion (pass risk to exchange) [immediate-stablecoin] - Futures/options hedge (advanced derivatives) [derivatives-hedge] - Donor contribution to volatility buffer fund [volatility-buffer-pool] #### UC-F-082 / tax-compliance-reporting Ask: What tax compliance and reporting approach would you need for cryptocurrency donations? Answer: pick one Requirement type: legal-checks - Donor-managed tax compliance (no org reporting) [donor-self-report] - Automated donor tax reports (1098-C style) [automated-donor-tax-reports] - FMV assessment + org reporting (IRS Form 8949) [fmv-assessment-org-reporting] - Automated tax calculations [smart-contract-tax-automation] - Stablecoin-only (simplified tax treatment) [stablecoin-simplified-tax] #### UC-F-082 / crypto-acceptance-count Ask: How many different cryptocurrencies/tokens does the NGO need to accept? Answer: pick one Requirement type: scale - Major coins only [major-only] - Top 10–20 cryptocurrencies [top-20] - Wide acceptance (50+ tokens including ERC-20s) [wide] - All major chains and tokens (80+) [all] #### UC-F-082 / conversion-strategy-detail Ask: What is the conversion strategy for received crypto donations? Answer: pick one Requirement type: general - Immediate conversion to fiat (minimise volatility risk) [immediate-fiat] - Immediate conversion to stablecoin (held as a regulated stablecoin) [immediate-stable] - Hold as crypto with periodic conversion [hold-periodic] - Hybrid: immediate conversion for operations, hold portion as reserve [hybrid] #### UC-F-082 / aml-screening-donations Ask: What AML/sanctions screening is needed for donation source addresses? Answer: pick one Requirement type: legal-checks. Hard gate: yes - Full digital analytics screening of all incoming addresses [full-screening] - Screening above a threshold amount [threshold] - Basic sanctions list check only [basic] - Unsure, need compliance guidance [unsure] #### UC-F-082 / tax-receipt-requirements Ask: What tax receipt/documentation requirements exist for crypto donations? Answer: pick one Requirement type: legal-checks. Hard gate: yes - Must issue tax receipts with fair market value at time of donation [full-receipt] - Tax receipt needed only for donations above a threshold [threshold-receipt] - No tax receipt requirement (jurisdiction doesn't recognise crypto donations) [no-receipt] - Multiple jurisdictions with different requirements [multi-jurisdiction] #### UC-F-082 / donation-channel Ask: Is the NGO accepting crypto donations directly or through a third-party processor? Answer: pick one Requirement type: general - Direct: NGO manages its own donation wallets [direct] - Third-party processor handles acceptance and conversion [third-party] - Hybrid: direct for major coins, processor for others [hybrid] - Undecided: need to evaluate options [undecided] #### UC-F-082 / beneficiary-choice Ask: How will beneficiaries exercise choice in how they receive and use this service? Answer: pick one Requirement type: general - Beneficiaries choose between delivery methods (cash, voucher, mobile money, direct) [delivery-choice] - Beneficiaries choose preferred merchants or service points [merchant-choice] - Beneficiaries control their own data sharing preferences [data-choice] - Multiple choice dimensions (delivery + merchant + data) [full-choice] - Limited choice: programme constraints determine delivery [limited] ### UC-F-083: Impact verification tied to specific donations Security level: Standard. #### UC-F-083 / impact-measurement-methodology Ask: What methodology should be used to measure and attribute impact? Answer: pick one Requirement type: credentials - Output metrics (direct deliverables counted) [output-metrics-direct] - Outcome metrics (beneficiary behavior change) [outcome-metrics-behavior] - Cost per impact unit ($/life saved, $/QALYs) [cost-per-impact-unit] - Theory of Change pathway (logical chain) [theory-of-change-pathway] - Randomized controlled trials (RCT gold standard) [rct-gold-standard] #### UC-F-083 / impact-verification-method Ask: What method would you prefer for verifying impact outcomes? Answer: pick one Requirement type: credentials - Self-reported by beneficiaries (lowest cost) [self-reported-beneficiary] - Field staff verification (direct observation) [field-staff-observation] - Third-party independent verification [third-party-independent] - Digitally recorded data (tamper-proof verification) [blockchain-onchain-data] - Sensor/IoT data (environmental measurement) [sensor-iot-data] #### UC-F-083 / third-party-verification-involvement Ask: What role should third parties play in impact verification? Answer: pick one Requirement type: credentials - No third party (organization self-reports) [no-third-party-self-report] - Advisory role (review and guidance only) [advisory-guidance-only] - Audit role (independent verification + certification) [audit-certification] - Collaborative partnership (shared measurement) [collaborative-partnership] #### UC-F-083 / impact-data-granularity Ask: How granular should impact data be linked to individual donations? Answer: pick one Requirement type: credentials - Aggregate program level (donor sees program outcome only) [aggregate-program-level] - Beneficiary cohort level (my $100 helped X people) [beneficiary-cohort-level] - Individual beneficiary linkage (donor identifies person) [individual-beneficiary-link] - Outcome timeline (track beneficiary progress over months) [outcome-timeline-tracking] #### UC-F-083 / impact-verification-timeline Ask: When should impact verification be conducted relative to the donation? Answer: pick one Requirement type: audit-trail - Immediate (within 30 days of program delivery) [immediate-30-days] - Medium-term (3-6 months post-delivery) [medium-term-3-6-months] - Long-term (12+ months for sustained impact) [longterm-12-plus-months] - Ongoing real-time monitoring (continuous verification) [ongoing-realtime-monitoring] #### UC-F-083 / beneficiary-choice Ask: How will beneficiaries exercise choice in how they receive and use this service? Answer: pick one Requirement type: general - Beneficiaries choose between delivery methods (cash, voucher, mobile money, direct) [delivery-choice] - Beneficiaries choose preferred merchants or service points [merchant-choice] - Beneficiaries control their own data sharing preferences [data-choice] - Multiple choice dimensions (delivery + merchant + data) [full-choice] - Limited choice: programme constraints determine delivery [limited] ### UC-F-084: Automated donor reporting Security level: Standard. #### UC-F-084 / report-frequency Ask: How frequently should donor reports be generated and delivered? Answer: pick one Requirement type: audit-trail - Real-time (immediate after each transaction) [realtime-per-transaction] - Daily summary reports [daily-summary] - Monthly consolidated report [monthly-consolidated] - Annual impact report with year-end tax documentation [annual-tax-compliant] #### UC-F-084 / report-format Ask: What formats should reports be delivered in? Answer: pick one Requirement type: audit-trail - Email summaries (text-based) [email-text-summary] - Dashboard portal (self-service web view) [dashboard-portal] - PDF downloadable documents [pdf-downloadable] - Multi-format (email + dashboard + PDF) [multi-format-comprehensive] #### UC-F-084 / report-personalization Ask: How personalized should donor reports be? Answer: pick one Requirement type: audit-trail - Generic template (same report for all donors) [generic-template] - Donation-specific (show only my donations and impact) [donation-specific-personalized] - Preference-based (donor selects what to see) [preference-based-choice] - AI-personalized (ML-optimized content per donor) [ai-personalized-ml] #### UC-F-084 / sq-UC-F-089-001 Ask: What impact metrics should be automatically calculated and included in reports? Answer: pick one Requirement type: general - Beneficiary reach [beneficiary-reach] - Cost per outcome [cost-per-outcome] - Programme milestones [programme-milestones] - Geographic coverage [geographic-coverage] - Custom donor KPIs [custom-donor-kpis] ### UC-F-085: Crowdfunding with built-in accountability Security level: Standard. #### UC-F-085 / milestone-based-model Ask: What milestones do you currently track in your programmes for outcome-based funding? Answer: pick one Requirement type: general - Fixed milestones (50% at design, 50% at delivery) [fixed-milestone-tranches] - Measurable outcome milestones (verified deliverables) [measurable-outcome-verified] - Flexible tranches (campaign decides schedule) [flexible-campaign-defined] #### UC-F-085 / escrow-mechanism Ask: Should funds be held in escrow until milestones are met? Answer: pick one Requirement type: general - Full escrow (all funds held until final milestone) [full-escrow-final] - Milestone escrow (held until each milestone met) [milestone-escrow-progressive] - No escrow (funds released immediately) [no-escrow-immediate-release] #### UC-F-085 / crowdfund-compliance Ask: What financial compliance requirements apply to crowdfunding? Answer: pick all that apply Requirement type: legal-checks - Tax deductibility receipting [tax] - Anti-money laundering (AML) / Know Your Donor [aml] - Cross-border fund transfer regulations [cross-border] - Cryptocurrency-specific regulations [crypto-reg] - No specific compliance requirements [none] #### UC-F-085 / sq-UC-F-089-001 Ask: What happens to funds if a campaign fails to reach its goal? Answer: pick one Requirement type: general - Full refund [full-refund] - Partial allocation to cause [partial-allocation] - Donor choice to redirect [donor-choice-redirect] - Keep for mission [keep-for-mission] - Escrow until decision [escrow-until-decision] #### UC-F-085 / payment-gateway-type Ask: What type of payment gateway is needed for donations? Answer: pick one Requirement type: money - Crypto-native payment gateway (accept crypto donations directly) [crypto-native] - Fiat-to-crypto gateway (donors pay in fiat, converted to crypto) [fiat-to-crypto] - Multi-currency gateway (accept both fiat and crypto) [multi-currency] - Not sure, need guidance [guidance-needed] #### UC-F-085 / beneficiary-choice Ask: How will beneficiaries exercise choice in how they receive and use this service? Answer: pick one Requirement type: general - Beneficiaries choose between delivery methods (cash, voucher, mobile money, direct) [delivery-choice] - Beneficiaries choose preferred merchants or service points [merchant-choice] - Beneficiaries control their own data sharing preferences [data-choice] - Multiple choice dimensions (delivery + merchant + data) [full-choice] - Limited choice: programme constraints determine delivery [limited] ### UC-F-086: Corporate giving with verified impact metrics Security level: Standard. #### UC-F-086 / impact-granularity-corporate Ask: How granular should impact reporting be for corporate donors? Answer: pick one Requirement type: credentials - High-level summary (total contribution + 1 headline outcome) [highlevel-summary-1outcome] - Detailed program impact (contributions + multiple outcomes) [detailed-program-impact] - Beneficiary-level detail (individual stories + metrics) [beneficiary-level-detail] - Real-time dashboard (live tracking of all contributions) [realtime-live-dashboard] #### UC-F-086 / audit-reporting-requirements Ask: What audit and reporting requirements should be met? Answer: pick one Requirement type: legal-checks - Annual financial audit (standard nonprofit requirement) [annual-financial-audit] - Enhanced impact audit (financial + impact verification) [enhanced-impact-audit] - Continuous compliance monitoring (quarterly checks) [continuous-quarterly-monitoring] - Real-time digital audit trail (permanent tamper-proof record) [realtime-blockchain-audit] #### UC-F-086 / corporate-reporting-channels Ask: What reporting channels do your corporate donors require for ESG? Answer: pick one Requirement type: audit-trail - Annual impact report (printed + PDF) [annual-report-print-pdf] - Interactive web dashboard (real-time metrics) [interactive-dashboard-realtime] - ESG report integration (embedded in corporate ESG reporting) [esg-report-integration] - Multi-channel (annual + dashboard + custom reports) [multichannel-comprehensive] ### UC-F-087: Recurring donation automation Security level: Standard. #### UC-F-087 / payment-scheduling Ask: What payment scheduling options should be offered? Answer: pick one Requirement type: money - Fixed monthly amounts (monthly recurring) [monthly-fixed-amount] - Flexible frequency (weekly/bi-weekly/monthly/quarterly) [flexible-frequency-choice] - Variable amounts (fixed schedule, donor can adjust) [variable-amount-adjustable] - Smart scheduling (AI-optimized gift timing) [smart-ai-optimized-timing] #### UC-F-087 / donor-management-features Ask: What donor management capabilities do you currently have? Answer: pick one Requirement type: general - Basic (pause/resume/cancel) [basic-pause-resume-cancel] - Advanced (pause/resume/change amount/change frequency) [advanced-full-control] - Premium (all + scheduled changes + seasonal adjustments) [premium-scheduling-advanced] #### UC-F-087 / retention-engagement-features Ask: What features support donor retention and engagement? Answer: pick one Requirement type: privacy - Milestone notifications (donor sees impact of their giving) [milestone-impact-notifications] - Incentive rewards (matching, tiers, badges) [incentive-rewards-gamified] - Personalized engagement (content + timing tailored to donor) [personalized-engagement] - Community features (connect with other donors) [community-donor-network] #### UC-F-087 / recurring-compliance Ask: What financial compliance requirements apply to recurring donations? Answer: pick all that apply Requirement type: legal-checks - Tax deductibility receipting [tax] - Anti-money laundering (AML) / Know Your Donor [aml] - Cross-border fund transfer regulations [cross-border] - Cryptocurrency-specific regulations [crypto-reg] - No specific compliance requirements [none] #### UC-F-087 / sq-UC-F-089-003 Ask: What donor communication should be triggered by recurring donation events? Answer: pick one Requirement type: usability - Monthly impact update [monthly-impact-update] - Annual summary [annual-summary] - Milestone notifications [milestone-notifications] - Minimal receipt only [minimal-receipt-only] - Personalised story [personalised-story] #### UC-F-087 / beneficiary-choice Ask: How will beneficiaries exercise choice in how they receive and use this service? Answer: pick one Requirement type: general - Beneficiaries choose between delivery methods (cash, voucher, mobile money, direct) [delivery-choice] - Beneficiaries choose preferred merchants or service points [merchant-choice] - Beneficiaries control their own data sharing preferences [data-choice] - Multiple choice dimensions (delivery + merchant + data) [full-choice] - Limited choice: programme constraints determine delivery [limited] ### UC-F-088: Donor-advised fund integration Security level: Standard. #### UC-F-088 / daf-platform-integration Ask: Which DAF platform do you currently use or plan to use? Answer: pick one Requirement type: integration - API integration (real-time grant recommendations) [api-realtime-integration] - Manual grant requests (DAF sponsor approval workflow) [manual-grant-workflow] - Pre-approved grants (qualified NGO in DAF donor networks) [preapproved-qualified-ngo] - Multi-DAF aggregator (integrated with multiple sponsors) [multi-daf-aggregator] #### UC-F-088 / tax-reporting-for-daf Ask: What are your current tax reporting requirements for DAF transactions? Answer: pick one Requirement type: legal-checks - Standard grant letter (recipient-issued) [standard-grant-letter] - Automated tax forms (1098-T or custom) [automated-tax-forms] - DAF platform handles tax reporting (passthrough) [daf-platform-passthrough] #### UC-F-088 / grant-timing-flexibility Ask: What flexibility should be offered for grant timing? Answer: pick one Requirement type: general - Immediate grants (funds received within days) [immediate-grant-days] - Scheduled grants (NGO proposes timeline) [scheduled-ngo-timeline] - DAF advisor discretion (no fixed timeline) [daf-advisor-discretion] #### UC-F-088 / sq-UC-F-089-001 Ask: Are there high-net-worth individuals in your supporter base who you know use donor-advised funds for charitable giving? Answer: pick one Requirement type: general - Direct API integration [api-direct] - CSV batch upload [csv-batch] - Manual entry [manual-entry] - Payment processor bridge [payment-processor-bridge] - Multi-platform support [multi-platform] #### UC-F-088 / sq-UC-F-089-006 Ask: What reporting back to DAF platforms is required? Answer: pick one Requirement type: legal-checks - Annual expenditure report [annual-expenditure-report] - Real-time utilisation [real-time-utilisation] - Impact narrative [impact-narrative] - Financial statement [financial-statement] - No reporting required [no-reporting-required] ### UC-F-089: Gift matching verification Security level: Standard. #### UC-F-089 / matching-rule-configuration Ask: What are your current matching fund rules and ratios? Answer: pick one Requirement type: general - 1:1 fixed match (every $1 matched by $1) [onetoone-fixed-match] - Tiered matching (higher match % for larger gifts) [tiered-progressive-match] - Budget-capped matching (match until cap reached) [budget-capped-match] - Time-limited matching (match available only during campaign) [time-limited-campaign-match] #### UC-F-089 / match-verification-method Ask: How do you currently verify that matching fund requirements are met? Answer: pick one Requirement type: credentials - Manual matcher attestation (honor system) [manual-attestation-honor] - Bank transfer verification (match funds confirmed received) [bank-transfer-confirmed] - Automated escrow (match funds locked until verified) [smart-contract-escrow] - Third-party matcher verification (independent confirmation) [third-party-verification] #### UC-F-089 / matcher-management Ask: How do you currently manage and track matching fund providers? Answer: pick one Requirement type: general - Single corporate matcher (one sponsor) [single-corporate-matcher] - Multiple individual matchers (crowdsourced matching) [multiple-individual-matchers] - Matching pool (aggregated from multiple sources) [matching-pool-aggregated] #### UC-F-089 / gift-match-compliance Ask: What financial compliance requirements apply to gift matching? Answer: pick all that apply Requirement type: legal-checks - Tax deductibility receipting [tax] - Anti-money laundering (AML) / Know Your Donor [aml] - Cross-border fund transfer regulations [cross-border] - Cryptocurrency-specific regulations [crypto-reg] - No specific compliance requirements [none] #### UC-F-089 / sq-UC-F-089-003 Ask: What verification is needed to confirm the matcher has actually transferred matched funds? Answer: pick one Requirement type: legal-checks - Bank confirmation [bank-confirmation] - Digital verification [blockchain-verification] - Matcher attestation [matcher-attestation] - Third-party escrow [third-party-escrow] - Trust-based [trust-based] #### UC-F-089 / matching-engine-type Ask: How does gift matching currently work for this fundraising solution? Answer: pick one Requirement type: general - Automated 1:1 matching (each gift auto-matched) [auto-1to1] - Pool-based matching (matching fund pool, allocated proportionally) [pool-based] - Tiered matching (different match rates based on criteria) [tiered] - Not sure, need guidance [guidance-needed] #### UC-F-089 / beneficiary-choice Ask: How will beneficiaries exercise choice in how they receive and use this service? Answer: pick one Requirement type: general - Beneficiaries choose between delivery methods (cash, voucher, mobile money, direct) [delivery-choice] - Beneficiaries choose preferred merchants or service points [merchant-choice] - Beneficiaries control their own data sharing preferences [data-choice] - Multiple choice dimensions (delivery + merchant + data) [full-choice] - Limited choice: programme constraints determine delivery [limited] ### UC-F-090: Donor identity verification for anti-money laundering compliance Security level: Standard. #### UC-F-090 / kyc-depth Ask: What level of donor due diligence is required? Answer: pick one Requirement type: legal-checks. Hard gate: yes - Light: basic identity capture, threshold-triggered verification [light] - Standard CDD: ID verification and sanctions screening at onboarding [standard-cdd] - Enhanced CDD for high-risk donors [ecdd] - Continuous: ongoing monitoring and re-verification [continuous] #### UC-F-090 / verification-source Ask: Where does the identity verification evidence come from? Answer: pick one Requirement type: credentials - Self-declared identity with no verification [self] - Government ID with manual review [gov-id-manual] - Commercial identity-verification provider [commercial] - Verifiable credentials from accredited issuers [vc] #### UC-F-090 / credential-model Ask: How should verified-donor status be represented? Answer: pick one Requirement type: credentials - Centralised database record (legacy KYC) [centralised] - Portable verifiable credential in donor-held wallet [vc-portable] - Zero-knowledge proof (prove verified, don't expose identity) [zk] - Hybrid: centralised record + ZK proof for public-chain donations [hybrid] #### UC-F-090 / sanctions-screening-frequency Ask: How frequently should sanctions and adverse-media screening run? Answer: pick one Requirement type: legal-checks - Onboarding only [onboarding] - Onboarding + annual re-screen [annual] - Onboarding + quarterly re-screen [quarterly] - Continuous monitoring [continuous] #### UC-F-090 / alert-handling-model Ask: How should AML alerts be handled? Answer: pick one Requirement type: general - Manual case review per alert [manual] - Triage tooling with manual resolution [triage] - Automated low-risk closure + manual escalation [auto-escalation] - Automated blocking with smart-contract enforcement for on-chain donations [smart-contract-block] ### UC-F-091: Pooled fund disbursement tracking (UN-managed funds) Security level: Standard. #### UC-F-091 / pooledfund-depth Ask: How deep into the sub-grantee chain does disbursement tracking need to go? Answer: pick one Requirement type: general - First-tier only (pool → agency) [tier1] - Second-tier (pool → agency → sub-grantee) [tier2] - Full chain to beneficiary (pool → agency → sub-grantee → field → beneficiary) [full] #### UC-F-091 / pooledfund-release-logic Ask: How are disbursements released? Answer: pick one Requirement type: general - Manual approval by pool manager [manual] - Milestone-triggered (released on evidence) [milestone] - Hybrid (milestone + manual override for sensitive cases) [hybrid] #### UC-F-091 / pooledfund-audience Ask: Who audits the disbursement ledger? Answer: pick one Requirement type: audit-trail - Pool governance body (internal) [internal] - Pool governance + external donor audit [external] - Public transparency (IATI-compliant public register) [public] #### UC-F-091 / pooledfund-confidentiality Ask: What confidentiality applies to individual transfers? Answer: pick one Requirement type: privacy - Full transparency [transparent] - Transparent aggregates, confidential specific transfers (e.g., sensitive contexts) [hybrid] - Confidential ledger with aggregate attestations [confidential] #### UC-F-091 / pooledfund-donor-dashboard Ask: What donor interface is required? Answer: pick one Requirement type: usability - Periodic reports (existing IATI format) [report] - Real-time dashboard (donor-facing) [dashboard] - Donor-embedded verifier (donor runs their own verification) [embedded] ### UC-G-090: Early warning systems with automated fund release triggers Security level: Standard. #### UC-G-090 / early-warning-data-sources Ask: What type of early warning data sources are required? Answer: pick one Requirement type: general - Weather/Meteorological data [weather-data] - Seismic/Geological sensors [seismic-data] - Conflict/Security intelligence [conflict-data] #### UC-G-090 / trigger-threshold-setting Ask: For trigger thresholds: do you prefer fixed values set by policy, automatic adjustment based on historical data patterns, or regular expert consensus review? Answer: pick one Requirement type: general - Fixed parametric thresholds (e.g., rainfall >150mm) [fixed-thresholds] - Dynamic thresholds based on historical patterns [dynamic-thresholds] - Expert consensus-based thresholds [consensus-thresholds] #### UC-G-090 / fund-release-speed Ask: What fund release speed is required after trigger activation? Answer: pick one Requirement type: money - Instant (minutes, automated settlement) [instant-release] - Fast (hours, with automated verification) [fast-release] - Moderate (24 hours, with manual final approval) [moderate-release] #### UC-G-090 / false-positive-tolerance Ask: What is acceptable tolerance for false positive triggers? Answer: pick one Requirement type: audit-trail - Very low (<1%): Cost of false trigger is critical [very-low-tolerance] - Low (1-5%): Multiple verification sources required [low-tolerance] - Moderate (5-15%): Speed prioritized over absolute certainty [moderate-tolerance] #### UC-G-090 / multi-trigger-scenarios Ask: Are there multiple independent trigger scenarios? Answer: pick one Requirement type: general - Single trigger: One condition activates release [single-trigger] - Multi-trigger (AND): All conditions must be met [multi-trigger-and] - Multi-trigger (OR): Any condition activates release [multi-trigger-or] #### UC-G-090 / early-warning-source Ask: What data sources should feed the early warning system? Answer: pick one Requirement type: general - Weather and climate data feeds from national or global weather services [climate-data] - Conflict and security data feeds from monitoring services [conflict-data] - Health and epidemic data feeds from public health surveillance services [health-data] - Multiple data sources combined [multi-source] ### UC-G-091: Disaster response fund pre-positioning Security level: Standard. #### UC-G-091 / disaster-types-covered Ask: Which disaster types will trigger fund release? Answer: pick one Requirement type: general - Earthquakes (magnitude-based) [earthquakes] - Cyclones/Hurricanes (wind speed metrics) [cyclones] - Floods (rainfall and water level) [floods] #### UC-G-091 / activation-authority Ask: Who currently has the authority to activate emergency fund releases? Answer: pick one Requirement type: governance - Fully automated on parametric trigger [fully-automated] - multi-party approval from designated organizations [multi-sig] - Government disaster authority (with digital verification) [government-authority] #### UC-G-091 / pre-positioned-fund-amount Ask: 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? Answer: pick one Requirement type: general - Fixed pool per disaster type [fixed-pool] - Needs-based assessment per geographic region [needs-based] - Insurance layer approach with co-insurance [insurance-backed] #### UC-G-091 / deployment-speed Ask: What deployment speed is achievable to disaster areas? Answer: pick one Requirement type: money - Same-day deployment (6-12 hours) [same-day] - 24-48 hour deployment with local coordination [48-hour] - One-week deployment with full beneficiary verification [one-week] #### UC-G-091 / geographic-coverage Ask: What geographic scope will be covered by pre-positioned funds? Answer: pick one Requirement type: general - Single high-risk country/region [single-region] - Multi-country (sub-regional: e.g., Sahel, SE Asia) [sub-regional] - Global network with localized pools [global] #### UC-G-091 / trigger-mechanism Ask: How does automated triggers and fund releases currently work? Answer: pick one Requirement type: general - Oracle-based: external data feeds trigger automated actions [oracle-based] - Threshold-based: predefined conditions trigger automated release [threshold] - multi-party approval: requires multiple parties to authorise [multi-sig] - Hybrid: automated triggers with human override capability [hybrid] #### UC-G-091 / timestamping-approach Ask: How is events and evidence currently timestamped for this solution? Answer: pick one Requirement type: audit-trail - Digital timestamping (each event anchored with tamper-proof proof) [on-chain] - Batch anchoring (events collected, periodically anchored) [batch-anchoring] - Trusted third-party timestamping authority [trusted-authority] - Not sure, need guidance on timestamping approach [guidance-needed] ### UC-G-092: Anticipatory action fund release mechanisms Security level: Standard. #### UC-G-092 / lead-time-requirement Ask: What lead time is available for anticipatory action? Answer: pick one Requirement type: general - Long lead time (2-8 weeks): Crisis predicted well in advance [long-lead] - Medium lead time (1-2 weeks): Shorter warning window [medium-lead] - Very short lead time (24-72 hours): Near real-time [very-short-lead] #### UC-G-092 / beneficiary-identification Ask: When are beneficiaries identified in anticipatory process? Answer: pick one Requirement type: audit-trail - Pre-registered: Beneficiary list confirmed beforehand [pre-registered] - Dynamic identification: Beneficiaries identified post-trigger [dynamic] - Hybrid: Pre-registered with emergency flexibility [hybrid-id] #### UC-G-092 / false-alarm-management Ask: 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? Answer: pick one Requirement type: general - Full refund: Unused funds returned to donor [full-refund] - Contingency reserve: Funds roll to next period/location [contingency-reserve] - Learning investment: Unused funds fund preparedness/training [learning-investment] #### UC-G-092 / trigger-transparency Ask: How transparent is the anticipatory trigger process? Answer: pick one Requirement type: general - Full transparency: All trigger data and decisions digital [full-transparent] - Selective transparency: Trigger logic public, data private [selective] - Confidential: Trigger process withheld to prevent manipulation [confidential] #### UC-G-092 / trigger-mechanism Ask: How does automated triggers and fund releases currently work? Answer: pick one Requirement type: general - Oracle-based: external data feeds trigger automated actions [oracle-based] - Threshold-based: predefined conditions trigger automated release [threshold] - multi-party approval: requires multiple parties to authorise [multi-sig] - Hybrid: automated triggers with human override capability [hybrid] #### UC-G-092 / early-warning-source Ask: What data sources should feed the early warning system? Answer: pick one Requirement type: general - Weather and climate data feeds from national or global weather services [climate-data] - Conflict and security data feeds from monitoring services [conflict-data] - Health and epidemic data feeds from public health surveillance services [health-data] - Multiple data sources combined [multi-source] ### UC-G-093: Climate adaptation financing Security level: Standard. #### UC-G-093 / climate-risk-types Ask: Which climate risks are you targeting for adaptation financing? Answer: pick one Requirement type: audit-trail - Slow-onset risks (sea-level rise, desertification, glacier melt) [slow-onset] - Acute weather events (droughts, floods, heat waves) [acute-weather] - Compound climate risks (multi-hazard cascades) [compound-risks] #### UC-G-093 / adaptation-project-monitoring Ask: How are adaptation project outcomes monitored and verified? Answer: pick one Requirement type: general - On-ground monitoring: Field teams + community reporting [on-ground] - Satellite monitoring: Remote sensing + change detection [satellite] - Hybrid: Satellite baseline + community verification [hybrid-monitoring] #### UC-G-093 / resilience-metrics Ask: What resilience metrics define project success? Answer: pick one Requirement type: audit-trail - Outcome-based: Community resilience scores (survey-driven) [outcome-based] - Impact-based: Ecosystem metrics (NDVI, soil health, water) [impact-based] - Process-based: Activity completion and resource uptake [process-based] #### UC-G-093 / mrv-mechanism Ask: What MRV (Monitoring, Reporting, Verification) structure is employed? Answer: pick one Requirement type: audit-trail - Centralized: Single implementing organization reports [centralized] - distributed: Multiple verification nodes validate [decentralized] - Open MRV: Community validation + transparent digital ledger record [open-mrv] #### UC-G-093 / climate-data-integration Ask: What climate data sources does your adaptation monitoring currently use? Answer: pick one Requirement type: audit-trail - IPCC/UNFCCC data feeds [ipcc-unfccc] - National meteorological/climate agencies [national-agencies] - Peer-reviewed climate datasets from public climate programmes [peer-reviewed] #### UC-G-093 / timestamping-approach Ask: How is events and evidence currently timestamped for this solution? Answer: pick one Requirement type: audit-trail - Digital timestamping (each event anchored with tamper-proof proof) [on-chain] - Batch anchoring (events collected, periodically anchored) [batch-anchoring] - Trusted third-party timestamping authority [trusted-authority] - Not sure, need guidance on timestamping approach [guidance-needed] ### UC-G-094: Conflict-sensitive resource allocation Security level: Higher. #### UC-G-094 / conflict-sensitivity-framework Ask: What conflict sensitivity approach currently guides your allocation decisions? Answer: pick one Requirement type: audit-trail - Do No Harm (CDA) framework [do-no-harm] - OECD DAC conflict sensitivity guidelines [oecd-dac] - Locally-developed framework (community-specific) [local-framework] #### UC-G-094 / do-no-harm-screening Ask: When and how frequently is do-no-harm screening conducted? Answer: pick one Requirement type: general - Pre-implementation: One-time baseline assessment [pre-implementation] - Ongoing: Quarterly or monthly reviews [ongoing-periodic] - Adaptive: Triggered by conflict escalation alerts [adaptive-trigger] #### UC-G-094 / stakeholder-mapping Ask: How many stakeholder groups need to be involved in approval or consultation for allocation decisions? Answer: pick one Requirement type: audit-trail - Basic: Direct beneficiaries + implementing partner [basic-stakeholders] - Extended: All community members + local authorities [extended-stakeholders] - Comprehensive: All actors including armed groups/spoilers [comprehensive-stakeholders] #### UC-G-094 / grievance-mechanism Ask: What grievance and accountability mechanism is in place? Answer: pick one Requirement type: audit-trail - Centralized: Submit complaints to implementing org [centralized-grievance] - digital: digital grievance automated rules [blockchain-grievance] - Community-mediated: Local reconciliation + escalation path [community-grievance] #### UC-G-094 / conflict-alloc-participant-count Ask: How many organisations or stakeholders participate in conflict-sensitive allocation? Answer: pick one Requirement type: scale - 2–5 parties [small] - 6–15 parties [medium] - 16–50 parties [large] - Over 50 parties [enterprise] #### UC-G-094 / evidence-platform-approach Ask: How is evidence and documents currently stored and verified? Answer: pick one Requirement type: audit-trail - distributed storage/distributed storage with digital ledger tamper-proof verification [ipfs-anchored] - Cloud storage with periodic digital ledger proof checkpoints [cloud-anchored] - Digital metadata with separate encrypted file storage [hybrid-storage] - Not sure, need guidance on evidence storage [guidance-needed] ### UC-G-095: Evidence preservation for human rights documentation Security level: Critical. #### UC-G-095 / evidence-types Ask: What types of evidence are captured and preserved? Answer: pick one Requirement type: audit-trail - Photo/video documentation [media-evidence] - Written reports and documents [document-evidence] - Witness testimony and victim statements [testimony-evidence] #### UC-G-095 / chain-of-custody Ask: How is chain of custody currently maintained and verified? Answer: pick one Requirement type: audit-trail - Manual log: Paper/digital handover records [manual-log] - automated rules: Automated custody transfers digital [smart-contract] - Hybrid: QR codes + digital verification [hybrid-custody] #### UC-G-095 / legal-admissibility Ask: What legal jurisdiction standards must evidence meet? Answer: pick one Requirement type: legal-checks. Hard gate: yes - Domestic courts (national jurisdiction) [domestic-courts] - International tribunals (ICC/ad-hoc courts) [int-tribunals] - Truth commissions and investigative bodies [truth-commission] #### UC-G-095 / confidentiality-protection Ask: How do you currently protect the confidentiality of sensitive information? Answer: pick one Requirement type: privacy - Full encryption: End-to-end encryption of all evidence [full-encryption] - Selective disclosure: Only authorized parties can view [selective-disclosure] - Anonymization: PII redacted with verified preservation [anonymization] #### UC-G-095 / long-term-archival Ask: How is long-term archival and accessibility ensured? Answer: pick one Requirement type: audit-trail - Centralized archive: Single trusted repository [centralized-archive] - Distributed: Multiple copies across independent storage providers [distributed-archive] - Hybrid: Institutional + distributed backup [hybrid-archive] #### UC-G-095 / evidence-platform-approach Ask: How is evidence and documents currently stored and verified? Answer: pick one Requirement type: audit-trail - distributed storage/distributed storage with digital ledger tamper-proof verification [ipfs-anchored] - Cloud storage with periodic digital ledger proof checkpoints [cloud-anchored] - Digital metadata with separate encrypted file storage [hybrid-storage] - Not sure, need guidance on evidence storage [guidance-needed] ### UC-G-096: Atrocity documentation with chain of custody Security level: Critical. #### UC-G-096 / evidence-integrity-verification Ask: For evidence integrity verification, do you need: cryptographic proof (hash verification), legal notarization, or multiple witness signatures? Answer: pick one Requirement type: audit-trail - Digital fingerprinting and timestamping [crypto-hash] - Digital forensics: Bit-level verification [digital-forensics] - Provenance chain: Full metadata + witness verification [provenance-chain] #### UC-G-096 / multi-jurisdiction-support Ask: 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? Answer: pick one Requirement type: residency - Single jurisdiction: Evidence format for one legal system [single-jurisdiction] - Multi-format: Evidence packaged for multiple jurisdictions [multi-format] - Universal admissibility: Standardized format accepted everywhere [universal-format] #### UC-G-096 / investigator-access Ask: What access rights do investigators have to evidence? Answer: pick one Requirement type: audit-trail - Open access: All investigators can view evidence [open-access] - Restricted: Access approved by managing organization [restricted-access] - Tiered: Access depends on investigator role/tribunal [tiered-access] #### UC-G-096 / atrocity-doc-evidence-volume Ask: What volume of atrocity documentation evidence needs to be captured and preserved? Answer: pick one Requirement type: audit-trail - Under 100 records [small] - 100–1,000 records [medium] - 1,000–10,000 records [large] - Over 10,000 records [mass] ### UC-G-097: Witness testimony timestamping Security level: Critical. #### UC-G-097 / testimony-format Ask: In what format is witness testimony recorded? Answer: pick one Requirement type: audit-trail - Audio recording (encrypted digital file) [audio-format] - Video recording (with face/identifier verification) [video-format] - Transcript + independent notarization [transcript-format] #### UC-G-097 / verification-level Ask: What level of witness verification is performed? Answer: pick one Requirement type: audit-trail - Self-declaration: Witness provides name/ID only [self-declaration] - Document verification: Passport/ID scan + liveness check [doc-verification] - Biometric + cross-reference: Fingerprint/facial + registry check [biometric-cross-ref] #### UC-G-097 / witness-evidence-volume Ask: What volume of witness testimony evidence needs to be captured and preserved? Answer: pick one Requirement type: audit-trail - Under 100 records [small] - 100–1,000 records [medium] - 1,000–10,000 records [large] - Over 10,000 records [mass] #### UC-G-097 / witness-stakeholders Ask: How many distinct parties need visibility into the testimony evidence data? Answer: pick one Requirement type: usability - Internal only (1–2 teams) [internal] - Internal + 1–3 external partners [few-external] - Multiple external stakeholders (4–10) [multi-external] - Ecosystem-wide (donors, partners, beneficiaries, regulators) [ecosystem] #### UC-G-097 / sq-UC-G-098-001 Ask: 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? Answer: pick one Requirement type: general - Pseudonymous with key escrow [pseudonymous-with-key-escrow] - Sealed identity: court only [sealed-identity-court-only] - Fully anonymous [fully-anonymous] - Tiered disclosure [tiered-disclosure] - Witness-controlled revelation [witness-controlled-revelation] ### UC-G-098: Displacement tracking and verification Security level: Higher. #### UC-G-098 / population-scale Ask: What scale of displaced population will be tracked? Answer: pick one Requirement type: audit-trail - Small-scale: <10,000 individuals [small-scale] - Medium-scale: 10,000-100,000 individuals [medium-scale] - Large-scale: >100,000 individuals [large-scale] #### UC-G-098 / tracking-scope Ask: What tracking scope is covered (origin, transit, destination)? Answer: pick one Requirement type: general - Origin only: Record where people came from [origin-only] - Origin + destination: Beginning and end point tracking [origin-destination] - Full path: Origin, transit, destination, and ongoing [full-journey] #### UC-G-098 / registration-touchpoints Ask: Where and when are registration touchpoints located? Answer: pick one Requirement type: credentials - Centralized: Fixed registration sites (camps, offices) [centralized-sites] - Mobile: Field teams conduct registration at communities [mobile-teams] - Multi-channel: Fixed + mobile + self-service online [multi-channel] #### UC-G-098 / privacy-protection Ask: How is personal data privacy protected in displacement tracking? Answer: pick one Requirement type: privacy - Minimal data: Only essential identifiers stored [minimal-data] - Encrypted storage: Data encrypted at rest and in transit [encrypted-storage] - privacy-preserving verification: Verification without data exposure [zero-knowledge] #### UC-G-098 / data-sharing-permissions Ask: What data do you currently share with humanitarian partners, and how? Answer: pick one Requirement type: legal-checks - Closed: Data shared only with direct implementing partners [closed-sharing] - Semi-open: Aggregated data shared with authorized organizations [semi-open] - Open: De-identified data available for research/analysis [open-sharing] #### UC-G-098 / evidence-platform-approach Ask: How is evidence and documents currently stored and verified? Answer: pick one Requirement type: audit-trail - distributed storage/distributed storage with digital ledger tamper-proof verification [ipfs-anchored] - Cloud storage with periodic digital ledger proof checkpoints [cloud-anchored] - Digital metadata with separate encrypted file storage [hybrid-storage] - Not sure, need guidance on evidence storage [guidance-needed] #### UC-G-098 / timestamping-approach Ask: How is events and evidence currently timestamped for this solution? Answer: pick one Requirement type: audit-trail - Digital timestamping (each event anchored with tamper-proof proof) [on-chain] - Batch anchoring (events collected, periodically anchored) [batch-anchoring] - Trusted third-party timestamping authority [trusted-authority] - Not sure, need guidance on timestamping approach [guidance-needed] ### UC-H-099: Land registry and title documentation (post-conflict/disaster) Security level: Higher. #### UC-H-099 / registry-model Ask: How do you currently maintain land or property records in your context? Answer: pick one Requirement type: general - Centralized government land registry with digital ledger audit trail [centralized-audit] - Distributed land registry ledger with multi-stakeholder validation [distributed-multi] - Hybrid model with centralized storage and distributed verification [hybrid-verification] #### UC-H-099 / land-surveying-tech Ask: For land surveying, what technology and precision is needed: GPS/handheld devices, drone/UAV mapping, satellite imagery, or traditional surveying? Answer: pick one Requirement type: general - Satellite-verified boundary engine with SAR/optical imagery [satellite-verified] - GPS and drone-based surveying with real-time boundary mapping [gps-drone-survey] - GIS and digital record system with historical boundary tracking [gis-blockchain-layer] - Community-annotated maps with participatory boundary validation [community-annotated] #### UC-H-099 / dispute-handling-mechanism Ask: For disputes, do you currently have: formal court processes, community elders/traditional mechanisms, administrative appeal, or none? Which should the system support? Answer: pick one Requirement type: governance - Multi-tiered resolution: automated for clear cases, escalation for complex ones [multi-tiered-resolution-automated-for-cl] - Community mediation with government appeal pathway [community-mediation-with-government-appe] - Formal adjudication with structured evidence collection [formal-adjudication-with-structured-evid] - Not sure, need guidance [not-sure-need-guidance] #### UC-H-099 / documentation-quality-baseline Ask: What baseline would you need for documentation quality in land and resource management? Answer: pick one Requirement type: general - Multi-source document verification with confidence scoring [doc-confidence-scoring] - Forensic document analysis with digital ledger timestamping [forensic-analysis] - Legacy system migration with verification checkpoint layers [legacy-migration] #### UC-H-099 / post-conflict-recovery-framework Ask: For post-conflict restitution, should decisions be guided by: pre-conflict ownership records, claimant testimony, community consensus, government restitution law, or combination? Answer: pick one Requirement type: general - Transitional justice model with truth commission digital ledger archive [transitional-justice] - Reparations tracking with digitally certified land claims [reparations-tracking] - Community-led restitution with elder council mediation and digital records [community-led] - Combined approach: government law + community testimony + documented ownership [combined] - Not sure, context-dependent, need guidance [unsure] #### UC-H-099 / registry-platform-approach Ask: What type of registry platform is appropriate for this context? Answer: pick one Requirement type: general - Government-integrated registry (supplement existing land authority) [gov-integrated] - Standalone digital ledger registry (parallel to government system) [standalone-chain] - Community-managed registry with local authority endorsement [community-managed] - Not sure, need guidance on registry approach [guidance-needed] #### UC-H-099 / title-documentation-approach Ask: What type of title or rights documentation is appropriate? Answer: pick one Requirement type: general - Formal title deeds with digital ledger registration [formal-deeds] - Occupancy certificates (intermediate documentation) [occupancy-certs] - Customary rights documentation with community attestation [customary-rights] - Progressive titling: start informal, formalise over time [progressive] #### UC-H-099 / mapping-integration Ask: How are land or boundaries currently mapped? Answer: pick one Requirement type: integration - GIS/satellite mapping integration [gis-satellite] - Community-drawn boundary mapping [community-mapping] - Government cadastral system integration [cadastral] - Mobile GPS-based mapping [mobile-gps] ### UC-H-100: Property rights documentation for displaced populations Security level: Critical. #### UC-H-100 / claim-documentation-method Ask: 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? Answer: pick one Requirement type: general - Digital claim forms with secure signing and timestamping [digital-signed-forms] - Multimedia affidavit system with photo/video evidence attachment [multimedia-affidavit] - Independent identity verification with portable personal credentials [ssi-credentials] #### UC-H-100 / evidence-types-acceptance Ask: Which evidence types should be accepted for displaced property claims? Answer: pick one Requirement type: audit-trail - Documentary evidence (deeds, certificates, government records) [documentary-evidence] - Witness testimony with credibility scoring and cross-verification [witness-testimony] - Satellite/geospatial evidence with possession history mapping [geospatial-evidence] - Biometric identity linking with genealogical/familial documentation [biometric-genealogy] #### UC-H-100 / verification-process-design Ask: What process would you need for verifying land and resource claims? Answer: pick one Requirement type: credentials - Multi-stakeholder verification consortium with independent auditors [consortium-verification] - Community-based verification with peer review mechanism [community-verification] - Government agency verification with digital ledger attestation trail [government-attestation] #### UC-H-100 / government-recognition-pathway Ask: What is your goal: formal government registration, government recognition, or community-based documentation? Answer: pick one Requirement type: integration - Digital evidence submitted as proof in government recognition process [blockchain-evidence-submission] - automated rules-mediated claims with government certification output [smart-contract-mediation] - Notarized claims with official government land registry submission [notarized-registry-submission] #### UC-H-100 / claim-portability-framework Ask: Do land claims need to be recognised across multiple jurisdictions? Answer: pick one Requirement type: general - Cross-border claim reciprocity with bilateral agreements [bilateral-reciprocity] - Standardized verifiable credential format for international transfer [vc-standard-transfer] - Single jurisdiction only: no cross-border recognition needed [single-jurisdiction] - Regional recognition within a country (e.g. across states or provinces) [regional] - Not sure, the displacement context makes this unclear [unsure] #### UC-H-100 / claims-management-approach Ask: How should claims and disputes be managed? Answer: pick one Requirement type: governance - Formal claims process with adjudication workflow [formal-adjudication] - Community-based mediation with digital ledger record [community-mediation] - Self-service claims portal with document upload [self-service] - Hybrid: self-service intake with formal adjudication [hybrid] #### UC-H-100 / title-documentation-approach Ask: What type of title or rights documentation is appropriate? Answer: pick one Requirement type: general - Formal title deeds with digital ledger registration [formal-deeds] - Occupancy certificates (intermediate documentation) [occupancy-certs] - Customary rights documentation with community attestation [customary-rights] - Progressive titling: start informal, formalise over time [progressive] #### UC-H-100 / evidence-platform-approach Ask: How is evidence and documents currently stored and verified? Answer: pick one Requirement type: audit-trail - distributed storage/distributed storage with digital ledger tamper-proof verification [ipfs-anchored] - Cloud storage with periodic digital ledger proof checkpoints [cloud-anchored] - Digital metadata with separate encrypted file storage [hybrid-storage] - Not sure, need guidance on evidence storage [guidance-needed] ### UC-H-101: Housing, land, and property (HLP) claims tracking Security level: Higher. #### UC-H-101 / claim-volume-capacity Ask: What is the expected claim volume and system capacity design? Answer: pick one Requirement type: scale - Small-scale deployment (< 10,000 claims) with rapid throughput [small-scale] - Medium-scale deployment (10,000-100,000 claims) with performance scaling [medium-scale] - Large-scale deployment (>100,000 claims) with enterprise digital ledger [large-scale] #### UC-H-101 / resolution-mechanism-design Ask: For resolving disputed claims, do you use: individual adjudication, negotiated settlement, third-party arbitration, community consensus, or combination? Answer: pick one Requirement type: governance - Fast-track resolution for straightforward cases with independent validation [fast-track-resolution-for-straightforwar] - Phased resolution with verification stages and checkpoint reviews [phased-resolution-with-verification-stag] - Government-moderated resolution with formal evidence documentation [government-moderated-resolution-with-for] #### UC-H-101 / stakeholder-representation-model Ask: Who should represent stakeholders in claim resolution: individual claimants, community leaders, formal legal representatives, international observers, or combination? Answer: pick one Requirement type: usability - Representative committee with veto power and consensus requirement [committee-consensus] - Weighted voting system with stakeholder token allocation [weighted-voting] - Rotating stakeholder roles with periodic review and rotation [rotating-roles] #### UC-H-101 / hlp-participant-count Ask: How many organisations or stakeholders participate in HLP claims? Answer: pick one Requirement type: scale - 2–5 parties [small] - 6–15 parties [medium] - 16–50 parties [large] - Over 50 parties [enterprise] #### UC-H-101 / sq-UC-H-106-001 Ask: What evidence types should be accepted to support HLP claims? Answer: pick one Requirement type: general - Documentary title [documentary-title] - Witness testimony [witness-testimony] - Satellite imagery [satellite-imagery] - Community attestation [community-attestation] - Cadastral records [cadastral-records] - Combination scoring [combination-scoring] #### UC-H-101 / claims-management-approach Ask: How should claims and disputes be managed? Answer: pick one Requirement type: governance - Formal claims process with adjudication workflow [formal-adjudication] - Community-based mediation with digital ledger record [community-mediation] - Self-service claims portal with document upload [self-service] - Hybrid: self-service intake with formal adjudication [hybrid] ### UC-H-102: Customary land rights documentation Security level: Standard. #### UC-H-102 / customary-documentation-approach Ask: What documentation approach works best for customary land rights in your context? Answer: pick one Requirement type: general - Oral history digitization with recorded testimony and digital archive [oral-history-digital] - Customary tenure tokenisation platform with community-issued tokens [customary-tokens] - GPS boundary mapping with ethnographic and genealogical metadata [gps-ethnographic] - Photographic documentation with digital temporal proof [photo-blockchain] #### UC-H-102 / government-recognition-integration Ask: Is government integration required, desired, or not applicable for your approach? Answer: pick one Requirement type: integration - Parallel digital ledger registry with government co-validation [parallel-registry-covalidation] - Government-issued certificates based on community attestations [gov-certificates-community] - Customary system preservation with digital ledger documentation only [customary-only] #### UC-H-102 / conflict-resolution-mechanisms Ask: How are conflicts over land claims currently resolved in your communities? Answer: pick one Requirement type: governance - Customary law priority with government appeal pathway [customary-priority] - Dual-track system with customary and statutory parallel recognition [dual-track] - Harmonized framework through government legal reform and integration [harmonized-reform] #### UC-H-102 / cultural-preservation-safeguards Ask: What safeguards exist to protect cultural and governance practices? Answer: pick one Requirement type: general - Indigenous technology requirements with local administration authority [indigenous-tech-local] - Cultural protocol embedding in automated rules code [cultural-protocol-code] - Community-controlled access: elders or traditional authorities approve any changes [community-controlled] - Formal legal protections combined with digital documentation of customary rules [legal-plus-digital] - Not sure, need to consult community leaders first [unsure] #### UC-H-102 / title-documentation-approach Ask: What type of title or rights documentation is appropriate? Answer: pick one Requirement type: general - Formal title deeds with digital ledger registration [formal-deeds] - Occupancy certificates (intermediate documentation) [occupancy-certs] - Customary rights documentation with community attestation [customary-rights] - Progressive titling: start informal, formalise over time [progressive] ### UC-H-103: Natural resource extraction tracking Security level: Standard. #### UC-H-103 / resource-type-tracking Ask: What resource type tracking and categorization should be used? Answer: pick one Requirement type: general - Mineral extraction ledger with commodity type and volume tracking [mineral-ledger] - Timber and forestry tracking with species and sustainability metrics [timber-sustainability] - Oil and gas resource ledger with environmental impact scoring [oil-gas-impact] - Multi-resource agile taxonomy with flexible commodity classification [multi-resource-agile] #### UC-H-103 / monitoring-methodology Ask: For monitoring extraction, what methods are feasible: satellite/remote sensing, ground-based observer patrols, extraction site meters, or community self-reporting? Answer: pick one Requirement type: general - sensor device networks with real-time extraction volume data [iot-realtime] - Satellite remote sensing with automated change detection [satellite-detection] - Manual audits with digital ledger-recorded inspection outcomes [manual-audits-blockchain] - Hybrid IoT-satellite monitoring with cross-validation [hybrid-monitoring] #### UC-H-103 / community-involvement-model Ask: How is your community currently involved in land and resource governance? Answer: pick one Requirement type: general - Community monitors with mobile app reporting and incentives [community-monitors] - Participatory verification with digitally-mediated community voting [participatory-verification] - Community-controlled monitoring dashboard with real-time data access [community-dashboard] #### UC-H-103 / environmental-impact-assessment Ask: For environmental monitoring, what should be tracked: extraction volume only, environmental indicators (water quality, vegetation), biodiversity surveys, or combination? Answer: pick one Requirement type: audit-trail - Automated environmental compliance scoring with oracle data feeds [auto-compliance-scoring] - Satellite-verified environmental impact with AI analysis [satellite-ai-impact] - Biodiversity monitoring with digital ledger-recorded audit trail [biodiversity-audit] #### UC-H-103 / supply-chain-provenance Ask: What supply chain provenance and anti-conflict mechanisms should be used? Answer: pick one Requirement type: audit-trail - Full supply chain transparency ledger from extraction to market [full-transparency-ledger] - Conflict minerals certification with digital ledger attestation [conflict-minerals-cert] - Targeted traceability at key handover points (mine, processor, exporter) [key-handover] - Community-verified origin documentation with local authority sign-off [community-verified] - Not sure, need to assess what is feasible in our extraction context [unsure] #### UC-H-103 / registry-platform-approach Ask: What type of registry platform is appropriate for this context? Answer: pick one Requirement type: general - Government-integrated registry (supplement existing land authority) [gov-integrated] - Standalone digital ledger registry (parallel to government system) [standalone-chain] - Community-managed registry with local authority endorsement [community-managed] - Not sure, need guidance on registry approach [guidance-needed] #### UC-H-103 / verification-layer Ask: How is records or claims currently independently verified? Answer: pick one Requirement type: credentials - Automated verification against digital records [automated] - Third-party verification with digital proof [third-party] - Community-based verification with attestation [community] - Not sure, need guidance [guidance-needed] ### UC-H-104: Community benefit sharing from resources Security level: Standard. #### UC-H-104 / sharing-mechanism-design Ask: For benefit-sharing, should distributions be: based on population share, land contribution, active participation in decision-making, or other criteria? Answer: pick one Requirement type: general - Per-transaction royalty with percentage-based distribution [transaction-royalty] - Annual profit-sharing with community stakeholder voting [annual-profit-sharing] - Trust-based fund management with elected community trustees [trust-fund-model] #### UC-H-104 / payment-model-options Ask: What payment and currency model should be adopted? Answer: pick one Requirement type: money - Direct fiat currency transfers with bank integration [fiat-transfers] - Stablecoin payments with community wallet infrastructure [stablecoin-payments] - Community benefit tokens with secondary market trading [benefit-tokens] #### UC-H-104 / transparency-mechanism Ask: What transparency mechanisms do you currently use for land and resource data? Answer: pick one Requirement type: audit-trail - Public digital ledger ledger with real-time transaction visibility [public-ledger] - Private register with privacy-preserving verification [private-zkproof] - Quarterly auditable reports with digital ledger-anchored timestamps [quarterly-audits] #### UC-H-104 / benefit-share-compliance Ask: What financial compliance requirements apply to community benefit sharing? Answer: pick all that apply Requirement type: legal-checks - Tax deductibility receipting [tax] - Anti-money laundering (AML) / Know Your Donor [aml] - Cross-border fund transfer regulations [cross-border] - Cryptocurrency-specific regulations [crypto-reg] - No specific compliance requirements [none] ### UC-H-105: Water rights management Security level: Standard. #### UC-H-105 / water-allocation-methodology Ask: For water allocation, should rights be based on: historical use patterns, proportional population share, seasonal rotation, priority to downstream users, or other criteria? Answer: pick one Requirement type: general - Volumetric allocation with automated seasonal adjustment rules [volumetric-allocation] - Priority-based water rights with junior/senior tier management [priority-tiers] - Proportional-need allocation with environmental flow requirements [proportional-need] #### UC-H-105 / seasonal-variation-adaptation Ask: How do you currently adapt water allocation for seasonal variations? Answer: pick one Requirement type: general - Dynamic allocation adjustment based on real-time water availability [dynamic-adjustment] - Proportional reduction mechanism during drought conditions [proportional-reduction] - Seasonal quota system with carry-over rights and banking [seasonal-banking] #### UC-H-105 / measurement-infrastructure Ask: For water measurement, what methods are currently available or feasible in your context? Answer: pick one Requirement type: general - Flow meter networks with IoT data streams to digital ledger [iot-flow-meters] - Satellite remote sensing with water level tracking [satellite-water-level] - Manual meter reading with digital ledger-recorded audit trail [manual-meter-audit] - Hybrid IoT-satellite monitoring with cross-validation protocols [hybrid-water-monitoring] #### UC-H-105 / drought-contingency-planning Ask: What drought contingency and emergency response approach do you currently use? Answer: pick one Requirement type: general - Automated drought trigger with pre-programmed allocation reduction [automated-drought-trigger] - Emergency water council activation with rapid stakeholder convening [emergency-council] - Water banking and strategic reserve mechanism with emergency release protocols [water-banking] #### UC-H-105 / transboundary-water-coordination Ask: What coordination mechanisms do you have for transboundary water resources? Answer: pick one Requirement type: integration - Bilateral/multilateral agreement framework with digital verification [multilateral-agreement] - Shared ledger system with all riparian states as validators [shared-ledger-riparian] - No transboundary issues, single jurisdiction water management [single-jurisdiction] - Informal cooperation between neighbouring communities across borders [informal-cooperation] - Not sure, transboundary aspects are unclear or emerging [unsure] #### UC-H-105 / registry-platform-approach Ask: What type of registry platform is appropriate for this context? Answer: pick one Requirement type: general - Government-integrated registry (supplement existing land authority) [gov-integrated] - Standalone digital ledger registry (parallel to government system) [standalone-chain] - Community-managed registry with local authority endorsement [community-managed] - Not sure, need guidance on registry approach [guidance-needed] ### UC-H-106: Fishing rights and marine resource access Security level: Standard. #### UC-H-106 / fishing-license-model Ask: For fishing rights, should licensing be based on: traditional fishing families, gear-based limits, area-based zones, species-based restrictions, or combination? Answer: pick one Requirement type: legal-checks - Individual transferable quotas as digital ledger tokens [itq-tokens] - Community fishing licenses with collective catch allocation [community-licenses] - Area-based management zones with spatial fishing rights NFTs [area-based-nfts] - Species-specific licenses with differential rights per species [species-specific] #### UC-H-106 / catch-monitoring-system Ask: What catch monitoring is currently feasible in your context? Answer: pick one Requirement type: integration - Vessel monitoring system with digital ledger catch reporting [vms-blockchain] - Electronic catch documentation system with photo verification [ecd-photo-verification] - Port-based monitoring with weight verification and digital ledger audit [port-monitoring] - Autonomous observer drones with AI catch species identification [observer-drones-ai] #### UC-H-106 / enforcement-mechanisms Ask: What enforcement mechanisms should be implemented? Answer: pick one Requirement type: audit-trail - Automated penalties when quota violations are detected [automated-penalties-when-quota-violation] - Official enforcement with digital evidence chain for prosecution [official-enforcement-with-digital-eviden] - Community monitoring with incentives for compliance [community-monitoring-with-incentives-for] - Insurance-based approach with performance bonds and automated claims [insurance-based-approach-with-performanc] - Not sure, need guidance [not-sure-need-guidance] #### UC-H-106 / sustainability-compliance Ask: What sustainability standards must your land/resource management comply with? Answer: pick one Requirement type: legal-checks - Ecosystem health indicators with oracle-triggered license suspension [ecosystem-health-oracle] - Seasonal fishing closures with automated rules enforcement [seasonal-closures] - Endangered species protection with digitally verified catch exclusion [endangered-protection] #### UC-H-106 / market-access-sustainability Ask: How do you currently ensure market access for sustainable products? Answer: pick one Requirement type: general - Supply chain certification with digital proof of sustainability [supply-chain-cert] - Digitally certified sustainable seafood with market tracking and transparency [tokenized-seafood] - Dynamic fishing license pricing based on sustainability compliance score [dynamic-pricing] #### UC-H-106 / stakeholder-participation Ask: How are stakeholders currently involved in sustainability decisions? Answer: pick one Requirement type: usability - Multi-stakeholder governance body with proportional voting rights [multi-stakeholder-governance] - Co-management committee with digitally recorded decisions [co-management-committee] - Advisory board with community consultation (decisions recorded but not binding votes) [advisory-board] - Government-led with community input sessions [govt-led] - Not sure, stakeholder engagement model still being designed [unsure] #### UC-H-106 / registry-platform-approach Ask: What type of registry platform is appropriate for this context? Answer: pick one Requirement type: general - Government-integrated registry (supplement existing land authority) [gov-integrated] - Standalone digital ledger registry (parallel to government system) [standalone-chain] - Community-managed registry with local authority endorsement [community-managed] - Not sure, need guidance on registry approach [guidance-needed] #### UC-H-106 / iot-sensor-approach Ask: What type of sensor or data collection devices will be used? Answer: pick one Requirement type: devices - GPS/location tracking devices [gps-location] - Environmental sensors (temperature, humidity, etc.) [environmental] - Smart meters (energy, water usage) [smart-meters] - Mobile phone-based data collection (photos, GPS, manual entry) [mobile-collection] ### UC-I-107: Renewable energy certificate tracking and trading Security level: Standard. #### UC-I-107 / generation-monitoring Ask: Do you have real-time IoT metering infrastructure available, or must you use periodic manual submissions? Answer: pick one Requirement type: credentials - Real-time IoT metering with direct digital ledger feed [iot-realtime] - Periodic meter readings with manual submission [manual-periodic] - Aggregated data from generation facilities [aggregated] #### UC-I-107 / trading-mechanism Ask: How frequently will certificates be traded? (daily peer-to-peer, weekly, or monthly batch auctions?) Answer: pick one Requirement type: general - direct OTC trading with settlement [p2p-otc] - Centralized marketplace with clearing [cex-clearing] - Hybrid DEX with liquidity pools [dex-liquidity] - Auction-based trading mechanism [auction] #### UC-I-107 / registry-model Ask: Do certificates need to be tradeable internationally, or will they operate within a single country? Answer: pick one Requirement type: credentials - Centralized registry with digital ledger settlement layer [centralized-registry] - Fully digital registry with digital tokens [onchain-erc1155] - coordinated across organisations registry across multiple digital ledgers [federated-registry] #### UC-I-107 / rec-verification-std Ask: What verification standards or methodologies apply to renewable energy certificates? Answer: pick one Requirement type: credentials - Gold Standard [gold-standard] - Verra / VCS [verra] - National or regional standard [national] - Custom or internal methodology [custom] - Not yet determined [tbd] #### UC-I-107 / rec-monitoring-freq Ask: How frequently does energy generation monitoring data need to be captured? Answer: pick one Requirement type: general - Real-time / continuous [realtime] - Daily [daily] - Weekly or monthly [periodic] - Seasonally or annually [seasonal] #### UC-I-107 / iot-sensor-approach Ask: What type of sensor or data collection devices will be used? Answer: pick one Requirement type: devices - GPS/location tracking devices [gps-location] - Environmental sensors (temperature, humidity, etc.) [environmental] - Smart meters (energy, water usage) [smart-meters] - Mobile phone-based data collection (photos, GPS, manual entry) [mobile-collection] ### UC-I-108: Carbon credit registry and marketplace Security level: Standard. #### UC-I-108 / mrv-approach Ask: What data collection infrastructure do you currently have? (manual field surveys, automated sensors, satellite monitoring?) Answer: pick one Requirement type: credentials - Satellite-based monitoring with automated reporting [satellite-auto] - On-site IoT sensors with third-party audit [iot-audit] - Hybrid approach combining multiple data sources [hybrid-mrv] #### UC-I-108 / credit-pricing Ask: Are credits sold at prevailing market prices or do you need auction-based price discovery? Answer: pick one Requirement type: money - Market-driven supply-demand pricing [market-driven] - Methodology cost baseline with risk premium [cost-plus-premium] - Regulatory or policy-set floor price [regulatory-floor] #### UC-I-108 / certificate-registry Ask: What type of certificate tracking do you need? Answer: pick one Requirement type: credentials - Public registry (anyone can verify certificates) [public] - Permissioned registry (only authorised parties can verify) [permissioned] - Integration with existing standard registries (e.g. Verra, Gold Standard) [existing-standard] - Not sure, need guidance [guidance-needed] #### UC-I-108 / credit-stakeholder-access Ask: How many parties need to view, trade, or verify credits in the registry? Answer: pick one Requirement type: usability - Project developer only: internal registry management [internal] - Project developer + verification body [developer-verifier] - Multiple parties: buyers, verifiers, regulators all need access [multi-party] - Public registry: anyone can view credit status and retirement [public] - Not sure, need guidance on access model [unsure] #### UC-I-108 / credit-trading-rules Ask: Once credits are issued, can they be traded or are they retired on first use? Answer: pick one Requirement type: money - Credits are retired on use: no secondary trading [retire-only] - Credits can be traded once before retirement [single-trade] - Open secondary market: credits can be traded multiple times [open-market] - Bundled trading: credits packaged with other environmental assets [bundled] - Not sure, trading model still being determined [unsure] #### UC-I-108 / credit-registry-reporting Ask: What registry reporting is required for your carbon credit programme? Answer: pick one Requirement type: audit-trail - Standard registry reports (issuance, retirement, balance) [standard] - Donor/funder reporting with impact metrics linked to credits [donor-impact] - Regulatory compliance reporting (national carbon accounting) [regulatory] - Full transparency: public dashboard showing all credit lifecycle events [full-transparency] - Not sure, need guidance on reporting requirements [unsure] ### UC-I-109: Green energy provenance for climate finance Security level: Standard. #### UC-I-109 / energy-type Ask: What renewable energy types are tracked? Answer: pick one Requirement type: general - Solar photovoltaic generation [solar-pv] - Wind power generation [wind] - Hydroelectric generation [hydro] - Mixed renewable portfolio [mixed-renewable] #### UC-I-109 / provenance-chain Ask: How many distinct steps/handoff points in your energy supply chain from generation to end-beneficiary? Answer: pick one Requirement type: audit-trail - Real-time meter-to-market provenance with atomic settlement [realtime-provenance] - Batch provenance bundles with periodic attestation [batch-provenance] - Additionality verification with counterfactual modeling [additionality-verification] #### UC-I-109 / financer-requirements Ask: What climate finance eligibility criteria must be met? Answer: pick one Requirement type: general - Green Bond eligibility per ICMA guidelines [green-bond-icma] - GCF (Green Climate Fund) eligibility criteria [gcf-eligible] - Paris Agreement Article 6 mechanism compliance [paris-article6] - Voluntary carbon market (VCM) eligibility [vcm-standard] #### UC-I-109 / verification-standard Ask: What verification standard is applied? Answer: pick one Requirement type: audit-trail - Third-party independent auditor verification [third-party-audit] - distributed oracle consensus verification [oracle-consensus] - Automated satellite imagery and data validation [satellite-validation] #### UC-I-109 / green-energy-monitoring-freq Ask: How frequently does energy provenance monitoring data need to be captured? Answer: pick one Requirement type: general - Real-time / continuous [realtime] - Daily [daily] - Weekly or monthly [periodic] - Seasonally or annually [seasonal] ### UC-I-110: Environmental monitoring data integrity Security level: Standard. #### UC-I-110 / sensor-types Ask: What environmental sensor types provide data? Answer: pick one Requirement type: devices - Air quality sensors (particulates, gas) [air-quality] - Water quality sensors (pH, turbidity, dissolved oxygen) [water-quality] - Soil and biological sensors (moisture, temperature, nutrient) [soil-biomonitor] - Multi-modal sensor network (mixed environmental) [multimodal-sensors] #### UC-I-110 / data-frequency Ask: What data reporting frequency is required? Answer: pick one Requirement type: credentials - Real-time streaming (< 5 minute intervals) [realtime-stream] - Hourly aggregated readings [hourly-aggregate] - Daily batch reporting with secure digital proofs [daily-batch] #### UC-I-110 / integrity-verification Ask: What is your acceptable error margin for environmental measurements? (e.g., +/- 2%, or max 5% data loss per month?) Answer: pick one Requirement type: audit-trail - Secure digital signatures with key rotation [crypto-signatures] - Multi-sensor consensus with outlier detection [multiSensor-consensus] - Hardware attestation with TPM/Secure Enclave [hardware-attestation] - Zero-knowledge proofs of data correctness [zk-proofs] #### UC-I-110 / data-sharing Ask: Who receives your environmental data and what sensitivity constraints apply? Answer: pick one Requirement type: general - Public digital register with anonymized data [public-anon] - Private network with role-based access controls [private-rbac] - Separate data store with digitally verified summaries [ofchain-lake] #### UC-I-110 / alert-mechanisms Ask: What triggers alerts in your monitoring system? Answer: pick one Requirement type: audit-trail - Automated threshold alerts with automated rules execution [threshold-alerts] - Multi-step manual approval with governance timelock [governance-approval] - Hybrid automated + escalation to data steward [hybrid-alert] ### UC-I-111: Circular economy and waste tracking Security level: Standard. #### UC-I-111 / waste-streams Ask: What waste streams are tracked? Answer: pick one Requirement type: general - Plastic and packaging waste [plastic-packaging] - Organic and biodegradable waste [organic-biodegradable] - Electronic waste (e-waste) [electronic-waste] - Construction and demolition waste [construction-demolition] - Mixed waste streams with composition analysis [mixed-composition] #### UC-I-111 / tracking-granularity Ask: What tracking granularity is required? Answer: pick one Requirement type: credentials - Individual item tracking with unique identifiers [item-level] - Batch tracking with bulk weight certificates [batch-weight] - Facility-level aggregate tracking [facility-aggregate] #### UC-I-111 / material-flow Ask: How many distinct stages in your waste recycling flow? (collection -> sorting -> reprocessing -> redistribution?) Answer: pick one Requirement type: credentials - Linear chain-of-custody with digital handoffs [linear-custody] - Circular loop with feedback to producers [circular-feedback] - Material bank with dynamic allocation [material-bank] #### UC-I-111 / recovery-targets Ask: What is your target waste recovery rate and timeline to achieve it? Answer: pick one Requirement type: integration - Producer extended responsibility with token rewards [producer-epr-rewards] - Mandatory recovery percentages with penalties [mandatory-recovery] - Market-based recovery credits trading [recovery-credits] #### UC-I-111 / circular-volume Ask: What is the monthly volume of waste/recycling items you need to track? Answer: pick one Requirement type: scale - Under 1,000 items [small] - 1,000–10,000 items [medium] - 10,000–100,000 items [large] - Over 100,000 items [enterprise] #### UC-I-111 / circular-monitoring-freq Ask: How frequently does waste and recycling monitoring data need to be captured? Answer: pick one Requirement type: general - Real-time / continuous [realtime] - Daily [daily] - Weekly or monthly [periodic] - Seasonally or annually [seasonal] #### UC-I-111 / audit-trail-approach Ask: What level of record-keeping and evidence trail do you need for this process? Answer: pick one Requirement type: audit-trail - Full permanent audit trail: every action logged digitally [full-immutable] - Key events only: milestones and approvals logged digital [key-events] - Hybrid: key details logged digitally, full records stored separately with tamper-proof links [hybrid] - Not sure, need guidance on audit trail design [guidance-needed] #### UC-I-111 / iot-sensor-approach Ask: What type of sensor or data collection devices will be used? Answer: pick one Requirement type: devices - GPS/location tracking devices [gps-location] - Environmental sensors (temperature, humidity, etc.) [environmental] - Smart meters (energy, water usage) [smart-meters] - Mobile phone-based data collection (photos, GPS, manual entry) [mobile-collection] ### UC-I-112: Reforestation verification Security level: Standard. #### UC-I-112 / monitoring-method Ask: What reforestation monitoring method is used? Answer: pick one Requirement type: credentials - Satellite imagery with ML-based tree detection [satellite-ml] - Drone-based aerial surveys with photogrammetry [drone-survey] - Ground-based surveys with GPS tree mapping [ground-survey] - Hybrid satellite + drone + ground survey [hybrid-monitoring] #### UC-I-112 / tree-survival-tracking Ask: How frequently must tree survival be measured? (quarterly, annually?) And what accuracy is required? Answer: pick one Requirement type: credentials - Year-over-year satellite vegetation index comparison [satellite-ndvi] - Drone-based DBH (diameter at breast height) measurement [drone-dbh] - QR-tagged sapling verification with IoT sensors [qr-iot-sensors] #### UC-I-112 / reforest-verification-std Ask: What verification standards or methodologies apply to reforestation? Answer: pick one Requirement type: credentials - Gold Standard [gold-standard] - Verra / VCS [verra] - National or regional standard [national] - Custom or internal methodology [custom] - Not yet determined [tbd] #### UC-I-112 / reforest-monitoring-freq Ask: How frequently does reforestation progress monitoring data need to be captured? Answer: pick one Requirement type: general - Real-time / continuous [realtime] - Daily [daily] - Weekly or monthly [periodic] - Seasonally or annually [seasonal] #### UC-I-112 / monitoring-platform-approach Ask: What monitoring approach do you currently use verify outcomes on the ground? Answer: pick one Requirement type: credentials - Satellite imagery with AI analysis [satellite-ai] - Ground-based monitoring with field agents [ground-based] - Community-based monitoring with mobile reporting [community-based] - Combined satellite + ground truth verification [combined] #### UC-I-112 / timestamping-approach Ask: How is events and evidence currently timestamped for this solution? Answer: pick one Requirement type: audit-trail - Digital timestamping (each event anchored with tamper-proof proof) [on-chain] - Batch anchoring (events collected, periodically anchored) [batch-anchoring] - Trusted third-party timestamping authority [trusted-authority] - Not sure, need guidance on timestamping approach [guidance-needed] ### UC-I-113: Biodiversity conservation tracking Security level: Standard. #### UC-I-113 / species-monitoring Ask: How are species populations monitored? Answer: pick one Requirement type: credentials - Camera trap networks with AI image classification [camera-trap-ai] - Acoustic monitoring with bioacoustic classification [acoustic-monitoring] - eDNA sampling with genetic analysis [edna-sampling] - Community-based monitoring with citizen science [citizen-science] #### UC-I-113 / protected-area-management Ask: How many management authorities/jurisdictions oversee your protected areas? Answer: pick one Requirement type: credentials - Satellite deforestation monitoring with alert system [satellite-deforestation] - GPS ranger patrol tracking with geofencing [gps-patrol-tracking] - Community-based area management with land rights registry [community-management] #### UC-I-113 / data-collection Ask: What biodiversity data sources are you currently using? Answer: pick one Requirement type: general - Standardized biodiversity protocols (IUCN, BirdLife) [iucn-birdlife-protocols] - Flexible schema with validation rules per ecosystem [flexible-schema] - Minimal schema with automated harmonization post-collection [minimal-schema] #### UC-I-113 / stakeholder-collaboration Ask: How many distinct stakeholder organizations need collaborative data access? Answer: pick one Requirement type: audit-trail - Public register with role-based access control [public-rbac] - Multi-stakeholder consortium with consensus-based updates [consortium-consensus] - Distributed data repository with verifiable contribution records [data-lake-proofs] #### UC-I-113 / biodiversity-verification-std Ask: What verification standards apply to your biodiversity conservation work? Answer: pick one Requirement type: credentials - Gold Standard [gold-standard] - Verra / VCS [verra] - National or regional standard [national] - Custom or internal methodology [custom] - Not yet determined [tbd] #### UC-I-113 / biodiversity-monitoring-freq Ask: How frequently does biodiversity monitoring data need to be captured? Answer: pick one Requirement type: general - Real-time / continuous [realtime] - Daily [daily] - Weekly or monthly [periodic] - Seasonally or annually [seasonal] #### UC-I-113 / monitoring-platform-approach Ask: What monitoring approach do you currently use verify outcomes on the ground? Answer: pick one Requirement type: credentials - Satellite imagery with AI analysis [satellite-ai] - Ground-based monitoring with field agents [ground-based] - Community-based monitoring with mobile reporting [community-based] - Combined satellite + ground truth verification [combined] #### UC-I-113 / iot-sensor-approach Ask: What type of sensor or data collection devices will be used? Answer: pick one Requirement type: devices - GPS/location tracking devices [gps-location] - Environmental sensors (temperature, humidity, etc.) [environmental] - Smart meters (energy, water usage) [smart-meters] - Mobile phone-based data collection (photos, GPS, manual entry) [mobile-collection] #### UC-I-113 / timestamping-approach Ask: How is events and evidence currently timestamped for this solution? Answer: pick one Requirement type: audit-trail - Digital timestamping (each event anchored with tamper-proof proof) [on-chain] - Batch anchoring (events collected, periodically anchored) [batch-anchoring] - Trusted third-party timestamping authority [trusted-authority] - Not sure, need guidance on timestamping approach [guidance-needed] ### UC-I-114: Clean cookstove distribution and usage verification Security level: Standard. #### UC-I-114 / usage-monitoring Ask: How is cookstove usage monitored? Answer: pick one Requirement type: credentials - IoT temperature/humidity sensor on stove [iot-sensor] - Periodic household surveys and self-reporting [survey-self-report] - Hybrid IoT sensors + spot checks [hybrid-iot-checks] #### UC-I-114 / carbon-reduction-verification Ask: How do you verify carbon reduction? (direct testing, usage-based calculation, audits?) Answer: pick one Requirement type: integration - Default emission factors from UNFCCC methodology [unfccc-default] - Fuel consumption measurement with combustion analysis [fuel-consumption] - Biochar production measurement for sequestration credit [biochar-sequestration] #### UC-I-114 / distribution-tracking Ask: How is cookstove distribution tracked? Answer: pick one Requirement type: general - Unique serial number registry with transfer history [serial-registry] - Batch distribution certificates with bulk handoff [batch-certificates] - Household geolocation with mobile payment verification [geolocation-payment] #### UC-I-114 / payment-model Ask: What payment model incentivizes usage? Answer: pick one Requirement type: money - One-time subsidy at distribution [onetime-subsidy] - Monthly usage-based payments via IoT verification [monthly-iot-payments] - Carbon credit revenue sharing with automated rules distribution [carbon-revenue-share] #### UC-I-114 / cookstove-volume Ask: What is the monthly volume of cookstoves distributed you need to track? Answer: pick one Requirement type: scale - Under 1,000 items [small] - 1,000–10,000 items [medium] - 10,000–100,000 items [large] - Over 100,000 items [enterprise] #### UC-I-114 / iot-sensor-approach Ask: What type of sensor or data collection devices will be used? Answer: pick one Requirement type: devices - GPS/location tracking devices [gps-location] - Environmental sensors (temperature, humidity, etc.) [environmental] - Smart meters (energy, water usage) [smart-meters] - Mobile phone-based data collection (photos, GPS, manual entry) [mobile-collection] ### UC-I-115: Co-financed measurement and verification registry (multi-funder climate and conservation programmes) Security level: Standard. #### UC-I-115 / mrv-funder-count Ask: How many distinct funders / buyers co-finance the programme? Answer: pick one Requirement type: scale - 2-3 (small co-financing arrangement) [small] - 4-10 (mid-scale pool) [medium] - 10+ (large co-financing or carbon-market scale) [large] #### UC-I-115 / mrv-evidence-source Ask: What MRV evidence sources do you need to aggregate? Answer: pick one Requirement type: audit-trail - Field verification only [field] - Remote-sensing only (satellite, aerial) [remote] - Hybrid (remote + field + IoT + community) [hybrid] #### UC-I-115 / mrv-double-count-risk Ask: How significant is double-counting risk across funders? Answer: pick one Requirement type: scale - Low: funders cover different outcomes [low] - Moderate: overlapping outcome claims possible [moderate] - High: funders claim same outcomes (carbon credits) [high] #### UC-I-115 / mrv-verifier-model Ask: Who verifies outcomes? Answer: pick one Requirement type: general - Single third-party verifier (e.g. Verra VVB) [single-verifier] - Multi-verifier consensus [multi-verifier] - Community + verifier hybrid [community-hybrid] #### UC-I-115 / mrv-disclosure Ask: What disclosure level applies to MRV evidence? Answer: pick one Requirement type: general - Aggregated public disclosure (anonymised) [aggregate] - Full public disclosure (open MRV) [full-public] - Funder-private, public aggregate [hybrid] ### UC-J-115: Volunteer management and hour tracking Security level: Standard. #### UC-J-115 / volunteer-tracking-method Ask: How are volunteer hours currently tracked and verified? Answer: pick one Requirement type: general - Manual timesheet submission [manual-timesheet] - Digitally verified volunteer credentials [blockchain-verified] - Digital badges and attestations [digital-badges] #### UC-J-115 / verification-approach Ask: What fraud tolerance level for volunteer time reporting? (self-reported with review vs requiring external verification?) Answer: pick one Requirement type: credentials - Supervisor attestation with permanent tamper-proof record [supervisor-attestation] - Multi-party consensus verification [multi-party-consensus] - Real-time location and activity verification [location-activity-verify] #### UC-J-115 / impact-measurement Ask: What volunteer impact metrics must you report? (hours, beneficiaries served, cost equivalent?) Answer: pick one Requirement type: audit-trail - Hours-based impact calculation [hours-based] - Outcome-driven impact metrics with digital proof [outcome-driven] - digital impact rewards [tokenized-rewards] #### UC-J-115 / reporting-mechanism Ask: What reporting structure is required for volunteer activities? Answer: pick one Requirement type: audit-trail - Weekly aggregated reports with signed attestation [weekly-aggregated] - Real-time digital ledger event logging [realtime-logging] - Donor-facing impact dashboard with verified data [donor-dashboard] #### UC-J-115 / volunteer-staff-count Ask: How many staff or individuals need to be tracked in volunteer management? Answer: pick one Requirement type: scale - Under 50 [small] - 50–200 [medium] - 200–1,000 [large] - Over 1,000 [enterprise] #### UC-J-115 / volunteer-jurisdictions Ask: How many jurisdictions or countries does volunteer operations span? Answer: pick one Requirement type: residency - Single country [single] - 2–5 countries [few] - 6–15 countries [many] - Over 15 countries [global] ### UC-J-116: Staff deployment records across locations Security level: Standard. #### UC-J-116 / deployment-tracking-method Ask: What system tracks staff deployment across locations? Answer: pick one Requirement type: general - Central HR database with location updates [central-db-updates] - Digitally recorded deployment events [blockchain-events] - Real-time GPS and check-in verification [gps-checkin-verify] #### UC-J-116 / cross-border-deployment Ask: Are staff deployed across national borders requiring regulatory documentation? Answer: pick one Requirement type: general - Domestic deployment only [domestic-only] - International deployments with verifiable visas and permits [intl-visa-permits] - Rapid deployment across regions with compliance automation [rapid-intl-deployment] #### UC-J-116 / role-specifications Ask: How many distinct staff roles exist, and what competency verification is required? Answer: pick one Requirement type: credentials - Manual role assignment with documentation [manual-assignment] - Digitally verified role credentials [blockchain-role-cred] - Dynamic role binding with automated competency checks [dynamic-competency] #### UC-J-116 / deployment-reporting Ask: What reporting requirements exist for deployment records? Answer: pick one Requirement type: audit-trail - Monthly staff location reports [monthly-reports] - Real-time deployment dashboard for management [realtime-dashboard] - Compliance reporting with digitally verified attendance [compliance-verified] #### UC-J-116 / staff-deploy-staff-count Ask: How many staff or individuals need to be tracked in staff deployment? Answer: pick one Requirement type: scale - Under 50 [small] - 50–200 [medium] - 200–1,000 [large] - Over 1,000 [enterprise] #### UC-J-116 / staff-deploy-jurisdictions Ask: How many jurisdictions or countries does staff deployment span? Answer: pick one Requirement type: residency - Single country [single] - 2–5 countries [few] - 6–15 countries [many] - Over 15 countries [global] #### UC-J-116 / deployment-tracking Ask: How should staff deployments be tracked and verified? Answer: pick one Requirement type: general - GPS-based location tracking with check-in/check-out [gps-checkin] - QR code check-in at deployment sites [qr-checkin] - Manager-attested deployment records [manager-attested] - Self-reported with supervisor verification [self-report] ### UC-J-117: Training completion records Security level: Standard. #### UC-J-117 / credential-format Ask: What credential formats do employers and regulators in your context accept? Answer: pick one Requirement type: integration - Paper certificates checked in person [paper-certificates-checked-in-person] - Digital documents (PDF, email) shared and reviewed manually [digital-documents-pdf-email-shared-and-r] - Online registry or database lookup to confirm validity [online-registry-or-database-lookup-to-co] - No standard process, it varies by employer and jurisdiction [no-standard-process-it-varies-by-employe] - Not sure, varies across our operating contexts [not-sure-varies-across-our-operating-con] #### UC-J-117 / verification-entity Ask: Who is authorized to issue and verify training credentials? Answer: pick one Requirement type: credentials - Internal training department only [internal-only] - Multiple accredited training institutions [multi-accredited] - Third-party independent assessor with digital ledger attestation [third-party-attest] #### UC-J-117 / expiration-tracking Ask: How are training credential expiration and renewal tracked? Answer: pick one Requirement type: credentials - Manual expiry date in documents [manual-expiry] - automated rules automated expiry and renewal prompts [smart-contract-expiry] - Digitally verified recertification with progressive disclosure [blockchain-recert] #### UC-J-117 / recognition-scope Ask: What is the geographic and institutional recognition scope for training? Answer: pick one Requirement type: credentials - Single organization only [single-org] - National or regional NGO consortium [regional-consortium] - International recognition via digital ledger credential registry [intl-blockchain] #### UC-J-117 / training-staff-count Ask: How many staff or individuals need to be tracked in training tracking? Answer: pick one Requirement type: scale - Under 50 [small] - 50–200 [medium] - 200–1,000 [large] - Over 1,000 [enterprise] #### UC-J-117 / training-jurisdictions Ask: How many jurisdictions or countries does training programmes span? Answer: pick one Requirement type: residency - Single country [single] - 2–5 countries [few] - 6–15 countries [many] - Over 15 countries [global] #### UC-J-117 / training-records Ask: How are training completion records currently managed? Answer: pick one Requirement type: credentials - Digital certificates with digital verification [digital-certs] - LMS integration (link to existing learning management system) [lms-integration] - Standalone training record ledger [standalone] - Not sure, need guidance [guidance-needed] ### UC-J-118: Safeguarding training verification Security level: Standard. #### UC-J-118 / training-standard Ask: What are your current training standards for your workforce? Answer: pick one Requirement type: credentials - Internal organizational safeguarding policy [internal-policy] - National safeguarding standards (NSPCC, Local Authority guidance) [national-standards] - International safeguarding standards with digital verification [intl-standards-verified] #### UC-J-118 / assessment-method Ask: What competency verification level do your safeguarding standards require? (attendance only, testing, practical eval?) Answer: pick one Requirement type: credentials - Training attendance with manual assessment notes [attendance-manual] - Automated online quiz with instant digital ledger recording [online-quiz-blockchain] - Competency-based assessment with signed supervisor attestation [competency-supervisor] #### UC-J-118 / renewal-tracking Ask: How is safeguarding training renewal tracked and enforced? Answer: pick one Requirement type: credentials - Annual manual reminder emails [manual-reminders] - automated rules automated expiry with forced re-enrollment [smart-contract-enforce] - Progressive disclosure of credential status with renewal prompts [progressive-disclosure] #### UC-J-118 / non-compliance-handling Ask: How is non-compliance with safeguarding training handled? Answer: pick one Requirement type: legal-checks - Suspension of duties pending retraining [duty-suspension] - Automated access revocation when training lapses [auto-revocation] - Escalated alerts to safeguarding board with digital evidence [escalation-alerts] #### UC-J-118 / confidentiality-requirements Ask: How are confidentiality requirements balanced with verification needs? Answer: pick one Requirement type: privacy - Centralized records with restricted access control [centralized-restricted] - Zero-knowledge proofs for verification without disclosure [zero-knowledge-proof] - Selective disclosure credentials with consent-based sharing [consent-sharing] ### UC-J-119: Security clearance and access management Security level: Higher. #### UC-J-119 / clearance-levels Ask: How many clearance levels are needed? Answer: pick one Requirement type: privacy - Single access level (all staff identical) [single-level] - Multi-tier clearance (basic, confidential, secret) [multi-tier] - Fine-grained permission model with geofenced access control [fine-grained-geo] #### UC-J-119 / background-check-depth Ask: What depth of background verification is required for your staff? Answer: pick one Requirement type: credentials - Reference checks only [references-only] - Standard background check with criminal records [standard-criminal] - Enhanced check with financial, employment, and health screening [enhanced-screening] #### UC-J-119 / access-control-model Ask: Who currently has access to medical records, and how is that controlled? Answer: pick one Requirement type: privacy - Role-Based Access Control (RBAC) [rbac] - Attribute-Based Access Control (ABAC) with automated policy enforcement [abac-smart] - Verified access with zero-trust architecture [blockchain-zerotrust] #### UC-J-119 / permission-escalation Ask: How are higher-level permission requests handled? Answer: pick one Requirement type: legal-checks - Manager approval with manual documentation [manager-approval] - automated rules-enforced escalation with tiered authorization [smart-escalation] - Risk-aware escalation with continuous re-verification [risk-aware-escalation] #### UC-J-119 / review-cycle Ask: How frequently are clearances reviewed? Answer: pick one Requirement type: legal-checks - Annual formal review [annual-review] - Quarterly risk-based review with automated rules triggers [quarterly-risk] - Continuous monitoring with real-time re-verification [continuous-monitoring] ### UC-J-120: Duty of care / staff location tracking in emergencies Security level: Higher. #### UC-J-120 / alert-escalation Ask: How are emergency alerts currently escalated? Answer: pick one Requirement type: governance - Manual escalation through phone tree [manual-phonetree] - automated rules-triggered automated alerts to command center [auto-alerts] - AI-powered risk assessment with context-aware escalation [ai-risk-escalation] #### UC-J-120 / privacy-balance Ask: How is the privacy vs. safety balance achieved? Answer: pick one Requirement type: privacy - Opt-in location tracking during emergencies only [opt-in-emergencies] - Geofenced monitoring with selective disclosure [geofence-selective] - privacy-preserving verification verification (location proof without exact coordinates) [zkp-location] #### UC-J-120 / emergency-protocol Ask: What is your current emergency procedure for verifying duty of care? Answer: pick one Requirement type: legal-checks - Manual check-in with supervisor confirmation [manual-checkin] - Automated safe/unsafe status via digital ledger with multi-source verification [auto-status-verify] - distributed autonomous duty-of-care contract with medical/security integration [dao-duty-care] #### UC-J-120 / geographic-coverage Ask: What geographic areas and connectivity scenarios are covered? Answer: pick one Requirement type: general - Urban areas with reliable mobile and internet coverage [urban-areas-with-reliable-mobile-and-int] - Remote areas where internet connectivity is unreliable or intermittent [remote-areas-where-internet-connectivity] - High-risk zones where normal communications infrastructure may be unavailable [high-risk-zones-where-normal-communicati] - Mix of all the above across different deployment locations [mix-of-all-the-above-across-different-de] #### UC-J-120 / coverage-requirements Ask: What coverage percentage and response time are required? Answer: pick one Requirement type: general - Best effort, no guaranteed SLA [best-effort] - 99% coverage with 5-minute response time SLA [99-percent-sla] - 99.9% coverage with sub-minute alerts and automated escalation [999-percent-sla] #### UC-J-120 / audit-trail-approach Ask: What level of record-keeping and evidence trail do you need for this process? Answer: pick one Requirement type: audit-trail - Full permanent audit trail: every action logged digitally [full-immutable] - Key events only: milestones and approvals logged digital [key-events] - Hybrid: key details logged digitally, full records stored separately with tamper-proof links [hybrid] - Not sure, need guidance on audit trail design [guidance-needed] ### UC-J-121: Contractor and consultant verification Security level: Standard. #### UC-J-121 / verification-depth Ask: What depth of contractor verification is required? Answer: pick one Requirement type: credentials - Basic portfolio and reference check [basic-portfolio] - Digitally verified qualifications and past client attestations [blockchain-verified] - Deep verification with background check and compliance screening [deep-compliance] #### UC-J-121 / qualification-tracking Ask: What contractor qualifications require periodic renewal and at what frequency? Answer: pick one Requirement type: credentials - Static documentation files [static-docs] - Digital credential wallet with continuous re-verification [blockchain-wallet] - Automated qualification lifecycle management [smart-contract-lifecycle] #### UC-J-121 / performance-history Ask: What contractor performance metrics do you track? (cost, quality, timeliness, compliance?) Answer: pick one Requirement type: audit-trail - Spreadsheet or document-based performance records [spreadsheet-or-document-based-performanc] - Formal performance management system with ratings and reviews [formal-performance-management-system-wit] - Project-based assessment (cost, quality, timeliness, compliance) recorded per engagement [project-based-assessment-cost-quality-ti] - No formal tracking, performance assessed informally [no-formal-tracking-performance-assessed-] - Not sure, need to establish a process [not-sure-need-to-establish-a-process] #### UC-J-121 / reference-checking Ask: Do you verify contractor references, and how formally? (informal calls vs formal attestations?) Answer: pick one Requirement type: credentials - Manual phone/email reference checks [manual-checks] - Digitally signed client attestations [blockchain-attest] - Distributed verification network with peer-reviewed ratings [decentralized-consensus] #### UC-J-121 / contractor-staff-count Ask: How many staff or individuals need to be tracked in contractor verification? Answer: pick one Requirement type: scale - Under 50 [small] - 50–200 [medium] - 200–1,000 [large] - Over 1,000 [enterprise] #### UC-J-121 / contractor-jurisdictions Ask: How many jurisdictions or countries does contractor engagement span? Answer: pick one Requirement type: residency - Single country [single] - 2–5 countries [few] - 6–15 countries [many] - Over 15 countries [global] #### UC-J-121 / audit-trail-approach Ask: What level of record-keeping and evidence trail do you need for this process? Answer: pick one Requirement type: audit-trail - Full permanent audit trail: every action logged digitally [full-immutable] - Key events only: milestones and approvals logged digital [key-events] - Hybrid: key details logged digitally, full records stored separately with tamper-proof links [hybrid] - Not sure, need guidance on audit trail design [guidance-needed]