Planning & AssessmentAction checklist

Security Quote Preparation and Site-Intake Checklist

A useful security quote starts with the problem to be addressed, not just a requested number of guards. Prepare the locations, operating hours, occupancy, public access, entrances, deliveries, assets, prior incident patterns, existing controls, desired duties, reporting needs, emergency contacts, start date and procurement requirements. Separate confirmed facts from estimates and keep access codes, exact patrol patterns, camera blind spots and personal data out of an unsecured online form. This checklist helps organize a first conversation; it does not produce a binding quote, staffing mandate, risk assessment or guarantee. A qualified provider should validate conditions before final scope and pricing are approved.

16 checks4 sectionsSources checked July 19, 2026
Why it matters

Use a system view, not a single-control view

Incomplete intake information can produce proposals that look comparable but rest on different assumptions about hours, posts, equipment, reporting or client responsibilities.

Clear goals and current site facts help a provider explain why it recommends a guard, patrol, camera tower or layered approach and help the buyer evaluate later whether the service is meeting its intended purpose.

Before you begin

How to use this checklist

  1. Complete the non-sensitive items with operations, property, procurement and security stakeholders before requesting proposals.
  2. Place confidential maps, incident records and access details in a controlled packet shared only after appropriate authorization.
  3. Identify confirmed requirements separately from preferences and estimates.
  4. Ask the provider to state assumptions, exclusions, client responsibilities and information still needed.
  5. Validate the final scope through a site walk or equivalent review before contract approval.
Interactive checklist

Mark each task from current evidence

Use Not applicable only when the item genuinely does not apply, and follow the site’s approved escalation process for any urgent condition.

Section 1 of 4

Organization and security goals

Explain what the organization needs the service to accomplish.

01Identify the contracting organization, decision-makers and authorized day-to-day security contacts.

Evidence to look for: Use business roles and controlled contact records; do not enter personal contact details in a public worksheet.

02State the primary security concerns and desired outcomes in plain language.

Evidence to look for: Examples may include after-hours presence, access support, incident reporting or periodic property checks without assuming a particular staffing solution.

03Define the locations, service start window, expected duration and hours needing coverage. Priority review item

Evidence to look for: Note whether hours are fixed, seasonal, event-based or subject to construction or tenant changes.

04Identify procurement, insurance, invoicing and contract-review requirements.

Evidence to look for: The correct internal reviewers state mandatory documents, deadlines and approval authority.

Section 2 of 4

Site and operating conditions

Give the provider enough context to plan while protecting sensitive information.

05Summarize property type, occupied areas, public access, normal population and after-hours activity.

Evidence to look for: Include employees, residents, visitors, contractors and deliveries as relevant, using ranges rather than unnecessary personal data.

06List entrances, gates, parking, loading and other service areas that may affect scope.

Evidence to look for: Use a controlled site plan for exact layouts and never put codes or exploitable gaps in the public intake.

07Describe current access control, lighting, alarms, cameras, reception and other protective measures.

Evidence to look for: State known owners, monitoring hours and limitations without assuming that installed equipment is fully operational.

08Identify site constraints such as construction, weather exposure, accessibility, limited power or connectivity.

Evidence to look for: Include conditions that affect safe staffing, patrol or equipment placement and have qualified parties validate technical claims.

Section 3 of 4

Incident and risk context

Use current, objective information to explain why coverage is being considered.

09Summarize relevant incident types, trends and time ranges without naming victims or suspects in the general intake.

Evidence to look for: Use verified reports where available and distinguish reported concerns from confirmed incidents.

10Identify high-consequence operations, assets or people that require special planning.

Evidence to look for: Describe the business impact at a useful level and keep detailed inventories and personal information controlled.

11Document credible emergency scenarios and the site's current emergency action plan interface. Priority review item

Evidence to look for: State who owns the plan and expected guard support; do not ask a security vendor to replace employer or public-safety responsibilities.

12Record known legal, lease, insurer or client requirements for security service.

Evidence to look for: Have the issuing or responsible professional verify each requirement rather than relying on assumptions.

Section 4 of 4

Service duties, reporting and proposal format

Define how proposed service will operate and how the buyer will evaluate it.

13List proposed guard, patrol or surveillance duties and identify items still requiring site assessment. Priority review item

Evidence to look for: Duties are outcomes and observable tasks, not unreviewed force, search, detention, medical or technical instructions.

14Define emergency, urgent and routine notification expectations with primary and backup client roles. Priority review item

Evidence to look for: Immediate danger always permits 911; internal contacts and response expectations are validated before service.

15Specify required activity, patrol, incident and management reporting.

Evidence to look for: State recipients, frequency, secure delivery, retention and useful content rather than requesting reports without a purpose.

16Request itemized pricing, assumptions, exclusions, client responsibilities and optional alternatives.

Evidence to look for: The format permits a fair comparison of total expected cost and proposed coverage.

Current result

Complete the checklist to see a summary

Results are informational and do not certify compliance or eliminate risk.

Common mistakes

What can weaken the review

  • Requesting a number of guards without explaining the desired outcome or site conditions.
  • Sending access codes, detailed vulnerabilities or personally identifiable incident records through an unsecured form.
  • Comparing quotes that use different hours, equipment, holiday, overtime or supervision assumptions.
  • Expecting a vendor to own the employer's emergency, HR, life-safety or maintenance duties.
  • Treating an early estimate as a final binding quote before site validation.
Practical questions

Frequently asked questions

What information is needed for a security guard quote?

Provide goals, locations, coverage hours, site use, access points, current controls, relevant incident patterns, desired duties, reporting, emergency contacts, start date and procurement requirements. Sensitive details should move through a controlled process.

Can a security company quote a site without visiting it?

A provider may be able to give an initial estimate from reliable information, but a site review is often needed to validate access, duties, constraints, equipment and assumptions before final scope.

Should I share incident reports with a security bidder?

Share only relevant, authorized and appropriately protected information. An anonymized trend summary may be enough initially; detailed records should follow legal, privacy, retention and need-to-know rules.

Why do security guard quotes vary?

Differences may reflect service hours, guard qualifications, supervision, relief coverage, equipment, technology, reporting, holidays, travel and contractual risk. Ask each provider to list assumptions and exclusions.

Sources and evidence baseline

These references support the general planning baseline. Site-specific decisions still require the responsible organization and appropriate qualified professionals.

  1. Security Assessment at First Entry (SAFE)Cybersecurity and Infrastructure Security Agency

    Site walkthrough, existing measures, vulnerabilities and options-for-consideration approach.

  2. NIST Special Publication 800-171 Revision 3, Physical Protection RequirementsNational Institute of Standards and Technology

    Physical access authorization, monitoring, logs, visitors and access-device considerations.

  3. Emergency Action Plan ChecklistOccupational Safety and Health Administration

    Emergency contacts, communication and site-specific plan responsibilities.

Source links checked: July 19, 2026

Related services and checklists

Continue with the service context or a neighboring planning tool that helps you act on what you found.