Standard operating procedure form: how it works and how to set it up

A standard operating procedure form turns a written procedure into something staff actually complete, step by step, with a record of who did what and when. The procedure document says what should happen. The form proves it happened, and the submission starts the next step without anyone remembering to pass it on. This article answers one question: how do you build internal procedure forms on the levelpartner.ai platform so a process such as client onboarding runs the same way whoever is on shift?

Why procedures fail without a form

Most companies with 30 or more staff have procedures written down somewhere. The trouble is that a document cannot tell you whether it was followed. A new starter skims it once. An experienced colleague skips the step they think is pointless. When a client complains, nobody can say which step was missed.

A procedure form fixes that by making each critical step a question the person must answer. Did you send the engagement letter? Which date was the kick-off booked for? Who is the account owner? The answers are stored against the client's contact record, so the history is in one place, and a workflow can act on them straight away.

Which procedures deserve a form

Not every procedure needs one. Use a form where the process runs often, involves a handover between people, or carries a cost when a step is missed. Good candidates include:

• client onboarding after a sale closes
• a case handover between a sales adviser and an administrator
• a monthly account review for retained clients
• a property listing checklist before marketing goes live
• a complaint log that must reach a manager within a set time

Leave out one-off tasks and anything that takes a single action. A form for a two-minute task becomes a form people fill in after the fact, from memory.

Before you start

You need access to Sites, Automation and Settings. Have the written procedure in front of you and mark the steps where a missed action causes real damage. Those become form questions. Agree who completes the form and who receives the result. Create custom fields for answers you want to see on the contact, such as onboarding date or account owner.

How to set it up

1. Pick one procedure and list its steps in order.
2. Turn each step that needs confirming into a yes or no question.
3. In Settings, open Custom Fields and create fields for contact answers.
4. Go to Sites, then Forms, and click + Create New Form.
5. Put the client's email first, then the confirmation questions in order.
6. Add a text field labelled "Anything not done, and why".
7. Click Conditional Logic, then Add New Condition, and choose Message.
8. Show a reminder message when any confirmation is answered no.
9. Save, preview and submit a test entry.
10. In Automation, create a workflow with the Form Submitted trigger.
11. Add an If/Else action that checks for any no answer.
12. On that branch, add Send Internal Notification to the procedure owner.
13. Publish the workflow, then click Integrate to copy the form link.
14. Paste the link into the written procedure at the right point.

How it runs day to day

The person doing the work opens the form at the end of the procedure, answers the confirmations and submits. That takes two or three minutes. The workflow then tags the client, assigns the next task and, if something was skipped, tells the owner. The owner's job shrinks from checking every case to reviewing only the exceptions.

What it replaces

The form replaces the onboarding spreadsheet, the handover email that says "all done", and the monthly meeting where someone reads through cases looking for gaps. Building it takes an afternoon. Keeping it current takes a few minutes whenever the procedure changes, because the form must change at the same time.

When a form is the wrong tool

If the procedure is mostly automatic, such as sending a welcome email and booking a reminder, build it as a workflow and skip the form. If several people must approve one case in sequence, you need approval steps rather than a single confirmation; routing a submission through approvals covers that. When procedure forms multiply across teams, keeping a growing set of forms under control helps with naming and owners. And for planning which internal paperwork to move first, read moving paper processes online in the right order.

Troubleshooting

Submissions do not attach to the client. Staff type the client's email slightly differently each time. Make the email field required and ask staff to copy it from the contact record.

The owner never receives exception alerts. The branch checks for the wrong answer value. Match the exact option text in the condition, then test with a "no" answer.

Staff fill in the form days later. The link is buried. Put it at the point in the procedure where the work finishes, and add a reminder task when the procedure starts.

The form and the written procedure disagree. Someone updated one and not the other. Name one owner for both and change them in the same sitting.

Frequently asked questions

Is a standard operating procedure form the same as an SOP document?

No. The document explains how to do the work. The form records that it was done and starts the next step.

Can clients see internal procedure forms?

Only if you share the link with them. Procedure forms are shared internally, usually linked from the written procedure or a staff page.

How many questions should a procedure form have?

As many as there are steps that cause damage when missed. For most procedures that is between five and ten.

Can a procedure form create a task for someone else?

Yes. The workflow started by the form can assign a task to a named user or to whoever owns the client.