Payments, Milestones and Acceptance

Purpose

Milestones and acceptance criteria connect delivery progress to commercial control.

They ensure that both parties understand when work is complete and when payment is due.

Milestone Design

A good milestone is:

• clearly named

• linked to deliverables

• time-bound

• evidenced

• commercially meaningful

• capable of acceptance

Acceptance Criteria

Acceptance criteria should define what must be true for a deliverable to be accepted.

Examples:

• document delivered in agreed format

• prototype demonstrates agreed workflow

• code merged into agreed repository

• test evidence provided

• security review completed

• customer walkthrough completed

• defects resolved to agreed threshold

Acceptance Process

The standard acceptance process is:

1. Deliverable submitted.

2. Evidence provided.

3. Customer review period starts.

4. Customer accepts, rejects with reasons, or requests clarification.

5. Rejection must reference agreed acceptance criteria.

6. Accepted deliverable triggers milestone completion where applicable.

Payment Evidence

Payment evidence may include:

• signed acceptance certificate

• approved milestone report

• customer email approval

• delivery dashboard evidence

• completed test evidence

• repository release tag

• deployment record