You Don't Need a CMMS. You Need a Camera.

Every facilities management article on the internet eventually tells you to buy a CMMS. Computerized Maintenance Management System. The name alone should be a warning. If you need four words and an acronym to describe what the software does, it probably does more than you need.

For a hospital system with 200 buildings and a 40-person maintenance team, a CMMS makes sense. For a facilities manager running three buildings with two maintenance staff and a handful of contractors, it's a solution to a problem you don't have.

Here's the problem you actually have: you walked a building today, spotted eight issues, photographed three of them, and wrote down zero. By Friday, you'll remember five. The property owner will ask about the one you forgot.

The CMMS trap

CMMS platforms are built for enterprise operations. They manage work orders, parts inventory, preventive maintenance schedules, asset lifecycles, and vendor contracts. They require setup: asset trees, location hierarchies, failure codes, priority matrices. Some require a dedicated admin.

The sales pitch is compelling. Everything in one place. Full visibility. Data-driven maintenance. The demo looks great. Then you try to roll it out to a team of three people who mostly communicate via group text, and reality sets in.

Your maintenance tech doesn't want to fill out a work order form with 12 fields. They want to take a photo of the broken thing, say what's wrong with it, and move on. Your property owner doesn't want to log into a dashboard. They want an email with a PDF that says what was found and what's being done about it.

The gap between what the CMMS offers and what a small team actually uses is enormous. Six months after purchase, you're using a fraction of the features and paying for all of them.

What small teams actually need

Strip it down to what matters. A facilities team with one to five buildings and one to five people needs exactly four things:

1. A fast way to capture issues in the field. Photo, description, location, category. In under 15 seconds, while standing in a hallway with a tenant waiting.
2. A record organized by building. Not a global feed. Not a Kanban board. A list of issues per building that you can scroll through and know what's open.
3. Status tracking. Open, in progress, resolved. That's it. Maybe a priority flag. You don't need failure codes or mean-time-to-repair calculations.
4. A way to share a report. With the property owner, the contractor, the tenant who reported the issue. A PDF or link that shows the photos, the status, and what happened.

That's the whole system. Capture, organize, track, share. Everything else is overhead until your operation is big enough to need it.

The camera is the system

The single most useful thing a facilities manager carries is already in their pocket. The phone camera is the fastest, most reliable way to document a building condition. It captures what's wrong, where it is, and when you found it, all in one action.

The problem isn't the camera. It's what happens after. The photo goes into the camera roll, mixed in with 4,000 other images. No building tag. No category. No description beyond whatever you can remember three hours later when you sit down to update the spreadsheet.

The fix isn't adding a CMMS on top. It's adding structure around the capture. Tag the photo with a building and a category at the moment you take it. Add a one-line description while you're standing in front of the problem. Let the timestamp and GPS do the rest.

When the capture is structured, the report writes itself. When the capture is a camera roll full of unlabeled photos, the report takes an hour of your evening.

The spreadsheet phase

Most small facilities teams land on spreadsheets because it's the path of least resistance. A Google Sheet with columns for date, building, location, issue, status, and notes. It works for a while.

Then you hit the limits. Photos don't live in the spreadsheet, they live in a shared drive folder that you have to cross-reference by filename. The sheet gets long and nobody archives resolved items. Two people edit it at the same time and overwrite each other's updates. The property owner asks for a formatted report and you spend 45 minutes copying cells into a Word document.

Spreadsheets aren't wrong. They're a sign that you need structure but not software. The question is what the next step should be, and for most small teams, the answer isn't a $200/month CMMS. It's something closer to a structured logbook that handles photos natively and exports clean reports.

When you actually need a CMMS

To be clear: CMMS platforms exist for good reasons. You probably need one if:

• You manage parts inventory. Tracking stock levels, reorder points, and parts-per-asset is real CMMS territory.
• You run preventive maintenance schedules. Recurring work orders with compliance requirements, due dates, and audit trails that regulators inspect.
• You have more than 10 buildings or more than 10 maintenance staff. At that scale, the coordination problem is real and a lightweight tool won't solve it.
• You need to track asset lifecycles. When every HVAC unit, elevator, and roof membrane has a replacement date and warranty status, you need a database, not a logbook.

If none of that applies, you're buying capability you won't use. And unused software isn't free. It's a monthly cost plus the ongoing tax of a system nobody fully adopted.

The real workflow

Here's what a realistic facilities workflow looks like for a small team:

Monday morning. Walk Building A. Spot a ceiling tile stain in the second-floor corridor. Photograph it. Tag it: Building A, Interior, Medium priority. Note: "Water stain on ceiling tile, 2nd floor east corridor near unit 208. No active drip. Check roof drain above."

That afternoon. Contractor texts that the parking lot light in Building B is fixed. Open the issue, mark it resolved, snap a photo of the working light.

Friday. Send the property owner a report: here's what was found this week, here's what's open, here's what got resolved. Photos attached. Five minutes to generate, not forty-five.

That workflow doesn't need a CMMS. It needs a camera with structure around it.

Start with what you'll actually use

The best system is the one your team will use every day. A CMMS that only the manager logs into is worse than a shared note that everyone updates. A photo log that gets filled out in the field is worth more than a work order system that gets filled out back at the office, from memory, two days later.

Start with capture. Get that right. Everything else, the reports, the tracking, the audit trail, follows from having good records in the first place. And good records start with a camera and 10 seconds of context.