Created by the First Role Skills Editorial Desk. This lesson uses a fictional workplace scenario and links to primary product documentation where the interface or feature matters.
Start with the work
A realistic scenario
You want to demonstrate spreadsheet judgment without exposing employer data. You will build a fictional two-week admin workload from scratch.
Avoid rework
Three beginner mistakes
Adding a dashboard before the source table works
Using color as the only status signal
Presenting a template without explaining decisions
The method
Complete it in six controlled steps
- 01
Define the workflow
Choose a believable scope: incoming requests, due dates, owners, priority, status, and next action. Keep the project small enough to explain in five minutes.
- 02
Create a tidy source table
Use one row per task and stable columns. Add fictional IDs, dates, request types, and owners. Do not use real employer, client, or applicant data.
- 03
Constrain entries
Use dropdown validation for Status and Priority. Include visible text labels so the tracker remains understandable without color.
- 04
Add useful logic
Create an overdue flag that ignores completed tasks. Add counts by status and owner. Test blank dates and tasks due today.
- 05
Design a restrained summary
Show three or four decisions: open work, overdue work, blocked tasks, and upcoming deadlines. Avoid decorative charts that do not answer a question.
- 06
Write the portfolio note
Explain the scenario, your role, the method, two design choices, how you tested it, and what you would improve with real user feedback.
See the difference
Before and after
A colorful sheet with merged headers, no validation, and tasks copied from a real company.
Fictional dataset, validated status fields, overdue logic, summary counts, accessibility note, and a one-page project explanation.
Original practice
Complete the exercise
Use the starter CSV to build the tracker. Add validation, one overdue formula, three summary counts, and a README sheet describing the fictional data and tests.
Use only fictional or fully anonymized data. Never upload an employer's confidential information to a portfolio.
Explain your decisions
Turn the exercise into credible evidence
Package the tracker with a one-page project note. Include the fictional scenario, fields you selected, the overdue rule, edge cases tested, and a screenshot of the restrained summary. State that the data is synthetic. A useful review demonstration is to add a new blocked task, change a due date, and show how the counts update. That proves the workbook behaves as a small system rather than a static colored template.
Quality gate
Check your own work
- Fictional data only
- One row per task
- Validated categories
- Edge cases tested
- Method explained