A commercial installation has more people involved than it first appears. On a typical project to put solar and a battery on a distribution warehouse, with chargers for the customer's vans, you might have a project manager, a designer, a purchasing lead, two or three install crews, an electrical subcontractor, a groundworks contractor, several suppliers, a manufacturer's commissioning engineer, the customer's facilities manager, their energy manager and, eventually, their service contact. Each holds part of the picture.
Coordination breaks down when that picture is scattered across inboxes, phones and spreadsheets. This article looks at who needs what on an installation, where the handoffs go wrong, and how to organise a project so that each party sees and contributes what they should.
Four groups, four sets of needs
The office. Project managers, planners, purchasing and accounts. They need to know status across every project: what is delivered, who is booked, what is complete, what is blocking.
Crews and subcontractors. They need to know where to be, what to install, how to install it, and what to record while they are there. They do not need, and often should not see, commercial details.
Suppliers. They need clear orders and clear feedback when something arrives short or damaged.
Customers. They need progress they can trust, a clear point at which to accept the work, and documentation they can find later. After handover, they need a simple way to report faults.
Good collaboration is not everyone seeing everything. It is each group seeing the right slice of one shared record.
Where installation handoffs go wrong
The same problems appear on project after project.
- Office to crew. The crew arrives with an old drawing, or without knowing the customer asked for chargers to move two bays along.
- Crew to office. A commissioning result, a snag or a shortage stays on the engineer's phone until the end of the week.
- Supplier to site. A delivery arrives short, nobody records it, and the gap is discovered on install day.
- Contractor to contractor. Groundworks finish the charger bases but nobody tells the install crew, so the booking sits idle.
- Office to customer. The customer hears about progress by phone, with no written record, and disputes what was agreed at handover.
Each one is a handoff without a shared record behind it.
One record per product, task and project
The most effective change is to stop passing information between people and start recording it in one place that each party can see according to their role.
In Integrio that record has three layers.
The project. Customer, site, scope, documents and the workflow of tasks for this type of job.
The products. Every item to be installed, with its delivery status, data points, testing form and history. See product management.
The tasks. Each step, assigned to a person or team, with instructions attached and notifications when it is ready to start.
When a crew commissions a charger, the product record updates. When the groundworks contractor completes the bases, their task closes and triggers the next one. When a delivery is checked in short, it is flagged on the schedule. The office does not need to ask; it can see.
Crews and subcontractors
Assign, do not broadcast. Tasks are assigned to the right team member or department, and automatic notifications tell the next person when their task is ready. That replaces the group chat where messages get lost.
Put the method with the task. Task instructions can hold checklists, procedures, safety requirements and quality standards, so a subcontractor installing chargers for the first time follows your method, not their habit.
Give external teams controlled access. Integrio's contractor access grants project-specific permissions, so a subcontractor can see and complete their tasks and forms without seeing other customers or pricing. See resource management.
Let them work offline. The mobile app works without signal and syncs when connection returns, which matters in switch rooms and underground car parks. See the installer's mobile app.
Suppliers
Supplier coordination is mostly about fast, specific feedback. Delivery schedules track incoming items against the project, and checking in by QR scan records exactly what arrived. Incomplete orders are flagged. When purchasing chases a supplier, they can point to the exact items missing rather than a vague "the delivery was short". If product and order data needs to reach your ERP, ERP integration avoids re-keying it.
Customers
Customers on commercial projects usually want three things: honesty about progress, a clear acceptance step and documents they can find again.
Progress. Reports produced from live project data, branded with your company details, give the customer an accurate picture without a special effort to prepare them.
Input without accounts. Forms can be shared by secure external link so a customer can complete a pre-start questionnaire, confirm access arrangements or approve a change from their browser, with no login.
Acceptance. Multi-stakeholder sign-off workflows can require approvals from the customer, your team and any other parties, with a real-time view of who has signed and what remains.
After handover. A client portal gives access to handover documentation and training materials after sign-off. Customers can scan a product's QR code with their phone to report a fault, which creates a ticket in your helpdesk against that specific item.
Meetings that use the record
Collaboration tools do not replace meetings, but they change them. A weekly project review run from the Kanban board and the delivery schedule focuses on blockers instead of status updates. A pre-handover meeting run from the sign-off view and the snag list agrees what remains rather than discovering it. A customer progress call that follows a shared report avoids arguing about what was said last time.
Putting it in place
- Map the parties on your most common project type and write down what each needs to see and to contribute.
- Set up the workflow for that project type, with tasks assigned by role and instructions attached.
- Invite subcontractors with project-specific access, and share customer-facing forms by external link.
- Move one recurring conversation, often delivery shortages or snag close-out, from phone and email into the shared record.
- After a few projects, look at which questions still arrive by phone and ask what record would have answered them.
For how coordination feeds the wider delivery of a job, see installation project delivery and construction project management.
