Integrations and source ownership

• Document storage. Agree where drawings, photographs and inspection files live. Keep stable file links and parent identifiers on the inspection evidence record.
• Identity provider. Map signed-in people to their application account and crew identity, including the process for disabling site access.
• Commercial system. If approved hours or milestone decisions feed billing, pass reviewed source references into the system that owns invoices and payment.
• Project schedule source. If another planning tool owns the programme, agree how project and package dates are imported and who resolves conflicts.

Name the owner of each source, the records sent or received and the identifier used to match them. Reconcile imported projects, people, hours and dates before a scheduled sync is enabled. A returned or duplicate event should remain visible with its source reference so the team can investigate without creating a second site record.

Give each connection only the access it needs. Keep provider credentials outside site records. Check a changed drawing link, a disabled crew member, an amended project date and a corrected timesheet in a pilot before extending the connection to other sites.

Use the implementation plan to agree the first handoffs.