The doctoral committee returned your synopsis — again — and the next DRC meeting is months away, which means the real cost is not embarrassment but calendar: a rejected synopsis burns a full committee cycle, and a second rejection burns a semester. Here is the good news hiding in that bad afternoon: committee rejections are not mysterious. Read enough DRC minutes and the objections sort into four diagnosable patterns, each with a specific repair. This guide walks you through diagnosing yours, fixing the document, and returning with a synopsis the committee can approve — plus the resubmission protocol that makes approval the path of least resistance. Tesify can carry the structural work; the diagnosis below is yours either way.
First: Get the Objection in Writing, and Read What It Actually Says
Before rewriting a single line, obtain the committee’s recorded remarks — the DRC minute, the review sheet, or at minimum your supervisor’s written summary. Scholars routinely repair the wrong thing because they worked from a corridor recollection of the meeting rather than the recorded objection. Then read it the way you will later read examiner reports: not for tone, but for category. Almost every synopsis rejection is one of these four.
Pattern 1: “The Problem Is Not Clear” — the Vague-Problem Rejection
The committee could not restate, in one sentence, what gap your research fills. The tell-tale remarks: “objectives are too general”, “what exactly is the research question?”, “this is a topic, not a problem”. The fix is structural, not verbal: rebuild the problem statement as a four-move argument — the ideal situation, the documented reality, the precise gap, and the consequence of leaving it unstudied — and then derive every objective from a sentence in that argument, deleting any objective that traces to none. Polishing the language around an undefined problem is the classic failed second attempt; committees notice the same hole in nicer clothes.
Pattern 2: “Too Broad / Not Feasible” — the Scope Rejection
The committee believed the problem is real but not that you can study it in the time, with the access and resources you have. Tell-tales: “narrow the scope”, “how will you access this data?”, “this is three PhDs”. The fix is subtraction plus evidence: cut the populations, variables or comparisons that are not load-bearing, and for whatever survives, show feasibility concretely — the named dataset you can reach, the pilot access already secured, the instrument that exists. A scope the committee can see being finished is half an approval; if the topic itself was overweight from the start, recalibrate against the discipline-wise topic guide before rebuilding.
Pattern 3: “Literature Is Inadequate” — the Thin-Grounding Rejection
The committee suspected you have not read enough to know whether your gap is real. Tell-tales: “recent literature missing”, “has this not been done already?”, “review is descriptive, not critical”. The fix is a genuine, documented search: re-run your literature sweep including the most recent years and prior Indian theses (your committee members know what sits in Shodhganga — search it before they do), rebuild the review section around themes and the gap they surround rather than paper-by-paper summaries, and make the gap claim calibrated and checkable: “a search of X and Y on [date] found work on A and B but none addressing C”. Every source cited with full, verifiable references — a synopsis whose references are sloppy invites exactly this rejection, and the formatting patterns are in the APA guide.
Pattern 4: “Method Does Not Match the Questions” — the Design Rejection
The committee read your questions, read your proposed methodology, and could not see how the second answers the first. Tell-tales: “how will this design address objective 3?”, “sample cannot support these conclusions”, “analysis plan is missing”. The fix is a mapping exercise: build a simple table — each research question against the data that answers it, the source of that data, and the analysis that converts one into the other — and rewrite the methodology section from that table. Any question with an empty row gets a redesigned method or gets cut; any method serving no question gets deleted. This table, incidentally, is the same artefact that will later anchor your pre-submission presentation and viva defence — building it now pays twice.
The Resubmission Protocol That Wins Committees Over
Committees approve resubmissions that make approval easy. Three moves. First, the response note: a one-page table listing every recorded objection, what you changed in response, and where in the revised synopsis the change lives. This is the single highest-leverage document in the entire process — it converts the committee’s job from re-reviewing a document to verifying repairs. Second, the pre-clearance pass: walk the revised synopsis through your supervisor, and where practice allows, informally past the committee member who raised the sharpest objection. Arriving at the DRC with your toughest critic already satisfied changes the meeting’s chemistry. Third, structural cleanliness: the revised document itself must be immaculate — consistent formatting, complete references, objectives numbered and traceable. A synopsis that looks controlled signals a scholar who is; the full section-by-section construction is in the PhD synopsis guide.
This is also where the calendar math argues for tooling. Between DRC cycles you have weeks, and the repair work is structural: rebuilding a problem statement, restructuring a literature section, keeping fifty references consistent through every revision. In Tesify, the synopsis lives as a structured document where sections, objectives and citations stay coherent while you rework them — and the AI assistance helps you sharpen and reorganise your argument without ever writing it for you, which is the only kind of help an integrity-compliant scholar can use. Scholars who spend the cycle fighting Word formatting resubmit tired; scholars who spend it on substance resubmit approvable.
What Not to Do
Three tempting mistakes, each observed often. Do not relitigate the rejection in the resubmission — a response note that argues the committee was wrong invites them to prove they were not. Concede what is repairable, repair it, and save genuine disagreements for a conversation your supervisor mediates. Do not change the topic silently: if the fix requires a real pivot, flag it through your supervisor before the meeting; committees dislike surprises more than they dislike pivots. Do not pad: a rejected 20-page synopsis does not become approvable at 40 pages — it becomes longer. Every pattern above is fixed by precision, not volume.
The next DRC meeting is coming either way. Arrive with the repaired synopsis, not the same one in better formatting. Tesify structures your problem statement, objectives, literature and references into one coherent, revisable document — written by you, organised with help. Used by 9,000+ students. Rebuild your synopsis in Tesify.
FAQ: Synopsis Rejection and Resubmission
What should I do first after a synopsis rejection?
Get the objections in writing — DRC minute, review sheet, or supervisor’s written summary — and categorise them into the four patterns before touching the document. Repairing from memory repairs the wrong thing.
How many times can I resubmit a synopsis?
Set by your university’s ordinance and DRC practice, not national rule. Ask your research section for the limit and the next meeting date in writing; the calendar is usually the binding constraint.
How long does a rejection delay the PhD?
At least one committee cycle — often a semester, since DRC meetings are periodic. That asymmetry is why the resubmission must close every recorded objection: a second rejection doubles the damage.
Is a rejected synopsis a bad sign about my PhD prospects?
No — it is an early, cheap correction from the people who will eventually examine the work. The scholars in trouble are those whose weak synopses were approved and who meet these objections at pre-submission instead.
Should I change my topic after rejection?
Only if the diagnosis says the problem is unfixable at feasible scope — most rejections are repairs, not replacements. If a pivot is genuinely needed, route it through your supervisor before the next meeting, never as a surprise.
What is a response note and is it required?
A one-page table: each recorded objection, your change, and its location in the revision. Rarely formally required, almost always decisive — it converts the committee’s task from re-review to verification.
Can AI tools rewrite my synopsis for me?
Submitting AI-generated research framing as your own violates integrity norms and collapses at the first committee question. The compliant use is structural: organising, sharpening and formatting the argument you build — which is exactly how Tesify assists.
My supervisor and the committee disagree — whose direction do I follow?
Surface the conflict explicitly with your supervisor and let them broker it before the meeting; a synopsis caught between authorities fails both. The committee’s recorded requirements ultimately gate approval, so alignment must be reached, not assumed.
Does the synopsis bind what my thesis must contain?
It sets the approved direction; reasonable evolution is normal and expected, with significant changes routed through your Research Advisory Committee. Document approved changes — the synopsis-to-thesis drift question resurfaces at the viva.
What single change most improves approval odds?
The four-move problem statement with objectives that trace to it line by line. Committees forgive many weaknesses in a synopsis whose problem is unmistakably clear — and forgive nothing in one whose problem is not.