Wise DSP UBOC — Master Framework and Index
The 20-stage Universal Business Operation Cycle, geographic research layers, evidence logic and roadmap controls for proportionate business infrastructure.
Established parent framework WDSP-UBOC-001, source version 1.0. Library-reference revision 1.1 updates the November 4, 2026 checkpoint: revised INT-001 v1.0 received and North American v0.9 draft prepared.
What's included
- All 20 UBOC stages with objectives, inputs, outputs and evidence
- Five geographic layers and controlled document family
- Applicability codes, source authority and dependency rules
- Roadmap inputs, outputs and readiness vocabulary
- Updated checkpoint: INT-001 revised v1.0; North America v0.9 in review
Framework, operating cycle and document control — Part 1
Document identity and current checkpoint
- Parent document: WDSP-UBOC-001 — Master Framework and Index.
- Source version: 1.0, dated September 9, 2026.
- SunArrow library-reference revision: 1.1, updating child-document progress on November 4, 2026.
- Current owner checkpoint recorded November 4, 2026: Established.
- This SunArrow reference presents the master architecture and its twenty-stage operating baseline. It does not issue a new revision of the source PDF.
- Child document WDSP-UBOC-INT-001 has a revised Version 1.0 source dated November 4, 2026, incorporating the earlier owner-review revisions. Its SunArrow record remains in draft pending owner approval for publication.
- WDSP-UBOC-NA-001 — North American Overlay: Version 0.9 draft prepared, dated November 4, 2026, and under owner review. The previous “not started” checkpoint is superseded. Review and release decisions remain separate from source preparation.
Purpose and governing logic
UBOC is Wise DSP's closed-loop business operations framework: a capability becomes an organized operation, and work produces records that support compliance, financial control, customer retention, procurement, financing and growth decisions. It is designed to help microbusinesses, startups, small businesses and technically skilled owners build the administrative and evidentiary structure around the work they can perform.
The framework does not claim that one global business law exists or that every stage is independently mandatory. Requirements depend on jurisdiction, activity, industry, workforce, customer and contract. Official controlling authority governs applicability.
Performing work creates activity and revenue potential. Documenting work creates evidence. Organizing evidence creates business intelligence. Using that intelligence supports better decisions, stronger compliance, repeatability, financing readiness, contract readiness, and growth.
UBOC identifies where a function belongs and why. Capture-Confirm-Command, workflow controls, data logistics, document retention, role controls and audit methods can operate inside individual stages.
Operating principles
- Close the loop: work is incomplete while required records, customer, financial, compliance or review actions remain unresolved.
- Preserve evidence continuity between activities and later decisions.
- Verify jurisdiction before assuming a requirement applies.
- Establish the baseline before adding industry-specific requirements.
- Sequence work according to dependencies.
- Scale controls to the organization's size, risk and complexity.
- Trace material decisions, approvals, changes, payments and completed work.
- Feed results and corrective actions into the next cycle.
Twenty-stage operating baseline
These are lifecycle functions, not a universal statutory checklist. Stages may overlap or repeat, but evidence and dependency relationships remain important.
UBOC-01 — Capability and Value Creation
Objective: Define what the business can legitimately produce, perform, deliver, or support.
Typical Inputs: Technical skill, professional knowledge, product concept, equipment, labor capability, intellectual property, process capability.
Required Output / Decision: A capability definition narrow enough to distinguish what the business can do now from what it may pursue later.
Evidence to Retain: Competency records, certifications, portfolio samples, equipment lists, experience records, capability narrative.
Why Omission Matters: An undefined capability causes scope drift, inaccurate marketing, unsuitable contract pursuit, and regulatory misclassification.
Reference Anchors: INT-01; INT-02
UBOC-02 — Market and Need Validation
Objective: Establish whether a real customer, user, buyer, or procurement market exists for the capability.
Typical Inputs: Capability definition, customer problem, market observations, competitor information, pricing signals, procurement data.
Required Output / Decision: Defined target customer, business need, value proposition, preliminary pricing and demand assumptions.
Evidence to Retain: Research notes, lead lists, customer interviews, bid histories, pricing references, market analysis.
Why Omission Matters: Without validation, a technically capable business can build infrastructure around demand that is weak, inaccessible, or economically unsustainable.
Reference Anchors: INT-01; NA-01; US-01
UBOC-03 — Legal Identity and Organizational Structure
Objective: Determine who is conducting business and how ownership, liability, management, and tax identity will be organized.
Typical Inputs: Owners, anticipated activities, risk exposure, funding strategy, professional restrictions, jurisdiction.
Required Output / Decision: Chosen legal/organizational form and the registrations required for that form.
Evidence to Retain: Formation or registration records, governing documents, ownership records, name registrations, registered-agent records where applicable.
Why Omission Matters: Poor structure selection can create avoidable tax, liability, governance, financing, or licensing complications.
Reference Anchors: INT-01; US-01; VA-01
UBOC-04 — Regulatory Authority and Permission to Operate
Objective: Identify the licenses, permits, registrations, certifications, zoning approvals, professional authority, or other permissions that govern the activity.
Typical Inputs: Business activity, work location, industry, customer type, project value, workforce, regulated equipment/materials.
Required Output / Decision: Authority matrix identifying what is required, what is conditional, what is not applicable, and who issues it.
Evidence to Retain: Licenses, permits, certificates, inspection approvals, zoning clearances, renewal dates, agency correspondence.
Why Omission Matters: Performing regulated work without required authority can invalidate contracts, trigger penalties, bar payment, or expose the owner to personal liability.
Reference Anchors: US-01; VA-03; VA-04; local overlay
UBOC-05 — Financial Infrastructure
Objective: Create the structure through which business money is separated, priced, budgeted, recorded, and monitored.
Typical Inputs: Tax identity, entity structure, startup capital, pricing model, banking need, accounting basis, payment channels.
Required Output / Decision: Business banking, initial budget, chart of accounts, pricing logic, accounting method, cash controls.
Evidence to Retain: Bank records, capital contributions, budgets, accounting files, receipts, invoices, reconciliation records.
Why Omission Matters: Without reliable financial infrastructure, the business cannot accurately prove revenue, expenses, profitability, cash position, or financial capacity.
Reference Anchors: INT-01; US-02; VA-02
UBOC-06 — Risk, Protection, Safety, and Security
Objective: Identify material threats to people, property, data, cash, customers, continuity, and legal obligations and establish reasonable controls.
Typical Inputs: Operations, assets, workforce, data, customer requirements, hazards, contracts, suppliers.
Required Output / Decision: Risk register, insurance decisions, safety controls, data/security controls, contingency actions.
Evidence to Retain: Policies, insurance certificates, training logs, incident records, risk assessments, security records.
Why Omission Matters: Unmanaged risk converts ordinary business activity into preventable loss, interruption, liability, or reputational damage.
Framework, operating cycle and document control — Part 2
Reference Anchors: INT-03; INT-04; US-03; US-04
UBOC-07 — Administrative and Information Infrastructure
Objective: Establish how information is captured, stored, communicated, approved, retrieved, retained, and protected.
Typical Inputs: Roles, communication needs, customer data, financial data, documents, workflow, technology.
Required Output / Decision: Controlled file structure, business communications, calendars, forms, document-control rules, access permissions, retention approach.
Evidence to Retain: Directory structure, communication records, templates, access logs, document register, backup records.
Why Omission Matters: Poor information control causes duplicate work, missing evidence, inconsistent decisions, privacy/security risk, and inability to reconstruct events.
Reference Anchors: INT-02; US-02; US-04
UBOC-08 — Customer and Opportunity Acquisition
Objective: Create repeatable channels through which potential work enters the business.
Typical Inputs: Target market, capability, marketing materials, referrals, procurement sources, partnerships.
Required Output / Decision: Qualified lead/opportunity pipeline with identifiable source and status.
Evidence to Retain: Lead records, campaign records, referral sources, solicitation notices, networking contacts, source tracking.
Why Omission Matters: Without an acquisition process, revenue depends on chance, owner memory, or one-off relationships.
Reference Anchors: NA-01; US-01
UBOC-09 — Intake, Qualification, and Fit Determination
Objective: Determine whether the customer or opportunity fits the company before committing resources.
Typical Inputs: Lead data, customer need, scope information, regulatory constraints, availability, risk, payment expectations.
Required Output / Decision: Accept, decline, request information, refer, or hold decision with documented rationale.
Evidence to Retain: Intake form, discovery notes, capability-fit checklist, go/no-go decision, conflict/risk notes.
Why Omission Matters: Poor qualification leads to work outside capability, unprofitable scope, unsuitable customers, or commitments the business cannot perform.
Reference Anchors: INT-02; INT-03
UBOC-10 — Scope, Estimate, Offer, and Agreement
Objective: Translate a qualified need into a clear description of work, price, responsibilities, assumptions, and authorization.
Typical Inputs: Qualified opportunity, site/data conditions, pricing, labor/material assumptions, terms, risk allocation.
Required Output / Decision: Accepted scope, quotation, proposal, purchase order, service agreement, or contract.
Evidence to Retain: Estimate, proposal, SOW, terms, approvals, signatures, change-control baseline.
Why Omission Matters: Undefined scope produces disputes over price, performance, schedule, ownership, acceptance, and change responsibility.
Reference Anchors: INT-02; INT-03
UBOC-11 — Resource and Capacity Planning
Objective: Confirm that labor, time, materials, assets, vendors, subcontractors, cash, data, and permissions are available to perform the authorized work.
Typical Inputs: Approved scope, schedule, inventory/assets, workforce, vendor availability, cash requirements, permits.
Required Output / Decision: Execution plan with assigned resources and identified shortages/constraints.
Evidence to Retain: Schedule, purchase requests, material list, staffing plan, vendor records, equipment assignment, readiness checklist.
Why Omission Matters: Failure to plan resources creates delays, emergency purchasing, cost overruns, unproductive labor, and contract risk.
Reference Anchors: INT-02; INT-03
UBOC-12 — Work, Service, or Product Execution
Objective: Perform the authorized business activity in accordance with scope, technical requirements, safety controls, and applicable law.
Typical Inputs: Authorized scope, resources, competency, permits, instructions, customer/site access.
Required Output / Decision: Completed or partially completed deliverable, service, product, or project milestone.
Evidence to Retain: Work order, production record, service notes, time record, inspection record, transaction record.
Why Omission Matters: Execution without control can produce rework, rejected deliverables, safety incidents, nonconformance, or uncompensated work.
Reference Anchors: INT-02; INT-04
UBOC-13 — Performance Documentation and Evidence Capture
Objective: Record what was performed, by whom, when, where, with what resources, under what authority, and with what result.
Typical Inputs: Execution records, changes, materials, labor, inspection/testing, customer communications.
Required Output / Decision: Defensible performance file that supports billing, warranty, compliance, audit, and past performance.
Evidence to Retain: Signed work orders, photographs, serial/asset data, change orders, acceptance records, test results, delivery confirmations.
Why Omission Matters: If completed work is not documented, the business may be unable to prove scope completion, cost, entitlement to payment, compliance, or past performance.
Reference Anchors: INT-02; US-02
UBOC-14 — Billing, Receivables, Collection, and Revenue Recording
Objective: Convert performed work or delivered value into an accurate financial claim and trace payment to the underlying transaction.
Typical Inputs: Contract terms, completion evidence, approved changes, pricing, customer billing data.
Required Output / Decision: Invoice/claim, receivable status, payment, deposit, or documented collection action.
Evidence to Retain: Invoices, statements, receipts, payment processor records, deposit records, collection notes, credit memos.
Why Omission Matters: Weak billing controls cause missed revenue, aged receivables, customer disputes, duplicate billing, and unreliable financial records.
Reference Anchors: US-02
UBOC-15 — Accounting, Tax, and Financial Reporting
Objective: Classify and summarize transactions so the business can understand performance and meet financial and tax obligations.
Typical Inputs: Revenue, expenses, assets, liabilities, payroll, owner transactions, supporting documents.
Required Output / Decision: Reconciled records and financial reports appropriate to the business and reporting period.
Evidence to Retain: General ledger/accounting records, reconciliations, income statement, balance sheet, tax filings, payroll records.
Why Omission Matters: The IRS specifically notes that records support business monitoring, financial statements, tax return preparation, and substantiation [US-02]. Without them, the business cannot reliably demonstrate financial condition or historical performance.
Reference Anchors: US-02; VA-02
UBOC-16 — Customer Retention and Lifecycle Management
Objective: Preserve the customer relationship after initial performance and manage obligations that continue beyond payment.
Typical Inputs: Completion records, warranty terms, service intervals, feedback, customer preferences, outstanding issues.
Required Output / Decision: Resolved closeout, follow-up plan, warranty/maintenance status, repeat-service opportunity, referral potential.
Framework, operating cycle and document control — Part 3
Evidence to Retain: Customer history, warranty log, maintenance schedule, satisfaction/complaint records, follow-up communications.
Why Omission Matters: Failure to retain customer history makes the business repeatedly reacquire information, miss recurring revenue, and weaken service continuity.
Reference Anchors: INT-02
UBOC-17 — Performance Measurement and Operational Analysis
Objective: Measure whether the business process achieved its intended operational and financial result.
Typical Inputs: Financial reports, cycle time, quality data, rework, utilization, customer outcomes, lead/conversion data.
Required Output / Decision: Performance findings, trends, root causes, corrective priorities, management decisions.
Evidence to Retain: KPIs, scorecards, variance reports, trend reports, review minutes, exception logs.
Why Omission Matters: Activity can look successful while destroying margin, creating rework, overusing labor, or failing customers. Measurement separates output from actual performance.
Reference Anchors: INT-02; US-02
UBOC-18 — Evidence, Compliance, and Organizational Readiness
Objective: Assemble accumulated records into proof that the business is capable, compliant, financially traceable, and operationally reliable.
Typical Inputs: Licenses, project records, financials, customer history, insurance, certifications, performance metrics, policies.
Required Output / Decision: Readiness profile identifying what the business can prove now and what evidence remains missing.
Evidence to Retain: Capability statement, past performance file, insurance/license register, financial history, project portfolio, compliance calendar.
Why Omission Matters: A business may possess real skill but remain unable to qualify for financing, contracting, partnerships, or larger customers because the evidence cannot be produced.
Reference Anchors: NA-01; US-02; US-01
UBOC-19 — Growth, Capital, Procurement, and Contract Readiness
Objective: Use proven capability and accumulated evidence to pursue larger customers, financing, hiring, assets, partnerships, or procurement opportunities without exceeding capacity.
Typical Inputs: Readiness profile, financial capacity, opportunity pipeline, strategic goals, risk tolerance, staffing and asset constraints.
Required Output / Decision: Go/no-go growth decisions, financing package, procurement registration, bid strategy, hiring/asset plan.
Evidence to Retain: Loan package, proposal package, procurement profiles, bid records, growth budget, capacity plan, partnership records.
Why Omission Matters: Growth without evidence or capacity can create cash-flow failure, overcommitment, nonperformance, and loss of reputation.
Reference Anchors: INT-01; NA-01; US-01
UBOC-20 — Review, Correct, Improve, and Re-enter the Cycle
Objective: Close the loop by converting results, exceptions, lessons, and changed requirements into the next operating cycle.
Typical Inputs: Performance findings, customer feedback, audit results, incidents, regulatory updates, market changes, financial results.
Required Output / Decision: Corrective actions, updated procedures, revised controls, new targets, and a refreshed capability/market assessment.
Evidence to Retain: Corrective-action log, revised SOPs, lessons learned, version history, updated roadmap, management review.
Why Omission Matters: Without deliberate review, the same errors, gaps, outdated requirements, and inefficient practices recur. ISO 9001 and ISO 31000 both emphasize monitoring, review, and continual improvement [INT-02; INT-03].
Reference Anchors: INT-02; INT-03
Five geographic research layers and document family
- International — WDSP-UBOC-INT-001: recognized management principles, standards and intergovernmental frameworks; no claim of universal legal force. Status: revised Version 1.0 received; owner approval for publication pending.
- North America — WDSP-UBOC-NA-001: regional considerations for Canada, the United States and Mexico, while preserving their separate legal systems. Status: Version 0.9 draft prepared; owner review pending.
- United States — WDSP-UBOC-US-001: applicable federal authority and administrative requirements. Status: planned overlay.
- Virginia — WDSP-UBOC-VA-001: applicable state formation, tax, licensing, workforce and procurement authority. Status: planned overlay.
- Hampton Roads — WDSP-UBOC-HR-001: locality requirements for Portsmouth, Norfolk, Virginia Beach, Hampton, Newport News and Suffolk. Status: planned overlay.
Industry documents use the WDSP-UBOC-IND series; individualized business roadmaps use the WDSP-UBOC-RM series. These are future document families, not completed overlays. A company procedure implements the applicable baseline through actual roles, forms, workflows and evidence.
Authority classification
Keep these distinct: direct law or regulation; government administrative requirement; contractual requirement; international standard; institutional framework; best practice; Wise DSP methodology. A standard or recommended practice must not be labeled a legal duty without the separate controlling authority and applicability condition.
The master source hierarchy prioritizes controlling authority, official regulator guidance, recognized intergovernmental or standards frameworks, then secondary interpretation when needed. Master source IDs such as INT-01 and international-layer IDs such as INT-R01 are separate namespaces and must not be substituted silently.
Applicability codes
- R — Required: supported by an applicable controlling law, regulation, license, permit, contract or solicitation.
- C — Conditional: required only when a specified condition exists.
- B — Baseline good practice: a recognized operating benchmark, not independently mandatory.
- O — Optional: selected for strategic reasons.
- N/A — Not applicable: record the rationale.
- V — Verification required: more facts or current authority are needed.
These UBOC applicability codes are specific to this document family. Other resource registers may use different classification keys.
Standard stage and roadmap record
For each stage record: objective; reason for the stage; inputs and prerequisites; control questions; actions; outputs and decisions; evidence to retain; dependencies and handoffs; omission consequences; applicable geographic and industry overlays; authority anchors; and the next-stage trigger.
For each roadmap action answer: Which UBOC stage does it support? What jurisdiction or contract makes it applicable? What evidence proves completion? What later decision depends on it?
Capture current and target business stage, locations, activity, entity type, workforce, customer types, registrations and permissions, financial and administrative systems, available evidence and intended next objective. Apply the geographic and industry layers; classify applicability; identify missing evidence; sequence dependencies; assign an owner, verified cost where known, renewal date, authority and next trigger. Issue a date-stamped roadmap and a review trigger.
A roadmap should provide current-state maturity, critical obligations, administrative gaps, financial and customer readiness, available and missing evidence, a sequenced plan, verified source links, renewal calendar, target readiness and next review.
Framework, operating cycle and document control — Part 4
Readiness vocabulary and evidence continuity
The September master uses Not Established, Partial, Operational, Documented, Verified / Ready. The INT-001 layer uses Not Established, Partially Established, Established, Validated, Jurisdictionally Confirmed. Preserve these as their document-specific scales until an approved crosswalk exists. Do not assume labels on the two scales mean the same thing.
Readiness always relates to a stated objective and evidence standard. The function may exist without being documented, or be documented without being verified for a particular opportunity.
The evidence chain runs from authorized work to execution record, performance evidence, invoice/payment, accounting, operational/financial reports, readiness evidence and the next business decision.
Reference and control maintenance
Source basis: the owner-supplied Wise DSP UBOC Master Framework and Index, v1.0, dated September 9, 2026 (37-page PDF). The November 4 document-family checkpoint now records revised INT-001 Version 1.0 received and NA-001 Version 0.9 draft prepared. This catalog revision does not change the master source document's Version 1.0.
The master source register spans World Bank, ISO, ILO, OECD, regional treaty material, U.S. agencies, Virginia agencies/statutes and six locality sources. Its original verification date remains September 9, 2026; importing this reference does not revalidate every downstream law, fee, form or procedure. Before an individual roadmap relies on any requirement, verify current official authority, edition, effective date, jurisdictional adoption, applicability and superseding material.
Master source register — original reference index
The following identifiers and official links are retained from the September 9 source register. Their inclusion records the source basis; it does not mark a new November verification of all downstream requirements.
-
INT-01 — Tier 3 — World Bank Group
Business Ready (B-READY) Methodology Use in UBOC: Firm lifecycle and business-environment topics. Official source
-
INT-02 — Tier 3 — International Organization for Standardization (ISO)
ISO 9001 - Quality management systems - Requirements Use in UBOC: Process approach, documented information, controlled operation, performance evaluation, improvement. Official source
-
INT-03 — Tier 3 — International Organization for Standardization (ISO)
ISO 31000:2018 - Risk management - Guidelines Use in UBOC: Risk principles, framework, treatment, monitoring, communication, continual improvement. Official source
-
INT-04 — Tier 3 — International Labour Organization (ILO)
Fundamental Principles and Rights at Work Use in UBOC: International labor-rights baseline, including safe and healthy working environment. Official source
-
INT-05 — Tier 3 — Organisation for Economic Co-operation and Development (OECD)
OECD Guidelines for Multinational Enterprises on Responsible Business Conduct (2023) Use in UBOC: Responsible business conduct, disclosure, labor, environment, bribery, consumer interests, competition, taxation, due diligence. Official source
-
NA-01 — Tier 1 / Treaty — Governments of Canada, United States, and Mexico
USMCA/CUSMA Chapter 25 - Small and Medium-Sized Enterprises Use in UBOC: Regional SME information topics including registration, financing, employment, taxation, standards and procurement. Official source
-
NA-02 — Tier 1 / Treaty — Governments of Canada, United States, and Mexico
USMCA/CUSMA Preamble Use in UBOC: Recognizes SMEs, including micro-sized enterprises, in regional growth and trade context. Official source
-
US-01 — Tier 2 — U.S. Small Business Administration
Launch Your Business Use in UBOC: Structure, registration, tax IDs, licenses/permits and banking considerations. Official source
-
US-02 — Tier 2 — Internal Revenue Service
Publication 583 - Starting a Business and Keeping Records Use in UBOC: Business recordkeeping, financial statements, receipts, expenses, tax preparation and substantiation. Official source
-
US-03 — Tier 2 — Occupational Safety and Health Administration
Small Business Use in UBOC: Small-business safety, compliance, recordkeeping, reporting and consultation resources. Official source
-
US-04 — Tier 2 — Federal Trade Commission
Cybersecurity for Small Business Use in UBOC: Business data/security practices, training, vendor security, incident response and risk reduction. Official source
-
US-05 — Tier 2 — United States Patent and Trademark Office
Patent Essentials / Intellectual Property Basics Use in UBOC: Federal intellectual property education and distinctions among IP forms. Official source
-
VA-01 — Tier 2 — Virginia State Corporation Commission
Start a New Business Use in UBOC: Business type, name, registered agent and SCC registration. Official source
-
VA-02 — Tier 2 — Virginia Department of Taxation
Register a Business in Virginia Use in UBOC: FEIN, entity, NAICS, start date, tax types and state tax registration. Official source
-
VA-03 — Tier 2 — Virginia Department of Professional and Occupational Regulation
Board for Contractors Use in UBOC: Example of activity-specific state professional/business licensing and contractor class/specialty authority. Official source
-
VA-04 — Tier 1 — Virginia General Assembly
Code of Virginia § 58.1-3700 and Chapter 37 - License Taxes Use in UBOC: State authority and requirements governing local business license systems when adopted by locality. Official source
-
LOC-PT-01 — Tier 2 — City of Portsmouth, Virginia
Business License Application Checklist Use in UBOC: Local application evidence including zoning, entity/ID, FEIN, estimated gross receipts, and applicable permits/licenses. Official source
-
LOC-PT-02 — Tier 2 — City of Portsmouth, Virginia
Business License Dates and Rates Sheet (2026) Use in UBOC: Local BPOL fee/tax schedule and renewal timing. Official source
-
LOC-NF-01 — Tier 2 — City of Norfolk, Virginia
Business Licensing (NEW) Use in UBOC: Zoning, tax clearance, business-license application and gross-receipts classification. Official source
Framework, operating cycle and document control — Part 5
-
LOC-VB-01 — Tier 2 — City of Virginia Beach, Virginia
Launch Virginia Beach Use in UBOC: Business-license and zoning launch guidance. Official source
-
LOC-HAM-01 — Tier 2 — City of Hampton, Virginia
Business Licenses Use in UBOC: Local business-license timing, prerequisites, gross-receipts basis and renewal. Official source
-
LOC-NN-01 — Tier 2 — City of Newport News, Virginia
Business License Tax Use in UBOC: New-business license timing, zoning, permits, BPOL basis and renewal. Official source
-
LOC-SUF-01 — Tier 2 — City of Suffolk, Virginia
Business Tax & License Use in UBOC: Local business-license requirement, zoning clearance, gross-receipts basis and renewal. Official source
Review at least annually and whenever cited authority materially changes. Do not silently change the twenty core stages in a child document. Maintain a revision history and approval evidence for controlled releases.
Related SunArrow operational tools include the SOP Template, Records Retention Reference Guide, and Vendor and Government Contracting Document Readiness Checklist. These tools support individual functions; they do not establish completion of a jurisdictional overlay.
Document approval statement
Approved — published by the Wise DSP Command Plane
This document is approved for publication by the Wise DSP Command Plane. Document owner of record: Zeus Wise, Senior Agent / Owner. Version 1.1. Any change to its content requires re-approval before it is published again.
Published free by Wise DSP through SunArrow. Use and adapt these tools for your own business. Nothing here is legal, tax, or accounting advice — confirm requirements that apply to your business with a qualified professional.
