BUS484 Week 4 planning manual

1. Capture the live Week 4 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 4 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 5. 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 unit economics reconcile at the midpoint

Halfway through an entrepreneurship term the numbers written casually in earlier submissions start to matter, because later work builds on them and a wrong figure propagates quietly. Whatever the live activity asks for, the audit worth running now is arithmetic: does one unit of the thing being sold actually pay for itself, and does the record already on file agree with itself?

Run the chain in order and write down each input rather than holding it in your head. Start with the price a buyer pays for one unit. Subtract only the costs that occur because that unit was sold: materials, delivery, payment processing, hourly labor tied to the job. What remains is the contribution each unit makes toward everything else. Divide the fixed costs that continue whether or not anything sells by that contribution, and the result is how many units the venture must move before it stops losing money. Then set the cost of acquiring one buyer against the contribution that buyer produces, and count how many purchases it takes to earn that acquisition cost back. A venture that needs several repeat purchases to recover acquisition is making a claim about retention, and that claim needs its own evidence.

Now reconcile backward. Open every earlier submission and check that the price used here matches the price stated there, that the cost assumptions have not drifted, and that any market size mentioned earlier is consistent with the volume this arithmetic requires. Where two documents disagree, decide which figure is right, correct it going forward, and note the correction so a reader who has both documents is not left wondering. Silent revision of a number a grader has already seen reads worse than an acknowledged fix.

Reading the rubric row by row

The midpoint is the last moment when rubric reading is a planning activity rather than a repair activity, so read across the whole set of returned criteria at once instead of one item at a time. Lay the marked rubrics side by side and tally which rows have lost points more than once. Two losses on the same row is a pattern, and patterns are what remain fixable while half the term is still ahead.

Do the weight arithmetic honestly. Add the weight of everything already graded, add the weight of everything still to come, and see plainly how much of the course outcome remains in play. This single calculation changes behavior more reliably than resolve does, because it converts a vague sense of being behind into a specific answer about where effort now pays. If the remaining weight is concentrated in later deliverables, the correct response is to invest in the skills those criteria reward rather than in relitigating a graded item.

Then read the current activity's criteria for accuracy and support rows specifically. Midcourse work in a business course tends to carry more numerical and evidentiary weight than the opening weeks did, and rows that ask for supported claims, appropriate evidence, or accurate application are the ones most exposed to the reconciliation problem described above. Verify that every number reaching the page can be traced to something written down. The posted rubric governs how these rows are weighted and worded; treat the reading here as a method, not as a description of what is on file.

Source work: numbers, series, and the discipline of retrieval

Quantitative sources need handling rules that prose sources do not. When a figure comes from a statistical series, four things travel with it or the figure is unusable: the unit, the period, the geography, and the collection body. A revenue statistic without a currency and a year is not a fact. A count of firms without a definition of what counted as a firm cannot be compared with anything. Write these into the sentence or the note, not into a mental footnote that will be gone by the final Week.

Distinguish quoted figures from derived ones. A quoted figure appears in the source exactly as written and needs a citation. A derived figure is one the student calculated from source inputs, and it needs the citation plus a visible derivation, because the reader cannot verify arithmetic that happened offstage. Keeping a small assumptions sheet listing every input, its origin, and the operation performed on it costs a few minutes now and protects the entire back half of the term.

Prefer the original issuing body over the outlet that reported it. Trade coverage of a government release should send you to the release. Where the original is genuinely unavailable, cite what was actually read and identify the chain inside the sentence rather than implying direct access to a document never opened. Also record retrieval dates on anything published to a website, since series get revised and a figure that no longer appears at the cited location looks like invention when it was simply superseded.

Three midpoint pitfalls and their fixes

The first is the average that hides its distribution. A single mean price, mean job size, or mean customer value flattens exactly the variation a venture decision depends on, and a plan built on the middle of a wide range will fail at both ends. The fix is to carry a range wherever the underlying data has one, state the low and high alongside the typical case, and show what happens to the conclusion at each end. Two extra numbers usually turn a fragile claim into a defensible one.

The second is postponing a gradebook discrepancy. A missing entry, an attempt that did not record, or feedback that references work the student did not submit will not resolve itself, and the window for a clean resolution narrows every Week. The fix is to raise it through Aspen's official channel the day it is noticed, with the submission receipt attached, rather than waiting to see whether it corrects.

The third is auditing the deliverable while ignoring the calendar. The remaining Weeks are not equally free; later ones typically concentrate more work per Week. The fix is to lay the remaining Weeks out with their known commitments visible, identify which Week is already overloaded, and pull whatever preparation can be done early into the lighter Week now sitting in front of you. Reconciliation of the schedule is part of the midpoint audit, not separate from 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 4 activity, so this manual never assigns it one.

Week 4 questions