Description

A focused course, tailored for you

The District LMS Operations Playbook for K-12 Administrators

Run a closed-loop district LMS across every campus, with adoption, privacy, accessibility, and SIS integration on one weekly cadence.

Your district LMS is live on every campus. Adoption varies five-fold between sites, the board wants a single adoption number, the cabinet wants instructional minutes from the same data, and a teacher just added a third-party tool that nobody ran through the FERPA queue.

$199 one-time

Tailored to your situation. Access within 24 hours. 30-day money-back.

Includes a hand-built implementation playbook delivered alongside course access, generated for your specific situation.

Why this course

Running a district learning management system across a K-12 district is not a tool problem. It is an operations problem. The platform is installed. Teachers have accounts. Students log in. But the gradebook sync to the student information system fails at one elementary site every Monday morning, parents call the front office instead of opening a help ticket, principals have wildly different ideas of what the weekly usage report means, and the privacy review of integrated apps is six weeks behind because every new edtech vendor wants to be added now. Meanwhile the board packet wants a single adoption percentage, the superintendent wants instructional minutes mapped to standards, and the state reporting cycle wants attendance and grade data straight from the LMS as a system of record. This course gives the district administrator a closed-loop weekly operating cadence that handles all four audiences off the same dataset, plus a clean handoff to the site leads so they own their own adoption number.

What you walk away with

A weekly per-site LMS operating cadence with named owners at every campus.
A FERPA, CCPA, and student data privacy review queue that clears within five business days for every teacher-added integration.
A Section 504 and WCAG accessibility audit baseline for district-published content with a remediation schedule.
A reconciliation routine between the LMS gradebook and the SIS that catches sync failures before parents do.
A board-ready adoption report that translates logins into instructional minutes mapped to standards.

The 12 modules

Module 1. The district LMS as a system of record, not a tool

What changes the moment the LMS holds the gradebook of record, holds the official assignment archive, and feeds the state reporting cycle. Names the artefacts the district owes to families, to the board, to the cabinet, and to the state, and maps which of them the LMS now owns versus which the SIS owns. Resets the operating model from a teacher-facing tool to a district-level system.

Module 2. The weekly per-site usage review

Builds the standing weekly meeting between the district LMS owner and each site principal or designee. Defines the per-site usage report, the three numbers each site lead has to answer to, the difference between a low-adoption number that is a training gap versus one that is a content gap, and the script for the site lead conversation. Includes the meeting cadence, the agenda template, and the escalation path.

Module 3. Teacher professional learning that actually shifts adoption

Why one-shot training sessions never moved the adoption number, and what does. Designs a job-embedded professional learning cycle anchored to the LMS feature your district most underuses, with site-based coaches, paired classroom visits, and a sixty-day adoption goal. Includes the coach selection criteria, the pairing schedule, and how to fund this inside the existing professional development calendar.

Module 4. FERPA, CCPA, and the third-party app approval queue

The legal floor and the operating reality of teacher-added integrations. Walks the FERPA school official exception, the California CCPA student data carve-out, the COPPA threshold for under-13 users, the data processing agreement clauses every vendor has to sign, and how to run a five-business-day approval queue that does not become a teacher complaint. Includes the intake form, the review checklist, and the rejection language.

Module 5. Section 504 and WCAG accessibility of district content

What accessibility means in a district LMS context. Covers the WCAG 2.1 AA baseline, the Section 504 obligations on district-published instructional materials, the Office for Civil Rights complaints pattern in K-12, and how to run a sampling audit on teacher-uploaded content without making teachers the audit target. Includes the audit script, the remediation triage rules, and the parent communication template.

Module 6. SIS gradebook reconciliation with Aeries or PowerSchool

The most common cause of parent calls to the front office is a gradebook number that does not match between the LMS and the SIS. Maps the integration architecture for Aeries and PowerSchool, the most common sync failure modes by category, the daily reconciliation routine that catches discrepancies before parents do, and the escalation path to the vendor when the sync breaks. Includes the reconciliation report template and the parent-facing remediation language.

Module 7. Parent portal, attendance, and the front-office handoff

The parent experience of the LMS is the parent portal. Defines the parent-portal feature set the district promises, the attendance entries the LMS owns versus the SIS owns, the front-office staff who answer parent calls about logins, and the training for those staff. Includes the parent-portal welcome packet, the front-office quick reference card, and the multilingual support plan.

Module 8. Special education, IEP accommodations, and the LMS

How LMS settings interact with IEP accommodations. Covers extended time on assignments, alternate format delivery, screen reader compatibility, the case manager view of student progress, the bilingual aide access pattern, and the discrete settings that have to be configured per student. Includes the case manager training script, the settings checklist by accommodation category, and the audit routine the special education director can run.

Module 9. The instructional minutes report for the cabinet

Translating raw LMS usage data into instructional minutes mapped to standards is the report the superintendent and cabinet want. Walks the data model, the standards crosswalk, the assumptions that have to be stated explicitly, the quality control routine that catches outlier numbers, and the narrative the cabinet reads off the chart. Includes the report template, the data quality checklist, and the narrative framing.

Module 10. The board adoption report and the public number

What the board wants is a single adoption percentage with a trend line, a per-site breakdown, and the answer to two predictable board member questions. Builds the board-ready adoption report, defines the public number and its calculation, scripts the answers to the predictable questions about equity and about teacher workload, and gives the chart pack that goes into the board packet. Includes the report template and the public-comment response language.

Module 11. Vendor management of the LMS platform itself

Running the relationship with the LMS vendor as a district customer with leverage. Covers the quarterly business review with the vendor, the feature request queue and how to escalate one, the service level agreement and what to do when it is missed, the renewal negotiation prep that starts six months out, and the comparable district benchmark conversation. Includes the QBR agenda, the SLA review template, and the renewal prep workbook.

Module 12. The district LMS twelve-month operating calendar

Ties every prior module into a twelve-month operating calendar that runs the cycle predictably. Names what happens in August before school starts, what happens in the first six weeks, what happens at semester turn, what happens at state testing window, what happens at the end-of-year archive, and the summer reset routine. Includes the full calendar, the role assignments at each phase, and the handover packet for any staffing change inside the cycle.

How this addresses your situation

Specific modules that map to what you said you are dealing with.

The principal who walks in asking why a sister site has higher adoption goes to modules 2 and 3.

The cabinet ask for instructional minutes mapped to standards goes to module 9.

The board adoption percentage goes to module 10.

The teacher-added third-party tool that nobody ran through the FERPA queue goes to module 4.

What you get with this course

Twelve text-based modules in the Art of Service learning environment.
Downloadable templates for every module, including the per-site review agenda, the FERPA intake form, the WCAG audit script, the SIS reconciliation report, the cabinet instructional-minutes report, and the board adoption report.
The hand-built implementation playbook for the district, delivered alongside course access.
Thirty-day refund guarantee.

What you will have in hand by Day 1, Week 1, Month 1

Within 24 hours, your account in the learning environment is provisioned and the tailored implementation playbook is delivered alongside it.

Weeks one and two: modules 1 to 4, the operating model, the weekly site cadence, and the FERPA queue.

Weeks three and four: modules 5 to 8, accessibility, SIS reconciliation, the parent portal, and special education.

Weeks five and six: modules 9 to 12, the cabinet report, the board report, vendor management, and the twelve-month calendar.

Before and after

Before

The LMS is live on every campus, adoption varies five-fold between sites, the FERPA approval queue is six weeks behind, parent calls about gradebook discrepancies land at the front office, and the board adoption number is stitched together by hand the week before every meeting.

After

The district LMS runs on a weekly operating cadence with named owners at every site, the FERPA queue clears in five business days, gradebook discrepancies are caught by the daily reconciliation routine, and the board adoption number plus the cabinet instructional-minutes report come off the same dataset on a predictable schedule.

What happens if you do not address this

The board adoption number stays a hand-stitched figure that the district administrator personally owns every month. The FERPA queue keeps growing until the first parent complaint becomes an Office for Civil Rights inquiry. The gradebook reconciliation stays reactive, and the parent calls keep landing at the front office. The site adoption gap widens because nobody owns it at the site level. When the district administrator leaves or moves roles, the operating knowledge leaves with them.

Who it is for

A district administrator inside a K-12 public school district who owns or co-owns the learning management system across multiple campuses. Typically sits in instructional services, educational technology, or assistant superintendent's office. Responsible for vendor management of the LMS platform, district-level content governance, teacher professional learning on the system, integration with the SIS, privacy review of teacher-added third-party tools, accessibility of district-published materials, and the adoption story told to the board and cabinet.

Who this is NOT for. Classroom teachers looking for instructional design tips, vendors selling LMS platforms, or districts that have not yet selected a system. This is for the administrator who already owns a live LMS deployment and needs the operating discipline to run it well across every campus.

How it arrives

Text-based course in the Art of Service learning environment, plus downloadable templates and worked examples for every module, plus the hand-built implementation playbook delivered alongside course access.

Time investment. Roughly four to six hours per module, taken at your own pace. Most district administrators complete the full course in six weeks while running their normal operating cadence.

Why $199 is the right number

Vendor-provided training covers the platform features but does not address district-level operations, board reporting, or the FERPA approval queue. State association conferences offer one-shot sessions that rarely shift adoption numbers. This course gives the district administrator a closed-loop operating cadence and the artefacts to run it, anchored to a hand-built implementation playbook for the specific district.

FAQ

Is this tied to a specific LMS platform?

No. The operating cadence applies whether the district runs Schoology, Canvas, Google Classroom, Seesaw, or another platform. The implementation playbook is built for the specific platform the district uses.

Does this cover the SIS itself?

It covers the LMS-to-SIS reconciliation routine for Aeries and PowerSchool, which are the two most common in California districts. It does not teach how to administer the SIS itself.

How is the implementation playbook tailored?

The implementation playbook is hand-built for the specific district, naming the actual sites, the actual LMS platform, the actual SIS, and the actual board and cabinet reporting cadence.

Is there a refund if it does not fit?

Yes. Thirty-day refund guarantee, no questions.

30-day money-back guarantee. If after a week of working through the materials this is not what you needed, reply to the receipt email and a full refund is processed. No questions, no forms.

Within 24 hours your account in the learning environment is provisioned and the tailored implementation playbook is delivered alongside it.