What columns an obligation matrix that works needs
A useful obligation matrix has, at minimum: the obligation in a concrete and actionable sentence (not 'meet deadlines' but 'notify weather-related delay within 48 hours'), the contract clause that supports it, the internal responsible party for complying with it, the date or condition that activates it, the available timeframe once activated, and the status (pending, complied, at risk, in breach). Without the supporting clause, the obligation becomes difficult to defend if someone questions it months later.
The column most often omitted and most needed is response or notification deadline: many contracts not only require complying with an obligation, but communicating a fact within a specific deadline to be able to exercise a right derived from it (an extension, an economic claim, a reservation). That column is what converts the matrix from a descriptive list into an alert tool.
Why notification deadlines are the most delicate part
When a contract conditions a right to communicating a fact within a set deadline, notifying it late can weaken that right even though the technical fact that originates it is completely real and demonstrable. A delay caused by a subcontractor who does not arrive on time may be objectively certain, but if the contract requires notifying it in 5 days and it is communicated in 20, the contractual position to claim for that delay is weakened, not from lack of substance but from lack of timely notice.
The matrix must distinguish between obligations to perform (execute something, deliver a document) and obligations to notify (communicate a fact to preserve a right). The latter need a visible day counter from the moment the fact occurs, not from when someone decides to draft the notification.
How to prioritize when there are dozens of open obligations at once
In a work of certain duration, the matrix can accumulate dozens of live obligations simultaneously: insurance to renew, document delivery milestones, response deadlines to inquiries, guarantees to activate. Prioritizing them by nearest expiration date is the basic criterion, but not the only one: an obligation expiring in 10 days that affects a relevant economic right should weigh more than one expiring in 3 days but whose consequence of breaching is smaller.
A practical criterion is crossing two variables, proximity of expiration and economic or schedule impact if breached, and treating as urgent only what scores high in both. This prevents attention from dispersing on minor administrative obligations while a notification with real economic impact approaches its deadline without being prioritized.
What evidence must be preserved for each obligation completed
Complying with a notice obligation is not just sending it: it is being able to prove later that it was sent, when, by what channel and that it reached its recipient. An email with read confirmation, a signed receipt or a time-stamped shipping record is solid evidence; a WhatsApp message without read confirmation from the correct recipient is much weaker evidence if the other party denies receiving it.
The matrix should link, for each completed row, the document or communication that proves compliance, not just mark a box as 'done'. That reference is what is needed to reconstruct when, months later, a discrepancy arises over whether a notification arrived on time or did not arrive at all.
How Bloqbase supports tracking of obligations and notices
Bloqbase allows using the Contract Analysis module to maintain obligations extracted from the contract associated with their clause, their responsible party and their deadline within the work context, rather than in a spreadsheet that needs to be manually updated and reviewed.
The tool organizes the information and evidence associated with each obligation; it does not replace the legal assessment of what effect notifying a specific fact late has or decide by itself what obligation deserves escalation. That decision continues to belong to site management or legal counsel, with the documentation already organized.