We report under CSRD in Europe and BRSR in India. Your tool claims to support both — but these frameworks change constantly. How do you keep pace, and what happens when your content is out of date?

The full executive answer

First, what "support" means precisely, because overclaiming here is how vendors get thrown out of CSustO offices: the platform models both standards structurally — CSRD with double materiality as an explicit materiality state, BRSR as a first-class standard alongside ISSB and TCFD — and manages your readiness per disclosure: materiality, data status from missing to assured, owner, deadline, overdue flags. It is a readiness and orchestration layer. It is not a legal-content subscription service, and it does not file anything on your behalf — your reporting counsel and assurance provider stay in the loop, as they must.

On keeping pace: the structural layer is the stable part — materiality, data maturity, ownership and deadlines survive framework revisions, which mostly change disclosure lists rather than the discipline of tracking them. Disclosure-level content updates ship through our normal release process, visible on the public changelog; and because the AI-generated assessments carry framework citations on every recommendation, your team can always see which version of which framework a claim rests on and challenge it.

The honest gap: we do not yet have a dedicated regulatory-content team doing same-week updates the way a Big Four subscription does — at our stage, framework updates ride the product release cycle, and founding customers with live CSRD or BRSR deadlines effectively co-steer which updates ship first. That is stated plainly because you would discover it in week two anyway, and because for the structural work the platform does, it is the right trade at this stage.