The current correspondence workflow is useful as a central email archive, but for real project execution it needs stronger process-based grouping.
A construction project does not only contain general communication. It contains orders, defects, change requests, RFIs, technical clarifications, additional works, offers, approvals, billing topics, and many other project-related processes.
For this reason, incoming project emails should not only be stored under the project. They should be assignable to a correspondence type or process group, and the system should generate a unique ID for that group.
Example:
All replies should remain connected to the same correspondence ID, so the full communication history is grouped by process and not only by email thread.
This should work not only when emails are uploaded manually via drag and drop, but also for emails received through the project email address. Ideally, this could be handled by rules, keywords in the subject, different project email addresses per correspondence type, or a review step where new incoming emails can be classified.
For contractors and field teams, this would turn Correspondence from a simple email archive into a real project communication register.
