Ryan Gilpatric

Independent digital product builder

Hello
MenuClose

Worked example No. 1 · Property management · Southern Maine

Where a Southern Maine property manager's week actually goes.

How a property management firm here actually runs, what Maine and Portland add to the job, where the week goes, and what I would put in place first. Checked against the statute. The questions at the end are where a conversation starts.

Handoff chain, section: one resident problem passing through seven hands, with the channels that never reach the system of record drawn as dashed leadersSeven stations on rules from resident to owner statement. One continuous line is the request's path. Four dashed leaders stop short of a hatched band marked the system of record: phone, text, and email; a turn board in a spreadsheet; approval outside the work order; estimate by email and photos by message. Three solid leaders reach it: work order opened, invoice coded, statement sent. A red revision triangle marks the first gap.Handoff chain, sectionone resident problem · first contact to owner statementthe system of recordwhere the work is logged,not where it happensResidentCoordinatorProperty managerOwnerVendorAccounts payableOwner statementphone · text · emailwork order openedturn board ina spreadsheetapproval outsidethe work orderestimate by emailphotos by messageinvoice codedstatement sentone problem · seven hands1Δ1 · The request lives in the gap until someone types it in.TitleHandoff chain, sectionStatusWorked exampleDate5 Sep 2026Drawn byR. GilpatricHandoff chain, section: one resident problem passing through seven hands, with the channels that never reach the system of record drawn as dashed leadersSeven stations on rules from resident to owner statement. One continuous line is the request's path. Four dashed leaders stop short of a hatched band marked the system of record: phone, text, and email; a turn board in a spreadsheet; approval outside the work order; estimate by email and photos by message. Three solid leaders reach it: work order opened, invoice coded, statement sent. A red revision triangle marks the first gap.Handoff chain, sectionone resident problem · first contact to owner statementthe system of recordwhere the work is logged,not where it happensResidentCoordinatorPropertymanagerOwnerVendorAccountspayableOwnerstatementphone · text · emailwork order openedturn board ina spreadsheetapproval outsidethe work orderestimate by emailphotos by messageinvoice codedstatement sentone problem · seven hands1Δ1 · The request lives in the gap until someone types it in.TitleHandoff chain, sectionStatusWorked exampleDate5 Sep 2026Drawn byR. Gilpatric

A worked example.

The firm, as it runs

One resident problem, first contact to owner statement

Somewhere between a hundred and two thousand units, some in Portland, some on the coast for the season. A property manager, a bookkeeper, an office, a maintenance crew or a list of vendors. One resident problem can cross seven hands before it closes: resident, coordinator, property manager, owner, vendor, accounts payable, owner statement. The property management system is the system of record. It is not the system where the work happens. Phone, text, email, photos by message, estimates by email, owner approvals outside the work order, a turn board in a spreadsheet: that is where the week goes.

The firms say as much on their own pages. Several in Southern Maine name AppFolio outright, one of them saying every request, expense, and message is logged there. One runs on Rent Café and defines an emergency as no heat, no hot water or water, no power, with an after-hours line for those and a work order for everything else. One publishes a phone tree where emergency maintenance is option 1, maintenance is option 2, and vendor coordination is option 3. One keeps a full-time crew on 24-hour call. Portals and phones coexist everywhere. No firm publishes a channel mix, a response time, or a touch count. Those live inside the office, which is where the questions at the end of this page go. The other side of that no-heat call is the second worked example. The third does the same for a landscape firm.

What Maine changes

Verified at the statute, 5 September 2026

National property management software ships with national defaults. Maine changed several of the rules, some of them in 2023, and Portland has rules of its own on top. Eight to check, with the statute beside each.

The Maine configuration audit · eight to check
The ruleThe statuteWhat to check in your system
Applicant screening.

Only the actual cost of one screening; a complete copy to the applicant; no second fee within 12 months. In Portland, no application fee at all.

14 M.R.S. §6030-H · Portland Sec. 6-223

The applicant-paid screening setting, how a returning applicant inside a year is recognized, and that Portland units carry no fee.

Two clocks on late rent.

A 7-day notice at 7 days in arrears, void if paid before it expires; a late charge only after 15 days, capped at 4% of one month, with prior written notice.

§6002 · §6028

That the delinquency workflow does not treat them as one clock.

One month drawn as a line, with the 7-day notice and the 15-day late charge marked as two clocksrent dueone month7 · notice may issue15 · late charge · 4% capOne month drawn as a line, with the 7-day notice and the 15-day late charge marked as two clocksrent dueone month7 · notice may issue15 · late charge · 4% cap
Deposits.

Two months at most; returned within 30 days under a written lease or 21 days at will; normal wear not deductible; held apart from the firm's money. In Portland, no more than one month.

§6032 · §6033 · §6038 · Portland Sec. 6-223

The deposit cap by jurisdiction, and that the return deadline sits on the turn calendar.

Portland registration.

Every long-term unit, by December 31; $55 per unit as of July 1, 2026; $50 and $200 per-unit late fees at 14 and 45 days.

City of Portland

That renewals are on the calendar with the unit list.

Portland rent control.

2.2% allowable for 2026, 2.6% for 2027, set each September 1 at 70% of the Boston CPI-U change; never more than 10% in 12 months.

City of Portland

That renewal logic knows which units are in Portland.

Short-term rentals.

29 days or less must register in Portland; the license number on every advertisement; 293 mainland non-owner-occupied units for 2026.

City of Portland

Registration status before a listing renews.

Heat and lead.

Where the landlord supplies heat it must hold 68°F at minus 20°F outside, so no-heat is a priority class, not a ticket. Pre-1978 buildings need 30 days' notice before paint-disturbing work.

§6021 · §6030-B

That no-heat is its own priority class, and that the building's year is on the work order.

Notice of an increase.

Rent or a mandatory recurring fee rises only on 45 days' written notice; 75 days at 10% or more, or for increases summing to 10% within 12 months. In Portland, 90 days.

§6015 · City of Portland

That the renewal calendar counts back from the effective date by jurisdiction.

Rules as posted on 5 September 2026.

A worked example.

Where the time goes

Hypotheses
  1. 1.

    Leasing, screening, deposit, and increase settings do not reflect Maine's rules and Portland's.

    Maine-observed
  2. 2.

    Maintenance intake, triage, dispatch, and follow-up consume coordinator and manager time; winter makes it consequential here.

    Maine-observed · observed nationally
  3. 3.

    Registrations, licenses, and renewal dates are scattered across the towns' systems, the firm's system, and staff procedure.

    Maine-observed · inference
  4. 4.

    Processing an application takes hours the screening fee cannot recover.

    Maine-observed
  5. 5.

    Turnover runs against the deposit clock and the trades' calendar.

    Maine-observed · inference
  6. 6.

    Requests and decisions cross too many channels, so information is entered twice and chased.

    Observed nationally
  7. 7.

    Month-end owner reporting, payables coding, and trust reconciliation generate rework.

    Observed nationally
  8. 8.

    Maintenance capacity is constrained by technician and vendor availability.

    Maine-observed · inference

Two things the public record does say. In 2024, Portland's enforcement investigated 3,911 units and found almost 6% of covered units reporting increases above the 10% cap, which the Rent Board called either registration errors or violations. And a Maine manager told the Legislature in 2023 that processing one application takes three to five hours, including calling references.

City of Portland Rent Board, 2024 annual report · Testimony on LD 691, 131st Legislature

The first of these the audit above can settle this afternoon. The one I would test first in your office is the second: a coordinator rebuilding context and pushing the same job across people, because intake, decision rights, owner rules, vendor rules, and close criteria are not written down tightly enough.

What I would put in place first

The ladder

Process first: one record per request, named emergency categories with make-safe-first, owner approval thresholds written down, vendor acceptance and escalation defined, completion evidence before close. Then the settings you already pay for: categories, priorities, owner notes, the building's year and lead status, vendor trade and service area. Then an integration, if calls and texts still land outside the record. Then a small tool, only if the system cannot show the loops staff actually chase. AI on classification and drafting, with a person confirming every emergency and every dispatch.

Replacing the system is the last hypothesis, not the first.

The exception board

Concept
Exception board, elevation: a concept drawing of one screen showing a property management firm's open loops on a winter morningEight rows of open loops with a scale showing where each stands and who it waits on: a no-heat call awaiting dispatch, marked with a red revision triangle; a vendor who has not accepted; an owner approval waiting; a deposit clock running toward its 21-day mark; a Portland registration renewal due; a pre-1978 paint job open under its 30-day notice; and two requests that arrived by text with no record yet. The title block reads concept; the board reads from the property management system and writes nothing.Exception board, elevation · a winter morning · conceptOpen loopWhere it standsWaiting onNo heat · awaiting dispatchdispatchVendor has not acceptedvendorOwner approval waitingownerDeposit clock · toward 21 days21bookkeeperPortland registration · renewal dueofficePre-1978 · paint job open · 30 days' notice30managerArrived by text · no record yetno recordcoordinatorArrived by text · no record yetno recordcoordinator1Δ1 · Where the landlord supplies heat it must hold 68° at minus 20 outside (§6021): a priority class, not a ticket.TitleException board, elevationStatusConceptDate5 Sep 2026Drawn byR. GilpatricReadsfrom the property management system · writes nothingException board, elevation: a concept drawing of one screen showing a property management firm's open loops on a winter morningEight rows of open loops with a scale showing where each stands and who it waits on: a no-heat call awaiting dispatch, marked with a red revision triangle; a vendor who has not accepted; an owner approval waiting; a deposit clock running toward its 21-day mark; a Portland registration renewal due; a pre-1978 paint job open under its 30-day notice; and two requests that arrived by text with no record yet. The title block reads concept; the board reads from the property management system and writes nothing.Exception board · a winter morningOpen loopWhere it standsNo heat · awaiting dispatchVendor has not acceptedOwner approval waitingDeposit clock · toward 21 days21Portland renewal duePre-1978 · paint job open30Arrived by text · no record yetno recordArrived by text · no record yetno record1Δ1 · Where the landlord supplies heat it must hold 68° atminus 20 outside (§6021): a priority class, not a ticket.TitleException board, elevationStatusConceptDate5 Sep 2026Drawn byR. GilpatricReadswrites nothing

A worked example.

How we would know it worked

Measured before, then after
  • Request to acknowledgement, dispatch, first visit, and close, emergency and routine apart

  • Staff touches per ordinary work order

  • Requests arriving outside the system, by channel

  • Hours from month end to owner statements sent

  • Deposit returns inside the statutory deadline

  • Registrations renewed before their deadlines

Your records, before and after.

Before any of this is true of your firm

The questions
  1. 1.

    Walk me through the last five maintenance requests from first contact to paid invoice; where did each message, approval, photo, and invoice live?

  2. 2.

    Who decides a request is an emergency, and who can dispatch without owner approval?

  3. 3.

    For an ordinary work order, how many staff touches before close?

  4. 4.

    What does the bookkeeper do between the last day of the month and sending owner statements?

  5. 5.

    How are the screening fee, late fee, notices, and Portland increase configured today, and who checks that when the law changes?

  6. 6.

    For each Portland or coastal property, where do you keep the registration, license number, renewal date, and inspection status?

  7. 7.

    If you could eliminate one repeated piece of chasing, checking, copying, or explaining, what would it be?

We start with a conversation, not a contract.

A market dashboard in production and a bridal-shop app in pilot. See the record.