Primary 5 formal and informal vocabulary helps Grade 5 students choose language that fits audience, purpose and situation. This Top 100 Primary 5 Vocabulary collection teaches formal and informal word pairs, register, audience awareness, tone and rewriting for learners searching for Grade 5 formal and informal language, 5th grade register, formal vocabulary words, informal vocabulary words, formal vs informal English, academic word choice and audience-and-purpose practice. A strong learner knows that kids and children can refer to the same group while creating different levels of formality, and that ask for and request can express similar actions in different registers.

These Grade 5 formal and informal vocabulary pairs are not a list of “good words” versus “bad words.” Informal English is natural and appropriate in conversation, friendly messages and dialogue; formal English is useful in reports, school presentations, official requests and academic explanation. The 100 numbered entries therefore teach meaning preservation during register change: the learner must keep the same underlying message while adjusting vocabulary, contractions, sentence framing, politeness and precision.

This advanced Primary 5 English vocabulary resource is world-facing and designed for two-way register control. Alicia, Tricia and Kai Kai practise informal-to-formal rewriting and formal-to-natural rewriting because mastery means being able to move in both directions without sounding stiff, vague or unnatural. Current Grade 5 resources explicitly teach formal and informal English and register switching by audience and purpose; this page extends that skill into a 100-pair vocabulary system with original examples, diagnostics, casebooks and transfer tasks.

Register is language fitted to the room

Kai Kai texts a friend, “Can’t make it today—sorry!” The meaning is clear and the register fits a casual message. He would not normally write the same wording in a formal school request. There he might write, “I am unable to attend today. I apologise for the late notice.” The facts remain the same; the language relationship with the audience changes.

Tricia then makes the opposite mistake. She tells a friend, “I would be grateful if you could accompany me to the canteen.” The sentence is grammatical but unusually formal for an ordinary friendly exchange. Register control is not about making every sentence more formal. It is about selecting the level of formality that fits.

Alicia writes the rule on the board: preserve meaning, adjust register. A successful transformation does not exaggerate politeness, remove personality or change the facts. It changes vocabulary and structure while keeping the communicative purpose intact.

Choose the register family you need

Everyday words to neutral/formal alternatives: begin with 1–20.

Requests, replies and polite interaction: use 21–40.

School, report and academic vocabulary: use 41–60.

Informal phrasal choices to formal single-word alternatives: use 61–80.

Tone, precision and audience-sensitive choices: use 81–100.

After the 100: register-selection method · worked exercises · original casebooks · writing clinic · teaching system · references.

Five things that change when register changes

Vocabulary: kids → children; buy → purchase in some formal contexts. Contractions: can’t → cannot when a fuller formal style is preferred. Phrasal verbs: put off → postpone. Sentence framing: “Send me…” → “Could you please send…” or “Please provide…”. Tone: excitement, slang and conversational markers may be reduced in formal writing while clarity and precision increase.

This page is distinct from the broader eduKate Vocabulary Learning System, the phrasal-verbs collection and the academic collocations collection. Here the organising question is register: which wording fits this audience and purpose while preserving meaning?

Pairs 1–20: everyday words to neutral and formal alternatives

These pairs show common shifts from conversational wording toward more neutral or formal choices. The formal alternative is not automatically superior; it is useful when audience, purpose and genre call for it.

1. kids / children

Register shift: Kids is casual and conversational; children is neutral to formal and suits school reports, notices and academic prose. Example: Informal: “The kids finished early.” Formal/neutral: “The children completed the activity early.”

Precision check: Do not replace kids in natural dialogue merely to sound advanced. Register depends on speaker and setting.

2. buy / purchase

Register shift: Buy is neutral and common; purchase is more formal and common in notices, reports and transactional writing. Example: “Families can buy tickets online.” / “Tickets may be purchased online.”

Precision check: Purchase can sound needlessly formal in everyday conversation. Preserve the same transaction meaning.

3. help / assist

Register shift: Help is neutral and broad; assist is more formal and often used in institutional or written contexts. Example: “Can you help me?” / “A staff member will assist visitors at the entrance.”

Precision check: Assist is not automatically better. Help is often clearer and warmer even in professional writing.

4. ask / inquire

Register shift: Ask is neutral; inquire is more formal when the meaning is seek information. Example: “Ask the office about the timing.” / “Please inquire at the office regarding the timing.”

Precision check: Inquire does not replace every sense of ask, especially ask someone to do something.

5. tell / inform

Register shift: Tell is neutral and conversational; inform is more formal when conveying information. Example: “Tell me if the room changes.” / “Please inform me if the room changes.”

Precision check: Inform normally concerns information, not storytelling or commanding.

6. need / require

Register shift: Need is neutral; require is more formal and often expresses an official or necessary condition. Example: “You need a pass.” / “Visitors require a pass for entry.”

Precision check: Require may sound stronger or more institutional. Do not change the level of obligation accidentally.

7. enough / sufficient

Register shift: Enough is neutral; sufficient is more formal and common in analytical or report language. Example: “We have enough time.” / “There is sufficient time to complete the task.”

Precision check: Sufficient can sound unnatural in casual dialogue. Meaning should remain adequacy, not abundance.

8. before / prior to

Register shift: Before is neutral; prior to is more formal and common in administrative prose. Example: “Check the file before printing.” / “Verify the file prior to printing.”

Precision check: Prior to is often wordier without adding meaning. Use it only when the register benefits.

9. after / following

Register shift: After is neutral; following is more formal when it means after an event. Example: “After the meeting, we revised the plan.” / “Following the meeting, the plan was revised.”

Precision check: Following can also mean next or moving behind; context must select the temporal sense.

10. about / regarding

Register shift: About is neutral; regarding is more formal when introducing a topic. Example: “I have a question about the schedule.” / “I have a question regarding the schedule.”

Precision check: Regarding is useful in formal correspondence but can sound stiff in ordinary speech.

11. so / therefore

Register shift: So is common and conversational; therefore is more formal when marking a conclusion or consequence. Example: “The file was outdated, so we replaced it.” / “The file was outdated; therefore, it was replaced.”

Precision check: Therefore often needs stronger logical structure and punctuation. It is not a decorative replacement for every so.

12. but / however

Register shift: But is neutral and direct; however is more formal as a sentence connector marking contrast. Example: “The plan is simple, but it is expensive.” / “The plan is simple; however, it is expensive.”

Precision check: However and but differ in syntax. Register change may require sentence restructuring.

13. also / additionally

Register shift: Also is neutral; additionally is more formal and common when adding a separate point in reports. Example: “The room is larger and also quieter.” / “Additionally, the room has better lighting.”

Precision check: Additionally is not a natural substitute for every position of also.

14. maybe / perhaps

Register shift: Maybe is conversational-neutral; perhaps is slightly more formal in many contexts. Example: “Maybe we should check again.” / “Perhaps the figures should be checked again.”

Precision check: Both are standard English. The difference is register tendency, not correctness.

15. a lot of / many

Register shift: A lot of is common and conversational; many is more concise and often preferred with countable nouns in formal prose. Example: “A lot of students replied.” / “Many students replied.”

Precision check: With uncountable nouns, many does not fit; use much, considerable or another precise quantity expression.

16. a lot of / much

Register shift: A lot of is common; much is more formal in some negative/question structures and with uncountable nouns. Example: “We do not have a lot of time.” / “We do not have much time.”

Precision check: In affirmative sentences, much can sound unnatural without modifiers: “much time” is context-dependent.

17. big / large

Register shift: Big is common and conversational; large is often more neutral-formal in measurement and report writing. Example: “It was a big group.” / “A large group attended.”

Precision check: Large does not replace big in every idiom: a big decision often sounds more natural than a large decision.

18. small / minor

Register shift: Small is general size/amount; minor is more formal when the meaning is limited importance or seriousness. Example: “There was a small error.” / “There was a minor error.”

Precision check: Minor changes the dimension from physical size to importance/seriousness. Use only when that is intended.

19. good / effective

Register shift: Good is broad; effective is more precise and formal when judging whether something achieves its purpose. Example: “The new method was good.” / “The new method was effective at reducing errors.”

Precision check: Effective is not a general synonym for morally good, pleasant or high quality.

20. bad / ineffective

Register shift: Bad is broad and informal-neutral; ineffective is precise/formal when something fails to achieve its intended result. Example: “The first method was bad.” / “The first method was ineffective because it did not reduce errors.”

Precision check: Ineffective evaluates function, not every negative quality.

Return to the register routes.

Pairs 21–40: requests, replies and polite interaction

Register becomes especially visible in requests, apologies, greetings and responses. These pairs show how formality can change through phrasing while the communicative purpose remains stable.

21. thanks / thank you

Register shift: Thanks is friendly and informal-neutral; thank you is fuller and often more suitable in formal interaction. Example: “Thanks for the update.” / “Thank you for the update.”

Precision check: Both can be polite. Formality depends on the whole message, not one word alone.

22. sorry / I apologise

Register shift: Sorry is natural in conversation; I apologise is more formal and explicit. Example: “Sorry I’m late.” / “I apologise for the delay.”

Precision check: An apology should match the seriousness of the situation. Formal wording does not replace genuine responsibility.

23. can you…? / could you please…?

Register shift: Can you is direct and common; could you please is more conventionally polite/formal for requests. Example: “Can you send the file?” / “Could you please send the file?”

Precision check: Could does not literally change ability here; it softens the request.

24. I want… / I would like…

Register shift: I want is direct; I would like is softer and more polite/formal. Example: “I want a copy.” / “I would like a copy, please.”

Precision check: In emergencies or direct instructions, plain want/need may be clearer.

25. send me… / please send…

Register shift: Send me is direct; please send adds conventional politeness and suits formal requests. Example: “Send me the timetable.” / “Please send me the updated timetable.”

Precision check: Please helps tone but does not automatically make an abrupt message fully formal.

26. tell me… / please let me know…

Register shift: Tell me is direct; please let me know is softer and common in polite correspondence. Example: “Tell me when it’s ready.” / “Please let me know when it is ready.”

Precision check: Let me know is itself relatively conversational-neutral; context determines how formal the full sentence is.

27. I can’t attend / I am unable to attend

Register shift: Can’t attend is conversational; am unable to attend is fuller and more formal. Example: “I can’t attend tomorrow.” / “I am unable to attend tomorrow.”

Precision check: Unable to can sound overly formal in a friendly text. Keep the audience in mind.

28. I need help / I require assistance

Register shift: Need help is direct and neutral; require assistance is more formal/institutional. Example: “I need help with this form.” / “I require assistance with this form.”

Precision check: The formal version can sound impersonal. In many professional contexts, “I need help” is perfectly appropriate.

29. what’s up? / how are you?

Register shift: What’s up? is casual; How are you? is neutral and more suitable in polite/formal interaction. Example: “Hey, what’s up?” / “Good afternoon. How are you?”

Precision check: How are you? can also be casual. Register comes from greeting, titles and surrounding language.

30. hi / good morning

Register shift: Hi is informal-neutral; Good morning is more formal and situationally polite. Example: “Hi, Ms Tan.” / “Good morning, Ms Tan.”

Precision check: Hi is widely acceptable in professional contexts too; the contrast is a tendency, not a prohibition.

31. bye / goodbye

Register shift: Bye is casual; goodbye is fuller and slightly more formal. Example: “Bye! See you later.” / “Goodbye, and thank you for your time.”

Precision check: Many formal messages end with written closings rather than goodbye.

32. sure / certainly

Register shift: Sure is conversational; certainly is more formal and can express confident agreement. Example: “Sure, I can do that.” / “Certainly, I can provide the information.”

Precision check: Certainly can sound overly emphatic if the context only requires a simple yes.

33. okay / acceptable

Register shift: Okay is conversational and broad; acceptable is formal when judging whether something meets a standard. Example: “This version is okay.” / “This version is acceptable for submission.”

Precision check: Acceptable may imply minimum standard rather than enthusiastic approval.

34. no problem / you’re welcome

Register shift: No problem is casual; you’re welcome is more conventional and neutral-formal after thanks. Example: “Thanks!” “No problem.” / “Thank you.” “You’re welcome.”

Precision check: Both are polite in suitable contexts. Register is social, not a correctness ranking.

35. I get it / I understand

Register shift: I get it is informal; I understand is neutral-formal. Example: “I get it now.” / “I understand the procedure now.”

Precision check: Get has many meanings; the formal shift also removes ambiguity.

36. I don’t know / I am not certain

Register shift: I don’t know is direct; I am not certain is more cautious/formal when uncertainty rather than total lack of knowledge is meant. Example: “I don’t know the answer.” / “I am not certain that the figure is correct.”

Precision check: Do not replace complete lack of knowledge with mild uncertainty if that changes meaning.

37. I think / in my view

Register shift: I think is neutral; in my view is a more formal framing for opinion. Example: “I think the second design is clearer.” / “In my view, the second design is clearer.”

Precision check: In academic writing, evidence may matter more than an opinion frame.

38. you should / I recommend that

Register shift: You should is direct advice; I recommend that is more formal and explicitly advisory. Example: “You should check the source.” / “I recommend that the source be checked.”

Precision check: The formal form can become passive or impersonal; preserve who is responsible where relevant.

39. give me… / could I have…?

Register shift: Give me is direct and may sound abrupt; could I have is more polite for ordinary requests. Example: “Give me the form.” / “Could I have the form, please?”

Precision check: Direct imperatives are appropriate in some urgent or instructional settings.

40. wait / please wait a moment

Register shift: Wait is direct; please wait a moment is more polite and measured. Example: “Wait—I need to check.” / “Please wait a moment while I verify the information.”

Precision check: Adding politeness also changes rhythm and sometimes perceived urgency.

Return to the register routes.

Pairs 41–60: school, report and academic vocabulary

These pairs help students shift from conversational wording into school reports, explanations and academic prose. The formal choice should add precision or fit the genre—not merely sound longer.

41. look at / examine

Register shift: Look at is broad and conversational-neutral; examine is more formal when the action means inspect carefully. Example: “Look at the chart again.” / “Examine the chart for changes in the final column.”

Precision check: Examine implies closer inspection. Do not use it when the action is only glance or view.

42. talk about / discuss

Register shift: Talk about is conversational; discuss is concise and common in academic/formal writing. Example: “We talked about the problem.” / “The report discusses the problem.”

Precision check: Discuss normally takes the topic directly: discuss the issue, not discuss about the issue in standard usage.

43. find out / determine

Register shift: Find out is conversational-neutral; determine is more formal when the meaning is establish through evidence or calculation. Example: “We found out the total.” / “The group determined the total from the verified records.”

Precision check: Determine can sound more conclusive. Do not use it when the information was merely heard casually.

44. show / demonstrate

Register shift: Show is broad; demonstrate is more formal when evidence or a process makes something clear. Example: “The results show a difference.” / “The results demonstrate a consistent difference.”

Precision check: Demonstrate can imply stronger evidential support. Avoid upgrading weak evidence through vocabulary alone.

45. point out / indicate

Register shift: Point out is neutral; indicate is more formal when data, signs or evidence suggest something. Example: “Tricia pointed out the error.” / “The data indicate a possible error.”

Precision check: Indicate is not always a direct synonym for a person verbally pointing something out.

46. think about / consider

Register shift: Think about is neutral; consider is more formal when weighing an idea or option. Example: “Think about the second option.” / “Consider the second option before deciding.”

Precision check: Consider often implies deliberate attention, not merely having a thought.

47. deal with / address

Register shift: Deal with is neutral and flexible; address is formal when meaning tackle or respond to an issue. Example: “The plan deals with the timing problem.” / “The plan addresses the timing problem.”

Precision check: Address can also mean speak to or location; context must select the intended sense.

48. keep / retain

Register shift: Keep is neutral; retain is more formal when preserving possession, information or a feature. Example: “Keep the original heading.” / “Retain the original heading in the final version.”

Precision check: Retain is not natural for every everyday sense of keep, such as keep walking.

49. leave out / omit

Register shift: Leave out is conversational-neutral; omit is formal and precise for exclusion from a text, list or process. Example: “Leave out the repeated sentence.” / “Omit the repeated sentence from the final draft.”

Precision check: Omit can sound deliberate; if something was forgotten accidentally, say so.

50. go up / increase

Register shift: Go up is conversational; increase is more formal for quantities, rates and measurements. Example: “Attendance went up.” / “Attendance increased by twelve per cent.”

Precision check: Increase fits measurable change; it is not a replacement for physical movement such as go up the stairs.

51. go down / decrease

Register shift: Go down is conversational; decrease is more formal for measurable reduction. Example: “The error rate went down.” / “The error rate decreased after revision.”

Precision check: Decrease refers to amount/level, not all senses of go down.

52. make sure / ensure

Register shift: Make sure is neutral; ensure is formal and concise when meaning make certain. Example: “Make sure the file is saved.” / “Ensure that the file is saved.”

Precision check: Ensure is different from assure, which commonly takes a person.

53. set up / establish

Register shift: Set up is neutral; establish is more formal when creating a system, process or organisation. Example: “The team set up a checking system.” / “The team established a checking system.”

Precision check: For physically arranging chairs or equipment, set up may be more natural than establish.

54. put together / compile

Register shift: Put together is conversational; compile is formal when collecting information into an organised whole. Example: “We put together the results.” / “The group compiled the results into a summary table.”

Precision check: Compile suits information or collections, not every physical assembly task.

55. write down / record

Register shift: Write down is conversational-neutral; record is more formal when storing information systematically. Example: “Write down the final number.” / “Record the final number in the table.”

Precision check: Record can imply an official or systematic entry; choose it when that nuance fits.

56. check / verify

Register shift: Check is neutral and broad; verify is formal when confirming accuracy or truth against evidence. Example: “Check the date.” / “Verify the date against the original source.”

Precision check: Verification requires a basis for confirmation. Do not use verify when only glancing at something.

57. say / state

Register shift: Say is neutral; state is more formal when presenting information explicitly in writing or speech. Example: “The notice says the room is closed.” / “The notice states that the room is closed.”

Precision check: State suggests explicit wording; infer should be used when the message is indirect.

58. give / provide

Register shift: Give is broad; provide is more formal when supplying information, support or resources. Example: “Give two examples.” / “Provide two examples to support the explanation.”

Precision check: Provide is not natural for every transfer sense of give, especially idioms.

59. use / employ

Register shift: Use is neutral and usually best; employ is more formal when meaning make use of a method, strategy or technique. Example: “Use a table to organise the data.” / “The report employs a table to organise the data.”

Precision check: Employ can sound inflated in simple writing. Use remains correct and often clearer.

60. try / attempt

Register shift: Try is neutral; attempt is more formal when making an effort to do something. Example: “Try to solve the problem.” / “The group attempted to solve the problem using a second method.”

Precision check: Attempt can emphasise effort without success. Do not imply failure unless context supports it.

Return to the register routes.

Pairs 61–80: informal phrasal choices to formal alternatives

Phrasal verbs are not inferior English. Many are natural in speech and strong writing. These pairs show formal alternatives for situations where a report, notice or academic explanation benefits from a more compact or specialised verb.

61. put off / postpone

Register shift: Put off is common and conversational; postpone is more formal for delaying an event or action. Example: “They put off the meeting.” / “The meeting was postponed until Friday.”

Precision check: Postpone covers the delay sense of put off, not the separate sense of discourage.

62. call off / cancel

Register shift: Call off is conversational-neutral; cancel is more formal and direct. Example: “They called off the event.” / “The organisers cancelled the event.”

Precision check: Both mean the planned event will not proceed as scheduled; do not confuse with postpone.

63. look into / investigate

Register shift: Look into is neutral; investigate is more formal when examining a problem systematically. Example: “We’ll look into the error.” / “The team will investigate the source of the error.”

Precision check: Investigate may imply a more systematic process than a brief check.

64. find out / ascertain

Register shift: Find out is common; ascertain is formal and advanced when meaning establish a fact with care. Example: “We need to find out the date.” / “The editor sought to ascertain the correct date.”

Precision check: Ascertain is rare in everyday speech and can sound unnecessarily stiff for Primary 5 writing.

65. come up with / devise

Register shift: Come up with is conversational; devise is formal when creating a plan, method or solution. Example: “They came up with a new system.” / “They devised a new checking system.”

Precision check: Devise fits intentional creation, not every idea that happens to occur.

66. carry out / conduct

Register shift: Carry out is neutral-formal; conduct is more formal for investigations, interviews, surveys and procedures. Example: “They carried out a survey.” / “The students conducted a survey.”

Precision check: Conduct does not replace carry out in every physical or everyday task.

67. bring up / raise

Register shift: Bring up is conversational; raise is more formal when introducing an issue, concern or question. Example: “Alicia brought up the missing permission.” / “Alicia raised the issue of the missing permission.”

Precision check: Raise has many other meanings; the formal shift applies to topic introduction.

68. go over / review

Register shift: Go over is conversational; review is more formal when examining material again. Example: “Go over the instructions.” / “Review the instructions before submission.”

Precision check: Review can also mean evaluate, not only reread. Context selects the sense.

69. work out / calculate

Register shift: Work out is conversational; calculate is formal and precise for numerical computation. Example: “Work out the total.” / “Calculate the total from the figures provided.”

Precision check: Work out also means solve, understand or exercise; calculate covers only the numerical sense.

70. sort out / resolve

Register shift: Sort out is conversational; resolve is more formal when solving a problem or disagreement. Example: “We sorted out the schedule problem.” / “The team resolved the scheduling problem.”

Precision check: Resolve may imply successful completion. Do not use it while the issue remains open.

71. rule out / eliminate

Register shift: Rule out is neutral; eliminate is more formal when removing a possibility from consideration. Example: “The evidence rules out Monday.” / “The evidence eliminates Monday as a possible date.”

Precision check: Eliminate can sound absolute; ensure the evidence genuinely excludes the option.

72. turn down / reject

Register shift: Turn down is conversational; reject is more formal when refusing an offer, proposal or application. Example: “They turned down the proposal.” / “The committee rejected the proposal.”

Precision check: Turn down also means reduce volume; reject covers the refusal sense only.

73. hand in / submit

Register shift: Hand in is common school language; submit is more formal and used in academic/administrative contexts. Example: “Hand in the form by Friday.” / “Submit the completed form by Friday.”

Precision check: Submit can be electronic or physical; hand in usually suggests delivery to a person/place.

74. fill in / complete

Register shift: Fill in is neutral; complete is more formal for forms and required information. Example: “Fill in the form.” / “Complete the form before submission.”

Precision check: Complete may mean finish the whole form, not merely one blank.

75. go on / continue

Register shift: Go on is conversational; continue is neutral-formal for ongoing action. Example: “The discussion went on.” / “The discussion continued for another ten minutes.”

Precision check: Go on has other senses such as happen or encourage someone to speak.

76. cut down / reduce

Register shift: Cut down is conversational; reduce is formal when lowering quantity, length or frequency. Example: “Cut down the repeated wording.” / “Reduce repeated wording in the final draft.”

Precision check: Cut down can also mean fell a tree; reduce covers the quantity sense.

77. get back to / respond to

Register shift: Get back to is conversational; respond to is more formal in correspondence and reports. Example: “I’ll get back to you tomorrow.” / “I will respond to your question tomorrow.”

Precision check: Respond to can sound more formal but does not always carry the same promise of delayed follow-up.

78. take part in / participate in

Register shift: Take part in is neutral; participate in is more formal and common in reports. Example: “Thirty students took part in the survey.” / “Thirty students participated in the survey.”

Precision check: Participate usually takes in before the activity.

79. look over / inspect

Register shift: Look over is conversational; inspect is more formal when checking something carefully for condition or compliance. Example: “Look over the equipment.” / “Inspect the equipment before use.”

Precision check: Inspect implies a closer or more systematic check.

80. put together / assemble

Register shift: Put together is conversational; assemble is more formal when joining physical parts into a whole. Example: “Put the model together.” / “Assemble the model according to the diagram.”

Precision check: Assemble also means gather people; context matters.

Return to the register routes.

Pairs 81–100: tone, precision and audience-sensitive choices

These pairs show why register and meaning cannot be separated. A more formal word may also change precision, certainty or connotation. Students should preserve the intended claim rather than upgrading every casual word automatically.

81. awesome / excellent

Register shift: Awesome is enthusiastic and informal; excellent is more neutral-formal for evaluation. Example: “That was awesome!” / “The presentation was excellent.”

Precision check: Excellent still expresses strong praise. Do not use it if the evidence supports only acceptable or adequate. Write one context where the informal choice is better and one where the formal choice is better.

82. weird / unusual

Register shift: Weird is conversational and can sound judgmental; unusual is more neutral and formal. Example: “That result looks weird.” / “The result is unusual and requires further checking.”

Precision check: Unusual describes rarity/difference without necessarily implying badness. Write one context where the informal choice is better and one where the formal choice is better.

83. stuff / materials

Register shift: Stuff is vague and informal; materials is more formal when referring to resources used for a task. Example: “Bring your stuff.” / “Bring the required materials.”

Precision check: Materials is not a universal replacement for stuff; the intended category must actually be materials. Write one context where the informal choice is better and one where the formal choice is better.

84. thing / item

Register shift: Thing is broad and conversational; item is more precise/formal for one object, entry or element in a list. Example: “Check that thing on the list.” / “Check the final item on the list.”

Precision check: Item works when something is countable within a set; matter/issue may be better for abstract things. Write one context where the informal choice is better and one where the formal choice is better.

85. lots of / numerous

Register shift: Lots of is informal-neutral; numerous is formal for many countable items. Example: “Lots of students replied.” / “Numerous students replied.”

Precision check: Numerous can sound inflated if the number is small or already stated exactly. Write one context where the informal choice is better and one where the formal choice is better.

86. a bit / slightly

Register shift: A bit is conversational; slightly is more formal for small degree. Example: “The second version is a bit clearer.” / “The second version is slightly clearer.”

Precision check: Slightly is useful for degree, not every sense of a bit. Write one context where the informal choice is better and one where the formal choice is better.

87. really important / highly important

Register shift: Really is conversational emphasis; highly can be more formal with selected adjectives. Example: “This step is really important.” / “This step is highly important.”

Precision check: Highly important is possible but often less natural than very important or essential. Formality should not override natural collocation. Write one context where the informal choice is better and one where the formal choice is better.

88. right / correct

Register shift: Right is broad and conversational-neutral; correct is more formal for accuracy. Example: “Your answer is right.” / “Your answer is correct.”

Precision check: Right also means direction, entitlement or moral correctness; correct narrows to accuracy. Write one context where the informal choice is better and one where the formal choice is better.

89. wrong / incorrect

Register shift: Wrong is broad; incorrect is more formal when an answer, fact or form is inaccurate. Example: “The date is wrong.” / “The date is incorrect.”

Precision check: Incorrect is not a substitute for morally wrong or inappropriate behaviour. Write one context where the informal choice is better and one where the formal choice is better.

90. cheap / inexpensive

Register shift: Cheap is common and can carry a negative connotation; inexpensive is more neutral when meaning low in price. Example: “The bag was cheap.” / “The bag was inexpensive.”

Precision check: Cheap can imply poor quality; inexpensive focuses on price. Register and connotation both matter. Write one context where the informal choice is better and one where the formal choice is better.

91. old version / previous version

Register shift: Old is broad; previous is more precise/formal when referring to the version immediately before the current one. Example: “Use the old version for comparison.” / “Compare the current document with the previous version.”

Precision check: Previous is temporal/sequence-specific and may not mean very old. Write one context where the informal choice is better and one where the formal choice is better.

92. new version / revised version

Register shift: New is broad; revised is more precise when a version has been changed after review. Example: “Use the new version.” / “Use the revised version dated 24 September.”

Precision check: Revised says why it is new; use it only if revision actually occurred. Write one context where the informal choice is better and one where the formal choice is better.

93. get better / improve

Register shift: Get better is conversational; improve is neutral-formal and concise. Example: “The results got better.” / “The results improved after the revision.”

Precision check: Improve can describe quality or performance; avoid implying cause unless evidence supports it. Write one context where the informal choice is better and one where the formal choice is better.

94. get worse / deteriorate

Register shift: Get worse is conversational; deteriorate is formal for declining condition or performance. Example: “The print quality got worse.” / “The print quality deteriorated over time.”

Precision check: Deteriorate may sound too strong for a tiny temporary decline. Write one context where the informal choice is better and one where the formal choice is better.

95. a chance / an opportunity

Register shift: Chance is broad and conversational; opportunity is more formal when meaning a favourable possibility to act. Example: “I had a chance to speak.” / “I had an opportunity to present the findings.”

Precision check: Chance can also mean probability or randomness; opportunity does not cover those senses. Write one context where the informal choice is better and one where the formal choice is better.

96. a problem / an issue

Register shift: Problem is direct and neutral; issue is often more formal and sometimes softer in institutional writing. Example: “There is a problem with the schedule.” / “There is an issue with the schedule.”

Precision check: Issue can sound euphemistic. Use problem when the situation genuinely requires directness. Write one context where the informal choice is better and one where the formal choice is better.

97. idea / proposal

Register shift: Idea is broad; proposal is formal when an idea is formally put forward for consideration. Example: “Kai Kai had an idea for the layout.” / “Kai Kai submitted a proposal for the revised layout.”

Precision check: A proposal is not just any thought; it is presented for consideration or action. Write one context where the informal choice is better and one where the formal choice is better.

98. answer / response

Register shift: Answer is neutral; response is more formal and broader in surveys, correspondence and analysis. Example: “Write your answer.” / “Record each participant’s response.”

Precision check: Response can include reactions that are not answers to questions. Write one context where the informal choice is better and one where the formal choice is better.

99. proof / evidence

Register shift: Proof often suggests conclusive demonstration; evidence is more cautious and formal in many analytical contexts. Example: “This is proof the method works.” / “This provides evidence that the method may be effective.”

Precision check: Do not weaken or strengthen certainty purely for style. Choose according to evidential strength. Write one context where the informal choice is better and one where the formal choice is better.

100. guess / estimate

Register shift: Guess is informal when based on little information; estimate is more formal when based on some method or evidence. Example: “I guessed the number.” / “The team estimated the number from the sample.”

Precision check: Estimate is not simply a formal guess. It should involve a basis or method. Write one context where the informal choice is better and one where the formal choice is better.

Tone laboratory

Take cheap/inexpensive, problem/issue, proof/evidence and guess/estimate. These are not simple formality swaps. Each pair changes connotation or evidential precision. Explain what would be lost if the words were treated as interchangeable.

Return to the register routes, or continue to the register-selection method.

How to choose formal or informal vocabulary without changing the message

Register control begins with a simple principle: the meaning, audience, purpose and relationship between people come before the vocabulary upgrade. Students often make one of two errors. Some write everything casually because informal English feels natural. Others replace ordinary words with longer ones until the sentence becomes stiff or inaccurate. Strong control means choosing the level that fits.

Step 1: identify the audience

Ask who will read or hear the message. A close friend, sibling or classmate normally allows a more relaxed register. A teacher, organiser, unknown adult, formal audience or public reader may require fuller wording, clearer politeness and fewer casual shortcuts. Audience does not automatically decide every word, but it sets expectations.

Compare: “Hey, can you send me the file?” to a friend and “Good afternoon. Could you please send me the updated file?” to an organiser. The request is the same. Greeting, contraction, modal phrasing and politeness shift because the social relationship changes.

Step 2: identify the purpose

Is the writer chatting, requesting, informing, reporting, apologising, persuading, explaining or recording evidence? Formality often follows purpose. A report benefits from precise verbs such as indicate, verify, increase and omit. Friendly conversation often sounds better with show, check, go up and leave out.

Purpose also changes sentence framing. “I want the form” expresses desire. “I would like a copy of the form” makes a polite request. “Please provide the completed form by Friday” gives a formal instruction. The same topic can require different structures because the communicative job differs.

Step 3: preserve the factual meaning

Register transformation is not permission to strengthen the claim. “The method was good” cannot automatically become “The method was highly effective” because effective has a narrower meaning: it achieved its purpose. “I guess there were about fifty people” cannot automatically become “The team estimated fifty participants” unless the number was actually based on a method or evidence.

Before changing vocabulary, paraphrase the original message in plain language. Then choose formal wording that expresses the same proposition. If the formal sentence becomes more certain, more polite, more negative or more specific than the original, check whether the shift is intended.

Step 4: decide how formal the whole message needs to be

Register is a continuum, not two sealed boxes. “Hi, could you please send me the file?” combines an informal greeting with a polite request and may be perfectly natural in a school email to a familiar teacher. “Dear Sir or Madam, I would be grateful if you could provide…” is much more formal. Both can be correct depending on context.

Students should therefore avoid labeling isolated words as permanently formal or informal. The article uses pair labels as tendencies. Real register emerges from the sentence, relationship and genre.

Step 5: choose vocabulary that naturally belongs together

A formal word inside an otherwise casual sentence can sound awkward: “Hey, could you ascertain whether the pizza has arrived?” The verb ascertain is possible English but mismatched to the situation. “Hey, can you find out whether the pizza has arrived?” is natural.

Likewise, a formal report that says “lots of stuff went wrong” mixes an imprecise informal phrase with an institutional genre. Better: “Several problems occurred during the trial,” if that is the intended meaning. Collocation and genre should reinforce one another.

Step 6: check contractions

Contractions such as can’t, won’t, I’m and they’re are normal standard English, especially in speech and friendly writing. Very formal writing often uses full forms: cannot, will not, I am, they are. The absence of contractions contributes to formality but does not automatically create it.

“I cannot attend” is more formal than “I can’t attend,” but “I cannot attend coz something came up” remains register-mixed. Students should treat contractions as one signal among many, not a complete rule.

Step 7: inspect phrasal verbs, but do not ban them

Formal writing sometimes prefers single-word alternatives: put off → postpone, look into → investigate, hand in → submit. But many phrasal verbs are standard in formal English: carry out, point out, set out, follow up on. Replacing every multi-word verb can make prose less natural.

Use the alternative that fits meaning and genre. “The study carried out three tests” is not automatically improved by replacing carried out with conducted if the surrounding wording already reads well.

Step 8: inspect vague words

Words such as stuff, thing, good, bad, weird and big can be useful in ordinary speech but may be too vague for academic writing. Formal revision should increase precision: stuff → materials, good method → effective method, weird result → unusual result, big increase → substantial increase if the data justify it.

Precision is more important than formality. “Large problem” may be formal-sounding but less precise than “serious scheduling problem.” The writer should name the relevant dimension.

Step 9: inspect politeness and directness

Formal requests often use modal verbs and polite framing: “Could you please…?”, “I would be grateful if…”, “Please provide…”. Informal requests can be shorter: “Can you send…?” or “Send me the photo when you can.” The key is not maximum politeness; it is appropriate politeness.

In urgent safety instructions, direct language can be better: “Leave the room now.” Turning it into “I would be grateful if you could consider leaving the room” would be inappropriate. Register must serve purpose.

Step 10: inspect emotional intensity

Informal language often uses intensifiers and evaluative words: really, super, awesome, terrible, weird. Formal writing usually benefits from evidence-based description: “The method reduced errors by half” rather than “The method was super awesome.” But emotional language remains appropriate in dialogue, reviews and personal writing.

Removing emotion is not always the goal. A speech or personal reflection may need warmth. Formality adjusts expression; it should not erase the writer’s purpose or voice.

Step 11: inspect sentence structure

Informal English often tolerates fragments, ellipsis and conversational openings: “Can’t make it. Sorry!” Formal writing more often uses complete sentences: “I am unable to attend the meeting and apologise for the late notice.” The change involves syntax as well as vocabulary.

Do not make formal sentences unnecessarily long. “Please send the file by noon” is concise, complete and formal enough for many situations. Complexity is not a requirement of professionalism.

Step 12: inspect pronouns and viewpoint

Some formal genres reduce first- and second-person language: “I think the method works” may become “The results suggest that the method is effective.” This changes more than register; it moves from personal opinion to evidence-based claim. Use the shift only when the evidence supports it.

Other formal texts appropriately use I or we: reflective writing, letters, speeches, research reports describing actions. Register rules depend on genre conventions.

Step 13: inspect discourse connectors

Conversation often uses so, but, plus, anyway. Formal prose may use therefore, however, in addition, in any case. These are not simple one-for-one substitutions because punctuation and logical force differ. “So” can mark result casually; “therefore” often presents a more explicit logical consequence.

Teach the relationship first, connector second. Otherwise students may insert however or therefore where the logic does not fit.

Step 14: perform the reverse translation

After converting informal to formal, convert the sentence back into natural informal English. “I would like to inquire whether the revised timetable is available” might become “Can I check if the new timetable is out yet?” If the reverse version changes the meaning, the formal transformation may have drifted.

Two-way translation is one of the strongest register tests because it checks semantic preservation rather than surface sophistication.

Step 15: use a three-question final check

Ask: Does the wording fit the audience? Does it fit the purpose/genre? Does it preserve the intended meaning? If all three answers are yes, the register choice is likely sound. If one answer is no, revise only that layer.

Return to the register routes, or continue to the worked exercises.

Formal and informal language exercises with worked answers

These exercises test register choice, meaning preservation and audience awareness. Complete each set before opening the worked answers. More than one wording may be acceptable if it fits the audience and preserves the message.

Set A: choose the more suitable register

A1. A message to a close friend: “I am unable to join you this afternoon” or “Can’t make it this afternoon—sorry!” Which is more natural?

A2. A school report: “Lots of stuff went wrong” or “Several problems occurred during the trial”?

A3. A formal request to an organiser: “Send me the form” or “Could you please send me the form?”

A4. Dialogue between friends: “That was awesome!” or “The performance was excellent in every respect”?

A5. A science explanation: “The temperature went up” or “The temperature increased by five degrees”?

A6. A notice: “Please submit the completed form by Friday” or “Hand this thing in sometime soon”?

A7. A teacher speaking warmly to a student: “Can you check this again?” or “Please verify the document against the primary source before resubmission”?

A8. A formal email opening: “Hey, what’s up?” or “Good morning. I am writing regarding…”?

Worked answers: Set A

A1: The casual version normally fits a close friend better. The formal version is grammatical but socially distant for an ordinary text.

A2: “Several problems occurred during the trial” is more precise and suitable for a report. “Stuff” is vague.

A3: The polite modal request fits a formal organiser relationship better.

A4: “That was awesome!” sounds natural in friendly dialogue. Formal evaluation can be useful in a review, but not every casual reaction needs upgrading.

A5: The measurable formal version is stronger because it adds exact data, not merely formality.

A6: The first version is precise, formal and deadline-specific.

A7: Either can fit depending on lesson context, but the first is warmer and more natural in ordinary teacher–student interaction. Formality should not become robotic.

A8: The second fits a formal email opening.

Set B: informal to formal

Rewrite each sentence for a formal school report or email.

B1. “We found out that the old file was wrong.”

B2. “A lot of kids didn’t hand in the form.”

B3. “The group put off the test because the printer was acting weird.”

B4. “Can you send me the new timetable?”

B5. “We looked into it and sorted out the problem.”

B6. “The number went up a lot.”

B7. “I think the second idea is way better.”

B8. “They left out the last bit.”

Possible answers: Set B

B1: “The group determined that the previous file contained an error.” This is only appropriate if the group actually used evidence to establish the error.

B2: “Many children did not submit the form.”

B3: “The group postponed the test because the printer was functioning unusually.” Better still, name the actual fault if known: “because the printer repeatedly jammed.” Precision beats vague formality.

B4: “Could you please send me the revised timetable?”

B5: “The group investigated the issue and resolved the problem.” Use resolved only if it was genuinely solved.

B6: “The number increased substantially.” If the actual amount is known, state it instead.

B7: “In my view, the second proposal is considerably stronger.” Better in evidence-based writing: state why it is stronger.

B8: “They omitted the final section.” Only use section if the omitted material really is a section.

Set C: formal to natural informal English

Rewrite each sentence for a friendly message or ordinary conversation without changing the meaning.

C1. “I am unable to attend the activity this afternoon.”

C2. “Could you please provide the photograph when convenient?”

C3. “I would like to inquire whether the room is available.”

C4. “The organisers postponed the meeting until next week.”

C5. “Please inform me when the revised version is ready.”

C6. “The result appears unusual and may require further investigation.”

Possible answers: Set C

C1: “I can’t make it this afternoon.”

C2: “Can you send me the photo when you get a chance?”

C3: “Can I check if the room is free?”

C4: “They put the meeting off until next week.”

C5: “Let me know when the new version is ready.”

C6: “The result looks weird, so we might need to check it again.” The informal version is natural, but weird can sound more evaluative than unusual.

Set D: preserve certainty

Decide whether each formal rewrite changes the strength of the original claim.

D1. “I guess the method helped” → “The evidence proves that the method was effective.”

D2. “The result looks a bit different” → “The result is significantly different.”

D3. “Maybe the date is wrong” → “The date may be incorrect.”

D4. “The new system worked well for these two groups” → “The new system is universally effective.”

D5. “We checked the date against the source” → “We verified the date against the source.”

Worked answers: Set D

D1: Yes, drastically. Guess/helped becomes proof/effective. Formality has created unjustified certainty.

D2: Yes. Slight difference becomes statistical or practical significance. Do not use significantly without evidence.

D3: Usually no major certainty change. “May be incorrect” preserves possibility reasonably well.

D4: Yes. Evidence from two groups cannot justify universal effectiveness.

D5: Often acceptable if the source is authoritative enough to confirm the date. Verify should have a genuine confirmation basis.

Set E: choose precision over formality

E1. Replace “The method was good” with a precise evaluation if the method reduced errors.

E2. Replace “The result was weird” if the result differed from the expected pattern.

E3. Replace “a big change” if the recorded value rose from 20 to 80.

E4. Replace “lots of people” if the exact count is 146.

E5. Replace “some stuff was missing” when the missing items were two consent forms and one label.

Possible answers: Set E

E1: “The method was effective at reducing errors.”

E2: “The result was unusual because it did not follow the expected pattern.”

E3: “The value increased from 20 to 80.” Exact data are stronger than an adjective.

E4: “A total of 146 people attended.”

E5: “Two consent forms and one label were missing.”

Set F: mixed-register repair

Repair the mismatched register while preserving meaning.

F1. “Dear Sir, hey, can you shoot me the form?”

F2. “Yo Kai Kai, I would be grateful if you could accompany me to lunch.”

F3. “The report indicates that lots of weird stuff happened.”

F4. “The kids commenced playing after lunch.”

F5. “Could you please kinda check this thing?”

Possible answers: Set F

F1 formal: “Dear Sir, could you please send me the form?”

F2 informal: “Hey Kai Kai, want to have lunch together?”

F3 formal: “The report indicates that several unusual events occurred.” Better still, name the events.

F4 natural neutral: “The children started playing after lunch.” Commenced is unnecessarily formal for an ordinary action.

F5 polite-neutral: “Could you please check this?” If the object can be named, replace this with the specific noun.

Diagnostic use

If a learner always chooses the longest word, the problem is “formal = difficult” thinking. If a learner never changes vocabulary but changes only greetings, the problem is limited register range. If meaning drifts during rewriting, the priority is semantic preservation. If formal writing remains vague, the priority is precision rather than formality itself.

Return to the register routes, or continue to the original casebooks.

Original register casebooks: same facts, different audiences

The following casebooks are original fiction created for this collection. Their people, messages and documents are invented teaching material. Read each version for meaning first, then track how vocabulary, sentence structure, politeness and precision change with audience and purpose.

Casebook 1: The message that sounded wrong in the right grammar

Kai Kai needed the revised timetable from Alicia. He first sent a message that said, “Dear Alicia, I would be most grateful if you could provide the aforementioned timetable at your earliest convenience.”

Alicia replied almost immediately: “You can just ask me normally.”

The grammar was correct. The register was not wrong in an absolute sense; it was simply much more formal than their ordinary relationship required. Kai Kai rewrote it: “Hi Alicia, can you send me the new timetable when you get a chance? Thanks.”

Later that afternoon, he needed to ask an external organiser for the same document. He copied the friendly message but realised that “when you get a chance” and the casual greeting might sound too relaxed for a first contact. He changed it to: “Good afternoon. Could you please send me the revised timetable when convenient? Thank you.”

Tricia compared the three versions. The first was over-formal for a friend. The second was natural for a familiar peer. The third was polite and professional for an unfamiliar organiser. None changed the central fact: Kai Kai wanted the revised timetable.

Then Alicia asked him to write a formal record of the exchange for the project log. Kai Kai wrote: “The revised timetable was requested from the organiser and received later that afternoon.” Now the purpose had changed again. The project log did not need a greeting, request wording or thanks. It needed a concise record of action.

“So formal does not mean adding polite phrases everywhere,” Kai Kai said.

“Exactly,” Tricia replied. “A formal email and a formal project log are both formal, but they have different jobs.”

They made a four-column table: friend text, formal email, project log, public notice. Under each they wrote the same information in a different way. The exercise showed that audience and genre work together. Register is not a switch marked casual/formal; it is a set of choices shaped by the communication situation.

Questions: The message that sounded wrong

R1. Why is Kai Kai’s first message grammatically correct but socially mismatched?

R2. Which features make the second message natural for a friend?

R3. Which changes make the third message more suitable for an unfamiliar organiser?

R4. Why does the project log remove the greeting and polite request?

R5. What fact remains unchanged in all versions?

R6. What does the four-column table teach about formal language?

Worked answers: Casebook 1

R1: The wording is excessively distant and bureaucratic for a familiar friend. Correct grammar does not guarantee appropriate register.

R2: Hi, can you, when you get a chance, and thanks create a friendly, polite but relaxed tone.

R3: Good afternoon, could you please, revised timetable, when convenient and thank you create a more professional first-contact register.

R4: The project log records the action and outcome rather than reenacting the social interaction.

R5: Kai Kai requests the revised timetable.

R6: Formality varies by genre. A formal email, report, notice and log use different conventions even when all are non-casual.

Casebook 2: From “weird stuff” to an accurate report

During a display trial, two labels fell off, one tablet restarted unexpectedly, and four visitors chose the wrong tray. After the session, Kai Kai told Tricia, “A lot of weird stuff went wrong.”

For conversation, the sentence was understandable. For the project report, Alicia asked him to rewrite it.

Kai Kai’s first formal attempt was: “Numerous anomalous circumstances transpired during the operational period.”

Tricia laughed. “That sounds formal, but now I don’t know what happened.”

They returned to the recorded facts. The final report said: “During the trial, two labels became detached, one tablet restarted unexpectedly, and four visitors selected the incorrect tray.”

The revision was more formal, but more importantly it was more precise. “A lot” became exact counts. “Stuff” disappeared because the events were named. “Weird” became specific descriptions rather than an evaluative adjective. “Went wrong” became verbs describing what occurred.

Next, Kai Kai wrote, “The new labels were highly effective.” Alicia asked what evidence supported that wording. The four visitors who selected the wrong tray had all used the new labels. The claim was not supported.

He changed it to: “The new labels did not prevent all selection errors during this trial; four visitors still selected the incorrect tray.” The sentence sounded less impressive but was more accurate.

Tricia then asked him to turn the report back into an informal spoken update for a classmate. He said, “Two labels fell off, the tablet restarted, and four people still picked the wrong tray, so we’ve got some things to fix.”

The informal version was not inferior. It was shorter, conversational and still factual. The successful transformation preserved the event while changing vocabulary, sentence length and tone.

At the end, Alicia wrote a rule on the board: “Formal writing is not vague language wearing a suit.” The class copied it because it summarised the central lesson: register should improve fit and precision, not hide ordinary meaning behind longer words.

Questions: From “weird stuff” to an accurate report

R7. Why is “a lot of weird stuff went wrong” acceptable in conversation but weak in a report?

R8. What is wrong with “Numerous anomalous circumstances transpired”?

R9. Which changes in the final report improve precision?

R10. Why is “highly effective” unsupported?

R11. Does the informal spoken update become less accurate? Explain.

R12. Explain the sentence “Formal writing is not vague language wearing a suit.”

Worked answers: Casebook 2

R7: Conversation can tolerate broad shorthand when listeners share context. A report must identify events precisely enough for readers who were not there.

R8: It replaces simple vagueness with formal vagueness. The reader still does not know which events occurred.

R9: Exact counts replace a lot; specific nouns replace stuff; concrete verbs describe labels detaching, a tablet restarting and visitors selecting a tray.

R10: Four visitors still made the target error, so the evidence does not justify a strong effectiveness claim.

R11: No. It remains factual while becoming shorter and more conversational. “People” replaces visitors and “picked” replaces selected, but the events stay intact.

R12: Longer or more formal-sounding vocabulary is not valuable if it reduces clarity or precision. Formal writing should communicate more appropriately, not obscure meaning.

Return to the register routes, or continue to the writing and editing clinic.

Writing and editing clinic: change register without flattening the writer’s voice

Register editing should produce language that fits the situation, not language that sounds artificially adult. The strongest Primary 5 writer can make a report precise, a formal request polite, a friendly message natural and a character’s dialogue believable. This clinic focuses on those different jobs.

Clinic 1: friendly message to formal email

Friendly message: “Hi! Can you send me the new schedule? I can’t find mine. Thanks!” Formal email: “Good afternoon. Could you please send me the revised schedule? I am unable to locate my copy. Thank you.”

The transformation changes greeting, request framing, contraction and word choice. It does not invent a reason, add urgency or change which schedule is requested. Register editing should leave the factual skeleton intact.

Clinic 2: formal email to natural friendly text

Formal: “I would appreciate it if you could inform me when the revised document is available.” Friendly: “Let me know when the new version is ready.” The friendly version is shorter and less ceremonious while preserving the request.

Students often find this reverse direction harder because they have been trained to “improve” language only by formalising it. True control is bidirectional.

Clinic 3: dialogue must sound like a person

Over-formal dialogue: “I am unable to comprehend why you proceeded without informing me.” Natural angry dialogue between classmates might be: “I don’t get why you went ahead without telling me.” Both communicate confusion and frustration, but the second sounds more plausible for the character and relationship.

Dialogue can still become formal when the character, setting or intention demands it. A student speaking during a formal presentation may say, “I do not understand why the procedure was changed.” Voice follows situation.

Clinic 4: report language should name the event

Weak informal report: “A bunch of things messed up.” Weak formal report: “Several operational complications occurred.” Strong report: “Two labels detached, one tablet restarted, and four visitors selected the wrong tray.”

The final version is not impressive because of formality. It is useful because it is specific. When possible, replace vague evaluation with observable facts.

Clinic 5: formal does not mean passive

“The form was submitted by Alicia” is formal, but “Alicia submitted the form” is equally formal and usually clearer when the actor matters. Passive voice can be useful when the actor is unknown, obvious or less important, but it is not a required feature of formal English.

Teach students to choose voice based on information structure, not a belief that passive sentences sound more advanced.

Clinic 6: remove slang without removing personality

Informal reflection: “I was super nervous, but the group was really nice.” A more formal reflection might be: “I was extremely nervous, but the group was very supportive.” Yet a personal speech may keep “really nervous” because it sounds authentic.

Register editing should preserve emotional truth. The goal is not to make every student sound like an official notice.

Clinic 7: use exact quantities where available

Informal: “Lots of people came.” Formal but vague: “Numerous people attended.” Strong report: “A total of 146 people attended.” Exact information often makes a bigger difference than a vocabulary substitution.

Students should ask whether a number, category or specific event can replace a broad word. Precision is one of the strongest markers of mature formal writing.

Clinic 8: avoid fake sophistication

Weak: “The aforementioned individual proceeded to utilise the available seating apparatus.” Clear: “The person used the available chair.” Longer words can reduce readability without adding meaning. Formal writing is not a contest to avoid common English.

Use a more specialised word only when it improves precision, fits convention or clarifies the relationship. “Verify” can be better than “check” when confirmation against evidence is important. “Utilise” is rarely better than “use” merely because it is longer.

Clinic 9: change connector register carefully

Conversational: “The file was old, so we replaced it.” Formal: “The file was outdated; therefore, we replaced it.” The formal connector makes the consequence more explicit and changes punctuation. “However” likewise differs structurally from “but.”

Students should never replace every but with however mechanically. Grammar and logical relation must survive the change.

Clinic 10: distinguish politeness from uncertainty

“Could you please send the file?” is a polite request, not a question about physical ability. “The file could be wrong” expresses possibility. Modal verbs perform different jobs. Students should not interpret every could as uncertainty merely because it sounds softer.

When formalising requests, preserve the speech act: request, not speculation.

Clinic 11: distinguish caution from vagueness

Academic caution can be precise: “The results suggest that the revision may improve readability for this group.” Vague writing is different: “Maybe it sort of works.” The formal sentence states the evidence level, population and outcome.

Teach students to hedge for a reason—limited evidence, uncertainty or scope—not because formal writing should sound unsure.

Clinic 12: preserve responsibility

Informal: “I forgot to send the file.” Weak formalisation: “The file was not sent.” The passive version removes responsibility. A better formal version is “I did not send the file as required and apologise for the oversight.”

Register should not be used to hide agency when responsibility is relevant.

Clinic 13: public notices need clarity before politeness

Weak: “Would visitors perhaps consider refraining from entering this area?” Clear notice: “Please do not enter this area.” Public instructions often need direct, respectful language. Over-softening can make requirements look optional.

The appropriate level of directness depends on whether the message is a request, rule, safety instruction or suggestion.

Clinic 14: school presentation register

Presentation opening to classmates: “Good morning. Today we’ll explain how the model works.” This is moderately formal but still natural. “Esteemed audience, we shall elucidate the operational mechanism…” would be inappropriate over-formalisation for most Primary 5 settings.

Students need a middle register: clear, confident, respectful and understandable.

Clinic 15: personal reflection register

A reflection can use first person and emotion while remaining school-appropriate: “I was disappointed by the first result, but I realised that our instructions were unclear.” There is no need to turn this into detached institutional language.

Genre matters. Formality in a reflection means coherent, respectful and precise—not emotionless.

Clinic 16: summary register

A summary should usually remove chatty framing: “Basically, they kinda figured out that the file was old” becomes “The group determined that the file was outdated.” But if “determined” overstates the evidence, “found that” may be the better neutral choice.

Formality must remain subordinate to factual accuracy.

Independent writing task: one message in four registers

Use one fact: tomorrow’s meeting has moved from Room 3 to Room 8. Write it as (1) a text to a friend, (2) a message to a teacher, (3) a public notice and (4) a project log entry. Preserve the room change and timing in every version.

Then compare greeting, pronouns, contractions, verbs, politeness, sentence length and omitted information. The strongest lesson is not which version is “best,” but why each version fits its role.

Independent editing task: formal but natural

Take a 150-word school report and highlight every word chosen mainly because it “sounds formal.” Replace any word that reduces clarity or naturalness. Keep specialised terms that add precision. The final version should be understandable to a careful reader on the first pass.

Return to the register routes, or continue to the teaching and review system.

Teaching and review system: from register recognition to flexible control

Register should be taught as a choice system rather than a list of forbidden words. Students need to recognise levels of formality, explain why a wording fits, switch registers without changing meaning, and eventually choose naturally without an explicit worksheet prompt. The teaching sequence below moves from comparison to independent production.

Stage 1: compare two versions of the same message

Give paired sentences that preserve facts: “Can’t make it today—sorry!” and “I am unable to attend today. I apologise for the late notice.” Ask what changed: contraction, sentence completeness, apology wording and tone. Then ask what did not change: absence today.

Starting from matched meanings prevents students from thinking formal language simply means “different vocabulary.”

Stage 2: identify register signals

Common informal signals include slang, conversational particles, contractions, phrasal verbs, vague nouns and direct short requests. Common formal signals include fuller sentence structure, precise nouns, conventional politeness, specialised verbs and explicit logical connectors. No signal is absolute.

Make students find at least two signals before labelling a sentence. One word such as hi should not decide the entire register by itself.

Stage 3: match register to audience cards

Prepare audience cards: close friend, classmate, teacher, principal, unknown organiser, project report reader, public visitor, younger child. Give one message and ask learners to rewrite it for two audiences.

Then compare versions. The purpose may stay constant while social distance and expected conventions change.

Stage 4: match register to genre

Use genres such as text message, email, report, notice, reflection, dialogue, presentation and project log. Formality is shaped not only by who receives the message but by what kind of text it is.

A formal project log may omit greetings completely. A formal email needs greeting and polite request. A public notice may be short and direct. Students should learn genre conventions alongside vocabulary.

Stage 5: two-way translation

Most learners practise informal → formal only. Add formal → natural informal. “I would like to inquire whether…” becomes “Can I check if…?” “Please inform me when…” becomes “Let me know when…”. Two-way practice proves that register control is flexible rather than hierarchical.

Require a meaning check after every transformation. Students should underline facts that must remain unchanged.

Stage 6: precision before sophistication

Give vague sentences and ask for a report version: “A lot of stuff happened.” The first goal is naming events, not finding impressive synonyms. “Two labels detached and one tablet restarted” is stronger than “Numerous anomalous circumstances transpired.”

This stage protects students from equating long words with mature writing.

Stage 7: certainty preservation

Give informal hedges and ask learners to formalise without strengthening them: “Maybe the date is wrong” → “The date may be incorrect.” “I think this might help” → “This may be helpful.” Then show bad transformations such as maybe → proves.

Register editing should never become evidence inflation.

Stage 8: register mixing diagnosis

Use sentences such as “Dear Sir, hey, can you shoot me the file?” and “Yo Kai Kai, I would be grateful if you could accompany me.” Students identify mismatched signals and choose a coherent target register.

Mixed register is not always wrong—real language blends levels—but deliberate school tasks benefit from recognising when the mix sounds accidental.

Stage 9: register and connotation

Compare cheap/inexpensive, weird/unusual, problem/issue, proof/evidence. The shift is not merely formal. Connotation or certainty changes. Ask students to name the semantic difference before selecting the register.

This stage connects register to the broader vocabulary system without duplicating the existing connotation owner.

Stage 10: delayed register production

After a delay, give a scenario only: “Ask an unfamiliar organiser for the revised timetable.” The learner must produce the message from scratch. Then give “Tell a close friend the same information.” The pair tests independent selection rather than sentence conversion.

Delayed production is stronger evidence than immediate rewriting because the model is absent.

A five-week adaptable review map

Week 1: everyday formal/informal pairs and audience matching. Week 2: requests, apologies, greetings and politeness. Week 3: reports, academic verbs and precision. Week 4: phrasal-to-formal alternatives and meaning boundaries. Week 5: mixed genres, two-way rewriting and independent production.

The sequence is adjustable. A student who writes strong reports but stiff dialogue needs more informal-natural production, not another week of formal vocabulary.

Build a register notebook with paired contexts

Use columns: casual/neutral form; formal alternative; meaning difference; informal context; formal context. Example: put off / postpone | delay | conversation with friend / project report. Add a warning if the formal alternative covers only one sense of the informal phrase.

The context columns are essential. Without them, students may treat one side as correct and the other as inferior.

Use error codes

AUD = audience mismatch; GEN = genre mismatch; SEM = meaning drift; PREC = vague wording; OVER = over-formal; CAS = too casual; CERT = certainty changed; POL = politeness/directness mismatch.

Error codes guide practice. OVER errors need natural simplification. SEM errors need meaning-preservation drills. PREC errors need specific nouns and data. CERT errors need evidence-aware rewriting.

Teacher prompts

Ask: “Who is the audience?” “What is the purpose?” “What facts must stay the same?” “Which words make this casual?” “Which words make this formal?” “Did the certainty change?” “Is the formal version actually clearer?” “Would a real person say this?”

These prompts gradually become internal editing questions.

Parent support through ordinary messages

Use real-life contrasts: text a friend versus email a teacher; ask a sibling versus write to an organiser. Ask the child to say the same message both ways. Keep the activity short and focused on appropriateness rather than correction-heavy grammar.

Parents can also ask why one version fits better. The explanation matters more than choosing a “formal” label.

Reading strategy: notice register before judging character

Stories may use informal language to reveal age, relationship, setting or emotion. Formal language may show distance, authority, ceremony or professionalism. Students should ask what the register contributes to characterisation rather than automatically correcting dialogue into standard formal prose.

Register becomes a reading clue as well as a writing choice.

What mastery looks like

Strong control means the learner can recognise register signals, match language to audience and genre, rewrite in both directions, preserve meaning and certainty, avoid over-formality, increase precision where needed and explain why a chosen wording fits.

Mastery is not “always formal.” It is adaptable language.

Return to the register routes, or continue to the final FAQ and transfer checks.

Primary 5 formal and informal vocabulary: final FAQ and mastery checks

What is register in English?

Register is the level and style of language chosen for a particular audience, purpose and situation. Formal and informal are broad labels within a larger continuum. A close-friend message, classroom discussion, school presentation, formal email, report and public notice can all require different combinations of vocabulary, grammar, tone and politeness.

Register is therefore not only a list of formal words. It is a relationship between language and context.

Does formal English mean better English?

No. Formal English is appropriate in some settings; informal English is appropriate in others. “Can’t make it—sorry!” can be excellent English in a friendly text and poor English in a formal report. “I am unable to attend” can be excellent in an email and unnecessarily distant between close friends.

The best choice is the one that fits the communicative situation while remaining clear and accurate.

Are contractions always informal?

Contractions are common in speech and many kinds of writing, including professional communication. Very formal styles may prefer full forms such as cannot, will not and I am, but contractions are not automatically incorrect or unprofessional.

Teach them as one register signal among many. A sentence with no contractions can still be casual; a polite professional email can still contain contractions.

Are phrasal verbs informal?

Some phrasal verbs have more formal single-word alternatives: put off/postpone, look into/investigate, hand in/submit. But many phrasal verbs are standard in formal English, including carry out, point out and set out.

Students should not replace every phrasal verb. Meaning, collocation and genre decide whether the alternative improves the sentence.

Why do formal words sometimes sound unnatural?

Because a word can be grammatical but mismatched to the social setting. “I would be grateful if you could accompany me to the canteen” is formal and correct, but a child may simply say “Want to come to the canteen?” to a close friend.

Naturalness is part of register competence. Learners need examples of real situations, not isolated word pairs alone.

What is over-formal writing?

Over-formal writing uses unnecessarily elaborate vocabulary, distant phrasing or bureaucratic structure for a simple purpose. “Please utilise the available seating apparatus” is less clear than “Please use the available chair.”

Over-formality can make writing harder to read without adding precision. The cure is usually simpler natural English, not more advanced vocabulary.

How do students know when to use a formal alternative?

Ask three questions: Who is the audience? What is the purpose or genre? Does the alternative preserve the meaning? If the formal choice makes the sentence clearer, more precise or more suitable for the setting, use it. If it only makes the sentence longer, keep the simpler form.

Register is a decision system, not a replacement chart.

Why is “kids” not always wrong in school writing?

Kids is informal but standard. It can be natural in dialogue, a personal reflection or a friendly article. Children is usually more neutral/formal and may suit reports or academic contexts better.

The choice depends on genre and voice. Marking kids as universally wrong teaches a false rule.

Should students replace “use” with “utilise” in formal writing?

Usually not. Use is standard, concise and fully acceptable in formal English. Utilise can be appropriate in specialised contexts but is often unnecessary. Longer words do not automatically create better register.

The same principle applies to many vocabulary upgrades: prefer precision and natural collocation over length.

What is the difference between formal and academic vocabulary?

Formal vocabulary concerns social and genre appropriateness. Academic vocabulary concerns words commonly useful in school, analysis and knowledge work, such as evidence, conclude, indicate and evaluate. The categories overlap but are not identical.

A word can be academic without sounding especially formal, and a formal politeness phrase may not be academic at all.

How is register different from tone?

Register concerns level/style appropriate to context; tone concerns attitude or emotional quality. A formal email can have a warm, apologetic, firm or neutral tone. An informal message can be cheerful, irritated or serious.

The two interact, but students should not assume formal always means cold or informal always means friendly.

How is register different from dialect?

Dialect is a variety of language associated with region, community or social group and can involve vocabulary, grammar and pronunciation. Register changes with situation and audience. One speaker can use the same dialect across several registers.

Students should avoid treating dialect features as simply “informal mistakes.” Varieties of English have their own systems and social meanings.

How can students make writing formal without sounding robotic?

Use clear sentence structure, precise vocabulary, appropriate politeness and evidence-based wording. Keep common words when they are the clearest choice. Avoid stuffing every sentence with nominalisations, passive voice or rare synonyms.

A sentence such as “Please submit the form by Friday” is formal, direct and natural.

Should formal writing always avoid first person?

No. Letters, reflections, speeches and many reports use I or we appropriately. Some academic genres reduce personal pronouns to foreground evidence or process, but this is a genre convention, not a universal rule.

Teach the genre, not a blanket ban.

Why is exact information more important than formal synonyms?

“Numerous people attended” is more formal than “lots of people came,” but “146 people attended” is more informative than either if the count is known. Formal writing often improves through specificity, not just vocabulary substitution.

Numbers, named categories and concrete actions reduce ambiguity and help readers evaluate the claim.

How should students handle certainty?

Preserve the evidence level. “Maybe” can become “may” or “perhaps,” but not “proves.” “I guess” can become “an estimate” only if the number is actually based on some method. “Looks different” should not become “significantly different” without evidence.

Register editing must never inflate certainty merely to sound academic.

What if the informal wording is more precise?

Keep it. “The tablet restarted twice” is more precise than “a technological irregularity occurred.” The first sentence is ordinary vocabulary but excellent report writing because it names the event exactly.

Precision outranks ceremonial formality.

Can formal and informal language appear in the same text?

Yes. A formal article can quote informal dialogue. A presentation can begin formally and include conversational examples. A narrative can contain formal narration and casual character speech. Controlled variation can improve voice and realism.

The problem is not mixing itself; it is accidental mismatch that confuses audience or purpose.

How can register help comprehension?

Register provides clues about relationship, setting, genre and character. A highly formal request may suggest social distance or authority. Slang may signal intimacy, age, group membership or setting. Students can use these clues when interpreting dialogue and tone.

Register should be interpreted alongside context rather than used to stereotype speakers.

How can register improve composition?

Writers can give characters distinct voices and shift narration appropriately. A principal addressing a hall, a child whispering to a friend and a narrator describing an event should not all sound identical.

Register choices can reveal social distance and emotion without explicit explanation.

What is the best evidence of mastery?

The learner can identify a register, explain the signals, rewrite the same message for different audiences, move in both directions, preserve meaning and certainty, avoid over-formality, and produce an appropriate version without seeing a model.

The strongest evidence is flexible independent choice, not memorising which side of a list is labeled formal.

Final 90-second register challenge

Take one message: “Tomorrow’s session is moved to Room 8.” Say it as a text to a friend, an email to a teacher, a public notice, a presentation announcement and a project-log entry. Keep the facts identical. Explain one register choice in each version.

If one version changes the date, room, certainty or obligation, the transformation has failed even if it sounds formal.

Return to the register routes, or continue to cross-context transfer.

Cross-context transfer: one message, many audiences and genres

Register becomes useful when students can carry the same meaning across contexts. The following laboratories keep the underlying information stable while changing audience, purpose or genre. The task is to notice what should change and what must not.

Transfer 1: room change

Fact: tomorrow’s meeting moves from Room 3 to Room 8. Friend text: “Hey, we’re in Room 8 tomorrow, not Room 3.” Teacher email: “Good afternoon. I understand that tomorrow’s meeting has been moved from Room 3 to Room 8.” Public notice: “Tomorrow’s meeting will be held in Room 8 instead of Room 3.” Project log: “Venue updated: Room 3 → Room 8 for tomorrow’s meeting.”

The information stays constant while greeting, pronouns, sentence completeness and formatting change.

Transfer 2: asking for a file

Friend: “Can you send me the file?” Teacher: “Could you please send me the revised file?” Formal organiser: “I would be grateful if you could provide the revised file when convenient.” Internal project log: “Revised file requested from organiser.”

The project-log form is not “more polite”; it has a different communicative purpose. It records action rather than performs the request.

Transfer 3: reporting an error

Conversation: “There’s something wrong with the date.” Formal email: “I noticed a possible error in the date shown on the notice.” Report: “The notice displays 14 May, while the source record lists 15 May.” The report version is strongest because it names the discrepancy rather than only labeling it an error.

Students should learn that formal reporting often replaces evaluation with evidence.

Transfer 4: apology

Friend: “Sorry I’m late.” Teacher: “I’m sorry for arriving late.” Formal organiser: “I apologise for the delay and appreciate your patience.” Project log: “Arrival delayed by ten minutes.” The log records the event without reproducing the apology.

The core fact can stay while the social function changes or disappears by genre.

Transfer 5: disagreement

Friend: “I don’t think that’ll work.” Discussion: “I’m not sure that approach will work.” Formal presentation: “I have concerns about whether this approach will achieve the intended result.” Report: “The proposed approach may not meet the stated requirement.”

Each version adjusts directness and evidence. Formal disagreement often benefits from specifying the reason rather than simply sounding polite.

Transfer 6: asking for clarification

Friend: “What do you mean?” Teacher: “Could you explain what this part means?” Formal email: “Could you please clarify the final requirement?” Academic discussion: “Could you clarify whether the condition applies to both groups?”

Greater formality often pairs with greater specificity. The best version names exactly what needs clarification.

Transfer 7: giving a recommendation

Friend: “You should try the second one.” Teacher feedback: “You may want to try the second method.” Formal report: “The second method is recommended because it produced fewer errors in the trial.”

The formal report adds an evidential basis. Register transformation can therefore require content selection, not merely word substitution.

Transfer 8: describing a result

Conversation: “It got way better.” Neutral: “It improved a lot.” Formal: “The result improved substantially.” Strong report: “The score increased from 42 to 78.” Exact data may replace evaluative intensifiers entirely.

Students should recognise the progression from impression to measurement.

Transfer 9: asking someone to wait

Friend: “Hang on a sec.” Polite-neutral: “Please wait a moment.” Formal service language: “Please wait while I verify the information.” The more formal version often explains the reason for the delay.

Informal speech may use idioms or shortened forms; formal contexts favour transparent wording.

Transfer 10: thanking someone

Friend: “Thanks!” Teacher: “Thank you for your help.” Formal correspondence: “Thank you for your assistance and for providing the revised document.” The degree of detail grows with the interaction, not because a longer thank-you is automatically more respectful.

Overly elaborate thanks can sound insincere. Match the wording to the contribution.

Transfer 11: public instructions

Casual: “Don’t go in there.” Public notice: “Please do not enter.” Safety instruction: “Do not enter this area.” In urgent contexts, removing politeness markers can make the command clearer and stronger.

This demonstrates why formality is not identical to softness. Direct language can be appropriate and professional.

Transfer 12: uncertainty

Conversation: “Maybe it’s wrong.” Neutral: “It may be wrong.” Formal: “The value may be incorrect.” Analytical: “The value may be incorrect because it conflicts with the source record.” The formal versions preserve uncertainty while increasing precision.

Students should resist replacing may with is or proves merely to sound decisive.

Transfer 13: opinion to evidence-based evaluation

Opinion: “I think the second design is better.” Formal opinion: “In my view, the second design is stronger.” Evidence-based evaluation: “The second design is easier to read from the back row because the font is larger.”

The last version is not simply more formal; it changes the basis from personal evaluation to observable reason. Use that shift only when the evidence exists.

Transfer 14: formal to child-friendly explanation

Formal: “The procedure requires participants to verify the final entry before submission.” Child-friendly: “Before you hand it in, check that the last answer is correct.” The second version is not worse. It is better suited to a younger audience.

Audience adaptation can require simplifying vocabulary while keeping the rule intact.

Transfer 15: formal to oral presentation

Written report: “The second trial produced a lower error rate than the first.” Oral presentation: “In the second trial, we saw fewer errors than in the first.” Spoken language can be slightly less compressed and more audience-friendly while remaining formal enough for a presentation.

Good speakers do not simply read report prose aloud.

Transfer 16: dialogue inside formal narrative

Narration: “Alicia informed the group that the venue had changed.” Dialogue: “Hey, we’re in Room 8 now.” The narrator and character can use different registers in the same composition. The contrast can make the story feel natural.

Students should preserve character voice rather than “correcting” every spoken line into report language.

Transfer 17: one fact, three levels of formality

Fact: the printer has no paper. Informal: “The printer’s out of paper.” Neutral: “The printer has run out of paper.” Formal/operational: “Printing cannot continue because the paper supply has been exhausted.”

The final version may be appropriate in a technical log but excessive in ordinary school communication. Register choice is local.

Transfer 18: two-way translation check

Choose any five pairs from the numbered list. Write a formal sentence, translate it into natural informal English, then translate back without looking at the original. Compare the first and third versions. If the message changes, identify where the drift occurred.

This is one of the strongest tests of semantic preservation.

Transfer 19: register ladder

Build a three-step ladder for one message: casual, neutral, formal. Example: “Send me the file” → “Can you send me the file?” → “Could you please send me the revised file?” Then explain which changes affect politeness, which affect vocabulary and which affect social distance.

Register is easier to understand as a continuum when learners see intermediate forms.

Transfer 20: final audience-switch challenge

Write 150 words explaining a delayed school event to a close friend, a teacher and a public audience. Keep date, reason and new timing identical. Then highlight vocabulary changes, contractions, greetings, request structures and omitted details.

If the factual core is stable and each version sounds natural for its audience, the register system is working.

Return to the register routes, or continue to the final production manual.

Final production manual: 15 drills for independent register control

This final manual removes most of the visible models. The learner should make register decisions from audience, purpose and meaning rather than by copying formal alternatives from the numbered list. The drills move from recognition to independent production and editing.

Drill 1: audience before wording

Choose one fact: “The meeting starts at four.” Write it for a close friend, a teacher, a public notice and a project log. Do not begin by choosing vocabulary. Begin by naming the audience and purpose.

After writing, underline the features that changed: greeting, contraction, directness, verb choice, sentence completeness and level of detail. Circle the factual information that stayed the same.

Drill 2: preserve meaning while formalising

Rewrite: “Maybe the new sign helped a bit.” A careful formal version might be: “The new sign may have produced a small improvement.” If actual data exist, use them. Do not write “The new sign was highly effective” unless the evidence supports that claim.

Repeat with five sentences containing maybe, I think, a bit, good and bad. Formalise without changing certainty or evaluation strength.

Drill 3: formalise by adding precision, not length

Start with “A lot of stuff went wrong.” Ask what happened. Replace vague nouns and quantities with observable details. A strong result might be “Two labels detached and one tablet restarted.” No rare vocabulary is needed.

Do this with “The thing was bad,” “Loads of people came,” “It got much better,” and “Something weird happened.” Precision should drive the revision.

Drill 4: de-formalise unnatural dialogue

Rewrite dialogue that sounds like a report. “I am unable to comprehend your decision” might become “I don’t understand why you did that.” “I would appreciate your immediate departure” might become “Please go now” depending on tone and relationship.

Keep character age, emotion and social distance in mind. Natural dialogue is not careless writing.

Drill 5: identify false friends in register pairs

Review pairs where formality also changes meaning: cheap/inexpensive, proof/evidence, guess/estimate, good/effective, small/minor. For each, write one sentence where substitution is safe and one where substitution changes the claim.

This drill prevents students from treating the 100 pairs as a mechanical thesaurus.

Drill 6: contraction control

Write a friendly email with contractions, then create a more formal version using full forms. Next, write a professional email that still uses one or two natural contractions. Compare tone. The learner should see that contractions contribute to register without completely defining it.

Finally, write an official notice where contractions would be less expected. Genre should guide the final choice.

Drill 7: phrasal-verb register switch

Choose ten pairs from 61–80. Use the phrasal verb in a conversational sentence and the single-word alternative in a formal report sentence. Then test whether the alternative covers the same sense.

Example: “They put the meeting off” → “They postponed the meeting.” But “The smell put me off the food” cannot become “The smell postponed me from the food.” One phrasal verb can have several meanings; register pairs are sense-specific.

Drill 8: formal connector repair

Replace so, but and also with more formal connectors only where grammar and logic allow. “The source was incomplete, so we checked another record” can become “The source was incomplete; therefore, we checked another record.” “The first version was clearer, but it was longer” can become “The first version was clearer; however, it was longer.”

Then create one example where the simple connector is better. Register choice should remain flexible.

Drill 9: politeness ladder

Create a request ladder: “Send me the file.” → “Can you send me the file?” → “Could you please send me the file?” → “I would be grateful if you could provide the file.” Match each to a plausible situation.

Then decide where the ladder becomes over-formal for a close friend. Formality is gradient and relationship-sensitive.

Drill 10: public instruction versus polite request

Compare “Could you please avoid entering?” with “Please do not enter” and “Do not enter this area.” Rank them for a casual request, ordinary public notice and urgent safety instruction. More direct language can be more appropriate in higher-stakes contexts.

This drill prevents students from equating formal register with maximum softness.

Drill 11: report evidence ladder

Start with opinion: “I think the new layout is better.” Move to formal opinion: “In my view, the new layout is more effective.” Move to evidence: “In the trial, readers found the target information faster with the new layout.” The last sentence changes the basis of the claim.

Students should identify where register changes and where evidential content changes. They are related but not identical editing operations.

Drill 12: genre switch without fact drift

Use one event: “The session was postponed because the room flooded.” Write a friend message, teacher email, public notice, report sentence and project-log entry. Every version must preserve postponed—not cancelled—and the same cause.

Compare how much social framing each genre needs. The log may be the shortest despite being formal.

Drill 13: over-formality detector

Highlight words in a formal draft that could be replaced by shorter common words without loss of precision: utilise→use, commence→begin, aforementioned→previous/this depending context, facilitate→help/enable when appropriate. Do not simplify specialised terms that are genuinely precise.

The goal is plain formal English: professional, clear and efficient.

Drill 14: register repair from authentic writing

Take 150–200 words from the learner’s own recent writing. Mark sentences that sound too casual, too formal, vague or mixed. For each, label the cause: audience, genre, precision, politeness, certainty or voice.

Revise only the sentences that genuinely need change. This prevents register lessons from becoming wholesale rewriting of the student’s voice.

Drill 15: forty-eight-hour blind production

After two days, give five scenarios with no word bank: apologise to a friend; request a file from a teacher; report a numerical increase; write a public instruction; tell a classmate that an event was postponed. Produce each message independently.

Then explain one register choice in each. Mark responses independent, prompted or not yet secure. Delayed production is stronger evidence than immediate pair matching.

A final self-edit checklist

Before submitting, ask: Who is my audience? What is my purpose? What genre am I writing? Does my vocabulary fit? Are my sentences too casual or unnecessarily stiff? Have I preserved certainty? Can I replace vague words with specific information? Does the message sound like a real person in this situation?

If the answer to the last question is no, formal correctness may still need stylistic repair.

Final production standard

A learner has strong register control when the same underlying message can be expressed naturally to different audiences without fact drift, certainty inflation or vocabulary showmanship. The student can formalise, simplify, explain and self-correct.

Return to the register routes.

Mixed register practicum: 15 fresh scenarios with no word bank

These scenarios mix audience, genre, politeness, precision and certainty. Write the message first, then compare it with the analysis. More than one answer may be acceptable if it fits the context and preserves the intended meaning.

Scenario: asking a classmate for notes

A natural message might be: “Hey, can you send me yesterday’s notes? I missed the last part. Thanks!” A version such as “I would be grateful if you could provide the aforementioned notes” is over-formal for most close classmates.

The key choices are casual greeting, contraction, direct reason and friendly thanks. No specialised vocabulary is needed.

Scenario: requesting the same notes from an unfamiliar teacher

“Good afternoon, Ms Lim. Could you please send me the notes from yesterday’s lesson? I missed the final section. Thank you.” The message is more formal but still natural and concise.

Notice that the reason remains the same. Register changes social framing rather than inventing justification.

Scenario: recording the request in a project log

“Requested yesterday’s lesson notes from Ms Lim after missing the final section.” The log does not need greeting, please or thank you because it is not performing the social request.

This distinction prevents students from assuming every formal text must contain polite formulas.

Scenario: reporting an uncertain date

Weak casual: “The date looks wrong.” Better analytical: “The date may be incorrect because the notice lists 14 May while the source record lists 15 May.” The formal version preserves uncertainty and adds evidence.

Do not write “The date is definitely incorrect” unless a trustworthy source resolves the conflict.

Scenario: declining an invitation

Friend: “Sorry, I can’t make it.” Formal organiser: “Thank you for the invitation. Unfortunately, I am unable to attend.” Both are polite; the second adds conventional social framing.

The decline remains a decline. Formality should not create false reasons or over-apology.

Scenario: correcting a classmate privately

“I think the date might be 15 May, not 14 May—can we check the source?” This is polite-neutral and collaborative. A highly formal correction such as “Your assertion is demonstrably erroneous” would be socially inappropriate and unnecessarily confrontational.

Register includes interpersonal sensitivity, not just vocabulary level.

Scenario: correcting a public report

“The report currently lists 14 May. The verified source record gives 15 May; the date should therefore be corrected.” The wording is impersonal, evidence-based and direct.

Public correction benefits from clear evidence rather than conversational hedging.

Scenario: telling a friend an event was cancelled

“They called the event off.” A formal notice might say, “The event has been cancelled.” The meaning is the same. If the event is merely delayed, neither version should be used; choose put off/postponed instead.

Register control depends on semantic control first.

Scenario: describing a successful method

Conversation: “That method worked really well.” Report: “The method reduced the error rate from 18% to 6%.” The report version avoids a vague evaluation by using data.

If exact data are unavailable, “The method appeared effective in this trial” may be more honest than a strong unqualified claim.

Scenario: giving urgent safety instructions

“Do not touch the exposed wire.” This direct command can be more appropriate than “Would you mind refraining from touching the wire?” Politeness should never obscure urgency.

The best register serves the communicative risk and purpose.

Scenario: speaking during a school presentation

“Good morning. Today we’ll explain how we tested the two designs.” This is clear and moderately formal. “Esteemed audience, we shall presently elucidate…” is theatrical and over-formal for the setting.

Students need a presentation register that sounds prepared without sounding artificial.

Scenario: writing a reflection after failure

“I was disappointed because our first design failed, but I realised the instructions were unclear.” The sentence is personal and still school-appropriate. Replacing it with detached passive language would weaken the reflective genre.

Formal school writing can still use personal voice when the task requires reflection.

Scenario: summarising a conversation

Conversation: “The printer’s acting weird again.” Summary: “The printer malfunctioned again.” Report: “The printer restarted twice and failed to complete the print job.” Each level moves from impression toward observable event.

Students should choose the most informative version appropriate to the evidence and genre.

Scenario: softening a request without becoming vague

Direct: “Send the corrected file now.” Polite: “Could you please send the corrected file now?” Softer: “Could you please send the corrected file when possible?” The last version changes urgency. Do not soften away an actual deadline.

Politeness choices can alter timing and obligation, so meaning preservation still matters.

Scenario: explaining a technical term to a younger child

Formal textbook: “Evaporation is the process by which a liquid changes into a gas.” Child-friendly: “Evaporation happens when liquid water changes into water vapour.” The second may use simpler syntax while keeping the scientific concept.

Audience adaptation sometimes means simplifying register while retaining technical accuracy.

Scenario: final mixed repair

Draft email: “Hey Principal, I wanna ask if you can kinda tell me whether the hall is free because we need it for this thing.” Formal-natural revision: “Good afternoon, Principal Tan. Could you please let me know whether the hall is available for our rehearsal?”

The revision changes greeting, contractions, vague wording and request framing while preserving the underlying question. It also replaces “this thing” with the specific purpose, rehearsal.

Practicum review

Choose five scenarios and rewrite each for a different audience. Then label every change as vocabulary, politeness, grammar, precision, certainty, genre or tone. If a fact changes, undo that change unless the new scenario explicitly requires different information.

This final mixed practice checks whether register is becoming a controlled system rather than a memorised formal-word bank.

Return to the register routes, or continue to the final synthesis.

Register networks: organise vocabulary by communicative job

Register becomes easier to control when vocabulary is organised by communicative function rather than alphabetically. A learner can then retrieve a set of options for requesting, reporting, evaluating, disagreeing or recording evidence and choose the one that fits the situation.

Request network

Direct: “Send me the file.” Neutral request: “Can you send me the file?” Polite: “Could you please send me the file?” More formal: “I would be grateful if you could provide the revised file.” The wording moves along a politeness/formality continuum while the core request remains.

Students should match the ladder to relationship and urgency. In a time-critical situation, an elaborate request can be less effective than a clear direct one.

Apology network

Casual: sorry. Neutral: I’m sorry for… Formal: I apologise for… Reflective/formal: I apologise for the delay and accept responsibility for… The network shows that greater formality can add explicit responsibility, but only when the situation warrants it.

A student should not inflate a minor inconvenience into a dramatic apology merely because the vocabulary is available.

Information network

tell → let someone know → inform → notify. These forms overlap but differ in register and typical context. “Tell me when you arrive” is natural. “Please let me know when you arrive” is polite-neutral. “Please inform the office of any change” is formal. “Registered users will be notified by email” is institutional.

The network helps students choose a verb that fits both social distance and genre.

Investigation network

check → look into → examine → investigate → verify. These are not a simple formality scale because each adds meaning. Check is broad. Look into suggests inquiry. Examine suggests close inspection. Investigate suggests systematic inquiry. Verify means confirm against evidence.

This network demonstrates the central rule of the article: formal alternatives often carry semantic boundaries. Choose by task, not by word length.

Change network

get better → improve; go up → increase; go down → decrease; get worse → deteriorate. These formal alternatives are especially useful for measurable change. But exact data may be stronger still: “increased from 40 to 65” communicates more than “improved substantially.”

Students should place numerical evidence above vocabulary ornament when the data are known.

Decision network

think about → consider; turn down → reject; put off → postpone; call off → cancel; choose → select/adopt depending context. Each formal verb identifies a different decision action. Postpone is not cancel; reject is not merely delay; adopt means accept/take up rather than choose casually.

Register study therefore reinforces precise decision vocabulary.

Evidence network

show → indicate → demonstrate; check → verify; guess → estimate; proof → evidence. The network becomes progressively more dangerous if treated as a simple formal ladder. Demonstrate can be stronger than show; verify implies confirmation; estimate needs a basis; proof may imply conclusiveness.

Students should ask what the evidence justifies before choosing the formal word.

Quantity network

lots of → many/much → numerous/considerable → exact number or amount. Formal writing often becomes stronger by moving from vague quantity toward measurable detail. “Numerous responses” is useful when the exact count is unavailable; “146 responses” is better when known.

Countability still matters: many responses, much time, considerable evidence.

Evaluation network

good → useful/effective/accurate/appropriate depending dimension. bad → ineffective/inaccurate/inappropriate/poorly organised depending dimension. Formal writing often replaces broad evaluation with a more specific criterion.

This network is especially important for composition and report writing because it teaches students to ask “good in what way?”

Uncertainty network

maybe → perhaps/may; I think → in my view; I’m not sure → it is uncertain whether; I guess → I estimate only when there is a basis. Formality can express uncertainty more precisely rather than remove it.

Students should learn calibrated wording: possible, likely, tentative, uncertain and confirmed all represent different evidence states.

Contrast network

but → however; even though → although; different from → in contrast to; while → whereas in selected formal comparisons. These changes affect syntax and punctuation as well as vocabulary.

Connector choice must follow the logical relation. Register editing should never create false contrast simply because however sounds formal.

Addition network

also → additionally; plus → in addition; another thing → another factor/point depending context. Formal writing benefits when added information is categorised precisely rather than introduced with vague conversational markers.

Yet “also” remains standard and useful in formal prose. The network offers options, not bans.

Register-network task

Choose one communicative job and build a five-step ladder from casual to formal. For each step, write a realistic context. Then identify where meaning changes, not merely register. The point at which meaning changes is a boundary students must learn.

Return to the register routes, or continue to the final capstone.

Capstone: one event rewritten across five registers

Use one event throughout: a school exhibition planned for Friday has been postponed to Monday because the hall is unavailable. The facts are fixed: event = school exhibition; original day = Friday; new day = Monday; reason = hall unavailable; status = postponed, not cancelled. Every version below must preserve those facts.

Version 1: close-friend message

“Hey, the exhibition’s been moved from Friday to Monday because the hall isn’t free. Just letting you know.” This version uses a casual greeting, contraction, phrasal-style wording and a friendly closing. It sounds natural between peers.

Notice that “moved” is slightly broader than postponed. It works here because the new date is stated. If the date were unknown, postponed would communicate the status more precisely.

Version 2: message to a teacher

“Good afternoon, Ms Lim. The school exhibition has been postponed from Friday to Monday because the hall is unavailable. I wanted to confirm that I have the updated date correctly. Thank you.”

The message is polite, complete and moderately formal. It uses postponed and unavailable but avoids over-elaborate wording. The added confirmation sentence reflects the teacher-directed purpose; it would not belong in every version.

Version 3: public notice

“NOTICE: The school exhibition scheduled for Friday has been postponed to Monday because the hall is unavailable. Please use the updated date when making arrangements.”

The notice removes personal greeting and first-person voice. It foregrounds the status change and action readers should take. The register is formal but concise.

Version 4: project report

“The school exhibition was postponed from Friday to Monday after the hall became unavailable. The schedule was updated and the revised date was communicated to participants.”

The report records event and response. It uses passive structures because the actor communicating the update is less important than the operational record. If responsibility matters, the actor should be named instead.

Version 5: project log

“Exhibition postponed: Friday → Monday. Reason: hall unavailable. Revised date communicated to participants.”

This is formal in function but highly compressed. It shows why formal does not mean long. Logs often value efficient record-keeping over full sentences.

What changed across the five versions?

Greeting changed or disappeared. Contractions appeared in the friend message and disappeared in formal versions. Vocabulary shifted from moved/isn’t free to postponed/unavailable. Personal pronouns decreased in public and record genres. Sentence completeness varied. The project log used fragments because the genre permits them.

What did not change: the event, original date, new date, reason and postponed status. These facts form the semantic core that every register transformation must protect.

Capstone variation: cancellation instead of postponement

Now change one fact: the exhibition is cancelled rather than moved to Monday. Rewrite all five versions. The vocabulary must change from moved/postponed to called off/cancelled as appropriate. Do not leave “Monday” in the message unless a replacement event has actually been scheduled.

This variation tests whether register work is built on accurate event semantics. A formal sentence using the wrong event status is still wrong.

Capstone variation: uncertain information

Now suppose Monday is only proposed, not confirmed. Friend: “Looks like it might move to Monday, but it’s not confirmed yet.” Formal: “The exhibition may be moved to Monday; the revised date has not yet been confirmed.” Public notice should probably wait for confirmation unless the uncertainty itself needs communicating.

Register must preserve uncertainty just as carefully as facts.

Capstone variation: urgent safety message

Suppose the hall becomes unsafe during the event. Friendly politeness ladders are no longer the main concern. “Leave the hall immediately and move to the assembly area.” The message is direct, formal and urgent. “Would you mind leaving when convenient?” would fail the purpose.

This variation proves that audience, purpose and risk can outweigh ordinary politeness preferences.

Capstone variation: explaining to younger students

“The exhibition will happen on Monday instead of Friday because we cannot use the hall on Friday.” The vocabulary is simpler than the public notice, but the information is complete. Audience adaptation can move toward simpler language while remaining respectful and accurate.

Students should recognise that simplification is a form of register control, not a reduction in intelligence.

Capstone variation: school newsletter

“Please note that the school exhibition has been rescheduled from Friday to Monday because the hall is unavailable. We apologise for any inconvenience and look forward to welcoming families on Monday.”

The newsletter combines public information with a warmer community tone. Formality and warmth coexist.

Capstone editing challenge

Write your own five-register set for one of these facts: a deadline changes; a room closes; a form is missing; a result is uncertain; a rehearsal is cancelled. Keep the factual core in a box above the page. After rewriting, compare every version with the box.

Mark any drift in date, obligation, cause, certainty, quantity or event status. Those are semantic errors, not style differences.

Capstone self-assessment

Give yourself one point for appropriate audience, one for appropriate genre, one for natural vocabulary, one for preserved meaning, one for preserved certainty and one for precise information. A version that sounds formal but loses meaning should not score highly.

The scoring system is not a permanent label. It is a diagnostic for one piece of writing.

Final synthesis principle

Register is successful when readers receive the right message in language that feels appropriate to the situation. Formality is one dimension among audience, purpose, precision, certainty, politeness and voice. The writer’s task is to coordinate them.

A learner who can move one message across friend text, teacher email, public notice, report and log without changing the facts has acquired a powerful language-control skill that extends far beyond a Top 100 vocabulary list.

Last independent register lab: repair twelve messages without a formal-word list

This final lab removes the pair bank. For each message, decide the target audience and purpose, preserve the factual core, and make only the changes that improve fit. The sample repairs are possibilities rather than single required answers.

Message 1: too casual for a formal request

Draft: “Hey, can you chuck me the updated form when you’re free?” Target: unfamiliar organiser. Possible repair: “Good afternoon. Could you please send me the updated form when convenient? Thank you.”

The repair changes greeting, slang-like chuck, request framing and closing. It does not change which form is needed.

Message 2: too formal for a close friend

Draft: “I regret to inform you that I shall be unable to accompany you to lunch.” Target: close friend. Possible repair: “Sorry, I can’t make lunch today.”

The shorter message remains polite and factual. Social closeness supports contractions and ordinary vocabulary.

Message 3: formal but vague report

Draft: “Several adverse operational incidents occurred.” Recorded facts: one label detached and the tablet restarted twice. Repair: “One label detached and the tablet restarted twice during the trial.”

The repair becomes less abstract and more useful. Formal reports benefit from observable events.

Message 4: certainty accidentally increased

Draft informal: “Maybe the new instructions helped.” Bad formalisation: “The revised instructions proved effective.” Repair: “The revised instructions may have improved performance in this trial.”

The modal may preserves uncertainty. Scope language “in this trial” prevents overgeneralisation.

Message 5: polite request that loses urgency

Fact: corrected file is required by noon. Weak softening: “Could you send it whenever convenient?” Better: “Could you please send the corrected file by noon?”

Politeness should not remove a genuine deadline.

Message 6: public notice that sounds conversational

Draft: “Hey everyone, don’t leave your stuff here.” Repair: “Please do not leave personal belongings in this area.”

Personal belongings is more specific than stuff; the greeting is unnecessary for a posted notice.

Message 7: child-facing instruction that is over-formal

Draft: “Participants are required to deposit completed documentation within the designated receptacle.” Target: younger primary students. Repair: “Put your completed form in this box.”

Simplification improves audience fit without reducing the requirement.

Message 8: dialogue flattened into report language

Draft character line: “I am extremely dissatisfied with your failure to notify me.” If the speaker is an upset classmate, a more natural line could be: “I’m really upset you didn’t tell me.”

The emotion remains; the voice becomes believable. Composition register should support characterisation.

Message 9: informal phrase with no simple formal substitute

Draft: “The idea didn’t really work out.” Before replacing work out, identify the sense. If the idea failed to achieve its goal: “The approach was unsuccessful.” If the plan could not be resolved: “The issue remained unresolved.” If a calculation failed: “The calculation could not be completed.”

Sense selection must precede register selection.

Message 10: a report that hides responsibility

Draft: “The source check was not completed.” If the writer was responsible and the task requires accountability, better: “I did not complete the source check before submission.”

Passive voice may be formal but can remove relevant agency. Register should not become a shield.

Message 11: casual but accurate becomes formal and inaccurate

Original: “About twenty people came.” Bad rewrite: “Numerous participants attended.” If about twenty is an estimate based on observation, better: “Approximately twenty people attended.”

The formal word numerous loses useful quantitative information. Approximate numerical language is both formal and precise.

Message 12: natural formal English versus jargon

Draft: “The team utilised a methodology to facilitate enhanced navigational outcomes.” Clear formal version: “The team used a revised method to improve navigation.”

The shorter sentence retains the formal report register while removing unnecessary nominalisation and jargon.

Independent extension

Create six messages from your own school context. Make two too casual, two over-formal and two semantically misleading through an inappropriate “formal” synonym. Exchange with a partner. The partner must identify the problem type before rewriting.

Then rewrite each message in two acceptable registers rather than only one. This prevents the exercise from implying that every situation has a single correct sentence.

Final register principle

Strong register control is invisible when it works. The reader does not stop to admire how formal the vocabulary sounds; the language simply feels appropriate, clear and trustworthy. The student has chosen words that fit the relationship between writer, reader, purpose and evidence.

That is the endpoint of this Top 100 collection: not replacing informal English with formal English, but gaining the flexibility to use both well.

Final synthesis: meaning first, register second, precision throughout

Take the simple message “The result looks wrong.” Before formalising it, ask what the writer actually knows. If the value conflicts with a source, write: “The result may be incorrect because it conflicts with the source record.” If the value is merely unexpected, write: “The result is unusual and requires further checking.” If the value has been verified as wrong, write: “The recorded result is incorrect.” Three formal versions emerge from three evidence states.

Now take “Can you send me the file?” The message may already be perfect for a colleague or familiar teacher. Formalising it to “I would be most grateful if you could provide the aforementioned document” adds distance without useful precision. Register control includes knowing when no change is needed.

Take “A lot of kids liked it.” In a report, the first question should be “How many?” If 18 of 20 students gave a positive response, say so. “Eighteen of the twenty students responded positively” is stronger than “numerous children expressed approval.” Exact evidence outperforms ornamental vocabulary.

Take “The method was bad.” Ask which dimension failed. Was it inaccurate, inefficient, confusing, impractical, unsafe, expensive or ineffective? Formal writing often improves by naming the evaluation criterion. The same principle applies to “good”: effective, accurate, clear, efficient and appropriate are different claims.

Take “They put it off.” Context must identify what it is and which sense of put off is active. If a meeting was delayed, postpone is a formal alternative. If a smell discouraged someone from eating, postpone is wrong. Meaning selection must happen before register substitution.

Take “I’m sorry.” In a friend message, that may be complete and sincere. In a formal apology where responsibility matters, more information may be needed: “I apologise for missing the deadline and have submitted the corrected file.” The difference is not that longer is better. The formal situation requires the event and response to be explicit.

Take “Do not enter.” In a safety context, this short command may be more appropriate than a softer polite request. Formal language can be direct. Politeness is one dimension of register, but clarity, urgency and obligation can take priority.

Take “I think the second design is better.” If the task asks for personal preference, the sentence may be suitable. If the task asks for evaluation, supply the criterion: “The second design is easier to read from the back row because the font is larger.” Register work becomes reasoning work when the writer replaces unsupported evaluation with evidence.

Finally, take one fact from your own writing and express it in five contexts: a text message, email, presentation, report and notice. Underline what changes and circle what remains. If the facts, certainty and obligation survive while the language adapts naturally, register has become a usable skill rather than a list of formal synonyms.

The central rule can therefore be stated in one line: meaning first, register second, precision throughout. A student who follows that order can sound casual without being careless, formal without being stiff, and academic without overstating the evidence.

Last independent transfer note

Close the article and choose one ordinary message from your real school day: ask for a missing worksheet, explain a delayed task, report a mistake, thank someone, disagree with an idea or give an instruction. Write the message first exactly as you would naturally say it to a close friend.

Next, rewrite it for a teacher or unfamiliar adult. Preserve every fact and every degree of certainty. Change only what the audience requires: greeting, politeness, contractions, word choice, sentence completeness and level of detail. Then rewrite the same information as a report or log entry. Remove the social framing that the record no longer needs.

Finally, translate the report back into natural spoken English. Compare the first and last versions. If the facts have drifted, locate the exact word that caused the change. Did guess become estimate without evidence? Did maybe become a definite statement? Did put off become cancel instead of postpone? Repair the semantic error before judging style.

This four-direction exercise—friend → teacher → report → friend—tests whether the learner controls register independently of a memorised pair list. Strong performance means the same message survives while the language adapts naturally to each communicative setting.

Keep one final principle in view: register is successful when the reader notices the message, not the vocabulary display. Appropriate language feels fitted to the situation. It can be simple or advanced, warm or distant, direct or cautious, but it should remain clear, accurate and socially intelligible.

For the final independent check, choose one sentence from your own writing and rewrite it for two different audiences without using the pair list. Explain which words changed, which facts stayed fixed, and whether the level of certainty remained the same. Then ask another reader which version sounds more appropriate in each situation and why. If the reader can identify the intended register from the language alone, the vocabulary choices are doing their job.

Reference notes and next learning routes

IXL’s DoDEA fifth-grade ELA standards mapping includes Grade 5 language work on comparing varieties of English, including registers, and choosing language with awareness of style and context.

One More Sheet — 5th Grade Formal or Informal English reflects current Grade 5 search and practice language around switching between formal and informal English while preserving meaning. Its teaching notes emphasise matching register to situation rather than treating informal English as inherently wrong.

The Louisiana Department of Education Grade 5 teacher guide describes register as differences in language formality and discusses formal and informal register in Grade 5 grammar instruction.

Continue through the eduKate Vocabulary Learning System and its advanced Primary 5 companions: vocabulary analogies, multiple-meaning words, commonly confused words, prepositional phrases, phrasal verbs and academic collocations.

Final principle: preserve the message, fit the audience, fit the purpose, and choose the clearest natural wording at the required level of formality.

Return to the routes · 1–20 · 21–40 · 41–60 · 61–80 · 81–100 · Exercises · Casebooks.