What my Doha staff needed from a bilingual platform

First week of September, my Year 8 maths set was half Arabic-dominant and half new arrivals from the UK. I had ten minutes to pivot from place value vocabulary in Arabic to non-calculator methods for the British group. That’s the classroom context leaders in Qatar are solving for: mixed proficiency, tight inspection windows, and parents who read reports closely. The brief isn’t fancy; it’s continuity across rooms, bilingual clarity, and data that means something when the Ministry asks.

When we tested options, I wanted a platform that wouldn’t fall apart when a cover teacher walked in with zero context. ClassPods did better than most because the live view mirrored what I was doing and students joined quickly without me babysitting logins. For SLT, the win was that our lesson artefacts didn’t vanish after the bell—work was captured, tagged, and ready for departmental moderation. If you want to see the same flow I showed my head of secondary, you can skim a live-style overview here.

On 12 November, during a MoEHE drop-in, my Year 4 science lesson needed objectives displayed in Arabic and English, with questioning that included both. The observer sat near a pupil whose reading confidence dips in English. I didn’t have time to translate mid-explanation, so I built my prompts in both languages and flowed between them. That’s what earned nods—not the tech, but the way it supported a policy we already live by.

Rolling this out schoolwide only stuck when staff could keep their voice. I shared a simple start: two bilingual slides, one quick check for understanding, and a saved exit ticket for the next morning’s reteach. Early adopters mentored colleagues, and our Arabic department led training so the dual-language practices felt native, not bolted on. ClassPods didn’t make us bilingual; it just stopped getting in the way of being bilingual. If you’re lining up a September start, you can request the same onboarding sequence we used through this rollout form.

Thursday, Week 6, my Year 11 IB Physics group dragged in after sports day. I opened with a two-question retrieval warm-up, moved to a short demo on forces, and then parked them in pairs to annotate free-body diagrams. The crucial bit wasn’t the slideshow; it was that I could freeze the class when chatter spiked, spotlight a strong student attempt, and stash misconceptions for Friday’s intervention without breaking my pacing.

After the bell, I skimmed the saved responses, tagged the three patterns I kept seeing (units confusion, vector direction, and net force sign), and lined up a mini-task for the next lesson. Parents saw the same targets in their weekly email, so my inbox stayed calm. The next day, my colleague borrowed the set for her IGCSE group—no retyping, just slight edits to fit her scheme. If you’re curious what that looks like in practice, the community materials we riff on are easy to browse in the library.

In January budget week, our SLT huddled with department heads and the IT lead to decide what survives the cut. We needed clean pricing for a site license, a dashboard that shows who’s actually using the thing, and a plan that won’t implode when half the staff is proctoring mocks. I argued for a short pilot with clear success criteria, then a September full start if the data and staff feedback aligned.

What helped was the admin view: usage by subject, session artefacts for appraisal, and exportable evidence for internal reviews. No one wants another tool that’s brilliant in one classroom and invisible everywhere else. ClassPods ticked the visibility box and didn’t demand hours of extra marking, which is what swings staff sentiment. For your own SLT discussion, it’s easier to talk specifics when you’ve seen the cost model and what’s included; I kept our notes next to the numbers from the pricing page.