Thirty Days on the Wall

Create up to 20 seconds from 0:00. Available for free opening episodes. Preparing a clip downloads this episode on your device.

The counter was above the coffee machine on Monday morning. David could see it from the queue, losing seconds while the machine made the same indifferent grinding noise for everyone. Twenty-nine days and something. The display had turned a month into a quantity small enough to watch being spent.

His question had acquired a second acknowledgement during the night. The team responsible for validation would respond in due course. There was no original annex attached. He showed the message to Priya, who read it standing beside a table already occupied by someone's unopened folder.

"Due course isn't on the timetable," she said.

At nine, Elise led them into the assessment room. Each desk had a screen and a folded card carrying a participant number. David found his beneath the name displayed at the welcome. Priya was two rows away. The woman beside him introduced herself as Lena Ortiz and immediately asked whether the afternoon session would finish at the advertised time. She had another piece of paid work to deliver that evening.

Elise said the schedule was designed to accommodate professional commitments. Lena wrote that down rather than thanking her for understanding.

The first assignment was not to manage a real fund. It was a paper exercise using a supplied set of businesses, price histories and fictional constraints. They had to select assumptions, construct a model and explain what would make it fail. No customer money would be moved. No participant was being asked to execute a trade. David found the boundaries reassuring because they were specific, unlike almost everything said about the consequences of failure.

The file supplied to his desk contained a data sheet, a submission template and an account of how a common reference would be used to assess their work. The reference itself was not included. A note said its construction was confidential to preserve the integrity of the competition.

Someone at the back asked how they could distinguish a bad assumption from a departure from an undisclosed benchmark.

"By explaining your assumptions," Elise said. "The evaluation rewards reasoning, not imitation."

David wanted that to be true. He began with the question the assignment actually asked, which was how a paper portfolio behaved under a sudden interruption to revenue. There were limitations in the supplied history. He marked them. Then he made an estimate where the template required one, and labelled it an estimate rather than allowing the spreadsheet to disguise it as a fact.

The work absorbed him. For twenty minutes, the counter ceased to exist. He changed an input, watched the result move and traced the movement back through the cells. Here, at least, uncertainty had a place to go.

At eleven, a new banner appeared above the submission button. Current methodology acknowledgement required before final validation.

He stopped typing.

The read access Elise had enabled still worked. He could open the template and save his own work, but the button which would formally accept the submission was grey. Beneath the banner, a link led to the same receipt-and-agreement box he had left empty the previous night.

Lena leaned across the space between their desks. "Is yours doing that?"

"Yes."

"I've got three hours of work in this."

He had nearly as much. Around them, chairs shifted. One participant clicked through and resumed typing. Another called Elise over. David looked at the time remaining before the first submission deadline, which was noon, and understood how an unanswered question could be made to look like his decision to miss it.

He asked Elise whether the system could record delivery without requiring acceptance of the disputed schedule. She said she could not change the standard acknowledgement on an individual screen.

"Then how do I submit the work the signed letter requires?"

She asked him to wait while she consulted the technical team. David saved an ordinary copy of his model and explanatory note. He checked that the files opened on his own machine. The saving did not prove he had submitted anything, but it prevented a portal problem from becoming the loss of the work itself.

At eleven twenty-eight, Elise returned with an alternative. The participant address could accept the files, provided the subject included his number and the assignment code. Staff would register them manually. It was an accommodation for the unresolved access issue, not agreement with his interpretation of the contract.

He asked her to put the route in writing. For the first time, impatience showed in her face.

"You are standing in front of me, David."

"And tomorrow someone else may be reading the receipt."

She considered him, then sent a brief message from her programme account. It contained the address, the two required identifiers and the noon deadline. He thanked her without trying to turn her irritation into evidence of anything larger.

Priya had come to the desk. She read the route only when Elise showed it to her, not by looking over David's shoulder. Her own acknowledgement question was different, she said, but she needed the same alternative. Elise sent the instruction to all twelve participants.

The address accepted David's files at eleven forty-six. An automated receipt listed both filenames. He replied asking staff to confirm that both attachments were readable. At eleven fifty-three, a person answered that they were and that the submission had been registered on time.

He wrote the two times beside the assignment code in his notebook. There was satisfaction in the small completeness of the record. He knew it was not an answer to the larger question.

At lunch, Priya asked whether he would mind discussing the assignment without sharing their actual model choices. They sat outside with sandwiches bought from a shop rather than the programme café. David had noticed the café prices. He suspected she had too.

She had asked for the reference construction before signing. The answer had described a stable comparison, with adjustments to be explained when used. The language did not make it clear whether a participant could inspect those explanations before a result became final.

"I've worked with proprietary models," David said. "Not everything can be open."

"I didn't ask for their software. I asked what I would be compared with."

He broke a piece of bread off his sandwich and failed to find a useful reply. She did not press the advantage. Instead she asked what he wanted from the month, and the ordinary question was more difficult.

"Work people will take seriously."

"Work, or people?"

He laughed without pleasure. "Both, preferably."

Priya ran a small practice. A client had delayed payment, and a larger assignment she had expected had gone elsewhere. She had accepted the Challenge because the sponsors could commission the kind of careful, unglamorous analysis she liked. She did not describe herself as trapped. She described herself as someone who could not afford a month which ended with nothing but a certificate.

David thought of telling her about his lost client. He said instead that he had been taking shorter assignments. It was true, and he recognised the shelter he was using it for.

During the afternoon review, Rusk spoke about intellectual courage. The twelve paper models had produced different results, which he called evidence that genuine thought was taking place. He did not name a winner. The first provisional scores would appear that evening; final validation would follow review of the explanations.

David asked whether a provisional adverse score could by itself initiate a payment claim. Rusk turned toward him with the attentive expression from the welcome.

"A number does not send an invoice," he said. "People validate obligations. We expect professionals to complete that process."

It was reasonable enough to win several nods. It did not identify the obligations, the people or the process David had asked about. He sent the question again afterward, including the words provisional score so nobody could answer a different one by accident.

At six seventeen, the portal showed his result. Sixty-four evaluation units. Completed, provisional, awaiting validation. Beside it, a separate field for cost allocation said Not determined.

He downloaded the result supplied to his account and compared the submission identifier with the receipt. They matched. The result was not brilliant, but it was respectable. He caught himself feeling relieved by the score even though he had spent the day asking how it was made.

In the hotel, he put the first receipt, the readable-attachments confirmation and the result in one folder. Then he opened tomorrow's assignment and set a limit on how long he would work before eating.

The limit arrived. He ignored it for nine minutes, corrected one label, and finally closed the laptop. Outside, the city was conducting an evening which had no interest in where he ranked.