California Equitable Indemnity Attorney Fee Petition Mechanics: Subcontract Execution Date in General Contractor's Project Management System as Primary Welch Anchor, CCP § 1021.6 Discretionary Attorney Fees
California Code of Civil Procedure § 1021.6, California's equitable indemnity attorney fee statute, provides that upon motion a court may award attorney's fees to an indemnitee who prevails in an action which would have been covered by an indemnity agreement if the court finds three conjunctive conditions satisfied: (1) the indemnitee was found not liable on the underlying claim; (2) the indemnitor had a duty to indemnify the indemnitee; and (3) the indemnitee was required to defend the underlying claim because of the indemnitor's conduct — making § 1021.6 a discretionary but Ketchum-eligible fee provision uniquely tied to the three-part trifecta of successful indemnity defense. Section 1021.6 is the governing fee provision in construction defect litigation — the largest and most common context — where general contractors seek equitable indemnity from subcontractors after homeowners or owners sue the general contractor for foundation cracking, water intrusion, HVAC failures, or other construction defects attributable to the subcontractor's scope of work; premises owners seek equitable indemnity from maintenance contractors or service contractors after slip-and-fall or premises liability plaintiffs prevail; design-build entities seek equitable indemnity from engineering or specialty design subcontractors after project owners assert design defect claims; and product liability defendants seek equitable indemnity from component suppliers after downstream product liability claims are resolved. The statute also applies in commercial real estate, where landlords seek equitable indemnity from tenant businesses whose operations caused the underlying premises liability or property damage claim. The primary Welch anchor — the earliest objective institutional timestamp that starts the lodestar period under Hensley v. Eckerhart (461 U.S. 424 (1983)) — is the SUBCONTRACT EXECUTION DATE RECORDED IN THE GENERAL CONTRACTOR'S PROJECT MANAGEMENT SYSTEM: the Procore Construction Project Management subcontract execution date and certificate of substantial completion date, the Autodesk Build (formerly BIM 360 Field) subcontract award date and Notice to Proceed date, the CMiC Construction Project Management subcontract execution timestamp and scope of work commencement date, the Oracle Primavera P6/Contract Management subcontract execution date and project milestone dates, or the Sage 300 Construction and Real Estate subcontract execution date, completion percentage dates, and final payment application date — each an institutional timestamp recorded in the general contractor's proprietary project management platform entirely outside the indemnitee attorney's scheduling control, existing as a permanent record in the project management database from the moment the subcontract is executed. This is THE ONLY PAGE in the fee-petition-mechanics series where the PRIMARY CLAIM IS RECOVERY OF ATTORNEY FEES BY A PREVAILING INDEMNITEE from an indemnitor under CCP § 1021.6 in an equitable indemnity action — distinct from Civ. Code § 1717 contractual fee clause enforcement (§ 1717 enforces a contractual fee clause; § 1021.6 shifts fees from the indemnitor to the indemnitee when the indemnitee was required to defend because of the indemnitor's conduct), distinct from CCP § 128.5 frivolous conduct sanctions (court-imposed sanctions for litigation misconduct, not post-indemnity-action fee recovery), distinct from general negligence attorney fee recovery under the American Rule (no fee shifting without statute or contract — § 1021.6 is the specific indemnity-based exception), and distinct from Civ. Code § 2782 anti-indemnity (§ 2782 voids indemnity provisions for contractor's own negligence; § 1021.6 addresses fee recovery after indemnity is determined). This is THE ONLY PAGE where the PRIMARY DEFENDANT IS AN INDEMNITOR — a subcontractor, component supplier, maintenance contractor, tenant, or design professional whose contractual indemnification duty was triggered by the underlying plaintiff's claim and who failed to accept tender of defense: specifically concrete subcontractors who declined tender after homeowners sued the general contractor for foundation cracking, roofing subcontractors who rejected tender after water intrusion lawsuits, HVAC subcontractors who refused tender after building fires claimed to originate from their mechanical work, component suppliers who contested tender after product liability claims, and tenant businesses that contested indemnity after slip-and-fall incidents in leased premises. And this is THE ONLY PAGE where the PRIMARY WELCH ANCHOR IS IN THE GENERAL CONTRACTOR'S PROJECT MANAGEMENT SYSTEM SUBCONTRACT EXECUTION DATE — Procore/Autodesk Build/CMiC/Oracle Primavera/Sage 300 records the subcontract execution date, Notice to Proceed date, and certificate of substantial completion date on the general contractor's institutional project management platform entirely outside the indemnitee or third-party plaintiff attorney's scheduling control, making it the Welch v. Metropolitan Life Ins. Co. (480 F.3d 942 (9th Cir. 2007)) institutional anchor from which the lodestar period commences. CCP § 1021.6 is PURE KETCHUM: no federal equitable indemnity statute provides attorney fee-shifting with a multiplier; the federal Contractor Disputes Act (41 U.S.C. § 7101) covers government contract disputes before the Armed Services or Civilian Board of Contract Appeals and provides no private-party equitable indemnity fee provision; FAR Part 31 indirect cost rules for federal contractors do not create a private fee-shifting right; no concurrent federal fee-shifting statute; no Dague constraint; no Hensley segregation required for pure California equitable indemnity claims. The § 1021.6 fee petition lodestar begins at the subcontract execution date in the general contractor's project management system — the moment the indemnification relationship was established between the general contractor-indemnitee and the subcontractor-indemnitor — and the billing gaps compound across three identifiable task categories: subcontract indemnity clause analysis and anti-indemnity statute review, Procore/Autodesk Build project records cross-referencing and tender-of-defense timeline coordination, and § 1021.6 fee motion preparation after prevailing on the indemnity claim. Across those three categories, a solo attorney handling California § 1021.6 equitable indemnity construction defect cases loses approximately 16.68 untracked billable hours per year — equal to $5,005–$8,342 annually at median California solo practitioner rates.
TL;DR
CCP § 1021.6 awards discretionary attorney fees to a prevailing indemnitee in equitable indemnity actions — pure Ketchum, no Dague constraint, no federal analog. Primary Welch anchor: subcontract execution date in the general contractor's project management system (Procore, Autodesk Build, CMiC, Oracle Primavera P6, Sage 300). The three-part § 1021.6 trifecta (not liable + duty existed + indemnitor's conduct required defense) must be documented from the subcontract execution date forward. Three billing gaps total 16.68 hrs = $5,005–$8,342/yr untracked.
Billing Gap 1 — Subcontract Indemnity Clause Analysis and Anti-Indemnity Statute Review (5.39 hrs/yr = $1,617–$2,695)
The first billing gap arises from time spent reviewing the subcontract indemnity clause scope, researching the indemnitor's scope of work overlap with the underlying plaintiff's claim, and analyzing the California anti-indemnity statute (Civ. Code § 2782) exceptions for construction contracts. This analysis is the foundational work of every § 1021.6 case and generates brief, unscheduled review sessions that accumulate outside calendar-triggered billing systems.
The subcontract indemnity clause analysis requires: (1) obtaining the full subcontract from the general contractor's Procore, CMiC, or Sage 300 project file — the subcontract execution date in the project management system is the Welch anchor establishing the start of the indemnification obligation; (2) parsing the indemnity clause scope to determine whether it covers the type of claim the underlying plaintiff asserted — construction defect indemnity clauses commonly cover bodily injury, property damage, and design defects arising from the subcontractor's work, but their precise scope varies by subcontract form (AIA A401, ConsensusDocs 750, or custom forms); (3) analyzing Civ. Code § 2782, California's anti-indemnity statute, which voids indemnity provisions in construction contracts to the extent they require a contractor to indemnify another party for that other party's own negligence — the § 2782 analysis is essential before tendering defense or pursuing § 1021.6 fees because a void indemnity clause eliminates the § 1021.6 duty-to-indemnify element; (4) reviewing the Civ. Code § 2782 exceptions: § 2782(b) allows indemnity from subcontractor to general contractor where the subcontract is for residential construction (Type I residential construction exception); § 2782(c) applies different rules for design professionals; (5) mapping the indemnitor's specific scope of work — as recorded in the subcontract's scope-of-work exhibit in Procore or CMiC — against the underlying plaintiff's allegations to determine whether the § 1021.6 element of indemnitor's conduct requiring defense is satisfied. The subcontract execution date in the project management system is the Welch anchor from which all subsequent billing time traces, because it is the date on which the indemnification relationship was established, recorded on the general contractor's institutional platform entirely outside the indemnitee attorney's scheduling control.
The § 1021.6 fee petition must document the lodestar from the subcontract execution date in the general contractor's project management system. Under Missouri v. Jenkins (491 U.S. 274 (1989)), time spent preparing the fee petition itself is compensable (fees-on-fees), extending the lodestar period through the petition filing date. The Procore/CMiC/Sage 300 subcontract records — obtaining through discovery or general contractor file access — provide the institutional timestamp anchoring all subsequent billing.
Billing Gap 2 — Procore/Autodesk Build Project Records Cross-Referencing and Tender-of-Defense Timeline Coordination (7.26 hrs/yr = $2,178–$3,630)
The second billing gap arises from time spent cross-referencing the Procore, Autodesk Build, CMiC, or Oracle Primavera project records for the subcontract execution date, certificate of substantial completion, and change orders that expanded scope; coordinating with the underlying plaintiff's counsel and the tender-of-defense letter timeline; and analyzing whether the indemnitor's conduct triggered the duty to defend in the underlying action. This is the most time-intensive billing gap category in § 1021.6 practice because the indemnitor's conduct analysis requires reconstructing the project timeline from the general contractor's project management system records.
The project records cross-referencing analysis requires: (1) obtaining the complete Procore or Autodesk Build project file — subcontract execution date, Notice to Proceed date, all change orders affecting the indemnitor's scope, daily reports, inspection records, and certificate of substantial completion — all recorded on the general contractor's institutional project management platform on the general contractor's project timeline entirely outside the indemnitee attorney's scheduling control; (2) analyzing the change order history to determine whether any change orders expanded the indemnitor-subcontractor's scope of work to include the work alleged to have caused the underlying plaintiff's claim — change orders are time-stamped in Procore and CMiC on the date executed, entirely outside attorney scheduling control; (3) coordinating the tender-of-defense letter timeline with the underlying plaintiff's claim — the § 1021.6 element that the indemnitee was required to defend because of the indemnitor's conduct requires establishing: when the underlying plaintiff sued the general contractor-indemnitee, when the general contractor-indemnitee tendered the defense to the subcontractor-indemnitor, when the indemnitor rejected or failed to respond to the tender, and whether the indemnitee was thereafter required to defend the underlying claim through judgment or settlement; (4) analyzing whether the indemnitor's specific scope of work — as documented in the project management system — overlapped with the area where the underlying plaintiff claims the defect or injury occurred; (5) reviewing the daily logs and inspection records in Procore or Autodesk Build for the indemnitor's subcontracted work area around the date of the alleged defect or incident. The Procore/Autodesk Build/Oracle Primavera P6 project records are institutional documents recorded on the general contractor's project management platform entirely outside the indemnitee attorney's scheduling control — each project milestone date recorded in those systems constitutes a secondary Welch anchor subordinate to the primary subcontract execution date anchor.
The tender-of-defense letter is a critical institutional document in every § 1021.6 case: it establishes the date on which the indemnitee formally demanded that the indemnitor accept the defense of the underlying claim, and the indemnitor's rejection of or failure to respond to the tender is essential to the § 1021.6 element that the indemnitee was "required to defend" because of the indemnitor's conduct. The tender-of-defense letter date appears on the indemnitee's own document management system and the indemnitor's rejection appears on the indemnitor's own business calendar — both entirely outside the indemnitee attorney's scheduling control as secondary institutional anchors subordinate to the primary Procore/CMiC subcontract execution date anchor.
Billing Gap 3 — CCP § 1021.6 Fee Motion Preparation After Prevailing on Indemnity Claim (4.03 hrs/yr = $1,210–$2,017)
The third billing gap arises from preparing the CCP § 1021.6 fee motion after prevailing on the indemnity claim: establishing the lodestar from the subcontract execution date as Welch anchor, documenting the trifecta of § 1021.6 requirements (not liable, duty existed, indemnitor's conduct required defense), and applying the Ketchum pure-California multiplier analysis. Because § 1021.6 is discretionary — the court "may" award fees upon finding the trifecta satisfied — the fee motion must both establish the trifecta and persuade the court to exercise its discretion in the indemnitee's favor, generating more complex petition preparation than mandatory fee statutes.
The § 1021.6 fee motion preparation requires: (1) establishing the § 1021.6 trifecta from the evidentiary record — the indemnitee was found not liable on the underlying claim (evidenced by judgment or settlement with express no-liability finding), the indemnitor had a contractual duty to indemnify (established by the subcontract indemnity clause surviving the § 2782 anti-indemnity analysis), and the indemnitee was required to defend the underlying claim because of the indemnitor's conduct (established by the tender-of-defense rejection and the indemnitor's scope of work overlap with the underlying claim); (2) building the lodestar from the subcontract execution date in the general contractor's Procore/CMiC/Sage 300 project management system — the earliest Welch anchor — through the § 2782 anti-indemnity analysis, the project records review, the tender-of-defense coordination, the underlying litigation monitoring, the indemnity claim litigation, and the § 1021.6 fee motion; (3) applying the pure Ketchum multiplier analysis under Ketchum v. Moses (24 Cal.4th 1122 (2001)) and PLCM Group Inc. v. Drexler (22 Cal.4th 1084 (2000)): no Dague constraint exists for § 1021.6 (no federal analog), so the full five-factor Ketchum analysis applies — contingency risk (indemnitee attorney took on the § 1021.6 claim knowing that the court has discretion to deny fees even if the trifecta is established), novelty of the indemnity theory (subcontract scope overlap and § 2782 anti-indemnity exception analysis), result obtained (complete recovery of defense costs from indemnitor), preclusion of other work, and experience and reputation; (4) documenting Missouri v. Jenkins (491 U.S. 274 (1989)) fees-on-fees: the attorney time spent preparing the § 1021.6 fee motion is itself compensable and included in the fee petition lodestar. Because § 1021.6 is discretionary rather than mandatory, the fee motion must additionally persuade the court to exercise its discretion to award fees — a briefing task distinct from the lodestar documentation task.
Under Ketchum v. Moses (24 Cal.4th 1122 (2001)), the trial court may enhance the lodestar for contingency risk in § 1021.6 cases — particularly compelling where the indemnitee attorney accepted the equitable indemnity claim knowing that the court retains discretion to deny fees even after the trifecta is established, and where the subcontract indemnity clause's survival of the § 2782 anti-indemnity analysis was uncertain at case inception. The pure Ketchum multiplier — unconstrained by Dague — allows enhancement for all five Ketchum factors when the § 1021.6 trifecta is proven and the court exercises its discretion to award fees.
Three Unique Distinctions in the Fee-Petition-Mechanics Series
This page covers the only California attorney fee statute with all three of the following simultaneously:
- THE ONLY page where the PRIMARY CLAIM is RECOVERY OF ATTORNEY FEES BY A PREVAILING INDEMNITEE from an indemnitor under CCP § 1021.6 in an equitable indemnity action — specifically the three-part § 1021.6 trifecta: (1) indemnitee found not liable on the underlying claim; (2) indemnitor had a duty to indemnify; and (3) indemnitee was required to defend the underlying claim because of the indemnitor's conduct. Distinct from Civ. Code § 1717 contractual fee clause enforcement (§ 1717 enforces a contractual fee clause bilateral regardless of which party the contract designated; § 1021.6 shifts fees specifically when the indemnitee was required to defend because of the indemnitor's conduct, not merely because a contract contained a fee clause); distinct from CCP § 128.5 frivolous conduct sanctions (court-imposed sanctions for litigation misconduct, not post-indemnity-action fee recovery); distinct from general negligence attorney fee recovery under the American Rule (no fee shifting without statute or contract — § 1021.6 is the specific indemnity-based exception in California); distinct from Civ. Code § 2782 anti-indemnity (§ 2782 voids indemnity provisions for contractor's own negligence; § 1021.6 addresses fee recovery after indemnity is determined to be valid and the trifecta is satisfied).
- THE ONLY page where the PRIMARY DEFENDANT is an INDEMNITOR — a subcontractor, component supplier, maintenance contractor, tenant, or design professional whose contractual indemnification duty was triggered by the underlying plaintiff's claim and who failed to accept tender of defense — specifically: concrete subcontractors who declined tender after homeowners sued the general contractor for foundation cracking; roofing subcontractors who rejected tender after water intrusion lawsuits; HVAC subcontractors who refused tender after building fires claimed to originate from their mechanical work; plumbing subcontractors who denied duty to defend after water damage claims; component suppliers who contested tender after product liability claims against the integrator; tenant businesses (restaurant operators, retail lessees, fitness facility operators) who contested indemnity after slip-and-fall incidents in leased premises where the landlord-indemnitee was named defendant; and design professionals (structural engineers, MEP engineers, geotechnical engineers) who refused tender after design defect claims against the design-build general contractor.
- THE ONLY page where the PRIMARY WELCH ANCHOR is in the GENERAL CONTRACTOR'S PROJECT MANAGEMENT SYSTEM SUBCONTRACT EXECUTION DATE — Procore Construction Project Management records subcontract execution date, change order execution date, and certificate of substantial completion date on Procore's institutional project management platform; Autodesk Build (formerly BIM 360 Field) records subcontract award date and Notice to Proceed date on Autodesk's institutional construction management platform; CMiC Construction Project Management records subcontract execution timestamp, scope of work commencement date, and lien release execution date on CMiC's institutional platform; Oracle Primavera P6/Contract Management records subcontract execution date and project milestone dates; Sage 300 Construction and Real Estate records subcontract execution date, completion percentage dates, and final payment application date — all general contractor project management systems record subcontract execution dates on the general contractor's institutional platform entirely outside the indemnitee or third-party plaintiff attorney's scheduling control.
DISTINCT FROM Civ. Code § 1717 contractual fee clause enforcement (§ 1717 enforces an existing contractual fee clause, making it bilateral regardless of which party the contract designated; § 1717's Welch anchor is the date of breach of contract on the contracting party's own payment or performance calendar; § 1021.6 shifts fees from the indemnitor to the indemnitee when the indemnitee was required to defend the underlying claim because of the indemnitor's conduct — a distinct three-part trifecta with no analog in § 1717; different defendants, different anchor, different fee framework). DISTINCT FROM CCP § 128.5 sanctions (§ 128.5 imposes court-ordered sanctions for frivolous tactics or bad-faith litigation conduct; § 1021.6 awards post-indemnity-action fee recovery to the prevailing indemnitee after satisfying the three-part trifecta; different triggering event, different standard, different motion). DISTINCT FROM Civ. Code § 2782 anti-indemnity (§ 2782 voids indemnity provisions requiring a contractor to indemnify another party for that other party's own negligence — it is a defense that the indemnitor raises to defeat the indemnity claim; § 1021.6 is the plaintiff-side fee-shifting statute that applies after the indemnity claim succeeds; § 2782 analysis precedes § 1021.6 analysis in every equitable indemnity case). DISTINCT FROM FAR/Davis-Bacon federal contractor disputes (the federal Contractor Disputes Act, 41 U.S.C. § 7101, covers government contract disputes before the ASBCA or CBCA and provides no private-party equitable indemnity fee provision; FAR Part 31 does not create private fee-shifting rights; § 1021.6 is exclusively a California private-party equitable indemnity fee statute in California Superior Court).
Ketchum / Dague Analysis for CCP § 1021.6 Equitable Indemnity
CCP § 1021.6 is PURE KETCHUM — no federal equitable indemnity statute provides attorney fee-shifting with a multiplier, and no Dague constraint applies. The analysis rests on four points:
- No federal equitable indemnity fee-shifting statute exists: The federal Contractor Disputes Act (41 U.S.C. § 7101 et seq.) covers government contract disputes before the Armed Services Board of Contract Appeals (ASBCA) or Civilian Board of Contract Appeals (CBCA) but provides no private-party equitable indemnity fee provision. FAR Part 31 governs the allowability of costs in federal contracts but does not create a private right of action or fee-shifting provision. No federal statute provides fee-shifting in private-party construction defect equitable indemnity actions in California courts — making § 1021.6 purely California-law fee-shifting with full Ketchum multiplier eligibility.
- No Dague constraint applies to pure § 1021.6 claims: City of Burlington v. Dague (505 U.S. 557 (1992)) applies only to federal fee-shifting statutes — it expressly held that federal fee-shifting statutes do not permit contingency multipliers. Because § 1021.6 is a California state statute with no federal analog, Dague does not constrain the Ketchum multiplier analysis for any time spent on the California equitable indemnity claim.
- Hensley segregation only if concurrent federal construction law claims exist: For the vast majority of private construction defect and premises liability § 1021.6 actions — between private parties in California courts — no Hensley segregation is required. Hensley segregation would be required only if the underlying construction action also involved concurrent federal Davis-Bacon Act violations, federal procurement law claims, or other federal construction law claims with their own federal fee-shifting provisions, in which case the attorney would need to segregate time spent on the federal issues (Dague-constrained) from time spent on the California § 1021.6 equitable indemnity issues (pure Ketchum). This scenario is rare in private residential and commercial construction defect litigation.
- § 1021.6 discretionary posture affects but does not eliminate Ketchum multiplier: Unlike mandatory fee statutes (e.g., Lab. Code § 1194 for unpaid wages, Civ. Code § 1780(e) for CLRA violations), § 1021.6 is discretionary — the court "may" award fees after finding the trifecta satisfied. This discretionary posture creates an additional contingency risk at inception that enhances, rather than diminishes, the Ketchum contingency factor: the indemnitee attorney accepted the § 1021.6 claim knowing not only that the trifecta must be proven but also that the court retains discretion to deny fees even after proof. PLCM Group Inc. v. Drexler (22 Cal.4th 1084 (2000)) and Ketchum v. Moses (24 Cal.4th 1122 (2001)) both support enhanced multipliers where the attorney accepted the case against substantial odds — the § 1021.6 discretionary layer adds to those odds.
The § 1021.6 Three-Part Trifecta: Documenting Each Element from the Subcontract Execution Date
CCP § 1021.6 requires the moving indemnitee to establish all three elements — the court may award fees only if all three are found. Each element generates its own billing task traceable from the subcontract execution date Welch anchor:
- Element 1 — Indemnitee Found Not Liable on the Underlying Claim: The indemnitee (general contractor, premises owner, or design-build entity) must have been found not liable on the underlying plaintiff's claim — by verdict, directed verdict, summary judgment, or settlement with an express no-liability admission. Documenting this element requires obtaining the underlying action's judgment or settlement agreement, which is a court record or contract document on the court's or mediator's own institutional calendar entirely outside the indemnitee attorney's scheduling control. The not-liable finding date is a secondary Welch anchor subordinate to the primary subcontract execution date.
- Element 2 — Indemnitor Had a Duty to Indemnify: The subcontract indemnity clause — recorded in the general contractor's Procore, CMiC, or Sage 300 project management system at the subcontract execution date — must create an enforceable indemnification duty after surviving the Civ. Code § 2782 anti-indemnity analysis. This element requires the subcontract indemnity clause scope analysis (Gap 1 work) and the § 2782 exception analysis performed at the outset of the representation.
- Element 3 — Indemnitee Required to Defend Because of Indemnitor's Conduct: The indemnitee must have been required to defend the underlying claim specifically because of the indemnitor-subcontractor's conduct — the indemnitor's scope of work overlap with the underlying claim area, the indemnitor's failure to accept the tender of defense, and the causal connection between the indemnitor's work and the underlying plaintiff's claim. This element is established through the Procore/Autodesk Build/CMiC project records cross-referencing (Gap 2 work) — the scope of work records, daily reports, change orders, and inspection records all recorded in the general contractor's institutional project management system on project timeline dates entirely outside the indemnitee attorney's scheduling control.
Because all three elements must be established, and because the project management system records are the primary documentary foundation for Elements 2 and 3, the subcontract execution date in the Procore/CMiC/Sage 300 system is the correct Welch anchor: it is the earliest institutional timestamp that establishes the indemnification relationship (Element 2 foundation) and the beginning of the indemnitor's scope of work period (Element 3 foundation).
Total Annual Billing Gap — Three-Gap Summary
- Gap 1 (subcontract indemnity clause & § 2782 anti-indemnity analysis): 5.39 hrs = $1,617–$2,695/yr
- Gap 2 (Procore/Autodesk Build records cross-reference & tender-of-defense coordination): 7.26 hrs = $2,178–$3,630/yr
- Gap 3 (§ 1021.6 fee motion preparation): 4.03 hrs = $1,210–$2,017/yr
- Total: 16.68 hrs = $5,005–$8,342/yr untracked at $300–$500/hr median California solo practitioner rate
These gaps accumulate because each billing event — reviewing the subcontract indemnity clause against the § 2782 anti-indemnity exception framework, cross-referencing Procore change orders against the underlying plaintiff's defect allegations, coordinating the tender-of-defense rejection letter timeline with the underlying claim defense posture — happens in short, unscheduled sessions without automatic time-capture triggers. The subcontract execution date in the general contractor's project management system is the Welch anchor from which all these billings trace, but without automatic capture they remain unrecovered.
How ClaimHour fits California CCP § 1021.6 equitable indemnity practice
ClaimHour captures billable moments automatically — call metadata, email activity, document edit time — without requiring a practice management system. For solo construction defect and premises liability attorneys handling § 1021.6 equitable indemnity cases, that means the subcontract indemnity clause analysis sessions, the Procore/Autodesk Build project records cross-referencing work, and the § 1021.6 fee motion preparation are all captured in the background. When you build the fee petition lodestar from the Procore/CMiC/Oracle Primavera subcontract execution date, ClaimHour's automatically-logged entries close the gap between what you billed and what you actually did.
Get early access