Inbox-buried contracts missed notice windows; ServiceNow IT Asset Management ingested terms and sent reminders

Overview

A construction firm stored vendor contracts in inboxes and shared drives, so renewals surprised owners, notice periods were missed, and legal terms were hard to find during negotiations. Intelligex implemented a document intake workflow that ingests contracts from email and file shares, extracts renewal dates and key terms, and records them in the firm’s IT Asset Management (ITAM) and contract modules. Owners received reminders ahead of renewal windows, legal review was required for sensitive or unusual terms, and a centralized view replaced email searches. Surprise lapses diminished, negotiations started earlier, and evidence lived in one place—while the firm’s ITAM, ERP, and collaboration tools remained in place.

Client Profile

• Industry: Construction and engineering services
• Company size (range): Corporate headquarters with regional offices and active project sites
• Stage: Contracts scattered across inboxes and drives; asset and spend data lived in ITAM and ERP; renewals tracked in spreadsheets; legal reviews requested by email
• Department owner: IT & Infrastructure (IT Asset Management and Procurement)
• Other stakeholders: Legal, Security, Finance/ERP, Project Management, Vendor Management, Internal Audit, Business Unit Leads

The Challenge

Vendor agreements arrived by email and were saved wherever convenient. Renewal dates, notice periods, and auto?renew clauses were buried in PDF pages. Project teams forwarded quotes and signed copies to IT or Procurement but kept their own versions. When a renewal approached, owners combed through inboxes and shared folders to find the latest terms. If a notice period was missed, the firm accepted an unplanned renewal or rushed to negotiate without leverage.

Visibility was fragmented. ITAM held entitlements and costs, ERP held vendor and payment data, and Legal tracked redlines in document libraries. There was no system of record tying a contract to an asset, owner, renewal window, and required reviews. Reminders were handcrafted in calendars. Audit requests for who approved a term or whether a legal review occurred required assembling threads and attachments from multiple places.

Why It Was Happening

There was no intake process that turned documents into structured records. Teams forwarded contracts to functional mailboxes or colleagues, and each group filed documents differently. Required metadata—owner, cost center, renewal date, notice period—was not captured or validated. Legal reviewed terms when asked, but approvals were not bound to specific clauses or to the contract record in ITAM. Without automation and governance, the firm operated on best effort rather than on a predictable lifecycle.

Ownership and timing were split. Project managers initiated agreements, Procurement negotiated, Legal reviewed, Finance processed invoices, and ITAM tracked assets. Without a shared workflow that captured terms, dates, and approvals and connected them to assets and owners, deadlines slipped and decisions relied on incomplete context.

The Solution

Intelligex built a contract intake and governance workflow around the firm’s existing ITAM and contract tools. Incoming documents from email and shared drives were ingested, parsed for key fields, and created as contract records linked to assets, vendors, and owners. Extracted terms included renewal date, notice period, auto?renew, governing law, and data or security clauses. A human?in?the?loop review validated fields, and required legal approvals were enforced for sensitive terms. Renewal reminders and negotiation tasks were generated automatically. The design used the firm’s contract and ITAM platform (for example, ServiceNow Docs) and a document extraction service such as AWS Textract for OCR and key?value extraction.

• Integrations: Dedicated intake mailbox and shared drive watchers; OCR and key?value extraction service; ITAM and Contract Management for records; ERP for vendor and cost centers; Identity for owner lookup; ITSM for tasking and approvals; SIEM for audit logs.
• Data model and mapping: Vendor, contract type, linked assets, owner, sponsor, cost center, start/end and renewal, notice period, auto?renew flag, negotiated terms, and attachment links; mapping to existing ITAM and ERP identifiers.
• Extraction and validation: Templates and pattern libraries to detect dates and clauses; confidence scoring; human review queue for ambiguous fields; normalization of dates and clause variants; currency and term alignment to corporate standards.
• Workflows and gates: Required legal review for privacy, data handling, and liability terms; Procurement sign?off on pricing and renewals; maker?checker approvals for exceptions; time?bound holds for contracts under negotiation.
• Renewal and negotiation: Reminders to owners and Procurement before notice windows; options to renew, renegotiate, or terminate with reason codes; tasks to collect usage and cost data for negotiation prep; automatic linkage to related assets and incidents.
• Dashboards and evidence: Upcoming renewals by vendor and owner, notice deadlines at risk, exception aging, contracts without linked assets, and legal review status; exportable packets with terms, approvals, and attachments.
• Security and privacy: Role?based access; redaction rules for sensitive clauses; immutable logs of intake, edits, and approvals; retention aligned to policy.

Implementation

• Discovery: Cataloged contract sources and types; sampled clauses and date formats; mapped current ITAM, ERP, and Legal repositories; reviewed approval paths and exception categories; gathered audit and retention requirements.
• Design: Defined the contract data model and required fields; authored extraction templates for common vendors and terms; set confidence thresholds and review queues; defined legal and procurement approval gates; planned renewal cadence, tasks, and notifications; designed dashboards and evidence exports.
• Build: Configured intake mailbox and drive watchers; implemented OCR and key?value extraction; built normalization, validation, and human?in?the?loop review; created record creation and linking in ITAM and Contract Management; wired legal and procurement approvals; enabled renewal reminders and negotiation tasks; forwarded logs to the SIEM.
• Testing/QA: Ran the pipeline in shadow mode to create draft records without notifications; validated extraction accuracy and mappings; refined templates for clause variations; piloted legal and procurement reviews on a subset; verified reminder timing and owner routing.
• Rollout: Enabled intake for new contracts first; backfilled high?value vendors by dragging historical documents through the same flow; turned on reminders and negotiation tasks; retained manual tracking as a controlled fallback during early cycles; expanded coverage to regional mailboxes and shared drives.
• Training/hand?off: Delivered sessions for Project Managers, Procurement, Legal, and ITAM on intake submission, reviews, and renewal actions; published intake guidelines and clause glossaries; updated SOPs for contract creation, extension, and termination; transferred ownership of templates, approval matrices, and dashboards to ITAM and Legal under change control.
• Human?in?the?loop review: Established recurring reviews of low?confidence extractions, exception aging, and renewal outcomes; decisions recorded with rationale and effective dates; updates flowed into extraction templates and approval policies.

Results

Renewal risk moved from inboxes to a governed calendar. Owners and Procurement received timely reminders with the terms and notice windows already parsed, so decisions to renew, renegotiate, or terminate happened on schedule with full context. Legal sign?off was recorded against the specific contract version and terms, and unusual clauses triggered review automatically rather than relying on memory.

Visibility improved across functions. ITAM records linked assets to contracts with owners, costs, and renewal posture, ERP context appeared alongside vendor and payment details, and dashboards highlighted what needed attention next. Audit evidence came from the same system that drove action, including intake logs, extracted terms, approvals, and attachments. Email and drives remained; the change was a structured intake and governance layer that made contracts actionable.

What Changed for the Team

• Before: Contracts lived in inboxes and shared folders. After: Intake captured documents and created structured records linked to assets and owners.
• Before: Renewal dates and notice periods were tracked in calendars and spreadsheets. After: Reminders and negotiation tasks flowed from contract records with validated terms.
• Before: Legal reviews were ad hoc. After: Required approvals were enforced for sensitive clauses with evidence attached.
• Before: Negotiations started with incomplete context. After: Terms, usage, and cost appeared together to support strategy.
• Before: Audits stitched together emails and attachments. After: Exportable packets tied terms, approvals, and versions to each contract.
• Before: Orphaned assets and contracts drifted. After: Dashboards flagged missing links and exceptions for cleanup.

Key Takeaways

• Start at intake; turn documents from email and drives into structured records with owners and dates.
• Extract what matters; normalize renewal, notice, and auto?renew terms and attach them to assets and vendors.
• Keep humans in the loop; confidence thresholds and legal gates ensure quality without slowing the flow.
• Make renewals proactive; reminders and negotiation tasks reduce surprise lapses and rushed decisions.
• Link systems, not screenshots; connect ITAM, ERP, and approvals so evidence and action live together.
• Integrate, don’t replace; keep existing tools—add extraction, workflow, and dashboards on top.

FAQ

What tools did this integrate with? Contracts were recorded in the client’s ITAM and contract platform (for example, ServiceNow Docs) and linked to assets and vendors. Intake used a dedicated mailbox and shared drive watchers, with OCR and key?value extraction provided by services like AWS Textract. Approvals ran through existing ITSM workflows, owner lookups came from the identity system, and ERP supplied vendor and cost center context.

How did you handle quality control and governance? Extraction used templates and pattern libraries with confidence scoring. Low?confidence fields entered a human review queue. Legal approvals were required for specific clause categories and any exceptions, with maker?checker for high?risk terms. Every intake, edit, and approval was logged immutably, and dashboards tracked exception aging and review status.

How did you roll this out without disruption? The pipeline ran in shadow mode to create draft records and test reminders. New contracts flowed through intake first, while historical documents were backfilled in waves. Manual spreadsheets remained a controlled fallback during early cycles. As accuracy and adoption grew, reminders and negotiation tasks replaced ad hoc calendar entries.

How were contracts ingested from email and drives? A dedicated mailbox accepted forwarded contracts and vendor updates; shared drive watchers detected new or updated files in targeted folders. Intake created a draft record with attachments, ran extraction, and queued low?confidence fields for review. Duplicates were detected by vendor, term, and checksum to avoid multiple records for the same document.

How did you protect sensitive information? Role?based access limited who could view contracts and extracted terms. Redaction rules masked sensitive fields in views and exports. Legal and Security had full visibility during review, while broader audiences saw only what was needed for renewal actions and asset linking. Logs avoided body text and captured metadata and actions instead.

How did you handle auto?renew and notice periods? Auto?renew flags and notice terms were extracted and normalized. Renewal tasks and reminders reflected the earliest notice window, with options to renew, renegotiate, or terminate. Exceptions required approvals, and holds paused reminders during active negotiations.

What about contracts that cover multiple assets or projects? The data model linked a contract to multiple assets, projects, or cost centers. Dashboards showed allocation by owner and project, and renewal actions considered linked usage to avoid orphaning active services.