Remote sign-interpreting communication checks
Link communication requirements to two-way picture/audio tests at actual positions and to pause and alternative-support arrangements.
User position is linked to two-way picture/audio test results.
- File formats
- English XLSX · CSV (UTF-8)
- Version
- 2.0
- Editorial review
- 31 Oct 2026
- Use this for
- Link communication requirements to two-way picture/audio tests at actual positions and to pause and alternative-support arrangements.
When to use it
Link communication requirements to two-way picture/audio tests at actual positions and to pause and alternative-support arrangements.
This form does not automatically establish that remote support is appropriate for a person. Do not shift the decision entirely to the participant; discuss alternatives with the person, provider and organiser.
Start with the guide: Remote sign-language interpretation and two-way communication: a practical guideFill in the template step by step
When to use it
Open a record when preparing the work. Link later checks and changes using the same item ID.
What to have ready
- Restricted record IDs for communication/support requests
- Actual seating and AV paths and interpreter/programme/alternative contacts
Record only necessary communication needs and identify actual positions.
Test face/hands, reverse views and the complete Q&A loop.
Separate technical results from user checks and confirm pause/alternative handover.
Worked example
Fictional example, not an actual event or supplier record
Eight columns · scroll horizontally to view the complete worked example.
| Session, user position, request ID | Communication needs and restricted link | Screen, camera, audio and network | Face/hands and reverse view | Question, interpretation, answer loop | Technical and user checks | Pause/alternative and authority | Retest and handover deadline |
|---|---|---|---|---|---|---|---|
| S01 / seat R2 / ACC01 | Sign-language request confirmed; restricted ACC01 | PATH01 proposed; not tested | R2 sightline unconfirmed | Not tested | Neither technical nor user check complete | Programme Park; alternative under discussion | Access Lee to rehearse8 Nov10:00 |
| S01-TECH / R2 | ACC01 conditions unchanged | PATH01 / two-way cameras | Interpreter visible; reverse hand view obstructed | Question M2 missing at interpreter | Technical REC01; not user verification | Proposed hold / alternative contact ALT01 | Technician Kim to fix and retest8 Nov12:00 |
| S01-R1 / R2 | ACC01 / minimum sharing | PATH02 revised / ENV02 | Both camera views checked TECH02 | Actual Q&A loop TEST02 | Technical passed; user confirmation ACC02 | Pause signal and alternative PLAN02 / Park | Site Lee receives13:00; retest on change |
Blank template preview
This preview shows a few rows. The downloaded file contains 24 prepared rows.
Eight columns · scroll horizontally to view the complete blank worksheet.
| Session, user position, request ID | Communication needs and restricted link | Screen, camera, audio and network | Face/hands and reverse view | Question, interpretation, answer loop | Technical and user checks | Pause/alternative and authority | Retest and handover deadline |
|---|---|---|---|---|---|---|---|
| — | — | — | — | — | — | — | — |
| — | — | — | — | — | — | — | — |
| — | — | — | — | — | — | — | — |
Sources used to develop this template
EVENTODIT created this template using the working methods described in the public sources below. It is not an official form and has not been reviewed or approved by those organisations.
- U.S. Department of Justice · Effective Communication · Video Remote Interpreting
Adapted to link the guide’s checks with evidence, owners and follow-up records. The fields are editorial proposals, not an authority’s official submission form.