Skip to content
HUDSON · TN FIELD GUIDE

How should a portfolio support the application?

Sources checked:

THE DIRECT ANSWER

Use lawfully shareable examples showing the applicant’s design contribution, with accurate project context. Keep the educational and experience records alongside it. The portfolio should illuminate the professional work rather than substitute for the specific credential path. Before assembling anything, decide what the portfolio is meant to prove. If the open question concerns the duty mix, a small set of annotated projects answers it. If the open question concerns the qualification path, no amount of imagery helps, and the transcript or the dated employment confirmations carry the file instead. Confusing the two produces a handsome submission that leaves the actual gap untouched.

Distinguish individual and team work

Explain which concepts, decisions or refinements belong to the applicant and which belong to colleagues. Obtain permission before sharing confidential prototypes. A clear factual account is preferable to implying sole authorship of a team’s entire product.

Ownership of the images is a decision in itself. Work made for a former employer usually belongs to that employer, so confirm in writing what may be shown and to whom before anything leaves your possession. Redacted or written summaries serve where a client will not release visuals, and an unauthorized disclosure creates a problem no immigration benefit offsets.

Where a project was collaborative, label the applicant’s contribution on the page carrying the image rather than in a covering note a reviewer may read separately.