How to track freelancer deliverables without chasing anyone

The short answer

Make each freelance deliverable its own item on the client's project, with a written definition of done, an owner, a due date with a time zone, an interim check, and a status. Ask the freelancer to deliver into that item, not by email or a private link. Review against the brief, record each round's notes on the same item, and close it only when the file is approved and stored. Then record the cost on the project so the deliverable has a price as well as a date.

What counts as a deliverable

A deliverable is something you can hand over and check: a model, a set of textures, a shot at blocking, a comp, an edit, a set of icons. "Help with the project" is not a deliverable, and "animation" is too big to be one.

Write each deliverable in one or two lines that answer three questions: what goes in, what comes out, and by when. If you cannot write it that short, split it. Five small deliverables with dates are easier to track than one large one with a date three weeks away, because the small ones show progress and the large one shows nothing until it is late.

The fields every deliverable needs

You do not need a special tool for this. A list, a spreadsheet or a project board will do, as long as every deliverable has the same fields:

The definition of done is the field most studios skip, and it is the one that prevents most arguments. "Done" for a 3D model can mean modelled, or modelled and textured, or modelled, textured, rigged and tested in the scene. Write which.

Statuses that mean something

Five statuses cover almost every studio: not started, in progress, in review (with you), changes requested (back with them), approved. Two rules make them useful.

First, the status has one owner at a time. "In review" means you owe the next move. "Changes requested" means the freelancer does. When you scan the list, you can see who is holding each item.

Second, only you move an item to approved. A freelancer can mark their work as delivered, but approved means it passed your review against the brief and, where needed, the client's.

Interim checks catch problems early

The most useful date on a deliverable is not the deadline. It is the interim check: a clay render after the first day, a blocking pass halfway through, a rough selection before the full edit. A problem found at the interim check costs an hour. The same problem found on the deadline costs the deadline.

Put the interim check on the item with its own date, and treat a missed check as an early warning. A freelancer who misses the interim check on Tuesday is unlikely to hit Thursday, and you want to know that on Tuesday.

One place for the files

Ask every freelancer to deliver into the deliverable, not by email, a chat message or a link to their own cloud folder. Personal links expire, get cleaned up or end up in an inbox nobody else can open. If they do send a link, download the files the same day and store them with the deliverable.

Agree a naming rule with the round in the name: sofa_r1.fbx, sofa_r2.fbx. The name tells you which round you are looking at, and the folder holds the history without anyone having to explain it.

Reviewing a delivery

Review against the brief and the definition of done, not against what the client said on a call the freelancer was not on. Write your notes on the deliverable as a numbered list, one change per line. Mark which notes are yours and which are the client's, so the freelancer has one list instead of two. Vague notes ("make it pop") are not ready for the list; turn them into something specific first.

Count the rounds. If the agreement includes two rounds of changes and you are about to send a third, either the brief was unclear (your cost) or the client changed it (the client's cost). Decide which before you send the notes.

A weekly check across all projects

Once a week, look at every open freelance deliverable across all projects in one view. Ask four questions of each:

1. Is it on track for its due date?
2. Who is holding it right now?
3. Has it missed an interim check?
4. Is anything waiting on the client before the freelancer can continue?

The last question matters most. Freelancers often wait without saying so, and every day of waiting is a day off the schedule.

Money on the same record

Record the agreed fee on the deliverable or on the client's project as soon as the work is agreed, in the freelancer's currency. When the deliverable is approved, ask for their invoice and pay on the terms you agreed. Tracking cost next to delivery tells you two things: what each job really made, and which freelancers deliver on time and on brief. The freelancer onboarding checklist covers contracts, NDAs and access, and managing freelancers in a 3D studio covers briefs and payment.

Doing this in OIO

In OIO each freelance deliverable is a ticket on the client's project, with a due date, an assignee, a status and a checklist for the definition of done. You send the freelancer a link to that ticket. They open it in a browser with no account and no seat, read the brief and the checklist, download the files, upload their work, comment and set the ticket to in progress or done. They see only their ticket.

The kanban and the timeline show every ticket's status across the project, so you can see who is holding what. Each round's notes go on the ticket. On images, you and the client pin numbered notes on the delivered file; on video, comments sit at the second. The freelancer's fee goes on the project as a cost in their currency, next to the quote and the invoice. OIO does not receive or pay freelancer invoices, and has no time tracker; hours are entered on the ticket.

Questions