Skip to content

Systems and records

International dataset policy conflict: global policy vs local procedure

By SourceX Editorial · Reviewed by Noah Loul ·

10 sections

Short answer

Do not merge them. Keep the group policy and the local procedure as separate records, each tagged with its issuing entity, scope, effective dates, original language and the outside authority it relies on. Then label the expected answer per jurisdiction using the company's own precedence clause and any local law it defers to. A policy authority task brief makes that traceable, and a specialist confirms every conflict that turns on law.

Countries and languages

International dataset policy

This page covers international dataset policy conflict: global policy vs local procedure.Illustrative

Key takeaways

  • A conflict between a group policy and a country procedure is information, not noise; flattening it into one rule teaches a model to give the wrong answer somewhere.
  • Local procedures often diverge for lawful reasons, such as national employment data rules or works council rights, so the local version may be the one that governs.
  • Every record needs its authority level, issuing entity, scope, effective dates, original language, translation status and the precedence clause that decides between documents.
  • Language tags, date formats, measurement systems and time zones can each reverse the expected answer if they are assumed rather than recorded.
  • The expected answer to a conflict task is often to route the question or to state the condition, not to pick one document's rule.
  • Conflicts that turn on law, collective agreements or translations need a qualified reviewer before they become labels.

How should training data represent conflicts between global policy and local procedure?

As two separate, fully attributed documents plus a labeled resolution. The group policy keeps its own record and the local procedure keeps its own, each with the entity that issued it, where and to whom it applies, when it took effect, which language it was written in and what outside authority it cites. The task built on top of them states which document governs for a given person, place and date, and why.

The resolution should come from the company's own rules, not the annotator's judgment. Most group policies contain a precedence or local-law clause, and most local procedures cite the statute, collective agreement or regulator that requires them to differ. Quote those clauses into the record. When neither document says which wins, the correct label is that the conflict is unresolved and the question goes to the policy owner.

This matters for any model that will answer staff questions, check compliance or act inside workflows across countries. A model trained on a merged rule will be confidently right in one country and confidently wrong in another, and nothing in the training data will tell it which is which.

Why does a single merged rule teach the wrong behavior?

Because it deletes the very facts the model needs to decide. When a data team cleans a policy library, the tempting move is to keep the newest or the most general document and drop the local variants as duplicates. The result reads well and contradicts itself only in the cases that matter.

Three things are lost. First, scope: the model no longer knows that a rule applies to one legal entity and not another. Second, authority: it cannot tell a binding procedure from a convenience summary. Third, timing: it cannot tell which version was in force on the date of the question. A useful policy dataset keeps all three, and keeps the disagreement visible.

Keeping the conflict also gives the model something valuable to learn: the habit of asking which entity, which date and which document before answering. Evaluation sets built this way can test exactly that, by pairing the same question with different entities or dates and checking that the answer changes when, and only when, the governing document does. A merged library cannot support that test at all.

Where do local procedures legitimately depart from group policy?

Wherever national law or a local agreement requires it, which is common in employment and data handling. The EU's General Data Protection Regulation, in Article 88, allows Member States, by law or by collective agreements, to set more specific rules for processing employees' personal data, with particular attention to monitoring systems at the workplace. A group-wide rule on employee data can therefore meet a stricter or more detailed national rule.

Germany's Works Constitution Act is a clear example. Section 87(1) no. 6 gives the works council a co-determination right over the introduction and use of technical devices designed to monitor employees' behavior or performance, insofar as legislation or a collective agreement does not already settle the matter. A German site procedure that delays a monitoring tool until an agreement is in place is not a local deviation to be cleaned away; it reflects a legal requirement.

International guidance points the same way. The OECD Guidelines for Multinational Enterprises state that obeying domestic laws is the first obligation of enterprises, and that where domestic law conflicts with the Guidelines' principles, enterprises should honor those principles to the fullest extent that does not violate domestic law. Many group policies are written with that hierarchy in mind, which is why their local-law clauses must be captured rather than ignored.

The policy authority task brief

Complete one brief per document involved in a conflict, then one task record that links them. The example values are illustrative. A reviewer qualified in the relevant jurisdiction signs the precedence and external authority fields.

The policy authority task brief
FieldWhat to recordIllustrative valueWhy it can change the answer
Document ID and versionStable ID, version number, link to the prior versionGRP-IT-014 v3; LOC-DE-IT-007 v2Tasks must cite the exact version in force, not the latest one
Issuing entity and levelLegal entity, function and authority level (group, region, country, site)Group IT; German operating company, site ITPrecedence clauses usually rank by level
ScopeEntities, countries, employee groups and systems coveredAll group laptops; German entity employees onlyA rule only governs the people and systems in its scope
Effective and superseded datesFull dates with time zone where timing mattersEffective 2026-03-02; superseded blankQuestions dated before a change take the old answer
Original language and translationLanguage tag of the original, IDs of translations, which version is bindingOriginal de-DE; en-GB convenience translationA translation may soften or lose a condition
Units and locale conventionsDate format, measurement system, currency code, number formatDates written day-first; metric03/04 and similar strings read differently by locale
Precedence clauseExact text of the clause that ranks this document against othersLocal law and works agreements prevail over this policyDecides which document wins when both apply
External authorityStatute, regulation, collective or works agreement the document relies onWorks Constitution Act section 87(1) no. 6Shows the divergence is required, not optional
Expected task answerThe answer per jurisdiction, or the routing step when unresolvedGermany: not before the works agreement; elsewhere: per group rolloutThis is the label the model learns
Reviewer and dateName or role of the qualified reviewer and review dateEmployment counsel, DE; 2026-10-18Labels that depend on law expire when the law changes

Which kind of conflict calls for which expected answer?

Classify each disagreement before writing the label. The type determines whether the task's correct answer is a rule, a condition or a referral.

Which kind of conflict calls for which expected answer?
Conflict typeIllustrative patternExpected task answer
Local law requires moreGroup says roll out now; country requires an agreement or notice firstApply the local requirement in that country and cite it; group rule elsewhere
Local procedure is looser than group policySite skips a group approval step without a cited legal basisGroup policy governs; flag the procedure as a compliance gap, do not train on it as correct
Different method, same goalDifferent form, system or approver for the same controlFollow the local method in scope; both are correct where they apply
Version lagLocal procedure still references a superseded group versionAnswer from the version in force on the question date; flag the stale reference
Translation divergenceTranslated text drops a condition present in the originalUse the binding language version; record the gap
Silent conflictNeither document has a precedence clause covering the caseDo not pick a winner; route to the named policy owner

Could a locale tag, date string or employing entity flip which document governs?

Any of them, which is why each is recorded rather than inferred. Language first: BCP 47 language tags combine a language subtag with optional subtags such as a region drawn from ISO 3166-1 codes, so en-GB and en-US, or de-DE and de-AT, can be told apart. A policy written in de-DE and translated into en-GB has two texts, and only one is binding.

Dates and units next. Unicode's CLDR locale data includes each locale's date and time formats and its measurement system as metric, UK or US. A deadline written as 03/04 or a threshold written in miles means different things depending on the locale that produced it, so normalize to an unambiguous form in the record and keep the original string alongside it.

Jurisdiction is the assumption most often missed. The governing rule depends on which legal entity employs the person or owns the process, not on where the question was typed or which office the policy author sits in. Record the entity on every task, and treat a task with no entity as incomplete.

How do you keep originals, translations and dates traceable?

Give every text a stable ID, link translations to their originals and store dates with offsets. The XLIFF 2.1 standard is a useful model even if you never use the format: it pairs source and target content segment by segment and declares the source and target languages for the file, so any translated sentence can be traced to the original sentence it renders.

For dates, RFC 3339 defines a profile of ISO 8601 in which every time carries a stated offset from Coordinated Universal Time. Effective dates usually need only the calendar date, but rollout cutoffs, approval deadlines and event logs that decide which version applied need the time and the offset.

Finally, keep superseded versions. A question dated last year should be answered by last year's procedure, and that is impossible if the library holds only the current text.

Worked case (illustrative): an endpoint monitoring rollout meets a German site procedure

This case is hypothetical. A group IT policy, written in English, says an endpoint activity monitoring agent will be installed on all company laptops from a set date and contains a clause that local law and works agreements prevail. The German operating company's IT procedure, written in German with an English convenience translation, says no monitoring tool may be activated for its employees until a works agreement has been concluded, citing section 87(1) no. 6 of the Works Constitution Act.

The task: an employee of the German entity asks, on a given date, whether the agent will run on their laptop next week. The expected answer is not yes or no. It is that, for this entity, activation waits for the works agreement, so the employee should check with local HR or IT on its status. For an employee of the group's U.S. entity on the same date, the expected answer follows the group rollout.

The exception: the English convenience translation of the German procedure says the tool will be introduced after consultation, which is weaker than the German original's requirement of a concluded agreement. Because the brief records the original as binding, the label follows the German text and the translation gap is logged for the policy owner.

The limit: the brief records what the company's documents say and which outside authority they cite. It does not decide whether the company's works agreement is valid or complete. That is a legal question for counsel in that jurisdiction.

Which conflicts need counsel or a localization specialist before labeling?

Stop and get a qualified reviewer when the expected answer depends on interpreting a statute, a collective or works agreement or a regulator's guidance; when the binding language version is not stated; when the documents' precedence clauses contradict each other; or when a label would tell people that a legally required step can be skipped.

Narrow the scope rather than guess when the library spans jurisdictions nobody on the team can review, when entity assignments for staff are missing, or when version histories are incomplete. A smaller set of conflicts with verified labels is worth more than a large set with plausible ones.

Policy libraries from international companies and SourceX review

Policies and procedures can be valuable training material precisely because real companies have to reconcile them. Before any of that material is licensed, the rights and privacy questions are reviewed separately from the authority mapping described here.

SourceX works with U.S., Canadian and EU companies that had 50 or more full-time employees at their peak, contractors excluded, and can consider companies in the UK, Australia, New Zealand, India, Singapore, South Africa, Latin America, the UAE and Saudi Arabia when at least 90% of the offered data is English. For those companies the English share is measured on the records actually offered, not on the group's working language, which matters for a library where German originals sit beside English convenience translations. Each dataset still goes through rights, privacy, quality and buyer-fit review, and a brief company assessment, with no records uploaded, is how a group learns whether it qualifies.

Frequently asked questions

Does local law always override a company's global policy?

Not automatically, but a company cannot lawfully follow a group rule that breaks domestic law, and the OECD Guidelines call obeying domestic laws the first obligation of enterprises. Many group policies say so in a local-law clause. Where local law sets a stricter requirement, the local procedure usually governs in that country.

Should training data include local procedures that contradict group policy?

Yes, with their authority and scope recorded. Dropping them teaches a model a rule that is wrong in some jurisdictions. A local procedure that is looser than group policy without a legal basis should be labeled as a compliance gap rather than as correct behavior.

Which version is authoritative when a policy is translated?

The one the company designates, which is usually the original language version unless the policy says otherwise. Record the binding version in each brief and link translations to it. When a translation drops a condition, the label follows the binding text.

How do you label a conflict that neither document resolves?

Label it as unresolved and make the expected answer a referral to the named policy owner. Guessing a winner trains the model to invent precedence. Track these cases so the company can add a precedence clause.

Why record time zones on policy effective dates?

Because a rollout cutoff, deadline or approval logged near midnight can fall on different dates in different offices. Recording the offset, as RFC 3339 does, makes it clear which version was in force for each event.

Sources

  • GDPR Article 88 lets Member States, by law or collective agreements, set more specific rules for employee data processing, with attention to workplace monitoring systems. Source
  • Germany's Works Constitution Act gives works councils co-determination over introducing and using technical devices designed to monitor employees. Source
  • The OECD Guidelines say obeying domestic laws is the first obligation of enterprises and principles should be honored as far as domestic law allows. Source
  • BCP 47 language tags combine a language subtag with optional region subtags based on ISO 3166-1 codes. Source
  • XLIFF 2.1 pairs source and target segments and declares source and target languages. Source
  • CLDR locale data includes measurement system (metric, UK, US) and date and time formats. Source
  • RFC 3339 profiles ISO 8601 so that every time has a stated offset from UTC. Source

See if your company qualifies

A short company assessment. No data uploads are needed.

See if your company qualifies