Spreadsheet-ready CSV versions

These files are the same artefacts as the Markdown templates next door, expressed as comma-separated values so they can be opened directly in a spreadsheet, imported into a project tool, or diffed in Git. They are deliberately plain: no formulas, no formatting, no macros.

Which version should I use?

Use the Markdown template when the artefact will live in the repository and be reviewed as text. Use the CSV when you need to sort, filter, or chart the data — resource levelling and earned value work are far easier in a spreadsheet. Keep one authoritative copy: if you maintain both, they will disagree.

Conventions

Convention	Rule	Why
Encoding	UTF-8	Names and currency symbols survive
Header row	Always present, first row	Import tools detect columns from it
Delimiter	Comma; quote any field containing a comma	Standard, and quoted fields survive Excel
Dates	ISO 8601 (YYYY-MM-DD)	Sortable, unambiguous between locales
IDs	Stable and never reused (R-01, FR-01, D-014)	References outlive the items they name
Currency	One currency per file, named in the currency column or the README	Mixed units make totals meaningless
Blank cells	Use an empty cell, not - or TBD	Distinguishes "not applicable" from "not yet recorded"
Durations	Working days, in a column labelled duration_days	Calendar days and working days are the classic error
Estimates	Add estimate_basis and, where used, estimate_low / estimate_high	A number without its basis cannot be challenged or reused
Personal data	Do not enter personal or sensitive data	These files are published in a public repository

Files

File	Markdown template	Use it for
stakeholder-register.csv	Stakeholder Register	Sorting by influence, filtering resistant stakeholders
requirements-traceability-matrix.csv	Requirements Traceability Matrix	Running the three traceability checks as filters
work-breakdown-structure.csv	Work Breakdown Structure	Rolling up estimates by deliverable
project-schedule.csv	Project Schedule	Forward and backward pass, float, critical path
resource-plan.csv	Resource Plan	Capacity against demand by period
product-backlog.csv	Product Backlog	Ordering and velocity calculations
risk-register.csv	Risk Register	Exposure sorting, residual exposure, ageing
defect-log.csv	Defect Log	Defect density, origin analysis, reopen rate
change-log.csv	Change Request	Cumulative scope and cost growth against the baseline
issue-log.csv	Issue Log	Ageing and blocked-work counts
decision-log.csv	Decision Log	Finding decisions and revisiting triggers
lessons-learned-register.csv	Lessons Learned Register	Tracking changes to practice to verification
project-dashboard.csv	Project Dashboard	Period-on-period trend charts

Each file contains its column headings and one illustrative row drawn from the worked example in the matching template. The data in those rows is invented for teaching — replace it with your own, and do not treat the figures as observations from a real project.

Limitations to be honest about

• No formulas are included. The arithmetic is documented in the templates and in tools/spm-calculators.py, so you can check your spreadsheet against a known example rather than trusting a hidden formula.
• A CSV cannot enforce anything. It will happily accept two accountable owners, a negative duration, or a date that precedes its predecessor. Validation is your job, and the self-check criteria in the labs tell you what to verify.
• Do not commit real personal data. The stakeholder register is the file where this is easiest to get wrong: record roles and engagement needs, not personal details.