Sources and scope · Guide reviewed September 22, 2026

Coverage: Faculty-job research statements: prompt control, contribution evidence, future-program logic, institution-specific fit, and final revision
Source basis: Six public university career and communication guides from MIT, Cornell, UCLA, the University of Washington, and UCSF

Prepared by the Manusights editorial team. Publisher and institutional instructions take precedence.

Faculty application desk

Control the prompt.
Build the evidence.

A research statement is not a CV in prose and not a generic grant plan. Build an argument that connects demonstrated contributions to a credible future program in the context of one actual position.

6 university sources5-part evidence architecture8-pass revision auditEdition 2026.09.22-statement-1

Five-page planning and revision pack

Faculty research statement evidence map

Capture the controlling prompt, map contribution evidence, design a future program, verify institutional fit, and record the final revision pass. Licensed CC BY 4.0 for the original Manusights framework.

Edition: 2026.09.22-statement-1
Format: PDF
License: CC BY 4.0
Evidence reviewed: September 22, 2026

Download PDF

Decision boundary

There is no universal page count or structure

Official university guidance disagrees on typical length because applications and disciplines differ. That disagreement is useful: it shows why the posting must control the document. Source A Source B Source C Source D

Official source	Its published example	Boundary
MIT CAPD	Length varies; typically 3-5 pages, excluding citations.	Cross-discipline overview that explicitly notes disciplinary variation.
MIT EECS Communication Lab	Around three pages in EECS.	Discipline-specific example, not a universal rule.
Cornell Graduate School	One or two pages, three at most.	General academic-job guidance from one institution.
UCLA Career Center	Usually 1-2 single-spaced pages.	General guidance that also says structures vary by discipline.

Control order: exact posting first, current field convention second, general guidance third. If the application does not specify something, label it unknown before deciding how to proceed.

Original Manusights framework

Five records turn a draft into an argument

Use the architecture before writing paragraphs. Each record has a controlling question, a bounded drafting task, and evidence that lets you audit the result.

1
Prompt control
What does this exact posting require?
Record
Copy the requested document name, prompt, page or word limit, file rules, named research area, position type, and deadline. Mark anything unstated as unknown rather than importing a rule from another application.
Evidence of completion
Posting URL or saved announcement, observation date, and a requirement checklist.
2
Research identity
What durable problem connects your record and future program?
Record
Write one plain-language sentence that names the problem, why it matters, and the distinctive perspective or capability you bring. Treat it as a testable throughline, not a slogan.
Evidence of completion
The same throughline remains visible in the opening, contribution sections, and future program.
3
Contribution chain
What did the work establish, and what question did it open?
Record
For each selected project, map problem, your contribution, evidence or output, significance, and the next question. Select projects for the argument they build rather than listing the CV chronologically.
Evidence of completion
Specific findings, methods, outputs, publications, datasets, software, archives, or other field-appropriate evidence.
4
Future program
What coherent work becomes possible next?
Record
For each direction, state the question, significance, approach, feasibility basis, expected contribution, and relationship to your prior work. Distinguish a program from a single project and from unsupported ambition.
Evidence of completion
A credible bridge from demonstrated capability to new work, with uncertainties and dependencies visible.
5
Institutional context
What changes because this is this position at this institution?
Record
Connect the program to verified facilities, collections, communities, teaching context, collaborators, or strategic priorities only when the public evidence is specific and relevant.
Evidence of completion
Current official source, exact fit claim, and a sentence explaining mutual contribution rather than generic praise.

Contribution chain

Do not make the reader infer what your work established

For each selected contribution, connect the problem to your role, checkable evidence, meaning, and the next question. The sequence is an editorial test, not a required set of headings.

1
Problem
What bounded research problem or gap did this work address?
2
Your contribution
What intellectual, methodological, empirical, theoretical, creative, or archival contribution was yours?
3
Evidence
Which result or output substantiates the contribution? Record a citation or stable locator.
4
Meaning
What did the evidence change, clarify, enable, or challenge?
5
Next question
Which unresolved question follows, and why does it belong in the future program?

Selection rule: include a contribution because it proves part of the future-program argument, not merely because it is recent, prestigious, or already listed on the CV.

Future program

Show a program without pretending the future is settled

University guidance consistently asks for future direction, but the form varies by field. Map each direction through six checks, then choose the number and level of detail required by the posting and local discipline. Source A Source B Source C

Question

What is the direction trying to learn, explain, build, recover, or test?

Significance

Why would a field-adjacent reader care if this succeeds?

Approach

What methods, sources, populations, materials, or analytic strategy make the direction concrete?

Feasibility

Which prior result, skill, access route, collaboration, or preliminary observation makes the work credible?

Distinct contribution

How does the direction extend beyond prior mentors, current projects, or an obvious next experiment?

Boundary

What remains uncertain, dependent, or adaptable? Avoid presenting a speculative result as settled.

Too retrospective

Past accomplishments never become a new program.

Too grant-like

Methods overwhelm the question, intellectual direction, and broader contribution.

Too aspirational

Importance claims have no approach, feasibility bridge, or honest dependency.

Institutional context

Fit is a claim that needs evidence

Cornell, UCLA, MIT, and Washington all connect the statement to the position or institution. Treat fit as a precise claim about how the work and environment interact, not a list of names. Source B Source C Source D Source E

Verify

Find the current official source for the facility, collection, community, collaborator, curriculum, or priority.

Connect

Explain what the verified fact changes, enables, or contributes to in the proposed program.

Bound

Avoid promising a collaboration, access route, or institutional commitment that has not been established.

Revision audit

Eight tests before export

Run each pass separately. A draft can be scientifically strong and still fail prompt control, mixed-audience access, fit accuracy, or document integrity.

Prompt coverage

Pass: Every explicit requirement in the posting maps to a visible section or sentence.

Repair if: The draft answers a remembered template instead of the actual prompt.

Argument continuity

Pass: Past evidence creates the problem space for the future program without forcing a false chronology.

Repair if: The document reads as disconnected project summaries or a publication list in prose.

Evidence specificity

Pass: Important claims identify a finding, output, contribution, or other checkable evidence.

Repair if: Adjectives such as innovative, rigorous, or impactful substitute for evidence.

Future feasibility

Pass: Each direction names a question, approach, feasibility basis, and honest dependency.

Repair if: The vision is either a grant-methods dump or an aspiration with no execution path.

Independence

Pass: The draft identifies what you will carry forward, what becomes newly yours, and where collaboration is appropriate.

Repair if: The future program could be mistaken for a continuation of a mentor's agenda.

Mixed-audience access

Pass: A reader outside the subdiscipline can recover the problem, contribution, and future direction from headings and opening sentences.

Repair if: Specialized terminology is doing the work that the argument should do.

Fit accuracy

Pass: Every institution-specific claim is current, sourced, and relevant to the proposed program.

Repair if: Names, facilities, or priorities are inserted as flattery or copied between applications.

Document integrity

Pass: The final PDF follows the posting, has readable hierarchy, complete citations, accessible figures, and no clipped or hidden content.

Repair if: Formatting, file naming, or export defects make the evidence harder to evaluate.

Evidence and maintenance

Source record and limits

The web guide, PDF, and source record share one edition. The synthesis uses public university guidance to expose variation rather than erase it. Original Manusights architecture and worksheet content are CC BY 4.0; source materials retain their own status.

A
Application Materials for a Faculty Job Search
MIT Career Advising and Professional Development / Research statement section. Supports: Variation in length and structure, distinct research identity, past accomplishments, future plans, methods, and discipline-specific norms.
B
Faculty Application: Research Statement
MIT EECS Communication Lab / Structure Diagram; Identify Your Purpose; Analyze Your Audience; Skills. Supports: Wide variation across fields, the EECS-specific three-page example, past-to-future continuity, non-specialist departmental readers, posting-specific tailoring, informative headings, and feedback.
C
Research Statement
Cornell University Graduate School / What Is a Research Statement; Formatting; Organization; Writing; Future Goals. Supports: Research accomplishments, current work, future direction, realistic scope, department context, accessibility outside the subdiscipline, and Cornell's own length guidance.
D
Research Statements
UCLA Career Center / Overview and two sample structures. Supports: The UCLA 1-2 page example, discipline variation, research trajectory, future direction, institutional tailoring, and contribution-to-field framing.
E
Research Statements
University of Washington Career and Internship Center / Goals and Purpose; Content. Supports: Disciplinary variation, scholarly independence, institutional compatibility, writing quality, field consultation, tailoring, and proofreading.
F
Application Materials for Faculty Positions
UCSF Office of Career and Professional Development / Developing Faculty Application Materials; sample-material boundaries. Supports: Research statements as one component of the faculty packet, prompt-specific preparation, the value and limits of examples, and the warning not to copy sample text.

Boundary: A planning and revision framework for faculty-job research statements. It does not set a universal page length, prescribe a discipline-wide structure, evaluate a candidate, or replace the exact posting and local field conventions. Recheck the six university guidance pages after a material page change and no later than 90 days after this review. The target posting always controls the application.

Common questions

Use the posting, then the field

How long should a faculty research statement be?

Follow the posting. There is no defensible universal length. Current university guidance in this source set ranges from 1-2 pages at UCLA to 3-5 pages at MIT CAPD, while both sources note variation by discipline or application. If the posting is silent, check recent field-specific examples and local faculty guidance.

How many projects or future directions should I include?

Use the number the prompt, field, and argument can support. A strong selection shows a coherent program and enough evidence for feasibility without becoming a catalog. This guide deliberately does not prescribe a universal number of aims.

Can I use sample research statements as templates?

Use samples to study field conventions, hierarchy, and level of detail, not to copy language or inherit another candidate's argument. UCSF explicitly says its samples are useful examples, not perfect models, and warns applicants not to copy them.

How should I tailor the statement for an institution?

Start with the posting, then verify facilities, collections, communities, collaborators, teaching context, or priorities that materially affect the proposed program. Name an institutional fact only when you can explain why it changes or enables the work.

Cite this resource

Citation formats

Free to use and cite, with attribution. See the reuse policy for what you may republish.

APA: Manusights. (2026). Faculty research statement evidence map. Edition 2026.09.22-statement-1. https://manusights.com/resources/research-statement-guide
MLA: Manusights. "Faculty Research Statement Evidence Map." Manusights, 22 Sept. 2026, https://manusights.com/resources/research-statement-guide.
Vancouver: Manusights. Faculty research statement evidence map [Internet]. 2026 Sep 22. Available from: https://manusights.com/resources/research-statement-guide