{"id":73,"date":"2026-07-09T10:22:07","date_gmt":"2026-07-09T10:22:07","guid":{"rendered":"https:\/\/my.construwx.in\/resources\/?p=73"},"modified":"2026-07-09T10:22:09","modified_gmt":"2026-07-09T10:22:09","slug":"how-better-collaboration-prevents-disputes-in-construction-projects","status":"publish","type":"post","link":"https:\/\/my.construwx.in\/resources\/how-better-collaboration-prevents-disputes-in-construction-projects\/","title":{"rendered":"How Better Collaboration Prevents Disputes in Construction Projects"},"content":{"rendered":"\n<p class=\"wp-block-paragraph\">Construction disputes rarely start with one dramatic argument. Most of them grow quietly.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">A consultant takes too long to answer an RFI. The contractor continues work based on an old drawing. A subcontractor does not receive access on time. The QS and site team disagree on what got completed. A planner reports delay, but the commercial team does not see the cost impact. The client wants faster progress, but approvals still sit pending.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Everyone thinks their part of the story is clear. Then the project reaches a difficult point, and the same people realise they do not share the same version of what happened.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">That is where disputes begin.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Better collaboration does not mean everyone agrees all the time. It means the project team creates a working system where issues surface early, decisions move through the right people, records stay clear, and disagreements do not grow in silence.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Construction partnering has existed for decades with the aim of improving communication, setting shared project goals, reducing claims, and creating a dispute resolution ladder before conflict turns serious. The Construction Industry Institute also lists Partnering and Disputes Prevention &amp; Resolution among its recognised construction best-practice areas.&nbsp;<\/p>\n\n\n\n<h2 class=\"wp-block-heading\"><strong>Collaboration is not the same as being polite<\/strong><\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Construction teams often confuse collaboration with friendliness. A polite meeting can still hide a broken project.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Good collaboration has structure. It creates a clear rhythm for how people share information, make decisions, raise risks, solve clashes, and escalate issues. It also gives each party a way to protect its position without turning every disagreement into a fight.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">A project team can speak politely and still fail if:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>RFIs sit unanswered for weeks<\/li>\n\n\n\n<li>design changes do not reach site teams<\/li>\n\n\n\n<li>subcontractors do not join planning meetings<\/li>\n\n\n\n<li>payment issues stay hidden until the bill cycle<\/li>\n\n\n\n<li>planners and QS teams do not compare delay and cost impact<\/li>\n\n\n\n<li>meeting minutes record vague comments instead of decisions<\/li>\n\n\n\n<li>site teams depend on calls and chat messages for critical instructions<\/li>\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\">A collaborative project does not avoid hard conversations. It brings them forward before they become expensive.<\/p>\n\n\n\n<figure class=\"wp-block-image size-large\"><img loading=\"lazy\" decoding=\"async\" width=\"1024\" height=\"768\" src=\"https:\/\/s3.ap-south-2.amazonaws.com\/trikona.prod.media\/wp-content\/uploads\/sites\/6\/2026\/07\/09101843\/Collaboration-vs-Politeness-1024x768.webp\" alt=\"\" class=\"wp-image-74\" srcset=\"https:\/\/s3.ap-south-2.amazonaws.com\/trikona.prod.media\/wp-content\/uploads\/sites\/6\/2026\/07\/09101843\/Collaboration-vs-Politeness-1024x768.webp 1024w, https:\/\/s3.ap-south-2.amazonaws.com\/trikona.prod.media\/wp-content\/uploads\/sites\/6\/2026\/07\/09101843\/Collaboration-vs-Politeness-300x225.webp 300w, https:\/\/s3.ap-south-2.amazonaws.com\/trikona.prod.media\/wp-content\/uploads\/sites\/6\/2026\/07\/09101843\/Collaboration-vs-Politeness-768x576.webp 768w, https:\/\/s3.ap-south-2.amazonaws.com\/trikona.prod.media\/wp-content\/uploads\/sites\/6\/2026\/07\/09101843\/Collaboration-vs-Politeness.webp 1448w\" sizes=\"auto, (max-width: 1024px) 100vw, 1024px\" \/><\/figure>\n\n\n\n<h2 class=\"wp-block-heading\"><strong>The biggest dispute trigger: teams working from different versions of reality<\/strong><\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Many construction disputes come from a simple problem: each team sees a different project.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">The site team sees access problems, labour issues, and daily pressure. The design team sees technical comments, revision control, and approval cycles. The planner sees progress slippage. The QS sees quantities and payment risk. The contractor sees cost exposure. The client sees missed dates and budget pressure.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">All of these views may contain truth. The dispute starts when the project never brings them together.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">For example, a slab activity slips by five days. The site team says it happened because the consultant delayed approval. The consultant says the contractor submitted incomplete details. The subcontractor says the area never had proper access. The planner says the activity affected the critical path. The client says no one warned them early enough.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Now the project has five stories.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Collaboration aims to reduce that gap. It creates one shared space where issues, owners, dates, effects, and next actions stay visible.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">This does not need a complicated system. A strong weekly control meeting can do more than ten unfocused meetings if it tracks the right things:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>open RFIs<\/li>\n\n\n\n<li>delayed approvals<\/li>\n\n\n\n<li>upcoming access constraints<\/li>\n\n\n\n<li>design changes<\/li>\n\n\n\n<li>procurement risks<\/li>\n\n\n\n<li>payment blockers<\/li>\n\n\n\n<li>quality concerns<\/li>\n\n\n\n<li>variation status<\/li>\n\n\n\n<li>upcoming critical activities<\/li>\n\n\n\n<li>decisions needed from each party<\/li>\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\">The point is not to talk more. The point is to make the right problems visible.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\"><strong>Early warnings matter more than late blame<\/strong><\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">The best time to discuss a problem is before it damages the project.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">NEC contracts place strong emphasis on early warning and mutual trust and cooperation. NEC4 changed the earlier \u201cRisk Register\u201d language to \u201cEarly Warning Register,\u201d which shows the project management intent behind the contract: teams should identify issues before they fully hit time, cost, or performance.&nbsp;<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Even outside NEC contracts, the principle helps. Every project needs a way to say:<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">\u201cThis may affect us soon.\u201d<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">That sentence can save weeks of argument.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">An early warning does not need to accuse anyone. It can simply record that a future issue may affect cost, time, quality, safety, or access. For example:<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">\u201cBasement waterproofing approval remains pending. If approval does not arrive by Friday, blockwork in Zone B may shift by four days.\u201d<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">That kind of warning helps the client, consultant, contractor, planner, QS, and site team act earlier. It also creates a calmer tone because the issue reaches the table before people feel cornered.<\/p>\n\n\n\n<figure class=\"wp-block-image size-large\"><img loading=\"lazy\" decoding=\"async\" width=\"1024\" height=\"768\" src=\"https:\/\/s3.ap-south-2.amazonaws.com\/trikona.prod.media\/wp-content\/uploads\/sites\/6\/2026\/07\/09101846\/Early-Warning-Flow-1024x768.webp\" alt=\"\" class=\"wp-image-75\" srcset=\"https:\/\/s3.ap-south-2.amazonaws.com\/trikona.prod.media\/wp-content\/uploads\/sites\/6\/2026\/07\/09101846\/Early-Warning-Flow-1024x768.webp 1024w, https:\/\/s3.ap-south-2.amazonaws.com\/trikona.prod.media\/wp-content\/uploads\/sites\/6\/2026\/07\/09101846\/Early-Warning-Flow-300x225.webp 300w, https:\/\/s3.ap-south-2.amazonaws.com\/trikona.prod.media\/wp-content\/uploads\/sites\/6\/2026\/07\/09101846\/Early-Warning-Flow-768x576.webp 768w, https:\/\/s3.ap-south-2.amazonaws.com\/trikona.prod.media\/wp-content\/uploads\/sites\/6\/2026\/07\/09101846\/Early-Warning-Flow.webp 1448w\" sizes=\"auto, (max-width: 1024px) 100vw, 1024px\" \/><\/figure>\n\n\n\n<h2 class=\"wp-block-heading\"><strong>Design coordination can stop disputes before site work begins<\/strong><\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Design issues create many construction conflicts. A drawing mismatch may look small during design review, but it can become rework, delay, variation, or blame once work reaches site.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Better collaboration starts before execution. The contractor, consultant, design team, MEP team, QS, planner, and key subcontractors should review buildability and coordination early, especially on complex projects.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Design-build routes often bring teams together earlier because one party handles both design and construction. Design-build can reduce the split between designer and contractor by creating one point of responsibility and allowing teams to overlap design and construction work.&nbsp;<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">That does not mean design-build removes all disputes. It means the delivery route can support earlier coordination when teams use it properly.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">On any route, the project team should treat design coordination as a dispute prevention tool. Before work starts, the team should ask:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Do drawings from all disciplines match?<\/li>\n\n\n\n<li>Do architectural, structural, and MEP drawings clash?<\/li>\n\n\n\n<li>Do specifications match BOQ descriptions?<\/li>\n\n\n\n<li>Did the team close RFIs before procurement?<\/li>\n\n\n\n<li>Did subcontractors review the areas that affect their work?<\/li>\n\n\n\n<li>Did the planner reflect approval and design dependencies?<\/li>\n\n\n\n<li>Did the QS capture possible scope changes?<\/li>\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\">This work may feel slow at the start. It costs less than fixing the same issue on site.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\"><strong>Collaboration must include commercial people early<\/strong><\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Many projects bring the QS, billing team, or contracts team into discussions only after execution creates a cost issue. That timing creates disputes.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Commercial input should not arrive after the story ends. It should sit inside the project conversation from the start.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">When a site instruction changes work, the QS needs to know early. When an approval delay affects sequence, the planner and contracts team need to know early. When the client asks for acceleration, the commercial team needs to check whether that creates extra cost. When a subcontractor faces access delay, the project team should understand time and payment impact before it becomes a formal claim.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">A project that separates site, planning, and commercial teams creates avoidable conflict.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">A collaborative rhythm can fix this:<\/p>\n\n\n\n<figure class=\"wp-block-table\"><table class=\"has-fixed-layout\"><tbody><tr><td><strong>Project issue<\/strong><\/td><td><strong>Who should join early<\/strong><\/td><\/tr><tr><td>Drawing change<\/td><td>Site engineer, consultant, QS, planner, contracts team<\/td><\/tr><tr><td>Access delay<\/td><td>Site team, subcontractor, planner, project manager<\/td><\/tr><tr><td>Extra work instruction<\/td><td>Site engineer, QS, contracts engineer, client\/consultant<\/td><\/tr><tr><td>Procurement delay<\/td><td>Procurement, planner, site team, project manager<\/td><\/tr><tr><td>Quality rejection<\/td><td>QA\/QC, site team, subcontractor, consultant<\/td><\/tr><tr><td>Payment blockage<\/td><td>QS, billing, project manager, client representative<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n<p class=\"wp-block-paragraph\">The main idea stays simple: the right people should see the issue while the project can still act.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\"><strong>Meetings should produce decisions, not noise<\/strong><\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Construction projects already have too many meetings. Collaboration does not mean adding more.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">A useful meeting should produce three things:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>decisions<\/li>\n\n\n\n<li>owners<\/li>\n\n\n\n<li>dates<\/li>\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\">If a meeting does not produce those, it becomes noise.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">A vague minute says:<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">\u201cTeam discussed pending approval.\u201d<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">A useful minute says:<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">\u201cConsultant to return approval comments on Block B fa\u00e7ade bracket detail by 18 June. Contractor to submit revised sketch by 16 June. Delay risk to remain open in the tracker until approval closes.\u201d<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">That kind of minute reduces argument later. It also helps the project manager follow up without relying on memory.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Every coordination meeting should keep one action tracker. The tracker should show issue, owner, due date, current status, and impact if delayed. The project team should close items only when the record shows proof, not when someone says, \u201cWe are checking.\u201d<\/p>\n\n\n\n<figure class=\"wp-block-image size-large\"><img loading=\"lazy\" decoding=\"async\" width=\"1024\" height=\"768\" src=\"https:\/\/s3.ap-south-2.amazonaws.com\/trikona.prod.media\/wp-content\/uploads\/sites\/6\/2026\/07\/09101847\/Meeting-Output-That-Prevents-Disputes-1024x768.webp\" alt=\"\" class=\"wp-image-76\" srcset=\"https:\/\/s3.ap-south-2.amazonaws.com\/trikona.prod.media\/wp-content\/uploads\/sites\/6\/2026\/07\/09101847\/Meeting-Output-That-Prevents-Disputes-1024x768.webp 1024w, https:\/\/s3.ap-south-2.amazonaws.com\/trikona.prod.media\/wp-content\/uploads\/sites\/6\/2026\/07\/09101847\/Meeting-Output-That-Prevents-Disputes-300x225.webp 300w, https:\/\/s3.ap-south-2.amazonaws.com\/trikona.prod.media\/wp-content\/uploads\/sites\/6\/2026\/07\/09101847\/Meeting-Output-That-Prevents-Disputes-768x576.webp 768w, https:\/\/s3.ap-south-2.amazonaws.com\/trikona.prod.media\/wp-content\/uploads\/sites\/6\/2026\/07\/09101847\/Meeting-Output-That-Prevents-Disputes.webp 1448w\" sizes=\"auto, (max-width: 1024px) 100vw, 1024px\" \/><\/figure>\n\n\n\n<h2 class=\"wp-block-heading\"><strong>Subcontractors need a place in the conversation<\/strong><\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Many disputes grow because subcontractors receive decisions late.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">A main contractor may attend design and client meetings, but the actual work depends on subcontractors. If the fa\u00e7ade subcontractor, MEP subcontractor, finishing contractor, or specialist vendor does not get the right information on time, the project still suffers.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">A strong collaboration process includes the people who carry the work.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Subcontractors should join discussions when their work affects:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>design coordination<\/li>\n\n\n\n<li>access planning<\/li>\n\n\n\n<li>material lead times<\/li>\n\n\n\n<li>method statements<\/li>\n\n\n\n<li>inspection timing<\/li>\n\n\n\n<li>sequence changes<\/li>\n\n\n\n<li>interface risks<\/li>\n\n\n\n<li>handover dates<\/li>\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\">This does not mean every subcontractor joins every meeting. It means the project brings the right package owner into the right conversation before the decision becomes late.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">A planner can build a look-ahead schedule, but the schedule becomes stronger when subcontractors confirm manpower, access, materials, and method constraints. A QS can prepare payment forecasts, but the forecast becomes stronger when subcontractor progress and measurement records stay current.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Collaboration works best when it reaches the workface.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\"><strong>Digital tools help only when teams trust the process<\/strong><\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Shared platforms, dashboards, common data environments, and digital trackers can improve collaboration. ISO 44001 also gives a wider management framework for collaborative business relationships, which shows that collaboration requires leadership, planning, support, operations, performance review, and improvement, not just goodwill.&nbsp;<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">But tools cannot fix a team that refuses to act.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">A dashboard may show 18 overdue RFIs. Someone still needs to decide who will close them. A shared tracker may show five delayed approvals. Someone still needs to escalate them. A document platform may show the latest drawing. Site teams still need to stop using old printouts.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Digital collaboration needs discipline:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>one source of current drawings<\/li>\n\n\n\n<li>one RFI tracker<\/li>\n\n\n\n<li>one approval tracker<\/li>\n\n\n\n<li>one action log<\/li>\n\n\n\n<li>one variation register<\/li>\n\n\n\n<li>one look-ahead planning rhythm<\/li>\n\n\n\n<li>one agreed escalation route<\/li>\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\">When teams use these systems honestly, disputes reduce because fewer issues disappear into memory.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\"><strong>A dispute resolution ladder should exist before trouble starts<\/strong><\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">A dispute resolution ladder gives people a step-by-step way to handle disagreements. The project team should not design this process during a crisis.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">A simple ladder may look like this:<\/p>\n\n\n\n<ol class=\"wp-block-list\">\n<li>Site-level discussion between engineers<\/li>\n\n\n\n<li>Package-level discussion with subcontractor or consultant<\/li>\n\n\n\n<li>Project manager review<\/li>\n\n\n\n<li>Commercial and contracts review<\/li>\n\n\n\n<li>Senior management meeting<\/li>\n\n\n\n<li>Formal dispute route under the contract<\/li>\n<\/ol>\n\n\n\n<p class=\"wp-block-paragraph\">This helps because most issues do not need to jump straight into formal conflict. The team gets a chance to solve the issue at the right level first.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Partnering approaches often include agreed dispute resolution steps so teams can deal with conflict early and avoid litigation where possible.&nbsp;<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">The ladder should not block contractual notices. It should work beside them. A contractor may still need to send a notice to protect rights while the team discusses the issue commercially. Good collaboration does not mean giving up protection. It means managing protection without damaging the working relationship.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\"><strong>Final takeaway<\/strong><\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Better collaboration prevents disputes because it gives the project fewer places to hide problems. It brings risks forward, connects site and commercial teams, includes subcontractors at the right time, clarifies decisions, and gives everyone a shared view of progress, cost, design, approvals, and responsibility.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Construction projects do not need more polite meetings. They need clearer working habits. They need early warnings, decision logs, issue owners, clean trackers, commercial input, design coordination, and a dispute ladder that starts before conflict grows.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">For learners who want to grow into site management, planning, QS, contracts, procurement, project controls, or project management,<a href=\"https:\/\/constructionlearning.online\/\" target=\"_blank\" rel=\"noreferrer noopener\">Construction Learning<\/a> can help build the role-based skills behind better collaboration. Strong construction professionals do not only know their own task. They understand how their decisions affect the whole project team.<\/p>\n\n\n\n<hr class=\"wp-block-separator has-alpha-channel-opacity\" \/>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>References<\/strong><\/p>\n\n\n\n<ol class=\"wp-block-list\">\n<li>Construction partnering overview<br><a href=\"https:\/\/en.wikipedia.org\/wiki\/Construction_partnering\" target=\"_blank\" rel=\"noreferrer noopener\">https:\/\/en.wikipedia.org\/wiki\/Construction_partnering<\/a><\/li>\n\n\n\n<li>Construction Industry Institute overview and best practices<br><a href=\"https:\/\/en.wikipedia.org\/wiki\/Construction_Industry_Institute\" target=\"_blank\" rel=\"noreferrer noopener\">https:\/\/en.wikipedia.org\/wiki\/Construction_Industry_Institute<\/a><\/li>\n\n\n\n<li>NEC contracts overview<br><a href=\"https:\/\/en.wikipedia.org\/wiki\/New_Engineering_Contract\" target=\"_blank\" rel=\"noreferrer noopener\">https:\/\/en.wikipedia.org\/wiki\/New_Engineering_Contract<\/a><\/li>\n\n\n\n<li>ISO 44001 collaborative business relationship management overview<br><a href=\"https:\/\/en.wikipedia.org\/wiki\/ISO_44001\" target=\"_blank\" rel=\"noreferrer noopener\">https:\/\/en.wikipedia.org\/wiki\/ISO_44001<\/a><\/li>\n\n\n\n<li>Design-build project delivery overview<br><a href=\"https:\/\/en.wikipedia.org\/wiki\/Design%E2%80%93build\" target=\"_blank\" rel=\"noreferrer noopener\">https:\/\/en.wikipedia.org\/wiki\/Design%E2%80%93build<\/a><\/li>\n<\/ol>\n\n\n\n<p class=\"wp-block-paragraph\"><\/p>\n","protected":false},"excerpt":{"rendered":"<p>Construction disputes rarely start with one dramatic argument. Most of them grow quietly.<\/p>\n","protected":false},"author":58,"featured_media":40,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[18],"tags":[],"class_list":["post-73","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-planning-project-controls"],"thumbnail":"https:\/\/s3.ap-south-2.amazonaws.com\/trikona.prod.media\/wp-content\/uploads\/sites\/6\/2026\/07\/09055324\/email-Procurement-Supply-Chain-365x245.webp","categories_names":["Planning &amp; Project Controls"],"tags_names":[],"blog_design":"design2","_links":{"self":[{"href":"https:\/\/my.construwx.in\/resources\/wp-json\/wp\/v2\/posts\/73","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/my.construwx.in\/resources\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/my.construwx.in\/resources\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/my.construwx.in\/resources\/wp-json\/wp\/v2\/users\/58"}],"replies":[{"embeddable":true,"href":"https:\/\/my.construwx.in\/resources\/wp-json\/wp\/v2\/comments?post=73"}],"version-history":[{"count":1,"href":"https:\/\/my.construwx.in\/resources\/wp-json\/wp\/v2\/posts\/73\/revisions"}],"predecessor-version":[{"id":77,"href":"https:\/\/my.construwx.in\/resources\/wp-json\/wp\/v2\/posts\/73\/revisions\/77"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/my.construwx.in\/resources\/wp-json\/wp\/v2\/media\/40"}],"wp:attachment":[{"href":"https:\/\/my.construwx.in\/resources\/wp-json\/wp\/v2\/media?parent=73"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/my.construwx.in\/resources\/wp-json\/wp\/v2\/categories?post=73"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/my.construwx.in\/resources\/wp-json\/wp\/v2\/tags?post=73"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}