MAINTENANCE / WO-1132
Investigate the drain
FCU-09 · Riley Chen
Inspection photo and location attached
CONNECTED OPERATIONS
Connect the work
across your teams.
Bring requests, people, assets, purchasing, and proof of completion into connected workflows, so each team can act on the same information.
Aligned perspectives. Smarter outcomes.
A WORK RECORD THAT CONNECTS THE TEAMS
CLIENT REQUESTAirflow needs attention
✓WORKFORCEQualified · On shift
✓
Maintenance / Work ordersWO-1042Request received
Restore airflow
Northstar Services / East Campus
LINKED ASSETAHU-04 · Air handling unit
JL
ASSIGNED TEAMJordan Lee · Maintenance
✓Request details attached to the work.
NEXT PERSPECTIVEOne shared work history
From the first request to the next decision.
PILOT IN DEVELOPMENT
Maintenance and Assets & Inventory are the initial focus. The examples also show planned connections across the wider platform.
BUILT AROUND THE WORK
Built for the way your organization operates.
WO-1042Request, meet the rest of the operation.
01 / THE CONNECTION IS THE PRODUCT
Give every handoff
a shared record.
A request can become assigned work, draw on inventory, trigger a follow-up, and leave evidence for review. Each team builds on information already captured.
Information spread across separate tools
A requestin an email
An assignmentin a schedule
A resourcein a spreadsheet
An outcomein another report
WO-1042Every handoff stays linked to the original request.
02 / FOLLOW THE WORK
Follow one piece of work.
Choose a scenario. Follow the same record
as each team adds its part.
Context carries forward
Interactive examples show the platform’s intended connections. Feature availability depends on the release.
FROM OBSERVATION TO FOLLOW-UP
Give every finding
a way forward.
Select the observation to see how a repair and cleanup can grow from the same inspection.
The observation keeps its photo, location, and inspection history.
JANITORIAL / JW-0260
Coordinate the cleanup
Service-area floor
Follow-up linked to the repair
Planned workflow · Fictional example
ACCOUNTABILITY IN EVERY HANDOFF
Know who has taken responsibility.
Important work needs an acknowledgment and a clear owner. OperisFlow is designed to escalate unacknowledged issues according to their priority, while keeping the response attached to the record.
Keep people in control of exceptions
Authorized overrides can require a reason, so a necessary change in priority or assignment remains visible in the history.
RESPONSE TRACKINGPlanned workflow
WO-1120 · West Service Hub
UrgentEquipment needs urgent attention
- ✓Notification sent
Assigned team notified at 10:00
- 02Awaiting acknowledgment
No team member has accepted responsibility yet.
- 03Escalation remains active
The next contact follows the operation’s priority rules.
Fictional example; no notification is sent.
03 / EXPLORE THE CONNECTED PLATFORM
Explore your
connected operation.
Choose an area to see its workflow,
connections, and shared records.
MaintenanceShared contextOne action can move several parts of the operation.
Shared across the platformTasksApprovalsDocumentsCommunicationsAudit historyReporting
Representative product views, informed by the current application. All people and records shown are fictional.
FOLLOW THE RESOURCE
See where every part goes.
From an approved purchase to the equipment it helps maintain, the item carries its history with it.
Illustrative purchasing workflow
04 / YOUR OPERATION SETS THE CONTEXT
Put service requirements
into practice.
Run your own sites or deliver services for a client. Connect what was agreed to where it happens, who can do it, and what proves it’s done.
Facilities & propertyField servicesMulti-site teamsContracted services
Property operations are one application of a broader operational structure.
TRY AN OPERATIONAL REQUIREMENT
Watch a rule carry through.
Select a requirement from the sample service agreement.
Illustrative contract-driven connections. Availability depends on the release.
WO-1042 · AHU-04Your assignment and its history stay with you in the field.
05 / FROM THE DESK TO THE FIELD
Keep office and field teams
in sync.
Select the assignment on the coordinator’s screen. Complete the sample task on the phone and watch the shared record update.
Interactive demo · Fictional dataA PERSON BEHIND THE ASSIGNMENT
Choose an eligible team member to hand over the sample work.
WO-1158 · EAST CAMPUSInspect air handler
MRMorgan ReedSecurity · Different service
Illustrative assignment · Fictional data · No live dispatch
The outcome will travel with the work
CoordinatorAwaiting completion
Asset historyWork remains linked
Client viewRequest is assigned
ReportingScheduled or active
Designed for desktop and mobile/PWA workflows. Mobile capabilities depend on the release.
06 / CONNECTED BEYOND YOUR TEAM
Coordinate with clients and service partners.
Give external participants a focused view of their requests, assignments, and documents, with access tied to their role and relationship.
THE SAME WORK FROM ANOTHER PERSPECTIVE
WO-1042 · EAST CAMPUS
Restore airflow
AHU-04 · Maintenance service
AssignedIllustrative permissions; actual access depends on role, scope, and release.
Focused access for external participants
INTERNAL OPERATION
One connected record.
Work & assignmentInternal
Costs & approvalsInternal
Team conversationInternal
Role + scope + relationship
WO-1042 · Evidence attachedEvery outcome has a source.
07 / FROM ACTIVITY TO UNDERSTANDING
The work behind
every number.
Follow events across the operation. Open a number or an activity to see the records behind it.
Operations Activity
Fictional dataEvery event links to its source.
Counts are calculated from the sample work records. Completing the field demo updates both views.
08 / CONNECTION WITH CONTROL
Connection with control.
Organization boundaries, scoped permissions, protected attachments, and reviewable changes are part of the platform’s security design.
Organization isolation
Keep each organization’s records and access within its own context.
Roles and scoped permissions
Control actions and visibility by responsibility, site, and relationship.
Authentication and MFA
Secure sign-in and additional verification support controlled account access.
History and approvals
Keep changes attributable to the people who made them, with approval rules and archived records that preserve operational history.
BRING YOUR EXISTING RECORDS
Start with the information
you already have.
The Import Center is being built to bring work orders, preventive maintenance, assets, and inventory into OperisFlow without recreating each record by hand.
- 01
Map your columns
Match existing spreadsheet columns to the right fields.
- 02
Review before importing
Check missing details, uncertain matches, and possible duplicates.
- 03
Confirm the changes
Review what will be created, updated, skipped, or rejected before committing.
Import CenterIn development
assets.csvPreview · Fictional data
Review your records
Resolve flagged rows before confirming the import.
| Record | Review result |
|---|---|
| AHU-04East Campus · Air handling unit | Ready to create |
| PMP-08Site not supplied | Missing site |
| DR-12Matches an existing asset ID | Possible duplicate |
Review required before any record is changed.
Illustrative preview of the planned import workflow.
STEP INSIDE THE CONNECTIONS
Explore a connected
working day.
Take a guided tour of one request, or explore the fictional organization at your own pace.
No account needed for the demo. Account actions open OperisFlow Preview, our staging environment.
Connecting people, services, resources, and decisions.
Can we import our existing spreadsheets?
The Import Center is being built for work orders, preventive maintenance, assets, and inventory. The planned process includes column mapping, a preview, row-level validation, and duplicate checks before confirmation. Supported file formats and record types will depend on the release.
Can we manage several locations in one account?
OperisFlow is designed to share people, teams, and operational records across multiple sites while keeping site-specific assignments, permissions, and reporting. A site can be a facility, property, or another service location.
How does OperisFlow decide who can receive work?
The dispatch design brings together schedules, clock-in status, site authorization, availability, and qualifications. A coordinator can assign a team or an individual, with documented overrides where the organization permits them.
Can our contractors and clients use it too?
External participants are part of the product design. Contractors can remain associated with their own employer, while clients, tenants, and vendors receive access appropriate to their relationship. Their view is intended to show relevant work and documents without opening internal costs or team conversations.
Can our team use it on their phones?
The mobile direction is an installable web app for field tasks and time and attendance. Work records, asset details, and completion evidence are the focus. Offline behavior, push notifications, and installation support depend on the device and release.
Can we start with just the modules we need?
The rollout is designed to be gradual. Maintenance and Assets & Inventory are the pilot focus, with the purchasing, staffing, and mobile capabilities needed to support them. Other operational areas can be introduced as their releases become ready.
Will completed work include photos, readings, and notes?
Completion requirements are designed around the service being performed. A task can call for a comment, a measurement, or inspection evidence, with review where required. The result stays linked to the work and related asset rather than being reduced to a completed checkbox.
Is OperisFlow ready for our team to use?
OperisFlow is in development for its initial operational pilot. You can explore the fictional demo on this page now. The wider workflow examples describe the product direction; pilot access and usable capabilities depend on the current release.