Every working day
The 5pm report
- What was done today
- What's planned tomorrow
- A minimum of six dated photos
- Any blocker raised, with an owner and a deadline
- Pushed by email, kept on the dashboard
10
Years of London
project deliveryBattle-tested · operational
project deliveryBattle-tested · operational
Why this structure exists
The delivery structure that survived ten years of London projects.
Every other model was tested and dropped. The single-foreman-six-sites model. The general-foreman-no-QA model. The marketplace gig model. What’s on this page is what stayed — refined job after job until it consistently held quality, programme and price across loft conversions, extensions, basements, full renovations and commercial fit-outs.
It’s the most efficient structure we’ve found, and we keep using it because the numbers keep proving it: higher first-time QA pass rate, fewer programme overruns, fewer post-handover snags than any model we ran before it. Not a marketing structure — an operational one.
- Capped capacity
- Daily reporting
- Independent QA
- One named PM
- Founder-led escalation
What an M2 Manager is
A vetted specialist crew. Run inside the 2VP system.
Most London builders run sites the same way: a single foreman juggles six or seven projects, and yours gets whatever attention is left over after the loudest client of the week. We don’t do that.
An M2 Manager is a vetted, accredited specialist crew that has passed our five-criteria onboarding and signed onto the 2VP Dashboard system. They lead site execution end-to-end — labour, sequencing, sub-trade coordination, snagging — under a contract that locks in price, programme and reporting cadence.
They never carry more than four 2VP projects at once. When they’re full, we mark them full and route the next job to another M2 Manager. Capacity is enforced by the dashboard, not by promise.
The 4-project rule
Focus is the mechanic — not a marketing line.
Quality on a London build comes from attention, not from talent alone. The fastest way to lose attention is to spread a manager across too many sites. We picked four because the calendar maths works: a single M2 Manager can physically be on each site for half a day a week, with buffer for issues — anything beyond four and that breaks.
At capacity — routed to next M2 ManagerHard cap. Enforced by the dashboard. No exceptions on busy weeks.
2VP Dashboard cadence
You’ll never wonder what’s happening on site.
Every M2 Manager runs the project on the 2VP Dashboard. Five working days a week, every site uploads what was done, what’s next, and dated photos before 5pm. Every Friday, the client walks the site with their PM. Every month, an audit lands in your inbox. The cadence isn’t aspirational — it’s the system.
Independent QA
The person checking the work doesn’t work for the person doing it.
The most common failure on a London build is silent: the foreman signs off his own work because there’s no one else to do it. We split the roles. The M2 Manager runs the build. A separate, salaried 2VP QA Manager checks it — and the QA Manager reports to 2VP HQ, never to the M2 Manager on the site they’re inspecting.
Builds
M2 Manager
Vetted specialist crew. Owns labour, sub-trades, sequencing, programme and daily reporting on this site.
Audited by
Independently checks
2VP QA Manager
Salaried by 2VP. Walks every active site weekly, signs every stage gate, and is paid the same whether they pass or fail the work — never the M2 Manager.
Pays
Stage payments — to 2VP only
You never pay the M2 Manager directly. Every stage release goes to 2VP, against a QA-signed milestone, against a fixed quote line.
Released by
Releases
Named PM (Founder-led escalation)
Your one named PM signs the release. If QA hasn’t passed the gate, the release doesn’t happen — and the founder is on every escalation.
Why this matters: the M2 Manager has every commercial reason to mark their own work “done.” Splitting QA into a separate role, paid by 2VP and not the crew, removes that conflict. Stage payments are gated on QA — not on the calendar, not on the foreman’s word.
How we vet M2 Managers
Five checks, in writing, before they touch your project.
An M2 Manager doesn’t get a 2VP project because someone vouched for them at the pub. Onboarding takes 4–6 weeks and most applicants don’t pass. These are the five checks, in the order we run them.
01
Insurance verified
Public liability minimum £5m, employer's liability £10m, contractor's all-risks in date — certificates checked annually with the underwriter, not just the broker.
02
Accreditation in writing
Trade-relevant: NICEIC for electrical, Gas Safe for gas, FENSA for windows, CSCS cards for site labour. Numbers logged. Expiry dates monitored.
03
References — three completed
Three client references on completed jobs of comparable scope, in the last 24 months. We call them, we ask the same eight questions, we record the answers.
04
Site visit — finished work
A 2VP QA Manager inspects a recently completed job in person. Joinery, plumbing detail, finish quality, snagging closure — all reviewed against our standard.
05
Financial stability check
Companies House filings, county court judgments, VAT registration, last two years of accounts. No mid-build cashflow surprises.
Staying on the panel
Performance is scored every month. Underperformance loses the panel seat.
Onboarding is the front door — it’s not enough on its own. Every M2 Manager carries a live performance score across four metrics. Slip on the score, and the next project doesn’t route to them. Slip twice, and the panel seat is gone.
01
Report compliance
% of working days with the 5pm dashboard report submitted on time, with photos. Target: 100%. Floor: 95%.
02
QA pass rate
% of stage gates passed first time by the independent QA Manager. Target: ≥85%. Floor: 70%.
03
Programme adherence
Days actual vs days quoted, by stage. Variance over 10% triggers a project review with the named PM.
04
Client rating
Weekly walk-through rating from the client (1–5). Average must hold ≥4.5 across last 5 jobs.
05
Snag closure speed
Average days from snag raised to snag closed and QA-signed. Target: ≤7 days during build, ≤14 post-handover.
What you see, as the client
The view from your side of the dashboard.
You don’t manage the M2 Manager. You don’t chase photos. You don’t reconcile invoices to the schedule. The system does that. Your job is to walk the site once a week and tell us if it feels right.
Every Friday
The site walk-through
- 30–45 minutes on site, with your named PM
- Walk every room, see every active work area
- Raise anything — finish, fit, materials, programme
- Actions logged the same day, owner and deadline assigned
- Rating: you score the week 1–5 on the dashboard
At every stage
The QA gate
- Independent QA Manager signs the stage
- You see the signed-off snag list before it closes
- Stage payment only releases after the gate is signed
- Five gates: strip-out · 1st fix · pre-plaster · 2nd fix · handover
- Founder signs the final handover personally
1
One named PM. One mobile number. The founder on every escalation.
If something on site doesn’t feel right, you don’t navigate a marketplace ticket queue or wait for a regional coordinator. You message your named 2VP PM. If the issue isn’t resolved within 24 hours, the founder is automatically copied — that escalation path is built into the dashboard, not a promise on a sales call.
Next step
Run your numbers, then meet the team that runs the system.
The calculator gives you a fixed-price estimate in 90 seconds. Request a quote and your named PM walks you through the M2 Manager and the independent QA Manager assigned to your project — before you sign anything.
FAQ
Questions homeowners ask about how the site is run.
Is the M2 Manager a 2VP employee or a subcontractor?
An M2 Manager is a vetted specialist crew contracted to 2VP — a single accountable entity, not a marketplace gig. They've passed our five-criteria onboarding, signed onto the 2VP Dashboard, and accepted our reporting and QA cadence in their contract. The 2VP PM, the QA Manager and the founder are all 2VP employees.
Why a maximum of four projects, not three or six?
Four is what the calendar supports. Each project needs roughly half a day a week of M2 Manager presence, plus buffer for issues — that fits four sites in a five-day week. Three is uneconomic and pushes prices up; six leaves no time for the issues that actually need a manager. Four is the maximum that keeps focus without inflating cost.
What stops the M2 Manager from secretly running other (non-2VP) jobs?
Two things. First, the contract: M2 Managers declare their full project load monthly. Second, the dashboard: a 2VP project missing the 5pm report compliance target triggers a review — and a manager who's overcommitted shows up in the metrics within two weeks, not two months. We've offboarded crews for this.
Is the QA Manager really independent if 2VP pays them?
The QA Manager is paid the same whether they pass or fail the M2 Manager’s work, and they don’t report into the M2 Manager. The structural conflict that the QA fix removes is the foreman signing off his own work. We don’t claim “fully external” — we claim “structurally separated,” and that’s the conflict that matters on a build.
Can I meet the M2 Manager and the QA Manager before signing?
Yes. Before contract, you'll meet the named PM, the proposed M2 Manager and the QA Manager assigned to your project. You see their accreditations, their last three references and a recent finished job — in person if it helps you decide.
What happens if I'm unhappy with the M2 Manager mid-project?
You raise it on the dashboard or with your named PM. The QA Manager runs an unscheduled audit within 48 hours. If the issue is real, the M2 Manager is replaced — at 2VP's cost, against the same fixed quote, with the programme rebaselined in writing. You're never left to argue with the crew.
Do I ever pay the M2 Manager directly?
No. Every payment goes to 2VP, against a QA-signed milestone, against a fixed quote line. The M2 Manager is paid by 2VP — not by you. That's how the QA gate has teeth.
Ready to see how this runs on your project?
Get a fixed-price estimate in 90 seconds, then a 30-minute call with a named PM to walk you through the M2 Manager assigned to your build — and the QA Manager who’ll sign every stage.