How to set up automated reminders and notifications in Juro

If you’re managing contracts, you know how easy it is for deadlines and approvals to fall through the cracks. Maybe it’s renewal dates, maybe it’s a signature you’re still waiting on—either way, nobody wants to be the person who missed something important. This guide is for anyone using Juro who wants to stop chasing people (or being chased) and let the tool do the nagging for you.

Let’s break down how to get automated reminders and notifications working in Juro, what’s worth setting up, and what you can safely ignore.

Why bother with automated reminders?

You probably didn’t get into contract work for the thrill of manual follow-ups. Automated reminders keep things moving—people sign, deadlines don’t sneak up, and you spend less time in your inbox. The thing is, not all reminders are created equal. Too many, and people tune them out. Too few, and stuff gets missed.

Juro gives you several ways to automate reminders and notifications, but you’ll want to be specific about what you set up. Otherwise, you’re just swapping one headache for another.

Step 1: Understand Juro’s notification system

Before you start flipping switches, take a minute to understand what Juro can (and can’t) do with notifications.

Types of notifications in Juro:

Email notifications: Juro sends these out for things like signature requests, approval steps, and contract status changes.
In-app notifications: These pop up in Juro itself, but honestly—if you’re not in Juro all day, you’ll miss them.
Automated reminders: These are scheduled nudges, typically for contract deadlines, renewals, or when someone needs to take action.

What doesn’t Juro do (as of mid-2024):

No SMS or Slack reminders out-of-the-box.
Limited customization of email templates.
No crazy “if this, then that” automation natively—you’ll need Zapier or similar for that.

Pro tip: Before setting up reminders, check your team’s notification fatigue. If everyone’s ignoring their inbox, start with the most critical reminders only.

Step 2: Decide what needs a reminder (and what doesn’t)

Not every contract or action needs a reminder. Here’s what usually matters:

Signature requests: When someone needs to sign, and you don’t want to chase them.
Approval steps: If you’re waiting on internal approval and things stall.
Renewal/expiry dates: So you don’t get surprised by auto-renewals or missed deadlines.
Key contract milestones: Anything that, if missed, would cause a small fire.

What not to bother with:

Routine status changes—most people don’t care.
Reminders for folks who are always on top of things. (They’ll just get annoyed.)
Anything you wouldn’t chase manually.

Make a quick list: what’s actually caused problems in the past? That’s where reminders make sense.

Step 3: Set up automated reminders for contract deadlines

The most common use case: you want to know before a contract expires or renews automatically.

Here’s how to do it:

Tag your key dates correctly.
In Juro, make sure every contract has the relevant date fields filled in (e.g., “End date,” “Renewal date”).
If you skip this step, the system can’t remind you—the field has to exist and be populated.
Set up deadline reminders.
Go to your contract template or an individual contract.
Look for the section labeled “Reminders” or “Notifications” (wording may vary slightly depending on your Juro version).
Choose “Add reminder.”
Pick the date field you want the reminder tied to (like “End date”).
Set how far in advance you want the reminder—common options are 30, 14, or 7 days before, but you can usually set a custom number.
Decide who should get the reminder—yourself, a team, or external parties.
Save and test.
Hit “Save.” If your version supports it, send a test reminder to yourself first to see how it shows up.

What works:
Reminders about renewals and expiries are almost always worth it. Set them up for any contract where missing the date costs you money or credibility.

What doesn’t:
Reminding the whole team about every contract expiry—overkill. Stick to the contract owner or a small group.

Step 4: Automate signature and approval reminders

Chasing signatures is nobody’s idea of a good time. Juro can automate this, but you have to tell it how aggressive to be.

To set up signature or approval reminders:

Within your contract workflow:
When sending a contract for signature, ensure you’ve added the right signers and set their roles.
In most Juro setups, you’ll see an option to “Remind signers” automatically after X days if they haven’t signed.
Configure frequency and recipients:
Choose how often reminders go out—daily, every three days, or only once.
Decide if only the signer gets nudged, or if you (the sender) also want a heads-up.
Approval steps:
If you have an approval workflow, you can set reminders for approvers who haven’t acted.
Same process: pick the trigger (e.g., “not approved after 2 days”), set recipients.

Be careful:
More isn’t always better. If you remind someone every day, you’re training them to ignore you. Once every few days is usually fine.

Step 5: Customize who gets notified (and avoid spamming people)

Juro’s default is to notify the contract owner, but you can add others—just do it thoughtfully.

Best practices:

Role-based reminders: Assign reminders to the person actually responsible. Don’t CC the whole legal team unless you want a mutiny.
External parties: Juro lets you send reminders to counterparties, but double-check their contact info. Nothing says “we care” like a reminder sent to the wrong address.
Multiple reminders: If more than one date matters (like notice period and renewal), set separate reminders for each.

What to ignore:
Don’t turn on every notification “just in case.” People will tune out, and when something is truly important, they’ll miss it.

Step 6: Use integrations for advanced notification workflows (optional)

If you need more than email reminders—like Slack alerts, or syncing with a project management tool—you’ll need integrations.

How to do it:

Zapier: Juro supports Zapier integrations. You can set up a Zap to trigger when a contract reaches a certain status or date, and send a Slack message, create a Trello card, etc.
API: For the truly technical, Juro’s API documentation lets you build custom notifications, but this is overkill for most teams.
Calendar sync: Some users export key dates to Google Calendar or Outlook. This isn’t as automated, but it keeps things visible.

Keep in mind:
Integrations sound great, but they can break or need upkeep. Only set up what you’ll actually use and maintain.

Step 7: Review and adjust your reminders regularly

Set-it-and-forget-it sounds nice, but in reality, contract processes change. Take five minutes each quarter to:

Check which reminders are firing.
Ask your team if they’re helpful or annoying.
Delete or tweak anything that’s not working.

Pro tip:
If people are ignoring reminders, the problem isn’t the tool—it’s the process. Less can be more.

Quick reference: Common reminder setups that actually work

Here’s what most teams find useful:

30 days before contract expiry: Reminder to contract owner.
7 days before renewal: Reminder to whoever manages renewals.
Signature not received after 3 days: Reminder to signer, cc contract owner.
Approval not given after 2 days: Reminder to approver only.

Skip reminders for every little status change—no one wants them.

Wrapping up: Keep it simple (and don’t be a robot)

Automated reminders in Juro can save your team from dropped balls and last-minute scrambles. But more isn’t always better. Start with a few critical reminders, see how they work, and adjust. If you get feedback that people are drowning in notifications, dial it back. If you’re still chasing people manually, add another reminder or tweak the timing.

Set up what you need, ignore the rest, and check in every so often. That’s how you keep contracts moving—without annoying everyone.