The single biggest predictor of whether a solar EPC will scale past 50 projects/month is whether their field engineers actually use the company software, or whether they fall back to WhatsApp by lunchtime on day one. We've seen it dozens of times. The pattern is the same: the office team picks a tool that looks great on a 27-inch monitor, the field team rejects it within a week, and the company gives up — and loses every visibility benefit a CRM was meant to provide.

This article is a checklist of what your installation team should be capturing on every visit, AND the requirements your software must meet for them to actually do it.

What engineers must capture — at every site visit

Survey visit

  • 4 directional rooftop photos (N, S, E, W)
  • Existing electricity meter photo (with consumer number visible)
  • Available roof area in sq ft (paced or measured)
  • Shading observations (water tank, neighbour's wall, trees)
  • Roof type (RCC, sheet, tile)
  • Distance from roof to meter for cabling
  • Customer's signed survey acknowledgement
  • Estimated kW capacity

Material delivery day

  • Pallet photos with serial numbers visible
  • Inverter serial plate
  • Structure component count vs. BOM
  • Damaged item photos (if any)
  • Customer's "received" signature

Installation day

  • Pre-install rooftop "before" shot
  • Structure mounting photos (anchor bolts, base plates)
  • Panel laying photo per row
  • Earthing pit with measuring tape visible
  • AC and DC cabling routes
  • ACDB / DCDB box internals
  • MCB ratings close-up
  • Final 4-angle "after" shots
  • Inverter standby light + display
  • Net-meter location photo

Commissioning day

  • First-day generation photo (kWh display)
  • Customer training photo (engineer + customer)
  • Handover document signature
  • Single Line Diagram (SLD) on site

Capturing all of this on every project sounds like a lot — and it is. The total photo count for a typical 5 kW residential install is 30–40 photos. Multiply by 50 projects a month and you have 1,500–2,000 photos that need to be (a) taken, (b) tagged to the right project, (c) accessible 6 months later when the inspector asks.

Doing this in WhatsApp is impossible. Doing this in a CRM that wasn't built for mobile-first capture is also impossible. The CRM must meet these requirements:

The 8 mobile-first software requirements

  1. Opens in under 3 seconds on a Vivo Y-series. Half your engineers are not using flagship phones.
  2. Camera capture from inside the project page. The engineer should NOT have to switch apps. One tap → camera → photo → photo lands in the project gallery with stage tag and GPS already set.
  3. Offline-first storage. Most rooftops have terrible connectivity. Photos and notes captured offline must queue and sync automatically when the engineer is back in 4G range.
  4. One-handed UI. Big tap targets (≥ 48 px). No tiny dropdowns. The engineer's other hand is holding a panel, a screwdriver or themselves.
  5. Stage-aware checklists. When the engineer opens a project at the "Installation" stage, they should see the installation checklist — not the survey checklist.
  6. Push notifications for new task assignment. No more office calls saying "Karthik, the customer in JP Nagar is calling, why haven't you started?"
  7. Barcode scan for stock movements. When the engineer takes 3 panels off the truck for project X, they scan the carton, type 3, done. No data entry on a 5-inch keyboard.
  8. Hindi (or Tamil, Telugu, Marathi…) support. Your engineers may not be comfortable in English. If your software is English-only, expect the photos to never get taken.

How SolarIonix delivers

SolarIonix's Flutter mobile app is built around exactly these 8 requirements. Photos are automatically tagged to the correct project and stage, GPS-stamped, and offline-first synced.

The result: when a DISCOM inspector asks "show me the cabling photos of this project from 3 weeks ago", the answer is a 4-second tap. Not a 20-minute WhatsApp scrollback.

See the mobile field app →