Home
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.
Understand Round Plans and Rounds
A round plan defines what Operators inspect, where they work, how often the work occurs, and what they record. Scheduling the plan creates rounds that can be assigned and monitored.

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.
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.
- Understand Round Plans and Rounds
  A round plan defines what Operators inspect, where they work, how often the work occurs, and what they record. Scheduling the plan creates rounds that can be assigned and monitored.
- What's New for Supervisors in mRounds
  Review the Release 2605 changes that affect round authoring, templates, permissions, monitoring, attachments, and the web application experience.
- System Requirements
  Check the supported desktop operating systems, browsers, storage, and memory requirements before using the mRounds web application.
Log in to the Web Application
Sign in to the mRounds web application using the method configured by your organization. Your permissions determine which planning, monitoring, approval, and administration options appear.
Find Your Way Around the Web Application
Use the web application modules to plan rounds, schedule work, monitor execution, manage findings, review reports, and prepare shift handovers.
Accept the Shift Handover Report
As the incoming Supervisor, review and accept the previous shift’s handover before taking ownership of open rounds, exceptions, Issues, Actions, notes, and attachments.
Assess and Monitor the Shift
Use the dashboards together to understand compliance, identify exceptions, review workload, and open the rounds, Issues, or Actions that need attention.
Create and Prepare a Round Plan
Create a round plan by choosing the best starting method, defining its scope, building the Operator workflow, validating the mobile experience, and preparing it for approval and scheduling.
Review and Approve Round Plans
Review the plan before publication, record the approval decision, and use workflow configuration or audit history only when those administrative tasks are required.
Schedule and Assign Round Plans
Schedule a published round plan to define when rounds are generated, when they are due, and which Operators or groups receive the work.
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.
Choose an Issue, an Action, or an ERP Notification
Choose the follow-up record that matches the finding, then track it through ownership, progress, resolution, or enterprise maintenance processing.
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.
Configure Dashboards and Reports
Create reusable dashboards and reports when the standard shift views do not provide the combination of metrics or detail the organization needs.
Find Rounds, Issues, and Actions
Use search when you know identifying details for a record, and apply filters when you need to narrow a larger list of round plans, scheduled rounds, Issues, or Actions.
Troubleshoot Common Problems
Use this guidance when planning, approval, scheduling, monitoring, reporting, or handover behavior does not match what you expect.
Administration and Governance
Use these occasional configuration and governance tasks to control templates, permissions, email delivery, handover setup, and retained content outside the daily shift workflow.

Understand Round Plans and Rounds

A round plan defines what Operators inspect, where they work, how often the work occurs, and what they record. Scheduling the plan creates rounds that can be assigned and monitored.

Round plan and round

A round plan is the reusable design for an inspection. It contains the route, locations or assets, pages, sections, tasks, response types, guidance, and any conditional logic required in the field.

A round is one execution of that plan. When you publish and schedule a plan, mRounds generates rounds for the selected dates, shifts, users, or groups. Operators complete those rounds in the mobile app, and you monitor the resulting status, readings, exceptions, Issues, and Actions from the web application.

Why well-designed rounds matter

They turn inspection requirements into clear, repeatable field work.
They help Operators capture complete and consistent data instead of relying on memory or paper notes.
They make abnormal readings and missed work visible so teams can respond earlier.
They provide a history that supports maintenance decisions, compliance reviews, and shift continuity.
They reduce rework by giving Operators the right guidance, units, limits, and response choices at the point of work.

Building blocks

Element	Purpose
Route, location, and asset	Define where the Operator works and the order in which equipment is visited.
Page and section	Organize long inspections into manageable groups.
Task	Describe one inspection check or required field action.
Response type	Define how the Operator records the result.
Guidance and logic	Explain what to check and show the correct follow-up based on the response.
Schedule and assignment	Define when rounds generate and who receives the work.

Round lifecycle

A plan normally moves from Draft to Published, then becomes scheduled work. Generated rounds may appear as Open or Assigned, move to In Progress while an Operator works, and end as Submitted, Skipped, Overdue, or another configured status. Use the status and recorded findings to decide whether follow-up is required.