FAQs

R2 Utility is a recording and reporting platform designed to manage operational records within a connected system. The platform allows users to track locations, assets, tasks, notices, and reports while maintaining a clear history of activity across those records.

The system is designed to support flexible workflows. Core records such as locations, assets, and tasks can exist independently or be connected together depending on how an organization structures its operations.

R2 is built around several core record types including locations, assets, tasks, notices, and reports. These records can exist independently or be linked together depending on the workflow being performed.

For example, an asset can be associated with a location, a task can be assigned to an asset, and a notice can be applied to either a location or an asset. This structure allows users to organize operational data while maintaining clear relationships between records.

A location represents a physical place where work is performed or where assets are managed. Locations act as the central organizational record for a site and can store associated assets, tasks, notices, and other related information.

An asset represents a piece of equipment or infrastructure that needs to be tracked and managed. Assets store identification details, specifications, and other information necessary to monitor equipment over time.

Yes. A single location can contain multiple assets. This allows users to manage all equipment associated with a site within one location record while still maintaining separate records for each asset.

Yes. Assets, locations, and tasks can exist as standalone records and do not have to be tied to other records.

However, associating assets with locations is generally recommended because it helps organize information and provides clearer operational context for the asset.

Asset records contain the information displayed on the asset summary page. This includes identification details, specifications, and other information used to track the asset over time.

The asset record can also display related activity such as tasks, notices, and other records associated with that asset.

Yes. Asset records can be updated at any time. If equipment is relocated or assigned to a different site, the asset can be moved to a different location while preserving its history and related information.

A task represents a unit of work that needs to be completed.

Tasks are typically grouped within a work order, which acts as a container used to organize multiple related tasks together. However, tasks can also exist as standalone records when a work order is not required for the workflow.

Yes. Tasks can be assigned to specific users so responsibility for the work is clearly defined.

When a task is assigned, it will appear in the assignee’s Message Center, Daily Rounds, and Tasks view.

Tasks assigned to a user appear in several areas of the platform including the Message Center, Daily Rounds, and the Tasks view. These areas allow users to quickly see their assigned work, review task details, and track progress.

Yes. Tasks can be associated with a location, an asset, or exist as standalone records. Linking tasks to these records helps maintain a clear history of work performed on those records.

Yes. Tasks can be reassigned if responsibility changes or if another user needs to complete the work.

When a task is executed by the assignee, it moves to a review stage. The assigner then reviews the completed work and determines whether the task should be accepted and closed or returned for further review.

This process helps ensure work is reviewed before it is finalized.

Notices are created using notice templates. A template defines the structure of the notice and can be reused whenever a notice needs to be generated.

Yes. Notice templates can be applied to either locations or assets depending on the communication being sent. Associating notices with these records helps keep communications organized and tied to the correct record.

A report template defines the structure and data used to generate reports within the system.

Reports are generated by selecting a report template and executing it within the system. The template compiles the selected data and produces a report based on the defined structure.

Yes. Notices and reports can both be automated using triggers.

Triggers allow actions to occur automatically when certain events or conditions occur within the system.

Triggers are automation rules that execute actions when specific conditions are met within the system. Depending on how they are configured, triggers can automatically apply notices, generate reports, or perform other automated actions.

Filters allow users to narrow record lists based on specific criteria. This helps users quickly focus on the records most relevant to their workflow.

No. Filters are saved at the user level, allowing each user to create and maintain their own workflow views without affecting other users.

Yes. Filters remain applied until they are changed or removed.

Yes. Record lists can be sorted and searched to help users quickly locate the information they need.

Record lists can be viewed in multiple formats depending on the user’s workflow or device. R2 supports panel view, table view, and mobile view.

Yes. Multiple users can work within the system simultaneously while sharing the same database.

Yes. Each user has their own login credentials. This allows activity to be tracked by user and ensures each person can maintain their own workflow preferences.

No. Preferences such as filters, sorting, and views are saved at the user level.

Yes. Core records such as locations, assets, and tasks can exist independently and do not have to be tied together.

This design allows organizations to structure workflows flexibly while still allowing records to be connected when needed.

Yes. R2 tracks activity using two levels of history.

Activity history provides a high-level timeline of actions that occur on a record.

Audit logs provide a detailed system record showing who made a change, what was changed, when the change occurred, and where the change occurred within the system.