> 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

> *Stub — to be expanded.*

**Excel is the recommended authoring format** for most CISO Assistant content. Once an Excel file is written it gets converted to YAML by a single command, and the resulting `.yaml` is what the platform actually loads. The Excel route is faster than hand-writing YAML, much easier to review with non-engineers, and the converter tooling validates the structure for you before it ever reaches your instance.

This page captures the editorial conventions for Excel-driven authoring; the full v2 Excel format reference and the converter command-line are in [Designing your own libraries](/ciso-assistant/configuration/libraries/custom-libraries.md).

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

* [Designing your own libraries](/ciso-assistant/configuration/libraries/custom-libraries.md) — the full Excel-to-YAML reference, including the v2 format spec and the converter usage.
* [`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.
* [Library upgrade](/ciso-assistant/configuration/libraries/library-upgrade.md) — what changes in a re-converted Excel file are safe to ship as a minor upgrade.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

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

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.