What to do when your manager sends a "quick" Excel task

Your manager sends a message at 4:47pm on a Friday.

"Can you just do a quick vlookup against the client master list before you log off? Cheers."

You say yes. They go offline. You open the file. The "master list" has 47 columns, half of them are dates in three different formats, and there's a tab called DO NOT USE that has data in it.

It is not quick.

If you've been on a graduate scheme for more than a fortnight you've had a version of this moment. The senior who asked isn't being cruel. They've done this task two hundred times and have genuinely forgotten what not-knowing feels like. To them it is quick. To you it's a tightrope walk over your probation review.

Here's a method that works. It's not clever. It's just the order of operations nobody tells you on day one.

First, translate the request

Most "quick" Excel asks translate roughly like this:

• "Quick vlookup" — there are duplicates and the lookup column has probably moved since the last version
• "Just sum this column" — the column has hidden rows and a #REF! error halfway down
• "Pull the totals by region" — the region names are spelled three different ways ("London", "london", "LDN")
• "Format it nicely for the client" — it should match the firm's branded report template, which they have not shared with you

Spotting which of these you're actually being asked to do is half the battle.

The 4-step method

1. Buy thirty seconds before you say yes

Don't reply "on it!" the second the message arrives. Reply with one clarifying question. Even a basic one works:

"On it. Quick check — output in a new tab, or overwriting the existing summary?"

This does two things. It makes you look like someone who thinks before they act. And it forces the senior to specify, which means if something turns out wrong later, it's not solely on you.

2. Look at the data before touching anything

Open the file. Click on cell A1. Press Ctrl + End. Where does the data actually end? Press Ctrl + ↓ on each key column. Are there gaps? Is column C dates and column D also dates, but in different formats?

Ninety seconds of looking will save you thirty minutes of "why is XLOOKUP returning #N/A for half the rows."

3. Use these three formulas, in this order

You don't need to know all of Excel. You need to know three formulas and when to reach for each.

For looking up values from another table — XLOOKUP, not VLOOKUP. XLOOKUP doesn't break when someone reorders the columns in the source file. The syntax:

=XLOOKUP(what_you're_looking_up, where_to_look, what_to_return, "Not found")

For summing with conditions — SUMIFS, not a manual filter. SUMIFS keeps working when the data updates next week. Syntax:

=SUMIFS(numbers_to_sum, region_column, "London", date_column, ">=01/04/2026")

For cleaning messy text — TRIM and PROPER. TRIM removes trailing and leading spaces, which cause roughly 60% of all "why doesn't my lookup match" panics. PROPER fixes inconsistent capitalisation. Both are one argument long:

=TRIM(A2) and =PROPER(A2)

Three formulas. They solve eighty per cent of "quick" tasks.

4. Sanity-check before you send

Before you hit send, do three things:

• Filter the data and eyeball five rows by hand. Do they match what your formula returned?
• Scroll to the bottom of the file. Did you accidentally include rows you shouldn't have, like a totals row?
• If you can, open it on your phone for ten seconds. The formatting often looks completely different on a smaller screen, and the senior will likely view it that way first.

Two minutes of checking saves you from the 6:15pm message that begins "this can't be right…"

The actual skill of corporate Excel is knowing which three formulas to reach for in a panic.

The bigger thing nobody tells you

You are not stupid for not knowing how to do this. The senior who asked was also lost in their first week. They've just had longer to forget.

The job isn't memorising every function. It's having a small, reliable toolkit and the discipline to look at the data before you start typing. That's it. That's the whole thing.

Build that toolkit and the "quick" task on Friday afternoon stops being scary. It becomes ten minutes of work and a clean reply.