> 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/site-management/scaffolds/handovers.md).

# Handovers

Review scaffold details, company handover questions and permissions before recording a handover certificate.

Review the correct scaffold, open its handover form and understand the fields before recording a handover.

A handover brings together scaffold details and your company’s handover checklist. Complete the handover for a Pending / Work In Progress scaffold to move it to Needs Signature. Once the handover is signed, the scaffold moves to Active.

## Before you begin

Create the site and scaffold first. Open the correct scaffold and review its reference, location, dimensions and deck details. If the underlying record is inaccurate, correct it through the scaffold editing workflow before preparing a handover.

The example uses a scaffold in Pending / Work In Progress. Check your site and scaffold references before starting.

## Desktop: open the handover form

### 1. Click Sites in the main navigation.

Find the required site in the list.

### 2. Click the required site code.

**Check:** the site code and name at the top of the page match the site you intended to open.

### 3. Click Scaffolds.

The site’s scaffold list opens.

### 4. Click Pending if its scaffold list is hidden.

Skip this click if the Pending list is already expanded. This example uses a pending scaffold.

### 5. Click the scaffold code.

Open the existing record. In this example, SCA26000001 appears under Pending with Work In Progress status.

<figure><img src="https://3532476255-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FsVJ0qURLvzCOxTGXEZIZ%2Fuploads%2F4NEATQRKRW3cOQrauZod%2Fclipboard.png?alt=media&amp;token=0659e01b-42a3-4005-9dd0-3764045765df" alt="Pending scaffold list with a red circle and arrow marking the SCA26000001 scaffold code to open its record."><figcaption></figcaption></figure>

**Check Overview:**

Check the site code, site name, scaffold code and tag number. Review the scaffold and deck dimensions. The sample values in these screenshots are examples, not values to copy into a real handover.

### 6. Click Handovers.

This tab lists handover records for the selected scaffold. An empty list shows “No data to display” and 0 total.

<figure><img src="https://3532476255-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FsVJ0qURLvzCOxTGXEZIZ%2Fuploads%2FROmOFb1KAZJVZEFq8ojj%2Fclipboard.png?alt=media&amp;token=3023e6e8-3959-4bb6-ba32-e79f7cb113e6" alt="Scaffold overview for SCA26000001 with a red circle and arrow identifying the Handovers tab."><figcaption></figcaption></figure>

### 7. Click the yellow + button.

The Add Handover form opens. It has three sections: Scaffold details, Safety checklist and Handover status. A displayed HAN reference alone does not establish that a handover has been saved.

<figure><img src="https://3532476255-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FsVJ0qURLvzCOxTGXEZIZ%2Fuploads%2Fbkm4XyYhi2aS0rMxqR7J%2Fclipboard.png?alt=media&amp;token=eaf3deee-4e53-4cf5-94bd-c73b35ac6f59" alt="Empty Handovers list showing 0 total and No data to display, with a red circle and arrow identifying the yellow plus button that opens Add Handover."><figcaption></figcaption></figure>

## Desktop: read the form

### Check Scaffold details

Check the scaffold and site references in the header. The form shows the tag, description, scaffold dimensions and deck details prefilled from the existing record. Tag No, Description, Location and scaffold Level were labelled Optional. Deck fields displayed length, width, level and quantity. Check the information against the actual scaffold.

Review every default before completing a real handover. “Section Safe for use” displayed Yes in the initial form, while the separate overall “Is the scaffold safe for use?” question was unanswered. A prefilled default is not a safety assessment.

<figure><img src="https://3532476255-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FsVJ0qURLvzCOxTGXEZIZ%2Fuploads%2FlY35siOBWWGmegZDoBjB%2Fclipboard.png?alt=media&amp;token=2d83fdf8-02f7-4027-9f75-cc8ab9883b7d" alt="Scaffold details with a red circle and arrow highlighting the initial Section Safe for use value, Yes, which must be reviewed rather than treated as a safety assessment."><figcaption></figcaption></figure>

### 8. Scroll to Safety checklist.

The example company template contains 31 questions in nine groups, with Yes and No choices. Your company’s configured questions may differ. Read each question literally: some ask whether hazards are present, including settlement or instability and nearby overhead obstructions or powerlines. Do not treat Yes as a blanket pass response.

For a real handover, record the actual findings through your company’s authorized safety process. Do not choose answers merely to enable submission.

### 9. Scroll to Handover status.

The form displayed six maximum-load categories, from Access only to Special / Extra Heavy Duty, an overall “Is the scaffold safe for use?” Yes/No question, optional Notes, and a document/photo/video upload area. The displayed load labels are UI choices, not engineering recommendations. Use the approved design and your company’s competent person to establish the correct load and outcome.

If Create Handover is disabled, check for incomplete required fields. Record the actual findings and approved load, rather than choosing answers merely to enable submission. Signing is a separate step after handover.

### 10. Return to the handover list when reviewing only.

If you only opened the form to review it and have not changed any fields, use the back arrow beside Add Handover. Opening and leaving the form does not create a completed handover.

<figure><img src="https://3532476255-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FsVJ0qURLvzCOxTGXEZIZ%2Fuploads%2F8d1s0XbV5xo6iMo2l9w5%2Fclipboard.png?alt=media&amp;token=0c6cca27-0d13-49d4-b129-1005dcea940f" alt="Add Handover header with a red arrow marking the back arrow used to return from the form."><figcaption></figcaption></figure>

## Template, permissions and follow-up

The Handover Certificate Template supplies your company’s questions and handover details. Review that configuration with the appropriate administrator. Scaffold dimensions and deck configuration should reflect the actual scaffold record.

Scaffolds → Handovers includes Create, View, Update and Approve permissions. A missing action can reflect role restrictions. Use the site and scaffold references when locating handover records in the Handover Log.

## Related guides

* [Overview](https://docs.cloudscaff.com/site-management/scaffolds/overview)
* [Handover Certificate Template: Build and Edit](https://docs.cloudscaff.com/settings/templates/handover-certificate-template-build-and-edit)
* [Handover Log](https://docs.cloudscaff.com/logs/handover-log)
* [Permissions Structure Overview](https://docs.cloudscaff.com/settings/user-management/permissions-structure-overview)

## Handover checks

A handover record brings together the scaffold details and your company’s handover checklist. Use it to record the handover information and approvals associated with the correct site and scaffold.

## Check the underlying record

1. Open the relevant site and scaffold.
2. Review the scaffold Overview, including its reference, location, dimensions and platform details.
3. Correct inaccurate scaffold details through the scaffold editing workflow before preparing the handover.

## Use the configured template

The Handover Certificate Template supplies the company’s questions and handover details. It also uses scaffold dimensions and board configuration from the scaffold record. Check the information presented and record the actual handover details using your company’s agreed process.

## Access and follow-up

Scaffolds → Handovers includes Create, View, Update and Approve permissions. A missing action can reflect role restrictions. The Handover Log provides access to issued handover records across sites; use the site and scaffold references when locating the certificate later.

## Related guides

* [Overview](https://docs.cloudscaff.com/site-management/scaffolds/overview)
* [Handover Certificate Template: Build and Edit](https://docs.cloudscaff.com/settings/templates/handover-certificate-template-build-and-edit)
* [Handover Log](https://docs.cloudscaff.com/logs/handover-log)
* [Permissions Structure Overview](https://docs.cloudscaff.com/settings/user-management/permissions-structure-overview)
