From Site Survey to Proposal: How Solar EPCs Can Automate BOQ and Estimation

2026-09-08

This is Part 2 of our series breaking down the 7 operational modules from The Complete Guide to Solar Business Management Software (2026) - this piece goes deeper on the second: Site Survey, BOQ & Proposals.

A site survey can be completed correctly and the final proposal can still be wrong.

The problem often occurs between the field engineer and the office estimating team. Measurements may be written down, photographs remain on a phone, shading observations arrive through WhatsApp, and technical details are manually transferred into Excel.

One missed measurement or incorrect module count can then affect the Bill of Quantities (BOQ), Balance of System (BOS), Module Mounting Structures (MMS), cabling, and project margin.

For a C&I Solar EPC, the site survey should not be treated as a separate activity from estimation. It is the starting point for the technical and commercial information that eventually shapes the project.

Fixing this isn't about second-guessing the field engineer's judgment - it's about making sure what gets captured on site doesn't get lost in translation on the way to a quotation. ERP Consulting Group helps Solar EPC teams connect that survey data directly to BOQ generation and procurement, so a proposal reflects what's actually available and cost, not just what the design called for.

The Real Cost of an Incorrect BOQ

A BOQ error rarely stays inside the quotation. If the module count is incorrect, related requirements such as MMS, cables, connectors, protection equipment, and installation effort can also change.

A missing BOS component may look insignificant during proposal preparation but become a real procurement cost after the customer has accepted the quotation.

The problem becomes more expensive when the EPC has already committed to a project price. At that stage, correcting the requirement may mean absorbing the additional cost, negotiating a variation, or delaying procurement.

The same issue applies to inconsistent pricing. If different sales teams use separate spreadsheets, they may work with different material costs, discounts, or margin assumptions. A centralized workflow can establish common pricing rules and approval controls.

The objective is not to make every quotation identical. It is to ensure that differences are controlled and commercially justified.

Why Design Software Alone Is Not Enough

Specialized tools such as PVsyst and AutoCAD remain important for solar engineering. But technical design alone does not answer a critical commercial question: can we actually procure and deliver this configuration at the cost assumed in the proposal?

A design may specify particular modules, inverters, MMS, or BOS components while procurement is dealing with different supplier prices, availability, lead times, or warehouse stock. If these systems remain disconnected, the estimator can produce a technically sound proposal using commercially outdated information.

A connected system can link the proposal workflow with procurement and inventory information - moving the question from "What does the design require?" to "What will this project actually require, cost, and need from procurement?"

Building a Connected Survey-to-Proposal Workflow

The goal is to connect the information created during pre-sales with the wider business workflow, rather than treating the survey, BOQ, quotation, and procurement process as separate activities. Below is what that looks like in practice.

Native Digital Field Capture

The field team can capture relevant survey information against the customer or opportunity instead of relying on paper notes and scattered messages. This can include measurements, photographs, electrical requirements, shading observations, and supporting drawings.

The objective is simple: capture important information once and make it available to the next team.

Dynamic Automated BOQ Generation

Survey and design inputs can feed the estimating workflow, helping create a structured BOQ covering modules, inverters, MMS, cabling, protection equipment, and other BOS requirements.

When the technical configuration changes, the commercial workflow can be updated without rebuilding the entire proposal from separate spreadsheets. This creates a connected chain:

Margin Protection

A technically accurate BOQ does not automatically guarantee a profitable project. Material costs, stock availability, procurement prices, labour assumptions, and project-specific requirements all influence the final margin.

Connecting the estimating process with procurement and inventory information gives the team an opportunity to identify cost or availability issues before the proposal is committed.

Legacy Spreadsheet vs. Connected Workflow

Process

Manual Spreadsheet Model

Connected Workflow

Site survey

Paper, phone, WhatsApp

Digital record linked to opportunity

Measurements

Manually transferred

Structured survey information

Photos & drawings

Scattered across devices

Connected to project record

Shading data

Manually interpreted

Captured with survey information

BOQ

Created separately

Connected to project inputs

BOS components

Risk of omissions

Structured material requirements

Pricing

Different spreadsheets

Centralized pricing controls

Stock

Checked separately

Connected inventory visibility

Proposal revision

Multiple file versions

Updated within workflow

Margin

Estimated manually

Connected to material costing

Handover

Information recreated

Proposal data continues into execution


Executive Summary

Capture once: keep site measurements, technical information, documents, BOQ, and proposals connected.

Protect margins: centralized pricing and procurement visibility reduce costly estimation errors.

Connect execution: carry accepted BOQ information into procurement and project mobilization.

The real value is not simply producing a proposal faster. It is creating continuity between what the engineer observes, what the estimator calculates, what sales promises, and what procurement and projects eventually deliver.

Deep-Dive FAQ

Can engineering teams still use PVsyst or AutoCAD alongside Odoo?

Yes. Odoo does not need to replace specialist engineering software. PVsyst, AutoCAD, and similar tools can remain part of the technical design process, while relevant project information, drawings, reports, and outputs are connected to the ERP through integrations or document management.

The goal is: Site Survey → Odoo Opportunity → Engineering Design → Technical Output → BOQ → Proposal.

This keeps engineering teams in their preferred tools while giving sales, procurement, and project teams visibility into the information they need.

How does centralized pricing prevent inconsistent quotations?

Instead of allowing every salesperson to maintain their own pricing spreadsheet, a connected system can centralize product costs, pricing structures, discounts, margins, and approval rules.

Management can establish pricing guardrails and minimum margin parameters. A salesperson can still negotiate, but exceptions can require approval instead of silently reducing project profitability. This creates a controlled relationship between:

Purchase Cost → Selling Price → Discount → Margin → Approval.

Can field teams work from remote sites without the internet?

This depends on which part of the workflow you mean, and it's worth being precise about it rather than giving a blanket yes. Odoo's Point of Sale module has genuine, well-established offline support. For custom field workflows - like a mobile site-survey form - offline reliability typically depends on how that specific workflow was built, and often needs deliberate configuration or a dedicated offline-capable module rather than working offline automatically out of the box.

The honest version: offline field capture for a solar site survey is achievable, but it's an implementation decision to plan for up front, not a default guarantee - confirm exactly what's supported for your specific workflow with whoever is building it before relying on it in the field.

What happens to the BOQ after the customer accepts the proposal?

The BOQ should not become a dead quotation document. Once the proposal is accepted, the relevant technical and commercial information can move into project execution. Depending on the configured workflow, material requirements can feed procurement planning while project tasks can be created for the teams responsible for mobilization and execution.

The intended chain is:

Proposal Accepted → Project Created → BOQ Confirmed → Procurement → Task Dispatch → Mobilization.

This reduces the need to recreate the same project information across departments.


Ready to Connect Your Site Survey to Project Execution?

ERP Consulting Group  can help map your existing site survey → BOQ → proposal → procurement → project workflow, using RENEWvate, our Odoo-based tool for renewable energy operations, to identify where manual handoffs are costing you accuracy and margin.

Start with your process, not a generic software demo -Book a Free Strategy Session or email info@erpconsulting24.com.

This article is part of our Complete Guide to Solar Business Management Software (2026) - read the full guide for the other 6 modules, including lead pipeline management, subsidy tracking, and GST-compliant invoicing.