QC Sign-Offs & Shop Records in FabTrk

QC Sign-Offs and Shop RecordsQuality control in FabTrk: attributed assembly sign-offs, notes and photos from the floor, and time logs that tie labor to the work.The paper trail is half the product in fabrication. Who inspected this frame? When was that flange issue caught, and what did it look like? How many hours actually went into that mezzanine? FabTrk builds those records where the work happens, so they exist without anyone "doing documentation." QC sign offs on assemblies Every assembly (a frame line, a purlin run, a girt line) can carry a QC sign off. Signing is one action on the assembly page, with an optional note ("welds visually inspected, UT on splices passed"). Three properties make the sign off worth something: Attributed. The signature is the logged in account, recorded with a timestamp. It cannot be entered on someone else's behalf: when the record says an inspector passed a frame, that inspector's login did it. Permissioned. Signing (and withdrawing a signature) requires the edit task permission. The QC Inspector, Lead Welder, foreman, and office roles have it by default; roles that shouldn't certify work don't. Durable. Sign offs are stored with the project. They survive redeploys, device changes, and personnel changes, and they are visible wherever the assembly appears. A sign off can be withdrawn (inspections get redone), and re signing records the new signer and time. Notes and photos from the floor Tasks accept notes and photos from anyone with write access. A fitter who shims a base plate photographs it; the photo and note live on the task, timestamped and attributed, in the project record forever. This is deliberately low ceremony. The floor will not fill out forms, but they will tap a camera button. Over a job's life those notes become the narrative an RFI, a back charge dispute, or a warranty claim needs, searchable in the project instead of buried in someone's text messages. Deleting notes is restricted to senior roles. The record is append friendly and edit hostile, which is exactly what makes it credible later. Time logs Time entries are logged against a project and, optionally, a task; the task list filters live to the selected project, so the log lands on the right work in two taps. Editing time entries is its own permission ( edit time ), so the crew logs their own hours while corrections stay controlled. Because time ties to the same projects and tasks the pipeline tracks, labor actuals sit next to production status: what a job consumed and what it produced are one record, not two systems to reconcile at the end of the month. The thread through all of it Every record in this guide (a sign off, a photo, a time entry) shares three attributes: who, when, and against which work. That is the entire discipline. FabTrk's job is to make capturing those three things nearly free at the moment they happen, because a record created in the moment is the only kind anyone believes a year later.