Write a project scope small enough to use

A project scope is useful when it helps you decide what to do next and what to leave out. It does not need grand language. For a first undergraduate project, a short document can prevent a broad interest from expanding into several unfinished tasks. Treat the scope as a draft for discussion with your mentor, not as permission to collect data or begin a new procedure.

Choose a question with a boundary

Write the question in one sentence. Then add what the project will not attempt to answer. An illustrative literature project might compare how a small set of papers defines a concept, without trying to establish which definition is universally correct. This boundary does not make the work unimportant. It makes the proposed contribution easier to examine and the next task easier to identify.

The Early Experiences Lab student page describes developing research questions through classes, lab work and discussion, followed by mentor refinement. That is one lab’s guidance, not a universal proposal format. The broader editorial lesson is to bring a question that can be improved in conversation rather than waiting until you believe it is perfect.

Define the first visible output

Choose something the mentor can review early: a reading map, a brief methods comparison, an annotated outline or another suitable product. Ask which format is useful for this team. “Make progress on the project” is difficult to assess. “Bring a draft comparison of three approaches to the next meeting” is clearer, provided that the mentor agrees the task is appropriate and feasible.

State how you will know the first output is ready for discussion. It need not be polished. It should make your reasoning and uncertainties visible. For instance, an outline can include questions beside each section instead of hiding gaps behind confident prose. Keep source references with your notes so that the mentor can distinguish an idea from the evidence supporting it.

List dependencies before promising dates

Some tasks depend on training, access, materials, feedback or formal approval. Write those dependencies beside the task they affect. Do not schedule a procedure as if it can begin immediately when a required condition is unresolved. Ask the mentor which activities can safely and appropriately proceed while you wait, such as reading public material or refining a question.

Include a clear boundary around confidential or unpublished information. Use the team’s approved storage and sharing arrangements. Do not put participant information, restricted data or unpublished results into a personal planning tool without authorization. Your one-page scope can describe the work at a high level while the project itself remains in the appropriate research environment.

Agree how the scope can change

Research questions evolve. Set a point for reviewing whether the first output still makes sense and whether the question needs narrowing. Record changes with a date and a short reason so that an older plan is not mistaken for the current agreement. This journal’s scope format is an optional planning aid. It is not a University application template, ethics approval, course contract or replacement for the mentor’s instructions.