Every hour, every program, every partner. Verified.
The trusted record of everything a community does outside the classroom.
I’m a…
Six ways in. Each one explains what TierSphere does for you, in your words.
How verification works
One chain, start to finish. Every hour on TierSphere got here one of two ways, and a person signed off on both.
Staff run the check-in live
Someone on site opens the session and checks people in while it is happening. The record is made at the moment it is true, by the person who was standing there.
Hours from elsewhere are reviewed
Work happens off-platform too, and people submit it after the fact. Those hours sit as pending until a coordinator at the organization reviews them and approves them.
Only approved hours count
Approved hours roll into the totals a district, a funder, or a family sees. Pending hours are visible as pending and are counted nowhere until someone approves them.
Nothing counts until a person verifies it. That is the whole claim, and it is the only one we make. Not “no self-reported hours” — people do submit their own. They just don’t count until someone approves them.
What it actually looks like
Not a mockup of something coming later. These are the screens, with sample data in place of anyone’s real record.
The pending row is the feature. Two hours are sitting there uncounted until a coordinator approves them, and the total says 7.5, not 9.5.
The answer before the question. When a district asks who is cleared to be around students, this is already the answer, not a week of email.
The agreement stops being paperwork. It turns green in one place both sides can see, with the expiry tracked, instead of living in someone’s inbox.