Release procedureRef 04Mitchell Finance & Technology Ltd

Publishing & releases

Getting software live accurately, and keeping a record of every change.

App store submissions

Finance apps often face additional review questions. We prepare accurate descriptions, real screenshots, privacy declarations based on the data the app genuinely collects, and documentation reviewers may request, such as evidence of your relationship with an authorised provider. Developer accounts are held by your organisation.

Change control for web releases

  • R1

    Change list

    Written in plain English, linked to the request that prompted it.

    Before
  • R2

    Staging test

    Calculation tests pass; a person checks key journeys with test data.

    Before
  • R3

    Backup

    Taken and verified immediately before release.

    Before
  • R4

    Release and check

    Released in a quiet period; live check recorded.

    During
  • R5

    Rollback ready

    A tested way back if anything misbehaves.

    After

Hosting and domains

We set up hosting in the region your data policies require, TLS certificates, email authentication records so your messages are less likely to be spoofed, backups and monitoring. Everything is documented in a handover guide.

Release notes

Every release has notes written for users and a separate technical record for your team and auditors.