Field notesAUWENSearch
Explore Systems
← tools

Office tools for operations

Use Excel, Word and PowerPoint to make reliable reports and usable runbooks.

3 lessons published · Updated 2026-09-14

Before you begin

Use a current desktop or web edition of Microsoft Office. Menu labels vary by edition. Work with the synthetic data below; no company exports are needed.

Working toward: Produce a checked inventory workbook, a usable maintenance runbook and a concise service-status briefing.

Read each explanation, run the example in your own lab, and attempt the exercise before opening its answer. Published lessons are ready to study; unfinished roadmap topics remain planned.

Validation: Based on upstream documentation. Platform-specific labs require the learner’s matching environment and are not execution-tested here.

1. Keep identifiers as text

A spreadsheet cell has a value and a display format. An identifier such as 0012 is not a quantity; importing it as a number can discard leading zeros. Format the ID column as Text before entering the fixture. Keep one header row and one record per row.

A1: Asset ID    B1: Role    C1: RAM GB
A2: 0012        B2: Web     C2: 8
A3: 0013        B3: Data    C3: 16
C4: =SUM(C2:C3)

What to expect

IDs retain four characters and the RAM total is 24. Do not count the total row as another asset.

Your turn

Why does changing an already-converted 12 cell to Text not recover the original 0012?

Show answer and reasoning
Formatting cannot reconstruct lost source characters. Reimport from the original with the correct column type or restore from a trusted source. Do not guess identifier lengths.

Watch for: CSV does not preserve workbook formatting or formulas as a native workbook does. Preserve the raw source and record import choices.

Link to this lesson

2. Write a runbook someone can follow

A runbook records a repeatable task and how to verify it. Use Word heading styles so navigation and a table of contents follow the document structure. Separate prerequisites, numbered actions, observations and rollback criteria.

Title: Lab web service health check
Owner and revision date
Prerequisites and target
1. Identify the host and service
2. Inspect status and logs
3. Check the test URL
Expected observations
Stop conditions and escalation
Evidence record

What to expect

A document with meaningful headings and numbered actions. Another person should be able to identify the intended target without asking the author.

Your turn

Replace the vague step “check that it works” with an observable criterion.

Show answer and reasoning
Example: request the lab /health endpoint, record the HTTP status and expected response, and confirm the application can read its synthetic fixture. Name the timeout and what happens on failure.

Watch for: Screenshots can supplement instructions, but they become stale and may be inaccessible. Keep essential commands and criteria as readable text.

Link to this lesson

3. Brief a decision with evidence

A status slide should let someone distinguish an observation from a hypothesis and an action. PowerPoint helps present that structure, but cannot make unsupported conclusions reliable. Use a clear title, readable labels and a source timestamp.

Title: Lab service recovered; follow-up test pending
Observed: health check passes at 14:20 UTC
Impact: synthetic requests failed for 8 minutes
Hypothesis: connection pool exhausted
Next action: reproduce under load in the lab
Decision needed: approve a test window

What to expect

One readable slide containing status, evidence time, impact, uncertainty and next action. No invented incident metrics should replace the synthetic fixture.

Your turn

Why is “all systems green” weaker than a named check and timestamp?

Show answer and reasoning
It hides what was tested, when it was tested and what remains unknown. Name the service and validation evidence so the audience can assess the claim.

Watch for: Do not use colour as the only status signal. Write labels and include a source for each chart or metric.

Link to this lesson

Path to advanced

In-progress stages identify the lessons already published. All other listed topics remain planned. Each addition needs teaching, a reproducible lab, failure cases, and a checkpoint before the capstone.

  1. Structured reports

    Excel tables, validation, lookups, pivots, Power Query and repeatable refreshes.

    PLANNED

  2. Team documentation

    Word styles, accessible tables, review history, ownership and version control.

    PLANNED

  3. Operational communication

    PowerPoint briefings with evidence, clear decisions and follow-up actions.

    PLANNED

References

Original AUWEN lessons, with upstream documentation for further study and version checks.

All learning paths and update notes →