NYSC & Graduates
A CDS project can be genuine portfolio material — but only if it's documented properly. Here's how.
Last reviewed: 16 September 2026 · Reviewed by Paleon Training
Overview
A CDS project can be genuine portfolio material — but only if it's documented properly. Here's how.
The difference between a CDS project that helps your portfolio and one that doesn't is documentation, not the project itself.
Key takeaways
How to document it properly
The single most important habit is documenting as the project happens — photos, specific numbers or outcomes, notes on decisions made — rather than trying to reconstruct a compelling account from memory months later. A write-up framed around your specific contribution and the actual outcome ("I managed the social media presence for our CDS literacy drive, growing our page from X to Y followers over the CDS year") reads as a real portfolio piece; "participated in CDS activities" doesn't.
A simple problem/solution structure — what the CDS group needed, what you specifically did, what resulted — makes this genuinely readable to someone reviewing your portfolio cold. See Free Tools to Host Your Portfolio for where to publish this once written up.
Common questions
As it happens, not afterward -- photos, specific outcomes, and notes on decisions made are much harder to reconstruct accurately from memory months later.
Specificity about your actual contribution and the real outcome, structured around what was needed and what you did about it -- not a generic 'participated in CDS activities' line.
It works especially well for projects with a digital-skills angle (social media, basic design, content work), though the documentation principle applies to any project.
Sources & methodology
This guide reflects general good practice for documenting project work as portfolio material, applied specifically to the CDS context.
Continue reading
The main pillar guide.
Where to publish this once documented.
How CDS connects to skill-building more broadly.
Keep exploring