Job card
A React block (a whole screen) in Beamline's Shop app.
A technician's repair order, phone-first. The vehicle, the customer and when it's due in words (due at, due in, overdue by how long); an offline copy says when it last synced. Tasks with their state; the open task shows estimated and logged time side by side with their own labels, its checklist, the clock, and every time entry (a clock span, or time added by hand with why), so logged time is never made up. Finishing a task while its clock runs asks what to do with the timer: stop it and finish, or keep it running for the next task. Internal notes and recommendations for the customer are separate labelled sections, and the customer preview shows exactly what the customer receives, never an internal note.
Use it for
- A technician working one job on a phone or tablet: clocking tasks, ticking checklists, adding notes.
- Anywhere logged time must come from a clock or a stated reason, and internal notes must never reach the customer.
Not for
- A manager's board of every order (work-orders).
- Timesheets across days (timesheet-review).
Anatomy
- header: the product's mark, the order number, vehicle, plate and mileage, the customer, the due state in words
- offline notice with the last sync
- tasks: name, logged against estimated, state
- the open task: estimated and logged, over the estimate, the clock, checklist, time entries, add time by hand, finish or reopen
- finishing with the clock running: stop it and finish, or keep it running for the next task
- notes: recommendations for the customer and internal notes (who sees each a hint on its heading), each added from a button that opens its box; the customer preview
States
- due: soon (warning), overdue (danger), otherwise neutral
- task: to do, started (warning), clock running (info), done (success)
- over the estimate: the logged box tinted warning and says by how much
- not estimated: said, never zero
- offline: said with the last sync
- refused save: the change is undone and the reason said
- phone: tasks and notes on a switch, the task under the list
- right to left: the layout mirrors
- reduced motion: nothing animates
Keyboard
- Tab through tasks, the clock, checklist, entries and notes; Enter or Space opens a task and presses buttons; Space ticks checklist items
Motion
Nothing moves; the running clock's minutes refresh every 30 seconds only while one runs.
Props
| Prop | Type | Default | Description |
|---|---|---|---|
order (required) | RepairOrder | — | |
defaultTasks (required) | JobTask[] | — | |
defaultNotes (required) | JobNote[] | — | |
technician (required) | string | — | The technician using it, named on what they add. |
defaultTaskId | string | — | |
offline | { syncedAt: string; } | null | — | Working from a stale copy: when it last synced. |
now | string | — | |
onTaskChange | ((task: JobTask) => Promise<unknown>) | — | Save a task's change (clock, checklist, finish, time by hand); reject with the reason to keep it here. |
onNote | ((note: JobNote) => Promise<unknown>) | — | |
product | string | — | Your product's name, shown as its mark. |
className | string | — | Classes on the documented visual root; no override by default. |
ref | Ref<HTMLDivElement> | — | Receives the documented native target or imperative handle; omitted by default. |
Built from
- Avatar
- Button
- Checkbox
- Empty state
- Input
- Label
- Number field
- Segmented control
- Select
- Skeleton
- Spinner
- Switch
- Text morph
- Textarea
- Tooltip
Import
import { JobCard } from "@beamline/job-card";
Get it
Job card is part of Beamline UI. Install the parts you need in your React app as compiled packages or editable source. Get Beamline · Connect your agent
More in Shop
- Product editor: A product being made in a shop's back office, every value read as text at rest. The variant grid, grouped by the first option, lists each combination…
- Category manager: A shop's product categories, nested and ranked. Each category moves up, down or into another from its menu, and every move gets its own receipt (saving…
- Inventory item: One stock item in a shop's back office, apart from the variants that sell it (how many each uses per unit). Stock per location as stocked, reserved and…
- Plan comparison: Plans side by side against every feature: prices that roll between monthly and yearly, the current and recommended plan marked, a header that stays in…
- Step form: The finished frame for any multi-step form you compose — onboarding, intake brief, questionnaire, booking, application: a wide card with progress, the…
- Orders admin: A shop's order desk: today's orders and revenue, quick filters for what needs doing (to fulfil, unpaid, returns), a virtualised orders grid, and the…
- Order detail: One shop order with payment and fulfilment as two separate lanes. The header says where each stands (paid, partly paid, awaiting, refunded; not…
- Order board: A shop's orders as cards in its columns, on the shared kanban with drag and keyboard moves. Each card: number, estimate or work order, customer, vehicle…
- Order composer: An order made inside a support ticket: products found by name, each variant with its stock drawn and said (in stock, none, oversold, not known) and the…
- Draft orders: A draft order made for a customer in a shop's back office that reads like the order it will become. The lines lead: each with its variant and SKU or…
- Order changes: What happens to a shop order after it's placed. Edit: the order as it stands beside the requested version, each line marked new, changed (old → new…
- Special orders: Customers' special orders as demand to buy for, per outlet: To order apart from Ordered; each product's demand, what is reserved, incoming and on order…
- Order history and fills: Every order the account placed and every fill it got, for a period: totals for volume, fees, fill rate and maker share; orders with their status and how…
- Order ledger: Purchase orders as money. Each order's spend is drawn against its approved total (paid, billed, pending, what is left, and any overrun past the end…
- Ticket orders: A customer's orders inside a support ticket, each action's effect said before it's done: orders and drafts kept apart, a paid draft shown once as its…
- Record search: One search across connected records (customers, vehicles, orders) by name, phone, plate, VIN or order number. What the words look like is said (info)…
- Return queue: A queue of return cases. Search by return, order or customer, exactly (the default) or loosely; status tabs with counts, Requires attention first; a date…
- Return case: One return as one place where every act is its own. The return, its order (linked out) and the customer on three cards; the stage said on its tone. Items…
- Return request: Staff start a return from an order, and edit the reasons customers pick. New return: the order's lines as a checklist, each with its variant, price and…
- Purchase orders: A salon's purchase orders, received: the orders down the side, the chosen one beside them. Each line still due reads as a strip of received, this…
- Print quote: A print shop's quoting in three places. Quote: a group of garments that share one imprint and one quantity break, the group's pieces counted together and…
- Service estimate: An estimate for one vehicle. Services added from the catalogue (one not listed for this vehicle said on warning, fit unknown said); each with its lines…
- Parts tracker: Parts across a shop's work orders: each with its number, the order and vehicle, supplier, quantity and cost (not known said), and where it is: ordered…
- Visit board: The staff board for a walk-in queue: visits move from waiting through called and serving to done today. Arrival (here or on the way), the place in the…