Time to Awareness: The KPI Every Legal Team Should Measure

Time to awareness is the elapsed time between a relevant court event becoming available and the legal team actually receiving, validating, or acknowledging it. In practical terms, it shows how quickly a firm or corporate legal department becomes aware of a publication, movement, order, or potential deadline.

The metric is different from publication date, filing date, or deadline date. A court may make information available at one moment, while a team only sees it hours later after someone checks a diary, opens a portal, identifies the correct case, and forwards the information internally.

That delay creates operational risk. A deadline can be technically visible in a court system and still be functionally invisible to the person responsible for reviewing it, assigning work, or contacting the client.

For Brazilian legal teams, the challenge is amplified by fragmented sources, multiple courts, different publication patterns, and large portfolios of cases. Manual checking can consume hours every week while still leaving uncertainty about coverage and timing.

The National Council of Justice DataJud documentation illustrates the scale and complexity of judicial data in Brazil. A useful KPI must therefore measure the operational path from source availability to usable legal intelligence, not simply whether someone eventually found the publication.

A useful report has three layers. The executive layer shows total monitored events, median time to awareness, 90th percentile, SLA attainment, coverage, and the number of high-risk exceptions. The operational layer shows performance by court, instance, team, and event type. The audit layer preserves identifiers, timestamps, source details, and transformation logic.

Pocket Jurídico can provide a practical data foundation for this model because its monitoring workflow captures publications and movements across more than 490 diaries and courts, validates the process, and presents the result in a feed. The important reporting principle is to preserve each native timestamp rather than exporting only a final status.

A typical export mapping might use fields such as event_id, process_number, court, instance, source_captured_at, pre_publication_at, process_validated_at, feed_delivered_at, publication_type, monitored_term, and status. Your actual export headers may differ, so map them in a data dictionary before building formulas or queries.

In Google Sheets, create a raw_data tab, a normalized_data tab, and a dashboard tab. In the normalized layer, convert timestamps, calculate duration in hours, classify SLA status, and derive month, week, court group, and priority fields.

A representative formula for elapsed hours is conceptually: (feed_delivered_at minus source_captured_at) multiplied by 24. A safer implementation also checks for blanks, negative values, duplicate event IDs, and timestamps outside the reporting period.

For larger volumes, Power BI can ingest a CSV export or API response, apply Power Query transformations, and calculate measures such as median duration, 90th percentile duration, and SLA rate. Microsoft’s official Power BI documentation is a useful reference for data modeling, refresh, and dashboard governance.

The dashboard should let a director answer five questions in less than a minute: Are we seeing events quickly? Where are delays concentrated? Are urgent events meeting their target? Is coverage complete? What action will reduce risk this week?

The fastest improvements usually come from removing handoffs, not from asking people to work faster. Start by listing every step between source detection and legal action, then identify where a person rechecks information that a system could validate once.

First, review monitoring coverage. Confirm that every relevant court, instance, process number, monitored name, and business term is included. A retail legal department, for example, may need to expand beyond its most frequently used courts because regional disputes often create the longest blind spots.

Second, route events by urgency. A publication that may start a deadline should go to a priority queue with an owner, while routine movements can follow the standard review process. Add escalation when no one acknowledges a priority event within the agreed interval.

Third, remove parallel spreadsheets. Deliver the publication, process context, comments, assignment, and decision history in the same workflow. Email can remain a notification channel, but it should not be the system of record for legal responsibility.

Fourth, automate the next action. From a validated publication, create a task, calendar event, or deadline review request in the office or corporate workflow. Integrations through API can synchronize monitoring data with an ERP, CRM, legal management platform, or internal application.

Fifth, use AI carefully for triage. A summary, extracted deadline, or suggested action can reduce reading time, but a responsible reviewer should confirm the legal meaning before a deadline is committed. The Brazilian Data Protection Authority guidance on processing personal data is a useful reminder to include access control, purpose limitation, and governance in automation decisions.

An anonymized retail legal operation illustrates the potential of focused changes. After expanding coverage to 120 courts, removing manual diary checks, and routing validated publications into a single feed, its reported median time to awareness fell from approximately 48 hours to 6 hours. The result came from coverage and workflow redesign together, not from a single dashboard formula.