Projavio is in private beta | applications now open for UK construction consultancies.

Module · Procurement

Tender to award to PCSR - one workflow.

Define procurement packages, build tender packs, issue to selected suppliers, capture returns, award, commit to the PCSR. End-to-end procurement that doesn't live in a folder.

projavio.app/projects/imperial-house/procurement

Procurement

Imperial House - 47 packages · £1.36m committed

3 in tender11 awarded22 on site
PkgTradeValueTenderersStatus
P-01Demolition & Strip-Out£124,3004Closed
P-02Groundworks£186,5005On Site
P-03Frame & Deck£312,8004On Site
P-04Mechanical & Electrical£412,8003Awarded
P-05Curtain Walling£228,0004Mobilising
P-06Joinery & Finishes£94,2006In Tender
Showing 6 of 47 packagesNext award due: 5 Nov

Why procurement leaks value

Procurement runs in folders, spreadsheets, and email - and the value leaks out at every step.

A package is defined in one workbook, tender pack assembled across two folders, sent via email, returns collated in another spreadsheet, awarded by phone, captured (eventually) in the PCSR. Each step loses information; the final answer is "how did we end up at this number?".

Tender pack assembly takes a day per package

Pull BoQ from the take-off; pull drawings from the design folder; pull conditions from the contract template; assemble; email. Half a day per package, repeated for 12 packages per project.

Supplier returns collation is manual

Six suppliers return in different formats. Someone re-keys them into a comparison spreadsheet. The comparison is a snapshot - by the time it's done, two more returns have arrived.

Award doesn't hit the PCSR until next month

Variation approved, supplier confirmed, but the PCSR's committed column doesn't update until the next monthly QS pass. Cost forecast lags reality by weeks.

What's inside

A workflow from package definition to PCSR commitment.

Package definition

Define procurement packages with BoQ, drawings, conditions, programme constraints. Reads from measuring + estimates so no re-keying.

Tender pack generation

Generate tender packs combining BoQ + drawings + conditions + form of tender. Issue to selected suppliers in one click.

Supplier returns capture

Suppliers return via the supplier portal (token-link, no account needed). Returns land in Projavio in a comparable shape - not 6 different file formats.

Side-by-side comparison

Compare returns side-by-side, line-by-line. Highlight the line items that vary most. Pick the winner with full evidence.

Award + PCSR commitment

Award a package and the PCSR's committed column updates the same second. No monthly lag; the cost report tracks reality.

Purchase order issue

Generate the PO from the awarded package. The PO carries the awarded value into the PCSR; supplier history accumulates in the supplier directory.

Who uses it

Built for the people running procurement - and the supply chain on the other end.

Quantity Surveyors

Define packages, send tender packs, capture returns, award - in one tool. The PCSR updates as you award, not at next month's pass.

Procurement / Commercial

Cross-project procurement visibility. Which packages are still un-awarded? Which suppliers are scoring well across recent tenders?

Suppliers

Receive a tender pack via a clean token link. Submit a return in the supplied format. Get notified of the award decision. No fighting with the consultant's file naming conventions.

See procurement run end-to-end on a real package.

A 30-minute walkthrough - bring a package definition; we'll run it through to award.

Frequently asked questions

Can suppliers submit returns without a Projavio account?

Yes - suppliers receive a token link to view the tender pack and submit a return. No account, no friction. Returns land in Projavio in a comparable shape.

Is the supplier directory shared with procurement?

Yes - every tender history populates the supplier directory. Past performance, win rates, governance status surface when you build the next shortlist.

Does Projavio handle PO generation and tracking?

Yes - POs are issued from awarded packages and tracked through the project. PO commitment flows into the PCSR's committed column automatically.

Can we customise the tender pack template?

Workspace-managed tender pack templates are on the roadmap. Today the standard pack assembly handles BoQ, drawings, conditions and form of tender.

Stop running procurement out of folders.

One workflow from package definition to PCSR commitment. Audit trail intact, value preserved.