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; } } }

Benefit of tracking Clauses in Repository?

Christine_List

All:

We are setting out our legacy import parameters and I keep coming back to the same question:

What am I really getting out of the manual effort to tag the existence of clauses (in both legacy and future contracts)?

I have designed our custom fields to track the substance of our material obligations/rights. So I will have visibility and reporting on the fact that our contracts contain relevant clauses that way. The story we want to tell comes from these custom fields.

Am I missing some benefit to tagging certain "AI detected" clauses? Because the manual effort of verifying/editing the auto detected fields is not small.

Thanks all!

Christine

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!