SOPs with no owner

An SOP with no owner is just a suggestion

The binder at the line holds three versions of the same document and not one of them has a name on it. Give every document an owner, a review date and one live version, and the standard starts holding.

By clicking "Schedule Demo," you agree to the use of your data in accordance with LeanSuite's Privacy Notice, including for marketing purposes.

The same finding

Why SOP compliance slips, week after week

Retrain and move on

The supervisor walks the operator through the sheet again and closes the finding. Nothing on the document changed, so the same finding is back next month, and the plant keeps working the operator instead of the standard.

Fix the document itself

If they want to upload something new for that, it will create a version two of the same document, so always, for the entire factory, the latest version of any document is available. It will make sure that if any document is coming to an expiration, it needs to get reapproved or get taken out of the circulation system so that nobody is able to get access to it because it is obsolete.

Sound familiar?

Three versions of the same SOP, none of them owned

Ask why SOP compliance slips and the honest answer is that the sheet at the line is older than the job. Someone changed a step, printed a fresh copy and left the laminated one on the wall. When an operator finds a step that is wrong, there is no name on the document to take it to. So they run it the way they were shown, and the binder becomes decoration.

Documents with no name

Three versions on the floor

Nobody can say which sheet at the station is the current one.

Nowhere to take a wrong step

The operator spots an error in the instruction and there is no owner to send it to.

Audit week scramble

When the audit is coming, everybody is running around.

Documents under control

An owner on every document

I can add an owner to this, and I can add an expiration to this as well, or to any document for that matter.

Only the latest version opens

It will stay there with the signature that the owner signed off on it and this is the latest version. If they want to upload something new for that, it will create a version two of the same document.

Sign-off on the dashboard

I can submit this and assign it to that individual or to a role, it will automatically show up on their dashboard that they need to do this today, and they can simply just sign off on it.

Before the software

What plants try first, and why it fades

1

A big SOP rewrite project

Everything gets updated in one push and the floor looks great for a quarter. Then the next process change lands and nobody is named to carry it into the document.

2

Laminate and post at the line

The sheet on the wall looks official, but it carries no revision and no owner. When it changes there is no way to pull the old one back off the wall.

3

A shared drive and naming rules

The folders hold the files, but nothing tells anyone a document is due for review. The old file still opens, and people cannot tell it from the new one.

How it works

One library. One owner. One live version.

Users have a way to build a hierarchical structure similar to what we get on Google Drive or SharePoint. You can add an expiration to that SOP, add an owner for that SOP, or any document for that matter. Then you can take that and assign those to people with certain schedules as well, so that you can watch the compliance.

  1. Bring every document into one place
  2. Put a name and a date on it
  3. Send it to the shift, not the wall
  4. Make the steps worth reading

Step 1

Bring every document into one place

You can build your repository of all those manuals, all the SOPs, all the OPLs in one place. Users have a way to build a hierarchical structure similar to what we get on Google Drive or SharePoint. And we can attach any documentation that is out there on the factory floor today, so you do not have to enter anything manually.

Step 2

Put a name and a date on it

I can add an owner to this, and I can add an expiration to this as well. Then it will help me to manage before that expiration is coming, to build the escalation plan in place, who should be approving this document. It will help send out notifications when the document is coming to expiration, and it needs to get reapproved or get taken out of the circulation system.

Step 3

Send it to the shift, not the wall

If I save and publish this, I can now assign it to whoever needs to see this. I can click on Create Schedule and assign it to an operator role, because we can create as many roles and add people to them, but we can individually assign this as well. It will automatically show up on their dashboard that they need to do this today, and they can simply just sign off on it.

Step 4

Make the steps worth reading

You can actually upload a video and it will analyze that video for you, and it created that SOP. It highlights the PPE, the tool requirement, and it breaks it down into step by step. What it also does is that it puts certain questions in between, so if you assign this SOP to somebody to sign off on, it will make sure to ask certain questions that are relevant to certain steps. So it is making sure that the person actually understood the SOP.

An SOP generated from a process video with numbered steps, frames and QR codes

If nothing changes

How a good SOP quietly stops being a standard

  1. Day one

    The sheet is written

    Someone documents the job properly and prints a clean copy for the station.

  2. A month in

    Two versions at the line

    A step changes, a new copy goes up, and the old laminated sheet stays where it was.

  3. Six months in

    Operators stop looking

    People run the job from memory because the sheet has been wrong before and nobody fixed it.

  4. Audit week

    The hunt begins

    You spend the week proving which documents are current and who approved them.

Angad Singh, Co-Founder of LeanSuite

From our co-founder

The biggest issue is there are multiple documents floating around that don't have any owners, that shouldn't be there because they're expired.
Angad Singh, Co-Founder, LeanSuite

Where to go next

Fix the document before you chase the owner

An unowned SOP is usually also an unreadable or out-of-date one, so the writing and the format are part of the same problem. These three pages cover how the instructions get written, how the forms around them get built, and how the steps reach the operator at the line.

See one of your own SOPs under control

Bring a document you use today and we will show it with an owner, a review date, version control and a sign-off from the floor.