JLPT N4 て-Form: Conjugation and Usage Examples

1. Overview: the decision behind the form

This te-form engine addresses how one high-frequency verb form connects actions to requests, aspect, permission, preparation and many auxiliary patterns. The challenge is rarely vocabulary alone. A familiar place, verb or connective can still lead to a wrong interpretation when its grammatical relationship is misread. Start each te-form engine decision with the final predicate, then connect the marked phrase to the scene the speaker is presenting. That sequence keeps an English gloss from deciding too early.

The compact working rule for this te-form engine is: Group 2 verbs generally replace る with て; する becomes して and 来る becomes 来て; Group 1 endings follow the って, んで, いて, いで or して sound patterns, with 行く becoming 行って. Treat that statement as a map, not a password. The map becomes useful only when a complete example shows who acts, what changes, when the event is located and which information the speaker foregrounds. Every later te-form engine clinic changes one of those variables while preserving the others.

The central contrast for this te-form engine is: The て-form itself does not supply one fixed English meaning or a complete tense. The expression after it and the surrounding clause determine its job. Say this te-form engine distinction aloud before studying exceptions. If two constructions can produce similar English in te-form engine work, preserve the Japanese viewpoint in a short structural paraphrase. A structural paraphrase for te-form engine, such as ‘endpoint reached,’ ‘representative list’ or ‘reported judgement,’ is often more useful than a polished translation during the first pass.

The JLPT label attached to this te-form engine organizes study; it is not an official claim that one published grammar list defines this level. The official JLPT FAQ states that the revised test does not publish fixed vocabulary, kanji and grammar specifications, a limit that also applies when organizing te-form engine study. All te-form engine dialogues, contrasts and exercises in this chapter are original learning material. They teach transferable te-form engine analysis rather than reproduce examination questions.

2. Formation: build the inside before the ending

Write the te-form engine formula on one line: Group 2 verbs generally replace る with て; する becomes して and 来る becomes 来て; Group 1 endings follow the って, んで, いて, いで or して sound patterns, with 行く becoming 行って. On the next line, write a complete sentence from memory. Mark the attachment boundary with brackets and underline the final predicate. This simple layout separates the content clause from the expression that frames it. It also reveals where tense, polarity or politeness belongs when the sentence is revised.

Use 窓を開けて、空気を入れました。 as the first te-form engine model. It means “I opened the window and let air in” and the diagnostic point is that the first て-form connects a natural action sequence. Change only the time phrase, then only the participant. If neither change alters the grammatical relationship, retain the structure. If the relationship changes, name the new clue before selecting a replacement.

Use ここに名前を書いてください。 as the contrasting te-form engine model. It means “Please write your name here” and てください turns the form into a direct polite request. Place the two models side by side. Circle the smallest difference that changes interpretation, but keep the full predicates visible. Memorizing only the highlighted fragment can hide restrictions supplied by verb type, time sequence or discourse role.

Finally, create four te-form engine cells: affirmative nonpast, negative nonpast, affirmative past and negative past. Not every target expression naturally fills every cell, so unnatural results are informative. Note whether negation denies the embedded event or the final judgement. Note whether past marking locates the event, the decision, the report or the state reached.

3. Four examples that establish the range

Example 1 is 窓を開けて、空気を入れました。 It communicates “I opened the window and let air in.” In this te-form engine, the first て-form connects a natural action sequence. For example 1, read the Japanese once for the overall scene and once for its decisive clue for structural boundary. Then cover the English and state the example 1 relationship in your own words. A correct te-form engine explanation for example 1 should predict why the nearest alternative would shift the message.

Example 2 is ここに名前を書いてください。 It communicates “Please write your name here.” In this te-form engine, てください turns the form into a direct polite request. For example 2, read the Japanese once for the overall scene and once for its decisive clue for speaker viewpoint. Then cover the English and state the example 2 relationship in your own words. A correct te-form engine explanation for example 2 should predict why the nearest alternative would shift the message.

Example 3 is 妹は今、電話で話しています。 It communicates “My younger sister is speaking on the phone now.” In this te-form engine, ている presents an activity in progress. For example 3, read the Japanese once for the overall scene and once for its decisive clue for time and aspect. Then cover the English and state the example 3 relationship in your own words. A correct te-form engine explanation for example 3 should predict why the nearest alternative would shift the message.

Example 4 is この席に座ってもいいですか。 It communicates “May I sit in this seat?” In this te-form engine, てもいい asks permission. For example 4, read the Japanese once for the overall scene and once for its decisive clue for negative scope. Then cover the English and state the example 4 relationship in your own words. A correct te-form engine explanation for example 4 should predict why the nearest alternative would shift the message.

4. Four frequent errors and how to repair them

Error 1 is using a Group 2 shortcut on a Group 1 verb such as 帰る or 走る. Compare that risk with 窓を開けて、空気を入れました。 The intended meaning is “I opened the window and let air in” and the first て-form connects a natural action sequence. For error 1, repair only the faulty te-form engine choice; do not rewrite unrelated vocabulary. After correcting error 1, invent a different scene where the rejected construction would be natural. That second error-1 scene turns a prohibition into a usable boundary.

Error 2 is forming 行いて by analogy with 書いて instead of remembering 行って. Compare that risk with ここに名前を書いてください。 The intended meaning is “Please write your name here” and てください turns the form into a direct polite request. For error 2, repair only the faulty te-form engine choice; do not rewrite unrelated vocabulary. After correcting error 2, invent a different scene where the rejected construction would be natural. That second error-2 scene turns a prohibition into a usable boundary.

Error 3 is translating every て as and, even when an auxiliary such as いる changes the construction. Compare that risk with 妹は今、電話で話しています。 The intended meaning is “My younger sister is speaking on the phone now” and ている presents an activity in progress. For error 3, repair only the faulty te-form engine choice; do not rewrite unrelated vocabulary. After correcting error 3, invent a different scene where the rejected construction would be natural. That second error-3 scene turns a prohibition into a usable boundary.

Error 4 is placing politeness on the linked verb instead of allowing the final predicate to carry sentence style. Compare that risk with この席に座ってもいいですか。 The intended meaning is “May I sit in this seat” and てもいい asks permission. For error 4, repair only the faulty te-form engine choice; do not rewrite unrelated vocabulary. After correcting error 4, invent a different scene where the rejected construction would be natural. That second error-4 scene turns a prohibition into a usable boundary.

5. Case clinic: structural boundary

The working te-form engine sentence for structural boundary is 窓を開けて、空気を入れました。 Its practical translation is “I opened the window and let air in.” The decisive structural boundary observation is that the first て-form connects a natural action sequence. For this structural boundary clinic, keep three layers separate: printed form, contextual meaning and analytical reason. The te-form engine structural boundary analysis is secure only when the reason survives after familiar vocabulary has been replaced.

For the te-form engine structural boundary check, read from the predicate toward the beginning. During this structural boundary pass, bracket the material that belongs together and label any omitted participant as an inference. Apply the structural boundary parse again to “I opened the window and let air in” without assuming English word order matches Japanese scope. Because the first て-form connects a natural action sequence, the marked structural boundary relationship must remain visible in the final explanation.

A realistic failure in this te-form engine structural boundary case would be using a Group 2 shortcut on a Group 1 verb such as 帰る or 走る. That structural boundary shortcut would misrepresent “I opened the window and let air in” because the first て-form connects a natural action sequence. Instead of memorizing a red correction for structural boundary, write one conditional rule: the rejected option would work if the scene supplied a different predicate, viewpoint, time relationship or level of authority. Name the exact condition changed in the structural boundary contrast.

Now rebuild the te-form engine structural boundary sentence with a new person, place or time. Preserve the fact that the first て-form connects a natural action sequence, but use vocabulary from your own routine for this structural boundary transfer. Make a second structural boundary version that deliberately changes that fact and therefore needs a neighboring construction. Read both structural boundary versions aloud, translate both, and finish by explaining their difference without naming English keywords alone.

6. Case clinic: speaker viewpoint

The working te-form engine sentence for speaker viewpoint is ここに名前を書いてください。 Its practical translation is “Please write your name here.” The decisive speaker viewpoint observation is that てください turns the form into a direct polite request. For this speaker viewpoint clinic, keep three layers separate: printed form, contextual meaning and analytical reason. The te-form engine speaker viewpoint analysis is secure only when the reason survives after familiar vocabulary has been replaced.

For the te-form engine speaker viewpoint check, read from the predicate toward the beginning. During this speaker viewpoint pass, bracket the material that belongs together and label any omitted participant as an inference. Apply the speaker viewpoint parse again to “Please write your name here” without assuming English word order matches Japanese scope. Because てください turns the form into a direct polite request, the marked speaker viewpoint relationship must remain visible in the final explanation.

A realistic failure in this te-form engine speaker viewpoint case would be forming 行いて by analogy with 書いて instead of remembering 行って. That speaker viewpoint shortcut would misrepresent “Please write your name here” because てください turns the form into a direct polite request. Instead of memorizing a red correction for speaker viewpoint, write one conditional rule: the rejected option would work if the scene supplied a different predicate, viewpoint, time relationship or level of authority. Name the exact condition changed in the speaker viewpoint contrast.

Now rebuild the te-form engine speaker viewpoint sentence with a new person, place or time. Preserve the fact that てください turns the form into a direct polite request, but use vocabulary from your own routine for this speaker viewpoint transfer. Make a second speaker viewpoint version that deliberately changes that fact and therefore needs a neighboring construction. Read both speaker viewpoint versions aloud, translate both, and finish by explaining their difference without naming English keywords alone.

7. Case clinic: time and aspect

The working te-form engine sentence for time and aspect is 妹は今、電話で話しています。 Its practical translation is “My younger sister is speaking on the phone now.” The decisive time and aspect observation is that ている presents an activity in progress. For this time and aspect clinic, keep three layers separate: printed form, contextual meaning and analytical reason. The te-form engine time and aspect analysis is secure only when the reason survives after familiar vocabulary has been replaced.

For the te-form engine time and aspect check, read from the predicate toward the beginning. During this time and aspect pass, bracket the material that belongs together and label any omitted participant as an inference. Apply the time and aspect parse again to “My younger sister is speaking on the phone now” without assuming English word order matches Japanese scope. Because ている presents an activity in progress, the marked time and aspect relationship must remain visible in the final explanation.

A realistic failure in this te-form engine time and aspect case would be translating every て as and, even when an auxiliary such as いる changes the construction. That time and aspect shortcut would misrepresent “My younger sister is speaking on the phone now” because ている presents an activity in progress. Instead of memorizing a red correction for time and aspect, write one conditional rule: the rejected option would work if the scene supplied a different predicate, viewpoint, time relationship or level of authority. Name the exact condition changed in the time and aspect contrast.

Now rebuild the te-form engine time and aspect sentence with a new person, place or time. Preserve the fact that ている presents an activity in progress, but use vocabulary from your own routine for this time and aspect transfer. Make a second time and aspect version that deliberately changes that fact and therefore needs a neighboring construction. Read both time and aspect versions aloud, translate both, and finish by explaining their difference without naming English keywords alone.

8. Case clinic: negative scope

The working te-form engine sentence for negative scope is この席に座ってもいいですか。 Its practical translation is “May I sit in this seat?” The decisive negative scope observation is that てもいい asks permission. For this negative scope clinic, keep three layers separate: printed form, contextual meaning and analytical reason. The te-form engine negative scope analysis is secure only when the reason survives after familiar vocabulary has been replaced.

For the te-form engine negative scope check, read from the predicate toward the beginning. During this negative scope pass, bracket the material that belongs together and label any omitted participant as an inference. Apply the negative scope parse again to “May I sit in this seat” without assuming English word order matches Japanese scope. Because てもいい asks permission, the marked negative scope relationship must remain visible in the final explanation.

A realistic failure in this te-form engine negative scope case would be placing politeness on the linked verb instead of allowing the final predicate to carry sentence style. That negative scope shortcut would misrepresent “May I sit in this seat” because てもいい asks permission. Instead of memorizing a red correction for negative scope, write one conditional rule: the rejected option would work if the scene supplied a different predicate, viewpoint, time relationship or level of authority. Name the exact condition changed in the negative scope contrast.

Now rebuild the te-form engine negative scope sentence with a new person, place or time. Preserve the fact that てもいい asks permission, but use vocabulary from your own routine for this negative scope transfer. Make a second negative scope version that deliberately changes that fact and therefore needs a neighboring construction. Read both negative scope versions aloud, translate both, and finish by explaining their difference without naming English keywords alone.

9. Case clinic: politeness and register

The working te-form engine sentence for politeness and register is 試験の前に単語を復習しておきます。 Its practical translation is “I will review vocabulary in advance of the test.” The decisive politeness and register observation is that ておく presents preparation for a later need. For this politeness and register clinic, keep three layers separate: printed form, contextual meaning and analytical reason. The te-form engine politeness and register analysis is secure only when the reason survives after familiar vocabulary has been replaced.

For the te-form engine politeness and register check, read from the predicate toward the beginning. During this politeness and register pass, bracket the material that belongs together and label any omitted participant as an inference. Apply the politeness and register parse again to “I will review vocabulary in advance of the test” without assuming English word order matches Japanese scope. Because ておく presents preparation for a later need, the marked politeness and register relationship must remain visible in the final explanation.

A realistic failure in this te-form engine politeness and register case would be using a Group 2 shortcut on a Group 1 verb such as 帰る or 走る. That politeness and register shortcut would misrepresent “I will review vocabulary in advance of the test” because ておく presents preparation for a later need. Instead of memorizing a red correction for politeness and register, write one conditional rule: the rejected option would work if the scene supplied a different predicate, viewpoint, time relationship or level of authority. Name the exact condition changed in the politeness and register contrast.

Now rebuild the te-form engine politeness and register sentence with a new person, place or time. Preserve the fact that ておく presents preparation for a later need, but use vocabulary from your own routine for this politeness and register transfer. Make a second politeness and register version that deliberately changes that fact and therefore needs a neighboring construction. Read both politeness and register versions aloud, translate both, and finish by explaining their difference without naming English keywords alone.

10. Case clinic: conversation response

The working te-form engine sentence for conversation response is 駅まで歩いてみました。 Its practical translation is “I tried walking to the station.” The decisive conversation response observation is that てみる frames an action as a trial. For this conversation response clinic, keep three layers separate: printed form, contextual meaning and analytical reason. The te-form engine conversation response analysis is secure only when the reason survives after familiar vocabulary has been replaced.

For the te-form engine conversation response check, read from the predicate toward the beginning. During this conversation response pass, bracket the material that belongs together and label any omitted participant as an inference. Apply the conversation response parse again to “I tried walking to the station” without assuming English word order matches Japanese scope. Because てみる frames an action as a trial, the marked conversation response relationship must remain visible in the final explanation.

A realistic failure in this te-form engine conversation response case would be forming 行いて by analogy with 書いて instead of remembering 行って. That conversation response shortcut would misrepresent “I tried walking to the station” because てみる frames an action as a trial. Instead of memorizing a red correction for conversation response, write one conditional rule: the rejected option would work if the scene supplied a different predicate, viewpoint, time relationship or level of authority. Name the exact condition changed in the conversation response contrast.

Now rebuild the te-form engine conversation response sentence with a new person, place or time. Preserve the fact that てみる frames an action as a trial, but use vocabulary from your own routine for this conversation response transfer. Make a second conversation response version that deliberately changes that fact and therefore needs a neighboring construction. Read both conversation response versions aloud, translate both, and finish by explaining their difference without naming English keywords alone.

11. Case clinic: reading evidence

The working te-form engine sentence for reading evidence is 朝ご飯を食べてから出発します。 Its practical translation is “I will leave after eating breakfast.” The decisive reading evidence observation is that てから makes the completion order explicit. For this reading evidence clinic, keep three layers separate: printed form, contextual meaning and analytical reason. The te-form engine reading evidence analysis is secure only when the reason survives after familiar vocabulary has been replaced.

For the te-form engine reading evidence check, read from the predicate toward the beginning. During this reading evidence pass, bracket the material that belongs together and label any omitted participant as an inference. Apply the reading evidence parse again to “I will leave after eating breakfast” without assuming English word order matches Japanese scope. Because てから makes the completion order explicit, the marked reading evidence relationship must remain visible in the final explanation.

A realistic failure in this te-form engine reading evidence case would be translating every て as and, even when an auxiliary such as いる changes the construction. That reading evidence shortcut would misrepresent “I will leave after eating breakfast” because てから makes the completion order explicit. Instead of memorizing a red correction for reading evidence, write one conditional rule: the rejected option would work if the scene supplied a different predicate, viewpoint, time relationship or level of authority. Name the exact condition changed in the reading evidence contrast.

Now rebuild the te-form engine reading evidence sentence with a new person, place or time. Preserve the fact that てから makes the completion order explicit, but use vocabulary from your own routine for this reading evidence transfer. Make a second reading evidence version that deliberately changes that fact and therefore needs a neighboring construction. Read both reading evidence versions aloud, translate both, and finish by explaining their difference without naming English keywords alone.

12. Case clinic: listening cue

The working te-form engine sentence for listening cue is 電気が消えています。 Its practical translation is “The light is off.” The decisive listening cue observation is that with a change-of-state verb, ている can describe the resulting state. For this listening cue clinic, keep three layers separate: printed form, contextual meaning and analytical reason. The te-form engine listening cue analysis is secure only when the reason survives after familiar vocabulary has been replaced.

For the te-form engine listening cue check, read from the predicate toward the beginning. During this listening cue pass, bracket the material that belongs together and label any omitted participant as an inference. Apply the listening cue parse again to “The light is off” without assuming English word order matches Japanese scope. Because with a change-of-state verb, ている can describe the resulting state, the marked listening cue relationship must remain visible in the final explanation.

A realistic failure in this te-form engine listening cue case would be placing politeness on the linked verb instead of allowing the final predicate to carry sentence style. That listening cue shortcut would misrepresent “The light is off” because with a change-of-state verb, ている can describe the resulting state. Instead of memorizing a red correction for listening cue, write one conditional rule: the rejected option would work if the scene supplied a different predicate, viewpoint, time relationship or level of authority. Name the exact condition changed in the listening cue contrast.

Now rebuild the te-form engine listening cue sentence with a new person, place or time. Preserve the fact that with a change-of-state verb, ている can describe the resulting state, but use vocabulary from your own routine for this listening cue transfer. Make a second listening cue version that deliberately changes that fact and therefore needs a neighboring construction. Read both listening cue versions aloud, translate both, and finish by explaining their difference without naming English keywords alone.

13. Case clinic: controlled writing

The working te-form engine sentence for controlled writing is 資料を持ってきてください。 Its practical translation is “Please bring the materials here.” The decisive controlled writing observation is that てくる combines direction toward the reference point with the request. For this controlled writing clinic, keep three layers separate: printed form, contextual meaning and analytical reason. The te-form engine controlled writing analysis is secure only when the reason survives after familiar vocabulary has been replaced.

For the te-form engine controlled writing check, read from the predicate toward the beginning. During this controlled writing pass, bracket the material that belongs together and label any omitted participant as an inference. Apply the controlled writing parse again to “Please bring the materials here” without assuming English word order matches Japanese scope. Because てくる combines direction toward the reference point with the request, the marked controlled writing relationship must remain visible in the final explanation.

A realistic failure in this te-form engine controlled writing case would be using a Group 2 shortcut on a Group 1 verb such as 帰る or 走る. That controlled writing shortcut would misrepresent “Please bring the materials here” because てくる combines direction toward the reference point with the request. Instead of memorizing a red correction for controlled writing, write one conditional rule: the rejected option would work if the scene supplied a different predicate, viewpoint, time relationship or level of authority. Name the exact condition changed in the controlled writing contrast.

Now rebuild the te-form engine controlled writing sentence with a new person, place or time. Preserve the fact that てくる combines direction toward the reference point with the request, but use vocabulary from your own routine for this controlled writing transfer. Make a second controlled writing version that deliberately changes that fact and therefore needs a neighboring construction. Read both controlled writing versions aloud, translate both, and finish by explaining their difference without naming English keywords alone.

14. Case clinic: translation discipline

The working te-form engine sentence for translation discipline is 友だちが写真を送ってくれました。 Its practical translation is “A friend sent me a photograph.” The decisive translation discipline observation is that てくれる adds a beneficiary viewpoint. For this translation discipline clinic, keep three layers separate: printed form, contextual meaning and analytical reason. The te-form engine translation discipline analysis is secure only when the reason survives after familiar vocabulary has been replaced.

For the te-form engine translation discipline check, read from the predicate toward the beginning. During this translation discipline pass, bracket the material that belongs together and label any omitted participant as an inference. Apply the translation discipline parse again to “A friend sent me a photograph” without assuming English word order matches Japanese scope. Because てくれる adds a beneficiary viewpoint, the marked translation discipline relationship must remain visible in the final explanation.

A realistic failure in this te-form engine translation discipline case would be forming 行いて by analogy with 書いて instead of remembering 行って. That translation discipline shortcut would misrepresent “A friend sent me a photograph” because てくれる adds a beneficiary viewpoint. Instead of memorizing a red correction for translation discipline, write one conditional rule: the rejected option would work if the scene supplied a different predicate, viewpoint, time relationship or level of authority. Name the exact condition changed in the translation discipline contrast.

15. Case clinic: contrastive substitution

The working te-form engine sentence for contrastive substitution is まだ箱を開けてはいけません。 Its practical translation is “You must not open the box yet.” The decisive contrastive substitution observation is that てはいけない expresses prohibition. For this contrastive substitution clinic, keep three layers separate: printed form, contextual meaning and analytical reason. The te-form engine contrastive substitution analysis is secure only when the reason survives after familiar vocabulary has been replaced.

For the te-form engine contrastive substitution check, read from the predicate toward the beginning. During this contrastive substitution pass, bracket the material that belongs together and label any omitted participant as an inference. Apply the contrastive substitution parse again to “You must not open the box yet” without assuming English word order matches Japanese scope. Because てはいけない expresses prohibition, the marked contrastive substitution relationship must remain visible in the final explanation.

A realistic failure in this te-form engine contrastive substitution case would be translating every て as and, even when an auxiliary such as いる changes the construction. That contrastive substitution shortcut would misrepresent “You must not open the box yet” because てはいけない expresses prohibition. Instead of memorizing a red correction for contrastive substitution, write one conditional rule: the rejected option would work if the scene supplied a different predicate, viewpoint, time relationship or level of authority. Name the exact condition changed in the contrastive substitution contrast.

16. Case clinic: delayed recall

The working te-form engine sentence for delayed recall is 道を聞いて、地図を見て、会場を見つけました。 Its practical translation is “I asked the way, checked a map, and found the venue.” The decisive delayed recall observation is that successive て-forms organize related steps before the final tensed verb. For this delayed recall clinic, keep three layers separate: printed form, contextual meaning and analytical reason. The te-form engine delayed recall analysis is secure only when the reason survives after familiar vocabulary has been replaced.

For the te-form engine delayed recall check, read from the predicate toward the beginning. During this delayed recall pass, bracket the material that belongs together and label any omitted participant as an inference. Apply the delayed recall parse again to “I asked the way, checked a map, and found the venue” without assuming English word order matches Japanese scope. Because successive て-forms organize related steps before the final tensed verb, the marked delayed recall relationship must remain visible in the final explanation.

A realistic failure in this te-form engine delayed recall case would be placing politeness on the linked verb instead of allowing the final predicate to carry sentence style. That delayed recall shortcut would misrepresent “I asked the way, checked a map, and found the venue” because successive て-forms organize related steps before the final tensed verb. Instead of memorizing a red correction for delayed recall, write one conditional rule: the rejected option would work if the scene supplied a different predicate, viewpoint, time relationship or level of authority. Name the exact condition changed in the delayed recall contrast.

17. Independent exercises

• Exercise 1: For 窓を開けて、空気を入れました。 underline the final predicate and draw the attachment boundary. Use the te-form engine to justify every changed element. Do not inspect the supplied translation, “I opened the window and let air in.,” until your structural explanation is complete.
• Exercise 2: For ここに名前を書いてください。 move the scene into the past and decide which ending carries that change. Use the te-form engine to justify every changed element. Do not inspect the supplied translation, “Please write your name here.,” until your structural explanation is complete.
• Exercise 3: For 妹は今、電話で話しています。 make the intended negative scope explicit. Use the te-form engine to justify every changed element. Do not inspect the supplied translation, “My younger sister is speaking on the phone now.,” until your structural explanation is complete.
• Exercise 4: For この席に座ってもいいですか。 replace the participant and check whether viewpoint remains stable. Use the te-form engine to justify every changed element. Do not inspect the supplied translation, “May I sit in this seat?,” until your structural explanation is complete.
• Exercise 5: For 試験の前に単語を復習しておきます。 rewrite the setting for a workplace or public notice. Use the te-form engine to justify every changed element. Do not inspect the supplied translation, “I will review vocabulary in advance of the test.,” until your structural explanation is complete.
• Exercise 6: For 駅まで歩いてみました。 construct the closest competing version and state its different implication. Use the te-form engine to justify every changed element. Do not inspect the supplied translation, “I tried walking to the station.,” until your structural explanation is complete.
• Exercise 7: For 朝ご飯を食べてから出発します。 turn the statement into a socially suitable question or response. Use the te-form engine to justify every changed element. Do not inspect the supplied translation, “I will leave after eating breakfast.,” until your structural explanation is complete.
• Exercise 8: For 電気が消えています。 summarize the Japanese relationship before producing natural English. Use the te-form engine to justify every changed element. Do not inspect the supplied translation, “The light is off.,” until your structural explanation is complete.

18. Worked answer principles

• Answer principle 1: A valid response preserves or intentionally changes the fact that the first て-form connects a natural action sequence. For answer 1, the exact vocabulary may differ, but the te-form engine explanation must account for “I opened the window and let air in” and must say why the competing structure would present another relationship.
• Answer principle 2: A valid response preserves or intentionally changes the fact that てください turns the form into a direct polite request. For answer 2, the exact vocabulary may differ, but the te-form engine explanation must account for “Please write your name here” and must say why the competing structure would present another relationship.
• Answer principle 3: A valid response preserves or intentionally changes the fact that ている presents an activity in progress. For answer 3, the exact vocabulary may differ, but the te-form engine explanation must account for “My younger sister is speaking on the phone now” and must say why the competing structure would present another relationship.
• Answer principle 4: A valid response preserves or intentionally changes the fact that てもいい asks permission. For answer 4, the exact vocabulary may differ, but the te-form engine explanation must account for “May I sit in this seat” and must say why the competing structure would present another relationship.
• Answer principle 5: A valid response preserves or intentionally changes the fact that ておく presents preparation for a later need. For answer 5, the exact vocabulary may differ, but the te-form engine explanation must account for “I will review vocabulary in advance of the test” and must say why the competing structure would present another relationship.
• Answer principle 6: A valid response preserves or intentionally changes the fact that てみる frames an action as a trial. For answer 6, the exact vocabulary may differ, but the te-form engine explanation must account for “I tried walking to the station” and must say why the competing structure would present another relationship.
• Answer principle 7: A valid response preserves or intentionally changes the fact that てから makes the completion order explicit. For answer 7, the exact vocabulary may differ, but the te-form engine explanation must account for “I will leave after eating breakfast” and must say why the competing structure would present another relationship.
• Answer principle 8: A valid response preserves or intentionally changes the fact that with a change-of-state verb, ている can describe the resulting state. For answer 8, the exact vocabulary may differ, but the te-form engine explanation must account for “The light is off” and must say why the competing structure would present another relationship.

19. Fourteen-day consolidation plan

On days one and two, reconstruct the te-form engine rule—Group 2 verbs generally replace る with て; する becomes して and 来る becomes 来て; Group 1 endings follow the って, んで, いて, いで or して sound patterns, with 行く becoming 行って.—and parse the first two cases. Days three and four cover cases three through six with one controlled substitution each. Day five is an error day: correct all four listed pitfalls and write the changed condition that would make each rejected form acceptable.

Days six and seven turn the te-form engine into sound. Record four original te-form engine lines, listen without text, and mark the cue that carries the relationship. On day eight, use cases seven through ten for te-form engine reading practice. Write a five-word te-form engine function label beside each sentence, such as rule, endpoint, concession, report or representative example.

Days nine through eleven focus on te-form engine production. Adapt cases eleven and twelve to your own work, study or travel situation. Pair every new te-form engine line with a contrast that changes only one factor. On day twelve, translate the te-form engine pair naturally, then add a structural note so fluent English does not erase the Japanese distinction.

Day thirteen is a closed-book mixed check. Day fourteen is a short dialogue or paragraph where the te-form engine solves a real communicative need. Schedule later checks after three days, one week and one month. Track accuracy, explanation quality and response time separately; improvement in one measure can reveal progress before all three become stable.

20. Final mastery checklist

You can state the te-form engine formation rule and reconstruct at least two original examples. You can bracket a longer sentence without assigning every visible particle to the featured construction. You can locate tense, negation and politeness at the predicate that actually carries them. These are stronger signs of control than recognizing a highlighted form.

You can explain this te-form engine contrast in your own words: The て-form itself does not supply one fixed English meaning or a complete tense. The expression after it and the surrounding clause determine its job. You can also describe a scene where the closest alternative becomes preferable. If your explanation depends on one memorized noun, substitute a new participant and time. A transferable rule should still predict the choice after that change.

You can diagnose using a Group 2 shortcut on a Group 1 verb such as 帰る or 走る, forming 行いて by analogy with 書いて instead of remembering 行って, translating every て as and, even when an auxiliary such as いる changes the construction, and placing politeness on the linked verb instead of allowing the final predicate to carry sentence style. Keep any recurring problem in a small error log with the decisive clue and a corrected pair. Retire an item only after several delayed attempts succeed for the right reason, not immediately after rereading the answer.

You can use the te-form engine while following a conversation or paragraph without losing its larger purpose. When uncertainty remains, you know whether to consult an official teaching reference, inspect corpus examples or ask for contextual information. That combination of formation, meaning, register and verification completes the chapter.