BUS454 Week 8 planning manual

1. Capture the live Week 8 packet

Create one row for every visible activity. Record its exact name, type, complete instructions, rubric or grading criteria, points and course weight, due date with time zone, permitted and required resources, length and file format, discussion reply rules, group or supervisor dependencies, attempt limits, submission location, and instructor announcements. Save the rubric version with the working file.

2. Translate criteria into visible proof

Rewrite each criterion as a testable question: what must the reader see to award this row? Pair it with the concept, evidence, example or calculation, reasoning step, and location where the proof will appear. This prevents a polished response from missing a small but expensive instruction. When the Week contains several activities, map each separately before deciding the order of work.

3. Apply the policy and ethical reasoning method

For BUS454 Ethical Decision Making for Business, the working focus is this: Identify the controlling rule or principle, distinguish facts from assumptions, compare affected stakeholders, and defend an action while acknowledging constraints and competing obligations.

Verify authority and dates, test the recommendation against a plausible counter-position, and separate legal requirements from ethical judgment.

Use course materials first when the live instructions require them. Add outside evidence only when permitted, verify every source directly, and keep notes that distinguish the source's claim from the student's interpretation. For calculations or structured analyses, retain inputs, units, assumptions, intermediate steps, and an independent check.

4. Build a student-owned response

Draft from the evidence map rather than from a generic sample. Open each section with its purpose, make the claim proportional to the evidence, explain the relationship the rubric asks for, and close with the decision, implication, or transition the reader needs. A tutor may demonstrate a parallel problem, question the logic, or comment on a student draft; the student's own judgment, context, language, verification, and final version must remain visible.

5. Run the Week 8 quality gate

Compare the finished work line by line with the live instructions and rubric. Check factual support, evidence currency, calculations, citations, headings, file type, accessibility, confidentiality, originality, and the stated audience. Confirm that replies, approvals, group actions, proctored steps, or supervised requirements have actually been completed by the student where the registered Week requires them.

6. Submit and close the loop

The student performs the final upload or entry, opens the submitted artifact to confirm it is readable, and saves the receipt. When a grade or feedback arrives, record the criterion-level result, instructor comment, required correction, and lesson for Week 8. If an attempt is missing, late, or technically broken, use Aspen's official channel immediately rather than assuming the gradebook will repair itself.

Worked reasoning: writing so a reader who was not there can act

Closing work is judged by whether somebody outside your own head can follow the reasoning to the same conclusion. Assume a reader who is capable, busy, and entirely unfamiliar with your term. That reader needs four things in the first paragraph: the decision at issue, the recommendation, the principal reason for it, and the main cost of following it.

Build the closing structure backwards from that paragraph. State the situation in the minimum facts needed for the decision to make sense. State the ethical question in a form that can be answered, or that names the obligations in competition. Present the analysis in the order that supports the recommendation, not in the order you happened to discover it. Give the recommendation with its owner and its measure. Close with the objection and your answer, so the reader can see that the hard version was considered rather than avoided.

Then read the whole document once as an opponent, marking every place where you would say prove it. Each unmarked assertion that survives should either gain evidence or lose some of its confidence. This is the same discipline the course has been building since orientation, now applied to a document that has to stand on its own.

Carry the method out of the course as an artifact. Write a one page protocol for yourself: the questions you now ask before deciding, the frameworks you found most useful and the point at which each fails, and the checks that caught your own errors. That protocol is what the term was for, and it travels. Whatever the registered final activity requires is what you actually submit.

Reading the rubric row by row on the last pass

The final read of a rubric is a verification exercise rather than a planning one. Open the criteria beside the finished document and move down the rows one at a time, pointing to the specific page and paragraph that satisfies each. If you cannot point, the row is not earned, whatever your impression of the draft as a whole.

Give extra scrutiny to rows carrying the largest share, since closing deliverables in an eight week course often concentrate weight, and to any row that references the course as a whole rather than this week alone. Cumulative rows usually want evidence that earlier material has been absorbed, which means naming concepts explicitly instead of assuming a reader will infer them.

Check the mechanical rows last and completely: file type, file name where one is specified, length, headings, title page and reference formatting, and anything the instructions require to be included or left out. Then confirm the submission route and the deadline with its time zone from the registered classroom itself, since that posting, and not any calendar you built, is the authority.

Closing the source file and carrying it forward

Finish the term with a source set you could defend line by line. Run a last verification of every citation remaining in the final document, then clear out of your working file anything you decided not to use, so what survives contains only material you have actually read and checked.

Reorganize the remainder for reuse. Group entries by what they establish rather than by the week you found them: frameworks and definitions, empirical findings, legal and regulatory instruments, standards and codes, organizational documents. Add one line to each saying what you would cite it for next time and what it cannot support.

Keep the searches too. The term produced a set of search phrasings and a sense of which collections were productive for this subject, and that knowledge is easy to lose between courses. Note the sources you rejected and why, since the same weak material will surface again. Store the whole file somewhere a later course can reach it, together with your rubric notes and the correction list you have been maintaining. None of it substitutes for the resource requirements posted in whatever course comes next.

Three closing pitfalls and their fixes

The first is the summary that only summarizes. A closing section restating each earlier part in order adds nothing and consumes words the argument still needs. The fix is to make the closing do new work: state what the analysis established, what it could not settle, and what should happen next.

The second is the final hour submission. Files convert badly, uploads fail, and a document that looked correct in one program can lose its formatting in another. The fix is to finish early enough to submit, reopen the submitted version exactly as a reader will see it, confirm every page rendered, and save the receipt.

The third is closing without harvesting. Once a course ends, access to feedback, criteria, and returned work can lapse, and with it the record of which habits cost you points. The fix is to save the criterion-level results, the instructor comments, your corrections list, and the final deliverables before the term closes, then write three sentences on what you will do differently, which is the part of this that improves the next course. Use the official channel for anything still unresolved in the gradebook.

Source boundary

Aspen University's official FAQ verifies that courses run eight weeks and that each Week's activities are organized in the online-classroom syllabus. The active catalog verifies this course code and title. Neither public source identifies the student's current Week 8 activity, so this manual never assigns it one.

Week 8 questions