How Long Should Your ABOS Part II Case Summary Be?

Candidates ask this question more than almost any other: how long should my ABOS Part II case summary actually be? The honest answer is that length is the wrong question. Fit is the right one.

Here's the framing that matters. Your case selectors assign you twelve cases. You will only defend your own cases in the exam room. The summary you upload is not a supporting document sitting off to the side — it is the structure of your presentation. When you walk into the room and start talking, you are walking through the same summary the examiners are reading on their screen. That's the spine. Everything else is muscle around it.

Which means the length question becomes a performance question. Too short and the examiners have nothing to anchor on — they jump straight to interrogation because you haven't given them a story to follow. Too long and you ramble in the exam room, lose the thread, and run out the clock before you get to the parts that showcase your judgment.

The Sweet Spot: Stand-Alone but Walkable

Think of your case summary as serving two audiences at once. Audience one is the examiner who is reading silently while you present — they should be able to follow along and cross-check what you're saying against what you submitted. Audience two is you, the candidate, presenting out loud. You need to be able to walk the room through that summary in the time you have per case without skipping anything load-bearing.

That gives you a practical test: a summary is the right length if it is complete enough to stand alone as a document and concise enough to walk through verbally in your allotted time. If a colleague could read it cold and understand the case without asking questions, it's complete. If you can walk through it out loud at a natural pace and finish with time left for examiner questions, it's concise.

Those two constraints squeeze you into a narrow band. That band is where you want to live.

What a Complete Summary Actually Contains

Regardless of exact word count, the elements that make a summary stand on its own are the same across every case. If any of these are missing, examiners will notice — and they'll ask about exactly the thing you left out.

• Presenting complaint — what brought the patient in, in their own terms, plus duration and mechanism if relevant.
• Relevant history — medical comorbidities, prior surgeries, occupation, hand dominance, smoking, anything that changes your risk calculus or treatment options.
• Physical exam findings — pertinent positives and pertinent negatives. Don't read every line, but the negatives that rule out alternatives need to be there.
• Imaging — what you ordered, what it showed, and the classification if one applies.
• Diagnosis — stated clearly, not buried.
• Treatment plan and shared decision making — what conservative measures were tried, what the options were, what the patient chose and why.
• Intraoperative decisions — approach, implants, anything non-standard, and the reasoning.
• Post-op course — weight bearing, therapy, complications if any.
• Outcome — honest, specific, and humble in tone.

That list is non-negotiable. The summary length you end up with is whatever it takes to cover those elements cleanly — not a word more, not a word less.

Format: Bullets or Short Paragraphs

Dense prose is your enemy. When you're standing in the room presenting, you need to be able to glance down and find your place instantly. Walls of text don't let you do that. Bullet points or short paragraphs do.

Short paragraphs are fine for the narrative sections — presenting complaint, decision making, operative course. Bullets work better for exam findings, imaging, and post-op timeline. The goal is a visual structure that mirrors how you actually talk through the case.

One non-obvious point: before you finalize any formatting choices, check your submitted summaries against whatever current ABOS guidance exists for your exam cycle. Formatting expectations can change, and you don't want to discover on exam day that your layout fights the system you're uploading into.

Why Too Short Is Worse Than It Sounds

Candidates who under-write their summaries usually think they're being efficient. They strip out “obvious” details, compress the history into a single line, leave the pertinent negatives off entirely. They assume the examiners will ask if they want more.

That assumption is expensive. When a summary is thin, the examiners lose confidence in your documentation before you've said a word — and the second examiner in the room, the one reviewing your PDFs silently while the first examiner runs the conversation, starts hunting for what you left out. Every gap in the document becomes a question you weren't expecting. You lose narrative control before you even start.

A summary that stands on its own is the cheapest defense you have. It signals that you documented the case carefully, that you know what's relevant, and that you're not hiding anything. Those signals matter before you open your mouth.

Why Too Long Is Just as Dangerous

The other failure mode is the candidate who treats the summary like a research paper. Every lab value, every encounter note, every paragraph from the op report. They figure more information is safer information. It isn't.

A bloated summary does two things to you in the exam room. First, it gives the examiners a menu of things to grill you on — if it's in your document, it's fair game, and you'd better know why you included it. Second, it makes you ramble when you present. Candidates who write too much feel obligated to cover too much verbally, which means they burn clock on low-value details and arrive at the decision points with no time left to defend them.

The decision points are where the exam is actually won. You want to arrive at them early, with time and composure to spare.

The Verbal Test

Here is the test almost no candidate actually runs. Pick a summary. Stand up. Walk through it out loud, at a natural pace, as if an examiner is listening. Don't read it — reference it the way you will in the real room.

Time yourself. If you run long, your summary is too long — or it's written in a way that makes you meander. If you run short, either you're rushing or the summary is thin. If you stumble, the structure isn't matching how you naturally think about the case.

Do this for every one of your twelve cases. Do it more than once. Repetition is what turns a summary from a document you wrote into a presentation you own. For more on why reps beat variety, see practicing under time pressure for the ABOS Part II.

Rewrite Until It Sounds Like You

The last filter is voice. If your summary uses phrasing you would never actually say out loud, it will trip you up in the room. The language needs to match your natural speaking cadence. Read a sentence aloud — if it feels stiff, rewrite it until it sounds like something you'd tell a colleague in the hallway.

This is where most candidates stop too early. They write the summary, upload it, and assume they'll figure out how to talk through it on exam day. That's the failure mode. The rehearsal is the preparation. The summary is just the script you rehearse from.

The Bottom Line

Stop asking how many words your case summary should be. Start asking whether it stands alone as a document and whether you can walk through it verbally in your time window. Those two constraints define the right length for your specific case and your specific speaking style.

Complete enough to anchor the examiners. Concise enough to keep you on the rails. Written in your voice. Rehearsed until it flows. That's the standard. Everything else — word counts, page counts, rules of thumb from the internet — is noise.