E · Contracts and audit
Analyze source changes and impact
Compare added, removed, and modified clauses across two change versions and trace impact to obligations, deadlines, amounts, and deliverables. Text differences and semantic impact remain separate states.
- Version
- 1.5.1
- Editions
- Standard · Pro
- Last verified build
1.5.1-private-commercial-r12
If the app is not installed, the link falls back to the safe download guide. It carries no file path, question, account, token, or evidence text.
WHEN TO USE IT
When this task is useful
Compare added, removed, and modified clauses across two change versions and trace impact to obligations, deadlines, amounts, and deliverables. Text differences and semantic impact remain separate states.
PREPARE
Check these items before you start
Select the previous and current change versions and their approval dates.
STEP BY STEP
Complete these steps in order
Select the previous and current change versions and their approval dates.
Run clause alignment and change-impact preview in Version compare.
Verify that prior/current clause text and every affected item are linked.
The change list and stale dependents appear, and related deliverables are not overwritten automatically.
FOR EXAMPLE
Installed synthetic contract Demo
These files and values are automatically verified against the synthetic Demo shipped with Orbivell; they are not personal or company data.
- Files
- Service_Agreement_v1.docx, Service_Agreement_Amendment_v2.pdf, SLA_Table.xlsx
- Question
- How did the amount and payment terms change from v1 to v2?
- Orbivell result
- Orbivell shows KRW 120,000,000 to KRW 132,000,000 and 30 to 45 days as changed claims linked to both source locations.
- User action
- Open both contracts, verify the changes, and approve the review result.
- Final result
- Only approved changes plus conflict and missing-evidence states enter the contract review and audit manifest.
CHECK THE RESULT
How to know the task is complete
- Verify that prior/current clause text and every affected item are linked.
- The change list and stale dependents appear, and related deliverables are not overwritten automatically.
EVIDENCE STATE AND NEXT ACTION
Read the state, then make the decision
Even a source-confirmed item should be adopted only after opening its source location. Partial, conflicting, missing, and review-needed items are never silently finalized; choose the appropriate next action: open the source, correct a value, add a source, or exclude the item.
LOCAL/EXTERNAL AI AND COST
Review transfer and cost before execution
Local only
Indexing, keyword search, opening sources, and reviewing existing results can run without external requests or external-processing credits.
When external processing is selected
Orbivell shows the external-processing service, excerpt scope, estimated credits, and maximum, and sends only after one-time approval. Actual usage is reconciled with a tamper-evident usage history.
LIMITS AND ERRORS
What Orbivell does not silently finalize
Documents with poor OCR or restructured clause numbering may require manual alignment review.
Error or state code: REVISION_ALIGNMENT_REVIEW
If the state repeats, follow the next action shown in Status. Do not alter the source or delete failure records; request support with a redacted diagnostics bundle.