California Civil Stalking Civ. Code § 1708.7 attorney fee petition mechanics: DATE OF FIRST QUALIFYING STALKING ACT as primary Welch anchor (the ONLY primary anchor in the fee-petition-mechanics series proven through civil discovery of defendant's own carrier/device/platform metadata records across THREE DISTINCT INSTITUTIONAL CALENDARS — text message timestamps on defendant's cellular carrier CDR infrastructure calendar; GPS location data on defendant's device manufacturer cloud calendar; social media activity logs on platform server calendar — all created on defendant-controlled infrastructure entirely outside victim-plaintiff attorney's scheduling control and NOT KNOWN to plaintiff at time of occurrence; distinct from CIPA DATE OF INTERCEPTED COMMUNICATION [blog #69] where a single defendant server logs the covert interception; distinct from every court filing date, every government-authored notice, every bilateral contract execution date, and every plaintiff's own physical site visit in the series), § 1708.7(b) mandatory "the court SHALL AWARD" attorney fees to prevailing plaintiff, § 1708.7(d) treble punitive damages if defendant convicted under Pen. Code § 646.9, Pen. Code § 646.9 DA criminal prosecution calendar, CCP § 527.6 civil harassment TRO court calendar, carrier/platform legal compliance production calendar, Hensley lodestar segregation between § 527.6 TRO hours and § 1708.7 civil damages hours, and pure Ketchum multiplier advisory (VAWA § 13981 struck down United States v. Morrison (2000) 529 U.S. 598 — no federal civil stalking parallel — no City of Burlington v. Dague 505 U.S. 557 (1992) no-multiplier constraint)

The § 1708.7(a) pattern of conduct analysis, carrier/device/platform metadata discovery and preservation advisory, and § 1708.7(b) mandatory fee advisory at the DATE OF FIRST QUALIFYING STALKING ACT: 5.39 untracked hours = $1,617–$2,695/year

The DATE OF FIRST QUALIFYING STALKING ACT — the date on which the defendant committed the first of at least two acts constituting the required pattern of conduct under Civ. Code § 1708.7(a)(1) — is the primary Welch temporal anchor for California Civil Stalking attorney fee billing documentation. California civil stalking § 1708.7 practice is the ONLY practice area in the fee-petition-mechanics series where the primary Welch anchor is proven through civil discovery of defendant's own metadata records across THREE DISTINCT INSTITUTIONAL CALENDARS — (1) the defendant's cellular carrier's CDR infrastructure, (2) the defendant's device manufacturer's cloud infrastructure, and (3) the defendant's social media platform's server infrastructure — each owned and operated by an independent institutional entity, each maintaining its own data retention and legal compliance architecture, and each requiring an independent civil subpoena or legal process request that is processed on the institution's own legal compliance calendar entirely outside the victim-plaintiff attorney's contemporaneous scheduling control.

Civ. Code § 1708.7(a) defines the elements of the civil stalking tort. A person is liable for the tort of stalking when the plaintiff proves all of the following elements: (1) the defendant engaged in a pattern of conduct — a course of conduct defined as a series of acts over a period of time, however short — the intent of which was to follow, alarm, place under surveillance, or harass the plaintiff; in proving the pattern of conduct, the plaintiff must establish that the pattern included at least two acts by the defendant with the requisite intent; (2) as a result of that pattern of conduct, the plaintiff reasonably feared for their safety or the safety of an immediate family member; and (3) one of the following: (A) the defendant made a credible threat with the intent to place the plaintiff in reasonable fear for their safety, or (B) the defendant violated a restraining order, including a temporary restraining order, a restraining order, an injunction, or any other court order prohibiting any act described in subdivision (a).

Three distinct institutional calendars for the DATE OF FIRST QUALIFYING STALKING ACT. The DATE OF FIRST QUALIFYING STALKING ACT generates metadata across three independent institutional calendars simultaneously. The plaintiff's attorney learns the exact date only through civil discovery production from each institutional source. First institutional calendar — cellular carrier CDR: when the defendant sends a harassing text message, makes a surveillance call, or activates a call-forwarding or spoofing service as part of the stalking pattern, the defendant's cellular carrier records the transmission event in the carrier's Call Detail Record (CDR) database. CDRs contain the originating number, the terminating number or message recipient, the date and time stamp of the transmission (in UTC or carrier-local time), the call duration or message send/receive status, and for some carriers, the cell tower ID associated with the transmission event. AT&T, Verizon, T-Mobile, and regional carriers maintain CDR data on their own network operations infrastructure for billing, regulatory compliance, and law enforcement compliance purposes on the carrier's own institutional calendar. The CDR timestamp for the first qualifying stalking text message or call is embedded in the carrier's CDR database at the moment of transmission — entirely outside the victim-plaintiff attorney's scheduling control and NOT KNOWN to the plaintiff at the moment it occurs. Production requires a civil subpoena served on the carrier's legal compliance department, processed by the carrier on the carrier's own legal compliance workflow calendar (typically 4–6 weeks after service).

Second institutional calendar — device manufacturer cloud: when the defendant uses their smartphone's GPS to track the plaintiff's location (through a location-sharing app, a covertly installed tracking app, or the device's native location services), the defendant's device manufacturer logs the GPS location fix, the timestamp, and the device identifier in the device manufacturer's cloud infrastructure. Apple stores device location history in iCloud (including location data from the Find My network, Maps searches, and location services used by apps on the defendant's device) on Apple's own iCloud server infrastructure on Apple's institutional calendar. Google stores Android device location history in Google Maps Timeline and Google Account activity data on Google's own server infrastructure on Google's institutional calendar. Samsung stores additional telemetry in Samsung SmartThings and Samsung account cloud on Samsung's own infrastructure. Third-party location-sharing apps (Life360, Find My Friends, Google Family Sharing) maintain their own server-side activity logs on their own institutional calendars. The GPS fix timestamps in the device manufacturer's cloud record the exact time and coordinates of the defendant's location surveillance acts at the moment they occur — entirely outside the victim-plaintiff attorney's scheduling control and NOT KNOWN to the plaintiff at the moment they occur. Production requires civil legal process to the device manufacturer's law enforcement/legal process response team (Apple Legal Process — requests processed on Apple's own team calendar; Google Law Enforcement Request System — processed on Google's calendar; Samsung Legal Department), or a civil subpoena to the third-party location-sharing app's legal compliance department.

Third institutional calendar — social media platform server: when the defendant sends harassing direct messages, monitors the plaintiff's social media accounts, creates impersonation profiles, or posts threatening content as part of the stalking pattern, each platform's own server-side infrastructure records the activity timestamp in the platform's own database on the platform's own institutional calendar. Meta (Instagram, Facebook) stores DM timestamps, account access logs, and content delivery metadata in Meta's server infrastructure on Meta's own calendar — accessed through Meta's Law Enforcement Online Request System (LERS) for preservation requests and through the civil subpoena process for production. Twitter/X stores tweet timestamps, DM metadata, and account access logs in X Corp.'s server infrastructure on X Corp.'s own calendar — accessed through Twitter/X's legal support portal. Snapchat stores snap send/receive timestamps and account data in Snap Inc.'s server infrastructure on Snap's own calendar — accessed through Snap's law enforcement guide procedures. TikTok stores account activity logs, DM metadata, and video creation timestamps in TikTok Inc.'s server infrastructure on TikTok's own calendar — accessed through TikTok's law enforcement portal. Each platform processes civil subpoenas on its own legal compliance department calendar, entirely outside the plaintiff attorney's scheduling control.

§ 1708.7(a) pattern analysis advisory. The advisory call cycle at the DATE OF FIRST QUALIFYING STALKING ACT covers two distinct categories. First: § 1708.7(a)(1) qualifying act identification — which of the defendant's acts constitute the required course of conduct? The advisory covers the full taxonomy of qualifying acts under § 1708.7(a)(1): physical following (defendant physically follows plaintiff to work, residence, or other locations — documented through plaintiff's own contemporaneous logs and potentially through security camera footage); electronic surveillance acts (defendant monitors plaintiff's social media accounts, uses location tracking apps, installs GPS tracker on plaintiff's vehicle); cross-platform messaging (defendant sends harassing messages through multiple platforms — Instagram DMs, text messages, Twitter DMs, email — the multi-platform pattern is particularly relevant because it creates metadata on all three institutional calendars simultaneously). Second: carrier/device/platform preservation and subpoena strategy advisory — the advisory covers the critical 90-day CDR data preservation window (some carriers retain CDR data for only 90 days in rolling retention; preservation letters must be sent to the carrier immediately after representation begins to stop the 90-day clock from rolling off the first qualifying act metadata); device manufacturer cloud preservation requests (Apple, Google, Samsung offer law enforcement preservation request procedures that can be used for civil matters in some circumstances, or alternatively a preliminary injunction to preserve electronically stored information can be obtained from the California Superior Court directed at the manufacturer before expiration of the applicable retention window); and social media platform preservation requests (Meta, Twitter/X, Snap, TikTok maintain preservation request procedures that hold the account data pending legal process — preservation must be requested as soon as representation begins to prevent deletion by the defendant or platform data retention policies). Arithmetic: 7 clients × 2 calls × 42 min × 55% = 5.39 hrs = $1,617–$2,695/year at $300–$500/hr.

The DA Pen. Code § 646.9 criminal prosecution calendar, CCP § 527.6 civil harassment TRO court calendar, and carrier/platform legal compliance production calendar advisory call cycle: 7.26 untracked hours = $2,178–$3,630/year

California civil stalking § 1708.7 practice generates three concurrent externally-controlled institutional calendars that operate independently of each other and of the civil damages action timeline — the District Attorney's Pen. Code § 646.9 criminal prosecution calendar (DA's own prosecutorial institutional schedule entirely outside civil plaintiff attorney scheduling control), the CCP § 527.6 civil harassment restraining order court calendar (court's own scheduling calendar for TRO, preliminary injunction, and permanent restraining order hearings entirely outside plaintiff attorney scheduling control), and the carrier/device/platform legal compliance production calendar (three independent legal compliance departments processing three independent civil subpoenas on three independent institutional legal compliance workflow timelines entirely outside plaintiff attorney scheduling control). Ketchum v. Moses (2001) 24 Cal.4th 1122. PLCM Group Inc. v. Drexler (2000) 22 Cal.4th 1084. Hensley v. Eckerhart (1983) 461 U.S. 424. Missouri v. Jenkins (1989) 491 U.S. 274.

DA Pen. Code § 646.9 criminal prosecution calendar. California Penal Code § 646.9 makes criminal stalking a felony or misdemeanor depending on circumstances — following, harassing, and threatening another person with the intent to place that person in reasonable fear for their safety. The DA's decision to file § 646.9 charges, the criminal court's arraignment and preliminary hearing schedule, any plea bargain negotiations, and the criminal trial all run on the DA's own prosecutorial calendar and the criminal court's own master calendar, entirely outside the civil plaintiff attorney's scheduling control. Advisory calls arrive at three DA calendar decision points. First, the DA filing decision: when the DA decides to file § 646.9 criminal stalking charges against the defendant, the criminal charging document identifies specific charged stalking acts — these may overlap with the § 1708.7(a) civil pattern of conduct, and the filing date of the charging document arrives on the DA's own calendar (not the civil plaintiff attorney's calendar); advisory covers whether the criminal charging document's factual allegations corroborate the § 1708.7(a) pattern of conduct, how the criminal proceeding affects civil discovery (the defendant may invoke the Fifth Amendment in civil depositions while criminal charges are pending, potentially delaying the civil damages action), and whether a stay of the civil action should be sought pending the criminal proceedings. Second, the § 646.9 conviction: if the DA obtains a § 646.9 conviction of the defendant (whether by jury verdict, bench trial verdict, or guilty plea), the conviction date arrives on the criminal court's calendar entirely outside the civil plaintiff attorney's scheduling control; the § 646.9 conviction triggers § 1708.7(d) — "If the defendant was convicted of a crime of violence against the plaintiff, the court shall, upon request of the plaintiff, award treble punitive damages" — meaning the plaintiff's attorney must request treble punitive damages in the civil action based on the § 646.9 conviction; advisory covers the timing and mechanism of the § 1708.7(d) treble punitive damages request relative to the criminal conviction date and the civil trial schedule; the conviction can be obtained before or after the civil trial (if obtained before civil trial, it is admissible as evidence of civil liability; if obtained after civil judgment, a supplemental § 1708.7(d) motion may be required). Third, the DA declination: when the DA declines to prosecute § 646.9 or dismisses the criminal case, the declination date generates advisory calls about civil strategy — the absence of criminal prosecution does not bar civil recovery under § 1708.7 (the civil burden of proof is preponderance of the evidence, not beyond reasonable doubt); a DA declination may strengthen the CCP § 1021.5 private attorney general fee petition argument that private civil enforcement was necessary to vindicate the victim's rights when the DA declined to act.

CCP § 527.6 civil harassment TRO court calendar. Code of Civil Procedure § 527.6 provides an expedited civil harassment restraining order procedure entirely independent of the § 1708.7 civil stalking damages action. A victim of harassment (including stalking) may petition for a temporary restraining order (TRO) to be issued ex parte immediately upon application, with a noticed hearing typically scheduled within 21 days under § 527.6(g). The § 527.6 TRO application date, the TRO grant or denial date (typically within one court day of application), the noticed hearing date, and any preliminary injunction or permanent restraining order hearing dates all run on the civil court's own scheduling calendar, set by the court's master calendar department, entirely outside the plaintiff attorney's scheduling control beyond the initial application filing date. Advisory calls arrive when: (a) the court issues the TRO ex parte — the TRO issuance date is set by the court's own issuance procedures; advisory covers preserving the evidence supporting the TRO application for use in the § 1708.7 civil damages action (the same stalking acts that supported the TRO application form part of the § 1708.7(a)(1) pattern of conduct); (b) the noticed hearing is held — the court schedules the noticed hearing and the defendant is served; the defendant's response to the restraining order (compliance or violation) generates additional advisory calls; if the defendant violates the TRO, the violation is both a contempt of court and a potential § 1708.7(a)(3)(B) predicate act (one of the alternative third elements of civil stalking); (c) the court modifies or terminates the restraining order — modifications and terminations are set by the court on the court's own scheduling calendar; advisory covers how restraining order modifications affect the § 1708.7 civil damages case strategy.

Carrier/device/platform legal compliance production calendar. When the plaintiff's attorney serves civil subpoenas on the cellular carrier (AT&T, Verizon, T-Mobile, or regional carrier), the device manufacturer (Apple, Google, Samsung, or third-party location app provider), and the social media platforms (Meta, Twitter/X, Snap, TikTok), each institution's legal compliance department processes the subpoena on its own internal legal compliance calendar. AT&T, Verizon, and T-Mobile each maintain separate legal compliance / law enforcement support divisions that receive civil subpoenas and process them according to the carrier's own internal procedures and capacity; production timelines typically run 4–6 weeks from the date of valid service, but may be extended if the subpoena is challenged (carriers may move to quash civil subpoenas that do not comply with California Penal Code § 1524.3's restrictions on subscriber information), meaning the production date arrives on the carrier's legal compliance calendar entirely outside plaintiff attorney scheduling control. Apple's law enforcement/legal process team processes civil legal process requests (such as California Superior Court subpoenas backed by civil discovery orders) on Apple's own legal team calendar; production format for iCloud location data is typically a JSON-formatted archive of location data points. Google's Law Enforcement Request System processes civil legal process requests for Google account data (including Google Maps Timeline, Google location history, and Gmail) on Google's own legal team calendar. Meta's LERS processes civil subpoenas for Instagram and Facebook Messenger account data on Meta's own processing queue calendar; Meta returns data in a structured ZIP archive format. Twitter/X, Snap, and TikTok each have their own legal support portals and their own processing timelines on their own legal compliance calendars. Advisory calls arrive when each institution completes production and delivers the data: the plaintiff attorney must immediately audit the produced metadata to identify the DATE OF FIRST QUALIFYING STALKING ACT and each subsequent qualifying stalking act across all three institutional calendar sources, correlate the timestamps across carrier CDR, device location history, and platform DM records to reconstruct the full pattern of conduct, and prepare the corroborated pattern-of-conduct timeline for use in the § 1708.7 civil complaint and the Welch lodestar documentation.

The unique billing gap driven by three concurrent external institutional calendars: California civil stalking § 1708.7 practice generates advisory calls on three entirely independent institutional calendars — the DA's prosecutorial calendar, the civil harassment court's scheduling calendar, and three carrier/device/platform legal compliance production calendars — making § 1708.7 practice the only practice area in the fee-petition-mechanics series where the second billing gap involves advisory calls on potentially five independent institutional calendars running in parallel (DA calendar + civil court calendar + carrier legal compliance calendar + device manufacturer legal compliance calendar + social platform legal compliance calendar). Arithmetic: 6 clients × 3 calls × 44 min × 55% = 7.26 hrs = $2,178–$3,630/year at $300–$500/hr.

The § 1708.7(b) mandatory "shall award" fee petition + § 1708.7(d) treble punitive damages advisory + § 527.6 Hensley lodestar segregation + pure Ketchum multiplier (VAWA § 13981 struck down Morrison 2000 — no federal civil stalking parallel — no Dague constraint) advisory call cycle: 4.03 untracked hours = $1,210–$2,017/year

California Civil Stalking § 1708.7 creates a structurally distinctive fee petition landscape for two compounding reasons: (1) § 1708.7(b) uses the strongest mandatory fee language in the fee-petition-mechanics series — "the court shall award reasonable attorney's fees to a prevailing plaintiff" — and (2) the complete absence of any surviving federal civil stalking parallel after United States v. Morrison (2000) 529 U.S. 598 struck down VAWA § 13981 means the § 1708.7(b) fee petition in California Superior Court is purely Ketchum multiplier eligible without any City of Burlington v. Dague (1992) 505 U.S. 557 no-multiplier constraint. Together, these two features create a fee petition environment where the plaintiff's attorney faces no discretionary denial risk (because the "shall award" mandate eliminates judicial discretion) and no Dague segregation burden (because no federal fee petition track exists).

§ 1708.7(b) mandatory "shall award" language. The fee mandate in § 1708.7(b) reads: "A person who is liable under this section shall be liable for reasonable attorney's fees to a prevailing plaintiff." The use of "shall" — not "may," not "is entitled to," not "at the court's discretion" — eliminates the trial court's discretion to deny fees to a prevailing plaintiff. This distinguishes § 1708.7(b) from discretionary fee statutes (such as the PAGA § 2699(g)(1) fee award, which is awarded "in the discretion of the appeals board" in WCAB proceedings) and from asymmetric mandatory fee statutes (such as FEHA § 12965(b), where Christiansburg Garment Co. v. EEOC (1978) 434 U.S. 412 limits the prevailing defendant's fee recovery to cases where the plaintiff's action was frivolous, unreasonable, or without foundation). In § 1708.7(b) civil stalking practice, a prevailing plaintiff is entitled to mandatory attorney fees as a matter of law. The "shall award" mandate does not, however, eliminate the burden of documenting the lodestar: the court must still determine the reasonable number of hours and the prevailing market rate under PLCM Group Inc. v. Drexler (2000) 22 Cal.4th 1084. The key lodestar documentation obligation in § 1708.7(b) fee petitions is anchoring the lodestar to the DATE OF FIRST QUALIFYING STALKING ACT under Hensley v. Eckerhart (1983) 461 U.S. 424 — not to the civil complaint filing date. Hours spent analyzing the § 1708.7(a) pattern of conduct, issuing carrier CDR preservation letters, drafting device manufacturer and social platform legal process requests, auditing CDR/location/DM metadata, and preparing the civil complaint based on the documented pattern are all causally connected to the § 1708.7(b) mandatory fee claim from the DATE OF FIRST QUALIFYING STALKING ACT. A fee petition that begins the lodestar at the complaint filing date misses the pre-filing carrier preservation letters, device manufacturer legal process preparation, social platform subpoena strategy, and metadata audit hours — all of which are compensable under § 1708.7(b) from the DATE OF FIRST QUALIFYING STALKING ACT.

VAWA § 13981 struck down Morrison (2000) — no federal civil stalking parallel — pure Ketchum. In United States v. Morrison (2000) 529 U.S. 598, the Supreme Court held by a 5–4 margin that Congress lacked authority under the Commerce Clause or Section 5 of the Fourteenth Amendment to enact 42 U.S.C. § 13981, which had provided a federal civil right of action for victims of gender-motivated violence, including stalking. After Morrison, no federal civil stalking remedy exists: 18 U.S.C. § 2261A (federal criminal stalking) creates criminal liability prosecuted by the US Attorney but provides no private right of action. The VAWA reauthorizations since Morrison have restored other provisions (housing protections, immigration remedies, grant programs) but have not and cannot (under Commerce Clause constraints identified in Morrison) restore the § 13981 civil damages remedy. The practical consequence for § 1708.7(b) fee petitions: in California Superior Court, a prevailing plaintiff bringing a California civil stalking § 1708.7 claim has no federal parallel claim creating a Dague-track fee petition. In Ketchum v. Moses (2001) 24 Cal.4th 1122, the California Supreme Court held that California courts may apply a positive multiplier to the lodestar in appropriate cases based on contingency risk. The contingency factors relevant to the DATE OF FIRST QUALIFYING STALKING ACT include: (a) pattern identification uncertainty — at the DATE OF FIRST QUALIFYING STALKING ACT, the plaintiff's attorney could not know how many qualifying stalking acts the defendant had committed, whether the defendant's acts would be found to constitute a "pattern of conduct" (requiring at least two qualifying acts), or whether the defendant's conduct would satisfy the § 1708.7(a)(1) intent element; (b) metadata availability uncertainty — at the DATE OF FIRST QUALIFYING STALKING ACT, the plaintiff's attorney could not know whether carrier CDR data had been preserved (90-day rolling retention), whether the defendant had disabled device location services (eliminating the device manufacturer cloud evidence), or whether the defendant had deactivated social media accounts (destroying platform metadata); (c) § 1708.7(a)(3) third-element uncertainty — at the DATE OF FIRST QUALIFYING STALKING ACT, the plaintiff's attorney could not know whether a credible threat element would be provable under § 1708.7(a)(3)(A) or whether a § 527.6 TRO violation would occur under § 1708.7(a)(3)(B); (d) § 1708.7(d) treble punitive uncertainty — at the DATE OF FIRST QUALIFYING STALKING ACT, the plaintiff's attorney could not know whether the DA would charge § 646.9, whether a criminal conviction would be obtained, or whether the criminal proceeding would conclude before or after the civil judgment.

§ 527.6 Hensley task-level segregation. When the victim simultaneously pursues a CCP § 527.6 civil harassment restraining order (an expedited summary proceeding focused on injunctive relief) and a Civ. Code § 1708.7 civil stalking damages action (a full civil trial on liability and damages), Hensley v. Eckerhart (1983) 461 U.S. 424 task-level segregation applies. Section 527.6 does not provide a mandatory attorney fee award to a prevailing petitioner in the same terms as § 1708.7(b). Code of Civil Procedure § 527.6(s) permits attorney fee awards but does not use "shall award" mandatory language — the § 527.6 fee award is discretionary based on findings of bad faith by the respondent. This means § 527.6 TRO preparation hours are NOT automatically compensable under the § 1708.7(b) mandatory fee petition unless there is a direct causal connection between the § 527.6 TRO work and the § 1708.7 damages claim. Specific segregation analysis covers: (1) § 527.6 TRO application drafting hours — these are primarily § 527.6 proceeding hours; they are compensable under § 1708.7(b) only if the same factual evidence in the TRO application was directly used in the § 1708.7 civil damages complaint and trial; (2) § 527.6 TRO hearing preparation hours — these are § 527.6 proceeding hours; compensable under § 1708.7(b) only to the extent the § 527.6 hearing established facts (testimony, documentary evidence) that were directly used in the § 1708.7 civil trial; (3) § 527.6 restraining order monitoring hours — monitoring the defendant's compliance with the § 527.6 TRO is primarily § 527.6 work; compensable under § 1708.7(b) only to the extent any TRO violation was used as the § 1708.7(a)(3)(B) predicate act; (4) carrier CDR and platform metadata discovery hours — these are dual-purpose hours: the carrier CDRs and platform metadata sought for the § 1708.7(a) pattern-of-conduct analysis may also have been needed for the § 527.6 TRO evidentiary support, creating a shared-purpose hour analysis under Hensley (hours that contributed to both the § 527.6 and the § 1708.7 claims are generally fully compensable under § 1708.7(b) if the § 1708.7 mandatory fee claim is the principal cause of the work).

Missouri v. Jenkins (1989) 491 U.S. 274 fees-on-fees: hours spent preparing and litigating the § 1708.7(b) fee petition itself are compensable and must be logged with the fee petition preparation date as the secondary anchor. At 55% untracked: 5 clients × 2 calls × 44 min × 55% = 4.03 hrs = $1,210–$2,017/year at $300–$500/hr.