Canvas Course Sandbox

Canvas Course Sandbox Design

A private, unpublished Canvas shell where you can build, rehearse, and revise a course with none of it visible to a live section. No Canvas experience required to start one, and nothing here touches the course your students are currently in.

A sandbox is not a template you fill in, and it is not a redesign of your course. It is a clean, correctly built copy of the course as you actually teach it, structured and styled to CIDAT standards, with zero students enrolled, that becomes yours to work in and copy forward each term. CIDAT builds it. You keep it.

One principle governs the whole process: enrollment in a course is not ownership. Before anything is built, we confirm directly with you which course is actually yours to redesign, rather than assuming it from a Canvas role.

The Process

Six steps, from first conversation to the yearly refresh. The first build takes real effort; everything after it is a loop.

Confirm ownership: We start by confirming which course is genuinely yours to rebuild, not by inferring it from your Canvas role. Co-teaching or evaluation access is not the same thing as owning the content.
Intake, kept light: This is a personal ask, not an audit, and it never arrives with a list of everything wrong with your current course. Depending on the course, that means either a short request for your texts, the shape of your semester by week, and one filled-in example of each kind of class day, or, when fidelity to a course you already run well matters more, importing your existing course directly so the sandbox starts from your own material.
Build to the house standard: The shell is built in CIDAT's visual and structural style: a styled front page, the standard course navigation, a working example of correct structure built into the course itself, and a check for broken links and leftover content from wherever the material came from.
Verify before handoff: Every link resolves, every image renders, navigation matches the standard, and the shell itself, along with everything in it, stays unpublished with zero students enrolled until you say otherwise.
Hand it back: The sandbox becomes your working master. You copy it into your live course and adjust dates and content however you like. CIDAT does not touch live sections; the sandbox is where the building happens, not the classroom.
Refresh, not maintain: The sandbox is a cleaned checkpoint of your last good term, refreshed forward once per matching term rather than kept in constant sync. At refresh, an audit surfaces both what broke and what you changed on purpose during the term, and you decide which of those changes carry into the next version.

Two Sandboxes, Two Starting Points

Name and course numbers below are left out on purpose. Both are real CIDAT builds, shown to illustrate that the process bends to how a faculty member actually works, not the other way around.

Case Study

A two-course communication sequence, rebuilt from the ground up.

A faculty member teaching two sections of a writing sequence was rebuilding each new term from the one before it, and small problems were compounding and traveling forward: broken links, duplicated modules, leftover dates from an old term. Before CIDAT proposed a fix, he proposed his own: one sandbox per term, which he would copy from and adjust the dates on himself. It matched CIDAT's own thinking almost exactly, so it went in as he designed it.

The sandbox reflects his course as he actually teaches it, not a reinterpretation of it. When he renamed a page mid-term and left a batch of links pointing at the old page, that surfaced at the next scheduled audit and was fixed there, rather than chased down mid-semester.

Case Study

A two-course communication sequence, built from the faculty's own sections.

For another faculty member's two-course sequence, the starting point was his own most recent online sections, imported directly into the new shells so he wasn't starting from a blank course. From there: the standard style assets were loaded in, the front page was rebuilt to the house standard, folding an existing welcome page into it at his request rather than leaving two, and a worked example of correct module structure was added inside his own course as a live reference he could look at directly instead of a separate manual.

One thing mattered enough to flag here: nearly forty stale announcements had come over with the imported sections. Left alone, every one of them would have fired at students the moment the course published. They were cleared before handoff, alongside two course banners built to match the current palette. Both shells came back to him unpublished, with zero students enrolled, ready for him to build in.

Standing Rules

The reasons faculty can trust CIDAT with course-level access in the first place.

1)

We do not touch a course CIDAT is not enrolled in. Enrollment is the test, not the course name.

2)

CIDAT does not touch live course shells. Work happens in the sandbox, never in the section your students are in.

3)

An error-free shell is a property of a moment, not a permanent state. That's why the sandbox is audited at every refresh, not built once and forgotten.

4)

Nothing generates a student-facing notification during the build unless a notification is the actual point.

Get Started

Want a Sandbox Built for your Course?

Email Mark Stevens directly and we'll set up a time to talk through what you're teaching and how you want it built.

EMAIL MARK

BACK TO SERVICES AND SOFTWARE