# Delivered work is not always an accepted outcome. · New requests appeared after work began

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 separate the original task, comments on completed work and new requests. With the team, I would prepare continuation options and their effects on scope and the nearest date.

## What you would have

A comparison of the original task and changes, with options for the next stage.

## Participants

The client, delivery lead and commercial owner.

## Roles and decisions

The team provides estimates; the parties approve changes to scope and terms.

## 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