COVU Service Order

Template version: 1.0 attorney-review draft - July 29, 2026 Provider: COVU Inc., a Delaware corporation Status: INTERNAL SOURCE - APPROVED FOR SYNTHETIC/STAGING VALIDATION ONLY; EXTERNAL, PRODUCTION, CHARGING, AND ROUTING USE HELD

This Service Order (this "Service Order") is the scope-specific commercial and operational order under the COVU Service Network Services Agreement (the "Service Agreement") and the COVU OS Lite Terms of Service (the "Platform Terms"). It becomes effective only when an authorized Agency owner or administrator accepts it with the Service Agreement, the required rate-card version, payment or invoicing branch, and any Credits Schedule stated below.

Order of precedence. Where documents conflict, the following order applies, and only for the subject each document expressly addresses: (1) a negotiated enterprise master services agreement executed by both parties, for the scope it covers; (2) the Data Processing Addendum, for the processing of Agency Customer Data; (3) the Security Exhibit, for security commitments; (4) the Service Network Services Agreement, for Service Network work; (5) an accepted Feature-Specific Consent, Additional Module Order, Service Order, or data addendum, for the feature, scope, price, cap, and term it names; and (6) the OS Lite Terms of Service, for the base platform. The Privacy Notice is a notice and acknowledgment and does not override any of the above or waive a statutory right. A document does not change another document on a subject it does not expressly address: this Service Order does not itself authorize a sensitive data connection or route any task; an accepted handoff remains subject to the required availability, authority, capacity, QA, provider, and release gates.

1. Order identity and selected scope

Service Order ID / version / hash: [ID / VERSION / SHA-256]
Effective date / term: [DATE / TERM]
Agency legal name / Agency ID: [NAME / ID]
Agency accepting owner/admin: [NAME / TITLE / EMAIL / USER ID]
Agency operational owner / escalation contact: [NAME / TITLE / EMAIL]
COVU operational owner: [NAME / TITLE / EMAIL]
Related Service Agreement / Platform Terms versions: [VERSION / HASH]
Negotiated enterprise agreement status: [NONE / MANAGED AGREEMENT ID / COVERED SCOPE]
Operating states / lines of authority / business: [STATES / LINES]
Carrier, appointment, access, and delegation rule: [RULE / SOURCE]
Selected catalog IDs, display labels, and lane IDs: [IMMUTABLE IDS / DISPLAY LABELS / LANE IDS]
Included work and deliverables: [PLAYBOOK / OUTPUT]
Excluded work and no-action boundaries: [EXCLUSIONS]
Proof and availability state required at handoff: [STATE / EVIDENCE]
Human approvals, review, and escalation rules: [ROLE / EVENT]
Data systems, access method, and feature-consent IDs: [SYSTEMS / OAUTH OR DELEGATED ACCESS / CONSENT IDS]

2. Price and commercial terms

Accepted rate-card version / hash / effective date: [VERSION / HASH / DATE]
Customer-facing billing unit and success rule: [OBJECTIVE UNIT / SUCCESS RULE]
Price factors and final price calculation: [FACTORS / AMOUNT / CURRENCY]
Discount rule after Credits are exhausted: [NONE / RULE / EXPIRY]
Credits Schedule / grant ID / price basis: [NONE / VERSION / HASH / GRANT ID]
Spend-control policy / period / approver: [UNRESOLVED — DO NOT EXTERNALLY ENABLE UNTIL FINANCE/PRODUCT POLICY IS APPROVED]
Payment branch: [STORED PAYMENT AUTHORIZATION / APPROVED INVOICE OR ACH SCHEDULE]
Auto-reload: [OFF / ON - SEPARATE ELECTION ID]
Taxes and approved pass-through costs: [NONE / DESCRIPTION / LIMIT]
Billing cadence and receipt/invoice delivery: [CADENCE / DELIVERY]

3. Handoff, commercial states, and timing

Handoff start event: [EVENT]. The accepted rate card and applicable Service Order must be available to the Agency on demand. There is no per-send price or confirmation screen. At accepted send, the server must record the selected lane, accepted rate-card version, price factors, final customer price, Credit application, payment branch, COVU-controlled timing target, third-party-wait rule, human-approval requirement, and applicable billable milestones or valid dispositions.

Price snapshot: At accepted send, COVU creates an immutable server-side event-level snapshot of the accepted Order, lane, catalog ID, price factors, final price, Credit application, discount, any separately approved spend-control result, currency, payment branch, and timestamp. The price may not increase after accepted send without a separately accepted new scope or Order.

COVU-controlled steps and evidence packet: [STEPS / EVIDENCE / REVIEWER].

Billable milestones: [MILESTONE / PRICE / REQUIRED EVIDENCE].

Valid terminal dispositions: [DISPOSITION / BILLABLE OR RELEASED / REQUIRED EVIDENCE]. A carrier, customer, system, access, authority, or other external result is billable only if it is expressly listed here as a billable disposition and COVU completed the specified COVU-controlled steps. If the result is not listed, the reservation must be released or sent to the approved exception process.

Third-party waits: [DEPENDENCY / WHEN CLOCK PAUSES / UPDATE CADENCE / BILLING TREATMENT].

Redo and rework rule: [COVU DEFECT / CHANGED AGENCY FACTS / NEW SCOPE / EXTERNAL CHANGE]. A redo at no charge may not create a second price snapshot, Credit reservation, or charge for the same accepted unit.

Delay and missed-service remedy: [EXACT TRIGGER / CREDIT OR ADJUSTMENT AMOUNT / EXCLUSIONS / EVIDENCE]. This field is required if Product displays a delay or missed-service remedy. Product may not infer a remedy from an internal target or a third-party wait.

Cancellation and suspension: [TERMINATION / PRE-HANDOFF RELEASE / POST-MILESTONE TREATMENT / SUSPENSION RULE].

4. Required customer acceptance

> By selecting Accept Service Order and enable selected lanes, I represent that I am a current Agency owner or administrator authorized to bind [AGENCY LEGAL NAME]. I accept this Service Order, the Service Network Services Agreement, the identified rate card, and the displayed payment or invoicing branch. I understand that only the selected lanes and scope are enabled; the rate card is available on demand; the server will pin the applicable price at accepted send; and acceptance does not guarantee availability or automatically route work.

Button:

> Accept Service Order and enable selected lanes

If this Service Order includes Credits, display the Credits Schedule separately and require its distinct, unselected acceptance control. If it includes a payment authorization or auto-reload, display and require each distinct authorization before activation.

5. Activation record and fail-closed checks

Product may mark this Service Order as contractually active only after it records the Agency, authorized accepter, authority representation, exact document versions/hashes, rendered Order, rate-card version, payment or invoicing branch, related Credits Schedule, displayed copy, timestamp, and receipt.

Product must still block every task submission unless the runtime also verifies the selected catalog/lane's current availability; Agency and provider authority; required licenses, appointments, carrier permissions, and system access; capacity; QA/reviewer coverage; data/feature consent; payment status; any separately approved spend-control policy; and required release flags. A missing, stale, revoked, unreadable, or conflicting record fails closed. An active Service Order is not an approval to route a task.

Required review

Attorney-reviewable first draft; not legal advice. Licensed counsel must approve operating-state insurance structure, clickwrap formation, the Service Agreement relationship, payment/credit treatment, arbitration/opt-out treatment, and any task/disposition-specific commercial terms. Finance, Product, Security, and Service Network must verify the event schema, price snapshots, cap, wallet, receipts, authority, availability, evidence, and fail-closed controls before external or production use.