You can build a dope card that hits without ever opening a ballistic app, and the card you build that way will often be more trustworthy than the one the app prints. The reason is simple once you see it. A solver predicts what your rifle should do, while a confirmed drop records what your rifle actually did, and the second number is the one that puts rounds on steel. This guide walks through building a dope card from scratch, starting with a handful of measured drops at known distances and ending with a column of numbers you can dial with confidence.
Building a dope card from confirmed drops is the oldest method in long-range shooting, and it still anchors the modern process. The solver is a wonderful accelerator, but it works best as a check on real data rather than a replacement for it. By the end of this guide you will know how to gather those drops, convert them into come-ups, fill the gaps between them, and only then bring a solver in to calibrate against what you proved on the range.
What a dope card actually is
A dope card is a compact table that answers one question for every distance you might shoot. How much elevation do I add to hit center? The word dope is shorthand for data on previous engagements, and the card is simply that data organized so you can read it under time pressure. Most cards list a distance in one column and the corresponding elevation correction in the next, expressed in the angular units your scope uses.
The correction itself is a come-up, the amount of elevation you add above your zero to counter the bullet's drop at that range. If your rifle is zeroed at one hundred yards, a five hundred yard target sits well below your line of sight by the time the bullet arrives, so you raise the point of aim by a measured amount to compensate. You can apply that come-up by dialing it onto the elevation turret or by holding it on a marked reticle, and a good card serves both methods equally.
What makes a card yours, rather than a generic chart, is that every number on it came from your rifle, your load, and your zero. That is the whole premise of building one from confirmed drops. You are not copying a manufacturer's table that assumes a velocity and a barrel you do not have, you are recording the truth your own setup tells you on the range.
Why measured beats predicted
A ballistic prediction starts from inputs you can only estimate, and small errors in those inputs grow with distance. The solver needs your muzzle velocity, the bullet's drag, and the air density, and a few feet per second of velocity error or a slightly optimistic drag figure will throw the far solution off by a tenth of a mil or more. Inside three hundred yards that error hides in the noise, but past six hundred it starts to cost you center hits.
A confirmed drop carries none of that uncertainty, because it is a measurement rather than a forecast. When you dial a correction and the bullet lands dead center at six hundred yards, you have established a fact about your rifle that no model can override. That fact already bakes in your real velocity, your real barrel, the day's air, and even quirks the solver never sees, which is exactly why a measured card tends to beat a predicted one where it matters.1
None of this makes the solver useless, and a later section gives it an important job. The point is the order of operations. You gather truth first, then you calibrate the prediction to match it, instead of trusting a prediction and hoping the truth agrees.
Before you collect a single drop
The fastest way to ruin a dope card is to build it on a scope that does not move the way its markings claim, so the groundwork comes before the data. Your card is only as trustworthy as the mechanism that applies it, and a little verification up front saves a lot of confusion later.
Start by confirming your scope's tracking, ideally with a tall-target-test. You fire at the bottom of a tall, plumb target, dial a large known amount of elevation, and fire again near the top, then measure whether the impact actually climbed the amount you dialed. If ten mils of dialing moves the bullet a true ten mils, your turret-tracking is accurate and your future come-ups will mean what they say.2 If it moves slightly more or less, you record the correction factor and apply it, because otherwise every drop you collect inherits that hidden error.
Pick your units and commit to them. A scope that reads in mil wants a card in mils, and one that reads in minutes of angle wants a card in minutes, and mixing the two is a reliable way to miss. Settle the reticle and turret in the same language, gather a notebook or a data-book to log conditions, and confirm you have a safe range with verified distances, since a wrong yardage corrupts every number built on it.
Heads up. A dope card inherits every error in the system that built it. A scope that tracks ten percent short shifts every come-up you record by the same factor, so the card looks perfectly consistent. Verify the mechanics first, then trust the data.
Setting and confirming your zero
Every come-up on your card is measured from your zero, so the zero has to be solid before anything above it means anything. Most precision shooters use a one hundred yard zero, because drop data past that point is well documented and the bullet's behavior there is easy to read.3 A consistent zero is the foundation the entire card stands on.
Confirm the zero with a real group rather than a single shot, because one round can land off center by luck and send you chasing a correction you do not need. Fire three to five rounds, find the center of that group, and adjust until the group's center sits on your point of aim. Then fire another group to verify the change held, and note the exact conditions in your book, since you are establishing the reference that every later number depends on.
Document your zero-distance explicitly, because the choice cascades through the whole card. A one hundred yard zero needs upward corrections starting almost immediately past that distance, while a two hundred yard zero shifts where your come-ups begin. There is no single right answer, only a documented one, and writing it down keeps you from guessing later about what your numbers are referenced to.
Collecting confirmed drops, distance by distance
With the mechanics verified and the zero set, you collect drops one distance at a time, and the method is a short loop you repeat. Move to a known distance, dial your best starting estimate of the come-up, fire a small group, and observe where it lands relative to center. The first estimate can come from a generic chart, a shooting partner's data for a similar load, or simple intuition, because you are going to correct it on the spot anyway.
If the group prints low, you need more elevation, and if it prints high, you need less. You measure how far off center the group sits, convert that miss into an angular correction using the math in the next section, and adjust your dialed value accordingly. Then you fire again to confirm the corrected come-up actually centers the group, and only when it does do you write that number down as confirmed. A drop you did not verify with a second group is a guess, not data.
Work through the distances you realistically expect to shoot, often in two or three hundred yard steps, such as two hundred, four hundred, six hundred, and eight hundred. You do not need every hundred-yard increment, because the gaps fill in cleanly later, but you do want enough confirmed anchors to define the curve. Shoot when conditions are calm if you can, since wind and mirage make it harder to read true elevation, and record the density altitude or the raw temperature and pressure for the session.
Pro tip. Collect your drops in the calmest air you can find, ideally early morning. Wind drift and vertical mirage both muddy your read of where the bullet truly landed, and a dope card built in messy conditions carries that mess into every future shot. Clean inputs make a clean card.
Turning a miss into a correction
The one piece of arithmetic this process requires is converting a miss on the target into a turret correction, and it is lighter than it sounds. Your scope's units are angular, so the same number of clicks covers more inches the farther out you shoot, which is the relationship you are using when you adjust.
In mils, one mil spans roughly 3.6 inches at one hundred yards, and it scales with distance, so it covers about 7.2 inches at two hundred yards and 21.6 inches at six hundred.4 To turn a vertical miss into a correction, you divide the miss in inches by the inches-per-mil at that distance. A group landing seven inches low at three hundred yards, where one mil is about 10.8 inches, needs roughly two-thirds of a mil more elevation, so you add 0.6 to 0.7 mil and confirm.
If your scope reads in minutes of angle, the same logic applies with a different constant, since one true minute subtends about 1.047 inches at one hundred yards and scales from there.4 Many shooters round that to a clean inch per hundred yards for field math, which is the shooter's MOA convention, and the small difference only begins to matter at longer range. Either way, you are translating a measured miss into the angular language your turret speaks, then dialing that amount and verifying the result.
Filling the gaps between your anchors
A handful of confirmed drops does not leave you with holes, because bullet drop follows a smooth, predictable curve as long as the bullet stays supersonic. Between two anchors you measured, the come-up for an in-between distance sits very close to a straight-line estimate, so you can interpolate the gaps with confidence. If four hundred yards confirmed at a certain come-up and six hundred at another, the five hundred yard value lands near the midpoint of the two.
This is why you do not need to shoot every hundred-yard increment to build a usable card. A few well-spaced anchors define the curve, and arithmetic fills the spaces between them closely enough to center a hit, especially inside the ranges where most shooting happens. You can always confirm an interpolated value later by shooting it, treating the interpolation as a strong estimate rather than a final answer.
The interpolation does break down as the bullet slows toward the transonic region, where the trajectory steepens and the drop stops behaving in a straight line.5 Near and past that point, the spacing between your come-ups grows faster than a simple average predicts, so you confirm those far distances directly rather than interpolating them. Knowing where your load goes transonic tells you where to stop trusting the easy math and start shooting the actual yardage.
Writing the card so it survives the field
A dope card is only useful if you can read it fast and trust it when it is wet, cold, and crumpled in a pocket. Keep the layout clean, with distance in the left column and the confirmed come-up beside it, and mark clearly which entries you measured and which you interpolated so you know how much to trust each one. A column for a base wind hold alongside the elevation turns it into a complete range card for the shot.
Record the conditions the card was built under, because a set of come-ups is only valid for the air density it was measured in. Note the density-altitude or the temperature, pressure, and elevation of the session, since the same drops will need small adjustments on a very different day. A card built at a five thousand foot density altitude will call slightly too much elevation on a cold, dense morning, and knowing the baseline lets you account for the shift.6
Protect the physical card, laminated or taped to the stock or carried in a sleeve, and keep the master copy in your data book where it cannot be lost. The field card is a working copy of the truth you collected, and the data book is the archive that lets you rebuild it, refine it, and watch how your rifle behaves across seasons. Treat both as the institutional memory of the rifle.
What can throw a card off
A dope card can be perfectly consistent and still be wrong, which is what makes a few specific errors worth naming. Each one biases your numbers in a way that looks clean on paper, so you catch them by understanding them rather than by spotting an obvious mistake.
The first is a zero that shifts between sessions. If your zero shifts between sessions, every come-up you reference from it shifts too, so confirm the zero at the start of each data-collection trip before you trust a single drop. The second is the cold bore shot, since some rifles throw the first round from a cold barrel slightly off the warm group, and a come-up built only on cold shots, or only on warm ones, may not match the shot that counts. Track where your cold bore lands relative to your zero and note it.7
The third is a vertical wind component read as elevation. A vertical component in the wind, or a misread of where the group truly centered, can nudge your confirmed come-up off by a click or two, which is why calm air and careful group measurement matter so much. The fourth is the scope itself drifting out of turret-tracking spec over time, so re-running a tall-target test every so often keeps the foundation under your card sound.
Caution. A consistent card is not the same as a correct card. Errors in zero, tracking, or conditions repeat on every line, so they sit inside numbers that look reliable. Re-confirm your zero and your tracking periodically, and treat any sudden disagreement with a solver as a prompt to investigate rather than ignore.
Checking it against a solver later
Once you have a card built from confirmed drops, a ballistic solver comes in handy, not as the source of your data but as a way to extend and audit it. You enter your bullet, your conditions, and a starting velocity, then compare the solver's predicted come-ups against the ones you measured. Where they agree, you have a model you can trust to fill ranges you have not shot yet.
Where they disagree, you let your real drops win and adjust the solver to match, a process called truing. The usual lever is velocity-truing, nudging the muzzle velocity input until the solver's predictions line up with your confirmed corrections across the distances you measured. If your near drops match but the far ones drift apart, the drag model is the more likely culprit, and adjusting the ballistic coefficient is the better fix.8 A trued solver then predicts the distances between and beyond your anchors with real authority, because it has been calibrated to your rifle rather than to a catalog.
This is the payoff of building the card by hand first. Your measured data becomes the reference that disciplines the model, the solver becomes a fast way to extend that reference to new ranges and conditions, and a ballistic-solver you have trued to confirmed drops is far more trustworthy than one running on factory numbers. You end up with the speed of software and the credibility of real measurement at the same time.
How I would build my first card
If I were building my first dope card, I would spend the first range trip entirely on the foundation rather than rushing to collect drops. I would run a tall-target test to confirm tracking, shoot a careful one hundred yard zero with confirming groups, and write down the exact conditions, treating that session as the bedrock everything else stands on. A day spent verifying the mechanics is never wasted, because it keeps a hidden error from poisoning every number that follows.
On the data-collection trips I prefer to work in calm morning air and confirm each distance with two groups, one to find the come-up and one to prove it centers. I would anchor two hundred, four hundred, six hundred, and as far as my range and my load's supersonic envelope allow, then interpolate the gaps and mark them as estimates rather than confirmed. My approach is to log every shot in a data book so the card is rebuildable, because a card you cannot reconstruct is one bad laundry day away from gone.
Only after the card proves itself on steel would I open a solver and true it to my numbers. I would enter the load and the conditions, adjust velocity until the prediction matched my confirmed drops, and then lean on the trued model to reach the distances I had not yet shot. That sequence, measure first and calibrate second, is the one I would teach anyone starting out, because it builds a card you trust for the right reason.
FAQ
How do you build a dope card without a ballistic solver?
You build a dope card without a solver by measuring confirmed drops at known distances. After verifying your scope's tracking and a solid zero, you go to each distance, dial a starting come-up, fire a group, and adjust until the group centers, then record that confirmed elevation. Repeating this at a few well-spaced distances and interpolating the gaps produces a usable card built entirely from your rifle's real performance.
How many distances do you need to confirm for a dope card?
You need only a handful of well-spaced confirmed distances, often something like two hundred, four hundred, six hundred, and eight hundred yards. Bullet drop follows a smooth curve while the bullet stays supersonic, so you can interpolate the come-ups for in-between ranges from those anchors. You confirm the far distances near the transonic region directly, since the trajectory steepens there and simple interpolation stops being accurate.
Why is a confirmed dope card more accurate than a solver prediction?
A confirmed dope card is more accurate because it records what your rifle actually did rather than what a model predicts it should do. A solver depends on estimated inputs like muzzle velocity and drag, and small errors in those inputs grow with distance. A measured drop already accounts for your true velocity, barrel, and conditions, so confirmed data tends to beat prediction at the longer ranges where input errors matter most.
Should you still use a ballistic solver after building a dope card?
You should still use a solver after building a dope card, as a tool to extend and audit your measured data. You compare its predictions to your confirmed drops, then true the solver by adjusting velocity or ballistic coefficient until it matches your real corrections. A solver calibrated to confirmed drops can then predict ranges and conditions you have not shot, combining the speed of software with the credibility of measured data.
Citations
- (2023). Dial in Your Hunting Rifle: How to Build an Accurate DOPE. MTNTOUGH.
- Cal Zant. (2014). Tactical Scopes: Mechanical Performance Part 1. PrecisionRifleBlog.com.
- (2023). Ballistics Basics Guide: Trajectory, Drop, and Zeroing. American 2A Firearms.
- Richard Mann. (2011). Mil, MOA or Inches?. Shooting Illustrated (NRA).
- (2014). Long Range Shooting: External Ballistics - The Transonic Region. The Arms Guide.
- Ron Spomer. (2021). How Altitude Changes Trajectory. Ron Spomer Outdoors.
- (2023). The Cold Bore Shot: Myth, Measure, and Material Science. Precision Rifle Basics.
- (2022). Truing Rifle Data. XLR Industries.