Gauth Finals Week Campaign Sprint

Coordinate a Gauth campaign with tracking, creative assets, revisions, and QA.

Introduction

30 Second Summary

Finals week campaigns move fast. One missed deadline or one unverified claim can turn launch day into a scramble.

In this project, you will coordinate the fictional Finals Week Confidence campaign as Gauth's Marketing Coordinator. You will turn an incomplete brief into a launch-ready package while keeping every deadline, revision, claim, and approval visible.

What You'll Build

Your finished workspace gives a manager everything needed to approve the campaign at a glance: the live plan, verified message, finished creative, and launch decision.

By the end of this project, you'll have:

  • A campaign tracker that lets you spot blockers, trace revisions, and see who owns each deadline or approval.
  • A coordinated campaign package that you can present through a four-slide deck, three campaign graphics, campaign copy, and stakeholder messages.
  • A launch handoff where every claim, link, filename, date, and approval passes quality assurance. Clear version control preserves the revision trail.
  • Secret Mission: Respond to an executive who requests an unsupported performance claim minutes before launch. Document an evidence-based go or no-go decision without silently changing the approved assets.

Are there any prerequisites?

Your confirmed Google account covers Google Drive. Your confirmed Canva account completes the prerequisites because no Gauth account is required.

Before We Start

Before the hands-on work begins, commit to treating this exercise as a live campaign coordination simulation. Your statement will anchor every decision to launch readiness.

Set Up the Campaign Workspace

Campaign deadlines become fragile when briefs, feedback, and assets live in separate places. One Google Drive workspace keeps every working file and handoff visible.

This step creates one home for the campaign from planning through handoff. Canva Free stays ready in a separate tab for later creative work.

In this step, get ready to:
  • Create the campaign folder structure in Google Drive.
  • Create blank files in Google Sheets, Google Docs, and Google Slides.
  • Prepare a free Canva workspace for manual creative production.
Create the Drive structure

The main folder gives the campaign a clear boundary. Its two subfolders separate active work from materials prepared for handoff.

  • Enter https://drive.google.com in your browser's address bar.
  • Press Enter to load Google Drive.
  • Sign in with your Google account if Drive asks you to authenticate.
  • Click New in the upper-left corner.
  • Select New folder.
  • Enter Gauth_Finals_Week_Campaign_Simulation as the folder name.
  • Press Enter to create the folder.
  • Double-click Gauth_Finals_Week_Campaign_Simulation to open it.

You should see an empty Gauth_Finals_Week_Campaign_Simulation folder. This folder now defines the boundary of your campaign workspace.

  • Click New inside the campaign folder.
  • Select New folder.
  • Enter Working Files as the folder name.
  • Press Enter to create the folder.
  • Click New again.
  • Select New folder.
  • Enter Handoff as the folder name.
  • Press Enter to create the folder.

You should now see Working Files beside Handoff. The Handoff folder stays empty until campaign materials are ready for delivery.

Create and name the campaign files

Clear file names make the tracker, brief, and deck easy to locate under deadline pressure. Each blank file establishes a named home for work completed in later steps.

  • Double-click Working Files to open it.
  • Click New.
  • Select Google Sheets from the document types.
  • Click Untitled spreadsheet at the top of the new file.
  • Enter 01_Campaign_Tracker as the file name.
  • Press Enter to apply the name.
  • Return to the Working Files browser tab from earlier.

You should see 01_Campaign_Tracker listed inside Working Files.

How does automatic saving help?

Google automatically saves online changes as you type. Clear file names give the campaign an understandable structure without a separate save process.

  • Click New inside Working Files.
  • Select Google Docs from the document types.
  • Click Untitled document at the top of the new file.
  • Enter 02_Working_Brief_and_Copy as the file name.
  • Press Enter to apply the name.
  • Return to the Working Files browser tab from earlier.

You should now see 02_Working_Brief_and_Copy beside the campaign tracker.

  • Click New inside Working Files.
  • Select Google Slides from the document types.
  • Click Untitled presentation at the top of the new file.
  • Enter 03_Stakeholder_Deck as the file name.
  • Press Enter to apply the name.
  • Return to the Working Files browser tab from earlier.

Good progress. The three core working files now have named homes inside the same campaign folder.

Keep the simulation label visible

Every deliverable must carry Practice simulation. Not for publication. in its notes. This label keeps the fictional campaign standards separate from public Gauth statements.

You will add the label as each blank file gains content. The same requirement applies to every later asset and handoff note.

  • Compare the names in Working Files with 01_Campaign_Tracker, 02_Working_Brief_and_Copy, and 03_Stakeholder_Deck.

Missing or misplaced a file?

  • Check that you returned to Working Files before creating each file.
  • Use the file name at the top of an open Google file to correct any spelling difference.

Ask for help with a missing campaign file.

Prepare the creative workspace

Canva provides the workspace for the three campaign graphics. A paid-trial prompt can feel like a required part of setup.

The free workflow supports this simulation without an upgrade. Each format will use a blank design or free template.

  • Press Cmd+T (macOS) or Ctrl+T (Windows) to open a second browser tab.
  • Enter https://www.canva.com in the address bar.
  • Press Enter to load Canva.
  • Sign in with your Canva account if the site asks you to authenticate.
  • Decline any invitation to start a paid trial.
  • Confirm your account profile is visible on the Canva home screen.

How will the free design workflow work?

Canva Free supports social designs created from blank canvases or free templates. You will build the landscape, square, and vertical formats separately.

Choose only templates and elements identified as free. Manual format adaptation keeps the workflow clear of paid resizing tools.

Seeing a payment prompt?

A payment prompt can indicate that a selected template or element requires payment. Keep the project free by returning to the picker and choosing an option identified as free.

Ask for help identifying a free Canva option.

Before the final check, picture the folder count and file count you expect to see.

  • Return to the Gauth_Finals_Week_Campaign_Simulation folder from earlier.
  • Confirm that Working Files and Handoff are visible.
  • Open Working Files.
  • Confirm that the three named Google files are visible together.
  • Switch back to the Canva browser tab.
  • Confirm that Canva shows your signed-in home screen.

You should see two campaign subfolders in Drive. Inside Working Files, you should see the blank tracker, brief, and deck with their exact names.

Canva should remain open in a separate browser tab under your signed-in account. Your campaign workspace is now ready for controlled planning and manual free-format design.

Your campaign hub is ready. Next, you will audit the incomplete brief and turn its open questions into a controlled timeline.

Audit the Brief and Control the Timeline

Your Google Drive workspace gives every campaign file a clear home. That structure makes the incomplete request easier to investigate.

The Google Docs brief will hold the evidence. The Google Sheets tracker will turn that evidence into accountable work.

The request contains conflicting launch dates. It also omits decisions that affect approval.

Starting production with those gaps would create rework. It would also make the launch date unreliable.

In this step, get ready to:
  • Annotate Simulation Packet A with questions, risks, and contradictions.
  • Build a tracker that exposes priorities, dependencies, owners, approvals, and blockers.
  • Use a clarification message to resolve the initial decision blockers.
Audit Simulation Packet A

A campaign briefing gives production work its boundaries. A brief audit separates confirmed facts from assumptions before those assumptions spread into assets.

  • Switch back to the Google Drive browser tab from earlier.
  • Open the Working Files folder.
  • Open 02_Working_Brief_and_Copy.
  • Add the packet header and campaign facts by pasting this text into the document:
Simulation Packet A
Practice simulation. Not for publication.

Campaign context:
Campaign: Finals Week Confidence
Audience: College students preparing for final exams
Objective: Build awareness and drive qualified clicks to Gauth's official download page
Channels: Organic social media and a student email placement
Budget: No paid media
Deliverables: Four-slide stakeholder deck, landscape promotional graphic, square social post, vertical Story asset, two captions, one email subject line, and launch handoff

Conflicting information:
Marketing calendar launch: Thursday at 12:00 PM
Manager email launch: Friday at 3:00 PM
Primary call to action: Missing
Final approver: Missing
Designer availability: Unconfirmed after Thursday morning

What does this packet establish?

  • The campaign context defines the audience, objective, channels, budget, and deliverables.
  • The conflicting information exposes decisions that could change the schedule or approval path.
  • Review the pasted text for missing lines.
  • Wait for Google to finish saving 02_Working_Brief_and_Copy automatically.

Did the packet lose its line breaks?

Undo the paste if the packet appears as one continuous line. Paste it again at the start of an empty paragraph.

If the formatting still looks wrong, help me restore the structure of Simulation Packet A in Google Docs.

The next section creates a claim verification boundary. Every public product statement must trace back to evidence in this source card.

  • Place your cursor below the conflicting information.
  • Add the claim candidates and verified source card by pasting this text:
Claim candidates supplied by the fictional requester:
AI homework helper
Step-by-step solutions
Detailed explanations
Ace every exam instantly
Guaranteed better grades
Real experts online 24/7

Verified public source card:
Gauth publicly uses Your AI Homework Helper.
Gauth publicly describes Step-by-step solutions.
Gauth publicly describes Detailed explanations.
Gauth publicly states Real experts online 24/7.
Official campaign destination: https://www.gauthmath.com/download

How should you use the source card?

  • The source card defines which public product statements have supporting evidence.
  • Each claim candidate needs an evidence status before it reaches campaign copy.
  • Compare every claim candidate with the verified source card.
  • Confirm that the official campaign destination ends in /download.

Unsure whether a claim is supported?

Match the full meaning of the candidate with the source card. A product feature does not provide evidence for a guaranteed academic outcome.

If the distinction still feels unclear, help me compare a campaign claim with the verified Gauth source card.

The simulation brand sheet controls the visual system for this exercise. It does not represent Gauth's real internal brand guidance.

  • Place your cursor below the verified source card.
  • Add the simulation-only brand sheet by pasting this text:
Simulation-only brand sheet:
Palette: violet #6C5CE7
Palette: mint #2DE2A6
Palette: dark navy #182033
Palette: off-white #F7F8FC
Wordmark: Use the typed word Gauth. Do not download an unofficial logo.
Typography: Select one sans-serif family available in both Canva and Google Slides. Use no more than two weights.
Layout: Use one clear focal point.
Layout: Use high contrast.
Layout: Use a short headline.
Layout: Use consistent call-to-action treatment.
Restriction: Do not publish the simulation or imply that the fictional standards are Gauth's real internal brand guide.

What does the brand sheet control?

  • The palette and typography rules create a repeatable visual system.
  • The restriction keeps the fictional standards clearly separated from Gauth's public identity.
  • Review the palette entries for all four color values.
  • Confirm that the publication restriction appears at the bottom of the sheet.

Missing part of the brand sheet?

Compare the final line in your document with the restriction shown above. Repeat the paste if the line was cut off.

For help checking the section, help me compare my simulation brand sheet with the required source text.

  • Highlight one line that exposes the conflicting launch dates.
  • Click Add comment.
  • Type Contradiction: followed by your explanation of the conflict.
  • Click Comment.
  • Highlight one line containing a missing decision.
  • Click Add comment.
  • Type Question: followed by the decision you need from Maya Chen.
  • Click Comment.

What do these annotations prove?

Your comments preserve the original request beside your analysis. That record shows which facts came from the requester and which issues came from your audit.

  • Highlight one line that creates timing or production exposure.
  • Click Add comment.
  • Type Risk: followed by the possible campaign consequence.
  • Click Comment.

You now have visible evidence of a contradiction, a decision-blocking question, and a campaign risk. The brief keeps those gaps exposed instead of silently resolving them.

Build the campaign tracker

A tracker converts the brief into accountable work. Its dependencies reveal which tasks cannot move until another decision or deliverable is ready.

  • Return to the Working Files folder in the Google Drive tab.
  • Open 01_Campaign_Tracker.
  • Select cell A1.
  • Enter Practice simulation. Not for publication..
  • Select cell A2.
  • Create the tracker structure by pasting this tab-separated grid:
Task	Deliverable	Owner	Requested Due Date	Confirmed Due Date	Dependency	Status	Priority	Approver	Latest Feedback	Version	Risk	Next Action
Briefing	Audited campaign brief
Claim review	Verified product claim list
Stakeholder deck	Four-slide stakeholder deck
Promotional graphic	Landscape promotional graphic
Square social post	Square social post
Story asset	Vertical Story asset
Copy	Campaign copy sheet
Stakeholder review	Review decision record
Revisions	Revised campaign package
QA	Final QA log
Handoff	Launch handoff package

How does this tracker help?

  • Each row gives one campaign workstream a traceable place.
  • The fields connect ownership, timing, dependencies, feedback, risk, and approval.
  • Confirm that each heading occupies its own column.
  • Confirm that the tracker contains eleven task rows.
  • Wait for Google to finish saving 01_Campaign_Tracker automatically.

Did the grid paste into one cell?

Undo the paste. Select only cell A2 before pasting the tab-separated grid again.

If the columns still do not separate, help me split tab-separated tracker data into Google Sheets columns.

  • Record both requested launch times in the relevant Requested Due Date or Latest Feedback cells.
  • Enter UNCONFIRMED wherever the packet does not name an owner, approver, or confirmed date.
  • Set the affected Status cells to BLOCKED when a missing decision prevents progress.
  • Map each dependency to the decision or deliverable that must come first.
  • Assign a priority that reflects launch impact.
  • Summarize the visible schedule or accuracy risk for every affected row.
  • Add an initial version label to every row.
  • Add a concrete next action to every row.
  • Include the required disclaimer check in the Next Action cell for every planned deliverable.
  • Review the tracker for empty cells that could hide missing information.

That is a major control point complete. Your tracker now exposes missing decisions before they can become missed deadlines.

Resolve the timeline with Response Packet A

A clarification message should ask for decisions that unblock work. It should also show what can continue while the stakeholder responds.

What makes the message useful?

  • It identifies the conflict without assigning blame.
  • It asks only questions that affect launch timing, approval, distribution, destination, or production.
  • It gives Maya Chen a clear response deadline.
  • Switch back to 02_Working_Brief_and_Copy.
  • Add the heading Clarification Message to Maya Chen below the brand sheet.
  • Draft a concise message that names the launch-date conflict.
  • Ask only the questions that block a reliable launch plan.
  • State which campaign work can continue during the response window.
  • Give Maya Chen a specific response deadline.
  • Remove any question that does not affect a decision or dependency.
  • Confirm that your message is complete before revealing the simulated response.

Your clarification message now captures your judgment before the simulation supplies an answer. That sequence preserves an honest record of how you handled ambiguity.

  • Add the heading Response Packet A below your clarification message.
  • Record the simulated stakeholder decisions by pasting this packet:
Response Packet A
Confirmed launch: Friday at 3:00 PM
Final approver: Maya Chen
Campaign destination: https://www.gauthmath.com/download
Distribution: Organic channels only
Call-to-action wording: The coordinator must recommend a concise option for approval
Designer availability: Ends Thursday at 11:00 AM

What changed after the response?

  • The launch time, approver, destination, distribution, and designer cutoff now have confirmed values.
  • The call to action still requires your recommendation plus Maya Chen's approval.
  • Add a short change record below Response Packet A.
  • Preserve the original requested dates in that record.
  • Return to 01_Campaign_Tracker.
  • Record Friday at 3:00 PM as the confirmed launch for launch-dependent work.
  • Enter Maya Chen as the final approver for work that needs campaign approval.
  • Add https://www.gauthmath.com/download to the relevant dependency or next-action cells.
  • Record Organic channels only in the relevant Latest Feedback cells.

Keep the response traceable

The confirmed values belong beside the original requests. That comparison shows how the campaign plan changed after clarification.

  • Record Thursday at 11:00 AM as the designer availability cutoff.
  • Add the designer cutoff to every affected risk or dependency cell.
  • Write your own concise call-to-action recommendation in the relevant Next Action cell.
  • Keep the call-to-action approval Status set to BLOCKED.
  • Name Maya Chen as the decision owner for the call-to-action approval.
  • Update each affected row with its current status.
  • Update each affected row with its current version label.
  • Keep any remaining unknown value visibly marked as UNCONFIRMED.

Does the tracker look fully approved?

Check the call-to-action row or dependency. Response Packet A asks for a recommendation, so approval remains unresolved.

If you cannot tell which cells should remain blocked, help me distinguish confirmed decisions from unresolved blockers in Response Packet A.

Before you inspect the two files, which tracker fields do you expect to remain blocked after Response Packet A?

  • Review 02_Working_Brief_and_Copy from Simulation Packet A through Response Packet A.
  • Confirm that your questions, risks, and contradictions remain visible beside the original information.
  • Review all eleven rows in 01_Campaign_Tracker.
  • Confirm that every row has an owner field, due-date field, status, dependency, approval field, risk, version, and next action.
  • Confirm that the tracker shows the official destination plus organic-only distribution.
  • Confirm that unresolved information remains visibly marked.

You should see a Friday launch at 3:00 PM, Maya Chen as final approver, and a Thursday designer cutoff at 11:00 AM.

You should also see the proposed call to action waiting for approval. That visible blocker proves the tracker distinguishes a recommendation from an approved decision.

Your brief now records the evidence behind the plan. Next, you will turn that plan into a stakeholder deck built for quick decisions.

Build the Stakeholder Deck

Your audited brief now separates confirmed decisions from visible blockers. The next task is to turn that evidence into a deck Maya Chen can assess quickly.

A decision-ready Google Slides deck gives every campaign decision one visible home. Maya can assess it without a verbal explanation.

In this step, get ready to:
  • Plan a four-slide narrative that guides Maya through the campaign decision.
  • Apply the simulation brand system while controlling every product claim.
  • Review the deck before recording its version and current review status.
Plan the four-slide narrative

A stakeholder deck should follow the order of the decision. Each slide should answer the next question Maya needs resolved.

The Four-Slide Decision Map

  • Slide 1 states the campaign objective. It names college students as the audience. It points them to https://www.gauthmath.com/download as the intended action.
  • Slide 2 presents the message direction. Its rationale traces every product statement to the verified source card.
  • Slide 3 makes the launch path visible. It covers deliverables. It names owners. It shows dependencies. It includes the timeline.
  • Slide 4 surfaces risks. It shows open decisions. It asks Maya Chen for approval.

What Belongs in the Notes?

Keep decision-critical information on each slide. Use speaker notes for supporting rationale or source traceability that would clutter the main view.

  • Switch back to 03_Stakeholder_Deck inside Working Files.
  • Use the slide control in the top toolbar to make the deck exactly four slides.

You should see exactly four slide thumbnails in the presentation sidebar.

  • Draft slide 1 from the first purpose in the decision map.
  • Draft slide 2 from the second purpose in the decision map.
  • Preview the first two slides in presentation view.

You should see a clear progression from the campaign goal to the proposed message direction.

  • Draft slide 3 from the third purpose in the decision map.
  • Draft slide 4 from the fourth purpose in the decision map.
  • Preview all four slides in presentation view.

You should see a complete path from campaign purpose to approval request. Each slide should have one distinct job.

Speaker notes keep the simulation disclaimer available without crowding the decision story. The notes area sits beneath the slide canvas.

  • Select slide 1 in the presentation sidebar.
  • Add Practice simulation. Not for publication. to its speaker notes.
  • Repeat the same note on slides 2 through 4.
  • Inspect the speaker notes beneath each slide.

You should find the same disclaimer beneath every slide.

Apply the simulation brand system

The visual system makes the campaign recognizable across future assets. Claim verification keeps that confidence grounded in evidence.

Verified Claim Card

These are the public product statements available to this simulation. Slide 2 can use the statements that support your chosen direction.

  • Your AI Homework Helper.
  • Step-by-step solutions.
  • Detailed explanations.
  • Real experts online 24/7.
  • Switch back to the Canva tab from earlier.
  • Check the font chooser for a sans-serif family that also appears in Google Slides.
  • Return to 03_Stakeholder_Deck.
  • Apply the selected family across all four slides.
  • Limit the typography to two weights.
  • Preview slide 1 at full size.

You should see a clear hierarchy between the headline and supporting information.

  • Use #182033 for the main dark surfaces.
  • Use #F7F8FC for text on those dark surfaces.
  • Preview slide 1 at full size.

You should be able to read the primary message without straining against the background.

  • Apply #6C5CE7 as the primary accent across the deck.
  • Reserve #2DE2A6 for a smaller secondary accent role.
  • Preview slides 1 and 2 in presentation view.

You should see violet guiding attention. Mint should support the hierarchy without competing for focus.

  • Add the typed Gauth wordmark to the same position on every slide.
  • Standardize the spacing between headlines and supporting content.
  • View all four slide thumbnails together.

You should see the wordmark holding one consistent position. The repeated spacing should make the slides feel related.

  • Give each slide one clear focal point.
  • Apply one consistent visual treatment to every call to action.
  • Preview all four slides in presentation view.

The deck should now feel like one campaign system. The call-to-action treatment should remain recognizable throughout.

  • Mark the proposed call-to-action wording as pending Maya Chen's approval.
  • Compare every product statement with the verified claim card.
  • Remove any academic-outcome guarantee from the deck.

Slide 2 should contain only traceable product statements. Slide 4 should keep the call-to-action approval visibly open.

Review decision readiness

A deck is decision-ready when Maya can understand it without narration. This review tests the artifact from her perspective.

  • Review slide 1 to check whether the campaign goal is immediately clear.
  • Review slide 2 to check whether Maya can approve or challenge the message direction.
  • Review slide 3 to check whether the launch path is understandable.
  • Review slide 4 to check whether every blocker is explicit.
  • Revise any slide that fails its decision-readiness check.
  • Page through the revised deck in presentation view.

You should be able to answer each review question from the slides alone.

Version control preserves the review baseline before feedback arrives. The tracker then shows which baseline Maya is reviewing.

  • Click Last edit at the top of the deck.
  • Confirm that the current four-slide deck is the latest entry.

You should see the current deck state at the top of the version history.

  • Click More beside the latest entry.
  • Select Name this version.
  • Enter Version 1.
  • Press Enter.

You should see Version 1 attached to the current deck state. Your review baseline is now preserved.

  • Switch back to 01_Campaign_Tracker.
  • Find the stakeholder deck row.
  • Enter 1 in the Version column.
  • Set the Status field to Awaiting stakeholder review.

The stakeholder deck row should now identify version 1 as the current review baseline.

  • Confirm that Maya Chen remains listed as the approver.
  • Confirm that call-to-action approval remains visible as an unresolved blocker.

Before the final review, do you think Maya could understand the campaign decision without asking for a verbal walkthrough?

  • Return to 03_Stakeholder_Deck from Working Files.
  • Page through all four slides in presentation view.
  • Check that each slide has one distinct purpose.
  • Check every product statement against the verified claim card.
  • Inspect every speaker-notes panel for Practice simulation. Not for publication..

You should see four high-contrast slides with one purpose each. The typed Gauth wordmark should stay in a consistent position.

The palette should remain consistent throughout the deck. No unsupported academic-outcome claim should appear.

That is the decision layer finished. Maya can now review the campaign direction without a verbal walkthrough.

Your deck now sets a review-ready campaign direction. Next, you will turn that system into coordinated campaign assets and copy.

Produce Assets and Copy

Your four-slide deck now gives Maya a decision-ready view of Finals Week Confidence.

The clarified campaign direction now needs tangible assets before stakeholders can review it.

These version 1 assets make the campaign reviewable. Final launch readiness comes after stakeholder feedback.

In this step, get ready to:
  • Create a landscape promotional graphic from the campaign direction.
  • Adapt the visual system into square social content plus a vertical Story.
  • Complete the source-checked copy package plus its handoff records.
Create the promotional graphic

The landscape graphic establishes the visual hierarchy that the social formats inherit. Canva Free gives you the manual controls needed to build that source design.

Keep the workflow free

A design containing premium elements can trigger a purchase prompt. A blank canvas with free elements keeps this project at zero cost.

  • Switch back to the Canva Free tab from earlier.
  • Start a blank landscape design from the Canva home page.

You should see a blank landscape canvas ready for the campaign system.

  • Name the design Gauth_FinalsWeek_Promotional_Landscape_v1.
  • Add Finals Week Confidence as the campaign name.

The canvas now has a versioned identity plus a visible campaign anchor.

Keep the Claim Traceable

Every product statement must map directly to the verified Gauth source card. Choose from these supported statements:

  • Your AI Homework Helper.
  • Step-by-step solutions.
  • Detailed explanations.
  • Real experts online 24/7.
  • Choose one source-card statement for the landscape design.
  • Write a short headline that stays within the chosen statement's meaning.
  • Place the chosen statement beneath the headline as supporting copy.

You should see a short headline supported by a traceable product statement.

  • Add the typed Gauth wordmark in the position established in 03_Stakeholder_Deck.
  • Apply the four-color simulation palette from 03_Stakeholder_Deck.

The design should now reuse violet #6C5CE7. It should also reuse mint #2DE2A6. Dark navy #182033 plus off-white #F7F8FC complete the shared palette.

  • Apply the selected sans-serif family from 03_Stakeholder_Deck.
  • Limit the typography to two weights.

The landscape graphic should now feel connected to the stakeholder deck.

  • Adjust the text color for high contrast.
  • Add your proposed CTA as a separate action line.

The message should be readable at a glance. The CTA remains a proposal pending Maya Chen's approval.

  • Style the CTA with the treatment established in 03_Stakeholder_Deck.
  • Choose one free focal image or illustration.

The CTA should now look consistent with the deck. The chosen visual should support one clear focal point.

  • Arrange the elements around the focal point.
  • Review every selected element for a paid marker.

You should see one clear hierarchy with no premium element selected.

Seeing a Premium Element?

  • Remove the marked element from the landscape design.
  • Replace it with a free alternative.
  • Review the hierarchy after the replacement.

Ask for help if you need another way to create the same visual effect. Help me replace a premium Canva element while preserving my campaign hierarchy.

Adapt the visual system

Square feeds use a compact reading path. Vertical Stories need a top-to-bottom hierarchy.

Why Adapt Manually?

Canva identifies Magic Switch as a Pro feature. Manual adaptation keeps the workflow free while giving each format its own hierarchy.

  • Create a blank square design in Canva.
  • Name the design Gauth_FinalsWeek_Social_Square_v1.

You should see a square canvas with a clear versioned name.

  • Rebuild the landscape design's campaign message stack in the square canvas.
  • Recompose the layout around a square focal point.

You should see the established campaign message compressed into a readable square hierarchy.

  • Create a blank vertical Story design in Canva.
  • Name the design Gauth_FinalsWeek_Story_Vertical_v1.

You should see a vertical canvas with a clear versioned name.

  • Rebuild the campaign message stack in the vertical canvas.
  • Recompose the layout around a top-to-bottom focal path.

You should see the same campaign system arranged for a vertical reading path.

Exact filenames protect version control during review. Each design now needs an individual PNG export.

  • Return to Gauth_FinalsWeek_Promotional_Landscape_v1.
  • Select Share in the Canva editor.
  • Select Download.
  • Choose PNG as the file type.
  • Select Download to export the landscape graphic.
  • Repeat the export workflow for Gauth_FinalsWeek_Social_Square_v1.
  • Repeat the export workflow for Gauth_FinalsWeek_Story_Vertical_v1.

Your browser should show three completed PNG downloads.

Canva Requests Payment?

  • Return to the design named in the payment prompt.
  • Remove every premium element.
  • Replace each removed element with a free alternative.
  • Download the PNG again.

Need help finding the paid content? Help me identify which Canva element is triggering a payment prompt.

Required Export Names

  • Gauth_FinalsWeek_Promotional_Landscape_v1.png.
  • Gauth_FinalsWeek_Social_Square_v1.png.
  • Gauth_FinalsWeek_Story_Vertical_v1.png.
  • Use your browser's download controls to reveal the saved files.
  • Compare each filename with the required names above.
  • Correct any filename that does not match the required list.
  • Open the landscape PNG from its saved folder.
  • Open the square PNG from its saved folder.
  • Open the Story PNG from its saved folder.

Each downloaded file should open as a complete graphic with no watermark.

  • Switch back to the Handoff folder from earlier.
  • Drag the three PNG files from their saved folder into Handoff.

Your Google Drive folder should now list all three versioned PNG files.

Upload Still in Progress?

  • Wait for the current upload indicator to finish.
  • Upload one PNG at a time if the batch stalls.
  • Compare the uploaded filenames with the required list.

Get targeted help if a file repeatedly fails to upload. Help me troubleshoot a PNG upload to my Google Drive Handoff folder.

Complete the copy sheet

The 02_Working_Brief_and_Copy file is your Google Docs source of truth for campaign language. Its copy must follow the same claim controls as the graphics.

  • Switch back to 02_Working_Brief_and_Copy from earlier.
  • Add a heading named Campaign Copy v1.

The document should now have a dedicated section for reviewable campaign copy.

  • Draft the first caption option using one verified product statement.
  • End the first caption with your proposed CTA.

The first caption should connect a source-backed statement to the intended action.

  • Draft the second caption option around a different source-card statement.
  • Draft one email subject line without an academic-outcome promise.

Stakeholders should now have two caption directions plus one safe email subject line to review.

  • Draft one short email introduction.
  • Add the proposed CTA as a separate approval line.

The copy section should now make the unapproved CTA dependency visible.

  • Write alt text for the landscape graphic based on its visible content.
  • Write alt text for the square social post based on its visible content.

The first two graphics should now have descriptions that match what viewers can see.

  • Write alt text for the vertical Story based on its visible content.
  • Add a heading named Deliverable Notes.

All three graphics should now have matching alt text records plus a place for simulation disclosures.

  • Create one deliverable-note entry for each PNG filename.
  • Place Practice simulation. Not for publication. beneath each filename.

Each exported asset now has a matching disclosure in the campaign record.

  • Compare every product statement in the copy section with the verified source card.
  • Remove any wording without direct source-card support.
  • Confirm that the campaign destination is https://www.gauthmath.com/download.

Every remaining product statement should be traceable. The campaign destination should match the verified download page exactly.

The Google Sheets tracker now needs to connect each deliverable to its review state.

  • Switch back to 01_Campaign_Tracker from earlier.
  • Add the Drive link for each PNG to its matching tracker row.
  • Add the 02_Working_Brief_and_Copy link to the copy row.

The asset rows plus the copy row should now point directly to their current files.

  • Set the Version cell to 1 for each asset row.
  • Set the Version cell to 1 for the copy row.

The tracker should now distinguish this first review package from future revisions.

  • Record the current owner for each asset row.
  • Record the current owner for the copy row.

Every new deliverable should now have an accountable owner.

  • Update each asset status to reflect its review readiness.
  • Update the copy status to reflect its review readiness.

The tracker should show that the files are ready for review instead of approved for launch.

  • Record CTA approval as a dependency on every affected row.
  • Keep Maya Chen as the approver on the affected rows.
  • Set stakeholder review as the next action for each new deliverable.

The stakeholder deck remains at version 1 with its current review status. The new rows now expose the remaining approval need.

Before you check the handoff, which consistency issue do you think is easiest to miss?

  • Return to the Handoff folder.
  • Open Gauth_FinalsWeek_Promotional_Landscape_v1.png in Drive preview.
  • Open Gauth_FinalsWeek_Social_Square_v1.png in Drive preview.
  • Open Gauth_FinalsWeek_Story_Vertical_v1.png in Drive preview.

You can now inspect the exported files instead of relying on the Canva canvases.

  • Compare the campaign name across the three files.
  • Compare the verified product statement across the three files.
  • Compare the proposed CTA treatment across the three files.
  • Compare the shared palette across the three files.
  • Compare the visual hierarchy across the three files.

You should see Finals Week Confidence presented through one recognizable visual system. Each file should use source-backed product wording plus the same proposed CTA treatment.

Strong work. Your campaign now has a reviewable asset system backed by source-checked copy.

Next, you'll test this package against conflicting stakeholder feedback under a compressed deadline.

Triage Feedback and Run Final QA

Your first-pass campaign package is ready for review. A Thursday feedback round now disrupts its launch plan.

This step uses feedback triage to turn every comment into a recorded decision.

You will preserve the original work before applying revisions. A final quality assurance gate will determine whether the evidence supports launch readiness.

In this step, get ready to:
  • Log Simulation Packet B with clear classifications.
  • Preserve version 1 before creating revised deliverables.
  • Audit the handoff package against a documented QA gate.
Log and classify Simulation Packet B

The tracker in Google Sheets gives each feedback item a visible owner. Its classification separates urgent work from unresolved conflicts.

Before you log the packet, predict which feedback items will conflict with the verified source card or the current schedule.

Simulation Packet B

Treat this packet as feedback received at Thursday 10:15 AM.

  • Maya Chen moves the launch to Thursday at 2:00 PM.
  • Maya Chen requests a more urgent tone using Instant A's before finals.
  • Leo Patel rejects academic-outcome guarantees. He limits product statements to the verified source card.
  • Nia Brooks requests removal of every extra accent color.
  • Nia Brooks requires one consistent wordmark position. Her sign-off cutoff is Thursday 11:00 AM.
  • Jordan Kim needs the caption thirty minutes before launch. His note still refers to Friday.
  • The designer cannot complete the revisions. Coordination plus light production now belongs to you.
  • Return to 01_Campaign_Tracker from the campaign workspace.
  • Use the relevant existing rows to log every item from Simulation Packet B.
  • Enter Thursday 10:15 AM at the start of each new feedback note.
  • Prefix each note in the Latest Feedback field with Required, Recommended, Conflicting, or Blocked.
  • Leave every version 1 file unchanged while you assess the packet.

How should feedback be classified?

  • Required feedback controls the latest approved schedule or protects claim accuracy.
  • Recommended feedback improves the campaign without changing an approved fact.
  • Conflicting feedback cannot coexist with another instruction or verified source.
  • Blocked feedback needs a named decision before the related work can proceed.
  • Update the Confirmed Due Date field to Thursday 2:00 PM for the revised launch.
  • Record Thursday 11:00 AM as the design sign-off dependency.
  • Set the caption deadline to Thursday 1:30 PM.
  • Reassign coordination plus light production to yourself.
  • Flag Instant A's before finals as a claim-control escalation.
  • Keep Leo Patel's source-card restriction as the governing claim requirement.
  • Keep the proposed CTA visibly pending Maya Chen's approval.
  • Update each affected row with its current status, priority, risk, approver, dependency, plus next action.

The feedback now exposes the schedule conflict instead of hiding it. You have converted a rushed review into an accountable revision plan.

Preserve version 1 and create version 2

Version history provides version control inside Google Slides. Naming the current state protects the review trail before edits begin.

  • Return to 03_Stakeholder_Deck from earlier.
  • Click Last edit at the top of the deck.
  • Click More in the version history panel.
  • Click Name this version.
  • Enter Version 1 - Pre-Packet B as the version name.
  • Return to the current deck.

You should see the named version in the deck's history. This gives you a recoverable record of the pre-feedback presentation.

  • Set the deck title to Finals Week Confidence.
  • Change the active launch plan to Thursday at 2:00 PM.
  • Page through all four slides to confirm the corrected title plus schedule are visible.

The deck should now present one campaign name. Its timeline should use the accelerated Thursday launch.

  • Update slide 3 with the revised owners plus deadlines.
  • Update slide 4 with the current risks plus approval needs.
  • Remove any academic-outcome guarantee from slide 2.
  • Retain only Your AI Homework Helper, Step-by-step solutions, Detailed explanations, or Real experts online 24/7 as product claims.
  • Confirm every slide's speaker notes retain Practice simulation. Not for publication..
  • Set the deck's tracker version to version 2.

The revised deck should now show the new launch path. It should preserve every claim-control boundary.

The current brief in Google Docs serves as the campaign's written decision record. Revise its active plan without erasing the clarification history.

  • Switch back to 02_Working_Brief_and_Copy from earlier.
  • Set the current launch time to Thursday at 2:00 PM.
  • Remove every academic-outcome guarantee from the current caption options.
  • Reread the revised current-plan section.

The active brief should now show the Thursday launch. Historical references to the earlier Friday decision should remain clearly labelled as history.

  • Review the email subject line against the verified source card.
  • Review the email introduction against the verified source card.
  • Review the proposed CTA against its pending approval dependency.
  • Review all three alt-text entries against the actual graphics.
  • Revise any wording that fails one of those checks.

What must the stakeholder update answer?

The update gives stakeholders enough information to act without reconstructing the review themselves.

  • State the schedule change.
  • Identify the feedback you accepted.
  • Identify the feedback you challenged.
  • Name each remaining decision owner.
  • State whether the Thursday 2:00 PM launch remains achievable.
  • Add a short stakeholder status plus escalation update to 02_Working_Brief_and_Copy.
  • State the revised launch time.
  • Describe the feedback you accepted.
  • Explain why unsupported claims were challenged.
  • Name the owner of each unresolved decision.
  • Give your evidence-based assessment of launch achievability.
  • Reread the update to confirm all six elements are explicit.

The brief now tells stakeholders what changed. It also shows which decision still controls launch readiness.

In Canva Free, separate copies protect the original creative work. The revised designs can now carry the new brand direction without overwriting the review history.

  • Switch back to the Canva workspace from earlier.
  • Create a separate copy of each of the three version 1 designs.
  • Rename the landscape copy Gauth_FinalsWeek_Promotional_Landscape_v2.
  • Rename the square copy Gauth_FinalsWeek_Social_Square_v2.
  • Rename the Story copy Gauth_FinalsWeek_Story_Vertical_v2.
  • Confirm that the three original designs remain listed separately.

You should now see three preserved originals plus three editable revisions. The creative review trail is intact.

  • Remove every extra accent color from the three version 2 designs.
  • Place the typed Gauth wordmark in one consistent position across all three designs.
  • Compare the three designs side by side.

The set should now use only violet, mint, dark navy, plus off-white. The wordmark should occupy the same relative position in every format.

  • Remove any academic-outcome guarantee from the three revised designs.
  • Apply one coherent CTA treatment across the three revised designs.
  • Compare each revised design with its preserved original.
  • Confirm each revised design's notes retain Practice simulation. Not for publication..

Each revision should still look like part of Finals Week Confidence. Every product statement should trace back to the verified source card.

The revised PNG files now move from Canva Free into the Handoff folder in Google Drive.

  • In the landscape version 2 design, click Share.
  • Select Download.
  • Choose PNG as the file type.
  • Select Download to export the landscape design.
  • Repeat the same export workflow for Gauth_FinalsWeek_Social_Square_v2.
  • Repeat the same export workflow for Gauth_FinalsWeek_Story_Vertical_v2.
  • Locate all three downloaded PNG files in File Explorer.
  • Upload all three PNG files to the Handoff folder.

The folder should now contain all three preserved v1 exports. It should also contain Gauth_FinalsWeek_Promotional_Landscape_v2.png, Gauth_FinalsWeek_Social_Square_v2.png, plus Gauth_FinalsWeek_Story_Vertical_v2.png.

Canva asks for payment?

A payment prompt means one of the copied designs still contains a premium element. Remove that element before repeating the export without starting a trial.

Get help identifying the paid item in your design.

  • Return to 01_Campaign_Tracker.
  • Add the three version 2 export links to their relevant rows.
  • Keep every version 1 link in the tracker.
  • Set the square post's approver to the actual approver or Pending.
  • Update each revision row with its current status plus next action.

That is the revision cycle complete. Your tracker now connects preserved originals to their current handoff versions.

Run the final QA gate

A QA gate turns a visual review into recorded evidence. Every defect needs a correction owner plus a verification result.

Before you inspect the manifest, predict whether a complete-looking handoff folder is enough to support launch readiness.

Deliberately flawed handoff manifest

Use this manifest as an audit test. Treat every mismatch as a defect that needs evidence.

  • The deck title is listed as Final Week Confidence.
  • The Story filename is listed as Gauth_FinalsWeeks_Story_v1.png.
  • The campaign destination is listed as https://www.gauthmath.co/download.
  • The brief still lists the launch as Friday at 3:00 PM.
  • One caption contains an academic-outcome guarantee.
  • The square post is marked approved without a recorded approver.

The manifest looks complete at a glance. Its hidden defects show why file presence alone cannot prove launch readiness.

  • Return to 01_Campaign_Tracker.
  • Add a new sheet tab.
  • Rename the new tab QA.
  • Enter Check Area, Defect, Correction, Owner, plus Verification Result as headers.
  • Create one QA row for each flawed manifest item.

You should now see six open defect rows in the QA tab. Each row has a place for ownership plus proof.

  • Compare the manifest's deck title with 03_Stakeholder_Deck.
  • Set the deck title to Finals Week Confidence.
  • Record the title correction in the matching QA row.
  • Compare the manifest's Story filename with the Handoff folder.
  • Set the revised Story filename to Gauth_FinalsWeek_Story_Vertical_v2.png.
  • Record the filename correction in the matching QA row.

The corrected title now uses the full campaign name. The revised Story file now follows the singular FinalsWeek naming pattern.

  • Compare every current campaign destination with https://www.gauthmath.com/download.
  • Replace the malformed destination wherever it appears in current deliverables.
  • Record the link correction in the matching QA row.
  • Inspect the active launch time in 02_Working_Brief_and_Copy.
  • Set the active launch time to Thursday at 2:00 PM.
  • Record the schedule correction in the matching QA row.

The current campaign destination should now use the verified .com address. The active brief should show the Thursday launch.

  • Review both current captions for academic-outcome guarantees.
  • Remove any remaining guaranteed-grade wording.
  • Record the caption correction in the matching QA row.
  • Inspect the square post's approval field.
  • Set the approval field to a named approver or Pending.
  • Record the approval-state correction in the matching QA row.

The captions should now contain only verified product truth. The square post should no longer claim approval without evidence.

What does the full QA gate cover?

  • Check spelling plus punctuation.
  • Check formatting plus dates.
  • Check links plus product claims.
  • Check campaign naming plus asset dimensions.
  • Check visual consistency plus version labels.
  • Check approval status plus handoff ownership.
  • Add a QA row for each remaining check area.
  • Assign one owner to every defect.
  • Record the correction applied to every defect.
  • Record a verification result for every completed correction.

Before the final review, predict whether the current evidence supports a launch-ready decision.

  • Page through all four slides in 03_Stakeholder_Deck.
  • Read the current brief plus copy in 02_Working_Brief_and_Copy.
  • Open every v1 plus v2 PNG in the Handoff folder.
  • Open https://www.gauthmath.com/download to test the campaign destination.
  • Inspect every tracker row for a current owner, date, status, version, approval state, plus next action.
  • Confirm every deliverable retains Practice simulation. Not for publication..
  • Mark the package launch-ready only when no unresolved high-risk defect is hidden.

You should see three preserved v1 PNG files. You should also see three corresponding v2 PNG files.

Every tracker row should show a current owner. Each row should also show a current date.

Every row should show its status plus version. Its approval state should match the available evidence.

Every row should name a next action. No unresolved high-risk defect should sit behind a launch-ready status.

Found a mismatch during the final review?

  • Keep the affected tracker row out of Launch-ready status.
  • Assign one owner to the unresolved defect.
  • Record the required correction plus deadline.
  • Repeat the relevant QA check after the correction.
  • Get help tracing a mismatch across the tracker, source files, plus handoff package.

Your handoff now earns its status through evidence. Another coordinator can see the decision trail without guessing what happened.

Secret mission

Handle an Unsupported Executive Request

Minutes before launch, a fictional executive requests an academic-outcome guarantee that the campaign evidence does not support. Protect claim accuracy while giving stakeholders a workable path to a clear launch decision.

Clean Up Your Resources

Clean Up Your Resources

The campaign uses existing free accounts in Google Drive and Canva Free. Keeping these materials adds no project-specific charge. Decide whether to keep your campaign workspace available, pause it for later, or delete its project files.

Resources you used:

  • The Gauth_Finals_Week_Campaign_Simulation Google Drive folder containing Working Files, Handoff, campaign files, review history, exported assets, the executive response, and the go/no-go note.
  • The landscape, square, and vertical Story designs in Canva Free, including preserved version 1 designs and revised version 2 designs.
  • Any downloaded version 1 and version 2 PNG copies in the Windows Downloads folder.

Keep everything running

No action is needed. Choose this if you want to revisit the simulation or use it as a campaign coordination reference.

  • Retain the Gauth_Finals_Week_Campaign_Simulation folder with its version history and QA evidence.
  • Retain both versions of the landscape, square, and vertical Story designs in Canva Free.
  • Replace fictional stakeholder names with role labels before sharing screenshots.
  • Keep Practice simulation. Not for publication. visible on every deliverable.

Pause - I'll come back to this later

Pause the campaign record so you can return without reconstructing the launch state. Your files remain saved in Google Drive and Canva Free.

  • Switch back to 01_Campaign_Tracker inside Working Files.
  • Mark the campaign as paused in the tracker.
  • Record the next action required to restart coordination.
  • Record the point where you plan to resume the campaign.
  • Leave the current files in Working Files.
  • Leave the approved handoff evidence in Handoff.

Delete - I don't want to use this again

Remove all campaign resources if you want to start fresh. This clears the project copies from Google Drive, Canva Free, and Windows Downloads.

  • Return to Google Drive from earlier.
  • Move up to the location containing Gauth_Finals_Week_Campaign_Simulation.
  • Right-click Gauth_Finals_Week_Campaign_Simulation to open its context menu.
  • Move the selected folder to trash from that menu.
  • Confirm that Gauth_Finals_Week_Campaign_Simulation no longer appears in its former Drive location.
  • Return to Canva Free from earlier.
  • Locate the landscape, square, and vertical Story campaign designs in versions 1 and 2.
  • Open the options menu for each campaign design.
  • Delete each campaign design from your Canva account.
  • Confirm that the six campaign designs no longer appear in your active Canva design list.
  • Press the Windows key to open the search bar.
  • Type File Explorer into the search bar.
  • Press Enter to open File Explorer.
  • Select Downloads in the left sidebar.
  • Select Gauth_FinalsWeek_Promotional_Landscape_v1.png, Gauth_FinalsWeek_Promotional_Landscape_v2.png, Gauth_FinalsWeek_Social_Square_v1.png, Gauth_FinalsWeek_Social_Square_v2.png, Gauth_FinalsWeek_Story_Vertical_v1.png, and Gauth_FinalsWeek_Story_Vertical_v2.png.
  • Press the Delete key.
  • Confirm that the six campaign PNG files no longer appear in Downloads.

Nice Work!

You made it! You coordinated the fictional Gauth Finals Week Confidence campaign from an incomplete brief to a quality-checked handoff package.

Your workspace now gives another coordinator the evidence needed to understand every deadline, decision, risk, revision, approval, and next action.

You learned how to:

  • Build a campaign tracker that keeps owners, deadlines, dependencies, blockers, versions, approvals, risks, and next actions visible.
  • Coordinate a campaign package containing a decision-ready stakeholder deck, promotional graphics, social assets, campaign copy, and structured handoff files.
  • Apply feedback triage and final QA under an accelerated deadline. You preserved earlier versions while correcting claim, link, naming, schedule, and approval defects.
  • Secret Mission: Documented an evidence-based executive response and go/no-go decision when a senior stakeholder requested the unsupported claim Guaranteed better grades minutes before launch.

Ready to quiz yourself?