THE FIELD GUIDE
Building maintenance: make the site note reach the right asset and work order.
A photo report can be useful without being a maintenance system. Compare the handoff, the recurring work, and the record of completion separately.
A useful note still needs a destination
A worker can take clear photos and write a careful description, yet the maintenance team may still need to identify the asset, find the open work order, and decide who owns the next action. That is a handoff problem. Before buying a capture tool, identify which part of that handoff is causing repeated calls or re-entry.
This article offers an evaluation method. It does not rank full maintenance platforms or establish that the current solution index covers that market. The first edition has documentation, scheduling, and asset-custody examples; a dedicated CMMS comparison remains future research.
Capture is one part of maintenance management
PNNL’s Comprehensive O&M Program describes maintenance software supporting work-order tracking, scheduling, and analysis of failures and costs. It also emphasizes that the maintenance approach depends on the facility’s mission and equipment context. The source is a federal-facilities framework, not an endorsement of any product in our index.
Our inference is that a polished site report should be assessed against the downstream maintenance record. Does it reach the correct asset? Is the observation distinguishable from a recommended action? Who authorizes work, and who records that it was completed? A tool can contribute to that sequence without owning all of it.
Keep four states distinct
- Observed: a worker records a condition, with supporting evidence.
- Proposed: someone recommends a next action for review.
- Authorized: the responsible process approves work.
- Completed and reviewed: the required record and review establish what happened.
These are editorial distinctions for the trial, not prescribed status names. Use the statuses in the actual maintenance process. An AI summary must not move a record between them without the required authority.
Compare the capture path
CompanyCam’s official overview describes visual job records and reports. Fulcrum’s overview describes structured forms and field data. A visual capture path may suit a photo-led handoff; a structured path may suit repeatable asset observations. Neither overview alone establishes the exact connection to your maintenance system.
Prepare a benign completed job with the asset identifier, location, observation, evidence, and one outstanding action. Use the same information in each demo. Ask the vendor to show the receiving record, not just a notification that a report was sent.
Test the correction, not only the submission
- Capture the example and associate it with the intended asset and work order.
- Correct an identifier and one sentence. Inspect the exported or synchronized result.
- Leave an action unresolved. Check that it remains visible to its owner.
- Ask a maintenance colleague to find the original evidence without a verbal explanation.
- Confirm what happens if the receiving system is unavailable or the record is rejected.
Record clarification time, missing fields, duplicate entries, and unowned actions. Treat these as observations from the defined sample. They do not establish a general saving or reliability rate.
What to establish before rollout
Agree on asset naming, access, retention, correction rights, and responsibility for failed handoffs. For recurring maintenance, verify the schedule and work-order system separately. For tool custody, verify the asset-management workflow separately. The decision is whether the configured connection reduces a specific burden while preserving a record the maintenance team trusts.
Sources & evidence
Official sources reviewed November 3, 2026. Vendor materials establish descriptions, not independently measured performance. Original evaluation criteria are our analysis.