Skip to Main Content
University of Phoenix logo
University Library

LRR Queue SOP

Processing Re-Use Requests

Once the template has been selected and applied from the Library Request field to the new re-use request, take the following steps to begin processing the request.

  1. Verify that the linked CDG reflects the correct course.
  2. Verify accuracy of the Request Type, including Web and Tabs fields.
  3. Ensure the ID has specified a re-use request in the description..
  4. Open the course project (linked at top) in a new tab. On the course project page:
    • Look for the Review & Approve Design tasks near the bottom of the Course Design section.
    • Briefly review any that have comments.
    • Note the latest date among those.
    • Copy the task link of one that has the latest date (choose one if multiple).
  5. In the Task Management subtask:
    • Add a dependency using the Review & Approve Design task link copied from the course:
      • In the Dependencies section near the top, click the plus sign.
      • Ensure pre-text is "Blocked by."
      • Paste the task link into the field, selecting the full Asana task that displays below the pasted link.
    • Assign yourself the subtask.
    • Set the subtask due date.
      • If the CDG is approved, set the due date approximately 1 week out (or to align with the overall Build Request due date).
      • If the CDG is not approved, align the due date to the Review & Approve Design due date. (You can continue to adjust this date as needed.)
  6. Review the existing LRR to scan for external links that lack a corresponding Asana permission link.
  7. Update the parent task Issues field with any relevant issues as needed.
    • CDG not approved - The CDG was not yet approved upon task submission.
    • Pending permissions - External source(s) are included but don't yet have an Allowed status (or haven't been submitted).
  8. Communicate with the ID, noting any issues. If applicable, inform the ID that we'll start the build and note any adjustments that may be needed to the due date. (Re-use requests require that the CDG be reviewed before being processed.)
    • Thanks for submitting this, ID. We will get started on this once the CDG review is complete, which is our standard approach with the re-uses, since even minor changes/adjustments would be a change of scope and require the entire guide to be rebuilt.
    • Thanks for submitting this, ID. For the two external resources, can you please link the permission requests in the Description field? We will get started on this once those have been cleared and the CDG review is complete.
    • Thanks for submitting this, ID. We will get started. We've adjusted the due date a bit to allow for library processing.
  9. When a CDG is approved, set subtask due dates as appropriate.
    • Set the Task Management subtask due date for about 1 week later.
    • Set remaining subtasks - from Review & Make Any Necessary Updates to Tech Review - to fall in between the current date and the Task Management due date. (You can double up on subtasks when necessary, such as assigning Review & Make Any Necessary Updates, Tech Review/Task Management for another date, etc.)
  10. Assign subtasks based on the individuals' roles and considering their current workload.
    • Review & Make Any Necessary Updates
      • Assign to builder
    • ID Review: Draft Links
      • Assign to builder
    • Make Requested Edits
      • Assign to builder
    • ID Review: Draft Links (2)
      • Assign to builder
    • Make Requested Edits
      • Assign to builder
    • Tech review (if needed)
      • Assign to tech reviewer