The approvedAt timestamp on a ReportVersion is set when the approvedBy name is recorded, marking the moment the report transitioned from draft to approved status. This timestamp is important for regulatory compliance: permits typically specify deadlines by which reports must be submitted, and approvedAt (combined with any external submission timestamp) demonstrates the timeline. If a report was approved and submitted before a deadline, approvedAt provides the evidence. Null approvedAt means the version is still in draft status and has not been formally cleared for regulatory submittal.
Technical section
Data model, API, and internals — visible to developers.