Connections

• Finance and payments. Agree how approved certificate values reach the system that handles contractor payment and accounting.
• Document exchange. Agree how site evidence arrives as attachments and how shared material is distributed outside the project team.
• Identity. Link each active team member to the correct platform user before assigning package ownership.

Start from the package and approved certificate that identify the reviewed work. Decide who owns the destination system and how a transferred value is checked against the original certificate number and revision. If a guarded action has an operation receipt, preserve its key and result. Keep internal attachments within their intended audience and confirm shared visibility before external distribution.