> For the complete documentation index, see [llms.txt](https://guide.scribe.gov.sg/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://guide.scribe.gov.sg/guides/generate-summaries/summarise-by-templates/create-a-template.md).
# Create a Template
Scribe learns from your example, so your template is only as good as the example you give it. To get started, pick a note from a recurring meeting or conversation type that you often have, with the format and level of detail you want your summaries to have.
### How do I set up a Template?
{% stepper %}
{% step %}
### **Give Scribe an example of your writing**
* Paste your example into the `Paste example` field.
* Name your template and write a short description of what it’s for.
* Click `Next`
{% endstep %}
{% step %}
### **Test your Template and refine as needed**
Scribe learns your structure, tone, and formatting from your example and creates a Template you can edit. Preview your Template using an existing session to see how it performs.
{% hint style="info" %}
**Need help with refining your Template?**\
Use "Refine with AI": Simply tell it what you want to change, and Scribe will update it for you.
{% endhint %}
{% endstep %}
{% step %}
### **Save your Template**
Once you're happy with it, click `Save`. It's ready to use whenever you need it.
{% endstep %}
{% endstepper %}
***
### How do I use my Template once it's created?
To use your Template,
1. Go to your session’s page
2. Click `Generate Summary` > `By Template`
3. Select your desired Template > Click `Generate`
***
### Need some Template ideas?
Templates work best for conversations you document the same way each time.
For example:
* **Intake assessments:** capture a client’s background, needs and presenting concerns in your standard format.
* **Case notes:** record each client session in the structure your team uses.
* **Interviews:** summarise candidate or stakeholder interviews using the headings and assessment format.
* **Meeting minutes:** keep decisions and action items in the same layout for every recurring meeting.
---
# 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://guide.scribe.gov.sg/guides/generate-summaries/summarise-by-templates/create-a-template.md?ask=&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.
.png?alt=media&token=fe839fd5-7b62-4ece-a569-c6bc76ca2dd9)
.png?alt=media&token=ddd7a782-aa88-431c-91e8-c8ced1c82955)
.png?alt=media&token=a3f96a79-5df6-42c3-8f4f-b77d16271d6f)
.png?alt=media&token=97465ce6-a74f-4dbf-af35-24b9c05793c9)