What a business analyst
portfolio should include.
A business analyst portfolio should lead with the artifacts that prove you turn ambiguity into a clear specification: requirements documents, user stories with acceptance criteria, as-is and to-be process maps, and stakeholder analysis. Show two or three sanitised case summaries that state the problem, the analysis you ran, the recommendation, and the measured outcome. It must never contain a confidential requirements document, real production data, an unredacted query against a live system, or a client name held under NDA. Below is the full list of what to put in, the terms a BA recruiter searches, and which of the Portfolio designs suit an artifacts-first CV.
The sections a BA portfolio needs.
A business analyst is hired on evidence of clear thinking, not on visuals, so the portfolio is organised around artifacts and outcomes. Work through these in order, and read the flagged block twice before you publish anything.
Requirements artifacts
The documents that show how you capture and structure a need: a business requirements document, functional requirements, user stories with acceptance criteria, and a use case or two. These are the core of the job, so lead with sanitised samples that show your format and your precision.
Process maps and modelling
As-is and to-be process flows, BPMN diagrams, and swimlane diagrams that show how work moves across roles. A clean before-and-after map is the fastest way to prove you can see a whole process and redesign it, so include a thumbnail or two with the sensitive detail removed.
Stakeholder and elicitation work
Show that you manage people, not just documents: a stakeholder analysis, a RACI matrix, and a short note on how you elicit requirements through interviews and workshops. Hiring managers want a BA who can run a room and reconcile conflicting needs, not only write them up afterwards.
Data and query skills
State your SQL level and the BI and reporting tools you work in, such as Tableau, Power BI, or Looker. If you can pull your own data and build a report, say so plainly and show a sanitised dashboard, because a BA who does not wait on an analyst moves faster and is worth more.
Tools and certifications
List the tools you actually use day to day, Jira, Confluence, Visio, Lucidchart, and Excel, and any certification that carries weight: IIBA CBAP, CCBA, or ECBA, PMI-PBA, and an Agile or Scrum credential where it is relevant. Put the issuing body next to each certification.
Analysis case summaries
Two to four short case blocks, each with the problem, the analysis you performed, the recommendation you made, and the measured outcome in aggregate. Describe the domain and industry knowledge you brought, and show how you translated a business need into a clear specification an engineering team could build.
Never include: confidential requirements or real data
No confidential requirements documents, no real production data, no unredacted query run against a live system, no client or employer name held under NDA, and no internal process detail that is confidential. A leak of this on a public page can end an engagement and expose you to a claim.
Anonymise everything. Recreate a process map with generic role names, blur or replace figures, and describe outcomes as a percentage change rather than a raw number tied to a company. Show sanitised or redacted artifacts only, and when a piece cannot be safely shown, describe it instead.
Terms a BA recruiter searches.
A recruiter filters an applicant tracking system for specific competencies. If these are true of you, use the exact words, because the system indexes the words you wrote, not the ones you meant.
Paste your resume into the free ATS score checker with a real business analyst posting to see which of these terms the posting uses and your resume is missing.
Which designs suit an artifacts-first CV.
Business analysis is a clarity-and-artifacts field, so the design should be structured and legible, with room for a few sanitised case blocks. Of the 60 Portfolio designs and 48 resume layouts, these are the shapes that fit.
Pick a quiet design that leads with skills and certifications and reads top to bottom. Leave room for two to four artifact blocks, a process map thumbnail, a requirements sample, so a reviewer can see your work without hunting for it.
Of the 48 resume layouts, choose a single-column one over a two-column design. Multi-column resumes can serialise into a scrambled reading order when a company system parses them, which is the last thing you want on a screened BA application.
Order the page so skills, tools, and certifications come first, then the sanitised case blocks that prove them. Use the block page builder to lay out each artifact case as its own tidy unit rather than cramming them into one wall of text.
The image-led gallery designs are built for visual portfolios and push text below the fold. They bury the specifications and outcomes a BA reviewer reads for, so skip them for this field.
Who a BA portfolio is not for.
A portfolio helps some business analysts and is invisible to others. Read this before you spend an evening building one, because for a large share of BA roles a clean, parsable resume matters far more.
Worth building if you
- +Are an independent or contract BA who wins work directly and wants one link that shows your artifacts, tools, and certifications at a glance.
- +Are moving toward product owner, product manager, or systems analysis and want to show a body of analysis work.
- +Are changing industries and need to prove transferable analysis skill when your job titles do not tell the story.
- +Have sanitised artifacts and a certification worth presenting, or do consulting work where a BA portfolio wins trust.
Skip it, for now, if you
- −Apply only through a company internal Workday or Greenhouse portal, where an external site is rarely opened at screening.
- −Are a contract BA placed by an agency that submits a standardised profile on your behalf. Fix that profile first.
- −Would be tempted to expose any confidential requirements or real data. If in doubt, do not publish, an ATS-clean resume is safer.
- −Are on a deadline. Spend the time making your resume machine-readable, then build the site after.
Questions BAs ask.
Straight answers on confidentiality, artifacts, and whether the effort is worth it.
Can I show real requirements documents in my portfolio?
Not the real ones. Anything produced for an employer or client is usually confidential and often covered by an NDA, so publishing it can breach your contract. Recreate the artifact instead: build a sanitised sample with generic role names, invented figures, and no company detail, that shows your format and rigour without exposing anyone. When a piece cannot be safely rebuilt, describe what you did rather than showing the document.
Do business analysts need a portfolio website?
Often not for a role filled through a large company's internal system, where a clean, parsable resume does the work. A portfolio earns its keep for independent and contract BAs who win work directly, for anyone moving toward product or systems analysis, and for a career changer proving transferable analysis skill. If you have sanitised artifacts and a certification worth presenting, a single link makes your case faster than a resume can.
How do I present a process map without exposing confidential data?
Redraw it. Replace real system and department names with generic labels, strip any figures tied to the business, and keep only the shape of the flow: the steps, the decision points, and the hand-offs between roles. A to-be map with anonymised swimlanes proves you can model a process without revealing a single confidential detail. Keep the original private and show only the sanitised version.
Which BA certifications should I list first?
Lead with the IIBA credential that matches your experience level, CBAP for a senior analyst, CCBA for a mid-level one, and ECBA for someone earlier in their career, because a BA recruiter recognises these first. Add PMI-PBA if you hold it, and an Agile or Scrum certification where the role is delivery-focused. Put the issuing body next to each one so a reviewer can confirm it.
Should I show SQL or BI work in a BA portfolio?
Yes, if it is genuinely part of your work, because a BA who can pull and read their own data is more valuable than one who waits on an analyst. State your SQL level plainly and show a sanitised report or dashboard built in Tableau, Power BI, or Looker, with the underlying figures replaced. Never publish a query that runs against a real system or any extract of live data.
Where to go next.
Build the site, test your resume, or read how the paste-a-resume flow works.
Turn your BA
resume into a site.
Paste your resume and Portfolio drafts a clean, artifacts-first website in about a minute. Skills and certifications up top, room for sanitised case blocks, no confidential data anywhere, published to your own domain with TLS handled for you.