Add Evidence to a TOEFL Technical Case in 2026
Yes. Add evidence to an existing TOEFL technical case by replying in the same thread with new facts, a clear timeline, and one specific request.
The Short Version
Use 1 existing case number instead of opening a duplicate report.
Add a timeline with the exact test date, appointment time, and time zone.
Separate new evidence from information already sent.
End with 1 specific action request, such as confirmation of test status.
Do not send passwords, full payment-card numbers, or unauthorized recordings from a secure test session.
How do you add evidence to a TOEFL technical case in 2026?
To add evidence to a TOEFL technical case in 2026, reply through the same support thread or channel that contains the existing case reference. Put the case number near the beginning, identify what is new, and ask for one clear next step. This keeps the evidence attached to one history instead of forcing a reviewer to reconcile two separate reports.
Start with the appointment facts that identify the incident: your name as registered, test date, scheduled time, time zone, appointment number if available, and the existing technical case number. Then add only the material that was not included before. A useful update might contain a corrected timestamp, a newly received account-status message, a support email, or a concise explanation of what happened after the original report.
Do not describe a guess as a confirmed event. Write “the second-camera page became blank at 10:14 a.m.” rather than “the system rejected my camera.” The first statement records what you observed. The second claims a cause that you may not be able to prove.
ETS says that a Home Edition test taker should communicate with the proctor during an active technical problem by speaking, waving, or using chat when available. If a second camera disconnects during the test, the proctor pauses the exam and gives reconnection instructions. That guidance is about the live session; a later case update should preserve the same discipline by recording the instructions you received without inventing a cause or outcome.
Before writing, use the technical case number checklist to confirm that you are referring to the correct support record. This reduces the chance that evidence is attached to the wrong appointment or a duplicate issue.
What evidence should you add?
Add evidence that changes, verifies, or clarifies the existing case. The strongest update is usually short enough to scan in two minutes and specific enough that a reviewer can identify the appointment, event, and requested action without asking you to repeat the entire history.
| Evidence | What to include | Why it helps | What to avoid |
|---|---|---|---|
| Appointment identifiers | Test date, scheduled time, time zone, appointment number, and case number | These details connect the update to one booking and one incident. | Passwords, security answers, or unrelated account data |
| Chronology | Exact or approximate times for check-in, interruption, reconnection, and test ending | A sequence helps a reviewer see what changed and when. | Long narrative without timestamps or event order |
| Observed messages | The exact wording of a status or error message, copied after the secure session when permitted | Precise wording is more useful than a broad description such as “it failed.” | Unauthorized screenshots or recordings during the active test |
| Support communication | Date, channel, response summary, and any reference number | This shows which instructions were already given and prevents repetition. | Creating several new cases for the same event |
| Requested outcome | One question or action, such as confirmation of appointment status or whether more documents are needed | A specific request makes the next response easier to act on. | Several unrelated requests in one paragraph |
Use the incident record checklist to reconstruct the timeline before contacting support. A written chronology reduces contradictions between messages and helps you distinguish the original evidence from the new addition.
What should you leave out?
Leave out information that does not help identify the incident or answer the unresolved question. More material is not automatically stronger evidence. Ten repeated paragraphs can hide the one new fact that matters.
Do not include your ETS account password, email password, security answers, full payment-card number, or copies of unrelated identity documents. When an attachment contains more personal information than the case requires, redact the unnecessary fields while keeping the appointment identifiers and relevant dates readable.
Do not create screenshots, audio, or video recordings during a secure test session unless an authorized representative explicitly instructs you and the action is permitted. ETS Home Edition rules restrict unauthorized devices and recording. After the session, you can record your own recollection, save permitted support correspondence, and note the exact account status you can lawfully view.
Avoid opening a second case merely because the first reply was slow or incomplete. Continue the existing thread when possible and state that the message is an evidence addendum. The camera-disconnect follow-up sequence explains how to continue one record and ask for an actionable update.
How should you write the evidence update?
Use five short parts: identifier, new fact, timeline, attachment list, and request. This format is easier to review than a long emotional account, and it gives the support team a clear reason to reopen or reassess the record.
1. Identifier: “Existing case: [case number]. TOEFL appointment: [appointment number], [date], [time and time zone].”
2. New fact: “I am adding information that was not included in my original report.” State the new evidence in one or two sentences.
3. Timeline: List three to six events in chronological order. Use exact times when you recorded them and label estimates clearly.
4. Attachments: Name each permitted file and explain what it shows. For example, “Attachment 1 is the support email received after the appointment.”
5. Request: Ask for one outcome: confirmation that the evidence was added, clarification of the appointment status, instructions for the next required step, or confirmation that no further evidence is needed.
A practical closing sentence is: “Please confirm that this evidence has been added to case [number] and tell me whether any further document is required.” It requests both acknowledgment and a defined next step without assuming the final decision.
How to Practice This
Aidoss Academy uses the C-A-R-R loop for error tracking: Capture, Analyze, Repair, Retest. The same loop can organize a technical-case update because it turns a stressful event into a sequence of verifiable actions.
Capture: Write the appointment number, case number, date, time zone, observed messages, and proctor or support instructions. Capture facts as soon as the secure session has ended and you are permitted to use your notes and devices.
Analyze: Mark each statement as an observed fact, an approximate memory, or an assumption. Delete assumptions that cannot help the reviewer. This improves accuracy because the final message does not mix evidence with speculation.
Repair: Convert the remaining facts into one chronological addendum. Add only permitted attachments, remove excessive personal data, and finish with one request.
Retest: Read the message once as if you were the case reviewer. Can you identify the appointment in 20 seconds? Can you see what is new? Is the requested action unmistakable? If any answer is no, revise before sending.
Worked example: “Existing case 12345 concerns my July 18 appointment at 2:00 p.m. local time. I am adding one new fact: my account showed ‘appointment incomplete’ at approximately 5:10 p.m. after the proctor had paused the test. The original report already contains the camera-disconnection details. I have attached the permitted post-session support email. Please confirm that this evidence is attached to case 12345 and clarify the current appointment status.”
Use the free Essentials edition of the TOEFL iBT 2026 Error Log Notebook to build a clean C-A-R-R record, then use the Complete Digital edition for a fuller tracking system. The structured fields help separate observed facts from assumptions and keep dates, case references, repairs, and follow-ups in one place, which can make both support communication and later preparation more consistent.
For preparation beyond the incident itself, complete the TOEFL Readiness Check. It helps identify technical and study-plan gaps before the next appointment, so corrective work is directed at specific risks rather than general worry.
FAQ
Can I email new evidence without a case number?
You can contact support, but the existing case number is the strongest link to the earlier record. Include the appointment number and test date if the case number is unavailable.
Should I open a new TOEFL technical case for every new attachment?
No. Add related evidence to the existing case whenever the support channel allows it. One consolidated history reduces duplicate review and conflicting responses.
Can I send a screenshot from the TOEFL test session?
Do not create unauthorized screenshots or recordings during the secure session. Send only material that was lawfully created or received and that the support process permits.
What if the attachment is too large?
State what the file contains and ask which approved method should be used to provide it. Do not split the same incident into several new cases simply to send multiple files.
Sources: ETS TOEFL Home Edition test-day guidance and ETS guidance on getting assistance.
