Subcontract Partnership Operations

Security companies often rely on trusted partners to extend their coverage. A guarding business may need a keyholding or mobile response provider in an area where it does not operate directly, while a regional supplier may have the local people, vehicles and knowledge needed to deliver the service well. The challenge is making that relationship feel joined up without blurring responsibilities or opening one company's system to another.

GMS Partnerships provides a controlled way for two security businesses to work together on subcontracted response services. Each company continues to manage its own operation, but approved sites and incidents can move between them through a clear partnership workflow. The requesting company keeps its client relationship and process; the service provider receives the operational work it has agreed to undertake.

Once the relationship and sites have been set up, everyday use is deliberately simple. Controllers work from the familiar incident and dispatch screens, the remote supplier works inside its own GMS environment, and the important response information comes back into the requesting company's incident record.

The partnership begins with an invitation between two companies that have enabled the module. The requesting company identifies the service provider and creates a one-use invitation key with an expiry date. The invited provider confirms that it is willing to deliver services before the relationship can be used operationally.

Both sides can see the partnership in a shared register, together with its role, status and linked sites. The service provider chooses the client record under which the incoming work will be managed in its own system. This creates a clear commercial and operational home for the relationship without giving either company general access to the other's data.

Once the approvals are complete, the partnership becomes part of the normal workflow. There is no need for controllers to remember a separate portal, forward every instruction manually or maintain a second spreadsheet of subcontracted sites.

The requesting company creates and manages its client site in GMS as normal, then assigns it to a partner-serviced region and requests provision from the chosen service company. The request includes the key site information needed for the provider to review the location, rather than relying on an informal email or telephone handover.

The provider can review each request and accept or decline it. When accepted, GMS creates the provider's own linked site record beneath the client record selected for the partnership, ready for the provider to complete its local operational setup. The two site records remain separately owned but are connected by a controlled mapping, so both companies can reconcile the relationship without maintaining duplicate reference lists by hand.

Current, pending, declined and cancelled relationships remain easy to understand from the Partnerships page. Both sides can see which sites are live and which still need attention, helping the initial setup stay organised even where several locations are being transferred.

When something happens, the requesting company logs the incident in its own GMS system just as it would for a directly delivered service. If the site has a live partnership link, the normal dispatch area presents a clear Send to Partner action with the service provider's name.

Selecting that option checks the live partnership and site mapping before creating a corresponding incident inside the provider's company account. The provider sees the job against its own linked site and client record, using the incoming incident category and workflow configured for partnership work. Controllers do not have to copy the incident into an email, re-enter it in somebody else's portal or hope that the right control room has received the message.

GMS also protects against an incident being handed over twice. If the same request has already created a provider incident, the existing linked record is recognised and retained rather than silently producing a duplicate job.

A partnership should connect the work, not merge two businesses. The provider's incident belongs to the provider, while the requesting company's incident remains part of its own client history. The provider can dispatch its own staff, manage its own operational notes and follow its established response procedure without the requesting company gaining control over those internal records.

This separation makes the module practical as well as secure. Staff see the tools and information appropriate to their own company, while GMS handles the approved hand-off in the background. Each business remains accountable for the part of the service it delivers.

Different providers have different control-room arrangements, so GMS does not force every partnership into the same dispatch model. A provider can allow incoming partner requests to create an incident for manual review, or it can allow GMS to attempt its normal response dispatch workflow automatically.

Where automatic dispatch is enabled, GMS uses the provider's own operational checks and dispatch process. If no suitable resource can be deployed automatically, the provider incident remains safely created and its control route is notified to log in and take over. That notification is deliberately a signpost rather than an email full of sensitive incident detail.

This gives both companies a useful balance: rapid hand-off where the operating model supports it, with clear human control where it does not.

Once the provider accepts and progresses the response, key milestones such as accepted, on scene and cleared are reflected back into the requesting company's incident. The response window can therefore be handled in the familiar incident, reporting and billing flow rather than being reconstructed later from a separate supplier timesheet.

The provider can also choose which operational notes are suitable for the client-facing record. Notes marked for reports are available to the requesting company and are clearly identified with the provider's name. Internal provider notes remain internal.

This controlled feedback reduces telephone chasing and gives the requesting company's team a much clearer answer when its client asks what happened, who attended and when the response was completed.

One of the strongest benefits of GMS Partnerships appears at the end of the incident. The requesting company can produce and send the report through its own normal process, directly from the incident record. It can download the PDF, send it to an individual client contact or send it to all of the relevant contacts already held in GMS.

The report carries the requesting company's name, logo and configured report styling, helping it present a consistent service to the end client. At the same time, partner response timings and report-visible supplier notes can be included, with the remote service provider clearly identified. The client receives one coherent report from the company it contracted, while still seeing who delivered the local response and what that supplier reported.

This removes an awkward administrative gap that often exists in subcontracted services. The requesting company does not need to wait for a differently branded supplier document, copy details into its own template or send two disconnected reports. The partner's contribution becomes part of the same controlled incident record and client communication flow.

GMS Partnerships is designed as a controlled integration between companies, not a shortcut around company separation. Normal screens and records remain company-specific. Cross-company activity takes place only through the approved partnership, site and incident links created for that purpose.

The requesting company cannot browse the provider's wider client list, staff records or internal incident notes. It cannot edit provider-owned notes or decide after the event that an internal supplier note should appear on a report. Only notes that the provider has already marked as report-visible are brought into the requesting company's incident and report view.

That means the information shared with the end client can be useful and transparent without opening the door to unrelated operational or commercially sensitive data.

Access to Partnerships is protected by authenticated user accounts, module settings and role permissions. Viewing a partnership and managing one are separate capabilities, while partner dispatch is controlled by its own company configuration.

Invitation keys are randomly generated, expire after a chosen period and are shown only when created. GMS stores a secure hash rather than retaining the readable key. Operational hand-offs are allowed only where the partnership and the individual site link are both live, and each cross-company action is tied to the relevant companies, user, time and status for traceability.

Public-facing references use the companies' published identifiers rather than exposing internal database IDs. If a partnership is cancelled, new site requests and incident hand-offs stop, but the historic records and audit trail are retained so previous activity does not simply disappear.

The real value of security company partnership software is not simply the ability to connect two accounts. It is the ability to make cooperation feel like part of the service rather than an exception to it. Sites are approved, incidents are handed over, progress is returned and client reports are produced without abandoning the normal GMS workflow.

For the requesting company, this means broader coverage without losing ownership of the client relationship. For the provider, it means clearer instructions and properly structured incoming work. For the end client, it means a consistent, professionally branded report that explains both the service delivered and the trusted partner behind it.