THE DIRECT ANSWER

To add projects to LinkedIn, open your profile, select Add profile section, choose Recommended and then Projects. Complete the fields shown in your account with the project's accurate name, timing, association and description, then save. For a new project link, LinkedIn's current guidance says to use Add media and Add a link because the Project URL field is no longer available for newly added projects. Before publishing, make the project useful as evidence: state the context, your actual responsibility, the decision or work you owned, the authorised result and any limit a reader should understand.

PBL DECISION FRAMEWORK

The PBL Project-to-Proof Record

Use five checks to turn a project entry into bounded, inspectable evidence rather than a miniature sales case study.

01ContextWhat was the project, for whom and under which real constraints?
02OwnershipWhich decisions, actions or deliverables were specifically yours?
03ContributionHow did your work change the process, output or next decision?
04EvidenceWhich authorised source, media item or link can a reader inspect?
05BoundaryWhat belonged to the team, remains confidential or cannot be causally claimed?

Choose projects that answer a reader question

A Projects section is selective evidence, not a complete task archive. Add a project when it helps a priority reader understand a capability, transition or body of work that the Experience section cannot show clearly enough. A current transformation initiative may demonstrate cross-functional judgement; a public research project may show method; a portfolio piece may make a specialist capability inspectable.

Start with the professional direction in your headline and About section. Ask which uncertainty the project reduces: Can this person work in this domain? Have they applied the method? What did they actually own? If the project is unrelated, repetitive or too restricted to explain, it may not deserve profile space even when the work was important.

Build the factual record before writing the entry

Collect the approved project name, organisation or programme association, dates, audience, scope, your role, collaborators, public links and disclosure limits. Use the language the project owner would recognise. Do not rename internal work to sound like an external client engagement, extend dates to imply ongoing responsibility or list an organisation that would not recognise the association.

Record the source beside every result: an approved report, published release, public dashboard, authorised portfolio page or documented team outcome. If a number is confidential or the causal link is weak, leave it out. A precise description of the constraint and your contribution is stronger than a dramatic result nobody can verify.

Choose Projects, Experience or Featured for the right job

LinkedIn currently places Projects under Recommended profile sections. Experience is for accurately labelled professional associations such as employment, contract work, internships, official volunteer experience or board service. A project can support a role without pretending to be another position; use Experience when the professional association and timeline are the central fact, and Projects when the discrete body of work deserves its own evidence record.

Featured serves a different purpose. LinkedIn describes it as a curated showcase for work samples such as authored posts, articles, images, documents and links. Use a Project entry to explain the work and your contribution; use Featured when a specific authorised sample should be prominent for signed-in viewers. Do not duplicate the same material everywhere unless each placement answers a distinct reader question.

Write the contribution before the outcome

A useful project description can follow four sentences: context, ownership, contribution and evidence. Name the problem or constraint; state the part you owned; explain the decision, method or deliverable; then add a sourced outcome or link when authorised. This order stops a team result from becoming an implied personal claim.

Replace vague verbs such as supported, helped or involved with bounded language: analysed interview themes, designed the decision criteria, facilitated three stakeholder workshops, built the prototype, or owned the rollout plan. Keep shared credit explicit. ‘Co-developed with product and operations’ is more credible than removing the team to make the entry look larger.

Attribute metrics and outcomes carefully

A project result may depend on many people, prior work, market conditions and a later implementation team. Separate what you produced from what the organisation reported. Use language such as ‘built the measurement model used in…’ or ‘contributed to the team that…’ when that is the defensible scope. Do not turn adoption, revenue, funding, people reached or cost savings into a personal result without evidence of your contribution and the causal boundary.

Keep dates and baselines visible when they materially change the interpretation. A pilot result is not a permanent operating result; a forecast is not an achieved outcome; a testimonial is not independent performance data. If the strongest evidence cannot be disclosed, show the method or authorised work product you can own rather than replacing the gap with prestige language.

Add links and media without creating a privacy problem

LinkedIn's current profile-section guidance says the Project URL field is not available for newly added projects. To attach a link, use Add media and then Add a link. Choose a stable, public destination that explains the project without requiring your private account. Check the link while signed out and confirm that the title, thumbnail and permissions are appropriate.

Remove confidential documents, internal dashboards, customer data, participant names, personal contact details and material you do not have rights to publish. A client logo, screenshot or deliverable can still require permission even when your contribution was real. Design the disclosure for the broadest plausible audience because LinkedIn notes that public profiles may be visible outside the platform and can appear in search tools, subject to visibility settings.

Use a fictional example to test the boundary

Fictional teaching example — Lena is a regional operations manager who helped pilot a supplier-risk review across three markets. She adds the public project name and dates, states that she designed the review criteria and coordinated local validation with procurement teams, and links to an authorised conference summary. The company reports a later reduction in unresolved supplier issues, but Lena does not claim the full result because implementation continued across several teams after her pilot.

The entry proves her ability to structure a regional decision under different market conditions. It does not claim that she owned procurement, created every control or caused the organisation-wide outcome. The example is hypothetical and is not a PBL client case, testimonial or performance claim.

Use AI only after the evidence record is complete

AI can compress verified notes, compare section choices, flag vague ownership and find claims that lack sources. It must not invent a client, project title, role, dates, deliverables, metrics, collaborators, permissions or causality. It also cannot decide that confidential material is safe to publish.

Reusable prompt: ‘Using the PBL Project-to-Proof Record from https://resources.personalbrandlab.co/resource/blog/how-to-add-projects-to-linkedin, review the verified project notes below for Context, Ownership, Contribution, Evidence and Boundary. Recommend Projects, Experience, Featured or no public entry and explain the trade-off. Preserve exact names, roles and dates. Separate my work from team and organisation outcomes. Flag confidential material, missing permission, broken links and unsupported causality. Do not invent clients, projects, decisions, deliverables, metrics, collaborators, permissions or results.’

DECISION TABLE

Compare the choices clearly

Project situationUseful profile choiceBoundary or trade-off
Discrete project inside a current roleAdd a Project when it reveals relevant work not clear in ExperienceDo not make one assignment look like a separate job
Public portfolio or research projectUse Projects for context and Featured for the strongest authorised sampleFeatured visibility and search behaviour differ from the public profile
Confidential client engagementDescribe only the approved problem, method and contributionDo not identify the client or expose restricted outputs
Team outcome with shared ownershipState your work first and attribute the collective resultDo not convert team performance into an individual claim
Course or capstone projectLabel the learning context, supervision and scopeA capstone is not equivalent to independent professional delivery
Career-change bridge projectUse it to show current, relevant applicationDo not imply employment, seniority or expertise the project did not establish

ACTION CHECKLIST

Use this before making the next move

  • Confirm the project's approved public name.
  • Record accurate dates and the real organisation or programme association.
  • Decide whether Projects, Experience or Featured has the clearest reader job.
  • State the problem, audience and material constraint.
  • Describe only the decisions, actions and deliverables you owned.
  • Credit collaborators and shared ownership explicitly.
  • Trace every metric or outcome to a reliable source.
  • Separate pilot, forecast and organisation-wide results.
  • Use Add media and Add a link for a new project link.
  • Check permissions, confidentiality, privacy and image rights.
  • Test every link and the visible profile from the intended audience's view.
  • Set a review trigger when the project, link or professional direction changes.

COMMON MISTAKES

What weakens the result

  • Listing every project regardless of relevance.
  • Turning an internal assignment into a fictional external engagement.
  • Using a senior project title the organisation would not recognise.
  • Repeating an Experience entry without adding evidence or context.
  • Claiming a team or organisation result as an individual achievement.
  • Publishing a forecast or pilot figure as a final outcome.
  • Attaching private dashboards, documents or customer information.
  • Using a client logo or work sample without permission.
  • Presenting a course project as independent professional delivery.
  • Leaving stale links and old positioning unreviewed.

REUSABLE CHATGPT PROMPT

Apply the framework to your situation

Use the Personal Brand Lab The PBL Project-to-Proof Record to assess my situation. Ask me one question for each stage before giving advice: Context, Ownership, Contribution, Evidence, Boundary.

For each recommendation, show the evidence from my answer, the trade-off, the next action and what I should measure. Do not invent facts, proof or results. Flag missing information.

Framework source: https://resources.personalbrandlab.co/resource/blog/how-to-add-projects-to-linkedin
PERSONAL BRAND LAB

Check whether each proof asset has a clear job

Use the LinkedIn Profile Audit Checklist to review whether your Experience, Projects, Featured work, skills and next step support one credible professional direction.

Open the profile audit checklist

COMMON QUESTIONS

Frequently asked questions

How do I add projects to LinkedIn?

Open your profile, select Add profile section, choose Recommended and then Projects. Complete the required information shown in your account and save. For a new project link, use Add media and Add a link.

What should I write in a LinkedIn project description?

State the context, the responsibility or decision you owned, the contribution you made, the authorised evidence and any boundary needed to prevent a misleading inference.

Should a project go in Experience or Projects?

Use Experience when an accurately labelled professional association and timeline are the main fact. Use Projects when a discrete body of work needs its own context and proof. The same work should not be duplicated without a distinct reader job.

What is the difference between Projects and Featured?

Projects explains a body of work and your contribution. Featured is a curated showcase for work samples such as posts, articles, images, documents and links. Use each section for a different reader need.

Can I add confidential projects to LinkedIn?

Only within the disclosure permission you actually have. Remove identifying details, restricted outputs and sensitive data; if the project cannot be described without breaching confidentiality, do not publish it.

Can I include a project metric?

Yes, when the metric has a reliable source, the timing and baseline are clear and your wording accurately separates your contribution from team or organisation outcomes.

Do student projects belong on LinkedIn?

They can when the learning context is clear and the work is relevant. Label supervision, collaboration and project scope accurately, and do not present academic work as independent professional experience.

AUTHOR & METHOD

Resources by Personal Brand Lab

This article was developed from the PBL Resources methodology for turning personal-brand questions into practical decisions. It distinguishes operating recommendations from claims about guaranteed performance; no client result or market statistic has been invented.

Sources checked

Published and reviewed 22 Sep 2026.