Goals and the Work page
A goal is an outcome Chat plans into tasks for your team. The Work page lists every task, open or done, with who has it, how far it got and what it cost.
On this page
Goals: from a sentence to a plan#
Use a goal when the work needs several people or steps, such as “Prepare the Q4 price list for our top 20 customers”. For one piece of work by one person, give a task instead.
- 1
Describe the goal in Chat
Say what you want done and roughly what it may spend, in credits while they pay. If you give no budget, Chat asks for one.
- 2
Confirm the goal
Chat proposes it with an AI spend cap: the most Royak may spend on AI and app calls for this goal. It’s not a business budget. Edit changes the wording or the cap; Confirm and plan asks the planner for a plan. Nothing has started yet.
- 3
Read the plan
The plan panel shows the Estimated cost against the budget left, the Departments involved, the numbered Steps with who leads each and what it produces, and Done when. It also says when a step needs an app that isn’t connected or granted yet, or when the right department is busy.
- 4
Approve and start
Approve and start hands each step to its leader’s team. Change plan lets you ask for changes in words. You can also Step-test this plan first: its parts run one at a time and stop at every handoff, within a test budget, and nothing is sent to your apps.
Approve and start stays disabled while the plan costs more than the budget left, needs apps that aren’t ready, or is led by employees Chat proposed that you haven’t activated yet. The panel says which.
Following a goal#
A goal is Planning, Plan waiting for you, Needs you, Running, Completed, Failed or Canceled. While it runs, the plan panel shows each part’s progress, how often review returned it, its cost, and “Spent $x of $y”. See the work in the office shows who is on it.
When it ends, the panel shows a Report built from Royak’s records, not the employees’ own accounts: Who did what, Cost against the budget and the estimate, and Limitations, such as a part that failed or work you accepted as it was.
The Work page#
Work has three tabs: Open, Routines and Done. Open groups tasks as Waiting for you (a question, an approval, a review decision, a plan to accept), In progress and Queued; Done as Done, Failed and Canceled. Select a task to open its record beside the list.
| Column | Shows |
|---|---|
| ID | The task’s short ID, such as KS-142. Type it anywhere in Chat to link it. |
| Task | The title, and “Team task”, “Part T2 of …” or “Routine” when it is one. |
| Assignee | Who does it, and their department. |
| Status | The same words and glyphs as the Office. |
| Progress | “Step 3 · Searching knowledge”, a team’s “2 of 3 parts”, “After KS-140” while it waits for another task, or the steps it took. |
| Cost | What every run of the task cost in AI calls so far. |
| Updated | When it last changed. |
Filter tasks (/) matches titles and assignees; type a whole short ID and press Enter to open that task. Any department and Anyone narrow the list, and Group by sorts it by status, assignee or department. The list shows the latest 100 tasks; Show older tasks loads more. New task (C) opens the New task sheet.
Task statuses#
| Status | Means |
|---|---|
| Queued | Waiting for a free slot to start. |
| Waiting | Starts once the task it depends on is done. |
| Working | Running now. |
| Input needed | Asked you a question. |
| Approval needed | Waits for your approval of an action or a limit raise. |
| Not making progress | Stopped because its last steps added nothing new; needs your guidance. |
| Needs a key | This month’s credits are used up and no key of yours pays. |
| Plan waits for you | A team’s plan waits for you to accept it. |
| Needs decision | Review kept returning the work; you decide. |
| Blocked | A task it depends on failed, or it waits while an update to Royak rolls out. |
| Paused / Pause requested | Held by a pause; continues from the same step. |
| Done, Failed, Canceled | How it ended. |
Seeing how work connects#
Switch the Work toolbar from List to Dependencies for a graph of tasks that start after others, and of team tasks with their parts. Arrows point from the earlier work; select a node to open that task. Drag to pan, scroll to zoom, and Show everything to fit it all. A note under it says how many tasks have no dependencies.
Two more graphs live elsewhere. Knowledge › Graph shows your sources, the tasks that read them and the deliverables built on them, and warns when a deliverable rests on an older version of a source (see Sources). People › Org chart shows who reports to whom.
Finding a task#
Press ⌘K (Ctrl+K on Windows) on any company page to search pages, people, departments, recent tasks, sources and artifacts. A short ID such as KS-142 in any chat message links to its task, and links from the Inbox open the task on Work.
Questions#
Goal or task: which should I use?
A task for one piece of work you can describe in a brief. A goal when you want Chat to plan the steps and who does them.
Can a goal spend more than its cap?
Not without you. Every call is reserved against the cap before it is made; when the cap is reached, the task waits and asks you to raise it. Your monthly limits still apply.
Why is a task Queued for a while?
Your plan runs a set number of tasks at once. Queued work starts as soon as a slot is free.
Where do routines show?
Under Routines on Work. Each run of a routine is an ordinary task in Open and Done.