What is MR reporting software?
MR reporting software is the system a pharma company uses to record what each medical representative did in the field: which doctors and chemists were met, which brands were detailed, which samples were handed over, and what the day cost in travel. It turns that record into approvals and reports for the ASM, RSM and head office.
Most Indian pharma companies arrive at it from one of two starting points. Either reps send a DCR as a WhatsApp message each evening and someone at head office copies it into Excel, or the company already pays for a subscription tool that no longer matches its incentive rules or TA/DA policy. Both situations lead to the same question: should the MR reporting software be something you own?
A complete system has two faces. The field app is what the representative opens forty times a day, so it must be quick on a mid-range Android phone and forgiving when the network drops. The web panel is where the sales office, finance and HR work, so it needs filters, exports and an audit trail. Our team builds both: one of us writes the app and APIs, another of us sets up the cloud, database and reporting layer, and the third of us runs the plan and the rollout with your sales admin.
Which pharma companies need MR reporting software, and which can wait?
You need MR reporting software once managers can no longer answer simple questions quickly: which A-class doctors did nobody visit this month, how many chemist calls did the Nagpur HQ make, what did the Patna team spend on outstation travel. If answering takes a day of spreadsheet work, the process has outgrown manual reporting.
In practice the tipping point is around twenty representatives or two layers of management. PCD pharma franchise companies hit it early because they deal with many franchisees and want to see promotion on their brands; ethical marketing companies hit it when they open a second division or a new zone.
Build now if
You have 20+ MRs, a written TA/DA policy with slabs, sample stock that never reconciles, or incentive schemes that depend on call data you cannot trust.
Wait if
You have fewer than ten reps, one manager who knows every doctor personally, and no immediate plan to expand into new states.
If you are still at the spreadsheet stage and want to move step by step, our page on how to convert Excel sheets into software explains a gentle path from sheets to a proper web app.
How the daily call report works inside MR reporting software
The daily call report is a list of every call made that day, each with the customer, the products detailed, the samples or inputs given, any joint-work partner and a short remark. Good MR reporting software makes a call take under a minute to log.
Speed comes from the doctor master. When a rep selects a patch, the app shows only the doctors and chemists planned for that area, sorted by category. Tapping a doctor pre-fills the speciality, the brands usually detailed to that speciality, and the last visit date. The rep adjusts quantities, adds a remark if needed and moves on.
At day end the app asks the rep to submit. Late submission rules are yours to set: some companies lock a DCR after 48 hours, others allow backdating with manager approval. We build the rule you already follow, not a new one.
- Doctor call: brands detailed, samples and literature given, POB if any, joint-work manager
- Chemist call: stock check on focus brands, order booked for a stockist, remarks
- Stockist call: secondary sales note, pending orders, expiry returns
- Non-field day: meeting, training, leave or holiday, each coded for reports
Tour programme planning: doctor lists, patches and manager approval
A tour programme is the rep’s plan for the month: which patch on which day, and whether the day is HQ, ex-HQ or outstation. In MR reporting software the TP is drafted by the rep, sent to the ASM, edited or approved, and then used as the benchmark for that month’s DCR.
The value is in deviation tracking. When a rep reports calls from a patch that was not on the TP for that day, the system flags it for the manager rather than rejecting it, because real field days change for good reasons: a doctor asks for a visit, a train is late, a stockist has an urgent issue.
Well-designed TP screens also enforce coverage norms. If your policy says A-class doctors must be met twice a month and B-class once, the TP draft shows which doctors are not yet scheduled, so the rep fixes the plan before submitting rather than after the month is lost.
Joint working
When an ASM plans to accompany a rep, the TP records it on both calendars, and both DCRs later show the joint call so it is not counted twice in coverage reports.
Mid-month changes
Reps can request a TP change for future dates; the manager sees the old and new plan side by side before approving.
Sample and input tracking in MR reporting software under UCPMP 2024
Sample tracking answers one question: for every strip of samples issued to a representative, where did it go? MR reporting software keeps a running stock per MR by product and batch, reduces it with each doctor call, and highlights gaps at month end.
Compliance is the other reason to take this module seriously. The Department of Pharmaceuticals notified the Uniform Code for Pharmaceutical Marketing Practices (UCPMP) 2024, which restricts free samples and prohibits gifts and personal benefits to healthcare professionals, and the department runs an online portal where companies disclose marketing expenditure under the code. Your MR reporting software cannot make you compliant on its own, but it can give your compliance team clean per-doctor, per-batch records to work from.
We therefore build the input module around categories your compliance head approves: samples, scientific literature, brand reminders and so on. Anything outside approved categories simply does not appear in the app. Limits per doctor or per month can be enforced in code once your team defines them; we do not decide those limits, and the final reading of the code should come from your own compliance adviser.
- Issue: head office or depot issues batch-wise stock to each MR, with acknowledgement in the app
- Use: each doctor call reduces stock by product, batch and quantity
- Return: expired or unused stock returned and logged
- Reconcile: month-end report of opening, issued, given, returned and closing stock
TA/DA expense claims: how MR reporting software calculates them
TA/DA is where most spreadsheets break, because the rules have several layers. MR reporting software should calculate the claim automatically from the day’s work type and the distance, leaving the rep to add only genuine extras such as a courier bill or a hotel receipt.
A typical policy pays a daily allowance that depends on whether the day was HQ, ex-HQ or outstation, plus a fare that depends on distance slabs between HQ and the patch. Some companies pay a fixed allowance per kilometre, others reimburse actual bus or train fares. Grade matters too: an RSM’s outstation allowance differs from a trainee’s.
We code your policy as a rule table the admin can edit, not as fixed logic. When the policy changes in April, finance updates the table and the next month’s claims follow it, without a developer.
If you want expense approvals for office staff as well, the same engine can serve the whole company; see our note on expense management software for claims outside the field force.
Are geo-tagged visits in an MR app accurate enough to trust?
Geo-tagging tells a manager roughly where the phone was when a call was logged; it is good evidence, not perfect proof. Phone GPS inside a hospital building or a crowded market can drift, and some doctors’ clinics sit above shops on busy roads.
The fair way to use it in MR reporting software is to store the location with each call, compare it with the doctor’s saved clinic location, and flag calls that fall well outside a radius you choose. Managers review flags; the app does not reject calls automatically. Saving the clinic location the first time a rep visits builds the reference map over a few weeks.
Be open with your field force about what is recorded. We capture location when a call is saved and at day start and day end, not all day in the background, unless you ask for continuous tracking and tell your staff. Continuous tracking drains batteries on budget phones and causes more resentment than it solves. India’s Digital Personal Data Protection Act, 2023 applies to your employees’ and doctors’ personal data, so check your notices and consent with your own legal adviser.
ASM, RSM and ZSM approvals: designing the hierarchy
Approvals in MR reporting software follow your reporting lines: the MR submits, the ASM approves or sends back with a comment, and certain items escalate to the RSM. Getting the hierarchy right is more important than any screen design.
Real hierarchies are messy. One ASM covers two HQs, a vacancy means the RSM approves an MR directly for three months, a division has no ZSM. The software must handle vacancies and dual reporting without a developer, so we store the hierarchy as data the admin can change, with effective dates so old approvals stay correct.
- MR: submits TP, DCR, expenses, leave and doctor-addition requests
- ASM: approves TP and expenses, reviews DCR, logs joint work
- RSM: approves exceptions such as outstation beyond policy, reviews area coverage
- ZSM or sales head: zone dashboards, incentive inputs, policy changes
- Admin and HR: masters, hierarchy, holidays, exports to payroll
Managers approve on the phone, from a single list of pending items with the MR’s name, the date and the amount. Nothing is hidden three menus deep, because approvals that sit untouched delay salaries and damage trust in the system.
Does MR reporting software work offline in rural territories?
It should, and ours does. The field app stores the doctor master, TP and sample stock on the phone, saves calls locally, and syncs when the network returns. A rep working a patch with patchy coverage loses nothing.
Offline design has consequences for the build. The app needs a local database, a sync queue that retries safely, and conflict rules for the rare case where a manager edits a record while the rep is offline. That work is a real part of the quote, and it is the part cheap apps usually skip.
We also test on the phones your reps actually carry. A field app that runs well on a flagship but stutters on an entry-level Android handset with limited storage is not finished. Before rollout we ask sales admin for the three most common phone models in the team and test on similar devices.
Ready-made MR reporting software or a custom build: how to decide
Buy a ready-made subscription when your process is close to standard and you want to start next week. Build custom MR reporting software when your rules, hierarchy or data ownership needs keep clashing with what a product allows, or when per-user fees across a growing field force add up to more than owning the system.
Neither choice is wrong. The honest test is to write down your five most important rules, such as the TA/DA slabs, the coverage norms, the sample categories, the approval chain and the reports the MD reads, and check how many a product handles without workarounds. If most fit, subscribe. If several need spreadsheets on the side, you are already paying for a custom process, just manually.
Choose a subscription when
You have a standard process, fewer than about fifty users, no in-house IT and no strong need to host data yourself.
Choose a custom build when
You have your own policy logic, several divisions, plans to integrate with ERP or payroll, and want no per-user licence cost.
Our broader guide on custom software development costs in India explains how owning software changes the cost curve over three to five years.
How much does MR reporting software cost in India?
With BtechWaleTech, a custom MR reporting software system with an Android and iOS field app and a web admin panel starts at ₹60,000. A narrower DCR-and-TP app on a simple backend starts at ₹40,000. Final cost depends on modules, roles, offline sync and integrations.
The price moves with scope, not with the number of users, because you own the software. Twenty reps or two hundred, the code is the same; what changes is the server size, which is a small monthly hosting bill in your own cloud account. That is the main financial difference from a per-user subscription.
Lines that commonly add to a quote: offline sync with conflict handling, sample stock with batches and expiry, payroll or ERP export in a set format, stockist secondary sales, incentive calculation, Hindi or regional-language labels, and AI-written manager summaries, which start at ₹40,000 as an add-on.
For a line-by-line view of how app budgets are built, see app development cost in India.
The tech stack behind a dependable MR reporting app
We build the field app in Flutter by default, which gives one codebase for Android and iOS and handles offline storage well; React Native is an option if your IT team prefers JavaScript. The web panel is a React or Next.js front end on a Node.js or Python API with PostgreSQL as the database.
Hosting goes into your own AWS or other cloud account, set up by another of us, with daily database backups and role-based access. Push notifications remind reps about pending DCRs and managers about approvals. Reports that head office runs often are pre-computed overnight so dashboards open quickly even with a year of call data.
We avoid exotic tools. A pharma company should be able to hire any competent developer later to maintain its MR reporting software, so the stack is mainstream, documented and handed over with the source code.
Reports sales managers actually open
Most MR reporting software ships with dozens of reports and managers use four. We start with the few that change decisions and add more only on request.
- Doctor coverage: A, B and C doctors met against the norm, by MR, HQ and area
- Missed doctors: listed doctors with no call in the month, sorted by category
- Call average: doctor and chemist calls per field day, trending by week
- TP adherence: planned patches against reported patches
- Sample reconciliation: opening, issued, given, returned, closing stock
- Expense summary: TA/DA by HQ, with outliers highlighted for review
Every report exports to Excel, because your analysts will want to pivot it. For live charts across divisions, the same data can feed a dashboard; our team handles data dashboards and automation alongside app work.
Who owns the doctor master, and how do you migrate from Excel?
Your company owns the doctor and chemist master, the call history and the source code. The database sits in your cloud account, the app is published under your Google Play and App Store developer accounts, and we hand over repository access at launch.
Migration usually starts with a messy Excel file of doctors per HQ, with duplicates and spelling variations. We clean it with your sales admin: merge duplicates, standardise specialities, assign categories and map each doctor to a patch. This step often takes longer than people expect, and it decides whether the app feels trustworthy on day one.
Old DCR history can be imported if it is structured; if it lives in WhatsApp messages, we usually recommend starting fresh and keeping the old sheets as an archive.
MR reporting software timeline: from brief to field rollout
A typical build runs 6–12 weeks, followed by a pilot. Rolling out to one area first catches problems while they affect ten people instead of two hundred.
- Week 1: workshop with sales admin, finance and one ASM; written scope and rule sheets
- Weeks 2–3: doctor master cleanup, hierarchy setup, screen designs approved
- Weeks 3–8: field app and web panel built, demos every week
- Weeks 8–10: testing on real phones, TA/DA rules checked against last month’s claims
- Pilot: one area of 10–15 reps for two to three weeks
- Rollout: remaining areas in waves, with short training videos in Hindi and English
Checking the new TA/DA engine against last month’s manually approved claims is the single best test we know. If totals match, finance trusts the system from the start.
Worked example: planning MR reporting software for a 40-rep PCD pharma company
Imagine a hypothetical PCD pharma company in Ahmedabad with 40 medical representatives across Gujarat and Rajasthan, four ASMs and one sales head. Today reps send DCRs on WhatsApp and a coordinator types them into Excel every morning.
Phase one would cover the doctor master, TP with ASM approval, DCR with offline sync, and a basic sample stock per rep. That fits the starting range of ₹60,000. Phase two, a couple of months later, might add TA/DA with the company’s slab rules and an export for the accountant. Phase three could add AI-written weekly summaries for the sales head.
The coordinator would stop typing and start checking exceptions: missed A-class doctors, unusual expenses, deviations from TP. That shift, from data entry to review, is the real return on MR reporting software, and it is visible within the first month of use.
MR reporting software checklist before you sign any quote
Use this list whether you hire us, another developer or buy a product. Each point is cheap to settle before the build and expensive to fix after rollout.
- Written TA/DA policy with slabs, grades and exceptions
- Clean doctor and chemist master with categories and patches
- Hierarchy with vacancies and dual reporting explained
- Sample and input categories approved by your compliance head
- Decision on location capture: per call only, or continuous with consent
- Offline sync confirmed and tested on your reps’ phones
- App published under your own developer accounts
- Source code, database and admin logins handed to you
- Maintenance terms and costs agreed in writing
For wider background on choosing developers, the hire a software developer guide covers vetting questions that apply to any build.