Home Approach Solutions Availability Contact
Availability

Scheduling an audit engagement

Audit engagements are scheduled on a rolling basis. The information below describes how the scheduling process works and what to expect when you reach out.

How Scheduling Works

From first inquiry to confirmed start date

Each audit engagement requires a discovery call before a start date is confirmed. This call is necessary because the scope, data requirements, and timeline vary depending on the size and complexity of your API surface. We do not confirm start dates before completing this initial conversation.

After the discovery call, we provide a written scope summary and proposed timeline. Once the scope is agreed upon, we schedule the engagement start. The time between inquiry and engagement start depends on current scheduling and the lead time needed to prepare for data collection.

Continuous Review engagements are scheduled differently from one-time audits. If you are interested in an ongoing arrangement, the scheduling conversation will cover the cadence, reporting format, and how we handle communication between quarterly cycles.

Current Availability

Availability for new engagements is updated on an ongoing basis. Contact us to discuss current scheduling and expected lead times.

Check Availability

Typical Timelines

  • Focused Audit2-3 weeks
  • Full Surface Audit3-5 weeks
  • Continuous ReviewQuarterly cycles
Planning Considerations

Factors that affect audit timing

API Surface Size

Larger API surfaces require more analysis time. An estate with hundreds of endpoints will take longer to examine than one with a focused set of services. This affects both the audit duration and the preparation time needed before analysis begins.

Historical Data Availability

Audits that can draw on several months of historical log and trace data produce richer findings than those limited to recent data. If your retention period is short, this affects what patterns are detectable and should be discussed during the discovery call.

Team Availability for Discovery

The discovery phase requires time from engineers who understand the API landscape and the systems that depend on it. Scheduling this phase depends on the availability of the relevant people on your team, not just on our calendar.

Data Access and Security Review

Organizations with strict data handling requirements may need time for internal security review before data sharing arrangements are confirmed. We can discuss data handling approaches during the discovery call to help your team prepare.

Next Steps

How to move forward

Send an inquiry

Use the contact form or email us directly with a brief description of your API landscape and what prompted your interest in an audit. This helps us prepare for the discovery call.

Discovery call

We schedule a call to understand your API landscape, current concerns, and what data is available. This typically runs 45 to 60 minutes.

Scope agreement

We provide a written scope summary with a proposed timeline. Once agreed, we confirm the engagement start date.

Engagement begins

Data collection starts on the agreed date. We keep you informed at key milestones and flag anything that requires your input during the analysis phase.