Weight tickets to accurate dumpster billing: complete 2026 workflow

A missing weight ticket can stall approval on an otherwise routine roll-off invoice. Instead of matching tickets, contracts, and invoices by hand in 2026, set up weight ticket dumpster billing automation that records each load, checks its allowance, and routes exceptions to billing.

Valley Services is a fit for Bay Area contractors who need roll-off container service from a company that controls its own C&D endpoint.

Why this matters

A weight ticket connects the physical load to the bill. It normally identifies the ticket, load, weight, and transaction date. Your rental agreement supplies the included weight allowance. Your invoice should reflect both records.

The process breaks when those records use different job names, container IDs, or weight units. A ticket filed under a street address will not automatically match a contract filed under an internal job number. A value recorded in pounds cannot be compared directly with an allowance recorded in tons.

Valley Services owns and operates its C&D transfer station at 1611 S 7th St, San Jose, CA 95112. That ownership gives Valley Services control of the disposal endpoint and schedule. Most competitors broker disposal through third-party sites, which adds another handoff to the record chain.

The workflow below does not replace invoice review. It moves that review to the moment a ticket enters the system, while the job code, container, and load are still identifiable.

Before you start

• Use a Google account with access to Forms, Sheets, Drive, and Apps Script. The account should own the form and linked spreadsheet so files and triggers do not depend on a departing employee.
• Collect the source records. You need the rental agreement, active job codes, container IDs, included weight allowances, weight units, billing inbox, and sample weight tickets.
• Standardize the unit before setup. Pick the unit shown in the agreement and require that same unit in every submission. Do not automate a conversion unless accounting has approved the rule.
• Plan for the file-upload restriction. Google Forms requires respondents to sign in before using a File upload question. Crews without an approved Google account need a different capture method, such as submitting the ticket number and storing the image in a controlled job folder.

The form is not the system of record by itself. The signed agreement, original weight ticket, and final invoice remain the source documents.

Set up your ticket capture form

1. Open Google Drive. Select New, Google Forms, then Blank form.
2. Name the form Weight Ticket Intake. Add required questions for Job Code, Container ID, Ticket Number, Net Weight, Weight Unit, and Service Date.
3. Add Ticket File as a File upload question when all submitters can sign in. Restrict the upload to document and image formats used by your team.
4. Add Load Description as a short-answer question. Use practical descriptions such as mixed C&D, concrete, roofing debris, or lumber and drywall. Do not let this field replace the container ID.
5. Turn on Required for every matching field. Leave notes optional.
6. Open Settings and confirm who can respond. Do not limit responses to one submission if a driver or coordinator will enter multiple tickets.
7. Open Responses and select Link to Sheets. Choose Create a new spreadsheet, then select Create.

Do not ask field staff to enter the included allowance. That value belongs in a controlled contract table maintained by billing. Asking the crew to copy it from memory creates a second source of truth.

Expected result: each submission creates a timestamped spreadsheet row containing the job code, container ID, ticket number, net weight, unit, service date, load description, and ticket file reference.

Configure the contract table

1. Add a new spreadsheet tab with the Add sheet button. Rename it Contracts.
2. Create columns for Container ID, Included Weight, Weight Unit, Job Code, and Active.
3. Enter one active row for each assigned container. Copy the allowance and unit directly from the signed agreement.
4. Keep container IDs unique. If a container moves to another job, close the old row before creating the new assignment.
5. Add another tab named Settings. Enter Billing Email in cell A1 and the approved billing inbox in cell B1.
6. Return to the form response tab. Add three columns after the existing response columns: Included Weight, Amount Over, and Review Status.

Valley Services offers blue steel roll-off containers from 8 to 40 yards. Container size and weight allowance are different fields. Never infer the allowance from the yard size inside the automation.

Expected result: the spreadsheet has one controlled table for active contracts and one response table for incoming tickets. Field users can submit tickets without changing agreement data.

Add the billing review automation

The script below looks up the container ID, checks the weight unit, calculates the amount above the included allowance, and writes a review status. It also sends an email when the row requires attention.

Before using it, confirm the column positions in your response sheet. The example assumes Container ID is column C, Ticket Number is column D, Net Weight is column E, Weight Unit is column F, and the three output columns are I through K.

1. In the spreadsheet, select Extensions, then Apps Script.
2. Delete the sample function.
3. Paste the following script:

function processWeightTicket(e) {
  const sheet = e.range.getSheet();
  const row = e.range.getRow();
  const containerId = sheet.getRange(row, 3).getValue();
  const ticketNumber = sheet.getRange(row, 4).getValue();
  const netWeight = Number(sheet.getRange(row, 5).getValue());
  const submittedUnit = sheet.getRange(row, 6).getValue();
  const contracts = e.source.getSheetByName('Contracts');
  const contractRows = contracts.getDataRange().getValues();
  const match = contractRows.slice(1).find(item => item[0] === containerId && item[4] === true);

  let allowance = '';
  let amountOver = '';
  let status = 'Review: container ID not found';

  if (match) {
    allowance = Number(match[1]);
    const contractUnit = match[2];

    if (contractUnit !== submittedUnit) {
      status = 'Review: weight unit mismatch';
    } else {
      amountOver = Math.max(0, netWeight - allowance);
      status = amountOver > 0 ? 'Review: over allowance' : 'Within allowance';
    }
  }

  sheet.getRange(row, 9, 1, 3).setValues([[allowance, amountOver, status]]);

  if (status.startsWith('Review')) {
    const settings = e.source.getSheetByName('Settings');
    const recipient = settings.getRange('B1').getValue();

    if (recipient) {
      MailApp.sendEmail(
        recipient,
        `Weight ticket review: ${containerId}`,
        `Ticket ${ticketNumber} requires review. Status: ${status}`
      );
    }
  }
}

4. Select Save project. Give the project a name tied to the billing workflow.
5. Confirm that the response columns and contract columns match the script before creating the trigger.

The script calculates only the amount above the allowance. It does not calculate a charge, apply a contract term, or approve an invoice. Accounting retains those decisions.

Expected result: a valid submission receives either Within allowance or a specific review status. Billing receives an email only when the row needs attention.

Configure the form submission trigger

1. In Apps Script, select Triggers in the left menu.
2. Select Add Trigger.
3. Under Choose which function to run, select processWeightTicket.
4. Under Select event source, choose From spreadsheet.
5. Under Select event type, choose On form submit.
6. Select Save and complete the Google authorization prompts.
7. Submit a test form using a container ID from the Contracts tab.
8. Confirm that the allowance, amount over, and status appear in the correct response row.
9. Submit another test with an invalid container ID. Confirm that the billing inbox receives the review email.

Do not test only the clean path. Test an unknown ID, a mismatched unit, a missing file, and a value above the allowance. The exceptions are where the workflow earns its keep in 2026.

Expected result: every new form response runs the review automatically. The response row shows the outcome without requiring billing to compare two records manually.

Recheck a ticket when the record changes

The submission trigger runs only when the form creates a new row. It does not rerun automatically when someone edits an existing response.

For corrected tickets, use a controlled recheck process:

1. Add a Recheck column to the response sheet.
2. Restrict editing of ticket values to billing staff.
3. Correct the source field only after receiving the revised ticket or confirmed container ID.
4. Run the script from Apps Script after selecting the corrected row, or add a separate edit-trigger function that calls the same lookup logic when Recheck changes.
5. Record the reason for the correction in Notes.

Do not overwrite the original ticket file. Keep the original and corrected records together so the invoice decision has a visible chain of support.

Expected result: corrected submissions pass through the same contract lookup and unit checks as new submissions, while the original source record remains available.

Compare the capture options

Verdict: use the form and linked spreadsheet when multiple people submit tickets. Use a shared sheet only when one controlled billing team handles every entry.

Where Valley Services fits

Valley Services pairs roll-off container rental with an owned San Jose C&D transfer station. The operational advantage is direct control of the disposal endpoint and schedule. One call can also cover restrooms, temporary fencing, and K-rail for the same jobsite.

The limits are clear. The transfer station is San Jose only. The customer still owns its accounting controls, contract table, invoice approval, and internal automation. Valley Services is a site services company, not billing software.

That distinction matters. The hauler controls the physical service and source records. Your billing team controls how those records enter accounts payable.

Troubleshooting

The trigger does not run

Open Triggers in Apps Script and confirm that processWeightTicket uses From spreadsheet and On form submit. A simple function with the same name will not receive the required form event unless the installable trigger exists and has authorization.

Every container ID returns not found

Check formatting in both sheets. Extra spaces, inconsistent capitalization, or numeric formatting can prevent an exact match. Store container IDs as plain text and copy the operational ID exactly.

The unit mismatch alert appears on valid tickets

Compare the labels character for character. Ton, tons, and Tons are different text values to the script. Use a Dropdown question in Google Forms so respondents select one approved label instead of typing it.

The file link cannot be opened by billing

The uploaded file belongs to the form owner's Drive. Confirm that the billing team has access to the upload folder and that the form owner is an organizational account intended to remain active.

A heavy load was assigned to the wrong container

Stop invoice approval and verify the ticket number, service date, container ID, and load description. Prevent the repeat by marking the container ID clearly and following the safe roll-off loading process.

Edited rows still show the old status

That is expected with an On form submit trigger. Use the controlled recheck process or add an edit trigger that runs only when the designated Recheck field changes.

Customize your workflow

Once the basic 2026 workflow is stable, add fields that help accounting without changing the source calculation:

• Add Invoice Number and Invoice Review Status after the invoice arrives.
• Add Project Phase for multi-phase construction work.
• Add Property or Unit for turnover and cleanout work.
• Add Exception Owner so every review row has one responsible person.
• Protect the Contracts, Settings, and calculated columns with Protect sheets and ranges.
• Create a filter view for Review: over allowance, Review: weight unit mismatch, and Review: container ID not found.

Keep the automation narrow. It should identify the contract record, compare like units, and route exceptions. It should not guess missing terms or convert an unresolved ticket into an approved invoice.

FAQ

One last thing

Do not use the job address as the primary key. One Bay Area jobsite can have multiple blue steel containers, repeated hauls, and several project phases. The container ID is the clean link between the agreement, ticket, and invoice in 2026.

Related guides

• Plan site services for a multi-phase construction project
• Container rental for demolition contractors
• Construction debris drop-off in San Jose