Automated Moodle Course Readiness Checks
Every Monday, WebRun opens Moodle, goes through the courses due to run, checks visibility, section content, assignment due dates, and enrolment methods on each, posts a per-course setup report to Slack, and drafts an email in Gmail to the teacher of every course with something missing.
How do I check every Moodle course is set up before term starts?
WebRun opens Moodle every Monday and checks the courses due to run: whether each is visible, whether any section is empty, whether assignment due dates still point at last term, and whether enrolment is open. It posts a per-course readiness report to Slack and drafts a fix email per teacher in Gmail.
- Students never open a course with no visible content
- Due dates from last term are caught before the first week
- The not-ready count falls every week instead of surfacing on day one
Built for course coordinators · learning technologists · school and university admins · training managers
What does WebRun do on every run?
The exact actions WebRun takes, in order - in plain language, so you can adjust anything.
-
WebRun signs in and gets to work
Opens
moodle.orgin a real browser with your saved login - no setup, no API keys. -
1
Moodle - check setup on every course
WebRun opens Moodle to check setup on every course. - Open Moodle and list the courses due to run this term
- Check each course is visible to students rather than hidden
- Look for sections with no activities or resources in them
- Read the assignment due dates and flag any still set to last term's values, then check the enrolment methods are open to the right cohort
Done when Every course has a result recorded for visibility, sections, dates, and enrolment.
-
2
Slack - post the readiness report
WebRun opens Slack to post the readiness report. - Post a readiness report to the teaching channel with one line per course
- Mark each course ready or not ready and name what is missing
- Put the courses starting soonest at the top
- Show the count of courses still not ready so the number falls week by week
Done when The teaching channel has this week's course readiness report.
-
3
Gmail - draft a fix request per teacher
WebRun opens Gmail to draft a fix request per teacher. - Draft an email to the teacher of each course that is not ready
- List only that course's issues, such as a hidden course or a due date from last year
- Leave every draft unsent for the coordinator to review and send
- Never email a teacher or a student without approval
Done when A fix request sits drafted in Gmail for every course that is not ready.
How is each run configured?
Secure by default
Connect once, stays signed in
WebRun signs in once and keeps each session in a persistent environment, so every run picks up right where it left off.
Every action is checked against this policy before it runs.
Questions, answered
Will it change my courses?
No. WebRun reads course settings and reports what it finds. It unhides no course, moves no due date, and enrols nobody. Every change stays with the teacher who owns the course.
Does it email teachers automatically?
No. It drafts the email in Gmail and leaves it unsent. The coordinator reads each draft and sends it. The only thing posted without approval is the internal Slack report.
How does it spot a stale due date?
It compares each assignment's due date against the term dates you give it. Anything falling before the term starts, or matching last term's pattern, is flagged as needing a new date.
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.