BUS484 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 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 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: testing whether the business model actually holds together

Integration in a venture course means something more demanding than referencing earlier Weeks. It means checking that the parts describe one business rather than several. A model has a handful of components that must agree with each other: who the buyer is, what value they receive, how they are reached, how money comes in, what the cost structure looks like, and what the venture must be capable of doing every day to deliver any of it. Each of these has probably been written about separately by now. The integration test is whether they can be true at the same time.

Test it by walking one path all the way through. Take the buyer as defined in the earlier work and follow that specific person to the point of purchase. Does the channel described actually reach them where they already are? A positioning built on high-touch consultative service paired with a self-serve online funnel is a contradiction, and it is invisible while the two sit in separate sections. Does the revenue model match how that buyer prefers to pay, and does the pricing leave room for the channel's own cost? A channel that takes a share of each sale must appear in the cost structure, not only in the narrative.

Then run the test backward from operations. List what the venture must do repeatedly to keep the promise, and check that each capability is either already present, purchasable at a cost that appears in the model, or explicitly named as a gap. A business model that requires a capability nobody has budgeted for is a wish. Write one paragraph naming the single component the whole model most depends on, since that is the component whose failure takes everything else with it.

Reading the rubric row by row

Criteria at the integrating stage usually contain rows that reward connection, and connection is scored on visibility rather than on the student's private awareness of it. Look for language about applying course concepts, building on prior work, synthesizing material, or demonstrating cumulative understanding. Those rows are not satisfied by a draft that happens to be consistent with earlier submissions; they are satisfied by sentences that state the relationship out loud.

Place those statements deliberately. The strongest position for an integrating sentence is the opening of a section, where it frames what follows, and the second strongest is the transition between two sections, where it explains why one leads to the other. Buried mid-paragraph, the same sentence does the same intellectual work and collects fewer of the points, because the reader scanning for the connection row does not find it where the row expects it.

Read the organization row with fresh attention as well. Integrated drafts get long, and length exposes structure. A grader deciding between bands on organization is asking whether the sequence of sections was chosen or merely accumulated. Give the draft a visible logic, state that logic in a short roadmap near the beginning if the format allows one, and make each heading name a function rather than a topic. What any of these rows is worth, and whether they exist in this form at all, is settled only by the criteria posted in the live Week.

Source work: retiring source silos across the project

By the fifth Week most projects have developed source silos: the competitive sources live in the competitive section, the operational sources in the operational section, and nothing crosses. Integration frequently means the same source now speaks to two different claims, and using it twice is legitimate as long as the two uses are genuinely different. Borrowing a licensing requirement from a regulatory source in one section and the compliance cost implied by that same requirement in another is one source doing two jobs, and it should be cited in both places without apology.

Build a source map to find the crossings. List the project's main claims down one side and the sources across the top, then mark which source supports which claim. Two patterns will appear. A claim with no marks is unsupported and needs either evidence or demotion to an explicit assumption. A source with marks in only one row is probably underused, and rereading it with the other sections in mind often yields the connective evidence an integration row is asking for.

Reusing your own earlier prose is a separate question and a real one. Carrying forward material written for an earlier Week of the same course may be expected, restricted, or prohibited depending on the instructor's stated policy, so check the policy in the registered classroom before assuming either way. Where reuse is permitted, revise rather than paste: earlier prose was written to answer an earlier prompt, and text that fit the old question rarely fits the new one without work.

Three integration pitfalls and their fixes

The first is the stapled draft. Sections assembled from previous work in sequence produce a document with no argument of its own, and readers notice immediately because the register shifts at every seam. The fix is to write the connective material first, as a standalone outline of how each part depends on the one before it, and only then place the existing sections underneath it. Anything that will not attach to the outline does not belong in the integrated version.

The second is the number that changed in one place. When a price, a cost, or a market figure is revised in a later section and its earlier appearances are left alone, the document contradicts itself, and a reader who spots one contradiction begins checking everything. The fix is a single search pass per key figure before submission: search the document for the number, confirm every instance matches, and keep a short list of the figures that must be searched so the pass takes minutes rather than an afternoon.

The third is integrating the content while leaving the citations fragmented. Merged sections often carry duplicated references, two formats for the same source, or citations pointing at material that was cut. The fix is to rebuild the reference list from the merged draft rather than from the pieces: read the finished document straight through, note each citation as it appears, and construct the list from that pass alone.

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