Identify the object and the circumstance to be checked
Intellectual property covers different types of objects, so a single general brief is rarely sufficient. For a technical solution, structural or process features matter; for a sign, its composition and perception; for software, the source materials and versions. Start by identifying exactly what needs to be compared and the context in which the dispute arose.
A useful description identifies two or more specific objects, the relevant period and the subject of doubt. For example, the task may be to compare a device with patent claims, establish the nature of similarities between two mock-ups or identify the contents of transferred source code. An allegation of infringement states a participant's position but does not replace specific examination questions.
Gather relevant documents
A patent examination requires the document number, claims, description and information about the version being checked. For a trademark, the exact image and the goods or services considered are important. For a work or software, source files, published versions and information on how they were obtained are useful. A general folder without explanations makes it difficult to identify the object.
Include contracts, technical specifications, transfer documents and questions separately if they help define the work's boundaries. The specialist needs to know which information was provided by a party, which was extracted from documents and which remains to be established. There is no need to turn a covering letter into a finished report in advance.
Separate versions and specimens
Comparison loses its meaning if photographs relate to one modification, drawings to another and a characteristics table to a third. Label each version, date and source. If a physical product is being examined, state its markings, completeness and available provenance documents. The technical description must relate to that particular specimen.
For a digital project, retain the original archives and create working copies separately. State the repository branch or snapshot, export date and the files excluded. Do not add new modules to an old set without explicitly identifying them: mixing versions can distort the result even when preparation is undertaken in good faith.
Formulate the examination questions
The question ‘who stole the idea?’ does not define a checking method and contains a legal assessment. It is more practical to establish which features are found in the object, which elements coincide, what explains differences and which data are missing. When comparing software, shared libraries, automatically generated elements and the project's own code are considered separately.
It is important to distinguish visual similarity, technical correspondence and legal consequences. The same observed fact may require different additional materials before a further conclusion can be reached. The brief is therefore first refined according to its subject and available methods, rather than a predetermined answer being promised.
Agree the outcome and limitations
Before work begins, define the objects, permissible actions involving them, inspection possibilities and the result format. A complex structure may require additional data or a specialist from the relevant industry. Information searches also have date, database and subject boundaries, which should be described in advance.
A useful report allows the path from an original file or component to a comparison table and conclusion to be traced. It also records circumstances not established. Decisions on registration, infringement, ownership of rights and remedies are made through the appropriate legal procedure, considering the complete body of materials rather than a single technical correspondence.
If the set contains several independent developments, prepare an inventory for each object. In one row, state the version, source, date and related documents. Confidential technical information is transferred to the agreed extent; active passwords and unrelated data are generally unnecessary for comparison. This preparation helps keep the examination focused and avoid accidentally mixing different projects.