How Track works

A connected loop, from brief to learning.

Track organizes the operating sequence so the work can move fast without losing its history: define the work, execute it, review it, and learn from the outcome.

01 / ADMIN

Create the operating structure

Start with a Client. Add a Project. Define a Target with a search string, daily goal, criteria groups, status, and assigned sourcers.

02 / SOURCING

Execute against the brief

Sourcers work assigned targets in the extension and record profile decisions with the context needed for review.

03 / QA

Validate the signal

QA reviewers work through pending decisions and use the same criteria to approve, reject, or return a decision.

04 / ADMIN

Improve the next cycle

Admin and operations use outcomes, assignments, duplicates, and audit history to refine the next project and target.

1ClientOWNER
2ProjectCONTEXT
3Target + criteriaBRIEF
4Sourcing decisionSIGNAL
5QA outcomeTRUST

Why the sequence matters

The handoff is where quality is won or lost.

Track keeps the context visible at each transition. That reduces the gap between what the client needs, what sourcing finds, what QA verifies, and what Admin can explain later.