GitLaw How-To guides
Set reminders for key contract dates
To set a reminder in GitLaw, open the Reminders area from the main navigation, click New reminder, give it a name and a due date, choose who to notify, then save. GitLaw emails the chosen recipients when the date arrives. You can link reminders to documents and contacts, make them recur, and let GitLaw create them automatically from dates it extracts when you upload a contract.
Before you start: a GitLaw account.
How do I create a reminder in GitLaw?
Never miss a renewal window or payment deadline. GitLaw lets you attach reminders directly to documents and contacts:
- Open the Reminders area from the main navigation.
- Click "New reminder" and give it a name (for example, "Acme MSA renewal").
- Set the due date: the date you want to be reminded.
- Optionally link the reminder to one or more documents or contacts so it appears on their detail views.
- Choose a recurrence if the deadline repeats. Options include daily, weekly, monthly, quarterly, yearly, or a custom interval.
- Add a note (optional) for any context you want included in the reminder email.
- Choose who to notify. In an organisation, set the Notify field: No one, All members, or Specific people. Everyone on that list receives the reminder email.
- Save. GitLaw emails the chosen recipients when the due date is reached.
How reminders are organised
Reminders are grouped into four buckets by urgency, so you can see what needs attention at a glance:
| Group | What it means |
|---|---|
| Overdue | Due date has passed and not yet marked complete |
| Today | Due today |
| This week | Due later this week (after today) |
| Upcoming | Due beyond this week |
Completed reminders are kept separately and do not appear in the urgency groups unless you choose to view them.
How recurring reminders work
When you mark a recurring reminder complete, GitLaw automatically schedules the next occurrence, so you do not need to recreate it. Recurrence ends either on an end date you specify or after a maximum number of occurrences. If you set neither, the reminder repeats indefinitely.
AI-suggested reminders from uploaded contracts
When you import a Word or PDF contract, GitLaw looks for the dates the contract sets deadlines on, such as renewal and expiry, notice and payment deadlines, reporting obligations, reviews and termination windows, and can create reminders from them automatically. This is a best-effort read of the document, not a guarantee that every deadline is caught, which is why automatically created reminders are tagged inferred: check them against the contract and add by hand anything it missed. To confirm an inferred reminder, open it and save any edit, or use the explicit confirm action; the inferred tag is removed and the reminder is treated as fully user-owned from that point.
Reminders on a contact
If a reminder is linked to a document, and that document is associated with a contact, the reminder also appears on the Notifications tab of the contact's detail view. This gives you a single place to see every upcoming deadline related to a counterparty.
Completing, editing and deleting reminders
- Mark complete: open the reminder and click Mark as complete. For recurring reminders this schedules the next occurrence; for one-off reminders it moves the item to your completed list.
- Edit: open any reminder to change its name, due date, note, linked documents, linked contacts or recurrence.
- Delete: choose Delete from the reminder detail to remove it entirely.
Frequently asked questions
How am I notified when a reminder is due?
GitLaw sends an email when the due date is reached, including any note you added to the reminder. In an organisation, the Notify field decides who receives it: no one, all members, or specific people.
What does the inferred tag on a reminder mean?
It marks a reminder GitLaw created automatically from dates extracted from an uploaded contract. Confirm it by opening it and saving an edit, or using the confirm action, and the tag is removed.
Do recurring reminders stop on their own?
Recurrence ends on the end date you specify or after a maximum number of occurrences. If you set neither, the reminder repeats indefinitely.
Related articles
Reviewed by the GitLaw team. Last updated 29 July 2026.