Evidence, Portfolio & Mastery Tracking
Drive area: https://drive.google.com/drive/folders/1LZ_MpWzQX7RL0R0AXyuD_y4WQ1XCs3p9
Live Master Tracker
Open the CDMP Applied Lab & Technology Mastery Tracker
Important: The 00C 330-row execution checklist controls the learner’s current sequence/order. The Master Tracker here records competency, lab status, evidence, decisions, datasets, software setup and capstones. Its older 100-step execution tab is legacy/superseded.
Tracker tabs and their jobs
| Tab | Use it for |
|---|---|
| START HERE | Tracker orientation and links to the active 00C execution system. |
| LEGACY 100-STEP EXECUTION | Historical/superseded execution plan; do not use for current order. |
| TECHNOLOGY SKILLS | Track T0–T14 competency/readiness, practice evidence and gaps. |
| CHAPTER LABS | Record chapter-lab status, prerequisite state and completion. |
| LAB EVIDENCE | Index evidence produced by individual labs. |
| DEFECT CATALOG | Track Meridian defects, status, repair evidence and dependencies. |
| COMPANY DECISIONS | Record governance/architecture/master-data/quality/security decisions that later labs may inherit. |
| DATASET REGISTER | Record source/derived dataset identity, provenance, state and links. |
| SOFTWARE SETUP | Record required/optional software installation/readiness. |
| CROSS-CHAPTER CAPSTONES | Track CAP-01 through CAP-05 readiness and completion. |
| SOURCES | Index source/control documents used by the applied program. |
Evidence repository areas
- Evidence, Portfolio & Lab Journal: https://drive.google.com/drive/folders/1oEMLbxlXXVAZSrWP8bQXtN4dwAxNCPVS
- Templates, Registers & Trackers: https://drive.google.com/drive/folders/11vUvJAQMaEo_mQxHvWhEFH0XyA0gLUyq
- Generated technical outputs/evidence: https://drive.google.com/drive/folders/1ulXIrZ3cSdCcMDt-5Up57w66DeU0nukh
Minimum evidence rule
A completed applied lab should leave evidence sufficient to show:
- what the starting state/problem was;
- what the learner did or decided;
- what result changed or what evidence was discovered;
- how the result maps back to DMBOK concepts;
- whether the learner could reproduce/transfer the reasoning with reduced scaffolding.
Suggested evidence package
For each lab, preserve as applicable:
- source SQL/Python/DDL or management artifact;
- result output / before-and-after comparison;
- screenshots only as supporting evidence, not as the sole proof of logic;
- decision record and rationale;
- relevant diagram/map;
- DMBOK debrief;
- independent rebuild result;
- error/repair note;
- link back to the relevant 00A theory and 00C sequence.
Completion record
At minimum record:
| Field | Record |
|---|---|
| Lab ID / Chapter | Stable ID and chapter |
| Date | Completion date |
| Technology blocks | T# skills used |
| Scaffold level | Guided / Faded / Diagnostic / Independent |
| Evidence link | Drive/GitHub path |
| Independent rebuild | Pass / Partial / Fail + note |
| DMBOK debrief | Score/summary |
| Errors / repair | Actual learner mistakes and repair action |
| Next revisit | Date or trigger |
GitHub vs Drive
Use GitHub for searchable working notes, Markdown evidence explanations, SQL/Python source and cross-links. Use Drive for Google-native artifacts, spreadsheets, PDFs and larger evidence files where Drive remains the better source format.
The goal is one coherent evidence system—not duplicate uncontrolled copies.