Pipeline Reporting Practical (DOI)

Module 3 · Practical assignment

Brief and submission

Submit the report file and your written caveat.

Practical assignment ~180 minLesson 7 of 7
DOI-native

This is the part that can become evidence. The lessons record learning; the reviewed artefact is what moves a skill claim up the ladder.

Assignment brief

You are the operations hire at a fictional 40-person logistics company. The revenue lead asks for a weekly pipeline view every Monday at 08:00 and has told you they will read it on a phone.

What to hand in

  • A pipeline report file with a first screen that answers the five questions
  • A change log listing every cleaning decision you made
  • A one-paragraph caveat, at most 120 words, stating what the data cannot tell the reader and what you would fix first

What the reviewer looks for

  • The five questions are answered without the reader scrolling or asking
  • Every judgement word ('at risk', 'stalled') has a stated rule
  • Data-quality problems are visible rather than smoothed away
  • The change log is complete enough to reverse your work
  • The caveat names a concrete next action, not a general disclaimer

A shareable https:// link DOI reviewers can open (Google Docs/Drive, GitHub, Loom, portfolio). No passwords, secrets or client-confidential material. It goes to your Evidence Portfolio as candidate-submitted work for human review. Demo mode: kept on this device only.

Previous

Preview · Sample data — Demo course content authored by DOI for this prototype. Signed in, progress is saved to your DOI account; otherwise it stays on this device. Finishing lessons records learning; it does not prove competence — that comes from reviewed practical evidence and DOI assessment. DOI claims no accreditation for this course.