As I’ve said in other posts, writing time isn’t just hard to come by: It’s non-existent right now.

Except, that is, for at work. I’m working on two or three essays based on past of future presentations I’ve made. More on those later. This week I’ve had the pleasure of working on a construction specification. The project is a tire shop in Oklahoma. The client is a major tire dealer that we developed the standard specs for. Actually, I’m the one who developed the standard specs for them, a year or so ago, maybe a little longer. They had seen our specs, saw what we did (I do) with internal notes to guide the spec writer, and wanted us to do it for them.

The project manager had already downloaded the specs needed from the client’s website and put them in a project folder on the network. I opened them one by one and saw the notes to specifier in bold red staring at me. On a real project situation I was able to read those notes and do what they suggested. Overall I found them to be pretty good. My attention was directed to where in the spec section it was most needed.

On the project I found four construction items for which we did not prepare a standard spec for this client, so I’m having to create them—not quite from scratch, though. Two of them are similar to sections we already have, so I’m able to pull them up, modify them as needed, and save them as new sections. I’ll do that for the project. Then, hopefully before the end of the year, I’ll expand them, first into a guide spec for our company; second as a standard spec for that client.

I have one new product added to an existing section, one of the new sections done, and a second new spec section started. Next will be the section from scratch. Actually, even that won’t be from scratch as they’re using a proprietary product on the project so I can take the manufacturer’s spec and modify them.

It’s not exactly creative writing, but it is writing. And I need to get back to is.

As I’ve said elsewhere, the Time Crunch has prevented me from working on my different writing projects. Alas, that’s how life is sometimes. That’s how it is now, and for the foreseeable future. I have no expectations of doing much writing for the rest of 2014.

But, yesterday, during my noon hour, I had a few moments to think about things, and decided to see exactly what I had written this month. Pulling things together, checking a few websites, I came up with a long list. It is summarized as follows.

• 6 posts at this blog
• 5 posts at my other blog
• My first devotional, turned in on the 20th
• 3 comments at the Books & Such blog
• 2 brief comments at the Passive Voice blog
• 1 comment at the Absolute Write forums
• 17 personal e-mails, some of them one-liners
• 39 work e-mails, some of them one-liners

All of these aren’t publishable writing pieces, but they are writing. It doesn’t include many posts on Facebook, both writing related and personal. Nor does it include a couple of things at work that are started only in outline form. These are “curriculum” type items, cobbling together various classes I’ve taught over the last eight years into eight to ten class courses. So far I haven’t done any original writing on them, but most likely will before the end of the month.

That also doesn’t include three new classes that I’m preparing to teach: one in November, one in December, and one probably next March. Each of these will require quite a bit of prep for a one hour class. At least one of them (the one in March) will have a significant essay as part of it.

So, I have been writing this month; just not publishable things, with one exception. I guess I need to take what writing I can find time to do.

Last week at work I found myself in a position I’d waited for for a long time: All major tasks caught up, all training planned and in motion for the next few weeks, and the ability to look for things I’d left hanging or set aside but could not pick up again.

The last of my major tasks was a project audit. I finished that early last week, and shot off e-mails to the Dept. Head, requesting a meeting to discuss the results. I knew his key man on the project was out last week, so the meeting about the audit results would be delayed. With that done (on Tuesday, I think), and with me not having to teach a class all week, I sat back and said, “What to do next?” Almost immediately I answered, “Work on the spec for stormwater underground detention.”

One of my jobs at CEI is “keeper of the standards”. It’s up to me, working with our corporate CADD trainer, to make sure whatever standards we have for engineering work are up to date and being followed. The project audits are to see how well the standards were followed on a project. Construction specifications are part of that. I maintain our database of guide specification sections. Construction specs has been a passion of mine through the years. I enjoy that part of a project more than any other.

I guess I enjoy them because it’s word-smithing. You try, in a few pages, to tell the contractor in words what you can’t easily show in pictures. When lines on a drawing fail you, you use words. But the language is different. You are terse. You don’t worry about complete sentences. You use lists when you can. You leave out many definite and indefinite articles. You talk directly to the contractor, so can leave off a lot of unnecessary words. I love it. So different from creative writing, but I love it. When I teach classes on spec writing, I always say “You aren’t writing literature.”

An example of best practice in specifications language can be seen in the following three ways to say a thing.

• The Contractor shall construct a underground detention basin.
• An underground detention basin shall be construction.
• Construct an underground detention basin.

Eight words, seven word, and five words in those three examples. The third one is considered best practice, and the way I do it.

In this particular spec section, I had set it aside almost a year ago because I couldn’t pull it all together. We have a choice between many available systems: plastic, metal, concrete, manufactured, built-in-place, half concrete half earthen, arch structures, pipe structures, etc. Each one has advantages. Our office tends to use one specific type more than others, though others can be considered. I started out writing a spec section that would include all types of systems, but found it impossible to do so in less than 10 to 14 pages. A spec section that size is too long. So I decided to break it into two of three sections, and concentrate first on the plastic structures. Once I did that, it started to come together quickly.

But, when I laid it aside, it still wasn’t quite done. I had taken out all the extraneous language on concrete and metal systems, but hadn’t really described the different plastic systems available. It was Wednesday last week, I think, that time became available. I picked up the spec section and began properly describing the different plastic systems available. I had to name a couple of categories of systems. I had to research ASTM standards (mostly done before). I had to fit everything into the pigeonholes established by the construction specifications standard-setting organization.

One big thing I had to do was write a section on the actual construction. This was difficult because the differing systems available require different construction sequences. We generally don’t like to give the contractor a lot of restrictions on the “how” part of construction, or the sequence. But we do have to say a few things. I managed to put something together, and I had a completed spec. That was mid-day on Friday.

The next thing I did was e-mail it to each of the manufacturers mentioned, to make sure I have it right for their system. I did so on Friday, with one straggler going out yesterday. Slowly, responses are coming in. Today I’ll start taking a look at those, and tweaking the spec based on the comments.

Spec writing is as far away from creative writing as you can get. Except for making every word count. And using active voice as much as possible. And making sure you are communicating to your intended audience in a way that will be understood. I hope the next few months provide me with much more time to work on specs. It will make me a better writer.

I continue with my creative writing endeavors. Last night I made good progress on Documenting America: Civil War Edition. I typed some writing from manuscript, and added to it on the computer to complete a chapter. Then I continued research into the next chapter to be written. Today I completed reading the source document, and read some background material. Tomorrow I’ll excerpt the material and write the chapter. Good stuff, good progress.

But my main writing work yesterday and today was working on my technical paper for the EC15 conference. The paper was due today to the International Erosion Control Association. I still haven’t finished and submitted it. The presentation will be in Portland, OR next February. Long lead time, I know.

The idea for this paper came to me over a year ago, and gelled into an outline at the EC14 conference in Nashville last February. The concept was: gather data from the bid forms from a number of projects about how erosion control work is bid out. Analyze the data, as well as qualitative information from the projects, to see if one method of contracting seems to be better. My hopes, and soft expectation, was that unit price contracting, as opposed to lump sum contracting, would be better for erosion and sediment control work. Hence the name of my paper: “Unit Price Contracting for Erosion and Sediment Control Work: Does it Improve Our Practice?”

I gathered the data (i.e. the bid forms) from ten projects several months ago, and talked with our employee who handled the field work on several of those projects. I’m a big fan of unit price contracting because it is a risk-sharing approach to construction contracting. Explaining what I mean with that would be way too long for a blog post. I teach a 90 minute class on that topic. I felt that going with this risk-sharing approach for erosion and sediment control work would result in better prices, better implementation  of devices and practices, better maintenance of these devices, and less pollution to the environment. It was the ultimate win-win situation to me.

But that’s my intuitive analysis, based on my own biases and qualitative analysis. What would the data say? As I said above, I gathered the data some time ago, and had aggregated it into one spreadsheet. I created my outline about a month ago, and wrote a tentative introductory sentence. There the paper stood until yesterday just afternoon.

At that time I started with the real writing. I had much more introduction to write, then get into an explanation of what I mean by “improved practice.” I also had a little more outline to think over, and dusting off and re-looking at the data. I did all this, and by the end of the day I had a little over 900 words. I anticipate the paper will run somewhere around 3,000 words, so this seemed like reasonable progress. I was pretty sure I wouldn’t be able to finish the paper today, but I might get close.

The morning was full of meetings, site visits, and a little personal stuff. I got back to the paper around 1:30 p.m., ready to write the part about the hard data I collected and draw some conclusions out of it. I started writing, but when I got to the part where I should show what the data said, I realized I had never gone the next step and done a few calculations to see what the data actually said. Did it support my hope and anticipation that unit price contracting would result in less expensive erosion control measures that were equally effective as were those of a project that’s where the erosion control work is bid as a lump sum?

So I stopped writing and went back to the data. I quickly saw that I had too much data. I wasn’t going to be able to present all the data I had intended; it would overwhelm the paper. Including it in an appendix was a possibility, but for the moment I had to concentrate on what was in the paper.

I dug into it, and after an hour figured out what I had to do. I ran the calculations needed, from the data already in the spreadsheet, then ranked the projects according to which had the least expensive erosion control, then penciled in the type of bidding used (unit price, lump sum, mixed). To my great pleasure the five lowest cost projects (on a unit basis) for erosion control work were the five that were bid as unit prices! The most expensive three were the ones that trended most to lump sum, using fewer unit prices. My hope and expectation had been realized. On two projects I didn’t have enough data to do the full calculations and rank by unit cost.

I e-mailed the IECA education coordinator, telling her I wouldn’t have the paper in until Tuesday and hoped that would still be alright. I believe it will be. I printed the paper and have it here. I’ll work on it some, or maybe a lot, this weekend. Hopefully by Monday it will be written. All I’ll have to do is see if I can find the rest of the data for those two projects, and interview the field man to get his further opinion on the non-qualitative criteria.

I wish I had it done by the deadline, but I feel good about it. The end is in sight, and it will be a good paper.