# Google Workspace Learning Studio

50 lessons. Product features vary by edition and organization policy. Local scenarios do not connect to a Google account.

## 1. Choose the right app

Start with the outcome, not the tool. Docs suits a shared narrative, Sheets structured calculations, Slides a presentation, and Forms repeatable responses. Drive organizes the files and permissions that connect the work.

1. Write the output you need
2. choose one primary app
3. identify where the source data lives.

Check: Which app best collects consistent survey responses?
Answer: Forms

## 2. Separate personal and work accounts

An account determines which organization owns your work and which policies apply. Browser profiles can help separate contexts. Before sharing or creating a file, inspect the signed-in account rather than relying on a familiar avatar.

1. Check your account address
2. identify the intended work profile
3. create a harmless practice file there.

Check: What should you verify before creating a work document?
Answer: The signed-in account

## 3. Build a simple project home

A useful project home gives people a starting point: purpose, owner, source files, decisions and next actions. A folder alone does not explain how a team should use its contents. Keep one authoritative source for each deliverable.

1. Draft a project index in Docs
2. link the active files
3. name an owner and review date.

Check: What reduces conflicting copies?
Answer: One clearly identified authoritative source

## 4. Understand availability and policies

Features vary by Workspace edition, account type and administrator settings. A missing recording or sharing option may be a policy or licensing issue rather than a mistake. Verify what your own organization supports before designing a workflow around it.

1. List required features
2. check their availability in your account
3. plan a fallback.

Check: Why might a feature be missing?
Answer: Edition or administrator settings

## 5. Make work accessible

Use meaningful headings, descriptive links, sufficient contrast and text alternatives. A clear document structure helps both assistive technology and people skimming. Test the actual task, including keyboard navigation and the reading order.

1. Replace vague link text
2. add headings
3. review one file with keyboard navigation.

Check: Which link label is more useful?
Answer: Download the project brief

## 6. Write an actionable email

A useful message states its purpose early, names the requested action and makes the deadline clear. Separate background from the decision needed. Use a subject that will still make sense when someone searches for the message later.

1. Write a decision-focused subject
2. put the action first
3. specify owner and deadline.

Check: Which subject is easiest to act on?
Answer: Approve launch brief by Friday

## 7. Use To, Cc and Bcc deliberately

To identifies primary recipients; Cc keeps others informed. Bcc hides recipient addresses from other recipients, but it does not prevent forwarding or screenshots. For ongoing team distribution, consider an organization-managed group.

1. Identify who must act
2. separate people needing awareness
3. review visible recipient addresses.

Check: Does Bcc prevent a recipient forwarding the message?
Answer: No

## 8. Labels are not folders

Gmail labels categorize messages, and one message can have several labels. Archiving removes the Inbox label without deleting the message. A sustainable system needs only a few labels tied to real retrieval or action needs.

1. Create a project label
2. apply it to a practice message
3. archive and locate that message again.

Check: What does archive normally do?
Answer: Removes a message from the inbox without deleting it

## 9. Search before you sort

Search operators can narrow by sender, subject, attachment or date. Combine a few criteria and inspect the results before making a filter. Avoid assuming that a complex query captures exactly the business meaning you intended.

1. Use the local search builder
2. inspect its synthetic matches
3. try the generated query in your own Gmail.

Check: Which operator narrows by sender?
Answer: from:

## 10. Filters and delayed sending

A filter applies actions to matching messages. Test the search before enabling actions such as archive or delete. Scheduled sending changes delivery timing, not responsibility for the content; recheck recipients and context before scheduling.

1. Test a search query
2. decide on a reversible label action
3. inspect scheduled messages before their send time.

Check: What should come before creating an automatic filter?
Answer: Reviewing the search results

## 11. Organize by purpose

Use a shallow structure with predictable names and clear ownership. Separate active work from reference and archive material. Moving a file can affect access through its location, so review sharing when reorganizing a collaborative folder.

1. Create Active, Reference and Archive areas
2. agree on a naming pattern
3. document the project home.

Check: What makes a folder structure useful?
Answer: Predictable purpose and ownership

## 12. Choose a sharing role

Give collaborators the capability they need: reading, feedback or editing. A feedback-only reviewer does not normally need to modify the original. Check the actual sharing dialog and organization restrictions before confirming.

1. Use the sharing exercise
2. compare a reviewer and a coauthor
3. inspect the real file role before sharing.

Check: Which role generally fits feedback without editing the original?
Answer: Commenter

## 13. Check effective access

A person may receive access through a direct share, group, folder or general-access setting. Removing one direct entry may not remove another route. Review all relevant paths, especially when someone still opens a supposedly restricted file.

1. Identify direct and inherited access
2. inspect group membership when authorized
3. verify the resulting access.

Check: Why might removing a direct share be insufficient?
Answer: Another access route may remain

## 14. Links and access are separate

Copying a file link does not necessarily give the recipient permission. Conversely, broadly accessible links may reach people beyond the intended audience. Test access with the correct account rather than using your own already-authorized session.

1. Send a link only through an approved channel
2. verify its access setting
3. test as the intended recipient.

Check: Does merely copying a restricted link grant permission?
Answer: No

## 15. Team continuity and shared drives

Where available, shared drives support team-based continuity rather than depending on one individual’s My Drive ownership. Roles differ from ordinary file roles. Plan where long-lived team assets belong and confirm organizational rules before moving them.

1. Identify long-lived team assets
2. check shared-drive availability
3. plan ownership and access during handover.

Check: What is a key reason to use a shared drive?
Answer: Team continuity

## 16. Structure a document

Heading styles create navigable structure. Make the document’s purpose and current status clear before adding detail. A short summary and decision section can make a long document useful to both reviewers and implementers.

1. Add a title and purpose
2. use heading styles
3. inspect the outline.

Check: Why use heading styles instead of only bold text?
Answer: They provide document structure

## 17. Comments versus suggestions

Use comments to ask questions or discuss a passage. Suggesting mode proposes text changes for review rather than silently replacing the accepted wording. Agree who resolves feedback and who has final editorial responsibility.

1. Add a question as a comment
2. propose wording as a suggestion
3. assign a reviewer in your workflow.

Check: What is a good use of a suggestion?
Answer: Proposing wording for review

## 18. Keep decisions out of comment limbo

Comments are a collaboration channel, not the only place to store final decisions. Move accepted outcomes into the document or a decision log. Resolve threads when the action is complete and preserve enough context for future readers.

1. Review one comment thread
2. record the accepted decision
3. mark the related action complete.

Check: Where should an important final decision also appear?
Answer: In the maintained document or decision log

## 19. Version history and recovery

Version history can help identify and recover earlier work. Inspect changes before restoring: a restore may affect other people’s recent contributions. Name significant checkpoints so a team can recognize a reviewed draft.

1. Inspect an earlier version
2. compare changes
3. name a meaningful checkpoint.

Check: What should you do before restoring an older version?
Answer: Review what later work could be affected

## 20. Prepare a document for handoff

A handoff needs a clear status, owner, next action and reliable links. Exported files are separate snapshots and may not carry the live collaboration context. Decide whether readers need the live document or a fixed export.

1. State draft or approved status
2. verify linked file access
3. choose live link or export intentionally.

Check: An exported PDF is generally…
Answer: A snapshot separate from the live document

## 21. Build analyzable tables

Use one record per row and one attribute per column. Keep headers clear and avoid merged cells inside raw data. Separate source records from summary calculations so imports and filters do not mix detail with totals.

1. Create a clean source table
2. identify numeric fields
3. put summaries elsewhere.

Check: Which structure supports analysis?
Answer: One record per row

## 22. Separate inputs and formulas

Make editable inputs distinguishable from calculated outputs. A note explaining the input’s units is often more useful than decorative formatting. Protect formulas against accidental edits where appropriate, while remembering protection is not confidentiality.

1. Label units
2. identify editable columns
3. document the calculation.

Check: Does range protection hide confidential data from viewers?
Answer: No

## 23. Use filters without losing records

Filters hide unmatched records rather than deleting them. Sorting must keep all fields of a record together. Filter views can help collaborators work with their own views of shared data.

1. Filter a category
2. remove the filter
3. verify the source record count.

Check: What happens to filtered-out source records?
Answer: They remain in the data

## 24. Summarize before you chart

A chart should answer a specific question. Establish the metric and grouping, then reconcile the totals. Category comparisons and time trends need different presentations. Keep the underlying numbers available to readers.

1. Define one metric
2. build a summary
3. choose a chart and inspect its labels.

Check: What should a chart be based on?
Answer: A defined metric and trustworthy summary

## 25. Check a sheet before sharing

Test a normal case, an empty or missing value and a boundary case. Check totals against an independent calculation. Include instructions for adding new records and explain which ranges or formulas must expand.

1. Test an edge case
2. reconcile a total
3. add a usage note.

Check: Which test is valuable before handoff?
Answer: A zero or missing input

## 26. One main idea per slide

A presentation supports the audience’s understanding; it is not a document pasted into boxes. Use a claim-oriented title and evidence that supports it. Put detailed explanations into speaker notes or a separate handout.

1. Write the slide’s main claim
2. remove unrelated detail
3. add supporting evidence.

Check: Where can detailed speaking prompts go?
Answer: Speaker notes

## 27. Layouts and consistency

Use layouts and theme choices to maintain hierarchy and spacing. Consistent structure helps the audience compare slides. Make a deliberate exception only when it improves understanding rather than adding visual noise.

1. Choose a repeatable layout
2. align content
3. inspect headings across the deck.

Check: What does a consistent layout improve?
Answer: Readability and comparison

## 28. Use charts and images responsibly

Label charts with units and sources. Add meaningful alternative text when an image conveys information. Crop or simplify visuals without changing their meaning, and verify that the image remains legible when projected.

1. Inspect chart units
2. add useful image descriptions
3. test a full-screen view.

Check: What should a data chart communicate clearly?
Answer: Units and meaning

## 29. Rehearse the actual delivery

Review the deck in the mode and device you will use. Check media playback, links, presenter notes and timing. Have a fallback for unreliable connectivity rather than assuming every resource will load during the session.

1. Run the presentation
2. time the opening
3. prepare an appropriate backup.

Check: Why rehearse in the real delivery setup?
Answer: To catch environment-specific problems

## 30. Collaborate without breaking the story

Agree on an outline and an editorial owner before parallel editing. Keep a consistent message across sections and consolidate repeated content. A final review should check the narrative as well as formatting.

1. Assign sections
2. agree on the main message
3. review the complete sequence.

Check: Who helps keep a collaborative deck coherent?
Answer: A clear editorial owner

## 31. Write a useful invitation

A meeting invitation should state the outcome, preparation and attendees. Invite people because their contribution is needed. A link to an agenda helps people prepare, but the linked file still needs appropriate access.

1. State the outcome
2. add preparation links
3. identify required attendees.

Check: What belongs in a useful invite?
Answer: Outcome and preparation

## 32. Handle time zones explicitly

A date and local clock time are incomplete without a time zone when people work in different regions. Daylight-saving changes can alter offsets. Use Calendar’s time-zone-aware event settings and verify the invite display for participants.

1. Identify participant zones
2. select the event zone
3. verify the displayed local times.

Check: Are time-zone offsets fixed throughout the year everywhere?
Answer: No

## 33. Distinguish calendar access from event access

Sharing availability is different from showing all calendar details. An event invitation also does not grant blanket access to the organizer’s other events. Choose the narrowest useful visibility and check organization policy.

1. Decide whether free/busy is sufficient
2. inspect calendar visibility
3. review event guests.

Check: What can free/busy visibility communicate?
Answer: Availability without ordinary event details

## 34. Use recurring meetings intentionally

Recurring events are helpful for a repeating purpose, but they can outlive their value. Specify an end or review date and distinguish editing one occurrence from editing a series. Revisit attendees and objectives periodically.

1. Give the series a purpose
2. set a review point
3. inspect the scope before editing.

Check: What matters when editing a recurring event?
Answer: Whether one occurrence or the series changes

## 35. Turn discussion into follow-through

A meeting is useful when decisions and next actions become visible. Record an owner and due date for each action, then share the agreed outcome. Do not require every participant to reconstruct the decision from a recording.

1. Record decisions
2. assign owners and deadlines
3. send or link the outcome through the agreed channel.

Check: What makes an action item actionable?
Answer: An owner and clear next step

## 36. Prepare for a video call

Check your microphone, camera, speaker route and surroundings before joining. Use a short agenda to make the session purposeful. Features such as recordings or transcripts depend on account capabilities and administrator settings.

1. Test devices
2. review the agenda
3. confirm which meeting features are available.

Check: Why test the speaker route?
Answer: To avoid audio going to the wrong device

## 37. Share the intended content

Choose the appropriate screen, window or tab for the material. A full-screen share may reveal unrelated notifications or windows. Verify what participants can see and stop presenting when the shared task ends.

1. Select the smallest useful presentation surface
2. check visibility
3. stop presenting afterward.

Check: Why share a specific window when possible?
Answer: To limit unrelated content being shown

## 38. Make meetings accessible

Offer preparation material and an agenda, speak clearly, and use available captions when useful. Captions can contain errors, so clarify names and decisions. Provide an accessible written summary for essential outcomes.

1. Share preparation material
2. explain visual information aloud
3. publish a readable summary.

Check: Are automatic captions guaranteed error-free?
Answer: No

## 39. Choose Chat or email

Chat works well for short, contextual coordination; email may suit a formal request or broader communication. Keep decisions in a durable, discoverable location. A message thread is not automatically a task-management system.

1. Choose the communication channel
2. include necessary context
3. record the final decision in its home.

Check: Where should durable project decisions also live?
Answer: A maintained project record

## 40. Use spaces and threads clearly

A space can give an ongoing team conversation a home. Use a topic and thread structure people can follow. Membership, external participation and file permissions need review; posting a link does not always settle the recipient’s access.

1. Define the space purpose
2. keep related replies together
3. verify linked-file access.

Check: What helps a space stay useful?
Answer: A clear purpose and organized conversations

## 41. Design questions around decisions

Collect only information you will use. Each question should have a clear meaning and appropriate response type. Avoid combining two different questions into one; the answer would be hard to interpret.

1. Name the decision the form supports
2. remove unnecessary fields
3. separate double questions.

Check: Which question is easier to analyze?
Answer: One clear concept per question

## 42. Choose response types and required fields

A controlled choice helps standardize responses; free text captures detail. Mark a question required only when the workflow truly needs an answer. Explain unusual requirements so respondents know what is expected.

1. Choose types deliberately
2. require only essential fields
3. preview the respondent experience.

Check: Why use a multiple-choice question?
Answer: To collect a consistent choice set

## 43. Review response access and identity

Decide whether you need identified or anonymous responses and check the actual settings and organization restrictions. Collecting email addresses is not the same as granting respondents access to the response sheet. Limit access to sensitive results.

1. Review identity settings
2. inspect who can see responses
3. test with a practice respondent.

Check: Does submitting a form automatically mean access to its response spreadsheet?
Answer: No

## 44. Connect responses to a workflow

A response is an input, not a completed process. Decide who reviews it, what qualifies it for action and how progress is tracked. Keep raw responses intact and put calculations or status tracking in an appropriate separate area.

1. Define the review owner
2. preserve raw responses
3. create a status and follow-up process.

Check: What turns responses into useful work?
Answer: A defined review and action process

## 45. Track tasks with ownership

A reminder is not the same as a shared project plan. Choose a task tool and ownership model that match the work. Keep the next action specific, and review stale or overdue items rather than merely accumulating more notifications.

1. Write an action verb
2. assign an owner in the chosen workflow
3. set a review time.

Check: Which task is clearer?
Answer: Sam: review the brief by Thursday

## 46. Build a repeatable weekly review

A weekly review connects messages, meetings, documents and tasks. Identify unanswered requests, upcoming commitments and blocked work. Keep the review short enough to repeat and leave each item with a next action.

1. Review commitments
2. identify blockers
3. update owners and next actions.

Check: What should a weekly review produce?
Answer: Clear next actions

## 47. Use templates thoughtfully

Templates reduce repeated setup but can carry stale names, links and permissions. Treat a copied template as a starting point. Review its assumptions, source data and access before using it for a new project.

1. Copy the approved template
2. replace context
3. check links and access.

Check: What should be reviewed after copying a template?
Answer: Stale content and sharing assumptions

## 48. Use AI as a draft assistant

AI-generated text and analysis can be useful starting points, but check claims, source data and permissions before using them. Availability and data handling depend on the product and organization settings. Do not assume a confident answer is correct.

1. Define the task
2. use approved data
3. verify the output against sources.

Check: What should happen before relying on an AI summary?
Answer: Verify important claims

## 49. Choose automation after the process is clear

Automate a stable, understood workflow. First document the trigger, inputs, output, permissions and failure behavior. A small manual checklist may be better than a fragile automation for an infrequent task.

1. Map the process
2. identify repeatable steps
3. define what happens on failure.

Check: What should precede automation?
Answer: A clear process and failure plan

## 50. Capstone: launch a team project

Combine a project home, shared draft, structured intake, agenda and action log. Review roles and linked-file access, test the respondent and meeting experience, and document how work moves from request to completion.

1. Use the workflow builder
2. assemble the project in your own account
3. test as the intended collaborator.

Check: What makes the project ready for handoff?
Answer: Clear ownership, access and next actions