What do you make of an end-of-day-one score of 243 for 5? Is there a good 243 for 5 and a bad 243 for 5?
If you're the bowling team, is it better if you've taken those five wickets at roughly equal intervals, or if they've come in a clump? If they've come in a clump, is it better if they came early in the day or towards the end?
Did 243 for 5, in short, represent a good opening day for India at the Basin Reserve, or did it not?
Given the shape the day took, with New Zealand recovering from 70 for 5 thanks to an unbroken partnership of 173 between Henry Nicholls and Glenn Phillips, recent happenings seemed to colour the tone of the end-of-day's-play press conferences, particularly the one attended by India batting coach Sitanshu Kotak.
That India sent out their batting coach on a bowling day was, in itself, a sign of what was to come. It was a strategic decision on a day when they had picked a four-man pace attack that didn't include Mohammed Siraj.
Kotak has this ability to defuse tense exchanges in a gentle, almost avuncular manner. But in a sign of the temperature of the press conference, his replies were terse and carefully unspecific.
"At the time when the team management, the captain, they pick the team, they see what is the best XI they can play, and I think everyone felt this is the best XI, and that's the XI that played."
That was Kotak's reply to the Siraj question, and different angles of attack were met with a similarly defensive blade.
"There's nothing wrong [with Siraj]. I can't see anything wrong," he said when asked if Siraj's performances in Sri Lanka in August, when he was noticeably down on pace, had contributed to his exclusion here. "Like I said, that's the best possible XI the team management thought it was, and that is the one that played. Sri Lanka, obviously it was different conditions, and Siraj played both the Tests there, but there is nothing wrong with anyone."
When asked what specific qualities the four seamers picked here were picked for, Kotak named attributes without attaching them to specific bowlers.
"One obviously is pace," he said. "If it's a short answer, I would say two [bowlers] seam the ball well, two swing the ball well. And obviously pace is one thing, because when you are playing on a wicket which is a little damp, soft to start with, with a lot of grass, we would go obviously [with] one with the height, which gives the bounce, and this is just the first day.
"There will be some dents, it will be second, third and fourth innings also, so when you pick an XI, you think about all four or five days it will go on till, it is not just one day. This is the best possible bowling attack, we felt, and that is the one which played."
Perhaps this was a comment on Siraj having lost a yard of pace. Inevitably, Kotak was asked if Anshul Kamboj - who had bowled a testing new-ball spell but, like most of his colleagues, looked less threatening as the day progressed - hadn't been down on pace himself, having slipped to as low as 126kph on occasion.
"Kamboj bowled quick only - in the third spell there were balls around 129-130 [kmph], maybe a couple of balls were 126," Kotak said. "Yes, definitely pace matters when it's thick grass, because if the pace is low, the batsman gets time to adjust to uneven movement, which is obvious.
"Siraj also is a world-class bowler, there's nothing [wrong with him]. On the day, for this match, we thought this is the best bowling attack."
If the day had ended with New Zealand on the same total after taking a different route to get there, would this press conference have looked and sounded different? Would someone other than Kotak have fronted up?
More pertinently, what did it mean for this Test match that New Zealand were 243 for 5 at stumps on day one?
Given the way the day panned out, this seemed to be one of those classic Basin Reserve surfaces that look ominously green at the start but only test batters severely for the first hour or two before beginning to flatten out. Or like some of the surfaces that India played on during their England tour of 2025, which were helpful to the fast bowlers when the ball was new but docile when it lost its shine.
Control numbers bear out the theory that this might have been a new-ball pitch. Against India's fast bowlers, the batters achieved a control percentage of 78.45 in the first 30 overs, and of 89.47 from the 31st to 80th overs. That's a pretty significant jump.
Given this, and given the fact that India will begin day two with a rested pace attack, with a second new ball that's only two overs old, and with New Zealand's lower order just one wicket away, this Test match might still very much be in the balance.
There is, however, one caveat - that the old-ball control numbers might have reflected not just the conditions but the limitations of India's attack. Until New Zealand have bowled on this surface, we won't know if there's a significant gap in old-ball threat between the two attacks.
This was a key factor in New Zealand's 2-0 victory the last time India played a Test series here, back in 2019-20, and Matt Henry's skill with the wobble seam and Kyle Jamieson and Jacob Duffy's extra height could well get more out of this surface with the old ball than India's fast bowlers did.
This, however, is still only a hypothesis.
India had a tall, hit-the-deck bowler of their own, and Prasidh Krishna performed a thankless job for most of the day. He was the fourth seamer used, which meant he only bowled three of the first 30 overs. Without a new or new-ish ball for him to get too much out of the surface with, India mostly used him in an enforcer role, setting short-ball fields and asking him to bend his back and hit the pitch hard.
It's a role with the potential for leaking runs, and Prasidh has done this in the past. On this day he was India's most expensive bowler, but still went at less than four an over. And he could have had a wicket to show for his efforts if Devdutt Padikkal had held on to a steepling top-edged hook from Nicholls in the 74th over of the day.
"Prasidh, being an attacking bowler, we actually know that he can go for a little more runs than others, but that is the choice you make," Kotak said. "When he bowls a good spell, when he gets two-three wickets in quick time, people like it, but when he goes for a few runs, people don't like it. You can't just comment like that on a bowler [after one] day."
That Prasidh only went at 3.62 despite being India's most expensive bowler, and that New Zealand's sixth-wicket pair scored at only 3.22 per over despite putting on 173, suggested that India might have actually done a pretty good job of controlling the scoring when wickets weren't coming their way.
One factor behind this was India following up on their pre-match claims and picking four genuine fast bowlers. Perhaps this was the reason why Siraj didn't play. Jasprit Bumrah is Jasprit Bumrah, and Prasidh offers the point of difference with his hit-the-deck style, and Siraj could have only played ahead of Akash Deep or Kamboj. But those two have better batting credentials, and India may have viewed them as a No. 8 and 9 who could together score the runs that Nitish Kumar Reddy might have made at No. 8.
Even if it's unclear that India picked their best four fast bowlers, they picked four proper fast bowlers. It meant New Zealand didn't get pressure-release overs from a non-threatening allrounder, and it meant that the four quicks were all used roughly equally - all of them bowled between 15 and 18 overs on day one.
Another contributor to India's scoreboard control was the performance of Washington Sundar, who played ahead of Ravindra Jadeja because his offspin was viewed as a bigger threat against New Zealand's exclusively left-handed top four. Washington conceded just 38 runs in 16 overs. Kotak said he had allowed India to manage both their over rate and their seamers' workloads.
"Both things," he said. "With four fast bowlers, any team will have to bring on the spinner to control the over rate. And even the [fast] bowlers, you can't be using them for more than 15-16-17 overs on day one. And particularly when the spinner isn't giving away runs, you have to hold one end and attack from the other with the fast bowlers, so that went well actually."
India left out two big names at the Basin, in Siraj and Jadeja, and the exclusion of the former will, in particular, continue to be hotly debated. There is little question that Siraj bowling at his best would have offered more of an old-ball threat than either Kamboj or Akash Deep did on Thursday, particularly with his wobble-seam ball.
But India's handling of Siraj over the last few weeks suggests he may not be bowling at his best. Could India have done more to help him get back to his best, either by giving him a run of games in the ODI series or by sending him to Wellington after the third ODI to join the pre-Test-series camp? Probably.
But it's not clear that Siraj in his current red-ball form - whatever that may look like - would have done more than Kamboj or Akash Deep did on Thursday.
And it's not clear that India did much wrong as a bowling unit, or that they are in anything but a position of parity in this Test match. For now at least.
