Task Fulfillment is about doing exactly what the prompt asks, in the right tone, within the word range.
What Task Fulfillment checks (plain view)
- Relevance: You answer the question they asked.
- Completeness: You cover every sub-task/bullet.
- Tone: You write with the right voice for the situation.
- Word Count: You stay close to 150–200 words.
Staying on-task (fast routine)
Step 1 — Mark the sub-tasks
- Underline each “Do the following” bullet.
- Turn each bullet into a simple sentence you will include.
Step 2 — Map one place for each
- Email: greeting → purpose → bullet A → bullet B → next steps → sign-off
- Survey: choice in line 1 → reason A → reason B → brief wrap-up
Step 3 — Relevance filter
- Before typing, ask: “Does this line answer a bullet or support my choice?”
If not, cut it.
Step 4 — End-of-draft sweep
- Can you point to where each bullet is answered? If not, add one clear sentence.
Covering all sub-tasks (bullet-to-sentence method)
- Write one short sentence for each bullet.
- Add one detail/example to each sentence.
- Keep one idea per paragraph so nothing gets lost.
Email example (prompt says: describe the problem; explain impact; request actions; ask next steps)
- Problem: “The north elevator stops often, including last night.”
- Impact: “Residents on higher floors miss deliveries and appointments.”
- Request: “Please send a technician and post daily repair updates.”
- Next steps: “Kindly confirm the repair date and who to contact.”
Word count: hit the range without padding
Target: about 150–200 words. Use the on-screen counter.
If you’re short
- Add one concrete detail (time, place, small number).
- Give a result: “This reduces wait times by…”
If you’re long
- Cut filler (really, very, a lot).
- Merge two similar sentences.
- Remove repeated ideas.
Tone control by task
Emails (semi-formal)
- Voice: polite, professional, clear.
- Moves: greeting → purpose → reasons + examples → request/next steps → sign-off.
- Useful frames:
- “I’m writing to report/request/follow up on…”
- “Could you please… / Would it be possible to…?”
- “Please let me know by… / Kindly confirm…”
Common tone errors → fixes
- Too casual: “Hey, this is a pain.” → “Hello, I’m writing about repeated delays.”
- Too harsh: “Your staff is terrible.” → “Service delays have caused missed appointments.”
- Missing ask: Add a clear request and timeline.
Surveys (concise & persuasive)
- Voice: direct, confident, respectful.
- Moves: choice in line 1 → 2–3 reasons with short examples → brief nod to the other option (only if space).
- Useful frames:
- “I support X because…”
- “This reduces… / This improves… / As a result…”
- “Although Y helps in one way, X solves the main problem.”
Common tone errors → fixes
- Academic style: “In summation, aforementioned…” → Plain: “In short, X helps more because…”
- Both-sides writing: Decide early; keep focus on your choice.
Before → After (Task Fulfillment in action)
Before (off-task + wrong tone)
“I think parks are cool. People like them. Anyway, thanks.”
After (on-task + right tone)
Survey: “I support funding new park washrooms because they cut long waits for families. First, weekend events bring large crowds, so lines form quickly. Second, clean facilities keep parks usable in winter. Although extra benches help, washrooms solve the main problem.”
Micro-checklist (copy before you submit)
Relevance & Completeness
- Every bullet answered
- Each idea supports the task or my choice
Tone
- Email: polite request + clear next steps
- Survey: firm choice in line 1; respectful, concise reasons
Word Count
- Near 150–200 words (checked on screen)
Final pass (1–2 mins)
- No repeated ideas or filler
- One concrete detail per reason
- Sign-off (email) or short wrap-up (survey)
5-minute “Task & Tone” audit
- Mark bullets; write one sentence per bullet (1 min).
- Add one detail/result to each (2 min).
- Tone check: swap any casual/harsh words (1 min).
- Trim/pad to 150–200; confirm ask or choice is clear (1 min).