Information detected by AI on import
Issue date (effective date)
Section titled “Issue date (effective date)”Definition
Section titled “Definition”The issue date is the day the document was officially issued, sent, or made effective. For contracts, it often matches the effective or signature date. For emails, it is the sent date shown in the message.
How it is detected
Section titled “How it is detected”Contradic looks for explicit date labels in the document (for example “Effective date”, “Issued on”, or “Date signed”). If nothing is clear, it may fall back to the file’s last modified date or the upload date. When the AI is not confident, the field stays empty. You can always set or correct it in the document details panel.
Ambiguous cases (emails, drafts)
Section titled “Ambiguous cases (emails, drafts)”If an email contains a key attachment, the attachment’s date takes priority. Drafts often list multiple dates (creation, review, proposed start); in that case the AI may leave the issue date blank.
Best practices (checking key contracts)
Section titled “Best practices (checking key contracts)”Use the issue date to sort or filter in views, but verify it for high-impact documents such as master agreements or change orders. Check the signature block or the effective date clause and update the field if needed.
Sentiment (positive / neutral / negative)
Section titled “Sentiment (positive / neutral / negative)”What it actually measures
Section titled “What it actually measures”Sentiment reflects the overall tone of the document’s language: positive, neutral, or negative. Most legal and operational documents read as neutral even when they are important.
Use cases (identify tensions, disputes)
Section titled “Use cases (identify tensions, disputes)”Use sentiment to quickly spot documents that might signal tension (claims, disputes, or delays). In views, a cluster of negative sentiment can help you prioritize review.
Limits (neutral legal language)
Section titled “Limits (neutral legal language)”Legal language is often formal and balanced, which can hide sentiment signals. Treat sentiment as a hint, not a verdict, and adjust it manually when context says otherwise.
Difference between filename and detected title
Section titled “Difference between filename and detected title”The filename is the original file name you uploaded. The detected title is a clean, human-readable title suggested by AI from the document content. Use the title for display in lists and views, and edit it if it is too generic or too long.
Email / attachment cases
Section titled “Email / attachment cases”For email threads, the AI may use the email subject or the attachment title. If the attachment is the real document you care about, keep the title focused on that attachment.
Summary
Section titled “Summary”Automatic summary
Section titled “Automatic summary”The summary is a short AI-generated overview of the document’s key points. It is meant for quick scanning, not for legal interpretation.
When to rework it manually
Section titled “When to rework it manually”Edit the summary when it misses scope, key dates, parties, or obligations. Always refine it for high-risk or business-critical documents.
Use as a “summary note”
Section titled “Use as a “summary note””Treat the summary as a quick note for teammates. You can copy it into your own notes or share it in a view to speed up review.
Document type
Section titled “Document type”Link to the full classification page
Section titled “Link to the full classification page”See the full list of categories and how they are defined.
Open automatic document classificationKey role in filters / views / claims
Section titled “Key role in filters / views / claims”Document type is one of the main ways to filter and organize your workspace. It powers filters in views and can narrow down which documents are relevant to claims or investigations. If the type is off, update it in the document details so your views stay accurate.