Define deliverables smaller than the whole contract
Track each model, animation, UI set, audio batch or code task with a stable ID. Give it a due date, owner and acceptance criteria that can actually be checked.
Separate status from acceptance
“Submitted” is not “Accepted.” Keep a distinct review state so rework, rejection and final acceptance stay visible.
Track revision limits and scope changes
When revisions exceed the planned limit or a new requirement appears, record it as a scope decision instead of silently treating it as another small edit.
Make final handoff explicit
Record whether final files arrived, whether source files were expected and received, where backups live, and which agreement/rights reference applies. List important third-party dependencies rather than discovering them at release time.
Keep invoice status separate
Payment administration and quality acceptance are related but not identical. Track invoice reference, amount, due date and status without putting banking credentials into the project workbook.
Project-management guidance only. A tracker is not a contract and does not determine tax, worker classification, legal/IP rights or payment disputes.