Skip to main content
GullySystem
Real estate and construction

Technician Scheduling for Waterproofing contractors

Assign service work to suitable available technicians.

Field Service

Does this function belong in your operation?

Use when your business dispatches technicians or field-service teams.

A visit is booked, changed or escalated.

Applicator gangs are placed on terraces, basements and tanks according to weather and curing time. A wet forecast moves outdoor jobs indoors. Supervisors see which gang waits on which coat.

Bring the records the workflow depends on.

  • Jobs and locations
  • Technician availability
  • Skill and scheduling rules

Outputs to check

  • Assigned service schedule
  • Capacity and delay exception list
  • Reassignment history

Follow the technician scheduling workflow.

Use this sequence to compare your current process with the proposed module. Agree the owner, permission and exception at each step.

  1. 1. Collect due work

    Combine accepted jobs, planned visits and authorised priorities.

  2. 2. Check suitability

    Compare requirements with technician skills and availability.

  3. 3. Assign the slot

    Record the responsible technician and planned visit details.

  4. 4. Handle changes

    Review absences, emergencies and overruns before reassigning work.

  5. 5. Reconcile progress

    Use job updates to distinguish planned, in-progress and completed visits.

Who uses the module, and who approves?

Keep responsibilities distinct even when one person holds more than one role.

Service coordinator

Builds the day, absorbs the emergency and knows who is free at three.

Technician

Reviews the assigned jobs, reports availability changes and records progress through the service process.

Supervisor

Watches what is running late and rings before the customer does. Late jobs show first.

Owner

Reviews completed jobs, delays and unfilled assignments before changing field capacity.

Decide how exceptions are handled.

These business rules belong in configuration and testing. A normal transaction alone does not demonstrate that the workflow is ready.

Emergency job arrives

Record the priority decision and review work displaced by reassignment.

Technician absent

Reassign open jobs and notify the responsible coordinator.

Visit overruns

Update expected availability before promising the next appointment.

Can this work independently?

Scheduling needs jobs, technician availability and any required skills. It can use entered calendars, but attendance and job-card updates keep capacity current. Dispatch, travel navigation and proof of work are separate capabilities; assigning a job does not confirm arrival or completion.

Systems and records it connects with

  • Job cards: Service findings, approved work, parts and completion records.
  • AMC contracts: Contract coverage, dates and planned service obligations.
  • Service reports: Approved work evidence and unresolved service findings.
  • Attendance: Approved shift attendance, absence and correction records.

Configure, test and introduce the workflow.

  • Describe a typical day and area split. A note shows how jobs will be grouped.
  • Provide the skills, clearances and areas of each technician. A worked example of a day is shown. Try it. A small group uses it for a chosen week. Their feedback returns as changes.
  • Coordinator, supervisors and technicians see their own screens. Phone guides in your language follow. All jobs are assigned through the system. After the opening month a review reads the timing.

Check the result before rollout.

Apply these checks to a sample from the agreed workflow, then repeat with an exception. Keep the expected result beside the test record.

  • Conflicting assignments are visible.
  • Unavailable technicians are excluded.
  • Changes remain linked to the job.
Waterproofing contractors

How the business operates.

Nobody judges waterproofing on the day. They judge it in the rain. Your warranty record needs the material applied, covered area and application date.

Leak inspection report

Record photos, moisture spots, the area measured and the likely source on a phone, standing on the terrace. The report is done on site.

Treatment quote by system

Quote by area and treatment type, with surface preparation, number of coats and the warranty period listed.

See the full industry workflow, reports and implementation plan →

The records that hold the operation together.

  • Enquiries and leak complaints. Log enquiries from clients, builders and referrers, with the address, the type of leak and the inspection visit assigned. A tender request from a builder keeps its own due date.
  • Site inspection records. Record measurements, surface condition, damp patches, cracks, expansion joints and photographs for each area before anything is quoted, so the supervisor’s notes travel with the estimate to the office.
  • Quotations by area and system. Price terrace, bathroom, basement, sump and tank work from measured square feet and the treatment system chosen for each area, whether membrane, slurry, injection grout or crystalline coating.
  • Treatment stage records. Log hacking, surface preparation, primer, coats, mesh and protection screed as each stage is finished, with the date and the crew, so a skipped stage shows.

Operational bottlenecks to check

What was applied cannot be proved

There is no record of the coats, the client says the leak came from your work, and nothing shows the ponding test ever happened.

Re-visits are free and endless

Every wet season brings calls from jobs finished years ago, and nobody checks whether the leak is even in the area you treated. The crew goes out anyway.

How work flows across this business

This module sits within a wider operating process. Use the sequence to identify the other teams and records affected by a change.

  1. 1. Enquiry

    A leak complaint or a builder’s tender request is logged with the address, the area affected and who referred it. An inspection visit is booked for a supervisor, who carries a moisture meter and a tape.

  2. 2. Inspection

    The supervisor records measurements, the surface, cracks, damp patches, expansion joints and any earlier treatment, with photographs for each area, so the quotation starts from facts and not from a guess.

  3. 3. Quotation

    The estimator picks the treatment system for each area, such as polyurethane membrane, cementitious slurry or crystalline coating, and prices it from the measured square feet. The client receives the quotation and the proposed warranty terms.

  4. 4. Treatment

    Crew are assigned to the job and material is issued from the store. Each stage is logged as it is finished, from hacking and surface preparation to the final coat and protection screed.

  5. 5. Test and handover

    The ponding test is recorded with start and end times and the result. The client signs the handover, and the warranty register opens for that area.

  6. 6. After the job

    Stage bills and retention are followed up. Leak callbacks within the warranty are logged against the original treatment, and warranty end dates raise a reminder for the office to call the client.

Industry reports to connect with

  • Enquiries by source and quotations converted
  • Jobs in progress by stage and crew
  • Material issued against quoted use, by site
  • Warranties ending soon, by client and area

Questions before implementation.

When should waterproofing contractors consider technician scheduling?

Use when your business dispatches technicians or field-service teams. A visit is booked, changed or escalated.

What should we bring to the requirements discussion?

Bring anonymised examples of Jobs and locations; Technician availability; Skill and scheduling rules. Show who creates, checks and changes each record. Use only records from an activity that meets the suitability conditions above.

Does this replace our existing business software?

The starting point is your current system and the gap you need to close. Assign service work to suitable available technicians. Configuration, a connected module or a custom build are evaluated against that gap before a replacement is proposed.

What is outside this module?

Your authorised team verifies required qualifications. Technicians and coordinators update actual travel, arrival and completion status.

How are scope, price and rollout decided?

The proposal follows a review of your records, user roles, branches and existing software. Data migration, connections, training and support are scoped separately where needed. Conflicting assignments are visible. Use this check when reviewing the first working version.

Related functions for waterproofing contractors.

    Talk to us

    Discuss technician scheduling for your business.

    Tell us which workflow needs attention and which systems your team uses. The next step is a requirements discussion and a written scope.

    What happens after you share your requirements

    1. We review your brief and the systems you already use.
    2. We clarify the workflow, missing information and the work to consider first.
    3. The proposed scope sets out the deliverables, responsibilities and dependencies.
    4. Review the scope and commercial terms before deciding whether to proceed.

    Start with your requirements

    Describe your current process, the people involved and the change you need. Start with the details you know; we can clarify the rest together.

    Share your requirements