BUS499 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 research and synthesis method

For BUS499 Senior Capstone, the working focus is this: Turn a bounded question or practice problem into a traceable line from purpose through evidence and method to a conclusion no broader than the record supports.

Check alignment among problem, question, evidence, method, analysis, limitations, and recommendation; one changed element may require the rest of the chain to change.

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: making the functional areas speak to each other

A senior capstone in business administration is assessed partly on whether the separate disciplines of the degree behave as one system in your hands. Integration is not a section to be appended; it is a property of the reasoning. The practical test is whether a decision proposed in one functional area is followed through into the areas it disturbs.

Work an example. Suppose the analysis points toward raising the price of a core product line. Treated as a marketing decision alone, that is a positioning statement and little more. Treated as an integrated decision it moves several things at once: contribution margin and break-even volume shift, which is a finance consequence; forecast volume changes, which alters capacity utilization and possibly inventory policy, which is an operations consequence; the sales incentive structure may now reward the wrong behavior, which is a human resources consequence; and if the product serves a regulated or contract-bound customer segment, there may be a compliance consequence. A recommendation naming all of these, even briefly, demonstrates the reasoning a capstone exists to assess.

Build a short cross-impact grid in your notes. List each recommendation down the side and the functional areas across the top, then force at least one sentence into every cell that is genuinely affected. Empty cells are fine where nothing is affected. Unexamined cells are not.

Reading the rubric row by row for the integration criteria

Integration rows are the ones most often lost by submissions that are otherwise well written. Scan the posted criteria for language reaching across topics: words such as across, connect, relate, comprehensive, or holistic, and any row naming more than one functional area in a single sentence. Those rows are not satisfied by covering each area well in its own section. They are satisfied by sentences that carry a claim from one area into another.

Some rubrics award integration explicitly with a row of its own. Others fold it into the recommendation or conclusion row, where the criterion expects the recommendation to be informed by everything preceding it. Determine which pattern the posted criteria follow, because it changes where the integrating sentences need to sit. If integration is its own row, it needs visible cross-references the reader can find. If it lives inside the recommendation row, the integration has to be audible in the recommendation itself.

Then test the draft with a reader's move: read only the section headings and the recommendation. If the recommendation could have been written without several of those sections, the integration rows are not yet earned, and the repair is to make the recommendation depend explicitly on the analysis currently sitting unused. The registered classroom remains the authority on which criteria apply and how they are weighted.

Source work: reusing evidence without recycling sentences

Integration naturally brings earlier sources back into play, and this is where two different rules get confused. Reusing a source is ordinary scholarly practice: the same annual report can legitimately support a claim about revenue mix in one section and a claim about geographic concentration in another. Reusing your own sentences is a separate matter, and a paragraph pasted forward from an earlier section usually signals that the new claim was never actually thought through.

The clean method is to re-enter the source through your notes rather than through the earlier draft. Return to the register row, reread the recorded claim, ask what the current section needs from that document, and write a new sentence for the new purpose with a fresh citation at the point of use. If the note does not contain what the new section needs, reopen the document itself, since a source often supports more than the single claim you first extracted from it.

Two boundaries deserve attention at this stage. Material written for a previous course is governed by the policy stated in the registered classroom, so check that position before carrying anything across. Confidential information from an employer, including internal figures and named individuals, should be generalized or omitted unless you hold clear permission to use it.

Three Week 5 pitfalls and how to fix them

The first pitfall is the stapled submission: strong individual sections with nothing running between them. It happens because sections get drafted in separate sittings, each one complete in itself. The fix is a linking pass in which the last sentence of each section is rewritten to hand something specific to the next, and any section that cannot hand anything forward is examined for whether it belongs at all.

The second pitfall is a recommendation that no evidence produced. Recommendations often arrive from professional intuition, which is valuable but not sufficient on its own, and the criteria reward the traceable version. The fix is to write each recommendation on its own line and note beside it the specific analysis and the specific source that generated it. Any recommendation whose line stays empty must either be supported with real evidence or cut.

The third pitfall is quietly widening the analysis to fit whatever sources happened to be collected. Integration invites this, because bringing everything together feels like a reason to include everything found. The fix is to keep the bounded question visible while writing and to test each incoming piece against it. A capstone answering a narrow question thoroughly reads as controlled work. One surveying a wide field reads as unfinished.

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