diff --git a/liaisons.md b/liaisons.md
index e9244daf..cc4a08f2 100644
--- a/liaisons.md
+++ b/liaisons.md
@@ -1,3 +1,89 @@
 ## Liaisons to the W3C WoT Community Group
 
-To be decided
+The liaisons of the W3C WoT CG are not explicitly outlined in the CG charter; however, they are documented in this document. 
+This markdown document details each liaison and explains the extent of its scope.
+
+Current liaisons:
+
+- [Web of Things Interest and Working Group](#web-of-things-interest-and-working-group)
+
+> [!NOTE] 
+> The key words MAY, MUST, MUST NOT, RECOMMENDED, SHOULD, and SHOULD NOT in this document are to be interpreted as described in [BCP 14](https://www.rfc-editor.org/info/bcp14) [RFC2119](https://www.rfc-editor.org/rfc/rfc2119) [RFC8174](https://www.rfc-editor.org/rfc/rfc8174) when, and only when, they appear in all capitals, as shown here. 
+
+### Web of Things Interest and Working Group
+
+> [!NOTE] 
+> This is only a draft until a resolution is reached in both WG/IG and CG. These will be documented via email.
+> The CG Charter MAY need changes to satisfy the liaison. Agreeing on this document implies agreeing on the corresponding CG Charter changes.
+
+> The content below, until the horizontal line, is composed by the CG based on inputs from the TPAC Joint Meeting, CG Internal Meeting, and Office Hours inputs. Please refer to [Original Input](#original-input) for the discussion results form W3C TPAC 2023.
+
+The WoT IG/WG liaison is categorized based on the nature of collaboration. 
+The categories below explain the scope of collaboration.
+
+Note: WG/IG collectively refers to both WoT Interest and Working Group, while CG pertains to the WoT CG.
+
+#### Documents
+
+If the CG intends to produce a document, it MUST adhere to the [W3C CLA](https://www.w3.org/community/about/process/cla/).
+This mandates that the CG participants don't directly edit or open Pull Requests to change WG/IG documents.
+Relevant WG/IG documents MAY incorporate content from CG reports following Section 9 of the [W3C CLA](https://www.w3.org/community/about/process/cla/).
+Any CG document related to a WG/IG document type (e.g. use cases, bindings), MUST comply with the format and content requirements established by the WG/IG. 
+Deviating from these requirements requires explicit authorization from the WG/IG.
+CG reports, as explained by the CG charter, MAY take the form of Markdown, HTML, or similar formats 
+
+Examples of document types pertinent to WG/IG, eligible as CG reports:
+
+- Use cases
+- Requirements
+- Feature Proposals
+- Bindings
+
+#### Role of WoT CG
+
+The role of the CG in this collaboration is categorized into two: facilitating a low entry barrier and engaging in outreach.
+
+##### Ensuring a Low Entry for WoT Involvement
+
+Considering the existence of membership fees for WG/IG participation, fostering more participants to exchange ideas on WoT-related topics becomes relevant.
+
+CG participants CAN actively and openly exchange ideas on WoT-related topics within the CG, collaborate on non-normative CG reports, and experiment with the implementations of the WG/IG reports.
+
+##### Outreach
+
+The CG utilizes various channels under the CG administration to reach a broad audience interested in WoT, aligning with the low-entry barrier principle.
+
+#### Events
+
+The WG/IG collaborates on Plugfest events with the CG, thereby leveraging the community to garner a wider audience. 
+WG/IG MAY also engage in collaboration with other CGs and liaisons. 
+Joint meetings, such as Face to Face (F2F) and TPAC meetings, may be convened between WG/IG and the CG.
+
+#### Test Cases
+
+CG participants are permitted to contribute to the testing activity of the WG/IG Task Forces. 
+Contributions MUST adhere to WG requirements regarding quality, folder structure, file naming conventions, and other specifications.
+The CG participants MUST contribute test cases to the CG GitHub repository.
+
+---
+
+#### Original Input
+
+The part below is written together with IG/WG in the TPAC 2023 Joint Meeting.
+
+Collaboration on the following topics:
+
+- Bindings
+- Use Cases
+- Requirements
+- Feedback on Draft Specifications
+- Outreach of WG Activities
+- Joint Activities such as Plugfests
+- Contribution to WG test cases from CG Participants
+- Feature Proposals
+
+Further clarifications on the following points are being worked on:
+
+- How the collaboration will work, what is the process
+- Detailing what those topics mean
+- Roles of the CG and WG participants per point/topic