BuildPath NZ logo

Consents

Building consent

This stage manages building consent documentation, council questions, issued plans, inspections, amendments, and CCC readiness. This page shows what a beginner residential developer in Auckland should check, who to ask, what evidence to save, and where to verify before committing money or instructions.

building consentNZ Building CodeRFIissued plansCCC6 rolesLast reviewed 11 August 2026

How to execute this stage

Micro-stage control plan

Work through each applicable step in order. A hold point means pause the dependent decision or work until the stated evidence and authorised review are complete.

8 structured steps
  1. 01NZ Building Code pathwayLevel 2 · Consents
    TaskCheckHold pointEvidenceRecordNext action

    Simple explanation

    NZ Building Code pathway

    Technical context

    Test this point against Building consent application, the current feasibility version and written input from Architect. Separate verified facts, professional opinion and assumptions.

    Why it matters: This check can change yield, consent pathway, acquisition terms, funding, cost, programme or exit strategy. It must be resolved before the developer relies on whether documentation is complete.

    Prerequisites

    • Building consent application is current and its source/date are recorded.
    • The project objective, feasibility version and decision deadline are clear.
    • Architect has a focused brief where professional confirmation is required.

    Checks

    • Does Building consent application directly support the conclusion?
    • Which information is verified, assumed, missing, superseded or contradictory?
    • Has the feasibility, programme, risk register and decision register been updated?

    Evidence to save

    • Building consent application
    • Written Architect response or a recorded reason it is not required
    • Dated feasibility/risk/decision update

    Hold point

    Do not waive a condition, instruct design/work, commit funding, lodge, purchase, settle or represent the conclusion as confirmed until the authorised decision-maker has the required evidence and advice.

    Stop or escalate when

    • The source is missing, old, inconsistent or outside the reviewer's scope.
    • The check changes yield, approval pathway, funding, legal rights, tax, safety or a material cost/programme assumption.
    • A deadline is approaching and the responsible professional has not confirmed the position.

    Documents and records

    • Building consent application
    • Consent tracker
    • RFI tracker
    • Current feasibility, risk register and decision register
    Cost effect
    Record changes to land value, consultant/council cost, construction/civil cost, finance, holding cost, contingency and exit value before whether documentation is complete.
    Programme effect
    Record the decision deadline, dependencies, information lead time and effect on acquisition, consent, procurement, construction, sales or settlement milestones.

    Next action

    drawings

    Applicability: Confirm whether this check applies to the actual site, ownership, strategy, consent pathway, infrastructure and delivery model; record a reason when not applicable.

    Use current site-specific documents and appropriately appointed professional advice. BuildPath does not make the development decision for you.

  2. 02drawingsLevel 2 · Consents
    TaskCheckHold pointEvidenceRecordNext action

    Simple explanation

    drawings

    Technical context

    Test this point against Architectural drawings, the current feasibility version and written input from Engineer. Separate verified facts, professional opinion and assumptions.

    Why it matters: This check can change yield, consent pathway, acquisition terms, funding, cost, programme or exit strategy. It must be resolved before the developer relies on rfi response priorities.

    Prerequisites

    • Architectural drawings is current and its source/date are recorded.
    • The project objective, feasibility version and decision deadline are clear.
    • Engineer has a focused brief where professional confirmation is required.

    Checks

    • Does Architectural drawings directly support the conclusion?
    • Which information is verified, assumed, missing, superseded or contradictory?
    • Has the feasibility, programme, risk register and decision register been updated?

    Evidence to save

    • Architectural drawings
    • Written Engineer response or a recorded reason it is not required
    • Dated feasibility/risk/decision update

    Hold point

    Do not waive a condition, instruct design/work, commit funding, lodge, purchase, settle or represent the conclusion as confirmed until the authorised decision-maker has the required evidence and advice.

    Stop or escalate when

    • The source is missing, old, inconsistent or outside the reviewer's scope.
    • The check changes yield, approval pathway, funding, legal rights, tax, safety or a material cost/programme assumption.
    • A deadline is approaching and the responsible professional has not confirmed the position.

    Documents and records

    • Architectural drawings
    • Consent tracker
    • RFI tracker
    • Current feasibility, risk register and decision register
    Cost effect
    Record changes to land value, consultant/council cost, construction/civil cost, finance, holding cost, contingency and exit value before rfi response priorities.
    Programme effect
    Record the decision deadline, dependencies, information lead time and effect on acquisition, consent, procurement, construction, sales or settlement milestones.

    Next action

    specifications

    Applicability: Confirm whether this check applies to the actual site, ownership, strategy, consent pathway, infrastructure and delivery model; record a reason when not applicable.

    Use current site-specific documents and appropriately appointed professional advice. BuildPath does not make the development decision for you.

  3. 03specificationsLevel 2 · Consents
    TaskCheckHold pointEvidenceRecordNext action

    Simple explanation

    specifications

    Technical context

    Test this point against Engineering drawings, the current feasibility version and written input from Builder. Separate verified facts, professional opinion and assumptions.

    Why it matters: This check can change yield, consent pathway, acquisition terms, funding, cost, programme or exit strategy. It must be resolved before the developer relies on whether build pricing uses issued consent documents.

    Prerequisites

    • Engineering drawings is current and its source/date are recorded.
    • The project objective, feasibility version and decision deadline are clear.
    • Builder has a focused brief where professional confirmation is required.

    Checks

    • Does Engineering drawings directly support the conclusion?
    • Which information is verified, assumed, missing, superseded or contradictory?
    • Has the feasibility, programme, risk register and decision register been updated?

    Evidence to save

    • Engineering drawings
    • Written Builder response or a recorded reason it is not required
    • Dated feasibility/risk/decision update

    Hold point

    Do not waive a condition, instruct design/work, commit funding, lodge, purchase, settle or represent the conclusion as confirmed until the authorised decision-maker has the required evidence and advice.

    Stop or escalate when

    • The source is missing, old, inconsistent or outside the reviewer's scope.
    • The check changes yield, approval pathway, funding, legal rights, tax, safety or a material cost/programme assumption.
    • A deadline is approaching and the responsible professional has not confirmed the position.

    Documents and records

    • Engineering drawings
    • Consent tracker
    • RFI tracker
    • Current feasibility, risk register and decision register
    Cost effect
    Record changes to land value, consultant/council cost, construction/civil cost, finance, holding cost, contingency and exit value before whether build pricing uses issued consent documents.
    Programme effect
    Record the decision deadline, dependencies, information lead time and effect on acquisition, consent, procurement, construction, sales or settlement milestones.

    Next action

    engineering

    Applicability: Confirm whether this check applies to the actual site, ownership, strategy, consent pathway, infrastructure and delivery model; record a reason when not applicable.

    Use current site-specific documents and appropriately appointed professional advice. BuildPath does not make the development decision for you.

  4. 04engineeringLevel 2 · Consents
    TaskCheckHold pointEvidenceRecordNext action

    Simple explanation

    engineering

    Technical context

    Test this point against Specifications, the current feasibility version and written input from Council building consent officer. Separate verified facts, professional opinion and assumptions.

    Why it matters: This check can change yield, consent pathway, acquisition terms, funding, cost, programme or exit strategy. It must be resolved before the developer relies on whether documentation is complete.

    Prerequisites

    • Specifications is current and its source/date are recorded.
    • The project objective, feasibility version and decision deadline are clear.
    • Council building consent officer has a focused brief where professional confirmation is required.

    Checks

    • Does Specifications directly support the conclusion?
    • Which information is verified, assumed, missing, superseded or contradictory?
    • Has the feasibility, programme, risk register and decision register been updated?

    Evidence to save

    • Specifications
    • Written Council building consent officer response or a recorded reason it is not required
    • Dated feasibility/risk/decision update

    Hold point

    Do not waive a condition, instruct design/work, commit funding, lodge, purchase, settle or represent the conclusion as confirmed until the authorised decision-maker has the required evidence and advice.

    Stop or escalate when

    • The source is missing, old, inconsistent or outside the reviewer's scope.
    • The check changes yield, approval pathway, funding, legal rights, tax, safety or a material cost/programme assumption.
    • A deadline is approaching and the responsible professional has not confirmed the position.

    Documents and records

    • Specifications
    • Consent tracker
    • RFI tracker
    • Current feasibility, risk register and decision register
    Cost effect
    Record changes to land value, consultant/council cost, construction/civil cost, finance, holding cost, contingency and exit value before whether documentation is complete.
    Programme effect
    Record the decision deadline, dependencies, information lead time and effect on acquisition, consent, procurement, construction, sales or settlement milestones.

    Next action

    H1/energy

    Applicability: Confirm whether this check applies to the actual site, ownership, strategy, consent pathway, infrastructure and delivery model; record a reason when not applicable.

    Use current site-specific documents and appropriately appointed professional advice. BuildPath does not make the development decision for you.

  5. 05H1/energyLevel 2 · Consents
    TaskCheckHold pointEvidenceRecordNext action

    Simple explanation

    H1/energy

    Technical context

    Test this point against Producer statements, the current feasibility version and written input from Developer. Separate verified facts, professional opinion and assumptions.

    Why it matters: This check can change yield, consent pathway, acquisition terms, funding, cost, programme or exit strategy. It must be resolved before the developer relies on rfi response priorities.

    Prerequisites

    • Producer statements is current and its source/date are recorded.
    • The project objective, feasibility version and decision deadline are clear.
    • Developer has a focused brief where professional confirmation is required.

    Checks

    • Does Producer statements directly support the conclusion?
    • Which information is verified, assumed, missing, superseded or contradictory?
    • Has the feasibility, programme, risk register and decision register been updated?

    Evidence to save

    • Producer statements
    • Written Developer response or a recorded reason it is not required
    • Dated feasibility/risk/decision update

    Hold point

    Do not waive a condition, instruct design/work, commit funding, lodge, purchase, settle or represent the conclusion as confirmed until the authorised decision-maker has the required evidence and advice.

    Stop or escalate when

    • The source is missing, old, inconsistent or outside the reviewer's scope.
    • The check changes yield, approval pathway, funding, legal rights, tax, safety or a material cost/programme assumption.
    • A deadline is approaching and the responsible professional has not confirmed the position.

    Documents and records

    • Producer statements
    • Consent tracker
    • RFI tracker
    • Current feasibility, risk register and decision register
    Cost effect
    Record changes to land value, consultant/council cost, construction/civil cost, finance, holding cost, contingency and exit value before rfi response priorities.
    Programme effect
    Record the decision deadline, dependencies, information lead time and effect on acquisition, consent, procurement, construction, sales or settlement milestones.

    Next action

    fire/access where relevant

    Applicability: Confirm whether this check applies to the actual site, ownership, strategy, consent pathway, infrastructure and delivery model; record a reason when not applicable.

    Use current site-specific documents and appropriately appointed professional advice. BuildPath does not make the development decision for you.

  6. 06fire/access where relevantLevel 2 · Consents
    TaskCheckHold pointEvidenceRecordNext action

    Simple explanation

    fire/access where relevant

    Technical context

    Test this point against Council RFIs, the current feasibility version and written input from QS. Separate verified facts, professional opinion and assumptions.

    Why it matters: This check can change yield, consent pathway, acquisition terms, funding, cost, programme or exit strategy. It must be resolved before the developer relies on whether build pricing uses issued consent documents.

    Prerequisites

    • Council RFIs is current and its source/date are recorded.
    • The project objective, feasibility version and decision deadline are clear.
    • QS has a focused brief where professional confirmation is required.

    Checks

    • Does Council RFIs directly support the conclusion?
    • Which information is verified, assumed, missing, superseded or contradictory?
    • Has the feasibility, programme, risk register and decision register been updated?

    Evidence to save

    • Council RFIs
    • Written QS response or a recorded reason it is not required
    • Dated feasibility/risk/decision update

    Hold point

    Do not waive a condition, instruct design/work, commit funding, lodge, purchase, settle or represent the conclusion as confirmed until the authorised decision-maker has the required evidence and advice.

    Stop or escalate when

    • The source is missing, old, inconsistent or outside the reviewer's scope.
    • The check changes yield, approval pathway, funding, legal rights, tax, safety or a material cost/programme assumption.
    • A deadline is approaching and the responsible professional has not confirmed the position.

    Documents and records

    • Council RFIs
    • Consent tracker
    • RFI tracker
    • Current feasibility, risk register and decision register
    Cost effect
    Record changes to land value, consultant/council cost, construction/civil cost, finance, holding cost, contingency and exit value before whether build pricing uses issued consent documents.
    Programme effect
    Record the decision deadline, dependencies, information lead time and effect on acquisition, consent, procurement, construction, sales or settlement milestones.

    Next action

    inspection list

    Applicability: Confirm whether this check applies to the actual site, ownership, strategy, consent pathway, infrastructure and delivery model; record a reason when not applicable.

    Use current site-specific documents and appropriately appointed professional advice. BuildPath does not make the development decision for you.

  7. 07inspection listLevel 2 · Consents
    TaskCheckHold pointEvidenceRecordNext action

    Simple explanation

    inspection list

    Technical context

    Test this point against Issued consent, the current feasibility version and written input from Architect. Separate verified facts, professional opinion and assumptions.

    Why it matters: This check can change yield, consent pathway, acquisition terms, funding, cost, programme or exit strategy. It must be resolved before the developer relies on whether documentation is complete.

    Prerequisites

    • Issued consent is current and its source/date are recorded.
    • The project objective, feasibility version and decision deadline are clear.
    • Architect has a focused brief where professional confirmation is required.

    Checks

    • Does Issued consent directly support the conclusion?
    • Which information is verified, assumed, missing, superseded or contradictory?
    • Has the feasibility, programme, risk register and decision register been updated?

    Evidence to save

    • Issued consent
    • Written Architect response or a recorded reason it is not required
    • Dated feasibility/risk/decision update

    Hold point

    Do not waive a condition, instruct design/work, commit funding, lodge, purchase, settle or represent the conclusion as confirmed until the authorised decision-maker has the required evidence and advice.

    Stop or escalate when

    • The source is missing, old, inconsistent or outside the reviewer's scope.
    • The check changes yield, approval pathway, funding, legal rights, tax, safety or a material cost/programme assumption.
    • A deadline is approaching and the responsible professional has not confirmed the position.

    Documents and records

    • Issued consent
    • Consent tracker
    • RFI tracker
    • Current feasibility, risk register and decision register
    Cost effect
    Record changes to land value, consultant/council cost, construction/civil cost, finance, holding cost, contingency and exit value before whether documentation is complete.
    Programme effect
    Record the decision deadline, dependencies, information lead time and effect on acquisition, consent, procurement, construction, sales or settlement milestones.

    Next action

    conditions

    Applicability: Confirm whether this check applies to the actual site, ownership, strategy, consent pathway, infrastructure and delivery model; record a reason when not applicable.

    Use current site-specific documents and appropriately appointed professional advice. BuildPath does not make the development decision for you.

  8. 08conditionsLevel 2 · Consents
    TaskCheckHold pointEvidenceRecordNext action

    Simple explanation

    conditions

    Technical context

    Test this point against Building consent application, the current feasibility version and written input from Engineer. Separate verified facts, professional opinion and assumptions.

    Why it matters: This check can change yield, consent pathway, acquisition terms, funding, cost, programme or exit strategy. It must be resolved before the developer relies on rfi response priorities.

    Prerequisites

    • Building consent application is current and its source/date are recorded.
    • The project objective, feasibility version and decision deadline are clear.
    • Engineer has a focused brief where professional confirmation is required.

    Checks

    • Does Building consent application directly support the conclusion?
    • Which information is verified, assumed, missing, superseded or contradictory?
    • Has the feasibility, programme, risk register and decision register been updated?

    Evidence to save

    • Building consent application
    • Written Engineer response or a recorded reason it is not required
    • Dated feasibility/risk/decision update

    Hold point

    Do not waive a condition, instruct design/work, commit funding, lodge, purchase, settle or represent the conclusion as confirmed until the authorised decision-maker has the required evidence and advice.

    Stop or escalate when

    • The source is missing, old, inconsistent or outside the reviewer's scope.
    • The check changes yield, approval pathway, funding, legal rights, tax, safety or a material cost/programme assumption.
    • A deadline is approaching and the responsible professional has not confirmed the position.

    Documents and records

    • Building consent application
    • Consent tracker
    • RFI tracker
    • Current feasibility, risk register and decision register
    Cost effect
    Record changes to land value, consultant/council cost, construction/civil cost, finance, holding cost, contingency and exit value before rfi response priorities.
    Programme effect
    Record the decision deadline, dependencies, information lead time and effect on acquisition, consent, procurement, construction, sales or settlement milestones.

    Next action

    Make and record the stage decision: RFI response priorities. Then open the next applicable development stage.

    Applicability: Confirm whether this check applies to the actual site, ownership, strategy, consent pathway, infrastructure and delivery model; record a reason when not applicable.

    Use current site-specific documents and appropriately appointed professional advice. BuildPath does not make the development decision for you.

Developer go / no-go control

Decision gates before the next commitment

A gate records whether evidence supports a commercial decision. It does not replace advice or predict an authority, lender, purchaser or market outcome.

Before building consent lodgement

Decision: Lodge coordinated documents, resolve gaps, or defer

Minimum evidence

  • • Architectural, structural, civil, services and specifications are coordinated
  • • Design producer statements/calculations and approval dependencies are identified
  • • Consent deliverables reflect the intended procurement and construction scope

Update before deciding

  • • Developed-design quantities and trade scope
  • • Authority, testing and observation requirements
  • • Long-lead procurement and consent response allowance

Stop / escalate when

  • • Unresolved interface changes could invalidate another discipline
  • • Required approval/ownership information is absent
  • • Budget or programme has not been updated for the developed design
Record this gate in the Workspace →

What this stage means

  • Building consent is the part of the project where the developer turns an idea into a checked decision, not a guess.
  • The stage should connect market demand, planning rules, legal constraints, design, cost, funding, time, risk, and exit strategy.
  • For Auckland residential development, the answer is site-specific. The same idea can be low risk on one site and unworkable on the next because of zoning, overlays, title interests, services, slope, flooding, neighbours, or finance.

Why this stage matters

  • Early mistakes become expensive because land, design, consultants, holding costs, consent fees, and finance costs continue even when the project is paused.
  • The developer needs written evidence for lenders, consultants, lawyers, valuers, builders, purchasers, and future dispute protection.
  • This stage usually needs verification from Auckland Council building consents, MBIE Building Code compliance, MBIE Build to the consent before the developer treats the conclusion as reliable.

Step-by-step guide

  1. 1Define the decision needed at the end of this stage and the date it is needed by.
  2. 2Gather the stage documents: Building consent application, Architectural drawings, Engineering drawings, Specifications, and the remaining stage records.
  3. 3Read the documents once for understanding, then again to list unknowns, risks, contradictions, missing evidence, and professional questions.
  4. 4Ask the responsible professionals to confirm the critical points: Architect, Engineer, Builder, Council building consent officer.
  5. 5Update the feasibility, programme, risk register, and decision register with source references and dates.
  6. 6Decide whether to proceed, pause, redesign, renegotiate, add conditions, seek more advice, or abandon the option.
  7. 7Save the evidence in a dated folder and write a short stage closeout note explaining what was decided and why.

What the developer must do

  • Write down the development objective for building consent in one clear paragraph: build-to-sell, build-to-rent, retain one dwelling, subdivide, renovate, or staged development.
  • Open the current feasibility, programme, decision register, risk register, and due diligence folder before making new commitments.
  • Collect the documents needed for this stage: Building consent application, Architectural drawings, Engineering drawings, Specifications, Producer statements, Council RFIs, Issued consent.
  • Send focused questions to the right people: Architect, Engineer, Builder, Council building consent officer, Developer, QS.
  • Record assumptions separately from verified facts so the feasibility does not look more certain than it really is.
  • Update cost, time, consent, finance, and sales assumptions immediately after receiving new information.
  • Escalate anything that changes yield, sale price, cost, timing, consent pathway, title, funding, or settlement risk.

Verification

Source / where to check

Use current official information and the controlled documents for the actual project.

Auckland Council building consents

Auckland Council explains local building consent processes, CCC, related certificates, producer statements, LBP notification, and whether resource consent may also be needed.

MBIE Building Code compliance

Use MBIE Building Performance to find the current Building Code clauses, Acceptable Solutions, Verification Methods, updates, and technical guidance.

MBIE Build to the consent

MBIE guidance explains that work should be built to the issued building consent, inspections must be managed, and records/certificates should be kept for CCC.

Project-specific consented documents and professional advice override generic guidance.

Common mistakes

  • Treating an agent comment, generic online rule, or old document as verified site-specific advice.
  • Forgetting to update the feasibility after design, consent, finance, or market information changes.
  • Not allowing enough contingency, professional fees, council fees, finance costs, holding costs, and time risk.
  • Failing to keep written records of who confirmed what and when.
  • Using building consent to push ahead even when the red flags show the project should pause.

Common risks

  • Yield reduces after proper planning, engineering, title, or infrastructure review.
  • Costs increase after QS, builder, civil, geotechnical, demolition, asbestos, or consent information is received.
  • Programme moves out because consultant inputs, council RFIs, neighbour issues, finance, title, or construction sequencing take longer than assumed.
  • Funding or sales assumptions change before the project reaches settlement.
  • The developer relies on unverified information and loses negotiating power or misses a due diligence deadline.

Common costs

  • Professional fees for planner, architect/designer, surveyor, engineer, QS, lawyer, accountant, valuer, and lender reports.
  • Council fees, consent fees, development contribution estimates, engineering approvals, infrastructure checks, and inspection/monitoring costs where relevant.
  • Design revisions, reports, investigations, demolition/asbestos work, service location, geotechnical testing, and valuation updates.
  • Holding costs such as interest, rates, insurance, utilities, temporary maintenance, and security.
  • Contingency for unverified conditions until the relevant professional confirms them.

Quotes and fee proposals to obtain

  • Obtain written fee proposals or quotations from the relevant stage professionals: Architect, Engineer, Builder, Council building consent officer, Developer, QS.
  • Issue the same current documents and a clear scope to each party so prices, exclusions, assumptions, deliverables, lead times, and programme can be compared.
  • Identify council, authority, investigation, testing, design, construction, monitoring, and close-out charges that may sit outside a consultant or contractor quote.
  • Record every provisional sum, estimate, exclusion, expiry date, dependency, and unverified allowance in the Quote Register and feasibility.
  • Do not approve an appointment or purchase order until scope ownership, evidence required, payment terms, variation process, insurance or competency checks, and completion deliverables are understood.

Common delays

  • Waiting for property file, LIM, title instruments, survey information, consultant reports, or council responses.
  • Design changes caused by planning controls, infrastructure constraints, engineering findings, budget pressure, or market feedback.
  • Lender, valuer, lawyer, or purchaser conditions not being satisfied on time.
  • Council RFI responses needing more consultant work than expected.
  • Construction or subdivision closeout documents not matching settlement or sales deadlines.

Common consultant questions

  • For Building consent, what are the three highest risks that could change cost, time, yield, or approval pathway?
  • Which parts of your advice are confirmed, which are assumptions, and which require another professional to confirm?
  • What documents did you rely on, and are any documents missing, outdated, superseded, or inconsistent?
  • What decision does the developer need to make now, and what should wait until more information is available?
  • What wording should go into the decision register, consultant meeting minutes, or lender/client update?

Red flags

  • A professional says the issue is outside their scope and no one else has been asked to confirm it.
  • The feasibility only works if optimistic sale prices, low construction costs, fast consent, low interest, and no delays all happen together.
  • A title, planning, flooding, geotechnical, access, service, or covenant issue may prevent the intended yield.
  • A seller, agent, builder, or consultant pressures the developer to waive due diligence before core checks are complete.
  • The project file has no written evidence for a major decision.

When to stop and get professional advice

  • Stop and get professional advice when title, easements, covenants, unit title, cross lease, or subdivision matters affect the proposal.
  • Stop and get professional advice when zoning, overlays, activity status, notification, infrastructure capacity, flooding, geotechnical, contamination, or heritage could affect yield.
  • Stop and get professional advice when GST, income tax, entity structure, lending, guarantees, or sale contract terms affect the decision.
  • Stop and get professional advice when the developer is about to sign, waive a condition, lodge consent, start work, approve a variation, accept practical completion, or settle.

Decisions that must be made

  • Whether documentation is complete
  • RFI response priorities
  • Whether build pricing uses issued consent documents

Evidence to save

  • Dated source documents and consultant advice.
  • Feasibility version showing the assumptions used at the time of decision.
  • Risk register and decision register entries.
  • Meeting notes, emails, marked-up plans, calculations, photos, and council/lender/consultant responses.
  • Clear note of who approved the next step and any conditions attached to that approval.

Beginner-friendly example

The developer keeps tender pricing separate from final contract pricing until the issued building consent and RFI changes are understood.

Use this in my project

Turn building consent into controlled action

Open the relevant workspace register, create the project-specific record, link the controlling documents and preserve evidence. The guide does not automatically approve or verify the action.

Open workspace
Create a task →Record a document →Update feasibility →Record a decision →Record a constraint →Compare quotes →
All development stagesDevelopment problem solverDevelopment formsQuote register