Service Skills for ITE Students: Ask Better Questions and Write a Clear Handover

Tom — Singapore Digital Business & Systems Consultant

Tom

Digital Business & Systems Consultant · Singapore

7 min read Article date First published
Service Skills for ITE Students: Ask Better Questions and Write a Clear Handover

Good client communication comes down to three habits: ask what outcome the person needs before discussing what to make, write a short factual summary they can check, and confirm who owns the next step and by when. When you do not understand something, say so and promise to check. Below is a one-page discovery-to-handover template for a part-time shift, an attachment, a class project or a relative's request.

Key takeaways

  • Ask about the outcome first, not what to build.
  • Summarise in the person's words, separate facts from guesses, and let them correct it.
  • Every handover ends with one next step, one owner and one date.
  • "Let me check" is a professional answer when you follow through.

Why these skills matter in any client-facing role

Whatever your course, someone will ask for something they cannot fully describe: "a website", or "the report fixed". The skill is turning that request into something you can both check. Shifts in F&B, retail or events already train this, because taking an order back to the kitchen correctly is a handover. No selling is needed.

Ask what outcome the person needs

People often name a solution ("I need an app") when they mean an outcome ("I'm tired of answering the same question all day"). Ask about the outcome first, and write down their words, not your translation:

  • "What would you like to be different after this?"
  • "What happens now when this comes up?"
  • "Who else is affected: customers, staff or family?"
  • "When do you need it sorted, and why then?"

When you do not understand the technical request yet

Nodding along to words like "SEO" or "backend" usually costs more time later. Copy the term exactly with a question mark, then try:

  • "I'm not familiar with that term. Can you show me what it looks like now?"
  • "When you say a booking system, what would a customer do with it, step by step?"
  • "I don't want to guess. Let me check with someone who knows."

Write a short factual summary

Right after the conversation, write five to eight lines. Then send it or read it back: "Did I get this right?" A correction now is cheaper than a wrong job later.

  • Facts first, in the person's words; label any guess as a guess.
  • Write "unknown" instead of filling a gap yourself.
  • Record prices or dates they mention as questions, never as promises.
  • Leave out passwords, customer lists and private screenshots.

Confirm who owns the next step

Many handovers fail at the last line, because everyone assumed someone else would act. End every summary with one action, one named owner and a date:

  • "Next: I'll send you two options by Thursday evening."
  • "Next: you decide by Friday whether to speak to a developer. I'll wait to hear from you."

Saying "let me check and come back"

Not knowing is normal. Name what you will check, who you will ask and when you will reply:

  • "I don't want to give you the wrong answer. Let me check with my supervisor and reply by 6pm."
  • "I'm not sure that's possible. I'll find out and reply tomorrow, even if it's a no."
  • "I can't promise that. I'll pass it to the person who can, and tell you who they are."

Then reply on time, even if only to say "still checking".

The one-page discovery-to-handover template

Copy these six sections into your phone's notes, fill them in during or after the conversation, and show the person before anyone acts on it.

SectionWhat to writeA question that helps
1. Outcome neededWhat should be different, in their words"What would you like to be different?"
2. Current situationWhat happens today and what they tried"What happens now?"
3. ConstraintsTime, people and limits they mention"What should I work around?"
4. What I will doSmall actions you can actually deliver"Would it help if I…?"
5. What I will not doPrices, dates, results or access that are not yours to promise"Someone else must confirm that."
6. Next step and dateOne action, one owner, one date"So the next step is… by…?"

A filled-in example (fictional example)

Syafiq studies an IT-related course at ITE. His neighbour, Mdm Chua, runs a one-person clothing alteration shop and asks him to "make a website, since you study computers". Instead of saying yes or no, he asks what she wants to change, then writes:

  • Outcome: fewer calls asking "is my alteration ready?"; she misses calls while sewing.
  • Current situation: paper ticket book; customers call or message her mobile.
  • Constraints: works alone; calls come mostly on weekdays; not ready to spend money yet.
  • I will: send this summary, and show her on my phone how a saved reply for "is it ready?" messages could work.
  • I will not: build a website, quote a price, promise the calls will stop, or ask for her passwords.
  • Next step: Syafiq sends this by Wednesday; Mdm Chua decides by Saturday whether to try the saved reply or speak to a web developer.

Reading it back, Mdm Chua corrects the constraints: most calls come on Saturdays. That changes what would help.

The upside: the saved reply may be enough, and Syafiq gains a portfolio story about solving a problem without building anything. The uncertainty: she may want a website after all, or wait a year. If she speaks to a developer, his summary becomes her starting brief; the decision and the relationship stay hers. The effort: two short conversations and twenty minutes of unpaid writing.

Using the same habits for a website introduction

Sometimes the outcome really is a website or system. BusinessWithTom runs a referral programme: with a business owner's permission, you introduce them, and I handle the discovery call, proposal and closing. You do not sell, quote or promise results, and you tell the owner early that you may receive a referral payment.

Commission terms, covered services and payment timing are on that page; read the current version and confirm with me first. Commission is not guaranteed: your introduction must have directly contributed to the project, as the programme terms define it, and an introduction can end with no project. The programme is for adults aged 18 or over; if your right to do this depends on a pass, such as a Student's Pass, check with the issuing authority first. Side hustles for ITE students covers those checks.

For the introduction itself, use the shorter seven-field brief for website enquiries. To understand what I build, read the website development page.

Practise before you need it

Try the template on your next class project brief or family request. Turning a course project into customer research? Start with a customer problem interview. At a part-time job, follow your employer's handover method and keep customer details inside it, never in a personal note.

Before you send a handover

  • The outcome is in the person's words, and gaps say "unknown".
  • I listed what I will not promise: prices, dates or results.
  • There is one next step, one owner and one date.
  • The person has seen the summary or heard it read back.
  • I have not collected passwords, customer lists or private screenshots.

Sources (checked 31 October 2026)

Frequently Asked Questions

What if I do not understand the technical request?

Say so early, and ask the person to show you what happens now or describe what a customer would do, step by step. Note their exact words and check with someone who knows before promising anything.

How can I say I need to check an answer?

Name what you will check, who you will ask and when you will reply, such as: let me confirm with my supervisor and message you by 6pm. Then reply on time, even if the answer is still pending.

Do I need a client to practise these skills?

No. A class project brief, a shift handover or a relative's request is enough, and nothing needs to be sold.

What if someone asks me for a price or a date?

Write it down as a question, not a promise, and say who will answer it.

Can I use this template for a referral to BusinessWithTom?

It helps you understand the need, but for an introduction use the shorter referral brief and read the current programme page first. The programme is for adults aged 18 or over, and if your right to do this depends on a pass, check with the issuing authority before introducing anyone.

Curious whether the referral route suits you? It is for adults aged 18 or over; message me with your questions before you introduce anyone. No obligation: the template is useful either way.

No obligation. No sales pitch. Just an honest conversation.

お問い合わせ