MaintenEase: maintenance operations for small teams.

Problem

Small maintenance teams (facilities, fleet, building ops) run on clipboards, email chains and shared spreadsheets. A tenant reports a leak, a technician gets a text, and the work order lives in someone’s inbox. PM schedules slip because nothing generates them. Asset history is scattered across photos, PDFs and memory.

Enterprise CMMS tools require implementation projects and overwhelm a four-person team.

Before

Requests arrive by phone, text and email with inconsistent detail. A coordinator triages from memory. Technicians carry paper checklists or nothing. PM work is reactive because schedules are not connected to work-order generation. Occupants have no structured way to report issues.

How it works

Submit. Occupants use the public portal: choose standard or urgent, describe the issue, add location and contact details, and optionally attach photos. Submissions land in the team’s request inbox.

Triage. A coordinator confirms location and priority, associates the correct asset and converts the request to a work order. Urgent requests notify the team immediately.

PM. Schedules auto-create work orders on interval, alongside reactive work with the same asset history.

Assistant. It can summarize open work, look up asset history and propose actions. No silent database changes.

Exceptions

Public portals create exception volume by design. QR-code submissions enter the request inbox first so maintenance can remove duplicates, confirm priority and associate the correct asset before assignment. The inbox is where exceptions live, not the work-order queue.

What I learned

An assistant that writes without asking destroys trust. Every proposed action waits for a human.

The foundation comes first. Work orders, assets and PM schedules come first; the assistant sits on top of data the team already trusts.