Log maintenance on an asset
maintenance_logLog work done on an asset: the day, what was done, the cost in whole cents, who did it, and when the next service falls due -- as a date (next_due) or as an interval in days (interval_days), never both. A repair that sets no schedule takes neither. A future work date is refused.
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| date | Yes | The day the work was done, YYYY-MM-DD. A future date is refused | |
| work | Yes | What was done, e.g. Oil and filter change, or Annual boiler service | |
| asset | Yes | The asset id, e.g. AST-2026-0003, its serial or asset tag, or its name when only one asset has it | |
| next_due | No | The date the next service falls due, YYYY-MM-DD. Pass either this or interval_days, not both | |
| cost_cents | No | What the work cost in whole cents. 12000 is 120.00. Default 0, for in-house work | |
| technician | No | Who did the work, e.g. Anna, or Acme Heating Ltd | |
| interval_days | No | Days after the work date the next service falls due, e.g. 90 for quarterly. Turned into a date once, at log time |