Reports & PDFs
How a submission becomes a printable report, and what each element contributes to it.
Every submission can be turned into a PDF report that puts the case, the learner's work, and the scoring side by side. Instructors use it for review and feedback; learners can download their own. This page explains when a report is generated, what's on it, and which element types draw which visuals.
When and how a report is generated
A report is generated on demand — there's no overnight batch. When you open a submission and choose to download or view the report, Theta assembles the PDF right then from the stored submission:
- An instructor or admin in the course's organization can generate the report for any learner's submission in that course.
- A learner can generate the report for their own submission — unless the lesson locks results. Then there is no report for them (Theta refuses it, not just the button), or, on an assessment with a pass mark, a one-page exam result instead: pass or not, the overall score, a score per skill, testing confidence and who to contact — with no case content, answers or answer key on it. Instructors still get the full report.
Because it's built fresh each time, the report always reflects the submission's current scored result — including any re-scoring you've applied since.
The report is a true PDF (downloadable and printable), not just an on-screen view. The filename includes the student name and the date/time it was generated.
What appears on the report
The report walks through the lesson's elements in the order they appear in the lesson, and includes:
- Every scored element — its visual plus a scoring table.
- Every report-only element or field — shown for reference, clearly marked as not counted.
It does not include:
- Hidden elements. If an element was hidden from the learner during the submission (for example an audiogram used only to derive a linked speech test), its answer key is instructor-only and is kept off the report.
- Off fields. Anything left in the Off state contributes nothing and isn't shown.
See How scoring works for the Off / Scored / Report-only distinction that decides this.
Anatomy of the report
Header
The first thing on the report is a header band with the organization's logo and the submission's key facts:
| Field | What it shows |
|---|---|
| Student | The learner's name |
| Organization | The org the course belongs to |
| Course / Lesson | Where this submission came from |
| Mode | Practice or Exam |
| Type | Template (values regenerated per submission) or Fixed |
| Time | Total time on task, derived from the activity trail |
| Score | Overall result, e.g. 85% (17/20), or Not scored |
Per-element sections
Below the header, each element gets its own section with a title and, typically, two parts:
- A visual component — a faithful rendering of what the learner saw and did (the same chart, image, or waveform type used in the simulation).
- A data table — rows comparing the designed (expected) value, the submitted value, and whether each scored field was correct.
In the data table, correct rows are marked OK, incorrect rows X, and
report-only rows show a dash (—) with a footnote noting they're shown for
reference only and not scored. Leniently-scored ("accepted either way") rows are
flagged with an asterisk and an explanation. Each scored element's table ends
with its correct/total and percentage.
The visual on the report overlays the learner's submission against the expected answer where it helps — for example the audiogram plots the submitted thresholds on top of the true thresholds, so a reviewer can see at a glance where the learner diverged.
What each element type contributes
Different elements draw different visuals. Here's what each puts on the page:
| Element | Visual component | Data / table component |
|---|---|---|
| Audiometry | Right- and left-ear audiograms, submitted thresholds overlaid on the expected ones; a profile summary (degree / type / configuration) when scored | Per-frequency table of expected vs. submitted thresholds and masking fields, plus profile rows |
| Tympanometry | Right- and left-ear tympanograms (the pressure–compliance curves) | Expected vs. submitted tympanogram type per ear |
| Acoustic Reflexes (ART) | The reflex threshold plot for each ear (ipsilateral and contralateral) | Per-frequency thresholds and reflex classifications, ipsi/contra |
| Otoscopy | The otoscopy image the learner examined, per ear | Selected category and referral-needed decision, expected vs. submitted |
| Speech in Quiet (SRT / WRS / sound-sensitivity) | The performance-intensity function (PIF) curve, with the learner's submission plotted against the design | Field table: SRT, WRS, SAT/MCL/UCL, etc. — expected vs. submitted per ear |
| Information | The reference text you provided to the learner | The learner's collected free-text response, shown for reference (not auto-scored) |
Elements that are templates regenerate their underlying values per submission, so two learners' reports for the "same" lesson can show different numbers and curves — each report reflects that learner's actual case. The header's Type field tells you whether you're looking at a templated or fixed report.
Reading a report well
- Start at the header score for the overall result and mode.
- Scan each element's visual to see the shape of the learner's work.
- Drop into the table to see exactly which fields were right, wrong, or shown for reference.
- Remember that report-only rows are intentional context — they're there to inform, not to penalise.
For the rules behind which fields land in which column, and how the numbers are computed, see How scoring works.