A fourth-year associate at an Am Law 100 firm in New York stopped being honest in her informal check-ins after a single conversation went wrong.
In May, her supervising partner asked how she was doing in a casual hallway exchange. She said she was tired — it had been a stretch on a contentious matter, and she was struggling to find rhythm on a new client team. Eight months later, in her year-end review, that comment surfaced as documented concern about her “resilience” and “client adaptability.” Her bonus reflected it. The line was traceable back to the May conversation she had thought was a moment of candor, not a data point in her permanent file.
She did not raise it with HR. She simply stopped being honest in check-ins. By the following spring, she was interviewing with three competitors, none of whom would have to read about her “resilience concerns.”
This pattern is one of the most discussed problems in legal HR and on r/biglaw right now, and it is the structural failure underneath a lot of what shows up as engagement and retention data. When associates cannot tell the difference between a developmental coaching conversation and an entry in their permanent record, they default to defensive behavior. They stop being honest. They stop asking for help. The information firms most need from their associates becomes the information associates are most careful never to give them.
In November 2025, the NALP Foundation released its first comprehensive study of associate performance evaluation practices at 106 leading US law firms. One of the findings the study specifically named was a gap in data utilization — firms collect feedback but lack clear architecture for what to do with it once it is collected. The conflation of coaching and formal review is the most operationally visible form of that gap.
SRA has designed and run confidential performance review programs exclusively for US law firms since 1987. The architectural separation between coaching conversations and formal evaluation records is one of the design principles our programs are built on, because it is one of the easiest things for firms to get wrong and one of the most consequential when they do.
Two activities, two purposes, two different trust requirements
Most law firms run coaching and formal review as if they are points on a single continuum. They are not. They are two different activities with different purposes, different audiences, different documentation rules, and most importantly different trust contracts with the associate.
The trust contract row is the one most firms miss. Associates are not confused about whether their year-end evaluation will affect their compensation; they assume it will. They are confused about whether a Tuesday morning check-in will affect their compensation. When the answer turns out to be yes, the coaching system breaks. When the answer is reliably no, the coaching system works.
Why conflating the two destroys both
This is not a hypothetical concern. The conflation has predictable, repeating consequences that show up in associate behavior, evaluation quality, and retention data.
Coaching becomes unsafe and stops working. When associates cannot trust that an informal conversation will stay informal, they stop being honest. They stop volunteering struggles. They present curated versions of themselves in every interaction. The supervising partner ends up coaching a performance, not a person, and the developmental function the firm thought it was buying never actually runs.
Formal evaluations get contaminated with unreliable data. When coaching notes drift into the formal record, the record contains observations that were never meant to be evaluative — captured in moments of vulnerability, without the structured aggregation a real evaluation requires. Compensation decisions then get made on data the associate never knew was being scored, which is both unfair and (in PIPs and terminations) legally risky.
Associates over-prepare for every interaction. The associate who learned the hard way in May 2025 doesn’t just stop being honest in check-ins. She starts treating every hallway exchange, every coffee, every “how are things going” from a partner as a potential evaluation moment. This is exhausting and corrosive. It also makes the firm worse at its job.
Firm leadership loses its earliest warning signals. Honest informal conversations are the firm’s earliest signal of attrition risk, workload imbalance, partner-associate friction, and practice group dysfunction. When those conversations get contaminated by formal-record consequences, the signal disappears. The first time leadership hears about the problem is in the exit interview, when it is too late.
Wrongful termination risk increases. Performance improvement plans and terminations built on a documentation trail that mixes coaching notes with formal evaluation entries are legally fragile. Employment lawyers consistently treat structured, multi-source, dated evaluation records as the authoritative documentation. Coaching notes pulled into evaluation files muddy the trail and make terminations harder to defend.
What the November 2025 NALP data reveals about data utilization gaps
The NALP Foundation Performance Evaluations Study surveyed 106 leading US law firms. While the headline findings covered cycle times and evaluation components, one of the more important second-tier findings was about what firms do with feedback after they collect it.
Read together, the NALP findings show that US law firms have invested in the formal evaluation record — multi-source input, self-assessments, qualitative comments, quantitative metrics — without making a corresponding investment in the coaching layer that should sit underneath it. The result is that the formal record absorbs the work of the missing coaching layer, which is exactly the conflation that produces the behavioral problems above.
The structural separation: what goes where
The good news is that this is a design problem, not a values problem. Firms that want to separate the two functions cleanly can do it. The architecture is straightforward; it is the discipline of holding to the architecture that takes work.
Principle 1 — The coaching layer is a one-way information channel into the associate. Information flows from the partner to the associate (feedback) and from the associate to the partner (struggles, questions, context). Information does not flow from the coaching conversation outward into evaluation records, comp committee discussions, or other partners’ awareness without the associate’s explicit knowledge.
Principle 2 — The formal record is built from structured inputs, not from accumulated impressions. Multi-source input, self-assessment, quantitative metrics, peer or upward feedback — all collected through a dated, structured process the associate knows is happening. Nothing in the formal record should be data the associate would not have reasonably expected to be captured for evaluation purposes.
Designing the separation deliberately
SRA designs and runs continuous review programs and structured evaluation programs as separate but connected systems. The coaching layer captures real-time feedback in a confidential channel that does not flow into the formal record. The formal evaluation runs on dated, multi-source structured input, administered by an independent third party (SRA) so that confidentiality is enforced at the architecture level, not promised at the policy level.
A practical test: Ask three of your associates anonymously whether they believe a casual comment in a check-in could end up in their year-end review. If two of them say yes, your firm has a coaching-vs-record problem regardless of what your policy documents say.
→ Schedule a consultation on coaching and evaluation architecture → Explore SRA’s review and evaluation programs
How leading US law firms design the two-track system
Firms that have separated the two functions successfully share five design choices.
1. Different cadence, different infrastructure. The coaching layer runs on a continuous cadence — quarterly minimum, monthly for first- through third-year associates. It runs in conversations, not in software. The formal evaluation runs once or twice a year, in a structured platform (often administered by an external partner) that captures multi-source input with audit trails.
2. Different people. Coaching is best done by partners or senior associates the associate is actually working with. Formal evaluations are aggregated by HR or a dedicated PD function, drawing on input from multiple partners across the year. The same person can do both, but the moments are clearly demarcated.
3. Different documentation rules. Coaching conversation notes, if taken at all, are the coach’s personal notes, used to follow up at the next coaching conversation. They are not archived in the associate’s file. Formal evaluation entries are archived, dated, attributable (or explicitly anonymous), and follow a documented process.
4. Explicit framing. Leading firms train partners and associates explicitly on the distinction. “What I’m about to discuss with you is coaching — it stays here unless something rises to a pattern that needs to enter your formal review next quarter, in which case I’ll tell you before that happens.” That sentence does meaningful work.
5. Independent administration of the formal evaluation. The single most consistent design choice across firms that have made this work: the formal evaluation is administered by an external party (like SRA) rather than by HR staff who are themselves embedded in coaching relationships. Independence creates the confidentiality the formal record needs and protects the coaching layer from contamination.
Three questions to test whether your current program has the right separation
If your firm wants to audit its own coaching-vs-record architecture, three questions surface the issue quickly.
Question
If “yes,” you have separation. If “no,” you have conflation.
Can an associate identify a clear cadence of coaching conversations distinct from their formal review?
If associates only know about the year-end review, you don’t have a coaching layer.
Would your associates say a casual mid-year conversation is genuinely off-the-record?
If they would say “probably not,” the trust contract is broken even if your policy says it isn’t.
Are formal evaluations administered with structural separation from coaching relationships?
Self-administered programs by HR staff who are themselves coaching associates tend to produce contamination.
Three yeses means the architecture is sound and the work is in execution. Two yeses means the firm is most of the way there. One or zero means the firm is running a single-track system that’s presenting itself as two-track, which is the most common pattern at US firms in 2026.
What happens when the separation is clear — and when it isn’t
The behavioral effects of getting this right show up faster than most firms expect.
None of these outcomes requires new technology to achieve. They require the firm to make the architectural commitment to treat coaching and formal review as different functions — and to design the operational rhythm, documentation rules, and infrastructure to match.
Frequently asked questions
Can the same partner do both coaching and formal evaluation? Yes, and most do. The separation is not about different people, it is about different moments, different documentation rules, and different trust contracts. A partner can have a Tuesday coaching conversation with an associate and submit a formal evaluation entry in October, as long as both partner and associate understand which mode they are in and what the rules are for each.
What if coaching surfaces something serious — like ethics issues or harassment? That is not the coaching layer’s job to handle and should not be the coaching layer’s job to handle. Serious issues belong in a separate HR/risk process with its own documentation rules. Coaching is for developmental feedback; not for misconduct investigation. Firms that try to use coaching to handle both produce bad outcomes on both fronts.
How do firms document coaching without contaminating the formal record? Most firms allow coaches to keep personal notes for their own follow-up, but those notes do not enter any firm system or get shared with anyone else. If a coaching theme rises to a pattern that should enter the formal record, the partner tells the associate explicitly before the formal cycle, so the associate knows what is going to be documented.
Does this mean partners cannot use coaching notes in writing year-end evaluations? Partners can and should bring their year of observation to the year-end evaluation. The question is whether the input is structured and the associate knows it is being captured. “I noticed in our March conversation that you mentioned struggling with X, and we worked on it through the year” is appropriate. “In May you said you were tired, which I read as a resilience concern” is not.
What about written informal feedback — Slack messages, email comments, meeting notes? Anything documented in writing is generally not the coaching layer. The coaching layer is verbal, real-time, and intentionally minimal in documentation. Written informal feedback tends to drift into the record because it exists in a searchable, archivable form. Firms with strong coaching cultures keep coaching primarily verbal.
How does this connect to formal performance reviews and evaluations? Coaching is the developmental layer. The formal performance evaluation is the documented decisional layer. They are the two halves of a connected system, and the separation between them is what makes both halves work. We covered the broader distinction in
What Is the Difference Between a Performance Evaluation and a Performance Review at a US Law Firm?.
Is this different at small firms versus Am Law 200 firms? The principle is the same, the infrastructure is different. A 12-attorney firm can run the two-track system with explicit conversational framing and a structured annual review process. A 500-attorney firm needs a more formal coaching infrastructure (PD function, documented cadence, training for partners) and typically benefits from external administration of the formal evaluation. The trust contract works at every size.
Sources
- NALP Foundation (November 2025). Performance Evaluations Study: A Comprehensive Assessment of Process and Efficacy at 106 Leading Law Firms. nalpfoundation.org
- NALP Foundation (2025). Update on Associate Attrition and Hiring (CY 2025). nalpfoundation.org
- Canadian Lawyer Magazine (November 2025). Most law firm associate evaluations don’t use AI or give speedy feedback: survey. canadianlawyermag.com
- ABA Journal (April 2025). Associates continue to leave firms within 5 years of hire, new report says. abajournal.com
- Legal Evolution (December 2025). The 2026 ‘Burning Issues’ Confronting Firm Leaders. legalevolution.org
Related reading on srahq.com
- → What Is the Difference Between a Performance Evaluation and a Performance Review at a US Law Firm?
- → Attorney Performance Review: A Complete Law Firm Guide (2026)
- → How to Create a Culture of Continuous Feedback in Law Firms
- → Attorney Self-Assessment Surveys at US Law Firms: How the Self-vs-Partner Gap Reveals What Annual Reviews Miss (2026)
- → Partner Performance Review: How US Law Firms Evaluate Equity Partners in 2026
- → Which Employee Engagement Software Should US Law Firms Actually Use in 2026?
The separation between coaching and the formal review record is not a policy question. It is an architectural one. Firms that get the architecture right run better coaching, produce more defensible evaluations, and retain associates longer. Firms that conflate the two get the opposite of all three.
SRA designs and runs continuous review programs and structured evaluation programs as separate but connected systems for US law firms. Confidential, third-party administered, with the architectural separation between coaching and formal record enforced at the system level. Built for US law firms since 1987.
Performance Reviews | Upward Reviews | 360-Degree Feedback | Firm Engagement Survey | Schedule a Consultation
Exclusively serving United States law firms since 1987.
.png){kind=small}