I’m a project manager at a contract archaeology company, which means I have to be both an archaeologist and a businesswoman. Anathema to purists, maybe, but in the United States most archaeology is done commercially, as part of an industry called Cultural Resource Management (CRM), and businesses need people doing business-y things to keep them running. In CRM, developers hire archaeologists and architectural historians to help them deal with cultural resources that will be affected by their development project, in much the same way as they hire environmental scientists, traffic engineers, and architects. We work for the developer, but our first duty is to the resources.
For me, the 2012 Day of Archaeology was pretty typical. My primary task for the day, as it has been for the last month or so, is to continue editing a site report. The archaeologist who wrote the report works mostly on prehistoric sites, but this report is about a historic site. Since it’s her first historic-period report, we’re taking our time with it to teach her how to do it right. Historic-period artifacts require completely different analysis knowledge than prehistoric artifacts (e.g., learning to recognize mold seams on bottles or differentiate fabric types in ceramics, vs. categorizing edge flaking in stone tools), which takes time to learn. You also have more lines of evidence (in the form of historical maps and records) that you need to bring in to your analysis. Work on the report has been slow-going because I often am too busy with other things to get a chance to work on it.
The Day Begins
My first task upon getting to the office–after brewing a pot of tea, of course–is to check in with our people in the field. Today we have two field projects going on, both of which are in the monitoring stage. “Monitoring” means that an archaeologist watches the construction crew as they dig, in order to spot any emerging resources (artifacts/sites/etc.) before they’re damaged or destroyed. Monitoring is usually done after we’ve already done testing and evaluation of anything we know is on site, and is largely a failsafe to protect things we didn’t know were there.