Building management software for the people who keep buildings running

What building management software means here

Building management software, in the sense TaskLoop uses it, is software for running the day-to-day operations of a building: taking in resident and tenant requests, turning them into work orders, assigning them to technicians, following up until the job is done, and keeping a record that proves it. It is the system the building office, the facility manager and the maintenance team work in every day.

That definition needs one clarification, because the term is used in two different ways.

BMS in engineering means building automation

If you ask a chief engineer or an MEP consultant what a BMS is, they will describe a building automation system. It is the control layer that monitors and runs equipment: chillers, AHUs, fan coil units, pumps, lighting circuits, sometimes access control and fire alarm interfaces. It talks to that equipment over protocols such as BACnet or Modbus, shows alarms and trends on a front-end workstation, and adjusts setpoints automatically. Siemens, Honeywell, Johnson Controls and Schneider Electric are typical names in that world.

TaskLoop is not that. It does not read sensors, control plant, or connect to the BMS front end. There is no IoT integration.

TaskLoop is the operations and maintenance layer

What a building automation system does not do is manage people. When the BMS raises a high-temperature alarm on a chiller, someone still has to be told, go and look, fix it or call the contractor, and record what was done. When a resident in a tower reports a leaking tap, there is no sensor involved at all. That human workflow is where TaskLoop sits:

• Work orders for corrective jobs, from a flickering light in a corridor to a blocked drain in a car park.
• Resident and tenant requests, registered by the building office and tracked from report to completion.
• Preventive maintenance jobs such as filter changes, pump checks and fire door inspections, created as tasks with deadlines and instructions. Recurring schedules and inspection checklists generate these tasks automatically.
• Inspections and snag lists, where each item becomes a task with an owner and a photo when it is closed.
• Contractor coordination, so that jobs handed to the lift company or the fire system vendor are still tracked. Contractors can receive and close their jobs directly, with photo proof.

In the language of the industry, this is closer to a lightweight CMMS or the help-desk part of a CAFM system than to a BMS. If you want the long version of that distinction, read CMMS vs CAFM vs BMS.

Who it is for

TaskLoop is built for the people who keep a building running rather than the people who design its controls:

• Building managers and community managers in residential towers, who take requests from residents, deal with move-ins and move-outs, and answer to an owners’ association or a landlord.
• Facility managers in commercial buildings and offices, who look after common areas, tenant requests and service standards across one or several sites.
• Chief engineers and maintenance supervisors, who plan the technicians’ day, decide what is urgent, and need to know which jobs are still open at the end of the shift.
• Maintenance technicians, cleaners and security staff, who receive the work on their phone and close it on site.
• Facility management companies, who run several buildings for different clients and have to show each client what was done. See facility management companies.

Common problems in building operations

Requests arrive everywhere

A resident calls the concierge, a tenant emails the property manager, a board member sends a WhatsApp message with a photo, and a technician notices something on his rounds. Each channel has its own memory. When the resident calls again a week later, nobody can say who had the job or what happened to it.

Nobody owns the job

In a shared chat group, a request for a plumber is seen by six people. Each assumes one of the others will pick it up. Two technicians turn up, or none does.

No proof and no timeline

When a tenant complains that the air conditioning in their office was never fixed, the building manager needs to show when the request came in, who went, and what they did. A paper logbook or a chat thread rarely answers that.

Preventive work slips behind reactive work

Every building has a list of jobs that should happen on a schedule: AHU filter changes, water tank cleaning, generator test runs, fire door checks. When the day fills up with resident calls, these jobs are the first to slip, and nobody notices until something fails.

Contractors are a black box

Lift maintenance, fire systems and specialist repairs are often handed to outside companies. Once the call is made, the building office loses track of the job until the invoice arrives.

Managers manage by complaint

Without a live view of open work, the facility manager learns about problems when an owner or a tenant escalates them. There is no data to show which requests take longest, which floors generate the most faults, or whether the team is understaffed.

How TaskLoop handles each problem

One place for every request. Requests from every channel are registered in the admin dashboard, with the unit or area, a category, a description and a priority. Requests that arrive by phone or at the desk are typed in once, and from then on they are tracked like everything else. Residents and tenants can also report issues themselves through a QR code in their unit, a common area or on an asset.

One owner per work order. Each job is assigned to a named person or a department, with a deadline and instructions such as access arrangements or the parts to bring. The technician receives a push notification on the staff app and accepts the job, so there is no doubt who has it.

A timeline and photo proof. Every status change is recorded. When the technician closes the job, they can attach a photo, and the completion timestamp is stored. The building manager can answer “when was this fixed?” in seconds, with evidence.

Escalation instead of silence. If a work order runs past its deadline, it escalates to a supervisor. A forgotten job becomes visible before the resident has to call again.

Preventive work in the same queue. Planned jobs are created as tasks next to reactive work, with the same assignment, deadline and proof. They can no longer disappear because they live in a separate spreadsheet. TaskLoop repeats these jobs automatically on the schedule you set.

Contractor jobs stay tracked. A job handed to an outside company is still logged as a task with an owner, a deadline and a record of the outcome. Contractors can receive and close the job themselves, with photo proof.

Reports that show where time goes. The dashboard shows open work and department workload in real time. Reports show task completion rates, response and completion times and staff performance, so the facility manager can see which request types are slow and where to add capacity.

A typical workflow

Take a residential tower on a weekday morning.

1. Request. A resident on the 14th floor tells the concierge that the corridor light outside her flat has been flickering for two days. The concierge registers it in the dashboard as an electrical request for the 14th-floor corridor, normal priority.
2. Assign. The building office assigns it to the electrician on shift, with a deadline of end of day and a note that a ladder is needed.
3. Act. The electrician receives a push notification, accepts the job, replaces the driver, takes a photo of the working light and closes the task. The completion time is recorded.
4. Review. At the end of the week the building manager reviews the reports. Electrical requests on the upper floors are taking longer than average, and the same corridor has appeared twice. That is a pattern to raise with the chief engineer.

The same loop applies to a tenant’s office in a commercial building, a leak found in a car park, or a planned pump check.

Manual methods vs TaskLoop

What TaskLoop is not

Being clear about scope saves everyone time.

• Not a building automation system. TaskLoop does not monitor or control HVAC, lighting, pumps or any other equipment, and does not integrate with BACnet, Modbus, sensors or meters.
• Not an IoT platform. There are no connected devices or automatic alarms feeding into it. People raise the work.
• Not a full enterprise asset management suite. It does not manage spare-parts inventory, purchasing, or depreciation of assets.
• Not accounting or property management software. Service charges, leases, rent collection and owner statements belong in your property or accounting system.
• Not a resident social app. It is for requests and the work that follows, not for community announcements or amenity bookings.

TaskLoop is the layer where requests become owned, tracked, finished work. For many building teams that is the missing piece, because the plant is already automated and the accounts are already in software, while the daily work still runs on phone calls and chat groups.

Getting started

The quickest way to judge whether TaskLoop fits is to see your own request types in it. In a demo we walk through how requests reach your building office today, set up a sample flow for your buildings, and show the dashboard, the staff app and the reports. If you also run hotel or serviced apartment operations, the same platform covers them; see hotel management. For crews that are not tied to one building, see task management. Pricing is quote-based; see pricing.