Your Contract Management Data Template

The Contract ID serves as the definitive case identifier, uniquely linking all events and activities related to a specific contract. This allows for a comprehensive, end-to-end analysis of each contract's journey, from its inception to its resolution.

In process mining, this attribute is fundamental for reconstructing the lifecycle of every contract. It ensures that all related activities, such as drafting, reviews, approvals, and execution, are correctly associated with the appropriate contract, enabling accurate measurement of cycle times and identification of process variations.

This is the primary key for process analysis, enabling the tracking of a contract's complete journey and ensuring data integrity.

This is a core attribute of the Contract Agreement object in Icertis.

The Activity Name describes a specific step or milestone in the contract management process. These events are ordered by their timestamps to build the process flow for each contract.

Analysis of this attribute reveals the sequence of operations, frequency of different activities, and the overall structure of the process. It is used to identify common process paths, deviations from the standard procedure, and activities that cause rework or delays, such as multiple revision cycles.

It defines the steps of the process, which is essential for visualizing the process map, analyzing process flow, and identifying bottlenecks.

This information is typically generated from event logs or workflow history tables within Icertis, which track the status changes and tasks performed on a contract.

This attribute records the precise date and time that an activity was started or completed. It is the temporal foundation for process mining, providing the chronological order of events for each contract case.

The Event Time is crucial for all time-based analysis. It is used to calculate cycle times between activities, identify waiting periods, measure the duration of specific phases like negotiation or approval, and pinpoint bottlenecks where contracts stall for extended periods.

This timestamp is critical for calculating all performance metrics, such as cycle times and durations, and for understanding the sequence of events.

This is a standard field in Icertis audit trail or workflow history logs, associated with every recorded event.

This attribute identifies the individual, team, or automated user who performed a given activity. It can be a specific user name, an employee ID, or a system account.

Analyzing the Activity Owner is crucial for understanding resource allocation, workload distribution, and performance. It helps answer questions like which users or teams are bottlenecks, who are the most efficient reviewers, and how work is distributed. This directly supports the 'Reviewer Workload Distribution' dashboard.

It allows for performance analysis by user or team, helping to identify workload imbalances and training opportunities.

This information is usually available in the workflow history or audit trail data within Icertis, linked to each event.

This attribute indicates the overall status of the contract case, for example 'Draft', 'In Review', 'Awaiting Signature', or 'Executed'. This is typically a case-level attribute that reflects the last major milestone reached.

It is vital for operational dashboards like 'Contract Status And Throughput', which provide a real-time snapshot of the contract pipeline. It helps managers understand the volume of contracts in each stage and identify where work is piling up, enabling proactive management of the contract portfolio.

Provides a high-level view of the contract pipeline, essential for operational monitoring and managing throughput.

This is a primary status field on the Contract Agreement object in Icertis.

The Contract Type categorizes agreements based on their legal or business purpose. This is a fundamental attribute for segmenting and comparing contract lifecycles.

Different contract types often follow distinct process paths and have different complexity levels and SLAs. Analyzing the process by Contract Type allows for targeted improvements, such as creating optimized workflows for high-volume, low-risk agreements like NDAs versus complex, high-value MSAs. It is essential for the 'Contract Variant Analysis' and 'Policy Compliance Score' KPIs.

Allows for process segmentation to compare lifecycles and compliance across different kinds of agreements.

This is a standard attribute configured on the Contract Agreement object in Icertis.

This attribute represents the financial worth of the contract, such as the total contract amount or annualized value. It is a critical business metric for prioritizing contracts and understanding financial impact.

In process mining, Contract Value is used to segment analysis and focus on high-value agreements. For instance, one can analyze if high-value contracts take longer to approve or negotiate. It also helps in risk assessment, as delays in high-value contracts can have significant revenue implications.

Enables prioritization and value-based analysis, helping to focus improvement efforts on the most financially significant contracts.

This is typically a standard currency field on the Contract Agreement object in Icertis.

This attribute captures the completion time of an activity. While StartTime marks the beginning, EndTime marks the conclusion, defining the activity's discrete timespan.

Having both a start and end time is essential for accurately calculating the processing time or duration of each individual activity. This enables analysis of which steps consume the most time, distinguishing between active processing time and idle waiting time between steps. It is key for dashboards like 'Approval Process Bottlenecks' and 'Drafting And Revision Efficiency'.

Enables the precise calculation of activity durations, helping to differentiate between processing time and waiting time.

Similar to StartTime, this is found in Icertis audit trail or workflow history logs. Some events may be instantaneous, where StartTime equals EndTime.

This attribute specifies the business department, such as Legal, Sales, or Procurement, associated with the user who performed the activity. It provides an aggregated view of resource involvement in the process.

Analyzing by department is key to understanding inter-departmental collaboration and handoffs. It helps identify systemic delays between departments, such as long waits for legal review after a sales submission, which is the focus of the 'Departmental Handoff Delays' dashboard.

Facilitates analysis of departmental performance and handoff efficiency, highlighting cross-functional bottlenecks.

This data may need to be enriched by joining with an HR system or user directory, using the Activity Owner as the key. It may also be stored directly in Icertis user profiles.

This attribute identifies the internal division or business unit that owns or requested the contract, such as 'Enterprise Sales North America' or 'Global Procurement'.

Similar to Department, this allows for a higher-level aggregation of the process data. It helps in comparing process efficiency and compliance across different parts of the organization, providing valuable insights for senior management and supporting strategic resource allocation decisions.

Enables high-level process performance comparison across different organizational units.

This is often a key metadata field on the contract agreement, linking it to the organizational structure.

This attribute identifies the other party involved in the agreement. It provides essential context for analyzing interactions and negotiations.

Analyzing the process by counterparty can reveal patterns in negotiation cycles. For example, it can show if contracts with certain vendors consistently take longer to negotiate or require more revisions. This insight is valuable for strategic relationship management and for tailoring negotiation strategies, directly supporting the 'Negotiation Cycle Time And Rework' dashboard.

Allows for analysis of negotiation patterns and relationship performance with specific external parties.

This information is stored as part of the contract's metadata, typically linking to a counterparty or vendor master data object in Icertis.

This attribute tracks the iteration of the contract document as it goes through drafting, redlining, and revisions. It is typically an integer or a major.minor version number.

Document Version is a direct indicator of rework. A high number of versions for a contract suggests multiple rounds of changes, which can be investigated to understand the root causes. It is a key input for calculating the 'Contract Revision Rate' KPI and for the 'Drafting And Revision Efficiency' dashboard.

Directly measures the amount of rework and revision a contract undergoes, highlighting inefficiencies in drafting and negotiation.

Icertis maintains version history for all contract documents. This attribute can be extracted from the document's metadata or event log.

This attribute stores the end date of the contract term. It is a critical date for managing the contract's lifecycle post-execution, triggering renewal or termination activities.

This date is essential for monitoring the effectiveness of end-of-life management. It serves as the baseline for the 'On-Time Renewal/Termination Rate' KPI, which measures whether renewal or termination processes are initiated and completed in a timely manner, avoiding unwanted auto-renewals or lapses in service.

Crucial for managing contract renewals and terminations, ensuring that end-of-life processes are handled proactively.

This is a standard date field on the Contract Agreement object in Icertis.

This boolean attribute signifies whether the contract originated from a pre-approved, standard template or was created as a non-standard, bespoke agreement. This is a key factor in assessing risk and compliance.

Contracts based on standard templates typically have faster cycle times and lower risk. This attribute is the basis for the 'Contract Template Adherence Rate' KPI and helps in analyzing the process impact of using non-standard paper. It can highlight departments or contract types that frequently deviate from standards, guiding efforts to improve template usage.

Measures adherence to company standards, which directly correlates with process efficiency and risk reduction.

This could be a checkbox field on the contract or derived based on the document's origin or metadata within Icertis.

This attribute indicates the freshness of the data being analyzed. It records the date and time of the last data extraction from the source system.

This information is crucial for users to understand the timeliness of the insights presented in the dashboards. It helps them know if they are looking at real-time information or data that is a few hours or days old, setting the right context for decision-making.

Provides context on data freshness, ensuring users understand how current the process analysis is.

This timestamp is generated by the data pipeline or ETL tool at the end of each successful data refresh cycle.

This attribute tracks the due dates for key obligations, commitments, and deliverables defined within the contract after it has been executed. A single contract may have multiple obligations, each with its own due date.

Tracking these dates is critical for post-execution compliance and risk management. This attribute is the foundation for the 'Obligation Adherence Rate' KPI, allowing the organization to monitor whether it is meeting its commitments on time and to proactively address potential breaches.

Enables monitoring of post-execution compliance, which is crucial for avoiding penalties and maintaining good business relationships.

Icertis has modules for obligation management. This data would come from the obligations associated with a contract.

Processing Time is the calculated duration from an activity's start time to its end time. It represents the actual time resources were engaged with a task, as opposed to the waiting time between tasks.

This metric is fundamental for performance analysis. It helps pinpoint which specific activities are the most time-consuming in the entire process. For example, it can show that while the overall legal review phase is long, the actual time spent reviewing documents is short, indicating that most of the time is spent in a queue. This is vital for almost all dashboards, especially those focused on cycle time and efficiency.

Separates active work time from idle wait time, providing a more accurate target for efficiency improvements.

This is calculated from the 'EventTime' (StartTime) and 'EndTime' attributes in the dataset.

This attribute specifies the geographic area, such as EMEA, APAC, or North America, to which the contract applies. This is important for global organizations with regional variations in their processes.

Analyzing by region can uncover differences in process performance, compliance requirements, or negotiation tactics driven by local laws and business cultures. It allows for region-specific benchmarking and the identification of best practices that could be shared globally.

Helps identify regional variations in process performance and compliance, which is crucial for global organizations.

This is typically a metadata field on the contract object in Icertis, often part of the standard configuration.

This calculated metric provides a count of revision-related activities, such as 'Contract Redlined Or Revised', for each contract case. It serves as a simple, powerful indicator of process friction.

A high revision count signals potential issues in the drafting or negotiation phases, such as unclear requirements, poor initial drafts, or difficult negotiations. This metric is the direct input for the 'Contract Revision Rate' KPI and is used in dashboards to identify contracts and process variants with excessive rework.

Quantifies rework in the contract lifecycle, directly measuring the efficiency of the drafting and negotiation stages.

This is calculated by counting the occurrences of specific revision activities for each 'ContractId' in the event log.

This attribute is derived by comparing the duration of certain process phases against predefined SLA targets. For example, it might flag a legal review as 'Late' if it exceeds the standard 48-hour turnaround time.

SLA Status is essential for compliance monitoring and performance management. It allows for the creation of alerts and dashboards, like the 'Contract Compliance Overview', that immediately highlight breaches. This helps teams prioritize overdue tasks and enables managers to track performance against key targets.

Provides immediate visibility into compliance with service level targets, helping to prioritize work and manage performance.

This is calculated by defining business rules in the process mining tool that compare timestamps against predefined SLA thresholds (e.g., Legal Review duration > 2 days).

This attribute identifies the origin of the data, which is 'Icertis' for this process. It helps in data governance and traceability, especially in environments where data might be aggregated from multiple systems.

In analysis, it can be used to filter data to a specific source system or to compare processes across different systems if applicable. For this view, it serves as a constant identifier for all events.

Ensures data lineage and traceability, which is important for data validation and managing data from multiple sources.

This is typically a static value added during the data extraction and transformation process to label the origin of the data.