Obligations — never miss a renewal again
Renewal dates, notice deadlines and payment milestones, pulled out of the signed text automatically.
The expensive mistakes in contracts are usually dates. A contract renews because nobody remembered the notice window; a milestone slips because it lived in clause 14 and nowhere else.
When an agreement completes, SignSpry reads it and files what you're committed to.
What it finds
| Type | Example |
|---|---|
| Term expiry | "shall remain in force until 31 March 2027" |
| Auto-renewal | "shall thereafter be automatically renewed" |
| Non-renewal notice deadline | derived — the renewal date minus the notice window |
| Payment due | "shall pay ₹4,50,000 per month within 30 days" |
| Delivery / milestone | "shall deliver the integration by 15 July 2026" |
| Review point | "the parties shall review performance quarterly" |
The notice deadline is the one worth pausing on. If a contract renews on 31 March and requires 60 days' notice, the date that actually matters to you is 30 January — and that date appears nowhere in the document. SignSpry calculates it.
Reminders
Each obligation has a lead time — 30 days for renewals and notice deadlines, 7 for everything else. You get an email that far ahead. Adjust the lead time per obligation, snooze by a week, mark done, or dismiss.
Adding your own
Not everything is in the text. Add obligation files anything you like against an agreement, with its own reminder.
Checking the work
Every auto-detected obligation keeps the sentence it came from — expand Where this came from to see it. Use Re-scan agreements to look through documents signed before this feature existed.