Building Maintenance Log
One building and every job done to it, sorted by the part of the building that consumed the money. Most logs are kept per asset, which answers a different question. This one answers the owner's question, which is where the budget actually went and which part of the fabric is quietly taking more of it every year.
- Spend split across sixteen building elements, not by asset
- Each element's share of the budget, with a trend against last year
- Spend per unit of area, the figure that compares buildings
- Reactive share of jobs, and what to move into the plan
Building Maintenance Log
Where the budget went
| # | SPEND BY BUILDING ELEMENT | JOBS | SPEND | SHARE |
|---|---|---|---|---|
| 1 | Roof and rainwater, two gutter failures on one elevation | |||
| 2 | HVAC and ventilation, planned service plus three callouts | |||
| 3 | Electrical and lighting, mostly statutory and reactive lamps |
The document you will get. Download for the full, editable file.
Who this building maintenance log is for
One building, one year, and three people who want different things from the same log.
The building or estates manager
You keep it, and the element table is what you get back. It turns a year of individual jobs into a statement about which parts of the fabric are consuming the budget.
The owner or landlord
Your question is where the money went, and no asset-level record answers it. Spend per unit of area is what lets this building be set against the rest of the portfolio.
Whoever builds the capital plan
The trend column. An element rising two years running has stopped being a maintenance line and become a capital case, and this is where that first becomes arguable.
Whoever inherits the building
A year of jobs against elements is the fastest possible briefing on a building you have never managed, including which faults keep recurring in the same place.
Where spend by element matters most
The elements suit most commercial buildings. What changes is who reads the total and what they do with it. If you run one of these, the sector page goes further than the template does.
- Commercial real estate
Owner reporting, where spend per unit of area across a portfolio is the comparison and the element split is the explanation behind it.
Portfolio maintenance software - Corporate facilities
Occupied offices, where interior fabric and finishes generate most of the jobs and almost none of the capital risk.
Corporate facilities software - Education
Estates with long-lived fabric and compressed working windows, so a rising element has to be caught a year before the work can happen.
Campus maintenance software - Retail and malls
Trading premises where external areas and paving carry liability as well as cost, and both show up in the same table.
Retail maintenance software - Healthcare
Buildings where statutory work is a large share of spend, so it is separated as its own work type rather than buried in planned.
Healthcare maintenance software - FM service providers
Contracted buildings, where the element split is what justifies next year's budget to a client who only sees the total.
FM service provider software
What a building maintenance log should contain
A building maintenance log is the record of every job carried out on one building, sorted by the part of the building that the money was spent on. It holds each job with its element, type, hours and cost, then totals spend per element as a share of the budget, against last year, and per unit of floor area.
A. The sections that carry the weight
| Field | What goes in it | Why it earns its place |
|---|---|---|
| Building details | The building, its type, gross area and the annual budget | Area and budget are the two denominators. Without them the log records spending and cannot produce a rate or a variance. |
| The work log | One row per job with date, location, element, type, hours and cost | Every job on the building regardless of who did it or what kind it was. A log that only holds planned work cannot show a reactive share. |
| Building element per job | Which of the sixteen elements the money was spent on | The field that makes the whole document work, and the one that takes a moment of thought per job. Everything downstream is built from it. |
| Work type | Preventive, reactive, corrective, statutory or improvement | Five types, with statutory separated deliberately. Statutory spend is not discretionary and should not sit inside planned when a budget is being argued. |
| Work by type | A count against each type, calculated | Shows the shape of the year. A building drifting toward reactive is telling you the planned program is not covering something. |
| Spend by element | Jobs, hours, spend, share of budget and trend for each element | The table the document exists for. It converts a year of unrelated jobs into a statement about the fabric. |
| Trend against last year | Whether this element is taking a rising share | The capital signal. A single expensive year is noise; the same element rising twice is a pattern that belongs in a capital plan. |
| A note per element | Why that element cost what it did | Turns a number into an argument. Two gutter failures on one elevation reads very differently from routine roof maintenance at the same cost. |
| The year in numbers | Jobs, reactive share, hours, spend, variance against budget | The summary an owner reads. Variance is calculated, so the overspend is stated rather than explained away. |
| Spend per unit of area | Total spend divided by gross floor area | What allows comparison. A building's spend figure alone says nothing about whether it is expensive. |
| Highest spending element | Which element consumed the most, named | One line that usually surprises whoever commissioned the log, and the fastest route into next year's conversation. |
| What the year is telling us | Rising elements, recurring faults, what moves to planned or capital | The section that converts the table into decisions, including the statutory work still outstanding. |
Tagging each job to a building element is the one piece of extra effort this log asks for, and it is the only reason the document is worth keeping. It takes a few seconds per job and it is the difference between a list of work and an account of a building. The reason it matters is that the fabric does not appear in any asset register. A chiller has an asset record, a maintenance history and a replacement cost; a roof has none of those things, and yet the roof is where buildings most often quietly consume their budget. Kept per asset, six separate roof repairs across a year are six unrelated jobs on six different work orders. Kept per element, they are one number with a share and a direction, and that number is what a capital case is built from. The trend column is what completes it: one expensive year is weather, and two in a row is a decision waiting to be made.
B. What it looks like filled in
Five of the sixteen elements from one year on a four thousand two hundred unit office building. The top line is not the biggest problem because it is the biggest.
| Element | Jobs | Spend | Share | Trend |
|---|---|---|---|---|
| Roof and rainwater | 9 | 6,240 | 18% | Up |
| HVAC and ventilation | 11 | 5,900 | 17% | Flat |
| Electrical and lighting | 6 | 3,410 | 10% | Flat |
| Plumbing and drainage | 5 | 2,980 | 9% | Up |
| Car park and paving | 2 | 1,240 | 4% | Flat |
| All sixteen elements | 46 | 34,180 | 100% |
The roof is the line that matters, and it is not because it is the largest. HVAC at seventeen percent is close behind it and flat, which is what a serviced system is supposed to look like: predictable, planned, boring. The roof is at eighteen percent and rising, and the note against it says two gutter failures on the same elevation. That is no longer a maintenance pattern, it is one defect being repaired repeatedly, and the right response is a capital case rather than a third repair. Nothing about that is visible in a log kept per asset, because a roof is not an asset and never appears in an asset register. The year's totals give the other half of the argument: thirty-four thousand one hundred and eighty spent against a thirty-two thousand budget, which is eight point one four per unit of area, and that rate is the only figure in the document that can be set against another building.
Word for a version you want to adapt to an unusual building, Excel for the one that totals spend by element with its share and variance against budget, with a Building Register tab holding a row per year, and PDF for the copy that goes into an owner's report. One file per building per year. Free, and yours to rebrand.
How do you keep a building maintenance log?
Set the building up once, then tag every job to an element as it is logged. Doing that at the end of the year is what makes the table wrong. Six steps.
Set the building up with its area and budget
Building, type, gross area and the annual maintenance budget. These are the two denominators behind every useful figure, and area is the one people leave until they need it.
Log every job, whoever did it
Date, location, description, element, type, hours, contractor and cost. Work done under a contract belongs here as much as work done in house, or the element totals understate themselves.
Tag the element as you log it, not afterwards
Which of the sixteen parts of the building the money went on. Doing this at year end from memory is how a roof repair becomes a general building line and disappears.
Separate statutory work from planned
Statutory is its own type rather than a subset of preventive, because it is not discretionary and should not be inside the number somebody is trying to cut.
Read the element table, then the trend column
Share tells you where the money went, and trend tells you whether it is going there again. An element rising two years running is the one to act on, whatever its absolute size.
Convert it into next year
Move recurring reactive work into the planned program, put rising elements into the capital plan, and record any statutory work still outstanding on its own line.
Logging by building element versus by asset
Two ways of logging the same year of work. Both are legitimate, they answer different questions, and one of them cannot see the fabric at all.
| Aspect | Logged by building element | Logged by asset |
|---|---|---|
| The question it answers | Where the building's budget went | Whether this machine is worth keeping |
| What it can see | Roof, walls, paving, drainage | Only things with an asset record |
| The unit of the total | A part of the building | One machine |
| What a rising share means | A capital case on the fabric | An asset approaching replacement |
| Who asks for it | The owner, the budget holder | The planner, the engineer |
| What it cannot tell you | Whether one chiller is failing | That six roof repairs were one defect |
Most estates need both, and the gap between them is where buildings lose money quietly. An asset log is excellent at the thing it does: it accumulates a machine's history and eventually says whether to replace it. What it structurally cannot do is notice the fabric, because fabric has no asset record. Six roof repairs in a year are six closed work orders against six different locations, and there is no line anywhere that adds them up. Logged by element they are one number with a share and a direction. If you only have the appetite for one, keep the one that matches the question you are actually being asked, which for most owners is where the money went rather than which unit is old.
When the template starts to feel limiting
The file is built for one building over one year. Four things start to hurt as soon as that is not the shape of the problem.
One file per building per year
Comparison is the point and the file cannot do it. Asking which of eleven buildings has a rising roof share means opening eleven workbooks and reading the same table in each.
The element tag depends on judgment
A leaking pipe above a ceiling is plumbing to one person and internal fabric to another. Without a convention written down, the table drifts and two years stop being comparable.
It is a year in arrears
The trend only appears once a second year is complete, which means the earliest a rising element can be caught is after two full cycles of paying for it.
Contracted work often never arrives
Jobs done under a service contract are invoiced in a lump and frequently never logged per job, which quietly understates whichever elements that contract covers.
What running this in Facilio looks like
The log does not change. What changes is that spend attaches to the building and its elements as work closes, instead of being tagged by hand once a year.
Ops Performance Intelligence
The element split builds itself
Every closed job carries its cost and its location, so spend by element is current rather than a table somebody reconstructs at budget time.
Audit Report Intelligence
A rising element surfaces early
Because the share is held against the building over time, an element trending up is an exception that appears rather than a pattern found after the second year.
Work Order Intelligence
Repeat faults in one place connect
Several repairs at the same location read as one recurring defect instead of separate jobs closed weeks apart by different people.
Asset Intelligence
Fabric gets a record too
Parts of the building that never appear in an asset register still accumulate their own cost history, which is exactly where an asset-based system usually goes blind.
Hallucination-free by design. Atom AI answers from the records in your tenant rather than generating plausible text, so an empty field reads as empty rather than filled in for you.
Frequently asked questions
What is a building maintenance log?
A building maintenance log is the record of every job carried out on a single building over a period, sorted by the part of the building the money was spent on. It holds the date, location, element, work type, hours and cost for each job.
What makes it different from most logs is the element split. Instead of totalling spend per machine, it totals spend across sixteen parts of the building, each with its share of the budget and whether that share is rising.
What is the difference between a building maintenance log and a maintenance log?
A maintenance log covers one asset and its whole service history, ending in a repair-or-replace position for that machine. A building maintenance log covers one building and sorts spend by building element.
They barely overlap. The building log can see a roof, a car park and a drainage run, none of which have asset records. The asset log can see a chiller's parts history, which no element total will ever show.
Why sort maintenance spend by building element?
Because it is the only view that shows the fabric. Roofs, walls, paving and drainage consume real budget and appear in no asset register, so work on them is otherwise scattered across unrelated job records.
It is also the form the question usually arrives in. An owner asking where the money went is not asking which unit was serviced; they are asking which part of their building is expensive.
What does a rising share against last year actually mean?
It means that element is taking more of the budget than it did, which is a different signal from simply costing a lot. A large but flat element is usually a serviced system behaving normally.
An element rising two years running has generally stopped being maintenance. It is a defect being repaired repeatedly, and the file exists to make that visible while it is still a capital decision rather than a failure.
Should contracted work be logged here too?
Yes, and it is the most common omission. Work carried out under a service contract is often invoiced as a single annual figure and never broken down per job, which quietly understates whichever elements that contract covers.
If the contract cannot be split per job, apportion it across the elements it covers and note that you have. An approximate split is far better than an element total that is missing a whole contract.
How many elements should a building be split into?
This template uses sixteen, which is enough to be meaningful without becoming a taxonomy exercise. It covers the envelope, the interior, the main services, life safety, and external areas.
What matters more than the number is that the convention is written down and used consistently. A leak above a ceiling has to be booked the same way every time or two years of data stop being comparable.
Does this measure whether preventive maintenance is being done on time?
No, and it is deliberately not trying to. There is no due date and no adherence measure anywhere in this file; it records what was done and what it cost, not whether it happened when it should have.
Schedule adherence is a preventive maintenance log's job, which measures each visit against the date it was due. The two are complementary and there is almost no overlap between them.
What is spend per unit of area for?
Comparison. A building that spent thirty-four thousand tells you nothing on its own, because it may be a small building in trouble or a large one in good order.
Divided by gross floor area it becomes a rate, and a rate can be ranked against other buildings and against previous years. It is the one figure in the log that travels beyond the building it describes.
In one paragraph
A building maintenance log records every job on one building and sorts the money by the part of the building that consumed it. Tag the element as you log each job rather than at year end, keep statutory work as its own type, and log contracted work even when it arrives as one invoice. Then read the element table: share says where the budget went, and the trend column says which element has stopped being a maintenance line and become a capital case.
The log is the floor, not the ceiling
Keep one per building per year, tag elements consistently and watch the trend column rather than the totals. Once you are comparing buildings, or want a rising element flagged before the second year is over, the spreadsheet has done its job.
