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 a business posts it and a professor claims it into a course.
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 signs off that the outcome was real and useful. That is the second signature.
5. 5With both signatures, the deliverable becomes verified evidence on the student's record. The student can feature it on a public profile they control.

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.