Timesheets Support Records

Retrieval metadata

feature_group: "Timesheets"
record_count: 3
approx_page_tokens: 2173
recommended_chunking: one Knowledge Record section per vector chunk

Feature group overview

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

This section contains chatbot training records for Timesheets sub-features.

Knowledge Record: Timesheets / Timekeeping

record_id: LFS-timesheets-timekeeping

primary_intents:

how_to_setup
when_to_use
workflow_design
troubleshooting
quickbooks_sync

Sample user utterances

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

Entities to extract

user_role
workspace
feature_area
quickbooks_version
sync_status
source_of_truth
technician_name
foreman_name
crew_name
time_type

Timekeeping covers the full lifecycle of shift time and work-order-specific time. Use it when the business needs payroll, job costing, productivity, or work order labor documentation. Before giving exact setup steps, confirm: Does the user need shift time, work time, technician entry, foreman entry, or office correction. Then explain the recommended configuration, test with a sample record, and note this guardrail: QBO time/work types do not sync like QBD; confirm QuickBooks version before giving integration guidance.

Configure when

the business needs payroll, job costing, productivity, or work order labor documentation.

Ask before answering

Does the user need shift time, work time, technician entry, foreman entry, or office correction?

Dependencies

QuickBooks version confirmed
integration settings checked
source-of-truth rules defined
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

QBO time/work types do not sync like QBD; confirm QuickBooks version before giving integration guidance.

Escalation rule

Escalate if data is missing after sync, accounting source-of-truth is unclear, or the user asks for accounting treatment.

Source URLs

Default response pattern

For questions about Timekeeping, 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: Timesheets / Timesheets, timesheets shown in a table view (Technicians Name, Start Time, S...

record_id: LFS-timesheets-timesheets-timesheets-shown-in-a-table-view-technicians-name-start-time-s

primary_intents:

how_to_setup
when_to_use
workflow_design
troubleshooting
quickbooks_sync

Sample user utterances

How do I set up Timesheets, timesheets shown in a table view (Technicians Name, Start Time, S in Lexul?
When should we use Timesheets, timesheets shown in a table view (Technicians Name, Start Time, S?
Why is Timesheets, timesheets shown in a table view (Technicians Name, Start Time, S not working or not showing?
Can Lexul handle Timesheets, timesheets shown in a table view (Technicians Name, Start Time, S for our workflow?

Entities to extract

user_role
workspace
feature_area
quickbooks_version
sync_status
source_of_truth
technician_name
foreman_name
crew_name
time_type

Approved answer basis

Timesheets table shows technicians, start/stop times, per diem, work entries, edit options, and approval status. Use it when office/admin users review, correct, approve, and export time. Before giving exact setup steps, confirm: What date range and technician should be reviewed? Are entries approved. Then explain the recommended configuration, test with a sample record, and note this guardrail: Office permissions can create overlapping entries; align work time within shift time for proper nesting.

Configure when

office/admin users review, correct, approve, and export time.

Ask before answering

What date range and technician should be reviewed? Are entries approved?

Dependencies

QuickBooks version confirmed
integration settings checked
source-of-truth rules defined
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 create overlapping entries; align work time within shift time for proper nesting.

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 Timesheets, timesheets shown in a table view (Technicians Name, Start Time, S..., 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: Timesheets / Export (XLSX, PDF)

record_id: LFS-timesheets-export-xlsx-pdf

primary_intents:

how_to_setup
when_to_use
workflow_design
troubleshooting
quickbooks_sync
export_report

Sample user utterances

How do I set up Export (XLSX, PDF) in Lexul?
When should we use Export (XLSX, PDF)?
Why is Export (XLSX, PDF) not working or not showing?
Can Lexul handle Export (XLSX, PDF) for our workflow?

Entities to extract

user_role
workspace
feature_area
quickbooks_version
sync_status
source_of_truth
technician_name
foreman_name
crew_name
time_type

Approved answer basis

Timesheet exports create XLSX/PDF payroll or accounting support files. Use it when payroll, job costing review, or management reports need downloadable time data. Before giving exact setup steps, confirm: Should the export include only approved time entries? What date range is required. Then explain the recommended configuration, test with a sample record, and note this guardrail: Exported data quality depends on accurate technician/foreman time entry and approval workflow.

Configure when

payroll, job costing review, or management reports need downloadable time data.

Ask before answering

Should the export include only approved time entries? What date range is required?

Dependencies

QuickBooks version confirmed
integration settings checked
source-of-truth rules defined
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

Exported data quality depends on accurate technician/foreman time entry and approval workflow.

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 Export (XLSX, PDF), 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.

Timesheets Support Records

On this page