Hi everyone,
We are looking for input from teams that create an MSA and multiple SOWs within a single workflow. Our workflow produces all documents during intake, and they are signed and stored together as a single repository record. We use lifecycle presets, but we are encountering a limitation related to tracking expirations and renewals when multiple documents with different timelines exist within a single record.
In our setup, the MSA is evergreen and the SOWs follow different term structures. Since lifecycle presets apply only one renewal type and one expiration date to a single repository record, we can track lifecycle information for only one document in the bundle. The remaining SOWs do not appear correctly in expiration views, renewal tracking, or reminder configurations.
Ironclad told us they are looking into improvements in this area. In the meantime, they recommended using the Related records feature. It'd require us to configure the workflows so the MSA and each SOW sit in separate records with their own lifecycle tracking, or to “unbundle” the signed PDF and manually import the individual documents into separate workflows. Both approaches would require us to change our current process, and it feels like it would reduce some of the efficiency gains we expect from using a CLM.
Our goal is to track expirations and renewals for all documents in the bundle, create views such as “Active contracts expiring in 90 days,” and send those reports to the team by email. Right now, only one document can drive that reporting, so we lose visibility into the rest.
Before we consider restructuring, we would really appreciate hearing from teams who:
- Generate multiple documents with different timelines in one workflow
- Have run into challenges tracking SOW expirations or renewals due to the lifecycle presets limitations
- Have tried using Related Records or separate workflows for MSAs and SOWs as a workaround
- Have moved away from bundled workflows specifically to improve lifecycle and renewal tracking
Any shared experience or insight would be invaluable as we assess our next steps.
Thank you all!
@Figueredo_Susana
