Coordinate approved service work, including customer equipment, priority, warehouse, technician activity, parts, labor, and status.
## At a glance
- **Identify it by:** **Service Order #**, **Status**, and **Service Date**.
- **Check its business context:** **Customer**, **Equipment**, **Status**, **Type**, and **Warehouse**.
- **Why care:** Customer, equipment, scope, priority, technician availability, parts, labor, and status must stay aligned from intake through billing.
- **Why care:** Treat posted, processed, paid, reversed, and edit-locked states as controls—not ordinary descriptive fields. Confirm the source transaction before changing any state that the screen permits you to change.
- **Why care:** Status communicates workflow progress to other staff. Change it only when the underlying work, approval, payment, or handoff has actually occurred.
## Before you begin
You need the Brisk permission for the action you are taking on service orders. If a Create, Edit, or Delete control is absent, do not work around it with another user’s account; ask an administrator to review your role.
Create a service order
Create a service order only after confirming that the source document or operational event has not already been entered.
1. Select the business context first: **Customer**, **Equipment**, **Status**, **Type**, **Warehouse**, and **Service Quote**, plus the remaining screen fields.
2. Enter the required identifying and operational values: **Service Order #**.
3. Review **Priority**, **Edit Locked**, and **Converted** deliberately; these choices control availability or workflow rather than merely describing the record.
4. Save the service order, then confirm **Service Order #**, **Status**, and **Service Date** on its detail page before continuing.
After saving: Keep technician time, parts, notes, and status current; when work is complete, review the customer billing and payment handoff.
Delete a service order
Delete this service order only when it was entered by mistake and no downstream history depends on it. Use a reversal, void, credit, counter-adjustment, or status correction for a real event that later changed.
Before confirming, check for related **Bookings**, **Inventory Records**, **Service Invoices**, **Service Labor**, and **Service Parts**, plus the remaining screen fields. Brisk may refuse deletion when another record depends on this one; resolve the duplicate or use the supported correction workflow instead of breaking the trail.
On the confirmation page, verify **Service Order #**, **Status**, and **Service Date**. After confirmation, return to the Service Orders list and make sure only the intended service order was removed.
Review service order details
A fictional service order awaiting parts for a customer-owned irrigation pump.
Use the detail page as the shared record of what this service order currently means. Verify **Status**, **Priority**, **Service Date**, and **Edit Locked** before relying on it for a decision.
Follow **Customer**, **Equipment**, **Status**, **Type**, **Warehouse**, and **Service Quote**, plus the remaining screen fields to determine whether the issue is on this service order or on one of those linked records.
Next check: Keep technician time, parts, notes, and status current; when work is complete, review the customer billing and payment handoff.
Edit an existing service order
The Service Orders update screen in the Brisk documentation demo.
Edit this service order to correct or complete the same source document or operational event; use the supported reversal or follow-up workflow when the business event itself changed.
1. Open the detail page. Compare **Customer**, **Equipment**, **Status**, **Type**, **Warehouse**, and **Service Quote**, plus the remaining screen fields with the supporting document or approved request.
2. Recheck **Customer**, **Status**, **Warehouse**, **Priority**, **Service Date**, and **Edit Locked**. These values are most likely to change intake, estimating, dispatch, parts, labor, completion, and billing.
3. Save the change, return to the list, and confirm that the service order now appears under the expected **Status**, **Priority**, and **Edit Locked**.
After the change: Keep technician time, parts, notes, and status current; when work is complete, review the customer billing and payment handoff.
Find and review service orders
The Service Orders list screen in the Brisk documentation demo.
Use the Service Orders list to find the correct record before opening or changing it. Compare **Service Order #**, **Status**, and **Service Date**. Records with similar names or numbers can still belong to different **Customer**, **Equipment**, **Status**, **Type**, **Warehouse**, and **Service Quote**, plus the remaining screen fields.
- Keyword search checks **Service Order #**, **Memo**, **Display Name**, **Unit Number**, **Description**, and **Name**, plus the remaining screen fields.
- Narrow the list with **Customer**, **Equipment**, and **Status** filters.
- The date filter uses **Service Date**; choose a range that matches the business event you are reconciling.
- The initial order emphasizes **Id**. Select a column heading when you need a different comparison.
Open the service order whose **Service Order #**, **Status**, and **Service Date** match the task. If it is missing, clear the list filters and recheck **Customer**, **Equipment**, **Status**, **Service Date**, **Priority**, and **Edit Locked** rather than creating a replacement immediately.
## Fields and business rules
Brisk stores 15 user-relevant fields for this service order, including 8 linked-record selections and 1 controlled-choice field. Create and edit screens may hide calculated or workflow-managed values from this full reference.
| Field | Required | What it controls |
|---|---:|---|
| **Service Order #** | Yes | A serivce order's friendly name, used to identify the transaction in receipts, reports, and searches. |
| **Customer** | No | Links this service order to the selected Customer; verify the relationship before saving. |
| **Equipment** | No | Links this service order to the selected Equipment; verify the relationship before saving. |
| **Status** | No | Links this service order to the selected service status; verify the relationship before saving. |
| **Type** | No | If your service department tracks work by category, use this field to record it. |
| **Warehouse** | No | The physical location from which inventory items for this service order are sourced. |
| **Service Quote** | No | Optional originating service quote linked to this service order. |
| **Quote** | No | Optional originating quote for this service order. |
| **Lead** | No | Optional originating service lead. |
| **Priority** | No | Controls dispatch urgency and backlog ordering. Available values: Low, Normal, High, Urgent. |
| **Memo** | No | Use this field to store internal notes about this service order. |
| **Service Date** | No | The date and time that this service order was started. |
| **Mileage/Hours** | No | Record the equipment mileage, hours, or other time tracking metric. |
| **Edit Locked** | No | Whether the edit locked option applies to this service order. |
| **Converted** | No | Marks this service order as conerted to an invoice and completed. |
## What happens next
Keep technician time, parts, notes, and status current; when work is complete, review the customer billing and payment handoff.
## Common mistakes and troubleshooting
- **The record will not save:** Recheck **Service Order #** and any message beside the field. A required related record may also be inactive or unavailable to your role.
- **The record saved but is not available where expected:** Recheck **Status**, **Priority**, and **Edit Locked**, then clear the filters on the destination list. A saved record can still be inactive, unpublished, locked, unapproved, or in the wrong workflow state.
- **The values look right but the result is wrong:** Open **Customer**, **Equipment**, **Status**, **Type**, **Warehouse**, and **Service Quote**, plus the remaining screen fields from the detail page. Correct the specific relationship that is wrong instead of forcing a total or status to compensate for it.
