Period to date, usually shortened to PTD, is a running total of a chosen metric from a start date you set through the current day. The start date is yours to define, which is what separates PTD from month-to-date, quarter-to-date, or year-to-date figures that always begin on a fixed calendar boundary. You reach for PTD whenever the thing you want to measure — a pay period, a campaign, a project phase, a production cycle — doesn’t line up with the calendar.
The metric itself can be almost anything measurable: revenue, labor costs, hours worked, units shipped. What matters is that the period reflects an actual business cycle rather than an accounting convention. Each day adds new data to the total, so the PTD figure you pull on Tuesday will differ from the one you pulled on Monday.
How PTD Differs From MTD, QTD, and YTD
Month-to-date, quarter-to-date, and year-to-date all share one trait: the calendar picks their start dates. MTD begins on the first of the current month. QTD begins on the first day of the current fiscal quarter. YTD begins on the first day of the fiscal year. You don’t choose.
PTD removes that constraint. If a retailer launches a 45-day promotion on May 17th, PTD starts on May 17th. Standard MTD reporting would fragment that campaign across May, June, and possibly July, forcing analysts to stitch partial months together to see the full picture. A PTD figure captures the whole promotion in one number.
The distinction is worth stating plainly. YTD tells you how the year is going. QTD tells you how the quarter is going. MTD tells you how the month is going. PTD tells you how a specific thing is going, on its own schedule. When your period happens to align with a calendar boundary, PTD and the corresponding calendar metric produce the same number. For most operational tracking, they don’t align, which is where PTD earns its place.
How to Calculate a PTD Figure
The math is basic addition with a defined starting point. Pick the start date, pick the metric, and sum every relevant transaction from that start date through today.
Say you’re tracking PTD sales for a marketing campaign that began October 1st. Today is October 25th. Add up daily sales across those 25 days. If sales averaged $5,000 a day, PTD sales are $125,000.
That number on its own is just a total. It becomes useful when you compare it against the period’s goal and the time elapsed. Suppose the campaign’s 42-day sales target is $210,000. Twenty-five days in, roughly 60% of the time has passed, and the $125,000 PTD figure represents about 59.5% of the goal. Slightly behind a straight-line pace, but close enough that a strong weekend could close the gap. That’s the kind of early read PTD is built for.
Projecting the final result uses the same arithmetic in reverse. Divide the PTD total by days elapsed to get a daily average, then multiply by the total days in the period. Here, $125,000 divided by 25 days is a $5,000 daily average; times 42 days, the projected finish is $210,000. The projection is only as good as the assumption behind it, which is that daily activity stays reasonably stable. When it doesn’t, the number can mislead you.
Where PTD Reporting Gets Used
Payroll
Payroll is where most people encounter PTD without knowing the label. Companies on bi-weekly pay cycles track hours, commissions, overtime, and tax accruals from the start of each 14-day period, not from the first of the month. A period that begins on a Wednesday and ends on a Tuesday two weeks later has no relationship to calendar months, and the PTD figures for that cycle are exactly what shows up on the paycheck.
When a manager asks how much labor cost has been incurred “so far this pay period,” that’s a PTD question. The answer includes wages, employer tax contributions, and benefits accruals from the start of the period through today.
Project Cost Tracking
Long-term projects rarely align with fiscal years, which makes them natural candidates for PTD tracking. An 18-month construction contract has its own start date, its own budget, and its own milestones. Tracking costs on a YTD basis would lump the project in with unrelated spending and reset every January, neither of which helps a project manager judge whether the job is on budget.
PTD cost tracking also connects directly to the percentage-of-completion method that federal tax law requires for most long-term contracts. Taxable income is recognized by comparing costs incurred to date against estimated total costs.1Office of the Law Revision Counsel. 26 USC 460 – Special Rules for Long-Term Contracts If a project’s estimated total cost is $2 million and PTD costs have reached $800,000, the project is 40% complete for income recognition. The PTD figure is the numerator.
Campaigns and Product Launches
Marketing campaigns and launches almost always run on custom timelines: a 90-day launch assessment, a 6-week holiday push, a 10-day flash sale. PTD lets you measure each on its own terms. Sixty days into a 90-day launch with PTD revenue at $400,000 against a $750,000 target, you’re at 53% of goal with 67% of the time elapsed. That’s a signal you can act on while there’s still time to adjust pricing, ad spend, or inventory.
Retail Periods
Much of U.S. retail runs on the 4-5-4 calendar maintained by the National Retail Federation, which divides the fiscal year into four 13-week quarters, each split into periods of 4, 5, and 4 weeks. Every period holds the same number of Saturdays and Sundays, which matters for businesses whose sales swing on weekend traffic. Retailers using this calendar run PTD reports against those periods rather than calendar months. The IRS accommodates this through the 52-53 week tax year, which lets a business end its fiscal year on the same day of the week each year.2Internal Revenue Service. Publication 538 – Accounting Periods and Methods
Using PTD to Build a Run Rate
One of the most common downstream uses of PTD is calculating a run rate. Take the PTD figure, divide by periods elapsed, and multiply by the total number of periods you want to project across.
If PTD revenue through the first 8 weeks of a fiscal quarter is $2.4 million, the weekly run rate is $300,000. Multiply by 13 weeks and the projected quarterly revenue is $3.9 million. Scale that to four quarters and you have an annualized run rate of $15.6 million.
Run rates are handy for quick sanity checks, but they carry an assumption worth respecting: the future will look like the recent past. That assumption breaks when seasonality enters the picture (retail Q4 doesn’t predict Q1), when the PTD window includes a one-time event like a large contract, or when the period is so short that random variation dominates. A run rate built on two weeks of data is a guess in the shape of math. Built on nine months, it’s a reasonable forecast. In between, judgment matters more than the formula.
Where PTD Can Mislead
The flexibility that makes PTD useful is also what makes it easy to abuse. Because you choose the start date, you can frame performance to flatter or scare, deliberately or not. Starting the window the day after a slump improves the numbers. Starting it the day before a big sale inflates the daily average. Anyone reviewing a PTD figure should ask why the period begins where it does.
Comparability is a second issue. Everyone knows when January 1st is; nobody outside your company knows what “Period 7” or “Sprint 14” means. PTD reports need clear labeling: start date, expected end date, and total length of the period. Without that framing, the number floats free of context.
Incomplete-period distortion is the most common analytical trap. Early in a period, the daily average is volatile — one strong or weak day swings the projection dramatically. Extrapolating from three days of data in a 42-day period produces a projection with a huge error margin. As a working rule, PTD projections start to become meaningful only after about a third of the period has elapsed, and even then only if daily activity is reasonably stable.
PTD also doesn’t account for known future events inside the period. If you’re 10 days into a 30-day window and a price increase is scheduled for day 15, the daily average from the first 10 days will understate the likely finish. Careful forecasting adjusts for known schedule changes instead of assuming a flat rate.
PTD Is an Internal Metric, Not a Tax Year
Custom reporting periods don’t replace the tax year. Federal tax law recognizes three options for computing taxable income: a calendar year ending December 31st, a fiscal year ending on the last day of any other month, or a 52-53 week tax year that always ends on the same day of the week.3Office of the Law Revision Counsel. 26 USC 441 – Period for Computation of Taxable Income The 52-53 week election is made by attaching a statement to your return specifying the ending month, the day of the week, and whether the year closes on the last occurrence of that day in the month or the nearest occurrence to month-end.4eCFR. 26 CFR 1.441-2 – Election of Taxable Year Consisting of 52-53 Weeks
None of that constrains how you use PTD internally. Payroll can run 14-day periods, project managers can track 18-month timelines, and marketing can measure 45-day campaigns, while finance maps everything back to the official tax year for external reporting. The reconciliation work sits at the accounting layer, not the operational one where PTD data is generated and used.