# Define the work and the result you expect

Canonical: https://savrn.com/cloud/work-orders

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

A Work Order gives a research request an explicit scope: the sources it may use, the deliverable it should produce and the resource allowance within which it should operate. SAVRN Cloud’s preview demonstrates that workflow through a sample artifact and review. Connected research execution is Coming soon.


## Write a request that can be reviewed

In the preview, create a Work Order with a title, source collection, expected deliverable and maximum sample credits. A useful request describes an assessable output, such as a comparison grounded in a defined set of materials. That specificity helps a reviewer understand what they are approving and gives the final recipient a basis for acceptance.

## Authorize the scope before execution

Submit the local Work Order for approval, then review its scope and budget in the approval queue. Approval moves it to a ready state; it does not produce the deliverable. The separate Run workflow action generates a sample artifact and usage record. All of these effects remain within the browser demonstration and make no external research or model calls.

## Distinguish completion from acceptance

Inspect the simulated artifact after execution. Accept the deliverable when it satisfies the stated request, or return it for revision with an explanation. This is a different decision from approving the original budget or observing that execution completed. Recording the distinction helps teams understand whether work reached a useful business or research outcome.

## Keep revisions within an explicit agreement

If the task needs materially different sources or an expanded objective, a new scope should be reviewed rather than hidden in an execution retry. The planned connected workflow needs durable artifacts, source provenance, safe recovery and reliable resource settlement. A workflow should not report success solely because an internal task finished when the promised deliverable is missing.

## What you can explore today

Create, approve and run local Work Orders, then accept or return their labeled sample artifacts.

## Before this service launches

Connected Work Orders require approved execution tools, durable deliverables, source handling, authorization and effect-based recovery.

## The customer outcome

The intended outcome is an accepted research deliverable whose authorized scope, supporting sources, execution record and review decision remain connected.

## Related documentation

- [First research Work Order](https://savrn.com/cloud/docs/start-first-work-order)
- [Agents, sessions and recovery](https://savrn.com/cloud/docs/agents-overview-recovery)
- [Governed literature-review walkthrough](https://savrn.com/cloud/docs/guides-literature-review)
- [Explore Work Orders](https://savrn.com/cloud/console/#/work-orders): Follow a scoped sample request through deliverable review.