Questions
These are the questions we hear on the enquiry call. If your case is odd, write anyway. A short honest note is easier to answer than a long form that hides the constraint.
Foundations is written for that starting point. Night one assumes you can use a laptop and name a repeating task, nothing more. We open the tool together and we refuse the first answer on purpose so you can see a check. People who have only tried a chatbot at home usually belong here. If you cannot name a file you are allowed to practise on, write to us first and we will help you pick a stand-in before the Tuesday starts.
No. The joining notes list any free accounts that help, and we run the teaching segment on the shared screen so you can follow without a paid seat. If your employer already pays for a tool, bring that login. If a paid feature is the only way to finish a later step, we will say so in week one and offer a stand-in path. Tool licences are not included in the course fee.
Bring a file you are allowed to work on. Do not bring identity documents, health records, unreleased financials, full customer lists, or anything your employer has marked restricted. We teach redaction and synthetic stand-ins on night one. If you are unsure, treat the file as restricted and ask before the lab. We will stop a share that looks wrong. Lab time is not recorded.
Yes, we issue a certificate of attendance that names the course, the dates and Learnaieasily. It is a record that you were in the room. It is not a professional licence, not a ministry award, and not a claim that you are an expert. The document we care about is the workflow you take back to your desk. If an employer asks what you can do, show them that.
A laptop you can type on for two and a half hours, a current browser, and a charger. Windows, macOS or a Chromebook that can open ordinary office files will do. Install nothing exotic before you arrive. The joining notes name the current tools for your intake. Phones are a poor substitute because the lab needs two windows open. Tablets can work if you have a keyboard and can edit a real document.
Yes, within limits. The teaching segment is recorded and stays available for 30 days. Lab time is not recorded. Watch the teaching recording before the next night and bring the homework so we can use the recap on you. Missing two sessions on a four-week course usually means you should transfer to the next intake. Write to us as soon as you know.
Only the teaching segment. The 35-minute demonstration is recorded so you can replay the clicks. The lab and the group review are not recorded, because your files are on the desks and other people are speaking about their work. Recordings are for enrolled learners, for 30 days, and they are not for posting. We will not send a recording to a colleague who is not on the course.
Yes. Say in the enquiry that the seat is sponsored. We will send the invoice to the finance contact you name and we will complete reasonable sponsorship forms that ask for course title, dates, hours and fee. We do not complete forms that ask us to invent a registry code or a tax identifier we do not publish. Payment terms sit on the invoice. The seat is confirmed when payment instructions are met.
It is often more relevant. A restriction is a design constraint we can teach inside. Tell us what is allowed. We will teach on permitted tools or on stand-in files, and the one-page rule you write at the end will match the policy you already have. If the policy bans every tool we can teach, we will say the course is a poor fit rather than take the fee.
The workbook is reviewed before every 2026 intake. If a step broke because a product changed, the pages are rewritten and recent cohorts on that track are sent the update. We do not freeze a January screenshot and keep selling it in October. You will see the current tool list in the joining notes, not as a permanent promise on the public pages.
We advise against stacking two evening courses in the same month. Each week already asks for 60 to 90 minutes of homework on a live file. Foundations plus Prompting in the same block usually means both files get a thin pass. Take one, finish the workflow, then join the next intake. Automation is only offered after Foundations or Prompting, or after we have seen equivalent daily use.
No. The public programmes are for people who need to run a workplace job with current tools. People who want to become engineers should look for a different school. You will not be asked to write Python or to fine-tune a model. Spreadsheet formulae you already understand are welcome. If your aim is software engineering, this is the wrong school and we will tell you so.
Still choosing
If the answers above still leave the month empty, write two sentences: the weekly file you want to bring, and whether a model has already touched that file at work. That pair is enough for us to point at Foundations, Prompting, Data or a later Automation intake. We would rather send you to a later month than fill a seat that will stall in week two.
Send the role, the weekly task and any tool rule your employer already has. We reply within one working day.