Demand Partner security

Access follows the organisation, the request and the assignment.

Demand Partner is designed to limit information to the people and businesses entitled to use it at each stage. This page explains the product model without making unsupported certification claims.

Organisation access

Authenticated, team-controlled and organisation-scoped.

Demand Partner activity is tied to an organisation and its authorised users. Team access should reflect each person’s role and current membership status.

Authenticated access

Demand Partner records are not intended to be available through anonymous public browsing.

Organisation scope

Requests, pools and assignments belong to the relevant Demand Partner organisation.

Team control

Access can be limited to active authorised organisation users rather than a shared public identity.

Contractor information

Approved does not mean publicly exposed.

An organisation works with businesses in its controlled contractor pools. Businesses should only see information appropriate to their opportunity or assignment.

Private pool boundary

The contractor pool is an operating group, not a public directory.

Relevant opportunities

Service, area, eligibility and capacity rules limit which businesses receive an offer.

No competitor browse

The controlled sequence does not require businesses to browse named competing contractors or public bids.

Customer information

Customer contact details are not an open lead.

Privacy-safe request details support matching. Customer identity and contact fields are held separately and released only through the controlled assignment and authority rules.

Necessary information

The organisation identifies which contact fields are authorised for the work.

Stage-based release

Contact access is associated with the assigned business, not every candidate.

Authority recorded

The model records organisation authority confirmation rather than assuming direct customer consent in every case.

Work routing

Controlled offers replace public auctions.

Requests move inside the relevant approved pool. Exclusive, time-limited offers avoid an uncontrolled simultaneous race and support one final assignment.

Eligibility first

Only businesses meeting the relevant rules should enter the candidate sequence.

One active route

Request and offer locks help prevent conflicting parallel assignment.

No guarantee

A request can remain unplaced when suitable capacity is unavailable.

Auditability

Operational events can form a structured request history.

Request versions, offer states, acceptance, assignment, contact access and outcomes can be recorded to support operations, troubleshooting and accountability.

Traceable states

Status and timestamps show how the request progressed.

Access evidence

Assignment records identify authorised fields and contact-access status.

Outcome record

Completion, cancellation and unplaced outcomes remain distinct.

Controlled rollout

Apply for controlled pilot access.

Applications are reviewed, organisation-domain verification is required, and approval is not automatic.

Cookies on RelayLocal

Essential cookies keep RelayLocal working. Analytics run only if you allow them. Cookie Policy