Educational guide
California private investigation firms work under BSIS licensing, the Private Investigator Act, strict confidential-communication recording rules, surveillance evidence, and attorney handoffs. PI Core can organize that record without deciding licensing status or recording legality.
Direct answer
A California PI file should track the licensed agency, qualified manager context, assignment scope, surveillance media, interview instructions, Penal Code section 632 recording review, any section 633.5 exception review, and delivery status. PI Core can keep those checkpoints visible, but BSIS eligibility, consent, exceptions, and evidence use remain practitioner-reviewed.
Regulatory framework
The California PI Core pages identify BSIS and Penal Code section 632. This educational guide goes deeper on how licensing, scope, recording review, and attorney delivery should sit together in an investigation record.
The Bureau of Security and Investigative Services administers California PI licensing. A case system should carry agency, qualified manager, branch, renewal, insurance, and license-review context without implying the system files BSIS forms.
Business and Professions Code sections 7520 through 7522 frame licensing, qualifying manager, and regulated investigative services. The case file should identify whether the assignment is surveillance, locating, evidence gathering, interview work, or attorney-requested investigation.
California treats confidential communication recording as a high-risk area. A PI workflow should flag interviews, calls, audio surveillance, and undercover communications for consent and legal review before capture or delivery.
The crime-related exception for certain threats or violent offenses should be treated as counsel-reviewed context. It should not become a normal one-party recording assumption for PI assignments.
Procedure walkthrough
California firms need a record that makes the review sequence visible before field work creates audio, media, or evidence problems.
Record the licensed agency, qualified manager or supervising role, investigator assignment, client, attorney, subject, scope, and jurisdiction. That keeps BSIS context connected to the work rather than buried in an administrative folder.
Use a specific scope label for locating people, gathering evidence, investigating conduct, surveillance, witness work, or attorney-requested support. That helps reviewers decide what statutes, client instructions, and evidence practices matter.
Interview recordings, phone calls, body-worn audio, in-car audio, and hidden audio should have a visible review status. The field note should distinguish video without audio from audio capture and from later transcription or delivery.
If a file invokes extortion, violence, kidnapping, domestic violence, or a similar statutory exception context, store that review separately with attorney or senior investigator ownership. The exception should not be mixed with routine consent notes.
When a law firm retains the investigator, the record should preserve report drafts, media references, privilege or work-product notes, delivery status, and review owner before materials leave the investigation file.
Local variation
BSIS and Penal Code rules are statewide. Implementation still varies when firms serve major court markets and attorney teams across different counties.
Los Angeles assignments may span LA, Orange, Riverside, San Bernardino, and Ventura practice. A PI system should preserve the anchor county and neighboring-county context without treating every assignment as a single courthouse matter.
San Diego investigators often work around county court, border, military, and federal Southern District contexts. The workflow should preserve local context while keeping BSIS and recording-law review statewide.
San Francisco, San Jose, and Oakland work may involve dense attorney handoffs and public-records work across multiple counties. Media, consent, and delivery notes need a clear county and client record.
Licensing, branch, renewal, and insurance notes should stay in a statewide agency record. Individual investigations should reference the relevant license context without duplicating compliance documents in every case.
Implementation check
The implementation goal is not to automate California law. It is to keep the source, scope, recording context, evidence, and review owner visible.
A single media field cannot carry California risk cleanly. Separate video, audio, transcript, interview, and consent-review fields make the case easier to audit before reports are delivered.
The case should link BSIS source context, Penal Code references, client instructions, and attorney guidance near the assignment so later reviewers know what controlled the field decision.
Use statuses like review needed, consent documented, attorney reviewed, or do not record. Avoid labels that imply the software has decided legality, admissibility, or BSIS eligibility.
A California migration should include one surveillance matter with video, one interview matter with consent notes, and one attorney-requested report package. That tests the actual risk surface.
Practitioner review limits
PI Core can make BSIS and recording-law context visible. It does not replace a licensed investigator, qualified manager, attorney, or regulator.
California PI licensing and recording workflow can be represented as source references, assignment records, license-review notes, audio flags, evidence status, report drafts, and responsible owners. BSIS licensing status, Penal Code section 632 consent analysis, section 633.5 exception analysis, and admissibility decisions remain reviewed outside the product.
BSIS records, the Private Investigator Act, Penal Code provisions, client instructions, and attorney guidance control the operating record. PI Core can keep those instructions visible near the investigation file, but it cannot convert a firm-side note into an official license, court, or admissibility determination.
Surveillance video, audio, phone calls, witness interviews, undercover work, and third-party media require state-specific review. The file should show who reviewed recording context, what source was checked, and what instruction controlled the assignment.
Firms moving from CROSStrax, Trackops, CaseFleet, spreadsheets, or mixed folders should test active assignments, reports, evidence references, media libraries, billing notes, and attorney delivery records before cutover.
Butler workflow relevance
PI Core can track California assignments, investigators, scope notes, surveillance logs, media references, audio flags, consent notes, attorney review, report drafts, and migration review. It does not file BSIS renewals, decide recording legality, or claim direct court evidence filing.
Related Butler pages
FAQ
No. It is an educational workflow guide for investigation firms and adjacent legal teams. Licensing status, scope-of-practice questions, surveillance legality, recording-law analysis, and evidence-use decisions remain investigator, agency, attorney, court, or regulator reviewed.
No. PI Core can track audio flags, consent notes, assignment instructions, legal-review status, and source references. It does not decide whether a recording is lawful under California Penal Code section 632 and related exceptions or any related exception.
Private investigation work often turns on surveillance, interviews, phone calls, media capture, and attorney handoffs. Licensing explains who may perform the work; recording law helps determine how audio or communications are reviewed before they are captured, stored, delivered, or used.
Use it to build demo scenarios from real work: one surveillance assignment, one witness interview, one attorney-requested matter, one licensing or renewal record, and one migrated case. The evaluation should test whether source references, recordings, reports, evidence, and review owners stay together.
No. These educational pages describe firm-side organization. License applications, renewals, regulatory submissions, official license status, and disciplinary responses remain outside the product unless a specific integration is separately validated.
Start with California PI Core for geographic context, then review PI Core pricing if user count, trial timing, founding cohort eligibility, and migration are the buying questions. Bring a reviewed sample investigation file into the evaluation so product discussion stays tied to actual practice.
Sources checked
Sources combine BSIS licensing materials, the Private Investigator Act, California recording statutes, and attorney-technology context.
Next step
Bring one BSIS compliance record, one surveillance file, one witness interview, and one attorney handoff into a PI Core evaluation. That exposes whether licensing, consent, media, and report review stay visible.