
Sauna reads your routings, cycle-time logs, and work instructions, drafts process documentation and ECN packets, opens improvement tickets, and assembles line-balancing summaries — sourced from your data and held for approval.
What it does
Turns your process notes and photos in Drive into a structured, step-by-step work instruction in Google Docs, formatted to your template.
Assembles the affected part numbers, drawing revisions, and rationale into an engineering change notice for review before it routes for approval.
Reads station cycle times from Google Sheets and drafts a line-balance summary showing the bottleneck and the takt gap.
Logs each kaizen and cost-reduction idea as a tracked issue in Jira with savings estimate, owner, and status for the weekly review.
Put Sauna to work on this.
Get started for freeIn context
Sauna shows up where you already work — the web app, Slack, email, iMessage, and Superhuman. It reads what it needs, does the task, and comes back with the draft for your approval.
Try it
The literal prompt for this job. Open it in Sauna and it picks up from there.
“Draft work instructions for the new fixture changeover from my notes in Drive, then open a Jira ticket for the cycle-time reduction project with the estimated savings.”
Plugs into the tools you already run — and thousands more, or any MCP server.
Good to know
Yes. It writes into your Google Docs template using your process notes and photos, and flags any step where the source material was unclear so you can fill the gap before release.
No. It assembles the change-notice packet from your part and drawing data, but routing and approval stay with you and your change board.
Sauna reads only what you connect, and acts only after you approve. Your workspace and its memory are yours, not training data.
Keep exploring