Hello Ironclad Community,
We’ve reviewed the November 2025 update that introduces the ability to update parent contract terms directly from amendments. While this feature is promising, we’ve encountered several limitations in our workflow setup that prevent us from benefiting fully:
- Existing Amendment Workflows Already Linked: Our amendment workflow is already configured to link amendments to their parent agreements. However, the new feature does not apply to amendments that are already linked through a workflow, meaning we cannot leverage the automatic property roll-up as intended.
- Manual Linking Required for New Functionality: The update appears to require manual linking of amendments to parent records to trigger the new update options. This is not practical for teams with automated or integrated amendment processes.
- No Option to Reassign or Update Properties Post-Execution: Once an amendment is executed and linked via workflow, there is no way to reassign or update the parent record properties automatically. This limits the usefulness of the feature for organizations with established amendment workflows.
- Testing Alternative Linking Methods Is Inefficient: Changing our workflow to use a different type of record relationship (e.g., from parent to related record) would require significant reconfiguration and manual intervention, reducing efficiency and increasing the risk of errors.
- Current Workarounds Are More Efficient: We are currently working on a process to validate and update contract end dates and amounts by comparing Ironclad data with our ERP, then using metadata imports for updates.
Request for Improvement:
We recommend that Ironclad enhance this feature to support amendment workflows that already link to parent agreements, enabling automatic property updates without manual intervention. This would better serve organizations with integrated contract management processes.
Has anyone else encountered similar challenges? Would appreciate any insights or workarounds from the community.
Thank you!
