> For the complete documentation index, see [llms.txt](https://experience-digital-transform.gitbook.io/experience-digital-transformation/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://experience-digital-transform.gitbook.io/experience-digital-transformation/building-block/module-6-run-the-method-in-your-administration.md).

# Module 6 — Run the method in your administration

What to require from a supplier; change; progress read from the work; the AI assistant and the person who rules; the next service; another sector; the method's own limits

**Written for:** the team that commissions the service and makes the case to the minister (Strategist register). **Videos:** 7.

**What it teaches.** What to require from a supplier; change; progress read from the work; the AI assistant and the person who rules; the next service; another sector; the method's own limits.

**What you can do afterwards.** Require the documents from a supplier, handle change, read progress from the work, use the AI assistant safely, and carry the method to the next service and another sector.

**What it uses of the worked example.** A change of an institution's name, the trace report, and the digital credential as the next service.

## Subtopics

| #                                                                                                                                                                             | Subtopic                                                        | Class         | Demonstration | Single message                                                                                     |
| ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | --------------------------------------------------------------- | ------------- | ------------- | -------------------------------------------------------------------------------------------------- |
| [6.1](/experience-digital-transformation/building-block/module-6-run-the-method-in-your-administration/6.1-what-to-require-from-a-supplier.md)                                | What to require from a supplier                                 | Core          | —             | The twelve documents are deliverables you name in the contract, each accepted by a named person.   |
| [6.2](/experience-digital-transformation/building-block/module-6-run-the-method-in-your-administration/6.2-when-something-changes-correct-the-document-that-owns-the-fact.md) | When something changes, correct the document that owns the fact | Core          | Yes           | A change goes up to its source and everything below is produced again.                             |
| [6.3](/experience-digital-transformation/building-block/module-6-run-the-method-in-your-administration/6.3-read-where-the-work-stands-from-the-work.md)                       | Read where the work stands from the work                        | Core          | —             | Progress is a report the programs produce from the documents, never a figure someone remembers.    |
| [6.4](/experience-digital-transformation/building-block/module-6-run-the-method-in-your-administration/6.4-the-ai-assistant-at-every-step-and-the-person-who-rules.md)        | The AI assistant at every step, and the person who rules        | Core          | —             | The assistant drafts each document; a person rules on every proposal and every gap keeps its name. |
| [6.5](/experience-digital-transformation/building-block/module-6-run-the-method-in-your-administration/6.5-the-next-service-on-the-same-foundation.md)                        | The next service on the same foundation                         | Core          | —             | The second service, a digital credential, reuses what the first one built and proved.              |
| [6.6](/experience-digital-transformation/building-block/module-6-run-the-method-in-your-administration/6.6-carry-the-method-to-another-sector.md)                             | Carry the method to another sector                              | Core          | —             | The method holds no sector's content; another sector brings its own catalogue and its own records. |
| [6.7](/experience-digital-transformation/building-block/module-6-run-the-method-in-your-administration/6.7-before-you-rely-on-it-what-the-method-does-not-claim.md)           | Before you rely on it: what the method does not claim           | Supplementary | —             | The method states its own limits, and a manager reads them before relying on it.                   |

**Self-check.** [Four questions on what a manager decides](/experience-digital-transformation/building-block/module-6-run-the-method-in-your-administration/self-check-module-6.md), with the answer the module gives to each.

{% hint style="info" %}
The reference pages hold what every module uses: [the twelve documents](/experience-digital-transformation/building-block/the-twelve-documents.md), [the blank instruments](/experience-digital-transformation/building-block/the-blank-instruments.md), [the worked examples](/experience-digital-transformation/building-block/the-worked-examples.md), [the frameworks and standards](/experience-digital-transformation/building-block/frameworks-and-standards.md), [the public sources](/experience-digital-transformation/building-block/the-public-sources.md), [the standings of the method's standards](/experience-digital-transformation/building-block/the-standings-of-the-methods-standards.md), [the glossary](/experience-digital-transformation/building-block/glossary.md) and [the figures](/experience-digital-transformation/building-block/figures.md).
{% endhint %}


---

# 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://experience-digital-transform.gitbook.io/experience-digital-transformation/building-block/module-6-run-the-method-in-your-administration.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.