You’re deep in a deliverable on Tuesday morning when your phone buzzes. Text from a client: “Quick question, did we decide on the blue or the teal?” You check Slack, same question, sent 10 minutes later. You open email, there it is again, sent just now. Three channels, one question, all of them interrupting your focus. You spend 12 minutes responding in three places, context-switching away from two hours of productive work.
This isn’t a difficult client. It’s an undefined system. The client doesn’t know which channel to use, so they use all of them. The question wasn’t urgent, it just felt urgent in the absence of any norms. If you’d defined the communication matrix in Week 1, the text and Slack message never happen. The question goes to Slack, you answer it between blocks, and the morning is uninterrupted.
Defining communication channels is a 20-minute setup task that prevents hundreds of hours of channel confusion over the course of an engagement.
The 4-channel matrix
Each channel has a specific purpose, a default response time, and a format. The matrix makes every communication decision a simple channel-matching exercise.
Email: Non-urgent, documented, formal
What it’s for:
- Non-urgent questions that don’t need a same-day answer
- Formal decisions, approvals, and scope changes, anything that needs a record
- Invoices, contracts, and legal documents
- Anything you’d want to reference months later in case of a dispute
- Initial outreach and relationship communication before a project starts
What it’s not for:
- Quick back-and-forth project questions (use Slack)
- Visual explanations (use Loom)
- Reference documents that will be updated (use Notion)
Response time commitment: 24 hours on business days. You don’t check email constantly, twice per day (morning and early afternoon) is enough for most projects.
Why it matters: Email is the paper trail. Any decision made in email is documented and timestamped. Any decision made in a text message or casual Slack thread is deniable. Train clients to route formal approvals and scope changes through email, not because you’re being legalistic, but because disputes are rare and both parties benefit from a record.
Slack: Project questions, quick answers, team chat
What it’s for:
- Quick project questions that need a same-day answer
- Daily check-ins on active work
- File sharing and quick feedback
- Conversations that benefit from being documented but don’t need email formality
What it’s not for:
- Formal decisions or approvals (those go to email)
- Complex explanations (use Loom)
- Reference documentation that needs to be permanent (use Notion)
- After-hours communication (set Slack notification schedules)
Response time commitment: Same business day, during working hours. Be explicit: “I check Slack twice daily and respond same-day during business hours.”
The Slack boundaries: Set your Slack notification schedule to your working hours only. On desktop: Preferences → Notifications → set “Do not disturb” schedule. On mobile: same location in the app. Clients cannot Slack you at 10pm if your notifications are off. This isn’t avoidance, it’s a feature of a professional working relationship.
Notion: Permanent reference, project documentation
What it’s for:
- The project brief and scope
- Meeting notes and decision log
- Milestone tracker and deliverable status
- Brand guidelines, reference materials, style guides
- Anything that needs to be findable, updateable, and permanent
What it’s not for:
- Real-time conversation (use Slack or email)
- Quick questions (use Slack)
- Feedback on specific content (use Loom or inline comments)
How to use it: Create a client-specific Notion page at kickoff. Share it with the client. Update it throughout the project. When a client asks “what was the decision we made about X?”, the answer is in Notion. When you’re wrapping up and they ask for all project documentation, it’s in Notion.
The key discipline: Notion is a living document, not an archive. Update it in real time, not at the end of each month.
Alternative: Google Docs folder with a shared index page works for clients who don’t want to use Notion. Same logic, different tool.
The most common freelance communication failure isn’t using the wrong words, it’s using the wrong channel. A formal approval in a Slack thread feels casual and gets forgotten. A quick question in an email creates a 48-hour delay on something that needed 2 minutes. Channel matching is a skill, and clients follow the lead of whoever sets the norms first.
Loom: Walkthroughs, feedback, async explanations
What it’s for:
- Delivering feedback on creative work (show what you’re referencing, not just describe it)
- Explaining complex decisions where tone matters
- Screen walkthroughs of new features, tools, or deliverables
- Any explanation that would require 200+ words in email
- Replacing a 30-minute meeting that could be a 5-minute video
What it’s not for:
- Official approvals or decisions (follow up Looms with an email confirmation)
- Urgent responses (response time for Loom is longer than Slack)
- Routine brief exchanges (overkill, use Slack)
Response time commitment: 24 hours to watch and respond. When you send a Loom, note what response you need: “Watch this 4-minute walkthrough and confirm the approach works for you, reply with email or Loom.”
The Loom advantage for freelancers: You can record and send a Loom in 5 minutes that replaces a 30-minute scheduled call. For time-consuming explanatory conversations that don’t require real-time interaction, Loom is the most efficient tool in the stack. It also creates a record, the client can watch it again, share it with stakeholders, and reference it later.
The norms document: what to send at kickoff
Send this at project kickoff, not when communication chaos starts, but before it can. One page:
Subject: How we’ll communicate on [Project Name]
Hi [Name],
To make sure we work together efficiently, here’s a quick note on how I handle communication:
Email: For anything formal, important decisions, scope changes, invoices, and anything we’d want a record of. I respond within 24 hours on business days.
Slack: For quick project questions, day-to-day check-ins, and file sharing. I check and respond same-day during business hours (Mon–Fri, 9am–6pm).
Notion ([link]): Our project source of truth, brief, milestones, decisions, reference materials. I update it throughout the project. Check here first before asking something I might have already documented.
Loom: I’ll use Loom for complex explanations, deliverable walkthroughs, and feedback. When I send one, I’ll note what I need from you in return.
Urgent matters: If something is genuinely urgent (blocked on a deliverable, something breaking), mark the subject line URGENT and I’ll prioritize it. Text is fine for true emergencies.
Working hours: [Hours and time zone]. I don’t check messages outside these hours.
Any questions about this setup, ask now, it’s much easier to clarify before we start than to adjust mid-project.
[Your name]
This document takes 10 minutes to write once, then lives in your email template library for reuse.
What breaks when you don’t define channels
Three failure modes, in order of how much they cost:
1. The multi-channel same question. The client texts, emails, and Slacks the same thing. You respond in three places. The client isn’t sure which answer is authoritative. You’ve lost 20 minutes and the client has gained confusion. This happens 2–4 times per week on undisciplined engagements.
2. The informal approval. A client approves a major change in a text message. Two months later, the project is over budget and the client claims they never approved the extra scope. You have a text message; they say they don’t remember sending it. Formal approvals through email would have prevented the entire dispute.
3. No real off time. When every channel is open and no channel is defined, clients default to constant low-level contact. You’re never truly off. Every dinner, every evening, every weekend has the possibility of a Slack message or text demanding your attention. Defined channels with defined response times solve this, not by making you less available, but by making your availability legible and predictable.
Enforcing the channels mid-project
When a client sends an important decision via Slack that should be in email: don’t be annoyed. Just redirect:
“Got it, can you send that confirmation in an email so I have it documented? I’ll proceed as soon as I have that.”
When a client emails you a question that’s clearly a quick Slack exchange: redirect:
“This is a quick one, shooting you a Slack message so we can go back and forth faster there.”
The redirection is a training signal. After 2–3 redirects, most clients adapt to the channels naturally. You’re not policing them, you’re teaching them how to work with you in a way that benefits both sides.
Ready to send stronger proposals?
Build, send, and track proposals in one place so follow-up is easier.
Start your free trial →
