Our methodology

Who builds this

Built by Stanford GSB alumni who have coached applicants into the world's most selective MBA programs, many on scholarship. We publish as a team, under a collective byline, because the method is the product: what earns your trust here is not a name at the top of the page but whether the coaching holds up when you put your own material through it.

Everything in AdmitForge, the rubrics, the guidance, the questions the software asks you, was written by people who have sat on the coaching side of real applications to the most selective programs. That provenance is stated plainly and it is the only claim we make about ourselves. We do not promise outcomes, and we would not believe anyone who did.

A team byline also serves you better than a personality would. Individual coaches have good days and blind spots; a method that has been argued over, written down, and tested against real drafts is more consistent than any one reader. When you get a critique here, you are getting the distilled judgment of the team, not the mood of whoever picked up your file.

Where the method comes from

The method was not written for the internet. It comes from real coaching engagements: margin notes on real resumes and essays, the same corrections showing up again and again across applicants, the patterns that separated drafts that worked from drafts that stalled. We distilled those recurring notes into rubrics and encoded them into the product, so the software asks the questions a coach would ask, in the order a coach would ask them.

Encoding a method is harder than writing advice, and that difficulty is the point. A blog post can stay vague; software cannot. To turn a coach's instinct into a rubric, we had to name exactly what the instinct was responding to, test the written version against drafts where we knew what the right call was, and rewrite it until the encoded read matched the human one. Where the two disagreed, we treated that as a bug in the rubric, not in the coach, and went back to the source notes.

Underneath the story and essay work sits a leadership-assessment lens: a structured way of reading what a story actually shows about how someone leads, drawn from how selective programs evaluate potential. We keep the mechanics inside the product on purpose. The public artifacts that describe the standard, like the essay rubric and the four-stage process, tell you what strong work tends to do. The coaching on how to get your draft there is the paid product, and keeping that line clean is how we keep both sides honest.

How we keep the data honest

The product carries per-school facts: essay prompts, deadlines, class profile numbers, and each school's stated position on AI use. Every one of those facts is sourced against the school's own official pages, dated in the interface so you can see when it was last checked, and re-checked on a rolling basis through the application season. Where we summarize a school's policy, we label the summary as our plain-English reading and link the source so you can read the original yourself, for example on the MBA AI policy tracker.

Freshness is treated as part of the fact. Essay prompts are carried verbatim, not paraphrased; deadlines are shown with the round they belong to; class profile numbers keep the scale the school reported them on. When something changes mid-season, and most seasons something does, the dated stamp is what tells you whether we caught it yet.

We say "sourced" and "checked" rather than guaranteed, because schools change pages without notice. If you spot anything stale or wrong, tell us at support@getadmitforge.com and we will check it against the source and correct it.

The line we never cross

AdmitForge never writes your application. Not an essay, not a paragraph, not a replacement sentence to paste. The product critiques, scores, outlines, and asks questions; the words that go to a school are always yours. This is not a compliance posture we adopted late. It is the founding design constraint, and it is why the coaching works: an essay only does its job when it could not have been written by anyone else.

The full reasoning, including why ghostwritten prose tends to hurt the applicant it was supposed to help, is in our AI Integrity Policy. The standard your drafts are read against is public in the essay rubric.

How the AI is used

AI is the delivery mechanism for the method, not the method itself. It scores stories against our coaching models, pressure-tests goals and resume bullets, maps stories to each school's prompts and outlines structure, and builds recommender briefs and interview storyboards. Every one of those actions starts from raw material you bring; when a detail is missing, you get the question that surfaces it, never an invented stand-in.

Because schools increasingly ask how AI touched an application, your essay work here builds its own answer: outlines and draft critiques are logged per school, and you can export that record any time. The AI questioned and critiqued; it did not write. That is a disclosure most applicants cannot make cleanly, and ours is designed so you always can.

Your content is not used to train AI models, and we do not access it except to operate and support the product. What we store, for how long, and how to export or delete it is laid out in our Privacy Policy.