Each record the pet chain holds gets its own row, sorted by collection method and marked use, hold or exclude, in a customer data inventory for MT362 Unit 3. Searches like "mt 362 unit 3 assignment example", "mt362 unit 3 sample" and "mt362 unit 3 example" land here.
What a finished MT362 Unit 3 customer data inventory looks like
A wide table of thirteen rows and eight columns, followed by four pages of notes. Columns cover the source, the fields it holds, the collection method, the notice or terms in force when it was gathered, the date range, the internal owner, known quality problems and a verdict for the churn model. Rows run from point-of-sale transactions linked to Copperline Rewards since 2016, through pet profiles customers typed into the app, Repeat Delivery schedule edits and exit-survey answers, to chat transcripts, app location data and a household data file bought from a broker in 2023. Birth years collected at Rewards sign-up until 2021 get their own row. Vaccine clinic records appear too, marked as held by the veterinary partner rather than the chain, and so outside the inventory's reach.
How a MT362 Unit 3 example is structured
Collection method organizes the table, because the same field can be fair to use or not depending on how it arrived. Data customers entered themselves come first, then records the business generated by observing transactions, then data inferred or bought. Each row states the notice in force at collection, quoting the privacy policy version by date, so that the Unit 4 consent review can hold the churn model up to the notice customers actually read. Quality problems are recorded as plainly as sources: email open rates marked unreliable since mail apps began preloading images, and pet weights never updated after puppyhood. The verdict column uses three values only, use, hold or exclude, and every hold names the question that must be answered first. The notes then explain the four hardest rows at length, closing with a list of data the churn model will not need.
Told, observed, bought
Rows are grouped by origin. Pet profiles and exit-survey answers were told directly; purchases and schedule edits were observed; a broker file estimating household income and homeownership was bought in 2023, and its notes record that nobody could say which campaign used it.
The notice beside every row
Each source cites the privacy policy version live when its data was gathered, from a 2019 policy to the 2023 revision. That column is what lets a later review ask whether a churn model counts as a purpose customers were told about.
Birth years nobody asked for since 2021
About 38 percent of Rewards members gave a birth year before the field was dropped. The inventory keeps it out of the model but flags it for audit use, anticipating the bias review later in the term.
Records the chain does not hold
Vaccine clinic histories sit with a veterinary partner under a separate agreement. Listing them anyway prevents the common assumption that a retailer can draw on everything that happens inside its stores.
Signal the model can do without
Location pings, chat transcripts and the broker file are marked hold. The notes argue that order history, schedule edits and pet profiles likely carry most of the signal, so the questions blocking the other three need not delay a test.
Where marks go in MT362 Unit 3
Inventories that list systems rather than data are the recurring weakness in this MT362 unit; naming the email platform says little about which fields it holds or how they got there. The collection column is where the grade is decided. A row that records how a field arrived, typed by the customer, observed at checkout or bought from a broker, allows the later privacy review to work, and a row that omits it forces guesswork. Assuming every in-store interaction belongs to the retailer is a slip when a partner holds the records. Quality problems stated honestly, such as unreliable open tracking or stale pet weights, count in the paper's favor. A hold with its blocking question named shows judgment, and a short list of data the model does not need often impresses more than the table itself.
Get a MT362 Unit 3 example written to your instructions
Whatever business your Unit 3 prompt assigns, list the kinds of customer records it seems to hold, even roughly, and add the prompt and rubric. A custom inventory sorted by how each record was gathered, with a verdict for every row, comes back in 24-48h, and the first one is on us.
MT362 Unit 3 questions, answered
How many data sources should the inventory include?
Enough to cover every place the proposed use might draw from, which for a mid-sized retailer is often ten to fifteen. Graders care less about the count than about completeness for the use case and the detail in each row. A short inventory that records collection method, notice and quality for each source usually outscores a long list of system names.
What if I do not know how the data was collected?
Say so in the row and mark it as a question to resolve. An honest unknown is useful, since it tells the later privacy review exactly where to look. Where the case gives hints, such as a loyalty sign-up form or a purchased list, describe the likely method and label it as inferred rather than confirmed.
Should the inventory include data the business does not own?
Include it when people might assume the business holds it, and mark who actually does. Partner records, platform data the business can only view, and vendor-held files are common examples. Listing them with a clear owner prevents a later section of the proposal from relying on information the business has no right or means to use.