Client Consent for Your Portfolio: A Practical Guide

Client consent for a portfolio is written permission from the party that owns or controls a project to let you display, describe, or reference that work in your own professional materials. Obtain it before the contract is signed whenever possible, record it in a document that names the work, the channels, and the materials, and keep a dated copy. Without it, work you created may still be work you are not entitled to show.

This guide covers the legal baseline in the United States, the right moment to ask, the clauses a consent form needs, the handling of confidential and personal material, and the options when a client declines or later withdraws permission.

TL;DR

• Under US copyright law, a commissioning party can own work you produced, so authorship alone does not give you portfolio rights; permission has to be explicit.
• Ask at contract signing if you can, and otherwise at delivery, in writing, with a narrow and specific request.
• A usable consent record names the work and dates, each channel (site, social, print, interactive profile), the exact materials, and whether the client’s name and logo may appear.
• Where material is confidential, anonymize it, abstract it, or show outcomes rather than artifacts.
• If permission is refused or revoked, treat the answer as binding, and keep the evidence of your role in a form you can share privately.

Table of Contents

• Why portfolio consent is a legal question, not a courtesy
• When to ask for permission
• What a portfolio consent form should cover
• How to make the request easy to approve
• Protecting confidential, personal, and proprietary material
• Testimonials and results claims
• What to do when a client refuses or withdraws permission
• Perspective: consent as part of the evidence chain
• Building the consent record into an interactive profile
• A short checklist before any project goes public
• FAQ
• Sources

Why portfolio consent is a legal question, not a courtesy

Most professionals assume that because they made something, they may show it. The law is less generous. The US Copyright Office explains that for a work made for hire, the hiring or commissioning party is the initial copyright owner unless the parties have signed a written agreement to the contrary. Its general guidance on copyright adds that the default rule for using a protected work is to seek permission from the copyright owner. Copyright owners may authorize others to exercise their exclusive rights, which is precisely what a portfolio clause does.

In contract practice this permission is called a portfolio right: a contractual permission defining whether and how a creator may display, share, or reference client work in their own marketing. The same source notes that without explicit portfolio rights, a creator may be legally restricted from sharing work even though they made it. Employees, freelancers, agency staff, and consultants all face a version of this problem, with differing degrees of exposure depending on what their employment or service agreement says.

The consequence is practical. A portfolio is a set of representations about your work. Each item in it rests on two separate questions: is it true, and are you permitted to show it? Clients and recruiters increasingly ask both.

When to ask for permission

Timing changes the odds of approval and the quality of the paper trail.

At contract signing

The strongest position is upfront. TechRepublic’s guidance states that the best way to ensure you can include work in a portfolio is to obtain permission when you get the contract. At that point the client has no completed deliverable to protect and no reason to treat the request as a favor, so it reads as a routine term. A short portfolio clause costs almost nothing to negotiate then, and a great deal to recover afterward.

At project close

If the contract is silent, the next best moment is delivery. One practitioner guide recommends asking at project closing or right after successful delivery, when client satisfaction is highest. The client has seen the result, trusts you, and can evaluate precisely what you propose to show. Attach the proposed materials, since a request tied to a concrete artifact is easier to approve than an abstract one.

Later, in writing

Permission can still be obtained after the engagement ends, but the client has less incentive to respond. TechRepublic’s guidance still recommends doing it in writing and identifying the work dates, the portfolio format, and the specific materials. Never rely on a conversation or a passing “sure, that’s fine” in a chat thread as your only record.

What a portfolio consent form should cover

A consent form does not need to be long. It needs to be unambiguous. Drawing on the TechRepublic checklist and on contract guidance from portfolio-clause specialists, a sound permission record contains the following elements.

1. Identification of the work and dates. Name the project, the engagement period, and your role.
2. Format and channels. Matchstick Legal advises listing each intended channel instead of relying on the vague phrase “portfolio use”: websites, digital media, social channels, print samples, competitions, festivals, shows, and office displays.
3. Exact materials. Specify which deliverables, screenshots, metrics, documents, or recordings may be shown.
4. Name and logo. State whether the client’s name and logo may be used, or whether the work must be described anonymously.
5. Compensation. State whether the client receives any, which is usually none.
6. Public-release condition. Say whether the work must already be publicly released before you may display it.
7. Accuracy of your role. The same source recommends addressing whether your role must be described accurately, which protects both parties from inflated claims.
8. Retention. The form should say that portfolio materials remain in your possession.
9. Signature and copy. Per TechRepublic, the authorized signer should sign and date the form, and the client should receive a copy.

The phrase “authorized signer” matters. A project manager who loved your work may not have authority to release the company’s materials. Ask who can sign on behalf of the organization and address the form to that person.

When people appear in the work

Identifiable individuals add a second layer. A U.S.-oriented model-release template from Lightfolio lists the terms usually needed: permitted media and purposes, geographic scope, duration, editing rights, compensation, release of privacy, publicity, and defamation claims, age, signatures, and dates, with a parent or guardian signing for a minor. Photography, video case studies, user research recordings, and testimonial screenshots all fall into this category. Client consent does not automatically cover the consent of the people shown inside the client’s materials.

A compact comparison of consent levels

How to make the request easy to approve

Approval is a function of effort and risk on the client’s side. Reduce both.

• Be narrow. A specific, narrow request, such as anonymized work or one named tier of permission, is easier for a client to approve than an open-ended ask.
• Show the exact material. Send the screenshot, paragraph, or chart you intend to publish. TechRepublic recommends showing the material where you can.
• Offer options. Provide a full version and an anonymized version and let the client select.
• Offer a review window. Letting the client approve final wording removes most of the perceived downside.
• Attach a one-page form. Make signing a two-minute task, and send them a copy.

A sample request might read: “We completed the platform migration between March and August. I’d like to show two dashboard screenshots with figures redacted and a description of my role on my professional profile and personal site. May I send the exact images for your approval?” It is dated, scoped, and limited to named materials, which are the three properties an approver looks for.

Protecting confidential, personal, and proprietary material

Consent addresses ownership and permission. Confidentiality is a separate obligation, and a client can approve the display of a project while an NDA still restricts particular details.

TechRepublic’s guidance is to review confidentiality clauses, use nonconfidential or nonproprietary segments, remove company names and identifying information, consider client approval, and keep materials in your own possession. For programming work, it suggests considering a demonstration rather than showing uncompiled code.

The stakes are higher than embarrassment. The USPTO notes that trade secrets derive value from not being publicly known and must be subject to reasonable efforts to preserve confidentiality, and that secrecy can be lost through disclosure by the owner or someone the owner authorized. A portfolio entry that exposes a client’s process may therefore damage the client’s legal position, not merely their comfort. A practical principle from freelancer guidance on NDA-protected work is to honor the agreement while looking for ways to showcase the work anyway. Sectors with strict secrecy requirements show how far this can go; an overview of defence R&D partnerships in Europe illustrates how promotion and nondisclosure obligations must be balanced when the work itself cannot be displayed.

Techniques that preserve credibility without exposing detail

• Abstract the problem. Describe the category of challenge, not the client’s internal system.
• Convert absolute figures to ratios. A 22 percent reduction in cycle time reveals less than the underlying volumes.
• Substitute a demonstration for source artifacts. Show behavior, not code or files.
• Separate the claim from the evidence. Publish the claim and release the supporting document only to verified viewers on request.

That last approach is the gap that static resumes and public portfolios leave open. Alloquy’s guidance on showing work without compromising privacy or credibility works through it in more depth, and its checklist for secure portfolio sharing before sending work to recruiters covers the final review before a profile goes live.

Testimonials and results claims

Client consent also governs quotes and outcome figures. The FTC’s business guidance states that testimonials and endorsements must reflect typical consumer experiences unless the ad clearly states otherwise, and that claims must be substantiated. Applied to a portfolio, a quoted client praising your results should be approved by the quoted person, and a headline metric should trace to a document you can produce. An unsupported figure is a liability whether or not the client consented to the display.

What to do when a client refuses or withdraws permission

A refusal is not a negotiating position when the client owns the copyright. As Freelancers Union explains, if the client holds the copyright and forbids use, you have no choice, and displaying the work anyway exposes you to a lawsuit. Anything the client does grant afterward is a courtesy. The same page suggests several fallback requests.

1. Ask for a delayed release. Propose that the work may appear after a set number of months or years.
2. Ask for private showing. Request permission to show the work to a particular prospective client in a non-competitive field, without publishing it.
3. Ask for an anonymized version. Offer to remove names, logos, and identifying figures.
4. Ask for a reference instead. Agree on a short description of your role the client will confirm if contacted.
5. Fix the next contract. If the clause reverts every right to the client, request a narrow portfolio exception before signing.

If permission is withdrawn after publication, remove the material promptly, confirm the removal in writing, and check every place it may have been copied: your site, social profiles, PDFs sent to recruiters, and any profile that syndicates content. A court may later weigh whether you acted in good faith, and a fast, documented response is the best evidence. Review your agreement as well, because some contracts address revocation and some are silent. For questions about your specific contract, an attorney who handles intellectual property or employment agreements in your state can read the clause in context.

In every refusal scenario, keep what you can legitimately retain: your own notes about your role, non-confidential outcomes, and contacts who may serve as references. Those carry forward into interviews even when the artifacts cannot.

Perspective: consent as part of the evidence chain

We approach consent from the standpoint of how a career claim is verified. A portfolio entry is persuasive only when a reader can trace it to a source, and a source is usable only when you are entitled to expose it. Those two requirements pull against each other, and most portfolios resolve the tension by choosing vagueness: polished summaries with nothing behind them.

Our view is that consent should be recorded as metadata attached to the evidence, not as a footnote in an email. When you link documents to an achievement, each document should carry its own status: public, shareable with the client’s name removed, or private. A recruiter asking a question should receive an answer grounded in what you are permitted to disclose, and nothing beyond it. That discipline protects the client, protects you, and makes the answers more trustworthy because the boundary is explicit.

We also think professionals underestimate how much an unambiguous consent record helps in interviews. Saying “I have written approval to discuss this project and can show the redacted outcome data” signals judgment, which is the quality hiring managers are trying to assess.

— Alloquy Team

Building the consent record into an interactive profile

The consent form is only useful if you can find it and act on it. Keep one folder per engagement containing the contract, the signed permission, the approved materials, and a note of any restrictions. Review the folder before each portfolio update, since an entry added last year may have been approved only for a limited period or channel.

Alloquy lets you link Google Drive documents or add evidence manually to a public profile, where an AI assistant answers recruiter questions using the material you attached. Because the assistant draws on your linked evidence, you control the boundary: attach only approved documents, and the answers stay inside that boundary. You can create a free profile to test this with a single approved project, or see the plans on our pricing page for expanded evidence storage and generation limits.

Before publishing, read our notes on chatbot privacy checks before you publish, and use the structure in the portfolio case study guide to present approved work as outcome-led stories.

A short checklist before any project goes public

• Is there written permission from someone with authority to sign?
• Does it name the work, dates, materials, and each channel?
• Are client names, logos, and metrics covered, or removed?
• Have you checked any NDA and confidentiality clause separately?
• Do identifiable people in the work have releases, and is a guardian’s signature on file for any minor?
• Can every outcome claim be traced to a document you may show?
• Does the client have a copy, and do you know how to remove the work if asked?

FAQ

Do I need client consent to put my own work in my portfolio?

Often, yes. If the work was made for hire, the commissioning party is the initial copyright owner unless a written agreement says otherwise, so your right to display it depends on the contract or on the client’s permission. Read the intellectual property and confidentiality clauses first, and ask in writing if they are silent.

Is an email enough as client consent?

A clear, specific email from someone with authority can serve as written permission, and it is far better than a verbal yes. It is stronger if it names the work, dates, materials, and channels, and if you keep a dated copy. A signed one-page release is cleaner for high-value or sensitive projects.

Can I show work covered by an NDA?

Not the protected details, unless the client agrees. You can usually show anonymized, abstracted, or outcome-level descriptions that contain no confidential information, and you can ask the client to approve a version. When in doubt, show a demonstration or discuss it privately in interviews.

What if a client approved my portfolio use and later changes their mind?

Remove the material promptly, confirm in writing, and check every place it was published or sent. Whether a contract allows revocation depends on its wording, so have an attorney review it if the dispute is significant.

Sources

• Circular 30: Works Made For Hire, US Copyright Office
• Circular 1: Copyright Basics, US Copyright Office
• What Does Portfolio Rights Mean?
• Including clients’ projects in your portfolio, TechRepublic
• Steps to secure client permission to share a case
• Understanding and Negotiating Your Portfolio Clause
• Free Model Release Form Template, Lightfolio
• Getting permission to show AI work publicly
• USPTO intellectual property basics
• Can you show NDA protected work in your portfolio?
• FTC: Advertising and Marketing on the Internet, Rules of the Road
• What if a client forbids you from including something in your portfolio?
• Defence R&D Partnerships in Europe

Recommended

• Portfolio Chatbot Privacy: What to Check Before You Publish
• Portfolio Mistakes Recruiters Catch: Fix Clutter, Prove Impact
• Custom Portfolio Sections That Make Recruiters Notice
• Portfolio Evidence Checklist: 12 Checks Before You Publish