Skip to content

Polish Maintenance Workflow for MamNajem

Executive answers

Minimum useful MVP flow. The smallest flow that is genuinely useful in Poland is not a full property-manager work-order suite. It is a lease-linked issue ticket that lets a tenant report a problem with category, location, urgency, description, photos/files, access permission, and availability; lets the landlord triage responsibility and severity; lets the landlord either schedule a repair, route the matter to building administration, or mark it as tenant-responsibility; and then keeps every message, attachment, visit, status change, and completion proof in one timeline until closure. That shape matches the legal need to document notice, deadlines, access, and proof, and it matches the baseline implementation used by leading maintenance products such as AppFolio, Buildium, DoorLoop, TenantCloud, Property Meld, and Rentila. citeturn4view1turn4view2turn32view0turn20search0turn20search1turn22search18turn23search1turn21search2turn19view0turn24search4

Statuses, fields, notifications, and permissions. The cleanest model is three separate dimensions rather than one giant status list: a workflow status, a responsibility decision, and an urgency level. In practice, the workflow can stay lean, while the legal complexity sits in “who is responsible” and “how urgent is it.” Required fields should therefore include lease type, issue category, affected room/asset, description, started-at time, severity, consent to enter, pets/security notes, availability windows, assignee, and attachments; notifications should cover submission, request-for-more-info, scheduling, rescheduling, completion, and reopening; and tenant rights should be limited to reporting, adding evidence, answering questions, and confirming/reopening, while landlord rights should cover triage, responsibility, scheduling, financial charging, and closure. Competitor products consistently expose attachments, priorities, assignees, access instructions, vendor assignment, status updates, and message history, which supports this separation. citeturn20search0turn20search1turn23search3turn22search13turn21search0turn19view1turn19view2

How maintenance should connect to MamNajem’s existing modules. Every issue should be anchored to both property and lease, because Polish repair responsibility depends on the lease relationship, the condition of the premises, and formal notice. Messaging should be issue-specific rather than mixed into generic lease chat; documents should store photos, contractor reports, invoices, and protocol files; the calendar should carry visits and recurring statutory inspections; and audit logs should record every notice, responsibility decision, access-consent change, and closure event. For tenant-caused damage or unresolved move-out issues, the same record should feed final settlement and, where appropriate, payment requests or deposit deductions. That is also how mature products avoid fragmented communication and missing evidence. citeturn4view1turn4view2turn29view0turn32view0turn7view0turn22search2turn22search13turn14search15

Polish legal obligations that affect repair responsibility. For standard residential leases, Poland’s tenant-protection act gives a detailed default split between landlord and tenant responsibilities in Articles 6a–6e, but private-market parties may modify that split contractually under Article 6f. For occasional and institutional leases, the act largely does not apply, so responsibility falls back much more heavily on the Civil Code and the contract. Across all lease forms, the Civil Code still requires the landlord to deliver and keep the premises fit for agreed use, gives the tenant a right to set an appropriate deadline for landlord repairs and then perform necessary repairs at the landlord’s cost if the landlord fails, and allows rent reduction or even termination when defects materially impair use or threaten health. The tenant must also allow emergency access immediately and, after prior arrangement, access for inspections and necessary works. citeturn2view0turn2view1turn29view0turn25view0turn25view1turn4view0turn4view1turn4view2turn31view1turn32view0

For an ordinary long-term residential lease, the best legal starting point is not a generic “landlord pays major repairs, tenant pays minor repairs” rule. Polish law is more granular. Under Article 6a of the Act on the Protection of Tenants’ Rights, the landlord must ensure the functioning of building-related installations and equipment that allow the tenant to use water, gas and liquid fuels, heat, electricity, lifts, and other equipment specified by law; maintain common parts in proper order and cleanliness; repair the building and shared devices; and repair or replace internal installations and technical elements that are not charged to the tenant, including internal water, gas, hot-water, sewage, central-heating with radiators, internal electrical installation, and certain larger replacement items such as heating stoves, window and door joinery, floors, floor coverings, and plaster. Under Article 6b, the tenant must keep the unit in proper technical and sanitary condition, observe house rules, protect common areas from damage, and handle a specific list of repairs and maintenance: floors and wall coverings, windows and doors, built-in furniture, many kitchen/heating/water-heating/sanitary devices, electrical accessories and protections other than wiring, drains to the vertical stack including immediate unclogging, and painting/wall-surface upkeep. citeturn2view0turn2view1turn31view3

That legal detail matters for product design because several categories are split by the nature of the work, not only by the object itself. A window problem is not always a “landlord ticket” or always a “tenant ticket”: the tenant is charged with maintenance and repair of windows and doors, while the landlord’s default obligations include replacement of worn-out window and door joinery. Plumbing has a similar split: the landlord covers internal installations, while the tenant covers faucets, valves, sanitary fixtures, siphons, and drain blockage up to the vertical stack. Electrical issues split between tenant-handled accessories/protections and landlord-handled wiring and the broader installation. This is why MamNajem should store a responsibility decision with a legal basis instead of trying to encode payer logic directly into category names. citeturn2view0turn2view1turn31view3

The next complication is lease type. For private-market leases outside the public housing stock, Article 6f allows the parties to modify the Article 6a–6e split contractually. For occasional lease and institutional lease, the tenant-protection act largely does not apply at all, except for specific provisions such as emergency access and a few termination rules. In those lease types, the app should not pretend that the Article 6a/6b matrix is the governing rule; it should instead show the contract rule first, with the Civil Code as the fallback. Put differently: MamNajem needs a lease_type field and a responsibility_scheme field from day one. citeturn29view0turn25view0turn25view1

The Civil Code then supplies the broad remedies that make notice history legally important. Article 662 says the landlord must deliver and keep the thing fit for the agreed use, while small ordinary outlays fall on the tenant. Article 663 allows the tenant to set an appropriate deadline for landlord-borne repairs and, after ineffective expiry, perform necessary repairs at the landlord’s cost. Article 664 allows rent reduction for defects limiting agreed use and termination without notice if defects preventing use were not removed in appropriate time after notice, or cannot be removed. Article 682 goes further for residential units: when defects threaten the health of the tenant or the household, the tenant may terminate even if they knew of the defects at signing. This means a maintenance module must preserve timestamps for notice, deadline-setting, landlord response, and whether the defect was resolved or disputed. citeturn4view0turn4view1turn4view2turn31view1

Polish law also defines access rules that should appear directly in the workflow. Article 10 of the tenant-protection act requires the tenant to give access immediately in the case of a failure causing damage or directly threatening damage; if the tenant is absent or refuses access, the owner may enter in the presence of the police or municipal guard, and with the fire service if needed. After prior arrangement, the tenant must also give access for periodic or ad hoc technical inspections, determination of necessary works, and substitute performance of work charged to the tenant. If a necessary repair requires vacating the premises, the owner must provide a substitute premises at the owner’s cost, for no longer than a year, and the substitute rent may not exceed the previous rent. In product terms, “permission to enter,” “access instructions,” and “temporary relocation required” are not luxury fields; they are operational reflections of legal reality. citeturn32view0

There is no bright-line Polish statute saying a landlord must solve every broken tap within 24 or 48 hours. The law mostly uses standards such as “appropriate time” and “appropriate deadline.” What is explicit are safety and building-maintenance obligations: under the Building Law, the owner or manager must keep the building in proper technical condition and ensure safe use; buildings must undergo at least annual checks of gas installations and chimney flues, at least five-year checks of overall technical condition plus electrical and lightning installations, and, in the specific case of residents reporting unjustified alterations or interference causing non-compliance with basic safety/use conditions, a control within three days of the report. As a result, MamNajem should present SLAs as operational targets, not as statutory entitlements, while still surfacing safety-critical categories and recurring inspection deadlines. citeturn31view2turn7view0

Finally, evidence retention must balance civil-claims reality with GDPR storage limitation. GDPR requires personal data to be kept no longer than necessary for the purpose for which it is processed. The Polish Civil Code sets a general six-year limitation period and three years for periodic and business-related claims; for a narrower category of claims especially relevant at move-out, Article 677 gives a one-year period from return of the premises for the landlord’s claims against the tenant for damage/deterioration and for the tenant’s claims for reimbursement of outlays or overpaid rent. The practical consequence is that maintenance evidence should stay available through tenancy and settlement, then remain under a configurable retention policy with legal hold and timed deletion rather than living forever. citeturn33view1turn10view0turn34view0

Minimum viable workflow

The MVP should begin with a guided tenant intake, because the first minutes determine both safety and evidence quality. If the tenant selects gas smell, fire/smoke, electric sparking, heavy flooding, or another immediate-danger category, the app should show emergency instructions first and ask the tenant to call the relevant public line before or while filing the ticket; in Poland, 112 is the general emergency number, and 992 is the gas emergency line. For non-immediate danger, the form should capture category, room, free-text description, “when did it start,” whether the issue blocks normal use of the premises, and photos or files. This mirrors the safety logic in Polish law and the intake patterns used by Property Meld, AppFolio, Buildium, DoorLoop, and TenantCloud. citeturn11search0turn11search8turn32view0turn19view0turn23search3turn22search18turn20search0turn21search7

The second step is landlord triage, and that is where the Polish legal model should be made visible. The owner should classify urgency, decide whether the matter is landlord-responsibility, tenant-responsibility, shared/contract-specific, or building-admin-related, and either ask for more details or move directly to action. For apartment blocks, the app should specifically allow referral to building administration for common-area or building-system issues while keeping the landlord visible to the tenant as the accountable counterparty. That referral pattern fits both the statutory distinction between common/building obligations and unit obligations and the way Polish property-management firms describe day-to-day maintenance handling. citeturn2view0turn2view1turn16search1turn16search10

The third step is scheduling and handoff. The landlord should be able to pick one of three resolutions in the MVP: landlord will handle directly, an outside contractor will be scheduled, or the item is routed to building administration/other external party. At that moment, the system should capture consent to enter, pets/security notes, and tenant availability windows, then create the maintenance visit in the calendar and push a written confirmation to the parties. DoorLoop, Property Meld, AppFolio, and TenantCloud all expose some combination of access instructions, assignees/vendors, notifications, and scheduling logic, and those features are particularly valuable in Poland because Article 10 requires prior arrangement for non-emergency access. citeturn20search0turn20search1turn19view0turn23search3turn21search2turn32view0

The fourth step is execution with a single evidence timeline. All messages, reschedules, contractor notes, before/after photos, invoices, “no fault found” notes, and completion comments should stay inside the same issue record. This is where the app earns its value during disputes: if the tenant later seeks rent reduction, claims the landlord ignored notice, or contests a charge, the timeline already contains notice date, access history, attendance, outcome, and evidence. Buildium, Property Meld, TenantCloud, and Rentila all emphasize centralized communication and attachment history for this reason. citeturn4view1turn4view2turn19view1turn19view2turn22search13turn21search3turn24search4

The final step is closure with financial consequence. If the problem was landlord-borne, closure should create either a property cost entry or a maintenance cost record. If the issue was tenant-caused or contractually tenant-borne and remains unpaid, the owner should be able to create a payment request during tenancy or link the issue to move-out settlement later. Polish law already ties technical condition, handover protocols, and move-out repair accounting together, so the maintenance module should not end at “done”; it should end at “financially and evidentially settled.” citeturn2view1turn34view0

Status model and data design

The right state model for Poland is a small workflow status machine plus two separate decision layers. The workflow itself should answer only “where in the process is this issue?” The legal layer should answer “who bears responsibility?” The operations layer should answer “how urgent is it?” This mirrors Polish law more faithfully than a US-style all-purpose work-order enum because the decisive question is often not whether the ticket is “open” or “pending,” but whether the defect is landlord-borne, tenant-borne, shared by contract, or routed to building administration, and whether it threatens health, usability, or merely comfort. citeturn2view0turn2view1turn25view0turn25view1turn4view1turn31view1

A recommended MVP workflow machine is:

DRAFT -> SUBMITTED -> NEEDS_INFO -> TRIAGED -> SCHEDULED -> IN_PROGRESS -> COMPLETED -> CLOSED

Any open state -> CANCELLED
COMPLETED -> REOPENED -> TRIAGED

tenant_responsibility, building_admin_route, and emergency should be flags or side fields, not main statuses. So should awaiting_access, which is better represented by the next visit object and access-consent fields. Products like DoorLoop and AppFolio expose lean task/work-order statuses while keeping priority, access, assignee, and owner approval in separate fields; that is the better pattern here too. citeturn20search0turn20search1turn23search1turn23search3

The required MVP fields should include: property, unit, lease, lease type, reporter, subject, category, room/location, affected asset if known, description, started-at date/time, impact on use of the dwelling, urgency, photos/files, responsibility candidate, responsibility decision, decision basis, access permission, pets/security notes, availability windows, assignee, handling party, schedule window, completion note, completion photos, invoice or cost amount, and reopen reason. The category set should reflect the legal split and common rental reality: plumbing/water leak, heating/hot water, electrical, gas/ventilation, windows/doors/locks, sanitary fixtures, walls/floors/ceilings/plaster, mold/moisture, appliances/fitted equipment, common area/building systems, and other. That category set maps far better to Articles 6a, 6b, and 681 than a generic “maintenance” bucket. citeturn2view0turn2view1turn31view1turn20search0turn20search1turn19view0

The permission model should stay deliberately narrow in the MVP because your current visible product roles are owner and tenant, not a full delegated property-manager or agency hierarchy. Tenants should be able to create issues for their active lease, add evidence, answer follow-up questions, update availability, and reopen within a configured period; owners should triage, assign, schedule, set responsibility, record costs, and close; admins should have internal support visibility and audit access, not day-to-day operational ownership by default. Contractor logins are better deferred; a secure appointment link or lightweight guest update channel is enough for the first version. The richer vendor/team role models used by TenantCloud and Property Meld are good later-stage references, not MVP requirements. citeturn21search0turn21search2turn18view1turn19view2

The notification rules should be simple but strict. Submission should trigger push plus email to the owner; emergency-tagged submissions should bypass snooze and call out emergency instructions. “Needs info” should notify the tenant immediately, with a reminder if unanswered. Scheduling and rescheduling should notify all relevant parties and include access instructions. Completion should notify the tenant and invite confirmation or reopening. Tickets left too long in submitted, triaged, or scheduled should trigger internal escalation. Because Polish law repeatedly turns on notice, deadline, and written communication, the app should also generate an exportable written summary for key events such as responsibility decision, landlord repair commitment, access request, and closure. citeturn32view0turn29view0turn19view2turn22search18turn20search0

Integration with MamNajem

Maintenance should be a first-class domain object connected to lease and property, not just another message type. Lease linkage matters because visibility, responsibility defaults, and final settlement rights all depend on the actual tenancy relation and lease type. Property and unit linkage matter because one class of issues belongs to the apartment itself, another to the building/common area, and another to a specific fixture already documented at handover. In polishe practice, especially in apartment buildings, some matters will need routing to building administration; Hamilton May explicitly describes tenant maintenance reporting through a tenant panel while the property manager coordinates the work. citeturn2view0turn2view1turn25view0turn25view1turn16search1

The message layer should be issue-specific even if MamNajem keeps a broader lease chat. Legally, the issue record should preserve one chain of communication tied to the defect itself: initial report, landlord response, request for access, contractor update, completion note, and dispute or reopening. Competitor products that treat maintenance as a structured ticket rather than a loose chat thread consistently expose better history and easier evidence recovery. That structure is particularly important under the Polish Civil Code because remedies turn on whether the landlord was notified, whether an appropriate deadline was set, and whether the defect was fixed in time. citeturn4view1turn4view2turn19view2turn22search13turn24search2

The document layer should store more than photos. It should hold invoices, contractor notes, building-administration correspondence, warranty cards, and inspection protocols. Polish law already gives move-in and move-out protocols special evidentiary relevance, because Article 6c makes the initial protocol the basis for settlement at return, and Article 6e deals with move-out repair/renewal accounting. The practical design implication is that a maintenance issue should be able to link back to move-in evidence and forward to move-out settlement evidence. citeturn2view1

The calendar layer should do two jobs. First, it should handle one-off visits and access windows for active tickets. Second, it should support recurring compliance and upkeep tasks, especially the annual gas/chimney checks and five-year electrical/technical checks that the Building Law already requires owners or managers to arrange. Even if recurring preventive maintenance is not in the first sprint, the data model should leave room for it now so that a future version can convert inspection findings into maintenance tickets instead of living in a separate system. citeturn31view2turn7view0

The audit log should store every state change, attachment upload, responsibility change, consent-to-enter update, schedule change, and closure action with actor and timestamp. That is not just an enterprise nicety. It is what turns the app into a usable dispute record when a tenant alleges no response, a landlord alleges denied access, or either side contests cost allocation. Buildium, Property Meld, TenantCloud, and Rentila all lean on documented history to reduce back-and-forth and prove what happened. citeturn22search13turn19view2turn21search3turn24search4

Finally, maintenance should connect directly to payments, property costs, handover, and final settlement. An owner-borne ticket can produce a property cost entry. A tenant-borne ticket can become a payment request during the lease or a settlement line at move-out. A recurring unresolved defect can also inform lease renewal decisions or risk flags. This is where MamNajem’s broader rental-operations surface is a real advantage over narrower products: the maintenance record can live through the full lifecycle instead of dying at “repaired.” citeturn2view1turn34view0

Competitors and roadmap

The competitor landscape splits into three visible patterns. General property-management suites like Buildium, AppFolio, DoorLoop, and TenantCloud all treat maintenance as a structured portal workflow with resident submission, attachments, status tracking, assignees/vendors, and updates. Buildium highlights work-order submission with images, documents, and videos, full history, and status updates. AppFolio emphasizes residents tracking and communicating progress and allows photo upload and permission-to-enter details. DoorLoop exposes due date, priority, status, assignees, access instructions, files, parts/labor, and owner approval fields. TenantCloud offers online maintenance requests, vendor/service portals, auto-assignment, and a maintenance board. These are the baseline patterns MamNajem should borrow. citeturn22search18turn22search13turn23search1turn23search3turn20search0turn20search1turn21search2turn21search15

Maintenance-specialist platforms like Property Meld go a step further and show what “later” can look like. Property Meld gives tenants 24/7 guided intake and troubleshooting, supports photo/video uploads, captures entry preferences and appointment windows, and keeps chat plus email/text notifications around the same maintenance record. It also explicitly supports resident, vendor, technician, owner, and manager views. That is powerful, but it is beyond what MamNajem needs for an initial Polish MVP. The lesson to copy is not “build everything Property Meld has”; it is “keep intake structured, keep communications inside the ticket, and never lose the scheduling/evidence trail.” citeturn18view1turn19view0turn19view1turn19view2

At the small-landlord end, Rentila is more relevant to MamNajem’s near term. Rentila lets both landlord and tenant create maintenance items, both sides add comments and documents, and the landlord mark completion or reopen the maintenance. That is very close to the lowest viable operational baseline. In the Polish market, firms like MamNajems and Hamilton sell “current/ongoing maintenance” mainly as a managed service; Hamilton also mentions a tenant panel for maintenance reporting, but the process is still centered on a human property manager. Rendin’s Polish positioning, by contrast, is overtly centered on lease templates, legal aid, rent-payment guarantee, and property-damage reimbursement, not on a dedicated operational maintenance-ticket flow. The gap this creates is clear: a mobile-first Polish app can differentiate by making maintenance operationally strong without trying to become a full enterprise PM stack on day one. citeturn24search4turn15search6turn15search13turn16search1turn15search8turn15search22

The best MVP/later split is therefore straightforward. MVP should include: issue intake with media, category and urgency; responsibility decision with legal/contract basis; owner triage; scheduling with access instructions; issue-specific messaging; calendar visit creation; cost and completion proof; reopening; and exportable written summaries for legal moments. Later releases can add contractor portals, quote comparison, owner approval workflows for larger repairs, vendor scorecards, preventive-maintenance schedules, inspection templates, AI-assisted troubleshooting, after-hours intake, warranty tracking, and delegated property-manager/team roles. That sequencing is consistent with how the more mature products layer sophistication on top of a simple work-order core, and it avoids overbuilding before you know how Polish landlords and tenants actually use the feature. citeturn20search1turn21search0turn22search18turn23search2turn19view0turn24search4

The main product requirement, in one sentence, is this: build a legally aware issue timeline, not a generic task list. In Poland, repair responsibility depends on lease type, contract wording, defect type, urgency, access, and proof of notice; the strongest products in the market all converge on structured intake, message history, attachments, scheduling, and documented closure. If MamNajem ships that core first, it will already cover the minimum useful maintenance workflow for long-term residential rental in Poland. citeturn2view0turn2view1turn25view0turn25view1turn4view1turn4view2turn20search0turn23search1turn19view2