Assistant 1

Browser lacks capabilities required to play.

Upgrade or switch to another browser.

Loading…

<h1>Laurentis Launch Assistant</h1> <p> This walkthrough helps you review a course before students see it. You will look at your course in another tab while you answer a few questions here. At the end, you will get a short summary of items that are ready and items that may need work. <p>What are you reviewing today?</p> [[A whole course|Scope_Course]] [[A single module or unit|Scope_Module]] [[A single assignment or activity|Scope_Activity]]

<<set $issues = 0>>

<span class="meta-label">Scope</span> <p> You are checking a full course. The questions will focus on dates, content completeness, navigation, assessments, and a few basic accessibility checks. </p> [[Begin the check|Dates]]

<span class="meta-label">Scope</span> <p> You are checking a single module or unit. The questions will focus on how this piece fits into the course and whether it is ready for students. </p> [[Begin the check|Dates]]

<span class="meta-label">Scope</span> <p> You are checking one assignment or activity. The questions will focus on timing, clarity of instructions, grading settings, and basic accessibility. </p> [[Begin the check|Dates]]

<span class="meta-label">Step 1</span> <h2>Dates and visibility</h2> <div class="checklist"> • Check course start and end dates. <br> • Check due dates for early activities. <br> • Check whether Week 1 items are visible to students. </div> <p> With those items in mind, how would you describe the current state of your dates and visibility settings </p> [[Everything looks correct|DatesReady]] [[Some dates or visibility settings need attention|DatesIssues]]

<p> You did not see any obvious date or visibility problems. Students should see the right items at the right time. </p> [[Continue to content|Content]]

<p> You noticed one or more issues with dates or visibility. For example, an old date from a previous term, a hidden item that should be visible, or a due date that does not match your outline. </p> <p> Before you publish, plan to correct these items so that students are not blocked or surprised. </p> <<set $issues += 1>> [[Continue to content|Content]]

<span class="meta-label">Step 2</span> <h2>Content completeness</h2> <div class="checklist"> • Look for empty or placeholder topics. <br> • Check that linked files and pages open correctly. <br> • Confirm that Week 1 has clear instructions and activities. </div> <p> Thinking about what students will see, how complete does the content feel </p> [[The content for this scope feels complete|ContentReady]] [[Some content is missing, placeholder, or not ready|ContentIssues]]

<p> The modules or activities you reviewed feel complete. When students arrive, they will have clear material to work with. </p> [[Continue to navigation|Navigation]]

<p> You identified content that still needs work, such as missing files, placeholder headings, or partial modules. Before you publish, it will help to remove placeholders and fill in these gaps. </p> <<set $issues += 1>> [[Continue to navigation|Navigation]]

<span class="meta-label">Step 3</span> <h2>Navigation and structure</h2> <div class="checklist"> • Is there a clear place for students to start. <br> • Are weeks or modules named in a consistent way. <br> • Can students reach key items for Week 1 without hunting. </div> <p> From a student point of view, how does the path through the course feel </p> [[Navigation feels clear and consistent|NavReady]] [[Navigation feels confusing or inconsistent|NavIssues]]

<p> A student entering the course would be able to find a starting point and move into the next steps without guesswork. </p> [[Continue to assessments|Assessments]]

<p> You saw signs of confusion, such as two different places that look like a starting point or module names that jump between formats. Clarifying these patterns will reduce questions and support requests. </p> <<set $issues += 1>> [[Continue to assessments|Assessments]]

<span class="meta-label">Step 4</span> <h2>Assessments and grading</h2> <div class="checklist"> • Check that due dates and points or weights match your outline. <br> • Read assignment instructions in student facing language. <br> • If you use rubrics or criteria, confirm they are attached and visible. </div> <p> How confident do you feel about the assessment setup for the scope you are reviewing </p> [[I am confident the assessments are set up correctly|AssessReady]] [[Some assessment settings or instructions need review|AssessIssues]]

<p> The early graded work appears aligned and understandable. Students will see what is expected and when. </p> [[Continue to accessibility|Accessibility]]

<p> You noticed assessment items that need attention. For example, mismatched points, unclear instructions, or criteria that are not visible to students. Adjusting these before launch will help students focus on the task rather than the logistics. </p> <<set $issues += 1>> [[Continue to accessibility|Accessibility]]

<span class="meta-label">Step 5</span> <h2>Basic accessibility checks</h2> <div class="checklist"> • Key images that carry meaning have alt text or descriptions. <br> • Important videos have captions or transcripts. <br> • Text is readable against its background without strain. </div> <p> This is an introductory check and does not replace a full accessibility review. Based on what you saw, how would you describe your current accessibility readiness </p> [[These basic accessibility items are in place|AccessReady]] [[Some of these accessibility items still need work|AccessIssues]]

<p> You have already addressed several important accessibility needs. This will support a wider range of learners from the first week. </p> [[View launch readiness summary|Summary]]

<p> You identified accessibility improvements to make, such as adding alt text to key images, providing captions or transcripts for central media, or improving text contrast. Planning these changes now will make the course more inclusive. </p> <<set $issues += 1>> [[View launch readiness summary|Summary]]

<h2>Launch readiness summary</h2> <<if $issues == 0>> Based on your responses, you did not flag any major issues in dates, content, navigation, assessments, or basic accessibility. You appear ready to publish this course as it stands. Any changes you make before or during Week 1 can focus on refinement rather than repair. <</if>> <<if $issues > 0 and $issues <= 2>> You identified a small number of areas that need attention before or shortly after launch. Use your notes from this walkthrough to make targeted updates. Fixing a few specific issues in dates, content, navigation, assessments, or accessibility can have a noticeable impact on students’ first impressions. <</if>> <<if $issues >= 3>> You marked several areas as needing work. This is useful information to have before students arrive. If possible, delay publishing until you have addressed the key issues you noted. If you must launch on schedule, consider prioritizing items that block access or understanding, such as hidden Week 1 content, unclear assessments, or missing captions. <</if>> You can reuse this walkthrough whenever you prepare a new course or make significant changes for a future term.