BUS454 Week 5 planning manual

1. Capture the live Week 5 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 5 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 6. 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: moving from the act to the system that produced it

Integration in an ethics course means connecting the individual judgment you practiced early in the term to the organizational conditions that make such judgments predictable. Take a hypothetical distributor whose sales compensation pays the full commission at signature, with no adjustment when a customer cancels inside the first quarter. Representatives begin closing marginal accounts. The early-term question was whether a particular representative acted wrongly. The integrated question is why an organization staffed with ordinary people reliably produced that pattern.

Work through the system in layers. The incentive layer rewards the behavior directly. The measurement layer counts signatures rather than retained accounts, so the harm never appears in the numbers leadership reads. The voice layer determines whether anyone who notices has a route to say so and whether using that route is safe. The tone layer sets whether written commitments are treated as real constraints or as aspirations.

Now pitch the recommendation at the level where the cause actually lives. A memo instructing representatives to behave better addresses a symptom; changing when commission vests, and adding a retention measure to the same report, addresses the mechanism. Say explicitly which layer each recommendation touches and acknowledge what it costs, because a proposal with no admitted cost reads as untested.

Keep the earlier weeks visible while you do this. The stakeholder work and the framework comparison built before are the inputs, and the systems view is what they add up to. Whether organizational recommendations belong in the current deliverable is settled by the posted instructions.

Reading the rubric row by row when synthesis is the criterion

Synthesis rows are scored on connections, and connections stay invisible unless the prose makes them explicit. Read each row and ask what two things it wants joined: a concept with a case, a framework with a recommendation, earlier course material with the present problem, or evidence with a claim.

Then hunt for the joining sentences. A synthesis paragraph has a recognizable shape. It names both elements, states the relationship in a verb that does real work, such as constrains, explains, or contradicts, and then shows that relationship operating on the facts in front of it. Paragraphs that set two ideas side by side without a verb between them read as a list and score as one.

Check whether any row rewards carrying earlier material forward. If it does, name the concept and use it rather than gesturing at previous learning. Then count the required parts again. Integration deliverables tend to have several components, and a row that quietly asks for one specific section is cheap to satisfy and expensive to miss. Only the criteria posted in your registered week decide any of this.

Triangulating organizational documents with published research

At the integration stage the strongest support comes from setting different source families against each other on the same question. Scholarship tells you what tends to happen and why. An organization's own documents, its published code, its governance charter, its annual disclosures, tell you what it has committed to. Regulatory instruments and agency guidance tell you what is required and where enforcement attention has gone.

Triangulation means finding one question addressed by at least two families and reporting the fit. Where a published commitment lines up with what research says works, you have a supported claim. Where the commitment exists but the practice described elsewhere does not match it, you have found the gap that most ethics analysis is really about. Name that gap in a sentence instead of leaving a reader to notice it unaided.

Handle organizational documents carefully in the prose. Attribute them as statements by an interested party, quote operative language exactly where the wording carries the point, and give the document date, since codes and policies are revised. Keep a separate note of what each document does not say, because silence on a topic is frequently the finding. Confirm permitted source types against the live activity before building on any of them.

Three integration pitfalls and their fixes

The first is the seam. Sections written on different days in different voices sit next to each other with no transition, and a reader feels the paper change hands. The fix is a dedicated pass that reads only the first and last sentence of each section in order, rewriting until the sequence tells one continuous story.

The second is recycled prose. Bringing an earlier week's paragraph forward unchanged answers the earlier prompt inside the current one, and the mismatch is immediately visible. The fix is to carry the finding forward and rewrite the sentences for the present question, keeping the citation attached.

The third is the recommendation with no owner. A proposal saying the organization should strengthen oversight cannot be evaluated, because nobody is named and nothing is scheduled. The fix is to attach four elements to every recommendation: who acts, what triggers the action, how anyone would later know it happened, and what it costs.

A useful check before submission is to read the deliverable as though you were the person named in the recommendation. If you could not begin work on Monday morning from what the page says, the recommendation is still an intention rather than a plan, and the analysis above it will read as unfinished too. Where the registered activity specifies its own format, that format takes precedence over this general shape.

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 5 activity, so this manual never assigns it one.

Week 5 questions