A decision can be clear during a planning discussion and difficult to understand a month later. The people reopening it may need to know which version was reviewed, what the check found and why a particular change was accepted.
That is why Aerlattice keeps plans, assessments, decisions and recordings together in its local workspace. The record should help someone follow the decision without relying entirely on memory.
Keep the assessment attached to the request
A check has meaning in relation to the inputs it used. If the route or timing changes, an earlier result may no longer describe the request being considered.
Aerlattice checks saved drafts before review. Accepted revisions remain fixed until an explicit replacement decision, giving the record a stable reference. Review notes explain the reason for accepting, rejecting or pre-empting a request.
When another option is considered later, it stays a draft while it is examined. That helps distinguish a proposal from the version already accepted.
Retain enough context to revisit it
A route and a final decision may leave out much of the discussion. Assessments and recordings can provide more context about the exercise, the findings and how the situation changed over time.
Complete workspace backups preserve that material together. Exports allow project records and planning geometry to be retained outside the workspace as well.
The aim is a record someone can inspect and question, including the limits of the information it contains.
Be clear about what the record establishes
A saved planning decision can contribute evidence to a wider review. It does not, by itself, establish a complete safety case, satisfy every requirement for an operation or authorise a flight.
Aerlattice remains a demonstrator. Its records describe work within that application and the inputs represented there. Establishing suitability for operational use requires broader evidence and validation, which remain work ahead.
