3.5 A deliverable-based timeline
| Work package | Depends on | Evidence of completion | Typical review |
|---|---|---|---|
| Project framing | Organizational context | Agreed problem statement and scope | Project sponsor or decision owner |
| Data dictionary | Data access and source context | Reviewed variable definitions | Data lead and subject expert |
| EDA | Dictionary and initial cleaning | Reproducible findings and issue log | Full analytical team |
| Secondary research | Defined information needs | Source log and integrated evidence | Research lead and analyst |
| Main analysis | EDA and analytical plan | Validated results and limitations | Technical reviewer |
| Projections | Assumptions and baseline data | Auditable model and scenarios | Team and decision owner |
| Recommendations | Stable findings | Evidence-linked actions and measures | Team and stakeholder review |
| Final communication | Reviewed conclusions | Report, presentation, and handoff | Full team |
The table is a starting structure rather than a universal sequence. Some research can begin while the dictionary is being created. Data quality and modelling may require several loops. The important point is that every major deliverable has a visible basis and a planned review.