Legal Services Offshore blog

Build an arbitration demand intake checklist that records service and filing dates

An arbitration intake checklist that separates the demand filing, the filing fee, and service on each respondent while counsel owns the claims and the forum strategy.

Build an arbitration demand intake checklist that records service and filing dates editorial illustration
Defined workflowAttorney review gatesPractical escalation

Key takeaways

An arbitration demand starts a process with its own forum rules, service requirements, and response deadlines. The intake checklist records the forum, the demand date, the filing fee, the service method, and the person responsible for each step. It also records the source document for each date. A demand that was drafted but not filed is not an intake.

The filing and the service are separate events. A demand may be accepted by the forum while service on a respondent is still outstanding. Record both dates and the evidence for each. A checklist that treats filing as service will hide the gap.

Forum rules differ on fees, formatting, and the number of copies. The checklist should name the rule set and the version used at intake. Do not assume that a process from another forum applies. Record the question and route it to counsel.

Counsel decides the claims, the forum strategy, and whether to amend or withdraw. The support lane confirms that the intake fields are complete and that the records match. That division keeps a procedural checklist from becoming a legal opinion. Each exception should name the lawyer who will resolve it.

Identify the forum and the governing rules

Record the arbitration provider or the ad hoc forum named in the agreement, and note the clause that selects it. Copy the clause text and the section reference into the intake record. A clause that names an institution and a set of rules should show both. The reviewer should be able to see why the forum was chosen.

Record the version of the rules in effect on the demand date and the source used to confirm it. Rules change, and a later printout may not match the version that applied. Note the source date and the person who checked it. A question about which version controls belongs to counsel.

Record the seat or the place of arbitration and any language or nationality requirements. These fields affect scheduling and the pool of arbitrators. Record the source for each field rather than inferring from the contract. An uncertain field should be marked as an open question.

Record the number of arbitrators, the method of appointment, and any deadline for appointing them. Do not calculate the appointment path without the rules in hand. Record the rule reference and the lawyer who will confirm it. The intake should show what remains to be decided.

Record the demand and the filing fee

Record the demand date, the method of submission, and the confirmation number issued by the forum. A saved draft is not a filed demand. Attach the filed copy and the receipt to the intake record. The entry should distinguish submission from acceptance.

Record the filing fee, the currency, the payer, and the date of payment. Keep the payment evidence with the demand record and note any installment arrangement. A fee that was promised but not received can stall the file. Record the forum confirmation of payment.

Record the amount in dispute as stated in the demand and note that it is a pleading figure, not an accounting conclusion. A later amendment may change the figure. Record the source and the date. The intake should not silently update an earlier amount.

Record the attachments required by the forum, such as the agreement, the demand, and proof of payment. Check each attachment against the forum list and note any missing item. Record the person who assembled the packet. A complete packet is easier to serve and easier to audit.

Track service on each respondent

Create one service row for each respondent and record the address, the method, and the date sent. Record the tracking number or the transmission record. A single service note for multiple respondents hides who was actually served. The reviewer should see each respondent separately.

Record the date the respondent acknowledged receipt or the date the forum confirmed service. A delivery scan is evidence of delivery, not proof that the respondent received the demand. Record both when the file supports them. The distinction matters when a response deadline is calculated.

Record any respondent that could not be served and the reason in neutral terms. Route the question to counsel before attempting an alternative method. Record the instruction and the date it was given. The intake should not choose a substitute method on its own.

Record the deadline for the response or the answer as stated by the forum or the rules. Do not calculate it from memory. Record the source and the person who confirmed it. The service record and the response deadline should sit together.

Keep the claims, defenses, and legal strategy in counsel work product, not in the intake checklist. The checklist records dates, documents, parties, and procedural facts. A summary of the legal theory belongs to the lawyer who will sign the demand. The support lane should not draft a position.

Record the facts the demand relies on and the source document for each, but do not characterize their legal effect. A date, a payment, or a notice can be recorded without deciding whether it breaches the agreement. Record the source and any conflict between documents. The lawyer decides what the facts mean.

When a client supplies a new account of events, record the new statement and its date rather than replacing the earlier one. Note the difference and route it to counsel. A changed fact can affect the demand and the intake record. The history should remain readable.

Record any privileged or confidential material by reference and keep it out of the general intake folder. Note the access list and the person who approved it. A checklist is not a safe place for a legal opinion. The intake should point to the protected file.

Handle a deficient or amended demand

When the forum identifies a deficiency, record the notice date, the missing item, and the cure deadline. Assign the cure to a named person and record the date it was completed. A deficiency that is closed without evidence will reappear. The intake should show the forum acceptance after the cure.

When the demand is amended, record the new version, the date filed, and the claims or amounts that changed. Keep the earlier version and link the two entries. Do not overwrite the original intake. The record should show the sequence of filings.

Record any change in the respondent list and the service work that follows. A new respondent requires its own service row and its own evidence. Record the lawyer instruction and the date. The intake should not treat an added party as served by the earlier packet.

Record the forum response to the amendment and the next deadline. A filed amendment may reset part of the schedule. Record the source and the person who confirmed it. The checklist should show which dates are now current.

Review the intake before the answer date

Run a review before the response deadline and confirm that every respondent has a service record and a current deadline. Check the demand, the fee, and the attachments against the forum list. Record the reviewer and the date. A late review leaves no time to cure a service gap.

Confirm that the intake record matches the filed demand and the forum acknowledgment. A difference in the respondent name or the amount should be flagged. Record the correction and the source. The reviewer should see the filed version, not a working draft.

Confirm that each open question has a named lawyer and a date for resolution. An open question without an owner tends to remain open. Record the assignment and the follow-up date. The intake is complete only when every exception has a path.

Record the review result and the next review date in the checklist. Keep the checklist with the matter record so the next filing starts from the same source. A recurring review prevents the same deficiency from recurring. The next demand should need fewer corrections.

A supervised support lane can record the demand, the fee, and the service evidence for each respondent while the lawyer decides the claims and the forum strategy. Explore litigation document review support.

Sources

  1. American Bar Association, Model Rules of Professional Conduct

  2. Cornell Legal Information Institute, Federal Arbitration Act

  3. American Arbitration Association, Commercial Arbitration Rules

  4. GAO, Standards for Internal Control in the Federal Government

Bring the messy task list

We will help turn it into one clear legal support role.

Share the work, tools, hours, and review needs. The next step is a practical staffing scope, not a public rate card.