Service Leave

Service Leave

Purpose and when to use this record

Block a technician’s dispatch availability for PTO, illness, training, meetings, or another approved absence.

At a glance

• Identify it by: Technician, Leave Type, Start, and End.

• Check its business context: Technician.

• Why care: Customer, equipment, scope, priority, technician availability, parts, labor, and status must stay aligned from intake through billing.

Before you begin

You need the Brisk storespermission for the action you are taking on service leaveleave. asIf parta ofCreate, theEdit, serviceor module.Delete This generated referencecontrol is awaitingabsent, workflowdo review.not work around it with another user’s account; ask an administrator to review your role.

Have valid Technician records ready first. Those selections determine where this Service Leave belongs and which later screens can find it.

Create a recordService Leave

TheCreate evidencea packetService identifiesLeave after searching for the viewperson, organization, item, location, or resource under alternate names and sourceidentifiers. locationMerge foror correct an existing master record instead of creating a duplicate.

1. Select the business context first: Technician.

2. Enter the required identifying and operational values: Technician, Start, and End.

3. Review Leave Type, and Approved deliberately; these choices control availability or workflow rather than merely describing the record.

4. Save the Service Leave, then confirm Technician, Leave Type, Start, End, Approved, and Notes on its detail page before continuing.

After saving: Verify this action.Service ConfirmLeave user-facingin stepsthe next transaction or assignment screen before approvingstaff build new activity on it; correct ownership, classification, and active state now rather than after transactions accumulate.

Delete a Service Leave

Delete this page.Service Leave only if it is an unused duplicate or setup mistake. Once other records refer to it, preserve that history and make the value inactive when the screen provides that option.

On the confirmation page, verify Technician, Leave Type, Start, and End. After confirmation, return to the Service Leave list and make sure only the intended Service Leave was removed.

ViewReview recordService Leave details

The evidence packet identifiesUse the viewdetail page as the shared record of what this Service Leave currently means. Verify Leave Type before relying on it for a decision.

Follow Technician to determine whether the issue is on this Service Leave or on one of those linked records.

Next check: Verify this Service Leave in the next transaction or assignment screen before staff build new activity on it; correct ownership, classification, and sourceactive locationstate fornow thisrather action.than Confirmafter user-facingtransactions steps before approving this page.accumulate.

Edit an existing recordService Leave

TheEdit evidencethis packetService identifiesLeave to keep the viewsame real-world party, item, location, or resource accurate. Do not repurpose it for a different entity after activity is attached.

1. Open the detail page. Compare Technician with the supporting document or approved request.

2. Recheck Leave Type. These values are most likely to change intake, estimating, dispatch, parts, labor, completion, and sourcebilling.

   location

3. Save the change, return to the list, and confirm that the Service Leave now appears under the expected Leave Type, and Approved.

After the change: Verify this Service Leave in the next transaction or assignment screen before staff build new activity on it; correct ownership, classification, and active state now rather than after transactions accumulate.

Fields and business rules

Brisk stores 6 user-relevant fields for this action.Service ConfirmLeave, user-facingincluding steps1 beforelinked-record approvingselection and 1 controlled-choice field. Create and edit screens may hide calculated or workflow-managed values from this page.full reference.

Deletearecord

sourcelocation

Field	Required	What it controls
Technician	Yes	The evidencetechnician packetassociated identifieswith thethis viewservice andleave.
Leave Type	No	The leave type recorded for this action.service Confirmleave. user-facingAvailable stepsvalues: PTO, Sick, Training, Meeting, Other.
Start	Yes	Date and time recorded for start on this service leave.
End	Yes	Date and time recorded for end on this service leave.
Approved	No	Whether the approved option applies to this service leave.
Notes	No	Additional internal notes about this service leave.

What happens next

Verify this Service Leave in the next transaction or assignment screen before approvingstaff thisbuild new activity on it; correct ownership, classification, and active state now rather than after transactions accumulate.

Common mistakes and troubleshooting

• The record will not save: Recheck Technician, Start, and End and any message beside the field. A required related record may also be inactive or unavailable to your role.

• The values look right but the result is wrong: Open Technician from the detail page. Correct the specific relationship that is wrong instead of forcing a total or status to compensate for it.