Put the right action in the right hands.

Describe one real document journey before comparing plan names.

Reuse the document structure while deliberately checking its wording, roles and changing values.

Map fields to participant roles before you place them on the document.

Require information only when the document process genuinely depends on it.

Use an order when the process requires a dependency, not simply because the option exists.

Do not request a signature from someone who only needs a copy, or mistake a viewer for a required party.

Validate the recipient list and template constraints before issuing many independent requests.

Treat an access code as private access information, not as a public part of a signing link.

Share the minimum useful template collection and check what the folder exposes.