Your solar designer just sent a WhatsApp message — one month notice. You have four rooftop projects at different design stages, a DISCOM submission due in eleven days, and a bid tender that needs a PVsyst report by Friday. Every EPC founder who has scaled past three designers has faced this moment. Most wing it and lose two to four weeks of project momentum. The ones who recover fast do so because they have a protocol, not because they panicked less.

Direct answer. When a solar designer quits, the first 72 hours determine whether active projects slide by days or by months. Audit all open work-in-progress files immediately, identify which deliverables are at a critical handover risk (DISCOM submission, bankable PVsyst, stamped SLD), and engage a qualified outsourcing partner on the same day to cover the gap. The average designer notice period in India is 30–45 days, but DISCOM deadlines do not wait. A structured four-phase Designer Exit Protocol — Triage, Handover, Bridge, Rebuild — can protect every live project with zero client-facing delays.

This playbook is written for Rohan — the Indian C&I EPC founder managing 4–15 designers across 10–40 simultaneous projects, where one departure at the wrong moment can create a cascade of missed deadlines, unhappy clients, and lost deposit revenue. Whether your designer resigned out of frustration, got a better offer, or is simply relocating, the protocol below applies the same way.

The 72-Hour Triage — What to Do the Moment You Hear the News

The first three days after a resignation set the trajectory for everything that follows. Most founders spend day one in disbelief, day two trying to negotiate a retention, and day three realizing neither worked. Use those 72 hours differently.

Hour 0–4: Freeze the file environment. Before anything else, ensure the departing designer cannot delete, move, or take project files. If your team uses Google Drive or a shared NAS, revoke edit permissions immediately — keep read access so the handover works, but disable write and download privileges on CAD files and PVsyst project folders. This is not about distrust; it is about version control and protecting client data.

Hour 4–24: Complete a full work-in-progress audit. Pull every active project the designer owns and categorize by criticality:

Project StageCriticalityRisk If Delayed
DISCOM submission within 14 daysCriticalCustomer penalty clause, lost deposit
PVsyst report for lender / investorCriticalLoan disbursement delay
Bid-stage drawing for tenderHighMissed bid window, lost order
IFC-stage design in progressHighConstruction delay, LD exposure
Pre-design / feasibilityMediumSales timeline slip
As-built / post-designLowCommissioning minor delay

Hour 24–48: Initiate bridge coverage. For every project in the Critical or High bucket, contact an outsourcing partner on day two — not day fifteen. The handover file package from the departing designer is still fresh, the project context is available, and you have time to brief properly. Waiting until the last week of the notice period makes every handover messier, costlier, and slower.

Hour 48–72: Schedule the structured knowledge transfer. Block two to three hours of the designer’s final working weeks for a documented handover session per critical project. Record the session if possible. The handover file should include: the PVsyst .PAN and .VCi files, the AutoCAD .DWG with all layers named correctly, the DISCOM format used, any DISCOM-specific comments from previous submissions, the string sizing rationale, and the equipment schedule from the BOQ.

Watch out. A designer who gives notice without a formal handover file is not being malicious — they may simply not know what to hand over. Give them a structured checklist (the one in this article) during the first week of the notice period, not the last. A rushed handover on the final Friday produces incomplete files that take your next designer twice as long to unpick.

The Designer Exit Protocol — The 4-Phase TERR Framework

Every EPC firm that runs three or more designers needs a standing protocol for designer exits. The TERR Framework — Triage, Extract, Replace, Rebuild — converts a crisis into a managed transition.

1

Triage (Hours 0–24)

Freeze file access, run the WIP audit table, classify all open projects by criticality tier, and identify which ones have deadlines inside the notice window. This is a spreadsheet exercise, not an emotional one — complete it before any conversation about retention or replacement.

2

Extract (Days 2–7)

Run structured knowledge-transfer sessions for each Critical and High project. Use a standard handover checklist (see below). Record every session. Capture the DISCOM format notes — these are the hardest institutional knowledge to reconstruct because they are often tribal, learned through rejection notices.

3

Replace (Days 2–14, parallel to Extract)

Engage an outsourcing partner on day two for bridge coverage of Critical projects. Begin a parallel recruitment process for a permanent hire if the WIP volume demands it — but do not let recruiting timelines dictate project timelines. The bridge partner should be fully operational within 48 hours of the first brief.

4

Rebuild (Days 14–60)

After the immediate crisis is resolved, conduct a post-mortem: why did this designer leave, what institutional knowledge left with them, and what structural change prevents the next exit from becoming a crisis? The answer usually involves either better documentation standards, a partial outsourcing relationship, or both.

The Handover Checklist — What Files You Actually Need

A designer resignation is only damaging when the project files are not ready to be handed off. The following checklist covers the minimum viable handover package for each project type.

For a rooftop project (DISCOM submission or IFC stage):

  1. AutoCAD .DWG with all layers named and purged — no external references unless shared
  2. PVsyst .PAN (panel) and .VCi (variant) files, plus the .PRJ project folder
  3. DISCOM submission format used — which version, which state circle, which DISCOM officer’s name if known
  4. BOQ Excel with formula-linked cells and equipment model numbers, not just final totals
  5. String sizing rationale — DC/AC ratio, number of strings per MPPT, wire sizing calculation basis
  6. Structural assessment note or STAAD Pro report if the project required it
  7. Any previous DISCOM rejection notices and the corrections made

For a utility-scale or ground-mount project:

  1. PVsyst .PRJ folder including terrain horizon profile files
  2. Layout DWG with GCR, inter-row spacing, and inverter block assignments
  3. Civil drawing package — pile layout, foundation dimensions, road plan
  4. Electrical one-line diagram (SLD) with equipment ratings and protection settings
  5. Yield report (.PDF) and all underlying assumption sheets
  6. Tracker selection rationale and shadow analysis methodology notes
  7. Lender / IREDA submission status and any open queries

Definition. A "handover-ready" project file is one where any qualified engineer at an outsourcing firm can open the files, understand the design intent, and continue work without a briefing call. Achieving handover-readiness before a resignation happens — as a standing documentation standard — is the highest-ROI thing a growing EPC firm can do.

How to Brief an Outsourcing Partner in Under an Hour

When you engage an outsourcing firm during a designer crisis, the quality of your brief determines how fast they can deliver. A disorganized brief produces a first draft that misses the DISCOM format, misses the string sizing basis, and wastes three days of revisions.

The fastest brief format is a voice note plus a file drop. A three-minute WhatsApp voice message with the following five points, followed by a shared Drive link with the handover files, is enough to get a qualified outsourcing engineer started:

  1. Project type and scale — “3-phase rooftop, 250 kW, industrial factory, Rajkot”
  2. Stage of design — “SLD is 60% complete; BOQ is done; DISCOM format not started”
  3. Hard deadline — “UGVCL submission is due in 11 working days”
  4. Equipment already decided — “Waaree 545W bifacial, ABB inverters (model in BOQ), Mounting: East-West, flat roof”
  5. DISCOM format notes — “Previous UGVCL submission was 2024; format has changed; they now require single-line in A3 portrait with the net meter spec on a separate sheet”

With those five points and the files, a professional outsourcing firm can begin work within 24 hours and deliver a DISCOM-ready drawing package in three to five working days for a standard rooftop project.

Field tip. Share your DISCOM format reference file from a previous successful submission — this single file saves more revision cycles than any other element of the brief. If you do not have one, ask the outsourcing firm whether they already have your DISCOM format on file.

What the Notice Period Math Actually Looks Like

The standard employment notice period in India’s solar sector is 30–90 days depending on the seniority and the employment agreement. According to Mercom India’s 2025 solar engineering workforce report, the average effective notice period (the time before the designer actually stops working) is 21 days — well below the contractual 30 days in most cases. Bridge to India’s 2025 market report identifies designer attrition as the top operational risk cited by C&I EPCs in the 5–50 MW annual volume segment. Here is what actually happens during that window versus what should happen.

WeekWhat Usually HappensWhat the TERR Protocol Requires
Week 1Founder in denial; retention conversations; no project actionTriage + file audit complete; outsourcing partner briefed on Critical projects
Week 2Internal debate about replacement — hire vs outsourceExtract sessions complete for Critical and High projects; bridge partner delivering first drafts
Week 3Panic as deadlines approach; rushed handover on FridayBridge partner in full flow; permanent replacement shortlisting begins
Week 4Designer leaves; files partially handed over; team scramblesClean handover complete; all Critical projects delivered or on track; permanent hire interviewing

The delta between those two columns is two to four weeks of project delay, plus client communication damage, plus the LD risk if your client contract has delay penalties. The TERR Framework converts that delta to near-zero.

34%

Annual attrition rate

Solar design roles, India, Mercom India 2025

18 days

Average project delay post-resignation

Heaven Designs client intake surveys, 2025

₹1.8–4.2L

Cost per unplanned exit

Recruitment, delay, rework combined

72 hrs

Critical response window

After which project delay risk increases 3×

Hiring vs Outsourcing — The Decision You Face on Day One

The moment a designer resigns, you face two simultaneous decisions: how to cover the gap now, and whether to replace them permanently. These are separate decisions and should be treated separately.

REPLACE WITH IN-HOUSE HIRE

  • Design volume is stable and predictable (8+ projects/month consistently)
  • DISCOM format expertise is highly state-specific and requires repeated interactions
  • Client relationship requires a named designer on calls
  • You already have a strong employer brand and low attrition track record

MOVE TO OUTSOURCING

  • Design volume fluctuates by 40%+ between peak and off-season
  • You have lost two or more designers in the last 18 months
  • Project types are diverse (rooftop + ground-mount + CEIG + structural)
  • You want to remove the single-point-of-failure risk permanently

The in-house vs outsource decision is covered in depth in our guide to in-house versus outsourced solar design for Indian EPCs and the solar designer salary benchmarks for India. The short version: for most EPCs with fewer than 20 projects per month, a hybrid model — one senior in-house coordinator plus an outsourcing bench — is more resilient than a fully in-house team of three to five.

Need bridge coverage for active projects right now?

Heaven Designs can take a handover brief today and deliver DISCOM-ready drawings or a bankable PVsyst report within 3–5 working days. We work with your existing files and formats.

Get bridge coverage now →

How to Prevent the Next Exit from Becoming a Crisis

The real fix is upstream of any individual resignation. EPCs that never have a designer-exit crisis are not EPCs with zero attrition — India’s solar sector simply does not allow that. According to SEIA’s Solar Means Business 2025 report, US installers who use outsourcing for design report 40% lower pipeline disruption from staffing changes than firms that rely solely on in-house design teams — a pattern that mirrors what Heaven Designs observes across Indian C&I EPCs. The PV Magazine India 2025 workforce analysis similarly found that EPCs with at least one outsourcing partner maintain 95%+ project on-time delivery even through designer transitions. They are EPCs with three structural safeguards in place.

Safeguard 1: Documentation standards. Every project file must be handover-ready at all times, not just when someone resigns. This means named layers in every CAD file, a PVsyst project folder that includes the .PAN and .VCi files (not just the PDF report), and a brief design-rationale note for every non-standard design choice. This takes five to ten minutes per project and saves days of reconstruction.

Safeguard 2: Outsourcing relationship pre-established. The worst time to evaluate an outsourcing partner is during a crisis. Establish a relationship with one or two qualified firms before you need them — run a small project through them, verify their DISCOM format knowledge, confirm their turnaround. When the next resignation happens, you can brief them same-day.

Safeguard 3: No single-designer projects. For any project above 500 kW or with a critical client relationship, ensure that at least two people — whether in-house or outsourced — understand the project status. The “bus factor” in solar design is real: one resignation should not be the thing that stops a ₹2 crore project in its tracks.

The ultimate guide to outsourcing solar design covers the evaluation framework for finding an outsourcing partner that can serve as a reliable second bench. The how to outsource solar design playbook has the specific briefing templates and SLA checklist.

How Heaven Designs Helps

When an EPC reaches Heaven Designs during a designer exit — and approximately 30% of our new client enquiries come in exactly this context — we begin with a ten-minute WhatsApp intake call to assess the project urgency, then dispatch a senior engineer to review the handover files within four hours. We have worked with files in every state of completeness, from a fully documented PVsyst project ready for final report generation to a partial AutoCAD DWG with no layers named and a verbal brief.

Contact us with a project brief and we will confirm a start date within 24 hours.

FAQ

What should I do in the first 24 hours after a solar designer resigns?

In the first 24 hours, complete two actions in parallel: freeze file access permissions so no project files can be deleted or moved, and run a full work-in-progress audit across all active projects. Classify every project by criticality — anything with a DISCOM submission, lender report, or bid tender deadline inside the notice period is Critical. Contact an outsourcing partner on day one for Critical projects. Do not wait until week three of the notice period to engage external coverage.

How long does it take to onboard a replacement designer?

A fresh in-house hire takes four to eight weeks to become independently productive in most Indian EPC environments — longer if they need to learn your DISCOM format requirements or a new software stack. An outsourcing partner with existing DISCOM format knowledge can begin delivering on day two or three of engagement. For an EPC with active critical deadlines, outsourcing is the faster bridge regardless of the long-term replacement decision.

Can an outsourcing partner pick up a half-finished PVsyst simulation?

Yes, provided the handover files are complete. The critical requirement is the .PAN and .VCi files (the panel and variant configuration files), the .PRJ folder, and a note on the simulation assumptions — GCR, tilt angle, soiling loss, and bifacial gain model if used. A qualified outsourcing engineer can pick up from any stage of a PVsyst simulation with those files. If the designer only left a PDF report and no source files, the simulation must be rebuilt — which adds two to three days.

Should I replace the designer with another in-house hire or switch to outsourcing?

This depends on your project volume and variability. If you run more than ten complex projects per month consistently, an in-house designer with outsourcing backup makes sense. If your volume fluctuates by 40% or more between peak and low season, a partial or full outsourcing model is more cost-effective. The hidden cost analysis of in-house solar design has the full ₹/project comparison.

How do I prevent losing project knowledge when a designer leaves?

Establish documentation standards before any resignation happens. Every project folder should contain named CAD layers, source PVsyst files (not just PDFs), a string sizing rationale note, and the DISCOM format reference used. If you treat every project as if it will need a handover tomorrow, actual handovers take hours instead of weeks.

What is the average notice period for solar designers in India?

The most common notice period in India for mid-level solar engineers (2–5 years experience) is 30 days, with some senior contracts requiring 60–90 days. In practice, many departing employees negotiate a shorter exit and the employer accepts it rather than enforce the full period. Plan your TERR Protocol around a realistic 21-day effective window, not the 30-day contract term.

How do I handle a DISCOM submission deadline during the notice period?

Brief an outsourcing partner on day two of the notice period for any DISCOM submission inside the 30-day window. Provide the handover file plus a previous successful DISCOM submission from the same DISCOM circle as a format reference. A competent outsourcing firm can produce a DISCOM-ready drawing package in three to five working days for a standard rooftop project, giving you adequate time for review and resubmission if needed.

What happens if the designer refuses to hand over files?

In most Indian employment contexts, project files created during employment are the property of the employer. If a designer refuses to provide files or deletes work, this constitutes a breach of contract and potentially a civil wrong under the Information Technology Act 2000. However, prevention is more practical than enforcement: maintain a cloud-shared file system (Google Drive, SharePoint, or a client portal) where project files live on company infrastructure, not the designer’s local machine. This eliminates the refusal risk entirely.