Common questions about EdgeRecord engagements.
The questions below come up most often during scoping conversations. If your situation isn't covered here, the answer is probably "yes, with conditions" — start a conversation and we will tell you whether the engagement is a good fit before any work begins.
What is EdgeRecord, in one sentence?
EdgeRecord is a technical recordkeeping service that documents what exists, what changed, who touched it, and what evidence remains — for systems where memory and screenshots are not enough.
Who actually reads an EdgeRecord report?
Three audiences. Operators and engineers use it to trust the running state of a system. Executives use it to make decisions without translating jargon. Reviewers — insurance, legal, audit, regulators, and vendor accountability conversations — use it as structured evidence.
Is this an audit?
No. EdgeRecord is operational recordkeeping, not certification. We document what is true at a moment in time and what changed between two moments. The output is evidence the business can use, not a pass or fail stamp.
Do you need access to our production systems?
Not always. Many engagements work from existing artifacts: configuration exports, change tickets, vendor reports, monitoring data, backup manifests, and conversations with the people who own the systems. Where direct access is required, scope is agreed in writing first.
What does the engagement actually look like?
Every engagement starts with a scoping conversation. From there: capture the current state, record the change or incident, gather supporting artifacts, write the report in operator-readable, executive-readable, and reviewer-readable form, and deliver. Most starter engagements complete in seven business days.
Will you keep our infrastructure data?
Only what is required to deliver the engagement. Sensitive material is handled under a written agreement, and clients can request that working copies be destroyed once the report is delivered. See our privacy and confidentiality page for details.
How is this different from a managed service provider?
An MSP runs your systems. EdgeRecord documents them. The two roles can coexist — in fact, EdgeRecord is often most useful when there is an MSP, a vendor, or an internal team whose work needs an independent operational record.
Can you work alongside our existing tools?
Yes. EdgeRecord is designed to fit on top of whatever ticketing, monitoring, configuration management, or backup tooling is already in place. The deliverable is a record, not another platform to maintain.
What if we only have one upcoming change to document?
That is the most common starting point. The Change Evidence Sprint package exists for exactly this case — a single migration, vendor visit, firewall change, cloud update, or incident review.
How do we start?
Send a short note describing the system, change, incident, or recovery question you need documented. A scoping reply usually comes back within one business day.