nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Sending Cover Sheet with Draft, but Not with Signature Packet

zuhair_saadat

Hi all, we have a request/requirement to include a cover sheet to go out with our draft MSAs. However, we wouldn't want this cover sheet to be included in the signature packet once the draft has been finalized.

What are some solutions/workarounds for this? The only one I can think of is to remember to manually remove the auto-generated cover sheet from the Ironclad Workflow before approving for signature.

Thanks all, looking forward to hearing your thoughts.

Find more posts tagged with

Status: None

Comments

Erin_Till

Hi, @zuhair_saadat! If the cover sheet doesn't necessarily need to be a document itself, you could possibly update the email template for sharing documents to include the relevant information. A caveat, though: this template would apply every time you email any document from within the workflow (even when it is not an MSA), so users may need to modify it when it's not applicable.

Tuffer_Harris

I think there are a few related threads on this and similar topics, so it sounds like an important feature (I know its one of our top would-like-have items). We also have a cover sheet we don't want to include in signing. In addition, we have PDF handbooks and guides that the contract references and we'd like distributed with the initial MSA request but not in the signature packet. There are some recent threads on related "multi-document" issues like removing certain documents manually vs. automatically. It seems like an overall theme is users would like more sophisticated handling of multiple documents in a workflow, including automation and rules, as well as manual controls.

I think this reflects a move I would like to see structurally that workflows and templates should be separate concepts. A workflow could include a template, but it could also not include a template for tracking questions, or it could include multiple templates. Then you could also have the same template included in different workflows. https://community.ironcladapp.com/t5/Ironclad-Idea-Exchange/De-coupling-Templates-and-Workflows/idi-p/5958

Related threads about multi-document handling:

https://community.ironcladapp.com/t5/Ironclad-Users-Forum/Information-document-in-Workflow-not-to-be-signed/td-p/5672 (this is basically the same request as this thread)

https://community.ironcladapp.com/t5/Ironclad-Idea-Exchange/OPTION-to-combine-multiple-documents-from-a-workflow-or-leave/idi-p/6770

https://community.ironcladapp.com/t5/Ironclad-Idea-Exchange/Removing-Main-Draft-Document-from-Workflow/idi-p/3162

https://community.ironcladapp.com/t5/Ironclad-Idea-Exchange/Multiple-Record-Types-in-a-Single-Workflow/idi-p/4652

Geneva_Yourse

I would love this functionality. I currently replace the docs with blank ones so that it is not part of the signature packet.

Geneva_Yourse

Still waiting on this one!! Just putting it back up on the list because it came up again!

As a FYI, I am currently replacing the doc with a blank doc so that when it goes to the signature packet there is nothing there. This is a serious pain - especially when I forget!

Erin_Till

Thank you for the nudge @Geneva_Yourse! We appreciate your feedback. I am going to move this post over to the Idea Exchange to ensure we have the right teams tracking it.

Geneva_Yourse

Thank you! It would greatly help many Ironclad users!