Choose a method
Start from a task: verify, compare, document or decide.
Search
A single starting point to find the method, source or situation relevant to your question.
Find a method for your taskAll words must match, regardless of case or accents. Search stays in the selected language.
From two characters: use arrows to choose, Enter to open, Escape to close. You can also submit the full search.
Choose limited scope and an isolated environment. Define test data, expected outcome and differences to record; verify recovery before considering a switchover.
Compare consequences for the priority journey and affected users. Document the reproducible obstacle, then examine effort and dependencies; appearance alone does not establish order.
Replay the case that exposed it, a neighbouring case and shared components. Close the issue only when the expected outcome is observable and remaining limitations are named.
Name a decision owner for the relevant scope and the contributors to consult. Present options, effects and expected criteria; record the decision or precise reason for deferral.
Describe its difference from agreed scope. Examine workload, dependencies and expected outcome, then decide on inclusion, substitution or deferral before changing commitments.
Provide a useful answer or a clearly described link to the appropriate guide. Keep the offer identifiable and suggest contact when assistance becomes relevant.
Define the useful expected action and check its accessibility on the page. Compare queries, visits and observable next steps; more visits do not prove the question was answered.
First show each series’ composition. If needs differ, retain separate results or rerun a common series; a raw difference alone does not measure improvement.
Date the change and identify affected series. Keep answers and observed conditions, flag the break and rerun a common subset if comparison remains necessary.
Start from the observed obstacle. A missing answer calls for content work; an unusable journey calls for interface work. Discuss automation once the task and its checks are stable.
Describe the question, affected audience, a specific page or case, known constraints and expected decision. These support an initial scope rather than a default bundle of services.
Keep a number attached to its register and jurisdiction. BRIS supports searches across registers; a similar name or number is insufficient for matching.
TMview brings together participating offices’ information. Tie an absence to the name, filters and scope actually searched.
Notice types describe different stages. In the system explained by GOV.UK, UK1 announces a pipeline and UK4 signals an opportunity to tender.
DesignView provides information from participating registers. Visual similarity does not replace the identifier and record review.
The record describes a dataset and its resources. Its publication date alone does not date the observations within a resource.
Read a percentage with its definition, education level and population. The same symbol does not make two indicators comparable.
The library provides reports from different institutions. Distinguish portal, report author and commissioning body before attributing a recommendation.
The EBA list reproduces information supplied by competent authorities. For a current conclusion, link identity to activity, country and the relevant authority’s register.
Fictional example: old and current addresses share an identifier. Check the recorded change instead of creating a second actor.
Fictional example: a Monday notice corrected on Thursday may describe one event; counting two operations distorts the timeline.
In a fictional dossier, 120 covers twelve months and 30 three months. The difference does not establish a 75% annual revenue fall.
Two fictional companies have similar names. An account's company number belongs to the second; attributing it to the first confuses entities.
Fictional example: a technical failure precedes a valid result. Keep two consultations without turning the first into historical invalidity.
Start from a task: verify, compare, document or decide.
Examine the origin, date, scope and limits of information.
Find definitions before applying a protocol.
DEEPER READING / PRACTICE
A query produces several close results. Reading should help to distinguish the need definition folder, detailed method and implementation tool.
Updated on .
Formulate a specific need and then try neighboring terms. Read the descriptions and select the type of resource according to the searched step: understand, run or control.
The first result is not always the best document to the context. An absence can come from the vocabulary used rather than a lack of content.
A short route connects a need definition page, a guide and a checklist. Maintaining unresolved questions helps to rebuild research.
PRACTICAL CASE / WORKED EXAMPLE
The following case illustrates an approach to defining the need. Situations are pedagogical: they serve to examine the choices and conditions of success, without describing a fulfilled mission or announcing a guaranteed result.
A reader is looking for how to check a number, while the resources use the word indicator. The results must allow to continue despite a different formulation of the title.
Try the neighboring terms and read the descriptions. Differentiate methods of calculation, comparison and verification of sources. Choose the resource that corresponds to the actually sought-by-step.
Research becomes a path of solution. The questions still open serve to clarify the next query instead of multiplying the words without clear intention.
Keep the starting question and then specify the object, operation and resource type. Useful results give a complementary vocabulary, but their title should not automatically replace the reader's target.
DETAILED WORKSHOP / APPLICATION
Describe the initial question and the desired result. Identify the object, operation and type of resource that could help: file, method or tool.
Try a formulation and read the descriptions. Release the useful terms and test the variants without giving up the intention. Compare the resources found according to their contribution to the route.
If the results are close but too general, specify the operation or scope. A well-classed page is not necessarily the one that meets the searched step.
Research is useful when it leads to a resource whose response can be identified. Open questions are used to prepare for the next consultation.
Keep a short track with request, resource and supplement. The reader can restart his work without repaired the tests that have led to useful content.
ANNOTATED WORKING DOCUMENT / REVIEW GRID
The note retains question, tried formulations, useful results and next resource. It distinguishes the exploration vocabulary from the initial goal of the reader.
On a small screen, scroll the grid horizontally to read all three columns.
| Observation | Supported interpretation | Next step |
|---|---|---|
| A resource responds to the desired operation. | The result can serve as a useful step in the course. | Keep the passage and choose the necessary supplement. |
| The results remain general despite the good topic. | The request must specify action, object or scope. | Try an appropriate formulation without losing the initial question. |
| The first result has the word but not the answer. | The presence of the term does not prove its relevance. | Read the descriptions and compare the contribution of resources. |
The final verification verifies that each step reduces an open question. A link list is not yet a useful path if the reader cannot explain what each page brings.
REPORTING / EXAMPLE WORDING
A search result must be judged according to its contribution to the searched operation.
Check that the track keeps the initial question despite the vocabulary variants.
The resource selected meets the described stage of the need. The questions still open guidelines the next consultation and remain distinct from the answer found.