DCR full form and definition
DCR = Daily Call Report. A record submitted by a Medical Representative at the end of each working day, listing every doctor, chemist and stockist visited, what was discussed or detailed, what samples or reminders were given, and what orders resulted.
In Indian pharma the word "call" does not mean a phone call. A call is a face-to-face visit to a healthcare professional or trade customer. So a Daily Call Report is a report of the day's visits — not the day's phone activity.
The DCR is the base unit of almost everything a pharma company knows about its own field operation. Coverage percentages, doctor frequency, territory productivity, incentive calculations, sample accountability and expense justification are all computed from it, directly or indirectly. If the DCR is wrong, everything built on top of it is wrong in the same direction, and usually with more confidence.
Why India runs on DCRs specifically
Field reporting exists everywhere, but the DCR carries more weight in India than its equivalent does in most Western markets, for a structural reason.
In regulated Western markets, prescription and dispensing data is centrally available. A company can measure what a doctor actually prescribed without asking the rep. In India that data is not centrally available in the same way, so the company measures the input it can see — visits made, doctors covered, frequency achieved — and infers the rest, supplementing it with Retail Chemist Prescription Audit at the counter.
That inference only holds if the input data is honest. Which is why the quality of DCR capture is not an administrative concern in Indian pharma. It is the measurement system.
What a DCR contains: the standard fields
Formats vary by company, but a complete DCR covers the following. If you are designing one, or evaluating whether an existing one is adequate, this is the checklist.
| Field | What it records | Why it is there |
|---|---|---|
| Date and working day type | Field day, holiday, leave, meeting, HQ or ex-HQ working | Drives working-day counts and expense entitlement |
| MR name and territory | Who reported, against which territory | Ties activity to the coverage plan |
| Doctor visited | Name, speciality, grade or category | Coverage and frequency are computed per grade |
| Time of call | When the visit happened | Distinguishes a real day's route from a reconstructed one |
| Products detailed | Which brands were promoted, in what order | Links promotional effort to prescription movement |
| Samples given | Product, quantity, batch where applicable | Sample accountability, and UCPMP documentation |
| Brand reminders / inputs | Item and value, from an approved list | Demonstrates the value cap was respected |
| Chemist and stockist calls | Outlet visited, stock position, RCPA observations | Secondary sales visibility and competitor movement |
| Orders booked (POB) | Value or units ordered | Converts activity into a commercial number |
| Work-with | Whether a manager accompanied the MR | Coaching record and joint-working norms |
| Remarks / next action | What was committed, what to follow up | The field most often left blank and most often needed |
| Travel | Distance and mode between calls | Expense derivation, and a reality check on the route |
Two fields do disproportionate work: time of call and next action. Time of call is what separates a genuine day's route from one assembled afterwards. Next action is the only field that makes the DCR useful to the MR who wrote it, rather than only to the office.
The 10pm problem
Here is the thing everyone in Indian pharma knows and few systems are designed around.
In principle the DCR is filed as the day happens — one entry per call, made at or near the point of the visit. In practice, on a great many teams, the MR sits down at the end of the day and fills the whole thing from memory. Sometimes at the end of the week.
This is not primarily an integrity problem. It is a design problem. It happens whenever filing during the visit is slower or more awkward than remembering — a form with too many fields, an app that stalls without network, a login that times out between calls. The MR takes the path that costs less, exactly as anyone would.
The consequence is specific and worth naming. A DCR filled from memory is not a record of what happened; it is a record of what the MR recalls, shaped by what they believe the office wants to see. Coverage numbers built from it describe recall rather than reality — and every report, incentive calculation and territory decision downstream inherits that gap, without any indication that it is there.
Which produces the diagnostic that matters when you are evaluating any field system: is filing during the visit genuinely faster than filling it in at 10pm? Not "can it be done during the visit" — every system can. Faster. Time it on a phone, standing up, with one hand.
Reporting activity vs managing coverage
A well-filed DCR tells you what was done. It does not, by itself, tell you whether enough was done. Those are different questions and they need different numbers.
Activity, from the DCR: 412 calls made this cycle against 1,180 planned for the month.
Coverage against target: core-grade doctors at 61% of required frequency with nine working days left, concentrated in two territories.
The first is a number for a report. The second is a number a manager can act on this week, while the cycle can still be saved.
Getting from the first to the second requires two things the DCR alone does not supply: a frequency target set per doctor grade at the start of the cycle, and a live comparison against it. Most platforms in this category report activity well. Fewer close that loop. It is worth knowing which kind you have.
DCR formats: Excel, paper, app
Paper and Excel
Still common in smaller companies, and there is no shame in it — plenty of well-run field forces operate this way. The limitations are structural rather than moral. There is no timestamp, so there is no way to distinguish a contemporaneous record from one written later. There is no audit trail, so an edit leaves no trace. And consolidation is manual, which means the coverage question gets answered weekly at best, usually after the point where anything can be done about it.
Mobile app
The intended answer, with a caveat. An app only improves things if it is faster than memory at the point of the call. An app that is slow, or that fails without network at a rural chemist counter, actively makes the problem worse — it trains the MR to record later while giving the office false confidence that capture is live. When evaluating, the question about connectivity is not cosmetic: ask what happens with no signal, and what happens to that record when signal returns.
Five ways DCR practice goes wrong
- Too many mandatory fields. Every field added to the form is a small tax on live capture. Past a threshold the MR stops filing live entirely, and you lose more data than the extra fields were ever going to give you.
- Grades that are stale. Coverage targets are computed off doctor grade. If grading was done two years ago and never revisited, the coverage report is precise and meaningless.
- Using the DCR purely as surveillance. If the only time an MR hears about their DCR is when something is wrong, it becomes a compliance ritual rather than a working tool. The "next action" field is the cheapest fix — it makes the record useful to the person writing it.
- Reviewing at month end. A DCR reviewed on the 31st is history. Reviewed on the 18th, it is a plan for the remaining days.
- No link to expenses. Where the expense claim is a separate number typed into a form at month end, it is disconnected from the day it supposedly funded. Derived from the recorded route, it justifies itself — and most reconciliation disputes disappear.