Contents 🚀
Introduction 👋
The new document workflows you will use as a Juro customer will, by default, create a data-rich repository of documents. However, for your legacy pre-Juro documents, you might not have as rich or easily accessible data.
Through tagging, you can structure the data associated with your legacy documents so your Juro repository becomes a valuable source of truth for new and old documents alike.
|
Defining your data points 🧂
Whilst every organisation we work with has unique priorities, here are some data points that we commonly see customers looking to extract from their documents either via the AI-powered tagging service Juro offers or via other means:
Data Type | Notes |
Document Type | Document classified as one of a pre-set list of document classifications.
e.g. "Vendor, Commercial, Employment" or "MSA, NDA, Offer Letter, DPA" |
Effective Date | The date that the contract begins/comes into effect. |
Renewal Date | The date that the contract renews (not always applicable). |
Opt-Out Date | The date by which either party can opt out before the contract automatically renews for a second term. [A key field to set reminders for]. |
End Date (or end of first/initial term) | The date that the contract will come to an end. |
Term (or initial term) | The length of the agreement. |
Contract Value | The total value of the contract or annualised contract value. |
Product/Service Details | An overview of specific details relating to the product or service provided by one party to another. This may vary depending on the type of document. |
Renewal | Details relating to whether or not a contract renews. e.g. "Auto-renewal". |
Contract Currency | Currency that the fees etc. should be paid in. |
Specific Clauses | Y/N or TRUE/FALSE answers to whether specific clauses or sections are present in a document. e.g. "Is there a confidentiality clause?" N.B. You will need a data point for each specific clause you're looking to track. A general 'Specific Clauses' field is typically not a helpful approach. |
Termination | Overview of how the contract can be terminated. e.g. "termination for convenience", "termination at any point with X days' notice". |
Payment Frequency | e.g. "annual" or "monthly". |
Billing Terms | Days within which a fee must be paid. e.g. "30". |
Paper | Whose paper the document is on? e.g. "own paper", "third-party paper". |
Counterparty Name | The full legal name of the counterparty. |
Counterparty Address | Full registered address of the counterparty. |
Notices Email | Email address to which notices under the contract should be sent. |
When scoping a tagging project, it's helpful to clarify if data exists in a structured format elsewhere in your organisation. Data which has already been structured and stored elsewhere might be importable when you import your legacy documents. Juro needs this data to be in a certain format. You can read more about importing data here.
⚠️ When setting up data points in Juro you'll be using our smartfields functionality. It is best practice to keep smartfields named consistently between templates. This will help you get maximum value from your contract reports.
💁♀️ As always, our Support Team is happy to help you with anything further if needed. Start a chat with us right here by clicking the Intercom button in the bottom-right-hand corner of this page.
Alternatively, you can email your query to support@juro.com 🚀
|