How, exactly, are you supposed to know the future?
That’s the question applicants should ask the minute they start panicking over “expected hours.” I’ve watched too many premeds treat this part of the application like it’s an IRS audit crossed with a prophecy exam. They stare at a volunteer entry and think, If I don’t predict the exact number of hours I’ll complete by next spring, admissions will assume I’m sloppy, dishonest, or unserious.
No. That’s not how this works.
Here’s the myth: your activities section is supposed to function like a perfectly closed ledger, with every hour known, verified, and fixed in stone. That sounds neat. It’s also nonsense for any role that’s still ongoing. If you’re still volunteering in a clinic, still working in a lab, still leading a campus group, then by definition some of those hours haven’t happened yet. You are estimating. Everyone knows you are estimating. Schools know this too.
What they want isn’t supernatural precision. They want honest reporting based on the best information you have when you submit. Reasonable dates. Reasonable weekly averages. Reasonable totals. That’s it.
Applicants get tripped up because they think “expected hours” is a trap. It’s not a trap. The real trap is overthinking it until you either inflate the numbers to look impressive or become so afraid of being wrong that you report something distorted and incomplete. I’ve seen both. Neither helps.
The right approach is less dramatic and much more credible: report what you’ve actually done, project what you’re likely to do, and keep the math anchored in reality. Not fantasy. Not vibes. Reality.
What “expected hours” actually means in the real world
Let’s kill the biggest misconception first: expected hours are not a promise carved in stone. They’re a projection for an activity that will continue after you submit your application.
That means there are really three buckets:
- Completed hours: what you’ve already done as of submission.
- Projected hours: what you reasonably expect to complete after submission.
- Total anticipated hours: completed plus projected.
Simple. But applicants love to turn simple things into weird things.
Admissions readers understand these categories are different. They do not expect future hours to carry the same certainty as completed hours. If you’ve done 120 hours of hospital volunteering and expect another 60 before the role ends, that doesn’t mean you’re claiming 180 happened already. It means you’re showing the full arc of a commitment that is still underway.
Where people get into trouble is trying to game the optics. They think bigger totals automatically look stronger, so suddenly a 2-hours-per-week role becomes a projected monster commitment with some absurd total that doesn’t even fit the calendar. I’ve seen applicants claim projected hours that would require them to volunteer through finals week, winter break, MCAT prep, and apparently sleep deprivation-induced time travel.
Bad move.
If your math looks unrealistic, the problem isn’t just that one activity. The problem is trust. Once a reviewer sees one padded estimate, they start wondering what else in the application has been polished past the truth. That’s avoidable. And unnecessary.
Expected hours should answer one practical question: Given your current pattern and known schedule, what will this activity likely amount to? Not what you hope. Not what sounds better. What’s likely.
How to calculate expected hours without making it weird
You do not need a spreadsheet worthy of NASA. Use the boring formula because boring is reliable:
average hours per week × remaining weeks = expected hours
Then round conservatively.
If you volunteer 3 hours a week and expect to continue for 20 more weeks, that’s 60 projected hours. Clean. Easy. Defensible.
Now the part applicants skip: adjust for real life.
Your future schedule is not a straight line. Classes change. Finals hit. Summer starts. The lab slows down. The clinic closes on holidays. You go home for winter break. If you know interruptions are coming, build them in. Don’t pretend every week between now and matriculation will look identical.
A better projection might look like this:
- 3 hours/week for 8 regular semester weeks = 24 hours
- 0 hours during 3 exam-heavy weeks = 0 hours
- 2 hours/week for 6 lighter summer weeks = 12 hours
Total projected hours: 36, not the fantasy number you’d get by multiplying 3 × 17 and calling it a day.
That’s what honest estimating looks like.
A few rules I give students all the time:
Use your actual average, not your best week.
If you volunteered 6 hours once but usually do 2, your average is not 6.Round down when you’re unsure.
Conservative estimates age well. Inflated ones don’t.Account for known end dates.
If the role ends in August, don’t project through the following spring just because it sounds nice.Don’t project hours for something that may never happen.
“I might continue shadowing if the physician emails me back” is not an activity plan. That’s wishful thinking.Add a brief note when needed.
Something like: “Ongoing through July; reduced summer schedule anticipated.” That’s enough.
You’re not trying to impress anyone with your forecasting genius. You’re showing that you can report an experience like an adult. That matters more than people realize.
What admissions readers care about more than exact numbers
Here’s what committees actually care about: credibility, pattern, and consistency.
Not whether you projected 140 hours instead of 152.
They’re asking questions like these:
- Does this activity fit the applicant’s timeline?
- Does the weekly commitment make sense alongside school, work, and other activities?
- Does the role show sustained involvement or meaningful responsibility?
- Does the description match the numbers?
That last one matters. A tiny, occasional role written up like a life-defining commitment looks off. So does a giant hour total attached to a description with no depth, no responsibility, and no reflection.
Another myth worth burying: more hours do not automatically make an activity stronger. A thoughtful 120-hour role with real patient contact, responsibility, and clear growth can be far more compelling than a padded 300-hour entry that reads like filler. Depth beats bloat. Every time.
And yes, inflated estimates can contaminate your whole application. If one entry feels obviously exaggerated, reviewers may start questioning the tone of the rest. That’s the hidden cost. Not just a bad number. A shaky narrative.
Common mistakes, edge cases, and how to document them cleanly
The classic mistakes are predictable because applicants keep making the same ones.
First: double-counting overlapping hours. If you were doing research in a clinical setting, don’t count the same block of time as both research and clinical volunteering unless those were genuinely separate responsibilities with separate time. One hour is one hour. This isn’t application cryptocurrency.
Second: forgetting end dates. A tutoring role that ends at graduation is not ongoing forever. Neither is that club leadership job that dies the second you hand over the Google Drive.
Third: adding speculative hours. Shadowing you haven’t scheduled yet. A volunteer role waiting for orientation. A summer plan that depends on acceptance into a program you haven’t gotten into. Don’t report dreams as commitments.
Changing schedules are common, and they’re not a problem if you explain them briefly. Examples:
- “Activity paused during exam period; resumes in June.”
- “Seasonal volunteer role limited to school breaks.”
- “Ongoing at reduced frequency due to summer relocation.”
- “Commitment ends in August at conclusion of research fellowship.”
That’s clean. Short. Useful.
Paused activities deserve honesty too. If you stopped for three months, don’t smooth that over. If a role depends on school breaks, say so. If continuation is uncertain, either report completed hours only or use a very restrained projection. Restraint reads as mature. Padding reads as amateur.
A practical reporting checklist applicants can actually use
If you want a system, use this one:
- Step 1: Enter the real start date.
- Step 2: Determine whether the activity is truly ongoing after submission.
- Step 3: Count completed hours up to the submission date.
- Step 4: Estimate your average weekly commitment based on normal participation, not peak weeks.
- Step 5: Count the remaining weeks the activity will likely continue.
- Step 6: Subtract breaks, finals, travel, and known pauses.
- Step 7: Multiply and round conservatively.
- Step 8: Add a short clarifying note if the schedule changes or the role has a fixed end date.
- Step 9: Sanity-check the final number against your actual life.
That last step matters. A lot.
If your projected total looks wildly out of proportion to your known availability, revise it. If you’re taking 18 credits, working part-time, studying for the MCAT, and claiming another 15 hours a week of future volunteering, the math probably isn’t bold. It’s bad.
The safest strategy is accuracy with context, not perfection with guesswork. You are not being graded on clairvoyance. You’re being judged on whether your application feels believable.
And believable wins more often than applicants think.
FAQ
1. Should I include expected hours for an activity I’m still doing?
Yes. If the activity will continue after you submit, include a conservative projection. Report what you’ve already completed, then estimate what’s likely to happen next. That’s honest. Pretending future hours don’t exist can understate a meaningful commitment, but pretending they already happened is just sloppy.
2. What if I’m not sure I’ll keep doing the activity?
Then don’t invent a future. Report completed hours only, or use a very cautious estimate and clarify the uncertainty. I’d much rather see a restrained application than one stuffed with fictional ambition. Admissions readers can smell made-up commitment from across the room.
3. Can I round up my expected hours to make the activity look stronger?
You can round. You should not inflate. Round conservatively and keep it defensible. A slightly lower number that fits your timeline is far stronger than a puffed-up total that makes the whole application look shady. Accuracy with context wins. Every time.
