PFIT Business - IT Management Portfolio Requirement is BUS 4891 in the WGU catalog and carries 3 competency units, an undergraduate business portfolio assessment for the IT Management degree. The four-character code is one of WGU's older formats and appears that way in Degree Plans, so PFIT and BUS 4891 are the same requirement. A portfolio is scored differently from an essay: artifacts are the exhibits and the writing around them is the argument, and an artifact with no argument attached proves nothing. Each rubric aspect needs its own 2.
What a portfolio requirement is actually asking
The premise of portfolio assessment is that competency is demonstrated by work rather than described in prose. Instead of writing about what you can do, you show something you produced and explain what it demonstrates. That sounds easier than an essay and is usually harder, because the burden shifts to selection and to argument.
Selection is the first skill: choosing artifacts that actually evidence the competencies the rubric names, rather than the artifacts you are proudest of. Argument is the second: writing the passage that connects an artifact to a competency, since an evaluator cannot be expected to infer what a document proves. The companion course in the degree is QFT1 Business - IT Management Capstone Project, and the technical background sits in the IT hub.
Mapping artifacts to aspects
WGU does not publish assessment types or task requirements in its catalog; the Course of Study inside your portal has yours. If a performance assessment carries this requirement, the planning method is a grid rather than an outline. Put the scored aspects down one side and your candidate artifacts across the top, and mark which artifact could evidence which aspect.
A worked example. Suppose eleven aspects and a written component of about 2,000 words. Reserve 150 for an introduction framing the portfolio and 80 for the close, leaving 1,770. Six aspects tied directly to artifacts take 200 each, giving 1,200. Three reflective aspects, covering what you learned or how you would work differently, take 140 each, giving 420. Two aspects on professional development or career direction take 75 each, giving 150. Sum: 1,200 plus 420 plus 150 equals 1,770. Then read the grid: any aspect with no artifact against it is your first problem to solve, and it is far cheaper to solve in week one than in week five.
The passage that makes an artifact count
| Element | What to write | Why it is needed |
|---|---|---|
| Artifact identification | What the item is, when it was produced, and for what purpose | Establishes authenticity and context |
| Your role | Exactly what you did, especially where the work was collaborative | Portfolios evidence your competency, not your team's |
| Competency claimed | The named competency this artifact evidences | Ties the exhibit to the rubric explicitly |
| The specific proof | Which part of the artifact demonstrates it, by section or page | Removes the inference an evaluator would otherwise have to make |
| Context and constraints | What made the work difficult or non-routine | Distinguishes competence from routine execution |
| Outcome | What the artifact produced in practice | Evidence that the work was real and had consequences |
| Reflection | What you would do differently now | Frequently its own scored aspect and easy to leave out |
Choosing artifacts that hold up
Three qualities make an artifact strong. It should be yours, with your contribution identifiable, since group deliverables need an explicit statement of what you personally produced. It should be substantive, meaning it required judgment rather than only effort. And it should be presentable, which usually means it can be anonymized without becoming meaningless.
Anonymization is the practical constraint most students hit. Workplace artifacts often contain client names, internal figures or system details that cannot be shared, and the answer is to redact identity while preserving structure. A project plan with organization names removed still demonstrates planning competence; a project plan with all its content removed does not. Where an artifact cannot be shared at all, build a comparable one that demonstrates the same competency and say plainly that it was produced for the portfolio. That is honest and acceptable; presenting a constructed artifact as workplace output is not, and submitted material passes through WGU's Similarity Checker.
What passes in a portfolio assessment
WGU records Competent or Not Competent, keeps no letter grades and no GPA, and each aspect needs its own 2. Portfolios return for two dominant reasons. Artifacts are included with insufficient explanation, so the evaluator is left to work out what each one demonstrates. Or the same artifact is used to evidence four different competencies, stretching a single piece of work past what it can carry.
Passing portfolios are explicit to the point of feeling repetitive. Every artifact has its own passage, every passage names the competency, and every claim points at a specific part of the artifact. They also spread the evidence, since several artifacts covering different competencies is stronger than one impressive item asked to prove everything. And the reflective sections are specific, naming what was learned and what would change, rather than expressing general satisfaction. Returned submissions come back with aspect-level comments and cost nothing to resubmit at WGU.
Six mistakes that cost time on a portfolio
- Artifacts with no argument. An included document that is never explained proves nothing to an evaluator.
- One artifact stretched across many competencies. Each claim gets thinner, and several aspects end up unsupported.
- Group work with no role statement. If your contribution is not identified, the competency is not evidenced.
- Over-redaction. An artifact stripped of all specifics loses the substance that made it evidence.
- Reflection written as satisfaction. Aspects asking what you would do differently want a specific change, not a positive summary.
- Leaving the grid until late. A missing artifact discovered in week five is a much bigger problem than one discovered in week one.
Portfolio with gaps in the grid
Send the rubric and your candidate artifacts. You get a coverage map against the aspects and model passages that make each artifact prove what it claims.
What to do about a competency you have no artifact for
Almost every portfolio has at least one gap, and the way students handle it decides how long the requirement takes. The unproductive response is to search harder through old work and eventually submit something adjacent, hoping the connection is obvious. It rarely is, and an artifact that nearly evidences a competency reads worse than one openly built for the purpose.
Three productive responses exist. The first is reframing: an artifact you dismissed may evidence the competency from a different angle, since a document produced for one reason often demonstrates several skills, and the passage you write around it decides which one it proves. Look at what you had to do to produce the artifact rather than at what it says. The second is construction: build something that demonstrates the competency, state clearly that it was produced for the portfolio, and treat it with the same rigour as workplace output. A well-built system evaluation, requirements document or analysis produced for this purpose is legitimate evidence when it is presented honestly. The third, where the requirement allows it, is documenting a process rather than a product, such as writing up how you approached a problem, what you considered and why you decided as you did.
What all three share is that the gap gets closed deliberately rather than papered over. Evaluators are considerably more forgiving of an artifact that says here is work I produced to demonstrate this competency than of one that quietly hopes a tangential document will pass. Close the grid early, and the rest of the requirement becomes writing rather than searching.
Three questions PFIT students ask
Can I use coursework from earlier in my degree?
How many artifacts should a portfolio contain?
What does support look like for a portfolio?
Three CUs and a flat-rate term
Portfolios have an unusual time profile: the writing is modest and the assembly is slow, because gathering, anonymizing and mapping artifacts happens in short bursts spread across days. That makes PFIT an ideal parallel course inside a six month flat-rate term, run alongside something that needs sustained concentration. Start the grid in week one and the requirement rarely needs a block of its own. The progress guide covers unit tracking across a term.
Where PFIT sits in WGU's programs
The July 2026 catalog places this code in 1 current WGU program. Open a program page for the complete standard path and term positions. The live Degree Plan remains authoritative after transfer credit, substitutions, and mentor planning.
The assessments, one by one
The public catalog does not publish this course's PA/OA identity or task count. WGU Tutors publishes at most one PA manual per course and only from a WGU-controlled public rubric. Until that source exists, PA help begins from the student's real Course of Study and OA support remains preparation only.