Reportmarshal

Companies can accumulate dashboards across several business-intelligence systems until employees no longer know which report answers a question. The supplied research confirms metadata-scanning interfaces for two major BI platforms and engineering-oriented data catalogs, while reporting no reviewed end-user router centered on 'which report should I use.' One of three referenced interfaces remains unverified, and metadata availability varies by tenant and administrative permission.

Reportmarshal would preserve organization, BI platform, workspace, report, report version, dashboard, sheet or tile, owner assertion, steward, business domain, audience description, role tag, question tag, metric name, metric-definition source, data-source reference, refresh schedule, last refresh, certification assertion, deprecation status, replacement report, permission requirement, platform access check, user identity, job-role assertion, business purpose, user question, interpreted intent, route candidate, route rationale, confidence, access decision, deep link, open event, feedback, wrong-report reason, steward correction, catalog version, audit event, retention and deletion as distinct records.

A job title does not establish need-to-know, and a metadata API does not expose every row-level or embedded permission. Report names and descriptions can be stale, duplicated or misleading. Popularity does not make a report canonical, and an open event does not prove usefulness or business value. Reportmarshal must not bypass platform authorization, expose restricted metadata, answer the business question from underlying data, infer employee performance, hide deprecated alternatives or call a routed report correct without steward review.

The pilot should use synthetic metadata plus a small permissioned set of reports from one BI platform. The likely buyer is a business-intelligence, analytics enablement, data-governance or internal-tools leader at a company with report sprawl. Platform coverage, administrator access, row-level permission semantics, metadata quality, steward workload, role taxonomy, routing accuracy, adoption, managed setup, budget and competition from catalogs or BI vendors remain unverified.

A business-intelligence, analytics enablement, data-governance or internal-tools leader responsible for report discovery across an existing BI estate.