侠Liangshen AIailiangshen.com
AI Implementation Course · Core lessons · Lesson 8

Let It Run on Its Own: Start with Semi-Automation, Then Decide on Full Automation

Start with Semi-Automation, Then Decide on Full Automation

Freeabout 60 minNo experience neededWeb lesson + slides + video

In previous lessons, we established workflows and created dedicated assistants. This lesson focuses on getting them to run independently. The key takeaway: default to semi-automation.

What this lesson covers

  • Opening
  • Concepts
  • AI in Office Suites
  • Demo: Building a Semi-Automated Workflow
  • Exercise A: Plan and Minimum Permissions Table
  • Exercise B: Run Through, Handle Breakpoints, Reconcile
  • Common Sticking Points and Incident Reporting
  • Weekly Inspections, Quizzes, and Assignments
  • Assignments and Wrap-up (Including Buffer Time)

Video version: about 14 min

Narration is AI-generated. The video plays on YouTube; the chapter buttons above jump to the matching places. You can skip the video and scroll down to read.
01

Opening

About 3 minutes

Scenario: Four Weekly TasksFictional Example, Numbers for Illustration

Yuanfan Technology · Administrative Specialist Lin Yue

After each Monday meeting, she performs four small tasks: locate the meeting notes, open the assistant, paste the notes, and copy the results into a document.

The four tasks are brief, but they require manual effort every week. When busy, she often delays them until the next day.

Today, we do not aim for full automation. Instead, we fix these four steps to ensure stable operation.

Fix first, automate later. Skipping steps is the most common cause of failure.
02

Concepts

About 7 minutes

Three Stages of Automation: Trigger, Processing, Action

1
TriggerWhen does it start? For example, set a calendar reminder.
2
ProcessWhat does the Dragon Warrior do, and which script version is used?
3
ActionWhere are the results stored? Prepare drafts in advance and send reminders.
Don't automate tasks with unclear start times. Steps that can be handled by fixed rules—such as saving by name or archiving by date—should not be assigned to AI.

Three-tier approach; default to Level 2.

Level 1: Manual fixed location

Records are stored in a fixed location. Manually open the assistant and save drafts. This is the baseline that anyone can perform.

Level 2: Semi-automatic (default)

Three fixed steps plus calendar reminders. Usually, no additional approval is needed; data remains compliant with company regulations.

Level 3: Fully automatic

The tool automatically detects triggers, invokes AI, and saves drafts. Requires company approval; this is an elective option.

Project success does not require Level 3. Writing Level 2 is fully acceptable.

Three principles for scheduled tasks

Principle 1: On which computer does it operate?

When you are not around, can it access the necessary materials?

Principle 2: Every waiting-for-confirmation step is a break point

The break point immediately before sending should always be left for human review.

Principle 3: Its claim of completion is not enough; check it yourself

Verify if the file exists and if the structure is complete. Cross-check by sampling two numbers.

Let it run automatically, but do not let it take charge. The boss remains at the door.
03

AI in Office Suites

About 4 minutes

First, check if your company's existing office suite includes AI

1
Look for it firstOpen your commonly used documents, spreadsheets, or emails, and look for buttons labeled 'AI' or 'Assistant'.
2
Not foundIt might not be enabled or included in your version. Check with the IT department first.
3
Try it firstUse a sanitized, low-priority document for testing
Benefit: Data typically stays within the company's approved environment, so no additional accounts are needed. Note: Built-in AI suites usually don't include your personal files, so you'll need to manually add some lists and templates.
04

Demo: Building a Semi-Automated Workflow

About 15 minutes

Step 1: Write the plan in one sentence

1
TriggerFifteen minutes after the weekly Monday meeting, a calendar reminder titled 'Meeting Minutes Time' will appear. This is a rule-based reminder and does not require AI.
2
ProcessSave the sanitized records into the 'Weekly Meeting Records' folder, open the fixed entry point, and organize them according to Script v1.
3
ActionSave the result to 'Meeting Minutes Draft' and do not send it to any colleagues.
4
GatekeepingLin Yue verifies the responsible person and deadlines, then sends it out herself after confirmation.

Industry version: Batch processing of work orders, same structureFictional Example, Numbers for Illustration

Trigger and Process (Luo Xiaotang)

  • Calendar reminders for 'Work Order Batch Processing' appear daily at 10:00 AM and 3:00 PM.
  • New work orders are sanitized and sent to the Work Order Assistant: categorize, match entries, and draft replies, indicating whether to escalate to a human agent.
  • Replies must cite entry numbers; if not found, write 'Escalate to human agent.'

Action and Gatekeeping

  • Save results to the 'Reply Drafts' area, one work order per entry.
  • Do not reply directly in the work order system or change the work order status.
  • Refunds, compensation, service commitments, security incidents, and suspected major failures are all escalated to human agents.
The structure is the same: What is received, what is done, where it is stored, and who handles gatekeeping.

Step 2: Use three 'fixed' elements to stabilize semi-automation

Where to store records

A fixed folder, such as 'Weekly Meeting Records'

Where do I open the assistant?

A fixed entry point; always start from the same place.

Where are drafts saved?

A fixed draft location, such as 'Meeting Notes Draft'.

If a task can be handled by calendar reminders or folder naming, don't hand it over to the AI.

Step 3: Minimum permission table, start with the least.

Principle: Grant the minimum first; add more only if necessary. For each addition, write down the reason. Do not grant access to the colleague contact list, as the list is already in the dossier.

Step 4: Apply to the IT department and keep a record of approval.

1
Specify locations and permissions.Granted locations are read-only; granted write locations are for creating new files only; explicitly state permissions that are not needed.
2
How is data handled?First, anonymize data according to company regulations; exclude passwords and contract text.
3
Duration and responsible personStart with a two-week trial. If issues arise, disable it immediately and report to the IT department.
One-sentence rule: Do not enable automatic execution without written or archivable confirmation. For verbal responses, send a follow-up message on the same day to confirm. If approval is not obtained, the project remains at Level 2, which is fully acceptable.

On-site acceptance: Observe reality first, then ask follow-up questions.Interface demonstration · Fictional dialogue

Preset Draft A (intentionally omits one item)
1. This week's conclusion: New employee onboarding materials will uniformly use the new checklist starting next week. 2. To-do: 1. Update onboarding materials checklist | Xu Jing | Before Wednesday; 2. Complete contact information for client data forms | Zhou Kai | Before Friday. 3. To be confirmed: Schedule adjustments, under discussion, undecided.
Follow-up questions
There are only two items on the to-do list, but the log shows three tasks that need to be done. Why wasn't Chen Wei's task included? What constraints in your rules cause you to skip a record? Please list them all.
The old template in the archive states: Items without a clear deadline are not added to the to-do list.
It didn't make a mistake; we just failed to notice this old rule. Find it, update the rule file, and don't just patch this single instance.

After updating the rules, review Draft B.Pre-set result (run before class)

Draft A

  • Two items on the to-do list; Chen Wei's task is missing.
  • The old rule in the archive: Items without a clear deadline are not added to the to-do list.

Draft B (after updating rules)

  • Three items on the to-do list; Chen Wei's task is now included.
  • Items without a deadline are added to the to-do list, with the deadline marked as 'To Be Confirmed'.
We update the rule file, not just patch this single instance.

On-site re-run: Change one condition, time it, and correct deviations mid-process.

1
Change one condition.Change the record source from 'This Week's Folder' to 'This Week Plus Last Week's Carryovers'. Run this only once to see if other areas are affected.
2
Live timing broadcast.From this point on, do not edit out waits or errors. Report the total time after completion.
3
Mid-process stop and correction.If the result needs to be pasted directly into the conversation, stop, add the instruction 'Save to the Meeting Notes Draft Folder', and then continue.
Honest conclusion: First check reality. Are the files there? Are all four components present? Pick two dates to cross-check against the original records, then see what the tool says. If the on-site re-run fails, switch to the pre-set Draft B and state this clearly.

Breakpoint: Choose one of three options: A (Release), B (Write into rules), or C (Leave for humans).

1
A: ReleaseConfirm within the minimum necessary permissions, such as whether reading this folder is allowed. Release it within the scope of the permission table and log it in the release record.
2
B: Write into rulesUncertain edge cases, such as duplicate files. Select a default action and add it to the 'Requires My Decision' list.
3
Type C: Intentionally reserved for human judgment.Irreversible actions: sending, deleting, or modifying someone else's data. These always require human approval.
Lin Yue encountered three breakpoints this time: read confirmation defaults to Type A, duplicate files default to Type B (keep the latest version and add to the list), and send confirmation defaults to Type C.
05

Exercise A: Plan and Minimum Permissions Table

About 7 minutes

Exercise A: Draft your own plan

Automation Level

Level 1, 2, or 3; default is Level 2

Trigger, Processing, Action

When it starts, which assistant handles it, and where the result is stored

Gatekeeping and Permission Table

Who verifies what and when; what is denied and why

Release and Error Handling Procedures

Who responds and when; how to handle empty inputs, duplicates, or failures; weekly inspections

Choose one: Your own task; Lin Yue's meeting notes assistant; or an industry-specific version for ticket classification or alert aggregation.

Plan Review Criteria

Common pitfalls: Pursuing full automation from the start without clarifying triggers; granting 'Send' permissions for convenience with the excuse 'I'll check anyway'; or offloading steps that could be handled by rules to the AI.
06

Exercise B: Run Through, Handle Breakpoints, Reconcile

About 10 minutes

Classroom Task 1: Run a normal input and fill in Row 1 of the reconciliation table simultaneously.

1
Store in a fixed locationPlace a past record into a designated folder, open the fixed entry point, paste it, and let the assistant process it.
2
Fill out the reconciliation table while waitingFirst, fill in the source, expected trigger, and actual trigger. If the run fails, directly use the preset run record instead of waiting indefinitely.

The second classroom task: Use the preset run record to handle breakpoints.

A fictional meeting record.

Used for comparison.

Two assistant drafts.

One is normal, and one intentionally omits one to-do item.

A reconciliation sheet with the first row already filled.

For reference.

One run history.

The tool tip indicates a save failure, but the file has actually been saved to the draft location.

Handle breakpoints and complete the first row of the reconciliation sheet.

First check reality, then check what it says. Record false positives in both directions: saying it's complete when it hasn't been generated, and saying it failed when it has already been saved.

How to fill out the run record reconciliation sheet.

1
Is the structure complete?The minutes have four sections: conclusions, to-dos, items to confirm, and next steps. Are they all present?
2
Extract two numbers for reconciliation.Pick two numbers or dates from the original record, find them in the output, and consider it a pass only if they match.
3
Write the two columns separately.What the tool says itself and what is seen in reality are two columns; inconsistency between them is a false positive.
Lin Yue's first reconciliation: extracted two dates, one was correct, and one wrote 'Friday' as 'Thursday', recorded as one manual correction. After class, supplement with at least three normal cases and one intentional error.
07

Common Sticking Points and Incident Reporting

About 4 minutes

Common Bottlenecks and Fallbacks

Cannot locate the file

Switch to semi-automatic: Place the file in a fixed location accessible to the tool, or paste it manually

Require approval for every step

Handle one by one using the 'choose three' method; if it still fails, revert to the secondary level

Reconciliation reveals a missing entry

Do not just add that single entry. Investigate which constraints caused it to be skipped, and update the rules file

Permissions revoked, or tool version updated

Revert to manual processing and log the action. Re-initiate the approval process. After the update, run three test cycles

Do not bypass the approval process. The fallback is always to revert to the previous level.

In case of an incident, report using three sentences

1
1. What happenedTime, which process, what phenomenon
2
2. What data is involvedCategory, approximate number of records, whether it contains restricted data
3
3. What actions have been takenWhat has been disabled, who has been notified, who is expected to respond next
Fixed sequence: Disable first, then report, then review. Data classification and external notifications must comply with company policies, information security regulations, and legal department guidelines.
08

Weekly Inspections, Quizzes, and Assignments

About 5 minutes

Weekly inspection: ten minutes, fixed schedule

If all checks pass for three consecutive weeks, you may reduce the frequency to once every two weeks, but do not cancel it.

Three quick questions to check yourself

Question 1: Which of the following statements is correct?

Answer B.The three fixed steps in semi-automation save most of the time spent searching; full automation requires prior approval.

Question 2: When the tooltip displays 'Save Failed,' what should you do first?

Answer B.The message might say 'Failed' when the file is actually saved, or 'Completed' when it isn't. Check the actual status first, then look at what the message says.
09

Assignments and Wrap-up (Including Buffer Time)

About 5 minutes

Assignment and Project Card: Column 9

1
Finalize the Automation PlanUse the template from Exercise A to specify the automation level
2
Submit a request to the IT DepartmentRecord the approval status; if no response is received, remain at Level 2 and note this.
3
Complete the Reconciliation TableInclude at least three normal runs and one intentional error; select one option for each breakpoint
4
Set up weekly inspectionsPerform the first inspection and record the results
Optional: Complete the full automation (requires approval) and internal tools from the appendix after the course.
Show the full transcript (video narration)
Let It Run on Its Own

Welcome to Lesson 8 of the AI Implementation Course. In previous lessons, we established workflows and created dedicated assistants. This lesson focuses on getting them to run independently. The key takeaway: default to semi-automation. Full automation is an optional step requiring company approval.

Scenario: Four Weekly Tasks

Here is the scenario. Lin Yue's meeting notes assistant is ready, but after each Monday meeting, she still performs four small tasks: locate the meeting notes, open the assistant, paste the notes, and copy the results into a document. These tasks are brief but require manual effort every week. When busy, she often delays them until the next day. Today, we do not aim for full automation. Instead, we fix these four steps to ensure stable operation.

Three Stages of Automation: Trigger, Processing, Action

Automation consists of three stages: Trigger (when it starts), Process (what the Dragon Warrior does), and Action (where the results go). Don't automate tasks with unclear start times. Steps that can be handled by fixed rules—such as saving by name, archiving by date, or sending timely reminders—should use rules, not AI. AI is only used for steps requiring content understanding.

Three-tier approach; default to Level 2.

Three-tier approach; default to Level 2. Level 1 is manual fixed location, which anyone can perform and serves as the baseline. Level 2 is semi-automatic, involving three fixed steps plus calendar reminders; only this level is covered in class. Level 3 is fully automatic, where the tool detects triggers, invokes AI, and saves drafts; it requires company approval and is an elective option. Project success does not require Level 3; writing Level 2 on the project card is fully acceptable.

Three principles for scheduled tasks

Scheduled tasks must pass three checks. Principle 1: On which computer does it operate? When you are not around, can it access the necessary materials? Principle 2: Every waiting-for-confirmation step is a break point. Break down what can be broken; the break point immediately before sending should always be left for human review. Principle 3: Its claim of completion is not enough; check it yourself: Verify if the file exists and if the structure is complete. Cross-check by sampling two numbers. Let it run automatically, but do not let it take charge. The boss remains at the door.

First, check if your company's existing office suite includes AI

Many companies already have office suites with built-in AI features. For example, Copilot in Microsoft 365, Gemini in Google Workspace, or AI features in WPS. Names and features are for illustration only and may change. Check what your company already provides before deciding whether to look for additional tools. How to find it: Open your usual documents, spreadsheets, or emails and look for an AI or assistant button; if not found, ask the IT department; once found, test it with a sanitized, low-priority document.

Step 1: Write the plan in one sentence

Demonstration begins. Step 1: Write the plan in one sentence using the format: What is received, what is assigned to Dragon Warrior to do, and where the result is stored. Lin Yue's plan is: Trigger, fifteen minutes after the weekly Monday meeting, a calendar reminder for 'Meeting Minutes Time,' which is a rule-based reminder and does not use AI. Process, save the sanitized records into a fixed folder, open the fixed entry point, and organize them according to Script v1. Action, save the result to 'Meeting Minutes Draft' and do not send it to any colleagues. Gatekeeping, Lin Yue verifies the responsible person and deadlines, then sends it out herself after confirmation.

Industry version: Batch processing of work orders, same structure

The industry example features Luo Xiaotang from Qilan Intelligence, a fictional character. Her trigger is the daily calendar reminders at 10:00 AM and 3:00 PM. The process involves sanitizing a batch of new work orders and sending them to the Work Order Assistant to categorize, match knowledge base entries, and draft initial replies. The action is saving them to the 'Reply Drafts' area without replying directly to customers or changing work order status. Gatekeeping ensures that refunds, compensation, service commitments, security incidents, and suspected major failures are all escalated to human agents. The structure is identical to Lin Yue's plan.

Step 2: Use three 'fixed' elements to stabilize semi-automation

Step 2: Stabilize semi-automation with three fixed elements. Where records are stored: a fixed folder. Where to open the assistant: a fixed entry point. Where drafts are saved: a fixed draft location. These three fixes save most of the time spent searching and provide a place for later reconciliation. If a task can be handled by fixed rules like calendar reminders or folder naming, don't hand it over to the AI.

Step 3: Minimum permission table, start with the least.

Step 3: Write the minimum permission table. Clearly state for each item whether it is granted and why. Read records folder: Granted. Create draft file: Granted. Entire shared drive: Denied, irrelevant to this task. Send emails: Denied, only draft. Delete any file: Denied, errors are irreversible. The principle is: grant the minimum first; add more only if necessary, and write down the reason for each addition.

Step 4: Apply to the IT department and keep a record of approval.

Step 4: Apply to the IT department and keep a record of approval. Whenever folder reading/writing, email, or third-party tools are involved, you must obtain approval. The application should clearly specify: locations to read, locations to write, permissions not needed, how data is handled, duration, and the responsible person. One-sentence rule: Do not enable automatic execution without written or archivable confirmation. If approval is not obtained, this project remains at Level 2, which is fully acceptable.

On-site acceptance: Observe reality first, then ask follow-up questions.

On-site verification. Open the draft and count: there are only two items on the to-do list, but the log shows three tasks. Don't rush to add the missing one. First, ask: Why wasn't Chen Wei's task included? What constraints in your rules cause you to skip a record? It answers: The old template in the archive states that items without a clear deadline are not added to the to-do list. It didn't make a mistake; we just failed to notice this old rule. Find it, update the rule file, and don't just patch this single instance.

After updating the rules, review Draft B.

After updating the rules, the pre-set Draft B is generated. There are three items on the to-do list, Chen Wei's task is included, and the deadline is set to 'To Be Confirmed' rather than guessed as a specific day. This way, every subsequent run benefits, rather than just fixing this one instance.

On-site re-run: Change one condition, time it, and correct deviations mid-process.

There is only one on-site re-run, with no editing. I change only one condition: the record source is changed from 'This Week's Folder' to 'This Week Plus Last Week's Carryovers'. Timing starts, and waits or errors are not edited out. The total time is reported after completion. Mid-process, if I find that the result needs to be pasted directly into the conversation, I stop, add the instruction 'Save to the Meeting Notes Draft Folder', and then continue. After the re-run, I first check reality: Are the files there? Are all four components present? I pick two dates to cross-check against the original records, then see what the tool says. For any step that differs from expectations, I honestly state where it differs from the pre-class setup.

Breakpoint: Choose one of three options: A (Release), B (Write into rules), or C (Leave for humans).

Every pause for confirmation during a trial run is a breakpoint; handle each with a Type A, B, or C choice. Type A: Release with minimal permission and log it in the release record. Type B: Codify it into rules; for uncertain edge cases, select a default action and add it to the 'Requires My Decision' list. Type C: Intentionally reserve it for humans; irreversible actions like sending, deleting, or paying always require human approval. Lin Yue encountered three breakpoints this time: read confirmation defaults to Type A, duplicate files default to Type B, and send confirmation defaults to Type C.

Exercise A: Draft your own plan

Exercise A: Draft your semi-automated plan and minimal permission table. Choose one: Your own task (prioritize those with trial run records); Lin Yue's meeting notes assistant (can be rewritten with a different trigger); or an industry-specific version for ticket classification or Hong Zhiyuan's alert aggregation (write a separate error handling procedure). The plan must specify the automation level, trigger, processing, action, gatekeeping, permission table, release record, error handling, and inspection schedule.

Plan Review Criteria

Review the plan against the four criteria. The plan must be clearly describable in one sentence. The minimal permission table must include at least three 'Deny' entries, including 'Send.' The automation level is specified; full automation is not mandatory. There is a release record, or it explicitly states 'Not yet released, paused at Level 2.' Common pitfalls include pursuing full automation from the start, granting 'Send' permissions, or offloading rule-based steps to the AI.

Classroom Task 1: Run a normal input and fill in Row 1 of the reconciliation table simultaneously.

Exercise B is divided into two parts. The first classroom task involves placing a past record into a fixed location, opening a fixed entry point, pasting it, and letting the assistant process it, then saving it to a fixed draft location. While waiting, fill in the first few columns of the first row of the reconciliation sheet: Source, Expected Trigger, and Actual Trigger. If the output doesn't generate, directly use the preset run record instead of waiting. The remaining runs and the complete reconciliation are left for after class.

The second classroom task: Use the preset run record to handle breakpoints.

For the second classroom task, use the preset run record. It contains a fictional meeting record, two assistant drafts (one normal, one intentionally omitting a to-do item), a reconciliation sheet with the first row filled, and one run history: the tool tip indicates a save failure, but the file is actually in the draft location. First, check reality: how many files are in the draft location, and does what the tool says match reality?

Handle breakpoints and complete the first row of the reconciliation sheet.

Handle breakpoints and complete the first row. First check reality: how many files are in the draft location. For the draft that missed one item, ask about the constraints, find them, and update the rules, not the single result. For each place in the trial run that waits for confirmation, choose one of three options and write it in the last column of the reconciliation sheet. Then complete your own first row. Remember the false positives in both directions: saying it's complete when it hasn't been generated, and saying it failed when it has already been saved. So the order is always: first check reality, then check what it says.

How to fill out the run record reconciliation sheet.

How to fill out the reconciliation sheet. Is the structure complete, and are all four sections of the minutes present? Extract two numbers for reconciliation: pick two numbers or dates from the original record, find them in the output, and consider it a pass only if they match. What the tool says itself and what is seen in reality must be written in separate columns. Lin Yue's first reconciliation: extracted two dates, one was correct, and one wrote 'Friday' as 'Thursday', recorded as one manual correction. After class, supplement with at least three normal cases and one intentional error.

Common Bottlenecks and Fallbacks

Common bottlenecks and fallbacks. If you cannot locate the file, switch to semi-automatic. Require approval for every step, handle one by one using the 'choose three' method, and if it still fails, revert to the secondary level. If reconciliation reveals a missing entry, do not just add that single entry; investigate the constraints in the rules. If permissions are revoked or the tool is updated, revert to manual processing and log the action, re-initiate the approval process, and run three test cycles after the update. Do not bypass the approval process; the fallback is always to revert to the previous level.

In case of an incident, report using three sentences

If an incident occurs, such as a draft being sent by mistake or unauthorized data entering the tool, perform only three actions in a fixed sequence: disable, report, and review. The report requires only three sentences: what happened, what data is involved, and what actions have been taken. Data classification and external notifications must comply with company policies, information security regulations, and legal department guidelines; do not make these decisions independently.

Weekly inspection: ten minutes, fixed schedule

The greatest risk of automation is silent failure: triggers not starting, triggers running without output, or output going unnoticed. Therefore, perform a fixed ten-minute weekly inspection. Check trigger counts, output locations, failure and idle run records, unauthorized or out-of-scope content, reconcile two random numbers with original records, and verify if permissions remain minimal. If all checks pass for three consecutive weeks, you may reduce the frequency to once every two weeks, but do not cancel it.

Quiz Question 1

Question 1. Which of the following statements is correct? The options are: For a project to be considered successful, it must be fully automated; The default approach is semi-automation; full automation is an optional upgrade requiring company approval; Semi-automation is not considered true automation. The answer is B. The three fixed steps in semi-automation save most of the time spent searching; for full automation, you must first obtain approval.

Quiz Question 2

Question 2. When the tooltip displays 'Save Failed,' what should you do first? The options are: Run it again immediately; Open the draft location first to check if the file is already there; Trust it and assume nothing was done. The answer is B. The message might say 'Failed' when the file is actually saved, or 'Completed' when it isn't. Check the actual status first, then look at what the message says.

Assignment and Project Card: Column 9

Assignment. Finalize your own automation plan and specify the automation level. Submit a request to the IT Department, record the approval status, and if no response is received, remain at Level 2 and note this. Complete the Reconciliation Table with at least three normal runs plus one intentional error, selecting one option for each breakpoint. Set up a weekly inspection reminder and perform the first inspection. These are the contents for Column 9 of the Project Card.

Next Lesson: Measuring Results

Next lesson: Measure results. Using your pilot data, we will calculate time saved, quality changes, and costs to create a cost-benefit analysis. Please bring your pilot records and use the same acceptance checklist to review several past manual outputs beforehand. This will serve as your manual baseline.