Outdoor event lawn
Event Lawn
500max
MORNING BRIEFING · —
Good morning, Amrita.
Calendar
JUL 2026
S
M
T
W
T
F
S
Upcoming Events
VIEW ALL →
6:00 PMJul 21
Mehndi Hospitality
MEO Ready
9:00 AMJul 22
Haldi Brunch
MEO Ready
6:00 PMJul 22
Mehndi Dinner Buffet
Bar Package Mismatch
6:00 PMJul 23
Sangeet Dinner Buffet
Cocktail Pricing
8:00 PMJul 25
Reception Dinner
MEO Ready
Risk Feed
L1 · RULES
Kaur & Nanda
Guarantee window opens in 1 business day. Final headcount must be communicated 72 hours prior to function (Marriott terms); expected becomes guaranteed otherwise.
VIEW DATA →
L3 · LLM
Kaur & Nanda
Mehndi Dinner bar package shows Prestige Package on revised BEO — earlier negotiation locked Deluxe Host Bar on Consumption. $89 pp × 219 guests is a $19,491 swing. Escalate to Kim Houston.
VIEW DATA →
L3 · LLM
Kaur & Nanda
Sangeet specialty cocktails (Lucky Boy, Pyar Dosti Hai, Small Town Girl) listed at $20 each — but client expects them included in the $89 Prestige package. Confirm pricing model before printing menus.
VIEW DATA →
L2 · ML
Kaur & Nanda
Sangeet equipment gap: hotel CANNOT provide (2) Tall Stoves and (1) Portable Charcoal Grill. Caterer must source — historical pattern shows 40% of caterers miss this 7+ days out.
VIEW DATA →
PORTFOLIO
Programs
Sort by
WEDDING · MULTI-DAY
Kaur & Nanda Wedding
Managed by Amrita Jhaveri
STAGE
CONTRACTED
DATES
Jul 20–26, 2026
MINIMUM
$420,000
CORPORATE
Patel Corporate Summit
Managed by Nevil Jhaveri
STAGE
CONFIRMED
DATES
Jul 18, 2026
MINIMUM
$240,000
SOCIAL
Sharma Quinceañera
Managed by Amrita Jhaveri
STAGE
TENTATIVE
DATES
Aug 22, 2026
MINIMUM
$58,000
WEDDING
Chen-Wong Wedding
Managed by Amrita Jhaveri
STAGE
FINAL
DATES
Jul 24, 2026
MINIMUM
$145,000
Program info
Edit Program
Kaur & Nanda Wedding
Add Event
WEDDING · QUOTE M-U76YC66 · FOLIO 9198
Kaur & Nanda Wedding
A seven-day program at The Ritz-Carlton, Las Colinas · Monday, Jul 20 – Sunday, Jul 26, 2026
EVENTS
9
PEAK GUESTS
353
F&B MIN
$420K++
REVISION FLAGS
2 critical
GUARANTEE
72 hr prior
RUN OF SHOW · EVENTS
Jul 20–26, 2026 · scroll left/right · click any event
TUE 7/21 · 6 PM
Mehndi Hospitality
THE GALLERY · 80
WED 7/22 · 9 AM
Haldi Brunch
POOL DECK · 158
WED 7/22 · 6 PM
Mehndi Dinner Buffet
TERRACE · 219
THU 7/23 · 4:15 PM
Baraat Welcome
EVENT LAWN · 353
THU 7/23 · 6 PM
Sangeet Dinner
EVENT LAWN · 344
FRI 7/24 · 1 PM
Wedding Lunch · High Tea
PAVILION · 346
SAT 7/25 · 6 PM
Cocktail Reception
PROMENADE · 353
SAT 7/25 · 8 PM
Reception Dinner
TERRACE · 353
SAT 7/25 · 10 PM
Dessert & Dance
BALLROOM · 353
CONTRACT · GENESIS DOCUMENT
REVISED_JKK_JUL20-Kaur-Nanda-Wedding-BEOs-v2-071926.pdf
Parsed · 9 catered events extracted · 2 revision flags
EVENTS · 9 CATERED FUNCTIONS · 7 DAYS
TUE
23
JUL
Mehndi Hospitality
→
WED
24
JUL
Haldi Brunch
→
WED
24
JUL
Mehndi Dinner Buffet
→
THU
25
JUL
Baraat Welcome
→
THU
25
JUL
Sangeet Dinner Buffet
→
FRI
26
JUL
Wedding Lunch · High Tea
→
SAT
27
JUL
Cocktail Reception
→
SAT
27
JUL
Reception Dinner
→
SAT
27
JUL
Dessert Reception & Dance
→
AT A GLANCE
Quote #M-U76YC66
Folio #9198
StageCONTRACTED
ClientsH. Kaur · Dr. A. Nanda
On-SiteHarleen Kaur
Hotel MgrKim Houston · Kristin Pedigo
ManagerAmrita Jhaveri
F&B Minimum$420,000++
Room Rental$8,500 (across functions)
Service Charge15% F&B
Admin Fee11% (taxable)
Sales Tax8.25%
Room Charge26% svc + 6% state tax
Peak Guests353 (Sat dinner)
PROGRAM RISKS · 5
L3
Mehndi Dinner — bar package shows Prestige but should be Deluxe Host on Consumption per earlier pricing. $19K swing.
VIEW DATA →
L3
Sangeet specialty cocktails listed at $20 each — confirm if included in $89 bar package.
VIEW DATA →
L2
Sangeet equipment gap — hotel cannot provide Tall Stoves or Charcoal Grill. Caterer must source.
VIEW DATA →
L1
Wedding Lunch diagram "Set Up TBC" — escalate to Kim Houston before guarantee.
VIEW DATA →
L1
Reception Dinner — (45) Service Tables flagged "what does this look like and where?" by hotel.
VIEW DATA →
PROGRAM NOTES
Booking name: In Honor of Harleen Kaur and Dr. Amit Nanda Wedding. Billing through DALIL Wedding Account · 1391 Osage Road, North Brunswick, NJ 08902. On-site contact: Harleen Kaur (732) 640-4714.
Multi-day program: Tue Jul 21 (Mehndi Hospitality) → Sun Jul 26 (teardown). Wedding Showroom holds storage continuously across all 7 days; The Gallery hospitality room refreshes nightly.
Two revision flags from BEO v2 (printed Sun 7/19): (1) Mehndi Dinner bar package should revert to Deluxe Host on Consumption per earlier pricing, not Prestige. (2) Sangeet specialty cocktails ($20 each) likely already covered in $89 Prestige bar — confirm with Kim Houston.
Caterer-driven program: outside catering provides ALL hot food, lassi, chai, and most beverages across 9 functions. Hotel handles bar packages, hot box rentals, urns/mugs, and equipment. Prashe Design Atelier handles all decor, linens, and Reception tablescape (chargers, plates, cutlery, gold serving spoons).
Equipment gap on Sangeet: hotel cannot provide (2) Tall Stoves or (1) Portable Charcoal Grill. Caterer must source.
EVENT · MAY 15, 2026
Three-Course Dinner
AI · CONFLICTS DETECTED
L3 · LLM: Five vendor slots remain TBC at 12 days from event. Guarantee window opens Tuesday 5/12.
REVIEW →
DATE
Sat, Jul 25, 2026
TIME
8:30 PM – 1:30 AM
GUESTS
201
VENUE
Terrace
SETUP
8:00 AM
BREAKDOWN
2:00 AM
BEATS · RUN OF SHOW
—
COMMUNICATION HUB
Inbox
👥
LoomaPro Team
All team members
DOCUMENT VAULT
Documents
Contracts, MEOs, change orders, invoices — all versioned and traceable.
Coming with the alpha
Document vault, version diffing, and contract clause search.
REFERENCE
Codes & conventions
A glossary of every label, badge, and code in LoomaPro — what each one means and when you'll see it.
DOCUMENT CODES
Codes you'll see on every screen.
LoomaPro uses a small set of canonical document codes that thread through the entire program — from contract through invoice. Once you learn them, every screen reads quickly.
LO #
LETTER OF ORDER
The program identifier. Format is MMDDYY-INITIALS where the date is the wedding or first event date and the initials are the first letters of each party's last name. The LO carries through to the MEO, invoice, change orders, and addenda for the program's full life.
ExampleQuote M-U76YC66 · Jul 20–26, 2026 · Kaur-Nanda
MEO
MASTER EVENT ORDER
LoomaPro's branded operational document. Dynamically generated per event from structured data. Versioned (Rev 01, 02, 03…) with a full audit trail. Bidirectionally traceable to contract clauses — every line item points to a section. Replaces the legacy BEO.
WhereEvent Detail → "View Master Event Order" gold button
BEO
BANQUET EVENT ORDER
The legacy industry document — static, manually generated, often faxed. LoomaPro does not produce BEOs; the MEO supersedes it. Mentioned here for vocabulary continuity with operators who came up through Delphi, Cvent, or Tripleseat.
INV #
INVOICE
Same root as the LO with a revision suffix. Each revision is captured in the audit log. Invoices are pre-event estimates that auto-reconcile post-event against actual consumption.
ExampleINV #M-U76YC66-02 · the 2nd revision of Kaur-Nanda's invoice
CO #
CHANGE ORDER
Issued when contracted terms change mid-program. Numbered sequentially per program (CO #001, CO #002…). Always references the original section being amended. Triggers a DocuSign envelope to the client. Appears in Documents → Pending Signatures.
ExampleCO #003 · Sangeet music extension · sourced from May 2 client email
§
CONTRACT SECTION
Section reference within the executed contract. Format is § N(letter) where N is the section number and the letter is the subsection. Appears throughout the trace overlay and in citation chips.
Example§ 4(g) · Section 4 (F&B) · subsection (g) (Reception · Beverage)
SOURCE DOC PILL
The original source PDF is available. Clicking opens the underlying document (contract, addendum, scanned rider) at the cited page. Appears at the top of the trace overlay.
THE THREE-LAYER AI CASCADE
How LoomaPro reasons.
Every output from LoomaPro — a risk flag, a suggestion, a draft, an executed action — comes from one of three reasoning layers. Knowing which layer fired tells you whether to trust the output absolutely, weigh it, or verify it before acting.
L1 · RULES
Rules engine
Deterministic. Always correct.
Hard rules from the contract: capacity, F&B minimums, attrition, service charges, sales tax. Computed, not inferred.
"Resort Pool Deck capacity is 180; Haldi at 158."
L2 · ML
Risk scoring
Probabilistic. Weighted on history.
Statistical models trained on prior events at this property and across the network. Outputs are probabilities with confidence bands.
"75% probability of F&B minimum miss based on current pacing."
L3 · LLM
Reasoning
Narrative. Anthropic Claude.
Reasoning over context — contract, MEO, communications, vendor schedules. Surfaces emergent conflicts no rule could catch.
"Ceremony breakdown 6:30 PM and reception load-in 6:15 PM share a loading dock."
L1 · RULES
DETERMINISTIC
Use as ground truth. L1 outputs are hard rules from the contract — capacity violations, missed minimums, attrition over-runs. If L1 says it, treat it as fact and act on it. L1 risks are typically must-fix.
WhereRisk Feed · Trace overlay · Agent thinking steps
L2 · ML
PROBABILISTIC
Treat as informed forecast. L2 outputs are predictions — pacing risk, attrition exposure, undercharged add-ons. Always show a probability and a confidence band. Verify with current data before acting; outputs degrade if the underlying fields are stale. L2 risks are should-fix.
L3 · LLM
REASONING
Always read before sending. L3 outputs are the most powerful and the most fallible. Used for contract parsing, conflict detection, drafting, and change-order generation. Anthropic Claude is the reasoning core. L3 risks are usually judgment calls.
TipClick any agent citation marked with ↗ to see the full L3 reasoning chain
Cascade re-run
When a field changes — say a guest count update — all three layers re-evaluate. L1 checks for new violations, L2 re-scores risk, L3 detects new emergent issues. Visible in Ask LoomaPro → Act mode.
PROGRAM STAGES
Where the program is.
Programs progress through four stages, shown as colored pills on the program card and in "At a Glance."
TENTATIVE
Initial inquiry. Contract drafted but not signed; client may still be comparing properties. F&B minimums and dates are working assumptions, not commitments.
CONFIRMED
Verbal commitment received but contract not yet countersigned. Common for repeat clients and corporate accounts. LoomaPro still parses the draft contract for risk modeling.
CONTRACTED
Contract signed and executed. The genesis event is complete; the program is live in LoomaPro. All four AI layers are active. MEOs can be generated. This is the working state of most programs.
FINAL
All MEOs locked, invoice issued, event(s) complete. Used for closeout reporting and historical performance analysis. Becomes training data for L2 and L3.
FIELD STATUS
What each pill means.
When you open an event accordion or look at an MEO field, you may see one of these labels.
PARSED
Field was extracted automatically from the contract by the LLM. Confidence ≥ 95%. No human input needed. Most fields on a typical contract land here.
NEEDS ATTN
Field was extracted but L1, L2, or L3 flagged it for human review. Click the field to see the flag's reasoning. Common causes: ambiguous contract language, conflicting riders, novel addendum structure.
Complete · 42 fields parsed
Contract parse summary. Shown on the Program Detail's contract card. The number reflects how many fields the LLM successfully extracted. Anything that didn't parse is flagged separately.
— Not yet entered
Field exists in the schema but has no value. Operations team needs to fill it before the MEO can be locked. Clicking opens an inline editor.
MEO Ready
All required fields populated; document is ready for client review. Shown on the dashboard's "Upcoming Events" panel.
Needs Review
Required fields missing or fields flagged for ops team validation. Click into the event to see which accordions need attention.
Live
Event is currently in progress. LoomaPro freezes most edits during this state to preserve audit integrity; emergency edits go through an approval flow.
PARSE CONFIDENCE
How sure LoomaPro is.
Every field extracted from the contract has a confidence score, visible in the trace overlay when you click any line item.
High
95–100%
Clear contract terms, unambiguous extraction. Default state for most fields. Most well-drafted contracts produce 90%+ High-confidence on first parse. No review required.
Medium
85–95%
Some ambiguity. Auto-extracted but flagged for ops review. Common for hand-written riders, addenda with novel structure, or contracts that reference external schedules. Reviewer date stamp recorded.
Low
< 85%
Ambiguous or conflicting language. Triggers a "NEEDS ATTN" flag on the related accordion. Manual entry or correction required. Rare on well-drafted contracts.
Auto-confirmed
L1 ONLY
Field was extracted by the L1 Rules engine — deterministic — and requires no human review. Common for room rentals, attrition tiers, and tax/service-charge rates. Shown in the trace overlay's "Reviewed" row.
CONCEPTS
The vocabulary underneath.
Terms that don't appear as labels but shape how LoomaPro works. Useful in conversation with engineering, legal, or design partners.
Genesis event
The act of ingesting an executed contract as the originating data event for a program. The contract is the system of record; every downstream artifact (MEO, invoice, change order) inherits from it. LoomaPro's defining onboarding pattern.
Bidirectional traceability
Every line item in the MEO and invoice traces back to a contract clause; every clause traces forward to the items it produced. Click any invoice line to see the source clause; click a contract clause (in Documents) to see all line items it produced. Enables automatic detection of contract-vs-operational drift.
Cross-event memory
LoomaPro remembers the structure of every program it processes. The Kaur-Nanda Wedding (a 7-day Punjabi/South Indian program) informs the next multi-day Indian wedding's parse confidence; the Patel Corporate Summit informs the next mid-size corporate program. The system gets smarter with every property onboarded — an operational moat that compounds.
Drift detection
LoomaPro compares contracted terms against operational state continuously. When the MEO drifts from the contract — a guest count change, a vendor swap, a menu addition — the relevant layer flags it and proposes a change order if material.
Addendum
A formal written amendment to the executed contract. Numbered sequentially per program. LoomaPro can draft addenda automatically (Ask LoomaPro → Draft mode) and route them for signature. Each addendum produces its own parse pass and is layered on top of the original contract in the trace overlay.
Last revised May 3, 2026 · LoomaPro v0.4 · pre-alpha
VISION · MOBILE
LoomaPro in the field.
A glanceable, voice-first companion for event directors during live service. Same Ask LoomaPro agent · same contract data · designed for AirPods and a hand on the iPhone.
VOICE-FIRST
Hands stay clean.
"Hey LoomaPro, what's next on the run of show?" The captain doesn't break service to type.
GLANCEABLE
Now-status, not deep screens.
Live event card, current run-of-show position, active risks. The desk app's depth, demoted.
OFFLINE-READY
Hotel back-of-house has dead spots.
MEO, allergens, run of show, vendor contacts cached locally. L1 queries always work.
LIVE EVENT
LOOMAPRO · LIVE
NAIR · PUROHIT
Dinner
Terrace · 353 guests · Family-style
NOW · 9:35 PM
21% in
!
Lamb · 70 plates · pour sauce center of chop
·
Calabrian chili oil set on all 30 tables
Captain's home view during service. Run-of-show progress, what's next, what needs attention.
VOICE Q&A
‹
Ask LoomaPro
Listening…
"How is the lamb supposed to be served?"
L
Sauce covers center of chop. Goosenecks on table with extra sauce. High request for well done. Calabrian chili oil set with cover.
TAP FOR DETAILS ↓
RECENT
"Late night menu — pork or beef?"
"Vegetarian count tonight"
"Bar service end time"
●
One-sentence answers. Citations collapsed. AirPods or hand-raise to ask.
PROACTIVE PUSH
9:00
Tuesday, May 12
L
LOOMAPRO
now
Final guarantee due today
Kaur-Nanda · 72 hours prior per Marriott terms. Saturday count 347 adult / 6 minor = 353. Expected becomes guaranteed if no update.
Tap to open LoomaPro →
Decisions reach the captain even when the app is closed. One tap to confirm.
BUILD SEQUENCE
Pre-alpha · now → Q3. Web LoomaPro. Desk-grade. Ship five paid pilots and learn what they actually do on mobile.
Late alpha · Q4. PWA wrapper of the web app — offline cache, push notifications, voice-in. One engineer, ~6 weeks. Buys 6–9 months of mobile learning before native.
Series A milestone. Native iOS (then Android) with AirPods voice integration. watchOS companion designed in alongside it. By this point, the field interactions are known from real usage.
PROPERTY DATABASE
Venues
Capacities, kitchen specifications, noise ordinances, union ratios.
EVENT SETUP PREVIEW · HOVER AREAS FOR DETAILS
Indexed property
The Ritz-Carlton Las Colinas
Property reference data compiled from indexed contract and BEO records: event spaces, kitchen paths, setup windows, outdoor exposure, service notes, rental inventory, and department watch zones.
12Spaces
4Kitchens
428Keys
500Largest cap
Outdoor terrace
Terrace
350max
Indoor ballroom
Ballroom
500max
Pool / deck venue
Resort Pool Deck
180max
Pavilion / covered space
Pavilion
350max
Pre-function / foyer
Promenade + Foyer ABCD
350max
Hospitality / breakout
The Gallery
80max
Back-of-house support
Showroom + Office
Opssupport
Arrival / guest movement
Villa 200 + Main Tower
Flownode
Kitchen and service paths
Operational map
Ballroom Kitchen
Primary service hub for ballroom, terrace, promenade, foyer, plated service, receptions, dessert stations, and late-night operations.
Pavilion Kitchen
Support kitchen for pavilion and lawn-side events; store access windows, hot-box staging, vendor prep rules, and service corridor notes.
Poolside Kitchen
Pool deck and outdoor-station support path; document storage rooms, live-station limits, fire/safety rules, and service timing constraints.
Gallery Corridor
Hospitality and breakout support route; note refresh timings, equipment allowed, overnight hold permissions, and staffing handoff points.
Standards and inventory
Reference data ready
Capacities
Room capacities by setupStore max seated, reception, classroom, theater, u-shape, boardroom, and custom floorplan limits per space.Service
Kitchen routes and timingsKeep service elevators, loading dock, prep kitchens, hot-box staging, and stewarding notes attached to venue records.Inventory
Tables, chairs, bars, stagingReusable property inventory belongs here so each program can reference it without duplicating operational facts.Rules
Noise, weather, safetyCapture evergreen restrictions: curfew, music limits, fire code, rain backup, security, access control, and vendor insurance.Active conversations
L
Choose a conversation
Use New message to start or select an active DM.
SYSTEMS
Connectors
Hotel systems, client channels, files, calendars, and sales data feeding one operational view.
Bring every planning signal into LoomaPro.
Connect the tools teams already use, then let LoomaPro attach contracts, messages, meetings, files, room blocks, and handovers to the right program.
9
Connectors
M
Contracts
Gmail
Import signed contracts, vendor threads, change requests, and attachments into the program inbox.
Ready
Meetings
Zoom
Attach planning call recordings and transcripts to the right program for AI review.
Not connected
M
Meetings
Google Meet
Capture meeting notes, attendee context, and follow-ups from client or internal calls.
Not connected
W
Client chat
Bring client, planner, vendor, and banquet-team messages into one traceable event thread.
Ready
31
Schedule
Google Calendar
Sync event dates, tastings, site visits, production calls, and key operational deadlines.
Connected
O
Enterprise
Outlook
Support hotel teams using Microsoft mail, calendars, Teams invites, and shared folders.
Connected
D
Files
Drive / SharePoint
Watch shared folders for contracts, BEOs, menus, floorplans, run sheets, and vendor quotes.
Connected
P
Hotel data
Opera / PMS
Connect room blocks, account profile, deposits, billing notes, and arrival patterns.
Request access
S
Events CRM
Delphi / Tripleseat
Pull opportunity, event order, space hold, package, and sales handover data into LoomaPro.
Request access
Intake
Channel priority
Data flow
Source handling
HELP
Support
Ask the LoomaPro assistant how to use the platform, troubleshoot a workflow, or find the right screen.
L
LoomaPro Support AI
Product guidance · onboarding · workflow help
Online
How can I help?
Ask about uploading contracts, reviewing extracted fields, managing programs, using the Inbox, generating MEOs or invoices, connecting systems, or inviting your team.
ACCOUNT
Settings
Manage your profile, photo, and personal details.
Profile picture
Accepted files: JPG, PNG, TIFF.
Personal information
Not shown on public profile.
Profile information
Visible to your team.