Compliance registryLaw firms & in-house teams

Every obligation logged,
risk escalating on its own —
before anyone has to check.

08

statutory categories in one workspace registry — GST to FEMA, pharma to custom

Filings, licences, and renewals tracked in one per-workspace registry, with milestones and real linked tasks — and a risk score that moves on its own as a deadline gets closer, not when someone remembers to re-triage it.

01One registry

One record type.
Eight statutory categories.

Every obligation carries an authority, jurisdiction, site or entity, periodicity, and an owner and assignee — resolved to real workspace users, not free-text names.

01

GST

Return cycles, registration renewals, and filing deadlines.

02

Income Tax

Assessment, TDS, and annual return obligations.

03

Corporate

Board resolutions, ROC filings, statutory registers.

04

Labour

PF, ESI, and workplace-compliance renewals.

05

Pharma

Drug licences, manufacturing and import approvals.

06

Environment

Consent renewals and pollution-control filings.

07

FEMA

FDI, ECB, and cross-border reporting.

08

Custom

Anything a workspace tracks on its own schedule.

02Escalating automatically

Nothing waits for
someone to notice.

Status moves from Active to Due Soon at thirty days out, then Overdue past the deadline. Risk climbs the same way — layering a per-category base severity, deadline pressure, high-consequence keywords, and any missed milestone into one Low-to-Critical score, recomputed every time the registry loads.

ActiveDue soonOverdueCritical
03Filed, and rolled forward

Closing one cycle
opens the next.

Marking a recurring obligation Filed captures the filing date and acknowledgement number, then advances the next due date by its own periodicity and resets status to Active — one action, not a re-entry.

GSTR-9 · Annual ReturnFiled
Filed on
14 Feb 2026
Acknowledgement
GST/2026/0417
Periodicity
Annual
GSTR-9 · Annual ReturnActive
Next due
14 Feb 2027
Advanced by
one periodicity cycle
No one recalculates the next cycle by hand
04Government sources, monitored daily

A daily read of gazette,
FSSAI, and state notifications.

Every day, an extraction pipeline narrows real government notifications down to the ones that actually obligate a workspace to do something — three layers, each one built to spend LLM calls only where they earn their cost.

01Deterministic skip

Ministry and subject-line filters drop routine notifications before any LLM call runs.

02LLM triage

A short yes/no pass decides relevance — bypassed outright for a fixed high-signal ministry list.

03Structured extraction

Obligation, deadline, penalty and issuing authority pulled out, anti-hallucination prompted.

  • Matched workspaces get the obligation as a task, assigned straight to their admins
  • Priority is set to High automatically when the deadline is thirty days out or less
05On the record

Built for the rest
of the workflow, not just the date.

01Bundle wizard

A Private Limited company seeds a 15-obligation GST / Income Tax / MCA / Labour starter pack in one flow.

02Milestones

Break any obligation into sub-deadlines, each with its own authority, due date and status.

03Linked tasks

Every checklist item is a real task — assignable, trackable, independent of the record's own milestones.

04Stats & filters

Four live KPI tiles double as filters across the whole workspace registry.

05Urgency strip

The six soonest deadlines across every category, always visible above the fold.

Workspace-scoped row-level security on every record — the same isolation model as every other module.

Let the risk score do the checking.

Bring your workspace’s obligations across GST, labour, pharma, or any of the eight categories, and we’ll walk you through the registry on your own data.