Public Demo
You are welcome to explore this solution. Prior to official go-live, you may use it freely — however, your data may be lost in future updates. No guarantees or liability are given. Use at your own discretion.

Working with requests

Capture the work that needs scheduling — create requests, nest them into containers, and manage them as a tree or a list.

Published

The Requests page (“Organize tasks and groups and track their schedules.”) is where work enters Orkyo. A request records what needs to happen, what it requires, and — once scheduled — when and where it happens.

Two views

Switch with the View mode toggle:

  • Tree view — requests in their parent/child hierarchy. Expand all / Collapse all manage large trees, and a search box narrows to matching requests (their parents stay visible so you keep your bearings).
  • List view — a flat list; better for scanning and bulk review. Its column headers sort and filter — by kind, status, schedule or duration — like every list in Orkyo (see Sorting and filtering lists).

The same requests appear in both; pick whichever fits the moment.

Creating a request

Choose New Request (an empty page offers Create Request directly). The form’s Details tab gathers everything about the request:

  • Basic Information — name, description, and an icon.
  • Schedule (Optional) — a start and end, if you already know them. Leaving it empty keeps the request in the unscheduled backlog for the Utilization board to place later.
  • Requirements — the criteria a hosting resource must satisfy, using the vocabulary from capability matching.
  • Resources — what kind of thing the request needs, and which one. Needs lists the resource types (Spaces, Tools, and any type you have defined); ticking one adds a picker for it below. A request holds one resource per type, so a job needing a room and a van names both.
  • People — who is needed, on the same tab beneath the pickers. People work differently: a request carries as many as the work takes, so they are added here rather than through Needs. Orkyo validates assignments as you edit and reports issues by name (“No issues found” when clean).
  • Scheduling Constraints (Optional) — “Specify time windows when this request can be scheduled”: an Earliest Start and/or Latest End that manual and auto-scheduling must respect.

Save with Create Request; editing an existing one ends with Update Request.

Containers and child requests

Requests nest. Use the Children tab — or Add Child Request — to break work down; the parent becomes a Container whose children carry the actual schedules.

A container can declare a Boundary Window (Optional): “Children must start and finish within this window.” The form also shows the container’s Derived Schedule (read-only) — the envelope of its children’s schedules — so the parent always reflects reality.

Use containers for projects, recurring programs, or any batch of related work that should be reviewed — and time-boxed — as one unit.

Validation, up front

The form validates continuously against the same rules the scheduler enforces: resource type mismatches, missing capabilities, overbooking, absences, site mismatches, and more, each named explicitly (e.g. Required capability missing, Overlaps with a holiday). Fixing issues at capture time is far cheaper than firefighting conflicts after placement.

From capture to schedule

Captured requests appear in the Utilization board’s Requests panel, ready to drag into place — or to hand to auto-scheduling in bulk. For the full first pass, follow Create your first schedule.