Safety Audit and Error Handling
Category: For Practitioners Reading time: ~4 min
Overview
Every script generated by TheraScripts goes through a multi-pass safety audit before it can be exported. This is not an optional step — it is a mandatory gate in the workflow. Understanding what the audit checks and how it behaves will help you work with it effectively.
What the safety audit checks
The audit runs four categories of checks:
1. Contraindication flags
Certain client profile conditions are associated with specific contraindications. The audit compares the assembled script against the clinical context you have recorded for the client and flags any combination where a module or output format is considered inappropriate or potentially harmful.
When a contraindication is detected, the audit either blocks the export (RED flag) or applies a constraint requiring your acknowledgement (AMBER flag). The flag description always explains the specific concern so you know what to address.
2. Language appropriateness
The audit checks the assembled script for language patterns that are inappropriate for the identified client context. This includes checking delivery-mode suitability (a script written for in-person delivery may need adjustments for self-guided audio use).
3. Structural safety
The audit verifies that the session has an appropriate opening and close, that no modules have been removed in a way that creates a structural safety gap, and that the session arc is coherent.
4. Attestation gate
For scripts that pass all checks, the final step requires you to confirm that you have reviewed the output and take clinical responsibility for its use. This attestation is logged.
How flags work
RED flags — blocking: The script cannot be exported until the issue is resolved. Resolution may mean removing a module, changing a delivery mode, or (in some cases) the contraindication cannot be resolved and export is permanently blocked for this session configuration.
AMBER flags — advisory: You can acknowledge the flag and proceed, but your acknowledgement is recorded. These typically cover cases where a technique is not contraindicated but warrants clinical judgement.
GREEN — clear: No issues detected in that check category.
When something goes wrong in generation
If the generation pipeline encounters an error — for example, a module that cannot be assembled into the session sequence — you will see a clear error message explaining what happened. You can:
- Retry the generation (transient errors resolve automatically)
- Adjust the session parameters and try again
- Contact support if the error persists (include the session ID shown on screen)
The platform does not silently produce a partial or broken script. If generation fails, you are told.