Capstone: Real-Time Team Collaboration on a Shared Report

The Excel/Word & PowerPoint and LibreOffice capstones each rebuilt one report-plus-deck project end to end. This capstone takes a genuinely different shape, because Google Workspace's own genuine differences aren't about individual features inside one document — they're about what happens when several people work on that document at the same time. This capstone is a scenario, not a rebuild: a three-person team producing one shared quarterly report, exercising every chapter's own collaboration-first angle along the way.

The Scenario

Three teammates — a writer, a data analyst, and a manager — need to produce a quarterly report together, plus a short companion deck for a stakeholder meeting, all inside a single working day, without ever emailing a file back and forth.

Step 1 — Setting Up the Doc for Real Collaboration

The writer creates a new Google Doc and shares it directly with the analyst and manager, choosing Editor access for both — the cloud-native "share the object, not a copy of a file" model Chapter 1 established as the foundation everything else in this course builds on.

Step 2 — Simultaneous Editing in Action

All three open the Doc at once. The writer drafts the opening summary while the analyst adds a data section below it, each visible to the other in real time with their own labelled cursor — the live, simultaneous editing model Chapter 2 contrasted directly against Word & PowerPoint's own asynchronous Track Changes.

Step 3 — Suggesting Mode and Comments for Review

The manager reviews the draft in Suggesting mode rather than editing directly, proposing wording changes the writer can accept or reject, and leaves a Comment flagging a section that needs the analyst's input — Chapter 3's own pairing of Suggesting mode (Google's live equivalent of Track Changes) with Comments (discussion without editing), both happening in real time alongside the live editing from Step 2.

Step 4 — An Accidental Deletion, and Recovering It

The analyst accidentally deletes an entire paragraph while reformatting a table and doesn't notice right away. Rather than panic, the writer opens File → Version History, finds the version from just before the deletion, and restores the missing paragraph — Chapter 4's own continuous, automatic safety net standing in for the manual-save-and-recover habit every other course in this subject assumed by default.

Step 5 — Pulling in Data from Sheets

The analyst builds the supporting numbers in a separate Google Sheet, then inserts a live chart into the Doc linked back to that Sheet, so it updates automatically if the underlying figures change — Chapter 5's own point about Sheets' formulas transferring familiar syntax while adding live, multi-editor collaboration on the same data.

Step 6 — A Companion Slide Deck

The manager spins up a short Google Slides deck summarizing the report's key points for the stakeholder meeting, deliberately keeping it simple — a small Theme, no elaborate custom animation — consistent with Chapter 6's own "simplicity over depth" framing rather than trying to force PowerPoint-level polish out of Slides.

Step 7 — Automating the Weekly Status Email

Rather than manually remembering to notify the wider team each Monday, the analyst writes a short Apps Script function, attached to a time-based trigger, that emails a summary of the report's current state every Monday at 8am — Chapter 7's own example of Apps Script's cloud-native execution doing something no locally-running macro language could replicate without external help.

Step 8 — Sharing the Final Report Externally

The external stakeholder uses Microsoft Word, not Google Docs, so the writer uses File → Download to export the finished report as a .docx file before sending it along — Chapter 8's own reverse conversion, generating a genuine file from a cloud-native object that had none, going the opposite direction from Step 1's own upload-free starting point.

Hands-On Exercises