Buyer authority
Each request identifies the authorized requester, procurement contact, security lead, consent, and lawful basis before work begins.
Contact
Start with the mission.
Institutional buyers, partner firms, operators, and training clients can start the right JTF request here.
SOW package
Quote, statement of work, acceptance, approval, and mission requirements stay connected for client and procurement review.
Evidence terms
Each service request declares standard, restricted, or client-approved-only evidence handling before incidents can be released.
Delivery records
Reports, invoices, history exports, and after-action records are prepared from approved mission activity.
Licensing
Licensed work is checked by jurisdiction before acceptance, with regulated investigation and protective-service boundaries handled before staffing.
Insurance
Partner firms and delivery teams must provide insurance references before JTF routes subcontract work or represents coverage to a buyer.
Evidence handling
Requests declare standard, restricted, or client-approved-only evidence handling so incident records are useful without exposing unnecessary material.
Privacy
Client, operator, and partner information is shown only where it is needed, with sensitive personal data kept out of public and client-facing views.
Credential verification
Operators, instructors, and firms disclose credentials through JTFID Passport so buyers can see trust signals without receiving raw private files.
Chain of command
Every mission has accountable handoff points for intake, supervision, incident response, reporting, billing, and closeout.