FTS commercial lane
40 hours · Proposed September commencement
02

Platform Maintenance

A 40-hour monthly maintenance retainer for support, upkeep, monitoring, corrective work and technical continuity from September.

Capacity
40 hours / month
Commencement
September proposed
Relationship
Maintenance + projects
Rollover
No expiration
Executive summary

Platform Maintenance becomes the steady operating relationship after Finish. Forty hours each month are prioritised across support, maintenance and small corrective work. New features, site builds and Assessment AI sit in separately scoped Project Work.

Signal
40hMonthly maintenance
Signal
7Maintenance task groups
Signal
0hProject work inside retainer
01 · Maintenance scope

What can be completed within the retainer.

Typical maintenance tasks, prioritised against the 40-hour monthly allocation.

01

Maintenance agreement

  • 40 hours per month
  • Proposed commencement in September
  • Unused hours roll over without expiration
  • Monthly priorities agreed with FTS
1
02

Production incidents and support

  • Production incident investigation
  • Service restoration and break/fix
  • Application error and log review
  • Business-hours operational support
2
03

Bugs and corrective changes

  • Reproducible defect fixes
  • Regression corrections
  • Permission and access fixes
  • Small workflow corrections
3
04

Patching and technical upkeep

  • Application and dependency updates
  • Security and configuration maintenance
  • Database and integration upkeep
  • Stability and resilience improvements
4
05

Integration and workflow monitoring

  • Invoice and MYOB queue monitoring
  • Email and document processing checks
  • Scheduled job and integration failures
  • Post-release smoke checks
5
06

Data and administration maintenance

  • Company, vendor and estate record corrections
  • Duplicate and incomplete data clean-up
  • Import and export validation
  • Administration configuration changes
6
07

Minor improvements and reporting

  • Small reporting and dashboard corrections
  • Minor usability improvements that fit within capacity
  • Monthly completed / open / proposed report
  • Hours used, remaining and rolled over
  • Larger work moves into a separate project scope
7
02 · Value

What value it will deliver.

The operational and commercial return, stated plainly.

01

Operational continuity

FTS retains access to the platform knowledge required to support and maintain the system.

02

Predictable maintenance

A finite 40-hour allocation keeps routine support and upkeep visible and prioritised.

03

Clear project investment

New initiatives are scoped and approved separately instead of being hidden inside maintenance.

03 · Next steps

What happens next.

A short sequence with an owner and a clear outcome.

Confirm September commencement

Confirm the proposed start month.

FTS

Finalise maintenance priorities

Agree the task types and first monthly priority list.

FTS

Confirm rollover rules

Confirm no-expiry rollover and the bank arrangement.

FTS

Complete Finish handover

Move monitoring and maintenance items into the retainer.

White Tower team

Start monthly maintenance reporting

Report completed work, hours, rollover and next priorities.

White Tower team

Decision requested

Confirm September commencement for the 40-hour Platform Maintenance retainer.

Decision · September + 40h