One definition.
A whole way of working.
A client. A site. An asset. A service visit. Define the things your organization works with—and connect their information, rules, and actions in one model.
Give the work a shared shape.
Start with a curated type or create your own. Define the fields, units, and relationships that make a service visit meaningful to your organization.
This is the definition of a Service visit. It is not a particular visit or a written operating procedure.
Service visit
Stable identityReference → SiteReference → TeamRequired before dispatchStructured values + notesThe blueprint for a kind of record. Each actual visit gets its own identity and history.
Connect the things people work with.
A visit belongs to a client, happens at a site, and concerns an asset. Connect those records by identity, so people can follow the context without copying it into another spreadsheet.
A mention is a reference to a record. Access to the referenced information still follows the viewer’s permissions.
Follow the visit’s context.
CLIENT-018SITE-042ASSET-004A note, document, or workflow can point to these same records.
Make the right next step explicit.
Define the states, prerequisites, and roles that govern an action. A dispatch needs confirmed access and an assigned crew. A review may need a different person from the operator.
Rules shape what is allowed. The approved procedure supplies the specific instructions for doing the work.
A lifecycle with conditions.
- 1Draft
- 2Ready
- 3Dispatched
- 4Review
- 5Complete
- Site access confirmed
- Qualified crew assigned
- Requester has dispatch permission
Required evidence is present. The reviewer is independent of the operator.
The same rules meet every request.
A person clicks a button. An integration calls the API. An AI client requests a permitted tool. The engine checks identity, permissions, current state, and required evidence before accepting the action.
Try the access check in this illustration. This is a local demonstration of a decision, not a request to the Helix application.
Can this visit move forward?
- Requester can dispatch visits
- Visit is in the ready state
- A qualified crew is assigned
- Site access confirmed
The request satisfies the illustrated dispatch checks.
Give each person a useful way to work.
The published type shapes the fields, views, and available actions. Approved content brings the instructions. People see the workspace that fits their role and where they work.
A derived SOP draws on structured operating content, with narrative context and document review. A schema alone is not an approved SOP.
The same visit. Different views.
Procedure SOP-032 · Rev 3
Keep the record while the work happens.
Observations, sources, revisions, and decisions stay attached to the work. See which selected controls have supporting evidence and open the gaps that still need attention.
A readiness score describes the selected scope and its evidence. Your organization determines applicable requirements and compliance.
The work leaves a connected record.
Selected control scope · 2 awaiting review
Source-linked evidence supports review. The score describes this scope, not the compliance of the whole organization.
Evolve the model without losing the story.
Propose a new field, instruction, or rule. Review its impact, test what changes, and approve its adoption. Earlier work retains the revisions and evidence that governed it.
Type versions, procedure revisions, and execution records have distinct lifecycles. A draft change does not silently rewrite approved work.
Add a completion photo.
+ completionPhotoFile reference · required at completion- Forms & completion action
- Checks & verification evidence
- Instructions & team readiness
A proposal is not an activation. New work adopts the approved version according to your rollout.
Change the model.
Carry the operation forward.
Fewer disconnected copies to reconcile. Clearer rules at the moment of action. A record people can follow afterward. The same foundation can support service teams, client operations, projects, laboratories, and production.
Three things stay distinct.
- The type
- Service visit · v3
Shared structure and behavior. - The procedure
- SOP-032 · Rev 3
Approved instructions and context. - The execution
- VIS-208
What happened on a particular visit.
Build a model around your work.
Start with a template in your free sandbox. Shape the records and rules, then try the workflow for yourself.