Stuck at work? How to ask for the help you actually need

Work out what kind of stuck you are

Before writing a message, complete this sentence: “I can do the next part if I have…” Be specific about what is missing rather than deciding that you are simply bad at the whole task.

If you do not understand the task, ask for the expected outcome or an example of good work. “Which decision should this report help us make?” is more useful than guessing what a previous report was trying to do. In a new role, our first-month agreement guide can help you clarify those expectations earlier.

If you understand the task but do not know the method, ask for an explanation of one step. If you cannot get the information or permission you need, ask who owns access or the decision. If you know what to do but cannot fit it into the available time, you have a capacity question, not necessarily a skills problem.

You may have more than one obstacle. Separate them. “I need the account owner to approve access, and I need you to choose which deadline can move” is clearer than presenting the entire situation as a request for someone to teach you the software.

Try enough to locate the obstacle, not to prove your worth

For ordinary, reversible work, inspect the relevant instructions and try a reasonable approach. Make a short note of what you checked and where it stopped helping. You are gathering information for the conversation, not producing a defence of every minute you spent.

There is no universal rule that you should struggle alone for twenty minutes or two hours. A familiar task, a new system and a time-sensitive decision need different judgement. If continuing could create a safety, security, customer or financial problem, stop and use the appropriate workplace route promptly. Do not make a risky change just to show that you tried something first.

If you genuinely do not know where to begin, say that. “I have read the brief, but I cannot tell which source of information we should use. Could you help me identify the starting point?” is an honest request. Inventing attempts makes the next conversation harder.

The National Careers Service includes asking questions to understand the bigger picture within its problem-solving guidance^[1]. That supports treating a well-placed question as part of doing the work, not as the opposite of being capable.

Make the smallest request that would genuinely help

“Can you help with this?” leaves the other person to discover the problem, estimate the effort and decide what you want from them. Give them a more bounded request: explain a step, check a choice, identify an owner or make a decision.

For an explanation, try: “Could you walk me through how you choose the reporting period? I can complete the rest once I understand that decision.” For a review: “I have two possible approaches. Could you check the assumption in the first one before I continue?”

For access: “The instructions refer to the team folder, but my account cannot open it. Who can authorise access?” For a decision: “I can deliver the short version by Friday, or the full version next week. Which outcome do you want me to prioritise?”

Do not make a request artificially small to make it easier to accept. If you need a substantial handover or training session, say so. “A quick question” that turns into an hour of unplanned work does not respect either person's time.

A five-line request you can adapt

Use the following prompts as a drafting aid. They are CareerFood's practical template, not a validated communication model. You can combine them into a short message rather than sending five rigid headings.

Outcome: “I am preparing [specific piece of work] for [purpose or agreed deadline].”

What I checked: “I have checked [relevant instruction or example] and tried [appropriate step].” If you have not tried a step, describe what you reviewed instead.

Blocker: “I am stuck at [precise point], because [information, permission, understanding or capacity that is missing].”

Request: “Could you [explain, check, point me to, approve or decide the specific thing]?”

Next move: “With that clarified, I will [what you will do next]. If you cannot help, is there an appropriate person or channel I should use?”

Keep the context proportionate. Share an approved link or a small, safe example if it helps. Do not send a confidential document to a personal account or paste workplace information into an unapproved AI tool just to make your question easier to answer.

A worked example: the numbers do not match

Imagine Priya is preparing a weekly service update. A dashboard and an exported report show different totals. She has checked the dates and filters but cannot establish which definition the team uses. This is a fictional example, not a reported customer case.

Her first message is: “The reporting system is confusing. Can you take a look?” A colleague would need to reconstruct almost everything before helping. A more useful message is:

“I am preparing Friday's service update. I checked that the dashboard and export cover the same week, but they still show different totals. I cannot tell whether the export excludes reopened cases. Could you confirm which definition we use, or point me to the person who owns it? Once that is clear, I will finish the update and note the definition alongside the figure.”

The improved message does not pretend that Priya has found the cause. It distinguishes what she checked from what she suspects. It also asks for a definition, not for the colleague to finish the whole report.

If the answer is “I do not know”, the useful next step is finding the owner or agreeing how to handle the uncertainty. It is not choosing the more flattering total. If the agreed deadline is at risk, Priya should make that visible while there is still a decision to make.

Choose the route, not just the wording

Use the person or channel appropriate to the obstacle. A team reference page may answer a routine question. A colleague may be able to explain a method. A manager may need to resolve competing priorities. A designated support team may own an access problem.

State the real time constraint without manufacturing urgency. “I need the decision by Thursday afternoon to meet the agreed Friday deadline” explains the dependency. “Urgent!!!” does not. For an immediate risk, use the relevant escalation process rather than waiting for a normal chat reply.

If no answer arrives, follow up with the consequence and the choice: “I am still blocked on the reporting definition. Without it, I can send a clearly labelled provisional update or move the deadline. Who should agree that decision?” Keep any provisional work within what your workplace permits; a draft label does not make an unsafe action acceptable.

When the real issue is missing support

If you keep returning to the same obstacle, improve the working arrangement rather than polishing the message indefinitely. You might need an agreed training session, a current example, a named decision owner or a regular point for questions. Confirm who will maintain any shared note instead of silently taking on another responsibility.

The Health and Safety Executive's support standard^[2] describes support as including resources from the organisation, managers and colleagues, and knowing how to access them. The point here is narrow: effective support is not solely a matter of an employee finding the perfect sentence. This article is not a legal assessment of your employer.

If the issue is too much work rather than missing knowledge, use our guide to asking which priority should move. If you need to question the approach rather than learn it, our guide to disagreeing with your manager addresses that different conversation.

Close the loop without pretending it is solved

After getting help, summarise what you understood and what you will do. “Thanks. I will use the agreed definition, finish the update and bring back any remaining mismatch” gives the other person a chance to correct a misunderstanding.

If their answer did not resolve the obstacle, say where you are still stuck. You can be appreciative without claiming that you now understand something you do not. Record a reusable explanation in an approved team location if that is appropriate, not in a private archive of work files.

For your next stuck task, write the outcome, the obstacle and the specific help you need before opening a message. Read it once from the recipient's point of view: can they tell what you are asking them to do? Then ask while there is still time to use the answer.