Why Vocabulary is Important in 21st Century | Preventing Wrong File Submissions by Distinguishing Draft, Under Review, Approved and Published

Did you know that a school newsletter file named FINAL_v7.docx might still be an unapproved draft? The word final in a filename can be written by anyone. It does not prove that the science facts, student names, photograph permissions or print layout have passed review.

The direct answer: draft describes a version still being developed; under review means someone is examining it and may request changes; approved means an authorised reviewer has accepted a specified version for a specified purpose; and published means material has been released to its intended audience. These are different stages of a document’s life, and the order and formal permissions depend on the organisation’s system. A filename is not a reliable substitute for an actual approval record.

The student project problem: four copies, one deadline

Imagine a Secondary 2 project team preparing a short guide to water conservation. There is a document called WaterGuide_Final in one student’s downloads folder, a shared document with comments, a PDF sent for teacher review and a newer PDF ready for print. A student emails the first file because its name contains “Final”. The result may be an outdated chart or a paragraph with an earlier error that the team already corrected.

The preventable error is not poor spelling. It is confusing version name with workflow status. Files can be named carelessly, saved locally, emailed to different people or downloaded before a decision is made. A useful process identifies the document by version, status, owner, decision and destination—not by one exciting word.

Four stages, four questions

Draft — What is being developed? A draft is an unfinished or provisional version. It may be coherent enough to read, but facts, wording, citations, images and layout can still change.
Under review — Who is checking it, and what remains open? A reviewer may suggest corrections, raise unanswered questions or verify evidence. The file is not automatically approved because somebody opened it.
Approved — Who authorised this particular version for this particular use? Approval should have an accountable decision, such as a teacher approving a poster for printing. Another use, such as posting the same poster online, may need additional checks.
Published — Where and to whom was the material actually released? Publication may be a web post, a printed booklet, a class newsletter or a public PDF. A published file can later require correction or withdrawal.

The words are related but not synonyms. “Approved for classroom printing” does not mean “approved for unrestricted internet sharing”. Similarly, an internal draft may be visible to collaborators without being public. Ask what audience the decision covers.

Why review and approval are different

Review is an activity: somebody examines material and provides observations or suggestions. Approval is a decision: an authorised person signals that an identified version meets the applicable requirement. A reviewer can propose edits without having authority to grant release, and an approver may return material for further work. In Microsoft SharePoint libraries configured to require content approval, submitted items can have a Pending status until an authorised person approves them; this demonstrates the difference between asking for approval and receiving it.

The precise workflow is not universal. A class may use a teacher’s email response, while a workplace may use a formal document-control tool. Some documents may be published without a separate approval stage, although that may be inappropriate for sensitive content. The lesson is to understand what the status actually certifies in the system being used.

Microsoft’s content-approval guidance describes states such as Pending and Approved in configured lists or libraries. Those exact states illustrate a real software workflow; they are not a claim that every Singapore school uses SharePoint or requires the same stages.

An invented workflow with a real decision

The next scenario is fictional. The names and version numbers are teaching examples, not a report of a real school. A class team submits WaterGuide_v1 to a teacher. The teacher marks two issues: a chart has an unlabeled vertical axis, and a photo lacks documented reuse permission. The team changes the chart to show litres per person per day and replaces the photo with one it is authorised to use. The new file is WaterGuide_v2.

A class representative writes, “Version 2 is approved because we fixed the mistakes.” That sentence overclaims. It may now be ready for review, but the students’ own confidence is not the teacher’s approval. The safe handoff is to ask the responsible reviewer to check the changed document and record the decision.

Once the teacher approves the identified version for classroom printing, the team exports a PDF from that version and checks the printed copy. Suppose they later change the data table. The old approval should not simply be assumed to cover the changed content. The team should ask whether the updated version needs another check. Publication is a separate event: printed copies or the authorised PDF finally reach readers.

A mini version-control table in words

A concise file handoff could say: “Document: WaterGuide. Version: 2.1. Status: awaiting teacher approval. Changed since v2: diagram labels and image credit. Next action: teacher checks v2.1. Distribution: not yet authorised.” That is far more informative than WaterGuide_final_FINAL.pdf.

For older primary pupils, reduce the message to three prompts: “Which copy?”, “Has it been checked?” and “Where can it go?” Secondary students can extend it to “Which revision was approved?”, “Who has the authority?” and “Did publication use that exact version?” In future careers, the same habits transfer to reports, engineering drawings, brochures, research summaries and other documents, although each setting has its own controls.

Tracked changes do not equal approval

Word processors often distinguish between commenting, suggesting, accepting an edit and approving a document. These are not interchangeable. In Microsoft Word, tracked changes can be accepted or rejected individually. Accepting a proposed sentence makes that change part of the document; it does not automatically authorise the whole document for publication.

The distinction is visible in Microsoft’s Track Changes guidance. A team may accept every spelling correction while a missing safety warning, incorrect number or permission problem remains unresolved. No visible red markup is not a formal guarantee of factual correctness.

Likewise, setting a shared document’s access to “anyone with the link” is a permission change, not an editorial approval. A document can be easy to open and still be inappropriate to circulate.

The vocabulary of a controlled handoff

Revision / revise / revised: making a new version to address changes. A revised draft is not necessarily approved.
Review / reviewer / review comments: examination and feedback. “In review” means the decision may still be open.
Approve / approved / approval: a decision taken by someone authorised in the particular workflow. “Approval pending” means approval has not happened.
Publish / publication / published: release to an audience, not merely save a file.
Release / released / release candidate: a candidate may be almost ready but still require checks; released means it is available in its intended context.
Withdraw / withdrawal / withdrawn: removing material from use or distribution after a decision, without pretending readers never saw an earlier version.

Common misconceptions

“The file says final, so it is approved.” No. A filename is evidence of what somebody named the file, not proof of an authorised decision. Look for an approval record or a clear instruction from the responsible person.

“Someone wrote a comment, so the work is rejected.” Not necessarily. Comments can be suggestions, questions, minor improvements or serious objections. Read the actual comment and status.

“Published means correct forever.” Publication is an action, not a lifetime certificate. New information may require a dated correction, clarification or updated version. Do not silently rewrite an old claim and leave readers thinking nothing changed.

“We can share the approved file anywhere.” Not automatically. Approval may be specific to a class, audience or form of distribution. Image rights, privacy and audience restrictions still matter.

A practical check before pressing Send

Identify the exact document and latest version, ideally with a stable link or clearly named file.
Check what the current status means in this team’s workflow; do not infer it from a filename.
Read unresolved review comments, especially questions about figures, sources, names and permission to share images.
Confirm who must approve the material and whether their approval covers this version and intended audience.
Check that the exported PDF or printed copy matches the approved content, including images, tables and captions.
After release, record the date and location of publication and preserve an accessible correction route.

Retrieval and transfer exercise

Without looking back, write four sentences using draft, review, approval and publication correctly. Then answer: a student has fixed comments but the teacher has not responded—what status can safely be claimed? A brochure was approved for a school corridor but is now being uploaded to a public website—what new permission question arises? A file was published yesterday and a figure is wrong—what should the author do?

A day later, repeat those questions using a different object: a science poster, a group presentation, a club announcement or an application portfolio. The transfer is the point. Students should learn to apply status language to unfamiliar files instead of recognising four definitions only in one article.

Advice for students, parents and teachers

Students: appoint a version owner in a group project. Record decisions in a short change log, ask before publishing classmates’ photos and stop relying on filenames that say FINAL or FINAL2. Parents: ask, “Is this your newest draft, or the version your teacher checked?” instead of “Have you finished it?” Teachers: make review and approval criteria explicit. A simple “ready to submit / needs changes / approved for this audience” routine helps learners see the difference.

For secondary English, this is a lesson in precise register: submitted for review is a truthful professional phrase when approval is pending. For Mathematics and Science, it helps preserve which table, graph or numerical claim was actually checked. For careers, it supports accountable handovers without asserting that every employer uses the same software.

Frequently asked questions

Is an approved document always public? No. It may be approved for internal use only. Does reviewed mean approved? No; review can conclude with changes required. Does a file need the word FINAL in its name? No; a stable version identifier and clear status are more useful. Can a published page change? Yes, but a responsible update process should preserve clarity about significant corrections and dates.