Unit 2 Review Video Script
Cold Open
ON SLIDE | NARRATION
Unit 2 review; find the right process; map the workflow; define the automation; prioritize the best ideas | Before you build any automation, you need to know where it will help most. In this unit, you looked at real work, mapped the steps, and turned ideas into clear automation plans.

2a
ON SLIDE | NARRATION
Analyze work processes; repetitive tasks; error-prone tasks; high-impact tasks; automation opportunities | You first learned to analyze work processes and spot the best automation targets [2.1 Spotting Repetitive Tasks in Your Work]. Look for tasks that repeat often, take time, or lead to errors. Focus on work that is repetitive, error-prone, and high-impact, because those are the tasks that can benefit most from automation [2.1 Spotting Repetitive Tasks in Your Work].

To review, see: [2.1 Spotting Repetitive Tasks in Your Work]
2b
ON SLIDE | NARRATION
Process maps; current workflow state; future workflow state; workflow steps; automation plan | You also learned how to create process maps [2.2 Creating Visual Process Maps]. A process map shows the current workflow state, so you can see each step as it happens now. It can also show the future workflow state, so you can plan how the process will work after automation [2.2 Creating Visual Process Maps].

To review, see: [2.2 Creating Visual Process Maps]
2c
ON SLIDE | NARRATION
Trigger; action; condition; data requirements; automation design | Next, you practiced defining the parts of an automation [2.3 Defining Triggers, Actions, and Conditions]. A trigger starts the automation. An action is what the automation does. A condition sets the rule for when the automation should run. You also need the right data, because automations depend on clear inputs and information [2.3 Defining Triggers, Actions, and Conditions].

To review, see: [2.3 Defining Triggers, Actions, and Conditions]
2d
ON SLIDE | NARRATION
Prioritize automation ideas; impact; effort; feasibility; choose the best idea | Finally, you learned how to prioritize automation ideas [2.4 Prioritizing Automation Ideas]. Use impact, effort, and feasibility to compare your options. High-impact ideas can save more time or reduce more errors. Lower-effort ideas can be easier to start. Feasibility helps you check whether the idea is realistic with the tools and data you have [2.4 Prioritizing Automation Ideas].

To review, see: [2.4 Prioritizing Automation Ideas]
Close
ON SLIDE | NARRATION
Review the unit resources; practice analyzing, mapping, defining, and prioritizing; build stronger automation plans | You now have a practical method for finding good automation opportunities and shaping them into clear plans. Review the readings and videos again if you want more practice, and use the unit resources to strengthen each step.

Last modified: Thursday, 18 June 2026, 1:28 PM
Callback before_footer in local_aigrade component should be migrated to new hook callback for core\hook\output\before_footer_html_generation
  • line 7225 of /lib/moodlelib.php: call to debugging()
  • line 7292 of /lib/moodlelib.php: call to {closure}()
  • line 71 of /lib/classes/hook/output/before_footer_html_generation.php: call to get_plugins_with_function()
  • line 987 of /lib/classes/output/core_renderer.php: call to core\hook\output\before_footer_html_generation->process_legacy_callbacks()
  • line 94 of /mod/page/view.php: call to core\output\core_renderer->footer()