# First research Work Order

Canonical: https://savrn.com/cloud/docs/start-first-work-order

SAVRN Cloud · Coming soon. Public documentation and a browser simulation are available; connected services are not yet available.

A SAVRN Cloud Work Order gives a research task an explicit deliverable, source boundary and spending ceiling. This walkthrough follows a fictional task through approval, simulated execution and review, keeping permission to run separate from acceptance of the result.

**SAVRN Cloud · Coming soon · Public preview · Browser-local simulation · No live compute or payments**

## Prepare a small task

Select a project in [Projects](https://savrn.com/cloud/console/#/projects), then open [Work Orders](https://savrn.com/cloud/console/#/work-orders). Use a short invented research task, such as comparing three fictional laboratory scheduling policies. Describe the intended deliverable and its acceptance criteria. Keep sources public or synthetic.

Choose **New work order**. Enter a title, select the **Approved source collection**, describe the **Expected deliverable** and set **Maximum sample credits**. Choose **Submit for approval**. The record starts **Awaiting approval**. In [Approvals](https://savrn.com/cloud/console/#/approvals), inspect the request and choose **Approve scope and budget** to make it ready. An approval is permission for the next step; it is not the deliverable.

## Complete the walkthrough

Choose **Run workflow** from the ready Work Order. Inspect its status, generated result and associated activity. Compare the result with the original acceptance criteria. Choose **Accept deliverable** or **Return for revision**. A return requires a note and sets **Needs revision**; create a revised Work Order for a new approved scope. Check [Usage](https://savrn.com/cloud/console/#/usage) for the local accounting representation.

The output demonstrates workflow structure. It is not evidence of research, retrieval or contact with external sources.

## Before connected services launch

A real Work Order needs authenticated ownership, authorized sources, enforceable spending limits, durable execution and retained artifacts. Source citations must resolve to material actually used. Resource charges and deliverable acceptance need separate policies: delayed review must not leave accounting indefinitely unresolved. Production approval must be enforced server-side and tied to the exact task revision.