Best Approach for Handling Contracts - Need Advice

Hi @Dean Russell,

Kitzzy here from the Education team. Thanks for posting this question to generate ideas.

To answer your first question, if you amend the contract in a smart file, the entire thing will be sent again to your clients. So it sounds like option two may work best for you, where the first file includes the basic contract and invoice, then a separate smart file with just the updated contract. However, I’m curious to hear from our other members on what has worked best for them!

Thanks,
Kitzzy

@kitzzy 

Thanks for your reply! I ran some tests and found that the whole file gets sent (darn), so I came up with a compromise.

1. Client receives a proposal with only a service overview and timeline.
2. After submission, the client is sent a contract smart file to sign.
3. This triggers the invoice/pay smart file to be sent.
4. The kickoff meeting follows the deposit.
5. Update the contract with new information and resend for signature.

This way, the contract is sent independently, so updates only send the contract, not the entire file. I know combining contracts and invoices in one file is the charm of “smart files,” but resending the invoice/pay smart file would confuse clients. Perhaps a future update could allow sending just one updated file in a smart file?

Hi @Dean Russell,

Glad you found a compromise that worked for you. If you haven’t already, I suggest submitting a feature request for this here so our product team can consider it. 

Thanks,

Kitzzy