BUS499 Week 2 planning manual

1. Capture the live Week 2 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 2 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 3. 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: converting early feedback into a stable routine

By the second week of an eight-week term the first marked work or the first instructor comments usually exist, and the most valuable thing a capstone student can do is turn those comments into a repeatable habit rather than a one-time patch. The most common note on early business capstone writing is that the work is descriptive. In capstone terms, description reports what an organization does, sells, or reported. Analysis explains why that fact changes the decision under examination. A paragraph that stops at the first is doing half the work the criteria expect.

Build a three-move paragraph shape and apply it everywhere. Move one states the fact with its source. Move two states the mechanism, meaning why that fact produces an effect in this market or this firm. Move three states the consequence for the question you set in the opening week. Worked through a concrete case, a sentence reporting that a competitor opened eleven new locations becomes a paragraph only when it explains that the expansion raises local density, compresses the catchment area your subject firm draws from, and therefore weakens the volume assumption sitting underneath any expansion recommendation. Once that shape is habitual it steadies the rest of the term, because every later section inherits it instead of being invented from nothing.

Reading the rubric row by row against your first marks

This is the first point where the criteria can be read against real marks rather than in the abstract. Put the returned work beside the posted rubric and assign every comment to a row. Comments that cannot be placed usually belong to a mechanical expectation stated in the instructions rather than in the rubric itself, and those are worth listing separately so they are not lost.

For each row where credit was withheld, write down the missing proof rather than a verdict about effort. A note reading that the section needed a stated evaluation criterion before its judgment is actionable. A note reading that the work should be more analytical is not, even when an instructor wrote it, so the work of converting the second kind into the first belongs to the student. Separate rows you missed completely from rows you addressed thinly, because those two failures have different repairs: the first needs new material, the second needs depth in material you already hold.

Carry the result forward as a short debt list, one line per row still owed. Review that list at the start of every remaining week and retire items as later work covers them. This stops criteria that were weak in the opening week from quietly staying weak until the term ends. Should the criteria be revised at any point, the version in the live classroom is the one that counts.

Source work: building a working library that holds up

Stabilization is when the source base stops being a pile of open tabs and becomes a register. Keep one table with a fixed set of columns: author or issuing organization, year, document type, the specific claim you took from it, the page or section, the retrieval date, and the place in your draft where it is used. A register in this shape answers the two questions that cause late trouble, namely what a citation was for and whether it is still needed after a section has been rewritten.

Set a discipline about verification while the library is small. Retrieve and read every document you intend to cite, even briefly. Confirm the author, the publication year, and the issuing body from the document itself rather than from a search result summary, because aggregators frequently attach the wrong date to reposted material. For any figure describing a market, a price, or a headcount, record the period the figure covers as well as the year it was published, since a report issued this year may describe conditions from two years earlier.

Where the registered activity restricts evidence to course materials, the register still earns its place: it records which required reading supported which claim, which is exactly what a criterion about using course content asks you to demonstrate.

Three Week 2 pitfalls and how to fix them

The first pitfall is repairing the one sentence an instructor marked while leaving the identical flaw in five other places. Feedback on early work is nearly always a sample rather than an exhaustive audit. The fix is to treat every comment as a search pattern: after correcting the marked instance, read the whole file hunting for the same move and correct all of them.

The second pitfall is letting the source register fall behind the draft. Once citations are added faster than the register is updated, the two drift apart, and reconciling them later costs several hours at exactly the point in the term when hours are scarce. The fix is a rule that no citation enters the draft until its row exists in the register.

The third pitfall is carrying opening-week prose forward without revision. Text written before the question was fully bounded often no longer matches the question being answered, yet it reads smoothly enough to survive review. The fix is a deliberate pass in which every paragraph inherited from earlier work is checked against the current question, and anything answering the old version is rewritten or removed. Reusing your own earlier material is normally fine inside a single course, but confirm the position stated in the registered classroom before doing it.

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

Week 2 questions