Methodology / Benchmark v1

How we test field service software

Revudit Limited uses a documented benchmark to test common field-service workflows under comparable conditions. It reports the evidence and the gaps separately.

Benchmark workflow

1. Set up the account and record plan, date, device, and test-user context.
2. Create a customer, job, estimate, invoice, and payment path where available.
3. Schedule and reschedule work, including a conflict scenario.
4. Check recurring-work behaviour and mobile task continuity.
5. Test named AI features only when accessible in the tested account.
6. Capture what was observed, what was blocked, and what was not tested.

Evidence rules

Observed describes something directly seen in the tested product. Calculated is derived from stated inputs. Vendor-stated comes from a vendor-controlled source. Blocked means the workflow could not proceed. Not tested names untouched downstream steps. Date-sensitive identifies claims likely to change.

Result rules

Individual benchmark steps can be labelled Pass, Partial, Fail, Blocked, or Not tested. Revudit Limited does not collapse those results into a star score.

Updates and corrections

When a later test supersedes an earlier observation, the affected passage is marked “Updated by later test” and the new date is recorded. Corrections remain distinct from test updates.