The Wet Slab
Evelyn
The man with the measuring wheel wants me to walk across the slab again. Rain is running down the back of his collar. He has the particular patience of somebody who is being paid by the hour and knows I am not.
“Ordinary steps,” he says. “Don’t help yourself.”
“I wasn’t helping myself.”
“You were reaching. Like a flamingo.”
I take my boots back to the chalk mark. Behind us the temporary footbridge makes a short gray line between two banks of nettles. It looks too small to be worth this much trouble. A truck could lose the entire thing under a load of gravel without noticing. Three steel beams, timber panels, handrails wrapped in plastic. I have spent most of the morning checking the beams on paper. Now I am here to confirm the dimensions, and I have made the mistake of telling the foreman that my pace is good enough for a first comparison.
Cal Mercer rolls the wheel beside me. Its counter ticks through the rain. I keep my arms down and stop trying to impress a man whose gloves have holes in all the useful places.
At the far end he reads the counter and waits while I divide the distance by my steps. I do it in the margin of my waterproof notebook. The pencil is flat and red, stamped with the contractor’s name. I borrowed it when mine rolled into a drain.
“Two foot seven,” I say.
“Near enough for finding your truck. Not near enough for putting a bearing on concrete.”
“I do know that.”
He looks at my notebook. “Good. Write it somewhere you can see it.”
Twenty-six years old, in my second year at a job I worked most of my life to get, and I have just received a lesson in walking. I write the number anyway. There is a difference between being embarrassed and being wrong, although my ears refuse to learn it.
Cal takes me to the east abutment. The new deck ends at a concrete pad beside the old stonework. On the school side a path bends behind a fence, then climbs toward a redbrick building with bright paper triangles in its windows. The water below is narrow and brown. A shopping basket catches weeds against an upstream grille. Nothing about it resembles the clean blue stroke on my drawing.
“Leat,” Cal says when I call it a stream. “Fed the mill. Most of the water goes under the road now.”
“Does this branch still take flood flow?”
“Sometimes. I’m not the water man.”
He says it without defensiveness. I like him better for that. People in offices can answer a question beautifully long after they have stopped knowing the answer.
I put the tape on the bearing pad while he holds the other end. The beam locations agree with my copy. So do the bolt centers. A wrapper from a sandwich sticks to the sole of my boot, and I spend a minute scraping it off on a stone because I cannot bear to take it onto a school crossing. Cal watches me with the first suggestion of amusement I have earned.
“Not opened yet,” he says.
“It can start clean.”
“Tell the pigeons.”
The last dimension is the level at the east approach. A brass survey nail sits in the older slab, surrounded by a painted circle. I crouch to read the little aluminum tag fixed beside it. The tag carries a reference code and an elevation. My drawing carries the same code. The number beside the code is different.
I wipe the tag with my sleeve. Rain immediately fills the letters again.
“What’s the trouble?” Cal asks.
I show him both. He bends awkwardly, one knee refusing to fold all the way, and holds his cap over the tag while I take a photograph. The camera focuses on the drops. I try again, closer. This time the stamping is clear.
“Old mark,” he says. “They’ve probably transferred it.”
“Then it needs a new reference.”
“Probably does.”
The discrepancy could be ordinary. Surveyors change control points. Drawings arrive at different revisions. Someone leaves an old tag in place because removing it is nobody’s job. I have done enough checking to know that most frightening numbers become dull after one phone call. I have not done enough to stop hoping for the dull phone call.
Cal takes me to the site cabin. Wet coats steam on hooks beside a heater. A kettle rattles as if it contains screws. Leon Briggs has a ruler across an invoice and is crossing out something with a pen that costs more than my watch.
“Our engineer,” he says. “How’s the little bridge?”
“I’ve got a query on the east survey reference.”
“Then it’s lucky you’re here.”
He pulls out a chair with a dry seat. There is no reason to dislike him. His boots are muddy, he has been here since before daylight, and he moves a stack of papers so I can spread my drawing without putting it in somebody’s lunch. I show him the photograph.
“Superseded,” he says immediately.
“Which survey replaced it?”
“I’ll get you the sheet. The office has everything.”
He starts looking through a folder before I can ask another question. Cal stands by the door, turning his cap in his hands. I can hear the wheel measure dripping onto the floor outside.
Leon finds a plan with the approach shaded yellow. It has the same elevation as mine. Across the bottom, in small lettering, is the statement that existing ground conditions are to be verified against the inspection report. The report number is familiar. It sits in the assumptions box on my calculation sheet.
“There,” he says.
“That tells me the design level. I need the survey that establishes it.”
He looks up. His expression does not change much, but he stops turning the pages.
“We aren’t building a motorway, Evelyn.”
I feel my cheeks warm again. He has used my first name from the visitor form. I am still calling him Mr. Briggs in my head.
“I know what the bridge is for.”
“Good. Because the school has been waiting since January, and the old route is a mile around. Peter knows the situation. All of this went through him.”
Peter Hale is my project director. He also signed my leave request last week and asked whether I was settling in well. I have not yet learned how to hear his name on a construction site without feeling that I am being called into his office.
“I’ll ask him for the revised survey,” I say.
Leon smiles. “That’s the sensible thing. Coffee?”
I decline because I already need the toilet and the cabin has only one, behind a door that does not latch. Outside, I pull the hood of my coat up and find Cal putting the wheel into the back of his truck.
“Do you remember them moving the control point?” I ask him.
“I wasn’t here for the survey.”
“Who was?”
“Groundworks lot. Different foreman then.”
“Could I have his name?”
Cal searches my face. “You making a list of people to blame?”
“I’m making a list of people who might know.”
He closes the tailgate. “Might look the same from where they’re standing.”
That is fair enough to annoy me. I write the former foreman’s name after Cal gives it, along with the fact that Cal was not present for the survey. There are small ways a notebook can become dishonest without a single false sentence. You leave out what someone did not see. You put two answers next to each other and let the reader supply a connection. I make a gap between his account and my photograph.
The rain eases while I return to the slab. From here I can see a low arch of brick almost hidden by leaves below the path. It is not on the site arrangement drawing. It might be an abandoned drain. It might lead nowhere. Water has polished a dark strip across the brickwork, though, and the nettles immediately below it are flattened.
I stay behind the temporary rail and photograph the arch from the accessible path. I cannot see its other end. On the plan in my hand, that part of the bank is solid shading, an uncomplicated piece of earth holding up the end of an uncomplicated bridge.
Somebody calls from the school fence.
A woman in a purple raincoat has a ring of keys hooked over one finger. She is holding a rolled banner under her arm, sheltered in a clear plastic sleeve. She asks if I am the person who can tell her where the children should stand.
“For what?”
“The photograph on Friday. We’re keeping them off the bridge itself until the ribbon’s done. Leon said that was sensible.”
I look at the deck again. The protective plastic is still on the rails. At my office the schedule shows the installation finishing this week. It does not show children with scissors and a ribbon.
“Have you got an opening time?” I ask.
“Ten. Parents at half past nine. I’m Inez, by the way. School office, which means everything nobody else can find.”
I introduce myself and explain that I am checking part of the engineering package, not arranging the opening. Her smile slips only a little.
“Will it be ready?”
“I can’t answer that today. There are checks still to finish.”
“Leon told us there was only paperwork left.”
The banner slides against her sleeve. She catches it with her elbow, and I see a cartoon bridge printed on the fabric. Every child in the picture has both arms in the air. Somebody has drawn a dog on the handrail. It is an ugly, cheerful thing, made by people who expect the ground to remain under them.
“Sometimes the paperwork is the check,” I say.
She looks past me, toward the cabin. “Should I stop handing out invitations?”
I want to say yes. I also want to say something that will not be repeated as an instruction from an engineer who has found a dangerous bridge. I have not found that. I have found a number I cannot reconcile and a brick opening I do not understand. Those facts deserve attention without becoming a diagnosis I cannot support.
“Please ask the project manager for written confirmation before you make any arrangements you can’t change. I’ll put the question in my report today.”
“That’s a long way of saying you don’t know.”
“It is. Sorry.”
She laughs once, without much pleasure. “At least you let me get there.”
I give her the office number and my extension. She gives me a school card with her own handwriting across the back, because the printed number reaches a menu she says was designed by a person who has never needed anything. Then she walks back along the fence with the banner under her coat.
I telephone Peter from the bus shelter. The site is a dark rectangle across the road. My trousers have wicked water almost to the knee. When I sit down, the cold from the metal bench comes through the rest of them.
“What’s happened?” he says, before I explain.
“Nothing’s happened. I’ve got a reference discrepancy.”
I hear his keyboard stop. I describe the tag, the drawing, the opening in the bank. I keep each observation separate. It takes longer that way. A bus passes without stopping because I have not raised my hand, and I watch my ride home disappear around the bend while Peter asks whether I have checked the revision register.
“I will in the morning. I haven’t got remote access to the whole file.”
“Don’t send queries to the client until you’ve checked our records.”
“The school thinks it opens Friday.”
“It does, subject to approval.”
“Do they know the subject-to part?”
He exhales close to the receiver. “Evelyn, I need the steelwork calculation by tomorrow afternoon. The ground inspection is an existing-structure matter. We’re checking a replacement deck, not redesigning the bank.”
“The calculation assumes the supports are adequate.”
“Of course it does. And there’s a report for that. Read it before you make work.”
He is not shouting. There is no unfairness I can point to in being told to read a report. Still, I look at the photograph on my phone after the call and feel the odd wish that the rain had made it unreadable. Then I could go back with a reason nobody could argue with. A clear photograph requires me to decide what to do with it.
I type an email with my thumbs. Site visit observations, not conclusions. I attach both photographs, describe the mismatch, ask where the replacement survey is filed, and state that I have not verified the ground conditions supporting the design assumptions. Peter gets it. The project inbox gets it. I do not send it to Inez because I have not established a public safety finding, and I am still junior enough to think distribution lists can make a fact either responsible or reckless.
Then I call Rachel. She answers over a sound like a cupboard full of cups falling down.
“Please tell me that’s at work,” I say.
“Dog bowls. Why are you whispering?”
“I’m not. I’m freezing.”
“Come over. I’ve got soup.”
“You’ve got an exam tomorrow.”
“And soup. Two things can happen.”
I tell her I will come at the weekend. She tells me to buy something hot before I get on another bus, then asks how the little bridge went. I say there is a number I need to check. She says numbers are usually where I start being happy.
After we hang up I go to the shop next to the shelter and buy a tea that tastes of the paper cup. The woman behind the counter lets me stand under the heater while she counts change. On the wall is another poster for Friday, already curling at the corners. I look at the cartoon dog and wonder who has been told the bridge is safe, and by whom, and how many times the sentence has traveled without the qualification attached.
Back at the shelter I open the notebook on my knee. Under the reference code I put the number from the tag, then the number from the drawing. I draw no line connecting them. I do not yet know which one belongs to this slab.
The next bus arrives in a gust of dirty water. I wave this time. Before I stand, I make a square around the discrepancy, pressing hard enough that the pencil dents the page beneath it. I have a report due tomorrow, a damp coat, and no sensible reason to be frightened.
I put the wrong number in a box and carry it home.
A Number Missing
Evelyn
By Tuesday morning my coat has dried into the shape of a person who has given up. I hang it behind my chair and open the Mill Lane file before I take the lid off my coffee. On the screen, the project directory offers me eight folders called Final, Current, Revised, and variations of those words that cannot all be true.
The revision register lives under General. I print it and put a ruler below each entry as I read. There is one survey issued for design, one revised approach drawing, and a note saying the existing abutments have been inspected. No replacement survey. No instruction to transfer the brass reference mark. The number on the slab has not simply fallen out of the paperwork. According to the paperwork, it was never changed.
At nine I telephone the surveyor. His voicemail tells me he is away until Thursday. I leave the reference code, my name, and a request for whoever is covering his work. Then I make a sketch of what I saw, with the open leat below the deck and the little brick arch under the east approach. I leave the concealed length of the arch as a dotted line. It is tempting to draw it straight through. That would make the picture satisfyingly complete and possibly entirely false.
Peter arrives carrying a box of pastries for the team. He puts one on my desk before he takes his coat off.
“A dry site visit next time,” he says.
“I’d settle for a site visit with the right drawing.”
He looks at my printouts. “Still on that?”
“The register doesn’t show the survey Leon mentioned.”
“Have you asked Leon?”
“I copied him into the query this morning.”
“Good. Let him answer it. How’s the calculation?”
The answer is that the calculation is right if the assumptions are right. I turn the screen toward him and show him the support condition carried across from the inspection report. He bends to read, one hand on the back of my chair.
“That’s standard,” he says.
“It is. I need the report to support it.”
“The report’s in the folder.”
“I’ve got the summary. I can’t find the test annex.”
“Then ask Document Control.”
He says it kindly. He also moves my ruler off the printed register to give the pastry a safer place. I pick it up again after he leaves, embarrassed by how much that tiny interruption has unsettled me.
Document Control is a desk beside the copy room, occupied by a woman covering two people’s leave. She shows me the transmittal while answering another phone with her shoulder. The original inspection package had a cover, twelve numbered pages and an annex listed separately. Our received PDF ends at page twelve. Its contents list still names the annex.
“Was it a separate attachment?” I ask.
She points to the attachment count. Two files. We have one in the current directory.
“Might be in the email archive. Put in a request.”
“Can I look while you’re busy?”
“You haven’t got permission for that mailbox.”
I stand there a moment, holding the transmittal. I dislike the rule because it slows me down, which is a bad reason for deciding it does not apply. She gives me the form for access, and I fill it in at the end of her desk while she tells someone that a file called New New Final is not a document number.
In the copy room the old plan copier gives off a hot chemical smell. A fluorescent tube flickers over the paper tray. I print the inspection summary at full size and lay it beside my site photograph. The report refers to a drainage feature at the eastern approach. The drawing calls that whole area existing compacted fill. Neither statement rules out the other. Neither tells me whether anyone looked below the place where the support load is supposed to go.
Mara Singh returns my call at eleven. Her firm carried out the earlier tests. I recognize her voice from a training afternoon, where she told a room of graduate engineers that measuring something once did not make it a property of the universe.
“Are you the person who asked about the annex?” she says.
“Yes. Evelyn, Halloran and Voss.”
“Which version of the report have you got?”
I read the date and reference. She asks me for the number after the slash. I give it. There is a silence while she retrieves something.
“That’s the surface survey summary,” she says. “What are you using it for?”
“Checking the assumptions for a temporary deck.”
“It doesn’t establish bearing capacity.”
“The cover says existing abutment inspection.”
“The cover describes the commission. The limitations describe the work we were allowed to do. Read me the last paragraph on page twelve.”
I do. It says no intrusive investigation was undertaken in the eastern approach pending access approval. The words have been in front of me all morning. I have read them twice. Only now do I hear the difference between an inspection of something and an inspection prevented from reaching part of it.
“Was access ever approved?” I ask.
“Not under that instruction. There’s a separate note about the culvert. It should be in the annex.”
“Is that the arch facing the leat?”
“Could be. I won’t identify a structure over the phone from a description. Send me your photograph.”
I send it while we talk. She asks for the drawing too and says she can compare the records but cannot give me a fresh site opinion from an office chair. I tell her the public opening is Friday. This time the silence lasts longer.
“Who is signing the opening approval?”
“Peter Hale.”
“Then Peter needs to read the complete report.”
I write down her exact distinction: complete report, not another engineer’s summary of it. When we end the call, I stand up too quickly and catch my knee on the underside of the desk. The pain is small, ridiculous, helpful. It gives me something to do for a few seconds other than look at Peter’s closed door.
He is in a client meeting. I send a short note asking him not to rely on the summary for ground conditions until the annex is recovered. I attach Mara’s email confirming what she has actually said. Then I return to the steelwork calculation and finish the arithmetic. I can do that part honestly. It is almost a relief to work inside a question with edges.
At lunch, a colleague asks why I have not signed the internal review box. I tell her about the missing attachment. She rolls her eyes in sympathy and offers to show me how to search the archived correspondence. I say I have asked for access.
“You’re making it official?”
“It’s project work.”
“Right. I just mean, it usually goes quicker if you ask someone who can get in.”
She is trying to help. I know she is. I thank her and take my sandwich to the little courtyard, where the benches are dry on the side nobody wants to sit on. A bus engine idles beyond the wall. I eat standing up and try to work out when finding a missing attachment became the sort of thing a person could do too officially.
The access reply arrives at one fifteen. It authorizes Document Control to retrieve the original message for me. It does not give me the mailbox. By two I have a printed copy log showing that both attachments were received and distributed on the same afternoon. The annex file name contains its own revision suffix. Someone saved the summary into Current and put the second attachment in Correspondence, under the contractor’s message rather than the report number.
There is nothing sinister about that. Filing systems fail all the time. I feel so relieved that I almost stop reading.
Then I see the note beneath the attachment names. Replacement pack to follow. Disregard second attachment pending clarification.
The instruction came from Leon.
I ask Document Control whether the replacement pack was received. She searches the project number, then the sender, then the date range. There is a later email with a clean summary attached. No annex. The clean summary has the same report reference but a new cover note saying the site information has been confirmed by the contractor.
“Is that normal?” I ask.
She gives me a tired look. “Normal isn’t a filing category. Do you want both?”
I do. She saves read-only copies into a review folder and records the retrieval in the register. I take the printouts back to my desk with a care that would be absurd if anybody were watching. There is no theft, no locked drawer, no page slipped under a coat. There are simply two versions of the thing I have been asked to trust.
Leon rings before I have finished comparing them.
“Heard you’ve been digging through the archives,” he says.
“I’ve been trying to find the report annex.”
“I’ve sent you the right package now. Have a look in your inbox.”
His new message arrives while the phone is against my ear. A PDF opens with a clean title page, tidy bookmarks, all twelve pages in order. The contents list no longer includes an annex. In the limitations paragraph, the eastern approach is described as outside the original testing scope. That matches the older summary. It still does not establish the ground condition.
I scroll to the signature sheet. It is an image of Mara’s firm’s signed page, carried over from the earlier issue. The new contents page has no separate signature or revision record. I ask Leon whether the testing firm approved this compilation. He says the technical text hasn’t changed, which answers a different question.
“Can you show that the annex was withdrawn?” I ask.
“Not from here.”
I open a blank comparison table and put the question in it before we continue. I have nearly accepted the tidy appearance as evidence of a new professional opinion. In fact, the new package gives me less information under the old signature. I could close my query now and probably nobody would ask why. That possibility makes me stop scrolling. I leave the signature page on screen, put the earlier contents list beside it, and wait for Leon to tell me who authorized the difference.
He asks if I am still there. I say yes.
“Who revised the contents page?” I ask.
“Our office assembled the pack. Saves you carrying obsolete sheets around.”
“The testing firm hasn’t issued a replacement report.”
“It’s the same report. Different compilation.”
“Then I need the omitted material as well.”
He lets me hear the site around him: a reversing alarm, somebody calling for a gate to be opened, the practical urgency of people doing work while I ask about pages.
“Evelyn, your manager asked us for a usable pack. That’s what we’ve given him. If there are questions, Peter can deal with them at his level.”
“Please send the annex.”
“I’ll see what’s available.”
Afterward I save his new message beside the retrieved one. I do not overwrite the old package. The computer asks me whether I want to replace a file with the same name, and my finger hovers over the blue button before I realize what an efficient way that would be to lose the whole argument.
I add the received date to both file names. Then I make a comparison note that says exactly what changed: contents page, cover note, omitted attachment. I do not write falsified report. I do not yet know who changed what beyond the compilation Leon has acknowledged. The restraint costs me more effort than an accusation would.
Peter calls me in at four. The pastry box is empty on his cabinet. He has my calculation open, the unsigned review box yellow on the screen.
“We need to be proportionate,” he says.
“Mara’s report doesn’t support the ground assumption.”
“Mara wasn’t commissioned to. That’s what I’ve been telling you.”
“Then what does?”
He folds his hands. “The contractor has undertaken to verify existing conditions.”
“Where’s the verification?”
“I’ve asked Leon.”
“So have I.”
He looks at me for long enough that I can hear the clock above his door. I have not meant to challenge him. I have meant to locate a piece of evidence. But the effect in the room is the same.
“Finish the part you’re responsible for,” he says. “State the assumption clearly. I will resolve the wider issue.”
“Will you tell the client it’s unresolved?”
“That is my responsibility.”
I leave with no instruction I can fairly call wrong. Finish the calculation. State the assumption. Let the senior engineer resolve the rest. Yet the word unresolved has not appeared anywhere in the file except in messages I have written myself.
Back at my desk I complete the calculation note. Beside the support assumption I add that verification of existing ground conditions remains outstanding and that the calculation is not an approval to open the crossing. I send the draft to Peter for review. My hands are steady while I type, which surprises me. Perhaps I have used up all the shaking on arguments that did not need it.
Mara’s reply to my photograph is waiting. She cannot confirm the full culvert alignment from the picture, but the brick opening is consistent with the structure mentioned in her annex. Her firm’s archive contains a signed copy, held under the council commission. She can release it through the client; she cannot quietly send it around the client because I sound worried.
I telephone the council engineering office. The first person transfers me to highways, the second to records, and the third asks whether I am reporting a blocked drain. By the time I reach the project administrator, I have rehearsed the request so often that it comes out without any of the anxiety I started with.
She asks for the report number, my employer, and Peter’s authorization for project-record access. I send the request with Peter copied. She gives me a case reference and a slot the following morning for supervised inspection, subject to confirmation. I repeat the reference back and write it at the top of a new notebook page.
Outside the office windows the cleaners have begun dragging the courtyard chairs into a stack. I save the day’s comparison note, put the original printouts in a folder, and leave a copy in the project record. Nothing is hidden. That ought to make me feel safer. Instead it makes every step feel visible.
Before I shut down, I check the new council reference once more against the email. It is a small, plain string of characters. It proves only that I have asked a question and that someone has agreed to keep the request.
The missing page has a number, and now so do I.
