Three sources, counted separately: a workbook that records payments, a bucket that records evaluations, and a bucket that records finalised work. They overlap, so nothing here is added across sources.
Accepted tasks
-
Distinct tasks in the bucket, cross-cohort repeats removed
Client accepted
-
-
Finalisation v2
-
-
Paid out
-
Recorded in the workbook Paid Out tab
Pending tasks
-
-
Active trainers
-
-
Payout exposure
Paid against still-owed, at $300 a task. Both figures come from the workbook, never from the bucket.
Outstanding-
-
Where the work sits
Loading the bucket scan...
Current evaluations
Latest evaluation of each task family in the bucket.
Company and Computer bench
Split by the roster team of the task owner. Work with no resolved owner sits in neither bench.
Money
Payouts
Accepted work comes from the workbook task list, deduplicated. Payments come from the Paid Out tab and the payment tracker. The bucket is not used here.
Loading the payout ledger...
By trainer
One row per person. Pending is what they are owed now, not what they have earned in total.
Person
Team
Manager
Accepted
Paid
Paid $
Pending
Pending $
24h
Task ledger
Every task in the workbook task list, one row each. Rows repeating a task for the same trainer are folded in and reported as extra ledger rows.
Loading...
Task
Trainer
Type
Valid
Payment
CJ
Rows
Teams
Delivery
Team and manager rollups from the roster, and the daily mining plan against what was actually delivered.
Teams and managers
Grouped by roster team. Accepted and pending carry the Payouts definitions.
Plan against actual
Workbook-wide daily mining commitment. Not person-level, and not affected by filters on other tabs.
Evaluations
Pipeline
Read from the trainer evaluation ledgers in GCS. Current shows the latest attempt per task family; history counts every attempt, so the two must never be added.
Loading the GCS export...
Status of current work
Done is not an acceptance. Accepted and Rejected each require an explicit verdict on the submission.
Start date must be on or before end date.
Date
Task
Trainer
Type
Domain
Status
Delivered work
Finalisation
A read-only scan of every finalisation cohort in the bucket. One task can be finalised into several cohorts, so folders and tasks are counted separately.