Architectural Services Framework

NFP provides a compliant route to market through pre-procured frameworks and DPS solutions. Our Step 1–4 process is a simple, standard route from initial engagement through to awarding a call-off contract.

In most cases, yes. The process is designed to keep call-offs consistent, auditable, and aligned to the framework rules. If your requirement needs a tailored approach (e.g., urgent mobilisation), we’ll confirm the compliant route.

Yes. NFP frameworks are procured in accordance with the relevant UK regulations applicable at the time they were tendered (e.g., PCR 2015 for earlier frameworks and Procurement Act 2023 for newer ones). Each framework page or documentation set will confirm the applicable basis.

Typically: housing associations, local authorities, public bodies, contracting authorities, and other eligible organisations that are permitted to access the framework.

Step 1 is a Confidentiality Agreement (NDA). It allows NFP to share additional information that may be commercially sensitive—such as supplier details, pricing structures, benchmarking, draft documentation, and procurement support materials.

Because some information we provide could prejudice suppliers commercially or compromise a live/anticipated procurement if shared more widely. The NDA ensures information is controlled, used appropriately, and only for the intended purpose.

A person authorised by your organisation (e.g., procurement lead, finance director, asset director, head of service). If your internal governance requires it, your legal team may also review it first.

Typically, yes—both parties commit to handling shared information appropriately. (If your version is one-way, you can swap this line accordingly.)

As stated in the NDA. Many NDAs specify a period (e.g., 2–5 years) and/or continuing obligations for truly confidential information.

We can share the next-stage pack (Step 2 materials), including call-off guidance, supplier shortlists by lot/region, templates, and any commercially sensitive supporting information required to progress.

We will respond to you within 30 minutes during working hours. If you haven’t heard, please check your spam filter or message us on live chat.

Step 2 is the Specification. This is a password-protected document.

Because it may include commercially sensitive content and is shared under the confidentiality provisions in Step 1.

Our team will email you the password separately, once Step 1 has been completed.

If you do not receive the password within 40 minutes, please:

• Check your spam/junk folder, and

• Contact us so we can resend or provide it by an alternative method.

It is a performance specification designed to help you define outcomes and service standards, rather than prescribing a specific method.

Yes. The Step 2 performance specification can be used as a guide for setting your own requirements.

You can use it to support your requirement under:

• Direct Selection

• Automatic Award

• Competitive Selection

(We’ll confirm which approach applies to your chosen framework/lot and help you apply the correct process.)

Step 3 is the Cost Model. This is an indicative model showing the typical market rates available via the framework or DPS.

No. It is indicative—intended to help you benchmark and understand market ranges. Final pricing will depend on your scope, volumes, locations, risk profile, and the call-off route used.

Common uses include:

• Budget planning and early-stage benchmarking

• Informing your own pricing schedule for a mini-competition

• Sense-checking supplier submissions (where applicable)

• Supporting value-for-money discussions and approvals

Not necessarily. Rates may vary between suppliers and may change over time. The model is provided to give a realistic indication of the market available through the framework/DPS.

Step 4 is where you complete the call-off (Direct Selection / Automatic Award / Competitive Selection as applicable), make the award, and mobilise the supplier.

This depends on the framework/DPS rules. We will confirm the correct documentation and call-off approach for your requirement.