Read the article
Decide the purpose first. A project clinic is practice, not marking. Teams explain their project to someone who has not seen it, hear the questions an interviewer might ask, and leave with one thing to improve. Say this plainly to students and to faculty, so that nobody treats it as an extra review.
Choose the timing. The best time is a few weeks before final reviews and campus drives, when the project is far enough along to explain but there is still time to change how it is presented. Avoid exam weeks.
Keep the format simple and equal. Twenty to thirty minutes per team is usually enough: five minutes for the team to explain, ten to fifteen for questions and feedback, and a few minutes to agree on one improvement. Give every team the same time, and run two or three rooms in parallel if there are many teams.
Ask each team to prepare a little. A two-minute explanation of the problem, their approach and the result, a short demo or a few screenshots, and a list of who did which part. Ask them not to bring a presentation of thirty slides.
Invite volunteers carefully. Working professionals in a related field, alumni and local business owners are good choices. Brief them before the day: they are there to ask honest questions and give useful feedback, not to judge. Share a short note on the kind of project each team is doing, and give them a few sample questions. If you do not know suitable volunteers, an organisation that arranges such sessions can help.
Prepare a simple note-taking sheet for each session with three boxes: what was clear, what was not, and one thing to improve before the review. Give a copy to each team afterwards, so the feedback survives the day.
Finally, follow up. Ask teams a week later what they changed. Ask volunteers what they noticed across teams, such as common gaps in explaining or testing, and share that with faculty. That is often where the department learns the most: it shows which skills to teach earlier in the year.