You may have a project that proves exactly what you can do, but your resume gives it only one bullet. A one-page career case study lets you explain what you did and why it mattered without asking someone to read an entire portfolio.

This document isn't a replacement for your résumé, and you don't need one for every application. Think of it as a supporting piece to pull out when an achievement lines up with an opportunity. The best ones are specific and easy to scan.

1. Start With One Achievement, Not Your Entire Career

A useful case study is narrow. Instead of summarizing every role you have had, choose one project with a clear starting point and outcome. For a student, that might be a campus event. For someone already working, it could be a shared resource that made a difficult project easier for the team.

The example does not need to be dramatic. It only needs to show what changed because you were involved. Ask yourself: What was different after I stepped in? If you can answer that question in a sentence or two, you probably have your subject.

The best choice is not always the largest project. A smaller example that closely matches the opportunity will often give the reader more useful evidence.

2. Give the Reader Just Enough Context

The reader needs to understand the challenge before the result will mean anything. Start by explaining the goal and the obstacle you faced. Two or three sentences are usually enough. Leave out company history or timelines that do not affect your contribution.

For example, imagine that a student organization had low registration for an annual event. That gives the reader a clear starting point. The page can then move into what the student changed and what happened next.

3. Separate Your Contribution From the Team’s Work

Many worthwhile accomplishments happen as part of a team. You can acknowledge that teamwork while still making your own contribution clear. Use “we” for the shared goal and “I” for the work you personally handled.

Avoid phrases such as “helped with the project” or “supported a successful launch.” They leave too much unanswered. A clearer version might say that you interviewed participants and then rewrote the instructions based on what you learned. If you changed the timeline, explain why. These details give the reader evidence without requiring you to oversell your role.

4. Show a Result the Reader Can Trust

If you have an accurate number, use it. Attendance may have grown. A project may have finished early. Perhaps fewer questions reached the team after you revised a resource. Include only figures you can verify, and give the reader enough context to understand what changed.

Not every meaningful result comes with a percentage. Maybe your recommendation was approved, or the guide you created became the version everyone used. When formal measurements do not exist, describe the change someone else could have seen. Never invent a number to make the outcome sound more impressive.

Compare “the project was successful” with “the team adopted the revised guide for future events, and new volunteers were able to use it without additional instructions.” The second version does not rely on a dramatic statistic. It simply gives the reader a concrete sign that the work solved a real problem.

5. Connect the Example to Transferable Skills

Once the accomplishment is clear, name the most relevant skills. Then connect each one to an action instead of dropping in a generic list. Changing a timeline after discovering a conflict, for example, can show planning and adaptability.

You can also adjust the emphasis for different opportunities. The same project might highlight organization for one role and communication for another, while the underlying facts remain unchanged.

Keep this section brief. Let the evidence do the persuading instead of asking the reader to accept a string of unsupported qualities.

6. Format the Case Study for Easy Scanning

A one-page limit forces you to decide what matters most. Use clear headings and enough white space. Keep the sections in a consistent order so the reader can find the key information quickly. A practical structure is:

A short project or achievement title
The context and goal
Your specific contribution
The most important actions you took
The outcome and supporting evidence
The skills demonstrated or lesson learned

You do not need decorative graphics or dense blocks of text. A descriptive title and a handful of clearly labeled sections will usually communicate more than an elaborate design.

Save the finished page as a PDF so the layout stays consistent when you email or upload it. If you also want a copy for an in-person interview, consider how paper thickness and finish affect readability and handling. A simple, professional choice will keep the focus on your accomplishment.

7. Use the Case Study at the Right Moment

A relevant page can accompany an application when work samples are requested. It can also support an interview answer or add context to a thoughtful follow-up. For students, a class project may be the best example. Someone returning to paid work might instead draw from a volunteer or community role.

You do not need to rebuild the page each time. Instead, revise the opening or skill emphasis so the most relevant part of the accomplishment is easy to spot.

Do not send it with every application just because you have it. Choose an example that addresses the skills or problems connected to the opportunity. If the relationship is unclear, save the page for a more appropriate conversation.

8. Run a Final Accuracy Check

Before sharing the page, make sure a reader can tell what the challenge was and what you contributed. Check every number, then remove any detail you are not allowed to share. If you name a client or organization, get their permission first. Finally, read it once more for jargon or small errors that could distract from the work.

Turn One Accomplishment Into Clear Evidence

A good one-page career case study does not need to cover everything you have achieved. It needs to make one relevant example easy to understand. Choose a project you know well. Describe your role honestly, then give the result enough context to speak for itself.