Age
Age in Salesforce is a calculated metric showing how long a record has been in an open or active state.
Definition
Age in Salesforce is a calculated metric showing how long a record has been in an open or active state. The most common form is days since a record was created (or since it last changed state, depending on the implementation), expressed as a number that grows over time until the record is closed. Age applies to many objects: Case Age (days since the case was opened), Opportunity Age (days since the opportunity was created or since it entered the current stage), Lead Age (days since the lead was captured), Task Age (days since the task was created without completion).
Age is the workhorse metric of operational reporting because it surfaces records that need attention. A Case open for 30 days indicates a customer waiting longer than the team's SLA; a Lead untouched for 14 days indicates marketing-to-sales handoff friction; an Opportunity sitting at 45 days in the current stage indicates a stalled deal. Mature operations teams build dashboards around Age across every relevant object, with thresholds that trigger workflow, alerts, or escalation when records exceed their expected lifecycle duration. Without Age tracking, stale records accumulate invisibly and the team loses the ability to manage workload effectively.
Age across objects and implementation patterns
Case Age and SLA monitoring
Case Age is one of the most heavily used Age metrics. The standard Case object includes an Age field that calculates days since the case was opened, automatically updated. Service teams use Case Age in dashboards showing the distribution of open cases by age bucket (less than 1 day, 1 to 3 days, 3 to 7 days, more than 7 days). Cases exceeding the SLA threshold are flagged for supervisor review or escalation. The Entitlements and Milestones feature adds more sophisticated SLA tracking, but plain Case Age is the starting point for any service operation.
Opportunity Age versus Stage Duration
Opportunity Age is the total time the opportunity has been open, while Stage Duration is the time in the current stage. Both are useful but measure different things. A deal in pipeline for 90 days total with 30 days in current stage is an old deal in a recent stage transition; a deal at 90 days total with 90 days in current stage is a stalled deal. The two metrics together describe the deal's lifecycle better than either alone, and most pipeline dashboards include both. Computing Opportunity Age is straightforward (NOW minus CreatedDate); Stage Duration requires capturing the stage entry date through automation.
Lead Age and conversion windows
Lead Age is the time since the lead was captured, often a critical metric for marketing-to-sales handoff. Industry benchmarks suggest that converting a lead within 5 minutes of capture has dramatically higher success than converting after 30 minutes, with diminishing returns extending to days. Lead Age dashboards expose where the handoff is breaking: which leads are aging beyond the threshold before any sales follow-up, what is the average age at first contact, how does Lead Age correlate with eventual conversion. Closing the loop on Lead Age requires both the metric and a discipline of acting on it.
Task Age and follow-up discipline
Task Age, especially for tasks past their Due Date, signals follow-up debt accumulating in the team. Overdue tasks aging beyond 7 days suggest a rep is failing to keep their queue clean; aging beyond 14 days suggests the task may no longer be relevant. Task Age dashboards drive the productivity coaching conversation: which reps maintain a clean task queue versus which let tasks pile up. Combined with task type, the Age view shows which kinds of follow-up are most likely to slip (cold outreach calls aging fast versus customer-specific commitments aging less).
Calculating Age in reports and formulas
Age is typically calculated through formula fields or report-level summary calculations. The basic formula is TODAY minus CreatedDate, producing a number of days. More sophisticated implementations exclude weekends and holidays for an SLA-relevant business-day calculation, or compute Age in hours rather than days for high-velocity processes. Report Bucket fields let users group Age into ranges (0 to 1 day, 1 to 3 days, etc.) for distribution analysis. CRM Analytics dashboards extend the analysis with more advanced bucketing, trend analysis, and predictive scoring.
Aging in dashboards and alerts
Age becomes operationally valuable when it drives dashboards, reports, and alerts that the team actually uses. Standard patterns include: aging buckets showing distribution of open records, top-N old records highlighting the most aged outliers, trend reports showing whether average Age is improving or declining over time, and alerts when specific records exceed thresholds. The alerts can be email notifications, Chatter posts, mobile push notifications, or automated tasks to assign owners follow-up work. Mature service and sales operations teams pair the metric with disciplined follow-up to drive Age down over time.
Pitfalls in Age tracking
Several common pitfalls reduce the value of Age tracking. Closing records that should remain open just to reset the Age clock is gaming the metric without solving the underlying problem. Defining Age inconsistently across teams creates dashboards that disagree about basic facts. Ignoring time zones when computing Age can shift values by a day, which matters for SLA reporting on cases near the threshold. Calculating Age without filtering for the right status (closed cases should not appear in open-case age reports) clutters the view. Each pitfall is preventable with clear definitions and consistent implementation, but they recur in orgs that have not invested in operational discipline around metrics.
Age as a leading indicator of operational health
Beyond the basic per-object Age tracking, mature organizations treat Age as a leading indicator of overall operational health. Aggregate metrics like the average Age of all open Cases, the median Age of newly created Opportunities still in early stages, and the seventy-fifth-percentile Age across the entire pipeline tell a story about whether the team is staying current or falling behind. A trend of rising average Case Age over several weeks usually signals an under-staffed service team, a problem with the case routing algorithm, or a backlog from a recent product issue spike. A trend of rising Opportunity Age suggests sales execution problems that show up in win rate weeks or months later. By the time these trends produce obvious downstream effects (missed SLAs, missed quotas), they have usually been visible in the Age metrics for a meaningful amount of time. Operations teams that watch Age trends weekly catch these problems early. Operations teams that look only at outcome metrics (win rate, CSAT, response time at close) react late, after the damage has accumulated. The discipline of watching Age trends as part of the regular operational rhythm is one of the highest-leverage practices a Salesforce-driven business operation can adopt. It costs nothing to implement once the metrics are in place; the cost is the cognitive overhead of watching the trends and acting on what they reveal. Programs that have made this practice routine consistently outperform programs that have not, across both service and sales contexts.
Implement and operationalize Age metrics
Implementing Age metrics is straightforward, but operationalizing them is where the value comes from. The workflow below covers the standard sequence for adding Age to a Salesforce reporting program.
- Identify the objects and Age definitions to track
Inventory the objects where Age tracking will add value: Case, Lead, Opportunity, Task, custom objects relevant to the business. For each, agree on the Age definition: total time open, time in current state, business days versus calendar days. Document the definitions in the org's reporting wiki so future analysts know exactly what each Age field represents. Misaligned definitions are the most common source of metric confusion.
- Implement Age fields and bucketing
Add Age fields where the standard object does not provide one (formula field calculating TODAY minus CreatedDate). For business-day calculations, build a more complex formula that subtracts weekends, or use a custom function from the AppExchange. Configure bucket fields in reports for grouping Age into ranges. Test the fields with sample records and confirm the math matches expectations, particularly around time zones and date boundaries.
- Build the operational dashboards
Create the dashboards that surface Age in the operational cadence: open cases by age bucket and owner, leads by age and source, opportunities by age and stage. Pin these dashboards in the relevant app home pages so the team sees them daily. Schedule the dashboards for weekly review in the team's standup or pipeline meeting. The dashboard is not the goal; the conversation it drives is.
- Add alerts and automation
Build alerts that fire when individual records exceed Age thresholds: an email to the case owner when a case ages past 5 days, a Chatter post in the team feed when a lead ages past 24 hours, a task created when an opportunity ages past 60 days in any stage. The alerts should drive specific action, not just notification. Tune the thresholds based on actual operational performance: too low and alerts become noise, too high and they fire only after damage is done.
- TODAY-based formulas refresh only when records are queried or saved. Dashboards may show slightly stale values until records are accessed.
- Time zones affect Age calculation. A record created at 11 PM EST and viewed at 9 AM EST the next day shows Age of 1 day, but viewed from PST shows 0 days.
- Business-day calculations require careful logic for weekends, holidays, and timezone-aware boundaries. Off-the-shelf formulas often miss edge cases.
- Age dashboards must filter for the right status (open versus closed). Including closed records inflates the average and hides the real issue.
- Gaming the metric (closing records prematurely) is a real risk. Pair Age with quality measures to prevent the gaming.
Trust & references
Straight from the source - Salesforce's reference material on Age.
- Formula FieldsSalesforce Help
- Reports and DashboardsSalesforce Help
About the Author
Dipojjal Chakrabarti is a B2C Solution Architect with 29 Salesforce certifications and over 13 years in the Salesforce ecosystem. He runs salesforcedictionary.com to help admins, developers, architects, and cert/interview candidates sharpen their fundamentals. More about Dipojjal.
Test your knowledge
Q1. What type of data does Age typically work with?
Q2. What is the primary purpose of Age in Salesforce?
Q3. Who benefits most from Age in an organization?
Discussion
Loading discussion…