Editorial standards & current facts

Clear sourcing. Current facts. Traceable corrections.

This page is the public reference for DocketServe facts that can change over time—coverage, pricing, product definitions, plan limits, Network status and iPhone status—along with the standards used to research and correct published information.

OperatorVanguard Atlantic Legal Services LLC
Live coverage7 Florida county clusters
Standard service$75 · up to 3 attempts
Current statusWeb available · iPhone coming soon

Current DocketServe facts

Facts most likely to change.

These are the operating facts DocketServe currently publishes. Scope-specific product pages and current written terms still control when a detail needs more context.

01

Brand & operator

DocketServe is operated by Vanguard Atlantic Legal Services LLC.

DocketServe is the client process-service request workflow. DocketServe Command is software for independently sourced private process-server work. DocketServe Network is the credentialed field-capacity layer.

02

Live Florida coverage

South Florida: Miami-Dade, Broward and Palm Beach Counties.

Central Florida: Orange, Osceola, Polk and Hillsborough Counties.

Published coverage does not guarantee acceptance for every address or timeline.

03

Process-service pricing

Standard: $75, up to three attempts within seven days from the first attempt under the published standard scope.

Rush: $150, 48-hour turnaround measured from order confirmation for accepted rush scope.

Additional approved attempt: $25.

04

DocketServe Command

Professional: $49/month for 75 new private jobs per calendar month.

Business: $99/month for 200 new private jobs per calendar month.

The published trial is 14 days without a card, subject to current terms and credential requirements.

05

DocketServe Network

Network has a $0 subscription and is separate from Command. It is a growing Florida server roster used to understand qualified field capacity.

Participation does not guarantee assignments, volume, frequency or income.

06

iPhone status

The DocketServe web workspace is available now. DocketServe for iPhone is coming soon.

No public release date has been announced. App Store availability remains subject to Apple approval.

07

Public trust

DocketServe maintains dedicated Trust & Security, Accessibility and Release Notes pages.

Security and accessibility statements are published conservatively and do not claim certifications or conformance that have not been verified.

Structured current-facts file

The same operating facts are maintained in a structured public file for consistency across DocketServe publishing and release QA.

Open docketserve-facts.json

Core principles

Published information should help a reader make a better decision.

DocketServe pages should use the strongest available source, separate fact from judgment, make limitations visible and avoid generic filler that does not improve the reader's understanding.

01

Use the strongest available source

DocketServe facts are checked against current DocketServe product pages and terms. Competitor facts are checked against the competitor's own public materials when available. Local procedural facts are grounded in official court, county, city and agency sources whenever practical.

02

Separate fact from judgment

Pages may explain differences in workflow, scope, pricing or business model, but a preference should not be presented as a universal fact. If a public claim cannot be verified, it should not be presented as settled.

03

Write for the person using the page

Local pages should add meaningful service context. Comparison pages should help buyers evaluate real options. Product pages should explain what is included, what is not and what should be verified before acting.

Source hierarchy

What carries the most weight.

The closer a source is to the actual operator, publisher or official authority, the more weight it receives. When information is incomplete, the page should say so rather than fill the gap with assumptions.

1

DocketServe pricing, product and status facts

Preferred source: current DocketServe pricing, product, app and plan pages, plus the facts maintained on this page.

Current published terms control over older summaries, screenshots or prior messaging.

2

Florida service-law and court references

Preferred source: Florida Legislature, Florida Courts, judicial circuits, clerks and official court resources.

These sources support procedural context without turning DocketServe content into legal advice.

3

County and city research

Preferred source: county, municipality, clerk or agency sources.

Use these sources for geography, public offices and locally relevant context that helps prepare a service request.

4

Competitor capabilities and pricing

Preferred source: competitor websites, pricing pages, product documentation and official public materials.

Missing public information should be marked as unavailable rather than inferred.

Page standards

Different page types need different discipline.

A local service page should not read like a software comparison or a pricing page. The questions, supporting research and next action should match the job the page is doing for the reader.

Local pages

Useful local service context

City and county pages should add service-relevant information rather than only changing a place name.

  • Actual jurisdiction and local geography.
  • Address, access, property and corridor context where relevant.
  • Relevant courthouse or county information.
  • Clear next steps to prepare or submit the request.
Comparisons

Buyer research, not disguised rankings

Comparison pages should identify the provider's public positioning, business model and clearly visible differences that matter to the buyer.

  • Quote public pricing only when supported.
  • Keep material competitor strengths visible.
  • Use non-affiliation and trademark-respect language where appropriate.
Products & pricing

Clarity over shorthand

Pricing and product pages should explain what is included, what requires approval and what should not be assumed from a short summary.

  • Keep scope connected to price.
  • Make plan limits, timing and exclusions readable.
  • Align public copy with the current account and ordering experience.

Updates & corrections

Changing facts should change the canonical page.

Pricing, coverage, product scope, competitor information and local public information can change. The goal is to keep the current page aligned with the current fact rather than preserving stale wording.

1

Material changes are reviewed

When pricing, product terms, coverage positioning or notable external facts change, the affected page should be checked against the current source.

2

One current version controls

Current operating facts should be updated in the canonical source and then synchronized across pages that repeat them.

3

Corrections stay practical

A factual issue should be reported with the page URL, disputed statement and supporting first-party or official source when available.

Operational information, not legal advice.

When an answer depends on legal interpretation, court rules, venue strategy, filing deadlines or the validity of service under specific facts, readers should rely on applicable law, official court guidance or qualified legal counsel.