BUS484 Week 7 planning manual

1. Capture the live Week 7 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 management and organizational decisions method

For BUS484 Entrepreneurship, the working focus is this: Define the business problem, affected stakeholders, alternatives, evidence, resource consequence, risk, recommendation, and measure of success.

Challenge the main assumption, compare at least one viable alternative, quantify where the record permits, and attach a realistic implementation and measurement plan.

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 7 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: a risk register the reader can actually use

Reconciliation in a venture course includes reconciling the plan with everything that could go wrong with it, and the section where students lose the most credibility is the risk discussion. The familiar failure is a list of generic hazards followed by generic reassurance: competition is a risk, and the venture will monitor the market closely. That paragraph names nothing and commits to nothing. A usable register does four things per risk, and it does them in a fixed order.

Name the specific event, not the category. Not supply chain risk, but the fact that one supplier provides a component with no qualified second source. Estimate how likely it is and what it costs if it happens, in the venture's own terms rather than on an abstract scale, so that a low-probability event with a fatal consequence is not filed alongside a likely nuisance. Separate mitigation from contingency, because students routinely merge them and the two are different commitments: mitigation reduces the chance or the damage before the event, such as qualifying a second supplier now; contingency is what happens after it occurs anyway, such as the substitution the venture would run and what that substitution costs in margin and delay. Finally, state the trigger, meaning the observable condition that tells the operator the contingency is now live. A contingency with no trigger never activates, because nobody is watching for the moment to use it.

Reconcile the register against the rest of the work. Every risk should be traceable to a dependency named somewhere earlier, and every strong dependency should appear in the register. A plan whose risk section does not mention its own most load-bearing assumption has not been reconciled; it has been decorated.

Reading the rubric row by row

The seventh Week is when rubric reading becomes forensic. Print or copy the criteria, then read the draft with the criteria in hand and mark the document itself, putting the row number beside the passage that satisfies it. Two kinds of trouble surface immediately. Unmarked passages are text that costs the reader time and earns nothing, and unmatched rows are points sitting unclaimed. Both are cheap to fix at this stage and expensive to fix later.

Give particular attention to the rows that are lost through documentation rather than through thinking. Internal consistency, correct attribution, complete reference lists, adherence to the required format, and following the stated instructions are rows a strong analyst loses by running out of time. They are also the rows that depend least on insight, which makes them the ones worth clearing first while a whole Week remains.

Then read for the instruction that is not a rubric row at all. Activities frequently carry directions in the prompt that the criteria do not restate: an audience to write for, a length range, a required section, a file format, a specific resource to draw on. Graders enforce these even when no row names them. Build a short list of every directive in the prompt that has no matching row, and verify each one separately. The registered classroom's prompt and criteria are the authority on all of it, and where the live version differs from anything described here, the live version is what counts.

Source work: auditing the reference record before the last Week

Run the reference audit now, in both directions, because doing it under closing-Week pressure is where citation errors are born. Read the finished draft and confirm that every in-text citation has a matching entry in the list. Then read the list and confirm that every entry is actually cited in the text. Orphans in either direction are common after a term of cutting and merging, and both directions look careless to a reader who checks.

Verify that the sources still exist and still say what the draft claims. Open each link. Web pages move, statistical series get revised, working papers become published articles with different pagination, and organizations reissue reports under new dates. A citation pointing at a page that no longer resolves invites the reader to doubt everything else. Where a source has been revised, decide whether the claim survives the revision before simply updating the date, since a changed number sometimes changes the argument that rested on it.

Check for the substitution error specifically. When a source is swapped late in a term, the replacement often does not support the claim as precisely as the original did, and the sentence is left unchanged because it reads fine. Reconcile each late substitution by rereading the sentence against the new source and rewriting the claim to fit what the new source actually establishes. Finish by confirming edition, year, issuing body, and title against the source itself rather than against the earlier draft, since transcription errors replicate quietly from one version to the next.

Three reconciliation pitfalls and their fixes

The first is deferring reconciliation into the closing Week. Final Weeks in an eight-week course concentrate work, and a document that arrives there still carrying contradictions will be submitted with them intact because there is no room left to hunt. The fix is to treat this Week as the deadline for consistency and the last one as the deadline for the deliverable itself, and to write those as two separate dates on the calendar so they cannot merge.

The second is the claim that has quietly outlived its support. Arguments evolve across a term, and a sentence written in an early Week often remains in the document long after the reasoning behind it changed. The fix is a claims pass distinct from the reference pass: read only the assertive sentences, ignoring everything around them, and ask of each whether the current body of evidence still supports it. Claims that no longer hold get revised or removed, not softened with a hedge and left in place.

The third is reconciling the document while leaving the classroom record unreconciled. Submissions, receipts, gradebook entries, and any outstanding feedback are part of what has to balance before the final Week. The fix is to open the classroom record this Week, confirm that every completed item appears as recorded, and raise anything missing through Aspen's official channel immediately, while there is still time for it to be resolved before the course closes.

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

Week 7 questions