Table of Contents

1. Prep Course for QA

Markette Pierce Updated by Markette Pierce

As of November 2025, the DEV to QA Checklist has been retired and its contents moved to either the Prep for Review Checklist or to the "Prep Course for QA" (formerly "Complete DEV to QA Checklist") Wrike task.

If your Wrike task doesn't yet include the checklist of DEV to QA items, see either the spreadsheet or use the short list of items below.

Short Course (Standard) DEV to QA Handoff

  1. Create and set up a QA course in Canvas.
    1. In the DEV course
      1. Change the title to ABC101QA: Course Title
        eg. SHA101DEV: Baking Summer Bread ---> SHA101QA: Baking Summer Bread
      2. Set the course code to ABC101QA
      3. Leave the SISID blank
      *Note: Leaving the SISID blank is especially important for courses that include Codio and other programs that rely on the SISID.
    2. Make a Copy of the ABC101QA
      1. In the copy, change the title to ABC101DEV
      2. Set the course code to ABC101DEV
      3. Set the SISID to ABC101DEV
        This will become the backup course
    3. Unpublish the DEV course. From this point forward, all work will be done in the QA course, and the DEV will be used as a reference only. Don't make any further changes to the DEV course.
  2. Handle Pre-Requisite Quizzes (if Applicable)
    1. Hold Harmless/Disclaimers/ Set-up pages: If the course has any preliminary pages such as these, be sure they're:
      1. in the Course Details module
      2. graded quizzes worth 1 point
      3. present in the syllabus table of assignments
      4. completion requirements in Course Details module include submission of quiz
      5. each following module has prerequisite to complete Course Details module
      Pre-req quizzes were not in place during review to facilitate ease of access for faculty author. Be sure they are in place and that the settings are correct before sending a course to QA.
  3. Create and Set Up QA Tracker
    1. In QA Tracker file, duplicate the Template sheet (create a new sheet within the 2026 QA Tracker file, and leave the Template sheet as is):
    2. Name the new sheet Course Code QA: double click the tab until it is editable, then fill in "ABC123 QA."
    3. Add links
      1. Add a link to the QA course in cell 1A and add the correct course code and course title.
      2. Add a link to the Wrike QA task in 1B.
    4. In the QA course, copy the Module tree structure from the Course Map to your clipboard. Paste this in cell 31A of the new QA Tracker page, to populate the sheet with the page titles. (If the Map doesn't appear, you can copy the Module Structure itself and paste it to the tracker. Then, at the top of the tracker sheet, pull down Script Center Menu and click Delete dupe rows.)
    5. Add the homepage link to line 30A.
  4. Update or Create Wrike Task
    1. Find the Parent QA Wrike task named "ABC123 7. QA".
      1. Link within the Wrike task to the completed QA tracker and the QA version of the course.
      2. Include any launch dates or deadlines you're aware of in the Description.
      3. If couse is intentionally using document-based projects, mention this in the Description.
      4. @mention the ID in the description
      5. Assign to Karen. No need to @ anyone else.
      6. Set the "Coursecode 7. QA" task to "To Do"
      7. If a "[COURSE] finalize video" Wrike task exists, make it a subtask of this main QA task.

Redux/Revision/Updates Course DEV to QA Handoff

  1. Complete the standard steps above, and then...
  2. Highlight in the QA tracker the course pages you have made updates to.
    You can find this information by checking View All Pages by last edit.
    You can then mark the Wrike task "ABC123_Update YYYY 1. Document Page Changes for QA & OD (ID/IDA)" as Done.

For-Credit DEV to QA Handoff

  1. Prepare Assets that Live Outside of Canvas for QA
    1. Communicate standards for specific to this course via the Styles and Settings Guide: In this Style & Settings Guide file, create a new tab and add any specific, unusual, uncommon, or difficult names or terms, capitalization, specific usages, etc. in the course that the copy editors need to know. If there are source documents that will be helpful during CE or QA (e.g. the faculty's video recording slide deck), please link them with a brief description. Be sure to complete the settings section, clarifying the specifics for this course.
    2. Alert QA team that SRT files are ready for copy editing via Wrike (2. Copy Edit Captions) as soon as they are available.
      Mark 2. Copy Edit Captions Wrike task "To Do".
      **If you have SRTs before the course is ready, please start an SRT-only QA Tracker.**
    3. Send downloadable tools to QA team for CE/ QA via Wrike (2. Copy Edit Course and Files) as soon as they are available.
      Ensure tool footers are in place and accurately reflect course and school information.
  2. Prep Course to Begin QA
    1. Ensure members of QA team are enrolled into course as designers.
    2. Make sure the three AA pages are (as needed):
      1) Unpublished
      2) Not listed in Modules view
      3) Overview is completed
      4) Facilitator notes are completed, if needed, or communicate to QA that blank page is intentional
    3. Ensure the language on the assignment submission page(s) appears as follows:
      "Click the Start Assignment button on this page, upload your file(s), and then click Submit Assignment to send it to <faculty/ your facilitator> for evaluation and credit."
    4. Be sure a "Meet the Experts" page is published appears only in page view if the course uses "Ask the Expert" pages. Do not add this page to modules view. Make sure slug on MTE page matches exactly slug on ATE page
  3. Create and Set up QA Tracker as outlined above.
  4. Update or Create Wrike Task as outlined above.

How did we do?

7. QA - Wrike Task Definitions

2. Copy Edit Captions

Contact