Project correspondence, on the record.
Built-in mail keeps project communication linked to the documents and decisions it concerns, not buried in personal inboxes.
- Inbox3
- RFIs2
- Documents
- Sent
- TransmittalAction requiredCivils set, Rev C issuedCape Civils
- RFIFor informationBeam clash at grid C/4Structural
- DocumentAcknowledgedA-102 approvedS. Naidoo
Critical instructions sit in one person's inbox. When they are away, or gone, the thread goes with them.
What Built-in mail gives you.
One inbox for the project
Transmittals, RFIs, and documents land in a single, sortable inbox.
Linked to documents
Every item ties back to the drawing or record it concerns.
Threaded history
The full conversation, in order, for anyone with access.
Action labels
See at a glance what needs action, what is for information, and what is acknowledged.
Read, archive, snooze
Work the inbox down with the dispositions you expect.
On the audit trail
Correspondence is part of the project record.
Three steps, start to finish.
It lands in the inbox
Transmittals and RFIs you receive show up in one place.
Act on it
Acknowledge, answer, or request a revision, then archive or snooze.
Keep it searchable
It stays on the record for whoever needs it next.
More of the platform.
Document control
Register, version, transmit, and mark up every drawing on one accountable record, so the whole project builds from the current set.
ExploreChange log and audit
A structured, linked audit trail across documents, projects, and tenders, so a dispute is settled by the record, not by memory.
ExploreContacts
Organisations and people, distribution lists, and project participants, kept in one place and reused across the platform.
ExploreSee Built-in mail on your project.
A short demo with your own drawings and data.