A Formal Project is the only kind of work on MasarUX that a person reads and scores. Everything that can verify a Professional Competency comes from here.
Before you submit
- Read the Project brief and the review criteria together. The criteria are published before you start — a reviewer will score against exactly those, and nothing else.
- Check which fields the submission actually requires. A submission missing a required field cannot be sent, and finding that out at the end is avoidable.
- Make every link you include openable by someone who is not you. A reviewer who cannot open your file cannot score your work.
- Save a draft while you work. A draft is yours and is not visible to a reviewer.
- Submit when it is genuinely ready, then request a review.
What happens after you submit
Your submission joins a review queue. A reviewer reads it and scores each criterion on the published four-point scale, with written comments. The outcome, and what to do with it, is covered in the Human Review articles.
The final Project of a path
A path's final Project is the heaviest piece of work in it, and it is the one most closely tied to credential eligibility. It is worth reaching it with your earlier Projects already approved rather than still open, because the Competencies they verify are what the final stage is measured against.
Open this in MasarUX
Related articles
- How Human Review worksA reviewer scores each published criterion from 1 to 4 and returns one of three decisions.
- Reading your review and resubmittingHow to turn a needs-revision decision into an approved one without guessing at what changed.
- Portfolios and Case StudiesWork you add yourself, Case Studies built automatically from approved Projects, and what each one shows publicly.
Still need help?
If this did not answer your question, the FAQ covers the shortest answers and our support team reads every message.