> For the complete documentation index, see [llms.txt](https://docs.cloudscaff.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.cloudscaff.com/logs/handover-log.md).
# Handover Log
## Purpose
The Handovers Log stores every handover certificate created in the system.
Each entry is automatically assigned to a site, scaffold and a customer, and includes attached signatures and certificate details.
**Use this log to:**
* View signed and unsigned handover certificates
* Confirm the handover certificate dates and the responsible person
* Access and download Handover Certificates
* Track client approvals
***
## **How the Handover Log Works**
The Handover Log stores all handover certificates issued across every site. A scaffold will appear in this log the moment a handover is created.
The system follows this workflow:
* **Handover is created**
* When a scaffold is erected and a handover is issued, the handover is immediately recorded in the **Handover Log**.
* Each handover includes customer details, handover dates, signatures, and uploaded documents or photos.
* **Signatures and completion**
* Once all required signatures are completed, the handover record is marked as signed.
* The handover certificate can be downloaded at any time for client or audit use.
* **Linked to scaffold activity**
* The scaffold that was handed over will appear in the **Scaffold Log** as an active scaffold.
* All certificates remain permanently stored in the Handover Log, even after the scaffold is dismantled.
This ensures every scaffold has a traceable, legally recorded handover, stored permanently for compliance and reporting purposes.
***
## How to Access
In the side navigation, go to:\
**Instructions → Handover Log**
***
## Table Layout
Each row includes:
| Column | Description |
| ---------- | ------------------------------------------------------------- |
| Code | Unique handover certificate number (auto-generated) |
| Customer | The customer receiving the scaffold |
| Site | Site the handover was created for |
| Start Date | The erection date or the date the scaffold was made available |
| End Date | Expected dismantle date or certificate end date |
| Created | Date the handover was generated |
| Notes | Any notes added at the time of creation |
| Created By | User responsible for issuing the handover |
| Uploads | Number of photos or documents uploaded to the record |
| Status | Indicates if the handover is signed or still pending |
***
## Status Types
| Status | Meaning |
| -------------------- | -------------------------------------------------------------------- |
| Signed | All required signatures are complete and the scaffold is handed over |
| Pending (if visible) | Waiting for one or more signatures |
***
### Available Actions
Inside each handover, you can:
* View the full handover record
* Review signatures
* View notes and attachments
* Download the Handover Certificate
{% hint style="info" %}
[Learn how to build a handover certificate](/settings/templates/handover-certificate-template-build-and-edit.md)
{% endhint %}
{% hint style="info" %}
[Learn how to use a handover certificate](/site-management/scaffolds/handovers.md)
{% endhint %}
***
#### Search, Filters and Pagination
Search
* Type at least three characters to filter by code, site or status
* Use the clear (×) icon to reset
Pagination
* Pagination buttons appear at the bottom of the page
Rows Per Page
* Adjust the number of rows displayed at once
{% hint style="info" %}
[Learn how the Search Bar (Data Tables)](/general-tools-and-features/search-and-filter-bar.md)
{% endhint %}
{% hint style="info" %}
[Learn how Table Pagination and Rows Per Page Selector](/general-tools-and-features/table-pagination-and-rows-per-page-selector.md)
{% endhint %}
***
## Best Practices
* Make sure customer names and site names are accurate before issuing a certificate
* Add clear notes for safety, access or special conditions
* Export reports monthly for compliance and billing
* Ensure all signatories have completed the digital signature process
---
# 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://docs.cloudscaff.com/logs/handover-log.md?ask=&goal=
```
`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.