A parking proposal that passes contains six parts: the problem in numbers, the proposed solution in one sentence, what it costs per apartment per month, who is affected and how, when enforcement starts, and what happens if the assembly votes no. Write those six parts, keep the whole thing under one page, and submit it before the agenda deadline in your bylaws — typically several weeks before the assembly.
Timing: the assembly season is short
Danish associations concentrate their general assemblies in March–May, and agenda items close weeks earlier. That means the real work — measuring the problem, getting quotes, aligning the board — has to happen in January and February. Miss the window and the proposal waits a year.
Use the winter to collect the numbers the proposal needs: how often the lot is full, how many outside cars are observed, and what the current arrangement costs in board hours. A proposal with numbers gets debated; a proposal with adjectives gets postponed.
Template — copy and adapt
Proposal: introduction of digital resident parking
The board proposes introducing digital resident parking from [date].
Background: Our parking area is regularly occupied by vehicles without connection to the association. A count in [month] showed the area full [X] of [Y] evenings, with an estimated [Z] outside vehicles.
Proposal: Residents register their license plates free of charge ([1] vehicle per apartment, additional by [waiting list/fee]). Guests are registered via a link with [15] guest days per apartment per month. Enforcement by [operator/own controllers] begins [4] weeks after rollout, with control fees at the customary level. Signage is updated to meet current legal requirements.
Economy: [Amount] kr. per apartment per month / covered by [control fee revenue / budget].
If rejected: The current arrangement continues, and the board will not bring parking proposals for the coming year.
The objections you will meet — prepare answers
- "It's surveillance" → only plates and registration times are stored, with defined retention — bring the data policy
- "My guests can't handle an app" → guests don't need one; they open a link and type a plate
- "The elderly are excluded" → offer board-assisted registration; it takes five minutes per household, once
- "We'll fine our own neighbors" → the grace period plus registration means fees in practice hit outside vehicles
1
Page — maximum proposal length
Details go in an appendix
mar-maj
The Danish assembly season
Prepare in January–February
6
Parts every passing proposal contains
Problem, solution, cost, fairness, start, plan B
FAQ: The assembly proposal
Simple or qualified majority?
Depends on your bylaws and whether the scheme changes rights of use or requires house-rule amendments. Ask your administrator before the meeting — being corrected on procedure mid-assembly kills proposals.
Should we invite a supplier to present at the assembly?
A short demo can defuse the 'too technical' objection, but let the board own the proposal — the assembly is voting on the association's decision, not a sales pitch. Five minutes of demo, questions answered by the board.
What if it fails?
Ask why, concretely: was it the cost, the enforcement, the data? Most failed proposals pass the following year with one variable changed — and the measurement data you keep collecting meanwhile makes the case stronger.