White Label SaaS · glossary
Larchpay's written report on what caused the downtime and what it has done to stop it happening again. Schedule 3 requires one within 10 Working Days after any month with more than 4 hours of unplanned downtime. Agreement, Schedule 3, paragraph 4 · Chapter 6 · see Availability Service Level
Explained in Chapter 6, Service Levels, Service Credits and Support, of White Label SaaS.
After any month over the limit, Schedule 3 also requires a written root-cause report within 10 Working Days. It says what caused the downtime and what Larchpay has done to stop it happening again. Tressick needs it to judge whether the next pay day is safe.Read Chapter 6, Service Levels, Service Credits and Support →
Chapter 1 and this glossary are open to everyone; the whole edition is free to read with a free account until 31 January, and it stays open to an account opened by then.Chapter 1 of White Label SaaS and this glossary are free to read; the rest of the edition is in the Library, at €12 a month or €79 for a Year Pass.
Related terms
Where this term lives
This term is part of one complete fictional deal, with every document attached and a test after every chapter. Open White Label SaaS → · All terms A–Z →