Access route intake

Intake is the least glamorous and most valuable hour of an engagement. A remote access request that is written down properly — people, sites, systems, hours, evidence — costs an afternoon. The same request left verbal costs a quarter of confused permissions.

What intake captures

We interview the people who will live with the arrangement: an operations lead, whoever owns the systems, and one person from governance. We ask the same questions of every request, which is what makes requests comparable across a year.

• People. Named roles, employing entity, manager, start and end dates, and the authority that approves them.
• Sites. Where the person sits, whether the location is trusted, and whether the connection is fixed or travels.
• Systems. Each service or host that must be reached, classified by the data it holds and by the harm that would follow a mistake.
• Hours. When access is expected, what happens outside those hours, and how an exception is raised and recorded.
• Evidence. What the client must be able to show later — an approval, a log, a review note — and for how long.

The written brief

Within a working week we return a brief of two to four pages. It states the request in one paragraph, lists the decisions already taken, marks the questions still open, and proposes a route: named groups, a time-boxed grant, an expiry date, a review owner. The client edits it, signs it, and only then does configuration begin. The brief becomes the first item in the engagement record and the reference point for every later review.

Why intake is worth the time

Later disputes about access are almost never disputes about technology. They are disputes about who approved what. A brief with a signature and a date settles most of them in a sentence. It also shortens delivery: engineers who know the target set configure faster and test better than engineers who are still discovering requirements while typing.

Common intake findings

Over many intakes we see the same handful of issues: grants without an end date, shared credentials nobody owns, an approval chain that exists only in one manager's memory, and a documented process that no longer matches practice. None of these are exotic. They are ordinary drift. Intake is where drift becomes visible and where a client can choose, deliberately, to keep it or correct it.

What we need from you

A list of the systems in scope, the names of one operations lead and one governance owner, your working hours and maintenance windows, and an hour with the people who do the work. If some of that is not yet clear, we will help you assemble it — that is part of the service.