Pre-Manufactured Value has quietly shifted from a niche acronym to a line in UK tender return templates. For MMC bids, clients and frameworks increasingly expect a clear, defensible PMV calculation that shows how much of the scheme is delivered offsite, by package and by MMC category. Manual spreadsheets built the night before submission can’t keep up with shifting models, package splits and supplier quotes. Automating the PMV pipeline from model and estimate to evidence pack is fast becoming a competitive necessity.
TL;DR
/>
– Treat PMV as a data pipeline linking model, BoQ and supplier scopes, not a single spreadsheet tab.
– Classify elements consistently (e.g., Uniclass) and map them to MMC categories and an agreed PMV rule set.
– Automate with lightweight scripts/Power Query/IFC properties and keep an audit trail of overrides.
– Lock the denominator early (what counts as “project value”) and prevent double counting across packages.
– Produce a clear evidence pack: rules, data sources, assumptions, and supplier confirmations.
The moving parts behind PMV in MMC bids
/> At its core, PMV is a ratio: the value of pre-manufactured components and processes over the value of the project scope being measured. In UK tenders that emphasise MMC, clients usually ask for a breakdown by MMC categories (for example, volumetric modules, panelised systems, sub-assemblies, MEP modules) along with narrative on what’s offsite and why. The denominator is where many teams stumble—some clients mean construction cost only, excluding prelims and fees; others expect a wider basket. Establish that definition early, write it down, and make sure everyone applies it the same way.
Two data structures make PMV calculable at scale. First, a consistent classification and element ID scheme in the model and take-off (Uniclass is common in the UK and works well). Second, a package-aligned estimate with cost codes that can carry flags such as “offsite portion”, “MMC category” and “evidence link”. With those in place, you can automate the mapping from model/BoQ items to the PMV numerator and denominator with fewer heroic last-minute edits.
PMV is not only about finished assemblies. Factories may handle framing, MEP skids, bathroom pods, façade cassettes, stair cores, riser modules, and even process tasks like pre-applied firestopping or factory-installed QA. Your ruleset needs to capture both product and process that genuinely shift value offsite.
How automation actually works between model, estimate and evidence
/> A practical automation flow for a UK tender looks like this:
– Start with a federated model or reliable IFC export, where elements are classified and have a stable ID. Add custom properties to tag intended MMC category and an “offsite proportion” field, even if initially defaulted.
– Link the estimate to the model via element IDs or classification codes. If you can’t fully link, create a mapping table that pairs BoQ line items to model categories and packages.
– Create a PMV rules table that translates classifications and scopes into numerator/denominator treatments. For example, façade cassettes delivered as panels contribute their offsite portion to the numerator; site-installed brackets may sit in the denominator only.
– Automate data pulls using Power Query or scripts: ingest the model schedule/IFC properties, the estimate export, and the rules table; join them; calculate PMV at element, package and project level; and output a dashboard plus a line-by-line audit sheet.
– Validate with suppliers. Replace provisional offsite proportions with values agreed in pre-tender clarifications and capture the email or technical submittal link in your evidence column.
– Lock a snapshot for submission, but keep the pipeline live for post-tender clarifications. Version control the ruleset and inputs so that you can show exactly what changed and why.
For many teams, this can be built with everyday tools: IFC exports or model schedules; Excel with Power Query and named ranges; a shared rules workbook; and a simple Power BI view for the bid room. Where models are mature, visual scripting (e.g., Dynamo or similar) can write MMC tags back to elements so the design team owns the classification rather than the estimator carrying it alone.
A tender-room scenario: automating PMV on a housing mid-rise
/> A main contractor is bidding a 12-storey residential block for a northern housing provider. The client wants an MMC narrative and a PMV return split by categories, with pods, façade panels and MEP skids in play. The design manager has a federated model but MEP is late, the estimator’s BoQ sits in a cost tool, and the bathroom pod supplier has issued a scope matrix that doesn’t line up neatly with the model zones. The bid manager is up against a Friday noon submission and needs the PMV to tally with the prelims and programme narrative. The digital lead builds a Power Query pipeline: imports the model element schedule with Uniclass codes, the BoQ export by cost code, and a simple mapping sheet that assigns “MMC category” and “offsite proportion by line”. They reconcile clashes at package boundaries—pods including MEP connections up to isolation valves, façade panels excluding site rails—and attach the supplier confirmation emails as hyperlinks. By Thursday evening, the PMV dashboard updates automatically when the design team reissues the bathroom layout, giving the bid team confidence to finalise the narrative without copy-pasting figures between tabs.
Where PMV automation trips teams up, and how to steady it
/> Double counting sits at the heart of most disputes. Interfaces between factory scope and site-assembled items (e.g., pod MEP tails, façade brackets, acoustic treatments) can appear in multiple packages. Your rules table should allocate interfaces explicitly to either numerator or denominator and reference the package responsible.
Prelims and temporary works rarely get consistent treatment. Some clients insist they are outside PMV; others see factory-side prelims as within the numerator where they are integral to the offsite process. Document your interpretation in the assumptions and provide a sensitivity view if needed.
Supplier marketing can get ahead of commercial reality. Tie the offsite proportion to priced scope and measurable deliverables, not brochure claims. Ask suppliers to state exclusions and the site interfaces they expect your team to complete.
Finally, change control matters. Late design shifts can reshuffle scope between offsite and site. An automated pipeline with versioning lets you re-baseline quickly and show your workings, which is often the difference between a scored submission and a clarification loop.
# Common mistakes
/>
– Treating PMV as a model-only calculation and ignoring the estimate. Without cost alignment, percentages look neat but won’t match the commercial return.
– Leaving the denominator vague. If prelims, fees or contingencies float in and out, PMV swings wildly between drafts and destroys credibility.
– Tagging elements inconsistently across disciplines. Architectural panels marked as MMC while structural supports remain untagged will skew the ratio and trigger challenges.
– Relying on manual overrides without an audit trail. When someone tweaks a cell at 23:00, you need a comment and a link to the evidence or you own the risk in post-tender.
Pre-bid PMV automation checklist
/>
– Fix the PMV denominator in writing and get client-side confirmation on inclusions/exclusions.
– Build a one-page PMV rules matrix mapping Uniclass/BoQ lines to MMC categories and numerator/denominator logic.
– Add MMC and offsite proportion properties to model elements or create a stable mapping table if models are immature.
– Establish a single source of truth for supplier scope confirmations, with hyperlinks captured against each affected line.
– Set up an automated data pull (Power Query/script) and a refreshable dashboard that reports by package and MMC category.
– Run a pilot on one block or typical floor to shake out double counts and interface gaps before scaling to the full scheme.
– Freeze a submission snapshot and archive inputs, rules and outputs for post-tender queries.
What “good” looks like to a technical evaluator
/> A clean PMV submission reads like a mini technical file: a clear definition of the denominator; a table of MMC categories with examples used on the scheme; a package-by-package PMV breakdown that reconciles to the cost summary; and hyperlinks to supplier confirmations and drawings. The numbers update coherently if a drawing revision lands, and any overrides are justified by a cited assumption. The narrative describes how factory QA, logistics and site interfaces will uphold the stated offsite scope, aligning with programme benefits and risk reduction rather than hard-selling. In short, it’s consistent, auditable and anchored in buildable scope.
As MMC continues to normalise across UK housing and public frameworks, expect tighter data schemas and more prescriptive PMV templates. Teams that industrialise their PMV pipeline now will spend bid week on strategy, not spreadsheet archaeology.
FAQ
/>
How do clients usually want PMV evidenced in tenders?
Most ask for a numerical PMV percentage supported by a breakdown per MMC category and package. They typically expect a short narrative and an evidence pack referencing drawings, supplier scope matrices and assumptions. The stronger submissions link back to a classification system and show an audit trail for any manual assumptions.
# What data structures make PMV automation feasible?
/> A model or take-off aligned to a consistent classification like Uniclass and a cost plan with stable codes are the backbone. Add fields for MMC category and offsite proportion at line level, and maintain a rules matrix that maps those fields into the PMV numerator/denominator. With that in place, simple queries can recalc PMV across revisions without hand-editing.
# How should teams handle PMV when the design changes late?
/> Keep a versioned pipeline rather than a static spreadsheet. When a change lands, refresh the inputs, tag new elements or update the mapping, and regenerate the outputs with a new timestamp. Include a short change note so evaluators can see what moved and why, which reduces clarification cycles.
# Who owns PMV data and who signs it off?
/> On contractor-led bids, the estimator or bid commercial lead usually owns the PMV figure, with inputs from design and key suppliers. Sign-off often sits with the bid manager or commercial director, backed by an evidence pack. Clarify early if the client expects a consultant or manufacturer letter to corroborate specific offsite proportions.
# Does automating PMV change how packages are procured?
/> It often nudges teams to define package interfaces more cleanly and to secure early supplier input on scope splits. Clear scopes reduce double counting and help protect the PMV position through later design development. You may also adjust package splits to align with factory workflows, provided it doesn’t undermine competition or create site coordination risk.
