Control packet intake and scope

At 8:15 Monday morning, Cedar Trail's controller asks whether the Year 5 reporting package can be released Friday. The folder contains a trial balance, subledgers, contracts, estimates, a draft cash-flow statement, note tables, and a digital-fact export. Several files have “final” in their names. That is not version control.

Create the intake manifest before opening the technical issues. Record entity, reporting basis, period, units, currency, preparer handoff, received timestamp, file name, version, source owner, and hash. Preserve the original packet read-only. Additions and replacements enter a change log.

Build a completeness expectation from the known business: bank and debt confirmations, receivable aging, inventory count and cutoff, fixed-asset register, lease population, tax provision, equity register, benefit schedules, legal letter, acquisition file, currency rates, derivative contracts, statement drafts, note checklist, and XBRL export. “Not present” is an intake result, not a reason to invent a fact.

Define the release decision and materiality framework supplied by the case. Name what this capstone does not provide: an audit opinion, legal advice, valuation attestation, tax return, or independent advanced-accounting conclusion.

The first deliverable is a packet manifest and missing-evidence register. It should be possible for another team to reproduce exactly what the learner knew before any adjustment was proposed.