The week
Change the form in June and every visit from March changes with it.
That is how most form builders work. The answers are stored against question identifiers, the questions are edited in place, and a year of field intelligence quietly becomes unreadable — the answers are still there and nobody can tell what was asked.
Pinning the version fixes it.
Versions
A visit answers the form it was planned against.
Publishing does not edit the template — it takes a copy and freezes it. Each visit records which frozen version it belongs to, and the answers are checked against that version rather than against whatever the form has become since.
So a visit logged in March still reads, in December, as the form the rep actually filled in.
And publishing re-checks the form before it freezes it, so an invalid one can never be pinned to anything.
- A template in use will not be retired —
Deactivating or deleting one is refused while visits are still in flight against it — with the count named, rather than a generic refusal.
- Answers to a question that was removed are kept —
With the reason written down: they are harmless to keep and they are somebody's work. They are not shown as errors either.
- Six kinds of question —
Short text, long text, a choice, a one-to-five scale, a date and an attachment — with required marked per question and enforced at logging.
- Five starter forms, seeded once —
And if you delete them, they stay deleted. The product does not keep putting them back.
Logging
What is recorded, and what deliberately is not.
The answers, the outcome, the time. The audit of that act records which questions were answered — not what was answered, which is the distinction between an operational trail and a second copy of the data.
Photos and files attach to the visit, capped tighter than the rest of the platform with the reason written in: so a rep on a mobile connection does not accidentally push a twenty-megabyte photo from a customer's car park. The file type is resolved from the content, and a client's own label is honoured only where it agrees — so a document cannot be mislabelled as a photo.
- Attachments are never required —
Nothing marks a visit incomplete for lacking one.
- Deleting a file does not depend on the storage working —
The record is removed immediately; the bytes follow. A storage hiccup cannot leave a file visible after somebody deleted it.
- A visit can be logged after being marked missed —
Because sometimes you do go after all, and the record should be able to say so.
›Can a question be marked visible only to admins?
The control exists in the editor and is not enforced anywhere — a question marked rep-only is returned in full to anybody who can open the visit. Do not rely on it. We would rather say that here than let somebody put something sensitive behind it.
›Can a file be attached to one specific question?
No — attachments are at the visit level. An attachment-type question renders as a text field today.
›Can I restore an old version of a form?
You can read every published version and what it contained. Restoring one means re-authoring it.