BrightPath Client Handoff Pack
This is the actual account handoff referenced in Lesson 7.1 — everything you need to complete all five capstone deliverables. It's deliberately organized the way a real handoff would be: some materials are clean, some are messy, and a few things are genuinely unclear. Sorting that out is part of the assignment.
Contents
- 01 — Client Introduction
- 02 — Brand & Communication Guide
- 03 — Sarah's Email (This Week's Asks)
- 04 — Customer Support Thread
- 05 — Team Meeting Transcript
- 06 — Existing Onboarding Confirmation Process
- 07 — Business Data (Tasks, Hours & Weekly Support Volume)
- 08 — Research Request & Prior Notes
- 09 — Scheduling Information
Client Introduction
BrightPath Learning Co. is a small online learning company. It teaches practical workplace skills — spreadsheets, business writing, and general digital-office skills — through short, self-paced courses aimed at working adults who want to build job-relevant skills without going back to school. The flagship products include the Advanced Excel Workbook and Basic Excel Workbook courses, along with a general onboarding/orientation track for new students.
The team is small:
- Sarah — Founder and operations lead. Based in the U.S. (Eastern Time). Handles client-facing decisions, approves content, and is the main point of contact for the VA.
- Daniel — Handles onboarding content, the FAQ, and course copy.
- Maya — Handles customer support and reviews student feedback.
You (the VA) are being brought on to help with administrative support, customer communication, documentation, reporting, and occasional research — working async, since you're in a different time zone from the team.
Sarah's own words from the onboarding call: "I don't need someone to reinvent how we do things. I need someone who can take what's already half-organized and make it actually usable — and who'll tell me when something doesn't add up instead of just guessing."
Brand & Communication Guide
Voice: clear, direct, professional. Friendly, but not overly warm — Sarah has said more than once that she doesn't want customer emails that sound like they're trying too hard.
Avoid: generic enthusiasm ("we're thrilled to..."), padded apologies, idioms that might not translate for non-U.S. students, and any wording that sounds templated rather than specific to the situation.
Audience: mostly working professionals in the U.S., but BrightPath has a growing number of international students, so dates, times, and phrasing should be unambiguous.
Sign-off style: first name only ("Thanks, Sarah" / "Thanks, BrightPath Support"), no company slogans or taglines in email signatures.
One standing rule: never promise a refund, replacement timeline, or policy exception in writing unless it's been confirmed. If something isn't confirmed, say so rather than guessing.
Sarah's Email — This Week's Asks
1) We have a new student who signed up but I don't think ever got a proper welcome message — can you put something together? Keep it short, matches our usual tone.
2) Forwarding a customer email below — she got the wrong workbook. Can you handle the response? I already checked, we're sending the correct one, just need someone to reply.
3) We keep doing the onboarding confirmation step differently depending on who's covering it that day, which is a problem. Can you turn what we've got into an actual SOP? I put our rough notes below.
4) Can you pull together this week's status update for me? Check the tracker doc — I don't have time to read through everything myself.
5) Also — not urgent, but whenever you get to it — we talked about researching how other online learning companies handle new-student onboarding, see if there's anything we should consider. Daniel started pulling some notes together already, I'll forward what he has.
Let me know if anything above doesn't make sense. Thanks!
— Sarah
Customer Support Thread
Note: this thread doesn't say whether Maria has already been told anything, or whether this is the first response. Treat it as the first reply unless something in your own deliverable suggests otherwise.
Team Meeting Transcript
Daniel: That could work. I'll check what would be involved.
Sarah: Let's hold off on adding it for now — we need to review the current onboarding emails first.
Daniel: I'll update the onboarding email draft by Thursday.
Sarah: Good. We'll review that version before deciding whether we need anything else.
Maya: Also flagging — I reviewed five recent support cases this week. Two students said the orientation video was hard to find in the welcome email.
Sarah: Is the link actually broken?
Maya: No, it works, it's just near the bottom of the email, easy to miss.
Daniel: The FAQ page doesn't mention where the video is either, now that you mention it.
Sarah: Can someone check whether the welcome email can make the video easier to find? Don't change it yet, I want someone to review the layout first.
Maya: I can review the welcome email layout this week.
Sarah: One more thing — onboarding confirmations. I noticed we're not doing it the same way every time. Whoever's covering it seems to improvise. Can we get an actual written process for that? I'll send over what I think the steps are, but I know it's incomplete.
Daniel: Agreed, that's been an issue.
Sarah: Let's get that documented this week if we can.
Existing Onboarding Confirmation Process (Sarah's Rough Notes)
Sarah's notes don't say what to do if a student's enrollment record can't be found in the spreadsheet at all (as opposed to being incomplete). That's a real gap in the source material, not something to fill in on your own.
Business Data — Tasks, Hours & Weekly Support Volume
This week's task log:
| Task | Status | Hours |
|---|---|---|
| FAQ cleanup | Completed | 2 |
| Customer responses | Done | 3 |
| Onboarding copy (Daniel) | In progress | 1 |
| Competitor onboarding research | Ongoing | 4 |
| Welcome email layout review (Maya) | Pending | — |
Status labels are inconsistent across the sheet (Completed / Done / In progress / Ongoing / Pending) — this is the real state of the tracker, not a formatting choice for this exercise.
Weekly student support questions (from the support inbox count):
| Week | Questions |
|---|---|
| Week 1 | 18 |
| Week 2 | 21 |
| Week 3 | 20 |
| Week 4 | 34 |
No explanation is provided for the Week 4 increase. Two of those Week 4 questions are the orientation-video ones Maya mentioned in the meeting transcript — the rest are unrelated.
Research Request & Prior Notes
— Several of them send some kind of short welcome/orientation video early in the sequence, seems pretty common.
— A couple use a short checklist for the first week (like "watch this," "set up your profile," etc.)
— One had a pretty long, text-heavy welcome email — I actually thought it was worse than ours.
— Draft line I wrote for a summary, not sure this is actually supported: "Students are abandoning onboarding because our video is hard to find."
Didn't get further than this before I got pulled onto the FAQ work. Up to you whether to build on it.
Daniel's notes are explicitly informal and partial — he says himself some of it isn't verified. His draft summary line is a claim worth looking at carefully against what the rest of this pack actually supports.
Scheduling Information
This is background information, not one of the five capstone deliverables — but it's a good candidate for your Open Questions list in Lesson 7.1, since it involves the same "don't guess a time zone conversion" discipline from Lesson 3.7.
That's the full handoff pack. Back to Lesson 7.1 →