FIGURE 12

Post-Acceptance Lifecycle State Machine

OFFRPORTL — Counter Offer · Amendment · Termination · Reinstatement Workflows

Abstract

A computer-implemented system and method for managing the complete post-acceptance lifecycle of a real estate transaction offer record. Following offer acceptance, the system supports four concurrent and sequential workflows: (1) counter offer negotiation with withdrawal capability and tri-source engagement tracking; (2) structured amendment proposals with an append-only amendments array and per-amendment-index view history isolation; (3) contract termination with PDF storage and timestamping; and (4) reinstatement proposals enabling either party to revive a terminated contract. All workflows share a unified engagement tracking architecture — document-isolated view history arrays, email delivery logging, and tracking pixel correlation — producing a litigation-grade audit trail across the full post-acceptance transaction lifecycle.

§1 — Post-Acceptance Master State Machine

ACCEPTED

status = accepted Binding contract uploaded All parties notified

→

COUNTERED

status = countered Counter PDF uploaded Buyer agent notified

→

AMENDMENT PENDING

Amendment proposed Pending accept/reject All parties notified

→

REINSTATEMENT PENDING

Reinstatement proposed Pending accept/reject All parties notified

→

TERMINATED

status = terminated Termination PDF stored Reinstatement available

→

SOLD

status = sold Full audit archived Transaction complete

From State	Event / Trigger	To State	Actor	Key Data Written
Accepted	Agent sends counter offer	Countered	Listing Agent / Buyer's Agent	counter_pdf_url, counter_submitted_at, status
Countered	Receiving party accepts counter	Accepted	Listing Agent / Buyer's Agent	accepted_at, binding_contract_url, status
Countered	Counter withdrawn	Accepted	Initiating Agent	counter_withdrawn, counter_withdrawal_pdf_url, counter_withdrawn_at
Accepted	Amendment proposed	Amendment Pending	Either Agent	amendments[ ] append: proposed_by, proposed_at, pdf_urls, status=pending
Amendment Pending	Amendment accepted	Accepted	Opposing Agent	amendments[i].status=accepted, amendments[i].accepted_at, response_pdf_urls
Amendment Pending	Amendment rejected	Accepted	Opposing Agent	amendments[i].status=rejected
Accepted	Contract terminated	Terminated	Either Agent	termination_pdf_url, termination_reason, terminated_at, status
Terminated	Reinstatement proposed	Reinstatement Pending	Either Agent	reinstatement_proposed_by, reinstatement_pdf_url, reinstatement_proposed_at, reinstatement_status=pending
Reinstatement Pending	Reinstatement accepted	Accepted	Opposing Agent	reinstatement_status=accepted, reinstatement_accepted_at, reinstatement_accepted_pdf_url
Reinstatement Pending	Reinstatement rejected	Terminated	Opposing Agent	reinstatement_status=rejected
Accepted	Closing completed	Sold	System / Agent	status=sold, full audit archived

§2 — Detailed Workflow Steps Per Event Type

Counter Offer Workflow (6 Steps)

Agent Initiates Counter

Listing agent or buyer's agent selects "Send Counter Offer" from offer detail. Counter terms entered: price, closing costs, closing date, earnest money, custom notes.

Counter PDF Uploaded

Counter offer PDF uploaded to file storage. counter_pdf_url stored on Offer entity. counter_submitted_at timestamp recorded server-side.

Status → Countered

Offer status field updated to countered. Previous status archived in audit trail. Counter terms persisted on Offer entity fields.

Notifications Dispatched

Email sent via Resend API to buyer agent + buyer. In-app bell notification with unread badge. counter_notification_acknowledged_by array tracks who has acknowledged.

Tri-Source Tracking

counter_offer_viewed_by array populated on email open (pixel) and portal view. Engagement correlation engine synthesizes delivery log + pixel + portal view per party.

Counter Decision

Receiving party accepts (status → accepted), rejects (status → rejected), or counter-counters (new counter initiated). Counter withdrawal available: counter_withdrawn = true, counter_withdrawal_pdf_url stored.

Amendment Workflow (6 Steps)

Either Party Proposes Amendment

Listing agent or buyer's agent proposes amendment from accepted offer view. Amendment description entered. One or more amendment PDFs uploaded (pdf_urls array).

Amendment Record Created

New object appended to amendments array on Offer entity. Fields: proposed_by (role), proposed_at (timestamp), description, pdf_urls, status = pending.

Notifications Dispatched

sendAmendmentNotifications dispatched to all parties. Email includes amendment description, PDF link, and direct portal link. amendment_viewed_by[amendment_index] tracking initiated.

Opposing Party Reviews

Receiving party accesses portal. amendment_viewed_by array updated with viewer_email, viewer_role, viewed_at, source (portal or email). Engagement gap detection active.

Accept or Reject Decision

Receiving party accepts or rejects amendment. amendments[index].status updated to accepted or rejected. amendments[index].accepted_at timestamp recorded. Response PDFs optionally uploaded.

Acceptance Notifications

sendAmendmentAcceptedNotifications dispatched to all parties. Amendment acceptance logged in email_delivery_log. Amendment history permanently preserved on Offer entity.

Termination & Reinstatement Workflow (6 Steps)

Contract Terminated

Either party initiates termination. Termination PDF uploaded (termination_pdf_url). termination_reason recorded. terminated_at timestamp set. Status → terminated.

Reinstatement Proposed

Either party may propose reinstatement. reinstatement_proposed_by (role) set. reinstatement_pdf_url uploaded. reinstatement_notes recorded. reinstatement_proposed_at timestamped. reinstatement_status = pending.

Notifications Dispatched

sendReinstatementNotifications dispatched. reinstatement_viewed_by array tracking initiated. Engagement correlation active for reinstatement document. View reminders scheduled.

Opposing Party Reviews

Receiving party accesses reinstatement proposal via portal or email link. reinstatement_viewed_by array updated (viewer_email, viewer_role, viewed_at, source). ViewReminder auto-resolves on confirmed view.

Accept or Reject Decision

Receiving party accepts or rejects reinstatement. reinstatement_status updated to accepted or rejected. reinstatement_accepted_at timestamp recorded. reinstatement_accepted_pdf_url stored on acceptance.

Outcome: Reinstated or Closed

On acceptance: status reverts toward active transaction. sendReinstatementAcceptedNotifications dispatched. On rejection: offer remains terminated. Full audit trail preserved.

§3 — Data Model — Post-Acceptance Offer Entity Fields

Scope	Field	Type	Description
Counter Offer	counter_price	number	Counter offer purchase price.
Counter Offer	counter_closing_date	date	Proposed closing date in counter.
Counter Offer	counter_pdf_url	string	URL to uploaded counter offer PDF.
Counter Offer	counter_submitted_at	datetime	Server-side timestamp of counter submission.
Counter Offer	counter_expires_at	datetime	Expiration timestamp of counter offer.
Counter Offer	counter_withdrawn	boolean	True if counter offer was withdrawn before response.
Counter Offer	counter_offer_viewed_by	array	Document-isolated view history for counter offer (viewer_email, viewer_role, viewed_at, source).
Amendment	amendments[ ]	array	Array of amendment objects: proposed_by, proposed_at, description, pdf_urls, status, accepted_at, response_pdf_urls.
Amendment	amendment_viewed_by[ ]	array	Per-amendment view history keyed by amendment_index. Isolates each amendment's engagement independently.
Termination	termination_pdf_url	string	URL to uploaded termination document.
Termination	termination_reason	string	Free-text termination reason.
Termination	terminated_at	datetime	Server-side termination timestamp.
Reinstatement	reinstatement_proposed_by	enum	Role of proposing party: listing_agent or buyer_agent.
Reinstatement	reinstatement_pdf_url	string	URL to reinstatement proposal document.
Reinstatement	reinstatement_status	enum	Current reinstatement state: pending, accepted, or rejected.
Reinstatement	reinstatement_accepted_at	datetime	Timestamp of reinstatement acceptance.
Reinstatement	reinstatement_viewed_by	array	Document-isolated view history for reinstatement proposal.

§4 — Shared Engagement Tracking Architecture (All Post-Acceptance Events)

Document Isolation

Each post-acceptance event type has its own dedicated viewed_by array on the Offer entity. counter_offer_viewed_by, amendment_viewed_by (keyed by amendment_index), and reinstatement_viewed_by are fully isolated. View events never cross-contaminate between document types.

Tri-Source Correlation

For every document event, three independent sources are correlated per party: (1) email_delivery_log confirms transmission, (2) tracking pixel (trackEmailView function) confirms email open, (3) authenticated portal view confirms document access. Source field on every view event enables synthesis.

ViewReminder Integration

Every post-acceptance document event (counter sent, amendment proposed, reinstatement proposed) creates a ViewReminder entity record. The sendViewReminders scheduled automation polls every 30 minutes, detecting engagement gaps and dispatching escalating reminders at 12h, 24h, and 72h intervals.

§5 — Key Patentable Claims Summary

Claim 1.A method for managing a counter offer lifecycle on an accepted real estate transaction record comprising: uploading a counter offer PDF, recording a counter_submitted_at timestamp, transitioning offer status to countered, dispatching multi-party notifications with engagement tracking, and enabling counter withdrawal by setting counter_withdrawn = true with a withdrawal PDF stored on the entity.

Claim 2.A method for managing contract amendments on an accepted real estate transaction by appending amendment objects to a persistent amendments array on the Offer entity, each object recording proposed_by role, proposed_at timestamp, pdf_urls array, and status field, with per-amendment view history isolated by amendment_index in a parallel amendment_viewed_by array.

Claim 3.A method for managing contract termination and reinstatement comprising: transitioning offer status to terminated with a termination PDF and timestamp, enabling either party to propose reinstatement by populating reinstatement_proposed_by, reinstatement_pdf_url, and reinstatement_status fields, and resolving reinstatement via reinstatement_status = accepted or rejected with a timestamped reinstatement_accepted_at record.

Claim 4.The system of claims 1–3, wherein each post-acceptance document event (counter offer, amendment, termination, reinstatement) initiates an independent document-isolated view history array on the Offer entity, and each view event carries a source field (portal or email) enabling tri-source engagement correlation with the email_delivery_log for litigation-grade audit.

Fig. 12 — Post-Acceptance Lifecycle State Machine. Following offer acceptance, the system manages four concurrent workflows: counter offer negotiation (with counter withdrawal), structured amendment proposals (with per-amendment-index view isolation), contract termination, and reinstatement. All state transitions are timestamped and persisted on the Offer entity. A shared document-isolated engagement tracking architecture applies tri-source correlation (email delivery, pixel, portal view) and automated escalating ViewReminder workflows to every post-acceptance document event.