MBA Recommender Questions: Constructive Feedback

MBA Recommender Questions: The Constructive-Feedback Answer

You have agreed to recommend someone for an MBA and you are expecting a blank page. You will not get one. Most business-school forms are a ratings grid plus three or four fixed questions, and one asks for the most important piece of constructive feedback you gave this person, the circumstances, and how they responded.

That is the question people stall on, and the one a reader uses to decide whether the rest of your letter is testimony or advertising. This guide is for you, the recommender: what the questions are, what each program prints beside them, how to build the feedback answer out of something you watched happen, and what the applicant should hand you. For a second read on a finished draft, that is what a letter of recommendation review is for — subject to one program-policy caveat below.

An applicant put the problem plainly on r/MBA in January 2022: "At my job, me and my manager didn't really have a culture of sitting down and doing a performance evaluation." Most workplaces don't. The answer still has to exist, and to be true.

The three questions almost every program asks

Many programs use, or reproduce, GMAC's Common Letter of Recommendation. Its open-ended section reads, on the 2024 form:

1. "Please provide a brief description of your interaction with the applicant and, if applicable, the applicant's role in your organization. (Up to 50 words)"
2. "How does the performance of the applicant compare to that of other well-qualified individuals in similar roles? Please provide specific examples. (Up to 500 words)"
3. "Describe the most important piece of constructive feedback you have given the applicant. Please detail the circumstances and the applicant's response. (Up to 500 words)"
4. "Is there anything else we should know? (Optional)"

Before the questions sits a ratings section: GMAC's page describes a grid of "12 competencies and character traits that contribute to successful leadership," in five categories, and lists the participating programs — Tuck, Fuqua, Stern, Stanford GSB, Haas, Ross, Darden and Yale SOM among them. Prose and ratings are read together, so a top-decile box beside a paragraph of mild adjectives is a contradiction the reader will notice.

Question 2 has drifted — Tuck, Kellogg and Booth ask for specific examples; Ross and Stern still print the older "(E.g. what are the applicant's principal strengths?)". Question 3 has not drifted. Of the 16 programs we checked on 1 September 2026, nine print it on their own pages in near-identical words, two more say they use the GMAC form containing it, one has it reported for this cycle, three publish no questions, and one page we could not read.

Who asks for what: letters, limits and wording

All sixteen pages were read on 1 September 2026 (Ross errors on some automated requests; read from the same URL). Where no limit is printed, write to the GMAC ceiling — but open the form first.

The constructive-feedback answer: observation, feedback, response

Stern prints the whole demand in one line: "Describe the most important piece of constructive feedback you have given the applicant. Please detail the circumstances and the applicant's response." That last clause is why the question exists, and the half most answers skip.

Observation. What you saw, when, in what setting. Not a trait, a scene. "He was slow to delegate" is a label; "by April the review queue was three days deep and two engineers had stopped proposing work" is something a reader can weigh.

Feedback. What you said, roughly when, and in what forum — a one-to-one, a written review, a conversation after a client meeting. If you softened it, say so; readers are calibrating your judgement too.

Response. What changed, over what period, and how you know. This is the only part nobody else can write for you, and the part that turns a criticism into a recommendation. Give it a date and a second observation: the queue cleared, the deck came in at eight slides, the client called back.

The skeleton is four sentences: the situation and its cost; the feedback and where you gave it; what they did next, with a date; where it stands now.

Six composite answers

The six below are composite — constructed by us for this guide, not letters anyone submitted. Each follows the shape above and sits inside the tightest limit on the question, HBS's reported 250 words.

1. Delegation. (composite) R. led a four-person workstream and reviewed every change personally before it merged. By April the queue was three days deep and two engineers had stopped proposing work. I told her the standard was right and the queue was the bottleneck, and that I would judge her on the team's throughput, not her own output. She disagreed in the room. Ten days later she had written a two-page merge standard and handed approval to two engineers, and the queue cleared within a month. Measurable cost, disagreement left in, checkable change.

2. Over-preparation. (composite) This one usually fails, because "works too hard" is a compliment in disguise. T. brought a 62-page deck and no recommendation to a client steering meeting, and the client deferred the decision three weeks. I told him the deck was insurance against a question he could not answer, and that the insurance cost more than the risk. He rebuilt the next as three slides and an appendix, and took the feared question on slide two. A cost, not a virtue; the change is a habit, not a mood.

3. Written concision. (composite) K.'s analysis was the best in the group and the least read: nine-page memos with the finding on page six. Twice I watched stakeholders skim to the appendix and ask something she had already answered. I told her a finding a reader does not reach is a finding she did not deliver, and to open with the decision and the two numbers behind it. Her next memo was two pages, and the division head later quoted its first paragraph back to her. About impact, not style; the last detail is an observation.

4. Stakeholder patience. (composite) In a regulatory remediation, M. was right about the sequencing and could not get compliance to move. He treated their questions as obstruction, escalated twice in a month, and the relationship stalled. I told him being right had become the least useful thing about him, and asked for a fortnight without escalating. He spent it in their stand-up, learned what their audit obligation required, and returned with a plan that met both. The compliance lead now asks for him by name. A real weakness, a specific instruction, a third party as evidence.

5. Technical-to-managerial shift. (composite) Promoted to lead the team he had been the strongest engineer in, A. kept the hardest problem for himself, and two juniors went a quarter without work either could point to. I told him at his first-quarter review that his job had changed from solving to staffing, and his year would be measured by what the team could do without him. He gave away the next hard problem, paired two weeks, then stopped. That junior presented the result to our director in July while A. sat at the back, saying nothing. A handover, not an attitude; the last clause is firsthand.

6. Conflict avoidance. (composite) Running a cross-functional initiative, S. agreed in the room with two teams who wanted incompatible things, then absorbed the conflict for six weeks. The work slipped a month before either team knew there was a disagreement. I told her that holding conflict privately cost the initiative its early warning, and that surfacing a disagreement in week one is a service, not a failure. She rebuilt the weekly steering meeting to open with the open conflicts by name; the next slip was flagged in four days. The feedback became a mechanism she built; the outcome is a time difference.

What weakens the answer

No observation. Feedback with no scene attached reads as invented, because it usually is. "I encouraged her to develop her strategic thinking" says nothing about the applicant and something unflattering about the writer. If you never gave substantive feedback, say what you did observe; a short honest answer survives scrutiny better than a manufactured one.

A strength disguised as a weakness. "Too much of a perfectionist," "cares too deeply." Readers treat these as a decision to skip the question. If the true answer is flattering, give it a cost: what did it delay, and what changed?

A paragraph the applicant wrote. Two programs are worth quoting here. Stanford GSB: "Your recommenders must be the sole authors of your letters of recommendation. Drafting, writing, translating, editing, or submitting (even if written by your recommender) your own recommendations, or having any outside party review or edit them (even if asked to do so by a recommender), is a violation of our application terms." Yale SOM: "you can have no role in the drafting or submission of your recommendations," and shared language between essays and letter "may raise concerns to us about the independence of the recommendations." If you have been offered a draft, our guide to being asked to write your own letter of recommendation has the alternatives: ask for facts, not prose. One dated incident beats a page of adjectives; how long a letter of recommendation should be covers the rest.

HBS: recommenders are asked about AI too

For 2026-27 the HBS form is reported to carry a certification question — "Have you utilized AI in completing this recommendation?" — reported by Clear Admit for the Class of 2029. We found no AI text on the HBS application-process page on 1 September 2026, so treat it as reported and confirm it in the form. The applicant's side is covered in MBA AI-use disclosure statements by school.

Two rules follow. Absence is not permission: a page with no AI or outside-assistance rule authorizes neither, and the certification you tick at submission is what binds you. And a published rule may reach further than AI — Stanford GSB's sentence above rules out any outside party reviewing or editing the letter, so no second read of any kind, ours included, belongs on a GSB recommendation.

So read the program's current authorship, AI and outside-assistance rules before using any review of your letter; do not use one where AI review or outside assistance is prohibited; submit only your own writing. Where a review is permitted, ours reads the two core answers against the questions the form asks and points to the sentences behind each comment — whether the comparison names a group you know, whether the feedback answer says what changed. It does not draft, and the review is visible only to you unless you choose to share it. An account comes with two free Quick Reviews each day; your first Full Review costs $5 and is typically ready in about 2–3 minutes. The MBA recommender rubric is published — read it first.

The briefing kit the applicant should hand you

If you are the applicant reading over a recommender's shoulder: this is your job, and it is not a draft. One page of facts separates a letter written from memory from one written from evidence.

1. The working relationship. Dates, your role and theirs, the reporting line, how often you worked together. That is question one, in 50 words.
2. The comparison group. Who to compare you with — "the eight analysts you have managed since 2022," not "your colleagues." A comparison with no named group is the commonest weak answer.
3. Three or four incidents. Each with a date, what you did, what happened, any number attached. Bullets, no adjectives, nothing paste-ready.
4. The feedback moment as you remember it. When they told you something hard, roughly what they said, what you did next. They will write their own version — that is the point — but this memory is hardest to retrieve and easiest to supply.
5. Logistics. Every program, portal and deadline. Recommendations are the slowest part of an application, so send this early.
6. Nothing else. No draft, no suggested phrasing, no copy of your essays — Yale warns about shared language.

Hand that page over, and if your recommender wants a second read on the finished answers, point them at the recommendation letter review — where the program's rules allow it. Your essays are a separate job (MBA essay review covers that), and our graduate school letters of recommendation guide covers portals, waivers and timing.

A checklist before you submit

1. Open the form first. Wording and limits vary; several programs print none.
2. Name the comparison group in the second answer, with the basis for it.
3. Write the feedback answer as a scene: observation, feedback, response.
4. Check the response half exists. If the answer stops at what you said, it is half an answer.
5. Reconcile prose and ratings. A top-decile box needs a paragraph that earns it.
6. Keep the two answers distinct. If the feedback answer has become more praise, a question is unanswered.
7. Confirm the certification — authorship, outside assistance, the reported HBS AI question — before uploading.

Sources

Every page linked above was read on 1 September 2026.

• Published, first-party — every program page in the table, plus GMAC's Common LOR page and 2024 form, Stanford GSB's letters-of-reference terms, and the HBS application-process page, which carried no AI text.
• Reported — Clear Admit's 2026-27 HBS recommendation questions: the limits and the AI question.
• Not retrieved — Columbia Business School's admissions pages, HTTP 403 on every route tried.
• Applicant voice — r/MBA, "Constructive feedback recommendation question", 23 January 2022.