FREE TECHNICAL WRITING LEARNING PATH

WikiFree original practice workbook

The clarity press

CASE STATUS: fictional/synthetic teaching material. Do not present the example as real research, employment experience or measured business performance.

OUTCOME
Produce and test a concise task guide with prerequisites, ordered steps, expected results and a troubleshooting section.

BEFORE YOU START
Comfort writing short English sentences and using a text editor. No programming or paid course account.

CASE
The fictional Birch Learning Club needs a guide for exporting a completed attendance file. The process uses a local practice application described in the workbook: open the attendance table, choose the completed session, select Export CSV and save the file. The guide must distinguish previewing attendance from exporting it.

INPUTS
Reader need,Guide requirement
Find the right session,State the session-selection step
Know what was exported,Name the file and expected columns
Handle an empty session,Explain the no-records outcome
Protect source data,Export a copy without editing attendance


ENTRY CHECK

Question: Should a procedure hide prerequisites in its last step?

Self-check: No. State them before the task.

Question: Is export the same as delete?

Self-check: No. Use precise action words.

Question: How do you know a guide works?

Self-check: Test it against the stated task and record where a reader gets stuck.

STAGE 1: Define the audience and task

Prerequisite: Comfort writing short English sentences and using a text editor. No programming or paid course account.

Instruction: A task guide serves a reader with a goal and a starting state. Identify what they already know, what files or access they need and what success looks like. The assigned public pre-class reading introduces clear technical writing; the following original exercises apply those ideas to one small procedure. Avoid mixing a tutorial, reference and troubleshooting article without a clear purpose.

Practice task: Write a reader profile, scope statement and prerequisites for exporting attendance.

Deliverable: An audience and task brief.

Acceptance check: The brief names the starting state, intended reader and exported-file outcome.

If stuck: Replace a broad topic such as attendance management with the specific task.

Record your work, decisions and evidence:




Record your result against the acceptance check:



STAGE 2: Draft action-led steps

Prerequisite: Bring your previous output: An audience and task brief.

Instruction: Each step should tell the reader what to do and where to do it. Use consistent interface names from the practice specification, and keep the sequence in the order the reader encounters it. Put a necessary condition before the action it changes. Short sentences help, but splitting every phrase into a separate numbered step can obscure the actual task.

Practice task: Draft five to seven numbered steps from the supplied process. Add an expected result after export.

Deliverable: A first procedural draft.

Acceptance check: A reader can identify the action, object and next state in each step.

If stuck: Replace passive wording such as the file should be saved with an explicit Save action.

Record your work, decisions and evidence:




Record your result against the acceptance check:



STAGE 3: Make terms and examples consistent

Prerequisite: Bring your previous output: A first procedural draft.

Instruction: Choose one name for each concept and use it consistently. Session, event and class might sound interchangeable but can confuse a reader if the interface uses only Session. A small example file name and column list make the output concrete. Explain any abbreviation at first use when the audience may not know it.

Practice task: Create a five-term mini glossary and revise the draft for consistent labels. Add a synthetic example file name and columns.

Deliverable: A revised guide and terminology sheet.

Acceptance check: The guide uses the same session and export labels throughout and identifies the expected CSV columns.

If stuck: Do not change interface labels merely to avoid repeating a word.

Record your work, decisions and evidence:




Record your result against the acceptance check:



STAGE 4: Add recoverable troubleshooting

Prerequisite: Bring your previous output: A revised guide and terminology sheet.

Instruction: Troubleshooting connects a symptom to a useful next action. For an empty session, explain how to verify the selected session and whether attendance exists. Do not ask the reader to repeat a destructive or unrelated operation. Keep the common failure cases close to the procedure and state when the reader should stop and ask the responsible owner.

Practice task: Write entries for an empty export, wrong session and missing save permission. Include expected recovery and escalation.

Deliverable: A three-case troubleshooting section.

Acceptance check: Each case has a symptom, a check and a bounded next action.

If stuck: Avoid the unhelpful instruction try again without explaining what should change.

Record your work, decisions and evidence:




Record your result against the acceptance check:



STAGE 5: Test the guide against the task

Prerequisite: Bring your previous output: A three-case troubleshooting section.

Instruction: A documentation test observes whether the stated steps lead from the starting state to the promised result. Use the supplied process simulator or a clearly labeled walkthrough; do not invent participant feedback. Record where information is missing, revise the guide and repeat the affected steps. A style checklist complements task testing but cannot replace it.

Practice task: Run the guide through the provided paper walkthrough, record three checks and revise at least one ambiguity.

Deliverable: A tested guide with a revision log.

Acceptance check: The final guide produces the expected file description and distinguishes untested real-application behavior.

If stuck: Do not claim a user study if you performed only a solo walkthrough.

Record your work, decisions and evidence:




Record your result against the acceptance check:



WORKED CASE
A precise step says: Select the completed session, then choose Export CSV. Its expected result names the downloaded attendance copy and its columns. If there are no records, the guide asks the reader to verify the session instead of inventing data or changing attendance.

FINAL PROJECT
Deliver the task brief, final guide, glossary, troubleshooting entries and test log. Add a short quick-start version that preserves the prerequisites and expected result without losing necessary actions.

REQUIRED CRITICAL CHECK
The final procedure has an unambiguous starting state, action sequence and verifiable result, with no fabricated test evidence.

SCORING
Score each of the five stage acceptance checks from 0–16 (0 missing/incorrect; 8 partially supported; 16 complete and evidenced). Score the final integrated project from 0–20 (0 missing; 10 incomplete handover; 20 complete, reproducible and consistent with the case). Target: at least 80/100 AND the critical check must pass. A total score never overrides a failed critical check.

SCOPE LIMIT
This is a task-documentation project, not the instructor-led portion of Google training, a writing credential or a complete documentation system.

SOURCES AND ACCESS
The public pre-class material is free. No registration, instructor-led session or certificate is required for this path.

Google Technical Writing One: Free Self-Paced Lessons
WikiFree: https://wikifree.com/courses/google-technical-writing-one/
Official source: https://developers.google.com/tech-writing/one
Why selected: Google Technical Writing One supplies public pre-class instruction. The attendance-export specification, writing tasks and review checklist are original WikiFree exercises.

Stage 1 assigned focus: Technical Writing One: public pre-class material; 120 minutes (Provider planning estimate).

Google Technical Writing One
https://developers.google.com/tech-writing/one

REUSE
Original WikiFree teaching text and synthetic fixtures are supplied for personal learning and adaptation with attribution. Provider lessons remain on their original sites and retain their own terms. No provider certificate is included.