nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Best Practices for Managing Contract Renewals and Automating User Input

Thijs

Hi Ironclad Community,

I hope you’re all well!

I’m currently working on optimizing our contract renewal process and would love to learn how others have structured their workflows to manage this efficiently. Specifically, I’m looking for best practices and advice on the following:

1.User Input for Renewals:

How do you handle cases where user input is needed to decide whether a contract should be renewed or not? Is there a way to automate reminders and prompts for users to confirm renewal decisions?

2.Automation vs. Manual Steps:

Are there any recommendations for reducing manual steps while ensuring that key stakeholders are notified and their input is captured?

3.Workflow Configuration:

If anyone has examples or tips on configuring workflows or repository reminders for renewals, I’d love to hear about your experiences!

I’ve already reviewed the articles on Enhanced Contract Reminders and Configure Repository Contract Reminders but would appreciate any insights on how you’ve tailored these features to your needs.

Thanks in advance

Thijs

Find more posts tagged with

Welcome!

It looks like you're new here. Sign in or register to participate in conversations. Don't forget to confirm your email address after registration!