Short answer

Cost — yes. Every Job has a Cost (£) field, so you can record what a piece of work cost. Who did it — yes, via the assignee. How long it took — not as a dedicated field yet (note it in the description for now; timers are on the roadmap). Attaching a quote document — not yet either (attachments are in development). The way to keep a clean money-and-history trail today is to break a fix into one job per step and put the cost on each; they all roll up under the defect's and the asset's Related Records.

Detail

Cost

The Cost (£) field is on Jobs (also on Inspections and Routines — but not on Defects). Enter the actual spend on the job. If a fix takes several jobs (get quote → order part → install), put the cost on each one so the running total is visible when you look at the defect's Related Records.

Cost is web-app only. The field is not on the mobile app, so a figure can't be entered in the field. In practice that suits most councils, because the person doing the work often isn't the person who knows what it cost. The usual pattern is that the operative completes the job on their phone and whoever handles the invoices adds the cost on the web app afterwards.

No, and there is nothing planned in the near term. Integrating with accounting packages is on the longer-term roadmap, so it isn't something to plan around yet. For now the cost figures live in Civic.ly and export from there; the same separation applies to asset values, where Civic.ly holds the itemised register and the accounts carry the single annual total (see Which asset value fields should I fill in (purchase, current, replacement, insurance) — and how does this feed my AGAR?).

Multiple quotes

The pattern people use is to model each quote as its own job — "Get quote from Supplier A", "Get quote from Supplier B" — with the figure and supplier in the title/description, and the chosen one carried into the job that does the work. Attaching the actual quote PDF isn't possible quite yet — attachments are being built. Until then, keep the key detail (supplier, figure) in the description.

How long it took

There's no duration field yet. For now, record it in the job's Description, or convert the hours to a figure and put it in the Cost field (hours × your hourly rate) so the totals at least add up and export. A timer is on the roadmap — an explicit start / pause / stop control on the job itself. The pause is the important part for work that spans several days: the job can be started, paused overnight and resumed, so what you get is the hours actually worked rather than the days elapsed.

Where it all shows up

Each job carries its cost, assignee and the dates you set (as milestones). Open the defect's Related Records to see every job involved in the fix together, and open the asset to see every task ever linked to it — inspections, defects and jobs — as the asset's full history.

Watch-outs

  • Defects have no cost field. Put cost on the job, not the defect.
  • Cost can't be entered on a phone. It's a web-app field, so don't ask a field operative to record spend on the job they've just completed. Someone adds it on the web app afterwards.
  • No accounts-package integration. Nothing is planned in the near term, so treat Civic.ly as where the job costs live rather than something that will feed your accounts automatically.
  • One photo per job. If you need to show several things, raise a job (or defect) per issue rather than expecting multiple photos on one.
  • Duration and attachments aren't live yet. Use the description as the interim home for both; both are on the roadmap. For hours specifically, the Cost field is the better interim than free text — it's the only place a number can be totalled and exported.
  • Don't assume status history will turn into timing data. The timer is a separate control you start and stop deliberately (see the note above), so how long a job sat in In Progress is not what it will report.