View Expense Registration Summary Before Submission
Before final submission, the peer mentor should be presented with a confirmation screen that summarizes all expense line items, their calculated amounts, the total claim value, any attached receipts (with thumbnails), and the expected approval path (auto-approved or requires coordinator review). The summary screen should apply the cognitive accessibility pattern — single action per screen, plain language, confirm-before-submit — to ensure mentors with cognitive disabilities can review confidently. The user must explicitly tap a 'Submit Claim' button to finalize.
User Story
Audience Summaries
The pre-submission summary screen directly addresses one of the most common sources of coordinator overhead: incorrectly submitted expense claims that require rejection, correction, and resubmission cycles. By presenting mentors — including those with cognitive disabilities, a key demographic for NHF — with a clear, plain-language review screen before finalizing, the platform dramatically reduces submission errors. This translates into measurable time savings for coordinators, faster reimbursement cycles for mentors, and higher trust in the digital system over legacy paper processes. The confirm-before-submit accessibility pattern also signals organizational commitment to inclusive design, which strengthens NHF's relationship with its volunteer network and supports mentor retention.
Reducing friction and error rates in expense submission accelerates adoption of the digital platform across the broader volunteer base.
This story has three upstream dependencies — the base expense registration story and both the mileage and receipt attachment stories — meaning it cannot enter development until those are stable and their data structures are finalized. The summary screen must aggregate all expense line items, calculated amounts, receipt thumbnails, and the approval routing decision (auto-approve vs. coordinator review) into a single coherent view. Accessibility requirements add QA scope: the confirm-before-submit pattern and plain language must be validated against NHF's cognitive accessibility guidelines, potentially requiring user testing with the target demographic.
The 'Edit' navigation back to specific form steps with preserved state is a non-trivial UX flow that needs careful state management design. Rollout should include coordinator feedback on whether the approval path notice reduces their inbound queries about claim status.
The summary screen requires aggregating state from across the multi-step expense form, meaning a well-structured form state model (likely a context or store) must be in place before this story is implemented. Each expense line item — mileage, flat-rate, receipts — must be rendered with its calculated reimbursement value, requiring the calculation logic to be accessible at the summary layer. Receipt thumbnails need to be loaded from local state or a temporary upload reference without re-fetching. The approval routing decision (auto-approve vs.
coordinator review) must be computed client-side or fetched from the API based on claim attributes before the summary renders. The 'Edit' deep-link back to a specific form step must preserve all form state across the navigation, which may require serializing form state to a navigation parameter or a persistent store. Submission triggers the final claim creation API call, and the success/failure states must be handled gracefully with appropriate user feedback and history list refresh.
Acceptance Criteria
- Given I have completed the expense form, when I tap 'Review', then a summary screen displays all expense line items with types, distances or amounts, and calculated reimbursement totals
- Given a receipt has been attached, when the summary screen loads, then a thumbnail preview of the receipt is shown alongside the relevant expense line
- Given the claim qualifies for auto-approval, when the summary screen is displayed, then a notice states 'This claim will be automatically approved'
- Given the claim requires coordinator review, when the summary screen is displayed, then a notice states 'This claim will be sent to your coordinator for approval'
- Given I identify an error on the summary screen, when I tap 'Edit', then I am returned to the relevant step in the expense form with my data preserved
- Given I confirm and submit from the summary screen, when submission succeeds, then a success confirmation is shown and the claim appears in my expense history with 'Submitted' status
Business Value
A confirmation step before submission significantly reduces the rate of incorrectly submitted claims, which in turn reduces coordinator workload in processing rejections and resubmissions. For mentors with cognitive disabilities (a key demographic for NHF), the confirm-before-submit pattern provides a safety net that builds trust and confidence in using the digital system.