how do I make a form only applicable for a specific site

To make a safety form applicable only to a specific site or location, configure it around site-specific applicability, role-based access, workflow assignment, and document control. At minimum, the form should require a site/location field, tie the form to that site in your system logic, and prevent use outside the approved location. This approach aligns with construction safety expectations that hazards, access, traffic control, storage areas, and work methods can be specific to the site, and that some plans must be developed for conditions specific to the site and be available at the work site. [2] [2] [2]

• Create a mandatory Site/Location field and make it the primary applicability filter.
• Assign each form template to one approved site, project, yard, plant area, or geofenced location.
• Use conditional logic so only users assigned to that site can view, start, edit, approve, or close the form.
• Display the site name, project number, and physical work area on the form header and completed record.
• Require the user to confirm the exact work location before submission.
• Block cross-site copying unless reapproved for the new location.

[1] [2] For site-specific applicability, build the form so its questions, hazards, and required controls change by location. A good model is a job hazard analysis form that captures the job/task location, steps, hazards, and preventive measures. In practice, this means the site selection should trigger location-specific sections such as traffic control, housekeeping, sanitation, excavation, scaffolding, radiation, welding, or hazardous substance requirements that apply at that site. [1] [1] [1] [3]

• Map each site to its applicable hazards and regulatory topics.
• Use conditional sections for site-specific risks such as excavation, scaffolding, welding, radiation, traffic control, sanitation, and hazardous substances.
• Require a competent person or qualified person review when the site has higher-risk operations or alternate methods.
• Include fields for work area, contractor, subcontractor, shift, and affected crews so applicability is precise.

[8] [2] For access restrictions, use role- and site-based permissions. Limit access so only authorized personnel for that location can use the form, and only trained or qualified personnel can complete sections tied to specialized equipment or hazardous work. Separate permissions for drafting, review, approval, and closure. If contractors or subcontractors are involved, restrict them to the forms and records for their own site and scope of work. [9] [9] [8]

• Viewer: can read forms only for assigned site(s).
• Initiator: can create forms only for assigned site(s) and work areas.
• Supervisor or competent person: can review and sign site inspections, JHAs, and corrective actions.
• Qualified person: required approver for engineered plans or alternate methods tied to site-specific conditions.
• Administrator: can assign sites, retain records, and control template revisions, but should not bypass approval rules without audit logging.

[8] [2] For assigned workflows, route the form based on site, activity, and risk level. A practical workflow is: initiator completes the form, supervisor reviews site conditions, competent person verifies hazards and controls, required specialists approve if triggered, then the form is released for use at that site. Add automatic reassignment when the selected site changes. Also require periodic review for active sites and recurring inspections. [8] [8]

1. User selects the site/location.
2. System loads the site-specific version of the form and required sections.
3. User completes task steps, hazards, and preventive measures.
4. Supervisor reviews for operational fit and contractor coordination.
5. Competent person or qualified person approves where required.
6. Form becomes active only for that site and remains available at the work site.
7. Corrective actions, inspections, and reapprovals are triggered by changes in conditions, incidents, or scope.

[1] [1] [2] For compliance requirements, configure the form to enforce the regulations and internal rules that apply to the selected site and activity. The form should not just collect information; it should require evidence that the employer has instructed employees, identified hazards, assigned preventive measures, conducted inspections, and controlled unsafe equipment or conditions. Include mandatory checks for housekeeping, sanitation, access/traffic control, equipment safety, and any topic relevant to the site. [8] [9] [4] [4]

• Require training acknowledgment for users completing or approving the form.
• Require hazard identification and preventive measures for each task step.
• Require inspection frequency rules by site type: fixed site, satellite site, mobile site, or infrequently visited site.
• Require tagging, lockout, or removal of unsafe equipment when identified.
• Require site housekeeping, sanitation, and waste controls where applicable.
• Require additional sections when the site involves scaffolds, excavations, welding, radiation, vehicles, or hazardous substances.

[8] [7] [5] [6] [10] For regulatory documentation controls, treat the form as a controlled safety record. Assign a document owner, revision number, effective date, approved site(s), and retention rule. Keep only the current approved version available for active use at the site, archive superseded versions, and maintain an audit trail of who changed applicability, workflow, approvals, and attachments. Where regulations require documents or manuals to be available with equipment or at the work site, your system should support attachment control and on-site availability. [2] [5] [5]

• Document ID, revision, effective date, and approval signatures.
• Approved site/location and work scope.
• Linked regulatory references and internal procedures.
• Required attachments such as site plans, permits, manuals, SDSs, inspection records, and training records.
• Read-only archive of obsolete versions with change history.
• Audit trail for access, edits, approvals, and distribution.
• Availability of the current approved record at the work site or with the equipment, as applicable.

[2] [5] A strong configuration standard is to make the form unusable unless these fields are completed: site/location, task or process, hazards, preventive measures, responsible reviewer, approval role, effective date, and required attachments. If the site changes, the system should force re-review and reapproval because hazards, access, traffic control, storage, sanitation, and applicable rules may change from one location to another. [1] [1] [2] [4]

In short, configure the form so site selection drives applicability, permissions, workflow, compliance checks, and document availability. That gives you a form that is truly limited to the intended location and defensible from both an operational and regulatory standpoint.