The Projects dashboard, and starting your first project
What the four counters mean, how the project table is organised, and the two-field drawer that turns a folder of files into a run.
Four counters, read as two questions
The header carries four cards. Read them as two questions rather than four facts: how much have we loaded, and how much of it has actually been priced. A library that grows faster than the run count is normal early on and a problem later — it means customer files are landing but nobody is rating them.
- Projects — Every project in the workspace, run or not.
- Total runs — Rating runs across all projects, all time.
- Awaiting — Runs paused on a question only you can answer.
- Golden ready — Runs finished and cleared for delivery.
The project table
Each row is one project: an initials chip, the name, its run count, its file count, and when it last moved. The table is your entry point to everything else in the product — you do not rate from the dashboard, you open a project and rate inside it.
The header cards are sums of the table
When a run completes while you are watching, two numbers move together: the project's own run count in its row, and Total runs in the header. That coupling is worth internalising, because it tells you how to react when they disagree — the header is a sum of the rows, so a header that contradicts the table below it is stale rather than authoritative. Reload before investigating.
Reading the gap between files and runs
Compare the run counts down the table against the file counts beside them. A workspace where a handful of projects own every run, and the rest hold files nobody has priced, is telling you the upload half of the workflow is working and the rating half has not caught up. The fix is not more files — it is opening the largest untouched project and running it.
Awaiting is a queue, not a status
Awaiting counts runs that stopped to ask you something, and it is the same fact as the approval banner above the table. Treat it as work assigned to you: a run sitting in Awaiting is not slow, it is blocked, and nothing downstream of it will move until the question is answered.
Starting a project is a name and a drag
New Project opens a drawer with exactly two things to do: type a name, and add the files. There is no schema to declare, no column mapping to fill in, no template to choose — the agent reads the sheets and works out their shape during the run. Files are saved to the project as soon as they are added, so a half-finished project is not a lost one.
- Add Files — Individual spreadsheets, documents, or .msg email exports.
- Add Folder — The whole customer folder in one go.
- General instructions — Optional. Leave blank to run the files as they are.
Save, or Create & Run
Both buttons stay disabled until the project has a name and at least one file, which is the only validation in the drawer. Save parks the project in the library for later; Create & Run creates it and immediately starts a rating run. Choose Save while you are still collecting files, and Create & Run when the folder is complete — a run against a partial file set produces a rate sheet you will have to redo.
Where a new project lands
On create, the Projects counter increments and the new project appears at the top of the table stamped "just now" with a zero run count. The table sorts by activity, so a new project is always the first row until something else moves — a convenient default and a poor filing system. Name projects for the customer, not for the week you made them.
One habit worth forming in this drawer
Check that the name you typed and the files you dragged belong to the same customer before you confirm. The agent will rate whatever is in the folder, and it has no way to know that a file came from somewhere else — so a mismatch survives all the way into a deliverable. The drawer is the last place it is cheap to fix.
Ready to build your own?
Start free and ship your first app in minutes — or have us set it up with you.
More guides in Getting Started
More resources