Repair Workflow Setup

Within 10 working days, every open repair is controlled through a working system.

Each repair has an owner, status, next action, chase date and update status. The workflow is designed, configured, tested and handed over inside a suitable tool your team can use every day.

£750 founding-client rate One reactive-repair workflow One team Up to approximately five staff
Property management office where a repair workflow can be operated
Repair A · active record Under control
OwnerProperty Manager A
StatusWaiting on contractor
Next actionConfirm appointment time
Chase date14 July
Tenant updateSent, next update due
Landlord updateApproval recorded
01Named owner
02Working status
03Specific next action
04Visible chase date
05Update status
Keys and residential property representing a managed lettings portfolio
Ideal customer and trigger

Built for a small lettings team with real repair volume and inconsistent follow-up.

The best fit is an independent UK lettings agency or property-management team that already has a way to log repairs, but does not have a reliable working view of ownership, waiting points, next actions and updates.

  • Tenants or landlords repeatedly chase for repair progress.
  • Contractor appointments, estimates or completion evidence are overdue.
  • Repairs become unclear when a team member is absent or work changes hands.
  • A manager cannot see the active queue and current next step quickly.
  • Portfolio growth has made the existing informal process unreliable.
  • The team is preparing for a service review, complaint trend or operational improvement push.
Not the right fit: a business with little active repair volume, several teams or branches needing one enterprise rollout, or a project that depends on complex custom development.
Controlled scope

One workflow, one team and a finish line everyone understands.

The fixed scope keeps the ten-day build realistic and protects the project from turning into an open-ended systems programme.

01One reactive-repair workflow

From initial report through ownership, action, chasing, updates, completion checks and closure.

02One operational team

A single lettings or property-management team using one agreed working route.

03Up to approximately five staff

The setup, testing and training are designed for a small group of active users and cover.

The client supplies the agreed list of active repairs in a usable format. Large historical data clean-up or migration is not included.

Ten working day delivery

Discovery, Design, Implementation, Testing and Handover.

Each stage produces a working decision or completed part of the system. The service does not end with a report or recommendation pack.

Days 1 to 201

Discovery

Review the current route, team roles, approved sample repairs, current tool and the points where ownership or follow-up breaks down.

Day 302

Design

Define the workflow stages, fields, owners, update points, alerts and completion checks in a Setup Plan for approval.

Days 4 to 803

Implementation

Configure the approved workflow inside the agreed existing tool or a suitable lightweight tracker.

Day 904

Testing

Run agreed sample repairs through the route, test ownership, dates, views and supported alerts, then correct in-scope issues.

Day 1005

Handover

Demonstrate the working system, deliver one hour of team training and provide the operating guide.

When the clock starts: the ten working days run from the agreed start date after the first payment, required access, active-repair information and client point of contact are in place. Delayed access or approvals pause the timetable.
Exact deliverables

A working repair-control system, not advice about what you might build.

The deliverables are configured, tested and handed over within the approved scope.

01Working repair viewOne agreed view or tracker showing the active repair queue and the fields the team needs to control it.
02Defined statusesA short status set matched to the real repair stages, including visible waiting points and completion checks.
03Ownership rulesRules for the current owner, cover arrangements and when responsibility moves or returns to the team.
04Next-action and chase fieldsA specific next action, responsible person and chase date for each open repair.
05Update status and templatesPractical tenant, landlord and contractor messages for acknowledgement, delays, appointments, outcomes and closure.
06Overdue views or alertsOverdue visibility and basic reminders where the agreed tool supports them without complex development.
07End-to-end testAt least one agreed sample repair processed through the implemented workflow and completion criteria.
08Training and handover guideOne hour of team training and a concise one to two page operating guide for daily use.
Fourteen days of minor in-scope adjustments

After handover, the team can request small changes within the approved design, such as renaming a status, adjusting a reminder time or refining an update template. New features, additional workflows and integrations are separate scope.

Supported tools

Use a suitable tool you already have, where possible.

The service is tool-aware, not tied to one software brand. During Discovery, I confirm whether the current system can support the agreed owners, statuses, actions, dates, views and alerts.

If a specialist property or repair platform is already in use, the Setup can work around its existing repair record and supported follow-up functions. Platform-specific configuration is confirmed case by case.

No blanket software claim: naming a tool here does not mean Property Follow-Up is an accredited partner or specialist implementer for every feature. Only supported, testable configuration agreed during Discovery is included.
Environment 01Existing property-management or repair platform
Environment 02CRM with suitable fields, tasks and views
Environment 03Microsoft Lists or Planner, Asana or Trello
Environment 04Excel or Google Sheets lightweight tracker
Price and risk control

A fixed founding-client rate with clear payment points.

Founding-client rate
£750

Fixed total for the stated scope

One reactive-repair workflow, one team and up to approximately five staff.

  • £375Due to book the project and begin Discovery and Design.
  • £375Due after the final working-system demonstration and agreed completion checks, before the adjustment period.

Clear Setup Guarantee

You approve what will be built, see the system working before the second payment and have a defined period for minor in-scope adjustments.

  • Approved plan first: the workflow, fields, ownership rules and deliverables are written into the Setup Plan before implementation.
  • No unapproved build: work outside the approved plan is not added without a separate agreement.
  • Working demonstration: the configured workflow is demonstrated before the second payment becomes due.
  • Fourteen-day adjustment period: minor changes within the approved design are included after handover.
  • Feasibility boundary: if Discovery shows no practical in-scope solution can be delivered, the project pauses before build and no second payment is due.
Completion means: the approved reactive-repair workflow is implemented in the agreed tool, the required owner, status, next-action, chase-date and update fields are visible, one agreed sample repair passes the end-to-end test, and the training plus handover guide have been delivered.
Exclusions

What the £750 Setup does not include.

Anything outside these boundaries needs a separate scope or is declined.

×

Complex development

No custom software build, advanced coding, complex API integration or enterprise automation programme.

×

Large migrations

No large historical data migration, extensive record clean-up or full replacement of a property-management system.

×

Unrelated workflows

No planned maintenance, inspections, lettings progression, general operations or other processes outside the agreed reactive-repair workflow.

×

More teams or users

No multi-branch rollout, several operational teams or training programme for more than the agreed small group.

×

Ongoing administration

No contractor chasing, tenant communication, call answering, repair processing or daily operation of the system after handover.

×

Legal or technical judgments

No legal advice, hazard assessment, compliance certification, contractor selection or guarantee of third-party response times.

Questions before buying

The practical details.

The scope is intentionally specific. If your situation falls outside it, that should be clear before the project starts.

What if we already use a repair platform?

The aim is not to duplicate software. I first check whether the existing tool can support the agreed workflow. Platform-specific changes are included only when they are supported, accessible and agreed.

When do the ten working days begin?

From the agreed start date after the first £375 payment, required access, active-repair information and client point of contact are ready.

Will you move all our historical repair data?

No. The client provides the agreed active repair list in a usable format. Large historical migration or extensive data clean-up is excluded.

What counts as a minor adjustment?

Examples include renaming an approved status, refining a template or changing a supported reminder time. A new workflow, integration or feature is separate scope.

Do you guarantee faster contractors or fewer complaints?

No. The service guarantees the agreed setup process and completion criteria. It cannot guarantee contractor behaviour, tenant satisfaction or a legal or regulatory outcome.

What must our team provide?

One point of contact, timely access, approved sample repairs, the active repair list, design approval and staff attendance for Discovery, Testing and Handover.

Next step

Put every open repair behind a clear owner and next action.

Ask about the £750 founding-client Setup, or start with the free Repair Workflow Review if you want a one-page view of the proposed starting point first.

Scroll to Top