FREQUENTLY ASKED QUESTIONS & OPERATIONAL POLICIES

This page explains how Maxflow Traffic Control & Thermoplastic LLC (“Maxflow”) performs traffic control and pavement marking services on active projects in Colorado. It is intended to reduce field friction by clarifying scope, scheduling, responsibilities, and common jobsite outcomes.

This page is informational only. Services are provided only under a written quote/proposal, purchase order, or signed agreement. Where a written agreement conflicts with this page, the written agreement controls.


1) What services does Maxflow provide?

Maxflow provides the following services, subject to project requirements, jurisdiction rules, site conditions, and availability:

Traffic Control Services

  • Work-zone setup, maintenance, and removal

  • Lane closures, shoulder closures, road closures, detours, traffic shifts

  • Temporary access control and no-parking posting (where applicable)

  • Pedestrian routing and work-zone signing (as required by TCP/specs)

Traffic Control Plans (TCPs)

  • MUTCD-based TCP preparation and staging layouts (jurisdiction-dependent)

  • Coordination-ready plans intended to support review and field execution

Pavement Markings

  • Parking lot striping, layouts, and re-stripes

  • ADA-related markings

  • Thermoplastic symbols/legends (where specified and appropriate)

Service offerings for any specific project are defined solely by the written scope.


2) Who does Maxflow work with?

Maxflow primarily supports:

  • General Contractors (Prime Contractors)

  • Utility and underground contractors

  • Municipal/public agencies

  • Commercial property and HOA managers

Maxflow generally operates as a subcontractor unless otherwise agreed in writing.


3) Are your services MUTCD / CDOT / jurisdiction compliant?

Maxflow performs work in accordance with the Manual on Uniform Traffic Control Devices (MUTCD) and applicable jurisdiction requirements (city/county/DOT) for the project.

Final authority and interpretation of requirements rests with the Authority Having Jurisdiction (AHJ) and the project’s controlling documents (plans/specs/TCP approvals).


4) Do you prepare TCPs?

Yes, when included in scope. TCPs may be prepared based on:

  • Project plans/specifications

  • Site conditions and operational constraints

  • Jurisdiction submission standards

Important: TCP approval, review comments, and acceptance are controlled by the AHJ or designated reviewer. Maxflow does not control approval timelines or outcomes.


5) What is required before Maxflow mobilizes?

Mobilization occurs only after all applicable requirements are satisfied, including:

  1. Approved TCP (when required), and

  2. Written Notice to Proceed (NTP) or equivalent written authorization confirming:

    • scope and closure type

    • dates/hours

    • billing party (“customer of record”)

    • site access point and onsite contact

Verbal directions, texts, or field requests are not authorization unless confirmed in writing.


6) Can Maxflow mobilize same day or on short notice?

Short-notice requests may be considered based on staffing, device availability, travel time, jurisdiction requirements, and safety constraints. Same-day or emergency response is not guaranteed unless confirmed in writing.


7) What are your travel, mobilization, and service-area policies?

Maxflow is a mobile operation. Mobilization typically includes:

  • scheduling labor and equipment

  • staging/loading devices

  • travel to/from site

  • setup and breakdown activities

Travel/mobilization charges may apply based on location, schedule, and scope. Projects outside the primary service area may include additional travel/mobilization cost.

If a project is paused or restarted, remobilization charges may apply.


8) Cancellation and rescheduling policy (field-realistic)

Traffic control requires scheduling labor and securing devices. Cancellations create real costs.

  • More than 24 hours notice: reschedule when possible; charges may still apply if staffing/equipment was committed.

  • Within 24 hours of start time: may be billed for committed labor, equipment, and mobilization.

  • Same-day cancellation after dispatch: may be billed as a mobilization/standby event.

  • Jurisdiction delays (permit, TCP rejection, inspector unavailability) are not considered Maxflow-caused cancellations.

Cancellation/reschedule requests must be communicated in writing.


9) Standby, delays, and “job not ready” outcomes

If Maxflow is mobilized but unable to perform work due to conditions outside Maxflow’s control, time may be billed, including but not limited to:

  • site not ready / work limits not prepared

  • other trades blocking access or conflicting operations

  • inspector delays or failed coordination with AHJ

  • missing approvals, permits, notifications

  • changes to dates/hours not communicated

  • unsafe conditions created by others

  • owner/foreman/PM not available for release, access, or direction

Standby is billed at applicable labor/equipment rates. If release occurs and return is required later, remobilization may apply.


10) Site access and onsite coordination requirements

Customer must provide:

  • safe site access at the scheduled time

  • an onsite point of contact (foreman/superintendent/PM) authorized to coordinate

  • a clear work window and limits consistent with the approved TCP

Delays caused by lack of access, locked gates, missing escort, or inability to locate the onsite contact may be billed as standby or remobilization.


11) Scope changes and “field add-ons”

Traffic control scope must match the approved TCP and written agreement.

Any change to:

  • closure type (lane → full closure, etc.)

  • additional intersections/driveways

  • extended limits

  • added devices or labor

  • after-hours/night/weekend work

  • added days or shifts

must be confirmed in writing and may affect pricing and availability.

Field-level requests do not modify scope unless documented in writing.


12) Do you provide flaggers?

Flagging may be provided when included in the written scope and based on availability and jurisdiction requirements.

If the project requires Uniformed Traffic Control (UTC) or law enforcement presence, those services are typically arranged through the jurisdiction or authorized provider and billed accordingly. UTC scheduling and availability are outside Maxflow’s control.


13) Do you provide arrow boards, message boards, or impact attenuators?

When required by the approved TCP or project requirements, the following may be provided when included in scope:

  • Arrow boards

  • Portable message signs (PMS/VMS)

  • Impact attenuators (TMA)

Availability must be confirmed in writing prior to mobilization. Certain roadways/speeds may require additional protection per TCP/jurisdiction standards.


14) Who is responsible for permits and jurisdiction approvals?

Unless explicitly included in writing, the customer/prime contractor is responsible for:

  • permits and lane closure approvals

  • jurisdiction notifications and required coordination

  • inspection scheduling and required third-party approvals

Maxflow may assist with coordination when requested; responsibility must be defined in writing.


15) What information is required for an accurate quote?

To quote accurately, Maxflow typically needs:

  • address/location and jurisdiction

  • dates and hours

  • closure type and limits

  • duration (days/shifts)

  • TCP status (existing/needed) and submission requirements

  • pedestrian/bike routing requirements

  • UTC / special requirements (schools, events, arterials, night work)

Incomplete information may require revised pricing or scheduling.


16) Do you guarantee inspection approval, approvals, or timelines?

No. Maxflow executes work to applicable standards; however:

  • approval timelines and inspection results are controlled by the AHJ and project stakeholders

  • traffic incidents, weather, third parties, and site conditions can impact outcomes

No approval, inspection outcome, or schedule result is guaranteed unless expressly stated in a written agreement.


17) Weather, emergencies, and unsafe conditions

Safety governs operations. If conditions become unsafe due to:

  • severe weather / visibility

  • traffic incidents or emergency response

  • unsafe site conditions

  • unforeseen hazards

Maxflow may pause, modify, or stop operations until safe. Delays or additional mobilizations caused by unsafe conditions may affect schedule and cost.


18) Damage, loss, and theft of devices

The customer of record (the party who hired Maxflow and authorized service) is responsible for devices damaged, missing, or stolen while deployed on the project, including damage caused by third-party drivers, incidents, or unauthorized site access.

Replacement costs may be billed as separate line items tied to the job.


19) Public safety and third-party behavior

Maxflow cannot control third-party drivers or the actions of the public. Maxflow performs traffic control according to the approved TCP and applicable standards. Customer is responsible for overall site operations and coordination of trades.

Maxflow is not responsible for delays or incidents caused by third parties beyond Maxflow’s reasonable control.


20) Payment terms and non-payment

Payment terms are defined in the written quote/proposal/invoice. Depending on scope and duration, Maxflow may require:

  • deposit / pre-mobilization payment

  • payment for mobilization and initial service period

  • payment for additional days or scope changes before further deployment

The customer of record is responsible for payment. Non-payment may result in suspension of service where lawful and safe to do so.


21) Limitation of liability (standard protection)

To the fullest extent permitted by law, Maxflow shall not be liable for indirect, incidental, special, or consequential damages (including lost profits, delay damages, or third-party claims) arising from or related to services performed.

Maxflow’s responsibility, if any, shall be limited as provided in the written agreement and applicable law.


22) Force majeure (events beyond control)

Maxflow is not responsible for delays or non-performance caused by events beyond its reasonable control, including severe weather, traffic incidents, emergencies, government actions, labor disruptions, or acts/omissions of third parties.


23) Legal notice and scope clarification

Information on this page is provided for general informational purposes only and does not create a binding agreement.

All services are performed solely under a written quote/proposal, purchase order, or signed agreement defining scope, schedule, jurisdictional requirements, and billing responsibility. In the event of a conflict, the written agreement controls.


READY TO PROCEED?

Call 1-888-912-8999 to discuss traffic control requirements
or submit a request for review. Requests are typically reviewed within one business day.