Attended data entry for Windows
ReKey carries structured data into the systems that will not take a file — one field at a time, at the operator's pace, with a person watching every value land.
In development · 2026
There is no integration to build and no project to approve. Someone maps the form once; everybody else runs the map.
A spreadsheet, a CSV, an XML or JSON export, or a table pasted straight out of an email. No file? Paste the table.
An ordered list of the fields, in the form's own words, with the formats the target expects. Authored once, shared with the team.
The next value appears, large, exactly as it will arrive. Press a key and it goes in. Press it again for the next.
Every value is released by a person who can see the value and the form at the same moment. That is not a limitation waiting to be relaxed — it is what lets ReKey be installed where the alternatives cannot go.
Save, Submit and Next are the operator's, always. The engine refuses those keys; they are not merely left out of profiles.
No scheduler, no headless mode, no command line. Every value needs a keypress from someone who can see it.
It cannot store, read or enter them. A field Windows reports as a password field is refused, in code.
No session, no cookie, no token, no API. ReKey does not know what the target is beyond a window title.
Between the spreadsheet and the field sits a chain of small corrections, set once in the profile and applied to every row.
| Correction | What it fixes |
|---|---|
| Dates | Read whatever the export wrote; emit the one format the form accepts. Date formats are the commonest reason a submission comes back. |
| Numbers | Strip the symbols and separators, fix the decimal places, write a negative the way the form wants it. |
| Padding | Restore the leading zeros the spreadsheet ate; pad a reference to its fixed width. |
| Lookups | Translate your codes into the target's — the mapping everyone keeps in a spreadsheet somewhere, made part of the profile. |
| Lengths | Trim to the field's maximum deliberately, rather than letting the form do it silently. |
And every row is checked before the run starts. A bad code or an unreadable date appears in one table you can fix, not at field 8 of row 27 with the first half already submitted.
Four levels, chosen per form and per field. Your IT function can switch the higher ones off for everyone, centrally, and they stay off.
| Level | What a keypress does | Synthetic input |
|---|---|---|
| Queue | Puts the next value on the clipboard. You paste and tab. | None at all |
| Step | Pastes it and moves to the next field. | Two keys |
| Row | Fills a whole row of the form, in order. | Two keys per field |
| Type | Types the value, for the fields that refuse a paste. | One key per character |
The first level uses no synthetic input whatsoever, which means it needs no security argument at all. It is a perfectly good place to stay.
Anywhere the data is structured, the target is a form, and integration is either forbidden or not worth its own project.
RPA solves the adjacent problem by removing the person: it holds credentials, runs to a schedule, clicks and submits, and needs an IT project and a governance case before it can start.
ReKey is the opposite trade. It holds nothing, decides nothing and submits nothing. It is installed by the person who will use it, in an afternoon, and it makes them several times faster at the job they were already doing.
Not yet released
ReKey is in development. If your team spends its days retyping data into a system that will not take a file, we would like to hear which system — it is how we decide what ships first.