For funders
Hours that survive an audit
Most programs report hours a coordinator typed into a sheet. menti reports hours the system observed, and shows you how it knows.
One way in
There is a single insert path into the hour ledger. Nothing is counted unless it came through that path, and every row is deduplicated.
Append-only
No interface can edit a counted row. A correction voids the original and writes a replacement, so the history stays intact.
Verification levels
Hours are labeled by how they were verified, and the mix is reported alongside the total rather than averaged away.
Held hours
Anything flagged for overlap, a daily ceiling breach, an attestation mismatch or missing evidence is held out of the total until a person resolves it.
Nightly sampling
A random five percent of records is re-checked every night. The confirmation rate is published with the figures.
Frozen snapshots
Monthly figures are frozen. A later correction appears as a reconciliation line in the next snapshot, never as a quiet rewrite.
The evidence packet
What lands on an auditor's desk
- The summary report with the reporting tuple on the cover
- The underlying ledger rows as CSV
- The metric policy that was in force
- The audit sample and its results
- A manifest with the generation timestamp and a content hash
Hours you can defend
Every figure arrives with its evidence
menti never reports a bare number. Each hour figure is published as a tuple, so a reader can see what it is made of before they rely on it.
- Total hours
- Verified minutes only. Flagged hours are held out until a person resolves them.
- Sessions
- How many distinct meetings, events or lessons produced the total.
- Participants
- How many distinct people are represented in the figure.
- Percent at level 3
- The share of hours backed by two independent confirmations.
- Audit confirmation rate
- How often a nightly random sample confirmed the record.
- Policy version
- The counting rules in force when the hour was recorded.