CMS Training Pipeline for County Government

A county government was migrating its public-facing website from CivicPlus to Acquia/Drupal — a significant platform change that touched every department. More than 75 staff members across the organization would need to learn a new content management system before the site went live.

The problem wasn’t just the scale. It was the spread. These editors ranged from communications professionals who lived in their CMS to department directors who updated a page once a quarter. They had different schedules, different comfort levels with technology, and different stakes in getting it right.

There was no existing training infrastructure. No onboarding process. No way to know who had been trained or who was ready for CMS access. And with a launch date approaching, we needed a system that could handle volume without creating a bottleneck for IT.

Rather than building a one-size-fits-all classroom experience, I designed a multi-stage compliance pipeline using tools already available in the county’s Microsoft 365 environment. The goal was to make training self-serve wherever possible, enforce prerequisites automatically, and hand IT a clean, verified list of editors ready for access — instead of an inbox full of “can you give me access?” emails.

The pipeline had four stages:

Registration with prerequisite enforcement — editors couldn’t skip ahead

Dual-mode training delivery — live sessions for collaborative learners, self-paced video for everyone else

Knowledge verification and automated recordkeeping — a quiz tied to Power Automate flows

Controlled, manual access provisioning — IT only provisioned access to verified completers

1PowerApps Registration GatewayPrerequisite lock · Certification validation · Automated enrollment2Live Training SessionsInstructor-led · Q&A · Role-specificOR2Self-Paced (Camtasia)Screen recording · Subtitled · On-demand3SharePoint Knowledge Check + Power AutomateQuiz · System-of-record update · Confirmation email · Access review flag4Manual Drupal Access ProvisioningIT reviews completion flag · Approves access · Editor enters live CMS

The four-stage pipeline moved editors from registration to CMS access with minimal IT overhead.

I built a registration form in Microsoft PowerApps that served as the entry point to the entire pipeline. Editors self-enrolled, but the form enforced prerequisites: you couldn’t move forward until you confirmed completion of any prior requirements. This created a clean, filterable list of who was in the pipeline, at what stage, and when — without anyone having to manually track it.

The gateway also triggered automated enrollment notifications, so training facilitators always had an up-to-date headcount.

Not everyone learns the same way, and not everyone could attend a live session. So I designed two complementary options:

Live sessions for editors who benefited from real-time demonstration, Q&A, and role-specific walkthroughs. These were structured around actual county use cases — creating press releases, updating department landing pages, managing documents.

Self-paced Camtasia recordings for remote staff, those with scheduling conflicts, or anyone who needed to revisit content. Each module was subtitled, task-specific, and organized by editor role.

Both paths led to the same next step. The choice was about access, not rigor.

After training, every editor completed a knowledge check hosted in SharePoint. The quiz wasn’t designed to fail people — it was designed to confirm readiness and create an audit trail.

When an editor submitted, Power Automate kicked off three things simultaneously:

Updated the system of record to mark their training as complete

Sent a confirmation email to the editor and their supervisor

Flagged the record for IT to review and provision Drupal access

This removed the manual step of editors emailing IT directly and eliminated the “I never heard back” problem that had plagued earlier rollouts.

The final step remained intentionally manual. IT reviewed the flagged completions, confirmed everything looked right, and provisioned Drupal access on a rolling basis. This kept humans in the loop for the actual permission grant while removing every other friction point from the process.

Editors who needed access urgently could be prioritized without disrupting the broader pipeline.

The pipeline processed all 75+ editors before the county’s launch date. More importantly, it did so without creating a backlog for IT or requiring a project manager to manually chase completions.

In the first 90 days after launch:

Zero failed compliance audits. Every editor who had CMS access could demonstrate they’d completed training. The system-of-record logs made verification instantaneous.

Significant reduction in IT support tickets related to access requests and basic CMS navigation — editors arrived with context, not just credentials.

The pipeline template was reused for a second training cohort when the county onboarded additional departments mid-year.

The biggest win wasn’t the training itself. It was that the process of training became something the organization could repeat, document, and hand off — without me in the room.