Multi-location junk removal · Portfolio onboarding
Portfolio junk removal onboarding fixes a familiar problem. Most multi-property portfolios run on a patchwork of per-property vendor relationships accumulated over years of property-by-property hiring decisions. Per-pickup pricing varies. COI documentation is inconsistent. AP gets dozens of small invoices. The fix is a portfolio-onboarding engagement: one MSA, property-coded invoicing, COI rollup, and a single point of contact across the whole footprint.
A structured handoff from fragmented vendor coverage to consolidated single-vendor coverage across the portfolio. This is operationally distinct from rollouts (time-bounded program work). Onboarding is recurring portfolio coverage — the goal at the end of onboarding is steady-state ongoing service across every property in the portfolio under unified terms.
The most common starting point: a regional VP or operations director realizes they're managing 30+ vendor relationships across the portfolio for what should be one vendor relationship. The on-site managers at individual properties have no incentive to consolidate (their existing vendor works fine for their property), but the corporate operations team has every incentive (reduced AP burden, consistent COI documentation, predictable spend, single accountability).
On-site managers don't lose autonomy on day-of operational decisions. The MSA covers terms, pricing, and SLA; individual property managers still submit requests, communicate with the on-site Loader crew, and approve completion documentation. The change is in the back-office structure, not the day-of operations.
Most portfolio onboardings run on a 60-day cadence from initial conversation to first full-portfolio service month. The structure: weeks 1-2 are MSA negotiation and legal review, weeks 3-4 are portfolio inventory (every property identified, current vendor identified, transition timeline set), weeks 5-6 are pilot service at 5-10 properties to validate operational fit, weeks 7-8 are portfolio-wide rollout with property-by-property handoff from the prior vendor.
For larger portfolios (200+ properties), onboarding extends to 90 days with regional-by-regional rollout rather than portfolio-wide all at once. Each region hits steady-state before the next region begins handoff. This avoids overwhelming on-site managers and AP teams with simultaneous vendor changes across the whole footprint.
For portfolios with substantial geographic spread, regional account managers are assigned during onboarding so each on-site manager has a single point of contact for their region rather than calling a national 800 number.
Most portfolio AP teams want a single monthly invoice with property-level breakdown rather than per-property invoices. Property-coded invoicing sets up GL coding at MSA execution: property name, property address, internal property code, regional cost center, and any other coding needed for the portfolio's accounting structure.
Common AP integration patterns: direct CSV/Excel export matching the portfolio's ERP intake format (Yardi, RealPage, MRI for property management; SAP, Oracle, NetSuite for corporate), API integration where the portfolio runs on a modern AP automation platform, or PDF rollup with itemized property-level breakdown for portfolios still on paper-based AP.
Multi-property COI is one of the genuinely thorny problems in portfolio onboarding. Each property has its owning entity. Many properties have different owning entities even within the same management company. Some properties are co-owned with capital partners that need to be named. Some are mall properties or master-planned community properties with master-property COI requirements layered on top.
We work with your insurance broker on COI consolidation: single master COI naming all owning entities, all property addresses, and any required co-insureds. Renewal cycles align with the portfolio's broader insurance renewal rather than running a separate certificate cycle for our scope. For portfolios that add or remove properties during the year, we issue COI updates without requiring new master agreements.
Standard structure for ongoing portfolio relationships. Quarterly call with the regional or corporate team covering: volume trends across the portfolio, properties trending above or below tier-pricing assumptions, SLA performance metrics, any operational issues at specific properties, and forward-looking changes (acquisitions, dispositions, planned property reconfigurations).
Most portfolio teams use these reviews to identify opportunities — properties where additional services would make sense, regional patterns suggesting different SLA structures, properties where the volume tier should adjust. The review cadence is what keeps the relationship from drifting into transactional after onboarding completes.
Frequently asked
Standard 60 days from MSA execution to portfolio-wide steady state. Larger portfolios (200+ properties) extend to 90 days with regional-by-regional rollout. The bottleneck is usually MSA legal review and AP integration setup, not operational mobilization.
No. Day-of operational decisions stay with on-site managers. The MSA covers terms, pricing, and SLA at the corporate level; individual property managers still submit requests, communicate with the Loader crew, and approve completion. The change is in back-office structure, not day-of operations. This matters — most failed onboardings fail because corporate tries to centralize decisions on-site managers should still own.
For properties where the on-site manager has a strong relationship with the existing vendor and the rest of the portfolio is consolidating, the typical approach is to grandfather the existing vendor at that property and consolidate the rest. We don't pressure on-site managers to switch when the existing relationship is working. The portfolio-level value still comes through (MSA pricing on consolidated properties, COI rollup, AP simplification) without forcing transitions that don't need to happen.
Most major property management AP systems (Yardi, RealPage, MRI) and corporate ERPs (SAP, Oracle, NetSuite) have standard integration patterns we've seen before. Direct CSV export, API where available, or itemized PDF rollup for paper-based AP. We adapt to your system rather than imposing ours on yours.
Portfolios constantly change — acquisitions add properties, dispositions remove them, repositioning triggers operational changes. The MSA is built to handle this without amendment for routine changes. New properties are added through dispatch with COI update issued the same day. Dispositions are removed similarly. Major portfolio changes (acquiring 50+ properties at once) trigger MSA amendment but don't pause service.
Rollouts are time-bounded program work — a defined start, defined end, defined scope. Portfolio onboarding is structuring an ongoing recurring relationship. Different sales motion (operations VP vs program manager), different operational structure (steady-state vs rolling), different pricing (volume-tiered vs per-location program rate). Some accounts have both — a national rollout running concurrent with ongoing portfolio coverage.
Number of properties, geographic spread, current vendor structure, and your AP system if you know it. Our multi-location accounts team handles portfolio onboardings directly and gets back to you within one business day.
Multi-location · Portfolio onboarding