<?xml version="1.0"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
		<id>http://www.conrunner.net/wiki/index.php?action=history&amp;feed=atom&amp;title=Line_Management</id>
		<title>Line Management - Revision history</title>
		<link rel="self" type="application/atom+xml" href="http://www.conrunner.net/wiki/index.php?action=history&amp;feed=atom&amp;title=Line_Management"/>
		<link rel="alternate" type="text/html" href="http://www.conrunner.net/wiki/index.php?title=Line_Management&amp;action=history"/>
		<updated>2026-04-12T11:07:21Z</updated>
		<subtitle>Revision history for this page on the wiki</subtitle>
		<generator>MediaWiki 1.24.1</generator>

	<entry>
		<id>http://www.conrunner.net/wiki/index.php?title=Line_Management&amp;diff=17335&amp;oldid=prev</id>
		<title>John Bray: Created page with &quot;Lines, or queues, may be predictable given your site, or spring out of no-where. Common bottlenecks are registration, signings and programme handover.  Discuss with th...&quot;</title>
		<link rel="alternate" type="text/html" href="http://www.conrunner.net/wiki/index.php?title=Line_Management&amp;diff=17335&amp;oldid=prev"/>
				<updated>2021-12-28T06:56:49Z</updated>
		
		<summary type="html">&lt;p&gt;Created page with &amp;quot;Lines, or queues, may be predictable given your site, or spring out of no-where. Common bottlenecks are &lt;a href=&quot;/wiki/index.php?title=Registration&quot; title=&quot;Registration&quot;&gt;registration&lt;/a&gt;, &lt;a href=&quot;/wiki/index.php?title=Signings&quot; title=&quot;Signings&quot;&gt;signings&lt;/a&gt; and programme handover.  Discuss with th...&amp;quot;&lt;/p&gt;
&lt;p&gt;&lt;b&gt;New page&lt;/b&gt;&lt;/p&gt;&lt;div&gt;Lines, or queues, may be predictable given your site, or spring out of no-where. Common bottlenecks are [[registration]], [[signings]] and programme handover.&lt;br /&gt;
&lt;br /&gt;
Discuss with the site, as they will have seen most problems before. Agree a plan that fits with fire safety rules.&lt;br /&gt;
&lt;br /&gt;
White tape on the ground looks clear until people actually arrive and stand on it.&lt;br /&gt;
&lt;br /&gt;
Snaking queues feel better than straight ones, as the tail can see what&amp;#039;s happening at the head.&lt;br /&gt;
&lt;br /&gt;
Provide wide open lanes for others to pass. Not only is a mass of people triggering for some people, its very hard to negotiate from the lower sightline of a wheelchair.&lt;br /&gt;
&lt;br /&gt;
Provide queue wranglers with hi-vis jackets.&lt;br /&gt;
&lt;br /&gt;
If multiple queues, make it very clear what they are all for. Assign a staff member to the head of each line, produce a placard with the queue name that can be passed back as new people arrive.&lt;br /&gt;
&lt;br /&gt;
If the queue is slow-moving, give time estimates from each point. If the queue is waiting for a room to open, issue reminders as to when that will happen. Keep walking the queue to update people, and allow them to vent.&lt;br /&gt;
&lt;br /&gt;
If queue members need to do something, walk the queue checking they have everything ready, forms complete, id etc.&lt;br /&gt;
&lt;br /&gt;
Escort people with time pressures that affect the con, like programme participants on shortly to jump the queue.&lt;br /&gt;
&lt;br /&gt;
Queues are usually good natured, but the mood can turn if they feel bullied, or are missing out on something. Getting queue members to chat makes the wait seem shorter.&lt;br /&gt;
&lt;br /&gt;
Strolling players entertain the queue with their bagpipes may start to grate.&lt;br /&gt;
&lt;br /&gt;
Have a policy on those unable to stand for long periods. Do they queue jump, have seating, get a token allowing them to come back when its quieter but with the same precedence.&lt;/div&gt;</summary>
		<author><name>John Bray</name></author>	</entry>

	</feed>