PPSB administers private protective services
The Private Protective Services Board publishes license-type, application, FAQ, and continuing-education materials. A PI workflow should keep PPSB source context near agency and assignment records.
Educational guide
North Carolina private investigation work sits inside Chapter 74C and the Private Protective Services Board framework. PI Core can organize license, assignment, recording-law, evidence, and attorney handoff context without filing PPSB submissions or deciding recording legality.
Direct answer
A North Carolina PI file should track Private Protective Services Board license context, agency and individual roles, Chapter 74C scope, continuing education or renewal context, assignment type, section 15A-287 one-party recording review, and attorney delivery status. PI Core can organize those records, but license eligibility and recording-law application remain practitioner-reviewed.
Regulatory framework
The North Carolina PI Core page identifies the Private Protective Services Board. This guide goes deeper on licensing, scope-of-practice, recording review, and major-market implementation.
The Private Protective Services Board publishes license-type, application, FAQ, and continuing-education materials. A PI workflow should keep PPSB source context near agency and assignment records.
Chapter 74C covers private protective services and defines private investigator-related work. The case file should identify whether the assignment is PI work, attorney support, surveillance, locating, or another regulated service.
North Carolina administrative rules provide implementation detail for PPSB-regulated work. Source references should live near compliance records and assignments that depend on license posture.
North Carolina is treated as one-party for recording workflow, but the file should still document participant role, audio plan, consent basis, and attorney or senior-investigator review.
Procedure walkthrough
North Carolina implementation should make license context, assignment type, and recording posture visible before field work starts.
Record the license type, license holder, assigned investigator, responsible reviewer, client, attorney, subject, and assignment scope. That keeps Chapter 74C context tied to the matter.
Distinguish surveillance, interviews, locating, records work, background investigation, attorney-requested investigation, and related protective-services categories.
For calls, interviews, or in-person conversations, the file should show whether a consenting party is present, what audio is planned, who reviewed it, and whether counsel imposed additional restrictions.
Charlotte is the current North Carolina city+vertical PI anchor. Raleigh, Greensboro, and Durham are hub-only in this phase, so their context belongs in implementation notes rather than non-existent city PI links.
Photos, audio, video, reports, transcripts, and attorney notes should remain tied to the assignment while final delivery status stays separately reviewable.
Local variation
PPSB licensing is statewide. Major local markets still change records, court-adjacent, and attorney handoff details.
Charlotte PI work often supports Mecklenburg County and federal Western District contexts. The Charlotte PI Core page anchors city-specific implementation.
Raleigh, Durham, and Chapel Hill work can involve Wake, Durham, and Orange County contexts. Current site coverage is hub-only for Raleigh and Durham, so this page links statewide and to Charlotte for vertical depth.
Greensboro, Winston-Salem, Wilmington, and coastal assignments may have different records and attorney handoff patterns, but Chapter 74C and PPSB remain statewide controls.
License, renewal, continuing education, and rule source references should live in the agency compliance record and be available from assignments.
Implementation check
The implementation goal is to keep North Carolina license, scope, recording, and evidence context reviewable.
A firm should be able to see who holds the relevant PPSB credential, who performed the field work, and who reviewed the report without reading every note.
Participant role, consent basis, audio flag, attorney review, and do-not-record statuses make one-party review more reliable than freeform notes.
PPSB application, FAQ, continuing-education, statute, and rule sources should be visible when a license or assignment record is reviewed.
A North Carolina migration should include one Charlotte assignment, one Triangle or Piedmont matter, one recording-sensitive file, and one PPSB compliance record.
Practitioner review limits
PI Core can organize North Carolina licensing and recording-law context. It does not decide Chapter 74C eligibility, NCAC compliance, section 15A-287 recording questions, or evidence use.
North Carolina PPSB PI workflow can be represented as source references, assignment records, license-review notes, audio flags, evidence status, report drafts, and responsible owners. PPSB license status, Chapter 74C role analysis, NCAC compliance, recording-law application, and evidence-use decisions remain reviewed outside the product.
PPSB materials, Chapter 74C, 14B NCAC 16, section 15A-287, 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 North Carolina assignments, PPSB license context, investigator roles, audio flags, consent notes, evidence records, attorney handoffs, report drafts, and migration review. It does not file PPSB applications or decide recording legality.
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 North Carolina section 15A-287 one-party recording-law review 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 local-compliance 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, court petitions, regulatory submissions, official license status, and disciplinary responses remain outside the product unless a specific integration is separately validated.
Start with North Carolina 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 PPSB licensing materials, Chapter 74C, 14B NCAC 16, North Carolina recording-law authority, and court context.
Next step
Bring one PPSB compliance record, one Charlotte assignment, one Triangle or Piedmont matter, and one audio-sensitive file into a PI Core evaluation.