> 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/instructions-log.md).

# Instructions Log

## Purpose

The Instructions Log provides a permanent record of every instruction created and issued across your company’s sites.

It ensures all site actions are traceable, time-stamped, and linked to the responsible user.

You can use it to:

* Track work orders or requests from supervisors and clients
* Record written instructions tied to a specific scaffold or site
* View who issued the instruction and when it was completed
* Provide proof of instruction handover for accountability and safety

***

## **How the Instructions Log Works**

The Instructions Log records general instructions issued across all sites. These instructions may relate to work requests, access notes, safety communication, or client requests.

The system follows this workflow:

* **Instruction is created**
  * When a user issues an instruction on a site, it is automatically added to the **Instructions Log**.
  * Each record shows who issued the instruction, the date, and which site it applies to.
* **Instruction is viewed and actioned**
  * Supervisors and site teams can view the full instruction record, including notes and uploaded documents.
  * Once the instruction is actioned or completed, status can be recorded for traceability.
* **Permanent audit record**
  * Instructions remain in the log for historical reference.
  * The full log can be exported for operational, safety, or client reporting.

This ensures all site instructions are documented, traceable, and linked to a responsible user, improving communication and compliance on every job site.

***

## How to Access

In the side navigation, scroll to **Instructions → Instructions Log**.

This opens the full list of issued site instructions.

<div align="left" data-with-frame="true"><figure><img src="/files/SubfTiY9xBBKK2bVw40o" alt="" width="360"><figcaption></figcaption></figure></div>

***

## Table Layout

<div align="left" data-with-frame="true"><figure><img src="/files/oNFACLvognmmwuyHkitW" alt=""><figcaption></figcaption></figure></div>

Each row in the table represents a site instruction and includes the following fields:

| Column     | Description                                                               |
| ---------- | ------------------------------------------------------------------------- |
| Code       | Unique auto-generated instruction reference number                        |
| Site Name  | The site that the instruction belongs to                                  |
| Customer   | Customer name linked to the site                                          |
| Date       | Date the instruction was created                                          |
| Created By | User who issued the instruction                                           |
| Status     | Status label showing whether the instruction is completed or still active |

***

### Status Types

| Status       | Meaning                                              |
| ------------ | ---------------------------------------------------- |
| Completed    | Instruction has been issued and finished             |
| Pending/Open | Instruction has been logged but is not yet completed |

Status labels are color-coded for visibility.

<div align="left" data-with-frame="true"><figure><img src="/files/Nl4Y2u18uS7yfh3IrEyL" alt="" width="183"><figcaption></figcaption></figure></div>

***

### Available Actions

Inside each instruction record, you can:

* View the full instruction details
* Read notes or attached information
* See who created the instruction and when

{% hint style="info" %}
[Learn how to issue a site instruction](/site-management/site-instructions.md)
{% endhint %}

***

### Search, Filters and Pagination

The Instructions Log uses standard Cloudscaff table controls.

Search

* Type at least three characters to filter results
* Use the clear (×) icon to reset the search

Pagination

* Use the pagination controls at the bottom of the table to move between pages

Rows Per Page

* Select how many instructions appear at once (for example 7, 10, 15)

{% hint style="info" %}
[Learn about the Search Bar (Data Tables)](/general-tools-and-features/search-and-filter-bar.md)
{% endhint %}

{% hint style="info" %}
[Learn about Table Pagination and Rows Per Page Selector](/general-tools-and-features/table-pagination-and-rows-per-page-selector.md)
{% endhint %}

***

## Best Practices

* Use clear, descriptive notes to simplify tracking and auditing
* Close instructions when completed to maintain accurate site records
* Export monthly for internal review or client reporting
* Ensure users issuing instructions have the correct Role Permissions


---

# 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/instructions-log.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.
