<\/p>\nYou open your inbox and there it is \u2014 a dense, line-by-line critique of your draft, delivered with a few margin notes that read like a final exam. Your chest tightens. You\u2019re not alone. Many IB Diploma students meet a supervisor who seems very demanding: high standards, short replies, firm deadlines. That strictness can feel personal, unfair, or even demotivating.<\/p>\n
This blog is for the student who wants to keep their cool, get the most from supervision, and turn tough feedback into measurable progress \u2014 for Internal Assessments, the Extended Essay, and Theory of Knowledge projects alike. You’ll find practical communication scripts, meeting agendas, a simple feedback-to-action table you can copy, and mindset shifts that make a strict supervisor work for you instead of against you.<\/p>\n
<\/p>\n
Before pushing back or panicking, step back and diagnose. A strict supervisor usually has a reason; it might be workload, a desire to protect academic integrity, or a pattern of past students submitting weak final work. Often, strictness is a proxy for care \u2014 but poorly expressed. Spotting the motive helps you respond smartly.<\/p>\n
Recognizing which of these fits your supervisor will shape your plan. If it\u2019s a workload issue, streamline your requests. If it\u2019s standards, show how you\u2019ll meet them. If it\u2019s communication style, adapt how you write and speak.<\/p>\n
It helps to reframe: strict feedback often equals clear expectations. When you translate critique into steps, strictness becomes structure. Try swapping the thought \u201cThey\u2019re being harsh\u201d for \u201cThey want a clear, defensible final product.\u201d That mental shift turns resistance into curiosity \u2014 and curiosity is the engine of progress.<\/p>\n
When your supervisor is strict, clarity beats emotion every time. Tight, polite communication reduces friction and shows you respect their time.<\/p>\n
Always send a short agenda 24\u201348 hours before a meeting. That small habit changes the tone of the meeting: it signals organization, focuses discussion, and lets your supervisor prepare targeted feedback instead of giving broad criticism.<\/p>\n
Bring a one-page list of choices you need to make. For each choice include a recommendation and the reason. A strict supervisor will appreciate that you came prepared to decide, not to be told what to do from scratch.<\/p>\n
A 3\u20135 line recap email does two things: it confirms you heard correctly and it creates a written trail. Use this pattern: one line summary, three bullet points of agreed actions, and the next meeting or deadline. This makes future criticism easy to contextualize.<\/p>\n
Below is a simple table you can adapt for IA, EE, or TOK supervision. Use it as a shared template so supervisor and student are aligned about what each meeting should produce.<\/p>\n
| Meeting Type<\/th>\n | Purpose<\/th>\n | Student brings<\/th>\n | Expected output<\/th>\n<\/tr>\n<\/thead>\n | ||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Initial scoping<\/td>\n | Define research question and scope<\/td>\n | Two topic ideas, one-page rationale<\/td>\n | Agreed research question and next steps<\/td>\n<\/tr>\n | ||||||||||||
| Literature check<\/td>\n | Confirm key sources and gaps<\/td>\n | Annotated bibliography draft<\/td>\n | List of 6\u201310 core sources and citation plan<\/td>\n<\/tr>\n | ||||||||||||
| Methodology review<\/td>\n | Ensure method is valid and feasible<\/td>\n | Methodology draft and ethical notes<\/td>\n | Revised method and data-collection checklist<\/td>\n<\/tr>\n | ||||||||||||
| Draft review<\/td>\n | Targeted feedback and structural fixes<\/td>\n | Draft section(s) highlighted<\/td>\n | Specific edits and a timeline to final draft<\/td>\n<\/tr>\n<\/tbody>\n<\/table><\/div>\nTurn strict feedback into a to-do list<\/h2>\nStrict supervisors love specifics. They\u2019ll give you dense notes; your job is to convert those notes into an actionable plan. Create a simple feedback log: one row per comment, with a clear action, a feasible deadline, and a status column. Moving from vague correction to a checklist reduces anxiety and proves progress.<\/p>\n
|
<\/p>\n