Deliberate steps from intake to client record.

An authorised user creates an intake in the intake screen under client management. This screen is not an anonymous intake form. Phone, referral and web-form source options describe where a record came from; they do not install a website form, read email or automatically import channels.

The record accepts applicant name, email, phone, subject and source; the response also includes status, assigned lawyer, creation time and any converted client ID. Optional extra form data may be entered as valid JSON; this is not a visual form designer or a schema for opposing parties or rejection history. Avoid unnecessary sensitive detail in free text.

The office separately evaluates urgent dates. The deadline calculation tool and calendar records are separate operations; creating an intake creates neither a deadline nor an appointment. A qualified person must verify inputs, applicable rules and results.

Office checklist

• Check name/title and necessary contact details.
• Keep the subject short; select suitable records and access boundaries for detail.
• Select the source label for the actual channel.
• Maintain a separate office checklist for missing information, opposing parties and urgency.

The office evaluates practice area, capacity and necessary information. A New intake label does not perform that professional assessment. Define who makes each decision in your office procedure.

Plan missing information and communication methods within the office. Creating an intake does not automatically send an information request, rejection message or privacy notice. This guide sets no universal message, response deadline or automatic closure rule.

Office checklist

• Identify the required parties and existing documents.
• Separately check approaching dates and responsibility for communication.

There is no separate Assigned status. Stored states are New intake, Initial meeting, Agreement, Active client and Rejected. On the web, Advance status submits the next stage and the acting user ID as assignee; it creates no appointment or distribution rule.

The mobile status form can select an allowed next status and an accessible firm member. The system checks that an assignee is an active company member and verifies relevant access. Tenant, branch and operation permissions still apply; selecting an assignee does not make the record visible only to that person.

Use roles and permissions to determine necessary operation access. Intake records do not promise separate note access restricting detailed notes to an assigned lawyer and manager. Review the permissions guide alongside actual role and branch scope.

Determining relevant people and relationships, sufficient records and acceptance suitability requires professional assessment. This guide does not claim a single search exhaustively scans all office records or previous intakes.

Conflict checking evaluates identifiers and name candidates among accessible clients; it does not scan all intakes, cases and opposing parties. An optional case reference separately requires full or assigned-case access, and client selection requires read permission. An inaccessible record means the result is not proof of absence across the office. Creating an intake does not automatically start this search.

Results are not automatically written to the intake, client card or a timestamped intake history. Maintain necessary review evidence separately under the office procedure. Matches, potential matches and no results are not legal acceptance decisions; also evaluate search limits in the conflict-check guide.

A qualified person assesses acceptance or rejection and applicable notice requirements for the matter. A software label proves neither legal suitability nor delivery of a message. Check current professional rules separately.

The mobile status form offers an eligible Rejected transition from New intake, Initial meeting and Agreement. The web row menu offers the next stage and eligible conversion; it has no separate rejection command. Active client and Rejected are terminal states; do not assume rollback or repeat conversion.

The intake response has no separate rejection reason, rejection date or notice date fields. Rejected status sends no automatic email or SMS. The office separately determines correspondence, delivery evidence and retention; text entered in a free field is not verified delivery.

The office assesses fees, scope, expenses and representation authority under applicable current rules and the actual matter. This guide approves no current tariff, universal percentage limit, mandatory form or fee model for every matter.

Advancing to Agreement does not upload a signed fee agreement or power of attorney and does not validate signatures. Relevant documents may be stored separately in document management; the user separately establishes authority, document and case links. Automatic acceptance through electronic signatures or UYAP is not assumed.

Office checklist

• Review parties, scope and authority documents.
• Verify fees, expenses, payments and termination terms for the matter.
• Separately retain the signed copy and necessary authority documents in the appropriate record.

First advance the intake from Agreement to Active client. The active label alone creates no client card. The separate Convert to client operation requires intake-update and client-create permissions, an active record not already converted, and write access in the receiving branch.

The conversion form takes client type, identity/tax number and address. Checksum validation is a format check, not an official identity-service lookup, authority verification or agreement review. The system uses the intake name, email and phone plus entered details to create a new client card in the same receiving branch; the new client ID is stored on the intake. Status remains Active client; there is no separate Converted state.

Intake history, meeting notes, extra JSON and conflict results are not automatically transferred to the card. There is no merge with an existing client or automatic linking of later intakes to that card. A concurrent second conversion is rejected by the converted-record check; this does not resolve whether different intakes concern the same person.

Create the case separately in case management and select the client as a party. Intake conversion creates neither a case nor a general advisory file; do not assume the same schema suits every non-litigation matter.

Add documents, tasks, hearings and other calendar entries as separate operations using existing fields and permissions. Creation of a case is not system verification that every opening document is uploaded, every deadline is identified or legal work has begun.

Automatic UYAP matching is not available. Separately review UYAP preparation status. A qualified person verifies the deadline result and record association for the matter.

The office determines personal-data processing, information and retention decisions for the actual process and current requirements. Intake creation does not automatically show privacy information, collect applicant consent or prove delivery. The platform user consent flow does not replace these steps for applicants.

Process only necessary data with appropriate access. Tenant, branch and operation permissions apply; the assignee field provides no separate note privacy. Do not assume every read appears in intake history or a complete activity statement is available to users. See the security page for product scope.

No universal retention period or automatic expiry deletion is promised for rejected records. Retention, document relationships and finding/erasing person data across different records require separate assessment; this guide sets no person-matching or erasure policy. Use the privacy guide with qualified review of actual requirements.

Office checklist

• Manage privacy information and communication separately in office procedures.
• Review role and branch access using actual users.
• Separately determine retention/erasure by record and data type.