One-Folder-Per-Job System for Small Builders

A customer asks why the final invoice is higher than the original quote. The builder knows there were three changes: upgraded windows, an added drain repair, and weekend work requested by the owner. But the evidence is scattered.

• The estimator has the original quote on a laptop.
• The signed contract is in the owner’s email.
• A window selection arrived by text.
• The drain price is written on the back of a material receipt.
• The superintendent’s photos live on a personal phone.
• Accounting has two invoices but not the change orders.
• The permit card is still taped inside the job trailer.

The builder has a fragmented job record. Each person can see part of the history, but nobody can readily trace the final price from the signed scope through the approved changes.

One folder per job is a simple operating rule: every project gets one canonical digital container, one stable job ID, one document index, and one place where the current contractual, field, cost, inspection, and closeout record can be found. That root folder can contain orderly subfolders and link to specialized accounting or scheduling systems. It does not mean dumping every file into a single directory.

The goal is not administrative perfection. It is that an authorized person can answer, quickly and with evidence:

• What did we promise?
• Which version did the customer sign?
• What changed, who approved it, and what did it cost?
• What was selected and ordered?
• What happened on site?
• What is still open?
• What has been billed and paid?
• Which inspections passed?
• What did we hand over?
• Which records must we retain?

This guide addresses U.S. small builders and trade contractors. Contract, payroll, tax, lien, licensing, safety, environmental, permit, warranty, privacy, insurance, and record-retention requirements vary by jurisdiction, business structure, project, and document. Build a retention matrix from actual obligations; do not adopt one blanket deletion period from a generic checklist.

Documentorium can supply the working records inside that folder. Begin with a work-request intake and carry the same job ID into the construction estimate, construction agreement, and every change order. During the job, complete the daily report under that ID; at handoff, finish the record with a completion signoff. Download or file each completed PDF in the matching job folder, using the signed or issued date and revision in the filename.

The forms are most useful when the team follows the same habits every day. The guide to construction daily reports explains what belongs in the field record, signed change orders shows how to preserve customer decisions, and the closeout checklist guide covers the final handoff. Together, they turn the folder from storage into a readable history of the job.

One folder means one source of job identity

Many businesses already have a folder for each project and still cannot find anything. The missing piece is controlled identity.

Assign every opportunity or awarded job a unique ID, for example:

JB-02418

Use that ID in:

• estimate and proposal;
• contract;
• customer and site record;
• folder name;
• schedule;
• purchase order;
• time entry;
• daily log;
• change order;
• invoice and payment allocation;
• permit record;
• inspection;
• photo metadata;
• warranty claim; and
• closeout archive.

The job ID should remain stable even if:

• the customer changes a project nickname;
• the estimator leaves the company;
• the address has formatting variations;
• the work pauses and resumes;
• the contract is amended;
• the project manager changes; or
• the folder is archived.

Do not use only the customer’s last name. Two Smith projects and one address typo will eventually mix records.

Use one authoritative job header

At the top of the folder, maintain a job index with:

• job ID;
• legal customer and billing party;
• property owner if different;
• service address;
• project name;
• project type;
• estimator;
• project manager;
• superintendent or lead technician;
• contract value and current approved value;
• contract status;
• current schedule status;
• permit jurisdiction and permit number;
• insurer, lender, architect, engineer, or adjuster relationships where relevant;
• document-access classification;
• open changes and open deficiencies;
• closeout status; and
• retention class.

The header is an index, not a second contract. It should link to the signed controlling documents rather than paraphrasing them into a conflicting source.

Give every job the same folder skeleton

Consistency is more valuable than an elaborate hierarchy. A new employee should know where a signed change order lives without guessing how a project manager thinks.

Use a structure such as:

JB-02418_customer_short-name_project/
  00_job-index-and-access/
  01_lead-estimate-proposal/
  02_contract-notices-insurance/
  03_design-plans-selections-submittals/
  04_permits-utilities-inspections/
  05_procurement-subcontracts-deliveries/
  06_field-daily-logs-photos/
  07_changes-rfis-customer-decisions/
  08_costs-invoices-payments-lien-docs/
  09_testing-commissioning-punch/
  10_closeout-warranties-owner-handoff/
  11_claims-incidents-legal-hold_restricted/

The numbers keep folders in operational order. The names tell people what belongs inside.

Not every employee should see every folder. Payroll, bank data, claims, medical information, background checks, access credentials, and attorney communications may require separate systems or restricted permissions. One folder per job describes the index and relationship, not unrestricted visibility.

Job index and access

This is the map.

Include:

• job index;
• current document register;
• project contacts and roles;
• emergency contacts;
• responsibility matrix;
• distribution list;
• folder owner;
• permissions list;
• status definitions;
• document naming guide;
• open-item dashboard; and
• links to authoritative accounting, scheduling, CRM, or field systems.

Do not store passwords, alarm codes, lockbox codes, or shared administrative credentials in the general contact sheet. Use a secure credential manager or controlled access process and record only that access was issued.

Add a document register

The register identifies material records without replacing them.

Fields should include:

• document ID;
• type;
• title;
• revision;
• status;
• author or issuer;
• party responsible;
• sent-to list;
• approval or signature status;
• controlling or superseded relationship;
• folder or system link;
• retention class; and
• confidentiality level.

The register is especially valuable for plans, submittals, selections, changes, permits, inspections, and warranties. A filename alone cannot show whether a document is draft, issued for pricing, approved, rejected, superseded, or record copy.

Lead, estimate, and proposal records

Preserve the evidence that created the price.

Include:

• customer inquiry and source;
• site-visit notes;
• measurements;
• pre-quote photos;
• customer requirements;
• existing-condition assumptions;
• subcontractor and supplier quotes;
• labor, material, equipment, and markup estimate;
• alternates and allowances;
• quote revisions;
• proposal sent;
• delivery evidence;
• questions and clarifications; and
• accepted package reference.

Keep the accepted job’s estimate with its supporting assumptions under the applicable retention policy. It is the budget baseline and helps explain scope and cost decisions.

Separate internal estimating detail from the customer-facing proposal. The customer may be entitled to the proposal and contract but not necessarily internal margin calculations, other customers’ pricing, or confidential supplier terms.

Preserve lost and superseded quotes

Mark them clearly:

• Draft—not issued;
• Issued—not accepted;
• Superseded by identified revision;
• Expired; or
• Accepted and incorporated into contract.

Never overwrite final proposal.pdf with a later price. Preserve the exact version delivered and the exact version accepted.

Contract, notices, and insurance records

This folder answers what did we agree to?

Include:

• signed agreement;
• incorporated scope, plans, specifications, allowances, and schedule;
• required licensing and consumer notices;
• cancellation form and delivery evidence;
• financing documents within the authorized process;
• insurance certificates and endorsements;
• bonds;
• owner, landlord, association, or lender approvals;
• permits responsibility;
• tax exemption certificate;
• electronic-signature audit record;
• completed customer copy; and
• amendments that change stable legal terms.

Do not keep only the signature page. Preserve the complete document package presented to and accepted by every signer.

California’s Contractors State License Board tells homeowners to put scope, products, price, payment, permits, and warranties in writing. For California home-improvement contracts, it says that changes to price or scope must be documented in a written change order signed by both parties before the changed work begins. Rules elsewhere may differ; preserve the complete signed contract and the changes approved under its terms.

Lock the executed contract

After signature:

• store a read-only record copy;
• preserve all attachments;
• record the signature workflow;
• prohibit silent editing;
• issue corrections through amendment, not replacement; and
• link the contract value to accounting without turning the accounting field into the legal document.

If a genuine clerical error exists, preserve the original and document the agreed correction.

Design, plans, selections, and submittals

This folder controls what will be built or installed.

Include:

• survey and existing-condition information;
• drawings and specifications;
• engineering;
• shop drawings;
• product data;
• samples;
• color, model, finish, and hardware selections;
• approved substitutions;
• submittal log;
• architect, engineer, owner, or authority comments;
• revision history;
• issued-for-construction set; and
• as-built or record set.

Every document needs a status. A pretty rendering is not necessarily a construction document. A customer’s inspiration photo is not automatically a product selection.

Use statuses such as:

• reference only;
• design in progress;
• submitted for review;
• revise and resubmit;
• approved as noted;
• approved for procurement;
• issued for construction;
• superseded; and
• record/as-built.

Make selections measurable

A selection record should identify:

• category and location;
• manufacturer;
• model or product number;
• finish, color, size, and options;
• quantity;
• allowance basis;
• price difference;
• tax, freight, and lead-time treatment;
• compatibility and required accessory;
• selection decision maker;
• approval action;
• procurement release; and
• substitution process.

White tile from text message is not enough. Capture the message, then issue a structured selection confirmation tied to the job and contract.

Permits, utilities, and inspections

Include:

• permit applications;
• approved plan set;
• permit card;
• plan-review comments;
• revisions;
• contractor and trade registrations;
• utility applications and releases;
• right-of-way, road, environmental, or special permits;
• inspection requests;
• inspection results;
• corrections and reinspection;
• certificate of occupancy, completion, or final approval; and
• closeout correspondence.

Record:

• permit number;
• authority;
• approved scope;
• permit holder;
• inspection type;
• requested and actual status;
• inspector or source;
• correction item;
• responsible party;
• resolution evidence; and
• final status.

Do not use permit passed when only a rough inspection passed. Keep each milestone distinct.

Preserve the approved set

The drawings returned by the authority may differ from the submitted set. Mark the approved set and make it available to the field. When revised, withdraw the superseded field copy and preserve it in the archive.

Procurement, subcontracts, and deliveries

This folder connects scope to cost and materials.

Include:

• purchase orders;
• vendor confirmations;
• subcontracts;
• subcontractor scope and exclusions;
• licensing, insurance, and onboarding evidence;
• shop drawings and approved submittal link;
• order acknowledgments;
• delivery tickets;
• packing slips;
• serial, lot, and batch information where relevant;
• receiving inspection;
• damage and shortage record;
• returns and credits;
• stored-material record;
• owner-furnished material handoff; and
• warranties.

Use the job ID and cost code on each purchase. A credit-card statement shows payment, but it may not identify what was purchased or which job received it. IRS Publication 583 explains that proof of payment alone does not establish entitlement to a tax deduction; keep the supporting invoice or receipt and the job allocation.

Protect vendor and worker data

Do not place unredacted bank forms, taxpayer IDs, background reports, payroll detail, or personal insurance information in the open procurement folder. Store sensitive onboarding and payment data in the authorized finance or HR system and link only the status needed by project staff.

Field daily logs and photos

This is the factual history of work.

A daily log should capture:

• job ID and site;
• author;
• weather and material conditions when relevant;
• workers and subcontractors on site;
• work areas and activities;
• quantities or production;
• equipment used;
• deliveries;
• inspections and visitors;
• customer or design-team direction;
• safety, environmental, or access events;
• delay and cause;
• changed or concealed conditions;
• open questions;
• photos and finding IDs;
• tomorrow’s plan; and
• signature meaning.

Write observations, not blame. No work due to missing owner selection S-07 is more useful than owner delayed us again.

Keep a photo log

Photos should have:

• job ID;
• capture event;
• location;
• direction or component;
• subject;
• phase—before, during, concealed, after, deficiency, correction;
• related daily log, RFI, change, or inspection;
• photographer; and
• privacy classification.

Required photo sets may include:

• preexisting conditions;
• protection and access;
• concealed work before covering;
• utilities and shutoffs;
• measurements and labels;
• installed products and serial numbers;
• damage or shortage;
• changed condition;
• inspection correction;
• completion; and
• owner walkthrough.

Do not rely on a foreman’s personal camera roll. Upload promptly, preserve originals where appropriate, and remove unnecessary images from personal devices under company policy.

Changes, RFIs, and customer decisions

This folder prevents while you’re here work from disappearing.

Separate:

• request for information;
• field clarification;
• proposal request;
• price and schedule quotation;
• change order;
• construction change directive where the contract permits it;
• allowance reconciliation;
• substitution;
• customer selection;
• concealed-condition notice;
• delay notice; and
• claim or reservation of rights.

For each change, preserve the sequence:

1. condition or request;
2. photos, measurements, or source documents;
3. scope impact;
4. price basis;
5. schedule impact;
6. exclusions and dependencies;
7. authorization;
8. field release;
9. work performed;
10. cost and billing; and
11. closeout.

Use statuses:

• identified;
• pricing;
• submitted;
• approved;
• rejected;
• withdrawn;
• time-critical direction pending formalization;
• performed under defined authority; and
• closed.

Do not place unsigned proposed changes in the approved folder. Do not delete rejected proposals; they explain why work was not done.

Capture texts and verbal decisions

When a customer decides by phone or text:

• preserve the original communication;
• issue a written confirmation in the contract’s authorized channel;
• identify scope, price, and schedule effect;
• obtain the required signature before changed work;
• link the approval to field release; and
• give accounting the same change ID.

A screenshot without sender context, job ID, or full conversation can be misleading. Preserve enough context and use a structured confirmation.

Costs, invoices, payments, and lien documents

The project folder supports the ledger; it should not become an uncontrolled duplicate accounting system.

Include or link:

• budget baseline;
• cost codes;
• purchase and subcontract commitments;
• approved changes;
• labor allocation;
• equipment and material costs;
• vendor invoices;
• customer invoices;
• payment applications;
• payment evidence;
• deposits;
• credits and refunds;
• tax treatment;
• retainage;
• lien notices, waivers, releases, and affidavits as applicable;
• collections correspondence; and
• final account reconciliation.

The IRS states that businesses may use a recordkeeping system suited to the business if it clearly shows income and expenses. Its guidance stresses supporting documents and orderly, safe retention. A job folder should make every ledger entry traceable to source evidence without granting field staff access to all bank or payroll data.

Use a three-way match where practical

For material and subcontract costs, connect:

1. approved purchase order or subcontract;
2. delivery or completed-work evidence; and
3. vendor invoice.

Resolve mismatched quantity, price, tax, freight, damage, or credit before payment.

For customer billing, connect:

• contract or change authorization;
• payment milestone or measured work;
• invoice;
• lien document if required; and
• payment allocation.

Do not post a change-order invoice to the base contract without its change ID.

Testing, commissioning, and punch records

Include:

• test plans;
• pressure, leakage, electrical, moisture, compaction, or material tests;
• balancing and commissioning;
• equipment start-up records;
• inspection deficiencies;
• internal quality checks;
• architect or owner punch list;
• correction evidence;
• reinspection or retest; and
• final acceptance status.

Each item needs:

• stable ID;
• exact location;
• requirement;
• observation or measurement;
• responsible party;
• due point;
• correction;
• verification; and
• closure authority.

Do not delete a failed test after the retest passes. Preserve initial result, correction, and final result.

Closeout, warranties, and handoff

Closeout should be built throughout the job, not assembled from memory after final billing.

Include:

• final approved plans or record drawings;
• permit and inspection completion;
• equipment, model, serial, and start-up information;
• operations and maintenance manuals;
• manufacturer and contractor warranties;
• warranty registrations;
• product care instructions;
• finish, color, and selection schedule;
• spare materials and keys;
• owner training;
• final photos;
• punch completion;
• lien and payment closeout;
• certificate or final sign-off;
• customer acceptance or acknowledgment;
• emergency and service contacts; and
• archive manifest.

The customer handoff should be a usable package, not a link to the contractor’s internal folder.

Create an owner copy that:

• contains only authorized customer records;
• uses descriptive file names;
• includes a table of contents;
• opens without proprietary software where possible;
• excludes internal estimates, margins, legal advice, employee data, other customers, and security secrets; and
• remains readable after the contractor changes systems.

Define warranty start events

Record whether each warranty starts at installation, start-up, substantial completion, final payment, registration, closing, or another event. Preserve the governing certificate, not only the marketing headline.

Claims, incidents, and legal holds

This folder needs restricted access and different retention controls.

It may contain:

• injury or property incident;
• safety investigation;
• insurance notice and claim;
• customer complaint;
• demand letter;
• regulator inquiry;
• warranty dispute;
• chargeback;
• litigation hold;
• attorney communication; and
• settlement documentation.

Do not mix attorney-client communications with the ordinary field file and assume a folder name makes them privileged. Follow counsel’s instructions.

When a claim or legal hold applies:

• stop routine deletion for covered records;
• identify custodians and systems;
• preserve texts, emails, photos, logs, and versions;
• prevent alteration;
• document collection; and
• release the hold only through the authorized process.

Use file names that sort and explain themselves

A practical pattern is:

JOBID_document-type_sequence_or_subject_revision_status.ext

Examples:

JB-02418_contract_rev-0_executed.pdf
JB-02418_change-order_CO-003_approved.pdf
JB-02418_selection_S-014_kitchen-faucet_approved.pdf
JB-02418_daily-log_042.pdf
JB-02418_photo_F-008_north-wall_concealed-plumbing.jpg
JB-02418_invoice_INV-005_issued.pdf
JB-02418_closeout-index_record.pdf

Dates can help sort event records when the workflow uses an unambiguous YYYY-MM-DD format, but a date should not replace revision, document type, or status. The signed contract date does not tell a user whether the file is complete or superseded.

Avoid:

• final.pdf;
• final2.pdf;
• newest contract.pdf;
• IMG_8341.jpg;
• scan.pdf;
• customer Social Security number in a filename;
• bank account in a filename; and
• punctuation that breaks synchronization or links.

Separate revision from status

• Revision identifies content version.
• Status identifies permitted use.

Rev 3 — submitted can later become Rev 3 — approved without changing content. Rev 4 means content changed.

Record both in metadata or the document register. Do not rename the only file until no one can trace what was issued.

Set a capture rule for every channel

Important job decisions arrive through:

• email;
• text message;
• messaging app;
• phone call;
• video meeting;
• paper note;
• supplier portal;
• permit portal;
• field application;
• accounting software; and
• customer signature platform.

The rule should be:

If the communication changes scope, price, time, selection, safety, access, quality, payment, warranty, or responsibility, capture it in the job record through the corresponding controlled document.

Examples:

• phone request becomes a change request;
• texted fixture selection becomes a documented selection approval under the contract’s process;
• email schedule direction becomes a schedule notice;
• supplier substitution becomes a submittal;
• verbal inspection correction becomes a written inspection item; and
• site disagreement becomes a daily log and issue record.

Do not dump every email into the folder. Preserve material decisions and their context, then link them to the controlled workflow.

Set role-based access

Not everyone needs everything.

The FTC recommends taking stock of personal information, keeping only what the business needs, protecting it, disposing of it properly, and planning for incidents. Apply those principles to every job folder.

Use:

• individual accounts;
• multi-factor authentication;
• least privilege;
• prompt offboarding;
• access logs;
• encryption in transit and at rest;
• secure sharing links;
• download controls where appropriate;
• device security; and
• incident response.

Do not share one company cloud password with the entire crew.

Back up the folder and test restoration

Cloud synchronization is not automatically a backup. Deletion, ransomware, account takeover, or a bad sync can propagate.

CISA’s StopRansomware Guide recommends protected backups and regular restoration tests. Build a proportionate plan with:

• automated backups;
• separate recovery copies;
• version history;
• protection against deletion or overwrite;
• encryption;
• documented recovery credentials;
• backup monitoring;
• periodic restore test;
• defined recovery point and recovery time; and
• continuity procedure when the main system is unavailable.

Test by restoring a closed-job folder and confirming:

• index works;
• signed PDFs open;
• photos retain association;
• versions remain distinct;
• permissions can be reconstructed;
• accounting links have exports; and
• customer closeout can be reproduced.

A backup that has never been restored is an assumption.

Use a retention matrix, not a single rule

The IRS says record retention depends on the action, expense, or event recorded. Tax supporting documents generally remain necessary through the applicable limitations period, employment-tax records have their own minimum, property records can continue through disposition-related periods, and non-tax duties may require longer retention.

For each document class, identify:

• record owner;
• governing law, contract, warranty, insurance, tax, permit, or policy;
• retention start event;
• minimum period;
• longer dependency;
• legal-hold override;
• disposal authorization;
• deletion method;
• customer-copy rule; and
• archive format.

Classes may include:

• estimate and contract;
• change order;
• plans and permits;
• payroll and time;
• tax and expense support;
• employee safety record;
• environmental record;
• equipment and property basis;
• warranty and maintenance;
• customer financial information;
• access credentials;
• incident and insurance claim;
• photos; and
• closeout.

Do not keep sensitive records forever merely because storage is cheap. Do not delete a contract because the tax period passed while a warranty, limitation period, claim, or licensing rule remains.

Dispose securely

When the retention rule permits deletion:

• confirm no hold or open claim;
• obtain authorized approval;
• delete production copies and let protected recovery copies expire under the approved retention schedule;
• shred paper with sensitive data;
• securely dispose of retired devices and media;
• revoke shared links;
• record the disposition; and
• preserve the archive manifest where appropriate.

Simple desktop deletion may not securely erase the data.

Keep paper under the same job ID

Small builders still need paper on site. Use one field binder or board with:

• current approved plans;
• permit card;
• site contacts;
• emergency and safety information;
• current scope and approved changes;
• inspection status;
• material or equipment instructions needed in the field;
• daily log capture; and
• controlled forms.

Mark paper copies:

• job ID;
• revision;
• status;
• controlled or uncontrolled copy;
• replaced-by reference; and
• return or destruction process.

At update, remove superseded field documents. Scan signed or annotated originals promptly, preserving whether the paper original must also be retained.

Close the folder deliberately

A job is not closed when the crew leaves.

Use a closeout gate:

• [ ] Contract scope and approved changes are complete
• [ ] Open RFIs and selections are resolved
• [ ] Permits and inspections are final
• [ ] Testing and commissioning are complete
• [ ] Punch list is closed or transferred by written agreement
• [ ] Customer invoices and payments reconcile
• [ ] Vendor and subcontract costs and credits reconcile
• [ ] Lien documents are complete where applicable
• [ ] Warranties are registered and delivered
• [ ] Owner manuals, training, keys, and spares are delivered
• [ ] Final photos and as-builts are stored
• [ ] Customer closeout packet is exported
• [ ] Sensitive temporary access is revoked
• [ ] Folder permissions change from active to archive
• [ ] Retention classes and legal holds are applied
• [ ] Backup and restore evidence exists

After closeout, freeze the record copy. Warranty service, claims, or later changes should create linked records without rewriting the historical job.

Roll out the system without stopping work

Define the minimum

Choose:

• job ID format;
• folder skeleton;
• document statuses;
• file naming;
• owner of each folder;
• required records at contract, field start, billing, and closeout; and
• access roles.

Pilot on one active job

Do not reorganize the entire company first. Pick one moderate project, create the folder, and test:

• estimate-to-contract transition;
• selection capture;
• daily logs and photos;
• change approval;
• vendor invoice match;
• billing; and
• closeout index.

Fix the friction

If crews avoid the system, find the actual obstacle:

• too many required fields;
• poor mobile upload;
• slow connection;
• unclear owner;
• duplicate entry;
• permissions block;
• bad filename automation; or
• no feedback after submission.

Keep mandatory evidence; simplify needless clicks.

Bring active jobs into the system

Move only known, non-secret project records through a controlled process. Do not delete source data until completeness, access, backup, and retention are verified.

Create a migration manifest:

• source location;
• record owner;
• files copied;
• duplicates resolved;
• missing documents;
• restricted data separated;
• validation completed; and
• source disposition authorized.

Archive older closed jobs separately after risk-based review.

Weekly folder audit

For every active job, ask:

• Is the executed contract complete and locked?
• Does current approved value equal base plus approved changes?
• Are unsigned changes separated from approved changes?
• Do field workers have the current plan and scope?
• Are selections approved before procurement?
• Are daily logs and photos current?
• Are permit corrections assigned and closed?
• Can each invoice be traced to authority and evidence?
• Are sensitive records restricted?
• Are closeout records being collected now?
• Did backup complete, and has restoration been tested on schedule?

The audit should produce named actions, not a score nobody uses.

Sources

• Internal Revenue Service — Recordkeeping
• Internal Revenue Service — Publication 583, Starting a Business and Keeping Records
• Internal Revenue Service — How Long Should I Keep Records?
• U.S. Small Business Administration — Manage Your Finances
• U.S. Small Business Administration — Business Guide
• California Contractors State License Board — What Is a Home Improvement Contract?
• California Contractors State License Board — Consumer Guide to Filing Construction Complaints
• Federal Trade Commission — Protecting Personal Information: A Guide for Business
• Federal Trade Commission — Start With Security: A Guide for Business
• Cybersecurity and Infrastructure Security Agency — Protect Data Stored on Your Devices
• Cybersecurity and Infrastructure Security Agency — Use Logging on Business Systems
• Cybersecurity and Infrastructure Security Agency — StopRansomware Guide

Disclaimer

This article is general information, not legal, tax, accounting, cybersecurity, or construction advice for a particular job. Retention periods, contract and permit requirements, privacy duties, and access controls depend on the applicable jurisdiction, agreement, record, and circumstances. Confirm the requirements for your projects with qualified advisers and the relevant authorities before setting policy or disposing of records.