Register Driver Honorarium with Confidentiality Declaration
Blindeforbundet requires that drivers transporting contacts sign a confidentiality declaration before or alongside receiving honorarium payment. The app must provide a driver honorarium registration form, support sending an encrypted declaration to the driver (by contact or email), track whether the declaration has been acknowledged, and prevent final submission of the honorarium claim until acknowledgement is received or an override is granted by a coordinator. This workflow is gated behind a feature flag so it is only available to organizations that have enabled the driver feature.
User Story
Audience Summaries
This story addresses a direct legal and compliance requirement for Blindeforbundet, an organization that transports contacts with sensitive health information. By digitizing the driver confidentiality declaration workflow, the platform eliminates paper-based processes that expose the organization to legal liability through incomplete or lost documentation. Every driver engagement becomes fully auditable, protecting the organization from regulatory risk while demonstrating commitment to data protection standards. The feature-flag architecture ensures this compliance workflow is scoped only to organizations with the driver feature enabled, keeping the experience clean for other users.
Longer term, this capability positions the platform as a trusted tool for organizations operating under strict privacy regulations, opening the door to similar compliance-sensitive clients and increasing platform stickiness among existing ones.
This story carries medium priority but significant compliance weight, making it a delivery risk if deprioritized. It involves multiple cross-functional workstreams: the honorarium registration form, encrypted declaration delivery (contact or email channel), acknowledgement tracking, and conditional submission gating. A feature flag must be implemented and tested across both enabled and disabled organization states. Acceptance criteria require thorough end-to-end testing covering the full declaration lifecycle — send, acknowledge, unlock, and submit with audit log.
The coordinator override path adds a secondary workflow that needs its own test coverage. Dependencies link to the base travel expense registration story, so that story must be stable before this one can be completed. Rollout should be coordinated with Blindeforbundet directly to validate the declaration content and delivery channel configuration before go-live.
Implementation requires building a driver honorarium registration form as a new expense type, conditionally rendered based on a feature flag checked at the organization level. The declaration delivery system must support encrypted transmission via at least two channels (contact/email), requiring integration with the existing messaging or email service. Acknowledgement state must be persisted per honorarium record, likely as a status enum (pending, acknowledged, overridden) on the honorarium entity. Submission gating logic must block final claim submission unless acknowledgement status is 'acknowledged' or a coordinator override flag is set.
An audit log entry must be written at submission time linking the declaration record to the payment record. Edge cases include: declaration sent but never acknowledged, coordinator override flow, feature flag toggled mid-workflow, and re-sending declarations. All new state transitions should be covered by unit and integration tests.
Acceptance Criteria
- Given the driver feature flag is enabled for my organization, when I open the expense registration screen, then a 'Driver Honorarium' option is available
- Given I select driver honorarium, when I fill in the registration form, then I can specify the driver, amount, and trip details
- Given I complete the honorarium form, when I tap 'Send Declaration', then a confidentiality declaration is sent to the driver via the configured channel and a pending status is shown
- Given the driver has received the declaration, when they acknowledge it, then the status updates to 'Acknowledged' and the honorarium claim is unlocked for submission
- Given the driver feature flag is disabled for my organization, when I view the expense type list, then the driver honorarium option is not displayed
- Given the declaration has been acknowledged, when I submit the honorarium, then the claim is stored with an audit log entry linking the declaration to the payment
Business Value
Driver honorarium with confidentiality declaration is a legal and compliance requirement for Blindeforbundet when transporting contacts with sensitive health information. Digitizing this workflow replaces paper-based processes that are prone to loss or incomplete documentation, reducing legal exposure and ensuring all driver engagements are fully auditable.
Components
- Driver Honorarium Form ui
- Driver Fee Registration Form ui
- Confidentiality Declaration Send Screen ui
- Confidentiality Declaration Acknowledgement Screen ui
- Declaration Status Badge ui
- Driver Assignment History List ui
- Driver Feature Flag Guard Widget ui
- Driver Assignment Service service
- Confidentiality Declaration Management Service service
- Declaration Acknowledgement Service service
- Declaration Delivery Notification Service service
- Organization Feature Flag Service service
- Declaration Encryption Service service
- Driver Assignment Repository data
- Confidentiality Declaration Repository data
- Declaration Template Repository data
- Declaration Supabase Storage Adapter data
- Declaration Audit Logger infrastructure
- Driver Feature Flag Configuration infrastructure
- Driver Honorarium Service service