T&M Ticket Tool - iPad field entry + on-site signature¶
| Stage | Backlog |
|---|---|
| Status | Deferred |
| Design status | In review |
| Estimate | L |
| Confidence | Medium |
| Linear | PIN-304 ↗ PIN-53 ↗ |
| Linear status | Done · +1 planned |
| Cycle | C16 |
| Design | Design ↗ |
| Linear epic | Project Management & Controls |
| Module | Change Orders ↗ |
Status check: deferred, but shipped work exists
This surface is marked deferred, yet Linear shows PIN-53 as Done. Confirm whether it actually shipped (move the status off deferred) or only the remaining scope is deferred. Flagged for reconciliation.
Status: Not built · Route: not yet designed
Scope¶
Field-first Time & Material (T&M) ticket capture: crews log scope, hours, and on-site workers from an iPad, capture an on-site GC/client signature, and save offline-tolerant (local cache, synced when back online). Tickets are multi-selected and compiled into a formal Change Order, inheriting ticket data with hours rolled up by labor rate through the standard CO submission flow. (Source: PIN-304, PIN-53.)
Acceptance criteria¶
- Ticket form (iPad-optimized): date, project, floor, scope of work (free text + voice-to-text), workers on site (multi-select), hours per worker
- Photo attachment via iPad camera; touch signature capture canvas plus signer name/role
- Save creates a ticket in
signedstatus; offline-friendly local cache with sync when back online - Ticket list sub-section on the Change Orders tab: date, scope summary, signer, hours, status
- Multi-select tickets → "Compile into CO" creates a new CO with all selected tickets attached and an auto-generated description
- Bundled CO inherits worker/hours/scope data; hours roll up by labor rate from the cost code / vendor master
- Compiled CO goes through the standard CO submission flow; source tickets lock to
bundledstatus
Field-first Time & Material (T&M) ticket tool: field crews log scope of work, hours, and workers on an iPad, then capture an on-site GC/client signature before saving the ticket. Tickets accumulate over the life of the project and are later multi-selected and compiled into a formal Change Order (hours roll up by labor rate; the CO inherits the ticket data and goes through the standard CO submission flow).
Notes¶
Not started — Linear Backlog, 8 points. Distinct from the core Change Orders CRUD/workflow already covered by Project Detail - Change Orders (PIN-53) — this is the field-capture pipeline that feeds it. Large lift: offline-tolerant iPad entry plus signature capture.