Kit instructions, fixes and walkthroughs in one place.

In current kits, open Settings → This computer. These checks use a small diagnostic file to test downloading, opening and printing. They do not import or replace your work, change your selected save file, or approve the kit’s records or outputs. Nothing is sent anywhere.

If the kit cannot start, follow the opening screen’s troubleshooting instructions and IT request. You can also download the separate computer check below and open it locally in the browser you’ll use for the kit. It checks scripts, browser storage, downloads, opening files, pop-up windows and printing.

Older kit folders may include CHECK-YOUR-COMPUTER.html; open that adjacent file only if it is present. Current kits keep their diagnostics inside Settings.

Download the computer check

If a check shows a problem

On a work computer?

Work-managed laptops often block a few things the kit needs. Find yours below.

Subject: Request to run a local HTML tool (Extrasphere kit)

Hi [IT contact],

I've purchased an Extrasphere AI governance kit for [team or purpose]. It is a set of HTML files that run entirely in the browser from a local folder. It makes no network connections, installs nothing, and stores data only in the browser and in files I save myself. Vendor details: extrasphere.com/help and extrasphere.com/trust.

On my machine, the following step(s) are blocked: [paste the compatibility check result].

To run the kit, the browser needs to:
1. Open a local .html file from a folder (file:// URLs) in a current desktop version of Chrome, Edge, Safari or Firefox.
2. Run the JavaScript inside that file.
3. Save the kit's work file (.json) where I choose, and download its reports or readable exports in the formats offered by that kit.
4. Let me choose a file to open (the standard file picker) to open a work file or import a CSV.
5. Print to PDF.

Could you allow these for my account, or tell me the approved way to run a local HTML tool here? I'm not asking for any security setting to be turned off for others.

Thanks,
[Name]

The mapping wizard is included free. Import AI inventory and actions in the AI Governance Toolkit, AI Policy & Rollout Kit and Shadow AI Risk Kit, actions and past questions and answers in the AI Questionnaire Response Kit, or actions in the SSPA Section K Readiness Kit. Their industry editions support the same record types. The ISO Evidence Collection kit uses its separate CSV partner-request importer. The AI Feature Record Kit also imports feature, change, evidence and action records.

For the AI Questionnaire Response Kit: Import brings in action records (follow-ups, owners, dates) or past questions and answers. Past answers arrive as unreviewed drafts; reuse one through the response register, where the usual review applies.

Two ways to start

Manual import reads your existing spreadsheet directly.

Manual import works without any AI tool. Your file is read on your computer and nothing is sent anywhere.

For help reformatting it, choose Prepare a file with your AI: select the record type, click Copy import prompt, then paste it into your work-approved AI with the spreadsheet or table. Bring back the prepared CSV using Use pasted CSV or the file picker. Both routes continue through column mapping and review.

The prompt uses plain text and CSV, without a provider-specific integration. Your assistant must support reading the supplied spreadsheet or pasted table and returning CSV; capabilities and company permissions vary. The dashboard sends nothing to AI. Compare the prepared records with your original spreadsheet and confirm that check before importing. AI checks formatting and consistency; it does not independently verify the facts. Source details for this route refer to the AI-prepared file.

1. Choose your records

   In the dashboard, select Import records and choose AI inventory or actions where available. Select an Excel .xlsx or .csv file, then choose its worksheet and the row containing column headings.

2. Match and review

   Confirm which spreadsheet column belongs in each dashboard field. Leave unwanted columns as Do not import. Check Values to add, resolve flagged dates or choices, and confirm any action links to inventory records. Duplicate rows are skipped; you choose which other valid rows to add. An approval or completion in your file arrives as “Imported: Approved, please confirm” (or the decision your file records) and counts as undecided, not as an active approval or a completed action, until you choose Confirm on the record. Empty rows are skipped and counted in the summary.

3. Add, check and save

   Confirm the selected records, then choose Open populated dashboard to review them in their register. View report includes the imported records. Your work file keeps records and import history in a portable work file; use Open to restore it later.

Import files are read locally in your browser. If you choose AI preparation, you share the spreadsheet with your approved assistant yourself. Importing is a reviewed copy into the dashboard; it does not synchronize with your spreadsheet. Save your current work before importing.

The columns each export writes, in order, so a partner or reviewer can map them into their own system. Company is the company name from the kit’s Settings, and the date and time are when you exported. The kits write these files on your computer; nothing is uploaded.

Fictional samples with these columns, using reference numbers only: SSPA Evidence index and handover (Excel) · Handover (CSV); ISO Evidence handover (CSV) · Same columns (Excel).

One record per customer-facing AI feature. A record moves through five states, and the kit only lets it move forward when the facts behind it are recorded.

Draft

The feature is recorded but not yet checked.

Verified

Every required field is filled in and none reads Unverified.

Customer-ready

Verified, with the last reviewed date and reviewer recorded. Only Customer-ready and Published features can go into the disclosure.

Published

The reviewed disclosure has gone out through your normal channel, with the date and channel recorded.

Held

Waiting on a fact, with the reason recorded. A held feature stays out of the disclosure.

Required before Verified

• Provider and model as recorded
• Listed as a sub-processor
• Data sent to the model
• Provider retention of prompts and outputs
• Provider retention status
• Provider uses customer content to train or improve models
• Human oversight
• Owner
• Reviewer
• Evidence references

Provider retention and training can be Not applicable for a self-hosted or internal model. Customer-ready also needs Last reviewed on and Last reviewed by.

When a feature may involve a decision about a person or business

This feature may involve a decision about a person or business. Record a specialist review (name or role, date) before marking it Customer-ready. The kit does not decide whether any rule applies.

Your team sets this answer; the kit never suggests it. Unsure works like Yes. The field is Specialist review recorded (name or role, date).

Changes and re-checks

Log each change to a feature in the Change log. A change marked Triggers re-check: Yes moves a Customer-ready or Published feature back to Verified and shows Re-check due until the re-check is recorded. Changes worth marking: a new model or provider, a change in which customer data reaches the model, or a change to a retention or training setting.

Disclosure

The disclosure, titled AI in our product, shows Last reviewed (date and reviewer role) and a Limits and open items section. That section stays on the page while any included feature has an open item.

Import columns

Feature-Register-Import.csv in your download has every column, with the same names as the dashboard. Common header variations are matched for you; review the matches before importing. A blank value reads as Unverified. If an imported record claims a state its facts do not support, the kit moves it back and says why. The change log and the evidence list import the same way.

Move records to another kit

• Package for the AI Questionnaire Response Kit: for each Customer-ready or Published feature, the evidence entries and answer rows for common customer questions. Each row keeps its evidence reference, checked date and limits, and arrives for your review, never as approved.
• Package for the ISO 42001 Evidence Collection Kit: the feature register and its evidence, as evidence sources you link to partner requests yourself. No standard clauses or request list are added.

Importing the same package again adds nothing twice.

See the AI Feature Record Kit · Writing an AI feature disclosure from your records