{"id":200210,"date":"2025-07-16T10:24:20","date_gmt":"2025-07-16T14:24:20","guid":{"rendered":"https:\/\/www.attendancebot.com\/blog\/?p=200210"},"modified":"2025-07-16T10:30:21","modified_gmt":"2025-07-16T14:30:21","slug":"pto-in-sprint-planning-tools-tips-tactics","status":"publish","type":"post","link":"https:\/\/www.attendancebot.com\/blog\/pto-in-sprint-planning-tools-tips-tactics\/","title":{"rendered":"PTO in Sprint Planning: Tools, Tips, and Team Tactics"},"content":{"rendered":"<p><span style=\"font-weight: 400;\">Every sprint starts with the best of intentions. The backlog is refined, the team commits confidently, and the burndown chart is ready to tell a satisfying story. But then someone takes a day off. And then another. Before you know it, your tightly scoped sprint is fraying at the edges &#8211; tasks are rolling over, velocity plummets, and standups start to sound like confessionals.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">Time off is a normal part of work and is essential for the long-term health of the team. But when PTO isn\u2019t factored into sprint planning from the get-go, it creates a ripple effect that derails delivery and frustrates everyone involved. This blog unpacks how unplanned (or even poorly planned) PTO can sneak up on your agile team\u00a0 &#8211;\u00a0 and what you can do to keep sprints on track, even when key players are out.<\/span><\/p>\n\n<div class=\"lyte-wrapper fourthree\" style=\"width:960px;max-width:100%;margin:5px auto;\"><div class=\"lyMe\" id=\"WYL_2A9rkiIcnVI\"><div id=\"lyte_2A9rkiIcnVI\" data-src=\"https:\/\/blog.attendancebot.com\/wp-content\/plugins\/wp-youtube-lyte\/lyteCache.php?origThumbUrl=%2F%2Fi.ytimg.com%2Fvi%2F2A9rkiIcnVI%2Fhqdefault.jpg\" class=\"pL\"><div class=\"tC\"><div class=\"tT\"><\/div><\/div><div class=\"play\"><\/div><div class=\"ctrl\"><div class=\"Lctrl\"><\/div><div class=\"Rctrl\"><\/div><\/div><\/div><noscript><a href=\"https:\/\/youtu.be\/2A9rkiIcnVI\" rel=\"nofollow\"><img loading=\"lazy\" decoding=\"async\" src=\"https:\/\/blog.attendancebot.com\/wp-content\/plugins\/wp-youtube-lyte\/lyteCache.php?origThumbUrl=https%3A%2F%2Fi.ytimg.com%2Fvi%2F2A9rkiIcnVI%2F0.jpg\" alt=\"YouTube video thumbnail\" width=\"960\" height=\"700\" \/><br \/>Watch this video on YouTube<\/a><\/noscript><\/div><\/div><div class=\"lL\" style=\"max-width:100%;width:960px;margin:5px auto;\"><\/div><\/p>\n<h2><span style=\"font-weight: 400;\">What Is Sprint Planning, and Why Does It Matter?<\/span><\/h2>\n<p><span style=\"font-weight: 400;\">Sprint planning is a core ceremony in Agile frameworks like Scrum. It\u2019s where the team decides what work can be completed in a fixed time period &#8211; typically one or two weeks &#8211; based on priorities, capacity, and historical velocity. The goal is to create a realistic plan that helps the team focus and deliver value in a short, iterative cycle.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">A <strong><a href=\"https:\/\/www.attendancebot.com\/blog\/how-to-create-your-best-weekly-sprints\/?utm_source=blog&amp;utm_medium=in-line&amp;utm_campaign=PTO-in-sprint-planning\">sprint plan<\/a> <\/strong>typically includes:<\/span><\/p>\n<ul>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">A clearly defined sprint goal<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">A list of prioritized tasks (or user stories) pulled from the backlog<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Capacity estimates based on team availability<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Commitments from team members on what can be completed<\/span><span style=\"font-weight: 400;\"><br \/>\n<\/span><\/li>\n<\/ul>\n<h2><span style=\"font-weight: 400;\">What Is PTO, and How Does It Affect Sprints?<\/span><\/h2>\n<p><span style=\"font-weight: 400;\"><strong><a href=\"https:\/\/www.attendancebot.com\/blog\/pto-software\/?utm_source=blog&amp;utm_medium=in-line&amp;utm_campaign=PTO-in-sprint-planning\">Paid Time Off (PTO)<\/a> <\/strong>includes vacation days, personal time, and other forms of leave that allow employees to step away from work while still getting paid. While PTO is essential for employee well-being, it can significantly impact team output, especially when it overlaps with a sprint.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">When time off isn\u2019t accurately accounted for during planning, the result is often:<\/span><\/p>\n<ul>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Overcommitting the team<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Delayed deliverables<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Bottlenecks when key contributors are absent<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Team frustration and loss of morale<\/span><\/li>\n<\/ul>\n<p><span style=\"font-weight: 400;\">In short, ignoring PTO when building a sprint plan is like ignoring weather forecasts when planning a hike &#8211; you <\/span><i><span style=\"font-weight: 400;\">might<\/span><\/i><span style=\"font-weight: 400;\"> be fine, but you\u2019re probably in for a rough surprise.<\/span><\/p>\n<p><img loading=\"lazy\" decoding=\"async\" class=\"aligncenter wp-image-200212 size-epcl_single_content\" src=\"https:\/\/blog.attendancebot.com\/wp-content\/uploads\/2025\/07\/ChatGPT-Image-Jul-16-2025-06_56_57-PM-min-675x450.jpg\" alt=\"What Is PTO, and How Does It Affect Sprints?\" width=\"668\" height=\"445\" srcset=\"https:\/\/blog.attendancebot.com\/wp-content\/uploads\/2025\/07\/ChatGPT-Image-Jul-16-2025-06_56_57-PM-min-675x450.jpg 675w, https:\/\/blog.attendancebot.com\/wp-content\/uploads\/2025\/07\/ChatGPT-Image-Jul-16-2025-06_56_57-PM-min-300x200.jpg 300w, https:\/\/blog.attendancebot.com\/wp-content\/uploads\/2025\/07\/ChatGPT-Image-Jul-16-2025-06_56_57-PM-min-1024x683.jpg 1024w, https:\/\/blog.attendancebot.com\/wp-content\/uploads\/2025\/07\/ChatGPT-Image-Jul-16-2025-06_56_57-PM-min-768x512.jpg 768w, https:\/\/blog.attendancebot.com\/wp-content\/uploads\/2025\/07\/ChatGPT-Image-Jul-16-2025-06_56_57-PM-min-100x67.jpg 100w, https:\/\/blog.attendancebot.com\/wp-content\/uploads\/2025\/07\/ChatGPT-Image-Jul-16-2025-06_56_57-PM-min.jpg 1536w\" sizes=\"auto, (max-width: 668px) 100vw, 668px\" \/><\/p>\n<h2><span style=\"font-weight: 400;\">Why Sprint Plans Fall Apart When PTO Is an Afterthought<\/span><\/h2>\n<p><span style=\"font-weight: 400;\">In theory, sprint planning is a clean, data-driven process. You\u2019ve got your historical velocity, your refined backlog, and a team ready to commit. But that plan assumes something deceptively simple: that everyone will be available. Once PTO enters the picture &#8211; especially last-minute or unaccounted-for leave &#8211; the whole structure wobbles.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">Here\u2019s why:<\/span><\/p>\n<h3><span style=\"font-weight: 400;\">1. Capacity Gets Overestimated<\/span><\/h3>\n<p><span style=\"font-weight: 400;\">If PTO isn\u2019t factored into planning, your velocity estimates are inflated from the start. You\u2019re setting goals based on ideal capacity, not actual team availability. This leads to overcommitment, missed deliverables, and stressed-out devs scrambling to pick up the slack.<\/span><\/p>\n<h3><span style=\"font-weight: 400;\">2. Dependencies Breakdown<\/span><\/h3>\n<p><span style=\"font-weight: 400;\">Agile teams work cross-functionally, and often one person\u2019s task is a prerequisite for the next. When a key contributor is out, say, your only QA engineer or the frontend dev on a major feature, it creates a bottleneck no one accounted for. Work stalls, blockers pile up, and your carefully plotted sprint burndown graph flatlines.<\/span><\/p>\n<h3><span style=\"font-weight: 400;\">3. Morale Takes a Hit<\/span><\/h3>\n<p><span style=\"font-weight: 400;\">When the team consistently misses sprint goals due to avoidable planning blind spots, it wears them down. Developers lose confidence in the process. Stakeholders start asking why nothing\u2019s ever \u201cdone.\u201d The blame game starts &#8211; not because people aren\u2019t working hard, but because they\u2019re planning with incomplete information.<\/span><\/p>\n<h3><span style=\"font-weight: 400;\">4. Manual Workarounds Don\u2019t Scale<\/span><\/h3>\n<p><span style=\"font-weight: 400;\">Some teams try to track PTO with shared calendars, spreadsheets, or Slack reminders. But these solutions are error-prone, easy to forget, and disconnected from sprint planning tools. When time-off info lives outside the systems used to plan work, it\u2019s no wonder capacity gets misjudged.<\/span><\/p>\n<h2><span style=\"font-weight: 400;\">How High-Performing Teams Plan Sprints Around Time Off<\/span><\/h2>\n<p><span style=\"font-weight: 400;\">Elite Agile teams don\u2019t wait to be surprised by PTO &#8211; they expect it, plan for it, and adapt around it. Their secret isn\u2019t superhuman velocity or burnout-fueled heroics. It\u2019s visibility, process maturity, and a little automation.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">Here\u2019s what sets them apart:<\/span><\/p>\n<h3><strong>1. They Treat Availability as a First-Class Planning Input<\/strong><\/h3>\n<p><span style=\"font-weight: 400;\">Before discussing velocity or story points, these teams ask: <\/span><i><span style=\"font-weight: 400;\">\u201cWho\u2019s actually available next sprint?\u201d<\/span><\/i><span style=\"font-weight: 400;\"> It\u2019s a small question with huge impact.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">During sprint planning, availability is reviewed <\/span><i><span style=\"font-weight: 400;\">before<\/span><\/i><span style=\"font-weight: 400;\"> commitments are made. This often involves:<\/span><\/p>\n<ul>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Scanning team calendars for out-of-office blocks<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Checking shared leave planners (e.g., Google Calendar, Outlook)<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Reviewing recurring leave trends (e.g., public holidays, school breaks)<\/span><\/li>\n<\/ul>\n<p><span style=\"font-weight: 400;\">According to the <\/span>Scrum Guide<span style=\"font-weight: 400;\">, planning should include \u201ccapacity planning for the upcoming Sprint\u201d and explicitly account for time-off or other external obligations <strong>(<\/strong><\/span><strong><a href=\"https:\/\/www.scrum.org\/resources\/what-is-sprint-planning\">Scrum.org<\/a><\/strong><span style=\"font-weight: 400;\"><strong>)<\/strong>.<\/span><\/p>\n<h3><strong>2. They Integrate Leave Data Into Their Sprint Tools<\/strong><\/h3>\n<p><span style=\"font-weight: 400;\">Manual PTO tracking isn\u2019t just inefficient &#8211; it\u2019s risky. Relying on shared calendars or Slack messages means availability data is scattered and easily missed during sprint planning.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">Instead, high-functioning teams use integrated tools that:<\/span><\/p>\n<ul>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Sync directly with HR or leave management systems<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Surface real-time availability inside Jira, Asana, Trello, or ClickUp<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Send automated Slack alerts when team members log PTO<\/span><\/li>\n<\/ul>\n<p><span style=\"font-weight: 400;\">For example,<\/span><a href=\"https:\/\/www.attendancebot.com\/?utm_source=blog&amp;utm_medium=in-line&amp;utm_campaign=PTO-in-sprint-planning\"> <b>AttendanceBot<\/b><\/a><span style=\"font-weight: 400;\"> (for Slack and Microsoft Teams) automatically syncs leave requests into shared calendars and provides visual indicators for time-off during planning sessions. It reduces the need for back-and-forth by surfacing availability <\/span><i><span style=\"font-weight: 400;\">where the work happens<\/span><\/i><span style=\"font-weight: 400;\">.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">Other integrations that help:<\/span><\/p>\n<ul>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><a href=\"https:\/\/support.atlassian.com\/jira-software-cloud\/docs\/sync-jira-issues-with-your-google-calendar\/\"><b>Jira + Google Calendar<\/b><\/a><span style=\"font-weight: 400;\"> (sync issue due dates with calendar views)<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><a href=\"https:\/\/www.teamgantt.com\/blog\/plan-around-vacation\"><b>TeamGantt<\/b><\/a><span style=\"font-weight: 400;\"> (features built-in vacation tracking for project timelines)<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><a href=\"https:\/\/www.parabol.co\/blog\/agile-sprint-planning-guide\/\"><b>Parabol<\/b><\/a><span style=\"font-weight: 400;\"><span style=\"font-weight: 400;\"> (Sprint planning templates with team availability tracking)<\/span><\/span><img loading=\"lazy\" decoding=\"async\" class=\"aligncenter wp-image-200213 size-epcl_single_content\" src=\"https:\/\/blog.attendancebot.com\/wp-content\/uploads\/2025\/07\/ChatGPT-Image-Jul-16-2025-07_01_33-PM-min-e1752675594570-700x409.jpg\" alt=\"Why Sprint Plans Fall Apart When PTO Is an Afterthought\" width=\"668\" height=\"390\" srcset=\"https:\/\/blog.attendancebot.com\/wp-content\/uploads\/2025\/07\/ChatGPT-Image-Jul-16-2025-07_01_33-PM-min-e1752675594570-700x409.jpg 700w, https:\/\/blog.attendancebot.com\/wp-content\/uploads\/2025\/07\/ChatGPT-Image-Jul-16-2025-07_01_33-PM-min-e1752675594570-300x175.jpg 300w, https:\/\/blog.attendancebot.com\/wp-content\/uploads\/2025\/07\/ChatGPT-Image-Jul-16-2025-07_01_33-PM-min-e1752675594570-1024x598.jpg 1024w, https:\/\/blog.attendancebot.com\/wp-content\/uploads\/2025\/07\/ChatGPT-Image-Jul-16-2025-07_01_33-PM-min-e1752675594570-768x448.jpg 768w, https:\/\/blog.attendancebot.com\/wp-content\/uploads\/2025\/07\/ChatGPT-Image-Jul-16-2025-07_01_33-PM-min-e1752675594570-100x58.jpg 100w, https:\/\/blog.attendancebot.com\/wp-content\/uploads\/2025\/07\/ChatGPT-Image-Jul-16-2025-07_01_33-PM-min-e1752675594570.jpg 1518w\" sizes=\"auto, (max-width: 668px) 100vw, 668px\" \/>\n<p><span style=\"font-weight: 400;\"><br \/>\n<\/span><\/li>\n<\/ul>\n<h3><b>3. They Adjust Commitments Based on Actual Capacity &#8211; Not Ideal Scenarios<\/b><\/h3>\n<p><span style=\"font-weight: 400;\">Once availability is visible, the smartest teams scale their sprint scope accordingly. Instead of loading up the same number of points every sprint, they flex the workload based on who\u2019s in and for how long.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">If two engineers are out for three days, that\u2019s roughly <\/span>25-30% less capacity<span style=\"font-weight: 400;\">, and the sprint plan reflects that. Features might be broken down into smaller deliverables, non-essential stories might be pushed to the backlog, or the team might commit to fewer tickets altogether.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">This isn\u2019t about lowering the bar &#8211; it\u2019s about being transparent with stakeholders and setting expectations early. A recent report by <\/span>Atlassian notes that teams with strong stakeholder alignment \u201cdeliver more predictably and are 2x more likely to meet deadlines\u201d <strong>(<a href=\"https:\/\/community.atlassian.com\/forums\/Official-Atlassian-Events\/Atlassian-Unveils-the-Future-of-Teamwork-Key-Highlights-from-the\/ba-p\/2999000#:~:text=Connecting%20Disconnected%20Teams,%2C%E2%80%9D%20emphasized%20Cannon%2DBrooks.\">State of Teams Report, Atlassian<\/a>).<\/strong><\/p>\n<h3><b>4. They Normalize Early and Ongoing PTO Communication<\/b><\/h3>\n<p><span style=\"font-weight: 400;\">Culture is key. Even with the best tools, sprint plans fall apart when team members feel uncomfortable announcing PTO, or do it too late.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">High-performing teams create regular rituals for surfacing upcoming time off, such as:<\/span><\/p>\n<ul>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">A quick round during retros: \u201cAnyone planning time off next sprint?\u201d<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">A shared Slack thread or Notion page for upcoming absences<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Monthly reminders for the team to log leave into the system (triggered by bots like AttendanceBot or Geekbot)<\/span><\/li>\n<\/ul>\n<p><span style=\"font-weight: 400;\">It\u2019s not about policing time off &#8211; it\u2019s about respecting it enough to plan properly around it. <\/span><a href=\"https:\/\/hbr.org\/2025\/05\/what-people-get-wrong-about-psychological-safety?tpcc=orgsocial_edit&amp;\"><span style=\"font-weight: 400;\"><strong>According to<\/strong> <\/span><b>HBR<\/b><\/a><span style=\"font-weight: 400;\">, teams that foster psychological safety around work-life balance report \u201chigher trust, more sustainable pace, and better creative output.\u201d<\/span><\/p>\n<h3><b>5. They Use Forecasting to Spot Risks Ahead of Time<\/b><\/h3>\n<p><span style=\"font-weight: 400;\">Advanced teams take it a step further with capacity forecasting. They don\u2019t just track who\u2019s out &#8211; they use trends to spot upcoming constraints. For example:<\/span><\/p>\n<ul>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Are multiple team members taking leave around the same time every quarter?<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Is PTO spiking right before a major release window?<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Are there cross-team dependencies that could break if one team\u2019s capacity drops?<\/span><\/li>\n<\/ul>\n<h2><b>Why It\u2019s Okay to Deliver Less When People Are Out<\/b><\/h2>\n<p><span style=\"font-weight: 400;\">Even when availability drops, many teams still try to deliver the full sprint scope- convinced they can \u201cmake it work.\u201d It\u2019s a common trap: the sprint was agreed upon, stakeholders are expecting results, and reducing scope feels like a failure. But that mindset turns PTO into a silent stressor.<\/span><\/p>\n<h3><b>Planning to Full Capacity Isn\u2019t Realistic<\/b><\/h3>\n<p><span style=\"font-weight: 400;\">Most sprints are planned close to 100% capacity. When someone takes even a single day off, there\u2019s suddenly no buffer for delays, blockers, or reviews. Instead of adjusting the plan, teams often redistribute work on the fly &#8211; putting extra pressure on available teammates.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">This leads to:<\/span><\/p>\n<ul>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Lower-quality code from rushed handovers<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Frustration from taking on unfamiliar tasks<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Skipped QA or documentation to meet deadlines<\/span><\/li>\n<\/ul>\n<p><span style=\"font-weight: 400;\">In a healthy Agile process, time off should be treated the same way you\u2019d treat a dependency delay or a security patch &#8211; something that changes the delivery landscape, not something to ignore and &#8220;work around.&#8221;<\/span><\/p>\n<h3><b>Normalize Reducing Scope When Needed<\/b><\/h3>\n<p><span style=\"font-weight: 400;\">The fix isn\u2019t about working harder &#8211; it\u2019s about planning smarter. High-performing teams set clear expectations: if someone\u2019s out and capacity dips, <\/span>scope should shrink<span style=\"font-weight: 400;\">. Communicating this early avoids disappointment later.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">Velocity over time stays more stable, and the team avoids overpromising. This doesn\u2019t mean taking it easy &#8211; it means delivering predictably without grinding people down when capacity drops.<\/span><\/p>\n<h2><b>How to Communicate PTO-Driven Changes<\/b><\/h2>\n<p><span style=\"font-weight: 400;\">Even with smart planning, the Agile Delivery Manager still needs to <\/span>explain<span style=\"font-weight: 400;\"> capacity shifts to stakeholders. The challenge? It can feel like making excuses, especially in a culture focused on velocity and constant delivery.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">Here\u2019s how to keep those conversations productive.<\/span><\/p>\n<h3><b>Use Data, Not Apologies<\/b><\/h3>\n<p><span style=\"font-weight: 400;\">When communicating a sprint adjustment due to PTO, lead with facts:<\/span><\/p>\n<ul>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">\u201cOur sprint capacity is at 80% due to scheduled time off.\u201d<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">\u201cTwo contributors will be out next week, which reduces frontend bandwidth by 40%.\u201d<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">\u201cWe\u2019ve adjusted the scope accordingly to ensure quality and avoid <strong><a href=\"https:\/\/www.attendancebot.com\/blog\/workplace-burnout\/?utm_source=blog&amp;utm_medium=in-line&amp;utm_campaign=PTO-in-sprint-planning\">burnout<\/a><\/strong>.\u201d<\/span><\/li>\n<\/ul>\n<p><span style=\"font-weight: 400;\">This framing shifts the focus from blame to context. Use capacity charts, team calendars, or time-off reports (via tools like<\/span><a href=\"https:\/\/www.attendancebot.com\/\"> <b>AttendanceBot<\/b><\/a><span style=\"font-weight: 400;\">) to show what changed, not why someone\u2019s time off is inconvenient.<\/span><\/p>\n<h3><b>Offer a Clear Re-Alignment Plan<\/b><\/h3>\n<p><span style=\"font-weight: 400;\">Stakeholders are less concerned about <\/span><i><span style=\"font-weight: 400;\">why<\/span><\/i><span style=\"font-weight: 400;\"> the sprint changed and more concerned about <\/span><i><span style=\"font-weight: 400;\">what happens next<\/span><\/i><span style=\"font-weight: 400;\">. Focus on solutions:<\/span><\/p>\n<ul>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">What stories are moving out of scope?<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">When will they be picked up?<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">What impact (if any) does this have on upcoming releases?<\/span><\/li>\n<\/ul>\n<p><span style=\"font-weight: 400;\">When the plan is transparent and tied to clear capacity data, stakeholders are more likely to respond with understanding, not micromanagement.<\/span><\/p>\n<h3><b>Make It Routine, Not Reactive<\/b><\/h3>\n<p><span style=\"font-weight: 400;\">The more often your planning accounts for time off, the less surprising it is when changes occur. When every sprint includes a brief capacity overview, PTO-driven shifts feel routine, not disruptive. It builds confidence and sets a culture where both delivery and downtime are respected.<\/span><\/p>\n<p><img loading=\"lazy\" decoding=\"async\" class=\"aligncenter wp-image-200214 size-epcl_single_content\" src=\"https:\/\/blog.attendancebot.com\/wp-content\/uploads\/2025\/07\/ChatGPT-Image-Jul-16-2025-07_14_43-PM-min-300x450.jpg\" alt=\"How to Communicate PTO-Driven Changes\" width=\"300\" height=\"450\" srcset=\"https:\/\/blog.attendancebot.com\/wp-content\/uploads\/2025\/07\/ChatGPT-Image-Jul-16-2025-07_14_43-PM-min-300x450.jpg 300w, https:\/\/blog.attendancebot.com\/wp-content\/uploads\/2025\/07\/ChatGPT-Image-Jul-16-2025-07_14_43-PM-min-200x300.jpg 200w, https:\/\/blog.attendancebot.com\/wp-content\/uploads\/2025\/07\/ChatGPT-Image-Jul-16-2025-07_14_43-PM-min-683x1024.jpg 683w, https:\/\/blog.attendancebot.com\/wp-content\/uploads\/2025\/07\/ChatGPT-Image-Jul-16-2025-07_14_43-PM-min-768x1152.jpg 768w, https:\/\/blog.attendancebot.com\/wp-content\/uploads\/2025\/07\/ChatGPT-Image-Jul-16-2025-07_14_43-PM-min-67x100.jpg 67w, https:\/\/blog.attendancebot.com\/wp-content\/uploads\/2025\/07\/ChatGPT-Image-Jul-16-2025-07_14_43-PM-min-800x1200.jpg 800w, https:\/\/blog.attendancebot.com\/wp-content\/uploads\/2025\/07\/ChatGPT-Image-Jul-16-2025-07_14_43-PM-min.jpg 1024w\" sizes=\"auto, (max-width: 300px) 100vw, 300px\" \/><\/p>\n<h2><b>When You Should Delay the Sprint vs. Adjust the Plan<\/b><\/h2>\n<p><span style=\"font-weight: 400;\">Not every sprint is worth salvaging. Sometimes, the smarter move isn\u2019t to squeeze work into a half-staffed sprint &#8211; it\u2019s to pause, shift, or reframe the sprint altogether. But how do you know when to adjust the scope versus when to delay?<\/span><\/p>\n<p><span style=\"font-weight: 400;\">Here\u2019s a simple decision-making framework to help Agile Delivery Managers navigate high-impact PTO scenarios with clarity.<\/span><\/p>\n<h3><b>\u2705 Adjust the Plan When:<\/b><\/h3>\n<ul>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><b>Only one or two team members are out<\/b><span style=\"font-weight: 400;\">, and their tasks can be redistributed or postponed without blocking key deliverables.<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><b>The team still has 70\u201380% of its usual capacity<\/b><span style=\"font-weight: 400;\">, and there\u2019s flexibility in what gets committed.<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><b>The work is modular<\/b><span style=\"font-weight: 400;\"> &#8211; meaning stories can be re-ordered or broken into smaller chunks without causing dependency issues.<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><b>Stakeholders are aligned<\/b><span style=\"font-weight: 400;\"> and open to a reduced scope as long as communication is timely.<\/span><\/li>\n<\/ul>\n<p><span style=\"font-weight: 400;\">\u2705 <\/span><i><span style=\"font-weight: 400;\">Example<\/span><\/i><span style=\"font-weight: 400;\">: Your QA lead is on vacation, but your developers can still complete feature tickets and leave testing until the next sprint. You flag the delay early and commit to a narrower slice of the feature set.<\/span><\/p>\n<h3><b>\ud83d\uded1 Delay or Reframe the Sprint When:<\/b><\/h3>\n<ul>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><b>Multiple people are out<\/b><span style=\"font-weight: 400;\">, especially across roles (e.g., design + dev + QA), making cross-functional work impossible.<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><b>Key contributors are unavailable<\/b><span style=\"font-weight: 400;\"> for critical, high-priority tasks that no one else can take on.<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><b>Your sprint velocity drops below 50%<\/b><span style=\"font-weight: 400;\">, making meaningful progress unrealistic.<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><b>There\u2019s a risk of burnout or rushed handovers<\/b><span style=\"font-weight: 400;\"> by asking the remaining team to overextend.<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><b>There\u2019s nothing of value to ship<\/b><span style=\"font-weight: 400;\">, and maintaining the sprint cadence would hurt more than help.<\/span><\/li>\n<\/ul>\n<p><span style=\"font-weight: 400;\">\ud83d\uded1 <\/span><i><span style=\"font-weight: 400;\">Example<\/span><\/i><span style=\"font-weight: 400;\">: Your frontend team is down to one developer, and a major UI overhaul is on the backlog. Instead of pushing ahead with workarounds, you turn the sprint into a &#8220;tech debt and documentation&#8221; sprint, or delay by a few days to restore capacity.<\/span><\/p>\n<h3><b>\ud83c\udfaf Strategic Alternatives to Consider<\/b><\/h3>\n<p><span style=\"font-weight: 400;\">If delaying the sprint feels risky or politically sensitive, consider creative middle paths:<\/span><\/p>\n<ul>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><b>Shorten the sprint<\/b><span style=\"font-weight: 400;\"> to align with the team\u2019s available days (e.g., a 5-day sprint instead of 10)<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><b>Run a \u201cmaintenance sprint\u201d<\/b><span style=\"font-weight: 400;\"> focused on code cleanup, automation, bug fixes, or backlog grooming<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><b>Use the time for discovery or internal learning<\/b><span style=\"font-weight: 400;\">, especially if PTO lines up with quieter periods in your product roadmap<\/span><\/li>\n<\/ul>\n<p><span style=\"font-weight: 400;\">The goal is to maintain the rhythm of Agile without treating the sprint timeline as sacred. Flexibility leads to resilience.<\/span><\/p>\n<h2><b>Wrapping Up<\/b><\/h2>\n<p><span style=\"font-weight: 400;\">PTO doesn\u2019t have to derail your sprint &#8211; it just needs to be part of the plan. When Agile teams treat time off as a normal constraint, not a surprise, they set themselves up for more predictable delivery, less stress, and stronger stakeholder trust. The key is visibility, honest capacity planning, and a willingness to flex when needed.<\/span><\/p>\n","protected":false},"excerpt":{"rendered":"<p>Discover how to manage PTO in sprint planning with the right tools, smart tips, and team strategies to keep workflows on track.<\/p>\n","protected":false},"author":13,"featured_media":200211,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[6],"tags":[],"class_list":["post-200210","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-hr-best-practices"],"yoast_head":"<!-- This site is optimized with the Yoast SEO Premium plugin v24.8 (Yoast SEO v26.8) - https:\/\/yoast.com\/product\/yoast-seo-premium-wordpress\/ -->\n<title>PTO in Sprint Planning: Tools, Tips, and Team Tactics | AttendanceBot<\/title>\n<meta name=\"description\" content=\"Discover how to manage PTO in sprint planning with the right tools, smart tips, and team strategies to keep workflows on track.\" \/>\n<meta name=\"robots\" content=\"index, follow, max-snippet:-1, max-image-preview:large, max-video-preview:-1\" \/>\n<link rel=\"canonical\" href=\"https:\/\/www.attendancebot.com\/blog\/pto-in-sprint-planning-tools-tips-tactics\/\" \/>\n<meta property=\"og:locale\" content=\"en_US\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"PTO in Sprint Planning: Tools, Tips, and Team Tactics\" \/>\n<meta property=\"og:description\" content=\"Discover how to manage PTO in sprint planning with the right tools, smart tips, and team strategies to keep workflows on track.\" \/>\n<meta property=\"og:url\" content=\"https:\/\/www.attendancebot.com\/blog\/pto-in-sprint-planning-tools-tips-tactics\/\" \/>\n<meta property=\"og:site_name\" content=\"AttendanceBot Blog\" \/>\n<meta property=\"article:publisher\" content=\"https:\/\/www.facebook.com\/Anaekhq\/\" \/>\n<meta property=\"article:published_time\" content=\"2025-07-16T14:24:20+00:00\" \/>\n<meta property=\"article:modified_time\" content=\"2025-07-16T14:30:21+00:00\" \/>\n<meta property=\"og:image\" content=\"https:\/\/blog.attendancebot.com\/wp-content\/uploads\/2025\/07\/ChatGPT-Image-Jul-16-2025-07_09_23-PM-min.jpg\" \/>\n\t<meta property=\"og:image:width\" content=\"1536\" \/>\n\t<meta property=\"og:image:height\" content=\"1024\" \/>\n\t<meta property=\"og:image:type\" content=\"image\/jpeg\" \/>\n<meta name=\"author\" content=\"Ruhma\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:creator\" content=\"@anaekhq\" \/>\n<meta name=\"twitter:site\" content=\"@anaekhq\" \/>\n<meta name=\"twitter:label1\" content=\"Written by\" \/>\n\t<meta name=\"twitter:data1\" content=\"Ruhma\" \/>\n\t<meta name=\"twitter:label2\" content=\"Est. reading time\" \/>\n\t<meta name=\"twitter:data2\" content=\"11 minutes\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\/\/schema.org\",\"@graph\":[{\"@type\":\"Article\",\"@id\":\"https:\/\/www.attendancebot.com\/blog\/pto-in-sprint-planning-tools-tips-tactics\/#article\",\"isPartOf\":{\"@id\":\"https:\/\/www.attendancebot.com\/blog\/pto-in-sprint-planning-tools-tips-tactics\/\"},\"author\":{\"name\":\"Ruhma\",\"@id\":\"https:\/\/www.attendancebot.com\/blog\/#\/schema\/person\/76f798b139e1efec6a0b2c90b1ef44c2\"},\"headline\":\"PTO in Sprint Planning: Tools, Tips, and Team Tactics\",\"datePublished\":\"2025-07-16T14:24:20+00:00\",\"dateModified\":\"2025-07-16T14:30:21+00:00\",\"mainEntityOfPage\":{\"@id\":\"https:\/\/www.attendancebot.com\/blog\/pto-in-sprint-planning-tools-tips-tactics\/\"},\"wordCount\":2217,\"image\":{\"@id\":\"https:\/\/www.attendancebot.com\/blog\/pto-in-sprint-planning-tools-tips-tactics\/#primaryimage\"},\"thumbnailUrl\":\"https:\/\/blog.attendancebot.com\/wp-content\/uploads\/2025\/07\/ChatGPT-Image-Jul-16-2025-07_09_23-PM-min.jpg\",\"articleSection\":[\"HR Best Practices\"],\"inLanguage\":\"en-US\"},{\"@type\":\"WebPage\",\"@id\":\"https:\/\/www.attendancebot.com\/blog\/pto-in-sprint-planning-tools-tips-tactics\/\",\"url\":\"https:\/\/www.attendancebot.com\/blog\/pto-in-sprint-planning-tools-tips-tactics\/\",\"name\":\"PTO in Sprint Planning: Tools, Tips, and Team Tactics | AttendanceBot\",\"isPartOf\":{\"@id\":\"https:\/\/www.attendancebot.com\/blog\/#website\"},\"primaryImageOfPage\":{\"@id\":\"https:\/\/www.attendancebot.com\/blog\/pto-in-sprint-planning-tools-tips-tactics\/#primaryimage\"},\"image\":{\"@id\":\"https:\/\/www.attendancebot.com\/blog\/pto-in-sprint-planning-tools-tips-tactics\/#primaryimage\"},\"thumbnailUrl\":\"https:\/\/blog.attendancebot.com\/wp-content\/uploads\/2025\/07\/ChatGPT-Image-Jul-16-2025-07_09_23-PM-min.jpg\",\"datePublished\":\"2025-07-16T14:24:20+00:00\",\"dateModified\":\"2025-07-16T14:30:21+00:00\",\"author\":{\"@id\":\"https:\/\/www.attendancebot.com\/blog\/#\/schema\/person\/76f798b139e1efec6a0b2c90b1ef44c2\"},\"description\":\"Discover how to manage PTO in sprint planning with the right tools, smart tips, and team strategies to keep workflows on track.\",\"breadcrumb\":{\"@id\":\"https:\/\/www.attendancebot.com\/blog\/pto-in-sprint-planning-tools-tips-tactics\/#breadcrumb\"},\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\/\/www.attendancebot.com\/blog\/pto-in-sprint-planning-tools-tips-tactics\/\"]}]},{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\/\/www.attendancebot.com\/blog\/pto-in-sprint-planning-tools-tips-tactics\/#primaryimage\",\"url\":\"https:\/\/blog.attendancebot.com\/wp-content\/uploads\/2025\/07\/ChatGPT-Image-Jul-16-2025-07_09_23-PM-min.jpg\",\"contentUrl\":\"https:\/\/blog.attendancebot.com\/wp-content\/uploads\/2025\/07\/ChatGPT-Image-Jul-16-2025-07_09_23-PM-min.jpg\",\"width\":1536,\"height\":1024,\"caption\":\"PTO in Sprint Planning: Tools, Tips, and Team Tactics\"},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\/\/www.attendancebot.com\/blog\/pto-in-sprint-planning-tools-tips-tactics\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Home\",\"item\":\"https:\/\/www.attendancebot.com\/blog\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"PTO in Sprint Planning: Tools, Tips, and Team Tactics\"}]},{\"@type\":\"WebSite\",\"@id\":\"https:\/\/www.attendancebot.com\/blog\/#website\",\"url\":\"https:\/\/www.attendancebot.com\/blog\/\",\"name\":\"AttendanceBot Blog\",\"description\":\"Musings on Work\",\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":{\"@type\":\"EntryPoint\",\"urlTemplate\":\"https:\/\/www.attendancebot.com\/blog\/?s={search_term_string}\"},\"query-input\":{\"@type\":\"PropertyValueSpecification\",\"valueRequired\":true,\"valueName\":\"search_term_string\"}}],\"inLanguage\":\"en-US\"},{\"@type\":\"Person\",\"@id\":\"https:\/\/www.attendancebot.com\/blog\/#\/schema\/person\/76f798b139e1efec6a0b2c90b1ef44c2\",\"name\":\"Ruhma\",\"image\":{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\/\/www.attendancebot.com\/blog\/#\/schema\/person\/image\/\",\"url\":\"https:\/\/secure.gravatar.com\/avatar\/30629d3573de7b14d0803d4defa1e1dd?s=96&d=mm&r=g\",\"contentUrl\":\"https:\/\/secure.gravatar.com\/avatar\/30629d3573de7b14d0803d4defa1e1dd?s=96&d=mm&r=g\",\"caption\":\"Ruhma\"},\"url\":\"https:\/\/www.attendancebot.com\/blog\/author\/ruhma\/\"}]}<\/script>\n<!-- \/ Yoast SEO Premium plugin. -->","yoast_head_json":{"title":"PTO in Sprint Planning: Tools, Tips, and Team Tactics | AttendanceBot","description":"Discover how to manage PTO in sprint planning with the right tools, smart tips, and team strategies to keep workflows on track.","robots":{"index":"index","follow":"follow","max-snippet":"max-snippet:-1","max-image-preview":"max-image-preview:large","max-video-preview":"max-video-preview:-1"},"canonical":"https:\/\/www.attendancebot.com\/blog\/pto-in-sprint-planning-tools-tips-tactics\/","og_locale":"en_US","og_type":"article","og_title":"PTO in Sprint Planning: Tools, Tips, and Team Tactics","og_description":"Discover how to manage PTO in sprint planning with the right tools, smart tips, and team strategies to keep workflows on track.","og_url":"https:\/\/www.attendancebot.com\/blog\/pto-in-sprint-planning-tools-tips-tactics\/","og_site_name":"AttendanceBot Blog","article_publisher":"https:\/\/www.facebook.com\/Anaekhq\/","article_published_time":"2025-07-16T14:24:20+00:00","article_modified_time":"2025-07-16T14:30:21+00:00","og_image":[{"width":1536,"height":1024,"url":"https:\/\/blog.attendancebot.com\/wp-content\/uploads\/2025\/07\/ChatGPT-Image-Jul-16-2025-07_09_23-PM-min.jpg","type":"image\/jpeg"}],"author":"Ruhma","twitter_card":"summary_large_image","twitter_creator":"@anaekhq","twitter_site":"@anaekhq","twitter_misc":{"Written by":"Ruhma","Est. reading time":"11 minutes"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"Article","@id":"https:\/\/www.attendancebot.com\/blog\/pto-in-sprint-planning-tools-tips-tactics\/#article","isPartOf":{"@id":"https:\/\/www.attendancebot.com\/blog\/pto-in-sprint-planning-tools-tips-tactics\/"},"author":{"name":"Ruhma","@id":"https:\/\/www.attendancebot.com\/blog\/#\/schema\/person\/76f798b139e1efec6a0b2c90b1ef44c2"},"headline":"PTO in Sprint Planning: Tools, Tips, and Team Tactics","datePublished":"2025-07-16T14:24:20+00:00","dateModified":"2025-07-16T14:30:21+00:00","mainEntityOfPage":{"@id":"https:\/\/www.attendancebot.com\/blog\/pto-in-sprint-planning-tools-tips-tactics\/"},"wordCount":2217,"image":{"@id":"https:\/\/www.attendancebot.com\/blog\/pto-in-sprint-planning-tools-tips-tactics\/#primaryimage"},"thumbnailUrl":"https:\/\/blog.attendancebot.com\/wp-content\/uploads\/2025\/07\/ChatGPT-Image-Jul-16-2025-07_09_23-PM-min.jpg","articleSection":["HR Best Practices"],"inLanguage":"en-US"},{"@type":"WebPage","@id":"https:\/\/www.attendancebot.com\/blog\/pto-in-sprint-planning-tools-tips-tactics\/","url":"https:\/\/www.attendancebot.com\/blog\/pto-in-sprint-planning-tools-tips-tactics\/","name":"PTO in Sprint Planning: Tools, Tips, and Team Tactics | AttendanceBot","isPartOf":{"@id":"https:\/\/www.attendancebot.com\/blog\/#website"},"primaryImageOfPage":{"@id":"https:\/\/www.attendancebot.com\/blog\/pto-in-sprint-planning-tools-tips-tactics\/#primaryimage"},"image":{"@id":"https:\/\/www.attendancebot.com\/blog\/pto-in-sprint-planning-tools-tips-tactics\/#primaryimage"},"thumbnailUrl":"https:\/\/blog.attendancebot.com\/wp-content\/uploads\/2025\/07\/ChatGPT-Image-Jul-16-2025-07_09_23-PM-min.jpg","datePublished":"2025-07-16T14:24:20+00:00","dateModified":"2025-07-16T14:30:21+00:00","author":{"@id":"https:\/\/www.attendancebot.com\/blog\/#\/schema\/person\/76f798b139e1efec6a0b2c90b1ef44c2"},"description":"Discover how to manage PTO in sprint planning with the right tools, smart tips, and team strategies to keep workflows on track.","breadcrumb":{"@id":"https:\/\/www.attendancebot.com\/blog\/pto-in-sprint-planning-tools-tips-tactics\/#breadcrumb"},"inLanguage":"en-US","potentialAction":[{"@type":"ReadAction","target":["https:\/\/www.attendancebot.com\/blog\/pto-in-sprint-planning-tools-tips-tactics\/"]}]},{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/www.attendancebot.com\/blog\/pto-in-sprint-planning-tools-tips-tactics\/#primaryimage","url":"https:\/\/blog.attendancebot.com\/wp-content\/uploads\/2025\/07\/ChatGPT-Image-Jul-16-2025-07_09_23-PM-min.jpg","contentUrl":"https:\/\/blog.attendancebot.com\/wp-content\/uploads\/2025\/07\/ChatGPT-Image-Jul-16-2025-07_09_23-PM-min.jpg","width":1536,"height":1024,"caption":"PTO in Sprint Planning: Tools, Tips, and Team Tactics"},{"@type":"BreadcrumbList","@id":"https:\/\/www.attendancebot.com\/blog\/pto-in-sprint-planning-tools-tips-tactics\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https:\/\/www.attendancebot.com\/blog\/"},{"@type":"ListItem","position":2,"name":"PTO in Sprint Planning: Tools, Tips, and Team Tactics"}]},{"@type":"WebSite","@id":"https:\/\/www.attendancebot.com\/blog\/#website","url":"https:\/\/www.attendancebot.com\/blog\/","name":"AttendanceBot Blog","description":"Musings on Work","potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/www.attendancebot.com\/blog\/?s={search_term_string}"},"query-input":{"@type":"PropertyValueSpecification","valueRequired":true,"valueName":"search_term_string"}}],"inLanguage":"en-US"},{"@type":"Person","@id":"https:\/\/www.attendancebot.com\/blog\/#\/schema\/person\/76f798b139e1efec6a0b2c90b1ef44c2","name":"Ruhma","image":{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/www.attendancebot.com\/blog\/#\/schema\/person\/image\/","url":"https:\/\/secure.gravatar.com\/avatar\/30629d3573de7b14d0803d4defa1e1dd?s=96&d=mm&r=g","contentUrl":"https:\/\/secure.gravatar.com\/avatar\/30629d3573de7b14d0803d4defa1e1dd?s=96&d=mm&r=g","caption":"Ruhma"},"url":"https:\/\/www.attendancebot.com\/blog\/author\/ruhma\/"}]}},"amp_enabled":true,"_links":{"self":[{"href":"https:\/\/www.attendancebot.com\/blog\/wp-json\/wp\/v2\/posts\/200210","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.attendancebot.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.attendancebot.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.attendancebot.com\/blog\/wp-json\/wp\/v2\/users\/13"}],"replies":[{"embeddable":true,"href":"https:\/\/www.attendancebot.com\/blog\/wp-json\/wp\/v2\/comments?post=200210"}],"version-history":[{"count":3,"href":"https:\/\/www.attendancebot.com\/blog\/wp-json\/wp\/v2\/posts\/200210\/revisions"}],"predecessor-version":[{"id":200217,"href":"https:\/\/www.attendancebot.com\/blog\/wp-json\/wp\/v2\/posts\/200210\/revisions\/200217"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.attendancebot.com\/blog\/wp-json\/wp\/v2\/media\/200211"}],"wp:attachment":[{"href":"https:\/\/www.attendancebot.com\/blog\/wp-json\/wp\/v2\/media?parent=200210"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.attendancebot.com\/blog\/wp-json\/wp\/v2\/categories?post=200210"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.attendancebot.com\/blog\/wp-json\/wp\/v2\/tags?post=200210"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}