Language
English English Vietnamese (Tiếng Việt) Vietnamese (Tiếng Việt) Chinese (简体中文) Chinese (简体中文) Portuguese (Brazil) (Português do Brasil) Portuguese (Brazil) (Português do Brasil) Spanish (Español) Spanish (Español) Indonesian (Bahasa Indonesia) Indonesian (Bahasa Indonesia)
Hours to Weeks

Hours to Weeks

Puts a module's notional learning hours on the same scale as the teaching calendar, so an ECTS or credit-hour workload becomes an honest weekly study figure.

The Handbook Says 150 Hours, the Timetable Says 12 Weeks

Every module descriptor carries a workload figure — 125 hours, 150 hours, 675 hours for a full semester — and almost nobody knows what to do with it. The number is a promise about how much of a student's life the credit is meant to cost, but it is quoted as a lump sum while the course is actually delivered in weeks. Turning that lump sum into a weekly figure is the one calculation that decides whether a syllabus is honest, and it starts by putting the hours on the same scale as the calendar.

Conversion factor: 1 wk = 168 h, so divide hours by 168. A 150-hour module is 0.893 weeks of continuous elapsed time — which is exactly why nobody plans a course that way. Spread across a 12-week teaching term the same 150 hours is 12.5 hours a week, and that is the number a student can argue with.

What a Credit Is Actually Promising

ECTS counts the whole workload

Sixty credits describe one full academic year, and each credit is defined as roughly 25 to 30 hours of student effort. A year therefore lands somewhere between 1 500 and 1 800 notional hours, lectures and private reading included.

US credit hours count the classroom, then assume the rest

One semester credit is about 15 contact hours across a 15-week term, with the long-standing expectation of two hours of outside work per contact hour. The study time is real but implicit, which is why the two systems look so different on paper.

The week on this page is 168 hours long

It is a block of elapsed calendar time, not a working week. Reading a module as 0.89 weeks tells you the workload would fill nine-tenths of an unbroken week if a person never slept — useful as a scale check, not as a schedule.

Term length changes everything

The same 150 hours is 10 hours a week over 15 teaching weeks and 15 hours a week if the module is compressed into 10. Two universities can award identical credit for very different weekly demands.

From a Credit Total to a Week-by-Week Study Plan

The workflow below is the one a programme leader runs when validating a module, and the one a student runs in week one when the reading list arrives and looks impossible.

1

Enter the notional hours from the descriptor

Type 125, 150 or 675 into the left field and the week equivalent appears as you type. A comma is accepted in place of a decimal point and spaces are ignored, so a figure pasted out of a validation document needs no tidying.

2

Use the week figure as a sanity check on the term

A full 30-credit ECTS semester comes to about 4.46 weeks of solid clock time. Against a 15-week term that is under a third of the available calendar, which is roughly what a sustainable 50-hour study week looks like. When the fraction climbs past a half, the workload statement is fiction.

3

Swap the direction to size the term itself

Press the swap button (↔) for wk → h when you have the term length instead: 12 teaching weeks is 2 016 calendar hours, the pot that the whole cohort's timetable has to fit inside.

4

Copy the bare figure into the workload sheet

The copy control on each field hands over digits alone, with no unit and no separators, ready for the spreadsheet column that totals a programme's credits. Ctrl + C inside a field does the same.

Divide by teaching weeks, not by the answer: the converter returns elapsed weeks of 168 hours each. Weekly effort comes from dividing the hours by the number of weeks the module is taught over — 150 h across 12 weeks is 12.5 h per week, not 0.893.

Credit Systems and the Hours They Stand For

Common course loads under both systems, shown as the notional hours the descriptor claims, the elapsed weeks that represents at 168 hours each, and the weekly effort once the hours are spread over a realistic teaching period.

Course load Notional hours Weeks at 168 h Teaching weeks assumed Hours per teaching week
5 ECTS module at 25 h per credit125 h0.744 wk158.3 h
5 ECTS module at 30 h per credit150 h0.893 wk1510 h
US 3-credit course, 45 contact + 90 study135 h0.804 wk159 h
10 ECTS dissertation module at 30 h300 h1.786 wk1225 h
US 15-credit full-time semester675 h4.018 wk1545 h
30 ECTS semester at 25 h per credit750 h4.464 wk1550 h
60 ECTS academic year at 25 h per credit1 500 h8.929 wk4037.5 h

Read down the last column and the two systems converge on the same reality: a full-time student is being asked for something between 37 and 50 hours a week, which is a job. The gap between 675 and 750 hours for what is nominally the same semester is the whole reason credit transfer needs a conversation rather than a lookup table — the ratio people reach for, two ECTS to one US semester credit, is a rounding of that difference and not an identity.

How the Two Fields Get Used at Validation

A workload figure answers back immediately

Both fields are live, so a validation panel can try 125, 150 and 200 hours in sequence and watch the scale move without anyone reaching for a calculator.

Term lengths run the other way

Swapping the pair turns a 12-, 15- or 40-week structure into the calendar hours it contains, which is the denominator every workload argument eventually needs.

Days and months share the dropdown

Both unit lists are searchable across every time unit here, so a placement counted in months or a lab block counted in days can be compared with a taught module on one screen.

Fractions of a week keep their detail

Results carry up to eight decimals, so a 20-hour micro-credential still reads as 0.11904762 weeks instead of collapsing to a flat 0.12.

Questions From the Course Handbook

How many hours does one ECTS credit stand for?

Between 25 and 30, and which end of that range applies is a national decision rather than a European one. The fixed point is the year: 60 credits describes a full-time academic year, so a country using 25 hours per credit is describing a 1 500-hour year and one using 30 is describing 1 800. That 300-hour spread is why the same 5-credit module can be published as 125 hours in one country and 150 in another without either being wrong.

Why is a 3-credit course counted as 135 hours when I only sit in class for 45?

Because the credit was never a measure of attendance alone. The traditional expectation attached to a US semester credit is one hour of instruction plus two hours of independent work each week, so three credits over a 15-week term is 45 contact hours carrying 90 hours of reading, problem sets and assessment behind them. The 135-hour total is what a European descriptor would print openly as notional learning hours; the US version simply leaves the larger part unstated on the transcript.

Does 0.89 weeks mean I could finish the module in under a week?

Only if you never slept, and the number is not trying to suggest otherwise. A week here is 168 hours of clock time, so 0.89 weeks means the workload would occupy 89 % of every hour in a week end to end. Its real value is as a ratio: it says the module claims nine-tenths of a full week of human existence, which against a 12-week term is a manageable slice and against a two-week intensive block is a warning.

My module lists 150 notional hours — how should I spread them?

Divide by the weeks the module actually runs, then subtract the fixed timetable before planning anything else. Over 12 teaching weeks 150 hours is 12.5 a week; if 3 of those are lectures and seminars, 9.5 hours of private study remain. The trap is assessment: a module with a 3 000-word essay and an exam will consume 30 to 40 of its 150 hours in the final fortnight, so a flat 12.5 every week overstates the early load and badly understates the end.

How do I line up an ECTS transcript with US credit hours?

The working rule is two ECTS to one US semester credit, which makes a 30-credit European semester read as roughly 15 US credits and a 60-credit year as 30. Check the hours before trusting it: 30 ECTS at 25 hours is 750 hours against the 675 a 15-credit US semester implies, so the mapping is around 11 % generous to the incoming student. Admissions offices vary the ratio for exactly this reason, and institutions on quarter hours add a further 1.5 factor on top, so treat any single number as an opening position rather than a rule.

h
wk

Course Workload Across a Term

125 h=0.744 wk
135 h=0.804 wk
150 h=0.893 wk
300 h=1.786 wk
675 h=4.018 wk
1 500 h=8.929 wk

Hour (h)

The unit a credit is defined in. One ECTS credit is 25 to 30 notional learning hours and one US semester credit implies about 45, counting contact time and the private study assumed behind it.

Week (wk)

168 hours of elapsed calendar time, not a working week. Terms are counted in weeks, so this is the scale a workload total has to be divided by before it means anything to a student.

Enter the descriptor's notional hours — 125, 150 or 675 — and read the week equivalent as you type
The week here is 168 clock hours, so treat it as a scale check and divide by teaching weeks for weekly effort
Swap (↔) gives wk → h when you have the term length: 12 weeks is 2 016 hours
Up to eight decimals are kept, so a 20-hour micro-credential still reads as 0.11904762 wk
Want to learn more? Read documentation →
1/5

Time Converter

Centuries to Millenniums Centuries to Years Days to Hours Days to Minutes Days to Months Days to Seconds Days to Weeks Days to Years Decades to Centuries Decades to Years Hours to Days Hours to Minutes Hours to Months Hours to Seconds Hours to Weeks (current page) Hours to Years Microseconds to Milliseconds Microseconds to Nanoseconds Microseconds to Seconds Millennia to Years Millenniums to Centuries Milliseconds to Microseconds Milliseconds to Minutes Milliseconds to Seconds Minutes to Days Minutes to Hours Minutes to Milliseconds Minutes to Seconds Minutes to Years Months to Days Months to Hours Months to Weeks Months to Years Nanoseconds to Microseconds Nanoseconds to Seconds Seconds to Days Seconds to Hours Seconds to Microseconds Seconds to Milliseconds Seconds to Minutes Seconds to Nanoseconds Seconds to Years Weeks to Days Weeks to Hours Weeks to Months Weeks to Years Years to Centuries Years to Days Years to Decades Years to Hours Years to Minutes Years to Months Years to Seconds Years to Weeks
Start typing to search...
Searching...
No results found
Try searching with different keywords