Based on current ACC functionality and help documentation:
- No robust reporting capability exists to analyze correspondence that has been sent (e.g., by date, type, sender, recipient, or status).
- Correspondence Types are static and limited, offering minimal configuration beyond basic categorization.
- No ability to “Send on Behalf Of” another role (e.g., Document Control, Project Manager, or JV entity), which is a common requirement on large construction projects.
- No templated message content tied to correspondence types, resulting in inconsistent messaging and increased administrative effort.
These limitations create real project risks and inefficiencies:
- Lack of auditability: Teams cannot easily demonstrate what formal correspondence was sent, when, and by whom.
- Inconsistent communication: Without templates, similar correspondence varies by sender, increasing contractual and claims risk.
- Administrative bottlenecks: Document Control teams must rely on workarounds (manual logs, exports, or parallel systems).
- Reduced adoption: Teams revert to email or external tools when ACC does not support required correspondence workflows.
Proposed EnhancementsCorrespondence Reporting
- Enable reports and exports for:
- Sent correspondence
- Correspondence by type
- Sender / recipient
- Date ranges and status
- Align reporting behavior with other ACC modules (e.g., RFIs, Submittals).
Enhanced Correspondence Types
- Allow administrators to:
- Configure correspondence types with required fields
- Assign default recipients
- Enforce naming or numbering standards
“Send on Behalf Of” Capability
- Permit authorized users to send correspondence on behalf of:
- Project roles (e.g., Document Control)
- Companies or JV entities
- Maintain full audit history showing the actual sender and delegated role.
Templated Message Content
- Allow message body templates tied to correspondence types.
- Support placeholders (project name, reference numbers, dates).
- Improve consistency and reduce repetitive manual entry.
