Editorial review: 9 October 2026
Make the reader's next step clear
Professional writing skills help you turn accurate information into a document a particular reader can use. A polished sentence is not enough if an instruction omits a condition, a report hides its evidence or a proposal describes an unapproved idea as a decision.
Plan the purpose, select the necessary facts, draft a complete document, and revise its meaning before proofreading. This guide works through an original fictional instruction sheet from source notes to a revised version and a different audience's version. Nothing in the exercise is an actual company procedure or evidence of a real reader's behaviour.
Purdue OWL's business-writing guidance encourages revision from the reader's perspective, including attention to purpose and necessary detail. The practical documents and review method below are our own teaching examples. They are not Purdue templates or a reproduction of its checklist. Read Purdue's guidance on revision.
Decide what kind of document you need
A fictional training group needs an instruction sheet for submitting a practice reading note. The reader is a participant who has not used this exercise before. The purpose is to explain which file to prepare, where to put it and what to do if the supplied destination is unavailable.
That purpose calls for a short instruction sheet. An executive summary would not supply enough procedural detail. A promotional article about the benefits of writing would not tell a participant how to submit. A friendly email could carry the instructions, but its tone would not replace the actual conditions.
For other work, make the same choice deliberately. A report should distinguish observations from interpretation and recommendations. A proposal should identify the decision being requested. A presentation should guide a spoken explanation without requiring an audience to decipher a dense paragraph while listening. The document's shape should follow its purpose.
Establish the source facts before drafting
The following are all the facts supplied for our fictional exercise:
- Prepare one practice reading note of 150–200 words about either of two supplied fictional passages, Passage A or Passage B.
- Save it as a PDF using the participant's assigned exercise identifier followed by “reading-note.” For identifier P17, the filename is P17-reading-note.pdf.
- Put the file in the exercise folder labelled “Reading notes — practice.” The folder link is supplied separately in the exercise materials; no working public link is part of this example.
- Include the chosen passage label at the top of the note. Names and phone numbers are not requested.
- If the supplied folder cannot be opened, tell the facilitator the exercise identifier and that the folder is unavailable. Do not submit the file to a different destination without further instructions.
- The facilitator has not supplied a deadline or a promise of feedback. Submission is not the same event as feedback being given.
These source notes are invented for the lesson. Their word limit and file format are exercise conditions, not general rules for professional writing. A real procedure must use its actual owner's requirements.
Inspect a complete flawed draft
Here is the entire first draft:
Reading task
Write a great summary of both passages and upload it tomorrow. Use your full name as the file title so that we can identify you easily. Send a Word document or PDF to the usual folder. If the folder does not work, email the note to any trainer. Everyone will get feedback after submitting. Please complete this important task promptly.
The grammar is mostly readable, but the instructions conflict with the source. The draft requests both passages instead of either one. It omits the 150–200-word limit and passage label. It invents a deadline, accepts an unsupported file type, substitutes a name for the identifier, leaves the folder ambiguous and invents both an alternative submission route and a feedback promise.
Replacing “great” with “excellent” would not repair those problems. Revision must first correct meaning and missing conditions. The final sentence adds urgency without supplying an authorised date; removing it is more useful than making it sound more formal.
Produce the complete revised instruction sheet
The revised artifact below is ready as a fictional practice document. Its separately supplied folder link remains outside the example; no placeholder is presented as a working destination.
Practice reading note: preparation and submission
Choose either Passage A or Passage B from the exercise materials. Write one reading note of 150–200 words and put the chosen passage label at the top. You do not need to include your name or phone number.
Save the note as a PDF. Use your assigned exercise identifier followed by “reading-note” as the filename. For example, participant P17 would use P17-reading-note.pdf.
Use the separately supplied link to the folder labelled “Reading notes — practice” and put your PDF there.
If you cannot open that folder, tell the facilitator your exercise identifier and that the folder is unavailable. Wait for further instructions before sending the file to another destination.
No submission deadline or feedback arrangement has been supplied for this exercise. Ask the facilitator if you need either detail before planning your submission.
Explain why the revision works
The revised sheet follows the participant's task order: choose, write, label, save and submit. The exception appears beside the submission step it affects. The filename example illustrates a rule without replacing the participant's own identifier.
The final paragraph preserves a real unknown instead of filling it with “tomorrow.” It does not suggest the task is optional or claim that no deadline will ever exist. It states that a deadline has not been supplied and identifies the person to ask.
This is also a useful conciseness lesson. The revised document needs more precise detail than the flawed one, even if that makes it longer. Cutting necessary conditions to achieve a shorter word count would undermine the purpose. Remove repetition and vague praise before removing information the reader needs.
Adapt the same facts for a different reader
Now the intended reader is the facilitator checking whether the instruction sheet accurately reflects the supplied exercise. That reader needs a compact review record rather than participant-facing steps. Here is a separate complete version:
Reading-note instruction review
The participant sheet requests one 150–200-word note on either Passage A or Passage B, with the selected passage label at the top. It requires a PDF named with the assigned identifier plus “reading-note,” using P17-reading-note.pdf as an example.
The submission destination is the separately supplied “Reading notes — practice” folder. The sheet asks participants who cannot open it to report their identifier and the access problem to the facilitator, then wait for instructions before using another destination. It does not request names or phone numbers.
The source notes contain no deadline or feedback promise. The sheet identifies those details as unsupplied. Please confirm whether either detail should be added; this review does not itself authorise a change.
The facts remain the same, but the order and emphasis change. The facilitator version makes the unresolved decision explicit. It does not imply that requesting confirmation means confirmation has arrived.
Test clarity with a limited reader response
The exercise supplies this fictional participant paraphrase:
“I choose one passage, write 150–200 words with its label, and save a PDF using my identifier. I use the supplied practice folder. If it will not open, I report that to the facilitator and wait. I need to ask about the deadline.”
Compare the response with the instruction sheet. It captures the core task, format, naming basis, destination, exception and missing deadline. It does not mention the exact filename suffix, so that detail could use a targeted follow-up question: “What would your full filename be for identifier P17?”
The supplied response is evidence only of this fictional paraphrase. It does not prove that a file was created, named correctly, uploaded or reviewed. Likewise, “Looks fine” from a real reader is not automatically evidence that every condition is understood. Ask the reader to explain the action in their own words when that check is appropriate.
Build a practical writing routine
Before drafting, write one sentence naming the reader and intended use. Keep source facts separate from proposed additions. If a date, number or permission is absent, flag it as a question for the owner.
During revision, compare every instruction with its source. Inspect words that change obligations or scope: “either” and “both,” “may” and “must,” “proposed” and “approved,” “submitted” and “accepted.” These small words can alter meaning more than a spelling error.
Then review structure. Give each paragraph a job and put conditions near the action they govern. Replace unclear pronouns such as “it” when two possible referents appear. Use headings to make a longer document navigable and lists when the reader needs a sequence.
Finally, proofread names, figures, filenames, punctuation and formatting in the version the reader will receive. Open the exported document and check links you are authorised to share. A clean draft in an editor does not establish that its exported copy is complete.
Frequently asked questions
How can I practise writing skills without a workplace task?
Make a small fictional instruction sheet with explicit conditions. Draft it, mark unsupported additions, revise it and ask a willing reader to paraphrase the intended action. Keep any claims about that feedback limited to what the reader actually said.
Should professional writing always sound formal?
Choose language appropriate to the reader and task. In this exercise, plain instructions are sufficient. Formal vocabulary would not make an invented deadline more accurate or an ambiguous folder easier to find.
Can a writing tool or AI assistant do the revision?
It may suggest phrasing if your use is permitted, but you must compare its output with the source. Check that it has not invented dates, destinations, promises or approvals. Do not supply confidential material to an unauthorised tool.
How should I measure improvement?
Track concrete revision issues: omitted conditions, unsupported claims, unclear references and errors in the exported version. A reader's accurate paraphrase can support a narrow clarity finding. It does not guarantee agreement, execution or a career outcome.
Where should I apply these skills next?
Try a genuine, permitted work sample or a clearly labelled practice document. For application writing, the résumé guide shows how to preserve evidence and ownership. The problem-solving guide develops the same distinction between observations, proposals and checked results.