Security Company RFP Enquiry Form: Fields That Qualify a Guarding Opportunity

Overview

A weak security-company form asks:

Then the commercial team receives:

Need security. How much?

A stronger form does not try to write the final guarding scope.

It helps the team answer:

That is the right job for the first public form.

• name;
• email;
• message.
• Is this a service we provide?
• Is the site inside our coverage area?
• Is the request temporary or ongoing?
• How many sites may be involved?
• What hours or coverage pattern is being considered?
• Is there an RFP/specification?
• What commercial follow-up is needed?

Field 1: Name

Recommended label: Name

Simple.

Field 2: Company

For B2B guarding enquiries, company name is important.

Useful for:

• procurement routing;
• account matching;
• multi-site clients;
• existing-client recognition.

Field 3: Role

Optional choices can include:

This helps the sales team understand the buying context.

Do not force the visitor into an internal title taxonomy.

• procurement;
• facilities;
• property management;
• construction/site management;
• event management;
• operations;
• business owner;
• other.

Field 4: Work email

Useful for commercial follow-up and procurement communication.

Do not ask for security-system credentials.

Field 5: Phone

Commercial security opportunities often need clarification.

Collect a phone number when the company genuinely follows up by phone.

Field 6: Site postcode or address

This is one of the highest-value qualification fields.

It helps answer:

Do not use a public address field as an operational site-security record.

• Do we cover this area?
• Which branch or commercial team should review it?
• Is this one site or part of a wider account?

Field 7: Number of sites

Possible options:

Use ranges that make sense for the business.

This is prospect context.

Operational sites should be created later after the contract is accepted.

• one site;
• 2–5;
• 6–20;
• 20+;
• not sure yet.

Field 8: Sector / facility type

Possible options can include:

Publish only sectors the company serves.

• construction;
• warehouse/logistics;
• retail;
• office/corporate;
• residential development;
• event/venue;
• hospitality;
• healthcare;
• education;
• industrial;
• vacant property;
• other.

Field 9: Service required

Possible choices:

Do not include CCTV/security-system installation in this guard-company form when a separate installer journey owns that intent.

• manned guarding;
• static guarding;
• mobile patrol;
• keyholding;
• alarm response;
• construction-site security;
• event security;
• concierge/front-of-house security;
• temporary cover;
• not sure.

Field 10: One-off, temporary or ongoing

Possible choices:

This quickly changes the commercial path.

• one event;
• temporary project;
• short-term cover;
• ongoing contract;
• tender/RFP;
• not sure.

Field 11: Preferred start date

Recommended label:

When do you expect coverage to begin?

This is a desired commercial start.

It is not a confirmed guard deployment.

Field 12: Coverage hours

A useful prompt can be:

What coverage are you considering?

Possible choices:

This helps the company understand scope without collecting post orders.

• business hours;
• nights;
• weekends;
• 24/7;
• specific event hours;
• not sure;
• other.

Field 13: Number of posts or guards

Keep it optional.

Recommended label: Approximate number of posts or officers, if already known

A prospect may not know.

Use not sure.

The final staffing model belongs after assessment and commercial review.

Field 14: Shift pattern

Optional examples:

Do not force a prospect to design the rota.

• 8-hour;
• 12-hour;
• day/night rotation;
• event-specific;
• buyer has specification;
• not sure.

Field 15: Site type and operating environment

A short field can ask:

Anything about the site that affects the commercial requirement?

Safe examples:

Do not ask for vulnerable access points or exact patrol weak spots on the public form.

• public-facing;
• active construction;
• warehouse/logistics;
• vacant;
• multiple entrances;
• high visitor volume.

Field 16: Existing provider

Optional question:

Is there an existing security provider?

Options:

This can help the sales team understand:

Do not ask for confidential competitor pricing in the first form.

• yes;
• no;
• not sure/pre-market.
• replacement tender;
• new requirement;
• temporary gap.

Field 17: RFP or specification status

Possible options:

If the real workflow supports documents, explain the correct submission path.

Do not promise upload when no verified upload exists.

• RFP/specification ready;
• draft requirements;
• early research;
• site discussion needed;
• not sure.

Field 18: Procurement deadline

For formal tenders, ask:

Is there a response deadline?

Use:

This is different from the proposed service start date.

• date;
• not applicable;
• not sure.

Field 19: Site discussion or survey need

Possible prompt:

Would a site discussion or consultation be useful?

Options:

A defined consultation can later be booked if the business uses that workflow.

Do not turn this into guard deployment.

• yes;
• maybe;
• not sure.

Field 20: Commercial requirement summary

Use one free-text field.

Recommended prompt: Briefly describe the security service you need.

This catches the information the structured fields miss.

What not to ask on the public form

Do not collect:

The first form is for commercial qualification.

Sensitive operational information belongs later in the approved process.

• access codes;
• alarm PINs;
• CCTV passwords;
• guard patrol routes;
• emergency response plans;
• exact vulnerable entrances;
• key locations;
• post orders;
• incident evidence;
• staff personal data;
• sensitive site drawings.

Should the form ask for budget?

It depends on the company's sales process.

A budget range may help some firms qualify opportunities.

For other guarding contracts, staffing and compliance requirements matter more than buyer budget.

If used:

• make it optional;
• explain why;
• use realistic ranges;
• do not turn the budget into the quote.

Should the form ask for guard licence type?

Usually no.

The buyer should describe the service requirement.

The security company should decide the workforce eligibility and licence requirements after reviewing the contract and jurisdiction.

Do not make the customer design compliance.

Should the form ask for headcount?

It can be useful as an optional commercial input.

Use wording such as:

Approximate number of officers/posts, if already specified

Do not make it mandatory.

Many prospects are buying expertise because they do not yet know the correct staffing model.

Should buyers book guards online?

No, not as a normal public appointment.

A prospect can:

Actual guard deployment belongs after:

• submit an enquiry;
• request a quote;
• send an RFP;
• book a consultation or site discussion where appropriate.
• commercial review;
• contract;
• staffing;
• operations acceptance.

Enquiry vs RFP

Not every commercial lead has a formal tender.

Enquiry vs operational site setup

This distinction matters.

The public form can say:

Three warehouses, night coverage

The guard-operations system may later create:

Do not pre-create operational records from unqualified enquiries.

• Site A;
• Site B;
• Site C;
• posts;
• rotas;
• patrols;
• post orders.

Confirmation message

Do not say:

Your guards are booked.

unless that is literally true.

Safer wording:

Thanks. We received your commercial security enquiry. Our team will review the service, location and scope and contact you about the next step.

If the company has a real response-time policy, it can add it.

Do not invent one.

Connect the enquiry to ordinary client history

OneStudio can support:

Guard-management software should own:

• public enquiry;
• contact details;
• suitable consultation booking;
• reminders;
• ordinary client history;
• analytics.
• sites;
• posts;
• guards;
• shifts;
• GPS;
• patrols;
• incidents;
• operational reports;
• compliance;
• payroll.

A compact commercial security form

A practical first-stage form can include:

That is enough to create a serious first brief.

1. name;
2. company;
3. role;
4. work email;
5. phone;
6. site postcode/address;
7. number of sites;
8. sector;
9. service required;
10. one-off/temporary/ongoing;
11. preferred start date;
12. coverage hours;
13. approximate posts/guards if known;
14. RFP/specification status;
15. procurement deadline if applicable;
16. short commercial requirement.

Collect enough to price the conversation, not run the shift

The best public form gives the commercial team a usable brief without collecting the operational security plan.

That is the balance:

site + service + scale + timing + procurement context

Then the right people can take over.

Explore OneStudio features, compare plans, or review the turnkey website service.

Questions businesses ask