> ## Documentation Index
> Fetch the complete documentation index at: https://docs.oncanary.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Create and review Requests

> Submit a maintenance need, route it to the right reviewers, and create its linked work order.

Requesters use **New Request** to tell maintenance what needs attention. Admins and routed team members review Pending Requests and decide whether to create work.

## Submit a Request from an account

1. Open **Requests**.
2. Select **New Request**.
3. Enter the required **Request Title**.
4. Complete the fields shown by your organization's Request preferences. These can include **Description**, **Location**, **Asset**, **Priority**, **Pictures**, and **Files**.
5. Add **Contact Information**.
6. Choose **Assign To** when approval routing is enabled.
7. Select **Submit Request**.

An organization can make Description, Location, Asset, Priority, or attachments hidden, optional, or required. Approval routing can offer admins, selected teams, and **Other**, and it can require a selection.

A Request supports up to 20 total attachments, with a 25 MB limit for each attachment. Pictures and files keep their original role on the Request.

## Update a Pending Request

Open your Request and select **Edit Request** to correct its details while it is Pending. Select **Cancel Request** to stop a Pending Request; Canary requires an explanation and keeps it visible on the record.

**Duplicate** creates a new Request from an eligible Request you own. Use it when the same need occurs again and review every copied value before submitting.

## Review a Request

Admins can review all Pending Requests. A member can review a Request assigned to one of their teams.

### Approve and create work

1. Open the Pending Request.
2. Select **Approve Request**.
3. Review the work-order form. Canary prefills available Request context, including title, description, contact, priority, location, asset, and custom values.
4. Optionally apply a Work Order Template or add a Procedure.
5. Set the work-order status, assignment, dates, and any other job-specific fields.
6. Select **Create**.

Canary creates the work order, links it to the Request, and changes the Request to **Approved** in one committed operation. A Request priority of **None** becomes **Medium** on the work order unless the reviewer chooses another priority.

The Request detail then shows **Linked Work Order** to viewers who also have access to that work order.

### Decline a Request

1. Open the Pending Request.
2. Select **Decline Request**.
3. Enter a clear **Reason**.
4. Select **Decline Request** to confirm.

The requester can see the decline reason. A Declined Request stays in Request history and cannot enter the approval flow; duplicate it when revised work should receive a new review.

## Follow completion

The linked work order drives the final Request state:

* Work order becomes Done → Request becomes Completed.
* Done work order is reopened → Request returns to Approved.

Other work-order status changes leave the approved Request connected to the same work order.