To write a maintenance request email with photos, identify your unit and the exact spot, describe what you can observe, say when you noticed it, and ask for a clear next step. Attach a few useful images with matching filenames. Send through your building's correct channel, then keep the sent message and the attachments you actually sent.
Use the copyable maintenance request email templates for a routine first request and a follow-up. Replace every bracketed field and remove anything that is not true. These are communication aids, not official notice forms. An ordinary email may not satisfy the formal notice process that applies to your rental.
First check the reporting channel and urgency
Find the maintenance instructions in your lease, resident portal or move-in materials. Check the actual recipient rather than sending to a marketing address or a former manager. Some properties use a portal for requests and email for coordination. If so, adapt the wording below to the portal fields and save the confirmation it produces.
If there is immediate danger, leave the unsafe area and use the appropriate emergency service or building emergency contact. A routine email is not an emergency response channel. Do not stay near exposed wiring, an active hazard or an unstable fixture to take a better photograph.
For a question about legally effective notice, use local guidance. USAGov's tenant-rights page directs renters to state agencies and other housing assistance. This article does not set a nationwide repair deadline, access rule or escalation procedure.
What should the maintenance email include?
A helpful message lets the reader identify the place and understand the request without reconstructing a long conversation. Begin with the issue and unit. Put the specific observations before background, and separate what you know from what you are asking someone to inspect.
| Element | Useful content | Leave out or qualify |
|---|---|---|
| Subject | Maintenance request — [unit] — [specific location and issue] | A vague “urgent!!!” for a routine issue |
| Location | Property/unit, room and identifiable fixture or spot | “The cabinet” when several fit that description |
| Observation | What is visibly different or what you actually experienced | Unverified diagnosis, blame or a guessed cause |
| Timing | When you noticed it; when the attached photos were taken, if different | A claimed start date you do not know |
| Next step | Request inspection or repair and ask how access will be arranged | A promise of unrestricted entry you did not intend to give |
| Photos and reply details | Short attachment list, contact details and relevant availability | Access codes, identity documents or unrelated private photos |
Be specific without diagnosing. “The upper corner of the door sits lower than the neighboring door” describes a visible condition. “The hinge was installed incorrectly” states a cause you may not be able to establish. A clear description can still ask for attention without pretending you performed an inspection.
Use honest dates and plain wording
Distinguish “I noticed this today” from “this began today.” The first can be accurate even if the condition existed earlier. If you only know an approximate observation date, say that. Do not turn a phone's file date into a stronger claim than your knowledge supports.
Keep the request focused on the current issue. If a related request already exists, give its actual reference number and date. Avoid adding unrelated complaints simply because you are writing an email; separate issues may need their own tickets or locations under your property's process.
Include relevant access constraints as coordination information. For example, ask the recipient to contact you to arrange access rather than putting a door code in an attachment. A sentence in this template should not silently replace whatever access arrangements or notice requirements actually apply.
A routine maintenance request email example
This fictional example concerns a visible cabinet-door alignment problem, not an emergency. The bracketed fields deliberately remain blank. Choose words that match your situation; do not copy the described condition if you have not observed it.
Subject: Maintenance request — [property and unit] — kitchen cabinet door beside sink
Hello [maintenance team or manager],
I am requesting an inspection of the kitchen cabinet door immediately [left/right] of the sink in [unit]. I noticed on [actual observation date] that the upper corner sits lower than the neighboring door. I do not know the cause.
I have attached [actual number] photos taken on [actual photo date]:
- [actual filename] — kitchen view locating the cabinet.
- [actual filename] — closer view of the door alignment.
Please let me know the next step for inspection or repair and how access should be arranged. You can reach me at [contact details]. [Relevant availability or access constraint, if appropriate.]
Please confirm receipt and provide a request number if one is assigned.
Thank you,
[name]
[property and unit]
The message asks for a next step without claiming a contractor's conclusion. It does not say the condition is your fault, the landlord's fault, new, dangerous or already accepted. If additional facts matter, add them accurately rather than relying on this example's phrasing.
Before sending, check the subject against the body and filenames. Remove unused bracketed fields. Confirm that the attachments are present and show the same cabinet you named. Save a working copy separately if you want to keep drafting; the draft is not your record of delivery.
Choose photo attachments that explain the request
Start with a location view and a closer view of the relevant condition. Add another image only when it answers a different question. Several nearly identical close-ups can hide the useful detail and make a message harder to review. There is no universal required number of photos.
Name attachment copies so they can be matched to the message, such as kitchen-cabinet-location.jpg and kitchen-cabinet-alignment.jpg. Keep a record of which original each copy came from. Check what the receiving channel accepts before converting a file or compressing it for email.
Preserve originals independently. If you crop or annotate a copy to point out a feature, label the copy and do not discard the unedited source. A mark on an image can explain which area you mean, but it should not obscure the feature or imply a measurement you did not take.
Review the edges of every image. Remove unrelated mail, screens, identity documents, faces and private belongings from the frame where you safely can. If redaction is needed, retain the original privately and send a clearly identified edited copy. Check the resulting image before attaching it.
A photo can show a visible surface or location. It may not show intermittent behavior, a sound or a hidden cause. Describe an experience in words and be clear about what the image cannot establish. Do not repeatedly operate a faulty fixture or open a cover to manufacture a more convincing picture.
For Gmail on a computer, Google's official attachment instructions explain adding files and handling size limits. Check the actual attached files before sending, whichever email app you use.
Watch on YouTube ↗
Follow up with the original request attached to the context
Follow your property's process for checking status. If you follow up by email, reply in the existing thread where practical and reference the actual submission. Check whether a reply or portal update has already arrived before saying you have received no response.
Subject: Follow-up — [actual request number or original subject]
Hello [team or manager],
I am following up on the request I sent through [actual channel] on [actual date] about [specific issue and unit]. The request number is [actual number, or remove this sentence].
As of [date checked], I have not found [a receipt/an inspection appointment/a status update — choose the accurate description]. [State any new observation and its actual date, if relevant.]
Could you confirm the current status and the next step for arranging inspection or repair? I have included the original request below [only if actually included].
Thank you,
[name and unit]
“No appointment arranged” is different from “no reply received.” Preserve that distinction. If management says a repair is complete but the visible issue remains, describe the later observation and ask for clarification. Do not rewrite the earlier message to make it look as if it contained information you learned afterward.
This example intentionally gives no automatic waiting period. Local requirements, the actual condition and the property's reporting process can affect the appropriate next action. If conditions become urgent, reassess safety and use the appropriate immediate channel rather than continuing a routine email exchange.
Keep the sent email, photo sources and actual replies
After sending, save the original message in a form your email service supports, with the attachments. If you used a portal, retain the request text, actual ticket number and available confirmation or download. Check that the saved files open. A note that you planned to send something is not a substitute.
| Record | What it helps establish | What it does not establish by itself |
|---|---|---|
| Private photo and note | What you recorded and how you described it | Notice to management or authenticated capture time |
| Sent email or submitted ticket | The text and files in that actual submission | That a person read or agreed with it |
| Receipt or acknowledgment | What the system or recipient actually confirmed | Agreement about cause, responsibility or completion |
| Later reply or observation | A specific update, commitment or visible later condition | A missing earlier state or an unrecorded conversation |
The value of retaining correspondence is not just our suggestion: in its New York City repair guidance, NYC HPD tells tenants to keep a copy of a repair letter and records of contact attempts. That page describes a local process; its delivery instructions and legal rules should not be generalized to every rental.
For a broader filing routine, see how to keep rental maintenance records. This email becomes one source in that record, alongside the photos and later updates. The separate photo export guide covers an independently usable copy of your image archive.
Where Tenacove fits in this workflow
Tenacove organizes photos and notes by room, spot and stage. It does not send this maintenance request to your landlord. Original emails, PDFs and videos are not imported as source records, so retain those in your own correspondence archive.
A Lease Pass offers optional email receipts, check-ins and move-out reminders. Those are separate from reporting a repair to management. An archive receipt records an archive event; it is not a landlord acknowledgment. To see the workflow without uploading private photos, explore the synthetic sample home, whose fictional records are separate from a real account.
Maintenance request email FAQ
Does an email count as formal repair notice?
Do not assume so. The applicable law, lease and required delivery process matter. Use this guide to compose a clear routine message, then check the appropriate local instructions if formal notice is needed. A good subject line does not solve a delivery requirement.
What if I do not know what is causing the problem?
Describe what you observed and ask for inspection. Identify uncertainty directly. A photo of a mark or misaligned door can locate the issue without proving the underlying cause. You do not need to supply a diagnosis to explain what needs attention.
Should I send my whole photo archive?
Usually a focused selection is easier to understand. Send the views relevant to this request through the accepted channel, retain originals privately, and offer more context if needed. Avoid a broad shared folder that exposes unrelated tenancy records or changes after the recipient opens it.