Overview

Bulk-import legacy contract sets and preserve metadata for risk indexing.

Audience

• Lawyer
• Ops

Product Area

Contracts

Prerequisites

• Contract archive prepared

Steps

1. Upload contract batch

Use CSV manifest with counterparties, dates, and governing law fields.

1. Validate extraction

Review extracted clauses and resolve low-confidence fields.

Expected Result

The Contracts workflow completes without unresolved validation errors, and the result is visible to the intended roles.

Security and Audit Notes

• Use the least-privileged role that can complete the task.
• Confirm the resulting change or decision appears in the workspace audit trail when the workflow changes customer data or access.

Limits and Preconditions

• Available controls depend on the tenant plan, enabled modules, jurisdiction, and administrator policy.
• If a named control is not visible, confirm entitlement and role access before treating the behavior as a product failure.

Troubleshooting

• Missing contract metadata: Populate manifest with required fields before import.

Related Articles

• Troubleshoot Failed Import
• Review AI Citations

Escalation

If the documented result cannot be reached after the checks above, capture the workspace identifier, affected product area, timestamp, and a redacted error message, then use Support. Never include secrets, privileged legal content, or customer documents in the initial report.