MEMBER PORTAL ACCEPTANCE CHECKLIST RapidIteration | https://rapiditeration.com/insights/nonprofit-member-portal-requirements/ Version: October 31, 2026 Adapt these planning prompts to your portal and use approved sample data. PROJECT Organization: Decision owner: Intended first release: Five highest-priority member/staff journeys: Explicit exclusions: FOR EACH JOURNEY ID and priority: Person, role and membership state: Record type, publication state and group: Starting point and action: Expected result: Expected result for an unauthorized person: Failure/recovery behaviour: Acceptance evidence (observed result, date, tester, version): Open issue and accountable owner: Accepted / changes required / deferred, with reason: SAMPLE JOURNEYS TO ADAPT [ ] Guest can find and open public resources. [ ] Closed-group content is protected in search, direct URLs and attachments. [ ] Pending members understand their status; approval changes access correctly. [ ] Removed members lose access as agreed; downloaded-copy limits are understood. [ ] Staff can draft, review, publish, correct and archive content. [ ] Regional event dates display correctly, including a daylight-saving example. [ ] Registration, cancellation and capacity behave as agreed. [ ] Missing translations have an agreed visitor experience and content owner. [ ] Migration counts reconcile; exceptions, attachments and old URLs are checked. [ ] Key journeys work using the agreed accessibility testing approach. [ ] Account ownership, exports, backups, recovery and support are documented. [ ] Staff complete handover tasks without developer intervention. BUY / CONFIGURE / BUILD COMPARISON Requirement: Product or proposed implementation: Native / configuration / integration / custom work: One-time cost from supplier: Recurring cost from supplier, including currency and period: Staff administration requirement: Export and exit arrangements: Open assumptions and who resolves them: RELEASE DECISION Evidence reviewed: Blocking issues: Accepted limitations: Recovery plan and responsible person: Approver and date: