Report parameter management without ad hoc production edits

The operational bottleneck

Report owners needed parameter changes across more than 150 reports. Ad hoc edits created avoidable coordination, audit, and production-risk problems, especially when the change had to move through a recurring reporting workflow.

Model variation through metadata

The dashboard was a full-stack workflow driven by decoupled metadata rather than a separate bespoke screen for each report. That made report variation explicit and gave the system a reusable way to represent which parameters could change and how those changes should move through review.

Make change control visible

Soft locks reduced conflicting edits. Versioning preserved the state being reviewed, while audit logs made the change history traceable. Approval workflows made the boundary between editing a proposed value and accepting it operationally visible.

Together, these controls moved report-parameter management away from ad hoc production edits and toward a workflow that could be reviewed before it was used.

Revamp for reuse

A later revamp applied clean-architecture and atomic-modelling ideas to make the dashboard easier to scale, keep consistent, and reuse. The important move was not another report-specific screen; it was keeping configuration, review, history, and approval as explicit parts of the system.