How to Use AI to Manage Projects Across Several Clients

Put every client's tasks on one board with the same four fields (client, task, owner, due date), ask an AI assistant to turn a weekly export into a one-page status per client, and let the board's own rules send deadline alerts. AI summarises and drafts. People change dates and statuses.

That split is the part most setups get wrong. If you let an assistant read the board and write the digest, you save the Friday hour spent compiling updates. If you let it edit the board, you will eventually have a deadline moved by a guess. The rest is plumbing: a consistent card format, a prompt that leaves blanks blank, and a few automation rules you set once.

Follow me on Instagram@sagnikteaches

A four-person IT support firm with six client projects open

The main illustration for this tutorial: a four-person IT support firm. At any moment it has six client projects open (a mail migration, two office moves, a backup overhaul, a new-starter laptop rollout and a security tidy-up), plus a stream of small tickets that live elsewhere. The firm's owner currently tracks projects in a mix of notes, email flags and memory, and spends about 90 minutes every Friday assembling update emails.

Connect on LinkedInSagnik Bhattacharya

The numbers that make the case: six clients, an average of 14 open tasks each, so 84 open tasks. A missed date on any of them costs goodwill; a missed date on an office move costs a day of someone's hired van. Say two dates a month slip without anyone noticing until the client asks. The target is zero silent slips, and the Friday hour cut to about 20 minutes of reading and editing.

Subscribe on YouTube@sagnikteaches

Build the board so an assistant can read it

AI reads structure far better than it reads chaos, so the board is the foundation. Use whichever tool you already have: a board tool such as Trello, Asana or monday.com, or a shared spreadsheet. The tool matters less than the discipline.

One board, same fields on every card

Create a single board (or sheet) for all clients rather than one per client. Every card needs:

• Client (a label or column; one value only)
• Task (start with a verb: "Migrate shared mailbox", not "Mailbox")
• Owner (one person, not "team")
• Due date (a real date, never "soon")
• Status (Not started, In progress, Waiting on client, Blocked, Done)

The status "Waiting on client" is worth the extra word. It separates delay you caused from delay the client caused, and the digest can then say so plainly. Without it every late task looks like your failure and every chaser email looks like an apology.

Add two optional fields that pay off

A "Next step" field (one line, written by the owner) and a "Client-facing?" flag (yes/no) make the digest far better. Next step tells the assistant what is about to happen; the flag tells it which items belong in the client version and which are internal. If you add nothing else, add these.

A before and after of one card

Before: title "Office move stuff", no owner, no date, description "check with the site guy about the router". After: client "Client D", task "Confirm router model and port count with site contact", owner "Tech A", due 12 Nov, status "Waiting on client", next step "Chase site contact by phone Thursday". Only the second can be summarised, sorted by date or alerted on. If your team writes the first kind of card, fix that before you buy any AI plan.

Set deadline alerts with rules, not with AI

Deadline alerts are a rules job. A rule says "when a card is due in two days and its status is not Done, notify the owner". Rules are cheap, predictable and do not drift. Board tools call this automation or rules, and the allowances differ by plan. As of November 2026, Trello's pricing page lists 250 workspace command runs a month on the free plan and 1,000 on Standard, monday.com lists 250 automation actions a month on Standard, and Asana lists unlimited automations on Starter. A rule that fires on every card every day can use up a small allowance quickly, so do the sum for your card count before you rely on a free tier.

Set four rules and stop:

1. Due in 3 days and not Done: message the owner.
2. Due tomorrow and not Done: message the owner and the person who manages the client.
3. Overdue: move the card to a visible "Overdue" list or highlight it, and notify the manager.
4. Status set to "Waiting on client" for more than 4 days: remind the owner to chase.

Rule 4 is the one most firms miss. Client waits are where projects quietly stall. In an illustrative month, the IT firm finds three "waiting" cards that had sat for nine days each; the rule would have flagged each on day five.

Some tools have built-in AI that can write or suggest rules, and they often cap usage. For example, Asana's paid plans include 5 AI requests per user a month (up to 50 per account on Starter and Advanced) and then charge $0.50 to $0.60 a request, while monday.com's work-management plans come with a monthly pool of AI credits that grows with the plan (1,000 a month on Basic). Treat those as extras to check on the vendor's current pricing page, not as the core of the system.

The Friday digest: export, filter, summarise

This is where the assistant earns its place. The routine takes about 20 minutes once set up.

Step one: export one client at a time

Export the board as CSV. Spreadsheets always can; some board tools keep export for paid plans, so check yours before you plan around it. Filter to a single client, and keep only these columns: task, owner, due date, status, next step, client-facing. Drop comments and attachments; they often carry names, quotes and contract detail you do not need to paste. Paste the cleaned rows into your assistant's chat. If your firm uses a business plan of an assistant, use that rather than a personal account, for the reasons covered in how to roll out an AI policy.

Step two: the prompt

Below are the open tasks for one client. Today is [date].
Write a status update for the client in plain language, under 180 words, with these headings:
Done this week / Happening next week / Needs your input / Risks.
Rules:
- Only use client-facing = yes rows in the update. List internal rows separately for me, not the client.
- "Needs your input" = rows with status Waiting on client. Give the date we need the answer by.
- A risk is any row due within 5 days that is not Done, or any Blocked row.
- Do not invent dates, owners or reasons. If something is missing write MISSING.
Rows:
[paste]

Illustrative result for the mail-migration client:

Done this week: Shared mailboxes migrated for finance and sales.
Happening next week: Migrate remaining 9 user mailboxes (Tuesday-Thursday); update phone profiles.
Needs your input: Confirm the cut-over time for Thursday evening (we need this by Monday 9 Nov).
Risks: Domain records change is due Wednesday and still depends on your registrar login. MISSING: owner for the registrar task.

The MISSING line is useful, not a failure. It tells you the board has a hole and exactly where. Before sending, the owner reads the digest against the board, fixes any MISSING items and edits tone.

Step three: the internal summary across all clients

After the six client digests, ask for a second, internal view, using all six exports pasted with the client name kept (this one is for you, not for sending):

Across these clients, list: (1) every task due in the next 7 days, sorted by date, with owner and client;
(2) any person with more than 5 tasks due in that window;
(3) clients with two or more Waiting on client tasks older than 4 days;
(4) anything marked Blocked.

Item 2 catches overload. If one technician has nine tasks due Thursday across three clients, you want to see it on Friday, not Thursday morning. The task scheduling tutorial goes further on turning that list into a week's plan around capacity.

A check that the digest is honest

Spot-check three rows per client against the board each week for the first month. Count mismatches. If the count is above zero, the likely causes are, in order: stale cards, a pasted export that was filtered wrongly, or a prompt that lets the model fill gaps. After four clean weeks, cut the check to one row.

Another firm, other fields: a print shop with job deadlines

The same structure works in a different trade. A small print shop runs, say, 20 live jobs for 11 business clients, each with a proof date, an approval date and a delivery date. Three due-date fields on one card is messy, so the shop uses one card per milestone: "Proof to client", "Client approval", "Print", "Deliver". The status "Waiting on client" now means proof approval, which is where most print jobs slip. Their Friday digest becomes a short list per client: proofs awaiting approval and the last date approval can arrive and still make delivery. The prompt change is one line: "For each Waiting on client row, state the latest approval date that still allows delivery, using the lead time in the Lead column." The lead time lives in a column the owner fills once per job. The assistant does the date maths, but the owner spot-checks two rows, because date arithmetic is exactly where models slip.

The same board as a spreadsheet, column by column

If you do not want another subscription, a shared spreadsheet does the job for up to a dozen clients. Use one sheet, one row per task, and lock the header. The columns that matter, in order:

Use data validation for Status and Client-facing, so nobody can type a stray value. A conditional-format rule that turns a row red when the due date is before today and the status is not Done gives you a poor man's overdue alert; a daily reminder email from the spreadsheet tool, if it has one, covers the rest. For tidying a messy sheet before you paste it, clean messy data shows the quick checks.

A wedding planner running eight events as eight clients

Take a wedding planner with eight couples booked across the year, and the workload peaks in two or three months. Each couple has the same milestone shape: venue deposit, caterer final numbers, florist order, seating plan, supplier confirmations. The planner puts these on the board with the couple's code as the client, and the due dates are the supplier deadlines, which are fixed by other people's calendars. That makes the "Waiting on client" status the loudest one: couples forget to send final guest numbers.

Her Friday prompt is the same shape, with one change for tone: "Write each update as a short, warm message to the couple, using their first names from the Contact column. Do not mention internal rows." A sample output, illustrative: "Hi [first name], a quick update: the florist has your order, and the venue is holding the date. We need your final guest numbers by Friday 13 Nov so the caterer can lock the menu. Could you send them over by then?" She sends each in her own words after a read-through, and the digest turns a Sunday evening of messages into 25 minutes.

The internal view matters more for her. Asking "which couples have a supplier deadline in the next 14 days with a Waiting on client status" produces the list of people to ring first. In a peak month with four weddings overlapping, that single query is worth more than the written updates.

Retainers and recurring work

Not all client work is a project with an end. A retainer client has recurring tasks: monthly reports, quarterly reviews, annual renewals. Handle these with a recurring card that creates itself (the board's repeat or recurring-task feature) and a due date that is always the next one. Add a "Cycle" label so the digest can say "Monthly report: due 27 Nov" rather than showing it as an overdue task from last month. If a recurring card shows as overdue for two cycles in a row, that is a signal the retainer is under-resourced, and the internal view should raise it. Ask the assistant: "Which recurring tasks have been completed late in two of the last three cycles?" This needs a Completed date column; without it the question cannot be answered, which is a decent argument for adding the column.

An example of the all-clients view in a busy week

For the IT firm, here is an illustrative internal output for the week starting 9 November, from the second prompt above:

Due next 7 days (sorted):
10 Nov - Client B - Order replacement switch - Tech A
11 Nov - Client D - Confirm cut-over time - waiting on client
12 Nov - Client A - Migrate 9 user mailboxes - Tech B
12 Nov - Client C - Test restore of nightly backup - Tech B
13 Nov - Client E - Image 6 laptops - Tech A
Overload: Tech B has 6 tasks due 12-13 Nov across 3 clients.
Stale waits: Client D has 2 Waiting on client tasks older than 4 days.
Blocked: Client F security tidy-up (needs admin password reset).

The owner reads this and makes three decisions in two minutes: move the backup test to Monday the 16th because Tech B is overloaded, ring Client D, and unblock Client F. The assistant produced the list; every decision is human. That is the line to hold.

A quick sum worth doing before you roll it out

Say the Friday routine currently takes 90 minutes and the AI version takes 20 minutes of reading plus 10 minutes of board hygiene, so 30 minutes. That saves an hour a week, about 4 hours a month. Setting up the board fields and the four rules takes an afternoon, say 4 hours once. Payback in the first month. If your shop is smaller, with two projects, the saving is smaller and the board is probably enough on its own; add the digest only when the update emails start to feel like a chore.

The bigger saving is the missed dates. If two silent slips a month cost an hour of apology and rework each, and the alerts stop most of them, that is another couple of hours, plus the harder-to-count benefit of clients who do not have to ask where things stand.

Handling client data across several clients

A multi-client board holds several businesses' information in one place, and that deserves a rule. Three habits cover it:

• Generate per client. Never paste two clients' rows into the same client-facing prompt. If an assistant is asked to write for Client A with Client B's rows in view, it can leak a detail. Keep the internal all-clients view for yourself.
• Use initials or codes in task text. "Client D" on the card and the real name only in your own client list. A lost export then tells a stranger very little.
• Keep personal data off the cards. Task titles should name the job, not a person's home address or a staff member's HR matter. If it is in the title, it is in every export.

If a client's contract restricts which third-party tools may touch their data, their rows stay out of the AI step, and you write that client's update by hand from the board. The overall pattern of what to ask your clients, and your vendors, is in the small consultancy workflow, which treats confidentiality as the first decision, and the same logic applies to any firm with several clients.

Where multi-client AI tracking tends to break

• Stale cards. If nobody updates the board, the digest is a polished summary of last week. Add a Thursday 10-minute "board touch" and use rule 3 to expose overdue cards.
• Dates with no year or timezone. "3/11" is a different day depending on which date order the reader expects. Use unambiguous dates ("3 Nov") in the export and the prompt.
• Merged duplicates. Two cards for the same task show up twice in the digest. Ask the assistant to list suspected duplicates; deleting them is yours.
• A confident risk list that misses unlisted risks. The prompt defines risk by rule (due within 5 days, blocked), so the digest only flags what the board shows. A risk that exists only in your head is still yours to raise.
• Over-automation. The more the assistant touches, the more a quiet mistake costs. Keep it read-only for now.

Four weeks to a working setup

Week one: build the board with the five fields and migrate only open work. Week two: add the four rules and watch what they fire. Week three: run the Friday digest for one friendly client and compare it with what you would have written. Week four: roll the digest out to all clients and drop the spot-check to one row. When a project ends, archive its cards so the board stays readable. If a month of this shows your tools cannot do the filtering or alerts you need, a short 1:1 call to look at what you already have is usually cheaper than buying a new tool.

For a worked second perspective on the same problem in a very different business, the Claude Projects setup for an office manager shows one shared assistant project per job, and the compliance tasks tutorial uses the same rules-plus-digest idea for recurring deadlines.

Practical questions about multi-client tracking

Do I need a paid project tool for this?

Not to start. A free tier of a board tool such as Trello or Asana, or even a shared spreadsheet, holds six client projects. You need a paid plan when you outgrow the free automation allowance or want the vendor's own AI, and both are capped on many plans, so check the current plan page before relying on them.

Should the AI move cards or change due dates itself?

No. Let it read, summarise and draft, and let people change the board. An assistant that edits dates unprompted creates the exact silent errors you are trying to remove, and a client chasing a date nobody agreed is a worse problem than a late digest.

How do I keep one client's data out of another's report?

Produce one digest per client from that client's own cards, never from a mixed export. Put the client name in a column, filter before you paste, and read the output for any name that does not belong. The check takes under a minute per client.

What if my team will not update the board?

Shrink the update to one thing: a status word and a date on each card, touched twice a week. A digest built from stale cards is wrong with great confidence, so the first fix is a habit, not a tool.

Further reads

• AI Tools for a Coaching Business: Notes, Programmes and Follow-Up — Session notes and follow-ups for client-based practices.
• How Freelancers Use AI for Invoices, Proposals and Chasers — Chasers and invoices for the same busy client load.
• CRM With Accounting Integration: Link Deals to Invoices and Payments — Link deals to invoices once the work is tracked.
• How Consultants Use AI for Client Research Before Discovery Calls — Prepare for the next client call in 20 minutes.
• How to Mention AI Use in Client Contracts and Proposals — Tell clients how AI is used on their projects.
• AI Tools and AI Development: The Complete 2026 Guide — the AI hub, including every tutorial in the AI-for-business series.

Sources: Asana, monday.com and Trello pricing pages, read on 4 November 2026; the setup is working method.