IOPARTNER / SAMPLE DELIVERABLE
Acceptance plan
Observable scenarios instead of “it should work”.

Illustrative example: connecting a payment to a customer workspace. These documents show the level of detail we work towards; they are neither a quote nor a promise of results.

Payment and repetition
- One confirmed test payment creates exactly one project. Replaying the same event creates no duplicate or second entitlement.
- An incomplete or failed payment grants no access.

Access and privacy
- Customer A can access their project but cannot open customer B’s project, even with its identifier.
- Expired or reused links are rejected; recovery does not reveal whether another address has an account.

Recorded acceptance
- For each scenario: expected result, observed result, date, environment and evidence. Classify blocking and non-blocking issues.
- The designated owner explicitly accepts the demonstrated version. Significant fixes require verification again.

No implied 24/7 availability or resolution deadline. Hosting, maintenance, licences and support are explicitly included or excluded in your proposal.

support@iopartner.ch