Turn a rough owner request, bid note, floor plan or contractor conversation into a structured project scope before equipment selection starts.
A strong Basis of Design is the bridge between an owner saying “we need cameras and access control” and a project team knowing what is actually being priced. It records the operating objective, project boundaries, assumptions, interfaces and the decisions that still need to be made.
For contractors and procurement teams, this page is designed to create a usable first-pass scope without pretending that every project begins with a perfect drawing set. You can start with a facility type, approximate quantities and a short narrative, then turn that into a concise project brief for further review.
The resulting brief is a planning artifact, not a stamped engineering document. Code, permitting, licensing, AHJ requirements and professional-design responsibility remain project- and jurisdiction-specific.
These are planning tools. Final design, code, licensing, manufacturer limits and project-specific requirements still require verification.
Enter the project facts and build a first-pass scope summary.
No. A Basis of Design explains intent, assumptions and technical direction. Final drawings, permits, sealed documents and licensed design responsibility depend on the project and jurisdiction.
Yes. The workspace is intentionally useful early in a project. Missing information becomes part of the open-question list instead of being silently guessed.
Floor plans, RFP/RFQ documents, schedules, owner standards, existing-system information and any preferred manufacturers are all useful starting material.
Safsale can use the result as a starting point for product selection, project pricing, documentation or procurement support.