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 counts as project evidence?
Start with the assigned task, then make your work inspectable. A repository should include instructions to run it. A live demo should show the required behavior. A design or analysis should include the brief, your reasoning, and the final output. Submit the evidence requested by your task instead of a certificate screenshot.
What should a useful submission explain?
Describe the problem, the work you personally completed, a decision you made, and how you checked the result. A campaign plan needs an audience, message, channel rationale, and measurement plan; a process improvement needs a current-state map, a proposed change, and a way to test it. A software task needs working behavior and checks. Identify unfinished requirements and separate proposed outcomes from measured results.
How does feedback affect completion?
Review the feedback and revise your work when changes are requested. A submitted task is not automatically a passed task. In the standard ProofCohort program flow, every weekly task must be reviewed or approved with at least 65% before the certificate bundle becomes available.
Does buying a certificate change my result?
No. The ₹499 program certificate bundle is available after the assessment requirements are met. Payment unlocks the eligible credential; it does not replace completing and passing the work.
What should I check before submitting?
Use this checklist for code, design, analysis, business, marketing, or operations work. The assigned task remains the source of the actual grading requirements; this is a preparation aid, not a new scoring rubric.
- Map each requested deliverable to a file, page, demo, or specific section. Mark anything missing.
- Open every shared link using the access a reviewer will have. Include viewing or setup instructions and the version you submitted.
- State your contribution, collaborators' contributions, sources, and any AI assistance required to be disclosed by your program.
- Record what you checked, the expected outcome, the observed outcome, and a limitation. A plan or forecast is not a measured result.
- Remove secrets and personal information that the reviewer does not need. Use authorized data and label synthetic data.
- After feedback, connect each requested change to the revised evidence. Keep the original and revised versions distinguishable.