RELATED IDEAS
TRANSMITTALS OPTIMIZATION
Traceability, Permissions, and Audit Implications
To send a Transmittal, the record must be locked, which prevents anyone else—even users with permissions—from modifying it.
While locking protects the record before sending, the workflow does not allow reliable recipient confirmation (acknowledgment) without either unlocking the record (which alters a sent document) or performing external follow-up (phone call, chat, emails).
If a Transmittal is sent unlocked, there is no authorship discrimination; any user with Transmittals permissions can access and modify any record.
Notifications and Internal Alerts
ProjectSight currently does not notify recipients when a Transmittal is sent within the platform.
Ideally, notifications should function internally within the platform, similar to an assignment or task, to ensure user awareness.
Without internal notifications, external follow-up (phone call, chat, emails) is required to confirm receipt.
It would be beneficial for the transmittal module to function similarly to an email system, enabling users to send and respond to correspondence directly within the platform. This would improve correspondence traceability, rather than relying on the module solely as a record-keeping tool.
