How to write D224 Assessment 1: TIM2 activity log
A source-bound manual for the one D224 deliverable WGU publishes openly: Global and Population Health Time Log. It explains the verified requirements without inventing activities, hours, experiences, or a second task.
D224 Assessment 1 is the TIM2 Global and Population Health Time Log. WGU requires 35 real field-experience hours and directs submission through the Activity Log link on the Field Experience page—not the Performance Assessment link.
Verified identity and submission channel
The public WGU document names five competencies: foundations in population health and the nurse's role; social determinants of health; epidemiological data sources; global health trends; and evaluation of population-health interventions. The log is the evidence that the student completed qualifying activity across this competency territory.
Follow the live Field Experience page for the current form and workflow. The published rubric makes an unusual channel rule explicit: submit through the Activity Log link and do not use the ordinary Performance Assessment link. That is not a cosmetic instruction. A correct document sent through the wrong workflow can still fail to register as the required field-experience record.
The 35-hour gate
Thirty-five hours is a factual completion requirement, not a writing target. The student performs the hours, chooses truthful activity categories, records dates and durations accurately, and keeps any supporting evidence required by the live field-experience instructions. No tutor can manufacture, backfill, estimate, or sign those facts.
Plan the hours before writing narrative detail. Use a private tracker with date, start and end time, duration, sphere of care, activity, population or setting, competency connection, and evidence retained. Reconcile the duration column after every session. Waiting until the end invites arithmetic errors, duplicated time, vague memories, and descriptions that no longer show why an activity qualifies.
| Log field | What the student records | Quality check |
|---|---|---|
| Date and duration | The real activity date and time completed | Totals reconcile to 35 without overlap |
| Sphere of care | Wellness/disease prevention, regenerative/restorative care, or both | The choice fits what actually occurred |
| Activity | A concrete action rather than a broad topic | A reviewer can tell what the student did |
| Population link | The community, group, or system relevance | Individual care is not mislabeled as population work |
| Competency connection | Why the activity develops one or more published competencies | The explanation names a mechanism, not a keyword |
Use the five competencies as a coverage audit
Do not force every activity to mention all five competencies. Instead, audit the completed set for reasonable coverage. A source review may develop epidemiological-data judgment; a community-needs activity may expose social determinants; an intervention comparison may address environmental effects and population solutions. The connection should describe what the student learned or evaluated, not paste the competency wording after an unrelated activity.
Distinguish global, public, and population health accurately. Define the population and setting. When data is involved, name the source, measure, period, and denominator. When a trend is discussed, explain how it affects capacity or service decisions. When an intervention is evaluated, name the intended outcome, mechanism, implementation context, equity implication, and limitation.
Originality, privacy, and evidence
The rubric states that submissions must be original and caps direct quotation or close paraphrase at 30 percent combined and 10 percent from any one source, even when cited. A field log should rarely approach either ceiling. Describe the student's real activity in original language and cite only the external fact, framework, or data source needed to explain it.
Remove patient names, record numbers, exact addresses, employee identifiers, and any protected or proprietary details. The log can identify the kind of setting, population, or resource without exposing a person. If the live instructions require documentation or verification, follow that workflow exactly and retain records privately.
Write concise entries that still prove the connection
A strong entry can be brief when it answers four questions: what happened, what population-health issue it addressed, which competency it developed, and what the student learned or would do differently. Avoid inflated language. Field documentation is stronger when it is specific, restrained, and chronologically true.
Use verbs that describe the real action—reviewed, compared, mapped, observed, analyzed, discussed, developed, evaluated—then name the object. Follow with one sentence of population reasoning. Finish with an implication or limitation. Never claim implementation, patient contact, stakeholder agreement, or an outcome unless it actually occurred and can be documented.
Build each entry from the record, not from memory
Draft the factual spine first: date, duration, setting, action, and the population-health object of the work. Compare that spine with whatever contemporaneous evidence the live Field Experience page requires. Only then add the competency connection. This order keeps reflection from changing the underlying event and makes the hour total independently checkable.
Use one concise reasoning chain for the explanatory field: “I performed or observed X; it revealed Y about this population or system; that matters because Z; the limitation or next step is Q.” The wording is not a required template, but the logic prevents two common failures—an entry that is merely a diary note and an entry that copies competency language without showing what the activity contributed.
Audit the set in chronological order and again by competency. The chronological pass finds overlap, missing time, and inconsistent settings. The competency pass finds clusters and gaps. If a competency is weak, plan a future qualifying activity through the approved field-experience process; do not relabel a completed event after the fact. Preserve the private evidence trail, but place only the minimum de-identified detail required into material shared for tutoring or review.
Pre-submission audit
- The total equals 35 real hours, with no overlap or duplicate entry.
- Every activity fits one or both published spheres of care.
- Descriptions state what the student actually did, not what the topic generally means.
- The set demonstrates the five published competency areas without forced repetition.
- Data claims include source, period, measure, and denominator where relevant.
- No protected, identifying, proprietary, or fabricated information appears.
- Quoting and close paraphrase remain far below the published originality limits.
- The current Activity Log form and Field Experience submission link are used.
The non-negotiable boundary
The student completes the experience, chooses truthful categories, keeps supporting records, writes the first factual account, and makes the final submission. Tutoring may explain the public rubric, help build a forward-looking activity plan, check hour arithmetic, review de-identified wording, and point out a missing competency connection. It cannot supply hours, invent events, reconstruct undocumented activity, contact a site, obtain signatures, or submit the log.