> For the complete documentation index, see [llms.txt](https://intuitem.gitbook.io/ciso-assistant/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://intuitem.gitbook.io/ciso-assistant/configuration/authoring/excel.md).

# Excel-driven authoring

Authoring frameworks, matrices, and other library content from Excel

> *Stub — to be expanded.*

Excel is one way to author library content, especially when adapting a source spreadsheet or preparing a file to share. CISO Assistant accepts the workbook directly and converts it to YAML during import. To create and edit a library on your instance without a spreadsheet, use the [Library builder](/ciso-assistant/configuration/authoring/library-builder.md).

This page introduces Excel-driven authoring. For the workbook creation and optional conversion steps, see [Create a Library](/ciso-assistant/configuration/libraries/create-library.md). The [Library objects](/ciso-assistant/configuration/libraries/library-objects.md) pages describe the sheets and fields for each object.

For framework scoring, the framework `_meta` tab defines the default `min_score`, `max_score`, and `scores_definition` used when audits are created. Individual requirement rows can override those values with their own `min_score`, `max_score`, and `scores_definition_ref` (a named entry in the framework's `scores_definition.alternatives` registry) when a framework mixes scoring ranges. Leave those cells blank to inherit the audit-level scale at runtime.

## What this page will cover

* **Why Excel over raw YAML** — fewer errors, easier diff with subject-matter experts, free spreadsheet validation (data types, dropdowns).
* **The v2 format at a glance** — `_meta` tab, per-object tabs (requirements, matrices, threats, reference controls, mappings), the `depth` / `assessable` columns.
* **Skeleton generation** — using `prepare_framework_v2.py` to scaffold a valid Excel file rather than starting from a blank sheet.
* **Conversion workflow** — `convert_library_v2.py my_file.xlsx`, where the YAML lands, how to spot validation errors.
* **What can be authored in Excel** — frameworks, risk matrices, threat catalogues, reference controls, mappings; what *can't* (custom code, dynamic logic).
* **Reviewing in spreadsheet form** — using sheet review, comments, and named ranges to collaborate with non-engineers before conversion.
* **Excel pitfalls** — auto-formatting numbers as dates, hidden characters from PDF copy-paste, encoding mismatches in non-Latin scripts.

## Existing material

* [Create a Library](/ciso-assistant/configuration/libraries/create-library.md) — the step-by-step Excel workflow and optional YAML conversion.
* [`tools/example_framework.xlsx`](https://github.com/intuitem/ciso-assistant-community/raw/refs/heads/main/tools/example_framework.xlsx) — annotated reference Excel that converts cleanly.
* [`tools/excel/`](https://github.com/intuitem/ciso-assistant-community/tree/main/tools/excel/README.md) — repository of real Excel sources used to produce the built-in libraries (CIS, CCB, e-ITS, CMMC, …).

## Related

* [Library builder](/ciso-assistant/configuration/authoring/library-builder.md) — the in-app alternative, and the editorial discipline that sits on top of the library format.
* [Update a library](/ciso-assistant/configuration/libraries/update-library.md) — how to publish a new version and apply it to existing audits.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://intuitem.gitbook.io/ciso-assistant/configuration/authoring/excel.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.