By the ProofCohort team. Questions or corrections? Contact our team.
Free editable text file (.md). Open it in any text editor or copy it into your document. No account needed.
What belongs in a project portfolio?
Choose work you can explain. For each project, include the original problem, your role, the output, and a way to inspect it. A short explanation of your decisions is more useful than a long list of tools without context.
How do I make a software project inspectable?
Add setup instructions, a working example, and meaningful checks to the repository. Link a live demo when appropriate. Explain any missing features or required configuration. Remove secrets and private user information before making files public.
How do I show design or analysis work?
Present the brief, your evidence or dataset, the method, and the final result. Separate measured findings from assumptions. Use permitted or public data and explain limitations so someone else can understand what the result does and does not establish.
What evidence fits each career area?
Choose evidence that lets someone inspect the skill you claim. These are illustrative formats, not a list of currently available programs or completed learner outcomes.
- Technology: a working demo or repository, setup instructions, test cases, and a technical decision you can explain.
- Design & Product: the problem, research or clearly labeled assumptions, alternative flows, a prototype, and observations from any tests you actually ran.
- Business & Growth: a sourced market or customer analysis, explicit assumptions, alternatives considered, and a recommendation with risks.
- Data & AI: a permitted dataset, preparation steps, a reproducible analysis or evaluation, a baseline, and errors or limitations.
- Marketing: an audience brief, message and channel choices, sample assets, and a measurement plan. Label unlaunched campaigns as concepts.
- Operations: a process map, responsibilities, an exception log, and a tested improvement proposal. Separate simulated checks from operational results.
Where does a credential fit?
Place the issued verification link next to the relevant project, where a reader can check it. The credential supports the work; the project itself shows what you can do. Keep the experience description consistent with the credential's issuer and completion criteria.
A project write-up you can reuse
Use six short sections: Problem; My contribution; Decisions; Evidence; Checks and feedback; Limitations. The downloadable template works in a document, portfolio page, or repository README. Keep the summary brief and link detailed artifacts beside each claim. State whether the project is independent practice, assessed learning, or authorized client work. Replace every placeholder before publishing.
Worked example: documenting a practice campaign
For a fictional community workshop, a marketing portfolio could show the audience assumptions, two message variants, an outreach calendar, and a measurement sheet. Explain why you chose each channel and show how you checked whether the message included the date, location, and intended audience. If the campaign was never launched, the honest outcome is a completed campaign proposal. Do not claim registrations, revenue, or conversion improvements. The same distinction applies to an untested design, a simulated operations change, or a model evaluated only on sample data.