E068 Ethical Engineering, catalog number HUMN 1120, is the three-CU course covering ethical, professional and societal responsibilities in engineering practice, professional codes of ethics, and ethical decision-making frameworks. What separates it from a general ethics course is the presence of codes. Engineering has written professional obligations, and in this course they function as authority you can cite rather than as background.
Professional codes change how the argument works
In a general ethics course you reason from principles to a conclusion. In engineering ethics you also have a document that already states what the profession expects, and a strong answer uses it. That shifts the writing in a specific way: instead of arguing that safety should be prioritised, you cite the obligation that says so and then argue about how it applies to the facts in front of you.
The obligations that recur across engineering codes are worth knowing as a group. Public safety, health and welfare are held above obligations to a client or an employer. Engineers work only in areas of their competence. Statements made publicly are to be objective and truthful. Conflicts of interest are disclosed rather than managed quietly. Credit is given where work was done by others.
Those are not slogans, they are decision rules, and most engineering cases turn on the first one colliding with a commercial pressure. Recognising that structure quickly is what makes case analysis fast.
The safety obligation is the hinge of most cases
Almost every case worth analysing in this course has the same shape underneath. An engineer holds information about a risk. Someone above them, or a schedule, or a budget, wants a decision that does not reflect that information. The question is what the engineer is obliged to do and to whom.
The productive analysis works through four steps. What is known, and how confident is the knowledge. Who bears the risk, and did they choose it. What has already been tried inside the organisation, since escalation usually comes before external disclosure. And what the code actually requires, as opposed to what would be brave.
That fourth step keeps the analysis honest in both directions. Codes rarely require dramatic action as a first move, and an answer that jumps to going public without addressing internal escalation has skipped the part professionals are actually expected to do. Equally, an answer that stops at raising a concern and being overruled has not engaged with what the obligation to public safety means when the concern is dismissed.
Turning scored aspects into a case-analysis plan
Open your Course of Study before drafting, since the public catalog gives competencies and the rubric lives inside the course. Count the scored aspects. Each is judged on its own three-point scale, a score of 2 in each passes the task, and nothing averages, so a strong code discussion will not carry a weak stakeholder section.
Engineering ethics rubrics typically ask for a described situation, an identified obligation or conflict, an applied framework, a consideration of consequences to parties beyond the client, and a decision. Write each under its own heading. The aspect most often lost is the one about societal responsibility, because students answer it inside the stakeholder discussion and never give it a visible home.
A worked word budget. Suppose six scored aspects and directions asking for roughly 1,800 words. Take 130 for an opening and 130 for a close, leaving 1,540 across six aspects, or about 255 each. Then reweight: the aspect applying a code or framework takes 400, drawn from the situation description at 130, because description is finished when it is accurate. If a separate aspect covers professional responsibility, protect at least 250 words for it rather than letting it be absorbed.
A structure for an engineering ethics case
Where directions set a format, follow it exactly. Otherwise this order maps onto how engineering cases are usually scored.
| Section | Contents | What earns the aspect |
|---|---|---|
| Technical situation | The system, the risk and what is actually known about it | Technical accuracy, since a wrong account invalidates the analysis |
| Roles and duties | Who holds which professional role, and what each owes to whom | Duties named as obligations rather than as job descriptions |
| Code provisions | The specific provisions engaged, quoted or paraphrased with citation | Provisions applied to these facts, not listed |
| Conflict | The collision between obligations, stated as a genuine tension | Both sides given real weight |
| Options | Realistic courses of action, including internal escalation | Options a working engineer could actually take, in order |
| Societal impact | Effects on parties outside the contract, including future users | Named parties and named harms, not general public interest |
| Decision | The recommended action, its justification and its cost | A decision with a cost the writer acknowledges |
The options row is the one that separates competent case analysis from student essays. Real engineering ethics is sequential: raise it, document it, escalate it, and only then consider steps outside the organisation. Presenting the sequence shows understanding of practice as well as of principle.
Evidence craft for professional ethics writing
- Cite code provisions precisely, by the section that states the obligation, so a reader can check that it says what you claim.
- Keep technical claims separate from ethical ones. A statement about a failure mode is a technical claim and needs technical support.
- Where a real incident is used, source the facts and be careful with contested details. Well-known engineering failures have disputed accounts and using a simplified version undermines the analysis.
- Do not treat compliance with regulation as the end of the question. Meeting a standard is a floor, and codes frequently require more.
- Name uncertainty in the technical picture. Ethical obligations under uncertainty are different from obligations under known risk, and saying which situation you are in changes the whole answer.
- Attribute frameworks by their standard formulation rather than paraphrasing from memory.
One habit strengthens these papers noticeably: state what the engineer in the case did not know at the time. Analysis written with hindsight is easy and unpersuasive. Reconstructing the decision from the information actually available is harder and it is what professional judgment means.
What Competent looks like in E068
WGU records outcomes as Competent or Not Competent, without letter grades or an ordinary grade point average. Performance assessment work can be revised and resubmitted with no penalty for the earlier version, so a return costs queue time and rework inside a six-month flat-rate term.
Engineering ethics work that passes on the first read tends to show:
- A technically accurate account of the situation before any judgment.
- Specific code provisions cited and applied rather than listed.
- A conflict presented with both obligations given genuine weight.
- A realistic sequence of options including internal escalation.
- Societal impact addressed under its own heading with named parties.
Where a proctored objective assessment forms part of the course, the boundary holds. Proctored assessments are yours to sit. We prepare with code drills, worked cases and timed practice, and we give an honest readiness read. We do not sit or assist during an assessment and we never ask for portal credentials.
Six mistakes that cost time in E068
- Ignoring the codes. They are the authority this subject supplies, and an analysis that never cites one is doing general ethics in an engineering setting.
- Jumping straight to disclosure outside the organisation. Professional practice expects escalation first, and skipping it reads as unfamiliarity with how the obligation works.
- Writing with hindsight. Knowing the outcome makes the decision look obvious and removes the reasoning being assessed.
- Confusing legal compliance with professional obligation. Codes routinely require more than regulation does, and that gap is often the point of the case.
- Treating the client as the only stakeholder. The public safety obligation exists precisely because the paying party is not the only party at risk.
- Recommending an action with no cost. Every real option in these cases costs something, and naming the cost is what makes the recommendation credible.
How support works on this course
Send the rubric from your Course of Study and the task directions. What comes back is aspect-mapped: a model case analysis with code provisions cited and applied, a sequence of realistic options, societal impact given its own section with named parties, and a decision with a stated cost, plus a walkthrough of the reasoning so the pattern transfers to later professional practice courses.
Terms at WGU run six months at a flat rate, so what lowers your cost per course is how many you close inside a term. Engineering ethics is a course where preparation compounds: knowing the recurring code obligations well enough to recognise which is engaged turns a multi-day writing task into a one-day one.
Questions students ask about E068
Is E068 the same as HUMN 1120?
Which code of ethics should I use?
How is E068 different from the technology ethics courses?
Engineering case due and the code is doing none of the work?
Send the rubric and directions. You get a model case analysis with provisions cited and applied, a realistic option sequence, and a decision with a stated cost.
Where E068 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.