---
title: "Which approvals must clear before a subcontractor starts?"
description: "Map contract consent, data authorization and access permissions to the named subcontractor, then test the start date and replacement route."
canonical: "https://zephior.com/insights/verify-subcontractor-approval-terms"
last-updated: 2026-09-06
---

# Which approvals must clear before a subcontractor starts?

> Map contract consent, data authorization and access permissions to the named subcontractor, then test the start date and replacement route.

By [Tony Kim](https://zephior.com/authors/tony-kim). Published 2026-09-06; updated 2026-09-06. 17 minute read.

## Definition

A subcontractor approval review establishes which permissions must exist before a named party can be contracted, mobilized or allowed to perform a particular activity. The work product is an approval-and-start record: exact entity and scope, governing provision, required application, decision-maker, timing, decision evidence, residual conditions and replacement triggers. A supplier can satisfy the tender’s eligibility tests while still lacking permission to begin work. The record must say which next action is allowed, rather than reducing every stage to an approved supplier flag.

## Problem

The delivery plan assumes a specialist starts immediately after award. Its name appears in the tender, procurement has accepted its questionnaire and the supplier has reserved staff. The draft contract nevertheless requires separate consent to the subcontract. A processing schedule names another approval owner, while site access depends on checks that have not started. The bid has committed to a date that none of those records supports. Replacing the specialist with its sister company does not remove the problem.

## Point of view

Treat permission as specific to an actor, activity and point in time. This review takes an already defined supplier configuration and examines the approval mechanisms in the proposed contract. It does not repeat the full subcontractor eligibility audit or negotiate every downstream obligation. The legal examples were checked on 6 September 2026 and remain limited to their stated regimes; counsel determines applicability and meaning. Alderfen Instruments, its suppliers and every timing and cost assumption below are fictional. They demonstrate planning decisions, not buyer promises or statutory response times.

## Ask what the permission lets the supplier do

Begin with the actual chain of contracts, not the vendor directory. Record the prime’s legal identity, each proposed subcontracting entity, its immediate contracting counterparty and the precise activities allocated to it. Include lower-tier relationships where the applicable terms reach them. A product vendor, labour provider, consortium member and entity whose capacity supports qualification can trigger different questions. Use the existing eligibility review as an input; do not decide the legal category from the supplier’s preferred label.

For every activity, identify the act that needs permission. The tender may allow the bidder to name a proposed specialist before that specialist has been approved for performance. A later condition may govern signing a subcontract, issuing a purchase order, giving a notice to proceed, processing personal data or entering a controlled site. Treat these as separate gates unless the operative document expressly combines them. A positive answer from one owner cannot be carried across the other gates without evidence.

In the EU public-procurement example, Directive 2014/24/EU Article 63(2) permits certain critical tasks to be reserved to the bidder or a group participant. Article 71 distinguishes tender disclosure from performance-stage information duties. National implementation and the issued documents determine the applicable requirements; neither provision is blanket approval of a named subcontractor.

Alderfen’s proposed field-data specialist would collect measurements, upload identifiable operator records and work at buyer-controlled locations. Its tender declaration names Moorbank Field Services Ltd. The quotation comes from Moorbank Group Ltd. Stop the entity reconciliation there: group membership does not explain which company will sign, perform and receive approval. Keep the quotation as evidence of an unresolved identity issue, not as a replacement for the declared party.

**Separate release questions for Alderfen’s fictional specialist**

| Proposed action | Evidence to identify | Insufficient on its own |
| --- | --- | --- |
| Name the party in the bid | Tender disclosure rule and authorized statement | A listing in the internal vendor system |
| Enter the subcontract | Applicable consent or evidenced exemption for the exact instrument | A supplier’s signed quotation |
| Begin the work package | Performance consent and satisfied commencement conditions | The prime contract award announcement |
| Process operator data | Applicable processing authorization and completed prerequisites | A procurement reviewer’s commercial approval |
| Enter a controlled site | Site and person-specific access release | Approval of the subcontracting company |

## The consent clause needs its schedules and exceptions

Collect the tender instructions, draft contract, supplier schedules, security and processing terms, changes and relevant clarifications. Record their version and order of precedence. A clause allowing subcontracting in principle can coexist with a named-party approval requirement elsewhere. Check definitions of key subcontractor, affiliate and material change, any value or scope threshold, exceptions, reserved activities and requirements applying to changes in ownership or control. Preserve an unclear conflict for review instead of selecting the easier clause.

US FAR 52.244-2 makes consent depend on contract and purchasing-system circumstances, clause entries and variants. Required consent is written permission to enter a particular subcontract. Under paragraph (f), it normally neither relieves prime performance responsibility nor determines cost allowability or acceptability of subcontract terms. Check the incorporated version and agency deviations.

Write the operative rule as a source-linked test: identified party, proposed action, trigger, required material, recipient with authority, time rule, decision form and permitted exceptions. Retain any refusal grounds, conditions on consent, withdrawal powers and required response to a buyer objection. A reasonableness qualifier may constrain a decision legally; it does not let the bid team manufacture the missing decision. Counsel should distinguish an enforceable right from a preferred negotiating position.

Check what happens when consent is refused or delayed. Can the prime perform the work itself? Is another party allowed, and must it meet the original evaluated conditions? Does the prime carry the delay and additional cost, or is there a defined relief process? Those questions affect the offer. A reserve in the price cannot purchase permission that the terms prohibit, and an alternative supplier is not a usable contingency until its own route has been tested.

## A complete request is different from a received request

Build a requirements list for each approval application. Depending on the actual rule, it can include legal identity, precise services, subcontract form, price and payment terms, duration, capacity evidence, due-diligence results, processing particulars or proposed access. Mark the source requiring each item. Reuse verified evidence only while its entity, scope and currency remain appropriate. Do not attach a whole supplier file because one certificate is requested.

The French DAJ’s current DC4 notice describes a declaration used to seek acceptance of the subcontractor and approval of its payment terms. The form is optional unless the buyer requires it, and signature treatment differs by stage. This French mechanism must be read in its own context, not treated as generic EU subcontracting consent.

Keep creation, approval for transmission, dispatch, receipt, completeness and decision as separate events. Save the actual package version and the authorized recipient’s acknowledgement. If the buyer asks for a missing annex, record whether the governing rule starts, pauses or restarts a clock; do not choose whichever interpretation preserves the planned start. Distinguish working days from calendar days and record holidays, cut-offs and the event from which counting begins. Without a supported rule, the deadline remains unresolved.

Partner pricing, personal information and commercial relationships may require controlled disclosure. Confirm who is entitled to receive each item and how it is transmitted. If a supplier objects to sharing a required document, seek an authorized restricted route, permitted substitute or buyer clarification. A confidentiality objection is not permission to omit a requirement, and redaction must not remove facts that make the application decidable. Never publish a live supplier dossier as an example.

## Commercial consent may leave data and access blocked

EU GDPR Article 28(2) requires prior specific or general written controller authorization before another processor is engaged. General authorization includes notice of intended additions or replacements and an opportunity to object. It does not itself prescribe a universal notice period. Determine the actual roles, authorization and contract procedure before treating a provider change as cleared.

Map processing and access approvals to the activities that need them. Identify the person authorized to decide for the buyer, not merely the person who received the email. A proposed subprocessor may be acceptable for one service but not another dataset or location. A supplier company’s clearance may leave individual staff, devices and site induction outstanding. Record these limits in the release record so that a valid narrow permission is neither ignored nor overstated.

If the terms use notice and objection rather than affirmative consent, preserve the existing authorization, required notice contents, valid recipient, evidenced receipt, applicable period and any objection. Silence has only the effect established by the governing rule. A missing reply, an out-of-office message or a green portal status cannot settle that legal question. Escalate disputed receipt, incomplete information or an objection; do not run a timer that automatically grants access.

Ask whether any preparatory activity can proceed without crossing a blocked boundary. Training with synthetic data at the supplier’s premises may be a separate permitted task, while a production-data upload is not. Record the authorized preparation scope and its owner. A plan to mobilize at commercial risk must still respect consent requirements; willingness to pay for idle staff does not authorize signing, processing or site entry.

## Model the approval path before promising a start

Use a dependency schedule. For a serial gate, the next activity starts only after its predecessor is complete; parallel gates converge at the latest necessary clearance. Add partner availability, onboarding and any final release review. Label each duration as a contractual rule, agreed service target, observed estimate or assumption. A calculated date remains conditional while the necessary permissions are missing.

In Alderfen’s fictional case, working-day index 0 is the planning origin. All durations below are elapsed working days from that origin, not inclusive calendar counts. The identity issue is assumed resolved before the listed packets become complete. Contract consent, specific processing authorization and site review can run independently. Each needs an affirmative decision. The quoted durations are planning estimates, with no guaranteed response or implied consent. Four further working days of onboarding can start only after all three clearances.

The modeled readiness point is day 25 against a required day 22, leaving a three-day shortfall. If the contract packet moves from day 4 to day 8, its modeled decision moves to day 18; readiness stays at day 25 because processing remains later. If the processing packet instead moves from day 6 to day 10, readiness becomes day 29 and the shortfall becomes seven days. Chasing the first application would not fix that second scenario.

A limited management estimate assumes the prime would retain an otherwise idle team at GBP 2,400 for each delayed working day, plus GBP 1,800 of one-off application rework. That gives GBP 9,000 in the base-delay case and GBP 18,600 in the later-processing case. These are alternative cases, not additive costs. They exclude subcontract price changes, contractual remedies, lost revenue and further delays. Retaining the team or spending the allowance requires its own approval.

The bid cannot describe this supplier as ready for day 22. The owner must establish a permitted earlier application route, revise an allowable dependency, obtain an authorized timetable change or decide that the proposed delivery model cannot support the requirement. Do not accelerate the forecast by deleting a required gate. Even a positive margin would establish planning feasibility only, not present permission.

**Fictional working-day schedule, conditional on affirmative decisions**

| Gate | Complete packet or predecessor | Assumed duration | Modeled completion |
| --- | --- | --- | --- |
| Contract consent | Day 4 | 10 working days | Day 14 |
| Specific processing authorization | Day 6 | 15 working days | Day 21 |
| Site clearance | Day 3 | 8 working days | Day 11 |
| Onboarding after all clearances | Latest clearance: day 21 | 4 working days | Day 25 |
| Later processing packet scenario | Day 10 plus 15, then onboarding | 4 further working days | Day 29 |

## A replacement cannot inherit the old permission

List the changes that reopen the record: a different contracting entity, moved work, additional tier, new site, changed processing, expired consent or an ownership event covered by the clause. Identify what remains valid and what requires a new application. Preserve the old decision and its end of applicability. A changed trading name and a transfer to another legal entity need different evidence; neither should be decided by a similarity match.

Under the UK Procurement Act exclusions guidance, a supplier affected by an excluded or excludable subcontractor must have an opportunity to replace it before exclusion. The replacement is checked, including continued satisfaction of participation conditions. This procedural protection is not an unrestricted right to change an evaluated solution; use the applicable process and legal review.

For an ordinary commercial replacement, read the buyer’s consent process independently of that exclusions example. Record the reason, old and proposed scopes, comparative evidence, revised terms, price effect, transition plan and affected bid claims. If the original supplier supplied a reference, named expert or scored method, send the change back to the eligibility and proposal owners. Do not keep its evidence attached to the replacement’s name.

Alderfen’s sister-company fallback would need an identified instrument, its own approval evidence and a new availability check. If replacement is required during delivery, also plan permitted continuity, information transfer and access termination. Urgency does not create an approval exception unless the governing terms provide one. A new supplier beginning work before clearance can compound the original failure rather than resolve it.

## Hand over a decision that names the next allowed action

Close the record with the tender and contract versions, party and scope, each gate, evidence link, authorized reviewer, decision time, conditions and next review trigger. Use separate states for not applicable with a documented basis, not requested, application incomplete, awaiting decision, conditionally granted, granted for a defined action, refused and superseded. Where a notice mechanism applies, describe its evidenced state rather than forcing it into an affirmative-consent label.

Bid release and operational release are different decisions. If the tender permits post-award approval, the bid can identify the proposed supplier and the unresolved dependency accurately, subject to the required delivery commitment. If it demands approval evidence with the offer, a plan to obtain it later does not satisfy that gate. The permitted clarification or departure process must determine the treatment; an internal approver cannot waive the buyer’s requirement.

The handover should say who will request permission, keep the schedule current, verify the returned instrument and prevent premature work. Link the approved supplier scope to the final offer and contract without exposing protected attachments publicly. Recheck after award because the executed terms, named supplier or mobilization date may differ from the bid assumptions. An approval record that nobody maintains will not control the first purchase order.

An agent can compare authorized documents, identify absent evidence and calculate the disclosed schedule. It must stop on unclear legal effect, unresolved identity, inaccessible evidence or conflicting authority. It may draft a question or release packet for review. It may not contact the buyer or supplier, disclose protected data, sign a subcontract, issue work instructions, grant access or submit the tender without explicit authority for that action.

**Decision evidence limits what can be released**

| Recorded situation | Supported treatment | Action still blocked |
| --- | --- | --- |
| Party only named in tender | Retain it as proposed, if the procedure permits | Claim that all operational permissions exist |
| Complete application received | Track review and model uncertainty | Treat receipt as approval |
| Consent subject to conditions | Record each condition and who confirms it | Start the affected activity before conditions are met |
| Defined action approved | Release only that action through its authorized owner | Extend approval to another entity, site or scope |
| Refusal or material change | Use the permitted resolution or replacement route | Substitute a party or rewrite the approved record silently |

## Useful outcomes

- Each restricted action has a named authority and an identifiable release condition.
- Application completeness, receipt, review and permission are recorded separately.
- The mobilization plan includes serial approvals and work that can run in parallel.
- Replacement, scope and ownership changes reopen the permissions they affect.
- The bid approver can distinguish a permitted future dependency from a false present assurance.

## Workflow

1. **Fix the proposed subcontract and restricted actions.** Identify the legal entity, tier, work package, lot, sites and processing activities. Separate naming the party in a bid, signing its subcontract, starting work and granting access.
2. **Read each approval mechanism.** Extract the incorporated clause, schedule, amendment, authorized decision-maker, required submission and timing rule. Record unresolved precedence or jurisdiction questions for legal review.
3. **Test the application and decision evidence.** Check completeness and authorized receipt. Compare any response with the requested entity, scope, conditions and action; a portal acknowledgement does not close a consent gate.
4. **Calculate the conditional start.** Map dependencies, review estimates, partner availability and onboarding. Test delay and replacement cases without assuming silence or a target review date grants permission.
5. **Approve the bid treatment and handover.** Resolve the gap through the permitted process, retain the exact approved wording and assign post-award checks. Obtain separate authority before contact, disclosure, signing, access changes or submission.

## Key decisions

- Which action is prohibited until which approval exists?
- Does an existing permission cover this entity, activity, site, period and subcontract version?
- What makes the application complete and starts any contractual clock?
- Can the proposed start survive an objection, delayed response or lost supplier slot?
- Which bid statement is supportable now, and which remains conditional?

## Risks

- Tender disclosure is treated as consent to place the subcontract or commence performance.
- An approval belongs to a parent company, another lot or a narrower service.
- A review estimate is scheduled as though it were an enforceable approval deadline.
- A supplier replacement changes the evidence on which the bid was assessed.
- Confidential commercial or personnel records are sent beyond the approved recipient group.

## Metrics

- Restricted activities without verified release evidence
- Approval applications missing a required input or authorized recipient
- Working-day margin between modeled readiness and the promised start
- Material supplier changes awaiting an approval-impact decision

## Frequently asked questions

### Does naming a subcontractor in the tender mean the buyer has approved it?

Only if the applicable mechanism gives that naming and the resulting buyer action that effect. Check the relevant document and stage. Disclosure, consent to enter the subcontract and permission to start a particular activity can be separate requirements.

### Can work start while consent is pending if the prime accepts the cost risk?

Cost ownership does not remove a permission requirement. Determine which preparatory activities are independently allowed and keep prohibited signing, processing, site access or performance on hold until the appropriate gate is cleared.

### Does no reply by the review target date count as consent?

Not without an applicable rule giving silence that effect and evidence that its conditions are satisfied. A service target or planning estimate does not create deemed consent. Refer disputed receipt, completeness, timing or legal effect to the authorized reviewer.

### Can an approved subcontractor use another company in its group?

Check the exact legal entity and the permission’s scope. A separate group company may require a new application and a review of qualification, processing, price and availability. A shared brand is not evidence that the existing approval follows the work.

### What should the bid reviewer receive if post-award approval is allowed?

The proposed entity and scope, source-linked approval requirements, completeness gaps, conditional schedule, delay scenarios and approved bid wording. Name the post-award owners and operational stops. Future approval must not be presented as a fact already established.


## Primary sources

- [Directive 2014/24/EU, Articles 63(2) and 71](https://eur-lex.europa.eu/eli/dir/2014/24/oj/eng), European Union
- [FAR 52.244-2, Subcontracts, basic clause and Alternate I](https://www.acquisition.gov/far/52.244-2), US Federal Acquisition Regulatory Council
- [DC4 explanatory notice, current form guidance linked by DAJ](https://www.economie.gouv.fr/files/files/directions_services/daj/media-document/Notice-DC4-maj20231122.pdf), Direction des Affaires juridiques
- [GDPR, Article 28(2), authorization of another processor](https://eur-lex.europa.eu/eli/reg/2016/679/oj/eng), European Union
- [Procurement Act exclusions guidance, subcontractor replacement](https://www.gov.uk/government/publications/procurement-act-2023-guidance-documents-procure-phase/guidance-exclusions-html), UK Cabinet Office


## Related articles

- [How to verify a subcontractor meets tender conditions](https://zephior.com/insights/verify-subcontractor-tender-compliance)
- [How to coordinate prime and subcontractor bid commitments](https://zephior.com/industries/coordinate-prime-and-subcontractor-bid-commitments)
- [Which data-processing terms change the proposed service?](https://zephior.com/insights/review-a-tender-data-processing-schedule)
- [How to manage tender exceptions and qualifications](https://zephior.com/insights/manage-rfp-exceptions-and-qualifications)