Ennov RIM dashboards need conflict-preserving totals

Count conflicts instead of hiding them

The direct answer is to give unresolved state conflicts their own visible population. When a central master, local affiliate record, authority portal, formal letter, submission tool, correspondence tracker, and reporting mart disagree, retain every candidate value with its source, observation time, effective date, scope, import job, owner, and confidence. Mark the portfolio item unresolved until the authorized owner records which evidence governs and why.

Do not let last-write-wins logic or a dashboard precedence rule turn a disagreement into apparent certainty. Separate stale from contradictory, missing from not applicable, future-effective from current, submitted from accepted, and local implementation from authority action. A conflict count should drill through to the competing records and the open decision, while the main total states whether unresolved items are included, excluded, or presented separately.

Publish the arithmetic behind every portfolio view

For each chart, retain the population query, object type, product granularity, market and procedure scope, legal entity, as-of time, refresh cutoff, denominator, exclusions, partial-record rule, conflict treatment, grouping logic, and calculation version. Multi-market procedures and products with several presentations can otherwise be counted once, several times, or not at all depending on a hidden join. The displayed number must be reproducible from the same frozen inputs.

Show data latency and completeness beside status. A green percentage based only on affiliates that submitted updates can look healthier as coverage falls. Report records awaiting local confirmation, authority evidence, reconciliation, or translation separately. When the taxonomy or aggregation logic changes, preserve the former calculation and bridge the movement so a reporting change is not presented as regulatory progress.

Route reconciliation without rewriting history

A reconciliation case should name the competing claims, affected market and reporting output, materiality, evidence requested, decision authority, due date, interim reporting treatment, conclusion, approval, and downstream correction. Preserve the value that appeared in each prior report and the evidence available at that time. Correcting the master is necessary; replacing historical snapshots would make earlier decisions impossible to reconstruct.

Define who can enter, import, challenge, reconcile, approve, and publish a state. A workflow completion, affiliate acknowledgement, or data-steward correction is not automatically a regulatory conclusion. Escalate questions about authority effect, legal holder, approved terms, commitment status, or market action to qualified regulatory owners, and retain the resulting source record rather than encoding the answer only in a dashboard override.

Test a portfolio with deliberate disagreement

Create a controlled test spanning one product and several markets: one portal update arrives late, one letter conflicts with an imported code, one affiliate reports a future-effective withdrawal, one shared procedure creates duplicate rows, and one taxonomy version changes mid-period. Reviewers should reproduce totals at two as-of times, isolate every disagreement, prevent accidental double counting, preserve the published snapshots, and trace the authorized reconciliation.

Ennov's official page supports the attributed centralization, structured-data, workflow, notification, dashboard, reporting, global-portfolio, product, market, registration, submission, correspondence, and commitment positioning. It does not establish a customer's source completeness, aggregation rule, reconciliation, status accuracy, validated configuration, regulatory conclusion, or outcome. Regulatory, quality, safety, labeling, supply, IT, validation, data, and legal owners retain their responsibilities.

Enterprise buyer test

Translate this change into the exact population, record type, workflow stage, decision owner, effective date, and evidence that could be affected. Ask current or prospective providers to demonstrate the named workflow with representative data and an exception—not a polished feature tour. Record what official documentation establishes, what a provider states, what the team observes, and what remains unresolved.

A defensible review also identifies the dependency outside the product. Authority interpretation, policy configuration, data quality, integrations, human judgment, approval rights, release governance, training, and retained evidence may remain customer or service responsibilities. The evaluation should preserve those boundaries instead of treating a technology claim as the complete operating model.

What we will watch next

RegQuality Review will watch the named source and affected market records for later evidence that changes status, scope, availability, implementation timing, workflow consequence, or the limits of the initial report. A later announcement does not silently overwrite this dated account; the change ledger preserves the sequence.