8 sheets · US Letter · Print the whole pack, or select pages 2–4 for learner cards.

SkillRise Spark · Facilitator guide · 1 / 8

BrightSpark Digital

Digital marketing agency · Halden Cross

An email travels further than intended. A hybrid team leaves things unsaid. Give learners space to untangle communication, trust and discretion.

Before learners arrive

Choose one of the three cards. Read its opening and try that workday online so you can discuss the consequences. Print one card per pair; keep this guide and the discussion sheet for yourself. No account is needed.

A 35-minute session

Frame · 3 minutes. “We are practicing decisions, not grading people. Explain what you would do and what it might cost.” Do not announce the skills beforehand.
Notice · 5 minutes. Read the card silently, or a volunteer reads it aloud. Separate known facts from assumptions; learners may think privately or jot notes.
Decide · about 12 minutes. Play the selected workday, or discuss the printed opening offline. In pairs, alternate decision-maker and observer; partners can choose differently and don’t need to agree. Offline cards cover the opening only, not branching consequences.
Discuss · 10 minutes. Use the matching question on sheet 5. Invite two defensible approaches, then name the trade-off and the boundary.
Reflect · 5 minutes. Offer the optional closing reflection. Learners may think privately, write, speak or pass; do not require personal workplace disclosures.

Keep the boundary clear

Keep internal messages and private coworker information within authorized channels. Repair an error without spreading the disclosure further.

Observe without grading

Listen for a learner distinguishing facts from guesses, explaining who is affected, and naming a next action. Record only what was actually said or chosen, not confidence, personality or assumed competence.

Suggested timings are flexible. Most practice scenarios take about 12 minutes; exploration and reflection add optional time.

SkillRise Spark · Learner scenario card · 2 / 8

BrightSpark Digital · Workday 01

Reply All

Monday · 8:52 AM

You get in, badge through, and your laptop is still loading when Priti swivels her chair over.

Priti: Have you seen the Dunmore thread this morning?

Friday at 5:40 you'd sent a quick note to close out the week: the banner assets were two days behind because the client hadn't approved copy, and you wanted it on record before you logged off.

you: “Just flagging — we're behind on banners because copy approval is still outstanding on Dunmore's side. Wanted this noted before EOW.”

You'd hit Reply All without checking who was on the thread. It turns out that includes Harold, his boss, Denise, Marcus, two people from the design vendor, and three people at Dunmore you've never spoken to.

Priti: Harold forwarded it to his whole team with 'per BrightSpark, we're behind.'

Denise's name shows up in your inbox before you've even opened it.

Denise messages you directly: “Can you call me in five?” What do you do first, before that call?

Draft a short apology-and-correction to send to the full thread.
Wait for Denise's call and let her tell you how to handle it.
Message Harold privately first to try to walk it back with him.
Write yourself two lines on what actually happened, so you don't guess on the call.

My next action and why: __________________________________

What it protects — and what it costs: ________________________

What I still need to check: __________________________________

No grades. Real consequences. Explain your reasoning; safety and privacy boundaries still apply.

skillrisespark.com/work/brightspark-digital/reply-all

SkillRise Spark · Learner scenario card · 3 / 8

BrightSpark Digital · Workday 02

Nobody Said No

Wednesday · 9:40 AM

Since the Dunmore thread, you've been careful with your writing — reading things twice, checking the CC line. Today is quieter. No fires. Just a brief.

Denise: Larkview Clinics want a social calendar for next month. Client's easy, budget's fine. Just get me a draft by Friday.

She's already half out of her chair, headed to a call. That's the whole brief.

There's no doc, no example calendar, no note on how many posts, what platforms, or whether Larkview's last agency left anything behind you could look at.

What do you actually do first?

Catch Denise before her call and ask two clarifying questions.
Ask Priti what a Larkview social calendar usually looks like.
Start drafting your best guess and adjust later.
Send Denise a Slack message with questions and wait for her to reply.

My next action and why: __________________________________

What it protects — and what it costs: ________________________

What I still need to check: __________________________________

No grades. Real consequences. Explain your reasoning; safety and privacy boundaries still apply.

skillrisespark.com/work/brightspark-digital/nobody-said-no

SkillRise Spark · Learner scenario card · 4 / 8

BrightSpark Digital · Workday 03

The Deadline That Won't Move

Monday · 10:15 AM

Denise asked where Marcus's copy is. You're the one who's been coordinating the Dunmore relaunch since your reply-all week, and you actually know the answer, because Marcus DM'd you an hour ago.

Marcus: hey — i'm not going to make wednesday. my kid's been in and out of urgent care since friday, i haven't opened the doc. i'm sorry, i should've said something sooner

Wednesday is when the copy goes to design, which is the only reason the relaunch launches on schedule Friday, which Harold has already told his boss is locked.

Denise is waiting for your answer in the channel.

What do you do?

Tell Denise now: Marcus is out, the copy isn't coming, and say why in general terms.
Tell Denise you're 'checking on it' and message Marcus first to see if there's a partial version.
Tell Denise the copy is delayed without explaining why, to protect Marcus's privacy.
Message Marcus's actual manager directly instead of Denise, since it's his deadline to manage.

My next action and why: __________________________________

What it protects — and what it costs: ________________________

What I still need to check: __________________________________

No grades. Real consequences. Explain your reasoning; safety and privacy boundaries still apply.

skillrisespark.com/work/brightspark-digital/the-deadline-that-wont-move

SkillRise Spark · Discussion & reflection · 5 / 8

Bring the decisions into the room

01 · Reply All

What would you change about the Friday email, and what would that change protect?

02 · Nobody Said No

When did an unclear expectation become something worth checking?

03 · The Deadline That Won't Move

Where is the line between protecting a coworker's privacy and withholding information the team needs?

When the group disagrees

Ask: “What is the strongest case for the other option? Who carries its cost? What fact would change your mind?” Explore the reasoning without endorsing unsafe action. State the relevant boundary plainly.

Reveal the skills after practice

Ask learners to name a skill in the action they actually chose. These are discussion connections, not automatic evidence:

Reply All: Written tone · Owning a mistake · Repair
Nobody Said No: Judging when to ask · Managing ambiguity · Following up
The Deadline That Won't Move: Escalation · Timing hard news · Accountability

Optional closing reflection

What would you check before forwarding a workplace message to someone outside its original audience?

“In this practice, I chose to ______ because ______. Next time, I would check ______.”

Adapt to your learners

Read aloud or allow silent reading. Explain unfamiliar terms without choosing for learners. Offer spoken, written, partner or private responses, and let anyone pass; never require reading aloud, acting or personal disclosure. Use one card for a short session, or compare workplaces in a longer class.

Evidence, not a credential

Separate skills practiced, actions demonstrated in actual choices, and areas still developing. Offline discussion does not generate a platform evidence card. Neither a discussion nor an online evidence card proves real-world competence or awards a certificate, credential or grade.

SkillRise Spark · Companion · 6 / 8

Companion · optional “Try it your way” practice

Practice a repair message

Purpose. Discuss communication, accountability and how to repair a mistake without escalating it.

Durable skills explored: Professional communication, Accountability, Written tone.

This is a separate practice email on the Dunmore project, not Monday's thread. The facts are deliberately simpler so you can practice the repair from the start. Everything here is simulated — nothing is sent.

Source material (as learners see it)

Dunmore project email · 09:10

“Please send the revised launch copy to Denise only for review. Do not send to the client.”
Your reply-all went to the client. It said: “We are still waiting on Marcus.”
Delivery timing is not confirmed.
Denise can authorize client updates.

Discussion prompts

What is the difference between a draft and a sent message here?
How do you describe what happened without guessing anyone's motive?
When Denise takes over, what is still yours to do?

One possible response

To Denise: “I sent an internal update to the client by reply-all. Here is the exact message; can you approve a correction and confirm who will send it?”

Proposed correction (draft — not sent): “Our earlier message included an internal coordination note. Denise will confirm the delivery update once checked.”

The example is one possible response, not the required wording. Look for exact reporting, no invented motive, and a clear question about who sends the next message.

What changes if…?

Denise says she has already spoken to the client and wants no further email.

The client draft stays unsent. Denise is now the owner of anything said to the client.
You can still ask whether any internal follow-up is needed — for example, letting Marcus know what was shared.
Nothing here tells you the client accepted an apology, so it's worth not assuming that.

Participation options

Individual:: Learners read the email and draft privately, or just think it through. Writing is optional.
Paired:: One partner drafts the note to Denise; the other reads it as Denise and says what they would still need to know.
Group:: Show the source email. Collect possible first sentences aloud, then introduce the changed condition and discuss what changes.

Writing is optional; learners may think privately, discuss, or skip. Nothing is graded or collected. Source: Blueprint v3.0 · Section 30 · B1 Reply All · p. 75.

SkillRise Spark · Companion · 7 / 8

Companion · optional “Try it your way” practice

Clarify the scope before you build

Purpose. Discuss initiative, judgment and clarifying expectations when a brief is vague and nobody has answered.

Durable skills explored: Initiative, Judgment, Clarifying expectations.

This is a separate practice situation, not the Larkview calendar from your workday. It's a different BrightSpark brief on a different week. Denise is still the one who approves work. Everything here is simulated. Nothing gets published or sent.

Source material (as learners see it)

Thursday brief · landing page

“Make the landing page more accessible before Friday review.”
The brief lists no budget, no scope and no approver.
You proposed a complete redesign. Nobody has replied.
The current page has unlabeled form fields and low-contrast helper text.
Denise owns approval.

Discussion prompts

What's the difference between no reply and approval?
Which page problems are clear, and which changes need a decision?
When the approver is away, what's still safe to do?

One possible response

“May I fix the field labels and check the helper-text contrast for Friday, while holding layout changes for approval?”

First step: list every affected field, or prepare an annotated internal draft. Publish nothing.

The example is one possible response. Look for a specific question, a step that's easy to undo and nothing published. No backup approver is named in the source, so learners shouldn't invent one.

What changes if…?

Denise is unavailable. The team procedure allows internal drafts, but nothing can be deployed without approval.

You could still prepare an annotated internal draft. The procedure allows that.
Write down the unanswered scope question so it's waiting when someone with approval is available.
Nothing is deployed. Nobody else has been given Denise's authority here, so don't assume someone has. If you're unsure, ask how approval works while she's away.

Participation options

Individual:: Learners sort known and undecided items, then draft one question or just think it through. Writing is optional.
Paired:: One partner plays Denise and answers only what the brief supports; the other asks the scope question.
Group:: Display the brief. List “known” and “not decided” together, then introduce Denise's absence and discuss what's still allowed.

Writing is optional; learners may think privately, discuss, or skip. Nothing is graded or collected. Source: Blueprint v3.0 · Section 30 · B2 Nobody Said No · p. 76.

SkillRise Spark · Companion · 8 / 8

Companion · optional “Try it your way” practice

Work out the timing, then say it plainly

Purpose. Discuss planning, communication, privacy and responding to constraints when a deadline is fixed.

Durable skills explored: Planning, Communication, Privacy, Responding to constraints.

This is a separate practice situation with a different launch week from your workday. The timings below are the only facts. Marcus has shared a private personal reason here too, but this practice doesn't say what it is and you don't need to know.

Source material (as learners see it)

Launch plan · Friday

Launch: Friday 15:00.
Copy must arrive before layout can begin.
Layout takes 2 hours. Checks take 1 hour after layout.
Marcus says copy may arrive Friday at 14:00.
A prepared shorter page is possible only if copy is approved by Friday 12:00 (noon).
Denise can change the scope.
Marcus has shared a private personal reason with you.

Times use the 24-hour clock, as in the launch plan.

Discussion prompts

Walk through the timeline: why is the full-page finish 17:00?
Why isn't the shorter page available with a 14:00 copy arrival?
How can you be honest about the risk without sharing why Marcus is late?

One possible response

Timing: copy at 14:00, layout 14:00–16:00, checks 16:00–17:00. A checked full page could be ready at 17:00, two hours after launch.

“Copy may arrive at 14:00, so a checked full page would be ready at 17:00. If copy could be approved by noon, we could launch the shorter page on time. Otherwise, could we move the launch? I'll check on the copy timing at 11:00.”

The example is one possible response. Look for the 17:00 finish, the shorter page offered only if copy is approved by noon, the decision left with Denise, and no private detail.

What changes if…?

Copy is confirmed for Friday 11:00, but the person who does the checks is only available from 14:00.

Layout (2 hours of work): 11:00–13:00.
Checks (1 hour of work): 14:00–15:00, the earliest the checker can start. The gap from 13:00 to 14:00 is waiting time, not work.
A 15:00 finish is possible, with no buffer at all, and only if the checker's 14:00 start is confirmed. That's worth flagging to Denise.

Participation options

Individual:: Learners draw the timeline on paper or on screen and draft an update, or talk it through without writing.
Paired:: One partner reads the launch plan aloud while the other marks a timeline; swap for the changed condition.
Group:: Draw a Friday timeline from 11:00 to 17:00 together. Place copy, layout and checks, then move copy to 11:00 and the checker to 14:00.

Writing is optional; learners may think privately, discuss, or skip. Nothing is graded or collected. Source: Blueprint v3.0 · Section 30 · B3 The Deadline That Won't Move · p. 77.