FEZA innovation – Home
← All products

Developed on request

Law Firm & Legal Practice

Law Firm Software

Review documents, lawyer-defined deadlines and expenses within each matter. We will scope hearings and deadline tracking separately in the software we will build for your firm. Client-facing information and internal working notes will follow access boundaries defined around your team.

  • Document archive by matter
  • Deadlines defined by lawyers
  • Expenses linked to advances
Scales, stacked files and a thick book beside a tablet displaying a calendar grid
  1. Discovery
  2. Scope and quote
  3. Development

When calendar notes lose their link to matter documents

Choose a structure connecting documents, dates and tasks so the next step in a matter can be reviewed. Hearings in another calendar, notices in separate folders and client conversations on phones require searching when responsibility changes. Expense advances in separate spreadsheets also make the basis of spending harder to trace.

The software we will build will relate courts or enforcement offices, file numbers, parties and stages within each matter. Lawyer-defined deadlines could link to documents and tasks. You can define lead and backup responsibilities and date checks. Internal notes and client-shared information will be scoped separately. Open accounts and closed matters will also be distinct states.

A calendar detached from matters

  • The source document for a deadline is searched for elsewhere.
  • Advance and spending movements may not match the matter’s stage.

Matter-centred scope

  • Dates supplied by lawyers could link to documents and tasks.
  • Expenses, documents and responsible people could share a matter.

From incoming documents to lawyer review and task completion

Our sample starts with a new document arriving at the firm. Upload responsibilities and the lawyer’s deadline assessment will be designed separately. Explain who is notified after recording a document and how completed work is checked. If expenses arise, their document links will join the scenario. These steps form an initial outline of responsibilities for the project we will build.

  1. 01

    Link documents to matters

    Petitions, minutes, decisions and notices could be matched by type. Uploader and recording time remain separate from legal assessment.

  2. 02

    Define dates and tasks

    Start and end dates will be entered on the lawyer’s decision. Lead and backup responsibilities, task descriptions and reminders could be selected together.

  3. 03

    Check completion

    Evidence of completed work and task outcomes could join the matter. Expenses could link to advances, with the reviewer’s closing decision scoped separately.

From litigation and enforcement records to tasks and expenses

The first release could combine matter identity, documents and dates you define. Litigation and enforcement stages will use your firm’s terminology. Linking each task to a matter helps select notes currently held in personal calendars. Time recording or client views could be additional needs. Expenses, advances and legal-fee instalments will be discussed as separate movement types.

  1. Initial firm scope

    Matters, documents and deadlines
    Matter records, document types, lawyer-defined dates and lead and backup assignments could enter the first release.
  2. Optional firm additions

    Work records and client area
    Time records, detailed expenses and limited matter-specific client information could be added as needed.
  3. Subject to external access

    Data and notification flows
    External data or messaging will be reviewed separately if the relevant provider offers connections and access.

Distinguish litigation stages from enforcement movements

If your firm handles both, shared documents and tasks can coexist with separate stages. Litigation may focus on hearings and decisions; enforcement may require payment orders, seizure and collections. Your examples will determine fields in the scope we will build. Client accounts will also be designed independently of matter type, keeping expenses and collections linked to their own sources.

Stage record

Litigation matter
Hearings, interim decisions and case status will be defined with your firm.
Enforcement matter
Applications, payment orders and seizure stages could be selected.

Date relationship

Litigation matter
Lawyer-defined deadlines and hearing details could remain separate.
Enforcement matter
Lawyer-defined task dates for enforcement will be scoped.

Account movement

Litigation matter
Matter expenses and advance use could be linked.
Enforcement matter
Collections and enforcement expenses could join the relevant client account.

Matter-specific permissions for lawyers, trainees and secretaries

A firm role need not grant access to every matter. The project we will build will consider roles together with assignments. Permission for trainees to add documents could be separate from changing deadline decisions. You can define who downloads documents, shares client information or edits closed matters. Boundaries for confidential professional records will be discussed during discovery.

Lead lawyer

Date approval, assignments and client-visible fields could be linked to the authorised lawyer. Backup access will be discussed separately.

Documents and administration

Secretaries and trainees could have separate upload, calendar and expense permissions. Document versions and editing history could be designed.

Confidentiality and personal data

KVKK, Turkey's personal data protection law, professional confidentiality, access logs, backups and retention are scoped. Your firm selects client-visible information.

Review limitation deadlines separately when hearings are adjourned

A changed hearing date must not be assumed to change every other date in a matter. The project we will build will scope hearings separately from deadlines the lawyer identifies as affecting the loss of rights. New hearing dates could link to explanatory documents and the person making the change. The authorised lawyer will assess deadline effects; the software will be designed to record that decision and its reminders.

We will define backup tasks and approval routes when the lead lawyer is on leave. History could retain earlier dates with explanations. Viewing a reminder and actually completing a task will be different states. Adjournment, deadline assessment and task closure will therefore be scoped around their own decision evidence.

Decisions mixed in the calendar

  • Adjournment may be interpreted as resetting every date.
  • Reading a reminder may count as completing the task.

Distinctions based on lawyer decisions

  • Hearing changes and deadline assessments could be recorded separately.
  • Task outcomes could link to documents and reviewers.

Match file numbers, document folders and open tasks

Court names and file numbers may be inconsistent in existing lists. We will review matter identity and client links through samples. Where folders mix documents from different matters, matching will require your firm’s checks. Open tasks, lawyer-verified dates and account balances will form separate migration areas. You select the detail transferred for closed matters.

  1. 01

    Review source fields

    Anonymised lists could map types, numbers and responsibilities. Rows missing identity fields will be flagged for review.

  2. 02

    Verify documents and dates

    Document links and open tasks will be compared in a sample transfer. Tracked dates will be selected under authorised lawyer review.

  3. 03

    Define external information routes

    Transfers from UYAP, Turkey’s judicial information system, or other sources depend on access. Available connections will be reviewed; otherwise files or manual entry can be discussed.

Review matter tracking as custom application scope

Matter management relies on everyday links between tasks and documents. Our web service offers an approach to scoping your firm’s record structure. The website and application article can also help you consider decision points. As you read, use examples to distinguish internal records from information intended only for client sharing.

Start with an anonymised matter record and deadline-check example

Prepare a matter record without party or client information, a task list and an expense example. Explain how you update adjourned hearings and who checks deadlines. The first release of the software we will build could centre on matters, documents and tasks. Client views and time records will be assessed separately for their access needs.

  • Share lead and backup lawyers’ decision points.
  • Distinguish document upload roles from date approval.
  • Identify archive sources and external information transfer methods.

The quotation will follow the defined firm workflow. Subscription use, support, migration and any alternative contract terms will be discussed in writing.

How we work

We do not sell an off-the-shelf package: we design the software around your workflow, build the first version in short steps and keep running it after launch.

  1. 01

    Discovery

    We listen to how your business works, your team and the tools you use today.

  2. 02

    Scope and quote

    Modules, priorities and price are set out in a written quote.

  3. 03

    Development

    We show working versions at short intervals and move on with your feedback.

  4. 04

    Setup and migration

    We move your existing records across and help your team get started.

  5. 05

    Support

    We run the software on a subscription and keep it up to date and secure.

Frequently asked questions

Can it work with UYAP, the Turkish court system?

We do not claim an official UYAP integration. How information taken from UYAP is transferred into your files is scoped per project; where a direct connection is not possible, it is entered by hand or by file import. Your work in UYAP itself continues there.

Does the software calculate deadlines?

The lawyer defines the deadline: the start date and the number of days. The software tracks that date, counts down and sends reminders. When a period legally begins is a matter of legal judgement; the software does not make that call for you, it makes sure the call you made is not forgotten.

Can enforcement files be tracked as well?

Yes. Enforcement proceedings can be scoped as a separate file type with their own stages, such as the enforcement request, payment order, attachment and collection, with collected amounts linked to the client account.

What can clients see?

That is entirely your decision. If a client screen is part of the scope, you set it per file: hearing dates only, interim decisions, or selected documents. You can also choose to show nothing at all.

How is access restricted for professional confidentiality?

Access is defined by role and by file: each user sees only the files they are authorised for, and every opening of a file is logged. The software is designed to support the lawful processing of personal data under KVKK, the Turkish data protection law; your firm remains the data controller.

Can we import our existing list of files?

Importing a file list from a spreadsheet or your current software can be included in the scope. How much can be transferred depends on how your existing records are structured; we look at this together during discovery.

Would every reminder change when a hearing is adjourned?

Hearings and other deadlines could remain separate. Your lawyer determines affected dates and tasks; earlier values and reasons for change will be designed into the matter record.

Could earlier responsibility remain visible when a backup lawyer takes over?

Handover could link previous and new responsible people. Open tasks, lawyer-defined deadlines and handover notes will be selected together, with access following your firm’s boundaries.

How is the price set?

After a discovery meeting we prepare a written quote covering the scope, the modules and the setup work. The software is provided on a monthly or annual subscription.

Do we receive the source code?

In our standard model the software is provided on a subscription and the source code is not transferred. If you need a different model, it is agreed in a separate written contract.

Who is responsible for what is done with the software?

We build and operate the software. The business using it is responsible for how it is used, the data entered and the content published; the details are set out in the service agreement.

Related products

Share your firm’s matter workflow

Let us prepare law firm software scope from your document, deadline and task examples.

  • Document archive by matter
  • Deadlines defined by lawyers
  • Expenses linked to advances