DiscoveryVIP / Apps Script AcademyHelp

Educator resources and 25 presenter demonstrations

Demonstrations are prepared scripts, not produced videos. Rehearse timing and verify target-browser behavior. Ask learners to predict before Run, compare observed state, then explain and extend. Grade evidence, explanation, transfer and safe deployment separately.

1. What Apps Script can do

3–7 minutes; rehearse before recording

Launch Prepared Demo

We will explore what apps script can do using fictional data and real editable JavaScript.

  1. Open the prepared lesson and read the problem.

    First identify the input and the result we intend to observe.

  2. Find Source · Code.gs and predict the result.

    Read the important operation aloud. Ask the audience to predict what will change.

  3. Click Run on fresh sample.

    This executes our source locally. Watch the relevant preview and the actual console.

  4. Click Step Through, then Next operation.

    Inspect actual service calls. Pure JavaScript uses the supported snapshots instead.

  5. Change one argument or operation, then rerun.

    Compare the first divergent result with our prediction. The animation represents observed state.

  6. Click Show Finished Code, explain, and Save Script.

    Use the reference for comparison, then export the complete source and review real-Google setup.

Explain the input, operation and observed result, and state which Google behavior remains untested.

2. Running your first script

3–7 minutes; rehearse before recording

Launch Prepared Demo

We will explore running your first script using fictional data and real editable JavaScript.

  1. Open the prepared lesson and read the problem.

    First identify the input and the result we intend to observe.

  2. Find Source · Code.gs and predict the result.

    Read the important operation aloud. Ask the audience to predict what will change.

  3. Click Run on fresh sample.

    This executes our source locally. Watch the relevant preview and the actual console.

  4. Click Step Through, then Next operation.

    Inspect actual service calls. Pure JavaScript uses the supported snapshots instead.

  5. Change one argument or operation, then rerun.

    Compare the first divergent result with our prediction. The animation represents observed state.

  6. Click Show Finished Code, explain, and Save Script.

    Use the reference for comparison, then export the complete source and review real-Google setup.

Explain the input, operation and observed result, and state which Google behavior remains untested.

3. Variables and functions

3–7 minutes; rehearse before recording

Launch Prepared Demo

We will explore variables and functions using fictional data and real editable JavaScript.

  1. Open the prepared lesson and read the problem.

    First identify the input and the result we intend to observe.

  2. Find Source · Code.gs and predict the result.

    Read the important operation aloud. Ask the audience to predict what will change.

  3. Click Run on fresh sample.

    This executes our source locally. Watch the relevant preview and the actual console.

  4. Click Step Through, then Next operation.

    Inspect actual service calls. Pure JavaScript uses the supported snapshots instead.

  5. Change one argument or operation, then rerun.

    Compare the first divergent result with our prediction. The animation represents observed state.

  6. Click Show Finished Code, explain, and Save Script.

    Use the reference for comparison, then export the complete source and review real-Google setup.

Explain the input, operation and observed result, and state which Google behavior remains untested.

4. Exploring SpreadsheetApp

3–7 minutes; rehearse before recording

Launch Prepared Demo

We will explore exploring spreadsheetapp using fictional data and real editable JavaScript.

  1. Open the prepared lesson and read the problem.

    First identify the input and the result we intend to observe.

  2. Find Source · Code.gs and predict the result.

    Read the important operation aloud. Ask the audience to predict what will change.

  3. Click Run on fresh sample.

    This executes our source locally. Watch the relevant preview and the actual console.

  4. Click Step Through, then Next operation.

    Inspect actual service calls. Pure JavaScript uses the supported snapshots instead.

  5. Change one argument or operation, then rerun.

    Compare the first divergent result with our prediction. The animation represents observed state.

  6. Click Show Finished Code, explain, and Save Script.

    Use the reference for comparison, then export the complete source and review real-Google setup.

Explain the input, operation and observed result, and state which Google behavior remains untested.

5. Selecting ranges

3–7 minutes; rehearse before recording

Launch Prepared Demo

We will explore selecting ranges using fictional data and real editable JavaScript.

  1. Open the prepared lesson and read the problem.

    First identify the input and the result we intend to observe.

  2. Find Source · Code.gs and predict the result.

    Read the important operation aloud. Ask the audience to predict what will change.

  3. Click Run on fresh sample.

    This executes our source locally. Watch the relevant preview and the actual console.

  4. Click Step Through, then Next operation.

    Inspect actual service calls. Pure JavaScript uses the supported snapshots instead.

  5. Change one argument or operation, then rerun.

    Compare the first divergent result with our prediction. The animation represents observed state.

  6. Click Show Finished Code, explain, and Save Script.

    Use the reference for comparison, then export the complete source and review real-Google setup.

Explain the input, operation and observed result, and state which Google behavior remains untested.

6. Reading and writing values

3–7 minutes; rehearse before recording

Launch Prepared Demo

We will explore reading and writing values using fictional data and real editable JavaScript.

  1. Open the prepared lesson and read the problem.

    First identify the input and the result we intend to observe.

  2. Find Source · Code.gs and predict the result.

    Read the important operation aloud. Ask the audience to predict what will change.

  3. Click Run on fresh sample.

    This executes our source locally. Watch the relevant preview and the actual console.

  4. Click Step Through, then Next operation.

    Inspect actual service calls. Pure JavaScript uses the supported snapshots instead.

  5. Change one argument or operation, then rerun.

    Compare the first divergent result with our prediction. The animation represents observed state.

  6. Click Show Finished Code, explain, and Save Script.

    Use the reference for comparison, then export the complete source and review real-Google setup.

Explain the input, operation and observed result, and state which Google behavior remains untested.

7. Two-dimensional arrays

3–7 minutes; rehearse before recording

Launch Prepared Demo

We will explore two-dimensional arrays using fictional data and real editable JavaScript.

  1. Open the prepared lesson and read the problem.

    First identify the input and the result we intend to observe.

  2. Find Source · Code.gs and predict the result.

    Read the important operation aloud. Ask the audience to predict what will change.

  3. Click Run on fresh sample.

    This executes our source locally. Watch the relevant preview and the actual console.

  4. Click Step Through, then Next operation.

    Inspect actual service calls. Pure JavaScript uses the supported snapshots instead.

  5. Change one argument or operation, then rerun.

    Compare the first divergent result with our prediction. The animation represents observed state.

  6. Click Show Finished Code, explain, and Save Script.

    Use the reference for comparison, then export the complete source and review real-Google setup.

Explain the input, operation and observed result, and state which Google behavior remains untested.

8. Processing spreadsheet rows

3–7 minutes; rehearse before recording

Launch Prepared Demo

We will explore processing spreadsheet rows using fictional data and real editable JavaScript.

  1. Open the prepared lesson and read the problem.

    First identify the input and the result we intend to observe.

  2. Find Source · Code.gs and predict the result.

    Read the important operation aloud. Ask the audience to predict what will change.

  3. Click Run on fresh sample.

    This executes our source locally. Watch the relevant preview and the actual console.

  4. Click Step Through, then Next operation.

    Inspect actual service calls. Pure JavaScript uses the supported snapshots instead.

  5. Change one argument or operation, then rerun.

    Compare the first divergent result with our prediction. The animation represents observed state.

  6. Click Show Finished Code, explain, and Save Script.

    Use the reference for comparison, then export the complete source and review real-Google setup.

Explain the input, operation and observed result, and state which Google behavior remains untested.

9. Batching service calls

3–7 minutes; rehearse before recording

Launch Prepared Demo

We will explore batching service calls using fictional data and real editable JavaScript.

  1. Open the prepared lesson and read the problem.

    First identify the input and the result we intend to observe.

  2. Find Source · Code.gs and predict the result.

    Read the important operation aloud. Ask the audience to predict what will change.

  3. Click Run on fresh sample.

    This executes our source locally. Watch the relevant preview and the actual console.

  4. Click Step Through, then Next operation.

    Inspect actual service calls. Pure JavaScript uses the supported snapshots instead.

  5. Change one argument or operation, then rerun.

    Compare the first divergent result with our prediction. The animation represents observed state.

  6. Click Show Finished Code, explain, and Save Script.

    Use the reference for comparison, then export the complete source and review real-Google setup.

Explain the input, operation and observed result, and state which Google behavior remains untested.

10. Formatting spreadsheets

3–7 minutes; rehearse before recording

Launch Prepared Demo

We will explore formatting spreadsheets using fictional data and real editable JavaScript.

  1. Open the prepared lesson and read the problem.

    First identify the input and the result we intend to observe.

  2. Find Source · Code.gs and predict the result.

    Read the important operation aloud. Ask the audience to predict what will change.

  3. Click Run on fresh sample.

    This executes our source locally. Watch the relevant preview and the actual console.

  4. Click Step Through, then Next operation.

    Inspect actual service calls. Pure JavaScript uses the supported snapshots instead.

  5. Change one argument or operation, then rerun.

    Compare the first divergent result with our prediction. The animation represents observed state.

  6. Click Show Finished Code, explain, and Save Script.

    Use the reference for comparison, then export the complete source and review real-Google setup.

Explain the input, operation and observed result, and state which Google behavior remains untested.

11. Custom functions

3–7 minutes; rehearse before recording

Launch Prepared Demo

We will explore custom functions using fictional data and real editable JavaScript.

  1. Open the prepared lesson and read the problem.

    First identify the input and the result we intend to observe.

  2. Find Source · Code.gs and predict the result.

    Read the important operation aloud. Ask the audience to predict what will change.

  3. Click Run on fresh sample.

    This executes our source locally. Watch the relevant preview and the actual console.

  4. Click Step Through, then Next operation.

    Inspect actual service calls. Pure JavaScript uses the supported snapshots instead.

  5. Change one argument or operation, then rerun.

    Compare the first divergent result with our prediction. The animation represents observed state.

  6. Click Show Finished Code, explain, and Save Script.

    Use the reference for comparison, then export the complete source and review real-Google setup.

Explain the input, operation and observed result, and state which Google behavior remains untested.

12. Generating Google Docs

3–7 minutes; rehearse before recording

Launch Prepared Demo

We will explore generating google docs using fictional data and real editable JavaScript.

  1. Open the prepared lesson and read the problem.

    First identify the input and the result we intend to observe.

  2. Find Source · Code.gs and predict the result.

    Read the important operation aloud. Ask the audience to predict what will change.

  3. Click Run on fresh sample.

    This executes our source locally. Watch the relevant preview and the actual console.

  4. Click Step Through, then Next operation.

    Inspect actual service calls. Pure JavaScript uses the supported snapshots instead.

  5. Change one argument or operation, then rerun.

    Compare the first divergent result with our prediction. The animation represents observed state.

  6. Click Show Finished Code, explain, and Save Script.

    Use the reference for comparison, then export the complete source and review real-Google setup.

Explain the input, operation and observed result, and state which Google behavior remains untested.

13. Personalizing templates

3–7 minutes; rehearse before recording

Launch Prepared Demo

We will explore personalizing templates using fictional data and real editable JavaScript.

  1. Open the prepared lesson and read the problem.

    First identify the input and the result we intend to observe.

  2. Find Source · Code.gs and predict the result.

    Read the important operation aloud. Ask the audience to predict what will change.

  3. Click Run on fresh sample.

    This executes our source locally. Watch the relevant preview and the actual console.

  4. Click Step Through, then Next operation.

    Inspect actual service calls. Pure JavaScript uses the supported snapshots instead.

  5. Change one argument or operation, then rerun.

    Compare the first divergent result with our prediction. The animation represents observed state.

  6. Click Show Finished Code, explain, and Save Script.

    Use the reference for comparison, then export the complete source and review real-Google setup.

Explain the input, operation and observed result, and state which Google behavior remains untested.

14. Organizing Drive

3–7 minutes; rehearse before recording

Launch Prepared Demo

We will explore organizing drive using fictional data and real editable JavaScript.

  1. Open the prepared lesson and read the problem.

    First identify the input and the result we intend to observe.

  2. Find Source · Code.gs and predict the result.

    Read the important operation aloud. Ask the audience to predict what will change.

  3. Click Run on fresh sample.

    This executes our source locally. Watch the relevant preview and the actual console.

  4. Click Step Through, then Next operation.

    Inspect actual service calls. Pure JavaScript uses the supported snapshots instead.

  5. Change one argument or operation, then rerun.

    Compare the first divergent result with our prediction. The animation represents observed state.

  6. Click Show Finished Code, explain, and Save Script.

    Use the reference for comparison, then export the complete source and review real-Google setup.

Explain the input, operation and observed result, and state which Google behavior remains untested.

15. Preparing email drafts

3–7 minutes; rehearse before recording

Launch Prepared Demo

We will explore preparing email drafts using fictional data and real editable JavaScript.

  1. Open the prepared lesson and read the problem.

    First identify the input and the result we intend to observe.

  2. Find Source · Code.gs and predict the result.

    Read the important operation aloud. Ask the audience to predict what will change.

  3. Click Run on fresh sample.

    This executes our source locally. Watch the relevant preview and the actual console.

  4. Click Step Through, then Next operation.

    Inspect actual service calls. Pure JavaScript uses the supported snapshots instead.

  5. Change one argument or operation, then rerun.

    Compare the first divergent result with our prediction. The animation represents observed state.

  6. Click Show Finished Code, explain, and Save Script.

    Use the reference for comparison, then export the complete source and review real-Google setup.

Explain the input, operation and observed result, and state which Google behavior remains untested.

16. Building Forms

3–7 minutes; rehearse before recording

Launch Prepared Demo

We will explore building forms using fictional data and real editable JavaScript.

  1. Open the prepared lesson and read the problem.

    First identify the input and the result we intend to observe.

  2. Find Source · Code.gs and predict the result.

    Read the important operation aloud. Ask the audience to predict what will change.

  3. Click Run on fresh sample.

    This executes our source locally. Watch the relevant preview and the actual console.

  4. Click Step Through, then Next operation.

    Inspect actual service calls. Pure JavaScript uses the supported snapshots instead.

  5. Change one argument or operation, then rerun.

    Compare the first divergent result with our prediction. The animation represents observed state.

  6. Click Show Finished Code, explain, and Save Script.

    Use the reference for comparison, then export the complete source and review real-Google setup.

Explain the input, operation and observed result, and state which Google behavior remains untested.

17. Processing submissions

3–7 minutes; rehearse before recording

Launch Prepared Demo

We will explore processing submissions using fictional data and real editable JavaScript.

  1. Open the prepared lesson and read the problem.

    First identify the input and the result we intend to observe.

  2. Find Source · Code.gs and predict the result.

    Read the important operation aloud. Ask the audience to predict what will change.

  3. Click Run on fresh sample.

    This executes our source locally. Watch the relevant preview and the actual console.

  4. Click Step Through, then Next operation.

    Inspect actual service calls. Pure JavaScript uses the supported snapshots instead.

  5. Change one argument or operation, then rerun.

    Compare the first divergent result with our prediction. The animation represents observed state.

  6. Click Show Finished Code, explain, and Save Script.

    Use the reference for comparison, then export the complete source and review real-Google setup.

Explain the input, operation and observed result, and state which Google behavior remains untested.

18. Creating calendar events

3–7 minutes; rehearse before recording

Launch Prepared Demo

We will explore creating calendar events using fictional data and real editable JavaScript.

  1. Open the prepared lesson and read the problem.

    First identify the input and the result we intend to observe.

  2. Find Source · Code.gs and predict the result.

    Read the important operation aloud. Ask the audience to predict what will change.

  3. Click Run on fresh sample.

    This executes our source locally. Watch the relevant preview and the actual console.

  4. Click Step Through, then Next operation.

    Inspect actual service calls. Pure JavaScript uses the supported snapshots instead.

  5. Change one argument or operation, then rerun.

    Compare the first divergent result with our prediction. The animation represents observed state.

  6. Click Show Finished Code, explain, and Save Script.

    Use the reference for comparison, then export the complete source and review real-Google setup.

Explain the input, operation and observed result, and state which Google behavior remains untested.

19. Generating Slides

3–7 minutes; rehearse before recording

Launch Prepared Demo

We will explore generating slides using fictional data and real editable JavaScript.

  1. Open the prepared lesson and read the problem.

    First identify the input and the result we intend to observe.

  2. Find Source · Code.gs and predict the result.

    Read the important operation aloud. Ask the audience to predict what will change.

  3. Click Run on fresh sample.

    This executes our source locally. Watch the relevant preview and the actual console.

  4. Click Step Through, then Next operation.

    Inspect actual service calls. Pure JavaScript uses the supported snapshots instead.

  5. Change one argument or operation, then rerun.

    Compare the first divergent result with our prediction. The animation represents observed state.

  6. Click Show Finished Code, explain, and Save Script.

    Use the reference for comparison, then export the complete source and review real-Google setup.

Explain the input, operation and observed result, and state which Google behavior remains untested.

20. Automatic triggers

3–7 minutes; rehearse before recording

Launch Prepared Demo

We will explore automatic triggers using fictional data and real editable JavaScript.

  1. Open the prepared lesson and read the problem.

    First identify the input and the result we intend to observe.

  2. Find Source · Code.gs and predict the result.

    Read the important operation aloud. Ask the audience to predict what will change.

  3. Click Run on fresh sample.

    This executes our source locally. Watch the relevant preview and the actual console.

  4. Click Step Through, then Next operation.

    Inspect actual service calls. Pure JavaScript uses the supported snapshots instead.

  5. Change one argument or operation, then rerun.

    Compare the first divergent result with our prediction. The animation represents observed state.

  6. Click Show Finished Code, explain, and Save Script.

    Use the reference for comparison, then export the complete source and review real-Google setup.

Explain the input, operation and observed result, and state which Google behavior remains untested.

21. Menus and sidebars

3–7 minutes; rehearse before recording

Launch Prepared Demo

We will explore menus and sidebars using fictional data and real editable JavaScript.

  1. Open the prepared lesson and read the problem.

    First identify the input and the result we intend to observe.

  2. Find Source · Code.gs and predict the result.

    Read the important operation aloud. Ask the audience to predict what will change.

  3. Click Run on fresh sample.

    This executes our source locally. Watch the relevant preview and the actual console.

  4. Click Step Through, then Next operation.

    Inspect actual service calls. Pure JavaScript uses the supported snapshots instead.

  5. Change one argument or operation, then rerun.

    Compare the first divergent result with our prediction. The animation represents observed state.

  6. Click Show Finished Code, explain, and Save Script.

    Use the reference for comparison, then export the complete source and review real-Google setup.

Explain the input, operation and observed result, and state which Google behavior remains untested.

22. Building a web app

3–7 minutes; rehearse before recording

Launch Prepared Demo

We will explore building a web app using fictional data and real editable JavaScript.

  1. Open the prepared lesson and read the problem.

    First identify the input and the result we intend to observe.

  2. Find Source · Code.gs and predict the result.

    Read the important operation aloud. Ask the audience to predict what will change.

  3. Click Run on fresh sample.

    This executes our source locally. Watch the relevant preview and the actual console.

  4. Click Step Through, then Next operation.

    Inspect actual service calls. Pure JavaScript uses the supported snapshots instead.

  5. Change one argument or operation, then rerun.

    Compare the first divergent result with our prediction. The animation represents observed state.

  6. Click Show Finished Code, explain, and Save Script.

    Use the reference for comparison, then export the complete source and review real-Google setup.

Explain the input, operation and observed result, and state which Google behavior remains untested.

23. External API fixtures

3–7 minutes; rehearse before recording

Launch Prepared Demo

We will explore external api fixtures using fictional data and real editable JavaScript.

  1. Open the prepared lesson and read the problem.

    First identify the input and the result we intend to observe.

  2. Find Source · Code.gs and predict the result.

    Read the important operation aloud. Ask the audience to predict what will change.

  3. Click Run on fresh sample.

    This executes our source locally. Watch the relevant preview and the actual console.

  4. Click Step Through, then Next operation.

    Inspect actual service calls. Pure JavaScript uses the supported snapshots instead.

  5. Change one argument or operation, then rerun.

    Compare the first divergent result with our prediction. The animation represents observed state.

  6. Click Show Finished Code, explain, and Save Script.

    Use the reference for comparison, then export the complete source and review real-Google setup.

Explain the input, operation and observed result, and state which Google behavior remains untested.

24. Connecting Gemini

3–7 minutes; rehearse before recording

Launch Prepared Demo

We will explore connecting gemini using fictional data and real editable JavaScript.

  1. Open the prepared lesson and read the problem.

    First identify the input and the result we intend to observe.

  2. Find Source · Code.gs and predict the result.

    Read the important operation aloud. Ask the audience to predict what will change.

  3. Click Run on fresh sample.

    This executes our source locally. Watch the relevant preview and the actual console.

  4. Click Step Through, then Next operation.

    Inspect actual service calls. Pure JavaScript uses the supported snapshots instead.

  5. Change one argument or operation, then rerun.

    Compare the first divergent result with our prediction. The animation represents observed state.

  6. Click Show Finished Code, explain, and Save Script.

    Use the reference for comparison, then export the complete source and review real-Google setup.

Explain the input, operation and observed result, and state which Google behavior remains untested.

25. Multi-service automation

3–7 minutes; rehearse before recording

Launch Prepared Demo

We will explore multi-service automation using fictional data and real editable JavaScript.

  1. Open the prepared lesson and read the problem.

    First identify the input and the result we intend to observe.

  2. Find Source · Code.gs and predict the result.

    Read the important operation aloud. Ask the audience to predict what will change.

  3. Click Run on fresh sample.

    This executes our source locally. Watch the relevant preview and the actual console.

  4. Click Step Through, then Next operation.

    Inspect actual service calls. Pure JavaScript uses the supported snapshots instead.

  5. Change one argument or operation, then rerun.

    Compare the first divergent result with our prediction. The animation represents observed state.

  6. Click Show Finished Code, explain, and Save Script.

    Use the reference for comparison, then export the complete source and review real-Google setup.

Explain the input, operation and observed result, and state which Google behavior remains untested.

Module teaching plan 1: Getting started

Use the five lessons in order or select a targeted review. First elicit a prediction, run the smallest example, then let pairs modify one input and compare evidence. Discuss which state changes prove the result and which real Google assumptions remain.

Worksheet: record input, predicted output, actual output, first mismatch, repair and second test. Assessment rubric: 0 = no evidence; 1 = working sample only; 2 = working normal and invalid tests with explanation; 3 = independent extension plus reviewed deployment and recovery plan.

Project assignment: choose the related complete project, implement its missing operation, explain service choices and demonstrate a controlled failure. Review the transcript and actual outputs rather than awarding mastery for page visits.

Module teaching plan 2: JavaScript fundamentals

Use the five lessons in order or select a targeted review. First elicit a prediction, run the smallest example, then let pairs modify one input and compare evidence. Discuss which state changes prove the result and which real Google assumptions remain.

Worksheet: record input, predicted output, actual output, first mismatch, repair and second test. Assessment rubric: 0 = no evidence; 1 = working sample only; 2 = working normal and invalid tests with explanation; 3 = independent extension plus reviewed deployment and recovery plan.

Project assignment: choose the related complete project, implement its missing operation, explain service choices and demonstrate a controlled failure. Review the transcript and actual outputs rather than awarding mastery for page visits.

Module teaching plan 3: Arrays, objects and loops

Use the five lessons in order or select a targeted review. First elicit a prediction, run the smallest example, then let pairs modify one input and compare evidence. Discuss which state changes prove the result and which real Google assumptions remain.

Worksheet: record input, predicted output, actual output, first mismatch, repair and second test. Assessment rubric: 0 = no evidence; 1 = working sample only; 2 = working normal and invalid tests with explanation; 3 = independent extension plus reviewed deployment and recovery plan.

Project assignment: choose the related complete project, implement its missing operation, explain service choices and demonstrate a controlled failure. Review the transcript and actual outputs rather than awarding mastery for page visits.

Module teaching plan 4: Google Sheets fundamentals

Use the five lessons in order or select a targeted review. First elicit a prediction, run the smallest example, then let pairs modify one input and compare evidence. Discuss which state changes prove the result and which real Google assumptions remain.

Worksheet: record input, predicted output, actual output, first mismatch, repair and second test. Assessment rubric: 0 = no evidence; 1 = working sample only; 2 = working normal and invalid tests with explanation; 3 = independent extension plus reviewed deployment and recovery plan.

Project assignment: choose the related complete project, implement its missing operation, explain service choices and demonstrate a controlled failure. Review the transcript and actual outputs rather than awarding mastery for page visits.

Module teaching plan 5: Processing spreadsheet data

Use the five lessons in order or select a targeted review. First elicit a prediction, run the smallest example, then let pairs modify one input and compare evidence. Discuss which state changes prove the result and which real Google assumptions remain.

Worksheet: record input, predicted output, actual output, first mismatch, repair and second test. Assessment rubric: 0 = no evidence; 1 = working sample only; 2 = working normal and invalid tests with explanation; 3 = independent extension plus reviewed deployment and recovery plan.

Project assignment: choose the related complete project, implement its missing operation, explain service choices and demonstrate a controlled failure. Review the transcript and actual outputs rather than awarding mastery for page visits.

Module teaching plan 6: Advanced spreadsheet operations

Use the five lessons in order or select a targeted review. First elicit a prediction, run the smallest example, then let pairs modify one input and compare evidence. Discuss which state changes prove the result and which real Google assumptions remain.

Worksheet: record input, predicted output, actual output, first mismatch, repair and second test. Assessment rubric: 0 = no evidence; 1 = working sample only; 2 = working normal and invalid tests with explanation; 3 = independent extension plus reviewed deployment and recovery plan.

Project assignment: choose the related complete project, implement its missing operation, explain service choices and demonstrate a controlled failure. Review the transcript and actual outputs rather than awarding mastery for page visits.

Module teaching plan 7: Google Docs automation

Use the five lessons in order or select a targeted review. First elicit a prediction, run the smallest example, then let pairs modify one input and compare evidence. Discuss which state changes prove the result and which real Google assumptions remain.

Worksheet: record input, predicted output, actual output, first mismatch, repair and second test. Assessment rubric: 0 = no evidence; 1 = working sample only; 2 = working normal and invalid tests with explanation; 3 = independent extension plus reviewed deployment and recovery plan.

Project assignment: choose the related complete project, implement its missing operation, explain service choices and demonstrate a controlled failure. Review the transcript and actual outputs rather than awarding mastery for page visits.

Module teaching plan 8: Google Drive automation

Use the five lessons in order or select a targeted review. First elicit a prediction, run the smallest example, then let pairs modify one input and compare evidence. Discuss which state changes prove the result and which real Google assumptions remain.

Worksheet: record input, predicted output, actual output, first mismatch, repair and second test. Assessment rubric: 0 = no evidence; 1 = working sample only; 2 = working normal and invalid tests with explanation; 3 = independent extension plus reviewed deployment and recovery plan.

Project assignment: choose the related complete project, implement its missing operation, explain service choices and demonstrate a controlled failure. Review the transcript and actual outputs rather than awarding mastery for page visits.

Module teaching plan 9: Gmail and email automation

Use the five lessons in order or select a targeted review. First elicit a prediction, run the smallest example, then let pairs modify one input and compare evidence. Discuss which state changes prove the result and which real Google assumptions remain.

Worksheet: record input, predicted output, actual output, first mismatch, repair and second test. Assessment rubric: 0 = no evidence; 1 = working sample only; 2 = working normal and invalid tests with explanation; 3 = independent extension plus reviewed deployment and recovery plan.

Project assignment: choose the related complete project, implement its missing operation, explain service choices and demonstrate a controlled failure. Review the transcript and actual outputs rather than awarding mastery for page visits.

Module teaching plan 10: Google Forms automation

Use the five lessons in order or select a targeted review. First elicit a prediction, run the smallest example, then let pairs modify one input and compare evidence. Discuss which state changes prove the result and which real Google assumptions remain.

Worksheet: record input, predicted output, actual output, first mismatch, repair and second test. Assessment rubric: 0 = no evidence; 1 = working sample only; 2 = working normal and invalid tests with explanation; 3 = independent extension plus reviewed deployment and recovery plan.

Project assignment: choose the related complete project, implement its missing operation, explain service choices and demonstrate a controlled failure. Review the transcript and actual outputs rather than awarding mastery for page visits.

Module teaching plan 11: Google Calendar automation

Use the five lessons in order or select a targeted review. First elicit a prediction, run the smallest example, then let pairs modify one input and compare evidence. Discuss which state changes prove the result and which real Google assumptions remain.

Worksheet: record input, predicted output, actual output, first mismatch, repair and second test. Assessment rubric: 0 = no evidence; 1 = working sample only; 2 = working normal and invalid tests with explanation; 3 = independent extension plus reviewed deployment and recovery plan.

Project assignment: choose the related complete project, implement its missing operation, explain service choices and demonstrate a controlled failure. Review the transcript and actual outputs rather than awarding mastery for page visits.

Module teaching plan 12: Google Slides automation

Use the five lessons in order or select a targeted review. First elicit a prediction, run the smallest example, then let pairs modify one input and compare evidence. Discuss which state changes prove the result and which real Google assumptions remain.

Worksheet: record input, predicted output, actual output, first mismatch, repair and second test. Assessment rubric: 0 = no evidence; 1 = working sample only; 2 = working normal and invalid tests with explanation; 3 = independent extension plus reviewed deployment and recovery plan.

Project assignment: choose the related complete project, implement its missing operation, explain service choices and demonstrate a controlled failure. Review the transcript and actual outputs rather than awarding mastery for page visits.

Module teaching plan 13: Triggers and events

Use the five lessons in order or select a targeted review. First elicit a prediction, run the smallest example, then let pairs modify one input and compare evidence. Discuss which state changes prove the result and which real Google assumptions remain.

Worksheet: record input, predicted output, actual output, first mismatch, repair and second test. Assessment rubric: 0 = no evidence; 1 = working sample only; 2 = working normal and invalid tests with explanation; 3 = independent extension plus reviewed deployment and recovery plan.

Project assignment: choose the related complete project, implement its missing operation, explain service choices and demonstrate a controlled failure. Review the transcript and actual outputs rather than awarding mastery for page visits.

Module teaching plan 14: Menus, dialogs and sidebars

Use the five lessons in order or select a targeted review. First elicit a prediction, run the smallest example, then let pairs modify one input and compare evidence. Discuss which state changes prove the result and which real Google assumptions remain.

Worksheet: record input, predicted output, actual output, first mismatch, repair and second test. Assessment rubric: 0 = no evidence; 1 = working sample only; 2 = working normal and invalid tests with explanation; 3 = independent extension plus reviewed deployment and recovery plan.

Project assignment: choose the related complete project, implement its missing operation, explain service choices and demonstrate a controlled failure. Review the transcript and actual outputs rather than awarding mastery for page visits.

Module teaching plan 15: Web applications

Use the five lessons in order or select a targeted review. First elicit a prediction, run the smallest example, then let pairs modify one input and compare evidence. Discuss which state changes prove the result and which real Google assumptions remain.

Worksheet: record input, predicted output, actual output, first mismatch, repair and second test. Assessment rubric: 0 = no evidence; 1 = working sample only; 2 = working normal and invalid tests with explanation; 3 = independent extension plus reviewed deployment and recovery plan.

Project assignment: choose the related complete project, implement its missing operation, explain service choices and demonstrate a controlled failure. Review the transcript and actual outputs rather than awarding mastery for page visits.

Module teaching plan 16: APIs and external services

Use the five lessons in order or select a targeted review. First elicit a prediction, run the smallest example, then let pairs modify one input and compare evidence. Discuss which state changes prove the result and which real Google assumptions remain.

Worksheet: record input, predicted output, actual output, first mismatch, repair and second test. Assessment rubric: 0 = no evidence; 1 = working sample only; 2 = working normal and invalid tests with explanation; 3 = independent extension plus reviewed deployment and recovery plan.

Project assignment: choose the related complete project, implement its missing operation, explain service choices and demonstrate a controlled failure. Review the transcript and actual outputs rather than awarding mastery for page visits.

Module teaching plan 17: Gemini and AI automation

Use the five lessons in order or select a targeted review. First elicit a prediction, run the smallest example, then let pairs modify one input and compare evidence. Discuss which state changes prove the result and which real Google assumptions remain.

Worksheet: record input, predicted output, actual output, first mismatch, repair and second test. Assessment rubric: 0 = no evidence; 1 = working sample only; 2 = working normal and invalid tests with explanation; 3 = independent extension plus reviewed deployment and recovery plan.

Project assignment: choose the related complete project, implement its missing operation, explain service choices and demonstrate a controlled failure. Review the transcript and actual outputs rather than awarding mastery for page visits.

Module teaching plan 18: Debugging and reliability

Use the five lessons in order or select a targeted review. First elicit a prediction, run the smallest example, then let pairs modify one input and compare evidence. Discuss which state changes prove the result and which real Google assumptions remain.

Worksheet: record input, predicted output, actual output, first mismatch, repair and second test. Assessment rubric: 0 = no evidence; 1 = working sample only; 2 = working normal and invalid tests with explanation; 3 = independent extension plus reviewed deployment and recovery plan.

Project assignment: choose the related complete project, implement its missing operation, explain service choices and demonstrate a controlled failure. Review the transcript and actual outputs rather than awarding mastery for page visits.

Module teaching plan 19: Professional development

Use the five lessons in order or select a targeted review. First elicit a prediction, run the smallest example, then let pairs modify one input and compare evidence. Discuss which state changes prove the result and which real Google assumptions remain.

Worksheet: record input, predicted output, actual output, first mismatch, repair and second test. Assessment rubric: 0 = no evidence; 1 = working sample only; 2 = working normal and invalid tests with explanation; 3 = independent extension plus reviewed deployment and recovery plan.

Project assignment: choose the related complete project, implement its missing operation, explain service choices and demonstrate a controlled failure. Review the transcript and actual outputs rather than awarding mastery for page visits.

Module teaching plan 20: Complete application development

Use the five lessons in order or select a targeted review. First elicit a prediction, run the smallest example, then let pairs modify one input and compare evidence. Discuss which state changes prove the result and which real Google assumptions remain.

Worksheet: record input, predicted output, actual output, first mismatch, repair and second test. Assessment rubric: 0 = no evidence; 1 = working sample only; 2 = working normal and invalid tests with explanation; 3 = independent extension plus reviewed deployment and recovery plan.

Project assignment: choose the related complete project, implement its missing operation, explain service choices and demonstrate a controlled failure. Review the transcript and actual outputs rather than awarding mastery for page visits.

Independently launchable experiments