Short answer: a portfolio onboarding readiness scorecard should show whether agreement scope, property and unit records, active leases, opening financials, deposits, vendors, open maintenance, access, resident and owner communication, integrations, staff capacity, exceptions, and launch approvals are ready for service. A high average score must not hide one unresolved safety, legal, financial, or access blocker.
Buildium's software-onboarding guidance emphasizes preparing structured data, defining an accounting start date, understanding balances and liabilities, configuring payment settings, and deliberately launching resident and owner access. AppFolio's owner-onboarding guidance emphasizes complete information, expectations, communication, and a clear handoff. This independent scorecard supports readiness decisions but does not validate a management agreement, opening balance, deposit treatment, legal duty, migration, insurance position, or vendor implementation.
Define the portfolio and service-start decision
Record legal entities, owners, properties, units, occupancy, services, exclusions, agreement effective date, proposed system date, first resident-facing action, first owner report, and decision authority. Separate contract effective date from operational launch when records or controls require staged acceptance.
Use blocker gates before percentages
Define conditions that prevent launch regardless of total score: unresolved life-safety issues, unverified legal authority, missing critical lease records, unclear funds, uncontrolled access, unavailable emergency response, or an unapproved data migration. Qualified reviewers should set gates for the property type and jurisdiction.
Verify property, unit, and lease records
Reconcile addresses, buildings, units, occupancy, lease parties, term dates, charges, deposits, amendments, notices, concessions, renewals, and document links. Use the owner onboarding and agreement handoff checklist to connect the signed scope to the opening property record.
Accept opening financial data deliberately
Define accounting start date, chart of accounts, bank and payout instructions, opening balances, resident ledgers, owner balances, deposits and custody, unpaid bills, reserves, recurring charges, management fees, and reconciliation evidence. Preserve source totals and exceptions rather than forcing a clean import that cannot be traced.
Inventory physical operations and open risk
Review keys, codes, alarms, utilities, warranties, recurring services, vendors, insurance or credential records, inspections, open work orders, approved estimates, known defects, emergencies, resident commitments, and scheduled visits. Every inherited issue needs priority, temporary control, owner, due date, and communication status.
Download the onboarding scorecard
Download the editable portfolio onboarding readiness scorecard (CSV). It includes domain, requirement, source evidence, blocker status, completion, quality review, exception, owner, due date, launch decision, post-launch validation, and acceptance sign-off.
Test roles, portals, and integrations
Create and test staff, owner, resident, vendor, and service identities with fictional or approved records. Confirm portfolio scope, communication channels, exports, connected services, payments, reports, and mobile workflows. Use the integration reconciliation playbook for control totals, mapping, retries, and recovery.
Calculate operating capacity for launch
Estimate onboarding tasks, recurring workload, inherited backlog, field travel, accounting demand, communication volume, training, and stabilization support. Compare required hours and skills with available capacity through the portfolio capacity planning model. Signed units are not ready units when the team cannot support them.
Run a role-based launch rehearsal
Rehearse a resident payment question, urgent maintenance request, owner approval, vendor dispatch, lease event, document retrieval, report review, integration failure, and escalation. Record failures and retest. A platform demonstration is not a rehearsal of the configured portfolio.
Approve known exceptions explicitly
List missing records, conflicting balances, incomplete access, delayed vendors, untrained users, integration gaps, and inherited maintenance. Record consequence, temporary control, owner, deadline, escalation, and who accepts launch risk. Never convert unknown into complete to improve the score.
Validate the first operating cycle
After launch, reconcile opening records, first payments, work orders, communications, owner reports, access logs, and integrations. Compare actual volume and staffing with the readiness assumptions. Keep onboarding open until critical validation and approved exceptions have evidence.
Frequently asked questions
What score means a portfolio is ready?
There is no universal percentage. Use mandatory gates, consequence-weighted domains, and explicit exception approval. A portfolio with complete marketing records but uncertain resident funds is not ready because its average looks high.
Should all properties launch on one day?
Not necessarily. A phased launch can reduce risk when entities, accounting dates, integrations, or operating teams differ. Define phase scope and preserve one controlled portfolio plan.