Introducing the Voyager SOP Module
One published version of every procedure, tied to the assets it governs.
Your Building Should Run the Same Way with Every Change
You run facilities so recurring work gets done right: chillers shut down in the correct sequence, fire pumps get inspected on schedule, electrical panels get isolated safely, every time, by whoever is on that shift. The knowledge exists. Your best people carry it in their heads, and somewhere on a network drive or a binder there’s a collection of PDF’s that describes each process.
The real question is whether the new technician doing the task tonight is working from the same instructions as the one who did it last month. In most facilities, nobody can answer that with confidence.
The Problem: Procedures That Drift
Standard operating procedures usually live in binders, shared drives, and email attachments. That creates 2 problems that compound over time.
First, versions multiply. A procedure gets updated, but the old copies don’t disappear. They sit in a binder in the mechanical room, in someone’s downloads folder, in a 3-year-old email thread. When a technician grabs the nearest copy, there’s no way to know if it’s the current one.
Second, the procedure says nothing about the actual building. “Shut down the chiller” in a static PDF could mean any of 4 machines on the mezzanine. The document can’t point to the asset, its maintenance history, its spec sheet, or where it sits in the model. The person doing the work has to bridge a huge context gap themselves, and how well they bridge it depends on how long they’ve worked in your building.
What That Drift Actually Costs
- Inconsistent execution. The same task gets done 3 different ways by 3 different technicians, and equipment wears accordingly.
- Safety exposure. An outdated isolation or shutdown procedure on critical equipment is a risk you carry every day without seeing it.
- Knowledge that walks out the door. When your most experienced operator retires, the correct way to do the work often retires with them.
- Slow onboarding and audit pain. New hires learn by shadowing instead of following approved steps, and proving compliance means reconstructing which version was in effect when.
The Fix: Put Procedures Where Your Building Data Lives
The fix is structural. Give every procedure a single published version that everyone follows, keep a full history of every change, and link each step to the real assets and documents it refers to, so the instructions and the building stay connected.
That’s exactly what the new SOP module in Voyager does. It brings your standard operating procedures into the same digital twin that already holds your building model, your assets, and your documents, and it turns each one into a clear, ordered list of steps that anyone with the right access can follow.
Digital Steps Tied to the Real Building
Each step in a procedure can link directly to the asset it concerns and the documents, BIM elements, and data feeds that support it. Open a step and the digital equipment record is one tap away.
Authoring is designed to be fast. Each SOP carries:
- a unique code (Voyager suggests one automatically),
- a title,
- a location (pulled from Voyager’s existing rooms list),
- a category for filtering,
- an estimated time to complete (pulled from the SOP’s individual steps,
- an automated prepared-by and date for accountability and version control
Steps are added one at a time, each with a title, instructions, a category badge such as Safety, Critical, or Quality, an optional photo, and links to the relevant asset or documents inside Voyager. Steps can be reordered, duplicated, or removed as the procedure takes shape, so refining even a long checklist stays quick.
See It on Your Own Procedures
Think of the highest-stakes procedure in your building right now. If you can’t say with certainty which version of it your team would pull tonight or how much facility context is attached the procedure, that’s the gap this module closes. Every month it stays open, the drift gets wider and the fix gets more expensive.
Bring a procedure and we’ll build it into the SOP module with you, publish it, and link it to the assets it governs. Request a Voyager demo at today.