Progress Seminar
Session at a Glance
Mid-semester oral presentation of work-in-progress to a faculty review panel; demonstration of research progress; structured feedback to guide the final writing and revision phase
12-minute presentation + 10–12 minutes panel Q&A + structured written feedback; panel evaluates progress, methodology execution, and readiness for the final phase
2 hrs Prep Workshop + Individual Seminar Slot
Progress Seminar — formal checkpoint on capstone execution
Learning Objectives
By the end of this session, you will be able to:
- Construct a concise, honest work-in-progress presentation that communicates what you have accomplished, what you are finding, what challenges you have encountered, and what remains to be done — distinguishing the progress seminar from the proposal defence (which argued for a plan) and the final defence (which argues for completed research)
- Present incomplete or preliminary findings with appropriate confidence and appropriate caution — acknowledging the provisional nature of results while demonstrating that the research trajectory is sound and the remaining work is clearly defined
- Anticipate the questions a progress review panel is likely to ask — focusing on methodology execution fidelity, data quality and sufficiency, preliminary findings' credibility, timeline feasibility, and readiness to transition to the writing phase
- Receive, interpret, and integrate mid-course feedback — distinguishing between feedback that requires immediate action (methodological corrections), feedback that shapes the writing phase (emphasis, structure, argument), and feedback that is advisory rather than directive
- Develop a concrete post-seminar action plan that translates panel feedback into specific revisions, identifies the highest-priority writing tasks, and confirms that the remaining timeline is realistic given the current state of the research
Week 20 Planner
This week is structured around the progress seminar event. Preparation and rehearsal precede the seminar; the post-seminar work converts feedback into an action plan for the final writing phase.
| Time / Phase | Activity | Details | Mode |
|---|---|---|---|
| 0:00–0:25 | Seminar Prep Workshop | Progress seminar structure and expectations; how it differs from proposal defence and final viva; presenting incomplete work; anticipating panel questions; common mistakes | Whole class |
| 0:25–0:55 | Structured Rehearsal | Each student delivers an 8-minute condensed version to a peer. Peer provides timed feedback using the structured rubric: was progress clear? Were challenges honestly presented? Were preliminary findings appropriately caveated? Was the remaining work plan realistic? | Pairs |
| 0:55–1:15 | Anticipated Questions Exercise | For your current project state, write the 5 hardest questions the panel could ask. Draft responses. Exchange with a partner — they find the question you didn't anticipate. Focus on: methodology deviations, data quality concerns, timeline feasibility, and preliminary findings' limitations. | Pairs |
| 1:15–1:30 | Break | — | — |
| 1:30–1:50 | Panel Logistics & Q&A Strategy | Seminar schedule; panel composition; evaluation criteria; responding to critical feedback professionally; distinguishing between "fix this" and "consider this" | Whole class |
| 1:50–2:00 | Final Q&A | Open questions; anxiety management; what happens after the seminar | Whole class |
| Day 2–3 | Individual Seminar Slots | 12-minute presentation + 10–12 minutes panel Q&A. Panel provides immediate verbal feedback and written feedback within 48 hours. | Individual |
| Day 4–5 | Post-Seminar Action Planning | Translate feedback into a concrete action plan. Identify revisions, prioritise writing tasks, update the Weeks 20–30 project plan based on panel input. Schedule follow-up supervisor meeting. | Individual |
1. The Progress Seminar — Purpose and Positioning
The progress seminar is the midpoint checkpoint of the capstone execution phase. It sits between the proposal defence (Week 8 — "Here is what I plan to do") and the final viva (Week 30 — "Here is what I did and what it means"). The progress seminar answers a different question: "Here is what I have done so far, what I am finding, what challenges I have encountered, and what remains — am I on track to complete a quality capstone?"
The progress seminar is a formal oral presentation and Q&A session in which a student presents their work-in-progress to a faculty review panel. Unlike the proposal defence (which evaluates a plan) or the final viva (which evaluates completed research), the progress seminar evaluates execution fidelity and trajectory: is the student executing the approved methodology? Is the data of sufficient quality? Are preliminary findings credible? Have challenges been managed appropriately? Is the remaining work feasible within the timeline? The outcome is formative feedback intended to strengthen the research before the intensive writing phase — the panel identifies problems NOW, while there is still time to address them.
1.1 Three Seminars, Three Questions
| Dimension | Proposal Defence (Week 8) | Progress Seminar (Week 20) | Final Viva (Week 30) |
|---|---|---|---|
| Core Question | "Is this a well-designed, feasible, and worthwhile study?" | "Is the study being executed as designed? Is it on track? What needs attention before the final phase?" | "Does the completed study meet the standards for a capstone? Does the student understand their research and its contribution?" |
| What You Present | A plan — what you WILL do, why, and how | Work-in-progress — what you HAVE done, what you are FINDING, what REMAINS | Completed research — what you DID, what you FOUND, and what it MEANS |
| Tense of Presentation | Future: "This study will employ..." "The sample will comprise..." | Mixed — past for completed work, present for ongoing analysis, future for remaining tasks: "I have collected... The preliminary analysis suggests... I will complete..." | Past: "This study employed..." "The findings revealed..." |
| Panel's Primary Concern | Design quality and feasibility | Execution fidelity, data quality, trajectory, and timeline realism | Contribution, rigour, argumentation, and the student's intellectual ownership |
| Best Possible Outcome | "Approved — this is a strong plan. Proceed." | "You're on track. Your data can answer your RQs. Here's how to strengthen the writing phase." | "Pass with distinction — this is a substantial contribution." |
| Worst Possible Outcome | "Major revision required — fundamental problems with the design." | "Your data cannot answer your RQs. Significant additional data collection or methodological rework is required." | "The dissertation does not demonstrate the required level of competence." |
By Week 20, you have invested 20 weeks in your capstone and have 10 weeks remaining. The progress seminar is the last formal checkpoint before the final submission. Feedback received here can be incorporated into the writing phase; feedback received at the final viva cannot. Treat the progress seminar as your most valuable feedback opportunity — the panel's observations now can prevent the disappointment of discovering fundamental problems during the final defence, when it is too late to address them. The student who listens carefully, takes detailed notes, and acts systematically on progress seminar feedback produces a substantially stronger dissertation than the student who treats it as a bureaucratic hurdle to be survived.
2. Structuring the Work-in-Progress Presentation
The progress seminar presentation is a distinct communication genre. It is NOT a shortened proposal defence (presenting the plan again). It is NOT a premature final viva (pretending findings are complete). It is a status report with intellectual depth — showing the panel what you have accomplished while being transparent about what is incomplete and what challenges remain.
2.1 The 10-Slide Progress Seminar Structure
| Slide | Content | Time | What to Include — and What to Leave Out |
|---|---|---|---|
| 1 | Title & Context | 0:30 | Working title, your name, supervisor. One sentence reminding the panel of your topic: "My capstone examines [problem] in [context] using [approach]." Don't re-present the full proposal — the panel has read it or has a summary. A single sentence of context is sufficient. |
| 2 | Recap — RQs in One Slide | 0:45 | Your RQs — exactly as approved (or noting any approved modifications). This anchors the presentation: everything that follows is about progress toward answering THESE questions. Don't re-justify the RQs — the proposal already did that. State them and move on. |
| 3 | Methodology at a Glance | 1:00 | A single slide summarising: design, sample (planned vs. achieved), instruments, and analytical approach. The purpose is to orient the panel to what you set out to do — so they can evaluate whether you are doing it. Flag any MAJOR deviations from the proposal here — don't bury them in later slides. |
| 4 | Execution Status — What Has Been Done | 1:30 | A clear, honest status report. Data collection: what % complete? Sample achieved vs. planned? Any quality issues? Analysis: what % of planned analyses are complete? What is done vs. in progress vs. not yet started? Artefact development (BCA/DSR): current state of the artefact. Be specific. "Data collection: 187 of 200 planned surveys complete (94%). Response rate: 31%. Quality check: 12 incomplete responses excluded; final n = 175." |
| 5–7 | Preliminary Findings | 4:00 | The core of the presentation. For each RQ: what have you found so far? Present descriptive statistics, key analyses, preliminary themes. Include appropriate caveats: "These are preliminary findings based on [n = X / analysis in progress]. The final analysis will additionally include [planned additions]. These findings should be interpreted as indicative pending the complete analysis." For qualitative: present your thematic map and 1–2 themes with supporting quotes. For BCA/DSR: present your evaluation framework and preliminary results. |
| 8 | Challenges & Deviations | 1:00 | Be honest. What did not go according to plan? What challenges did you encounter? How did you address them? The panel will find out anyway — presenting challenges proactively demonstrates professionalism. For each challenge: what was the issue, what was its impact, and what was your response? "I planned 20 interviews but completed 16. My analysis suggests saturation was reached at interview 14 — here is my saturation tracking evidence." |
| 9 | Remaining Work & Timeline | 1:15 | What remains to be done? Present a realistic timeline for Weeks 20–30. Identify the critical path — what must be completed for each subsequent phase to begin. Flag any concerns about feasibility: "My analysis is 2 weeks behind my original schedule. I have adjusted by [specific adjustment]. I am confident of completion by Week 29, providing one week of buffer before submission." |
| 10 | Questions for the Panel | 0:30 | This is distinctive to the progress seminar: present 1–2 specific questions you would like the panel to address. "I am considering two approaches to [specific methodological decision] — I would value the panel's guidance." "My preliminary findings suggest [pattern] — I would appreciate feedback on whether this pattern is worth developing further or is tangential to my RQs." This transforms the Q&A from interrogation to consultation. |
2.2 Presenting Incomplete Work — Confidence with Appropriate Caution
The most psychologically challenging aspect of the progress seminar is presenting work that is not finished. Students often respond by either overclaiming (presenting preliminary results as if they were final) or underclaiming (apologising so frequently that the panel loses confidence in the work). The balance is to present what you have found with appropriate confidence grounded in your methodology while being transparent about the provisional nature of the analysis.
| Instead of (Overclaiming)... | Or (Underclaiming)... | Try (Appropriate Confidence)... |
|---|---|---|
| "My regression analysis conclusively demonstrates that autonomy is the strongest predictor of satisfaction." | "I ran a regression but I'm not sure if I did it right and the results are probably wrong and I need to check everything..." | "Preliminary regression analysis on 175 complete responses suggests that autonomy is emerging as the strongest predictor of satisfaction (β = 0.31, p < .001), consistent with the hypothesised relationship. I am currently completing assumption diagnostics and will test the robustness of this finding with [additional analyses]. If confirmed, this would suggest [tentative implication]." |
3. What the Panel is Evaluating — Five Dimensions of Progress
The progress seminar panel evaluates your capstone across five dimensions. Understanding what they are looking for — and how they assess each dimension — enables you to structure your presentation and preparation to address their concerns directly.
| Dimension | What the Panel Asks Themselves | Evidence You Should Present | Red Flags the Panel is Watching For |
|---|---|---|---|
| 1. Execution Fidelity | "Is the student executing the methodology they proposed? If not, are deviations justified and documented?" | Clear comparison of planned vs. actual methodology; explicit acknowledgement of deviations with justification; the retrospective review (Week 18) should inform this section | Significant unacknowledged deviations; methodology that has drifted from the proposal without explanation; describing the planned methodology as if it were executed |
| 2. Data Quality & Sufficiency | "Is the data of sufficient quality and quantity to answer the RQs? Has the student assessed data quality systematically?" | Sample characteristics (achieved vs. planned); response rates; data screening results (missing data, outliers, reliability); for QUAL: evidence of saturation or information power; for BCA: dataset characteristics and limitations | Data that is clearly insufficient to answer RQs; no data quality assessment; ignoring missing data or outliers; sample that differs substantially from target population with no acknowledgement |
| 3. Analytical Progress & Credibility | "Are the preliminary findings credible? Has analysis been conducted systematically? Does the student understand what they have found so far?" | Clear presentation of analytical approach; preliminary results with appropriate caveats; evidence of systematic analysis (not cherry-picking); for QUAN: assumption checks; for QUAL: coding evidence and theme development logic | Overclaiming from preliminary data; analysis that appears superficial or selective; inability to explain analytical decisions during Q&A; findings that don't connect to RQs |
| 4. Challenge Management | "Has the student encountered challenges? Have they managed them professionally? Have they sought help appropriately?" | Honest identification of challenges; description of response strategies; evidence of problem-solving; appropriate escalation when needed; supervisor awareness of issues | No challenges reported (suggests either lack of reflection or lack of honesty); challenges that clearly should have been escalated but weren't; blaming external factors without taking responsibility for solutions |
| 5. Timeline Feasibility | "Can this student complete a quality capstone within the remaining 10 weeks? Is their plan realistic? Do they understand what remains?" | Detailed remaining work plan; realistic task estimates with buffer; awareness of dependencies; honest assessment of risks; contingency plans for likely delays | Overly optimistic timeline with no buffer; significant remaining work with insufficient time; no contingency planning; unclear understanding of what the writing phase actually requires |
A student who presents flawless progress with no challenges, perfect data, and unequivocal preliminary findings is either (a) unusually fortunate, (b) not being fully transparent, or (c) not reflective enough to recognise the limitations of their work. Panels are experienced researchers — they know that every research project encounters challenges. A presentation that acknowledges difficulties honestly and demonstrates professional responses to them inspires more confidence than a presentation that pretends everything went perfectly. The panel's trust is earned through transparency, not through performance of success.
4. After the Seminar — From Feedback to Action
The progress seminar's value is realised in the weeks after the presentation — when panel feedback is systematically translated into revisions, refinements, and a strengthened final-phase plan. The worst outcome is not negative feedback; it is feedback that is noted, filed, and never acted upon.
4.1 Classifying and Prioritising Panel Feedback
| Feedback Type | What It Sounds Like | Required Response | Timeline |
|---|---|---|---|
| Critical — Action Required | "Your sample size of 40 is insufficient for the regression you're planning with 6 predictors. You need at least 98 based on Green's rule. This is a fundamental issue." | Address immediately. This feedback identifies a problem that, if unaddressed, will undermine your findings. Meet with your supervisor within 48 hours to develop a plan. Document the issue and your response in your methodology chapter. | 1–2 weeks |
| Important — Strengthen Before Submission | "Your thematic analysis would benefit from a clearer articulation of your coding process. The themes are interesting, but I want to see more evidence of systematic coding — perhaps include a codebook excerpt or a coding tree in an appendix." | Incorporate into the writing phase. This feedback strengthens your dissertation but does not require fundamental rework. Add to your revision checklist. Address before submitting the complete draft to your supervisor. | 2–4 weeks |
| Advisory — Consider at Your Discretion | "You might consider framing your discussion around institutional theory rather than resource-based view — it could provide a richer lens for your findings." | Evaluate the suggestion. Discuss with your supervisor. If it strengthens the dissertation, incorporate it. If it would require substantial rework for marginal benefit, acknowledge the suggestion and explain (in your discussion) why your chosen framework is appropriate. You are not obligated to implement every suggestion. | At your discretion |
4.2 The Post-Seminar Action Plan
| Panel Feedback | Type | Specific Action | Chapter(s) Affected | Priority (H/M/L) | Target Completion | Status |
|---|---|---|---|---|---|---|
| "Sample size justification needs power analysis — n=140 is below Green's rule for 5 predictors" | Critical | Run G*Power analysis; if n insufficient, acknowledge as limitation; consider reducing predictors; document in Ch3 methodology and Ch6 limitations | Ch 3, Ch 6 | High | Week 21 | ☐ |
| "Your interview quotes are compelling but need more analytic commentary — the researcher's voice should lead" | Important | Revise each thematic subsection: reduce quote length, expand analytic commentary, ensure researcher voice leads each section | Ch 4 | Medium | Week 22 | ☐ |
| "Consider adding a brief comparison with Kumar (2024) — their recent work is directly relevant to your RQ2" | Advisory | Read Kumar (2024); assess relevance; if adding, integrate into Ch2 lit review and Ch5 discussion | Ch 2, Ch 5 | Low | Week 23 | ☐ |
| (Your feedback item 1) | ☐ | |||||
| (Your feedback item 2) | ☐ |
Students often react to panel feedback emotionally — defensiveness ("they didn't understand my approach") or despair ("everything is wrong"). Neither response is productive. Instead, treat feedback as data to be analysed: (1) transcribe all feedback within 24 hours while it is fresh; (2) classify each item by type and priority; (3) identify patterns — are multiple panel members raising the same concern? A concern raised independently by two panel members deserves more weight than a suggestion made by one; (4) discuss your classification with your supervisor — they can help you distinguish between critical, important, and advisory feedback; (5) build the action plan. This analytical approach transforms emotional reactions into systematic improvement.
Think Deeper — Cross Questions
Discuss in pairs before sharing with the class.
Draft the opening two sentences of your progress seminar presentation. Now compare with the opening of your proposal defence (if you remember it). How are they different? What does this difference reveal about the distinct purposes of the two presentations — one arguing for a plan, the other reporting on execution?
You are preparing Slide 8 (Challenges & Deviations). Identify the most significant challenge or deviation in your capstone. Write the bullet points you would put on this slide. Now: role-play as a panel member. What is the hardest follow-up question you could ask about this challenge? How would you answer it?
During your progress seminar, a panel member says: "Your preliminary findings are interesting, but I'm concerned that your sample — predominantly young, urban, English-speaking professionals — cannot answer RQ3, which asks about 'Indian consumers' broadly. Your findings may only apply to a narrow demographic." This is a legitimate concern. Draft your response — one that acknowledges the limitation honestly, explains what your data CAN speak to, and does not overclaim generalisability.
After the seminar, you receive contradictory feedback: one panel member praises your thematic analysis as "rich and well-structured" while another comments that the analysis "needs more systematic coding evidence." How do you interpret this? Is it genuinely contradictory, or are the panel members addressing different aspects of your analysis? What process would you follow to determine whether and how to act on both comments?
Quick Check — Progress Presentation Diagnosis
Diagnose the problem with each progress seminar approach.
1. A student's progress seminar devotes 5 of their 12 minutes to re-presenting their proposal — the problem statement, the RQs justification, the literature gap, and the theoretical framework in detail. Preliminary findings get 2 minutes. Challenges get zero mention.
2. A student's Slide 4 (Execution Status) says: "Data collection: complete. Analysis: ongoing. Preliminary findings: positive." No numbers, no specifics, no percentages, no sample characteristics.
3. A student's presentation has no slide on challenges or deviations. When asked during Q&A whether everything went according to plan, the student says: "Yes, I followed my methodology exactly as proposed." The panel later discovers (from the written progress report) that the student changed their sampling strategy from stratified random to convenience sampling.
4. After receiving critical feedback on their methodology, a student responds during Q&A: "That's how my supervisor told me to do it." The panel member asks a follow-up question about the methodological reasoning; the student repeats: "My supervisor approved this approach."
Knowledge Check — Interactive Quiz
Test your understanding of the progress seminar.
Q1. How does the core question of the progress seminar differ from the proposal defence?
Q2. What proportion of a progress seminar presentation should be devoted to preliminary findings (vs. re-presenting the proposal)?
Q3. When presenting preliminary findings, what is the appropriate balance between confidence and caution?
Q4. A panel member identifies a significant methodological concern during your progress seminar. What is the BEST way to respond?
Q5. What is the most important outcome of the progress seminar?
Lab Activity — Progress Seminar Preparation
Part A: Build Your Progress Seminar Slide Deck (45 min)
- Create your presentation following the 10-slide structure (Section 2.1). Allocate time strictly: 12 minutes total. Rehearse each slide against the recommended timing.
- Apply the "execution focus" test: for each slide, ask "Is this about what I HAVE DONE, or what I PLANNED to do?" If a slide is primarily about the plan, cut it. The proposal was approved at Week 8. The panel needs to see execution.
- For preliminary findings slides: include appropriate caveats. Use language like "preliminary analysis suggests," "emerging pattern," "pending confirmation with complete dataset."
Part B: Anticipate and Prepare for the Hardest Questions (30 min)
Write the 5 hardest questions the panel could ask about your current project state. For each: draft a response that is honest, acknowledges limitations where appropriate, and demonstrates professional engagement with the concern.
| # | Hardest Question | Dimension (Section 3) | Your Draft Response |
|---|---|---|---|
| 1 | |||
| 2 | |||
| 3 | |||
| 4 | |||
| 5 |
Part C: Timed Rehearsal with Structured Peer Feedback (35 min per person)
- Present your full 12-minute seminar to a peer. Peer times strictly and signals at 10 minutes (2-minute warning) and 12 minutes (must stop).
- Peer provides feedback using the structured rubric (1–5 scale): execution status clarity, preliminary findings credibility, challenge honesty, timeline realism, overall readiness.
- Peer asks 3 unscripted panel-style questions. Student responds without preparation. This simulates the Q&A experience.
Part D: Post-Seminar Action Plan (if seminar completed) (20 min)
Complete the post-seminar action plan template (Section 4.2). Classify all feedback by type. Identify the 3 highest-priority actions. Update your Weeks 20–30 project plan based on panel input.
Exit Ticket
Submit after your progress seminar.
- Submit your slide deck. After rehearsal, did your presentation fit within 12 minutes? If not, what did you cut?
- What was the hardest question your peer asked during the mock Q&A? How did you respond?
- What is the most significant gap between your proposal's planned methodology and your actual execution? How did you present this in your seminar?
- Submit your post-seminar action plan (if seminar completed). What are your 3 highest-priority actions?
- On a scale of 1–10: How confident are you that you can complete a quality dissertation within the remaining 10 weeks? If below 7, what is the single biggest barrier?
Key Takeaways — Week 20
The panel has already approved your plan. They need to see what you have DONE, what you are FINDING, and whether you are on TRACK. Devote 60–70% of your presentation to execution status and preliminary findings. A single slide is sufficient for the proposal recap.
Every research project encounters challenges. Presenting yours honestly — with evidence of professional responses — builds more credibility than pretending everything went perfectly. The panel will discover unacknowledged deviations, and the discovery damages trust.
The value of the progress seminar is realised in the weeks after the presentation. Classify feedback by type and priority. Build an action plan. Discuss with your supervisor. The worst outcome is feedback that is heard, appreciated, and never acted upon.
The progress seminar at Week 20 is the final formal checkpoint before the dissertation submission at Week 30. Feedback received here can be incorporated. Feedback received at the final viva cannot. Treat every panel observation as valuable data that can strengthen your final submission.
Facilitator Notes
Preparation Checklist
- Constitute the progress seminar panels at least one week in advance. Include at least one panel member familiar with the student's proposal — continuity between proposal defence and progress seminar enables evaluation of execution fidelity. Brief panel members on the five evaluation dimensions (Section 3).
- Prepare the progress seminar schedule: 12-minute presentation + 12-minute Q&A + 5-minute panel deliberation + 5-minute buffer = ~35 minutes per student. Communicate the schedule at least 3 days in advance. Panel chairs should enforce time limits rigorously — a presentation that runs to 18 minutes is unfair to subsequent presenters and reduces Q&A time.
- Prepare a structured feedback form aligned with the five evaluation dimensions. Panel members complete the form during the presentation and Q&A. Written feedback should be returned to the student within 48 hours.
- For the prep workshop, prepare a 3-minute demonstration of "how NOT to present a progress seminar" — re-presenting the proposal, vague status report, no challenges mentioned, overclaiming preliminary findings. Follow with a 3-minute "good" version of the same project. The contrast makes the expectations visible.
Common Student Difficulties
- Re-presenting the proposal: Students default to the presentation structure they know — the proposal defence. They spend 60% of their time re-justifying the research design and 20% on findings. The progress seminar must invert this: 20% context, 80% execution and findings.
- Hiding challenges: Students fear that acknowledging problems will lower their evaluation. The opposite is true: identified challenges with professional responses demonstrate research maturity. Unacknowledged deviations that are discovered during Q&A damage credibility. Train panel chairs to probe for challenges if none are presented.
- Overclaiming from preliminary data: Students present preliminary regression results or initial themes as if they were definitive. Require explicit caveat language on findings slides. If a student does not volunteer caveats, panel members should ask: "How confident are you in these preliminary findings? What additional analyses are planned before you would consider them final?"
- Appealing to supervisor authority: As with the proposal defence (Week 8), students deflect methodological questions by citing the supervisor. The progress seminar evaluates the STUDENT's understanding, not the supervisor's guidance. Panel members should redirect: "I understand your supervisor approved this approach. I'm asking YOU — can you explain the reasoning behind this methodological choice?"
Pacing & Panel Management Tips
- The progress seminar is emotionally charged — it is the midpoint assessment of a year-long project. Some students will be anxious; others may be defensive. Panel chairs set the tone. Open Q&A with a positive observation before moving to critical questions: "Thank you for that clear presentation. I appreciate the honesty about your sampling challenges. I have a few questions that I hope will help strengthen the final phase..."
- If the panel identifies a serious problem (data cannot answer RQs, fundamental methodological flaw), the panel chair should acknowledge the difficulty while being constructive: "This is a significant concern, and I want to be direct about it because addressing it now is better than discovering it during the final viva. Let's discuss specific steps you can take..." Schedule a follow-up meeting with the student and their supervisor within 48 hours.
- Written feedback must be specific and actionable. "Strengthen the methodology" is not useful. "Your sample size of 75 is below the minimum for regression with 6 predictors (Green's rule: n ≥ 98). Options to consider: (1) reduce predictors to 3–4, (2) acknowledge reduced power and frame findings as exploratory, (3) continue data collection if feasible." Specificity enables action.