FIGURE 11

Transaction Coordinator Invitation and Access Workflow

OFFRPORTL — Role-Scoped TC Invitation, Authentication, and Post-Acceptance Access Control
Abstract
A computer-implemented method and system for extending authenticated, role-scoped access to a real estate transaction record for a transaction coordinator (TC) party. Either the listing agent or buyer's agent may independently invite a TC by creating a TransactionCoordinator entity record linked to the offer via offer_id. Upon authentication, the TC receives read-only access to post-acceptance offer data — including binding contracts, amendments, reinstatement proposals, and party contact information — and is included in all post-acceptance notification workflows. All TC access events are timestamped and persisted for a complete audit trail. TC parties are explicitly excluded from all write operations on the offer lifecycle.
§1 — Invitation & Access Process Flow (6 Steps)
1
LISTING AGENT or BUYER'S AGENT
Initiates TC Invitation
Either agent navigates to accepted offer detail view and selects "Add Transaction Coordinator." Agent enters TC name, email, and phone. System records added_by (agent email) and added_by_role (listing_agent or buyer_agent).
2
SYSTEM
Creates TC Record & Sends Invitation Email
System creates a TransactionCoordinator entity record linked to the offer via offer_id. invited_at timestamp recorded server-side. Invitation email dispatched to TC via Resend API containing property address, offer details, and direct portal access link.
3
TRANSACTION COORDINATOR
Accepts Invitation & Authenticates
TC clicks portal link in invitation email. TC authenticates via platform login (email match). System verifies TC email against TransactionCoordinator entity email field. Access granted upon match. last_accessed_at timestamp recorded.
4
TRANSACTION COORDINATOR
Accesses Post-Acceptance Offer View
TC is granted read-only access to the accepted offer record including: binding contract PDF, amendment history, termination documents, reinstatement proposals, and all party contact information. TC cannot submit, accept, reject, or counter offers.
5
TRANSACTION COORDINATOR
Receives Relevant Notifications
TC is included in email notification chain for post-acceptance events: amendment proposals, amendment acceptances, termination notices, reinstatement proposals, and closing status updates. Each notification logged in email_delivery_log.
6
SYSTEM
Maintains Audit Trail
All TC access events recorded with last_accessed_at timestamp. TC record persists on offer entity for full transaction lifecycle. TC invitation and access history preserved for litigation-grade audit replay.
§2 — TC Access State Diagram
OFFER ACCEPTED
Offer status = accepted Binding contract uploaded
→
TC INVITED
TC entity created invited_at recorded Invite email sent
→
TC AUTHENTICATED
Email match verified last_accessed_at recorded Portal access granted
→
TC ACTIVE
Read-only access Notifications enabled Audit trail active
→
TRANSACTION CLOSED
Status = sold Full audit preserved TC record archived
TC can be added by either agent at any point after offer acceptance · Multiple TCs supported per offer
§3 — Data Model — TransactionCoordinator Entity Schema
EntityFieldTypeDescription
TransactionCoordinatoroffer_idstring (FK)Foreign key linking TC record to the associated Offer entity. One TC record per offer per coordinator.
TransactionCoordinatornamestringFull name of the transaction coordinator.
TransactionCoordinatoremailstringTC email address. Used for authentication match and notification delivery.
TransactionCoordinatorphonestringTC phone number for contact reference.
TransactionCoordinatoradded_bystringEmail of the agent who added this TC. Preserved for audit.
TransactionCoordinatoradded_by_roleenumRole of inviting agent: listing_agent or buyer_agent.
TransactionCoordinatorinvited_atdatetimeServer-side timestamp when TC was invited. Establishes invitation audit anchor.
TransactionCoordinatorlast_accessed_atdatetimeUpdated each time TC authenticates and accesses the offer portal. Enables access audit trail.
§4 — Access Control Matrix — Post-Acceptance Permissions
PermissionListing AgentBuyer's AgentTCSellerBuyer
View Accepted Offer Terms (AI Parsed)✔✔✔——
View Binding Contract PDF✔✔✔✔✔
View Amendment History✔✔✔——
View All Party Contact Info✔✔✔——
Propose Amendment✔✔———
Accept / Reject Amendment✔✔———
Initiate Termination✔✔———
Propose Reinstatement✔✔———
Upload Binding Contract✔✔———
Export / Download PDFs✔✔✔✔✔
Receive Post-Acceptance Notifications✔✔✔✔✔
Add Another TC✔✔———
✔ Permission granted  ·  — Not permitted  ·  TC column highlighted — TC has read-only access to post-acceptance data only
§5 — Security & Audit Properties
Email-Based Identity Verification
TC identity is verified by matching authenticated session email against the email field on the TransactionCoordinator entity. No separate credential system required.
Offer-Scoped Access
TC access is scoped exclusively to the linked offer_id. TC cannot access other listings, other offers, or any data outside the specific transaction.
Invitation Timestamping
invited_at is recorded server-side at creation. Establishes a tamper-evident invitation audit anchor for the full transaction timeline.
Access Event Logging
last_accessed_at is updated on every authenticated TC portal visit, enabling full chronological replay of coordinator access history.
Dual-Agent Invitation Authority
Either listing agent or buyer's agent may independently invite a TC. added_by and added_by_role fields preserve which agent extended each invitation.
Write-Operation Exclusion
TC role is explicitly excluded from all offer lifecycle write operations at the application layer — counter, accept, reject, amend, terminate, reinstate.
§6 — Key Patentable Claims Summary
Claim 1.A method for granting a transaction coordinator party access to a real estate offer record by creating a TransactionCoordinator entity linked via offer_id, verifying the coordinator's identity by matching authenticated email to the stored TC email field, and recording a last_accessed_at timestamp on each access event.
Claim 2.The method of claim 1, wherein either a listing agent or buyer's agent may independently initiate a TC invitation for the same offer, and each invitation stores the inviting agent's email and role separately, enabling multi-party TC coordination on a single transaction.
Claim 3.The method of claim 1, wherein the transaction coordinator is included in the email notification chain for all post-acceptance offer lifecycle events including amendment proposals, termination notices, and reinstatement proposals, with each notification logged in the offer email_delivery_log.
Claim 4.The system of claim 1, wherein the transaction coordinator is granted read-only access to post-acceptance offer data including binding contract, amendment history, and party contacts, while being explicitly excluded from all write operations including counter offers, acceptances, rejections, and amendments.
Fig. 11 — Transaction Coordinator Invitation and Access Workflow. Either agent may invite a TC by creating a TransactionCoordinator entity record linked to the offer. TC identity is verified via email match at authentication. TC receives read-only access to post-acceptance offer data and is included in all post-acceptance notification chains. All access events are timestamped. TC write operations are explicitly prohibited at the application layer.