The full launch process is documented in New Property Setup: Your Launch Guide. This article is the shorter companion: a 10-item readiness checklist to walk through in the day or two before going live, so you can confirm every essential piece is in place before patrol enforcement begins.
Use this when you're close to launch and want a quick go/no-go review. If you find any "no" answers, slow down — launching with one of these items unresolved is what most launch-week issues trace back to.
The 10-Item Checklist
1. Property configuration verified
Open Property Settings and confirm: unit list is complete and accurate, vehicle limits per unit are set, parking rules are finalized, and guest parking settings match what was agreed during onboarding.
If anything looks wrong — wrong unit count, wrong addresses, missing rules — flag it with your Account Manager before launch, not after.
2. Property keyword located and documented
The property keyword is what residents use to self-register. Confirm you know it, that it's in your welcome email, and that it's on any printed materials.
Keywords are case-sensitive — copy it exactly as it appears in the dashboard.
3. Residents invited
Choose your onboarding path and execute it:
Bulk-import for established properties with an existing rent-roll.
Individual invitations for smaller properties or staggered onboarding.
Keyword-only self-registration as the backup channel for ongoing intake.
By launch day, your initial resident set should have at least received the invitation — they don't all need to be registered, but they shouldn't be hearing about ParkingPass for the first time after enforcement starts.
4. Welcome communication sent
Residents have received an email or notice explaining: what ParkingPass is, the enforcement start date, how to register (with the keyword), what they need to provide, and where to go for help.
This isn't just courtesy — residents who don't know enforcement is starting account for most of the avoidable first-week complaints.
5. Signage installed and visible
Tow signage, parking rule signs, and any keyword/registration signage are physically posted in the property and visible from where vehicles enter and park.
Walk the property yourself. Confirm signs are legible at distance, lit at night where relevant, and compliant with your state and local jurisdiction's requirements. Your patrol vendor or local counsel can confirm specific requirements.
6. Do-Not-Tow list seeded
Every vehicle that should be protected from enforcement on day one is on the DNT list, with an appropriate expiration date set:
Property employees (maintenance, office, leasing).
Regular vendors (landscaping, pool, pest control, HVAC).
Recurring delivery vehicles where applicable.
Any pre-arranged contractors who'll be on-site during launch week.
The system does not warn before DNT entries expire, so set the dates deliberately. See Permit Types Explained for guidance.
7. Patrol vendor ready
Your patrol vendor has:
Confirmed the start date in writing.
Been briefed on your specific property's layout and hotspots.
Been briefed on any first-week patrol holds (move-in events, contractor windows, holiday gatherings).
An after-hours contact you can reach.
8. Staff users created with correct roles
Every team member who needs access to ParkingPass has an account, the right role, and has logged in at least once to confirm the credentials work. Notification preferences are set so the right people see new applications, vehicle changes, and patrol alerts.
9. Real-time contact designated (where required)
For Colorado properties (real-time tow authorization), at least one designated representative is identified, contactable, and trained on the authorization workflow. For all properties, the patrol vendor has a clear after-hours contact at your end.
See Colorado Real-Time Tow Authorization if applicable.
10. Payment infrastructure complete (if applicable)
If your property uses paid permits, paid guest passes, the Parking Spot Marketplace, or Revenue Share, your Stripe Connect setup is complete and verified. Funds can't flow until this is in place.
See Revenue Share: A Complete Guide for the Stripe Connect setup walk-through.
If You Hit a "No"
Most of these items can be resolved within a day or two if caught in advance. A few common situations:
Property configuration is wrong — Contact your Account Manager. Unit and rule changes go through Support.
Resident invitations haven't been sent — Send them today. Even a partial set of residents being aware is better than zero.
Signage isn't up — This is often the highest-friction "no" because it depends on a signage vendor's schedule. If you can't get signs installed by your planned launch date, push the launch date rather than launching without them.
DNT list is empty or incomplete — Build it now. The worst launch-day call is a towed employee.
Patrol vendor isn't ready — Confirm with the vendor and your Account Manager. Don't launch enforcement until the vendor is actively patrolling.
Stripe Connect isn't complete — For properties without paid features, this can be deferred. For properties with paid features, complete it before launching the paid program.
Pushing the launch date by a few days to resolve a "no" is almost always less expensive than launching with the issue and dealing with the consequences.
After Launch
The first week is its own phase. A few things to watch:
Application volume. Residents who got the invitation will start registering. New Resident Applications, New Vehicle Applications, and Vehicle Change Requests will appear on the dashboard. Clear them daily.
Last Patrol (Days Ago). Should be 0 once patrol has started. Anything else means enforcement isn't actually running.
Violation pattern. A short, sharp spike in warnings in the first week is normal as residents adjust. Watch for any patterns that suggest signage or communication issues — see Using Patrol Analytics to Improve Your Parking Program.
First disputes. Expect a few. Handle them through the standard workflow — see Citation Disputes: A Complete Workflow Guide.
Shift to the daily playbook. Once past the first week, transition to the routine in Property Manager Quick Start: Your Daily Playbook.
Important Notes
This checklist assumes your property has completed initial configuration with your Account Manager. If you're earlier in the process, work through New Property Setup: Your Launch Guide first.
A clean launch is much less expensive than a recovered one. Time spent on this checklist tends to pay back many times over in the first month.
If you find yourself debating whether to launch despite a "no" on any item, the answer is usually to push the date a few days and resolve the item.
State-specific items (Florida sales tax, Colorado real-time tow authorization) are handled at the platform level but still need awareness from the PM. See State Compliance Overview.