<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>time - Stephen Ullstrom</title>
	<atom:link href="https://stephenullstrom.com/tag/time/feed/" rel="self" type="application/rss+xml" />
	<link>https://stephenullstrom.com</link>
	<description>Indexing &#38; Writing</description>
	<lastBuildDate>Tue, 05 May 2026 16:15:17 +0000</lastBuildDate>
	<language>en-CA</language>
	<sy:updatePeriod>
	hourly	</sy:updatePeriod>
	<sy:updateFrequency>
	1	</sy:updateFrequency>
	<generator>https://wordpress.org/?v=7.1.3</generator>

<image>
	<url>https://i0.wp.com/stephenullstrom.com/wp-content/uploads/2014/12/w0BqQSga-54a1c676v1_site_icon.png?fit=32%2C32&#038;ssl=1</url>
	<title>time - Stephen Ullstrom</title>
	<link>https://stephenullstrom.com</link>
	<width>32</width>
	<height>32</height>
</image> 
<site xmlns="com-wordpress:feed-additions:1">66154179</site>	<item>
		<title>Indexing Big Books</title>
		<link>https://stephenullstrom.com/indexing-big-books/</link>
					<comments>https://stephenullstrom.com/indexing-big-books/#respond</comments>
		
		<dc:creator><![CDATA[Stephen]]></dc:creator>
		<pubDate>Tue, 05 May 2026 19:11:53 +0000</pubDate>
				<category><![CDATA[Indexing]]></category>
		<category><![CDATA[Indexing Insights]]></category>
		<category><![CDATA[Recent Work]]></category>
		<category><![CDATA[Work Process]]></category>
		<category><![CDATA[audience]]></category>
		<category><![CDATA[book indexing]]></category>
		<category><![CDATA[Index]]></category>
		<category><![CDATA[indexes]]></category>
		<category><![CDATA[indexing]]></category>
		<category><![CDATA[main headings]]></category>
		<category><![CDATA[speed]]></category>
		<category><![CDATA[subcontractors]]></category>
		<category><![CDATA[subheadings]]></category>
		<category><![CDATA[time]]></category>
		<category><![CDATA[work process]]></category>
		<guid isPermaLink="false">https://stephenullstrom.com/?p=1899</guid>

					<description><![CDATA[I’m currently indexing a history of nuclear reactors. It is about 300,000 words. Meticulously researched and written, with a strong narrative. It is a big book, and it is taking a while to get through. It is also not the only large volume I’ve indexed this year. I feel like I’ve done more than usual,&#8230;&#160;<a href="https://stephenullstrom.com/indexing-big-books/" rel="bookmark">Read More &#187;<span class="screen-reader-text">Indexing Big Books</span></a>]]></description>
										<content:encoded><![CDATA[<p>I’m currently indexing a history of nuclear reactors. It is about 300,000 words. Meticulously researched and written, with a strong narrative.</p>
<p>It is a big book, and it is taking a while to get through. It is also not the only large volume I’ve indexed this year. I feel like I’ve done more than usual, including an Oxford handbook on Baptist studies, an edited collection on Black Canadian art and literature, and a biography of Canadian poet Margaret Avison. These are books that are the equivalent of two or three regular-length volumes.<span class="Apple-converted-space"> </span></p>
<p>Large books can be challenging to index. I have a theory that the length of the index grows exponentially with the length of the book (while, maybe not quite exponentially, but the length does grow), because the longer the book, the more details there are to index, the more locators there are, and the more likely subheadings are needed. Subheadings take up more space and take more time to write and edit, and so the work goes on and on. Also, the larger the book, the more there is to keep in mind. I need to remind myself to reset my expectations for how long the index will take.<span class="Apple-converted-space"> </span></p>
<p>I still want to complete the index efficiently and as quickly as possible, even if the overall number of days and weeks is longer. I’ve been reflecting on what it is I do that is different compared to indexing a shorter book. This is what I’ve gathered so far:</p>
<ul>
<li>I write more notes for myself, such as brief summaries for each chapter. Because there is so much more to remember, I don’t want to forget what the beginning of the book was about by the time I reach the end. These notes can also help me see the overarching storyline and themes running through the book.</li>
<li>I slow down and consciously remind myself to connect back to the big picture. With so many pages to get through, the temptation is to rush and to focus on picking up the easy entries—the low-hanging fruit—of people, places, reactors, chemical elements, etc…Those details are important and need to be picked up, but why are they important? What is the larger discussion or story? I need to make sure that I am creating headings and subheadings at those broader levels too, which means slowing down and understanding what all this is actually about.</li>
<li>I write subheadings at a broader level. I still pick up plenty of smaller details, but I think broader subheadings are both easier to understand and navigate, and can help keep the array at a manageable length. For main characters and topics, which are going to have a lot of subheadings anyway, indexing less granular may be the difference between forty subheadings versus sixty or eighty, for example. Forty subheadings is still a lot, while still being easier to scan.<span class="Apple-converted-space"> </span></li>
<li>As I mentioned, broader subheadings can also be easier to navigate. This is because they encompass more and clearly express the larger context. Say a person is involved in constructing the National Research Experimental (NRX) reactor, is quoted reflecting on the reactor, and is also present for the reactor’s meltdown. A more granular approach would be to have separate subheadings for each of those three elements, which are arguably distinct. But in a large array, those three subheadings may sort apart from each other and a reader may not see all of them. Three distinct subheadings also take up more space (see point above). Better, I think, for a single subheading at a broader level, “National Research Experimental (NRX) reactor and,” to capture all of those discussions. The details of construction and meltdown can still be delineated as subheadings under the reactor itself.<span class="Apple-converted-space"> </span></li>
<li>While indexing at a broader level, I still want main headings and subheadings to be clear and specific. Indexing at a less granular level is not synonymous with being vague. If I go back, say when editing the index, and I don’t know what the subheading is referring to, then I can’t expect the reader to know. The meaning needs to be clear. Which reactor? Which relationship? Which concept or discovery? I try to make my first pass as clear as possible, so I have less work on my second pass and so I don’t leave myself confused when I come back around again.</li>
<li>Lastly, I want to acknowledge that I use subcontractors on this large projects. I usually ask subcontractors to pick up the names of people, and perhaps also other common elements, such as, for the Avison biography, titles of poems and other works. Having a subcontractor handle these aspects frees up my headspace to focus on the subject entries and the overall structure of the index. It also helps me to get through my own draft more quickly, because I have less to pick up. So many thanks to the indexers I work with. With so much material to get through, I find it can make a noticeable difference.</li>
</ul>
<p>In one sense, indexing a large book is no different from indexing any other book. I still pick up the same types of entries and my process doesn’t change too much. On the other hand, everything that makes indexing a regular monograph difficult is magnified simply because there is more of it. There are more details, more entries, more subheadings, more cross-references. I find writing the index requires a bit more planning, more notes, and more patience. Because the big picture is so big, it can be difficult to focus on, and so I need to make an even more conscious effort to keep referring back to what the book is about.</p>
<p>The big picture—the story that is being told—is the underlying aboutness, which needs to be visible in the index. I don’t want to get lost while indexing, and I don’t want the reader to be lost either. I need to slow down, think through my decisions, make sure I am seeing as clearer as I can in that moment, so that the reader can hopefully see through me.</p>
]]></content:encoded>
					
					<wfw:commentRss>https://stephenullstrom.com/indexing-big-books/feed/</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
		<post-id xmlns="com-wordpress:feed-additions:1">1899</post-id>	</item>
		<item>
		<title>Q&#038;A: Biggest Bottlenecks Starting as an Indexer?</title>
		<link>https://stephenullstrom.com/qa-biggest-bottlenecks-starting-as-an-indexer/</link>
					<comments>https://stephenullstrom.com/qa-biggest-bottlenecks-starting-as-an-indexer/#respond</comments>
		
		<dc:creator><![CDATA[Stephen]]></dc:creator>
		<pubDate>Tue, 30 Dec 2025 20:00:20 +0000</pubDate>
				<category><![CDATA[Clients]]></category>
		<category><![CDATA[Communication]]></category>
		<category><![CDATA[Freelancing]]></category>
		<category><![CDATA[Project Management]]></category>
		<category><![CDATA[Q&A]]></category>
		<category><![CDATA[book indexing]]></category>
		<category><![CDATA[clients]]></category>
		<category><![CDATA[communication]]></category>
		<category><![CDATA[freelancing]]></category>
		<category><![CDATA[indexers]]></category>
		<category><![CDATA[indexing]]></category>
		<category><![CDATA[project management]]></category>
		<category><![CDATA[time]]></category>
		<guid isPermaLink="false">https://stephenullstrom.com/?p=1847</guid>

					<description><![CDATA[It is once again the last Tuesday of the month. Today’s question seems appropriate in anticipation of the New Year, as it is about beginning a freelance indexing career. The question is: I’m looking to get into the business of freelance indexing, and I am wondering if the primarily bottleneck to taking on new jobs&#8230;&#160;<a href="https://stephenullstrom.com/qa-biggest-bottlenecks-starting-as-an-indexer/" rel="bookmark">Read More &#187;<span class="screen-reader-text">Q&#038;A: Biggest Bottlenecks Starting as an Indexer?</span></a>]]></description>
										<content:encoded><![CDATA[<p>It is once again the last Tuesday of the month. Today’s question seems appropriate in anticipation of the New Year, as it is about beginning a freelance indexing career. The question is:</p>
<blockquote><p>I’m looking to get into the business of freelance indexing, and I am wondering if the primarily bottleneck to taking on new jobs is finding them or simply having the time to even manage more and more clients every month?</p></blockquote>
<p>Thank you for the question. There are a couple of things to unpack here, starting with what makes starting a freelance business so difficult.</p>
<p>One factor, definitely, as noted, is finding work. A freelance business isn’t going anywhere without clients or projects. So when starting, one of the first tasks is to market. Marketing can be as simple as asking family, friends, and acquaintances for referrals. Marketing can also be more involved, such as researching and contacting publishers that you’d like to work with. However you decide to go about marketing, yes, finding clients and projects is an important bottleneck to break through while developing a freelance indexing business.</p>
<p>Another important bottleneck is acquiring and building indexing skills. In addition to landing projects, you want to make sure that you are doing a good job. This is important for building your reputation and for encouraging repeat clients and referrals. Long term, filling your schedule is going to be much easier with referrals and repeat clients, as opposed to constantly needing to find new clients because past clients don’t want to return. So to avoid client churn, focus on delivering excellent work. (And, on a related note, be someone who is easy to work with.)</p>
<p>If just starting out, building indexing skills can feel like the classic chicken and egg dilemma. Should you focus on developing skills first and then look for work? Or can you go ahead and look for work, knowing that your skills are still a work in progress? I think you can go ahead and start looking for work, so long as you know more than the client. But remain open to feedback and be intentional about continuing to learn. Treat each project as an opportunity to practice. It may take time for your skills to improve, and you may lose some clients along the way if mistakes are made, but the important thing is to be aware of those mistakes and to keep trying to do better next time. After fourteen years of indexing, I am still on the lookout for ways to improve. Over time, as your indexes get better, repeat work and referrals should come.</p>
<p>The last point I want to explore is the question of time and client management. With the question phrased as “having the time to even manage more and more clients every month?” I wonder how many clients or projects you anticipate each month. For myself, I usually index 4 to 6 books per month. I am also in contact with clients about potential upcoming projects, whether negotiating details or checking in to see if proofs are on schedule. Many of these projects are for repeat clients, which usually means less management on my part because we have a history and certain details are already settled. So for me, at least, client management usually does not require a lot of time.</p>
<p>If anyone requires a lot of time, it is usually new clients, especially authors who may not know much about indexing or publishing. These can require additional work educating them about the process or explaining what I need to do my part, though I also use boilerplate language that I can customize, which helps to cut down on the time needed.<span class="Apple-converted-space"> </span></p>
<p>As more work comes in, you will need to figure how how much work you can reasonably accommodate. More work may also prompt you to figure out how to streamline your process so that you can index more quickly (I still think about how to index more efficiently). More indexing work can also mean less time to market. This is where repeat work and referrals come in handy because once those relationships and systems are in place, they often don’t require much maintenance. But if you are having trouble retaining clients, or if you want to expand or shift clients, perhaps to indexing a different type of book or to higher paying clients, then that will require a new marketing effort, which can be difficult to find time for.</p>
<p>For now, though, when starting out, I think the main bottlenecks are finding those first few jobs and building your indexing skills. Gaining experience is tough, but if you keep at it, your efforts should begin to snowball. Focus on delivering excellent work and service, and clients should return or pass your name along. Once that happens, finding work should be easier, your schedule will begin to fill up, and you are moving past being a brand new freelancer.</p>
]]></content:encoded>
					
					<wfw:commentRss>https://stephenullstrom.com/qa-biggest-bottlenecks-starting-as-an-indexer/feed/</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
		<post-id xmlns="com-wordpress:feed-additions:1">1847</post-id>	</item>
		<item>
		<title>Confessions from a Tight Schedule</title>
		<link>https://stephenullstrom.com/confessions-from-a-tight-schedule/</link>
					<comments>https://stephenullstrom.com/confessions-from-a-tight-schedule/#respond</comments>
		
		<dc:creator><![CDATA[Stephen]]></dc:creator>
		<pubDate>Tue, 05 Jun 2018 03:58:18 +0000</pubDate>
				<category><![CDATA[Indexing Conference]]></category>
		<category><![CDATA[Project Management]]></category>
		<category><![CDATA[project management]]></category>
		<category><![CDATA[time]]></category>
		<guid isPermaLink="false">https://stephenullstrom.com/?p=633</guid>

					<description><![CDATA[I leave Wednesday morning for the Indexing Society of Canada’s annual conference, held this year in Winnipeg. Departure is now less than forty-eight hours away. This last week I have been counting down the projects I need to finish before I leave. My goal is to finish the last index on Tuesday, so I can&#8230;&#160;<a href="https://stephenullstrom.com/confessions-from-a-tight-schedule/" rel="bookmark">Read More &#187;<span class="screen-reader-text">Confessions from a Tight Schedule</span></a>]]></description>
										<content:encoded><![CDATA[<p>I leave Wednesday morning for the Indexing Society of Canada’s annual conference, held this year in Winnipeg. Departure is now less than forty-eight hours away. This last week I have been counting down the projects I need to finish before I leave. My goal is to finish the last index on Tuesday, so I can enjoy the conference without a deadline hanging over my head. So far I seem to be on track, fingers crossed. I have a bad habit of keeping a tight schedule right until it is time to walk out the door. More often than not I end up finishing the index on the airplane. I am trying to avoid that this trip. It is not worth the stress.</p>
<p>Unfortunately, time has still been pretty tight this last week, and I chose not to draft<span class="Apple-converted-space">&nbsp; </span>a longer blog post this weekend in order to index. My apologies. Writing is one of my favourite activities, and I have enjoyed blogging these last couple of months. Weeks like these remind me, though, that I can’t always do everything. I recently read Jon Acuff’s book, <i>Finish. </i>He makes the point that sometimes in order to finish one task or goal, you have to decide that you are going to suck, at least temporarily, at something else. I think there is some wisdom in that, as much as I also chafe at having to prioritize, say no, and not follow through this week on writing for this blog.</p>
<p>So, a short blog post instead. I thought I owed you an explanation. I am sorry that I don’t have anything more substantial for you this week. I look forward to writing for you again next week.<span class="Apple-converted-space">&nbsp;</span></p>
<p>If you are going to be in Winnipeg&#8211;see you there! It looks to be a great <a href="https://indexers.ca/wp-content/uploads/2018/04/Conference-Program.pdf">line-up</a>, as well as excellent colleagues, as always. This will be my fifth indexing conference. It is definitely a highlight in the indexing calendar.</p>
]]></content:encoded>
					
					<wfw:commentRss>https://stephenullstrom.com/confessions-from-a-tight-schedule/feed/</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
		<post-id xmlns="com-wordpress:feed-additions:1">633</post-id>	</item>
		<item>
		<title>How to Marinate an Index and Other Time Factors</title>
		<link>https://stephenullstrom.com/how-to-marinate-an-index-and-other-time-factors/</link>
					<comments>https://stephenullstrom.com/how-to-marinate-an-index-and-other-time-factors/#comments</comments>
		
		<dc:creator><![CDATA[Stephen]]></dc:creator>
		<pubDate>Tue, 29 May 2018 03:04:19 +0000</pubDate>
				<category><![CDATA[Indexing]]></category>
		<category><![CDATA[Project Management]]></category>
		<category><![CDATA[Work Process]]></category>
		<category><![CDATA[indexing]]></category>
		<category><![CDATA[project management]]></category>
		<category><![CDATA[time]]></category>
		<category><![CDATA[work process]]></category>
		<guid isPermaLink="false">https://stephenullstrom.com/?p=628</guid>

					<description><![CDATA[“How long does it take to index a book, anyway?” This is one of the most common questions I am asked by non-indexers. It is a fair question. What is this alchemy of words and numbers that I do from which an index is created? Do I actually have to read the whole book? This&#8230;&#160;<a href="https://stephenullstrom.com/how-to-marinate-an-index-and-other-time-factors/" rel="bookmark">Read More &#187;<span class="screen-reader-text">How to Marinate an Index and Other Time Factors</span></a>]]></description>
										<content:encoded><![CDATA[<p><img data-recalc-dims="1" fetchpriority="high" decoding="async" class="aligncenter size-large wp-image-629" src="https://i0.wp.com/stephenullstrom.com/wp-content/uploads/2018/05/pexels-photo-280248.jpeg?resize=900%2C599&#038;ssl=1" alt="" width="900" height="599" srcset="https://i0.wp.com/stephenullstrom.com/wp-content/uploads/2018/05/pexels-photo-280248.jpeg?resize=1024%2C681&amp;ssl=1 1024w, https://i0.wp.com/stephenullstrom.com/wp-content/uploads/2018/05/pexels-photo-280248.jpeg?resize=300%2C199&amp;ssl=1 300w, https://i0.wp.com/stephenullstrom.com/wp-content/uploads/2018/05/pexels-photo-280248.jpeg?resize=768%2C510&amp;ssl=1 768w, https://i0.wp.com/stephenullstrom.com/wp-content/uploads/2018/05/pexels-photo-280248.jpeg?w=1920&amp;ssl=1 1920w" sizes="(max-width: 900px) 100vw, 900px" /></p>
<p>“How long does it take to index a book, anyway?”</p>
<p>This is one of the most common questions I am asked by non-indexers. It is a fair question. What is this alchemy of words and numbers that I do from which an index is created? Do I actually have to read the whole book?</p>
<p>This is also an important question for editors and authors who are looking to hire an indexer. How much time does the production schedule need to allow for indexing? If a rush job is required, how rushed is reasonable?</p>
<p>To answer this question, I often say that I can complete most indexes in fifteen to twenty-five hours. These are hours spent at the computer, actively working on the index. This is true enough, in that I time myself and these are the numbers I get. But it is still a simplistic answer. A better answer is, if I have no other projects on the go, I can complete an index for a 200 page book in three days. Three long days, depending on the book’s content, but still, three days. A week is more comfortable for me, for most books. I currently index, on average, 4-5 books per month. &nbsp;</p>
<p>Most of my clients, when they send me a project, give me two to four weeks to complete the index (different clients have different schedules). Occasionally I am asked to complete an index in less time, which I might be able to do, but I still prefer at least two weeks. Why is this? Does this not contradict what I wrote above about completing an index in three days? Even three days is a somewhat simplistic answer. There are a number of factors that affect how long it takes to write an index.&nbsp;</p>
<p><strong>Length and Complexity</strong></p>
<p>Let’s start with the easiest factors. A long book will usually take longer to index than a short book. A more complex book—as in complexity in structure, argument, or subject matter—will also usually take longer to index than a simple book. This is usually the different between a book intended for a general audience and a book intended for a specialist or scholarly audience. If you are an author or editor, think about the audience for your book and how it is written, as well as the page or word count. That should give you an idea for how long it will take to write the index.</p>
<p><strong>Overlapping Projects and Deadlines</strong></p>
<p>Some indexers prefer to work on only one project at a time. I see value in that. It is easier on the mind to not have to switch back and forth between projects. For that reason I try not to work on more than two indexes at a time, though I am currently working on three. When I edit an index, I also tend to double down and not work on anything else until I am done, in order to maintain focus and to keep the big picture of the index in my mind.&nbsp;</p>
<p>But still, I often do work on more than one index at a time. I also usually have one or more projects waiting on my desktop for me to start. This means what while I may have three weeks to complete an index, I am not actively working on that index everyday for those three weeks. I am sorry if this bursts your conception of how I work. Please know, however, that sometime in those three weeks I will write the best index for you that I can. &nbsp;</p>
<p>Why do I work like this, with multiple overlapping projects? The main reason is that publishing schedules often change. When I book a project, I mark those dates on my calendar and I try to space projects in a reasonable way. I also believe that my clients are being sincere about the dates they give me. But, dates change. I may learn about changes a few weeks or a month in advance, or it might just be a few days. I have decided that in order to maintain a full schedule, so that a change of dates does not leave a big hole, it is worthwhile to have overlapping projects. Having two or more weeks to complete an index, while technically more time than I usually need, does allow me to work on more than one project at a time, as well as provides a cushion when schedules slip.&nbsp;</p>
<p><strong>Time to Think</strong></p>
<p>This, in my opinion, is the most important factor when thinking about the time it takes to write an index. If I am indexing a short book that will take, say, eight hours, I could conceivably write the index in one day. But I would never want to do that. Why? Because that kind of compressed work does not give me time to think.</p>
<p>What do I mean by this? Surely I am thinking all throughout the indexing process. There is reading the text and understanding what it means. There is thinking at the micro level, about what main headings and subheadings to use, and how to word them. There is thinking at the macro level, about the index structure. Then there is the final edit, which is a different sort of thinking from reading the book and creating the initial entries. In order to edit with a freshed mind, I prefer to start editing the day after I finish reading the book. So, yes, a lot of thinking goes into the index.&nbsp;</p>
<p>By time to think, I also mean time away from the index, time that is not captured in those eight hours. These are insights that come to me when I am at the gym, washing the dishes, or driving. Sometimes if I am stuck I will simply go for a walk, hoping that the break and the change in activity will stimulate my thinking. I find that these moments away from the index, when I give my subconscious a chance to hum along while I do something else, are crucial to writing the index. In a way, the index needs time to marinate. The index will be better for spacing the work out over a few days.</p>
<p><strong>Time to Rest</strong></p>
<p>Related to time to think is time to rest. This is both for within a project and between projects. Reading sixty or a hundred pages per day, and created index entries, is a lot of information to process. My mind often feels like mush at the end of the day, and I need to take time to rest so that I can do it again the next day. The same is true between projects, especially as I prefer, as I mentioned, to double down on editing to keep the big picture in my mind. This can make for some long days editing. Depending on how I am feeling, I might take the next day off, or at least work fewer hours, to give my mind a chance to recover.</p>
<p><strong>Rush Jobs</strong></p>
<p>I mentioned rush jobs at the beginning of this post and how they fit in. When a client asks for a rush job, it usually means that I am being asked at the last minute, and the index is due in a week or less. Given that I am already often working on a couple of indexes, I usually turn down rush jobs. If you are lucky, another project has slipped and I have an unexpected hole in my schedule, but that is usually the exception. The other exception is if I really want to work on the project, for whatever reason, or if I am doing it as a favour to the client, at which point I am probably working evenings and the weekend to fit it in.</p>
<p>Figuring out the time it takes to write an index is complicated. Being a freelancer and working with multiple clients means a fluid schedule. There are the deadlines, and then there is how I structure my days and weeks to actually meet those deadlines. If you are an author or editor, hopefully this blog post will give you a better understanding of what you are helping to set in motion when you say, please complete this index in two weeks.&nbsp; If you are an indexer, what factors are at play for you?</p>
]]></content:encoded>
					
					<wfw:commentRss>https://stephenullstrom.com/how-to-marinate-an-index-and-other-time-factors/feed/</wfw:commentRss>
			<slash:comments>1</slash:comments>
		
		
		<post-id xmlns="com-wordpress:feed-additions:1">628</post-id>	</item>
	</channel>
</rss>
