What It Is Like to Be a Management Consultant 2026: Counted

Ten hours before dinner, in three days the firm published

McKinsey has published three consultant days with complete timestamps. Counted from the first work block to the departure for the evening meal, and with meals subtracted, they come to 10 hours, 10 hours and 10 hours 45 minutes. All three then describe further work after dinner, with no length attached to it.

Here is the arithmetic, done in the order each account sets it out.

The Chicago associate whose day McKinsey published on 17 March 2016 arrives with her teammate at 8am and leaves for a team dinner at 7pm. That span is 11 hours. Dinner runs from 7pm to her 9pm return to the hotel, another 2 hours, giving 13 hours from 8am to 9pm. Lunch takes 1 hour and dinner takes 2, so 13 minus 3 leaves 10 hours of labeled work.

The Santiago day splits the same way. Its author starts at the client at 8:30am and leaves for dinner at 8pm, an 11.5 hour span, with a 1.5 hour lunch inside it. 11.5 minus 1.5 leaves 10. His client-facing time is the 2.5 hour morning meeting plus the 2 hour coordination meeting, which makes 4.5, and the rest adds to 5.5. The check holds: 4.5 plus 5.5 is 10.

The London day resists a clean split, and we say so rather than force one. Its lunch doubled as the team kick-off, so it cannot honestly be deducted. The span from arrival at 8am to leaving at 6:45pm is 10 hours 45 minutes, and she had already worked on slides before 8am.

The only weekly management consultant number in writing

Bain states a floor. Its live Consultant posting, checked 30 September 2026, says that "given the workload and performance expectations of this position, consultants are regularly required to work more than 50 hours/week to perform essential duties of the job." That sentence appears on a posting covering more than 60 offices at once, with no variation by city.

Spread across five days, 50 hours is 10 hours a day. The word Bain uses is "more than," so 10 is the floor of a floor. Set that beside the three counted days above and the two numbers agree to the hour, which is the useful result: the published day is roughly a 10 hour day before the evening block, and the evening block sits on top of it.

McKinsey declines to give a number at all. Its Denmark careers page, checked 30 September 2026, says "there is no typical week at McKinsey Denmark, and while long hours are not an uncommon requirement at varying points during a client-project cycle, we are committed to offering our consultants work-life flexibility." BCG also declines. Its Consultant posting dated 28 September 2026 says the role "at times, requires extended working hours" and stops there.

Three firms, three levels of precision on one question. One files a number, one describes a pattern, one uses an adverb. The number is worth more than the adverb, and it comes from the firm with the least incentive to publish it.

What a management consultant does, hour by labeled hour

The hour count answers how long. The labels answer what a management consultant does with those hours, and they are more surprising than the total. They also answer what a management consultant is in the only way this page can source it, which is by what four named people recorded themselves doing.

The three published days carry 34 timestamped blocks between them: 12, 12 and 10. Eight of those are meals or personal time, and three are the wake-up. That leaves 34 minus 8 minus 3, which is 23 work blocks. Of the 23, a meeting or a call accounts for 16. That is close to seven in ten.

The names the authors give those blocks are worth listing, because they are the job:

1. Client meeting, at 9am, 8am and 8:30am respectively.
2. Internal problem solving session with the wider firm team.
3. Structuring a data request with an analyst on the client side.
4. Drafting or reviewing slides and building a presentation outline.
5. Email, to-do lists and summaries of what each meeting decided.
6. Mentoring, professional development conversations and diary management.
7. A meal with the team, the client, or a colleague.

Not one of the 23 blocks is labeled as producing a strategic idea. The thinking is spread through the problem solving sessions and the slide work, and it never gets an hour of its own with its own name on it.

How the management consultant day changes from intern to principal

Four published accounts sit at four different rungs, and the share of the day spent in front of a client is the figure that moves. Two firms and four years separate them, so this is four accounts rather than a ladder.

Recomputed by hand. The Chicago day puts 3 client-facing hours inside 10 counted hours, so 3 over 10 is 30 percent. Santiago puts 4.5 inside 10, which is 45 percent. London puts 5 inside 10 hours 45 minutes, and 5 divided by 10.75 is 0.4651, so about 47 percent, rounded. The intern's account carries no closing timestamp, so no denominator exists and we leave the cell empty rather than guess at one.

Two things move together across those three computable rows. The client-facing share rises with the rung, and the solo work block moves later in the day: the associate drafts slides in the afternoon, the implementation leader starts his own block at 5pm, and the principal has already done hers before 8am.

Say what that is worth and no more. These are three single days at three rungs, chosen for publication by the employer, and nothing here establishes a rule. Bain's weekly floor, the only number in writing, covers the Consultant title across more than 60 offices with no level breakdown at all, and no firm in our reading publishes hours by rank. The direction in the table is a pattern in three accounts.

What travel looks like in the four published days

No firm in our reading publishes a number of nights away from home, or a number of days per week on a client site. What exists is a sentence, a country count, and three accounts that disagree with each other.

BCG writes the sentence in the job itself. Its Consultant posting says consulting work is "much of it performed at our client sites", that "projects can vary in length, size, and location, depending on the client's challenge", and that "because our clients operate all over the world, you may travel internationally." Three clauses, no frequency.

McKinsey's Denmark page supplies the one count anybody publishes: consultants from that office worked in more than 30 countries last year. That measures the spread of a single office's work rather than the load on one person, and it is still the most concrete travel figure we found.

Then the published days break the pattern three different ways. The Chicago associate starts her day in a hotel lobby with her teammate, so she is away. The London principal walks into the office at 8am and spends her evening at home. The Santiago leader calls his family at 9pm from his own city. One firm, three accounts, three travel realities. The BCG intern states she was in the office three or four days a week, and she also states the reason, which was the pandemic, so that figure describes 2021 rather than the job.

The honest summary is that travel in this job is set by the staffing of one project rather than by the role, which is why the firms write it as a possibility and never as a rate.

Why 10 hours and 14 hours are both honest answers

Search results for this question usually give a 12 to 14 hour day, with spikes to 16. The firms' own timestamps give 10. Both can be true, and the difference is a definition rather than a disagreement.

Count labeled work blocks and the Chicago day is 10 hours. Count from waking to sleeping and the same day is 6:45am to about 11pm, which is 16 hours 15 minutes. Inside that span sit a commute spent on email, a working lunch at the client cafeteria, a team dinner, and a wrap-up session at the hotel. Whether those count is the whole question.

Our view, stated as a view: the honest number depends on which of those you would describe as your evening. A commute where you clear your inbox is work by any test. A team dinner is somewhere in between, and the published accounts treat it as the good part of the day rather than as a cost.

What matters for a decision is the shape of the day rather than one figure. The day starts before 9am, runs past 6pm, contains a social block you do not choose, and reopens after dinner. If any of those four is a problem, the total hours are not the thing to look at.

The evening block every management consultant account describes

Three published days, three returns to work after dinner: 9pm, 9pm and 10pm. Every one of the three describes it, and not one gives it a length.

The London principal is explicit about how she feels about it. "I prefer not to work in the evenings, but in this case, it was worth the investment," she writes, before working through a few pages at home while her husband was out. The Santiago account ends with "10:00pm Wrap up. I review a document one of the teams prepared on operational improvement. Now it's time for sleep." The Chicago account has her back at the hotel at 9pm to "wrap up anything I need for the next day," in bed around 11pm.

This is the part of the job that the hour count hides. The evening block is short, it is routine, and it is unbounded. It also explains why the weekly figure Bain files sits above 50 rather than at 50: five 10 hour days make exactly 50, and the evenings are what push it over.

The week and the project cycle a day sits inside

The published days are single days. What governs a week is the project, and here McKinsey does say something concrete: "projects typically last 2 to 4 months."

The same page attributes long hours to "varying points during a client-project cycle." That is the firm naming the driver without quantifying it. The end of a workstream is heavier than its middle, and no firm publishes the shape of that curve.

BCG supplies the location half. Its posting says consulting work is "much of it performed at our client sites," that "projects can vary in length, size, and location, depending on the client's challenge," and that "because our clients operate all over the world, you may travel internationally." There is no number of days per week in any of it.

You can see the difference in the published days themselves. The Chicago associate starts in a hotel lobby, so she is traveling. The London principal goes home to her husband, and the Santiago leader calls his family at 9pm. Same firm, same kind of role, three different travel realities in three published accounts. The pay side of these roles is set out in our consulting salary guide, and the management consultant hierarchy those rungs belong to in our McKinsey hierarchy page.

An intern's day, told by the intern

BCG publishes one account from the entry end of the ladder, checked 30 September 2026. Marit Enterman took a consulting internship at BCG after a master's in econometrics from the University of Amsterdam in March 2021, and converted it into an Associate offer.

Her day has a different rhythm from the three above. A 7am spin class. Client meetings at 8am or 8:30am on her public sector case, at 9am on her private equity case. A second coffee at 10am. A mentor meeting once or twice a month. Lunch with people from other teams. Case work through the afternoon. Then, she writes, "at around 4:00 PM every day I would connect with my case team buddy, who was a team member that I worked with directly."

Her learning goals are the most concrete thing in any of the four accounts, and they say what an entry-level day is made of: "these could be anything from learning how to prepare client meetings, to understanding tableau, or to mastering PowerPoint basics." She also records the late night plainly: "sometimes, depending on the demand of the case, we needed to work later into the night to get our work done."

What these four accounts cannot tell you

Four firm-published days is more evidence than the market usually cites, and it is still thin evidence. Three limits, all of them ours to declare.

They are old. The three McKinsey accounts are dated 2016, 2014 and 2017. The BCG internship ran during the pandemic. Nothing here is a 2026 observation, and a firm can change how it staffs a week in less time than that.

They are selected. A firm does not publish the day of an unhappy employee. These accounts are primary evidence of what four named people did, and they are unrepresentative by construction. We have no independent first-hand accounts to set against them. Our attempts on 30 September 2026 are logged in the knowledge base behind this page, and none of them produced anything citable.

They also stop short of five facts nobody publishes: the share of nights away from home, the distribution of hours rather than a rough middle, the shape of the workload curve inside a project, hours broken out by level, and any figure at all from a firm other than Bain. Where a firm holds that information and keeps it, the right move is to ask in the interview rather than to read an estimate online. Our consulting career path page covers what the next rungs change.

Practicing the part of the day that the interview tests

One block from these published days is the one you are assessed on. The problem solving session, the data request, the slide that has to carry a finding to someone who was not in the analysis: that is what a case interview samples.

Our drills run single exercises of that kind and score them on named dimensions, with the weights published in our method page. What they do not do is reproduce the day. They do not simulate travel, a staffing decision, a client who interrupts, or an evening block. They also do not teach business content. And 0 of 6 of our assessment simulators are live today, which our assessments page states itself.

If you want a fuller picture of the hours than this page can source, the fastest honest route is to ask two questions of the people who interview you. How many nights were you away last month, and what did the last two weeks of your last project look like. Both are answerable from memory, neither is confidential, and no published page will ever hold them.