Key Takeaways
- The department you inherited has plenty of problems you can describe and almost none you can prove. The assessment closes that gap.
- Five questions cover it, and not one of them needs software to answer. A clipboard and a month of honest counting will do.
- What you end up with is a baseline. Everything you change afterwards is measured against it, including whether you needed a system at all.
What are you actually trying to find out?
Five things, and none of them is a judgement about the department. What you own. What is already owed. What fails, and how often. Who does the work. Where the knowledge sits when nobody has written it down.
Write it for yourself. Its job is to replace what you believe with what you can show.
How do you build an asset list when there isn't one?
You walk the floor and build it yourself, one unit at a time. Whatever list you were handed has been decaying since somebody stopped updating it.
A partial register is the ordinary condition of the trade. Only 58% of facilities-maintenance teams use dedicated software for their asset register, according to SFG20's latest State of Facilities Management report, published in 2026. Half still keep at least part of it in a spreadsheet. What you were handed was probably accurate once.
Keep each entry thin enough that you will actually finish:
- What it is, in the name the crew uses rather than the one on the invoice.
- Where it is, specifically enough that somebody new could walk to it.
- What stops if it stops, which is the only criticality rating you need this early.
- Make, model and serial number, read off the machine rather than off a purchase order.
How do you find the real backlog?
You measure it forward. The backlog here exists as a habit rather than a document, so there is nothing to go and read. Route every incoming request through one channel and count for a month.
In a department with no system, a request is a conversation. Somebody catches you by the loading bay, you nod, and the job survives only as long as you remember it. The ones you forgot are still work nobody is counting, and eventually people stop bothering to ask.
That month also tells you which department you took over. Teams without a system fall into two camps that look identical from the outside. One runs on spreadsheets: organized, inefficient, honest about what is outstanding. The other is firefighting, where the backlog stays invisible because anything urgent becomes an emergency and everything else gets dropped. They need different things from you next.
How do you learn what actually breaks, and how often?
You ask the people who fix it. The failure history you want was never written down, so it lives in the crew's memory, and the fastest route into it is a direct question: which machines do you dread?
Memory leans toward the dramatic and the recent, so push for specifics. What did you repair twice this year? Which one has a workaround that only works if you already know it? Those answers give you a shortlist no spreadsheet could have produced.
Treat it as a shortlist rather than a finding, since you are working from one crew's recall and your own data will overturn some of it. Holistic Industries cut grow room turnover time by 50% once preventive work was scheduled against the equipment that needed it. Knowing what to schedule came first.
How do you gauge the team without putting them on the defensive?
You measure the work and never the people. A new manager counting things looks exactly like a new manager building a case for cuts, and your crew has seen that film before.
Their reading is rational. Technicians resist efficiency for a reason nobody says out loud: if ten people become efficient enough that eight would do, two of them are gone. Resistance to being measured is self-interest working correctly, and it deserves a straight answer.
The straight answer is to show them early what the count is for. A maintenance director with thirty years on the floor used work order volume to prove a single manager was carrying more than one person's load, and won two technicians with it. The record argued for the team.
Be realistic about the roster. 65% of manufacturers name attracting and keeping talent as their primary business challenge, according to the National Association of Manufacturers' Q1 2024 outlook survey. The people in front of you are very likely the people you will have next year, so assess them as a fixed asset.
What does a finished assessment actually give you?
A baseline and an argument. The baseline is the state of the department on the day you stopped guessing. The argument is everything you can now prove to somebody who was not there.
Maintenance is a black box to most organizations. One head of engineering at a manufacturer running fifteen sites described operations where the only figure anybody upstairs could produce was a yearly maintenance total, with no way to say which assets had eaten it. You are standing inside that box, and the assessment switches a light on. Grace Healthcare describes the change as accountability and transparency, meaning the work became visible to the people depending on it.
One boundary is worth naming. An assessment gives you the present. No amount of looking recovers ten years of failure data nobody recorded. What you get is a starting line.
It also settles a question you may not have thought to ask yet. Whether this operation has outgrown the tools it runs on is a real decision, and the assessment is what puts evidence under it. Make that call on its own terms, once the picture is finished.
Week one, you could describe the department, and so could everyone above you. What you hold at the end of an assessment is a list nobody can dispute, a count nobody can argue down, and a number that makes everything you do next measurable.
That is also the standard to hold any vendor to. Ask one to show you the report naming which assets failed most this quarter. Then ask what has to be entered, by whom, and at which moment, for that report to be true. The distance between those two answers is the size of the job they are quietly handing you.
