How a project becomes verified experience

Here is the full lifecycle, start to finish. Each role's collection has the detailed guide for its part.

The path

1. 1A project is set up inside a course, with an outcome, a timeline, and milestones. A professor creates it, or an organization posts it, a professor asks to run it in a course, and the organization accepts.
2. 2Students join the class and do the work, attaching deliverables to each milestone.
3. 3The professor reviews a deliverable and certifies it. That is the faculty verification signature, and if the course is connected to an LMS, it posts the grade to the gradebook at the same time.
4. 4The sponsor can sign off that the outcome was real and useful. That optional second signature makes the work fully verified.
5. 5Once the professor has verified it, the student chooses whether to publish it to their record, and can feature it on a public profile they control. Confidential projects stay off the public record.

Everything downstream of that, the verified record and the public profile, belongs to the student and outlives the course. If they leave the school or the sponsor closes, the verified evidence is still theirs.