Treating Your PhD Proposal as a Binding Research Contract

Can you turn scope into a contract?

When a supervisor keeps tacking on new deliverables, the easiest reflex is to treat each request as a favor you’ll grant because “they’re the advisor.” That mindset keeps the conversation in a gray area where “yes” feels polite but the workload silently explodes. A more powerful way to see the problem is to treat the original research plan as a contract between you and your supervisor. A contract isn’t a legal document; it’s a mutual agreement that spells out what will be delivered, by when, and under what conditions the agreement can be revised.

Seeing your proposal as a contract does three things:

• It forces you to ask “What does this change cost me?” before you answer.
• It gives you a concrete reference point when the supervisor says, “I need another dataset.”
• It creates a language—“scope,” “budget,” “revision”—that both of you can use without sounding confrontational.

From here, every new request can be evaluated against the contract’s terms. If the request fits within the agreed‑upon budget of time, resources, and ethical approvals, you can say yes. If it doesn’t, you have a legitimate, model‑based reason to push back.

Critical warning: If you add more than 20 % extra work you risk missing the submission date.

What happened when you kept saying yes?

Last month a second‑year psychology PhD student was asked to collect data in a neighboring country and then build a second dataset from scratch. The original proposal had already slipped once because of a delayed ethics review. The student’s first instinct was to reassure the supervisor: “Sure, I’ll add the new country.” The supervisor smiled, added a third country two weeks later, and then asked for a new qualitative interview guide.

Within three weeks the student was juggling three field trips, two IRB amendments, and a spreadsheet that doubled in size every day. The original milestones—literature review, pilot analysis, chapter 3 draft—were pushed back. When the student finally raised the issue, the supervisor replied, “We’ll figure it out later.” The student felt trapped, exhausted, and uncertain whether it was even legitimate to claim the scope was infeasible.

The failure wasn’t a lack of diligence; it was the absence of a clear boundary framework. The student had no structured way to say, “My current plan can’t absorb this without jeopardizing the defense.” Instead, they kept saying yes, hoping the workload would magically compress.

Critical warning: You have only 2 weeks left before your defense deadline.

How a simple “boundary‑budget” model reshaped that conversation

The turning point came when the student discovered a “boundary‑budget” model in a graduate‑student workshop. The model is essentially a three‑column spreadsheet:

1. List every deliverable (original and new).
2. Assign an estimated time cost in hours.
3. Mark whether the item fits within the pre‑agreed “budget” (e.g., 300 hours total for data collection).

When the supervisor proposed the second country, the student filled in the spreadsheet. The new field trip added 120 hours of travel, translation, and data cleaning. The total rose to 420 hours, well above the 300‑hour budget. The student then presented the numbers, saying, “According to our contract, we have 300 hours allocated for data collection. Adding the second country pushes us 40 % over budget, which means we’ll have to drop or delay another milestone.”

The supervisor, seeing the concrete numbers, agreed to postpone the third country and to let the student keep the original timeline for chapter 3. The conversation shifted from “Can you do more?” to “How can we stay within the budget?” The model gave the student a factual basis to negotiate, and it gave the supervisor a clear picture of the trade‑offs.

The model’s power lies in its simplicity: it turns vague “more work” into a quantifiable breach of the contract, which is far easier to discuss than feelings of overwhelm.

How does this model work for different kinds of research?

Not every graduate project looks like a cross‑country data collection. Below are three common scenarios and how the boundary‑budget model adapts.

Lab‑based experimental thesis

Typical deliverables: number of participants, number of experimental conditions, analysis scripts, manuscript drafts. The budget column might be “person‑hours of lab time” or “software licenses.” If a supervisor asks for an extra condition, you plug the additional setup time into the spreadsheet. If it exceeds the budget, you propose either merging conditions or extending the data‑collection phase.

Capstone project with a community partner

Deliverables often include needs assessments, intervention materials, and evaluation reports. The budget may be “total community‑engagement hours.” When the partner requests a new workshop series, you calculate the prep and delivery hours. If the sum goes beyond the agreed budget, you suggest scaling back the number of workshops or reallocating existing hours.

Part‑time master’s dissertation while working full‑time

Time is the scarcest resource. The contract’s budget is “available evenings per week.” A supervisor might ask for an extra literature review chapter. You estimate the additional reading and writing hours, then compare to the weekly budget. If it doesn’t fit, you negotiate a later submission of that chapter or a reduction in other sections.

Across all three contexts the steps stay the same: list, estimate, compare. The language of “budget” and “scope” remains consistent, so you can reuse the same spreadsheet template throughout your program.

One step you can take tonight to set a clear boundary

Grab a piece of paper or open a new spreadsheet and complete the following checklist. It takes about ten minutes, but it gives you a concrete tool for your next meeting.

1. Write down every deliverable that is currently on your to‑do list, including the ones you just heard about.
2. Next to each item, note the estimated hours you’ll need to finish it. Be generous; add a 10 % buffer for unexpected delays.
3. Sum the hours and compare the total to the amount you originally agreed on in your proposal (the “budget”).
4. If the total exceeds the budget, highlight the newest items in red.
5. Draft a short email that references the contract, shows the numbers, and proposes a specific adjustment (e.g., “I can keep the original two datasets if we drop the third country, which would bring the total back to 300 hours.”).

Send that email before your next scheduled meeting. By presenting the boundary‑budget before the conversation, you force the discussion to focus on numbers, not personalities. The supervisor can either accept the adjustment or suggest an alternative that stays within the budget.

FAQ

Is it legitimate to say the current scope is not feasible?

Yes. Your proposal is a formal agreement that outlines what is expected for a successful defense. If new tasks push you beyond the agreed‑upon time or resource budget, you are within your rights—and indeed your responsibility—to flag the infeasibility. Cite the specific clause in the proposal (e.g., “Section 3.2 limits data‑collection to two sites”) and back it up with the boundary‑budget numbers you prepared.

How do I phrase a boundary without sounding confrontational?

Use “I” statements that focus on the contract, not the person. For example: “I’ve updated the scope‑budget table and see that adding a third country would increase total data‑collection time by 120 hours, which exceeds our agreed 300‑hour limit. To stay on track for the defense, I suggest we keep the two‑country design and allocate those extra hours to deeper analysis.” This frames the issue as a logistical problem, not a personal disagreement.

What if the supervisor insists anyway?

When the supervisor pushes back, refer back to the contract and the numbers. Ask, “What part of the contract can we adjust to accommodate this request?” If the supervisor still refuses a compromise, involve a third party—such as the graduate program director or a departmental ombudsperson—who can mediate based on the documented budget.

Decision matrix for evaluating new deliverable requests

Use this matrix during meetings. Fill in the “Time impact” column with your own estimates, then follow the “Action” column to decide quickly.