Write investment banking deal experience as transaction context + your work + the decision your work supported. Name the client or transaction value only when that information is public and your employer permits it. Otherwise, anonymize the company and use a truthful range—or omit the number.
The goal is not to make every deal sound closed or headline-worthy. It is to let a reviewer distinguish work you performed from a process you merely observed, without disclosing information you were expected to protect.
Use the SAFE disclosure test before writing
Run each fact through SAFE before it reaches the page.
| Test | Question | If the answer is no or unclear |
|---|---|---|
| S — Status | Is the transaction and the fact you want to use publicly announced? | Describe the client and process generically. |
| A — Authorization | Does your employer's policy allow you to include it? | Ask the appropriate internal reviewer or omit it. |
| F — Fact check | Can you verify the number, stage, and your contribution? | Remove the number or narrow the claim. |
| E — Exposure | Could the remaining details identify a confidential client or reveal nonpublic information when combined? | Generalize the sector, size, geography, or timing. |
Public status does not automatically make every detail public. An announced acquisition may still have confidential valuation work, bidder information, forecasts, financing assumptions, or process details behind it.
The CFA Institute Code and Standards provides useful professional context: it addresses duties to employers, material nonpublic information, and preservation of confidentiality. It is not a resume-writing rule, and it does not replace your employment agreement, firm policy, legal advice, or a supervisor's direction.
Build the bullet in four parts
Use this sentence architecture:
Transaction context + specific action + analytical object + decision or process supported
Each part answers a different reviewer question.
| Part | What it proves | Useful detail |
|---|---|---|
| Context | You understand where the work sat | M&A, refinancing, equity raise, pitch, live mandate; sector; size range if safe |
| Action | You personally did something | Built, analyzed, drafted, reconciled, researched, coordinated |
| Analytical object | The work had technical substance | DCF, trading comps, buyer list, debt schedule, operating case, diligence tracker |
| Decision supported | The output had a purpose | Valuation discussion, buyer prioritization, financing choice, management meeting, diligence response |
Do not force a result metric into every bullet. Banking work often supports a decision rather than producing a clean percentage improvement. A precise description of the model, output, and decision is more credible than an invented efficiency or impact number.
Annotated example: a confidential sell-side process
Assume an analyst supported a sell-side process that has not been announced. The analyst built trading comps, updated a buyer list, and prepared management-presentation materials.
Too vague
Worked on an M&A deal and performed valuation analysis.
This establishes neither ownership nor the purpose of the work.
Too exposed
Advised [private company name] on its confidential $425 million sale to [buyer name], building the model that set the final purchase price.
This may identify an unannounced process. It also overstates what one model—and likely one analyst—determined.
Specific without identifying the client
Supported a confidential sell-side mandate for a middle-market business-services company by updating trading-company and precedent-transaction analyses, screening 40+ strategic and financial buyers, and preparing valuation materials for management discussions.
The bullet shows transaction type, sector, analytical work, research scope, and use. It does not claim the deal closed, name a party, or attribute the final valuation to the analyst.
If “40+” came from a version-controlled buyer list you maintained, it is a supportable workload fact. If you are estimating from memory, remove it.
Announced, pending, closed, and pitch work are different
Use the label that was true when you last verified it.
| Actual stage | Accurate language | Avoid |
|---|---|---|
| Pitch | “Prepared pitch materials for…” | “Advised” or “executed” |
| Live, unannounced | “Supported a confidential…” | Client names, counterparties, exact values, outcome claims |
| Announced, pending | “Supported the announced…” | “Completed” or “closed” |
| Closed | “Supported the completed…” | Claiming sole responsibility for team outcomes |
| Paused or terminated | “Supported a strategic review” or the truthful process type | Implying completion |
“Advised on” can be reasonable at the team level, but the rest of the bullet should still identify your contribution. “Led” should be reserved for work you actually directed, not a workstream where you assembled pages under supervision.
Five before-and-after examples
1. Valuation
Before: Performed valuation for a healthcare deal.
After: Built a DCF and updated trading-company and precedent-transaction analyses for an announced healthcare-services acquisition, supporting the deal team's valuation discussion.
Why it works: it names the analytical outputs and their purpose without claiming the analyst selected the price.
2. Capital raise
Before: Helped a company raise debt.
After: Analyzed leverage, interest coverage, and maturity scenarios for a confidential refinancing, and prepared lender-comparison materials for senior-team review.
Why it works: the key credit work is visible even without an issuer name or amount.
3. Buyer research
Before: Researched potential buyers.
After: Segmented strategic and sponsor buyers by acquisition history, geographic fit, and portfolio overlap for a confidential industrials sell-side process.
Why it works: it explains the screening logic rather than treating a long list as the accomplishment.
4. Diligence
Before: Managed due diligence.
After: Maintained the diligence request tracker, reconciled open items across legal and financial workstreams, and prepared weekly status summaries for a pending transaction.
Why it works: it replaces an inflated “managed” claim with the coordination work actually performed.
5. Pitch work
Before: Worked on multiple pitches that won business.
After: Prepared market updates, buyer screens, and preliminary valuation pages for three consumer-sector pitches presented to prospective clients.
Why it works: it describes pitch experience without claiming credit for a mandate unless that attribution is known and approved.
What numbers are worth using
Use a number when it adds decision-relevant scale and you can defend it.
Good candidates include:
- a publicly disclosed transaction value;
- an approved size range for an anonymized client;
- the number of companies screened using a defined set of criteria;
- the number of operating cases or financing structures analyzed;
- the number of workstreams coordinated when the count is meaningful.
Weak candidates include hours worked, pages formatted, arbitrary percentages for “accuracy,” and revenue or valuation impact you cannot isolate. Never convert an internal forecast into a public-looking achievement.
The SEC's Regulation FD adopting release explains rules around selective disclosure by public issuers. Your resume is not a Regulation FD compliance document, and the rule does not govern every confidentiality question you will face. The useful boundary is narrower: do not treat possession of deal information as permission to publish it.
A two-bullet deal entry template
For experienced analysts and lateral candidates, two bullets can separate technical work from process responsibility.
[Public or anonymized transaction context]
- Built or updated [model / valuation / analysis], testing [key variables] to support [specific discussion or decision].
- Prepared or coordinated [materials / research / diligence workstream], using [criteria or scope] for [management, senior team, lender, or buyer process].
Do not add a separate transaction heading if it makes a confidential client identifiable. The same content can sit under the employer entry as ordinary bullets.
Final review checklist
Before sending the resume, verify that every deal bullet passes these checks:
- The stage is accurate: pitch, live, announced, closed, paused, or terminated.
- Client and counterparty names are public and permitted—or removed.
- Transaction values and ranges are verified and allowed.
- Your verb matches your actual ownership.
- The analytical output is named.
- The business purpose is clear.
- No internal forecast, bidder detail, financing term, or process fact has slipped in.
- The bullet still makes sense when challenged line by line in an interview.
Then compare the full document against the investment banking resume checklist. If the experience will also appear in your interview introduction, make sure the same stages and responsibilities remain consistent in your walk-me-through-your-resume answer.
The limitation to remember
No universal anonymization formula makes disclosure safe. A narrow sector, city, date, size range, and unusual process can identify a client even when the name is missing. When policy or permission is unclear, omit the identifying detail and keep the work itself specific.
Once the bullets pass SAFE, the useful next step is an outside check for clarity and overstatement: compare the resume review options if you want line-by-line feedback.