Morrow helps your team coordinate work across a program.

Morrow is a free, open-source way for each person to connect their own assistant to the courses they can open. Faculty and staff can divide the course list, stay within their own access, and compare what each person found.

Each person uses their own account.

Each person connects the courses their own Canvas or Moodle sign-in can already open, and a shared review does not give anyone new access.

Find the Page for Your Role

Share a clear report.

Each person uses their own course sign-in.
The report names the page or assignment and proposed change.
Each course owner reviews and approves changes to their course.

Instructional DesignerI have reviewed eight nursing courses, but Ava owns NUR 210. I need to hand hers over without stepping on it.

Your Assistant Using MorrowI read NUR 210 and prepared a 14-item report: the current content, the proposed replacement, where it sits and why. NUR 210 has not changed.

Instructional DesignerGood. Apply the repairs in the seven I own.

Your Assistant Using MorrowNinety-six repairs applied and checked across your seven courses. NUR 210 is untouched, and its report is ready to share through your institution’s approved system.

Instructional DesignerAva has finished hers. Put both together for Friday.

Your Assistant Using MorrowThe meeting brief keeps each owner’s courses, decisions and results separate, and links every item back to the evidence that person shared.

Divide the work.

Morrow does not provide a shared team workspace. Each person keeps their own Morrow records, reviews their own courses, and shares only the reports their institution permits. Agree on the course list and who reviews what, then compare those reports. The examples below show possible ways to divide the work. They are not reports from actual Morrow users.

Faculty and designers build a course together.

Faculty bring the subject knowledge, the materials, and the learning goals. The designer turns them into modules, lessons, practice, and assessments, and asks faculty to decide the rest.

What Each Person Hands Over The designer hands faculty a course plan: the proposed pages and activities, the materials each one came from, and the questions only faculty can answer.

Plan weekly student support together.

An administrator compares missing work and discussion activity across the sections of a course. Each instructor decides who needs a personal check-in and reads every draft before sending it.

What Each Person Hands Over The administrator gives each instructor one comparison. It shows how many students did not submit, how many did not post, and the assignment or discussion behind each count.

Fix program-wide problems together.

A reviewer finds the repeated content and accessibility problems. A curriculum lead judges how they affect the learning sequence. Faculty decide which repairs go into the next revision.

What Each Person Hands Over The reviewer gives faculty the affected pages and assignments with the proposed wording for each. The report also identifies every item that still needs a person or another access tool to review it.

Two People, One Course List, and Clear Ownership.

When a designer prepares a repair across fourteen courses, the faculty member who owns a course still reads the proposed wording and approves it before anything is saved. Decide in advance who approves course content, who approves dates, and who reviews each change.

See How a Review Works