Commitments
Promises kept as records — who promised what to whom, when it's due, and how it was closed out.
A commitment is a promise your company made. It is the most-used of the five Company State record types, and the only one the landing page highlights by due date.
Three different people
A commitment names up to three:
- Promisor — who made the promise.
- Promisee — who it was made to. This is required; a promise with no recipient isn't one.
- Owner — who is on the hook for delivering it.
They're often the same person, and promisor and owner can both be left blank. A commitment nobody owns is one nobody will chase, so fill the owner in when you can.
Creating one
New Commitment needs a title and a promisee. Everything else — description, owner, promisor, due date — is optional but is what makes the record findable and chaseable later.
Two fields take a compact list format:
- Affected entities —
account:acct-1:Acme, project:proj-1. These become links out to the record involved. - External references —
gmail:msg-1:https://mail.example/msg-1, pointing back at the original message or record.
Filtering the list
Status and owner are applied by the server. The due filter is applied to what came back, and only ever matches open commitments:
- Overdue — past its due date and still open.
- Due soon — due within seven days and still open.
- No due date — no due date set, whatever the status.
A commitment that was missed and then closed will not show under Overdue — it's no longer open. Search matches title, promisee, and owner.
Closing one out
Open commitments show Mark satisfied on the row, for the clean case where the promise was kept.
When the outcome isn't a clean yes, open the commitment and use Close Commitment instead. That asks you to pick the outcome — fulfilled, missed, or cancelled — and lets you add a reason, which is kept with the record. Closing needs the close permission.
Marking something satisfied when it was actually missed loses the one signal worth having. Use the real outcome.