Paste a week's worth of scribbled notes, and TimeNet's natural language engine turns them into clean, categorized time entries. From chicken scratch to billable entries in seconds.
We've all been there. It's Friday afternoon, you've got a yellow pad full of scribbled notes from the week, and 30+ time entries to create before you can go home. With traditional billing software, that's 30 minutes of clicking, tabbing, and typing. With TimeNet Law 6's Bulk Import, it's 10 seconds.
Paste your notes, let the natural language engine parse them, review, and you're done.
Import Entries opens from the File menu, and where you open it from decides what it does.
What pinning actually saves you is the Matter column. A scoped import never asks you to map one, and never asks you to confirm a matter you are already looking at. If you are importing one matter's worth of time, start from that matter and skip the step.
The file type decides the rest. Spreadsheets and CSVs go straight to column mapping. Plain text and RTF are read as natural language, one entry per line. Photographs and PDFs of handwritten timesheets take a different road: see Time Drop, where Oasis reads the handwriting on your Mac before the entries ever reach this window.
Five steps. The whole thing takes longer to explain than to do.
From the menu: File → Bulk Import, or hit ⌘ + Shift + I. The import window opens with a blank text area waiting for your notes.
Type or paste your time entries, one per line. Include a duration, a description of what you did, and the word "for" before the matter name. That's the pattern the parser needs.
TimeNet's natural language engine identifies individual entries, extracts durations, matches clients and matters, and pulls out descriptions. It happens in under a second.
See all parsed entries in a clean table. Color-coded by confidence. Edit any that need tweaks - click any cell to fix it inline.
Hit Import All and every entry is created instantly. They show up in your Launchpad, timesheets, and reports immediately.
One line per entry. The golden rule: use the word "for" or "to" before your matter name. That's how the parser knows where your task description ends and the matter begins.
All of these work:
If you've selected a specific timekeeper in the Import window (not "All Timekeepers"), you can skip the name — it's assigned automatically:
The word "for" (or "to") is the magic keyword. Everything before it becomes the task description. Everything after it is matched against your matters. No keyword, no match — so always include it.
After parsing, you see a preview table with every entry the engine found. Each row shows:
Entries are split into two groups:
Click any cell to edit inline. Fix a matter match, adjust a duration, edit a description — all right in the table.
If an entry shows as invalid, it's almost always because the matter name didn't match. Make sure you're using a recognizable part of the matter name (not just the client name) after "for" or "to".
Same fuzzy matching engine as Quick Capture, but working at scale:
Paste from anywhere. If there's a duration and a client name in there, TimeNet will find it.
You can even select text from a document and paste it directly. The parser doesn't care where it came from - just that there's something to work with.
The Import Entries window gives you two modes depending on what you're working with:
Both modes parse instantly, show you the same preview table, and let you edit inline before importing.
If you have structured data, use CSV mode — it's more predictable. Natural language mode shines when you're dictating entries or typing them from memory, where the "for [matter]" pattern feels natural.
Once imported, entries behave exactly like any other time entry in the system:
Stop dreading Friday afternoon data entry. Scribble notes all week however you want, paste them in on Friday, review the parsed results, hit Import, and go home. Napkin to invoice in 10 seconds. That's the TimeNet Law 6 difference.
Bulk Import is just one way TimeNet Law makes time entry dangerously fast. Check out these related features:
If you've got a note format the parser struggles with, send it over. Perry will either show you a trick or improve the engine.