{"id":11839,"date":"2026-04-20T23:25:20","date_gmt":"2026-04-20T17:55:20","guid":{"rendered":"https:\/\/cataligent.in\/blog\/uncategorized\/writing-for-business-vs-manual-reporting\/"},"modified":"2026-06-16T01:00:44","modified_gmt":"2026-06-16T08:00:44","slug":"writing-for-business-vs-manual-reporting","status":"publish","type":"post","link":"https:\/\/cataligent.in\/blog\/strategy-planning\/writing-for-business-vs-manual-reporting\/","title":{"rendered":"Writing for Business vs Manual Reporting: What Teams Should Know"},"content":{"rendered":"<h1>Writing for Business vs Manual Reporting: What Teams Should Know<\/h1>\n<p>Writing for business is no longer only about clear memos, board notes, and polished management updates. In transformation offices, PMOs, consulting engagements, and cost programmes, business writing now competes with manual reporting because leaders need current evidence, not just well written summaries.<\/p>\n<p>The problem is not that teams write too much. The problem is that they often write from stale spreadsheets, disconnected trackers, approval emails, and slide packs that have already drifted away from the real execution picture. A strong report should explain what changed, what decision is needed, who owns the next move, whether value is still on track, and what risk has become material.<\/p>\n<p>The central question for enterprise teams and consulting firms is simple: should reporting be treated as a writing exercise or as an execution control process? The answer matters because a well written status note can still hide weak ownership, missing approvals, unvalidated savings, and unclear milestones.<\/p>\n<h2>Why manual reporting weakens business writing<\/h2>\n<p>Manual reporting usually begins with good intent. A project manager updates a spreadsheet, a consultant asks workstream owners for progress, a finance controller confirms a number, and a leader expects a management ready update by Friday. The cycle looks familiar, but it creates several points of risk.<\/p>\n<ul>\n<li>Different teams use different definitions for red, amber, and green status.<\/li>\n<li>Financial potential is reported separately from implementation progress.<\/li>\n<li>Approvals are buried in email chains rather than tied to the measure being approved.<\/li>\n<li>Slide decks are refreshed manually, so one page may disagree with another.<\/li>\n<li>Risks and dependencies are described in words without a clear escalation path.<\/li>\n<\/ul>\n<p>When those issues exist, the writing team has to compensate. They add caveats, rewrite narratives, chase missing updates, and soften unclear data. The final document may sound professional, but it can still fail the leadership test: can the steering committee make a confident decision from it?<\/p>\n<h2>What business writing should prove<\/h2>\n<p>Good business writing in execution environments should do more than summarize activity. It should prove whether a programme is governed, whether progress is supported by evidence, and whether the expected value is still credible. For example, a useful transformation update should show the initiative owner, sponsor, controller, milestone status, forecast impact, actual impact, risks, decisions needed, and next reporting date.<\/p>\n<p>That is why writing and reporting cannot be separated. If the underlying execution model is weak, the report becomes a negotiation over wording. If the execution model is governed, the report becomes a clear narrative drawn from trusted data.<\/p>\n<h2>Where teams lose time in the reporting cycle<\/h2>\n<p>Teams usually lose time in predictable places. One group is confirming milestone dates. Another is asking finance to validate a savings number. A third is preparing a slide for a steering committee. A fourth is checking whether an approval actually happened. These are not writing problems. They are governance and data control problems.<\/p>\n<p>Consulting firms feel the cost of this quickly. Analysts spend hours reconciling versions, partners review inconsistent packs, and client teams question which number is current. Enterprise PMOs face the same issue when multiple workstreams report into one executive cadence. The result is reporting effort without enough execution control.<\/p>\n<h2>How to move from manual reporting to governed reporting<\/h2>\n<p>A better model starts before the first report is written. Teams should define the hierarchy of work, assign ownership, set status rules, connect milestones to value, and agree which approvals are required before a measure can move forward. This creates the conditions for writing that is clear because the execution data is clear.<\/p>\n<ul>\n<li>Define the portfolio, programme, project, measure package, and measure structure.<\/li>\n<li>Separate implementation progress from expected business value.<\/li>\n<li>Set a reporting cadence that shows achievements, issues, decisions, and next steps.<\/li>\n<li>Require evidence for important stage movements and value claims.<\/li>\n<li>Give leaders a current view instead of a manually rebuilt slide pack.<\/li>\n<\/ul>\n<h2>How Cataligent Helps Through CAT4<\/h2>\n<p><a href=\"https:\/\/cataligent.in\/\">Cataligent<\/a> helps consulting firms and enterprise teams replace manual reporting cycles with governed execution reporting through CAT4, its no code strategy execution platform. For teams working on <a href=\"https:\/\/cataligent.in\/business-transformation\">business transformation<\/a>, project portfolios, or value tracking, CAT4 connects initiatives, owners, workflows, approvals, financial impact, and executive reporting in one controlled platform.<\/p>\n<p>The platform is especially useful where writing quality depends on reliable execution data. CAT4 can track Implementation Status and Potential Status separately, so leadership can see whether milestones are progressing and whether the expected value is still credible. Its Degree of Implementation, or DoI, model supports stage gate control from defined work to controller backed closure.<\/p>\n<p>For a consulting firm, this means the engagement method can be configured into a repeatable reporting and governance model. For an enterprise PMO, it means workstream updates, risks, approvals, and financial data can roll up into management ready reporting without rebuilding the story from scattered files each cycle.<\/p>\n<h2>What teams should check before changing their reporting approach<\/h2>\n<p>Before replacing manual reporting habits, leaders should ask five practical questions. Where does the current status data originate? Who can change it? What evidence supports a change in status? How is financial impact validated? Which decisions are waiting for leadership approval?<\/p>\n<p>Those questions expose whether the organization has a writing issue or an execution system issue. If every answer depends on another spreadsheet or another email, the reporting model will remain fragile. If the answers sit inside a governed platform with clear ownership and audit history, business writing becomes sharper and shorter.<\/p>\n<h2>A practical reporting operating model<\/h2>\n<p>Teams can make this shift without turning every update into a heavy process. The operating model should define one owner for each measure, one place for current status, one rule for financial validation, and one cadence for leadership review. It should also define what belongs in a report: progress against plan, change in expected value, key risks, decision needed, owner of the next action, and evidence for important status changes.<\/p>\n<p>This model gives business writing a cleaner job. The writer no longer has to ask ten people which number is correct or whether an approval was final. Instead, the report can focus on what leaders need to understand: where execution is moving, where value is slipping, where a decision is blocked, and what action should happen before the next reporting period.<\/p>\n<h2>Specific CTA for teams still relying on manual packs<\/h2>\n<p>Still rebuilding business reports from spreadsheets, emails, and slide decks? Talk to Cataligent about using CAT4 to connect execution control, value tracking, approvals, and leadership reporting before the next reporting cycle becomes another manual exercise.<\/p>\n<h2>FAQs<\/h2>\n<h3>Q: Is manual reporting always a problem for business teams?<\/h3>\n<p>Manual reporting is not always wrong, but it becomes risky when many owners, approvals, savings claims, and leadership decisions depend on it. The risk grows when the report is treated as the source of truth instead of being generated from governed execution data.<\/p>\n<h3>Q: How can business writing improve without adding more reporting effort?<\/h3>\n<p>Business writing improves when teams reduce reconciliation work and write from current, structured execution data. A governed platform gives writers clearer status, ownership, financial context, and decision points before the narrative is drafted.<\/p>\n<h3>Q: How does Cataligent support better reporting through CAT4?<\/h3>\n<p>Cataligent helps teams configure CAT4 around initiatives, workflows, approvals, financial tracking, DoI stage gates, and executive reporting. This gives consulting firms and enterprise leaders a stronger basis for reports that connect activity with measurable execution.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>Writing for Business vs Manual Reporting: What Teams Should Know Writing for business is no longer only about clear memos, board notes, and polished management updates. In transformation offices, PMOs, consulting engagements, and cost programmes, business writing now competes with manual reporting because leaders need current evidence, not just well written summaries. The problem is [&hellip;]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[2104],"tags":[2033,568,632,1739,2107,1967,2106,2105],"class_list":["post-11839","post","type-post","status-publish","format-standard","hentry","category-strategy-planning","tag-business-strategy","tag-cost-reduction-strategies","tag-cost-reduction-strategy","tag-digital-strategy","tag-planning","tag-strategic-decision-making","tag-strategic-planning","tag-strategy-planning"],"yoast_head":"<!-- This site is optimized with the Yoast SEO plugin v27.4 - https:\/\/yoast.com\/product\/yoast-seo-wordpress\/ -->\n<title>Writing for Business vs Manual Reporting: What Teams Should Know - Cataligent<\/title>\n<meta name=\"robots\" content=\"index, follow, max-snippet:-1, max-image-preview:large, max-video-preview:-1\" \/>\n<link rel=\"canonical\" href=\"https:\/\/cataligent.in\/blog\/strategy-planning\/writing-for-business-vs-manual-reporting\/\" \/>\n<meta property=\"og:locale\" content=\"en_US\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"Writing for Business vs Manual Reporting: What Teams Should Know - Cataligent\" \/>\n<meta property=\"og:description\" content=\"Writing for Business vs Manual Reporting: What Teams Should Know Writing for business is no longer only about clear memos, board notes, and polished management updates. In transformation offices, PMOs, consulting engagements, and cost programmes, business writing now competes with manual reporting because leaders need current evidence, not just well written summaries. The problem is [&hellip;]\" \/>\n<meta property=\"og:url\" content=\"https:\/\/cataligent.in\/blog\/strategy-planning\/writing-for-business-vs-manual-reporting\/\" \/>\n<meta property=\"og:site_name\" content=\"Cataligent\" \/>\n<meta property=\"article:publisher\" content=\"https:\/\/www.facebook.com\/Cataligentstrategyimplementation\/\" \/>\n<meta property=\"article:published_time\" content=\"2026-04-20T17:55:20+00:00\" \/>\n<meta property=\"article:modified_time\" content=\"2026-06-16T08:00:44+00:00\" \/>\n<meta name=\"author\" content=\"cat_admin_usr\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:creator\" content=\"@cataligentindia\" \/>\n<meta name=\"twitter:site\" content=\"@cataligentindia\" \/>\n<meta name=\"twitter:label1\" content=\"Written by\" \/>\n\t<meta name=\"twitter:data1\" content=\"cat_admin_usr\" \/>\n\t<meta name=\"twitter:label2\" content=\"Est. reading time\" \/>\n\t<meta name=\"twitter:data2\" content=\"6 minutes\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\\\/\\\/schema.org\",\"@graph\":[{\"@type\":\"Article\",\"@id\":\"https:\\\/\\\/cataligent.in\\\/blog\\\/strategy-planning\\\/writing-for-business-vs-manual-reporting\\\/#article\",\"isPartOf\":{\"@id\":\"https:\\\/\\\/cataligent.in\\\/blog\\\/strategy-planning\\\/writing-for-business-vs-manual-reporting\\\/\"},\"author\":{\"name\":\"cat_admin_usr\",\"@id\":\"https:\\\/\\\/cataligent.in\\\/blog\\\/#\\\/schema\\\/person\\\/649c37d6027e076e1e76bd18bac05756\"},\"headline\":\"Writing for Business vs Manual Reporting: What Teams Should Know\",\"datePublished\":\"2026-04-20T17:55:20+00:00\",\"dateModified\":\"2026-06-16T08:00:44+00:00\",\"mainEntityOfPage\":{\"@id\":\"https:\\\/\\\/cataligent.in\\\/blog\\\/strategy-planning\\\/writing-for-business-vs-manual-reporting\\\/\"},\"wordCount\":1234,\"commentCount\":0,\"publisher\":{\"@id\":\"https:\\\/\\\/cataligent.in\\\/blog\\\/#organization\"},\"keywords\":[\"Business Strategy\",\"Cost Reduction Strategies\",\"Cost Reduction Strategy\",\"Digital Strategy\",\"Planning\",\"Strategic Decision-Making\",\"Strategic Planning\",\"Strategy Planning\"],\"articleSection\":[\"Strategy Planning\"],\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"CommentAction\",\"name\":\"Comment\",\"target\":[\"https:\\\/\\\/cataligent.in\\\/blog\\\/strategy-planning\\\/writing-for-business-vs-manual-reporting\\\/#respond\"]}]},{\"@type\":\"WebPage\",\"@id\":\"https:\\\/\\\/cataligent.in\\\/blog\\\/strategy-planning\\\/writing-for-business-vs-manual-reporting\\\/\",\"url\":\"https:\\\/\\\/cataligent.in\\\/blog\\\/strategy-planning\\\/writing-for-business-vs-manual-reporting\\\/\",\"name\":\"Writing for Business vs Manual Reporting: What Teams Should Know - Cataligent\",\"isPartOf\":{\"@id\":\"https:\\\/\\\/cataligent.in\\\/blog\\\/#website\"},\"datePublished\":\"2026-04-20T17:55:20+00:00\",\"dateModified\":\"2026-06-16T08:00:44+00:00\",\"breadcrumb\":{\"@id\":\"https:\\\/\\\/cataligent.in\\\/blog\\\/strategy-planning\\\/writing-for-business-vs-manual-reporting\\\/#breadcrumb\"},\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\\\/\\\/cataligent.in\\\/blog\\\/strategy-planning\\\/writing-for-business-vs-manual-reporting\\\/\"]}]},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\\\/\\\/cataligent.in\\\/blog\\\/strategy-planning\\\/writing-for-business-vs-manual-reporting\\\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Home\",\"item\":\"https:\\\/\\\/cataligent.in\\\/blog\\\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"Writing for Business vs Manual Reporting: What Teams Should Know\"}]},{\"@type\":\"WebSite\",\"@id\":\"https:\\\/\\\/cataligent.in\\\/blog\\\/#website\",\"url\":\"https:\\\/\\\/cataligent.in\\\/blog\\\/\",\"name\":\"https:\\\/\\\/cataligent.in\\\/\",\"description\":\"Strategy Execution Tool for Cost Saving Program\",\"publisher\":{\"@id\":\"https:\\\/\\\/cataligent.in\\\/blog\\\/#organization\"},\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":{\"@type\":\"EntryPoint\",\"urlTemplate\":\"https:\\\/\\\/cataligent.in\\\/blog\\\/?s={search_term_string}\"},\"query-input\":{\"@type\":\"PropertyValueSpecification\",\"valueRequired\":true,\"valueName\":\"search_term_string\"}}],\"inLanguage\":\"en-US\"},{\"@type\":\"Organization\",\"@id\":\"https:\\\/\\\/cataligent.in\\\/blog\\\/#organization\",\"name\":\"Cataligent Project Pvt. Ltd.\",\"url\":\"https:\\\/\\\/cataligent.in\\\/blog\\\/\",\"logo\":{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\\\/\\\/cataligent.in\\\/blog\\\/#\\\/schema\\\/logo\\\/image\\\/\",\"url\":\"https:\\\/\\\/cataligent.in\\\/blog\\\/wp-content\\\/uploads\\\/2025\\\/01\\\/logoColored-1.png\",\"contentUrl\":\"https:\\\/\\\/cataligent.in\\\/blog\\\/wp-content\\\/uploads\\\/2025\\\/01\\\/logoColored-1.png\",\"width\":296,\"height\":75,\"caption\":\"Cataligent Project Pvt. Ltd.\"},\"image\":{\"@id\":\"https:\\\/\\\/cataligent.in\\\/blog\\\/#\\\/schema\\\/logo\\\/image\\\/\"},\"sameAs\":[\"https:\\\/\\\/www.facebook.com\\\/Cataligentstrategyimplementation\\\/\",\"https:\\\/\\\/x.com\\\/cataligentindia\",\"https:\\\/\\\/www.linkedin.com\\\/company\\\/cataligentstrategy\\\/\",\"https:\\\/\\\/www.instagram.com\\\/cataligentindia\\\/\"]},{\"@type\":\"Person\",\"@id\":\"https:\\\/\\\/cataligent.in\\\/blog\\\/#\\\/schema\\\/person\\\/649c37d6027e076e1e76bd18bac05756\",\"name\":\"cat_admin_usr\",\"image\":{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\\\/\\\/secure.gravatar.com\\\/avatar\\\/5a61f472589fc237202ca132bc60e152f3e6a99196f2e24dcf2a5f01626f1b4a?s=96&d=mm&r=g\",\"url\":\"https:\\\/\\\/secure.gravatar.com\\\/avatar\\\/5a61f472589fc237202ca132bc60e152f3e6a99196f2e24dcf2a5f01626f1b4a?s=96&d=mm&r=g\",\"contentUrl\":\"https:\\\/\\\/secure.gravatar.com\\\/avatar\\\/5a61f472589fc237202ca132bc60e152f3e6a99196f2e24dcf2a5f01626f1b4a?s=96&d=mm&r=g\",\"caption\":\"cat_admin_usr\"},\"sameAs\":[\"https:\\\/\\\/cataligent.in\\\/blog\"],\"url\":\"https:\\\/\\\/cataligent.in\\\/blog\\\/author\\\/cat_admin_usr\\\/\"}]}<\/script>\n<!-- \/ Yoast SEO plugin. -->","yoast_head_json":{"title":"Writing for Business vs Manual Reporting: What Teams Should Know - Cataligent","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:\/\/cataligent.in\/blog\/strategy-planning\/writing-for-business-vs-manual-reporting\/","og_locale":"en_US","og_type":"article","og_title":"Writing for Business vs Manual Reporting: What Teams Should Know - Cataligent","og_description":"Writing for Business vs Manual Reporting: What Teams Should Know Writing for business is no longer only about clear memos, board notes, and polished management updates. In transformation offices, PMOs, consulting engagements, and cost programmes, business writing now competes with manual reporting because leaders need current evidence, not just well written summaries. The problem is [&hellip;]","og_url":"https:\/\/cataligent.in\/blog\/strategy-planning\/writing-for-business-vs-manual-reporting\/","og_site_name":"Cataligent","article_publisher":"https:\/\/www.facebook.com\/Cataligentstrategyimplementation\/","article_published_time":"2026-04-20T17:55:20+00:00","article_modified_time":"2026-06-16T08:00:44+00:00","author":"cat_admin_usr","twitter_card":"summary_large_image","twitter_creator":"@cataligentindia","twitter_site":"@cataligentindia","twitter_misc":{"Written by":"cat_admin_usr","Est. reading time":"6 minutes"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"Article","@id":"https:\/\/cataligent.in\/blog\/strategy-planning\/writing-for-business-vs-manual-reporting\/#article","isPartOf":{"@id":"https:\/\/cataligent.in\/blog\/strategy-planning\/writing-for-business-vs-manual-reporting\/"},"author":{"name":"cat_admin_usr","@id":"https:\/\/cataligent.in\/blog\/#\/schema\/person\/649c37d6027e076e1e76bd18bac05756"},"headline":"Writing for Business vs Manual Reporting: What Teams Should Know","datePublished":"2026-04-20T17:55:20+00:00","dateModified":"2026-06-16T08:00:44+00:00","mainEntityOfPage":{"@id":"https:\/\/cataligent.in\/blog\/strategy-planning\/writing-for-business-vs-manual-reporting\/"},"wordCount":1234,"commentCount":0,"publisher":{"@id":"https:\/\/cataligent.in\/blog\/#organization"},"keywords":["Business Strategy","Cost Reduction Strategies","Cost Reduction Strategy","Digital Strategy","Planning","Strategic Decision-Making","Strategic Planning","Strategy Planning"],"articleSection":["Strategy Planning"],"inLanguage":"en-US","potentialAction":[{"@type":"CommentAction","name":"Comment","target":["https:\/\/cataligent.in\/blog\/strategy-planning\/writing-for-business-vs-manual-reporting\/#respond"]}]},{"@type":"WebPage","@id":"https:\/\/cataligent.in\/blog\/strategy-planning\/writing-for-business-vs-manual-reporting\/","url":"https:\/\/cataligent.in\/blog\/strategy-planning\/writing-for-business-vs-manual-reporting\/","name":"Writing for Business vs Manual Reporting: What Teams Should Know - Cataligent","isPartOf":{"@id":"https:\/\/cataligent.in\/blog\/#website"},"datePublished":"2026-04-20T17:55:20+00:00","dateModified":"2026-06-16T08:00:44+00:00","breadcrumb":{"@id":"https:\/\/cataligent.in\/blog\/strategy-planning\/writing-for-business-vs-manual-reporting\/#breadcrumb"},"inLanguage":"en-US","potentialAction":[{"@type":"ReadAction","target":["https:\/\/cataligent.in\/blog\/strategy-planning\/writing-for-business-vs-manual-reporting\/"]}]},{"@type":"BreadcrumbList","@id":"https:\/\/cataligent.in\/blog\/strategy-planning\/writing-for-business-vs-manual-reporting\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https:\/\/cataligent.in\/blog\/"},{"@type":"ListItem","position":2,"name":"Writing for Business vs Manual Reporting: What Teams Should Know"}]},{"@type":"WebSite","@id":"https:\/\/cataligent.in\/blog\/#website","url":"https:\/\/cataligent.in\/blog\/","name":"https:\/\/cataligent.in\/","description":"Strategy Execution Tool for Cost Saving Program","publisher":{"@id":"https:\/\/cataligent.in\/blog\/#organization"},"potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/cataligent.in\/blog\/?s={search_term_string}"},"query-input":{"@type":"PropertyValueSpecification","valueRequired":true,"valueName":"search_term_string"}}],"inLanguage":"en-US"},{"@type":"Organization","@id":"https:\/\/cataligent.in\/blog\/#organization","name":"Cataligent Project Pvt. Ltd.","url":"https:\/\/cataligent.in\/blog\/","logo":{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/cataligent.in\/blog\/#\/schema\/logo\/image\/","url":"https:\/\/cataligent.in\/blog\/wp-content\/uploads\/2025\/01\/logoColored-1.png","contentUrl":"https:\/\/cataligent.in\/blog\/wp-content\/uploads\/2025\/01\/logoColored-1.png","width":296,"height":75,"caption":"Cataligent Project Pvt. Ltd."},"image":{"@id":"https:\/\/cataligent.in\/blog\/#\/schema\/logo\/image\/"},"sameAs":["https:\/\/www.facebook.com\/Cataligentstrategyimplementation\/","https:\/\/x.com\/cataligentindia","https:\/\/www.linkedin.com\/company\/cataligentstrategy\/","https:\/\/www.instagram.com\/cataligentindia\/"]},{"@type":"Person","@id":"https:\/\/cataligent.in\/blog\/#\/schema\/person\/649c37d6027e076e1e76bd18bac05756","name":"cat_admin_usr","image":{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/secure.gravatar.com\/avatar\/5a61f472589fc237202ca132bc60e152f3e6a99196f2e24dcf2a5f01626f1b4a?s=96&d=mm&r=g","url":"https:\/\/secure.gravatar.com\/avatar\/5a61f472589fc237202ca132bc60e152f3e6a99196f2e24dcf2a5f01626f1b4a?s=96&d=mm&r=g","contentUrl":"https:\/\/secure.gravatar.com\/avatar\/5a61f472589fc237202ca132bc60e152f3e6a99196f2e24dcf2a5f01626f1b4a?s=96&d=mm&r=g","caption":"cat_admin_usr"},"sameAs":["https:\/\/cataligent.in\/blog"],"url":"https:\/\/cataligent.in\/blog\/author\/cat_admin_usr\/"}]}},"_links":{"self":[{"href":"https:\/\/cataligent.in\/blog\/wp-json\/wp\/v2\/posts\/11839","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/cataligent.in\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/cataligent.in\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/cataligent.in\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/cataligent.in\/blog\/wp-json\/wp\/v2\/comments?post=11839"}],"version-history":[{"count":0,"href":"https:\/\/cataligent.in\/blog\/wp-json\/wp\/v2\/posts\/11839\/revisions"}],"wp:attachment":[{"href":"https:\/\/cataligent.in\/blog\/wp-json\/wp\/v2\/media?parent=11839"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/cataligent.in\/blog\/wp-json\/wp\/v2\/categories?post=11839"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/cataligent.in\/blog\/wp-json\/wp\/v2\/tags?post=11839"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}