A personal injury firm should get help with intake when the incident types and the file's facts are already known and someone still retypes the web form. Hire help when you already know which incident types you take and which facts the file needs, and someone still retypes them because the form does not match the file. The help should map those fields. It should not write a promise about an outcome.
Takeaways
- Hire when staff retype a web form into the file you already designed.
- Bring the incident types and the facts, and treat them as the assignment.
- Map each field on the page to a field in the file.
- Keep outcome language out of the project.
- Judge the work by a note that lands without retyping.
When Retyping Means the Form Is the Project
Retyping means the form is the project when a person on your staff copies the web note into the file by hand. They translate a message box into the kind of incident, the timing, and whether another firm is involved. The caller already typed something. The file needs something else. The gap between those two shapes is the work, and it repeats on every matter that starts online.
You can live with that gap while the volume of notes is small and the person retyping knows the file by heart. It becomes a project when the retyping is the intake, and the page is only a way to collect a name. At that point a new headline about the firm will not shorten the copying. A form that uses the file's fields will.
The Personal Injury page sells the work. This article teaches when intake help is justified, and which promises it must not add. The Legal Services page covers the firm's other doors. This hire is the injury form and the injury file, kept as one list.
Notice who does the retyping and when. If it happens after hours, or between calls, the form is borrowing time from the people who should be reading a finished note. Help is timely when you can point at that copying and at the fields you wish had arrived already filled. If you cannot name the fields, sit with the file first. A builder cannot map a list you have not written.
A closed cream folder rests on a small table next to an empty armchair.
A closed folder waiting by a chair, the intake packet a site and a front desk have to describe the same way.
Which Facts You Should Already Know
You should already know the incident types you take and the facts the file needs before you ask anyone to build. Those are practice decisions. The hire starts after they are stable enough to write down. A firm still arguing about which harms it accepts will get a form that changes every week, and the retyping will return under a new layout.
Bring a list like this.
- Name the incident types you take, in the words the file uses, and mark the types you decline.
- Under each type, list the facts the file has a place for: kind of incident, when it happened, whether another firm is involved, and any other fact you always write down.
- Note which of those facts the web form currently fails to ask, or asks in a story the staff must parse.
- Say where the note should arrive so the person who opens the file sees it without a second copy.
- Write one line the page may say about a response, and exclude every line about an outcome.
Step two is the map's raw material. If the file has a place for the other firm and the form has a message box, that pair is the job. If the file has no place for a fact, decide whether the file should gain it or the form should stop asking. Help can build either change. You choose which.
A public sequence for this help is Initial Contact, Detailed Discussion, and Implementation. Bring the list to Initial Contact. Use Detailed Discussion to match each file field to a question. Use Implementation to stop the retyping, then test with a note you do not edit by hand. A proposal that starts with a new look and mentions the file later has the order backwards.
How the Form Has to Match the File
The form has to match the file field for field, in the same order the staff scan. When the words differ, someone translates, and translation is the retyping you are trying to end. Kind of incident on the page should be kind of incident in the file. Timing should land in timing. The other-firm answer should land where that answer is read first.
| File field | What the form should collect | What causes retyping | What the mapped note shows |
|---|---|---|---|
| Kind of incident | The types you take, plus a short line for another harm | A message that mentions the harm in passing | The type, in the file's words |
| When it happened | A date or a plain description | A story with the timing buried | Timing in its own place |
| Another firm | Yes, no, or not sure, and a name if yes | The fact appearing only if the caller remembers | Counsel status before the call |
| Where the note goes | A destination the file already watches | An inbox nobody copies from | The note opened in the file |
| Response line | That someone will read the facts | A promise about how the matter ends | A conversation, if you can look |
Walk the rows with the person who retypes. Each row they still copy by hand is unfinished. A row they only confirm is done. Do not add fields the file will ignore. Extra questions feel thorough and become another paragraph to skip or to copy into a note labeled other. The map is complete when every required file fact has a home on the form and every form answer has a home in the file.
Choices beat a story for the common types. A story remains available as a short line after the choices, for the harm that does not fit. The staff should see the choice before they see the line. If they see only the line, you have rebuilt the message box and called it a form.
What Help Must Leave Unsaid
Help must leave outcomes unsaid. The assignment is the map of fields. A sentence about what happens to people with this kind of harm, how matters resolve, or what the caller should expect at the end is a different assignment, and you should not add it to look finished. The page can say a person will read the note and respond about whether a conversation is next.
Review every draft sentence that is not a question or a routing line. If it could be removed and the file would still receive the same facts, it is optional. If it predicts an ending, it is outside the hire. Staff who call a person after a loud promise spend the opening undoing the page. That is a new kind of retyping, done out loud.
Ask the person you hire to repeat the scope in their words before Implementation. They should say they are matching the incident types and the facts to the form and the file. If they say they are making the firm sound stronger, pause. Strength on this page is a note the file can accept without editing. The practice's reputation is not a field.
You still decide which incident types exist. A builder who adds a type you do not take, because the menu looked short, creates notes you will decline and copy anyway. Strike the extra type. The decline is part of the map.
How to Tell the Map Is Finished
The map is finished when a test submission appears in the file with the kind of incident, the timing, and the other-firm answer already in their places, and nobody retyped them. Read that test the way you read a new matter. If you would still open the web message to interpret it, the fields did not match. Send it back.
Do one test for each incident type you take, plus one for a harm that uses the short line. The line should land where a person can see it, not in a discarded comment. The declined types should be absent, so you are not testing a door you do not want.
Sit with the staff after a few real notes. Ask what they still copy. A single missed field is an edit, not a reason to abandon the form. A return to the old message box means the new form is harder to find, often because the homepage still offers the old one. Point injury traffic at the mapped form. Retire the box that made retyping necessary.
Keep the map when the file changes. A new fact the office starts writing down should become a field, or the retyping will creep back for that fact alone. Tell the person who maintains the form in a short note. The ongoing work is alignment. It is the same hire, in a smaller shape, each time the file gains a question you now ask every time. If two people retype, ask both what they still copy. They often copy different leftovers, and both leftovers belong on the form. Keep the field list beside the file's labels so a renamed label changes on the form the same day.
Questions
When Should a Personal Injury Firm Hire Intake Help?
When you already know the incident types you take and the facts the file needs, and someone still retypes the web form to create them. The copying is the signal. A wish for a newer look is not the signal.
What Should the Helper Map?
Each fact in the file to a question on the page, using the same words. Kind of incident, timing, and whether another firm is involved are the usual core. The note should arrive where the file is opened, without a second copy.
What Must the Project Leave Out?
A promise about an outcome. The page can say someone will read the facts and respond. It should not predict an ending or describe what happens to a type of harm. Those sentences are not fields.
Who Decides the Incident Types?
You do. The list of harms you take, and the harms you decline, is the practice. Help builds that list into the form. An extra type added to fill a menu creates notes you did not ask for.
How Do You Know the Retyping Has Stopped?
A test note shows the facts in the file's own places, and the person who used to copy says there is nothing left to copy. If they still open the original message to interpret it, the map is incomplete.
Sit with the person who opens the file and mark which form fields they retype today. Those marks are the project. Leave off any field that exists only to make the page look thorough. A shorter form that matches the file beats a long one that staff correct by hand.
Conclusion
Hire help when you already know which incident types you take and which facts the file needs, and someone still retypes them because the form does not match the file. The help should map those fields. It should not write a promise about an outcome. You now know when personal injury intake help is justified, and which promises it must not add.
When you are ready to decide when the page and the intake form are one project, Speak With Us.
