<style>
/* Read one-handed, outdoors, while walking. Hence a nav that never leaves the
   screen, and body text large enough to read at arm's length in daylight. */
.sc { --ink:#1c1917; --mute:#78716c; --line:#e7e5e4; --accent:#f97316;
      --box:#fff7ed; --say:#fafaf9;
      max-width: 760px; margin: 0 auto; padding: 0 1.1rem 5rem; color: var(--ink); }

.sc-nav { position: sticky; top: 0; z-index: 50; margin: 0 -1.1rem 1.75rem;
          padding: 0 1.1rem; background: rgba(255,255,255,.96);
          backdrop-filter: saturate(180%) blur(8px);
          border-bottom: 1px solid var(--line); }
.sc-nav-inner { display: flex; gap: .4rem; overflow-x: auto; scrollbar-width: none;
                -webkit-overflow-scrolling: touch; padding: .6rem 0; }
.sc-nav-inner::-webkit-scrollbar { display: none; }
.sc-nav a { flex: 0 0 auto; padding: .45rem .7rem; border-radius: 999px;
            font-size: .82rem; font-weight: 500; text-decoration: none;
            color: var(--mute); background: #f5f5f4; white-space: nowrap; }
.sc-nav a:hover, .sc-nav a:focus-visible { color: #fff; background: var(--accent); }

.sc h1 { font-size: 2rem; line-height: 1.15; margin: 1.5rem 0 .4rem; text-wrap: balance; }
.sc .sc-lead { color: var(--mute); font-size: 1.05rem; line-height: 1.65; margin: 0 0 1.5rem; }
.sc h2 { font-size: 1.3rem; margin: 2.75rem 0 .75rem; padding-top: .6rem;
         border-top: 2px solid var(--accent); scroll-margin-top: 4.25rem; }
.sc h3 { font-size: 1.02rem; margin: 1.6rem 0 .4rem; }
.sc p, .sc li { font-size: 1rem; line-height: 1.7; }
.sc ol, .sc ul { padding-left: 1.25rem; }
.sc li { margin: .3rem 0; }
.sc code { font-family: ui-monospace, SFMono-Regular, Menlo, monospace;
           font-size: .88em; background: #f5f5f4; padding: .1rem .35rem; border-radius: 4px; }

/* What you actually say out loud. */
.sc-say { background: var(--say); border-left: 3px solid var(--accent);
          padding: .85rem 1rem; margin: 1rem 0; border-radius: 0 8px 8px 0;
          font-size: .97rem; line-height: 1.6; }
.sc-say b { display: block; font-size: .7rem; letter-spacing: .07em;
            text-transform: uppercase; color: #c2410c; margin-bottom: .35rem; }
.sc-say em { color: var(--ink); font-style: italic; }

.sc-note { background: var(--box); padding: .8rem 1rem; margin: 1.1rem 0;
           border-radius: 8px; font-size: .95rem; }
.sc-note p { margin: 0; font-size: .95rem; }

.sc-sec { border: 1px solid var(--line); border-radius: 10px;
          padding: .9rem 1.05rem; margin: .9rem 0; }
.sc-sec h3 { margin: 0 0 .35rem; }
.sc-sec p { margin: 0 0 .4rem; color: #44403c; }
.sc-sec ul { margin: .3rem 0 0; }

.sc-standard { background: var(--say); border-radius: 8px; padding: .9rem 1rem .9rem 2.2rem;
               margin: .9rem 0; }
.sc-standard li { margin: .25rem 0; }
.sc-cmd { width: 100%; border-collapse: collapse; font-size: .95rem; }
.sc-cmd td { border-bottom: 1px solid var(--line); padding: .6rem .4rem; vertical-align: top; }
.sc-cmd td:first-child { white-space: nowrap; width: 1%;
                         font-family: ui-monospace, SFMono-Regular, Menlo, monospace; }

@media (max-width: 700px) {
  .sc h1 { font-size: 1.65rem; }
  .sc h2 { font-size: 1.15rem; margin-top: 2.25rem; }
}
</style>

<div class="sc">

<nav class="sc-nav"><div class="sc-nav-inner">
<a href="#start">Start</a>
<a href="#plan">Your plan</a>
<a href="#overview">Site overview</a>
<a href="#access">Access</a>
<a href="#locations">Locations</a>
<a href="#restrictions">Restrictions</a>
<a href="#questions">Questions</a>
<a href="#shooting">Shooting</a>
<a href="#closing">Closing</a>
<a href="#commands">Commands</a>
</div></nav>

<h1>Running a location scout</h1>

<p class="sc-lead">Talk as you go. Send photographs and videos as you take them.
Everything is dictated — you never type a report. This page is the order to do
it in and what each part needs.</p>

<h2 id="start">Start — record this first</h2>

<p>Before anything else, one message that says who and what. Everything here
ends up in the report header, so if you skip it the report has no idea what it
is about.</p>

<div class="sc-say"><b>Say something like</b>
<em>“This is Jane Smith, Northlight Locations, reachable on 07700 900 123.
Scouting for The Gallows Pole, second series. The location is the Château de
Fontainebleau, the main site on the east side.”</em></div>

<p>Five things, in any order:</p>

<ul>
<li><b>Your name</b></li>
<li><b>Your company</b>, if you're working for one</li>
<li><b>How to reach you</b> — phone or email</li>
<li><b>The production</b> — what this scout is for</li>
<li><b>The location</b> — the site, and which part of it if that matters</li>
</ul>

<div class="sc-note"><p>You don't need to say the date or the time. Those are
recorded automatically, and so is the time of every photograph — which is what
lets the report work out where the sun was.</p></div>

<h2 id="plan">Then say what you're going to do</h2>

<p>Name the sections and locations you intend to cover. This is what the check
measures you against — without it, nothing can tell you that you missed
something, only that you stopped.</p>

<p>A normal scout has these sections:</p>

<ol class="sc-standard">
<li><b>Site overview</b> — the whole place, once</li>
<li><b>Access</b> — entry, exit, vehicles, ground, moving around</li>
<li><b>Locations</b> — one section for each location you're documenting</li>
<li><b>Restrictions</b> — what you're told or see that you can't do</li>
<li><b>Questions</b> — asked, answered, or left open</li>
</ol>

<p>Say which of those you're doing, which you're skipping, and list the
locations by name.</p>

<div class="sc-say"><b>Say something like</b>
<em>“Today I'm doing the site overview, the vehicle access, then three
locations: the main courtyard, the west gardens and the orangery. I'm not doing
the interiors, they were covered on the first visit.”</em></div>

<p>Two things worth saying explicitly:</p>

<ul>
<li><b>What you're skipping and why</b> — on a second scout, most sections may
already be done. Say so, and they won't be reported as gaps.</li>
<li><b>Anything you add later</b> — <em>“there's also a service yard round the
back, I'm adding that”</em>. The plan grows; that's normal.</li>
</ul>

<h2 id="overview">Site overview</h2>

<p>The shape and character of the whole place, so someone who has never been can
picture it.</p>

<p><b>You don't have to do this in one go.</b> On a big site you can't — walking
the whole thing takes an hour, and by then you've forgotten half of it. Start
with whatever you can give at once, a map or an aerial view if there is one, and
add to it as you move.</p>

<div class="sc-say"><b>Say when something is for the overview</b>
<em>“This is for the site overview — the courtyard and the gardens connect
through this passage, it's about eighty metres.”</em></div>

<p>Say it, because otherwise a remark made while walking between two locations
gets filed under the one you just left. Connections between places, distances,
how the site hangs together — that's overview material, and it's usually noticed
in transit rather than standing still.</p>

<div class="sc-sec">
<h3>What it needs</h3>
<ul>
<li>Wide views that establish the site and how the parts relate</li>
<li>What kind of place it is, what condition it's in</li>
<li>How busy it is, and whether today is typical</li>
<li>Weather and light — overcast, hard sun, and roughly where the sun is</li>
<li>Who you're dealing with on site, and their role</li>
</ul>
</div>

<h2 id="access">Access — entry, exit and moving around</h2>

<p>Everything about getting people and equipment in, round and out.</p>

<div class="sc-sec">
<h3>What it needs</h3>
<ul>
<li>The approach road, and the last junction before the site</li>
<li>Every gate and entrance, and which are usable by vehicles</li>
<li>Where a vehicle can stop, unload, turn and park</li>
<li>Pedestrian routes in, and how far it is from parking to the locations</li>
<li>Exits, including ones only usable on foot</li>
<li>Barriers, security points, height restrictions, narrow turns</li>
<li>Ground: steps, slopes, gravel, mud, cobbles, anything a trolley hates</li>
<li>The route between the locations you're covering</li>
</ul>
<p>Film a slow walk of the main arrival route, beginning to end.</p>
</div>

<h2 id="locations">Locations</h2>

<p>Then one section per location. Say which one you're in when you start —
<em>“I'm now in the main courtyard”</em> — and everything after that is filed
there until you say otherwise.</p>

<p>A location is anything worth documenting in its own right. A courtyard is one.
So is a staircase, a side entrance or a single room. They all get the same
treatment.</p>

<div class="sc-sec">
<h3>What each location needs</h3>
<ul>
<li>What it is and how you get into it</li>
<li>Its size, and what it feels like to stand in</li>
<li>Every way in and out</li>
<li>Ground and surfaces</li>
<li>Light — where it comes from, what's in shade, how it changes</li>
<li>What's fixed and can't be moved</li>
<li>Modern things that will show on camera: signs, bins, lights, cameras, cabling</li>
<li>Whether the public comes through, and how much</li>
<li>Anything that would get in the way of filming</li>
<li>The strongest angle, and what you'd shoot from there</li>
</ul>
</div>

<div class="sc-note"><p>If you say nothing about a location beyond its name, the
check will tell you it's thin. That's the point of running it before you
leave.</p></div>

<h2 id="restrictions">Restrictions</h2>

<p>Anything you're told you can't do, or see that you can't do. Record it when
you hear it, not later.</p>

<div class="sc-say"><b>Say who told you, and when</b>
<em>“The head gardener just told me no vehicles on the gravel at all, and the
fountains can't be switched off.”</em></div>

<p>A restriction without a source is worth very little three months later, when
someone is deciding whether to build a crane on that gravel.</p>

<h2 id="questions">Questions</h2>

<p>Ask, and record the answer as you get it. If you don't get one, say so —
an unanswered question is a real result and belongs in the report.</p>

<ul>
<li>Which areas can be filmed, and which can't</li>
<li>Dates or times when the site isn't available</li>
<li>Where vehicles can stop, unload and park</li>
<li>Limits on crew size or equipment</li>
<li>Drones, lighting, generators, cranes, track</li>
<li>Rules about lawns, gravel, fountains, historic surfaces</li>
<li>Whether public areas can be closed or controlled</li>
<li>Restrictions on filming façades, artworks or details</li>
<li>Scheduled works, events or temporary structures coming up</li>
<li>Who to contact for a technical scout</li>
</ul>

<div class="sc-note"><p>If something was only agreed in conversation, say that.
It goes in the report as needing written confirmation.</p></div>

<h2 id="shooting">Shooting</h2>

<p>The same pattern in every location.</p>

<h3>Photographs</h3>

<ol>
<li>A wide shot showing the whole space</li>
<li>The same space from the opposite direction</li>
<li>From each corner or main access point</li>
<li>Every entrance, exit, gate, stair and pathway</li>
<li>Medium and close shots of anything important</li>
<li>Anything that would affect filming</li>
<li>A shot that conveys size and scale</li>
</ol>

<p>Horizontal for the main set. Vertical as extras, when the subject is tall.</p>

<div class="sc-note"><p><b>Take every photograph with the phone&rsquo;s Camera
app &mdash; never with the camera inside WhatsApp or Telegram.</b> Tap out of the
chat, shoot, then come back and send. A photograph taken inside a chat app
arrives at a third of the resolution and with no location at all &mdash; measured
on the same phone, seconds apart: 24.5 megapixels with coordinates and a compass
bearing from the Camera app, 8.3 megapixels with neither from the in-app one.
Neither loss can be repaired afterwards, because the location was never recorded
in the first place.</p></div>

<div class="sc-note"><p><b>No Portrait mode, no filters, no heavy zoom.</b>
Portrait mode isn't the same as a vertical photo — it's the phone faking a
blurred background, and the background is exactly what these photographs exist
to show. It can't be undone.</p></div>

<h3>Video</h3>

<ul>
<li>Open on a wide, still view for about five seconds</li>
<li>Pan slowly left to right, then film the reverse</li>
<li>Walk the main route through, slowly</li>
<li>Show how this location connects to the next</li>
<li>Cover entrances, exits, stairs and changes in level</li>
</ul>

<p>Clips of 15 to 45 seconds. No rapid turns, no digital zoom. Don't talk while
walking — stop, say which area you're in, keep it short.</p>

<h2 id="closing">Before you leave</h2>

<p>Run <code>/check</code>. It tells you what's still open and shows you where
every note has been filed. Both are only fixable while you're still on site.</p>

<p>If something is filed wrongly, say so — <em>“note 105 is the west
courtyard”</em>, or a range: <em>“100 to 105 are the staircase”</em>. Then run
<code>/check</code> again to confirm it took.</p>

<p>Last, dictate the two things only you can give:</p>

<ul>
<li><b>Your overall impression</b> — is this location right, and why</li>
<li><b>Whether a technical scout is needed</b>, who should come, and what they
should look at</li>
</ul>

<h2 id="commands">Commands</h2>

<table class="sc-cmd">
<tr><td>/check</td><td>What's still open, and where everything is filed</td></tr>
<tr><td>/report</td><td>The report so far</td></tr>
<tr><td>/final</td><td>Finish this scout and start a new one</td></tr>
<tr><td>/upload</td><td>A link for sending full-resolution originals</td></tr>
<tr><td>/i</td><td>This page</td></tr>
</table>

<div class="sc-note"><p><b>Send the real files through <code>/upload</code>.</b>
Photographs sent as ordinary chat messages are recompressed by WhatsApp and
Telegram before they arrive &mdash; around 1280 or 2048 pixels, with the location
and timing data stripped out. Fine for a quick note; not the original.</p>
<p style="margin-top:.5rem"><code>/upload</code> gives you a link. Open it on the
phone, choose the photographs <b>from your library</b>, and they arrive whole:
full resolution, location, and the direction the camera was pointing. Do it at
the end of the visit, for everything you sent through chat.</p></div>

</div>
