Nobody is sure which version is current
Copies, filters and manual edits make it difficult to know whether the coordinator, project manager and field technician are looking at the same plan.
Geotechnical operations guide
How to replace a geotechnical job scheduling spreadsheet.
A practical migration path for geotechnical teams that have outgrown a shared spreadsheet, messages and separate calendars—but cannot disrupt the field week to change systems.
Built for a staged rollout
Project and location context
Connects to digital dockets
When the spreadsheet has become the scheduling bottleneck Excel can be a sensible starting point. The problem begins when the schedule stops being a reliable operational record for the office and field team.
Changes live in messages instead of the schedule
Reassignments, cancellations and site instructions arrive through calls or group chats, leaving the shared spreadsheet behind the real field week.
A calendar entry does not carry enough job context
Technicians still need to chase the project number, site address, contact, location, work scope or expected field record before attending.
Unassigned work and capacity gaps are hard to see
The team can appear busy while individual jobs remain unallocated, or the same person is booked beyond the hours actually available.
Field completion creates another manual handoff
Once the visit is finished, the office must reconcile the schedule with notes, photos, hours, dockets, reporting status and invoice readiness.
[01] Migration plan
/ Map → Pilot → Connect
Replace the spreadsheet in stages—not in one risky cutover. The safest migration preserves the useful parts of the current process, fixes the ownership problem first and connects downstream work after the schedule is trusted.
Step 1 · Map the current field week
Document what the spreadsheet is really doing.
List who creates bookings, who changes them, which project and site details are required, how unassigned work is identified, and which messages or calendars carry information the spreadsheet cannot hold.
- Identify the actual schedule owner
- List required project and location fields
- Record every manual handoff after field completion
Step 2 · Pilot one team or job type
Move project-linked bookings into one shared schedule.
Start with a coordinator and a small group of field staff. Create jobs against the correct project and location, allocate the work, and use the shared schedule for changes rather than maintaining a parallel operational copy.
- Begin with a contained field team
- Keep timing, project and location together
- Review unassigned work before each field day
Step 3 · Connect field completion
Attach the field record to the job that was scheduled.
Once the schedule is trusted, connect the digital docket so work items, notes, photos, time, travel and client sign-off return against the correct job, with reporting and invoicing states visible to the office.
- Capture the record while the job is current
- Avoid rekeying project and site identity
- Make reporting and billing handoffs visible
Information to preserve before switching systems Do not migrate every historical cell simply because it exists. Preserve the operational information required to run current work and find important history.
- Active project numbers, names, clients and site addresses
- Current and upcoming field bookings
- Assigned field staff and unassigned work
- Job types, priorities and expected duration
- Site contacts and mapped field locations
- Open, cancelled and completed job states
- The field record expected after each job type
- Reporting, billing and invoice handoff requirements
- A read-only archive of historical spreadsheets
Geotechnical scheduling migration questions
When should a geotechnical business replace its scheduling spreadsheet?
Replace it when the spreadsheet is no longer a dependable shared record: changes are communicated elsewhere, project or location details are missing, unassigned work is difficult to see, or field completion requires repeated reconciliation. A small stable team with a simple schedule may not need to change yet.
Should we migrate every historical booking?
Usually not. Prioritise active projects, upcoming work and the history needed for current delivery or client queries. Older spreadsheets can remain in a controlled read-only archive unless a clear operational or compliance reason requires migration.
How do we avoid running two competing schedules?
Use a short, defined pilot with one named schedule owner. Set a cutover date for the pilot group, make changes only in the new schedule, and retain the old spreadsheet as a reference rather than an editable second source of truth.
What should a scheduled geotechnical job contain?
At minimum: the project, job type, site or field location, scheduled time, assigned people, priority and the information the field team needs before attendance. The exact fields depend on your services and dispatch process.
Can we implement scheduling before digital dockets or reporting?
Yes. Scheduling can be the first workflow. Once the team trusts it, digital dockets and reporting can be connected so downstream work retains the same project and job context.
How long should a pilot run?
Run it long enough to cover ordinary work plus at least a few changes, cancellations or urgent bookings. The objective is to test ownership and handoffs, not merely confirm that a booking can be created.
Use next week’s field schedule
Map your spreadsheet into a workable pilot.
Bring the current columns, calendars and message handoffs. We will show how the same field week can be organised in GeoCRM without changing every process at once.