Maluti QMS — home Contact

Industries · Herbal medicinal products

Herbal medicinal products

For sites that receive plant material, dry and prepare it, extract it, and test and release the result.

The path of one batch, in four stages.

  1. 1Incoming material and storage5 steps · 3 with limits
  2. 2Preparing the plant4 steps · all available
  3. 3Extraction3 steps · 3 with limits
  4. 4Testing and release5 steps · 2 with limits

What you can run from start to finish today

From receipt to release on the screens, for plant material that is dried, or extracted with carbon dioxide or by mechanical separation.

Where it stops

  • Stops the process. Entering the residual solvent result is not available on the screens yet. So a batch extracted with an organic solvent, such as ethanol, cannot be released from the screens.
  • Not on the screens yet: Run an identity test on every batch received; Qualify equipment through URS, IQ, OQ, PQ; Close the balance on the active substance.
  • Quarantine status recorded. Material in quarantine can still be used in production: MALUTI does not yet stop a run from consuming raw material that has not passed its own tests. Only the finished batch is held back at release.
  • Hold and monitor storage conditions. A reading outside its limit is shown on the screen, but it is not yet recorded as an alarm by itself: someone has to see it and act.

What this page says about MALUTI was checked against the product’s code on 30 September 2026. It has not yet been walked through from start to finish on a test site.

Incoming material and storage

1Supplier approval under GACPBuilt in MALUTIOpenClose

Register counterparties and score suppliers

Built in MALUTI

Your team

Your qualified person registers each supplier with the licence it works under.

In MALUTI

The supplier: kind, name, licence number, issuing authority, expiry date, and certificates kept with a fingerprint, so any later change to the file shows. Every change stays visible.

Checked by MALUTI

  • Only the qualified person can register or change a supplier.
  • A licence without the authority that issued it is refused.

Boundaries

  • Entered by hand: the supplier score and the judgement behind it.
Technical detail
  • Ledger operations RegisterCounterparty, AmendCounterparty, SetCounterpartyCertificate; the role check is in the ledger, not the screen.

Audit suppliers and keep the reports

Done by the site, recorded in MALUTI

Your team

Your site or its auditor audits the supplier and writes the report.

In MALUTI

The audit against that supplier: date, outcome, the report kept with a fingerprint, so any later change to the file shows, and when the next audit is due.

Checked by MALUTI

  • Only the qualified person can record an audit.
  • An audit without its date, its outcome or its report is refused.

Boundaries

  • MALUTI does not audit suppliers; it keeps the record that the audit took place and what it found.
  • Entered by hand: the audit itself and its outcome.
Technical detail
  • Ledger operation RecordSupplierAudit.

Regulatory context

The starting material comes from a supplier under GACP. Only herbal starting material made in accordance with GMP and the marketing authorisation, from suppliers in compliance with good agricultural and collection practice, with the audits of them documented.

Annex 7 §7 source

2Goods-in examination and identityAvailable with limitsOpenCloseRecording the identity test of a received batch is not available on the screens yet.

A grower declares a delivery

Built in MALUTI

Your team

The grower or supplier declares a delivery before it arrives.

In MALUTI

The declared delivery: supplier, strain, plot of origin, gross and tare weight, wet or dry, and the plant parts it contains.

Checked by MALUTI

  • A delivery without a supplier, a strain or the plot it came from is refused.
  • A tare that is not less than the gross weight is refused.

Boundaries

  • Anyone with access can declare a delivery; the check comes at goods-in.
  • Entered by hand: the declared figures come from the supplier.
Technical detail
  • Ledger operation DeclareDelivery; no role restriction in the ledger.

Examine each container: labels, damage, broken seals

Built in MALUTI

Your team

Goods-in staff examine every container: label, damage, broken seals.

In MALUTI

The examination: number of containers, the name as printed on the supplier label, and a plain answer to each of the four points Part II 7.20 names.

Checked by MALUTI

  • A delivery cannot be accepted until it has been examined.
  • Only goods-in operators and the qualified person can accept a delivery.

Boundaries

  • Entered by hand: what the person saw on the containers.
Technical detail
  • Ledger operations ExamineDelivery and AcceptDelivery; acceptance refuses an unexamined delivery.

Run an identity test on every batch received

Not on the screens yet

Recording the identity test of a received batch is not available on the screens yet.

Your team

The laboratory tests the identity of every batch received, or your site relies on the supplier's certificate where the supplier has earned it.

In MALUTI

The identity test of the batch: your own test or the supplier's certificate, and the verdict.

Checked by MALUTI

  • A supplier certificate is accepted instead of a test only when that supplier has enough full analyses on record.

Boundaries

  • An identity test is not required before the material is used, or before the finished batch is released.
  • Entered by hand: the test itself is the laboratory's.
Technical detail
  • Ledger operation RecordIdentityTest exists behind POST /api/module1/batch/:id/identity; no page calls it.

Regulatory context

Every container examined, every batch identified. Each container examined on arrival for labels, damage and broken seals, and an identity test run on every batch received.

Part II 7.20, 7.30 source

3Specification for the plant materialBuilt in MALUTIOpenClose

Approve a specification, every limit naming its method

Built in MALUTI

Your team

Your qualified person approves the specification for the plant material.

In MALUTI

The specification with its version and its source (monograph, guideline or regulation); every limit with its unit and test method. Each batch is held to a named specification.

Checked by MALUTI

  • Only the qualified person can approve a specification or hold a batch to one.
  • A limit without a test method or a unit, or with minimum above maximum, is refused.
  • A released batch cannot be put under a new specification.

Boundaries

  • Entered by hand: the limits themselves are your site's decision.
Technical detail
  • Ledger operations DefineSpecification and HoldToSpecification.

Regulatory context

The specification names the plant, not only the limits. The binomial scientific name, the source of the plant, the part used, the drying system, identity tests, water content, assay of markers, pesticides, fungal and microbial limits with aflatoxins, toxic metals and foreign materials.

Annex 7 §8 source

4Quarantine and separate storageAvailable with limitsOpenCloseMaterial in quarantine can still be used in production.

Quarantine status recorded

Available with limits

Material in quarantine can still be used in production: MALUTI does not yet stop a run from consuming raw material that has not passed its own tests. Only the finished batch is held back at release.

  • Available Quarantine status on every received batch
  • Available Quarantine lifted only by the qualified person's release
  • Not yet Quarantined material stopped from being used in production

Your team

The store keeps received material apart until it is released.

In MALUTI

Every accepted batch starts in quarantine; only a release by the qualified person lifts it.

Checked by MALUTI

  • Release is refused for anything that is not in quarantine.

Boundaries

  • There is no state "used at risk, pending a result", which Annex 2 allows.
  • Entered by hand: where the material physically stands.
Technical detail
  • The batch is created with status quarantine by AcceptDelivery. Transform refuses a released input and accepts a quarantined one; no check of the input's own test result.

Store on pallets, off walls, apart from other crops

Done by the site, recorded in MALUTI

Your team

The store keeps material on pallets, off the walls and apart from other crops.

In MALUTI

A schedule for the check, who did it and when, the file kept with a fingerprint, so any later change to the file shows, and when it is next due.

Checked by MALUTI

  • A check marked as done carries who did it and when.

Boundaries

  • MALUTI does not see the store; it keeps the record of your own check.
  • Entered by hand: the storage itself and the check are done by people.
Technical detail
  • Upkeep schedule and marks (/upkeep.html); no ledger operation of its own.

Control pests in storage, by authorised people only

Done by the site, recorded in MALUTI

Your team

Authorised people or a contractor carry out pest control.

In MALUTI

A schedule for pest control, who did it and when, the contractor's report kept with a fingerprint, so any later change to the file shows, and when it is next due.

Checked by MALUTI

  • A visit marked as done carries who did it and when.

Boundaries

  • MALUTI does not carry out or inspect pest control; it keeps the schedule and the record.
  • Entered by hand: the pest control itself.
Technical detail
  • Upkeep schedule and marks (/upkeep.html); no ledger operation of its own.

Regulatory context

Stored apart, quarantine separate from approved. Herbal substances stored in their own areas, with different enclosed areas for incoming and for approved material, and protection against insects and rodents.

Annex 7 §1 source

5Storage conditions and monitoringAvailable with limitsOpenCloseA reading outside its limit is shown on the screen, but it is not yet recorded as an alarm by itself.

Hold and monitor storage conditions

Available with limits

A reading outside its limit is shown on the screen, but it is not yet recorded as an alarm by itself: someone has to see it and act.

  • Available Storage condition declared for each batch
  • Available Readings from connected instruments
  • Shown on the screen only Reading compared with its limit
  • Not yet An excursion recorded as an alarm on its own

Your team

Your site keeps the store within its declared conditions and runs the instruments that watch them.

In MALUTI

For each batch, the storage condition from its label, the coldest and warmest it may be kept at, and the basis for it; for each room, its declared conditions and the readings of connected instruments.

Checked by MALUTI

  • Only the qualified person can declare a batch's storage condition.
  • A condition without its basis (stability data, monograph or licence) is refused.

Boundaries

  • MALUTI reads instruments; it does not control heating, cooling or humidity.
  • Entered by hand: readings typed in where no instrument is connected.
Technical detail
  • Ledger operation SetBatchStorageCondition. The limit judgement runs in the browser (conditions screen), not on the server, so an excursion does not write an alarm record.

Regulatory context

Humidity, temperature and light are held and watched. Where storage needs special conditions of humidity, temperature or light protection, those conditions are both provided and monitored.

Annex 7 §4 source

Preparing the plant

6Container inspectionBuilt in MALUTIOpenClose

Examine every container for foreign matter and rot

Built in MALUTI

Your team

Staff open each container and look for foreign matter, rot and adulteration.

In MALUTI

The examination of the batch: containers examined, containers rejected, and what was found in each rejected one.

Checked by MALUTI

  • A rejected container without what was found in it is refused.

Boundaries

  • Entered by hand: what the person saw.
Technical detail
  • Ledger operation RecordContainerExamination.

Regulatory context

Each container is opened and looked into. Written instructions and records that each container is examined for adulteration or substitution, for foreign matter such as metal, glass, animal parts, stones or sand, and for rot and signs of decay.

Annex 7 §10 source

7Sieving and cleaning before storageBuilt in MALUTIOpenClose

Sieve out foreign material before storage

Built in MALUTI

Your team

Staff sieve and pick out foreign material before the plant goes into storage.

In MALUTI

How the material was cleaned or sieved and how much was removed; zero recorded on purpose counts.

Checked by MALUTI

  • A cleaning without its method is refused.

Boundaries

  • Entered by hand: the sieving and weighing what was removed.
Technical detail
  • Ledger operation RecordCleaningOfMaterial.

Regulatory context

Sieving and selection before the material is stored. Security sieving or another method of removing foreign material, and the cleaning or selection of plant material before the approved herbal substance goes to store.

Annex 7 §11 source

8Drying and size reduction recordsBuilt in MALUTIOpenClose

Dry to temperature and time, and record both

Built in MALUTI

Your team

Staff dry and reduce the plant material.

In MALUTI

Each drying run against its approved process: the temperature and time it asks for, the mass in and out, and who ran it.

Checked by MALUTI

  • A run without every parameter the process asks for is refused.
  • A value the process expects from an instrument cannot be typed in without a stated reason.
  • A run outside the process limits needs an explanation; its output goes to quarantine and a deviation is opened.

Boundaries

  • MALUTI does not control the dryer; it records the run and checks it against the process.
  • Entered by hand: values typed in where no instrument is connected.
Technical detail
  • Ledger operation Transform against a process defined with DefineProcess.

Define a process as data, with its limits

Built in MALUTI

Your team

Your qualified person approves each process as a written instruction.

In MALUTI

The process with its version: what it uses and produces, how its mass must balance, parameter limits and where each value comes from, the solvent and its residual limit.

Checked by MALUTI

  • Only the qualified person can approve a process.
  • A version number already used for that step is refused.
  • A process with a solvent is refused without a residual limit.

Boundaries

  • Entered by hand: the content of the instruction is your site's.
Technical detail
  • Ledger operation DefineProcess.

Regulatory context

Drying and size reduction are instructions, not habits. Processing instructions covering cleaning, drying, crushing and sifting, with the drying time and temperature and the method used to control cut or particle size.

Annex 7 §9 source

9Dust control and equipment cleaningBuilt in MALUTIOpenClose

Maintain buildings, floors, lighting, changing rooms

Done by the site, recorded in MALUTI

Your team

Your site maintains its buildings, floors, lighting and changing rooms.

In MALUTI

A schedule for the maintenance checks, who did them and when, the file kept with a fingerprint, so any later change to the file shows, and when they are next due.

Checked by MALUTI

  • A check marked as done carries who did it and when.

Boundaries

  • MALUTI does not inspect premises; it keeps the record of your checks.
  • Entered by hand: the maintenance itself.
Technical detail
  • Upkeep schedule and marks (/upkeep.html); no ledger operation of its own.

Keep the use and cleaning log of each machine

Built in MALUTI

Your team

Staff clean each machine to its written procedure and note each use and cleaning.

In MALUTI

The log of each machine: every use and every cleaning, how it was cleaned, when and by whom, in the order they happened.

Checked by MALUTI

  • A cleaning without how it was done is refused.

Boundaries

  • Entered by hand: the cleaning itself.
Technical detail
  • Ledger operations RecordCleaning and GetEquipmentLog.

Clean equipment between tasks and account for the residue

Done by the site, recorded in MALUTI

Your team

Staff clean the equipment between tasks and weigh the residue they recover.

In MALUTI

The cleaning of the equipment, and separately how much residue was recovered and where it went.

Checked by MALUTI

  • A recovery without the amount and where it went is refused.

Boundaries

  • Entered by hand: the cleaning and the weighing.
Technical detail
  • Ledger operations RecordCleaning and RecordCleaningRecovery.

Regulatory context

Dust is a cross-contamination problem, and is treated as one. Specific provisions during sampling, weighing, mixing and processing wherever dust is generated, so that cleaning is possible and cross-contamination is avoided.

Annex 7 §5 source

Extraction

10Extraction run recordsAvailable with limitsOpenCloseEntering the residual solvent result is not available on the screens yet.

Define a process as data, with its limits

Built in MALUTI

Your team

Your qualified person approves each process as a written instruction.

In MALUTI

The process with its version: what it uses and produces, how its mass must balance, parameter limits and where each value comes from, the solvent and its residual limit.

Checked by MALUTI

  • Only the qualified person can approve a process.
  • A version number already used for that step is refused.
  • A process with a solvent is refused without a residual limit.

Boundaries

  • Entered by hand: the content of the instruction is your site's.
Technical detail
  • Ledger operation DefineProcess.

Extract with a solvent and measure the residue

Not on the screens yet

Entering the residual solvent result is not available on the screens yet. So a batch extracted with an organic solvent, such as ethanol, cannot be released from the screens.

Your team

The laboratory measures the residual solvent in the extract.

In MALUTI

The residual solvent result against the limit in the process, with the certificate of analysis kept with a fingerprint, so any later change to the file shows.

Checked by MALUTI

  • A batch extracted with an organic solvent cannot be released without a residual solvent result.
  • A result above the process limit stops the release.

Boundaries

  • Extraction with carbon dioxide or by mechanical separation does not need this result, and is not affected.
  • Entered by hand: the analysis is the laboratory's.
Technical detail
  • Ledger operation RecordResidualSolvent exists behind POST /api/batch/:id/residual; no page calls it. The release gate skips it for solvent classes none and outside_q3c.

Start and run a process

Built in MALUTI

Your team

Operators start the extraction on qualified equipment and record the run.

In MALUTI

The run on its equipment: materials in and out with their masses, the process values, and where instrument readings came from.

Checked by MALUTI

  • A run cannot start on equipment that is suspended, of the wrong kind, already in use, or whose qualification has run out.
  • Material already used or already released cannot go into a run.
  • Instrument readings must name the instrument they came from.

Boundaries

  • MALUTI records and checks the run; it does not start or stop the machine.
  • Entered by hand: values typed in where no instrument is connected, with a stated reason.
Technical detail
  • Ledger operations StartRun and Transform; instrument readings carry the sealed chain that covers them.

Regulatory context

Solvent, time, temperature, concentration. For a herbal preparation the instructions give the solvent, the time and the temperature of extraction, and the detail of any concentration stage and the methods used.

Annex 7 §12 source

11Equipment compatibility with the solventAvailable with limitsOpenCloseRecording the individual qualification stages (URS, IQ, OQ, PQ) is not available on the screens yet.

Register equipment and its qualification

Built in MALUTI

Your team

Your qualified person registers each piece of equipment and the date its qualification runs out.

In MALUTI

The equipment: label, kind, location, serial number, service state and the date until which it is qualified.

Checked by MALUTI

  • Only the qualified person can register equipment.
  • Equipment without the date its qualification runs out is refused.
  • A run cannot start on equipment whose qualification has expired.
Technical detail
  • Ledger operations RegisterEquipment, SetEquipmentSerial, SetEquipmentService.

Qualify equipment through URS, IQ, OQ, PQ

Not on the screens yet

Recording the individual qualification stages (URS, IQ, OQ, PQ) is not available on the screens yet.

Your team

Engineers qualify equipment through URS, IQ, OQ and PQ.

In MALUTI

Each qualification stage against the equipment, in order, with its protocol kept with a fingerprint, so any later change to the file shows.

Checked by MALUTI

  • Only an engineer or the qualified person can record a stage.
  • A stage cannot be recorded before the stages that come before it, or twice.

Boundaries

  • The equipment screen does take the date until which the equipment is qualified, and runs are stopped after it.
  • Entered by hand: the qualification work and the protocols.
Technical detail
  • Ledger operation RecordQualificationStage exists behind POST /api/module4/equipment/:id/qualification; no page calls it.

Regulatory context

The equipment survives the solvent, and so does the product. Equipment and filtering materials compatible with the extraction solvent, so that nothing is released into the product and nothing is absorbed out of it.

Annex 7 §6 source

12Yield and active substance balanceAvailable with limitsOpenCloseClosing the active substance balance is not available on the screens yet.

Investigate a significant deviation from expected yield

Built in MALUTI

Your team

Your site investigates a yield that comes out wrong.

In MALUTI

Each run compared with the ratio its process declares; a yield outside the tolerance opens a deviation on the run.

Checked by MALUTI

  • A yield outside the declared tolerance opens a deviation and sends the output to quarantine.
  • Such a run needs a stated explanation.
  • A batch with an open deviation cannot be released.

Boundaries

  • Entered by hand: the investigation and its conclusion.
Technical detail
  • Ledger operation Transform (ratio breach → deviation record).

Close the balance on the active substance

Not on the screens yet

Closing the active substance balance is not available on the screens yet.

Your team

The laboratory assays every part that went in and came out.

In MALUTI

The balance of the active substance across a run, from the laboratory results of every part.

Checked by MALUTI

  • The balance cannot be closed while any part lacks its laboratory result.
  • A gap above the process tolerance needs a stated explanation.

Boundaries

  • Entered by hand: the assays are the laboratory's.
Technical detail
  • Ledger operation ReconcileActive exists behind POST /api/transform/:id/reconcile-active; no page calls it.

Regulatory context

A yield that comes out wrong is investigated. Any significant deviation from the expected yield is investigated and recorded.

ch. 5 §5.44 source

Testing and release

13SamplingBuilt in MALUTIOpenClose

Take a sample to a sampling plan

Built in MALUTI

Your team

A person who knows the plant takes the sample.

In MALUTI

The sample: what it was taken of, quantity and unit, where it is stored, and the sampling plan it was taken to.

Checked by MALUTI

  • Only the qualified person can record a sample.
  • A sample without where it is stored, or without a sampling plan in force, is refused.

Boundaries

  • Entered by hand: the sampling itself.
Technical detail
  • Ledger operation TakeSample.

Regulatory context

Sampling by someone who knows the plant. Sampling carried out with special care by personnel with particular expertise, because plant material is heterogeneous, and each batch identified by its own documentation.

Annex 7 §13 source

14Reference samplesBuilt in MALUTIOpenClose

Keep reference and retention samples

Built in MALUTI

Your team

Your site keeps a reference sample of the plant and disposes of it at the end of its period.

In MALUTI

The reference sample with its quantity, place and retention period, and its disposal.

Checked by MALUTI

  • A reference sample must be enough for two full analyses.
  • Retention cannot be counted where the batch has no shelf life to count it from.

Boundaries

  • Entered by hand: keeping the sample physically.
Technical detail
  • Ledger operations TakeSample and DisposeSample.

Regulatory context

A reference sample of the plant is kept. A reference sample of the plant material, and samples of unmilled material where powders are used.

Annex 7 §14 source

15Qualified quality control staffBuilt in MALUTIOpenClose

Record what a person is qualified by

Built in MALUTI

Your team

Your site makes sure the people in quality control can recognise the plant and its adulteration.

In MALUTI

What each person is qualified by: what, from whom, when, and the document kept with a fingerprint, so any later change to the file shows.

Checked by MALUTI

  • Only the qualified person can record a qualification.
  • A diploma or certificate without its document is refused.

Boundaries

  • MALUTI records what a person is qualified by; it does not test whether they can recognise adulteration.
  • Entered by hand: experience is recorded in words.
Technical detail
  • Ledger operation RecordQualification, against the person's certificate.

Regulatory context

Quality control can recognise adulteration by eye. Quality control personnel with particular expertise and experience in herbal substances, able to recognise adulteration, fungal growth, infestation and non-uniformity within a delivery.

Annex 7 §15 source

16Identity and quality testingAvailable with limitsOpenCloseRecording the identity test of a received batch is not available on the screens yet.

Run an identity test on every batch received

Not on the screens yet

Recording the identity test of a received batch is not available on the screens yet.

Your team

The laboratory tests the identity of every batch received, or your site relies on the supplier's certificate where the supplier has earned it.

In MALUTI

The identity test of the batch: your own test or the supplier's certificate, and the verdict.

Checked by MALUTI

  • A supplier certificate is accepted instead of a test only when that supplier has enough full analyses on record.

Boundaries

  • An identity test is not required before the material is used, or before the finished batch is released.
  • Entered by hand: the test itself is the laboratory's.
Technical detail
  • Ledger operation RecordIdentityTest exists behind POST /api/module1/batch/:id/identity; no page calls it.

Regulatory context

Identity and quality against the monograph. Identity and quality determined in accordance with the current European guidance on herbal medicinal products and the relevant Ph. Eur. monographs.

Annex 7 §16 source

17Batch releaseAvailable with limitsOpenCloseA batch extracted with an organic solvent cannot be released from the screens yet, because its residual solvent result cannot be entered there.

Release a batch

Available with limits

A batch extracted with an organic solvent cannot be released from the screens yet, because its residual solvent result cannot be entered there. Batches from drying, carbon dioxide extraction or mechanical separation are not affected.

  • Available Release signed by the qualified person
  • Available Release refused until specification, certificate, deviations and cold chain are in order
  • Not yet Release of a batch extracted with an organic solvent

Your team

Your qualified person decides and signs the release.

In MALUTI

The release: who signed, their role, the declaration and the time — and every reason it was refused until the batch was in order.

Checked by MALUTI

  • Only the qualified person can release.
  • Release is refused if the batch is past its expiry, was never held to a specification, lacks a passing certificate of analysis, has an open deviation, a cold chain excursion, a run cut short, or a missing or failed residual solvent result.
  • Release is refused while a number typed in by one person still waits for its second check.

Boundaries

  • Entered by hand: the decision is the qualified person's.
Technical detail
  • Ledger operation SignRelease; the release gates run in the ledger. The time on the record is the transaction time, which the sending client sets.

Assemble a batch dossier

Built in MALUTI

Your team

Your qualified person assembles the batch dossier for review or for an inspector.

In MALUTI

One document for the batch, assembled from what is recorded, each figure with the record it came from. The document is kept at the site with its fingerprint recorded.

Checked by MALUTI

  • The dossier calculates nothing of its own: where there is no record, it says so.

Boundaries

  • The dossier does not yet mark figures that were corrected after they were first entered (Annex 11 §8.2).
Technical detail
  • Assembled by services/dossier.js; its hash is written to the ledger.

Regulatory context

The authorised person releases the batch. Certification by the authorised person before release, against the batch dossier.

Annex 16 §1.6 source

What a launch needs

  • Instruments. Readings come from instruments that can report them; each one is surveyed at your site before we promise to connect it. MALUTI reads instruments; it does not control the dryer, the extractor or the store climate.
  • Your laboratory. Certificates of analysis are kept as files and results are entered against the specification. MALUTI does not run analyses.
  • Your procedures. Processes, specifications and sampling plans are approved by your qualified person; MALUTI holds them and checks the work against them.

Modules this path uses

Taken from the screens each step is done on. The subscription covers the software; implementation, hardware and integrations are quoted separately. Prices →

Full catalogue and how it is countedShowHide

EU GMP Part I · EU GMP Annex 7 · EU GMP Part II, and the path above: 61 of 84 record types kept in MALUTI · 21 not built yet · 2 outside the software.

A record type is one thing a clause asks a site to record, counted once even when two documents or a step ask for it. “Kept in MALUTI” covers what MALUTI does itself and the record it keeps of work your site does. It is a count of what we have mapped, not a share of the regulation — and not the same as the check above: 4 record types counted as kept cannot yet be recorded from the screens.

Not built yet (21)

Built in MALUTI (55)ShowHide
Done by the site, recorded in MALUTI (6)ShowHide
Outside the software (2)ShowHide

Detailed catalogue with every clause →

Let’s map MALUTI to your site.

Tell us about one of your processes. We show the matching functions, name the integrations it needs and prepare an individual offer. Documents for supplier evaluation →

Discuss your configuration