Obliga · for contract & procurement teams
Obliga is a contract lifecycle system built around one job: making sure every renewal, notice deadline, and cancellation window reaches a decision from the right person — on time, with a full paper trail, every time.
01 — Repository
Title, counterparty, department, owner, effective and expiry dates, renewal type, notice-period days, estimated value and currency, status, notes — plus custom fields for anything specific to your organization, added without code changes.
| Renewal type | Auto-renew · Manual · Evergreen · Fixed-term |
|---|---|
| Status | Draft record · Active · Expiring · Closed · Cancelled |
| Attachments | PDFs, scans, Word docs — stored in your own Azure storage |
| Saved views | "Expiring this quarter," "Auto-renew," "My contracts" — shareable by link |
A separate closed/history view keeps expired, cancelled, and superseded agreements out of the active portfolio without deleting the record.
02 — Notification engine
An administrator builds notice schedules as a plain sentence made real: "First notice 120 days before expiry to the Approver; repeat weekly; escalate to the Executive Stakeholder at 60 days." Every number is editable — nothing is hardcoded.
Expiry date, the notice deadline (expiry minus notice-period), or any custom date field.
Each notice point has its own recipient set — first notice to the Approver, later ones add the Executive Stakeholder.
Optional nudges — daily, weekly, every N business days — until someone responds or the next notice point takes over.
A last-resort alert fires inside a configurable final window regardless of mute, snooze, or cadence — nothing slips through silently.
03 — Decisions
Every notice carries secure, single-use decision links. The default set — configurable per organization:
Renew and Cancel are terminal — they stop the cycle outright and move the contract to "pending record update" until a Contract Manager executes it (a new expiry date, or a closed status). Renegotiate and Needs discussion are interim — they pause the current reminder, but later notice points stay armed, so escalation resumes automatically if the deadline approaches with nothing settled.
The same five-color status vocabulary appears everywhere in Obliga — the grid, the dashboard, the console — so the whole team reads urgency the same way at a glance.
04 — Oversight, audit, reporting
Exactly what will be sent and when, per contract — with mute and snooze, each requiring a one-line reason that lands in the audit trail.
Every create, update, and decision logged: who, when, old value, new value. Append-only, exportable for compliance review.
What's expiring in 30/60/90/180 days, what's awaiting a decision, and total active portfolio value — one glance, no charts to interpret.
A scheduled summary to every Contract Manager, plus CSV/Excel import and export on every grid view.
05 — Confidentiality
Department is a first-class concept — every contract has exactly one owning department, with optional visibility grants to others for shared agreements. Two tenant-wide modes: Open (everyone sees everything — the default) or Scoped (each person sees only their department's contracts). Enforcement happens at the data layer, not by hiding rows in the browser. Independent of that, any individual contract can be further restricted to named people regardless of department — for the handful of agreements that need it.
Deploys entirely inside your own Microsoft 365 tenant. Your team signs in with the identity they already have; contract data never leaves your organization's own Azure subscription.
This is the primary reason privacy-sensitive and public-sector organizations choose this model over a shared, vendor-hosted platform.
A governed record, a schedule that actually runs, and a decision that's always on file — that's the whole system.
← All Obliga guides