Skip to main content
GullySystem
Real estate and construction

Stock Tracking and Alerts for Waterproofing contractors

Record stock movements and flag items reaching configured levels.

Inventory Management

Does this function belong in your operation?

Use when the business holds physical stock or consumables requiring quantity control.

Goods are received, issued, transferred or counted.

Primer drums, polymer coating, membrane rolls and sealant tubes are issued to a site against its area. Leftover material comes back to the store. Shortages show before the gang reaches the roof.

Bring the records the workflow depends on.

  • Item and location list
  • Opening quantities
  • Reorder and movement rules

Outputs to check

  • Item-location balance register
  • Movement and count-adjustment history
  • Replenishment exception list

Follow the stock tracking and alerts workflow.

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

  1. 1. Set opening stock

    Approve item-location quantities and tracking rules.

  2. 2. Record movements

    Capture authorised receipts, issues, sales and transfers.

  3. 3. Compare counts

    Investigate physical differences before adjustment.

  4. 4. Review thresholds

    List shortages using the appropriate item and location level.

  5. 5. Handover replenishment

    Send requirements to purchasing or production without treating an alert as an approved order.

Who uses the module, and who approves?

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

Storekeeper

Issues material against a job, counts a rack on a slow afternoon, and answers for the difference. Every difference gets a name.

Counter staff

Checks recorded stock and location before confirming availability under the business's reservation rules.

Owner

Reads the alert list and the dead stock report, which is where the tied-up working capital sits.

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.

Count differs from record

Investigate recent movements and approve an adjustment with the reason.

Negative balance attempted

Apply the agreed hold or exception rule and expose the cause.

Goods held for inspection

Keep them distinct from stock available for issue or sale.

Can this work independently?

Stock tracking can run from entered receipts and issues, but every physical movement needs a record. Purchase, sales, production and warehouse connections provide those movements. Reorder alerts signal a threshold; purchasing still decides quantity, supplier and approval.

Systems and records it connects with

  • Purchase order management: Authorised supplier commitments and open line balances.
  • Goods receipt: Counted, accepted and rejected supplier-delivery quantities.
  • Point of sale billing: Counter sales, tender records and authorised returns.
  • Multi-outlet stock: Outlet quantities and acknowledged transfer movements.

Configure, test and introduce the workflow.

  • Show us the godown and the counters. A note lists the locations and the item groups.
  • Supply levels per item and place, or ask for suggestions from history. Balances and alerts then appear for trial. A count is taken and loaded as the opening balance. The team checks a sample against the shelf.
  • Each group practises receipts, issues and transfers. Short cards for the shelves follow. Alerts reach named people. A review once the opening season ends lists slow stock.

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.

  • Movements reconcile with location balances.
  • Count adjustments retain approval.
  • Alerts use the correct item and location threshold.
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 stock tracking and alerts?

Use when the business holds physical stock or consumables requiring quantity control. Goods are received, issued, transferred or counted.

What should we bring to the requirements discussion?

Bring anonymised examples of Item and location list; Opening quantities; Reorder and movement 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. Record stock movements and flag items reaching configured levels. Configuration, a connected module or a custom build are evaluated against that gap before a replacement is proposed.

What is outside this module?

Recorded balances depend on timely movement entries. Physical availability must be confirmed through the agreed count and reservation process.

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. Movements reconcile with location balances. Use this check when reviewing the first working version.

Talk to us

Discuss stock tracking and alerts 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