Exporting evidence

Attestation packet

Open a family from Controls and choose Export packet. You get a ZIP of that family's completed attestations, each record as it was read, and a manifest in JSON and CSV.

For every item, the manifest lists the hash, the integrity result, the roles held, the governance library version, and the result, score and pass mark. People who attempted an exercise and never passed are listed too, marked as not completing it.

Document package

Open Document package under Review and choose Download package. You get one ZIP with where each family stands, what is still open, who holds which role, what training is owed, an index of your evidence files and each family's attestation packet.

It holds five lists, each as a CSV file and a JSON file: family-summary (every family, its status and how many attestations are recorded), open-items (the rows of the Open items table), roles (the principal, stewards and viewers of each role), training (per person, the exercises owed and done) and evidence-index (each evidence file, its last-modified time and a link to it). Beside them are a manifest and a packets folder with the attestation packet of each family.

The evidence index links to the files in your own SharePoint site. It holds no copies.

A package with open families can still be downloaded, and its manifest lists exactly what is missing. With no standard in scope, there is nothing to download.

Generated documents

Open Document library, find the document and choose Generate PDF. The PDF is saved to your Evidence library and linked on the page. The page marks a document Out of date when the mandate it was generated against has changed since.

Placeholders in a document are filled from the values saved on the Variables page. If a saved value was changed outside the app, the document leaves it out and the placeholder stays unfilled, and the page says which one.

Diagrams

The Crosswalk view under Visualize has an Export button that saves the whole diagram, not only the part on screen, as a PNG or a PDF.

Where the files go

Your browser builds each file. The packet, the package and the diagram download to your device. A generated PDF is saved to your Evidence library.

Before you hand a file over

Check Open items for families that need review. A family that needs review has an evidence file that is missing or has changed since it was attested, and the package reports it.

What it does not do

• It does not assess you. The package states what was recorded in your tenant when it was assembled, and says nothing about whether any family meets a standard.
• It does not sign anything. The hashes in a manifest are tamper-evidence against casual alteration only, and the key ships inside the app.
• A packet on its own cannot repeat the integrity check for a keyed hash. Its integrity column records what the Turbo Governance System found when it built the packet.
• It does not say why an evidence file changed or who changed it. It reads only whether the file exists and when it was last modified.

Next