If you're early in your internship under the Internship in Architecture Program (IAP) or its provincial equivalent, you may not have priced a project line by line yet. Here is how to study RSMeans without getting buried in tables of numbers.
Tip 1, study the method, not the numbers. The specific 2012 dollar figures will be wrong for any project today. What the ExAC actually tests is whether you understand quantity takeoff, the four estimate types, location factors, and indexes. Read for method.
Tip 2, remember it is United States base data. RSMeans bare costs are presented at a United States national average and adjusted to specific cities with location factors. For Canadian projects, the location factor is doing real work. Practise applying it.
Tip 3, pair RSMeans with Yardsticks. Yardsticks for Costing is Canadian elemental data; RSMeans is North American unit price and assemblies data. Most ExAC cost-management questions sit at the intersection of the two. Both are primary resources on Examitect's ExAC study plan.
Tip 4, match the estimate type to the project phase. If a question describes programming work, expect square foot or order of magnitude. If it describes design development, expect assemblies. If it describes tendering, expect unit price. The phase tells you the estimate type, and the estimate type tells you the accuracy you can promise the client.
Tip 5, learn one Unit Price page deeply. Open any page in Chapter 6 and identify the description, unit of measure, crew, daily output, labour hours, and the bare and total cost columns. Once you can read one page in detail, every other page reads the same way.
Tip 6, treat the Reference Section as the lookup layer. Location factors, historical cost indexes, square foot costs, crew listings, and the square foot project size modifier all live there. ExAC questions that ask you to adjust a number almost always send you to the Reference Section in real practice.
Tip 7, ask your firm's cost team or senior architect for one walk-through. Pricing a real project, even at the assemblies level, makes the book stick faster than re-reading the chapters. Tie the estimating method to a current job and the workflow becomes intuitive.