Authenticated access
Demand Partner records are not intended to be available through anonymous public browsing.
Demand Partner security
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
Demand Partner activity is tied to an organisation and its authorised users. Team access should reflect each person’s role and current membership status.
Demand Partner records are not intended to be available through anonymous public browsing.
Requests, pools and assignments belong to the relevant Demand Partner organisation.
Access can be limited to active authorised organisation users rather than a shared public identity.
Contractor information
An organisation works with businesses in its controlled contractor pools. Businesses should only see information appropriate to their opportunity or assignment.
The contractor pool is an operating group, not a public directory.
Service, area, eligibility and capacity rules limit which businesses receive an offer.
The controlled sequence does not require businesses to browse named competing contractors or public bids.
Customer information
Privacy-safe request details support matching. Customer identity and contact fields are held separately and released only through the controlled assignment and authority rules.
The organisation identifies which contact fields are authorised for the work.
Contact access is associated with the assigned business, not every candidate.
The model records organisation authority confirmation rather than assuming direct customer consent in every case.
Work routing
Requests move inside the relevant approved pool. Exclusive, time-limited offers avoid an uncontrolled simultaneous race and support one final assignment.
Only businesses meeting the relevant rules should enter the candidate sequence.
Request and offer locks help prevent conflicting parallel assignment.
A request can remain unplaced when suitable capacity is unavailable.
Auditability
Request versions, offer states, acceptance, assignment, contact access and outcomes can be recorded to support operations, troubleshooting and accountability.
Status and timestamps show how the request progressed.
Assignment records identify authorised fields and contact-access status.
Completion, cancellation and unplaced outcomes remain distinct.
Controlled rollout
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