Quality
TQs
Technical Queries
Technical queries as activities with tag and document links — not a side mailbox.
A TQ is a question that must stay attached to equipment or a drawing revision until it is answered. Configure a Technical Query activity type, target the tag, hierarchy, or document, and keep the thread on the activity: comments, evidence, status, assignee.
Entity references pin a document revision so the query does not drift off the sheet that caused it. This is not a pre-built TQ approval workflow or a different product from RFI-style walkdown labels — those are configured separately. It is the register pattern completions teams already understand.
The question stays on the drawing
A mailbox TQ dies when the inbox moves on. An activity linked to the tag and the pinned revision is still there when the cert is ready to sign and someone asks why that valve changed.
What it does
- ✓Raise a TQ against equipment, drawings, or documents
- ✓Hold the question, answer, and closeout on the activity
- ✓Pin supporting document revisions so the query stays on the right sheet
- ✓Assign TQs to engineers and track them through to completion or rejection
- ✓Use comment and evidence steps when the procedure should record the exchange
- ✓Label by discipline or subsystem for filtering
- ✓Surface open TQs in assignee My Work queues
- ✓Export open and closed TQ registers with related tag and document metadata
- ✓Same model as NCRs and punch: one queue, one hierarchy
Highlights
- • TQs stay searchable with the rest of commissioning work
- • Document revision pinning on references
- • Type and labels are yours to configure
- • Not a default legal TQ form pack
Demo
Demo video coming soon
See the rest of the platform, or talk to us about a demo.