What to include
Name the tool and describe the steps that led to the problem. Include the input format, mapped columns, horizontal and vertical units, relevant options, and the result you expected. Quote the error message or identify the original row rather than saying only that the file did not work. For numerical differences, show the expected calculation with enough digits to explain the discrepancy.
A minimal example often needs only two or three points. Use invented coordinates and descriptions when they reproduce the same issue. If the problem depends on a specific spreadsheet sheet, separator, character encoding or DXF object type, mention that detail. Keep an original copy of your source and do not repair it repeatedly before preserving the evidence.
What the report buttons do
Save report as TXT creates a text file on your device. It does not create a support ticket or send a message. Open email draft uses your configured email application and the public address above; you must review and send that draft yourself. Long reports may need to be saved and attached manually because email links have practical length limits.
No original file, screenshot or download is automatically attached. If you decide to include a file, review it first for client names, credentials, confidential coordinates and unrelated worksheets. The typed report remains in the current page and is not saved as a browser preset. Save it before leaving the page if you want to keep it.
Check these references first
The format reference explains column order, delimiters, units and missing fields. The public examples let you determine whether the tool works with a known input. The methodology page describes calculation signs and assumptions. Tool-specific guides cover common reasons a result remains incomplete even when a file opens successfully.
For a file that imports incorrectly in Civil 3D, compare the actual columns with the selected point format and test a few known points. For a design versus measured comparison, confirm the same reference and a valid point pairing before changing the tolerance. Include what you already checked in your report so the investigation starts at the unresolved step.
Feature requests and follow-up
Explain the job you are trying to finish, the input you have and the output the next person or application needs. A sample with a known answer is more useful than a broad request for more features. Related requests can sometimes be solved with an existing tool plus clearer guidance, without introducing another separate workflow.
CogoKit is independently run by an individual, and there is no guaranteed support response time. The public contact address is hi@cogokit.com. You can save a local report first, then decide whether to open an email draft and send it through your own mail application. The privacy notice explains how correspondence is handled.