Keep a project team online across short site deployments
Plan connectivity before the crew leaves for site. Check what work needs a connection, which devices the team will use, what coverage they can expect and who can help if access fails.
| Before arrival | During work | Closeout |
|---|---|---|
| Confirm roster and tasks | Record top-ups and issues | Recover assets and stop future credit |
By Freepaid · Published
Write a connectivity plan for the site
Seven people on a ten-day job with R50 each need R350 in face value at that allowance. Check the amount against the work plan and product terms. Confirm that staff or device custodians can receive the credit at the site. Decide whether they’ll use company devices, their own phones or a shared hotspot and name the person responsible for each shared device. Keep project records separate from personal content.
Record the crew, dates, approved limit, product and support contact under the project code. Set the date when temporary access and top-ups stop, and name the person who will close the job. Give the team an offline procedure for work that can continue without coverage. Make sure they know how to report a delayed order, who can approve an urgent exception and who else will reconcile it later.
Recalculate when the deployment extends
If the job runs a week longer, recalculate the requirement and get an extension approved against the same project code. Put the revised end date on the roster and share the approval with finance before the next scheduled allocation.
Close the deployment deliberately
The closeout owner should collect equipment, remove temporary access and cancel future allocations. Match the confirmed spend to the project code and follow up on open orders using their original references. Record outages and what the crew did instead so the next site team can plan around recurring problems.