Speaking is the module most platforms omit
It needs a prompt, a voice, a recording, and a examiner-style judgement. Most platforms either omit it or post static cue cards, which is the module students most need to rehearse.
Most online IELTS sites are question banks that skip Speaking. IELTS Test BD tests Listening, Reading, Writing and Speaking, records Speaking answers in the browser and returns an AI transcript and band estimate, saves work through a dropped connection, and runs the whole centre from an 18 screen admin workspace.
15 screens, from the public landing page to the admin workspace.

Real exam experience, instant results, progress tracking and data security, stated on the first screen alongside a view of the product. The 2 admission office numbers sit in a strip above the navigation, because a large share of this audience still books by phone.
2 office numbers above the fold on every page

8 active bundles from a free trial to 24 mock tests, searchable and filterable by level. The free full mock is listed first so a student can complete a real test before paying.
1 free full mock, no purchase required

Each bundle lists what is included and what the student should be able to do afterwards. Pricing shows list price against current price, and promo codes are validated on the server rather than trusted from the browser.
Discounts calculated server-side, never client-side

Listening runs audio-led parts with protected playback. Reading uses passage layouts built for scanning and matching. Writing carries live word counts and rubric review. Speaking runs Introduction plus Parts 1, 2 and 3. Each keeps the exam format while reporting into one progress record.
4 modules, 1 combined progress record

The centre also registers candidates for the official IELTS exam. The form collects test date, venue, module, delivery type, passport and NID details, destination countries and document scans, generates a reference number, and arrives in an admin inbox with the uploads attached.
Identity documents stored in private storage

The mock card lists all 4 modules as compact rows, each showing Start, Resume or Result based on the current attempt state. The main action changes with them, so a returning student reaches the right place in 1 tap.
Start, Resume or Result per module

A full mock does not have to be completed in one session. Listening on one day and Speaking on another is supported, and each module scores and reports independently. Once all 4 are complete the platform calculates the overall band.
Modules scored separately, band combined at the end

The toolbar shows the timer, the word target per task tab and a live Saved state. Answers save to the server as the student writes, and a local draft is written before the network request completes. Reopening restores the exact question, notes, mode and remaining time.
Server autosave plus a local draft, merged by timestamp

Speaking opens with a headphone check, a microphone check and a waiting room, so audio faults surface before the attempt rather than after. The student then answers each part aloud in the browser. The checks guide but do not block entry.
Headphone and microphone checked before entry

Average band, best band, completed attempts and pending reviews across the top, then a panel per skill with best, average and attempt count. A recommendation names the single most useful next test, calculated from the weakest skill.
Next test chosen from the weakest skill

All 4 skills are grouped under the parent mock, with a band each and an overall band rounded to the nearest half. Objective questions show the student answer beside the correct one with an explanation. Writing and Speaking show rubric feedback, and Speaking includes the transcript.
Answers released only after submission

Writing is scored against the 4 IELTS criteria: task achievement, coherence, lexical resource and grammatical range. The platform produces a preliminary band and rubric notes, then an admin corrects or confirms them. Comments appear in the student result page, not in a separate message.
Automated first pass, admin confirms the band

The first screen lists writing reviews queued, payments awaiting approval, registrations submitted and today's activity. Analytics are available but placed after the queues, since an operator opens the workspace to make decisions. Common tasks sit beside the queue, 1 click from the next action.
Payments, reviews and registrations queued first

Results are grouped under the parent mock rather than listed as separate skill attempts, so each student is 1 row with 4 module states and an overall band. Submitted work opens from the queue. Student names are blurred in this screenshot only; the live workspace shows them in full.
1 row per mock instead of 4 skill attempts

A 4 step builder covering test details, sections, questions and solutions, with skill, status, duration and band target set per test. Answer keys entered here stay on the server and are used only for scoring. New mocks and Speaking variations are added in the admin, with no development work.
Answer keys never leave the server
6 requirements an IELTS mock test has that a standard web app does not.
It needs a prompt, a voice, a recording, and a examiner-style judgement. Most platforms either omit it or post static cue cards, which is the module students most need to rehearse.
Listening and Reading can be marked mechanically, but Writing and Speaking need judgement. With one centre and hundreds of attempts, manual review becomes the bottleneck that caps enrolment.
Test sessions run 30 to 60 minutes on connections that are not always stable. Losing a Writing task to a reload is the fastest way to lose a student permanently.
A full mock is 4 modules back to back. Students working or studying full time need to split it across days without the platform treating that as an abandoned attempt.
Much of this market pays by mobile transfer and expects to send a transaction reference and a screenshot. A card-only checkout would exclude a large share of genuine buyers.
If correct answers ship to the browser with the questions, the test is worthless. They have to be withheld during the attempt and released only once it is submitted.
Agreed before development started, in the order they were solved.
Listening, Reading, Writing and Speaking under one mock identity, so a student sees a test rather than 4 unrelated exercises.
Record in the browser, transcribe it, and return a criterion-based estimate, so the hardest module stops being the one that gets skipped.
Autosave to the server, keep a local draft as a second net, and restore the exact position on return.
Any skill on any day, scored independently, with the overall band assembled once all 4 are done.
Raw scores mean nothing to an IELTS candidate. Every module ends in a band estimate with feedback attached.
Mobile transfer with a reference and proof, reviewed and approved by a human, with a card gateway ready behind it.
Students, tests, scores, payments, registrations, documents and feedback in a single workspace instead of a spreadsheet and an inbox.
6 build decisions and what each one traded off.
Listening and Reading mark themselves against a server-held key. Writing and Speaking get an automated first pass that an admin can correct. That splits the work so volume scales without pretending a model has final say on a band.
Microphones are wrong, tabs get closed, uploads fail. So audio is checked before entry, each answer records separately and can be retried alone, and finished recordings are held in the browser's own storage so a reload does not erase them.
Naive autosave loses data when an older request finishes after a newer one. Saves are debounced and ordered, later writes cannot be overwritten by earlier ones, and local and server state are merged by timestamp rather than by whichever loaded last.
Correct answers are never part of the data the test page loads. They are applied during server-side scoring and released to the student through a separate endpoint only after submission, which is the only version of this that actually holds.
Most platforms bolt local payment on as an afterthought. Here the proof upload, the private storage, the admin review and the approval emails were built as the primary path, with the card gateway kept ready alongside it.
An operator's question is what needs deciding today, not how many users signed up this quarter. So the workspace opens on pending reviews, payments and registrations, and the analytics sit behind that.
8 systems that run during a timed attempt.
4 stages, and what each one covers.
18 management screens, grouped into 4 areas.
10 differences between this platform and a practice question site.
Counts from the delivered build. Not traffic or revenue figures.
How the platform changes the centre's operation. Not separately measured outcomes.
A student can rehearse a full Speaking test and get criterion feedback without an examiner sitting with them, which is the part of preparation that used to cap how many students the centre could serve.
Listening and Reading need no human at all, and Writing and Speaking arrive pre-scored with rubric notes, so review becomes confirmation rather than assessment from scratch.
The most common reason people abandon an online test is losing an hour to a reload. 2 layers of saving mean a dropped connection costs seconds, not the attempt.
Independent modules let a working student practise in the time they actually have, which turns a full mock from a weekend commitment into 4 manageable sessions.
Accepting a mobile transfer with a reference and a screenshot, reviewed by a person, keeps the buyers a card-only checkout would have turned away.
Students, tests, scores, payments, registrations, documents and email live together, so the centre stops reconciling a spreadsheet against an inbox against a folder of receipts.
The whole platform, not a website with a quiz attached:
It runs the shape of a real Speaking interview, in a browser:
No, and the platform is deliberate about saying so:
Very little, which was the point:
Yes. This is the largest build in my portfolio and the pattern transfers:
If enrolment is limited by how much your staff can mark, a platform that automates the mechanical scoring removes the ceiling.