What is tacit consent in client approvals?

Tacit consent is a contract mechanism where a client is given a clear review window and told that silence counts as approval — but only when that rule was agreed upfront, the client received proper notice, and the process is documented. Credently helps agencies and freelancers run that workflow: one secure link, a visible approval deadline, email verification before any decision, and an audit trail with a downloadable certificate. It does not guarantee legal enforceability in your jurisdiction.

The short answer

If your master agreement or statement of work includes a tacit-consent clause, you can send deliverables with a stated deadline. The client may approve, request revision, or not respond. Credently does not offer a reject button — objection is expressed by requesting revision in writing before the deadline. When tacit consent applies and the client stays silent, the request can close as auto-approved when the deadline passes. Everything is logged so you are not relying on a vague "OK" in chat.

What tacit consent means in client approvals

In B2B creative and professional services, "approval" often drags on. Emails pile up, stakeholders travel, and projects stall waiting for a thumbs-up that never arrives. Tacit consent — sometimes called approval by silence — addresses that gap by defining what happens when nobody speaks.

The core idea is straightforward:

• You send a specific deliverable (or bundle of files) for review.
• You set a review deadline long enough for a reasonable review.
• You tell the client that if they do not request revision before that deadline, the work is treated as approved under your agreed terms.

That last point matters. Tacit consent is not a trick to force acceptance. It is a pre-agreed default that both parties understood when they signed the contract. The deadline turns passive silence into a recorded outcome instead of an endless "pending" state.

For agencies, studios, and freelancers, the benefit is operational clarity: billing, handoff, and scope discussions can move forward when clients go quiet — without abandoning fairness or documentation.

What tacit consent does not mean

Misunderstanding tacit consent causes more disputes than using it correctly. Be explicit about the boundaries.

It is not a substitute for a contract clause

Credently can document how a deadline was set, when notice was sent, and what the client did or did not do. It cannot invent a legal rule your agreement never contained. If your contract says nothing about silence counting as approval, running a timer alone does not create tacit consent. Start with language both parties accepted — our sample clause template is a starting point for counsel to adapt, not legal advice.

It is not "we emailed once, so it's approved"

Fair tacit consent requires clear notice: what is being reviewed, how long the client has, what happens if they stay silent, and how to object (request revision). A buried line in a footer or a vague "let me know" does not meet that bar.

It is not guaranteed enforceable everywhere

Whether a tacit-consent clause holds up depends on jurisdiction, industry, contract type, and how the clause was negotiated. Credently documents the workflow; it does not guarantee outcomes in court or with procurement. When in doubt, ask your lawyer — see also our FAQ on enforceability.

Silence without tacit consent is just silence

If you did not configure tacit consent (or your plan/terms do not apply it), a client who never responds has not approved anything. The request may expire without a positive approval outcome. Do not assume auto-approval unless your agreement and request settings align.

Request revision is how clients object

Credently gives clients two active choices before the deadline: Approve and Request revision. There is no separate reject button. A client who wants changes should use revision; that pauses the clock and creates a written record of feedback. Treat revision requests as the legitimate objection path — not as failure of the process.

The role of a pre-agreed contract clause

Software can enforce a deadline on screen; only your contract defines whether silence counts legally. A well-drafted clause typically covers:

• Which deliverables fall under tacit consent (final creative, not every draft).
• Minimum notice period and how notice is delivered (email to the contact on file).
• That written revision requests before the deadline stop auto-approval.
• That the platform record (timestamps, views where logged, final status) supports the process.

Paste adapted language into your MSA, freelance agreement, or SOW before your first live request. The sample clause page explains the placeholders; your counsel should finalize wording for your country and client type.

When a new client pushes back, walk through the clause once at kickoff. Many disputes disappear when everyone knows the rule before the first PDF goes out.

Setting a fair approval deadline

Deadlines that feel punitive backfire. A fair approval deadline balances your need to ship with the client's need to review.

Match the work to the window

A social post mockup might need 48 hours; a 40-page website copy deck might need five business days. Scale duration to complexity, stakeholder count, and whether legal review is involved.

Translate business-day terms into a clear expiry

Credently approval requests currently use 24-hour, 72-hour, or one-week review windows rather than a business-day calendar. If your contract refers to business days, choose a window that leaves the promised working time after weekends and holidays, then state the exact expiry date and time in your message. Mixed calendars and time zones are a common source of "I didn't have enough time" claims.

Say what happens at expiry

In the request email and on the approval page, state plainly: "If we do not receive a revision request by [date/time], this deliverable will be treated as approved under our agreement." Repetition reduces surprise.

One structured link, not a thread

Send one approval link with the files or links attached to that request. Scattering assets across Slack, WhatsApp, and email makes it impossible to prove what was actually under review.

Client notice and email verification

Notice and identity matter as much as the deadline itself.

Notice at send

When you create a request, Credently sends the client an email with the secure link, title, deadline, and your message. The platform logs that the request was sent — part of the audit trail you may rely on internally or share with finance.

No client account required

Your client does not need to sign up for Credently. They open the link in a browser. Only you, as the creator, need an account to build and manage requests. That lowers friction for busy approvers who will never adopt another tool.

Verify before deciding

Before a client can approve or request revision, they confirm identity via a one-time email magic link sent to the address on the request. This reduces the risk that someone with the URL but not the inbox acts on the client's behalf. After verification, the approve and revision actions unlock.

What the client sees

On the approval page: the deliverable (or linked files), countdown to the approval deadline, your terms/context, and the two decision buttons. If they do nothing, the outcome depends on whether tacit consent applies — silence may become auto-approved when the timer ends.

Step-by-step: tacit consent in Credently

Here is the typical flow from contract to certificate.

1. Add a tacit-consent clause to your agreement (counsel-reviewed). Keep a copy in your onboarding pack.
2. Create a Credently account if you have not already. Choose a plan that fits your monthly request volume.
3. Start a new approval request from your dashboard. Add client name and email, title, description, and file or URL links.
4. Pick a review duration that matches the deliverable. The wizard shows how long until auto-approval may apply when tacit consent is in effect.
5. Write a clear email message restating the deadline and what silence means under your contract.
6. Send the request. Credently emails the client and logs the send event.
7. Client opens the link — view events are recorded where available.
8. Client requests a magic link to their inbox and verifies before acting.
9. Client chooses: Approve, Request revision (with written feedback), or no response.
10. Deadline passes. If tacit consent applies and no revision was submitted, status may move to auto-approved. Explicit approval records immediately when they click Approve.
11. Download or share the certificate — reference code, outcome, key audit events, and verification options for third parties.

If the client requests revision, address feedback and send an updated version with a fresh window rather than arguing over an expired timer.

A practical agency scenario

Imagine a branding agency delivering final logo files to a startup marketing lead.

Monday 9:00 — The agency's MSA includes tacit consent for final creative, reviewed by counsel six months ago. They send a Credently request: vector files, brand guidelines PDF, and a one-week review window.

Monday 10:15 — The marketing lead opens the link on mobile during a stand-up. Credently logs the view. They mean to review later but do not verify or decide yet.

Wednesday — A designer on the client side emails informally: "Looks mostly good, maybe tweak the icon?" That informal note is not a Credently revision request. Unless someone submits revision through the verified flow before the deadline, the structured process still treats the deliverable as pending.

Following Monday — Deadline passes with no verified revision. Status becomes auto-approved (tacit consent applies). The agency attaches the certificate to the invoice. Accounts payable sees a reference code, timestamped outcome, and audit events — not a screenshot of a Slack emoji.

If the marketing lead had verified and clicked Request revision with specific feedback on Tuesday, the timer would have paused, the agency would iterate, and a new round would open with a clear paper trail.

This is how tacit consent is supposed to work: fair notice, an easy objection path, and a record that outlives chat apps.

Mistakes to avoid

• Skipping the contract clause and hoping the timer alone creates legal approval.
• Deadlines too short for the asset type — invites pushback and weakens your position.
• Unclear scope — approving "the campaign" when only one banner was linked.
• Chasing informal OKs in parallel with Credently; pick one system of record per deliverable.
• Ignoring revision requests because they came late; if submitted in time through the product, honor the process.
• Assuming auto-approval without checking that tacit consent applies to that request and agreement.
• Overclaiming legal effect to clients; say Credently documents the process — your lawyer assesses enforceability.

Checklist before you send

Use this before every tacit-consent request goes live:

• Contract or SOW includes a tacit-consent / approval-by-silence clause reviewed for your jurisdiction.
• Client contact email on the request matches the address in the agreement.
• Deliverable links or files match exactly what you describe in the title and description.
• Deadline length is reasonable for the work and any internal client review steps.
• Email message states the deadline, how to request revision, and what happens if they stay silent.
• Stakeholders know informal chat messages do not replace a verified revision in Credently.
• You know where to find the certificate and audit trail after the decision (or auto-approval).

Common questions

Does my client need a Credently login? No. They use the secure link and verify via one-time email. You manage requests from your account.

Can they reject the work? There is no reject button. They approve or request revision in writing before the deadline. Silence may become auto-approval only when tacit consent applies.

What if they say they never got the email? Credently logs send and view events where available. That supports your internal record; whether it satisfies your contract is for you and counsel to judge. See our FAQ.

Is the certificate legal proof? It is a structured record of what happened in Credently — timestamps, outcome, audit events, and verification aids. It is not a guarantee of legal enforceability or a substitute for legal advice.

Where do I get clause language? Start at Resources → Sample clause, then have your lawyer adapt it.

What does it cost? See pricing for plans and request credits. You can sign up and test the flow on your next deliverable.

---

Legal information: This article explains how tacit consent works in client approval workflows and how Credently documents them. It is general information, not legal advice. Laws vary by country and contract type. Credently does not guarantee that any clause, deadline, or certificate will be enforceable in your jurisdiction. Consult qualified counsel before relying on tacit consent for high-value or regulated work.