February 03, 2026, 09:00 AM
vthokyAdobe Acrobat users -- I need some e-signature help, please.
In the quest to get away from pushing so much paper, we're using Acrobat to deliver documents for signature. Using the built-in E-Sign function has turned out to be pretty easy, once we stumbled through it a couple of times.
Documents I prepare typically go to two or three people, so it's no big deal to add three people to the list when preparing a document. What we've run into this morning is a different situation: engineering change requests (ECR) and engineering change orders (ECO) typically require about ten different people to review and sign. Adding ten people to the list once is one thing, but this will be a repetitive thing (nothing is constant but change, right?).
What we're wondering is if there's a way to set up a
group in Acrobat -- that list of ten people who will be asked for signatures routinely -- and then be able to add that group instead of adding the ten people individually every time we create an ECO or ECR.
I've been beating on Adobe's site this morning trying to find the answer, but so far I'm about as successful as I am when I'm fishing. (If I had to rely solely on my fishing for my eating, I'd starve.)
Adobe gurus, chime in! Thank you.
- - - - -
ETA: for what it's worth. the Acrobat version I'm using is 2025.001.21111.
February 03, 2026, 09:17 AM
sig2392This may be what you are looking for.
https://helpx.adobe.com/sign/u...0workflow%20designer.
February 03, 2026, 10:13 AM
HRKquote:
Originally posted by vthoky:
I've been beating on Adobe's site this morning trying to find the answer, but so far I'm about as successful as I am when I'm fishing. (If I had to rely solely on my fishing for my eating, I'd starve.)
Adobe gurus, chime in! Thank you.
- - - - -
ETA: for what it's worth. the Acrobat version I'm using is 2025.001.21111.
Rebuilding a form now, not using e-signatures yet as most of the companies I deal with don't accept it.
Why not build an e-signatures document with the 10 signature fields, and anytime you need it just attach it to the original document as needed.
I agree, looking for help on the Adobe site is absolutely frustrating just trying to figure out how to frame the query in a manner like Adobe has it framed, it's almost like they do it on purpose to make it difficult.
February 03, 2026, 10:47 AM
SpinZoneWe use this extensively for approvals for documents in the validation process. Our document revisions and our change control are handled by dedicated software that manages the e-sigs.
I don’t know of a way to create a signature group that you can save, It may be an option but it is not something we would have used so I never looked at it. I have created documents with 20+ signers but due to the company’s size and structure, some of the signers would always be different from doc to doc.
HRK, due to .gov rules we fell under, a separate signature page wouldn’t have worked for us. The approvals had to be part of the original document.
Maybe a separate signature page could be merged with the ECR to create a new document or, if the ECRs are individually written as needed, create a template document with the signatures already configured and use the template when you start a new ECR.
February 03, 2026, 11:27 AM
vthokyThank you for the link, sig2392. That potential solution works with a different Adobe product, called Sign. I have a conference call set up for tomorrow afternoon with an Adobe rep to discuss the product. I did learn this morning that it's "transaction-based." What I think that means is that you pay by the document. I'm looking forward to learning more about that tomorrow.
HRK's separate signature page might be a partial solution, but as SpinZone mentions, the approvals have to be part of the original document. Merging a signature page could be done; it'll involve rebuilding the ECO and ECR forms. (Certainly doable.)
When I chatted with the Adobe rep earlier, there was a question about whether we deal with compliance issues, such as HIPAA and CFR Pt 11. We don't at the moment, but there are potential projects in the pipe that could require it. I'll learn more about that question and its implications tomorrow as well.
And yes, Adobe's site is
very frustrating.