Heritage Documentation Standards: International Frameworks and Indian Best Practice

Why This Matters

Heritage documentation without a clear standard is documentation to an unknown quality. It may be adequate; it may not be. The problem with unknown quality documentation is that it cannot be used with confidence. A heritage report submitted to a planning authority whose drawings were produced to an undeclared and unverifiable standard will face scrutiny. An archive of photographs of an important building, taken without systematic coverage, without scale references, without metadata, may record the building's appearance — but not in a form that permits accurate measurement or comparison with future surveys.

Standards serve three purposes. First, they define a minimum acceptable quality so that professionals, clients and regulators share a common expectation. Second, they enable independent verification — if work claims to comply with a named standard, the claim can be checked. Third, they ensure that documentation produced by one person can be understood and used by another — essential for work that is intended to serve generations of future professionals and researchers.

In India, the absence of a single unified national heritage documentation standard has created a fragmented landscape in which quality varies enormously between ASI-supervised projects, state archaeology department work, private conservation commissions, and academic research. Understanding the international framework provides a coherent basis for professional practice even where national requirements are incomplete.

Foundational Principles

Before specific standards, it is important to establish the principles that govern all heritage documentation regardless of the specific framework applied. These principles are distilled from the major international charters and represent the consensus of the international conservation community.

International Frameworks

International heritage documentation standards derive from a hierarchy of charters, guidelines and technical standards. The hierarchy runs from philosophical charters (Venice, Burra, INTACH) through methodological guidelines (ICOMOS-CIPA, UNESCO) to technical specifications (HABS levels, E-RIHS protocols).

HABS / HAER Documentation Levels

The Historic American Buildings Survey (HABS), Historic American Engineering Record (HAER) and Historic American Landscapes Survey (HALS) define three documentation levels that have been widely adopted as a practical shorthand for documentation intensity internationally, including in Indian practice.

ICOMOS-CIPA Standards

The ICOMOS International Scientific Committee on Heritage Documentation (CIPA) has produced the most technically detailed and authoritative set of standards for heritage recording. CIPA's guidelines address photogrammetry, TLS, digital documentation and data management in specific technical depth.

CIPA's core documentation standard establishes five quality levels for heritage documentation, defined by positional accuracy and drawing content rather than by documentation method:

CIPA also specifies requirements for photographic documentation: systematic facade photography (100% coverage, controlled overlap), close-range record photography (every significant element from square-on), contextual photography (setting, approach, relationship to landscape), and archival photography (large-format or high-resolution digital with colour targets, scale bars and metadata).

For digital heritage documentation, CIPA recommends: raw format capture with full metadata; open format archiving (TIFF for images, E57/LAS for point clouds, IFC for BIM, PDF/A for reports); and archival metadata to Dublin Core standard minimum.

Indian Standards and Requirements

Indian technical standards for heritage documentation are fragmented across multiple authorities and documents. No single unified national heritage documentation standard exists comparable to English Heritage's measured survey guidelines or the HABS program. The following documents constitute the relevant Indian standards framework.

Authority-Specific Requirements

In Indian practice, the authority with jurisdiction over a heritage building determines the documentation requirements. These vary significantly and must be investigated at project inception.

The Documentation Plan

A documentation plan is the project document that translates general standards into specific requirements for a particular building, site and purpose. It should be produced at the beginning of every heritage documentation project and agreed with the client and relevant authority before fieldwork begins.

A documentation plan contains:

1. 1Purpose statement — why documentation is being undertaken; what decisions or actions it will support; who will use the documentation and for what purpose.
2. 2Significance statement (preliminary) — what aspects of the building are considered to be of heritage significance; this determines what must be documented comprehensively versus what requires only overview coverage.
3. 3Documentation scope — which drawing types, at what scales, covering which areas of the building; which photographic records; what written records.
4. 4Standards compliance statement — which international and national standards the documentation will be produced to; how compliance will be verified.
5. 5Accuracy specification — the positional accuracy required for each drawing type; the measurement method that will be used to achieve it.
6. 6Personnel and competency — who will undertake each element; what qualifications and experience they will bring.
7. 7Data management plan — how data will be stored during production; what format archival copies will be produced in; where they will be held and for how long.
8. 8Programme — field survey dates; drawing production schedule; review and approval process.
9. 9Budget — detailed enough to identify if scope changes will affect cost.

Data Management and Archiving

Documentation that cannot be found, read or understood fifty years from now has failed its purpose. Archiving standards are as important as production standards.

Quality Assurance

Quality assurance (QA) in heritage documentation is the systematic process of verifying that documentation meets the specified standard before issue. Without QA, there is no basis for claiming standard compliance.

• Drawing check — all drawings reviewed against field notes by a person who was not involved in either fieldwork or CAD production; key dimensions verified; notes resolved.
• Scale and accuracy check — key dimensions scaled from the drawing and compared to field measurements; discrepancies above tolerance investigated and corrected.
• Completeness check — drawing set reviewed against documentation plan scope; all required drawing types, scales and areas accounted for; any gaps noted and justified.
• Metadata check — all photographs have IPTC metadata populated; GPS coordinates present where specified; drawing title blocks complete.
• Format compliance check — all files in specified format; archival copies produced; naming convention applied consistently.
• Standards compliance statement — final declaration by project lead that documentation meets the specified standard; identification of any elements that do not fully comply and the reason.

Standard Selection: Decision Framework

Selecting the appropriate standard for a documentation project depends on four factors: the heritage significance of the subject, the regulatory authority with jurisdiction, the purpose of documentation, and the available budget.

Indian Practice Context

Indian heritage documentation practice is in a state of transition. The generation of conservation professionals trained in the 1980s and 1990s produced primarily hand-drawn measured drawings and print photographic records. The current generation is adopting photogrammetry, TLS and BIM. Standards are adapting unevenly.

Several practical realities shape Indian documentation practice that international standards do not fully anticipate.

• ASI's protected monument portfolio of 3,693 sites greatly exceeds its documentation capacity; many significant sites have no systematic measured drawings; INTACH's unlisted heritage is even less documented.
• The Survey of India's GTS benchmark network is the national height datum but benchmark density and maintenance vary by state; in some regions, benchmarks are damaged or relocated; always verify benchmark before use.
• WGS84 horizontal datum vs the older Everest 1830 datum used in older Indian maps creates coordinate offsets of 100–200m in South India; always specify datum on all survey drawings; see the article on Remote Sensing for India for datum transformation notes.
• Tamil Nadu's Agama Shastra — the traditional canon governing temple construction — creates specific documentation requirements for temples under HR&CE administration; documentation must identify elements governed by Agama Shastra versus later additions.
• India's monsoon creates documentation windows: July–September (northeast monsoon in Tamil Nadu) and June–September (southwest monsoon) make field survey difficult and may affect photogrammetric record quality; plan surveys in pre-monsoon or post-monsoon periods where possible.

Common Mistakes

The following failures in standards compliance account for the majority of documentation quality problems in Indian heritage projects.

• Specifying a documentation standard without a documentation plan — naming 'HABS Level II' as the scope without a project-specific drawing list, scale and accuracy specification, leaving both parties with different expectations.
• Omitting metadata — photographs filed without IPTC metadata, without GPS location, and without reference to the drawing they illustrate; impossible to use effectively by anyone other than the original photographer.
• Using non-archival formats — submitting DWG files (software-version dependent), JPEG files at compressed quality, or proprietary point cloud formats without archival conversion; format obsolescence will make these unreadable within 10–20 years.
• Failing to record the datum — drawings produced without a stated datum level or benchmark reference cannot be compared to any future survey; a critical loss for buildings that will require monitoring over decades.
• Treating documentation as the last task — documentation planned as the final project activity is always compressed; documentation must be planned at project inception and resourced proportionately.
• No QA process — documentation reviewed only by its creator; systematic errors (wrong scale, accumulated dimension error, missed elements) pass into the archive uncorrected.
• Under-documenting during construction or conservation works — demolition phases, exposed construction details and hidden fabric revealed during intervention are irreplaceable; a photographic record brief must be in place before works begin.

Field Notes

**The ASI brief that wasn't.** On a heritage conservation project at a centrally protected monument in Tamil Nadu, the project architect specified 'ASI standard drawings' as the documentation requirement. On completion of fieldwork and drawings, ASI's reviewing Superintending Archaeologist requested additional drawings at a scale and content not included in the original brief. The additional surveys cost the client six weeks delay and approximately ₹8 lakhs in additional fees. The lesson: 'ASI standards' is not a scope; request the specific project brief from the relevant ASI Circle office before accepting or estimating a documentation commission for a protected monument.

**The datum that migrated.** A measured survey of a significant 19th-century institutional campus used a temporary benchmark established on a stone step at the main entrance. Three years later, the step was repaired and lowered by 50mm. A subsequent survey produced for extension planning was connected to the same benchmark — now 50mm different from the original datum. Floor levels in new drawings differed from the original survey by exactly 50mm. The lesson: always connect to a permanent Survey of India GTS benchmark; record the benchmark fully (number, location, elevation); verify before use on any subsequent survey.

**Photogrammetric records saved by metadata.** A photogrammetric documentation project for a significant carved gateway produced approximately 4,000 photographs over two days. The project was archived. Five years later, when a carved panel fragment was found and its original location needed to be determined, the photogrammetric model was reopened. Because each photograph had IPTC metadata including date, time, GPS location and camera settings, it was possible to reconstruct the camera positions precisely and identify the original location of the fragment in the 3D model. Documentation with proper metadata is documentation that serves future researchers in ways that cannot be anticipated at the time of recording.

Documentation Standard Compliance Checklist

Use at project inception to establish the documentation plan, and at project completion to verify compliance.

1. 1Has the regulatory authority been identified and their specific documentation requirements obtained in writing?
2. 2Has a documentation plan been produced and agreed with the client covering: purpose, scope, standards, accuracy, personnel, data management and programme?
3. 3Has the appropriate standard been selected (HABS level, ICOMOS-CIPA level, or project-specific) and agreed?
4. 4Has the datum and benchmark been established and recorded on the drawings?
5. 5Are drawing title blocks complete: building name, drawing title, scale at print size, date, surveyor, drawing number?
6. 6Is the measurement method declared on each drawing with its accuracy specification?
7. 7Are all photographs labelled with building reference, element, direction of view and date — and does IPTC metadata include this information?
8. 8Are archival copies of all deliverables in open, non-proprietary formats (PDF/A, TIFF, E57, CSV)?
9. 9Has an independent QA check been completed against the field notes and the documentation plan scope?
10. 10Has a standards compliance statement been produced, declaring the standard achieved and noting any departures with reasons?

Professional Practice

In professional practice, the documentation standard conversation must happen with the client and the regulatory authority before any fee is agreed. Clients without heritage experience often assume that 'a set of drawings' is a sufficient scope description. The professional obligation is to explain what standard is appropriate, what it requires in terms of time and resources, and why it matters for the intended purpose.

Fee proposals for heritage documentation should reference the specific standard being applied. A fee proposal that says 'we will produce measured drawings to ICOMOS-CIPA Level 3 standard with a documentation plan, QA report and archival delivery in PDF/A and E57 formats' is a professional commitment that can be verified. A fee proposal that says 'we will produce measured drawings' is an ambiguity waiting to become a dispute.

Post-project archiving is a professional responsibility that few Indian clients plan for. The default outcome — documentation delivered to client and stored on a hard drive that may fail — does not serve the heritage mission. Conservation professionals should advocate for submission of significant documentation to ASI, INTACH, relevant state archives, or institutional repositories where this is possible. For private clients, recommend at minimum cloud storage with independent backup and a commitment to update formats when necessary.

Standards familiarity is a professional competency that benefits from active maintenance. ICOMOS and CIPA update guidelines periodically; ASI requirements change; new digital documentation technologies create new standards needs. Professional development through INTACH short courses, ICOMOS workshops, and CIPA events is the most effective way to stay current.