Skip to Main Content
Need Support? Let’s guide you to the right answer or agent.
Status Future consideration
Created by Guest
Created on Sep 26, 2023

Remove ack required to view attachments in General Correspondence

Remove the requirement for General Correspondence to be acknowledged by all recipients marked "ack required" in order to view attachments, or enable a delegate function.

Practical use of functionality?

Other members of the same organisation should be able to view the General Correspondence (non-contractual correspondence) and the attachments without waiting for ALL recipients with an ack required (which can be 1 or many) - this is the same setup in systems like Aconex and InEight.

Where contractual or sensitive information is being shared, a CONFIDENTIAL General Correspondence should be employed controlling the audience of that information. A delegate option should also be available to acknowledge Confidential General Correspondence in the event a receiver is on leave or not available.

What is the impact of not doing this?

Currently users are unable to view attachments on General Correspondence if they are not an included recipient and the package has not been acknowledged by ALL recipients marked as acknowledgement required. There is not even an option to delegate so if someone is on leave and another user needs to view the attachments and were left off the correspondence, the attachments cannot be viewed causing unnecessary delays to the sharing of information.

  • Guest
    Reply
    |
    Apr 23, 2024

    Is there anyway this idea could be escalated? We are having HUGE time delays on having to wait to download attachments on a General Correspondence because an individual has not acknowledged the package. Even a delegate option would be an ideal immediate work around as currently my project team are operating days behind just to view and attached letter.

  • Guest
    Reply
    |
    Dec 6, 2023

    An even better alternative would be to set up the General Correspondence in a similar format to the RFI form with a TO and CC field, which doesn't require an acknowledgement required for other internal project team members from seeing the correspondence and attachments.