diff --git a/TallyFlow/Integration/ServiceNow/ServiceNow Integration Approach.md b/TallyFlow/Integration/ServiceNow/ServiceNow Integration Approach.md
new file mode 100644
index 0000000..09c5f64
--- /dev/null
+++ b/TallyFlow/Integration/ServiceNow/ServiceNow Integration Approach.md	
@@ -0,0 +1,70 @@
+# ServiceNow Integration Approach
+
+**Status:** Recommended Pattern  
+**Date:** 2026-07-07
+
+## Overview
+
+TallyFlow should integrate with ServiceNow through **TallyFlow Core** rather than directly from TallyFlow Assets (Mobile) or other components. Core acts as the integration hub and single source of truth for field operations data.
+
+## Recommended Architecture
+
+```mermaid
+flowchart LR
+    A[TallyFlow Assets Mobile] -->|REST / WebSocket| B[TallyFlow Core]
+    C[TallyFlow Print] -->|REST| B
+    D[TallyFlow Capture] -->|REST| B
+    E[TallyFlow IoT] -->|REST / MQTT| B
+    B -->|REST / Integration Hub| F[ServiceNow]
+    F -->|REST| B
+```
+
+**Core Principle:** All external systems, including ServiceNow, connect to TallyFlow Core.
+
+## Data Flow Directions
+
+| Direction                  | Typical Data                          | Trigger                          | Recommended Method                  |
+|---------------------------|---------------------------------------|----------------------------------|-------------------------------------|
+| **ServiceNow → TallyFlow** | Asset master data, locations, status  | Scheduled or event-driven        | ServiceNow Integration Hub → Core REST |
+| **TallyFlow → ServiceNow** | Real-time location, RFID scans, condition updates | Mobile scan, IoT event, zone change | Core → ServiceNow REST / Flow Designer |
+| **Bidirectional**          | Asset status synchronization          | On change or scheduled           | Core as middleware                  |
+
+## Key Integration Points
+
+### 1. Asset Master Data
+- ServiceNow remains the system of record for asset metadata.
+- TallyFlow Core receives updates (new assets, location changes, status).
+- TallyFlow enriches ServiceNow records with RFID tag data, real-time location, and movement history.
+
+### 2. Field Operations Data
+- TallyFlow Assets (Mobile) captures RFID scans, photos, zone movements, and condition data.
+- This data is pushed to ServiceNow for visibility in Asset Management, Work Orders, or CMDB.
+
+### 3. Real-time Location & Condition
+- IoT and mobile events flow through Core and are published to ServiceNow (via REST or Integration Hub).
+
+## Authentication & Security
+
+- Use **OAuth 2.0** or **ServiceNow Integration Hub** credentials from Core.
+- Core should manage token refresh and retry logic.
+- Avoid embedding ServiceNow credentials in the mobile app.
+
+## Benefits of Routing Through Core
+
+- Maintains TallyFlow’s offline-first capabilities.
+- Ensures consistent data model and audit trail.
+- Simplifies future integrations (ERP, WMS, etc.).
+- Allows TallyFlow to act as a specialized asset tracking layer on top of ServiceNow.
+
+## Next Steps (Typical Engagement)
+
+1. Define asset data model mapping between ServiceNow and TallyFlow.
+2. Identify events that should trigger synchronization.
+3. Build or configure a lightweight connector in TallyFlow Core.
+4. Use ServiceNow Integration Hub or REST Message for the ServiceNow side.
+5. Test bidirectional sync and conflict resolution rules.
+
+---
+
+**Owner:** TallyFlow Product Team  
+**Related Documents:** [[TallyFlow Architecture]]
\ No newline at end of file