# Delivered work is not always an accepted outcome.

All stories are fictional. They do not describe specific people, companies or projects. Any resemblance is coincidental.

The team presents the completed work and a closed task list. The client expected something else. Some comments concern defects, some new requests and some agreements the parties remember differently. The next demonstration could repeat the same conversation.

## Where we could start

I would review agreements and comments with the participants. I would distinguish confirmed conditions from new expectations and identify decisions missing for the next review.

## What you would have

Questions and decisions needed to agree an acceptance process.

## Participants

The authorised client representative, account owner and delivery lead.

## Roles and decisions

Specialists check implementation quality; the client approves criteria and scope changes.

## Factual experience, separate from the fictional story

MVP Lab / Pivot: Client requirements, approvals, demonstrations and release review.
https://apiperson.com/experience/#work-pivot

Keiss Media: Managing digital campaigns: client requests, estimates, budgets, suppliers and delivery.
https://apiperson.com/experience/#work-keiss

[Criteria are agreed, but there are comments](https://apiperson.com/clients/acceptance/criteria/)

[People understand the agreements differently](https://apiperson.com/clients/acceptance/expectations/)

[New requests appeared after work began](https://apiperson.com/clients/acceptance/new-requests/)

[Book a 30-minute call](https://calendar.app.google/4FrxQkHkAZ32PkzA9)

mailto:apiperson.com@gmail.com