Work Requests
1. Overview
Work Requests in tamato allow users to report maintenance issues, service needs, or improvement requests in a structured and traceable way. They act as the entry point for all unplanned maintenance activities.
By using Work Requests, teams ensure that problems are documented clearly, prioritized correctly, and processed consistently before any work begins.
2. When to Use This Feature
Use a Work Request whenever a maintenance need is identified but no work order exists yet.
Typical use cases include:
Reporting a broken or malfunctioning asset
Requesting preventive or corrective maintenance
Notifying maintenance about safety or compliance issues
Submitting facility-related service requests
Work Requests are commonly created by:
Operators or employees
Technicians
Maintenance managers
External requesters (if enabled)
3. Step-by-Step Instructions
To create a new Work Request in tamato:
Navigate to Work Requests in the main navigation
Click "+ Work Request"
Fill in the required fields:
Title (required)
Upload a picture or attachment (optional)
Description (optional)
Assign to a specific user or team (optional)
Priority (required)
Location (required)
Click "Create"
Once submitted, the Work Request is saved and visible to authorized users.
4. Field Explanations
Title (required)
A short summary describing the issue or request.
Best practice: Clearly state the problem (e.g. “Hydraulic pump leaking oil”).
Upload a picture or attachment (optional)
Photos or documents related to the request.
Best practice: Attach images to speed up diagnosis and reduce clarification questions.
Description (optional)
A detailed explanation of the issue, including symptoms and context.
Best practice: Include when the issue started, how often it occurs, and any impact on operations.
Assign to a specific user or team (optional)
User or teams related to the work request.
Best practice: If it is clear who or which team will take care of the work request, assign it directly and speed up diagnosis
Priority (required)
Indicates how urgent the request is.
Best practice: Base priority on operational risk and downtime impact, not convenience.
Location (required)
Specifies where the issue is occurring or which asset is affected.
Best practice: Always select the most specific location available.
5. What Happens After Submission
After submission:
The Work Request is created with the status "Not Started"
Authorized users (e.g. maintenance managers) can review the request
Notifications may be sent based on system settings
The request can be approved (automatically converts the Work Request to a Work Order), rejected, or updated
6. Common Mistakes & Tips
Avoid vague titles such as “Issue” or “Broken”
Do not set every request to high priority
Use attachments and pictures to improve clarity
Always assign a specific location when possible
Review open requests regularly to avoid backlog accumulation
7. Short Summary
Work Requests are the starting point for unplanned maintenance in tamato. They ensure issues are captured clearly, reviewed consistently, and converted into work only when appropriate.
Using Work Requests improves prioritization, accountability, and overall maintenance efficiency.
Last updated