This fictional composite shows how a strong recommendation can follow the LOR Writer format while remaining specific to its destination. It is not an actual applicant letter, proof of admission, or a promise of results.
The structure and evidence choices are informed by the official sources listed below. Every name, institution, event, and result is invented. A real writer must replace them with facts they personally know and can honestly defend.
Complete sample in the LOR Writer format
Destination: MBA and graduate business programs. Every identifying detail and event below is fictional.
Dear MBA Admissions Committee:
I have managed Alex Morgan for three years, first as a senior analyst and now as a product operations manager. Alex leads cross-functional work across engineering, customer support, and finance, and I review both the operating results and the way Alex develops colleagues through that work.
Last year, delayed customer implementations were creating revenue risk and conflict between teams. Alex mapped the handoffs, found that three groups were tracking different definitions of readiness, and convened a working session in which each team named its constraints. Rather than impose a dashboard, Alex built the measures with the people who would use them. Within two quarters, median implementation time fell from 41 to 29 days while escalations declined by 22 percent. More important, the teams continued using the process after Alex stepped out of the weekly meetings.
Alex’s development has been equally revealing. Eighteen months ago, I told Alex that a desire for complete analysis was slowing decisions and limiting delegation. Alex asked for examples, began distinguishing reversible from irreversible decisions, and assigned two analysts ownership of defined workstreams with weekly coaching rather than daily intervention. One of those analysts now leads our enterprise implementation portfolio. Alex still values evidence, but now matches the depth of analysis to the cost of delay.
Among the 14 managers I have supervised at a comparable career stage, Alex is in the top three for cross-functional influence and talent development. That ranking reflects sustained operating results, the trust of peers outside Alex’s reporting line, and the growth of people Alex has coached.
Alex will bring rigorous problem-solving, self-awareness, and collaborative leadership to an MBA classroom. I recommend Alex enthusiastically and expect the program to accelerate an already meaningful leadership trajectory.
Do not copy the fictional evidence. Use the format to organize a real relationship, firsthand observations, honest interpretation, and the writer’s independent recommendation.
Why this research-informed sample works
The letter establishes the writer’s vantage point before making judgments, develops observable moments instead of adjectives, and connects those moments to the destination’s actual decision criteria.
- The GMAC Common Letter asks for relationship context, comparison with similar professionals, specific examples, and constructive feedback.
- The results example distinguishes Alex’s decisions from the team’s shared work.
- The feedback paragraph shows both a real development need and the applicant’s response.
- The comparison uses a relevant role and career-stage group.
Use the structure—never the fictional facts
Treat the sample as a map: relationship, evidence, interpretation, calibrated endorsement, and independent submission. Copying its stories, rankings, outcomes, or language into a real letter would make the recommendation less credible and potentially misleading.
- Replace each example with a firsthand moment the writer actually observed.
- Define the comparison group before using a rank or superlative.
- Remove any claim the writer cannot verify independently.
- Follow the current program, portal, employer, or board instructions.
- Have the writer review, revise, sign, and submit the final letter personally.
Why we do not call any sample a guaranteed winner
Admissions and selection decisions depend on the full application, the applicant pool, institutional priorities, and destination-specific rules. No public sample can prove that a letter caused an acceptance. The honest standard is research-informed, evidence-rich, and appropriate for the decision—not guaranteed.
Official guidance used for this sample
These sources informed the destination criteria and workflow. Requirements can change; always check the current destination instructions.
Borrow the evidence-first architecture, preserve the writer’s real voice, and replace every fictional detail with something true, firsthand, and destination-relevant.
Keep the mba requirements in view.
GMAC’s Common LOR is designed to reduce duplicate work across participating schools. Its core prompts ask about the working relationship, comparative performance with specific examples, and the most important constructive feedback given—including how the applicant responded. School-specific instructions still control submission.
Return to the MBA cluster →