The new features let operations staff create and apply short-term or experimental operation plans for power equipment. A wrong plan could affect operating costs and supply stability: power supply could be interrupted, or equipment might not charge as needed for the next day.
Plans are uploaded as CSV files, and each upload replaces the selected day's data as a snapshot. Anything missing from the file can be treated as deleted. The relationship between what the user does, how the file is validated and how the data is updated had to be defined with care.
A similar app used elsewhere in the same business showed why this mattered. The boundary between days, especially at midnight, was unclear, and mistakes were frequent. Users had to remind each other what to watch out for. Errors could say only "There is an error. Please contact the person in charge", show a bare code, or show nothing. People could not tell how to fix problems themselves, and the app eventually fell out of use.
My reading of the cause: a manager asks for a feature and an engineer builds it as requested. Neither is wrong, but no one clearly owns the decisions between the request and the implementation. This project had no designer or project manager. That conversation was my work.
Some requirements could not be decided without seeing concrete behaviour. The scale also had to be planned for: around six devices at first release, and 50 to 100 devices across 48 half-hour slots later.