E101 Applied Professional Experience, catalog number PJMG 3810, is the three-competency-unit course where WGU stops asking whether you know how project artifacts work and starts asking whether you can produce them and explain them to somebody who was not there. Two things are scored and they pull in different directions. The artifacts themselves have to be technically sound. The communication around them has to be intelligible to a reader without your context. Students who are strong at one are frequently weak at the other, and the course is designed to find that out.
What PJMG 3810 is actually testing
An applied experience course is built on the idea that producing a document under real conditions teaches something that reading about the document cannot. The conditions are the point: incomplete information, a stakeholder who changes their mind, a resource who is only available on Thursdays. Artifacts produced against clean inputs are exercises. Artifacts produced against messy inputs are experience, and the write-up is where you show which one you had.
The communication half is scored harder than students expect. A charter, a schedule and a register are all internal documents whose meaning is obvious to their author and opaque to everyone else. Communicating them means saying what decision each artifact supports, what it assumes, and what a reader should do with it. A submission that presents artifacts with captions has not communicated them. A submission that walks a reader through why the schedule looks the way it does, what the constraint was, and what would have to change to compress it has.
Underneath both halves sits professional judgment about disclosure. Applied experience work often touches real organizations, real budgets and real people. Deciding what to anonymize, what to generalize and what to leave out entirely is part of the professional skill being assessed, and handling it explicitly in the document reads far better than handling it silently.
Turning the rubric into an artifact plan
Scoring detail sits inside your Course of Study rather than in the catalog. Read it before you decide which artifacts to produce, because in an applied course the rubric usually tells you what has to exist. Each aspect is scored independently against a three-point scale and a 2 in each aspect passes the task, so an artifact set that is strong in five areas and missing one comes back for the one.
Where the course is assessed by performance assessment, treat the rubric as a checklist twice: once for what must be produced and once for what must be said about it. Those are usually different aspects, and producing an artifact without discussing it leaves half the score unclaimed.
The word budget, worked. Assume six scored aspects and directions calling for roughly 1,900 words of narrative alongside the artifacts themselves. Take 150 for context on the project and the conditions you worked under, and 130 for a closing on what you would do differently. That leaves about 1,620 across six aspects, or 270 each. Then shift weight toward the aspects that ask you to explain rather than to produce, since explanation is where thin submissions lose points: give those 380 and pull the difference from the aspects the artifacts themselves largely answer.
Do not let the narrative describe what the artifact already shows. If the reader can see the dependency table, the paragraph beside it should explain why those dependencies exist, not list them again in sentences.
A structure that fits an applied experience submission
Follow your task directions on required components and format. Where the arrangement is yours, this order lets a reader who was not present follow the work.
| Section | What belongs in it | How it tends to be scored |
|---|---|---|
| Context | The organization or scenario, the project, and the conditions you worked under | Enables everything else; without it artifacts float free of any situation |
| Artifacts | The documents the rubric calls for, complete and internally consistent | Scored for technical soundness and for agreement with each other |
| Rationale | Why each artifact takes the form it does, given the constraints | The aspect most often thin; artifacts alone do not answer it |
| Communication | How each artifact would be presented to its intended audience | Scored for audience awareness, not for design polish |
| Constraints and adaptations | What went differently from plan and how you responded | Where applied experience distinguishes itself from a classroom exercise |
| Reflection | What you learned, stated as changed practice rather than as feeling | Scored for insight; a summary of activities earns nothing |
Keep the artifacts and their explanations adjacent rather than putting all artifacts in an appendix. An evaluator reading an aspect about rationale should not have to flip to the back to see what is being rationalized.
Evidence craft in applied work
Applied courses shift the evidence question from literature to documentation. Your evidence is largely what you produced and what you can show about the conditions you produced it under.
- Date and version your artifacts. Applied work changes over time, and showing an early and a revised version is stronger evidence of experience than showing only the final one.
- Record the constraint that shaped each decision. A schedule compressed because a resource left is a much better artifact story than a schedule that simply exists.
- Anonymize deliberately and say so. Replacing a company name with a descriptor and stating that you have done so is professional. Silently inventing details is not.
- Cite standards where you followed them, in APA, wherever the rubric asks for citation.
- Distinguish what you did from what the team did. Applied experience aspects are about your contribution, and vague collective phrasing obscures it.
- Keep quoted organizational material minimal and attributed. WGU scans submissions for authenticity.
The strongest applied submissions include one artifact that did not work. Showing a plan that had to be rebuilt, with the reason, demonstrates more command than six artifacts that all went smoothly.
What separates Competent from a returned applied task
Everything resolves to Competent or Not Competent, with no letter grades and no ordinary grade point average. Performance assessment work can be revised and resubmitted with no grade penalty, so a return is a delay in a six-month flat-rate term rather than a mark on record.
Applied submissions that pass on the first read tend to have:
- Every artifact the rubric names, present and complete rather than sketched.
- Consistency across artifacts, with the same names, numbers and dates used throughout.
- A rationale for each artifact that goes beyond restating its contents.
- Audience identified for every communication decision.
- At least one genuine constraint described, with the adaptation it forced.
- Reflection framed as what you would now do differently rather than what you enjoyed.
Where an objective assessment forms part of this course in your plan, the boundary is absolute. Proctored exams are yours to sit. We prepare with study plans, drilled terminology and practice questions, and give an honest readiness verdict. We do not sit assessments and we never ask for portal credentials.
Six mistakes that cost time in E101
- Submitting artifacts without explanation. Production and communication are usually separate aspects, and only one of them is answered by the artifact.
- Narrating what the artifact already shows. Restating a table in prose consumes your word budget and earns nothing.
- Sanitizing the experience. An account where nothing went wrong reads as a classroom exercise rather than applied work.
- Blurring your contribution into the team's. Aspects assess what you did, and collective phrasing makes that unassessable.
- Inconsistent details across artifacts. A date in the charter that contradicts the schedule undermines both documents at once.
- Reflection as feelings. Insight means a changed decision rule, not a statement that the experience was valuable.
How support works on this course
Applied courses are the easiest place to lose points for something that has nothing to do with your competence, because artifacts you understand perfectly can be unreadable to someone who was not there. Send the rubric from your Course of Study, the task directions and your artifact drafts. The work comes back with each artifact checked for internal consistency and against the others, rationale written where the draft only had output, audience named for every communication decision, and reflection rewritten as changed practice.
Everything you produce here is portfolio material as well as coursework, so the version that satisfies an evaluator is usually also the version worth keeping for an interview. That is worth some deliberate effort while the material is in front of you. A charter you can hand to a hiring manager, with a paragraph explaining the constraint it was written under, does more in a conversation than a line on a resume claiming project experience. Build it once at that standard and the course and the portfolio close together.
Questions students ask about E101
Is E101 the same course as PJMG 3810?
Does E101 require a workplace project?
How much detail about my employer can I include?
Artifacts done but the write-up thin?
Send the rubric, the task directions and your drafts. You get consistency checks across artifacts, rationale written where output stands alone, and reflection reframed as changed practice.
Where E101 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.