FlightLogger's acknowledgement and authorization workflow enable a dispatch function to collect and document any required preflight acknowledgements and authorizations.
This video explains the workflow and how to get started with acknowledgements and authorizations:
The acknowledgement and authorization workflow
For a description of how to enable acknowledgement and authorization and how to appoint dispatchers in FlightLogger, please visit this page.
Once the functionality has been enabled, you are ready to use it on the Departure/Arrival page. Flights must be booked via the booking page in order to appear on the Departure/Arrival page, so first make sure you have created a booking for the lesson (single or multi-student), operation, or rental flight.
Before a flight, all relevant users must acknowledge or authorize via their personal FlightLogger login. For lesson flights, both the instructor and student(s) must 'acknowledge/authorize', while the PIC must do it for operation and rental flights.
Acknowledging/authorizing a flight as a student, instructor, crew, or renter
First, log in to your FlightLogger account using your personal credentials.
From here, go to the Departure/Arrival page, and find your flight in the Departures section. Next to your name you should find an icon that you must click to open an acknowledgement message.
After carefully reading the acknowledgement text, simply click Acknowledge or Authorize.
A green icon appears confirming that your acknowledgement has been registered in FlightLogger. Hovering the icon opens a timestamp of when the acknowledgement was done.
The dispatchers' responsibilities
Before dispatching a flight you should verify that all relevant users have made their acknowledgements, by confirming there's a green icon next to each user on the flight.
Once that is done, click the pencil icon to the right of the flight.
Optional warning popup and blocking feature
If preferred, you can via the account settings enable the warning popup and select rules for blocking dispatch if rules are not complied with. If this function is enabled, a popup appears when clicking the pencil icon on a booking (if not, then skip to the below section called Dispatching).
The warning popup automatically verifies all booked resources, allowing the dispatcher a quick compliance overview before dispatching. It any resources do not comply with the selected blocking rules, the dispatch will be blocked. Otherwise, the dispatcher simply clicks Continue to dispatch after making sure everything is ok.
Dispatching
This opens a popup allowing you to manage the status of the flight, again with icons displaying if acknowledgements have been made.
Once the status is changed to Flight, the dispatcher must click the Dispatch button to confirm. Note that a flight can be dispatched in FlightLogger without the acknowledgements having been done(unless you have activated the blocking function). It is therefore up to the dispatcher to manually verify this before dispatching the flight.
The flight now moves to the Arrivals section and a new green icon in the Status field confirms that the flight has been dispatched. Hovering the icon opens info about who dispatched it and when.
This information remains on the flight when set as completed and moved into the History section. From here it can be exported as a pdf, XML or CSV file, which all include the logged acknowledgement and dispatch information.