> For the complete documentation index, see [llms.txt](https://docs.labii.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.labii.com/widgets/section-widgets/productivity/other/timer.md).
# Timer
## Specs
| Label | Value |
| ------------------------- | ----------------------------- |
| **Version** | 1.1.0 (updated on 2022-09-23) |
| **Developer** | Labii Inc. |
| **Type** | Section |
| **Support Configuration** | No |
## Overview
The Timer widget provides a lightweight countdown tool directly inside a Labii record so users can track short waiting periods without leaving the documentation context. It is designed for laboratory workflows that include incubation, settling, reaction, wash, or observation intervals where a simple visible timer is more practical than creating a full workflow step structure. By keeping the timer in the same record as the surrounding protocol or experiment notes, Labii helps users stay focused on the task while reducing the risk of missed timing checkpoints.
## Use Cases
* **Incubation tracking**: Count down defined waiting periods during sample incubation, hybridization, or reagent reactions.
* **Wash and rinse cycles**: Monitor repeated short intervals in plate washing, cleaning, or preparation workflows.
* **Observation timing**: Track how long a sample, culture, or reaction should be observed before the next action.
* **Bench-side protocol support**: Keep a visible timer next to written procedures so users do not need a separate phone or desktop app.
* **Training workflows**: Help new staff follow standardized wait times accurately during protocol execution.
## Interface
### Read-only View
In read-only view, the widget displays the configured countdown duration and the control buttons used to manage the timer. Users can quickly confirm the current target duration and see whether the timer is running, paused, or reset.
* **Time Display**: Shows the countdown using hours, minutes, and seconds.
* **Status Visibility**: Makes the remaining time easy to monitor during active work.
* **Inline Access**: Keeps the timing tool embedded in the same record as the related procedure or experiment documentation.
The read-only view displays the countdown timer and its current remaining time inside the record
### Edit View
In edit view, users can set or adjust the countdown duration by entering the required hours, minutes, and seconds. The widget is designed for fast setup rather than complex configuration, so the edit surface focuses on direct time entry and immediate timer control.
* **Input Methods**: Enter the countdown duration using hour, minute, and second fields.
* **Control Actions**: Start, pause, and reset the timer from the widget controls.
* **Fast Adjustment**: Update the duration quickly when protocol timing changes mid-run.
* **Low Complexity**: No advanced formatting or configuration is required.
## Configuration
The Timer widget requires no configuration. Once added to a record, it is ready to use immediately.
### Initial Setup
{% stepper %}
{% step %}
Open the target record and click **Add Section**.
{% endstep %}
{% step %}
Select **Timer** from the section widget library.
{% endstep %}
{% step %}
Save the section. The timer appears in the record and can be used immediately.
{% endstep %}
{% endstepper %}
### Required Settings
The Timer widget has no required settings.
### Optional Settings
The Timer widget has no optional settings.
{% hint style="info" %}
The timer defaults to `00:10:30`, which is useful as a quick starting point for common short laboratory wait periods.
{% endhint %}
## Additional Functions
### Set the Countdown Duration
{% stepper %}
{% step %}
Open the Timer widget in the record.
{% endstep %}
{% step %}
Enter the desired **Hours**, **Minutes**, and **Seconds** for the countdown.
{% endstep %}
{% step %}
Review the displayed time and confirm it matches the required wait period.
{% endstep %}
{% endstepper %}
### Start the Timer
Click **Start** to begin the countdown. The remaining time updates continuously until the timer reaches zero or is paused.
### Pause the Timer
Click **Pause** to temporarily stop the countdown without losing the remaining time. This is useful when a procedure is interrupted or when the next step depends on a manual check before continuing.
### Reset the Timer
Click **Reset** at any time to restore the timer to the configured starting duration.
### Completion Alert
When the countdown reaches zero, the widget plays a sound to alert the user that the timed interval has finished.
## Best Practices
### Data Organization
* Place the Timer widget next to the section that describes the timed step so the wait period stays clearly connected to the procedure.
* Use descriptive section titles such as "Incubation Timer" or "Wash Cycle Timer" when a record contains more than one timer.
* Keep one timer focused on one wait period instead of reusing a single section for unrelated timing tasks.
### Performance Optimization
* Use the Timer widget for simple countdown needs instead of building a larger workflow section when only timing is required.
* Reset the timer between repeated runs so the displayed duration always matches the current procedure step.
* For complex protocols with many timed stages, use a workflow-oriented widget instead of managing all timing manually in one Timer section.
### Security and Compliance
* Use the Timer widget as an execution aid, not as the sole compliance record for regulated timing events.
* Pair timed work with appropriate documentation sections so the reason for the timing interval is captured in the record.
* For workflows that require explicit completion tracking, use a process-oriented widget that records user actions and timestamps.
{% hint style="success" %}
The Timer widget works best for lightweight, repeatable waiting periods where speed and visibility matter more than formal workflow control.
{% endhint %}
### Common Pitfalls to Avoid
* **Avoid** relying on memory alone after starting the timer; keep the record open so the countdown and alert remain visible.
* **Avoid** using ambiguous section names such as "Timer" multiple times in the same record when different wait periods are being tracked.
* **Instead** create separate timer sections for each distinct timed step when a protocol includes several different intervals.
### Maintenance and Troubleshooting
* Review the configured duration before each run to make sure it matches the current protocol requirement.
* If the timer is not useful for a multi-stage workflow, replace it with a more structured widget that tracks timed steps individually.
* If users repeatedly miss timer alerts, place the widget higher in the record or keep the related record section open during execution.
### Workflow Integration Tips
* Combine the Timer widget with a text-based documentation section so the timed action and its instructions stay together.
* Use it alongside a [Steps](/widgets/section-widgets/process-management/steps.md) widget when a protocol contains both simple standalone wait periods and more formal tracked procedure steps.
* Pair it with a [Files](/widgets/section-widgets/office/file/files.md) section when the timed task depends on attached SOPs, worksheets, or instrument instructions.
## Related Widgets
* [**Steps**](/widgets/section-widgets/process-management/steps.md): Use Steps when the timed interval is part of a larger procedural sequence that also needs completion tracking, verification, or action buttons.
---
# 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:
```
GET https://docs.labii.com/widgets/section-widgets/productivity/other/timer.md?ask=
```
The question should be specific, self-contained, and written in natural language.
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.