> For the complete documentation index, see [llms.txt](https://help.matrack.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.matrack.io/eld/readme/categories/matrack-eld-driver-app-guides/complete-guide-to-recap-hours.md).

# Complete Guide to Recap Hours

### What Are Recap Hours? Recap hours consist of:

* Hours worked on the first day of the cycle
* Remaining hours in the cycle These become available after the last day of the cycle

## Key Rules

#### Usage Requirements

* It cannot be used when clocks are at zero
  * In this case, it must take a 34-hour restart
* Includes both Driving and Duty hours
* Can continue driving without 34-hour restart
* Applicable to both 70-hour/8-day and 60-hour/7-day cycles

#### Reset Options

* 34-hour restart before the 9th day provides a full 70 hours
* Without restart, receive the first day's hours plus the remaining cycle hours

### 70-Hour/8-Day Cycle Example

| Day | Available Hours | Hours Worked                               | Hours Remaining                                                               |
| --- | --------------- | ------------------------------------------ | ----------------------------------------------------------------------------- |
| 1st | 70 hours        | <mark style="color:orange;">7 hours</mark> | 63 hours                                                                      |
| 2nd | 63 hours        | 3 hours                                    | 60 hours                                                                      |
| 3rd | 60 hours        | 11 hours                                   | 49 hours                                                                      |
| 4th | 49 hours        | 9 hours                                    | 40 hours                                                                      |
| 5th | 40 hours        | 7 hours                                    | 33 hours                                                                      |
| 6th | 33 hours        | 8 hours                                    | 25 hours                                                                      |
| 7th | 25 hours        | 11 hours                                   | 14 hours                                                                      |
| 8th | 14 hours        | 11 hours                                   | <mark style="color:orange;">3</mark> <mark style="color:orange;">hours</mark> |

#### 9th Day Calculation

* Hours worked on the first day: 7 hours
* Hours remaining in cycle: 3 hours
* Total available for 9th day: 10 hours (7 + 3)

{% hint style="warning" %}

### <mark style="color:red;background-color:yellow;">Important Notes</mark>

* <mark style="background-color:yellow;">Monitor daily hours carefully</mark>
* <mark style="background-color:yellow;">Track remaining cycle hours</mark>
* <mark style="background-color:yellow;">Plan routes based on available recap hours</mark>
* <mark style="background-color:yellow;">Consider a 34-hour restart when beneficial</mark>
* <mark style="background-color:yellow;">Maintain accurate duty status records</mark>
  {% endhint %}

Need assistance calculating your recap hours? Contact Matrack support for help.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://help.matrack.io/eld/readme/categories/matrack-eld-driver-app-guides/complete-guide-to-recap-hours.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.