tertiusTertius treats transcription as the middle of the workflow. The user selects an outcome or playbook, records live or imports a file, then receives both text and a shaped result. That design is useful when the same kind of work repeats but the recording changes.
Meetings: preserve what was decided
Use a meeting-notes outcome to organize decisions, open questions, risks, and next steps. Keep the transcript available when a statement is ambiguous. Never add an owner or due date that was not spoken; absence is more accurate than confident invention.
Interviews and research: separate evidence from synthesis
First produce a clean transcript that stays close to the source. Then create a summary or research-note outcome as a separate layer. Quote only after checking the audio. Automated cleanup can change nuance, remove hesitation, or mishear terminology, so the recording remains the evidence.
Client work: draft the update, then own it
Speak rough context while it is fresh, then apply a playbook that asks for a concise status, decisions, risks, and the next requested action. Review tone, commitments, dates, pricing, and names before sending. Tertius can shorten the path to a draft; it cannot take professional responsibility for the message.
Classes and learning: convert listening into retrieval
Import a lecture or recorded class, preserve the transcript, and produce structured notes or a summary. Use a custom playbook to request key terms, examples, and unresolved questions. Verify definitions against course material before treating the output as authoritative.
Field notes: capture before detail fades
A global shortcut works well for immediate observations. A custom playbook can enforce a stable structure such as context, observation, implication, and next action. If field notes contain confidential or regulated data, confirm that the managed cloud transcription service, provider processing, and beta security posture fit your organization’s policy first.
| Workflow | Input | Suggested first outcome | Human check |
|---|---|---|---|
| Meeting | Live thought or recorded call | Meeting notes | Decisions, owners, dates |
| Interview | Audio or video file | Clean transcript | Quotes, names, context |
| Client update | Quick dictation | Professional email | Commitments, tone, figures |
| Lecture | Recorded class | Summary or notes | Definitions, citations, examples |
| Field note | Quick dictation | Custom playbook | Sensitive data, observations |
Build a useful playbook
- Name the real destination: “client status email” is clearer than “professional.”
- Specify the required sections in order.
- State what must not be invented, especially owners, dates, quotes, and figures.
- Describe tone in plain language and include an expected length.
- Test the playbook against messy real recordings, then adjust it.
Professional use raises the review standard. Do not rely on Tertius without qualified human review for legal, medical, financial, hiring, safety, or other consequential decisions.