How to Build a Client Project Tracker That Stays Useful

Track only fields that support a real decision. These sample values are illustrative, not a customer case study.

Avoid adding every note, file, and subtask to this overview. Link to the underlying project instead.

Track one row per active project. One client may have a website redesign awaiting approval and a monthly retainer moving normally. Combining them into one client status hides the difference. Group projects by client for reporting, but preserve separate project records.

Define each status with an observable condition:

• Not started: agreed work has not begun.
• In progress: someone can advance the deliverable.
• Waiting: the next response belongs to someone else.
• Blocked: a dependency prevents planned work.
• Complete: agreed work is finished, with approval tracked separately where required.

For every Waiting or Blocked item, name the person or dependency and the next action. A color alone is not enough.

The delivery deadline and the date you plan to chase feedback answer different questions. If a client promises feedback Monday, that does not automatically change Friday's delivery deadline. Record both dates and discuss schedule changes explicitly when a dependency slips.

Update the record when a meaningful event occurs: a milestone finishes, an owner changes, a decision arrives, or a new blocker appears. Review exceptions, not every field, during your regular planning check. Close or archive finished engagements so active work stays visible.

Noddis Portfolio compares projects in Cards, Snapshot, and Board views, while Execute holds the selected project's task-level work. Follow-Up separates what you owe from what you are waiting to receive. Record a task-linked commitment and its date when the next move belongs to someone else. The workspace guide explains where each view fits.

The fields and example statuses above are a planning template, not a set of custom fields automatically created by Noddis. Keep decisions and milestone context in the relevant project or task notes. Test the workflow in the Noddis live demo; the same field structure can also work in a spreadsheet.

A designer is handling a website refresh, a pitch deck, and a monthly retainer. The website is waiting on homepage approval. The pitch deck is due November 7. The retainer has six small tasks, none urgent. Counting open tasks makes the retainer look busiest, but it is not the highest-priority work.

The tracker should show the website as waiting on client, with an approver and follow-up date; the deck as in progress, with its deadline; and the retainer as on track, with its next milestone. The designer can then send the approval reminder, protect time for the deck, and batch retainer tasks later.

Illustrative example, not actual customer data. Detailed files and tasks belong inside each project, not duplicated in this overview.

1. Using progress as a substitute for status. A project can be nearly complete and still blocked.
2. Confusing delivery ownership with next-action ownership. You may own the project while the client owes the next decision.
3. Tracking deadlines but not reminders. A deadline tells you when work is due; a follow-up date tells you when to act.
4. Copying every task into the overview. A useful summary points to detail instead of duplicating it.
5. Only updating before meetings. Record changes when decisions happen so the tracker remains trustworthy.

At the end of the week, see whether you can identify every active project's next action without searching email. Check for missed commitments and surprise deadlines. If maintaining the tracker requires a second administrative session, remove fields before adding more automation.