How this app is laid out

There are fewer screens here than the feature list suggests, and they are worth a tour before you start, because the course sends you to each of them in turn.

The dashboard is the hub. It holds your beacons, the box for logging the day's practice, your streak, and at the bottom the controls for exporting or deleting everything. A beacon is what this app calls a project: one community problem you are working on, with a named person at the centre of it.

Opening a beacon gives you the workbench. It stacks the tools in the order you use them — the six-part worksheet first, then the ten-question test, then the gate check, then the place you record what actually happened. You are not meant to fill it top to bottom in one sitting. Most of it waits until you have talked to someone.

The insights page is the one that adds up. It multiplies four factors together rather than averaging them, which means it tells you which single thing is holding your score down instead of giving you a comfortable middle number. That page is the reason the arithmetic in module six is worth understanding.

One convention runs through all of it and is worth knowing now. Every number in this app declares where it came from. Adoptions, test scores, cleared gates and practice days are things the app watched happen. People helped, hours returned and every Return on Technology figure are things you typed in. They are shown differently and they are never added together, because a credibility record that blurs the two is worse than no record.

Your plan sets how many beacons you can run at once, how far back your practice history goes, and how many AI assists you get each month. The free plan carries one beacon, which is exactly what this course needs.