ACC/291 Principles of Accounting II Week 2 guide

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 once feedback exists

By the second Week you hold something the first Week did not have: a graded artifact. Read the new rubric with the returned one open beside it. Where the two share a row, the earlier comment tells you how this particular grader interprets the language, and that interpretation outranks your own reading of the same words. Where a row is new, treat it as untested and give it more preparation time than its weight alone would suggest.

Work through the rows in descending weight order and assign each one a destination in the file before writing a sentence. A row that inspects computation belongs in a schedule with visible inputs. A row that inspects judgment belongs in prose that names an alternative and explains why it was rejected. A row that inspects format belongs in the template itself, handled once at setup so it never competes for attention later.

Watch for rows that quietly bundle two obligations, since second-Week rubrics commonly ask you to both calculate and evaluate inside one line. Split those into two acceptance tests and answer both explicitly, because a partial result on a bundled row usually traces to the half nobody wrote. The posted rubric and the current directions remain the authority; this ordering is only a way to read them.

Time the rubric read to the drafting session, not to the Week opening. Reading it on the first day and starting work on the third means you are drafting from a memory of the rubric, and memory smooths away exactly the qualifying words that decide rows. Reread the full rubric in the ten minutes before you begin producing, every time.

Produce the Week 2 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: plant assets as the term compounds

Plant assets appear in the published description of this class directly after receivables, without any Week assignment attached to them. The registered classroom sets the real second-Week task. What follows is practice on the reasoning pattern, not a claim about what is posted.

Start with the capitalization question, because it decides everything downstream. Suppose equipment with an invoice price of 88,000, freight of 3,000, installation and testing of 5,000, and a first-year insurance policy of 2,400. The first three costs are necessary to bring the asset to its intended use and belong in a capitalized cost of 96,000. The insurance is a period expense. Put it in the asset and every depreciation figure for the rest of the term inherits the error.

Now depreciate that 96,000 with a 6,000 salvage estimate and a five-year life. Straight-line divides the 90,000 depreciable base evenly at 18,000 a year. Double-declining-balance applies twice the straight-line rate, or forty percent, to book value and ignores salvage until the floor is reached, giving 38,400 in year one and forty percent of the remaining 57,600, or 23,040, in year two. Units-of-activity divides the 90,000 base by expected output; at 150,000 units the rate is 0.60 per unit, so 32,000 units produce 19,200. Same asset, three defensible answers, and the rubric usually cares less about which one you compute than about whether you explain the pattern of expense each method creates.

Then handle the change nobody expects. After two straight-line years, accumulated depreciation is 36,000 and book value is 60,000. If the remaining life is revised to six more years with salvage of 4,800, the new annual charge is 60,000 less 4,800 divided by six, or 9,200. Prior years are not restated. If the asset is instead sold for 52,000 at that point, the 8,000 shortfall against book value is a loss, and naming it as a loss rather than as a negative gain keeps the later cash flow work clean.

Source work for plant asset and depreciation claims

For this material the authoritative reference is the FASB codification topic covering property, plant, and equipment, and the useful equivalent inside a company's own reporting is the significant accounting policies note together with the property and equipment note. Those two disclose the depreciation methods in use, the useful life ranges by asset class, and the accumulated depreciation balance. A claim about how a company depreciates should cite the note, not a secondary summary of it.

Industry context is a different category and needs a different source. Comparative useful lives, capital expenditure intensity, and asset turnover across peers come from the filings of comparable companies or from published industry data, and any figure you borrow needs its fiscal period stated because asset bases move. Rating agency notes, analyst commentary, and business press coverage are interpretation. They can frame a discussion, but they cannot establish a measurement, and a row asking for evidence rarely accepts them alone.

Sources enter a plant asset draft in a specific order. Establish the accounting treatment first with the standard or the note. Present your own computation second, so the reader sees the method before the conclusion. Introduce comparative or industry evidence third, only where it supports the management judgment you are making. Every in-text citation needs a matching entry in the reference list and every reference needs a place where it was actually used, and the permitted-source rule in the live directions overrides this ordering whenever the two disagree.

One caution is specific to depreciation questions. Textbook examples and filed statements use different conventions for partial-year treatment, and borrowing a convention from a source without saying so produces a schedule a grader cannot reproduce. State the convention you applied in a single line beneath the table.

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 3. Reconcile the class grade and update the next action.

Three failures that surface in the second Week

The first is applying declining-balance to the depreciable base. Subtracting salvage before applying the rate is the most common plant asset error there is, and it produces a number that looks plausible and is wrong from year one onward. The fix is a written reminder at the top of the schedule: declining-balance multiplies book value, salvage only sets the stopping point, and the final year is plugged so book value lands exactly on salvage.

The second is restating prior periods after a change in estimate. A revised useful life or salvage value is handled going forward, spreading remaining book value over remaining life, with no correction to years already reported. The fix is to state that treatment explicitly in one sentence before the revised schedule, since a grader reading a revised table cannot otherwise tell a deliberate forward-looking treatment from an oversight.

The third is losing the feedback loop. Comments returned from the first Week get read once and never converted into behavior, so the same deduction repeats. The fix is mechanical: keep a short running list of grader corrections and run that list against the draft before the delivery pass, retiring an item only after two clean submissions.

Questions about ACC/291 Week 2