# Client Clock: track the days every project waits on your client > Ask clients for content, files and approvals on the ticket. Navbatly counts the days each one waits, sends reminders and moves the project's target date to match. - Canonical page: https://navbatly.com/features/client-clock - Language: en-GB - Also in: [Русский](https://navbatly.com/ru/features/client-clock.md), [Oʻzbekcha](https://navbatly.com/uz/features/client-clock.md) - Last reviewed: 29 October 2026 - Maintained by: Karve Digital (hello@karvedigital.com) Most late projects are waiting on the client, not the agency. Client Clock puts what you need from them on the ticket, counts every day it waits, and shows your client the same count. ## How it works 1. **Ask for it on the ticket.** Add a client action to the ticket: what you need, such as the homepage copy, room photos, a login or an approval, who at the client you're asking, and a note with basic formatting if it needs one. They get an email listing what you asked, with a link to send it. Several asked at once arrive in one email. 2. **They send it from their link.** The link opens their private request link, with no sign-in. They write a message, drop in files or both, or for an approval, approve it or say what to change. Either way the ball is back with you: the clock stops and your team is told. 3. **Send it back if it isn't enough.** If what came isn't enough, send it back with a note. They're told, and the clock runs again, adding to the same days waited. 4. **Work carries on.** A client action is not a ticket status, so your team can keep working on the ticket while it waits. Resolving or closing the ticket withdraws anything still outstanding. ## Both sides of the clock ### What your client sees Everything happens on the client's private request link, which needs no account and works on any device. - Waiting on you: everything they owe, grouped by project, with who it's asked of and the days it has waited - Send or Review on each one, with a note on anything you sent back - Your projects: each target date, the agreed date behind it and every change to it - Their monthly report, and a form to send you a new request ### What your team sees The Waiting on clients page lists every outstanding client action across your clients, longest wait first. - Filter by client, project or the person it's asked of - Mark one received when it came another way, send it back or withdraw it - A card on your overview, and an hourglass with the days waited on each ticket in your lists - A marker when a project is due a pause notice ### On each project's page A project's page puts its target date and the days it has waited on the client above its tickets. - The target date, with the agreed date behind it and the days waited that moved it - The days the project has waited, and one click to what is still outstanding - Whether a pause notice is due, with a draft you edit before sending ## Dates that move with the wait Give a project an agreed date: the date you and your client agreed it would be finished by. Navbatly shows its target date, the agreed date moved later by each day the project has waited on the client since it was agreed or last changed. A day counts once for the project, however many things were outstanding that day. Change the agreed date and your client sees the date it replaced and when it changed, so a new date never looks like a slip. For example: An agreed date of 20 Nov, with 13 days waited on the client since, gives a target date of 3 Dec. ## Reminders and the pause notice - **Reminders:** Pick your team's reminder days, 3, 7 and 14 to start with. When something reaches one of them, Navbatly emails that person a list of everything they still owe, with their link. You can switch reminders off for a client; the clock still runs. - **Pause notice:** When a project has waited 21 days (your pause day, which you can change), Navbatly suggests a pause notice: an email saying the work is on hold until the outstanding actions arrive. Owners and admins edit it and choose whether to send it. It goes only to the client's people who owe something, and changes nothing else about the project. ## On the monthly report Each client's monthly report lists the client actions they delivered that month and those still outstanding at its end, with the days each one waited. It shows only what was asked and of whom, never your internal notes. ## Client Clock, defined - **Client action:** Something a ticket needs from the client, such as content, a file or an approval, asked of one person there. - **Outstanding:** Asked, and not yet delivered or withdrawn. - **Delivered:** Answered from the request link with a message or files or, for an approval, approved or with changes asked. You can also mark one received when it came another way. - **Sent back:** Returned with a note because what came was not enough. Its clock runs again. - **Withdrawn:** No longer needed. The days it waited still count. - **Days waited:** The days an action waited on the client. A day counts when it is still outstanding at the end of that day, so one delivered the day it was asked has waited none. - **Request link:** The client's private link to send what they owe, see their projects' dates and send you requests, without signing in. - **Agreed date:** The date you and the client agreed a project would be finished by. - **Target date:** The agreed date moved later by the days the project waited on the client since it was agreed or last changed. - **Reminder:** An email listing everything one person at the client still owes, sent on your team's reminder days. - **Pause notice:** An email you choose to send saying a project's work is on hold until its outstanding client actions are delivered. - **Pause day:** The days waited at which Navbatly suggests a pause notice: 21 unless you change it. The count starts again once one is sent. ## Questions about Client Clock ### Does my client need an account? No. They send everything from their private request link, without signing in. ### Does an outstanding client action stop work on the ticket? No. A client action is separate from the ticket's status, so your team can keep working while it waits. When the ticket is resolved or closed, anything still outstanding is withdrawn. ### What if the client sends it by email instead? If they answer an email about that one ticket, their answer and files land on it as their reply. Mark the action received there: that delivers it and stops the clock, just as if they had sent it from their link. ### Can I turn reminders off? Yes. Switch them off for one client, or change your team's reminder days or clear them to send none. The clock keeps counting either way. ### Does sending a pause notice pause the project? No. It is an email to the people who owe you something. Navbatly has no paused status: the project stays as it is, and the days counted toward the next notice start again. ### Does Client Clock cost extra? No. It is part of Navbatly, not an add-on. ## Put a clock on what clients owe you Create a team, add a client and ask for the first thing you need. Questions first? Ask for a walkthrough by email. Create a team at https://navbatly.com/register, or email hello@karvedigital.com.