Follow a fictional facilities-services team through connected projects, onboarding, certificates, meetings, forms, equipment, incident follow-up and reporting. Includes changing the account timezone.
Recorded with fictional demonstration information. Available actions depend on your role and organization settings.
Video transcript
People, work and evidence
Welcome to ZoTracker. In this walkthrough, we follow Cedarbridge Facilities Services as its team prepares and carries out maintenance at Riverside Community Centre. Cedarbridge, its people and its customer are fictional, but the screens and actions come from the application. We will connect people, project responsibilities, onboarding, work records and follow-up. You will see the organization’s view, then switch to the person completing assigned work. The aim is a clear working picture: what needs doing, who owns it, what evidence has been recorded, and what still needs attention.
01. Start with the workspace
The dashboard provides a starting point across the organization. Module cards lead to people, qualifications, learning, forms, assets and projects. Summary figures help a manager decide where to look next. They are a view of recorded activity, so the date window and the work included in that view matter. Open the relevant record to understand the detail behind a number. Throughout this example, we will return to the same customer project, rather than create separate stories for each module. That makes it easier to see how the information supports real work.
02. Set the account timezone
Before setting deadlines, check the organization’s timezone. As the account owner, open Account Details and choose the edit option. Find Time Zone, select America slash Toronto, and save the account information. Cedarbridge works in Toronto, so that is the appropriate choice for this example. This is an account setting, rather than a preference for just one employee. Check the saved account details and refresh the session before reviewing time-sensitive work. Choosing the right zone helps people interpret the dates and times they see consistently. Keep using the zone that matches your organization’s operating needs.
03. Introduce the team
Employees provides the team directory and individual profiles. Olivia Bennett owns the account, Marcus Chen manages operations, Noah Williams coordinates the site, and Sophie Turner carries out facilities work. A profile brings the person’s details and related work together, making it easier to check the right employee before assigning something. Job titles describe the example organization; the actions available to each signed-in person depend on their actual access. We will make the change of person clear when Sophie takes over. An employee should be able to find their work without needing the manager’s full workspace.
03. Add the external relationships
Customers and Contractors hold different relationships. Harbor Community Properties is the customer responsible for Riverside Community Centre. Clearway Electrical is the external company helping with the work, represented here by Liam Foster. Keeping these profiles distinct helps the team identify who receives a service and who participates in delivering it. Their related records provide context when a manager reviews a project or follows up an issue. External participation does not mean unrestricted access to the organization. Use the supported assigned workflows for the particular person and task. These fictional profiles give our project a realistic working team.
04. Open the project file
Here is the Riverside Community Centre maintenance project. The customer, site, scope and target dates establish what the team is trying to deliver. Marcus is the project manager, with Olivia as sponsor and Noah coordinating site work. These responsibilities matter more than simply adding names to a list. They tell the organization who should keep delivery moving and who needs to make decisions. The project also provides places for planning, milestones, tasks, issues, files and activity. We will use a small selection of those tools to tell a complete story, rather than fill every available field.
04. Connect the project resources
Project assignments connect the delivery file to the resources involved. Add Sophie as the facilities technician, the Riverside generator as equipment, and Liam as the electrical contractor. Give each assignment a useful purpose so that another manager can understand why the resource is present. The saved register now shows the team and equipment attached to this project. Project leadership is handled separately from ordinary resource assignments. That distinction keeps the project manager and operational team clear. Linking an asset or person here provides context; the work itself still needs a task, inspection or other appropriate record.
04. Give the work an owner
A project becomes easier to manage when the next action is explicit. Use a milestone for the readiness checkpoint, then add a task to check the service-yard access route. Assign the task to Sophie and give it a due date. The task is now a recorded responsibility instead of a request hidden in a conversation. Later, Sophie can open her own task view to follow the work. Planning and capacity tools can support a larger programme, while logs, issues and change controls help manage delivery. For this walkthrough, one clear task is enough to show how responsibility becomes visible.
05. Share the working procedure
Documents is the shared library for resources such as procedures and guidance. Our example procedure explains Riverside access, visitor routes and the reporting process. Give the file a clear title, place it in a useful category, and choose the intended audience. Open the saved document to check that staff will receive the correct material. A shared procedure is different from a qualification certificate or a file attached only to one person’s profile. That distinction helps organizations keep reusable guidance easy to find while maintaining the context of more specific records.
05. Keep guidance beside the work
The same procedure can be referenced from the project, so people do not have to guess which copy applies. Use the document linking tools to select the shared resource, then confirm it appears with the project’s related documents. Open its preview to verify the result. The document remains a library resource, with access checked when someone opens it. Linking a document makes it available in context; it does not mean the person has read or acknowledged it. When acknowledgment matters, use an assigned orientation, meeting or form that actually records the required completion.
06. Prepare the site induction
Orientations supports structured onboarding. Riverside Site Induction is connected to the same project and contains the practical information a person needs before starting. The builder organizes that material into sections and can include supporting resources and questions when required. Our short example covers site access, keeping public walkways clear and reporting unsafe conditions. Assign the induction to the intended learner and check the assignment list. Due dates and completion rules should reflect the organization’s actual needs. This example does not issue a qualification certificate automatically; orientation completion and qualification evidence remain distinct records.
06. Complete the induction as an employee
We are now signed in as Sophie, the facilities technician. Her assigned induction opens in the learner experience. Read the content, review the site instructions, and complete the required acknowledgment. The saved result is what matters: the assignment moves from outstanding work to a completed record. This gives the organization a way to see who has completed this particular onboarding activity. It does not prove that every possible training requirement has been met. A contractor can receive an assignment through the supported contractor workflow too. Keep each person’s completion attached to their own assignment, even when the learning content is shared.
07. Track the required qualification
Certificates helps the organization track qualification evidence for employees and contractors. Here we ask Sophie to provide her equipment safety awareness record. The assignment records what is required and who needs to respond. It should not be confused with an approved certificate that is already on file. The person can follow the assignment to provide the requested document and dates. Every sample qualification used in this walkthrough is clearly marked demonstration only and is not a valid qualification. In a real organization, choose titles, evidence requirements and review rules that fit the work being performed.
07. Review the submitted evidence
Sophie provides the demonstration document and its issue and expiry dates. The organization’s reviewer then opens the submission and checks the evidence before making a decision. A saved approval is separate from merely receiving a file. The certificate view also shows date-based status, so an approved record may still need renewal as its expiry approaches. Where history is retained, a renewal can be reviewed without treating the previous record as a completely unrelated qualification. Use the actual record and review state to understand what is current. Reminder settings help follow-up, but this walkthrough does not demonstrate email delivery.
08. Prepare the daily briefing
Meetings handles a different need from induction. The morning briefing brings the team back to today’s maintenance plan: confirm the access barriers, inspect the generator, coordinate the electrical work and keep visitor routes clear. The meeting record can contain the briefing material and links or documents needed by the attendees. Assign it to the relevant people and check the completion requirements. A short daily briefing should remain focused on the work ahead. It is a separate activity from the induction, even when the same people participate and both records relate to the same project.
08. Record the briefing acknowledgment
Back in Sophie’s workspace, open the assigned briefing and review its content. Complete the required acknowledgment, then check the saved completion result. The manager can return to the meeting assignment list to see participation. This creates a useful record of the assigned activity without turning the meeting into a qualification certificate. It also makes the difference between preparing a meeting and completing an assignment visible. The organization still needs to decide what briefing content is appropriate and how to run the actual discussion. ZoTracker keeps the assigned material and its recorded completion together.
09. Build a practical checklist
Forms provides structured records for everyday checks, submissions and reviews. Riverside Daily Work Checklist asks whether the work area and visitor route were checked, whether the equipment pre-use check was completed, and what work or follow-up needs recording. The builder defines the questions before the form is published. This example is designed for project and equipment context, so the submission can be understood alongside the work it describes. Publishing makes the prepared version available for use. Assignment then identifies who should complete it. A form connected to equipment does not replace the equipment module’s own inspection records.
09. Submit and review the checklist
Sophie opens her assigned checklist, records the checks she has performed and adds a practical note about the work area. Submit the form, then switch back to the manager to inspect the saved answers. Where review is required, the reviewer records the appropriate decision rather than treating submission alone as approval. The resulting record keeps the answers, author and workflow state together. This is useful for daily operations, quality checks and other repeatable processes. The form should ask for information the organization will actually use, with clear wording and an amount of detail that fits the task.
10. Manage the asset in context
The generator has its own equipment record. It identifies the asset, location, responsible employee and linked customer project. That gives a manager a starting point for inspection, maintenance and follow-up without mixing every asset into a single list of notes. Equipment also provides areas for requests, parts, maintenance and reporting. Use the asset number to distinguish this generator from another similar machine. In our example, Sophie is the assigned person and Marcus coordinates its upkeep. An assignment records responsibility and context; the current inspection and maintenance records explain what has actually been checked or done.
10. Turn an inspection finding into follow-up
Now record a pre-use inspection of the generator. The demonstration finding is a damaged cable cover that needs attention before the equipment returns to service. Save the inspection result, describe the finding and choose the supported work-order escalation option. Check the saved inspection and the resulting follow-up work order. This connection makes the next action visible, rather than leaving a failed result with no owner. It does not mean every inspection creates a work order automatically. The chosen result and escalation settings determine the path. The organization remains responsible for the safe operational decision.
10. Record the maintenance outcome
Open the maintenance follow-up and review its scope, owner and due date. Record the completed repair and the verification note when the work has actually been carried out. Then check the saved maintenance state. An inspection finding, a planned repair and completed maintenance tell different parts of the asset’s story. Keeping those records distinct makes the history easier to understand. For a larger equipment programme, schedules, parts and requests help organize ongoing work. Here, the important result is simple: the team can see what was found, what action followed and what outcome was recorded.
11. Report a near miss
An incident workflow records an event that needs a response. Our fictional near miss concerns a visitor route that was briefly obstructed during maintenance. There was no injury in this scenario. Record what happened, the immediate action taken, and the relevant project and equipment context. Linking these records helps the investigator understand where the event occurred and what work was involved. The report is the beginning of the response, not the end. It is also separate from the equipment inspection we just completed. Do not assume that entering one record automatically creates every other record the organization may need.
11. Investigate and close the loop
The investigator reviews the event and records the contributing factors. Assign a corrective action to improve how visitor access is maintained during the work. Give the action a named owner and a due date, then record the completed action and verification. Review the resulting incident state before considering the matter closed. A useful workflow makes outstanding responsibility visible and keeps the response attached to the original report. It should also leave enough explanation for a manager to understand the decision later. The example demonstrates recorded follow-up; it does not replace the organization’s incident response procedure.
12. Find outstanding work
Notifications helps a person find events addressed to them, while My Tasks brings assigned work into a personal view. Open the relevant item to take action in the module that owns it. We can return to Sophie’s project task, record the work result and inspect the updated state. Project logs provide additional delivery context, and approvals or change requests record decisions when the work requires them. These tools support different responsibilities, so they should not be treated as interchangeable checkboxes. The connected workspace helps a person move from an alert or task to the underlying record that needs attention.
12. Review the organization’s position
Return to the management view to review the outcome. Project records show the team and connected activity. Module dashboards and reports provide more focused views of completion, open actions, assets and qualifications. Use filters and date ranges to answer a specific question, then open details or export a report where appropriate. Scheduled Reports can prepare recurring delivery for supported reports, but we will not create a live delivery in this example. The figures reflect the records and scope included in each view. They help management follow up; they are not a guarantee that every organizational requirement has been satisfied.
13. Help people keep moving
Help Center keeps written guidance close to the work. Open the relevant module topic when someone needs a reminder of the steps or an explanation of a status. Technical Support provides a place to describe an application issue and follow its ticket, when support is needed. We will only preview that entry point here. Across this walkthrough, the same people, customer project and equipment have connected planning, onboarding, evidence and operational follow-up. That is the practical value: clearer responsibilities and a record of what happened. Explore ZoTracker at zotracker dot com, or contact support at zotracker dot com.