Consent with a timestamp: what it means — and what belongs to it
“Timestamp” sounds technical, but it’s very practical: later you want to be able to trace when an approval existed and what scope it had. What matters isn’t only the time, but the context (project/occasion) and a clear closure state.
Short version
- Timing: when was it approved?
- Scope: approved for what exactly (purposes/platforms)?
- Mapping: which project/occasion does it belong to?
- Closure: when did “received” become a final state (finalize)?
What belongs in “clean” documentation?
- Project/occasion (e.g. appointment, job, shoot).
- Scope (e.g. Instagram, website, advertising).
- Timestamp (when received).
- Reference (so it’s unambiguous later).
- Optional: proof level (email verified / signature), depending on the situation.
Examples (everyday)
Approval for portfolio + Instagram. Timestamp + project name make it clear later which appointment it referred to.
QR code at the entrance. Consents land in the event project; you finalize proof only for relevant people.
Multiple people share links. One consistent flow avoids version chaos; finalizing fixes the state.
What does a timestamp mean in consent?
That the time of approval is documented — together with context and scope, so it remains traceable later.
Is a screenshot/chat enough as a timestamp?
In day-to-day work often yes. If you later need clean mapping/explanation, a project flow helps more than scattered evidence.
What else should be included?
Project/occasion, scope (purposes/platforms), a clear reference/ID — and a closure state (finalize).
When is it exportable?
In LegitForm only after you finalize: that’s when proof (PDF + protocol) is created.
Is this legal advice?
No. This is practical guidance for documentation/workflow.