LegalGEСодержание
Legal Sandbox Georgia LLC
Document Type: Function Rulebook (Binding) Version: 1.1 Effective Date: 13 May 2026 Document Language: English (Georgian version prevails in case of conflict) Status: Binding contract, incorporated by reference into all applicable Role Terms and Conditions
Changes in v1.1: Cross-reference addition for Calendar Function Rulebook v1.0. §8.1.1 updated to reference Calendar Rulebook for publication mechanics. The legal/contractual effect of publication (Standing Offer per §8.3) remains governed here. No operational rule changes; no re-consent required.
This Specializations & Pricing Function Rulebook ("Rulebook") establishes the rules governing how Specialists select their professional specializations, publish service pricing, and offer book-from-calendar consultations on the legal.ge platform operated by Legal Sandbox Georgia LLC, Registration Number 405713768 (the "Platform").
This Rulebook is a binding part of the Terms and Conditions of every role permitted to set specializations or publish pricing on the Platform. By selecting a specialization, publishing pricing, or making a calendar slot available for booking, You agree to be bound by this Rulebook.
In the event of any conflict between this Rulebook and a Role Terms and Conditions document, the Role Terms and Conditions prevail with respect to that role's specific obligations not addressed in this Rulebook; this Rulebook prevails on matters of specialization selection, pricing publication, and book-from-calendar mechanics. In the event of any conflict between this Rulebook and another Function Rulebook, conflict resolution is governed by Article 19.
1.1.1 This Rulebook provides a single authoritative source of truth governing the Specializations and Pricing function on the Platform.
1.1.2 This Rulebook serves to:
(a) Define the four-level practice area hierarchy (L1 → L2 → L3 → Services);
(b) Establish how Specialists select specializations (at L2 level);
(c) Govern published pricing for Services (FIXED, RANGE, QUOTE pricing models);
(d) Govern the book-from-calendar consultation flow;
(e) Govern the median market price display on Service catalog pages;
(f) Define tier-gated pricing capabilities (advanced fields available at higher subscription tiers);
(g) Specify what happens when subscription tier changes affect specialization or pricing eligibility;
(h) Allocate liability for pricing-related and specialization-related matters.
1.2.1 This Rulebook applies to:
(a) Specialization selection by Solo Specialists and Company Specialists;
(b) Pricing publication for Services in the Platform catalog;
(c) Bulk pricing operations;
(d) Book-from-calendar consultation initiation;
(e) Median market price aggregation and display;
(f) Subscription-tier impact on specialization and pricing capabilities.
1.2.2 This Rulebook does NOT govern:
(a) Subscription tier definitions, billing, and lifecycle — governed by the Subscriptions & Billing Function Rulebook;
(b) Inquiry submission, Quote, payment Capture — governed by the Inquiries & Messaging Function Rulebook (except where this Rulebook modifies Quote behavior for book-from-calendar);
(c) Video session mechanics — governed by the Video Consultations Function Rulebook;
(d) Reviews and Ratings — governed by the Reviews & Ratings Function Rulebook;
(e) Calendar UX, Google Calendar integration, week-grid interface — governed by Platform operational documentation, not this Rulebook;
(f) Verification process and standards — governed by individual Role Terms and Conditions and Platform Verification policy.
1.3.1 This Rulebook directly affects the following roles:
| Role | Capability |
|---|---|
| Solo Specialist | Selects specializations; publishes pricing; offers calendar bookings |
| Company Specialist | Selects specializations independently within Company's L2 specializations; publishes pricing; offers calendar bookings |
| Company | Holds Affiliated Specialist Specializations as institutional context; does NOT itself publish individual Service pricing |
| Trainer | May hold specializations in Trainer capacity (training topics); pricing for Trainings governed by Trainer T&C, not this Rulebook |
| User (Client) | Views published pricing; books from calendar; submits Inquiries |
| Moderator | May review and moderate custom_note content |
| Author | Not affected |
| Trainee | Not affected |
| Organisation | Not affected (Organisations do not provide Services on the Platform) |
2.1 Capitalized terms used but not defined in this Rulebook have the meanings given in the applicable Role Terms and Conditions or other Function Rulebook where context makes clear.
2.2 For purposes of this Rulebook:
"Available Slot" means a calendar time window published by a Specialist as available for book-from-calendar consultation booking per Article 8.
"Bulk Pricing Operation" means a single API request through which a Specialist creates or updates pricing for multiple Services simultaneously, governed by Article 7.
"Consultation Fee" means the fee published by a Specialist as the standard rate for a calendar-booked consultation, governed by Article 8.
"DRAFT Status" means a pricing record that has been created but is not publicly visible; pricing in DRAFT status does not appear on the Specialist's public Profile or in the catalog.
"FIXED Pricing" means a pricing model in which the Specialist publishes a single specific price for a Service, governed by Article 5.
"L1" means a top-level practice area domain in the Platform's category hierarchy.
"L2" means a specialization category — the level at which Specialists select their professional specializations.
"L3" means a sub-specialization category nested under L2.
"Median Market Price" means the aggregate median pricing displayed by the Platform for a given Service across all Specialists who have published pricing for that Service, governed by Article 9.
"Pricing Model" means the type of pricing structure used (FIXED, RANGE, or QUOTE), governed by Article 5.
"PUBLISHED Status" means a pricing record that is publicly visible on the Specialist's Profile and in the catalog.
"QUOTE Pricing" means a pricing model in which the Specialist publishes no specific price for a Service; price is set per Inquiry per the Inquiries Rulebook, governed by Article 5.
"RANGE Pricing" means a pricing model in which the Specialist publishes a minimum and maximum price for a Service, governed by Article 5.
"Service" means a specific service offering in the Platform catalog, attached to an L3 category, for which Specialists may publish pricing.
"Specialty Slot" means an L2 specialization position in a Specialist's Profile, the count of which is governed by the Subscriptions Rulebook tier matrix.
"Standing Offer" means the binding effect of an Available Slot publication: the Specialist commits to honoring book-from-calendar bookings during such windows, governed by Article 8.
"Subscriptions Rulebook" means the Subscriptions & Billing Function Rulebook v1.1 or successor.
"Tier-Gated Field" means a pricing field whose use is restricted to Specialists holding a specific subscription tier or higher (e.g., custom_note, turnaround_days_min, turnaround_days_max), governed by Article 6.
"Verified Specialist" means a Specialist whose Verification has been completed; required for publishing pricing per Article 4.4.
3.1.1 The Platform organizes legal practice areas in a four-level hierarchy:
L1 — Top-level practice domain (e.g., "Civil Law", "Criminal Law")
└── L2 — Specialization (e.g., "Family Law", "Tax Law")
└── L3 — Sub-specialization category (e.g., "Divorce Proceedings", "Tax Disputes")
└── Service — Specific service offering (e.g., "Divorce Filing Preparation", "Tax Audit Defense")
3.1.2 Specialists interact with the hierarchy as follows:
(a) L1 — organizational only; Specialists do NOT select L1 categories;
(b) L2 — the level at which Specialists select their specializations (governed by Article 4);
(c) L3 — automatically inherited based on Specialist's L2 selections; Specialists do NOT manually pick L3;
(d) Services — the level at which Specialists publish pricing (governed by Article 5).
3.2.1 The Platform maintains the L1/L2/L3 category tree and the Service catalog.
3.2.2 Categories and Services may be added, modified, or deprecated by the Platform per operational policy.
3.2.3 Where the Platform deprecates a category or Service:
(a) Specialists with active selections or pricing under the deprecated entity are notified;
(b) Reasonable transition period is provided (typically 30 days);
(c) After transition period, deprecated selections are migrated, archived, or rendered inactive per the Platform's deprecation plan.
3.3.1 Each Service in the catalog is attached to an L3 category, which is itself nested under an L2 specialization category.
3.3.2 A Specialist may publish pricing for a Service only where the Service's L3 → L2 chain maps to an L2 specialization the Specialist has selected per Article 4.
3.3.3 This mapping is enforced at pricing creation and update; pricing requests for Services outside the Specialist's L2 specializations are rejected.
4.1.1 All Specialists (Solo Specialists and Company Specialists) must select at least one (1) L2 specialization to operate on the Platform.
4.1.2 L2 specializations declare the Specialist's professional practice area and:
(a) Determine which Services the Specialist may price (Article 3.3);
(b) Drive Specialist visibility in directory searches and Inquiry routing;
(c) Form part of the Specialist's public Profile.
4.2.1 L2 specializations are selected in two contexts:
(a) Onboarding:
(i) During the onboarding flow, the Specialist selects L2 specializations before submitting Verification documentation;
(ii) Selections are recorded in the Platform's specialist_service_categories data store;
(iii) Specializations may be selected pre-Verification but pricing remains blocked until post-Verification per Article 4.4.
(b) Profile Update:
(i) Verified Specialists may modify selected L2 specializations at any time through Profile management;
(ii) Update operations follow a delete-then-insert pattern: existing specialization rows are removed and new selections inserted;
(iii) This pattern ensures the Specialist's active specializations always reflect their latest selections.
4.3.1 The number of L2 specializations a Specialist may select is governed by the Subscriptions Rulebook tier matrix:
| Tier | L2 Specialty Slots |
|---|---|
| Solo Specialist — Freemium | 1 |
| Solo Specialist — Pro | 3 |
| Solo Specialist — Expert | 7 |
| Company — Basic | 5 (Pool, first-come-first-served) |
| Company — Established | 10 (Pool) |
| Company — Enterprise | Unlimited |
| Company Specialist | Per Affiliated Company's tier (inherited from Pool per Subscriptions Rulebook Article 7) |
4.3.2 The Subscriptions Rulebook is canonical for these limits; this Rulebook references them but does not modify them.
4.3.3 Where a Specialist's selected specialization count exceeds the allowed limit (e.g., due to subscription downgrade), Article 11 applies.
4.4.1 Pre-Verification: specialization selection is allowed; pricing publication is blocked.
4.4.2 Post-Verification: specialization selection AND pricing publication are unlocked.
4.4.3 Pricing actions attempted by unverified Specialists are rejected at the API layer.
4.5.1 Specialists may change their L2 specializations as often as needed; no cooldown period applies in v1.0.
4.5.2 The Platform reserves the right to introduce reasonable change-frequency limits in future versions for system stability or to prevent abuse.
4.6.1 When a Specialist removes an L2 specialization:
(a) Existing pricing records for Services nested under that L2 are preserved in the Specialist's pricing data;
(b) Pricing remains in the Specialist's pricing data store for record-keeping;
(c) Such pricing continues to feed into the Median Market Price calculation per Article 9 to maintain catalog statistical continuity;
(d) Such pricing is NOT publicly displayed on the Specialist's Profile after L2 removal until the L2 is re-selected;
(e) If the Specialist re-selects the L2 later, the previously-preserved pricing becomes publicly visible again automatically.
4.6.2 This preservation model serves two purposes:
(a) Specialists do not lose pricing work due to specialization adjustments;
(b) Catalog Median Market Price remains statistically stable across specialization fluctuations.
4.7.1 A Company Specialist may select specializations independently of the Affiliated Company's institutional specializations.
4.7.2 A Company Specialist's selections must, however, fall within the Company's selected L2 specializations.
4.7.3 Each Company Specialist counts toward the Affiliated Company's specialization Pool per Subscriptions Rulebook Article 7.
4.7.4 Where the Company removes a Specialty Slot the Specialist depends on, the Specialist's pricing for affected Services is preserved per Article 4.6 but rendered non-public until the Company restores the Slot or the Specialist transitions to Solo or another Company.
4.8.1 Where a Trainer holds specializations in Trainer capacity, these are training topics, not legal Services.
4.8.2 Trainer specializations and Training pricing are governed by the Trainer Terms and Conditions, not this Rulebook.
4.8.3 Where a Trainer also operates as a Solo Specialist or Company Specialist, this Rulebook applies to the Specialist capacity, separately from Trainer obligations.
5.1.1 The Platform supports three pricing models for Services:
(a) FIXED — Specialist publishes a single specific price for the Service.
(b) RANGE — Specialist publishes a minimum and a maximum price for the Service.
(c) QUOTE — Specialist publishes no specific price; price will be determined per Inquiry per the Inquiries Rulebook.
5.1.2 A Specialist selects a Pricing Model per Service; different Services may use different models.
5.2.1 Under FIXED Pricing:
(a) The Specialist sets price_fixed to a specific GEL amount;
(b) The price is published on the Specialist's Profile and in the catalog;
(c) The price is indicative only — see Section 5.5.
5.3.1 Under RANGE Pricing:
(a) The Specialist sets price_min and price_max to GEL amounts;
(b) price_min must be strictly less than price_max — degenerate ranges (min = max) are rejected; Specialists wishing to publish a single price must use FIXED instead;
(c) Both bounds are published on the Specialist's Profile and in the catalog;
(d) The published range is indicative only — see Section 5.5.
5.4.1 Under QUOTE Pricing:
(a) No price fields are populated;
(b) The Service is shown on the Specialist's Profile with "Price on quote" or equivalent indicator;
(c) Pricing is determined when an Inquiry is submitted, per Inquiries Rulebook §10.2.
5.5.1 Published pricing (FIXED or RANGE) is indicative only. Specifically:
(a) Published prices serve as marketing and discovery information — they help Clients evaluate Specialists and select among them;
(b) Published prices do NOT constitute a binding offer that a Client may accept by acceptance alone;
(c) The Inquiry Quote process under the Inquiries Rulebook §10.2 governs the actual binding price for any consultation;
(d) The Inquiry Quote may differ from the published price (higher or lower) at the Specialist's discretion based on the specific Inquiry.
5.6.1 All published pricing displayed on Specialist Profiles and in the Platform catalog SHALL be accompanied by a public disclaimer, in the user's interface language, substantively to the effect:
"Published prices are indicative. The actual price for any consultation is set at the Quote stage based on the specific Inquiry, and may differ from the published price. Please submit an Inquiry to receive a binding Quote."
5.6.2 The disclaimer's specific wording is at the Platform's discretion but must clearly communicate the indicative nature of published pricing.
5.6.3 The disclaimer is mandatory; pricing display without it constitutes a Platform compliance failure to be corrected promptly upon discovery.
5.7.1 Notwithstanding the indicative-only status under Section 5.5, the Platform may, in its discretion, investigate and act on patterns of substantial Quote-vs-Published-Price divergence where such patterns suggest deceptive practice (e.g., consistently publishing low FIXED prices to attract Inquiries, then quoting substantially higher).
5.7.2 Action under this Section may include:
(a) Warning the Specialist;
(b) Requiring revision or removal of misleading published pricing;
(c) In severe cases, treating as a violation under the Inquiries Rulebook §13 or this Rulebook's Article 18.
6.1.1 A pricing record (specialist_service_pricing) for a Service contains:
| Field | Type | Description | Tier-Gated? |
|---|---|---|---|
service_id |
reference | Associated Service offering | No |
pricing_tier |
enum | FIXED / RANGE / QUOTE | No |
price_fixed |
GEL amount | Fixed price (FIXED only) | No |
price_min |
GEL amount | Minimum price (RANGE only) | No |
price_max |
GEL amount | Maximum price (RANGE only) | No |
consultation_fee |
GEL amount | Calendar-booking rate (Article 8) | No |
consultation_free |
boolean | Free initial consultation flag | No |
billing_model |
enum | Pricing or payment model descriptor | No |
custom_note |
text (max 500 chars) | Specialist note visible to Clients | YES — Expert/Enterprise tier only |
turnaround_days_min |
integer | Expected delivery window minimum | YES — Expert/Enterprise tier only |
turnaround_days_max |
integer | Expected delivery window maximum | YES — Expert/Enterprise tier only |
status |
enum | DRAFT / PUBLISHED / ARCHIVED | No |
6.2.1 The following fields are restricted to Specialists at higher subscription tiers:
(a) custom_note — available only to:
(i) Solo Specialists on Expert tier;
(ii) Company Specialists whose Affiliated Company holds Enterprise tier subscription;
(b) turnaround_days_min and turnaround_days_max — same tier restrictions as above.
6.2.2 Specialists at lower tiers (Freemium, Pro, Basic, Established) cannot populate these fields; attempts to do so are rejected at the API layer.
6.2.3 Where a Specialist's subscription is downgraded such that they lose access to a tier-gated field:
(a) Existing field values are preserved in the pricing record;
(b) Field values are NOT publicly displayed while subscription remains at the lower tier;
(c) Field values become publicly visible again if the Specialist subsequently upgrades back to the eligible tier;
(d) Specialists are notified of the field-display change at downgrade.
6.3.1 custom_note content:
(a) Maximum 500 characters;
(b) Plain text only — no HTML, scripts, or active content;
(c) Subject to Platform content moderation per Posting Rulebook content rules where applicable;
(d) May be reviewed and moderated by Moderators;
(e) Should not contain off-Platform contact information (per Inquiries Rulebook §13);
(f) Should not contain promotional content for non-Platform services;
(g) Should not contain claims that conflict with the Specialist's Verified credentials.
6.4.1 turnaround_days_min and turnaround_days_max express the estimated service completion time from the start of the engagement to delivery of the deliverable (e.g., document drafted, opinion issued).
6.4.2 Turnaround commitments are indicative, not binding:
(a) They communicate the Specialist's typical delivery window;
(b) They are not legally enforceable delivery deadlines;
(c) Actual completion times depend on the specific matter and may vary.
6.4.3 Where turnaround_days_min is provided, turnaround_days_max must also be provided; both must be positive integers; turnaround_days_min must be less than or equal to turnaround_days_max.
6.5.1 A pricing record may be in one of three statuses:
(a) DRAFT — created but not publicly visible; only the owning Specialist sees it;
(b) PUBLISHED — publicly visible on Specialist Profile and in catalog;
(c) ARCHIVED — explicitly archived by the Specialist; not displayed; counts toward neither active pricing nor Median Market Price calculation.
6.5.2 Transitions:
(a) DRAFT → PUBLISHED requires Specialist Verification per Article 4.4;
(b) PUBLISHED → ARCHIVED is at Specialist's discretion;
(c) ARCHIVED → DRAFT is permitted (revives for editing);
(d) Direct ARCHIVED → PUBLISHED is permitted but counts as a fresh publication for pricing-history purposes.
7.1.1 A Specialist creates pricing for a single Service through Platform interface or API.
7.1.2 Validation rules at creation:
(a) Specialist is authenticated;
(b) Specialist is Verified per Article 4.4;
(c) Service exists in the catalog and is in published status;
(d) Service's L3 → L2 mapping aligns with one of the Specialist's selected L2 specializations per Article 3.3;
(e) Required fields for the chosen Pricing Model are populated:
(i) FIXED: price_fixed required;
(ii) RANGE: price_min and price_max required, with price_min < price_max;
(iii) QUOTE: no price fields required;
(f) Tier-gated fields (custom_note, turnaround_days) are blocked for ineligible tiers per Article 6.2;
(g) The total count of non-archived pricing records does not violate any subscription plan pricing-row count limit.
7.1.3 Successful creation returns the pricing record with assigned status (DRAFT or PUBLISHED per Specialist's choice and Verification status).
7.2.1 A Specialist may update an existing pricing record at any time.
7.2.2 Updates may modify any field within the constraints of the Pricing Model and tier-gating rules per Articles 5–6.
7.2.3 Updates require the same eligibility checks as creation (verification, specialization mapping, tier eligibility).
7.2.4 Where an update would cause loss of compliance (e.g., tier downgrade affecting custom_note), the update is rejected; Specialist must first remove the offending field or upgrade tier.
7.3.1 A Specialist may delete a pricing record at any time.
7.3.2 Deletion is hard delete; the record is removed from the data store.
7.3.3 Distinguish from ARCHIVED: archived records are preserved (per Section 6.5.1); deleted records are removed.
7.3.4 Deleted records:
(a) Are no longer publicly displayed;
(b) Cease contributing to Median Market Price calculation per Article 9;
(c) Cannot be recovered (no soft-delete in v1.0).
7.3.5 Specialists are advised to use ARCHIVED status for temporary suspension and DELETE only when permanently abandoning a Service offering.
7.4.1 Specialists may create or update pricing for multiple Services simultaneously through Bulk Pricing Operations.
7.5.1 Maximum batch size: two hundred (200) Services per Bulk Pricing Operation.
7.5.2 Two operation modes:
(a) create-missing (default):
(i) Pricing records are created only for Services that do not already have a pricing record by the Specialist;
(ii) Existing pricing records are not modified;
(b) overwrite-all:
(i) Pricing records are created for Services without existing pricing AND existing pricing records for Services in the request are overwritten with the new template;
(ii) Use with caution — this overwrites prior pricing irreversibly except by re-issuing pricing.
7.6.1 Bulk operations validate:
(a) All target Service IDs map to the Specialist's L2 specializations per Article 3.3;
(b) Tier-gated fields in the bulk template are permitted for the Specialist's tier per Article 6.2;
(c) Resulting total non-archived pricing rows do not exceed any subscription plan limits;
(d) Pricing Model template is valid (e.g., RANGE template requires price_min < price_max).
7.6.2 Where any Service ID in the batch fails validation, the entire batch is rejected; partial success is not supported.
7.7.1 Bulk operations are logged in the Platform audit trail with:
(a) Specialist ID;
(b) Operation mode;
(c) List of affected Service IDs;
(d) Pricing template values;
(e) Timestamp;
(f) Success/failure outcome.
8.1.1 Specialists may publish Available Slots in their calendar through the Platform Calendar Functionality. The mechanics of calendar publication, modification, withdrawal, sync with Google Calendar, and Personal Block management are governed by the Calendar Function Rulebook v1.0. The legal/contractual effect of publication (Standing Offer per §8.3 of this Rulebook) is governed here and not in the Calendar Rulebook.
8.1.2 Clients may book Available Slots directly from the Specialist's Profile, triggering an automated consultation booking flow at the Specialist's published consultation_fee.
8.1.3 This represents a third consultation initiation path alongside:
(a) Service Inquiry Consultations (governed by Inquiries Rulebook);
(b) Direct Consultations (Specialist-initiated magic-link, governed by Video Consultations Rulebook Article 7);
(c) Book-from-Calendar Consultations (this Article).
8.2.1 A Specialist may publish Available Slots only if:
(a) Specialist is Verified per Article 4.4;
(b) Specialist holds at least one selected L2 specialization;
(c) Specialist has published at least one Service pricing record under their L2;
(d) consultation_fee is set on at least one pricing record;
(e) Specialist's subscription is in good standing (not Past Due / Suspended).
8.3.1 Publication of an Available Slot constitutes a Standing Offer:
(a) The Specialist commits to honoring book-from-calendar bookings during published Available Slots;
(b) A Client booking an Available Slot constitutes immediate acceptance of the Standing Offer;
(c) The booking is binding upon Client payment; no further Specialist Quote step or acceptance is required;
(d) The Specialist cannot decline a valid book-from-calendar booking after Client payment.
8.3.2 Standing Offer is preserved while:
(a) The published Available Slot remains in the calendar;
(b) The Specialist's Verification, subscription, and specialization status remain valid;
(c) The Specialist has not removed or modified the Slot.
8.3.3 Specialists wishing to retain discretion over individual booking acceptance must NOT publish Available Slots; they should use Inquiry-initiated consultations instead.
8.4.1 Booking sequence:
(a) Client browses Specialist's Profile and views Available Slots in the published calendar;
(b) Client selects an Available Slot;
(c) Platform auto-creates an Inquiry record with:
(i) Service: Specialist's specified Service for which consultation_fee is set;
(ii) Quote price: equal to consultation_fee;
(iii) Communication Format: per Specialist's calendar configuration (typically Video);
(iv) Scheduled time: the booked Available Slot;
(d) Inquiry is auto-accepted by virtue of the Standing Offer (no Specialist Quote step);
(e) Client completes payment per Inquiries Rulebook §10.3 (preauth);
(f) Upon successful preauth, the Available Slot becomes a confirmed booking;
(g) Consultation proceeds at the scheduled time per the applicable Communication Format Rulebook (Video Rulebook for Video sessions);
(h) Capture and post-consultation Appeal mechanics follow Inquiries Rulebook §11–12.
8.5.1 Book-from-Calendar bookings follow the standard Inquiries Rulebook §10.3 cancellation rules:
(a) Cancellation before consultation start releases the preauth (refund);
(b) Cancellation rules for late cancellation, no-show, etc. follow Inquiries Rulebook §12.
8.5.2 Where Specialist becomes unable to honor a Standing Offer booking due to circumstances outside their control:
(a) Specialist must notify the Platform and the Client as soon as practicable;
(b) Specialist must propose reschedule per Inquiries Rulebook §12.6 mechanics;
(c) Where reschedule is not accepted by the Client, full refund per Inquiries Rulebook §10.3 applies;
(d) Repeated failure to honor Standing Offers may constitute violation under Article 18.
8.6.1 A Specialist may remove an Available Slot at any time before a Client books it.
8.6.2 Once a Client has booked the Slot:
(a) The Slot is no longer "available" — it is a confirmed booking;
(b) The Specialist cannot remove or unilaterally cancel the booking absent justification per Section 8.5.2.
8.7.1 The consultation_fee field on a pricing record serves as the rate for book-from-calendar bookings of that Service.
8.7.2 Where multiple Services have consultation_fee set, the Specialist's calendar configuration determines which Service's consultation_fee applies to which Available Slot.
8.7.3 Where consultation_free is true:
(a) consultation_fee may still be set as a notional value (used for accounting purposes);
(b) Client pays nothing for the consultation itself;
(c) The 10 GEL Platform fee per Inquiries Rulebook §10.5 applies, charged to the Specialist on Capture;
(d) The Specialist receives no payment for the consultation but bears the 10 GEL Platform fee.
8.8.1 Specialists may terminate the Standing Offer for future bookings by:
(a) Removing all Available Slots from the calendar;
(b) Setting consultation_fee to null on all pricing records;
(c) Removing the underlying pricing records.
8.8.2 Termination of Standing Offer does not affect bookings already confirmed.
9.1.1 The Platform displays a Median Market Price for each Service in the catalog, providing Clients with reference pricing information when browsing the catalog.
9.1.2 Median Market Price aids:
(a) Client price discovery and comparison;
(b) Specialist competitive insight (Specialists see how their pricing compares to median);
(c) Catalog usability and trust.
9.2.1 Median Market Price for a Service is calculated as the median of:
(a) All FIXED pricing records' price_fixed values for that Service in PUBLISHED status;
(b) All RANGE pricing records' midpoint values for that Service in PUBLISHED status, where midpoint = (price_min + price_max) / 2.
9.2.2 QUOTE pricing records do not contribute to Median calculation (no numeric value).
9.2.3 DRAFT and ARCHIVED pricing records do not contribute to Median calculation.
9.2.4 Pricing records preserved per Article 4.6 (where Specialist removed L2 specialization but pricing retained):
(a) Continue contributing to Median per Section 4.6.1(c);
(b) This maintains catalog statistical continuity.
9.3.1 Median Market Price is displayed on the public Service catalog page for each Service.
9.3.2 Median Market Price is NOT displayed on individual Specialist Profiles; Specialist Profiles show only the Specialist's own pricing.
9.4.1 Median Market Price is displayed for any Service that has at least one (1) PUBLISHED pricing record contributing to the calculation.
9.4.2 No minimum number of contributing pricing records is required; even Services with one PUBLISHED price will display that single price as the median.
9.4.3 The Platform reserves the right to introduce minimum-threshold display rules in future versions for statistical reliability.
9.5.1 Median Market Price updates automatically as pricing records are created, updated, archived, or deleted.
9.5.2 Real-time recalculation is not guaranteed; the Platform may use cached values updated periodically (e.g., daily) for performance.
9.6.1 Median Market Price displayed in the catalog SHALL be accompanied by a disclaimer indicating:
(a) The figure represents a calculated median across published prices;
(b) Actual prices vary by Specialist;
(c) Individual Specialist's Quote may differ from the median.
10.1.1 Subscription tier determines the maximum number of L2 specializations a Specialist may select per Article 4.3.
10.1.2 Tier limits are enforced at:
(a) Specialization selection (cannot exceed limit on add);
(b) Subscription downgrade (over-limit conditions trigger Article 11);
(c) Bulk operations and pricing creation (cannot create pricing for Services outside specialty slots).
10.2.1 Subscription tier controls access to tier-gated pricing fields per Article 6.2.
10.2.2 Specialists upgrading to a tier with access to additional fields gain immediate use; previously-empty tier-gated fields can be populated.
10.2.3 Specialists downgrading to a tier without access to certain fields:
(a) Retain field values in storage per Section 6.2.3;
(b) Lose public display of those values until tier is restored;
(c) Are notified at downgrade.
10.3.1 Subscription plans may impose maximum total pricing-row counts (combined non-archived PUBLISHED + DRAFT records).
10.3.2 Where applicable, plans specify the limit; the Platform's published Plan documentation is canonical.
10.3.3 Bulk operations and individual pricing creation are blocked from exceeding the limit.
10.4.1 When a Specialist's subscription enters Past Due state per Subscriptions Rulebook §8.3:
(a) Existing pricing records remain visible during the grace period;
(b) New pricing creation may be blocked at Platform's discretion;
(c) Available Slots remain published for already-scheduled bookings only.
10.4.2 When a Specialist's subscription transitions to Freemium (per Past Due exhaustion in Subscriptions Rulebook §8.4.1):
(a) Existing pricing records are preserved;
(b) Specialist's specialization count must comply with Freemium limit (1) — over-limit triggers Article 11;
(c) Tier-gated fields in pricing records become non-public per Section 6.2.3;
(d) Available Slots remain published for already-scheduled bookings only.
11.1.1 A Specialist's specialization or pricing configuration may become "over-limit" through:
(a) Subscription downgrade reducing specialty slots;
(b) Subscription Past Due exhaustion auto-degrading to Freemium per Subscriptions Rulebook §8.4;
(c) Plan deprecation per Subscriptions Rulebook Article 19;
(d) Manual Platform intervention (e.g., admin reduction).
requires_config_resolution Flag11.2.1 When over-limit conditions are detected, the Platform sets the Specialist's subscription record to requires_config_resolution: true.
11.2.2 This flag triggers:
(a) In-app notification to the Specialist;
(b) Email notification to the Specialist;
(c) UI prompt at next login directing the Specialist to resolve the over-limit condition;
(d) Restricted access to certain Platform actions until resolution.
11.3.1 The Specialist resolves an over-limit condition by either:
(a) Reducing specializations to within the new limit:
(i) Specialist selects which L2 specializations to keep;
(ii) Removed L2 specializations: pricing for those L2's Services is preserved per Article 4.6;
(b) Upgrading subscription back to a tier supporting the existing specialization count.
11.4.1 The Specialist has a reasonable period (typically 30 days) to resolve the over-limit condition.
11.4.2 During the resolution period:
(a) Existing public Profile remains visible;
(b) Existing PUBLISHED pricing records remain visible (consistent with Subscriptions Rulebook §8.4 feature degradation but not visibility loss);
(c) New pricing creation outside the new limit is blocked;
(d) New specialization additions are blocked;
(e) Existing Available Slots remain published only for previously-scheduled bookings.
11.5.1 Where the Specialist fails to resolve within the resolution period:
(a) The Platform may automatically reduce specializations to fit the limit, applying a deterministic rule (e.g., earliest selected specializations retained);
(b) Affected pricing for removed specializations is preserved per Article 4.6;
(c) The Specialist is notified of automatic resolution.
11.5.2 Automatic resolution may produce an outcome the Specialist did not choose; Specialists are encouraged to resolve manually.
11.6.1 Where the Specialist chooses to remove multiple L2 specializations:
(a) The delete-then-insert workflow per Section 4.2.1(b) applies;
(b) Pricing for all affected Services is preserved per Article 4.6;
(c) requires_config_resolution flag is cleared upon successful reduction.
12.1.1 A Company Specialist publishes pricing independently for Services within the Affiliated Company's L2 specializations.
12.1.2 Each Company Specialist's pricing is their own and is displayed on their individual Specialist Profile.
12.1.3 Different Company Specialists at the same Affiliated Company may publish different prices for the same Service.
12.2.1 A Company Specialist may publish pricing only for Services nested under the Affiliated Company's selected L2 specializations.
12.2.2 The Affiliated Company's L2 specializations are managed at the Company level by Company management roles per Company T&C.
12.2.3 When a Company Specialist's eligible L2 specializations change due to Company action (e.g., Company removes an L2 from its Pool):
(a) Affected pricing records are preserved per Article 4.6;
(b) Pricing becomes non-public until the L2 is restored or the Specialist transitions to Solo/another Company;
(c) The Specialist is notified.
12.3.1 When a Company Specialist departs an Affiliated Company:
(a) Pricing records are preserved with the Specialist (not the Company);
(b) The 15-day grace period under Subscriptions Rulebook §12.5 applies for tier features;
(c) Pricing visibility depends on the Specialist's post-departure subscription status:
(i) If activates Solo Tier: pricing remains visible per Solo subscription rules;
(ii) If does not activate Solo Tier within 15-day grace: enters No Subscription state per Subscriptions Rulebook §8.6; pricing preserved but not publicly displayed.
12.4.1 Company-wide pricing (where the Company sets pricing applied to all Affiliated Specialists) is NOT supported in v1.0.
12.4.2 Each Company Specialist must publish their own pricing.
12.4.3 Company-wide pricing may be considered in future Platform versions.
13.1.1 The Platform logs all specialization and pricing actions, including:
(a) Specialization additions, removals, and updates;
(b) Pricing creation, updates, deletions, and bulk operations;
(c) Status transitions (DRAFT, PUBLISHED, ARCHIVED);
(d) Tier-gated field access and changes;
(e) Standing Offer publications (Available Slots);
(f) requires_config_resolution flag transitions.
13.1.2 Audit log entries record:
(a) Timestamp;
(b) Specialist ID;
(c) Action type;
(d) Affected entity (specialization, pricing record, Service);
(e) Before/after values for modifications;
(f) Source of the action (UI, API, bulk operation, admin).
13.2.1 Specialists may request audit log entries pertaining to their own specialization and pricing actions through the Platform interface.
13.2.2 Such requests are honored within reasonable timeframes consistent with the Platform's Privacy Policy.
13.3.1 The Platform's pricing API enforces:
(a) Specialist authentication and Verification status;
(b) Service eligibility per L3 → L2 mapping;
(c) Tier-gated field permissions;
(d) Subscription plan limits;
(e) Pricing Model field requirements;
(f) Required disclaimer display.
13.3.2 Client-side enforcement is supplementary; server-side validation is authoritative.
13.4.1 Pricing creation and updates are permissioned and validated by Platform backend services.
13.4.2 Service eligibility is enforced by category ownership rather than client-side assumptions.
13.4.3 Subscription plan state is authoritative for pricing capabilities.
14.1.1 Specialists shall NOT:
(a) Publish FIXED or RANGE pricing intending to substantially deviate from those prices in actual Inquiry Quotes (bait-and-switch under Section 5.7);
(b) Falsify Verification documents to gain pricing privileges;
(c) Publish pricing for Services outside their selected L2 specializations through any technical workaround;
(d) Publish custom_note content violating Section 6.3 rules;
(e) Use bulk operations to abuse the Platform (e.g., spamming pricing across many irrelevant Services);
(f) Publish Available Slots without intent to honor them;
(g) Repeatedly cancel book-from-calendar bookings absent legitimate justification;
(h) Misrepresent specialty credentials through L2 selection.
14.2.1 Clients shall NOT:
(a) Bulk-book Available Slots without intent to attend;
(b) Submit Inquiries solely to compare published prices to actual Quotes for non-engagement reasons;
(c) Misuse the post-consultation appeal process per Inquiries Rulebook §12.
14.3.1 Violations may result in:
| Severity | Possible Consequences |
|---|---|
| Minor | Warning |
| Standard | Pricing privileges restricted; specific records removed |
| Serious | Pricing rights suspended; loss of Standing Offer eligibility |
| Severe | Account suspension or termination per Role T&C |
14.3.2 Specific consequence application is at Platform discretion in coordination with Moderators per Moderator T&C.
15.1.1 The Platform shall notify Specialists of the following events:
(a) Pricing record published (transition to PUBLISHED);
(b) Pricing record archived by Specialist action;
(c) Tier downgrade affecting tier-gated fields (Section 6.2.3);
(d) Tier downgrade affecting specialization count (requires_config_resolution);
(e) requires_config_resolution flag set (Article 11.2);
(f) Automatic resolution applied after failure to resolve (Article 11.5);
(g) Available Slot booked by Client (Article 8.4);
(h) Available Slot cancelled by Client;
(i) Bulk operation completion (success or failure);
(j) Service catalog deprecation affecting Specialist's pricing (Article 3.2.3);
(k) L2 specialization deprecation affecting Specialist's selections.
15.2.1 The Platform shall notify Clients of:
(a) Booking confirmation after successful book-from-calendar payment;
(b) Booking cancellation by Specialist (Section 8.5.2);
(c) Reschedule offered following Specialist inability to honor Standing Offer.
15.3.1 Notifications are delivered via:
(a) In-app notification (mandatory);
(b) Email to address on file (mandatory);
(c) Other channels at Platform discretion.
16.1.1 This Rulebook is governed by the laws of Georgia.
16.2.1 Any dispute arising out of or relating to this Rulebook that cannot be resolved through Platform mechanisms shall be subject to the exclusive jurisdiction of the courts of Tbilisi, Georgia.
16.3.1 This Rulebook is published in English, Georgian, and Russian. In the event of any conflict between language versions, the Georgian version prevails.
17.1.1 The Platform reserves the right to amend this Rulebook at any time, in its sole discretion.
17.2.1 Non-material amendments take effect upon publication; continued use constitutes acceptance.
17.2.2 Material amendments (e.g., changes to Pricing Model availability, changes to tier-gating, changes to Standing Offer mechanics) are subject to:
(a) Affirmative re-consent for Specialists wishing to continue publishing pricing;
(b) At least thirty (30) days' advance notice.
17.3.1 A Specialist who does not accept a material amendment may decline; the consequence is loss of pricing publishing privileges and removal of Available Slots from the calendar.
18.1.1 The Platform's liability for matters under this Rulebook is limited to:
(a) Maintaining the L1/L2/L3/Service catalog;
(b) Operating the pricing data store and API;
(c) Calculating and displaying Median Market Price;
(d) Enforcing tier-gating and validation rules;
(e) Providing audit logging.
18.1.2 The Platform is NOT liable for:
(a) The accuracy of any Specialist's published pricing;
(b) Mismatch between published pricing and actual Inquiry Quotes (subject to Section 5.7 anti-bait-and-switch);
(c) Specialist's failure to honor Standing Offers (governed by Inquiries Rulebook §12 and this Article 14);
(d) Median Market Price as an indicator of actual market value;
(e) Loss of business arising from Specialist's specialization or pricing decisions.
18.2.1 The Specialist is liable for:
(a) Accuracy of their published pricing;
(b) Maintaining published Available Slots they intend to honor;
(c) Compliance with custom_note content rules per Section 6.3;
(d) Specialty selection consistent with their actual professional qualifications;
(e) Honoring Standing Offers per Article 8;
(f) Tax obligations on consultation income (per Subscriptions Rulebook Article 15).
18.3.1 The Specialist shall defend, indemnify, and hold harmless the Platform from claims arising from:
(a) Misrepresentation of credentials through L2 specialization selection;
(b) Bait-and-switch pricing practices;
(c) custom_note content violations;
(d) Failure to honor Standing Offers;
(e) Disputes arising from published pricing inaccuracy.
18.4.1 The Platform's display of mandatory disclaimers per Sections 5.6 and 9.6 is essential to the Platform's liability protection; the Platform commits to including these disclaimers and updating them as appropriate.
19.1.1 This Rulebook coordinates with the following Function Rulebooks:
| Topic | Where the Rules Live |
|---|---|
| Subscription tier definitions and limits | Subscriptions & Billing Function Rulebook |
| Inquiry submission, Quote, Capture | Inquiries & Messaging Function Rulebook |
| Communications conduct, privilege | Inquiries & Messaging Function Rulebook |
| Video session mechanics | Video Consultations Function Rulebook |
| Direct Consultations (magic-link) | Video Consultations Function Rulebook Article 7 |
| Reviews and ratings | Reviews & Ratings Function Rulebook |
| Posting (where pricing relates to advertised content) | Posting Function Rulebook |
| Organisation membership | Organisation Terms and Conditions |
19.2.1 Conflicts are resolved as follows:
(a) Subscription tier definitions, billing, and lifecycle — Subscriptions Rulebook prevails;
(b) Inquiry mechanics, Quote, payment, Capture, post-consultation Appeals — Inquiries Rulebook prevails;
(c) Video session mechanics — Video Consultations Rulebook prevails;
(d) Reviews — Reviews Rulebook prevails;
(e) Specialization selection, pricing models, book-from-calendar Standing Offer mechanics, Median Market Price — this Rulebook prevails;
(f) Where matters genuinely cross categories — interpreted to give effect to all and avoid conflict; if irreducible, the more specific Rulebook prevails over the more general.
19.3.1 This Rulebook modifies the Inquiries Rulebook §10.2 Quote process for the limited case of book-from-calendar bookings:
(a) Inquiries Rulebook §10.2 generally requires a Specialist Quote step;
(b) For book-from-calendar bookings, the Specialist Quote step is auto-accepted based on the Standing Offer;
(c) This modification applies only to book-from-calendar bookings; standard Inquiry submission flow remains unchanged.
19.4.1 Adoption of this Rulebook may require minor reference updates to:
(a) Inquiries Rulebook — note book-from-calendar Quote auto-acceptance exception;
(b) Subscriptions Rulebook — note pricing tier-gating reference (no rule change; reference for completeness);
(c) Subscriptions Rulebook §1.2.2(d) — note "specialization selection" governed by this Rulebook;
(d) Such updates are non-substantive and applied through routine Rulebook updates.
20.1.1 If any provision of this Rulebook is held invalid, illegal, or unenforceable, the provision shall be modified to the minimum extent necessary to make it valid; if not possible, the provision shall be severed, and the remaining provisions shall continue in force.
20.2.1 This Rulebook, together with the master Terms and Conditions, Privacy Policy, Cookie Policy, and applicable Function Rulebooks and Role Terms and Conditions, constitutes the entire agreement regarding the Specializations and Pricing function on the Platform.
20.3.1 The Platform's failure to enforce any provision shall not constitute a waiver. Any waiver must be in writing to be effective.
| Version | Date | Author | Description |
|---|---|---|---|
| 1.0 | 13 May 2026 | Legal Sandbox Georgia LLC | Initial publication |
| Parameter | Value | Source |
|---|---|---|
| Practice area hierarchy | L1 → L2 → L3 → Services (4 levels) | Art. 3.1 |
| Specialist selection level | L2 | Art. 4.1 |
| Pricing creation level | Service (under L3) | Art. 5 |
| Pricing models | FIXED / RANGE / QUOTE | Art. 5.1 |
| Published price status | Indicative only | Art. 5.5 |
| Disclaimer required | Yes — on Profile and catalog | Art. 5.6 |
| Specialty slots — Freemium | 1 | Art. 4.3, Subs Rulebook §5.1 |
| Specialty slots — Pro | 3 | Art. 4.3 |
| Specialty slots — Expert | 7 | Art. 4.3 |
| Specialty slots — Company Basic | 5 (Pool, FCFS) | Art. 4.3 |
| Specialty slots — Company Established | 10 (Pool) | Art. 4.3 |
| Specialty slots — Company Enterprise | Unlimited | Art. 4.3 |
| Verification required for pricing | Yes | Art. 4.4 |
| Specialization changes | Unlimited | Art. 4.5 |
| Pricing on L2 removal | Preserved (private; contributes to Median) | Art. 4.6 |
| RANGE constraint | price_min < price_max (strict) | Art. 5.3 |
custom_note limit |
500 chars; plain text | Art. 6.3 |
custom_note tier gate |
Expert (Solo) / Enterprise (Company) | Art. 6.2 |
turnaround_days tier gate |
Expert (Solo) / Enterprise (Company) | Art. 6.2 |
| Bulk operation max | 200 Services | Art. 7.5.1 |
| Bulk modes | create-missing / overwrite-all | Art. 7.5.2 |
| Pricing statuses | DRAFT / PUBLISHED / ARCHIVED | Art. 6.5 |
| Standing Offer model | Calendar publication = binding offer | Art. 8.3 |
| Standing Offer cannot decline after payment | True | Art. 8.3.1(d) |
| Inquiry auto-acceptance | Book-from-calendar only | Art. 19.3 |
| Median calculation | Median of FIXED + RANGE midpoints (PUBLISHED only) | Art. 9.2 |
| Median display | Service catalog page only | Art. 9.3 |
| Median minimum threshold | None (any PUBLISHED price displayed) | Art. 9.4 |
| Free consultation Platform fee | 10 GEL on Specialist (per Inquiries §10.5) | Art. 8.7.3 |
| Over-limit resolution period | 30 days | Art. 11.4 |
| Failure-to-resolve action | Automatic deterministic reduction | Art. 11.5 |
| Company-wide pricing | Not in v1.0 | Art. 12.4 |
| Material amendment notice | 30 days | Art. 17.2 |
END OF RULEBOOK
© 2026 LegalGE. Все права защищены.