Variables and blanks
Two ways to leave something out of a contract until it's needed, and they work in opposite directions.
Variables are filled by CoreHue from information it already has. Client fields are blanks your client types into while signing.
The full comparison is in Auto-filled details and blanks. This page is the reference.
The variables
Insert them from Insert Variable in the toolbar. There are 28, grouped by where the information comes from.
Client Client Name · Client Email · Client Phone · Client Address
Business Business Name · Business Email · Business Phone · Business Address · Registration Number
Contract Contract Number · Contract Date · Expiry Date
Booking Booking Date · Booking End Date · Service Name · Venue · Booking Duration · Start Time · End Time · Package · Add-ons
Invoice Invoice Number · Invoice Total · Currency · Deposit · Balance
Dates Today's Date · Current Year
Where they get their values
| Group | Source |
|---|---|
| Client | The contact's record |
| Business | Settings → Business |
| Contract | The contract itself |
| Booking | The linked booking |
| Invoice | The linked invoice |
| Dates | The date the contract is prepared |
Every variable has to be filled in before you send
A contract can't go out with a gap in it. If something can't be filled in, the send is stopped and CoreHue lists each one with the reason: No booking linked, Business phone not set in profile, No expiry date set.
The usual causes:
A booking variable on a contract with no booking. Booking Date on a standalone contract has nothing to read. Link a booking in the details card, or take the variable out.
An invoice variable with no invoice linked. Link one, or remove them.
A business detail you haven't filled in. Registration Number is blank until you enter one under Settings → Business.
In a proposal's contract, the invoice variables are the exception. No invoice exists yet, so they're allowed to wait, but only if the proposal collects payment. Without payment there will never be an invoice, so CoreHue tells you to turn payment on or remove them.
If one slips into a document that's already out, it shows in red italic text, so it's visible rather than silently blank.
Contracts attached to booking services
These are stricter, because the contract is signed at the moment a client books, with nobody there to notice a problem.
A service contract only becomes available once every variable in it can be filled in for every booking, and you have a saved signature. The service page lists what's outstanding under Finish these first.
Four variables can't be used on a service contract at all, because nothing at booking time can fill them: Expiry Date, Booking End Date, Package and Invoice Number. CoreHue names them and asks you to remove or replace them.
One thing worth knowing. If your contract uses Client Phone, CoreHue won't attach it until the booking form collects a phone number and marks it required. It tells you which switches to turn on, and leaves you to turn them on.
The blanks
A client field is a blank your client fills in while signing. Two types:
- Text, for anything written
- Date, with a date picker
That's the full set. There's no initials field and no signature field beyond the signature itself.
Add one from Client Field in the toolbar. Each has a Label, a Type and a Required switch. They're listed under the contract body as Client fields, with a count, so you can see at a glance what you're asking of them.
Label them clearly. Your client is reading a legal document, probably on a phone. "Name of your day-of coordinator" beats "Coordinator".
Up to 50 fields per contract, which is far more than any sensible contract needs.
Once signed
Whatever the client typed is locked into the finished document, underlined where it sits in the text. You'll see it filled in when you view or download the signed copy.