An SOP and quality checklist app with proof of completion

Most companies already have standard operating procedures. They live in a binder on a shelf, a shared drive folder nobody can find, or the head of the one person who has been there longest. The checklists that are supposed to put those procedures into practice live on clipboards, and a clipboard full of ticks tells you very little. It does not tell you whether the step was done, when it was done, who did it, or what happened when something failed.

An SOP and quality checklist app closes that gap. It turns each procedure into steps that people complete on a phone or tablet, captures proof as they go, and turns every failure into a fix someone owns. This guide walks through the problems with the current way, everything the app should contain, a plain-words request you can hand to FORGE, a rollout plan, the mistakes that sink these projects, and how to measure the result.

What the current way costs you

• Ticks without evidence. A paper checklist with every box ticked at 4:59 p.m. in the same pen is a familiar sight. Nobody can tell which checks were real.
• Failures that go nowhere. When someone marks a step as failed on paper, the sheet goes in a folder. The leak, the misaligned guard or the out of spec reading waits until someone happens to notice again.
• Old versions in circulation. The procedure changed in March, but the laminated copy on line two is from last year. People follow what is in front of them.
• No view across shifts or sites. A manager cannot see which locations skip the closing checks or which step fails most often without collecting and reading stacks of paper.
• Audits become scavenger hunts. When a customer, an inspector or a certification auditor asks for records, someone spends days pulling binders and hoping the right sheets are there.
• Training depends on shadowing. New people learn the procedure from whoever is on shift, including that person's shortcuts.
• Rigid inspection software rarely fits. Packaged audit tools can be strong, but teams often bend their process to the tool's template, pay per user for people who only complete checks, or give up when a step does not fit the tool's field types.

What the app should contain

Roles

• Operator or crew member: completes assigned checklists, attaches proof, reports problems.
• Supervisor or lead: assigns checklists, reviews completed ones, signs off, assigns corrective actions.
• Quality or operations manager: owns the templates and SOP library, sees reports across sites, closes corrective actions.
• Owner or admin: manages people, sites and access.

The SOP library

• Each SOP has a title, number, version, effective date, owner, the steps in plain language, photos or diagrams of the right result, safety notes, and a list of changes from the last version.
• Every checklist step can link to the relevant SOP section, so help is one tap away.
• When an SOP changes, people assigned to it are notified and, if you want, asked to confirm they have read the new version.

Checklist templates

Each template is a list of steps. Each step has:

• The instruction: short, one action.
• A response type: pass or fail, yes or no, a number with an acceptable range, a choice from a list, free text, a photo, a signature or a scan of an equipment code.
• Required evidence: whether a photo or note is required, always or only on failure.
• Critical flag: whether a failure on this step stops the job or needs a supervisor immediately.
• Assignment rules: which site, line, shift, product or piece of equipment the checklist applies to, and how often it runs (each shift, daily, weekly, per batch, per job).

Completed checklists

• Who completed it, where, which template version, start and finish time, each response with its time, all photos and readings, and the supervisor sign-off.
• Statuses: Scheduled, In progress, Submitted, Reviewed, Failed items open, Closed.
• A completed checklist cannot be edited after sign-off. Corrections are added as notes with a name and time, so the original record stays intact.

Corrective actions

• Opened automatically when a step fails, or manually by a supervisor.
• Fields: what failed, where, severity, owner, due date, root cause, action taken, proof of the fix, who verified it.
• Statuses: Open, In progress, Waiting on parts or vendor, Fixed, Verified, Closed.

Screens

1. Today: each person's assigned checklists, what is due, what is overdue.
2. Run a checklist: one step at a time on a phone, large buttons, camera ready.
3. Supervisor review: submitted checklists waiting for sign-off, failed items highlighted.
4. Corrective actions board: every open action by owner and due date.
5. SOP library: searchable, with the current version clearly marked.
6. Reports: completion rate, on-time rate, failure rate by step and site, corrective action aging.

Notifications

• A reminder before a scheduled checklist is due, and an alert to the supervisor when it is missed.
• An immediate alert on any critical step failure.
• A notice to the owner of each corrective action, with reminders as the due date nears.
• A weekly summary for the manager.

Example request

Example request: "Build a quality checklist app for our two production sites. Quality managers create checklist templates and link each step to the matching section of our SOPs, which have a number, version, effective date and owner. Steps can be pass or fail, a number with a minimum and maximum, a photo, or a signature. A photo is required on every failed step, and a number outside the range counts as a fail. Mark some steps critical, and when one fails, alert the shift supervisor right away. Assign the startup checklist to every line at the start of each shift and the changeover checklist whenever an operator starts a new product. Operators complete checklists on a tablet at the line. Supervisors review and sign off. Every failed step opens a corrective action with an owner, due date, root cause and proof of the fix, and a quality manager verifies it before it closes. Once signed off, a checklist cannot be edited, only added to with notes. Show a dashboard of completion, on-time and failure rates by site, line and step, and a list of overdue corrective actions. When an SOP changes, notify everyone assigned to it and ask them to confirm they read it."

Paper, spreadsheet, packaged tool or your own app

Rollout plan

1. Pick the checklist that costs you the most. The one tied to customer complaints, rework, safety findings or audits. Start there, not with all forty templates.
2. Clean up the SOP first. Walk the procedure with the people who actually do it. Remove steps nobody does, add the steps everyone does but nobody wrote down.
3. Decide where proof matters. Not every step needs a photo. Require evidence on critical steps and on every failure.
4. Build and run it yourself. The quality manager completes the checklist on the real line, on the real device, wearing gloves if the crew wears gloves.
5. Pilot on one shift for two weeks. Keep the paper version as a backup only for the first two days, then retire it.
6. Review failures every day during the pilot. The fastest way to win trust is to fix what the checklist finds.
7. Add templates one at a time. Each new template goes through the same walk, build and pilot.
8. Retire the binders. Once the app is the only place the current SOP lives, old copies come off the wall.

Mistakes to avoid

• Copying a forty-step paper form one for one. Long checklists get rushed. Group steps, cut what does not matter, and split long checklists by area.
• Making every step require a photo. People will photograph the floor to get through it. Ask for evidence where it proves something.
• No owner for corrective actions. An action assigned to "maintenance" is assigned to nobody. Every action names a person.
• Editing completed records. If people can change a past checklist, the records are worthless in an audit. Lock them and allow notes.
• Changing templates without versions. You need to know which version of a checklist was used on a given date.
• Measuring completion only. A site with a perfect completion rate and zero failures may be the site not checking.

How to measure that it works

• On-time completion rate by site and shift.
• Failure rate by step: which steps fail most, and whether that changes after you fix the root cause.
• Corrective action aging: how many actions are open past their due date.
• Repeat failures: the same step failing at the same place again within a month.
• Downstream results: rework, customer complaints, returns or incidents connected to the processes you check.
• Audit preparation time: how long it takes to pull records when asked.

Checklist before you build

1. Choose the first procedure and gather its current SOP.
2. Walk the procedure with the crew and rewrite the steps in plain words.
3. Mark critical steps and decide what proof each step needs.
4. Set acceptable ranges for every measured value.
5. Decide who completes, who reviews and who verifies fixes.
6. Decide how often the checklist runs and what triggers it.
7. Define corrective action fields, owners and due dates by severity.
8. Choose devices and test them where the work happens.
9. If you are certified or regulated, confirm your record requirements with your auditor or advisor.

How FORGE handles it

With FORGE, your quality or operations manager describes the app in plain words, like the example above. A panel of top AI models plans the tool, a dedicated AI crew builds it, and every piece is checked for quality and security before it is saved. Most teams have their first real tool the same day, on phones, tablets and desktops.

The app lives inside your company, and people join only by invite. Roles decide who builds and who only completes checklists, and app users are free, so putting a tablet on every line never becomes a budget question. FORGE keeps a complete record of who did what, so you always know who changed a template and when. When a procedure changes, the builder describes the change, and it counts as a small fraction of a build only when something actually changes.

It is $49 a seat a month for each person who builds, with 3 builds included. Our team onboards every company starting with a workflow workshop. Talk to us and bring the checklist that causes you the most trouble.

Questions people ask