Recording an attestation
An attestation is a completed exercise recorded in your SharePoint site with the evidence file it produced, and the Controls pages show where each family stands.
How one is recorded
Passing an exam, or submitting an exercise that has no graded question, writes a record to your SharePoint site and uploads a PDF to your Evidence library.
The record names the exercise, who submitted it, when, the answers, every role the submitter held at that moment and the governance library version pinned in your tenant.
In the Turbo Governance System, a submission page opens for the person who submitted it and for the people above them in your directory. That is a screen in the app, not a permission. Who can read the list in SharePoint is set by the list's own permissions.
What the status of a family means
Attested: an attestation is recorded and its evidence file is in place.
Needs review: the family is attested, but its evidence file is missing or has changed since it was attested.
Not yet attested: no attestation is recorded for the family.
Nothing in this app attests it yet: no exercise in the Turbo Governance System covers the family.
Keeping them current
Open items lists every family not yet attested, every family that needs review, every attestation that has lapsed and the training still owed, with an owner and a target date where one exists.
Renewals lists the attestations that are overdue or due soon, with each one's renewal cycle and its window in days. Attest the exercise again to renew it.
If a new governance library version removes an item, the records on it stay in your tenant as written. Records on retired items, under Tenant admin, lists them and exports them as JSON.
Checking a record
When the Turbo Governance System shows a record, your browser recomputes a hash of the record and compares it with the hash stored when the record was written. Verified means they match. Not verified means they differ, or there is no hash to compare against. While the records behind a figure are still being checked, the figure is marked Not yet verified, and if your browser cannot run the check the screen shows no status and asks you to reload.
A count leaves out any record that changed outside the app, and lists it beside the count.
The Audit log, under Settings, Tenant admin, lists every create, update and delete the Turbo Governance System made to your tracked lists: who, what and when. It marks an entry Changed outside the app when its stored hash no longer matches, and the page states what its checks find and what they do not.
Each time you open the Audit log, your browser also checks the order of the entries and reports most entries deleted from the middle of the log. It reports entries deleted from the end only after a checkpoint has recorded the log, and the page says when no checkpoint is active in your tenant.
What it does not do
- It does not make you compliant. Attestations are your records of work done, and they certify no one.
- The hash is tamper-evidence against casual alteration, not a signature. The key ships inside the app, so it does not prove who wrote a record.
- It does not stop someone with write access to your SharePoint lists from changing a record. It marks the change the next time it reads the record.
- Its checks do not defend against a tenant or site administrator, who can change a list's permissions and its entries.
- A submission page shows each question as it reads today, which may differ from the wording when it was submitted.