Customer acceptance
A Plainly deployment is ready only when the configured product, customer integration and agreed measurement all pass. This is the shared sign-off standard for a paid pilot.
One written acceptance recordowned by Plainly and the customer technical owner before production launch
What gets accepted
| Area | Evidence required | Owner |
|---|---|---|
| Configuration | Client, campaign, policy and configuration identifiers, brand colours, approved domains, employee contribution range, employer rules, understanding question and next step pass their contracts. | Plainly |
| Calculations | Employee take-home, pension funding, employer cost, matching, NI sharing and supported minimum-wage boundaries pass unit, threshold and browser cases for the supported tax year. | Plainly |
| Integration | The loader renders on staging, rejects an unapproved origin, resizes correctly and preserves state between enabled tools. | Both |
| Privacy | No calculator values leave the iframe; any customer-side event collection is value-free and covered by the customer's notice. | Both |
| Accessibility | Keyboard, labels, focus, zoom, reduced motion and 320px to desktop layouts pass the agreed checks. | Plainly |
| Operations | Support contacts, incident route, release identifier and rollback owner are recorded. | Both |
| Measurement | One primary outcome, baseline, value-free event definitions, aggregate evidence source, optional understanding categories and reporting owner are approved without inventing an ROI claim. | Customer |
Release evidence
- Exact Git commit and production deployment recorded
- Type, unit, build, CSP, bundle-budget and browser suites passing
- Automated WCAG A and AA scan passing on the contracted workflow
- Mobile overflow and host-page scrolling checked at supported widths
- Customer configuration contract passing before the embed can build
- Machine-checked customer release manifest and written acceptance record agree
- Staging acceptance dated by both named owners
Launch decision
A failed calculation, privacy, origin-control or accessibility check blocks launch. Lower severity presentation issues need a named owner and agreed date. Production is verified against the accepted commit, and rollback returns to the last accepted deployment.