Project Collaboration and Data Governance

This Schedule supplements the SiteAxis B2B SaaS Master Services Agreement and Order Form for a shared construction or infrastructure Project. It addresses multi-company workspaces where owner/client organizations, general contractors, contractors, subcontractors, consultants and inspectors collaborate. It is not itself a construction contract, delegation of statutory duties or assignment of underlying IP/evidence rights.

Project/workspace: To be confirmed: project name and identifier · Sponsor: To be confirmed: project sponsor organizations · Participating entities: To be confirmed: participating organizations · Authority model: To be confirmed: customer project authority model.

1. Organization-level and record-level responsibilities

1.1 A Project Sponsor is the organization identified in the signed Order and authorized by its applicable project agreements to establish the workspace, invite eligible participants and define shared rules. Where the real-world project owner and subscription payer differ, sponsor designation must explain the source of authority.

1.2 A Participating Organization remains legally distinct. It may appoint representatives for work it controls, and exercise user and record permissions expressly assigned by the Sponsor and permitted by Project agreements. A construction subcontractor's parent-child association with a contractor does not establish independent contractual authority to control every workspace record.

1.3 A Project Administrator manages configuration and access only within the authority actually delegated to that organization and role. The software's "Company Admin" or "Project Admin" permission is a technical control, not an assignment of IP, ownership of all project evidence, or power of attorney for a separate company.

1.4 Each record may have a contributing organization, author, source, reviewing/approving organization, visibility scope and record custodian as described in To be confirmed: project record rights matrix. Absent express agreement, display in a shared workspace does not transfer copyright or waive confidentiality.

2. Agreed project governance matrix — mandatory before shared-project contracting

3. Sharing and access

3.1 The Project Sponsor will specify initially authorized companies, available module access, personnel classifications, required MFA, location/sublocation and contractor/subcontractor association rules, and use of distribution lists/notifications. Technical selection controls do not expand the rights granted under the applicable agreements.

3.2 Changes to assigned companies, projects or participants must remain within the lawful authority of the instructing party and the agreed access model.

3.3 The Sponsor and participating companies must agree which classes of records are shared, restricted to the originating organization, available to regulators/owner representatives, or eligible for external transmittal. Photographs, injury/witness information, personnel details and financial/commercial terms may require narrower access than ordinary progress reports.

3.4 A Project user must not use an invitation, linked record or export to circumvent another organization’s confidential record restrictions. SiteAxis may suspend unauthorized sharing pending identity/authority verification, with proportionate notice where lawful.

4. Operational evidence and record integrity

4.1 Project participants remain responsible for inspecting, verifying, signing, approving and issuing the substantive contents of submitted records, including permit status, corrective actions, schedule activity links and commercial notices. Platform-generated numbers, timestamps, PDF reports, signatures or automated classifications do not alone determine legal notice effectiveness or evidentiary admissibility.

4.2 Records may be corrected, superseded, archived or voided through auditable workflows; whether a particular record is immutable, signed or an authoritative original must be set out in To be confirmed: record provenance and evidence rules and actually implemented. No legal evidence-destruction rights are granted by a generic UI Archive action.

4.3 Each Party shall avoid entering sensitive data beyond what is needed, especially in safety incidents and witness statements. To be confirmed: allowed injury data scope establishes permissions and retention for legitimate incident processing.

5. Onboarding, invitations and termination

5.1 Sponsor designates the invitation authorities; a participating company may administer only its agreed individuals and data. Invites can expire, be revoked or require verification, but a specific invitation expiry period is not a contract term unless expressly set in To be confirmed: invitation terms.

5.2 On participating-company withdrawal, SiteAxis may revoke active access while retaining audit history and records required by other participants or law. Ownership and export rights are governed by the matrix, not by UI state. An outgoing organization may request copies of records it lawfully controls within To be confirmed: participant exit export rights.

5.3 Ending a subscription or deleting a tenant does not authorize destruction of legitimately shared Project evidence. The Parties will agree which successor custodian can hold legally retained files and whether any paid transition services are needed, as To be confirmed: shared project retention policy.

6. Disputes, legal holds and project transition

6.1 On conflicting instructions over rights to preserve, access, export or delete records, SiteAxis may temporarily restrict changes to the disputed dataset and require documented consensus from legally authorized entities, a governing project contract provision or an enforceable order. Emergency safety access and regulator duties must be assessed separately.

6.2 The Parties will promptly designate a dispute contact and cooperate in good faith. SiteAxis shall not choose winners in underlying construction contract, employment or insurance disputes. Project transfer to a replacement GC, owner or construction management provider requires an authorized change instruction, privacy assessment and access review.

6.3 Records subject to judicial/regulatory holds, open insurance claims, injury investigations, litigation or statutory construction retention obligations may be preserved only as reasonably needed and with restricted access. The hold origin, scope and review date shall be recorded.

7. Control owner and acknowledgement

Sponsor authorized representative: To be confirmed: project sponsor signer · Project records custodian: To be confirmed: project records custodian · Security/privacy reviewer: To be confirmed: customer privacy contact · SiteAxis account manager: To be confirmed: siteaxis account manager.

Signatures/approval or signed Order incorporation: To be confirmed: project schedule execution status.