download dots

📘 Write Down How the Work Is Done

Use answer-first prompts to design data models, approval matrices, executive reviews, portfolio risk systems, job costing, cash scenarios, vendor SLAs, commission trackers, retention dashboards, and customer health scorecards. Each prompt asks for the operating rules and evidence needed before generating an app or workflow.
  • Tested prompts
  • Edit for your use case
  • Works across models
  • Save in Taskade
Write Down How the Work Is Done

Copy

Our processes live in three people's heads and it is a real risk. Build me a process library. Keep one record per process with its name, purpose, the roles that perform it, the trigger that starts it, the steps written so someone new could actually follow them, the tools or systems involved, what a good outcome looks like, and the common things that go wrong. Give every procedure an owner, a version and a review date. Link procedures to the roles that use them, so a new starter in a role can see everything they need. Track which processes are documented and which are still undocumented, prioritised by how many people know them, since the ones only one person knows are the risk. Add an AI agent that takes a rough description of how something is done and drafts a structured procedure from it, asking about the steps that were skipped over, so writing one is a conversation rather than a project. Automate two things: a review reminder to each owner, and a prompt to review the relevant procedure after any incident or complaint. Two logins: a process owner who maintains their own, and an operations owner who sees coverage.

STATUS · LIVE
v1

01 / Spark - intelligence awakens

Write Down How the Work Is Done

Turn undocumented processes into owned, reviewed step-by-step procedures linked to the roles that use them.

// the spark catches · intelligence awakens · the answer unfolds

Most small operations run on what a few people know. This turns that into procedures with owners and review dates, which makes holidays, growth, and handovers survivable.

What's Included

  • One procedure per process written as steps someone can follow.
  • An owner and a review date on each.
  • Linked to the roles that use it so it is findable.
  • An assistant that drafts a first version from a description.

How To Use

  1. Write the steps someone new could follow, not a description of the process.
  2. Give each procedure an owner. Unowned procedures go stale immediately.
  3. Start with the processes only one person knows. That is the risk.
  4. Review after anything goes wrong. That is when you learn what was missing.

Control the versions with document control, and train against it with training matrix prompts.