A031

Spellcheck vs Generative Rewriting: Questions to Ask Before Editing

Spellcheck and generative rewriting can both change written work, but their functions are not automatically equivalent. A basic correction may identify a likely spelling error, while another feature may generate alternative wording, restructure a sentence, or replace a larger passage. The relevant question is therefore not simply which product you used. Before editing university work, identify what the specific feature does, check whether that function is permitted for the task, and determine whether its use must be disclosed. This independent topic resource is not official, approved, endorsed by, or affiliated with any university. Official unit materials, assessment instructions, rubrics, policy pages, platform notices, and teaching staff are authoritative.

Why the spellcheck vs AI rewriting distinction matters

A tool’s brand name does not provide enough information to classify every action performed within it. One application may contain ordinary spelling correction, grammar suggestions, predictive text, translation, paraphrasing, sentence generation, and whole-document rewriting. These functions can involve materially different levels of intervention in a student’s expression and reasoning.

Focus on the operation you selected and the output it produced. Ask whether the feature merely flagged a possible error, proposed a limited correction, supplied new phrasing, reorganised an argument, or generated content that was not previously present. This feature-level approach supports a more precise comparison than treating every digital writing aid as either harmless spellcheck or prohibited artificial intelligence.

Start with the rules for the particular task

Permission can depend on the specific task and its current instructions. Before using an editing feature, read the assessment directions, rubric, relevant policy pages, and notices on the learning platform. Look for statements about proofreading, language assistance, generative tools, translation, paraphrasing, collaboration, acknowledgement, and retention of drafts or prompts.

Do not assume that permission in one context transfers to another. If the wording is unclear, ask teaching staff a narrow question that names the function and intended use. For example, explain whether you want to accept isolated spelling corrections or request generated alternatives for complete sentences. A precise question is more useful than asking whether a product is generally allowed.

Feature-level permissions checklist

Before editing, record the feature name and describe what you expect it to do. Then check: Does it only flag text, or does it replace text? Does it correct a likely typographical error, or generate new language? Can it alter meaning, tone, evidence, structure, or reasoning? Does it process a selected phrase, a paragraph, or the entire document? Are its suggestions automatic, or do you review and accept each change?

Next, connect those answers to the applicable instructions. Confirm whether the function is allowed, restricted, or subject to acknowledgement. Check whether you must preserve prompts, outputs, version history, tracked changes, or another record. Also consider privacy and confidentiality requirements before entering assessment text, personal information, unpublished material, or third-party content into any external system. If the rules do not resolve the issue, pause and seek clarification rather than guessing.

Protect meaning, evidence, and reasoning while editing

Even a permitted editing feature can introduce errors. Review every accepted change against your intended claim. Check whether qualifications have disappeared, technical terms have shifted, relationships between ideas have changed, or the revised wording now makes a stronger claim than the evidence supports. Generated fluency is not evidence of factual accuracy.

Recheck citations after rewriting. A new sentence may no longer match the cited source, and a paraphrase may remain too close to source wording despite superficial substitutions. Confirm that each citation supports the exact proposition beside it and that quoted or paraphrased material is represented accurately. Use the citation style and source requirements specified in the official task materials.

Document allowed use and prepare an accurate disclosure

Where disclosure is required, describe the actual function and scope of use rather than relying on a broad product label. A useful record may include the feature used, the purpose of using it, the portions of the document affected, and how you reviewed the suggestions. Follow the required acknowledgement format if one is supplied.

Keep records only as required or reasonably useful under the applicable rules, and do not treat documentation as retroactive permission. A disclosure explains use; it does not by itself make a restricted function acceptable. Equally, this article cannot determine whether a particular action complies with local requirements. Current official instructions and teaching staff guidance take priority.

Complete an integrity and submission review

Before submission, read the final work without the editing interface. Confirm that you understand and can support every claim, that the reasoning remains yours where required, and that no generated wording has introduced unsupported facts, fabricated references, or misleading attribution. Compare the final version with your notes and sources, and resolve any passage whose origin or evidential basis is uncertain.

Finally, verify the submission itself. Check that the intended file opens, the correct version is attached, citations and references display properly, and any required acknowledgement is included in the designated place. Review current platform notices and task instructions at the time of submission. No tool classification, writing pattern, or automated output can conclusively prove authorship on its own.

Reference values and review limits

The supplied reference values for this topic are TEQSA student advice on artificial intelligence, the UNSW AI toolkit, and Monash University material on AI acknowledgement. Their supplied URLs are https://www.teqsa.gov.au/students/artificial-intelligence-advice-students, https://www.unsw.edu.au/student/managing-your-studies/academic-skills-support/toolkit/ai, and https://www.monash.edu/learning-teaching/teachhq/Teaching-practices/artificial-intelligence/ai-acknowledgement.

These links are listed as reference values supplied for the article; this resource does not claim to have visited or verified their current wording. Product functions, policy language, and local procedures may change. Verify current information directly in authoritative materials before acting.

Independent Resource and Official Requirements

This is an independent academic resource, not an official university page, and it does not claim university affiliation. Use it for planning and review while relying on the current unit outline, assessment brief, rubric, policy pages, learning-platform notices, and teaching staff for authoritative requirements.

No grade, outcome, price, extension, acceptance decision, or policy interpretation is promised here. Verify every source and submission detail yourself, keep the work authentically yours, and ask the relevant university contact when an instruction is unclear.

Frequently asked questions

Is spellcheck always permitted in university work?

Not necessarily. Permission depends on the applicable task instructions and current local rules. Check what the feature actually does, because a product described as a spellchecker may also offer generative rewriting. Official unit materials, rubrics, policy pages, platform notices, and teaching staff are authoritative.

When does a correction become generative rewriting?

There is no universal boundary stated in the supplied facts. Examine whether the feature flags an error, makes a limited correction, or generates replacement language, structure, or content. If the distinction affects permission and the instructions are unclear, describe the exact function to teaching staff and request guidance.

Should I disclose an AI-assisted edit if I changed the suggestion afterward?

Follow the disclosure requirements for the task. Later modification does not necessarily remove a requirement to acknowledge earlier use. Record the function, purpose, scope, and review process where relevant, then use any acknowledgement format specified in official materials.

What should I record before using a rewriting feature?

Where consistent with applicable rules, note the feature used, its intended purpose, the text affected, and whether prompts, outputs, tracked changes, or version history must be retained. Do not enter confidential or third-party material into an external system without checking relevant requirements.

Can A031 determine whether my editing method is allowed?

No. A031 is an independent article identifier, not an official permission decision. This resource offers a process for asking better questions, but current assessment instructions, rubrics, policies, platform notices, and teaching staff determine the applicable requirements.