Time Tracking Support Records

Retrieval metadata

feature_group: "Time Tracking"
record_count: 5
approx_page_tokens: 3337
recommended_chunking: one Knowledge Record section per vector chunk

Feature group overview

This page contains chatbot training records for Time Tracking sub-features. Retrieve one ### Knowledge Record: chunk at a time when possible.

This section contains chatbot training records for Time Tracking sub-features.

Knowledge Record: Time Tracking / Shift Times

record_id: LFS-time-tracking-shift-times

primary_intents:

how_to_setup
when_to_use
workflow_design
troubleshooting
quickbooks_sync

Sample user utterances

How do I set up Shift Times in Lexul?
When should we use Shift Times?
Why is Shift Times not working or not showing?
Can Lexul handle Shift Times for our workflow?

Entities to extract

user_role
workspace
feature_area
technician_name
foreman_name
crew_name
time_type

Shift time records the technician's clocked time for the day. Use it when the business needs daily clock-in/clock-out, payroll export, or time review. Before giving exact setup steps, confirm: Who is clocking in/out and what start/stop time applies. Then explain the recommended configuration, test with a sample record, and note this guardrail: Work time outside shift time may not nest correctly under the shift; align entries carefully.

Configure when

the business needs daily clock-in/clock-out, payroll export, or time review.

Ask before answering

Who is clocking in/out and what start/stop time applies?

Dependencies

active users
time types
permission roles

Role workflow

Foreman/technician records time; office reviews and approves; accounting exports or syncs as needed.

Permissions and visibility

Technicians/foremen enter time; supervisors/accounting should control approvals, edits, exports, and syncs.

Known limits and guardrails

Work time outside shift time may not nest correctly under the shift; align entries carefully.

Escalation rule

Escalate when the user reports unexpected system behavior, requests a workflow not documented in sources, or needs custom development.

Source URLs

Default response pattern

For questions about Shift Times, first identify whether the customer is asking about setup, fit, workflow design, troubleshooting, permissions, or QuickBooks sync. Use the approved answer basis above, ask only the listed clarification question when needed, and end with the escalation rule when the issue cannot be resolved from documented checks.

Knowledge Record: Time Tracking / Work Times

record_id: LFS-time-tracking-work-times

primary_intents:

how_to_setup
when_to_use
workflow_design
troubleshooting
quickbooks_sync

Sample user utterances

How do I set up Work Times in Lexul?
When should we use Work Times?
Why is Work Times not working or not showing?
Can Lexul handle Work Times for our workflow?

Entities to extract

user_role
workspace
feature_area
technician_name
foreman_name
crew_name
time_type

Approved answer basis

Work time records time against a specific work order and time type. Use it when the business needs job costing, invoice labor detail, or proof of work by task/job. Before giving exact setup steps, confirm: Which work order and time type should receive the time? Is it billable or job-cost only. Then explain the recommended configuration, test with a sample record, and note this guardrail: If time is missing from an invoice, verify work time exists on the work order and is approved/imported as needed.

Configure when

the business needs job costing, invoice labor detail, or proof of work by task/job.

Ask before answering

Which work order and time type should receive the time? Is it billable or job-cost only?

Dependencies

active users
time types
permission roles

Role workflow

Foreman/technician records time; office reviews and approves; accounting exports or syncs as needed.

Permissions and visibility

Technicians/foremen enter time; supervisors/accounting should control approvals, edits, exports, and syncs.

Known limits and guardrails

If time is missing from an invoice, verify work time exists on the work order and is approved/imported as needed.

Escalation rule

Escalate when the user reports unexpected system behavior, requests a workflow not documented in sources, or needs custom development.

Source URLs

Default response pattern

For questions about Work Times, first identify whether the customer is asking about setup, fit, workflow design, troubleshooting, permissions, or QuickBooks sync. Use the approved answer basis above, ask only the listed clarification question when needed, and end with the escalation rule when the issue cannot be resolved from documented checks.

Knowledge Record: Time Tracking / Crew tracking (controlled by a foreman technician user)

record_id: LFS-time-tracking-crew-tracking-controlled-by-a-foreman-technician-user

primary_intents:

how_to_setup
when_to_use
workflow_design
troubleshooting
quickbooks_sync
permissions_visibility

Sample user utterances

How do I set up Crew tracking (controlled by a foreman technician user) in Lexul?
When should we use Crew tracking (controlled by a foreman technician user)?
Why is Crew tracking (controlled by a foreman technician user) not working or not showing?
Can Lexul handle Crew tracking (controlled by a foreman technician user) for our workflow?

Entities to extract

user_role
workspace
feature_area
technician_name
foreman_name
crew_name
time_type

Approved answer basis

Foreman crew tracking lets one foreman log shift/work times for crew members. Use it when crews travel/work together and individual technicians should not enter duplicate time. Before giving exact setup steps, confirm: Which crew is active and is the foreman responsible for all crew time today. Then explain the recommended configuration, test with a sample record, and note this guardrail: Foreman permissions allow crew timesheet visibility and logging; avoid crew changes while active time is being logged.

Configure when

crews travel/work together and individual technicians should not enter duplicate time.

Ask before answering

Which crew is active and is the foreman responsible for all crew time today?

Dependencies

active users
time types
permission roles

Role workflow

Foreman/technician records time; office reviews and approves; accounting exports or syncs as needed.

Permissions and visibility

Technicians/foremen enter time; supervisors/accounting should control approvals, edits, exports, and syncs.

Known limits and guardrails

Foreman permissions allow crew timesheet visibility and logging; avoid crew changes while active time is being logged.

Escalation rule

Escalate when the user reports unexpected system behavior, requests a workflow not documented in sources, or needs custom development.

Source URLs

Default response pattern

For questions about Crew tracking (controlled by a foreman technician user), first identify whether the customer is asking about setup, fit, workflow design, troubleshooting, permissions, or QuickBooks sync. Use the approved answer basis above, ask only the listed clarification question when needed, and end with the escalation rule when the issue cannot be resolved from documented checks.

Knowledge Record: Time Tracking / Bulk time entry

record_id: LFS-time-tracking-bulk-time-entry

primary_intents:

how_to_setup
when_to_use
workflow_design
troubleshooting
quickbooks_sync

Sample user utterances

How do I set up Bulk time entry in Lexul?
When should we use Bulk time entry?
Why is Bulk time entry not working or not showing?
Can Lexul handle Bulk time entry for our workflow?

Entities to extract

user_role
workspace
feature_area
technician_name
foreman_name
crew_name
time_type

Approved answer basis

Bulk time entry should support office correction or faster entry for repeated crew/technician work. Use it when many similar time entries need to be added or corrected at once. Before giving exact setup steps, confirm: Which technicians, work orders, date range, time type, and approval status should be applied. Then explain the recommended configuration, test with a sample record, and note this guardrail: If bulk entry behavior is not documented publicly, document internal workflow and escalate uncertain permissions/edge cases.

Configure when

many similar time entries need to be added or corrected at once.

Ask before answering

Which technicians, work orders, date range, time type, and approval status should be applied?

Dependencies

active users
time types
permission roles

Role workflow

Foreman/technician records time; office reviews and approves; accounting exports or syncs as needed.

Permissions and visibility

Technicians/foremen enter time; supervisors/accounting should control approvals, edits, exports, and syncs.

Known limits and guardrails

If bulk entry behavior is not documented publicly, document internal workflow and escalate uncertain permissions/edge cases.

Escalation rule

Escalate when the user reports unexpected system behavior, requests a workflow not documented in sources, or needs custom development.

Source URLs

Default response pattern

For questions about Bulk time entry, first identify whether the customer is asking about setup, fit, workflow design, troubleshooting, permissions, or QuickBooks sync. Use the approved answer basis above, ask only the listed clarification question when needed, and end with the escalation rule when the issue cannot be resolved from documented checks.

Knowledge Record: Time Tracking / Manual shift and work time entry

record_id: LFS-time-tracking-manual-shift-and-work-time-entry

primary_intents:

how_to_setup
when_to_use
workflow_design
troubleshooting
quickbooks_sync

Sample user utterances

How do I set up Manual shift and work time entry in Lexul?
When should we use Manual shift and work time entry?
Why is Manual shift and work time entry not working or not showing?
Can Lexul handle Manual shift and work time entry for our workflow?

Entities to extract

user_role
workspace
feature_area
technician_name
foreman_name
crew_name
time_type

Approved answer basis

Manual time entry allows office/admin correction of shift or work time records. Use it when technicians forgot to clock in/out, work time needs correction, or payroll reconciliation requires edits. Before giving exact setup steps, confirm: Is the entry a shift time or work time? Does it overlap existing entries. Then explain the recommended configuration, test with a sample record, and note this guardrail: Office permissions can add/edit times but overlapping/misaligned entries may not display under the expected shift.

Configure when

technicians forgot to clock in/out, work time needs correction, or payroll reconciliation requires edits.

Ask before answering

Is the entry a shift time or work time? Does it overlap existing entries?

Dependencies

active users
time types
permission roles

Role workflow

Foreman/technician records time; office reviews and approves; accounting exports or syncs as needed.

Permissions and visibility

Technicians/foremen enter time; supervisors/accounting should control approvals, edits, exports, and syncs.

Known limits and guardrails

Office permissions can add/edit times but overlapping/misaligned entries may not display under the expected shift.

Escalation rule

Escalate when the user reports unexpected system behavior, requests a workflow not documented in sources, or needs custom development.

Source URLs

Default response pattern

For questions about Manual shift and work time entry, first identify whether the customer is asking about setup, fit, workflow design, troubleshooting, permissions, or QuickBooks sync. Use the approved answer basis above, ask only the listed clarification question when needed, and end with the escalation rule when the issue cannot be resolved from documented checks.

Time Tracking Support Records

On this page