> For the complete documentation index, see [llms.txt](https://docs.fairmarkit.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.fairmarkit.com/buyers/requests-intake-buyers/generate-a-scope-of-work-sow/managing-sow-templates.md).
# Managing SOW Templates
{% hint style="info" %}
Only admins can edit scope of work templates in Fairmarkit.
{% endhint %}
As organizations have multiple different Scope of Work templates, you can manage these directly within the admin area of Fairmarkit for your users to use when creating their requests.
{% stepper %}
{% step %}
#### Navigate to the SOW templates tab in the Administration area of Fairmarkit.
{% endstep %}
{% step %}
#### To create a new Scope of Work Template, click the Create Template button in the top right. To edit or delete existing ones, click the pencil or trashcan icon next to the relevant SOW.
{% endstep %}
{% step %}
#### Here you can add any content you want as standard SOW text. You can add conditional elements directly in the documentation as well, as you can see in the template below. The main elements you can add in (type, background context, deliverables, milestones and resources). Best practice is to start writing your template, then have KIT insert the relevant conditional text into the flow.
{% endstep %}
{% step %}
**This template is now available for your organization to use when creating SOW's.**
{% endstep %}
{% endstepper %}
---
# 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://docs.fairmarkit.com/buyers/requests-intake-buyers/generate-a-scope-of-work-sow/managing-sow-templates.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.
