03 Oct, 2026
Last updated: October 2026
Imagine a recruiter opens your portfolio.
The work looks excellent. The writing is sharp. The designs are polished. The case study is unusually detailed.
Then they ask one question:
“How much of this did you actually do?”
That question is becoming harder to avoid.
AI can now help with research, writing, design exploration, coding, analysis, presentations, and dozens of other parts of professional work. The problem is not using AI. The problem starts when your portfolio makes AI-assisted work look entirely human-made.
In 2026, showing how you work is becoming just as important as showing what you made. Google itself recommends giving readers context about how AI or automation was used when that information would reasonably be expected.
I’m Riten, founder of Fueler, a skills-first portfolio platform building the career infrastructure for 100 million creative professionals. Fueler connects talented individuals with companies through assignments, portfolios, and projects, not just resumes or CVs. Think of it as Dribbble/Behance for work samples combined with AngelList for hiring infrastructure.
So let’s get into the part most portfolio guides skip: how to disclose AI use without making your work look less valuable, how to explain your contribution, what recruiters actually need to see, and why hiding AI assistance can create a bigger credibility problem than using AI in the first place.
AI-assisted work is professional work where AI contributed somewhere in the process, but you remained responsible for the direction, decisions, quality, editing, execution, or final result.
That could mean using AI to brainstorm ideas, organize research, create a first draft, explore visual directions, write code, analyze information, or find alternatives.
The level of AI involvement matters.
AI-assisted does not mean AI-created: Asking AI for ten headline ideas and choosing one after rewriting it is very different from publishing an AI-generated article without meaningful editing. Your portfolio should make this difference clear rather than placing both activities under one vague “used AI” label.
Your contribution is the important part: Recruiters do not need a dramatic explanation of every prompt you entered. They need to understand what you owned. Explain the decisions you made, the problems you solved, the changes you introduced, and what you personally delivered.
AI involvement can happen at different stages: AI might have helped with research, ideation, drafting, production, testing, or refinement. Mentioning the stage is often more useful than simply saying “AI was used.”
AI tools do not replace professional responsibility: LinkedIn’s current guidance says people remain responsible for content created with AI assistance and recommends reviewing, editing, and approving it before publishing.
Think in terms of contribution, not guilt: There is nothing inherently dishonest about using AI at work. The misleading part is presenting a substantially AI-generated result as if you personally produced every part of it without assistance.
Yes, when AI played a meaningful role and someone viewing the project could reasonably wonder how it was created.
The disclosure does not need to dominate your case study. One clear sentence can often provide enough context. Google specifically recommends explaining how automation or AI was used when that context would help readers understand the work.
A good disclosure answers three simple questions: Where did AI help? What did you do? Who made the final decisions?
Keep the disclosure specific: “AI was used for early ideation and research organization; I developed the final strategy, messaging, and campaign structure” tells readers much more than “Made with AI.” Specificity makes your contribution easier to understand.
Disclose substantial assistance: If AI generated most of the first draft, created major visual concepts, wrote significant portions of code, or transformed large amounts of material, say so. Hiding substantial assistance creates a misleading impression about your process.
Do not over-disclose minor assistance: You do not need a warning label because AI corrected a spelling mistake. If AI played a small supporting role, mentioning it may add unnecessary noise. Focus disclosure on assistance that materially influenced the work.
Put the disclosure near the project: Do not bury important information on an “About Me” page. Add a short AI note inside the relevant case study, where someone can understand the context while evaluating the work.
Treat transparency as part of the case study: The strongest portfolio projects explain the problem, your process, your decisions, the final outcome, and the role of AI. That creates a much clearer picture of your actual professional ability.
You do not need complicated language.
The best AI disclosure is short, factual, and focused on your contribution. It should sound like a normal part of documenting your work, not a legal disclaimer.
Here are practical formats you can adapt depending on the project.
For writing projects: “I used AI during the research and outlining stage to explore angles and organize ideas. I wrote, edited, fact-checked, and finalized the article.” This makes your role clear without pretending AI was absent from the workflow.
For design projects: “AI was used to explore early visual directions. I selected the final concept, rebuilt the composition, refined the visual system, and prepared the final assets.” This separates exploration from the professional design decisions you owned.
For coding projects: “AI assisted with code exploration and debugging. I designed the implementation, reviewed the generated code, tested the application, and made the final changes.” This is much stronger than simply claiming that AI “helped with coding.”
For marketing projects: “AI supported research synthesis and initial content ideas. I developed the campaign strategy, audience positioning, content plan, and final messaging.” The disclosure shows that AI accelerated parts of the workflow without claiming responsibility for your strategic thinking.
For heavily AI-generated work: “This project was created primarily with generative AI, with my contribution focused on concept development, prompt direction, selection, editing, and final presentation.” If the AI contribution was substantial, being direct is more credible than trying to make the work appear fully manual.
This is where many portfolios fail.
They show the finished image, article, website, or campaign but almost nothing about how the person arrived there. When AI is involved, that missing process becomes even more important.
Your portfolio should give evidence of your thinking.
Show the original problem: Explain what the client, company, audience, or project actually needed. A strong problem statement immediately gives context to your decisions and prevents the portfolio piece from becoming another isolated piece of polished work.
Show important decisions: Explain why you selected one direction instead of another. If AI produced several options, showing how you evaluated them demonstrates taste, judgment, and problem-solving. Those skills are difficult to understand from a final deliverable alone.
Show meaningful iterations: You do not need to publish every failed attempt. Show one or two important changes and explain what you learned. Before-and-after comparisons can demonstrate how your thinking improved the original AI-assisted output.
Show what you changed: If AI created a rough draft, explain what you rewrote. If AI generated code, explain what you modified. If AI produced images, explain what you edited. Specific changes provide tangible evidence of your contribution.
Show the outcome: Connect the work to something measurable when possible. That could be conversions, engagement, reduced production time, improved usability, successful delivery, client feedback, or another relevant result. A portfolio becomes stronger when it shows consequences, not just aesthetics.
The easiest way to create trust is to show evidence that is difficult to fake with a polished final file.
You do not have to expose private client information or publish every working document. Instead, select a few pieces of evidence that reveal how the project developed.
Include process screenshots selectively: A research board, wireframe, content structure, code iteration, campaign plan, or design exploration can show how the final work developed. Choose evidence that supports your story rather than filling the portfolio with random screenshots.
Explain your decisions in plain English: Instead of writing “I leveraged an AI-assisted iterative framework,” say what actually happened. For example: “The first version felt too generic, so I changed the audience, simplified the message, and rewrote the opening.” Clear explanations feel more believable.
Keep useful drafts: You do not need to publish every draft, but keeping them can help you explain your process during interviews, client calls, or portfolio reviews. They also make it easier to reconstruct a project months later.
Document results while they are fresh: Record the objective, your role, major decisions, tools used, and final outcome immediately after completing a project. This turns scattered project memories into usable portfolio material later.
Make your proof of work match your claim: If you say you are a strategist, show strategic decisions. If you say you are a designer, show design thinking. If you say you are a developer, show technical decisions. AI disclosure becomes much easier when the portfolio already proves your expertise.
There are two extremes to avoid.
The first is pretending AI did not exist. The second is making AI the main character of every project.
Your portfolio is supposed to demonstrate your professional ability. AI is part of the process, not the entire story.
Do not claim fully manual work when it was not: Saying “I created everything from scratch” when AI generated substantial parts of the work creates an unnecessary credibility risk. A recruiter may forgive AI assistance more easily than misleading representation.
Do not write “AI did the boring parts”: That phrase can accidentally make your own role sound smaller. Explain the actual workflow instead. Show which parts were automated and which parts required your judgment, expertise, and responsibility.
Do not dump prompts into every case study: A portfolio is not a prompt library. Prompts can be useful when they demonstrate a meaningful creative or technical process, but they should support the project story rather than replace it.
Do not hide weak work behind AI language: “AI-assisted” does not make an average result impressive. The final work still needs to solve a real problem, communicate clearly, and demonstrate relevant skill.
Do not make unverifiable claims: Avoid statements such as “AI increased productivity by 10x” unless you actually measured it. Your portfolio becomes more credible when it sticks to evidence you can explain and defend.
The rise of AI does not make portfolios useless. In many cases, it makes a detailed portfolio more useful because the final output alone tells recruiters less than it used to.
If AI can help many candidates produce a polished result, recruiters have another reason to look at how the result was produced.
Judgment becomes easier to notice: When several people can generate similar outputs, the person who can identify the right problem, reject weak options, and make good decisions becomes more valuable. Your portfolio should make those decisions visible.
Process becomes part of your evidence: A short explanation of your research, iterations, testing, and final choices can reveal more about your skill than another polished mockup. This is particularly useful when AI contributed to production.
Taste becomes more important: AI can generate possibilities quickly. It cannot remove the need to decide which possibility is actually appropriate for a particular audience, brand, product, or business problem. Show your selection process.
AI literacy becomes a practical skill: Knowing when to use AI, when not to use it, and how to check its output is increasingly part of modern professional work. Your portfolio can demonstrate that judgment without turning into a list of AI tools.
Results still matter: A beautiful AI-assisted project with no clear purpose is weaker evidence than a simple project that solved a real problem. Hiring teams ultimately need to understand what you can accomplish, not just what you can generate.
You do not need a separate “AI Projects” section unless AI itself is part of the skill you are selling.
In most cases, AI-assisted projects should sit naturally alongside your other work. The difference is that your case study should make the workflow transparent.
A simple structure can make this much easier.
Start with the project: State what you were asked to solve, who it was for, and what you delivered. Do not begin with the AI. The problem should remain the centre of the case study.
Explain your role: Clearly state whether you were responsible for strategy, writing, design, development, research, editing, analysis, or another part of the project. This gives readers a baseline for judging your contribution.
Add an AI involvement note: Use one or two sentences to explain where AI entered the process. Mention whether it supported research, ideation, drafting, production, testing, or another stage.
Show your decisions: Highlight the moments where you made choices, rejected outputs, changed direction, or improved the result. This is where your expertise becomes visible.
Finish with the outcome: Explain what happened after the work was delivered. If you have a measurable result, include it. If you do not, explain the practical outcome honestly rather than inventing a number.
Usually, hiding meaningful AI assistance creates a bigger problem than disclosing it.
The issue is not that someone used AI. The issue is whether the portfolio creates a false impression about who did the work and how it was produced.
That distinction is becoming more important as AI-generated and AI-edited content becomes easier to identify and document.
Transparency protects your credibility: If someone discovers later that substantial AI assistance was hidden, they may question other claims in your portfolio. A small disclosure can prevent a much larger trust problem.
Your portfolio should survive questions: Imagine being asked, “Walk me through how you created this.” If you can comfortably explain the workflow, decisions, edits, and AI involvement, the project is much easier to defend.
Hiding AI can make interviews harder: If your portfolio claims a level of manual expertise that your process does not support, technical or practical follow-up questions can expose the gap quickly. Honest positioning keeps your portfolio aligned with what you can actually demonstrate.
AI use is becoming part of normal workflows: LinkedIn currently recommends disclosure when someone has relied heavily on AI and the use is not obvious from context. The emphasis is on authenticity, review, and responsibility rather than pretending AI does not exist.
The strongest position is neither fear nor hype: You do not need to apologize for using AI, and you should not exaggerate what it can do. Treat it like part of your working process and be precise about the value you personally added.
If you are unsure what to write, use this four-part framework:
AI used → Purpose → Human contribution → Final responsibility.
It gives recruiters the information they actually need without turning your portfolio into an explanation of technology.
AI used: State that AI assisted the project when its involvement was meaningful. You can name the category of AI assistance without listing every tool, model, or version unless that information is relevant to the project.
Purpose: Explain what AI helped you accomplish. Examples include exploring ideas, organizing research, creating an initial draft, testing alternatives, debugging, or accelerating repetitive production work.
Human contribution: Explain what you personally handled. Mention strategy, editing, research, creative direction, technical implementation, quality control, testing, or other substantial responsibilities.
Final responsibility: Make it clear that you reviewed and approved the final work. This matters because AI output can contain errors, weak assumptions, copyright concerns, or unsuitable recommendations.
Keep it proportional: A two-line disclosure is enough for a project where AI played a supporting role. A project created largely through generative AI deserves a more detailed explanation. The amount of disclosure should match the amount of AI involvement.
AI makes finished outputs easier to produce, which makes proof of work more important, not less. Your portfolio should show how you think, make decisions, solve problems, and improve an initial idea. Documenting that process gives recruiters evidence they cannot get from a resume alone. Platforms such as Fueler can help organize those projects into a portfolio that shows both the outcome and the work behind it.
You do not need to hide AI from your portfolio.
You need to make your role impossible to misunderstand.
Show the problem. Show your decisions. Explain where AI helped. Show what you changed. Then show the result.
The future of portfolio building is unlikely to be about proving that you never used AI. It will be about proving that you know how to use it without handing over your judgment.
Yes, when AI played a meaningful role in creating or modifying the work. Keep the disclosure short and specific. Explain what AI helped with and what you personally handled. Minor assistance, such as basic proofreading, usually does not need a prominent disclosure.
Focus on your contribution. Explain the original problem, your decisions, the parts AI supported, what you changed, and the final outcome. Showing your process makes it easier for recruiters to understand your actual skills rather than judging the project only by its final appearance.
Yes, but you should represent it accurately. If AI created most of the work, say so and explain your role in concept development, direction, selection, editing, or presentation. Do not present primarily AI-generated work as entirely manual work you created yourself.
Use a simple structure: explain where AI was used, what it helped accomplish, what you personally contributed, and who made the final decisions. For example: “AI supported early ideation. I developed the final concept, edited the output, and prepared the finished work.”
Not automatically. The value depends on the problem you solved, your decisions, the quality of execution, and the outcome. AI can speed up parts of professional work, but it does not remove the need for judgment, creativity, expertise, quality control, or accountability.
Fueler helps professionals showcase proof of work through projects, assignments, case studies, and achievements.
Thousands of professionals use Fueler to create their digital portfolio
Thousands of projects are published on Fueler. Check here
Startups and Companies hire through proof of work on Fueler
Used by freelancers, creators, marketers, video editors, writers, designers, and product managers
Our mission is to help the next 100 million professionals build a verified professional identity through proof of work
You've read the article. Now turn your skills into proof of work and unlock more opportunities.
Create a clean portfolio with projects, assignments, resumes, and AI stack details that companies actually want to see.
Create your Fueler portfolio →Stand out by solving real tasks from companies hiring on Fueler.
Explore assignments →Make your work public and let recruiters discover your skills through actual projects instead of keywords.
Get discovered →
Trusted by 162100+ Generalists. Try it now, free to use
Start making more money