E-Signature Expand Default Contact Options

[relleumk]

@ian_turner

I talked with you about this at AU 2025. Would like to see the default list of e-signers for subcontracts (suppliers) expanded to included all the "additional contacts" from the supplier details section: 

Also, we would like "Additional contacts" concept added to the Company Setup Section in Cost Management Settings for at least the Owner, Contractor, and Architect Sections. Then apply these to the default list for e-signers.

We often have several people who need to initial and/or sign documents at different times and adding person or role doesn't always work.

[ian_turner]

Hi Kevin

Please can you provide a list of the contact roles you would like to see for Owner, Contractor, and Architect Sections?

Thanks

[relleumk]

@ian_turner,

I think the below list should be a good start, but I would do some more research.

Owner Signatory - Person who might need to only execute the original contract documents

Owner Main Contact – Person who would be signing CORs / OCOs for remainder of project

Owner Pay App Contact – Person who might be reviewing Pay App submissions

Contractor Signatory - Person who might need to only execute the original contract documents

Contractor Main Contact 1, 2, 3,etc.  – Person(s) who would be signing or initialing SCOs, CORs, OCOs for remainder of project. Multiple might be nice since some large projects have different PMs for different scopes

Contractor Pay App Contact – Person who might be reviewing Pay App submissions

Architect Signatory - Person who might need to only execute the original contract documents

Architect Main Contact – Person who would be signing CORs / OCOs for remainder of project

Architect Pay App Contact – Person who might be reviewing Pay App submissions

[prem_agrawal]

Hi Kevin,

Could you please clarify this point from your note:

“Contractor Main Contact 1, 2, 3, etc. – Person(s) who would be signing or initialing SCOs, CORs, OCOs for the remainder of the project. Multiple might be nice since some large projects have different PMs for different scopes.”

I wanted to confirm whether the intent here is that only one person from the group (Main Contact 1, 2, 3, etc.) needs to sign for the process to be completed, or if all listed contacts would be required to sign before it’s considered complete.

[relleumk]

@prem_agrawal

Depending on the item, one or all persons must sign for the item to be considered complete. For example we might have Owner, Project Manager, Project Assistant who all need to sign Contracts, but then one PM and/or might only be required for SCOs and CORs for the structural trades but then we might have a second PM who needs to sign the TI trades. 

[ian_turner]

Hi Kevin

Having main contact 1,2,3 etc doesn’t really work. You could use project specific roles for that purpose.

We have a similar concept for RFQ recipients where you can assign multiple but it means they will all be notified if you send an RFQ out, but only the first will be used for e-signature.

We’re good with the concept of adding more contacts for the GC/Owner/Arch but if they are hard coded I think we need clear defined contact types for e-signature so they mean the same project to project, similar to what we have for supplier contacts.

Can you suggest some defined contact types rather than generic 1,2,3?

thanks, Ian

[relleumk]

@prem_agrawal 

The multiple is nice for a large project, but if that is too difficult i think a majority of the projects will be fine with Just one Contractor Main Contact