Keep contract-linked obligations, due dates, evidence references, verification notes and recorded waivers in one shared workspace.

Obligation Desk opens with a deadline ledger for open commitments beside the working obligation queue. Accountable owners and due dates remain visible while reviewers inspect the contract context, evidence reference and verification rationale. Completion and waiver decisions retain their supporting notes in the record history.
Built for Legal operations, procurement and account teams coordinating contractual deliverables.
Keep contract-linked obligations, due dates, evidence references, verification notes and recorded waivers in one shared workspace.
Link a named obligation to a contract, owner, due date, obligation type and required deliverable.
See when the review window starts, adjust the delivery deadline, and record the evidence reference and review rationale. Changed completed evidence, verifier or deadline must return to review.
Completion requires evidence, a verifier and an outcome. Waiver requires an explicit rationale retained in history.
Keep counterparty and scope guidance alongside the contract reference and expected review lead time.
Link a named obligation to a contract, owner, due date, obligation type and required deliverable.
See open obligations ordered by due date, with owners, review-window start dates and delivery deadlines.
Completion requires evidence, a verifier and an outcome. Waiver requires an explicit rationale retained in history.
Retain earlier stages, decision notes and timestamps inside the work record when a review is saved.
The pilot uses 2 tables with fictional records. No external database is needed to explore the source app.
| Table | Sample data | What it stores |
|---|---|---|
| Contract register | 5 sample records | Reference codes, names, policy values and review guidance. |
| Obligation records | 16 sample records | Fictional work records with contextual fields, saved policy, stages and embedded decision history. |
Records operational obligations; it does not interpret contracts or provide legal advice. Evidence is a reference, not an uploaded file. No e-signature, automated reminders or enforced verifier roles. English desktop pilot. Loaded views and counts cover up to 500 rows per table. No concurrent-update protection. Business-write lifecycle, package export and clean installation remain unverified.
This design is a starting point. Describe the look you want, add your logo and brand colors, or ask for new features in a prompt. Use the starter prompt to build your own version in the ToolJet AI builder, or use a suggested prompt to modify an app you already have. Review and test the result.
Suggested prompts describe changes you can request. Additional features and translations still need to be built and tested.
Choose ToolJet Cloud, or download the application package to import into your self-hosted instance once the template is released.
Explore the sample records in ToolJet Database, then add your records and configure the workflow for your team.
Describe your preferred design, branding, and new features in the AI builder. Test your workflow, then share your app with the people who need it.
Keep contract-linked obligations, due dates, evidence references, verification notes and recorded waivers in one shared workspace. It includes three connected screens, two ToolJet Database tables, five reference records and sixteen fictional work records.
Link a named obligation to a contract, owner, due date, obligation type and required deliverable. See when the review window starts, adjust the delivery deadline, and record the evidence reference and review rationale. Changed completed evidence, verifier or deadline must return to review. Completion requires evidence, a verifier and an outcome. Waiver requires an explicit rationale retained in history.
Yes. New records copy their reference rules. Editing the reference register does not silently rewrite existing work.
Records operational obligations; it does not interpret contracts or provide legal advice. Evidence is a reference, not an uploaded file. No e-signature, automated reminders or enforced verifier roles.
Yes. Use the starter prompt to request changes to branding, layout, fields or workflow. Additional features and languages must be built and tested.