The Danger of Running Projects Through Personal Relationships
Personal relationships are valuable in construction. Trust, professional networks and experience can solve urgent problems quickly. The danger begins when the project can function only because specific individuals know whom to call, how to bypass normal channels or how to personally secure resources. What looks like agility can become unmanaged Key Person Risk.
Resource dependency map
The risk is concentration of knowledge and access, not the existence of relationships.
Personal network vs institutional network
Maturity preserves relationships while making them reproducible.
Executive Summary
A strong engineer who can secure a crane, vehicle, supplier, crew or material at short notice may protect a milestone. That intervention has real value. But if the organization depends on the same individual repeatedly, the process is not institutionalized. The project becomes vulnerable to absence, turnover, conflict of interest, inconsistent commercial terms, undocumented commitments and unequal access to information. Mature organizations capture the useful network while moving decisions and commitments into governed workflows.
Problem Definition
Key Person Risk exists when critical knowledge, authority, contacts or workarounds are concentrated in one person and cannot be reproduced by the organization. In construction, this often appears in equipment sourcing, supplier coordination, permits, logistics, subcontractor mobilization or client interfaces. The problem is not personal relationships themselves; it is the absence of an organizational mechanism behind them.
Why It Happens
Projects reward fast problem solving, so informal networks naturally develop. Formal systems may be slow, procurement may not maintain ready supplier data, plant allocation may lack visibility and emergency procedures may be unclear. Capable people then create shortcuts. Because the shortcut works, management may celebrate the result without examining why the normal system could not respond. Over time, the workaround becomes the operating model.
Typical Warning Signs
Warning signs include repeated statements that only one engineer can arrange a certain resource, supplier contacts stored in personal phones, commitments made before formal approval, project continuity dropping when a key person is on leave, external parties bypassing official channels, undocumented rates or scope agreements, dependence on personal favors and resource allocation based on relationships rather than transparent project priority.
Root Causes
Root causes include weak supplier and equipment databases, slow approval workflows, poor emergency procurement controls, missing succession plans, inadequate delegation, no shared contact history, fragmented project records and lack of organizational memory. Another cause is management tolerance of informal commitments when the outcome is favorable, even though the same behavior can create governance problems when conditions change.
Impact on Cost
Personal sourcing can sometimes reduce immediate cost, but unmanaged relationships can also create inconsistent pricing, unrecorded obligations, limited competition, duplicate commitments and weak negotiation leverage. When the key person leaves, replacement teams may have to rebuild the network. Cost risk therefore comes from both the transaction and the loss of institutional knowledge.
Impact on Schedule
Personal networks can accelerate urgent response, but they create schedule fragility if no alternative path exists. A reliable schedule should depend on controlled supplier capacity, framework agreements, resource pools, qualified vendor lists and escalation workflows, not on whether one individual can reach the right person. Resilience means the organization can reproduce the response even when staff changes.
Impact on Safety
Urgent personal sourcing can introduce safety risk if equipment, drivers, operators, subcontractors or suppliers are mobilized before normal qualification and verification are complete. Emergency procedures should preserve critical HSE and quality checks. Speed should come from prequalification, approved frameworks and known escalation paths rather than bypassing essential controls.
Impact on Productivity
When engineers become informal procurement, logistics and resource coordinators, their technical productivity falls. They also become interruption points because colleagues route more problems through them. The organization then experiences a paradox: the strongest problem solver becomes overloaded, making the project more dependent and less scalable. Institutionalizing the process returns technical staff to higher-value work.
Impact on Organizational Reputation
External parties can become uncertain about who has authority when personal relationships dominate formal channels. Suppliers may receive commitments that later require correction, and internal teams may perceive favoritism in resource allocation. Transparent governance protects both the individual and the organization by making authority, competition and decision records clear.
Case Example — Fully Anonymized
A generalized project may repeatedly rely on one experienced engineer to locate cranes and access equipment through personal contacts whenever the normal fleet is unavailable. The interventions protect work fronts, but no shared vendor register, rate history or emergency sourcing workflow is created. The lesson is that management should capture the successful network into an institutional resource rather than continue depending on the individual.
Management Controls
Create governed supplier, subcontractor and equipment networks with qualification status, capabilities, commercial framework and contact ownership. Define emergency sourcing procedures, delegation thresholds and post-event review. Require commitments to enter the official system even when the initial contact is personal. Establish role backup, succession and knowledge-transfer requirements for critical relationships.
Recommended KPIs
Track percentage of emergency sourcing through approved vendors, transactions initiated outside the formal workflow, key suppliers with multiple organizational contacts, critical roles with documented backup, supplier-response coverage, emergency procurement cycle time, undocumented commitment exceptions and recurring resources obtained through a single individual. The objective is to identify concentration, not punish useful professional networking.
Digital Controls
A digital ecosystem can maintain shared vendor profiles, equipment availability, qualification records, commercial history, resource requests, approvals and communication evidence. Contact knowledge becomes organizational rather than personal. Role-based workflows can still allow rapid emergency action while preserving approval and audit requirements. The system should support the relationship, not erase it.
Implementation Method
Create a Key Person Risk register for operational dependencies, not only senior succession. Map the activities that depend on unique contacts, undocumented know-how, unusual authority, specialist technical judgment or personal access to suppliers and external parties. For each dependency, record the business impact of absence, the secondary owner, where the knowledge is stored and what institutional control can reduce concentration. Supplier and equipment relationships should migrate into qualified vendor records with capability, geographic coverage, commercial history, HSE and quality status, previous performance and multiple organizational contacts. Emergency sourcing should still permit speed, but it should define minimum qualification checks, delegated commercial authority and a post-event formalization requirement. Critical stakeholder relationships need handover notes and meeting history inside the governed record rather than private messaging alone. The objective is not to make relationships impersonal. It is to make the value of those relationships available to the organization under appropriate permissions.
Governance Risks and Safeguards
Relationship-driven operations can create less visible governance risks: inconsistent vendor access, commitments made without authority, perceived favoritism, conflicts of interest, undocumented rate negotiations and data retained on personal devices. Controls should therefore distinguish relationship development from transactional authority. Employees may introduce or communicate with suppliers, but qualification, competition, approval and commitment should follow the governed commercial process unless a documented emergency rule applies. Periodic conflict-of-interest declarations and vendor-master reviews help protect both staff and company. Communications that materially change price, scope, delivery, safety requirements or contractual position should be captured in the official record. Management should also monitor workload concentration. The person everyone relies on may become a bottleneck or burnout risk long before resignation occurs. Cross-training, rotation and documented backup contacts reduce that exposure while preserving the individual’s professional contribution. A quarterly dependency review should also test external continuity. Ask whether critical suppliers, local service providers and specialist subcontractors are known to more than one authorized employee, whether qualification documents are current and whether framework terms remain valid. Where a relationship is commercially important, record the organizational relationship owner and an operational backup. This is especially useful during project transfer, annual leave and rapid mobilization. The organization should be able to preserve trust with external parties without allowing any single person to become the sole channel through which information, commitments or access must pass.
Lessons Learned
Personal initiative is an asset; unmanaged dependency is a risk. The correct response is not to discourage engineers from using experience and networks. It is to capture repeatable value into approved supplier pools, resource catalogues, documented workflows and shared knowledge. A mature organization turns personal capability into institutional capability.
Management Checklist
List activities that currently depend on named individuals. For each, identify what knowledge, contacts, authority or data would be lost if that person became unavailable. Confirm whether alternative suppliers, backups and system records exist. Review whether urgent commitments made through personal contacts are subsequently formalized. Any process that cannot operate during normal leave should be treated as a resilience gap.
Conclusion
Projects should benefit from professional relationships without becoming hostage to them. The strongest organizations combine human networks with transparent governance, shared knowledge and repeatable workflows. When success can be reproduced by the system rather than only by the individual, the organization has converted Key Person Risk into organizational capability.
ORQIV Insight
ORQIV’s supplier, procurement, resource and document-control concepts illustrate how relationship knowledge can be attached to governed records rather than left in private channels. The broader principle is continuity: operational history, qualification, commitments and approvals should remain available to authorized teams even when people move between roles or projects.
Move from guidance to governed workflow.
ORQIV publishes practical project-control guidance publicly while keeping customer data, proprietary algorithms and private implementation details inside the governed product boundary. Review methodology is documented in the Editorial Policy.