⭐ XP 0/0
⏱ 00:00
ASDAN Studio Β· Community Project Β· Week 4 of 6

Partner Update

BUILD Pathway Β· ASDAN Studio Β· Community evidence

Progress SoW Β· BUILD ASDAN AutΒ 1 Β· 2026–27 Β· Community evidence Β· Week 4πŸ… Banks: ASDAN/UAS community evidence
Spark: Partners deserve updates.

Success looks like

  • I can help prepare an update for our partner
  • I can report progress honestly, including problems
  • I can say what we need from them
Aspire Β· anticipate the partner's hardest question β€” and draft our answer.

Teacher Print Tools β€” Week 4

Retrieval Quiz

Arrival Task – What Do You Already Know?

1. Say it

Why tell our partner our progress?

Any honest answer counts β€” say it out loud.

2. Spot it

One good way to share an update?

Any honest answer counts β€” say it out loud.

3. Point to it

Point to what we'd show them.

Any honest answer counts β€” say it out loud.

Starter

Today at a Glance

Key Question: What are we building today β€” and where does the evidence go?
πŸ’‘

Big Idea

Partners deserve updates.

SPARK
🎲

Today We Play

Put it in order

GAME
🧱

The Wall Grows

Onto the Project Board (our partner sees it)

VOICE
πŸ…

It Banks

ASDAN/UAS community evidence

EVIDENCE

Talk first, then we play β€” every voice counts here.

I Do

The Model β€” Partner Update

Key Idea: Partners deserve updates.
Step 0 of 3

Why we keep our community partner updated.

Partners gave us their site and their trust β€” updates are the rent. An informed partner stays an ally; a surprised one becomes a doubter.

Preparing a short, polite progress update.

A good update is short, polite and honest: what's done, what's stuck, what's next. Three beats of news, no padding.

Using photos to show progress.

Photos carry progress better than promises β€” a picture of the sanded frame outweighs a paragraph about effort.

We Do

Put it in order

How it works: These belong in an order. Tap them one at a time β€” does each land where you expected?Found: 0/5
Choose the photos
Write one line each
Practise it politely
Share the update
Say thank you

I Do

Proving It β€” The Evidence Loop

Key Idea: Launch extension: one written line β€” the sentence you'd want our partner to repeat to someone else.
Step 0 of 3

Documentarian

photo/record the update.

Annotate

'we told our partner ___'.

Witness

staff tick 'helped update the partner', sign.

For the moderator, not just the folder

A tick says it happened. A witness statement says what you did. Before the photo is filed, the adult writes one sentence naming the thing they actually saw you do — and rings whether you did it Supported, Standard or Stretch.

That ring is the part that counts. It is the difference between “the class did this” and “this candidate did it, at this level, with this much help.” The witness sheet prints with every pack.

We Do

Skip One Step β€” What Breaks the Update?

Step 1: Tap a card, then its partner. Step 2: Watch the WAGOLL write itself. Score: 0/5
Choose the photos
Write one line each
Practise it politely
Share the update
Say thank you
Skip it and one person speaks for everyone
Skip it and the nerves do the talking instead of you
Skip it and the next ask is a harder one
Skip it and the work happened but nobody outside knows
Skip it and you're showing them a blurry pile of nothing

Photos chosenProblems includedTheir say invitedEvidence banked

Independent Work

Independent Work β€” Studio Time

Instructions: Work at your level. Evidence goes in your ASDAN portfolio β€” Documentarian photo + annotation + witness tick β€” ASDAN/UAS community evidence.
15:00

🀝 With support

Task: Choose the two progress photos that show real change, then build your update line from the printed sentence frames.

Steps: One step at a time β€” adult support is right there. Photo when you’re proud of it.

πŸ‘€ On your own

Task: Prepare a short progress update for our partner using our build photos and one next step.

Steps: Work the task through β€” photo as you go, annotate at the end, witness tick before you pack up.

πŸš€ Take it further

Task: Prepare a short progress update for our partner using our build photos and one next step. Stretch: anticipate the partner's hardest question β€” and draft our answer.

Steps: Task first, stretch second β€” and your annotation should explain the why, not just the what.

Lundy Loop

Lundy Loop β€” Your Voice on the Wall

Why: Article 12 β€” your view counts here, and it genuinely changes what happens next.

πŸšͺ SPACE

The Project Board is a real-stakes space β€” our partner sees it β€” but it's still safe: nothing goes up without your say-so, and 'pass' is allowed.

πŸ“£ VOICE

Say the line you think should go to the partner. Your words, not a form's.

πŸ‘₯ AUDIENCE

This one leaves the room for real β€” an actual person reads what we send.

⭐ INFLUENCE

The lines the room picks are the lines we send. Nothing gets rewritten behind you.

Exit Ticket

Exit Ticket

Instructions: Answer independently. Own words β€” no wall-peeking.

1.

I can help prepare an update for our partner β€” true for you today? Say how.

Point to today’s work as your proof.

2.

I can report progress honestly, including problems β€” true for you today? Say how.

Point to today’s work as your proof.

3.

I can say what we need from them β€” true for you today? Say how.

Point to today’s work as your proof.

Slide 1/10
πŸ…πŸ“ΈβœοΈ

Partner Update β€” banked!

Keep them informed βœ…

βœ“ I can help prepare an update for our partnerβœ“ I can report progress honestly, including problemsβœ“ I can say what we need from themβœ“ Onto the Project Board (our partner sees it): Say one thing you'd tell our partner. Today's outcome goes onto the P…Next lesson: Plan the Handover β€” present & install
⏸ MID-POINT PEER CHECK

Pens down β€” quick partner check!

πŸ“£ Show your partner where you’re up to. Check together against today’s success: I can help prepare an update for our partner and I can report progress honestly, including problems. If something’s missing, help them add it β€” kindly.

2 minutes max. Then I’ll resume the timer.