The main use case for which we have designed FltCheck is when the user has to go over the same procedure time and time again as a part of their routine. Each run through a such procedure can be based on different variables and yield different results, but the procedure itself doesn’t change much.
As an example this may be a pilot carrying out pre-flight procedure before each take off or flight support employee requesting a certain permit for each clients trip request.
Templates and Checklists
Scenario described above assumes a defined, repeatable process being set in place and then following it on occasions when it needs to be carried out. In FltCheck we handle this with Templates which describe the process and Checklists which are created based on Templates for each time process needs to be followed through.
Knowing that there are some procedures that you’ll repeat often – it’s best if you capture them as Templates.
To create a Template you need to go to Templates tab and press “New Template” button in top-right corner of the screen.
A New Template window will show up, in which you have to provide your template Title, description (not required, but may come handy sometimes) and decide whether this template will be visible only to you or your whole team. Don’t worry too much about getting it perfect now, you can edit any of these details and options later on.
Great! You have your template created. FltCheck operates on checklists, so each step of a procedure becomes a single check. Let’s add some checks now. You do this by simply typing the names of the steps in the input on top of the left column and hitting Enter to add each new item.
Sticking to our example with Egypt overflight permit, we would lay out steps of the procedure as we usually go about it:
Now, you can click and drag items to reorder them or click an item to view it’s details in the right panel. You can edit check’s name, add or edit a description and add documents. This last feature is especially useful if every time running a procedure, you for example need some form or document. This is an easy way to always have it handy while running a checklist.
Let’s add some useful information in the checks description. These will come in handy each time we’ll be running checks later on.
Outside adding descriptions, at this point you can do even better by embedding documents in checklist template. For example if there is an overflight request form available to use, you can embed it in “Prepare Overflight Application” item, so every time you’re at that step you have the form ready to be printed out immediately.
You can also set a check type. In many cases a Simple Check (which only has two statuses: checked/unchecked) will be enough. In other cases you can switch to Advanced Checks which will allow you to assign more specific values to checks. We’ll cover check types and handling in a separate post.
That’s it. The template is ready. At any time you can go back and edit it.
Now that the template is ready, you can run it any time you need to get a permit by simply clicking Run button in top-right corner of the screen.
This will open a window in which you will provide some details regarding this specific run. In our case, let’s say we provide flight number and the date by which the procedure is due to be finished.
By clicking Run you create a new Checklist out of template. This will also take you automatically to Checklist view.
You can do it multiple times, so at any time you can have multiple checklists based on the same template opened. You can see all your Opened (and archived) Checklists in Checklist tab.
As you progress with the procedure for obtaining the permit, you simply check the next items on the list. This way you and your team can easily track progress on every process you’re in.
Active Checklists have a few useful features that are not accessible on template level, but can be very handy especially when you’re working with other people: assigning people and comments. Without getting into much details at this point let’s see how a quick run through a checklist would look like including assigning people and adding actual permit obtained in the process.
When you are all done, you can archive the checklist so it doesn’t show up on your active checklists view, but you can go back and refer to it any time in the future.
This completes the description of basic FltCheck functionality. Our development team is working on extending these feature and adding new ones: timelines, improved mentions, more powerful library and real-time updates and notifications for larger teams among others. If you have any comments or feedback about the existing or upcoming features we would love to hear from you!