{"id":1532,"date":"2026-07-16T05:32:44","date_gmt":"2026-07-16T05:32:44","guid":{"rendered":"https:\/\/www.dcirrus.com\/blog\/?p=1532"},"modified":"2026-07-16T05:39:26","modified_gmt":"2026-07-16T05:39:26","slug":"concurrent-deals-framework-strategies","status":"publish","type":"post","link":"https:\/\/www.dcirrus.com\/blog\/2026\/07\/concurrent-deals-framework-strategies\/","title":{"rendered":"The Concurrent Deal Framework: A Strategic Playbook for Managing Parallel IPO &amp; M&amp;A Workflows in a VDR"},"content":{"rendered":"\n<p>When you are running&nbsp;<strong>concurrent deals<\/strong>, the real failure mode is not lack of effort. It is cross-contamination: the wrong draft, the wrong counterparty, the wrong watermark, or the wrong Q&amp;A thread slipping into the wrong mandate. In a market where one team may be handling two DRHPs, a QIP, and an open offer at once, a single-deal tool is the wrong mental model. You need&nbsp;<strong>pipeline management<\/strong>&nbsp;and&nbsp;<strong>multi-deal orchestration<\/strong>, not project tracking.<\/p>\n\n\n\n<p class=\"py-4\">That is the gap this playbook closes. It gives you a practical framework for running&nbsp;<strong>parallel workflows<\/strong>&nbsp;in one VDR without losing control of permissions, audit trails, or deal velocity. If you are trying to stand up a compliant data room in under 4.5 months, keep SEBI inspection-ready records, and stop email from slowing diligence by 2 to 3 weeks, this is the structure to use.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Why&nbsp;<strong>concurrent deals<\/strong>&nbsp;need a different operating model<\/h2>\n\n\n\n<p class=\"py-4\">A merchant banker\u2019s live pipeline is a portfolio, not a queue. That matters because the same counterparties, the same documents, and the same compliance obligations often appear across multiple mandates at the same time.<\/p>\n\n\n\n<p>The operating problem is simple: generic project tools assume one owner, one timeline, one set of files. But IPO and M&amp;A work demands isolated workspaces, strict role separation, and a clean record of every action taken inside each deal. That is why the framework below is built around&nbsp;<strong>pipeline management<\/strong>&nbsp;at the workspace level.<\/p>\n\n\n\n<p class=\"py-4\">It also fits the regulatory reality. For public issues, the DRHP must follow Schedule VI disclosure logic, merchant bankers must maintain a&nbsp;<a href=\"https:\/\/www.dcirrus.com\/repository\">Repository of Documents<\/a>, and PIT rules require structured logging of UPSI sharing. In other words, the workflow has to satisfy compliance first, speed second, and convenience third.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">The 10-step framework for&nbsp;<strong>multi-deal orchestration<\/strong><\/h2>\n\n\n\n<h3 class=\"wp-block-heading py-4\">1) Stand up one isolated workspace per mandate<\/h3>\n\n\n\n<p>Start with isolation. Every deal gets its own workspace, tenant, audit trail, and retention policy, even when you are running three to five live mandates.<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Create a separate workspace for every IPO, M&amp;A buy-side, M&amp;A sell-side, or pre-IPO restructuring mandate.<\/li>\n\n\n\n<li>Use a unique tenant identifier and deal code.<\/li>\n\n\n\n<li>Avoid issuer names in URLs or document IDs.<\/li>\n\n\n\n<li>Preload default permission templates by deal type.<\/li>\n\n\n\n<li>Enroll users in SSO or MFA before first access.<\/li>\n<\/ul>\n\n\n\n<p class=\"py-4\">Why this matters: it prevents permission leakage, watermark cross-contamination, and accidental reuse of prior deal material.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">2) Build the folder spine around Schedule VI<\/h3>\n\n\n\n<p>Do not use a generic M&amp;A folder tree. For IPO work, the&nbsp;<a href=\"https:\/\/www.dcirrus.com\/blog\/2026\/03\/designing-scalable-folder-structures-for-multi-round-fundraising-and-ma-deals\">folder structure<\/a>&nbsp;should mirror the disclosure order in Schedule VI so diligence maps directly to the DRHP.<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Organize the top level around incorporation, capital structure, business overview, financial information, management, related-party transactions, risk factors, use of proceeds, and litigation.<\/li>\n\n\n\n<li>Split each section into filings, supporting documents, and third-party reports.<\/li>\n\n\n\n<li>Reserve\u00a0<code>99_Repository_SEBI<\/code>\u00a0for the Repository of Documents.<\/li>\n\n\n\n<li>Reserve\u00a0<code>98_Audit_Trail_Exports<\/code>\u00a0for immutable audit exports.<\/li>\n\n\n\n<li>Tag each upload with deal code, upload date, and uploader identity.<\/li>\n<\/ul>\n\n\n\n<p class=\"py-4\">This gives you faster retrieval and cleaner disclosure alignment when SEBI asks how a point was supported.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">3) Lock down role-based access before the first external login<\/h3>\n\n\n\n<p class=\"py-4\">This is where most teams get loose. Once ten-plus counterparties start entering the room, access must be role-based, not ad hoc.<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Predefine roles such as Issuer CFO, Issuer CS, Statutory Auditor, Legal Counsel on both sides, Book Runner Lead, Co-Manager, Registrar, Printer, and SEBI Observer.<\/li>\n\n\n\n<li>Map each role to specific folders and permissions.<\/li>\n\n\n\n<li>Use view, download, print, and annotate controls deliberately.<\/li>\n\n\n\n<li>Disable print and download by default for sensitive folders.<\/li>\n\n\n\n<li>Set shorter session timeouts for non-issuer users.<\/li>\n<\/ul>\n\n\n\n<p class=\"py-4\">This is how you support&nbsp;<strong>parallel workflows<\/strong>&nbsp;without exposing working papers across counterparties.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">4) Turn on immutable audit trails from day one<\/h3>\n\n\n\n<p class=\"py-4\">If SEBI asks how diligence was handled, your answer has to be in the log. The Repository of Documents regime and PIT requirements both depend on a tamper-evident record.<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Log login, logout, view, open, download, print, share, and permission changes.<\/li>\n\n\n\n<li>Capture IP address, device fingerprint, and timestamp for every action.<\/li>\n\n\n\n<li>Lock the audit log so it can only be appended to or exported.<\/li>\n\n\n\n<li>Export audit logs weekly into\u00a0<code>98_Audit_Trail_Exports<\/code>.<\/li>\n\n\n\n<li>Cross-stamp monthly exports to the issuer\u2019s compliance officer.<\/li>\n<\/ul>\n\n\n\n<p class=\"py-4\">This is not a back-office feature. It is the operational proof that your process was controlled.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">5) Replace email Q&amp;A with a central hub<\/h3>\n\n\n\n<p class=\"py-4\">Email is where deal flow slows down. It also creates the exact kind of unstructured record that is hard to defend later.<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Use one\u00a0<a href=\"https:\/\/www.dcirrus.com\/m-and-a-due-diligence-q-and-a-virtual-data-room-2\">Q&amp;A workspace<\/a>\u00a0per mandate.<\/li>\n\n\n\n<li>Route legal questions to counsel, accounting questions to the auditor, and commercial questions to management.<\/li>\n\n\n\n<li>Set response SLAs at 24 hours for routine questions and 4 hours for urgent ones.<\/li>\n\n\n\n<li>Track question owner, status, and resolution date.<\/li>\n\n\n\n<li>Export Q&amp;A history weekly to compliance.<\/li>\n<\/ul>\n\n\n\n<p class=\"py-4\">If you are trying to compress diligence and stop the usual 2 to 3 week slippage, this is one of the biggest leverage points in the entire framework.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">6) Apply dynamic watermarks before any external download<\/h3>\n\n\n\n<p class=\"py-4\">Every external view or download should leave a trace. That is basic discipline in regulated transactions.<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Embed viewer email, IP address, and timestamp in\u00a0<a href=\"https:\/\/www.dcirrus.com\/blog\/2025\/11\/digital-rights-management-in-virtual-data-rooms-protecting-your-most-valuable-assets\">dynamic watermarks<\/a>.<\/li>\n\n\n\n<li>Use different watermark treatments for issuer and BRLM materials.<\/li>\n\n\n\n<li>Apply full-page watermarks for highly confidential documents.<\/li>\n\n\n\n<li>Block screen capture and printing by default.<\/li>\n\n\n\n<li>Log every print attempt and screen-block event.<\/li>\n<\/ul>\n\n\n\n<p class=\"py-4\">This does two things at once: it deters leakage and it makes trace-back possible if a document shows up where it should not.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">7) Run a visible deal-clock dashboard<\/h3>\n\n\n\n<p class=\"py-4\">When three or more deals are live, deadlines do not stay in one person\u2019s head. They need to be visible to every internal stakeholder.<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Show DRHP filing date, RHP date, issue open and close, listing date, and post-issue milestones.<\/li>\n\n\n\n<li>Surface SEBI observation windows and other regulatory SLAs.<\/li>\n\n\n\n<li>Show Q&amp;A SLA performance.<\/li>\n\n\n\n<li>Show audit export cadence.<\/li>\n\n\n\n<li>Push daily deadline digests to every role group.<\/li>\n<\/ul>\n\n\n\n<p class=\"py-4\">This is the practical backbone of&nbsp;<strong>pipeline management<\/strong>. It gives bankers, lawyers, and compliance one shared timeline instead of separate spreadsheets.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">8) Use AI to accelerate indexing and response prep<\/h3>\n\n\n\n<p class=\"py-4\">AI is not the replacement for judgment. It is the multiplier that stops a small team from drowning in document volume.<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Auto-tag uploads against the Schedule VI spine.<\/li>\n\n\n\n<li>Surface related-party, materiality, and risk-factor language.<\/li>\n\n\n\n<li>Use\u00a0<a href=\"https:\/\/www.dcirrus.com\/blog\/2024\/11\/accelerating-due-diligence-the-role-of-ai-in-faster-and-more-accurate-data-room-analysis\">semantic search<\/a>\u00a0to draft Q&amp;A responses faster.<\/li>\n\n\n\n<li>Assist with redaction of sensitive personal data.<\/li>\n\n\n\n<li>Flag duplicate or stale uploads.<\/li>\n<\/ul>\n\n\n\n<p class=\"py-4\">Used well, this turns document retrieval from a manual hunt into a controlled process, which is exactly what&nbsp;<strong>multi-deal orchestration<\/strong>&nbsp;needs.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">9) Rehearse compliance before listing<\/h3>\n\n\n\n<p class=\"py-4\">By the time you are in the final stretch, surprises are expensive. Rehearsal is what converts unknowns into knowns before the deal clock gets tight.<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Begin weekly rehearsals about six weeks before listing.<\/li>\n\n\n\n<li>Simulate SEBI observation responses with mock queries.<\/li>\n\n\n\n<li>Run a book-building dry run with the syndicate team.<\/li>\n\n\n\n<li>Rehearse allotment and listing-day logistics with the registrar and exchanges.<\/li>\n\n\n\n<li>Store rehearsal notes in\u00a0<code>99_Rehearsal_Notes<\/code>.<\/li>\n<\/ul>\n\n\n\n<p class=\"py-4\">This is where you reduce avoidable friction in the final mile.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">10) Lock and archive the workspace without losing the record<\/h3>\n\n\n\n<p class=\"py-4\">Closing a deal is not the same as deleting its history. The record has to stay available for the regulatory retention window.<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Lock the workspace on listing day plus 30 days.<\/li>\n\n\n\n<li>Export the full audit trail to immutable storage.<\/li>\n\n\n\n<li>Preserve\u00a0<code>98_Audit_Trail_Exports<\/code>\u00a0and\u00a0<code>99_Repository_SEBI<\/code>.<\/li>\n\n\n\n<li>Keep the Repository of Documents index for the life of the listing.<\/li>\n\n\n\n<li>Maintain an off-platform disaster-recovery copy with quarterly restore tests.<\/li>\n<\/ul>\n\n\n\n<p class=\"py-4\">This is how you keep the process defensible after the deal closes.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">How to set up roles and responsibility in practice<\/h2>\n\n\n\n<p class=\"py-4\">A framework only works if ownership is clear. For concurrent deal work, the BRLM Lead should stay accountable for workspace setup, Q&amp;A governance, audit exports, and archive closure.<\/p>\n\n\n\n<p>A simple operating matrix looks like this:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Workspace creation and tenant isolation<\/strong>: BRLM Lead accountable<\/li>\n\n\n\n<li><strong>Schedule VI folder spine<\/strong>: BRLM Lead responsible<\/li>\n\n\n\n<li><strong>Role-based access provisioning<\/strong>: BRLM Lead accountable<\/li>\n\n\n\n<li><strong>Document upload and tagging<\/strong>: Issuer management responsible<\/li>\n\n\n\n<li><strong>Q&amp;A routing and SLA tracking<\/strong>: BRLM Lead accountable<\/li>\n\n\n\n<li><strong>Weekly audit export<\/strong>: BRLM Lead accountable<\/li>\n\n\n\n<li><strong>DRHP filing<\/strong>: BRLM accountable, with legal counsel involved<\/li>\n\n\n\n<li><strong>Observation-letter response<\/strong>: BRLM accountable, with counsel support<\/li>\n\n\n\n<li><strong>Repository of Documents preparation<\/strong>: BRLM accountable<\/li>\n\n\n\n<li><strong>Listing-day close and archive<\/strong>: BRLM accountable<\/li>\n\n\n\n<li><strong>Post-listing repository maintenance<\/strong>: BRLM accountable<\/li>\n<\/ul>\n\n\n\n<p class=\"py-4\">The cadence should be equally explicit:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Daily 9:30 AM stand-up for 15 minutes<\/li>\n\n\n\n<li>Weekly audit-log review every Friday<\/li>\n\n\n\n<li>Bi-weekly DRHP or RHP review<\/li>\n\n\n\n<li>Quarterly cross-deal retrospective across all live mandates<\/li>\n<\/ul>\n\n\n\n<p class=\"py-4\">That rhythm is what keeps&nbsp;<strong>parallel workflows<\/strong>&nbsp;from becoming reactive.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">What breaks in concurrent deal management<\/h2>\n\n\n\n<h3 class=\"wp-block-heading py-4\">Permission sprawl<\/h3>\n\n\n\n<p>This happens when a user keeps access after moving between mandates.<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Tie access to workspace, not to person alone.<\/li>\n\n\n\n<li>Deprovision on role change.<\/li>\n\n\n\n<li>Run quarterly access reviews.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading py-4\">Version confusion<\/h3>\n\n\n\n<p>This is what happens when two advisors both think they own \u201cv3.\u201d<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Use a\u00a0<a href=\"https:\/\/www.dcirrus.com\/blog\/2026\/03\/version-control-that-holds-up-in-due-diligence-10-naming-and-versioning-rules-partners-can-enforce\">versioning protocol<\/a>.<\/li>\n\n\n\n<li>Enforce single check-out and check-in.<\/li>\n\n\n\n<li>Block parallel uploads to the same filename.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading py-4\">Email-based Q&amp;A creep<\/h3>\n\n\n\n<p>Once questions start leaking into email, the control framework weakens fast.<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Keep all Q&amp;A inside the VDR.<\/li>\n\n\n\n<li>Use 4-hour and 24-hour timers.<\/li>\n\n\n\n<li>Publish a governance note at kickoff.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading py-4\">Audit trail gaps<\/h3>\n\n\n\n<p>Manual exports create inconsistency between live and archived workspaces.<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Automate weekly exports.<\/li>\n\n\n\n<li>Store exports on write-once media.<\/li>\n\n\n\n<li>Test restores quarterly.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading py-4\">Cross-deal contamination<\/h3>\n\n\n\n<p>This is the most dangerous failure in&nbsp;<strong>concurrent deals<\/strong>. A document or session from one mandate lands in another.<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Keep workspaces isolated.<\/li>\n\n\n\n<li>Avoid shared indexes.<\/li>\n\n\n\n<li>Separate audit logs per workspace.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading py-4\">Schedule slippage<\/h3>\n\n\n\n<p>A 2-week delay in filing can push you outside the observation window.<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Use the deal-clock dashboard.<\/li>\n\n\n\n<li>Surface counterparty deadlines early.<\/li>\n\n\n\n<li>Keep buffer in the schedule.<\/li>\n<\/ul>\n\n\n\n<h2 class=\"wp-block-heading py-4\">Why this framework is better than a basic VDR setup<\/h2>\n\n\n\n<p>The point is not just security. It is speed with control.<\/p>\n\n\n\n<p class=\"py-4\">A single-deal setup can hold one transaction together. But once you are running 3 to 5 live mandates, the real need is&nbsp;<strong>multi-deal orchestration<\/strong>: isolated workspaces, consistent permissions, auditable activity, structured Q&amp;A, and timeline visibility across the portfolio. That is what lets a mid-sized merchant banker protect compliance without adding headcount linearly.<\/p>\n\n\n\n<p>It also has a cost angle. Indian buyers already feel the pressure of global VDR pricing, especially when fees are being pushed back by smaller IPO clients. A controlled, fixed-price setup matters because it protects margins while still supporting the audit trail and security posture the market now expects.<\/p>\n\n\n\n<h2 class=\"wp-block-heading py-4\">Summary and next steps<\/h2>\n\n\n\n<p>If you are managing IPO and M&amp;A mandates in parallel, do not try to force a single-project mindset onto a portfolio problem. Build for isolation, traceability, and shared visibility from the start.<\/p>\n\n\n\n<p class=\"py-4\">The high-priority move is simple: set up one workspace per mandate, wire in the Schedule VI spine, enforce role-based access, and make audit logs and Q&amp;A part of the daily operating rhythm. That is the core of&nbsp;<strong>pipeline management<\/strong>&nbsp;in a regulated deal environment.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">FAQ<\/h2>\n\n\n\n<h3 class=\"wp-block-heading py-4\">What is a concurrent deal framework in a VDR context?<\/h3>\n\n\n\n<p>It is a way of running multiple live mandates in separate, controlled workspaces so documents, permissions, Q&amp;A, and audit trails do not overlap.<\/p>\n\n\n\n<h3 class=\"wp-block-heading py-4\">How does the Repository of Documents change merchant banker operations?<\/h3>\n\n\n\n<p>It makes document traceability a standing requirement. You now need preserved records of the materials relied on during diligence, not just a finished data room.<\/p>\n\n\n\n<h3 class=\"wp-block-heading py-4\">How can I run 3 to 5 IPO or M&amp;A deals without leakage?<\/h3>\n\n\n\n<p>Use separate workspaces, role-based permissions, isolated audit logs, and per-deal Q&amp;A hubs. Do not share folder structures or indexes across mandates.<\/p>\n\n\n\n<h3 class=\"wp-block-heading py-4\">What VDR features matter most for parallel workflows?<\/h3>\n\n\n\n<p>The priorities are isolated workspaces, granular permissions, audit trails, dynamic watermarking, centralized Q&amp;A, and searchable document intelligence.<\/p>\n\n\n\n<h3 class=\"wp-block-heading py-4\">How does wall-crossing relate to VDR audit logs?<\/h3>\n\n\n\n<p>Wall-crossing creates a compliance event. The VDR log should show who accessed what, when, and under which permissions, so the UPSI trail is defensible.<\/p>\n\n\n\n<h3 class=\"wp-block-heading py-4\">How long should it take to stand up a compliant data room?<\/h3>\n\n\n\n<p>The dossier points to a mandate-win-to-DRHP window of under 4.5 months as the pressure point. The key is to start with structure, not manual cleanup.<\/p>\n\n\n\n<h3 class=\"wp-block-heading py-4\">What causes the most delay in due diligence?<\/h3>\n\n\n\n<p>Email-based document chasing is still one of the biggest causes of slippage. A centralized Q&amp;A process compresses that delay.<\/p>\n\n\n\n<h3 class=\"wp-block-heading py-4\">How should a merchant banker think about cost?<\/h3>\n\n\n\n<p>Not as a one-off software fee, but as part of deal economics. The goal is to protect margin while keeping compliance and control intact.<\/p>\n\n\n\n<h2 class=\"wp-block-heading py-4\">Need a VDR that can keep up with parallel deal execution?<\/h2>\n\n\n\n<p>If your team is juggling multiple IPO and M&amp;A mandates, you need more than storage. You need a platform that supports security, auditability, and faster collaboration without making your operating model heavier.<\/p>\n\n\n\n<p class=\"py-4\">DCirrus VDR is built for exactly that kind of workload, with role-based access, dynamic watermarking, AI-assisted document intelligence, centralized Q&amp;A, and audit trails that support SEBI-ready document handling across active deals.<\/p>\n\n\n\n<p><a href=\"https:\/\/www.dcirrus.com\/request-a-demo\/\">Book a free demo<\/a><\/p>\n\n\n\n<p><\/p>\n","protected":false},"excerpt":{"rendered":"<p>When you are running&nbsp;concurrent deals, the real failure mode is not lack of effort. It is cross-contamination: the wrong draft, the wrong counterparty, the wrong watermark, or the wrong Q&amp;A thread slipping into the wrong mandate. In a market where one team may be handling two DRHPs, a QIP, and an open offer at once, [&hellip;]<\/p>\n","protected":false},"author":1,"featured_media":1533,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[1],"tags":[],"class_list":["post-1532","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-technology"],"_links":{"self":[{"href":"https:\/\/www.dcirrus.com\/blog\/wp-json\/wp\/v2\/posts\/1532","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.dcirrus.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.dcirrus.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.dcirrus.com\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.dcirrus.com\/blog\/wp-json\/wp\/v2\/comments?post=1532"}],"version-history":[{"count":3,"href":"https:\/\/www.dcirrus.com\/blog\/wp-json\/wp\/v2\/posts\/1532\/revisions"}],"predecessor-version":[{"id":1539,"href":"https:\/\/www.dcirrus.com\/blog\/wp-json\/wp\/v2\/posts\/1532\/revisions\/1539"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.dcirrus.com\/blog\/wp-json\/wp\/v2\/media\/1533"}],"wp:attachment":[{"href":"https:\/\/www.dcirrus.com\/blog\/wp-json\/wp\/v2\/media?parent=1532"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.dcirrus.com\/blog\/wp-json\/wp\/v2\/categories?post=1532"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.dcirrus.com\/blog\/wp-json\/wp\/v2\/tags?post=1532"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}