A scope register is the central operational record of every deliverable, approved variation, and billing milestone on your project. It governs precisely what our teams produce, ties individual outputs directly to invoice schedules, and prevents unbudgeted costs from reaching your account.
How the scope register functions
When a project begins, Operations & Client Services establishes your scope register alongside the signed quote or statement of work. For package work priced on the packages page, the register mirrors the published feature set. For bespoke commissions, it reflects the specifications agreed during the quoting phase.
Every deliverable receives a unique line item, an assigned department—Creative, Technology, or Operations & Client Services—and a predefined billing trigger. As tasks move from production to quality review and delivery, the register updates in real time. Our studio operates Monday to Thursday, 09:00 to 17:00 GMT, and all register updates occur within these operational windows.
Because billing correlates directly with this register, no invoice is produced without a corresponding completed milestone or scheduled stage payment signed off internally by the relevant department lead.
Baseline deliverables versus variations
Your agreed scope covers only the items formally documented at the start of work. Anything outside those parameters is treated as a variation:
1. In-scope tasks: The core deliverables required to complete the brief. These are covered by your initial deposit and standard scheduled payments. 2. Out-of-scope variations: New features, revised technical specifications, extra design iterations beyond the agreed allowance, or significant strategic pivots.
When a request falls outside baseline specifications, Operations & Client Services raises a change item within the register. We calculate the cost and delivery impact and issue a variation quote. For bespoke adjustments, quotes are supplied within 48 hours of receiving a complete brief via the Ask Xylo chat on this portal. Production on the variation does not proceed until you confirm the quote in writing, ensuring unexpected fees never appear on your invoices.
Referred clients who have had a 10–30% discount confirmed in writing on their quote will see that discount applied uniformly to eligible additions in the register, while their referrer receives the standard ambassador commission.
Invoicing triggers and payment terms
Invoices are generated strictly against the state of the scope register. Depending on the engagement structure, billing aligns with one of three triggers:
- Upfront deposits: Required to allocate studio labour and lock the schedule. Deposits are non-refundable once your production slot is held. Before work begins, sums not yet earned are refunded pro rata; after work begins, completed work and booked time are charged. Defects are fixed free of charge within the acceptance window. The full terms are on the Refund Policy page of the main site.
- Milestone completions: Specific technical or creative deliverables logged as complete by our leads.
- Final handovers: Source files, deployment files, or system access handed over upon balance settlement.
If an item is marked as complete in the register, the accounting system automatically queues the corresponding invoice. If an item is delayed due to our internal schedule, its billing trigger is deferred alongside the deliverable.
Client responsibilities and dependency delays
A scope register also logs external dependencies. When deliverables rely on your feedback, content assets, or technical credentials, the register assigns an action item to you.
If you fail to provide necessary assets within the agreed timeframe, the following occurs: - The task status shifts to blocked in the register. - Milestone delivery dates adjust forward to preserve scheduling integrity across other projects. - Scheduled time-based billing triggers remain binding if studio capacity was reserved exclusively for that production block.
To avoid administrative delays or pause fees, upload all required assets through the Ask Xylo chat within standard operational hours.
Failure cases and scope disputes
Disputes regarding invoices arise almost exclusively when informal communication replaces the scope register. To maintain operational clarity, our studio enforces two firm rules:
- Informal communications via chat or draft documents do not constitute agreed scope changes until formally entered into the register by Operations & Client Services.
- Requesting an urgent addition without an approved variation quote will lead to the task being held in queue; studio specialists will not commence unauthorised labour.
If you believe an invoiced line item does not align with your deliverables, submit a review request through the Ask Xylo chat. Operations & Client Services responds to all enquiries within our standard 24-hour first reply target to audit the register entries against your written approvals.
Scope register checklist
Before signing off on project billing or requesting additions, confirm the following steps:
- Review the initial register baseline against your original quote before paying your deposit.
- Submit any new requirements via the Ask Xylo chat with a full brief rather than fragmented notes.
- Confirm every variation quote in writing prior to requesting that work begin.
- Ensure all required client-side assets are delivered ahead of the register's dependency deadlines.
- Check your milestone invoice references against the corresponding line numbers in your scope register.