PhD SOP: Describe Research Still in Progress

PhD SOP: Describe Research Still in Progress

Describe an ongoing research project by separating work completed, preliminary observations and planned steps. You can explain a meaningful contribution before final results exist. Do not report an expected finding as an outcome or turn a project idea into a manuscript in preparation.

Our recommendation is to anchor the paragraph in something already done. A research question, a design choice, a pilot or a documented obstacle can provide substance. A forecast that the project will produce an important paper cannot substitute for evidence available when you apply.

This is not primarily a publication-label problem. The under-review manuscript guide addresses a manuscript that exists. Here, the question is how to make a research experience intelligible when its central conclusion is still open.

Divide your notes into three time states

Before drafting, create three headings: completed, being evaluated and planned. Put each claim under exactly one heading. If you are unsure, check the project record or ask the supervisor.

This separation is especially useful when a deadline falls during data collection. You may have completed substantial preparation without knowing the answer to the main question. The statement should preserve that distinction rather than compress every stage into “I conducted a successful study.”

The NIH Office of Intramural Training and Education's statement guidance emphasizes explaining project goals, approaches, results and the applicant's role, while following the actual program prompt. When results are pending, state that fact and explain the completed work; do not fill the missing category with an anticipated conclusion.

Select the strongest available evidence

Ask what a knowledgeable reader could question you about today. Could you explain why one method was chosen? What a pilot revealed about feasibility? Which assumptions remain untested? What you would do if the next observation contradicts your expectation?

Those questions help identify a contribution that exists now. They also expose cases where the experience is mostly future tense. If you have just joined a project and attended one meeting, a long paragraph about its possible impact may give the wrong impression of your involvement.

There is no universal minimum project duration that makes an SOP paragraph legitimate. Time matters because it affects what you have actually done, not because a particular month count automatically proves depth. If an application separately requests research duration, follow its definitions and report the actual dates.

Choose between a recent ongoing project and an older completed one by evidence, relevance and the prompt. Recency alone should not displace the experience you can explain most clearly.

Case A: meaningful work before the primary result

Constructed GradPilot case; not a real applicant or study. A neuroscience research assistant helped prepare a study and test the data-processing procedure. Recruitment is ongoing, so the primary analysis has not begun. The assistant has already found a mismatch between recorded event times and the analysis script's assumptions.

A possible paragraph is:

I am contributing to an ongoing study of response timing. Before the primary analysis, I tested the processing script against manually checked records and found that it treated two event markers as interchangeable. I documented the mismatch and revised the script with my supervisor's approval. Recruitment is still underway, so the study has not yet produced its main result. The preparation work has made me interested in how measurement definitions influence the inferences drawn from behavioral data.

The paragraph gives the applicant an actual contribution without borrowing a future conclusion. It also separates the broader study from the preparatory task. The applicant did not design every aspect of the research merely because their work affected the pipeline.

If the revision has not been approved or implemented, those verbs must change. “I proposed a revision” is meaningful when true. It is not a weaker version of an implementation that never happened.

The next sentence in the SOP could connect the measurement question to a verified research area at the target program. It should not promise that the ongoing project will be completed, accepted or published by enrollment unless the statement has a sound basis for the relevant claim—and publication decisions still belong to the venue.

Case B: a project that has barely started

Second constructed case. An applicant has accepted a research-assistant role beginning shortly before applications are due. They have completed onboarding and read background papers, but have not yet carried out the planned experiments. Their earlier thesis provides a more substantial research record.

Our recommendation is to give the new role a brief, factual mention and let the thesis carry the detailed evidence. Do not write the planned job description as if it were an accomplishment.

A truthful sentence could be:

I recently joined a project examining material degradation and am completing the initial training for its measurement workflow; the experimental work is planned for the coming term.

The sentence establishes current activity and future context. It does not claim results, expertise or independence. The main research paragraph can then describe what the applicant actually did in the thesis.

If the new role is central to explaining a change of direction, add a short reason for choosing it. For example, the applicant may want experience with a measurement approach they previously studied only theoretically. That motivation is real even before the work is complete. It should remain a motivation, not be presented as demonstrated mastery.

The PhD SOP without publications guide can help identify evidence in completed work that an applicant may be undervaluing.

Write preliminary results at the right level of confidence

A preliminary observation can belong when it helps explain your next decision and can be shared. Label it as preliminary and identify the relevant limitation. Do not use the label as a small disclaimer attached to an otherwise sweeping claim.

For instance, a pattern in an initial subset may motivate a fuller analysis. That does not justify saying that the project established the pattern in the full population. A pilot that demonstrates the procedure can run is not necessarily evidence for the main scientific hypothesis.

Discuss the wording with the project supervisor. Ask whether the paragraph distinguishes observation from interpretation and whether ongoing work can be described externally. If confidentiality is involved, use the industry-research disclosure guide before sharing the draft.

You do not need to include every caveat from a technical report. Choose the limitation that prevents a reader from misunderstanding the claim. Precision is more useful than an elaborate list of uncertainties with no connection to the applicant's decision.

Keep the CV and application form synchronized

Use accurate dates and present-tense responsibilities for a current role. A CV may list an ongoing research appointment even when no publication exists. A publication field may have different rules; read its label rather than assuming it accepts every project.

Do not list “manuscript in preparation” merely because the team hopes eventually to write a paper. Confirm the actual state with the responsible collaborators. If a real manuscript exists, the separate paper-status guide covers the distinction between internal drafting, submission and acceptance.

The application should have one coherent cutoff: what was true when you submitted. If the program allows later updates, follow its instructions. Do not delay a complete application solely because you imagine that a result arriving after the deadline will automatically be accepted through any upload field.

See the graduate application update guide for the separate question of what a program permits after submission.

A final tense and evidence check

1. Underline every past-tense achievement and verify it happened.
2. Mark every preliminary finding and state the limitation that matters.
3. Put planned steps in future or conditional language.
4. Identify your contribution separately from the group's plan.
5. Remove promised publications and anticipated outcomes presented as facts.
6. Ask whether the paragraph still contains useful evidence after those corrections.

If the final answer is no, shorten the paragraph and use another experience. The application does not become stronger by expanding a plan into a history.

Should I wait until the project is finished to apply?

That depends on the target's requirements, your overall preparation and what completion would add. Compare the missing evidence with the cost of delaying. A finished project may matter substantially in one case and add little in another. There is no general rule that every ongoing project must end before an application can be credible.

Review the account you can defend today

The research-focused PhD SOP rubric, available through PhD statement review, can help examine whether completed work, uncertainty and future direction are clear in your draft. It does not authenticate results or predict a publication decision. The PhD essays hub collects related application-writing guidance.

Primary guidance checked September 14, 2026. All applicant cases and the tense-check procedure are original GradPilot illustrations.