Keeping contract statuses and dates accurate is what makes the rest of Aline work — clean expiration data powers your reports, your reminders, and your renewal planning.
This guide explains how Aline tracks document status, what the AI now sets for you automatically, how to capture and reconcile expiration and termination dates, and how to handle evergreen and auto-renewing agreements.
Overview
In this article you'll:
Understand the difference between Draft, Signed, Expired and Template documents
See what the AI sets for you on upload — status, type and parties
Turn on the signature scan for documents already in your repository
Capture expiration and termination dates as AI properties
Reconcile contracts that state more than one end date
Change status individually or in bulk
Label evergreen and auto-renewable agreements and give them a real date
Understanding Document Status
Every document in Aline sits in one of a few states, found under Documents > All:
Draft — an in-progress agreement that hasn't been executed
Signed — a finalized, executed contract
Expired — an agreement that is past its term and no longer active
Template — a document used to launch workflows rather than a contract in its own right
You can change a document's status from the editor, from a report, or in bulk from the repository.
Keeping these accurate matters for two reasons: it lets you filter reports down to contracts that are actually live, and it stops reminders from firing on agreements you no longer manage.
What the AI Sets for You
When a document lands in your repository, Aline reads it and fills in the basics itself — whether it is signed, the parties, and the contract type. These now appear in the documents grid straight away rather than after a delay.
All three are editable. If the AI gets a party or a type wrong, change it — and duplicate party records can be merged afterwards.
⚠️ Contract type and labels are not the same thing. The type is what the agreement is (MSA, NDA, Order Form) and the AI assigns it. Labels are yours, and they are what drive who can see a document. Aline deliberately has no folders — labels are the organising principle, so that every document has a single source of truth. See Organizing Documents with Labels & Bulk Labeling and Setting Permissions for Groups via Labels.
Signature Detection
Aline detects signatures on PDFs you upload and marks executed agreements as Signed automatically, showing where each signature sits in the document. For digitally signed PDFs it also reports whether the document was changed after it was signed.
Two things to know:
New uploads are handled automatically. Any file you bring in that was not sent out from Aline is checked on arrival.
Documents already in your repository are not — they need a one-off scan.
To scan your existing repository:
Click the organisation icon at the bottom left, then Settings.
Open Signature Detection.
Click Scan PDFs, then Start scan.
⚠️ The scan runs in the background and there is no progress indicator. While it is running, statuses across your repository are still settling — so if you are filtering by status during a scan, include both Draft and Signed rather than trusting either on its own.
📌 Signature detection is still in beta and is most reliable on single-signature documents. Spot-check a sample before you rely on it to clean up a large repository.
Step 1: Capture Expiration and Termination Dates
Use an AI report to extract the key dates from each contract as AI properties — typically Expiration Date, and where relevant Termination Date and Auto-Renewal Provision. Running these across a set of signed contracts gives you a single view of when everything ends.
💡 See Building AI Reports in Aline to set the report up. Everything a report extracts is saved back onto the document, so the dates are available outside the report too.
Step 2: Reconcile Conflicting Dates
Contracts don't always state a single clean end date. A document may list an expiration date in one clause and a termination or notice date in another. When these conflict:
Review both values side by side in the report
Decide which date governs for your purposes — usually the one that determines when you must act
Update or flag the contract so the governing date is the one your reminders read from
💡 Best Practice: For agreements where the two dates genuinely differ, keep both as separate columns so you can see the full picture, and point reminders at whichever date drives the action you need to take.
Step 3: Mark Contracts as Expired, Individually or in Bulk
When a contract has passed its term, mark it Expired so it drops out of your active views.
The fastest way to do a batch is from a report:
Open the report and click Filters → Add filter.
Filter on Expiration date is before today.
Select the results, then label them, change their status to Expired, or delete them — all across the whole selection at once.
From the repository, group or filter the list, tick the row checkboxes, and use the three-dot menu that appears at the bottom of the screen.
📌 Bulk status updates are especially useful when you're cleaning up a large repository after an initial upload. See Bulk Upload & Large-Repository Cleanup / Deduplication.
Step 4: Label Evergreen and Auto-Renewable Contracts
Evergreen contracts don't expire on a fixed date — they roll over automatically unless someone gives notice. A date property run against one comes back blank, which is why they need handling separately:
Run an AI prompt to identify agreements with auto-renewal or evergreen language
Apply a label such as Evergreen or Auto-Renewable so they're easy to filter
Capture a calculated next-expiration date (or notice deadline) as its own property, so you have a real date to remind against even though the contract technically never "expires"
Step 5: Handle Contracts With No Termination Date
Some agreements have no stated end date at all. Rather than leaving these blank — which makes them invisible to expiration reports — label them clearly (for example, No Fixed Term) so they're accounted for and reviewed on a schedule you set, instead of being silently ignored.
💡 Best Practices
Run the signature scan once, early, so your existing repository has accurate statuses before you build reports on it.
Don't trust status filters while a scan is running — include Draft and Signed until it settles.
Keep status current. Expired contracts left as Signed will skew every report and reminder you build.
Use labels, not types, to control access — the AI owns the type, you own the labels.
Keep both dates when they differ rather than overwriting one — then choose which one drives action.
Type your date properties as dates, not text, so you can sort, filter by range, and feed them into reminders.
Never leave an end date blank. Label it (No Fixed Term, Evergreen) so nothing goes missing.
Clean up status in bulk right after a migration, before you run large AI reports.
📚 Related Articles
❓ Need Help?
Cleaning up status and dates across a newly migrated repository? Click the Support button in Aline — we can help you build the reports that do the bulk updates in one pass.