> For the complete documentation index, see [llms.txt](https://support.pipefile.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://support.pipefile.com/requests/open-ended-requests.md).

# Open-ended requests

Send a single secure upload link with no checklist, for when you don't know exactly what the recipient will send.

An open-ended request is a secure upload link without a checklist. The recipient uploads whatever they have, as many times as they need, instead of working through a list item by item.

Use one when:

* You don't know exactly which documents the recipient has.
* A recipient needs a secure place to send documents on an ongoing basis.
* You only need one thing and a checklist would be overkill.

If you know what you need, a [checklist](/requests/checklists-and-sections.md) is usually better. It tells the recipient exactly what to send, tracks each item separately, and lets you review item by item.

## Create an open-ended request

{% stepper %}
{% step %}

### Start a request

Click **New Request** and add your recipients, reminders and tags as usual. See [Create and send a request](/requests/create-and-send-a-request.md).
{% endstep %}

{% step %}

### Switch to Open-Ended

Above the checklist, click **Open-Ended**. The checklist is replaced by a **Message** box.
{% endstep %}

{% step %}

### Write your instructions

In **Message - Optional**, tell the recipient what to send. To share files with them, such as a form to fill in or an engagement letter, click **Attach Files**.
{% endstep %}

{% step %}

### Send

Click **Next**, add a **Subject**, and click **Send Request**.
{% endstep %}
{% endstepper %}

{% hint style="warning" %}
Switching between **Checklist** and **Open-Ended** discards what you entered in the other mode when you send. A request is one or the other.
{% endhint %}

## How it behaves

* **Uploads**: the recipient can come back to the link and upload more at any time until you complete or archive the request.
* **Status**: the first upload moves the request from **Sent** to **Responded**. Later uploads keep it there and still notify you.
* **Reminders**: they stop after the first upload, since the request has been responded to.
* **Expiration**: an open-ended request only expires if nothing has been uploaded by the expiration date. Once it's **Responded**, the link stays open until you complete or archive it.
* **Comments**: you and your recipient can exchange comments on the request. Open them from the **Comments** icon on the request page.

## Ongoing collection

For a link a client can use month after month, send an open-ended request and leave it open. When you're done, click **Mark completed** or archive it to close the link. See [Expiration, completion and reopening](/requests/expiration-and-reopening.md).

To take uploads from people you haven't sent anything to, use a [lead form](/intake/lead-forms.md) or your [profile page](/intake/profile-page.md) instead.

## Related

* [Build your checklist](/requests/checklists-and-sections.md)
* [Upload documents to a request](/for-your-clients/upload-documents.md)


---

# 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://support.pipefile.com/requests/open-ended-requests.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.