During a security service discussion, someone may say that an entrance is rarely used or that visitors normally arrive during office hours. Such information helps an initial assessment, but it should not become a fixed proposal input unless its period and basis are understood. A short visit to a site in Ankara may not represent the organisation's complete operating pattern.
Treat information as a service input
Sampson and Froehle's Unified Services Theory explains the distinctive role of customer-supplied inputs in service production. [1] Our practical application is to record the source and uncertainty of information supplied by the client. The study does not experimentally validate the form below or its effect on security outcomes.
NPSA's operational requirements approach also focuses on turning security needs into a clear, reviewable statement. [2] When applying it, distinguish what someone reported, what was observed during the visit and what was confirmed through a record.
Use four information states
An observation is something directly seen at a specified place and time. Reported information is an explanation supplied by a client representative or another person. An assumption is an unconfirmed point provisionally used to continue planning. Verified information is supported by a record with an identified source and scope.
These labels are not a numerical confidence score. Seeing no arrivals during a short visit may be a valid observation. Concluding that the entrance is unused throughout the day is a separate assumption. Do not combine them into one apparently established statement.
Record six fields
- Statement: What exactly is the information affecting service planning?
- Source and date: Who supplied it, or which record was used to check it?
- Scope: Which day, time period, area or operating period does it describe?
- Status: Is it an observation, reported information, an assumption or a verified record?
- Open question: What information is missing, and who will provide it?
- Decision effect: If the answer changes, which duty, working period or part of the proposal must be reconsidered?
Keep only information appropriate to the purpose of the discussion rather than exposing detailed protective arrangements to unnecessary recipients. More sensitive records can be examined through separate, authorised channels.
Work through one example
Suppose a representative at a hypothetical business centre says the service entrance is not used in the evening. If the visit takes place in the afternoon, this is not something the visiting team has directly observed. It can be recorded as the representative's explanation, with evening operating arrangements awaiting confirmation.
An authorised client representative can then clarify whether deliveries or maintenance activities create exceptions. If the answer changes, review the assignment and timing requirements before immediately adding a staffing figure. This prevents an uncertainty from the first meeting being carried silently into the contract.
The same reasoning applies to photographs or a sample log. Each can support a limited observation, but its date, coverage and relevance still matter. A convenient piece of evidence should not be made to answer a broader question than it actually covers.
Make the effect of assumptions visible
If a provider prepares a quotation using an unresolved assumption, identify that basis explicitly. The client can likewise acknowledge uncertainty rather than present incomplete information as settled fact. Assigning an owner and review date gives both parties a concrete follow-up task.
At the end of the assessment, “site inspected” is not enough. The record should show which information is settled, what remains open and which decisions depend on it. This supports a more explainable service plan without overstating what the visit established.
