1. Write the requirement before collecting proposals.
Start with the property, location, proposed schedule, and the responsibilities you want covered. Identify what already belongs to your reception team, facilities staff, landlord, or other providers. A company cannot price or explain a meaningful role if the brief simply says “provide security.”
Use the site brief guide to assemble the basics. Keep it short enough that the people making the decision can understand it. For a portfolio, use a separate entry for each location rather than hiding the differences in a single total.
2. Compare the same type of presence.
A fixed onsite role and mobile patrol are different arrangements. Ask where the person or team would be assigned, what the schedule covers, and what the proposal does not include.
Do not infer continuous coverage from a phrase such as regular patrol. Likewise, do not assume an onsite post includes every building-management task. The written scope should make the distinction clear enough that a new manager can understand it later.
3. Ask for relevant evidence, not borrowed prestige.
Discuss the credentials, experience, and documentation relevant to the actual location and duties. A recognizable logo, impressive photograph, or general statement about professionalism is not evidence of suitability for your particular engagement.
References and case examples should be shared with appropriate permission. Ask what can be substantiated, what is confidential, and what needs to be confirmed. You should not have to guess whether a claim describes the company, one individual, or a proposed future capability.
4. Understand who owns the assignment.
Ask who clarifies instructions, who handles a change in the schedule, and who receives a concern. A sales contact and an operational contact may have different roles. The point is not the title; it is knowing where a decision belongs.
Discuss the communication expected during ordinary service and when an issue needs attention. Avoid promises so broad that nobody can explain how they will be fulfilled. Ask what the proposal says about matters outside the agreed scope.
5. Read the commercial assumptions.
Compare the proposed dates, hours, duties, exclusions, and process for changes alongside the price. Note any assumptions that would alter the arrangement if the property, schedule, or required role changes.
Request clarification from the appropriate professional before accepting terms you do not understand. This guide is a planning aid, not legal advice or a substitute for reviewing a contract and the requirements of the actual assignment.
6. Decide how the service will be reviewed.
Before the work starts, agree on useful review questions: Was the defined role delivered? Were relevant observations communicated? Did instructions reach the right people? Has the property changed enough to require a new scope?
Use the service review guide to structure that discussion. Good comparison continues after selection. It should help you distinguish a delivery issue from a maintenance issue, an unclear policy, or a genuinely new requirement.
Where do you need support?
Review the regional information, then confirm availability and assignment requirements directly.
