Ask three boards what their porter does and you get three answers, which is where the complaints start. A porter keeps the common areas presentable day to day: trash cans emptied, litter picked up, breezeways swept, the mail room wiped down, the pool deck hosed. Deep-cleaning interiors and fixing what is broken are two other trades with two other price lists. When the title is vague the work is vague too, and the scope document is where you make it specific.
This guide walks through what a community porter typically handles, what falls outside the role, and how to write a scope of work that leaves no room for guessing.
What a porter usually does
A porter is a generalist who keeps the shared, visible parts of a community clean and tidy on a recurring basis. Think of them as the person responsible for the first impression a resident or guest gets when they drive through the gate. Common duties include:
- Emptying and re-lining common-area trash cans and dog-waste stations
- Picking up litter along entrances, sidewalks, mail centers, and parking areas
- Wiping down and straightening shared furniture, mailboxes, and signage
- Cleaning up around dumpster enclosures and pooled trash
- Blowing or sweeping walkways, breezeways, and pool decks
- Spot-cleaning spills, gum, bird droppings, and cobwebs
- Restocking supplies in restrooms or dog stations
- Reporting the maintenance issues they spot, such as a burned-out light, graffiti, or a broken gate
The value of a good porter is not any single task. It is that a person walks the property regularly and handles the small stuff before it becomes the big stuff residents complain about.
What a porter usually does not do
Scope creep is where porter arrangements go sour. A porter is a janitor with a loop to walk, and asking one to do specialized work buys you a poor result and a liability question at the same time. Generally outside the role:
- Electrical, plumbing, or HVAC repair
- Pool chemical balancing (that is a licensed pool operator's job)
- Landscaping beyond light debris pickup. No mowing, pruning, or irrigation work
- Anything requiring a ladder above a safe reach, or roof access
- Pressure washing large surfaces, unless specifically contracted
- Pest control application
If you need those things, you need the right specialist. Asking a porter to do them saves nothing if the work is done wrong or someone gets hurt.
Day porter vs. route porter
Two models are common, and they solve different problems:
- Day porter. A person on site for a set block of hours, say four hours every weekday, handling whatever the community needs that day. Good for larger communities, active clubhouses, and amenities with heavy daily use.
- Route porter. A person who visits several communities on a rotation, spending a fixed amount of time at each on scheduled days. Good for smaller associations that need one to three visits a week rather than a daily presence.
Neither is better; match the model to your own community. Count the shared spaces and the stations, then walk the loop yourself at the hour a porter would walk it. A community whose only shared space is a mail kiosk is a different job from one with a pool deck, a gym, and an event lawn, and the walk tells you which one you have.
How to write a scope that works
The difference between a porter you never think about and one you constantly chase is almost always the scope document. Vague scopes produce vague work. Write yours with these pieces:
- A task list, grouped by frequency. Separate what happens every visit from what happens weekly or monthly. "Empty all trash cans" is a per-visit task. "Wipe down all common-area signage" might be weekly.
- A defined route or zone map. Name the specific areas covered. The north entrance, the pool deck, buildings 1 through 6. If it is not named, assume it will not get done.
- Frequency and hours. How many visits per week, on which days, and roughly how long. This sets expectations for both sides.
- Supplies and equipment. Who provides bags, liners, dog-station refills, cleaning products? Spell it out so nobody is surprised by a supply bill.
- A reporting expectation. How does the porter tell you what they did and flag issues they found? Even a simple photo log or a shared checklist beats "trust me, I was there."
Verifying the work gets done
Porter work is easy to under-deliver on precisely because it is spread out and low-drama. Nobody notices a clean entrance. Everybody notices an overflowing trash can. Build in a simple way to confirm the work:
- A dated photo log of key areas each visit
- A checklist the porter completes and you can review
- A monthly walk-through by a board member or manager against the scope
The record is there for the resident who asks what the porter line pays for. It turns that question into a two-minute answer rather than a defensive one.
Putting the scope to work
A scope this specific is worth posting rather than emailing around. The task list by frequency, the named areas, the visit count, the supply split, and the reporting you expect. That one document is what turns three different ideas of "porter" into one job everybody has agreed to.
A scope is worth writing only if somebody buys against it. Post yours, and local janitorial and porter companies propose on the work you named. Your board reads the proposals side by side and picks one; the contract is between your community and the company it picked, and that company employs its porter and does the cleaning. The three documents that gate a proposal are general liability, workers' compensation, and the credential the trade requires. Each certificate gets opened and verified against the limits your community set. The scope you wrote, the checklist recorded on each visit, the photos, and the company's own invoice arrive in one view, so "what are we paying the porter for" has an answer on the screen.