Automated CoreCampus Clock-Hour Attendance Alerts
Every morning, WebRun opens CoreCampus, finds students whose cumulative clock-hour attendance has fallen below the required pace, drafts a check-in email to each one for their advisor to review, and posts the full at-risk roster to Slack for the registrar.
How do I catch clock-hour attendance problems before they trigger a SAP warning?
WebRun checks CoreCampus every morning for students whose cumulative clock-hour attendance has slipped below their program's required pace. It drafts a supportive check-in email for each one, leaves it in Gmail for their advisor to review and send, and posts the full at-risk roster to Slack, so the registrar catches attendance problems weeks before they become a SAP violation.
- Attendance problems get caught weeks before a SAP violation
- Advisors open Gmail to a ready-to-send check-in instead of a blank page
- The registrar sees the full at-risk roster every morning without pulling a report
Built for trade school registrars · career college advisors · vocational school administrators · proprietary school compliance staff
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
www.corecampus.comin a real browser with your saved login - no setup, no API keys. -
1
CoreCampus - find attendance below pace
corecampus.com
WebRun opens CoreCampus to find attendance below pace. - Open CoreCampus and pull each active student's cumulative clock-hour attendance percentage
- Compare it against the program's required pace threshold
- Flag anyone below pace along with their program, hours completed, and hours remaining
Done when Every student below the required attendance pace is listed with their numbers.
-
2
Gmail - draft a check-in email
gmail.com
WebRun opens Gmail to draft a check-in email. - Draft a short, supportive check-in email for each flagged student
- Reference their current percentage and what's needed to get back on pace
- Leave every draft in Gmail for the assigned advisor to review and send. Never send directly to a student
Done when A draft check-in email is waiting for the advisor for every flagged student.
-
3
Slack - post the at-risk roster
slack.com
WebRun opens Slack to post the at-risk roster. - Post the full at-risk roster to the registrar's channel
- Sort by how far below pace each student is, worst first
- Flag anyone close to the SAP warning threshold in red
Done when The registrar has today's at-risk roster in Slack.
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 email students directly about their attendance?
No. WebRun only drafts the check-in email and leaves it in Gmail for the student's advisor to review and send. Nothing goes out without a person approving it first.
How does it know what attendance pace is required?
It reads the pace threshold set for each program in CoreCampus, so a 600-hour cosmetology program and a 1,200-hour HVAC program are each measured against their own requirement.
What happens once a student catches back up?
It reads live attendance from CoreCampus every morning, so a student who climbs back above pace simply drops off the next day's roster automatically.
Related templates
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.