Design Sign-off Form

Phase: Execution | Audience: Shared | Project: WEB-2026-01 Corporate Website Development

Understand it first

In simple words: The Design Sign-off Form is the client's formal written approval of the final designs. After this, design changes become change requests, and the second payment (M2) can be invoiced.

Think of it like: Before a tailor cuts the cloth, you approve the final measurements and design. After that, changes cost extra.

How it connects to other documents

1. Completes deliverable D2 in the SOW.
2. Triggers the M2 invoice in the Invoice Tracker.
3. Later design changes go through the Change Request process.

The sample document

Below is the actual document for project WEB-2026-01. Read the purpose first, then go through each numbered section.

Issued by: [Your Company] Technologies Pvt. Ltd.

Purpose: Formal client approval of the final UI designs. Signing this form completes deliverable D2 and triggers the M2 invoice.

1. Designs submitted

Design files: Figma project link [link]. Exported PDFs attached to the sign-off email of 28 Oct 2026.

2. Revision rounds

3. Client comments at sign-off

Approved. Minor change to hero image crop to be handled during development, as agreed in the call of 29 Oct.

4. Declaration

I confirm that the designs listed above are approved for development. Changes after this sign-off will be handled through the change request process and may affect cost and schedule.

WEB-2026-01/DSO · v1.0 · Shared with client. Bracketed items such as [Client Name] are placeholders.

Key takeaways

1. Sign-offs protect both sides and trigger payments.
2. Record how many revision rounds were used.
3. Written approval is better than a verbal 'looks good'.

Common mistakes to avoid

1. Starting development without signed approval.
2. Not recording which version was approved.
3. Forgetting to raise the invoice on the same day.

Next lesson: 26. Change Request Form and Log