Aloft has introduced Workflows to allow admins to set up procedures within the platform to help pilots follow established Standard Operating Procedures (SOPs). Workflow can contain many components like Checklists and Risk Assessments. Once a workflow has been created, we’ll need to associate the workflow to a role so that those users are prompted with the appropriate procedures. This will be their default, day-to-day, workflow. Workflows can also be assigned at a mission-specific level under the Procedures tab of the mission.
Workflows can also support a Planning Status. Just like preflight and postflight steps in the app, admins can provide structure to the mission planning workflow from the web browser. Pilots and admins can now document their compliance with any SOP requirements during the mission planning process.
In this screenshot, a pilot is being prompted to “Complete Planning” steps on their mission.
Operators can now run checklists and risk assessments right from their web browser to ensure the necessary steps are taken before the flight ever begins, saving you time and effort.
In this screenshot, the pilot is walked through the planning procedure right on their web browser. Progress can be saved and returned at any time.
The Planning workflow feature is highly customizable and can be set as required or optional by administrators depending on your mission needs. It provides the same flexibility as our existing preflight and post-flight options, allowing you to tailor it down to mission-specific requirements.
Along with the new Planning status, admins can also define which users have the ability to mark missions Approved. This allows for more direct approval processes and can be further supported by creating a specific Alert for these mission statuses. Admins can also require the planning status, and then pilots creating missions will approve their own missions for more of a hand-off approval approach.
The planning phase of the workflow is not required.
Next, we can dive into how checklists and risk assessments fit into the workflow.
Or, skip to Completing the Workflow to understand how these steps get logged.