An individual interpretation from the Chief Labour Inspector (GIP) looks like cheap insurance for an engagement model. You file the request under Article 14b(1) of the Act on the National Labour Inspectorate, as in force since 8 July 2026. The fee is PLN 40 for each factual state you describe. The decision comes within 30 days of a complete request. And it binds the PIP authorities. So much for the theory. Nine decisions from the summer of 2026 show that the maths is more complex.
Three recipients instead of one
The distribution list of every one of the nine published decisions names three parties. The applicant. The Social Insurance Institution, ZUS. And the National Revenue Administration, KAS. That is true of favourable decisions and it is true of negative ones.
The effect is simple. You file a request and you disclose your model to three agencies at once. If GIP finds your position wrong, ZUS receives a document in which a state authority describes your contract and states that it is employment under Article 22 § 1 of the Labour Code. The negative decisions carry long reasoning. They point to specific clauses of specific terms and contracts. For ZUS that is a ready case file on contributions.
GIP also reserves, in every decision, that an interpretation does not rule out an inspection. If an inspection finds facts different from those in the request, the authority will judge for itself. So says Article 14b(5) of the Act.
Protection covers the description, not the company
The interpretation binds the PIP authorities. It can be changed or revoked only if the circumstances of the case change, so says Article 14b(17). It does not bind you. But if you comply with it, it shields you from sanctions within its scope. And here is the catch. The protection covers only the facts you yourself described.
You can see this in the decision of 11 August 2026 on cooperation with self-employed sole traders. GIP found the firm’s position correct. But it wrote two conditions into the reasoning. First, the described setup is not employment provided the described conditions are kept. Second concerns the consultations foreseen in the contract. They will not amount to subordination as long as, in practice, they do not turn into binding orders.
These are not flourishes. These are conditions the protection depends on. Practice drifts from the description and the protection goes out. You are left with a document that has described your model to those with an interest in attacking it.
Favourable reasoning is thin
Compare the depth of the rulings.
The decision on B2B contractors at an IT company came on 29 July 2026. The request described two factual states. A framework agreement, work orders, billing models, contractual penalties, ISO 9001 and ISO/IEC 27001 requirements, and separately the services of a project manager. The general part on the features of employment runs for several pages. And the assessment of this specific model fits in one paragraph.
The negative decisions look the opposite. The decision on the bakery students argues with every point the firm made, one by one. Separately on declaring availability, separately on setting tasks, separately on irregular work and the intent of the parties.
The practical conclusion: a favourable interpretation confirms your description, it does not test your practice. It is worth as much as the description you filed.
An appeal costs more than the request
The decision can be appealed to a regional court. Jurisdiction follows the place of residence or seat of the appellant, Article 461 § 12 and § 24 of the Code of Civil Procedure. You file the appeal in writing through GIP, ul. Barska 28/30, Warsaw, within one month of service, Article 4777j of the same code. There is no cassation complaint in these cases.
The court fee is fixed at PLN 200. The same fee applies to a further appeal and to a complaint against a final ruling as unlawful, Article 36a of the Act on court costs.
A month is not much. Least of all when a negative decision takes the firm by surprise. The appeal scenario is better prepared before the request, not after the decision.
When a request makes sense
A request makes sense when the model has been audited and you know that practice matches the paperwork. Then the interpretation does what it was made for. It removes uncertainty towards PIP and gives you an argument for an inspection.
A request also makes sense before a change of model, when you want the structure checked before rollout. Five of the nine requests concerned future arrangements. Two of them won.
A request is risky, on the other hand, when you file it out of doubt and hope the authority will resolve the doubt your way. Then you risk one thing. You will document a doubtful model to ZUS and KAS. And a description cannot be taken back.
A separate note on clauses that GIP struck down despite correct form. A sham substitution clause hurt more than it helped, because it gave the authority a point of attack. And paying part of the fee for a cancelled task, meant as fair play towards contractors, was read as the employer’s risk.
Practice first, then the request
First, an audit of practice. Talks with the people who organise the work. A check of how the schedule really comes about and who sets the scope of tasks on a working day. And whether substitution has ever worked.
Then fixes, if the audit shows a gap. Changing the contract alone does not work. Article 22 § 11 of the Labour Code says it plainly. Work under the conditions of § 1 is employment regardless of the name of the contract.
The request comes last, if it is still needed. The description of the facts decides everything. And you write it once.
The decisions themselves, and the rules that flow from them, are covered in our text on the nine interpretation decisions of the Chief Labour Inspector.
The above text is for information purposes and does not constitute legal advice in an individual matter. Assessment of specific cooperation requires an analysis of the contract’s content and the actual conditions of its performance.