Construction

Inventory project-management systems, building information models, drawings, estimating files, schedules, and contractual records. Identify who owns each repository and how teams confirm they are using the current approved version. Include subcontractor portals and local copies used when connectivity is limited.

Librarian can help organize systems and project ownership. Cerberus can support approved data-handling workflows, but access restrictions should reflect actual project roles and confidentiality commitments. Review sharing when a subcontractor completes its work or when staff move between projects, rather than waiting for the entire project to close.

• Keep protected copies of critical project records.
• Expire temporary links and remove unnecessary external project members.

A convincing invoice or compromised project mailbox can redirect a legitimate payment. Establish a separate process for changes to banking details, with verification through an existing trusted contact and approval by authorized staff. Apply the process consistently to mobilization payments, progress claims, and final settlements.

Plutus and Psycher can support review of suspicious instructions. They should reinforce, not replace, independent callbacks and segregation of duties. Staff need explicit permission to delay a payment when verification fails, even if the request appears to come from a senior project leader.

• Keep supplier master-data changes separate from routine invoice approval.
• Record who verified the change and which trusted channel was used.

Manage mobile devices, site Wi-Fi, remote access, and shared equipment with practical controls. Separate guest connectivity from business systems and revoke access when devices are lost or workers leave. Confirm who supports temporary site technology and how it is retired at project completion.

Horsemen can support managed-device work within agreed coverage, while Dewey can assist with response planning. Human owners must approve consequential actions and site-impacting containment. Exercise a scenario where project files and email are unavailable, then verify how teams obtain safe, current instructions and preserve records of work completed.

• Test restoration of an active project's essential files.
• Keep incident contacts accessible to site supervisors without corporate email.