TallySignSupport

Suggested edits, change requests and versions

Customers propose wording or ask for a change; you accept, edit or decline, and Tally Sign publishes a new version.

4 sections · 11 screenshots · 4 clips

Step by step · 5 steps

Your customer suggested an edit

Where: Tally Sign → Documents → the document → Questions & changes

1. See the suggested edit

In Tally Sign, choose Documents in the menu on the left and open the document, then the Questions & changes tab. On the page, the paragraph shows the removed words in red and the new ones in green. The Suggested edit card under Open changes shows the same change and the customer's Reason.

More detail: See the suggested edit

1 of 5

The customer suggests an edit

  1. The customer clicks a paragraph and chooses Suggest edit.
  2. They edit the text in place. Their changes are marked up as they type.
  3. They add an optional reason and choose Send suggestion.
A paragraph being edited on the signing page with a reason and Send suggestion
Suggest an edit: the customer edits the text directly.
The paragraph showing removed text in red and added text in green
The suggestion shows as a redline on the page and as a card in the panel.

The customer requests a change

Some sections can't be edited directly, such as pricing. There the toolbar shows Request change instead. The customer describes what they need and chooses Send request. See Locked sections.

A Request a change box under the Investment section
A change request on a locked section.
The panel listing a change request, a suggested edit and a question
Open changes are listed above the conversation.

Decide on changes

Open the document from Documents and choose the Questions & changes tab. Open changes are listed at the top of Conversation, each as a card:

CardYour options
Suggested editAccept, Edit and accept (change the wording first), Decline
Change requestResolve (after you've made the change yourself), Decline

Each decision can carry an optional note for the customer. When you decline, the customer sees your reason.

Resolving a change request with a note to the customer
Resolve a change request with a short note, then choose Mark resolved.
Accepting a suggested edit: Accept and publish v2
Accepting an edit publishes a new version.
The suggested edit, on the page and in the panel.
Accepting publishes the next version.
Edit and accept publishes your wording instead.

New versions

Accepting an edit publishes the next version of the document. Signatures collected so far are cleared and every signer is asked to review and sign again. The customer's open signing page shows that a new version is ready.

What the customer sees in the new version: the first time they open it, everything that changed since the previous version is marked up on the page: removed words struck through in red, new words underlined in green, and a bar beside each changed paragraph. On a computer, What changed in version 2 at the top of the margin lists each change; clicking one, or the arrows, takes them through the changes in order, and a card beside each change says who made it and whether it was their own suggestion, accepted. The switch turns the markup off to read the document clean, and Compare with version 1 opens the two side by side. On a phone, Show changes next to the version does the same.

Tables are marked up the same way, inside the table: in a changed row of the scope table, key details or any other table, the old words are struck in red and the new ones underlined in green, a new row or bullet is all green, and a removed row stays where it was, struck through. The card beside the table says how many rows changed.

The document after accepting, showing Version 2
The accepted text is now part of the document.

On the document's Questions & changes tab, Versions lists each version with what changed. Click a version to see its full text with the changes marked.

The Versions tab with Version 1 and Version 2
Every published version is kept.
Version viewer highlighting the accepted change
Open any version to see exactly what changed.
Every version, with what changed.

On the website: No CRM needed·Pricing