What FlightPath is
The shape of the product: organizations, clubs, classes and members, and what a club night looks like in the app.
FlightPath runs the record-keeping side of an Awana-style children’s club: weekly check-in and points, handbook progress, awards and handing them out, family records, registration, reporting, and the club calendar.
It is a web app, so there is nothing to install and everyone in your church sees the same up-to-date information. It also installs to a phone or tablet home screen, which is how most leaders use it — see Install FlightPath on your phone or tablet. Admins tend to work on a desktop for setup and reports.
The five things everything is built on#
Almost every screen in FlightPath is some combination of these five.
Organization — your church. All of your data belongs to it, and nobody outside it can see any of it. If you only ever run one church’s club, you will barely think about this again.
Club — a program level: Cubbies, Sparks, T&T, Trek, Journey. Each club has its own check-in configuration, its own books, its own awards, and its own classes. That is why the same check-in item can be worth 10 points in Sparks and 5 in T&T.
Class — a group inside a club. “Kindergarten Sparks” or “T&T Boys 3-4”. A class has a color, an optional age range, its own leaders, and its own clubbers. The class color is what tints a clubber’s avatar everywhere in the app.
Member — one person. Clubbers, leaders, admins, parents and visitors are all member records. Only staff have logins; a clubber is a record, not an account.
Household — a family. The address, church, contacts and pickup notes live here once, shared by everyone in the family, instead of being typed onto each child.
What a club night looks like in the app#
- A leader opens FlightPath on a tablet. The Members page lists the clubbers in their scope, with a search box and filters above it.
- As each child arrives, the leader finds them and opens the Check-In tab, then ticks the boxes they earned — attendance, uniform, Bible, handbook. Every tick saves on its own; there is no submit button.
- When a clubber says their verses, the leader opens the Books tab and checks off the sections. Completed sections earn points, and any award they satisfy fires right then.
- Nobody has to tidy up afterwards. The night’s records are already in the reports.
Screenshot to come
The Members page on a tablet, with the clubber list on the left and a clubber's Check-In tab open on the right
Where the rest of it lives#
The top bar carries the day-to-day pages: Members (the home page), Households, Online Registration, DB Users, Reports, and Clubber Awards. Some of those are admin-only or need a permission flag — Roles and who can see what covers exactly which.
Setup lives behind your avatar in the top right: Profile, Meeting Schedule, Configuration, Admin Dashboard, API Tokens and Log Out. That is where an admin builds clubs and classes, edits books and awards, sets check-in items, and generates the season’s calendar.
Two ideas worth learning early#
Most of the confusion we hear about traces back to one of these two.
The first is the club week . Everything on club night is scoped to a week running Sunday through Saturday in your organization’s timezone. A check-in you record on Wednesday stays visible and editable all week, so you can fix Wednesday’s mistake on Friday morning. It rolls over on Sunday.
The second is what a leader can see . A leader is narrowed to the clubs and classes they are assigned to, and that assignment is the answer to almost every “why can’t they see this child?” question.
Where to go next#
- Brand new church, nothing set up yet: First-week setup checklist.
- Volunteering this Wednesday: Check a clubber in.
- Want the vocabulary first: Key concepts and glossary.