Nothing changes without a recorded approval

Morrow looks before it acts. Plan mode checks the Canvas course you have open and proposes changes in plain language; nothing writes until you approve.

Every approval becomes part of the trail.

Morrow opens read-only: it can inspect and propose, but not change You review every proposed change, in plain language, before anything changes Nothing writes until you approve, with undo where the course allows it

Plan proposes, Edit applies, and the approval between them is recorded

Morrow opens in Plan mode, so the default state is read-only: it can inspect and propose, but it cannot change anything. A change lands only after a deliberate switch to Edit and an approval.

Plan

Inspect and propose

Default · Read-Only

Morrow reads the course you have open and drafts the exact changes it would make, as a plain list a reviewer can sign off on. In Plan mode it cannot touch Canvas at all.

  • Inspects the course as it is right now, not a stale copy or export.
  • Shows every proposed change, with its scope, before anything happens.
  • Lets a reviewer reject the set or narrow it down item by item.

Edit

Apply what you approved

Applies Approved Changes

Once a change is approved, Morrow applies it and reads the result back from Canvas, so the record reflects what actually landed, not just what was intended.

  • Applies only the items that were approved, nothing extra, nothing inferred.
  • Confirms each result against Canvas and logs the outcome.
  • Still pauses for deletes and high-risk actions (see below).

You sign off on the whole change set before a single edit lands

When Morrow has a proposal, it stages the course, count, and changes as a card. You approve the set, reject it, or open it and sign off item by item.

That decision, and who made it, is what later shows the change was reviewed rather than automatic.

  • Plain-language items. Each line says what changes and where, so you can sign off without combing through every page.
  • Item-by-item sign-off. Keep the changes you’re confident in, hold back the ones that need a second look.
  • A person finalizes. Morrow never writes on its own. Approval is a deliberate, recorded step, not a default.

Hard-to-reverse actions always stop for a second yes

Confirmation Required

Even in Edit mode, deletes and other high-risk actions never run on momentum. Morrow classifies the risk of every change and stops for explicit confirmation on the ones that are hard to walk back.

Deleting course content Pages, assignments, modules, quiz questions, rubrics
Always Confirm
Bulk or irreversible changes Large batches and actions the course can’t undo
Always Confirm
Changes to people and enrollments Concluding or removing student access
Always Confirm

These never qualify for the quick path. They stage on their own and wait for a clear yes, recorded separately from the rest of the conversation.

Every change is logged, so the record is already there when someone asks

Approval is the safety step and the record-keeping step. Morrow keeps a dated history of what changed, who approved it, and what Canvas showed before and after.

The trail lives with the course, so a reviewer sees the work as it happened instead of a reconstruction later.

  • What it captures. Each entry records the change, who approved it, a timestamp, and the risk level, with before-and-after detail where Canvas supports it.
  • Reversible, and honest about what isn’t. Many changes can be undone from the history. Morrow flags up front which ones cannot be reversed, so the record never overstates what’s recoverable.
  • Exportable evidence. Download the record as JSON or HTML: a defensible trail you can hand to a reviewer, auditor, or accreditor without rebuilding it from scratch.

Plan, review, approve, execute, record

The same five steps every time, on every course. A person stays in control at the approval step, and every run leaves a defensible trail.

  1. Plan

    Morrow checks the course you have open and drafts the exact changes it would make.

  2. Review

    You read the proposal as a plain list, every item, before anything happens.

  3. Approve

    Approve the whole set, reject it, or sign off item by item at the recorded control point.

  4. Execute

    In Edit mode Morrow applies only what was approved, then reads the result back.

  5. Record

    Each change is logged with who approved it and a timestamp you can review, undo, or export.

Make every Canvas change defensible by default

Start with one Canvas course and the approval-first workflow fits a single instructor or designer right away. If your quality or accreditation team needs an auditable trail across courses, contact us.