Short answer

No — don't let asset values hold you up. Filling in financial values and other record details, and creating your inspections, maintenance jobs and defects, are two completely independent jobs. They can happen in parallel, or at entirely different times.

As soon as your assets are in, uploaded, and the AI has processed them, you can start creating recurring inspections, jobs and defects straight away. Adding (or later updating) the purchase/insurance/replacement values, notes, and other fields can be done whenever it suits — including weeks later, or by a different person — without affecting the inspections you've already set up.

Detail

Why people wait (and why they needn't). Councils often treat the asset register like an accounting exercise — get every value signed off, then "go live". That's understandable, but it delays the part of Civic.ly that protects you day to day: the recurring inspection and maintenance workflow. A bench gets inspected to keep it safe whether or not its replacement value has been entered yet. The value fields feed reporting and insurance/AGAR work; they are not a prerequisite for scheduling or doing the work.

What an inspection/job actually needs. A recurring inspection or job is built on the asset existing and being correctly classified — its location, type and checklist. None of that depends on the money fields. So once the register is captured and processed, the operational layer is ready to switch on.

The recommended approach. Capture and process the assets → set up your recurring inspections so the team is covered → backfill values and other details in parallel or as they're confirmed. If you're waiting on one person (e.g. the clerk) for figures, that's a reason to split the work, not to pause everything.

Watch-outs

  • This is separate from Draft vs Active. Leaving assets in Draft while you finish tidying the register is fine and expected. The point here is purely that values aren't a blocker for inspections.
  • Don't double-handle. Set the routine up once over the assets; you don't need to recreate or re-touch inspections after you later add values — updating a value won't disturb existing tasks.