How Team Members Should Communicate on Basecamp and Email

Communication is the difference between success and failure as a team.

When team members don’t know how to communicate, this wastes hours of our time we could use on higher leverage tasks and fixing issues.

One of the most important parts of managing your communication is your response to work assigned to you. This is a major bottleneck which slows everything down, since we value things getting done more than messages getting answered immediately.

For example, every time you hit send on a shared project, everyone receives an email. So while I’m managing over 1,000 emails a day, countless of these are responses to work already assigned out. Most of these responses include the following:

  • “Okay”
  • “Understood”
  • “Let me check”
  • “Sure”
  • “Thanks, checking it”
  • “Will respond after seeing it”

When a task is assigned or changes are requested, the instinctive response for many is to immediately acknowledge the message with quick replies such as “Okay,” “Understood,” “Let me check,” “Sure,” or “Thanks, checking it.” While these responses may seem polite and reassuring, they often add little value and can, in fact, be counterproductive.

These quick acknowledgments may only take a moment to send, but they generate unnecessary email traffic. Each time you send a message, it triggers a notification for the recipient, which can interrupt their focus and workflow. Over time, these interruptions can accumulate, leading to a less efficient work environment.

We value quality over quantity

AD 4nXdtYPZM128XUd9cOZ1L2BGgA8oQuHITiHxo0Ig7 XlGfpolEEIRL x MolAj3wtqcqIvJgtC8DVbUsqB dDuBOoDh3eOljiARV4eZdseWJCv6 cSEbXV3sTDbb1GSOkD7usFDNrNNX jbbZmEanZwDae7g?key=0XJjprL0NOVo0TiDe0fEGw
Multiple Messages Being Sent Instead of 1

Your response doesn’t need to be instant. We understand that it takes a few minutes to digest the task at hand, review the thread history, and formulate a plan of action. We do not expect you to respond within seconds. What we value more is a well-thought-out, comprehensive reply that addresses the task or query in full.

Rather than sending multiple short messages, take a moment to think through the task. Gather all your questions, concerns, or updates, and compile them into a single, concise message. This approach not only reduces unnecessary email traffic but also ensures that your communication is clear and complete.

Consider this scenario: A project manager sends a request for a minor change in a document. Within minutes, the team member responds with “Okay,” and a few minutes later with “Let me check.” Shortly after, another message follows: “I see the issue. I’ll update it now.”

Each of these messages might seem harmless on its own, but when viewed collectively, they create a fragmented communication trail. Each message triggers a notification, pulling the project manager’s attention away from other tasks. Instead of focusing on higher-level strategic work, the manager now spends time monitoring the progress of a small task, which could have been summarized in a single, well-considered reply.

Aim for inbox 0

AD 4nXdSf lOrkWqxZUH9LiLCktjPPbN5Xt S7uE1TVhHpMvBr3lg1B5vJ7oKXpOqjUK8UWZMm yycPgiJNMxBbtmSn2r8x3OsOuT8 p9k38cKD2rh mnNi1RwYyGAvcKX9uxWXi95cLVcgNZ0GNk5yFD5iL eYZ?key=0XJjprL0NOVo0TiDe0fEGw
Do, Delegate, Delete

Everyday you should be aiming for an empty inbox. You do this by following DDD, (do, delegate, delete) as shown in our level 1 VA training. This isn’t just for email but for Basecamp, Facebook, and any other platform where you’re communicating within the business.

The reason why this is so important is because we have clients and team members everywhere. Without personal efficiency with your communication, this makes this unnecessarily challenging even for simple tasks which take 5 minutes to complete.

Fortunately, fixing this is easy. We recommend installing plugins like Boomerang to return email messages at a certain date for projects which may take a while. For example, if you’re a website developer and know adding local service pages may take 2 days, boomerang messages out to that time so you can focus on getting things done and responding only when the task is complete.

You should avoid dot replies

AD 4nXcUSZIZvzWGCYkYbLLIC7XtzHRE4o7xNFBuLVt B27fpB 1og R2mW SdVty3j8ErhUmQBc0qOCR2zfDpycA7IFq4YLH31LKeuUcGRCu1dVVeh64C h3KwZKLv2k3NEpkGhYA7y8Zhwe9JHUuIh GWGuqKJ?key=0XJjprL0NOVo0TiDe0fEGw
Dennis Yu, Responding To An Email Thread With a Dot Reply

Dot replies are reminders of an email or basecamp thread which aren’t being answered. Every time you see this in your inbox, it means we want communication and iteration. Chances are, if you see this in your inbox it means that tasks aren’t being completed and your iteration is required.

We’ve heard every excuse on why this happens. Your internet goes down, or your mother get’s sick, or a typhoon kills your power for a few days. What you do in these situations separates the A players from everyone else. If you know you’ll be unavailable for a few days, it’s important to communicate with our team so we can delegate out your projects in advance.

Many VAs and team members have disappeared for a week, only to blame their absence on something outside of their control. As we’re building a team of A players, sudden long absences without communication will result in immediate termination from working with us.

Check your grammar before sending messages

Whether you’re from Pakistan, the Philippines, or even the USA – watch your English before sending messages to our team and clients. Even if unintentional, this makes us look unprofessional and throws into doubt our ability to get things done for our clients.

You should eliminate any improper slang when communicating. For example, “ur”, “idk”, etc. You should also follow basic English word structures and start sentences with a capital letter and end them with a period or question mark.

If a client who’s paying us thousands of dollars a month sees we can’t spell – how can he trust us to solve issues for his website or ads accounts? This results in less money for the agency, which in turn, means less money for us all.

You should be studying our level 1 VA training if you’re unsure on any of these

We only want A players on our team. What that means is proving you can communicate well within a team and add more value than you take away. Oftentimes, QAing your blog posts and text actually costs us more money and time than simply doing it ourselves, which serves no one and wastes countless hours.

This is also why studying and completing our level 1 VA course is a requirement for all new VAs who want to join our team.

Basecamp Basics – The Foundation of How We Work

Basecamp is the main place we communicate with our team and with clients. If you’re part of a project, you’re expected to stay on top of everything happening in Basecamp. We have a simple philosophy: if it didn’t happen in Basecamp, it didn’t happen.

That means tasks, updates, iterations, and files don’t live in email or Slack. They live here, so that there’s one place everyone can check and stay aligned.

Why Basecamp matters

Email gets messy. Slack is temporary. Basecamp is where we track client projects in a way that is transparent, documented, and easy to follow. It lets us:

  • Keep clients updated without confusion.
  • Make sure tasks don’t get lost.
  • Apply RACI (Responsible, Accountable, Consulted, Informed) so the right people are always looped in.

It’s also client-facing. With the exception of one “Updates (Internal)” thread, everything you post can be seen by clients. That’s why precision and clarity are non-negotiable here.

Basics – The Foundation of How We Work 1

It’s a core part of the OpsProcess, the structured way we run projects, hold people accountable, and keep quality consistent across the team.

Rules you must follow

To avoid confusion and wasted time, here are the standards we live by:

1. Tasks live in Basecamp.
When Dennis (or anyone else) gives you a task in email, turn it into a Basecamp To-Do. If it’s not here, it doesn’t exist.

Basics – The Foundation of How We Work 2
Basics – The Foundation of How We Work 3

2. Use proper naming in Basecamp.
Threads, projects, and tasks must be named so anyone can understand what they are at a glance. “Obtain access to John Smith’s Facebook Business Manager” is clear. “Access” is not.

Basics – The Foundation of How We Work 4

3. File handling.
When sharing with clients, always use PDFs. Internally, use Google Drive links instead of uploading directly into Basecamp. Our Drive is unlimited; Basecamp storage costs money.

4. Link everything.
Every update you post should include links even if you’ve already shared them before. Don’t make people hunt.

5. Don’t ping Dennis.
He sees the updates. Trust the system.

6. Apply RACI every time.
Only add the people who need to be there. Don’t flood inboxes. Remove subscribers who don’t belong.

Basics – The Foundation of How We Work 5

7. Never mark your own tasks complete.
Managers close tasks after QA. Your job is to finish and update, not to close.

Basics – The Foundation of How We Work 10

8. Don’t delete.
Nothing in Basecamp gets deleted. Even if something feels obsolete, the context may be valuable later.

9. Post frequent updates.
Silence is not an option. Even if you haven’t finished, post what’s been done so far.

10. Don’t ignore messages.
A message unanswered is work left hanging.

11. Continuation threads.
When threads hit 80+ comments, you must create a continuation thread so Gmail doesn’t truncate.

12. Rescue and revive.
If something is stalled, it’s your job to “rescue” or “revive” it; don’t let threads die without resolution.

13. Use “My Stuff.”
That’s where you’ll find every task on your plate. No excuses for missed deadlines.

Basics – The Foundation of How We Work 6

Internal vs. client-facing

Every thread is visible to clients unless it’s explicitly internal.

That’s why we have an “Updates (Internal)” thread. This is where drafts, rough versions, or questions go before posting client-facing updates.

Basics – The Foundation of How We Work 7

Once something is ready, it moves into the client threads.

Basics – The Foundation of How We Work 8

Managing subscriptions

By default, Basecamp adds everyone as a follower when you create a thread. That’s sloppy.

Change people to “Just Following” if they don’t need full project notifications, then subscribe them only to the specific threads where they’re relevant.

Basics – The Foundation of How We Work 9

Always apply RACI when deciding who gets notified.

Quality over quantity

Posting in Basecamp is about clarity and progress. A vague note like “Done” isn’t an update. A proper update is:

  • What was done.
  • The link to the deliverable.
  • What the next step is.
  • Who owns that next step.

That’s how we keep projects moving without wasting time.

Bottom line

Basecamp is the single source of truth for all client work. Learn to use it properly and you’ll avoid confusion, save time, and make clients happy. Skip it, and you’ll create chaos for yourself and everyone else.

If you want to learn how to run client calls, manage your team effectively, and handle both happy and frustrated clients with confidence, the Level 4 Account Manager Course will show you exactly how.

Why Am I Seeing a “Continuation” Thread in Basecamp?

We manage structured communication and projects in Basecamp to ensure we actually do what we said we would, tracing it back to individual tasks by individual people.

If you notice a thread labeled “Continuation” in Basecamp, there’s a simple reason for it.

Gmail places a 100-comment limit on each thread. Once that limit is reached, the thread can no longer be used reliably for tracking and follow-ups. To avoid running into that ceiling, we start a continuation thread before we get there, usually around 80 comments. This keeps communication organized and ensures nothing breaks at the worst possible moment.

Sometimes you may see a continuation thread started even earlier, around 50 or 60 comments. Our team uses Boomerang for Gmail to manage follow-ups, which can include internal reminders and messages that aren’t visible to clients.

Because of those additional follow-ups, the effective comment count can be higher than what you see. Rather than risk hitting the limit, we reset the thread early.

If you’re a client, seeing a continuation thread is actually a positive sign. It means there has been substantial communication and multiple rounds of iteration to refine your campaigns. More discussion usually means more optimization and attention to detail.

Any team member can start a continuation thread when a conversation begins to grow long. There’s no special approval required. If the comment count is climbing, we create a new thread and reference the original so the history remains connected and easy to follow.

On larger projects, this process can repeat several times. We have some threads with seven continuations, which means more than 700 iterations on a single initiative. This is common for living documents such as our Team Roster, which is updated frequently, and for core programs like our AI Apprentice Program, Quick Audit, and the Google Knowledge Panel package.

When you see a “Continuation” thread, nothing is wrong. It simply means the work is ongoing, the discussion has been extensive, and we are maintaining a clean, trackable system so projects can scale without communication breaking down.