TECHNOLOGY · 2.5 HOURS
No-Code Automation for Everyday Work
No-Code Automation for Everyday Work teaches administrators, coordinators and team leads to build one small automation for a repeating task in a tool they already have. You finish with a tested automation and a signed automation note that records what it does, how you will know it has stopped, and how to switch it off.
About this course
No-code automation means setting up a tool your organisation already licenses, such as Microsoft Power Automate, Zapier, Make or the rules in Outlook, to carry out a set of steps whenever a particular event happens, without writing any code. It can take repetitive copying, filing and notifying off a person's week, but only if the task is described precisely and the steps that need human judgement stay with a person. This course teaches you to decide what is safe to automate and to build one small automation that holds up in real use.
The course works on one repeating task of your own, from separating rule steps from judgement steps, through a written description and a careful choice of tool and access, to testing on real cases and planning for failure. You finish with a tested automation and a signed automation note that sets out its description, its access, its test log and a failure note a colleague can use while you are away.
What you will take away
- You will be able to mark each step of a task as a rule a tool can follow or a judgement a person makes, and plan the automation around the judgement.
- You will be able to write a description with one trigger, steps that name exact places and fields, and conditions that handle awkward cases, so a colleague could build from it without asking.
- You will be able to choose the simplest approved tool that does every step, and mark each permission a connector requests as needed or not needed.
- You will be able to test an automation on a normal case, a missing field, a duplicate and an unusual case, and record what was handled wrongly and what you changed.
- You will leave with a signed automation note covering the description, the access, an honest test log, and a failure note that says how someone will notice it has stopped and how to switch it off.
Who this course is for
- Administrators who spend part of every week copying details from forms and emails into trackers, folders and calendars.
- Coordinators who handle requests that follow the same steps each time, such as training bookings, invoices or volunteer sign-ups.
- Team leads who want a colleague's automation to be understood, tested and looked after rather than tied to one person's login.
- Staff who have access to an approved automation tool but no coding background and want to use it without creating risk for their organisation.
What you will do
Each lesson teaches one part of the method, works through a realistic example, and ends with a check on a case you have not seen. The course closes with an assessment and then the piece of work you sign.
- 5lessons with a worked example and a check
- 8scenario questions in the course assessment
- Signedthe automation note, with a record anyone can verify
- 2.5 hoursat your own pace, with progress saved
- 01
Lesson
Rule or judgement
This lesson explains what an automation actually does and gives you a test for telling a rule a tool can follow from a judgement a person must make. You mark each step of real tasks and plan to automate the rule steps around the judgement.
- What an automation actually does
- Two labels for every step
- What automation is not
- Automate around the judgement
You mark 4 statements from a realistic case and receive an explanation for each one.
- 02
Lesson
Trigger, steps and conditions
This lesson shows you how to describe an automation as a single trigger, ordered steps that name exact places, and conditions that handle awkward cases. You compare descriptions and choose the one that is ready to build without further questions.
- Three parts of every automation
- The trigger is one event
- Each step names a place
- Conditions change what happens
- Ready to build, or needs more detail
You compare two versions of the same piece of work, choose the stronger one, and see the reasoning behind the answer.
- 03
Lesson
A no-code path
This lesson covers choosing the simplest tool your organisation already allows and the account the automation runs under, which is the part people most often skip. You read the permissions a connector requests and mark each one as needed or not needed.
- Start with what your organisation already allows
- The simplest path that works
- Every automation runs as someone
- Access it needs and access it does not need
You mark 4 statements from a realistic case and receive an explanation for each one.
- 04
Lesson
Run it on real cases
This lesson explains the difference between a demonstration and a test, and how to run an automation on four kinds of real case before anyone relies on it. You read test results and mark each as handled correctly or handled wrongly.
- A demonstration is not a test
- Four kinds of case
- Quiet failures
- Recording what happened
You mark 4 statements from a realistic case and receive an explanation for each one.
- 05
Lesson
When it breaks
This lesson explains the ordinary reasons automations stop working and sets out the five parts of a failure note, including a check a person can make without the tool. You repair a weak failure note so a colleague could act on it.
- Automations break for ordinary reasons
- The five parts of a failure note
- How we know it stopped
- Owner, cover, by hand, and off
You repair a flawed draft so it meets the standard the lesson sets, and your revision is checked against it.
- 06
Course assessment
The whole method, on new cases
This course assessment brings the five moves together, shows the typical mistake at each one, and reviews a colleague's volunteer sign-up flow step by step. You then apply the method to eight new situations, each with a real document or decision.
- The method in one place
- Where people usually go wrong
- How the assessment works
You judge 8 new workplace situations, with feedback on every option, and need 6 correct to pass.
- 07
Final work and signed record
Your automation note
In this final lesson you write the automation note for a real automation you have built and tested, in four sections that bring together every earlier lesson. Each section is checked for substance before you sign it for your record.
- What the automation note is
- The four sections
- An honest test log
- How the note is checked
You write the automation note for your own work, part by part, and sign it as your record.
GOOD WORK.THE AUTOMATION NOTE, SIGNED.
WHAT CHANGES
What the course changes for you and your organisation.
- 01
Decisions stay with people
The course teaches you to keep judgement steps, such as approving a request or deciding whether a course is suitable, in human hands while the tool gathers and routes the information. The organisation avoids confirmations and approvals that nobody actually decided.
- 02
Access your IT team can accept
You learn to build with tools your organisation already allows and to grant only the access the steps use, preferably under an account that exists for the work. That makes the automation easier to approve and less likely to be switched off when someone notices it.
- 03
Work continues when it breaks
Your failure note names an owner and cover, a check a person can do without opening the tool, the manual route, and how to switch it off. When a password changes or a folder moves, the work carries on and the problem is found quickly.
- 04
Automation built outside IT
Gartner predicts that by 2026 at least 80% of low-code tool users will sit outside formal IT departments. Staff who can build, test and safely switch off a small automation give employers a practical way to reduce repetitive manual work.
QUESTIONS
Questions about No-Code Automation for Everyday Work
- What is No-Code Automation for Everyday Work about?
- No-code automation means setting up a tool your organisation already licenses, such as Microsoft Power Automate, Zapier, Make or the rules in Outlook, to carry out a set of steps whenever a particular event happens, without writing any code. It can take repetitive copying, filing and notifying off a person's week, but only if the task is described precisely and the steps that need human judgement stay with a person. This course teaches you to decide what is safe to automate and to build one small automation that holds up in real use. The course works on one repeating task of your own, from separating rule steps from judgement steps, through a written description and a careful choice of tool and access, to testing on real cases and planning for failure. You finish with a tested automation and a signed automation note that sets out its description, its access, its test log and a failure note a colleague can use while you are away.
- Who is No-Code Automation for Everyday Work for?
- Administrators who spend part of every week copying details from forms and emails into trackers, folders and calendars. Coordinators who handle requests that follow the same steps each time, such as training bookings, invoices or volunteer sign-ups. Team leads who want a colleague's automation to be understood, tested and looked after rather than tied to one person's login. Staff who have access to an approved automation tool but no coding background and want to use it without creating risk for their organisation. No specialist background is assumed, and every term is explained before it is used.
- What will I be able to do after No-Code Automation for Everyday Work?
- You will be able to mark each step of a task as a rule a tool can follow or a judgement a person makes, and plan the automation around the judgement. You will be able to write a description with one trigger, steps that name exact places and fields, and conditions that handle awkward cases, so a colleague could build from it without asking. You will be able to choose the simplest approved tool that does every step, and mark each permission a connector requests as needed or not needed. You will be able to test an automation on a normal case, a missing field, a duplicate and an unusual case, and record what was handled wrongly and what you changed. You will leave with a signed automation note covering the description, the access, an honest test log, and a failure note that says how someone will notice it has stopped and how to switch it off.
- How long does the course take, and how is it taught?
- The course takes about 2.5 hours and is studied online at your own pace. It has 5 lessons, each with a worked example, a practice exercise, and a check on a new case, followed by a course assessment of 8 scenario questions in which you need 6 correct to pass. Your progress is saved to your account.
- Do I get a certificate?
- Yes. When you pass, you sign a record that names you, the course, and the automation note. Anyone you share it with can verify it online and download it as a PDF. The record confirms what you completed and does not claim compliance with any regulation.
- How much does it cost, and when can I start?
- The course costs £99, paid once by card through Stripe. Access begins as soon as payment is confirmed, and you can save a sign-in to return to the course from any device.
- Can my organisation train a whole team?
- Yes. Individuals can buy any self-paced course online, and organisations can book trainer-led courses for teams, in person or online, through the Experrt Academy.
More technology courses are listed on the self-paced technology courses for non-technical teams page.
THERE IS A NEXT CHAPTER.
Start today, and finish with
the automation note your organisation can use.
Checkout takes an email address and a card, and access begins as soon as payment is confirmed. When you finish, you sign a record that names you and the automation note, which anyone you choose can verify online. The record confirms what you completed and does not claim compliance with any regulation.