Every procedure current, and in front of the people who run it.

Write each procedure once, have it approved by the people who own it, and put the current version in front of the line, the lab or the team that runs it. Every change is approved, sent and acknowledged again.

30-day trialUnlimited free viewersNo credit card required

From draft to the line, in five steps

One procedure, start to finish. Each step links to the part of the product that does it.

  1. 01

    Write it, or bring it

    Draft the procedure in AllyMatter, or upload the PDF you already use, and keep forms and records beside it.

    Versions and Reviews
  2. 02

    Approve it

    Quality, the supervisor and anyone else who owns it approve in order, up to four steps.

    Approval Workflows
  3. 03

    Put it in front of the people who run it

    Tag people by site, line, shift or team. Each procedure reaches only them, new starters included.

    Policy Distribution and Access
  4. 04

    Change it safely

    A change becomes a new version. The team keeps the current one until the new one is approved, then everyone is asked again.

    Versions and Reviews
  5. 05

    Show who has the current version

    Each acknowledgment is recorded by person and version. Filter it, export it, or attach the training records.

    Audit Trail and Export

The current version on the line

Operators open the current version only, download a PDF for the line, and acknowledge it there.

Forms and evidence beside it

Attach the forms, certificates and training records that go with each procedure.

Who asks to see it

Inside the company and outside it, people ask the same question: is this the approved procedure, and is it the one in use.

Inside the company

  • SupervisorsWhether everyone on the shift has the current procedure.
  • QualityWhich version is in use, and who approved the change.
  • Training leadsWho has acknowledged a procedure since it changed.
  • Operations leadershipThat procedures are current at every site.

Outside it

ISO 9001, clause 7.5.3

Control of documents

The current version available where it is used, protected, and changes controlled, with obsolete documents kept out of use.

  • Only the current version reaches the floor
  • Every change approved first
  • Earlier versions kept in history

ISO 13485, clause 4.2.4; 21 CFR 820

Medical device document control

Documents reviewed and approved before issue, changes approved, the current version at the point of use, and obsolete versions kept out of use.

  • Approval before issue, on record
  • The current version at the point of use
  • Every earlier version kept

29 CFR 1910.147(c)(4)

Energy control procedures

Machine-specific procedures are documented and used, and the people who service the equipment are told whenever one changes.

  • One procedure per machine, sent to maintenance
  • Each change approved, then acknowledged again
  • Training records attached

Wherever you operate

Local and customer rules

Customers, sectors and countries add their own procedure requirements. Each gets its own procedure beside the core set.

  • A procedure for each site or customer
  • Sent only to the teams who run it
  • Each change goes out again

Bring your own rules

Your region’s laws, the standards your customers ask for, and your own house rules. Write each one as a policy, approve it, and send it to the people it covers.

  • Laws of every country and state you work in
  • Standards and certifications
  • Customer and contract requirements
  • Your own policies and procedures
Check what your laws requirePolicy and Compliance lists the documents a business has to have in writing, by country and business type.Check your laws (opens in a new tab)

For every procedure people follow

From the line and the lab to the support desk and month-end close.

  • Changeover procedures
  • Work instructions
  • Lockout/tagout procedures
  • Calibration procedures
  • Cleaning and sanitation
  • Lab test methods
  • Incident response runbooks
  • Customer support playbooks
  • Month-end close
  • New starter checklists

Who can do what

EditorsWrite procedures, send them for approval and acknowledgment, and set review dates.
ApproversQuality, supervisors and owners, in order. Any role can approve.
ViewersSee the current procedures that cover them, download a PDF and acknowledge. Free.
AdminsManage people and tags by site, line and shift, and see the workspace log.

Need help writing the policies? Find a consultant for your standard.

Questions

Do operators need a paid seat?

No. They read, acknowledge and download procedures as viewers, free of charge.

How do we keep old versions off the floor?

People see the current version only. Earlier versions stay in history for editors and admins.

Can a supervisor approve procedures?

Yes. Add supervisors, quality or anyone else as approvers, in up to four steps.

Can we attach forms and records?

Yes. Attach forms, certificates and training records to the procedure they belong to.

What happens when a procedure changes?

It becomes a new version and goes through approval. Once approved, everyone it covers is asked to acknowledge it.

Can we bring the procedures we already have?

Yes. Upload a procedure as a PDF, or draft it in AllyMatter. On a yearly plan, we move your documents in for you.

Try AllyMatter free for 30 days

  • No credit card needed
  • 30-day money-back guarantee
  • Free migration on yearly plans