---
title: "SOP software that Claude and your team both follow · Projectify"
description: "SOP software that learns a procedure from a recording and turns it into steps people and Claude both follow, with checks where a person must look."
url: https://projectify.si/for/sops
---

# SOP software that Claude and your team both follow.

> Record yourself doing the task once. Projectify writes the summary, the diagram, the steps and a quiz, then turns it into a workflow your team and Claude run the same way, stopping where a person must check.

Start free: https://app.projectify.si/signup. A month of Premium free, no card. Agents never take a seat.

## Why SOPs end up in a folder nobody opens.

- "We write SOPs, and then nobody reads them." Here an SOP is a workflow people and Claude run, not a page to look up. The steps are the work, so they stay in use.
- "Writing a procedure down takes longer than doing it." Record yourself doing it, or drop in the doc you have. Projectify drafts the steps, prompts and checks for the owner to correct.
- "Everyone has their own shortcut, and the good ones never spread." A trick you teach becomes a technique Claude picks when it fits, and it shows in the workflow for the next person too.

## One procedure, followed the same way by everyone.

- **Learns a procedure from a recording.** Drop in a video, a link or a document. Projectify explains it with a summary, diagram, steps and a quiz, then drafts the workflow. For example: Refund approval: 9 steps, 1 check, a five-question quiz.
- **Stops where a person must look.** Mark the steps that need human judgement. A run stops there and waits in Approvals, whoever is running it. For example: Refund over $200 waits for Bruno.
- **Runs it for every row.** Run the procedure once, or for a list of orders, stores or suppliers. Claude works through the list and stops at each check. For example: Supplier check: 23 of 30 done, two flagged for you.
- **Finds the right version.** Every SOP document added is read and searchable down to the words inside, so the question “which form do we use?” has one answer. For example: Damage claims use form C2, see Courier claims v2.

## The board it starts with

- Statuses: To write, Drafting, Owner review, In use, Needs update, Retired
- Fields: Process owner, Team, Version, Last reviewed, Source recording, Next review
- Views: Board, List, Outline, Checklist, Calendar
- A workflow, Recording to SOP: Drop in the recording → Summary, diagram and steps → Owner corrects the steps (a person checks) → Mark the checks for a person → Quiz for new starters → Owner approves version one (a person checks)

## Before you rewrite the binder.

### How is this different from process documentation software?

Process documentation software keeps the write-up. Here the write-up is also the workflow, so people and Claude run the same steps and the checks stop for a person.

### What if Claude gets a step wrong?

The steps that matter are checks: the run stops and waits in Approvals until a person looks. Every change Claude makes is signed and can be undone.

### Can we bring our existing standard operating procedures?

Yes. Drop each document in and Projectify turns it into steps, prompts and checks; the original stays in Files, read and searchable.

### Do procedures run on a schedule?

Not on their own. A person runs a workflow once or for many rows; for daily and weekly work, a routine gives the team a checklist ticked by day.

Related: [Workflow management](https://projectify.si/for/workflow-management.md), [AI workflow automation](https://projectify.si/for/ai-workflow-automation.md), [Employee onboarding](https://projectify.si/for/employee-onboarding.md), [Client onboarding](https://projectify.si/for/client-onboarding.md), [HR teams](https://projectify.si/for/hr-teams.md). Every kind of work: [For your work](https://projectify.si/for.md).