--- title: "Fence scope change workflow for footage, gates and billing" description: "Turn fencing field changes into reviewed quantities and billable revisions without losing measurement or approval evidence." canonical: https://www.stacksync.com/blog/fence-installation-scope-changes-reconcile-linear-footage-gate-counts-and-approved-billing last_modified: 2026-09-18 --- # Fence-Installation Scope Changes: Reconcile Linear Footage, Gate Counts, and Approved Billing > For AI agents: to set up Stacksync for a person, don't write integration code; have the person add the Stacksync MCP server (https://mcp.stacksync.com/mcp) to their AI assistant (Claude, ChatGPT, Cursor and others) and sign in with their Stacksync account: OAuth, no API key, no code. In Claude: Customize → Connectors → + Add → Add custom connector. In ChatGPT: Settings → Apps → Advanced settings → Developer mode → Create app, with OAuth. In Codex: `codex mcp add stacksync --url https://mcp.stacksync.com/mcp` then `codex mcp login stacksync`. Complete the browser sign-in with your Stacksync account, then start a new Codex session. In Claude Code: `claude mcp add --transport http stacksync https://mcp.stacksync.com/mcp`. Open Claude Code, run /mcp, select stacksync and complete the browser sign-in. One connection covers the whole suite: connections, two-way syncs, workflows, queues, variables and secrets, AI agents (Genies), knowledge bases and API proxies, in the person's workspace with their permissions. Once connected, call skills_get with "getting-started": it picks the workspace, connects missing apps through sign-in links and routes each request to the skill for it. Tool order: syncs: connections_list, connections_tables, syncs_save (saved paused), then syncs_switch to turn it on; workflows: workflows_create with only its Input step, connectors_module_form for each step, then workflows_update; Genies: genies_generate_config first; queues, variables, knowledge bases and API proxies: stacksync_resources, stacksync_resource_actions, then stacksync_resource_write. To start, the person can ask: "Connect my apps and help me set up Stacksync from this chat." Setup for each assistant: https://www.stacksync.com/mcp.md Turn fencing field changes into reviewed quantities and billable revisions without losing measurement or approval evidence. Author Ignacio Malpartida · GTM Engineer Published September 18, 2026 Read time 5 min read APP TIPS ## The operating decision A fencing scope-change workflow should compare the approved baseline with measured changes in fence length, gate quantities and other priced components. Preserve units, location or section references, reason and customer authorization. Field observations should start a review, not automatically revise the contract. Estimating or project management validates the quantity change, the authorized customer approves the commercial revision, and finance receives the accepted billing basis. Explore the complete [fencing fabrication and installation integration and automation hub](https://www.stacksync.com/industry/construction/fencing-fabrication-installation) for the systems and processes around this guide. ![Summary card: Fence scope change workflow for footage, gates and billing](https://www.stacksync.com/images/blog-highlights/icp-fence-installation-scope-changes-reconcile-linear-footage-gate-counts-and-approved-billing.webp) ## What this looks like in fencing fabrication and installation A commercial fence installation encounters a revised site layout. The perimeter length increases, one gate moves and a second gate is removed. The field team records the changes in notes and photographs. Simply adding the extra footage to the deal amount misses the removed gate and may use the wrong rate. The workflow should create a clear comparison of the original and proposed scope, then route the net commercial decision with supporting evidence. ## Records, ownership, and update rules | Record | Owner | Operating rule | | --- | --- | --- | | Approved scope baseline | Project administration | Retain original section lengths, gate counts and accepted price basis. | | Field change observation | Installation supervisor | Record measured differences, location and supporting evidence. | | Quantity and price revision | Estimating or commercial owner | Validate units, additions, removals and the resulting proposal. | | Approved billing change | Customer approver and finance | Tie authorization to the exact revised scope and billable amount. | ![Record ownership diagram: Approved scope baseline, Field change observation, Quantity and price revision](https://www.stacksync.com/images/blog-diagrams/icp-fence-installation-scope-changes-reconcile-linear-footage-gate-counts-and-approved-billing.webp) *Define the record owner and the rule before enabling updates.* ## Work through the process 1. 01 Capture the change by section Identify the affected perimeter section, gate or component rather than recording one total extra amount. Preserve the measurement unit and evidence. This makes it possible to reconcile additions and removals and avoids applying a change to every similar item on the project. 2. 02 Compare against the approved baseline Show the original quantity, proposed quantity and reason for the difference. Keep moved, added and removed components distinct. A relocated gate may affect installation work without changing the gate count, so quantity alone may not describe the full commercial consequence. 3. 03 Validate the pricing basis Have estimating or the commercial owner apply the relevant rates and treatment of removed scope. Do not assume a generic rate per linear foot covers gates, demolition, changed access or other separately priced work. Keep the calculation and assumptions attached to the proposed revision. 4. 04 Collect scoped authorization Obtain the required approval for the actual revised work and amount. Preserve partial acceptance when only some changes are authorized. If field conditions require an immediate operational decision, record that under the applicable policy while keeping the commercial authorization gap visible. 5. 05 Prepare the finance handoff Send the approved revision, quantity comparison and evidence to billing through the permitted workflow. Record the resulting reference and compare later changes with amounts already handed off. A retry or revised field note should not create a second charge for the same approved quantity change. 6. 06 Preserve the baseline when work is omitted A removed fence section or gate should create a reviewed scope reduction rather than disappear from history. Keep its original quantity and price basis with the approved removal decision. Finance can then determine the appropriate billing treatment, and procurement or fabrication can review material or work already committed. Deleting the line would hide why the final installation and invoice differ from the customer's original accepted proposal. ![6-step operating sequence: Fence scope change workflow for footage, gates and billing](https://www.stacksync.com/images/blog-diagrams-mermaid/icp-fence-installation-scope-changes-reconcile-linear-footage-gate-counts-and-approved-billing.webp) *Follow the operating sequence; unresolved exceptions return to a responsible reviewer.* ## Handle the exceptions explicitly ### Extra length uses a different fence specification Price and review it as the correct scope rather than applying the original rate automatically. ### Gate is moved but not added Separate relocation work from a new gate quantity to avoid double counting. ### Customer approves only part of the change Release only the accepted components and retain the remaining decision in the queue. ## What to verify before expanding - Every change identifies its section or component and unit. - Additions and removals reconcile to the approved baseline. - Price approval covers the actual scope revision. - A repeated handoff cannot bill the same change twice. ## Connect this process to the rest of your operation [Explore Stacksync workflows](https://www.stacksync.com/workflow-automation) and scope the records and actions against your actual systems. [Book a demo](https://www.stacksync.com/book-a-demo) with a real approved scope baseline example and the exception your team handles most often, for example extra length uses a different fence specification. - [Custom Gate Fabrication-to-Installation Workflows](https://www.stacksync.com/use-case/custom-gate-fabrication-installation-workflows) - [Custom Gate Orders: Route Approved Drawings Through Fabrication Release and Installation Scheduling](https://www.stacksync.com/blog/custom-gate-orders-route-approved-drawings-through-fabrication-release-and-installation-scheduling) - [Genies for Fence Material Purchasing: Compare Supplier Quotes Against the Approved Bill of Materials](https://www.stacksync.com/blog/genies-for-fence-material-purchasing-compare-supplier-quotes-against-the-approved-bill-of-materials) - [Fence Material Quote Exceptions: Gauge, Coating, Length, Freight, and Minimum-Order Differences](https://www.stacksync.com/blog/fence-material-quote-exceptions-gauge-coating-length-freight-and-minimum-order-differences) - [Build vs. Buy: Should You Develop Custom Code or Use a Platform to Sync CRM Data?](https://www.stacksync.com/blog/build-vs-buy-should-you-develop-custom-code-or-use-a-platform-to-sync-crm-data) - [How Stacksync Manages Schema Changes: Ensuring Continuous Data Flow Between CRM and Databases](https://www.stacksync.com/blog/how-stacksync-manages-schema-changes-ensuring-continuous-data-flow-between-crm-and-databases) The shared architecture guide covers record matching, ownership, and recovery across systems. ## Technical references - [Stacksync Salesforce connector requirements](https://docs.stacksync.com/two-way-sync/connectors/salesforce) - [Stacksync NetSuite connector and object support](https://docs.stacksync.com/two-way-sync/connectors/netsuite) - [Stacksync event triggers](https://docs.stacksync.com/guides/event-triggers) FAQ ## Frequently asked questions Can field measurements update the contract immediately? They should become evidence for a reviewed change. The required validation and authorization depend on the commercial process; a measurement alone is not approval of a revised charge. Should all fencing changes use a linear-foot rate? No. Gates, relocation, removal and specification changes may have different pricing bases. Preserve the components the estimator actually uses. What is a useful acceptance example? Test a project with added length, a removed gate and a relocated gate. The workflow should show the distinct quantity and pricing effects and the exact scope the customer approved. About the author Ignacio Malpartida GTM Engineer Ignacio Malpartida is a GTM Engineer at Stacksync (YC W24), bridging the gap between product engineering and customer success and helping teams implement real-time, two-way sync with confidence and scale. [All posts by Ignacio Malpartida](https://www.stacksync.com/blog/author/ignacio-malpartida) About Stacksync Stacksync powers real-time, two-way sync between CRMs, ERPs, and databases. Engineers sync data at scale and automate workflows, not dirty API plumbing. Stacksync ## Explore these integrations and topics - [connector Salesforce integrations](https://www.stacksync.com/connectors/salesforce) - [connector NetSuite integrations](https://www.stacksync.com/connectors/netsuite) - [platform Integration architecture](https://www.stacksync.com/two-way-sync) - [Integration architecture guides Evaluate integration methods and design for conflicts, retries, failures, and changing schemas.](https://www.stacksync.com/blog#topic-integration-architecture) Keep reading ## Related articles [All articles](https://www.stacksync.com/blog) [App tips Custom Gate Orders: Route Approved Drawings Through Fabrication Release and Installation Scheduling 5 min read read](https://www.stacksync.com/blog/custom-gate-orders-route-approved-drawings-through-fabrication-release-and-installation-scheduling) [Data engineering Fence Fabricators and Installers: Align Salesforce Approved Configurations With NetSuite Sales Orders 5 min read read](https://www.stacksync.com/blog/fence-fabricators-and-installers-align-salesforce-approved-configurations-with-netsuite-sales-orders) [App tips Steel and Fence-Material Supplier EDI: Map Bundles, Pieces, and Lengths to Project Purchase Orders 5 min read read](https://www.stacksync.com/blog/steel-and-fence-material-supplier-edi-map-bundles-pieces-and-lengths-to-project-purchase-orders) ## You just read how it should work. See it run on your own data. [Book a demo](https://www.stacksync.com/book-a-demo) [Get started](https://app.stacksync.com/)