The week that fell apart
Monday: a web application test booked for five days. On Friday afternoon the client emails to say the release has slipped, can you start next Wednesday instead? The tester booked for it now has three empty days this week. Next Wednesday they are already booked on an internal infrastructure test that cannot move because it has been arranged around the client's change freeze.
Your operations manager opens the scheduling spreadsheet. It has testers down the side, weeks across the top, and coloured cells for bookings. They look for another tester with web application experience who is free next week. There is one, but they are on leave on the Thursday. Could the test be split? Maybe. Meanwhile, a different client has been waiting for an earlier slot and would take this week, if only their scoping were finished.
By the end of the day there are three calls to clients, a tester doing report writing to fill the gap, and the spreadsheet is a little more out of date than it was.
And the tester whose week vanished has now spent a day being shuffled rather than testing, which is the time a testing firm can least afford to lose.
Why testing calendars are fragile
- Client dates move for reasons you cannot control: releases, change freezes, internal approvals.
- Each engagement needs specific skills (web, mobile, cloud, infrastructure, social engineering) and sometimes specific certifications or clearance.
- Readiness depends on things outside the calendar: signed authorisation, credentials issued, test environment available, VPN access working.
- Report writing and QA time after each test is often not booked, so it squeezes the next engagement.
- The schedule is a spreadsheet, so it cannot tell you which bookings are at risk.
What schedule churn costs
| Scheduling failure | Cost |
|---|---|
| Test postponed at short notice | Tester idle, billable days lost |
| Readiness not checked | Test starts without access, days wasted |
| Wrong skills booked | Weaker test or reshuffle at the last minute |
| Report time not booked | Reports late, next test squeezed |
| Waiting clients not offered slots | Work goes elsewhere |
For a testing firm, tester days are the product. Every day lost to a reshuffle is a day that cannot be sold again.
The scheduling tool we build
- Every engagement has its test types, estimated days, required skills and certifications, client constraints (dates, testing windows, change freezes) and the report and QA time that follow.
- Testers have skills, certifications and clearances recorded, along with leave, training and internal work.
- The calendar shows bookings by tester and by engagement, and suggests testers who match an engagement's needs and are available.
- Each booking has readiness checks: authorisation signed, credentials and access confirmed, environment ready, briefing pack complete. Checks not met by a set point before the start date flag the booking as at risk and alert the account manager.
- When a booking moves, the tool shows the knock-on effects and a list of other engagements that could fill the gap, based on readiness and client flexibility.
- Clients can be offered earlier slots from a waiting list when gaps open.
We can build this as a standalone tool or around your existing practice system, pulling engagements from your CRM and writing bookings to testers' Microsoft 365 or Google calendars.
What the operations manager sees
One view of the next few weeks: bookings, readiness status, and which engagements are at risk. When a client postpones, the options to fill the gap are listed immediately. Testers see their upcoming engagements with the briefing pack attached. Report and QA time is booked as part of each engagement, so the next test does not start with the last report still unwritten.
Over time you also see patterns: which clients move dates most, which readiness checks fail most often, and where your skill mix is thin.
That last point matters when you hire. If the calendar keeps showing cloud configuration reviews waiting for the one tester who does them, you have evidence for the next hire rather than a feeling, and you can see how often that skill gap has cost you a booking.
Is your calendar like this?
- Tester schedules live in a spreadsheet.
- Client postponements leave testers with empty days.
- Tests start without access or authorisation ready.
- Report writing time is squeezed between tests.
- You struggle to find a tester with the right skills at short notice.