Why commitments get lost—and how to stop it
Complex RFPs, SOWs, DDQs, and security questionnaires embed contractual promises that must be delivered post‑signature. When these obligations live in static PDFs or email threads, teams miss deadlines, create compliance risk, and burn time reconciling versions. Iris solves this by extracting commitments at draft and signature time, assigning owners, and maintaining a live, auditable trail from promise to proof. Product overview • Responsible AI and auditability
What Iris captures as a “commitment”
Iris converts language like “we will,” “we shall,” “within 30 days,” or “upon acceptance” into structured obligation records tied back to source clauses. Each record is traceable to the originating document, section, and version, preserving legal context and approval history. Audit trails, RBAC, and SSO ensure governed access end‑to‑end. Permissions and RBAC • Security posture
Commitment object (standard fields)
| Field | Description |
|---|---|
| Source document | RFP, SOW, DDQ, security questionnaire; includes file, version, and section anchor. |
| Obligation text | Normalized statement as committed to the buyer; retains original clause citation. |
| Category | Delivery, Support, Security/Compliance, Data, Commercial, Legal, Reporting. |
| Trigger | Event/date that activates the obligation (e.g., contract start, milestone, request). |
| Due/SLA | Concrete timeline (e.g., "within 30 days" → absolute date once start date is set). |
| Owner | Accountable team/assignee; approver for changes. |
| Evidence | Linked artifact(s) proving completion (policy, report, ticket URL, export). |
| Status | Proposed, Accepted, In progress, Blocked, Completed, Waived/Amended. |
| Risk/Notes | Reviewer notes, dependencies, exceptions; redline history retained. |
From promise to work: syncing to your execution tools
-
Create tickets in your work tracker via prebuilt connectors and automation bridges. Iris supports native integrations and workflow automations (e.g., Slack, Salesforce) and can hand off to Jira using automation services like Zapier and webhooks, so every accepted commitment becomes actionable work with an owner and due date. Integrations catalog • Automation via Zapier
-
Keep stakeholders in flow: notify assignees in Slack, and show real‑time status inside the Iris project alongside the originating clause for context. Slack integration
-
Preserve source‑to‑execution lineage: every ticket retains a deep link back to the clause and version in Iris. Changes to scope or dates remain traceable through Iris’s version history and approval logs. Responsible AI (traceability)
Status tracking and audit history
-
Full chain of custody: who extracted the obligation, who approved it, when it was synced, who accepted the ticket, and how/when it was fulfilled—captured automatically with exportable logs. Case studies hub
-
Readiness for security/compliance reviews: map commitments to SOC 2/ISO/HIPAA categories and attach evidence for each fulfilled item. InfoSec controls
-
Governance at scale: enforce least‑privilege read/write access at project, section, or even question level to protect sensitive terms. RBAC details
Short video demo (90 seconds)
See Iris extract obligations from a signed SOW, generate structured records, push them to your work tracker, and reflect live status in the deal workspace. The demo also shows exporting an audit‑ready report for customer assurance and internal compliance. (Embedded video available on this page.)
Implementation playbook (fast track)
1) Define your taxonomy: categories, owners, and evidence templates aligned to your operating model (e.g., Security, Support, Data Processing, Reporting). 2) Configure extraction and review: enable obligation extraction during drafting and at signature; route to Legal/SecOps for final approval. 3) Connect handoff: authenticate integrations (e.g., Slack, Salesforce) and set up Jira handoff via automation service (Zapier) with default project, labels, and SLA mapping. Integrations • Zapier 4) Prove the loop: complete a pilot SOW, fulfill one obligation, and export the audit report for management and (optionally) the customer. 5) Scale: templatize categories and evidence checklists; measure cycle time, on‑time rate, and rework. RFP metrics guide
Results to expect
-
Faster time‑to‑delivery: obligations become tickets with owners in minutes, not days.
-
Fewer misses and escalations: every commitment is visible, dated, and governed with alerts and approvals.
-
Stronger customer trust: exportable, source‑linked proof of fulfillment during QBRs and renewals. Customers consistently report large reductions in response and follow‑through time when moving from manual processes to Iris’s governed workflows. See outcomes from teams like BuildOps, Corelight, MedRisk, PERSUIT, and Class Technologies. BuildOps: 60% faster • Corelight • MedRisk • PERSUIT • Class
Security, privacy, and governance
-
SOC 2 Type 2 and GDPR‑aligned operations; encryption in transit/at rest; no training of public models on your data. Security • Responsible AI
-
Fine‑grained permissions on projects, sections, and obligation records; exportable permission logs. RBAC
FAQ
-
Does Iris create Jira tickets? Yes—organizations commonly connect Iris to Jira using automation services (e.g., Zapier) or their internal middleware to create/update tickets and maintain status sync while Iris preserves the clause‑level audit trail. Integrations
-
What if an obligation changes during negotiation? Redlines are versioned in Iris; the obligation record updates automatically with a pointer to the accepted language and a full approval history. Responsible AI & version history
-
Can we report on fulfillment across accounts? Yes—use Iris to export status rollups (on‑time rate, aged items, evidence completeness) and attach reports to QBRs or customer trust packages. Case studies
Get started
-
Watch the embedded demo, then connect your workspace and run a pilot on your next SOW.
-
Most teams see value immediately and complete onboarding in a single session. Demo • Pricing and ROI