Using ClassWatcher beyond the K-12 classroom

ClassWatcher started life in a K-12 classroom, and it showed. Every screen said "Parent." Every message assumed the person you were writing to was somebody's mother. That's exactly right for a Grade 4 teacher — and exactly wrong for a college instructor, whose students are adults, or a workplace trainer, whose "class" is a room full of employees.

Brightspace itself has never had that problem. The same LMS runs elementary boards, high schools, universities and corporate training departments. So we've caught the product up: ClassWatcher now asks where you teach, and adjusts itself to match.

This post covers what each environment changes, what a typical workflow looks like at each level, and — because we'd rather be straight with you — what the switcher deliberately does not do.

The four environments

When you first set up ClassWatcher, onboarding now asks a single question: "Where do you teach?" You pick one of four answers, and you can change it anytime in Settings — nothing is locked in, and switching never touches your data.

Elementary and secondary

These two work the way ClassWatcher always has. Contacts are labelled Parent and Student, and messages default to parents — because in K-12, the person who can change what happens on Thursday night is usually at home, not in your class. If that's you, nothing changes and there's nothing to do; the rest of this post is a look over the fence.

College and university

Pick this and the parent half of the product disappears. Messages default to students directly, and the parent contact fields are hidden entirely — no parent phone column, no "Text Parent" button, no half-filled fields nagging at you.

That's not just decluttering. Post-secondary privacy law — FIPPA in Ontario, FERPA in the US — generally means an institution doesn't discuss an adult student's academic performance with their parents. In college mode there's no parent channel to misuse, because the interface never offers one: you're messaging the student about their own work, which is exactly the conversation the law expects you to be having.

Corporate and workplace training

Plenty of Brightspace runs outside education altogether — onboarding programs, safety modules, compliance refreshers. In this environment the labels become Employee and Supervisor, the messaging console becomes Text Employees, and the per-person report reads as a progress report rather than a report card. The vocabulary finally matches the room: nobody is texting an account manager's mother about an unfinished WHMIS module.

A college instructor's week

The core job at post-secondary is the same one K-12 teachers know: find out who hasn't submitted before it becomes a pattern. With a cohort of eighty, checking submission folders one by one is even less realistic than it is in high school — the mechanics are the ones we covered in how to see who hasn't submitted in Brightspace, just multiplied.

So the workflow looks like this: import the class list, put the assignments that actually matter on a watch list, and scan. The list of students who haven't submitted appears in one place, and from that same screen you message the students themselves — a short nudge before the drop deadline, sent to the adult responsible for the work, which at this level is the person who didn't submit it.

Every message is logged against the student, so when someone lands in your office hours claiming nobody warned them, you can see the date you did. Who to contact at which level — and why it changes as students get older — is something we've written about before in contacting students or parents about missing assignments; college mode simply makes the student-only answer the default instead of an option.

A corporate trainer's week

Swap "assignment" for "module" and the shape holds. Your onboarding or compliance content lives in Brightspace; the question every week is who hasn't finished it. Watch the modules with real deadlines, scan, and you get the list of employees with incomplete training — then nudge them by text or email from the same screen, in language that says Employee rather than Student.

The per-person progress report earns its keep at review time: one screen showing everything an employee has and hasn't completed, with scores where they exist. And the contact log answers the question trainers actually get asked — "was this person reminded?" — with dates, because every nudge you sent is recorded, and the history exports to Google Sheets or CSV whenever you need it outside the tool.

What this honestly is — and isn't

Worth being precise, because "corporate mode" can be oversold and we'd rather not.

• It's labels and defaults, not a different engine. ClassWatcher reads Brightspace pages the same way in every environment. The switcher changes what the interface calls people and who a message goes to first — it doesn't add new data sources.
• It is not compliance reporting. There's no certification-window tracking, no audit trail formatted for a regulator, no HR dashboard. If your training program needs completion reporting you can hand an auditor, your LMS's own reporting tools are still the right answer — ClassWatcher is the quick who-needs-a-nudge layer on top, not a replacement for them.
• Texting stays one-way. In every environment, messages go out from a shared number that doesn't take replies. It's for telling someone something, not for holding a conversation.
• The platform limits don't move. It's Brightspace only, in Chrome on a computer — the same constraints as ever, covered in the first-week setup guide.

Getting started

New users get the "Where do you teach?" question during onboarding; existing users will find the same choice in Settings. Either way it's one selection, changeable anytime.

ClassWatcher is free through October 1, 2026, which means a college instructor can run it across the September assignment crunch — or a trainer across a full onboarding cohort — and know before the free period ends whether it earns a place in the week.