ACC/349 Cost Accounting Week 1 guide
A source-bounded manual for the real registered Week: capture its identity, map its rubric, complete the permitted work, verify delivery, and carry feedback forward.
An official Phoenix program page establishes a 5-Week class context for this mapped code. It does not publish a universal topic or assessment for ACC/349 Week 1. The registered classroom is authoritative for the exact work.
Capture the live Week identity
Record the exact Week heading, assessment or discussion title, type, directions, point value or weight, rubric version, template, permitted sources and tools, deadline and time zone, file type, and submission location. Preserve any announcement that changes a requirement. Do not rely on a prior section or the public program duration for assignment identity.
Separate every obligation into its own row: initial discussion, peer replies, paper, case, calculation, quiz, presentation, project step, laboratory, simulation, group dependency, practicum document, clinical task, or exam-preparation block. One Week position can contain several distinct completion tests.
Mark prerequisite work before production begins. Required reading, data access, site or preceptor confirmation, group input, instructor approval, template download, or earlier project feedback can determine whether the Week is ready to draft.
Convert the rubric into acceptance tests
Rewrite every row as a yes-or-no test. Identify the action verb, required concept or decision, evidence, example or application, calculation or visual, destination, and top-band condition. Highlight all, each, compare, analyze, evaluate, and justify because each word changes what complete means.
Directions and rubric remain separate contracts. Directions control scenario, audience, length, format, source limits, tools, and submission. The rubric controls scoring. If they conflict, pause and obtain clarification rather than silently choosing the easier interpretation.
Build a criterion-to-section map before writing. Every rubric row needs a visible home. Every major paragraph, table, slide, calculation, or appendix should earn its space by satisfying a named requirement.
Reading the rubric row by row
Open the posted rubric before the first reading, not after a draft exists. In an opening position the grid doubles as a vocabulary list: it shows which words this instructor treats as technical and which are ordinary English. Paste it into a blank document where there is room to write beside it.
Take one row apart. Every row has four visible parts: the criterion label down the left, the performance levels across the top, the descriptive text inside each cell, and the point range attached to the row. Read the cells from the highest band leftward rather than from the bottom up. The top cell is the specification, and every weaker cell is that same specification with something removed. Comparing the top two cells is the fastest way to find the one word that separates them, and it is usually applied, justified, complete, accurate, or supported.
Now underline the verb in each row and note the artifact that verb demands. Identify wants a list. Classify wants a sorted list plus the basis you sorted on. Explain wants a because. Compute wants visible work. Apply wants a computed result carried back into the scenario. Contrast wants two items held side by side with the difference stated in words. A row that reads compute and interpret is two obligations sharing one point value, and the interpretation half is the half most often left out.
Finish by adding the point ranges and seeing where the weight actually sits. Then rewrite the rows in the order your deliverable will present them, so the checklist reads straight down while you write instead of forcing you to jump around the grid.
Produce the Week 1 work
Begin with the purpose, answer, or decision the prompt actually requires. Organize by rubric logic, not by the order ideas occurred. Connect claims to evidence and explain why that evidence matters in the specific scenario. Label assumptions and keep facts, interpretation, and recommendation distinct.
For discussions, answer the prompt directly, add permitted evidence, apply it, and end with a question or implication that supports substantive peer exchange. For papers and presentations, use headings or slide messages that expose the argument. For calculations, show inputs, units, method, intermediate result, final result, rounding rule, and interpretation.
Clinical, practicum, laboratory, simulation, group, and authenticated actions remain student-performed. Support can explain concepts, help plan de-identified written components, review calculations, rehearse a presentation, or prepare for a proctored exam. It cannot fabricate experience, signatures, attendance, patient facts, or assessment performance.
Worked reasoning: sort a cost before you try to trace it
Week 1 opens the run, so the habit worth building first is the one every later position borrows: decide what kind of cost you are holding before deciding where it goes. Cost accounting puts two questions to every dollar. What is this cost attached to, and where does it sit right now. Neither question has one universal answer, which is why an opening position spends its energy on vocabulary that later positions treat as settled. The registered classroom decides which of that vocabulary the opening assessment actually asks for, so read what follows as reasoning practice rather than as a description of your assignment.
Reason through a small example the way a grader reads one. A manufacturer buys sheet steel, pays the operator who cuts it, pays the supervisor who watches the floor, and pays a regional sales manager. Four payments, four different fates. Steel and operator wages attach to the product and can be traced to it, so they are direct product costs. The supervisor's salary supports production but attaches to no single unit, so it reaches the product only through an overhead pool. The sales manager never touches production, so that salary expires with the period. Naming those four outcomes in one clean sentence is the exercise; the arithmetic afterward is bookkeeping.
Then follow the flow, because product costs do not become expenses when they are paid. Materials wait in raw materials until they are requisitioned, ride through work in process while the unit is built, rest in finished goods until a customer buys, and only then land in cost of goods sold. A cost incurred but not yet sold is still an asset. Many opening losses are not arithmetic at all. They are a cost parked one account too far along the chain.
Add the behavior axis once the first two hold. Direct materials rise with volume, factory rent does not, and a maintenance agreement with a base fee plus an hourly charge does both. Traceability answers where a cost goes; behavior answers what happens when volume moves. The same dollar carries both labels at once, and an opening prompt often wants the pair rather than either half by itself.
What counts as a source in cost accounting
Cost accounting is an internal discipline. Its output goes to managers inside the organization rather than to outside investors, so no external reporting rulebook dictates how a cost report must look. That single fact reorders the source hierarchy compared with a financial accounting class, and it catches anyone arriving with the expectation that one authority settles every question.
Rank the sources deliberately. Assigned course material sits first, because the course's own definitions are the definitions being graded; when a text and a website disagree about what a mixed cost is, the text wins in this classroom. Professional bodies come next, and for managerial work that means the Institute of Management Accountants along with its published statements and ethics guidance. Standard setters matter at the seams where internal costing meets external reporting, such as which costs may sit in inventory. Company disclosures like annual reports and investor materials are evidence about one firm's cost structure, used as data rather than as authority. Peer-reviewed and reputable practitioner work reached through the university library supports claims about what organizations actually do. Homework answer sites, uploaded solution files, and study-aid summaries are none of these and belong in no reference list.
Sources enter a draft by paraphrase first. Read the passage, look away, write the idea in your own sentence, then return only to check accuracy and capture the locator. Reserve direct quotation for a definition whose exact wording carries the point. And remember that arithmetic is not cited: the citation belongs to the inputs you borrowed and to the name of the method, never to the number your own calculation produced. Start a source ledger in the opening Week, one line per source, carrying what it supports, when it was published, and where inside it the passage sits. Kept from here, it is still usable in the final Week.
Verify quality and delivery
Run a requirement pass first: every direction and rubric row is present. Run a reasoning pass: evidence fits the claim, analysis fits the prompt, calculations reproduce, and recommendations follow. Run a consistency pass across prose, tables, figures, slides, appendices, citations, and references.
Finish with the delivery pass: current template, citation style, accessibility, filename, file type, export, links, and rendered upload. Open the final file after export. A correct source document can still fail when a chart clips, a table shifts, a font disappears, or the wrong version uploads.
After submission, record the posted result and feedback. Classify the miss, revise the smallest complete unit if revision is allowed, trace dependent changes, and write one prevention rule for Week 2. Reconcile the class grade and update the next action.
Three opening-Week traps and their fixes
The first trap is collapsing indirect costs into direct ones because they happen inside the factory. Location is not traceability. The test is whether the dollar could be tied to one specific unit without inventing an allocation, and whether doing so would be worth the effort. Factory insurance, machine depreciation, and the floor supervisor's salary all fail that test, which makes them overhead however obviously manufacturing they feel. Fix it by writing the test as a question beside each cost and answering it on paper before sorting anything.
The second trap is expensing production costs the moment they are paid. It feels intuitive and it breaks the whole statement. Fix it by narrating the chain for each cost you touch: purchased, requisitioned, in process, finished, sold. If a cost has not reached the sold step it belongs on the balance sheet, and any income figure built on the shortcut is wrong by exactly the amount still sitting in inventory.
The third trap is answering a rubric row with a definition when the row asked for an application. Opening prompts are full of terms, and proving you learned them by defining them is tempting. A row that says apply or analyze scores the sentence after the definition, not the definition itself. Fix it with a two-sentence rule while drafting: sentence one names the concept, sentence two puts it to work on the specific numbers or the specific company in front of you. If the second sentence will not come, the row is not finished.