Your best rep is in Vyara, a few hours from the Surat office. Another is in Navsari and a third in Bardoli. Every evening each of them sends the same kind of message: "Sir, aaj 4 visit kiye, sab theek hai." You cannot tell which of the four visits happened, what the customer said, or whether a proposal went out. So you phone each rep at 8 pm and ask again.
That is the real problem with a field team you cannot see. You do not lack a map of where reps are. You lack a trace of what they did that you can check without taking their word, so every review turns into a mood.
This guide is the method we would use instead of location tracking. A normal day of selling already leaves marks: an estimate made on the phone, an activity logged on a lead, a follow-up reminder, a proposal PDF sent on WhatsApp. You sample those marks once a week, phone a few customers once a month, and check each rep less often as they earn it. It works for four reps or fourteen, and it needs no one's location.
It sits beside three other guides in this series. The daily message is the Five-Line Day Report. The weekly meeting is the solar sales pipeline review. Monthly goals are in how to set a solar sales target. This post is the check that tells you whether those three are true.
Key takeaway
To manage a field sales team in solar without seeing it, check the evidence the work leaves behind, not the rep's position. Run the Trail Check: once a week, pick five of a rep's leads and look for four trails on each (a logged activity, an estimate, a proposal sent on WhatsApp, a dated follow-up reminder). Then phone three customers a month. None of it needs GPS.
Why watching a rep is the wrong goal
When you cannot see a field rep, the useful question is not where they are but what they have produced. A rep parked outside a house is not selling. A proposal that has reached the customer's WhatsApp is. Location answers one narrow question, whether someone was near an address. It says nothing about what happened inside.
Here is what an owner usually wants to know, and what each kind of source can tell you.
| What you want to know | What a location pin tells you | What the work itself leaves behind |
|---|---|---|
| Did the visit happen? | A device was near the address for some time. | An activity on that lead, written in the customer's words, and the customer's own confirmation if you call. |
| Did the customer get a real price? | Nothing. | An estimate made in the app and a proposal PDF in the customer's chat. |
| Will anyone follow up? | Nothing. | A dated follow-up reminder on the lead. |
| Is the rep busy or just out? | Time spent at places. | Leads touched, estimates made and proposals sent in the week. |
| What did the customer actually say? | Nothing. | The rep's note on the lead. |
The fear of the unseen is often bigger than the problem. In a six-month randomised trial of 1,612 employees at a Chinese technology company, published in Nature in 2024, 395 managers expected hybrid working to cut productivity by 2.6% on average. After the trial they put the effect at plus 1.0%. Those were office staff, not field sellers, so do not stretch the result. It shows only that "I cannot see them, so something must be wrong" is a guess.
One exception. If you have already caught a rep inventing visits, you have a conduct problem, not a visibility problem, and you should deal with it directly. The rest of this guide is for honest reps whose work you simply cannot see.
The Trail Check: four trails and one phone call
The Trail Check is a weekly sample of the evidence a rep's work leaves behind. It looks for four trails on each sampled lead (Lead, Estimate, Proposal, Reminder) and adds one monthly phone call to the customer. The four trails follow the order of a normal solar sale, so a rep who does the job properly makes them with little extra effort.
-
LEAD
Lead trail: an activity logged on the lead
One line, written close to the day, in the customer's words ("wants 5 kW, wife wants EMI figures first"). You find it by opening the lead.
-
ESTIMATE
Estimate trail: an estimate made in the app
An estimate for this customer, with a kW size that matches what the rep told you. In Quickest Solar CRM, reps make estimates on the mobile app (Android, iOS and web).
-
PROPOSAL
Proposal trail: the proposal PDF that reached the customer
The PDF sent on WhatsApp. The rep shows the chat on a video call, or sends it to an office number as well, so you can see it without asking the customer.
-
REMINDER
Reminder trail: a dated follow-up on the lead
A reminder with a date, and the last one done on time. A lead with a proposal sent and no reminder has been left to luck.
-
CALL
Customer call-back: the one trail the rep does not write
A two-minute call from you to the customer, once a month, to confirm the visit, the proposal and the next step. This is what keeps the other four honest.
Note. The trails are evidence, not proof. A rep can type a note without visiting. That is why the sample is drawn by you, not the rep, and why the customer call exists. If your CRM or app cannot show you a trail, do not rely on it. Open a test lead in week one and see exactly what your login shows after a rep logs something.
Calling every rep every evening works for two reps and fails at six, because daily calls check mood, not records. The Trail Check moves your attention from the person to the file, and it is kinder: you ask about a lead, not about a rep's honesty.
What every visit must leave behind
Before you check anything, tell the team the minimum trail. A rule that reps know in advance is far more likely to be followed. A rule they discover during an audit gets resented. Here is the minimum that makes the Trail Check possible. It adds a minute or two per visit, so time it with one rep before you promise the team it is quick.
| Moment | What the rep does | Trail it leaves |
|---|---|---|
| Before leaving the customer's gate | Logs one line on the lead in the customer's words and sets the next follow-up reminder with a date. | Lead trail and Reminder trail |
| Before leaving, or in the car | Makes the estimate on the mobile app for the kW size discussed. If the roof is not yet measured, uses the survey notes (see our solar site survey checklist). | Estimate trail |
| The same day | Sends the proposal PDF to the customer on WhatsApp from the phone, and forwards the same PDF to an office number or a team group. | Proposal trail |
| After any phone call | Logs the outcome on the lead. If the customer says "call me Friday", sets a reminder for Friday. | Lead trail and Reminder trail |
| End of the day | Logs the same outcome on several leads in one go where it fits ("no answer, retry tomorrow"). | Lead trail |
Three rules go with the table. Say all three to the team, with a start date, in the team group:
- The check is random and the owner draws the sample. The rep never chooses which five leads you open.
- No trail, no credit for that visit when you count visits towards a target. Apply it from the day you announce it, never backwards.
- Customers will be called. Say so before the first call. It is the most important line in the announcement.
The Monday Trail Check: ten minutes per rep
The Monday Trail Check takes about ten minutes per rep: you draw five leads, ask four yes-or-no questions on each, and talk to the rep about the gaps only. Do it on Monday morning for the previous week's work. For six reps that is about an hour, so let a sales head run some of them if you have more reps than time.
-
1
Draw five leads from the rep's list
Two the rep reported visiting last week. One where a proposal went out. One that has gone quiet for seven days or more. One new lead from the past ten days. You pick them. Bring up that rep's leads in whatever way your CRM allows, then choose.
-
2
Open each lead and answer four questions
Lead trail: is there an activity from the visit week, specific to this customer? Estimate trail: is there an estimate whose kW matches what the rep said? Proposal trail: did the PDF reach the customer? Reminder trail: is there a dated reminder, and was the last one done on time? Answer yes, no, or not applicable.
-
3
Ask to see the proposal chat
On a short video call the rep opens the customer's WhatsApp chat and shows the PDF, or sends you a screenshot. If you have the forward-to-office rule, you check the office number instead and the rep is not needed.
-
4
Write the score in one row of a sheet
Rep, date, yes answers, applicable answers. Nothing else. Do not build a dashboard for this.
-
5
Talk about the gaps, not the score
Start with a question: "I could not find an activity for Chaudhari on Wednesday. What happened?" Ask first and tell later. Most gaps are habit, not dishonesty.
Note. A starting rule, not a benchmark: if fewer than three in four applicable answers are yes, hold a short call about the gaps that week. If a rep is above that for several weeks, check them less often (see the rhythm section). Adjust the line to your team after a month. We have no industry figure for this and do not claim one.
A worked example: one rep, five leads, three towns
Suppose Kiran sells for a Surat EPC and covers Navsari, Vyara and Bardoli. The owner draws five of his leads on a Monday. Every name, place and number below is invented to show how the check reads. This is illustrative.
| Lead | Lead trail | Estimate | Proposal | Reminder | Owner's read |
|---|---|---|---|---|---|
| Desai, Navsari, 4 kW, visited Tuesday | ✓ | ✓ | ✓ | ✓ | Clean. Nothing to say except thanks. |
| Chaudhari, Vyara, 3 kW, visited Wednesday | ✗ | ✗ | ✗ | ✗ | No trace at all. Customer call-back later confirms the visit happened. |
| Patel, Bardoli, 6 kW, proposal sent 9 days ago | ✓ | ✓ | ✓ | ✗ | Reminder is 5 days overdue. Follow-up has slipped. |
| Shah, Navsari, quiet for 16 days | ✗ | ✓ | ✓ | ✗ | Nothing logged since the proposal and no reminder set. Lead is drifting. |
| Rana, Vyara, new lead, 6 days old | ✓ | n/a | n/a | ✓ | Called and a reminder is set. Estimate not due yet. |
The score is 11 yes answers out of 18 applicable, below the owner's three-in-four line. The number is not the point. The sheet holds one surprise and one conversation.
Chaudhari is the surprise. A row of zeros looks like a visit that never happened. The owner phones the customer two days later, who says Kiran came on Wednesday, measured the roof and gave a rate on paper. The visit was real. Kiran had worked out the price on a calculator and written it on a slip. The fix is a rule, not a warning: make the estimate in the app before leaving the gate, so the proposal can go out the same day.
Patel and Shah are the conversation. Both have a proposal and no live reminder. The owner asks how many leads Kiran is carrying compared with the other reps. If it is far more, the problem is load, and that belongs to the owner. If not, the problem is treating "proposal sent" as the end of the job.
The customer call-back: five minutes, three questions
The customer call-back is a short call from the owner or sales head to a customer the rep reported visiting. It is the check a rep can least influence, so it is what makes the whole method hard to fake. Three calls per rep per month is enough to keep it honest.
Ask three things, in this order: did our rep visit you on that day, did a proposal reach you on WhatsApp, and do you know what happens next and who will call. Do not ask about the price quoted, any discount, or whether the rep was good. Those questions turn a check into a complaint line.
English script
Hello [Mr / Ms Name], this is [your name] from [company]. Thank you for talking to [rep's name] last week.
Just three quick things. Did [rep's name] visit you on [day]? Did you receive a proposal on WhatsApp?
And do you know who will call you next? That is all. Thank you for your time.
Hinglish script
Namaste [Name] ji, main [company] se [aapka naam] bol raha hoon. [Rep ka naam] pichhle hafte aapse mile the, sahi hai?
Kya aapko WhatsApp par proposal mila? Aur agla step kya hai, kaun call karega, yeh pata hai?
Bas itna hi poochna tha. Dhanyavaad.
Five rules keep the calls from becoming a burden for the customer or an ambush for the rep.
- Pick from the leads the rep logged as visited. Do not pick from the rep's favourite customers.
- Call within two weeks of the visit, while the customer still remembers it.
- Skip anyone who asked you not to call, and anyone in the middle of a dispute. The call is a courtesy, not a way to reopen an argument.
- Keep it under two minutes and call from the company number.
- Tell the rep the result. If the customer says the rep was excellent, say that too. The calls should find good work as often as bad.
If a customer says nobody visited, accuse no one that day. Check the lead, ask the rep, and call the next few customers on that rep's list. One wrong answer can be a wrong date or a colleague's visit. A pattern is something else. Our guide to solar lead follow-up cadence covers the same discipline from the customer's side.
Reading the patterns: what a thin trail usually means
A thin trail has a cause, and the cause decides your response. Read the pattern across a few weeks, not a single sheet. The most common patterns are below.
| Pattern in the sample | Usual cause | What to do first |
|---|---|---|
| Visits reported on WhatsApp, nothing logged on the leads | No logging habit, or the visits are being exaggerated. | Call two customers from the rep's list. If the visits are real, set a "log before you leave the gate" rule. |
| Estimates made, but no proposal sent | The rep is waiting for a price decision, or is unsure of the number. | Look at the Stuck line in the rep's day report. Settle the price question that week. |
| Proposals sent, no reminders set | The rep treats "sent" as the end of the job. | Rule: a proposal cannot be sent without a dated next step on the lead. |
| Many overdue reminders | Too many leads for one rep, or calls being avoided. | Count the rep's open leads against the other reps. Move leads before you lecture. |
| Perfect trails every week, zero losses ever logged | Trails are being filled for the audit, or losses are not being recorded. | Make two call-backs on leads the rep marked lost. Check that the reasons are written. |
Two comparisons are worth making once a week, alongside the sample. Put the team report next to what reps wrote in their day reports, and ask why any two numbers differ. And look at whether the weekly pipeline review is spending its time on real deals, or on deals the trails say are quiet. Our guide to stuck deals in a solar pipeline helps with the second.
A rhythm for reps in different towns
Reps in different towns need a rhythm that fits the owner's week: a few minutes daily, ten minutes per rep weekly, a few calls monthly, and a visit each quarter. The point is to spread the checking so no single day feels like an inspection.
| When | What the owner does | Time |
|---|---|---|
| Daily | Reads the day reports. Opens one lead named in one report and finds the last note and the next date. | About 5 minutes |
| Monday | Runs the Trail Check for each rep: five leads, four questions, talk about the gaps. | About 10 minutes per rep |
| Weekly | Runs the pipeline review as a group video call, with the sheet of trail scores in hand but not on screen. | 45 minutes |
| Monthly | Makes three customer call-backs per rep and talks to each rep about one thing done well. | About 15 minutes per rep |
| Quarterly | Spends a day in the rep's town: one customer visit together, one look at the local competition and the rep's week on paper. | One day per rep, rotating |
The check should relax as a rep earns trust, and tighten when they are new. A simple ladder works. Treat the numbers as a starting point and change them for your team.
| Stage | Trail Check | Customer call-backs | How the rep moves up |
|---|---|---|---|
| New (first 30 days) | Every week, all five leads, plus a look at every proposal | Three per month | Finish onboarding sign-off (see our guide to solar sales rep onboarding) |
| Established | Weekly, five leads | Three per month | Four weeks in a row above the three-in-four line |
| Trusted | Every second week, three leads | Two per month | Eight clean weeks in a row |
Nobody goes to zero. If a rep's score falls below the line twice in a row, they step back one level. Say that on day one, so a step back reads as the system working, not as a punishment.
Keep the leads in the company's account, not in a rep's phone
The most expensive thing a field rep can hold is a customer list that lives only on a personal phone. When the rep leaves, the leads leave too, with the chat history and every promise made. A team you cannot see needs its records in a shared place.
Four habits keep it that way. Whatever CRM you use, check each one in a test.
- Every lead is entered in the CRM, not only saved as a phone contact. The customer's name, locality, kW and last note belong on the lead.
- Give each team member the permissions the job needs. Quickest Solar CRM lets you add team members with permissions. Log in as a test rep and look at what that login sees before you rely on it.
- Plan the handover of a rep's leads before it is needed. When a rep leaves or changes town, remove their access that day and reassign their open leads to someone else. Check in your own tool how reassignment works. Our guide to solar lead routing rules covers who should get which lead.
- Do not let the customer relationship live only in a personal WhatsApp. The proposal PDF forwarded to an office number is a cheap safeguard. For team access and collaboration, see how to enable team collaboration in your solar CRM.
What about tracking location?
You do not need location tracking to run the Trail Check, and we do not claim that Quickest Solar CRM offers it. If you still want a tracker, treat it as a labour and privacy decision before a software one. The trade-offs for any tool that records where a staff member is look like this.
Where it helps
- ✓Shows that a phone was near an address at a time.
- ✓Can discourage invented visits.
- ✓Some customers or partners may ask for proof of site presence.
Where it falls short
- ✗Says nothing about what the rep said or sent.
- ✗A phone left in a bag, switched off, or a rep who lives near the customer can give a false signal either way.
- ✗Staff may read it as distrust, with real effects on morale (see the survey below).
- ✗Brings legal duties on how you collect, use and store the data.
On the people side, the best data we found is a survey, not a trial. The American Psychological Association's 2023 Work in America survey, run by The Harris Poll among 2,515 employed US adults in April 2023, found that workers who knew they were monitored reported more stress and more feeling micromanaged. The figures are correlations, not proof of cause, and the APA itself says there is "no confirmation of the root cause". They come from American workers across all jobs, not Indian field sales, so use them as a caution and not a verdict.
56%vs about 40%
felt tense or stressed at work
Monitored vs not monitored. Source: APA Work in America 2023
51%vs 33%
felt micromanaged
Monitored vs not monitored. Source: APA Work in America 2023
42%vs 23%
plan to look for a new job within 12 months
Monitored vs not monitored. Source: APA Work in America 2023
On the legal side, here is a short, general picture as of 31 October 2026. This is not legal advice. Take advice from a lawyer before you act.
- India's Digital Personal Data Protection Act, 2023 covers digital personal data. Where a tool records an identifiable employee's whereabouts, it is reasonable to treat that as personal data. Our DPDP Act glossary entry gives the basics.
- Section 7(i) of the Act lists, among the legitimate uses of personal data, processing "for the purposes of employment or those related to safeguarding the employer from loss or liability". How far that reaches for continuous location tracking is a question for your lawyer. We have not seen it settled, so we do not say it covers you.
- Section 5 requires a notice saying what data is processed and why. Section 6(1) says consent must be limited to the data necessary for the specified purpose. Both point one way: tell staff in writing and collect only what you need.
- The government notified the DPDP Rules, 2025 on 14 November 2025, according to the PIB release of that date, with an 18-month phased compliance timeline. The PIB backgrounder of 17 November 2025 repeats it. Check which provisions apply to you on the day you decide.
Verdict
Build the method on evidence the work already leaves, and keep it working with no tracker at all. If you later add any location tool, write the policy first, tell staff in writing, collect the least you need and take legal advice. A tracker can support the Trail Check. It cannot replace it.
How QuickEstimate fits
The Trail Check needs a place where a rep's work lands, and the rep's phone is where it starts. In Quickest Solar CRM, reps can make estimates on the mobile app (Android, iOS and web), add and edit leads, log an activity on a lead (also on several leads at once), set follow-up reminders and share the proposal PDF on WhatsApp. As the owner you can add team members with permissions, filter leads, and use the dashboard and the team report. Those are the raw material for the four trails and the sample you draw from. Test what your owner login shows for each one before you rely on it.
Be clear about the limits. We do not claim that Quickest Solar CRM tracks where a rep is, and this method does not depend on it. The CRM also does not check that a visit took place. It gives you the file to open and the questions to ask. The customer call-back stays with you.
- Download the app: put it on one rep's phone and one test lead on yours, then run the Trail Check on that lead before you roll it out.
- Pricing: the Free plan is 1 user and 10 proposals a month with no card. A team needs Pro, at ₹6,999 per user per year with a 3-user minimum (₹20,997 for 3 users), billed yearly with a GST invoice.
Run one test before you pay for anything. On a test lead, log an activity, make an estimate, set a reminder and send the PDF, then log in as the owner. If you cannot find all four trails in under a minute, the Trail Check will not survive a busy week, whichever CRM you use.
What to do this week
You can start the Trail Check with a spreadsheet and your existing CRM, in three jobs.
- Write the minimum trail on one page and send it to the team. Use the table from the section on what every visit must leave behind, with a start date and the three rules. Say that customers will be called.
- Run the first Trail Check on one rep. Draw five leads yourself, ask the four questions, and talk about the gaps in a calm tone. Do the first one together with a sales head so you agree what a "yes" means.
- Make your first three customer call-backs. Use the script above on three leads the rep logged as visited. Tell the rep the result.
For the weekly meeting this feeds, see the pipeline review guide. For what to measure, see solar sales team KPIs. To plan how structure changes as you add towns, see scaling a solar team from 5 to 50 and how to build a solar sales team.
Frequently asked questions
How do I manage a field sales team I can't see?
Check the evidence their work leaves, not their position. Once a week, draw five of a rep's leads and look for four trails on each: a logged activity, an estimate, a proposal sent on WhatsApp and a dated follow-up reminder. Once a month, phone three customers to confirm the visit and the proposal. Check new reps more often and trusted reps less often. This takes about ten minutes per rep per week.
Do I need GPS tracking for field sales reps?
No. GPS shows that a phone was near an address, not what was said or sent. A logged activity, an estimate, a proposal in the customer's chat and a customer call-back show more about the quality of the work. If you add any location tracking anyway, tell staff in writing, collect only what you need and take legal advice. We do not claim that Quickest Solar CRM tracks location.
How can I tell if a rep is really visiting customers?
Combine three checks. First, open a few of the leads the rep reported visiting and read the last activity. Second, ask to see the proposal in the customer's WhatsApp chat. Third, phone a customer from the rep's list and ask whether the visit happened. The call is the check a rep can least influence, so use it every month on every rep.
Is it legal to track an employee's location in India?
This is general information, not legal advice. Location of an identifiable employee is reasonably treated as personal data under the Digital Personal Data Protection Act, 2023. Section 7(i) allows processing for purposes of employment, but how far it covers continuous tracking is a question for a lawyer. Notice and necessity matter. The DPDP Rules were notified on 14 November 2025 with an 18-month phased timeline. Take advice first.
How often should I check a field rep's work?
Weekly for a new rep and for any rep below your line, every second week for a trusted rep, and never zero. The Monday Trail Check takes about ten minutes. Customer call-backs run at two or three a month per rep. Tell the team the schedule in advance so the checks read as routine, not as suspicion.
What if my reps say logging every visit is extra work?
It is, by a minute or two a visit, and you should admit that. Offer a trade: the trail replaces the evening phone call and the long WhatsApp report. It also protects the rep, because a lead with a clear log can be picked up by someone else when the rep is ill or leaves. Time one rep before you fix the rule.
Can one owner check ten reps?
Not alone. Ten reps at ten minutes each is about an hour and forty minutes every Monday, plus call-backs. Split it: a sales head or ops lead runs the Trail Check for most reps, and you keep the customer call-backs and one rep review a week. Move trusted reps to the fortnightly check to free time.
Does Quickest Solar CRM track my reps' location?
We do not claim that it does, and the Trail Check does not need it. Reps make estimates on the mobile app, log activities on leads, set follow-up reminders and share proposal PDFs on WhatsApp. You see the leads, the team report and the dashboard. Open a test lead on both a rep's login and yours to see exactly what each shows before you rely on it.
Want to put this into practice?
Quickest Solar CRM gives you everything in this article, proposal automation, lead capture, WhatsApp follow-up, built for Indian solar EPCs.
Start free