Delivery Acceptance Form: Why Ask for a Signature (and How to Do It Paperless)

You delivered the website, the system or the renovation. The client replied "looks good" in a WhatsApp voice message and vanished. Two weeks later, they show up asking for an adjustment "that was agreed", and the invoice is still sitting there waiting for an "approved" nobody made official. That's the cost of delivering without acceptance: the project never really ends.

The acceptance form solves this with a short document that records that the client received what was agreed and agrees that stage is complete. This article shows what it needs to include, when to ask for it and how to collect the signature on a phone, with proof you can present later.

What an acceptance form is for

It does three things at once.

• It closes the scope. What was delivered is described. A new request after acceptance is a different request, not an "adjustment that was missing".
• It releases billing. If the contract provides for payment on delivery, acceptance is the trigger. Without it, the conversation about payment turns into an argument about memory.
• It protects both sides. The client benefits too: they know exactly what they're receiving and what was left out, instead of finding out in the middle of using it.

Acceptance doesn't stop the client from complaining about a real defect. What it prevents is the endless complaining about something that was already shown, tested and approved.

What the form should include

One page is enough. Nobody reads a six-page document, and what nobody reads protects nobody.

Item	What to write
Identification	Project name, name and CNPJ or CPF (Brazilian company/individual tax IDs) of the client, name of the person delivering
What was delivered	Objective list of items, referencing the contract or proposal
Acceptance criteria	How it was verified to be ready (e.g., "all pages in the proposal published and tested on mobile")
Agreed pending items	What was left for later, with a deadline, so it doesn't look like an oversight
What happens next	Warranty period for defect fixes, if any, and how to request them
Declaration	A clear sentence: "I declare that I have received the items above and accept them for the purposes of the contract"
Signature	Name, date and time of the person accepting

If you'd like to start from a ready-made text, the delivery acceptance form template provides this structure for you to adapt.

The acceptance criteria are the part most often missing

Most forms say "delivered as agreed" and stop there. The problem is that "as agreed" is exactly what's in dispute. Write how the delivery was checked: who tested it, in which environment, what was seen working. The more concrete the criteria, the less room for "but I expected something different".

When to ask: by stage or only at the end

It depends on the size of the project and how long the client takes to respond.

Acceptance at the end

It works for short projects, one or two weeks long, with a single delivery: a visual identity, a landing page, a training session. One form, at delivery, and you're done.

Acceptance by stage

This is what we recommend for anything lasting more than a month. A renovation, system or campaign project has phases, and each accepted phase becomes a firm foundation for the next. If the client approves the layout in week 3 and changes their mind in week 10, the stage form shows what was decided and when, and the change becomes a new request, with its own deadline and cost.

Situation	When to ask
Single, short delivery	At the end
Project with phases and partial payments	At the end of each phase, before billing the installment
Construction or renovation	Per completed stage and at final handover
Recurring contract (support, monthly marketing)	At agreed milestones, such as the month-end or quarter-end close

In projects with a schedule, it helps to mark acceptance as a milestone: the stage only counts as complete when the milestone is met, and the team sees that in the plan.

Paper, PDF by email or signing on a phone

The old way is to print, sign, scan and send it back. It works, but it's slow, especially with the client who's already slow to respond. A PDF by email with "reply saying approved" is faster, but the proof is weak: a loose email in the middle of an inbox.

The most practical way today is a link the client opens on their phone, reads the form and signs on the spot. The key is that the signature comes with records that identify who accepted and when.

How to collect acceptance in Tasskee

In Tasskee, a form can collect a signed acceptance. You build the form, generate the public link and send it to the client, who opens the link, checks the content and signs. The record keeps:

• the name of the person who signed;
• the IP address the signature came from;
• the date and time;
• the SHA-256 hash of what was signed, which serves to show the content wasn't altered afterward.

It's important to be clear about the scope of this: it's a simple electronic signature, not a signature with an ICP-Brasil certificate (Brazil's official digital certificate standard). For the vast majority of business-to-business deliveries, an acceptance recorded this way serves as proof that the client saw it and agreed. For contracts where the law or the industry requires a digital certificate, this isn't the right instrument.

A workflow that works, step by step

1. Before delivering, agree with the client on what will be checked. Send the list of items and the criteria one or two weeks before the deadline, so there are no surprises.
2. Deliver and demonstrate. Show the result working. If the client follows the project through the guest portal, they've already seen the progress and the final approval is almost a formality.
3. Send the form the same day. Acceptance requested three weeks later loses force; the client has already forgotten what was shown.
4. Set a deadline for a response. For example, five business days. Any clause about the client's silence after that deadline is a matter for your lawyer.
5. Record pending items as tasks. What was agreed for later becomes a task with a deadline, and the form references that list.
6. Release billing. With the acceptance filed in the project, billing no longer depends on anyone's memory.

An example form, in plain language

To get a sense of the tone, imagine an agency that delivered a clinic's corporate website in Joinville. The form could say, in just a few lines: the project "Clínica Exemplo corporate website"; the six pages described in the proposal were delivered, along with a working contact form and the content editing panel; the review was done in a meeting with the receptionist and the manager, on a computer and on a phone; it was agreed, with a ten-business-day deadline, that two photos would be swapped and one text adjusted; acceptance of the items above is declared for the purposes of the contract. No legalese, and everything that matters is stated.

Common mistakes

• A form that's too generic. "Services rendered" describes nothing. List the items.
• Asking only after the client complains. Acceptance requested in the middle of a dispute looks like a defense, not a routine.
• Mixing acceptance with a new request. If the client wants an adjustment, note it as an agreed pending item or as a new request, and only then collect the signature for what's done.
• Keeping the acceptance in an email. In six months nobody can find it. The document needs to live alongside the project.

A note on the legal side

This article describes management practice, not legal advice. The validity of an electronic signature, the effects of the client's silence and warranty clauses depend on your contract and your industry. Have a lawyer review the form template once; after that, it becomes routine and you only fill in the items for each delivery.

If your operation also bills by the hour, acceptance pairs well with the hour closing for the client: one document says "I received what was delivered", the other says "I acknowledge the hours for the period". Together, they close the financial conversation with no rework.