Build an internal dashboard
An internal tool replaces a spreadsheet. Decide who may see it before you decide what it looks like.
What this business needs on a site
Internal tools are not used because they look good. They are used because entry is fast.
So the first result is a starting point, not the finished thing. Cut the daily taps down.
And an address without a login is a public address. Add staff accounts before you share it.
Who is allowed in
Staff only, or a manager view as well. This is the first decision, not the last.
The entry screen
Whatever gets typed every day. If it takes more than a few taps it will not be used.
Status and totals
The one screen someone opens each morning, plus the monthly figures.
Getting the data out
Export to a spreadsheet. Someone always needs it in a different shape.
What to type
Say what is being tracked and name the screens.
Internal tools want fewer words and more table. Naming the three screens is enough — decoration is not the point here.
What to fix in the result
Step 1. Match your own words
Class, session, cohort — use the words your staff already say. Ask for the rename in one sentence.
Step 2. Make entry faster
Bulk entry, defaults, keyboard order. Ask for it explicitly; the first result optimises for looks.
Step 3. Add a login
Internal tools need sign-in. Ask for staff accounts before you share the address.
Check before you publish
Sign-in before sharing
An address without a login is public. Add accounts, then share.
Your data stays in your app
Row-level rules mean each project's data is only visible inside that project. Test with a second account to see it working.
Collect less
Names and phone numbers of students or staff are personal data. Keep only the fields you use.
Nine security checks
The publish step runs nine checks and shows you the result before the address opens.
Three templates for this trade
Read next
Stuck somewhere this guide does not cover? Start with the questions people ask most and write to us if the answer is not there.