> For the complete documentation index, see [llms.txt](https://docs.silkline.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.silkline.ai/requests/managing-a-request.md).

# Managing a Request

Triage, edit, and progress an open request — adjust the hot flag, manage items, send RFQs, and convert selected quotes into purchase orders

After clicking into a Request, buyers can manage and edit the request.

<figure><img src="https://2684497859-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FwPsevXC0g5kNMF7GTyPN%2Fuploads%2Fgit-blob-073d164c2845750ec9b73131d4a6c5401505a6ee%2FScreenshot%202025-02-22%20at%2012.06.12%E2%80%AFPM.png?alt=media" alt=""><figcaption><p>Screenshot of <strong>Request</strong> page</p></figcaption></figure>

## Summary

The Summary section holds the request's core details. Every field there is edited in place — click it, change the value, and the change saves on its own. There is no separate save button.

<table><thead><tr><th width="191">Field</th><th>Description</th></tr></thead><tbody><tr><td>Description</td><td>The short description shown at the top of the request. Click it to edit.</td></tr><tr><td>Requester</td><td>The team member the request is for.</td></tr><tr><td>Buyer</td><td>The team member responsible for sourcing the request. Only members who can edit orders can be selected.</td></tr><tr><td>Location</td><td>Where the parts should be delivered. Shared with suppliers, and used as the ship-to location of orders created from the request. Required when your organization turns on <a href="https://docs.silkline.ai/profile-and-settings/organization-settings/locations.md#require-a-location-on-requests">Require a location on requests</a>.</td></tr><tr><td>Need date</td><td>When the parts are needed. Shared with suppliers. Leave blank to ask suppliers for an ASAP lead time on hot requests, or a standard lead time otherwise.</td></tr><tr><td>Suppliers</td><td>The suppliers to quote. Leave blank if unknown; prohibited suppliers are excluded from tag-based selections.</td></tr><tr><td>Tags</td><td>Labels used to organize requests.</td></tr></tbody></table>

Any custom fields your organization has configured for requests appear in this section too.

Fields your organization has marked **Required** must keep a value here, not only when the request is created. Clearing one is not saved — the field shows an error until a value is entered. See [Configurable Fields](https://docs.silkline.ai/profile-and-settings/organization-settings/configurable-fields.md).

## Request items

The **Items** table lists every line on the request. When a part appears on more than one line, such as a delivery schedule with a quantity for each need date, the table groups those lines under one item, with each line's quantity, need date, and awarded quote on its own row. Lines group only when their item details match; a line with a different description, supplier part number, quality clauses, or pedigree stays separate. Selecting items to split shows one row per line.

## Editing request items

In **Edit Request Items**, entering a **Supplier PN** fills an empty **Item** when the request has exactly one supplier and the part number maps to one item for that supplier. Selecting an Inventory item fills an empty Supplier PN when its mappings for that supplier agree on one part number.

Existing values stay unchanged. Requests with no suppliers, multiple suppliers, or ambiguous mappings need manual item selection. Save the form to keep the linked items and part numbers.

## Actions

The actions bar the top right allows users to take key actions for a request.

<figure><img src="https://2684497859-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FwPsevXC0g5kNMF7GTyPN%2Fuploads%2Fgit-blob-5235dbc4bd913c18e339fe1a45c0620016fcb1ef%2FScreenshot%202025-02-22%20at%2012.29.52%E2%80%AFPM.png?alt=media" alt="" width="563"><figcaption></figcaption></figure>

### Flag requests as hot

Requesters can mark urgency during submission. After submission, requesters cannot change urgency.

Buyers can still use the flag toggle next to the request state dropdown to adjust the hot flag during triage and request management.

**When the hot toggle is on:**

* The request shows as "hot" on the RFQ sent to suppliers; if no need date is specified, the supplier is asked to quote an "ASAP" lead time.
* A red flag icon appears next to the request number on the Requests table to indicate priority.

Request assignment notifications also clearly flag hot requests (for example, with a hot indicator in the subject and email body).

### About this request

Click the info icon (**About this Request**) next to the request state to see the objects related to the request, and jump to any of them:

* **Related Demand** — demand lines covered by the request's items. Shown only when the request covers demand.
* **Related Quotes** — the quotes linked to the request. Use **Link Quote** to link an existing quote.
* **Related Orders** — the orders linked to the request. Use **Link Order** to link an existing order.

<div align="left"><figure><img src="https://2684497859-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FwPsevXC0g5kNMF7GTyPN%2Fuploads%2Fgit-blob-e074b5fc90d72e243899003e12b262c833a93678%2Fabout-this-request.png?alt=media" alt="About this Request popover listing related demand, quotes, and orders" width="290"><figcaption></figcaption></figure></div>

### Request status

The state of the request can be changed using the dropdown on the top right of the page. Requests can have the following states:

* **Open** – request requires action
* **Complete** – request has been completed and no further action is required
* **On Hold** – request is blocked (e.g., design questions for the engineer)
* **Canceled** – request has been cancelled and no further action is required

{% hint style="info" %}
If a buyer is blocked from making progress on a request, we recommend changing the status to "On Hold". In the future, this will pause the clock, ensuring that buyer metrics are not impacted when input is needed from the requester.
{% endhint %}

### Follow request

Subscribes to following the request for the logged in user. Followed requests appear in the **Followed Requests** widget on your Home Page. When an order is created from the request, request followers automatically become followers of the order.

{% hint style="info" %}
The **buyer** and **requester** for a request are automatically added as followers.
{% endhint %}

{% hint style="info" %}
Note: Request followers do not receive email notifications at this time.
{% endhint %}

### Share a request

The **Share** button opens a sidebar. Its **Share** tab lists the external users a Request has been shared with as an RFQ. To share a request with new users as an RFQ, click "Send to Suppliers".

The sidebar's **Followers** tab lets you add other users as followers of the request. Users who can edit the request can remove a follower by clicking the **x** next to their name. Anyone can stop following a request with the follow toggle at the top of the sidebar.

RFQs also support a copyable share link — see [Copy share link](https://docs.silkline.ai/requests/rfqs.md#copy-share-link).

### Send to Suppliers

This button opens a sidebar to [send RFQs to suppliers](https://docs.silkline.ai/requests/rfqs.md).

## Files

The **Files** section holds the files shared with suppliers on RFQs. Click the download icon (**Download all**) to download them as a zip. The zip contains only the files attached to this request — not files stored on its parts, on quotes, or on BOM components — so it is not a certification packet for the parts or their subcomponents.

Click the folder icon (**Browse and add part files**) to copy files already stored on each requested item's part onto the request.

## Internal Files

The **Internal Files** section holds files visible only to your team — they are **never** sent to suppliers or exposed on RFQs and share links. Use it for internal-only material like engineering notes, prior quotes, or planning docs.

Click **Browse and add files** to upload or pick existing files. Files added under **Files** (not Internal Files) are still shared with suppliers via RFQs. Internal Files has its own **Download all** zip.

## Workflow tracker

The request status is **automatically determined** based on the request state and the progress of the request. Requests can have the following statuses:

* **New** – A request has been submitted, but has not yet been assigned to a Buyer
* **Assigned** – A request has been assigned to a buyer
* **In Work** – A buyer has started working on the request
* **Out for Quote** – An RFQ has been sent to suppliers
* **Review** – Quotes have been attached to the request
* **Complete** – The request has been marked as complete

## Activity feed

The activity feed shows a log of notes, related emails, and key events for a request, including threads for each RFQ sent. The activity feed displays automatically on large screens or can be launched from the **Actions** bar when viewing Silkline from a smaller screen. Users can search the contents of the activity feed to find items quickly.

RFQ send events show when an RFQ has been viewed and when suppliers have downloaded files.

<div align="center"><figure><img src="https://2684497859-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FwPsevXC0g5kNMF7GTyPN%2Fuploads%2Fgit-blob-8edc7c39966c4fa51448cf9480402c0fc09b1b55%2FScreenshot%202025-02-22%20at%2012.37.32%E2%80%AFPM.png?alt=media" alt="" width="375"><figcaption><p>Request activity feed</p></figcaption></figure></div>

## Request for Quotes

View RFQs in either a table or board layout. In the board layout, you can drag RFQ cads from one column to another to change the status of that RFQ.

<figure><img src="https://2684497859-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FwPsevXC0g5kNMF7GTyPN%2Fuploads%2Fgit-blob-841822d0b0bd1129b4b518045efbc1a1b10e9c68%2FScreenshot%202025-02-22%20at%2012.41.10%E2%80%AFPM.png?alt=media" alt=""><figcaption><p>Screenshot of <strong>Request for Quotes</strong> section</p></figcaption></figure>

## Quotes

View quotes linked to a request, create a new quote, or link an existing quote. You can also drag and drop a quote into the "Create Quote" card to upload a quote and link it to that request. If a supplier emailed a quote only to you, forward it to that RFQ's inbox to create a draft quote linked to the request and RFQ — see [RFQ inbox](https://docs.silkline.ai/requests/rfqs.md#rfq-inbox).

Click "Cut PO" to convert the quote to a PO. Click the menu of additional options to edit, unlink, or delete a quote. Unlinking a request keeps the quotes in Silkline but removes them from the request. Deleting a quote removes the quote entirely from Silkline.

<figure><img src="https://2684497859-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FwPsevXC0g5kNMF7GTyPN%2Fuploads%2Fgit-blob-aa60048b934158a3aa59710b786be7bb08d5361c%2FScreenshot%202025-02-22%20at%2012.43.52%E2%80%AFPM.png?alt=media" alt=""><figcaption><p>Screenshot of <strong>Quotes</strong> section</p></figcaption></figure>

## Linking Orders

When an order is created from a request, the request, quote, and order are all linked together. Orders can also be manually linked to a Request using the "Link order" button below the phase tracker.
