A substantial proportion of commercial buildings in India have a building management system that functions as an expensive monitoring screen. The capability exists; the configuration does not. The most common condition is a BMS commissioned at handover with default parameters and never revisited. Occupancy patterns change, tenants move, schedules shift and the BMS continues executing a configuration designed for a building that no longer exists. Schedule review is the highest-return intervention available. Comparing programmed operating schedules against actual occupancy hours, floor by floor, routinely identifies systems running several hours daily without benefit. This requires no capital and no vendor. Alarm management determines whether the system is used. A BMS generating four hundred alarms daily trains operators to ignore alarms entirely. Alarm rationalisation, suppressing nuisance alarms and prioritising consequential ones, restores the alarm function to usefulness. A well-configured system should generate a small number of alarms that each require action. Trend logging converts the BMS from a status display into a diagnostic tool. Logged chilled water temperatures, valve positions, zone temperatures and equipment run hours allow pattern analysis that real-time display cannot provide. Most systems have this capability disabled or unreviewed. Operator competence is frequently the binding constraint. A technician trained to acknowledge alarms and restart equipment is operating a fraction of the system. Structured training on the actual installed platform, rather than generic BMS concepts, changes utilisation substantially. Integration ambitions should follow basic utilisation. A building that has not reviewed its schedules in four years does not need an IoT integration layer.