SOPHAS Experiences: What to Repeat From a CV

SOPHAS Experiences: What to Repeat From a CV

Repeat the factual experience where your application requests it. Keep dates, roles and hours consistent, while adapting the explanation to each field. SOPHAS Experiences, Additional Experiences and your resume serve different purposes; a resume upload does not automatically replace the other sections.

The practical recommendation is to maintain one accurate record and produce the requested versions from it. Trying to make every section contain entirely new accomplishments creates unnecessary work and can introduce contradictions. For fees, verification and submission timing, use the existing SOPHAS application guide.

Here, the problem is allocation: what the reader needs in each place, how much repetition helps and where repeated information becomes misleading.

Give each surface a clear job

The public instructions below were checked September 16, 2026. Use the current fields in your own account for their exact wording and technical limits.

SOPHAS Additional Experiences includes optional questions about matters such as work since the first bachelor's degree and national service. Read the actual question before supplying another individual role.

Program instructions still matter. Harvard Chan tells applicants to complete SOPHAS sections and separately supply a resume/CV. Michigan labels the resume/CV recommended and says a cover letter is unnecessary. These are named programs' rules, not interchangeable instructions for every application.

Start from one role record

Before composing descriptions, make a private record for each experience: organization, actual title, start and end dates, current status, duties, average weekly hours and someone who can verify the role. Use information you can substantiate from your own records.

Resolve factual uncertainty here. If you cannot remember whether a role began in June or July, check the underlying information before reproducing a guess across several documents. If a position changed substantially, note when the change occurred and what changed. A promotion and a new responsibility are not always the same event.

The official SOPHAS Experiences guidance asks for responsibilities and time commitments, including average weekly completed hours. It advises choosing categories according to duties and notes that programs may classify an experience differently. It also rules out repeating hours between experience types.

That makes the content of the role more important than finding a category that sounds prestigious. Use the available definitions and your actual duties. If the categorization affects a program prerequisite, ask that program; a dropdown choice is not an eligibility determination.

Repetition becomes useful when the level of detail changes

Constructed example: Priya worked as an outreach assistant. She scheduled sessions, coordinated reminders and maintained attendance records under a program coordinator's supervision.

Her resume might summarize those responsibilities in a compact bullet. An experience entry could explain the setting, her routine responsibilities and how her work connected to the coordinator's role. Her personal statement could discuss a particular observation that changed the question she wanted to study.

Those versions can legitimately share the organization, role and dates. Their purposes differ:

• The resume helps a reader scan the trajectory.
• The entry makes one role understandable on its own.
• The statement explains why an experience matters to the applicant's direction.

A description such as “Supported community outreach” is short but leaves almost everything unstated. Adding the tasks above makes it informative. Adding a claim that Priya transformed community health would make it less defensible unless she had evidence for that much broader conclusion.

Do not embellish an entry merely because the box has unused space. The best stopping point is when the role, your contribution and its relevant context are clear. A character allowance is room to answer, not a requirement to expand every position equally.

For the later interpretive step, see the MPH statement examples. They address turning preparation into a reason for graduate training rather than cataloguing responsibilities.

A mixed-duty role does not create extra hours

Constructed calculation: An applicant worked an average of 12 hours per week in a role combining research support and another responsibility. Their records support an average split of eight hours on the first set of duties and four on the second.

If the role appropriately appears in two experience categories, the total remains 12 hours. Entering 12 hours under each category would describe 24 hours of work that did not happen.

SOPHAS permits dividing a mixed role's duties and hours between sections, with no duplicated hours. That does not mean every role should be split. First ask whether two entries clarify materially different responsibilities and fit the current application instructions. If a single accurate entry is clearer, avoid unnecessary fragmentation.

Do not invent a precise split from vague memory. Review schedules or records, and seek guidance where the form does not accommodate the way the role operated. The aim is an honest average, not impressive arithmetic.

Apply the same consistency check to overlapping jobs. Calendar overlap can be real; it needs an accurate account of the hours in each role. A busy schedule does not justify reporting a full-time equivalent you did not actually work.

Current experience is different from a future plan

The SOPHAS guidance allows current and in-progress experiences, rather than planned ones. It also recommends focusing on experience within the last ten years and at college level or later. Follow any additional program documentation requirements.

This distinction matters when your application is due before an internship finishes. Describe the experience you have begun accurately, with its current status. Do not quietly convert expected future accomplishments into completed responsibilities or results.

A future assignment can be relevant elsewhere if a program asks about plans. Its possible relevance does not change its status in the experience record. Check the exact field rather than using one sentence to blur completed work and anticipated work together.

Similarly, answering Additional Experiences about years since your first bachelor's degree is not the same as proving a particular program's work requirement. The MPH work-experience eligibility guide explains how degree format, qualifying work and the program's counting rule must be checked separately.

Choose details that someone else could confirm

The official experience instructions ask for a person who can verify the experience. For a student-organized group without an adviser, they allow a member who can verify your involvement. Choose someone with actual knowledge of the role, rather than assuming the most senior name is the best one.

Write the description so that this person would recognize it. Would they agree with the responsibilities, your level of independence and the dates? If you wrote that you led a project, does that mean you organized its schedule, supervised others or made the methodological decisions? Clarify the claim rather than relying on the broadest possible interpretation.

Where research is involved, distinguish supporting the project from owning the analysis. If a separate supplement asks about methods, your quantitative experience statement can explain the task in more depth. The experience entry should remain consistent with that explanation.

You do not need to attach someone else's private information or a confidential work product to make the role credible. Use the verification fields and permitted supporting materials as instructed.

Run a consistency check across the whole application

Open the resume, experience entries and main essay together. Check one role at a time rather than proofreading each document in isolation.

Look for mismatched dates, different titles, inconsistent current status, duplicated hours and claims that grow stronger each time they appear. Also check whether a team result has become your individual result in the personal statement.

Then check for omissions. Have you answered the requested structured fields, or assumed the reader will retrieve the information from another file? Have you answered the Additional Experiences question itself, or supplied a paragraph that belongs elsewhere?

Finally, use the application's available preview to examine what you are submitting. Keep a copy of the final versions so you can answer later questions consistently. For an uncertainty you cannot resolve from the published instructions, identify the exact field when contacting the application service or program.

These checks improve the accuracy of the record; they do not predict how a committee will value an experience. Nor does a longer description establish more preparation than a concise, specific one.

The graduate application collection provides related reading. When you move from documenting experiences to explaining them in your main MPH statement, the GradPilot MPH personal statement rubric and graduate statement review are the relevant review route. They do not review or verify the structured SOPHAS experience table, your resume or your eligibility calculation. Follow the current assistance rules for each program's writing.