Skip to main content
Get Updates

Workflow

How it works

AV Fields captures the site on iPad. AV Suite is being developed to carry that context through sales engineering, design, estimating and project delivery on the desktop.

This describes the connected workflow AP AI Software is developing. AV Fields is in private testing and being prepared for App Store submission. AV Suite's native macOS project workflow remains in development, with operations and project management on the broader roadmap. Neither product is commercially available. The wider Suite roadmap does not define the feature set of AV Fields’ first release.

  1. Step 1

    Capture the room

    Field measurement, photographs and room geometry are recorded on site, in an iPad application, while the room is still in front of you.

  2. Step 2

    Draw and document on site

    Floor plans, reflected ceiling plans, device placement and signal intent are authored in the field rather than reconstructed later from notes.

  3. Step 3

    Carry the evidence forward

    What the field recorded travels with the project, so a later reviewer can see where a measurement or an assumption came from.

  4. Step 4

    Develop requirements and design

    Source documents and site evidence become reviewable AV requirements, and the design develops with its assumptions and revisions visible.

  5. Step 5

    Estimate and propose

    Equipment and materials lists inform a proposal draft that can be checked against the reviewed scope and design.

  6. Step 6

    Review and issue

    Qualified people check and release the drawings, proposal and engineering documentation. AI proposes and assists; it does not approve.

  7. Step 7

    Hand over for delivery

    The planned operations workspace gives project managers an approved scope and project records for kickoff, scheduling and coordination.

  8. Step 8

    Deliver and close out

    The broader roadmap connects field execution, project records and closeout documentation, with access appropriate to each person’s role.

What travels with the work

The intended record trail below links an issued dimension to its reading, source device and human acceptance. It illustrates the architecture being developed, rather than a complete workflow available in the current app.

  1. 01

    Capture

    CaptureID

    A scan or photograph of the room, stored immutably with its sensor and source metadata.

  2. 02

    Reading

    ReadingID

    A measurement, its device and session provenance, and an explicit acceptance by the person who took it.

  3. 03

    Revision

    RevisionID

    The drawing that the accepted reading supported, appended as a new revision with its lineage intact.

  4. 04

    Equipment

    EquipmentID

    One ceiling-microphone record with typed ports, represented by an RCP location symbol and a one-line signal block.

  5. 05

    Publication

    Export manifest

    One resolved revision, its approval status and the sheets issued from it.

One measurement, end to end

This illustrative record trail follows one dimension through the workflow without presenting a mock product screen or drawing as finished software.

ILLUSTRATIVE A fictional room, with invented identifiers and dates. Not a customer project, not a screenshot, and not a record of work performed.

An invented measurement traced from capture to publication
Stage Record What it holds
Capture CAP-8831 LiDAR scan of the room, taken on site. Stored immutably with its sensor metadata.
Reading RDG-0421 22 ft 4 in wall-to-wall from a laser distance meter, accepted by the surveyor who took it.
Revision REV-r4 The floor plan that acceptance supported. Revision r3 is still there, unchanged.
Equipment EQ-114-MIC-01 One ceiling-microphone record with typed ports, referenced by the relevant drawing views.
Placement PL-0067, PL-0068 A ceiling location symbol on the RCP and a signal block on the one-line, each linked to that microphone record.
Publication PUB-2026-03-14 The sheet set issued from r4, with the manifest of what went out.

The point is the direction it runs in. Ask why a wall is where it is on the issued sheet, and the answer is a specific reading, taken with a specific device, that a specific person accepted — rather than a dimension someone typed in at some point and nobody can now account for.

The rules that make it hold

These are design commitments for software in development, not descriptions of shipped behaviour.

  • An accepted reading is evidence plus a decision.

    Taking a measurement does not silently resize the drawing. Someone applies it, and the drawing records which acceptance supported the change.

  • One device is one record.

    A ceiling microphone uses a location symbol on the RCP and a block on the one-line. The intended shared record links those views while keeping each drawing type appropriate to the device.

  • Schedules are derived, not maintained.

    A cable schedule comes from the signal graph. It is not a second list kept alongside it, because two lists eventually contradict each other.

  • Partial stays partial.

    The observed end of an incomplete scan is not a confirmed corner. Closure and construction readiness are explicit checks, not a guess at the nearest endpoint.

  • Editing appends.

    A revision is a descendant with its lineage intact. Earlier revisions are not overwritten, and a later change cannot rewrite what an issued sheet was based on.

Follow the work

Interested in where this workflow is going?

Tell us whether you want updates about AV Fields, AV Suite or both products.

Get Product-Specific Updates