The domain demanded high accuracy. Medico-legal terminology, reporting formats, and document structures were highly standardized, leaving very little room for interpretation.
Both teams invested considerable time in workshops to finalize the reporting framework. The solution was built on two key principles.

• Preserve report formats already familiar to doctors.
• Introduce intelligent automation by highlighting sections that required attention from transcription assistants using predefined contextual rules and algorithms.

This wasn’t just another feature.
It was the foundation on which the entire application was designed.
As development progressed, a new Project Manager joined from the client side.
With a fresh perspective came a new objective.
Instead of predefined algorithms, the expectation shifted toward a generalized platform where users could define their own report parameters and business rules.
Technically, the request appeared to be another enhancement.
Architecturally, it was something entirely different.
The project was no longer about building a specialized reporting solution. It had evolved into developing a configurable platform.
That single change fundamentally altered the application’s architecture, development effort, testing strategy, timelines, and overall project cost.
What initially appeared to be a change request opened a Pandora’s box.
The project was eventually put on hold while the revised direction was evaluated.