← Explore BMO HRM

BMO SOP module

Every policy read, understood and signed. On any device.

Turn policies, onboarding, checklists and emergency procedures into step-by-step walk-throughs your staff finish on a PC or their own phone, with quizzes, e-signatures and a record you can show an auditor.

  • Sign by QR code on the phone
  • English · Bahasa Melayu · 中文
  • 8 step types
  • Tamper-evident register
  • Prepared → reviewed → approved
Final acknowledgement page on a laptop with a QR code, next to a phone where the employee types their name and signs with a finger

Product screenshots use fictional demo company and employee data.

Why

“Please read the attached policy” is not proof

Paper forms get lost, emails get ignored, and when an auditor or a client asks who agreed to which version, nobody can answer quickly.

Built once by HR

Upload the PDF you already have, or build steps: read, quiz, video, checklist, form. Publish in three languages.

Done by staff anywhere

Desktop or phone, no app to install. One step at a time, then a signature on screen or by scanning a QR code.

Kept as a record

Every signature lands in an acknowledgement register with a certificate, coverage reports and an audit log.

How it works

Create, assign, track

Three steps for the admin. Four for the employee: open, go through, tick, sign.

Create

Upload a PDF or Word file and it becomes a signable SOP in a minute. Or build one step by step.

Upload a document dialog with file, title, message and publish options

Assign

Give it to everyone, a department or chosen people, with a due date. New joiners can get it automatically.

New assignment dialog: choose the SOP, who gets it and the due date

Track

See who has finished, who is in progress and who is overdue, down to the step where each person stopped.

Assign and Progress list with progress bars and overdue employees highlighted

For HR and managers

Everything in one dashboard

Library, programs, assignments, acknowledgements, reports and settings, one tab apart.

See what needs attention today

The dashboard shows SOPs in progress, overdue staff, the on-time rate, signatures in the last 30 days and SOPs due for review. Click any number to see the people behind it.

SOP Dashboard with key numbers, overdue list and SOPs completed per month

A library for every SOP

Policies, onboarding, checklists, drills and emergency procedures in one list, with status, version, languages and how many people have signed.

  • Upload an existing PDF or Word document
  • Add ready-made SOPs in English, Bahasa Melayu and Chinese
  • Preview as an employee, print a controlled copy
SOP Library listing SOPs with status, steps, languages and assignment counts

Build steps, not paperwork

Mix step types to fit the SOP. Each new step can start from a ready example, so nobody starts from a blank box. Publishing locks the content as a version; changes become a new version, and you choose whether people sign again.

SOP editor with the list of steps, translation badges and document details
Read & agreeA policy or document with a minimum reading time.
SignTyped name and finger or mouse signature.
ChecklistItems to tick, with photo evidence if needed.
QuizMultiple choice with a pass mark and retry.
VideoYouTube, Vimeo or an uploaded MP4.
Upload a fileStaff submit a photo or document.
FormText, date, number, choice and yes/no fields.
InformationContent only, with a Next button.

Programs for onboarding

Bundle the welcome pack, IT policy, data notice and code of conduct into one program. Assign it once, or let every new joiner in a department get it automatically. Staff sign once at the end.

  • Steps in order, or in any order
  • Re-acknowledge every N months
  • Due dates from assignment or from joining date
Edit program: New Employee Onboarding with seven SOPs in order, names in three languages and days to complete

Reports and a full audit log

Coverage by SOP and by department, overdue lists, quiz results, checklists and drills. Every admin action (publish, assign, reset, setting change) is logged with who and when. Export to Excel (CSV).

SOP Reports with coverage per SOP Audit Log with filters and list of admin actions

Help on every page

A guided tour highlights each part of the page the first time someone opens it. Picture guides and the full user guide are one click away, so new admins get going without training.

Guided tour bubble explaining the dashboard numbers

For employees

Simple enough to need no training

Staff open My SOPs, see what is due, and go through one step at a time. Progress is saved, so they can stop and continue later.

  • Works in the phone browser, no app to install
  • Documents open inline; quizzes show what to fix and allow a retry
  • A certificate at the end, and nothing to email back
Three phones showing My SOPs, a security quiz, and the signed confirmation

Read the real document, then agree

Upload the PDF you already use. On a computer, staff read it right on the page with page numbers, zoom and print, in the same layout as your printed copy. On a phone it opens with one tap.

  • “I agree” stays off until they scroll to the end and tick the statement
  • The record shows the exact file and version they read
  • Word, Excel and image files can be attached too
Employee reading the attached Lockout / Tagout procedure PDF inside the SOP page; call-out of the ticked statement and the enabled I agree button

See the sample

From PDF to acknowledgement and signature

Open the sample document, then explore the screens staff use to read, agree and sign. These examples use the fictional company ABC Sdn Bhd.

Preview the sample PDF on this page

ABC-SAF-007 · Lockout / Tagout (LOTO) Procedure · Version 2.0 · 2 pages · SAMPLE

If the PDF does not display in your browser, use Open sample PDF in a new tab.

Employee reading the sample Lockout / Tagout PDF, with the I agree button still disabled
1. Read the PDFThe attached document opens in the SOP reader.View full-size screen (new tab)
Sample SOP reader scrolled to the end of the PDF, with the acknowledgement ticked and I agree enabled
2. Acknowledge the documentScroll to the end and tick the statement to agree.View full-size screen (new tab)
Sample final acknowledgement page with typed-name and signature options and a QR code for phone signing
3. Sign the acknowledgementType a name and sign on screen, or scan the QR code to sign on a phone.View full-size screen (new tab)

Sign on your phone with a QR code

On a shared office PC, staff point their phone camera at the QR code, type their name and sign with a finger. The PC screen completes by itself.

  • One-time link that expires after 15 minutes
  • Or sign on the screen with a mouse or finger
  • The name must be typed; it is never filled in for them
Final acknowledgement page with the document ticked and a QR code to sign on the phone

English, Bahasa Melayu and 中文

Write the SOP once, add translations, and each employee reads in their own language. The register records which language they read and signed in.

The same Code of Conduct step on three phones in English, Bahasa Melayu and Chinese

The record

Proof you can show an auditor

Each signature is one line in the acknowledgement register, chained to the one before it with a fingerprint. If a record is changed or deleted, the register shows it.

WhoEmployee name, number, department and typed name
WhatSOP, version and language read
WhenStarted, finished all steps, signed
HowSignature image; computer or phone (QR)
Where fromIP address and browser / device
CheckRecord fingerprint, verified on every view
Acknowledgement record with version, language, dates, signature and an intact record check

A certificate for every signature

Print or save a one-page certificate with the employee, SOP, version, date, signature and record fingerprint. Export the whole register to Excel (CSV) for an audit or a client.

Certificate of Acknowledgement with document table and signature

Document control

Version control an auditor can follow

Who wrote this version, who checked it, who approved it, and which version each employee signed. One page answers the questions an ISO audit or an incident investigation will ask.

Prepared, reviewed, approved

Each SOP names its reviewer and approver. A new version goes to them for review and approval, and staff only see it after the approver signs it off.

  • Each sign-off: a tick, a comment and an e-signature
  • The person who prepared a version cannot review or approve it
  • Return for changes, with the reason recorded
  • Locked while under review; a content fingerprint proves the approved version is the one published
Reviewer signing version 1.1 of the Fire Evacuation Procedure: confirmation tick, comment and signature box

One version control record per SOP

Every version of the SOP with what changed, who prepared, reviewed and approved it (with signatures), which files were uploaded and by whom, and when it was published, took effect and was replaced.

  • Full approval trail with date, comment, signature and IP address
  • Open or print any earlier version, for example 1.0 when 1.1 is current
  • Old copies print stamped SUPERSEDED, “do not use for work”
  • Print the whole record for the audit file
Version control record for the Lockout / Tagout procedure with revision history and signatures, next to a printed version 1.0 stamped SUPERSEDED

Who signed which version

Every employee against every version: signed, covered by an earlier signature after a small correction, in progress, overdue or not signed. Did Ali sign 1.0? Does 1.1 need a new signature? It is all in one table.

  • Filter by department, include former staff
  • Export to Excel (CSV)
  • Print an all-employee progress report: given, due, started, signed, time taken
Table of employees against versions 1.0, 1.1 and 2.0 showing signed, covered by earlier signature, in progress and overdue

Incident check

After a machine breakdown or a near-miss, pick the employee, the SOP and the date and time. You see which version was in force, who prepared, reviewed and approved it, and whether that employee had read and signed it, with their full history.

  • Print it as an evidence report with an incident reference
  • It lists the facts; deciding responsibility stays with management
Incident check for Ali bin Abu and the Lockout / Tagout procedure: version 2.0 was in force and he had not yet signed it, overdue at the time

Emergency procedures, two taps away

Fire, medical, flood, power outage: published emergency SOPs get their own page with the emergency number, assembly point and contacts. Print a wall poster with a QR code that opens the same page on any phone.

Emergency wall poster with QR code next to a phone showing the emergency procedures page

Ready-made examples

Ten industry case studies to start from

Each sample shows the flow, the setup and the result. Add one to your library as a draft, adjust the wording, publish.

Corporate officeNew employee onboarding
Professional servicesNew client sign-up (KYC)
F&BDaily kitchen opening & food safety
RetailCash handling & store closing
ManufacturingMachine safety: lockout / tagout
ConstructionSite safety induction in 3 languages
HealthcareInfection prevention & hand hygiene
LogisticsForklift daily pre-use inspection
HospitalityHousekeeping standards & room check
FinanceAnnual anti-bribery & conflict declaration
Samples gallery with industry case study cards

Questions

Do employees need to install an app?

No. Staff use their normal BMO login in any browser, on a PC or a phone. Signing by QR code needs only the phone camera.

Can I use the policy documents I already have?

Yes. Upload a PDF, Word, Excel or image file (up to 20 MB). PDFs open directly on the page and on phones. The SOP is ready to assign in about a minute.

Can I add training videos?

Yes. Paste a YouTube or Vimeo link, or upload an MP4 or WebM file up to 100 MB. For uploaded videos you can require a minimum percentage watched.

What is recorded when someone signs?

The typed name, the signature image, the SOP and its version, the language read, the date and time, whether it was signed on a computer or a phone, the IP address and the browser or device.

What happens when a policy changes?

Make a small correction (for example 1.0 to 1.1, no re-signing) or a major change (to 2.0, everyone signs again). Earlier signatures stay recorded against the version people actually signed.

Who approves an SOP before staff see it?

When review and approval is switched on in SOP Settings, each version is prepared by an SOP admin, then reviewed and approved by the people named on that SOP, who sign electronically. Only the approver's sign-off publishes it, and the person who prepared a version cannot review or approve it.

Can I see which version each employee signed?

Yes. The version control record shows every employee against every version: signed, covered by an earlier signature after a small correction, in progress, overdue or not signed. Earlier versions can still be opened and printed; printed old copies are stamped SUPERSEDED.

Which languages are supported?

English, Bahasa Melayu and Chinese. You write the SOP once and add translations; each employee picks their language.

Is it part of BMO?

Yes. It is a module inside BMO (login.bmo.my), using your existing employees, departments and permissions.

See it with your own policies

We will set up a demo with one of your documents, so you can sign it on your own phone.