Firm Norms and Jargon

Deal-process conversations rely on a specific, dense shorthand for where a transaction stands: 'signing' (the definitive agreement is executed, but the deal hasn't yet closed), 'closing' (the transaction actually completes, ownership transfers), 'sign-to-close' (the period between the two, during which closing conditions like regulatory approval are satisfied), 'live' (an active, in-progress deal), and 'dead' (a process that's been terminated or a bid that lost). Fluency with this vocabulary, used constantly and without explanation in internal conversation, is expected within the first weeks, new analysts absorb it quickly simply through daily exposure to how the team talks about deal status.

Getting this vocabulary right matters beyond sounding fluent: precisely knowing whether a deal is 'signed' versus 'closed,' for instance, is often directly relevant to compliance obligations (restricted list status can change at signing) and to correctly understanding what stage of a process is actually being discussed in a given conversation.

Common shorthand for participants: the 'lead' or 'lead-left' bank (the bank running point on a deal, typically listed first/leftmost on the tender or offering documents), 'co-manager' or 'co-advisor' (a secondary role on a larger deal), 'counterparty' (the other side of a negotiation), and 'the client' (used specifically, distinguishing the party the bank is actually advising from other parties in a transaction, like the buyer in a sell-side process). Precision about exactly who 'the client' is in a given conversation matters, since a banker's obligations and posture differ meaningfully depending on which side of a transaction they're actually representing.

This vocabulary also extends to internal team shorthand for seniority and roles (referring colloquially to 'the staffer,' 'the deal team,' 'coverage' versus 'product') that a new analyst picks up quickly through the internal shorthand lesson's broader patterns, but deal-vocabulary specifically is worth learning deliberately early, since it's used constantly in every deal conversation from the first day.

Terms describing a deal's outcome or trajectory: 'broken deal' (a transaction that was announced or under negotiation but ultimately didn't close), 'topping bid' (a competing offer that exceeds an existing one during an active process), 'go-shop' (a contractual period after signing during which a target can still solicit competing offers, common in some deal structures), and 'MAC' or 'material adverse change' (a clause allowing a buyer to walk away from a signed deal if the target's business deteriorates significantly before closing).

Being fluent with these outcome-related terms specifically matters for following deal news and internal discussion of both the team's own live deals and broader market activity, a new analyst who can read a deal announcement or an internal update and immediately understand exactly what stage and status is being described is operating with real, functional fluency rather than just recognizing individual words.

The core marketing documents in a sell-side process, in order of increasing detail and confidentiality: the teaser (a brief, anonymized overview sent broadly), the CIM (a detailed, named marketing document sent to NDA'd parties), and management presentation materials (used in later-stage buyer meetings), each covered in detail in their own dedicated execution lessons. Process letters (formal instructions to bidders about submission deadlines and requirements at each round) and process trackers (internal documents tracking buyer status and outreach) round out the core documents used to actually run and manage a live process.

Knowing exactly which document is which, and at which stage of a process each one is typically used, is foundational vocabulary that every other execution-focused lesson in this curriculum assumes as background knowledge.

Key legal documents: the engagement letter (governs the bank-client relationship itself), the NDA (governs confidentiality for any party receiving sensitive information), letters of intent or indications of interest (non-binding early-stage expressions of interest and proposed terms), and the definitive purchase agreement (the binding, final legal document governing the actual transaction), each covered in more depth in the deal documents execution lesson.

A new analyst doesn't need to draft or deeply understand the legal mechanics of these documents immediately, but recognizing what each one is, roughly what it governs, and where it sits in a deal's chronological sequence is basic, expected fluency for following along in team discussions and understanding what stage a live deal has reached.

Beyond client-facing and legal documents, teams constantly reference internal analytical outputs by shorthand: 'the model' (the financial model underlying a specific analysis), 'the comps page' or 'the football field' (specific valuation outputs, covered in the pitchbook lessons), and 'the deck' (used generically for whatever presentation is currently being built, whether a full pitchbook or a smaller internal discussion document).

This internal shorthand overlaps with, but is distinct from, the broader internal-shorthand lesson covering people and process terminology, document-type vocabulary specifically is worth learning early because nearly every instruction a new analyst receives ('pull together the CIM,' 'update the football field') assumes this vocabulary is already understood without explanation.

Teams use consistent shorthand for roles and hierarchy: 'the staffer' (whoever is making staffing decisions for a given team), 'MD' (managing director), 'the deal team' (everyone actively working a specific transaction), and informal references to seniority ('a first-year,' 'a senior associate') used constantly in day-to-day conversation about who's doing what and who needs to be informed of a given update.

This vocabulary is absorbed quickly through simple daily exposure, but a new analyst benefits from actively noticing and internalizing it early rather than passively waiting for it to become familiar, asking directly when an unfamiliar term comes up is a low-cost way to close gaps quickly rather than nodding along without full understanding.

Common process shorthand: 'turn' or 'turn a draft' (revise a document and send it back), 'redline' (a marked-up document showing tracked changes, typically in a legal or negotiation context), 'blackline' (a clean, finalized comparison showing all changes between two document versions), 'EOD' (end of day, a common informal deadline marker), and 'bandwidth' (used to describe an analyst's or team's current capacity to take on additional work).

This vocabulary is used constantly in the kind of rapid-fire instructions and status updates covered in the workstream-management and verbal-communication lessons, fluency here isn't just about sounding experienced, it's genuinely necessary for correctly understanding what's actually being asked in a fast, informal instruction.

Informal shorthand extends to how outcomes and situations get described colloquially: a deal or task 'blowing up' (falling apart or hitting a serious problem), someone being 'buried' (overloaded with work), a page or model that 'doesn't tie out' (contains an inconsistency, connecting directly to the error-checking discipline covered elsewhere), and 'flagging' something (proactively raising an issue, connecting to the escalation judgment covered in the professional-craft lessons).

This kind of informal shorthand varies somewhat team to team and even person to person, and picking it up naturally through genuine attentiveness in daily interactions, rather than trying to memorize an exhaustive list, is the realistic way most analysts actually become fluent within their first few months.

Beyond the general banking-wide formatting conventions covered in the pitchbook formatting lesson, every firm, and often every specific group within a firm, maintains its own template decks, color palettes, and house-style guides that new analysts are expected to learn and apply precisely, typically absorbed through a combination of formal onboarding materials and repeated correction on early work. These firm-specific conventions are rarely fully documented anywhere comprehensive; much of the real detail is learned by studying recent, well-regarded decks from the specific team.

A new analyst joining from a different firm (a lateral hire) or transferring between groups within the same firm often needs to consciously relearn these specific conventions even if they're already broadly fluent in general banking formatting standards, the general skill transfers, but the specific rules don't automatically.

Beyond formatting for presentation decks, firms also maintain specific modeling conventions: standard color-coding for inputs versus formulas versus links (the blue/black/green convention is common but not universal, some firms use different colors or additional categories), standard tab naming and organization structures, and house preferences for specific formula approaches or model layouts.

Learning these modeling-specific conventions matters just as much as presentation formatting, since a model built with unfamiliar structure or coloring conventions is genuinely harder and slower for a teammate to review and trust, consistency here isn't merely aesthetic, it directly affects how quickly and confidently others can verify and build on an analyst's work.

The fastest way to internalize firm-specific conventions is deliberate study of recent, well-regarded work from the specific team, noting exact formatting choices, structural patterns, and language conventions used in actual, approved output, combined with actively asking a staffer or more senior analyst directly when a specific convention isn't clear, rather than guessing. Most firms also provide a template library and, often, a formal style guide as onboarding resources, which are worth reviewing closely in the first weeks rather than treated as reference material to consult only when something goes wrong.

Treating this learning process as a deliberate, active effort in the first weeks, rather than something that will simply happen passively over time, meaningfully shortens the period during which formatting corrections are a recurring, visible piece of feedback.