> For the complete documentation index, see [llms.txt](https://help.tahua.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.tahua.io/knowledge-base/administrator-help-guides/contracts/contract-templates/contract-signatories/funder-verifier-contract.md).

# Funder - Verifier Contract

<div align="left"><figure><img src="/files/3Lzm8nvfu5BjhHjTF2GW" alt="" width="168"><figcaption></figcaption></figure></div>

In order for a Verifier/Institution to be able to sign a Contract, you need to ensure they have been added to the Application (which you can do by clicking into the Applications main page).

<div align="left"><figure><img src="/files/n51XeLDnjHzygJcZwTI6" alt="" width="337"><figcaption></figcaption></figure></div>

The next step appears on the Contract "Details" page - here you need to ensure you tick "This Contract is with the Institution only".<br>

<figure><img src="/files/AXKedrtZuZTh2XWJWImE" alt=""><figcaption></figcaption></figure>

When you are setting up your Contract template, you can then add in the relevant Signature Blocks by using "personalisations".

<div align="left"><figure><img src="/files/qFhjztxTHMqhh8sgCGrz" alt="" width="250"><figcaption></figcaption></figure></div>

The Contract workflow will also request that you select what Signatories you wish to sign the Contract. It is these signatures that will then be inputted into the signed Contract. You can select more than one signatory, if appropriate, to sign the Contract (e.g. multiple Admin signatories from the Funder and/or Verifier/Institution).

<div align="left"><figure><img src="/files/woUYnbSqe23RTHagu5UR" alt="" width="279"><figcaption></figcaption></figure></div>

This results in the Contract looking like this. The electronic [Signing a Contract](/knowledge-base/administrator-help-guides/contracts/signing-a-contract.md) process then ensues.

<div align="left"><figure><img src="/files/AtvoYmtPLxBhFmj4V7Md" alt="" width="375"><figcaption></figcaption></figure></div>


---

# 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://help.tahua.io/knowledge-base/administrator-help-guides/contracts/contract-templates/contract-signatories/funder-verifier-contract.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.