Convert elapsed hours into decimal weeks or a clearer combination of complete weeks, days, hours and minutes. The calculator is especially useful for incident-response and recovery timelines, where urgent action may begin within hours but rebuilding disrupted services can continue for weeks.
The British Library cyberattack provides a real example of this contrast. Its crisis response was activated less than two hours after the major incident was identified, while restricted services and infrastructure recovery continued for much longer. You can also browse all time converters when a timeline uses minutes, days or other units.
Hours to Respond, Weeks to Recover: The British Library Cyberattack
On 28 October 2023, the British Library discovered that a major ransomware attack had compromised most of its online systems. According to the Library's incident review, the technology team identified the event as a major incident at 07:35. Its crisis-management plan was invoked at 09:15—a difference of 1 hour and 40 minutes.
Senior leaders were informed by 09:21, specialist cybersecurity advisers were engaged and the UK's National Cyber Security Centre became involved in the response. This rapid escalation allowed the organisation to begin assessing the damage, coordinating its response and protecting the services and information that remained available.
Activating a response plan did not mean the incident was fully contained or the Library had recovered. The attackers had copied approximately 600 GB of files, encrypted data and damaged parts of the server infrastructure. Although the buildings remained open, many research and online services were severely restricted.
From 1 Hour 40 Minutes to More Than 11 Weeks
A searchable version of the Library's main catalogue returned on 15 January 2024. That was approximately 79 days after 28 October, equivalent to 11 weeks and 2 days. Other systems and services required a much longer rebuilding programme, and in December 2023 the Library moved from crisis response to a formal recovery programme that it called Rebuild & Renew.
These figures should not be interpreted as a direct comparison between “containment time” and “complete recovery time.” The 1-hour-40-minute figure records how quickly the formal crisis response was activated. The 11-week figure marks one important service milestone, not the end of the overall recovery.
Why Cyberattack Response Takes Hours but Recovery Can Take Weeks
During the first hours of a serious incident, responders concentrate on urgent decisions. They may isolate systems, disable compromised accounts, preserve logs and other evidence, protect unaffected services and bring in external specialists. These actions can reduce further harm, but they do not prove that every route used by an attacker has been removed.
Investigation and recovery are slower because each affected system must be understood and handled safely. Teams may need to determine how access was gained, identify the data and accounts involved, rebuild computers, restore information from verified backups, reset credentials and test each service before reconnecting it.
Business recovery also extends beyond technical restoration. Staff may have to process delayed work, reconcile records created through temporary manual procedures, notify affected people and satisfy legal or regulatory duties. This is why an event that triggers action within hours can still affect normal operations many weeks later.
How to Convert Hours to Weeks
One standard elapsed week contains seven days, and each day contains 24 hours:
1 week = 7 × 24 = 168 hours
To convert hours to weeks, divide the number of hours by 168:
Weeks = hours ÷ 168
For example, the 1 hour and 40 minutes between identification of the British Library incident and activation of its crisis plan equals about 1.6667 hours:
1.6667 ÷ 168 ≈ 0.0099 weeks
The 79-day period leading to the return of the searchable catalogue contains 1,896 elapsed hours:
79 × 24 = 1,896 hours
1,896 ÷ 168 ≈ 11.2857 weeks
A decimal result is helpful for calculations, but a result such as 11 weeks and 2 days is usually easier to read. Enter the total below and the hours to weeks calculator will show both formats. To reverse the calculation, use the weeks to hours converter.
Elapsed Hours to Weeks, Days, Hours and Minutes Calculator
Enter an elapsed duration in hours. The tool displays decimal weeks for calculation and separates the same duration into complete weeks, days, hours and minutes for schedules and reports.
Converted duration
This calculator uses continuous elapsed time, where 1 week = 168 hours and 1 day = 24 hours. It does not treat a week as a 35-hour, 37.5-hour or 40-hour working week.
Hours-to-Weeks Response and Recovery Table
The table compares shorter response periods with longer recovery milestones. The context descriptions are illustrative unless they refer specifically to the British Library timeline.
| Elapsed hours | Decimal weeks | Weeks, days and hours | Timeline context |
|---|---|---|---|
| 1.6667 hours | 0.0099 weeks | 1 hour 40 minutes | British Library: identification to crisis-plan activation |
| 8 hours | 0.0476 weeks | 8 hours | One response-team shift |
| 24 hours | 0.1429 weeks | 1 day | The first full day after discovery |
| 72 hours | 0.4286 weeks | 3 days | Initial investigation and mitigation period |
| 168 hours | 1 week | 1 week | One complete week of elapsed time |
| 336 hours | 2 weeks | 2 weeks | A two-week restoration period |
| 672 hours | 4 weeks | 4 weeks | Extended rebuilding and service testing |
| 1,680 hours | 10 weeks | 10 weeks | A longer operational recovery programme |
| 1,896 hours | 11.2857 weeks | 11 weeks 2 days | British Library: attack discovery to searchable catalogue |
These values describe calendar time, not the number of staff-hours spent on recovery. Multiple teams may work simultaneously or in shifts, while some tasks may pause for testing, approval or coordination with outside organisations.
Sources and Further Guidance
The dates, response times and operational effects in the real example come from the British Library Cyber Incident Review .
For general incident-management information, see the UK National Cyber Security Centre's incident-response guidance and the NIST Guide for Cybersecurity Event Recovery .
Figures on this page are checked against the sources above. Spotted an error? Contact us.