A finished BU 455 Unit 6 governance and retention plan: each data category given a holding period, a named role for access, and somebody accountable for its deletion. Searches like "bu 455 unit 6 assignment example", "bu455 unit 6 sample" and "bu 455 unit 6 example" land here.
What a finished BU 455 Unit 6 governance and retention plan looks like
The plan is a set of tables with short arguments between them, and the tables carry the credit. A catalog comes first, listing the categories of data the case holds, what each contains, where it arrives from, and which of them identify a person. A retention table follows, giving every category a holding period, the reason behind that period, the event that starts the clock, and the role responsible for removing the records once it expires. An access table names roles rather than individuals, recording what each role may read, who approves an exception, and where that approval is written down. A closing lineage section takes one figure a decision maker relies on and traces the path back to the records underneath it.
How a BU 455 Unit 6 example is structured
The catalog precedes every rule because a rule written over an inventory nobody took applies to nothing in particular, and plans that read as generic almost always skipped this table. Retention follows the catalog so each period attaches to a named category instead of to the data at large, which is what makes the rule something a person can actually carry out. The event that starts the clock sits beside the period, since a rule saying seven years without saying seven years from what cannot be carried out by whoever holds the delete key. Access is written as roles because individuals change jobs and a document naming people is stale inside a term. Lineage closes the plan, worked for one figure rather than claimed for all of them, as a single traced path is evidence while a general assurance is decoration.
A catalog before any rule
The plan lists what data exists first, since a rule written over an inventory nobody took governs nothing in particular.
Periods attached to named categories
Each holding period belongs to one listed category rather than to the data at large, which separates a plan from a statement of intent.
The clock-starting event written down
A period means nothing until the plan says what starts it, because the person running the deletion needs a date to compute.
Access written as roles, not names
Naming positions keeps the plan usable after somebody changes jobs and forces a decision about what the role needs rather than who is trusted.
One figure traced to its records
Lineage is worked end to end for a single number somebody relies on, since one traced path is evidence and a broad assurance is not.
Obligations cited with a date
Where the case names a legal or contractual requirement, the plan points at the source rather than presenting a period as settled fact.
Where marks go in BU 455 Unit 6
Governance plans lose points by staying abstract. Paragraphs on the importance of stewardship, with no category listed and no period assigned, describe a value instead of deciding anything. Retention rules carrying a duration but no starting event cannot be executed by the person who has to perform the deletion. Plans naming individuals rather than roles are stale the moment somebody transfers. Access sections that grant everything to anyone with a business need have written a sentence rather than a rule. Legal retention requirements asserted as settled, carrying neither a citation nor a checking date, are the first lines an instructor from a compliance background will test. Lineage described as a capability rather than traced for one figure demonstrates nothing. The retention schedule your employer operates under is that organization's material and reflects its counsel's advice.
Get a BU 455 Unit 6 example written to your instructions
Copy the Unit 6 instructions and the BU 455 rubric out of your classroom, with whatever case or data inventory the assignment supplies. The custom example catalogs the data before writing any rule, gives each category a period and a starting event, writes access as roles, and traces one figure end to end. First custom sample free, returned in 24 to 48 hours.
BU 455 Unit 6 questions, answered
How long should I say each category is held?
Take the period from the case, from a source you cite with its date, or from a business reason you state, and make clear which of the three you used. Durations appearing with no origin are the commonest weakness in these plans. Where the assignment expects a legal minimum, name the requirement you are relying on instead of quoting a number from memory, since these differ by jurisdiction and are revised.
Does the plan need a lineage diagram?
The instructions decide, and a traced path set out in a table often reads better than a drawing. The criterion wants one figure followed the whole way back: the report it appears in, the job that computed it, the stored records that job read, and where those records originally arrived from. A diagram covering everything at once usually shows less than a single path followed properly.
Can I use my company's retention schedule as the model?
Leave it out of the document. A retention schedule reflects legal advice the organization paid for, contracts it signed and decisions about its own risk, which is why such schedules are commonly marked confidential. Build the plan from the case and cite public sources for anything legal. Recognizing that a period is useless without an event to start it is the transferable part, and that stays with you.