How to Build a Court-by-Court and Internal-Owner Risk Map to Prevent Missed Deadlines

Start with a consistent record for every relevant publication or procedural movement. At minimum, capture the court and jurisdiction, case identifier, responsible internal owner, outsourced firm if applicable, publication timestamp, date received by the team, estimated deadline, action required, current status, and completion timestamp.

The distinction between publication time and internal receipt time is essential. A team may technically receive a publication on the correct day but still have too little time to review it, assign an action, obtain client information, and prepare a filing.

Normalize timestamps before calculating performance. Store them in a single time standard, then display them in the local operating time zone. This prevents misleading comparisons between courts, platforms, and teams that record events differently.

The second layer is classification. Use a controlled list of action types, such as appeal, response, payment, document request, hearing preparation, expert evidence, or internal approval. Free-text labels make it difficult to compare risk across months.

The third layer is ownership. Distinguish the person who monitors the publication, the person who prepares the legal response, the person who reviews it, and the person who submits it. In smaller firms, one person may perform all four roles. In corporate legal departments, responsibility may be distributed among employees, business areas, and external firms.

A practical data model can include these fields:

| Field | Why it matters | |---|---| | Court and jurisdiction | Identifies institutional concentration of risk | | Source journal or tribunal system | Reveals gaps in monitoring coverage | | Publication timestamp | Establishes the starting point for analysis | | Internal receipt timestamp | Measures operational delay | | Action type | Separates routine events from high-impact tasks | | Estimated due date | Defines the time available for response | | Responsible owner | Connects exposure to capacity and accountability | | Outsourced firm | Shows external concentration and service quality | | Status and completion time | Measures whether work was completed on time | | Escalation history | Shows how often intervention was needed |

When defining due dates, document the legal assumptions used by the team. For example, the calculation may depend on the applicable procedural rule, publication date, business days, suspension periods, or a court-specific calendar. The Brazilian Code of Civil Procedure on Planalto is an important primary source for procedural rules, but it should not replace validation of the specific case and court context.

The most useful indicators are operational rather than purely financial. They show whether information arrives with enough time, whether someone takes ownership quickly, and whether the assigned professional can realistically complete the work.

A strong dashboard usually begins with six core metrics:

1. Publication frequency by court: the number of relevant publications per week or month, separated by action type.
2. Early-delivery rate: the percentage of publications received before the expected official publication date or before the internal monitoring threshold. This indicates how much preparation time the team gains.
3. Internal processing delay: the time between receipt and assignment, measured by median and 90th percentile. A high 90th percentile suggests occasional but severe bottlenecks.
4. Deadline lateness rate: the percentage of tasks completed after the internal target or legal due date. Report the numerator and denominator because a rate based on five tasks means something different from one based on 5,000.
5. Owner workload index: the number of open actions weighted by urgency and estimated effort, divided by the owner's available capacity. A queue of ten simple confirmations is not equivalent to ten complex appeals.
6. Escalation rate: the percentage of items requiring intervention by a coordinator or manager. Rising escalations may indicate unclear ownership, insufficient staffing, or unreliable external handoffs.

One practical scoring model uses a 0 to 100 scale. Assign 25 points to deadline lateness, 20 to short response windows, 20 to current workload, 15 to processing delay, 10 to publication volume, and 10 to escalation frequency. Adjust the weights after reviewing actual incidents rather than presenting the formula as a universal standard.

For example, a fictional retail legal department may find that Court A generates 38% of its monthly publications but only 12% of late tasks. Court B produces 14% of publications yet accounts for 41% of late tasks because notifications arrive with less internal preparation time and are routed through an overloaded external firm.

A fictional transportation company may discover a different pattern. Its highest risk may not be the busiest court, but the owner responsible for 76 open actions across three outsourced firms, with 18 deadlines due within five business days. The operational response is capacity redistribution, not simply more monitoring.

Validation should begin with reconciliation, not visualization. Select a sample of records from each major court, owner, and risk band, then compare the map with the original publication, case record, internal assignment, calendar entry, and final submission evidence.

A useful sample includes at least 20 high-risk records, 20 medium-risk records, and 20 apparently low-risk records when the data volume allows. Include both completed and unresolved items, because a model can look accurate while ignoring the cases that never reached a final status.

Check four types of error. First, coverage errors occur when a publication or court source is missing. Second, identity errors occur when a case is linked to the wrong process or owner. Third, timing errors occur when timestamps or due dates are calculated incorrectly. Fourth, status errors occur when an item is marked complete without reliable evidence.

Create a confusion table comparing predicted risk with actual outcome. If high-risk items frequently finish on time, the model may be over-sensitive. If low-risk items are repeatedly late, the model is missing a relevant signal, such as review dependency, client approval, or external-firm delay.

The map should also be tested after operational changes. Reassign a court portfolio, add an attorney, change an outsourced firm, or introduce automated monitoring, then compare results after 30, 60, and 90 days. This reveals whether the intervention reduced risk or merely moved work to another part of the process.

A reusable export can be built in CSV or spreadsheet format with columns for court, source, publication date, internal receipt date, expected deadline, owner, external firm, action type, workload band, risk score, status, and completion date. If the underlying system provides normalized timestamps and a complete process history, the team can refresh the file without rebuilding the analysis manually.

The CNJ DataJud system is a useful reference for understanding structured judicial data initiatives in Brazil. It does not replace the organization's own publication and workflow records, but it reinforces the value of consistent identifiers and standardized data when comparing courts.

The first mistake is ranking courts only by publication volume. Volume matters, but a low-volume court with short response windows, unreliable routing, or difficult procedural demands may deserve a higher priority than a busy court with stable processes.

The second mistake is measuring people without measuring capacity. A responsible attorney can appear inefficient when the real issue is an unrealistic caseload, excessive review layers, missing client information, or a poorly balanced portfolio.

Another common error is treating the outsourced firm as a black box. Record which firm received the publication, when it acknowledged the task, when it delivered its recommendation, and whether the internal team had enough time to review and submit the response.

Do not use a single risk score as a substitute for judgment. The score should prioritize attention, while the underlying fields explain why an item is risky. Managers must be able to challenge the classification and correct the data.

Avoid retrospective blame as the main governance mechanism. A useful review asks where the process lost time, whether the signal was available, and which control would prevent recurrence. This produces better improvements than simply recording that someone failed to act.

Finally, do not allow the map to become a monthly presentation disconnected from daily work. Every risk category should have an owner, a response time, and an escalation path. If a red cell does not change an assignment, alert, review, or capacity decision, it is only decoration.