A parking management scope of work is the section of the solicitation that defines exactly what the operator will staff, control, report, insure, and maintain at your property, and it is the single reason competing proposals either compare cleanly or do not compare at all.
Why the Scope Decides the Bid Before Any Bids Arrive
Owners who write a vague scope receive proposals they cannot evaluate, because each operator fills the gaps with a different set of assumptions. One bidder staffs the booth sixteen hours a day and another staffs it twelve. One includes sweeping and striping, another calls it an owner expense. The fee comparison at the bottom of each proposal is then meaningless, and the person who has to defend the selection to ownership has nothing defensible to point at.
One of the most common complaints from owners running a first solicitation is that the proposals are not comparable because every operator formats their numbers differently. That is not an operator problem. It is a specification problem, and it is fixed upstream, in the scope, before the parking management RFP goes out. A scope that names the hours, the positions, the reports, and the insurance limits forces every bidder onto the same page, which is the only condition under which scoring competing proposals produces a real answer.
What a Scope of Work Is, and What It Is Not
The scope of work describes the operation you want run, while the rest of the RFP describes the process for choosing who runs it and the contract describes what happens when something goes wrong. Keep the three separate in your own head even if they end up in one binder.
The scope is not a wish list, and it is not a description of your current operation copied forward. Copying the current operation forward preserves whatever is already broken, which is usually the reason you are bidding in the first place. Write the scope as a description of the operation you want in place ninety days after transition, then let the bidders tell you what it costs.
The scope is also the document that survives the selection. Whatever you specify becomes the performance baseline you enforce for the next three to five years, so specificity written now is leverage held later.
Start With the Facility Profile, Because Nobody Can Price What They Cannot See
The facility profile is the factual description of the asset that lets an operator build a staffing model and a revenue projection without guessing, and it belongs at the front of the scope. Bidders who guess wrong either pad the fee to cover the uncertainty or bid low and reopen the conversation after award.
At minimum, the profile should state:
Total stalls, broken out by level or lot, including reserved, accessible, and EV-equipped spaces
Current mix of monthly permit holders and transient parkers, with actual counts rather than estimates
Hours of operation, peak periods, and any event or seasonal patterns
Existing revenue control equipment by make, model, and approximate age
Current rate schedule, validation programs, and any tenant or contractual parking obligations
Existing labor arrangements, including any collective bargaining agreement or prevailing wage requirement
Include the parking-adjacent programs too. If the property runs shuttle and transportation programs, a commuter lot, or a valet stand at a separate entrance, those carry their own labor and liability profile and cannot be inferred from a stall count.
The Staffing Plan Is the Section Most Owners Under-Specify
Staffing is where scopes fail most often, because owners specify a headcount and assume the rest, while operators price the headcount and manage the rest to their own margin. Specify the shifts, not the bodies. A scope that says "two attendants" tells a bidder almost nothing, while a scope that says "one attendant at the entry booth from 6am to 10pm daily and a second from 7am to 9am and 4pm to 7pm weekdays" tells them exactly what to price.
Then specify what happens when someone does not show up. Coverage failure at peak is the operational problem owners actually experience, and it is rarely addressed in a scope at all. Ask bidders to describe the callout procedure, the supervisory backup, the maximum response time to an unfilled shift, and the recruiting pipeline that keeps the position filled in the first place. An operator who can explain how the position actually gets filled is telling you something a headcount table cannot.
Training and appearance standards belong here as well. Name the uniform standard, the customer service training, the cash handling training, and who pays for it. At a hospital entrance like the valet operation at Stony Brook University Hospital, where the attendant is often the last person a discharged patient interacts with, the training specification is not an administrative detail.
Revenue Control Is Where Vague Scopes Cost Real Money
Revenue control is the set of procedures that ensures every vehicle entering the facility produces a recorded transaction, and it is the section where under-specification is most expensive. Automation does not remove the need for it. A single convention center attendant diverted approximately $57,000 using a personal card reader, a scheme discovered only after cameras were installed in the toll booths (Orange County Comptroller audit, reported 2025). In a separate matter, auditors found a Miami operator had underreported nearly $900,000 in revenue (reported audit finding, 2019).
Your scope should require, in writing:
Ticket and permit inventory control, including sequential numbering and reconciliation procedures
Daily cash handling, deposit, and armored carrier procedures with named accountability
Segregation of duties between the person collecting revenue and the person reconciling it
Exception reporting for voids, comps, lost tickets, and manual overrides, with thresholds that trigger review
Surveillance coverage at every payment point and the retention period for that footage
The owner's right to conduct or commission an independent revenue audit at any time
These procedures live inside the day-to-day operation rather than beside it, which is why they belong in the scope rather than in a technology exhibit. They are also the language you will reuse verbatim the next time any garage in your portfolio goes out to bid.
Reporting: Name the Documents, the Fields, and the Due Date
Reporting requirements are the mechanism that turns an operation you cannot see into a performance line you can hand upward, and they should be specified with the same precision as a lease clause. "Monthly reporting" is not a requirement. A monthly settlement report delivered by the tenth business day, containing gross revenue by category, permit counts, transient volume, occupancy by daypart, labor hours by position, and a variance explanation against budget, is a requirement.
Ask for a redacted sample of the operator's actual monthly report as part of the proposal response. This is the single most useful thing you can request, because it shows you what you will really receive rather than what the proposal promises you will receive. An operator who cannot produce one has told you something important.
Specify system access as well. If the revenue control system produces data, name your right to a read-only login, direct report exports, and access to the raw transaction record. Owners negotiate hard on the management fee and routinely give away system access without noticing, which is how you end up dependent on the operator's summary of the operator's own performance.
Insurance, Indemnification, and Who Actually Holds the Risk
The insurance section defines whose balance sheet absorbs a damage claim, and it is the part of the scope your general counsel will read most closely. Name the required coverages and the limits rather than asking bidders to propose them, because a bidder proposing their own limits will propose the limits they already carry. General liability, garagekeepers legal liability, auto liability, workers compensation, and umbrella coverage each need a stated minimum.
Then name the mechanics. Require the owner and any lender or ground lessor as additional insureds, specify that coverage is primary and non-contributory, require waiver of subrogation, and set the deadline for the certificate of insurance relative to the commencement date. Specify who handles a damage claim from first report to resolution, and how quickly you are notified.
Valet operations carry a distinct exposure because taking possession of a vehicle creates a bailment relationship, and disclaimer language on a claim ticket does not reliably eliminate it. If the scope includes valet parking services, say so explicitly in the insurance section rather than letting it ride under a general parking heading.
Maintenance, Equipment, and Who Pays for What
The maintenance section allocates every recurring physical task and every repair dollar between operator and owner, and ambiguity here is what produces the pass-through expenses that grow year over year. Build a simple two-column allocation: task, and who pays. Sweeping, pressure washing, snow and ice removal, striping, signage, lighting relamping, elevator service, drain cleaning, and equipment maintenance each need a line.
Set approval thresholds while you are here. Name the dollar amount above which the operator needs written owner approval before incurring an expense, and name a separate, lower threshold for anything recurring. Owners who skip this discover the omission through the operating statement rather than through a conversation.
Distinguish operating maintenance from capital replacement. Routine parking facility maintenance is an operating expense the scope can assign cleanly, while a barrier gate replacement or a deck repair is a capital decision that belongs to ownership. Scopes that blur the two produce arguments about whether a failing piece of equipment is a repair or a replacement, usually at the worst possible moment.
Transition and Mobilization Belong in the Scope, Not the Kickoff Call
Transition risk is the reason owners stay with operators they are unhappy with, so the scope should require every bidder to price and describe the changeover rather than treating it as a post-award detail. Ask for a written mobilization plan with a day-by-day timeline covering the first thirty days.
The plan should address hiring or retaining incumbent staff, uniform and badge issuance, payroll setup, cash room and safe transfer, revenue system credential handover, permit holder migration and notification, signage changes, and the point at which financial responsibility shifts. Require a named transition manager and a named local operations contact who will still be there in month six.
Ask specifically how they will avoid a coverage gap on day one. The answer separates operators who have done this from operators who are describing it. Whatever contract structure you eventually sign, management agreement or revenue share, mobilization is the phase where a good contract still fails if nobody planned the first Monday.
Performance Standards Turn the Scope Into Something You Can Enforce
Performance standards are the measurable commitments that let you hold an operator to the scope without renegotiating it, and a scope without them is a description rather than an agreement. Choose a small number you will actually track. Five enforceable standards beat twenty that nobody reviews.
Useful ones include maximum unfilled shift hours per month, average valet retrieval time at peak, deposit timeliness, settlement report delivery by the stated date, response time to a written owner inquiry, and complaint resolution within a defined window. Attach a consequence: a cure period, a fee adjustment, or a termination right tied to repeated failure.
Public-sector buyers should specify how these standards will be scored during evaluation, not just enforced after award. A municipal solicitation like the one behind the Queens Borough Hall municipal parking garage operation is reviewed by people who were not in the room when the scope was drafted, which is exactly why the measurable version of a standard is the one that survives.
What Changes by Property Type
The core scope sections stay constant across asset classes, while the operating conditions inside them change enough to make a copied scope the wrong scope. Peak patterns, user mix, and compliance exposure drive most of the difference.
In hospital parking management, the scope has to address shift change and visitor peak as separate events, patient discharge assistance, and the accessibility requirements that come with an aging patient population. In hotel parking management, valet capacity at check-in and checkout, key control, and the guest damage claim procedure dominate. In office parking management, the scope centers on tenant allocation, validation programs, and a monthly permit population that has shifted with hybrid schedules. In multifamily parking, resident and guest space enforcement, towing authority, and after-hours access are the recurring flashpoints. Retail and mixed-use properties add employee parking control and shared-use allocation between tenants.
Write the section that matters for your asset and leave the sections that do not. A scope that specifies valet key control at a suburban surface lot signals that the document was assembled from a template, and sophisticated bidders read that signal.
Pressure-Test the Scope Before It Goes Out
A finished scope of work passes one test before release: two competent operators could read it and price the same operation. Read it back as a bidder would and confirm:
Could two bidders price the same shifts from the staffing section, callout procedure included?
Does the revenue control section name the audit right, the exception thresholds, and your system access?
Does the reporting section name the documents, the fields, and the due date, and request a redacted sample?
Did you set the insurance coverages and limits yourself, rather than inviting bidders to propose them?
Does every maintenance task have a named payer, and every expense an approval threshold?
Does every bidder have to price a written mobilization plan with named transition and local contacts?
Is each performance standard measurable, with a consequence attached?
Then read it against the operation you run today and mark every requirement it would fail. That list is the real reason you are bidding, and it belongs in the evaluation criteria.
How Parking Systems Responds to a Well-Written Scope
Parking Systems would rather bid against a specific scope than a vague one, because specificity is where real local staffing depth shows. The company runs garages, surface lots, valet stands, and shuttle programs across New York, New Jersey, Pennsylvania, Georgia, and the Carolinas, including public-sector work like the MTA Long Island Rail Road commuter garages and hospital campuses where coverage at shift change is the whole job.
If you want to know what your current operation produces before you write the scope, a parking consulting engagement documents it first. When the scope is ready, request a proposal for your property.