Skip to main content

Courses built around briefs, reviews, and handoffs

Each CourseFoundry track is designed like a studio sprint: you receive a brief with acceptance criteria, build in milestones, and ship a final package that reads like professional work. Choose a path below, then request the latest syllabus and cohort window.

Acceptance criteria included Structured critique loops Packaging and handoff standards

Cohort cadence

Weekly milestones and review windows are published up front. You can plan build time, revision time, and the final packaging step without guesswork.

Rubrics and QA

Each track uses explicit rubric criteria: clarity, craft, and handoff readiness. QA checklists keep revision cycles methodical rather than random.

Final packaging

You finish each project with a handoff package: naming conventions, version notes, exports, and a short rationale so the work is easy to review later.

Course tracks

Tracks share the same workflow backbone, but they emphasize different deliverables. If you are unsure which track fits your goal, request details and we will recommend a starting point based on the type of work you want to ship and the time you have each week.

Studio Foundations

A structured starting point for the habits that make studio work predictable: clear briefs, milestone planning, and repeatable review routines. You will learn a lightweight but strict system for constraints, acceptance criteria, and version history.

  • Duration: 4 weeks
  • Format: cohort-based with two critique windows per week
  • Practical work: 3 briefs, each with a packaging checklist

Typical assignments include: building a brief document, defining a rubric, running a self-review pass, and delivering a final “handoff folder” with notes.

Best first track

Portfolio Production

A deliverables-first track. You will build 4–6 portfolio artifacts with consistent structure: brief, iterations, final export, and rationale that holds up in a review meeting.

Duration: 6 weeks. Focus: iteration quality and packaging discipline.

Workflow Systems

Build a personal production system: file taxonomy, naming conventions, review templates, and a simple change log. The output is a kit you can reuse across future projects.

Duration: 5 weeks. Focus: repeatable systems and documentation.

Team Review Practice

A practice-heavy track for critique and decision-making. You will learn to run efficient review sessions, write rationale, and hand off work with fewer ambiguous “final_final” cycles.

  • Duration: 4 weeks
  • Format: guided critique sessions plus written review notes
  • Practical work: review scripts, rubrics, and meeting outcomes
Track contents change slightly between cohorts based on instructor feedback and new briefs. Request details to receive the current syllabus, a sample assignment, and a realistic weekly time plan.

What you will build

CourseFoundry is explicit about outputs because portfolio quality comes from the unglamorous details: constraints, review notes, and a final handoff that another person could pick up. Each track includes a set of briefs and a submission checklist. You will produce artifacts that show the work behind the work—decisions, revisions, and clarity.

Every project includes a brief with acceptance criteria, a milestone plan, and a rubric that guides critique. Iterations are logged so you can explain why changes were made. Final packaging covers file structure, naming, export settings, and a short rationale. That package is what makes an artifact readable in interviews and internal reviews.

Brief documents

A consistent brief format: scope, constraints, acceptance criteria, and review rubric. You will reuse this template after the course.

Iteration logs

Change notes and review feedback turned into a next-step checklist. This keeps revision cycles tight and auditable.

Handoff packages

A final deliverable bundle: structured folders, version labels, exports, and a short rationale. The aim is handoff readiness, not a single polished image.

A typical week, in one page

Every cohort follows the same cadence so expectations stay clear. You will always know what to submit, what “done” means, and how revisions should be tracked.

Brief + constraints
Scope, acceptance criteria, and the rubric for review.
Milestone submission
A checkpoint deliverable, not a last-minute final file.
Critique + next-step checklist
Annotated notes tied to rubric criteria and rationale.
Package for handoff
Exports, version labels, and a clean folder structure.
This overview is representative; the exact deliverables vary by track and cohort.
No inflated promises
Courses are educational and focused on workflow and deliverables. Outcomes vary based on time invested, revision cycles, and prior experience.

Request course details

Tell us which track you are considering and what you want to build. We will reply with the current syllabus, tool list (if applicable), the expected weekly time commitment, and the next cohort window. We do not sell your data.

What happens next

  • We review your request and confirm the best track to start with.
  • You receive the current syllabus and a sample assignment by email.
  • If timing works, we share the next cohort window and expectations.
Use the menu to choose a track

By submitting, you agree to our Privacy Policy.

Data use: we collect your contact details and message to respond to your request. Response time: typically within 1 business day.

Want the current syllabus for a specific track?

We will email the latest outline, tool requirements, and a sample assignment so you can evaluate the workload and the deliverables in a realistic way. No pop-ups, no aggressive sales flow—just the information you need.

Syllabus by email Sample brief included Clear privacy choices