Let’s discuss your
security requirements.

A useful first conversation

Start with what you need to protect

You do not need a finished security specification before getting in touch. Start with the setting and the concern that brought you here. You might be responsible for an event, a business premises, a residential property or a production. A short explanation of what is happening, where support is needed and the dates involved gives the team a useful starting point. If you are exploring options rather than ready to book, say so. The conversation can begin with the questions you are still trying to answer.

Describe the outcome you want in everyday language. For example, you may need a welcoming presence at an entrance, reassurance while a property is unoccupied, or help understanding which security measures are appropriate. It is more useful to explain the situation than to guess how many officers or which specialist service you should request. The scope and suitability of any proposed support can then be discussed against your actual requirements.

Include the practical details you already know

A location, approximate operating hours and expected start date help put an enquiry into context. For an event, include the event type and likely attendance if known. For a site, describe how it is used and whether the requirement concerns opening hours, overnight periods or a particular project. For a home or estate, a general location and an outline of the support required are enough to start. You can explain any uncertainty without delaying your first message.

Let us know whether you are enquiring for yourself, your organisation or a client, and who should receive the reply. Mention important decision dates, such as an event planning meeting or the start of a contract. If there is an existing specification, explain that it is available without pasting sensitive material into the form. Clear contact details matter too: check your email address and include a telephone number if you would prefer a conversation.

Keep sensitive information for the right conversation

Please keep an initial website enquiry proportionate. There is no need to include alarm codes, access credentials, detailed security weaknesses, identity documents or private information about other people. Explain the broad issue and ask how to discuss any sensitive operational details. A useful enquiry tells us enough to understand your request while leaving the finer detail for an appropriate direct conversation with the team.

If you are arranging support on behalf of an organisation, consider which information you are authorised to share. A general description of the premises or event will often be sufficient for the first exchange. Avoid including staff rotas, personal circumstances or confidential client documents simply to make your message more complete. Where information affects the proposed work, identify the topic so that the team can discuss what is actually needed.

Make the next step clear

Tell us what would help you most: a conversation about suitable services, clarification of a particular capability, or discussion of a defined requirement. If you have already spoken to Norvic, include a brief reference to that conversation so the new message has context. If your dates, location or requirements have changed since an earlier enquiry, summarise the changes rather than assuming the previous details still apply.

Before agreeing any work, make sure you understand the proposed scope, responsibilities, timings and costs. Useful questions include what is included, what information is still required and how changes would be handled. A website enquiry begins that discussion; it should not be treated as confirmation that personnel or dates have been reserved. Keep any subsequent written proposal and agreed arrangements together so everyone working on the requirement has the same information.

Choose the relevant route

For a course or learner booking, the training enquiry page provides a more direct starting point. Include the course you are considering and whether the enquiry is for an individual or a group. For operational security or medical support, use this contact page and describe the setting. If your requirement spans more than one area, explain how the parts fit together so the conversation can consider the overall plan.

If your enquiry covers several locations, describe how they relate to one another. A single event with separate venues may need a different conversation from unrelated sites operating on different schedules. Explain whether one person coordinates the whole requirement or whether each location has its own decision-maker. Include any dependencies you already know about, such as access being confirmed by a venue or dates awaiting approval. This helps the initial discussion focus on the parts that can be planned together.