You taught the lesson. The learners were with you, your tutor nodded in the right places, and the activity finished more or less on time.
Then it was 11pm. The kettle had gone cold, the document was open, and the cursor just blinked.
Strange, isn’t it? You know this material. You used it hours ago, standing at a whiteboard with a marker running dry.
Most trainees expect feedback that says “needs more theory”. What it usually says is shorter, scribbled in a margin: “Good, but why?”
That one word is the whole problem. And it can be fixed.
Where the marks quietly go missing
Most trainees can do two things well. They can spot what a learner got wrong, and they can name an activity that might help.
The marks sit in between. Why did the error happen, and why would that activity suit it?
Nobody really teaches that middle part. People pick it up by accident, usually after a disappointing grade.
Take “She go to work every day.” Spotting the missing -s takes two seconds. Deciding what it means takes a good deal longer.
One missing letter, three different stories
The same error can come from quite different places:
- The learner has never really noticed the -s in what they hear.
- They know the rule perfectly and lose it when speaking at pace.
- Their first language does not mark the verb that way, so the habit runs deep.
Each story needs a different lesson. A written exercise suits the first. Speaking practice suits the second. Contrasting examples might help the third.
Which one is true? From a single sentence, you often cannot tell. Say so.
There is a small, quiet satisfaction when this clicks. A trainee who spent a week writing “learners struggle with the third person” suddenly produces three careful sentences about why, and the paragraph stands up on its own.
Open the brief before your notes
If you have ever typed Celta Assignment Help into a search bar at midnight, the fix is often smaller than you think. Open the brief before your notes, and read it for its verbs.
- Identify: say what it is.
- Describe: say how it works or what it looks like.
- Explain: say why it happens.
- Analyse: show how the parts connect and what follows.
Plenty of drafts answer “what” beautifully when the brief asked “why”. Accurate, tidy, and still off target. It is a shame, because the writer clearly knew more than the page showed.
Many briefs pack two instructions into one sentence. Tick each one off as you plan.
A three-line note before every paragraph
Before each paragraph, scribble this on scrap paper:
- Observation: what the learner actually said or did.
- Possible causes: at least two.
- Decision: what you would do, and why it fits the likeliest cause.
If line two is empty, stop. You have an observation, not a paragraph yet.
It takes a couple of minutes. It also prevents the commonest weakness of all: a confident recommendation with nothing underneath it.
What a careful claim sounds like
Suppose learners drop -s in speech but get it right in a written gap-fill. A weaker paragraph announces the cause. A stronger one weighs it.
Something like: “Accuracy in writing suggests the form is known. Omission in speech may reflect limited automaticity under time pressure, though a few sentences cannot rule out other explanations.”
Listen to the verbs. Suggests. May reflect. Cannot rule out. It sounds like someone who has looked at real evidence and respects its limits, and markers tend to trust that tone more than certainty.
The teaching move follows naturally: a short speaking task around the form, delayed feedback, then a second attempt. More gap-fills are missing on purpose, and your paragraph can say why.
Evidence is something you interpret
A reference supports your point. It cannot make the point for you. A citation stuck onto a general statement looks like wallpaper.
Give each source one job:
- A grammar reference for how the form works.
- Course input for the teaching principle.
- Your lesson notes for what happened in the room.
Then separate what you noticed from what you think. “Four learners answered incorrectly” is an observation. “My instructions were unclear” is a guess. Both are welcome, so long as the page says which is which.
Tutors often write “what makes you think that?” beside lines like this. It is really a request for the label.
Be careful with learner background too. First language, confidence and past learning matter, but each is a lead, not a verdict.
Reflection that changes something
“Timing was an issue” is easy to write and gives a reader nothing to hold.
Try this instead:
- Pick one moment. Half the group started the wrong task, say.
- List the plausible reasons: unclear wording, no model, a rushed demonstration.
- Choose the likeliest and say what points to it.
- Name one change you would make next time.
A rough lesson does not mean every decision was wrong. It means one specific thing can be adjusted.
When the week is already full
CELTA piles planning, teaching, feedback and writing onto the same few days. Being tired by Thursday is normal.
So skip the long drafting session. Spend ten minutes turning the brief into a plan: for each section, jot the verb, the evidence you need and the classroom link.
Gaps show up when they cost minutes rather than a late night. Check your centre’s guidance on length and referencing too, because it varies more than people expect.
The “so what” read-through
Once the draft exists, read each paragraph and ask: so what?
If the answer is “so the learner needs this” or “so I would change that”, keep it. If the answer is a shrug, it is background.
Do this the next morning if you can. Then read the brief aloud once more. It feels odd, and it catches the instruction you skipped.
What stays with you
The best CELTA assignments are rarely the longest. They read like someone thinking carefully about a real room of real people, and being honest about what they cannot yet tell.
That habit does not stop when the course does. You will keep asking why things happened long after the certificate is framed.
So the next time a lesson goes well and the writing goes flat, ask the question the margin was asking. Why?
