Multiple notes per stage, written in a rich-text editor, filed under the project's actual contact and labelled with the project and stage. Editable and deletable with confirmation.
Also called: job notes · site notes · note on framing · write it down
- 1Notes resolve their contact from the project's bonded contact_id, mirrored into the project cache
- 2The stage detail string ('<project> / <stage>') categorises the note
- 3Fuzzy name matching survives only as a fallback for legacy projects created before the column existed
Notes on a stage were matched to a customer by name, and the match accepted any shared three-letter run — so a stage belonging to one customer resolved to a different customer entirely, and in a book of ten test jobs every single one landed on the wrong person. One customer's notes were displayed under another customer's build, which is the sort of thing that ends a relationship when the wrong person reads it. Any real book of business with two customers sharing a first name failed the same way. Notes are bound to the job's actual customer record.
- Notes attaching to the wrong contact via name matching
- Stage-level context living in text messages
See it on your own jobs
Twenty minutes, your numbers, no slide deck. We’ll build one of your real buildings in front of you and send you the estimate link at the end — yours to keep either way.
or keep browsing features →