CRM
Polygraph enquiry form: what to ask, what to avoid
A privacy-first polygraph enquiry form template that limits sensitive disclosures and routes suitability, consent and legal checks to a qualified professional.
Collect a request for contact, not a case file
The public form's purpose is to establish a safe way for an examiner to reply and decide whether the enquiry belongs in the business. It should not solicit accusations, an alleged offense, workplace test mandates, sensitive relationship details or a third party's private information. An ordinary website contact form is not a substitute for legal privilege, clinical intake or evidence-handling procedures.
Practical first-contact fields
If a potential employer sends an enquiry, the form should not invite the company to upload employee names or test requests without legal review. In the U.S., the EPPA restricts most private employment testing and provides limited exceptions under conditions. A "business enquiry" classification does not establish eligibility.
| Field | Include? | Reason |
|---|---|---|
| Contact name | Yes, with privacy notice | Identifies the correspondent |
| Safe email or phone | Yes | Allows a safe reply |
| General location/jurisdiction | Yes | Determines availability and potential legal relevance |
| Broad reason for contact | Optional category | Helps triage without disclosing allegations |
| Preferred contact method/time | Optional | Reduces inadvertent disclosure |
| Referral organization | Optional and not public | Enables professional follow-up when appropriate |
| Description of accusations | No | High-risk information for a generic form |
| Third-party IDs, medical records or case files | No | Belongs in an appropriately protected process, if lawful and necessary |
| Consent to the actual examination | No | Must follow the examiner's informed consent process, not a marketing checkbox |
Write explicit on-page boundaries
Suggested text: "Please use this form only to request a confidential reply. Do not include allegations, medical details, identifying information about other people, or legal documents. Submission does not create a professional engagement, confirm an examination, or establish that your request is lawful or suitable."
The actual privacy notice must reflect the provider's data handling, location and legal obligations. An example above is editorial guidance, not a complete legal notice.
The human review sequence
- Confirm safe contact details and general jurisdiction.
- Determine whether the examiner has capacity and the appropriate qualifications.
- Check lawful purpose, relevant restrictions and potential conflicts before taking sensitive information.
- Provide a separate explanation of consent, confidentiality limits, expected steps and reporting recipients where appropriate.
- Only then propose a consultation or examination time under the office's actual rules.
- Keep records according to applicable policies, professional standards and legal retention requirements, outside public-site notes unless the system has been reviewed for that purpose.
Test the website itself
Have an internal reviewer submit neutral test data. Check form errors, anti-spam handling, confirmation text, notification recipient, access permissions and deletion workflow. Test that the reply does not expose the enquiry subject in a shared email preview. A public "Your lie detector appointment is confirmed" screen is a serious design defect when only a contact request was submitted.
A CRM may track that a contact was made without storing the case. If the site cannot support the planned sensitivity and jurisdictional requirements, use a verified confidential channel instead of stretching a generic tool beyond its intended use.
Next step: Review OneStudio's published form and CRM scope and contact OneStudio to plan a minimal first-contact journey.