Facility service providers
Make site requirements usable for the team doing the work.
Connect customer contacts, site notes, preparation tasks and service follow-up while specialist facility management and asset systems stay in place.
- 01Clarify the site
- 02Prepare the team
- 03Document exceptions
- 04Follow up
A service instruction needs a clear origin and owner.
Facility teams often work at customer locations with different access rules and points of contact. Tsumira supports customer coordination and task-based preparation. It is not a CAFM platform, building-management system or proof that a statutory inspection has been completed. Keep the distinction clear when designing the operating process.
A concrete workflow
Clarify the site
Record the customer coordinator and practical access requirements.
Prepare the team
Assign checks and share only the necessary instructions.
Document exceptions
Capture what prevented or changed the planned work.
Follow up
Assign customer questions and remaining operational actions.
Keep customer and location instructions accessible.
Maintain the customer organization and its coordinators in CRM. Use shared documents for practical service instructions and access questions. Select file access for the team members who need the material; linking a customer is not a reason to expose sensitive site information to the whole company.
- Customer records and controlled site documents
Track preparation and exceptions as real work.
Assign tasks for preparation, customer answers and service follow-up. Clear owners and deadlines help the coordinator see unresolved dependencies. The task plan does not automatically optimize staff routes, shifts or equipment availability, so retain the dedicated tools needed for those decisions.
- Owned tasks and deadline-based coordination
Record what happened, not just that something closed.
After a visit, record observations, effort and remaining questions against the customer or project. Share reviewed supporting files deliberately. A completed task should not be treated as a legally sufficient inspection log, asset maintenance certificate or safety record without a separate validated process.
- Activities, service notes and supporting files
An illustrative working example
Illustrative scenario: a multi-location customer
A provider coordinates services for a customer with several locations. Contact records identify the coordinators, shared notes describe access, and project tasks track unresolved preparation. After an exception at one site, the team records it and assigns follow-up. Building assets and mandatory inspection evidence remain in specialist systems. Access instructions at one site change before the team arrives. The coordinator updates the shared note and assigns a check to the responsible person. After the visit, the record distinguishes completed work from the exception that still needs customer agreement. The pilot tests one location and its handover before expanding to a whole portfolio. Asset records, staff routing and mandatory safety evidence remain in their designated specialist workflows. Confirm who maintains each site instruction when the customer changes it.
Questions about this topic
Is it a CAFM or building-control platform?
No. The page describes customer and task coordination, not building models, telemetry or technical asset management.
Are legal inspections covered?
No compliance claim applies. Keep qualified inspections and required evidence in an appropriate validated process.
Can we schedule workforce routes?
Task ownership is supported; automatic routing, shift optimization and live dispatch are not implied.
Can site instructions be shared selectively?
Use document and file permissions deliberately, and review sensitive access information before sharing it.
Explore connections around this workflow.
Ideas for intended connections. Check the actual availability, permissions and supported data for each app before using a scenario.
