Polish Residential Lease Product Spec for MamNajem¶
Executive summary¶
This report converts the current Polish residential lease framework into a launch-ready product specification for MamNajem as of late May 2026. It is product research, not legal advice.
The legal core is relatively clear. A Poland launch should treat ordinary residential lease as mandatory, occasional lease as the most important special regime for private individual landlords, and institutional lease as relevant only if MamNajem is intentionally launching into the business-landlord or PRS segment. Ordinary leases remain the default regime; occasional leases are available only where the owner is a natural person who does not conduct a rental business and must be fixed-term, in writing, with specific annexes and a tax-office notification; institutional leases are for landlords conducting a rental business, must be fixed-term and in writing, and also require a notarial tenant statement. Ordinary leases over one year that are not put in writing are not void, but they are treated as indefinite-term instead. citeturn22view4turn6view2turn6view3turn6view4turn7view0
Before launch, MamNajem should support: lease-type eligibility gating; compliant document generation; wet-ink or qualified-signature execution for documents that require written form; external notary collection/upload for occasional and institutional leases; deposit collection and return logic; move-in and move-out handover evidence; lawful rent-increase notices for ordinary leases; landlord warning and termination workflows; final settlement; and a strong evidence vault with delivery proof. The biggest implementation mistake would be to treat an in-app tap, chat message, or simple e-signature as automatically equivalent to a statutory written form or a notarial act. Under Polish Civil Code rules, written form requires a handwritten signature, while electronic form equivalent to written form requires a qualified electronic signature; under eIDAS, only a qualified electronic signature is legally equivalent to a handwritten signature across the EU. citeturn22view2turn22view3turn18view0
The biggest messaging risk is overpromising. MamNajem should not market itself as providing “guaranteed eviction,” “fully legal e-signature” unless qualified signature or notarial requirements are actually met, or “automatic lawful rent increases” for all lease types. Special leases improve enforcement position, but they still depend on the correct lease type, the required annexes, formal written notices, and later court and enforcement steps. citeturn6view2turn6view3turn7view0turn32view0turn35view0
Lease types and the launch recommendation¶
Polish law creates materially different product behavior depending on lease type. MamNajem should therefore force a lease-type choice before draft generation and should block invalid combinations. The minimum gating rules are substantive, not cosmetic. citeturn6view2turn6view3turn6view4turn7view0turn22view4turn36view0
| Lease type | Who can use it | Term rules | Signature / formality rule | Special annexes | Product recommendation |
|---|---|---|---|---|---|
| Ordinary residential lease | Any landlord and tenant, subject to general landlord/tenant rules | Can be fixed-term or indefinite. If over 1 year and not in writing, it is treated as indefinite. Fixed-term termination requires cases defined in the contract, plus narrow statutory paths. citeturn22view4turn35view0turn22view5turn22view6turn23view0 | Written form strongly recommended for all; legally decisive for fixed terms over 1 year. Wet ink or qualified electronic signature if you want written-form confidence. citeturn22view2turn22view3turn22view4turn18view0 | None required by statute, but a move-in protocol is mandatory before handover. citeturn5view1 | MVP mandatory |
| Occasional lease | Owner must be a natural person who does not conduct business in renting premises | Fixed-term only, max 10 years. citeturn6view2 | Contract and amendments must be in writing under pain of invalidity. citeturn6view3 | Tenant’s notarial submission to enforcement; alternate premises indication; consent from the alternate-premises owner/right-holder, with notarized signature if demanded; tax-office notification within 14 days from lease start. citeturn6view2turn6view3 | MVP strongly recommended for private-landlord launch |
| Institutional lease | Landlord must conduct a rental business and may be a natural person, legal person, or other organizational unit | Fixed-term only. Art. 661 §1 conversion rule is switched off. citeturn6view4turn7view0turn36view0 | Contract and amendments must be in writing under pain of invalidity. citeturn7view0 | Tenant’s notarial submission to enforcement; no alternate-premises annex is required, but the tenant acknowledges that social housing / temporary premises rights do not apply in the enforcement path. citeturn7view0turn32view0 | Later unless business-landlord segment is launch-critical |
That leads to a practical launch recommendation.
For a first Polish launch, MamNajem should ship ordinary lease + occasional lease as a complete set. That combination covers the mainstream private-landlord market without forcing the product to solve “am I a rental business?” segmentation on day one beyond a simple lease-type eligibility declaration. Institutional lease should be added only if the product is deliberately selling to business landlords, PRS operators, or future property-manager accounts, because the legal path exists only for business landlords and creates a different commercial funnel, different notary pack, and different termination/enforcement logic. citeturn6view2turn6view3turn7view0
Legal and product matrix¶
The table below maps the legal requirements to what MamNajem must do in product terms.
| Workflow | Ordinary lease | Occasional lease | Institutional lease | What MamNajem should do |
|---|---|---|---|---|
| Lease-type eligibility | No special owner-type gate. citeturn22view4turn36view0 | Owner must be a natural person not conducting rental business. citeturn6view2 | Landlord must conduct rental business. citeturn6view4turn7view0 | Add a lease eligibility step before draft generation with hard blocks, not a post-fact warning. |
| Lease execution | If over 1 year, writing preserves fixed term; otherwise law treats it as indefinite. citeturn22view4 | Writing required under pain of invalidity. citeturn6view3 | Writing required under pain of invalidity. citeturn7view0 | Support draft generation in-app, but require wet ink or QES for final execution where written form matters. |
| Deposit | Max 12x monthly rent; return within 1 month after vacating; art. 6(3) provides indexed return formula. citeturn6view0 | Max 6x monthly rent; return within 1 month; special chapter preserves art. 6(3). citeturn9view0turn6view3turn32view0 | Max 6x monthly rent; return within 1 month; special chapter preserves art. 6(3); landlord may draw from deposit during lease and demand replenishment. citeturn7view0turn32view0 | Build a deposit ledger, indexed-return calculator inputs, deduction categories, and deadline timer. |
| Move-in protocol | Statutorily required before handover; it is the basis for settlement on return. citeturn5view1 | Not expressly preserved in the occasional-lease chapter. citeturn5view1turn32view0 | Not expressly preserved in the institutional-lease chapter. citeturn5view1turn32view0 | Make it mandatory in product for all lease types anyway, because it is essential evidence even where not expressly preserved. |
| Rent increase | Statutory workflow: written notice, 3-month notice period unless contract is longer, possible 14-day landlord explanation on tenant request, tenant refusal or court challenge within 2 months, no more often than every 6 months except owner-independent charges. citeturn4view3turn25view0turn25view1 | Rent may be increased only according to the contract. citeturn6view3 | Rent may be increased only according to the contract. citeturn7view0 | Implement two entirely different increase engines: statutory ordinary-lease engine and contractual special-lease engine. |
| Landlord termination for breach / arrears | Landlord may terminate only on statutory grounds; notice must be in writing and state the reason. For arrears: 3 full payment periods plus prior written warning and an additional month to cure. citeturn6view1turn8view0turn8view1 | Special chapter preserves art. 11(2)(1)-(3), and the contract can also define its own notice path. citeturn32view0turn6view3 | Same: statutory breach grounds preserved plus contract-driven notice path. citeturn32view0turn7view0 | Build a notice case engine with article-based reason codes and cure stages. |
| Owner-occupancy / other nondefault landlord termination | Highly regulated and fact-sensitive: 6 months, 3 years, substitute premises, senior protection, or court action for “important reasons.” citeturn8view0turn8view1turn9view0 | Not part of the imported owner-termination set. citeturn32view0 | Not part of the imported owner-termination set. citeturn32view0 | Support only as a manual / lawyer-reviewed document path at launch, not one-click automation. |
| Tenant termination | Indefinite leases follow contract/statutory periods; for premises with monthly rent, default notice is 3 months to month-end; health-threatening defects allow immediate termination. Fixed-term ordinary leases need contract-defined exit cases, except statutory immediate grounds. citeturn22view5turn22view6turn23view0turn35view0 | Contractual path plus end-of-term expiry. citeturn6view3 | Contractual path plus end-of-term expiry. citeturn7view0 | Add tenant notice templates, but keep contract-clause dependence explicit in UI. |
| Move-out and final settlement | Tenant must restore the flat / complete tenant-side repairs after the lease and return value of specified used technical elements; the protocol is the settlement base; deposit returns within 1 month after vacating. citeturn4view2turn5view1turn6view0 | 1-month deposit return still applies; proof package matters. citeturn6view3turn32view0 | Same, plus possible prior deposit top-up history. citeturn7view0turn32view0 | Build a structured final-settlement statement, with deductions tied to protocol items and payment evidence. |
| Vacate demand and enforcement pack | No fast-track notarial route; ordinary termination can still require court proceedings, and “important reasons” outside art. 11(2) require a lawsuit. citeturn8view1 | After expiry/termination, owner serves a written demand with officially certified signature and at least 7 days to vacate; then applies to court with the demand, service proof, proof of title, and tax-notification proof. citeturn6view3 | Same pattern, but minimum 14 days and no tax-notification proof; add the demand, service proof, and proof of title. citeturn7view0 | Build a special-lease enforcement packet generator, but keep court filing outside app unless later integrated. |
| Service and evidence | Burden of proof sits with the party relying on the fact; for ordinary lease address changes must be notified in writing, and old-address registered mail can be deemed served if parties fail to update. citeturn22view1turn4view0 | Court pack requires proof of service or proof of registered sending. citeturn6view3 | Same. citeturn7view0 | Build an immutable document and service layer with mailing evidence, timestamps, hashes, address history, and signature metadata. |
A second, simpler matrix is useful for engineering and UX decisions.
| Action | Can happen fully inside app | Must produce a PDF / durable document | Needs wet ink or QES | Needs external notary / authority |
|---|---|---|---|---|
| Property, tenant, and lease intake | Yes | No, unless finalized into a legal document | No | No |
| Lease draft review and negotiation | Yes | Yes, for the final draft artifact | No for draft; yes for final written-form execution where applicable citeturn22view2turn22view3turn18view0 | No |
| Ordinary lease execution | Intake yes | Yes | Yes if you want written-form certainty, especially for terms over 1 year citeturn22view4turn22view2turn22view3 | No |
| Occasional lease execution | Intake yes | Yes | Yes for the contract; a simple in-app signature is not enough citeturn6view3turn22view3turn18view0 | Yes for the tenant’s notarial deed and often for related annex handling citeturn6view2 |
| Institutional lease execution | Intake yes | Yes | Yes for the contract citeturn7view0turn22view3turn18view0 | Yes for the tenant’s notarial deed citeturn7view0 |
| Move-in / move-out protocol | Data capture yes | Yes, as a frozen artifact | Recommended, especially if parties are meant to accept it as the settlement baseline | No statutory notary step |
| Ordinary rent increase notice | No | Yes | Yes because writing is required under pain of invalidity citeturn4view3turn22view3turn18view0 | No |
| Arrears warning / termination notice | No | Yes | Safer as wet ink or QES for launch; landlord ordinary termination expressly requires writing citeturn6view1turn22view3turn18view0 | No |
| Special-lease demand to vacate | No | Yes | Not enough by itself | Yes, because the owner’s signature must be officially certified citeturn6view3turn7view0 |
| Tax-office notification for occasional lease | No | Yes | Landlord signature path should be supported | External authority step; at minimum track proof of submission and tenant-on-demand disclosure duty citeturn6view3 |
| In-app acknowledgments, read receipts, photos, chat | Yes | Optional export | No | No |
| Legal settlement agreement intended to waive claims | Not safely by tap-only UX | Yes | Yes if meant to operate as a formal bilateral legal settlement | No notary by default, unless counsel requires it |
Workflow diagrams in text¶
The diagrams below show the minimum defensible workflow shape.
The contract-creation flow must split early by lease type, because the legal annexes, notice logic, and enforcement path differ at the root of the process. Ordinary leases need strong written-form support; occasional and institutional leases need additional legal packs and should not be allowed to activate until those packs are complete. citeturn22view4turn6view2turn6view3turn7view0
START
-> Choose lease type
-> ORDINARY
-> collect parties / property / rent / deposit / service addresses
-> generate lease draft
-> execute with wet ink or QES
-> collect deposit
-> create mandatory move-in protocol
-> ACTIVE
-> OCCASIONAL
-> verify owner = natural person, non-business landlord
-> collect ordinary data
-> collect tenant notarial submission-to-enforcement deed
-> collect alternate premises declaration
-> collect alternate-premises owner consent
-> execute contract in writing
-> start lease
-> notify tax office within 14 days from lease start
-> collect proof of submission
-> move-in protocol
-> ACTIVE
-> INSTITUTIONAL
-> verify landlord conducts rental business
-> collect ordinary data
-> collect tenant notarial submission-to-enforcement deed
-> execute contract in writing
-> move-in protocol
-> ACTIVE
The ordinary rent-increase flow is a formal notice workflow, not a pricing toggle. The notice must be written, the notice period is 3 months unless the contract is longer, tenants get a two-month response window, and high-threshold increases can trigger a 14-day explanation duty and judicial review. Those rules do not govern occasional or institutional lease increases, which are contract-only. citeturn4view3turn25view0turn25view1turn6view3turn7view0
ORDINARY RENT INCREASE
Draft notice
-> validate not independent-charge-only adjustment?
-> compute 3-month notice period to month-end
-> issue written notice
-> wait up to 2 months for tenant response
-> tenant accepts / does nothing
-> new rent effective after notice period
-> tenant refuses in writing
-> lease ends at the end of the notice period
-> tenant sues / challenges
-> old rent remains payable until final judgment
-> if court approves some increase, back-payment delta becomes due
The ordinary landlord-termination flow must force statutory sequencing. For arrears, there is no lawful “terminate now” button: arrears must cover 3 full payment periods and the landlord must first send a written warning expressing the intent to terminate and granting at least one additional month to pay arrears and current charges. For other breach grounds, the landlord still needs a written path and clear reason coding. citeturn6view1turn8view0turn8view1
ORDINARY LANDLORD TERMINATION FOR ARREARS
arrears detected
-> check arrears >= 3 full periods
-> generate written warning + extra 1 month cure
-> serve and store proof
-> cure period ends
-> fully cured
-> case closes
-> not cured
-> generate written termination notice with reason
-> calculate end-of-month effective date
-> lease ends
-> if tenant stays, move to court path / outside-app enforcement
The move-out and final-settlement flow needs to center on possession return, protocol evidence, and the one-month deposit-return deadline. MamNajem’s existing “final settlement” concept is useful, but it should be framed as an accounting and evidence workflow unless the parties also sign a formal settlement agreement. citeturn5view1turn4view2turn6view0turn6view3turn7view0
MOVE-OUT / FINAL SETTLEMENT
termination or expiry
-> schedule return of possession
-> capture final meter readings / key return / protocol / photos
-> classify deductions:
unpaid rent
owner-independent charges already due
protocol-based damage / repair claim
other lease-based charges
-> compute indexed deposit baseline and deductions
-> generate final settlement statement
-> return deposit balance within 1 month from vacating
-> if dispute, freeze evidence bundle for court / mediation
The special-lease vacate path should be modeled as a separate legal funnel. This is where many products fail by treating “contract ended” as the same thing as “eviction can start.” It is not. For occasional and institutional leases, the owner still needs a separate written demand to vacate with officially certified signature and statutory minimum time to leave, followed by a court application with an attachment pack. citeturn6view3turn7view0
SPECIAL LEASE VACATE PATH
lease expired or validly terminated
-> tenant still occupies premises
-> generate demand to vacate
OCCASIONAL: minimum 7 days
INSTITUTIONAL: minimum 14 days
-> obtain official certification of owner signature
-> serve and preserve proof of service / proof of registered sending
-> no voluntary move-out
-> generate court pack
occasionals: demand + service proof + title proof + tax-notification proof
institutionals: demand + service proof + title proof
-> outside-app court filing
Required data model, statuses, deadlines, and audit events¶
The table below lists the fields MamNajem should treat as legally material.
| Workflow object | Minimum statuses | Required fields and deadlines | Mandatory audit events | Legal anchor |
|---|---|---|---|---|
| Lease file | draft -> eligibility_blocked / eligibility_passed -> awaiting_execution -> executed -> active -> ended -> post-lease |
lease_type; owner_natural_person; owner_business_rental_flag; fixed_or_indefinite; start_date; end_date; signed_at; rent_amount; independent_charges_model; deposit_multiple; service_address_history; e-delivery address if any; contractual termination clauses. For ordinary leases over 1 year, flag if no written-form execution. For occasional leases, cap at 10 years. citeturn22view4turn36view0turn6view2turn6view3turn6view4turn7view0 |
Lease type chosen; eligibility declaration accepted; contract version rendered; execution method recorded; final document hash stored. | KC 660, 661, 673; tenant act 19a, 19g, 19f. citeturn22view4turn36view0turn35view0turn6view2turn6view3turn7view0 |
| Special-lease annex pack | not_required / collecting / complete / incomplete / invalidated |
For occasional: notarial tenant deed ref, alternate premises address, alternate-premises owner/right-holder identity, consent document, notarized-signature-demanded flag, tax-notification due date = lease_start_date + 14 days, tax-proof file. For institutional: notarial tenant deed ref only, plus business-landlord verification. Also store annex invalidation if alternate premises are lost; deadline: tenant must provide a replacement within 21 days from learning of the loss. citeturn6view2turn6view3turn7view0 |
Annex uploaded; notarization verified; alternate-premises change notice recorded; tax-notification proof uploaded; annex pack locked at activation. | Tenant act 19a, 19b, 19d, 19f, 19i. citeturn6view2turn6view3turn7view0 |
| Deposit ledger | not_set / due / collected / partially_applied / top-up_due / refundable / returned / disputed |
deposit_amount; deposit_multiple; rent_at_collection; rent_at_return; indexed_refund_formula_inputs; deduction_items; vacated_at; refund_due_at = vacated_at + 1 month; for institutional also top_up_due_at when deposit is used mid-lease. Use different max caps: 12x ordinary, 6x occasional/institutional. Store enough data to run art. 6(3) logic. citeturn6view0turn9view0turn7view0turn32view0 |
Deposit demanded; collected; applied to debt; top-up demanded; tenant repayment; refund statement issued; refund completed. | Tenant act 6, 19a(4)-(5), 19f(4)-(8), 19e, 19j. citeturn6view0turn9view0turn7view0turn32view0 |
| Handover protocol | draft / signed_move_in / signed_move_out / disputed |
handover_date; itemized list of rooms / installations / devices; technical state; wear level; meter readings; keys; photos; videos optional; signatures; witness fields; attachments. Make the move-in protocol mandatory in UI for all leases, even though the statute expressly requires it only in the ordinary regime. citeturn5view1turn32view0 |
Protocol created; evidence bundle frozen; any later edits versioned; move-out comparison generated. | Tenant act 6c, 6e. citeturn5view1turn4view2 |
| Rent-increase case | draft / issued / awaiting_tenant_response / explanation_requested / explanation_sent / refused / challenged_in_court / effective / closed |
Ordinary only: old_amount; new_amount; service_date; effective_date; tenant_response_deadline = service_date + 2 months; landlord_explanation_request_date; explanation_due_date = request_date + 14 days; increase_category; replacement_value_basis; CPI_basis; last_effective_increase_date. Enforce “not more often than every 6 months,” except owner-independent charges. For occasional/institutional, store only the contract rule used. citeturn4view3turn25view0turn25view1turn6view3turn7view0 |
Notice rendered; notice served; tenant explanation request received; written explanation served; refusal received; court challenge flagged; effective date reached. | Tenant act 8a, 9, 19c(2), 19h(2). citeturn4view3turn25view0turn25view1turn6view3turn7view0 |
| Notice / termination case | draft / precondition_missing / warning_issued / cure_running / cure_failed / notice_issued / terminated / escalated_to_court / closed |
notice_initiator; notice_type; legal_ground_code; reason_text; arrears_period_count; warning_date; cure_deadline; termination_service_date; termination_effective_date; owner_occupancy_person if relevant; substitute_premises_offered if relevant. For ordinary arrears, require 3 full periods plus extra month cure. For fixed-term ordinary, require contract clause reference. For “important reasons” outside statutory grounds, mark as court-path only. citeturn6view1turn8view0turn8view1turn35view0turn23view0 |
Warning served; proof stored; cure expired; termination served; article basis locked; court escalation packet created. | Tenant act 11; KC 673, 682, 688. citeturn6view1turn8view0turn8view1turn22view5turn22view6turn23view0 |
| Final settlement file | preparing / issued / accepted / disputed / paid / closed |
vacated_at; protocol_diff; final_meter_charges_due; rent_arrears_due; repair_claims; deposit_offset; refund_amount; payment_request_amount; statement_issued_at; payment_or_refund_due_at. Label “accepted” carefully: if it is only in-app acknowledgment, it is evidence, not necessarily a globally waiving legal settlement. |
Settlement statement generated; viewed; accepted / rejected; linked payments made; refund paid. | Tenant act 6, 6c, 6e; CC form rules. citeturn6view0turn5view1turn4view2turn22view2turn22view3 |
| Service and evidence record | pending / sent / delivered / deemed_served / failed / replaced |
channel (registered_mail, e-delivery, in_person, QES_email_package, other); address_snapshot; postal_tracking_id; proof_of_posting; proof_of_delivery; return_reason; document_hash; signature_type; QES_certificate_ref; qualified_timestamp_ref; sender_id; recipient_id. Retention recommendation: keep legal files for at least lease end + 6 years, and tax-proof artifacts at least through the tax limitation period. That is a product-risk recommendation based on civil and tax limitation periods, not a lease-statute command. citeturn22view1turn18view0turn18view1turn18view2turn17search17turn22view0turn19search1 |
Every document rendered; every document signed; every service event; every failed service; every address change; every evidence export. | CC art. 6, 77^2, 78, 78^1, 118; eIDAS arts. 25, 41, 43; tenant act 6g, 19d, 19i. citeturn22view1turn22view2turn22view3turn22view0turn18view0turn18view1turn18view2turn4view0turn6view3turn7view0 |
Two engineering decisions matter especially.
First, MamNajem should model form as a first-class field on every legal artifact: in_app_record, document_form, written_form_wet_ink, written_form_qes, notarial_deed, signature_certified_notice. Without that, the system will blur internal workflow convenience with legal effect. Under Polish law, document form and written form are not the same thing. citeturn22view2turn22view3turn18view0
Second, MamNajem should model delivery separately from creation. A beautifully generated notice is legally weak if the product cannot later prove where it was sent, when it was sent, what exact version was sent, and how service was evidenced. That is particularly important for occasional and institutional vacate demands, where service proof becomes part of the later court pack. citeturn6view3turn7view0turn22view1turn18view2
Copy and legal-risk guardrails¶
Product copy should avoid claiming that the app “makes documents legally binding” unless the specific required form has actually been satisfied. For Polish residential leasing, that means at minimum distinguishing between an in-app acknowledgment, a simple or advanced e-signature capture, a qualified electronic signature, and a notarial act. Only the qualified electronic signature is treated as equivalent to handwritten signature in the written-form analysis, and notarial steps remain separate external formalities. citeturn22view3turn18view0
The app should also avoid presenting special leases as universally available. “Use occasional lease for faster eviction” is too broad and risky because occasional lease is available only where the owner is a natural person who does not conduct a rental business; institutional lease depends on the opposite commercial profile. “Guaranteed eviction” is also too strong, because even special leases still require correct annexes, proper notices, and a later court and enforcement path. citeturn6view2turn6view3turn7view0turn32view0
Ordinary rent-increase copy needs similar restraint. The product should not describe rent as something the landlord can “update anytime.” In the ordinary regime, the increase is a statutory notice with timing rules, possible explanation duties, a tenant refusal option, a tenant court challenge path, and a six-month spacing rule. Conversely, for occasional and institutional leases the increase path is primarily contractual, so the product should not imply the ordinary statutory notice engine applies there. citeturn4view3turn25view0turn25view1turn6view3turn7view0
Settlement copy should also stay conservative. If MamNajem lets the tenant click “accept final settlement,” that should usually mean “I have seen and acknowledged this statement” unless the workflow separately captures a legally intended bilateral settlement document in the required form. Otherwise the product risks suggesting a broader waiver of claims than the evidence actually supports. The safer UX is to label the default action as acknowledge statement and reserve sign settlement agreement for a separate form-governed workflow. citeturn22view2turn22view3turn35view0
Finally, template drafting needs consumer-law discipline. Contract terms and app-generated legal text should be clear and comprehensible, and the product should avoid one-sided clauses that unreasonably burden the tenant, force performance despite the landlord’s non-performance, impose excessive penalties, or let only the landlord interpret compliance unilaterally. Polish Civil Code rules on unfair terms matter here, especially if the landlord is acting as an entrepreneur. citeturn35view0turn34view1
MVP, later, and launch checklist¶
The recommended MVP for a Polish launch is:
| Scope bucket | Recommendation | Why |
|---|---|---|
| Ordinary lease | Ship now | It is the baseline regime and necessary for virtually every launch path. citeturn22view4turn8view0 |
| Occasional lease | Ship now for private-landlord launch | It is the main special regime for non-business individual landlords and materially changes enforcement. citeturn6view2turn6view3turn32view0 |
| Institutional lease | Later unless business landlords are a launch segment | It only fits landlords conducting rental business and adds separate legal branching. citeturn6view4turn7view0 |
| Wet-ink / QES execution support | Ship now | Written form is a recurring legal requirement. citeturn22view2turn22view3turn18view0 |
| Notary attachment collection and validation | Ship now if occasional is in launch scope | Without it, occasional lease protections are incomplete. citeturn6view2turn6view3 |
| Ordinary rent-increase engine | Ship now | It is formal, legally distinct, and easy to get wrong manually. citeturn4view3turn25view0turn25view1 |
| Landlord warning / default termination engine | Ship now | Arrears and breach sequencing is legally strict. citeturn6view1turn8view0 |
| Handover protocols and final settlement | Ship now | They underpin evidence and deposit logic. citeturn5view1turn4view2turn6view0 |
| Court filing / bailiff integration | Later | Useful, but not required for launch if the product can produce a complete evidence pack. citeturn6view3turn7view0 |
| e-Doręczenia integration | Later, but design for it now | Legally valuable as a registered-delivery equivalent, but optional for citizens and not required for launch. citeturn17search17turn17search0turn18view2 |
| Owner-occupancy / “important reasons” advanced termination automation | Later | Too fact-sensitive for one-click automation; keep launch support manual and document-centric. citeturn8view0turn8view1 |
A launch checklist should contain at least the following items.
MamNajem should add a lease type eligibility gate and refuse invalid combinations. Occasional lease must be blocked unless the owner is a natural person and declares they do not conduct rental business; institutional lease must be blocked unless the landlord is operating rental business. citeturn6view2turn6view4
It should add a legal artifact engine that stores the rendered PDF, the exact version hash, the chosen legal form, the signer identity, the signature metadata, and the delivery proof for every rent-increase notice, warning, termination notice, vacate demand, protocol, and final settlement statement. citeturn22view1turn22view2turn22view3turn18view1turn18view2
It should implement deadline automation for: occasional-lease tax notification within 14 days from lease start; alternate-premises replacement within 21 days from the tenant learning it is no longer available; ordinary rent-increase explanation within 14 days after tenant request; tenant response to ordinary increase within 2 months; arrears cure month after warning; minimum 7-day special vacate demand for occasional leases; minimum 14-day special vacate demand for institutional leases; and deposit return within 1 month from vacating. citeturn6view3turn7view0turn25view0turn25view1turn6view0
It should make move-in and move-out protocol capture mandatory in the product, even when the chosen special lease chapter does not expressly preserve article 6c, because the protocol is still the cleanest evidence spine for deductions and disputes. citeturn5view1turn32view0
It should store service addresses as versioned historical data, not just as the latest profile value. For ordinary leases, address changes must be notified in writing and old-address registered mail can become legally consequential if parties fail to update their address data. citeturn4view0
It should keep legal records for a risk-based retention window of at least lease end plus 6 years, plus tax-office notification evidence through the relevant tax limitation period. That is a product-control recommendation based on limitation periods for civil claims and tax obligations, not a lease-statute retention command. citeturn22view0turn19search1
Two limitations should remain visible to the product team. First, this report focuses on residential lease law and formality, not on all adjacent areas such as GDPR, tax reporting beyond the occasional-lease notification duty, or court-filing mechanics. Second, there was a parliamentary proposal to amend tenant-protection rules in May 2026, so legal rules should be configuration-driven rather than hard-coded constants. The current product design should therefore keep article-based rules in a jurisdiction policy layer and reserve the right to update templates and validations quickly if the law is amended. citeturn11search2turn11search7turn6view2turn7view0turn8view0