Engineer Outsourcing Reality: SES vs. Contract vs. Quasi-Mandate

Misunderstanding and abuse of contract types in engineer outsourcing is causing serious labor problems.

Mr. A (frontend engineer, 28) accepted a "lump-sum contract" for web application development, but was actually required to work 9 AM to 6 PM at the client company's office, receiving detailed instructions from supervisors. While the contract stated he bore "responsibility for deliverable completion" as contract work, the reality was indistinguishable from being an employee. However, he received no overtime pay or social insurance, and when the project was delayed, he was told "as contract work, you're responsible until completion" and required to continue working without additional compensation.

Ms. B (infrastructure engineer, 35) worked in data center operations under an SES contract (System Engineering Service), but her contract was labeled "quasi-mandate." While quasi-mandate should only require fulfilling good faith management duties without being held responsible for outcomes, during system failures she was pressured to "take responsibility as SES" and pay damages. With ambiguous contract types and actual responsibility scope, she suffered unilateral disadvantages during troubles.

Such cases persist due to structural problems where engineer outsourcing contract type selection is done carelessly, and ordering parties interpret contract content to their advantage. The interests of freelance engineers who sign contracts without properly understanding SES contract work differences and companies using outsourcing as labor law loopholes don't align, creating a normalized dysfunctional situation.

Freelance engineer contracts should theoretically provide business freedom in exchange for losing employee protections, but reality often becomes the worst combination of "employee-level constraints + business-level responsibilities." Without properly understanding contract types and negotiating appropriate conditions based on actual work conditions, even skilled engineers cannot escape situations where they bear economic and legal risks unilaterally.

The three major contract types in engineer outsourcing show significant gaps between legal framework and practical implementation.

SES (System Engineering Service) is legally a type of quasi-mandate contract, but in practice operates similarly to worker dispatch. True quasi-mandate requires "fulfilling good faith management duties to process delegated tasks" without responsibility for specific deliverable completion. However, actual SES contracts often impose outcome responsibilities like "complete system construction by X month."

For example, Mr. C accepted SES contract work for infrastructure construction at 800,000 yen monthly. His contract stated "server environment construction work execution" (quasi-mandate expression), but he was verbally required to "take responsibility until stable production environment operation." The gap between contract documentation and reality made responsibility scope unclear during troubles.

Lump-sum contracts should theoretically pay for "deliverable completion and delivery," but engineer work often has ambiguous deliverable definitions. Even "website creation" lump-sum contracts proceed with unclear details like how many design revisions are included, browser support scope, and how long post-launch bug fixes are covered.

Contradictory "monthly fixed lump-sum contracts" are also widespread. True contract work should be lump-sum payment upon deliverable completion or piece-rate payment, but "contract work with monthly payment" contracts demand work styles identical to monthly salaries. This represents disguised contracts where ordering parties exploit only convenient aspects like "contract work means no overtime pay."

Quasi-mandate contracts are the most misunderstood type. Legally, these involve independent task processing without client supervision, but most practical "quasi-mandate" work involves "on-site work following instructions."

When quasi-mandate contracts specify 160 monthly work hours with mandatory client-site presence, the reality resembles worker dispatch. However, while worker dispatch provides labor law protections (work hour management, occupational safety responsibilities), quasi-mandate contracts lack such protections.

Actual contracts often use ambiguous phrasing like "service agreement (quasi-mandate)" or "service agreement (lump-sum)" to obscure legal characteristics, with clauses allowing interpretation changes as convenient. The same contract might include both "perform work according to Party A's instructions" (employee-like) and "Party B bears good faith management duties" (quasi-mandate-like), allowing ordering parties to switch interpretations situationally.

Avoiding risks specific to each contract type requires countermeasures during pre-contract, execution, and completion phases.

SES Contract Risk Avoidance Procedures

Pre-contract verification should prioritize work scope clarification. Instead of vague expressions like "system development support" or "infrastructure operation assistance," specify technical elements and responsibility areas concretely: "Web application frontend development (using React) for screen implementation and API integration."

For responsibility scope documentation, always include clauses like "Party B bears good faith management duties for delegated work and does not bear deliverable completion responsibility." Even if verbally told to "take responsibility until the end," there's no obligation to comply without contract documentation.

During execution, thoroughly document work instructions. Even when SES contracts involve actual supervision, record instruction content, change history, and additional work scope via email or chat. This provides evidence when later told "we didn't give such instructions" or "this isn't additional work."

Lump-Sum Contract Risk Avoidance Procedures

Deliverable specification confirmation takes highest priority. Beyond general frameworks like "e-commerce site creation," document detailed screen counts, feature lists, supported browsers, responsive design scope, payment functionality specifications, and admin panel feature scope. Also establish specific rates for specification changes: "100,000 yen per additional screen" or "feature additions at 8,000 yen hourly rate × man-hours."

For acceptance criteria clarification, create "operational verification item lists" and agree on which environments, browsers, and verification items constitute acceptance completion. Set objective judgment criteria to prevent acceptance rejection based on subjective reasons like "hard to use" or "different from expectations."

During execution, formalize progress reporting and obtain written agreement when specification changes or additional requests arise. While "minor modifications" often mask major specification changes, always treat changes requiring man-hours as additional contracts.

Quasi-Mandate Contract Risk Avoidance Procedures

Concretely define good faith management duty scope. For "system operation work," specify "weekday 9 AM-6 PM monitoring and primary response to failures." Since requiring "fundamental failure resolution" expands responsibility scope limitlessly, set "escalation (handoff to superiors) criteria."

For work hour limits, determine monthly work hour caps and overtime handling. Instead of vague "target 160 monthly hours with overtime by separate consultation," set concrete conditions like "160 monthly hour limit, overtime at 5,000 yen hourly rate."

Even experienced freelance engineers fall into several common judgment mistakes.

The "long-term contracts provide security" misconception represents the most dangerous trap. Securing 1-year or 2-year contracts creates a sense of stability, but often overlooks contract modification clauses during the term.

For example, Mr. D signed a long-term SES contract worth 10 million yen annually (833,000 yen monthly), but after 6 months was notified of "reduction to 600,000 yen monthly due to project downsizing." The contract's "work content and compensation may be modified through Party A-B consultation" clause enabled unilateral reductions. Even long-term contracts don't guarantee stability without "minimum guaranteed amounts during compensation reduction" and "advance notice periods for contract changes."

Overconfidence that "technical skills enable condition negotiation" also creates problems. Superior engineers tend to focus on technical discussions while postponing detailed contract condition review.

Machine learning engineer Ms. E (12 million yen annual income) became engrossed in technical implementation discussions for an AI development lump-sum contract and failed to confirm intellectual property ownership. The contract assigned patent application rights for developed algorithms to the client, preventing use of technical results in her next projects. Higher-value projects involve more complex rights relationships, making legal condition verification essential alongside technical review.

The naive belief that "verbal agreements work fine with trusted relationships" is also dangerous. Cases of simplifying contract documentation with long-term transaction clients and settling important conditions through verbal agreements are common.

Mr. F, who had 5 years of transaction history with a web development company, started a project with verbal agreement for "usual conditions," but the contact person changed mid-project. The new contact didn't understand past arrangements and insisted "work not in the contract requires additional fees," charging for minor modification work previously provided free.

Missing opportunity costs from "accepting low rates for continued orders" is another common pattern. Accepting low-rate projects for "track record building" or "relationship development" ultimately loses opportunities for appropriate-rate projects.

Ms. G continued 3,000 yen hourly coding work for 6 months expecting "future large project connections," during which she declined 6,000 yen hourly project offers. The expected large project ultimately went to another company, leaving only continued low-rate work. "Future investment" low-rate acceptance should consider opportunity costs (losses from declining better-condition projects).

Securing favorable long-term outsourcing conditions requires negotiation skill enhancement alongside technical skill improvement.

Specific price negotiation methods require quantitative market price understanding as a prerequisite. Collect compensation information for engineers with similar technical skills and experience years performing comparable work from multiple sources. Gather market rates from 3-4 freelance agencies, exchange information with peers, and reference public rates on project sites to set "evidence-based desired rates."

In rate negotiations, demonstrating "technical added value" numerically proves effective. Instead of "3 years React development experience," quantify business contributions: "developed 5 React web applications, improved display speed 40% over previous versions in 3 cases, increased monthly active users 150% in 1 case."

Contract condition negotiation points should include non-compensation condition improvements. Shortening payment cycles (period from billing to payment), extending advance notice periods for contract termination, sharing intellectual property rights, and permitting concurrent projects improve overall working conditions.

Changing monthly-end billing with payment 60 days later to monthly-end billing with payment 30 days later significantly improves cash flow. For an 8 million yen annual income engineer, shortening payment cycles by 30 days provides approximately 670,000 yen cash flow improvement.

Long-term career strategy sometimes requires prioritizing "skill-accumulating projects" over one-time high-rate projects. Projects including elements leading to future rate increases—new technology acquisition, upstream process experience, team leadership experience—justify short-term income reduction.

For example, transitioning from traditional frontend development (700,000 yen monthly) to full-stack development + team management (650,000 yen monthly) creates temporary income reduction, but opens paths to tech lead projects (over 1 million yen monthly) within a year.

Strategic agency utilization approaches strengthen negotiation power through multi-agency relationships. Single agency dependence weakens price negotiation power, so maintain ongoing relationships with 3-4 companies to create competitive project introduction environments.

Understand each agency's strengths (large enterprise projects, startup projects, specific technology domains) and use appropriately based on career goals. Agency commission rates range from 15-30%, so prioritizing lower-commission agencies for equivalent projects enables substantial take-home improvement.

For continuous contract condition improvement, set regular contract review timing. Conduct market price re-research and condition negotiations every 6 months or annually, adjusting to appropriate prices matching skill improvements. Even long-term contracts can secure compensation increases matching market price rises through "semi-annual condition review clauses."

Freelance engineer success depends not only on technical skills but also contract negotiation abilities and long-term strategic planning capabilities. Through appropriate contract type selection, favorable condition negotiations, and continuous condition improvements, it's possible to achieve working arrangements where technical skills receive proper evaluation.