Blog Kalinotes - April 2026

Discover how to organize website acceptance testing efficiently with your client. Definition, key steps, best practices and tools to centralize feedback — complete guide for web designers and freelance developers.

Why the acceptance phase is crucial (and often rushed)

The acceptance phase is an essential step but generally poorly managed by independent service providers. Without proper structure, this phase generates repetitive exchanges, requests exceeding the initial scope and relational friction.

What is website acceptance testing?

Acceptance testing represents the verification and validation phase before going live. It determines if the deliverable matches the agreed specifications.

Timing of acceptance testing in the project

The seven steps of a typical web project:

1. Client brief and specifications
2. Mockups and wireframes
3. Development on test environment
4. Internal acceptance
5. Client acceptance on test environment
6. Corrections from acceptance
7. Acceptance report signature and go-live

The five steps of organized acceptance testing

Step 1 — Prior internal acceptance

Before sending to the client, perform a complete verification including:

• Compliance with specifications
• Browser testing (Chrome, Firefox, Safari, Edge)
• Responsive verification (mobile and tablet)
• Form, link and redirection validation
• Performance control

Step 2 — Transmission of preview link

Communicate to your client:

• What they need to check
• The deadline for feedback
• A single channel for transmitting observations

Step 3 — Centralization of feedback

An effective system must allow:

• Precise identification of the concerned area
• Association of visual context to each request
• Maintenance of project history
• Tracking of correction progress

Step 4 — Corrections and validation

For each feedback:

• Determine if it falls under acceptance or evolution
• Process items within scope
• Bill separately for out-of-scope requests
• Document each correction made

Step 5 — Signed acceptance report

The signed report attests to the deliverable's compliance and represents the service provider's legal protection to trigger final payment.

Structure of the acceptance checklist

Elements to include

• Project information (name, test URL, date, version)
• List of features with status
• Detail of anomalies (description, screenshot, priority)
• History of client feedback
• Signature area with validation date

Five common mistakes to avoid

1. Absence of acceptance deadline
2. Acceptance of feedback on multiple channels
3. Starting corrections before complete collection of observations
4. Blurring the line between acceptance and evolutions
5. Going live before signing the acceptance report

Comparison of acceptance testing tools

The browser extension reduces client-side friction by allowing feedback directly on the page with automatic screenshot capture.

Acceptance report template

Summary of key points

• Plan acceptance from the contract
• Perform comprehensive internal acceptance before delivery
• Define explicit deadline for feedback
• Use a single centralization channel
• Differentiate acceptance (included) and evolutions (billable)
• Do not go live before signing the acceptance report
• Use signed acceptance report as condition for final payment