Open a landlord maintenance job report — Maintenance requests and tenant feedback
Review work evidence for a linked job.
Exact navigationLandlord Portal/Client Portal → Maintenance → Job Report
Before you begin
- Use an account with Authenticated linked landlord contact and confirm the intended record or setting before making a change.
- Follow the exact route above. If the screen or action is absent, check module activation, ownership and permissions rather than using another person’s account.
- Use controlled test data for configuration, integration, email, AI, payment, portal or automation changes before production-wide use.
What this guide covers
Review work evidence for a linked job. The instructions reflect the supplied module’s registered menus, controller actions, views, settings and code-backed validation flow.
Exact step-by-step process
- Open Landlord Portal/Client Portal → Maintenance → Job Report.
- Select the relevant record, filter, report, model or configuration described below.
- Use the displayed action or read the current values without altering unrelated data.
- Compare the output with the code-backed rules and expected result in this guide.
- Record or correct any mismatch before relying on the output in production.
Fields, choices and supported possibilities
Exact actionOpen a landlord maintenance job report
Exact navigationLandlord Portal/Client Portal → Maintenance → Job Report
Module version1.0.0
Access ruleAuthenticated linked landlord contact
VerificationReopen the source record and confirm the expected status, linked record, file, notification, portal visibility or financial effect.
Request recordCode, client, property/item, request type, currency, property price, term and inspection choice.
Notes and billingClient note, admin note and billing/shipping data where the form exposes them.
ConversionReview status and linked customer/property before converting to a contract or invoice.
Tenant/applicantIdentity, contact, current address, employment/income, occupants, pets, smoker/benefits/children flags and right-to-rent data where exposed.
Tenancy termsProperty, tenant client, start/end/move-in dates, term, rent, frequency, deposit, holding deposit and deposit scheme.
Consent and workflowInvite mode, consents, review notes, agreement template/body, signature stage and workflow action.
Maintenance requestProperty, tenant, subject/issue, priority, status, supplier, assignee, cost and administrative note.
Supplier work orderJob title/description, property/manual address, allocated amount, supplier notes, photos and completion evidence.
Financial linkSupplier invoice status, amount/final amount, payment mode, transaction ID and payment comments.
Organisation/personName, code, email, phone, website, tax/VAT, address, status and profile image where exposed.
Access and structurePlan, role, administrator flag, departments, staff type/company link, approval-manager and public flags where applicable.
Report filtersSelect the displayed month/year/custom period, status, property type, city, listing or payment criteria.
Source verificationOpen source property, request, tenancy, contract, invoice or payment records to reconcile totals.
Code-backed validations and workflow rules
- The job ID/property relationship is validated.
- Buy and rent requests use separate real_buy_request and real_rent_request capability groups.
- Status changes and conversion actions validate the current request and linked record IDs.
- Public application and onboarding actions use token/record checks and explicit workflow states.
- Do not advance a workflow until the required party, property, dates, financial terms and consent/evidence are complete.
- Maintenance hub visibility is tied to customer-view access in the registered menu.
- Supplier completion can create a Pending supplier invoice when one does not already exist.
- Company, owner, broker and staff records use different capability groups and ownership checks.
- Email-exists checks prevent duplicate staff/company identities in supported forms.
- Reports require real_report view capability.
- Report results depend on stored status/date/currency values and the current user’s accessible data.
Expected result and verification
- The supported open a landlord maintenance job report flow completes without bypassing permission or validation checks.
- The resulting record, setting, status, file, delivery event or external response is visible from the relevant workspace.
- Unexpected validation, provider or linked-record errors are investigated before retrying.
Security, privacy and operational checks
- Apply least privilege to purchasing, vendor, invoice, payment, return, contract and report permissions.
- Verify vendor identity, bank/payment details, tax, currency, totals and approvals before creating financial commitments.
- Treat public links, signatures, portal files, attachments and exported reports as controlled business records.
- Test settings and automated jobs with controlled records before production-wide use.