Home
Hand Over Your Shift
End the shift by reviewing the operational record, adding the required context, submitting the report, and making it available to the incoming Supervisor.
Manage Standing Instructions
Standing instructions carry information that every shift must see for a period — an outage, an audit, a holiday roster — and clear themselves when that period ends.

Title and Copyright
This page identifies the guide, release, publication details, copyright, and terms of use.
Preface
This guide is for Supervisors and Round Planners who use the mRounds web application. It explains the conventions, related information, and support contacts used throughout the guide.
What Your Administrator Controls
Several parts of the web application are governed by permissions and tenant configuration, so a screen or option described in this guide may not appear for your account.
Overview of mRounds
As a Supervisor or Round Planner, use mRounds to design inspection work, schedule and assign rounds, monitor execution, review findings, and hand over the shift.
Get Started
Log in to the web application and find your way around its modules.
Start Your Shift
Accept the Shift Handover Report and find the rounds, Issues, and Actions you need.
Monitor the Shift
Use the dashboards together to understand compliance, identify exceptions, review workload, and open the rounds, Issues, or Actions that need attention.
Investigate Rounds That Need Attention
Investigate overdue, skipped, partly open, or exception-flagged rounds to understand what happened and route the finding to the correct follow-up process.
Follow Up on Findings
Decide whether a finding becomes an Issue, an Action, an ERP Notification, or a Gensuite Issue, and how each one is tracked to closure.
Hand Over Your Shift
End the shift by reviewing the operational record, adding the required context, submitting the report, and making it available to the incoming Supervisor.
- Understand Shift Handover Reports
  A Shift Handover Report transfers responsibility and context between shifts by keeping completed work, open items, exceptions, instructions, and supporting evidence together.
- Manage Standing Instructions
  Standing instructions carry information that every shift must see for a period — an outage, an audit, a holiday roster — and clear themselves when that period ends.
- Schedule a Standing Instruction
  Set up a standing instruction in advance for a future date range — for a planned outage, a scheduled audit.
- Generate and Submit the Shift Handover Report
  As the outgoing Supervisor, review the shift information, add the required context, and submit the handover for the incoming Supervisor.
- Share the Shift Handover Report
  Download or email a submitted Shift Handover Report when stakeholders need the same operational record outside the application.
Create Dashboards and Reports
Build custom dashboards, widgets, and transaction reports, and share dashboard data as PDF reports.
Create a Round Plan
Choose the starting method that suits the plan you need — manual, copy, template, Excel, AI, or ad hoc. The preparation that follows is the same for all of them, from defining scope to approval and scheduling.
Build the Round Content
Add the locations, assets, pages, sections, and tasks Operators will work through, or import them from a template or another round plan.
Configure Responses and Logic
Choose and configure the response type for each task, and add conditional logic for follow-up tasks and outcomes.
Get a Round Plan Approved
Preview a round plan, send it for approval, approve it, and review the approval audit trail.
Schedule Rounds
Schedule a published round plan to define when rounds are generated, when they are due, and which Operators or groups receive the work.
Maintain Round Plans
Modify round plans one at a time or in bulk, and archive, restore, or delete them.
Create and Maintain Templates
Choose between local and global templates, create templates manually, from existing ones, or with AI, and edit or archive them.
Response Types: What Each One Captures
Look up any response type to see what it records, when to choose it, how it behaves during execution, and where to configure it.
Administration
Set up Issue fields, Shift Handover Report content and delivery, shift log templates, template access, and approval and notification workflows.
Troubleshoot Common Problems
Use this guidance when planning, approval, scheduling, monitoring, reporting, or handover behavior does not match what you expect.

Manage Standing Instructions

Standing instructions carry information that every shift must see for a period — an outage, an audit, a holiday roster — and clear themselves when that period ends.

A standing instruction is not part of one shift's handover. It applies for the period you set, across every shift in that period.

The instruction expires on its own, so it does not have to be removed manually when the period ends.

Standing instruction or handover note

Use a standing instruction when the information applies to every shift across a period, whoever is on. Use a handover note in the Shift Handover Report when the information is about what happened on your shift and what the next shift should pick up. See Understand Shift Handover Reports.

The lifecycle


Stage	What happens
Write	Give the instruction a title and write the text. Rich text, color coding, titles and lists are available.
Schedule	Set the start and expiry times for the period the instruction applies to. See Schedule a Standing Instruction.
Appear	The instruction appears automatically when the period starts. On mobile, Operators see scheduled instructions only during their active period.
Revise	Edit the instruction while it is active. Each change is kept, so the wording in force at any past point can be reviewed. See Version history below.
Expire	The instruction stops appearing when the period ends. Nobody has to remove it.

Version history

Every change to a standing instruction is kept, so the wording in force at any past point can be reviewed and two versions can be compared.

Standing instructions get edited while they are in force. A pressure limit is tightened mid-outage, a contact name changes, a caution is added after a near miss. Version history keeps each of those states.

The history lists each saved version. Comparing two versions is faster than reading both, particularly when the change was a single number inside a long instruction.

Expired instructions are retained, so the record does not end when the period does.