Client Follow-Up Tracker Template: Requests, Replies, and Next Actions

A client follow-up tracker records what you requested, who needs to respond, when you last contacted them, and what you will do next. Use one row per open request, with a next action and a date to review it.

This is useful when you are waiting for approval, content, access, payment confirmation, or a decision across several client projects.

The aim is to open your workday and know which conversations need attention, without searching every email thread.

Below is a free copy-paste template, a filled example, and a simple way to turn follow-ups into dated tasks.

Free client follow-up tracker template

Copy this into a spreadsheet or document. Use the ID to keep related notes attached to the same request.

Add a short note beneath a row, or in a separate notes column, when you need:

• A link to the conversation or document.
• The milestone affected by the request.
• The latest reply.
• A scope or scheduling decision.

Keep those details brief. The tracker should help you return to the source conversation.

The two dates mean different things

Agreed reply date is when the other person said they would respond.

Follow-up date is when you intend to check or act.

You can set a follow-up date yourself. You cannot turn it into a client commitment.

If nobody agreed to a reply date, write “not agreed.” That is more useful than presenting your preferred date as an overdue promise.

Filled example: three clients, five open requests

The following example is fictional. Dates illustrate how the tracker works.

Notice the difference between the final two rows.

For Cedar Consulting, the next useful move belongs to you. You need to make the question easier to answer.

For Harbor Co, the reply has already arrived. The request is ready for implementation, but the work is not finished yet.

“Client replied” and “request resolved” are different outcomes.

How to fill in each field

Request or decision needed

Write the exact thing that will move the work forward.

Weak: “Website feedback.”

Better: “Approve the homepage headline and section order.”

A broad request often produces a broad reply. A specific question gives both sides a clearer endpoint.

Waiting on

Name the person responsible for the next response.

If you do not know who can approve the work, your next action is to identify that person.

For a small team, add an internal owner column as well. “Waiting on Maya” does not explain who on your team should follow up.

Last contact

Record the date of the latest meaningful message and keep a short note of what changed.

For example:

Oct 14: Maya requested a headline revision. Revised preview sent the same afternoon.

You do not need to copy an entire conversation into the tracker.

Next action

Start with a verb:

• Ask for the missing file.
• Send the revised preview.
• Confirm who can approve.
• Verify that access works.
• Explain the effect on the delivery date.
• Implement the confirmed change.

“Waiting” describes a condition. It does not tell you what to do when you review the row.

Follow-up date

Choose a date based on the work, the agreed response window, and the effect of a delay.

A launch-blocking approval needs different attention from an optional testimonial request.

Use a small set of statuses

These labels are enough for most freelance and small-team workflows:

Use a separate impact note for blocked work, such as “launch cannot proceed without approval.”

This avoids confusing two things: who owes the next action and how important the delay is.

A practical follow-up routine

You do not need to check every row throughout the day.

At the start of the day

Review rows whose follow-up date has arrived.

For each one, choose an action:

• Send a message.
• Check whether the answer already arrived.
• Complete your own outstanding step.
• Agree a new date.
• Close the request.

If no action is useful yet, move the review date and record why.

After a reply

Update the row while the conversation is fresh.

Record the answer, change the status, and schedule any resulting work.

If the reply only answers part of the question, keep the missing part visible. Split the request when separate answers will now move on different timelines.

Once a week

Review every open row.

Look for requests with no next action, repeated unanswered messages, and work whose delivery assumptions have changed.

Sometimes the right move is a clearer question or a scheduling discussion.

How often should you follow up with a client?

Start with the response window you agreed.

If you asked for a decision by Friday, avoid treating Thursday as late. If there is no response window, set one in your next message.

For routine requests with no agreement, you might choose to review after two or three business days. Treat that as a starting point, not a universal rule.

Adjust for:

• Urgency and milestone impact.
• The client’s working days and timezone.
• The complexity of the decision.
• Whether you supplied everything needed to answer.
• The communication channel you agreed to use.

After repeated unanswered messages, explain what is blocked and ask whether timing or priorities have changed.

Increasing the number of reminders does not make an unclear request easier to answer.

Three follow-up messages you can adapt

1. A specific reminder

Hi [Name],

Following up on [specific request] from [date].

Could you confirm [decision or input]? I need it before [next project step].

If [proposed date] is difficult, please let me know what timing works.

2. A request that affects the schedule

Hi [Name],

We are still waiting for [input] before we can complete [work].

The current delivery plan assumes we receive it by [date]. If it arrives later, I will need to review the remaining schedule and confirm a revised delivery date.

Could you let me know when to expect it?

Use this wording only when that scheduling assumption is accurate. Do not suggest a deadline was previously agreed if it was not.

3. A reply that needs clarification

Hi [Name],

Thanks for the update. I have enough information to proceed with [confirmed part].

One point is still open: [specific question].

Would you prefer [option A] or [option B]? The difference is [brief practical effect].

These messages make the requested response visible. They also give you a useful record of what remains unresolved.

Use the tracker with dated tasks in SelfManager

The template provides an overview. A dated task gives you somewhere to act on it.

In SelfManager, you can organize work in date-based tables and keep related notes and comments with the tasks.

For example, on October 16:

Table: Client follow-ups

• North Studio: check homepage approval and follow up if missing.
• Harbor Co: verify collaborator access.
• Cedar Consulting: send the two reporting options.

Record the result beside the task. If another step is needed, create it on the appropriate day.

The field labels in this article are a template you can use in notes or a separate tracker. They are not a claim that SelfManager has a dedicated CRM pipeline with these exact columns.

SelfManager fits when follow-ups belong alongside your other daily client work. A dedicated CRM may fit better if your main need is sales stages, automatic email logging, or outbound sequences.

Try SelfManager with this week’s active follow-ups: create a dated table, add the next actions, and keep the latest decisions in the comments.

Use AI to review what is still open

SelfManager’s table AI can use task details and, when included, comments to help you review the work.

A useful prompt is:

Review these client follow-up tasks and included comments.

Separate:

Actions I owe.Requests waiting on a client.Replies that need implementation.Questions with no clear next step.

Use only the information recorded here. Flag missing dates rather than inventing them. Draft messages for me to review.

Verify drafts against the actual conversation before sending. Replies that only exist in your inbox need to be recorded or supplied as context.

Keep the tracker small enough to maintain

Start with your active requests.

You can add historical records later if they serve a purpose. Your first goal is to make today’s open loops visible.

A useful row answers three questions:

• What is needed?
• Who acts next?
• When will I review it?

Put those next actions on the days you intend to handle them in SelfManager, and keep a short outcome note after each conversation.

Frequently asked questions

What is a client follow-up tracker?

It is a record of open client requests, replies, responsible people, and next actions. It helps you see which conversations need attention and what is holding up the work.

Can I use this template in a spreadsheet?

Yes. Copy the table into your preferred spreadsheet or document and adapt the fields. Add filters if you want to review a particular client, status, or follow-up date.

What is the difference between a reply date and a follow-up date?

A reply date is an agreed commitment from the person responding. A follow-up date is your own planned review or action date. Keep them separate so your reminder does not become an invented client deadline.

Should I close a request when the client replies?

Only if the reply resolves it completely. If the answer requires implementation, move it to “Ready for work.” If information is still missing, record the remaining question and the next action.

Can SelfManager automatically send client follow-ups?

The workflow described here uses SelfManager to plan actions, record context, and draft messages with AI. You review and send the message through your communication channel. This template does not depend on automatic email sending or inbox synchronization.