SP-T2 — Supplier Data Foundations — Synthesia Scripts (v1.0)
Conventions (as SP-T1)
- One
## Scene= one Synthesia scene. Presenter,[SCREEN CAPTURE](ZAYAZ UI), and[DOCUMENT CAPTURE](sample document anatomy) scenes are never mixed. - All sample documents are fictional Brenna Components A/S material. No real data, no real client names.
- Pace ~130 wpm. Plain words, short sentences, translation-ready.
- White-label variable
[CLIENT NAME]. Framing rule (hard): no line states or implies client motives; only platform-visible facts. - Work sessions (m003–m006) end with a DO-IT-NOW task card; the learner is expected to leave and come back.
- Self-checks: m002 and m007 only, 2 questions each, non-gating (questions included at module end).
- m006 contains a PLACEHOLDER segment pending the onboarding-requirements design (CoC + ESG minimum).
m001 — Welcome, Data Gatherer (target 4:00, ~510 words)
Scene 1.1 — The badge changed (presenter)
[ON SCREEN] Tier badge animation: "Tier 1 — ESG Curious" → "Tier 2 — Data Gatherer"
VO: Welcome back — and look at that. Your badge changed. You're now a Data Gatherer, and that's visible on the platform right now. You did that. The system responds to what you do — that's the whole idea, and it's about to get much more real.
Tier one was about understanding. This course is different. This one is about doing. By the end of it, your company's first real ESG dataset will be live — and your score will move because of it.
Scene 1.2 — How this course works (presenter)
[ON SCREEN] Loop graphic: "Watch (5 min) → Do (your pace) → Come back"
VO: So let me set expectations, because this course works differently. This is not a course you watch in one sitting — and honestly, if you try to, you're doing it wrong.
Each module here is a short work session. I explain one group of data — say, your energy numbers. I show you where they live in your own paperwork. I show you exactly where they go on the platform. And then you pause, go get that data, and enter it. Then you come back for the next module. Your checklist remembers everything, always.
Let me be straight about the effort, like I promised in tier one. The videos here are about forty minutes. The real work — finding bills, asking colleagues, entering numbers — is more like two to four hours in total. Spread it over days or weeks; nothing expires. At the end, something real exists that didn't exist before. And everyone who matters can see it.
Scene 1.3 — Your personal checklist (SCREEN CAPTURE)
[SCREEN CAPTURE] Tier 2 checklist in ZAYAZ, personalized from a demo Snapshot: fast lane on top
VO: Here's your best friend for this course: your checklist. If you completed the Data Snapshot in tier one, this list is already personal. Everything you said you have sits at the top — your fast lane. Quick wins first. Below that, the items you weren't sure about, each with a hint on where that document usually lives. And at the bottom, the things you don't have yet — each with the simplest way to start.
If you skipped the Snapshot, no problem — the checklist shows the standard list, and there's a two-minute link right here to make it personal. Worth doing before anything else.
Scene 1.4 — The finish line (presenter)
[ON SCREEN] Completion card: "Dataset live = 6 data points · all three areas · published"
VO: And here's the finish line, so it never feels vague. This tier is complete when your dataset is live: at least six data points entered — a few environmental, a couple social, at least one governance — each with a source, and the whole thing published. That's it. No exam. No waiting. The moment your data goes live, tier three unlocks.
Six numbers. You have more than that in your inbox right now. Let's go find them — but first, one short module on what makes a number good enough to publish. It's the five minutes that makes everything else easier.
m002 — What makes a number defensible (target 5:00, ~640 words)
Scene 2.1 — The fear (presenter)
[ON SCREEN] Text: "What if my number is wrong?"
VO: Before we touch any data, let's deal with the fear that stops most companies — the quiet worry: what if my number is wrong? What if a customer checks it? What if it looks bad?
Here's the professional answer: nobody expects your numbers to be perfect. What they expect is that your numbers are defensible. And defensible is a much friendlier standard than perfect. It means: if someone asks "where does this number come from?" — you have an answer. That's it. Four things make a number defensible. Let me give you all four.
Scene 2.2 — Real source (presenter)
[ON SCREEN] Quality 1 card: "A real source" — bill icon vs thought-bubble icon
VO: One: a real source. The number comes from a document — a bill, a log, a payroll report — not from memory. "Our electricity was about fifty thousand kilowatt hours, I think" is a memory. The same figure read off your energy statement is a data point. Same number, completely different strength.
Scene 2.3 — Defined period (presenter)
[ON SCREEN] Quality 2 card: "A defined period" — calendar with 12 months highlighted
VO: Two: a defined period. Every number answers the question "when?" Fifty thousand kilowatt hours — over which twelve months? Calendar year? Your financial year? The platform asks you to set your reporting period once, and then every number lives inside that same window. Mixing periods is the most common data mistake there is — and setting the period first is the complete cure.
Scene 2.4 — Consistent unit (presenter)
[ON SCREEN] Quality 3 card: "A consistent unit" — kWh vs MWh mismatch visual
VO: Three: a consistent unit. Kilowatt hours or megawatt hours. Litres or cubic meters. Kilograms or tonnes. It genuinely doesn't matter which — what matters is you pick once and stay consistent. A thousand-fold error from a unit mix-up looks careless in a way an honest estimate never does. The platform shows the expected unit on every field; when your bill uses a different one, convert before you type.
Scene 2.5 — Repeatable method (presenter)
[ON SCREEN] Quality 4 card: "A repeatable method" — arrow looping year to year
VO: Four: a repeatable method. Ask yourself one question: could I produce this same number the same way next year? If yes — your method is repeatable, and next year's update takes minutes instead of hours. If no — you got a number once, but not a process. The checklist quietly builds this for you: where you found it this year is where you'll find it next year.
Scene 2.6 — The estimate preview + module 7 signpost (presenter)
[ON SCREEN] Two labels: "Flagged estimate ✓ defensible" / "Unflagged guess ✗ not"
VO: One more thing, and it's important. Sometimes the exact number doesn't exist — no separate meter, no old records. For that, there's a proper tool: the honest estimate. A number built from what you do know, with the assumption written down, and flagged as an estimate on the platform. A flagged estimate is fully defensible. An unflagged guess is not. The flag is the difference.
Module seven teaches the method properly. So here's your standing instruction for this whole course: if you hit a wall in any module — a number you can't find — don't stall, and don't skip. Jump to module seven. It's the rescue module, and it's there for exactly that moment.
Right — four qualities, one rescue plan. Quick self-check, and then we go get your first live data.
m002 self-check (non-gating, 2 Q)
- You remember roughly what last year's fuel cost. Is that a defensible data point? — No, not yet ✔ (A memory isn't a source. Pull the fuel card statement or accounting entry — then the same figure becomes defensible.) / Yes, close enough (Close isn't the standard — sourced is. The statement takes minutes to find and makes the number solid.)
- You can't find a separate heating figure anywhere. Best move? — Leave the field empty (Empty is the weakest state — and module 7 exists so you never need it.) / Build a flagged estimate using module 7's method ✔ (Exactly. Flagged estimates are defensible and score better than empty fields.)
m003 — Energy, fuel & heating: your first live data (target 6:00, ~760 words)
Scene 3.1 — Why these numbers (presenter)
[ON SCREEN] Title: "Energy — everyone's first win" + field icons
VO: We start with energy — deliberately. Almost every company on earth has an energy bill, the number on it is unambiguous, and for most businesses energy is the biggest piece of their environmental footprint. It's also the number your customers' own reports need most. One bill, and you're on the board. This module: electricity, fuel, and heating. By the end of it — and I mean today, this session — your first data point will be live.
Scene 3.2 — Bill anatomy: electricity (DOCUMENT CAPTURE)
[DOCUMENT CAPTURE] Brenna Components A/S electricity statement, zoom guided by highlights
VO: Here's an electricity statement — this one belongs to Brenna Components, our example company, so we can stare at it freely. Every energy bill in every country has the same three citizens living somewhere on it. First: consumption — here. That's the kilowatt-hour figure, and that's your number. Not the cost — the consumption. Second: the period — here. This statement covers one quarter, so Brenna needs four of these, or better, the annual summary from the supplier's web portal — one download, twelve months, done. Third: the meter or site reference — here. That matters only if you have more than one location: then it's one number per site, added together, and you note that.
Cost is fine to know — but the platform asks for consumption, because prices change and kilowatt hours don't lie.
Scene 3.3 — Fuel and heating anatomy (DOCUMENT CAPTURE)
[DOCUMENT CAPTURE] Brenna fuel card statement, then heating invoice; highlights per figure
VO: Fuel next. If you have fuel cards, the card provider's statement lists litres per fill-up — and usually a period total, right here. That total is your number. No fuel cards? Your accounting system knows every fuel purchase; the checklist hint shows you what to search for. Vehicle leasing companies often report fuel per vehicle too — one email.
Heating: if you buy gas, oil, or district heating, there's an invoice with a consumption figure — same anatomy as electricity, here. Two special cases. If your heating is electric, it's already inside your electricity number — so you mark it that way and never count it twice. And if your landlord provides heat, you ask the landlord for the annual figure or your share. Can't get either? That's a module-seven case — the building-size estimate — and it's the most common estimate in this entire field. You'd be in good company.
Scene 3.4 — Entering it (SCREEN CAPTURE)
[SCREEN CAPTURE] ZAYAZ basic reporting, E section: period set, electricity field entry with unit + source note, save
VO: Now watch how entering works, start to finish — this exact pattern repeats for every field in this course. First, the reporting period — set once, here, and every number after this lives in that window. Then the electricity field: the number — check the unit next to the field, convert if your bill differs — and then the source note, right here: "annual statement, supplier portal." One line. That line is what makes the number defensible, and it's next year's treasure map. Save. That's a live data point — your first.
Fuel field, heating field — same dance: number, unit, source. And if heating is electric or landlord-provided, this selector here is where you mark it.
Scene 3.5 — DO IT NOW (presenter)
[ON SCREEN] Task card: "① Set your reporting period ② Find your energy statement ③ Enter electricity — number · unit · source ④ Fuel & heating if at hand — or flag for module 7"
VO: Your turn — this is a pause point, and taking it is doing the course right. Set your period. Get your energy statement — the supplier portal is the fast route. Enter electricity: number, unit, source note. If fuel and heating are within reach, take them too; if not, the checklist remembers what's open.
Ten to twenty minutes, most companies. When your first number is in — and it will feel surprisingly good — come back. Waste, water, and travel are next, and they're faster than what you just did.
m004 — Waste, water & travel (target 5:00, ~630 words)
Scene 4.1 — Setup (presenter)
[ON SCREEN] Title: "Three smaller numbers — same pattern"
VO: Welcome back — one data point richer, I hope. This session: waste, water, and travel. Three smaller numbers, same pattern every time: find the document, read the figure, enter it with unit and source. And this module includes your likely first meeting with a real estimate — a friendly one.
Scene 4.2 — Waste anatomy (DOCUMENT CAPTURE)
[DOCUMENT CAPTURE] Brenna waste contractor invoice: container size, frequency, weight line highlighted in turn
VO: The waste invoice, from your waste contractor. Sometimes you get lucky: a weight line, right here — kilos collected. That's your number, straight in. But often the invoice shows something else: container size and how often it's emptied — here and here. A volume, not a weight. The platform wants weight — so this is estimate territory, and here's the honest version in one breath: container size, times collections per year, times a standard weight factor for your waste type — the platform provides the factor. Enter the result, flag it as an estimate, write the assumption in the source note. Done — defensible. And the upgrade path is one email: waste contractors produce annual weight summaries on request, usually free. Ask once, and next year the estimate becomes a real figure.
Scene 4.3 — Water and travel anatomy (DOCUMENT CAPTURE)
[DOCUMENT CAPTURE] Brenna water bill, then an expense-system travel export
VO: Water is the easy one — the utility bill shows cubic meters, here. Renting, with water in the service charge? Ask the landlord for your share; if that fails, module seven has a headcount-based bridge.
Travel: you do not need every boarding pass. An export from your expense system — everything tagged travel — is a legitimate source at this tier. Totals are enough: flights, hotels, mileage claims. Here on Brenna's export: the annual mileage total, the flights list. Perfect trip-level data is a later refinement, not today's standard.
Scene 4.4 — Entering all three (SCREEN CAPTURE)
[SCREEN CAPTURE] ZAYAZ E section: waste entry with estimate flag toggled + assumption in source note; water; travel
VO: Entering — and note the new move: the estimate flag. Waste: the calculated figure, and this toggle right here marks it as an estimate; the assumption goes in the source note — "1,100-litre container, weekly, standard factor." Water: number, unit, source — nothing new. Travel: the export totals, source note "expense system export." Three more fields live. Look at the E section now — it's starting to look like a company that knows itself.
Scene 4.5 — DO IT NOW (presenter)
[ON SCREEN] Task card: "① Waste — weight, or volume→flagged estimate ② Water — bill or landlord ③ Travel — expense export ④ Stuck? → module 7"
VO: Your session: waste, water, travel. Grab the waste invoice first and decide — weight line, or estimate. Then water, then the travel export. Fifteen minutes if the documents are near, and every one of these has a module-seven bridge if they're not.
Next time: we move from meters and bills to people — and I'll tell you why a zero can be one of the most valuable numbers you publish.
m005 — People data (target 5:00, ~640 words)
Scene 5.1 — What S data is and isn't (presenter)
[ON SCREEN] Title: "Your people, in numbers" + shield icon: "Aggregate only — never individuals"
VO: Now the S in ESG — your people. And I want to remove a worry before it forms, because at small companies this question always comes quietly: are we reporting on our employees? No. Not individuals — aggregates. The platform asks how many people, how safe, how trained. It never asks for names, salaries, or anything about any single person. Numbers about the workforce, never about a person. Say that to anyone who asks — it's a platform rule, not a preference.
Scene 5.2 — Headcount (DOCUMENT CAPTURE)
[DOCUMENT CAPTURE] Brenna payroll summary: headcount and contract-type split highlighted
VO: First field: headcount. Your payroll knows this to the person — here on Brenna's payroll summary: total employees, and the split — full-time, part-time, temporary. Pick a counting date — end of your reporting period is the natural one — note it in the source, and this becomes the easiest defensible number in the whole dataset. Under twenty people and no payroll system? A dated one-page list, signed by whoever runs the company, is a legitimate record. Write it today.
Scene 5.3 — Zero is data (presenter + DOCUMENT CAPTURE mix, keep as two scenes)
Scene 5.3a (presenter): [ON SCREEN] Two cards: "No log" (grey, "= no data") vs "Log showing 0 incidents" (green, "= excellent data")
VO: Safety next — and here's the teaching moment of this module. Suppose you've had no workplace accidents. Wonderful. But listen carefully: no accident log and a log showing zero accidents are completely different things. No log means no data — nothing to report, nothing to score. A log that exists and shows zero? That's a reportable fact — and an excellent one. Zero is data — but only if the log exists. If you don't have one: start it today. One page. Date, what happened, action taken. An empty log, maintained, is a valid and valuable record from day one.
Scene 5.3b (DOCUMENT CAPTURE): [DOCUMENT CAPTURE] Brenna one-page incident log, including a "no incidents this quarter" entry
VO: Here's Brenna's — one page, and look: a quarterly entry saying "no incidents." That entry is the habit that makes the zero defensible. Many industries already require an incident register by law — check whether yours exists before creating a new one; it may just be wearing a different name.
Scene 5.4 — Training + policy, and entering (SCREEN CAPTURE)
[SCREEN CAPTURE] ZAYAZ S section: headcount entry, incidents entry, training entry, policy reference
VO: Training records: certificates, safety briefing sign-offs, onboarding checklists — scattered is normal; one folder turns them into a record, and the annual count goes here. And your working-conditions policy — an employee handbook or contract annex counts — gets referenced here.
Entering the S section: headcount with its counting date. Incidents — the number, even when the number is zero, source "incident log." Training count. Policy reference. Same pattern as always: number, unit where it applies, source note. Two of these fields, and your gate minimum for S is met.
Scene 5.5 — DO IT NOW (presenter)
[ON SCREEN] Task card: "① Headcount from payroll — with counting date ② Safety log — find it or start it (empty is fine) ③ Training + policy if at hand"
VO: Your session: headcount first — one question to payroll. Then the safety log: find the one that exists, or start one today and enter your honest zero. Training and policy if they're within reach. Next module: governance — the section everyone fears and nobody should, because most of it is fifteen minutes and one page.
m006 — Governance (target 5:00, ~640 words)
Scene 6.1 — Governance demystified, again (presenter)
[ON SCREEN] Title: "Writing down what you already know"
VO: Governance — the G — and let's carry forward the tier-one reframe, because it's the whole module in one line: governance is writing down what the owner already knows. Who owns the company. Who decides what. Which rules you follow, on paper. At a fifty-person company this exists in systems; at a five-person company it exists in someone's head. Both are real — only one is reportable. Today we make yours reportable.
Scene 6.2 — The one-page responsibility note (DOCUMENT CAPTURE)
[DOCUMENT CAPTURE] Brenna's one-page ownership & responsibility note
VO: Exhibit one: Brenna's ownership and responsibility note. One page. Who owns the company — with the company registry as the source, here. Then five lines: who is responsible for safety, finances, quality, personnel, and this platform. That's it. This document takes fifteen minutes with the owner and a cup of coffee, and it's a fully legitimate governance record. If you have an org chart somewhere — even in an old pitch deck — that counts too. But don't wait for a beautiful chart; the one-pager wins on existence.
Scene 6.3 — Code of conduct [PLACEHOLDER — pending onboarding-requirements design] (presenter)
[ON SCREEN] TBD per onboarding design
VO: [PLACEHOLDER — script this segment after the CoC + ESG-minimum onboarding design is settled. Must cover: (a) the code of conduct accepted at platform onboarding and where it lives; (b) the distinction from the supplier's own code, if any — e.g. one signed for a large customer, which counts and is worth filing; (c) entry/reference on the platform. Keep to ≤60 seconds. Framing rule applies. No template offer.]
Scene 6.4 — Suppliers, certificates, insurance (DOCUMENT CAPTURE)
[DOCUMENT CAPTURE] Brenna vendor-list export (top rows), certificate, insurance policy front page
VO: Three quick items. Your own supplier list: your accounting system exports your vendors in one click — sorted by spend, the top ten to twenty is the useful core, like Brenna's here. And keep this list warm: much later in this programme, it becomes the seed of your own supplier ecosystem. That's all I'll say — for now.
Certificates: ISO, industry, product — they tend to live framed on walls and in sales folders. Collect the digital copies, check the expiry dates while you're at it. And having none is a valid answer at this tier — record it honestly. Insurance: your broker resends current policy documents same-day; it's one email.
Scene 6.5 — Entering + uploading (SCREEN CAPTURE)
[SCREEN CAPTURE] ZAYAZ G section: responsibility note upload, supplier count entry, certificate upload with expiry, insurance upload
VO: The G section works like everything else, with one addition: uploads. Your responsibility note — uploaded here, and that's a governance data point live. Supplier list: the count goes here, the export can be attached. Certificates: upload, and note the expiry date in this field — the platform will remind you before it lapses. Insurance: same. Notice these uploads are included in your free tier — the further you've come in this programme, the more the platform does for you. One governance point meets your gate minimum; you now likely have several.
Scene 6.6 — DO IT NOW (presenter)
[ON SCREEN] Task card: "① Responsibility note — 15 min with the owner ② Vendor export — one click ③ Certificates & insurance — collect and upload"
VO: Your session: the one-pager first — fifteen minutes, and it might be the highest value-per-minute document in this course. Then the vendor export, then certificates and insurance as you find them. And with that — look at your checklist — you have data in all three sections. Which means the next stop is the finish line. Almost. First, the rescue module — and even if you never got stuck, give it five minutes. It's where data confidence comes from.
m007 — When you don't have the number (target 5:00, ~640 words)
Scene 7.1 — Permission to estimate (presenter)
[ON SCREEN] Title: "The honest estimate" + the one-way ladder: empty → flagged estimate → real source
VO: This is the rescue module — for every wall you hit in modules three to six, and for walls you'll hit in years to come. Let's start with the permission, because someone needs to say it clearly: estimating is not cheating. Professional sustainability teams at the world's largest companies estimate constantly — there is a whole discipline for it. What separates professional estimation from guessing is method and honesty. Four steps. And one direction of travel: flagged estimates beat empty fields, real sources beat estimates. The ladder points one way — up.
Scene 7.2 — The method (presenter)
[ON SCREEN] Four steps building: "Base → Assumption → Calculation → Flag"
VO: The method. Step one: the base — something you do know. Your building's size. Your headcount. Your spend. Step two: the assumption — the bridge between what you know and what you need, written down. Step three: the calculation — simple, and simple is a feature: an estimate you can explain in one sentence is an estimate that survives questions. Step four: the flag — mark it as an estimate on the platform, assumption in the source note. That flag converts a guess into a defensible data point. Skipping the flag converts your honest work back into a guess. Never skip the flag.
Scene 7.3 — Worked example one: heating (presenter)
[ON SCREEN] Calculation card: base (m²) × assumption (kWh/m²/yr, platform default) = flagged estimate
VO: Worked example one — the most common estimate in this field: heating, with no separate meter. Base: your heated floor area — the lease agreement knows it. Assumption: a typical heating consumption per square meter for your building type — the platform provides a standard default, so you're not inventing physics. Calculation: multiply. Flag it, note it: "estimated from 400 square meters at standard factor; no separate meter." Fully defensible — and the source note has already told next year's you exactly what would make it better: a landlord figure, or a meter.
Scene 7.4 — Worked example two: travel (presenter)
[ON SCREEN] Calculation card: expense total ÷ average cost assumption = flagged estimate
VO: Worked example two: travel, where the expense system gives you money but not kilometers. Base: the annual travel spend, split flights versus driving if you can. Assumption: an average cost per flight, or the mileage reimbursement rate — which converts money back into distance. Calculation: divide. Flag it: "estimated from expense totals at standard rates." Is it precise? No. Is it defensible, useful, and better than an empty field? Completely. And the upgrade path is built in: next year, export trips instead of totals.
Scene 7.5 — What can't be estimated — only started (presenter)
[ON SCREEN] Text: "Some things can't be estimated — only started." + example: safety log
VO: Now the honest limit. Some things can't be estimated — only started. You cannot estimate a safety record into existence, or back-calculate a policy. If it's a record-keeping thing you've never kept — the move is not a formula. The move is: start today. A log started this month means that next year, this item sits in your fast lane. And hear this clearly, especially if your Snapshot had a long "don't have" column: that's not falling behind. That is how every documented company on this platform began — including, once upon a time, the large ones sending the questionnaires.
Scene 7.6 — Close (presenter)
[ON SCREEN] The ladder again: empty → flagged estimate → real source
VO: So: no more walls. Everything from here is either found, estimated, or started. Quick self-check — then we go make it official.
m007 self-check (non-gating, 2 Q)
- Your waste invoice shows container volume, not weight. You calculate weight using the standard factor and enter it. What's the one step that makes this defensible? — Rounding the result (Rounding isn't the issue — honesty about method is.) / Flagging it as an estimate with the assumption in the source note ✔ (Exactly. The flag plus the written assumption is what turns a calculation into a defensible data point.)
- You've never kept a training record. Best move? — Estimate last year's training hours (This one can't be estimated — records of events need records. It can only be started.) / Start the record today and build it forward ✔ (Right. Started today means fast lane next year — that's how every documented company began.)
m008 — Going live (target 4:00, ~500 words)
Scene 8.1 — The review (SCREEN CAPTURE)
[SCREEN CAPTURE] ZAYAZ dataset review screen: entries listed with sources and estimate flags, gate status showing "ready"
VO: This is the moment the whole course has been building toward. Here's your dataset review — every number you've entered, its source, its flags. Give it one honest pass: does each number have its source note? Are the estimates flagged? Is everything inside your reporting period? This indicator here confirms you've met the minimum — data in all three sections. Green means one thing left to do.
Scene 8.2 — Publish (SCREEN CAPTURE — the payoff scene; unhurried, protected)
[SCREEN CAPTURE] The publish action → score updates on screen in real time
VO: Ready? This button — publish. Watch your score.
[Direction: 2–3 seconds of silence; let the score movement play uncut.]
There it is. That movement just happened because of data you found, you structured, and you made live. Not a consultant. Not an algorithm guessing about your company. You. Your company has just moved from unreported to documented — and on this platform, that's the difference that matters most.
Scene 8.3 — What's now visible (SCREEN CAPTURE)
[SCREEN CAPTURE] Demo client dashboard: score moved, badge "Tier 2 — Data Gatherer", data status current
VO: And here's what's visible now, on the client side — same demo view as always, so you never have to guess. The score: moved. The badge: Data Gatherer, earned the moment you publish. Data status: current. [CLIENT NAME] can see this — and so can any client you share your profile with, today or in five years. Remember tier one: answer once, share everywhere. What you built these past sessions is the "once."
Scene 8.4 — Tier complete (presenter)
[ON SCREEN] Completion card: "Tier 2 complete → Tier 3 unlocked" + unlock animation
VO: Publishing was the finish line — so if you've done it, hear it properly: tier two, complete. No exam needed; the data is the exam, and it's live. Tier three — Target Setter — is already unlocked. One short module left in this course: how to keep what you've built alive with half an hour per quarter. Don't skip it — it's the module that protects everything you just did.
m009 — Keeping it alive (target 3:00, ~390 words)
Scene 9.1 — The quarterly half hour (presenter)
[ON SCREEN] Calendar card: "Data care — 30 min, 4× a year" with three checkboxes: new bills in · numbers updated · estimates upgraded
VO: Data has one enemy: time. A dataset published once and never touched slowly turns from an asset back into a question mark. The fix is small and boring, and I mean that as a compliment: one recurring calendar slot — thirty minutes, once a quarter, name it "data care." Three checkboxes. New bills and statements in. Numbers updated. And one look at your estimates: has real data arrived that can replace one? Remember the ladder — estimates were bridges. Each quarter, try to retire one. That's the whole routine. Put it in the calendar before this video ends — genuinely, pause and do it. Future you says thanks.
Scene 9.2 — The automation glimpse (SCREEN CAPTURE — the fence, shown once, ~90 seconds)
[SCREEN CAPTURE] ZAYAZ automated collection: connected sources feeding fields, auto-updates, estimate-replacement suggestion
VO: Before we close, let me show you something — not something you need, something worth knowing exists. Everything you did by hand in this course — finding statements, reading figures, entering, updating — can also run by itself. This is ZAYAZ automated collection: sources connected once, fields that update themselves, and — my favorite — the platform noticing when real data can replace one of your estimates, and suggesting the swap. Everything you just learned, running on rails. That's part of the ZAYAZ subscription; if it looks interesting, the details live under Plans on the platform. That's all I'll say — you came here to get your data live, and you did that on your own steam.
Scene 9.3 — Bridge to Tier 3 (presenter)
[ON SCREEN] End card: "Next: Tier 3 — Target Setter" + co-brand lockup + EcoWorld Academy lockup
VO: So here you stand: documented, published, visible — a Data Gatherer in fact, not just in badge. Which raises the natural next question: now that you have data... where should it go? Numbers become powerful when they point somewhere. In tier three, you'll set a target — not a slogan, a real one: sized for your company, built on the data you just published, and defensible in front of any client who asks. It's unlocked. It's waiting. See you there.
Production notes
- Scene isolation: all
[SCREEN CAPTURE]and[DOCUMENT CAPTURE]scenes are separately recorded. UI-dependent scenes: 1.3, 3.4, 4.4, 5.4, 6.5, 8.1, 8.2, 8.3, 9.2. Document scenes depend only on the Brenna sample pack (stable). - Sample pack dependency (§8 of spec): Brenna Components A/S — electricity statement, fuel card statement, heating invoice, waste invoice, water bill, travel expense export, payroll summary, incident log page, responsibility note, vendor-list export, certificate, insurance front page. Twelve fictional documents; produce before recording document scenes.
- PLACEHOLDER: m006 Scene 6.3 (code of conduct) awaits the onboarding-requirements design. All other scenes in m006 are recordable; the module assembles once 6.3 lands.
- m008 Scene 8.2 direction: the score movement plays uncut with a beat of silence — this is the course's payoff; do not compress in edit. Depends on the platform requirement: synchronous score update on publish.
- Platform-behavior dependencies to verify at recording: checklist personalization view (1.3), estimate flag + source note UI (4.4), heating "included in electricity / landlord" selector (3.4), upload flows with expiry reminder (6.5), gate-status indicator (8.1), Plans location (9.2).
[CLIENT NAME]occurrences: m008 (×1) + co-brand lockups (m001 open if used, m009 end card). Deliberately fewer than SP-T1 — this course is about the supplier's own work.- Framing-rule audit: client-side references (8.3) state only what is visible on the dashboard. No motive language anywhere.
- Fallback texts: m001–m009.md derive from these scripts → R2
fallback_text/SP-T2/; document-capture scenes convert to figure descriptions of the Brenna samples.