You need security services for a major project, but without a clear RFP, you’ll receive proposals that are impossible to compare and miss critical requirements. If you’re a project manager, procurement officer, or decision-maker overseeing major construction, mining, or infrastructure projects across Western Australia, writing a Security RFP for Your Next Major WA Project: What to Include starts with understanding how a well-structured request for proposal attracts qualified vendors and produces comparable, actionable proposals. After reading, you’ll know exactly what to include in your security RFP to ensure compliance, make fair comparisons, and reduce project risk through essential sections, WA-specific compliance requirements, evaluation criteria, and submission requirements that prevent unusable vendor responses.
Why Writing a Clear Security RFP Matters for Major WA Projects
A clear security RFP ensures you receive comparable, qualified proposals from vendors who understand your project requirements, which reduces procurement time, prevents cost overruns, and minimizes security gaps during project execution. When RFPs are vague, you end up with proposals that use different formats, omit critical details, and quote services that don’t match your actual needs. Comparing a 2-page quote against a 40-page proposal wastes evaluation time and often forces you back to vendors for clarification.
The RFP serves as your filter for attracting vendors with relevant experience in your industry. A mining operation near Kalgoorlie-Boulder has different security requirements than a METRONET construction site in metro Perth. When you specify your project type and location upfront, vendors without relevant experience self-select out, saving everyone time.
A structured security RFP protects your budget by defining scope and expectations before vendors price their services. Without clear boundaries on coverage hours, personnel numbers, or site access logistics, vendors either pad their quotes to cover unknowns or submit unrealistically low pricing that leads to change orders later.
WA project conditions require specific RFP language that generic templates miss. Remote sites between Port Hedland and Broome need vendors who can manage travel logistics and accommodation. Regional construction projects in Bunbury or Albany have different mobilization costs than metro work. Your RFP must address these factors so vendors can provide accurate, realistic pricing.
What to Do Before You Write Your Security RFP
Before writing your RFP, define your project security goals, identify site-specific risks and constraints, confirm your budget range, and establish who will evaluate proposals and what criteria matter most to your organization. This preparation prevents the need to reissue an RFP after receiving unusable responses.
Conduct an internal needs assessment. What assets need protection: equipment, materials, site infrastructure, personnel? What threats exist: theft, vandalism, unauthorized access, safety incidents? Review any previous security incidents on similar projects to understand patterns.
Identify your project context. Is the site in metro Perth, a regional center like Geraldton or Mandurah, or a remote location with limited access? Will security personnel need site-specific inductions for mining operations or hazardous area access? What communication infrastructure exists on site: reliable mobile coverage, two-way radios, satellite phones?
Clarify your decision-making process. Who will review proposals and participate in vendor interviews? What are your must-have requirements versus nice-to-have features? Who holds final approval authority and what budget limits apply?
Confirm your budget and timeline. Are you seeking cost comparisons to determine market rates, or evaluating value and capability within an established budget band? When must services commence, and does that allow realistic time for vendor mobilization?
Gather existing contracts or requirements that constrain your security RFP. Client contracts may mandate specific security levels. Insurance policies may require certain coverage types. Principal contractor obligations might dictate licensing, induction processes, or prequalification systems.
Need help defining your security requirements before issuing an RFP? Contact us to discuss your WA project and receive expert guidance on scope, compliance, and vendor selection.
Before reaching out, prepare:
- Project type, location, and duration (construction, mining, infrastructure, event)
- Required services (static guards, mobile patrols, access control, alarm response)
- Coverage hours and number of personnel needed
- Site-specific logistics (remote location, accommodation, travel, hazardous area access)
- Compliance and licensing requirements from clients or principals
- Anticipated contract start date and key project milestones
Project Overview and Background: Setting the Context
Your project overview should summarize your organization, the nature and location of the project, the reason for requiring security services, and any relevant background that helps vendors assess whether their capabilities align with your needs. Vendors use this section to decide whether to invest time in responding, so make it informative without disclosing commercially sensitive details.
Include a brief organizational profile. Describe your industry, company size, and project portfolio. A mining company that regularly operates in the Pilbara gives vendors context about your security expectations and site conditions. A developer working on commercial projects across Perth’s southern suburbs from Rockingham to Kwinana helps vendors understand your metro focus.
Describe the project in practical terms. State the project type: construction site, mining operation, infrastructure build, or major event. Specify the location with enough detail for vendors to assess mobilization: a specific suburb for metro projects, a regional town name, or the distance from the nearest major center for remote sites. Include project scale and duration.
Explain why you’re issuing a request for proposal security. Are you starting a new project, renewing an expiring contract, expanding scope beyond current arrangements, or responding to an incident that revealed security gaps? This context helps vendors understand your priorities.
Mention any principals, clients, or partners whose requirements flow down to security vendors. Major clients often mandate specific security standards, reporting formats, or contractor management systems. For mining security services, mine operators typically require vendors to meet site-specific safety protocols and emergency response procedures before remote sites will grant access.
Provide context on current security arrangements if you’re replacing or supplementing existing services. What’s working well that you want to continue? What gaps or issues prompted this RFP? Vendors can then position their proposals to address your specific pain points.
Scope of Work: Defining Exactly What You Need
The scope of work section must detail the specific security services required, coverage hours, number of personnel or patrols, site boundaries, assets to protect, and any special conditions like remote location logistics or hazardous area access. This section determines whether vendor proposals will be comparable or all over the map.
List the services you need. Static guards at entry points or specific assets? Mobile patrols covering multiple locations or large sites? Access control to verify personnel and vehicle entry? Alarm response for after-hours incidents? Loss prevention for high-value materials? Crowd control during busy site periods? Be specific about each service type.
Specify your coverage requirements. Do you need 24/7 security, business hours only, after-hours and weekends, or coverage that varies by project phase? Detail shift patterns if you have preferences: 12-hour shifts for remote sites, 8-hour shifts for metro locations, rotating rosters to maintain consistency.
Define the site boundaries and layout. Describe the physical area vendors must secure: fenced perimeter, multiple buildings, access points requiring monitoring, areas with restricted access due to hazards or sensitive operations. For large or complex sites, provide a site map.
Detail personnel requirements so vendors know what qualifications and certifications matter. How many guards per shift? Must they hold specific licenses: security agent, crowd controller, first aid? Do site conditions require additional training: working at heights, confined spaces, remote area first aid?
For mining and construction projects across WA’s regional areas, site-specific safety inductions are mandatory before personnel can enter.
Include logistical considerations that affect vendor costs and capability. Remote sites near Kalgoorlie-Boulder, Port Hedland, or Broome require vendors to arrange accommodation and manage travel logistics. Regional projects may need vehicles for mobile patrols. Consider seasonal weather that affects site access during the wet season in the north or winter storms in the south.
Clarify what’s out of scope to prevent vendors from including services you don’t need or excluding services you do. If you’re handling access control technology and only need personnel to monitor it, state that. If you need physical security but not cybersecurity or electronic surveillance system installation, make that clear.
WA Compliance, Licensing, and Regulatory Requirements
Your RFP must require vendors to confirm they hold current WA security licenses, meet WorkSafe and industry standards, carry appropriate insurance, and comply with any site-specific regulations such as mining or construction safety protocols. This section protects you from unqualified vendors and establishes baseline standards for all proposals.
Require proof of WA security agent licenses for all personnel providing security services. If crowd control is part of the scope, require crowd controller licenses. Vendors should provide license numbers and expiry dates, with copies available on request.
Request evidence of insurance coverage. Public liability insurance protects you if security activities cause third-party injury or property damage. Workers’ compensation covers security personnel if injured on your site. Professional indemnity insurance covers errors or omissions in security services. Specify minimum coverage amounts if your contract or insurance broker mandates them.
Specify compliance with WorkSafe WA and relevant industry codes. Construction sites must meet construction safety regulations. Mining operations follow mine-specific safety management plans. Infrastructure projects may have principal contractor requirements that flow to all subcontractors including security vendors.
Ask for quality certifications or memberships in professional security associations. While not mandatory, certifications demonstrate a vendor’s commitment to standards and ongoing professional development. Industry associations often require members to maintain insurance and comply with codes of conduct.
Include any client-mandated requirements. Principal contractors on large projects often require security vendors to complete prequalification processes, site inductions, and contractor management system registrations before mobilization.
When choosing a qualified security company, understanding these baseline compliance requirements helps you assess which vendors have experience meeting similar standards.
For remote or mining sites, require evidence of personnel training for isolated locations. Remote area first aid, emergency response procedures, hazardous area awareness, and site-specific safety training may all be prerequisites before personnel can access your project site.
Vendor Experience and Capability Requirements
Require vendors to demonstrate relevant project experience by providing case studies, client references, and examples of similar projects in scale, industry, or location, particularly for regional or remote WA sites with unique challenges. Experience requirements filter vendors who can deliver versus those who want to learn on your project.
Ask for examples of similar projects. Security for a construction site differs from mining operations or infrastructure builds. Request case studies that match your project type, showing vendors understand the specific challenges and requirements. Include details on project scale, duration, services provided, and outcomes achieved.
Request client references with contact details and permission to follow up. Require at least three recent references, ideally from projects similar to yours in size, location, or industry. Specify what information you’ll seek from references: service quality, responsiveness to issues, staff professionalism, contract compliance.
Require proof of experience in your project location or similar environments. A vendor with metro Perth experience may not have the systems to support remote operations. Conversely, a vendor experienced in Pilbara mining sites can certainly handle metro projects but should demonstrate they understand urban project constraints like noise, access, and community relations.
Ask how vendors handle common challenges. How do they manage personnel turnover while maintaining service continuity? How do they ensure reliable coverage for remote site logistics when weather closes roads or cancels flights? What’s their emergency response protocol if an incident occurs?
Request details on their personnel and operations. What’s their team size and do they have capacity for your project? Describe their recruitment process and how they screen personnel. What training programs do they provide beyond mandatory licensing? What’s their average staff retention rate, particularly for regional or remote assignments?
Include questions about technology and equipment. How do they track patrols and verify guards are where they should be? What incident reporting systems do they use and what access will you have to reports? What communication systems do they provide: two-way radios, mobile phones, satellite communication for remote areas?
Project Timeline, Milestones, and Mobilization
Clearly state your RFP response deadline, evaluation timeline, anticipated contract start date, project duration, and any key milestones or phases that will affect security requirements, so vendors can plan mobilization and resource allocation. Realistic timelines produce better proposals because vendors can properly resource their response and plan personnel deployment.
Provide the RFP issue date and response submission deadline. Allow sufficient time for vendors to review requirements, conduct site visits if needed, prepare detailed proposals, and submit questions during the Q&A period. Complex or remote projects need longer response windows than straightforward metro assignments.
Outline your evaluation process. When will you shortlist vendors? Will shortlisted vendors attend interviews or site visits? When do you expect to make your final decision? Being transparent about evaluation timing helps vendors plan for potential interviews and site visits.
Specify when services must commence and the expected contract duration. A firm start date lets vendors plan recruitment and inductions. Contract duration affects pricing: longer contracts may attract better rates, while short-term projects may carry premium pricing due to mobilization costs.
Detail any phased rollout. Does security need to start small and scale up as construction progresses? Will requirements change as you move from site establishment to active construction to demobilization?
Do seasonal factors affect security needs, such as increased activity during dry season access windows for remote northern sites?
Mention key project milestones that affect security. Phase changes in construction projects often mean new areas to secure or assets to protect. Shift changes in mining operations affect access control requirements. Seasonal peaks in infrastructure projects may require additional personnel during high-activity periods.
Allow realistic time for mobilization. Vendors need to recruit personnel if they don’t have available capacity, conduct license checks and background screening, arrange site-specific inductions, and complete any principal contractor prequalification. For regional projects in areas like Broome or Geraldton, personnel may need to relocate. Remote sites require travel booking and accommodation arrangements.
Budget Considerations and Pricing Structure
Request a detailed pricing breakdown that separates hourly rates, mobilization costs, equipment fees, travel allowances, and any additional charges, and specify whether you want fixed pricing, schedule of rates, or cost-plus arrangements. Clear pricing requirements enable genuine comparison rather than guessing what’s included in each vendor’s total.
Ask for itemized pricing. Request personnel rates broken down by role: guard rates, supervisor rates, mobile patrol officer rates. Specify how to quote overtime, public holiday loading, and weekend penalties. Different projects have different penalty rate exposures, so you need transparency to compare.
Request transparency on additional costs. What do vendors charge for uniforms, equipment, vehicles, fuel, and communication devices? For remote sites, what are the accommodation costs, travel allowances, and fly-in fly-out logistics? These costs can be substantial for regional and remote projects but often get buried in hourly rates, making comparison difficult.
Specify your preferred pricing model. Fixed price per shift provides budget certainty but less flexibility. Hourly rates give flexibility to adjust coverage but less cost predictability. Monthly retainers work for ongoing contracts with stable requirements. A schedule of rates listing prices for different services and times lets you mix and match as needs change.
Ask how pricing adjusts for scope changes. What happens if you need additional personnel during a project phase? How much notice do you need to give to add or reduce shifts? What are the rates for ad hoc or emergency call-outs outside scheduled coverage?
Request payment terms and invoicing frequency. Do vendors require payment on delivery, net 15 days, monthly in arrears, or other terms? How detailed are invoices: per shift, per person, itemized by service type? Clear payment terms help you manage cash flow and avoid disputes.
If you’re comparing vendors on value rather than lowest cost, make your evaluation criteria explicit. Vendors need to know whether you’ll choose the cheapest proposal or whether you weight experience, quality, and capability alongside price.
How to Write an RFP with Strong Evaluation Criteria and Weighting
Structure evaluation criteria by assigning percentage weightings to factors such as relevant experience, compliance and licensing, personnel quality and training, pricing and value, and responsiveness, then score each vendor’s proposal against these weighted criteria for objective comparison. Without defined criteria and weightings, evaluation becomes subjective and difficult to defend if challenged.
Decide what matters most to your project. Is price the primary factor because you have a tight budget and baseline security requirements? Do experience and quality outweigh cost because project risks are high or the site presents unique challenges?
Assign specific weightings to each criterion. Consider allocating weight across price, relevant experience, compliance and licensing, personnel quality and training programs, and vendor responsiveness during the RFP process. The total must add to 100 percent.
Define scoring rubrics for subjective selection criteria. What constitutes excellent versus adequate relevant experience: number of similar projects, size of projects, recency of projects, client satisfaction? What makes personnel quality high: training beyond minimum requirements, low turnover, qualifications beyond basic licensing? Document these definitions so all evaluators score consistently.
Communicate your weightings in the RFP. Vendors need to know what to emphasize in their proposals. If experience matters more than price, vendors will invest in detailed case studies and references rather than focusing solely on being the cheapest. Transparency also demonstrates fairness if your evaluation is later questioned.
Plan for a shortlist and interview stage if proposals are close or project complexity demands it. Interviews let you assess vendor professionalism, clarify ambiguous proposal sections, and gauge cultural fit. Site visits let vendors demonstrate their understanding of your project and propose specific solutions.
Document your evaluation process for transparency and audit purposes. Record individual evaluator scores, note key strengths and weaknesses of each proposal, and document how final rankings align with your weighted criteria. This documentation protects you if decisions are questioned internally or by unsuccessful vendors.
Submission Instructions and Response Format
Provide clear submission instructions including response format, page limits, required attachments (licenses, insurance, references), submission method (email, portal, hard copy), and a response template so all proposals follow the same format for easy comparison. When every vendor organizes their proposal differently, comparison takes twice as long.
Specify how to submit proposals. Provide an email address with required file formats (PDF, Word document, maximum file size). If you use an online procurement portal, include access instructions. If you require hard copies, state how many and where to deliver them. Include the time zone for deadline clarity.
Set a clear deadline. State both the date and specific time when proposals must arrive. Late submissions need a policy: will you reject them, accept them with point deductions, or review on a case-by-case basis?
Provide a response template or required structure. Request sections in a specific order: executive summary, company profile and experience, understanding of project and scope, methodology and approach, personnel and resources, compliance and licensing, pricing breakdown, references and case studies, appendices. Numbered sections matching your RFP sections make comparison straightforward.
List mandatory attachments vendors must include. Copies of WA security licenses, current insurance certificates, safety management plans, quality certifications, recent client references with contact details, case studies from similar projects, and organizational charts showing project team structure. Mark which attachments are mandatory versus optional.
Include page limits or word counts to keep responses concise and comparable. Long proposals aren’t better proposals. A 10-page limit for the main proposal plus appendices forces vendors to focus on relevant information and makes evaluation manageable.
Offer a Q&A period so vendors can clarify ambiguities before submitting proposals. Specify how to submit questions: email address, question format, deadline for questions. Commit to providing answers by a certain date, and issue answers as an addendum to all vendors who received the RFP. This ensures everyone works from the same information and maintains competitive fairness.
Common Mistakes to Avoid When Writing Your Security RFP
Common mistakes include vague scope definitions, omitting site-specific details, failing to specify compliance requirements, unclear evaluation criteria, unrealistic timelines, and not allowing vendors to ask questions, all of which produce poor-quality or incomparable proposals. Learning from these mistakes before issuing your security project proposal saves time and frustration.
Being too vague is the most frequent problem. Writing “security services required” without defining what services, where exactly, when and for how long, and how many personnel produces proposals that quote everything from a single guard to a comprehensive security program. Vendors can’t price what you haven’t defined.
Understanding the range of security services available helps you specify exactly what you need.
Omitting critical project context leads to unrealistic proposals. Remote location logistics matter: how far from the nearest town, what accommodation exists, what travel options work when weather closes roads? Hazardous area access requirements affect which personnel qualify. Seasonal weather in northern WA affects site access and security operations during the wet season.
Failing to specify mandatory compliance and licensing requirements lets unqualified vendors respond. You waste evaluation time reviewing proposals from vendors who can’t actually deliver because they lack licenses, insurance, or safety certifications. Make mandatory requirements clear in the opening section.
Setting unrealistic response or mobilization deadlines excludes capable vendors. If you issue an RFP on Friday and request responses by the following Wednesday, quality vendors already committed to other work may not have time to prepare a thorough proposal. If you need services to start three days after awarding the contract, vendors can’t recruit, induct, and mobilize personnel in time.
Not weighting evaluation criteria leads to subjective or inconsistent scoring. Without weightings, different evaluators prioritize different factors. One person focuses on price, another on experience, another on safety record. Weighted criteria align evaluators and make decisions defensible.
Closing off vendor questions prevents clarification of ambiguities. You may understand what you mean by “regular patrols” or “appropriate response time,” but vendors interpret these terms differently. A Q&A period lets vendors ask, you clarify once, and everyone responds to the same understanding.
Copying a generic template without adapting it to your RFP for security systems and project type wastes this opportunity. A template written for corporate office security in Sydney doesn’t address WA mining site logistics, regional construction challenges, or metro Perth infrastructure projects. Customize the template to your specific situation.
This guide focuses on security service RFPs for physical security: guards, patrols, access control. If your project requires cybersecurity, electronic surveillance system procurement, or integrated security technology platforms, your RFP will need additional technical specifications and vendor qualifications beyond this checklist.
Perth Security and Guard Services customizes security plans for major projects across WA, from metro construction sites to remote mining operations in Kalgoorlie-Boulder and Port Hedland, helping clients define scope and compliance requirements during the procurement planning stage.
Planning a major project in WA and need expert security services? Contact Perth Security and Guard Services to discuss your requirements and receive a tailored proposal.
Frequently Asked Questions
What should you include in an RFP for security services?
Include a project overview, detailed scope of work, compliance and licensing requirements, vendor requirements, project timeline, budget and pricing structure, evaluation criteria with weightings, and clear submission instructions with a response template.
How long should vendors have to respond to a security RFP?
Allow vendors at least two to three weeks to respond, especially for complex or remote projects requiring site visits or detailed resourcing plans. Include a Q&A period midway through the response window.
What licenses and compliance should a WA security vendor demonstrate?
Vendors must hold current WA security agent licenses, appropriate insurance (liability, workers’ compensation, professional indemnity), and comply with WorkSafe WA and industry-specific standards such as mining or construction safety protocols.
Should I include my budget in the RFP or ask for vendor pricing?
Either approach works. Stating a budget band helps vendors tailor proposals to your financial reality. Asking for vendor pricing without disclosing budget lets you compare market rates but may produce quotes outside your range.
How do I compare security vendor proposals objectively?
Use weighted evaluation criteria and score each proposal against these factors. Document scores and justifications for transparency. Common criteria include price, relevant experience, compliance requirements, personnel quality, and responsiveness.
What project details matter most for regional or remote WA sites?
Specify exact location, access logistics, accommodation availability, travel distances, communication infrastructure, emergency response times, and any hazardous area or site-specific safety inductions required for personnel.