D100 Introduction to Spreadsheets is BUS 2140 in the WGU catalog and carries a single competency unit, building proficiency in spreadsheet development and analysis for business applications. It is the smallest course most business students will meet, and it has an unusual scoring property: the deliverable is often a file rather than an essay, and a file is checked by opening it. If a performance assessment carries your version, each aspect still needs its own score of 2. D100 and BUS 2140 are the same course.
What D100 builds toward
Spreadsheets are the default analytical tool of business, and most people learn them by accident, which produces workbooks that give correct answers by methods nobody can follow. The course exists to replace accident with method: cells that reference rather than repeat, formulas that survive a changed input, sheets organized so a reader knows where the data ends and the calculation begins.
One competency unit means the scope is deliberately narrow. You are not expected to build a model; you are expected to demonstrate that you can construct a working sheet properly. Business plans that carry the broader treatment list D388 Fundamentals of Spreadsheets and Data Presentations instead or as well, and the analytical use of the same tool continues in D466 Analyzing and Visualizing Data. Check your Degree Plan for which of these your program actually lists.
Planning when the deliverable is a file
WGU does not publish assessment types or task requirements in the catalog; those sit in the Course of Study inside your portal. If a performance assessment carries your version and the deliverable is a workbook, the planning unit is not words at all. It is cells, sheets and named requirements, and the budget that matters is time.
A worked example. Suppose the rubric holds five scored aspects and the deliverable is a workbook with a short explanatory note. Convert each aspect into a location before you build: aspect one becomes the input sheet, aspect two becomes a set of named formulas in specific columns, aspect three becomes a summary block, aspect four becomes a chart, aspect five becomes the note. Then estimate time rather than length: allow roughly 45 minutes per aspect for building and checking, which is under four hours in total, plus an hour to verify. If the explanatory note is also scored, give it about 120 words per aspect it covers, so a note serving three aspects runs near 360 words. The value of that plan is that it turns a vague small task into five checkable pieces of work.
How to lay a workbook out so it can be scored
| Sheet or block | What lives there | Why it matters to an evaluator |
|---|---|---|
| Inputs | Every raw value and assumption, entered once | Makes the model changeable and the assumptions visible |
| Calculations | Formulas referencing the input cells, never retyped values | Demonstrates method rather than result |
| Summary | The answers the task asked for, clearly labeled | Lets the reader find the deliverable without hunting |
| Chart | One chart that answers a stated question | Chart type appropriate to the data is frequently its own aspect |
| Documentation | A short note on structure and any assumptions | Turns a file into something a colleague could inherit |
| Formatting | Consistent number formats, headers, and labeled units | Presentation aspects are real aspects in business tooling courses |
What counts as evidence in a workbook
In a spreadsheet task the formula is the evidence. A cell containing a typed number where a calculation was expected demonstrates nothing, even when the number is right, and it is the fastest way to lose an aspect. Build every derived value as a reference to something else, so that changing an input changes the answer.
Two habits make the evidence legible. Keep inputs in one place and refer to them, rather than embedding constants inside formulas where a reader cannot see them. And label everything: a column headed cost is ambiguous, while unit cost in dollars is not. Where your task provides a starter file or template, use it as given and do not restructure it, since aspects are frequently tied to specific locations. Anything you submit is scanned through WGU's Similarity Checker where applicable, and shared workbooks circulate widely, so build yours from the task's own data.
What passes in a one-CU tooling course
WGU records Competent or Not Competent, keeps no letter grades and no GPA, and requires a 2 in each aspect. Spreadsheet tasks return for a short list of reasons: hardcoded values where formulas were required, a chart type that does not suit the data, missing labels, a file saved in the wrong format, or a requirement met on the wrong sheet.
Every one of those is caught by a five minute check before submission. Change one input value and confirm that everything downstream updates. Read each chart and ask what question it answers. Confirm the file format matches what the task specified. And walk the rubric aspect by aspect, pointing at the cell or sheet that satisfies each one. Where a task does return, comments name the aspects and resubmission carries no penalty at WGU.
Six mistakes that cost time in D100
- Typed results instead of formulas. The single most common failure in spreadsheet tasks, and instantly visible to anyone who clicks a cell.
- Constants buried in formulas. A tax rate typed inside a calculation cannot be found or changed, and it hides an assumption.
- Chart type mismatched to data. Trends over time want a line, part-to-whole wants care, and category comparison wants bars.
- Unlabeled axes and units. A chart that does not say what it measures fails a presentation aspect on its own.
- Restructuring a provided template. Tidier is not better when aspects are tied to given locations.
- Wrong file format on submission. Correct content in the wrong container is a returned task, and it is entirely avoidable.
One CU, one workbook, done properly
Send the rubric and any starter file. The model workbook comes back with live formulas, labeled inputs and a note explaining the structure so you can defend it.
The handful of functions that cover most business tasks
Spreadsheet learning feels endless because the function list is enormous, and the useful subset for business coursework is small. Five families cover the great majority of what any introductory task asks for.
Aggregation is the first: summing, averaging, counting and finding maxima and minima across a range. Conditional aggregation is the second and the one that separates casual users from competent ones, meaning summing or counting only the rows that meet a criterion, which is how almost every business question about a category gets answered. Lookup is the third, matching a value in one table against a table elsewhere, which is how two data sets become one. Logic is the fourth, testing a condition and returning different results, which is how rules such as discount thresholds and commission tiers get encoded. And date arithmetic is the fifth, since business data is nearly always organized by period.
If those five are solid, an introductory task holds no surprises. The efficient way to acquire them is not to watch a course through; it is to take a small data set and answer five questions with it, one per family, then check each answer by hand. Two hours spent that way is worth more than a week of passive reading, and it produces exactly the fluency a one-CU course is testing.
Three questions D100 students ask
Does it matter which spreadsheet program I use?
Is one competency unit really worth a whole task?
How does support work on a file-based task?
One CU and the flat-rate term
WGU terms run six months at a flat rate regardless of how many courses close inside them, which makes very small courses a specific kind of opportunity. A one-CU course cleared in an afternoon costs almost nothing and still counts toward the unit total that keeps you on track. The mistake is treating small courses as filler to be done last, since they then collide with a term boundary alongside everything else. Bank them first. The progress guide covers how unit counts are tracked.
Where D100 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.