D494 Data and Information Governance, catalog number DTMG 3351, is a two competency unit School of Technology course about control. It establishes the rules of engagement, policies, procedures and data stewardship an organization needs to keep authority over its own data assets. Every other course in a data program teaches you to do something with data. This one asks who is allowed to, under what conditions, for how long, and who answers for it when the answer turns out to be nobody.
Governance documents are instruments, not essays
The single change that improves most submissions in this course is a change of genre. Students arrive expecting to write about governance and are actually being asked to write governance: documents an organization could adopt on a Monday and follow on a Tuesday. An essay explains a topic to a reader. An instrument tells a named role what to do in a named situation. The two read nothing alike, and the difference is visible in the first paragraph.
Four document types get confused constantly, and separating them cleanly is worth more than any other single habit here. A policy states what must be true and who is accountable for it, and it changes rarely. A standard fixes the measurable specifics that satisfy the policy, such as which classification levels exist. A procedure is the ordered steps a person follows to comply, written for the person who has to do it. A guideline is advisory and carries no obligation. Write a procedure where a policy belongs and the document ages out within months, because operational detail changes far faster than principle.
The test that catches almost everything is the Monday test. Take any rule you have written and ask whether a specific person could act on it without contacting you. If the answer requires interpretation, the rule is missing a piece: an owner, a trigger, a boundary, or a consequence. Rules that pass the Monday test tend to be short, which surprises students who expect governance writing to be long.
Stewardship is the part most often written as decoration. A data steward is not a title handed out at the end of a document, it is the answer to a question the organization will actually ask: who decides what this field means, who approves access to it, and who is accountable when its quality drops. Assign those decisions to roles rather than to individuals or to departments, because individuals leave and departments cannot be held to account.
Turning scored aspects into rules with word budgets
If your version of D494 is assessed by a performance assessment, the aspects your evaluator scores are the outline, and each one needs a score of 2 on its own for the task to pass. Governance aspects budget more predictably than most, because almost every one of them resolves to a rule or a role, and a rule that will not fit its allocation is usually two rules sharing a paragraph.
Worked example, from six aspects to a section plan. Say the rubric lists six scored aspects and the directions point at roughly 1,200 words. Reserve 100 words for a scope statement naming the organization, the data assets in scope and what is deliberately excluded, and 80 for a definitions block so that contested words are fixed before they are used. That leaves 1,020 across six aspects, or 170 each.
Now spend each 170 the same way, because governance rules have a fixed anatomy: about 40 words stating the rule itself, 45 naming the accountable role, 45 defining when the rule applies and to which classification of data, and 40 stating what happens when it is not followed. Any aspect that will not compress into that shape is carrying a second rule, and splitting it produces two clean sections instead of one muddy one.
The transferable idea: in governance writing, length is a symptom rather than a virtue. A section that keeps growing is telling you the rule underneath it has not been isolated yet, and evaluators reading for a specific scored aspect find isolated rules far faster than they find rules buried in exposition.
Shape for a governance deliverable
Where the work produces a policy, a stewardship framework or a governance plan for a described organization, these components cover what such a document has to contain. Follow the task directions wherever they name a format.
| Component | The question it answers | Share |
|---|---|---|
| Purpose and scope | Which data assets, which systems, which people, and what sits outside | 8 percent |
| Definitions | What the contested terms mean here, fixed before they are used | 7 percent |
| Roles and accountability | Who owns, who stewards, who approves, and who answers when something goes wrong | 16 percent |
| Classification scheme | How data is sorted into levels, and who assigns the level | 14 percent |
| Handling rules | What each level permits and forbids for access, storage, sharing and disposal | 17 percent |
| Lifecycle and retention | How long each category is kept, on what authority, and what ends it | 14 percent |
| Monitoring and enforcement | How compliance is observed, by whom, and what follows non-compliance | 13 percent |
| Exceptions and review | How to get a documented exception, and when the document itself is revisited | 11 percent |
The classification and handling components belong next to each other for a reason. Classification tiers only mean something if the handling rules differ between them, and a scheme with three levels that all receive identical treatment is a labelling exercise rather than governance.
Sourcing rules that constrain other people
Governance work cites two different kinds of authority and confusing them weakens the whole document. External authority tells you what the organization has no choice about. Internal authority is what the organization decided for itself. Both belong in the document, and each rule should make clear which it is.
- Cite the regulation, statute or published framework itself rather than a consultancy summary of it, and name the version or effective date, because obligations change and summaries lag.
- State the jurisdiction a requirement comes from. A rule that applies to residents of one region is not a rule about everyone in the organization.
- Separate the requirement from your implementation of it. The law may require deletion on request; the thirty day service window is your choice, and the reason for choosing it is scoreable.
- Where a recognised framework is used for structure, name it once and apply it consistently, rather than borrowing vocabulary from several at random.
- Paraphrase legal text instead of quoting long passages, with APA references, because submissions run through a similarity check and quoted regulation inflates the match rate for no analytic gain.
- Cite at the rule, not at the end of the section, so an evaluator scoring one aspect can see its authority without reading the whole document.
Where the task describes a fictional or generalised organization, the sourcing question becomes what you may reasonably assume. Assume openly. A sentence such as "this framework assumes a single jurisdiction of operation and no processing by external vendors" costs almost nothing and protects every rule downstream of it, because rules that would be wrong under different assumptions are only wrong when the assumption is hidden.
Enforceable, or sent back
Competent governance work is enforceable. Every rule has an accountable role, a trigger and a consequence. Classification levels produce different handling. Retention periods have an end and an authority behind them. Monitoring says who looks, at what, and how often. Exceptions have a path, which is what stops people quietly ignoring the whole document.
Returns cluster around aspiration. The policy says data will be managed responsibly, which no one can follow or breach. Accountability lands on a department rather than a role. The regulation is restated where a rule was wanted, so the document explains the law and governs nothing. Or retention is defined as a start date with no disposal, which is the failure the topic exists to prevent.
WGU records the result as Competent or Not Competent, with no letter grades and no ordinary grade point average, and the two competency units make this one of the lighter courses in the program. Terms are six months at a flat rate, so a two unit course cleared in the first weeks is a straightforward way to lower the effective cost of everything else in the term. Performance assessment work can be revised and resubmitted with no grade penalty. Where your course also carries an objective assessment, WGU objective assessments are proctored and our line is fixed: preparation only, with terminology drills, classification practice and a candid read on your preassessment result. We never sit an assessment, take no part during one, and never ask for or handle portal credentials.
Policy reading like an essay?
Send the D494 rubric and your draft. We convert exposition into numbered rules with owners, triggers and consequences, and return a plan with word targets.
Six mistakes that cost time in D494
- Writing procedures where policy belongs. Steps that name a specific system will be wrong within a year. Policy states the obligation; the procedure lives in its own document and changes freely.
- Accountability assigned to a department. A department cannot be called into a meeting. Name the role, and name only one per obligation, because shared accountability is the same as none.
- Classification tiers with identical handling. If confidential and internal data are stored, shared and destroyed the same way, the scheme is a colour code rather than a control.
- Reproducing the regulation as the policy. The law states the obligation. The policy states what this organization does about it, which is the part being scored.
- Retention with no disposal. A rule that says keep for seven years and stops is a hoarding policy. Say what triggers deletion, who performs it and how it is evidenced.
- No exception path. Every real organization meets a case the rules did not anticipate. Without a documented route to an approved exception, staff route around the whole framework instead.
Support on a policy deliverable
Send the rubric, the directions and the organizational scenario. The first pass is structural: we take whatever exposition exists and break it into numbered rules, each with an owner, a trigger, a scope of data and a consequence, then check that the classification scheme actually drives the handling section rather than sitting beside it. The second pass is authority, confirming that each external obligation cites the instrument it comes from and each internal choice is marked as a choice. The walkthrough runs the Monday test with you rule by rule, because that is the review an evaluator effectively performs.
D494 pairs naturally with the analytic courses that produce the data it governs, including D326 Advanced Data Management and D497 Data Wrangling, and it shares vocabulary with the security side of the program covered on our cybersecurity help page. At two competency units it is a sensible course to hold alongside a heavier one inside the same six month term.
Questions students ask about D494
Is D494 the same as DTMG 3351?
What is the difference between a policy and a procedure in this course?
Is data governance the same as data security?
Where D494 sits in WGU's programs
The July 2026 catalog places this code in 2 current WGU programs. Open a program page for the complete standard path and term positions. The live Degree Plan remains authoritative after transfer credit, substitutions, and mentor planning.
The assessments, one by one
The public catalog does not publish this course's PA/OA identity or task count. WGU Tutors publishes at most one PA manual per course and only from a WGU-controlled public rubric. Until that source exists, PA help begins from the student's real Course of Study and OA support remains preparation only.