Contractor to Company - created by contractor

Contractor to Company communications can be created in the Contractor Portal by contractor users with the following contract roles :

• Contractor Representative

• Contractor Administrator

• Contractor Information Management (communications with non-confidential information only - see Contract roles)

A typical lifecycle of a Contractor to Company communication which has been created by the contractor is:

1. The communication is created in the Contractor Portal by a contractor user.

2. The communication is saved as Draft.

3. The communication is published/sent to the company, i.e. it becomes visible on the Company Portal.

4. The routing workflow is automatically started for the communication. This can include reviews internal to the company.

The following diagrams show more detailed workflows.

Communication requires agreement

Example: The contractor sends a communication to the company; the company must confirm that they either agree or disagree with the communication.

The Required Response option of the communication template is set to Agreement Only or Agreement and Reply.

The possible communication states of a Contractor to Company communication, created by the contractor, which requires agreement are:

• Draft

• Awaiting Agreement from Company

• Agreed

• Not Agreed

• Rejected

  Note For a communication which requires Agreement and Reply, the process time limit in the following diagram is the time in which the agreement and the reply must be made.

Communication does not require agreement

Example: The contractor sends a communication to the company for their records.

The Required Response option of the communication template is set to None or Reply Only.

The possible communication states of a Company to Contractor communication which does not require agreement are:

• Draft

• Approved

• Rejected