HELP · SUMMARY COMPOSER
Summary composer
Turn the evidence you included into a written summary you can review, edit and approve — with every claim tied to a factor the chart actually produced.
Before you start
- At least one evidence factor included in the session workspace. A summary has to rest on something, and the composer links back if nothing is selected.
- A finished calculation. Evidence exists only once a run has produced it.
What you provide
- The wording of each section. Templates and your practice voice are offered where you have recorded them.
- Which evidence each section cites.
What you can do
- Draft the sections, or start from a template you have stored.
- Save as you go. Saving creates a new version, so nothing you have already written is overwritten.
- Open the review screen to look at the exact version a client would receive.
What you get
- A stored version of the summary, tied to the evidence it cites and to the engine that produced it.
- A version you can approve, and only then deliver.
Common problems
- The composer is locked
- The summary is already approved or already delivered. An approved version is immutable by design: to change one that has left the practice, start a correction from the review screen, which creates a new version and records your reason rather than rewriting what the client received.
- A cited factor is refused
- A summary may cite only factors included in this session. If the API refuses an identifier, re-open the workspace and include the factor there first — the composer cannot widen what the session holds.