{"id":13685,"date":"2026-10-20T00:00:00","date_gmt":"2026-10-20T00:00:00","guid":{"rendered":"https:\/\/formatourinc.com\/en\/identify-processes-to-automate-a-business-guide\/"},"modified":"2026-10-21T02:01:32","modified_gmt":"2026-10-21T02:01:32","slug":"identify-processes-to-automate-a-business-guide","status":"publish","type":"post","link":"https:\/\/formatourinc.com\/en\/identify-processes-to-automate-a-business-guide\/","title":{"rendered":"Identify Processes to Automate: A Business Guide"},"content":{"rendered":"<p>The process consuming the most staff time may be the wrong one to automate first. Knowing how to identify processes to automate starts with evidence: where work stalls, repeats, generates errors, or depends on frequent handoffs. Automating a flawed process can reproduce its problems at scale, so assessing the work is as important as choosing the technology.<\/p>\n<p>Manual work can drain time and attention, but a high workload alone doesn\u2019t prove automation is the right answer. Some processes need simplification or standardization first. Others rely on judgement, contain too many exceptions, or require human oversight because of the consequences of an error. A clear view of performance, data quality, ownership, and business value helps distinguish promising opportunities from costly distractions.<\/p>\n<p>This guide explains how to identify candidate processes using observable operational evidence, assess their readiness and risks, and compare automation with other improvement options. You\u2019ll also learn how to prioritize a practical first opportunity and define measures for evaluating it. Digital diagnostics and process optimization can help turn process discovery into a sound business decision rather than a software-first exercise.<\/p>\n<div class=\"key-takeaways\">\n<h2 id=\"key-takeaways\">Key Takeaways<\/h2>\n<ul>\n<li>Learn how to identify processes to automate by looking for repeatable work with clear outcomes and observable steps.<\/li>\n<li>Assess rules, exceptions, data quality, ownership, and risk separately to understand whether a process is ready.<\/li>\n<li>Compare automation with simplification, standardization, and human-led work before deciding on the best improvement path.<\/li>\n<li>Build a practical shortlist using operational evidence and input from process owners and the people doing the work.<\/li>\n<li>Plan a bounded test with a clear owner, expected outcome, exception handling, and a review approach.<\/li>\n<\/ul>\n<\/div>\n<div class=\"table-of-contents\" role=\"navigation\" aria-label=\"Table of Contents\">\n<h2 id=\"table-of-contents\">Table of Contents<\/h2>\n<ul>\n<li><a href=\"https:\/\/formatourinc.com\/en\/identify-processes-to-automate-a-business-guide#automate-processes-start-with-the-operational-problem\">Automate Processes: Start With the Operational Problem<\/a><\/li>\n<li><a href=\"https:\/\/formatourinc.com\/en\/identify-processes-to-automate-a-business-guide#assess-process-automation-readiness-rules-exceptions-data-and-risk\">Assess Process Automation Readiness: Rules, Exceptions, Data, and Risk<\/a><\/li>\n<li><a href=\"https:\/\/formatourinc.com\/en\/identify-processes-to-automate-a-business-guide#automation-or-another-improvement-compare-the-best-path-for-each-process\">Automation or Another Improvement? Compare the Best Path for Each Process<\/a><\/li>\n<li><a href=\"https:\/\/formatourinc.com\/en\/identify-processes-to-automate-a-business-guide#how-to-prioritize-automation-opportunities-and-build-a-practical-shortlist\">How to Prioritize Automation Opportunities and Build a Practical Shortlist<\/a><\/li>\n<li><a href=\"https:\/\/formatourinc.com\/en\/identify-processes-to-automate-a-business-guide#from-shortlist-to-sustainable-improvement-plan-the-next-step\">From Shortlist to Sustainable Improvement: Plan the Next Step<\/a><\/li>\n<\/ul>\n<\/div>\n<h2 id=\"automate-processes-start-with-the-operational-problem\">Automate Processes: Start With the Operational Problem<\/h2>\n<p>Start with the work, not the software. Before comparing automation technologies, identify the operational problem to solve. Requests may wait between departments, employees may enter the same information into several systems, or recurring corrections may delay a service. These symptoms show where to investigate, but not why the problem occurs. The cause might be unclear approval rules, incomplete information, unnecessary steps, or a gap in ownership.<\/p>\n<p><strong>Process improvement changes or clarifies how work should happen; automation uses technology to perform or support defined steps.<\/strong> That distinction is central to <a href=\"https:\/\/en.wikipedia.org\/wiki\/Business_process_automation\" target=\"_blank\" rel=\"noopener noreferrer nofollow\">Business Process Automation<\/a>: establish the process and intended result first, then determine which steps are suitable for technology.<\/p>\n<h3>What makes a process a credible automation candidate?<\/h3>\n<p>Look for observable evidence rather than relying on general impressions. Useful indicators include repeated handoffs, time spent waiting for approvals, duplicate data entry, recurring corrections, and requests returned because required details are missing. Record where each issue occurs, who is involved, and which outcome it affects. This makes it easier to compare candidates than ranking tasks by volume alone.<\/p>\n<h3>Why should teams examine the current process first?<\/h3>\n<p>Written procedures may not reflect how work happens in practice. Employees may rely on informal workarounds, make decisions based on context, or transfer responsibility in ways a process guide doesn\u2019t show. Speaking with process owners and the people doing the work can reveal these steps, clarify decision points, and establish who is accountable for the result.<\/p>\n<p>Without that investigation, automation may preserve the inefficiencies the organization wants to remove. A digital form won\u2019t fix unclear approval authority, and automatically transferring incomplete records can create more corrections downstream. Map the current flow, including exceptions and informal practices, then distinguish necessary controls from avoidable friction. This operational view also supports a broader <a href=\"https:\/\/formatourinc.com\/en\/\">digital transformation strategy<\/a>, where technology choices follow organizational priorities rather than define them.<\/p>\n<p>Formatour provides digital diagnostics and process automation and optimization to help organizations build an evidence base before selecting an approach. The goal is not to automate every repetitive task. It is to identify where a well-understood change can address a meaningful business problem while preserving appropriate oversight.<\/p>\n<h2 id=\"assess-process-automation-readiness-rules-exceptions-data-and-risk\">Assess Process Automation Readiness: Rules, Exceptions, Data, and Risk<\/h2>\n<p>Once a process has a defined purpose, assess whether its steps can be carried out reliably and governed appropriately. A useful readiness review separates consistency, rule clarity, exception frequency, data quality, ownership, and risk. A strong result in one area doesn\u2019t compensate for unresolved weaknesses in another. For teams evaluating <em>how to identify processes to automate<\/em>, this distinction helps show whether to proceed, clarify the process, or retain human judgement at key points.<\/p>\n<p><strong>Stable work is ready for automation assessment; unclear rules, recurring exceptions, or unreliable data signal a need to clarify or redesign the process first.<\/strong> These issues don\u2019t automatically rule out automation. They show what needs attention before automation can support dependable outcomes.<\/p>\n<h3>How do rules, exceptions, and process stability affect readiness?<\/h3>\n<p>Document the normal path from the first trigger to the intended result. Then record the decision rules at each point, the types of exceptions that occur, and who has authority to resolve them. For example, a routine request may follow a consistent route, while an incomplete submission requires an employee to interpret context or seek missing details. That distinction helps determine where automation can act and where a person should review the work.<\/p>\n<p>Distinguish occasional exceptions from recurring variations. A rare, well-defined case may be manageable if it has a clear route for review. Frequent variations, inconsistent decisions, or undocumented workarounds suggest that the process needs clarification. Standardizing procedures before automating them reduces the risk of encoding different interpretations into the workflow.<\/p>\n<h3>What data and governance questions should be addressed?<\/h3>\n<p>Review governance as a practical design requirement. Consider whether the process uses sensitive information, how access is assigned, who remains accountable for decisions, and what human oversight is appropriate. A low-risk administrative step may need different controls from a workflow that influences important decisions. Define how errors, exceptions, and changes will be escalated, and who will monitor the process after implementation.<\/p>\n<p>Digital diagnostics and an information systems audit can help clarify how process steps, systems, and data interact. Connect those findings with data security and governance so the assessment considers both operational fit and responsible information use. This creates a more complete picture of readiness than a technology checklist alone.<\/p>\n<p>When the review exposes gaps, document each issue and assign an owner before moving forward. Formatour\u2019s process automation and optimization work can include a structured assessment of process readiness. See <a href=\"https:\/\/formatourinc.com\/en\/contact\/\">how to discuss an operational assessment<\/a>.<\/p>\n<h2 id=\"automation-or-another-improvement-compare-the-best-path-for-each-process\">Automation or Another Improvement? Compare the Best Path for Each Process<\/h2>\n<p>Automation is one possible response to operational friction, not the default solution. A process can be repeatable but offer limited business value, or involve so many system changes and controls that another improvement is more appropriate. Compare the options against the same criteria before committing resources. <strong>Resolve avoidable complexity before automating it.<\/strong><\/p>\n<p>For example, a recurring internal report may require several approvals that add no meaningful review. Removing an unnecessary approval could improve the process without technology. If teams also use different templates, standardization may be the next step. Once inputs and rules are consistent, automating a defined portion may become worthwhile. Keep human review for interpretation, accountability, or cases that don\u2019t fit established rules.<\/p>\n<h3>When is process simplification or standardization preferable?<\/h3>\n<p>Simplify when the workflow contains redundant steps, repeated checks, or handoffs that don\u2019t contribute to the outcome. Standardize when teams perform the same work in different ways, making results difficult to compare or automate reliably. Automation may suit stable, rules-based steps after that work is complete. If judgement remains central, design the process to support human decisions rather than remove them.<\/p>\n<h3>How can teams compare value, effort, and risk?<\/h3>\n<p>Use a qualitative assessment rather than treating a score as a guarantee. Rate each option against consistent factors, explain the evidence behind each rating, and note unresolved assumptions. This helps teams compare opportunities transparently without implying that every benefit can be predicted precisely at the outset.<\/p>\n<table>\n<thead>\n<tr>\n<th>Improvement path<\/th>\n<th>Business value and readiness<\/th>\n<th>Complexity, risk, and oversight<\/th>\n<\/tr>\n<\/thead>\n<tbody>\n<tr>\n<td><strong>Automation<\/strong><\/td>\n<td>May reduce manual effort or delays when steps and rules are stable.<\/td>\n<td>Consider system and data dependencies, access, exception handling, and ongoing monitoring.<\/td>\n<\/tr>\n<tr>\n<td><strong>Simplification<\/strong><\/td>\n<td>Can remove friction when steps are redundant or add little value.<\/td>\n<td>Requires agreement on what can be removed and how the revised process will be managed.<\/td>\n<\/tr>\n<tr>\n<td><strong>Standardization<\/strong><\/td>\n<td>Can improve consistency when teams follow different versions of the same workflow.<\/td>\n<td>Requires clear shared procedures, with a way to handle justified differences.<\/td>\n<\/tr>\n<tr>\n<td><strong>Human-led work<\/strong><\/td>\n<td>Remains suitable when context, judgement, or accountable decisions shape the outcome.<\/td>\n<td>Clarify decision authority, review expectations, and how exceptions are escalated.<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<p>Compare expected operational impact with process readiness, implementation complexity, data requirements, governance needs, and continuing oversight. A high-volume task may rank lower if its impact is modest or prerequisites are weak. A process with meaningful service or quality implications may warrant improvement even if automation isn\u2019t the chosen route.<\/p>\n<p>A digital transformation assessment can help frame these trade-offs across departments, systems, and organizational priorities. It gives decision-makers a shared basis for determining <em>how to identify processes to automate<\/em> while keeping simplification, standardization, and human-led execution in view. The result is a more defensible priority, grounded in business value and operational fit rather than technology preference.<\/p>\n<p><!-- autoseo-infographic --><\/p>\n<div class=\"autoseo-infographic-container\"><img fetchpriority=\"high\" decoding=\"async\" width=\"1025\" height=\"1920\" src=\"https:\/\/formatourinc.com\/wp-content\/uploads\/2026\/10\/infographic_1792468509_sUxRAkCe.webp\" class=\"autoseo-infographic-image skip-lazy no-lazy\" alt=\"Identify Processes to Automate: A Business Guide\" loading=\"eager\" data-no-lazy=\"1\" data-skip-lazy=\"1\" \/><\/div>\n<p><!-- \/autoseo-infographic --><\/p>\n<h2 id=\"how-to-prioritize-automation-opportunities-and-build-a-practical-shortlist\">How to Prioritize Automation Opportunities and Build a Practical Shortlist<\/h2>\n<p>A shortlist should make decisions easier, not simply collect ideas. Use a consistent sequence to move from reported pain points to evidence-backed candidates. Include process owners and employees who perform the work day to day. Leaders can explain intended outcomes, while frontline employees often reveal where actual practice differs from written procedures.<\/p>\n<ol>\n<li><strong>Gather candidate processes.<\/strong> Invite teams to identify recurring operational problems and name the process connected to each one. Keep the initial scope clear, such as handling a specific request type rather than improving an entire department.<\/li>\n<li><strong>Define the process and its stakeholders.<\/strong> Record its purpose, boundaries, participants, systems, inputs, outputs, and known pain points. Identify who owns the outcome and who makes decisions along the way.<\/li>\n<li><strong>Establish the evidence base.<\/strong> Review available process records and interview the people involved to understand actual work. Capture baseline measures where available, such as cycle time, rework, handoffs, or consistency of service. State gaps and limitations instead of presenting incomplete data as a reliable benchmark.<\/li>\n<li><strong>Compare and shortlist.<\/strong> Assess candidates against agreed business priorities, readiness, complexity, data needs, and governance considerations. Select a bounded opportunity with an accountable owner and an outcome the team can evaluate.<\/li>\n<\/ol>\n<h3>What evidence should teams gather before ranking candidates?<\/h3>\n<p>Combine records with first-hand accounts. Procedures, forms, system records, and available performance reports can show the intended workflow or recurring patterns. Interviews can explain workarounds, informal approvals, and missing context. Ask process owners and frontline employees where delays or corrections arise and how exceptions are handled. Note which findings are measured, which are reported, and where evidence is incomplete.<\/p>\n<p>Set a practical baseline before making a change. For example, a team might track the time from receipt to completion, how often work returns for correction, or how consistently service requirements are met. Choose measures that connect to the process\u2019s purpose. If reliable data isn\u2019t available, record that limitation and agree how to establish a usable baseline before evaluating results.<\/p>\n<h3>How can leaders turn candidate reviews into a shortlist?<\/h3>\n<p>Agree on ranking criteria before comparing proposals so each candidate receives the same consideration. A simple qualitative rating, supported by evidence and brief notes, can make trade-offs visible without suggesting false precision. Give weight to business importance, process readiness, complexity, and governance. A high-impact candidate may still need clarification first; a simpler opportunity may be a better starting point if its result is meaningful and measurable.<\/p>\n<p>Keep the shortlist manageable. For each selected opportunity, define its boundary, accountable owner, intended outcome, baseline, and key dependencies. This makes approval a practical commitment to investigate or test a specific change, not blanket permission to automate every step. Formatour provides process automation and optimization to support an evidence-led approach to candidate selection.<\/p>\n<p>Organizations can include <a href=\"https:\/\/formatourinc.com\/en\/contact\/\">process automation and optimization support<\/a> in their opportunity assessment.<\/p>\n<h2 id=\"from-shortlist-to-sustainable-improvement-plan-the-next-step\">From Shortlist to Sustainable Improvement: Plan the Next Step<\/h2>\n<p>A shortlist identifies where to focus; a defined implementation plan determines how to learn safely and make a sound next decision. Treat the first effort as a bounded test of a specific process segment, not a commitment to automate every related activity. Set the boundaries, expected outcome, accountable owner, and review approach before the change begins. This structure helps the organization assess what happened, including whether automation remains the right path.<\/p>\n<h3>What should a responsible first implementation plan include?<\/h3>\n<p>Translate the selected opportunity into clear operating parameters. Define which cases are in scope, which remain outside it, who can make decisions, and who is responsible for day-to-day oversight. Compare results with the original baseline and intended outcome using relevant measures, such as cycle time, rework, handoffs, or service consistency. Record limitations in the baseline so the review reflects the quality of the available evidence.<\/p>\n<p>Plan for exceptions before they arise. Specify how an exception is identified, where it is sent, who reviews it, and how the resolution is documented and communicated to the process owner. Make human oversight deliberate: identify decisions that require judgement, points where employees can intervene, and the person accountable for the final outcome.<\/p>\n<ul>\n<li><strong>Scope:<\/strong> Set process boundaries and define the cases the test will handle.<\/li>\n<li><strong>Ownership:<\/strong> Name the operational owner and clarify roles and decision rights.<\/li>\n<li><strong>Data governance:<\/strong> Identify relevant data, access expectations, and how information quality will be maintained.<\/li>\n<li><strong>Review:<\/strong> Choose measures, a review cadence, and criteria for adjusting, pausing, or considering wider use.<\/li>\n<\/ul>\n<p>These safeguards make it possible to respond when the workflow behaves differently than expected. If exceptions become difficult to manage, data quality declines, or the intended outcome isn\u2019t supported by evidence, the responsible next step may be to revise the process or stop the test. Expansion should follow review, not assumption.<\/p>\n<h3>How can process improvement become an ongoing capability?<\/h3>\n<p>After the test begins, review performance and exception patterns against the baseline. Look beyond whether steps were completed: assess whether the change addressed the operational need, whether employees understand how to handle unusual cases, and whether oversight is working as intended. Document what needs adjustment, who will address it, and when the outcome will be reviewed again.<\/p>\n<p>Each review can strengthen the next decision. Teams can refine their criteria, update process documentation, and identify where data or governance needs more attention. This learning cycle supports a disciplined approach to <em>how to identify processes to automate<\/em>, without treating every successful test as a reason to scale. Sustainable improvement may mean expanding an automation, redesigning part of the workflow, or keeping human-led execution where it remains the better fit.<\/p>\n<p>Formatour provides digital diagnostics and process optimization to help organizations assess workflows, connect improvement priorities with information systems, and plan for data governance and operational ownership. Details about these services are available through <a href=\"https:\/\/formatourinc.com\/en\/contact\/\">Formatour\u2019s process automation and optimization services<\/a>.<\/p>\n<h2 id=\"make-your-next-automation-decision-with-confidence\">Make Your Next Automation Decision With Confidence<\/h2>\n<p>The next step doesn\u2019t need to be a large-scale transformation. Choose one operational challenge that matters, involve the people closest to the work, and agree on what evidence would justify moving forward. A disciplined approach to <em>how to identify processes to automate<\/em> helps turn uncertainty into a clear decision, including the option to simplify the process or keep human judgement at its centre.<\/p>\n<p>That decision can also establish a stronger foundation for future improvement. As your organization learns from each assessment, it can refine how opportunities are evaluated, how accountability is assigned, and how results are reviewed. Formatour Incorporated brings over 10 years of experience across public and private sectors, supporting organizations with digital diagnostics, information systems audit, process automation, and optimization. Its tailored, practical solutions are designed to support measurable, sustainable results.<\/p>\n<p><a href=\"https:\/\/formatourinc.com\/en\/contact\/\">Discuss your process automation priorities with Formatour Incorporated<\/a> and identify a practical next step for your organization.<\/p>\n<p>With a clear business objective and thoughtful ownership, your first decision can become the start of more confident, sustainable improvement.<\/p>\n<h2 id=\"frequently-asked-questions\">Frequently Asked Questions<\/h2>\n<h3>Is every repetitive business process a good candidate for automation?<\/h3>\n<p>No. Repetition makes work easier to examine, but it doesn\u2019t prove automation will create meaningful value. A task may happen often yet have little effect on service, quality, or staff capacity. For example, automating a low-impact internal update may be less useful than addressing an occasional step that causes a serious customer delay. Consider the outcome and consequences of errors, not just how often the task occurs.<\/p>\n<h3>Can a process with frequent exceptions be automated?<\/h3>\n<h3>How do you measure whether an automation opportunity is valuable?<\/h3>\n<p>Connect evaluation to the business outcome the change is intended to support. Alongside processing speed, consider whether the work becomes more accurate, service more consistent, or employees better able to focus on higher-value responsibilities. Define how each measure will be observed and who will review it. Compare results with a suitable starting point, and account for exceptions or work shifted elsewhere so apparent improvement reflects the full process.<\/p>\n<h3>Should a company automate a process before improving it?<\/h3>\n<p>Usually, teams should first determine whether unnecessary steps or inconsistent practices can be corrected. Automating a workflow as it stands may preserve approvals, duplicate checks, or handoffs that don\u2019t contribute to its purpose. For instance, if separate departments request the same information in different formats, agreeing on a common approach may resolve friction before technology is introduced. Automate only the steps that remain useful and sufficiently well understood.<\/p>\n<h3>Who should be involved in identifying processes to automate?<\/h3>\n<p>Involve the people accountable for the process, those who perform it, and representatives responsible for relevant systems, data, and operational risk. Each group sees a different part of the work: employees can describe everyday workarounds, process owners can explain intended outcomes, and technical or governance stakeholders can identify dependencies and oversight needs. This shared review helps teams determine how to identify processes to automate without overlooking impacts beyond one department.<\/p>\n<h3>How often should an organization reassess its automation opportunities?<\/h3>\n<p>There\u2019s no single review interval that suits every organization. Reassess opportunities during planned operational reviews and when a material change affects the workflow, such as a new system, revised service expectations, a shift in responsibilities, or recurring exceptions. Also review active automations against their intended outcomes. If performance or risk changes, update the assessment rather than assuming the original decision remains appropriate.<\/p>","protected":false},"excerpt":{"rendered":"<p>The process consuming the most staff time may be the wrong one to automate first. Knowing how to identify processes to automate starts with evidence:&#8230;<\/p>","protected":false},"author":4,"featured_media":13686,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"_seopress_titles_title":"Identify Processes to Automate: A Business Guide","_seopress_titles_desc":"Learn how to identify processes to automate using operational data. Evaluate readiness, reduce risks, and choose the right workflows to scale your business.","_seopress_robots_index":"","_seopress_robots_follow":"","_seopress_robots_imageindex":"","_seopress_robots_snippet":"","_seopress_robots_primary_cat":"","_seopress_robots_breadcrumbs":"","_seopress_robots_freeze_modified_date":"","_seopress_robots_custom_modified_date":"","_seopress_robots_canonical":"","_seopress_social_fb_title":"Identify Processes to Automate: A Business Guide","_seopress_social_fb_desc":"Learn how to identify processes to automate using operational data. Evaluate readiness, reduce risks, and choose the right workflows to scale your business.","_seopress_social_fb_img":"https:\/\/formatourinc.com\/wp-content\/uploads\/2026\/10\/identify-processes-to-automate-a-business-guide.webp","_seopress_social_fb_img_attachment_id":13686,"_seopress_social_fb_img_width":0,"_seopress_social_fb_img_height":0,"_seopress_social_twitter_title":"Identify Processes to Automate: A Business Guide","_seopress_social_twitter_desc":"Learn how to identify processes to automate using operational data. Evaluate readiness, reduce risks, and choose the right workflows to scale your business.","_seopress_social_twitter_img":"https:\/\/formatourinc.com\/wp-content\/uploads\/2026\/10\/identify-processes-to-automate-a-business-guide.webp","_seopress_social_twitter_img_attachment_id":13686,"_seopress_social_twitter_img_width":0,"_seopress_social_twitter_img_height":0,"_seopress_redirections_value":"","_seopress_redirections_enabled":"","_seopress_redirections_enabled_regex":"","_seopress_redirections_logged_status":"","_seopress_redirections_param":"","_seopress_redirections_type":0,"_seopress_analysis_target_kw":"how to identify processes to automate","iawp_total_views":13,"footnotes":""},"categories":[13],"tags":[376,366,165,208,262,240,213],"class_list":["post-13685","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-blog","tag-automation-strategy","tag-business-automation","tag-digital-transformation","tag-operational-efficiency","tag-process-improvement","tag-process-optimization","tag-workflow-automation"],"acf":[],"_links":{"self":[{"href":"https:\/\/formatourinc.com\/en\/wp-json\/wp\/v2\/posts\/13685","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/formatourinc.com\/en\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/formatourinc.com\/en\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/formatourinc.com\/en\/wp-json\/wp\/v2\/users\/4"}],"replies":[{"embeddable":true,"href":"https:\/\/formatourinc.com\/en\/wp-json\/wp\/v2\/comments?post=13685"}],"version-history":[{"count":4,"href":"https:\/\/formatourinc.com\/en\/wp-json\/wp\/v2\/posts\/13685\/revisions"}],"predecessor-version":[{"id":13737,"href":"https:\/\/formatourinc.com\/en\/wp-json\/wp\/v2\/posts\/13685\/revisions\/13737"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/formatourinc.com\/en\/wp-json\/wp\/v2\/media\/13686"}],"wp:attachment":[{"href":"https:\/\/formatourinc.com\/en\/wp-json\/wp\/v2\/media?parent=13685"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/formatourinc.com\/en\/wp-json\/wp\/v2\/categories?post=13685"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/formatourinc.com\/en\/wp-json\/wp\/v2\/tags?post=13685"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}