Textile Exchange’s Post

Documenting agreements: Creating documents that clarify the agreed-upon details, such as duration, cost, deliverables, and responsibilities, to maintain clarity in the relationship and avoid conflicts. #Agreements #Documentation #Clarity

When there is no clear documentation of the processes, the consistency goes down. Every time the process is executed, there will be differences in the end results. https://cady.ly/0445t

SOP (STAGGERED ORDER PROTOCOL) (Live Placement(s) and/or Adjustment(s)): #PRQ aka $PRQ [1] Sell Limit Price = 0.1748 (1.00x DCAP) Variable collaborations/instructions: https://lnkd.in/gfKzkhca

We just launched our latest feature, Question Sets by Hevi! Question Sets give you a detailed document review instantly! When reviewing contracts, or tender documents are you always searching for the same things? Simply create a CSV with up to 300 questions that you want to ask, and upload that into Hevi alongside the documents. In a matter of minutes, you’ll have a full detailed analysis, that is easily exported and ready to go. Don’t spend days or weeks trawling through documents, or waiting for other teams review notes. Check out the video below and get in touch to learn more today!

Unlock the potential of your operations with our Procedural Documentation Service! We create, review, standardize, and continuously improve procedures to ensure peak efficiency for your organization. For more information, you can email info@iviwe-kuhle.com. #businessefficiency #documentation #proudlysouthafricanbusiness #gqeberhabusiness #IVIWEKUHLECONSULTING #whereadministrationmeetsefficiency

Do you know the consequence of a poorly written Scope? A bucket load of compensation events and a stressed 𝘗𝘳𝘰𝘫𝘦𝘤𝘵 𝘔𝘢𝘯𝘢𝘨𝘦𝘳 constantly changing the Scope to align with 𝘊𝘭𝘪𝘦𝘯𝘵 requirements (and dealing with the CE process). Spend the time getting the Scope right.

Time is slipping away. Thorny issues when persuading a successful outcome in #EOT request: when determining delays, an analysis #technique needs to be selected, unless already provided for under the contract. Many standard forms of contract such as #JCT, #NEC and #FIDIC provide mechanisms for EOT requests. None of these, however, specifically address a technique to be implemented when determining delay. Although the wording of these contracts seems to, in principle, encourage EOT evaluations through estimations/forecasts (eg JCT and NEC), in practice, there might be instances where the events/effects ceased and works were completed before an EOT is granted. In this last scenario, a CA, court, or tribunal, will benefit from having knowledge of the actual events/facts that have occurred in the case. Either way, while the lack of specific delay technique may lead to uncertainty, the following may be considered before proceeding with the most suitable method for your case. • No judge is entitled to require a party to establish causation and loss by a specific method (𝘎𝘔𝘛𝘊 𝘷 𝘠𝘶𝘢𝘴𝘢) • A ‘retrospective and dissectional reconstruction’ of the events is what a case may require (𝘔𝘤𝘈𝘭𝘱𝘪𝘯𝘦 𝘷 𝘔𝘤𝘋𝘦𝘳𝘮𝘰𝘵𝘵) • Delays should be on the critical path (𝘏𝘦𝘯𝘳𝘺 𝘉𝘰𝘰𝘵 𝘷 𝘔𝘢𝘭𝘮𝘢𝘪𝘴𝘰𝘯) • It would be incorrect to disregard the impact of 'other events' (ibid) • It is important to establish a valid critical path both initially and at a subsequent significant point (𝘉𝘢𝘭𝘧𝘰𝘶𝘳 𝘉𝘦𝘢𝘵𝘵𝘺 𝘷 𝘓𝘰𝘯𝘥𝘰𝘯 𝘉𝘰𝘳𝘰𝘶𝘨𝘩) • Analysis should also be conducted for the period after the delay event to determine whether the delays were mitigated, neutralized, exacerbated (𝘊𝘰𝘴𝘵𝘢𝘪𝘯 𝘓𝘵𝘥 𝘷 𝘊𝘩𝘢𝘳𝘭𝘦𝘴) • Adjustments should be made to ensure consistency with the facts (𝘚𝘬𝘢𝘯𝘴𝘬𝘢 𝘷 𝘌𝘨𝘨𝘦𝘳). • The course of the project should be reviewed month by month (𝘔𝘪𝘳𝘢𝘯𝘵 𝘈𝘴𝘪𝘢-𝘗𝘢𝘤𝘪𝘧𝘪𝘤 𝘊𝘰𝘯𝘴𝘵𝘳𝘶𝘤𝘵𝘪𝘰𝘯 𝘷 𝘖𝘷𝘦 𝘈𝘳𝘶𝘱) • Whether or not an event actually causes delay is a matter that should be resolved based on principles of common sense (𝘊𝘪𝘵𝘺 𝘐𝘯𝘯 𝘷 𝘚𝘩𝘦𝘱𝘩𝘦𝘳𝘥). • SCL Protocol endorses 6 common methods • It would be incorrect to assume that a party cannot deviate from the method mentioned in the SCL Protocol or another accepted technique (𝘛𝘩𝘰𝘮𝘢𝘴 𝘉𝘢𝘳𝘯𝘦𝘴 𝘷 𝘉𝘭𝘢𝘤𝘬𝘣𝘶𝘳𝘯) • Courts and tribunals, might not be bound to any particular delay analysis technique or be bound to deal only with what put forward by the parties (𝘓𝘰𝘯𝘥𝘰𝘯 𝘜𝘯𝘥𝘦𝘳𝘨𝘳𝘰𝘶𝘯𝘥 𝘷 𝘊𝘪𝘵𝘺𝘭𝘪𝘯𝘬) 𝗪𝗵𝗮𝘁 𝗶𝘀 𝗺𝗼𝗿𝗲? Do no 'wait and see' the impacts of delay events Keep contemporary records  Update the programme Float and link, don't forget 😉 You may not impress with the complexity of the report and don't forget to deal with ‘concurrency’. This, likewise the above, might deserve specific guidance though. 𝗔𝗻𝘆𝘁𝗵𝗶𝗻𝗴 𝗳𝘂𝗿𝘁𝗵𝗲𝗿? #contractmanagement #construction

Bid and proposal professionals often face the daunting challenge of delivering high-quality proposals on schedule. Incomplete capture documents, resource shortages, and tight schedules can easily undermine the best efforts. So, how can you verify that your proposal meets the highest level of quality under these challenging conditions? Here are strategies to help you overcome these common obstacles and deliver winning proposals: https://lnkd.in/e98h_Fdu #HighQuality #Quality #ProposalQuality #ProposalManagement #ProproposalWriting #ProposalEditing #QualtyControl #LohfeldConsulting

Addendum: Is it that important? What do you do if you want to make some changes to the contract that has been signed and ready. You have two options: 1. You bin the signed contract and make a new one with changes you have agreed to with the other parties to the contract and get them signed again. 2. Or you make an additional document just featuring the changes agreed to and add that signed document to the contract. Which of the two routes would you choose? I will definitely choose the second one. Now you see, this new document is part of the contract and it is way less time consuming and has the same standing as the contract. This new document is called an addendum.

To prepare an effective claim submission, follow these refined principles: 1. User-Friendly: Structure the document for easy reading and navigation. Use clear language, logical organization, and proper referencing to facilitate the reviewer’s understanding. 2. Self-Contained: Make the claim comprehensive, including all relevant data and background information. This allows the reviewer to understand the claim fully without needing external resources. 3. Comprehensive and Clear: Present the claim in a way that assumes the reviewer has no prior knowledge of the project. Provide thorough explanations and contextual information to ensure clarity. 4. Relevant and Focused: Avoid unnecessary or irrelevant information. Keep the content concise and to the point, highlighting only what directly supports the claim. By following these principles, you’ll create a claim submission that is clear, thorough, and easily accessible to the reviewer.