{"id":192,"date":"2026-11-17T06:34:50","date_gmt":"2026-11-17T06:34:50","guid":{"rendered":"https:\/\/wisegrid.co\/blog\/?p=192"},"modified":"2026-11-03T06:35:58","modified_gmt":"2026-11-03T06:35:58","slug":"staffing-plan-engineering-firms","status":"publish","type":"post","link":"https:\/\/wisegrid.co\/blog\/staffing-plan-engineering-firms\/","title":{"rendered":"Staffing Plan for Engineering Firms: Template, Example and Steps (2026)"},"content":{"rendered":"<p><em>By <a href=\"\/blog\/author\/ryan-kramer\/\">Ryan Kramer<\/a>, founder of Wisegrid. Last updated November 2026.<\/em><\/p>\n<p>A <strong>staffing plan<\/strong> compares the work a firm expects over the next few months with the hours its people can deliver, role by role, and decides how to close any gap. For engineering and architecture firms, it answers one question early: do we have enough of the right people for the work we have signed and expect to win?<\/p>\n<p>Most small firms staff by instinct. A principal knows who is busy, a project manager asks for help when a deadline slips, and a new hire is approved after the team has been overloaded for months. A simple staffing plan replaces that with numbers you can check every month. This guide covers what goes in one, a worked example with a three-month gap, the steps to build it, and the options for closing a shortfall without hiring too early.<\/p>\n<blockquote>\n<p style=\"margin:0\"><strong>Key takeaways<\/strong><\/p>\n<p style=\"margin:0.55em 0 0\">\u2013 <strong>A staffing plan is demand minus capacity, by role.<\/strong> The firm-wide total hides the role that is actually short.<\/p>\n<p style=\"margin:0.55em 0 0\">\u2013 <strong>Plan capacity at target utilization, not 100%.<\/strong> People also need time for proposals, training and admin.<\/p>\n<p style=\"margin:0.55em 0 0\">\u2013 <strong>Count likely wins, weighted by your chance of winning.<\/strong> Signed work alone makes every future month look empty.<\/p>\n<p style=\"margin:0.55em 0 0\">\u2013 <strong>Size the gap in hours before you decide to hire.<\/strong> A shortfall of half a person is a contractor, not a new job.<\/p>\n<p style=\"margin:0.55em 0 0\">\u2013 <strong>Update it monthly<\/strong>, when timesheets and the proposal pipeline are fresh.<\/p>\n<\/blockquote>\n<nav class=\"wg-toc\" aria-label=\"Table of contents\">\n<div class=\"wg-toc-eyebrow\"><span class=\"lp-dot\" aria-hidden=\"true\"><\/span> On this page<\/div>\n<ul>\n<li><a href=\"#what-is-a-staffing-plan\">What is a staffing plan?<\/a><\/li>\n<li><a href=\"#what-goes-in\">What goes in a staffing plan for an engineering firm?<\/a><\/li>\n<li><a href=\"#staffing-plan-example\">Staffing plan example: a seven-person team<\/a><\/li>\n<li><a href=\"#how-to-build\">How to build a staffing plan, step by step<\/a><\/li>\n<li><a href=\"#closing-gaps\">How do you close a staffing gap?<\/a><\/li>\n<li><a href=\"#common-mistakes\">Common staffing plan mistakes<\/a><\/li>\n<li><a href=\"#from-spreadsheet-to-shared-sheet\">From spreadsheet to a shared staffing plan<\/a><\/li>\n<li><a href=\"#faq\">FAQ<\/a><\/li>\n<\/ul>\n<\/nav>\n<h2 id=\"what-is-a-staffing-plan\">What is a staffing plan?<\/h2>\n<p>A staffing plan is a forward look at people and work. It lists the roles in your firm, how many hours each role can deliver, how many hours your projects will need from each role, and what you will do about the difference. Good plans look three to six months ahead, which is long enough to hire or bring in help and short enough to be reasonably accurate.<\/p>\n<p>It sits between two other tools. <a href=\"\/blog\/utilization-rate-engineering-firms\/\">Utilization rate<\/a> tells you how busy people were last month. <a href=\"\/blog\/capacity-planning-template\/\">Capacity planning<\/a> books named people onto projects week by week. The staffing plan is the bigger picture that tells you whether the firm has enough of each role in the first place. The U.S. Office of Personnel Management describes workforce planning the same way: analyze the current workforce, find the gaps, then choose strategies to close them.<\/p>\n<h2 id=\"what-goes-in\">What goes in a staffing plan for an engineering firm?<\/h2>\n<p>A staffing plan for a small engineering or architecture firm fits on one sheet. These are the parts, and the question each one answers:<\/p>\n<div class=\"wg-table-wrap\">\n<div class=\"wg-table-wrap\"><table>\n<thead>\n<tr>\n<th style=\"white-space:nowrap\">Part<\/th>\n<th style=\"white-space:nowrap\">What\u00a0it\u00a0answers<\/th>\n<\/tr>\n<\/thead>\n<tbody>\n<tr>\n<td style=\"white-space:nowrap\"><strong>Roles<\/strong><\/td>\n<td>Which kinds of people do we need?<\/td>\n<\/tr>\n<tr>\n<td style=\"white-space:nowrap\"><strong>Headcount\u00a0by\u00a0role<\/strong><\/td>\n<td>How many do we have today?<\/td>\n<\/tr>\n<tr>\n<td style=\"white-space:nowrap\"><strong>Capacity<\/strong><\/td>\n<td>How many project hours can they give?<\/td>\n<\/tr>\n<tr>\n<td style=\"white-space:nowrap\"><strong>Signed\u00a0demand<\/strong><\/td>\n<td>How many hours does signed work need?<\/td>\n<\/tr>\n<tr>\n<td style=\"white-space:nowrap\"><strong>Weighted\u00a0wins<\/strong><\/td>\n<td>How many hours might new work need?<\/td>\n<\/tr>\n<tr>\n<td style=\"white-space:nowrap\"><strong>Gap<\/strong><\/td>\n<td>Where are we short or spare?<\/td>\n<\/tr>\n<tr>\n<td style=\"white-space:nowrap\"><strong>Actions<\/strong><\/td>\n<td>What will we do, by when, and who owns it?<\/td>\n<\/tr>\n<\/tbody>\n<\/table><\/div>\n<\/div>\n<p><strong>Capacity<\/strong> is people \u00d7 available hours \u00d7 target utilization. If you track staff as full-time equivalents, our guide to <a href=\"\/blog\/what-is-fte\/\">what a full-time equivalent (FTE) is<\/a> shows how to count part-time people. <strong>Weighted wins<\/strong> are the hours each open proposal would need, multiplied by your honest chance of winning it.<\/p>\n<h2 id=\"staffing-plan-example\">Staffing plan example: a seven-person team<\/h2>\n<p>A seven-person civil engineering team plans January. Each person has about 160 available hours a month. Capacity uses the billable targets from our <a href=\"\/blog\/utilization-rate-engineering-firms\/\">utilization example<\/a>: 75% for senior engineers and 85% for project engineers and drafters. Demand is signed work plus weighted wins. A negative gap means the role is short; <strong>bold<\/strong> rows are short.<\/p>\n<div class=\"wg-table-wrap\">\n<div class=\"wg-table-wrap\"><table>\n<thead>\n<tr>\n<th style=\"white-space:nowrap;padding:11px 14px;font-size:14px\">Role<\/th>\n<th style=\"text-align:right;white-space:nowrap;padding:11px 14px;font-size:14px\">People<\/th>\n<th style=\"text-align:right;white-space:nowrap;padding:11px 14px;font-size:14px\">Capacity<\/th>\n<th style=\"text-align:right;white-space:nowrap;padding:11px 14px;font-size:14px\">Demand<\/th>\n<th style=\"text-align:right;white-space:nowrap;padding:11px 14px;font-size:14px\">Gap<\/th>\n<\/tr>\n<\/thead>\n<tbody>\n<tr>\n<td style=\"white-space:nowrap;padding:11px 14px;font-size:14px\"><strong>Senior\u00a0engineer<\/strong><\/td>\n<td style=\"text-align:right;white-space:nowrap;padding:11px 14px;font-size:14px\">2<\/td>\n<td style=\"text-align:right;white-space:nowrap;padding:11px 14px;font-size:14px\">240<\/td>\n<td style=\"text-align:right;white-space:nowrap;padding:11px 14px;font-size:14px\">210<\/td>\n<td style=\"text-align:right;white-space:nowrap;padding:11px 14px;font-size:14px\">+30<\/td>\n<\/tr>\n<tr>\n<td style=\"white-space:nowrap;padding:11px 14px;font-size:14px\"><strong>Project\u00a0engineer<\/strong><\/td>\n<td style=\"text-align:right;white-space:nowrap;padding:11px 14px;font-size:14px\">3<\/td>\n<td style=\"text-align:right;white-space:nowrap;padding:11px 14px;font-size:14px\">408<\/td>\n<td style=\"text-align:right;white-space:nowrap;padding:11px 14px;font-size:14px\">470<\/td>\n<td style=\"text-align:right;white-space:nowrap;padding:11px 14px;font-size:14px\"><strong>\u221262<\/strong><\/td>\n<\/tr>\n<tr>\n<td style=\"white-space:nowrap;padding:11px 14px;font-size:14px\"><strong>Drafter<\/strong><\/td>\n<td style=\"text-align:right;white-space:nowrap;padding:11px 14px;font-size:14px\">2<\/td>\n<td style=\"text-align:right;white-space:nowrap;padding:11px 14px;font-size:14px\">272<\/td>\n<td style=\"text-align:right;white-space:nowrap;padding:11px 14px;font-size:14px\">300<\/td>\n<td style=\"text-align:right;white-space:nowrap;padding:11px 14px;font-size:14px\"><strong>\u221228<\/strong><\/td>\n<\/tr>\n<tr>\n<td style=\"white-space:nowrap;padding:11px 14px;font-size:14px\"><strong>Total<\/strong><\/td>\n<td style=\"text-align:right;white-space:nowrap;padding:11px 14px;font-size:14px\"><strong>7<\/strong><\/td>\n<td style=\"text-align:right;white-space:nowrap;padding:11px 14px;font-size:14px\"><strong>920<\/strong><\/td>\n<td style=\"text-align:right;white-space:nowrap;padding:11px 14px;font-size:14px\"><strong>980<\/strong><\/td>\n<td style=\"text-align:right;white-space:nowrap;padding:11px 14px;font-size:14px\"><strong>\u221260<\/strong><\/td>\n<\/tr>\n<\/tbody>\n<\/table><\/div>\n<\/div>\n<p>The firm-wide gap is only 60 hours, about 7% of capacity, which looks manageable. The role view shows the real problem: project engineers are 62 hours short while senior engineers have 30 hours to spare. One month is not enough to decide, so the plan looks three months ahead for the role that is short:<\/p>\n<div class=\"wg-table-wrap\">\n<div class=\"wg-table-wrap\"><table>\n<thead>\n<tr>\n<th style=\"white-space:nowrap;padding:11px 14px;font-size:14px\">Month<\/th>\n<th style=\"text-align:right;white-space:nowrap;padding:11px 14px;font-size:14px\">Signed<\/th>\n<th style=\"text-align:right;white-space:nowrap;padding:11px 14px;font-size:14px\">Weighted\u00a0wins<\/th>\n<th style=\"text-align:right;white-space:nowrap;padding:11px 14px;font-size:14px\">Capacity<\/th>\n<th style=\"text-align:right;white-space:nowrap;padding:11px 14px;font-size:14px\">Gap<\/th>\n<\/tr>\n<\/thead>\n<tbody>\n<tr>\n<td style=\"white-space:nowrap;padding:11px 14px;font-size:14px\"><strong>January<\/strong><\/td>\n<td style=\"text-align:right;white-space:nowrap;padding:11px 14px;font-size:14px\">400<\/td>\n<td style=\"text-align:right;white-space:nowrap;padding:11px 14px;font-size:14px\">70<\/td>\n<td style=\"text-align:right;white-space:nowrap;padding:11px 14px;font-size:14px\">408<\/td>\n<td style=\"text-align:right;white-space:nowrap;padding:11px 14px;font-size:14px\">\u221262<\/td>\n<\/tr>\n<tr>\n<td style=\"white-space:nowrap;padding:11px 14px;font-size:14px\"><strong>February<\/strong><\/td>\n<td style=\"text-align:right;white-space:nowrap;padding:11px 14px;font-size:14px\">360<\/td>\n<td style=\"text-align:right;white-space:nowrap;padding:11px 14px;font-size:14px\">120<\/td>\n<td style=\"text-align:right;white-space:nowrap;padding:11px 14px;font-size:14px\">408<\/td>\n<td style=\"text-align:right;white-space:nowrap;padding:11px 14px;font-size:14px\">\u221272<\/td>\n<\/tr>\n<tr>\n<td style=\"white-space:nowrap;padding:11px 14px;font-size:14px\"><strong>March<\/strong><\/td>\n<td style=\"text-align:right;white-space:nowrap;padding:11px 14px;font-size:14px\">300<\/td>\n<td style=\"text-align:right;white-space:nowrap;padding:11px 14px;font-size:14px\">160<\/td>\n<td style=\"text-align:right;white-space:nowrap;padding:11px 14px;font-size:14px\">408<\/td>\n<td style=\"text-align:right;white-space:nowrap;padding:11px 14px;font-size:14px\">\u221252<\/td>\n<\/tr>\n<tr>\n<td style=\"white-space:nowrap;padding:11px 14px;font-size:14px\"><strong>Total<\/strong><\/td>\n<td style=\"text-align:right;white-space:nowrap;padding:11px 14px;font-size:14px\">1,060<\/td>\n<td style=\"text-align:right;white-space:nowrap;padding:11px 14px;font-size:14px\">350<\/td>\n<td style=\"text-align:right;white-space:nowrap;padding:11px 14px;font-size:14px\">1,224<\/td>\n<td style=\"text-align:right;white-space:nowrap;padding:11px 14px;font-size:14px\"><strong>\u2212186<\/strong><\/td>\n<\/tr>\n<\/tbody>\n<\/table><\/div>\n<\/div>\n<p><strong>What this tells you:<\/strong> project engineers are short <strong>186 hours over the quarter<\/strong>, about 14 hours a week. One new project engineer at 85% would add 408 hours, more than twice the gap, and would be underused unless more proposals are won. A better first move is to give some of the work to senior engineers, who have spare time in January, and bring in a contract engineer for about 14 hours a week. Revisit in February: if the weighted wins turn into signed work, the hiring case becomes clear.<\/p>\n<h2 id=\"how-to-build\">How to build a staffing plan, step by step<\/h2>\n<ol>\n<li><strong>List roles, not names.<\/strong> Group people by what they can do: principal, senior engineer, project engineer, drafter, coordinator. Someone who covers two roles can be split between them.<\/li>\n<li><strong>Set available hours.<\/strong> Use the same definition every month, for example 40 hours a week minus holidays and booked vacation.<\/li>\n<li><strong>Set target utilization by role.<\/strong> Principals spend more time on sales and management, so their target is lower. Our <a href=\"\/free-tools\/utilization-rate-calculator\/\">utilization rate calculator<\/a> helps you check what is realistic.<\/li>\n<li><strong>Add signed demand.<\/strong> For each active project, take the remaining hours by role from the fee budget. Our guide to <a href=\"\/blog\/budget-vs-actual-engineering-architecture\/\">budget vs actual for engineering firms<\/a> shows how to get remaining hours you can trust.<\/li>\n<li><strong>Add weighted wins.<\/strong> For each open proposal, estimate hours by role and multiply by your chance of winning. Be honest: 30% means 30%.<\/li>\n<li><strong>Calculate the gap by role and month<\/strong>, and highlight anything short for two months or more.<\/li>\n<li><strong>Choose an action for each gap<\/strong>, with an owner and a date, and review the plan at the same meeting every month.<\/li>\n<\/ol>\n<h2 id=\"closing-gaps\">How do you close a staffing gap?<\/h2>\n<p>You close a staffing gap by moving work, adding hours or adding people, in roughly that order of cost and risk. The table compares the usual options:<\/p>\n<div class=\"wg-table-wrap\">\n<div class=\"wg-table-wrap\"><table>\n<thead>\n<tr>\n<th style=\"white-space:nowrap\">Option<\/th>\n<th style=\"white-space:nowrap\">Best\u00a0when<\/th>\n<th style=\"white-space:nowrap\">Watch\u00a0out\u00a0for<\/th>\n<\/tr>\n<\/thead>\n<tbody>\n<tr>\n<td><strong>Move work between roles<\/strong><\/td>\n<td>Another role has spare hours<\/td>\n<td>Seniors doing junior work cost more<\/td>\n<\/tr>\n<tr>\n<td style=\"white-space:nowrap\"><strong>Shift\u00a0project\u00a0dates<\/strong><\/td>\n<td>The client has flexibility<\/td>\n<td>Knock-on effects on other projects<\/td>\n<\/tr>\n<tr>\n<td style=\"white-space:nowrap\"><strong>Short-term\u00a0overtime<\/strong><\/td>\n<td>The gap is a few weeks<\/td>\n<td>Fatigue and mistakes if it lasts<\/td>\n<\/tr>\n<tr>\n<td><strong>Contract or freelance help<\/strong><\/td>\n<td>Gap is under one person<\/td>\n<td>Onboarding time and quality checks<\/td>\n<\/tr>\n<tr>\n<td style=\"white-space:nowrap\"><strong>Hire<\/strong><\/td>\n<td>Gap lasts and pipeline is strong<\/td>\n<td>Months before a hire is fully useful<\/td>\n<\/tr>\n<\/tbody>\n<\/table><\/div>\n<\/div>\n<p>Spare capacity is a gap too. If a role has spare hours for several months, that is a signal to push proposals, move people into another role, or pause a planned hire. The <a href=\"\/free-tools\/labor-cost-calculator\/\">labor cost calculator<\/a> helps you compare the cost of overtime, contractors and a new hire.<\/p>\n<h2 id=\"common-mistakes\">Common staffing plan mistakes<\/h2>\n<ul>\n<li><strong>Planning at 100% utilization.<\/strong> Nobody bills every available hour, so the plan always looks better than reality.<\/li>\n<li><strong>Only counting signed work.<\/strong> Every month after the next one looks empty, and you hire too late.<\/li>\n<li><strong>Counting every proposal at full value.<\/strong> The opposite problem: you hire for work you never win.<\/li>\n<li><strong>Looking only at the firm total.<\/strong> As the example shows, a small overall gap can hide a large gap in one role.<\/li>\n<li><strong>Remaining hours that ignore budget overruns.<\/strong> If a project is already over budget, its real remaining hours are higher than the fee says.<\/li>\n<li><strong>A plan nobody updates.<\/strong> A staffing plan from last quarter is a guess about the past.<\/li>\n<\/ul>\n<h2 id=\"from-spreadsheet-to-shared-sheet\">From spreadsheet to a shared staffing plan<\/h2>\n<p>A staffing plan usually starts as one spreadsheet kept by a principal or operations lead. It breaks when project managers keep their own versions, remaining hours are typed in by hand each month, and the plan disagrees with the timesheets. By the time it is reconciled, the month has moved on.<\/p>\n<p>In Wisegrid, the staffing plan reads from the same workspace as projects and timesheets. Remaining hours come from each project\u2019s budget sheet, actual hours come from the <a href=\"\/templates\/timesheet-template\/\">timesheet template<\/a>, and a cross-sheet report adds up demand by role and month. Gaps turn amber automatically, and project managers can view the plan for free. Weekly bookings for named people live in the <a href=\"\/templates\/resource-planning-template\/\">resource planning template<\/a> and the <a href=\"\/templates\/capacity-planning-template\/\">capacity planning template<\/a>, and fees in the <a href=\"\/templates\/project-budget-template\/\">project budget template<\/a>. It is still a grid, so the formulas above work as written.<\/p>\n<h2 id=\"faq\">FAQ<\/h2>\n<h3 id=\"what-is-the-difference-between-a-staffing-plan-and-a-resource-plan\">What is the difference between a staffing plan and a resource plan?<\/h3>\n<p>A staffing plan asks whether the firm has enough people in each role over the next few months. A resource plan, or resource allocation plan, assigns named people to specific projects week by week. The staffing plan sets headcount; the resource plan uses the people you have. Most firms need both.<\/p>\n<h3 id=\"how-far-ahead-should-an-engineering-firm-plan-staffing\">How far ahead should an engineering firm plan staffing?<\/h3>\n<p>Three to six months works for most small and mid-size firms. That is roughly how long it takes to find and onboard a new engineer, and far enough ahead to see the proposal pipeline turning into work. Beyond six months, demand estimates are usually too rough to act on, so keep a lighter yearly view for budgeting.<\/p>\n<h3 id=\"what-utilization-should-i-use-for-capacity\">What utilization should I use for capacity?<\/h3>\n<p>Use each role\u2019s target billable utilization, not 100%. Many firms set higher targets for project engineers and drafters and lower ones for principals, who spend more time on sales and management. Our <a href=\"\/blog\/utilization-rate-engineering-firms\/\">utilization rate guide<\/a> shows how to set a target from cost and billing rate.<\/p>\n<h3 id=\"how-do-you-estimate-hours-for-work-you-have-not-won-yet\">How do you estimate hours for work you have not won yet?<\/h3>\n<p>Take the hours by role from the proposal\u2019s fee estimate, then multiply by your chance of winning, based on your history with that client or type of project. A 200-hour proposal with a 40% chance adds 80 weighted hours. Review those chances every month as decisions come in.<\/p>\n<h3 id=\"is-there-a-free-staffing-plan-template\">Is there a free staffing plan template?<\/h3>\n<p>The table in the example above is the template: roles as rows, and people, capacity, demand and gap as columns, with one copy per month. For week-by-week bookings of named people, start from Wisegrid\u2019s free resource planning and capacity planning templates, which use the same roles and hours.<\/p>\n<h2 id=\"sources\">Sources<\/h2>\n<ul>\n<li><a href=\"https:\/\/www.opm.gov\/frequently-asked-questions\/hr-strategy-and-evaluation-services-faq\/workforce-and-succession-planning\/what-are-the-steps-involved-in-a-worforce-and-succession-planning-project\/\" target=\"_blank\" rel=\"noopener\">U.S. Office of Personnel Management: What are the steps involved in a workforce and succession planning project?<\/a><\/li>\n<\/ul>\n<hr>\n<h3 id=\"see-next-quarters-gap-before-it-hits\">See next quarter\u2019s gap before it hits<\/h3>\n<p>Keep projects, timesheets and the staffing plan in one Wisegrid workspace, and share it with project managers for free. Start with the <a href=\"\/templates\/resource-planning-template\/\">resource planning template<\/a>, the <a href=\"\/templates\/capacity-planning-template\/\">capacity planning template<\/a> and the <a href=\"\/templates\/timesheet-template\/\">timesheet template<\/a>.<\/p>\n<p><strong><a href=\"\/signup\/\">Start free \u2192<\/a><\/strong> \u00b7 <a href=\"\/blog\/utilization-rate-engineering-firms\/\">Utilization rate guide \u2192<\/a> \u00b7 <a href=\"\/free-tools\/utilization-rate-calculator\/\">Utilization calculator \u2192<\/a><\/p>\n<hr>\n<blockquote>\n<p><strong>About the author<\/strong> <strong><a href=\"\/blog\/author\/ryan-kramer\/\">Ryan Kramer<\/a><\/strong> is the founder of Wisegrid, a higher-capacity work management grid built around a 1,000,000-cell-per-sheet limit, date-triggered automations with run history, and cross-sheet reporting. He writes about the project management documents teams actually keep updated. <a href=\"\/blog\/author\/ryan-kramer\/\">More from Ryan \u2192<\/a><\/p>\n<\/blockquote>\n","protected":false},"excerpt":{"rendered":"<p>How engineering and architecture firms build a staffing plan: what goes in it, a worked example with a three-month gap, the steps, and ways to close it.<\/p>\n","protected":false},"author":2,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[4],"tags":[15,35],"class_list":["post-192","post","type-post","status-publish","format-standard","hentry","category-engineering-ae","tag-resource-planning","tag-staffing"],"_links":{"self":[{"href":"https:\/\/wisegrid.co\/blog\/wp-json\/wp\/v2\/posts\/192","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/wisegrid.co\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/wisegrid.co\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/wisegrid.co\/blog\/wp-json\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"https:\/\/wisegrid.co\/blog\/wp-json\/wp\/v2\/comments?post=192"}],"version-history":[{"count":1,"href":"https:\/\/wisegrid.co\/blog\/wp-json\/wp\/v2\/posts\/192\/revisions"}],"predecessor-version":[{"id":193,"href":"https:\/\/wisegrid.co\/blog\/wp-json\/wp\/v2\/posts\/192\/revisions\/193"}],"wp:attachment":[{"href":"https:\/\/wisegrid.co\/blog\/wp-json\/wp\/v2\/media?parent=192"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/wisegrid.co\/blog\/wp-json\/wp\/v2\/categories?post=192"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/wisegrid.co\/blog\/wp-json\/wp\/v2\/tags?post=192"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}