How much detail should a business analyst give about work covered by an NDA?
By Olive Jobs · Updated August 25, 2026 · 3 min read
Leaving program specifics off the résumé doesn't erase what a business analyst at a government agency can show, because the craft lives in the artifacts. Build each bullet from the requirements document, the process map, and the stakeholder sign-off record instead of the program behind them. Program names wait until whoever gave you the agreement clears them.
Where the useful detail actually lives
Detail splits into two kinds once work sits under an NDA: how you worked, and what the work served. The first covers elicitation sessions, drafting cycles, reconciled versions, and the route to sign-off. The second covers program names and unpublished specifics, and only the agreement you signed says where that line sits.
A business analyst can describe the shape of the work in full: who disagreed, how many drafts it took to reconcile them, and what the delivery manager needed before sign-off. That shape turns a vague request into something a team can build. It's yours to tell.
Writing the résumé line from the artifact outward
Requirements documents, process maps, and stakeholder sign-off records are the portfolio a business analyst carries, and each one supports a bullet without touching the program it served. Describe the artifact's scope, the sessions behind it, and the approvals it survived, then read your line back for anything a stranger couldn't already find.
A rebuilt bullet can read: "Ran structured elicitation across several program offices, reconciled competing requirements through successive drafts, and carried the final document to stakeholder sign-off." Each verb shows method. Nothing in the line names the mission.
At a government agency
At a public agency, the mission is usually public even when your piece of it isn't, and that inverts the NDA problem most private-sector résumés face. Much of what the organization does sits in published plans, budget documents, and program pages anyone can read, and published language sets a natural ceiling for yours.
Match your bullet's nouns to what the agency has already published about the program area, and go no further than that public text goes. Where the published trail stops, your description stops with it. Don't reach past that point until whoever administered your agreement says you can.
If you are mid-level
A few years in, the pull is to compensate for missing program names by listing every task you've ever touched. Resist it; the title covers two different jobs, requirements elicitation and data analysis, and a posting almost always means just one, so pick the artifacts that match the job it's describing.
A mid-level résumé wins on depth of artifact, not breadth of exposure, and the same restraint carries to your LinkedIn summary, which sits in public view where program stakeholders can read every word. Browse Business Analyst jobs to see which of the two the postings near you actually want.
Clearing a borderline detail before an interview
The person who handed you the NDA can say where it applies, and asking is a professional move, not a confession. Raise it with your supervisor or the office that administers the agreement before interviews start, because in a recruiter screen the question arrives out loud, with no time to redraft.
Tonight, rewrite one NDA-covered line from its artifact and read it to someone outside the organization. If they can say back what you're good at without learning what the program was, the level of detail is right; if they can name the program, cut until they can't.