Table of Contents and listing number of pages

I list the page numbers in the T of C as well as publish the drawing list. I’ve noticed that these documents often are copied and attached to the executed AIA A101. A101 provides columns for section, title and pages.

I guess Im among those guilty of old school thinking since I do include the number of pages for each section in the Table Of Contents. Yall may be forcing me to rethink that practice. What I never do is include Dates! I have never been given the correct date for anything more than two days prior to issue (theyre always changing). The last thing I want to do when trying to finish up a project is go back and insert a bunch of dates. We have established a system where we include an abbeviation for the Issue Identifier (Bid; Bid Package#; Addendum #; whatever) at the left margin adjacent to each section that identifies the Current Issue of each section, BP1 for example. That information doesnt change and I can insert it well in advance of the scheduled issue without fear of last-minute change. The official date of each issue is established by the accompanying documentation. We also identify the Issue on each page of specs with the same identifier, placed in the bottom left corner of each page. I can insert the issue identifier into the footer of a section, even if I begin working on it two months prior to actual issue since I know that wont change. Using this system its real easy to ensure that youre looking at the most current edition of any document, and I dont have to worry about changing dates at the last minute.

I often put a date in the footer on each section, but it is the date that the specific section was last modified - not the date the project manual is issued. It helps me keep track if I somehow discover I have two printed versions of the same section. Unfortunately, it confuses some people who assume I just forgot to correct the issue date on the sections. So, I’m considering abandoning the practice. I still put the issue date on the front cover.

For those who use MasterWorks, creating Table of Contents at the 11th hour is quick and easy. The only thing that will make it difficult is if the files properties have been altered in some way or not updated. MasterWorks requires 3 lines in the Summary tab of the Properties dialogue box. They are Title:, Subject:, and Keywords:

Title: Do not put spaces in the section number per MF04.

Subject: Omit the word section and section nubmer. Keep section name from line 1.

Keywords: If not alerady there, add BAS-12345-MS80 (BAS = BASIC, MS80 = MICROSOFT WORD 8.0) Have now idea what 12345 means. Open an AIA MasterSpec section and take a look.

Creating headers and footers with date or no date is also quick and easy.

In the past I did not put the moving target date in the header or footer and if I did it was monthn/year. The day was unpredictable. I relied in the project manual cover “Issued for Date” and a line in Division 01 Section “Summary”.

All of my current proejct are private. Dates in the header seems to work OK for these projects.

If a section is modified by addendum, I add a second line in the footer (left justified) that reads: Revised by Addendum #X, dated mon/day/year.

If a new section is added, the header reflects the new issued for date and I add a second line in the footer (left justified) that reads: Section added by Addendum #X, dated mon/day/year.

I have grown lazy in my advancing years and have stopped putting page number in the TOC but with the power of MasterWorks, it is quick and easy.

Richard,

I use a date code in the footer of all my specifications. When I print, I simply have to temporary change the date on my computer to whatever the issue date is. I use a date code on all computer generated correspondence as well. That way, I never have to type a date on anything.

It’s possible to put a print/modified date in a text box located in the margin of the first page header of your section. it runs right along the edge of the paper and is usually hidden by the binding of the manual. It helps me keep straight which copy is the latest when faced with multiple copies, but isn’t mistaken for an issue date.

We do large projects exclusively. 10 years from SD to Grand Opening is common, with many anticipated revisions over the years. Another reason I do not provide page counts in the TOC is that I would need to issue a revised TOC each time we added or removed “Tile Type CT-49” or whatever, and gained or lost a page.

Our firm uses a last printed date & filename on the binding edge of the page identifying when last printed, filename, firm author & copyright.

Our table of contents list does not list all the section page counts. We do that with individual Division Sheet Indexes which list page counts for each section. The TOC list only fist page/section to the last page/section number in each division. Each spec section ends with “End of Section” desigination so you know if you have all the pages.

More time, yes… But thats what sets us apart.

DTR what are the benefits of doing what you do?

Page numbers are not used…they always change until the last minute. Just one more thing to coordinate.

Didn’t the CSI specifications competition require pages numbers for the Table of Contents for project manuals that were submitted?