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 DemoWe will explore what apps script can do using fictional data and real editable JavaScript.
- Open the prepared lesson and read the problem.
First identify the input and the result we intend to observe.
- Find Source · Code.gs and predict the result.
Read the important operation aloud. Ask the audience to predict what will change.
- Click Run on fresh sample.
This executes our source locally. Watch the relevant preview and the actual console.
- Click Step Through, then Next operation.
Inspect actual service calls. Pure JavaScript uses the supported snapshots instead.
- Change one argument or operation, then rerun.
Compare the first divergent result with our prediction. The animation represents observed state.
- 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 DemoWe will explore running your first script using fictional data and real editable JavaScript.
- Open the prepared lesson and read the problem.
First identify the input and the result we intend to observe.
- Find Source · Code.gs and predict the result.
Read the important operation aloud. Ask the audience to predict what will change.
- Click Run on fresh sample.
This executes our source locally. Watch the relevant preview and the actual console.
- Click Step Through, then Next operation.
Inspect actual service calls. Pure JavaScript uses the supported snapshots instead.
- Change one argument or operation, then rerun.
Compare the first divergent result with our prediction. The animation represents observed state.
- 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 DemoWe will explore variables and functions using fictional data and real editable JavaScript.
- Open the prepared lesson and read the problem.
First identify the input and the result we intend to observe.
- Find Source · Code.gs and predict the result.
Read the important operation aloud. Ask the audience to predict what will change.
- Click Run on fresh sample.
This executes our source locally. Watch the relevant preview and the actual console.
- Click Step Through, then Next operation.
Inspect actual service calls. Pure JavaScript uses the supported snapshots instead.
- Change one argument or operation, then rerun.
Compare the first divergent result with our prediction. The animation represents observed state.
- 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 DemoWe will explore exploring spreadsheetapp using fictional data and real editable JavaScript.
- Open the prepared lesson and read the problem.
First identify the input and the result we intend to observe.
- Find Source · Code.gs and predict the result.
Read the important operation aloud. Ask the audience to predict what will change.
- Click Run on fresh sample.
This executes our source locally. Watch the relevant preview and the actual console.
- Click Step Through, then Next operation.
Inspect actual service calls. Pure JavaScript uses the supported snapshots instead.
- Change one argument or operation, then rerun.
Compare the first divergent result with our prediction. The animation represents observed state.
- 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 DemoWe will explore selecting ranges using fictional data and real editable JavaScript.
- Open the prepared lesson and read the problem.
First identify the input and the result we intend to observe.
- Find Source · Code.gs and predict the result.
Read the important operation aloud. Ask the audience to predict what will change.
- Click Run on fresh sample.
This executes our source locally. Watch the relevant preview and the actual console.
- Click Step Through, then Next operation.
Inspect actual service calls. Pure JavaScript uses the supported snapshots instead.
- Change one argument or operation, then rerun.
Compare the first divergent result with our prediction. The animation represents observed state.
- 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 DemoWe will explore reading and writing values using fictional data and real editable JavaScript.
- Open the prepared lesson and read the problem.
First identify the input and the result we intend to observe.
- Find Source · Code.gs and predict the result.
Read the important operation aloud. Ask the audience to predict what will change.
- Click Run on fresh sample.
This executes our source locally. Watch the relevant preview and the actual console.
- Click Step Through, then Next operation.
Inspect actual service calls. Pure JavaScript uses the supported snapshots instead.
- Change one argument or operation, then rerun.
Compare the first divergent result with our prediction. The animation represents observed state.
- 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 DemoWe will explore two-dimensional arrays using fictional data and real editable JavaScript.
- Open the prepared lesson and read the problem.
First identify the input and the result we intend to observe.
- Find Source · Code.gs and predict the result.
Read the important operation aloud. Ask the audience to predict what will change.
- Click Run on fresh sample.
This executes our source locally. Watch the relevant preview and the actual console.
- Click Step Through, then Next operation.
Inspect actual service calls. Pure JavaScript uses the supported snapshots instead.
- Change one argument or operation, then rerun.
Compare the first divergent result with our prediction. The animation represents observed state.
- 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 DemoWe will explore processing spreadsheet rows using fictional data and real editable JavaScript.
- Open the prepared lesson and read the problem.
First identify the input and the result we intend to observe.
- Find Source · Code.gs and predict the result.
Read the important operation aloud. Ask the audience to predict what will change.
- Click Run on fresh sample.
This executes our source locally. Watch the relevant preview and the actual console.
- Click Step Through, then Next operation.
Inspect actual service calls. Pure JavaScript uses the supported snapshots instead.
- Change one argument or operation, then rerun.
Compare the first divergent result with our prediction. The animation represents observed state.
- 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 DemoWe will explore batching service calls using fictional data and real editable JavaScript.
- Open the prepared lesson and read the problem.
First identify the input and the result we intend to observe.
- Find Source · Code.gs and predict the result.
Read the important operation aloud. Ask the audience to predict what will change.
- Click Run on fresh sample.
This executes our source locally. Watch the relevant preview and the actual console.
- Click Step Through, then Next operation.
Inspect actual service calls. Pure JavaScript uses the supported snapshots instead.
- Change one argument or operation, then rerun.
Compare the first divergent result with our prediction. The animation represents observed state.
- 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 DemoWe will explore formatting spreadsheets using fictional data and real editable JavaScript.
- Open the prepared lesson and read the problem.
First identify the input and the result we intend to observe.
- Find Source · Code.gs and predict the result.
Read the important operation aloud. Ask the audience to predict what will change.
- Click Run on fresh sample.
This executes our source locally. Watch the relevant preview and the actual console.
- Click Step Through, then Next operation.
Inspect actual service calls. Pure JavaScript uses the supported snapshots instead.
- Change one argument or operation, then rerun.
Compare the first divergent result with our prediction. The animation represents observed state.
- 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 DemoWe will explore custom functions using fictional data and real editable JavaScript.
- Open the prepared lesson and read the problem.
First identify the input and the result we intend to observe.
- Find Source · Code.gs and predict the result.
Read the important operation aloud. Ask the audience to predict what will change.
- Click Run on fresh sample.
This executes our source locally. Watch the relevant preview and the actual console.
- Click Step Through, then Next operation.
Inspect actual service calls. Pure JavaScript uses the supported snapshots instead.
- Change one argument or operation, then rerun.
Compare the first divergent result with our prediction. The animation represents observed state.
- 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 DemoWe will explore generating google docs using fictional data and real editable JavaScript.
- Open the prepared lesson and read the problem.
First identify the input and the result we intend to observe.
- Find Source · Code.gs and predict the result.
Read the important operation aloud. Ask the audience to predict what will change.
- Click Run on fresh sample.
This executes our source locally. Watch the relevant preview and the actual console.
- Click Step Through, then Next operation.
Inspect actual service calls. Pure JavaScript uses the supported snapshots instead.
- Change one argument or operation, then rerun.
Compare the first divergent result with our prediction. The animation represents observed state.
- 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 DemoWe will explore personalizing templates using fictional data and real editable JavaScript.
- Open the prepared lesson and read the problem.
First identify the input and the result we intend to observe.
- Find Source · Code.gs and predict the result.
Read the important operation aloud. Ask the audience to predict what will change.
- Click Run on fresh sample.
This executes our source locally. Watch the relevant preview and the actual console.
- Click Step Through, then Next operation.
Inspect actual service calls. Pure JavaScript uses the supported snapshots instead.
- Change one argument or operation, then rerun.
Compare the first divergent result with our prediction. The animation represents observed state.
- 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 DemoWe will explore organizing drive using fictional data and real editable JavaScript.
- Open the prepared lesson and read the problem.
First identify the input and the result we intend to observe.
- Find Source · Code.gs and predict the result.
Read the important operation aloud. Ask the audience to predict what will change.
- Click Run on fresh sample.
This executes our source locally. Watch the relevant preview and the actual console.
- Click Step Through, then Next operation.
Inspect actual service calls. Pure JavaScript uses the supported snapshots instead.
- Change one argument or operation, then rerun.
Compare the first divergent result with our prediction. The animation represents observed state.
- 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 DemoWe will explore preparing email drafts using fictional data and real editable JavaScript.
- Open the prepared lesson and read the problem.
First identify the input and the result we intend to observe.
- Find Source · Code.gs and predict the result.
Read the important operation aloud. Ask the audience to predict what will change.
- Click Run on fresh sample.
This executes our source locally. Watch the relevant preview and the actual console.
- Click Step Through, then Next operation.
Inspect actual service calls. Pure JavaScript uses the supported snapshots instead.
- Change one argument or operation, then rerun.
Compare the first divergent result with our prediction. The animation represents observed state.
- 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 DemoWe will explore building forms using fictional data and real editable JavaScript.
- Open the prepared lesson and read the problem.
First identify the input and the result we intend to observe.
- Find Source · Code.gs and predict the result.
Read the important operation aloud. Ask the audience to predict what will change.
- Click Run on fresh sample.
This executes our source locally. Watch the relevant preview and the actual console.
- Click Step Through, then Next operation.
Inspect actual service calls. Pure JavaScript uses the supported snapshots instead.
- Change one argument or operation, then rerun.
Compare the first divergent result with our prediction. The animation represents observed state.
- 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 DemoWe will explore processing submissions using fictional data and real editable JavaScript.
- Open the prepared lesson and read the problem.
First identify the input and the result we intend to observe.
- Find Source · Code.gs and predict the result.
Read the important operation aloud. Ask the audience to predict what will change.
- Click Run on fresh sample.
This executes our source locally. Watch the relevant preview and the actual console.
- Click Step Through, then Next operation.
Inspect actual service calls. Pure JavaScript uses the supported snapshots instead.
- Change one argument or operation, then rerun.
Compare the first divergent result with our prediction. The animation represents observed state.
- 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 DemoWe will explore creating calendar events using fictional data and real editable JavaScript.
- Open the prepared lesson and read the problem.
First identify the input and the result we intend to observe.
- Find Source · Code.gs and predict the result.
Read the important operation aloud. Ask the audience to predict what will change.
- Click Run on fresh sample.
This executes our source locally. Watch the relevant preview and the actual console.
- Click Step Through, then Next operation.
Inspect actual service calls. Pure JavaScript uses the supported snapshots instead.
- Change one argument or operation, then rerun.
Compare the first divergent result with our prediction. The animation represents observed state.
- 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 DemoWe will explore generating slides using fictional data and real editable JavaScript.
- Open the prepared lesson and read the problem.
First identify the input and the result we intend to observe.
- Find Source · Code.gs and predict the result.
Read the important operation aloud. Ask the audience to predict what will change.
- Click Run on fresh sample.
This executes our source locally. Watch the relevant preview and the actual console.
- Click Step Through, then Next operation.
Inspect actual service calls. Pure JavaScript uses the supported snapshots instead.
- Change one argument or operation, then rerun.
Compare the first divergent result with our prediction. The animation represents observed state.
- 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 DemoWe will explore automatic triggers using fictional data and real editable JavaScript.
- Open the prepared lesson and read the problem.
First identify the input and the result we intend to observe.
- Find Source · Code.gs and predict the result.
Read the important operation aloud. Ask the audience to predict what will change.
- Click Run on fresh sample.
This executes our source locally. Watch the relevant preview and the actual console.
- Click Step Through, then Next operation.
Inspect actual service calls. Pure JavaScript uses the supported snapshots instead.
- Change one argument or operation, then rerun.
Compare the first divergent result with our prediction. The animation represents observed state.
- 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 DemoWe will explore menus and sidebars using fictional data and real editable JavaScript.
- Open the prepared lesson and read the problem.
First identify the input and the result we intend to observe.
- Find Source · Code.gs and predict the result.
Read the important operation aloud. Ask the audience to predict what will change.
- Click Run on fresh sample.
This executes our source locally. Watch the relevant preview and the actual console.
- Click Step Through, then Next operation.
Inspect actual service calls. Pure JavaScript uses the supported snapshots instead.
- Change one argument or operation, then rerun.
Compare the first divergent result with our prediction. The animation represents observed state.
- 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 DemoWe will explore building a web app using fictional data and real editable JavaScript.
- Open the prepared lesson and read the problem.
First identify the input and the result we intend to observe.
- Find Source · Code.gs and predict the result.
Read the important operation aloud. Ask the audience to predict what will change.
- Click Run on fresh sample.
This executes our source locally. Watch the relevant preview and the actual console.
- Click Step Through, then Next operation.
Inspect actual service calls. Pure JavaScript uses the supported snapshots instead.
- Change one argument or operation, then rerun.
Compare the first divergent result with our prediction. The animation represents observed state.
- 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 DemoWe will explore external api fixtures using fictional data and real editable JavaScript.
- Open the prepared lesson and read the problem.
First identify the input and the result we intend to observe.
- Find Source · Code.gs and predict the result.
Read the important operation aloud. Ask the audience to predict what will change.
- Click Run on fresh sample.
This executes our source locally. Watch the relevant preview and the actual console.
- Click Step Through, then Next operation.
Inspect actual service calls. Pure JavaScript uses the supported snapshots instead.
- Change one argument or operation, then rerun.
Compare the first divergent result with our prediction. The animation represents observed state.
- 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 DemoWe will explore connecting gemini using fictional data and real editable JavaScript.
- Open the prepared lesson and read the problem.
First identify the input and the result we intend to observe.
- Find Source · Code.gs and predict the result.
Read the important operation aloud. Ask the audience to predict what will change.
- Click Run on fresh sample.
This executes our source locally. Watch the relevant preview and the actual console.
- Click Step Through, then Next operation.
Inspect actual service calls. Pure JavaScript uses the supported snapshots instead.
- Change one argument or operation, then rerun.
Compare the first divergent result with our prediction. The animation represents observed state.
- 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 DemoWe will explore multi-service automation using fictional data and real editable JavaScript.
- Open the prepared lesson and read the problem.
First identify the input and the result we intend to observe.
- Find Source · Code.gs and predict the result.
Read the important operation aloud. Ask the audience to predict what will change.
- Click Run on fresh sample.
This executes our source locally. Watch the relevant preview and the actual console.
- Click Step Through, then Next operation.
Inspect actual service calls. Pure JavaScript uses the supported snapshots instead.
- Change one argument or operation, then rerun.
Compare the first divergent result with our prediction. The animation represents observed state.
- 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
- Workspace service relationship map
- Apps Script editor explorer
- Script execution timeline
- Variable memory explorer
- Data type explorer
- Mathematical expression visualizer
- Conditional logic flowchart
- Loop execution animator
- Function input/output machine
- Array and object explorer
- Spreadsheet object hierarchy
- Cell and range selector
- A1 notation explorer
- Row and column coordinate visualizer
- Two-dimensional array explorer
- Spreadsheet read/write simulator
- Batch processing comparison
- Data transformation pipeline
- Spreadsheet formatting explorer
- Custom function playground
- Docs structure tree
- Template replacement visualizer
- Spreadsheet-to-document mapper
- Drive file tree
- File ID and metadata explorer
- File permission simulator
- Gmail thread explorer
- Gmail search query builder
- Personalized email merge
- Forms question builder
- Form response event inspector
- Calendar scheduling simulator
- Date and time zone explorer
- Slides structure explorer
- Spreadsheet-to-slides mapper
- Trigger behavior simulator
- Trigger execution timeline
- Event object inspector
- Automation workflow visualizer
- Custom menu designer
- Dialog and sidebar explorer
- Client-server architecture
- Asynchronous response timeline
- Web deployment explorer
- HTTP request and response inspector
- JSON structure explorer
- Authorization scope explorer
- Error handling and quota simulator
- Gemini structured output validator
- Human-reviewed intelligent workflow