What happens when a recipient requests changes or rejects?

Both actions stop the recipient from signing the current agreement, but they communicate different outcomes.

Requested changes

The recipient selects the change-request action and adds a note. Scriboflow records the event and gives the contract a changes-requested status so your organisation can review the feedback.

The request is not an automatic edit and does not mean the proposed wording has been accepted. Open the contract, read the note and decide what should change. Update the agreement through the supported flow, review the complete revision and send it again when ready.

Rejection

Rejection records that the recipient has declined the current contract and stops its active signing flow. Review the activity and any information the recipient provided before deciding what to do next. If a new proposal is appropriate, prepare it as a separate, reviewed agreement rather than treating the rejected version as signed.

Neither a change request nor rejection restores contract allowance usage after the contract's first successful external send. Status changes do not reverse that use.

For step-by-step handling, see Respond to requested changes. For recipient actions generally, see Understand what recipients can do.