Methodology
This methodology explains how DryRights turns official sources into structured, understandable material. It exists so a user can judge where information came from, how thoroughly it was verified and how current it is.
1. Source priority
We use sources in the following order:
- the official text of a law or regulation;
- an official government portal;
- the page of the competent public authority;
- an official registry or official form;
- an official instruction from a regional or local authority;
- a court decision from an official registry;
- a secondary source — used only as a lead towards a primary source.
Blogs, forums, social media and commercial advisory sites are not used as sole evidence for a legal statement.
2. Route structure
A practical route may include:
- who it applies to;
- who it does not apply to;
- the current basis for stay or action;
- a critical deadline;
- the competent authority;
- steps;
- documents;
- fees;
- processing time;
- rights while waiting;
- renewal or change of basis;
- refusal and appeal;
- official sources;
- the editorial review date.
3. Regional differences
If a procedure is decentralised, DryRights separately tracks authorities, addresses, contacts, payment accounts and local instructions. In Poland, for example, a route may define the competent authority per one of 16 voivodeships.
4. Editorial review
Before publication an important claim must be:
- linked to a source;
- read in context;
- checked against jurisdiction and date;
- written in plain language;
- labelled with a verification date;
- escalated to a subject-matter reviewer where necessary.
5. Status labels
| Status | Meaning |
|---|---|
| Imported | the record was ingested from a registry but full editorial review is not yet complete |
| Source verified | the reference and provenance have been confirmed |
| Editorially reviewed | the content has been checked by a human reviewer |
| In preparation | the feature or jurisdiction is not yet ready |
| Preview/Beta | the material is available for testing |
| Needs clarification | sources are incomplete or conflicting |
6. Uncertainty
If a rule depends on circumstances, has exceptions or varies in practice, DryRights should not present it as an unconditional guarantee. In such cases the user sees:
- an explanation of the limitation;
- clarifying questions;
- a recommendation to verify the information;
- a link to the competent authority;
- guidance to seek legal help for higher-risk situations.
7. Updates
A "verified" date means the date of the last editorial check of the available source. It does not guarantee the source has not changed since that date.
Routes involving critical deadlines, fees or special temporary rules should receive a higher priority for re-verification.
8. Automation
Automated tools may help to:
- detect changes;
- compare versions;
- prepare structured data;
- flag potential discrepancies;
- check the technical integrity of links.
Final responsibility for publishing legal content remains with a human.
9. Correcting errors
A user can report an error. The report is checked against an official source. If confirmed, the record is updated, and a material change is reflected in the version history.
10. Limits
DryRights provides general legal and procedural information. The platform does not:
- make decisions on behalf of an authority;
- guarantee the outcome of an application;
- establish a user's identity;
- automatically create an attorney-client relationship;
- replace individual legal advice.
Last updated: 7 September 2026