Home
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.

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.
- Create an Issue
  Create an Issue from the web application when a reported equipment condition or inspection finding requires investigation and ownership.
- Track Ongoing Issues
  Monitor open and in-progress Issues to understand priority, ownership, due dates, and whether follow-up is moving toward resolution.
- Update and Close an Issue
  Review the recorded resolution and close an Issue when the abnormal condition has been addressed and no further investigation is required.
- Create an Action
  Create an Action when follow-up work needs its own assignee, priority, and due date under the configured workflow.
- Monitor Actions
  Monitor Actions to see which follow-up activities are open, in progress, overdue, or ready for review.
- Update and Close an Action
  Review the completed follow-up and close the Action when its outcome has been recorded and no further work is required.
- Create ERP Notification for an Asset
  Create an ERP notification when a round finding must enter the organization’s enterprise maintenance process for further planning or execution.
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.
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.

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.

Use this decision after reviewing a round or exception and determining that the finding needs follow-up beyond the submitted response.

Table 1. Choose the follow-up record
Use...	When...
Issue	A round or observation surfaces an anomaly, such as an Observation, Maintenance condition, Incident, Near Miss, or Hazard, that needs tracking and investigation.
Action	A separately assignable follow-up activity is needed with its own priority, due date, and assignee, and the configured workflow allows an Action to be created.
ERP Notification	The finding must enter the organization's enterprise maintenance process. The notification is created from an Issue: automatically when the Issue Category is Maintenance or when Convert to ERP Notification is turned on, or by clicking Create on an existing Issue. This path requires SAP integration and the applicable configuration.
Gensuite Issue	The follow-up belongs in EHS rather than maintenance. The finding details are sent to Gensuite and the reference is stored with the mRounds record. Requires Gensuite API access and field mapping.

Send a finding to Gensuite

When a finding's follow-up belongs in EHS rather than maintenance, create the Gensuite Issue from mRounds so the two records stay connected. Creating the Gensuite Issue from mRounds saves entering the same details twice.

The finding details are sent to Gensuite and the Gensuite reference is stored against the original mRounds record, so you can trace either one from the other. Several findings from the same round can be sent together.

Before you can use it: Gensuite API access must be configured for your tenant, with locations, categories, and required fields mapped. See What Your Administrator Controls.

Convert to an ERP notification when it is maintenance work — see Create ERP Notification for an Asset. Keep it as an mRounds Issue when your own team will investigate and close it.

Continue the follow-up

Create the selected record with the finding and supporting details.
Assign or route it according to the configured workflow.
Monitor progress from Issues, Actions, or the ERP notification history.
Resolve and close the mRounds record after the required outcome is recorded.

Return to Investigate Rounds That Need Attention to continue monitoring the shift.