Unit 08 · Informational & Technical Communication · Week 23

Technical Reading & Procedural Writing

How can a writer make a process accurate, safe, and reproducible?

Five complete lessons with local technical evidence, explicit instruction, printable workspaces, and evaluator-reviewed mastery.

Weekly targets

Explain accurately and accessibly

  • Use accurately: procedure, prerequisite, imperative, condition, constraint, sequence, verification, troubleshooting.
  • Make structure, evidence boundaries, and usability visible.
  • Complete Tested check-in procedure with usability report.
  • Revise after testing and evaluator feedback.

Local communication commission · Rivermark Learning Annex

Write information people can actually use

Following the Unit 7 investigation, Rivermark authorizes a ten-day evening pilot. The student communication team must explain the pilot, write a usable check-in procedure, and report attendance accessibly.

Evidence boundary: Rivermark, its annex, and all records in this packet are course-created simulations. They support this instructional commission only and must not be represented as real public data.

Week 23 technical packet

Shared facts and constraints

Operational requirements

  1. Visitor presents a student ID or approved temporary pass.
  2. Staff records arrival time and chosen work area; no sensitive notes belong in the public sign-in view.
  3. Visitor stores food, reviews the area expectation, and confirms transportation home.
  4. Collaborative-room use requires a reservation when capacity reaches twelve.
  5. At departure, visitor checks out and returns borrowed equipment.

Exception cards

  • ID forgotten but identity can be confirmed by an authorized school record.
  • Quiet room is full.
  • A visitor needs an accessible route or communication format.
  • The final bus leaves before the visitor’s planned departure.
  • The sign-in device is unavailable.

Day 111 · Required lesson

Read procedures as systems

Identify goal, user, prerequisites, inputs, sequence, decision points, outputs, and verification.

Direct instruction and model

A procedure is a model of action. Missing prerequisites or hidden decisions cause failure even when every sentence is grammatical.

Independent evidence

Annotate the operational requirements using the seven system elements. Identify three details a first-time user still needs.

Day 112 · Required lesson

Write precise actions

Use imperative verbs, concrete nouns, quantities, locations, and observable results.

Direct instruction and model

“Handle the form correctly” is vague. “Enter the arrival time in the check-in field, then confirm the student’s work area” is testable.

Independent evidence

Rewrite five vague directions. For each, add an observable success condition without inventing unavailable policy.

Day 113 · Required lesson

Design decisions and exceptions

Use conditional language for branches without burying the normal path.

Direct instruction and model

Write the normal sequence first; place “if/then” branches at the exact decision point. Safety and accessibility exceptions must be visible, not footnotes.

Independent evidence

Integrate all five exception cards into a decision table: condition, action, responsible person, and verification.

Day 114 · Required lesson

Run a usability test

Test the document, not the reader.

Direct instruction and model

A tester thinks aloud while following only the written instructions. The observer records hesitation, error, question, and recovery without coaching.

Independent evidence

Conduct or simulate two test runs. Record task completion, unclear step, error type, time or step count, and the revision the evidence supports.

Day 115 · Required lesson

Revise for reproducibility

Separate verified instructions from assumptions and unresolved policy.

Direct instruction and model

Do not conceal missing authority with confident wording. Label unresolved decisions and route them to an evaluator or authorized staff member.

Independent evidence

Submit the procedure, decision table, two test records, before-and-after revision excerpt, and a short limitation statement.

Weekly mastery assessment

Tested check-in procedure with usability report

Submit the named product, five daily responses, fact check, meaningful revision, and reflection. Preparation and submission are not mastery.

Criterion2 · Secure1 · Developing0 · Insufficient
Accuracy and evidence boundarySpecific, accurate and completePartly demonstrated; revision requiredMissing, unusable or inaccurate
Structure and reasoningSpecific, accurate and completePartly demonstrated; revision requiredMissing, unusable or inaccurate
Audience usabilitySpecific, accurate and completePartly demonstrated; revision requiredMissing, unusable or inaccurate
Language and accessible designSpecific, accurate and completePartly demonstrated; revision requiredMissing, unusable or inaccurate
Testing, revision and reflectionSpecific, accurate and completePartly demonstrated; revision requiredMissing, unusable or inaccurate

Mastery: 8/10 after evaluator review. Below 8/10, revise the lowest criterion and resubmit. Optional tools and completion controls cannot assign the score.