How we work

Licensed people. Supervised shifts. A record you can keep.

Before you hire us you should know who will be on the post, what they are licensed for, how incidents are handled, and what lands on your desk when the job is done.

Credentials

We do not publish private licences on this page.

A person or firm can send you a time-bound proof link for the credentials they choose. This page will not invent a wall of sample names to look busy.

Checked first

Who is on the job

Operators and firms prove identity and current licences before they are offered a post.

The job file

What you can see

Assignments, check-ins, incidents, reports, and invoices stay on the same job — not in three inboxes.

A person signs

Drafts and AI

Anything that goes to a client is reviewed by a named JTF person. Software does not speak for us.

You set the terms

How we handle evidence

Standard, restricted, or client-approved release — chosen before the first incident, not after.

jurisdiction checked

Licensing

We check the licence for the city and the work before we accept it. If the job needs a private investigator licence we do not have, we refuse it.

required

Insurance

A partner firm shows insurance before we put them on your job or tell you they are part of the plan.

client controlled

Evidence handling

You decide how incident records are released so the file is useful without leaking more than the job needs.

minimum necessary

Privacy

We show names, routes, and personal data only where the job needs them. Public pages do not list private licences.

Passport verified

Credential verification

Operators and firms share a time-bound proof link. You see what is current without receiving a stack of private files.

named owner

Chain of command

Every job has a named owner for intake, supervision, incidents, reporting, billing, and closeout.

before you sign

Capability plan

Which licences, which city, which partner firm, and who supervises — written before the first shift.

on request

Security review

Who can see the job, how long records are kept, and how incidents are released.

after the job

Delivery file

Timeline, staffing, incidents, reports, and invoices from the same file.

required

Human review

If a draft was machine-assisted, a named reviewer still accepts it before you see it.

tracked

NCAGE

Vendor eligibility and renewals stay ready for procurement review.

tracked

UNGM

Global institutional registration status stays visible to buyers.

tracked

CanadaBuys

Canadian procurement status stays visible for qualified opportunities.

planned

NATO NSPA

Alliance-facing registrations are planned as JTF pursues larger institutional work.

required

Buyer authority

We need the person who can authorize the work, where updates should go, and why the job is lawful — before anyone is posted.

tracked

SOW package

Quote, statement of work, and acceptance stay on one file so procurement is not chasing three versions.

agreed

Evidence terms

You choose standard, restricted, or client-approved release before the first incident — not after someone asks for the footage.

exportable

Delivery records

Reports, invoices, and after-action notes come from the same job file you already approved.