9:41
📶🔋
‹Field issue threadResolve
!
Field Issue #FI-0234
Sealant depth insufficient
MK
Mike Kelly09:14
Sealant depth at this joint is only 8mm. Spec requires minimum 12mm.
📷 IMG_0892.jpg
JP
James Parker09:32
@Sarah can you confirm the correct bead profile for this detail?
SC
You09:45
Profile should be 12×15 triangular. Drawing DWG-CW-401 detail 3. I'll raise with the installer.
Unread thread
RFI and Field issues
Action closed
Owner and date recorded
Evidence export
Signed record ready
XO-Threads

Project threads tied to the record.

XO-Threads keeps messages, files, voice notes, decisions, actions, and read state attached to the project entity they belong to. RFIs, document revisions, estimates, CVR snapshots, Field issues, and general records get a searchable, auditable conversation instead of another loose chat.

See XO-Threads in ActionExplore Features
Entity-linked threads
Decisions + actions
External access
Evidence export
Part of BrieXO FIELD

This app is one surface inside the FIELD bundle. Use this page for product-specific detail, then compare bundle tiers when you are ready to buy.

Explore FIELD See FIELD Pricing
Entities
RFIs, docs, Field issues
Outcomes
Decisions and actions
Access
Participants and invites
Evidence
Signed export bundles
The Problem

Chats break away from the work they discuss

Project teams need quick conversations, but they also need those conversations attached to the RFI, document, issue, estimate, or CVR snapshot they are actually about.

Record Context Gets Lost

Messages about RFIs, Field issues, and document revisions drift into separate chat tools, leaving the formal record behind.

Decisions Do Not Become Outcomes

Approvals, follow-ups, and closeout promises are easy to miss when they stay buried as free-text replies.

Audit Trails Are Hard to Prove

When a dispute appears, teams need messages, attachments, read state, decisions, actions, and audit events in one exportable record.

Capabilities

Collaboration workflows XO Threads supports

XO-Threads turns project communication into entity-linked records with outcomes, access control, evidence export, mobile queued sends, and governed partner access.

Entity-linked threads

Create project threads for general records, RFIs, document revisions, estimates, CVR snapshots, and Field issues with validation against source records.

RFIsDocsField issues

Messages, files, and voice notes

Support text, image, file, voice, and system messages with replies, mentions, reactions, bookmarks, attachments, and voice transcription where services are configured.

VoiceFilesXO Capture

Mobile queued sends

Mobile can stage media and voice, queue existing-thread and new general-thread messages, retry with backoff, and post with idempotency keys.

QueueRetriesIdempotency

Decisions and action items

Capture decisions, link them to messages or target entities, and create action items with assignees, due dates, statuses, and completion metadata.

DecisionsActionsAssignees

Participants and read state

Track roles, private thread access, pinned/starred/muted preferences, last-read state, read receipts, and seen-by context.

RolesRead statePreferences

Search and evidence export

Search across threads, messages, decisions, and actions, then export signed thread records with message CSV, audit CSV, and attachment manifests.

SearchPDF/ZIPAudit CSV
Features

Fast conversation, controlled outcomes

XO-Threads keeps day-to-day collaboration close to the project records, permissions, and evidence trail your team already relies on.

Thread workspace with record context

See project threads in one workspace, filter by status, priority, entity type, project, or record, then open the discussion, messages, decisions, actions, and participants together.

  • Entity filtersWork across RFIs, document revisions, estimates, CVR snapshots, Field issues, and general threads
  • Unread and seen-by stateUse last-read state and participant read receipts to understand who has seen what
  • Searchable project historySearch across thread titles, messages, decisions, and action records
  • Realtime refresh where configuredSocket events can refresh thread state and presence when the service is enabled
9:41
📶🔋
Threads
AllRFIsDocsIssues
!
Sealant depth insufficient3
FI-0234 • Zone A Level 12
Sarah: Profile should be 12×15 triangular...
?
Bracket orientation2h ago
RFI-0156 • Grid 3-4
Mike: Confirmed with structural engineer...
D
Corner detail revision1
DOC-401 • Revision C
James: Confirmed revision comments...
✓
Glass chip damageResolved
SN-0198 • Zone B Level 8
Replacement ordered and scheduled
4 active threads
2 need your response

Messages, attachments, and voice from site

Thread messages can carry text, files, images, voice notes, and XO Capture photo references, with mobile queueing for poor signal and idempotent send receipts.

  • File and XO Capture referencesAttach a file asset or XO Capture photo reference with metadata and media type
  • Voice notes and transcriptsMobile voice notes can be uploaded and transcribed when the backend services and credentials are available
  • Queued mobile sendsStage media, retry due queue items, and clean staged files after successful send
  • Reactions, bookmarks, and repliesKeep quick acknowledgements and message-level references inside the thread record
!
Adding to: FI-0234
Sealant depth insufficient
âš¡
↻
Attachment linked
Stored on the thread
Capability Buckets

What XO Threads owns

The product is a collaboration and evidence layer for fast discussion, controlled outcomes, governed access, and exportable proof.

Voice Notes

Mobile recording, staged audio upload, backend transcription, transcript metadata, and refresh events where services are configured.

Read Receipts

Participant last-read state, seen-by projections, authenticated read paths, public invite reads, and federation reads.

Mentions and Interactions

Mention metadata, reactions, bookmarks, replies, update/delete permissions, and soft deletion.

Realtime Refresh

Signed backend emits and Socket.IO room refresh events when the realtime service is configured.

External Invites

Tokenized viewer/commenter access with expiry, revocation, use counts, read state, and text replies.

Federation Gateway

Contract-scoped partner thread list, messages, read state, and text responses through shared federation controls.

Evidence Export

Signed JSON, PDF, or ZIP outputs with messages, audit timeline, decisions, actions, read state, and attachment manifests.

AI and Analytics

Permissioned summaries, recaps, project digests, and backend decision/action/risk rollups with fallback behavior.

Integrations

Threads are created from real project records

XO Threads can be created or ensured by adjacent modules after their source records exist, following project permissions and each module's handoff path.

XO-Field

Native Field issues and issue-profile form instances can create or ensure project-visible threads.

XO-RFI

RFI records can create entity threads so discussion stays attached to the query.

XO-Docs

Document revision uploads can create or ensure threads for revision discussion.

XO-Commercial

CVR snapshot activity can create threads so commercial context is part of the record.

XO-Estimating

Estimate activity hooks can create discussion context for estimating records.

Ready to make project discussions auditable?

Use XO-Threads to keep project conversations tied to records, decisions, actions, partner access, and exportable evidence.

Book a DemoStart Free Trial