Sign in with your Google account to access your property management workspace.
Your Google account must be added to the Users sheet by an administrator before you can sign in.
Access Not Granted
Your Google account hasn't been added to this workspace yet.
Locatiebeheerder
Problem AssetsView all →
Statisticslast 90 days
By Priority
Last 8 Weeks
Tickets
Show closed
Assets
Team
Staff & Contractors
Buildings
Inspections
Show completed
Inspection Round
Suppliers
Floor
Units
Floors
Logbook
Show gesloten
Calendar
For an overview of scheduled entries and tickets by date — tap a highlighted day to see what's planned.
Tickets / logbook match
Inspection start date
Both on same day
Entries
Info
App reference guide
Tap a screen to see how it works and what it tracks.
Stats
Portfolio overview & trends
Priorities
Urgent & overdue items
Tickets
Issues, tasks & statuses
Inspections
Rounds, items & results
Logbook
Events, notes & observations
Buildings
Health score, size & workload
Stats
Stats gives a portfolio-wide view of your buildings’ workload. Each building gets a workload score based on how much active work it currently demands — not simply how big it is. All numbers recalculate live from your Google Sheets data.
What drives the score
🎫
Open tickets carry the most weight. Every ticket that is not yet closed counts as active work that still needs to be handled.
🔍
Active inspections (not yet completed) add to the load because they require planning and follow-up.
📋
Recent logbook entries from the last 90 days give a sense of how much activity the building has seen lately. Older entries fade out automatically.
🔴
Failed assets — assets marked failed during an inspection, or assets with status Under Maintenance / Decommissioned linked to an open ticket — carry the highest weight.
Key calculations
Occupancy rateOccupied ÷ Total units
Open ticket rateOpen ÷ All tickets
Asset healthActive ÷ Total assets
Avg days openSum(days) ÷ Open count
Size adjustment
The raw score is adjusted for building size. A small building with 5 open tickets is proportionally under more pressure than a large building with the same 5 tickets — so the small building ranks higher. Each item is weighted by urgency: open ticket ×3, active inspection ×2, log entry ×1, closed / completed ×0.5. Resolved work still counts but at half weight, so a building that clears its backlog improves its score. The health % reflects real workload pressure, not just building size.
Trend chart
Monthly ticket volume for the last 6 months, calculated from dateOpened on each ticket row in the Tickets sheet.
Priorities
Priorities surfaces assets and units that need attention. Every asset and unit is scored based on how many problem signals are pointing at it — the more signals, the higher the priority band. The list recalculates on every load based on today's date.
What drives the score
🔍
Failed in an inspection is the strongest signal (+4 points). An item that did not pass an inspection round needs attention regardless of whether a ticket exists yet.
🎫
An open ticket linked to the asset or unit adds +3 points — it means active work is already pending.
⚠️
Asset status matters too. Decommissioned adds +3 points, Under Maintenance adds +2 — both signal the asset is not in normal operation.
🔒
Warranty alerts add weight too. An expired warranty adds +3 points, a warranty expiring within 30 days adds +1.
📋
A recent logbook entry (last 90 days) adds +1 point — it shows the item has been on the radar lately.
Priority bands
Critical
7+ points — act same day
High
4–6 points — act within 3 days
Medium
2–3 points — act within 7 days
Low
1 point — act within 30 days
Overdue calculation
Days open = Today − dateOpened Overdue if days open > priority threshold AND status ≠ Closed
Tickets
Tickets track issues that need to be resolved — a broken heater, a leak, a planned replacement. Each ticket moves through a status lifecycle.
Status lifecycle
Open
Newly reported
In Progress
Being worked on
Closed
Resolved & done
Planned
Scheduled future work
Ordered
Parts / contractor ordered
Requested
Awaiting approval
Dashboard score
Score = weighted pressure across your accessible buildings:
Open ticket ×3 · Active inspection ×2 · Log entry ×1 · Closed / completed ×0.5
A higher score means more active, unresolved work in your portfolio.
Key fields
Building · Floor · Unit · Assigned to · Supplier · Category · Priority · Date opened · Due date · Activity log
How are Ticket entries' workload calculated
Each ticket card shows a Workload % that reflects how much pressure its building is currently under — not the individual ticket itself.
Workload % = Open tickets in this building ÷ Total open tickets across your accessible buildings × 100
A building with more open tickets gets a higher, redder bar. All tickets from the same building share the same workload %. Only buildings you have access to are included in the denominator — so workload reflects your own portfolio, not the entire system.
≥ 40% of totalRed — high pressure
20 – 39%Amber — moderate
< 20%Green — low pressure
Inspections
Inspections are structured rounds where you walk through a building and mark each item as approved or flagged. Flagged items can auto-create tickets.
How a round works
1Select building & scope
2Check each item: OK / Flag
3Add notes on flagged items
4Complete round — saves to sheet
Completion score
Score = Approved items ÷ Total items × 100% Flagged items appear in Priorities if unresolved
Dashboard score
Score = weighted pressure across your accessible buildings:
Open ticket ×3 · Active inspection ×2 · Log entry ×1 · Closed / completed ×0.5
A higher score means more active inspection load relative to your portfolio.
Logbook
The Logbook records events that don't need follow-up action — a meter reading, a tenant visit, a delivery. It's your property diary.
Entry types
Onderhoud
Routine maintenance done
Keuring
Certification or check
Reparatie
Repair completed
Inspectie
Observation recorded
Dashboard score
Score = avg % of entries + assets + suppliers across all buildings.
Reflects how actively each building is being logged and maintained.
Logbook vs Tickets
Logbook = something happened (past, no action needed). Ticket = something needs to happen (future, assigned & tracked). Logbook entries have no status lifecycle or assignee.
How are Logbook entries' workload calculated
Each logbook card shows a Workload % that reflects how much of the total logging activity is concentrated in that entry's building.
Workload % = Logbook entries in this building ÷ Total logbook entries across your accessible buildings × 100
A building with more logbook entries gets a higher, redder bar. All entries from the same building share the same workload %. Only buildings you have access to are included in the denominator — so workload reflects your own portfolio, not the entire system.
≥ 40% of totalRed — high activity
20 – 39%Amber — moderate
< 20%Green — low activity
Buildings
Each building gets a health score based on how much active work it demands relative to its size. A small building with many open tickets ranks under more pressure than a large building with the same tickets.
Size Index
Measures how large a building is. Used to normalise the workload so pressure is comparable across buildings of different sizes.
If m² is set: m² ÷ 100 + (floors ÷ 1 000 m²) + (units ÷ 1 000 m²) + (assets ÷ 1 000 m²)
If m² not set: floors × 3 + units × 2 + workspace × 1 + assets × 0.5
Workload
The raw pressure on a building — how many active issues it currently carries, weighted by severity.