03 · Administrative & operations
You keep Maven Tech running — comms, SOPs, vendors, scheduling. Your prompts favor speed and tone control. Remember: client and case details count as sensitive; keep specifics generic in prompts.
Prompt iteration example
Section titled “Prompt iteration example”Use case: Vendor evaluation, end to end.
You’re evaluating a new transcription vendor. You type:
Evaluate [vendor] for use at Clarity. Table: what it does, pricing, HIPAA posture (BAA available?), data residency, and integration effort. Flag anything that touches PHI handling. Keep vendor and client names generic.
Then you narrow to the deciding factor and draft the outreach — chaining follow-ups the same way the other roles do: one ask per prompt, refined in place.
Example use cases
Section titled “Example use cases”Operations coordinator
Section titled “Operations coordinator”Use case: Email drafting.
Draft this email. Tone: direct, short sentences, no filler, no exclamation points. Audience: [physician / attorney / MSP partner / vendor]. Goal: [goal]. Context: [context]. Two variants: soft and direct.
Use case: SOP writer.
Turn this process into an SOP: purpose, owner, trigger, numbered steps (one action per step), failure/escalation path, and what NOT to do. If any step involves client or patient data, insert the data-handling rule inline.
Use case: Calendar triage.
Here’s next week’s meeting list. Group: decisions needed / status-only / could-be-async. For each status-only meeting, draft the one-paragraph async update that replaces it.