CAEL Technical Failure: What to Send Your University
Report a CAEL technical incident within the official window, build a factual evidence packet and ask admissions the right deadline questions, with 20 FAQs.
A CAEL technical failure should be reported to the test staff or online proctor immediately and to Paragon within the provider's published 48-hour window. A university message is a separate action: explain that an official incident is under review, give the application and evidence deadlines, and ask what documentation or contingency the institution will accept.
Do not tell the university that the provider has granted a retest, cancelled a score or confirmed an outage unless that decision exists in writing. A frozen screen, silent microphone or lost connection is an incident to document, not automatic proof of a particular remedy.
Updated 16 November 2026. Written by the SpeakShark Team.
Key takeaways
- Tell test-centre staff or the online proctor while the problem is happening.
- CAEL says an issue that may affect results must be reported to Paragon within 48 hours of the test.
- The test provider investigates the incident; the university controls its document deadline and admission response.
- Send admissions a concise timeline and official case evidence, not passwords, full identity documents or unsupported conclusions.
- Do not book another test until you understand the incident route, deadline and likely result timing.
In this guide: Act during the test | Build the incident record | Contact the university | Choose the next action | Return to speaking practice
Act while the problem is happening
At a test centre, raise your hand and tell test personnel immediately. The CAEL test-centre requirements say issues should be reported to centre staff and that a contact card can be provided on request. Note the approximate time, test section and visible symptom after staff have acknowledged the issue.
For CAEL Online, use the ProProctor chat or raise-hand function. The online test-day requirements direct candidates to notify the proctor and use ProProctor support for technical help. If a readiness agent has not connected within the published period, follow the official support instruction rather than repeatedly restarting software without guidance.
Obey the proctor or supervisor. Do not use a phone, photograph secure content, open another application or copy a live question in an attempt to create evidence. Those actions can create a test-security problem that is more serious than the original fault. Evidence should identify the incident without reproducing protected material.
Use a plain symptom description. "The microphone indicator stopped responding during my spoken response at approximately 10:18" is more useful than "the whole test was broken." Record whether staff saw the problem, whether the timer continued, whether the section resumed and whether the session ended normally.
| Observation | Useful detail | Avoid |
|---|---|---|
| Time | Approximate local time and section | Guessing an exact second later |
| Symptom | No input level, frozen page, disconnect or missing audio | Copying secure test content |
| Test response | Continued, paused, restarted or terminated | Claiming a remedy was approved |
| Human witness | Proctor or centre staff acknowledgement | Publishing staff names online |
| Reference | Booking and incident case number | Sharing account credentials |
Our microphone troubleshooting guide helps distinguish device permission, missing hardware and a busy input before a future test. It cannot diagnose the provider platform after the event.
Build a provider-ready incident record
CAEL's centre and online instructions state that an issue which may have affected results must be reported to Paragon within 48 hours of the test. They also warn that no corrective action will be taken for problems reported after scores are released or more than 48 hours after the sitting, whichever comes first. Treat that as an urgent reporting boundary.
Your provider report should include your account or registration details through the official channel, test date and delivery mode, centre or online appointment, approximate incident time, affected section, symptom, staff or proctor action, and any case reference. Attach only material the provider requests. Do not send payment-card details or passwords.
Separate facts from impact. Facts include "the proctor reconnected me" or "the timer continued for approximately two minutes." Impact is your concern that the lost time affected the response. The provider decides whether logs support that concern and what remedy, if any, follows.
Keep the sent message, automated acknowledgement, case number and subsequent reply. If you called support, write the date, channel and summary immediately afterward. A clean chronology is easier to assess than ten messages containing changing descriptions.
CAEL says results are normally available in the account within eight business days. The official scoring page also explains score reports and re-evaluation. An incident investigation is not necessarily the same process or timeline as ordinary result release or score re-evaluation.
Practise a clear incident explanation if you need to speak with support or admissions.
For a delayed score rather than a test-day fault, use CAEL score missing or delayed. For a disagreement with a released rating, see CAEL re-evaluation timing. Those paths should not be merged into one generic complaint.
Send the university a decision-ready message
Contact the university when the incident could affect an English-evidence deadline. The purpose is not to persuade admissions that a particular score should be assumed. It is to establish what evidence the institution needs while the provider investigates.
Include the programme, intake, application reference, English-document deadline, CAEL test date, delivery mode and provider case status. Ask whether the institution needs the case acknowledgement, whether a pending result can be matched later, and whether any approved alternative or extension exists for your application.
An original message structure:
Subject: CAEL incident and English-evidence deadline for [programme], [application reference]
I took CAEL [Online/at a test centre] on [date]. A technical incident occurred during the test, and I reported it through the official channel within the provider's reporting window. My case reference is [reference]. My English-evidence deadline is [date]. Could you confirm what documentation you require while the provider reviews the incident, and whether there is an approved contingency if the result or decision is not available by that deadline?
Do not attach a full passport unless the verified university process requests it. A provider case acknowledgement, booking confirmation and concise incident timeline are usually more relevant to the timing question. Redact unrelated personal information before sharing screenshots.
| University needs to decide | Evidence you can offer | What you must not promise |
|---|---|---|
| Is an incident case open? | Provider acknowledgement and reference | That the complaint will succeed |
| Which application is affected? | Application reference, programme and intake | That admission is otherwise guaranteed |
| Which deadline is at risk? | Published requirement or offer condition | That the school must extend it |
| What happens next? | Expected provider update when known | A free retest or a particular score |
A receiver such as UBC publishes its own English-language competency rules, illustrating why provider incident evidence and university acceptance must be checked separately.
Check the institution's exact English policy before proposing another test. Our CAEL retake deadline checklist, CAEL eligibility and format guide, and CAEL result validity guide address separate decisions.
Separate four possible next actions
There are at least four different paths: continue waiting for the normal result, follow the incident investigation, request score re-evaluation after a result, or book another eligible sitting. Only the facts of your case determine which path is relevant.
An incident report concerns delivery conditions. Re-evaluation concerns the rating of submitted performance. A retake creates a new performance. A university extension changes an institutional deadline. Success in one path does not automatically produce the outcome of another.
Before paying again, ask whether the provider has instructed you to wait and whether another result can arrive before the receiver's deadline. CAEL's registration-frequency and result-release rules must be combined with real appointment availability. Do not let panic convert an unresolved platform case into an unnecessary second fee.
If the provider confirms that no score will be issued or offers a remedy, preserve the exact wording. If a result appears, check whether the university can verify it and whether your condition is satisfied. If the institution grants an extension, note the new date and any required upload channel.
For broader comparisons, see CAEL versus IELTS, CAEL versus PTE Academic, and best speaking apps for international students. Product choice is secondary until the administrative route is clear.
Return to speaking practice only after the administrative plan
A technical failure can damage confidence even when it says nothing about language ability. Rebuild the speaking routine with short, low-pressure recordings. Check microphone selection, browser permission and input level before starting. Then practise one explanation, one supporting detail and one follow-up.
Do not try to recreate protected CAEL questions. Use original academic topics or public materials. Explain a claim, compare two ideas and state a conclusion. Review audibility, structure and meaning rather than treating a consumer app score as an official CAEL prediction.
Use recording and reviewing answers for a general self-review method, speaking test microphone checklist, recovering after a failed speaking test, and how to stop freezing for confidence practice.
Run a short speaking rehearsal with SpeakShark only if conversation practice is the remaining gap. SpeakShark cannot access CAEL logs, decide an incident case, issue a score or change a university deadline. Review pricing separately from the provider and admission decisions.
Try one more unscripted explanation after the provider and university plan is settled.
Sources and editorial method
We checked CAEL's current online and test-centre requirements and official scoring page on 16 November 2026. The evidence table, email structure and practice routine are original editorial tools. They do not reproduce live test content or predict how Paragon or a university will decide a case.
About SpeakShark
SpeakShark provides AI-assisted English conversation practice. Website: SpeakShark. Support: speaksharksupport@gmail.com. See current pricing before purchasing.
Practice and affiliation notice
We are a speaking improvement tool. We are not an exam preparation provider and are not affiliated with CAEL, Paragon, Prometric ProProctor or any exam board. For official test rules and results, go to the exam body. Use SpeakShark to make your spoken English stronger, and use official material to learn the test.
FAQ
What should I do first if CAEL has a technical problem?
How long do I have to report a CAEL technical issue?
Who handles technical support during CAEL Online?
What evidence should I record after a CAEL incident?
Can I photograph the screen to prove the problem?
Does a technical failure automatically give me a free CAEL retake?
Should I contact my university before CAEL answers?
What should I send the university about the incident?
Can a CAEL booking confirmation satisfy an English condition?
How quickly are ordinary CAEL results released?
Is a technical incident the same as score re-evaluation?
Should I book another CAEL test immediately?
What if the microphone stopped but the timer kept running?
What if I was disconnected from CAEL Online?
Can the university force CAEL to issue a new score?
What if my university deadline arrives before the case is resolved?
Should I share my full passport with admissions as evidence?
How can I prevent microphone problems before another test?
Can SpeakShark investigate my CAEL technical failure?
What is the final checklist after a CAEL technical incident?
Curious how it works? Explore SpeakShark's features or see plans and pricing.
Keep reading
Cambridge B2 Speaking Problem: What to Send a University
Cambridge B2 Speaking problem? Learn what to report to the centre, how Special Consideration works and what evidence to send a university, with 20 FAQs.
C1 Advanced Speaking Problem: What to Send a University
Report a C1 Advanced Speaking incident, protect test-day photo evidence, use Special Consideration correctly and update a university through 20 FAQs.
C2 Proficiency Speaking Problem: University Evidence Guide
Report a C2 Proficiency Speaking incident, use Special Consideration correctly, track certificate evidence and update a university through 20 FAQs.