Direct answer: A service-procurement/business-outsourcing page is not a line saying "we provide/accept outsourcing, price negotiable". The page should state: service scope and categories (R&D, credit investigation, feasibility study, toll processing, property management, customer service, IT, testing, logistics, consulting); core/non-core boundary and the "outsource or not" decision; major/general outsourcing and approval; contractor selection (legal entity, business scope, fixed office, professional qualifications, personnel qualifications, technology/experience); pricing and competition (cost-benefit, tender/comparison, no bribery/rebate); contract/SOW/SLA (scope, service and quality standards, confidentiality, fee settlement, breach); performance monitoring, subcontracting, data/confidentiality, contingency; acceptance (deliverables, service levels, evidence, acceptance certificate); settlement, termination/claims, exit/transition; public boundary. On the rules: MOF Internal Control Application Guideline No. 13 (Business Outsourcing) requires classified management, defined scope/method/conditions/procedure, avoiding core-business outsourcing, approval within authority, competitive contractor selection, reasonable pricing, contract terms covering service/quality standards/confidentiality/settlement/breach, continuous performance evaluation, and acceptance with a certificate; No. 7 (Procurement) applies to service procurement authority/pricing/contract/acceptance/payment; No. 16 (Contract Management) requires written contracts, term review, signature within authority, performance monitoring, change/termination, disputes and archive. This article is current to 2026-11-09 and is a summary of public rules and page method, not legal, procurement or outsourcing-audit advice; company outsourcing policy, contracts, SOW/SLA and system configuration control.
This article is for procurement, business, IT, finance, legal, quality, EHS and website teams at equipment, electronics, automotive-parts, medical-device, hardware, chemical, packaging and export manufacturers in Changzhou and nearby. It covers how to write and accept a service-procurement/business-outsourcing page. The usual gap is "unclear scope, core business outsourced, contractor qualifications unchecked, price without basis, missing SOW/SLA, acceptance based only on a report, no one manages subcontracting/data/confidentiality, no transition on termination", ending with a page that only says "professional services, long-term cooperation", while delivery/acceptance/settlement/exit still disagree.
First define the boundary: what can be outsourced, what cannot, major or general, who approves. Then define delivery: SOW/SLA, deliverables, acceptance criteria, evidence and acceptance certificate. Finally manage performance: subcontracting, data/confidentiality, continuous evaluation, settlement, termination for breach and transition. "Professional services, long-term cooperation" is not enough.
How does this page relate to SOW/technical specification, contract, on-site contractor, hazardous-waste service and budget pages?
The service-procurement/outsourcing page answers "which services to outsource, how to select the contractor, how to price/accept/exit"; the SOW/technical-specification page answers "technical/business requirements, standards, acceptance method, version"; the contract page answers "terms/priority/signature/version"; the on-site service/contractor page answers "induction, work permit, safety agreement, insurance, exit"; the hazardous-waste service page answers "operating permit, manifest, transport, storage, ledger"; the budget page answers "limit/encumbrance/execution". The service-procurement page is the main page for "services/outsourcing" and cannot be replaced by a SOW or on-site safety page.
Common breaks: outsourcing core business; major outsourcing not reported to the board; contractor qualifications/personnel unchecked; arbitrary price; SOW only says "as needed"; SLA has no metrics/measurement; acceptance based only on the provider's report; subcontracting not disclosed; no data/confidentiality agreement; no performance evaluation; no claim for breach; no transition/data handover on exit; settlement disconnected from acceptance. The page separates "boundary—selection—pricing—SOW/SLA—performance—acceptance—settlement—exit—public boundary" so business/procurement/finance/legal/quality share one vocabulary.
| Page | Question it answers | Key content | Cannot replace |
|---|---|---|---|
| Service/outsourcing | What to outsource/how to select/price/accept/exit | Scope, contractor, SOW/SLA, acceptance, termination | SOW technical specification |
| SOW/specification | Technical/business requirements/standards/acceptance method | Scope, standards, deliverables, version | Outsourcing decision/contractor selection |
| Contract | Terms/priority/signature/version | Rights, breach, confidentiality | Service performance/acceptance |
| On-site contractor | Induction/permit/safety/insurance/exit | Training, permit, agreement | Service scope/SLA |
| Hazardous-waste service | Permit/manifest/transport/storage | Qualification, manifest, ledger | General service procurement |
| Budget | Limit/encumbrance/execution | Budget, encumbrance, variance | Outsourcing pricing/acceptance |
Page relationships are editorial; company outsourcing policy, contracts and SOW/SLA control.
Which services can be outsourced, and how should classification/boundary be set?
Classify first: R&D, credit investigation, feasibility study, toll processing, property management, customer service, IT services, testing/calibration, logistics/warehousing, consulting/training, security/cleaning, etc.; then classify by impact as "major/general outsourcing", with major outsourcing submitted to the board or similar body, and the CFO/accounting head participating in the decision. Dimensions: whether it is core business/technology/data; impact on qualification/compliance/safety/customers; reversibility/alternatives; cost-benefit; data/confidentiality; supply-interruption risk. Guideline No. 13 states that companies should weigh pros and cons and avoid outsourcing core business; scope/method/conditions/procedure should be institutionalised, not signed ad hoc by a department.
Acceptance checks: service list; core/non-core; major/general; approval level; outsourcing rationale; reversibility/alternatives; data/security impact; budget. Common gaps: core business outsourced; no classification; major not reported; rationale only "save money"; no fallback.
| Dimension | What to write | Evidence | Common gap |
|---|---|---|---|
| Service categories | R&D/credit/feasibility/processing/property/customer service/IT/testing/logistics/consulting | Service list | Unclear scope |
| Core boundary | Core business/technology/data not outsourced or strictly controlled | Assessment | Core outsourced |
| Major/general | Impact, approval level | Policy/resolution | No classification |
| Rationale | Cost/capability/speed/risk | Assessment | "Save money" only |
| Reversibility | Fallback/alternative supplier/transition | Plan | No fallback |
| Data/security | Data classification/access/confidentiality/compliance | Assessment | Not assessed |
| Budget | Annual/project/cost basis | Budget | No budget |
| Approval | Department/management/board | Record | Ultra vires |
Classification/boundary are editorial; Guideline No. 13, company outsourcing policy and the articles control.
How should contractor selection, pricing and contract be accepted?
Contractor conditions at least: legally established/licensed, matching business scope, fixed office; professional qualifications, personnel meeting role/qualification requirements and professional technical qualifications; technology and experience meeting the requirement. Selection should introduce competition, be open/fair/impartial, and follow tender law where tendering; company personnel must not accept bribery/rebates/benefits, and contractors must not bribe to win business. Pricing should consider internal/external factors and cost-benefit; select within authority and sign a contract. The contract should cover service content/scope, rights/obligations, service and quality standards, confidentiality, fee settlement, breach; a separate NDA is needed where confidential, and the contractor must inform its personnel. The contract should align with SOW/SLA, acceptance, payment, data/subcontracting terms.
Acceptance checks: entity/scope/office; qualifications/personnel; technology/experience; competition/tender; pricing basis; contract terms; NDA; authority/signature. Common gaps: unqualified; no comparison; contract lacks service standard; confidentiality/subcontracting missing; work before contract.
| Item | What to write | Evidence | Common gap |
|---|---|---|---|
| Entity/scope | Legally established/scope/office | Licence/site | Unqualified |
| Qualifications | Qualification/personnel/experience | Certificate/CV | Personnel mismatch |
| Competition/tender | Open/invited/tender, evaluation | Record | Direct appointment |
| Pricing | Cost-benefit/market/quote comparison | Comparison | Arbitrary |
| Contract content | Scope/rights/service standard/confidentiality/settlement/breach | Contract | No standard |
| Confidentiality | NDA/personnel notice | NDA | No NDA |
| Subcontracting | Allowed/approval/liability | Clause | Default subcontracting |
| Authority/signature | Sign within authority/seal | Authority | Ultra vires |
Contractor/pricing/contract are editorial; Guideline No. 13, tender rules and company contract policy control.
How should SOW, SLA, deliverables and acceptance be accepted?
SOW states "what to do": scope, objectives, work content, deliverables, time/milestones, location, interfaces, assumptions/exclusions, standards/specifications, acceptance method and change process. SLA states "how well": service hours/response/recovery/availability/accuracy/complaint handling/reporting metrics, measurement method, data source, measurement period and remedies (service credit/remediation/termination). Acceptance: accept by deliverable/milestone/service period, checking quantity/quality/standard/evidence; services cannot rely only on a "report" — require verifiable records (tickets, logs, sampling, user confirmation); issue an acceptance certificate; report/handle exceptions immediately. Data/IP/knowledge transfer should be stated in SOW/contract.
Acceptance checks: SOW completeness; SLA metrics/measurement; deliverable list; milestones; acceptance criteria; evidence; acceptance certificate; exception handling; knowledge transfer. Common gaps: SOW says "as needed"; SLA no metrics; acceptance only a report; no certificate; no knowledge transfer.
| Element | What to write | Evidence | Common gap |
|---|---|---|---|
| SOW scope | Objectives/content/deliverables/time/interfaces/exclusions | SOW | "As needed" |
| SLA metrics | Response/recovery/availability/accuracy/complaints | SLA | No metrics |
| Measurement | Method/data source/period/owner | Report | Not measurable |
| Remedies | Service credit/remediation/termination | Clause | No remedy |
| Deliverables | List/format/version/ownership | List | Unclear |
| Acceptance criteria | Quantity/quality/standard/sampling/user confirmation | Standard | Report only |
| Acceptance certificate | Organisation/signature/date/conclusion | Certificate | No certificate |
| Knowledge transfer | Documents/training/accounts/data | Record | No transfer |
SOW/SLA/acceptance are editorial; the service contract, SOW/SLA and company acceptance policy control.
How should performance monitoring, subcontracting, confidentiality and data be accepted?
Performance monitoring: continuously assess the contractor's capability under the contract/SLA; for major outsourcing, monitor closely and establish a contingency mechanism to avoid business interruption; regular communication, tickets/reports, exception escalation and remediation closure. Subcontracting: state whether allowed, approval, subcontractor qualifications, joint liability and data/security requirements; do not assume subcontracting. Confidentiality: NDA, limited access, personnel notice, exit recovery; data: classification, minimisation, storage location, cross-border, deletion/return, incident notification; personal information/important data follows applicable law. Change: scope/price/SLA/subcontracting changes in writing/approved; major change re-assesses the outsourcing decision. Termination: material breach may be terminated with claims; transition/data handover/account closure required.
Acceptance checks: performance assessment; SLA reports; exceptions/remediation; contingency; subcontracting approval; subcontractor qualifications; NDA; data classification/cross-border/deletion; change; termination/transition. Common gaps: no assessment; subcontracting undisclosed; no data agreement; verbal change; no transition on termination.
| Item | What to write | Evidence | Common gap |
|---|---|---|---|
| Performance assessment | Capability/quality/timeliness/compliance/finance | Assessment | No assessment |
| SLA report | Metrics/misses/remediation | Report | No report |
| Contingency | Major outsourcing/interruption/alternative | Plan | No plan |
| Subcontracting | Allowed/approval/qualification/liability | Clause/record | Default subcontracting |
| Confidentiality | NDA/access/personnel notice/recovery | Agreement | No NDA |
| Data | Classification/minimisation/location/cross-border/deletion/incident | Agreement/record | No agreement |
| Change | Scope/price/SLA/subcontracting written approval | Change order | Verbal change |
| Termination/transition | Breach/notice/handover/account closure | Record | Sudden stop |
Performance/subcontracting/data are editorial; Guideline No. 13, contracts, data-protection and security requirements control.
How should settlement, termination, claims and exit be accepted?
Settlement: settle per contract/SOW/SLA and acceptance results, checking service volume/unit price/milestones/credits/tax/invoice; no payment without acceptance or where service levels are missed; prepayment needs guarantee/verification; cost accounting follows accounting standards. Termination: terminate promptly when a material breach makes performance impossible; claim damages per contract and hold responsible persons accountable; termination for the company's own reasons follows notice/compensation/transition. Exit: hand over documents/data/accounts/equipment/site, knowledge transfer, notify subcontractors/suppliers, confidentiality obligations survive, archive. Guideline No. 13 requires continuous performance evaluation, termination for material breach, claims and acceptance certificate; Guideline No. 16 requires performance monitoring, change/termination, dispute handling and registration/archive.
Acceptance checks: settlement basis; acceptance result; service volume/unit price; credits; invoice/tax; prepayment; termination conditions; claims; handover; archive. Common gaps: payment before acceptance; no credit for missed SLA; prepayment not verified; no claim for breach; no handover on exit.
| Item | What to write | Evidence | Common gap |
|---|---|---|---|
| Settlement basis | Contract/SOW/SLA/acceptance | Document | Pay before acceptance |
| Volume/unit price | Hours/tickets/milestones/unit price | Record | Estimate |
| Credits/penalties | Missed SLA/service credit | Calculation | No credit |
| Invoice/tax | Invoice/tax rate/payment terms | Invoice | Non-compliant |
| Prepayment | Guarantee/verification/progress | Record | No verification |
| Termination | Breach/notice/compensation/transition | Notice | No termination right |
| Claims | Loss/evidence/time limit/accountability | Claim letter | No claim |
| Exit/archive | Documents/data/accounts/equipment handover, archive | List | No handover |
Settlement/termination/exit are editorial; the contract, accounting standards and company exit process control.
How should the website page be written, and what must not be published?
Suggested sections: (1) service scope and categories; (2) core/non-core boundary and outsourcing principles; (3) contractor selection/pricing/contract principles; (4) SOW/SLA/deliverables/acceptance; (5) performance/subcontracting/confidentiality/data; (6) settlement/termination/exit; (7) contact window/update date. The public page explains "scope, principles, process, roles, boundaries" and does not publish specific provider names/contacts, prices/quotes, SLA penalties, contract terms, data/system details, customer information or undisclosed disputes. The English page should use consistent terms (service procurement, business outsourcing, contractor, SOW, SLA, deliverable, acceptance, subcontracting, confidentiality, data processing, termination/transition) and state the cut-off date.
Do not turn the service page into "we can do everything", and do not claim "100% service levels/zero risk/lowest price" if it cannot be proven. The page should let suppliers and internal teams judge "what can be outsourced, how to select, how to accept, how to exit", without exposing price, data and customer information.
Go-live acceptance checklist
Ten checks: service list/boundary; major/general and approval; contractor qualifications/personnel; competition/pricing; contract/SOW/SLA; deliverables/acceptance criteria/certificate; performance/SLA/exceptions; subcontracting/confidentiality/data; settlement/termination/claims/exit; public boundary. Each needs evidence and a review date. The pass standard is not "the page says professional services", but that business/procurement/finance/legal/quality can judge whether to outsource, whom to select, how to accept, what to do when service levels are missed and how to exit.
Before go-live, run a tabletop exercise with a real (redacted) service: demand → outsourcing decision → contractor selection → pricing → contract/SOW/SLA → performance → acceptance → settlement → missed SLA/remediation → termination/exit, simulating "core business outsourced", "undisclosed subcontracting", "missed SLA" and "acceptance based only on a report", to see whether the page and process work.
| Check | Pass standard | Evidence | If failed |
|---|---|---|---|
| Service/boundary | List, core/non-core, rationale | List/assessment | Add boundary |
| Classification/approval | Major/general, board/management | Policy/resolution | Add approval |
| Contractor | Entity/scope/office/qualification/personnel/experience | Certificate/CV | Add qualification |
| Competition/pricing | Tender/comparison, cost-benefit, no bribery | Record | Add comparison |
| Contract/SOW/SLA | Content/standards/confidentiality/settlement/breach/subcontracting | Contract | Add terms |
| Acceptance | Deliverables/criteria/evidence/certificate | Acceptance sheet | Add acceptance |
| Performance/data | Assessment/SLA/exceptions/subcontracting/confidentiality/data | Report/agreement | Add monitoring |
| Settlement | Acceptance/volume/credits/invoice/prepayment | Document | Reconcile |
| Termination/exit | Breach/claims/handover/account closure/archive | Record | Add exit |
| Public boundary | No provider/price/penalty/data | Page/permissions | Take down |
The acceptance list is editorial; company outsourcing policy, contracts, SOW/SLA and audit requirements control.
Who should read it, who should not, and what decisions does it support?
For procurement, business, IT, finance, legal, quality, EHS and website teams at equipment, electronics, automotive-parts, medical-device, hardware, chemical, packaging and export manufacturers in Changzhou and nearby; also for companies handling "core business outsourced, contractor qualifications unchecked, price without basis, missing SOW/SLA, acceptance based only on a report, no one manages subcontracting/data/confidentiality, no transition on termination". Not for teams without service procurement/outsourcing, or that want one page to replace legal/outsourcing-audit advice.
Read it if: building a service/outsourcing page; only "professional services, long-term cooperation"; core business outsourced; no classification/approval; unqualified contractor; no comparison; contract lacks service standards; SOW/SLA missing; acceptance only a report; subcontracting undisclosed; no data agreement; no transition. Not suitable if: treating "service procurement" as "goods procurement"; "outsourcing" as "manage nothing"; "SLA" as "a slogan"; "page" as "contract/audit conclusion". Supports: scope/boundary, contractor/pricing, SOW/SLA/acceptance, performance/data, termination/exit and public-boundary self-checks.
FAQ
What is the difference between service procurement and goods procurement?
Goods procurement centres on physical specification/quantity/delivery/acceptance; service procurement centres on scope, deliverables, service levels, personnel/qualifications, process evidence and acceptance. Many services have no physical item, so SOW/SLA, tickets/logs/sampling/user confirmation are needed to prove performance. Service procurement still follows authority, pricing, contract, acceptance and payment, but cannot be managed only by "goods receipt".
Which services are suitable for outsourcing, and which are not?
Guideline No. 13 lists R&D, credit investigation, feasibility study, toll processing, property management, customer service, IT services, etc., and requires major/general classification, weighing pros and cons, and avoiding core-business outsourcing. The decision depends on whether it is core business/technology/data, impact on qualification/compliance/safety/customers, reversibility/alternatives, cost-benefit, data/confidentiality and interruption risk; there is no universal list, so each company must set its boundary by strategy and risk.
How do SOW and SLA differ?
SOW (statement of work) states "what to do": scope, objectives, work content, deliverables, time/milestones, location, interfaces, assumptions/exclusions, standards, acceptance method and change process. SLA (service level agreement) states "how well": response/recovery/availability/accuracy/complaint handling/reporting metrics, measurement method, data source, measurement period and remedies. They usually work together and cannot replace each other.
How is a service accepted when there is no physical item?
Accept by deliverable/milestone/service period: check deliverable quantity/quality/format/version, SLA metrics/tickets/logs/sampling/user confirmation, and compliance/data/confidentiality requirements; issue an acceptance certificate and report/handle exceptions immediately. Do not rely only on the provider's self-reported report; critical services need verifiable source records and user/business confirmation.
Which pricing models exist for services, and how to choose?
Common: fixed price/milestone, time and materials (hours × rate), person-month/on-site, per-volume/per-transaction, subscription/retainer, outcome/savings share. Choose based on scope certainty, work measurability, quality/timeliness incentives, budget control and audit evidence; fixed price suits clear scope, time/volume suits variable demand but needs timesheet/ticket evidence, outcome-based needs baseline/attribution/cap. Whatever the model, compare/cost-benefit, and state settlement and change clearly.
How should subcontracting/data/confidentiality in service outsourcing be managed?
The contract should state whether subcontracting is allowed, approval, subcontractor qualifications, joint liability and data/security requirements; do not assume subcontracting. Confidentiality requires an NDA, limited access, personnel notice and exit recovery; data requires classification, minimisation, storage location, cross-border, deletion/return and incident notification; personal information/important data follows applicable law. Subcontractors should bear equivalent confidentiality/data obligations, and the company should keep a subcontractor list and audit rights.
Should the website publish provider names, prices and SLAs?
Usually not specific provider names/contacts, prices/quotes, SLA penalties, contract terms, data/system details, customer information or undisclosed disputes; it can publish service scope/categories, outsourcing principles, contractor requirements, SOW/SLA/acceptance process, contact window and update date. The goal is to let suppliers understand "how to work together", not to disclose price, data and customer positions.
One-sentence takeaway
The service-procurement/business-outsourcing page on a Changzhou manufacturer's website is not about "professional services, long-term cooperation"; it is about turning service scope/core boundary, major/general and approval, contractor qualifications/personnel, competition/pricing, contract/SOW/SLA, deliverables/acceptance criteria/certificate, performance/SLA/exceptions, subcontracting/confidentiality/data, settlement/termination/claims/exit and public boundaries into a checkable list, so business/procurement/finance/legal/quality can judge whether to outsource, whom to select, how to accept, what to do when service levels are missed and how to exit.
Research method and limitations
This article is a summary of public rules and page method, not legal, procurement or outsourcing-audit advice. It uses no unpublished company provider lists, prices/quotes, contract terms, SLA penalties, data/system details, customer information or undisclosed disputes; the tables and acceptance items are editorial and not legal/procurement/outsourcing-audit conclusions. MOF Internal Control Application Guideline No. 13 (Business Outsourcing), No. 7 (Procurement) and No. 16 (Contract Management) are public sources; company outsourcing policy, contracts, SOW/SLA, data-protection and security requirements control. This article does not decide whether any specific service is suitable for outsourcing, and does not promise "zero risk/100% service levels"; companies should set them item by item based on strategy, service, contractor, data and contract.
Sources and basis
Current to 2026-11-09; the official pages below control.
- MOF Internal Control Application Guideline No. 13 — Business Outsourcing (Cai Kuai [2010] No. 11): Linyi Finance Bureau. Outsourcing classification/scope/risks, avoiding core-business outsourcing, contractor selection/qualification/competition/pricing/contract/confidentiality, performance monitoring/contingency, continuous evaluation/termination/claims, acceptance certificate; explicitly excludes engineering-project outsourcing.
- MOF Internal Control Application Guideline No. 7 — Procurement (Cai Kuai [2010] No. 11): Linyi Finance Bureau. Sourcing methods, pricing, contract, acceptance, payment and records; applies to the procurement stage of services.
- MOF Internal Control Application Guideline No. 16 — Contract Management (Cai Kuai [2010] No. 11): Linyi Finance Bureau. Written contracts, term review, signature within authority, performance monitoring, change/termination, dispute handling, registration/archive and annual evaluation.