“What happened earlier?” is not a handover system

Shift changes often happen in a corridor, near the security post, or through a short group-chat message. The incoming staff member asks, “What happened tonight?” The previous shift answers, “There was an air-conditioning complaint, a vendor may come, and do not forget to check the basement.” Soon, important details begin to disappear: which unit reported the issue, which vendor was contacted, whether the tenant has been updated, and when the work needs to be checked again.

Handover problems do not necessarily happen because the team is careless. Operational information is easy to lose when it has no format, timebox, PIC, or clear evidence. The risk is greater in apartments, boarding houses, and buildings that operate across multiple shifts and involve engineering, security, housekeeping, tenant relations, vendors, and management.

A practical solution is a 15-minute shift handover. Fifteen minutes is a recommended timebox to keep the handover focused, not a universal rule. High-risk or high-volume properties can adjust the duration.

Why does a short handover still matter?

A handover that is too long often turns into a meeting. A handover that is too short becomes a conversation without a record. A 15-minute format keeps the team focused on the information most important for service continuity:

• What has been completed?

• What is still in progress?

• What must the next shift do?

• What risks need to be monitored?

• Who is the PIC and what is the due time?

Building operations are increasingly connected to technology, which makes consistent information flow across roles more important. The Directorate General of Human Settlements under Indonesia’s Ministry of Public Works explains that Smart Buildings involve technology integration, resource efficiency, resident comfort, and building management and operations.the official Directorate General of Human Settlements source on Smart Buildings A handover is not a smart-building certification, but it is a work habit that helps technology and teams produce usable information.

Five types of information every handover needs

1. Open issues and the latest status

Record every unresolved issue, including location, impact, latest status, and owner. Avoid a general sentence such as “AC problem on the 12th floor.” Write information that can be acted on immediately: “AC in unit 12-08 is leaking; the technician inspected the drain hose; vendor visit scheduled at 10:00; tenant can be contacted after 09:00; PIC Engineering A.”

2. Priority work for the next shift

Not every open task must be completed at the same time. Separate emergency, high, normal, and scheduled work. If a task relates to safety, security, risk of spreading damage, or a critical service, place it at the top.

3. Tenant events and service requests

Tenant relations should share information that affects the next shift, such as a tenant waiting for an update, a scheduled technician visit, a noise complaint, a need for unit access, or an approved special request.

Share only the information needed for the work. Do not distribute unnecessary personal tenant data. Use a case number or internal identifier when the next shift does not need the person’s full name or contact details.

4. Vendors, technicians, and access

Record the vendor scheduled to arrive, the area they may access, the escorting PIC, required documents, and work status. Security should not receive vendor information only through an undocumented verbal message.

For restricted areas, write access instructions clearly. For example: “Pump vendor arrives at 14:00; access limited to basement pump room; accompanied by Engineering B; security checks assignment letter and records entry/exit.”

5. Risks and items to monitor

This section contains conditions that have not become incidents but require attention. Examples include declining water pressure, an access door that does not close completely, low emergency-light stock, a slippery floor after rain, or a package that has not been collected.

Do not wait until a risk becomes a major problem before recording it. Visible risks are easier to schedule and assign.

A 15-minute shift-handover template

Use this format as a document, form, or digital checklist:

BUILDING OPERATIONS SHIFT HANDOVER
Date: ______________________
Previous shift: _____________  Next shift: ____________________
Handed over by: _____________  Received by: _________________
A. IMPORTANT EVENTS
1. Time/location: __________ Event: __________ Status: ________
2. Time/location: __________ Event: __________ Status: ________
B. OPEN ISSUES
1
Location: 
Issue: 
Priority: 
PIC: 
Status: 
Due time: 
2
Location: 
Issue: 
Priority: 
PIC: 
Status: 
Due time: 
C. VENDORS / TECHNICIANS / ACCESS
Vendor/technician: __________ Time: __________ Area: __________
Escort: ____________________ Documents/access: ______________
D. TENANT / SERVICE REQUESTS
Case number: _______________ Request: ________________________
Next update by: _____________ Due time: _______________________
E. RISKS TO MONITOR
- ___________________________________________________________
- ___________________________________________________________
F. CONFIRMATION
[ ] Priority issues have been read
[ ] PIC and due times are understood
[ ] Vendor/access arrangements are confirmed
[ ] Questions have been answered
Name/signature of outgoing staff: __________
Name/signature of incoming staff: __________

The template does not have to be printed. The important elements are the information structure, task ownership, and confirmation trail.

How to run the handover in 15 minutes

Minutes 0–3: Cover safety and critical events

Start with fire, flooding, electrical disruption, security, lifts, emergency access, or other events with potentially serious impact. If an emergency is occurring, follow the property’s emergency procedure first; the handover can continue once the situation is safe.

Minutes 3–7: Review open work

Read the open-issue list one item at a time. For each issue, confirm the location, latest status, PIC, priority, and due time. If one piece of information is missing, assign someone to complete it.

Minutes 7–10: Cover tenants, vendors, and access

Discuss tenants waiting for updates, technician schedules, arriving vendors, restricted areas, relevant visitors according to policy, and packages that need follow-up.

Minutes 10–13: Review risks and next-shift work

Choose no more than three key risks or tasks. The handover is not the place to read every routine task. Non-urgent work should still be recorded and scheduled through the appropriate work channel.

Minutes 13–15: Confirm the receiver’s understanding

The incoming shift repeats the three actions that must be done, the PIC, and the due time. This helps identify ambiguity before the previous shift leaves the site.

Examples for engineering and security teams

Each team has different needs. Engineering requires information about asset condition, materials, vendors, and work schedules. Security needs information about access, incidents, visitors, areas to monitor, and escalation instructions.

Engineering

• Main information: Defects, repair status, materials, vendors

• Example follow-up: Check pump, wait for spare part, escort vendor

Security

• Main information: Access, incidents, visitors, risk areas

• Example follow-up: Verify access, add patrol, record incident

Housekeeping

• Main information: Dirty areas, cleaning schedule, stock

• Example follow-up: Prioritize lobby, replenish supplies

Tenant relations

• Main information: Complaints, tenants waiting, appointments

• Example follow-up: Send update, coordinate visit

Supervisor

• Main information: Risks, backlog, approval, decisions

• Example follow-up: Escalate, reassign PIC

For cross-department teams, use one shared summary and add details to each department’s work list.

Common mistakes

Relying only on a group chat

A group chat is useful for rapid communication, but it is difficult to use as a list of tasks that can be filtered and closed. Important messages can be buried by unrelated conversations.

Marking every task as an emergency

If every task is urgent, the team cannot set a useful order of work. Use agreed priority definitions and explain the impact.

Omitting the PIC and due time

“Please check this” is not yet an assignment. Add the PIC or responsible role, the required action, and when the status must be updated.

Failing to update the tenant

A technical task may be complete while the tenant still believes the report is unresolved. Record the need to send an update or request confirmation after the work is completed.

Sharing too much sensitive information

A handover should support the work, not expose unnecessary tenant data. Keep sensitive details under restricted access according to the property’s policy.

How Nextlivin supports a more structured handover

Handover becomes easier when work, complaints, access, and follow-up are not scattered across separate notes. Through Nextlivin Manage for Team, teams can connect Worktrack, Feedback, Team Chat, Visitor, and Package according to their operational workflow.

The Nextlivin Features page describes Work Process capabilities including Worktrack, Feedback, Billing, Facility, Broadcast, Visitor, and Package, while Data Management includes User, Documents, Team Chat, and Inventory. Building managers still need to define the SOP and access rights; the application helps make status, PICs, and history easier to trace.

Test it for seven days

Choose one shift change that frequently causes problems. Use the template for seven days and track three indicators: the number of questions that have to be asked again, the number of tasks without a PIC, and the number of reports that do not receive an update on time.

If the indicators improve, extend the template to another department. If they do not, check whether the format is too long, priority definitions are unclear, or information is still being recorded in another channel.

Conclusion

A good handover is not a long conversation and not a signature without substance. It ensures that the next shift knows what happened, what is in progress, who owns it, when it is due, and what risks need to be monitored.

Start with a 15-minute format covering critical events, open issues, priority work, tenants, vendors, access, risks, and confirmation. Use it for seven days, measure repeated questions and delays, and adapt it to the property’s needs.

If your team still moves between logbooks, group chats, and spreadsheets, explore the Nextlivin Manage for Team workflow to see how work and follow-up can be managed more systematically.