Remote Site Readiness: 5 Powerful Installation Checks

Remote site readiness makes an internet installation easier to organise at a Kenyan farm, camp or project office. A clear location, agreed access, suitable indoor equipment space and a named contact can prevent avoidable delays. Use this checklist to prepare the visit while leaving technical mounting and electrical decisions to qualified people.

1. Confirm remote site readiness with a location brief

Give the installer the county, nearest landmark and a reliable way to contact the person meeting the team. Explain road access and any site-entry process. Share precise access details privately with the service provider rather than in a public post.

Confirm whether there is already a Starlink kit and which components are available. Photographs of the packaged equipment may help identify what needs checking, but a photo should not be treated as proof that every component is functional.

2. Identify the work areas that need connectivity

List the office, accommodation, reception or stores that require access. Note the approximate distance between buildings and any obstacles the installer needs to assess. Separate essential work areas from places where coverage would simply be convenient.

Review the site preparation checklist and ask for a coverage assessment. A connection reaching the main building does not automatically establish coverage across the entire property.

3. Prepare access and an indoor equipment location

Confirm who can approve mounting work and which parts of the site are restricted. Keep the proposed indoor equipment area secure and accessible to authorised staff. Ask the installer to assess the mount and cable route instead of asking untrained staff to investigate elevated positions.

Tell the provider about known power interruptions and consult a qualified professional about suitable arrangements. Do not assume a particular backup device is compatible without checking the actual equipment and its requirements.

4. Coordinate transport and site contacts

Agree the visit date, arrival contact and how delays will be communicated. If you arrange separate transport, make clear which party is responsible for the equipment and journey. Services such as Dereva can be reviewed separately when considering transport needs; confirm availability and terms directly.

Keep a small checklist of the people needed for access, installation and acceptance. An installer may finish the physical work but still need an authorised account holder or staff member to complete the handover.

5. Agree the scope and acceptance checks

Ask for a written scope covering installation work, accessories, travel assumptions and any excluded areas. Compare the complete proposal using the package cost checklist. Ongoing service charges and site-specific extras should be understandable before work begins.

Choose practical tests from the intended work areas. For example, verify that staff can complete an ordinary browser task from the office and make a normal work call from the designated room. Record unresolved coverage gaps rather than describing the whole site as complete.

Keep a site record after installation

Store the quote, equipment list, support contact and handover notes together. Note where the equipment is installed and who can authorise changes. If staff rotate between project sites, this record helps the next team report issues accurately.

For broader website research, Awasa is an additional external resource. Check its current services and availability directly; no integration or installation relationship is implied.

Frequently asked questions

Can one router serve several separate buildings? Have the layout assessed. Building materials, distances and the chosen equipment affect the local network design, so coverage should not be promised from a headcount alone.

What should I send to Spacekits? Send your location, kit status, the areas requiring access and preferred date. Review installation services and ask which details need a site visit. Remote site readiness is about making these facts clear before the team travels.

Remote site readiness worksheet

Prepare the remote site readiness worksheet around the practical facts needed for the visit. Identify the site, nearest useful landmark, current contact and intended work areas. Add the kit status and the date you hope to arrange installation. Mark estimates clearly rather than presenting uncertain distances or access conditions as confirmed facts.

Keep detailed access information in the private communication with the provider. A public article or shared community group is not the right place for gate codes, staff schedules or other sensitive site instructions. The worksheet should make coordination easier without exposing information that unrelated people do not need.

Confirm who can approve the work

Remote site readiness includes knowing who can authorise mounting, cable routing and access to the relevant buildings. A caretaker may be able to open a gate but may not have authority to approve changes to the premises. Identify those boundaries before the installation team travels.

Choose a backup contact who understands the agreed scope. If the main contact is away, the team needs a practical way to resolve ordinary questions. Do not assume that a visitor or temporary staff member can make decisions simply because they are the only person available on site.

Remote site readiness example: a farm office

A farm wants internet in the main office and occasional access in a nearby store. The initial request says that the whole farm needs coverage. A more useful remote site readiness brief identifies the two working areas and explains the tasks performed in each, while marking wider compound coverage as a separate requirement for assessment.

The site contact confirms access arrangements and describes the available indoor equipment space. The provider then assesses mounting and cable routing rather than relying on untrained staff to inspect elevated positions. Any question about electrical preparation is directed to an appropriately qualified person.

At acceptance, the office completes an ordinary work task and the store checks the activity described in the brief. If the store remains outside the working coverage area, that gap is recorded. The result should not be described as complete coverage across the property based only on a test in the office.

Remote site readiness example: a camp reception

A camp needs reception connectivity for operational work and wants to discuss guest access separately. The remote site readiness record distinguishes those uses and identifies the rooms or areas involved. This helps the provider assess the requirements instead of treating every guest space as automatically included in the initial installation.

The manager records when reception is busiest and who can test the ordinary workflow. An acceptance test should use an approved method that does not create duplicate bookings or expose guest information. Ask the application provider about suitable test procedures where necessary.

After installation, keep the support details accessible to the staff who operate reception. Seasonal or rotating employees may not have attended the original handover. The remote site readiness record should therefore lead into clear operating instructions that remain useful when staff change.

Remote site readiness example: a project office

A temporary project office may move equipment or change its layout as work progresses. Record the current intended setup and explain any planned relocation to the provider. Do not assume that an installation suitable for one position will automatically remain suitable after a move.

The remote site readiness brief should state which tasks matter most, such as document uploads or calls with the main office. Identify the person managing the service account and the person responsible for equipment custody. These responsibilities can become unclear when several organisations share a project site.

At handover, record the equipment arrangement and any agreed limitations. If the site later changes, request a review rather than allowing informal modifications to accumulate without documentation. A short current record is more useful than an old installation plan that no longer describes the premises.

Access and travel coordination

Confirm the arrival contact, site-entry process and any relevant working-hour restrictions. Give the provider an accurate description of known access constraints. If conditions change before the visit, communicate promptly so that the team can review the arrangements rather than discovering the issue on arrival.

Remote site readiness does not mean guaranteeing a journey time from a rough location description. Ask the provider to confirm the practical travel arrangements and any assumptions affecting the quote. Where separate transport is involved, make responsibility for the journey and equipment clear between the relevant parties.

Prepare for a delayed arrival

Agree how the site contact and provider will communicate if timing changes. Identify whether access depends on a particular person remaining available. A visit can fail even when the team reaches the site if the only authorised contact has left and nobody else knows the agreed scope.

The remote site readiness worksheet should include a backup communication route where appropriate. Avoid relying on a single message that may not be received promptly. Keep the process simple and confirm the arrangements directly with the provider before the travel date.

Equipment and indoor space

List the equipment already available and identify any uncertainty about missing components. Photographs may help the provider understand what needs checking, but do not treat them as proof of compatibility or condition. Ask the provider to confirm what the proposed installation requires.

For remote site readiness, identify a suitable proposed indoor area where authorised staff can access the equipment. The provider should assess the actual placement and cable route. Avoid placing equipment where routine work, visitors or stored items are likely to disturb it.

Keep power questions within qualified assessment

Tell the provider about known power interruptions and the site’s existing arrangements. Ask an appropriately qualified professional to assess electrical requirements and any proposed backup equipment. Do not improvise connections or assume that a device is suitable because it has been used with different equipment elsewhere.

Record the outcome of that assessment in the remote site readiness file where relevant to the installation scope. If preparation is needed before the visit, assign an owner and completion date. An unresolved prerequisite should remain visible rather than being assumed complete because the installation has been booked.

Remote site readiness acceptance checklist

• Confirm that the work matches the agreed site and scope.
• Check the required indoor working areas.
• Complete the ordinary tasks identified in the brief.
• Record the location and device used for each test.
• Identify any area that remains outside the tested result.
• Confirm equipment ownership and the service-account contact.
• Record support contacts and basic reporting instructions.
• Assign an owner to any remaining recommendation or task.

Use the checklist as a record of the observed result. Remote site readiness and acceptance checks do not create a universal speed or uptime guarantee. If the organisation requires a particular service commitment, discuss the current terms with the relevant provider and obtain the agreed arrangement separately.

Comparing the written quote with site requirements

Review hardware, mounting, cable work, networking accessories and travel assumptions separately. Ask which parts of the quote are final and which depend on a site assessment. Comparing only the total can hide important differences between proposals.

The remote site readiness brief should make excluded work visible. If electrical preparation, permissions or additional buildings are outside the scope, identify who will handle them. A clear exclusion with an owner is easier to manage than a requirement that every party assumes somebody else will address.

Handle changes before work proceeds

If the site requests coverage in an additional building after the quote is prepared, tell the provider and ask for the implications. Do not assume that a new requirement is included because the team is already travelling to the property. Record the agreed change and any effect on scope or scheduling.

Keep the current remote site readiness document aligned with the approved work. Remove obsolete instructions that could mislead the installation team. Where an earlier version remains useful as history, label it clearly so that it is not mistaken for the current plan.

Handover for rotating site staff

Prepare a short operating record showing the equipment location, support contact and reporting process. Keep sensitive credentials in the approved secure location rather than in an openly shared handover note. Staff should know how to obtain authorised help without being given unnecessary administrative access.

The remote site readiness record can provide context for the next staff team, including which areas were tested and which were not part of the scope. This prevents a new employee from assuming that every building was intended to receive the same service.

Record changes after installation

If equipment is moved or the work area changes, update the operational record and consult the relevant provider where needed. Unrecorded changes can make a later support report difficult to interpret. The provider needs to know whether the current arrangement still matches the installation they assessed.

Review the remote site readiness file when the site expands, closes a building or changes its main activities. The original information is a useful starting point, but the new requirements should be assessed on their own facts rather than assumed to fit the earlier setup.

Reporting a problem from a remote site

Describe the affected area, approximate time, device and failed activity. State whether other users are affected and record any visible message that staff can observe safely. Do not ask employees to climb onto a roof or open electrical components to gather troubleshooting evidence.

A remote site readiness handover should identify the person who coordinates such reports. One clear summary is often more useful than several contradictory messages from different staff. Keep the original observations and any authorised actions together so that support can understand the sequence.

Distinguish a local coverage gap from an application issue

If one room has problems while the main office works, record that difference. If general browsing works but one application fails, include that observation. These facts do not prove the cause, but they help the provider choose the next appropriate question.

Keep confidential business information out of general support screenshots. Describe the task or provide a cropped, non-sensitive message where appropriate. Ask the provider what minimum evidence is required rather than sending an entire screen containing unrelated private records.

Frequently asked questions about remote site readiness

Can we prepare everything from photographs?

Photographs can help explain the site, but mounting, access, cable routing and coverage may still require an assessment. Mark uncertain details clearly and ask which assumptions need confirmation. Remote site readiness is about providing useful facts, not replacing qualified inspection with guesswork.

Should we buy accessories before the visit?

Confirm the requirements with the provider first. The appropriate components depend on the equipment and site arrangement. Buying items based on another property’s installation may result in components that do not suit the current project.

What if only the office is ready on installation day?

Discuss the available scope with the provider and record any agreed staged approach. Do not describe untested or unfinished areas as complete. The remote site readiness record should show which work was accepted and which areas require a later assessment or visit.

Final remote site readiness review

Before confirming the visit, check the contact details, access arrangements, equipment status and intended work areas. Review the open prerequisites and confirm who is responsible for each one. A short call or written check with the provider can resolve an assumption before it becomes a problem on site.

Keep the final remote site readiness brief with the quotation and handover record. Together, they explain what the team requested, what was agreed and what was tested. That practical history helps Spacekits and the site manager coordinate future support or expansion with a clearer understanding of the existing arrangement.

Talk to Spacekits

Discuss your requirements and the next practical step. Call 0725345345 or message us on WhatsApp.